SIEMENS
SIMATIC
Industrial Software
 


___________________
___________________
___________________
___________________
___________________
___________________
___________________
___________________
___________
___________________
___________
___________________
___________________
___________________
___________________
SIMATIC
Industrial Software
SIMATIC Safety - Configuring and
Programming
Programming and Operating Manual
10/2018
A5E02714440
-AH
Important notes
Product Overview
1
Configuring
2
Safety Administration Editor
3
Access protection
4
Programming
5
F-I/O access
6
Implementation of user
acknowledgment
7
Data exchange between
standard user program and
safety program
8
Safety-related
communication
9
Compiling and
commissioning a safety
program
10
System acceptance
11
Operation and Maintenance
12
Overview of instructions for
the safety program
13
Monitoring and response
times
A
Checklist
B
Siemens AG
Division Digital Factory
Postfach 48 48
90026 NÜRNBERG
GERMANY
09/2018 Subject to change
Copyright © Siemens AG 2011 - 2018.
All
rights reserved
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by
personnel qualified
for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 3
Important notes
Purpose of this documentation
The information in this documentation enables you to configure (Page 43) and program
(Page 111) SIMATIC Safety fail-safe systems. In addition, you will obtain information on
acceptance (Page 361) of a SIMATIC Safety F-system.
Note
The Programming and Operating Manual "SIMATIC Safety
- Configuring and Programming"
in its latest
version (possibly including product information for the manual) is the relevant
source of all information on functional safety regarding configuring and programming. This
also applies in the event of discrepancies between this manual and other documentatio
n on
functional safety regarding configuring and programming
You must heed all warnings in the Programming and Operating manual "SIMATIC Safety
-
Configuring and Programming".
Basic knowledge requirements
General basic knowledge of automation engineering is needed to understand this
documentation. Basic knowledge of the following is also necessary:
Fail-safe automation systems
Automation systems S7-300/400/1200/1500/1500 Software Controller/WinAC RTX F
Distributed I/O systems on PROFIBUS DP/PROFINET IO
Totally Integrated Automation Portal, including:
Hardware configuration with the
hardware and network editor
Programming in the LAD and FBD programming languages using the
program editor
.
Communication between CPUs
Important notes
SIMATIC Safety - Configuring and Programming
4 Programming and Operating Manual, 10/2018, A5E02714440-AH
Scope of this documentation
This documentation is valid for the optional packages
STEP 7 Safety Advanced V15.1
and
STEP 7 Safety Basic V15.1.
The optional packages
STEP 7 Safety Advanced V15.1
and
STEP 7 Safety Basic V15.1
are
used for configuration and programming of the fail-safe SIMATIC Safety system.
In this context, integration of the fail-safe I/O listed below in SIMATIC Safety is also
addressed:
S7-1500/ET 200MP fail-safe modules
ET 200SP fail-safe modules
ET 200S fail-safe modules
ET 200eco fail-safe I/O modules
ET 200eco PN fail-safe I/O modules
ET 200pro fail-safe modules
ET 200iSP fail-safe modules
S7-300 fail-safe signal modules
S7-1200 fail-safe modules
Fail-safe GSD based DP slaves
Fail-safe GSD based I/O devices
Approvals
The SIMATIC Safety F-system is certified for use in safety mode up to:
Safety integrity level SIL3 in accordance with IEC 61508:2010
Performance Level (PL) e and category 4 in accordance with ISO 13849-1:2015 or EN
ISO 13849-1:2015
Incorporation in the information landscape
Depending on your application, you will need the following supplementary documentation
when working with
STEP 7 Safety
.
Important notes
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 5
This documentation includes references to the supplementary documentation where
appropriate.
Documentation
Brief description of relevant content
For the SIMATIC Safety F-system Depending on which F-CPU you are using, you will need the following docu-
mentation:
For the F-CPUs S7-1200/1500, a Product Information
(http://support.automation.siemens.com/WW/view/en/109478599) de-
scribes all deviations from the respective standard CPUs.
Each F-CPU S7-300/400 that can be used has its own product infor-
mation. The product information describes the deviations from the respec-
tive standard CPUs.
The Device manuals
(http://support.automation.siemens.com/WW/view/en/67295862/133300)
describe the S7-1500 CPUs.
The "S7-300, CPU 31xC and CPU 31x: Installation"
(http://support.automation.siemens.com/WW/view/en/13008499) operating
instructions describe the installation and wiring of S7-300 systems.
The "CPU 31xC and CPU 31x, Technical Data"
(http://support.automation.siemens.com/WW/view/en/12996906) device
manual describes the CPUs 315-2 DP and PN/DP, the CPU 317-2 DP and
PN/DP, and the CPU 319-3 PN/DP.
The "S7-400 Automation System, Installation
(http://support.automation.siemens.com/WW/view/en/1117849) installation
manual describes the installation and wiring of S7-400 systems.
The "S7-400 Automation System, CPU Data"
(http://support.automation.siemens.com/WW/view/en/23904550) reference
manual describes the CPUs 414-3 PN/DP, the CPU 416-2, and the
CPU 416-3 PN/DP.
The "ET 200S Interface Module IM 151-7 CPU"
(http://support.automation.siemens.com/WW/view/en/12714722) manual
describes the IM 151-7 CPU.
The "ET 200S, Interface Module IM 151-8 PN/DP CPU"
(http://support.automation.siemens.com/WW/view/en/47409312) manual
describes the IM 151-8 PN/DP CPU.
The "ET 200S, Interface Module IM 154-8 CPU"
(http://support.automation.siemens.com/WW/view/de/24363739/0/en) man
ual describes the IM 154-8 CPU.
The Manual "Windows Automation Center RTX WinAC RTX (F) 2010
(http://support.automation.siemens.com/WW/view/en/43715176)" de-
scribes the WinAC RTX 2010 and the WinAC RTX F 2010.
The "S7-1500 Software Controller CPU 1505SP, CPU 1507S
(http://support.automation.siemens.com/WW/view/en/109249299)" manual
describes the SIMATIC S7-1500 Software Controller 1505SP and CPU
1507S.
"S7-1200 Functional Safety manual
(http://support.automation.siemens.com/W
W/view/en/104547552)" system manual
Describes the F-CPUs S7-1200 and the fail-safe modules S7-1200 (including
installation, wiring, and technical specifications)
Important notes
SIMATIC Safety - Configuring and Programming
6 Programming and Operating Manual, 10/2018, A5E02714440-AH
Documentation
Brief description of relevant content
"S7-1500/ET200MP system manual
(http://support.automation.siemens.com/W
W/view/en/59191792)" system manual
and the product manuals
(https://support.industry.siemens.com/cs/w
w/en/ps/14141/man) for the corresponding
S7-1500/ET 200MP fail-safe modules
Describes the hardware of the S7-1500 systems and the S7-1500/ET 200MP
fail-safe modules (including installation, wiring, and technical specifications)
"ET 200SP distributed I/O system
(http://support.automation.siemens.com/W
W/view/en/58649293)" system manual
and the product manuals
(https://support.industry.siemens.com/cs/w
w/en/ps/14059/man) for the corresponding
ET 200SP fail-safe modules
Describes the hardware of the ET 200SP fail-safe modules (including installa-
tion, wiring, and technical specifications)
"ET 200eco Distributed I/O Station Fail-
safe I/O Block
(http://support.automation.siemens.com/W
W/view/en/19033850)" manual
Describes the hardware of the ET 200eco fail-safe I/O module (including in-
stallation, wiring, and technical specifications)
Manual "ET 200eco PN F-DI 8 x 24 VDC,
4xM12 / F-DQ 3 x 24 VDC/2.0A PM,
3xM12
(https://support.industry.siemens.com/cs/w
w/en/)"
Describes the hardware of the ET 200eco PN fail-safe I/O module (including
installation, wiring, and technical specifications)
"Distributed I/O System ET 200S, Fail-
Safe Modules
(http://support.automation.siemens.com/W
W/view/en/27235629)" operating instruc-
tions
Describes the hardware of the ET 200S fail-safe modules (including installa-
tion, wiring, and technical specifications)
"S7-300 Automation System, ET 200M
Distributed I/O System, Fail-safe Signal
Modules
(http://support.automation.siemens.com/W
W/view/en/19026151)" manual
Describes the hardware of the S7-300 fail-safe signal modules (including
installation, wiring, and technical specifications)
"Distributed I/O system ET 200pro, fail-
safe I/O modules
(http://support.automation.siemens.com/W
W/view/en/22098524)" operating instruc-
tions
Describes the hardware of the ET 200pro fail-safe modules (including installa-
tion, wiring, and technical specifications)
"ET 200iSP distributed I/O device - Fail-
safe modules
(http://support.automation.siemens.com/W
W/view/en/47357221)" operating instruc-
tions
Describes the hardware of the ET 200iSP fail-safe modules (including installa-
tion, wiring, and technical specifications)
Help on
STEP 7
Describes the operation of the standard tools in
STEP 7
Contains information regarding configuration and parameter assignment of
hardware
Contains a description of the FBD and LAD programming languages
The complete
SIMATIC S7
documentation is available on DVD. You can find more
information on the Internet (http://www.automation.siemens.com/mcms/industrial-
automation-systems-simatic/en/manual-overview/manual-collection/Pages/Default.aspx).
Important notes
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 7
Guide
This documentation describes how to work with the optional packages
STEP 7 Safety.
It
includes instructions and reference sections (description of the instructions for the safety
program).
The following topics are addressed:
Configuration of SIMATIC Safety
Access protection for SIMATIC Safety
Programming of the safety program (safety-related user program)
Safety-related communication
Instructions for the safety program
Support for the system acceptance
Operation and maintenance of SIMATIC Safety
Monitoring and response times
Conventions
In this documentation, the terms "safety engineering" and "fail-safe engineering" are used
synonymously. The same applies to the terms "fail-safe" and "F-".
When
"STEP 7 Safety Advanced V15.1", "STEP 7 Safety Basic V15.1"
appears in italics, it
refers to the optional package for the "SIMATIC Safety" F-system.
"STEP 7 Safety V15.1"
stands for the optional package
"STEP 7 Safety Advanced V15.1"
and the optional package
"STEP 7 Safety Basic V15"
.
"(S7-300)" indicates that the section
only
applies to S7-300 F-CPUs. S7-300 F-CPUs also
includes the F-CPUs ET 200S and ET 200pro (IM F-CPUs).
"(S7-400)" indicates that the section
only
applies to S7-400 as well as WinAC RTX F.
"(S7-1200)" indicates that the section
only
applies to S7-1200 F-CPUs.
"(S7-1500)" indicates that the section
only
applies to S7-1500 F-CPUs. S7-1500 F-CPUs
also includes ET 200SP F-CPUs, the CPU 1516pro F-2 PN and the S7-1500 F Software
Controller.
The scopes can be combined.
The term "Safety program" refers to the fail-safe portion of the user program and is used
instead of "fail-safe user program," "F-program," etc. For purposes of contrast, the non-
safety-related part of the user program is referred to as the "standard user program".
All fail-safe modules and instructions are highlighted in yellow to distinguish them from the
modules and instructions of the standard user programs on the software interface (e.g., in
the project tree). Similarly, the fail-safe parameters of F-CPUs and F-I/O are highlighted in
yellow in the hardware configuration.
Each warning is marked with a unique number at the end of the text. This enables you to
easily reference other documents, for example, to obtain an overview of the safety
requirements for the system.
Important notes
SIMATIC Safety - Configuring and Programming
8 Programming and Operating Manual, 10/2018, A5E02714440-AH
Additional support
If you have further questions about the use of products presented in this manual, contact
your local Siemens representative.
You can find information on whom to contact on the Web
(http://www.siemens.com/automation/partner).
A guide to the technical documentation for the various SIMATIC products and systems is
available on the Web (http://www.siemens.com/simatic-tech-doku-portal).
You can find the online catalog and online ordering system on the Web
(www.siemens.com/industrymall).
Training center
We offer courses to help you get started with the S7 automation system. Contact your
regional training center or the central training center in Nuremberg (90327), Federal Republic
of Germany.
You can find more information on the Internet (http://www.sitrain.com).
Technical Support
To contact Technical Support for all Industry Automation products, use the Support Request
Web form (http://www.siemens.com/automation/support-request).
You can find additional information about our Technical Support on the Web
(http://www.siemens.com/automation/service).
Important notes
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 9
Important note for maintaining the operational safety of your system
Note
The operators of systems with safety
-related characteristics must adhere to operational
safety requirements. The supplier is also obliged to comply with special product monitoring
measures. Siemens informs system oper
ators in the form of personal notifications about
product developments and properties which may be or become important issues in terms of
operational safety.
You should subscribe to the corresponding notifications in order to obtain the latest
information
and to allow you to make any necessary modifications to your system.
Log in in the Industry Online Support. Follow the links below and click on "Email on update"
on the right
-hand side in each case:
SIMATIC S7-300/S7-300F
(https://support.industry.siemens.com/cs/products?pnid=13751&lc=en-WW)
SIMATIC S7-400/S7-400H/S7-400F/FH
(https://support.industry.siemens.com/cs/products?pnid=13828&lc=en-WW)
SIMATIC S7-1500/SIMATIC S7-1500F
(https://support.industry.siemens.com/cs/products?pnid=13716&lc=en-WW)
SIMATIC S7-1200/SIMATIC S7-1200F
(https://support.industry.siemens.com/cs/products?pnid=13683&lc=en-WW)
Software Controller
(https://support.industry.siemens.com/cs/products?pnid=13911&lc=en-WW)
Distributed I/O (https://support.industry.siemens.com/cs/products?pnid=14029&lc=en-
WW)
STEP 7 (TIA Portal)
(https://support.industry.siemens.com/cs/products?pnid=14340&lc=en-WW)
Important notes
SIMATIC Safety - Configuring and Programming
10 Programming and Operating Manual, 10/2018, A5E02714440-AH
Security information
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is
necessary to implement and continuously maintain a holistic, state-of-the-art industrial
security concept. Siemens' products and solutions constitute one element of such a concept.
Customers are responsible for preventing unauthorized access to their plants, systems,
machines and networks. Such systems, machines and components should only be
connected to an enterprise network or the internet if and to the extent such a connection is
necessary and only when appropriate security measures (e.g. firewalls and/or network
segmentation) are in place.
For additional information on industrial security measures that may be implemented, please
visit (https://www.siemens.com/industrialsecurity).
Siemens' products and solutions undergo continuous development to make them more
secure. Siemens strongly recommends that product updates are applied as soon as they are
available and that the latest product versions are used. Use of product versions that are no
longer supported, and failure to apply the latest updates may increase customers' exposure
to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS
Feed under (https://www.siemens.com/industrialsecurity).
Siemens Industry Online Support
You can find current information on the following topics quickly and easily here:
Product support
All the information and extensive know-how on your product, technical specifications,
FAQs, certificates, downloads, and manuals.
Application examples
Tools and examples to solve your automation tasks as well as function blocks,
performance information and videos.
Services
Information about Industry Services, Field Services, Technical Support, spare parts and
training offers.
Forums
For answers and solutions concerning automation technology.
mySupport
Your personal working area in Industry Online Support for messages, support queries,
and configurable documents.
This information is provided by the Siemens Industry Online Support in the Internet
(http://www.siemens.com/automation/service&support).
Important notes
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 11
Industry Mall
The Industry Mall is the catalog and order system of Siemens AG for automation and drive
solutions on the basis of Totally Integrated Automation (TIA) and Totally Integrated Power
(TIP).
Catalogs for all the products in automation and drives are available on the Internet
(https://mall.industry.siemens.com).
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 13
Table of contents
Important notes ....................................................................................................................................... 3
1 Product Overview .................................................................................................................................. 23
1.1 Overview ................................................................................................................................. 23
1.2 Hardware and Software Components ..................................................................................... 25
1.3 Installing/uninstalling STEP 7 Safety Basic V15.1 optional package ..................................... 30
1.4 Installing/uninstalling STEP 7 Safety Advanced V15.1 optional package .............................. 31
1.5 Installing/uninstalling STEP 7 Safety PowerPack ................................................................... 32
1.6 Migrating projects from S7 Distributed Safety V5.4 SP5 to STEP 7 Safety Advanced .......... 32
1.7 Migrating PLC programs to a n F-CPU S7-1500 .................................................................... 36
1.8 Upgrading projects to STEP 7 Safety V15.1........................................................................... 37
1.8.1 Upgrading projects from STEP 7 Safety V15 to V15.1 ........................................................... 37
1.8.2 Upgrading projects from STEP 7 Safety V14 SP1 to V15.1 ................................................... 37
1.8.3 Upgrading projects from STEP 7 Safety V13 SP1 to V15.1 ................................................... 38
1.8.4 Upgrading projects from STEP 7 Safety prior to V13 SP1 ..................................................... 39
1.9 First steps ............................................................................................................................... 42
2 Configuring ........................................................................................................................................... 43
2.1 Overview of Configuration ...................................................................................................... 43
2.2 Particularities for configuring the F-System ............................................................................ 46
2.3 Configuring an F-CPU............................................................................................................. 48
2.4 Configuring F-I/O .................................................................................................................... 53
2.5 Configuration control (option handling) for F-I/Os .................................................................. 58
2.5.1 Example .................................................................................................................................. 59
2.6 Configuring shared device ...................................................................................................... 63
2.7 Configuring isochronous mode (S7-1500) .............................................................................. 63
2.8 Recommendation for PROFIsafe address assignment .......................................................... 65
2.9 Configurations supported by the SIMATIC Safety F-system .................................................. 66
2.10 PROFIsafe addresses for F-I/O of PROFIsafe address type 1 .............................................. 68
2.11 PROFIsafe addresses for F-I/O of PROFIsafe address type 2 .............................................. 70
2.12 Setting the F-destination address for F-I/O with DIP switches ............................................... 72
2.13 Assigning a PROFIsafe address of the F-I/Os with SIMATIC Safety ..................................... 72
2.13.1 Identifying F-modules.............................................................................................................. 73
2.13.2 Assign PROFIsafe address .................................................................................................... 75
2.13.3 Assign PROFIsafe address to an F-module ........................................................................... 75
2.13.4 Changing the PROFIsafe address .......................................................................................... 76
Table of contents
SIMATIC Safety - Configuring and Programming
14 Programming and Operating Manual, 10/2018, A5E02714440-AH
2.14 Peculiarities when configuring fail-safe GSD based DP slaves and fail-safe GSD
based I/O devices .................................................................................................................. 77
3 Safety Administration Editor .................................................................................................................. 81
3.1 Opening the Safety Administration Editor .............................................................................. 83
3.2 "General" area ........................................................................................................................ 83
3.3 "F-runtime group" area ........................................................................................................... 86
3.3.1 "F-runtime group" area ........................................................................................................... 86
3.3.2 Pre-/postprocessing (S7-1200, S7-1500) .............................................................................. 87
3.4 "F-blocks" area ....................................................................................................................... 88
3.5 "F-compliant PLC data types" area (S7-1200, S7-1500) ....................................................... 89
3.6 “Web server F-Admins” area (S7-1200, S7-1500) ................................................................. 90
3.7 "Settings" area ....................................................................................................................... 90
3.8 "Flexible F-Link" area (S7-1200, S7-1500) ............................................................................ 96
4 Access protection................................................................................................................................. 101
4.1 Overview of access protection ............................................................................................. 101
4.2 Access protection for the safety program ............................................................................ 103
4.3 Access protection for the F-CPU ......................................................................................... 106
4.4 Access protection through organizational measures ........................................................... 109
5 Programming ....................................................................................................................................... 111
5.1 Overview of Programming ................................................................................................... 111
5.1.1 Program structure of the safety program (S7-300, S7-400) ................................................ 111
5.1.2 Program structure of the safety program (S7-1200, S7-1500) ............................................ 114
5.1.3 Fail-Safe Blocks ................................................................................................................... 117
5.1.4 Restrictions in the programming languages FBD/LAD ........................................................ 119
5.1.5 F-compliant PLC data types (UDT) (S7-1200, S7-1500) ..................................................... 126
5.1.5.1 Grouping PLC tags for inputs and outputs of F-I/O in structures (S7-1200, S7-1500) ........ 127
5.1.5.2 Example of structured PLC tags for inputs and outputs of F-I/O (S7-1200, S7-1500) ........ 128
5.1.6 Editing PLC tags with external editors ................................................................................. 131
5.1.7 Using Multiuser engineering ................................................................................................ 131
5.2 Defining F-Runtime Groups ................................................................................................. 132
5.2.1 Rules for F-Runtime Groups of the Safety Program ............................................................ 132
5.2.2 Procedure for defining an F-runtime group (S7-300, S7-400) ............................................. 134
5.2.3 Procedure for defining an F-runtime group (S7-1200, S7-1500) ......................................... 137
5.2.4 F-runtime group communication (S7-300, S7-400) ............................................................. 141
5.2.5 F-runtime group communication (S7-1200, S7-1500) ......................................................... 145
5.2.6 F-shared DB (S7-300, S7-400) ............................................................................................ 148
5.2.7 F-runtime group information DB (S7-1200, S7-1500) .......................................................... 148
5.2.8 Deleting an F-runtime group ................................................................................................ 150
5.2.9 Changing the F-runtime group (S7-300, S7-400) ................................................................ 150
5.2.10 Changing the F-runtime group (S7-1200, S7-1500) ............................................................ 151
Table of contents
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 15
5.3 Creating F-blocks in FBD / LAD ............................................................................................ 151
5.3.1 Creating F-blocks .................................................................................................................. 151
5.3.2 Know-how protection ............................................................................................................ 153
5.3.3 Reuse of F-blocks ................................................................................................................. 154
5.4 Programming startup protection ........................................................................................... 155
6 F-I/O access ....................................................................................................................................... 157
6.1 Addressing F-I/O ................................................................................................................... 157
6.2 Value status (S7-1200, S7-1500) ......................................................................................... 159
6.3 Process Data or Fail-Safe Values ......................................................................................... 162
6.4 F-I/O DB ................................................................................................................................ 165
6.4.1 Tags of the F-I/O DB ............................................................................................................. 166
6.4.1.1 PASS_ON ............................................................................................................................. 167
6.4.1.2 ACK_NEC ............................................................................................................................. 168
6.4.1.3 ACK_REI ............................................................................................................................... 168
6.4.1.4 IPAR_EN ............................................................................................................................... 169
6.4.1.5 DISABLE ............................................................................................................................... 170
6.4.1.6 QBAD/PASS_OUT/DISABLED/QBAD_I_xx/QBAD_O_xx and value status ......................... 171
6.4.1.7 ACK_REQ ............................................................................................................................. 172
6.4.1.8 IPAR_OK ............................................................................................................................... 172
6.4.1.9 DIAG ..................................................................................................................................... 172
6.4.2 Accessing tags of the F-I/O DB ............................................................................................ 174
6.5 Passivation and reintegration of F-I/O .................................................................................. 175
6.5.1 After startup of F-system....................................................................................................... 175
6.5.2 After communication errors ................................................................................................... 178
6.5.3 After F-I/O or channel faults .................................................................................................. 180
6.5.4 Group passivation ................................................................................................................. 184
7 Implementation of user acknowledgment ............................................................................................. 187
7.1 Implementing User Acknowledgment in the Safety Program of the F-CPU of a DP
Master or IO controller .......................................................................................................... 187
7.2 Implementing user acknowledgment in the safety program of the F-CPU of a I-slave or
I-device ................................................................................................................................. 192
8 Data exchange between standard user program and safety program .................................................. 195
8.1 Data Transfer from the Safety Program to the Standard User Program .............................. 196
8.2 Data Transfer from Standard User Program to Safety Program .......................................... 197
9 Safety-related communication ............................................................................................................. 201
9.1 Configuring and programming communication (S7-300, S7-400) ........................................ 201
9.1.1 Overview of communication .................................................................................................. 201
9.1.2 Safety-related IO controller-IO controller communication ..................................................... 204
9.1.2.1 Configure safety-related IO controller-IO controller communication .................................... 204
9.1.2.2 Safety-related IO controller-IO controller communication via SENDDP and RCVDP .......... 208
9.1.2.3 Program safety-related IO controller-IO controller communication ...................................... 209
9.1.2.4 Safety-related IO controller-IO controller communication - Limits for data transfer ............. 213
Table of contents
SIMATIC Safety - Configuring and Programming
16 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.1.3 Safety-related master-master communication ..................................................................... 213
9.1.3.1 Configure safety-related master-master communication ..................................................... 213
9.1.3.2 Safety-related master-master communication via SENDDP and RCVDP........................... 218
9.1.3.3 Program safety-related master-master communication ....................................................... 218
9.1.3.4 Safety-related master-master communication:Limits for data transfer ................................ 223
9.1.4 Safety-related IO controller-I-device communication ........................................................... 223
9.1.4.1 Configuring safety-related communication between IO controller and I-device .................. 223
9.1.4.2 Safety-related IO controller-I-device communication via SENDDP and RCVDP ................ 226
9.1.4.3 Programming safety-related IO controller I-device communication ..................................... 227
9.1.4.4 Safety-related IO-Controller-IO-Device communication - Limits for data transfer ............... 229
9.1.5 Safety-related master-I-slave communication ..................................................................... 229
9.1.5.1 Configuring safety-related master-I-slave communication .................................................. 229
9.1.5.2 Safety-related master-I-slave or I-slave-I-slave communication via SENDDP and
RCVDP ................................................................................................................................. 232
9.1.5.3 Program the safety-related master-I-slave or I-slave-I-slave communication ..................... 233
9.1.5.4 Limits for data transfer of safety-related master-I-slave or I-slave-I-slave
communication ..................................................................................................................... 235
9.1.6 Safety-related I-slave-I-slave communication ...................................................................... 236
9.1.6.1 Configure safety-related I-slave-I-slave communication ...................................................... 236
9.1.6.2 Safety-related I-slave-I-slave communication via SENDDP and RCVDP ........................... 240
9.1.6.3 Programming safety-related I-slave-I-slave communication ................................................ 240
9.1.6.4 Limits for data transfer of safety-related I-slave-I-slave communication ............................. 240
9.1.7 Safety-Related I-Slave-Slave Communication ..................................................................... 241
9.1.7.1 Configuring Safety-Related I-Slave-Slave Communication ................................................. 241
9.1.7.2 Safety-Related I-Slave-Slave Communication - F-I/O Access ............................................ 246
9.1.7.3 Limits for data transfer of safety-related I-slave-I-slave communication ............................. 246
9.1.8 Safety-related IO controller-I-slave communication ............................................................. 247
9.1.9 Safety-related communication via S7 connections .............................................................. 248
9.1.9.1 Configuring safety-related communication via S7 connections ........................................... 248
9.1.9.2 Communication via SENDS7, RCVS7, and F-Communication DB ..................................... 250
9.1.9.3 Programming safety-related communication via S7 connections ........................................ 251
9.1.9.4 Safety-related communication via S7 connections - Limits of data transfer ........................ 255
9.1.10 Safety-related communication with other S7 F-systems ..................................................... 255
9.1.10.1 Introduction .......................................................................................................................... 255
9.1.10.2 Communication with S7 Distributed Safety via PN/PN coupler (IO controller-IO
controller communication) .................................................................................................... 256
9.1.10.3 Communication with S7 Distributed Safety via DP/DP coupler (master-master
communication) .................................................................................................................... 257
9.1.10.4 Communication with S7 Distributed Safety via S7 connections .......................................... 258
9.1.10.5 Communication with S7 F/FH Systems via S7 connections ................................................ 260
9.2 Configuring and programming communication with Flexible F-Link (S7-1200, S7-1500) ... 262
9.2.1 Flexible F-Link ...................................................................................................................... 262
9.2.2 Example of a safety-related communication between two F-CPUs ..................................... 266
9.3 Configuring and programming communication (S7-1200, S7-1500) ................................... 270
9.3.1 Overview of communication ................................................................................................. 270
9.3.2 Safety-related IO controller-IO controller communication .................................................... 272
9.3.2.1 Configure safety-related IO controller-IO controller communication .................................... 272
9.3.2.2 Safety-related IO controller-IO controller communication via SENDDP and RCVDP ......... 276
9.3.2.3 Program safety-related IO controller-IO controller communication ..................................... 277
9.3.2.4 Safety-related IO controller-IO controller communication - Limits for data transfer ............ 281
Table of contents
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 17
9.3.3 Safety-related master-master communication ...................................................................... 281
9.3.3.1 Configure safety-related master-master communication ...................................................... 281
9.3.3.2 Safety-related master-master communication via SENDDP and RCVDP ........................... 285
9.3.3.3 Program safety-related master-master communication ........................................................ 286
9.3.3.4 Safety-related master-master communication:Limits for data transfer ................................. 290
9.3.4 Safety-related IO controller-I-device communication ............................................................ 290
9.3.4.1 Configuring safety-related communication between IO controller and I-device ................... 290
9.3.4.2 Safety-related IO controller-I-device communication via SENDDP and RCVDP ................. 293
9.3.4.3 Programming safety-related IO controller I-device communication ...................................... 294
9.3.4.4 Safety-related IO-Controller-IO-Device communication - Limits for data transfer ................ 296
9.3.5 Safety-related master-I-slave communication ...................................................................... 297
9.3.5.1 Configuring safety-related master-I-slave communication ................................................... 297
9.3.5.2 Safety-related master-I-slave communication via SENDDP and RCVDP ............................ 299
9.3.5.3 Programming safety-related master-I-slave communication ................................................ 300
9.3.5.4 Limits for data transfer of safety-related master-I-slave communication .............................. 303
9.3.6 Safety-related IO controller-I-slave communication .............................................................. 304
9.3.6.1 Safety-related IO controller-I-slave communication .............................................................. 304
9.3.7 Safety-related communication to S7 F-System S7 Distributed Safety ................................. 304
9.3.7.1 Introduction ........................................................................................................................... 304
9.3.7.2 Communication with S7 Distributed Safety via PN/PN coupler (IO controller-IO
controller communication) ..................................................................................................... 305
9.3.7.3 Communication with S7 Distributed Safety via DP/DP coupler (master-master
communication) ..................................................................................................................... 306
9.4 Configuring and programming communication between S7-300/400 and S7-1200/1500
F-CPUs ................................................................................................................................. 307
9.4.1 Overview of communication .................................................................................................. 307
9.5 Configuring and programming communication in several projects ....................................... 308
9.5.1 Safety-oriented IO Controller I device communication in several projects ........................... 308
9.5.1.1 Configuring safety-related communication between IO controller and I-device ................... 308
9.5.1.2 Programming safety-related IO Controller I-device communication ..................................... 309
10 Compiling and commissioning a safety program .................................................................................. 311
10.1 Compiling the safety program ............................................................................................... 311
10.2 Safety program work memory requirements (S7-300, S7-400) ............................................ 312
10.3 Downloading project data ..................................................................................................... 313
10.3.1 Downloading project data to an F-CPU ................................................................................ 313
10.3.1.1 Downloading project data to an S7-300/400 F-CPU with memory card inserted
(SIMATIC Micro memory card or flash card) ........................................................................ 317
10.3.1.2 Downloading project data to an S7-400 F-CPU without flash card inserted ........................ 317
10.3.1.3 Downloading project data to a WinAC RTX F ...................................................................... 318
10.3.1.4 Downloading individual F-blocks to an S7-300/400 F-CPU.................................................. 318
10.3.1.5 Downloading project data to an S7-1200 F-CPU without program card inserted ................ 319
10.3.1.6 Downloading project data to an S7-1200 F-CPU with program card inserted...................... 320
10.3.1.7 Downloading project data to an S7-1500 F-CPU ................................................................. 321
10.3.1.8 Downloading project data to an S7-1500 F Software Controller .......................................... 322
10.3.2 Downloading project data to a memory card and inserting a memory card ......................... 323
10.3.2.1 Inserting a SIMATIC Micro Memory Card or flash card into an S7-300/400 F-CPU ............ 324
10.3.2.2 Inserting a transfer card into an S7-1200 F-CPU ................................................................. 325
Table of contents
SIMATIC Safety - Configuring and Programming
18 Programming and Operating Manual, 10/2018, A5E02714440-AH
10.3.3 Downloading project data of an S7-1200 F-CPU from the internal load memory to an
empty SIMATIC Memory Card ............................................................................................. 327
10.3.4 Updating project data on an S7-1200 F-CPU using a transfer card .................................... 328
10.3.5 Restoring a backup of the safety program to an S7-300/1200/1500 F-CPU ....................... 328
10.3.6 Special features when creating and importing images of an S7-1500 F Software
Controller .............................................................................................................................. 329
10.3.7 Loading project data from an F-CPU to a programming device / PC .................................. 331
10.3.8 Loading PC station via the configuration file ........................................................................ 332
10.3.8.1 Creating a configuration file ................................................................................................. 333
10.3.8.2 Importing the configuration file ............................................................................................. 333
10.4 Program identification .......................................................................................................... 337
10.5 Comparing Safety Programs ................................................................................................ 339
10.6 Printing project data ............................................................................................................. 341
10.7 Testing the safety program .................................................................................................. 343
10.7.1 Overview of Testing the Safety Program ............................................................................. 343
10.7.2 Disabling safety mode .......................................................................................................... 344
10.7.3 Testing the safety program .................................................................................................. 347
10.7.4 Testing the safety program with S7-PLCSIM ....................................................................... 350
10.7.5 Changing the safety program in RUN mode (S7-300, S7-400) ........................................... 355
10.7.6 Changing the standard user program in RUN mode (S7-1200, S7-1500) .......................... 357
10.7.7 Deleting the safety program ................................................................................................. 357
10.8 F-change history .................................................................................................................. 359
11 System acceptance .............................................................................................................................. 361
11.1 Overview of System Acceptance ......................................................................................... 361
11.2 Correctness of the safety program including hardware configuration (including testing) .... 363
11.3 Completeness of the safety summary ................................................................................. 364
11.4 Compliance of the system library elements used in the safety program with Annex 1 of
the Report for the TÜV certificate ........................................................................................ 365
11.5 Compliance of the know-how protected F-blocks used in the safety program with their
safety documentation. .......................................................................................................... 366
11.6 Completeness and correctness of the hardware configuration ........................................... 368
11.7 Correctness and completeness of the communication configuration .................................. 374
11.8 Identity of online and offline program ................................................................................... 375
11.9 Other characteristics ............................................................................................................ 376
11.10 Acceptance of Changes ....................................................................................................... 378
12 Operation and Maintenance ................................................................................................................. 383
12.1 Notes on Safety Mode of the Safety Program ..................................................................... 383
12.2 Replacing Software and Hardware Components ................................................................. 386
12.3 Guide to diagnostics (S7-300, S7-400) ................................................................................ 389
12.4 Guide to diagnostics (S7-1500) ........................................................................................... 390
12.5 Guide to diagnostics (S7-1200) ........................................................................................... 390
Table of contents
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 19
13 Overview of instructions for the safety program .................................................................................. 363
13.1 General ................................................................................................................................. 392
13.1.1 LAD ....................................................................................................................................... 392
13.1.1.1 New network (STEP 7 Safety V15.1) .................................................................................... 392
13.1.1.2 Empty box (STEP 7 Safety V15.1) ....................................................................................... 393
13.1.1.3 Open branch (STEP 7 Safety V15.1).................................................................................... 393
13.1.1.4 Close branching (STEP 7 Safety V15.1) .............................................................................. 395
13.1.2 FBD ....................................................................................................................................... 396
13.1.2.1 New network (STEP 7 Safety V15.1) .................................................................................... 396
13.1.2.2 Empty box (STEP 7 Safety V15.1) ....................................................................................... 396
13.1.2.3 Open branch (STEP 7 Safety V15.1).................................................................................... 397
13.1.2.4 Insert binary input (STEP 7 Safety V15.1) ............................................................................ 398
13.1.2.5 Invert RLO (STEP 7 Safety V15.1) ....................................................................................... 399
13.2 Bit logic operations ................................................................................................................ 400
13.2.1 LAD ....................................................................................................................................... 400
13.2.1.1 ---| |---: NO contact (STEP 7 Safety V15.1) .......................................................................... 400
13.2.1.2 ---| / |---: NC contact (STEP 7 Safety V15.1) ........................................................................ 401
13.2.1.3 --|NOT|--: Invert RLO (STEP 7 Safety V15.1) ....................................................................... 402
13.2.1.4 ---( )---: Assignment (STEP 7 Safety V15.1) ......................................................................... 402
13.2.1.5 ---( R )---: Reset output (STEP 7 Safety V15.1) .................................................................... 403
13.2.1.6 ---( S )---: Set output (STEP 7 Safety V15.1) ........................................................................ 404
13.2.1.7 SR: Set/reset flip-flop (STEP 7 Safety V15.1) ...................................................................... 406
13.2.1.8 RS: Reset/set flip-flop (STEP 7 Safety V15.1) ..................................................................... 407
13.2.1.9 --|P|--: Scan operand for positive signal edge (STEP 7 Safety V15.1) ................................. 409
13.2.1.10 --|N|--: Scan operand for negative signal edge (STEP 7 Safety V15.1) ............................... 410
13.2.1.11 P_TRIG: Scan RLO for positive signal edge (STEP 7 Safety V15.1) ................................... 412
13.2.1.12 N_TRIG: Scan RLO for negative signal edge (STEP 7 Safety V15.1) ................................. 413
13.2.2 FBD ....................................................................................................................................... 414
13.2.2.1 AND logic operation (STEP 7 Safety V15.1) ........................................................................ 414
13.2.2.2 OR logic operation (STEP 7 Safety V15.1)........................................................................... 416
13.2.2.3 X: EXCLUSIVE OR logic operation (STEP 7 Safety V15.1) ................................................. 417
13.2.2.4 =: Assignment (STEP 7 Safety V15.1) ................................................................................. 419
13.2.2.5 R: Reset output (STEP 7 Safety V15.1) ............................................................................... 420
13.2.2.6 S: Set output (STEP 7 Safety V15.1).................................................................................... 421
13.2.2.7 SR: Set/reset flip-flop (STEP 7 Safety V15.1) ...................................................................... 422
13.2.2.8 RS: Reset/set flip-flop (STEP 7 Safety V15.1) ..................................................................... 423
13.2.2.9 P: Scan operand for positive signal edge (STEP 7 Safety V15.1) ....................................... 425
13.2.2.10 N: Scan operand for negative signal edge (STEP 7 Safety V15.1) ...................................... 426
13.2.2.11 P_TRIG: Scan RLO for positive signal edge (STEP 7 Safety V15.1) ................................... 427
13.2.2.12 N_TRIG: Scan RLO for negative signal edge (STEP 7 Safety V15.1) ................................. 429
13.3 Safety functions .................................................................................................................... 430
13.3.1 ESTOP1: Emergency STOP/OFF up to stop category 1 (STEP 7 Safety V15.1) ................ 430
13.3.2 TWO_HAND: Two-hand monitoring (STEP 7 Safety Advanced V15.1) (S7-300, S7-
400) ....................................................................................................................................... 436
Table of contents
SIMATIC Safety - Configuring and Programming
20 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.3.3 TWO_H_EN: Two-hand monitoring with enable (STEP 7 Safety V15.1)............................. 439
13.3.4 MUTING: Muting (STEP 7 Safety Advanced V15.1) (S7-300, S7-400) ............................... 445
13.3.5 MUT_P: Parallel muting (STEP 7 Safety V15.1) .................................................................. 456
13.3.6 EV1oo2DI: 1oo2 evaluation with discrepancy analysis (STEP 7 Safety V15.1) .................. 468
13.3.7 FDBACK: Feedback monitoring (STEP 7 Safety V15.1) ..................................................... 475
13.3.8 SFDOOR: Safety door monitoring (STEP 7 Safety V15.1) .................................................. 481
13.3.9 ACK_GL: Global acknowledgment of all F-I/O in an F-runtime group (STEP 7 Safety
V15.1) ................................................................................................................................... 487
13.4 Timer operations .................................................................................................................. 489
13.4.1 TP: Generate pulse (STEP 7 Safety V15.1) ........................................................................ 489
13.4.2 TON: Generate on-delay (STEP 7 Safety V15.1) ................................................................ 494
13.4.3 TOF: Generate off-delay (STEP 7 Safety V15.1) ................................................................ 499
13.5 Counter operations .............................................................................................................. 504
13.5.1 CTU: Count up (STEP 7 Safety V15.1) ............................................................................... 504
13.5.2 CTD: Count down (STEP 7 Safety V15.1) ........................................................................... 506
13.5.3 CTUD: Count up and down (STEP 7 Safety V15.1) ............................................................ 508
13.6 Comparator operations ........................................................................................................ 511
13.6.1 CMP ==: Equal (STEP 7 Safety V15.1) ............................................................................... 511
13.6.2 CMP <>: Not equal (STEP 7 Safety V15.1) ......................................................................... 512
13.6.3 CMP >=: Greater or equal (STEP 7 Safety V15.1) .............................................................. 514
13.6.4 CMP <=: Less or equal (STEP 7 Safety V15.1) ................................................................... 515
13.6.5 CMP >: Greater than (STEP 7 Safety V15.1) ...................................................................... 517
13.6.6 CMP <: Less than (STEP 7 Safety V15.1) ........................................................................... 518
13.7 Math functions ...................................................................................................................... 520
13.7.1 ADD: Add (STEP 7 Safety V15.1)........................................................................................ 520
13.7.2 SUB: Subtract (STEP 7 Safety V15.1) ................................................................................. 523
13.7.3 MUL: Multiply (STEP 7 Safety V15.1) .................................................................................. 526
13.7.4 DIV: Divide (STEP 7 Safety V15.1)...................................................................................... 529
13.7.5 NEG: Create twos complement (STEP 7 Safety V15.1) ...................................................... 533
13.7.6 ABS: Form absolute value (STEP 7 Safety V15.1) (S7-1200, S7-1500) ............................. 536
13.8 Move operations................................................................................................................... 538
13.8.1 MOVE: Move value (STEP 7 Safety V15.1) ........................................................................ 538
13.8.2 RD_ARRAY_I: Read value from INT F-array (STEP 7 Safety V15.1) (S7-1500) ................ 539
13.8.3 RD_ARRAY_DI: Read value from DINT F-array (STEP 7 Safety V15.1) (S7-1500) ........... 542
13.8.4 WR_FDB: Write value indirectly to an F-DB (STEP 7 Safety V15.1) (S7-300, S7-400) ...... 544
13.8.5 RD_FDB: Read value indirectly from an F-DB (STEP 7 Safety Advanced V15.1) (S7-
300, S7-400) ........................................................................................................................ 546
13.9 Conversion operations ......................................................................................................... 548
13.9.1 CONVERT: Convert value (STEP 7 Safety V15.1) .............................................................. 548
13.9.2 BO_W: Convert 16 data elements of data type BOOL to a data element of data type
WORD (STEP 7 Safety V15.1) ............................................................................................ 550
13.9.3 W_BO: Convert a data element of data type WORD to 16 data elements of data type
BOOL (STEP 7 Safety V15.1) .............................................................................................. 552
13.9.4 SCALE: Scale values (STEP 7 Safety Advanced V15.1) .................................................... 555
Table of contents
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 21
13.10 Program control operations .................................................................................................. 558
13.10.1 JMP: Jump if RLO = 1 (STEP 7 Safety V15.1) ..................................................................... 558
13.10.2 JMPN: Jump if RLO = 0 (STEP 7 Safety V15.1) .................................................................. 560
13.10.3 LABEL: Jump label (STEP 7 Safety V15.1) .......................................................................... 562
13.10.4 RET: Return (STEP 7 Safety V15.1) .................................................................................... 564
13.10.5 OPN: Open global data block (STEP 7 Safety Advanced V15.1) (S7-300, S7-400) ............ 565
13.11 Word logic operations ........................................................................................................... 567
13.11.1 AND: AND logic operation (STEP 7 Safety V15.1) ............................................................... 567
13.11.2 OR: OR logic operation (STEP 7 Safety V15.1) ................................................................... 568
13.11.3 XOR: EXCLUSIVE OR logic operation (STEP 7 Safety V15.1) ........................................... 570
13.12 Shift and rotate ...................................................................................................................... 571
13.12.1 SHR: Shift right (STEP 7 Safety V15.1) ................................................................................ 571
13.12.2 SHL: Shift left (STEP 7 Safety V15.1) .................................................................................. 574
13.13 Operating .............................................................................................................................. 577
13.13.1 ACK_OP: Fail-safe acknowledgment (STEP 7 Safety V15.1) .............................................. 577
13.14 Additional instructions ........................................................................................................... 585
13.14.1 LAD ....................................................................................................................................... 585
13.14.1.1 ---| |--- OV: Get status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-400) ............. 585
13.14.1.2 ---| / |--- OV: Get negated status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-
400) ....................................................................................................................................... 586
13.14.2 FBD ....................................................................................................................................... 587
13.14.2.1 OV: Get status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-400) ........................ 587
13.15 Communication ..................................................................................................................... 588
13.15.1 PROFIBUS/PROFINET ........................................................................................................ 588
13.15.1.1 SENDDP and RCVDP: Send and receive data via PROFIBUS DP/PROFINET IO
(STEP 7 Safety V15.1).......................................................................................................... 588
13.15.2 S7 communication ................................................................................................................ 599
13.15.2.1 SENDS7 and RCVS7: Communication via S7 connections (STEP 7 Safety Advanced
V15.1) (S7-300, S7-400) ....................................................................................................... 599
A Monitoring and response times ........................................................................................................... 607
A.1 Configuring monitoring times ................................................................................................ 608
A.1.1 Minimum monitoring time for the F-runtime group cycle time............................................... 610
A.1.2 Minimum monitoring time for safety-related communication between F-CPU and F-I/O ..... 610
A.1.3 Minimum monitoring time of safety-related CPU-CPU communication ................................ 612
A.1.4 Monitoring Time for Safety-Related Communication between F-Runtime Groups .............. 612
A.2 Response Times of Safety Functions ................................................................................... 613
B Checklist ............................................................................................................................................. 617
Glossary ............................................................................................................................................. 623
Index................................................................................................................................................... 637
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 23
Product Overview
1
1.1
Overview
SIMATIC Safety fail-safe system
The SIMATIC Safety fail-safe system is available to implement safety concepts in the area of
machine and personnel protection (for example, for emergency STOP devices for machining
and processing equipment) and in the process industry (for example, for implementation of
protection functions for safety devices of instrumentation and controls and of burners).
WARNING
The SIMATIC Safety F-system is used to control processes and to force the system into a
safe state after shutdown.
SIMATIC Safety can only be used for controlling processes in which an immediate
shutdown does not pose a danger to persons or the environment.
When realizing safety applications including the creation of the safety-relevant project data
you have to take into consideration the standards, directives and guidelines relevant for
your application. In particular include standards in which the software creation process is
described (for example IEC 61508-3 or ISO 13849-1).
(S062)
Achievable safety requirements
SIMATIC Safety F-systems can satisfy the following safety requirements:
Safety integrity level SIL3 in accordance with IEC 61508:2010
Performance Level (PL) e and category 4 in accordance with ISO 13849-1:2015 or EN
ISO 13849-1:2015
Product Overview
1.1 Overview
SIMATIC Safety - Configuring and Programming
24 Programming and Operating Manual, 10/2018, A5E02714440-AH
Principles of safety functions in SIMATIC Safety
Functional safety is implemented principally through safety functions in the software. Safety
functions are executed by the SIMATIC Safety system in order to bring the system to a safe
state or maintain it in a safe state in case of a dangerous event. Safety functions are
contained mainly in the following components:
In the safety-related user program (safety program) in the F-CPU
In the fail-safe inputs and outputs (F-I/O)
The F-I/O ensure the safe processing of field information (sensors: e.g. emergency STOP
pushbutton, light barriers; actuators, e.g. for motor control). They have all of the required
hardware and software components for safe processing, in accordance with the required
Safety Integrity Level. The user only has to program the user safety function. The safety
function for the process can be provided through a user safety function or a fault reaction
function. In the event of an error, if the F-system can no longer execute its actual user safety
function, it executes the fault reaction function; for example, the associated outputs are shut
down, and the F-CPU switches to STOP mode, if necessary.
Example of user safety function and fault reaction function
In the event of overpressure, the F-system will open a valve (user safety function). In the
event of a hazardous fault in the F-CPU, all outputs are deactivated (fault reaction function),
whereby the valve is opened, and the other actuators also attain a safe state. For a non-
faulty F-system, only the valve would be opened.
Product Overview
1.2 Hardware and Software Components
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 25
1.2
Hardware and Software Components
Hardware and software components of SIMATIC Safety
The following figure provides an overview of the hardware and software components
required to configure and operate a SIMATIC Safety F-system.
Hardware components for PROFIBUS DP
You can use the following fail-safe components in SIMATIC Safety F-systems on
PROFIBUS DP:
F-CPUs with DP interface, such as CPU 1516F-3 PN/DP
Fail-safe inputs and outputs (F-I/O), such as:
S7-300 fail-safe signal modules in ET 200M
S7-1500/ET 200MP fail-safe modules
ET 200SP fail-safe modules
ET 200S fail-safe modules
ET 200pro fail-safe modules
ET 200iSP fail-safe modules
Fail-safe I/O modules ET 200eco (S7-300, S7-400)
Fail-safe GSD based DP slaves (light grid, laser scanner, etc.)
You have the option to expand the configuration with standard I/O.
Product Overview
1.2 Hardware and Software Components
SIMATIC Safety - Configuring and Programming
26 Programming and Operating Manual, 10/2018, A5E02714440-AH
The following CPs/CMs can be used in a SIMATIC Safety F-system on PROFIBUS DP for
connection to distributed F-I/O:
CP 443-5 Extended
CM 1243-5
CM 1542-5
CP 1542-5
SP CM DP
Hardware components for PROFINET IO
You can use the following fail-safe components in SIMATIC Safety F-systems on
PROFINET IO:
F-CPUs with PN interface, e.g., CPU 1214FC DC/DC/DC
Fail-safe inputs and outputs (F-I/O), such as:
S7-300 fail-safe signal modules in ET 200M
S7-1500/ET 200MP fail-safe modules
ET 200SP fail-safe modules
ET 200S fail-safe modules
ET 200pro fail-safe modules
ET 200eco PN fail-safe I/O modules
Fail-safe GSD based I/O devices (light grid, laser scanner, etc.)
You have the option to expand the configuration with standard I/O.
The following CPs/CMs can be used in a SIMATIC Safety F-system on PROFINET IO for
connection to distributed F-I/O:
CP 443-1
CP 443-1 Advanced-IT
CM 1542-1
CP 1545-1
Hardware components for central configuration
You can use the following fail-safe components in SIMATIC Safety F-systems centrally on an
F-CPU:
S7-300 fail-safe signal modules
S7-1200 fail-safe modules
S7-1500 fail-safe modules
ET 200SP fail-safe modules
ET 200S fail-safe modules
ET 200pro fail-safe modules (can also be used with CPU 1516proF-2)
You have the option to expand the configuration with standard I/O.
Product Overview
1.2 Hardware and Software Components
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 27
Required software components
You require the following software components:
SIMATIC STEP 7 Basic V15.1
with the
STEP 7 Safety Basic V15.1
optional package
or
SIMATIC STEP 7 Professional V15.1
with the
STEP 7 Safety Basic V15.1
optional
package
or
SIMATIC STEP 7 Professional V15.1
with the
STEP 7 Safety Advanced V15.1
optional
package
STEP 7 Safety
optional packages
This documentation describes the optional packages
STEP 7 Safety Advanced V15.1
and
STEP 7 Safety Basic V15.1
. The
STEP 7 Safety
optional packages are the configuration and
programming software for the SIMATIC Safety F-system. With
STEP 7 Safety
, you receive
the following:
Support for configuring the F-I/O in the
hardware and network editor
of the TIA Portal
Support for creating the safety program using LAD and FBD and integrating error
detection functions into the safety program
Instructions for programming your safety program in LAD and FBD, which you are familiar
with from the standard user programs
Instructions for programming your safety program in LAD and FBD with special safety
functions
Moreover,
STEP 7 Safety
offers functions for comparing safety programs and for assisting
you with the system acceptance.
WARNING
The configuration of F-CPUs and F-I/Os as well as the programming of F-blocks must be
carried out in the TIA Portal as described in this documentation.
You must observe all
aspects described in the section System acceptance (Page 361) to ensure secure
operation with the system SIMATIC SAFETY. Any other procedures are not permitted.
(S056)
Additional optional packages
In addition to the
STEP 7 Safety
optional packages, you can use additional optional
packages with F-I/O and F-CPUs and use instructions for programming your safety program
with special safety functions within the SIMATIC Safety F-system. For example, SINUMERIK
or Failsafe HMI Mobile Panels.
The installation, parameter assignment and programming as well as what is important to
note during system acceptance, is described in the documentation for the specific optional
packages.
Please also read the notes in Configurations supported by the SIMATIC Safety F-system
(Page 66).
Product Overview
1.2 Hardware and Software Components
SIMATIC Safety - Configuring and Programming
28 Programming and Operating Manual, 10/2018, A5E02714440-AH
TIA Portal Cloud Connector
WARNING
Use of the TIA Portal Cloud Connector is only intended for engineering work with the TIA
Portal. This means online access in productive operation (e.g. SCADA) is not permitted.
This is particularly true for safety programs.
(S068)
Openness
Openness as part of STEP 7 Safety is supported with the functions listed below.
Requirement for this is that no password is created for the safety-related project data to
prevent the use of Openness in productive operation.
As part of STEP 7 Safety the following is supported:
Inserting / removing F-CPUs and F-I/Os
Copying / deleting F-CPUs and F-I/Os from templates
Compiling software (incl. safety program)
Reading / configuring fail-safe parameters of the F-CPU
Reading / configuring fail-safe parameters of F-I/O devices
Reading / configuring fail-safe modules of ET 200SP
Reading, declaring or deleting fail-safe variables in the PLC variable table
Updating projects to the latest type versions of F-blocks
Consistent station upload
Export and import of F-blocks and F-compliant PLC data types (UDT)
Comparison of hardware and software
The following are not supported.
Downloading to device
Compiling hardware
Note
If access protection is set up for the safety program, actions that require access
authorization cannot be executed.
WARNING
When using Openness while handling safety-related project data their integrity must be
ensured (for example in the context of saving or transferring of applications for "Source
Code Management"). In case of a connection of external tools, observe the requirements
for offline support tools according to IEC 61508-3. A violation of the integrity of the safety-
related project data can not be determined during the import with STEP 7 Safety. A final
verification of the correctness of the safety-related project data has to be carried out as
described in the section System acceptance (Page 361).
(S070)
Product Overview
1.2 Hardware and Software Components
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 29
Virtual environments
WARNING
Use of virtual environments in the engineering system
Note that a HYPERVISOR or a client software of a HYPERVISOR is not permitted to
perform any function that reproduces recorded message frame sequences with correct time
behavior in the network with accessible systems.
Make sure that this condition is met, for example, when using the following functions:
Reset of captured statuses (snapshots) of the virtual machines (VMs)
Suspending and resuming the virtual machines
Replay of recorded sequences in the virtual machines
Moving VMs between hosts in productive operation (e.g. Fault Tolerance (FT))
Digital twins of VMs in the virtual environment
If in doubt, disable these functions in the settings (HYPERVISOR administration console).
(S067)
Safety program
You can create a safety program using the
program editor
. You can program fail-safe FBs
and FCs in the FBD or LAD programming languages using the instructions from the optional
package and create fail-safe DBs.
Safety checks are automatically performed and additional fail-safe blocks for error detection
and fault reaction are inserted when the safety program is compiled. This ensures that
failures and errors are detected and appropriate reactions are triggered to maintain the F-
system in the safe state or bring it to a safe state.
In addition to the safety program, a standard user program can be run on the F-CPU. A
standard program can coexist with a safety program in an F-CPU because the safety-related
data of the safety program are protected from being affected unintentionally by data of the
standard user program.
Data can be exchanged between the safety program and the standard user program in the
F-CPU by means of bit memory or data of a standard DB or by accessing the process image
input and output.
See also
Data Transfer from the Safety Program to the Standard User Program (Page 196)
Product Overview
1.3 Installing/uninstalling STEP 7 Safety Basic V15.1 optional package
SIMATIC Safety - Configuring and Programming
30 Programming and Operating Manual, 10/2018, A5E02714440-AH
1.3
Installing/uninstalling STEP 7 Safety Basic V15.1 optional package
Software requirements for
STEP 7 Safety Basic V15.1
At a minimum, one of the following software packages must be installed on the programming
device or PC:
SIMATIC STEP 7 Basic V15.1
SIMATIC STEP 7 Professional V15.1
Reviewing the Readme file
The readme file contains important up-to-date information about the software (for example,
Windows versions supported). You can display the readme file in the setup program or open
it later in the
SIMATIC STEP 7
information system.
Installing
STEP 7 Safety Basic V15.1
1. Start the programming device or PC on which the
"SIMATIC STEP 7 Basic V15.1"
or
"SIMATIC STEP 7 Professional V15.1
" software package has been installed, and make
sure that
SIMATIC STEP 7 Basic V15.1
or
SIMATIC STEP 7 Professional V15.1
is
closed.
2. Insert the optional package product DVD.
3. Initiate the
SETUP.EXE
program on the DVD.
4. Follow the instructions of the Setup program, bearing in mind the information in the
readme file.
Displaying integrated Help
The help on
STEP 7 Safety Basic V15.1
is completely integrated into the information system
of
SIMATIC STEP 7 Basic V15.1
or
SIMATIC STEP 7 Professional V15.1
. You have the
following two options to open the integrated help:
In the "Help" menu, select the "Show help" command or press <F1> to show the
appropriate help for the context.
Click on the link within a tool tip cascade to go directly to a place with more information
within the help.
Uninstalling
STEP 7 Safety Advanced V15.1
To uninstall
STEP 7 Safety Basic V15.1
, proceed as described in the
STEP 7 Help
under
"Uninstall".
Post-uninstall procedures
After uninstalling the
STEP 7 Safety Basic V15.1
optional package, you can still open
projects with F-CPUs whose F-capability is enabled but you can no longer edit the safety
program. F-I/O is no longer supported.
Product Overview
1.4 Installing/uninstalling STEP 7 Safety Advanced V15.1 optional package
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 31
1.4
Installing/uninstalling STEP 7 Safety Advanced V15.1 optional
package
Software requirements for
STEP 7 Safety Advanced V15.1
At a minimum, the following software package must be installed on the programming device
or PC:
SIMATIC STEP 7 Professional V15 .1
Reviewing the Readme file
The readme file contains important up-to-date information about the software (for example,
Windows versions supported). You can display the readme file in the setup program or open
it later in the
SIMATIC STEP 7
information system.
Installing
STEP 7 Safety Advanced V15.1
1. Start the programming device or PC on which the
"SIMATIC STEP 7 Professional V15.1"
software package has been installed, and make sure that
SIMATIC STEP 7 Professional
V15.1
is closed.
2. Insert the optional package product DVD.
3. Initiate the
SETUP.EXE
program on the DVD.
4. Follow the instructions of the Setup program, bearing in mind the information in the
readme file.
Displaying integrated Help
The help on
STEP 7 Safety Advanced V15.1
is completely integrated into the information
system of
SIMATIC STEP 7 Professional V15.1
. You have the following two options to open
the integrated help:
In the "Help" menu, select the "Show help" command or press <F1> to show the
appropriate help for the context.
Click on the link within a tool tip cascade to go directly to a place with more information
within the help.
Uninstalling
STEP 7 Safety Advanced V15.1
To uninstall
STEP 7 Safety Advanced V15.1
, proceed as described in the
STEP 7 Help
under "Uninstall".
Post-uninstall procedures
After uninstalling the
STEP 7 Safety Advanced V15.1
optional package, you can still open
projects with F-CPUs whose F-capability is enabled but you can no longer edit the safety
program. F-I/O is no longer supported.
Product Overview
1.5 Installing/uninstalling STEP 7 Safety PowerPack
SIMATIC Safety - Configuring and Programming
32 Programming and Operating Manual, 10/2018, A5E02714440-AH
1.5
Installing/uninstalling STEP 7 Safety PowerPack
After the installation of the
STEP 7 Safety PowerPack
the functional scope of
STEP 7 Safety
Advanced V15.1
is available to you.
Software requirements for
STEP 7 Safety PowerPack
At a minimum, the following software package must be installed on the programming device
or PC:
SIMATIC STEP 7 Safety Basic V15.1
SIMATIC STEP 7 Professional V15.1
Installing
STEP 7 Safety PowerPack
1. Start the
Automation License Manager
on the programming device/PC on which the
"SIMATIC STEP 7 Professional V15.1"
software package is installed.
2. Install the license included in the
STEP 7 Safety PowerPack
as described in the
Automation License Manager help
.
Uninstalling
STEP 7 Safety PowerPack
To uninstall the license included in the
STEP 7 Safety PowerPack
, proceed as described in
the
Automation License Manager help
.
1.6
Migrating projects from S7 Distributed Safety V5.4 SP5 to STEP 7
Safety Advanced
Introduction
In
STEP 7 Safety Advanced
, you can continue to use projects with safety programs that you
created with
S7 Distributed Safety V5.4 SP5
.
Requirement
STEP 7 Safety Advanced
,
S7 Distributed Safety V5.4 SP5
, and the
F-Configuration Pack
used to create the project must all be installed on the computer you are using for migration.
The
F-Configuration Pack
V5.4 SP5
to
V5.5 SP13
is supported.
To that end, the projects must have been compiled in
S7 Distributed Safety V5.4 SP5
and
with the
F-Configuration Pack
.
Prior to migration
Delete all F-blocks not required by the safety program in your
S7 Distributed Safety V5.4
SP5
project prior to migration.
Product Overview
1.6 Migrating projects from S7 Distributed Safety V5.4 SP5 to STEP 7 Safety Advanced
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 33
Procedure as in
STEP 7 Professional
Proceed just as you would for standard projects to migrate projects from
S7 Distributed
Safety V5.4 SP5
to
STEP 7 Safety Advanced
. Once the migration is complete, you should
verify using the collective F-signature whether the project was migrated unchanged.
Note
If you use the safety program to migrate F
-blocks with know-how protection, remove the
know
-how protection prior to migration.
You can as
sign the F-blocks know-how protection again once the migration is completed.
This migration approach is described in the "Migration" section of the
STEP 7 Professional
Help. Special considerations about
STEP 7 Safety Advanced
are described below.
Note
We recommend that you enable the "Include hardware configuration" option in the "Migrating
project" window.
Older hardware versions
Older versions of F-hardware may not be supported by
STEP 7 Safety Advanced
.
If you have used and configured versions of F-CPUs and F-I/O in S7 Distributed Safety
projects that are not approved for
STEP 7 Safety Advanced
, you will need to upgrade this
hardware to the new version in
S7 Distributed Safety V5.4 SP5
and the corresponding
F-
Configuration Pack
. Once the upgrade is completed, migration to
STEP 7 Safety Advanced
is feasible. A Product Information with a list of approved hardware is available on the Internet
(https://support.industry.siemens.com/cs/ww/de/view/109481784):
Particularities for safety-related CPU-CPU communication via S7 connections
You can find information about the special considerations for migrated projects with safety-
related CPU-CPU communication via S7 connections in Safety-related communication via
S7 connections (Page 248). Please also note Communication with S7 Distributed Safety via
S7 connections (Page 258).
Particularities for ESTOP1 or FDBACK instructions
Information on the special considerations when using the ESTOP1 and FDBACK instructions
can be found in the "Instruction versions" section in ESTOP1: Emergency STOP/OFF up to
stop category 1 (STEP 7 Safety V15.1) (Page 430) and FDBACK: Feedback monitoring
(STEP 7 Safety V15.1) (Page 475).
Product Overview
1.6 Migrating projects from S7 Distributed Safety V5.4 SP5 to STEP 7 Safety Advanced
SIMATIC Safety - Configuring and Programming
34 Programming and Operating Manual, 10/2018, A5E02714440-AH
Post-migration procedures
Once migration is complete, you have a complete project with a safety program which has
retained the program structure of
S7 Distributed Safety
and the collective F-signature. F-
blocks from the S7 Distributed Safety F-library (V1) are converted into instructions that are
provided by
STEP 7 Safety Advanced
.
The migrated project therefore does not need to be re-accepted; it can be loaded as is to the
F-CPU as long as it has not been modified or compiled since migration.
Note
Safety summary
You cannot create a safety summary in
STEP 7 Safety Advanced
for a migrated project
. The
printout of the project created with
S7 Distributed Safety V5.4 SP5
and the corresponding
acceptance documents are still valid, because the collective F
-signature has been retained.
Compiling of the migrated hardware configuration
If you receive an error message after migration and subsequent compilation of the hardware
configuration stating that the F-source address does not match the "Central F-source
address" parameter of the F-CPU, change the "Central F-source address" parameter.
The F-source addresses of all F-I/Os assigned to the F-CPU are reassigned in the process.
If after migration of an SM 326; DI 24 x DC 24V (6ES7 326-1BK01-0AB0 and 6ES7 326-
1BK02-0AB0) and subsequent compilation of the hardware configuration, the error message
"F_IParam_ID_1: Value outside the permitted range" is displayed, delete the F-SM and
reinsert it.
In both cases, subsequent compilation of the safety program is required.
Compiling the migrated safety programs
As a result of compilation of the migrated project with
STEP 7 Safety Advanced
, the existing
program structure (with F-CALL) is converted to the new program structure of
STEP 7 Safety
Advanced
(with main safety block). This changes the F-collective signature and the safety
program has to be validated or acceptance may have to be carried out again.
(S7-300, S7-400) You must call up the main safety block according to the F-CALL from an
arbitrary block of the standard user program. We recommend a call from an OB 3x.
Note
During the first
-time compiling of the migrated safety program the call of the F-CALL is
replaced automatically by a call of the main safety block, if the calling block of the F
-CALL
was created using the programming language LAD, FBD or STL.
Product Overview
1.6 Migrating projects from S7 Distributed Safety V5.4 SP5 to STEP 7 Safety Advanced
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 35
Note
Changing the Safety system version
Before co
mpiling with
STEP 7 Safety Advanced
for the first time, you must change the safety
system version to a version which is not equal to 1.0 in the "Settings" area of the
Safety
Administration Editor
. We recommend that you use the highest available version.
Note
Using the latest version of instructions
If you want to expand the migrated safety program, we recommend that you update to the
latest version of the instructions used before compiling with
STEP 7 Safety Advanced
for the
first time. Read the informa
tion on instruction versions for each instruction.
Note
Note that compiling the migrated safety program extends the runtime of the F
-runtime
group(s) and increases the memory requirements of the safety program (see also Excel file
for calculating respo
nse time
(
http://support.automation.siemens.com/WW/view/en/49368678/133100)).
See also
Application example "Migration of a safety program to TIA Portal"
(https://support.industry.siemens.com/cs/ww/en/view/109475826)
Product Overview
1.7 Migšrating PLC programs to a n F-CPU S7-1500
SIMATIC Safety - Configuring and Programming
36 Programming and Operating Manual, 10/2018, A5E02714440-AH
1.7
Migšrating PLC programs to a n F-CPU S7-1500
To migrate an F-CPU S7-300/400 onto an F-CPU S7-1500, proceed as with the migration of
a standard CPU S7-300/400 onto a CPU S7-1500.
Points to note after migration:
Non-automatable actions
Creating an F-runtime group and assigning it to the main safety block.
The hardware configuration including the I/O of the initial F-CPU is not automatically
transferred to an S7-1500 F-CPU. Implement the hardware configuration of the new
CPU manually after migration.
Please also read the sections "Specify F-destination address for F-I/O of PROFIsafe
address type 1" and "Specify F-destination address for F-I/O of PROFIsafe address
type 2“ in chapter "Configuring an F-CPU (Page 48)“. Otherwise, this can lead to a
reassignment of the F-destination addresses in the configuration.
When using F-I/Os with PROFIsafe Protocol Version = Expanded Protocol (XP) (for
example S7-1500/ET 200MP F-modules) keep in mind that you need one byte more in
the address area of S7-1200/1500 F-CPUs than in S7-300/400 F-CPUs.
Replacement of the OV instruction by the connection of the ENO output for Math
functions (Page 520).
Replacement of the RD_FDB instruction by the instructions RD_ARRAY_I (Page 539)
and RD_ARRAY_DI (Page 542).
Replacement of the F-runtime group communication through Communication via
Flexible F-Link (Page 145).
Instructions not supported:
MUTING
TWO_HAND
WR_FDB
OPN
SENDS7
RCVS7
Data types not supported
DWORD
Changes to safety program programming
F_GLOBDB.VKE0/1 replaced by FALSE/TRUE (Page 119).
Readable values from the F_GLOBDB replaced by the F-runtime group information
DB. Additional information is available under F-shared DB (S7-300, S7-400)
(Page 148) and F-runtime group information DB (S7-1200, S7-1500) (Page 148).
Replacement of the QBAD_I_xx or QBAD_O_xx tag by the value status. Additional
information is available under Value status (S7-1200, S7-1500) (Page 159) and F-I/O
DB (Page 165).
Product Overview
1.8 Upgrading projects to STEP 7 Safety V15.1
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 37
New naming convention when naming the F-I/O DBs
Modified behavior of QBAD and PASS_OUT (Page 171) tags for F-I/O with "RIOforFA
safety" profile.
Compile the safety program and eliminate any compilation errors displayed.
Note
A new acceptance must b
e carried out following F-CPU migration.
See also
Programming (Page 111)
1.8
Upgrading projects to STEP 7 Safety V15.1
1.8.1
Upgrading projects from STEP 7 Safety V15 to V15.1
If you want to continue to work with a project from
STEP 7 Safety V15
, you must first
upgrade the project to
STEP 7 Safety V15.1
.
Perform the upgrade following the usual procedure for
STEP 7
. After upgrading to V15.1,
you have to compile your safety program.
1.8.2
Upgrading projects from STEP 7 Safety V14 SP1 to V15.1
If you want to continue to work with a project from
STEP 7 Safety V14 SP1
, you must first
upgrade the project to
STEP 7 Safety V15.1
.
Perform the upgrade following the usual procedure for
STEP 7
. After upgrading to V15.1,
you have to compile your safety program.
Product Overview
1.8 Upgrading projects to STEP 7 Safety V15.1
SIMATIC Safety - Configuring and Programming
38 Programming and Operating Manual, 10/2018, A5E02714440-AH
1.8.3
Upgrading projects from STEP 7 Safety V13 SP1 to V15.1
If you want to continue to work with a project from
STEP 7 Safety V13 SP1
, you must first
upgrade the project to
STEP 7 Safety V15.1
.
Perform the upgrade following the usual procedure for
STEP 7
. After upgrading to V15.1,
you have to compile your safety program.
(S7-300/400): After compilation, the safety program is consistent and the collective F-
signature of the upgraded safety program corresponds to the collective F-signature of the
safety program from V13 SP1. Acceptance of changes is not required
(S7-1200/1500): After compiling, your safety program is consistent and the collective F-
signature of the upgraded safety program has changed for system reasons. The new
collective F-signature of the safety program with
STEP 7 Safety V15.1
replaces the former
collective F-signature of the safety program with
STEP 7 Safety V13 SP1
.
You can find an overview of all system-related changes under "Common data/Protocols/F-
Convert Log+CPU name+time stamp". One of the system-related changes is that
STEP 7
Safety V15.1
automatically replaces versions of instructions no longer supported with new,
functionally identical versions. The overview contains a comparison of the previous
signatures with
STEP 7 Safety V13 SP1
to the new signatures with
STEP 7 Safety V15.1
and displays the automatically changed instruction versions. Print out the overview and store
this printout with your acceptance documents or your machine documentation. Change
acceptance is not required, since the "Collective F-signature with
STEP 7 Safety V13 SP1"
contained in the overview matches the collective F-signature in your current acceptance
documents.
Keep in mind that existing change histories are not upgraded. All previous entries are
deleted after the upgrade. If necessary, print out the change log before you upgrade.
Special features for user acknowledgment and reintegration of F-I/O after F-I/O or channel faults and
PASS_ON = 1 (S7-1200, S7-1500)
The following applies to F-I/Os:
S7-300 fail-safe signal modules
ET 200SP fail-safe modules
ET 200S fail-safe modules
ET 200pro fail-safe modules
ET 200iSP fail-safe modules
Keep in mind the changed behavior for user acknowledgment and reintegration when
configuring "Behavior after channel fault" = "Passivation of the channel" and tag ACK_NEC
(F-I/O DB) = 1. The behavior was adapted to the behavior when configuring "Behavior after
channel fault" = "Passivate the entire module":
Product Overview
1.8 Upgrading projects to STEP 7 Safety V15.1
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 39
As of
STEP 7 Safety V14
or higher, user acknowledgment of a corrected F-I/O or channel
fault is
possible
even when the tag PASS_ON (F-I/O DB) = 1. A reintegration (provision of
process values) takes place
as soon as the tag PASS_ON = 0
.
Until
STEP 7 Safety V13 SP1
, user acknowledgment of a corrected F-I/O or channel fault
was
not possible
as long as the tag PASS_ON (F-I/O DB) = 1. A user acknowledgment was
only possible once the tag PASS_ON = 0. The reintegration (provision of process values)
took place immediately after the user acknowledgment.
Special features when using instruction profiles
If you want to use an instruction profile in your project from
STEP 7 Safety V13 SP1
, delete
the instruction profile before you upgrade to
STEP 7 Safety V15.1.
Before deleting, make a
note of your settings. After upgrading create a new instruction profile, if required, and enter
the noted settings there, if applicable. Please note that some instruction versions are no
longer supported under
STEP 7 Safety V15.1
. You will find additional information about the
supported instruction versions in the description of the respective instruction.
1.8.4
Upgrading projects from STEP 7 Safety prior to V13 SP1
If you want to upgrade from a project
prior to
STEP 7 Safety V13 SP1
to
STEP 7 Safety
V15.1
, you must upgrade the project as in Standard to
STEP 7 Safety V13 SP1
via an
intermediate step.
The safety program signature does not change after upgrading the safety program to
STEP
7 Safety V13 SP1
. Acceptance of changes is therefore not required.
Perform the upgrade following the usual procedure for
STEP 7 Professional
.
Product Overview
1.8 Upgrading projects to STEP 7 Safety V15.1
SIMATIC Safety - Configuring and Programming
40 Programming and Operating Manual, 10/2018, A5E02714440-AH
When upgrading a project that was created with
STEP 7 Safety Advanced V11
. please note
the following information:
Note
Adjustments are required before you can continue working on a project upgraded fr
om
STEP
7 Safety Advanced V11
:
There was a product warning for
STEP 7 Safety Advanced V11
regarding setting the
parameters "Discrepancy behavior" and "Reintegration after discrepancy error" for the fail
-
safe digital input and output modules 4F
-DI/3F-DO DC24V/2A (6ES7138-4FC01-0AB0,
6ES7138
-4FC00-0AB0). These parameters could be displayed incorrectly in certain
combinations.
Based on the handling instructions in this product warning, you used a conversion table to
set the affected parameters so that they wer
e displayed incorrectly in the safety summary
and hardware configuration in order for them to have the correct effect in the F
-module. You
also corrected the safety summary by hand to document the actual behavior of F
-modules.
To reverse these changes, fol
low these steps:
1.
Compile the upgraded project with
STEP 7 Safety Advanced V13 SP1
. An error message
is displayed for each F-module in
STEP 7 Safety Advanced V11
the parameters of which
you have corrected: "The CRC (F_Par_CRC) of the module (xxx) does not match the
calculated value (yyy)."
2.
Adapt the parameter assignment of each F-module for which this error message is
displayed to match your handwritten corrections in the safety summary.
3.
Do this for each F-CPU and then compile the safety program.
4.
If the collective F-signature following compiling corresponds to the collective F-signature
on the safety summary, you have made all the necessary corrections.
Product Overview
1.8 Upgrading projects to STEP 7 Safety V15.1
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 41
Use of CPs
F-I/Os operated downstream from a CP443-5 Extended, CP443-1 or CP 443-1 Advanced-IT
were not automatically assigned a unique F-destination address.
As soon as you compile the hardware in a project with such F-I/Os in
STEP 7 Safety V13
SP1
, you are notified for the affected F-I/Os. You have to assign new, unique F-destination
addresses for the reported F-I/Os. Additional information is available under PROFIsafe
addresses for F-I/O of PROFIsafe address type 1 (Page 68), PROFIsafe addresses for F-I/O
of PROFIsafe address type 2 (Page 70) and Peculiarities when configuring fail-safe GSD
based DP slaves and fail-safe GSD based I/O devices (Page 77).
This changes the collective F-signature of the safety program. Because the F-SW collective
signature is unchanged, it is documented that the safety program has remained unchanged.
The changed F-HW collective signature indicates that the safety-related hardware
configuration has changed. You can now verify that solely the changed F-destination
addresses have caused this change:
The F-parameter signature (without address) for each changed F-I/O remains the same.
Only the affected F-I/O DBs are listed in the comparison editor of the safety program with
the filter set to "Compare only F-blocks relevant for certification".
Changed names of F-I/O DBs
Prior to
STEP 7 Safety V13 SP1
it was possible to change the name of an F-I/O DB. This
change results in a changed collective F-signature during upgrading.
If a changed collective F-signature is unwanted during upgrading, follow these steps:
1. Under
STEP 7 Safety V13
, rename the changed names of the F-I/O DBs back to the
original names.
2. Compile the safety program.
The collective F-signature does not change as a result.
3. Print a comparison printout (Page 339).
Use the comparison printout to ensure that you have only changed the names of the F-F-
I/O DBs.
4. Upgrading the safety program to
STEP 7 Safety V13 SP1
. After upgrading, the safety
program has the F-collective signature from step 2.
Product Overview
1.9 First steps
SIMATIC Safety - Configuring and Programming
42 Programming and Operating Manual, 10/2018, A5E02714440-AH
1.9
First steps
Getting Started in SIMATIC Safety
Three Getting Started documents are available to help you begin using SIMATIC Safety.
The Getting Started documentation is an instruction manual that provides a step-by-step
description of how to create a project with SIMATIC Safety. It gives you the opportunity to
quickly become familiar with the scope of features of SIMATIC Safety.
Contents
The Getting Started documentation describes the creation of a single, continuous project that
is extended with each section. Based on the configuration, you program a fail-safe
shutdown, make changes to the programming, and accept the system.
In addition to the step-by-step instructions, the Getting Started documentation also gives you
background information for every new topic, which explains the functions used in more detail
and how they interrelate.
Target audience
The Getting Started documentation is intended for beginners but is also suitable for users
who are switching from
S7 Distributed Safety
.
Download
Three Getting Started documents are available as PDF files for free download in the Industry
Online Support:
STEP 7 Safety Advanced V11 with S7-300/400 F-CPUs
(http://support.automation.siemens.com/WW/view/en/49972838)
STEP 7 Safety Basic V13 SP1 with S7-1200 F-CPUs
(http://support.automation.siemens.com/WW/view/en/34612486/133300) (part of the
manual "S7-1200 Functional Safety manual")
STEP 7 Safety Advanced V13 with S7-1500 F-CPUs
(http://support.automation.siemens.com/WW/view/en/101177693)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 43
Configuring
2
2.1
Overview of Configuration
Introduction
You basically configure a SIMATIC Safety F-system in the same way as a standard S7-300,
S7-400, S7-1200, S7-1500 or ET 200MP, ET 200SP, ET 200S, ET 200iSP, ET 200eco,
ET 200eco PN or ET 200pro automation system in
STEP 7.
This section presents only the essential differences compared to standard configuration you
encounter when configuring a SIMATIC Safety F-system.
This documentation distinguishes between two groups of F-I/O:
F-I/Os of PROFIsafe address type 1
F-I/Os which ensure the uniqueness of the PROFIsafe address solely with the F-destination
address, for example, ET 200S F-modules. The PROFIsafe address is usually assigned by
DIP switches.
F-I/Os of PROFIsafe address type 2
F-I/Os which can ensure the uniqueness of the PROFIsafe address with a combination of
F-source address and F-destination address, for example, S7-1500/ET 200MP F-modules.
The PROFIsafe address is usually assigned with
STEP 7 Safety
.
Which F-components can you configure with the
STEP 7 Safety
optional package?
The table below shows you which F-CPUs you can configure with
STEP 7 Safety Basic
and
which with
STEP 7 Safety Advanced
:
F-CPUs
STEP 7 Safety Basic
STEP 7 Safety Advanced
S7-300 x
S7-400
x
S7-1200
x
x
S7-1500
x
WinAC RTX F
x
S7-1500 F Software Controller
x
Configuring
2.1 Overview of Configuration
SIMATIC Safety - Configuring and Programming
44 Programming and Operating Manual, 10/2018, A5E02714440-AH
The table below shows you which F-I/Os you can configure with
STEP 7 Safety Basic
and
which with
STEP 7 Safety Advanced
as well as which PROFIsafe address type they support:
F-I/O
STEP 7 Safety Basic
STEP 7 Safety Advanced
PROFIsafe address type
S7-300 F-SMs
x**
x**
1
ET 200S F-modules x x 1
ET 200pro F-modules
x
x
1
ET 200iSP F-modules x x 1
ET 200eco DP F-I/Os With S7-300/400 F-CPUs
(only PROFIsafe V1 mode)
1
ET 200eco PN F-I/Os
x
x
2
S7-1200 F-modules
(centrally on S7-1200 F-CPUs)
x x 2
ET 200SP F-modules
x
x
2
S7-1500/ET 200MP F-modules
x
x
2
fail-safe GSD based DP slaves
x
x
*
fail-safe GSD based I/O devices
x
x
*
* Consult the respective documentation to determine the PROFIsafe address type of a GSD based DP slave/GSD based
I/O device. If in doubt, assume that the PROFIsafe address is type 1.
*** F-SMs that only support PROFIsafe V1 mode can only be used on F-CPUs S7-300/400.
Configuring
2.1 Overview of Configuration
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 45
Example: Configured F-system in
STEP 7 Professional
The following figure presents a configured F-system. You choose the fail-safe components in
the "Hardware catalog" task card as you would do with standard components and place
them in the work area of the network or device view. F-components are shown in yellow.
Additional information
For detailed information on F-I/O, refer to the
manuals for the relevant F-I/O
.
Configuring
2.2 Particularities for configuring the F-System
SIMATIC Safety - Configuring and Programming
46 Programming and Operating Manual, 10/2018, A5E02714440-AH
Which safety-related communication options can you configure?
You need to use the
hardware and network editor
to configure the following safety-related
communication options (see Configuring and programming communication (S7-300, S7-400)
(Page 201) or Configuring and programming communication (S7-1200, S7-1500)
(Page 270)):
Communication with Flexible F-Link (Page 262)
Safety-related master-master communication
Safety-related master-master communication for
S7 Distributed Safety
Safety-related master-I-slave communication
Safety-related I-slave-I-slave communication
Safety-related I-slave-slave communication
Safety-related IO controller-IO controller communication
Safety-related IO controller-IO controller communication for
S7 Distributed Safety
Safety-related IO controller-I-device communication
Safety-related IO controller-I-slave communication
Safety-related communication via S7 connections
Safety-related communication via S7 connections for
S7 Distributed Safety
or
S7 F
Systems
2.2
Particularities for configuring the F-System
Configuring is the same as for standard components
You configure a SIMATIC Safety F-system in the same way as a standard S7 system. This
means that you configure and assign parameters for the hardware in the
hardware and
network editor
as a centralized system (F-CPU and F-IO if required e.g. CPU 1516F-3
PN/DP and F-modules S7-1500/ET 200MP) and/or as a distributed system (F-CPU, F-SMs
in ET 200M, F-modules ET 200MP, F-modules ET 200SP, ET 200S, ET 200pro, ET 200iSP,
ET 200eco, ET 200eco PN, fail-safe GSD based DP slaves and fail-safe fail-safe GSD
based I/O devices).
Special F-parameters
For the F-functionality there are special F-parameters that you can review and set in the
"Properties" of the fail-safe components (F-CPU and F-I/O). F-parameters are marked in
yellow.
F-parameters are explained in "Configuring an F-CPU (Page 48)" and "Configuring F-I/O
(Page 53)".
Configuring
2.2 Particularities for configuring the F-System
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 47
Compiling the hardware configuration
You must compile the hardware configuration of the SIMATIC Safety F-system (shortcut
menu "Compile > Hardware configuration"). A configured F-CPU with enabled F-capability is
the only prerequisite for programming the safety program.
Note
Inconsistencies are possible when configuring the hardware and can also be saved. A full
consistency check of the hardware configuration and possible c
onnection data is performed
only during compilation. Therefore, perform "Edit > Compile" regularly.
Changing safety-related parameters
Note
If you change a safety
-related parameter (marked in yellow) for an F-I/O or an F-CPU, you
must then compile the modified hardware configuration and the
Compiling the safety
program
(Page 311) (shortcut menu "Compile > Hardware and software (only changes)")
and download. This also applies for changes to the F
-I/O which are not used in the safety
program. F
-I/O in standard operation is not affected by this.
Configuring
2.3 Configuring an F-CPU
SIMATIC Safety - Configuring and Programming
48 Programming and Operating Manual, 10/2018, A5E02714440-AH
2.3
Configuring an F-CPU
Introduction
You configure the F-CPU basically in the same way as a standard automation system.
F-CPUs are always configurable in
STEP 7
, regardless of whether or not the
STEP 7 Safety
optional package is installed. Without an installed optional package, however, the F-CPU
can only be used as a standard CPU.
If the
STEP 7 Safety
optional package is installed, you can enable or disable the F-capability
for the F-CPU.
If you want to use the F-I/O in safety mode or in safety-related communication, the
F-capability of the F-CPU must be enabled.
F-capability is enabled by default after the
STEP 7 Safety
optional package is installed.
Enabling/disabling F-capability
If you want to modify the F-capability setting, proceed as follows:
1. Select the F-CPU in the device or network view, and select the "Properties" tab in the
inspector window.
2. Select "Fail-safe" in the area navigation.
3. Use the appropriate button to enable/disable the F-capability.
4. If you want to disable F-capability, confirm the "Disable F-activation" dialog with "Yes".
Disabling F-capability for an existing safety program
If you want to disable the F-capability for an F-CPU because you intend to use the F-CPU as
a standard CPU although a safety program is installed, you must note the following:
You need the password for the safety program, if assigned.
The Safety Administration Editor (Page 81) is deleted from the project tree.
The F-OBs are deleted. (S7-1200, S7-1500)
All F-blocks are deleted.
From now on you cannot use F-I/O in safety mode with this F-CPU.
Configuring
2.3 Configuring an F-CPU
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 49
Configuring the F-parameters of the F-CPU
In the "Properties" tab of the F-CPU, you can change or apply the default settings for the
following parameters:
The F-destination address range
Low limit for F-destination addresses
High limit for F-destination addresses
The default F-monitoring time for central or distributed F-I/O at the F-CPU
Note
A change of the F
-monitoring time for central or distributed F-I/O at the F-CPU results in
modifications to the safety program when it is recompiled. A new acceptance may
the
refore be required.
Specify F-destination address for F-I/O of PROFIsafe address type 1
With the parameters "Low limit for F-destination addresses" and "High limit for F-destination
addresses" you specify a range for this F-CPU in which the F-destination address of newly
inserted F-I/Os of PROFIsafe address type 1 (Page 68) is assigned automatically. An F-
destination address that is not within the F-destination address range yet, is also reassigned
when you reassign a DP slave/IO device with the F-CPU or switch on the F-activation of the
F-CPU or change the logical address of this F-module.
The F-destination address is assigned in ascending order starting at the "Low limit for F-
destination addresses". When no free F-destination address is available in the F-destination
address range, the next available free F-destination address outside the F-destination
address range is assigned and a warning is output during compilation.
The maximum possible F-destination address for ET 200S, ET 200eco, ET 200pro, ET
200iSP F-modules and S7-300 F-SMs is 1022.
The F-destination addresses for F-I/O of PROFIsafe address type 1 must be unique network-
wide and CPU-wide.
By selecting different F-destination address ranges for different F-CPUs, you can define
different ranges for the automatic assignment of the F-destination address. This is useful
when you are operating multiple F-CPUs in one network. Subsequent manual address
changes are possible. (see also Recommendation for PROFIsafe address assignment
(Page 65))
Configuring
2.3 Configuring an F-CPU
SIMATIC Safety - Configuring and Programming
50 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example:
You have configured the F-destination address range as follows:
Low limit for F-destination addresses = 100
High limit for F-destination addresses = 199
When inserting the first F-I/O of PROFIsafe address type 1, the F-destination address 100 is
assigned. When inserting an additional F-I/O of PROFIsafe address type 1, the F-destination
address 101 is assigned.
Note
The parameters "Low limit for F
-destination addresses" and "High limit for F-destination
addresses" have no effect on the following F
-I/Os:
SM 326; DI 8 x NAMUR (as of article number 6ES7326-1RF00-0AB0)
SM 326; DO 10 x DC 24V/2A (article number 6ES7326-2BF01-0AB0)
SM 336; AI 6 x 13 bit (article number 6ES7336-1HE00-0AB0)
Specify F-destination address for F-I/O of PROFIsafe address type 2
The F-destination address of F-I/O of PROFIsafe address type 2 (Page 70) is assigned
automatically for each F-CPU in descending order starting with 65534. The low limit is the
value configured with the parameter "Low limit for F-destination addresses" (for F-I/O of
PROFIsafe address type 1) + 1.
When the value configured with the "High limit for F-destination addresses" parameter is
reached, a warning is output during compilation. (See also Recommendation for PROFIsafe
address assignment (Page 65))
Specify F-source address for F-I/O of PROFIsafe address type 2
You specify the F-source address for F-I/O of PROFIsafe address type 2 (Page 70) assigned
to this F-CPU with the "Central F-source address" parameter. The F-source address must be
unique throughout the network. (see also Recommendation for PROFIsafe address
assignment (Page 65))
Note
A change to the "Central F
-source address" parameter results in modifications to the safety
pr
ogram when it is recompiled. A new acceptance may therefore be required because the F-
source addresses of all F
-I/Os of address type 2 are changed centrally by this step.
Configuring
2.3 Configuring an F-CPU
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 51
"Default F-monitoring time" parameter
Configure the "Default F-monitoring time" for monitoring the communication between the
F-CPU and F-I/O.
You can adjust the F-monitoring time via the following parameters:
"Default F-monitoring time for central F-I/O"
"Default F-monitoring time for F-I/O of this interface"
The
default F-monitoring time for the central F-I/O
acts on the F-I/O that is arranged
centrally, i.e. near the F-CPU. You set this parameter in the properties of the F-CPU (select
F-CPU, then select "Properties > Fail-safe > F-parameters").
The
default F-monitoring time for the F-I/O of this interface
acts on the F-I/O that is assigned
to this interface of the F-CPU (PROFIBUS or PROFINET). You change this parameter in the
properties of the relevant interface (selection of the interface in the "Device view" tab, then
"F-parameters").
The various settings available allow you to flexibly adapt the F-monitoring time to the
conditions of your F-system, for example to take account of different bus cycles.
You can also change the F-monitoring time individually for each F-I/O in the F-I/O properties
(see Configuring F-I/O (Page 53) or Peculiarities when configuring fail-safe GSD based DP
slaves and fail-safe GSD based I/O devices (Page 77)).
Note
A change of the F
-monitoring time for central or distributed F-I/O at the F-CPU results in
modifications
to the safety program when it is recompiled. A new acceptance may therefore
be required.
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal state to be transferred will
be acquired at the sender end and transferred to the receiver if the signal level is pending
for at least as long as the assigned monitoring time.
(S018)
You can find additional information in Monitoring and response times (Page 607).
Configuring
2.3 Configuring an F-CPU
SIMATIC Safety - Configuring and Programming
52 Programming and Operating Manual, 10/2018, A5E02714440-AH
Automatic generation of the safety program
The safety program of an F-CPU consists of one or two F-runtime groups that contain the
F-blocks (see also Defining F-Runtime Groups (Page 132)). When the F-CPU (with activated
F-capability) is inserted into the work area of the device view or network view, a safety
program with an F-runtime group is generated automatically.
You can define in
STEP 7 Safety
that no F-runtime group is generated while inserting the
F-CPU (with activated F-capability).
Proceed as follows:
1. Select the "Options > Settings" menu command.
2. Select the "STEP 7 Safety" area.
3. If it is not already disabled, disable automatic generation of an F-runtime group by
deselecting the "Generate default fail-safe program" option.
This change has no influence on any existing safety programs; it only defines whether an
F-runtime group is automatically generated for each one of the subsequently inserted
F-CPUs.
Configuring the protection level of the F-CPU
WARNING
(S7-300, S7-400) In safety mode, access with the CPU password must not be authorized
during changes to the standard user program as this would also allow changes to the safety
program. To rule out this possibility, you must configure the protection level "Write
protection for fail-safe blocks" and configure a password for the F-CPU. If only one person
is authorized to change the standard user program and the safety program, the protection
level "Write protection" or "Read/write protection" should be configured so that other
persons have only limited access or no access at all to the entire user program (standard
and safety programs).
(S001)
WARNING
(S7-1200, S7-1500) In safety mode, the safety program must be password-protected. For
this purpose, configure at least the protection level "Full access (no protection)" and assign
a password under "Full access incl. fail-safe (no protection)". This protection level only
allows full access to the standard user program, not to F-blocks.
If you select a higher protection level, for example to protect the standard user program,
you must assign an additional password for "Full access (no protection)".
Assign different passwords for the individual protection levels.
(S041)
You configure the protection level following the same procedure as for standard CPUs.
For information on the password for the F-CPU, refer to Access protection (Page 101). Pay
special attention to the warnings in Access protection for the F-CPU (Page 106).
Configuring
2.4 Configuring F-I/O
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 53
2.4
Configuring F-I/O
Introduction
You configure the S7-1500/ET 200MP, ET 200SP, ET 200S, ET 200eco (S7-300, S7-400),
ET 200eco PN, ET 200pro and ET 200iSP F-modules, the S7-300 F-SMs and the S7-1200
F-modules as usual in
STEP 7
:
After you have inserted the F-I/O in the work area of the
device or network view
, you access
the configuration dialogs by selecting the relevant F-I/O and the "Properties" tab.
Note
Changes to the parameter assignment result in modifications to the safety program when it is
recompiled. A new acceptance may therefore be required.
The use of ET 200SP F-modules is possible with IM155-6PN ST as of Firmware V1.1, IM
155-6 PN HF and IM 155-6 DP HF.
The distributed use of S7-1500/ET 200MP F-modules is possible with IM 155-5 PN ST as of
firmware V3.0, IM 155-5 PN HF as of firmware V2.0 and IM 155-5 DP ST as of firmware
V3.0.
The central use of S7-1500/ET 200MP F-modules is possible with S7-1500 F-CPUs as of
firmware V1.7, distributed use as of firmware V1.5.
(S7-1200) We recommend you limit the total number of F-I/Os that are used centrally or
distributed in an S7-1200 F-CPU to 12. Depending on the volume of project data, the
maximum number of F-I/Os can be smaller.
WARNING
When you make changes in which the assignment of input/output addresses and wiring can
change, then you must perform a wiring test.
Examples for such changes are:
Adding F-I/O
Changing the start address of F-I/O
Changing the slot position of F-I/O
Changing
the rack
the slave/device address
the PROFIBUS DP/PROFINET IO subnet
the IP address
the device name
(S071)
Configuring
2.4 Configuring F-I/O
SIMATIC Safety - Configuring and Programming
54 Programming and Operating Manual, 10/2018, A5E02714440-AH
Channel-granular passivation after channel faults
You can configure how the F-I/O will respond to channel faults, such as a short-circuit,
overload, discrepancy error, or wire break, provided the F-I/O supports this parameter (e.g.
for ET 200S or ET 200pro F-modules). You configure this response in the properties for the
relevant F-I/O ("Behavior after channel fault" parameter). This parameter is used to specify
whether the entire F-I/O or just the faulty channel(s) are passivated in the event of channel
faults.
Note
(S7
-300, S7-400) Note that channel-granular passivation increases the runtime of the F-
runtime group(s) compared to passivation of the entire F
-
I/O (see also Excel file for response
time cal
culation (http://support.automation.siemens.com/WW/view/en/49368678/133100)).
"Channel failure acknowledge" parameter (S7-1200, S7-1500)
In the case of F-I/Os that support the "Channel failure acknowledge" channel parameter (for
example S7-1500/ET 200MP F-modules and S7-1200 F-modules), this replaces the
ACK_NEC tag of the F-IO data block.
If an F-I/O fault is detected by the F-I/O, passivation of all channels of the relevant F-I/O
occurs. If channel faults are detected, the relevant channels are passivated if "Passivate
channel" is configured. If "Passivate the entire module" is configured, all channels of the
relevant F-I/O are passivated. Once the F-I/O fault or channel fault has been eliminated,
reintegration of the relevant F-I/O occurs in line with the "Channel failure acknowledge"
parameter.
Automatically
Manually
Adjustable (when channel-granular passivation is configured.)
WARNING
The parameter assignment "Channel failure acknowledge = Automatic" is only allowed if
automatic reintegration is permitted for the relevant process from a safety
standpoint.
(S045)
Note
The default assignment for the "Channel failure acknowledge" parameter when the F
-
module
is created is "Manually".
Configuring
2.4 Configuring F-I/O
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 55
Organization block/Process image (S7-1200, S7-1500)
If you use F-I/O in standard mode, you can select the organization block/process image as
you do for standard I/O.
If you use F-I/O in safety mode, no selection is possible. The process image is updated at
the beginning or end of the F-OB (see section Program structure of the safety program
(S7-1200, S7-1500) (Page 114)).
Contrary to F-I/O operated in non-isochronous mode, you need to selected a process image
partition, such as PIP 1 for F-I/O that is operated in isochronous mode (see "Configuring
isochronous mode (S7-1500) (Page 63)").
Changing the name and number of the F-I/O DB
The name and number of the F-I/O DB (Page 165) are assigned automatically when the
F-I/O is configured. The name of the F-I/O DB by default contains the start address and the
name of the F-I/O. You can disable adding the prefix of the start address. The naming
scheme depends on the setting in Safety Administration Editor.
You can find information on the assignment of number ranges and disabling the prefix of the
start address in
Safety Administration Editor
, "Settings" area (Page 90).
Change the number of the F-I/O DB:
Change the number in the properties of the F-I/O.
Change the name of the F-I/O DB:
The name of the F-I/O DB is derived by the system from the name of the F-I/O depending on
the type of F-I/O.
For F-I/O with an F-module with a single F-submodule, the module name is used.
For F-I/O with multiple F-submodules, the submodule name is used.
You change the name of the F-I/O DB indirectly by changing the name of the F-I/O.
Configuring
2.4 Configuring F-I/O
SIMATIC Safety - Configuring and Programming
56 Programming and Operating Manual, 10/2018, A5E02714440-AH
Customizing the F-monitoring time for F-I/O
You can customize the F-monitoring time in the properties of the F-I/O under "F-parameters".
This may be necessary to prevent a timeout being triggered when no error occurs and the F-
I/O requires a longer F-monitoring time or assignment with a default F-monitoring time is not
possible. For this purpose, activate the corresponding check box and assign an F-monitoring
time.
Note
A change of the F
-monitoring time for central or distributed F-I/O at the F-CPU results in
mo
difications to the safety program when it is recompiled. A new acceptance may therefore
be required.
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal state to be transferred will
be acquired at the sender end and transferred to the receiver if the signal level is pending
for at least as long as the assigned monitoring time.
(S018)
You can find additional information in Monitoring and response times (Page 607).
Group diagnostics for fail-safe S7-300 signal modules
By disabling a channel of the fail-safe signal module in the module properties, you also
disable the group diagnostics for this channel.
Exception for S7-300/400 F-CPUs:
For the following S7-300 fail-safe signal modules
SM 326; DI 8 x NAMUR (as of article number 6ES7326-1RF00-0AB0)
SM 326; DO 10 x DC 24V/2A (article number 6ES7326-2BF01-0AB0) and
SM 336; AI 6 x 13Bit (article number 6ES7336-1HE00-0AB0)
Configuring
2.4 Configuring F-I/O
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 57
the "Group diagnostics" parameter enables and disables the monitoring of channel-specific
diagnostic messages of F-SMs (such as wire break and short-circuit) to the F-CPU. You
should disable group diagnostics for
unused
input or output channels.
WARNING
(S7-300, S7-400) For the following S7-300 fail-safe signal modules (F-SMs) with activated
safety mode, "Group diagnostics" must be enabled for all connected channels:
SM 326; DI 8 x NAMUR (as of article number 6ES7326-1RF00-0AB0)
SM 326; DO 10 x DC 24V/2A (article number 6ES7326-2BF01-0AB0)
SM 336; AI 6 x 13 Bit (article number 6ES7336-1HE00-0AB0)
Check to verify that you have only disabled group diagnostics for these F-SMs for input and
output channels that are actually unused.
(S003)
Diagnostic interrupts can be enabled optionally.
Additional information
For detailed description of the
parameters
, refer to the help on the properties of the
respective F-I/O and in the respective
manual for the F-I/O
.
Configuring
2.5 Configuration control (option handling) for F-I/Os
SIMATIC Safety - Configuring and Programming
58 Programming and Operating Manual, 10/2018, A5E02714440-AH
2.5
Configuration control (option handling) for F-I/Os
For configuration control (option handling) with F-I/Os proceed as with the standard I/O
devices. Detailed information can be obtained by searching for "Configuration control (option
handling)" in the help of
STEP 7
.
The following section describes what you have to observe additionally for F-I/Os.
Requirement
The requirements that are specified under "Configuration control (option handling)" in the
help of
STEP 7
are fulfilled.
The requirements that are specified under "Configuration control (option handling)" in the
help of
STEP 7
are fulfilled. Handle the F-I/O as standard I/O.
V2.1. is set as a safety system version.
The F-I/Os for which you use the configuration control (option handling) are located
Distributed at an F-CPU S7-300/400/1200/1500
Centrally at an F-CPU S7-1500
The PROFIsafe address of the F-I/Os are set or assigned.
Note
The
assignment of the PROFIsafe addresses (Page 72) is only possible if the maximum
configuration actually exists.
Procedure
(F-CPU S7-1200/1500) Deactivate the F-I/Os not existing in the respective variant (option)
by setting the DISABLE (Page 170) variable in the associated F-I/O DB (Page 165) to "1".
This prevents the flashing of the error LED of the F-CPU and diagnostic entries of the safety
program that reference these F-I/Os. With the DISABLED (Page 171) variable of the
associated F-IO data block, you can evaluate whether an F-module is deactivated.
(F-CPU S7-300/400) In order to prevent the flashing of the error LEDs of the F-CPUs you do
have to observe anything further. You cannot suppress diagnostics entries.
WARNING
If configuration control is used, your actual configuration deviates from the configured
maximum configuration. You identify F-I/Os that do not exist in the current variant (station
option) via control record as "not available".
If an F-I/O marked as "not available" is possibly nevertheless in the real structure, it has to
be ensured that substitute values (0) are provided for these F-I/Os in the safety program or
output at the outputs. This is achieved by setting the DISABLE variable (S7-1200/1500) or
respectively PASS_ON variable (S7-300/400) in the associated F-I/O DB to "1".
(S077)
Configuring
2.5 Configuration control (option handling) for F-I/Os
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 59
2.5.1
Example
Introduction
The following example shows how you to
Select/detect a station option
Disable F-I/Os that are not present in a station option (S7-1200/1500)
Provide your safety program for various station options
Safe selection/detection of the station option
You carry out a safe selection/detection of a station option with inputs of an F-I/O wired fixed
to M/L+.
For example, you can select up to 4 station options with 2 inputs of an F-I/O.
Option
OptionSelection_Bit_0
OptionSelection_Bit_1
Q
0
0
B 0 1
C
1
0
D
1
1
Note when detecting the station option that substitute values (0) are used for the inputs of
the F-I/O in certain situations, e.g. during startup of the F-system or when F-I/O channel
errors occur.
In these situations, the present station option cannot be detected. You should therefore also
evaluate the value status of inputs and only apply the station option one-time after startup of
the F-system.
Configuring
2.5 Configuration control (option handling) for F-I/Os
SIMATIC Safety - Configuring and Programming
60 Programming and Operating Manual, 10/2018, A5E02714440-AH
For one-time recognition of the station option, define a static local datum, for example,
OptionSelectionRuns with default value "TRUE".
Correspondingly for options C and D.
As soon as a station option is detected, reset the static local datum for one-time detection of
the station option:
Note
When you make the selection/detection of a station option only in the standard user
program, only the "Station option" is avai
lable to you as a standard datum that is not
secured.
Make sure that no dangerous states arise from this.
Read the section "
Data exchange between standard user program and safety program
(Page
195)".
Configuring
2.5 Configuration control (option handling) for F-I/Os
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 61
Disabling F-I/Os that are not present in a station option
If one or more F-I/Os are not present in a station option, you can prevent the blinking of the
error LED of the F-CPU by disabling these F-I/Os.
In addition, diagnostic messages of the safety program that refer to these F-I/Os are
suppressed.
Note
As long as the detection of the station option (during startup of the F
-system) is not yet
complete (OptionSelectionRuns = TRUE), you should disab
le all "optional" F-I/O devices.
Configuring
2.5 Configuration control (option handling) for F-I/Os
SIMATIC Safety - Configuring and Programming
62 Programming and Operating Manual, 10/2018, A5E02714440-AH
Providing the safety program for various station options
In the following example, the EMERGENCY STOP signals of different plant units or
machines are combined into a collective EMERGENCY STOP signal.
Machines I and III and the corresponding F-I/O with the EMERGENCY STOP signal for
machines I and III are not present with station option A.
Machine II and the corresponding F-I/O with the EMERGENCY STOP signal for machine II is
not present with station option B.
The substitute values (0) are therefore used in the safety program for the EMERGENCY
STOP signals from the respective unavailable machines.
In order to prevent the collective EMERGENCY STOP from being triggered because
machines / EMERGENCY STOP signals are not present with certain station options, you can
suppress the evaluation of the EMERGENCY STOP signal for unavailable machines by
taking into account the present station option.
Configuring
2.6 Configuring shared device
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 63
2.6
Configuring shared device
To configure shared devices follow the procedure as in the standard. The configuration is
described in the
STEP 7
help under "Configuring shared devices".
F-destination addresses
Please also read the chapter "Recommendation for PROFIsafe address assignment
(Page 65)“ for assigning the F-destination address.
See also
Assign PROFIsafe address to an F-module (Page 75)
2.7
Configuring isochronous mode (S7-1500)
To configure isochronous mode for F-I/Os that support this mode, e.g. "Profisafe Telgr 902"
submodule of the SINAMICS S120 CU310-2 PN V5.1 drive, proceed as in the standard. The
configuration is described in the
STEP 7
help under "Configuring isochronous mode".
Note the following:
Contrary to F-I/O operated in non-isochronous mode, you need to selected a process
image partition, such as PIP 1 for F-I/O that is operated in isochronous mode.
This process image partition must contain only F-I/O operated in isochronous mode and
no standard I/O.
The assigned isochronous mode interrupt OB must first be generated as F-OB by
specifying a F-runtime group (see Procedure for defining an F-runtime group (S7-1200,
S7-1500) (Page 137)). It is not possible to add an F-OB with event class "Synchronous
Cycle" directly during the configuration of the isochronous mode.
Requirement
F-CPUs S7-1500 as of firmware version 2.0, with IRT support.
Configuring
2.7 Configuring isochronous mode (S7-1500)
SIMATIC Safety - Configuring and Programming
64 Programming and Operating Manual, 10/2018, A5E02714440-AH
Connection of F-I/O operated in isochronous mode to the isochronous mode interrupt OB
You access F-I/O operated in isochronous mode in the same way as you do standard I/O
operated in isochronous mode, via the select process image partition.
Contrary to standard I/O that is operated in isochronous mode, the process image partition is
updated by the F-system at the beginning or end of the F-OB (see Program structure of the
safety program (S7-1200, S7-1500) (Page 114)).
No calling of the instructions SYNC_PI and SYNC_PO is required in the F-OB.
Note
With isochronously operated F
-I/O, it is not ensured (fail-safe) that all input data of the F-
I/Os
assigned to the process image partition are consistently available at the beginning of the
main safety block or all output data is transferred consistently to the F
-I/Os, in other words,
log
ically and temporally together. The consistency is only ensured within an F-I/O.
The consistency of all isochronous F
-I/Os of the process image partition usually depends on
the number of isochronous F
-I/Os and the scope of the safety program in the isochronous
mode interrupt OB.
If there are corresponding consistency requirements, you must check the consistency of the
input and output data yourself. You can do this, for example, by additionally transferring and
evaluating time stamps in the input and output
data of the isochronous F-I/Os.
Configuring
2.8 Recommendation for PROFIsafe address assignment
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 65
2.8
Recommendation for PROFIsafe address assignment
Before inserting the F-I/O, specify an address range for each F-CPU for the F-destination
addresses of the F-I/O of PROFIsafe address type 1 (Page 68) that does not overlap with
the address range of any other F-CPU network-wide or CPU-wide (system-wide). You define
the range for F-I/Os of PROFIsafe address type 1 with the parameters "Low limit for
F-destination addresses" and "High limit for F-destination addresses" (see also section
Configuring an F-CPU (Page 48)).
The F-destination addresses of F-I/O of PROFIsafe address type 2 (Page 70) must not
overlap with any address range of the F-I/O of PROFIsafe address type 1. The ranges of the
F-destination addresses of the F-I/O of PROFIsafe address type 2 may overlap if the
F-source addresses are different. This is the case for supported configurations (Page 66) if
the "Central F-source address" parameter has been set differently for each F-CPU.
Assign relatively low F-destination addresses for F-I/O of PROFIsafe address type 1 and
relatively high F-destination addresses for F-I/O of PROFIsafe address type 2.
Figure 2-1 Address assignment for F-I/O of PROFIsafe address types 1 and 2
The safety summary (Page 364) lists the following information for each F-CPU:
"Central F-source address" parameter (F-source address for F-I/O of PROFIsafe address
type 2)
Actually used range of the F-destination addresses of the assigned F-I/O of PROFIsafe
address type 1
Actually used range of the F-destination addresses of the assigned F-I/O of PROFIsafe
address type 2
Any F-I/O configured using I-slave-slave communication is taken into consideration in the
safety summary as part of the F-destination address range of the I-slave.
Any F-I/O configured in a shared device is taken is specified in the safety summary as part of
the F-destination address range of the F-CPU to which this F-I/O is assigned.
Configuring
2.9 Configurations supported by the SIMATIC Safety F-system
SIMATIC Safety - Configuring and Programming
66 Programming and Operating Manual, 10/2018, A5E02714440-AH
2.9
Configurations supported by the SIMATIC Safety F-system
Supported configurations
F-I/Os (see Overview of Configuration (Page 43)) are supported in the following
configurations:
central configuration (also I-slave):
The F-I/O is in the same rack as the associated F-CPU.
The F-I/O is located in a subrack of the rack of the associated F-CPU.
distributed configuration (at integrated DP-/PN interface of the CPU or at CP/CM):
PROFIBUS (also after IE/PB link)
The F-I/O is located on a DP Slave.
The F-I/O is located on a DP Slave and is addressed via I-slave-slave communication.
The assigned DP master (of the assigned IO controller of the IE/PB link) can be a
standard CPU or an F-CPU.
PROFINET IO
The F-I/O is located on an IO Device.
The F-I/O is located in a shared device.
For F-I/O not listed in "Overview of Configuration (Page 43)", please check the relevant
documentation to see whether it is supported by the SIMATIC Safety F-system. If in doubt,
treat these F-I/Os as part of a configuration that is not supported.
Checks performed by the SIMATIC Safety F-system
For supported configuration, the F-system checks:
Whether the PROFIsafe operating mode parameter (F_Par_Version) is set to V2 mode in
the PROFINET IO environment**.
Whether the F-destination addresses have been assigned uniquely CPU-wide.
You yourself must ensure the network-wide uniqueness of the PROFIsafe address.
Whether the F-source address for the F-I/O of PROFIsafe address type 2 corresponds to
the "Central F-source address" parameter of the F-CPU.
Configuring
2.10 PROFIsafe addresses for F-I/O of PROFIsafe address type 1
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 67
WARNING
Please note the following with configurations that are not included in supported
configurations:
Make sure that the F-I/O of this configuration appears in the safety summary and that an
F-I/O DB has been created for it. Otherwise, you cannot use the F-I/O in this
configuration. (Contact Customer Support.)
For F-I/Os in the PROFINET IO environment**, you must check the PROFIsafe
operating mode parameter (F_Par_Version) against the safety summary to make sure
that it is correct. V2 mode must be set in the PROFINET IO environment. F-I/O which
only support V1 mode may not be used in the PROFINET IO environment.
You must ensure that PROFIsafe address assignment is unique CPU-wide* and
network-wide***:
Check the correctness of the PROFIsafe addresses with the help of the safety
summary.
Use the safety summary to check that the F-source address corresponds to the
"Central F-source address" parameter of the F-CPU for F-I/O of PROFIsafe address
type 2.
For F-I/O of PROFIsafe address type 1 or if you cannot set the F-source address in
accordance with the "Central F-source address" parameter of the F-CPU, you will
have to ensure the uniqueness of the PROFIsafe address solely by assigning a
unique F-destination address.
You must check the uniqueness of the F-destination address individually for each F-I/O
based on the safety summary in a configuration that is not supported. (see
Completeness and correctness of the hardware configuration (Page 368))
(S050)
* "CPU-wide" means all F-I/Os assigned to an F-CPU: Central F-I/O of this F-CPU as well as
F-I/Os for which the F-CPU is DP master/IO controller and assigned F-I/O in a shared
device. An F-I/O that is addressed using I-slave-slave communication is assigned to the
F-CPU of the I-slave and not to the F-CPU of the DP master / IO controller.
** The F-I/O is located in the "PROFINET IO environment" if at least part of safety-related
communication with the F-CPU takes place via PROFINET IO. If the F-I/O is connected via
I-slave-slave communication, also keep in mind the communication line to the DP master/IO
controller.
*** A network consists of one or more subnets. "Network-wide" means beyond the
boundaries of the subnet. In PROFIBUS, a network includes all nodes accessible via
PROFIBUS DP. In PROFINET IO, a network includes all nodes accessible via
RT_Class_1/2/3 (Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP
(IP, Layer 3).
Configuring
2.10 PROFIsafe addresses for F-I/O of PROFIsafe address type 1
SIMATIC Safety - Configuring and Programming
68 Programming and Operating Manual, 10/2018, A5E02714440-AH
2.10
PROFIsafe addresses for F-I/O of PROFIsafe address type 1
F-destination address
The uniqueness of the PROFIsafe address is ensured solely with the F-destination address.
The F-source address is not displayed and has no effect on whether or not the PROFIsafe
address is unique.
Therefore, the F-destination address must be unique network-wide and CPU-wide (see the
following rules for address assignment).
To prevent incorrect parameter assignment, an F-destination address which is unique CPU-
wide is automatically assigned during placement of the F-I/O in the work area of the device
or network view as long as you only configure supported configurations (Page 66).
To ensure a network-wide unique F-destination address assignment when multiple DP
master systems and PROFINET IO systems are operated on one network, you must set the
"Low limit for F-destination addresses" and "High limit for F-destination addresses" in the
properties of the F-CPU in SIMATIC Safety F-systems appropriately, before placing the F-I/O
(see section "Recommendations for address assignment") so that the F-destination address
ranges do not overlap.
When you change the F-destination address of an F-I/O, the CPU-wide uniqueness of the
F-destination address is checked automatically for supported configurations. You yourself
must ensure the network-wide uniqueness of the F-destination address.
For ET 200S, ET 200eco (PROFIBUS), ET 200pro, ET 200iSP F-modules and S7-300
F-SMs:
You must set the F-destination address at the F-I/O with the DIP switch before you install the
F-I/O. You can assign up to 1022 different F-destination addresses.
Note
(S7
-300, S7-400) For the following fail-safe S7-300 signal modules, the F-destination
address is the start address of the F
-SM divided by 8:
SM 326; DI 8 x NAMUR (as of article number 6ES7326-1RF00-0AB0)
SM 326; DO 10 x DC 24V/2A (article number 6ES7326-2BF01-0AB0)
SM 336; AI 6 x 13 Bit (article number 6ES7336-1HE00-0AB0)
You can show the columns "F-source address" and "F-destination address" in the device
view of the device overview. The addresses displayed in these columns are for information
purposes only. You have to check the F-destination addresses in the safety summary when
you accept the system.
Configuring
2.10 PROFIsafe addresses for F-I/O of PROFIsafe address type 1
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 69
Rules for address assignment
WARNING
F-I/Os of PROFIsafe address type 1 are uniquely addressed by their F-destination address
(e.g. with the switch setting on the address switch).
The F-destination address (and therefore also the switch setting on the address switch) of
the F-I/O must be unique network-wide* and CPU-wide** (system-wide)
for the entire
F-I/O.
The F-I/O of PROFIsafe address type 2 must also be considered.
(S051)
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet. In PROFIBUS, a network includes all nodes accessible via PROFIBUS DP. In
PROFINET IO, a network includes all nodes accessible via RT_Class_1/2/3
(Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP (IP, Layer 3).
** "CPU-wide" means all F-I/Os assigned to an F-CPU: Central F-I/O of this F-CPU as well
as F-I/Os for which the F-CPU is DP master/IO controller and assigned F-I/O in a shared
device. An F-I/O that is addressed using I-slave-slave communication is assigned to the F-
CPU of the I-slave and not to the F-CPU of the DP master / IO controller.
Please also note Recommendation for PROFIsafe address assignment (Page 65).
See also
Completeness of the safety summary (Page 364)
Configuring
2.11 PROFIsafe addresses for F-I/O of PROFIsafe address type 2
SIMATIC Safety - Configuring and Programming
70 Programming and Operating Manual, 10/2018, A5E02714440-AH
2.11
PROFIsafe addresses for F-I/O of PROFIsafe address type 2
F-source address and F-destination address
The uniqueness of the PROFIsafe address is ensured by the combination of F-source
address and F-destination address.
The PROFIsafe address must be unique network-wide and CPU-wide. This is the case if the
following two conditions are met:
The F-source address ("Central F-source address" parameter) of the F-CPU is unique
network-wide. Keep this in mind for changes.
The F-destination address of the F-module is unique CPU-wide.
You define the F-source address using the "Central F-source address" parameter in the F-
CPU. Provided you only configure supported configurations (Page 66), this parameter is
automatically applied as the F-source address and a CPU-wide unique F-destination
address is assigned (usually in descending order starting with 65534).
When you change the F-destination address, the CPU-wide uniqueness of the F-destination
address is checked automatically for supported configurations.
You must assign the F-source address and F-destination address to the F-I/O before you
commission the F-I/O. You can find additional information in Assigning a PROFIsafe address
of the F-I/Os with SIMATIC Safety (Page 72).
You can show the columns "F-source address" and "F-destination address" in the device
view of the device overview. The addresses displayed in these columns are for information
purposes only. You have to check the F-source and F-destination addresses in the safety
summary when you accept the system.
Configuring
2.11 PROFIsafe addresses for F-I/O of PROFIsafe address type 2
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 71
Rules for address assignment
WARNING
FI/O of PROFIsafe address type 2 is uniquely addressed using a combination of F-source
address ("Central F-source address" parameter of the assigned F-CPU) and F-destination
address.
The combination of F-source address and F-destination address for each F-I/O must be
unique network-wide* and CPU-wide** (system-wide). In addition, the F-destination
address may not be occupied by F-I/O of PROFIsafe address type 1.
To ensure that addresses are unique across F-CPUs for supported configurations
(Page 66), you need to ensure that the "Central F-source address" parameter of all F-CPUs
is unique network-wide*. This is achieved through different settings for the "Central F-
source address" parameter of the F-CPUs.
(S052)
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet. In PROFIBUS, a network includes all nodes accessible via PROFIBUS DP. In
PROFINET IO, a network includes all nodes accessible via RT_Class_1/2/3
(Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP (IP, Layer 3).
** "CPU-wide" means all F-I/Os assigned to an F-CPU: Central F-I/O of this F-CPU as well
as F-I/Os for which the F-CPU is DP master/IO controller and assigned F-I/O in a shared
device. An F-I/O that is addressed using I-slave-slave communication is assigned to the F-
CPU of the I-slave and not to the F-CPU of the DP master / IO controller.
Please also note Recommendation for PROFIsafe address assignment (Page 65).
See also
Completeness of the safety summary (Page 364)
Configuring
2.12 Setting the F-destination address for F-I/O with DIP switches
SIMATIC Safety - Configuring and Programming
72 Programming and Operating Manual, 10/2018, A5E02714440-AH
2.12
Setting the F-destination address for F-I/O with DIP switches
Information on how to set the F-destination address for F-I/O with DIP switches is available
in the documentation of the respective F-I/O.
2.13
Assigning a PROFIsafe address of the F-I/Os with SIMATIC Safety
Introduction
Fail-safe ET 200SP modules, fail-safe S7-1500/ET 200MP modules, fail-safe ET 200eco PN
I/O modules and fail-safe S7-1200 modules do not have a DIP switch with which you set the
unique F-destination address for each module. Instead, you assign the PROFIsafe address
(Page 66) consisting of F-source address and F-destination address directly from
STEP 7
Safety
for fail-safe ET 200SP modules, fail-safe ET 200eco PN I/O modules and fail-safe S7-
1500/ET 200MP modules. The PROFIsafe addresses for S7-1200 F-modules are
automatically assigned during download of the hardware configuration.
In the following cases it is necessary to reassign the addresses of the fail-safe ET 200SP,
fail-safe ET 200eco PN I/O modules and fail-safe S7-1500/ET 200MP modules:
Later placement of a fail-safe module during initial commissioning (not for ET 200eco PN)
Intentional modification of the F-destination address
Modification of the "Central F-source address" parameter for the associated F-CPU
(changes the F-source address).
Replacement of the coding element
Commissioning of a mass-produced machine
In the following cases it is not necessary to reassign the addresses of the fail-safe ET 200SP
and fail-safe S7-1500/ET 200MP modules:
Power On/Off
Replacement of an F-module (repair) without PG/PC
Replacement of the BaseUnit (transferring the coding element with assigned F-source
address and F-destination address to the new BaseUnit)
Replacement of a BaseUnit without coding element
Changes in the design in case a new BaseUnit is inserted in front of a fail-safe module
Repair/replacement of the interface module
Reassignment is not required for fail-safe ET 200eco PN I/O modules in the following cases:
Power On/Off
Replacement of the compact device (transferring the coding element with assigned F-
source address and F-destination address to the new compact device)
Configuring
2.13 Assigning a PROFIsafe address of the F-I/Os with SIMATIC Safety
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 73
Basic procedure
Note
Assigning the PROFIsafe address for S7-1200 fail-safe modules
The procedu
re described below for identifying and assigning the PROFIsafe addresses is
not required for S7
-1200 fail-safe modules.
Note that an S7
-1200 F-CPU must not include an additional unconfigured F-module.
1. Configure the F-destination address (Page 70) and F-source address (Page 70) in the
hardware configuration in
STEP 7 Safety
.
2. Identify the ET 200SP, S7-1500/ET 200MP or the ET 200eco PN fail-safe I/O modules to
which you want to assign the configured PROFIsafe addresses.
3. Assign the PROFIsafe address to the F-modules.
2.13.1
Identifying F-modules
Requirement
The following requirements must be met:
The F-CPU and fail-safe modules are configured.
The hardware configuration has been downloaded.
When using an ET 200SP Open Controller, the hardware configuration of the ET 200SP
Open Controller
and
of the fail-safe software controller must be downloaded.
The F-CPU and fail-safe modules can be reached online.
WARNING
Make sure that the latest hardware configuration has been downloaded to the F-CPU
before identification.
Clicking "Identification" confirms the fail-safe correctness of the PROFIsafe addresses for
the fail-safe modules.
Therefore, proceed carefully when confirming the F-modules by LED flashing or the serial
number of the F-CPU with central fail-safe modules or the serial number of the interface
module with fail-safe modules.
An assignment of the PROFIsafe addresses with the serial number of the interface module
is only permitted when the assignment is made for all F-I/Os of a station. When selecting
individual F-I/Os, the flashing of each individual F-I/O must be checked and confirmed.
(S046)
Configuring
2.13 Assigning a PROFIsafe address of the F-I/Os with SIMATIC Safety
SIMATIC Safety - Configuring and Programming
74 Programming and Operating Manual, 10/2018, A5E02714440-AH
Procedure
Proceed as follows to identify the F-modules:
1. Establish an online connection to the F-CPU with which the fail-safe modules are
operated.
2. In the network view, select the F-CPU with fail-safe modules or the interface module with
the fail-safe modules to which you want to assign the PROFIsafe address.
3. Select "Assign PROFIsafe address" from the shortcut menu.
4. Under "Assign PROFIsafe address by", select the method to be used for identifying the F-
modules.
"Identification by LED flashing"
This is the default setting. The DIAG and STATUS LEDs of the F-modules to be
identified flash upon identification.
"Identification by serial number"
If you cannot see the fail-safe modules directly, you can identify the fail-safe modules
by the serial number of the F-CPU or interface module.
Note
The displayed serial number may be amended with a year number compared to the
serial number pri
nted on the interface module. The serial numbers are nevertheless
identical.
Note
Determining the serial number of an ET 200SP Open Controller
When you use the ET 200SP F
-modules centrally on an ET 200SP Open Controller
and identify them by the seria
l number, then read the serial number in the display of
the fail
-safe S7-1500 software controller in the menu "Overview > CPU".
5. In the "Assign" column, select all the F-modules to which you want to assign the
PROFIsafe address.
If you select the F-CPU or the interface module in the "Assign" column, all F-modules of
the station are selected.
6. Click the "Identification" button. Check whether the DIAG and STATUS LEDs for the F-
modules whose PROFIsafe address you want to assign are flashing green. If you identify
using the serial number, compare the displayed serial number to the serial number of the
F-CPU with central fail-safe modules or the interface module with fail-safe modules.
7. If you have configured more S7-1500/ET 200MP fail-safe modules than exist online, a
dialog is displayed. Enter the number of S7-1500/ET 200MP fail-safe modules actually
existing in this dialog and confirm the dialog.
If you have configured fewer S7-1500/ET 200MP fail-safe modules than exist online, the
online-offline difference is shown and the assignment of the PROFIsafe address is not
possible.
Configuring
2.13 Assigning a PROFIsafe address of the F-I/Os with SIMATIC Safety
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 75
2.13.2
Assign PROFIsafe address
Requirement
The F-modules have been successfully identified.
Procedure
To assign a PROFIsafe address, proceed as follows:
1. In the "Confirm" column, select all the fail-safe modules to which you want to assign the
F-source address and F-destination address.
2. Use the "Assign PROFIsafe address" button to assign the PROFIsafe address to the fail-
safe modules. You may have to enter the password of the F-CPU.
You must acknowledge the "Acknowledge assignment" dialog within 60 seconds to
assign the PROFIsafe address.
2.13.3
Assign PROFIsafe address to an F-module
Introduction
In the "Assign PROFIsafe address" dialog only the F-modules which are assigned to an F-
CPU of this project are offered, as the PROFIsafe address of an F-module in a shared
device can only be assigned from a project in which the F-CPU to which the F-modules are
assigned is located.
Requirement
Requirement for assignment of the PROFIsafe address is that you have downloaded the
hardware configuration completely to the F-CPU. When you have assigned the F-modules in
a shared device to multiple F-CPUs, you must first download the hardware configuration of
all F-CPUs involved before you assign the PROFIsafe addresses.
Note the following for the assignment:
If the corresponding interface module is not assigned to the corresponding CPU, the
programming device and shared device must be located in the same subnet. Otherwise,
follow the procedure as described in the sections Identifying F-modules (Page 73) and
Assign PROFIsafe address (Page 75).
See also
Configuring shared device (Page 63)
Configuring
2.13 Assigning a PROFIsafe address of the F-I/Os with SIMATIC Safety
SIMATIC Safety - Configuring and Programming
76 Programming and Operating Manual, 10/2018, A5E02714440-AH
2.13.4
Changing the PROFIsafe address
Changing the PROFIsafe address
Note
Keep in mind that after changing the PROFIsafe address of an F
-I/O you must also conduct
an
acceptance (Page 368) including check of your change (Page 378) per safety summary
(Page
341).
1. You change the PROFIsafe address (F-destination address, F-source address) in the
hardware configuration.
2. Compile the hardware configuration.
3. Download the hardware configuration to the F-CPU.
4. Select "Assign PROFIsafe address" from the shortcut menu.
5. Proceed as described under Identifying F-modules (Page 73) and Assign PROFIsafe
address (Page 75).
Configuring
2.14 Peculiarities when configuring fail-safe GSD based DP slaves and fail-safe GSD based I/O devices
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 77
2.14
Peculiarities when configuring fail-safe GSD based DP slaves and
fail-safe GSD based I/O devices
Requirement
In order to use fail-safe GSD based DP slaves for SIMATIC Safety, these GSD based slaves
must be operated on PROFIBUS DP and support the PROFIsafe bus profile. When used in
an S7-1200/1500 F-CPU, they must support the PROFIsafe bus profile in V2 mode.
Fail-safe GSD based DP slaves used in hybrid configurations on PROFIBUS DP and
PROFINET IO downstream from a IE/PB link must support the PROFIsafe bus profile in V2
mode.
In order to use fail-safe GSD based I/O devices for SIMATIC Safety, the GSD based devices
must be operated on PROFINET IO and support the PROFIsafe bus profile in V2 mode.
Configuration with GSD files
As is the case in a standard system, the basis for configuring fail-safe GSD based DP
slaves/IO devices is the device specification in the GSD file (device master file).
A GSD file contains all of the properties of a GSD based DP slave or GSD based I/O device.
For fail-safe GSD based DP slaves/GSD based I/O devices, certain parts are protected by a
CRC.
The GSD files are supplied by the device manufacturers.
Protection of the data structure of the device in GSD files
The only GSD files supported are those that satisfy the requirements for protection defined
as of
PROFIsafe Specification
V2.0 using a CRC stored in this file ("desired value" for
F_IO_StructureDescCRC).
The data structure described in the GSD file is checked when the F-I/O is added to the
hardware configuration and when the hardware configuration is compiled. When an error is
detected, you should clarify whether the GSD file provided by the device manufacturer
contains the desired value for F_IO_StructureDescCRC.
Configuring
2.14 Peculiarities when configuring fail-safe GSD based DP slaves and fail-safe GSD based I/O devices
SIMATIC Safety - Configuring and Programming
78 Programming and Operating Manual, 10/2018, A5E02714440-AH
Assignment and setting of the PROFIsafe address
WARNING
Check the documentation for your fail-safe GSD based DP slaves / GSD based I/O devices
to find out the valid PROFIsafe address type. If you do not find the necessary information,
assume PROFIsafe address type 1. Proceed as described under PROFIsafe addresses for
F-I/O of PROFIsafe address type 1 (Page 68) or PROFIsafe addresses for F-I/O of
PROFIsafe address type 2 (Page 70).
Set the F-source address for fail-safe DP standard slaves / fail-safe I/O standard devices
according to the manufacturer's specifications. If the F-source address needs to correspond
to the "Central F-source address" parameter of the F-CPU (PROFIsafe address type 2),
you will find the latter in the "Properties" tab of the F-CPU. In this case, also check in the
safety summary that the value of the F-CPU for the "Central F-source address" parameter
matches the value of the F-source address of the fail-safe GSD based DP slave / fail-safe
GSD based I/O device.
(S053)
Configuration procedure with GSD files
You import the GSD files to your project (see
Help on STEP 7 "GSD files"
).
1. Select the fail-safe GSD based DP slave / GSD based I/O device in the "Hardware
catalog" task card and connect it to the relevant subnet in the network view.
2. Select the fail-safe GSD based DP slave/GSD based I/O device and insert the necessary
F-modules, if this does not occur automatically.
3. Select the relevant F-module and open the "Properties" tab in the inspector window.
For fail-safe GSD based DP slaves/GSD based I/O devices (contrary to other F-I/O), the
"Manual assignment of the F-monitoring time" parameter is enabled. The result is that the
value specified in the GSD file for the F-monitoring time is used as default value when the
slaves/devices are plugged. You can change both values (time and type of assignment) later
manually.
Configuring
2.14 Peculiarities when configuring fail-safe GSD based DP slaves and fail-safe GSD based I/O devices
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 79
F-parameter "F_CRC_Seed" and "F_Passivation" for fail-safe GSD based I/O devices
The F-parameters "F_CRC_Seed" and "F_Passivation" influence the behavior of a fail-safe
GSD based I/O device. The combination of the F-parameters cannot be set but is specified
by selecting a corresponding F-module. Up to three F-module variants can be used,
depending on the S7-300/400 or S7-1200/1500 F-CPU used.
F-module
variant
F_CRC_Seed
F_Passivation
Behavior of the fail-safe GSD based I/O
device
Can be used with
F-CPU
1 Parameter does
not exist
Parameter does
not exist
The GSD based I/O device works with the
Basic Protocol (BP) from PROFIsafe.
The "RIOforFA-Safety" profile is not sup-
ported.
S7-
300/400/1200/1500*
2 CRC-Seed24/32 Device/module The GSD based I/O device works with the
Expanded Protocol (XP) from PROFIsafe.
The "RIOforFA-Safety" profile is not sup-
ported.
S7-1200/1500
3 CRC-Seed24/32 Channel The GSD based I/O device works with the
Expanded Protocol (XP) from PROFIsafe.
The "RIOforFA-Safety" profile is supported.
S7-1200/1500
* Only use the F-module variant 1 with S7-1200/1500 F-CPUs if neither F-module variant 2 nor 3 exists.
Additional information
You can find the description of the parameters in the Help on fail-safe GSD based DP slaves
and GSD based I/O devices.
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 81
Safety Administration Editor
3
Overview
The
Safety Administration Editor
supports you as follows:
Displaying of status of the safety program
Displaying of collective F-signature
(S7-1200, S7-1500) F-SW collective signature
(S7-1200, S7-1500) F-HW collective signature
Displaying of status of safety mode
Creating and organizing of F-runtime groups
Displaying information on the F-blocks
Displaying information about F-compliant PLC data types (UDT)
Information for users with F-Admin permission
Specifying/changing access protection
Set/modify settings for the safety program, e.g. Enable F-change history
(S7-1200, S7-1500) Create/display/delete F-communications via flexible F-Link
Safety Administration Editor
SIMATIC Safety - Configuring and Programming
82 Programming and Operating Manual, 10/2018, A5E02714440-AH
The
Safety Administration Editor
is divided into the following areas:
General
Under "General", the status of the safety mode, the safety program, the F-collective
signature and for F-CPUs S7-1200/1500 the F-SW collective signature and the F-HW
collective signature are displayed. Additional information on the "General" area can be
obtained in ""General" area (Page 83)".
F-runtime group
You define the blocks and properties of an F-runtime under "F-runtime group".
You can find information on F-runtime groups at ""F-runtime group" area (Page 86)".
F-blocks
Under "F-blocks", you can find information on the F-blocks used in your safety program
and their properties . Additional information on the "F-blocks" area can be obtained in
""F-blocks" area (Page 88)".
F-compliant PLC data types
Under "F-compliant PLC data types", you obtain information on the created F-compliant
PLC data types (UDT). There you also obtain information whether or not an F-compliant
PLC data type (UDT) is used in the safety program. Additional information on
"F-compliant PLC data types" can be found in ""F-compliant PLC data types" area
(S7-1200, S7-1500) (Page 89)".
Access protection
Under "Access protection", you can set up, change, or revoke the password for the safety
program. Access protection is mandatory for productive operation. Additional information
on access protection can be found in "Access protection for the safety program
(Page 103)".
Web server F-Admins
Under "Web server F-admins", you obtain information on users with the F-Admin attribute
for the Web server of the F-CPU. Additional information on the "Web server F-Admins"
area can be obtained in "Web server F-Admins” area (S7-1200, S7-1500) (Page 90)".
Settings
Under "Settings", you set the parameters for the safety program. Information on the
settings for your safety program can be found in ""Settings" area (Page 90)".
Flexible F-Link
In the "Flexible F-Link" area, you receive information about the configured
F-communications via Flexible F-Links in tabular form. You can obtain information at
""Flexible F-Link" area (S7-1200, S7-1500) (Page 96)".
See also
Program structure of the safety program (S7-1200, S7-1500) (Page 114)
Program structure of the safety program (S7-300, S7-400) (Page 111)
Defining F-Runtime Groups (Page 132)
Safety Administration Editor
3.1 Opening the Safety Administration Editor
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 83
3.1
Opening the Safety Administration Editor
Requirement
The
Safety Administration Editor
is visible as an element in the project tree, if you have
configured a CPU as an F-CPU in the project, which means the "F-capability activated"
option must be selected (in the properties of the F-CPU).
Procedure
To open the
Safety Administration Editor
, follow these steps:
1. Open the folder for your F-CPU in the project tree.
2. Double-click on "Safety administration" or right-click and select the corresponding
shortcut menu for the
Safety Administration Editor
.
Result
The
Safety Administration Editor
for your F-CPU opens in the work area.
3.2
"General" area
"Safety mode status"
The "Safety mode status" shows the current status of safety mode. The prerequisite is an
existing online connection to the selected F-CPU.
The following statuses are possible:
"Safety mode is activated"
"The safety mode is not activated"
"F-CPU is in STOP"
"No active F-CPU available"
"F-runtime group was not called"
"The safety program is not called"
"(No online connection)"
"Disable safety mode"
For existing online connection and active safety mode operation, you have the option of
using the "Disable safety mode" button to disable safety mode for the selected F-CPU.
Safety mode can be deactivated only for the entire safety program and not for individual F-
runtime groups.
Requirement:
"Safety mode can be disabled" is selected in the "Settings" area.
Safety Administration Editor
3.2 "General" area
SIMATIC Safety - Configuring and Programming
84 Programming and Operating Manual, 10/2018, A5E02714440-AH
Proceed as follows:
1. Click the "Disable safety mode" button.
2. Enter the password for the safety program in the dialog window and confirm with "OK".
3. A corresponding dialog will display the collective F-signature.
4. Using the displayed collective F-signature, verify that you have selected the desired F-
CPU.
5. If you have selected the correct F-CPU, confirm the dialog with "Yes".
Result:
Safety mode for the F-CPU is disabled.
"Safety program status"
"Safety program status" displays the current status of your online and offline program.
The following statuses are possible:
Consistent (with information if no password has been assigned.)
Inconsistent
Modified
If no connection to the online program could been established, the message "(no online
connection) " will be shown.
"F-signatures"
For a non-existing online connection
Under "F-signatures" multiple signatures are displayed. Each signature is formed from
different parts of the fail-safe project data.
F-collective signature: This signature changes with each change of the fail-safe project
data. It contains the signatures described below.
F-SW collective signature (S7-1200/1500): This signature changes with each change of
the safety program.
F-HW collective signature (S7-1200/1500): This signature changes with each change of
the fail-safe HW configuration.
F-communication address signature (S7-1200/1500): This signature changes with each
change of the name or the F-communication UUID of communication connections with
flexible F-link.
The time of the last compilation process is displayed for the F-collective signature in the
"Time stamp" column.
Safety Administration Editor
3.2 "General" area
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 85
For an existing online connection
For an existing online connection, the following is displayed under the "Program signature":
The status of safety program
Status
Meaning
The online and offline collective F-signatures match, and a password was assigned for
the online and offline safety programs.
The online and offline collective F-signatures do
not
match or no password was as-
signed for one of the safety programs.
The safety program status could not be determined.
The online and offline collective F-signatures
When the collective F-signatures match: Information on whether the F-block versions are
consistent online and offline.
Status
Version com-
parison
Statement
Not relevant The online and offline collective F-signatures
do not
match one
another.
The online and offline collective F-signatures match, but the online
versions of F-blocks differ from the offline versions.
The online and offline F-collective signatures match, identical ver-
sions of F-blocks are being used online and offline.
Not rele-
vant
The safety system versions could not be determined.
You can find additional information on the consistency of the online safety program at under
Identity of online and offline program (Page 375).
See also
Disabling safety mode (Page 344)
Program identification (Page 337)
Safety Administration Editor
3.3 "F-runtime group" area
SIMATIC Safety - Configuring and Programming
86 Programming and Operating Manual, 10/2018, A5E02714440-AH
3.3
"F-runtime group" area
3.3.1
"F-runtime group" area
A safety program consists of one or two F-runtime groups.
General information on F-runtime groups can be found in "Program structure of the safety
program (S7-300, S7-400) (Page 111)" and "Program structure of the safety program (S7-
1200, S7-1500) (Page 114)".
You can find information on creating F-runtime groups at Defining F-Runtime Groups
(Page 132)
(S7-1200, S7-1500) "Creating a global F-I/O status block"
You can create a standard block (FB) with the name "RTGx_GLOB_FIO_STATUS", which
evaluates whether substitute values are output instead of process values for at least one F-
I/O or at least one channel of an F-I/O of an F-runtime group x. The result of the evaluation is
available at the "QSTATUS" output. The F-O that you have disabled with the DISABLE
variable in the F-I/O DB are then ignored.
The "RIOforFA_VALUE_STATUS" output corresponds to the "QSTATUS" output, but only
takes F-I/Os into account with the "RIOforFA-Safety" profile.
To generate this standard FB, you use the "Create global F-I/O status block" button. You can
only create the standard FB when your safety program has been compiled. You can call the
standard FB anywhere in your standard user program.
Note
When adding or deleting an F
-I/O, you have to generate "RTGx_GLOB_FIO_STATUS"
again.
See also
Process Data or Fail-Safe Values (Page 162)
Safety Administration Editor
3.3 "F-runtime group" area
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 87
3.3.2
Pre-/postprocessing (S7-1200, S7-1500)
With preprocessing and postprocessing you have the option of calling standard blocks (FCs)
directly before or after an F-runtime group, for example for data transfer with fail-safe
communication via Flexible F-Link (Page 262).
Requirement
Only standard-FCs usable.
Only temporary local data and constants are permitted in the block interface of a
standard-FC.
Procedure
1. Create the standard-FCs for the preprocessing and the postprocessing.
2. Assign the standard-FCs in the Safety Administration Editor under "Pre-/postprocessing
of the F-runtime group".
Note
When you delete an assigned FC or overwrite it by copying, its selection as a pre
-
processing / post
-processing block is automatically reset.
Effect on the safety program
The runtime of the F-runtime group is extended by the runtime of the standard FCs for
pre-/postprocessing (influence on TRTG_CURR and TRTG_LONG in the F-runtime group
information DB).
Because the preprocessing / postprocessing does not change the functionality of the
safety program, the F-collective signature remains unchanged after compilation.
Load behavior
The calls of the selected standard FCs are placed during compiling or after the call of the
main safety block in the F-OB.
This means that the STOP operating state is required during a subsequent download.
Changes in the contents at the selected standard FCs can take place in RUN.
Exceptions are changes of the block name and block numbers which also include the
compilation of the safety program.
When a preprocessing/postprocessing block is uploaded individually by the F-CPU, it does
not automatically connect to the F-runtime group in the Safety Administration Editor.
If consistent loading of the F-CPU is performed instead, the settings for preprocessing and
postprocessing are updated according to the online CPU.
Safety Administration Editor
3.4 "F-blocks" area
SIMATIC Safety - Configuring and Programming
88 Programming and Operating Manual, 10/2018, A5E02714440-AH
3.4
"F-blocks" area
Overview
The "F-Blocks" area helps you in the following tasks:
Displaying the F-blocks used in your safety programs.
Displaying the F-blocks used in the F-runtime groups.
Displaying additional information about the F-blocks.
A description of the F-blocks is available in "Creating F-blocks in FBD / LAD (Page 151)".
Displayed information
The following information is displayed for F-blocks in offline mode:
Has the F-block been compiled and used?
Function of F-block in the safety program
Block signature
Time stamp of the last change
The following information is displayed for F-blocks in online mode:
Status (whether block has the same time stamp online and offline)
Function of F-block in the safety program
Block signature of the block offline
Block signature of the block online
The F-blocks are hierarchically displayed as in the "Program blocks" folder.
The description of the symbols in the "Status" column can be found in "Comparing Safety
Programs (Page 339)".
Note
During the offline
-online comparison, the comparison statuses may occasionally differ
between the
comparison editor
and status display in the
Safety Administration Editor
. The
decisive status is the result of the comparison in the
comparison editor
, since this is the only
comparison that takes into account the contents of the F
-blocks.
Safety Administration Editor
3.5 "F-compliant PLC data types" area (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 89
Filter function
Using the filter function, you can select whether you want to view all F-blocks of a certain F-
runtime group or the entire safety program.
Select "All F-blocks " from the drop-down list to view all F-blocks.
Select an F-runtime group from the drop-down list to see all F-blocks of this F-runtime
group.
3.5
"F-compliant PLC data types" area (S7-1200, S7-1500)
Overview
Under "F-compliant PLC Data Types" you obtain information on the F-compliant PLC data
types (UDT) you have defined.
You can delete F-compliant PLC data types (UDT) from the shortcut menu.
A description of F-compliant PLC data types (UDT) is available in "F-compliant PLC data
types (UDT) (S7-1200, S7-1500) (Page 126)".
Displayed information
The following information is displayed for F-compliant PLC data types (UDT) in offline mode:
Is the F-compliant PLC data type used in the safety program?
Time stamp of the last change.
The following information is displayed for F-compliant PLC data types (UDT) in online mode:
Status (whether the F-compliant PLC data types (UDT) have the same time stamp online
and offline)
The F-compliant PLC data types (UDT) are displayed hierarchically as in the folder "PLC
Data Types".
Double-click the F-compliant PLC data type (UDT) to open it for editing.
The description of the symbols in the "Status" column can be found in "Comparing Safety
Programs (Page 339)".
Note
During offline
-online comparison, the comparison statuses between the
comparison editor
and status display in the
Safety Administration Editor
can be different under certain
circumstances. The comparison result in the
comparison editor
is decisive, since this is the
only comparison that takes into account the contents of the F
-compliant PLC data types
(UDT).
Safety Administration Editor
3.6 “Web server F-Admins” area (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
90 Programming and Operating Manual, 10/2018, A5E02714440-AH
3.6
“Web server F-Admins” area (S7-1200, S7-1500)
You require the "F-admin" right in order to carry out restoration of a backup (Page 328) via
the Web server of your F-CPU. You assign the "F-admin" right in the hardware configuration
of the F-CPU under the user management of the Web server.
In this section, you obtain information on which users have the "F-admin" right online or
offline for F-CPUs that support this right. You can see from this whether a change to the
"F-admin" right is active on the F-CPU. In order to make a change to the "F-admin" right
effective, you have to load the configuration to the F-CPU.
See also
Completeness and correctness of the hardware configuration (Page 368)
3.7
"Settings" area
"Number ranges of the generated F-system blocks"
The number ranges assigned here are used by the F-System for new, automatically
generated F-blocks.
At this point, you can select whether the number ranges are managed by the F-system or if a
fixed range specified by you is used.
"F-system managed"
The number ranges are managed automatically by the F-system, depending on the
F-CPU used. The F-system selects an available number range. The start and end ranges
of the number ranges are displayed.
"Fixed range"
You can select the start and end ranges of the number ranges from the available range.
The available range depends on the F-CPU used.
An invalid number range selection is indicated by an error message.
The only check performed during configuration is whether the configured low limit is less
than or equal to the high limit and within the available range of the F-CPU. The check as
to whether the configured range is sufficient is first made during compiling. You need to
ensure a sufficiently large range. Where the available range is insufficient, a compiling
error occurs. Not all blocks are generated and the safety program is not executable.
Changes will become valid only during the next compilation. The automatically created F-
blocks may be moved into the new area during compilation. The F-I/O DBs are an exception.
They always retain their original number that you may change in the properties of the F-I/O.
Safety Administration Editor
3.7 "Settings" area
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 91
"Safety system version"
This parameter is used to specify the safety system version (including version of the
F-system blocks and automatically generated F-blocks, see Overview of Programming
(Page 111)).
A number of versions are available:
Ver-
sion3
S7-300/400
S7-1200
S7-1500
Function
1.6
x
x
These versions have identical functions.
Depending on the set version, the result may be different runtimes of the
F-runtime group(s) (see Excel file for response time calculation on the
Internet
(http://support.automation.siemens.com/WW/view/en/49368678/133100
)).
2.0 x x1 x2
2.1 x1 x2 Additionally supports the variables "DISABLE" and "DISABLED" in the
F-I/O DB
2.2 x1 x2 Supports the safety-related CPU-CPU communication and F-runtime
group communication with Flexible F-Link.
1
supported for Firmware version V4.2 or higher
2
supported for Firmware version V2.0 or higher
3
After the migration of projects that were created with
S7 Distributed Safety V5.4 SP5
, version 1.0 is set automatically in
order to identify migrated projects which have not yet been compiled with
STEP 7 Safety Advanced
.
Usually, you do not need to make any settings for this parameters.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the
F-CPU created is automatically preset.
"Local data used in safety program" (S7-300, S7-400)
You use this parameter to specify the amount of temporary local data (in bytes) that is
available for the call hierarchy below the main safety block.
The setting applies to each F-runtime group of a safety program. Additional information on
F-runtime groups can be found in "Program structure of the safety program (S7-1200,
S7-1500) (Page 114)" and "Program structure of the safety program (S7-300, S7-400)
(Page 111)".
The
minimum possible amount
is determined by the local data requirement of the F-blocks
generated automatically when the safety program is compiled.
For this reason, you must provide at least 440 bytes. However, the local data requirement for
the automatically added F-blocks may be higher depending on the local data requirement of
the F-blocks you created with FBD or LAD.
Therefore, provide as much local data as possible. If there is not enough local data available
for the automatically added F-blocks (440 bytes or more), the safety program will be
compiled nevertheless.
Safety Administration Editor
3.7 "Settings" area
SIMATIC Safety - Configuring and Programming
92 Programming and Operating Manual, 10/2018, A5E02714440-AH
Data in automatically added F-DBs are then used instead of local data. However, this
increases the runtime of the F-runtime group(s). You will receive a notice when the
automatically added F-blocks require more local data than configured.
WARNING
The calculated maximum runtime of the F-runtime group using the Excel file for response
time calculation (http://support.automation.siemens.com/WW/view/en/49368678/133100) is
no longer correct in this case because the calculation assumes sufficient availability of F-
local data.
In this case, use the value you configured for the maximum cycle time of the F-runtime
group (F-monitoring time) as the maximum runtime of the F-runtime group when calculating
the maximum response times in the event of an error and for any runtimes of the standard
system using the above-mentioned Excel file.
(S004)
The maximum possible amount depends on:
Local data requirement of the main safety block and the higher-level standard user
program. For this reason, you should call the main safety blocks directly in OBs (cyclic
interrupt OBs, whenever possible), and additional local data should not be declared in
these cyclic interrupt OBs.
Maximum volume of local data of the utilized F-CPU (see Technical Specifications in the
product information for the utilized F-CPU). For S7-400 F-CPUs, you can configure the
local data for each priority class. Therefore, assign the largest possible local data volume
for the priority classes in which the safety program (the main safety blocks) is called (e.g.,
OB 35).
Safety Administration Editor
3.7 "Settings" area
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 93
Maximum possible amount of local data as a function of local data requirement of main safety block
and higher-level standard user program (S7-300, S7-400):
Case 1: Main safety block called directly from OBs
Set the "Local data used in safety program" parameter to the maximum amount of local data
of the utilized F-CPU minus the local data requirement of the main safety block (if the main
safety block has 2 F-runtime groups, use the largest local data requirement) and minus the
local data requirement of the calling OBx (if there are 2 F-runtime groups, use the OB with
the largest local data requirement).
Note:
If you have not declared any temporary local data in the main safety blocks and calling
OBx, the local data requirement of the main safety blocks is 6 bytes and the local data
requirement of the calling OBx is 26 bytes. You can derive the local data requirement of the
main safety blocks and calling OBx from the program structure.
Select the utilized F-CPU in the project tree and then "Tools > Call structure". The table
gives the local data requirement in the path or for the individual blocks (see also the help on
STEP 7
).
Safety Administration Editor
3.7 "Settings" area
SIMATIC Safety - Configuring and Programming
94 Programming and Operating Manual, 10/2018, A5E02714440-AH
Case 2: Main safety block not called directly from OBs
Set the "Local data settings" parameter to the value calculated for Case 1, minus the local
data requirement of standard user program A (if standard user program A has 2 F-runtime
groups, use the largest local data requirement).
Note:
You can derive the local data requirement of the standard user program A from the
program structure.
Select the utilized F-CPU in the project tree and then "Tools > Call structure". The table
gives the local data requirement in the path or for the individual blocks (see also the help on
STEP 7
).
"Advanced settings"
"Safety mode can be disabled"
If you deselect the "Safety mode can be disabled" option, you can prevent the disabling of
safety mode for a safety program.
When you change the setting for this option, you need to recompile the safety program and
download it to the F-CPU for the change to become effective. This changes the F-collective
signature and the F-SW collective signature of your safety program.
We recommend that you disable this option before you start production and before
acceptance of the safety program to prevent an unintentional disabling of the safety mode.
"Enable F-change history"
Enable the logging of changes to the safety program by using the "Enable F-change history"
option. For more information, refer to the section "F-change history (Page 359)".
Safety Administration Editor
3.7 "Settings" area
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 95
"Enable consistent upload from the F-CPU" (S7-1500)
This option allows you to load the loaded project data (including safety-related project data)
consistently from the F-CPU.
The option can only be activated if the F-CPU and the firmware of the F-CPU supports the
loading of the project data (including safety-related project data).
F-CPUs S7-1500 as of firmware V2.1 are supported. S7-1500 F Software Controllers are not
supported.
At every change to this option you have to load the project data to the F-CPU.
Note that the activation of this option extends the loading of the safety-related project data
into the F-CPU.
"Activate variable F-communication- IDs" (S7-1200, S7-1500)
If you activate this option, you can supply the DP_DP_ID input of the SENDP or RCVSP
instructions with the variable values from a global F-DB.
WARNING
The value for the respective F-communication ID (input DP_DP_ID; data type: INT) can be
freely selected**; however, it must be unique for all safety-related communication
connections network-wide* and CPU-wide at all times. The uniqueness must be checked in
the safety summary during acceptance of the safety program. You can find additional
information in Correctness and completeness of the communication configuration
(Page 374).
You must supply constant values*** to the inputs DP_DP_ID and LADDR when calling the
instruction. Direct write accesses in the associated instance DB to DP_DP_ID and LADDR
are not permitted in the safety program!
(S016)
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet. In PROFIBUS a network includes all the nodes accessible via PROFIBUS DP.
In PROFINET IO, a network includes all the nodes accessible via RT_Class_1/2/3
(Ethernet/WLAN/Bluetooth, Layer 2) and, if applicable, RT_Class_UDP (IP, Layer 3).
** S7-1200/1500: As of version V3.0 of the SENDDP and RCVDP instructions, no connection
is established at the DP_DP_ID input for a F-communication ID "0".
*** S7-1200/1500: As of version V3.0 of the SENDDP and RCVDP instructions, the
DP_DP_ID input can also be supplied with variable values from a global F-DB. In this case
as well you have to check during the acceptance of the safety program that the uniqueness
is ensured
at every moment
, by checking the algorithm for the creation of the variable value
accordingly. If you cannot ensure a unique F-communication ID during startup of the safety
program, because it is only specified after startup of the safety program, you must ensure
that the value at the DP_DP_ID input is "0" during this phase.
Safety Administration Editor
3.8 "Flexible F-Link" area (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
96 Programming and Operating Manual, 10/2018, A5E02714440-AH
"System-generated objects" (S7-1200, S7-1500)
"Creates driver I-DBs without prefix"
When you select this option, the I-DBs of the F-I/O DBs are created without prefix.
Naming scheme:
Default: F{logical address(5-digit)}_{module_name}
With activated option: {module_name}
Uniqueness:
The driver I-DB names assigned by the system must not be used for other blocks any
longer. A compilation error is output in case of identical block names.
If the option is selected, all module names must be unique in their first 124 characters.
This is the maximum length of a block name. All additional characters of the module
name are cut off.
"Debug"
The "Debug" button is provided for service and support purposes.
3.8
"Flexible F-Link" area (S7-1200, S7-1500)
In the "Flexible F-Link" area, you create new F-communications, obtain information on
existing F-communications and delete F-communications.
Requirement
S7-1500 F-CPUs as of firmware V2.0
S7-1200 F-CPUs as of firmware V4.2
Safety system version as of V2.2
Information on created F-communications
In the "Flexible F-Link" area, you receive information on configured F-communications in
tabular form:
CPU-wide unique name of F-communication
F-compliant PLC data type (UDT) for send/receive data
Direction of F-communication: Transmitting/receiving
F-monitoring time of F-communication
F-Communication UUID
Tag for send data
Tag for receive data
Safety Administration Editor
3.8 "Flexible F-Link" area (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 97
Creating F-communication
1. In an empty row of the table click "<Add new>"
2. Assign a name to the communication connection.
3. Select an F-compliant PLC data type (UUID) for the communication connection.
If you have not yet created an F-compliant PLC data type (UDT) for the communication
connection or wish to create a new one, create a new F-compliant PLC data type (UDT)
(Page 126) with any structure. Note that the size can be a up to 100 bytes.
4. Select the direction of the communication connection ("Send" or "Receive").
5. Select the F-monitoring time of the communication connection (Page 608).
The UUID of the F-communication is displayed via Flexible F-Link in the "F communication
UUID" column. The F-communication UUID ensures sufficient uniqueness of the safety-
related communication ID even across network limits.
The "Tag for send data" column shows you the newly created tag for send data of the
F-communication DB.
The "Tag for receive data" column shows you the newly created tag for receive data of the
F-communication DB.
You can find the newly created F-communication DB for this F-communication under
"Program blocks\System blocks\STEP 7 Safety\F-communication DBs".
Deleting F-communication
1. Select the entire row and confirm "Delete" in the shortcut menu. You can also delete
multiple F-communications at the same time.
Copying F-communication
1. Select the entire row and confirm "Copy" in the shortcut menu. You can also copy
multiple F-communications at the same time.
2. With the "Paste" menu command, you can paste the copied F-communications into the
table as often as needed. The UUID for the respective F-communication is retained
during copying. If necessary, re-generate the UUID.
Generating a new F-communication-UUID
1. Select the entire row and confirm "Generate UUID" in the shortcut menu. You can also
generate multiple UUIDs at the same time.
Safety Administration Editor
3.8 "Flexible F-Link" area (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
98 Programming and Operating Manual, 10/2018, A5E02714440-AH
Interface of the F-communication DB for sending
The following table shows you the interface of the F-communication DB for the
communication connection with the direction "Send":
Section
Name
Data type
Initial value
Description
Input SEND_DATA F-compliant PLC data
type (UDT)
As in the F-compliant
PLC data type (UDT).
User data to be sent:
ACK_RCV_ARRAY Array[0..n] of Byte Each element with
16#0
Array with the received raw data.
Output ERROR BOOL False Signals currently pending com-
munication errors or communica-
tion errors not acknowledged yet
at the receiver (not in the initial
start).
1=Communication error
ACTIVATE_FV BOOL True Communication passivated, in the
initial start (for example receiver
not started), or HOST sends
ACTIVATE_FV. DEVICE sends
status bit: FV_ACTVATED, but no
0-values.
1=The communication uses fail-
safe values
DIAG Byte 16#0 Error bits (Timeout or CRC error
currently still pending, or commu-
nication after error not depassiv-
ated yet)
Bit 3: Acknowledgement request
active at the receiver
Bit 4: Timeout detected
Bit 6: CRC error detected
SEND_ARRAY Array[0..n] of Byte Each element with
16#0
Array with the received raw data
ACK_RCV_LENGTH UInt 0 Length information to
ACK_RCV_ARRAY in bytes
SEND_LENGTH UInt 0 Length information to
SEND_ARRAY in bytes
InOut
Static
Safety Administration Editor
3.8 "Flexible F-Link" area (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 99
Interface of the F-communication DB for receiving
The following table shows you the interface of the F-communication DB for the
communication connection with the direction "Receive":
Section
Name
Data type
Initial value
Description
Input PASS_ON BOOL False This way you can passivate the
output data (output of the pas-
sivation values)
1=Enable passivation
ACK_REI BOOL False Reintegration (in case of reinte-
gration request) by means of
positive edge
1=Acknowledgment for reintegra-
tion
RCV_ARRAY Array[0..n] of Byte Each element with
16#0
Array with the received raw data
Output RCV_DATA F-compliant PLC data
type (UDT)
As in the F-compliant
PLC data type (UDT).
Output data (PASS_VALUES or
data received).
ERROR BOOL False Signals currently pending com-
munication errors or communica-
tion errors not acknowledged yet
(not in the initial start).
1=Communication error
PASS_OUT BOOL True At PASS_OUT=1 the
PASS_VALUES are output
Could be: ERROR, PASS_ON, in
the initial start (e.g. sender not
started), or ACK_REQ is pending
(error not acknowledged)
ACK_REQ BOOL False Reintegration requirement (com-
munication stable again after
error, substitute values are still
output)
1=Acknowledgment request for
reintegration
SENDMODE BOOL False MOD_MODE is active or commu-
nication with PLCSIM Advanced
on the sending F-CPU
1=F-CPU with a sender in the
deactivated safety operation or on
a simulated CPU
Safety Administration Editor
3.8 "Flexible F-Link" area (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
100 Programming and Operating Manual, 10/2018, A5E02714440-AH
Section
Name
Data type
Initial value
Description
DIAG Byte 16#0 Error bits (Timeout or CRC error)
Bit 0: Timeout detected by the
sender
Bit 1: Communication error cur-
rently pending in the sender
Bit 2: CRC error detected by the
sender
Bit 4: Timeout detected by the
receiver
Bit 6: CRC error detected by the
receiver
ACK_SEND_ARRAY Array[0..n] of Byte Each element with
16#0
Array with the raw data to be
sent.
RCV_LENGTH UInt 0 Length information of
RCV_ARRAY in bytes
ACK_SEND_LENGTH
UInt 0 Length information of
ACK_SEND_ARRAY in bytes
InOut
Static PASS_VALUES F-compliant PLC data
type (UDT)
Same as the F-
compliant PLC data
type (UDT) or in the
I/O DB
Passivation or substitute values
See also
Flexible F-Link (Page 262)
F-runtime group communication (S7-1200, S7-1500) (Page 145)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 101
Access protection
4
Access protection is necessary for productive operation
Access protection to the SIMATIC Safety F-system is mandatory for productive operation.
No access protection is initially necessary for test purposes, commissioning, etc. This means
you can execute all offline and online actions without access protection, i.e., without
password prompt.
WARNING
Access to the SIMATIC Safety F-system without access protection is intended for test
purposes, commissioning, etc., when the system is not in productive operation. You must
guarantee the safety of the system through other organizational measures, for example,
restricted access to certain areas.
Before you transition into productive operation, you must have set up and activated access
protection.
(S005)
4.1
Overview of access protection
Introduction
You can protect access to the SIMATIC Safety F-system by two password prompts: one for
the safety program and another for the F-CPU.
Password for the safety program
The password for the safety program is available in two forms:
The offline password is part of the safety program in the offline project on the
programming device or PC.
The online password is part of the safety program in the F-CPU.
Password for the F-CPU
The access protection is set at the F-CPU level. This password is also used to identify the
F-CPU and must therefore be unique network-wide.
Access protection
4.1 Overview of access protection
SIMATIC Safety - Configuring and Programming
102 Programming and Operating Manual, 10/2018, A5E02714440-AH
Overview of password assignment and prompt
The following table provides an overview of the access permissions for the F-CPU and the
safety program.
The sections below show you how to assign the passwords and how to set up, change, and
cancel access permissions for the F-CPU and the safety program.
Password for F-CPU
Password for safety program
Assign-
ment
In the
hardware and network editor
, during configu-
ration of the F-CPU, inspector window, in "Settings"
tab under "Protection", corresponding safety level,
e.g., "Write protection for fail-safe blocks" (S7-300,
S7-400).
Select at least the access level "Full access (no
protection)" for S7-1200/1500 F-CPUs and assign a
password for "Full access incl. fail-safe (no protec-
tion)".
If you select a higher protection level, for example
to protect the standard user program, you must
assign an additional password for "Full access (no
protection)".
In the
Safety Administration Editor
under "Access Pro-
tection".
Prompt
If you do not have access permission for the safety
program (Page 103):
For example
When uploading the complete safety program to
the F-CPU
(S7-300, S7-400) when uploading the hardware
configuration to the F-CPU
(S7-1200, S7-1500) when uploading a hardware
configuration to the F-CPU that contains safety-
related changes
When PROFIsafe address is assigned
When F-blocks that are used in the safety pro-
gram are downloaded and deleted
When disabling safety mode
When restoring a backup of the F-CPU.
Exception with S7-1200/1500 F-CPUs: If neither
the safety program nor the F-CPU password is
changed by the restore process, you are not
prompted for the F-CPU password.
If you have assigned a password and this has not yet
been entered since the project was opened, or you do
not have access permission for the safety program
(Page 103):
Offline password
e.g.:
When the password is changed
When modifying the safety program
When changing and deleting F-runtime groups
When changing safety-related parameters of F-I/O
Online password
e.g., when disabling safety mode (the password must
always be entered, even if access permission for the
safety program is still valid)
Safety program recompilation is required after changes to standard DBs to which the safety
program has read or write access (Page 195). These standard DBs are not governed by the
safety program access protection.
Please note that you also require the online password to download the safety-relevant
changes to the hardware configuration. This is also true for changes to F-I/O not used in the
safety program.
You have to also recompile and download the safety program for the download to be
consistent.
Access protection
4.2 Access protection for the safety program
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 103
4.2
Access protection for the safety program
Setting up access protection for the safety program
To set up access protection for the safety program, assign a password for the safety
program. Proceed as follows:
1. Open the folder for your F-CPU in the project tree.
2. Select "Safety Administration" and select "Go to access protection" in the shortcut menu.
Alternatively, double-click on "Safety Administration". The
Safety Administration Editor
of
the F-CPU will open. Select "Access protection" in the area navigation.
3. Under "Offline safety program protection", click "Setup" and enter the password (max. 30
characters) for the safety program in the following dialog in the "New password" and
"Confirm password" fields.
4. Confirm the assigned password with "OK".
You have set up access protection for the safety program and have gained access
permission for the safety program.
Note
You cannot define the online password separately; the offline password assigned during the
next download is applied. After a change to the offline password, the online and offline
passwords may differ until the next time the offline safety p
rogram is downloaded to the
F
-CPU.
During loading from the device the offline password is replaced by the online password or
deleted.
Note
Use different passwords for the F
-CPU and the safety program to optimize access
protection.
WARNING
If access protection is not used to limit access to the programming device or PC to only
those persons who are authorized to modify the safety program, the following
organizational measures must be taken to ensure the effectiveness of the password
protection for the F-CPU at the programming device or PC:
Only authorized personnel may have access to the password.
Authorized personnel must explicitly cancel the access permission for the F-CPU before
leaving the programming device or PC by closing
STEP 7
or via the "Online > Delete
access rights" menu. If this is not strictly implemented, a screen saver equipped with a
password accessible only to authorized personnel must also be used.
(S006)
Access protection
4.2 Access protection for the safety program
SIMATIC Safety - Configuring and Programming
104 Programming and Operating Manual, 10/2018, A5E02714440-AH
Changing the password for the safety program
You may change the safety program password as long as you have the necessary access
permissions. It takes place likewise in the "Access protection" area (via "Change" button)
and is carried out as usual under Windows through entry of the old and double entry of the
new password.
Deleting access protection for the safety program
To delete access protection for the safety program, delete the password for the safety
program. Proceed as follows:
1. Open the folder for your F-CPU in the project tree.
2. Select "Safety Administration" and select "Go to access protection" in the shortcut menu.
Alternatively, double-click on "Safety Administration". The
Safety Administration Editor
of
the F-CPU will open.
3. Select "Access protection" in the area navigation.
4. Click the "Change" button.
5. Under "Old password", enter the password for the safety program.
6. Click "Revoke" and then on "OK".
Gaining access permission through login to the safety program
Log in to the safety program as follows:
1. Open the folder for your F-CPU in the project tree.
2. Select "Safety Administration" and select "Go to access protection" in the shortcut menu.
Alternatively, double-click on "Safety Administration". The
Safety Administration Editor
of
the F-CPU will open.
3. Select "Access protection" in the area navigation.
4. Enter the password for the safety program in the "Password" input field.
5. Select the "Login" button.
Validity of access permission for a safety program
If access permission for a safety program was obtained through the entry of the password,
this remains until the project is closed. If
STEP 7
is closed, any project that is still open is
automatically closed and any access permission granted is canceled.
Access protection
4.2 Access protection for the safety program
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 105
Canceling access permission through logoff
The access permission for the safety program can be canceled as follows:
By clicking the "Log off" button in the "Access protection" area in the "
Safety
Administration Editor
".
In the shortcut menu for the
Safety Administration Editor
shortcut menu (access by right-
clicking).
By using the lock symbol in the line of the
Safety Administration Editor
.
The user will then be prompted to enter the password for the safety program again the next
time an action requiring a password is performed. A Stop-Run transition is required to
"revoke" access permission for control.
Access permission for the safety program is canceled automatically, if the project or
STEP 7
has been closed.
Displaying the validity of access permission
The validity of the access permission is displayed in the project tree as follows:
The access permission is valid, if the lock symbol in the line of the
Safety Administration
Editor
is shown unlocked.
The access permission is not available, if the lock symbol shows a closed lock.
If no lock symbol is shown, no password was assigned.
Access protection
4.3 Access protection for the F-CPU
SIMATIC Safety - Configuring and Programming
106 Programming and Operating Manual, 10/2018, A5E02714440-AH
4.3
Access protection for the F-CPU
Setting up access protection for the F-CPU
To set up access protection for the F-CPU, assign a password for the F-CPU in the F-CPU
configuration.
You arrive there directly, if you click the link "Go to the "Protection" area of the F-CPU" in the
"Access protection" area in the
Safety Administration Editor
. Proceed as described in the
STEP 7
help under "Configuring access levels".
WARNING
(S7-300, S7-400) In safety mode, access with the CPU password must not be authorized
during changes to the standard user program as this would also allow changes to the safety
program. To rule out this possibility, you must configure the protection level "Write
protection for fail-safe blocks" and configure a password for the F-CPU. If only one person
is authorized to change the standard user program and
the safety program, the protection
level "Write protection" or "Read/write protection" should be configured so that other
persons have only limited access or no access at all to the entire user program (standard
and safety programs).
(S001)
WARNING
(S7-1200, S7-1500) In safety mode, the safety program must be password-protected. For
this purpose, configure at least the protection level "Full access (no protection)" and assign
a password under "Full access incl. fail-safe (no protection)". This protection level only
allows full access to the standard user program, not to F-blocks.
If you select a higher protection level, for example to protect the standard user program,
you must assign an additional password for "Full access (no protection)".
Assign different passwords for the individual protection levels.
(S041)
Access protection
4.3 Access protection for the F-CPU
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 107
You enable access protection by downloading (Page 313) the hardware configuration to the
F-CPU.
WARNING
If
multiple F-CPUs
can be reached over a network (e.g. Industrial Ethernet) by
one
programming device or PC
, you must take the following actions to ensure that the project
data is downloaded to the correct F-CPU:
Use passwords specific to each F-CPU, such as a uniform password for the F-CPUs with
attached Ethernet address for each.
Note the following:
A point-to-point connection must be used to activate the access protection of an F-CPU
when the hardware configuration is loaded for the first time (similar to assigning an MPI
address to an F-CPU for the first time).
Before downloading the safety program to an F-CPU, you must first revoke an existing
access permission for any other F-CPU.
The last download of the safety program prior to switching to productive operation must
be made with enabled access protection.
(S021)
WARNING
When using tools for the automation or operation (of TIA Portal or Web server) which allow
access protection for the F-CPU to be bypassed (e.g. saving or automatic entry of a CPU
password for the protection level "Full access incl. fail-safe (no protection)" or Web server
password), the safety relevant project data may not be protected against unintentional
changes anymore.
(S078)
Changing the password for the F-CPU
For the new password to become valid after a password change for the F-CPU, you must
download the changed configuration into the F-CPU. If necessary, you must enter the "old"
password for the F-CPU for this load operation. The F-CPU must be in STOP mode.
Deleting access protection for the F-CPU
To delete access protection for the F-CPU, delete the password for the F-CPU. To do this,
proceed as in the standard.
Obtaining access permission for the F-CPU
You obtain access permission for the F-CPU - depending on the configured protection level -
by entering the password for the F-CPU prior to performing an action requiring a password.
Access protection
4.3 Access protection for the F-CPU
SIMATIC Safety - Configuring and Programming
108 Programming and Operating Manual, 10/2018, A5E02714440-AH
Obtaining access permission for the F-CPU
Access permission for the F-CPU remains valid until the project is closed in
STEP 7
or
access permission is canceled.
Canceling access permission for the F-CPU
You cancel the access permission with the menu command "Online > Delete access rights"
auf.
WARNING
If access protection is not used to limit access to the programming device or PC to only
those persons who are authorized to modify the safety program, the following
organizational me
asures must be taken to ensure the effectiveness of the access protection
for the F-CPU at the programming device or PC:
Only authorized personnel may have access to the password.
Authorized personnel must explicitly cancel the access permission for the F-CPU before
leaving the programming device or PC by closing
STEP 7
or via the "Online > Delete
access rights" menu. If this is not strictly implemented, a screen saver equipped with a
password accessible only to authorized personnel must also be used.
(S006)
Access protection
4.4 Access protection through organizational measures
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 109
4.4
Access protection through organizational measures
To prevent that a safety program is swapped without authorization by exchanging removable
media (e.g. flash card, SIMATIC Micro Memory Card or hard disk with WinAC RTX F), you
must observe the following warning:
WARNING
You must limit access to the F-CPU to persons who are entitled for plugging removable
media through access protection.
(S079)
To prevent that a WinAC RTX F or an S7-1500 F Software Controller is accidentally
uninstalled or installed, you must observe the following warning:
WARNING
You must limit access to a WinAC RTX F or an S7-1500 F Software Controller through
access protection to persons who are authorized to uninstall and install or repair a WinAC
RTX F or an S7-1500 F Software Controller (e.g. by using Windows administrator rights
(ADMIN)).
(S075)
The "Delete Configuration" function is only offered in the panel of the PC station with an
S7-1500 F Software Controller when no access protection is set up on the F-CPU. We
therefore recommend that you do not set up F-access protection until after commissioning.
To prevent unauthorized restoration of the safety program, formatting of the F-CPU and
deleting program folders using the display of an S7-1500 F-CPU, you must observe the
following warning:
WARNING
The display password may only be given to persons who are authorized to restore safety
programs, format the F-CPU and delete program folders. If a password is not set up for the
display, you must protect the display through organizational measures ag
ainst unauthorized
operation. For example by setting up access protection for specific rooms.
(S063)
Access protection
4.4 Access protection through organizational measures
SIMATIC Safety - Configuring and Programming
110 Programming and Operating Manual, 10/2018, A5E02714440-AH
To prevent unauthorized restoration of the safety program with the Web server in an
S7-1200/1500 F-CPU, you must observe the following warning:
WARNING
The "F-admin" authorization for Web server without password protection (user "Everybody"
or "Anyone") is only intended for test purposes, maintenance, etc. This means only when
the system is not in productive operation. In this case you must ensure the safety of the
system through other organizational measures. For example by setting up access
protection for specific rooms.
Before you transition into productive operation, you must remove the "F-admin" right for the
user "Everybody".
Only authorized personnel may have access to the password of the Web server user with
the "F-admin" right. After downloading the hardware configuration, check whether only
permitted users of the Web server have the "F-admin" right on the F-CPU. To do so, use
the online view of the
Safety Administration Editor
(see also Safety Administration Editor
(Page 81)).
Saving the login file and the password of the Web server in the browser is only permitted
when use by unauthorized persons is prevented through other organizational measures
(e.g. access protection to the PG/PC).
(S064)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 111
Programming
5
5.1
Overview of Programming
Introduction
A safety program consists of F-blocks that you create using the FBD or LAD programming
language and F-blocks that are automatically added. Fault detection and reaction measures
are automatically added to the safety program you create, and additional safety-related tests
are performed. Moreover, you have the option to incorporate special ready-made safety
functions in the form of instructions into your safety program.
An overview of the following is given below:
The structure of the safety program
The fail-safe blocks
Differences in the programming of the safety program with FBD/LAD compared to
programming of standard user programs
5.1.1
Program structure of the safety program (S7-300, S7-400)
Representation of program structure
For structuring purposes, a safety program consists of one or two F-runtime groups.
Each F-runtime group contains:
F-blocks that you create using FBD or LAD or that are inserted from the project library or
global libraries
F-blocks that are added automatically (F-system blocks, automatically generated
F-blocks, and F-I/O DBs)
Below is a schematic diagram of a safety program or an F-runtime group for an S7-300/400
F-CPU.
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
112 Programming and Operating Manual, 10/2018, A5E02714440-AH
Main safety block
The main safety block is the first F-block of the safety program that you program yourself.
During compiling, it is supplemented by additional invisible calls of F-system blocks.
You must assign the main safety block to an F-runtime group (Page 132).
The main safety block in an S7-300/400 F-CPU is called from any block in the standard user
program. We recommend a call from an OB 3x.
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 113
F-runtime groups
To improve handling, a safety program consists of one or two "F-runtime groups". An F-
runtime group is a logical construct of several related F-blocks that is formed internally by the
F-system.
An F-runtime group consists of the following:
A main safety block (an F-FB/F-FC that you assign to the calling OB (FB/FC) as needed)
Any additional F-FBs or F-FCs that you program using FBD or LAD and call from the
main safety block
One or more F-DBs, as needed
F-I/O DBs
F-blocks from the project library or global libraries
F-system blocks F-SBs
Automatically generated F-blocks
Structuring the safety program in two F-runtime groups
You can divide your safety program into two F-runtime groups. By having parts of the safety
program (one F-runtime group) run in a faster priority class, you achieve faster safety circuits
with shorter response times.
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
114 Programming and Operating Manual, 10/2018, A5E02714440-AH
5.1.2
Program structure of the safety program (S7-1200, S7-1500)
Representation of program structure
For structuring purposes, a safety program consists of one or two F-runtime groups.
Each F-runtime group contains:
F-blocks that you create using FBD or LAD or that are inserted from the project library or
global libraries
F-blocks that are added automatically (F-system blocks F-SBs, automatically generated
F-blocks, F-runtime DB, and F-I/O DBs)
Below is a schematic diagram of a safety program or an F-runtime group for an S7-
1200/1500 F-CPU.
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 115
Main safety block
The main safety block is the first F-block of the safety program that you program yourself.
You must assign the main safety block to an F-runtime group (Page 132).
The main safety block in an S7-1200/1500 F-CPU is called by the F-OB assigned to the
F-runtime group.
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
116 Programming and Operating Manual, 10/2018, A5E02714440-AH
F-runtime groups
To improve handling, a safety program consists of one or two "F-runtime groups". An F-
runtime group is a logical construct of several related F-blocks that is formed internally by the
F-system.
An F-runtime group consists of the following:
An F-OB which calls the main safety block
A main safety block (an F-FB/F-FC that you assign to the F-OB)
Any additional F-FBs or F-FCs that you program using FBD or LAD and call from the
main safety block
One or more F-DBs, as needed
F-I/O DBs
F-runtime group information DB
F-blocks from the project library or global libraries
F-system blocks F-SBs
Automatically generated F-blocks
A preprocessing and/or postprocessing block, as needed (see Pre-/postprocessing (S7-
1200, S7-1500) (Page 87))
Pre-/postprocessing of an F-runtime group
You have the option of calling blocks of the standard application groups (FCs) directly before
or after an F-runtime group, for example for data transfer of fail-safe communication via
Flexible F-Link. (see Pre-/postprocessing (S7-1200, S7-1500) (Page 87))
Structuring the safety program in two F-runtime groups
You can divide your safety program into two F-runtime groups. By having parts of the safety
program (one F-runtime group) run in a faster priority class, you achieve faster safety circuits
with shorter response times.
See also
F-runtime group information DB (S7-1200, S7-1500) (Page 148)
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 117
5.1.3
Fail-Safe Blocks
F-blocks of an F-runtime group
The following table shows the F-blocks that you use in an F-runtime group:
F-block
Function
S7-300/400
F-CPUs
S7-1200/1500
F-CPUs
Main safety block The first step in programming of the safety program is the main safety
block.
The main safety block in S7-300/400 F-CPUs is an F-FC or F-FB (with
instance DB), which is called by a standard block (recommendation:
OB 35) from the standard user program.
The main safety block in S7-1200/1500 F-CPUs is an F-FC or F-FB (with
instance DB), which is called by the F-OB.
X X
F-FB/F-FC Both in the main safety block as well as additional F-FBs and F-FCs, you
can perform the following:
Program the safety program with the instructions available for F-
blocks in FBD or LAD
Call other created F-FBs/F-FCs for structuring the safety program
Insert F-blocks from the project library or global libraries
X X
F-DB Optional fail-safe data blocks that can be read- and write-accessed with-
in the entire safety program.
X X
F-I/O DB An F-I/O DB is automatically generated for each F-I/O when it is config-
ured. You can or you must access the tags of the F-I/O DB in conjunc-
tion with F-I/O accesses.
X X
F-shared DB The F-shared DB is a fail-safe data block that contains all of the shared
data of the safety program and additional information needed by the
F-system.
X
F-runtime group
information DB
An F-runtime group information DB is created when you create an F-
runtime group.
The F-runtime group information DB provides information on the F-
runtime group and on the safety program as a whole.
X
Note
You are not permitted to insert F
-system blocks from the "System blocks" folder in a main
safety block/F
-FB/F-FC.
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
118 Programming and Operating Manual, 10/2018, A5E02714440-AH
Instructions for the safety program
In the "Instructions" task card, you can find instructions for the F-CPU used and which you
can to use program the safety program.
You can find instructions that you know from the standard user program, such as bit logic
operations, mathematical functions, functions for program control, and word logic operations.
Moreover, there are instructions with safety functions, e.g., for two-hand monitoring,
discrepancy analysis, muting, emergency STOP/emergency OFF, safety door monitoring,
feedback monitoring and instructions for safety-related communication between F-CPUs.
Additional information
For a detailed description of the instructions for the safety program, refer to Overview of
instructions (Page 391).
Using instruction versions
As with the instructions for the standard user program, there may also be different versions
of the instructions for the safety program.
Additional information on instruction versions can be found in the help on STEP 7 in "Basics
for instruction versions".
Further information on the differences of the individual versions of the instructions for the
safety program can be found in the relevant chapter of the instructions.
Note
Note the following:
If you change the version of an instruction used in the safety program in the task card
“Instructions” to a version which does not have identical functions, the functioning of your
safety program may change after recompiling the safety program. In addition to the
signature of the F-block that uses the instruction, the F-collective signature and the F-
SW
collective signature of your safety program also change. You may have to perform an
acceptance test (Page 378).
(S7-300/400) If you use a know-how protected F-block
in your safety program which uses
an instruction which is not the same version as that set in the task card "Instructions",
when the program is compiled without entering the password for the know-how protected
F-block, it is adjusted to the version set in the task card "Instructions", providing the
interfaces of the instruction versions are identical. If the instruction versions do not have
identical functions, the functioning of the know-how protected F-block may change and
always its signature.
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 119
5.1.4
Restrictions in the programming languages FBD/LAD
LAD and FBD programming languages
The user program in the F-CPU typically consists of a standard user program and a safety
program.
The standard user program is created using standard programming languages such as SCL,
STL, LAD, or FBD.
For the safety program, LAD or FBD may be used with certain restrictions in the instructions
and the applicable data types and operand areas. Please also note the restrictions for the
individual instructions.
Supported instructions
The instructions available depend on the F-CPU used. You can find the supported
instructions in the description of the instructions (starting from (Page 391)).
Note
Enable input EN
and enable output ENO cannot be connected.
Exception:
(S7
-1200, S7-1500) With the following instructions you can program overflow detection by
connecting the enable output ENO:
ADD: Add (STEP 7 Safety V15.1) (Page 520)
SUB: Subtract (STEP 7 Safety V15.1) (Page 523)
MUL: Multiply (STEP 7 Safety V15.1) (Page 526)
DIV: Divide (STEP 7 Safety V15.1) (Page 529)
NEG: Create twos complement (STEP 7 Safety V15.1) (Page 533)
ABS: Form absolute value (STEP 7 Safety V15.1) (S7-1200, S7-1500) (Page 536)
CONVERT: Convert value (STEP 7 Safety V15.1) (Page 548)
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
120 Programming and Operating Manual, 10/2018, A5E02714440-AH
Supported data types and parameter types
Only
the following data types are supported:
BOOL
INT
WORD
DINT
DWORD (S7-300, S7-400)
TIME
ARRAY, ARRAY[*] when using the instructions RD_ARRAY_I: Read value from
INT F-array (STEP 7 Safety V15.1) (S7-1500) (Page 539) and RD_ARRAY_DI: Read
value from DINT F-array (STEP 7 Safety V15.1) (S7-1500) (Page 542).
Restrictions:
ARRAY only in F-global DBs
ARRAY limits: 0 up to max. 10000
ARRAY[*] only as in-out parameter (InOut) in F-FCs and F-FBs
ARRAY of UDT
ARRAY of Bool
ARRAY of Word
ARRAY of Time
F-compliant PLC data type (UDT) (S7-1200, S7-1500)
Note
If the result of an instruction is located outside the permitted ran
ge for this data type, the
F
-
CPU may switch to STOP. The cause of the diagnostics event is entered in the diagnostics
buffer of the F
-CPU.
You must therefore ensure that the permitted range for the data type is observed when
creating the program, or selec
t a matching data type or use the ENO output.
Note the description of the individual instructions.
Non-permitted data and parameter types
The following types are
not
permitted:
All types not listed in the section "Supported data types and parameters types" (e.g.
BYTE, REAL)
Complex data types (for example, STRING, ARRAY (S7-300, S7-400, S7-1200),
STRUCT, PLC data type (UDT) (S7-300, S7-400))
Parameter types (e.g. BLOCK_FB, BLOCK_DB, ANY)
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 121
Supported operand areas
The system memory of an F-CPU is divided into the same operand areas as the system
memory of a standard CPU. You can access the operand areas listed in the table below from
within the safety program.
Table 5- 1 Supported operand areas
Operand area
Description
Process image of the inputs
Of F-I/O Only read-only access to input channels of F-I/O is possible.
Transfer to IN_OUT parameters of an F-FB or F-FC is therefore not
valid either.
The process image of the inputs of F-I/O is updated prior to the start
of the main safety block.
Of standard I/O Input channels of standard I/O can only be accessed read-only.
Transfer to IN_OUT parameters of an F-FB or F-FC is therefore not
valid either.
In addition, a process-specific validity check is required.
See the
STEP 7 help
for the update times of the process image of the
inputs of standard I/O.
Process image of the outputs
Of F-I/O Only write-only access to output channels of F-I/O is possible.
Transfer to IN_OUT parameters of an F-FB or F-FC is therefore not
valid either.
In the safety program, the values for the outputs of the F-I/O are cal-
culated and stored in the process image of the outputs.
The process image of the outputs for F-I/O is updated after the end of
the main safety block.
Of standard I/O Output channels of standard I/O are write-only channels.
Transfer to IN_OUT parameters of an F-FB or F-FC is therefore not
valid either.
In the safety program, the values for the outputs of the standard I/O
are also calculated and stored in the process image of the outputs, if
needed.
See the
STEP 7 help
for the update times of the process image of the
outputs of standard I/O.
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
122 Programming and Operating Manual, 10/2018, A5E02714440-AH
Operand area
Description
Bit memory
This area is used for data exchange with the standard user program.
In addition, read access requires a process-specific validity check.
A particular element of the bit memory can be either read- or write-
accessed in the safety program.
Transfer to IN_OUT parameters of an F-FB or F-FC is therefore not
valid either.
Note that it is only permitted to use bit memory for connecting the
standard user program and the safety program; it must not be used as
a buffer for F-data
.
Data blocks
F-DB Data blocks store information for the program. They can either be
defined as global data blocks such that all F-FBs, F-FCs, or main
safety blocks can access them or assigned to a particular F-FB or
main safety block (instance DB). A tag of a shared DB can only be
accessed from one F-runtime group, and an instance DB only from
the F-runtime group in which the corresponding F-FB/instruction is
called.
DB This area is used for data exchange with the standard user program.
In addition, read access requires a process-specific validity check.
For a tag of a DB, either read access or write access is possible in the
safety program.
Transfer to IN_OUT parameters of an F-FB or F-FC is therefore not
valid either.
Please note that the tags of a DB can only be used for transferring
data between the standard user program and the safety program; DBs
must not be used as a buffer for F-data
.
Temporary local data
This memory area holds the temporary tags of a block (or F-block)
while the (F-) block is being executed. The local data stack also pro-
vides memory for transferring block parameters and for saving inter-
mediate results.
File type conversion
Just as with the standard user program, there are two possibilities for file type conversion in
the safety program.
Implicit conversion
The implicit conversion is executed as in the standard user program with the following
restrictions: The bit length of the source data type has to match the bit length of the
destination data type.
Explicit conversion
You use an explicit conversion instruction (Page 548) before the actual instruction is
executed.
Slice access
Slice access is not possible in the safety program.
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 123
Non-permitted operand areas
Access via units other than those listed in the table above is
not
permitted. The same applies
to access to operand areas not listed, in particular:
Data blocks that were automatically added
Exception: Certain tags in the F-I/O DB (Page 165) and in the F-shared DB (S7-300,
S7-400) (Page 148) or F-runtime group information DB (S7-1200, S7-1500) (Page 148)
I/O area: Inputs
I/O area: Outputs
Boolean constants "0" or "FALSE" and "1" or "TRUE" (S7-300, S7-400)
The Boolean constants "0" or "FALSE" and "1" or "TRUE" are available for S7-300/400
F-CPUs as "Tags" "RLO0" and "RLO1" in the F-global DB. You access them through a fully
qualified DB access ("F_GLOBDB".RLO0 or "F_GLOBDB".RLO1).
Boolean constants "0" or "FALSE" and "1" or "TRUE" (S7-1200, S7-1500)
The Boolean constants "0" or "FALSE" and "1" or "TRUE" are available for S7-1200/1500
F-CPUs to assign parameters during block calls.
You can also create "1" or "TRUE" in a tag with the help of the "Assignment (Page 402)"
instruction.
To do so, do not interconnect the box input of the "Assignment" instruction in FBD. In LAD,
you interconnect the input directly with the supply rail.
You obtain a tag with "0" or "FALSE" by subsequent inversion with the instruction "Invert
RLO (Page 399)".
Example FBD:
Example LAD:
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
124 Programming and Operating Manual, 10/2018, A5E02714440-AH
Operand area of temporary local data: Particularities
Note
Note when using the operand area of temporary local data that the first access of a local
data element in a main safety block/F
-FB/F-FC must always be a write access. This
initializes the lo
cal data element.
Make sure that a temporary local data element is initialized prior to the first JMP, JMPN, or
RET instruction.
The "local data bit" should be initialized with the Assign ("=") (FBD) or ("
--( )") (LAD)
instruction. Assign the local data b
it a signal state of "0" or "1" as a Boolean constant.
Local data bits cannot be initialized with the Flip Flop (SR, RS), Set Output (S) or Reset
Output (R) instructions.
The F
-CPU can go to STOP if this is not observed. The cause of the diagnostics event is
entered in the diagnostics buffer of the F
-CPU.
"Fully qualified DB access"
Access to tags of a data block in an F-FB/F-FC is "fully qualified DB access". This also
applies to initial access to tags of a data block after a jump label.
For S7-300/400 F-CPUs, only initial access needs to be "fully qualified DB access".
Alternatively, you can use the instruction "OPN".
Example of "fully qualified DB access":
Assign a name for the F-DB, e.g. "F_Data_1". Use the names assigned in the declaration of
the F-DB instead of the absolute addresses.
Figure 5-1 Example with fully-qualified access
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 125
Example of "non-fully qualified DB access" (S7-300, S7-400):
Figure 5-2 Example without fully-qualified access
Access to instance DBs
You can also access instance DBs of F-FBs with fully qualified access, e.g., for transfer of
block parameters. It is not possible to access static local data in single/multi-instances of
other F-FBs.
Note that accessing instance DBs of F-FBs that are not called in the safety program can
cause the F-CPU to go to STOP mode.
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
126 Programming and Operating Manual, 10/2018, A5E02714440-AH
5.1.5
F-compliant PLC data types (UDT) (S7-1200, S7-1500)
Introduction
You declare and use F-compliant PLC data types (UDT) as you would standard PLC data
types (UDT). You can use F-compliant PLC data types (UDT) in the safety program as well
as in the standard user program.
Differences to standard PLC data types (UDT) are described in this chapter.
Information on the use and declaration of standard PLC data types (UDT) is available in the
STEP 7 help
under "Declaring PLC data types".
Declaring F-compliant PLC data types (UDT)
You declare F-compliant PLC data types (UDT) as you would PLC data types (UDT).
In F-compliant PLC data types (UDT), you can use all data types (Page 119) that you can
also use in safety programs. Exception: ARRAY.
Nesting of F-compliant PLC data types (UDT) within F-compliant PLC data types (UDT) is
not supported.
Proceed as follows for declaration:
1. Click on "Add new PLC data type" in the "PLC Data Types" folder in the project tree.
2. To create an F-compliant PLC data type (UDT), enable the option "Create F-compliant
PLC data type" in the "Add new PLC data type" dialog.
3. Proceed as described in the
STEP 7 help
under "Programming structure of PLC data
types".
You specify default values for F-compliant PLC data types (UDT) during the declaration.
Using F-compliant PLC data types (UDT)
You use F-compliant PLC data types as you would standard PLC data types (UDT).
Changes to F-compliant PLC data types (UDT)
You need the password for the safety program to change F-compliant PLC data types
(UDT). Regardless if you are using the F-compliant PLC data type (UDT) in an F-block, in a
standard block or not at all.
See also
"F-compliant PLC data types" area (S7-1200, S7-1500) (Page 89)
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 127
5.1.5.1
Grouping PLC tags for inputs and outputs of F-I/O in structures (S7-1200, S7-1500)
You group PLC tags for inputs and outputs of F-I/O in structures (structured PLC tag) as you
would for inputs and outputs of standard I/O.
Use F-compliant PLC data types (UDT).
Rules
When creating structured PLC tags for inputs and outputs of F-I/O, you must also observe
the following rules in addition to the rules in the standard:
You must not group inputs/outputs of standard I/O and F-I/O at the same time in a
structured PLC tag.
You may only group inputs/outputs of actually existing channels (channel value and value
status) in a structured PLC tag.
See also Addressing F-I/O (Page 157)
You may only group inputs/outputs of channels (channel value and value status) that are
enabled in the hardware configuration in a structured PLC tag.
See also Addressing F-I/O (Page 157)
You may only group inputs of channels (channel value and value status) that provide the
result of the "1oo2 sensor evaluation" with set "1oo2 sensor evaluation".
See also Addressing F-I/O (Page 157)
In a structured PLC tag for an F-I/O with outputs, you must either group all outputs of this
F-I/O or an output range with multiples of 16 bits.
The F-CPU can go to STOP mode if this is disregarded. The cause of the diagnostics
event is entered in the diagnostics buffer of the F-CPU.
A structured PLC tag that groups outputs of an F-I/O must not overlap with other PLC
tags.
The F-CPU can go to STOP mode if this is disregarded. The cause of the diagnostics
event is entered in the diagnostics buffer of the F-CPU.
Note
To observe these rules, you must declare the F
-compliant PLC data type that is used for the
structured PLC tag accordingly.
You can find the addresses allocated to a structured PLC tag in the "IO tags" tab of an F-I/O
configuration.
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
128 Programming and Operating Manual, 10/2018, A5E02714440-AH
5.1.5.2
Example of structured PLC tags for inputs and outputs of F-I/O (S7-1200, S7-1500)
Introduction
This example uses the F-module 4 F-DI/3 F-DO DC24V/2A with 1oo2 evaluation to
demonstrate how you use structured PLC tags for access to F-I/O.
Channel structure of the 4 F-DI/3 F-DO DC24V/2A F-module
The table below sets out the channel structure and address assignment of the F-module 4
F-DI/3 F-DO DC24V/2A with 1oo2 evaluation. You may only access existing and enabled
channels (addresses I15.0 to I15.3 and I16.0 to I16.3). These channels provide the result of
1oo2 evaluation generated internally in the F-module.
Table 5- 2 Channel structure and addresses of the channel values of inputs with 1oo2 evaluation
Channel
Address
DI channel 0 channel value
I15.0
DI channel 1 channel value
I15.1
DI channel 2 channel value
I15.2
DI channel 3 channel value I15.3
I15.4
I15.5
I15.6
I15.7
Table 5- 3 Channel structure and addresses of the value status of the inputs with 1oo2 evaluation
Channel
Address
DI channel 0 value status
I16.0
DI channel 1 value status
I16.1
DI channel 2 value status
I16.2
DI channel 3 value status
I16.3
I16.4
I16.5
I16.6
I16.7
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 129
Table 5- 4 Channel structure and addresses of the value status of outputs
Channel
Address
DO channel 0 value status
I17.0
DO channel 1 value status I17.1
DO channel 2 value status
I17.2
DO channel 3 value status I17.3
Table 5- 5 Channel structure and addresses of the channel values of outputs
Channel
Address
DO channel 0 channel value
Q15.0
DO channel 1 channel value
Q15.1
DO channel 2 channel value
Q15.2
DO channel 3 channel value
Q15.3
Creating F-compliant PLC data types (UDT)
Create two F-compliant PLC data types (UDT), for example, for access to all channels.
The figure below shows an F-compliant PLC data type (UDT) for access to the channel
values and value status of the inputs with 1oo2 evaluation:
The figure below shows the F-compliant PLC data type (UDT) for access to the channel
values and value status of the outputs:
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
130 Programming and Operating Manual, 10/2018, A5E02714440-AH
Using F-compliant PLC data types (UDT)
As demonstrated in the figure below, you can use the two F-compliant PLC data types (UDT)
that you have created in an F-FC (e.g. "Motor"):
Creating structured PLC tag for the F-module 4 F-DI/3 F-DO DC24V/2A
Create structured PLC tags for the F-module 4 F-DI/3 F-DO DC24V/2A:
Programming
5.1 Overview of Programming
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 131
Accessing the F-FC
Transfer the structured PLC tags you have created when you call the F-FC (e.g. "Motor"):
See also
Addressing F-I/O (Page 157)
Value status (S7-1200, S7-1500) (Page 159)
5.1.6
Editing PLC tags with external editors
To edit PLC tags with external editors follow the procedure as in the standard. Additional
information can be found in the
STEP 7
help in "Editing PLC tags with external editors".
Note the following:
Note
After importing a tag table which contains tags used in the safety program, the collective
F
-signature of the safety program is reset.
To form the collective F
-signature again you h
ave to recompile the project data. For this, with
access protection set up for the safety program, you need a valid access authorization for
the safety program.
If you would like to edit PLC tags with external editors, we therefore recommend that you
store
PLC tags to be used in the safety program in a separate tag table.
5.1.7
Using Multiuser engineering
If you want to use Multiuser engineering, proceed as described in the STEP 7 help under
"Using Multiuser engineering".
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
132 Programming and Operating Manual, 10/2018, A5E02714440-AH
5.2
Defining F-Runtime Groups
5.2.1
Rules for F-Runtime Groups of the Safety Program
Rules
Note the following:
The channels (channel values and value status) of an F-I/O can only be accessed from a
single F-runtime group.
Tags of the F-I/O DB of an F-I/O can only be accessed from one F-runtime group and
only from that F-runtime group from which the channels or value status of this F-I/O are
also accessed (if access is made).
F-FBs can be used in more than one F-runtime group but they must be called with
different instance DBs.
Instance DBs of F-FB can only be accessed from the F-runtime group in which the
associated F-FB is called.
A tag of a global F-DB (except the F-global DB) can only be accessed from one F-runtime
group (however, a global F-DB can be used in more than one F-runtime group).
(S7-300, S7-400) A DB for F-runtime group communication can be read and write
accessed by the F-runtime group to which it was assigned as "DB for runtime group
communication", but only read-accessed by the "receiver" F-runtime group.
(S7-300, S7-400) An F-communication DB can only be accessed from one F-runtime
group.
(S7-1200, S7-1500) You must not call the main safety block yourself. It is automatically
called by the assigned F-OB.
Note
F
-OBs are protected by F-system know-how. The OB start information of F-
OBs therefore
cannot be evaluated.
(S7-1200, S7-1500). The F-OB should be created with the highest priority of all OBs.
Note
The cycle time of the F
-OB can be prolonged by, among other things, communication
load, the process
ing of higher-priority interrupts, as well as by test and commissioning
functions.
(S7-300, S7-400) The main safety block may only be called once from a standard block.
Multiple calls can cause the F-CPU to go to STOP mode.
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 133
(S7-300, S7-400) For optimal use of temporary local data, you must call the F-runtime
group (the main safety block) directly in an OB (cyclic interrupt OB, if possible); you
should not declare any additional temporary local data in this cyclic interrupt OB.
(S7-300, S7-400) Within a cyclic interrupt OB, the F-runtime group should be executed
before
the standard user program; i.e. it should be called at the very beginning of the OB,
so that the F-runtime group is always called at fixed time intervals, regardless of how long
it takes to process the standard user program.
For this reason, the cyclic interrupt OB should also not be interrupted by higher priority
interrupts.
The process image of the inputs and outputs of standard I/O, bit memory, and tags of
DBs in the standard user program may be accessed either as read-only or read/write
from more than one F-runtime group. (see also Data exchange between standard user
program and safety program (Page 195))
F-FCs can generally be called in more than one F-runtime group.
Note
You can improve performance by writing sections of the program that are not required for the
safety function in the standard user program.
When determining whi
ch elements to include in the standard user program and which to
include in the safety program, you should keep in mind that the standard user program can
be modified and downloaded to the F
-CPU more easily. In general, changes in the standard
user program
do not require an acceptance.
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
134 Programming and Operating Manual, 10/2018, A5E02714440-AH
5.2.2
Procedure for defining an F-runtime group (S7-300, S7-400)
Requirements
You have inserted an S7-300/400 F-CPU
in your project.
In the "Properties" tab of the F-CPU, the "F-capability activated" check box is selected
(default setting).
F-runtime group created by default
STEP 7 Safety
inserts F-blocks for an F-runtime group in the project tree by default after an
F-CPU has been added. When you open the "Program blocks" folder, you see the (F-)blocks
of the F-runtime group (CYC_INT5 [OB 35], Main_Safety [FB 1], and Main_Safety_DB [DB1])
in the project tree.
The following section describes how you modify the settings / parameters of the F-runtime
group created by default or add and additional F-runtime group.
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 135
Procedure for defining an F-runtime group
Proceed as follows to define an F-runtime group:
1. Open the
Safety Administration Editor
by double-clicking in the project tree.
2. Select "F-runtime group" in the area navigation.
Result:
The work area for defining an F-runtime group with the (default) settings for F-
runtime group 1 opens.
3. Specify the block in which the main safety block is to be called.
Cyclic interrupt OB 35 is suggested here by default. The advantage of using cyclic
interrupt OBs is that they interrupt the cyclic program execution in OB 1 of the standard
user program at fixed time intervals; that is, the safety program is called and executed at
fixed time intervals in a cyclic interrupt OB.
In this input field, you can select only those blocks that were created in the LAD, FBD, or
STL programming language. If you select a block here, the call is inserted automatically
into the selected block and, if necessary, removed from a previously selected block.
If you want to call the main safety block in a block that was created in another
programming language, you must program this call itself. The input field is then not
editable (grayed out), and you can change the call only in the calling block and not the
Safety Administration Editor
.
4. Assign the desired main safety block to the F-runtime group. If the main safety block is an
FB, you must also assign an instance DB.
Main_Safety [FB1] and Main_Safety_DB [DB1] are suggested by default.
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
136 Programming and Operating Manual, 10/2018, A5E02714440-AH
5. The F-CPU monitors the F-cycle time of the F-runtime group. For "Maximum cycle time of
F-runtime group", enter the maximum permitted time between two calls of the F-runtime
group.
WARNING
The F-runtime group call interval is monitored for the maximum value; i.e. monitoring is
performed to determine whether the call is executed often enough, but not whether it is
executed too often or, for example, isochronous. Fail-safe timers must therefore be
implemented using the TP, TON, or TOF instructions (Page 489) from the "Instructions"
task card and not using counters (OB calls).
(S007)
WARNING
The response time of their safety function depends, among other things, on the cycle
time of the F-OB, the runtime of the F-runtime group and, when distributed F-I/O is
used, the parameter assignment of PROFINET/PROFIBUS.
Therefore, the configuration/parameter assignment of the standard system influences
the response time of its safety function.
Examples:
The increase in priority of a standard OB compared to an F-OB can extend the
runtime of the F-runtime group due to the interruption by higher-priority interrupts.
The change of the send clock cycle of PROFINET changes the cycle time of an F-
OB
with event class "Synchronous cycle".
Note that the configuration / parameter assignment of the standard system is not subject
to access protection for the safety program and does not lead to a modification of the
collective F-signature.
If you do not take organizational measures to prevent changes in the configuration /
parameter assignment of the standard system with influence on the response time, you
must always set the monitoring times for the calculation of the maximum response time
of a safety function (see Configuring monitoring times (Page 608)).
The monitoring times are protected against change with the access protection of the
safety program and are recorded by the F-collective signature as well as the F-SW
collective signature.
When calculating with Excel file for response time calculation
(http://support.automation.siemens.com/WW/view/en/49368678/133100) you need to
consider the value that is specified for "Any standard system runtimes" as value for the
maximum response time.
(S085)
6. If one F-runtime group is to provide tags for evaluation to another F-runtime group of the
safety program, assign a DB for F-runtime group communication. Select an F-DB for "DB
for F-runtime group communication". (See also F-runtime group communication (S7-300,
S7-400) (Page 141))
7. If you want to create a
second F-runtime group
, click the "Add new F-runtime group"
button.
8. Assign an F-FB or F-FC as the main safety block to a calling block. This F-FB or F-FC is
automatically generated in the project tree, if not already present.
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 137
9. If the main safety block is an F-FB, assign an instance DB to the main safety block. The
instance DB is generated automatically in the project tree.
10.Follow steps 3 to 5 above to complete generation of the second F-runtime group.
5.2.3
Procedure for defining an F-runtime group (S7-1200, S7-1500)
Requirements
You have inserted an S7-1200/1500 F-CPU
in your project.
In the "Properties" tab of the F-CPU, the "F-capability activated" check box is selected
(default setting).
F-runtime group created by default
STEP 7 Safety
inserts F-blocks for an F-runtime group in the project tree by default after an
F-CPU has been added. When you open the "Program blocks", you see the (F-)blocks of the
F-runtime group (FOB_RTG1 [OB123], Main_Safety_RTG1 [FB1] and
Main_Safety_RTG1_DB [DB1]) in the project tree.
The following section describes how you modify the settings / parameters of the F-runtime
group created by default or add and additional F-runtime group.
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
138 Programming and Operating Manual, 10/2018, A5E02714440-AH
Procedure for defining an F-runtime group
Proceed as follows to define an F-runtime group:
1. Open the
Safety Administration Editor
by double-clicking in the project tree.
2. Select "F-runtime group" in the area navigation.
Result:
The work area for defining an F-runtime group with the (default) settings for
F-runtime group 1 opens.
3. Assign a name for the F-OB under "F-OB".
4. Specify the event class of the F-OB when you create a new F-runtime group.
For an F-OB you can select between the event classes "Program cycle", "Cyclic interrupt"
or "Synchronous cycle".
In the case of the F-runtime group created by default, the F-OB has the event class
"Cyclic interrupt". To change the event class of the F-OB of an already created F-runtime
group, you need to delete and F-runtime group and create a new one.
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 139
Note
We recommend creating the F
-OB with the event class "Cyclic interrupt" as "cyclic
interrupt OB". The safety program will then be called and run at fixed time inte
rvals.
F
-OBs with the event class "Synchronous cycle" are only recommended in conjunction
with F
-I/O devices that support isochronous mode, for example submodule "Profisafe
Telgr 902" of drive SINAMICS S120 CU310
-2 PN V5.1.
F
-OBs with the event class "Program cycle" are not recommended, as these have the
lowest priority "1" (see below).
Note
Note the maximum permissible number of OBs (incl. F
-OBs) with event class
"Synchronous cycle" (see technical specifications in the product manuals of the S7
-1500
C
PUs).
5. If required, you can manually change the number of the F-OB proposed by the system.
To do so, note the number ranges valid for the relevant event class.
6. Assign cycle time, phase shift and priority parameters for F-OBs with event class "Cyclic
interrupt".
Assign the priority parameter for F-OBs with event class "Synchronous cycle".
Select a cycle time which is less than the "Maximum cycle time of F-runtime group"
and less than the "Cycle time warning limit of F-runtime group".
Select a phase shift which is less than the cycle time.
If possible, select a priority that is higher than the priority of all other OBs.
Note
Through a high priority of the F
-
OB you ensure that the runtime of the safety program and
the
response time of your safety functions (Page 608) are influenced as little as possibly
by the standard user program.
Note
For F
-OBs with event class "Synchronous cycle" you need to also assign parameters for
application cycle (ms) and possibly delay time (ms) after defining the F
-
runtime group and
the connection of the isochronous F
-I/O to the isochronous mode interrupt OB. You can
find these parameters in the "Properties" dialog box of the isochronous mode interrupt OB
in the "Isochronous mode" group. Proceed as described in the STEP 7 help under
"Configuring isochronous mode interrupt OBs".
7. Assign the calling main safety block to the F-OB. If the main safety block is an FB, you
must also assign an instance DB.
Main_Safety_RTG1 [FB1] and Main_Safety_RTG1_DB [DB1] are suggested by default.
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
140 Programming and Operating Manual, 10/2018, A5E02714440-AH
8. The F-CPU monitors the F-cycle time of the F-runtime group. Two parameters are
available:
If the "Cycle time warning limit of F-runtime group" is exceeded, an entry is written to
the diagnostics buffer of the F-CPU. This parameter can, for example, be used to
determine whether the cycle time exceeds a required value without the F-CPU
switching to STOP mode.
If the "Maximum cycle time of F-runtime group" is exceeded, the F-CPU will go to
STOP. For "Maximum cycle time of F-runtime group", select the maximum permitted
time between two calls of this F-runtime group (maximum of 20000000 µs).
WARNING
The F-runtime group call interval is monitored for the maximum value; i.e. monitoring
is performed to determine whether the call is executed often enough, but not whether
it is executed too often or, for example, isochronous. Fail-safe timers must therefore
be implemented using the TP, TON, or TOF instructions (Page 489) from the
"Instructions" task card and not using counters (OB calls).
(S007)
WARNING
The response time of their safety function depends, among other things, on the cycle
time of the F-OB, the runtime of the F-runtime group and, when distributed F-I/O is
used, the parameter assignment of PROFINET/PROFIBUS.
Therefore, the configuration/parameter assignment of the standard system influences
the response time of its safety function.
Examples:
The increase in priority of a standard OB compared to an F-OB can extend the
runtime of the F-runtime group due to the interruption by higher-priority interrupts.
The change of the send clock cycle of PROFINET changes the cycle time of an F-
OB with event class "Synchronous cycle".
Note that the configuration / parameter assignment of the standard system is not
subject to access protection for the safety program and does not lead to a
modification of the collective F-signature.
If you do not take organizational measures to prevent changes in the configuration /
parameter assignment of the standard system with influence on the response time,
you must always set the monitoring times for the calculation of the maximum
response time of a safety function (see Configuring monitoring times (Page 608)).
The monitoring times are protected against change with the access protection of the
safety program and are recorded by the F-collective signature as well as the F-SW
collective signature.
When calculating with Excel file for response time calculation
(http://support.automation.siemens.com/WW/view/en/49368678/133100) you need to
consider the value that is specified for "Any standard system runtimes" as value for
the maximum response time.
(S085)
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 141
The "Cycle time warning limit of F-runtime group" must be configured as less than or
equal to the "Maximum cycle time of F-runtime group".
9. Assign a name for the F-runtime group information DB (Page 148) under "F-runtime
group DB".
10.If required, you can select blocks of the standard program (FCs) with regard to
preprocessing or postprocessing of an F-runtime group (see Pre-/postprocessing
(S7-1200, S7-1500) (Page 87))
11.If you want to create a
second F-runtime group
, click the "Add new F-runtime group"
button. Follow steps 3 to 10 above.
5.2.4
F-runtime group communication (S7-300, S7-400)
Safety-related communication between F-runtime groups
Safety-related communication can take place between the two F-runtime groups of a safety
program. This means fail-safe tags can be provided by one F-runtime group in an F-DB and
read in another F-runtime group.
Note
A DB for F
-runtime group communication can be read and write accessed by the F-runtime
group to which it was assigned as "DB for runtime group communication", while it can
only
be read
-accessed by the "receiver" F-runtime group.
Tip:
You can improve performance by structuring your safety program in such a way that as
few tags as possible are exchanged between the F-runtime groups.
Procedure for defining a DB for F-runtime group communication
You define the DB for F-runtime group communication in the work area "F-runtime groups".
Proceed as follows:
1. Click "F-runtime groups" in "
Safety Administration Editor
".
2. Select an existing F-DB in the "DB for F-runtime group communication" field or assign a
new one.
3. Assign a name to the F-DB.
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
142 Programming and Operating Manual, 10/2018, A5E02714440-AH
Up-to-dateness of tags read from another F-runtime group
Note
Tags read are up
-to-date as at the time of the last completed processing cycle of the
F
-runtime group providing the tags prior to start-up of the F-runtime group reading the tags.
If the tags supplied undergo multiple changes during runtime of the F-runtime group
supplying the tags, the F-runtime group reading the tags only receives the last change (see
figure below).
Assignment of fail-safe values
After F-system start-up, fail-safe values are supplied to the F-runtime group which has read
access to tags in the DB for F-runtime group communication of another F-runtime group (for
example, F-runtime group 2). These are the values you specified as initial values in the DB
for F-runtime group communication of F-runtime group 1.
F-runtime group 2 reads the fail-safe values the first time it is called. The second time the
F-runtime group 2 is called, it reads the latest tags if F-runtime group 1 has been processed
completely between the two calls of F-runtime group 2. If F-runtime group 1 has not been
processed completely, F-runtime group 2 continues to read the fail-safe values until
F-runtime group 1 is completely processed.
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 143
The behavior is illustrated in the two figures below.
Reading tags from F-runtime group 1, which has a longer OB cycle and lower priority than
F-runtime group 2
Startup of F-system
Cycle time of the (F-)OB in which the F-runtime group is called.
Runtime of the F-runtime group
... Tag of F-runtime group 1, written to DB for F-runtime group communication of F-
runtime group 1
...Tag of F-runtime group 2, read in DB for F-runtime group communication of F-runtime
group 1
Initial value in the DB for F-runtime group communication
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
144 Programming and Operating Manual, 10/2018, A5E02714440-AH
Reading tags from F-runtime group 1, which has a shorter OB cycle and higher priority than
F-runtime group 2
Startup of F-system
Cycle time of the (F-)OB in which the F-runtime group is called.
Runtime of the F-runtime group
... Tag of F-runtime group 1, written to DB for F-runtime group communication of F-
runtime group 1
... Tag of F-runtime group 2, read in DB for F-runtime group communication of F-runtime
group 1
Initial value in the DB for F-runtime group communication
F-runtime group supplying tags is not processed
Note
If the F
-runtime group whose DB for F-runtime group communication is to supply the tags is
not processed (the main s
afety block of the F-runtime group is not called), the F-CPU goes
to STOP mode. One of the following diagnostics events is then entered in the diagnostics
buffer of the F
-CPU:
Error in safety program: cycle time exceeded
Number of the relevant main safety block (of F-runtime group that is not processed)
Current cycle time in ms: "0"
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 145
5.2.5
F-runtime group communication (S7-1200, S7-1500)
Introduction
With the help of Flexible F-Link you realize a F-runtime group communication.
With Flexible F-Link a coded F-array is made available for the send data of the F-runtime
group. The coded F-array is transferred to the other F-runtime group with standard
instructions such as UNMOVE_BLK.
Requirement
S7-1500 F-CPUs as of firmware V2.0
S7-1200 F-CPUs as of firmware V4.2
Safety system version as of V2.2
F-runtime group communication
If you want to send a data fail-safe from one F-runtime group to another F-runtime group,
follow these steps:
1. Create an F-compliant PLC data type (UUID) for the F-runtime group communication. The
size is up to 100 bytes.
2. Create two F-communications for an F-runtime group communication in the Safety
Administration Editor in the "Flexible F-Link" area. One F-communication each for the
send and receive side.
3. Configure the same F-monitoring time and F-communication UUID for each F-runtime
group communication relationship.
Information on calculating the F-monitoring times can be found in Monitoring and
response times (Page 607).
For example:
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
146 Programming and Operating Manual, 10/2018, A5E02714440-AH
4. On the send side (e.g. RTG1) supply the data of the transmission DBs with the data to be
sent.
For example:
5. Read the receiving data from the receiving DB on the receive side (e.g. RTG2).
For example:
6. Call the instruction "UMOVE_BLK" in the F-runtime group for the send data (e.g. RTG1)
in the FC for post processing (Page 87).
7. Interconnect the "UMOVE_BLK" instruction for the data to be sent as follows:
"Send" is the F-communication DB (Page 96) of the F-runtime group that sends the data.
"Receive" is the F-communication DB (Page 96) of the F-runtime group that receives the
data.
8. Call the instruction "UMOVE_BLK" in the F-runtime group for acknowledgment (e.g.
RTG2) in the FC for post processing (Page 96).
9. Interconnect the "UMOVE_BLK" instruction for the acknowledgment connection as
follows:
"Receive" is the F-communication DB (Page 96) of the F-runtime group that sends the
acknowledgment telegram.
"Send" is the F-communication DB (Page 96) of the F-runtime group that receives the
acknowledgment telegram.
10.Compile the user program.
11.Download the user program to the F-CPU.
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 147
WARNING
During the acceptance use the safety summary to verify that the offsets of the elements of
the F-compliant PLC data types (UDT) match for the sending and receiving data within the
safety message frame. For this purpose all members and addresses are listed in the safety
summary per UDT. Also keep in mind that the size can be a up to 100 bytes.
(S088)
WARNING
When a new Flexible F-Link communication is created in the Safety Administration Editor,
the F-communication UUID for the communication is explicitly provided by the system. By
copying communications in Safety Administration Editor within the parameterization table or
when copying into another F-CPU, the F-communication UUIDs are not generated new and
are therefore not unique anymore. If the copy is used to configure a new communication
relationship, you yourself need to ensure the uniqueness. To do this select the affected
UUIDs and regenerate via the "Generate UUID" shortcut menu. The uniqueness must be
ensured in the safety summary during acceptance of the safety program.
(S087)
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal state to be transferred will
be acquired at the sender end and transferred to the receiver if the signal level is pending
for at least as long as the assigned monitoring time.
(S018)
Up-to-dateness of tags read from another F-runtime group
The same statements as those in the section "F-runtime group communication (S7-300, S7-
400) (Page 141)" apply (except for the storage locations written or read or initial values).
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
148 Programming and Operating Manual, 10/2018, A5E02714440-AH
5.2.6
F-shared DB (S7-300, S7-400)
Function
The F-shared DB is a fail-safe data block that contains all of the shared data of the safety
program and additional information needed by the F-system. The F-shared DB is
automatically inserted when the hardware configuration is compiled.
Using its name F_GLOBDB, you can evaluate certain data elements of the safety program in
the standard user program.
Reading an F-shared DB in the standard user program
You can read out the following information in the F-shared DB in the standard user program
or on an operator control and monitoring system:
Operating mode: safety mode or disabled safety mode ("MODE" tag)
Error information "Error occurred when executing safety program" ("ERROR" tag)
Collective F-signature ("F_PROG_SIG" tag)
Compilation date of the safety program ("F_PROG_DAT" tag, DATE_AND_TIME data
type)
You use fully qualified access to access these tags (e.g. ""F_GLOBDB".MODE").
5.2.7
F-runtime group information DB (S7-1200, S7-1500)
Introduction
The F-runtime group information DB provides key information on the corresponding
F-runtime group and on the safety program as a whole.
The F-runtime group information DB is generated automatically when an F-runtime group is
created. A symbol, for example, "RTG1SysInfo", is assigned for the F-runtime group
information DB. You can change the name in the
Safety Administration Editor
.
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 149
Information in the F-runtime group information DB
The F-runtime group information DB provides the following information:
Name
Data type
For processing
in the safety
program
For processing in
the standard user
program
Description
MODE
BOOL
x
x
1 = Disabled safety mode
F_SYSINFO
MODE
BOOL
x
1 = Disabled safety mode
TCYC_CURR DINT x Current cycle time of the F-runtime
group, in ms
TCYC_LONG DINT x Longest cycle time of the F-runtime
group, in ms
TRTG_CURR DINT x Current runtime of the F-runtime group,
in ms
TRTG_LONG DINT x Longest runtime of the F-runtime group,
in ms
T1RTG_CURR
DINT
x
Not supported by
STEP 7 Safety V15.1
.
T1RTG_LONG
DINT
x
Not supported by
STEP 7 Safety V15.1
.
F_PROG_SIG DWORD x Collective F-signature of the safety pro-
gram
F_PROG_DAT
DTL
x
Compilation date of the safety program
F_RTG_SIG
DWORD
x
F-runtime groups signature
F_RTG_DAT
DTL
x
Compilation date of the F-runtime group
VERS_S7SAF
DWORD
x
Version identifier for
STEP 7 Safety
You access the content of the F-runtime group information DB with fully qualified addressing.
Either collectively with the F_SYSINFO PLC data type (UDT), for example,
"RTG1SysInfo.F_SYSINFO", provided by the F-system or individual information, for
example, "RTG1SysInfo.F_SYSINFO.MODE".
See also
Program identification (Page 337)
"Flexible F-Link" area (S7-1200, S7-1500) (Page 96)
Programming
5.2 Defining F-Runtime Groups
SIMATIC Safety - Configuring and Programming
150 Programming and Operating Manual, 10/2018, A5E02714440-AH
5.2.8
Deleting an F-runtime group
Deleting an F-runtime group
To delete an F-runtime group, proceed as follows:
1. In the area navigation of the
Safety Administration Editor
, click on the F-runtime group to
be deleted.
2. Select the "Delete F-runtime group" button in the work area.
3. Confirm the dialog with "Yes".
4. Compile the safety program (Page 311) (menu command "Edit > Compile") to put your
changes into effect.
The assignment of the F-blocks to an F-runtime group (to the calling block of the main safety
block) is deleted. However, the F-blocks continue to exist.
Note
If you want to delete yo
ur safety program, delete all F-blocks outside the System blocks
folder in the project tree.
F
-blocks that do not allow deletion are deleted by recompiling the safety program or
deactivating F
-capability for the F-CPU (see Configuring an F-CPU (Page 48)).
5.2.9
Changing the F-runtime group (S7-300, S7-400)
Changing an F-runtime group
You can make the following changes for each F-runtime group in your safety program in the
corresponding "F-runtime group" work area:
Specify another block as the calling block of the main safety block.
Specify another F-FB or F-FC as main safety block.
Enter a different or new I-DB for the main safety block.
Change the value for the maximum cycle time of the F-runtime group
Specify another DB as a data block for F-runtime group communication.
Programming
5.3 Creating F-blocks in FBD / LAD
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 151
5.2.10
Changing the F-runtime group (S7-1200, S7-1500)
Changing an F-runtime group
You can make the following changes for each F-runtime group in your safety program in the
corresponding "F-runtime group" work area:
Change the name, number, cycle time, phase shift and priority of the F-OB.
Specify another F-FB or F-FC as main safety block.
Enter a different or new I-DB for the main safety block.
Change the value for the maximum cycle time and the cycle time warning limit of the
F-runtime group.
Assign another name for the F-runtime group information DB.
Specify an FC for the preprocessing and postprocessing.
5.3
Creating F-blocks in FBD / LAD
5.3.1
Creating F-blocks
Introduction
In order to create F-FBs, F-FCs, and F-DBs for the safety program, you should follow the
same basic procedure as for standard blocks. In the following, only the deviations from the
procedure for standard blocks are presented.
Creating F-FBs, F-FCs, and F-DBs
You create F-blocks in the same way as for standard blocks. Proceed as follows:
1. Double-click on "Add new block" under "Program blocks" in the project tree.
2. In the dialog that appears, specify the type, name, and language and select the "Create
F-block" check box. (If you do not select the check box, a standard block is created.)
3. After the dialog is confirmed, the F-block is opened in the
Program editor
.
Programming
5.3 Creating F-blocks in FBD / LAD
SIMATIC Safety - Configuring and Programming
152 Programming and Operating Manual, 10/2018, A5E02714440-AH
Note the following
Note the following important instructions:
Note
You may not declare block parameters in the block interface of the main safety block
because they cannot be sup
plied.
Note
You can edit start values in instance DBs. The function "Apply actual values" is not
supported.
Note
You may not access static local data in single instances or multi
-instances of other F-FBs.
Note
You must always initialize outputs
of F-FCs.
The F
-
CPU can go to STOP mode if the information above is not observed. The cause of the
diagnostics event is entered in the diagnostics buffer of the F
-CPU.
Note
If you wish to assign an address from the data area (data block) to a formal p
arameter of an
F
-FC as an actual parameter, you have to use fully qualified DB access. (S7-300, S7-400)
Note
Access to the inputs in an F
-FB/F-FC is read-only, while access to the outputs is write-only.
Use an in/out if you wish to have both read and w
rite access.
Note
For greater clarity, assign meaningful names to the F
-blocks you have created.
Copying/pasting F-blocks
You can copy F-FBs, F-FCs, and F-DBs in exactly the same was as blocks of the standard
user program.
(S7-1200, S7-1500) You may not copy an F-OB.
Exception:
You cannot copy blocks from the folder "Program blocks > System blocks".
See also
Changing the F-runtime group (S7-1200, S7-1500) (Page 151)
Programming
5.3 Creating F-blocks in FBD / LAD
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 153
5.3.2
Know-how protection
For know-how protection of F-blocks, proceed as described in the
STEP 7
help under
"Protecting blocks".
Requirements
Note the following with regard to know-how protection of F-blocks:
An F-block to which you wish to assign know-how protection must be called in the safety
program.
Before you can set up the know-how protection for an F-block, the safety program must
be consistent. For this purpose, compile (Page 311) the safety program.
Note
No source code is output for know
-how protected F-
blocks in the safety summary. Therefore,
create the safety summary (for
example to carry out a code review or accept the F-block)
before you set up the know
-how protection.
Note
If you want to edit the program code and/or the block interface of a know
-how protected F-
block, we recommend that you do not open the F
-block by entering a password, but rather
remove the know
-how protection completely and set it up again after compiling.
Note
(S7
-1200, S7-1500) When a know-how protected F-block or F-blocks called by it are
renamed, the signature of the know
-how protected F-blo
ck is not changed until the password
is entered when opening or removing the know
-how protection.
Note
When know
-how protected F-blocks are used, warnings and error messages whose cause
can lie in the know
-how protected F-blocks can be displayed during
compilation of the safety
program. The warnings and error messages contain corresponding information. Example: In
a know
-how protected F-block, you perform read access to a tag of the standard user
program to which write access is taking place in a differ
ent (know-how protected) F-block.
For S7
-1200/1500 F-
CPUs, you can obtain additional information from the safety summary in
the section "Know
-how protected F-blocks in the safety program".
See also
Reuse of F-blocks (Page 154)
Programming
5.3 Creating F-blocks in FBD / LAD
SIMATIC Safety - Configuring and Programming
154 Programming and Operating Manual, 10/2018, A5E02714440-AH
5.3.3
Reuse of F-blocks
Introduction
You can reuse F-blocks that you have already tested and, if applicable, approved, in other
safety programs without having to test and approve them again.
You can protect the content of the F-block by setting up the know-how protection.
Like standard blocks, you can store F-blocks as master copies or types in global libraries or
in the project library.
Additional information can be found in the
STEP 7 help
under "Using libraries".
Creating safety documentation for the F-block to be reused
Create safety documentation with the following information for F-blocks that you want to
reuse.
S7-300/400 F-CPUs
Signature and initial value signature of the know-how protected F-block
Versions of all the used versioned LAD/FBD instructions
Signatures and initial value signatures of all called F-blocks
S7-1200/1500 F-CPUs
Signature of the know-how protected F-block
Safety system version when setting up the know-how protection
Versions of all the used versioned LAD/FBD instructions
Signatures of all called F-blocks
The safety documentation should also contain a description of the functionality of the F-
block, in particular if it is know-how protected.
The required information is obtained by creating a safety summary of the safety program in
which you originally created, tested and approved the F-block to be reused.
This safety summary can also serve directly as the safety documentation for the F-block to
be reused.
Programming
5.4 Programming startup protection
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 155
Checks when using the F-block to be reused
When reusing the F-block, ensure the following:
The signature and initial value signature (S7-300/400) of the F-block are unchanged.
(SIMATIC S7-1200, S7-1500) The documented safety system version is set.
The documented (or functionally identical) versions of the versioned LAD/FBD
instructions are set. You can find information about the instruction versions in the
description of the instructions.
The called F-blocks with the documented signatures and initial value signatures
(S7-300/400) are used.
If the version conflicts cannot be eliminated due to other dependencies, please contact the
author of the know-how protected block in order to obtain a compatible approved version.
See also
Compliance of the know-how protected F-blocks used in the safety program with their safety
documentation. (Page 366)
5.4
Programming startup protection
Introduction
WARNING
STOP, for example, via programming device/PC, mode switch, communication function or
"STP" instruction
Initiating STOP, for example by means of programming device/PC operation, mode switch,
communication function or "STP" instruction as well as maintaining the STOP state are not
safety-oriented. This STOP state can be easily (and unintentionally) be revoked, for
example, by programming device/PC operation.
When an F-CPU is switched from STOP to RUN mode, the standard user program starts
up in the usual way. When the safety program is started up, all F-DBs are initialized with
the values from the load memory - as is the case with a cold restart. This means that saved
error information is lost. The F-system automatically reintegrates the F-I/O.
If your process does not allow such a startup, you must program a restart/startup protection
in the safety program: The output of process data must be blocked until manually enabled.
This enable must not occur until it is safe to output process data and faults have been
corrected.
(S031)
Programming
5.4 Programming startup protection
SIMATIC Safety - Configuring and Programming
156 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example of restart/startup prevention
In order to implement a restart/startup prevention, it must be possible to detect a startup. To
detect a startup, you declare a tag of data type BOOL with initial value "TRUE" in an F-DB.
Block the output of process data when this tag has the value "1," for example, by passivating
F-I/O using the PASS_ON tag in the F-I/O DB.
To manually enable the output of process data, you reset this tag by means of a user
acknowledgment.
See also
Implementing User Acknowledgment in the Safety Program of the F-CPU of a DP Master or
IO controller (Page 187)
Implementing user acknowledgment in the safety program of the F-CPU of a I-slave or I-
device (Page 192)
F-I/O DB (Page 165)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 157
F-I/O access
6
6.1
Addressing F-I/O
Overview
Below you will find a description of how to address the F-I/O in the safety program and which
rules must be observed in the process.
Addressing via the process image
As with standard I/O, you access F-I/O (e.g., S7-1500/ET 200MP fail-safe modules) via the
process image
(PII and PIQ).
Direct reading (with I/O identification ":P") of inputs or writing of outputs is not possible in the
safety program.
Updating the process image
The process image of the inputs of F-I/O is updated at the start of the F-runtime group. The
process image of the outputs of F-I/O is updated at the end of the F-runtime group (see
Program structure of the safety program (S7-300, S7-400) (Page 111) or Program structure
of the safety program (S7-1200, S7-1500) (Page 114)). For additional information on
updating the process image, refer to the note in Data Transfer from the Safety Program to
the Standard User Program (Page 196).
The communication required between the F-CPU (process image) and the F-I/O to update
the process image uses a special safety protocol in accordance with PROFIsafe.
F-I/O access
6.1 Addressing F-I/O
SIMATIC Safety - Configuring and Programming
158 Programming and Operating Manual, 10/2018, A5E02714440-AH
Rules
You may only address a channel (channel value and value status) of an F-I/O in
one
F-runtime group. The first programmed addressing defines the assignment for the F-
runtime group.
You may only address a channel (channel value and value status) of an F-I/O with a unit
that matches the data type of the channel.
Example: To access input channels of data type BOOL, you must use the "input (bit)" (I
x.y) unit. Access to the 16 consecutive input channels of the data type BOOL via the unit
"input word" (IW x) is not possible.
Address only inputs and outputs that reference an actually existing channel (channel
value and value status) (e.g. for an F-DO 10xDC24V with start address 10 only the
outputs Q10.0 to Q11.1 for the channel values and the inputs I10.0 to I11.1 for the value
status). Keep in mind that due to the special safety protocol, the F-I/O occupies a larger
area of the process image than is required for the existing and enabled channels on the
F-I/O (channel values and value status). To find the area of the process image where the
channels (channel values and value status) are stored (channel structure), refer to the
relevant manuals for the F-I/O.
Channels can be disabled for certain F-I/O (such as ET 200SP fail-safe modules or S7-
1500/ET 200MP fail-safe modules). Address only channels (channel value and value
status) that are enabled in the hardware configuration. When you address channels that
are disabled in the hardware configuration, a warning may be output when compiling the
safety program.
For certain F-I/O (such as ET 200SP fail-safe modules or S7-1500/ET 200MP fail-safe
modules), a "1oo2 (2v2) sensor evaluation" can be specified. Two channels are grouped
into one channel pair in this case, and the result of the "1oo2 sensor evaluation" is usually
provided under the address of the channel with the lower channel number (see relevant
manuals of the F-I/O). Address only this channel (channel value and value status) of the
channel pair. When you address a different channel, a warning may be output when
compiling the safety program.
WARNING
If you use an additional component between the F-CPU (S7-300/400) and the F-I/O that
copies the safety message frame in accordance with PROFIsafe between the F-CPU (S7-
300/400) and F-I/O per user program, you must test all safety functions affected by the
copy function whenever you change the user-programmed copy function.
(S049)
See also
Safety-Related I-Slave-Slave Communication - F-I/O Access (Page 246)
Value status (S7-1200, S7-1500) (Page 159)
F-I/O access
6.2 Value status (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 159
6.2
Value status (S7-1200, S7-1500)
Properties
The value status is additional binary information for the channel value of an F-I/O. The value
status is entered in the process image input (PII).
The value status is supported by S7-1500/ET 200MP, ET 200SP, ET 200eco PN, ET 200S,
ET 200iSP, ET 200pro, S7-1200 fail-safe modules or S7-300 F-SMs, fail-safe I/O standard
devices as well as fail-safe DP standard slaves that support the "RIOforFA-Safety" profile.
Information about the value status can be found in the documentation of the respective F-
I/O.
We recommend you amend the name of the channel value with "_VS" for the value status,
for example, "TagIn_1_VS".
The value status provides information on the validity of the corresponding channel value:
1: A valid process value is output for the channel.
0: A fail-safe value is output for the channel.
The channel value and value status of an F-I/O can only be accessed from the same F-
runtime group.
Location of value status bits in the PII for F-I/O with digital inputs
The value status bits come straight after the channel values in the PII.
Table 6- 1 Example: Address assignment in PII for F-I/O with 16 digital input channels
Byte in the F-CPU
Assigned bits in F-CPU per F-I/O:
7
6
5
4
3
2
1
0
x + 0
DI
7
DI
6
DI
5
DI
4
DI
3
DI
2
DI
1
DI
0
x + 1
DI15
DI14
DI13
DI12
DI11
DI10
DI9
DI8
x + 2
Value
status DI7
Value
status DI6
Value
status DI5
Value
status DI4
Value
status DI3
Value
status DI2
Value
status DI1
Value
status DI0
x + 3
Value
status DI
15
Value
status DI
14
Value
status DI
13
Value
status DI
12
Value
status DI
11
Value
status DI
10
Value
status DI
9
Value
status DI
8
x = Module start address
The location of the channel values in the PII can be found in the device manual for the F-I/O.
F-I/O access
6.2 Value status (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
160 Programming and Operating Manual, 10/2018, A5E02714440-AH
Location of value status bits in the PII for F-I/O with digital outputs
The value status bits in the PII are mapped with the same structure as the channel values in
the PIQ.
Table 6- 2 Example: Address assignment in PIQ for F-I/O with 4 digital output channels
Byte in the F-CPU
Assigned bits in F-CPU per F-I/O:
7
6
5
4
3
2
1
0
x + 0
DQ
3
DQ
2
DQ
1
DQ
0
x = Module start address
Table 6- 3 Example: Address assignment in PII for F-I/O with 4 digital output channels
Byte in the F-CPU
Assigned bits in F-CPU per F-I/O:
7
6
5
4
3
2
1
0
x + 0
Value
status DQ
3
Value
status DQ
2
Value
status DQ
1
Value
status DQ
0
x = Module start address
The location of the channel values in the PIQ can be found in the device manual for the F-
I/O.
Location of value status bits in the PII for F-I/O with digital outputs and digital inputs
The value status bits come directly after the channel values in the PII in the following order:
Value status bits for the digital inputs
Value status bits for the digital outputs
Table 6- 4 Example: Address assignment in PIQ for F-I/O with 2 digital input channels and 1 digital output channel
Byte in the F-CPU
Assigned bit in the F-CPU per F-I/O:
7
6
5
4
3
2
1
0
x + 0
DQ0
x = Module start address
F-I/O access
6.2 Value status (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 161
Table 6- 5 Example: Address assignment in PII for F-I/O with 2 digital input channels and 1 digital output channel
Byte in the F-CPU
Assigned bits in F-CPU per F-I/O:
7
6
5
4
3
2
1
0
x + 0
DI
1
DI
0
x + 1
Value
status DI
1
Value
status DI
0
x + 2
Value
status DQ0
x = Module start address
The location of the channel values in the PII and PIQ can be found in the device manual for
the F-I/O.
Location of value status bits in the PII for F-I/O with analog inputs
The value status bits come directly after the channel values in the PII.
Table 6- 6 Example: Address assignment in PII for F-I/O with 6 analog input channels (data type INT)
Byte in the F-CPU
Assigned bytes/bits in the F-CPU per F-I/O:
7
6
5
4
3
2
1
0
x + 0
Channel value AI
0
...
...
x + 10
Channel value AI
5
x + 12
Value
status AI5
Value
status AI4
Value
status AI3
Value
status AI2
Value
status AI1
Value
status AI0
x = Module start address
The location of the channel values in the PII can be found in the device manual for the F-I/O.
Location of value status bits in the PII for F-I/O with analog outputs
The value status bits are mapped in the PII.
Table 6- 7 Example: Address assignment in PIQ for F-I/O with 6 analog output channels (data type INT)
Byte in the F-CPU
Assigned bytes in the F-CPU per F-I/O:
7
6
5
4
3
2
1
0
x + 0
Channel value AO
0
...
...
x + 10
Channel value AO
5
x = Module start address
F-I/O access
6.3 Process Data or Fail-Safe Values
SIMATIC Safety - Configuring and Programming
162 Programming and Operating Manual, 10/2018, A5E02714440-AH
Table 6- 8 Example: Address assignment in PII for F-I/O with 6 analog output channels (data type INT)
Byte in the F-CPU
Assigned bits in F-CPU per F-I/O:
7
6
5
4
3
2
1
0
x + 0
Value
status AO5
Value
status AO4
Value
status AO3
Value
status AO2
Value
status AO1
Value
status AO0
x = Module start address
The location of the channel values in the PIQ can be found in the device manual for the F-
I/O.
6.3
Process Data or Fail-Safe Values
When are fail-safe values used?
The safety function requires that fail-safe values (0) be used instead of process data for
passivation of the entire F-I/O or individual channels of an F-I/O in the following cases. This
applies both to digital channels (data type BOOL) as well as for analog channels (data type
INT or DINT):
When the F-system starts up
When errors occur during safety-related communication (communication errors) between
the F-CPU and F-I/O using the safety protocol in accordance with PROFIsafe
When F-I/O faults and channel faults occur (such as wire break, short circuit, and
discrepancy errors)
As long as you enable passivation of the F-I/O with PASS_ON = 1 in the F-I/O DB (see
below)
As long as you disable the F-I/O with DISABLE = 1 in the F-I/O DB (see below)
F-I/O access
6.3 Process Data or Fail-Safe Values
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 163
Fail-safe value output for F-I/O/channels of an F-I/O
When
passivation
occurs for an
F-I/O with inputs
, the F-system provides the safety program
with fail-safe values (0) in the PII instead of the process data pending at the fail-safe inputs
of the F-I/O.
The overflow or underflow of a channel of the
SM 336; AI 6 x 13Bit
or
SM 336; F-AI 6 x 0/4 ... 20 mA HART
is recognized by the F-system as an F-I/O/channel
fault. The fail-safe value 0 is provided in place of 7FFFH (for overflow) or 8000H (for
underflow) in the PII for the safety program.
If you want to process fail-safe values other than "0" in the safety program for an F-I/O with
inputs
for analog channels of data type INT or DINT
, you can assign individual fail-safe
values for QBAD = 1 and value status = 0 or QBAD_I_xx/QBAD_O_xx = 1 (instructions
JMP/JMPN, LABEL and MOVE). For details about the characteristics go to
QBAD/PASS_OUT/DISABLED/QBAD_I_xx/QBAD_O_xx and value status (Page 171).
WARNING
For an F-I/O with digital input channels (data type BOOL), the value provided in the PII
must always be processed in the safety program, regardless of the value status or
QBAD/QBAD_I_xx.
(S009)
When
passivation
occurs in an
F-I/O with outputs
, the F-system outputs fail-safe values (0)
at the fail-safe outputs instead of the output values provided by the safety program in the
PIQ.
State of associated PAA/PIQ
by ...
F-I/O with "RIOforFA-Safety"
profile with S7-1200/1500
F-CPUs
F-I/O without "RIOforFA-
Safety" profile with S7-
1200/1500 F-CPUs
F-I/O with S7-300/400
F-CPUs
Startup of F-system
The F-system overwrites the PII/PIQ with fail-safe values (0).
Communication errors
F-I/O faults
The F-system overwrites the
PII with fail-safe values (0).
In the PII the values formed
in the safety program are
retained.
The F-system overwrites the PII/PIQ with fail-safe values
(0).
Channel faults in configura-
tion of passivation for com-
plete F-I/O
Channel faults during config-
uration of channel-granular
passivation
For the affected channels: The F-system overwrites the
PII/PIQ with fail-safe values (0).
As long as passivation of the
F-I/O is activated in the F-I/O
DB with PASS_ON = 1
The F-system overwrites the PII/PIQ with fail-safe values (0).
As long as the F-I/O is deac-
tivated in the F-I/O DB with
DISABLE = 1
The F-system overwrites the PII/PIQ with fail-safe values
(0).
-
F-I/O access
6.3 Process Data or Fail-Safe Values
SIMATIC Safety - Configuring and Programming
164 Programming and Operating Manual, 10/2018, A5E02714440-AH
Reintegration of F-I/O/channels of an F-I/O
The switchover from fail-safe values (0) to process data (
reintegration of an F-I/O
) takes
place
automatically
or following
user acknowledgment
in the F-I/O DB. The reintegration
method depends on the following:
The reason for passivation of the F-I/O or channels of the F-I/O
At F-I/Os without the "Channel failure acknowledge" channel parameter on the value of
the ACK_NEC variable of the associated F-IO data blocks (Page 165).
At F-I/Os with the "Channel failure acknowledge" channel parameter (for example F-
modules S7-1500 / ET 200 MP / F-modules SIMATIC S7-1200) on the value of the
channel parameter.
For fail-safe GSD based DP slaves / GSD based I/O devices with "RIOforFA-Safety" profile,
consult the respective documentation.
Note
Note that for channel faults in the F
-I/O, channel-granular passivation takes place if
configured accordingly in the
hardware and network editor
. For the concerned channels, fail-
safe values (0) are output.
Reintegration after channel faults rein
tegrates all channels whose faults were eliminated;
faulty channels remain passivated.
See also
Configuring F-I/O (Page 53)
F-I/O access
6.4 F-I/O DB
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 165
6.4
F-I/O DB
Introduction
An F-I/O DB is automatically generated for each F-I/O (in safety mode) when the F-I/O is
configured in the
hardware and network editor
. The F-I/O DB contains tags that you can
evaluate or can/must write to in the safety program. It is not permitted to change the initial
values of the tags directly in the F-I/O DB. When an F-I/O is deleted, the associated F-I/O
DB is also deleted.
Access to an F-I/O DB
You access tags of the F-I/O DB for the following reasons:
For reintegration of F-I/O after communication errors, F-I/O faults, or channel faults
If you want to passivate the F-I/O depending on particular states of your safety program
(for example, group passivation)
If you want to deactivate the F-I/O (for example, configuration control)
For changing parameters for fail-safe GSD based DP slaves/GSD based I/O devices
If you want to evaluate whether fail-safe values or process data are output
F-I/O access
6.4 F-I/O DB
SIMATIC Safety - Configuring and Programming
166 Programming and Operating Manual, 10/2018, A5E02714440-AH
6.4.1
Tags of the F-I/O DB
The following table presents the variables of an F-I/O DB:
Tag
Data type
Function
Initial
value
Tags that you
can or must
write
PASS_ON
BOOL
1=enable passivation
0
ACK_NEC BOOL 1=acknowledgment for reintegration re-
quired in the event of F-I/O or channel
faults
1
ACK_REI
BOOL
1=acknowledgment for reintegration
0
IPAR_EN BOOL Tag for parameter reassignment of fail-safe
GSD based DP slaves/GSD based I/O
devices or, in the case of
SM 336; F-AI 6 x 0/4 ... 20 mA HART, for
enabling HART communication
0
DISABLE*
BOOL
1=Deactivate F-I/O
0
Tags
that you
can evaluate
PASS_OUT
BOOL
Passivation output
1
QBAD
BOOL
1=Fail-safe values are output
1
ACK_REQ BOOL 1=Acknowledgment request for reintegra-
tion
0
IPAR_OK BOOL Tag for parameter reassignment of fail-safe
GSD based DP slaves/GSD based I/O
devices or, in the case of
SM 336; F-AI 6 x 0/4 ... 20 mA HART, for
enabling HART communication
0
DIAG
BYTE
Non-fail safe service information
0
DISABLED* BOOL 1=F-I/O is deactivated 0
QBAD_I_xx BOOL 1=fail-safe values are output to input chan-
nel xx (S7-300/400)
1
QBAD_O_xx BOOL 1=fail-safe values are output to output
channel xx (S7-300/400)
1
* As of Safety-System Version 2.1 for S7-1200/1500
F-I/O access
6.4 F-I/O DB
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 167
Differences in evaluation in S7-1200/1500 F-CPUs and S7-300/400
The following table describes the differences in the evaluation of tags of the F-I/O DB and
the value status depending on the F-I/O and F-CPU used.
Tag in the F-I/O DB or
value status
F-I/O with
"RIOforFA-Safety"
profile with S7-
1200/1500 F-CPU
F-I/O without profile
"RIOforFA-Safety" with S7-
1200/1500 F-CPU
F-I/O with S7-300/400 F-
CPU
ACK_NEC
2
x
x
QBAD3 x x x
PASS_OUT
3
x
x
x
QBAD_I_xx1 x
QBAD_O_xx
1
x
Wertstatus
1
x
x
1
QBAD_I_xx and QBAD_O_xx display the validity of the channel value channel-granular and thus
correspond to the inverted value status with S7-1200/1500. Value status or QBAD_I_xx and
QBAD_O_xx are not available with fail-safe DP GSD based slaves or fail-safe GSD based I/O de-
vices without the "RIOforFA-Safety" profile.
2
In the case of F-I/Os that support the "Channel failure acknowledge" channel parameter (for ex-
ample S7-1500/ET 200MP F-modules or S7-1200 F-modules), this replaces the ACK_NEC varia-
ble of the F-IO data block.
3
For details about the characteristics, see "QBAD/PASS_OUT/DISABLED/QBAD_I_xx/QBAD_O_xx
and value status"
6.4.1.1
PASS_ON
The PASS_ON tag allows you to enable passivation of an F-I/O, for example, depending on
particular states in your safety program.
Using the PASS_ON tag in the F-I/O DB, you can passivate F-I/O; channel-granular
passivation is not possible.
As long as PASS_ON = 1,
passivation
of the associated F-I/O occurs.
F-I/O access
6.4 F-I/O DB
SIMATIC Safety - Configuring and Programming
168 Programming and Operating Manual, 10/2018, A5E02714440-AH
6.4.1.2
ACK_NEC
If an F-I/O fault is detected by the F-I/O,
passivation
of the relevant F-I/O occurs. If channel
faults are detected and channel granular passivation is configured, the relevant channels are
passivated. If passivation of the entire F-I/O is configured, all channels of the relevant F-I/O
are passivated. Once the F-I/O fault or channel fault has been eliminated,
reintegration
of the
relevant F-I/O occurs, depending on ACK_NEC:
With ACK_NEC = 0, you can assign an
automatic reintegration
.
With ACK_NEC = 1, you can assign a
reintegration
by
user acknowledgment
.
WARNING
The parameter assignment of the ACK_NEC = 0 tag is only allowed if automatic
reintegration is permitted for the relevant process from a safety standpoint.
(S010)
Note
The initial value for ACK_NEC is 1 after creation of the F
-I/O DB. If you do not require
automatic reintegration, you do not have to write ACK_NEC.
See also
After F-I/O or channel faults (Page 180)
6.4.1.3
ACK_REI
When the F-system detects a communication error or an F-I/O fault for an F-I/O, the relevant
F-I/O is passivated. If channel faults are detected and channel granular passivation is
configured, the relevant channels are passivated. If passivation of the entire F-I/O is
configured, all channels of the relevant F-I/O are passivated.
Reintegration
of the
F-I/O/channels of the F-I/O after the fault has been eliminated requires a
user
acknowledgment
with a positive edge at variable ACK_REI of the F-I/O DB:
After every communication error
After F-I/O or channel faults only with parameter assignment "Channel failure
acknowledgement = manual" or ACK_NEC = 1
Reintegration after channel faults reintegrates all channels whose faults were eliminated.
Acknowledgment is not possible until tag ACK_REQ = 1.
F-I/O access
6.4 F-I/O DB
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 169
In your safety program, you must provide a user acknowledgment by means of the ACK_REI
tag for each F-I/O.
WARNING
For the user acknowledgement, you must interconnect the ACK_REI tag of the F--I/O DB
with a signal generated by an operator input. An interconnection with an automatically
generated signal is not permitted.
(S011)
Note
Alternatively, you can use the "ACK_GL" i
nstruction to carry out reintegration of the F-I/O
following communication errors or F
-I/O/channel faults (
ACK_GL: Global acknowledgment of
all F
-I/O in an F-runtime group (STEP 7 Safety V15.1) (Page 487)).
6.4.1.4
IPAR_EN
The IPAR_EN tag corresponds to the iPar_EN_C tag in the PROFIsafe bus profile as of
PROFIsafe Specification V1.20 and higher.
Fail-safe GSD based DP slaves/GSD based I/O devices
To find out when this tag must be set or reset when parameters of fail-safe GSD based DP
slaves/GSD based I/O devices are reassigned, consult the PROFIsafe Specification V1.20 or
higher or the documentation for the fail-safe GSD based DP slave/GSD based I/O device.
Note that IPAR_EN = 1 does not trigger passivation of the relevant F-I/O.
If passivation is to occur when IPAR_EN = 1, you must also set tag PASS_ON = 1.
HART communication with SM 336; F-AI 6 x 0/4 ... 20 mA HART
If you set the IPAR_EN tag to "1" while parameter "HART_Tor" = "switchable" is assigned,
the HART communication for the SM 336; F-AI 6 x 0/4 ... 20 mA HART is enabled. Setting
this tag to "0" disables the HART communication. The F-SM acknowledges the enabled or
disabled HART communication with tag IPAR_OK = 1 or 0.
Enable HART communication only when your system is in a status, in which any
reassignment of parameters for an associated HART device can be done without any risk.
If you want to evaluate the "HART communication enabled" status in your safety program,
e.g., for the purpose of programming interlocks, you must build up the information as shown
in the following example. This is necessary to ensure that the information is properly
available even if communication errors occur while the HART communication is enabled with
IPAR_EN = 1. Only change the status of the IPAR_EN tag during this evaluation if there is
no passivation due to a communication error or F-I/O or channel fault.
F-I/O access
6.4 F-I/O DB
SIMATIC Safety - Configuring and Programming
170 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example of enabling HART communication
Additional information on HART communication with SM 336; F-AI 6 x 0/4 ... 20 mA HART
can be found in the Automation System S7-300, ET 200M Distributed I/O System manual,
Fail-Safe Signal Modules (http://support.automation.siemens.com/WW/view/en/19026151)
manual and in the help on the F-module.
6.4.1.5
DISABLE
The DISABLE variable allows you to deactivate an F-I/O.
As long as DISABLI = 1, the associated F-I/Os are
passivated
.
Diagnostics entries of the safety program may no longer be entered in the diagnostics buffer
of the F-CPU for this F-I/O (for example, due to communication error).
Existing diagnostics entries are marked as outgoing.
F-I/O access
6.4 F-I/O DB
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 171
6.4.1.6
QBAD/PASS_OUT/DISABLED/QBAD_I_xx/QBAD_O_xx and value status
The following table set outs differences in the reaction of the channel values and QBAD,
PASS_OUT, DISABLED, QBAD_I_xx/QBAD_O_xx variables and of the value status
depending on the F-I/O and F-CPU used.
Fail-safe value output after...
F-I/O with "RIOforFA-
Safety" profile with S7-
1200/1500 F-CPU
F-I/O without profile
"RIOforFA-Safety" with
S7-1200/1500 F-CPUs
F-I/O with S7-300/400 F-CPU
Startup of F-system
QBAD and PASS_OUT = 1
DISABLED
unchanged
For
all
channels:
Channel value = fail-safe value (0)
Value status = 0*
QBAD and PASS_OUT = 1
For
all
channels:
Channel value = fail-safe value
(0)
QBAD_I_xx and QBAD_O_xx =
1*
Communication errors
F-I/O faults
Channel faults
in configuration of passivation
for complete F-I/O
Channel faults during configu-
ration of channel-granular
passivation
QBAD, PASS_OUT and
DISABLED
unchanged
For the
affected
channels:
Channel value = fail-safe
value (0)
Value status = 0
QBAD and PASS_OUT =
1
DISABLED
unchanged
For the
affected
chan-
nels:
Channel value = fail-safe
value (0)
Value status = 0*
QBAD and PASS_OUT = 1
For the
affected
channels:
Channel value = fail-safe value
(0)
QBAD_I_xx and QBAD_O_xx =
1*
As long as passivation of the
F-I/O is activated in the F-I/O
DB with PASS_ON = 1
QBAD = 1, PASS_OUT and DISABLED
unchanged
For
all
channels:
Channel value = fail-safe value (0)
Value status = 0*
QBAD = 1, PASS_OUT
un-
changed
For
all
channels:
Channel value = fail-safe value
(0)
QBAD_I_xx and QBAD_O_xx =
1*
As long as the F-I/O is deac-
tivated in the F-I/O DB with
DISABLE = 1
QBAD, PASS_OUT and DISABLED = 1
For
all
channels:
Channel value = fail-safe value (0)
Value status = 0*
-
* Value status or QBAD_I_xx and QBAD_O_xx are not available for fail
-safe GSD based DP slaves and fail-safe GSD
based I/O devices without the "RIOforFA-Safety" profile.
F-I/O access
6.4 F-I/O DB
SIMATIC Safety - Configuring and Programming
172 Programming and Operating Manual, 10/2018, A5E02714440-AH
6.4.1.7
ACK_REQ
When the F-system detects a communication error or an F-I/O fault or channel fault for an
F-I/O, the relevant F-I/O or individual channels of the F-I/O are passivated. ACK_REQ = 1
signals that
user acknowledgment
is required for reintegration of the relevant F-I/O or
channels of the F-I/O.
The F-system sets ACK_REQ = 1 as soon as the fault has been eliminated and user
acknowledgment is possible. For channel-granular passivation, the F-system sets
ACK_REQ = 1 as soon as the channel fault is corrected. User acknowledgment is possible
for this fault. Once acknowledgment has occurred, the F-system resets ACK_REQ to 0.
Note
For F
-I/O with outputs, acknowledgment after F-I/O or channel faults may only be possible
some minutes after the fault has been eliminated, until the necessa
ry test signal is applied
(see
F-I/O manuals
).
6.4.1.8
IPAR_OK
The IPAR_OK tag corresponds to the iPar_OK_S tag in the PROFIsafe bus profile,
PROFIsafe Specification V1.20 and higher.
Fail-safe GSD based DP slaves/GSD based I/O devices
To find out how to evaluate this tag when parameters of fail-safe GSD based DP slaves or
GSD based I/O devices are reassigned, consult the PROFIsafe Specification V1.20 or higher
or the documentation for the fail-safe GSD based DP slave/GSD based I/O device.
For HART communication with SM 336; F-AI 6 x 0/4 ... 20 mA HART see Chapter
IPAR_EN
(Page 169).
6.4.1.9
DIAG
The DIAG tag provides non-fail-safe information (1 byte) about errors or faults that have
occurred for service purposes. You can read out this information by means of operator
control and monitoring systems or, if applicable, you can evaluate it in your standard user
program. DIAG bits are saved until you perform an acknowledgment with the ACK_REI tag
or until automatic reintegration takes place.
F-I/O access
6.4 F-I/O DB
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 173
Structure of DIAG
Bit no.
Assignment
Possible error causes
Remedies
Bit 0 Timeout detected by F-I/O The PROFIBUS/PROFINET
connection between F-CPU
and F-I/O is faulty.
The value of the F-monitoring
time for the F-I/O is set too
low.
The F-I/O are receiving invalid
parameter assignment data
or
Check the PROFIBUS/PROFINET connec-
tion and ensure that there are no external
sources of interference.
Check the parameter assignment of the
F-I/O. If necessary, set a higher value for the
monitoring time. Recompile the hardware
configuration, and download it to the F-CPU.
Recompile the safety program.
Check the diagnostics buffer of the F-I/O.
Turn the power of the F-I/O off and back on.
Internal F-I/O fault
or
Replace F-I/O
Internal F-CPU fault
Replace F-CPU
Bit 1 F-I/O fault or channel fault
detected by F-I/O1
See
F-I/O manuals
See
F-I/O manuals
Bit 2 CRC error or sequence
number error detected by F-
I/O
See description for bit 0 See description for bit 0
Bit 3
Reserved
Bit 4 Timeout detected by F-
system
See description for bit 0 See description for bit 0
Bit 5 Sequence number error
detected by F-system
2
See description for bit 0 See description for bit 0
Bit 6 CRC-error detected by F-
system
See description for bit 0 See description for bit 0
Bit 7
Addressing error
3
Contact Service & Support
1
Not for F-I/O that support the "RIOforFA-Safety" profile.
2
For S7-300/400 F-CPUs only
3 For S7-1200/1500 F-CPUs only
F-I/O access
6.4 F-I/O DB
SIMATIC Safety - Configuring and Programming
174 Programming and Operating Manual, 10/2018, A5E02714440-AH
6.4.2
Accessing tags of the F-I/O DB
Name of the F-I/O DB
An F-I/O DB is automatically generated for each F-I/O when the F-I/O is configured in the
hardware and network editor
and a name is generated at the same time.
The name is formed by combining the fixed prefix "F", the start address of the F-I/O, and the
names entered in the properties for the F-I/O in the
hardware and network editor
(example:
F00004_F-DI24xDC24V_1).
Changing the name and number of the F-I/O DB
The name and number of the F-I/O DB are assigned automatically when the F-I/O are
configured. The naming scheme depends on the setting in the Safety Administration Editor
("Specifies driver I-DBs without prefix (Page 90)"). You change the number in the
"Properties" tab of the associated F-I/O. You change the name by renaming the F-I/O.
Rule for accessing tags of the F-I/O DB
Tags of the F-I/O DB of an F-I/O can only be accessed from the F-runtime group from which
the channels of this F-I/O are accessed (if access is made).
"Fully qualified DB access"
You can access the tags of the F-I/O DB via a "fully qualified DB access" (that is, by
specifying the name of the F-I/O DB and by specifying the name of the tag).
Example of evaluating the QBAD tag
See also
F-I/O DB (Page 165)
F-I/O access
6.5 Passivation and reintegration of F-I/O
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 175
6.5
Passivation and reintegration of F-I/O
Overview
In the following you can find information on passivation and reintegration of F-I/O.
Signal sequence charts
The signal sequences presented below represent typical signal sequences for the indicated
behavior.
Actual signal sequences and, in particular, the relative position of the status change of
individual signals can deviate from the given signal sequences within the scope of known
"fuzzy" cyclic program execution factors, depending on the following:
The F-I/O used
The F-CPU used
The cycle time of the (F-)OB in which the associated F-runtime group is called
The target rotation time of the PROFIBUS DP or the update time of the PROFINET IO
Note
The signal sequences shown refer to the status of signals in the user's safety program.
6.5.1
After startup of F-system
Behavior after a startup
Fail-safe value output after
startup of the F-system
F-I/O with "RIOforFA-Safety"
profile with
S7-1200/1500 F-CPU
F-I/O without profile
"RIOforFA-Safety" with
S7-1200/1500 F-CPU
Every F-I/O with S7-300/400
F-CPU
Passivation of the entire F-
I/O occurs during startup.
QBAD and PASS_OUT = 1
For
all
channels:
Channel value = fail-safe value (0)
Value status = 0*
QBAD and PASS_OUT = 1
For
all
channels:
Channel value = fail-safe
value (0)
QBAD_I_xx and QBAD_O_xx
= 1*
* Value status or QBAD_I_xx and QBAD_O_xx are not available for fail
-safe GSD based DP slaves and fail-safe GSD
based I/O devices without the "RIOforFA-Safety" profile.
F-I/O access
6.5 Passivation and reintegration of F-I/O
SIMATIC Safety - Configuring and Programming
176 Programming and Operating Manual, 10/2018, A5E02714440-AH
Reintegration of F-I/O
Reintegration
of the F-I/O, i.e. the provision of process values in the PII or the output of
process values provided in the PIQ at the fail-safe outputs, takes place
automatically
,
regardless of the setting at the ACK_NEC tag or the configuration "Channel failure
acknowledge", no sooner than the second cycle of the F-runtime group after startup of the
F-system.
You can find additional information on pending F-communication, F-I/O or channel errors
during startup of the F-system in the sections After communication errors (Page 178) and
After F-I/O or channel faults (Page 180).
For fail-safe GSD based DP slaves/GSD based I/O devices with "RIOforFA-Safety" profile,
consult the respective documentation for the fail-safe GSD based DP slave/GSD based I/O
device.
Depending on the F-I/O you are using and the cycle time of the F-runtime group and
PROFIBUS DP/PROFINET IO, several cycles of the F-runtime group can elapse before
reintegration occurs.
If communication between the F-CPU and F-I/O takes longer to establish than the F-
monitoring time set in the properties for the F-I/O, automatic reintegration does not take
place.
F-I/O access
6.5 Passivation and reintegration of F-I/O
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 177
Signal sequence for passivation and reintegration of F-I/O after F-system startup
Example for an F-I/O with inputs:
Startup of F-system/passivation
Automatic reintegration (e.g. third cycle)
WARNING
When an F-CPU is switched from STOP to RUN mode, the standard user program starts
up in the usual way. When the safety program is started up, all F-DBs are initialized with
the values from the load memory - as is the case with a cold restart. This means that saved
error information is lost.
The F-system automatically reintegrates the F-I/O, as described above.
An operating error or an internal error can also trigger a startup of the safety program with
the values from the load memory. If your process does not allow such a startup, you must
program a restart/startup protection in the safety program: The output of process data must
be blocked until manually enabled. This enable must not occur until it is safe to output
process data and faults have been corrected.
(S008)
F-I/O access
6.5 Passivation and reintegration of F-I/O
SIMATIC Safety - Configuring and Programming
178 Programming and Operating Manual, 10/2018, A5E02714440-AH
6.5.2
After communication errors
Behavior after communication errors
Fail-safe value output after
communication errors
F-I/O with "RIOforFA-Safety"
profile with S7-1200/1500 F-
CPU
F-I/O without profile
"RIOforFA-Safety" with
S7-1200/1500 F-CPU
Every F-I/O with S7-300/400
F-CPU
If a communication error
between the F-CPU and the
F-I/O is detected, all chan-
nels of the entire F-I/O are
passivated.
QBAD and PASS_OUT = 1
For
all
channels:
Channel value = fail-safe value (0)
Value status = 0*
QBAD and PASS_OUT = 1
For
all
channels:
Channel value = fail-safe
value (0)
QBAD_I_xx and QBAD_O_xx
= 1*
* Value status or QBAD_I_xx and
QBAD_O_xx are not available for fail-safe GSD based DP slaves and fail-safe GSD
based I/O devices without the "RIOforFA-Safety" profile.
Reintegration of F-I/O
Reintegration
of the relevant F-I/O, that is, provision of process data in the PII or output of
process data provided in the PIQ at the failsafe outputs, takes place only when the following
occurs:
All communication errors have been eliminated and the F-system has set tag
ACK_REQ = 1
A
user acknowledgment
with a positive edge has occurred:
At the ACK_REI tag of the F-I/O DB (Page 168) or
At the ACK_REI_GLOB input of the "ACK_GL" instruction (ACK_GL: Global
acknowledgment of all F-I/O in an F-runtime group (STEP 7 Safety V15.1) (Page 487))
F-I/O access
6.5 Passivation and reintegration of F-I/O
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 179
Signal sequence for passivation and reintegration of F-I/O after communication errors
Example for an F-I/O with inputs:
Communication error/passivation
All communication errors have been eliminated
Reintegration
See also
Implementing User Acknowledgment in the Safety Program of the F-CPU of a DP Master or
IO controller (Page 187)
Implementing user acknowledgment in the safety program of the F-CPU of a I-slave or I-
device (Page 192)
F-I/O access
6.5 Passivation and reintegration of F-I/O
SIMATIC Safety - Configuring and Programming
180 Programming and Operating Manual, 10/2018, A5E02714440-AH
6.5.3
After F-I/O or channel faults
Behavior after F-I/O faults
Fail-safe value output after
F-I/O faults
F-I/O with "RIOforFA-Safety"
profile with S7-1200/1500 F-
CPU
F-I/O without profile
"RIOforFA-Safety" with S7-
1200/1500 F-CPU
Every F-I/O with S7-300/400
F-CPU
If an F-I/O fault is detected
by the F-system, passivation
of all channels of the entire
F-I/O occurs.
QBAD and PASS_OUT = 1
For
all
channels:
Channel value = fail-safe value (0)
Value status = 0*
QBAD and PASS_OUT = 1
For
all
channels:
Channel value = fail-safe
value (0)
QBAD_I_xx and QBAD_O_xx
= 1*
* Value status or QBAD_I_xx and QBAD_O_xx are not available for fail
-safe GSD based DP slaves and fail-safe GSD
based I/O devices without the "RIOforFA-Safety" profile.
Behavior after channel fault
Fail-safe value output after
channel faults
F-I/O with "RIOforFA-Safety"
profile with S7-1200/1500 F-
CPU
F-I/O without profile
"RIOforFA-Safety" with S7-
1200/1500 F-CPU
Every F-I/O with S7-300/400
F-CPU
When passivation for
com-
plete
F-I/O is configured:
If a channel fault is detected
by the F-system, passivation
of all channels of the entire
F-I/O occurs.
QBAD and PASS_OUT = 1
For
all
channels:
Channel value = fail-safe value (0)
Value status = 0*
QBAD and PASS_OUT = 1
For
all
channels:
Channel value = fail-safe
value (0)
QBAD_I_xx and QBAD_O_xx
= 1*
With configuration of
chan-
nel-granular
passivation:
If a channel fault is detected
by the F-system, passivation
of all the affected channels
of the entire F-I/O occurs.
QBAD and PASS_OUT
un-
changed
For the
affected
channels:
Channel value = fail-safe
value (0)
Value status = 0
QBAD and PASS_OUT = 1
For the
affected
channels:
Channel value = fail-safe
value (0)
Value status = 0*
QBAD and PASS_OUT = 1
For the
affected
channels:
Channel value = fail-safe
value (0)
QBAD_I_xx and QBAD_O_xx
= 1*
* Value status or QBAD_I_xx and QBAD_O_xx are not available for fail
-safe GSD based DP slaves and fail-safe GSD
based I/O devices without the "RIOforFA-Safety" profile.
F-I/O access
6.5 Passivation and reintegration of F-I/O
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 181
Reintegration of F-I/O
Reintegration
of the relevant F-I/O or the relevant channels of the F-I/O, that is, provision of
process data in the PII or output of process data provided in the PIQ at the failsafe outputs,
takes place only when the following occurs:
All F-I/O or channel faults have been eliminated.
If you have configured channel-granular passivation for the F-I/O, the relevant channels are
reintegrated once the fault is corrected; any faulty channels remain passivated.
Reintegration is performed depending on your setting for the ACK_NEC tag or the "Channel
failure acknowledge" parameter (configuration of the S7-1500/ET 200MP F-module and
S7-1200 F-module)
With ACK_NEC = 0 or the configuration "Channel failure acknowledge = automatic",
automatic reintegration
is performed as soon as the F-system detects that the fault has
been corrected. For F-I/O with inputs, reintegration takes place right away. For F-I/O with
outputs or F-I/O with inputs and outputs, depending on the F-I/O you are using,
reintegration can take several minutes, first after the necessary test signals have been
applied, which are used by the F-I/O to determine that the fault has been eliminated.
With ACK_NEC = 1 or the configuration "Channel failure acknowledge = manual",
reintegration is performed only as a result of user acknowledgment with a positive edge
at the ACK_REI tag of the F-I/O DB or at the ACK_REI_GLOB input of the "ACK_GL"
instruction. Acknowledgment can be made as soon as the F-system detects that the fault
has been eliminated and tag ACK_REQ = 1 has been set.
For fail-safe GSD based I/O devices with "RIOforFA-Safety" profile, consult the respective
documentation for the fail-safe GSD based I/O device .
WARNING
Following a power failure of the F-I/O lasting less than the assigned F-monitoring time
for the F-I/O, automatic reintegration can occur regardless of your setting for the
ACK_NEC tag, as described for the case when ACK_NEC = 0 or configuration "Channel
failure acknowledge = automatic".
If automatic reintegration is not permitted for the relevant process in this case, you must
program startup protection by evaluating tags QBAD or QBAD_I_xx and QBAD_O_xx or
value status or PASS_OUT.
In the event of a power failure of the F-I/O lasting longer than the specified F-monitoring
time for the F-I/O, the F-system detects a communication error.
(S012)
F-I/O access
6.5 Passivation and reintegration of F-I/O
SIMATIC Safety - Configuring and Programming
182 Programming and Operating Manual, 10/2018, A5E02714440-AH
Signal sequence for passivation and reintegration of F-I/O after F-I/O faults or channel faults when
ACK_NEC = 0 or configuration "Channel failure acknowledge = automatic" (for passivation of entire
F-I/O after channel faults)
Example for an F-I/O with inputs:
F-I/O or channel faults
Passivation
F-I/O or channel faults corrected
Automatic reintegration
Signal sequence for passivation and reintegration of F-I/O after F-I/O faults or channel faults when
ACK_NEC = 1 or configuration "Channel failure acknowledge = manual" (for passivation of entire
F-I/O after channel faults)
For the signal sequence for passivation and reintegration of F-I/O after F-I/O or channel
faults when ACK_NEC = 1 or configuration "Channel failure acknowledge = manual" (initial
value), see After communication errors (Page 178).
F-I/O access
6.5 Passivation and reintegration of F-I/O
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 183
Signal sequence for passivation and reintegration of F-I/O after channel faults when ACK_NEC = 1 or
configuration "Channel failure acknowledge = manual" (for channel-granular passivation)
Example for an F-I/O with inputs:
Channel fault for channel 0/passivation of channel 0
Reintegration of channel 0
Channel fault for channel 1/passivation of channel 1
Channel fault eliminated for channel 1
Channel fault eliminated for channel 0
Reintegration of channel 1
F-I/O access
6.5 Passivation and reintegration of F-I/O
SIMATIC Safety - Configuring and Programming
184 Programming and Operating Manual, 10/2018, A5E02714440-AH
6.5.4
Group passivation
Programming a group passivation
If you want to enable passivation of additional F-I/O when an F-I/O or a channel of an F-I/O
is passivated by the F-system, you can use the PASS_OUT/PASS_ON tags to perform
group passivation
of the associated F-I/O.
Group passivation by means of PASS_OUT/PASS_ON can, for example, be used to force
simultaneous reintegration of all F-I/O after startup of the F-system.
For group passivation, you must OR all PASS_OUT tags of the F-I/O in the group and assign
the result to all PASS_ON tags of the F-I/O in the group.
During use of fail-safe values (0) due to group passivation by means of PASS_ON = 1, the
QBAD tag of the F-I/O of this group = 1.
Note
Note the different behavior of PASS_OUT for F
-I/O with/without "RIOforFA-Safety" profile
(see table in section
QBAD/PASS_OUT/DISABLED/QBAD_I_xx/QBAD_O_xx and value
status
(Page 171)).
Example of group passivation
F-I/O access
6.5 Passivation and reintegration of F-I/O
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 185
Reintegration of F-I/O
Reintegration
of F-I/O passivated by group passivation occurs
automatically
, if a
reintegration (
automatic
or
through user acknowledgment
) occurs for the F-I/O that triggered
the group passivation (PASS_OUT = 0).
Signal sequence for group passivation following communication error
Example for two F-I/O with inputs:
Communication error in F-I/O A
Passivation of F-I/O A
Passivation of F-I/O B
Communication error in F-I/O A corrected and acknowledged
Reintegration F-I/O A and B
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 187
Implementation of user acknowledgment
7
7.1
Implementing User Acknowledgment in the Safety Program of the
F-CPU of a DP Master or IO controller
Options for user acknowledgment
Depending on the result of the risk analysis, you have the following options for implementing
a user acknowledgment:
An acknowledgment key that you connect to an F-I/O with inputs
An acknowledgment key that you connect to an standard I/O with inputs
An HMI system
User acknowledgment by means of acknowledgment key
Note
When you implement user acknowledgment by means of acknowledgment key, and a
communication error, an F
-I/O fault, or a channel fault occurs in the F-I/O to which the
acknowledgment key is connected, then it will not be possible to acknowledge the
reintegration of this F
-I/O.
This "blocking" can only be removed by a STOP
-to-RUN transition of the F-CPU.
Conseque
ntly, it is recommended that you also provide for an acknowledgment by means of
an HMI system, in order to acknowledge reintegration of an F
-I/O to which an
acknowledgment key is connected.
A user acknowledgment may be issued using an acknowledgment key co
nnected to a
standard I/O with inputs if this risk analysis allows this.
User acknowledgment by means of an HMI system
For implementation of a user acknowledgment by means of an HMI system, the ACK_OP:
Fail-safe acknowledgment (STEP 7 Safety V15.1) (Page 577) instruction is required.
Implementation of user acknowledgment
7.1 Implementing User Acknowledgment in the Safety Program of the
F-CPU of a DP Master or IO controller
SIMATIC Safety - Configuring and Programming
188 Programming and Operating Manual, 10/2018, A5E02714440-AH
Procedure for programming user acknowledgment by means of an HMI system (S7-300, S7-400)
1. Select the "ACK_OP" instruction in the "Instructions" task card and place it in your safety
program. The acknowledgment signal for evaluating user acknowledgments is provided
at output OUT of ACK_OP.
2. On your HMI system, set up a field for manual entry of an "acknowledgment value" of "6"
(1st step in acknowledgment) and an "acknowledgment value" of "9" (2nd step in
acknowledgment).
or
Assign function key 1 to transfer an "acknowledgment value" of "6" (1st step in
acknowledgment) once, and function key 2 to transfer an "acknowledgment value" of "9"
(2nd step in acknowledgment) once. You need to assign the in/out IN (in the data area of
the ACK_OP instruction) to the field or the function keys.
3. Optional: In your HMI system, evaluate output Q in the instance DB of ACK_OP to show
the time frame within which the 2nd step in acknowledgment must occur or to indicate
that the 1st step in acknowledgment has already occurred.
If you want to perform a user acknowledgment exclusively from a programming device or PC
using the watch table (monitor/modify tag) without having to disable safety mode, then you
must transfer an operand (memory word or DBW of a DB of the standard user program) at
in/out IN when calling ACK_OP. You can then transfer "acknowledgment values" "6" and "9"
on the programming device or PC by modifying the memory word or DBW of a DB once. The
memory word or DBW of a DB must not be written by the program.
Note
If you connect the in/out IN to a memory word or DBW of a DB, you have use a separa
te
memory word or DBW of a DB of the standard user program for each instance of the
ACK_OP instruction at the in/out IN.
WARNING
The two acknowledgment steps must
not
be triggered by one single operation, for example
by automatically storing them along with the time conditions in a program and using a
function key to trigger them.
Having two separate acknowledgment steps also prevents erroneous triggering of an
acknowledgment by your non-fail-safe HMI system.
(S013)
Implementation of user acknowledgment
7.1 Implementing User Acknowledgment in the Safety Program of the
F-CPU of a DP Master or IO controller
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 189
WARNING
If you have HMI systems and F-CPUs that are interconnected and use the ACK_OP
instruction for fail-safe acknowledgment, you need to ensure that the intended F-CPU will
be addressed
before
you perform the two acknowledgment steps.
To do this, store a network-wide* unique name for the F-CPU in a DB of your standard
user program in each F-CPU.
In your HMI system, set up a field from which you can read out the F-CPU name from
the DB online before executing the two acknowledgment steps.
Optional:
in your HMI system, set up a field to permanently store the F-CPU name. Then, you can
determine whether the intended F-CPU is being addressed by simply comparing the F-
CPU name read out online with the permanently stored name.
(S014)
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet.
Note
The configuration of your operator control and monit
oring system does not have any effect
on the collective F
-signature.
Procedure for programming user acknowledgment by means of an HMI system (S7-1200, S7-1500)
1. Select the "ACK_OP" instruction in the "Instructions" task card and place it in your safety
program. The acknowledgment signal for evaluating user acknowledgments is provided
at output OUT of ACK_OP.
2. Assign the ACK_ID input an identifier between 9 and 30000 for the acknowledgment.
3. Assign the in/out IN a memory word or DBW of a DB of the standard user program.
Note
You need to provide the in/out parameter IN with a separate memory word or DBW of a
DB of the standard user program for each instance of the ACK_OP instruction.
Implementation of user acknowledgment
7.1 Implementing User Acknowledgment in the Safety Program of the
F-CPU of a DP Master or IO controller
SIMATIC Safety - Configuring and Programming
190 Programming and Operating Manual, 10/2018, A5E02714440-AH
4. On your HMI system, set up a field for manual entry of an "acknowledgment value" of "6"
(1st step in acknowledgment) and the "Identifier" configured at the ACK_ID input (2nd
step in acknowledgment).
or
Allocate a function key 1 for a one-time transfer of the "acknowledgment value" of "6" (1st
step in acknowledgment) and a function key 2 for a one-time transfer of the "Identifier" set
at the ACK_ID input (2nd step in acknowledgment).
You need to assign memory word or the DBW of the DB of the standard user program
assigned to the in/out IN to the field or the function keys.
5. Optional: In your HMI system, evaluate output Q in the instance DB of ACK_OP to show
the time frame within which the 2nd step in acknowledgment must occur or to indicate
that the 1st step in acknowledgment has already occurred.
WARNING
The two acknowledgment steps must
not
be triggered by one single operation, for example
by automatically storing them along with the time conditions in a program and using a
function key to trigger them.
Having two separate acknowledgment steps also prevents erroneous triggering of an
acknowledgment by your non-fail-safe HMI system.
(S013)
WARNING
If you have HMI systems and F-CPUs that are interconnected and use the ACK_OP
instruction for fail-safe acknowledgment, you need to ensure that the intended F-CPU will
be addressed
before
you perform the two acknowledgment steps.
Alternative 1:
The value for each identifier of the acknowledgment (ACK_ID input; data type: INT) can
be freely selected in the range from 9 to 30000, but must be unique network-wide* for all
instances of the ACK_OP instruction.
You must supply the ACK_ID input with constant values when calling the instruction.
Direct read or write access in the associated instance DB is not permitted in the safety
program!
Alternative 2:
To do this, store a network-wide* unique name for the F-CPU in a DB of your standard
user program in each F-CPU.
In your HMI system, set up a field from which you can read out the F-CPU name from
the DB online before executing the two acknowledgment steps.
Optional:
in your HMI system, set up a field to permanently store the F-CPU name. Then, you can
determine whether the intended F-CPU is being addressed by simply comparing the
F-CPU name read out online with the permanently stored designation.
(S047)
Implementation of user acknowledgment
7.1 Implementing User Acknowledgment in the Safety Program of the
F-CPU of a DP Master or IO controller
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 191
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet.
Note
The supply of the IN input/output of the ACK_OP instruction as well as the configuration of
your operator control and monitoring system do not have any effect on the F
-collective
signature, the F
-SW collective signature or the signature of the block that calls the ACK_OP
instruction.
Changes to the supply of the IN input/output or to the configuration of your operator control
and monitoring system therefore do not result in a changed F
-collective signature/F-SW
collective signature/signature of the
calling block.
Example of procedure for programming a user acknowledgment for reintegrating an F-I/O
1. Optional: set the ACK_NEC tag in the respective F-I/O DB (Page 168) to "0" if automatic
reintegration (without user acknowledgment) is to take place after an F-I/O fault or a
channel fault.
WARNING
The parameter assignment of the ACK_NEC = 0 tag is only allowed if automatic
reintegration is permitted for the relevant process from a safety standpoint.
(S010)
2. Optional: Evaluate the QBAD or QBAD_I_xx/QBAD_O_xx (S7-300/400) tags or value
status (S7-1200, S7-1500) or DIAG in the respective F-I/O DB to trigger an indicator light
in the event of an error, and/or generate error messages on the HMI system in your
standard user program by evaluating the above tags or the value status. These
messages can be evaluated before performing the acknowledgment operation.
Alternatively, you can evaluate the diagnostic buffer of the F-CPU.
3. Optional: Evaluate the ACK_REQ tag in the respective F-I/O DB, for example, in the
standard user program or on the HMI system, to query or to indicate whether user
acknowledgment is required.
4. Assign the input of the acknowledgment key or the OUT output of the ACK_OP instruction
to the ACK_REI tag in the respective F-I/O DB or the ACK_REI_GLOB input of the
ACK_GL instruction (see above).
Implementation of user acknowledgment
7.2 Implementing user acknowledgment in the safety program of the
F-CPU of a I-slave or I-device
SIMATIC Safety - Configuring and Programming
192 Programming and Operating Manual, 10/2018, A5E02714440-AH
7.2
Implementing user acknowledgment in the safety program of the
F-CPU of a I-slave or I-device
Options for user acknowledgment
You can implement a user acknowledgment by means of:
An HMI system that you can use to access the F-CPU of the I-slave/I-Device
An acknowledgment key that you connect to an F-I/O with inputs that is assigned to the
F-CPU of the I-slave/I-Device
An acknowledgment key that you connect to an F-I/O with inputs that is assigned to the
F-CPU of the DP master/IO controller
These three options are illustrated in the figure below.
1. User acknowledgment by means of an HMI system with which you can access the F-CPU of the
I-slave/I-device
The ACK_OP: Fail-safe acknowledgment (STEP 7 Safety V15.1) (Page 577) instruction is
required to implement user acknowledgment with an HMI system that you can use to access
the F-CPU of the I-slave/I-device.
Programming procedure
Follow the procedure described in "Implementing User Acknowledgment in the Safety
Program of the F-CPU of a DP Master or IO controller (Page 187)" under "Programming
procedure ...".
From your HMI system, you can then directly access the instance DB of ACK_OP in the
I-slave/I-Device.
Implementation of user acknowledgment
7.2 Implementing user acknowledgment in the safety program of the
F-CPU of a I-slave or I-device
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 193
2. User acknowledgment by means of an acknowledgment key at an F-I/O with inputs that are
assigned to the F-CPU of the I-slave/I-device
Note
In
the event of a communication error, F-I/O fault, or channel fault in the F-I/O to which the
acknowledgment key is connected, an acknowledgment for reintegration of this F
-I/O is no
longer possible.
This "blocking" can only be removed by a STOP
-to-RUN transition of the F-CPU of the
I
-slave/I-Device.
Consequently, it is recommended that you also provide for an acknowledgment by means of
an HMI system that you can use to access the F
-CPU of the I-slave/I-Device, in order to
acknowledge reintegration of an F
-I/O to which an acknowledgment key is connected (see
1).
3. User acknowledgment by means of an acknowledgment key at an F-I/O with inputs that are
assigned to the F-CPU of the DP master/IO controller
If you want to use the acknowledgment key that is assigned to the F-CPU at the DP
master/IO controller to perform user acknowledgment in the safety program of the F-CPU of
an I-slave/I-device as well, you must transmit the acknowledgment signal from the safety
program in the F-CPU of the DP master/IO controller to the safety program in the F-CPU of
the I-slave/I-device using safety-related master-I-slave/IO controller-I-device communication.
Programming procedure
1. Place the SENDDP (Page 588) instruction in the safety program in the F-CPU of the DP
master/IO controller.
2. Place the RCVDP (Page 588) instruction in the safety program in the F-CPU of the
I-slave/I-Device.
3. Supply an input SD_BO_xx of SENDDP with the input of the acknowledgment key.
4. The acknowledgment signal for evaluating user acknowledgments is now available at the
corresponding RD_BO_xx output of RCVDP.
The acknowledgment signal can now be read in the program sections in which further
processing is to take place with fully qualified access directly in the associated instance
DB (for example, "RCVDP_DB".RD_BO_02).
Implementation of user acknowledgment
7.2 Implementing user acknowledgment in the safety program of the
F-CPU of a I-slave or I-device
SIMATIC Safety - Configuring and Programming
194 Programming and Operating Manual, 10/2018, A5E02714440-AH
5. Supply the corresponding input SUBBO_xx of RCVDP with FALSE (fail-safe value 0) to
ensure that user acknowledgment is not accidentally triggered before communication is
established for the first time after startup of the sending and receiving F-systems, or in
the event of a safety-related communication error.
Note
If a communication error, an F
-I/O error, or a channel fault occurs at the F-I/O to which
the acknowledgment key is connected, then an acknowledgment for reintegration of this
F
-I/O will no longer be possible.
This "blocking" can only be removed by a STOP
-to-RUN transition of the F-CPU of the
DP master/IO controller.
Consequently, it is recommended that you also provide for an acknowledgment by means
of an HMI system that you can use to access the F
-CPU of the DP master/IO controller,
in order to acknowledge reintegration of the F
-I/O to which an acknowledgment key is
connected.
If a safety
-related master-I-slave/IO controller-I-Device communication error occurs, the
acknowledgment signal cannot be transmitted, a
nd an acknowledgment for reintegration
of safety
-related communication is no longer possible.
This "blocking" can only be removed by a STOP
-to-RUN transition of the F-CPU of the
I
-slave/I-Device.
Consequently, it is recommended that you also provide for an acknowledgment by means
of an HMI system that you can use to access the F
-CPU of the I-slave/I-Device, in order
to acknowledge reintegration of the safety
-related communication for transmission of the
acknowledgment signal (see 1).
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 195
Data exchange between standard user program and
safety program
8
You have the option of transferring data between the safety program and the standard user
program. Tags can be transferred using DBs, F-DBs and bit memory:
From the standard user program
From the safety program
Read access
Write access
Read access
Write access
Tag from DB Permitted Permitted A tag from the DB can be read-accessed
or
write-accessed
Tag from F-DB
Permitted
Not permitted
Permitted
Permitted
Bit memory Permitted Permitted Bit memory can be read-accessed
or
write-
accessed
You can also access the process image of the standard I/O and F-I/O:
From the standard user program
From the safety program
Read access
Write access
Read access
Write access
Process image of
standard I/O
PII
Permitted
Permitted
Permitted
Not permitted
PIQ
Permitted
Permitted
Not permitted
Permitted
Process image of F-I/O
PII
Permitted
Not permitted
Permitted
Not permitted
PIQ
Permitted
Not permitted
Not permitted
Permitted
Decoupling of the safety program from the standard program
For data exchange between standard user program and safety program, we recommend that
you define special data blocks (transfer data blocks) in which the data to be exchanged is
stored. This action allows you to decouple the blocks of the standard and the safety
program. The changes in the standard program do not affect the safety program (and vice
versa) provided these data blocks are not modified.
Data exchange between standard user program and safety program
8.1 Data Transfer from the Safety Program to the Standard User Program
SIMATIC Safety - Configuring and Programming
196 Programming and Operating Manual, 10/2018, A5E02714440-AH
8.1
Data Transfer from the Safety Program to the Standard User
Program
Data transfer from the safety program to the standard user program
The standard user program can read all data of the safety program, for example using
symbolic (fully qualified) accesses to the following:
The instance DBs of the F-FBs ("Name of instance DB".Signal_x)
F-DBs (for example "Name of F_DB".Signal_1)
The process image input and output of F-I/O (for example "Emergency_Stop_Button_1"
(I 5.0))
Note
For S7-300/400 F-CPUs
The process image input of F
-I/O is updated not only at the start of the main safety block,
but also by the standard operating system.
To find the standard operating system update times, refer to the
Help on STEP 7
under
"Process image input and output". For F
-CPUs that support process image partitions,
also bear in mind
the update times when process image partitions are used. For this
reason, when the process image input of F
-
I/O is accessed in the standard user program,
it is possible to obtain different values than in the safety program. The differing values
can occur
due to:
Different update times
Use of fail-safe values in the safety program
To obtain the same values in the standard user program as in the safety program, you
must not access the process image input in the standard program until after execution of
an F
-runtime group. In this case, you can also evaluate the QBAD or QBAD_I_xx tag in
the associated F
-I/O DB in the standard user program, in order to find out whether the
process image input is receiving fail
-safe values (0) or process data. When using process
image partitions, also make sure that the process image is not updated by the standard
operating system or by the UPDAT_PI instruction between execution of an F
-runtime
group and evaluation of the process image input in the standard user program.
Note
For S7-1200/1500 F-CPUs
The process image input of F
-I/O is updated prior to processing the main safety block.
You can also write safety program data directly to the standard user program (see also the
table of supported operand areas in: Restrictions in the programming languages FBD/LAD
(Page 119)):
Data exchange between standard user program and safety program
8.2 Data Transfer from Standard User Program to Safety Program
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 197
Data block/bit memory
In order to write safety program data directly to the standard user program (e.g., DIAG output
of the SENDDP instruction), you can write to data blocks of the standard user program from
the safety program. However, a written tag must not be read in the safety program itself.
You can also write to bit memory in the safety program. However, written bit memory must
not be read in the safety program itself.
Process image output
You can write to the process image output (PIQ) of standard I/O in the safety program, for
example for display purposes. The PIQ must not be read in the safety program.
8.2
Data Transfer from Standard User Program to Safety Program
Data transfer from standard user program to safety program
As a basic principle, only fail-safe data or fail-safe signals from F-I/O and other safety
programs (in other F-CPUs) can be processed in the safety program, as standard tags are
unsafe.
If you have to process tags from the standard user program in the safety program, however,
you can evaluate either bit memory from the standard user program, tags from a standard
DB, or the process image input (PII) of standard I/O in the safety program (see table of
supported operand areas in: Restrictions in the programming languages FBD/LAD
(Page 119)).
Note that structural changes to standard data blocks which are used in the safety program
lead to inconsistencies of the safety program and possibly to the password being requested.
In this case the collective F-signature is the same as the original again after compilation. To
prevent this effect, use "interprocess communication blocks" between the standard user
program and the safety program.
WARNING
Because these tags are not generated safely, you must carry out additional
process-specific validity checks in the safety program to ensure that no dangerous states
can arise. If bit memory, a tag of a standard DB, or an input of standard I/O is used in both
F-runtime groups, you must perform the validity check separately in each F-runtime group.
(S015)
To facilitate checks, all PLC tags from the standard user program that are evaluated in the
safety program are included in the safety summary (Page 341).
Data exchange between standard user program and safety program
8.2 Data Transfer from Standard User Program to Safety Program
SIMATIC Safety - Configuring and Programming
198 Programming and Operating Manual, 10/2018, A5E02714440-AH
Bit memory
In order to process tags of the standard user program in the safety program, you can also
read bit memory in the safety program. However, read bit memory must not be written in the
safety program itself.
Data block
In order to process tags of the standard user program in the safety program, you can read
tags from data blocks of the standard user program in the safety program. However, a read
tag must not be written in the safety program itself.
Process image of the inputs
You can read the process image input (PII) of standard I/O in the safety program. The PII
must not be written in the safety program.
Examples: Programming validity checks
Use Comparison (Page 511) instructions to check whether tags from the standard user
program exceed or fall below permitted high and low limits. You can then influence your
safety function with the result of the comparison.
Use the ---( S )---: Set output (STEP 7 Safety V15.1) (Page 404), ---( R )---: Reset output
(STEP 7 Safety V15.1) (Page 403) or SR: Set/reset flip-flop (STEP 7 Safety V15.1)
(Page 406) instructions, for example, with tags from the standard user program to allow a
motor to be switched off, but not switched on.
For switch-on sequences, use the AND logic operation instruction, for example, to
logically combine tags from the standard user program with switch-on conditions that you
derive from fail-safe tags.
If you want to process tags from the standard user program in the safety program, please
bear in mind that there is not a sufficiently simple method of checking validity for all tags.
Data exchange between standard user program and safety program
8.2 Data Transfer from Standard User Program to Safety Program
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 199
Reading tags from the standard user program that can change during the runtime of an F-runtime
group
If you want to read tags from the standard user program (bit memory, tags of a standard DB,
or PII of standard I/O) in the safety program, and these tags can be changed - either by the
standard user program or an operator control and monitoring system - during runtime of the
F-runtime group in which they are read (for example because your standard user program is
being processed by a higher-priority cyclic interrupt), you must use bit memory or tags of a
standard DB for this purpose.
(S7-1200/1500) You must create the standard OB with the same priority as the F-OB. The
standard OB must be called phase-shifted to the F-OB and describe the variables in this.
We recommend that you select the phase shift so that the standard OB is executed
immediately before the F-OB.
(S7-300/400) You must write the bit memory or tags of a standard DB with the tags from the
standard user program immediately before calling the F-runtime group.
You are then permitted to access only this bit memory or these tags of a standard DB in the
safety program.
Also note that
clock memory
that you defined when configuring your F-CPU in the
"Properties" tab can change during runtime of the F-runtime group, since clock memory runs
asynchronously to the F-CPU cycle.
Note
The F
-CPU can go to STOP if this is not observed. The cause of the diagnostics event is
entered in the diagnostics buffer of the F
-CPU.
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 201
Safety-related communication
9
9.1
Configuring and programming communication (S7-300, S7-400)
9.1.1
Overview of communication
Introduction
This section gives an overview of the safety-related communication options in SIMATIC
Safety F-systems.
Options for safety-related communication
Safety-related communication
On subnet
Additional hardware
required
I-slave-slave communication PROFIBUS DP
Safety-related CPU-CPU communication:
IO controller-IO controller communica-
tion
PROFINET IO PN/PN coupler
Master-master communication
PROFIBUS DP
DP/DP coupler
IO controller-I-device communication
PROFINET IO
Master-I-slave communication
PROFIBUS DP
I-slave-I-slave communication
PROFIBUS DP
IO controller-I-slave communication
PROFINET IO and PROFIBUS DP
IE/PB link
Safety-related communication via S7
connections
Industrial Ethernet
IO controller-IO controller communica-
tion for S7 Distributed Safety
PROFINET IO PN/PN coupler
Master-master communication for S7
Distributed Safety
PROFIBUS DP DP/DP coupler
Safety-related communication to S7
Distributed Safety or S7 F Systems via
S7 connections
Industrial Ethernet
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
202 Programming and Operating Manual, 10/2018, A5E02714440-AH
Overview of safety-related communication via PROFIBUS DP
The figure below presents an overview of the 4 options for safety-related communication via
PROFIBUS DP in SIMATIC Safety F-systems with S7-300/400 F-CPUs.
Safety-related master-master communication
Safety-related master-I-slave communication
Safety-related I-slave-I-slave communication
Safety-related I-slave-slave communication
Overview of safety-related communication via PROFINET IO
The figure below presents an overview of the four options for safety-related communication
via PROFINET IO in SIMATIC Safety F-systems with S7-300/400 F-CPUs. If an IE/PB-link is
used, safety-related communication is possible between assigned I-slaves.
Safety-related IO controller-IO controller communication
Safety-related IO controller-I-device communication
Safety-related IO controller-I-slave communication
Safety-related I-slave-I-slave communication integrating an IO controller
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 203
Safety-related CPU-CPU communication via PROFIBUS DP or PROFINET IO
In safety-related CPU-CPU communication, a fixed amount of fail-safe data of the data type
INT or BOOL is transmitted fail-safe between the safety programs in F-CPUs of DP
masters/I-slaves or IO controllers/I-devices.
The data are transferred using the SENDDP instruction for sending and the RCVDP
instruction for receiving. The data are stored in configured transfer areas of the devices.
Each transfer area consists of one input and one output address area.
Safety-related I-slave-slave communication via PROFIBUS DP
Safety-related I-slave-slave communication with F-I/O is possible in a DP slave that supports
safety-related I-slave-slave communication, for example with all ET 200SP F-modules with
IM 155-6 DP HF, firmware version > V3.1, with all ET 200S F-modules with IM 151-1 HF,
with all fail-safe S7-300 signal modules with IM 153-2, as of article
number 6ES7153-2BA01-0XB0, firmware version > V4.0.0.
Safety-related communication between the safety program of the F-CPU of an I-slave and F-
I/O of a DP slave takes place using direct data exchange, as in the standard program. The
process image is used to access the channels of the F-I/O in the safety program of the F-
CPU of the I-slave.
Safety-related CPU-CPU communication via Industrial Ethernet
Safety-related CPU-CPU communication via Industrial Ethernet is possible using S7
connections, both from and to the following:
S7-300 F-CPUs via the integrated PROFINET interface
S7-400 F-CPUs via the integrated PROFINET interface or a CP 443-1 or CP 443-1
Advanced-IT
In safety-related communication via S7 connections, a specified amount of fail-safe data of
data type BOOL, INT, WORD, DINT, DWORD, or TIME is transferred fail-safe between the
safety programs of the F-CPUs linked by the S7 connection.
The data transfer makes use of the SENDS7 instruction for sending and the RCVS7
instruction for receiving. Data are exchanged using one F-DB ("F-communication DB") each
at the sender and receiver ends.
Safety-related CPU-CPU communication to
S7 Distributed Safety
or
F-systems
Safety-related communication is possible from F-CPUs in
SIMATIC Safety
to F-CPUs in
S7
Distributed Safety
or
S7 F-systems
.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
204 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.1.2
Safety-related IO controller-IO controller communication
9.1.2.1
Configure safety-related IO controller-IO controller communication
Introduction
Safety-related communication between safety programs of the F-CPUs of IO controllers
takes place over a PN/PN coupler that you set up between the F-CPUs.
For 416F-2 DP CPUs without an integrated PROFINET interface, use a CP 443-1 or CP
443-1 Advanced-IT.
Note
Deactivate the "Data validity display DIA" parameter in the properties for the PN/PN coupler
in the
hardware and network editor
. This is the default setting. Otherwise, safety-related IO
controller
-IO controller communication is not possible.
Configuring transfer areas
You must configure one transfer area for output data and one transfer area for input data in
the
hardware and network editor
for each safety-related communication connection between
two F-CPUs in the PN/PN coupler. The figure below shows how both of the F-CPUs are able
to send
and
receive data (bidirectional communication). One transfer area for output data
and one transfer area for input data must be configured in the PN/PN coupler for each of the
two communication connections.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 205
Rules for defining transfer areas
The transfer area for output data and the transfer area for input data for the
data to be sent
must begin with the same start address. A total of 12 bytes (consistent) is required for the
transfer area for output data; 6 bytes (consistent) are required for the transfer area for input
data.
The transfer area for input data and the transfer area for output data for the
data to be
received
must begin with the same start address. A total of 12 bytes (consistent) is required
for the transfer area for input data; 6 bytes (consistent) are required for the transfer area for
output data.
Procedure for configuration
The procedure for configuring safety-related IO controller-IO controller communication is
identical to that in the standard system.
Proceed as follows:
1. Insert two F-CPUS from the "Hardware catalog" task card into the project.
2. Switch to the network view of the
hardware and network editor
.
3. Select a PN/PN Coupler X1 and a PN/PN Coupler X2 from "Other field
devices\PROFINET IO\Gateway\Siemens AG\PN/PN Coupler" in the "Hardware catalog"
task card and insert them into the network view of the hardware and network editor.
4. Connect the PN interface of the F-CPU 1 with the PN interface of the PN/PN Coupler X1
and the PN interface of the F-CPU 2 with the PN interface of PN/PN Coupler X2.
5. Switch to the device view of PN/PN Coupler X1 for bidirectional communication
connections i.e. where each F-CPU is both to send and to receive data. Select the
following modules from "IN/OUT" in the "Hardware catalog" task card (with filter
activated), and insert them in the "Device overview" tab:
One "IN/OUT 6 bytes / 12 bytes" module and
One "IN/OUT 12 bytes / 6 bytes" module
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
206 Programming and Operating Manual, 10/2018, A5E02714440-AH
6. In the properties of the modules, assign the addresses outside the process image as
follows:
For the "IN/OUT 6 bytes / 12 bytes" module for sending data for example:
Input addresses: Start address 518
Output addresses: Start address 518
For the "IN/OUT 12 bytes / 6 bytes" module for receiving data for example:
Input addresses: Start address 530
Output addresses: Start address 530
Note
Make sure that you assign identical start addresses for the address areas of the output
and input data.
Tip:
Make a note of the start addresses of the transfer areas. You need these to program
the SENDDP and RCVDP blocks (LADDR input).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 207
7. Select the following modules from "IN/OUT" in the device view of PN/PN coupler X2 and
insert them in the "Device overview" tab:
One "IN/OUT 12 bytes / 6 bytes" module and
One "IN/OUT 6 bytes / 12 bytes" module
8. In the properties of the modules, assign the addresses outside the process image as
follows:
For the "IN/OUT 12 bytes / 6 bytes" module for receiving data for example:
Input addresses: Start address 516
Output addresses: Start address 516
For the "IN/OUT 6 bytes / 12 bytes" module for sending data for example:
Input addresses: Start address 528
Output addresses: Start address 528
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
208 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.1.2.2
Safety-related IO controller-IO controller communication via SENDDP and RCVDP
Communication via SENDDP and RCVDP instructions
Safety-related communication between the F-CPUs of the IO controllers uses the SENDDP
and RCVDP instructions for sending and receiving, respectively. These can be used to
perform a fail-safe transfer of a
fixed
amount of fail-safe data of the data type INT or BOOL.
You can find these instructions in the "Instructions" task card under "Communication". The
RCVDP instruction
must
be called at the start of the main safety block. The SENDDP
instruction
must
be called at the end of the main safety block.
Note that the send signals are not sent until after the SENDDP instruction call at the end of
execution of the relevant F-runtime group.
A detailed description of the SENDDP and RCVDP instructions can be found in SENDDP
and RCVDP: Send and receive data via PROFIBUS DP/PROFINET IO (STEP 7 Safety
V15.1) (Page 588).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 209
9.1.2.3
Program safety-related IO controller-IO controller communication
Requirement for programming
The transfer areas for input and output data for the PN/PN coupler must be configured.
Programming procedure
You program safety-related IO controller-IO controller communication as follows:
1. In the safety program from which data are to be sent, call the SENDDP instruction
(Page 588) for sending at the end of the main safety block.
2. In the safety program in which data are to be received, call the RCVDP instruction
(Page 588) for receiving at the start of the main safety block.
3. Assign the start addresses of the output and input data transfer areas of the PN/PN
coupler configured in the
hardware and network editor
to the respective LADDR inputs.
You must carry out this assignment for every communication connection for each of the
F-CPUs involved.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
210 Programming and Operating Manual, 10/2018, A5E02714440-AH
4. Assign the value for the respective F-communication ID to the DP_DP_ID inputs. This
establishes the communication relationship between the SENDDP instruction in one
F-CPU and the RCVDP instruction in the other F-CPU: The associated instructions
receive the same value for DP_DP_ID.
The figure below contains an example of how to specify the F-communication IDs at the
inputs of the SENDDP and RCVDP instructions for 5 safety-related IO controller-IO
controller communication relationships.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 211
WARNING
The value for the respective F-communication ID (input DP_DP_ID; data type: INT) can
be freely selected; however, it must be unique for all safety-related communication
connections network-wide* and CPU-wide at all times. The uniqueness must be
checked in the safety summary during acceptance of the safety program. You can find
additional information in Correctness and completeness of the communication
configuration (Page 374).
You must supply inputs DP_DP_ID and LADDR with constant values when calling the
instruction. Direct write accesses in the associated instance DB to DP_DP_ID and
LADDR are not permitted in the safety program!
(S016)
* A network consists of one or more subnets. "Network-wide" means beyond the
boundaries of the subnet. In PROFIBUS, a network includes all nodes accessible via
PROFIBUS DP. In PROFINET IO, a network includes all nodes accessible via
RT_Class_1/2/3 (Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP
(IP, Layer 3).
5. Supply the SD_BO_xx and SD_I_xx inputs of SENDDP with the send signals. To cut
down on intermediate signals when transferring block parameters, you can write the
value directly to the instance DB of SENDDP using fully qualified access (for example,
"Name SENDDP_1".SD_BO_02) before calling SENDDP.
6. Supply the RD_BO_xx and RD_I_xx outputs of RCVDP with the signals that you want to
process further in other program sections or use fully qualified access to read the
received signals directly in the associated instance DB in the program sections to be
processed further (e.g., "Name RCVDP_1".RD_BO_02).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
212 Programming and Operating Manual, 10/2018, A5E02714440-AH
7. Supply the SUBBO_xx and SUBI_xx inputs of RCVDP with the fail-safe values that are to
be output by RCVDP in place of the process data until communication is established for
the first time after startup of the sending and receiving F-systems or in the event of an
error in safety-related communication.
Specification of constant fail-safe values:
For data of data type INT, you can enter constant fail-safe values directly as constants
in the SUBI_xx input (initial value = "0"). If you want to specify a constant fail-safe
value "TRUE" for data of the data type BOOL, provide the tag "F_GOBDB".VKE1 for
the SUBBO_xx input (initial value = "FALSE").
Specification of dynamic fail-safe values:
If you want to specify dynamic fail-safe values, define a tag that you change
dynamically through your safety program in an F-DB and specify this tag (fully
qualified) in the SUBI_xx or SUBBO_xx input.
WARNING
Note that your safety program for dynamically changing the tag for a dynamic fail-
safe value can only be processed after the call of the RCVDP, because prior to the
RCVDP call, there must not be any network and no more than one other RCVDP
instruction in the main safety block. You must therefore assign appropriate start
values for these tags to be output by RCVDP in the first cycle after a startup of the
F-system.
(S017)
8. Configure the TIMEOUT inputs of the RCVDP and SENDDP instructions with the required
monitoring time.
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal state to be transferred
will be acquired at the sender end and transferred to the receiver if the signal level is
pending for at least as long as the assigned monitoring time.
(S018)
Information on calculating the monitoring times can be found in Monitoring and response
times (Page 607).
9. Optional: Evaluate the ACK_REQ output of the RCVDP instruction, for example, in the
standard user program or on the HMI system in order to query or to indicate whether user
acknowledgment is required.
10.Supply the ACK_REI input of the RCVDP instruction with the acknowledgment signal for
reintegration.
11.Optional: Evaluate the SUBS_ON output of the RCVDP or SENDDP instruction in order to
query whether the RCVDP instruction is outputting the fail-safe values assigned in the
SUBBO_xx and SUBI_xx inputs.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 213
12.Optional: Evaluate the ERROR output of the RCVDP or SENDDP instruction, for
example, in the standard user program or on the HMI system in order to query or to
indicate whether a communication error has occurred.
13.Optional: Evaluate the SENDMODE output of the RCVDP instruction in order to query
whether the F-CPU with the associated SENDDP instruction is in disabled safety mode
(Page 344).
9.1.2.4
Safety-related IO controller-IO controller communication - Limits for data transfer
Note
If the data quantities to be transmitted exceed the capacity of the SENDDP / RCVDP
correlated instructions, a second (or third) SENDDP / RCVDP call can be used. This requires
configu
ration of an additional connection via the PN/PN coupler. Whether or not this is
possible with one single PN/PN coupler depends on the capacity restrictions of the PN/PN
coupler.
9.1.3
Safety-related master-master communication
9.1.3.1
Configure safety-related master-master communication
Introduction
Safety-related communication between safety programs of the F-CPUs of DP masters takes
place via a DP/DP coupler.
Note
Switch the data validity indicator "DIA" on the DIP switch of the DP/DP coupler to "OFF".
Otherwise, safety
-related CPU-CPU communication is not possible.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
214 Programming and Operating Manual, 10/2018, A5E02714440-AH
Configuring transfer areas
You must configure one transfer area for output data and one transfer area for input data in
the
hardware and network editor
for each safety-related communication connection between
two F-CPUs in the DP/DP coupler. The figure below shows how both of the F-CPUs are able
to send and receive data (bidirectional communication). One transfer area for output data
and one transfer area for input data must be configured in the DP/DP coupler for each of the
two communication connections.
Rules for defining transfer areas
The transfer area for input data and the transfer area for output data for the
data to be sent
must begin with the same start address. A total of 6 bytes (consistent) is required for the
transfer area for input data; 12 bytes (consistent) are required for the transfer area for output
data.
The transfer area for input data and the transfer area for output data for the
data to be
received
must begin with the same start address. A total of 12 bytes (consistent) is required
for the transfer area for input data; 6 bytes (consistent) are required for the transfer area for
output data.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 215
Procedure for configuration
The procedure for configuring safety-related master-master communication is identical to
that in the standard system.
Proceed as follows:
1. Insert two F-CPUS from the "Hardware catalog" task card into the project.
2. Switch to the network view of the
hardware and network editor
.
3. Select a DP/DP coupler from "Other field
devices\PROFIBUS DP\Gateways\Siemens AG\DP/DP Coupler" in the "Hardware
catalog" task card and insert it into the network view of the hardware and network editor.
4. Insert a second DP/DP coupler.
5. Connect a DP interface of F-CPU 1 to the DP interface of a DP/DP coupler and a DP
interface of F-CPU 2 to the DP interface of the other DP/DP coupler.
6. A free PROFIBUS address is assigned automatically in the properties of the DP/DP-
coupler in the device view. You must set this address on the DP/DP coupler of PLC 1,
either using the DIP switch on the device or in the configuration of the DP/DP coupler
(see DP/DP Coupler (http://support.automation.siemens.com/WW/view/en/1179382)
manual).
7. Switch to the device view of the DP/DP coupler for PLC1 for bidirectional communication
connections i.e. where each F-CPU is both to send and to receive data. Select the
following modules from the "Hardware catalog" task card (with filter activated), and insert
them in the "Device overview" tab:
One "6 bytes I/12 bytes Q consistent" module, and
One "12 bytes I/6 bytes Q consistent" module
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
216 Programming and Operating Manual, 10/2018, A5E02714440-AH
8. In the properties of the modules, assign the addresses outside the process image as
follows:
For "6 bytes I/12 bytes Q consistent" module for sending data for example:
Input addresses: Start address 530
Output addresses: Start address 530
For "12 bytes I/6 bytes Q consistent" module for receiving data for example:
Input addresses: Start address 542
Output addresses: Start address 542
Note
Make sure that you assign identical start addresses for the address areas of the
output and input data.
Tip:
Make a note of the start addresses of the transfer areas. You need these to
program the SENDDP and RCVDP blocks (LADDR input).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 217
9. Select the following modules from the "Hardware catalog" task card (with filter activated)
in the device view of DP/DP coupler PLC2, and insert them in the "Device overview" tab:
One "12 bytes I/6 bytes Q consistent" module, and
One "6 bytes I/12 bytes Q consistent" module
10.In the properties of the modules, assign the addresses outside the process image as
follows:
For "12 bytes I/6 bytes Q consistent" module for receiving data for example:
Input addresses: Start address 548
Output addresses: Start address 548
For "6 bytes I/12 bytes Q consistent" module for sending data for example:
Input addresses: Start address 560
Output addresses: Start address 560
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
218 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.1.3.2
Safety-related master-master communication via SENDDP and RCVDP
Communication via SENDDP and RCVDP instructions
Safety-related communication between the F-CPUs of the DP master uses the SENDDP and
RCVDP instructions for sending and receiving, respectively. These can be used to perform a
fail-safe transfer of a
fixed
amount of fail-safe data of the data type INT or BOOL.
You can find these instructions in the "Instructions" task card under "Communication". The
RCVDP instruction
must
be called at the start of the main safety block. The SENDDP
instruction
must
be called at the end of the main safety block.
Note that the send signals are not sent until after the SENDDP instruction call at the end of
execution of the relevant F-runtime group.
A detailed description of the SENDDP and RCVDP instructions can be found in SENDDP
and RCVDP: Send and receive data via PROFIBUS DP/PROFINET IO (STEP 7 Safety
V15.1) (Page 588).
9.1.3.3
Program safety-related master-master communication
Requirement for programming
The transfer areas for input and output data for the DP/DP coupler must be configured.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 219
Programming procedure
You program safety-related master-master communication as follows:
1. In the safety program from which data are to be sent, call the SENDDP instruction
(Page 588) for sending at the end of the main safety block.
2. In the safety program in which data are to be received, call the RCVDP instruction
(Page 588) for receiving at the start of the main safety block.
3. Assign the start addresses of the transfer areas for output and input data of the DP/DP
coupler configured in the
hardware and network editor
to the respective LADDR inputs.
You must carry out this assignment for every communication connection for each of the
F-CPUs involved.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
220 Programming and Operating Manual, 10/2018, A5E02714440-AH
4. Assign the value for the respective F-communication ID to the DP_DP_ID inputs. This
establishes the communication relationship between the SENDDP instruction in one
F-CPU and the RCVDP instruction in the other F-CPU: The associated instructions
receive the same value for DP_DP_ID.
The figure below contains an example of how to specify the F-communication IDs at the
inputs of the SENDDP and RCVDP instructions for 5 safety-related master-master
communications relationships.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 221
WARNING
The value for the respective F-communication ID (input DP_DP_ID; data type: INT) can
be freely selected; however, it must be unique for all safety-related communication
connections network-wide* and CPU-wide at all times. The uniqueness must be
checked in the safety summary during acceptance of the safety program. You can find
additional information in Correctness and completeness of the communication
configuration (Page 374).
You must supply inputs DP_DP_ID and LADDR with constant values when calling the
instruction. Direct write accesses in the associated instance DB to DP_DP_ID and
LADDR are not permitted in the safety program!
(S016)
* A network consists of one or more subnets. "Network-wide" means beyond the
boundaries of the subnet. In PROFIBUS, a network includes all nodes accessible via
PROFIBUS DP. In PROFINET IO, a network includes all nodes accessible via
RT_Class_1/2/3 (Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP
(IP, Layer 3).
5. Supply the SD_BO_xx and SD_I_xx inputs of SENDDP with the send signals. To cut
down on intermediate signals when transferring block parameters, you can write the
value directly to the instance DB of SENDDP using fully qualified access (for example,
"Name SENDDP_1".SD_BO_02) before calling SENDDP.
6. Supply the RD_BO_xx and RD_I_xx outputs of RCVDP with the signals that you want to
process further in other program sections or use fully qualified access to read the
received signals directly in the associated instance DB in the program sections to be
processed further (e.g. "Name RCVDP_1".RD_BO_02).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
222 Programming and Operating Manual, 10/2018, A5E02714440-AH
7. Supply the SUBBO_xx and SUBI_xx inputs of RCVDP with the fail-safe values that are to
be output by RCVDP in place of the process data until communication is established for
the first time after startup of the sending and receiving F-systems or in the event of an
error in safety-related communication.
Specification of constant fail-safe values:
For data of data type INT, you can enter constant fail-safe values directly as constants
in the SUBI_xx input (initial value = "0"). If you want to specify a constant fail-safe
value for data of the data type BOOL, provide the tag "F_GLOBDB".VKE1 for the
SUBBO_xx input (initial value = "FALSE").
Specification of dynamic fail-safe values:
If you want to specify dynamic fail-safe values, define a tag that you change
dynamically through your safety program in an F-DB and specify this tag (fully
qualified) in the SUBI_xx or SUBBO_xx input.
WARNING
Note that your safety program for dynamically changing the tag for a dynamic fail-
safe value can only be processed after the call of the RCVDP, because prior to the
RCVDP call, there must not be any network and no more than one other RCVDP
instruction in the main safety block. You must therefore assign appropriate start
values for these tags to be output by RCVDP in the first cycle after a startup of the
F-system.
(S017)
8. Configure the TIMEOUT inputs of the RCVDP and SENDDP instructions with the required
monitoring time.
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal state to be transferred
will be acquired at the sender end and transferred to the receiver if the signal level is
pending for at least as long as the assigned monitoring time.
(S018)
Information on calculating the monitoring times can be found in Monitoring and response
times (Page 607).
9. Optional: Evaluate the ACK_REQ output of the RCVDP instruction, for example, in the
standard user program or on the HMI system in order to query or to indicate whether user
acknowledgment is required.
10.Supply the ACK_REI input of the RCVDP instruction with the acknowledgment signal for
reintegration.
11.Optional: Evaluate the SUBS_ON output of the RCVDP or SENDDP instruction in order to
query whether the RCVDP instruction is outputting the fail-safe values assigned in the
SUBBO_xx and SUBI_xx inputs.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 223
12.Optional: Evaluate the ERROR output of the RCVDP or SENDDP instruction, for
example, in the standard user program or on the HMI system in order to query or to
indicate whether a communication error has occurred.
13.Optional: Evaluate the SENDMODE output of the RCVDP instruction in order to query
whether the F-CPU with the associated SENDDP instruction is in disabled safety mode
(Page 344).
9.1.3.4
Safety-related master-master communication:Limits for data transfer
Note
If the data quantities to be transmitted exceed the capacity of the SENDDP / RCVDP
correlated instructions, a second (or third) SENDDP / RCVDP call can be used. This requires
configuration of an additional connection via the DP/DP coupl
er. Whether or not this is
possible with one single DP/DP coupler depends on the capacity restrictions of the DP/DP
coupler.
9.1.4
Safety-related IO controller-I-device communication
9.1.4.1
Configuring safety-related communication between IO controller and I-device
Introduction
Safety-related communication between the safety program of the F-CPU of an IO controller
and the safety program(s) of the F-CPU(s) of one or more I-devices takes place via IO
controller-I-device connections (
F
-CD) in PROFINET IO, in the same way as in standard
systems.
You do not need any additional hardware for IO controller-I-device communication.
The F-CPU to be used as an I-device must support the "IO-device" operating mode.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
224 Programming and Operating Manual, 10/2018, A5E02714440-AH
Configuring transfer areas
For every safety-related communication connection between two F-CPUs, you must
configure transfer areas in the
hardware and network editor
. The figure below shows how
both of the F-CPUs are able to send and receive data (bidirectional communication).
The transfer area is assigned a label when it is created to identify it as the communication
relationship. For example, "F-CD_PLC_2 PLC_1_1" for the first F-CD connection between IO
controller F-CPU 1 and I-device F-CPU 2.
You assign the start addresses of the transfer areas to the LADDR input of the SENDDP and
RCVDP instructions in the safety programs.
Procedure for configuration
The procedure for configuring safety-related IO controller-I-device communication is identical
to that in the standard system.
Proceed as follows:
1. Insert two F-CPUS from the "Hardware catalog" task card into the project.
2. Enable the "IO Device" mode for F-CPU 2 in the properties of its PN interface and assign
this PN interface to a PN interface of F-CPU 1.
3. Select the PROFINET interface of F-CPU 2. Under "Transfer areas", you create an F-CD
connection (type "F-CD") for sending to the IO controller (←). The F-CD connection is
shown in yellow in the table and the address areas in the I-device and IO controller
assigned outside of the process image are displayed.
In addition, an acknowledgment connection is created automatically for each F-CD
connection. (see "Transfer area details").
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 225
4. Create an additional F-CD connection for receiving from the IO controller.
5. In the transfer area you just created, click the arrow in order to change the transfer
direction to receiving from IO controller (→).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
226 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.1.4.2
Safety-related IO controller-I-device communication via SENDDP and RCVDP
Communication via SENDDP and RCVDP instructions
Safety-related communication between the F-CPUs of the IO controller and an I-device
makes use of the SENDDP and RCVDP instructions for sending and receiving, respectively.
These can be used to perform a fail-safe transfer of a
fixed
amount of fail-safe data of the
data type INT or BOOL.
You can find these instructions in the "Instructions" task card under "Communication". The
RCVDP instruction
must
be called at the start of the main safety block. The SENDDP
instruction
must
be called at the end of the main safety block.
Note that the send signals are not sent until after the SENDDP instruction call at the end of
execution of the relevant F-runtime group.
A detailed description of the SENDDP and RCVDP instructions can be found in SENDDP
and RCVDP: Send and receive data via PROFIBUS DP/PROFINET IO (STEP 7 Safety
V15.1) (Page 588).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 227
9.1.4.3
Programming safety-related IO controller I-device communication
Requirement for programming
The transfer areas must be configured.
Programming procedure
The procedure for programming safety-related IO controller-I-device communication is the
same as that for programming safety-related IO controller-IO controller communication (see
Program safety-related IO controller-IO controller communication (Page 209)).
The assignment of the start addresses of the transfer areas to the LADDR input of the
SENDDP/RCVDP instructions can be obtained from the following table.
Instruction
Start address LADDR
From row
From column
SENDDP in the IO controller Address in the IO controller
RCVDP in the IO controller
Address in the IO controller
SENDDP in the I-device
Address in the IO device
RCVDP in the I-device
Address in the IO device
The figure below contains an example of how to specify the F-communication IDs for the
inputs of the SENDDP and RCVDP instructions for 4 safety-related IO controller-I-device
communication relationships.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
228 Programming and Operating Manual, 10/2018, A5E02714440-AH
WARNING
The value for the respective F-communication ID (input DP_DP_ID; data type: INT) can be
freely selected; however, it must be unique for all safety-related communication
connections network-wide* and CPU-wide at all times. The uniqueness must be checked in
the safety summary during acceptance of the safety program. You can find additional
information in Correctness and completeness of the communication configuration
(Page 374).
You must supply inputs DP_DP_ID and LADDR with constant values when calling the
instruction. Direct write accesses in the associated instance DB to DP_DP_ID and LADDR
are not permitted in the safety program!
(S016)
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet. In PROFIBUS, a network includes all nodes accessible via PROFIBUS DP. In
PROFINET IO, a network includes all nodes accessible via RT_Class_1/2/3
(Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP (IP, Layer 3).
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal state to be transferred will
be acquired at the sender end and transferred to the receiver if the signal level is pending
for at least as long as the assigned monitoring time.
(S018)
Information on calculating the monitoring times can be found in Monitoring and response
times (Page 607).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 229
9.1.4.4
Safety-related IO-Controller-IO-Device communication - Limits for data transfer
Limits for data transfer
If the amount of data to be transferred is greater than the capacity of related
SENDDP/RCVDP instructions, you can use additional SENDDP/RCVDP instructions.
Configure additional transfer areas for this purpose. Remember the maximum limit of 1440
bytes of input data or 1440 bytes of output data for transfer between an I-device and a IO
controller.
The following table shows the amount of output and input data assigned in safety-related
communication connections:
Safety-related
communication
Communication con-
nection
Assigned input and output data
In the IO controller
In the I-device
Output data
Input data
Output data
Input data
IO controller-
I-Device
Sending:
I-Device 1 to IO control-
ler
6 bytes 12 bytes 12 bytes 6 bytes
Receiving:
I-Device 1 from IO
controller
12 bytes 6 bytes 6 bytes 12 bytes
Consider all additional configured safety-related and standard communication connections
(transfer areas of type F-CD and CD) for the maximum limit of 1440 bytes of input data or
1440 bytes of output data for transfer between an I-device and an IO controller. In addition,
data are assigned for internal purposes such that the maximum limit may be reached sooner.
When the limit is exceeded, a corresponding error message is displayed.
9.1.5
Safety-related master-I-slave communication
9.1.5.1
Configuring safety-related master-I-slave communication
Introduction
Safety-related communication between the safety program of the F-CPU of a DP master and
the safety program(s) of the F-CPU(s) of one or more I-slaves takes place over master-I-
slave connections (
F-
MS), as in standard systems.
You do not need a DP/DP coupler for master-I-slave communication.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
230 Programming and Operating Manual, 10/2018, A5E02714440-AH
Configuring transfer areas
For every safety-related communication connection between two F-CPUs, you must
configure transfer areas in the
hardware and network editor
. The figure below shows how
both of the F-CPUs are able to send and receive data (bidirectional communication).
The transfer area is assigned a label when it is created to identify it as the communication
relationship. For example, "F-MS_PLC_2-PLC_1_1" for the first F-MS connection between
DP master F-CPU 1 and I-slave F-CPU 2.
You assign the start addresses of the transfer areas to the LADDR input of the SENDDP and
RCVDP instructions in the safety programs.
Procedure for configuration
The procedure for configuring safety-related master-I-slave communication is identical to that
in the standard system.
Proceed as follows:
1. Insert two F-CPUS from the "Hardware catalog" task card into the project.
2. Activate the "DP slave" mode (I-slave) for F-CPU 2 in the properties of its DP interface
and assign this DP interface to a DP interface of F-CPU 1.
3. Select the PROFIBUS interface of F-CPU 2. Under "Transfer areas", you create an F-MS
connection (type "F-MS") for sending to the DP master (←). The F-MS connection is
shown in yellow in the table and the transfer areas in the I-slave and DP master assigned
outside of the process image are displayed.
In addition, an acknowledgment connection is created automatically for each F-MS
connection. (see "Transfer area details").
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 231
4. Create an additional F-MS connection for receiving from the DP master.
5. In the transfer area you just created, click the arrow in order to change the transfer
direction to receiving from DP master (→).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
232 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.1.5.2
Safety-related master-I-slave or I-slave-I-slave communication via SENDDP and
RCVDP
Communication via SENDDP and RCVDP instructions
Safety-related communication between the F-CPUs of the DP master and an I-slave or
between the F-CPUs of multiple I-slaves makes use of the SENDDP and RCVDP
instructions for sending and receiving, respectively. These can be used to perform a fail-safe
transfer of a
fixed
amount of fail-safe data of the data type INT or BOOL.
You can find these instructions in the "Instructions" task card under "Communication". The
RCVDP instruction
must
be called at the start of the main safety block. The SENDDP
instruction
must
be called at the end of the main safety block.
Note that the send signals are not sent until after the SENDDP instruction call at the end of
execution of the relevant F-runtime group.
A detailed description of the SENDDP and RCVDP instructions can be found in SENDDP
and RCVDP: Send and receive data via PROFIBUS DP/PROFINET IO (STEP 7 Safety
V15.1) (Page 588).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 233
9.1.5.3
Program the safety-related master-I-slave or I-slave-I-slave communication
Requirements
The transfer areas must be configured.
Programming procedure
The procedure for programming safety-related master-I-slave communication or I-slave-I-
slave communication is the same as that for programming safety-related master-master
communication (see Program safety-related master-master communication (Page 218)).
The assignment of the start addresses of the transfer areas to the LADDR input of the
SENDDP/RCVDP instructions can be obtained from the following table.
Instruction
Start address LADDR
From row
From column
SENDDP in the DP master Master address
RCVDP in the DP master
Master address
SENDDP in the I-slave
Slave address
RCVDP in the I-slave
Slave address
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
234 Programming and Operating Manual, 10/2018, A5E02714440-AH
The figure below contains an example of how to specify the F-communication IDs at the
inputs of SENDDP and RCVDP instructions for four safety-related master-I-slave and two
I-slave-I-slave communications relationships.
WARNING
The value for the respective F-communication ID (input DP_DP_ID; data type: INT) can be
freely selected; however, it must be unique for all safety-related communication
connections network-wide* and CPU-wide at all times. The uniqueness must be checked in
the safety summary during acceptance of the safety program. You can find additional
information in Correctness and completeness of the communication configuration
(Page 374).
You must supply inputs DP_DP_ID and LADDR with constant values when calling the
instruction. Direct write accesses in the associated instance DB to DP_DP_ID and LADDR
are not permitted in the safety program!
(S016)
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet. In PROFIBUS, a network includes all nodes accessible via PROFIBUS DP. In
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 235
PROFINET IO, a network includes all nodes accessible via RT_Class_1/2/3
(Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP (IP, Layer 3).
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal state to be transferred will
be acquired at the sender end and transferred to the receiver if the signal level is pending
for at least as long as the assigned monitoring time.
(S018)
Information on calculating the monitoring times can be found in Monitoring and response
times (Page 607).
9.1.5.4
Limits for data transfer of safety-related master-I-slave or I-slave-I-slave
communication
Limits for data transfer
If the amount of data to be transferred is greater than the capacity of related
SENDDP/RCVDP instructions, you can use additional SENDDP/RCVDP instructions.
Configure additional transfer areas for this purpose. Note the maximum limit of 244 bytes of
input data or 244 bytes of output data for transfer between an I-slave and a DP master.
The following table shows the amount of output and input data assigned in safety-related
communication connections:
Safety-related
communication
Communication
connection
Assigned input and output data
DP master
I-slave 1
I-slave 2
Output data
Input data
Output data
Input data
Output data
Input data
Master-I-slave
Sending:
I-slave 1 to DP
master
6 bytes 12 bytes 12 bytes 6 bytes
Receiving:
I-slave 1 from DP
master
12 bytes 6 bytes 6 bytes 12 bytes
I-slave-I-slave
Sending:
I-slave 1 to I-
slave 2
18 bytes 12 bytes 6 bytes 6 bytes 12 bytes
Receiving:
I-slave 1 from I-
slave 2
18 bytes 6 bytes 12 bytes 12 bytes 6 bytes
Consider all additional configured safety-related and standard communication connections
(transfer areas of type F-MS-, F-DX-, F-DX-Mod., MS-, DX- and DX-Mod) for the maximum
limit of 244 bytes of input data or 244 bytes of output data for transfer between an I-device
and a DP master F-MS, F-DX, F-DX-Mod., MS, DX). If the maximum limit of 244 bytes of
input data or 244 bytes of output data is exceeded, you will receive a corresponding error
message.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
236 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.1.6
Safety-related I-slave-I-slave communication
9.1.6.1
Configure safety-related I-slave-I-slave communication
Introduction
Safety-related communication between the safety program of the F-CPUs of I-slaves takes
place using direct data exchange (
F-
DX) same as in standard programs.
You do not need any additional hardware for I-slave-I-slave communication.
I-slave-I-slave communication is also possible:
If the assigned DP master is a standard CPU that supports direct data exchange
when instead of a DP master, an IO controller is networked with the I-slaves via an IE/PB
link
Configuring transfer areas
For every safety-related communication connection between two I-slaves, you must
configure transfer areas in the
hardware and network editor
. In the figure below, both of the
I-slaves are to be able to send and receive data (bidirectional communication).
The transfer area is assigned a label when it is created to identify it as the communication
relationship. For example, "F-DX_PLC_2-PLC_1_1" for the first F-DX connection between F-
CPU 1 and F-CPU 2.
You assign the start addresses of the transfer areas to the LADDR input of the SENDDP and
RCVDP instructions in the safety programs.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 237
Procedure for configuration
The procedure for configuring safety-related I-slave-I-slave communication is identical to that
in the standard system. Proceed as follows:
1. Insert three F-CPUS from the "Hardware catalog" task card in the project.
2. Activate "DP slaves" mode (I-slave) for F-CPU 2 and F-CPU 3 in the properties of their
DP interfaces and assign these DP interfaces to a DP interface of F-CPU 1.
3. Select the DP interface of F-CPU 3 in the network view.
4. Select the "I/O communication" tab.
5. Use a drag-and-drop operation in the network view to move F-CPU 2 to the "Partner 2"
column on the "I/O-communication" tab.
This creates a line with "Direct data exchange" mode for sending to the I-slave (F-CPU 2)
(→).
6. Click in the newly created line (→).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
238 Programming and Operating Manual, 10/2018, A5E02714440-AH
7. In "Transfer areas" ("Direct data exchange" table), create an F-DX connection (type
"F-DX") for sending to the I-slave (F-CPU 2) (→). The F-DX connection is shown in yellow
in the table and the transfer areas in the I-slaves assigned outside of the process image
(PLC_2 and PLC_3) are displayed.
In addition, a line with "Direct data exchange" mode for receiving from the I-slave (F-CPU
2) (→) is created automatically in the "I/O communication" tab, and an acknowledgment
connection (←, transfer area x_Ack) is created automatically in the associated "Direct data
exchange" table.
One transfer area (type F-MS) for the master CPU (disabled in display) is created for in
the "I-slave communication table" of each I-slave.
This completes the configuration for sending to F-CPU 2.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 239
8. In the "I/O communication" tab, select the automatically created line with "Direct data
exchange" mode for receiving from the I-slave (F-CPU 3) (←).
9. In "Transfer areas" ("Direct data exchange" table), create another F-DX connection for
receiving from the I-slave (F-CPU 3).
In this case, as well, an acknowledgment connection (←, transfer area x_Ack) is created
automatically in the "Direct data exchange table" and two transfer areas (type F-MS) for
the master CPU (disabled in display) are created in the "I-slave communication" table of
both I-slaves.
This completes the configuration for receiving from F-CPU 2.
Changing disabled local address areas of the transfer areas
In order to change the disabled local address area of "Transfer area x", you must change the
address area of the corresponding acknowledgment connection "Transfer area x_Ack".
1. In "I/O communication", select the line with the arrow pointing in the same direction as the
arrow of "Transfer area x" in the "Direct data exchange" table.
2. Then select the line with "Transfer area x_Ack" in the "Direct data exchange" table.
3. Change the address area there.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
240 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.1.6.2
Safety-related I-slave-I-slave communication via SENDDP and RCVDP
Reference
The description of the communication via SENDDP and RCVDP for safety-related I-slave-I-
slave communication can be found in SENDDP and RCVDP: Send and receive data via
PROFIBUS DP/PROFINET IO (STEP 7 Safety V15.1) (Page 588).
9.1.6.3
Programming safety-related I-slave-I-slave communication
Reference
The description of the programming of safety-related I-slave-I-slave communication can be
found in Program the safety-related master-I-slave or I-slave-I-slave communication
(Page 233).
The assignment of the start addresses of the transfer areas to the LADDR input of the
SENDDP/RCVDP instructions can be obtained from the following table.
Instruction
Start address LADDR
From row
From column
SENDDP in the 1st I-slave Address in the <1st I-slave>
(in example column "Address in
PLC_2")
RCVDP in the 1st I-slave Address in the <1st I-slave>
(in example column "Address in
PLC_2")
SENDDP in the 2nd I-slave Address in the <2nd I-slave>
(in example column "Address in
PLC_3")
RCVDP in the 2nd I-slave Address in the <2nd I-slave>
(in example column "Address in
PLC_3")
9.1.6.4
Limits for data transfer of safety-related I-slave-I-slave communication
Limits for data transfer
The description of the limits for the data transfer of safety-related I-slave-I-slave
communication can be found in Limits for data transfer of safety-related master-I-slave or I-
slave-I-slave communication (Page 235).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 241
9.1.7
Safety-Related I-Slave-Slave Communication
9.1.7.1
Configuring Safety-Related I-Slave-Slave Communication
Introduction
Safety-related communication between the safety program of the F-CPU of an I-slave and F-
I/O in a DP slave takes place using direct data exchange (
F-
DX-Mod), same as in standard
programs.
You do not need any additional hardware for I-slave-slave communication.
I-slave-slave communication is also possible:
when the assigned DP master is a standard CPU, if the standard CPU supports direct
data exchange
when instead of a DP master, an IO controller is networked with the I-slaves via an IE/PB
link
An F-I/O DB is automatically generated for each F-I/O when it is configured in the
hardware and network editor
; this is required for the F-I/O access via safety-related I-slave-
slave communication. The F-I/O DB is initially created in the safety program of the DP
master, provided it is an F-CPU with F-activation. Only with the setup of the F-DX-Mod
connection is the F-I/O DB created in the safety program of the I-slave and deleted in the
safety program of the DP master.
The process image input is used to access the channels of the F-I/O in the safety program of
the F-CPU of the I-slave (see description in Safety-Related I-Slave-Slave Communication -
F-I/O Access (Page 246)).
Restrictions
Note
Safety
-related I-slave-slave communication with F-
I/O is possible in a DP slave that supports
safety
-related I-slave-slave communication, for example with all ET 200SP F-modules with
IM 155
-6 DP HF, firmware version > V3.1, with all ET 200S F-modules with IM 151-1 HF,
with all f
ail-safe S7-300 signal modules with IM 153-2, as of article
number
6ES7153-2BA01-0XB0, firmware version > V4.0.0.
Note
With safety
-related I-slave-slave communication, make sure that the CPU of the DP master
is powered up before the F
-CPU of the I-slave.
Otherwise, depending on the F
-monitoring time specified for the F-I/O, the F-system can
detect an error in safety
-related communication (communication error) between the F-CPU
and the F
-I/O assigned to the I-slave. This means that the F-I/O are not reintegrated
automatically after F
-system startup. They are instead only reintegrated after a user
acknowledgment with a positive edge in the ACK_REI tag of the F
-I/O DB (see also After
communication err
ors (Page 178) and After startup of F-system (Page 175)).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
242 Programming and Operating Manual, 10/2018, A5E02714440-AH
Configuring transfer areas
For every safety-related communication connection between an I-slave and slave, you must
configure transfer areas in the
hardware and network editor
.
The transfer area is assigned a label when it is created to identify it as the communication
relationship. For example, "F-DX-Mod_PLC_2-PLC_1_1" for the first F-DX-Mod connection
between F-CPU 1 and F-CPU 2.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 243
Configuration procedure using the example of an ET 200S with F-modules in the slave
The procedure for configuring safety-related I-slave-slave communication is identical to that
in the standard system.
Proceed as follows:
1. Insert two F-CPUS from the "Hardware catalog" task card into the project.
2. Insert a suitable DP slave, e.g. IM 151-1 HF, article no. 6ES7151-1BA0... from the
"Hardware catalog" task card into the network view of the
hardware and network editor
.
3. Insert a power module, a 4/8 F-DI module and a 4 F-DQ module in the device view of the
ET 200S.
4. Activate "DP slave" mode (I-slave) for F-CPU 2 in the properties of its DP interface and
assign this to F-CPU 1.
5. Assign the DP interface of the IM 151-1 HF to the DP master (F-CPU 1).
6. Select the DP interface of F-CPU 2 (I-slave) in the network view.
7. Select the "I/O communication" tab.
8. Use a drag-and-drop operation in the network view to move the ET 200S to the "Partner
2" column in the "I/O-communication" tab.
9. Click in the newly created line (←).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
244 Programming and Operating Manual, 10/2018, A5E02714440-AH
10.In "Transfer areas", create an F-DX-Mod connection (type "F-DX-Mod"). The F-DX-Mod
connection is marked in yellow in the table. The addresses for the "partner module" 4/8
F-DI in the I-Slave (PLC_2) are displayed. You can change the addresses directly in the
table, if required.
This completes the configuration for the 4/8 F-DI module.
11.In "Transfer areas", create another F-DX-Mod connection.
12.Change the partner module to the 4 F-DO module, either directly in the "Transfer areas"
table or in the details of transfer area 2, if the 4 F-DO module was not already selected.
This completes the configuration for the 4 F-DO module.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 245
In the "I-slave communication table" of the I-slave, a transfer area (type F-MS) for the master
CPU (disabled in display) is created for each F-DX-Mod connection:
Change in configuration of I-slave-slave communication
WARNING
If you have reconfigured I-slave-slave communication for an F-I/O or have deleted an
existing I-slave-slave communication, you must compile the hardware configuration of the
DP master as well as the hardware configuration of the I-slave and download them to the
DP master and I-slave, respectively.
The collective F-signature in the F-CPU of the I-slave and the collective F-signature in the
F-CPU of the DP master (if a safety program exists there, too) are set to "0". You must then
recompile the safety program(s).
(S019)
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
246 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.1.7.2
Safety-Related I-Slave-Slave Communication - F-I/O Access
Access via the process image
In safety-related I-slave-slave communication, you use the process image (PII or PIQ) to
access the F-I/O in the safety program of the F-CPU of the I-slave. This is the same as F-I/O
access to F-I/O that are directly assigned to an I-slave or DP master. In the I-slave you
access the F-I/O with the addresses that were assigned for the F-DX-Mod connection in
"Transfer areas" ("Direct data exchange" table).
In this case, ignore the displayed operand area. Access F-I/O with inputs using the PII and
F-I/O with outputs using PIQ.
Information on I/O access can be found in F-I/O access (Page 157).
9.1.7.3
Limits for data transfer of safety-related I-slave-I-slave communication
Limits for data transfer
Note the maximum limit of 244 bytes of input data or 244 bytes of output data for transfer
between an I-slave and a DP master.
An example of the amount of output data and input data that are assigned for safety-related
communication is shown in the table below for an ET 200S 4/8 F-DI and an ET 200S 4
F-DO:
Safety-related
communication
Communication connection
Assigned input and output data*
Between I-slave and DP master
Output Data in the
I-slave
Input data in the I-
slave
I-slave-slave I-slave-slave communication with
4/8 F-DI
4 bytes 6 bytes
I-slave-slave communication with
4 F-DO
5 bytes 5 bytes
* Example for 4/8 F-DI and 4 F-DO of ET 200S
Consider all additional configured safety-related and standard communication connections
(F-MS, F-DX, F-DX-Mod., MS and DX connections) for the maximum limit of 244 bytes of
input data or 244 bytes of output data for transfer between an I-slave and a DP master. If the
maximum limit of 244 bytes of input data or 244 bytes of output data is exceeded, you will
receive a corresponding error message.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 247
9.1.8
Safety-related IO controller-I-slave communication
Introduction
Safety-related communication between the safety program of the F-CPU of an IO-controller
and the safety program(s) of the F-CPU(s) of one or more I-slaves takes place over master
-I-slave connections (
F-
MS), as in standard systems.
IE/PB link
For the safety-related IO-controller-I-slave communication, the IE/PB link is mandatory. Each
of the two F-CPUs is linked to the IE/PB link by means of its PROFIBUS DP or PROFINET-
interface.
Note
If you are using an IE/PB link, you mus
t take this into account when configuring the
F
-specific monitoring times and when calculating the maximum response time of your
F
-system (see also Monitoring and response times (Page 607)).
Note that the Excel file for calculating response times
(
http://support.automation.siemens.com/WW/view/en/49368678/133100) for S7-300/400
F
-CPUs does not support all conceivable configurations.
Reference
The information on safety-related master-I-slave communication in Safety-related master-I-
slave communication (Page 229) also applies.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
248 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.1.9
Safety-related communication via S7 connections
9.1.9.1
Configuring safety-related communication via S7 connections
Introduction
Safety-related communication between the safety programs of F-CPUs via S7 connections
takes place by means of established S7 connections that you create in the network view of
the
hardware and network editor
- same as in standard programs.
Restrictions
Note
In SIMATIC
Safety, S7 connections are generally permitted only via Industrial Ethernet.
Safety
-related communication via S7 connections is possible from and to the following
CPUs:
S7-300 F-CPUs via the integrated PROFINET interface
S7-400 F-CPUs via the integrated PROFINET interface or a CP 443-1 or CP 443-1
Advanced-IT
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 249
Creating S7 connections
For each connection between two F-CPUs, you must create an S7 connection in the network
view of the
hardware and network editor
.
For every end-point of a connection, a local and a partner ID is automatically assigned from
the perspective of the end-point (the F-CPU). If necessary, you can change both IDs in the
"Connections" tab. You assign the local ID to the "ID" input of the SENDS7 and RCVS7
instructions in the safety programs.
Procedure for configuring S7 connections
You configure the S7 connections for safety-related CPU-to-CPU communication in the
same way as in
STEP 7 Professional
(see
Help on STEP 7 Professional
"S7 connections").
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
250 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.1.9.2
Communication via SENDS7, RCVS7, and F-Communication DB
Communication via the SENDS7 and RCVS7 instructions
You use the
SENDS7 and RCVS7
instructions for fail-safe sending and receiving of data via
S7 connections.
These instructions can be used to transmit a specified amount of fail-safe data of data types
BOOL, INT, WORD, DINT, DWORD, and TIME in a fail-safe manner. The fail-safe data are
stored in F-DBs (F-communication DBs) that you have created.
You can find these instructions in the "Instructions" task card under "Communication". The
RCVS7 instruction
must
be called at the start of the main safety block. The SENDS7
instruction
must
be called at the end of the main safety block.
Note that the send signals are sent only after calling the SENDS7 instruction at the end of
the relevant F-runtime group execution.
A detailed description of the SENDS7 and RCVS7 instructions is found in SENDS7 and
RCVS7: Communication via S7 connections (STEP 7 Safety Advanced V15.1) (S7-300,
S7-400) (Page 599).
F-communication DB
For each connection, send data are stored in an F-DB (F-communication DBx) and receive
data are stored in an F-DB (F-communication DBy).
You can assign the F-communication DB numbers in the SENDS7 and RCVS7 instructions.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 251
9.1.9.3
Programming safety-related communication via S7 connections
Introduction
The programming of safety-related CPU-CPU communication via S7 connections is
described below. You must set up the following in the safety programs of the relevant
F-CPUs:
Create F-DBs (F-Communication-DBs) in which send/receive data for communication are
stored.
Call and assign parameters for instructions for communication from the "Instructions"
Task Card in the safety program.
Requirement for programming
The S7 connections between the relevant F-CPUs must be configured in the network view in
the "Connections" tab of the
hardware and network editor
.
Creating and Editing an F-Communication DB
F-communication DBs are F-DBs that you create and edit in the same way as other F-DBs in
the project tree. You can assign the F-communication DB numbers in the SENDS7 and
RCVS7 instructions.
Note
The length and structure of the F
-communication DB on the receiver side must match the
length and structure of the associated F
-communication DB on the sender side.
If the F
-communication DBs do not match, the F-CPU can go to STOP mode. A diagnostics
event is entered in the diagnostics buffer of the F
-CPU.
For this reason, we recommend that you use the following procedure:
1.
Create an F-communication DB in the project
tree in or below the "Program blocks" folder
of the F-CPU at the sender end.
2.
Specify the appropriate structure of the F-
communication DB, taking into account the data
to be transferred.
3.
Copy this F-communication DB to the project tree in or below the "Program blocks" folder
of the F-CPU at the receiver end, and change the name, if necessary.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
252 Programming and Operating Manual, 10/2018, A5E02714440-AH
Other requirements for F-communication DBs
F-communication DBs must also conform to the following properties:
They are not permitted to be instance DBs.
Their length is not permitted to exceed 100 bytes.
In F-communication DBs, only the following data types may be declared: BOOL, INT,
WORD, DINT, DWORD, and TIME.
The data types must be arranged block-wise and in the following order: BOOL, data types
with bit length of 16 bits (INT, WORD), and data types with bit length of 32 bits (DINT,
DWORD, and TIME). Within the data blocks with lengths of 16 bits and 32 bits, the data
types can be arranged in any order.
No more than 128 data elements of data type BOOL are permitted to be declared.
The amount of data of data type BOOL must always be an integer multiple of 16 (word
limit). Reserve data must be added, if necessary.
If these criteria are not fulfilled,
STEP 7 Safety Advanced
outputs an error message during
compilation.
Assignment of fail-safe values
Fail-safe values are made available at the receiver end:
While the connection between the communication partners is being established the first
time after startup of the F-systems
Whenever a communication error occurs
The values you specified as initial values in the F-communication DB at the receiver end are
made available as initial values.
Programming procedure
You program safety-related communication via S7 connections as follows:
1. Supply the tags in the F-communication DB at the sender end with send signals using
fully qualified access (e.g., "Name of F-communication DB".tag name).
2. Read the tags in the F-communication DB at the receiver end (receive signals) that you
want to process further in other sections of the program using fully qualified access (e.g.,
"Name of F-communication DB".tag name).
3. In the safety program from which data are to be sent, call the SENDS7 instruction for
sending at the end of the main safety block.
4. In the safety program in which data are to be received, call the instruction RCVS7 for
receiving at the start of the main safety block.
5. Assign F-communication DB numbers to the SEND_DB input of SENDS7 and the
RCV_DB input of RCVS7.
6. Assign the local ID of the S7 connection (data type: WORD) from the perspective of the
F-CPU that was configured in the "Connections" tab of the network view to the ID input of
SENDS7.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 253
7. Assign the local ID of the S7 connection (data type: WORD) that was configured in the
"Connections" tab of the network view to the ID input of RCVS7.
8. Assign an odd number (data type: DWORD) to the R_ID inputs of SENDS7 and RCVS7.
This serves to specify that a SENDS7 instruction belongs to an RCVS7 instruction. The
associated instructions receive the same value for R_ID.
WARNING
The value for the respective F-communication ID (input R_ID; data type: DWORD) can
be freely selected; however, it must be odd for all safety-related communication
connections network-wide* and CPU-wide. The value R_ID + 1 is internally assigned
and must not be used.
You must supply inputs ID and R_ID with constant values when calling the instruction.
Direct read or write access to the associated instance DB is not permitted in the safety
program.
(S020)
* A network consists of one or more subnets. "Network-wide" means beyond the
boundaries of the subnet. In PROFIBUS, a network includes all nodes accessible via
PROFIBUS DP. In PROFINET IO, a network includes all nodes accessible via
RT_Class_1/2/3 (Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP
(IP, Layer 3).
9. Assign the TIMEOUT inputs of the SENDS7 and RCVS7 instructions with the required
monitoring time.
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal state to be transferred
will be acquired at the sender end and transferred to the receiver if the signal level is
pending for at least as long as the assigned monitoring time.
(S018)
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
254 Programming and Operating Manual, 10/2018, A5E02714440-AH
Information on calculating the monitoring times can be found in Monitoring and response
times (Page 607).
10.To reduce the bus load, you can temporarily shut down communication between the F-
CPUs at input EN_SEND of the SENDS7 instruction. To do so, supply input EN_SEND
(initial value = "TRUE") with 0. In this case, send data are no longer sent to the F-
communication DB of the associated RCVS7 instruction and the receiver RCVS7
provides fail-safe values for this period (initial values in its F-communication DB). If
communication was already established between the partners, a communication error is
detected.
11.Optional: Evaluate the ACK_REQ output of RCVS7, for example, in the standard user
program or on the HMI system in order to query or to indicate whether user
acknowledgment is required.
12.Supply the ACK_REI input of RCVS7 with the signal for the acknowledgment for
reintegration.
13.Optional: evaluate the SUBS_ON output of RCVS7 or SENDS7 in order to query whether
the RCVS7 instruction is outputting the fail-safe values you specified as initial values in
the F-communication DB.
14.Optional: Evaluate the ERROR output of RCVS7 or SENDS7, for example, in the
standard user program or on the HMI system in order to query or to indicate whether a
communication error has occurred.
15.Optional: evaluate the SENDMODE output of RCVS7 in order to query whether the F-
CPU with the associated SENDS7 instruction is in disabled safety mode (Page 344).
Particularities for migrated projects
If you have migrated a project from
S7 Distributed Safety V5.4 SP5
to
STEP 7 Safety
Advanced
in which safety-related communication via S7 connections is programmed, you
must note the following:
Do not delete migrated instance DBs for the SENDS7 and RCVS7 instructions in the
project tree in the "STEP 7 Safety" folder under "Program blocks > System blocks".
Otherwise, communication errors may occur in the relevant communication connections.
A migrated instance DB for the SENDS7 and RCVS7 instructions has been deleted if, after
compiling the safety program, the "User-defined ID" in the newly generated is not identical to
"FRCVS7CL" or "FSNDS7CL".
You can find the "User-defined ID" of a block in its properties in the "Information" area.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 255
9.1.9.4
Safety-related communication via S7 connections - Limits of data transfer
Note
If the amount of data to be transmitted exceeds the permitted length for the F
-
communication
DB
(100 bytes), you can create another F-communication DB that you transfer to additional
SENDS7/RCVS7 instructions with modified R_ID.
Note that USEND and URCV instructions are called internally at each SENDS7 or RCVS7
call and use connection resources in the F-CPU. This affects the maximum number of
communication connections available (
see manuals for F-CPUs
).
Additional information on the data transfer limits for S7 connections of individual F-CPUs is
available on the Internet (http://support.automation.siemens.com/WW/view/en/38549114).
9.1.10
Safety-related communication with other S7 F-systems
9.1.10.1
Introduction
Safety-related communication from F-CPUs in SIMATIC Safety to F-CPUs in S7 Distributed
Safety F-systems is possible via a PN/PN coupler or DP/DP coupler that you use between
the two F-CPUs as IO controller-IO controller communication, master-master communication
or communication via established S7 connections.
Safety-related communication from F-CPUs in SIMATIC Safety to F-CPUs in S7 F/FH
Systems F-systems is possible via established S7 connections.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
256 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.1.10.2
Communication with S7 Distributed Safety via PN/PN coupler (IO controller-IO
controller communication)
Communication functions between SENDDP/RCVDP instructions at the
STEP 7 Safety
Advanced
end and F-application blocks F_SENDDP/F_RCVDP at the
S7 Distributed Safety
end:
Procedure at the
S7 Distributed Safety
end
At the
S7 Distributed Safety
end, proceed as described in "Safety-related IO controller-IO
controller communication" in the S7 Distributed Safety - Configuring and Programming
(http://support.automation.siemens.com/WW/view/en/22099875) manual.
Procedure at the
STEP 7 Safety Advanced
end
At the
STEP 7 Safety Advanced
end, proceed as described in Safety-related IO controller-IO
controller communication (Page 204).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 257
9.1.10.3
Communication with S7 Distributed Safety via DP/DP coupler (master-master
communication)
Communication functions between SENDDP/RCVDP instructions at the
STEP 7 Safety
Advanced
end and F-application blocks F_SENDDP/F_RCVDP at the
S7 Distributed Safety
end:
Procedure at the
S7 Distributed Safety
end
At the
S7 Distributed Safety
end, proceed as described in "Safety-related master-master
communication" in the S7 Distributed Safety - Configuring and Programming
(http://support.automation.siemens.com/WW/view/en/22099875) manual.
Procedure at the
STEP 7 Safety Advanced
end
At the
STEP 7 Safety Advanced
end, proceed as described in Safety-related master-master
communication (Page 213).
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
258 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.1.10.4
Communication with S7 Distributed Safety via S7 connections
Communication functions between SENDS7/RCVS7 instructions at the
STEP 7 Safety
Advanced
end and F_SENDS7/F_RCVS7 F-application blocks at the
S7 Distributed Safety
end:
Procedure at the
S7 Distributed Safety
end
At the
S7 Distributed Safety
end, proceed as described in section "Safety-related
communication via S7 communications" in the S7 Distributed Safety - Configuring and
Programming (http://support.automation.siemens.com/WW/view/en/22099875) manual.
Because safety-related communication via S7 connections is not possible with unspecified
partners in S7 Distributed Safety, you must first create a "virtual" SIMATIC station in
S7
Distributed Safety
in which you configure an F-CPU as a proxy for the F-CPU in
STEP 7
Safety Advanced
with its IP address.
You then insert an S7 connection to this F-CPU in the connection table. Both the local
connection and partner connection resources (hex) are thereby fixed. You must then set
these in the associated, unspecified S7 connection that you created in
STEP 7 Professional
.
In addition, for all communication connections to this F-CPU, you must transfer the F-
communication ID that you assigned in the R_ID input of the associated calls of the
F_SENDS7 and F_RCVS7 F-application blocks additionally to the CRC_IMP tag in the
instance DB of F_SENDS7 and F_RCVS7, respectively, in the standard user program
immediately before calling the F-CALL.
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 259
Program example:
Procedure at the
STEP 7 Safety Advanced
end
At the
STEP 7 Safety Advanced
end, proceed as described in Safety-related communication
via S7 connections (Page 248).
For the F-CPU in
S7 Distributed Safety
, you must create and specify an unspecified S7
connection. You can find information on this in the
STEP 7
help, under "Creating an
unspecified connection" or "Specifying and unspecified connection".
For these you must set the local and partner connection resources (hex) that are fixed as a
result of the associated S7 connection that you have created in
S7 Distributed Safety
.
If the local connection resource (hex) is already occupied by an existing connection, you
must change the connection resource (hex) for it.
If the instance DBs of the SENDS7 and RCVS7, instructions that you want to use for
communication with
S7 Distributed Safety
were migrated from
S7 Distributed Safety
, you
must delete them in the project tree in the "STEP 7 Safety" folder, under "Program blocks >
System blocks" (contrary to the information in Programming safety-related communication
via S7 connections (Page 251), section "Particularities for migrated projects").
Safety-related communication
9.1 Configuring and programming communication (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
260 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.1.10.5
Communication with S7 F/FH Systems via S7 connections
Communication functions between SENDS7/RCVS7 instructions at the
STEP 7 Safety
Advanced
end and F_SDS_BO/F_RDS_BO F-blocks at the
S7 F Systems
end.
A maximum of 32 data elements of data type BOOL can be exchanged.
Procedure at the
S7 F Systems
end
At the
S7 F-systems
end, proceed as described in section "Safety-related communication
between F-CPUs" in the S7 F/FH Systems - Configuring and Programming
(http://support.automation.siemens.com/WW/view/en/16537972) manual.
Because safety-related communication via S7 connections is not possible with unspecified
partners in
S7 F/FH Systems
, you must first create a "virtual" SIMATIC station in
S7 F/FH
Systems
in which you configure an F-CPU as a proxy for the F-CPU in
STEP 7 Safety
Advanced
with its IP address.
You then insert an S7 connection to this F-CPU in the connection table. Both the local
connection and partner connection resources (hex) are thereby fixed. You must then set
these in the associated, unspecified S7 connection that you created in
STEP 7
Safety Advanced
.
In addition, you must insert a function in your S7 program (in the area reserved in CFC for
other applications), in which, for all communication connections for this F-CPU, you transfer
the F-communication ID that you assigned in the R_ID input of the associated calls of the
F_SDS_BO and F_RDS_BO F-blocks additionally to the CRC_IMP tag in the instance DB of
the F_SDS_BO and F_RDS_BO, respectively. You obtain the number of the instance DB
from the object properties of the block in CFC. Assign descriptive names for these instance
DBs. If you perform a compress operation in CFC, you must check whether the numbers of
these instance DBs have changed.
Safety-related communication
9.2 Configuring and programming communication with Flexible F-Link (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 261
Program example:
You must then import the function in CFC as block type and insert your standard user
program in a chart. In the run sequence, make sure that the associated standard runtime
group is processed before the F-runtime group.
Procedure at the
STEP 7 Safety Advanced
end
At the
STEP 7 Safety Advanced
end, proceed as described in "Safety-related
communication via S7 connections" (Page 248).
Particularity:
In
STEP 7 Safety Advanced
, you must create the F-communication DB with
exactly 32 data elements of data type BOOL.
For the F-CPU in
S7 F/FH Systems
, you must create and specify an unspecified S7
connection. You can find information on this in the
STEP 7
help under "Creating an unspecified connection" or "Specifying and unspecified
connection".
For these you must set the local and partner connection resources (hex) that are fixed as a
result of the associated S7 connection that you have created in
S7 F Systems
.
If the local connection resource (hex) is already occupied by an existing connection, you
must change the connection resource (hex) for it.
Safety-related communication
9.2 Configuring and programming communication with Flexible F-Link (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
262 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.2
Configuring and programming communication with Flexible F-Link
(S7-1200, S7-1500)
9.2.1
Flexible F-Link
Introduction
As of
STEP 7 Safety V15.1
a new fail-safe CPU-CPU communication "Flexible F-Link" is
available for the F-CPUs S7-1200 and S7-1500. This means fail-safe data can be easily
exchanged as fail-safe arrays with standard communication mechanisms between F-CPUs.
Flexible F-Link offers a series of advantages for exchanging fail-safe data:
Collection of fail-safe data to be transmitted in F-compliant PLC data types (UDTs)
Up to 100 bytes of fail-safe data per UDT
Support of fail-safe data types
Easy parameter assignment and automatic generation of fail-safe communication DBs
Transmission of fail-safe data with standard communication blocks also across network
limits
F-runtime group communication (Page 96) for F-CPUs 1200/1500
System-integrated and globally sufficiently unique F-communication UUID
Separate F-communication address signature for easy detection of changes to the F-
communication UUID
Requirement
S7-1500 F-CPUs as of firmware V2.0
S7-1200 F-CPUs as of firmware V4.2
As of safety system version V2.2
Safety-related communication
9.2 Configuring and programming communication with Flexible F-Link (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 263
Principles of communication via Flexible F-Link
Proceed as follows on the
send side
:
1. Create an F-compliant PLC data type (UDT) for the data to be sent. The size is up to
100 bytes.
2. Create an F-communication with direction "Sending" in the Safety Administration Editor.
A new F-communication DB is created for the F-communication under "Program
blocks\system blocks\STEP 7 Safety\F-communication DBs".
3. Set the F-monitoring time (Page 613) for the F-communication.
4. In the safety program, interconnect the tag for the send data (SEND_DATA) at the
F-communication DB (Page 96) of the F-communication.
5. To transmit the coded, fail-safe arrays, create suitable communication blocks for sending
and receiving (acknowledgment) in the standard program. For processing the process
values in the correct chronological order, you can make use of the F-OB Pre-/post-
processing (Page 87). Note when using standard communication blocks that the fail-safe
arrays are available consistently at the time of evaluation and that the F-monitoring time
(Page 613) is observed.
Use a standard instruction for consistent transfer of SEND_ARRAY (for example
TSEND_C, TSEND or USEND).
Use a standard instruction for consistent receiving of ACK_RCV_ARRAY (for example
TRCV_C, TRCV or URCV).
Safety-related communication
9.2 Configuring and programming communication with Flexible F-Link (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
264 Programming and Operating Manual, 10/2018, A5E02714440-AH
Proceed as follows on the
receive side
:
1. Create an F-compliant PLC data type (UDT) with the same structure as on the send side.
To do so, copy the F-compliant PLC data type (UDT) from the send side or use the
project library or global library.
2. Create an F-communication with the direction "Receiving" in the Safety Administration
Editor.
A new F-communication DB is created for the F-communication under "Program
blocks\system blocks\STEP 7 Safety\F-communication DBs"
3. Copy the F-communication UUID of the F-communication from the send side.
4. Set the same F-monitoring time as for the send side.
5. In the safety program, interconnect the tags for the receive data (RCV_DATA) at the F-
communication DB (Page 96).
6. To transmit the coded, fail-safe arrays, create suitable communication blocks for sending
and receiving (acknowledgment) in the standard program. For processing the process
values in the correct chronological order, you can make use of the F-OB Pre-/post-
processing (Page 96). Note when using standard communication blocks that the fail-safe
arrays are available consistently at the time of evaluation and that the F-monitoring time
(Page 613) is observed.
Use a standard instruction for consistent receiving of RCV_ARRAY (for example
TRCV_C, TSEND or USEND).
Use a standard instruction for consistent transfer of ACK_SEND_ARRAY (for example
TSEND_C, TRCV or URCV).
7. In the safety program, interconnect the tags for the receive data (RCV_DATA) at the F-
communication DB (Page 96) of the F-communication.
WARNING
During the acceptance use the safety summary to verify that the offsets of the elements of
the F-compliant PLC data types (UDT) match for the sending and receiving data within the
safety message frame. For this purpose all members and addresses are listed in the safety
summary per UDT. Also keep in mind that the size can be a up to 100 bytes.
(S088)
WARNING
When a new Flexible F-Link communication is created in the Safety Administration Editor,
the F-communication UUID for the communication is explicitly provided by the system. By
copying communications in Safety Administration Editor within the parameterization table or
when copying into another F-CPU, the F-communication UUIDs are not generated new and
are therefore not unique anymore. If the copy is used to configure a new communication
relationship, you yourself need to ensure the uniqueness. To do this select the affected
UUIDs and regenerate via the "Generate UUID" shortcut menu. The uniqueness must be
ensured in the safety summary during acceptance of the safety program.
(S087)
Safety-related communication
9.2 Configuring and programming communication with Flexible F-Link (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 265
WARNING
You must take the following into account for safety-related CPU-CPU communication with
the communication type Flexible F-Link:
If the F-CPU that sends the data is on a simulated F-CPU with S7 PLCSIM, you can no
longer assume that the data sent by this F-CPU are generated safely. You must then
implement organizational measures such as operation monitoring and manual safety
shutdown to ensure safety in those portions of the system that are affected by the sent
data. Alternatively, you must output fail-safe substitute values instead of the received data
in the F-CPU that receives the data by evaluating SENDMODE*.
* SENDMODE is available to you as a tag in the F-communication DB.
(S086)
See also
Example of a safety-related communication between two F-CPUs (Page 266)
F-runtime group communication (S7-1200, S7-1500) (Page 145)
Safety-related communication
9.2 Configuring and programming communication with Flexible F-Link (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
266 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.2.2
Example of a safety-related communication between two F-CPUs
Safety-related communication between two F-CPUs
If you want to send a data fail-safe from one F-CPU to another F-CPU, follow these steps on
the send side (e.g. F-CPU1):
1. Create an F-compliant PLC data type (UDT) for the data to be sent for F-CPU1. The size
is up to 100 bytes.
2. Create an F-communication with the direction "sending" in the Safety Administration
Editor in the "Flexible F-Link" range.
3. Configure the F-monitoring time and the F-communication UUID.
Information on calculating the F-monitoring times can be found in Monitoring and
response times (Page 607).
For example:
4. On the send side supply the data of the transmission DBs with the data to be sent.
For example:
5. Call a "Connection setup" FB in OB1 of the F-CPU1 and program the connection setup in
this function block.
6. Interconnect a "TCON" instruction twice to set up the communication connection as
follows:
Safety-related communication
9.2 Configuring and programming communication with Flexible F-Link (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 267
7. Call the "TSEND" instruction for the data to be sent in the FC for the post processing
(Page 87) of the F-CPU1.
8. Interconnect a "TSEND" instruction for the data to be sent as follows:
"Sending" is the F-communication DB (Page 96) that sends the data to the F-CPU1.
9. Call the "TRCV" instruction for the acknowledgment in the FC for the pre-processing
(Page 87) of the F-CPU1.
10.Interconnect a "TRCV" instruction for the acknowledgment connection as follows:
"Sending" is the F-communication DB (Page 96) that sends the data to the F-CPU1.
11.Compile the user program.
12.Download the user program to the F-CPU1.
Proceed as follows on the
receive side
(for example F-CPU2):
1. For F-CPU2 create an F-compliant PLC data type (UDT) with the same structure as
F-CPU1 for the data to be received. The size is up to 100 bytes.
To do so, copy the F-compliant PLC data type (UDT) from the send side or use the
project library or global library.
2. Create an F-communication with the direction "receiving" in the Safety Administration
Editor in the "Flexible F-Link" range.
3. Configure the same F-monitoring time and F-communication UUID as for F-CPU1.
For example:
Safety-related communication
9.2 Configuring and programming communication with Flexible F-Link (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
268 Programming and Operating Manual, 10/2018, A5E02714440-AH
4. Read the receiving data from the receiving DB on the receive side.
For example:
5. Call a "Connection setup" FB in OB1 of the F-CPU2 and program the connection setup in
this function block.
6. Interconnect a "TCON" instruction twice to set up the communication connection as
follows:
7. Call the "TRCV" instruction for the data to be received in the FC for the pre-processing
(Page 87) of the F-CPU2.
8. Interconnect a "TRCV" instruction for the data to be received as follows:
"Receiving" is the F-communication DB (Page 96) that sends the data to the F-CPU2.
9. Call the "TSEND" instruction for the acknowledgment in the FC for the post processing
(Page 87) of the F-CPU2.
Safety-related communication
9.2 Configuring and programming communication with Flexible F-Link (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 269
10.Interconnect a "TSEND" instruction for the acknowledgment connection as follows:
"Receiving" is the F-communication DB (Page 96) that sends the acknowledgment
telegram to the F-CPU2.
11.Compile the user program.
12.Download the user program to the F-CPU2.
WARNING
During the acceptance use the safety summary to verify that the offsets of the elements of
the F-compliant PLC data types (UDT) match for the sending and receiving data within the
safety message frame. For this purpose all members and addresses are listed in the safety
summary per UDT. Also keep in mind that the size can be a up to 100 bytes.
(S088)
WARNING
When a new Flexible F-Link communication is created in the Safety Administration Editor,
the F-communication UUID for the communication is explicitly provided by the system. By
copying communications in Safety Administration Editor within the parameterization table or
when copying into another F-CPU, the F-communication UUIDs are not generated new and
are therefore not unique anymore. If the copy is used to configure a new communication
relationship, you yourself need to ensure the uniqueness. To do this select the affected
UUIDs and regenerate via the "Generate UUID" shortcut menu. The uniqueness must be
ensured in the safety summary during acceptance of the safety program.
(S087)
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal state to be transferred will
be acquired at the sender end and transferred to the receiver if the signal level is pending
for at least as long as the assigned monitoring time.
(S018)
See also
FAQ: "How do you program the TCON communication instruction to set up a connection for
Open User Communication between two S7-1500 CPUs?"
(https://support.industry.siemens.com/cs/ww/en/view/58875807)
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
270 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.3
Configuring and programming communication (S7-1200, S7-1500)
9.3.1
Overview of communication
Introduction
This section gives an overview of the safety-related communication options in SIMATIC
Safety F-systems.
Options for safety-related communication
Safety-related communication
On subnet
Additional hardware re-
quired
Safety-related CPU-CPU communication:
IO controller-IO controller communication PROFINET IO PN/PN coupler
Master-master communication
PROFIBUS DP
DP/DP coupler
IO controller-I-device communication
PROFINET IO
Master-I-slave communication
PROFIBUS DP
IO controller-I-slave communication
PROFINET IO and PROFIBUS DP
IE/PB link
IO controller-IO controller communication for
S7
Distributed Safety
PROFINET IO PN/PN coupler
Master-master communication for
S7 Distributed
Safety
PROFIBUS DP DP/DP coupler
Note
Safety
-related communication with S7-1200 F-CPUs is only permitt
ed as of firmware version
V4.1.2.
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 271
Overview of safety-related communication via PROFIBUS DP
The figure below provides an overview of the options for safety-related communication via
PROFIBUS DP in SIMATIC Safety F-systems with S7-1200/1500 F-CPUs.
Safety-related master-master communication
Safety-related master-I-slave communication
Overview of safety-related communication via PROFINET IO
The figure below provides an overview of the options for safety-related communication via
PROFINET IO in SIMATIC Safety F-systems with S7-1200/1500 F-CPUs.
Safety-related IO controller-IO controller communication
Safety-related IO controller-I-device communication
Safety-related IO controller-I-slave communication
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
272 Programming and Operating Manual, 10/2018, A5E02714440-AH
Safety-related CPU-CPU communication via PROFIBUS DP or PROFINET IO
In safety-related CPU-CPU communication, a fixed amount of data of the data type BOOL or
INT (DINT as alternative) is transmitted fail-safe between the safety programs in F-CPUs of
DP masters/I-slaves or IO controllers/I-devices.
The data are transferred using the SENDDP instruction for sending and the RCVDP
instruction for receiving. The data are stored in configured transfer areas of the devices. The
hardware identifier (HW identifier) defines the transfer areas configured.
Safety-related CPU-CPU communication for
S7 Distributed Safety
Safety-related communication is possible from F-CPUs in
SIMATIC Safety
to F-CPUs in
S7
Distributed Safety
.
9.3.2
Safety-related IO controller-IO controller communication
9.3.2.1
Configure safety-related IO controller-IO controller communication
Introduction
Safety-related communication between safety programs of the F-CPUs of IO controllers
takes place over a PN/PN coupler that you set up between the F-CPUs.
Note
Deactivate the "Data validity display DIA" parameter in the properties for the PN/PN coupler
in the
hardware and network editor
. This is the default setting. Otherwise, safety-related IO
controller
-IO controller communication is not possible.
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 273
Configuring transfer areas
You must configure one transfer area for output data and one transfer area for input data in
the
hardware and network editor
for each safety-related communication connection between
two F-CPUs in the PN/PN coupler. The figure below shows how both of the F-CPUs are able
to send
and
receive data (bidirectional communication).
Rules for defining transfer areas
Data to be sent
:
A total of 12 bytes (consistent) is required for the transfer area for output data; 6 bytes
(consistent) are required for the transfer area for input data.
Data to be received
:
A total of 12 bytes (consistent) is required for the transfer area for input data; 6 bytes
(consistent) are required for the transfer area for output data.
Note
PN/PN Coupler article number 6ES7158-3AD10-0XA0
When configuring the transfer areas for the output and input data, proceed as described in
the "SIMATIC bus links PN/PN coupler
(
https://support.industry.siemens.com/cs/ww/en/view/44319532)" manual, section
"Configuring the PN/PN Coupler with STEP 7 TIA Portal".
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
274 Programming and Operating Manual, 10/2018, A5E02714440-AH
Procedure for configuration
The procedure for configuring safety-related IO controller-IO controller communication is
identical to that in the standard system.
Proceed as follows:
1. Insert two F-CPUS from the "Hardware catalog" task card into the project.
2. Switch to the network view of the
hardware and network editor
.
3. Select a PN/PN Coupler X1 and a PN/PN Coupler X2 from "Other field
devices\PROFINET IO\Gateway\Siemens AG\PN/PN Coupler" in the "Hardware catalog"
task card and insert them into the network view of the hardware and network editor.
4. Connect the PN interface of the F-CPU 1 with the PN interface of the PN/PN Coupler X1
and the PN interface of the F-CPU 2 with the PN interface of PN/PN Coupler X2.
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 275
5. Switch to the device view of PN/PN Coupler X1 for bidirectional communication
connections i.e. where each F-CPU is both to send and to receive data. Select the
following modules from "IN/OUT" in the "Hardware catalog" task card (with filter
activated), and insert them in the "Device overview" tab:
One "IN/OUT 6 bytes / 12 bytes" module and
One "IN/OUT 12 bytes / 6 bytes" module
Note
The transfer areas are assigned on the basis of the hardware identifier which is
automatically assigned to the modules and devices. You
need the HW identifier to
program the SENDDP and RCVDP blocks (LADDR input). A system constant is created
in the corresponding F
-CPU for each hardware identifier of the transfer area. You can
assign these system constants symbolically to the SENDDP and RCV
DP blocks.
6. Select the following modules from "IN/OUT" in the device view of PN/PN coupler X2 and
insert them in the "Device overview" tab:
One "IN/OUT 12 bytes / 6 bytes" module and
One "IN/OUT 6 bytes / 12 bytes" module
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
276 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.3.2.2
Safety-related IO controller-IO controller communication via SENDDP and RCVDP
Communication via SENDDP and RCVDP instructions
Safety-related communication between the F-CPUs of the IO controllers uses the SENDDP
and RCVDP instructions for sending and receiving, respectively. These can be used to
perform a fail-safe transfer of a
fixed
amount of fail-safe data of the data type BOOL or INT
(DINT as alternative).
You can find these instructions in the "Instructions" task card under "Communication". The
RCVDP instruction
must
be called at the start of the main safety block. The SENDDP
instruction
must
be called at the end of the main safety block.
You can also call up the RCVDP and SENDDP instructions in separate F-FBs/F-FCs which
you have to call at the start or end of the main safety block.
Note that the send signals are not sent until after the SENDDP instruction call at the end of
execution of the relevant F-runtime group.
A detailed description of the SENDDP and RCVDP instructions can be found in SENDDP
and RCVDP: Send and receive data via PROFIBUS DP/PROFINET IO (STEP 7 Safety
V15.1) (Page 588).
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 277
9.3.2.3
Program safety-related IO controller-IO controller communication
Requirement for programming
The transfer areas for input and output data for the PN/PN coupler must be configured.
Programming procedure
You program safety-related IO controller-IO controller communication as follows:
1. In the safety program from which data are to be sent, call the SENDDP instruction
(Page 588) for sending at the end of the main safety block.
2. In the safety program in which data are to be received, call the RCVDP instruction
(Page 588) for receiving at the start of the main safety block.
3. Assign the respective LADDR inputs HW identifiers (system constants in the default tag
table) for the transfer areas for output and input data of the PN/PN coupler that are
configured in the hardware and network editor.
You must carry out this assignment for every communication connection for each of the
F-CPUs involved.
4. Assign the value for the respective F-communication ID to the DP_DP_ID inputs. This
establishes the communication relationship between the SENDDP instruction in one F-
CPU and the RCVDP instruction in the other F-CPU: The associated instructions receive
the same value for DP_DP_ID.
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
278 Programming and Operating Manual, 10/2018, A5E02714440-AH
The figure below contains an example of how to specify the F-communication IDs at the
inputs of the SENDDP and RCVDP instructions for 5 safety-related IO controller-IO
controller communication relationships.
WARNING
The value for the respective F-communication ID (input DP_DP_ID; data type: INT) can
be freely selected**; however, it must be unique for all safety-related communication
connections network-wide* and CPU-wide at all times. The uniqueness must be
checked in the safety summary during acceptance of the safety program. You can find
additional information in Correctness and completeness of the communication
configuration (Page 374).
You must supply constant values*** to the inputs DP_DP_ID and LADDR when calling
the instruction. Direct write accesses in the associated instance DB to DP_DP_ID and
LADDR are not permitted in the safety program!
(S016)
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 279
* A network consists of one or more subnets. "Network-wide" means beyond the
boundaries of the subnet. In PROFIBUS, a network includes all nodes accessible via
PROFIBUS DP. In PROFINET IO, a network includes all nodes accessible via
RT_Class_1/2/3 (Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP
(IP, Layer 3).
** S7-1200/1500: As of version V3.0 of the SENDDP and RCVDP instructions, no
connection is established at the DP_DP_ID input for a F-communication ID "0".
*** S7-1200/1500: As of version V3.0 of the SENDDP and RCVDP instructions, the
DP_DP_ID input can also be supplied with variable values from a global F-DB. In this
case as well you have to check during the acceptance of the safety program that the
uniqueness is ensured
at every moment
, by checking the algorithm for the creation of the
variable value accordingly. If you cannot ensure a unique F-communication ID during
startup of the safety program, because it is only specified after startup of the safety
program, you must make sure that the value at the DP_DP_ID input is "0" during this
phase.
5. Supply the SD_BO_xx and SD_I_xx inputs (SD_DI_00 as alternative) of SENDDP with the
send signals. To cut down on intermediate signals when transferring block parameters,
you can write the value directly to the instance DB of SENDDP using fully qualified
access (for example, "Name SENDDP_1".SD_BO_02) before calling SENDDP.
6. Supply the RD_BO_xx and RD_I_xx outputs (RD_DI_00 as alternative) of RCVDP with
the signals that you want to process further in other program sections or use fully
qualified access to read the received signals directly in the associated instance DB in the
program sections to be processed further (e.g., "Name RCVDP_1".RD_BO_02).
7. If you want to send the data at the SD_DI_00 input instead of the data at the SD_I_00 and
SD_I_01 inputs, supply the DINTMODE input (initial value = "FALSE") of SENDDP with
TRUE.
8. Supply the SUBBO_xx and SUBI_xx or alternatively SUBDI_00 inputs of RCVDP with the
fail-safe values that are to be output by RCVDP in place of the process data until
communication is established for the first time after startup of the sending and receiving
F-systems or in the event of an error in safety-related communication.
Specification of constant fail-safe values:
For data of data type INT/DINT, you can enter constant fail-safe values directly as
constants in the SUBI_xx or alternatively SUBDI_00 input (initial value = "0"). If you
want to specify a constant fail-safe value "TRUE" for data of the data type BOOL, set
TRUE for the SUBBO_xx input (initial value = "FALSE").
Specification of dynamic fail-safe values:
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
280 Programming and Operating Manual, 10/2018, A5E02714440-AH
If you want to specify dynamic fail-safe values, define a tag that you change
dynamically through your safety program in an F-DB and specify this tag (fully
qualified) in the SUBBO_xx or SUBI_xx or alternatively SUBDI_00 input.
WARNING
Note that your safety program for dynamically changing the tag for a dynamic fail-
safe value can only be processed after the call of the RCVDP, because prior to the
RCVDP call, there must not be any network and no more than one other RCVDP
instruction in the main safety block. You must therefore assign appropriate start
values for these tags to be output by RCVDP in the first cycle after a startup of the
F-system.
(S017)
9. Configure the TIMEOUT inputs of the RCVDP and SENDDP instructions with the required
monitoring time.
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal state to be transferred
will be acquired at the sender end and transferred to the receiver if the signal level is
pending for at least as long as the assigned monitoring time.
(S018)
Information on calculating the monitoring times can be found in Monitoring and response
times (Page 607).
10.Optional: Evaluate the ACK_REQ output of the RCVDP instruction, for example, in the
standard user program or on the HMI system in order to query or to indicate whether user
acknowledgment is required.
11.Supply the ACK_REI input of the RCVDP instruction with the acknowledgment signal for
reintegration.
12.Optional: Evaluate the SUBS_ON output of the RCVDP or SENDDP instruction in order to
query whether the RCVDP instruction is outputting the fail-safe values assigned in the
SUBBO_xx and SUBI_xx or alternatively SUBDI_00 inputs.
13.Optional: Evaluate the ERROR output of the RCVDP or SENDDP instruction, for
example, in the standard user program or on the HMI system in order to query or to
indicate whether a communication error has occurred.
14.Optional: Evaluate the SENDMODE output of the RCVDP instruction in order to query
whether the F-CPU with the associated SENDDP instruction is in disabled safety mode
(Page 344).
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 281
9.3.2.4
Safety-related IO controller-IO controller communication - Limits for data transfer
Note
If the data quantities to be transmitted exceed the capacity of the SENDDP / RCVDP
correlated instructions, a second (or third) SENDDP / RCVDP call
can be used. This requires
configuration of an additional connection via the PN/PN coupler. Whether or not this is
possible with one single PN/PN coupler depends on the capacity restrictions of the PN/PN
coupler.
9.3.3
Safety-related master-master communication
9.3.3.1
Configure safety-related master-master communication
Introduction
Safety-related communication between safety programs of the F-CPUs of DP masters takes
place via a DP/DP coupler.
Note
Switch the data validity indicator "DIA" on the DIP switch of the DP/DP coupler to "OFF".
Otherwise, safety
-related CPU-CPU communication is not possible.
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
282 Programming and Operating Manual, 10/2018, A5E02714440-AH
Configuring transfer areas
You must configure one transfer area for output data and one transfer area for input data in
the
hardware and network editor
for each safety-related communication connection between
two F-CPUs in the DP/DP coupler. The figure below shows how both of the F-CPUs are able
to send and receive data (bidirectional communication).
Rules for defining transfer areas
Data to be sent
:
A total of 12 bytes (consistent) is required for the transfer area for output data; 6 bytes
(consistent) are required for the transfer area for input data.
Data to be received
:
A total of 12 bytes (consistent) is required for the transfer area for input data; 6 bytes
(consistent) are required for the transfer area for output data.
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 283
Procedure for configuration
The procedure for configuring safety-related master-master communication is identical to
that in the standard system.
Proceed as follows:
1. Insert two F-CPUS from the "Hardware catalog" task card into the project.
2. Switch to the network view of the
hardware and network editor
.
3. Select a DP/DP coupler from "Other field
devices\PROFIBUS DP\Gateways\Siemens AG\DP/DP Coupler" in the "Hardware
catalog" task card and insert it into the network view of the hardware and network editor.
4. Insert a second DP/DP coupler.
5. Connect a DP interface of F-CPU 1 to the DP interface of a DP/DP coupler and a DP
interface of F-CPU 2 to the DP interface of the other DP/DP coupler.
6. A free PROFIBUS address is assigned automatically in the properties of the DP/DP-
coupler in the device view. You must set this address on the DP/DP coupler, either via
the DIP switch on the device or in the configuration of the DP/DP coupler (see DP/DP
Coupler (http://support.automation.siemens.com/WW/view/en/1179382) manual).
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
284 Programming and Operating Manual, 10/2018, A5E02714440-AH
7. Switch to the device view of the DP/DP coupler PLC1 for bidirectional communication
connections i.e. where each F-CPU should both send and receive data. Select the
following modules from the "Hardware catalog" task card (with filter activated), and insert
them in the "Device overview" tab of the DP/DP coupler:
One "6 bytes I/12 bytes Q consistent" module, and
One "12 bytes I/6 bytes Q consistent" module
Note
The transfer areas are assigned on the basis of the hardware identifier which is
automatically assigned to the modules a
nd devices. You need the HW identifier to
program the SENDDP and RCVDP blocks (LADDR input). A system constant is created
in the corresponding F
-CPU for each hardware identifier of the transfer area. You can
assign these system constants symbolically to th
e SENDDP and RCVDP blocks.
8. Select the following modules from the "Hardware catalog" task card (with filter activated)
in the device view of DP/DP coupler PLC2, and insert them in the "Device overview" tab:
One "12 bytes I/6 bytes Q consistent" module, and
One "6 bytes I/12 bytes Q consistent" module
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 285
9.3.3.2
Safety-related master-master communication via SENDDP and RCVDP
Communication via SENDDP and RCVDP instructions
Safety-related communication between the F-CPUs of the DP master uses the SENDDP and
RCVDP instructions for sending and receiving, respectively. These can be used to perform a
fail-safe transfer of a
fixed
amount of fail-safe data of the data type BOOL or INT (DINT as
alternative).
You can find these instructions in the "Instructions" task card under "Communication". The
RCVDP instruction
must
be called at the start of the main safety block. The SENDDP
instruction
must
be called at the end of the main safety block.
You can also call up the RCVDP and SENDDP instructions in separate F-FBs/F-FCs which
you have to call up at the start or the end of the main safety block.
Note that the send signals are not sent until after the SENDDP instruction call at the end of
execution of the relevant F-runtime group.
A detailed description of the SENDDP and RCVDP instructions can be found in SENDDP
and RCVDP: Send and receive data via PROFIBUS DP/PROFINET IO (STEP 7 Safety
V15.1) (Page 588).
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
286 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.3.3.3
Program safety-related master-master communication
Requirement for programming
The address areas for input and output data for the DP/DP coupler must be configured.
Programming procedure
You program safety-related master-master communication as follows:
1. In the safety program from which data are to be sent, call the SENDDP instruction
(Page 588) for sending at the end of the main safety block or a separate F-FC/F-FB.
2. In the safety program in which data are to be received, call the RCVDP instruction
(Page 588) for receiving at the start of the main safety block or a separate F-FC/F-FB.
3. Assign the HW identifiers for the output and input data of the DP/DP coupler configured in
the
hardware and network editor
(constant in the tag table) to the respective LADDR
inputs.
You must carry out this assignment for every communication connection for each of the
F-CPUs involved.
4. Assign the value for the respective F-communication ID to the DP_DP_ID inputs. This
establishes the communication relationship between the SENDDP instruction in one
F-CPU and the RCVDP instruction in the other F-CPU: The associated instructions
receive the same value for DP_DP_ID.
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 287
The figure below contains an example of how to specify the F-communication IDs at the
inputs of the SENDDP and RCVDP instructions for 5 safety-related master-master
communications relationships.
WARNING
The value for the respective F-communication ID (input DP_DP_ID; data type: INT) can
be freely selected**; however, it must be unique for all safety-related communication
connections network-wide* and CPU-wide at all times. The uniqueness must be
checked in the safety summary during acceptance of the safety program. You can find
additional information in Correctness and completeness of the communication
configuration (Page 374).
You must supply constant values*** to the inputs DP_DP_ID and LADDR when calling
the instruction. Direct write accesses in the associated instance DB to DP_DP_ID and
LADDR are not permitted in the safety program!
(S016)
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
288 Programming and Operating Manual, 10/2018, A5E02714440-AH
* A network consists of one or more subnets. "Network-wide" means beyond the
boundaries of the subnet. In PROFIBUS, a network includes all nodes accessible via
PROFIBUS DP. In PROFINET IO, a network includes all nodes accessible via
RT_Class_1/2/3 (Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP
(IP, Layer 3).
** S7-1200/1500: As of version V3.0 of the SENDDP and RCVDP instructions, no
connection is established at the DP_DP_ID input for a F-communication ID "0".
*** S7-1200/1500: As of version V3.0 of the SENDDP and RCVDP instructions, the
DP_DP_ID input can also be supplied with variable values from a global F-DB. In this
case as well you have to check during the acceptance of the safety program that the
uniqueness is ensured
at every moment
, by checking the algorithm for the creation of the
variable value accordingly. If you cannot ensure a unique F-communication ID during
startup of the safety program, because it is only specified after startup of the safety
program, you must make sure that the value at the DP_DP_ID input is "0" during this
phase.
5. Supply the SD_BO_xx and SD_I_xx inputs (SD_DI_00 as alternative) of SENDDP with the
send signals. To cut down on intermediate signals when transferring block parameters,
you can write the value directly to the instance DB of SENDDP using fully qualified
access (for example, "Name SENDDP_1".SD_BO_02) before calling SENDDP.
6. Supply the RD_BO_xx and RD_I_xx outputs (RD_DI_00 as alternative) of RCVDP with
the signals that you want to process further in other program sections or use fully
qualified access to read the received signals directly in the associated instance DB in the
program sections to be processed further (e.g., "Name RCVDP_1".RD_BO_02).
7. If you want to send the data at the SD_DI_00 input instead of the data at the SD_I_00 and
SD_I_01 inputs, supply the DINTMODE input (initial value = "FALSE") of SENDDP with
TRUE.
8. Supply the SUBBO_xx and SUBI_xx or alternatively SUBDI_00 inputs of RCVDP with the
fail-safe values that are to be output by RCVDP in place of the process data until
communication is established for the first time after startup of the sending and receiving
F-systems or in the event of an error in safety-related communication.
Specification of constant fail-safe values:
For data of data type INT/DINT, you can enter constant fail-safe values directly as
constants in the SUBI_xx or alternatively SUBDI_00 input (initial value = "0"). If you
want to specify a constant fail-safe value "TRUE" for data of the data type BOOL, set
TRUE for the SUBBO_xx input (initial value = "FALSE").
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 289
Specification of dynamic fail-safe values:
If you want to specify dynamic fail-safe values, define a tag that you change
dynamically through your safety program in an F-DB and specify this tag (fully
qualified) in the SUBBO_xx or SUBI_xx or alternatively SUBDI_00 input.
WARNING
Note that your safety program for dynamically changing the tag for a dynamic fail-
safe value can only be processed after the call of the RCVDP, because prior to the
RCVDP call, there must not be any network and no more than one other RCVDP
instruction in the main safety block. You must therefore assign appropriate start
values for these tags to be output by RCVDP in the first cycle after a startup of the
F-system.
(S017)
9. Configure the TIMEOUT inputs of the RCVDP and SENDDP instructions with the required
monitoring time.
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal state to be transferred
will be acquired at the sender end and transferred to the receiver if the signal level is
pending for at least as long as the assigned monitoring time.
(S018)
Information on calculating the monitoring times can be found in Monitoring and response
times (Page 607).
10.Optional: Evaluate the ACK_REQ output of the RCVDP instruction, for example, in the
standard user program or on the HMI system in order to query or to indicate whether user
acknowledgment is required.
11.Supply the ACK_REI input of the RCVDP instruction with the acknowledgment signal for
reintegration.
12.Optional: Evaluate the SUBS_ON output of the RCVDP or SENDDP instruction in order to
query whether the RCVDP instruction is outputting the fail-safe values assigned in the
SUBBO_xx and SUBI_xx or alternatively SUBDI_00 inputs.
13.Optional: Evaluate the ERROR output of the RCVDP or SENDDP instruction, for
example, in the standard user program or on the HMI system in order to query or to
indicate whether a communication error has occurred.
14.Optional: Evaluate the SENDMODE output of the RCVDP instruction in order to query
whether the F-CPU with the associated SENDDP instruction is in disabled safety mode
(Page 344).
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
290 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.3.3.4
Safety-related master-master communication:Limits for data transfer
Note
If the data quantities to be transmitted exceed the capacity of the SENDDP / RCVDP
correlated instructions, a second (or third) SENDDP /
RCVDP call can be used. This requires
configuration of an additional connection via the DP/DP coupler. Whether or not this is
possible with one single DP/DP coupler depends on the capacity restrictions of the DP/DP
coupler.
9.3.4
Safety-related IO controller-I-device communication
9.3.4.1
Configuring safety-related communication between IO controller and I-device
Introduction
Safety-related communication between the safety program of the F-CPU of an IO controller
and the safety program(s) of the F-CPU(s) of one or more I-devices takes place via IO
controller-I-device connections (F
-
CD) in PROFINET IO, in the same way as in standard
systems.
You do not need any additional hardware for IO controller-I-device communication.
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 291
Configuring transfer areas
For every safety-related communication connection between two F-CPUs, you must
configure transfer areas in the
hardware and network editor
. The figure below shows how
both of the F-CPUs are able to send and receive data (bidirectional communication).
The transfer area is assigned a label when it is created to identify it as the communication
relationship. For example, "F-CD_PLC_2 PLC_1_1" for the first F-CD connection between IO
controller F-CPU 1 and I-device F-CPU 2.
When you create a transfer area, a system constant with the name of the transfer area is
created in the F-CPU of the IO controller and in the F-CPU of the I-device. The system
constant contains the hardware identifier of the transfer area for the corresponding F-CPU.
You assign the hardware identifier (system constant from the default tag table) of the transfer
areas symbolically to the LADDR input of the SENDDP and RCVDP instructions in the safety
programs.
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
292 Programming and Operating Manual, 10/2018, A5E02714440-AH
Procedure for configuration
The procedure for configuring safety-related IO controller-I-device communication is identical
to that in the standard system.
Proceed as follows:
1. Insert two F-CPUS from the "Hardware catalog" task card into the project.
2. Enable the "IO Device" mode for F-CPU 2 in the properties of its PN interface and assign
this PN interface to a PN interface of F-CPU 1.
3. Select the PROFINET interface of F-CPU 2. Under "Transfer areas", you create an F-CD
connection (type "F-CD") for receiving from the IO controller (←). The F-CD connection is
shown in yellow in the table and the address areas in the I-device and IO controller
assigned are displayed.
In addition, an acknowledgment connection is created automatically for each F-CD
connection. (see "Transfer area details").
4. Create an additional F-CD connection for sending to the IO controller.
5. In the transfer area you just created, click on the arrow to change the transfer direction to
sending to the IO controller (←).
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 293
9.3.4.2
Safety-related IO controller-I-device communication via SENDDP and RCVDP
Communication via SENDDP and RCVDP instructions
Safety-related communication between the F-CPUs of the IO controller and an I-device
makes use of the SENDDP and RCVDP instructions for sending and receiving, respectively.
These can be used to perform a fail-safe transfer of a
fixed
amount of data of the data type
BOOL or INT (DINT as alternative).
You can find these instructions in the "Instructions" task card under "Communication". The
RCVDP instruction
must
be called at the start of the main safety block. The SENDDP
instruction
must
be called at the end of the main safety block.
You can also call up the RCVDP and SENDDP instructions in separate F-FBs/F-FCs which
you have to call at the start or end of the main safety block.
Note that the send signals are not sent until after the SENDDP instruction call at the end of
execution of the relevant F-runtime group.
A detailed description of the SENDDP and RCVDP instructions can be found in SENDDP
and RCVDP: Send and receive data via PROFIBUS DP/PROFINET IO (STEP 7 Safety
V15.1) (Page 588).
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
294 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.3.4.3
Programming safety-related IO controller I-device communication
Requirement for programming
The transfer areas must be configured.
Programming procedure
The procedure for programming safety-related IO controller-I-device communication is the
same as that for programming safety-related IO controller-IO controller communication (see
Program safety-related IO controller-IO controller communication (Page 277)).
The assignment of the HW identifiers (system constants in the standard tag table) of the
transfer areas to the LADDR input of the SENDDP/RCVDP instructions can be obtained from
the following table:
Instruction
HW identifier
SENDDP in the IO controller Hardware identifier of the transfer area in the IO
controller
RCVDP in the IO controller Hardware identifier of the transfer area in the IO
controller
SENDDP in the I-device Hardware identifier of the transfer area in the
I-device
RCVDP in the I-device Hardware identifier of the transfer area in the
I-device
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 295
The figure below contains an example of how to specify the F-communication IDs for the
inputs of the SENDDP and RCVDP instructions for 4 safety-related IO controller-I-device
communication relationships.
WARNING
The value for the respective F-communication ID (input DP_DP_ID; data type: INT) can be
freely selected**; however, it must be unique for all safety-related communication
connections network-wide* and CPU-wide at all times. The uniqueness must be checked in
the safety summary during acceptance of the safety program. You can find additional
information in Correctness and completeness of the communication configuration
(Page 374).
You must supply constant values*** to the inputs DP_DP_ID and LADDR when calling the
instruction. Direct write accesses in the associated instance DB to DP_DP_ID and LADDR
are not permitted in the safety program!
(S016)
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet. In PROFIBUS, a network includes all nodes accessible via PROFIBUS DP. In
PROFINET IO, a network includes all nodes accessible via RT_Class_1/2/3
(Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP (IP, Layer 3).
** S7-1200/1500: As of version V3.0 of the SENDDP and RCVDP instructions, no connection
is established at the DP_DP_ID input for a F-communication ID "0".
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
296 Programming and Operating Manual, 10/2018, A5E02714440-AH
*** S7-1200/1500: As of version V3.0 of the SENDDP and RCVDP instructions, the
DP_DP_ID input can also be supplied with variable values from a global F-DB. In this case
as well you have to check during the acceptance of the safety program that the uniqueness
is ensured
at every moment
, by checking the algorithm for the creation of the variable value
accordingly. If you cannot ensure a unique F-communication ID during startup of the safety
program, because it is only specified after startup of the safety program, you must make sure
that the value at the DP_DP_ID input is "0" during this phase.
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal state to be transferred will
be acquired at the sender end and transferred to the receiver if the signal level is pending
for at least as long as the assigned monitoring time.
(S018)
Information on calculating the monitoring times can be found in Monitoring and response
times (Page 607).
9.3.4.4
Safety-related IO-Controller-IO-Device communication - Limits for data transfer
Limits for data transfer
If the amount of data to be transferred is greater than the capacity of related
SENDDP/RCVDP instructions, you can use additional SENDDP/RCVDP instructions.
Configure additional transfer areas for this purpose. Remember the maximum limit of 1440
bytes of input data or 1440 bytes of output data for transfer between an I-device and a IO
controller.
The following table shows the amount of output and input data assigned in safety-related
communication connections:
Safety-related
communication
Communication
connection
Assigned input and output data
In the IO controller
In the I-device
Output data
Input data
Output data
Input data
IO controller-
I-Device
Sending:
I-Device 1 to IO
controller
6 bytes 12 bytes 12 bytes 6 bytes
Receiving:
I-Device 1 from IO
controller
12 bytes 6 bytes 6 bytes 12 bytes
Consider all additional configured safety-related and standard communication connections
(transfer areas of type F-CD and CD) for the maximum limit of 1440 bytes of input data or
1440 bytes of output data for transfer between an I-device and an IO controller. In addition,
data are assigned for internal purposes such that the maximum limit may be reached sooner.
When the limit is exceeded, a corresponding error message is displayed.
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 297
9.3.5
Safety-related master-I-slave communication
9.3.5.1
Configuring safety-related master-I-slave communication
Introduction
Safety-related communication between the safety program of the F-CPU of a DP master and
the safety program(s) of the F-CPU(s) of one or more I-slaves takes place over master-I-
slave connections (
F-
MS), as in standard systems.
You do not need a DP/DP coupler for master-I-slave communication.
Configuring transfer areas
For every safety-related communication connection between two F-CPUs, you must
configure transfer areas in the
hardware and network editor
. The figure below shows how
both of the F-CPUs are able to send and receive data (bidirectional communication).
The transfer area is assigned a label when it is created to identify it as the communication
relationship. For example, "F-MS_PLC_2-PLC_1_1" for the first F-MS connection between
DP master F-CPU 1 and I-slave F-CPU 2.
When you create a transfer area, a system constant with the name of the transfer area is
created in the F-CPU of the DP master and in the F-CPU of the I-slave. The system constant
contains the hardware identifier of the transfer area for the corresponding F-CPU.
You assign the hardware identifier (system constant from the default tag table) of the transfer
areas symbolically to the LADDR input of the SENDDP and RCVDP instructions in the safety
programs.
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
298 Programming and Operating Manual, 10/2018, A5E02714440-AH
Procedure for configuration
The procedure for configuring safety-related master-I-slave communication is identical to that
in the standard system.
Proceed as follows:
1. Insert two F-CPUS from the "Hardware catalog" task card into the project.
2. If the F-CPU which is to be operated as DP master (F-CPU 1) does not have an
integrated PROFIBUS DP interface, insert an PROFIBUS-CM, for example.
3. From the device view of the F-CPUs which are to be operated as I-slaves (F-CPU 2),
insert a suitable CM DP module or CP DP module.
4. If necessary, enable "DP-slave" (I-slave) mode in the properties for the CM/CP DP
module.
5. Assign the DP interface of the CM/CP to a DP interface of F-CPU 1.
6. Select the PROFIBUS interface of F-CPU 2 or of the CM. Under "Transfer areas", you
create an F-MS connection (type "F-MS") for sending to the DP master (←). The F-MS
connection is shown in yellow in the table and the assigned transfer areas in the I-slave
and DP master are displayed.
In addition, an acknowledgment connection is created automatically for each F-MS
connection. (see "Transfer area details").
7. Create an additional F-MS connection for receiving from the DP master.
8. In the transfer area you just created, click the arrow in order to change the transfer
direction to receiving from DP master (→).
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 299
9.3.5.2
Safety-related master-I-slave communication via SENDDP and RCVDP
Communication via SENDDP and RCVDP instructions
Safety-related communication between the F-CPUs of the DP master and an I-slave makes
use of the SENDDP and RCVDP instructions for sending and receiving, respectively. These
can be used to perform a fail-safe transfer of a
fixed
amount of fail-safe data of the data type
BOOL or INT (DINT as alternative).
You can find these instructions in the "Instructions" task card under "Communication". The
RCVDP instruction
must
be called at the start of the main safety block. The SENDDP
instruction
must
be called at the end of the main safety block.
You can also call the RCVDP and SENDDP instructions in separate F-FBs/F-FCs which you
have to call up at the beginning or end of the main safety block.
Note that the send signals are not sent until after the SENDDP instruction call at the end of
execution of the relevant F-runtime group.
A detailed description of the SENDDP and RCVDP instructions can be found in SENDDP
and RCVDP: Send and receive data via PROFIBUS DP/PROFINET IO (STEP 7 Safety
V15.1) (Page 588).
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
300 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.3.5.3
Programming safety-related master-I-slave communication
Requirements
The transfer areas must be configured.
Programming procedure
The procedure for programming safety-related master-I-slave communication is the same
as that for programming safety-related master-master communication (see Safety-related
master-master communication (Page 281)).
The assignment of the HW identifiers of the transfer areas to the LADDR input of the
SENDDP/RCVDP instructions can be obtained from the following table.
Instruction
HW identifier
SENDDP in the DP master Hardware identifier of the respective transfer area
in the DP master
RCVDP in the DP master Hardware identifier of the respective transfer area
in the DP master
SENDDP in the I-slave Hardware identifier of the transfer area in the
I-slave
RCVDP in the I-slave Hardware identifier of the transfer area in the
I-slave
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 301
The figure below contains an example of how to specify the F-communication IDs at the
inputs of the SENDDP and RCVDP instructions for four safety-related master-I-slave
communication relationships.
WARNING
The value for the respective F-communication ID (input DP_DP_ID; data type: INT) can be
freely selected**; however, it must be unique for all safety-related communication
connections network-wide* and CPU-wide at all times. The uniqueness must be checked in
the safety summary during acceptance of the safety program. You can find additional
information in Correctness and completeness of the communication configuration
(Page 374).
You must supply constant values*** to the inputs DP_DP_ID and LADDR when calling the
instruction. Direct write accesses in the associated instance DB to DP_DP_ID and LADDR
are not permitted in the safety program!
(S016)
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
302 Programming and Operating Manual, 10/2018, A5E02714440-AH
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet. In PROFIBUS, a network includes all nodes accessible via PROFIBUS DP. In
PROFINET IO, a network includes all nodes accessible via RT_Class_1/2/3
(Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP (IP, Layer 3).
** S7-1200/1500: As of version V3.0 of the SENDDP and RCVDP instructions, no connection
is established at the DP_DP_ID input for a F-communication ID "0".
*** S7-1200/1500: As of version V3.0 of the SENDDP and RCVDP instructions, the
DP_DP_ID input can also be supplied with variable values from a global F-DB. In this case
as well you have to check during the acceptance of the safety program that the uniqueness
is ensured
at every moment
, by checking the algorithm for the creation of the variable value
accordingly. If you cannot ensure a unique F-communication ID during startup of the safety
program, because it is only specified after startup of the safety program, you must make sure
that the value at the DP_DP_ID input is "0" during this phase.
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal state to be transferred will
be acquired at the sender end and transferred to the receiver if the signal level is pending
for at least as long as the assigned monitoring time.
(S018)
Information on calculating the monitoring times can be found in Monitoring and response
times (Page 607).
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 303
9.3.5.4
Limits for data transfer of safety-related master-I-slave communication
Limits for data transfer
If the amount of data to be transferred is greater than the capacity of related
SENDDP/RCVDP instructions, you can use additional SENDDP/RCVDP instructions.
Configure additional transfer areas for this purpose. Note the maximum limit of 244 bytes of
input data or 244 bytes of output data for transfer between an I-slave and a DP master.
The following table shows the amount of output and input data assigned in safety-related
communication connections:
Safety-related
communication
Communication
connection
Assigned input and output data
DP master
I-slave
Output data
Input data
Output data
Input data
Master-I-slave
Sending:
I-slave 1 to DP
master
6 bytes 12 bytes 12 bytes 6 bytes
Receiving:
I-slave 1 from DP
master
12 bytes 6 bytes 6 bytes 12 bytes
Consider all additional configured safety-related and standard communication connections
(transfer areas of type F-MS-, F-DX-, F-DX-Mod., MS-, DX- and DX-Mod) for the maximum
limit of 244 bytes of input data or 244 bytes of output data for transfer between an I-device
and a DP master F-MS and MS). If the maximum limit of 244 bytes of input data or 244 bytes
of output data is exceeded, you will receive a corresponding error message.
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
304 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.3.6
Safety-related IO controller-I-slave communication
9.3.6.1
Safety-related IO controller-I-slave communication
Introduction
Safety-related communication between the safety program of the F-CPU of an IO-controller
and the safety program(s) of the F-CPU(s) of one or more I-slaves takes place over master-I-
slave connections (
F-
MS), as in standard systems.
IE/PB link
For the safety-related IO-controller-I-slave communication, the IE/PB link is mandatory. Each
of the two F-CPUs is linked to the IE/PB link by means of its PROFIBUS DP or PROFINET-
interface.
Note
If you are using an IE/PB link, you must take this into account when configuring the
F
-specific monitoring times and when calculating the maximum response time of your
F
-system (see also Monitoring and response times (Page 607)).
Note that the Excel file for calculating response times
(
http://support.automation.siemens.com/WW/view/en/49368678/133100) for S7-300/400
F
-CPUs does not support all conceivable configurations.
Reference
The information on safety-related master-I-slave communication in Safety-related master-I-
slave communication (Page 297) also applies.
9.3.7
Safety-related communication to S7 F-System S7 Distributed Safety
9.3.7.1
Introduction
Safety-related communication from F-CPUs in SIMATIC Safety to F-CPUs in S7 Distributed
Safety F-systems is possible, via a PN/PN coupler or DP/DP coupler that you use between
the two F-CPUs, as IO controller-IO controller communication or master-master
communication.
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 305
9.3.7.2
Communication with S7 Distributed Safety via PN/PN coupler
(IO controller-IO controller communication)
Communication functions between SENDDP/RCVDP instructions at the
STEP 7 Safety
end
and F-application blocks F_SENDDP/F_RCVDP at the
S7 Distributed Safety
end:
Procedure at the
S7 Distributed Safety
end
At the
S7 Distributed Safety
end, proceed as described in "Safety-related IO controller-IO
controller communication" in the S7 Distributed Safety - Configuring and Programming
(http://support.automation.siemens.com/WW/view/en/22099875) manual.
Procedure at the
STEP 7 Safety
end
At the
STEP 7 Safety
end, proceed as described in Safety-related IO controller-IO controller
communication (Page 272).
Safety-related communication
9.3 Configuring and programming communication (S7-1200, S7-1500)
SIMATIC Safety - Configuring and Programming
306 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.3.7.3
Communication with S7 Distributed Safety via DP/DP coupler
(master-master communication)
Communication functions between SENDDP/RCVDP instructions at the
STEP 7 Safety
end
and F-application blocks F_SENDDP/F_RCVDP at the
S7 Distributed Safety
end:
Procedure at the
S7 Distributed Safety
end
At the
S7 Distributed Safety
end, proceed as described in "Safety-related master-master
communication" in the S7 Distributed Safety - Configuring and Programming
(http://support.automation.siemens.com/WW/view/en/22099875) manual.
Procedure at the
STEP 7 Safety
end
At the
STEP 7 Safety
end, proceed as described in Safety-related master-master
communication (Page 281).
Safety-related communication
9.4 Configuring and programming communication between S7-300/400 and S7-1200/1500 F-CPUs
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 307
9.4
Configuring and programming communication between S7-300/400
and S7-1200/1500 F-CPUs
9.4.1
Overview of communication
Introduction
This section provides an overview of the options for safety-related communication between
S7-300/400 and S7-1200/1500 F-CPUs in SIMATIC Safety F-systems.
Options for safety-related communication
Safety-related communication
On subnet
Additional hardware required
Safety-related CPU-CPU communication:
Master-master communication PROFIBUS DP DP/DP coupler
Master-I-slave communication
PROFIBUS DP
IO controller-IO controller communica-
tion
PROFINET IO PN/PN coupler
IO controller-I-device communication
PROFINET IO
IO controller-I-slave communication PROFINET IO and
PROFIBUS DP
IE/PB link
Basic procedure for configuring and programming
Configure and program safety-related communication between S7-300/400 F-CPUs and
S7-1200/1500 F-CPUs as described in Configuring and programming communication
(S7-300, S7-400) (Page 201) and Configuring and programming communication
(S7-1200, S7-1500) (Page 270) for your application.
To program an S7-300/400 F-CPU, use the start addresses of the transfer areas. To
program an S7-1200/1500 F-CPU, use the HW identifiers of the transfer areas.
Safety-related communication
9.5 Configuring and programming communication in several projects
SIMATIC Safety - Configuring and Programming
308 Programming and Operating Manual, 10/2018, A5E02714440-AH
9.5
Configuring and programming communication in several projects
9.5.1
Safety-oriented IO Controller I device communication in several projects
9.5.1.1
Configuring safety-related communication between IO controller and I-device
Introduction
Safety-related communication between the safety program of the F-CPU of an IO controller
and the safety program(s) of the F-CPU(s) of one or more I-devices takes place via IO
controller-I-device connections (F
-
CD) in PROFINET IO, in the same way as in standard
systems.
The following section describes particular aspects when the IO Controller and the I-device
are located in different projects.
Requirement
The IO Controller is an S7-1200/1500 F-CPU that supports the IO Controller functionality.
The I-device is an S7-300/400/1200/1500 F-CPU that supports the I-device functionality.
The project in which the I-device is located, must have been created with
S7 Distributed
Safety V5.4
,
STEP 7 Safety V13
or later.
Configuring
1. Configure the safety-related communication in the project with the I-device as described
under "Configuring safety-related communication between IO controller and I-device
(Page 223)" (S7-300/S7-400) or "Configuring safety-related communication between IO
controller and I-device (Page 290)" (S7-1200/S7-1500) respectively. In this case the F-
CPU 1 (IO Controller) is only a placeholder for the F-CPU in the project of the IO
Controller.
Note
When creating with
STEP 7 Safety
< V14 SP1 avoid a subsequent change from the
transfer areas from CD to F
-CD.
When creating with
S7 Distributed Safety
V5.4
create the application transfer areas
of the
address type "Output" and "Input" directly after each other.
2. Export the I-device as a GSD file. Proceed as described in the
STEP 7
help under
"Configuring an I-device".
3. Import the GSD file in the project with the IO Controller. Proceed as described in the
STEP 7
help under "Installing a GSD file".
Safety-related communication
9.5 Configuring and programming communication in several projects
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 309
4. Insert the I-device from the "Hardware catalog" task card into the project with the IO
Controller.
5. Assign the F-CPU of the IO Controller to the I-device.
9.5.1.2
Programming safety-related IO Controller I-device communication
Programming procedure
To program the safety-related communication between the IO controller and I-device for an
F-CPU S7-300/400, analogously follow the procedure described under "Safety-related IO
controller-I-device communication via SENDDP and RCVDP (Page 226)" and "Programming
safety-related IO controller I-device communication (Page 227)". To program an S7-300/400
F-CPU, use the start addresses of the transfer areas.
To program the safety-related communication between the IO controller and I-device for an
F-CPU S7-1200/1500, analogously follow the procedure described under "Safety-related IO
controller-I-device communication via SENDDP and RCVDP (Page 293)" and "Programming
safety-related IO controller I-device communication (Page 294)". To program an S7-
1200/1500 F-CPU, use the HW identifiers of the transfer areas.
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 311
Compiling and commissioning a safety program
10
10.1
Compiling the safety program
To compile a safety program, follow the same basic procedure as for compiling a standard
user program. You can start at various points to accomplish this in
STEP 7
. The basics for
compiling user programs can be found in the
Help on STEP 7
.
Note
Please note that following a safety
-related change t
o the hardware configuration that not only
this, but also the safety program has to be recompiled and downloaded. This also applies for
changes to the F
-I/O which are not used in the safety program.
Note
The safety program is not compiled consistently with the menu command "Edit > Compile" or
the "Compile" icon under the following conditions:
When you select a user-created folder in the project tree.
When you select one or more (F-)blocks in the "Program blocks" folder in the project tree.
Use this proc
edure to test if modified F-blocks can be compiled.
Note
The following applies for S7
-300/400 F-CPUs:
If you want to compile a know
-how-protected F-block after a change, you must remove the
know
-how protection for this F-block before compiling.
Reporting compiling errors
You can recognize whether or not the compilation was successful based on the message in
the inspector window under "Info > Compile", error messages and warnings are output.
For information on the procedure you must follow to eliminate compiling errors, see
"Eliminating compiling errors" in the
Help on STEP 7
.
See also
Safety Administration Editor (Page 81)
Compiling and commissioning a safety program
10.2 Safety program work memory requirements (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
312 Programming and Operating Manual, 10/2018, A5E02714440-AH
10.2
Safety program work memory requirements (S7-300, S7-400)
Estimation
You can estimate the work memory requirement for the safety program as follows:
Work memory required for the safety program
32 KB for F-system blocks
+
4.4 KB for safety
-related communication between F-runtime groups
+
4.5 x work memory requirement for all F-FB/F-FCs/main safety blocks
+
4.5 x work memory requirement of all utilized
instructions, which are shown in the
"I
nstructions" task card with the block icon.
(except SENDDP, RCVDP, SENDS7, and RCVS7)
+
Work memory requirement of the util
ized SENDDP and RCVDP instructions
(4.3 KB each)
+
Work memory requirement of the utilized SENDS7 and RCVS7 instructions
(8.5 KB each)
Work memory required for data
5 x work memory requirement for all F
-DBs (including F-communication DB, but excluding
DB for F-runtime group communication) and I-DBs for main safety block/F-FB
+
24 x work memory requirement for all DBs for F-runtime group communication
+
2.3 x work memory requirement for all I
-DBs of instructions (except SENDDP, RCVDP,
SENDS7 and RCVS7)
+
Work memory requirement of all I
-DBs of instructions SENDDP (0.2 KB), RCVDP
(0.3 KB), SENDS7 (0.6 KB), and RCVS7 (1.0 KB)
+
0.7 KB per F-FC
+
0.7 KB per F-I/O (for F-I/O DBs, etc.)
+
4.5 KB
Block size of automatically generated F-blocks
Do not utilize the entire maximum size of an F-block, because the automatically generated
F-blocks are larger and as a result, the maximum possible size may be exceeded in the
F-CPU. If the block size is exceeded, this triggers a corresponding error message with
information on which F-blocks are too large. These must be divided up, if necessary.
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 313
10.3
Downloading project data
10.3.1
Downloading project data to an F-CPU
Introduction
Once you have successfully compiled your safety program, you can download it to the
F-CPU. To download a safety program, you follow essentially the same approach as for
downloading a standard user program, via different starting points in
STEP 7
.
In the "Load preview" dialog, enter data (e.g. password for the F-CPU) and set the
requirements for downloading (e.g. that the F-CPU is switched to STOP mode before
downloading).
The "Load results" dialog shows the results after downloading.
We will show you the options for downloading the safety program later. For basic information
on downloading, refer to the
Help on STEP 7
.
Rules for downloading the safety program to an F-CPU
WARNING
If
multiple F-CPUs
can be reached over a network (e.g. Industrial Ethernet) by
one
programming device or PC
, you must take the following actions to ensure that the project
data is downloaded to the correct F-CPU:
Use passwords specific to each F-CPU, such as a uniform password for the F-CPUs with
attached Ethernet address for each.
Note the following:
A point-to-point connection must be used to activate the access protection of an F-CPU
when the hardware configuration is loaded for the first time (similar to assigning an MPI
address to an F-CPU for the first time).
Before downloading the safety program to an F-CPU, you must first revoke an existing
access permission for any other F-CPU.
The last download of the safety program prior to switching to productive operation must
be made with enabled access protection.
(S021)
Note
You can perform the downloading of a consistent safety program only in STOP mode.
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
314 Programming and Operating Manual, 10/2018, A5E02714440-AH
Note
If
STEP 7 Safety
detects an inconsistent safety program during startup of the F-CPU, the
F
-CPU cannot be started, provided the F-CPU supports this detection function (see product
information for the particular S7
-300/400 F-CPU). This is always supported with S7-
1200/1500 F
-CPUs). A corresponding diagnostics event is entered in the diagnostics buffer
of the F
-CPU.
If the F
-CPU does not support this detection function, the F-
CPU can go to STOP mode if an
inconsistent safety program is executed in activated safety mode.
The cause of the diagnostics event is entered in the diagnostics buffer of the F
-CPU.
When downloading the safety program, ensure that the "Consistent download" action is set
for the "Safety program" selection in the "Load preview" dialog.
Inconsistent downloading is only possible in disabled safety mode.
Password prompt before downloading to an F-CPU
If you have assigned a protection level for the F-CPU (Page 106) (in the properties of the
F-CPU in the "Protection" tab), the corresponding password is prompted in "Load preview"
dialog. Without entry of password, only actions that are allowed without password are
possible. As soon as the conditions for downloading are met, the "Load" button becomes
active.
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 315
"Load preview" dialog
For an F-CPU, the "Load preview" dialog also contains the section "Safety program".
Make the following selection:
In order to download a consistent safety program, select the "Consistent download"
action under target "Safety program".
(S7-300, S7-400) To download individual F-blocks selectively (Page 318), select the
"Download selection" action under the target "Safety program", and then select the
required F-blocks. If necessary, you will be prompted to disable safety mode under
"Disable safety mode". This setting is only suitable for the online test of individual F-
blocks.
(S7-300, S7-400) In order to download the safety program only, select the "Consistent
download" action under target "Safety program" and the "Download selection" action
under target" Standard software", and then select only the standard blocks that call the
main safety block.
(S7-300, S7-400) To download no safety program, for example, because you do not know
the password of the F-CPU, select the "No action" action under target "Safety program".
For S7-1200/1500 F-CPUs, only the "Consistent download" value is possible as an action in
the "Load preview" dialog. It is not possible to select separate loading of standard program
or safety program. The complete user program is automatically consistently downloaded as
soon as changes have been made in both the standard program and in the safety program.
Refer also to the section entitled Data exchange between standard user program and safety
program (Page 195).
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
316 Programming and Operating Manual, 10/2018, A5E02714440-AH
"Load results" Dialog
After downloading into the F-CPU, the dialog "Load results" is opened. This dialog shows
you the status and the necessary actions after downloading.
Verify that the "Downloading of safety program completed without errors." message appears
in the "Load results" dialog. If not, repeat the download operation.
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 317
10.3.1.1
Downloading project data to an S7-300/400 F-CPU with memory card inserted
(SIMATIC Micro memory card or flash card)
When you download project data to an S7-300/400 F-CPU with memory card inserted
(SIMATIC Micro memory card for S7-300 or flash card for S7-400), you must observe the
following warning:
WARNING
If the function test of the safety program is not carried out in the destination F-CPU, you
must adhere to the following procedure when downloading the safety program to the
F-CPU with a
programming device/PC
to ensure that the F-CPU does not contain an "old"
safety program:
Download the safety program to the F-CPU.
Perform a program identification (i.e. check whether the collective F-signatures match
online and offline).
Perform a memory reset of the F-CPU using the mode switch or via the programming
device/PC. Once the work memory has been deleted, the safety program is again
transferred from the load memory (memory card, SIMATIC Micro memory card for S7-
300 F-CPUs,flash card for S7-400 F-CPUs) to the work memory.
(S022)
10.3.1.2
Downloading project data to an S7-400 F-CPU without flash card inserted
When you download project data to an S7-400 F-CPU without flash card inserted, you must
observe the following warning:
WARNING
If the function test of the safety program is not carried out in the destination F-CPU, you
must adhere to the following procedure when downloading the safety program to the
F-CPU with a
programming device/PC
to ensure that the F-CPU does not contain an "old"
safety program:
Perform a memory reset of the F-CPU using the
mode switch
or via the
programming
device/PC
.
Download the configuration and the safety program to the F-CPU.
Perform a program identification (i.e. check whether the collective F-signatures match
online and offline).
(S023)
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
318 Programming and Operating Manual, 10/2018, A5E02714440-AH
10.3.1.3
Downloading project data to a WinAC RTX F
When you download project data to a WinAC RTX F, you must observe the following
warning:
WARNING
You must adhere to the following procedure when downloading the safety program to the
WinAC RTX F with a programming device/PC to ensure that the WinAC RTX F does not
contain an "old" safety program:
1. Perform a memory reset of the WinAC RTX F (see Windows Automation Center RTX
WinAC RTX (F) 2010 (http://support.automation.siemens.com/WW/view/en/43715176)
manual).
2. Download the project data (Page 313) to the WinAC RTX F.
If the function test of the safety program does not take place in the destination WinAC
RTX F, you must also follow points 3. and 4:
3. Perform a program identification. This means you check whether the collective
F-signatures match online and offline.
4. Perform the F-system startup.
Between the online program identification and the startup of the F-system, the
WinAC RTX F must not be closed (for example, as a result of POWER OFF/POWER ON or
booting).
(S024)
10.3.1.4
Downloading individual F-blocks to an S7-300/400 F-CPU
Download F-blocks in disabled safety mode.
You can download F-blocks and standard blocks simultaneously to the F-CPU via the project
tree. However, as soon as F-blocks are to be downloaded, a check is carried out to
determine whether or not the F-CPU is in STOP mode or disabled safety mode. If not, you
have the option of switching to disabled safety mode or placing the F-CPU in STOP mode.
If you want to download individual F-blocks to the F-CPU, for example, to test changes,
make sure that you have not selected the folder "Program blocks" or the F-CPU in the
project tree but only the blocks you want to download.
Only then will you be prompted in the "Load preview" dialog to disable safety mode once you
have changed the option from "Consistent download" to "Download selection” and have
changed the option “Stop modules” to “No action”.
If you fail to observe this prompt, the blocks are downloaded without deactivation of the
safety mode which will STOP the F-CPU.
You can also deactivate the safety mode explicitly in the
Safety Administration Editor
before
you start the download.
Be aware that the consistency of the safety program in the F-CPU cannot be guaranteed
when individual F-blocks are downloaded. For a consistent safety program, always download
the entire safety program to the F-CPU.
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 319
Rules for downloading individual F-blocks
The following rules apply to downloading of individual F-blocks:
Downloading is only possible in disabled safety mode or when the F-CPU is in STOP
mode.
F-blocks can only be downloaded to an F-CPU to which a safety program has already
been downloaded.
Only an offline safety program is permitted to be used as a source program.
Consequently, you have to download the entire safety program when initially downloading
the safety program and after changing the password for the safety program.
Note
If you are downloading F
-blocks only, the blocks in which the main safety blocks are called
(e.g., cyclic int
errupt OB 35) are not downloaded. To do so, select the "Selection" option
under "Standard software" in the preview dialog, and select the necessary blocks.
Note
Downloading of individual F
-blocks is only suitable for testing F-blocks. Prior to the transition
to productive mode, you must download the safety program consistently to the F
-CPU.
10.3.1.5
Downloading project data to an S7-1200 F-CPU without program card inserted
When you download project data to an S7-1200 F-CPU without program card inserted, you
must observe the following warning:
WARNING
If the function test of the safety program is not carried out in the destination F-CPU, you
must adhere to the following procedure when downloading the safety program to the
F-CPU with a
programming device/PC
to ensure that the F-CPU does not contain an "old"
safety program:
Download the safety program to the F-CPU.
Perform a program identification (i.e. check whether the collective F-signatures match
online and offline).
(S042)
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
320 Programming and Operating Manual, 10/2018, A5E02714440-AH
10.3.1.6
Downloading project data to an S7-1200 F-CPU with program card inserted
When you download project data to an S7-1200 F-CPU with program card inserted, you
must observe the following warning:
WARNING
You must observe the following procedure to ensure that there is no "old" safety program in
the internal load memory of the F-CPU when you insert a program card into an S7-1200
F-CPU:
1. Check to see whether
the STOP/RUN LED (orange) and the maintenance LED flash
during startup for 3 seconds on an F-CPU without memory card
.
If this is the case, the internal load memory of the F-CPU has already been deleted (for
example, when the F-CPU has already been operated with a program card as external
load memory) and you can skip step 3.
2. Insert the program card into the F-CPU.
If the F-CPU is in RUN, it will change to STOP. The maintenance LED on the F-CPU is
flashing to indicate that the program card is being evaluated or that the internal load
memory must be deleted.
3. Use one of the following methods to delete the internal load memory:
Turn the F-CPU off and back on.
Switch the F-CPU from STOP to RUN.
Execute the "Memory reset" (MRES) function.
After restart and deletion of the internal load memory,
the STOP/RUN LED (orange) and
the maintenance LED must be flashing
. The internal load memory of the F-CPU has
been deleted in this case and does no longer store an "old" safety program.
4. Use one of the following methods to evaluate the program card:
Turn the F-CPU off and back on.
Switch the F-CPU from STOP to RUN.
Execute the "Memory reset" (MRES) function.
The F-CPU restarts and evaluates the program card.
The F-CPU then enters the startup mode (RUN or STOP) that has been set up for the
F-CPU.
(S061)
For an S7-1200 F-CPU without inserted SIMATIC Memory Card and deleted internal load
memory, the status LEDs have the status described in the table below.
Description
STOP/RUN Or-
ange/Green
ERROR Red
MAINT Orange
Internal load memory
deleted and SIMATIC
Memory Card
not
in-
serted.
Flashing (orange)
(for 3 seconds during
startup)
Off Flashing
(for 3 seconds during
startup)
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 321
WARNING
If you use a programming device/PC to download F-blocks to an S7-1200 F-CPU with
inserted program card (external load memory), you must ensure that the transfer takes
place to the external load memory. This can be accomplished by the following measures:
Check to see if the program card is inserted correctly.
Insert a program card whose memory size is different than the size of the internal load
memory. Check in the project tree under "Online & Diagnostics > Diagnostics >
Memory" if the memory size displayed for the load memory matches the memory size of
the program card.
(S058)
WARNING
If the function test of the safety program is not carried out in the destination F-CPU, you
must adhere to the following procedure when downloading the safety program to the
F-CPU with a
programming device/PC
to ensure that the F-CPU does not contain an "old"
safety program:
Download the safety program to the F-CPU.
Perform a program identification (i.e. check whether the collective F-signatures match
online and offline).
(S042)
10.3.1.7
Downloading project data to an S7-1500 F-CPU
When you download project data to an S7-1500 F-CPU, you must observe the following
warning:
WARNING
If the function test of the safety program is not carried out in the destination F-CPU, you
must adhere to the following procedure when downloading the safety program to the
F-CPU with a
programming device/PC
to ensure that the F-CPU does not contain an "old"
safety program:
Download the safety program to the F-CPU.
Perform a program identification (i.e. check whether the collective F-signatures match
online and offline).
(S042)
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
322 Programming and Operating Manual, 10/2018, A5E02714440-AH
10.3.1.8
Downloading project data to an S7-1500 F Software Controller
When you download project data to an S7-1500 F Software Controller, you must observe the
following warnings:
WARNING
If the function test of the safety program is not carried out in the destination F-CPU, you
must adhere to the following procedure when downloading the safety program to the
F-CPU with a
programming device/PC
to ensure that the F-CPU does not contain an "old"
safety program:
Download the safety program to the F-CPU.
Perform a program identification (i.e. check whether the collective F-signatures match
online and offline).
(S042)
WARNING
For security reasons, the password of an S7-1500 F Software Controller is also stored in a
separate memory in addition to the load memory.
Unlike the load memory, this separate memory is not deleted. This means the previous
passwords are once again active after deleting the S7-1500 F Software Controller followed
by a run-up.
For this reason, note the following:
The S7-1500 F Software Controller is deleted in case of the following download
scenarios of the PC station:
Downloading a PC station with revised interface assignment.
Downloading a PC station with revised storage location for retentive data.
We recommend that you do not set up F-access protection until after commissioning. If
you still have to change the interface assignment of the PC station or the storage
location for retentive data, you do not have to enter the F-password during the
subsequent mandatory download of the S7-1500 F Software Controller.
We recommend that you remove the F-access protection from an S7-1500 F Software
Controller that is no longer in use. If you forget the F-password when you want to
operate the S7-1500 F Software Controller later, you can remove it by
uninstalling/installing or loading a new image.
(S076)
See also
Downloading project data to an F-CPU (Page 313)
Software Controller (http://support.automation.siemens.com/WW/view/en/109249299)
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 323
10.3.2
Downloading project data to a memory card and inserting a memory card
Proceed as you would with standard blocks to download project data from an F-CPU to a
memory card (flash card for S7-400, SIMATIC Micro Memory Card for S7-300 or SIMATIC
Memory Card for S7-1200/1500). You must also observe the following warning:
WARNING
If the function test of the project data is not performed in the destination F-CPU, you must
ensure that the correct project data are on the memory card after downloading the project
data to the memory card.
Follow these steps:
1. Make sure that you are using an empty memory card.
2. Download the project data to the memory card.
3. If necessary, clearly label the memory card (e.g. with the collective F-signature).
The procedure outlined must be ensured through organizational measures.
(S043)
When inserting a memory card (flash card for S7-400, SIMATIC Micro Memory Card for
S7-300 or SIMATIC Memory Card for S7-1200/1500) with project data from an F-CPU, you
observe the following warning:
WARNING
If the function test of the safety program is not performed in the destination F-CPU, you
must ensure through online program identification or other suitable measures (e.g. by
checking the labeling of the memory card) that the memory card inserted has the correct
safety program.
(S025)
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
324 Programming and Operating Manual, 10/2018, A5E02714440-AH
10.3.2.1
Inserting a SIMATIC Micro Memory Card or flash card into an S7-300/400 F-CPU
When you insert a memory card (flash card for S7-400 or SIMATIC Micro memory card for
S7-300) into an S7-300/400 F-CPU , you must observe the following warning:
WARNING
If the function test of the safety program is not performed in the destination F-CPU, you
must adhere to the following procedure when inserting the memory card to ensure that the
F-CPU does not contain an "old" safety program:
Switch off the power to the F-CPU. For F-CPUs with battery backup (e.g. CPU 416F-2),
remove any battery. (To ensure that the F-CPU is de-energized, wait for the buffer time
of the power supply you are using or, if this is not known, remove the F-CPU.)
Remove the memory card with the old safety program from the F-CPU.
Insert the memory card with the new safety program into the F-CPU.
Switch on the F-CPU again. For F-CPUs with battery backup (e.g. CPU 416F-2),
reinsert the battery, if one was removed.
(S026)
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 325
10.3.2.2
Inserting a transfer card into an S7-1200 F-CPU
When you insert a transfer card into an S7-1200 F-CPU, you must observe the following
warning:
WARNING
You must observe the following procedure to ensure that there is no "old" safety program in
the internal load memory when you copy the project data to an S7-1200 F-CPU using a
transfer card:
1. Check to see whether
the STOP/RUN LED (orange) and the maintenance LED flash
during startup for 3 seconds on an F-CPU without memory card
.
If this is the case, the internal load memory of the F-CPU has already been deleted and
you can skip step 3.
2. Insert the transfer card into the F-CPU.
If the F-CPU is in RUN, it will change to STOP. The maintenance LED on the F-CPU is
flashing to indicate that the transfer card is being evaluated or that the internal load
memory must be deleted.
3. Use one of the following methods to delete the internal load memory:
Turn the F-CPU off and back on.
Switch the F-CPU from STOP to RUN.
Execute the "Memory reset" (MRES) function.
After restart and deletion of the internal load memory,
the STOP/RUN LED (orange)
and the maintenance LED must be flashing
. The internal load memory of the F-CPU
has been deleted in this case and does no longer store an "old" safety program.
4. Use one of the following methods to evaluate the transfer card (transfer from the
transfer card to the internal load memory):
Turn the F-CPU off and back on.
Switch the F-CPU from STOP to RUN.
Execute the "Memory reset" (MRES) function.
After restart and evaluation of the SIMATIC Memory Card, the F-CPU copies the project
data to the internal load memory of the F-CPU. Once the copy process is complete, the
maintenance LED on the F-CPU is flashing to indicate that you can remove the transfer
card.
5. Remove the transfer card from the F-CPU.
6. Use one of the following methods to evaluate the internal load memory:
Turn the F-CPU off and back on.
Switch the F-CPU from STOP to RUN.
Execute the "Memory reset" (MRES) function.
The F-CPU then enters the startup mode (RUN or STOP) that has been set up for the
F-CPU.
(S059)
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
326 Programming and Operating Manual, 10/2018, A5E02714440-AH
For an S7-1200 F-CPU without inserted SIMATIC Memory Card and deleted internal load
memory, the status LEDs have the status described in the table below.
Description
STOP/RUN
Orange/Green
ERROR Red
MAINT Orange
Internal load memory
deleted and SIMATIC
Memory Card
not
in-
serted.
Flashing (orange)
(for 3 seconds during
startup)
Off Flashing
(for 3 seconds during
startup)
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 327
10.3.3
Downloading project data of an S7-1200 F-CPU from the internal load memory
to an empty SIMATIC Memory Card
When you download project data from the internal load memory of an S7-1200 F-CPU to an
empty SIMATIC Memory Card, you must observe the following warning:
WARNING
To ensure that the safety program is downloaded from the internal load memory of the F-
CPU to the SIMATIC Memory Card when plugging an empty SIMATIC Memory Card into
an S7-1200 F-CPU and that the internal load memory of the F-CPU is deleted afterward,
you must observe the following procedure:
1. Make sure that you are using an empty SIMATIC Memory Card, for example, by
checking in the Windows Explorer that the "SIMATIC.S7S" folder and the "S7_JOB.S7S"
file are deleted.
2. Insert the empty SIMATIC Memory Card into the F-CPU.
If the F-CPU is in RUN, it will change to STOP. The maintenance LED on the F-CPU is
flashing to indicate that the program can be copied from the internal load memory to the
SIMATIC Memory Card and that the internal load memory is deleted afterward.
3. Use one of these methods to trigger copying from the internal load memory to the
SIMATIC Memory Card and subsequent deletion of the internal load memory:
Turn the F-CPU off and back on.
Switch the F-CPU from STOP to RUN.
Execute the "Memory reset" (MRES) function.
After restart and copying of the program from the internal load memory to the SIMATIC
Memory Card and subsequent deletion of the internal load memory,
the STOP/RUN
LED (orange) and the maintenance LED must be flashing
. The internal load memory of
the F-CPU has been deleted in this case and does no longer store the safety program.
The SIMATIC Memory Card is now a program card.
4. Use one of the following methods to evaluate the program card:
Turn the F-CPU off and back on.
Switch the F-CPU from STOP to RUN.
Execute the "Memory reset" (MRES) function.
The F-CPU restarts and evaluates the program card.
The F-CPU then enters the startup mode (RUN or STOP) that has been set up for the
F-CPU.
(S057)
Note
A
lso observe the setting "Disable copying from internal load memory to external load
memory" in the hardware configuration of your F
-CPU.
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
328 Programming and Operating Manual, 10/2018, A5E02714440-AH
10.3.4
Updating project data on an S7-1200 F-CPU using a transfer card
When you want to update the project data on an S7-1200 F-CPU using a transfer card, you
must observe the following warning:
WARNING
If you run an update of the safety program on an S7-1200 F-CPU with the help of a transfer
card, you must ensure that the transfer to the internal load memory took place correctly by
means of a subsequent program identification.
(S060)
10.3.5
Restoring a backup of the safety program to an S7-300/1200/1500 F-CPU
You have the option of backing up an F-CPU in the same way as a standard CPU and then
restoring it. You can find information on backing up a CPU in the
help on STEP 7
under
"Creating a backup of an S7-CPU".
Note the following warnings when restoring the software and hardware configuration of an
F-CPU:
WARNING
Once you have restored a backup of an F-CPU, you must perform a program identification.
(S055)
Note
We recommend that you use the collective F
-signature that is included in the name of the
backup file for program identification. You must not change the collective F
-signature in the
name in this case.
WARNING
(S7-1200/1500) If multiple F-CPUs with Web server can be reached by a programming
device or PC, you must take additional actions to ensure that the safety program is
downloaded to the correct F-CPU by restoring it.
Use CPU-specific passwords for the "F-Admin" right on the Web server. For example,
select a uniform password with attached IP address (e.g. Password_192.168.0.8) for each
F-CPU.
(S065)
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 329
10.3.6
Special features when creating and importing images of an S7-1500 F Software
Controller
Creating an image
WARNING
You must comply with the following points when creating an image with a safety program:
You must limit access to an S7-1500 F Software Controller through access protection to
persons who are authorized to create images.
Before creating the image, you must use program identification to ensure that the
correct safety program is installed on the S7-1500 F Software Controller.
Images with safety programs must be created on an empty data carrier (deleted or
formatted) or an existing image must be explicitly deleted.
After creating the image, remove the data carrier containing the image.
Clearly label the data storage medium (e.g. with the collective F-signature).
(S073)
NOTICE
If the safety program in the image and the old safety program on the S7-1500 F Software
Controller are not identical, the imported safety program would not start. In this case, you
must download the safety program to the F-CPU once again. For example, with the TIA
Portal. Therefore, you should always keep your image backups up-to-date.
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
330 Programming and Operating Manual, 10/2018, A5E02714440-AH
Import image
WARNING
You must comply with the following points when importing an image with a safety program:
You must limit access to an S7-1500 F Software Controller through access protection to
persons who are authorized to import images.
When importing an image via LAN, remote access or comparable accesses, you have to
ensure access protection (e.g. via Windows administrator permission (ADMIN)). Note,
however, that only authorized persons are set up as users.
To ensure that the images are written to the correct S7-1500 F software controller, when
importing an image via LAN you must ensure that only one S7-1500 F software
controller can be accessed. For example, by removing the physical connections and
routing options to other S7-1500 F software controllers.
You must ensure that the correct safety program is on the image, for example, through
unique identification of the data storage medium.
After importing the image, remove the image and copies thereof.
After importing the image, you must use program identification to ensure, for example
with the Panel, that the correct safety program is installed on the S7-1500 F software
controller.
(S074)
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 331
10.3.7
Loading project data from an F-CPU to a programming device / PC
Loading the user program (including safety program) to a programming device / PC (S7-300, S7-400)
To upload a user program (including safety program) to a programming device / PC, proceed
as with a standard program, "Online > Upload from device (software)" or "Online > Upload
device as new station (hardware and software)"
You can only upload the hardware configuration if F-capability is not enabled for the F-CPU.
You can only upload F-I/Os if these are operated in standard mode.
Note
In principle, it is possible to upload a safety program from the F
-CPU to a programming
device or PC. Note, however,
that any symbols used in the safety program are deleted and
cannot be recreated, since no symbol information is saved in the F
-CPU. Symbols are
available only if you are using an offline project.
A safety program uploaded from the F
-CPU to a programming device / PC may not be
loaded again into the F
-CPU.
Loading the project data (including safety-related project data) into a programming device / PC
(S7-1500)
The "Upload from device (software)" or "Upload device as new station (hardware and
software)" function is only possible for S7-1500 F-CPUs if the "Enable consistent upload
from the F-CPU" option is activated for the F-CPU in the
Safety Administration Editor
and the
project data are loaded to the F-CPU afterwards.
To load the project data (including safety-related project data) to a programming device or
PC, proceed as for standard blocks.
If multiple F-CPUs can be reached over a network (e.g. Industrial Ethernet) by the
programming device / PC, you have to ensure that the project data are downloaded from the
correct F-CPU. For example with "Online & diagnostics" > "Online accesses " > "Flash LED".
After successful loading from the device you can continue working as with a project that was
created offline.
WARNING
If you want to carry out an acceptance with the project data upload to the programming
device / PC or want to carry out changes to the safety-related project data and the F-CPU
is in STOP mode, you have set to programming device / PC to RUN before uploading. This
way, you can ensure that the safety program is executable. If the F-CPU remains in STOP,
you are not allowed to perform acceptance or changes with the safety-related project data.
(S080)
You can load individual F-blocks into a programming device / PC irrespective of the "Enable
consistent upload from the F-CPU" option.
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
332 Programming and Operating Manual, 10/2018, A5E02714440-AH
You cannot upload individual know-how protected F-blocks to a programming device / PC.
Note
The offline password is replaced or deleted
by the online password of the safety program.
See also
"Settings" area (Page 90)
10.3.8
Loading PC station via the configuration file
You have the option to save the system configuration of the PC system in a configuration
file, transport it and load it to a target system. The entire configuration of your PC station is
saved in a configuration file with the ending *.psc from the TIA Portal.
Saving and loading of the configuration file is supported as of:
STEP 7 Safety V15
S7-1500 F Software Controller V2.5
Example
You can find a detailed example on the Internet
(https://support.industry.siemens.com/cs/ww/en/view/109759142).
Identification parameters
The identification parameters include:
File name
Information in the project and the station that was stored from the TIA Portal in the PSC
file in the metadata.
For example:
Project version
Plant designation
Station comment
Save the identification parameters in a file, if necessary, that you store on the target system.
For evaluating and testing these identification parameters via script, you must store this
information directly in the script or save the identification parameters in a separate file, if
necessary, that you store on the target system.
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 333
10.3.8.1
Creating a configuration file
1. In the TIA Portal create a new configuration file with "Project > Memory Card file > New >
PC system configuration file (.psc)".
The configuration file is created in the project tree under "Card Reader/USB memory".
2. Use the collective F-signature to check in the SAE that you have selected the correct
project/station.
3. Use your mouse to drag the selected PC station to the configuration file.
This loads the PC station to the configuration file.
WARNING
Instead of online program identification, you can use a unique name for the configuration
file *.psc (
P
C
S
tation
C
onfiguration) to ensure that the correct security program is located in
the configuration file.
In addition, you have to observe the following when creating a configuration file:
On creation of a configuration file with the security program, an existing file may not be
used. You have to create a new file.
You should also remove configuration files with a faulty security program from data storage.
You must limit access to the configuration file (*.psc) through access protection to persons
who are authorized to import and modify the configuration file.
(S081)
10.3.8.2
Importing the configuration file
You have the following options for importing the configuration file:
Via the PC Station Panel menu (import configuration file)
By means of a script
Import via the PC Station Panel menu
Requirement
If you want to start the import of the configuration file via the menu in the PC Station Panel of
an S7-150xS(P) F, the executing user must be in the Windows user group "Failsafe
Operators".
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
334 Programming and Operating Manual, 10/2018, A5E02714440-AH
Procedure
WARNING
If the import operation was successful, you will receive a positive feedback. If you do not
receive a positive message, you must assume that the import operation was not successful
and that the old security program is still present.
When importing a configuration file of a PC station via the menu of the panel with a security
program, you must observe the following:
Use the unique name of the configuration file to check that you have selected the
required configuration file.
To ensure that the import is performed on the correct S7-1500 F software controller,
when importing a configuration file via LAN you must ensure that you address the
correct S7-1500 F software controller. To do this, perform one of the following actions:
Remove the physical connections and routing options to other S7-1500 F software
controllers.
Use unique computer names and unique user logins or use other identification
options.
(S084)
Import by means of a script
WARNING
You must check in the script based on the specified identification parameters whether the
import of the configuration file is permitted for the respective target system (e.g. by
evaluating the F-CPU name, project name or using the plant designation).
In addition, checking the respective instance of the target system, which means a
diversified check of your addressing and/or checking the version of the configuration file, for
example, only higher versions or the exclusion of specific versions (black list), can also be
necessary or useful. You must store this information on the target system beforehand.
Example of checking the respective version for reliability:
The script evaluates the information about the version and only allows configuration files
of a higher version, for example.
As a machine manufacturer, you must ensure that the script is protected against
unauthorized manipulation (change to contents or name).
If as a machine manufacturer you only make available the configuration files, you have to
ensure that an incorrect configuration file is not imported during import through technical
measures (extended checks in the script) and training of the machine operators.
(S082)
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 335
The script checks for:
Matching machine ID
Version ID greater than current one. If so, the new version is written to the txt file.
Instance number
The figure below contains a systematic overview of checking the configuration file in the
script with the help of an identification parameter stored in a separate file (shown in violet in
the figure below):
Compiling and commissioning a safety program
10.3 Downloading project data
SIMATIC Safety - Configuring and Programming
336 Programming and Operating Manual, 10/2018, A5E02714440-AH
WARNING
You determine the successful import of a security program via the script by evaluating the
corresponding return value (0x51A3). If the corresponding return value is not returned by
the script command PCSystem_Control, the import has failed and the old safety program
may still be present.
To ensure that the return value is not from the previous import, you need to reset the return
value to 0x3FF ("PCSystem_Control /ImportConfig" without entering a data name) before
the import and then check that the return value has been reset to 0x3FF (Enter
"PCSystem_Control /GetStatus /ImportConfig" and then enter "echo %errorlevel%". This
instruction must deliver the return value 0x3FF.)
If the import operation is triggered by a server, feedback about the positive return value
must be given.
For traceability we recommend that you document the import operation in a log file.
If the the configuration file is imported manually via the Windows command line (via script
command), you need to do one of the following:
Reset the return value to 0x3FF and check it before the import (see above).
Carry out the import.
Evaluate return value (enter "PCSystem_Control /GetStatus /ImportConfig" and then
enter "echo %errorlevel%". This instruction must deliver the return value 0x51A3).
Carry out the import.
Manual program identification performed, e.g. via the panel of the F-CPU.
(S083)
Note
The positive return value when importing a configuration file via script is "0x51A3” for an S7
-
1500 F software controller, in contrast to the S7
-1500 software controller, in which case it is
"0x0000".
When the file is imported via script, the authorization should be moved to the script. This
means that the executing user does not need a higher authorization as the script which was
made available by the machine manufacturer contains the necessary authorizations (user
group "Failsafe Operators").
The rights are assigned via script by assignment of the Windows service to the
corresponding user group. This initial installation must be performed beforehand by the
Windows administrator on every computer with S7-150xS(P) F. The Windows service can
be called by the executing user and the Windows service executes the script.
Compiling and commissioning a safety program
10.4 Program identification
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 337
10.4
Program identification
You use the program identification to determine that the correct safety program was
downloaded to the F-CPU To do so, you compare the collective F-signatures of the safety
program and the assignment of the "F-admin" rights online with the expected value. The
expected value can be, for example, the collective F-signature of the safety program offline
from the
Safety Administration Editor
or from the safety summary. Check the assignment of
the "F-admin" right in the
Safety Administration Editor
.
Use organizational measures to ensure that the safety program is not downloaded by any
other TIA Portal (on a separate programming device or PC) while you perform the program
identification.
With the
Safety Administration Editor
For a program identification using the
Safety Administration Editor
, follow these steps:
1. Open the
Safety Administration Editor
of the F-CPU you want to check.
2. Connect online with the F-CPU you want to check.
3. Compare the collective F-signature displayed online with the expected value in the
"General" section.
4. Check whether the offline and online program are consistent (Page 375).
5. Check whether the green symbol is displayed in the column "status" and "Version
comparison".
6. Check in the "Web server F-admins" section whether only authorized users have the "F-
admin" right offline and online.
Compiling and commissioning a safety program
10.4 Program identification
SIMATIC Safety - Configuring and Programming
338 Programming and Operating Manual, 10/2018, A5E02714440-AH
With HMI
For a program identification using the HMI, follow these steps:
1. Read the collective F-signature of the safety program from the F_PROG_SIG tag of the
F-global DB (Page 148) (S7-300, S7-400) or the tag F_SYSINFO.F_PROG_SIG of the
F-runtime group information DB (Page 148) (S7-1200, S7-1500).
2. Compare the value of the F_PROG_SIG tag with the expected value.
With the display of an S7-1500 F-CPU
For a program identification using the display of an F-CPU, follow these steps:
1. In the display menu, go to "Overview > Fail-safe".
2. Compare the displayed collective F-signature with the expected value.
With the Web server of an S7-1200/1500 F-CPU
For a program identification using the Web server of an S7-1200/1500 F-CPU, follow these
steps:
1. Read the collective F-signature on the homepage of the Web server.
2. Compare the displayed collective F-signature with the expected value.
See also
Safety Administration Editor (Page 81)
Compiling and commissioning a safety program
10.5 Comparing Safety Programs
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 339
10.5
Comparing Safety Programs
Compare safety programs as in standard
You can use the
comparison editor
in
STEP 7
for offline-online or offline-offline comparison
of safety programs. The procedure is the same as for standard user programs. The contents
of F-blocks are also compared for the comparison of safety programs. As a result, an offline-
offline comparison can also be used for an acceptance of changes (Page 378). You enable
this comparison by selecting the "Safety" comparison criterion and disabling all other
comparison criteria.
Comparison result for safety programs
The representation of the comparison result corresponds to the representation of
STEP 7
.
If you click the "Program blocks" folder on the left of the comparison editor, you can see the
collective F-signature of the safety program displayed under "Comparison result". You also
receive information about whether the safety program is consistent.
Compiling and commissioning a safety program
10.5 Comparing Safety Programs
SIMATIC Safety - Configuring and Programming
340 Programming and Operating Manual, 10/2018, A5E02714440-AH
If you click on an F-block, you can see the respective signatures and interface signatures in
addition to the standard information.
Note
If you interrupt the connection to the F
-CPU during the online/offline comparison, the
comparison result will be incorrect.
Comparison filter options
You can use filters in the
comparison editor
to limit the comparison result to the following
block groups:
Compare only F-blocks
Compare only F-blocks relevant for certification
Compare only standard blocks
You also have the
STEP 7
filter options "Show only objects with differences" and "Show
identical and different objects".
For comparison of safety programs, F-blocks in the "System blocks" folder are also relevant.
Comparison criteria
Make sure that under only the comparison criterion "Safety" is enabled.
Classification of displayed changes
Regardless of whether you carried out an offline/online or offline/offline-comparison, the
following changes could account for the indicated changes to the automatically generated F-
blocks:
Change in the maximum cycle time of F-runtime group and warn cycle time of F-runtime
group
Change in F-parameters of the F-CPU
changed safety system version or change to the hardware configuration (S7-1200/1500:
Displayed as change of the "F_SystemInfo_DB" block).
(S7-300/400) Change in the F-runtime group communication, for example, change in the
number of a DB for F-runtime group communication
Change in main safety block, F-FB, F-FC, F-DB
Change of the hardware configuration for the F-I/O addressed in the safety program
It is possible that a block is displayed as changed, but no changes are displayed in the
detailed comparison of the block content. This is not a display problem but means that
changes of addresses in the tag table, for example, have an effect on this block. Test this
block in case of doubt.
Compiling and commissioning a safety program
10.6 Printing project data
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 341
Printing result of comparison
The comparison result can be printed via "Project > Print" in the menu bar or the print button
in the toolbar. Select "Print objects/area" "All" and "Properties" "All".
Make sure that all pages were printed completely. Incomplete printouts (e.g. due to low on
toner) must not be used for the acceptance of changes.
10.6
Printing project data
Printing
You can print all important project data (hardware configuration of the F-CPU and F-I/O,
safety program). You obtain a "safety summary" that, alongside the documentation, serves
as a basis for testing the correctness of the individual components of the system.
Correctness is a prerequisite for system acceptance.
The collective F-signature specifications in the footer of the printout ensure that the printout
is explicitly associated with a safety program.
Safety summary
The safety summary provides documentation of the safety-related project data which
supports you during acceptance of the system.
Procedure for creating a safety summary
To create a safety summary, follow these steps:
1. In the project tree, select the
Safety Administration Editor
of the F-CPU whose safety
summary you want to create.
2. Select "Print" in the shortcut menu or "Project > Print" in the menu bar or the print button
in the toolbar.
In the displayed dialog, you can make layout settings for the printout and specify the
scope of the printout (all/subset), among other things.
3. Under "Document information", select one of the ISO formats, e.g.
"DocuInfo_ISO_A4_Portait".
4. Select the "All" option, if the F-blocks and F-compliant PLC data types are to be shown in
the printout. This is necessary, for example, to document the program code for the
acceptance(see Acceptance of system (Page 361)). Select the "Compact" option to
exclude the source code from the printout.
5. Click the "Print" button.
As a result, you receive the safety summary for the F-CPU.
Make sure that all pages were printed completely. Incomplete printouts (e.g. due to low on
toner) must not be used for the acceptance of changes.
Compiling and commissioning a safety program
10.6 Printing project data
SIMATIC Safety - Configuring and Programming
342 Programming and Operating Manual, 10/2018, A5E02714440-AH
Contents of the summary in overview
The topics that are considered in the summary are summarized in the following:
General information on program identification, signatures, software versions, access
protection, settings of the safety program (from the "Settings" work area of the
Safety
Administration Editor
), for example safety system version.
System library elements used in safety program (from the "Instructions" task card) along
with their versions
Information about the F-runtime groups (e.g. cycle time warning limit of the F-runtime
group, maximum cycle time of the F-runtime group)
List of the F-blocks within the "Program blocks" folder (e.g. name, function, associated
F-runtime group, signature)
(S7-1200, S7-1500) List of the know-how protected F-blocks used in the safety program
(e.g., name, signature, used safety system version, used versioned instructions or called
F-blocks).
(S7-1200, S7-1500) List of F-compliant PLC data types (UDT), if these exist in the safety
program.
Data from the standard user program that are evaluated in the safety program
Block parameters of the safety-related CPU-CPU communication
(S7-300, S7-400) Absolute addresses and names of the F-shared DB tags that can be
accessed from the standard user program
Information on hardware (used F-I/O, CPU version, addresses)
Information on the printout (print date, number of pages)
Content of the footer of the printouts
On the basis of the footer of the printout, you can find out:
Whether the printed safety-related project data is consistent and whether all pages of the
printout belong to the same safety program and the same version (the same F-collective
signature in the footer of every page means that the printout belongs to the safety
program with this F-collective signature).
The footer is added to the source code of the F-blocks only if the "All" option was selected
for the safety summary.
If F-blocks are printed by other means, the footer is omitted, and you can no longer easily
identify whether the block printout belongs to the current safety program version.
Printing a migrated project
You can only print a safety summary for a project migrated from
S7 Distributed Safety V5.4
SP5
if the project was compiled with
STEP 7 Safety Advanced
and the new program
structure for safety programs (main safety block) has therefore been applied. Otherwise, the
printout is not possible and you will receive a corresponding error message.
We recommend that you print out your project in
S7 Distributed Safety V5.4 SP5
before the
migration.
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 343
10.7
Testing the safety program
10.7.1
Overview of Testing the Safety Program
Complete function test or test of changes
After creating a safety program, you must carry out a complete function test in accordance
with your automation task.
For changes made to a safety program that has already undergone a complete function test,
only the changes and that there is no effect on the parts of the safety program that were not
changed need be tested.
Monitoring
Read-only test functions (such as monitoring tags of the safety program) are available for
safety programs as in the standard.
Modifying
Read and write test functions (such as controlling tags of the safety program) are only
available to a limited extent for safety programs and only in disabled safety mode.
Simulation via
S7-PLCSIM
You can test the safety program using
S7-PLCSIM
. You use
S7-PLCSIM
in the same way as
for standard user programs.
You start the simulation with
S7-PLCSIM
using menu item "Online > Simulation > Start".
Rules for testing
Forcing of F-I/O inputs and F-I/O outputs is not possible.
Controlling F-I/O outputs in connection with the function “Enabling F-I/O outputs" is not
possible.
Setting breakpoints in the standard user program will cause errors in the safety program
(see also Testing the safety program (Page 347)).
Changes in the configuration of F-I/O or safety-related CPU-CPU communication can
only be tested after the hardware configuration has been saved and downloaded, and
after the safety program has been compiled and downloaded to the F-CPU.
See also
Disabling safety mode (Page 344)
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
344 Programming and Operating Manual, 10/2018, A5E02714440-AH
10.7.2
Disabling safety mode
Introduction
The safety program generally runs in the F-CPU in safety mode. This means that all fault
control measures are activated. The safety program cannot be modified during operation (in
RUN mode) in safety mode. You must disable safety mode of the safety program to, for
example, modify tags in the safety program in RUN mode. Safety mode remains disabled
until the F-CPU is next switched from STOP to RUN mode.
Rules for disabling safety mode
WARNING
Because changes to the safety program can be made in RUN mode when safety mode is
deactivated, you must take the following into account:
Disabling safety mode is intended for test purposes, commissioning, etc. Whenever
safety mode is disabled, the safety of the system must be ensured by other
organizational measures, such as monitored operation, manual safety shutdown, and
access restrictions to certain areas.
Disabling of safety mode must be displayed.
Use the MODE tag in the F-global DB ("F_GLOBDB".MODE) for S7-300/400 F-CPUs or
in the F-runtime group information DB (e.g. RTG1SysInfo.F_SYSINFO.MODE) for
S7-1200/1500 F-CPUs, which you can evaluate to read the operating mode (1 =
Disabled safety mode). This means not only is the disabled safety mode displayed on
the programming device or PC in the dialog box for disabling safety mode, but it can
also be indicated by means of an indicator light controlled by the standard user program
or a message to an HMI system generated by evaluating the above-mentioned
"Disabled safety mode" variable in the F-shared DB.
It must be possible to verify that safety mode has been disabled. A log is required, if
possible by recording and, if applicable. archiving alarms to the operator control and
monitoring system or, if need be, through organizational measures. In addition, it is
recommended that disabling of safety mode be indicated on the HMI system.
Safety mode is disabled F-CPU-wide. You must, however, take the following into
account for safety-related CPU-CPU communication: If the F-CPU that sends the data is
in disabled safety mode, you can no longer assume that the data sent by this F-CPU are
generated safely. You must then ensure safety in those units that are affected by the
sent data through organizational measures or output safe substitute values in the
F-CPU that receives the data by evaluating SENDMODE* instead of the received data.
* SENDMODE is available to you as output of the RCVDP or RCVS7 instructions or in case
of communication via Flexible F-Link as a tag in the F-communication DB.
(S027)
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 345
Procedure for disabling safety mode
To disable safety mode, follow these steps:
1. Open the
Safety Administration Editor
of the corresponding F-CPU.
2. Open the work area "General (Page 83)" in the area navigation.
3. Check to see whether the safety mode status is displayed as activated.
If so, continue with the next step; if not, stop the process, because safety mode is already
disabled or cannot be disabled.
4. Click the "Disable safety mode" button.
5. Enter the password for the online safety program.
If you enter the correct password, another prompt will appear, which also contains the
collective F-signature in the F-CPU. Check to see whether this is the collective F-
signature you expected. If there is a match, acknowledge the dialog.
6. Enter the password for the F-CPU.
After correctly entering the password for the F-CPU, safety mode is disabled.
If the password is not valid, safety mode is not deactivated and remains active.
(S7-300, S7-400) When individual F-blocks are downloaded, the condition "Disable safety
mode" is listed automatically in the "Load preview" dialog. For this reason, it is not
necessary to explicitly disable safety mode before every F-block download.
Note
I
f the collective F-signature or the passwords do not agree for the safety program online and
offline, this means:
The offline safety program was modified after the last downloading, or
An incorrect F-CPU was addressed. Check the latter based on the online collective
F-signature.
Enabling safety mode
Note
To enable safety mode, the F
-CPU must be switched from STOP to RUN mode.
Switching the F
-CPU from STOP to RUN mode always enables safety mode, even if the
safety program has been modified or is not consistent. The MODE tag in the F
-
shared DB for
S7
-300/400 F-CPUs or F-runtime group information DB is set to "0" for S7-1200/1500
F
-CPUs.
If you have changed your safety program, but have not recompil
ed and downloaded it, the
F
-CPU can revert to STOP mode.
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
346 Programming and Operating Manual, 10/2018, A5E02714440-AH
Evaluating safety mode/disabled safety mode
If you wish to evaluate safety mode/disabled safety mode in the safety program, you can
evaluate the "MODE" tag in the F-shared DB for S7-300/400 F-CPUs or F-runtime group
information DB for S7-1200/1500 F-CPUs (1 = Disabled safety mode). You use fully qualified
access to access this tag (e.g. "F_GLOBDB".MODE or RTG1SysInfo.MODE).
You can use this evaluation, for example, to passivate F-I/O when the safety program is in
disabled safety mode. To do so, assign the "MODE" tag in the F-shared DB or F-runtime
group information DB to all "PASS_ON" tags in the F-I/O DBs of the F-I/O that you wish to
passivate.
WARNING
When the safety program is in disabled safety mode, the "MODE" tag in the F-shared DB or
F-runtime group information DB is also evaluated in disabled safety mode.
Even if the F-I/O are passivated in disabled safety mode as a result of evaluation of the
"MODE" tag, system safety must be ensured in disabled safety mode through other
organizational measures, such as operation monitoring and manual safety shutdown.
(S028)
See also
F-shared DB (S7-300, S7-400) (Page 148)
F-runtime group information DB (S7-1200, S7-1500) (Page 148)
Communication (Page 588)
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 347
10.7.3
Testing the safety program
Introduction
Tags of he safety program can be monitored at any time.
Controlling tags of the safety program is only possible in deactivated safety mode as some
fault control measures of the safety program have to be disabled for this.
You can control the following tags of the safety program:
Inputs and outputs of the F-I/O (channel values and value status (S7-1200, S7-1500))
Tags in F-global DB (except DB for F-runtime group communication)
Tags in instance DBs of F-FBs
Tags in F-I/O DBs (for permitted tags see F-I/O DB (Page 165))
Note
A modify function controlled by the F
-system is only possible if the
STEP 7 Safety
optional
package is installed. Modification of tags by means of an HMI system as well as modification
without an installed
STEP 7 Safety
optional package can cause the F-CPU to go into STOP.
Procedure for monitoring tags of the safety program
Monitor the required tags of the safety program from an open watch table or from the
program editor
(program status).
1. Proceed as in the standard. Additional information can be found in the
STEP 7
help
in
“Testing user programs".
Procedure for controlling tags of the safety program
Control the required tags of the safety program from an open watch table:
1. For modifying, deactivate the safety mode (Page 344) in the automatically shown dialog.
2. Terminate existing modify requests after testing is complete before activating safety
mode.
Values in F-DBs can only be modified online in the F-CPU. If the value is also to be changed
offline, you must do this by editing the start value offline and compiling the safety program.
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
348 Programming and Operating Manual, 10/2018, A5E02714440-AH
Proceed as follows to control tags of F-I/O:
1. Create a separate row for each channel value and value status (S7-1200, S7-1500) to be
modified. The control value must correspond to the channel value or value status.
2. Set “start of scan cycle" or “end of scan cycle" and "permanent" or “once".
Regardless of the trigger point setting, requests to modify inputs (PII) of F-I/O always
become effective before the main safety block is executed and requests to modify outputs
(PIQ) always become effective after execution of the main safety block.
3. (S7-300, S7-400) Create an additional watch table if you want to control more than 5
inputs/outputs.
Note
F
-I/O can only be modified in RUN mode of the F-CPU.
You cannot modify a configured F
-I/O from which neither a channel value or a value status
(S7
-1200, S7-1500), nor any tag from the associated F-I/O DB has been used in the safety
program. In your safety program, you should therefore always use at least one tag from the
associated F
-I/O DB or at least one channel value or value status (S7-1200, S7-1500) of the
F
-I/O to be modified.
For inputs (PI
I), modify requests take priority over fail-safe value output, while for outputs
(PIQ), fail
-safe value output takes priority over modify requests. For outputs (channels) that
are not activated in the properties for the F
-I/O, modify requests affect the PIQ only, and not
the F
-I/O.
Note
The following applies for S7
-1200/1500 F-CPUs:
To avoid invalid combinations of channel value and status value:
The value status is set by the F-system automatically to 1 when setting a channel value
to a value <> fail-safe value 0
The fail-safe value 0 is automatically output when setting the value status to 0 for the
associated channel value
WARNING
You need to specifically reset constant modify requests in the watch table in disabled safety
mode.
Please note that constant modify requests that are not correctly reset can remain active in
the background even after a STOP/RUN transition on the F-CPU.
Because the F-CPU is in safety mode again after a STOP/RUN transition, the constant
modify requests are no longer effective and are not shown in the watch table.
The requests become active again as soon as you disable safety mode again.
With a memory reset of the F-CPU, you can make sure that no constant modify requests
are active in the background on the F-CPU.
(S029)
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 349
Wiring test using watch table
You can carry out a wiring test for an input by changing an input signal and verifying whether
or not the new value arrives in the PII.
You can carry out a wiring test for an output by changing the output with the Modify function
and verifying whether the required actuator responds.
For the wiring test, note that a safety program must be running on the F-CPU, in which at
least one channel value or value status (S7-1200, S7-1500) of the F-I/O to be monitored or
modified or one tag from the associated F-I/O DB has been used.
For F-I/O that can also be operated as standard I/O (e.g., S7-300 fail-safe signal modules),
you can also carry out the wiring test for outputs using the Modify function in STOP mode by
operating the F-I/O as standard I/O rather than in safety mode.
Additional rules for testing (S7-300/400/1500)
Setting breakpoints in the standard user program will cause the following errors in the safety
program:
F-cycle time monitoring has expired
Error during communication with the F-I/O
(S7-1500) Fail-safe modules switch to safe mode after the configured F-monitoring time
has expired.
Error during safety-related CPU-CPU communication
Internal CPU faults
If you nevertheless want to use breakpoints for testing, you must first disable safety mode.
This will result in the following errors:
Error during communication with the F-I/O
Error during safety-related CPU-CPU communication
Difference between S7-1500 F-CPUs and S7-300/400 F-CPUs:
If a breakpoint is activated and reached, the F-CPU goes directly to STOP after HOLD.
If you want to switch to RUN again after HOLD to test your standard user program further,
you can simulate this with S7-PLCSIM.
No access protection is initially necessary for test purposes, commissioning, etc. This means
you can execute all offline and online actions without access protection, that is, without
password prompt.
See also
Changing the safety program in RUN mode (S7-300, S7-400) (Page 355)
Downloading project data to an F-CPU (Page 313)
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
350 Programming and Operating Manual, 10/2018, A5E02714440-AH
10.7.4
Testing the safety program with S7-PLCSIM
You can test your safety program together with your standard program on a simulated CPU
with
S7-PLCSIM
and without the need for hardware. Also observe warning S030 in the
section "Notes on Safety Mode of the Safety Program (Page 383)".
You use
S7-PLCSIM
for SIMATIC Safety F-systems as you would for S7 standard systems.
Note the following special features:
Safety mode/disabled safety mode
We recommend that you test your safety program in safety mode to detect whether the
F-CPU goes into STOP as early as in the test phase of your safety program in
S7-PLCSIM
as a result of, for example, that the results of instructions were outside the permitted range
for the data type.
The following simulations can be run in
S7-PLCSIM
, just as on an actual F-CPU, in disabled
safety mode only.
Modifying tags in F-DBs and F-I/O DBs.
The F-CPU can go to STOP mode in
S7-PLCSIM
if this is disregarded. The cause of the
diagnostics event is entered in the diagnostics buffer of the F-CPU.
(S7-1200, S7-1500) To prevent unintentional modification of tags in F-DBs and F-I/O DBs in
safety mode, we recommend that you do not select the "Activate/deactivate modification of
non-inputs" button in
S7-PLCSIM
During the simulation with
S7-PLCSIM
, monitoring of the maximum cycle time of the
F-runtime group and the cycle time warning limit of the F-runtime group (S7-1200, S7-1500)
are disabled.
Input simulation of F-I/O
Modification of inputs (channel values) in
S7-PLCSIM:
You modify inputs (channel values) of F-I/O as you would inputs (channel values) of
standard I/O in
S7-PLCSIM
.
Modification of inputs (value status) in
S7-PLCSIM:
(S7-1200, S7-1500) By modifying inputs (value status) of F-I/O you can simulate the
incoming and outgoing F-I/O/channel faults. Keep in mind the following notes/restrictions:
To realistically simulate the behavior of the F-I/O, you must note the connection between
channel value and value status on the real F-I/O. The combination value status = 0 and
channel value <> fail-safe value (0) is invalid and can result in the simulation deviating
from the behavior of the real F-CPU.
During the transition from "STOP" to "RUN" of the CPU in
S7-PLCSIM
, all F-I/O inputs
(value status) are initialized with 1. This means you can start with the modification of
inputs (channel values) without simulation of the inputs (value status).
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 351
The modification of inputs (value status) in
S7-PLCSIM
does not have an effect on the
tags QBAD and PASS_OUT in the F-I/O DB. Note that with real F-I/O QBAD and
PASS_OUT can be 1 as soon as the value status is 0 for at least one channel of the
F-I/O. (see tags of the F-I/O DB: PASS_OUT/QBAD/QBAD_I_xx/QBAD_O_xx and value
status (Page 171)).
For F-I/O configured with "Behavior after channel fault" = "Passivation of the complete
F-I/O", use the tag PASS_ON in the F-I/O DB for simulation of the passivation of the
complete F-I/O for F-I/O / channel faults. If you only passivate individual inputs (channel
value including value status) for the simulation, the behavior of the simulation will deviate
from the real F-CPU.
You can also use the PASS_ON tag in the F-I/O DB for F-I/O without value status to
simulate the passivation of the entire F-I/O in case of F-I/O or channel faults.
You must modify the inputs (channel values) to 7FFFH (for overflow) or 8000H (for
underflow) to simulate an F-I/O/channel fault of the SM 336; AI 6 x 13Bit or the SM 336;
F-AI 6 x 0/4...20 mA HART with configuration "Behavior after channel fault" = "Passivate
channel".
For F-I/O which does not support the "RIOforFA-Safety" profile, you must run a user
acknowledgment with a positive edge at the ACK_REI tag of the F-I/O DB as with a real
F-I/O for reintegration after the value status has changed from 0 to 1 or when the channel
value has changed from 7FFFH/8000H to unequal 7FFFH/8000H (see above) when
ACK_NEC = 1 of the F-I/O DB. Reintegration takes place automatically in all other cases
possibly deviating from the real F-I/O.
Update times
Keep in mind that the status of the inputs (channel values or value status (S7-1200/1500))
that you are monitoring in the SIM table in
S7-PLCSIM
is only identical to the status being
processed in the safety program if there is no passivation of the associated F-I/O.
With passivation of the F-I/O, the safety program operates with fail-safe values (channel
value and value status (S7-1200/1500) =0).
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
352 Programming and Operating Manual, 10/2018, A5E02714440-AH
Instructions for communication between F-CPUs
The following applies for SENDDP/RCVDP (S7-300/400) instructions and SENDDP/RCVDP
instructions with Version < 3.0 (S7-1200/1500):
You cannot simulate communication between F-CPUs with the SENDDP and RCVDP
instructions in
S7-PLCSIM
. You can, however, use the SENDDP and RCVDP instructions
together with
S7-PLCSIM
. During simulation in
S7-PLCSIM
, the RCVDP instruction outputs
the fail-safe values pending at its inputs SUBBO_xx and SUBI_xx ((S7-1200/1500) or
alternatively SUBDI_00). The SENDDP and RCVDP instructions signal this with 1 at output
SUBS_ON.
For SENDDP/RCVDP instructions with Version >= 3.0 the following applies:
During the simulation with
S7-PLCSIM
it is possible to simulate the received data and the
information "Deactivated Safety Mode" (RCVDP) or respectively the information "Substitute
value output" (SENDDP) in the corresponding transfer area for inputs. Note the following
notes:
The simulated values do not become active until you set the SIMULATION bit for the first
time in the respective simulation control word (see the following table) after the F-system
has started up. Before setting the SIMULATION bit, the RCVDP instruction outputs the
fail-safe values that are pending at its inputs SUBBO_xx and SUBI_yy ((S7-1200/1500) or
alternatively SUBDI_00).
The setting of the SEND_MODE bit in the simulation control word causes a setting of the
SENDMORE output for the RCVDP instruction.
The setting of the STATUS_SUBS bit in the simulation control word causes a setting of
the SUBS_ON output for the SENDDP instruction.
Reserved bits in the simulation control word always have to be 0.
During a STOP/RUN transition from
S7-PLCSIM
the most recently simulated values in
the transfer area for inputs are kept.
The start address(es) of the configured transfer area for the input and output data can be
found in the respective configuration (see also "Configuring and programming
communication (S7-1200, S7-1500) (Page 270)“).
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 353
Table 10- 1 Structure of the relevant transfer area for inputs of the simulation control word (instruction RCVDP)
Byte
Meaning
Comment
0
RD_BO_15 … RD_BO_08
1
RD_BO_07 … RD_BO_00
DINTMODE=0:
2 RD_I_00 Word RD_I_00, MSB1) first
3
4
RD_I_01 Word RD_I_01, MSB1) first
5
Alternative DINTMODE=1:
2
RD_DI_00 High Word from RD_DI_00, MSB1) first
3
4
Low Word from RD_DI_00
XOR 0x8000
, MSB1) first
5
6 Simulation control word (High Byte) Bit 0…6: Reserved
Bit 7: SIMULATION: Activating RCVDP simulation
7 Simulation control word (Low Byte) Bit 0: SEND_MODE: Set output SENDMODE
Bit 1…7: Reserved
8 … 11
Reserved
1) MSB: most significant bit
Table 10- 2 Structure of the relevant transfer area for inputs of the simulation control word (instruction SENDDP)
Byte
Meaning
Comment
0 Simulation control word (High
Byte)
Bit 0: STATUS_SUBS: Set output SUBS_ON
Bit 1…6: Reserved
Bit 7: SIMULATION: Activating SENDDP simulation
1 Simulation control word (Low
Byte)
Bit 0…7: Reserved
2 … 5
Reserved
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
354 Programming and Operating Manual, 10/2018, A5E02714440-AH
WARNING
You must take the following into account for safety-related CPU-CPU communication with
the communication type Flexible F-Link:
If the F-CPU that sends the data is on a simulated F-CPU with S7-PLCSIM, you can no
longer assume that the data sent by this F-CPU are generated safely. You must then
implement organizational measures such as operation monitoring and manual safety
shutdown to ensure safety in those portions of the system that are affected by the sent
data. Alternatively, you must output fail-safe substitute values instead of the received data
in the F-CPU that receives the data by evaluating SENDMODE*.
* SENDMODE is available to you as a tag in the F-communication DB.
(S086)
(S7-300, S7-400) You cannot simulate communication between F-CPUs with the SENDS7
and RCVS7 instructions in
S7-PLCSIM
. You can, however, use the SENDS7 and RCVS7
instructions together with
S7-PLCSIM
.
During simulation in
S7-PLCSIM
, the RCVS7 instruction outputs the initial values specified in
the communication DB as fail-safe values. The SENDS7 and RCVS7 instructions signal this
with 1 at output SUBS_ON.
Inconsistent safety program (S7-1200, S7-1500)
If the CPU goes into STOP in
S7-PLCSIM
with the diagnostic entry "Safety program:
inconsistent", the F-CPU is not initialized correctly in
S7-PLCSIM
yet. Perform a memory
reset of the F-CPU in
S7-PLCSIM
and download the program once again to the CPU in
S7-PLCSIM
.
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 355
10.7.5
Changing the safety program in RUN mode (S7-300, S7-400)
Introduction
Changes to the safety program during operation (in RUN mode) can only be made in
disabled safety mode (Page 344). You make changes to F-blocks offline in the
program
editor
in the same way as for a standard program. F-blocks cannot be changed online.
Note
If you do not
want to make changes to the safety program during operation, see Creating
F
-blocks in FBD/LAD (Page 151).
Procedure for changing the safety program in RUN mode
To change the safety program, follow these steps:
1. Change the main safety block or F-FB and its associated instance DB, F-FC, or F-DB in
the
Program editor
.
2. Download the changed F-block(s) to the F-CPU (for procedure, see Downloading project
data to an F-CPU (Page 313)). The entire program is then automatically compiled.
3. If safety mode is active, the "Load preview" dialog will prompt you to deactivate it and to
enter the password for the safety program.
Note
When do
wnloading in disabled safety mode, you can only download the fail-safe blocks
created by you (main safety blocks, F
-FB, F-FC, or F-DB), F-application blocks, or
standard blocks and their associated instance DBs. If you download automatically added
F
-blocks (F-SBs or automatically generated F-blocks and associated instance DBs,
F
-shared DB), the F-CPU can go to STOP mode or safety mode can be activated.
Therefore, always select individual blocks only when downloading in disabled safety
mode.
Sequence for downloading changes
Changes in the safety program in RUN mode when safety mode is disabled can, for
example, cause the status of an actuator to change as a result of program changes.
After changes, start by downloading the safety program and then the function of the standard
user program monitored by the safety program.
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
356 Programming and Operating Manual, 10/2018, A5E02714440-AH
Restrictions on safety-related CPU-CPU communication
During operation (in RUN mode), you cannot establish new safety-related CPU-CPU
communication by means of new SENDDP/RCVDP or SENDS7/RCVS7 instructions.
To establish new safety-related CPU-CPU communication you must always download the
relevant safety program consistently to the F-CPU while in STOP mode after inserting a new
SENDDP, SENDS7, RCVDP, or RCVS7 instruction.
Restrictions on F-runtime group communication
You cannot make any changes to the safety-related communication between F-runtime
groups in RUN mode. This means that you cannot assign, delete, or change any DBs for F-
runtime group communication of an F-runtime group.
Following changes in the F-runtime group communication, you must always download the
safety program consistently to the F-CPU while in STOP mode.
Restrictions on F-I/O access
If during operation (in RUN mode), you insert an F-I/O access to an F-I/O of which no single
channel value or tag from the associated F-I/O DB has yet been used in the safety program,
the F-I/O access only becomes effective when the safety program is downloaded
consistently to the F-CPU.
Changing the standard user program
You can download changes in the standard user program when the F-CPU is in RUN mode,
regardless of whether safety mode is enabled or disabled.
WARNING
(S7-300, S7-400) In safety mode, access with the CPU password must not be authorized
during changes to the standard user program as this would also allow changes to the safety
program. To rule out this possibility, you must configure the protection level "Write
protection for fail-safe blocks" and configure a password for the F-CPU. If only one person
is authorized to change the standard user program and the safety program, the protection
level "Write protection" or "Read/write protection" should be configured so that other
persons have only limited access or no access at all to the entire user program (standard
and safety programs).
(S001)
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 357
Procedure for applying changes to the safety program
If you download individual F-blocks to the F-CPU during operation (in RUN mode), the
F-system blocks (F-SBs) and the automatically generated F-blocks are neither updated nor
downloaded, resulting in an inconsistent safety program in the F-CPU. Use the following
procedure to apply changes to the safety program:
1. Download the safety program consistently to the F-CPU, and activate safety mode by
switching the F-CPU from STOP to RUN mode (for procedure, see Downloading project
data to an F-CPU (Page 313)).
2. Follow the steps described in Acceptance of Changes (Page 378).
10.7.6
Changing the standard user program in RUN mode (S7-1200, S7-1500)
Changing the standard user program
You can download changes in the standard user program when the F-CPU is in RUN mode,
regardless of whether safety mode is enabled or disabled.
10.7.7
Deleting the safety program
Deleting individual F-blocks
To delete an F-block, follow the same procedure as in
STEP 7
.
Deleting an F-runtime group
See Deleting an F-runtime group (Page 150)
(S7-300, S7-400) Remove all calls that you have used to call the safety program
(Main_Safety).
Compiling and commissioning a safety program
10.7 Testing the safety program
SIMATIC Safety - Configuring and Programming
358 Programming and Operating Manual, 10/2018, A5E02714440-AH
Deleting the entire safety program for S7-300/400 F-CPUs
with
inserted memory card
(SIMATIC Micro memory card or flash card)
To delete an entire safety program, proceed as follows:
1. Delete all F-blocks (shown with yellow symbol) in the project tree.
2. Remove all calls that you have used to call the safety program (Main_Safety).
3. Select the F-CPU in the
hardware and network editor
and clear the "F-capability
activated" option in the properties of the F-CPU.
4. Compile the project data of the F-CPU
The offline project no longer contains a safety program.
5. To delete a safety program on the Memory Card (SIMATIC Micro Memory Card or Flash
Card), insert the Memory Card (SIMATIC Micro Memory Card or Flash Card) in the
programming device or PC or in a SIMATIC USB prommer.
6. Select the menu command "Project > Card Reader/USB memory > Show Card
Reader/USB memory" in the menu bar.
7. Open the "SIMATIC Card Reader" folder and delete the Memory Card.
8. Insert the Memory Card into the F-CPU.
You can then download the offline standard user program to the F-CPU.
Deleting the entire safety program for S7-400 F-CPUs
without
inserted flash card
To delete an entire safety program, proceed as follows:
1. Delete all F-blocks (shown with yellow symbol) in the project tree.
2. Remove all calls that you have used to call the safety program (Main_Safety).
3. Select the F-CPU in the
hardware and network editor
and clear the "F-capability
activated" option in the properties of the F-CPU.
4. Compile the project data of the F-CPU
The offline project no longer contains a safety program.
5. Perform a memory reset on the F-CPU (in the "Online tools" task card of the F-CPU).
You can then download the offline standard user program to the F-CPU.
Delete the entire safety program for SIMATIC S7-1200/1500 F-CPUs
To delete an entire safety program, proceed as follows:
1. Delete all F-blocks (shown with yellow symbol) in the project tree.
2. Select the F-CPU in the
hardware and network editor
and clear the "F-capability
activated" option in the properties of the F-CPU.
3. Compile the project data of the F-CPU
The offline project no longer contains a safety program.
You can then download the offline standard user program to the F-CPU.
Compiling and commissioning a safety program
10.8 F-change history
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 359
10.8
F-change history
Enable the logging of changes to the safety program by using the option "Enable F-change
history" in the
Safety Administration Editor
. The F-change history behaves like the standard
change history.
An F-change history is created for each F-CPU in the project navigation under "Common
data/logs".
The following is logged in the F-change history:
Collective F-signature
User name
Compile time stamp
Download of the safety program with time stamp
Compiled F-blocks with signature and time stamp
The F-change history can contain a maximum of 5000 entries per F-CPU. When the 5000
entries are exceeded, a new F-change history is created using the naming scheme "F-
change history <CPU name> YYYY-MM-DD hh:mm:ss".
After a project upgrade, the "Go to" function is not supported anymore for the F-change
history of the project for the entries which were created before
STEP 7 Safety
V15.1.
NOTICE
The connection between the F-CPU and the associated F-change history is made through
the name of the F-change history.
Therefore, do not rename the F-CPU and the F-change history. If you rename the F-
CPU or
the F-change history, a new F-change history with the current name of the F-CPU is
started.
Note
You may not use
the F-change history to recognize changes in the safety program/in the
configuration of the F
-I/Os during the acceptance of changes.
To accept changes, proceed as described under
Acceptance of Changes (Page 378).
Note
We recommend activating the F
-change history before changing over to productive
operation.
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 361
System acceptance
11
11.1
Overview of System Acceptance
Introduction
During a system acceptance test, all the standards and guidelines (for example PROFINET
Installation Guidelines) relevant to the specific application must be complied with. This also
applies to systems that are not "subject to acceptance". For the acceptance, you must
consider the requirements in the Certification Report
(http://support.automation.siemens.com/WW/view/en/49368678/134200).
As a general rule, the acceptance of an F-System is performed by an independent expert.
The independence required of the expert must be defined in the safety plan and depends on
the required PL/SIL.
Observe all warnings in this manual.
WARNING
The configuration of F-CPUs and F-I/Os as well as the programming of F-blocks must be
carried out as described in this documentation.
You must observe all aspects described in
the section System acceptance (Page 361) to ensure secure operation with the system
SIMATIC SAFETY. Any other procedures are not permitted.
(S056)
System acceptance
11.1 Overview of System Acceptance
SIMATIC Safety - Configuring and Programming
362 Programming and Operating Manual, 10/2018, A5E02714440-AH
Proof of the correct implementation of the safety-related project data
In order for a system acceptance to be granted, you must recognize and document the
correctness of the individual components. For documentation of the component properties,
you must create a safety summary.
The following characteristics must be covered:
Correctness of the safety program including hardware configuration (including testing)
(Page 363)
Completeness of the safety summary (Page 364)
Compliance of the system library elements used in the safety program with Annex 1 of
the Report for the TÜV certificate (Page 365)
Compliance of the know-how protected F-blocks used in the safety program with their
safety documentation. (Page 366)
Completeness and correctness of the hardware configuration (Page 368)
Correctness and completeness of the communication configuration (Page 374)
Identity of online and offline program (Page 375)
Other characteristics (Page 376) such as software version, use of data from the standard
user program
After the acceptance, you should archive all relevant documents and also the project data so
as to make the accepted project available as a reference for a subsequent acceptance.
Safety summary
The safety summary (Page 341) is the project documentation required for acceptance of the
system.
System acceptance
11.2 Correctness of the safety program including hardware configuration (including testing)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 363
11.2
Correctness of the safety program including hardware configuration
(including testing)
The correctness of software cannot only be ensure through tests and verifications during
commissioning, but rather already requires the observance of a wide variety of measures
during creation. Also see warning S062 on this in chapter "Overview (Page 23)".
Verification/function test
Already during the creation, you will test (Page 343) your safety program and the associated
hardware configuration. You must carry out tests with regard to the specification of your
safety functions and document them before you seek acceptance for the system.
To allow you to perform a code review of your safety program and document the accepted
program code, the source code of all F-blocks is printed as a part of the safety summary
(Page 341), provided you have selected the "All" property for the printout.
If you want to carry out a function test after loading, you have to carry out program
identification after loading. Additional information is available in "Downloading project data
(Page 313)".
The correct function of the safety program must be guaranteed by complying with all steps
from the "Overview of System Acceptance (Page 361)" chapter before it may be used
productively. When using configuration control (option handling), you must ensure correct
operation of the safety program for all possible station options by performing appropriate
functional tests. You should archive the test reports along with the safety summary and the
acceptance documents.
Times, for example monitoring times (Page 607) and delay times, can only be verified to a
limited extent with functional tests (Page 313). You should check these times selectively to
determine whether they are dimensioned correctly, for example, on the basis of the safety
summary.
Some of these times are itemized specially in the safety summary, for example, the
F-monitoring time (for communication between F-CPU and F-I/O) and the monitoring time of
the safety-related CPU-CPU communication (TIMEOUT input). For the monitoring times
derived under normative conditions, the Excel file for response time calculation is available
on the Internet (http://support.automation.siemens.com/WW/view/en/49368678/133100).
These have to be considered together with the practically determined conditions of the
application. Note that these monitoring times have an impact on the response times of your
safety functions.
System acceptance
11.3 Completeness of the safety summary
SIMATIC Safety - Configuring and Programming
364 Programming and Operating Manual, 10/2018, A5E02714440-AH
Consistency of the safety program
Check in the "General information" section of the safety summary to determine whether the
safety program was recognized as "consistent".
This is the case for S7-300/400 F-CPUs only if the following signatures are also identical:
Collective F-signature ("General information" section, "Collective F-signature")
"Signature of F-blocks with F-attribute" ("General information" section, "Current
compilation")
Consistency of the safety program is required for the acceptance. If the signatures are not
identical, you have the possibility to establish the consistency through recompiling of the
safety program and new creation of the safety summary.
11.3
Completeness of the safety summary
Introduction
If your safety program status including hardware configuration is ready for acceptance, you
must carry out and document additional checks on the basis of the safety summary to prove
that the safety summary is complete and is part of the safety program to be accepted.
Procedure for creation of safety summary
To generate the safety summary, follow the procedure described in Printing project data
(Page 341).
In so doing, use the "All" property in order to include the source code of your F-blocks in the
printout.
Checking the safety summary for completeness
If you want to use an existing summary, whose completeness is not exactly known, you must
check to determine whether the same collective F-signature is contained in the footer on all
pages of the printout. This allows you to prove that all printed sheets belong to the same
project.
In section "Supplementary information", you can find the number of pages in the safety
summary, among other things. With this, you can prove that all pages of the safety summary
are printed. Incomplete printouts (for example due to low on toner) must not be used for an
acceptance.
If you created the safety summary with the "All" option, the source code of all F-blocks will
also be printed. The printout of this source code also contains the footer to enable you to
easily assign the source code to a particular safety summary.
System acceptance
11.4
Compliance of the system library elements used in the safety program with Annex 1 of the Report for the TÜV certific
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 365
Association with the safety program
In the "General information" section of the safety summary, check whether the collective F-
signature corresponds to the collective F-signature of the safety program to be accepted in
the work area of the
Safety Administration Editor
under "General". If they are not the same,
then the summary and safety program do not match.
11.4
Compliance of the system library elements used in the safety
program with Annex 1 of the Report for the TÜV certificate
Introduction
The
STEP 7 Safety
optional package contains LAD/FBD instructions for programming of
your safety program as well as F-system blocks that have been created and tested by
SIEMENS and certified by TÜV for creating an executable safety program. In the process,
the F-system blocks used are automatically defined by the F-system based on the set safety
system version (see section "Settings" area (Page 90)).
To allow you to check whether the used versioned LAD/FBD instructions and F-system
blocks correspond to Annex 1 of the Report for the TÜV certificate and to the versions you
intend to use, these are listed in the safety summary.
Procedure
To check, download the current Annex 1 of the report for the TÜV certificate "SIMATIC
Safety" from the Internet
(http://support.automation.siemens.com/WW/view/en/49368678/134200).
Proceed as follows for the check:
WARNING
(S7-1200, S7-1500) The versions of the versioned LAD/FBD instructions listed in the
safety summary in the section "System library elements used in safety program" must
correspond to the versions in Annex 1 of the Report for the TÜV Certificate.
(S7-300, S7-400) The versions, signatures and initial value signatures of the versioned
LAD/FBD instructions and F-system blocks listed in the safety summary in the section
"System library elements used in safety program" must correspond to the versions,
signatures and initial value signatures in Annex 1 of the Report for the TÜV Certificate.
The versions of the versioned LAD/FBD instructions listed in the safety summary must
meet the safety requirements of your application.
Keep in mind possible differences in functionality of different versions specified in the
section for the respective instruction.
The safety system version listed in the safety summary under "Safety program settings"
must match the versions in Annex 1 of the Report for the TÜV Certificate.
(S054)
In case of discrepancies, recheck whether you have the correct versions.
(S7-300 / 400) Differences may also arise when there are F-blocks / instructions in your
safety program that are not used.
System acceptance
11.5 Compliance of the know-how protected F-blocks used in the safety program with their safety
documentation.
SIMATIC Safety - Configuring and Programming
366 Programming and Operating Manual, 10/2018, A5E02714440-AH
11.5
Compliance of the know-how protected F-blocks used in the safety
program with their safety documentation.
If you use know-how protected F-blocks for the programming of your safety program
(e.g. from libraries), the source code for these is not printed in the safety summary.
Therefore, the author of the know-how protected F-block must already carry out acceptance
of the F-block and provide the following information:
S7-300/400 F-CPUs
Signature and initial value signature of the know-how protected F-block
Versions of all the used versioned LAD/FBD instructions
Signatures and initial value signatures of all called F-blocks
During a system acceptance test, you have to carry out the following checks using the safety
summary:
The signature and initial value signature of each know-how protected F-block listed in the
safety summary in the section "F-blocks in the safety program" must agree with the
signature and initial value signature documented by the author.
The versions of the versioned LAD/FBD instructions listed in the safety summary in the
section "System library elements used in safety program" must correspond to the
versions of each know-how protected F-block documented by the author or must be
functionally identical with these.
The signatures and initial value signatures of the F-blocks called in each know-how
protected F-block listed in the safety summary in the section "F-blocks in the safety
program" must correspond to the signatures and initial value signatures (of the called F-
blocks) documented by the author.
In case of differences, set the documented (or functionally identical) versions and use the F-
blocks with the documented signatures and initial value signatures. If the version conflicts
cannot be eliminated due to other dependencies, please contact the author of the know-how
protected block in order to obtain a compatible approved version.
S7-1200/1500 F-CPUs
Signature of the know-how protected F-block
Safety system version when setting up the know-how protection
Versions of all the used versioned LAD/FBD instructions
Signatures of all called F-blocks
System acceptance
11.5 Compliance of the know-how protected F-blocks used in the safety program with their safety documentation.
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 367
During a system acceptance test, you have to carry out the following checks using the safety
summary:
The signature of each know-how protected F-block listed in the safety summary in the
section "Know-how protected F-blocks in the safety program" must agree with the
signature documented by the author.
The safety system version of each know-how protected F-block listed in the safety
summary under "Know-how protected F-blocks in the safety program" must match the
versions in Annex 1 of the Report for the TÜV Certificate.
The versions of the versioned LAD/FBD instructions of each know-how protected F-block
listed in the safety summary in the section "Know-how protected F-blocks in the safety
program" must correspond to the versions documented by the author or must be
functionally identical with these.
The signatures of the F-blocks called in each know-how protected F-block listed in the
safety summary in the section "Know-how protected F-blocks in the safety program" must
correspond to the signatures (of the called F-blocks) documented by the author.
In case of differences, set the documented (or functionally identical) versions and use the F-
blocks with the documented signatures. If the version conflicts cannot be eliminated due to
other dependencies, please contact the author of the know-how protected block in order to
obtain a compatible approved version.
System acceptance
11.6 Completeness and correctness of the hardware configuration
SIMATIC Safety - Configuring and Programming
368 Programming and Operating Manual, 10/2018, A5E02714440-AH
11.6
Completeness and correctness of the hardware configuration
Introduction
The hardware configuration is an essential component of the project to be accepted. With
the configuration of the hardware, you have set properties that can influence the safety of
signals. You must document these settings with the safety summary to prove that you fulfill
the safety requirements for your application.
The section "Hardware configuration of F-I/O" is available in the safety summary for this.
This section consists of several tables:
A table with information about the F-CPU and the ranges of F-destination addresses used
and of the Central F-source address of the F-CPU.
An overview table with the F-I/O used.
A table for each F-I/O with information about the F-I/O and all parameters of the F-I/O
with the configured values.
Check whether only authorized users have the "F-admin" right in the
Safety Administration
Editor
or in the standard printout of the project data.
Note
Note that you will find F
-I/O that you address via safety-related I-slave-slave communication
in the safety summary of the
I-slave F-CPU and not in the F-CPU of the assigned DP
master.
The safety summary of the F
-CPU of the DP master includes a note for this F-I/O in the
overview table indicating that the F
-I/O is not assigned to this F-CPU.
Note
When using shared devices:
Note that you will find F
-
I/O that you address in a shared device in the safety summary of the
F
-CPU of the IO controller to which it is assigned.
The safety summary of the F
-CPUs of the other IO controllers between which the shared
device is divided, in
cludes a note in the overview table for this F-I/O that it is not assigned to
this F
-CPU.
Procedure for checking that the hardware configuration is complete
Ensure that all configured F-I/O are included in the safety summary. Also make sure that
there is no F-I/O that you have not configured as belonging to this F-CPU.
Note
If configuration control (option handling) is used, the safety summary must contain all the F
-
I/O devices of the maximum configuration. The following checks are to be carried out f
or al
the F
-I/Os of the maximum configuration.
System acceptance
11.6 Completeness and correctness of the hardware configuration
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 369
Procedure for checking the correctness of the hardware configuration using the safety summary
To check the hardware configuration for correctness, proceed as follows:
1. Check in the “F-hardware configuration“ section to verify the uniqueness of the
PROFIsafe addresses.
Please see sections PROFIsafe addresses for F-I/O of PROFIsafe address type 1
(Page 68) or PROFIsafe addresses for F-I/O of PROFIsafe address type 2 (Page 70),
Peculiarities when configuring fail-safe GSD based DP slaves and fail-safe GSD based
I/O devices (Page 77) and Recommendation for PROFIsafe address assignment
(Page 65).
Check if the "Central F-source address" parameter of the individual F-CPUs differs
network-wide. F-CPUs to which solely F-IOs of the PROFIsafe address type 1 are
assigned do not have to be considered during the check.
For F-I/Os of PROFIsafe address type 1 check whether the F-destination addresses
comply with the following warning:
WARNING
F-I/Os of PROFIsafe address type 1 are uniquely addressed by their F-destination
address (e.g. with the switch setting on the address switch).
The F-destination address (and therefore also the switch setting on the address
switch) of the F-I/O must be unique network-wide* and CPU-wide** (system-wide)
for
the entire
F-I/O. The F-I/O of PROFIsafe address type 2 must also be considered.
(S051)
* A network consists of one or more subnets. "Network-wide" means beyond the
boundaries of the subnet. In PROFIBUS, a network includes all nodes accessible via
PROFIBUS DP. In PROFINET IO, a network includes all nodes accessible via
RT_Class_1/2/3 (Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP
(IP, Layer 3).
** "CPU-wide" means all F-I/Os assigned to an F-CPU: Central F-I/O of this F-CPU as
well as F-I/Os for which the F-CPU is DP master/IO controller and assigned F-I/O in a
shared device. An F-I/O that is addressed using I-slave-slave communication is
assigned to the F-CPU of the I-slave and not to the F-CPU of the DP master / IO
controller.
For F-I/Os of PROFIsafe address type 2 check whether the F-destination addresses
comply with the following warning:
System acceptance
11.6 Completeness and correctness of the hardware configuration
SIMATIC Safety - Configuring and Programming
370 Programming and Operating Manual, 10/2018, A5E02714440-AH
WARNING
FI/O of PROFIsafe address type 2 is uniquely addressed using a combination of F-
source address ("Central F-source address" parameter of the assigned F-CPU) and
F-destination address.
The combination of F-source address and F-destination address for each F-I/O must
be unique network-wide* and CPU-wide** (system-wide). In addition, the F-
destination address may not be occupied by F-I/O of PROFIsafe address type 1.
To ensure that addresses are unique across F-CPUs for supported configurations
(Page 66), you need to ensure that the "Central F-source address" parameter of all
F-CPUs is unique network-wide*. This is achieved through different settings for the
"Central F-source address" parameter of the F-CPUs.
(S052)
* A network consists of one or more subnets. "Network-wide" means beyond the
boundaries of the subnet. In PROFIBUS, a network includes all nodes accessible via
PROFIBUS DP. In PROFINET IO, a network includes all nodes accessible via
RT_Class_1/2/3 (Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP
(IP, Layer 3).
** "CPU-wide" means all F-I/Os assigned to an F-CPU: Central F-I/O of this F-CPU as
well as F-I/Os for which the F-CPU is DP master/IO controller and assigned F-I/O in a
shared device. An F-I/O that is addressed using I-slave-slave communication is
assigned to the F-CPU of the I-slave and not to the F-CPU of the DP master / IO
controller.
fail-safe GSD based DP slaves / GSD based I/O devices check whether the
PROFIsafe addresses comply with the following warning:
WARNING
Check the documentation for your fail-safe GSD based DP slaves / GSD based I/O
devices to find out the valid PROFIsafe address type. If you do not find the
necessary information, assume PROFIsafe address type 1. Proceed as described
under PROFIsafe addresses for F-I/O of PROFIsafe address type 1 (Page 68) or
PROFIsafe addresses for F-I/O of PROFIsafe address type 2 (Page 70).
Set the F-source address according to the manufacturer specifications for fail-safe
DP standard slaves / fail-safe IO standard devices. If the F-source address needs to
correspond to the "Central F-source address" parameter of the F-CPU (PROFIsafe
address type 2), you will find the latter in the "Properties" tab of the F-CPU. In this
case, also check in the safety summary that the value of the F-CPU for the "Central
F-source address" parameter matches the value of the F-source address of the fail-
safe GSD based DP slave / fail-safe GSD based I/O device.
(S053)
System acceptance
11.6 Completeness and correctness of the hardware configuration
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 371
2. Check the safety-related parameters (including F-monitoring time or F_WD_Time) of all
configured F-I/O.
You can find these parameters in the "Hardware configuration of F-I/O" section in the
detailed tables for the F-I/O.
The table consists of two parts:
The left part contains the parameters which refer to the F-I/O itself ("Module data").
The right part contains the parameters of the individual channels ("Channel
parameters")
These parameters must be set as prescribed by the safety requirements of your
application.
When using fail-safe GSD based DP slaves/GSD based I/O devices, note the relevant
documents for the possible additional safety-related (technical) parameters.
Note
F
-I/O that are to be assigned the same safety-related parameters (except for PROFIsafe
addresses) can be copied during configuration. Except for the PROFIsafe addresses, you
no longer have to check the safety
-related parameters individually. It is sufficient to
compare the "Signature
of F-parameters (without addresses)" in the "Hardware
configuration of the F
-I/O" section in the overview table. This also applies to fail-
safe GSD
based DP slaves/GSD based I/O devices without i
-parameters. For GSD based DP
slaves / GSD based I/O devices
with i-parameters, it may be that "F-parameter signature
(w/o addresses)" does not match, even though all safety
-related parameters, except for
the PROFIsafe addresses, do match. In this case, you need to compare all safety
-
related
parameters.
Exception:
F
or F-I/Os that do not support the "RIOforFA-Safety" profile, you also need to compare
the "Behavior after channel fault" parameter, if any, for "F
-parameter signature (w/o
addresses)".
3. Check whether the article numbers of the F-I/O in the safety summary correspond to the
article numbers of the actual F-I/O in the system. If the article numbers are different, the
existing F-I/O must be spare-part-compatible to the F-I/O listed in the safety summary.
System acceptance
11.6 Completeness and correctness of the hardware configuration
SIMATIC Safety - Configuring and Programming
372 Programming and Operating Manual, 10/2018, A5E02714440-AH
4. For non-supported configuration, please see Configurations supported by the SIMATIC
Safety F-system (Page 66).
WARNING
Please note the following with configurations that are not included in supported
configurations:
Make sure that the F-I/O of this configuration appears in the safety summary and that
an F-I/O DB has been created for it. Otherwise, you cannot use the F-I/O in this
configuration. (Contact Customer Support.)
For F-I/Os in the PROFINET IO environment**, you must check the PROFIsafe
operating mode parameter (F_Par_Version) against the safety summary to make
sure that it is correct. V2 mode must be set in the PROFINET IO environment. F-I/O
which only support V1 mode may not be used in the PROFINET IO environment.
You must ensure that PROFIsafe address assignment is unique CPU-wide* and
network-wide***:
Check the correctness of the PROFIsafe addresses with the help of the safety
summary.
Use the safety summary to check that the F-source address corresponds to the
"Central F-source address" parameter of the F-CPU for F-I/O of PROFIsafe
address type 2.
For F-I/O of PROFIsafe address type 1 or if you cannot set the F-source address
in accordance with the "Central F-source address" parameter of the F-CPU, you
will have to ensure the uniqueness of the PROFIsafe address solely by assigning
a unique F-destination address.
You must check the uniqueness of the F-destination address individually for each F-
I/O based on the safety summary in a configuration that is not supported.
(S050)
* "CPU-wide" means all F-I/Os assigned to an F-CPU: Central F-I/O of this F-CPU as well
as F-I/Os for which the F-CPU is DP master/IO controller and assigned F-I/O in a shared
device. An F-I/O that is addressed using I-slave-slave communication is assigned to the
F-CPU of the I-slave and not to the F-CPU of the DP master / IO controller.
** The F-I/O is located in the "PROFINET IO environment" if at least part of safety-related
communication with the F-CPU takes place via PROFINET IO. If the F-I/O is connected
via I-slave-slave communication, also keep in mind the communication line to the DP
master/IO controller.
*** A network consists of one or more subnets. "Network-wide" means beyond the
boundaries of the subnet. In PROFIBUS, a network includes all nodes accessible via
PROFIBUS DP. In PROFINET IO, a network includes all nodes accessible via
RT_Class_1/2/3 (Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP
(IP, Layer 3).
System acceptance
11.6 Completeness and correctness of the hardware configuration
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 373
5. Check that only authorized persons have the "F-admin" right.
WARNING
The "F-admin" authorization for Web server without password protection (user
"Everybody" or "Everyone") is only intended for test purposes, maintenance, etc. This
means only when the system is not in productive operation. In this case, you must
ensure the safety of the system through other organizational measures, for example
through protected access to certain areas.
Before you transition into productive operation, you must remove the "F-admin" right for
the user "Everyone".
Only authorized personnel may have access to the password of the Web server user
with the "F-admin" right. After downloading the hardware configuration, check whether
only permitted users of the Web server have the "F-admin" right on the F-CPU. To do
so, use the online view of the
Safety Administration Editor
(see also Safety
Administration Editor (Page 81)).
Saving the login file and the password of the Web server in the browser is only
permitted when use by unauthorized persons is prevented through other organizational
measures (e.g. access protection to the PG/PC).
(S064)
System acceptance
11.7 Correctness and completeness of the communication configuration
SIMATIC Safety - Configuring and Programming
374 Programming and Operating Manual, 10/2018, A5E02714440-AH
11.7
Correctness and completeness of the communication configuration
Introduction
Safety-related communication is based on the mechanisms of the standard communication
of
STEP 7
.
To ensure that errors which standard communication does not discover are detected, safety-
related communication connections between F-CPUs are secured. Further parameters are
required for this, which you have to document and check on acceptance.
For this purpose, the "Block parameters for safety-related CPU-CPU-communication" and
"Overview of communication via Flexible F-Link" sections are available in the safety
summary. The section "Block parameters for safety-related CPU-CPU-communication"
contains up to two tables (for communication via PROFIBUS DP or PROFINET IO and for
communication via S7 connections). The section "Overview of communication via Flexible
F-Link" contains a table with an overview of the connection configurations and a
"Communication via Flexible F-Link for UDT" table for each used F-compliant PLC data type
(UDT).
Procedure for testing for correctness of the communication via Flexible F-Link
To check the communication via Flexible F-Link for correctness, follow these steps:
Check your connection parameter assignment in the table "Overview of communications
via Flexible F-Link". If you have copied communication relationships, ensure the
uniqueness of the UUID.
Check the table(s) "Overview of communications via Flexible F-Link" for each
F-communication relationship to ensure that the offsets of the elements of the F-
compliant PLC data types (UDT) match regarding send and receive data within the safety
message frame.
Procedure for testing for correctness of the communication configuration
To check the communication configuration for correctness, proceed as follows:
In the "Safety-related CPU-CPU communication via PROFIBUS DP or PROFINET IO"
table, check to determine whether you have assigned a unique DP_DP_ID input network-
wide* for all safety-related communication connections (e.g., master-master, master-
I-slave and IO controller-IO controller communication).
In the "Safety-related CPU-CPU communication via S7 connections" table, check to
determine whether you have assigned a unique R_ID input network-wide* for all safety-
related communication via S7 connections.
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet. In PROFIBUS, a network includes all nodes accessible via PROFIBUS DP. In
PROFINET IO, a network includes all nodes accessible via RT_Class_1/2/3
(Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP (IP, Layer 3).
System acceptance
11.8 Identity of online and offline program
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 375
11.8
Identity of online and offline program
Once you have checked all properties of the offline safety program you must ensure that the
safety program is identical on the F-CPU on which it is supposed to be run.
1. Connect online with the F-CPU. If multiple F-CPUs can be reached over a network
(e.g. Industrial Ethernet) by the programming device / PC, you have to ensure that you
are connected with the correct F-CPU. For example with "Online & diagnostics" > "Online
accesses " > "Flash LED".
2. Open the
Safety Administration Editor
.
3. Check whether the online and offline F-collective signatures match the F-collective
signatures from the safety summary.
4. In the "General" area, check the information for
F-collective signature online
F-collective signature offline
Information on whether safety programs are consistent online and offline.
Version check view
Use the output information to check which situation you are dealing with and, if
necessary, execute the recommended measure:
collective F-
signatures
online/offline
Consistency
online to
offline
Statement
Measure
not relevant The safety programs are differ-
ent.
Ensure that you are
connected with the de-
sired F-CPU.
Download the safety
program to the F-CPU.
The safety programs are identi-
cal but different versions of F-
blocks are used.
The safety program must be
downloaded to the F-CPU
for the latest versions to
become effective.
The safety programs are identi-
cal.
None
Keep in mind that only a change comparison will provide reliable information as to whether
the safety programs are identical. The display of signatures is used for quick identification of
changes.
System acceptance
11.9 Other characteristics
SIMATIC Safety - Configuring and Programming
376 Programming and Operating Manual, 10/2018, A5E02714440-AH
11.9
Other characteristics
Introduction
In addition, you must check a few more characteristics that are also relevant for the
acceptance of the project.
Validity check for data transfer from the standard program to the safety program
Check to determine whether a validity check was programmed for all data transferred from
the standard user program to the safety program. For this purpose, the "Data from the
standard user program" section lists all tags of the standard user program that you are
reading in the safety program. Tags of the safety program that you are writing in the safety
program are not listed here because a plausibility check is not required for them. For more
information, refer to the S015 warning in section "Data Transfer from Standard User Program
to Safety Program (Page 197)".
Checking the program version
Check whether the version of
STEP 7 Safety
used to create the summary (in the footer of
the printout) is as least as high as the version used to compile the safety program. The latter
version can be found in the "General information" section of the safety summary under
"Used Versions". Both versions must be listed in Annex 1 of the Report for the TÜV
certificate.
Ability to disable safety mode
Make sure that safety mode cannot be disabled. For information about this, refer to section
"General information" under "Safety program settings". This setting ensures that the safety
mode of the safety program cannot be disabled inadvertently. For more information, refer to
the S027 warning in section "Disabling safety mode (Page 344)".
Access protection
Check in the "General information" section under "Access protection" to determine whether
the setting for access protection is permitted. Note the following warning.
System acceptance
11.9 Other characteristics
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 377
Otherwise, the project must not be accepted, because the safety program in the F-CPU is
not protected against unauthorized accesses.
WARNING
(S7-300, S7-400) In safety mode, access with the CPU password must not be authorized
during changes to the standard user program as this would also allow change
s to the safety
program. To rule out this possibility, you must configure the protection level "Write
protection for fail-safe blocks" and configure a password for the F-CPU. If only one person
is authorized to change the standard user program and the safety program, the protection
level "Write protection" or "Read/write protection" should be configured so that other
persons have only limited access or no access at all to the entire user program (standard
and safety programs).
(S001)
WARNING
(S7-1200, S7-1500) In safety mode, the safety program must be password-protected. For
this purpose, configure at least the protection level "Full access (no protection)" and assign
a password under "Full access incl. fail-safe (no protection)". This protection level only
allows full access to the standard user program, not to F-blocks.
If you select a higher protection level, for example to protect the standard user program,
you must assign an additional password for "Full access (no protection)".
Assign different passwords for the individual protection levels.
(S041)
System acceptance
11.10 Acceptance of Changes
SIMATIC Safety - Configuring and Programming
378 Programming and Operating Manual, 10/2018, A5E02714440-AH
11.10
Acceptance of Changes
Introduction
In general, you can adopt the same approach for the acceptance of changes as the initial
acceptance (see Overview of System Acceptance (Page 361)).
You must check the complete safety program including the safety-related HW configuration
for changes.
WARNING
In the case of acceptance of changes, you must check whether the intended changes were
made correctly and completely.
You must also check whether unintentional changes may have been made at another
location (for example, I/O or instructions that were added).
(S072)
To avoid the acceptance of the entire system in case of negligible changes,
STEP 7 Safety
helps you to identify those parts of your safety program that have changed.
For an acceptance of changes, it is sufficient to check the following:
Checking the changed or newly added F-blocks.
Checking the changed or newly added instructions and F-system blocks.
Checking the safety-related parameters of the changed or newly added F-I/O.
Checking the structure of the safety-related HW configuration (e.g. slot positions or start
addresses of the F-I/Os).
Checking the changed communication connection with Flexible F-Link.
You then perform a function test of the F-blocks/F-I/Os affected by the changes.
System acceptance
11.10 Acceptance of Changes
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 379
Check that the changes have no impact on the unchanged parts of safety-related project
data, in particular for deleted F-blocks or deleted F-I/O.
Note
Acceptance of changes is not possible after CPU migration.
WARNING
When you make changes in which the assignment of input/output addresses and wiring can
change, then you must perform a wiring test (Page 347).
Examples for such changes are:
Adding F-I/O
Changing the start address of F-I/O
Changing the slot position of F-I/O
Changing
the rack
the slave/device address
the PROFIBUS DP/PROFINET IO subnet
the IP address
the device name
(S071)
Detection of changes in the safety-related project data
You need two TIA projects to identify relevant changes:
Reference project: Contains the initially accepted project data. They are the starting point
for the upcoming comparison.
Project to be accepted: Contains the current safety-related project data. It is the result of
the reference project and the changes made in it.
To detect changes you have to compare the safety-related project data from the reference
project with the data of the project to be accepted.
The F-collective signature is a quick first step to determine whether relevant changes have
been made. If the signature has changed, relevant changes are present in the safety-related
project data.
You can now use the F-SW collective signature, the F-HW collective signature and the F-
communication address signature to narrow down whether these changes are contained in
the safety program (F-SW collective signature changed) and/or in the safety-related project
data (F-HW collective signature) and/or in the communication data (with Flexible F-Link, F-
communication address signature).
System acceptance
11.10 Acceptance of Changes
SIMATIC Safety - Configuring and Programming
380 Programming and Operating Manual, 10/2018, A5E02714440-AH
Detection of changes in the safety program
A quick possibility to detect changes in the safety program is the comparison of the F-SW
collective signature of the safety-related project data in the reference project with the F-SW
collective signature in the safety-related project data in the project to be accepted. If they
differ from each other, this means that there are changes in the safety program which need
to be validated and, if necessary, accepted.
To localize changes in the safety program, perform an offline-offline comparison between the
changed safety program and the accepted safety program (see Comparing Safety Programs
(Page 339)). Use filter setting "Compare only F-blocks relevant for certification". This limits
the output of the comparison to exactly those F-blocks that must be considered for the
acceptance of changes.
WARNING
Make sure that the comparison criterion "Safety" is enabled so that the criteria relevant for
an acceptance of changes are taken into consideration in the comparison.
(S069)
By disabling the remaining comparison criteria, you can deselect those differences that are
irrelevant for the acceptance of changes (e.g. time stamp).
The status of the comparison helps you to identify which F-blocks were changed.
Detection of changes in the safety-related hardware configuration
A quick possibility to detect changes in the safety-related hardware configuration is the
comparison of the F-HW collective signature of the safety-related project data in the
reference project with the F-HW collective signature of the safety-related project data in the
project to be accepted. If they differ from each other, this means that there are changes in
the safety-related hardware configuration which need to be validated and, if necessary,
accepted.
If the F-HW collective signature has changed and all F-I/O devices are unchanged, this
indicates that safety-related parameters of the F-CPU have changed, or that the structure of
the safety-related hardware configuration has changed, for example, slot positions.
There are two possible ways for localizing safety-related changes in the safety-related
hardware configuration:
Comparison in the comparison editor
Comparison based on two safety summaries
System acceptance
11.10 Acceptance of Changes
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 381
Comparison in the comparison editor
If you have access to the reference project, you can also detect the changes in the safety-
related hardware configuration through an offline-offline comparison of the changed F-CPU
with the accepted F-CPU (see Comparing Safety Programs (Page 339)). Both projects must
be consistent and compiled.
1. Navigate in the comparison result to the "System blocks > STEP 7 Safety > F-I/O DBs"
folder. All data blocks listed in this folder are F-I/O-DBs and are each assigned to an
F-I/O.
If the F-I/O-DBs in the comparison result are identical, this means that the safety-
related configuration of the assigned F-I/O was also not changed. Standard-
parameters may have changed.
If the F-I/O-DBs in the comparison result are not identical, this means that the safety-
related configuration of the assigned F-I/O was also changed.
If the F-I/O DBs in the comparison result are marked as "not existing", associated
F-I/O devices may have been deleted or added or the name or start addresses of the
F-I/O devices have been changed. In this case you can find the assignment of an
F-I/O DB to a specific F-I/O in the safety summary under "Hardware configuration of
F-I/O".
2. If you have found changed F-I/O, you can check the changed parameters in the safety
summary as described below.
Comparison based on two safety summaries
Carry out a comparison based on two safety summaries as follows:
1. In the section "Hardware configuration of the F-I/O" compare the start addresses (I/O
addresses), the parameter "Behavior after channel fault" and the slot of the F-I/O.
2. In the overview table of the utilized F-I/O in the "Hardware configuration of F-I/O" section,
compare the parameter CRCs of the F-I/O with those in the safety summary of the
accepted F-CPU.
If the "Parameter signature (without addresses)" is different for an F-I/O, this indicates
the existence of a safety-related change of safety-related parameters of the F-I/O. In
addition, the PROFIsafe addresses may also be changed.
In this case, in the “F-I/O hardware configuration“ section check the safety-related
parameters of the F-I/O and verify the uniqueness of the PROFIsafe addresses.
If the "Parameter signature (w/o addresses) is identical, it is possible that only the
PROFIsafe addresses were changed.
In this case it is sufficient to verify the uniqueness of the PROFIsafe addresses.
Check as described in section “Completeness and correctness of the hardware configuration
(Page 368)“.
System acceptance
11.10 Acceptance of Changes
SIMATIC Safety - Configuring and Programming
382 Programming and Operating Manual, 10/2018, A5E02714440-AH
Detecting changes in the communication with Flexible F-Link
A quick possibility to detect changes in the configuration of the communication with Flexible
F-Link, the comparison of the F-communication address signature of the safety-related
project data in the reference project with the F-communication address signature of the
safety-related project data in the project to be accepted. If they differ from each other, this
means that there are changes in the configuration of the communication with Flexible F-Link,
which need to be validated and, if necessary, accepted.
To localize changes in the configuration of the communication with Flexible F-Link, compare
the table "Overview of communications via Flexible F-Link" of the reference project in the
respective safety summary with the one of the project to be accepted.
See also
Accessing tags of the F-I/O DB (Page 174)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 383
Operation and Maintenance
12
12.1
Notes on Safety Mode of the Safety Program
Introduction
Pay attention to the following important notes on safety mode of the safety program.
Use of simulation devices/simulation programs
WARNING
Use of simulation devices/simulation programs in plants
If you operate simulation devices or simulation programs that generate safety message
frames, for example, based on PROFIsafe, and make them available to the SIMATIC
Safety F-system via the bus system (such as PROFIBUS DP or PROFINET IO), you must
ensure the safety of the F-system using organizational measures, such as operational
monitoring and manual safety shutdown.
Note, for example, that a protocol analyzer is not permitted to perform any function that
reproduces recorded message frame sequences with correct time behavior.
S7-PLCSIM
version < 15.1 or
S7-PLCSIM Advanced version
< 2.0 SP1 and safety system
version < 2.2
If you use the
S7-PLCSIM
(Page 343) to simulate safety programs, the measures
mentioned above are not necessary because S7-PLCSIM cannot establish an online
connection to a real component.
S7-PLCSIM
version ≥ 15.1 or
S7-PLCSIM Advanced
version ≥ 2.0 SP1 or safety system
version ≥ 2.2
You must ensure the safety of the F-system with organizational measures, for example,
through operation monitoring and manual safety shutdown.
In addition, the loading of a safety program with Safety System version 2.2 and higher onto
an
S7-PLCSIM
is only permissible as of
S7-PLCSIM
V15.1 or
S7-PLCSIM Advanced
V2.0
SP1.
(S030)
Note
For an
S7-PLCSIM
before V15.1 or
S7-PLCSIM Advanced
before V2.0 SP1 and a Safety
System version
2.2 and higher, the safety program changes to STOP and a corresponding
diagnostics event is issued.
Operation and Maintenance
12.1 Notes on Safety Mode of the Safety Program
SIMATIC Safety - Configuring and Programming
384 Programming and Operating Manual, 10/2018, A5E02714440-AH
Switching F-CPU to STOP mode
WARNING
STOP via programming device/PC, mode switch, communication function or "STP"
instruction
Initiating STOP by means of programming device/PC operation, mode switch,
communication function or "STP" instruction as well as maintaining the STOP state is not
safety-oriented. This STOP state can be easily (and unintentionally) be revoked by
programming device/PC operation.
When an F-CPU is switched from STOP to RUN mode, the standard user program starts
up in the usual way. When the safety program is started up, all F-DBs are initialized with
the values from the load memory - as is the case with a cold restart. This means that saved
error information is lost. The F-system automatically reintegrates the F-I/O.
If your process does not allow such a startup, you must program a restart/startup protection
in the safety program: The output of process data must be blocked until manually enabled.
This enable must not occur until it is safe to output process data and faults have been
corrected (see Programming startup protection (Page 155)).
(S031)
Operation and Maintenance
12.1 Notes on Safety Mode of the Safety Program
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 385
CRC error in safety-related communication
Note
CRC error in safety-related communication
If you observe that an F
-CPU requests manual acknowledgement of a CRC error more than
once within the space of 100 hours, and this occurs repeatedly, check whether the
PROFINET or PROFIBUS installation guidelines have been followed.
There is a CRC error if:
The ACK_REQ tag of the F-I/O DB is set and the DIAG tag of the F-I/O DB (bit 2 or bit 6)
indicates CRC errors
or
A CRC error is entered in the diagnostic buffer of the F-CPU
In this case, the failure probability values
(
https://support.industry.siemens.com/cs/ww/en/view/109481784) (PFDavg/PFH) for safety-
related communication no longer apply.
Information on installation guidelines for PROFINET and PROFIBUS can be found in:
PROFIBUS Installation Guidelines (www.profibus.com/PBInstallationGuide)
PROFIBUS Interconnection Technology
(http://www.profibus.com/nc/downloads/downloads/profibus-interconnection-
technology/display/)
PROFINET Installation Guidelines (www.profibus.com/PNInstallationGuide)
PROFINET Cabling and Interconnection Technology
(http://www.profibus.com/nc/downloads/downloads/profinet-cabling-and-interconnection-
technology/display/)
PROFIsafe Environment Requirements (www.profibus.com/PROFIsafeRequirements)
When your review indicates that the configuration guidelines for PROFIBUS and PROFINET
have been met, contact Customer Support.
Operation and Maintenance
12.2 Replacing Software and Hardware Components
SIMATIC Safety - Configuring and Programming
386 Programming and Operating Manual, 10/2018, A5E02714440-AH
12.2
Replacing Software and Hardware Components
Replacement of software components
When replacing software components on your programming device or PC, e.g. with a new
version of
STEP 7
, you must adhere to the information regarding upward and downward
compatibility in the documentation and readme files for these products (e.g.
STEP 7 Safety
).
When replacing
STEP 7 Safety
, check whether the version of
STEP 7 Safety
is listed in
Annex 1 of the Report for the TÜV certificate.
Replacement of hardware components
Hardware components for SIMATIC Safety (F-CPU, F-I/O, batteries, etc.) are replaced in the
same way as in standard automation systems.
Replacement of S7-1500 F software Controllers
WARNING
After replacing a CPU module (e.g. new PC with data storage medium of old PC) or
replacement of the data storage medium (e.g. data storage medium with safety program 1
is replaced with data storage medium with safety program 2), you must use the Panel to
check if the correct collective F-signature is displayed or whether a program identification is
carried out.
(S066)
Removing and inserting F-I/O during operation
If removing and inserting is possible for standard I/O during operation, it is also possible for
the respective F-I/O. However, be aware that replacing an F-I/O module during operation
can cause a communication error in the F-CPU.
You must acknowledge the communication error in your safety program in the ACK_REI tag
of the F-I/O DB (Page 165) or, alternatively, by using the "ACK_GL (Page 487)" instruction.
Without an acknowledgment, the F-I/O will remain passivated.
CPU firmware update
Check of the CPU operating system for F-approval: When using a new CPU operating
system (firmware update), you must check to see if the CPU operating system you are using
is approved for use in an F-system.
The minimum CPU operating system versions with guaranteed F-capability are specified in
the appendix of the Certificate. This information and any notes on the new CPU operating
system must be taken into account.
Operation and Maintenance
12.2 Replacing Software and Hardware Components
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 387
Firmware update for interface module
When using a new operating system for an interface module, e.g. IM 151-1 HIGH FEATURE
ET 200S (firmware update), you must observe the following:
If you have selected the "Activate firmware after update" option for the firmware update (see
Help on
STEP 7
, "Online & Diagnostics"), the IM will be automatically reset following a
successful download operation and will then run on the new operating system. Note that the
firmware update for interface modules during operation generates a communication error in
the F-CPU.
You must acknowledge the communication error in your safety program in the ACK_REI tag
of the F-I/O DB (Page 165) or, alternatively, by using the "ACK_GL (Page 487)" instruction.
Without an acknowledgment, the F-I/O will remain passivated.
Preventive maintenance (proof test)
Proof test for complex electronic components generally means replacement with new,
unused components.
PFDavg and PFH values for S7-300/400 F-CPUs and F-I/O
You will find a list of the failure probability values (PFD avg, PFH values) for components that
can be used in SIMATIC Safety on the Internet.
PFDavg and PFH values for S7-1200/1500 F-CPUs
Below are the probability of failure values (PFDavg, PFH values) for S7-1200/1500 F-CPUs
with a service life of 20 years and an MTTR of 100 hours:
Operation in low demand mode
low demand mode
According to IEC 61508:2010:
PFDavg = Average probability of a dangerous failure on
demand
Operation in high demand or continuous mode
high demand/continuous mode
According to IEC 61508:2010:
PFH = Average frequency of a dangerous failure [h-1]
< 2E-05
< 1E-09
Operation and Maintenance
12.2 Replacing Software and Hardware Components
SIMATIC Safety - Configuring and Programming
388 Programming and Operating Manual, 10/2018, A5E02714440-AH
PFDavg and PFH values for safety-related communication
Below you will find the failure probability values (PFDavg, PFH values) for safety-related
communication:
Operation in low demand mode
low demand mode
According to IEC 61508:2010:
PFDavg = Average probability of a dangerous failure on
demand
Operation in high demand or continuous mode
high demand/continuous mode
According to IEC 61508:2010:
PFH = Average frequency of a dangerous failure [h-1]
< 1E-05*
< 1E-09*
*Note on S7-300/400 F-CPUs:
The PFH value is valid under the assumption that a maximum of 100 F-I/Os are involved in a
safety function. If you use more than 100 F-I/Os, you have to also add 4E-12 per F-I/O for
the safety function.
The PFDavg value is valid for a service life of 20 years and under the assumption, that a
maximum of 25 F-I/Os are involved in a safety function. If more than 25 F-I/OS are used, you
need to add 3.5E-7 per F-I/O for this safety function.
Operation and Maintenance
12.3 Guide to diagnostics (S7-300, S7-400)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 389
12.3
Guide to diagnostics (S7-300, S7-400)
Introduction
Here you find a compilation of diagnostic capabilities that can be evaluated for your system
when an error occurs. Most of the diagnostic capabilities are the same as those in standard
automation systems. The sequence of steps represents a recommendation.
Steps for evaluating diagnostic capabilities
The following table shows the steps you take to evaluate diagnostic capabilities.
Step
Procedure
Reference
1
Evaluate LEDs on the hardware (F-CPU, F-I/O):
BUSF LED on the F-CPU: Flashes when a communication error occurs on
PROFIBUS DP/PROFINET IO;
On if a programming error occurs when OB 85 and OB 121 are programmed (e.g. in-
stance DB is not loaded)
STOP LED on the F-CPU: illuminates when the F-CPU is in STOP mode
Fault LEDs on the F-I/O: e.g. SF-LED (group error LED) on if any fault occurs in the
individual F-I/O
Manuals for F-CPU and
F-I/O
2
Evaluate diagnostic buffer of the modules:
You read the diagnostic buffer of a module (F-CPU, F-I/O, CP) in its online and diagnostic
view in the "Diagnostic buffer" group under the "Online & Diagnostics" folder.
Help on STEP 7 and
manuals for the F-CPU
and
F-I/O
3
Evaluate stacks of the F-CPU:
when the F-CPU is in STOP mode, read the following successively:
Block stack: Check whether STOP mode of the F-CPU was triggered by an F-block of
the safety program
Interruption stack
Local data stack
Help on STEP 7
Operation and Maintenance
12.4 Guide to diagnostics (S7-1500)
SIMATIC Safety - Configuring and Programming
390 Programming and Operating Manual, 10/2018, A5E02714440-AH
Step
Procedure
Reference
4
Evaluate diagnostic tag of the F-I/O DB using testing and commissioning functions, by
means of an operator control and monitoring system, or in the standard user program:
Evaluate the DIAG tag in the F-I/O DB
F-I/O access (Page 157)
5
Evaluate diagnostic outputs of the instance DBs of instructions using testing and commis-
sioning functions, using an operator control and monitoring system, or in the standard
user program:
Evaluate the following for MUTING, EV1oo2DI, TWO_H_EN, MUT_P, ESTOP1,
FDBACK, SFDOOR in the assigned instance DB:
Output DIAG
Evaluate the following for SENDDP or RCVDP in the assigned instance DB:
Output RET_DPRD/RET_DPWR
Output DIAG
Evaluate the following for SENDS7 or RCVS7 in the assigned instance DB:
Output STAT_RCV
Output STAT_SND
Output DIAG
Instructions
Tip on RET_DPRD/RET_DPWR
The diagnostic information of the RET_DPRD/RET_DPWR outputs of the SENDDP or
RCVDP instructions corresponds to the diagnostic information of the RETVAL return value of
the "DPRD_DAT" and "DPWR_DAT" instructions. You can find the description in the help on
STEP 7
for the "DPRD_DAT" and "DPWR_DAT" instructions.
Tip: STAT_RCV and STAT_SND
The diagnostic information of the STAT_RCV output of the SENDS7 or RCVS7 instructions
corresponds to the diagnostic information of the STATUS output of the "URCV" instruction.
The diagnostic information of the STAT_SND output of the SENDS7 or RCVS7 instructions
corresponds to the diagnostic information of the STATUS output of the "USEND" instruction.
You can find the description in the help on
STEP 7
for the instruction "UCRV" or "USEND" .
12.4
Guide to diagnostics (S7-1500)
Detailed information on diagnostics for an S7-1500 F-CPU can be found in the Diagnostics
(http://support.automation.siemens.com/WW/view/en/59192926) function manual.
12.5
Guide to diagnostics (S7-1200)
Detailed information on diagnostics for an S7-1200 F-CPU can be found in the S7-1200
Functional Safety manual (http://support.automation.siemens.com/WW/view/en/104547552).
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 391
13
Overview of instructions for the safety program
When programming an F-block, you can find all instructions available for programming an
F-block in LAD or FBD with the configured F-CPU in the "Instructions" task card.
In addition to the instructions that are familiar to you from programming a standard block,
there are also special safety functions, e.g., for two-hand monitoring, discrepancy analysis,
muting, emergency STOP/emergency OFF, safety door monitoring, and feedback monitoring
and instructions for safety-related CPU-CPU communication.
Note the following
Note
Enable input EN and ena
ble output ENO cannot be connected.
Exception:
(S7
-1200, S7-1500) With the following instructions you can program overflow detection by
connecting the enable output ENO:
ADD: Add (STEP 7 Safety V15.1) (Page 520)
SUB: Subtract (STEP 7 Safety V15.1) (Page 523)
MUL: Multiply (STEP 7 Safety V15.1) (Page 526)
DIV: Divide (STEP 7 Safety V15.1) (Page 529)
NEG: Create twos complement (STEP 7 Safety V15.1) (Page 533)
ABS: Form absolute value (STEP 7 Safety V15.1) (S7-1200, S7-1500) (Page 536)
CONVERT: Convert value (STEP 7 Safety V15.1) (Page 548)
Overview of instructions for the safety
program
13.1 General
SIMATIC Safety - Configuring and Programming
392 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.1
General
13.1.1
LAD
13.1.1.1
New network (STEP 7 Safety V15.1)
Requirement
An F-block is open.
Procedure
To insert a new network, follow these steps:
1. Select the network after which you want to insert a new network.
2. Select the "Insert network" command in the shortcut menu.
Note
If you insert an element into the last empty network of the F
-
block in an LAD program, a new
empty network is automatically inserted below it.
Result
A new empty network is inserted into the F-block.
13.1 General
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 393
13.1.1.2
Empty box (STEP 7 Safety V15.1)
Requirement
A network is available.
Procedure
To insert an LAD instruction into a network using an empty box, follow these steps:
1. Open the "Instructions" task card.
2. Navigate to "Basic instructions > General > Empty box".
3. Use a drag-and-drop operation to move the "Empty box" element to the desired place in
the network.
4. Hover the cursor over the yellow triangle in the top right corner of the empty box.
A drop-down list is displayed.
5. Select the required instruction from the drop-down list.
If the instruction acts as a function block (FB) within the system, the "Call options" dialog
opens. In this dialog, you can create an instance data block for the function block, either as a
single instance or, if necessary, multi-instance, in which data of the inserted instruction are
stored. Once it is created, the new instance data block can be found in the "Program
resources" folder in the project tree under "Program blocks > System blocks". If you have
selected "multi-instance", you can find it in the block interface in the "Static" section.
Result
The empty box is changed to the appropriate instruction. Placeholders are inserted for the
parameters.
13.1.1.3
Open branch (STEP 7 Safety V15.1)
Description
Use branches to program parallel connections with the Ladder Logic (LAD) programming
language. Branches are inserted into the main current path. You can insert several contacts
into the branch, thereby creating a parallel connection from series connections. You can
program complex ladder diagrams in this way.
13.1 General
SIMATIC Safety - Configuring and Programming
394 Programming and Operating Manual, 10/2018, A5E02714440-AH
Requirement
A network is available.
The network contains elements.
Procedure
To insert a new branch in a network, follow these steps:
1. Open the "Instructions" task card.
2. Navigate to "Basic instructions > General > Open branch".
3. Use a drag-and-drop operation to move the element to the desired place in the network.
4. If you want to connect the new branch directly to the power rail, drag the element to the
power rail.
Example
The following figure provides an example of how to use branches:
13.1 General
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 395
13.1.1.4
Close branching (STEP 7 Safety V15.1)
Description
Branches must be closed again at suitable places. If necessary, branches will be arranged
so that they do not cross each other.
Requirement
A branch is available.
Procedure
To close an open branch, follow these steps:
1. Select the open branch.
2. Press and hold down the left mouse button.
A dashed line will appear as soon as the cursor is moved.
3. Drag the dashed line to a suitable place on the network. Permissible connections are
indicated by green lines.
4. Release the left mouse button.
Example
The figure below provides an example of how to use branches:
13.1 General
SIMATIC Safety - Configuring and Programming
396 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.1.2
FBD
13.1.2.1
New network (STEP 7 Safety V15.1)
Requirement
An F-block is open.
Procedure
To insert a new network, follow these steps:
1. Select the network after which you want to insert a new network.
2. Select the "Insert network" command in the shortcut menu.
Note
If you insert an element into the last empty network of the F
-
block in an FBD program, a new
empty network is automatically inserted below
it.
Result
A new empty network is inserted into the F-block.
13.1.2.2
Empty box (STEP 7 Safety V15.1)
Requirement
A network is available.
Procedure
To insert FBD elements into a network using an empty box, follow these steps:
1. Open the "Instructions" task card.
2. Navigate to "Basic instructions > General > Empty box".
3. Use a drag-and-drop operation to move the "Empty box" element to the desired place in
the network.
4. Hover the cursor over the yellow triangle in the top right corner of the empty box.
A drop-down list is displayed.
5. Select the desired FBD element from the drop-down list.
13.1 General
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 397
If the instruction acts as a function block (FB) within the system, the "Call options" dialog
opens. In this dialog, you can create an instance data block for the function block, either as a
single instance or, if necessary, multi-instance, in which data of the inserted instruction are
stored. Once it is created, the new instance data block can be found in the "Program
resources" folder in the project tree under "Program blocks > System blocks". If you have
selected "multi-instance", you can find it in the block interface in the "Static" section.
Result
The empty box is changed to the appropriate instruction. Placeholders are inserted for the
parameters.
13.1.2.3
Open branch (STEP 7 Safety V15.1)
Description
You use branches, which you insert between the boxes, to program parallel connections with
the Function Block Diagram (FBD) programming language You can insert additional boxes in
the branch, thereby programming complex function block diagrams.
Requirement
A network is available.
Procedure
To insert a new branch in a network, follow these steps:
1. Open the "Instructions" task card.
2. Navigate in the pane to "Basic instructions > General > Branch".
3. Use a drag-and-drop operation to move the element to the desired place to a connecting
line between two boxes.
Example
The following figure provides an example of how to use branches:
13.1 General
SIMATIC Safety - Configuring and Programming
398 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.1.2.4
Insert binary input (STEP 7 Safety V15.1)
Description
Use the "Insert binary input" instruction to expand the box of one of the following instructions
by a binary input:
"AND logic operation"
"OR logic operation"
"EXCLUSIVE OR logic operation"
You can query the signal state of several operands by expanding the instruction box.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand> Input BOOL The operand indicates the bit whose signal state will be
queried.
Example
The following example shows how the instruction works:
The box of instruction "AND logic operation" has been expanded by an additional binary
input at which the signal state of operand "TagIn_3" is queried. Output "TagOut" is set when
the signal state of operands "TagIn_1", "TagIn_2", and "TagIn_3" is "1".
See also
AND logic operation (STEP 7 Safety V15.1) (Page 414)
OR logic operation (STEP 7 Safety V15.1) (Page 416)
X: EXCLUSIVE OR logic operation (STEP 7 Safety V15.1) (Page 417)
13.1 General
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 399
13.1.2.5
Invert RLO (STEP 7 Safety V15.1)
Description
You can use the "Invert RLO" instruction to invert the result of logic operation (RLO).
Example
The following example shows how the instruction works:
Output "TagOut" is set when the following conditions are fulfilled:
The "TagIn_1" and/or "TagIn_2" input has the signal state "0".
The "TagIn_3" or "TagIn_4" input has the signal state "0" or the "TagIn_5" input has the
signal state "1".
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
400 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.2
Bit logic operations
13.2.1
LAD
13.2.1.1
---| |---: NO contact (STEP 7 Safety V15.1)
Description
The activation of the normally open contact depends on the signal state of the associated
operand. If the operand has signal state "1," the normally open contact is closed. Power
flows from the left power rail through the normally open contact into the right power rail and
the signal state at the output of the instruction is set to "1".
If the operand has signal state "0," the normally open contact is not activated. The power
flow to the right power rail is interrupted and the signal state at the output of the instruction is
reset to "0".
Two or more normally open contacts are linked bit-by-bit by AND when connected in series.
With a series connection, power flows when all contacts are closed.
The normally open contacts are linked by OR when connected in parallel. With a parallel
connection, power flows when one of the contacts is closed.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand>
Input
BOOL
Operand whose signal state is queried.
Example
The following example shows how the instruction works:
Operand "TagOut" is set when one of the following conditions is fulfilled:
Operands "TagIn_1" and "TagIn_2" have signal state "1".
The signal state at operand "TagIn_3" is "1".
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 401
13.2.1.2
---| / |---: NC contact (STEP 7 Safety V15.1)
Description
The activation of the normally closed contact depends on the signal state of the associated
operand. If the operand has signal state "1", the normally closed contact is opened and the
signal state at the output of the instruction is reset to "0".
If the operand has signal state "0", the normally closed contact is not activated and the signal
state at the output of the instruction is set to "1".
Two or more normally closed contacts are linked bit-by-bit by AND when connected in
series. With a series connection, power flows when all contacts are closed.
The normally closed contacts are linked by OR when connected in parallel. With a parallel
connection, power flows when one of the contacts is closed.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand>
Input
BOOL
Operand whose signal state is queried.
Example
The following example shows how the instruction works:
Operand "TagOut" is set when one of the following conditions is fulfilled:
Operands "TagIn_1" and "TagIn_2" have signal state "1".
The signal state at operand "TagIn_3" is "0".
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
402 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.2.1.3
--|NOT|--: Invert RLO (STEP 7 Safety V15.1)
Description
You can use the "Invert RLO" instruction to invert the signal state of the result of logic
operation (RLO). When the signal state is "1" at the input of the instruction, the output of the
instruction has the signal state "0". When the signal state is "0" at the input of the instruction,
the output has the signal state "1".
Example
The following example shows how the instruction works:
Operand "TagOut" is reset when one of the following conditions is fulfilled:
Operand "TagIn_1" has signal state "1".
Operands "TagIn_2" and "TagIn_3" have signal state "1".
13.2.1.4
---( )---: Assignment (STEP 7 Safety V15.1)
Description
You can use the "Assignment" instruction to set the bit of a specified operand. When the
result of logic operation (RLO) at the input of the coil is "1," the specified operand is set to
signal state "1". When the signal state is "0" at the input of the coil, the bit of the specified
operand is reset to "0".
The instruction does not influence the RLO. The RLO at the input of the coil is sent
immediately to the output.
The "Assignment" instruction can be placed at any position in the network.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand>
Output
BOOL
Operand to which the RLO is assigned.
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 403
Example
The following example shows how the instruction works:
Operand "TagOut" is set when one of the following conditions is fulfilled:
Operands "TagIn_1" and "TagIn_2" have signal state "1".
The signal state at operand "TagIn_3" is "0".
13.2.1.5
---( R )---: Reset output (STEP 7 Safety V15.1)
Description
You can use the "Reset output" instruction to reset the signal state of a specified operand to
"0".
If power flows to the coil (RLO is "1"), the specified operand is set to "0". If the result of logic
operation at the input of the coil is "0" (no signal flow to the coil), the signal state of the
specified operand remains unchanged.
The instruction does not influence the RLO. The RLO at the input of the coil is sent directly to
the output of the coil.
Note
If the operand area "local data (temp)" is used for the operands of the instruction, the local
data bit used must be initialized beforehand.
Note
You cannot use t
he "process image of the inputs", "process image of the outputs" from
standard I/O and "standard DB" and "bit memory" operand areas for the operands of the
instruction.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand>
Output
BOOL
Operand that is reset when RLO = "1".
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
404 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example
The following example shows how the instruction works:
Operand "TagOut" is reset when one of the following conditions is fulfilled:
Operands "TagIn_1" and "TagIn_2" have signal state "1".
The signal state of operand "TagIn_3" is "0".
13.2.1.6
---( S )---: Set output (STEP 7 Safety V15.1)
Description
You can use the "Set output" instruction to set the signal state of a specified operand to "1".
If power flows to the coil (RLO is "1"), the specified operand is set to "1". If the result of logic
operation at the input of the coil is "0" (no signal flow to the coil), the signal state of the
specified operand remains unchanged.
The instruction does not influence the RLO. The RLO at the input of the coil is sent directly to
the output of the coil.
Note
The instructio
n is not executed if it is applied to an output of an F-
I/O that is passivated (e.g.,
during startup of the F
-system). Therefore, it is preferable to access outputs of the F-I/O
using only the "Assignment" instruction.
An F
-I/O output is passivated if QBAD or QBAD_O_xx = 1 or value status = 0 is set in the
corresponding F
-I/O DB.
Note
If the operand area "local data (temp)" is used for the operands of the instruction, the local
data bit used must be initialized beforehand.
Note
You cannot use the "p
rocess image of the inputs", "process image of the outputs" from
standard I/O and "standard DB" and "bit memory" operand areas for the operands of the
instruction.
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 405
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand>
Output
BOOL
Operand that is set when RLO = "1".
Example
The following example shows how the instruction works:
Operand "TagOut" is set when one of the following conditions is fulfilled:
Operands "TagIn_1" and "TagIn_2" have signal state "1".
The signal state of operand "TagIn_3" is "0".
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
406 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.2.1.7
SR: Set/reset flip-flop (STEP 7 Safety V15.1)
Description
You can use the "Set/reset flip-flop" instruction to set or reset the bit of the specified operand
based on the signal state of inputs S and R1. If the signal state at input S is "1" and the
signal state at input R1 is "0", the specified operand is set to "1". If the signal state at input S
is "0" and the signal state at input R1 is "1", the specified operand is reset to "0".
Input R1 takes priority over input S. If the signal state is "1" at the two inputs S and R1, the
signal state of the specified operand is reset to "0".
The instruction is not executed if the signal state at the two inputs S and R1 is "0". The signal
state of the operand then remains unchanged.
The current signal state of the operand is transferred to output Q and can be queried there.
Note
If you want to use a formal parameter of an F
-FC for the operand of the instruction, it must
be declared as an input/output parameter.
Note
You cannot use the "process image", "standard DB" and "b
it memory" operand areas for the
operands of the instruction.
If the operand area "local data (temp)" is used for the operands of the instruction, the local
data bit used must be initialized beforehand.
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
S
Input
BOOL
Enable set
R1
Input
BOOL
Enable reset
<Operand>
Output
BOOL
Operand that is set or reset.
Q
Output
BOOL
Signal state of the operand
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 407
Example
The following example shows how the instruction works:
Operands ""F_DB_1".TagSR" and "TagOut" are set when the following conditions are
fulfilled:
Operand "TagIn_1" has signal state "1".
Operand "TagIn_2" has signal state "0".
Operands ""F_DB_1".TagSR" and "TagOut" are reset when the following conditions are
fulfilled:
Operand "TagIn_1" has signal state "0" and operand "TagIn_2" has signal state "1".
Both operands "TagIn_1" and "TagIn_2" have signal state "1".
13.2.1.8
RS: Reset/set flip-flop (STEP 7 Safety V15.1)
Description
You can use the "Reset/set flip-flop" instruction to reset or set the bit of the specified
operand based on the signal state of inputs R and S1. When the signal state is "1" at input R
and "0" at input S1, the specified operand is reset to "0". When the signal state is "0" at input
R and "1" at input S1, the specified operand is set to "1".
Input S1 takes priority over input R. If the signal state is "1" at the two inputs R and S1, the
signal state of the specified operand is set to "1".
The instruction is not executed if the signal state at the two inputs R and S1 is "0". The signal
state of the operand then remains unchanged.
The current signal state of the operand is transferred to output Q and can be queried there.
Note
If you want to use a formal parameter of an F
-FC for the operand of the instruction, it must
be declared as an input/output paramete
r.
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
408 Programming and Operating Manual, 10/2018, A5E02714440-AH
Note
You cannot use the "process image", "standard DB" and "bit memory" operand areas for the
operands of the instruction.
If the operand area "local data (temp)" is used for the operands of the instruction, the local
data bit used must be initiali
zed beforehand.
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
R
Input
BOOL
Enable reset
S1
Input
BOOL
Enable set
<Operand>
Output
BOOL
Operand that is reset or set.
Q
Output
BOOL
Signal state of the operand
Example
The following example shows how the instruction works:
Operands ""F_DB_1".TagRS" and "TagOut" are reset when the following conditions are
fulfilled:
Operand "TagIn_1" has signal state "1".
Operand "TagIn_2" has signal state "0".
Operands ""F_DB_1".TagRS" and "TagOut" are set when the following conditions are
fulfilled:
Operand "TagIn_1" has signal state "0" and operand "TagIn_2" has signal state "1".
Operands "TagIn_1" and "TagIn_2" have signal state "1".
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 409
13.2.1.9
--|P|--: Scan operand for positive signal edge (STEP 7 Safety V15.1)
Description
You can use the "Scan operand for positive signal edge" instruction to determine if there is a
change from "0" to "1" in the signal state of a specified operand (<Operand1>). The
instruction compares the current signal state of <Operand1> with the signal state of the
previous query saved in <Operand2>. If the instruction detects a change in the result of logic
operation from "0" to "1", there is a positive, rising edge.
If a rising edge is detected, the output of the instruction has signal state "1". In all other
cases, the signal state at the output of the instruction is "0".
Enter the operand to be queried (<Operand1>) in the operand placeholder above the
instruction. Enter the edge memory bit (<Operand2>) in the operand placeholder below the
instruction.
Note
The address of the edge memory bit must not be used more than once in the program,
otherwise the edge memory bit would be overwritten. This would influence edge evaluation
and the result would no longer be unequivocal.
Note
If you want to use a formal parameter of an F
-FC for the edge memory bit <Operand2> of
the instruction, it must be declared as an input/output parameter.
Note
You cannot use the "process image", "standard DB" and "bit memory" operand areas for the
edg
e memory bit <Operand2> of the instruction.
If operand area "local data (temp)" is used for the edge memory bit <Operand2> of the
instruction, the local data bit used must be initialized beforehand.
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand1>
Input
BOOL
Signal to be queried
<Operand2> InOut BOOL Edge memory bit in which the signal state of the
previous query is saved.
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
410 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example
The following example shows how the instruction works:
Operand "TagOut" is set when the following conditions are fulfilled:
There is a rising edge at input "TagIn_1". The signal state of the previous query is saved
at edge memory bit ""F_DB_1".Tag_M".
The signal state of operand "TagIn_2" is "1".
13.2.1.10
--|N|--: Scan operand for negative signal edge (STEP 7 Safety V15.1)
Description
You can use the "Scan operand for negative signal edge" instruction to determine if there is
a change form "1" to "0" in the signal state of a specified operand. The instruction compares
the current signal state of <Operand1> with the signal state of the previous query saved in
<Operand2>. If the instruction detects a change in the result of logic operation from "1" to
"0", there is a negative, falling edge.
If a falling edge is detected, the output of the instruction has signal state "1". In all other
cases, the signal state at the output of the instruction is "0".
Enter the operand to be queried (<Operand1>) in the operand placeholder above the
instruction. Enter the edge memory bit (<Operand2>) in the operand placeholder below the
instruction.
Note
The address of the edge memory bit must not be used more than once in the program,
otherwise the edge memory bit would be overwritten. This would influence edge evaluation
and the result would no longer be unequivocal.
Note
If you want to use a formal parameter of an F
-FC for the edge memory bit <Operand2> of
the instruction, it must be declared as an input/output parameter.
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 411
Note
You cannot use the "process image", "standard DB" and "bit memory" operand areas for the
e
dge memory bit <Operand2> of the instruction.
If operand area "local data (temp)" is used for the edge memory bit <Operand2> of the
instruction, the local data bit used must be initialized beforehand.
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand1>
Input
BOOL
Signal to be queried
<Operand2> InOut BOOL Edge memory bit in which the signal state of the previ-
ous query is saved.
Example
The following example shows how the instruction works:
Operand "TagOut" is set when the following conditions are fulfilled:
There is a falling edge at operand "TagIn_1". The signal state of the previous query is
saved at edge memory bit ""F_DB_1".Tag_M".
The signal state of operand "TagIn_2" is "1".
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
412 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.2.1.11
P_TRIG: Scan RLO for positive signal edge (STEP 7 Safety V15.1)
Description
You can use the "Scan RLO for positive signal edge" instruction to query a change in the
signal state of the result of logic operation from "0" to "1". The instruction compares the
current signal state of the result of logic operation (RLO) with the signal state of the previous
query, which is saved in the edge bit memory (<Operand>). If the instruction detects a
change in the RLO from "0" to "1", there is a positive, rising edge.
If a rising edge is detected, the output of the instruction has signal state "1". In all other
cases, the signal state at the output of the instruction is "0".
Note
The address of the edge memory bit must not be used more than once in the program,
otherwise the edge memory bit would be overwritten.
This would influence edge evaluation
and the result would no longer be unequivocal.
Note
If you want to use a formal parameter of an F
-FC for the edge memory bit <Operand> of the
instruction, it must be declared as an input/output parameter.
Note
You cannot use the "process image", "standard DB" and "bit memory" operand areas for the
edge memory bit <Operand> of the instruction.
If operand area "local data (temp)" is used for the edge memory bit <Operand> of the
instruction, the local data bit used
must be initialized beforehand.
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
CLK
Input
BOOL
Current RLO
<Operand> InOut BOOL Edge memory bit in which the RLO of the previous
query is saved.
Q
Output
BOOL
Result of edge evaluation
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 413
Example
The following example shows how the instruction works:
The RLO from the previous bit logic operation is saved in edge memory bit
""F_DB_1".Tag_M". If a change in the RLO signal state from "0" to "1" is detected, the
program jumps to jump label CAS1.
13.2.1.12
N_TRIG: Scan RLO for negative signal edge (STEP 7 Safety V15.1)
Description
You can use the "Scan RLO for negative signal edge" instruction to query a change in the
signal state of the result of logic operation from "1" to "0". The instruction compares the
current signal state of the result of logic operation with the signal state from the previous
query, which is saved in the edge memory bit (<Operand>). If the instruction detects a
change in the RLO from "1" to "0", there is a negative, falling edge.
If a falling edge is detected, the output of the instruction has signal state "1". In all other
cases, the signal state at the output of the instruction is "0".
Note
The address of the edge memory bit must not be used more than once in the program,
ot
herwise the edge memory bit would be overwritten. This would influence edge evaluation
and the result would no longer be unequivocal.
Note
If you want to use a formal parameter of an F
-FC for the edge memory bit <Operand> of the
instruction, it must be
declared as an input/output parameter.
Note
You cannot use the "process image", "standard DB" and "bit memory" operand areas for the
edge memory bit <Operand> of the instruction.
If operand area "local data (temp)" is used for the edge memory bit <Op
erand> of the
instruction, the local data bit used must be initialized beforehand.
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
414 Programming and Operating Manual, 10/2018, A5E02714440-AH
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
CLK
Input
BOOL
Current RLO
<Operand> InOut BOOL Edge memory bit in which the RLO of the previous
query is saved.
Q
Output
BOOL
Result of edge evaluation
Example
The following example shows how the instruction works:
The RLO of the previous bit logic operation is saved in edge bit memory ""F_DB_1".Tag_M".
If a change in the RLO signal state from "1" to "0" is detected, the program jumps to jump
label CAS1.
13.2.2
FBD
13.2.2.1
AND logic operation (STEP 7 Safety V15.1)
Description
You can use the "AND logic operation" instruction to query the signal states of two or more
specified operands and evaluate them according to the AND truth table.
If the signal state of all the operands is "1", then the conditions are fulfilled and the
instruction returns the result "1". If the signal state of one of the operands is "0", then the
conditions are not fulfilled and the instruction generates the result "0".
If the "AND logic operation" instruction is the first instruction in a logic string, it saves the
result of its signal state query in the RLO bit.
Each "AND logic operation" instruction that is not the first instruction in the logic string
logically combines the result of its signal state query with the value saved in the RLO bit.
This logical combination is performed according to the AND truth table.
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 415
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand>
Input
BOOL
The operand indicates the bit whose signal state will be queried.
Example
The following example shows how the instruction works:
Output "TagOut" is set when the signal state of operands "TagIn_1" and "TagIn_2" is "1".
AND truth table
The following table shows the results when linking two operands by an AND logic operation:
Signal state of the first operand
Signal state of the second operand
Result of logic operation
1
1
1
0
1
0
1
0
0
0
0
0
See also
Insert binary input (STEP 7 Safety V15.1) (Page 398)
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
416 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.2.2.2
OR logic operation (STEP 7 Safety V15.1)
Description
You can use the "OR logic operation" instruction to get the signal states of two or more
specified operands and evaluate them according to the OR truth table.
If the signal state of at least one of the operands is "1", then the conditions are fulfilled and
the instruction returns the result "1". If the signal state of all of the operands is "0", then the
conditions are not fulfilled and the instruction generates the result "0".
If the "OR logic operation" instruction is the first instruction in a logic string, it saves the result
of its signal state query in the RLO bit.
Each "OR logic operation" instruction that is not the first instruction in the logic string,
logically combines the result of its signal state query with the value saved in the RLO bit.
This logical combination is performed according to the OR truth table.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand> Input BOOL The operand indicates the bit whose signal state will be
queried.
Example
The following example shows how the instruction works:
Output "TagOut" is set when the signal state of operand "TagIn_1" or "TagIn_2" is "1".
OR truth table
The following table shows the results when linking two operands by an OR logic operation:
Signal state of the first operand
Signal state of the second operand
Result of logic operation
1
0
1
0
1
1
1
1
1
0
0
0
See also
Insert binary input (STEP 7 Safety V15.1) (Page 398)
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 417
13.2.2.3
X: EXCLUSIVE OR logic operation (STEP 7 Safety V15.1)
Description
You can use the "EXCLUSIVE OR logic operation" instruction to get the result of a signal
state query according to the the EXCLUSIVE OR truth table.
With an "EXCLUSIVE OR logic operation" instruction, the signal state is "1" when the signal
state of one of the two specified operands is "1". When more than two operands are queried,
the overall result of logic operation is "1" if an odd-numbered quantity of queried operands
returns the result "1".
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand> Input BOOL The operand indicates the bit whose signal state will be
queried.
Example
The following example shows how the instruction works:
Output "TagOut" is set when the signal state of one of the two operands "TagIn_1" and
"TagIn_2" is "1". When both operands have signal state "1" or "0" then output "TagOut" is
reset.
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
418 Programming and Operating Manual, 10/2018, A5E02714440-AH
EXCLUSIVE OR truth table
The following table shows the results when two operands are linked by an EXCLUSIVE OR:
Signal state of the first operand
Signal state of the second operand
Result of logic operation
1
0
1
0 1 1
1
1
0
0
0
0
The following table shows the results when three operands are linked by an EXCLUSIVE
OR:
Signal state of the first
operand
Signal state of the
second operand
Signal state of the
third operand
Result of logic operation
1
0
0
1
0
1
1
0
0
1
0
1
1
0
1
0
0
0
1
1
1
1
0
0
1
1
1
1
0
0
0
0
See also
Insert binary input (STEP 7 Safety V15.1) (Page 398)
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 419
13.2.2.4
=: Assignment (STEP 7 Safety V15.1)
Description
You can use the "Assignment" instruction to set the bit of a specified operand. If the result of
logic operation (RLO) at the box input has signal state "1" or the box input for S7-1200/1500
F-CPUs is not connected, the specified operand is set to signal state "1". If the signal state at
the box input is "0", the bit of the specified operand is reset to "0".
The instruction does not influence the RLO. The RLO at the box input is assigned directly to
the operand located above the Assign box.
The "Assignment" instruction can be placed at any position in the logic operation sequence.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand>
Output
BOOL
Operand to which the RLO is assigned.
Example
The following example shows how the instruction works:
Operand "TagOut" at the output of the "Assignment" instruction is set when one of the
following conditions is fulfilled:
Inputs "TagIn_1" and "TagIn_2" have signal state "1".
The signal state at input "TagIn_3" is "0".
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
420 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.2.2.5
R: Reset output (STEP 7 Safety V15.1)
Description
You can use the "Reset output" instruction to reset the signal state of a specified operand to
"0".
If the box input has signal state "1" or the box input for S7-1200/1500 F-CPUs is not
connected, the specified operand is reset to "0". If there is a result of logic operation of "0" at
the box input, the signal state of the specified operand remains unchanged.
The instruction does not influence the RLO. The RLO at the box input is transferred directly
to the box output.
Note
If the operand area "local data (temp)" is used for the operands of the instruction, the local
data bit used must be initialized beforehand.
Note
You cannot use
the "process image of the inputs", "process image of the outputs" from
standard I/O and "standard DB" and "bit memory" operand areas for the operands of the
instruction.
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand>
Output
BOOL
Operand that is reset with RLO = "1".
Example
The following example shows how the instruction works:
Operand "TagOut" is reset when one of the following conditions is fulfilled:
Operands "TagIn_1" and "TagIn_2" have signal state "1".
The signal state of operand "TagIn_3" is "0".
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 421
13.2.2.6
S: Set output (STEP 7 Safety V15.1)
Description
You can use the "Set output" instruction to set the signal state of a specified operand to "1".
If the box input has signal state "1" or the box input for S7-1200/1500 F-CPUs is not
connected, the specified operand is set to "1". If there is a result of logic operation of "0" at
the box input, the signal state of the specified operand remains unchanged.
The instruction does not influence the RLO. The RLO at the box input is transferred directly
to the box output.
Note
The inst
ruction is not executed if it is applied to an output of an F-
I/O that is passivated (e.g.,
during startup of the F
-system). Therefore, it is preferable to access outputs of the F-I/O
using only the "Assignment" instruction.
An F
-I/O output is passivated if QBAD or QBAD_O_xx = 1 or value status = 0 is set in the
corresponding F
-I/O DB.
Note
If the operand area "local data (temp)" is used for the operands of the instruction, the local
data bit used must be initialized beforehand.
Note
You cannot use
the "process image of the inputs", "process image of the outputs" from
standard I/O and "standard DB" and "bit memory" operand areas for the operands of the
instruction.
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand>
Output
BOOL
Operand that is set when RLO = "1".
Example
The following example shows how the instruction works:
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
422 Programming and Operating Manual, 10/2018, A5E02714440-AH
Operand "TagOut" is set when one of the following conditions is fulfilled:
Operands "TagIn_1" and "TagIn_2" have signal state "1".
The signal state of operand "TagIn_3" is "0".
13.2.2.7
SR: Set/reset flip-flop (STEP 7 Safety V15.1)
Description
You can use the "Set/reset flip-flop" instruction to set or reset the bit of the specified operand
based on the signal state of inputs S and R1. If the signal state at input S is "1" and the
signal state at input R1 is "0", the specified operand is set to "1". If the signal state at input S
is "0" and the signal state at input R1 is "1", the specified operand is reset to "0".
Input R1 takes priority over input S. If the signal state is "1" at the two inputs S and R1, the
signal state of the specified operand is reset to "0".
The instruction is not executed if the signal state at the two inputs S and R1 is "0". The signal
state of the operand then remains unchanged.
The current signal state of the operand is transferred to output Q and can be queried there.
Note
If you want to use a formal parameter of an F
-FC for the operand of the instruction, it must
be declared as an input/output parameter.
Note
You cannot use the "process image", "standard DB"
and "bit memory" operand areas for the
operands of the instruction.
If the operand area "local data (temp)" is used for the edge bit memory of the instruction, the
local data bit used must be initialized beforehand.
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
S
Input
BOOL
Enable set
R1
Input
BOOL
Enable reset
<Operand>
Output
BOOL
Operand that is set or reset.
Q
Output
BOOL
Signal state of the operand
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 423
Example
The following example shows how the instruction works:
Operands ""F_DB_1".TagSR" and "TagOut" are set when the following conditions are
fulfilled:
Operand "TagIn_1" has signal state "1".
Operand "TagIn_2" has signal state "0".
Operands ""F_DB_1".TagSR" and "TagOut" are reset when the following conditions are
fulfilled:
Operand "TagIn_1" has signal state "0" and operand "TagIn_2" has signal state "1".
Both operands "TagIn_1" and "TagIn_2" have signal state "1".
13.2.2.8
RS: Reset/set flip-flop (STEP 7 Safety V15.1)
Description
You can use the "Reset/set flip-flop" instruction to reset or set the bit of the specified
operand based on the signal state of inputs R and S1. When the signal state is "1" at input R
and "0" at input S1, the specified operand is reset to "0". When the signal state is "0" at input
R and "1" at input S1, the specified operand is set to "1".
Input S1 takes priority over input R. If the signal state is "1" at the two inputs R and S1, the
signal state of the specified operand is set to "1".
The instruction is not executed if the signal state at the two inputs R and S1 is "0". The signal
state of the operand then remains unchanged.
The current signal state of the operand is transferred to output Q and can be queried there.
Note
If you want to use a formal parameter of an F
-FC for the operand of the instruction, it must
be declared as an input/ou
tput parameter.
Note
You cannot use the "process image", "standard DB" and "bit memory" operand areas for the
operands of the instruction.
If the operand area "local data (temp)" is used for the edge bit memory of the instruction, the
local data bit u
sed must be initialized beforehand.
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
424 Programming and Operating Manual, 10/2018, A5E02714440-AH
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
R
Input
BOOL
Enable reset
S1 Input BOOL Enable set
<Operand>
Output
BOOL
Operand that is reset or set.
Q
Output
BOOL
Signal state of the operand
Example
The following example shows how the instruction works:
Operands ""F_DB_1".TagRS" and "TagOut" are reset when the following conditions are
fulfilled:
Operand "TagIn_1" has signal state "1".
Operand "TagIn_2" has signal state "0".
Operands ""F_DB_1".TagRS" and "TagOut" are set when the following conditions are
fulfilled:
Operand "TagIn_1" has signal state "0" and operand "TagIn_2" has signal state "1".
Operands "TagIn_1" and "TagIn_2" have signal state "1".
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 425
13.2.2.9
P: Scan operand for positive signal edge (STEP 7 Safety V15.1)
Description
You can use the "Scan operand for positive signal edge" instruction to determine if there is a
change from "0" to "1" in the signal state of a specified operand (<Operand1>). The
instruction compares the current signal state of <Operand1> with the signal state of the
previous query saved in <Operand2>. If the instruction detects a change in the result of logic
operation from "0" to "1", there is a positive, rising edge.
If a rising edge is detected, the output of the instruction has signal state "1". In all other
cases, the signal state at the output of the instruction is "0".
Enter the operand to be queried (<Operand1>) in the operand placeholder above the
instruction. Enter the edge memory bit (<Operand2>) in the operand placeholder below the
instruction.
Note
The address of the edge memory bit must not be used more than once in the program,
otherwise the edge memory bit would be overwritten. This would influence edge evaluation
and the result would no longer be unequivo
cal.
Note
If you want to use a formal parameter of an F
-FC for the edge memory bit <Operand2> of
the instruction, it must be declared as an input/output parameter.
Note
You cannot use the "process image", "standard DB" and "bit memory" operand are
as for the
edge memory bit <Operand2> of the instruction.
If operand area "local data (temp)" is used for the edge memory bit <Operand2> of the
instruction, the local data bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand1>
Input
BOOL
Signal to be queried
<Operand2> InOut BOOL Edge memory bit in which the signal state of the previous
query is saved.
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
426 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example
The following example shows how the instruction works:
"TagOut" is set when the following conditions are fulfilled:
There is a rising edge at input "TagIn_1".
The signal state of operand "TagIn_2" is "1".
13.2.2.10
N: Scan operand for negative signal edge (STEP 7 Safety V15.1)
Description
You can use the "Scan operand for negative signal edge" instruction to determine if there is
a change form "1" to "0" in the signal state of a specified operand. The instruction compares
the current signal state of <Operand1> with the signal state of the previous query saved in
<Operand2>. If the instruction detects a change in the result of logic operation from "1" to
"0", there is a negative, falling edge.
If a falling edge is detected, the output of the instruction has signal state "1". In all other
cases, the signal state at the output of the instruction is "0".
Enter the operand to be queried (<Operand1>) in the operand placeholder above the
instruction. Enter the edge memory bit (<Operand2>) in the operand placeholder below the
instruction.
Note
The address of the edge memory bit must not be used mo
re than once in the program,
otherwise the edge memory bit would be overwritten. This would influence edge evaluation
and the result would no longer be unequivocal.
Note
If you want to use a formal parameter of an F
-FC for the edge memory bit <Operand2> of
the instruction, it must be declared as an input/output parameter.
Note
You cannot use the "process image", "standard DB" and "bit memory" operand areas for the
edge memory bit <Operand2> of the instruction.
If operand area "local data (temp)" is
used for the edge memory bit <Operand2> of the
instruction, the local data bit used must be initialized beforehand.
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 427
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Operand1>
Input
BOOL
Signal to be queried
<Operand2> InOut BOOL Edge memory bit in which the signal state of the previous
query is saved.
Example
The following example shows how the instruction works:
Output "TagOut" is set when the following conditions are fulfilled:
There is a falling edge at input "TagIn_1".
The signal state of operand "TagIn_2" is "1".
13.2.2.11
P_TRIG: Scan RLO for positive signal edge (STEP 7 Safety V15.1)
Description
You can use the "Scan RLO for positive signal edge" instruction to query a change in the
signal state of the result of logic operation from "0" to "1". The instruction compares the
current signal state of the result of logic operation with the signal state from the previous
query, which is saved in the edge memory bit (<Operand>). If the instruction detects a
change in the RLO from "0" to "1", there is a positive, rising edge.
If a rising edge is detected, the output of the instruction has signal state "1". In all other
cases, the signal state at the output of the instruction is "0".
Note
The address of the edge memory bit must not be used mo
re than once in the program,
otherwise the edge memory bit would be overwritten. This would influence edge evaluation
and the result would no longer be unequivocal.
Note
If you want to use a formal parameter of an F
-FC for the edge memory bit <Operand> of the
instruction, it must be declared as an input/output parameter.
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
428 Programming and Operating Manual, 10/2018, A5E02714440-AH
Note
You cannot use the "process image", "standard DB" and "bit memory" operand areas for the
edge memory bit <Operand> of the instruction.
If operand area "local data (temp)" is u
sed for the edge memory bit <Operand> of the
instruction, the local data bit used must be initialized beforehand.
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
CLK
Input
BOOL
Current RLO
<Operand> InOut BOOL Edge memory bit in which the RLO of the previous query
is saved.
Q
Output
BOOL
Result of edge evaluation
Example
The following example shows how the instruction works:
The RLO from the previous bit logic operation is saved in edge memory bit
""F_DB_1".Tag_M". If a change in the RLO signal state from "0" to "1" is detected, the
program jumps to jump label CAS1.
13.2 Bit logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 429
13.2.2.12
N_TRIG: Scan RLO for negative signal edge (STEP 7 Safety V15.1)
Description
You can use the "Scan RLO for negative signal edge" instruction to query a change in the
signal state of the result of logic operation from "1" to "0". The instruction compares the
current signal state of the result of logic operation with the signal state from the previous
query, which is saved in the edge memory bit (<Operand>). If the instruction detects a
change in the RLO from "1" to "0", there is a negative, falling edge.
If a falling edge is detected, the output of the instruction has signal state "1". In all other
cases, the signal state at the output of the instruction is "0".
Note
The a
ddress of the edge memory bit must not be used more than once in the program,
otherwise the edge memory bit would be overwritten. This would influence edge evaluation
and the result would no longer be unequivocal.
Note
If you want to use a formal param
eter of an F-FC for the edge memory bit <Operand> of the
instruction, it must be declared as an input/output parameter.
Note
You cannot use the "process image", "standard DB" and "bit memory" operand areas for the
edge memory bit <Operand> of the inst
ruction.
If operand area "local data (temp)" is used for the edge memory bit <Operand> of the
instruction, the local data bit used must be initialized beforehand.
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
CLK
Input
BOOL
Current RLO
<Operand> InOut BOOL Edge memory bit in which the RLO of the previous query
is saved.
Q
Output
BOOL
Result of edge evaluation
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
430 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example
The following example shows how the instruction works:
The RLO of the previous bit logic operation is saved in edge bit memory ""F_DB_1".Tag_M".
If a change in the RLO signal state from "1" to "0" is detected, the program jumps to jump
label CAS1.
13.3
Safety functions
13.3.1
ESTOP1: Emergency STOP/OFF up to stop category 1 (STEP 7 Safety V15.1)
Description
This instruction implements an emergency STOP/emergency OFF shutdown with
acknowledgment for Stop Categories 0 and 1.
Enable signal Q is reset to 0, as soon as input E_STOP takes a signal state of 0 (Stop
category 0). Enable signal Q_DELAY is reset to 0 after the time delay set at input TIME_DEL
(Stop Category 1).
Enable signal Q is reset to 1 not before input E_STOP takes a signal state of 1 and an
acknowledgment occurs. The acknowledgment for the enable takes place according to the
parameter assignment at input ACK_NEC:
If ACK_NEC = 0, the acknowledgment is automatic.
If ACK_NEC = 1, you must use a rising edge at input ACK for acknowledging the enable.
Output ACK_REQ is used to signal that a user acknowledgment is required at input ACK for
the acknowledgment. The instruction sets output ACK_REQ to 1, as soon as input E_STOP
= 1.
Following an acknowledgment, the instruction resets ACK_REQ to 0.
Every call of the "Emergency STOP/Emergency OFF up to Stop Category 1" instruction must
be assigned a data area in which the instruction data are stored. The "Call options" dialog is
automatically opened when the instruction is inserted in the program for this reason. There
you can create a data block (single instance) (e.g., ESTOP1_DB_1) or a multi-instance (e.g.,
ESTOP1_Instance_1) for the "Emergency STOP/Emergency OFF up to Stop Category 1"
instruction. Once it is created, you can find the new data block in the project tree in the
"STEP 7 Safety" folder under "Program blocks > System blocks" or the multi-instance as a
local tag in the "Static" section of the block interface. For more information, refer to the help
on
STEP 7
.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 431
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
WARNING
The ACK_NEC tag must not be assigned a value of 0 unless an automatic restart of the
affected process is otherwise excluded.
(S033)
WARNING
When using an instruction with time processing, take the following timing imprecision
sources into account when determining your response times:
Known timing imprecision (based on standard systems) resulting from cyclic processing
Timing imprecision resulting from the update time of the time base used in the
instruction (see figure in section "Timing imprecision resulting from the update time of
the time base used in the instruction")
Tolerance of internal time monitoring in the F-CPU
For time values up to 200 ms, a maximum of 4 ms
For time values greater than or equal to 200 ms, a maximum of 2% of the (assigned)
time value
You must choose the interval between two call times of an instruction with time processing
in such a way that the required response times are achieved, taking into account the
possible timing imprecision.
(S034)
Note:
In case of two channels according to category 3,4 of ISO 13849-1:2015 or EN ISO
13849-1:2015, the discrepancy monitoring of the two NC contacts of the EMERGENCY
STOP/EMERGENCY OFF must already take place in the F-I/O. The F-I/O has to be
configured accordingly (sensor evaluation: two-channel, equivalent), and the result of the
evaluation interconnected with the E_STOP input. In order to keep the discrepancy time from
influencing the response time, you must assign "Supply value 0" for the behavior of
discrepancy during configuration.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
E_STOP
Input
BOOL
EMERGENCY STOP/EMERGENCY OFF
ACK_NEC
Input
BOOL
1=Acknowledgment necessary
ACK Input BOOL 1=Acknowledgment
TIME_DEL
Input
TIME
Time delay
Q
Output
BOOL
1=Enable
Q_DELAY
Output
BOOL
Enable is OFF delayed
ACK_REQ
Output
BOOL
1=Acknowledgment necessary
DIAG
Output
BYTE
Non-fail safe service information
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
432 Programming and Operating Manual, 10/2018, A5E02714440-AH
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x Version 1.0 requires that the F_TOF block with the number FB 186 is
available in the project tree in the "Program blocks/System
blocks/STEP 7 Safety" folder.
When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically. If you
want to compile a migrated safety program with
STEP 7 Safety Ad-
vanced
for the first time, we recommend that you first update to the
latest available version of the instruction. You will then avoid number
conflicts.
1.1
x
-—
These versions are functionally identical to version V1.0, but do not
require the F_TOF block to have a particular number.
1.2
x
o
1.3
x
o
o
1.4
x
o
o
1.5
x
x
x
1.6 x x x The reaction of the delay time TIME_DEL for F-CPUs S7-1200/1500
was adapted to the reaction of F-CPUs S7-300/400: If the input ESTOP
(0 -> 1 (including acknowledgment) -> 0) is changed while the delay
time is running, the delay time is restarted.
o This version is no longer supported.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the F-
CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
Startup characteristics
After an F-system startup, when ACK_NEC = 1, you must acknowledge the instruction using
a rising edge at input ACK.
Output DIAG
The DIAG output provides non-fail-safe information on errors for service purposes. You can
read out this information by means of operator control and monitoring systems or, if
applicable, you can evaluate it in your standard user program. DIAG bits 4 and 5 are saved
until you acknowledge at the ACK input.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 433
Structure of DIAG
Bit no.
Assignment
Possible error causes
Remedies
Bit 0
Incorrect TIM_DEL setting
Time delay setting < 0
Set time delay > 0
Bit 1 Reserved
Bit 2
Reserved
Bit 3
Reserved
Bit 4 Acknowledgment not possible
because emergency
STOP/emergency OFF is still
active
Emergency
STOP/Emergency OFF
pushbutton is locked
Release Emergency
STOP/Emergency OFF
pushbutton
F-I/O fault, channel fault, or
communication error, or
passivation by means of
PASS_ON of F-I/O of emer-
gency STOP/emergency
OFF pushbutton
For a solution, see the sec-
tion "Structure of DIAG", bits
0 to 6 in DIAG (Page 172)
Emergency
STOP/Emergency OFF
pushbutton is defective
Check emergency
STOP/emergency OFF
pushbutton
Wiring fault Check wiring of the emer-
gency STOP/emergency
OFF pushbutton
Bit 5 If enable is missing: input ACK
has a permanent signal state
of 1
Acknowledgment button
defective
Check acknowledgment
button
Wiring fault Check wiring of acknowl-
edgment button
Bit 6 Acknowledgment required
(= state of ACK_REQ)
Bit 7
State of output Q
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
434 Programming and Operating Manual, 10/2018, A5E02714440-AH
Timing imprecision resulting from the update time of the time base used in the instruction:
For the first call in cycle n+1, the call time of the instruction relative to the start of the F-runtime
group is earlier than that in cycle n by the amount of Δ1, e.g. because parts of the safety pro-
gram of the F-runtime group before the call time of the instruction in cycle n+1 are skipped. For
the time update, the instruction takes account of time TBase_1 instead of the time T1 that has
actually elapsed in cycle n since the call.
The instruction is called a second time in cycle n+1. This does not involve another time update
(by Δ2).
For the call in cycle n+2, the call time of the instruction relative to the start of the F-runtime
group is later than that in cycle n by the amount of Δ3, e.g. because the F-runtime group was
interrupted by a higher priority interrupt before the call time of the instruction in cycle n+2. The
instruction took into account time TBase_1 + TBase_2 instead of the time T3 that has actually
elapsed in cycle n since the call. This would also be the case if no call occurred in cycle n+1.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 435
Example
The following example shows how the instruction works:
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
436 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.3.2
TWO_HAND: Two-hand monitoring (STEP 7 Safety Advanced V15.1)
(S7-300, S7-400)
Description
This instruction implements two-hand monitoring.
Note
This
instruction is only available for S7-300 and S7-400 F-CPUs. For S7-1200/1500 F-
CPUs,
you use the instruction "Two
-hand monitoring with enable". The application "Two-hand
monitoring with enable" replaces the instruction "Two
-hand monitoring" with compatible
functions.
If pushbuttons IN1 and IN2 are activated within the permitted discrepancy time DISCTIME ≤
500 ms (IN1/IN2 = 1) (synchronous activation), output signal Q is set to 1. If the time
difference between activation of pushbutton IN1 and pushbutton IN2 is greater than
DISCTIME, then the pushbuttons must be released and reactivated.
Q is reset to 0 as soon as one of the pushbuttons is released (IN1/IN2 = 0). Enable signal Q
can be reset to 1 only if the other pushbutton has been released, and if both pushbuttons are
then reactivated within the discrepancy time. Enable signal Q can never be set to 1 if the
discrepancy time is set to values less than 0 or greater than 500 ms.
Every call of the "Two-hand monitoring" instruction must be assigned a data area in which
the instruction data are stored. The "Call options" dialog is automatically opened when the
instruction is inserted in the program for this reason. There you can create a data block
(single instance) (e.g., TWO_HAND_DB_1) or a multi-instance (e.g.,
TWO_HAND_Instance_1) for the "Two-hand monitoring" instruction. Once it is created, you
can find the new data block in the project tree in the "STEP 7 Safety" folder under "Program
blocks > System blocks" or the multi-instance as a local tag in the "Static" section of the
block interface. For more information, refer to the help on
STEP 7
.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
The instruction supports the requirements in accordance with EN 574:1996 + A1:2008.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 437
Note:
Only one signal per pushbutton can be evaluated in the instruction. Discrepancy
monitoring of the NC and NO contacts of pushbuttons IN1 and IN2 is performed directly
during suitable configuration (sensor evaluation: 1oo2 evaluation, non-equivalent) directly
through the F-I/O with inputs. The normally open contact must be wired in such a way that it
supplies the useful signal (see manual for the F-I/O you are using). In order to keep the
discrepancy time from influencing the response time, you must assign "Supply value 0" for
the behavior of discrepancy during configuration. If a discrepancy is detected, a fail-safe
value of 0 is entered in the process image of the inputs (PII) for the pushbutton and QBAD or
QBAD_I_xx = 1 is set in the relevant F-I/O DB. (See also F-I/O access (Page 157))
WARNING
When using an instruction with time processing, take the following timing imprecision
sources into account when determining your response times:
Known timing imprecision (based on standard systems) resulting from cyclic processing
Timing imprecision resulting from the update time of the time base used in the
instruction (see figure in section "Timing imprecision resulting from the update time of
the time base used in the instruction")
Tolerance of internal time monitoring in the F-CPU
For time values up to 200 ms, a maximum of 4 ms
For time values greater than or equal to 200 ms, a maximum of 2% of the (assigned)
time value
You must choose the interval between two call times of an instruction with time processing
in such a way that the required response times are achieved, taking into account the
possible timing imprecision.
(S034)
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN1
Input
BOOL
Pushbutton 1
IN2
Input
BOOL
Pushbutton 2
DISCTIME
Input
TIME
Discrepancy time (0 to 500 ms)
Q
Output
BOOL
1=Enable
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
438 Programming and Operating Manual, 10/2018, A5E02714440-AH
Timing imprecision resulting from the update time of the time base used in the instruction:
For the first call in cycle n+1, the call time of the instruction relative to the start of the F-runtime
group is earlier than that in cycle n by the amount of Δ1, e.g. because parts of the safety pro-
gram of the F-runtime group before the call time of the instruction in cycle n+1 are skipped. For
the time update, the instruction takes account of time TBase_1 instead of the time T1 that has
actually elapsed in cycle n since the call.
The instruction is called a second time in cycle n+1. This does not involve another time update
(by Δ2).
For the call in cycle n+2, the call time of the instruction relative to the start of the F-runtime
group is later than that in cycle n by the amount of Δ3, e.g. because the F-runtime group was
interrupted by a higher priority interrupt before the call time of the instruction in cycle n+2. The
instruction took into account time TBase_1 + TBase_2 instead of the time T3 that has actually
elapsed in cycle n since the call. This would also be the case if no call occurred in cycle n+1.
Example
The following example shows how the instruction works:
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 439
13.3.3
TWO_H_EN: Two-hand monitoring with enable (STEP 7 Safety V15.1)
Description
This instruction implements two-hand monitoring with enable.
If pushbuttons IN1 and IN2 are activated within the permitted discrepancy time DISCTIME
500 ms (IN1/IN2 = 1) (synchronous activation), output signal Q is set to 1 when existing
ENABLE = 1. If the time difference between activation of pushbutton IN1 and pushbutton IN2
is greater than DISCTIME, then the pushbuttons must be released and reactivated.
Q is reset to 0 as soon as one of the pushbuttons is released (IN1/IN 2 = 0) or ENABLE = 0.
Enable signal Q can be reset to 1 only if the other pushbutton has been released, and if both
pushbuttons are then reactivated within the discrepancy time when existing ENABLE = 1.
Every call of the "Two-hand monitoring with enable" instruction must be assigned a data
area in which the instruction data are stored. The "Call options" dialog is automatically
opened when the instruction is inserted in the program for this reason. There you can create
a data block (single instance) (e.g., TWO_H_EN_DB_1) or a multi-instance (e.g.,
TWO_H_EN_Instance_1) for the "Two-hand monitoring with enable" instruction. Once it is
created, you can find the new data block in the project tree in the "STEP 7 Safety" folder
under "Program blocks > System blocks" or the multi-instance as a local tag in the "Static"
section of the block interface. For more information, refer to the help on
STEP 7
.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
The instruction supports the requirements in accordance with EN 574:1996 + A1:2008.
Note:
Only one signal per pushbutton can be evaluated in the instruction. Discrepancy
monitoring of the NC and NO contacts of pushbuttons IN1 and IN2 is performed directly
during suitable configuration (sensor evaluation: 1oo2 evaluation, non-equivalent) directly
through the F-I/O with inputs. The normally open contact must be wired in such a way that it
supplies the useful signal (see manual for the F-I/O you are using). In order to keep the
discrepancy time from influencing the response time, during the configuration of discrepancy
behavior, you must configure "Supply value 0".
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
440 Programming and Operating Manual, 10/2018, A5E02714440-AH
If a discrepancy is detected, a fail-safe value of 0 is entered in the process image of the
inputs (PII) for the pushbutton and QBAD or QBAD_I_xx = 1 or respectively value status = 0
is set in the relevant F-I/O DB.
WARNING
When using an instruction with time processing, take the following timing imprecision
sources into account when determining your response times:
Known timing imprecision (based on standard systems) resulting from cyclic processing
Timing imprecision resulting from the update time of the time base used in the
instruction (see figure in section "Timing imprecision resulting from the update time of
the time base used in the instruction")
Tolerance of internal time monitoring in the F-CPU
For time values up to 200 ms, a maximum of 4 ms
For time values greater than or equal to 200 ms, a maximum of 2% of the (assigned)
time value
You must choose the interval between two call times of an instruction with time processing
in such a way that the required response times are achieved, taking into account the
possible timing imprecision.
(S034)
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN1
Input
BOOL
Pushbutton 1
IN2
Input
BOOL
Pushbutton 2
ENABLE
Input
BOOL
Enable input
DISCTIME
Input
TIME
Discrepancy time (0 to 500 ms)
Q
Output
BOOL
1=Enable
DIAG
Output
BYTE
Non-fail safe service information
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 441
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1 x o These versions have identical functions to version V1.0.
1.2
x
o
o
1.3
x
x
x
o This version is no longer supported.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the
F-CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
Output DIAG
The DIAG output provides non-fail-safe information on errors for service purposes. You can
read out this information by means of operator control and monitoring systems or, if
applicable, you can evaluate it in your standard user program. DIAG bits 0 to 5 are saved
until the cause of the error has been eliminated.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
442 Programming and Operating Manual, 10/2018, A5E02714440-AH
Structure of DIAG
Bit no.
Assignment
Possible error causes
Remedies
Bit 0 Incorrect discrepancy time
DISCTIME setting
Discrepancy time setting is <0 or >
500 ms
Set discrepancy time in range of 0 to
500 ms
Bit 1 Discrepancy time elapsed Discrepancy time setting is too low If necessary, set a higher discrep-
ancy time
Pushbuttons were not activated
within the discrepancy time
Release pushbuttons and activate
them within the discrepancy time
Wiring fault
Check wiring of pushbuttons
Pushbuttons defective
Check pushbuttons
Pushbuttons are wired to different
F-I/O, and F-I/O fault, channel
fault, or communication error, or
passivation by means of PASS_ON
on an F-I/O
For a solution, see the section
"Structure of DIAG", bits 0 to 6 in
DIAG (Page 172)
Bit 2
Reserved
Bit 3
Reserved
Bit 4 Incorrect activation sequence One pushbutton was not released Release pushbuttons and activate
them within the discrepancy time
Pushbuttons defective
Check pushbuttons
Bit 5 ENABLE does not exist ENABLE = 0 Set ENABLE = 1, release pushbut-
ton and activate it within the dis-
crepancy time
Bit 6
Reserved
Bit 7 State of output Q
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 443
Timing imprecision resulting from the update time of the time base used in the instruction:
For the first call in cycle n+1, the call time of the instruction relative to the start of the F-runtime
group is earlier than that in cycle n by the amount of Δ1, e.g. because parts of the safety pro-
gram of the F-runtime group before the call time of the instruction in cycle n+1 are skipped. For
the time update, the instruction takes account of time TBase_1 instead of the time T1 that has
actually elapsed in cycle n since the call.
The instruction is called a second time in cycle n+1. This does not involve another time update
(by Δ2).
For the call in cycle n+2, the call time of the instruction relative to the start of the F-runtime
group is later than that in cycle n by the amount of Δ3, e.g. because the F-runtime group was
interrupted by a higher priority interrupt before the call time of the instruction in cycle n+2. The
instruction took into account time TBase_1 + TBase_2 instead of the time T3 that has actually
elapsed in cycle n since the call. This would also be the case if no call occurred in cycle n+1.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
444 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example
The following example shows how the instruction works:
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 445
13.3.4
MUTING: Muting (STEP 7 Safety Advanced V15.1) (S7-300, S7-400)
Description
This instruction performs parallel muting with two or four muting sensors.
Note
This instruction is only available for S7
-300 and S7-400 F-CPUs. For S7-1200/1500 F-
CPUs,
you use the instruction "
Parallel muting (Page 456)". The instruction "Parallel muting"
replaces the instruction "Muting" with compatible functions.
Muting is a defined suppression of the protective function of light curtains. Light curtain
muting can be used to introduce goods or objects into the danger area monitored by the light
curtain without causing the machine to stop.
To utilize the muting function, at least two independently wired muting sensors must be
present. The use of two or four muting sensors and correct integration into the production
sequence must ensure that no persons enter the danger area while the light curtain is
muted.
Every call of the "Muting" instruction must be assigned a data area in which the instruction
data are stored. The "Call options" dialog is automatically opened when the instruction is
inserted in the program for this reason. There you can create a data block (single instance)
(e.g., MUTING_DB_1) or a multi-instance (e.g., MUTING_Instance_1) for the "Muting"
instruction. Once it is created, you can find the new data block in the project tree in the
"STEP 7 Safety" folder under "Program blocks > System blocks" or the multi-instance as a
local tag in the "Static" section of the block interface. For more information, refer to the help
on
STEP 7
.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
WARNING
When using an instruction with time processing, take the following timing imprecision
sources into account when determining your response times:
Known timing imprecision (based on standard systems) resulting from cyclic processing
Timing imprecision resulting from the update time of the time base used in the
instruction (see figure in section "Timing imprecision resulting from the update time of
the time base used in the instruction")
Tolerance of internal time monitoring in the F-CPU
For time values up to 200 ms, a maximum of 4 ms
For time values greater than or equal to 200 ms, a maximum of 2% of the (assigned)
time value
You must choose the interval between two call times of an instruction with time processing
in such a way that the required response times are achieved, taking into account the
possible timing imprecision.
(S034)
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
446 Programming and Operating Manual, 10/2018, A5E02714440-AH
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
MS_11
Input
BOOL
Muting sensor 1 of sensor pair 1
MS_12 Input BOOL Muting sensor 2 of sensor pair 1
MS_21
Input
BOOL
Muting sensor 1 of sensor pair 2
MS_22
Input
BOOL
Muting sensor 2 of sensor pair 2
STOP
Input
BOOL
1=Conveyor system stopped
FREE
Input
BOOL
1=Light curtain uninterrupted
QBAD_MUT Input BOOL QBAD signal of the F-I/O or QBAD_O_xx signal of
the muting lamp channel
DISCTIM1
Input
TIME
Discrepancy time of sensor pair 1 (0 to 3 s)
DISCTIM2
Input
TIME
Discrepancy time of sensor pair 2 (0 to 3 s)
TIME_MAX
Input
TIME
Maximum muting time (0 to 10 min)
ACK
Input
BOOL
Acknowledgment of restart inhibit
Q
Output
BOOL
1= Enable, not off
MUTING
Output
BOOL
Display of muting is active
ACK_REQ
Output
BOOL
Acknowledgment necessary
FAULT
Output
BOOL
Group error
DIAG
Output
BYTE
Non-fail safe service information
Schematic sequence of error-free muting procedure with 4 muting sensors (MS_11, MS_12, MS_21,
MS_22)
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 447
If both muting sensors MS_11 and MS_12 are activated by the product within DISCTIM1
(apply signal state = 1), the instruction starts the MUTING function. Enable signal Q
remains 1, even when input FREE = 0 (light curtain interrupted by product). The MUTING
output for setting the muting lamp switches to 1.
Note
The muting lamp can be monitored using the QBAD_MUT input. To do this, you must wire
the muting lamp to an output with wire break monitoring of an F
-I/O and supply the
QBAD_MUT in
put with the QBAD signal of the associated F-
I/O or the QBAD_O_xx signal
of the associated channel. If QBAD_MUT = 1, muting is terminated by the instruction. If
monitoring of the muting lamp is not necessary, you do not have to supply input
QBAD_MUT.
F
-I/O that can promptly detect a wire break after activation of the muting operation must
be used (
see manual for specific F-I/O
).
As long as both muting sensors MS_11 and MS_12 continue to be activated, the MUTING
function of the instruction causes Q to remain 1 and MUTING to remain 1 (so that the
product can pass through the light curtain without causing the machine to stop).
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
448 Programming and Operating Manual, 10/2018, A5E02714440-AH
The two muting sensors MS_21 and MS_22 must be activated (within DISCTIM2) before
muting sensors MS_11 and MS_12 are switched to inactive (apply signal state 0). In this
way, the instruction retains the MUTING function. (Q = 1, MUTING = 1).
Only if one of the two muting sensors MS_21 and MS_22 is switched to inactive (product
enables sensors) is the MUTING function terminated (Q = 1, MUTING = 0). The
maximum activation time for the MUTING function is the time set at input TIME_MAX.
Note
The MUTING function is also started if the product passes the light curtain in the reverse
direction and the muting sens
ors are thus activated by the product in reverse order.
Timing diagrams for error-free muting procedure with 4 muting sensors
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 449
Schematic sequence of muting procedure with reflection light barriers
If reflection light barriers are used as muting sensors, they are generally arranged diagonally.
In general, this arrangement of reflection light barriers as muting sensors requires only two
light barriers, and only MS_11 and MS_12 are interconnected.
The sequence is similar to that of the muting procedure with 4 muting sensors. Step 3 is
omitted. In step 4, replace MS_21 and MS_22 with MS_11 and MS_12, respectively.
Restart inhibit upon interruption of light curtain (if MUTING is not active), when errors occur, and
during F-system startup
Enable signal Q cannot be set to 1 or becomes 0, if:
Light curtain is interrupted (e.g., by a person or material transport) while the MUTING
function is not active
The muting lamp monitoring function responds at input QBAD_MUT
Sensor pair 1 (MS_11 and MS_12) or sensor pair 2 (MS_21 and MS_22) is not activated
or deactivated during discrepancy time DISCTIM1 or DISCTIM2, respectively
The MUTING function is active longer than the maximum muting time TIME_MAX
Discrepancy times DISCTIM1 and DISCTIM2 have been set to values < 0 or > 3 s
Maximum muting time TIME_MAX has been set to a value< 0 or > 10 min
In the identified cases, output FAULT (group error) is set to 1 (restart inhibit). If the MUTING
function is started, it will be terminated and the Muting output becomes 0.
WARNING
When a valid combination of muting sensors is immediately detected at startup of the
F-system (for example, because the muting sensors are interconnected to inputs of a
standard I/O that immediately provide process values during the F-system startup), the
MUTING function is immediately started and the MUTING output and enable signal Q are
set to 1. The FAULT output (group error) is not set to 1 (no restart inhibit!).
(S035)
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
450 Programming and Operating Manual, 10/2018, A5E02714440-AH
Acknowledgment of restart inhibit
Enable signal Q becomes 1 again, when:
The light curtain is no longer interrupted
If present, errors are eliminated (see output DIAG)
and
A user acknowledgment with positive edge occurs at input ACK (see also Implementation
of user acknowledgment (Page 187)).
The FAULT output is set to 0. Output ACK_REQ = 1 signals that user acknowledgment at
input ACK is required to eliminate the restart inhibit. The instruction sets ACK-REQ = 1 as
soon as the light curtain is no longer interrupted or errors have been eliminated. Once
acknowledgment has occurred, the instruction resets ACK_REQ to 0.
Note
Following discrepancy errors and once the maximum muting time has been exceeded,
ACK_REQ is immed
iately set to 1. As soon as a user acknowledgment has taken place at
input
ACK, discrepancy times DISCTIM1 and DISCTIM2 and maximum muting time
TIME_MAX are reset.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 451
Timing diagrams for discrepancy errors at sensor pair 1 or interruption of the light curtain
(if MUTING is not active)
Sensor pair 1 (MS_11 and MS_12) is not activated within discrepancy time
DISCTIM1.
The light curtain is interrupted even tho
ugh the MUTING function is not active.
Acknowledgment
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
452 Programming and Operating Manual, 10/2018, A5E02714440-AH
Behavior with stopped conveyor equipment
If, while the conveyor equipment has stopped, the monitoring for one of the following
reasons is to be deactivated:
To comply with discrepancy time DISCTIM1 or DISCTIM2
To comply with maximum muting time TIME_MAX
you must supply input STOP with a "1" signal for as long as the conveyor equipment is
stopped. As soon as the conveyor equipment is running again (STOP = 0), discrepancy
times DISCTIM1 and DISCTIM2 and maximum muting time TIME_MAX are reset.
WARNING
When STOP = 1, the discrepancy monitoring is shut down. During this time, if inputs
MSx1/MSx2 of a sensor pair both take a signal state of 1 due to an undetected error, e.g.,
because both muting sensors fail to 1, the error is not detected and the MUTING function
can be started unintentionally.
(S036)
Output DIAG
The DIAG output provides non-fail-safe information on errors for service purposes. You can
read out this information by means of operator control and monitoring systems or, if
applicable, you can evaluate it in your standard user program. DIAG bits are saved until
acknowledgment at input ACK.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 453
Structure of DIAG
Bit no.
Assignment
Possible error causes
Remedies
Bit 0 Discrepancy error or incorrect
discrepancy time DISCTIM 1 set-
ting for sensor pair 1
Malfunction in production se-
quence
Malfunction in production sequence
eliminated
Sensor defective
Check sensors
Wiring fault
Check wiring of sensors
Sensors are wired to different F-
I/O, and F-I/O fault, channel fault,
or communication error, or pas-
sivation by means of PASS_ON on
an F-I/O
For a solution, see the section "Struc-
ture of DIAG", bits 0 to 6 in DIAG
(Page 172)
Discrepancy time setting is too low If necessary, set a higher discrepancy
time
Discrepancy time setting is < 0 s or
> 3 s
Set discrepancy time in range between
0 s and 3 s
Bit 1 Discrepancy error or incorrect
discrepancy time DISCTIM 2 set-
ting for sensor pair 2
Same as Bit 0 Same as Bit 0
Bit 2 Maximum muting time exceeded or
incorrect muting time TIME_MAX
setting
Malfunction in production se-
quence
Malfunction in production sequence
eliminated
Maximum muting time setting is too
low
If necessary, set a higher maximum
muting time
Muting time setting is < 0 s or >
10 min
Set muting time in range from 0 s to
10 min
Bit 3 Light curtain interrupted and mut-
ing not active
Light curtain is defective
Check light curtain
Wiring fault Check wiring of light curtain (FREE
input)
F-I/O fault, channel fault, or com-
munication error, or passivation by
means of PASS_ON of F-I/O of
light curtain
(FREE input)
For a solution, see the section "Struc-
ture of DIAG", bits 0 to 6 in DIAG
(Page 172)
See other DIAG bits
Bit 4 Muting lamp is defective or cannot
be set
Muting lamp is defective
Replace muting lamp
Wiring fault
Check wiring of muting lamp
F-I/O fault, channel fault, or com-
munication error, or passivation by
means of PASS_ON of F-I/O of
muting lamp
For a solution, see the section "Struc-
ture of DIAG", bits 0 to 6 in DIAG
(Page 172)
Bit 5
Reserved
Bit 6
Reserved
Bit 7
Reserved
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
454 Programming and Operating Manual, 10/2018, A5E02714440-AH
Timing imprecision resulting from the update time of the time base used in the instruction:
For the first call in cycle n+1, the call time of the instruction relative to the start of the F-runtime
group is earlier than that in cycle n by the amount of Δ1, e.g. because parts of the safety pro-
gram of the F-runtime group before the call time of the instruction in cycle n+1 are skipped. For
the time update, the instruction takes account of time TBase_1 instead of the time T1 that has
actually elapsed in cycle n since the call.
The instruction is called a second time in cycle n+1. This does not involve another time update
(by Δ2).
For the call in cycle n+2, the call time of the instruction relative to the start of the F-runtime
group is later than that in cycle n by the amount of Δ3, e.g. because the F-runtime group was
interrupted by a higher priority interrupt before the call time of the instruction in cycle n+2. The
instruction took into account time TBase_1 + TBase_2 instead of the time T3 that has actually
elapsed in cycle n since the call. This would also be the case if no call occurred in cycle n+1.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 455
Example
The following example shows how the instruction works:
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
456 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.3.5
MUT_P: Parallel muting (STEP 7 Safety V15.1)
Description
This instruction performs parallel muting with two or four muting sensors.
Muting is a defined suppression of the protective function of light curtains. Light curtain
muting can be used to introduce goods or objects into the danger area monitored by the light
curtain without causing the machine to stop.
To utilize the muting function, at least two independently wired muting sensors must be
present. The use of two or four muting sensors and correct integration into the production
sequence must ensure that no persons enter the danger area while the light curtain is
muted.
Every call of the "Parallel muting" instruction must be assigned a data area in which the
instruction data are stored. The "Call options" dialog is automatically opened when the
instruction is inserted in the program for this reason. There you can create a data block
(single instance) (e.g., MUT_P_DB_1) or a multi-instance (e.g., MUT_P_Instance_1) for the
"Parallel muting" instruction. Once it is created, you can find the new data block in the project
tree in the "STEP 7 Safety" folder under "Program blocks > System blocks" or the multi-
instance as a local tag in the "Static" section of the block interface. For more information,
refer to the help on
STEP 7
.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
WARNING
When using an instruction with time processing, take the following timing imprecision
sources into account when determining your response times:
Known timing imprecision (based on standard systems) resulting from cyclic processing
Timing imprecision resulting from the update time of the time base used in the
instruction (see figure in section "Timing imprecision resulting from the update time of
the time base used in the instruction")
Tolerance of internal time monitoring in the F-CPU
For time values up to 200 ms, a maximum of 4 ms
For time values greater than or equal to 200 ms, a maximum of 2% of the (assigned)
time value
You must choose the interval between two call times of an instruction with time processing
in such a way that the required response times are achieved, taking into account the
possible timing imprecision.
(S034)
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 457
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
MS_11
Input
BOOL
Muting sensor 11
MS_12 Input BOOL Muting sensor 12
MS_21
Input
BOOL
Muting sensor 21
MS_22
Input
BOOL
Muting sensor 22
STOP
Input
BOOL
1=Conveyor system stopped
FREE
Input
BOOL
1=Light curtain uninterrupted
ENABLE
Input
BOOL
1=Enable MUTING
QBAD_MUT Input BOOL QBAD signal of the F-I/O or QBAD_O_xx signal /
inverted value status of the muting lamp channel
ACK
Input
BOOL
Acknowledgment of restart inhibit
DISCTIM1
Input
TIME
Discrepancy time of sensor pair 1 (0 to 3 s)
DISCTIM2
Input
TIME
Discrepancy time of sensor pair 2 (0 to 3 s)
TIME_MAX
Input
TIME
Maximum muting time (0 to 10 min)
Q
Output
BOOL
1= Enable, not off
MUTING
Output
BOOL
Display of muting is active
ACK_REQ
Output
BOOL
Acknowledgment necessary
FAULT
Output
BOOL
Group error
DIAG
Output
WORD
Non-fail safe service information
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x* When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1
x*
These versions have identical functions to version V1.0.
The output DIAG can now be correctly interconnected with the operand
of data type WORD.
1.2
x*
o
1.3 x* o o
1.4
x
x
x
o This version is no longer supported.
* S7
-300/400: When a restart inhibit (output FAULT = 1) and ENABLE = 1 is present, output ACK_REQ is set to 1 even if
not at least one muting sensor is activated. Use the DIAG bits 5 and 6 for additional information.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
458 Programming and Operating Manual, 10/2018, A5E02714440-AH
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the
F-CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
Schematic sequence of error-free muting procedure with 4 muting sensors (MS_11, MS_12, MS_21,
MS_22)
If muting sensors MS_11 and MS_12 are both activated by the product within DISCTIM1
(apply signal state = 1) and MUTING is enabled by setting the ENABLE input to 1, the
instruction starts the MUTING function. Enable signal Q remains 1, even when input
FREE = 0 (light curtain interrupted by product). The MUTING output for setting the muting
lamp switches to 1.
Note
The muting lamp can be monitored using the QBAD_MUT input. To do this, you must wire
the muting lamp to an output with wire break monitoring of an F
-I/O and supply the
QBAD_MUT input with the QBAD signal of the associated F
-
I/O or the QBAD_O_xx signal
/ with inverted value statues of the associated
channel. If QBAD_MUT = 1, muting is
terminated by the instruction. If monitoring of the muting lamp is not necessary, you do
not have to supply input QBAD_MUT.
F
-I/O that can promptly detect a wire break after activation of the muting operation must
be us
ed (
see manual for specific F-I/O
).
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 459
As long as both muting sensors MS_11 and MS_12 continue to be activated, the MUTING
function of the instruction causes Q to remain 1 and MUTING to remain 1 (so that the
product can pass through the light curtain without causing the machine to stop). Each of
the two muting sensors MS_11 and MS_12 may be switched to inactive (t < DISCTIM1)
for a short time (apply signal state 0).
Muting sensors MS_21 and MS_22 must both be activated (within DISCTIM2) before
muting sensors MS_11 and MS_12 are switched to inactive (apply signal state 0). In this
way, the instruction retains the MUTING function. (Q = 1, MUTING = 1).
Only if muting sensors MS_21 and MS_22 are both switched to inactive (product enables
sensors) is the MUTING function terminated (Q = 1, MUTING = 0). The maximum activation
time for the MUTING function is the time set at input TIME_MAX.
Note
The MUTING function is also started if the product passes the light curtain in the reverse
d
irection and the muting sensors are thus activated by the product in reverse order.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
460 Programming and Operating Manual, 10/2018, A5E02714440-AH
Timing diagrams for error-free muting procedure with 4 muting sensors
Schematic sequence of muting procedure with reflection light barriers
If reflection light barriers are used as muting sensors, they are generally arranged diagonally.
In general, this arrangement of reflection light barriers as muting sensors requires only two
light barriers, and only MS_11 and MS_12 are interconnected.
The sequence is similar to that of the muting procedure with 4 muting sensors. Step 3 is
omitted. In step 4, replace MS_21 and MS_22 with MS_11 and MS_12, respectively.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 461
Restart inhibit upon interruption of light curtain (MUTING is not active), as well as when errors occur
and during F-system startup
Enable signal Q cannot be set to 1 or becomes 0, if:
Light curtain is interrupted (e.g., by a person or material transport) while the MUTING
function is not active
Light curtain is (being) interrupted and the muting lamp monitoring at input QBAD_MUT is
set to 1
Light curtain is (being) interrupted and the MUTING function is not enabled by setting
input ENABLE to 1
Sensor pair 1 (MS_11 and MS_12) or sensor pair 2 (MS_21 and MS_22) is not activated
or deactivated during discrepancy time DISCTIM1 or DISCTIM2, respectively
The MUTING function is active longer than the maximum muting time TIME_MAX
Discrepancy times DISCTIM1 and DISCTIM2 have been set to values < 0 or > 3 s
Maximum muting time TIME_MAX has been set to a value< 0 or > 10 min
The F-system starts up (regardless of whether or not the light curtain is interrupted,
because the F-I/O is passivated after F-system startup and, thus, the FREE input is
initially supplied with 0)
In the identified cases, output FAULT (group error) is set to 1 (restart inhibit). If the MUTING
function is started, it will be terminated and the Muting output becomes 0.
User acknowledgment of restart inhibit (no muting sensor is activated or ENABLE = 0)
Enable signal Q becomes 1 again, when:
The light curtain is no longer interrupted
If present, errors are eliminated (see output DIAG)
and
A user acknowledgment with positive edge occurs at input ACK (see also Implementation
of user acknowledgment (Page 187)).
The FAULT output is set to 0. Output ACK_REQ = 1 (and DIAG bit 6) signals that user
acknowledgment at input ACK is required to eliminate the restart inhibit. The instruction sets
ACK_REQ = 1 as soon as the light curtain is no longer interrupted or the errors have been
eliminated. Once acknowledgment has occurred, the instruction resets ACK_REQ to 0.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
462 Programming and Operating Manual, 10/2018, A5E02714440-AH
User Acknowledgment of restart inhibit (at least one muting sensor is activated and ENABLE = 1)
Enable signal Q becomes 1 again, when:
If present, errors are eliminated (see output DIAG)
FREE occurs until a valid combination of muting sensors is detected
The FAULT output is set to 0. The MUTING function is restarted, if necessary, and the
MUTING output becomes 1 if a valid combination of muting sensors is detected. When
ENABLE = 1, output ACK_REQ = 1 (and DIAG bit 5) signals that FREE is necessary for
error elimination and for removal of the restart inhibit.*After successful FREE, ACK_REQ is
reset to 0 by the instruction.
Note
Once the maximum muting time is exceeded, TIME_MAX
is reset as soon as the MUTING
function is restarted.
FREE function
If an error cannot be corrected immediately, the FREE function can be used to free the
muting range. Enable signal Q and output MUTING =1 temporarily. The FREE function can
be used if:
ENABLE = 1
At least one muting sensor is activated
A user acknowledgment with rising edge at input ACK occurs twice within 4 s, and the
second user acknowledgment at input ACK remains at a signal state of 1
(acknowledgment button remains activated)
WARNING
When using the FREE function, the action must be observed. A dangerous situation must
be able to be interrupted at any time by releasing the acknowledgment button. The
acknowledgment button must be mounted in such a way the entire danger area can be
observed.
(S037)
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 463
Timing diagrams for discrepancy errors at sensor pair 1 or interruption of the light curtain
(MUTING is not active)
Sensor pair 1 (MS_11 and MS_22) is not activated within discrepancy time
DISCTIM1.
The light curtain is interrupted even though there is no enable (ENABLE=0)
FREE function
Acknowledgment
Behavior with stopped conveyor equipment
If, while the conveyor equipment has stopped, the monitoring for one of the following
reasons is to be deactivated:
To comply with discrepancy time DISCTIM1 or DISCTIM2
To comply with maximum muting time TIME_MAX
You must supply input STOP with a "1" signal for as long as the conveyor equipment is
stopped. As soon as the conveyor equipment is running again (STOP = 0), discrepancy
times DISCTIM1 and DISCTIM2 and maximum muting time TIME_MAX are reset.
WARNING
When STOP = 1 or ENABLE = 0, discrepancy monitoring is shut down. During this time, if
inputs MSx1/MSx2 of a sensor pair both take a signal state of 1 due to an undetected error,
e.g., because both muting sensors fail to 1, the fault is not detected and the MUTING
function can be started unintentionally (when ENABLE =1).
(S038)
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
464 Programming and Operating Manual, 10/2018, A5E02714440-AH
Output DIAG
The DIAG output provides non-fail-safe information on errors for service purposes. You can
read out this information by means of operator control and monitoring systems or, if
applicable, you can evaluate it in your standard user program. DIAG bits 0 to 6 are saved
until acknowledgment at input ACK.
Structure of DIAG
Bit
no.
Assignment
Possible error causes
Remedies
Bit
0
Discrepancy error or incorrect
discrepancy time DISCTIM 1
setting for sensor pair 1
Malfunction in production sequence Malfunction in production se-
quence eliminated
Sensor defective Check sensors
Wiring fault
Check wiring of sensors
Sensors are wired to different F-I/O, and F-
I/O fault, channel fault, or communication
error, or passivation by means of PASS_ON
on an F-I/O
For a solution, see the section
"Structure of DIAG", bits 0 to 6 in
DIAG (Page 172)
Discrepancy time setting is too low If necessary, set a higher discrep-
ancy time
Discrepancy time setting is < 0 s or > 3 s Set discrepancy time in range
between 0 s and 3 s
Bit
1
Discrepancy error or incorrect
discrepancy time DISCTIM 2
setting for sensor pair 2
Same as Bit 0 Same as Bit 0
Bit
2
Maximum muting time exceeded
or incorrect muting time
TIME_MAX setting
Malfunction in production sequence Malfunction in production se-
quence eliminated
Maximum muting time setting is too low If necessary, set a higher maxi-
mum muting time
Muting time setting is < 0 s or > 10 min Set muting time in range from 0 s
to 10 min
Bit
3
Light curtain interrupted and
muting not active
ENABLE = 0 Set ENABLE = 1
Light curtain is defective
Check light curtain
Wiring fault Check wiring of light curtain (FREE
input)
F-I/O fault, channel fault, or communication
error, or passivation by means of PASS_ON
of F-I/O of light curtain
(FREE input)
For a solution, see the section
"Structure of DIAG", bits 0 to 6 in
DIAG (Page 172)
Startup of F-system
For FREE, see DIAG Bit 5
See other DIAG bits
Bit
4
Muting lamp is defective or can-
not be set
Muting lamp is defective
Replace muting lamp
Wiring fault
Check wiring of muting lamp
F-I/O fault, channel fault, or communication
error, or passivation by means of PASS_ON
of F-I/O of muting lamp
For a solution, see the section
"Structure of DIAG", bits 0 to 6 in
DIAG (Page 172)
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 465
Bit
no.
Assignment
Possible error causes
Remedies
Bit
5
FREE is necessary See other DIAG bits Two rising edges at ACK within 4
s, and activate acknowledgment
button until ACK_REQ = 0
Bit
6
Acknowledgment necessary
Bit
7
State of output Q
Bit
8
State of output MUTING
Bit
9
FREE active
Bit
10
Reserved
...
Bit
15
Reserved
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
466 Programming and Operating Manual, 10/2018, A5E02714440-AH
Timing imprecision resulting from the update time of the time base used in the instruction:
For the first call in cycle n+1, the call time of the instruction relative to the start of the F-runtime
group is earlier than that in cycle n by the amount of Δ1, e.g. because parts of the safety pro-
gram of the F-runtime group before the call time of the instruction in cycle n+1 are skipped. For
the time update, the instruction takes account of time TBase_1 instead of the time T1 that has
actually elapsed in cycle n since the call.
The instruction is called a second time in cycle n+1. This does not involve another time update
(by Δ2).
For the call in cycle n+2, the call time of the instruction relative to the start of the F-runtime
group is later than that in cycle n by the amount of Δ3, e.g. because the F-runtime group was
interrupted by a higher priority interrupt before the call time of the instruction in cycle n+2. The
instruction took into account time TBase_1 + TBase_2 instead of the time T3 that has actually
elapsed in cycle n since the call. This would also be the case if no call occurred in cycle n+1.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 467
Example
The following example shows how the instruction works:
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
468 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.3.6
EV1oo2DI: 1oo2 evaluation with discrepancy analysis (STEP 7 Safety V15.1)
Description
This instruction implements a 1oo2 evaluation of two single-channel sensors combined with
a discrepancy analysis.
Output Q is set to 1, if the signal states of inputs IN1 and IN2 both equal 1 and no
discrepancy error DISC_FLT is stored. if the signal state of one or both inputs is 0, output Q
is set to 0.
As soon as the signal states of inputs IN1 and IN2 are different, the discrepancy time
DISCTIME is started. If the signal states of the two inputs are still different once the
discrepancy time expires, a discrepancy error is detected and DISC_FLT is set to 1 (restart
inhibit).
If the discrepancy between inputs IN1 and IN2 is no longer detected, the discrepancy error is
acknowledged according to the parameter assignment of ACK_NEC:
If ACK_NEC = 0, the acknowledgment is automatic.
If ACK_NEC = 1, you must use a rising edge at input ACK to acknowledge the
discrepancy error.
The output ACK_REQ = 1 signals that a user acknowledgment at input ACK is necessary to
acknowledge the discrepancy error (cancel the restart inhibit). The instruction sets
ACK_REQ = 1 as soon as discrepancy is no longer detected. After acknowledgment or if,
prior to acknowledgment, there is once again a discrepancy between inputs IN1 and IN2, the
instruction resets ACK_REQ to 0.
Output Q can never be set to 1 if the discrepancy time setting is < 0 or > 60 s. In this case,
output DISC_FLT is also set to 1 (restart inhibit). The call interval of the safety program (e.g.,
OB 35) must be less than the discrepancy time setting.
Every call of the "1oo2 evaluation with discrepancy analysis" instruction must be assigned a
data area in which the instruction data are stored. The "Call options" dialog is automatically
opened when the instruction is inserted in the program for this reason. There you can create
a data block (single instance) (e.g., EV1oo2DI_DB_1) or a multi-instance (e.g.,
EV1oo2DI_Instance_1) for the "1oo2 evaluation with discrepancy analysis" instruction. Once
it is created, you can find the new data block in the project tree in the "STEP 7 Safety" folder
under "Program blocks > System blocks" or the multi-instance as a local tag in the "Static"
section of the block interface. For more information, refer to the help on
STEP 7
.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
WARNING
The ACK_NEC tag must not be assigned a value of 0 unless an automatic restart of the
affected process is otherwise excluded.
(S033)
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 469
WARNING
When using an instruction with time processing, take the following timing imprecision
sources into account when determining your response times:
Known timing imprecision (based on standard systems) resulting from cyclic processing
Timing imprecision resulting from the update time of the time base used in the
instruction (see figure in section "Timing imprecision resulting from the update time of
the time base used in the instruction")
Tolerance of internal time monitoring in the F-CPU
For time values up to 200 ms, a maximum of 4 ms
For time values greater than or equal to 200 ms, a maximum of 2% of the (assigned)
time value
You must choose the interval between two call times of an instruction with time processing
in such a way that the required response times are achieved, taking into account the
possible timing imprecision.
(S034)
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN1
Input
BOOL
Sensor 1
IN2
Input
BOOL
Sensor 2
DISCTIME
Input
TIME
Discrepancy time (0 to 60 s)
ACK_NEC
Input
BOOL
1 = acknowledgment necessary for discrepancy error
ACK
Input
BOOL
Acknowledgment of discrepancy error
Q
Output
BOOL
Output
ACK_REQ
Output
BOOL
1 = acknowledgment required
DISC_FLT
Output
BOOL
1 = discrepancy error
DIAG
Output
BYTE
Non-fail safe service information
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
470 Programming and Operating Manual, 10/2018, A5E02714440-AH
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1 x o These versions have identical functions to version V1.0.
1.2
x
o
o
1.3
x
x
x
o This version is no longer supported.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the
F-CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
Activating inputs IN1 and IN2
Inputs IN1 and IN2 must both be activated in such a way that their safe state is 0.
Example with QBAD or QBAD_I_xx signal
For non-equivalent signals you need to OR the input (IN1 and IN2) with which you assign the
encoder signal to the safe state 1, with the QBAD signal of the associated F-I/O or the
QBAD_I_xx signal of the associated channel (with S7-300/400 F-CPUs) and negate the
result. Signal state 0 is then at input IN1 or IN2 when fail-safe values are output.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 471
Example with value status
For nonequivalent signals, you have to negate the input (IN1 or IN2) with which you have
assigned the encoder signal to a safe state of 1 and AND it with the value status of the
associated channel. Signal state 0 is then at input IN1 or IN2 when fail-safe values are
output.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
472 Programming and Operating Manual, 10/2018, A5E02714440-AH
Timing diagrams EV1oo2DI
If ACK_NEC = 1:
Startup characteristics
Note
If the sensors at inputs IN1 and IN2 are assigned to different F
-I/O, it is possible that the
fail
-safe values are output for different lengths of time following startup of the F-system due
to different startup characteristics of the F
-I/O. If the signal states of inputs IN1 and IN2
remain different after the discrepancy time DISCTIME has expired, a discrepancy error is
detected after the F
-system starts up.
If ACK_NEC = 1 yo
u must acknowledge the discrepancy error with a rising edge at input
ACK.
Output DIAG
The DIAG output provides non-fail-safe information on errors for service purposes. You can
read out this information by means of operator control and monitoring systems or, if
applicable, you can evaluate it in your standard user program. DIAG bits are saved until
acknowledgment at input ACK.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 473
Structure of DIAG
Bit no.
Assignment
Possible error causes
Remedies
Bit 0 Discrepancy error or incorrect dis-
crepancy time setting
(= status of DISC_FLT)
Sensor defective
Check sensors
Wiring fault Check wiring of sensors
Sensors are wired to different F-I/O,
and F-I/O fault, channel fault, or
communication error, or passivation
by means of PASS_ON on an F-I/O
For a solution, see the section
"Structure of DIAG", bits 0 to 6 in
DIAG (Page 172)
Discrepancy time setting is too low If necessary, set a higher dis-
crepancy time
Discrepancy time setting is < 0 s or
> 60 s
Set discrepancy time in range
between 0 s and 60 s
Bit 1 For discrepancy errors: last signal
state change was at input IN1
Bit 2 For discrepancy errors: last signal
state change was at input IN2
Bit 3
Reserved
Bit 4
Reserved
Bit 5 For discrepancy errors: input ACK
has a permanent signal state of 1
Acknowledgment button defective
Replace acknowledgment button
Wiring fault Check wiring of acknowledgment
button
Bit 6
Acknowledgment necessary
Bit 7
State of output Q
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
474 Programming and Operating Manual, 10/2018, A5E02714440-AH
Timing imprecision resulting from the update time of the time base used in the instruction:
For the first call in cycle n+1, the call time of the instruction relative to the start of the F-runtime
group is earlier than that in cycle n by the amount of Δ1, e.g. because parts of the safety pro-
gram of the F-runtime group before the call time of the instruction in cycle n+1 are skipped. For
the time update, the instruction takes account of time TBase_1 instead of the time T1 that has
actually elapsed in cycle n since the call.
The instruction is called a second time in cycle n+1. This does not involve another time update
(by Δ2).
For the call in cycle n+2, the call time of the instruction relative to the start of the F-runtime
group is later than that in cycle n by the amount of Δ3, e.g. because the F-runtime group was
interrupted by a higher priority interrupt before the call time of the instruction in cycle n+2. The
instruction took into account time TBase_1 + TBase_2 instead of the time T3 that has actually
elapsed in cycle n since the call. This would also be the case if no call occurred in cycle n+1.
Example
The following example shows how the instruction works:
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 475
13.3.7
FDBACK: Feedback monitoring (STEP 7 Safety V15.1)
Description
This instruction implements feedback monitoring.
The signal state of output Q is checked to see whether it corresponds to the inverse signal
state of the feedback input FEEDBACK.
Output Q is set to 1 as soon as input ON = 1. Requirement for this is that the feedback input
FEEDBACK = 1 and no feedback error is saved.
Output Q is reset to 0, as soon as input ON = 0 or if a feedback error is detected.
A feedback error ERROR = 1 is detected if the inverse signal state of the feedback input
FEEDBACK (to input Q) does not follow the signal state of output Q within the maximum
tolerable feedback time. The feedback error is saved.
If a discrepancy is detected between the feedback input FEEDBACK and the output Q after
a feedback error, the feedback error is acknowledged in accordance with the parameter
assignment of ACK_NEC:
If ACK_NEC = 0, the acknowledgment is automatic.
If ACK_NEC = 1, you must acknowledge the feedback error with a rising edge at input
ACK.
The ACK_REQ = 1 output then signals that a user acknowledgment is necessary at input
ACK to acknowledge the feedback error. Following an acknowledgment, the instruction
resets ACK_REQ to 0.
To avoid a feedback errors from being detected and acknowledgment from being required
when the F-I/O controlled by the Q output are passivated, you need to supply input
QBAD_FIO with the QBAD signal of the associated F-I/O or the QBAD_O_xx signal /
inverted value status of the associated channel.
Every call of the "Feedback monitoring" instruction must be assigned a data area in which
the instruction data are stored. The "Call options" dialog is automatically opened when the
instruction is inserted in the program for this reason. There you can create a data block
(single instance) (e.g., FDBACK_DB_1) or a multi-instance (e.g., FDBACK_Instance_1) for
the "Feedback monitoring" instruction. Once it is created, you can find the new data block in
the project tree in the "STEP 7 Safety" folder under "Program blocks > System blocks" or the
multi-instance as a local tag in the "Static" section of the block interface. For more
information, refer to the help on
STEP 7
.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
476 Programming and Operating Manual, 10/2018, A5E02714440-AH
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
WARNING
The ACK_NEC tag must not be assigned a value of 0 unless an automatic restart of the
affected process is otherwise excluded.
(S033)
WARNING
When using an instruction with time processing, take the following timing imprecision
sources into account when determining your response times:
Known timing imprecision (based on standard systems) resulting from cyclic processing
Timing imprecision resulting from the update time of the time base used in the
instruction (see figure in section "Timing imprecision resulting from the update time of
the time base used in the instruction")
Tolerance of internal time monitoring in the F-CPU
For time values up to 200 ms, a maximum of 4 ms
For time values greater than or equal to 200 ms, a maximum of 2% of the (assigned)
time value
You must choose the interval between two call times of an instruction with time processing
in such a way that the required response times are achieved, taking into account the
possible timing imprecision
(S034)
.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
ON
Input
BOOL
1= Enable output
FEEDBACK
Input
BOOL
Feedback input
QBAD_FIO Input BOOL QBAD signal of the F-I/O or QBAD_O_xx signal /
inverted value status of the Q output
ACK_NEC
Input
BOOL
1=Acknowledgment necessary
ACK Input BOOL Acknowledgment
FDB_TIME
Input
TIME
Feedback time
Q
Output
BOOL
Output
ERROR
Output
BOOL
Feedback error
ACK_REQ
Output
BOOL
Acknowledgment request
DIAG
Output
BYTE
Non-fail safe service information
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 477
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x Version 1.0 requires that the F_TOF block with the number FB 186 is
available in the project tree in the "Program blocks/System
blocks/STEP 7 Safety" folder.
When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically. If you
want to compile a migrated safety program with
STEP 7 Safety Ad-
vanced
for the first time, we recommend that you first update to the
latest available version of the instruction. You will then avoid number
conflicts.
1.1
x
These versions are functionally identical to version V1.0, but do not
require the F_TOF block to have a particular number.
1.2
x
o
1.3
x
o
o
1.4
x
o
o
1.5
x
x
x
o This version is no longer supported.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the
F-CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
Interconnection example
Sent to the FEEDBACK input of the instruction
from output Q of the instruction
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
478 Programming and Operating Manual, 10/2018, A5E02714440-AH
Output DIAG
The DIAG output provides non-fail-safe information on errors for service purposes. You can
read out this information by means of operator control and monitoring systems or, if
applicable, you can evaluate it in your standard user program. DIAG bits 0, 2, and 5 are
saved until acknowledgment at input ACK.
Structure of DIAG
Bit
no.
Assignment
Possible error causes
Remedies
Bit
0
Feedback error or incorrect feed-
back time setting
(= state of ERROR)
Feedback time setting < 0
Set feedback time > 0
Feedback time setting is too low If necessary, set a higher feedback
time
Wiring fault Check wiring of actuator and feed-
back contact
Actuator or feedback contact is defective Check actuator and feedback con-
tact
I/O fault or channel fault of feedback input
Check I/O
Bit
1
Passivation of F-I/O/channel
controlled by output Q (= state of
QBAD_FIO)
F-I/O fault, channel fault, or communication
error, or passivation by means of PASS_ON
of F-I/O
For a solution, see the section
"Structure of DIAG", bits 0 to 6 in
DIAG (Page 172)
Bit
2
After feedback error: feedback
input has permanent signal state
of 0
F-I/O fault or channel fault of feedback input
Check I/O
Feedback contact is defective
Check feedback contact
F-I/O fault, channel fault, or communication
error, or passivation by means of PASS_ON
of F-I/O of feedback input
For a solution, see the section
"Structure of DIAG", bits 0 to 6 in
DIAG (Page 172)
Bit
3
Reserved
Bit
4
Reserved
Bit
5
For feedback error: input ACK
has a permanent signal state of 1
Acknowledgment button defective
Check acknowledgment button
Wiring fault Check wiring of acknowledgment
button
Bit
6
Acknowledgment required
(= state of ACK_REQ)
Bit
7
State of output Q
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 479
Timing imprecision resulting from the update time of the time base used in the instruction:
For the first call in cycle n+1, the call time of the instruction relative to the start of the F-runtime
group is earlier than that in cycle n by the amount of Δ1, e.g. because parts of the safety pro-
gram of the F-runtime group before the call time of the instruction in cycle n+1 are skipped. For
the time update, the instruction takes account of time TBase_1 instead of the time T1 that has
actually elapsed in cycle n since the call.
The instruction is called a second time in cycle n+1. This does not involve another time update
(by Δ2).
For the call in cycle n+2, the call time of the instruction relative to the start of the F-runtime
group is later than that in cycle n by the amount of Δ3, e.g. because the F-runtime group was
interrupted by a higher priority interrupt before the call time of the instruction in cycle n+2. The
instruction took into account time TBase_1 + TBase_2 instead of the time T3 that has actually
elapsed in cycle n since the call. This would also be the case if no call occurred in cycle n+1.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
480 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example
The following example shows how the instruction for S7-300/400 F-CPUs works:
The following example shows how the instruction for S7-1200/1500 F-CPUs works:
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 481
13.3.8
SFDOOR: Safety door monitoring (STEP 7 Safety V15.1)
Description
This instruction implements safety door monitoring.
Enable signal Q is reset to 0 as soon as one of the inputs IN1 or IN2 take a signal state of 0
(safety door is opened). The enable signal can be reset to 1, only if:
Inputs IN1 and IN2 both take a signal state of 0 prior to opening the door (safety door has
been completely opened)
Inputs IN1 and IN2 then both take a signal state of 1 (safety door is closed)
An acknowledgment occurs
The acknowledgment for the enable takes place according to the parameter assignment at
input ACK_NEC:
If ACK_NEC = 0, the acknowledgment is automatic.
If ACK_NEC = 1, you must use a rising edge at input ACK for acknowledging the enable.
Output ACK_REQ = 1 is used to signal that a user acknowledgment is required at input ACK
for the acknowledgment. The instruction sets ACK_REQ = 1 as soon as the door is closed.
Following an acknowledgment, the instruction resets ACK_REQ to 0.
In order for the instruction to recognize whether inputs IN1 and IN2 are 0 merely due to
passivation of the associated F-I/O, you need to supply inputs QBAD_IN1 or QBAD_IN2 with
the QBAD signal of the associated F-I/O or QBAD_I_xx signal / inverted value status of the
associated channel. Among other things, this will prevent you from having to open the safety
door completely prior to an acknowledgment in the event the F-I/O are passivated.
Every call of the "Safety door monitoring" instruction must be assigned a data area in which
the instruction data are stored. The "Call options" dialog is automatically opened when the
instruction is inserted in the program for this reason. There you can create a data block
(single instance) (e.g., SFDOOR_DB_1) or a multi-instance (e.g., SFDOOR_Instance_1) for
the "Safety door monitoring" instruction. Once it is created, you can find the new data block
in the project tree in the "STEP 7 Safety" folder under "Program blocks > System blocks" or
the multi-instance as a local tag in the "Static" section of the block interface. For more
information, refer to the help on
STEP 7
.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
482 Programming and Operating Manual, 10/2018, A5E02714440-AH
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
WARNING
The ACK_NEC tag must not be assigned a value of 0 unless an automatic restart of the
affected process is otherwise excluded.
(S033)
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN1
Input
BOOL
Input 1
IN2
Input
BOOL
Input 2
QBAD_IN1 Input BOOL QBAD signal of the F-I/O or QBAD_O_xx signal / in-
verted value status of the channel of input IN1
QBAD_IN2 Input BOOL QBAD signal of the F-I/O or QBAD_O_xx signal / in-
verted value status of the channel of input IN2
OPEN_NEC
Input
BOOL
1= Open necessary at startup
ACK_NEC
Input
BOOL
1=Acknowledgment necessary
ACK
Input
BOOL
Acknowledgment
Q
Output
BOOL
1= Enable, safety door closed
ACK_REQ Output BOOL Acknowledgment request
DIAG
Output
BYTE
Non-fail safe service information
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1
x
o
These versions have identical functions to version V1.0.
1.2
x
o
o
1.3
x
x
x
o This version is no longer supported.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the F-
CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 483
Interconnection example
You must interconnect the NC contact of position switch 1 of the safety door at input IN1 and
the NO contact of position switch 2 at input IN2. Position switch 1 must be mounted in such a
way that it is positively operated when the safety door is open. Position switch 2 must be
mounted in such a way that it is operated when the safety door is closed.
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
484 Programming and Operating Manual, 10/2018, A5E02714440-AH
Startup characteristics
After an F-system startup, enable signal Q is reset to 0. The acknowledgment for the enable
takes place according to the parameter assignment at inputs OPEN_NEC and ACK_NEC:
When OPEN_NEC = 0, an automatic acknowledgment occurs
independently
of
ACK_NEC, as soon as the two inputs IN1 and IN2 take signal state 1 for the first time
following reintegration of the associated F-I/O (safety door is closed).
When OPEN_NEC = 1
or
if at least one of the IN1 and IN2 inputs still has a signal state of
0 after reintegration of the associated F-I/O, an automatic acknowledgment occurs
according
to ACK_NEC or you have to use a rising edge at input ACK for the enable.
Prior to acknowledgment, inputs IN1 and IN2 both have to take a signal state of 0 (safety
door has been completely opened) followed by a signal state of 1 (safety door is closed).
WARNING
The OPEN_NEC tag must not be assigned a value of 0 unless an automatic restart of the
affected process is otherwise excluded.
(S039)
Output DIAG
The DIAG output provides non-fail-safe information on errors for service purposes. You can
read out this information by means of operator control and monitoring systems or, if
applicable, you can evaluate it in your standard user program.
Structure of DIAG
Bit no.
Assignment
Possible error causes
Remedies
Bit 0
Reserved
Bit 1 Signal state 0 is missing at both IN1
and IN2 inputs
Safety door was not completely
opened when OPEN_NEC = 1 after
F-system startup
Open safety door completely
Open safety door was not com-
pletely opened
Open safety door completely
Wiring fault
Check wiring of position switch
Position switch is defective
Check position switch
Position switch is incorrectly ad-
justed
Adjust position switch properly
Bit 2 Signal state 1 is missing at both IN1
and IN2 inputs
Safety door was not closed Close safety door
Wiring fault
Check wiring of position switch
Position switch is defective Check position switch
Position switch is incorrectly ad-
justed
Adjust position switch properly
Bit 3 QBAD_IN1 and/or QBAD_IN2 = 1 F-I/O fault, channel fault, or com-
munication error, or passivation by
means of PASS_ON of F-I/O or
channel of IN1 and/or IN2
For a solution, see the section
"Structure of DIAG", bits 0 to 6 in
DIAG (Page 172)
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 485
Bit no.
Assignment
Possible error causes
Remedies
Bit 4
Reserved
Bit 5 If enable is missing: input ACK has a
permanent signal state of 1
Acknowledgment button defective Check acknowledgment button
Wiring fault Check wiring of acknowledgment
button
Bit 6 Acknowledgment required
(= state of ACK_REQ)
Bit 7
State of output Q
Example
The following example shows how the instruction for S7-300/400 F-CPUs works:
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
486 Programming and Operating Manual, 10/2018, A5E02714440-AH
The following example shows how the instruction for S7-1200/1500 F-CPUs works:
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 487
13.3.9
ACK_GL: Global acknowledgment of all F-I/O in an F-runtime group
(STEP 7 Safety V15.1)
Description
This instruction creates an acknowledgment for the simultaneous reintegration of all F-I/O or
channels of the F-I/O of an F-runtime group after communication errors, F-I/O errors, or
channel faults.
A user acknowledgment (Page 187) with a positive edge at input ACK_GLOB is required for
reintegration. The acknowledgment occurs analogously to the user acknowledgment via the
ACK_REI tag of the F-I/O DB (Page 168), but it acts simultaneously on all F-I/O of the
F-runtime group in which the instruction is called.
If you use the instruction ACK_GL, you do not have to provide a user acknowledgment for
each F-I/O of the F-runtime group via the ACK_REI tag of the F-I/O DB.
Every call of the "Global acknowledgment of all F-I/O of a runtime group" instruction must be
assigned a data area in which the instruction data are stored. The "Call options" dialog is
automatically opened when the instruction is inserted in the program for this reason. There
you can create a data block (single instance) (e.g., ACK_GL_DB_1) or a multi-instance (e.g.,
ACK_GL_Instance_1) for the "Global acknowledgment of all F-I/O of a runtime group"
instruction. Once it is created, you can find the new data block in the project tree in the
"STEP 7 Safety" folder under "Program blocks > System blocks" or the multi-instance as a
local tag in the "Static" section of the block interface. For more information, refer to the help
on
STEP 7
.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Note
An acknowledgment via the ACK_GL instruction is
only possible if the tag ACK_REI of the F-
I/O DB = 0. Accordingly, an acknowledgment via the tag ACK_REI of the F
-I/O DB is only
possible if the input ACK_GLOB of the instruction
= 0.
The instruction is only allowed to be called once per F
-runtime group.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
ACK_GLOB
Input
BOOL
1=acknowledgment for reintegration
13.3 Safety functions
SIMATIC Safety - Configuring and Programming
488 Programming and Operating Manual, 10/2018, A5E02714440-AH
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1 x o These versions have identical functions to version V1.0.
1.2
x
o
o
1.3
x
x
x
o This version is no longer supported.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the
F-CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
Example
The following example shows how the instruction works:
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 489
13.4
Timer operations
13.4.1
TP: Generate pulse (STEP 7 Safety V15.1)
Description
You can use the "Generate pulse" instruction to set output Q for a programmed period. The
instruction is started if the result of logic operation (RLO) changes from "0" to "1" (positive
edge) at input IN. The programmed period PT starts running when the instruction starts.
Output Q is set for period PT, regardless of the subsequent sequence of the input signal.
Also the detection of a new positive signal edge does not influence the signal state at output
Q as long as period PT runs.
You can query the current time value at the output ET. The time value begins at T#0s and
ends when the value of period PT is reached. If period PT is reached and the signal state at
input IN is "0", output ET is reset.
Every call of the "Generate pulse" instruction must be assigned a data area in which the
instruction data are stored. The "Call options" dialog is automatically opened when the
instruction is inserted in the program for this reason. There you can create a data block
(single instance) (e.g., F_IEC_Timer_DB_1) or a multi-instance (e.g.,
F_IEC_Timer_Instance_1) for the "Generate pulse" instruction. Once it is created, you can
find the new data block in the project tree in the "STEP 7 Safety" folder under "Program
blocks > System blocks" or the multi-instance as a local tag in the "Static" section of the
block interface. For more information, refer to the
help on STEP 7
.
WARNING
When using an instruction with time processing, take the following timing imprecision
sources into account when determining your response times:
Known timing imprecision (based on standard systems) resulting from cyclic processing
Timing imprecision resulting from the update time of the time base used in the
instruction (see figure in section "Timing imprecision resulting from the update time of
the time base used in the instruction").
Tolerance of internal time monitoring in the F-CPU
For time values up to 200 ms, a maximum of 4 ms
For time values greater than or equal to 200 ms, a maximum of 2% of the (assigned)
time value
You must choose the interval between two call times of an instruction with time processing
in such a way that the required response times are achieved, taking into account the
possible timing imprecision.
(S034)
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
490 Programming and Operating Manual, 10/2018, A5E02714440-AH
The operating system resets the instances of the "Generate pulse" instruction on a startup of
the F-system.
Note
The
functionality of this instruction differs from the corresponding standard TP instruction in
the following points:
If the instruction is called while the time is running with PT = 0 ms, the outputs Q and ET
are reset.
If the instruction is called with PT < 0 ms, the outputs Q and ET are reset.
To restart the pulse, a new rising signal edge at input IN is required once PT is greater
than
0 again.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN
Input
BOOL
Start input
PT
Input
TIME
Duration of pulse; must be positive.
Q
Output
BOOL
Pulse output
ET
Output
TIME
Current time value
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1
x
o
These versions have identical functions to version V1.0.
1.2
x
o
o
1.3
x
o
o
1.4
x
x
x
o This version is no longer supported.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the F-
CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 491
Pulse diagram
The following figure shows the pulse diagram of the instruction "Generate pulse":
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
492 Programming and Operating Manual, 10/2018, A5E02714440-AH
Timing imprecision resulting from the update time of the time base used in the instruction:
For the first call in cycle n+1, the call time of the instruction relative to the start of the F-runtime
group is earlier than that in cycle n by the amount of Δ1, e.g. because parts of the safety pro-
gram of the F-runtime group before the call time of the instruction in cycle n+1 are skipped. For
the time update, the instruction takes account of time TBase_1 instead of the time T1 that has
actually elapsed in cycle n since the call.
The instruction is called a second time in cycle n+1. This does not involve another time update
(by Δ2).
For the call in cycle n+2, the call time of the instruction relative to the start of the F-runtime
group is later than that in cycle n by the amount of Δ3, e.g. because the F-runtime group was
interrupted by a higher priority interrupt before the call time of the instruction in cycle n+2. The
instruction took into account time TBase_1 + TBase_2 instead of the time T3 that has actually
elapsed in cycle n since the call. This would also be the case if no call occurred in cycle n+1.
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 493
Example
The following example shows how the instruction works:
If the signal state of operand "TagIn_1" changes from "0" to "1", the "Generate pulse"
instruction is started and the period assigned at input PT (100 ms) runs, regardless of the
further course of operand "TagIn_1".
Operand "TagOut" at output Q has signal state "1" as long as the period is running. Operand
""F_DB_1".Tag_ET" contains the current time value.
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
494 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.4.2
TON: Generate on-delay (STEP 7 Safety V15.1)
Description
You use the "Generate on-delay" instruction to delay the setting of output Q by the assigned
period PT. The instruction is started if the result of logic operation (RLO) changes from "0" to
"1" (positive edge) at input IN. The programmed period PT starts running when the
instruction starts. When period PT has expired, output Q is set to signal state "1". Output Q
remains set as long as the start input is set to "1". When the signal state at the start input
changes from "1" to "0", output Q is reset. The time function is restarted when a new positive
signal edge is detected at the start input.
You can query the current time value at the output ET. The time value begins at T#0s and
ends when the value of period PT is reached. Output ET is reset, as soon as the signal state
at input IN changes to "0".
Every call of the "Generate on-delay" instruction must be assigned a data area in which the
instruction data are stored. The "Call options" dialog is automatically opened when the
instruction is inserted in the program for this reason. There you can create a data block
(single instance) (e.g., F_IEC_Timer_DB_1) or a multi-instance (e.g.,
F_IEC_Timer_Instance_1) for the "Generate on-delay" instruction. Once it is created, you
can find the new data block in the project tree in the "STEP 7 Safety" folder under "Program
blocks > System blocks" or the multi-instance as a local tag in the "Static" section of the
block interface. For more information, refer to the
help on STEP 7
.
WARNING
When using an instruction with time processing, take the following timing imprecision
sources into account when determining your response times:
Known timing imprecision (based on standard systems) resulting from cyclic processing
Timing imprecision resulting from the update time of the time base used in the
instruction (see figure in section "Timing imprecision resulting from the update time of
the time base used in the instruction")
Tolerance of internal time monitoring in the F-CPU
For time values up to 200 ms, a maximum of 4 ms
For time values greater than or equal to 200 ms, a maximum of 2% of the (assigned)
time value
You must choose the interval between two call times of an instruction with time processing
in such a way that the required response times are achieved, taking into account the
possible timing imprecision.
(S034)
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 495
The operating system resets the instances of the "Generate on-delay" instruction on a
startup of the F-system.
Note
The functionality of this instruction differs from the corresponding standard TON instruction in
the following points:
If the instruction is called while the time is running with PT = 0 ms, the output ET is reset.
If the instruction is called with PT < 0 ms, the outputs Q and ET are reset.
To rest
art the on-delay, a new rising signal edge at input IN is required once PT is greater
than
0 again.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN
Input
BOOL
Start input
PT
Input
TIME
Duration of on-delay; must be positive.
Q
Output
BOOL
Output that is set after expiration of time PT.
ET
Output
TIME
Current time value
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1
x
o
These versions have identical functions to version V1.0.
1.2
x
o
o
1.3
x
o
o
1.4
x
x
x
o This version is no longer supported.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the F-
CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
496 Programming and Operating Manual, 10/2018, A5E02714440-AH
Pulse diagram
The following figure shows the pulse diagram of the instruction "Generate on-delay":
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 497
Timing imprecision resulting from the update time of the time base used in the instruction:
For the first call in cycle n+1, the call time of the instruction relative to the start of the F-runtime
group is earlier than that in cycle n by the amount of Δ1, e.g. because parts of the safety pro-
gram of the F-runtime group before the call time of the instruction in cycle n+1 are skipped. For
the time update, the instruction takes account of time TBase_1 instead of the time T1 that has
actually elapsed in cycle n since the call.
The instruction is called a second time in cycle n+1. This does not involve another time update
(by Δ2).
For the call in cycle n+2, the call time of the instruction relative to the start of the F-runtime
group is later than that in cycle n by the amount of Δ3, e.g. because the F-runtime group was
interrupted by a higher priority interrupt before the call time of the instruction in cycle n+2. The
instruction took into account time TBase_1 + TBase_2 instead of the time T3 that has actually
elapsed in cycle n since the call. This would also be the case if no call occurred in cycle n+1.
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
498 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example
The following example shows how the instruction works:
When the signal state of operand "TagIn_1" changes from "0" to "1", the "Generate on-delay"
instruction is started and the period assigned at input PT (1 s) runs.
Operand "TagOut" at output Q feeds signal state "1" when the period has elapsed and
remains set as long as operand "TagIn_1" still feeds signal state "1". Operand
""F_DB_1".Tag_ET" contains the current time value.
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 499
13.4.3
TOF: Generate off-delay (STEP 7 Safety V15.1)
Description
You use the "Generate off-delay" instruction to delay the resetting of output Q by the
assigned period PT. Output Q is set if the result of logic operation (RLO) changes from "0" to
"1" (positive edge) at input IN. When the signal state at input IN changes back to "0", the
programmed period PT starts. Output Q remains set as long as period PT runs. After period
PT expires, output Q is reset. If the signal state at input IN changes to "1" before period PT
has expired, then the time is reset. The signal state at output Q remains at "1".
You can query the current time value at the output ET. The time value begins at T#0s and
ends when the value of period PT is reached. After time PT has elapsed, output ET remains
at its current value until input IN changes back to "1". If input IN changes to "1" before time
PT has expired, the output ET is reset to value T#0.
Every call of the "Generate off-delay" instruction must be assigned a data area in which the
instruction data are stored. The "Call options" dialog is automatically opened when the
instruction is in inserted in the program for this reason. There you can create a data block
(single instance) (e.g., F_IEC_Timer_DB_1) or a multi-instance (e.g.,
F_IEC_Timer_Instance_1) for the "Generate off-delay" instruction. Once it is created, you
can find the new data block in the project tree in the "STEP 7 Safety" folder under "Program
blocks > System blocks" or the multi-instance as a local tag in the "Static" section of the
block interface. For more information, refer to the
help on STEP 7
.
WARNING
When using an instruction with time processing, take the following timing imprecision
sources into account when determining your response times:
Known timing imprecision (based on standard systems) resulting from cyclic processing
Timing imprecision resulting from the update time of the time base used in the
instruction (see figure in section "Timing imprecision resulting from the update time of
the time base used in the instruction")
Tolerance of internal time monitoring in the F-CPU
For time values up to 200 ms, a maximum of 4 ms
For time values greater than or equal to 200 ms, a maximum of 2% of the (assigned)
time value
You must choose the interval between two call times of an instruction with time processing
in such a way that the required response times are achieved, taking into account the
possible timing imprecision.
(S034)
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
500 Programming and Operating Manual, 10/2018, A5E02714440-AH
The operating system resets the instances of the "Generate off-delay" instruction on a
startup of the F-system.
Note
The functionality of this instruction differs from the corresponding standard TOF instruction in
the following points:
If the instruction is called while the time is running with PT = 0 ms, the outputs Q and ET
are reset.
If the instruction is called with PT < 0 ms, the outputs Q and ET are reset.
To restart the off
-delay, another falling signal edge at input IN is required once PT is greater
than
0 again.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN
Input
BOOL
Start input
PT
Input
TIME
Duration of off delay; must be positive.
Q
Output
BOOL
Output that is reset after expiration of time PT.
ET
Output
TIME
Current time value
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1
x
o
These versions have identical functions to version V1.0.
1.2
x
o
o
1.3
x
o
o
1.4
x
x
x
o This version is no longer supported.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the F-
CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 501
Pulse diagram
The following figure shows the pulse diagram of the instruction "Generate off-delay":
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
502 Programming and Operating Manual, 10/2018, A5E02714440-AH
Timing imprecision resulting from the update time of the time base used in the instruction:
For the first call in cycle n+1, the call time of the instruction relative to the start of the F-runtime
group is earlier than that in cycle n by the amount of Δ1, e.g. because parts of the safety pro-
gram of the F-runtime group before the call time of the instruction in cycle n+1 are skipped. For
the time update, the instruction takes account of time TBase_1 instead of the time T1 that has
actually elapsed in cycle n since the call.
The instruction is called a second time in cycle n+1. This does not involve another time update
(by Δ2).
For the call in cycle n+2, the call time of the instruction relative to the start of the F-runtime
group is later than that in cycle n by the amount of Δ3, e.g. because the F-runtime group was
interrupted by a higher priority interrupt before the call time of the instruction in cycle n+2. The
instruction took into account time TBase_1 + TBase_2 instead of the time T3 that has actually
elapsed in cycle n since the call. This would also be the case if no call occurred in cycle n+1.
13.4 Timer operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 503
Example
The following example shows how the instruction works:
If the signal state of operand "TagIn_1" changes from "0" to "1", the signal state of
operand"TagOut" at output Q is set to "1".
If the signal state of operand "TagIn_1" changes back to "0", the period assigned at input PT
(200 ms) runs.
The "TagOut" operand at output Q is set back to "0" when the period expires. Operand
""F_DB_1".Tag_ET" contains the current time value.
13.5 Counter operations
SIMATIC Safety - Configuring and Programming
504 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.5
Counter operations
13.5.1
CTU: Count up (STEP 7 Safety V15.1)
Description
You can use the "Count up" instruction to increment the value at output CV. When the signal
state at the CU input changes from "0" to "1" (positive signal edge), the instruction is
executed and the current count at the CV output increases by one. The count value is
increased on each detection of a positive signal edge until it reaches the high limit of the
data type specified at the CV output. When the high limit is reached, the signal state at the
CU input no longer affects the instruction.
The counter status can be queried at output Q. The signal state at output Q is determined by
parameter PV. When the current count value is greater than or equal to the value of
parameter PV, output Q is set to signal state "1". In all other cases, the signal state at output
Q is "0".
The value at output CV is reset to zero when the signal state at input R changes to "1". As
long as signal state "1" exists at input R, the signal state at input CU has no effect on the
instruction.
Every call of the "Count up" instruction must be assigned a data area in which the instruction
data are stored. The "Call options" dialog is automatically opened when the instruction is
inserted in the program for this reason. There you can create a data block (single instance)
(e.g., F_IEC_Counter_DB_1) or a multi-instance (e.g., F_IEC_Counter_Instance_1) for the
"Count up" instruction. Once it is created, you can find the new data block in the project tree
in the "STEP 7 Safety" folder under "Program blocks > System blocks" or the multi-instance
as a local tag in the "Static" section of the block interface. For more information, refer to the
help on STEP 7
.
The operating system resets the instances of the "Count up" instruction on a startup of the
F-system.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
CU
Input
BOOL
Counter input
R Input BOOL Reset input
PV
Input
INT
Value for which output Q is set
Q Output BOOL Counter status
CV
Output
INT
Current count value
13.5 Counter operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 505
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1 x o These versions have identical functions to version V1.0.
1.2
x
o
o
1.3
x
x
x
o This version is no longer supported.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the F-
CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
Example
The following example shows how the instruction works:
When the signal state of the "CU" input changes from "0" to "1", the "Count up" instruction is
executed and the current count of the "CV" output increases by one. The count value is
increased on every additional positive signal edge until the high limit of the specified data
type (32767) is reached.
The value at the PV parameter is applied as the limit for determining the "TagOut" operands
at the Q output. Output "Q" returns the signal state "1" as long as the current count is greater
than or equal to the value of operand "PV". In all other cases, the "Q" output has the signal
state "0".
13.5 Counter operations
SIMATIC Safety - Configuring and Programming
506 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.5.2
CTD: Count down (STEP 7 Safety V15.1)
Description
You can use the "Count down" instruction to decrement the value at output CV. When the
signal state at input CD changes from "0" to "1" (positive signal edge), the instruction is
executed and the current count value at output CV is decreased by one. The count value is
decreased on each detection of a positive signal edge until it reaches the low limit of the
specified data type. When the low limit is reached, the signal state at input CD no longer
affects the instruction.
The counter status can be queried at output Q. When the current count value is less than or
equal to zero, output Q is set to signal state "1". In all other cases, the signal state at output
Q is "0".
The value at output CV is set to the value of parameter "PV" when the signal state at input
LD changes to "1". As long as signal state "1" exists at input LD, the signal state at input CD
has no effect on the instruction.
Every call of the "Count down" instruction must be assigned a data area in which the
instruction data are stored. The "Call options" dialog is automatically opened when the
instruction is inserted in the program for this reason. There you can create a data block
(single instance) (e.g., F_IEC_Counter_DB_1) or a multi-instance (e.g.,
F_IEC_Counter_Instance_1) for the "Count down" instruction. Once it is created, you can find
the new data block in the project tree in the "STEP 7 Safety" folder under "Program blocks >
System blocks" or the multi-instance as a local tag in the "Static" section of the block
interface. For more information, refer to the
help on STEP 7
.
The operating system resets the instances of the "Count down" instruction on a startup of the
F-system.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
CD
Input
BOOL
Counter input
LD Input BOOL Load input
PV
Input
INT
Value at the output CV when LD = 1 is set
Q
Output
BOOL
Counter status
CV
Output
INT
Current count value
13.5 Counter operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 507
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1 x o These versions have identical functions to version V1.0.
1.2
x
o
o
1.3
x
x
x
o This version is no longer supported.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the
F-CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
Example
The following example shows how the instruction works:
When the signal state of the "CD" input changes from "0" to "1", the "Count down" instruction
is executed and the current count at "CV" output decreases by one. The count value is
decreased on each additional positive signal edge until the low limit of the specified data
type (-32768) is reached.
Output "Q" returns the signal state "1" as long as the current count is less than or equal to
zero. In all other cases, output "Q" has signal state "0".
13.5 Counter operations
SIMATIC Safety - Configuring and Programming
508 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.5.3
CTUD: Count up and down (STEP 7 Safety V15.1)
Description
You can use the "Count up and down" instruction to increment and decrement the count
value at output CV. If the signal state at the CU input changes from "0" to "1" (positive signal
edge), the current count at the CV output increases by one. If the signal state at input CD
changes from "0" to "1" (positive signal edge), the count value at output CV is decreased by
one. If a positive signal edge is present at inputs CU and CD in one program cycle, the
current count value at output CV remains unchanged.
The count value can be increased until it reaches the high limit of the data type specified at
output CV. When the high limit is reached, the count value is no longer incremented on a
positive signal edge. When the low limit of the specified data type is reached, the count value
is no longer decreased.
When the signal state at input LD changes to "1", the count value at output CV is set to the
value of parameter PV. As long as signal state "1" exists at input LD, the signal state at
inputs CU and CD has no effect on the instruction.
The count value is set to zero, when the signal state at input R changes to "1". As long as
signal state "1" exists at input R, the signal state at inputs CU, CD, and LD has no effect on
the "Count up and down" instruction.
The status of the up counter can be queried at output QU. When the current count value is
greater than or equal to the value of parameter PV, output QU delivers signal state "1". In all
other cases, the signal state at output QU is "0".
The status of the down counter can be queried at output QD. When the current count value
is lesser than or equal to zero, output QD delivers signal state "1". In all other cases, the
signal state at output QD is "0".
Every call of the "Count up and down" instruction must be assigned a data area in which the
instruction data are stored. The "Call options" dialog is automatically opened when the
instruction is inserted in the program for this reason. There you can create a data block
(single instance) (e.g., F_IEC_Counter_DB_1) or a multi-instance (e.g.,
F_IEC_Counter_Instance_1) for the "Count up and down" instruction. Once it is created, you
can find the new data block in the project tree in the "STEP 7 Safety" folder under "Program
blocks > System blocks" or the multi-instance as a local tag in the "Static" section of the
block interface. For more information, refer to the
help on STEP 7
.
The operating system resets the instances of the "Count up and down" instruction when the
F-system is started up.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
CU
Input
BOOL
Count up input
CD Input BOOL Count down input
R
Input
BOOL
Reset input
LD Input BOOL Load input
13.5 Counter operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 509
Parameter
Declaration
Data type
Description
PV Input INT Value set at the output QU/ at which the output CV is
set at LD = 1.
QU Output BOOL Status of up counter
QD
Output
BOOL
Status of down counter
CV Output INT Current count value
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1
x
o
These versions have identical functions to version V1.0.
1.2
x
o
o
1.3
x
x
x
o This version is no longer supported.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the F-
CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
13.5 Counter operations
SIMATIC Safety - Configuring and Programming
510 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example
The following example shows how the instruction works:
When the signal state at the "CU" input or at the "CD" input changes from "0" to "1" (positive
signal edge), the "Count up and down" instruction is executed. When a positive signal edge
is present at the "CU" input, the current count of the "CV" output increases by one. When a
positive signal edge is present at the "CD" input, the current count at the "CV" output
decreases by one. The count value is increased on each positive signal edge at the CU input
until it reaches the high limit of 32767. The count value is decreased on each positive signal
edge at the CD input until it reaches the low limit of -32768.
Output "QU" returns the signal state "1" as long as the current count is greater than or equal
to the value at the "PV" input. In all other cases, output "QU" has signal state "0".
Output "QD" returns the signal state "1" as long as the current count is less than or equal to
zero. In all other cases, output "QD" has signal state "0".
13.6 Comparator operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 511
13.6
Comparator operations
13.6.1
CMP ==: Equal (STEP 7 Safety V15.1)
Description
You can use the "Equal" instruction to determine if the first comparison value (IN1 or
<Operand1>) is equal to the second comparison value (IN2 or <Operand2>).
If the condition of the comparison is satisfied, the instruction returns result of logic operation
(RLO) "1". If the condition of the comparison is not satisfied, the instruction returns RLO "0".
For LAD:
The RLO of the instruction is linked to the RLO of the entire current path as follows:
By AND, when the comparison instruction is connected in series.
By OR, when the comparison instruction is connected in parallel.
Enter the first comparison value (<Operand1>) in the operand placeholder above the
instruction. Enter the second comparison value (<Operand2>) in the operand placeholder
below the instruction.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
FBD: IN1
LAD: <Operand1>
Input INT, DINT, TIME,
WORD, (S7-
300/400) DWORD
First value to compare
FBD: IN2
LAD: <Operand2>
Input INT, DINT, TIME,
WORD, (S7-
300/400) DWORD
Second value to compare
You can select the data type of the instruction in the "<???>" drop-down list in the instruction
box.
13.6 Comparator operations
SIMATIC Safety - Configuring and Programming
512 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example
The following example shows how the instruction works:
Output "TagOut" is set when the following conditions are fulfilled:
"Tag_In1" has signal state "1".
The condition of the comparison instruction is fulfilled ("Tag_Value1" = "Tag_Value2").
13.6.2
CMP <>: Not equal (STEP 7 Safety V15.1)
Description
You can use the "Not equal" instruction to determine if the first comparison value (IN1 or
<Operand1>) is not equal to the second comparison value (IN2 or <Operand2>).
If the condition of the comparison is satisfied, the instruction returns result of logic operation
(RLO) "1". If the condition of the comparison is not satisfied, the instruction returns RLO "0".
For LAD:
The RLO of the instruction is linked to the RLO of the entire current path as follows:
By AND, when the comparison instruction is connected in series.
By OR, when the comparison instruction is connected in parallel.
Enter the first comparison value (<Operand1>) in the operand placeholder above the
instruction. Enter the second comparison value (<Operand2>) in the operand placeholder
below the instruction.
13.6 Comparator operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 513
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
FBD: IN1
LAD: <Operand1>
Input INT, DINT, TIME,
WORD, (S7-
300/400) DWORD
First value to compare
FBD: IN2
LAD: <Operand2>
Input INT, DINT, TIME,
WORD, (S7-
300/400) DWORD
Second value to compare
You can select the data type of the instruction in the "<???>" drop-down list in the instruction
box.
Example
The following example shows how the instruction works:
Output "TagOut" is set when the following conditions are fulfilled:
"Tag_In1" has signal state "1".
The condition of the comparison instruction is fulfilled ("Tag_Value1" <> "Tag_Value2").
13.6 Comparator operations
SIMATIC Safety - Configuring and Programming
514 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.6.3
CMP >=: Greater or equal (STEP 7 Safety V15.1)
Description
You can use the "Greater or equal" instruction to determine if the first comparison value
(IN1 or <Operand1>) is greater than or equal to the second comparison value (IN2 or
<Operand2>). Both comparison values must be of the same data type.
If the condition of the comparison is satisfied, the instruction returns result of logic operation
(RLO) "1". If the condition of the comparison is not satisfied, the instruction returns RLO "0".
For LAD:
The RLO of the instruction is linked to the RLO of the entire current path as follows:
By AND, when the comparison instruction is connected in series.
By OR, when the comparison instruction is connected in parallel.
Enter the first comparison value (<Operand1>) in the operand placeholder above the
instruction. Enter the second comparison value (<Operand2>) in the operand placeholder
below the instruction.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
FBD: IN1
LAD: <Operand1>
Input INT, DINT, TIME First value to compare
FBD: IN2
LAD: <Operand2>
Input INT, DINT, TIME Second value to compare
You can select the data type of the instruction in the "<???>" drop-down list in the instruction
box.
13.6 Comparator operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 515
Example
The following example shows how the instruction works:
Output "TagOut" is set when the following conditions are fulfilled:
"Tag_In1" has signal state "1".
The condition of the comparison instruction is fulfilled ("Tag_Value1" >= "Tag_Value2").
13.6.4
CMP <=: Less or equal (STEP 7 Safety V15.1)
Description
You can use the "Less or equal" instruction to determine if the first comparison value (IN1 or
<Operand1>) is less than or equal to the second comparison value (IN2 or <Operand2>).
Both comparison values must be of the same data type.
If the condition of the comparison is satisfied, the instruction returns result of logic operation
(RLO) "1". If the condition of the comparison is not satisfied, the instruction returns RLO "0".
For LAD:
The RLO of the instruction is linked to the RLO of the entire current path as follows:
By AND, when the comparison instruction is connected in series.
By OR, when the comparison instruction is connected in parallel.
Enter the first comparison value (<Operand1>) in the operand placeholder above the
instruction. Enter the second comparison value (<Operand2>) in the operand placeholder
below the instruction.
13.6 Comparator operations
SIMATIC Safety - Configuring and Programming
516 Programming and Operating Manual, 10/2018, A5E02714440-AH
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
FBD: IN1
LAD: <Operand1>
Input INT, DINT, TIME First value to compare
FBD: IN2
LAD: <Operand2>
Input INT, DINT, TIME Second value to compare
You can select the data type of the instruction in the "<???>" drop-down list in the instruction
box.
Example
The following example shows how the instruction works:
Output "TagOut" is set when the following conditions are fulfilled:
"Tag_In1" has signal state "1".
The condition of the comparison instruction is fulfilled ("Tag_Value1" <= "Tag_Value2").
13.6 Comparator operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 517
13.6.5
CMP >: Greater than (STEP 7 Safety V15.1)
Description
You can use the "Greater than" instruction to determine if the first comparison value
(IN1 or <Operand1>) is greater than the second comparison value (IN2 or <Operand2>).
Both comparison values must be of the same data type.
If the condition of the comparison is satisfied, the instruction returns result of logic operation
(RLO) "1". If the condition of the comparison is not satisfied, the instruction returns RLO "0".
For LAD:
The RLO of the instruction is linked to the RLO of the entire current path as follows:
By AND, when the comparison instruction is connected in series.
By OR, when the comparison instruction is connected in parallel.
Enter the first comparison value (<Operand1>) in the operand placeholder above the
instruction. Enter the second comparison value (<Operand2>) in the operand placeholder
below the instruction.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
FBD: IN1
LAD: <Operand1>
Input INT, DINT, TIME First value to compare
FBD: IN2
LAD: <Operand2>
Input INT, DINT, TIME Second value to compare
You can select the data type of the instruction in the "<???>" drop-down list in the instruction
box.
13.6 Comparator operations
SIMATIC Safety - Configuring and Programming
518 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example
The following example shows how the instruction works:
Output "TagOut" is set when the following conditions are fulfilled:
"Tag_In1" has signal state "1".
The condition of the comparison instruction is fulfilled ("Tag_Value1" > "Tag_Value2").
13.6.6
CMP <: Less than (STEP 7 Safety V15.1)
Description
You can use the "Less than" instruction to determine if the first comparison value (IN1 or
<Operand1>) is less than the second comparison value (IN2 or <Operand2>). Both
comparison values must be of the same data type.
If the condition of the comparison is satisfied, the instruction returns result of logic operation
(RLO) "1". If the condition of the comparison is not satisfied, the instruction returns RLO "0".
For LAD:
The RLO of the instruction is linked to the RLO of the entire current path as follows:
By AND, when the comparison instruction is connected in series.
By OR, when the comparison instruction is connected in parallel.
Enter the first comparison value (<Operand1>) in the operand placeholder above the
instruction. Enter the second comparison value (<Operand2>) in the operand placeholder
below the instruction.
13.6 Comparator operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 519
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
FBD: IN1
LAD: <Operand1>
Input INT, DINT, TIME First value to compare
FBD: IN2
LAD: <Operand2>
Input INT, DINT, TIME Second value to compare
You can select the data type of the instruction in the "<???>" drop-down list in the instruction
box.
Example
The following example shows how the instruction works:
Output "TagOut" is set when the following conditions are fulfilled:
"Tag_In1" has signal state "1".
The condition of the comparison instruction is fulfilled ("Tag_Value1" < "Tag_Value2").
13.7 Math functions
SIMATIC Safety - Configuring and Programming
520 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.7
Math functions
13.7.1
ADD: Add (STEP 7 Safety V15.1)
Description
You can use the "Add" instruction to add the value at input IN1 and the value at input IN2
and query the sum at the OUT output (OUT = IN1 + IN2).
Enable input "EN" or (S7-300, S7-400) of the "ENO" enable output cannot be connected.
The instruction is therefore always executed regardless of the signal state at enable input
"EN".
Note
When the result of the instruction is located outside the permitted range for this data type,
the F
-CPU may switch to STOP. The cause of the diagnostics event is entered in the
diagnostics buffer of the F
-CPU.
You must th
erefore ensure that the permitted range for the data type is observed when
creating the program!
(S7
-1200, S7-1500) You can avoid a STOP of the F-CPU by connecting the ENO enable
output, thereby programming overflow detection.
Note the following:
If the result of the instruction is located outside the permitted range for this data type, the
enable output ENO returns the signal state "0".
The result of the instruction reacts like the analogous instruction in a standard block.
The execution time of the instruction is extended (see also Excel file for response time
calculation (http://support.automation.siemens.com/WW/view/en/49368678/133100)).
Work memory requirement of safety program is increased.
(S7
-300, S7-400) You can avoid a STOP of the F-CPU by inserting a "Get status bit OV"
instruction in the next network, thereby programming overflow detection.
Note the following:
The result of the instruction reacts like the analogous instruction in a standard block.
The network with the "Get status bit OV" instruction must not contain any jump labels.
The execution time of the instruction is extended (see also Excel file for response time
calculation (http://support.automation.siemens.com/WW/view/en/49368678/133100)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Work memory requirement of safety program is increased.
13.7 Math functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 521
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
ENO Output BOOL (S7-1200, S7-1500)
Enable output
IN1 Input INT, DINT First addend
IN2
Input
INT, DINT
Second addend
OUT Output INT, DINT Total
You select the data type of the instruction in the "<???>" drop-down list in the instruction
box.
Example for S7-300/400 F-CPUs
The following example shows how the instruction works:
The "Add" instruction is always executed regardless of the signal state at enable input EN.
13.7 Math functions
SIMATIC Safety - Configuring and Programming
522 Programming and Operating Manual, 10/2018, A5E02714440-AH
The value of the "Tag_Value1" operand is added to value of the "Tag_Value2" operand. The
result of the addition is stored in the ""F_DB_1".Tag_Result" operand.
If needed, you can also store the signal status of the ENO enable output in an (F-)DB, and
centrally evaluate whether overflows have occurred for all or one group of instructions with
overflow detection.
When an overflow occurs during execution of the "Add" instruction, the status bit OV is set to
"1". In network 2, following the query of the status bit OV, the "Set output" (S) instruction is
executed and the "TagOut" operand is set.
Example for S7-1200/1500 F-CPUs
The following example shows how the instruction works:
The "Add" instruction is always executed regardless of the signal state at enable input EN.
The value of the "#Tag_Value1" operand is added to value of the "#Tag_Value2" operand.
The result of the addition is stored in the ""F_DB_1".Tag_Result" operand.
When no overflow occurs during execution of the "Add" instruction, the ENO enable output
has the signal state "1" and the "#TagOut" operand is set.
If needed, you can also store the signal status of the ENO enable output in an (F-)DB, and
centrally evaluate whether overflows have occurred for all or one group of instructions with
overflow detection.
See also
---| |--- OV: Get status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-400) (Page 585)
---| / |--- OV: Get negated status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-400)
(Page 586)
13.7 Math functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 523
13.7.2
SUB: Subtract (STEP 7 Safety V15.1)
Description
You can use the "Subtract" instruction to subtract the value at input IN2 from the value at
input IN1 and query the difference at the OUT output (OUT = IN1 IN2).
Enable input "EN" or (S7-300, S7-400) of the "ENO" enable output cannot be connected.
The instruction is therefore always executed regardless of the signal state at enable input
"EN".
Note
When the result of the instruction is located outside the permitted range for this data type,
the F
-CPU may switch to STOP. The cause of the diagnostics event is entered in the
diagnostics buffer of the F
-CPU.
You must therefore ensure tha
t the permitted range for the data type is observed when
creating the program!
(S7
-1200, S7-1500) You can avoid a STOP of the F-CPU by connecting the ENO enable
output, thereby programming overflow detection.
Note the following:
If the result of the instruction is located outside the permitted range for this data type, the
enable output ENO returns the signal state "0".
The result of the instruction reacts like the analogous instruction in a standard block.
The execution time of the instruction is extended (see also Excel file for response time
calculation (http://support.automation.siemens.com/WW/view/en/49368678/133100)).
Work memory requirement of safety program is increased.
(S7
-300, S7-400) You can avoid a STOP of the F-CPU by inserting a "Get status bit OV"
instruction in the next network, thereby programming overflow detection.
Note the following:
The result of the instruction reacts like the analogous instruction in a standard block.
The network with the "Get status bit OV" instruction must not contain any jump labels.
The execution time of the instruction is extended (see also Excel file for response time
calculation (http://support.automation.siemens.com/WW/view/en/49368678/133100)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Work memory requirement of safety program is increased.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
ENO Output BOOL (S7-1200, S7-1500)
Enable output
IN1
Input
INT, DINT
Minuend
13.7 Math functions
SIMATIC Safety - Configuring and Programming
524 Programming and Operating Manual, 10/2018, A5E02714440-AH
Parameter
Declaration
Data type
Description
IN2
Input
INT, DINT
Subtrahend
OUT Output INT, DINT Difference
You select the data type of the instruction in the "<???>" drop-down list in the instruction
box.
Example for S7-300/400 F-CPUs
The following example shows how the instruction works:
The "Subtract" instruction is always executed regardless of the signal state at enable input
EN.
The value of the "Tag_Value2" operand is subtracted from the value of the "Tag_Value1"
operand. The result of the addition is stored in the ""F_DB_1".Tag_Result" operand.
When an overflow occurs during execution of the "Subtract" instruction, the status bit OV is
set to "1". In network 2, following the query of the status bit OV, the "Set output" (S)
instruction is executed and the "TagOut" operand is set.
13.7 Math functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 525
Example for S7-1200/1500 F-CPUs
The following example shows how the instruction works:
The "Subtract" instruction is always executed regardless of the signal state at enable input
EN.
The value of the "#Tag_Value2" operand is subtracted from the value of the "#Tag_Value1"
operand. The result of the addition is stored in the ""F_DB_1".Tag_Result" operand.
When no overflow occurs during execution of the "Subtract" instruction, the ENO enable
output has the signal state "1" and the "#TagOut" operand is set.
See also
---| |--- OV: Get status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-400) (Page 585)
---| / |--- OV: Get negated status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-400)
(Page 586)
13.7 Math functions
SIMATIC Safety - Configuring and Programming
526 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.7.3
MUL: Multiply (STEP 7 Safety V15.1)
Description
You can use the "Multiply" instruction to multiply the value at input IN1 by the value at input
IN2 and query the product at output OUT (OUT = IN1 × IN2).
Enable input "EN" or (S7-300, S7-400) of the "ENO" enable output cannot be connected.
The instruction is therefore always executed regardless of the signal state at enable input
"EN".
Note
When the result of the instruction is located outside the permitted range for this data type,
the F
-CPU may switch to STOP. The cause of the diagnostics event is entered in the
diagnostics buffer of the F
-CPU.
You must therefore ensure that the permitted range for the data type is observed when
creating the program!
(S7
-1200, S7-1500) You can avoid a STOP of the F-CPU by connecting the ENO enable
output, thereby programming overflow detection.
Note the following:
If the result of the instruction is located outside the permitted range for this data type, the
enable output ENO returns the signal state "0".
The result of the instruction reacts like the analogous instruction in a standard block.
The execution time of the instruction is extended (see also Excel file for response time
calculation (http://support.automation.siemens.com/WW/view/en/49368678/133100)).
Work memory requirement of safety program is increased.
(S7
-300, S7-400) You can avoid a STOP of the F-CPU by inserting a "Get status bit OV"
instruction in the next network, thereby programming ov
erflow detection.
Note the following:
The result of the instruction reacts like the analogous instruction in a standard block.
The network with the "Get status bit OV" instruction must not contain any jump labels.
The execution time of the instruction is extended (see also Excel file for response time
calculation (http://support.automation.siemens.com/WW/view/en/49368678/133100)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Work memory requirement of safety program is increased.
13.7 Math functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 527
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
ENO Output BOOL (S7-1200, S7-1500)
Enable output
IN1 Input INT, DINT Multiplier
IN2
Input
INT, DINT
Multiplicand
OUT Output INT, DINT Product
You select the data type of the instruction in the "<???>" drop-down list in the instruction
box.
Example for S7-300/400 F-CPUs
The following example shows how the instruction works:
The "Multiply" instruction is always executed regardless of the signal state at enable input
EN.
13.7 Math functions
SIMATIC Safety - Configuring and Programming
528 Programming and Operating Manual, 10/2018, A5E02714440-AH
The value of the "Tag_Value1" operand is multiplied by the value of the "Tag_Value2"
operand. The result of the multiplication is stored in the ""F_DB_1".Tag_Result" operand.
When an overflow occurs during execution of the "Multiply" instruction, the status bit OV is
set to "1". In network 2, following the query of the status bit OV, the "Set output" (S)
instruction is executed and the "TagOut" operand is set.
Example for S7-1200/1500 F-CPUs
The following example shows how the instruction works:
The "Multiply" instruction is always executed regardless of the signal state at enable input
EN.
The value of the "#Tag_Value1" operand is multiplied by the value of the "#Tag_Value2"
operand. The result of the multiplication is stored in the ""F_DB_1".Tag_Result" operand.
When no overflow occurs during execution of the "Multiply" instruction, the ENO enable
output has the signal state "1" and the "#TagOut" operand is set.
See also
---| |--- OV: Get status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-400) (Page 585)
---| / |--- OV: Get negated status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-400)
(Page 586)
13.7 Math functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 529
13.7.4
DIV: Divide (STEP 7 Safety V15.1)
Description
You can use the "Divide" instruction to divide the value at input IN1 by the value at input IN2
and query the quotient at the OUT output (OUT = IN1 / IN2).
Enable input "EN" or (S7-300, S7-400) of the "ENO" enable output cannot be connected.
The instruction is therefore always executed regardless of the signal state at enable input
"EN".
Note
When the result
of the instruction is located outside the permitted range for this data type,
the F
-CPU may switch to STOP. The cause of the diagnostics event is entered in the
diagnostics buffer of the F
-CPU.
You must therefore ensure that the permitted range for the dat
a type is observed when
creating the program!
(S7
-1200, S7-1500) You can avoid a STOP of the F-CPU by connecting the ENO enable
output, thereby programming overflow detection.
Note the following:
If the result of the instruction is located outside the permitted range for this data type, the
enable output ENO returns the signal state "0".
The result of the instruction reacts like the analogous instruction in a standard block.
The execution time of the instruction is extended (see also Excel file for response time
calculation (http://support.automation.siemens.com/WW/view/en/49368678/133100)).
Work memory requirement of safety program is increased.
(S7
-300, S7-400) You can avoid a STOP of the F-CPU by inserting a "Get status bit OV"
instruction in the next network, thereby programming overflow detection.
Note the following:
The result of the instruction reacts like the analogous instruction in a standard block.
The network with the "Get status bit OV" instruction must not contain any jump labels.
The execution time of the instruction is extended (see also Excel file for response time
calculation (http://support.automation.siemens.com/WW/view/en/49368678/133100)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Work memory requirement of safety program is increased.
13.7 Math functions
SIMATIC Safety - Configuring and Programming
530 Programming and Operating Manual, 10/2018, A5E02714440-AH
Note
S7
-300/400, S7-1200/1500 (enable output ENO connected):
If the divisor (input IN2) of a DIV instruction = 0, the quotient of the division (result of division
at output OUT) = 0. The result reacts like the corresponding instruction in a standard block.
The F
-CPU does
not
go to STOP mode.
S7
-1200/1500 (enable output ENO not connected):
If the divisor (input IN2) of a DIV instruction = 0, the F
-CPU goes to STOP. The cause of the
diagnostics event is entered in the diagnostics buffer of the F
-
CPU. We recommend that you
rule out a divisor (input IN2) = 0
when creating the program.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
ENO Output BOOL (S7-1200, S7-1500)
Enable output
IN1
Input
INT, DINT
Dividend
IN2
Input
INT, DINT
Divisor
OUT
Output
INT, DINT
Quotient
You select the data type of the instruction in the "<???>" drop-down list in the instruction
box.
13.7 Math functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 531
Example for S7-300/400 F-CPUs
The following example shows how the instruction works:
The "Divide" instruction is always execute regardless of the signal state at enable input EN.
The value of the "Tag_Value1" operand is divided by the value of the "Tag_Value2" operand.
The result of the division is stored in the ""F_DB_1".Tag_Result" operand.
When an overflow occurs during execution of the "Divide" instruction, the status bit OV is set
to "1". In network 2, following the query of the status bit OV, the "Set output" (S) instruction is
executed and the "TagOut" operand is set.
13.7 Math functions
SIMATIC Safety - Configuring and Programming
532 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example for S7-1200/1500 F-CPUs
The following example shows how the instruction works:
The "Divide" instruction is always execute regardless of the signal state at enable input EN.
The value of the "#Tag_Value1" operand is divided by the value of the "#Tag_Value2"
operand. The result of the division is stored in the ""F_DB_1".Tag_Result" operand.
When no overflow occurs during execution of the "Divide" instruction, the ENO enable output
has the signal state "1" and the "#TagOut" operand is set.
See also
---| |--- OV: Get status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-400) (Page 585)
---| / |--- OV: Get negated status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-400)
(Page 586)
13.7 Math functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 533
13.7.5
NEG: Create twos complement (STEP 7 Safety V15.1)
Description
You can use the "Create twos complement" instruction to change the sign of the value at
input IN input and query the result at output OUT. If there is a positive value at input IN, for
example, the negative equivalent of this value is sent to output OUT.
Enable input "EN" or (S7-300, S7-400) of the "ENO" enable output cannot be connected.
The instruction is therefore always executed regardless of the signal state at enable input
"EN".
Note
When the result of the instruction is located outside the permitted range for this data type,
the F
-CPU may switch to STOP. The cause of the diagnostics event is entered in the
diagnostics buffer of the F
-CPU.
You must th
erefore ensure that the permitted range for the data type is observed when
creating the program!
(S7
-1200, S7-1500) You can avoid a STOP of the F-CPU by connecting the ENO enable
output, thereby programming overflow detection.
Note the following:
If the result of the instruction is located outside the permitted range for this data type, the
enable output ENO returns the signal state "0".
The result of the instruction reacts like the analogous instruction in a standard block.
The execution time of the instruction is extended (see also Excel file for response time
calculation (http://support.automation.siemens.com/WW/view/en/49368678/133100)).
Work memory requirement of safety program is increased.
(S7
-300, S7-400) You can avoid a STOP of the F-CPU by inserting a "Get status bit OV"
instruction in the next network, thereby programming overflow detection.
Note the following:
The result of the instruction reacts like the analogous instruction in a standard block.
The network with the "Get status bit OV" instruction must not contain any jump labels.
The execution time of the instruction is extended (see also Excel file for response time
calculation (http://support.automation.siemens.com/WW/view/en/49368678/133100)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Work memory requirement of safety program is increased.
13.7 Math functions
SIMATIC Safety - Configuring and Programming
534 Programming and Operating Manual, 10/2018, A5E02714440-AH
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
ENO Output BOOL (S7-1200, S7-1500)
Enable output
IN Input INT, DINT Input value
OUT
Output
INT, DINT
Twos complement of the input value
You select the data type of the instruction in the "<???>" drop-down list in the instruction
box.
Example for S7-300/400 F-CPUs
The following example shows how the instruction works:
The "Create two's complement" instruction is always executed regardless of the signal state
at enable input EN.
The sign of the "TagIn_Value" operand is changed and the result is stored in the
""F_DB_1".TagOut_Value" operand.
13.7 Math functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 535
When an overflow occurs during execution of the "Create two's complement" instruction, the
status bit OV is set to "1". In network 2, following the query of the status bit OV, the "Set
output" (S) instruction is executed and the "TagOut" operand is set.
Example for S7-1200/1500 F-CPUs
The following example shows how the instruction works:
The "Create two's complement" instruction is always executed regardless of the signal state
at enable input EN.
The sign of the "#TagIn_Value" operand is changed and the result is stored in the
""F_DB_1".TagOut_Value" operand.
When no overflow occurs during execution of the "Create two's complement" instruction, the
ENO enable output has the signal state "1" and the "TagOut" operand is set.
See also
---| |--- OV: Get status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-400) (Page 585)
---| / |--- OV: Get negated status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-400)
(Page 586)
13.7 Math functions
SIMATIC Safety - Configuring and Programming
536 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.7.6
ABS: Form absolute value (STEP 7 Safety V15.1) (S7-1200, S7-1500)
Description
You use the "Form absolute value" instruction to calculate the absolute amount of the value
which is specified at the input "IN". The result of the instruction is output at the OUT output
and can be queried there.
Enable input "EN" or (S7-300, S7-400) of the "ENO" enable output cannot be connected.
The instruction is therefore always executed regardless of the signal state at enable input
"EN".
Note
When the result of the instruction is located outside the permi
tted range for this data type,
the F
-CPU may switch to STOP. The cause of the diagnostics event is entered in the
diagnostics buffer of the F
-CPU.
You must therefore ensure that the permitted range for the data type is observed when
creating the program!
Y
ou can avoid a STOP of the F-CPU by connecting the ENO enable output, thereby
programming overflow detection.
Note the following:
If the result of the instruction is located outside the permitted range for this data type, the
enable output ENO returns the signal state "0".
The result of the instruction reacts like the analogous instruction in a standard block.
The execution time of the instruction is extended (see also Excel file for response time
calculation (http://support.automation.siemens.com/WW/view/en/49368678/133100)).
Work memory requirement of safety program is increased.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
ENO Output BOOL (S7-1200, S7-1500)
Enable output
IN
Input
INT, DINT
Input value
OUT
Output
INT, DINT
Absolute value of the input value
You select the data type of the instruction in the "<???>" drop-down list in the instruction
box.
13.7 Math functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 537
Example
The following example shows how the instruction works:
The instruction "Form absolute value"is always executed regardless of the signal state at
enable input "EN".
The absolute amount of the value at the "TagIn_Value" operand is calculated and the result
is stored in the ""F_DB_1".TagOut_Value" operand.
When no overflow occurs during execution of the "Form absolute value" instruction, the
enable output ENO has the signal state "1" and the "#TagOut" operand is set.
13.8 Move operations
SIMATIC Safety - Configuring and Programming
538 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.8
Move operations
13.8.1
MOVE: Move value (STEP 7 Safety V15.1)
Description
You can use the "Move value" instruction to transfer the content of the operand at input IN to
the operand at output OUT1.
Only operands with identical operand width and identical data structure can be specified for
input IN and output OUT1.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
(S7-1200, S7-1500) In the basic state, the instruction box contains an output (OUT1). The
number of outputs can be expanded. The inserted outputs are numbered in ascending order
on the box. During execution, the content of the operand at the IN input is transferred to all
available outputs. The instruction box cannot be expanded if operands with F-compliant PLC
data types (UDT) are transferred.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN Input INT, DINT, WORD, (S7-300/400)
DWORD, TIME, F-compliant PLC data
type (UDT)
Source value
OUT1 Output INT, DINT, WORD, (S7-300/400)
DWORD, TIME, F-compliant PLC data
type (UDT)
Destination address
13.8 Move operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 539
Example
The following example shows how the instruction works:
The instruction is always executed regardless of the signal state at enable input "EN". The
instruction copies the content of operand "TagIn_Value" to operand
""F_DB_1".TagOut_Value".
13.8.2
RD_ARRAY_I: Read value from INT F-array (STEP 7 Safety V15.1) (S7-1500)
Description
You use the "Read value from INT F-array" instruction to read an element from the array at
the ARRAY input, which refers to the index at the INDEX input, and write its value at the
OUT output. If an error occurs while accessing the array during runtime, this is displayed at
the output ERROR.
The array must be created in an F-global DB and can contain only one dimension. The
elements of the ARRAY must be data type INT. The following applies for the array limits in
contrast:
The low limit must be 0.
The high limit can be 10000 maximum.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at the "EN" enable input).
13.8 Move operations
SIMATIC Safety - Configuring and Programming
540 Programming and Operating Manual, 10/2018, A5E02714440-AH
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
ARRAY
Input
VARIANT
Array from which is read
INDEX Input DINT Element in the array which is
read. The specification may be
a constant or a tag.
OUT
Output
INT
Value which is read and output.
ERROR Output BOOL Error information
The parameter ERROR is set if
an error occurs during the pro-
cessing of the instruction.
ARRAY parameter
In addition to the direct connection with an array within a fail-safe global DB, this input can
also be interconnected with an INOUT of data type ARRAY[*] of INT. This enables the
decoupling of data and program logic in order, for example, to create a library function
without any connection existing to a dedicated data block.
ERROR parameter
The table below shows the meaning of the value of the ERROR parameter:
Value
Description
FALSE
No error
TRUE
Value at the INDEX parameter is outside the limit value of the ARRAY.
Instruction versions
One version is available for this instruction:
Ver-
sion
S7-
300/400
S7-1200
S7-1500
Function
1.0
x
1
1 supported as of firmware version V2.0
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the F-
CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
13.8 Move operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 541
Reaction to errors
If the value at the INDEX input is outside the array limits, the output ERROR = 1 is set, and
the array value of the element with index = 0 is output at OUT output, regardless of the value
passed at the INDEX input.
Therefore, set the value of the element with index = 0 as a fail-safe substitute value.
Example
The following example shows how the instruction works:
The following table shows how the instruction works using specific operand values:
Parameter
Operand
Value
ARRAY "Global_DB".Array The "Global_DB".Array operand is an ARRAY of data type Array[0..10]
of INT
INDEX
#Tag_Index
2
OUT
#TagOut_Value
Value of the element at the location array[2]
ERROR
#TagError_Value
False
The instruction "Read value from INT F-array" is always executed regardless of the signal
state at enable input "EN".
The content of the 2nd element of the operand "Global_DB.Array" is output at the
"#TagOut_Value" output.
13.8 Move operations
SIMATIC Safety - Configuring and Programming
542 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.8.3
RD_ARRAY_DI: Read value from DINT F-array (STEP 7 Safety V15.1)
(S7-1500)
Description
You use the "Read value from DINT F-array" instruction to read an element from the array at
the ARRAY input, which refers to the index at the INDEX input, and write its value at the
OUT output. If an error occurs while accessing the array during runtime, this is displayed at
the output ERROR.
The array must be created in an F-global DB and can contain only one dimension. The
elements of the array must be of the DINT data type. The following applies for the array
limits in contrast:
The low limit must be 0.
The high limit can be 10000 maximum.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at the "EN" enable input).
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
ARRAY
Input
VARIANT
Array from which is read
INDEX Input DINT Element in the array which is
read. The specification may be
a constant or a tag.
OUT
Output
DINT
Value which is read and output.
ERROR Output BOOL Error information
The parameter ERROR is set if
an error occurs during the pro-
cessing of the instruction.
ARRAY parameter
In addition to the direct connection with an array within a fail-safe global DB, this input can
also be interconnected with an INOUT of data type ARRAY[*] of DINT. This enables the
decoupling of data and program logic in order, for example, to create a library function
without any connection existing to a dedicated data block.
ERROR parameter
The table below shows the meaning of the value of the ERROR parameter:
Value
Description
FALSE
No error
TRUE
Value at the INDEX parameter is outside the limit value of the ARRAY.
13.8 Move operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 543
Instruction versions
One version is available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0
x
1
1 supported as of firmware version V2.0
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the
F-CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
Reaction to errors
If the value at the INDEX input is outside the array limits, the output ERROR = 1 is set, and
the array value of the element with index = 0 is output at OUT output, regardless of the value
passed at the INDEX input.
Therefore, set the value of the element with index = 0 as a fail-safe substitute value.
Example
The following example shows how the instruction works:
The following table shows how the instruction works using specific operand values:
Parameter
Operand
Value
ARRAY "Global_DB".Array The operand "Global_DB".Array is an ARRAY of data type Array[0..10]
of DINT
INDEX
#Tag_Index
2
OUT
#TagOut_Value
Value of the element at the location array[2]
ERROR
#TagError_Value
False
13.8 Move operations
SIMATIC Safety - Configuring and Programming
544 Programming and Operating Manual, 10/2018, A5E02714440-AH
The instruction "Read value from DINT F-array" is always executed regardless of the signal
state at enable input "EN".
The content of the 2nd element of the operand "Global_DB.Array" is output at the
"#TagOut_Value" output.
13.8.4
WR_FDB: Write value indirectly to an F-DB (STEP 7 Safety V15.1) (S7-300,
S7-400)
Description
This instruction writes the value specified in input IN to the tag addressed by INI_ADDR and
OFFSET in an F-DB.
The address of the tags addressed using INI_ADDR and OFFSET must be within the
address range defined by addresses INI_ADDR and END_ADDR.
If the F-CPU has gone to STOP mode with diagnostics event ID 75E2, check to determine if
this condition is satisfied.
The start address of the area in an F-DB to which the value at input IN is to be written is
transferred using input INI_ADDR. The associated offset in this area is transferred using
input OFFSET.
The addresses transferred in input INI_ADDR or END_ADDR must point to a tag of the
selected data type in an F-DB. Only tags of the selected data type are permitted between the
INI_ADDR and END_ADDR addresses. The INI_ADDR address must be smaller than the
END_ADDR address.
As shown in the following example, the INI_ADDR and END_ADDR addresses must be
transferred fully-qualified as "DBx".DBWy or in the corresponding symbolic representation.
Transfers in other forms are not permitted.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN
Input
INT, DINT
Value to be written to the F-DB
INI_ADDR Input POINTER Start address of the area in an F-DB
END_ADDR
Input
POINTER
End address of the area in an F-DB
OFFSET
Input
INT
Offset
You can select the data type of the instruction in the "<???>" drop-down list in the instruction
box.
13.8 Move operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 545
Examples of parameter assignment of INI_ADDR, END_ADDR, and OFFS
Name
Data type
Initial value
Comment
Static
VAR_BOOL10
BOOL
false
VAR_BOOL11
BOOL
false
VAR_BOOL12
BOOL
false
VAR_BOOL13
BOOL
false
VAR_TIME10
TIME
T#0MS
VAR_TIME11
TIME
T#0MS
VAR INT10
INT
0
<- INI ADDR = "F-DB 1".VAR INT10 Example 1
VAR_INT11
INT
0
VAR_INT12
INT
0
VAR INT13
INT
0
<- OFFSET = 3
VAR_INT14
INT
0
VAR INT15
INT
0
<- END ADDR = "F-DB 1".VAR INT15
VAR_BOOL20
BOOL
false
VAR_BOOL21
BOOL
false
VAR_BOOL22
BOOL
false
VAR_BOOL23
BOOL
false
VAR INT20
INT
0
<- INI ADDR = "F-DB 1".VAR INT20 Example 2
VAR_INT21
INT
0
VAR_INT22
INT
0
VAR INT23
INT
0
<- END ADDR = "F-DB 1".VAR INT23
VAR INT30
INT
0
<- INI ADDR = "F-DB 1".VAR INT30 Example 3
VAR INT31
INT
0
<- OFFSET = 1
VAR_INT32
INT
0
VAR_INT33
INT
0
VAR INT34
INT
0
<- END ADDR = "F-DB".VAR INT34
VAR_TIME20
TIME
T#0MS
VAR DINT10
DINT
0
<- INI ADDR = "F-DB 1".VAR DINT10 Example 4
VAR_DINT11
DINT
0
VAR DINT12
DINT
0
<- OFFSET = 2
VAR DINT13
DINT
0
<- END ADDR = "F-DB 1".VAR DINT13
13.8 Move operations
SIMATIC Safety - Configuring and Programming
546 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example
The following example shows how the instruction works:
13.8.5
RD_FDB: Read value indirectly from an F-DB (STEP 7 Safety Advanced V15.1)
(S7-300, S7-400)
Description
This instruction reads the tag addressed via INI_ADDR and OFFSET in an F-DB and
provides it at output OUT.
The address of the tags addressed using INI_ADDR and OFFSET must be within the
address range defined by addresses INI_ADDR and END_ADDR.
If the F-CPU has gone to STOP mode with diagnostics event ID 75E2, check to determine if
this condition is satisfied.
The start address of the area in an F-DB from which the tag is to be read is transferred using
input INI_ADDR. The associated offset in this area is transferred using input OFFSET.
The addresses transferred in input INI_ADDR or END_ADDR must point to a tag of the
selected data type in an F-DB. Only tags of the selected data type are permitted between the
INI_ADDR and END_ADDR addresses. The INI_ADDR address must be smaller than the
END_ADDR address.
The INI_ADDR and END_ADDR addresses must be transferred fully-qualified as
"DBx".DBWy or in the corresponding symbolic representation. Transfers in other forms are
not permitted. Examples of parameter assignment of INI_ADDR, END_ADDR, and OFFSET
are contained in WR_FDB: Write value indirectly to an F-DB (STEP 7 Safety V15.1) (S7-300,
S7-400) (Page 544).
13.8 Move operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 547
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
INI_ADDR
Input
POINTER
Start address of the area in an F-DB
END_ADDR Input POINTER End address of the area in an F-DB
OFFSET
Input
INT
Offset
OUT Output INT, DINT Value to be read from the F-DB
You can select the data type of the instruction in the "<???>" drop-down list in the instruction
box.
Example
The following example shows how the instruction works:
13.9 Conversion operations
SIMATIC Safety - Configuring and Programming
548 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.9
Conversion operations
13.9.1
CONVERT: Convert value (STEP 7 Safety V15.1)
Description
The "Convert value" instruction reads the content of parameter IN and converts it according
to the data types selected in the instruction box. The converted value is output at the OUT
output .
Enable input "EN" cannot be connected. The instruction is therefore always executed
(regardless of the signal state at the "EN" enable input). The connection of the "ENO" enable
output is only possible and required when converting from the "DINT" to the "INT" data type.
Note
When converting from "DINT" to the "INT" data type, you need to connect the ENO enable
output and thereby programming ov
erflow detection.
Note the following:
If the value at the input is outside the INT range, ENO returns 0.
The result of the instruction reacts like the analogous instruction in a standard block.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
ENO
Output
BOOL
Enable output
IN
Input
INT, DINT
Value to be converted.
OUT
Output
INT, DINT
Result of the conversion
You can select the data types of the instruction in the "<???>" drop-down lists of the
instruction box. The supported conversions are from "INT to DINT" and "DINT to INT".
13.9 Conversion operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 549
Example
The following example shows how the "Convert value "DINT to INT"" instruction for S7-
1200/1500 F-CPUs works:
The instruction is always executed regardless of the signal state at enable input EN.
The value of the "TagIn_Value" operand is converted to an integer (16-bit) and the result is
stored in the ""F_DB_1".TagOut_Value" operand.
When no overflow occurs during execution of the "Convert value "DINT to INT"" instruction,
the ENO enable output has the signal state "1" and the "TagOut" operand is set.
You can also store the signal status of the ENO enable output in an (F-)DB, and centrally
evaluate whether overflows have occurred for all or one group of instructions with overflow
detection.
See also
s7cotia.xls (http://support.automation.siemens.com/WW/view/en/49368678/133100)
13.9 Conversion operations
SIMATIC Safety - Configuring and Programming
550 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.9.2
BO_W: Convert 16 data elements of data type BOOL to a data element of data
type WORD (STEP 7 Safety V15.1)
Description
This instruction converts the 16 values of data type BOOL at inputs IN0 to IN15 to a value of
data type WORD, which is made available at output OUT. The conversion takes place as
follows: The i-th bit of the WORD value is set to 0 (or 1), if the value at input INi = 0 (or 1).
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN0
Input
BOOL
Bit 0 of WORD value
IN1 Input BOOL Bit 1 of WORD value
...
...
IN15
Input
BOOL
Bit 15 of WORD value
OUT
Output
WORD
WORD value consisting of IN0 to IN15
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1
o
o
These versions have identical functions to version V1.0.
1.2
x
o
1.3
x
o
o
1.4
x
x
x
2.0
x
x
1
x
2
o This version is no longer supported.
1
supported for Firmware version V4.2 or higher
2 supported for Firmware version V2.0 or higher
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the F-
CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
13.9 Conversion operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 551
Example
The following example shows how the instruction works:
13.9 Conversion operations
SIMATIC Safety - Configuring and Programming
552 Programming and Operating Manual, 10/2018, A5E02714440-AH
The following table shows how the instruction works using specific operand values:
Parameter
Operand
Value
IN0
TagValue_0
FALSE
IN1 TagValue_1 FALSE
...
...
IN13
TagValue_13
FALSE
IN14
TagValue_14
TRUE
IN15
TagValue_15
TRUE
OUT
"F_DB_1".Result
W#16#C000
The values of operands "TagValue_0" to "TagValue_15" are combined into a value of the
data type WORD and assigned to operand ""F_DB_1".TagResult".
13.9.3
W_BO: Convert a data element of data type WORD to 16 data elements of data
type BOOL (STEP 7 Safety V15.1)
Description
This instruction converts the value of data type WORD at input IN to 16 values of data type
BOOL, which are provided at outputs OUT0 to OUT15. The conversion takes place as
follows: Output OUTi is set to 0 (or 1), if the i-th bit of the WORD value is 0 (or 1).
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN
Input
WORD
WORD value
OUT0
Output
BOOL
Bit 0 of WORD value
OUT1
Output
BOOL
Bit 1 of WORD value
...
...
OUT15
Output
BOOL
Bit 15 of WORD value
13.9 Conversion operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 553
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1 o o These versions have identical functions to version V1.0.
1.2
x
o
1.3
x
o
o
1.4
x
x
x
2.0
x
x
1
x
2
o This version is no longer supported.
1
supported for Firmware version V4.2 or higher
2 supported for Firmware version V2.0 or higher
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the F-
CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
Example
The following example shows how the instruction works:
13.9 Conversion operations
SIMATIC Safety - Configuring and Programming
554 Programming and Operating Manual, 10/2018, A5E02714440-AH
The following table shows how the instruction works using specific operand values:
Parameter
Operand
Value
IN
"F_DB_1".TagValue
W#16#C000
OUT0
TagOUT_0
FALSE
OUT1
TagOUT_1
FALSE
...
...
OUT13 TagOUT_13 FALSE
OUT14
TagOUT_14
TRUE
OUT15
TagOUT_15
TRUE
The value of operand ""F_DB_1".TagValue" of data type WORD is converted to the 16
values "TagOUT_0" to "TagOUT_15" of data type BOOL.
13.9 Conversion operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 555
13.9.4
SCALE: Scale values (STEP 7 Safety Advanced V15.1)
Description
This instruction scales the value at input IN in physical units between the low limit value at
input LO_LIM and the high limit value at input HI_LIM. It is assumed that the value at input IN
is between 0 and 27648. The scaling result is provided at output OUT.
The instruction uses the following equation:
OUT = [ IN × (HI_LIM LO_LIM) ] / 27648 + LO_LIM
As long as the value at input IN is greater than 27648, output OUT is linked to HI_LIM and
OUT_HI is set to 1.
As long as the value at input IN is less than 0, output OUT is linked to LO_LIM and OUT_LO
is set to 1.
For inverse scaling, you must assign LO_LIM > HI_LIM. With inverse scaling, the output
value at output OUT decreases while the input value at input IN increases.
Every call of the "Scale values" instruction must be assigned a data area in which the
instruction data are stored. In addition, when the instruction is inserted in the program, the
"Call options" dialog is automatically opened, where you can create a data block (single
instance) (e.g., SCALE_DB_1) or a multi-instance (e.g., SCALE_Instance_1) for the "Scale
values" instruction. Once it is created, you can find the new data block in the project tree in
the "STEP 7 Safety" folder under "Program blocks > System blocks" or the multi-instance as
a local tag in the "Static" section of the block interface. For more information, refer to the
help on
STEP 7
.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Parameter
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN
Input
INT
Input value to be scaled in physical units
HI_LIM Input INT High limit value of value range of OUT
LO_LIM
Input
INT
Low limit value of value range of OUT
OUT
Output
INT
Result of scaling
OUT_HI
Output
BOOL
1 = Input value > 27648: OUT = HI_LIM
OUT_LO
Output
BOOL
1 = Input value < 0: OUT = LO_LIM
13.9 Conversion operations
SIMATIC Safety - Configuring and Programming
556 Programming and Operating Manual, 10/2018, A5E02714440-AH
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1 x o These versions have identical functions to version V1.0.
1.2
x
x
x
o This version is no longer supported.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the
F-CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
Behavior in the event of overflow or underflow of analog values and fail-safe value output
Note
If inputs from the PII of an SM 336;
AI 6 x 13Bit or SM 336; F-AI 6 x 0/4 ... 20 mA HART are
used as input values, note that the F
-system detects an overflow or underflow of a channel
of this F
-SM as an F-I/O fault or channel fault. The fail-safe value 0 is provided in place of
7FFF
H (for overflow) or 8000H (for underflow) in the PII for the safety program.
If other fail
-safe values should be output in this case, you need to evaluate the QBAD signal
of the associated F
-I/O or QBAD_I_xx signal / value status of the corresponding channel.
If the value in the PII of the F
-SM is within the overrange or underrange, but is > 27648 or <
0, you can likewise branch to the outpu
t of an individual fail-safe value by evaluating outputs
OUT_HI and OUT_LO, respectively.
13.9 Conversion operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 557
Example
The following example shows how the instruction works:
When operand "TagIn_Value" = 20000, the result for ""F_DB_1".TagOut_Value" is 361.
13.10 Program control operations
SIMATIC Safety - Configuring and Programming
558 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.10
Program control operations
13.10.1
JMP: Jump if RLO = 1 (STEP 7 Safety V15.1)
Description
You can use the "Jump if RLO = 1" instruction to interrupt the linear execution of the program
and resume it in another network. The destination network must be identified by a jump label
(Page 562) (LABEL). The description of the jump label is specified in the placeholder above
the instruction.
The specified jump label must be in the same block in which the instruction is executed. The
name you specify can only occur once in the block.
If the result of logic operation (RLO) at the input of the instruction is "1" or the input is not
connected, the jump to the network identified by the jump label is executed. The jump
direction can be towards higher or lower network numbers.
If the result of logic operation (RLO) at the input of the instruction is "0", the program
continues executing in the next network.
Note
(S7
-1200, S7-1500)
If the jump destination (jump label) for an instruction "JMP" or "JMPN" is above the
associated instruction "JMP" or "JMPN" (backwards jump), you cannot insert any other
instructions for program control (JMP, JMPN, RET, jump label) between them.
Exception:
You can insert an instruction "JMP" or "JMPN" between them if you also insert
the associated jump destination in between as well as below the associated instruction
"JMP" or "JMPN" (forward jump).
Non
-compliance can lead to compilation errors or to the F-CPU going to STOP.
Note
You are not permitted to insert any SENDDP or SENDS7 instructions between an instruction
JMP or JMPN and the associated jump destination (jump label).
13.10 Program control operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 559
Example
The following example shows how the instruction works:
When operand "TagIn_1" has signal state "1", the "Jump if RLO = 1" instruction is executed.
The linear execution of the program is interrupted and continues in Network 3, which is
identified by the jump label CAS1. When input "TagIn_3" has signal state "1", output
"TagOut_3" is reset.
13.10 Program control operations
SIMATIC Safety - Configuring and Programming
560 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.10.2
JMPN: Jump if RLO = 0 (STEP 7 Safety V15.1)
Description
You can use the "Jump if RLO = 0" instruction to interrupt the linear execution of the program
and resume it in another network, when the result of logic operation at the input of the
instruction is "0". The destination network must be identified by a jump label (Page 562)
(LABEL). The description of the jump label is specified in the placeholder above the
instruction.
The specified jump label must be in the same block in which the instruction is executed. The
name you specify can only occur once in the block.
If the result of logic operation (RLO) at the input of the instruction is "0", the jump to the
network identified by the jump label is executed. The jump direction can be towards higher or
lower network numbers.
If the result of logic operation (RLO) at the input of the instruction is "1", the program
continues executing in the next network.
Note
(S7
-1200, S7-1500)
If the jump destination (jump label) for an instruction "JMP" or "JMPN" is above the
associated instruction "JMP" or "JMPN" (backwards jump), you cannot insert any other
instructions for progr
am control (JMP, JMPN, RET, jump label) between them.
Exception:
You can insert an instruction "JMP" or "JMPN" between them if you also insert
the associated jump destination in between as well as below the associated instruction
"JMP" or "JMPN" (forward
jump).
Non
-compliance can lead to compilation errors or to the F-CPU going to STOP.
Note
You are not permitted to insert any SENDDP or SENDS7 instructions between an instruction
JMP or JMPN and the associated jump destination (jump label).
13.10 Program control operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 561
Example
The following example shows how the instruction works:
When operand "TagIn_1" has signal state "0", the "Jump if RLO = 0" instruction is executed.
The linear execution of the program is interrupted and continues in Network 3, which is
identified by the jump label CAS1. When input "TagIn_3" has signal state "1", output
"TagOut_3" is reset.
13.10 Program control operations
SIMATIC Safety - Configuring and Programming
562 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.10.3
LABEL: Jump label (STEP 7 Safety V15.1)
Description
You can use a jump label to specify a destination network, in which the program execution
should resume after a jump.
The jump label and the instruction in which the jump label is specified must be located in the
same block. The name of a jump label can only be assigned once in a block.
Only one jump label can be placed in a network. To each jump label can be jumped from
several locations.
Example
The following example shows how the instruction works:
13.10 Program control operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 563
When operand "TagIn_1" has signal state "1", the "Jump if RLO = 1" instruction is executed.
The linear execution of the program is interrupted and continues in Network 3, which is
identified by the jump label CAS1. When input "TagIn_3" has signal state "1", output
"TagOut_3" is reset.
See also
JMP: Jump if RLO = 1 (STEP 7 Safety V15.1) (Page 558)
JMPN: Jump if RLO = 0 (STEP 7 Safety V15.1) (Page 560)
RET: Return (STEP 7 Safety V15.1) (Page 564)
13.10 Program control operations
SIMATIC Safety - Configuring and Programming
564 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.10.4
RET: Return (STEP 7 Safety V15.1)
Description
You can use the "Return" instruction to stop the processing of a block.
If the result of logic operation (RLO) at the input of the "Return" instruction is "1" or the box
input of the S7-1200/1500 F-CPUs is not connected in FBD, program execution is terminated
in the currently called block and continued in the calling block (for example, in the main
safety block) after the call function. If the RLO at the input of the "Return" instruction is "0",
the instruction is not executed. Program execution continues in the next network of the called
block.
Influencing the status of the call function (ENO) is irrelevant, because the enable output
"ENO" cannot be connected.
Note
(S7
-300, S7-400) You may not program a RET instruction in the main safety block.
Example
The following example shows how the instruction works:
When the "TagIn" operand delivers signal state "1", the "Return" instruction is executed.
Program execution is terminated in the called block and continues in the calling block.
See also
JMP: Jump if RLO = 1 (STEP 7 Safety V15.1) (Page 558)
JMPN: Jump if RLO = 0 (STEP 7 Safety V15.1) (Page 560)
LABEL: Jump label (STEP 7 Safety V15.1) (Page 562)
13.10 Program control operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 565
13.10.5
OPN: Open global data block (STEP 7 Safety Advanced V15.1)
(S7-300, S7-400)
Description
You can use the "Open global data block" instruction to open a data block. The number of
the data block is transferred to the DB register. Subsequent DB commands access the
relevant blocks depending on the register contents.
Note
Note when using the "Open global data block" instruction that the content
of the DB register
can be changed after calls of F
-FB/F-
FC and "fully qualified DB accesses", such that there is
no guarantee that the last data block you opened with "Open global data block" is still open.
You should therefore use the following method fo
r addressing data to avoid errors when
accessing data of the DB register:
Use symbolic addressing.
Use only fully qualified DB accesses.
If you still want to use the "Open global data block" operation, you must ensure that the DB
register is restored by re
peating the "Open global data block" instruction following calls of F-
FB/F
-FC and "fully qualified DB accesses." Otherwise, a malfunction could result.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
<Data block>
Input
BLOCK_DB
Data block that is opened
"Fully qualified DB access"
The initial access to data of a data block in an F-FB/F-FC must always be a "fully qualified
DB access," or it must be preceded by the "Open global data block" instruction. This also
applies to the initial access to data of a data block after a jump label.
An example of "fully qualified DB access" and "non-fully qualified DB access" is provided in
Restrictions in the programming languages FBD/LAD (Page 119).
Access to instance DBs
You can also access instance DBs of F-FBs with fully qualified access, e.g., for transfer of
block parameters. It is not possible to access static local data in single/multi-instances of
other F-FBs.
Note that accessing instance DBs of F-FBs that are not called in the safety program can
cause the F-CPU to go to STOP mode.
13.10 Program control operations
SIMATIC Safety - Configuring and Programming
566 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example
The following example shows how the instruction works:
The "Motor_DB" data block is called in network 1. The number of the data block is
transferred to the DB register. The "DBX0.0" operand is queried in network 2. The signal
state of the "DBX0.0" operand is assigned to the "Tag_Output" operand.
13.11 Word logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 567
13.11
Word logic operations
13.11.1
AND: AND logic operation (STEP 7 Safety V15.1)
Description
You can use the "AND logic operation" instruction to combine the value at input IN1 to the
value at input IN2 bit-by-bit by AND logic and query the result at output OUT.
When the instruction is executed, bit 0 of the value at input IN1 and bit 0 of the value at input
IN2 are ANDed. The result is stored in bit 0 of output OUT. The same logic operation is
executed for all other bits of the specified values.
The result bit has signal state "1" only when both of the bits in the logic operation also have
signal state "1". If one of the two bits of the logic operation has signal state "0", the
corresponding result bit is reset.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN1
Input
WORD
First value of logic operation
IN2 Input WORD Second value of logic operation
OUT
Output
WORD
Result of the instruction
13.11 Word logic operations
SIMATIC Safety - Configuring and Programming
568 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example
The following example shows how the instruction works:
IN1
"Tag_Value1" = 01010101 01010101
IN2
"Tag_Value2" = 00000000 00001111
OUT
"F_DB_1"."Tag_Result" = 00000000 00000101
The instruction is always executed regardless of the signal state at enable input "EN". The
value of the "Tag_Value1" operand and the value of the "Tag_Value2" operand are ANDed.
The result is mapped bit-by-bit and output in the ""F_DB_1".Tag_Result" operand.
13.11.2
OR: OR logic operation (STEP 7 Safety V15.1)
Description
You can use the "OR logic operation" instruction to connect the value at input IN1 input to
the value at input IN2 bit-by-bit by OR logic and query the result at output OR.
When the instruction is executed, bit 0 of the value at input IN1 and bit 0 of the value at input
IN2 are ORed. The result is stored in bit 0 of output OUT. The same logic operation is
executed for all bits of the specified tags.
The result bit has signal state "1" when at least one of the two bits in the logic operation has
signal state "1". If both of the bits of the logic operation have signal state "0", the
corresponding result bit is reset.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
13.11 Word logic operations
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 569
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN1
Input
WORD
First value of logic operation
IN2 Input WORD Second value of logic operation
OUT
Output
WORD
Result of the instruction
Example
The following example shows how the instruction works:
IN1
"Tag_Value1" = 01010101 01010101
IN2
"Tag_Value2" = 00000000 00001111
OUT
"F_DB_1"."Tag_Result" = 01010101 01011111
The instruction is always executed regardless of the signal state at enable input "EN". The
value of the "Tag_Value1" operand and the value of the "Tag_Value2" operand are ORed.
The result is mapped bit-by-bit and output in the ""F_DB_1".Tag_Result" operand.
13.11 Word logic operations
SIMATIC Safety - Configuring and Programming
570 Programming and Operating Manual, 10/2018, A5E02714440-AH
13.11.3
XOR: EXCLUSIVE OR logic operation (STEP 7 Safety V15.1)
Description
You can use the "EXCLUSIVE OR logic operation" instruction to combine the value at input
IN1 and the value at input IN2 bit-by-bit by EXCLUSIVE OR logic and query the result at
output OUT.
When the instruction is executed, bit 0 of the value at input IN1 input and bit 0 of the value at
input IN2 are logically combined by EXCLUSIVE OR. The result is stored in bit 0 of output
OUT. The same logic operation is executed for all other bits of the specified value.
The result bit has signal state "1" when one of the two bits in the logic operation has signal
state "1". If both of the bits of the logic operation have signal state "1" or "0", the
corresponding result bit is reset.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN1
Input
WORD
First value of logic operation
IN2 Input WORD Second value of logic operation
OUT
Output
WORD
Result of the instruction
13.12 Shift and rotate
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 571
Example
The following example shows how the instruction works:
IN1
"Tag_Value1" = 01010101 01010101
IN2
"Tag_Value2" = 00000000 00001111
OUT
"F_DB_1"."Tag_Result" = 01010101 01011010
The instruction is always executed regardless of the signal state at enable input "EN". The
value of the "Tag_Value1" operand and the value of the "Tag_Value2" operand are logically
combined by EXCLUSIVE OR. The result is mapped bit-by-bit and output in the
""F_DB_1".Tag_Result" operand.
13.12
Shift and rotate
13.12.1
SHR: Shift right (STEP 7 Safety V15.1)
Description
Use the "Shift right" instruction to shift the content of the operand at input IN bit-by-bit to the
right and query the result at output OUT. Use input N to specify the number of bit positions
by which the specified value is to be moved.
If the value at input N is "0", the value at input IN is copied to the operand at output OUT.
If the value at input N is greater than the number of available bit positions, the operand value
at input IN is shifted to the right by the available number of bit positions.
The bit locations that are freed up in the left area of the operand during the shift operation
are filled with zeros.
13.12 Shift and rotate
SIMATIC Safety - Configuring and Programming
572 Programming and Operating Manual, 10/2018, A5E02714440-AH
The following figure shows how the content of an operand of data type WORD is moved by 6
bit positions to the right:
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Note
S7
-300/400:
Only the low
-byte is evaluated from input N.
S7
-1200/1500:
If the value at input N < 0, the
output OUT is set to 0.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN
Input
WORD
Value that is shifted
N
Input
INT
Number of bit positions by which the value is shifted
OUT
Output
WORD
Result of the instruction
13.12 Shift and rotate
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 573
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1 o o These versions have identical functions to version V1.0.
1.2
x
o
1.3
x
o
o
1.4
x
x
x
2.0
x
x
1
x
2
o This version is no longer supported.
1
supported for Firmware version V4.2 or higher
2 supported for Firmware version V2.0 or higher
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the
F-CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
Example
The following example shows how the instruction works:
13.12 Shift and rotate
SIMATIC Safety - Configuring and Programming
574 Programming and Operating Manual, 10/2018, A5E02714440-AH
The following table shows how the instruction works using specific operand values:
Parameter
Operand
Value
IN
"F_DB_1".TagIn_Value
0011 1111 1010 1111
N Tag_Number 3
OUT
"F_DB_1".TagOut_Value
0000 0111 1111 0101
The instruction is always executed regardless of the signal state at enable input "EN". The
content of the operand ""F_DB_1".TagIn_Value" is moved three bit positions to the right. The
result is output at output ""F_DB_1".TagOut_Value".
13.12.2
SHL: Shift left (STEP 7 Safety V15.1)
Description
Use the "Shift left" instruction to shift the content of the operand at input IN bit-by-bit to the
left and query the result at output OUT. Use input N to specify the number of bit positions by
which the specified value is to be moved.
If the value at input N is "0", the value at input IN is copied to the operand at output OUT.
If the value at input N is greater than the number of available bit positions, the operand value
at input IN is shifted to the left by the available number of bit positions.
The bit positions that are freed up in the right area of the operand during the shift operation
are filled with zeros.
The following figure shows how the content of an operand of data type WORD is moved by 6
bit positions to the left:
13.12 Shift and rotate
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 575
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Note
S7
-300/400:
Only the low
-byte is evaluated from input N.
S7
-1200/1500:
If the value at input N < 0, the output OUT is set to 0.
Parameters
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN
Input
WORD
Value that is shifted
N
Input
INT
Number of bit positions by which the value is shifted
OUT
Output
WORD
Result of the instruction
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1
o
o
These versions have identical functions to version V1.0.
1.2
x
o
1.3
x
o
o
1.4
x
x
x
2.0
x
x
1
x
2
o This version is no longer supported.
1
supported for Firmware version V4.2 or higher
2 supported for Firmware version V2.0 or higher
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the F-
CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
13.12 Shift and rotate
SIMATIC Safety - Configuring and Programming
576 Programming and Operating Manual, 10/2018, A5E02714440-AH
Example
The following example shows how the instruction works:
The following table shows how the instruction works using specific operand values:
Parameter
Operand
Value
IN
"F_DB_1".TagIn_Value
0011 1111 1010 1111
N
Tag_Number
4
OUT
"F_DB_1".TagOut_Value
1111 1010 1111 0000
The instruction is always executed regardless of the signal state at enable input "EN". The
content of the operand ""F_DB_1".TagIn_Value" is moved four bit positions to the left. The
result is output at output ""F_DB_1".TagOut_Value".
13.13 Operating
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 577
13.13
Operating
13.13.1
ACK_OP: Fail-safe acknowledgment (STEP 7 Safety V15.1)
Description (S7-300, S7-400)
This instruction enables fail-safe acknowledgment from an HMI system. It allows, for
example, reintegration of F-I/O to be controlled from the HMI system. Acknowledgment takes
place in two steps:
Input/output parameter IN changes to a value of 6 for exactly one cycle.
Input/output parameter IN changes to a value of 9 within a minute for exactly one cycle
Once the in/out parameter IN has changed to a value of 6, the instruction evaluates whether
this parameter has changed to a value of 9 after 1 second, at the earliest, or one minute, at
the latest. Output OUT (output for acknowledgment) is then set to 1 for one cycle.
If an invalid value is input or if in/out parameter IN has not changed to the value 9 within one
minute or the change occurred before one second has elapsed, then in/out parameter IN is
reset to 0, and both steps listed above must be repeated.
During the time in which in/out parameter IN must change from 6 to the value 9, output Q is
set to 1. Otherwise, Q has a value of 0.
Every call of the "Fail-safe acknowledgment" instruction must be assigned a data area in
which the instruction data are stored. The "Call options" dialog is automatically opened when
the instruction is inserted in the program for this reason. There you can create a data block
(single instance) (e.g., ACK_OP_DB_1) or a multi-instance (e.g., ACK_OP_Instance_1) for
the "Fail-safe acknowledgment" instruction. Once it is created, you can find the new data
block in the project tree in the "STEP 7 Safety" folder under "Program blocks > System
blocks" or the multi-instance as a local tag in the "Static" section of the block interface. For
more information, refer to the help on
STEP 7
.
Note
A separate data area must be used for each call of ACK_OP. Each call can be processed
only once in an F
-runtime group cycle.
The F
-CPU can go to STOP if this is not observed. The cause of the diagnostics event is
entered in the diagnostics buffer of the F
-CPU.
13.13 Operating
SIMATIC Safety - Configuring and Programming
578 Programming and Operating Manual, 10/2018, A5E02714440-AH
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
WARNING
The two acknowledgment steps must
not
be triggered by one single operation, for example
by automatically storing them along with the time conditions in a program and using a
function key to trigger them.
Having two separate acknowledgment steps also prevents erroneous triggering of an
acknowledgment by your non-fail-safe HMI system.
(S013)
WARNING
If you have HMI systems and F-CPUs that are interconnected and use the ACK_OP
instruction for fail-safe acknowledgment, you need to ensure that the intended F-CPU will
be addressed
before
you perform the two acknowledgment steps.
To do this, store a network-wide* unique name for the F-CPU in a DB of your standard
user program in each F-CPU.
In your HMI system, set up a field from which you can read out the F-CPU name from
the DB online before executing the two acknowledgment steps.
Optional:
in your HMI system, set up a field to permanently store the F-CPU name. Then, you can
determine whether the intended F-CPU is being addressed by simply comparing the F-
CPU name read out online with the permanently stored name.
(S014)
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet.
Note
You can read out output Q by means of operator control and monitoring systems or, if
applicable, evaluate it in your standard user program.
You can provide the in/out parameter IN with
a separate memory word or DBW of a DB of
the standard user program supply for each instance of the ACK_OP instruction.
Note
The configuration of your operator control and monitoring system does not have any effect
on the collective F
-signature.
13.13 Operating
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 579
WARNING
When using an instruction with time processing, take the following timing imprecision
sources into account when determining your response times:
Known timing imprecision (based on standard systems) resulting from cyclic processing
Timing imprecision resulting from the update time of the time base used in the
instruction (see figure in section "Timing imprecision resulting from the update time of
the time base used in the instruction")
Tolerance of internal time monitoring in the F-CPU
For time values up to 200 ms, a maximum of 4 ms
For time values greater than or equal to 200 ms, a maximum of 2% of the (assigned)
time value
You must choose the interval between two call times of an instruction with time processing
in such a way that the required response times are achieved, taking into account the
possible timing imprecision.
(S034)
Description (S7-1200, S7-1500)
This instruction enables fail-safe acknowledgment from an HMI system. It allows, for
example, reintegration of F-I/O to be controlled from the HMI system. Acknowledgment takes
place in two steps:
Input/output parameter IN changes to a value of 6 for exactly one cycle.
Input/output parameter IN changes to the value at the ACK_ID input within a minute for
exactly one cycle
Once the in/out parameter IN has changed to a value of 6, the instruction evaluates whether
this parameter has changed to a value at the ACK_ID input after 1 second, at the earliest, or
one minute, at the latest. Output OUT (output for acknowledgment) is then set to 1 for one
cycle.
If an invalid value is input or if in/out parameter IN has not changed to the value at the
ACK_ID input within one minute or the change occurred before one second has elapsed,
then in/out parameter IN is reset to 0, and both steps listed above must be repeated.
During the time in which in/out parameter IN must change from 6 to the value at the ACK_ID
input, output Q is set to 1. Otherwise, Q has a value of 0.
13.13 Operating
SIMATIC Safety - Configuring and Programming
580 Programming and Operating Manual, 10/2018, A5E02714440-AH
Every call of the "Fail-safe acknowledgment" instruction must be assigned a data area in
which the instruction data are stored. The "Call options" dialog is automatically opened when
the instruction is inserted in the program for this reason. There you can create a data block
(single instance) (e.g., ACK_OP_DB_1) or a multi-instance (e.g., ACK_OP_Instance_1) for
the "Fail-safe acknowledgment" instruction. Once it is created, you can find the new data
block in the project tree in the "STEP 7 Safety" folder under "Program blocks > System
blocks" or the multi-instance as a local tag in the "Static" section of the block interface. For
more information, refer to the help on
STEP 7
.
Note
A separate data area must be used for each call of ACK_OP. Each call can be processed
only
once in an F-runtime group cycle.
The F
-CPU can go to STOP if this is not observed. The cause of the diagnostics event is
entered in the diagnostics buffer of the F
-CPU.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
WARNING
The two acknowledgment steps must
not
be triggered by one single operation, for example
by automatically storing them along with the time conditions in a program and using a
function key to trigger them.
Having two separate acknowledgment steps also prevents erroneous triggering of an
acknowledgment by your non-fail-safe HMI system.
(S013)
13.13 Operating
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 581
WARNING
If you have HMI systems and F-CPUs that are interconnected and use the ACK_OP
instruction for fail-safe acknowledgment, you need to ensure that the intended F-CPU will
be addressed
before
you perform the two acknowledgment steps.
Alternative 1:
The value for each identifier of the acknowledgment (ACK_ID input; data type: INT) can
be freely selected in the range from 9 to 30000, but must be unique network-wide* for all
instances of the ACK_OP instruction.
You must supply the ACK_ID input with constant values when calling the instruction.
Direct read or write access in the associated instance DB is not permitted in the safety
program!
Alternative 2:
To do this, store a network-wide* unique name for the F-CPU in a DB of your standard
user program in each F-CPU.
In your HMI system, set up a field from which you can read out the F-CPU name from
the DB online before executing the two acknowledgment steps.
Optional:
in your HMI system, set up a field to permanently store the F-CPU name. Then, you can
determine whether the intended F-CPU is being addressed by simply comparing the
F-CPU name read out online with the permanently stored designation.
(S047)
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet.
Note
You can read out output Q by means of operator control and monitoring systems or, if
applicable, evaluate it in your standard user program.
You need to provide the in/out p
arameter IN with a separate memory word or DBW of a DB
of the standard user program for each instance of the ACK_OP instruction.
Note
The supply of the IN input/output of the ACK_OP instruction as well as the configuration of
your operator control and
monitoring system do not have any effect on the F-collective
signature, the F
-SW collective signature or the signature of the block that calls the ACK_OP
instruction.
Changes to the supply of the IN input/output or to the configuration of your operator con
trol
and monitoring system therefore do not result in a changed F
-collective signature/F-SW
collective signature/signature of the calling block.
13.13 Operating
SIMATIC Safety - Configuring and Programming
582 Programming and Operating Manual, 10/2018, A5E02714440-AH
WARNING
When using an instruction with time processing, take the following timing imprecision
sources into account when determining your response times:
Known timing imprecision (based on standard systems) resulting from cyclic processing
Timing imprecision resulting from the update time of the time base used in the
instruction (see figure in section "Timing imprecision resulting from the update time of
the time base used in the instruction")
Tolerance of internal time monitoring in the F-CPU
For time values up to 200 ms, a maximum of 4 ms
For time values greater than or equal to 200 ms, a maximum of 2% of the (assigned)
time value
You must choose the interval between two call times of an instruction with time processing
in such a way that the required response times are achieved, taking into account the
possible timing imprecision.
(S034)
Parameters (S7-300, S7-400)
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
IN
InOut
INT
Input variable from HMI system
OUT
Output
BOOL
Output for acknowledgment
Q
Output
BOOL
Time status
Parameters (S7-1200, S7-1500)
The following table shows the parameters of the instruction:
Parameter
Declaration
Data type
Description
ACK_ID
Input
INT
Identifier of the acknowledgment (9 to 30000)
IN
InOut
INT
Input variable from HMI system
OUT
Output
BOOL
Output for acknowledgment
Q
Output
BOOL
Time status
13.13 Operating
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 583
Instruction versions
A number of versions are available for this instruction:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1 x o These versions are identical in function to version V1.0 for S7-300/400
F-CPUs.
The input ACK_ID must also be taken into consideration for
S7-1200/1500 F-CPUs.
1.2
x
o
o
1.3 x x x
o This version is no longer supported.
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the
F-CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
13.13 Operating
SIMATIC Safety - Configuring and Programming
584 Programming and Operating Manual, 10/2018, A5E02714440-AH
Timing imprecision resulting from the update time of the time base used in the instruction:
For the first call in cycle n+1, the call time of the instruction relative to the start of the F-runtime
group is earlier than that in cycle n by the amount of Δ1, e.g. because parts of the safety pro-
gram of the F-runtime group before the call time of the instruction in cycle n+1 are skipped. For
the time update, the instruction takes account of time TBase_1 instead of the time T1 that has
actually elapsed in cycle n since the call.
The instruction is called a second time in cycle n+1. This does not involve another time update
(by Δ2).
For the call in cycle n+2, the call time of the instruction relative to the start of the F-runtime
group is later than that in cycle n by the amount of Δ3, e.g. because the F-runtime group was
interrupted by a higher priority interrupt before the call time of the instruction in cycle n+2. The
instruction took into account time TBase_1 + TBase_2 instead of the time T3 that has actually
elapsed in cycle n since the call. This would also be the case if no call occurred in cycle n+1.
Example
An example how the instruction is used is available under Implementing User
Acknowledgment in the Safety Program of the F-CPU of a DP Master or IO controller
(Page 187).
See also
Implementing user acknowledgment in the safety program of the F-CPU of a I-slave or
I-device (Page 192)
13.14 Additional instructions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 585
13.14
Additional instructions
13.14.1
LAD
13.14.1.1
---| |--- OV: Get status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-400)
Description
You can use the "Get status bit OV" instruction to detect whether a number range overflow
occurred in the last arithmetic instruction processed.
The "Get status bit OV" instruction functions like a normally open contact. If the query is
fulfilled, the instruction has signal state "1". If the query is not fulfilled, the instruction has
signal state "0".
The "Get status bit OV" evaluation must be inserted in the network that follows the
instruction that influences the OV. This network must not contain any jump labels.
Note
The execution time of the OV
-affecting instruction is extended when the "Get status bit OV "
instruction is used (see also Excel file for response time calculation
(
http://support.automation.siemens.com/WW/view/en/49368678/133100)).
Example
The following example shows how the instruction works:
The "Add" instruction is always executed (regardless of the signal state at enable input EN).
13.14 Additional instructions
SIMATIC Safety - Configuring and Programming
586 Programming and Operating Manual, 10/2018, A5E02714440-AH
The value of the "Tag_Value1" operand is added to value of the Tag_Value2 operand. The
result of the addition is stored in the ""F_DB_1".Tag_Result" operand.
If an overflow occurs during execution of the "Add" instruction, the status bit OV is set to "1".
In network 2, following the query of the status bit OV, the "Set output" (S) instruction is
executed and the "TagOut" operand is set.
13.14.1.2
---| / |--- OV: Get negated status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-
400)
Description
You can use the "Get negated status bit OV" instruction to detect whether a number range
overflow occurred in the last arithmetic instruction processed. This instruction is only
available in LAD.
The "Get negated status bit OV" instruction functions like a normally closed contact. If the
query is satisfied, the instruction has signal state "0". If the query is not satisfied, the
instruction has signal state "1".
The "Get negated status bit OV" evaluation must be inserted in the network following the
instruction that influences the OV. This network must not contain any jump labels.
Note
The execution time of the OV
-affecting instruction is extended when the "Get negated status
bit OV " instruction is used (see also Excel file for response time calc
ulation
(
http://support.automation.siemens.com/WW/view/en/49368678/133100)).
Example
The following example shows how the instruction works:
The "Add" instruction is always executed (regardless of the signal state at enable input EN).
13.14 Additional instructions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 587
The value of the "Tag_Value1" operand is added to value of the Tag_Value2 operand. The
result of the addition is stored in the ""F_DB_1".Tag_Result" operand.
If an overflow does
not
occur during execution of the "Add" instruction, the status bit OV is
reset to "0". In network 2, following the query of the status bit OV, the "Set output" (S)
instruction is executed and the "TagOut" operand is set.
13.14.2
FBD
13.14.2.1
OV: Get status bit OV (STEP 7 Safety Advanced V15.1) (S7-300, S7-400)
Description
You can use the "Get status bit OV" instruction to detect whether a number range overflow
occurred in the last arithmetic instruction processed.
The "Get status bit OV" evaluation must be inserted in the network that follows the
instruction that influences the OV. This network must not contain any jump labels.
If the query is fulfilled, the instruction has signal state "1". If the query is not fulfilled, the
instruction has signal state "0".
You can program a query of status bit OV for "0" with the "Invert RLO" instruction.
Note
The execution time of the O
V-affecting instruction is extended when the "Get status bit OV "
instruction is used (see also Excel file for response time calculation
(
http://support.automation.siemens.com/WW/view/en/49368678/133100)).
Example
The following example shows how the instruction works:
The value of the "Tag_Value1" operand is added to value of the Tag_Value2 operand. The
result of the addition is stored in the ""F_DB_1".Tag_Result" operand.
13.15 Communication
SIMATIC Safety - Configuring and Programming
588 Programming and Operating Manual, 10/2018, A5E02714440-AH
If an overflow occurs during execution of the "Add" instruction, the status bit OV is set to "1".
In network 2, following the query of the status bit OV, the "Set output" (S) instruction is
executed and the "TagOut" operand is set.
13.15
Communication
13.15.1
PROFIBUS/PROFINET
13.15.1.1
SENDDP and RCVDP: Send and receive data via PROFIBUS DP/PROFINET IO
(STEP 7 Safety V15.1)
Introduction
You use the SENDDP and RCVDP instructions for fail-safe sending and receiving of data
using:
Safety-related master-master communication
Safety-related master-master communication for S7 Distributed Safety
Safety-related master-I-slave communication
Safety-related I-slave-I-slave communication
Safety-related IO controller-IO controller communication
Safety-related IO controller-IO controller communication for S7 Distributed Safety
Safety-related IO controller-I-device communication
Safety-related IO controller-I-slave communication
13.15 Communication
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 589
Description
The SENDDP instruction sends 16 data elements of data type BOOL and 2 data elements of
data type INT or one data element of the data type DINT (S7-1200, S7-1500) in a fail-safe
manner to another F-CPU via PROFIBUS DP/PROFINET IO. The data can be received
there by the related RCVDP instruction.
Every call of this instruction must be assigned a data area in which the instruction data are
stored. The "Call options" dialog is automatically opened when the instruction is inserted in
the program for this reason. There you can create a data block (single instance) (e.g.
RCVDP_DB_1) for these instructions. Once it is created, the new data block can be found in
the "STEP 7 Safety" folder in the project tree under "Program blocks > System blocks". For
more information, refer to the help on
STEP 7
.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
With the SENDDP instruction, the data to be sent (for example, outputs of other F-
blocks/instructions) are available at input SD_BO_xx or SD_I_xx or SD_DI_00 as alternative.
With the RCVDP instruction, the data received are available at outputs RD_BO_xx and
RD_I_xx or RD_DI_00 as alternative for additional processing by other F-blocks/instructions.
(S7-1200, S7-1500) At the DINTMODE input of the SENDDP instruction you specify if the
data at the inputs SD_I_00 and SD_I_01 or the data at the input SD_DI_00 is sent.
The operating mode of the F-CPU with the SENDDP instruction is provided at output
SENDMODE. If the F-CPU with the SENDDP instruction is in disabled safety mode, output
SENDMODE = 1.
Communication between F-CPUs takes place in the background by means of a special
safety protocol. You must define the communication relationship between a SENDDP
instruction in one F-CPU and a RCVDP instruction in the other F-CPU by specifying an F-
communication ID at the DP_DP_ID inputs of the SENDDP and RCVDP instructions.
Associated SENDDP and RCVDP instructions are assigned the same value for DP_DP_ID.
WARNING
The value for the respective F-communication ID (input DP_DP_ID; data type: INT) can be
freely selected**; however, it must be unique for all safety-related communication
connections network-wide* and CPU-wide at all times. The uniqueness must be checked in
the safety summary during acceptance of the safety program. You can find additional
information in Correctness and completeness of the communication configuration
(Page 374).
You must supply constant values*** to the inputs DP_DP_ID and LADDR when calling the
instruction. Direct write accesses in the associated instance DB to DP_DP_ID and LADDR
are not permitted in the safety program!
(S016)
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet. In PROFIBUS, a network includes all nodes accessible via PROFIBUS DP. In
PROFINET IO, a network includes all nodes accessible via RT_Class_1/2/3
(Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP (IP, Layer 3).
** S7-1200/1500: As of version V3.0 of the SENDDP and RCVDP instructions, no connection
is established at the DP_DP_ID input for a F-communication ID "0".
13.15 Communication
SIMATIC Safety - Configuring and Programming
590 Programming and Operating Manual, 10/2018, A5E02714440-AH
*** S7-1200/1500: As of version V3.0 of the SENDDP and RCVDP instructions, the
DP_DP_ID input can also be supplied with variable values from a global F-DB. In this case
as well you have to check during the acceptance of the safety program that the uniqueness
is ensured
at every moment
, by checking the algorithm for the creation of the variable value
accordingly. If you cannot ensure a unique F-communication ID during startup of the safety
program, because it is only specified after startup of the safety program, you must make sure
that the value at the DP_DP_ID input is "0" during this phase.
Note
Within a safety program, you must assign a different start address (S7
-300/400) or HW
identifier (S7
-1200/1500) for every call of the SENDDP and RCVDP instructions at input
LADDR.
A separate instance DB must be used for each call of the SENDDP and RCVDP instructions.
You must not declare and call these instructions as multi
-instances.
(S7
-300/400) The inputs of the RCVDP and RCVS7 instructions may not have preceding
logic operations (for example "AND logic operation").
The inputs of the RCVDP instruction cannot be initialized using fully qualified DB accesses
with outputs of a RCVDP or RCVS7 instruction called in an upstre
am network.
(S7
-1200/1500) The RD_D_00 output must not be evaluated for DINTMODE = 0; the
RD_I_xx outputs of the RCVDP instruction must not be evaluated for DINTMODE = 1.
(S7
-1200/1500) The outputs of the SENDDP and RCVDP instructions must not be supplied
with tags from the standard user program. Exception: RET_DPRD, RET_DPWR and DIAG
outputs.
Fully qualified access to DP_DP_ID and LADDR is not possible in the safety program.
You cannot use an actual parameter for an output of an RCVDP instruction, if it i
s already
being used for an input of the same or another RCVDP or RCVS7 instruction.
The F
-CPU can go to STOP if this is not observed. The cause of the diagnostics event is
entered in the diagnostics buffer of the F
-CPU.
Note
You are not permitted to
insert any SENDDP/RCVDP instructions between a JMP or JMPN
instruction and the associated jump destination (jump label).
You cannot insert a RET instruction prior to a SENDDP instruction.
13.15 Communication
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 591
SENDDP parameter
The following table shows the parameters of the SENDDP instruction:
Parameter
Declaration
Data type
Description
SD_BO_00
Input
BOOL
Send data BOOL 00
... ...
SD_BO_15
Input
BOOL
Send data BOOL 15
SD_I_00
Input
INT
Send data INT 00
SD_I_01
Input
INT
Send data INT 01
SD_DI_00 Input DINT (S7-1200, S7-1500)
(hidden)
Send data DINT 00
DINTMODE Input DINT (S7-1200, S7-1500)
(hidden)
0=SD_I_00 u. SD_I_01 are sent
1=SD_DI_00 is sent
DP_DP_ID
Input
INT
F-communication ID between SENDDP and RCVDP
TIMEOUT Input TIME Monitoring time in ms for safety-related communication (see also
Monitoring and response times (Page 607))
LADDR Input INT (S7-300,
S7-400)
HW_SUBMOD
ULE (S7-
1200,
S7-1500)
The start address (S7-300, S7-400) or HW identifier (S7-1200,
S7-1500) of the address area/transfer area:
Of DP/DP coupler for safety-related master-master communi-
cation
For safety-related master-I-slave communication
For safety-related I-slave-I-slave communication
Of PN/PN coupler for safety-related IO controller-IO controller
communication
For safety-related IO controller-I-device communication
For safety-related IO controller-I-slave communication
ERROR
Output
BOOL
1=Communication error
SUBS_ON
Output
BOOL
1=RCVDP outputs fail-safe values
RET_DPRD Output WORD Non-fail-safe error code RET_VAL of the DPRD_DAT instruction
(for a description of error codes, refer to the help for the
DPRD_DAT instruction ("Extended instructions > Distributed I/O
> Other")).
RET_DPWR Output WORD Non-fail-safe error code RET_VAL of the DPWR_DAT instruction
(for a description of error codes, refer to the help for the
DPWR_DAT instruction ("Extended instructions > Distributed I/O
> Other")).
DIAG
Output
BYTE
Non-fail safe service information
13.15 Communication
SIMATIC Safety - Configuring and Programming
592 Programming and Operating Manual, 10/2018, A5E02714440-AH
RCVDP parameter:
The following table shows the parameters of the RCVDP instruction:
Parameter
Declaration
Data type
Description
ACK_REI Input BOOL 1=Acknowledgment for reintegration of send data following com-
munication error
SUBBO_00
Input
BOOL
Fail-safe value for receive data BOOL 00
...
...
SUBBO_15 Input BOOL Fail-safe value for receive data BOOL 15
SUBI_00
Input
INT
Fail-safe value for receive data INT 00
SUBI_01
Input
INT
Fail-safe value for receive data INT 01
SUBDI_00 Input DINT (S7-1200, S7-1500)
(hidden)
Fail-safe value for receive data DINT 00
DP_DP_ID
Input
INT
F-communication ID between SENDDP and RCVDP
TIMEOUT Input TIME Monitoring time in ms for safety-related communication (see also
Monitoring and response times (Page 607))
LADDR Input INT (S7-300,
S7-400)
HW_SUBMOD
ULE (S7-1200,
S7-1500)
The start address (S7-300, S7-400) or HW identifier (S7-1200,
S7-1500) of the address area/transfer area:
Of DP/DP coupler for safety-related master-master communi-
cation
For safety-related master-I-slave communication
For safety-related I-slave-I-slave communication
Of PN/PN coupler for safety-related IO controller-IO controller
communication
For safety-related IO controller-I-device communication
For safety-related IO controller-I-slave communication
ERROR
Output
BOOL
1=Communication error
SUBS_ON
Output
BOOL
1=Fail-safe values are output
ACK_REQ
Output
BOOL
1=Acknowledgment for reintegration of send data required
SENDMODE
Output
BOOL
1=F-CPU with SENDDP instruction in disabled safety mode
RD_BO_00
Output
BOOL
Receive data BOOL 00
...
...
RD_BO_15 Output BOOL Receive data BOOL 15
RD_I_00
Output
INT
Receive data INT 00
RD_I_01
Output
INT
Receive data INT 01
RD_DI_00 Output DINT (S7-1200, S7-1500)
(hidden)
Receive data DINT 00
RET_DPRD Output WORD Non-fail-safe error code RET_VAL of the DPRD_DAT instruction
(for a description of error codes, refer to the help for the
DPRD_DAT instruction ("Extended instructions > Distributed I/O
> Other")).
13.15 Communication
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 593
Parameter
Declaration
Data type
Description
RET_DPWR Output WORD Non-fail-safe error code RET_VAL of the DPWR_DAT instruction
(for a description of error codes, refer to the help for the
DPWR_DAT instruction ("Extended instructions > Distributed I/O
> Other")).
DIAG
Output
BYTE
Non-fail safe service information
Instruction versions
A number of versions are available for these instructions:
Ver-
sion
S7-300/400
S7-1200
S7-1500
Function
1.0 x When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated, version 1.0 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety
Advanced
for the first time, we recommend that you first update to the
latest available version of the instruction.
1.1
o
o
These versions have identical functions to version V1.0.
1.2
x
o
1.4
x
x
1.3
x
o
S7-300/400: These versions have identical functions to version V1.0.
S7-1200/1500: Instead of 2 data of data type INT, one data of data type
DINT can be sent/received as alternative. Otherwise identical function
as version V1.0.
1.5
x
x
x
2.0 x x1 x2
3.0 x x1 x2 S7-300/400: This version has identical functions to version V2.0.
S7-1200/1500:
The DP_DP_ID input can also be supplied with tags of a global F-
DB. In case of DP_DP_ID = 0 no connection is established.
Supports the data status byte of the PN/PN coupler as of V4.0
Supports the simulation of the communication in S7-PLCISM opera-
tion
Otherwise functionally identical to version V2.0
o This version is no longer supported.
1
supported for Firmware version V4.2 or higher
2 supported for Firmware version V2.0 or higher
When a new F-CPU is created with
STEP 7 Safety
, the latest available version for the F-
CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
13.15 Communication
SIMATIC Safety - Configuring and Programming
594 Programming and Operating Manual, 10/2018, A5E02714440-AH
Placement
You need to insert the RCVDP instruction
either
at the start of the main safety block
or
(with
S7-1200/1500 F-CPUs) in an F-FB/F-FC called directly at the start of the main safety block.
No other instructions can be located before in the main safety block and no other instructions
can be located before or afterwards in the F-FB/F-FC.
You need to insert the SENDDP instruction
either
at the end of the main safety block
or
(with
S7-1200/1500 F-CPUs) in an F-FB/F-FC called directly at the end of the main safety block.
No other instructions can be located afterwards in the main safety block and no other
instructions can be located before or afterwards in the F-FB/F-FC.
Startup characteristics
After the sending and receiving F-systems are started up, communication must be
established between the connection partners for the fist time (SENDDP and RCVDP
instructions). During this time, the receiver (RCVDP instruction) outputs the fail-safe values
present at its inputs SUBBO_xx and SUBI_xx or alternatively SUBDI_00.
The SENDDP and RCVDP instructions signal this with 1 at output SUBS_ON. The
SENDMODE output has default setting "0" and is not updated as long as output SUBS_ON =
1.
As of version V3.0 of the SENDDP and RCVDP instructions, communication is only
established when DP_DP_ID <> 0.
Behavior in the event of communication errors
If a communication error occurs, for example, due to a signature error (CRC) or when
monitoring time TIMEOUT expires or for F-CPUs S7-1200/1500 as of V3.0 due to a change
of the DP_DP_ID to 0 after establishment of communication, the outputs ERROR and
SUBS_ON = 1 are set. The receiver (RCVDP instruction) then outputs the fail-safe values
assigned at its inputs SUBBO_xx and SUBI_xx or alternatively SUBDI_00 inputs. Output
SENDMODE is not updated while output SUBS_ON = 1.
The send data of the SENDDP instruction present at inputs SD_BO_xx and SD_I_xx,
SD_DI_00 as alternative, are only output again when communication errors are no longer
detected (ACK_REQ = 1) and you acknowledge (Page 187) the RCVDP instruction with a
positive edge at input ACK_REI.
Communication errors also occur if the values of the DP_DP_IDs between associated
SENDDP and RCVDP are temporarily different on a change of the values of variable
DP_DP_IDs after communication establishment.
WARNING
For the user acknowledgment, you must interconnect input ACK_REI with a signal
generated by the operator input.
An interconnection with an automatically generated signal is not permitted.*
(S040)
13.15 Communication
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 595
* If variable F-communication IDs are used, the communication partner of the SENDDP or
RCVDP instructions can be changed during running operation. The resultant communication
errors may only be acknowledged with an automatically generated signal at the ACK_REI
input under the following conditions:
The F-program reliably forms a signal "Communication partner change is in progress"
with the RCVDP instruction on the basis of the process state.
The signal "Communication partner change is in progress" is only formed if there is no
communication error.
While the signal "Communication partner change is in progress" is active, no evaluation
of the received process values is carried out at the RCVDP instruction.
The automatic acknowledgement is only carried out if the "Communication partner
change is in progress" signal is available.
From a safety standpoint automatic reintegration is permitted for the relevant process.
Note that output ERROR (1=communication error) for a communication error will not be set
unless communication between the connection partners (SENDDP and RCVDP instructions)
has been previously established. If communication cannot be established after startup of the
sending and receiving F-Systems, check the configuration of the safety-related CPU-CPU
communication, the parameter assignment of the SENDDP and the RCVDP instructions, and
the bus connection. You also obtain information on possible error causes by evaluating
outputs DIAG, RET_DPRD and RETDP_WR.
In general, always evaluate RET_DPRD and RETDP_WR, since it is possible that only one
of the two outputs will contain error information.
13.15 Communication
SIMATIC Safety - Configuring and Programming
596 Programming and Operating Manual, 10/2018, A5E02714440-AH
Timing diagrams SENDDP/RCVDP
Output DIAG
In addition, non-fail-safe information about the type of communication errors that occurred is
provided at output DIAG of the SENDDP and RCVDP instructions for service purposes.
You can read out this information by means of operator control and monitoring systems or, if
applicable, you can evaluate it in your standard user program. DIAG bits are saved until you
acknowledge the errors at input ACK_REI of the RCVDP instruction.
13.15 Communication
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 597
Structure of DIAG of the SENDDP/RCVDP instruction
Bit no.
Assignment
Possible error causes
Remedies
Bit 0
Reserved
Bit 1 Reserved
Bit 2
Reserved
Bit 3 Invalid DP_DP_ID The DP_DP_ID is 0. Check the DP_DP_ID of SENDDP or
RCVDP.
Bit 4 Timeout of
SENDDP/RCVDP detect-
ed
The standard program overwrites
transfer areas of SENDDP and
RCVDP.
Check the standard program for writing ac-
cesses into the transfer areas of SENDDP
and RCVDP. Please also take indirect ac-
cesses into account.
DP_DP_ID of SENDDP and RCVDP
different.
Check the DP_DP_ID of SENDDP and
RCVDP.
For variable F-communication IDs
the values are changed at the
DP_DP_ID input.
When the DP_DP_ID of SENDDP and RCVD
is consistent again, perform an acknowledg-
ment at the ACK_REI input.
Interference in bus connection to
partner F-CPU.
Check the bus connection and ensure that
there are no external sources of interference.
Monitoring time setting for F-CPU
and partner F-CPU is too low.
Check the parameterized monitoring time
TIMEOUT at SENDDP and RCVDP of both
CPUs. Set a higher value if necessary.
Recompile the safety program.
Configuration of the DP/DP coupler
or PN/PN coupler is invalid.
Check the configuration of the DP/DP coupler
or of the PN/PN coupler.
Data validity indicator "DIA" of the
DP/DP coupler is "ON".
Set the data validity indicator "DIA" at the DIL
switch of the DP/DP coupler to "OFF".
Parameter "Data validity indicator
DIA" of the PN/PN coupler is acti-
vated.
Deactivate the "Data validity display DIA"
parameter in the properties for the PN/PN
coupler.
Parameter "Activate data status" of
the PN/PN coupler (as of V4.0) is
activated.
Deactivate the "Activate data status" parame-
ter in the properties for the PN/PN coupler (as
of V4.0)
or
S7-1200/1500: Use Version V3.0 of the
SENDDP and RCVDP instructions.
Internal fault of DP/DP coupler or
PN/PN coupler
Replace the DP/DP coupler or PN/PN coupler
CP in STOP mode, or internal fault
in CP
Switch the CP to RUN. Check the diagnostics
buffer of the CP.
If necessary, replace the CP.
F-CPU/partner F-CPU in STOP
mode, or internal fault in F-
CPU/partner F-CPU
Switch the F-CPUs to RUN. Check the diag-
nostics buffer of the F-CPUs.
If necessary, replace the F-CPUs.
Bit 5 Sequence number error of
SENDDP/RCVDP detect-
ed
See description for bit 4 See description for bit 4
13.15 Communication
SIMATIC Safety - Configuring and Programming
598 Programming and Operating Manual, 10/2018, A5E02714440-AH
Bit no.
Assignment
Possible error causes
Remedies
Bit 6 CRC-error of
SENDDP/RCVDP detect-
ed
See description for bit 4
See description for bit 4
DP_DP_ID of SENDDP and RCVDP
different
Check DP_DP_ID of SENDDP and RCVDP
Bit 7
Reserved
See also
Communication with S7 Distributed Safety via PN/PN coupler (IO controller-IO controller
communication) (Page 256)
Communication with S7 Distributed Safety via DP/DP coupler (master-master
communication) (Page 257)
Configuring and programming communication (S7-300, S7-400) (Page 201)
Safety-related IO controller-IO controller communication (Page 204)
Safety-related master-master communication (Page 213)
Safety-related IO controller-I-device communication (Page 223)
Safety-related master-I-slave communication (Page 229)
Safety-related IO controller-I-slave communication (Page 247)
13.15 Communication
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 599
13.15.2
S7 communication
13.15.2.1
SENDS7 and RCVS7: Communication via S7 connections (STEP 7 Safety Advanced
V15.1) (S7-300, S7-400)
Introduction
You use the SENDS7 and RCVS7 instructions for fail-safe sending and receiving of data
using S7 connections.
Note
In
STEP 7 Safety Advanced
, S7 connections are generally permitted over Industrial Ethernet
only.
Safety
-related communication via S7 connections is possible from and to F-CPUs with
PROFINET interface or S7
-400 F-CPUs with PROFINET-capable CPs. See also Safety-
related communication via S7 connections
(Page 248).
Description
The SENDS7 instruction sends the send data contained in an F-communication DB to the
F-communication DB of the associated RCVS7 instruction of another F-CPU in a fail-safe
manner using an S7 connection.
Every call of this instruction must be assigned a data area in which the instruction data are
stored. The "Call options" dialog is automatically opened when the instruction is inserted in
the program for this reason. There you can create a data block (single instance) (e.g.,
SENDS7_DB_1) or a multi-instance (e.g., SENDS7_Instance_1) for this instruction. Once it is
created, you can find the new data block in the project tree in the "STEP 7 Safety" folder
under "Program blocks > System blocks" or the multi-instance as a local tag in the "Static"
section of the block interface. For more information, refer to the help on
STEP 7
.
Enable input "EN" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Information on the F-communication DB is contained in "Programming safety-related
communication via S7 connections (Page 251)".
An F-communication DB is an F-DB for safety-related CPU-CPU communication with special
properties. You must specify the numbers of the F-communication DBs at inputs SEND_DB
and RCV_DB of instructions SENDS7 and RCVS7.
The operating mode of the F-CPU with the SENDS7 instruction is provided at output
SENDMODE of the RCVS7 instruction. If the F-CPU with the SENDS7 instruction is in
disabled safety mode, then output SENDMODE = 1.
13.15 Communication
SIMATIC Safety - Configuring and Programming
600 Programming and Operating Manual, 10/2018, A5E02714440-AH
To reduce the bus load, you can temporarily shut down communication between the F-CPUs
at input EN_SEND of the SENDS7 instruction. To do so, supply input EN_SEND with "0"
(default = "1"). In this case, send data are no longer sent to the F-communication DB of the
associated RCVS7 instruction, and the receiver provides fail-safe values for this period of
time (initial values in its F-communication DB). If communication was already established
between the partners, a communication error is detected.
You must specify the local ID - from the perspective of the F-CPU - of the S7 connection
(from the connection table in the network view) at input ID of the SENDS7 instruction (see
also Configuring (Page 43)).
Communication between F-CPUs takes place in the background by means of a special
safety protocol. You must define a communication relationship between an SENDS7
instruction in one F-CPU and a communication relationship between an RCVS7 instruction
and the other F-CPU by assigning an odd number at input R_ID (of the SENDS7 and RCVS7
instructions). Associated SENDS7 and RCVS7 instructions receive the same value for R_ID.
WARNING
The value for the respective F-communication ID (input R_ID; data type: DWORD) can be
freely selected; however, it must be odd for all safety-related communication connections
network-wide* and CPU-wide. The value R_ID + 1 is internally assigned and must not be
used.
You must supply inputs ID and R_ID with constant values when calling the instruction.
Direct read or write access to the associated instance DB is not permitted in the safety
program.
(S020)
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet. In PROFIBUS, a network includes all nodes accessible via PROFIBUS DP. In
PROFINET IO, a network includes all nodes accessible via RT_Class_1/2/3
(Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP (IP, Layer 3).
Note
A separate instance DB must be used for each call of the SENDS7 and RCVS7 instructions
within a safety program. You must not declare and call these instructions as multi
-instances.
The inputs of the RCVS7 instruction ca
nnot be initialized with outputs (using fully qualified
DB accesses) of a RCVS7 or RCVDP instruction called in an upstream network.
You cannot use an actual parameter for an output of an RCVS7 instruction, if it is already
being used for an input of the sa
me or another RCVS7 or RCVDP instruction.
The F
-CPU can go to STOP if this is not observed. A diagnostics event is entered in the
diagnostics buffer of the F
-CPU.
Note
You must not program any SENDS7/RCVS7 instruction between a JMP or JMPN instruction
and the associated destination network of the JMP or JMPN instruction.
You cannot program a RET instruction prior to a SENDS7 instruction.
13.15 Communication
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 601
SENDS7 parameter
The following table shows the parameters of the SENDS7 instruction:
Parameter
Declaration
Data type
Description
SEND_DB
Input
BLOCK_DB
Number of F-communication DB
TIMEOUT Input TIME Monitoring time in ms for safety-related communication (see
also Monitoring and response times (Page 607))
EN_SEND
Input
BOOL
1= Send enable
ID Input WORD Local ID of the S7 connection
R_ID Input DWORD Network-wide unique value for a F-communication ID between
a SENDS7 instruction and a RCVS7 instruction
ERROR
Output
BOOL
1=Communication error
SUBS_ON
Output
BOOL
1=Receiving block outputs fail-safe values
STAT_RCV Output WORD Non-fail-safe status parameter STATUS of the URCV instruction
(You can find a description of error codes in the help for the
URCV instruction ("Communication > S7 Communication"))
STAT_SND Output WORD Non-fail-safe status parameter STATUS of the USEND instruc-
tion (You can find a description of error codes in the help for the
USEND instruction ("Communication > S7 Communication"))
DIAG
Output
BYTE
Non-fail safe service information
13.15 Communication
SIMATIC Safety - Configuring and Programming
602 Programming and Operating Manual, 10/2018, A5E02714440-AH
RCVS7 parameter
The following table shows the parameters of the RCVS7 instruction.
Parameter
Declaration
Data type
Description
ACK_REI Input BOOL Acknowledgment for reintegration of send data after commu-
nication error
RCV_DB
Input
BLOCK_DB
Number of F-communication DB
TIMEOUT Input TIME Monitoring time in ms for safety-related communication (see
also Monitoring and response times (Page 607))
ID
Input
WORD
Local ID of the S7 connection
R_ID Input DWORD Network-wide unique value for a F-communication ID between
a SENDS7 instruction and a RCVS7 instruction
ERROR
Output
BOOL
1=Communication error
SUBS_ON
Output
BOOL
1=Fail-safe values are output
ACK_REQ
Output
BOOL
1=Acknowledgment for reintegration of send data required
SENDMODE Output BOOL 1=F-CPU with the SENDS7 instruction in disabled safety
mode
STAT_RCV Output WORD Non-fail-safe status parameter STATUS of the URCV instruc-
tion (You can find a description of error codes in the help for
the URCV instruction ("Communication > S7 Communica-
tion"))
STAT_SND Output WORD Non-fail-safe status parameter STATUS of the USEND in-
struction (You can find a description of error codes in the help
for the USEND instruction ("Communication > S7 Communi-
cation"))
DIAG
Output
BYTE
Non-fail safe service information
Instruction versions
A number of versions are available for these instructions:
Version
S7-300/400
S7-1500
Function
1.0 x
1.1 x This version has identical functions to version V1.0.
It also supports later versions of internally called instructions.
When projects that were created with
S7 Distributed Safety V5.4 SP5
are migrated,
version 1.1 of the instruction is used automatically.
If you want to compile a migrated safety program with
STEP 7 Safety Advanced
for the
first time, we recommend that you first update to the latest available version of the
instruction.
1.2 x This version has identical functions to version V1.0/1.1.
It also supports later versions of internally called instructions.
When a new F-CPU is created with
STEP 7 Safety Advanced
, the latest available version for
the F-CPU created is automatically preset.
For more information on the use of instruction versions, refer to the help on
STEP 7
under
"Using instruction versions".
13.15 Communication
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 603
Placement
You must insert the RCVS7 instruction at the start of the main safety block. No other
instructions may be located before it in the main safety block.
You must insert the the SENDS7 instruction at the end of the main safety block. No other
instructions may be located after it in the main safety block.
Startup characteristics
After the sending and receiving F-systems are started up, communication must be
established between the connection partners for the fist time (SENDS7 and RCVS7
instructions). The receiver (RCVS7 instruction) provides fail-safe values for this time period
(initial values in its F-communication DB).
The SENDS7 and RCVS7 instructions signal this with 1 at output SUBS_ON. The
SENDMODE output (RCVS7 instruction) has default setting "0" and is not updated as long
as output SUBS_ON = 1.
Behavior in the event of communication errors
If a communication error occurs, for example, due to a signature error (CRC) or when
monitoring time TIMEOUT expires, outputs ERROR and SUBS_ON = 1 are set. The receiver
(RCVS7 instruction) then provides fail-safe values (initial values in its F-communication DB).
Output SENDMODE is not updated while output SUBS_ON = 1.
The send data present in the F-communication DB (SENDS7 instruction) are not output
before the communication error is no longer detected (ACK_REQ = 1) and you acknowledge
(Page 187) with a positive edge at input ACK_REI of the RCVS7 instruction.
WARNING
For the user acknowledgment, you must interconnect input ACK_REI with a signal
generated by the operator input.
An interconnection with an automatically generated signal is not permitted.
(S040)
Note that output ERROR (1=communication error) will be set for the first time on a
communication error if communication has already been established between the connection
partners (SENDS7 and RCVS7 instructions). If communication cannot be established after
startup of the sending and receiving F-Systems, check the configuration of the safety-related
CPU-CPU communication, the parameter assignment of the SENDS7 and the RCVS7
instructions, and the bus connection. You can also receive information on possible error
causes by evaluating the STAT_RCV and STAT_SND outputs.
In general, always evaluate STAT_RCV and STAT_SND, since it is possible that only one of
the two outputs will contain error information.
If one of the DIAG bits is set at output DIAG, also check whether the length and structure of
the associated F-communication DB on both the sending and receiving ends match.
13.15 Communication
SIMATIC Safety - Configuring and Programming
604 Programming and Operating Manual, 10/2018, A5E02714440-AH
Timing diagrams SENDS7 and RCVS7
Output DIAG
Non-fail-safe information on the type of communication errors that have occurred is made
available at output DIAG for service purposes. You can read out this information by means of
operator control and monitoring systems or, if applicable, you can evaluate it in your
standard user program. DIAG bits are saved until you acknowledge them at input ACK_REI
of the associated RCVS7 instruction.
13.15 Communication
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 605
Structure of DIAG
Bit no.
Assignment of SENDS7 and
RCVS7
Possible error causes
Remedies
Bit 0
Reserved
Bit 1 Reserved
Bit 2
Reserved
Bit 3 Reserved
Bit 4 Timeout detected by SENDS7
and RCVS7
Fault in bus connection to partner
F-CPU
Check bus connection and ensure that
no external fault sources are present.
Monitoring time setting for F-CPU
and partner F-CPU is too low
Check assigned monitoring time
TIMEOUT for SENDS7 and RCVS7 of
both F-CPUs. If possible, set a higher
value. Recompile safety program
CPs in STOP mode, or internal fault
in CPs
Switch CPs to RUN mode
Check diagnostic buffer of CPs
Replace CPs, if necessary
F-CPU/partner F-CPU in STOP
mode, or internal fault in F-
CPU/partner F-CPU
Switch F-CPUs to RUN mode
Check diagnostic buffer of F-CPUs
Replace F-CPUs, if necessary
Communication was shut down with
EN_SEND = 0.
Enable communication again at the
associated SENDS7 with EN_SEND =
1
S7 connection has changed, the IP
address of the CP has changed, for
example
Recompile the safety programs and
download them to the F-CPUs
Bit 5 Sequence number error detected
by SENDS7 and RCVS7
See description for bit 4 See description for bit 4
Bit 6 CRC-error detected by SENDS7
and RCVS7
See description for bit 4 See description for bit 4
Bit 7 RCVS7:
Communication cannot be estab-
lished
Configuration of the safety-related
CPU-CPU communication is incor-
rect, parameter assignment of the
SENDS7 and RCVS7 instructions is
incorrect
See also description for Bit 4
Check configuration of the safety-
related CPU-CPU communication, the
parameter assignment of the SENDS7
and the RCVS7 instructions is incor-
rect
See also description for Bit 4
SENDS7:
Reserved
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 607
Monitoring and response times
A
Introduction
In the following, you will learn:
Which F-specific monitoring times you must configure
Which rules must be followed when specifying monitoring times
Where you enter the F-specific monitoring times
Which rules must be followed with regard to the maximum response time of a safety
function
Support for calculations
An Excel file is available on the Internet
(http://support.automation.siemens.com/WW/view/en/49368678/133100) to assist you in
calculating approximately the runtimes of the F-runtime groups, the minimum F-specific
monitoring times, and the maximum response times of your F-System.
Additional information
The monitoring and response times for the standard part are calculated in SIMATIC Safety in
exactly the same way as for standard S7-300, S7-400, S7-1200 and S7-1500 automation
systems and are not addressed here. For a description of this calculation, refer to the
hardware manuals for the CPUs
.
Monitoring and response times
A.1 Configuring monitoring times
SIMATIC Safety - Configuring and Programming
608 Programming and Operating Manual, 10/2018, A5E02714440-AH
A.1
Configuring monitoring times
Monitoring times to be configured
You must configure the following monitoring times:
Monitoring...
Setting...
Parameters
See
F-
cycle time or cycle time warning
limit of the F-runtime groups that
contain the safety program
in
Safety Administration
Editor
:
Dialog for definition of
an F-runtime group
Maximum cycle time
of the F-runtime
group
Procedure for defining an
F-runtime group (S7-300, S7-400)
(Page 134)
Procedure for defining an
F-runtime group (S7-1200, S7-
1500) (Page 137)
of the safety-related communica-
tion between F-CPU and F-
I/O via
PROFIsafe (PROFIsafe monitor-
ing time)
In the
hardware and
network editor
:
Centrally when con-
figuring the F-CPU;
properties of the F-
CPU; or
when configuring the
F-I/O; properties of
the F-I/O
F-monitoring time
F_WD_TIME
Configuring an F-CPU (Page 48)
Configuring F-I/O (Page 53)
Peculiarities when configuring fail-
safe GSD based DP slaves and
fail-safe GSD based I/O devices
(Page 77)
of the safety-related CPU-CPU
communication
At the TIMEOUT input of
the instructions:
SENDDP; RCVDP;
SENDS7; RCVS7
TIMEOUT Communication (Page 588)
(S7-1200, S7-1500) Communica-
tion with Flexible F-Link
in Safety Administration
Editor:
"Flexible F-Link" area
F-monitoring time of
F-communication
"Flexible F-Link" area (S7-1200,
S7-1500) (Page 96)
F-runtime group communication
(S7-1200, S7-1500) (Page 145)
Configuring and programming
communication with Flexible F-
Link (S7-1200, S7-1500)
(Page 262)
(S7-300, S7-400) You do not have to configure the monitoring time for safety-related
communication between F-runtime groups.
Monitoring and response times
A.1 Configuring monitoring times
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 609
Rules for configuring monitoring times
When configuring monitoring times, you must take into account the availability as well as the
safety of the F-system as follows:
Availability: To ensure that the time monitoring is not triggered when there is no error, the
monitoring times selected must be sufficiently long.
Safety: To ensure that the process safety time is not exceeded for the process, the
monitoring times selected must be sufficiently short.
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal state to be transferred will
be acquired at the sender end and transferred to the receiver if the signal level is pending
for at least as long as the assigned F-monitoring time.
(S018)
General procedure for configuring monitoring times
Use the following procedure for configuring monitoring times:
1. Configure the standard system.
Refer to the applicable
hardware manuals
and
Help on STEP 7
for the necessary
information.
2. Configure the specific monitoring times of the F-System with respect to availability. You
use the Excel file for response time calculation
(http://support.automation.siemens.com/WW/view/en/49368678/133100) to calculate the
approximate minimum monitoring time.
3. Use the Excel file for response time calculation to calculate the maximum response time
and then verify that the process safety time of the process is not exceeded. If necessary,
you must reduce the specific monitoring times of the F-System.
Monitoring and response times
A.1 Configuring monitoring times
SIMATIC Safety - Configuring and Programming
610 Programming and Operating Manual, 10/2018, A5E02714440-AH
A.1.1
Minimum monitoring time for the F-runtime group cycle time
Parameter "Maximum cycle time of the F-runtime group"
You configure the monitoring time for the F-runtime group cycle time in the
Safety
Administration Editor
in the work area for definition of the F-runtime group (Page 132).
To prevent F-runtime group cycle time monitoring from being triggered when there are no
pending faults and causing the F-CPU to go to STOP, you must set the maximum cycle time
of the F-runtime group high enough.
Use the Excel file for response time calculation
(http://support.automation.siemens.com/WW/view/en/49368678/133100) to determine the
minimum monitoring time for the F-runtime group cycle time. Note also the comments in the
Excel file.
For S7-1200/1500 F-CPUs, you can also use the "Cycle time warning limit of F-runtime
group (Page 137)", "Maximum cycle time of F-runtime group (Page 137)" and the tags
TCYC_CURR (Page 148) and TCYC_LONG (Page 148) for dimensioning.
A.1.2
Minimum monitoring time for safety-related communication between F-CPU and
F-I/O
Parameter "F-monitoring time"
You have two options for configuring the monitoring time of safety-related communication
between the F-CPU and F-I/O:
Centrally in the
hardware and network editor
during parameter assignment of the F-CPU
(Page 48); in the properties of the F-CPU, or
During parameter assignment of the F-I/O (Page 53) in the
hardware and network editor
;
in the properties of the F-I/O
"F-monitoring time" = PROFIsafe monitoring time TPSTO
The specified PROFIsafe monitoring time TPSTO must be high enough to prevent tripping the
F-cycle time monitoring when no faults are present.
Use the Excel file for response time calculation
(http://support.automation.siemens.com/WW/view/en/49368678/133100) available for
SIMATIC Safety to calculate the minimum monitoring time for safety-related communication
between the F-CPU and F-I/O.
Note also the comments in the Excel file.
Monitoring and response times
A.1 Configuring monitoring times
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 611
Check to determine whether configured PROFIsafe monitoring time is too short
Note
During commissioning of the F
-system, you can perform a check while safety mode is active
to determine whether the configured PROFIsafe monitoring time is too short.
This check of the PROFIsafe monitoring time is useful if you want to ensure that the
configured monitoring time exceeds the minim
um monitoring time by a sufficient amount. In
this way, you can avoid the possible occurrence of sporadic monitoring time errors.
Procedure:
1.
Insert an F-I/O (one that will not be needed later for system operation).
2.
Assign a shorter monitoring time for this F-I/O than for the F-I/O of the system.
3.
If the additional F-I/O fails and the "Monitoring time for safety message frame exceeded"
diagnostic is signaled, you have fallen below the minimum possible PROFIsafe
monitoring time.
4.
Increase the monitoring time for the added F-I/O just to the point where it no longer fails.
This monitoring time corresponds approximately to the minimum possible monitoring
time.
Conditions:
The F
-I/O to be inserted additionally and the F-
I/O whose PROFIsafe monitoring time is to be
c
hecked must have the following properties in common:
They must be inserted in the same rack
They must be nodes in the same subnet
Tip:
It may be useful to leave the additional F
-I/O in place for systems that will be modified or
expanded during operation af
ter commissioning. This F-I/O will then provide an early
warning in the event of changes in the time behavior, enabling you to avoid a process
shutdown triggered by the F
-I/O in the process.
Monitoring and response times
A.2 Response Times of Safety Functions
SIMATIC Safety - Configuring and Programming
612 Programming and Operating Manual, 10/2018, A5E02714440-AH
A.1.3
Minimum monitoring time of safety-related CPU-CPU communication
Input TIMEOUT at SENDDP and RCVDP or SENDS7 and RCVS7/F-monitoring time for
communication via Flexible F-Link
The time monitoring is performed in the SENDDP and RCVDP (Page 588) or SENDS7 and
RCVS7 (Page 599) instructions of the communication partner. You must assign the time
monitoring with identical monitoring time for both instructions at the TIMEOUT input.
You must specify a monitoring time TIMEOUT that is large enough so that monitoring is not
initiated when no faults are present.
For communication via Flexible F-Link you specify the F-monitoring time for the F-
communication when creating an F-communication (Page 96).
Use the Excel file for response time calculation
(http://support.automation.siemens.com/WW/view/en/49368678/133100) that is available for
SIMATIC Safety to determine the minimum value for TIMEOUT or the F-monitoring time.
Note also the comments in the Excel file.
A.1.4
Monitoring Time for Safety-Related Communication between F-Runtime Groups
Monitoring time for safety-related communication between F-runtime groups (S7-300, S7-400)
The monitoring time for safety-related communication between F-runtime groups is
determined automatically from the values for the "Maximum cycle time of F-runtime group"
(work area for Definition of the F-runtime group (Page 132) in the
Safety Administration
Editor
).
Monitoring time = (maximum cycle time of the 1st F-runtime group) + (maximum cycle time
of the 2nd F-runtime group)
Monitoring time for safety-related communication between F-runtime groups (S7-1200, S7-1500)
You can calculate the monitoring time for safety-related communication between F-runtime
groups from the values for the "Maximum cycle time of F-runtime group" (area for Definition
of the F-runtime group (Page 132) in the
Safety Administration Editor
), if you place the
default user program for the F-runtime group communication into pre-/postprocessing
(Page 87).
Monitoring time = (Maximum cycle time of the 1st F-runtime group) + (Maximum cycle time
of the 2nd F-runtime group).
Monitoring and response times
A.2 Response Times of Safety Functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 613
A.2
Response Times of Safety Functions
Definition of response time
The response time is the time from detection of an input signal until the linked output signal
changes.
Fluctuation range
The actual response time lies between a minimum response time and maximum response
time. You must always take the maximum response time into account in your system
configuration.
Rules for maximum response time of a safety function
The maximum response time of a safety function must be shorter than the process safety
time of the process.
Definition for process safety time of a process
The process safety time of a process is the time interval between the occurrence of an error,
within which the process can be left on its own without causing injury to operating personnel
or damage to the environment, and the point in time the response is completed.
The controlling F-system can perform any control during the process safety time, this
includes incorrectly or not at all. The process safety time of a process depends on the
process type and must be determined on a case-by-case basis.
Procedure for response time calculation
The Excel file for response time calculation
(http://support.automation.siemens.com/WW/view/en/49368678/133100) is available for
calculating the maximum response time of a safety function.
Use the Excel file to calculate the approximate maximum response time of the safety
function and then check that the process safety time of the process is not exceeded.
Monitoring and response times
A.2 Response Times of Safety Functions
SIMATIC Safety - Configuring and Programming
614 Programming and Operating Manual, 10/2018, A5E02714440-AH
If necessary, you must reduce the specific monitoring times of the F-system (see Minimum
monitoring time for safety-related communication between F-CPU and F-I/O (Page 610)).
WARNING
You may only use the Excel file for response time calculation or for timeout calculation
when using Flexible F-Link communication, if you have observed the following regulations
with regard to the standard instructions for consistent transfer of data:
CPU-CPU communication
(Page 262)
You must call the standard instruction for consistent sending of data and acknowledgments
in the postprocessing (Page 87) and the standard instruction for consistent receiving of
data and acknowledgments in the preprocessing (Page 87).
F-runtime group communication
(Page 145)
You have to call up the standard instruction UMOVE_BLK for transferring the data to be
sent in the postprocessing of the sending F-runtime group. You have to call the standard
instruction UMOVE_BLK for transferring the acknowledgment to be sent in the
postprocessing of the receiving F-runtime group.
(S089)
Monitoring and response times
A.2 Response Times of Safety Functions
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 615
WARNING
The response time of their safety function depends, among other things, on the cycle time
of the F-OB, the runtime of the F-runtime group and, when distributed F-I/O is used, the
parameter assignment of PROFINET/PROFIBUS.
Therefore, the configuration/parameter assignment of the standard system influences the
response time of its safety function.
Examples:
The increase in priority of a standard OB compared to an F-OB can extend the cycle
time of the F-OB or the runtime of the F-runtime group due to the higher-priority
processing of the standard OB. Please note that during creation of technology objects,
OBs with very high priority may be created automatically.
The change of the send clock cycle of PROFINET changes the cycle time of an F-OB
with event class "Synchronous cycle".
Note that the configuration / parameter assignment of the standard system is not subject to
access protection for the safety program and does not lead to a modification of the
collective F-signature.
If you do not take organizational measures to prevent changes in the configuration /
parameter assignment of the standard system with influence on the response time, you
must always set the monitoring times for the calculation of the maximum response time of a
safety function (see Configuring monitoring times (Page 608)).
The monitoring times are protected against change with the access protection of the safety
program and are recorded by the F-collective signature as well as the F-SW collective
signature.
When calculating with Excel file for response time calculation
(http://support.automation.siemens.com/WW/view/en/49368678/133100) you need to
consider the value that is specified for "Any standard system runtimes" as value for the
maximum response time.
(S085)
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 617
Checklist
B
Life cycle of fail-safe automation systems
The following table contains a checklist summarizing all activities in the life cycle of a
fail-safe SIMATIC Safety system, including requirements and rules that must be observed for
each activity.
Checklist
Legend:
Stand-alone section references refer to this documentation.
"F-SMs Manual"
refers to the Automation System S7-300, ET 200M Distributed I/O
System, Fail-Safe Signal Modules
(http://support.automation.siemens.com/WW/view/en/19026151) manual.
"F-Modules Manual"
refers to the ET 200S Distributed I/O System, Fail-Safe Modules
(http://support.automation.siemens.com/WW/view/en/27235629) manual.
"ET 200eco Manual"
refers to the ET 200eco Distributed I/O Station, Fail-Safe I/O Module
(http://support.automation.siemens.com/WW/view/en/19033850) manual.
"ET 200eco PN Manual"
refers to the ET 200eco PN F-DI 8 x 24 VDC, 4xM12 / F-DQ 3 x
24 VDC/2.0A PM, 3xM12.
(https://support.industry.siemens.com/cs/search?search=6ES7146-6FF00-
0AB0&type=Manual&lc=en-US) manual.
"ET 200pro Manual"
refers to the ET 200pro Distributed I/O System, Fail-Safe I/O Module
(http://support.automation.siemens.com/WW/view/en/22098524) manual.
"ET 200iSP Manual"
refers to the ET 200iSP Distributed I/O Device, Fail-Safe Modules
(http://support.automation.siemens.com/WW/view/en/47357221) manual.
"ET 200SP Manual
" refers to the ET 200SP System
(http://support.automation.siemens.com/WW/view/en/58649293) manual
"ET 200MP Manual
" refers to the S7-1500/ET 200MP Distributed I/O System
(http://support.automation.siemens.com/WW/view/en/59191792) manual
"ET 200SP Modules Manual"
refers to the device manuals for F-Modules of the ET
200SP Distributed I/O System
(https://support.industry.siemens.com/cs/ww/en/ps/14059/man)
Checklist
SIMATIC Safety - Configuring and Programming
618 Programming and Operating Manual, 10/2018, A5E02714440-AH
Phase
Note the following
Reference
Check
Planning
Requirement: "Safety
requirements specifica-
tion" available for the
intended application
Process-dependent
Specification of system
architecture
Process-dependent
Assignment of functions
and subfunctions to sys-
tem components
Process-dependent under Product Overview (Page 23)
Selection of sensors and
actuators
Requirements for actuators
F-SMs Manual
, section 6.5;
F-Modules Manual
, section 4.5;
ET 200eco Manual
, section 5.5
ET 200eco PN Manual
, section 5.2;
ET 200pro Manual
, section 4.4
ET 200S Manual
, section 4.5
ET 200SP manual
, section 5.2.2
ET 200MP manual
, section 5.2.2
Specification of required
safety properties for indi-
vidual components
IEC 61508:2010
Configuration
Installing the optional
package
Requirements for installation under Installing/uninstalling STEP 7 Safe-
ty Basic V15.1 optional package
(Page 30) orInstalling/uninstalling STEP 7
Safety Advanced V15.1 optional package
(Page 31)
Selection of S7 compo-
nents
Descriptions of configuration under Product Overview (Page 23);
F-SMs Manual
, section 3;
F-Modules Manual
, section 3;
ET 200eco Manual
, section 3
ET 200eco PN Manual
, section 4;
ET 200pro Manual
, section 2
ET 200iSP Manual
, section 3
ET 200SP Modules Manual
, section 3
ET 200MP Modules Manual
, section 3
Configuration of hardware Description of F-systems
Verification of utilized hardware com-
ponents based on Annex 1 of Report
in the Certificate
under Configuring (Page 43);
Annex 1 of Report on the Certificate
Checklist
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 619
Phase
Note the following
Reference
Check
Configuration of F-CPU Protection level, "Write protection for
F-blocks" (S7-300, S7-400)
Protection level, at least "Full access"
(S7-1200, S7-1500)
Password
F-capability enabled
Definition/setting of F-specific parame-
ters
Cycle time for the F-runtime group in
which the safety program is to be exe-
cuted, defined in accordance with the
requirements and safety regulations -
same as with standard system
under Configuring an F-CPU (Page 48);
Standard S7-300;
Standard S7-400;
S7-1200 standard;
S7-1500 standard;
under Monitoring and response times
(Page 607)
Configuration of F-I/O Settings for safety mode
Setting of passivation type
Configuring monitoring times
Defining sensor evaluation
Defining diagnostic behavior
Special F-parameters
Assigning names
Unique PROFIsafe address
under Configuring F-I/O (Page 53)
orPeculiarities when configuring fail-safe
GSD based DP slaves and fail-safe GSD
based I/O devices (Page 77)
under Monitoring and response times
(Page 607);
F-SMs Manual
, sections 3, 9, 10;
F-Modules Manual
, sections 2.4, 7;
ET 200eco Manual
, sections 3, 8;
ET 200eco PN Manual
, section 6;
ET 200pro Manual,
Sections 2.4, 8;
ET 200iSP Manual,
Sections 2.4, 7, 8
ET 200SP Modules Manual
, section 4
ET 200MP Modules Manual
, section 4
Programming
Defining program design
and structure
Follow warnings and notes on pro-
gramming
under Overview of Programming
(Page 111), Program structure of the
safety program (S7-300, S7-400)
(Page 111), Program structure of the
safety program (S7-1200, S7-1500)
(Page 114); Programming startup protec-
tion (Page 155);
Checklist
SIMATIC Safety - Configuring and Programming
620 Programming and Operating Manual, 10/2018, A5E02714440-AH
Phase
Note the following
Reference
Check
Creating the F-runtime
groups
Assignment of F-FB or F-FC as main
safety block to the calling block
(S7-300, S7-400) or F-OB (S7-1200,
S7-1500)
Setting maximum cycle time for the
F-runtime group in accordance with
requirements (dependent on process
and safety regulations)
Creating DB for F-runtime group
communication
(S7-300, S7-400) Call of main safety
blocks directly in OBs (e.g. OB 35),
FBs, or FCs
(S7-1200, S7-1500) Call of the main
safety block from the F-OB
under Defining F-Runtime Groups
(Page 132)
under Monitoring and response times
(Page 607)
Creating/inserting the F-
blocks
Generating, editing, and saving F-
FBs,
F-FCs, and F-DBs in accordance with
the requirements of the program struc-
ture
Description:
F-I/O access
Passivation and reintegration of
F-I/O
Inserting F-blocks from global li-
braries
Safety-related CPU-CPU commu-
nication
Communication with the standard
user program
under Creating F-blocks in FBD / LAD
(Page 151)
under Addressing F-I/O (Page 157)
under Implementation of user acknowl-
edgment (Page 187)
under Reuse of F-blocks (Page 154)
under Configuring and programming
communication (S7-300, S7-400)
(Page 201) and Configuring and pro-
gramming communication (S7-1200,
S7-1500) (Page 270)
under Data exchange between standard
user program and safety program
(Page 195)
Compiling the safety
program
under Compiling the safety program
(Page 311)
Implementing safety pro-
gram call (S7-300,
S7-400)
Check whether the main safety block is
called directly in OBs (e.g., OB 35), FBs,
or FCs.
under Defining F-Runtime Groups
(Page 132)
Installation
Hardware configuration Description of
Installation
Wiring
under Overview of Configuration
(Page 43); Particularities for configuring
the F-System (Page 46);
F-SMs Manual
, sections 5, 6;
F-Modules Manual
, sections 3, 4;
ET 200eco Manual
, sections 3, 4;
ET 200eco PN Manual
, sections 4, 5;
ET 200pro Manual,
Sections 2, 3;
ET 200iSP Manual,
sections 3 and 4;
ET 200SP Manual
, sections 4 and 5
ET 200MP Manual
, sections 4 and 5
Checklist
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 621
Phase
Note the following
Reference
Check
Commissioning, Testing
Switching on Description of commissioning same as
in standard
Standard S7-300;
S7-400 standard;
S7-1200 standard;
S7-1500 standard;
Standard-S7-1500 Software Controller;
WinAC RTX F
Downloading safety pro-
gram and standard user
program
Description
Downloading
Program identification
Comparing safety programs
under Downloading project data to an F-
CPU (Page 313)
under Comparing Safety Programs
(Page 339)
Testing the safety pro-
gram
Description of disabling of safety
mode
Procedures for changing safety
program data
under Downloading project data
(Page 313); Testing the safety program
(Page 347); Disabling safety mode
(Page 344)
Changing the safety pro-
gram
Description
Disabling safety mode
Changing the safety program
under Changing the safety program in
RUN mode (S7-300, S7-400) (Page 355);
Disabling safety mode (Page 344); Delet-
ing the safety program (Page 357);
Testing the safety-related
parameters
Description of configuration under Printing project data (Page 341);
F-SMs Manual
, sections 4, 9, 10;
F-Modules Manual
, sections 2.4, 7;
ET 200eco Manual
, sections 3, 8;
ET 200eco Manual
, section 6;
ET 200pro Manual,
Sections 2.4, 8;
ET 200iSP Manual,
Sections 2.4, 7, 8
ET 200SP Modules Manual
, section 4
ET 200MP Modules Manual
, section 4
System acceptance
Acceptance Description and notes on acceptance
Printouts
under System acceptance (Page 361)
Operation, maintenance
General operation Notes on operation under Notes on Safety Mode of the Safe-
ty Program (Page 383)
Access protection
under Access protection (Page 101)
Diagnostics Responses to faults and events under Guide to diagnostics (S7-300,
S7-400) (Page 389); Guide to diagnostics
(S7-1200) (Page 390); Guide to diagnos-
tics (S7-1500) (Page 390);
Checklist
SIMATIC Safety - Configuring and Programming
622 Programming and Operating Manual, 10/2018, A5E02714440-AH
Phase
Note the following
Reference
Check
Replacement of software
and hardware compo-
nents
Description
Module replacement
Update of operating systems of
F-CPU same as in standard
Update of SW components
Notes
Operating system update of IMs
under Replacing Software and Hardware
Components (Page 386); Addressing
F-I/O (Page 157);
Help on
STEP 7
Uninstallation, disassem-
bly
Notes for uninstalling software com-
ponents
Notes for disassembling modules
under Installing/uninstalling STEP 7 Safe-
ty Advanced V15.1 optional package
(Page 31); Installing/uninstalling STEP 7
Safety Basic V15.1 optional package
(Page 30); Replacing Software and
Hardware Components (Page 386);
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 623
Glossary
Access protection
→ Fail-safe systems must be protected against dangerous, unauthorized access. Access
protection for F-systems is implemented by assigning two passwords (one for the → F-CPU,
and one for the → safety program).
Automatically generated F-blocks
→ F-blocks that are automatically generated and, if necessary, called when the → safety
program is compiled, in order to generate an executable safety program from the safety
program programmed by the user.
Category
Category in accordance with ISO 13849-1:2015 or EN ISO 13849-1:2015
With SIMATIC Safety, use in → safety mode up to category 4 is possible.
Channel fault
Channel-specific fault, such as a wire break or short circuit.
CPU-wide
In the context of F-I/Os, "CPU-wide" means all F-I/Os assigned to an F-CPU: Central F-I/O
of this F-CPU as well as F-I/Os for which the F-CPU is DP master/IO controller and assigned
F-I/O in a shared device. An F-I/O that is addressed using I-slave-slave communication is
assigned to the F-CPU of the I-slave and not to the F-CPU of the DP master / IO controller.
In the context of safety-related CPU-CPU communication, "CPU-wide" encompasses all the
safety-related communication connections that are configured in an F-CPU.
CRC
Cyclic Redundancy Check → CRC signature
CRC signature
The validity of the process data in the → safety message frame, the correctness of the
assigned address relationships, and the safety-related parameters are validated by means of
a CRC signature contained in the safety message frame.
Glossary
SIMATIC Safety - Configuring and Programming
624 Programming and Operating Manual, 10/2018, A5E02714440-AH
DB for F-runtime group communication
-> F-DB for safety-related communication between F-runtime groups of a safety program.
Depassivation
→ Reintegration
Disabled safety mode
Temporary deactivation of → safety mode for test purposes, commissioning, etc.
The following actions are possible only in disabled safety mode:
Downloading changes of the → safety program to the -> F-CPU during ongoing operation
(in RUN mode)
Test functions such as "Modify" or other write access to data of the → safety program
(with limitations)
Whenever safety mode is deactivated, the safety of the system must be ensured by other
organizational measures, such as operation monitoring and manual safety shutdown.
Discrepancy analysis
Discrepancy analysis for equivalence or non-equivalence is used for fail-safe inputs to detect
errors caused by the time characteristic of two signals with the same functionality. The
discrepancy analysis is initiated when different levels are detected in two associated input
signals (when testing for non-equivalence: the same level). On expiration of an assignable
period (→ discrepancy time), a check is made to determine whether the difference in levels
(for non-equivalence testing, the same level) has disappeared after an assignable time
period, the so-called discrepancy time. If not, there is a discrepancy error. The discrepancy
analysis is performed between the two input signals of the 1oo2 evaluation of the sensors (→
sensor evaluation) in the fail-safe input.
Discrepancy time
Assignable time for the → discrepancy analysis. If the discrepancy time is set too high, the
fault detection time and → fault reaction time are prolonged unnecessarily. If the discrepancy
time is set too low, availability is decreased unnecessarily because a discrepancy error is
detected when, in reality, no error exists.
DP/DP coupler
Device for coupling two PROFIBUS DP subnets required for master-master communication
between → safety programs in different → F-CPUs in SIMATIC Safety and S7 Distributed
Safety.
Expert
The acceptance of a system, i.e., the safety-related acceptance test of the system, is usually
carried out by an independent expert (for example, from TÜV).
Glossary
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 625
Fail-safe GSD based DP slaves
Fail-safe GSD based DP slaves are standard slaves that are operated on PROFIBUS with
the DP protocol. They must operate in accordance with IEC 61784-1:2010 (Fieldbus profiles)
and the PROFIsafe bus profile. A GSD file is used for their configuration.
Fail-safe GSD based I/O devices
Fail-safe GSD based I/O devices are standard devices that are operated on PROFINET with
the I/O protocol. They must operate in accordance with IEC 61784-1:2010 (Fieldbus profiles)
and the PROFIsafe bus profile in V2-MODE. A GSD file is used for their configuration.
Fail-safe I/O modules
ET 200eco modules and ET 200eco PN modules that can be used for safety-related
operation (→ safety mode). These modules are equipped with integrated → safety functions.
They operate in accordance with IEC 61784-1:2010 (Fieldbus profiles) and the PROFIsafe
bus profile.
Fail-safe modules
Fail-safe modules ET 200SP, ET 200S, ET 200pro, ET 200iSP that can be used in the
ET 200SP, ET 200S, ET 200pro or ET 200iSP distributed I/O systems.
Fail-safe modules S7-1500/ET 200MP, which can be used centrally in an S7-1500 or in a
distributed I/O ET 200MP system.
Fail-safe module S7-1200 which can be used centrally in an S7-1200 system.
These modules are equipped with integrated safety functions ( Safety mode) for fail-safe
operation (→ Fail-safe operation). They operate in accordance with the → PROFIsafe bus
profile.
Fail-safe systems
Fail-safe systems (F-systems) are systems that remain in a safe state or immediately switch
to another safe state as soon as particular failures occur.
Fault reaction function
→ User safety function
Fault reaction time
The maximum fault reaction time for an F-system specifies the time between the occurrence
of any error and a safe reaction at all affected fail-safe outputs.
Glossary
SIMATIC Safety - Configuring and Programming
626 Programming and Operating Manual, 10/2018, A5E02714440-AH
F-blocks
The following fail-safe blocks are designated as F-blocks:
those created by the user in LAD or FBD
those created by the user as → F-DBs
those selected by the user from a global library
those added automatically in the → safety program (→ F-SBs, → automatically generated
F-blocks, → F-shared DB, → F-I/O DBs; instance DBs of F-FBs)
All F-blocks are shown in yellow in the project tree.
F-CALL
"F-call blocks" for the → safety program in
S7 Distributed Safety
.
F-collective signature
The F-collective signature uniquely identifies a particular state of safety-related project data.
It is important for the program identification as well as the on-site acceptance of the safety
program, for example by → experts.
F-communication address signature
The F-communication address signature is formed from the names and the F-communication
UUIDs of communication connections with Flexible F-Link that are used in the safety
program.
F-communication DBs
Fail-safe data blocks for the
safety-related CPU-CPU communication via S7 connections
Communication with Flexible F-Link
F-compliant PLC data type (UDT)
An F-compliant PLC data type (UDT) is a PLC data type (UDT) in which you can use all data
types that can be used in safety programs.
F-CPU
An F-CPU is a central processing unit with fail-safe capability that is approved for use in
SIMATIC Safety and in which a → safety program can run in addition to the → standard user
program.
Glossary
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 627
F-DBs
Optional fail-safe data blocks that can be read-/write-accessed from anywhere within the
safety program (exception: DBs for F-runtime group communication).
F-destination address
→ PROFIsafe address
F-FBs
Fail-safe function blocks (with instance DBs), in which the user programs the → safety
program in FBD or LAD.
F-FCs
Fail-safe FCs, in which the user programs the → safety program in → FBD or → LAD.
F-HW collective signature
The F-HW collective signature uniquely identifies a particular state of safety-related
hardware configuration. The F-HW collective signature is important to document the
change/non-change of the safety-related hardware configuration, for example in the context
of an acceptance of changes.
F-I/O
Collective name for fail-safe inputs and outputs available in
SIMATIC S7
for integration in
SIMATIC Safety, among others. The following are available:
→ ET 200eco fail-safe I/O module
→ ET 200eco PN fail-safe I/O module
→ S7-300 fail-safe signal modules
→ Fail-safe modules for S7-1200
→ Fail-safe modules for ET 200MP
→ Fail-safe modules for ET 200SP
→ Fail-safe modules for ET 200S
→ Fail-safe modules for ET 200pro
→ Fail-safe modules for ET 200iSP
→ Fail-safe GSD based DP slaves
→ Fail-safe GSD based I/O devices
Glossary
SIMATIC Safety - Configuring and Programming
628 Programming and Operating Manual, 10/2018, A5E02714440-AH
F-I/O DB
Fail-safe data block for F-CPUs to an → F-I/O in
STEP 7 Safety
. An F-I/O DB is automatically
created for each F-I/O when the F-I/O is configured in the
hardware and network editor
. The
F-I/O DB contains tags that the user can or must evaluate or write in the safety program as
follows:
For reintegration of the F-I/O after communication errors
For reintegration of F-I/O after F-I/O or channel faults
If the F-I/O must be passivated as a result of particular states of the safety program (for
example, group passivation)
For reassignment of parameters for fail-safe GSD based DP slaves/GSD based I/O
devices or enabling HART communication for the F-I/O with the corresponding
functionality
In order to evaluate whether fail-safe values or process data are output
F-I/O faults
Module-related F-I/O fault, such as a communication error or parameter assignment error
F-I/Os of PROFIsafe address type 1
F-I/Os which ensure the uniqueness of the PROFIsafe address solely with the F-destination
address, for example, ET 200S F-modules. The PROFIsafe address is usually assigned by
DIP switches.
F-I/Os of PROFIsafe address type 2
F-I/Os which can ensure the uniqueness of the PROFIsafe address with a combination of F-
source address and F-destination address, for example, S7-1500/ET 200MP F-modules. The
PROFIsafe address is usually assigned with
STEP 7 Safety
.
F-modules
→ Fail-safe modules
F-OB
The F-OB calls the main safety block of an F-runtime group in S7-1200/1500 F-CPUs.
F-runtime group
The → safety program consists of one or two F-runtime groups. An F-runtime group is a
logical construct of several associated → F-blocks. It is generated internally by the F-system.
An F-runtime group consists of the following F-blocks:
→ Main safety block, F-OB (S7-1200, S7-1500), if applicable → F-FBs/ → F-FCs, if applicable
→ F-DBs, → F-I/O DBs, F-blocks of global libraries, instance DBs, → F-SBs, and →
automatically generated F-blocks.
Glossary
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 629
F-runtime group information DB
The F-runtime group information DB provides key information on the corresponding → F-
runtime group and on the → safety program as a whole.
F-shared DB
(S7-300, S7-400) Fail-safe data block that contains all of the shared data of the → safety
program and additional information needed by the F-system. The F-shared DB is
automatically inserted and expanded when the hardware configuration is compiled. Using its
name F_GLOBDB, the user can evaluate certain data of the → safety program.
F-SMs
→ S7-300 fail-safe signal modules
F-source address
→ PROFIsafe address
F-SW collective signature
The F-SW collective signature uniquely identifies a particular state of the safety program.
The F-SW collective signature is important to document the change/non-change of the safety
program, for example in the context of an acceptance of changes.
F-system blocks
Fail-safe system blocks that are automatically inserted and called when the → safety
program is compiled in order to generate an executable safety program from the user's
safety program.
F-systems
→ Fail-safe systems
Hardware configuration
The hardware configuration encompasses the configuration of the standard parameters of
the CPUs and standard I/Os as well as the configuration of the safety-related parameters of
the F-CPUs and the I/Os.
I-device
The functionality of the "I-device" (intelligent I/O-device) of a CPU allows data exchange with
an I/O-controller and thus, its use as an intelligent preprocessor of sub-processes, for
example. In this case, the I-device is connected as an I/O-device to a "parent" I/O-controller.
Glossary
SIMATIC Safety - Configuring and Programming
630 Programming and Operating Manual, 10/2018, A5E02714440-AH
IE/PB link
Device for coupling PROFINET IO and PROFIBUS DP-systems required, among other
things, for IO-controller-I-slave communication between -> safety programs in different
F-CPUs in SIMATIC Safety.
i-parameter
Individual parameters of → fail-safe GSD based DP slaves and → fail-safe GSD based I/O
devices
I-slave
The functionality of the "I-slave" (intelligent DP slave) of a CPU allows data exchange with a
DP master and, thus, its use as an intelligent preprocessor of sub-processes, for example. In
this case, the I-slave is connected as a DP slave to a "parent" DP master.
Main safety block
"Introductory F-block" for fail-safe programming of the → safety program in
STEP 7 Safety
.
The main safety block is an → F-FB or → F-FC that the user assigns to the calling F-OB (S7-
1200, S7-1500) or block (OB, FC, FB) (S7-300, S7-400) of an → F-runtime group.
The main safety block contains the safety program and any calls of other → F-FBs/F-FCs for
program structuring.
Network-wide
A network consists of one or more subnets. "Network-wide" means beyond the boundaries of
the subnet. In PROFIBUS, a network includes all nodes accessible via PROFIBUS DP. In
PROFINET IO, a network includes all nodes accessible via RT_Class_1/2/32
(Ethernet/WLAN/Bluetooth, Layer 2) and if applicable RT_Class_UDP (IP, Layer 3).
Passivation
When passivation occurs in an → F-I/O with inputs, the → F-system provides the safety
program with fail-safe values (0) instead of the process data pending at the fail-safe inputs in
the PII.
When passivation occurs in an F-I/O with outputs, the F-system transfers fail-safe values (0)
to the fail-safe outputs instead of the output values in the PIQ provided by the safety
program.
PL
Performance Level (PL) in accordance with ISO 13849-1:2015 or EN ISO 13849-1:2015
With SIMATIC Safety, use up to Performance Level (PL) e is possible in → safety mode.
Glossary
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 631
PN/PN coupler
Device for coupling two PROFINET IO systems required for IO controller-IO controller
communication between → safety programs in different → F-CPUs in SIMATIC Safety and S7
Distributed Safety.
PROFIsafe
Safety-related bus profile of PROFIBUS DP and PROFINET IO for communication between
the → safety program and the → F-I/O in an → F-system. See IEC 61784-3-3:2010 or
PROFIsafe Profile for Safety Technology on PROFIBUS DP and PROFINET IO; Order No:
3.192 (V2.6.1).
PROFIsafe address
The PROFIsafe address (code name according to IEC 61784-3-3:2010) is used for
protection of standard addressing mechanisms, such as IP addresses. The PROFIsafe
address consists of an F-source address and an F-destination address. Each → F-I/O
therefore has two address parts, an F-source address and an F-destination address.
The F-source address is automatically assigned and is displayed for fail-safe GDS based DP
slaves/fail-safe GSD based I/O devices and F-modules ET 200SP, F-modules ET 200MP,
ET 200eco PN and F-modules S7-1200. The F-source address for F-modules ET 200S, ET
200eco, ET 200pro, ET 200iSP and F-SMs S7-300 is always 1. For F-modules ET
200SP/ET 200MP, the F-source address corresponds to the "Central F-source address"
parameter of the assigned F-CPU.
You need to configure the F-destination address in the
hardware and network editor
. You
assign the F-destination address for the ET 200S, ET 200eco, ET 200pro, ET 200iSP and F-
SMs S7-300 F-modules with a switch. For F-modules ET 200SP and F-modules ET 200MP,
ET 200eco PN assign the PROFIsafe address in the
hardware and network editor
. For S7-
1200 F-modules, the F-destination address is automatically assigned by the F-system.
Program signature
→ collective F-signature
Project data
The project data includes the → hardware configuration and the → user program.
Glossary
SIMATIC Safety - Configuring and Programming
632 Programming and Operating Manual, 10/2018, A5E02714440-AH
Reintegration
The switchover from fail-safe values (0) to process data (reintegration of an → F-I/O) takes
place automatically or following user acknowledgment in the F-I/O DB. The reintegration
method depends on the following:
The reason for → passivation of the F-I/O/channels of the F-I/O
The parameter assignment in the → F-I/O DB or in the configuration itself (for example,
ET 200MP fail-safe modules on an S7-1500 F-CPU and S7-1200 fail-safe modules on an
S7-1200 F-CPU)
Following reintegration for an → F-I/O module with inputs, the process data pending at the
inputs in the PII are provided again for the safety program. For an F-I/O with outputs, the F-
system again transfers the output values provided in the PIQ in the safety program to the
fail-safe outputs.
RIOforFA Safety
Remote IO for Factory Automation with PROFIsafe; profile for F-I/O
S7-300 fail-safe signal modules
Fail-safe signal modules of the S7-300 module series that can be used for safety-related
operation (→ Safety mode) as centralized modules in an S7-300 or as distributed modules in
the ET 200M distributed I/O system. The fail-safe signal modules are equipped with
integrated → safety functions. They operate in accordance with the → PROFIsafe bus profile.
S7-PLCSIM
The
S7-PLCSIM
application enables you to execute and test your program on a simulated
automation system on your programming device or PC. Because the simulation takes place
completely in your programming device or PC, you do not need any hardware (CPU, I/O).
Safe state
The basic principle of the safety concept in fail-safe systems is the existence of a safe
state for all process variables. For digital → F-I/O that conform to IEC 61508:2010, this is
always the value "0".
Safety Administration Editor
The
Safety Administration Editor
provides support for the main tasks of your safety program.
Safety function
Mechanism integrated in the → F-CPU and → F-I/O that allows them to be used in -> fail-safe
systems.
According to IEC 61508:2010, a function that is implemented by a safety device in order to
maintain the system in the safe state or bring the system to a safe state in the event of a
specific fault. (fault reaction function -> user safety function)
Glossary
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 633
Safety message frame
In → safety mode, data are transferred in a safety message frame between the → F-CPU and
→ F-I/O, or between the F-CPUs in safety-related CPU-CPU communication.
Safety mode
1. Operating mode of → F-I/O in which → safety-related communication can take place using
→ safety message frames.
2. Operating mode of the safety program. In safety mode of the safety program, all safety
mechanisms for error detection and fault reaction are enabled. In safety mode, the safety
program cannot be modified during operation. Safety mode can be disabled by the user
(→ disabled safety mode).
Safety program
Safety-related user program
Safety protocol
→ Safety message frame
Safety summary
The safety summary provides documentation of the safety-related project data which
supports you during acceptance of the system.
Safety-related communication
Safety-related communication is used to exchange fail-safe data.
Safety-related hardware configuration
The safety-related hardware configuration includes the configuration of the safety-related
parameters of the F-CPU as well as the configuration of the F-I/O devices.
Safety-related project data
The safety-related project data includes the safety-related hardware configuration as well as
the → safety program.
Sensor evaluation
There are two types of sensor evaluation:
1oo1 evaluation sensor signal is read once
1oo2 evaluation - sensor signal is read twice by the same → F-I/O and compared
internally
Glossary
SIMATIC Safety - Configuring and Programming
634 Programming and Operating Manual, 10/2018, A5E02714440-AH
Shared device
The "Shared Device" functionality enables distribution of the submodules of an IO-device
between different IO-controllers.
Signature
→ collective F-signatures
SIL
Safety integrity level SIL in accordance with IEC 61508:2010. The higher the Safety Integrity
Level, the more rigid the measures for prevention of systematic faults and for management
of systematic faults and random hardware failures.
With SIMATIC Safety, up to Safety Integrity Level SIL3 is possible in safety mode.
Standard communication
Communication used to exchange non-safety-related data
Standard mode
Operating mode of → F-I/O in which → safety-related communication between the F-CPU and
the F-I/O by means of → safety message frames is not possible; only → standard
communication is possible in this operating mode.
Standard user program
Non-safety-related user program
Startup of F-system
With an → F-CPU, the standard user program starts up in the normal way. When the → safety
program is started up, all F-DBs are initialized with the values from the load memory - as is
the case with a cold restart. This means that saved error information is lost.
The → F-system performs an automation → reintegration of the → F-I/O.
User program
The user program comprises the → standard user program and the → safety program.
User safety function
The → safety function for the process can be provided through a user safety function or a
fault reaction function. The user only has to program the user safety function. In the event of
an error, if the → F-system can no longer execute its actual user safety function, it executes
the fault reaction function: for example, the associated outputs are disabled, and the → F-
CPU switches to STOP mode, if necessary.
Glossary
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 635
Value status
The value status is additional binary information for a channel value. The value status is
entered in the process image input and provides information on the validity of the channel
value.
1: A valid process data is output for the channel value.
0: A fail-safe value is output for the channel value.
Versioned instruction
Instruction for which a version is displayed in the "Version" column of the "Instructions" task
card:
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 637
Index
=
=, 419
A
ABS, 536
Acceptance, 76
of safety-related changes, 378
of system, 361
Acceptance of safety-related changes, 378
Access
To tags of F-I/O DB, 174
Access permission
Canceling, 108
Setting up for the safety program, 103
Setup for F-CPU, 107
Validity, 103, 108
Access protection, 101, 101
ACK_GL, 487
ACK_NEC, 168
ACK_OP, 577
ACK_REI, 168
ACK_REQ, 172
Acknowledgment
Channel fault, 54
Fail-safe, 577
Add, 520
ADD, 520
Address assignment
Rules, 69, 71
AND, 414, 567, 567
Approvals, 4
Assignment, 402, 419
B
Behavior
After communication errors, 178
After F-I/O or channel faults, 180
After startup, 175
Bit logic operation
AND, 414
Assignment, 402, 419
EXCLUSIVE OR, 417
Insert binary input, 398
Invert RLO, 399, 402
Normally closed contact, 401
Normally open contact, 400
OR, 416
Reset output, 403, 420
Reset/set flip-flop, 407, 423
Scan operand for negative signal edge, 410, 426
Scan operand for positive signal edge, 409, 425
Scan RLO for negative signal edge, 413, 429
Scan RLO for positive signal edge, 412, 427
Set output, 404, 421
Set/reset flip-flop, 406, 422
Bit memory, 196
Block size of automatically generated F-blocks, 312
BO_W, 550
Breakpoints, 349
C
Category, 23
Central F-source address, 50
Change
Acceptance, 378
Detecting, 378
of the safety program in RUN mode, 355
Changing
Data of the safety program, 347
Channel fault, 54, 180
Acknowledgment, 54
Checking the program version, 376
Checklist, 617
Checks
through the F-system, 66
CMP <, 518
CMP <=, 515
CMP <>, 512
CMP ==, 511
CMP >, 517
CMP >=, 514
Code review of the safety program, 363
Collective F-signature, 344
Communication
Monitoring time, 610, 612
Standard user program and safety
program, 196, 197
Communication error, 178, 588
SENDDP/RCVDP, 588
Index
SIMATIC Safety - Configuring and Programming
638 Programming and Operating Manual, 10/2018, A5E02714440-AH
Comparator operations
Equal, 511
Greater or equal, 514
Greater than, 517
Less or equal, 515
Less than, 518
Not equal, 512
Comparing
Safety programs, 339
Compiling errors
Alarms, 311
Completeness
Checking the safety summary, 364
Configuration control, 58
Configuring
Fail-safe GSD based DP slaves, 77
Fail-safe GSD based I/O devices, 77
F-CPU, 48
F-I/O, 53
of F-components, 46
Overview, 43
Shared device, 63
Special features, 46
constants
Boolean, 123
FALSE, 123
TRUE, 123
Conversion operations
Convert BOOL to WORD, 550
Convert value, 548
Convert WORD to BOOL, 552
Scale values, 555
Convert
Data, 550, 552
Value, 548
CONVERT, 548
Convert data, 550, 552
Conveyor equipment, stopped, 445
Correctness
Hardware configuration, 368
Safety-related CPU-CPU communication, 374
Count
Down, 506
Up, 504
Up and down, 508
Count down, 506
Count up, 504
Count up and down, 508
CPU-CPU communication, 43
Options for safety-related, 43
Overview of safety-related, 201, 270, 307
Create twos complement, 533
CTD, 506
CTU, 504
CTUD, 508
Cycle time
F-runtime group, 135, 138
Maximum, 608
Monitoring time for, 610
D
Data block, 196
Data exchange
between standard user program and safety
program, 195
Data transfer
From safety program to standard user program, 196
From standard user program to safety program, 197
Data types
For safety program, 120
DB access, fully qualified, 124, 174
DB access, non-fully qualified, 125
Deleting
F-blocks, 357
DIAG
ESTOP1: Emergency STOP up to Stop Category
1,
EV1oo2DI: 1oo2 evaluation with discrepancy
analysis,
FDBACK: Feedback monitoring,
F-I/O DB, 172
MUT_P: Parallel muting,
MUTING: Muting,
RCVS7, 599
SENDDP/RCVDP, 588
SENDS7, 599
SFDOOR: Safety door monitoring,
TWO_H_EN: Two-hand monitoring with enable,
Diagnostic parameters, 389
Diagnostic tag, 389
Diagnostics
Fail-safe system, 389
Guide, 390, 390
DISABLE, 170
Disabling
F-capability, 48
Safety mode, 344
Discrepancy error, 445
DIV, 529
Divide, 529
Downloading
Hardware configuration, 313
Index
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 639
Safety program, 313
Standard user program, 313
Downloading Standard user program, 313
DP/DP coupler, 213, 281
E
Empty box
Inserting a LAD element, 393
Inserting an FBD element, 396
EN, 119
Enabling
F-capability, 48
Safety mode, 345
Enabling/disabling F-capability, 48
ENO, 119
ESTOP1, 430
EV1oo2DI, 468
EXCLUSIVE OR, 417, 570
Executing a system acceptance, 361
F
F_CRC_Seed, 79
F_IO_StructureDescCRC, 77, 79
F_Passivation, 79
Fail-safe acknowledgment, 577, 582
Fail-safe GSD based DP slaves
Configuring, 77
Fail-safe GSD based I/O devices
Configuring, 77
Fail-safe system, (See SIMATIC Safety)
Fail-safe value, 142, 162
F-array
read, 539, 542
Fault reaction function, 9, 24
FBD element
Inserting, 396
F-block
Copying, 152
Deleting, 357
F-change history, 359
F-channel faults, fail-safe value output, 163
F-Communication UUID, 96
F-compliant PLC data type (UDT), 126
F-components, 43
F-CPU, (See F-CPU), 43, 107
Configuring, 48
Going to STOP mode, 383
migrating, 36
Setting up access permission, 107
F-cycle time, monitoring time, 610
F-DB, 117
Creating, 151
for F-runtime group communication, 141
F-shared DB, 148
FDBACK, 475
F-destination address, 68, 70
F-destination address range, 49
F-FB, 117, 151
F-FC, 117, 151
F-I/O, 43
addressing, 157
Configuring, 53
Reintegration, 164, 175, 178, 180
Removing and inserting during operation, 386
F-I/O access, 157
During operation, 355
Restrictions in RUN mode, 356
Via the process image, 157, 246
F-I/O DB, 117, 166
Access to, 165, 174
Name, 55, 174
Number, 55, 174
Structure of DIAG, 172
F-I/O faults, fail-safe value output, 163
F-I/O or channel faults, 180
File type conversion, 122
Firmware update, 386
First steps, 42
Flexible F-Link, 96, 145, 262
Example, 266
F-monitoring time, 612
Flip-flop
Reset/set, 407, 423
Set/reset, 406, 422
F-monitoring time, 51, 56, 608
F-communication, 96
F-OB, 55, 117, 137
Move, 152
Form absolute value, 536
F-parameters, 46
F-runtime group, 111, 114, 117
Changing, 150, 151
Default setting, 134, 137
Defining, 135, 138
Deleting, 150
Maximum cycle time, 135, 138, 612
Rules, 132
Safety-related communication, 141
F-runtime group communication, 135, 138, 141, 145
Monitoring time, 612
Restrictions in RUN mode, 355
Index
SIMATIC Safety - Configuring and Programming
640 Programming and Operating Manual, 10/2018, A5E02714440-AH
F-runtime group information DB, 148
F-runtime groups signature, 148
F-shared DB, 148, 196, 344
F-source address, 50, 70
F-system
Checks, 66
Monitoring time, 607
Response time, 607
Fully qualified DB access, 124, 174
Function test of the safety program, 343, 363
G
Getting Started, 42
Global data block
Open, 565
Group diagnostics for fail-safe signal modules, 56
Group passivation, 184
GSD files
Configuration, 77
H
Hardware components, 25
Hardware configuration, 47
Checking for correctness, 368
Downloading, 313
Help
Open, 30, 31
HW identifier, 588
I
IE/PB link, 247, 304
Image
Creating, 329
running, 329
Implementation of user acknowledgment, 192
Importing of images, 329
Insert binary input, 398
Installation
STEP 7 Safety, 30, 31, 32
Instance DB, 125, 152
Instructions
for the safety program, 118
Get status bit OV, 587
Testing for acceptance, 365
IPAR_EN, 169
IPAR_OK, 172
J
JMP, 558
JMPN, 560
Jump
If RLO = 0, 560
If RLO = 1, 558
Jump label, 562
L
LABEL, 562
LAD element
Inserting, 393
Life cycle of fail-safe automation systems, 617
Light curtain, 445
Local data, 124
M
Main safety block, 117, 152
Math functions
Add, 520
Create twos complement, 533
Divide, 529
Form absolute value, 536
Multiply, 526
Subtract, 523
Maximum cycle time, 608, 612
Memory reset, 347
Migrating projects
from S7 Distributed Safety, 32
Migration
F-CPU, 36
from S7 Distributed Safety, 32, 251
Printout, 342
Modifying, 343
Safety program, 347, 347
Monitoring, 343
Safety program, 347, 347
Two-hand monitoring, 436, 439
Monitoring time, 607, 608
Communication between F-CPU and F-I/O, 610
Communication between F-CPUs, 612
Communication between I-salve and slave, 610
F-cycle time, 610
Move
Move value, 538
Read F-array, 539, 542
Write value indirectly to an F-DB, 544
MOVE, 538
Index
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 641
Move operations
Read value indirectly from an F-DB, 546
MUL, 526
Multiply, 526
MUT_P, 456
MUTING, 445
Structure of DIAG, 445
Muting operation
With 4 muting sensors, 445
With reflection light barriers, 445
N
N, 410, 426
N_TRIG, 413, 429
NEG, 533
Network
Inserting, 392, 396
Normally closed contact, 401
Normally open contact, 400
NOT, 402
O
Off delay, 499
Offline password, 103
Offline-online comparison of safety programs, 339
On delay, 494
Online password, 103
Operand
Scan for negative signal edge, 410, 426
Scan for positive signal edge, 409, 425
Operand area
For safety program, 121
Operating principle
RCVDP, 588
RCVS7, 599
SENDDP, 588
SENDS7, 599
Operating system update, 386
Operational safety of the system, 9
OPN, 565
Option handling, 58
OR, 416, 568, 568
Output
Reset, 403, 420
Set, 404, 421
OV, 585, 586, 587
P
P, 409, 425
P_TRIG, 412, 427
Parameter types, 120
Parameters, 456
Safety-related, 47
PASS_ON, 167
PASS_OUT, 171
Passivation
Channel-granular, 54
F-I/O, 175
Output of fail-safe values, 163
Passivation of F-I/O, 175
After communication errors, 178
After F-I/O or channel faults, 180
After startup, 175
Group passivation, 184
Password, 101, 345
F-CPU, 107
Offline, 103
Safety program, 103
Performance level, 23
PLC data type
F-compliant, 126
PLCSIM, 343, 347
PN/PN coupler, 204, 272
Printing
Project data, 341
Process image, 55, 157, 196
Process safety time, 613
Productive operation, 101
PROFIBUS DP, 25
PROFINET IO, 25
PROFIsafe address
assign, 73, 75
Assigning, 72, 78
Changing, 76
Recommendations, 65
PROFIsafe address type, 43
PROFIsafe address type 1, 49
PROFIsafe address type 2, 50
PROFIsafe destination address, 49
Program control operations
Jump if RLO = 0, 560
Jump if RLO = 1, 558
Jump label, 562
Open global data block, 565
Return, 564
Programming
Group passivation, 184
Overview, 111
Index
SIMATIC Safety - Configuring and Programming
642 Programming and Operating Manual, 10/2018, A5E02714440-AH
Startup protection, 155
Validity checks, 197
Programming an F-communication DB, 251
Project data
Printing, 341
Projects
upgrading, 37, 37, 38, 39
Proof test, 386
Protection level of the F-CPU, 52
Pulse
Generate, 489
Q
QBAD, 171, 174, 175
QBAD_I_xx, 171
QBAD_O_xx, 171
R
R, 403, 420
RCVDP, 208, 209, 218, 218, 226, 227, 232, 233, 276,
277, 285, 286, 293, 294, 299, 300, 344, 588
Behavior in the event of communication errors, 588
Receiving data, 588
Structure of DIAG, 588
Timing diagrams, 588
RCVS7, 250, 251, 344, 599
RD_ARRAY_DI, 539, 542
RD_FDB, 546
Readme file, 30, 31
Recommendations
PROFIsafe address, 65
Reflection light barriers, 445
Reintegration of F-I/O, 164, 168, 175
After communication errors, 178
After F-I/O or channel faults, 180
After startup of F-system, 175
Programming a user acknowledgment, 187, 192
with group passivation, 184
Replacing
Software components, 386
Response time of F-system, 607, 613
Restart inhibit
MUT_P, 456
MUTING, 445
On interruption of the light curtain, 445, 456
Restart protection, 155
RET, 564
Return, 564
RLO
Invert, 399, 402
Scan for negative signal edge, 413, 429
Scan for positive signal edge, 412, 427
RS, 407, 423
Rules
Address assignment, 69, 71
for testing, 347
RUN, 355
RUN mode, 355
S
S, 404, 421
S7 connection
Safety-related communication, 248
S7-PLCSIM, 343, 347
testing with, 350
Safety Administration Editor, 81
Safety function, 24
Calculation of response time, 613
Example, 24
Safety functions
ACK_GL: Global acknowledgment of all F-I/O in an
F-runtime group,
ESTOP1: Emergency STOP up to Stop Category
1,
EV1oo2DI: 1oo2 evaluation with discrepancy
analysis,
FDBACK: Feedback monitoring,
MUT_P: Parallel muting,
MUTING: Muting,
SFDOOR: Safety door monitoring,
TWO_H_EN: Two-hand monitoring with enable,
TWO_HAND: Two-hand monitoring,
Safety integrity level, 23
Safety mode
Disabling, 344
Enabling, 345
Safety program, 25
Automatic generation, 52
Code review, 363
Comparing, 339
Data types, 120
Deleting, 150
Downloading, 313
Function test, 343
Instructions, 118
Modifying, 343, 347, 347
Monitoring, 343, 347, 347
Online consistency, 375
Output of fail-safe values, 163
Index
SIMATIC Safety - Configuring and Programming
Programming and Operating Manual, 10/2018, A5E02714440-AH 643
Password, 103
Structuring, 111, 114
Testing, 347
Work memory requirement, 312
Safety requirements, 9, 23
Safety summary, 76, 341, 362
Safety-related communication between F-runtime
groups, 141
Safety-related communication via S7 connections
Configuring, 248
Data transfer limits, 255
Safety-related CPU-CPU
communication, 43, 201, 270, 307, 599
Checking for correctness, 374
F-communication DB, 251
Options, 43
RCVDP, 588
Restrictions in RUN mode, 355
SENDDP, 588
Safety-related IO controller-I-device communication
Configuring, 223, 290, 308
Data transfer limits, 229, 296
Programming, 227, 294
Safety-related IO controller-IO controller
communication
Configuring, 204, 272
Data transfer limits, 213, 281
Programming, 209, 277
Safety-related IO controller-I-slave
communication, 247, 304
Safety-related I-slave-I-slave communication
Configuring, 236
Data transfer limits, 235
Programming, 233
Safety-related I-slave-slave communication
Configuring, 241
Data transfer limits, 246
Safety-related master-I-slave communication
Configuring, 229, 297
Data transfer limits, 235, 303
Programming, 233, 300
Safety-related master-master communication
Configuring, 213, 281
Data transfer limits, 223, 290
Programming, 218, 286
Safety-related parameters, 47
Scale
Values, 555
SCALE, 555
SENDDP, 208, 209, 218, 218, 226, 227, 232, 233, 276,
277, 285, 286, 293, 294, 299, 300, 344, 588
Behavior in the event of communication errors, 588
Sending data, 588
Structure of DIAG, 588
Timing diagrams, 588
Sending and receiving data via S7 connections, 599
SENDS7, 250, 251, 344, 599
SFDOOR, 481
Shared device
Configuring, 63
Shift and rotate
Shift left, 574
Shift right, 571
Shift left, 574
Shift right, 571
SHL, 574
SHR, 571
Signature, 39
SIL, 23
SIMATIC Safety, 3, 23
Configuring and programming software, 25
Hardware and software components, 25
Principles of safety functions, 24
Product overview, 23
Safety program, 25
STEP 7 Safety optional package, 25
Simulation, 343
Simulation devices in the F-system, 383
Slice access, 122
Software components, 25, 386
Software requirements, 30, 31, 32
SR, 406, 422
Startup, 155, 175
Startup characteristics
MUT_P, 456
RCVDP, 588
RCVS7, 599
SENDDP, 588
SENDS7, 599
Startup protection, 155
Status bit OV
Get, 585, 587
Get negated, 586
STEP 7 Safety, 25
Additional support, 3
Basic knowledge, required, 3
Documentation, 4
Information landscape, 4
Service & Support, 3
Writing conventions, 7
STOP, 383
STP, 383
Structure of the safety program, 111, 114
SUB, 523
Index
SIMATIC Safety - Configuring and Programming
644 Programming and Operating Manual, 10/2018, A5E02714440-AH
Subtract, 523
Supported configurations, 66
T
Tag
F-I/O DB, 166
Monitoring/modifying, 347
Testing of safety program, 347
TIMEOUT, 608, 612
Timer operations
Generate off-delay, 499
Generate on-delay, 494
Generate pulse, 489
Timing diagrams, 445, 456, 588
RCVDP, 588
SENDDP, 588
TOF, 499
TON, 494
TP, 489
Training center, 3
Transfer area, 272
Truth table
AND, 415
EXCLUSIVE OR, 418
OR, 416
TÜV certificate, 365
TWO_H_EN, 439
TWO_HAND, 436
U
Uninstalling
STEP 7 Safety, 30, 31, 32
Upgrading
Projects, 37, 37, 38, 39
User acknowledgment, 187, 192, 445
Example, 191
HMI system, 188, 189
User safety function, 3, 24
V
V2-MODE, 77
Validity check, 197
Data transfer from standard program to safety
program, 376
Value
Convert, 548
Move, 538
Read indirectly from an F-DB, 546
Scale, 555
Write indirectly to an F-DB, 544
Value status, 159, 171
W
W_BO, 552
Watch table, 349
Wiring test, 347
Word logic operations
AND, 567
EXCLUSIVE OR, 570
OR, 568
Work memory requirement of safety program, 312
WR_FDB, 544
X
X, 417
XOR, 570