Professional Documents
Culture Documents
Important notes
Programming ___________________
Product Overview 1
___________________
Configuration 2
SIMATIC
___________________
Safety Administration Editor 3
Industrial Software
SIMATIC Safety - Configuring and ___________________
Access protection 4
Programming
___________________
Programming 5
Programming and Operating Manual
___________________
F-I/O access 6
Implementation of user
___________________
acknowledgment 7
Data exchange between
___________
8
standard user program and
safety program
Configuring and
___________
9
Programming
Communication
Compiling and
___________
10
commissioning a safety
program
___________________
System Acceptance Test 11
___________________
Operation and Maintenance 12
___________________
STEP 7 Safety Advanced
V11 Instructions 13
___________________
Monitoring and response
times A
___________________
Checklist B
08/2011
A5E02714440-01
Legal information
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
with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.
CAUTION
without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.
NOTICE
indicates that an unintended result or situation can occur if the relevant information is not taken into account.
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.
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
● Category 4 in accordance with EN 954-1
● Performance Level (PL) e according to ISO 13849-1: 2006 or in accordance with EN ISO
13849-1: 2008
The complete SIMATIC S7 documentation is available on DVD. You will find more
information on the Internet (http://www.automation.siemens.com/mcms/industrial-
automation-systems-simatic/en/manual-overview/manual-collection/Pages/Default.aspx).
Guide
This documentation describes how to work with the STEP 7 Safety Advanced V11 optional
package. 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 test
● 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 V11" appears in italics, it refers to the optional package for
the "SIMATIC Safety" F-system.
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 to obtain an overview of the safety requirements for the
system.
Additional support
If you have further questions about the use of products presented in this manual, contact
your local Siemens representative.
You will 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 will 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 will 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).
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 publishes a special newsletter to keep plant operators informed about
product developments and properties which may form important issues in terms of
operational safety. You should subscribe to the corresponding newsletter in order to obtain
the latest information and to allow you to modify your plant accordingly. Please go to the
Internet
(https://www.automation.siemens.com/WW/newsletter/guiThemes2Select.aspx?HTTPS=RE
DIR&subjectID=2) and register for the following newsletters:
SIMATIC S7-300/S7-300F
SIMATIC S7-400/S7-400H/S7-400F/FH
Distributed I/O
SIMATIC Industrial Software
To receive these newsletters, select the check box "Update".
Important notes.......................................................................................................................................... 3
1 Product Overview .................................................................................................................................... 17
1.1 Overview ......................................................................................................................................17
1.2 Hardware and Software Components..........................................................................................18
1.3 Installation/uninstallation of the STEP 7 Safety Advanced V11 optional package ......................21
1.4 Migration of projects from S7 Distributed Safety V5.4 SP5 to STEP 7 Safety Advanced
V11...............................................................................................................................................22
1.5 First steps.....................................................................................................................................24
2 Configuration ........................................................................................................................................... 25
2.1 Overview of Configuration............................................................................................................25
2.2 Particularities for configuring the F-System .................................................................................28
2.3 Configuring the F-CPU.................................................................................................................29
2.4 Configuring the F-I/O ...................................................................................................................33
2.5 Configuring fail-safe DP standard slaves and fail-safe standard I/O devices..............................38
3 Safety Administration Editor..................................................................................................................... 39
3.1 "General" tab................................................................................................................................41
3.2 "F-blocks" tab ...............................................................................................................................44
3.3 "Settings" tab................................................................................................................................45
4 Access protection .................................................................................................................................... 49
4.1 Overview of Access Protection ....................................................................................................49
4.2 Setting up, changing and revoking access permission for the safety program ...........................51
4.3 Setting up access permission for the F-CPU...............................................................................54
5 Programming ........................................................................................................................................... 55
5.1 Overview of Programming ...........................................................................................................55
5.1.1 Structure of the safety program ...................................................................................................56
5.1.2 Fail-Safe Blocks ...........................................................................................................................58
5.1.3 Restrictions in the programming languages FBD/LAD ................................................................59
5.2 Defining F-Runtime Groups .........................................................................................................65
5.2.1 Rules for F-Runtime Groups of the Safety Program....................................................................65
5.2.2 Procedure for Defining an F-Runtime Group ...............................................................................66
5.2.3 Safety-Related Communication between F-Runtime Groups of a Safety Program ....................69
5.2.4 Deleting an F-runtime group ........................................................................................................72
5.2.5 Modifying an F-runtime group ......................................................................................................72
$XWRPDWLRQV\VWHP
)FDSDEOH&38ZLWKVDIHW\SURJUDP
3URJUDPPLQJGHYLFH
)DLOVDIHLQSXWVRXWSXWV
67(3bb6DIHW\b$GYDQFHGb9RSWLRQDOSDFNDJH
'LVWULEXWHG,2V\VWHPLIQHFHVVDU\
&RQILJXULQJWRRO
3URJUDPPLQJWRRO )DLOVDIHLQSXWVRXWSXWV
2WKHUGLVWULEXWHG,2V\VWHPVLI
352),%86'3 QHFHVVDU\
352),1(7,2
)DLOVDIH'3VWDQGDUGVODYHVVWDQGDUG,2
GHYLFHVOLJKWJULGODVHUVFDQQHUHWFLI
QHFHVVDU\
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 error response are inserted when the safety program is compiled. This ensures that
failures and faults 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
inputs and outputs.
See also
Data Transfer from the Safety Program to the Standard User Program (Page 105)
Post-uninstall procedures
After uninstalling the STEP 7 Safety Advanced V11 optional package, you can no longer
open projects with F-CPUs whose F-capability is activated.
You may open and continue working with projects with F-CPUs whose F-capability was
previously deactivated (see also Configuring the F-CPU (Page 29)).
Introduction
In STEP 7 Safety Advanced V11 you may continue projects with safety programs that you
have created with S7 Distributed Safety V5.4 SP5. To that end, the projects must have been
compiled in S7 Distributed Safety V5.4 SP5 and then migrated.
Post-migration procedures
Once migration is complete, you obtain a complete project with a safety program which has
maintained the program structure of S7 Distributed Safety and the collective F-signature.
Therefore, the migrated project should not be considered a new one and can be loaded as it
is to the F-CPU as long as it has not been modified after migration.
Note
Safety printout
You cannot create a safety printout in STEP 7 Safety Advanced V11 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.
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 response time
(http://support.automation.siemens.com/WW/view/en/49368678/133100)).
Contents
The Getting Started documentation describes the creation of a single, continuous project that
is extended with each chapter. 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 addresses beginners but is also suitable for users that
are switching from S7 Distributed Safety.
Download
The Getting Started documentation is available as a PDF
(http://support.automation.siemens.com/WW/view/en/49972838) in the Service&Support
Portal free of charge.
Introduction
You configure a SIMATIC Safety F-system in basically the same way as a standard S7-300,
S7-400, or ET 200S/ET 200pro automation system in STEP 7 Professional.
This section presents only the essential differences compared to standard configuration you
encounter when configuring an SIMATIC Safety F-system.
Additional information
For detailed information on F-I/O, refer to the manuals for the relevant F-I/O.
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 the F-CPU (Page 29)" and "Configuring the F-I/O
(Page 33)".
Note
Inconsistencies are possible when configuring the hardware and can also be saved. A
consistency check of the hardware configuration and possible connection data is done only
on compilation. Therefore, perform "Edit > Compile" regularly.
Note
If you change a safety-relevant parameter (marked in yellow) for an F-I/O or an F-CPU, you
must Compiling the safety program (Page 169).
Introduction
You configure the F-CPU basically the same way as a standard automation system.
F-CPUs are always configurable STEP 7 Professional, regardless of whether the
STEP 7 Safety Advanced V11 optional package is installed or not. Without an installed
optional package, however, the F-CPU can only be used as a standard CPU.
When the STEP 7 Safety Advanced V11 optional package is installed, you can activate or
deactivate the F-capabiliity for the F-CPU.
The F-capability is activated by default.
Activating/deactivating 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. Open the "F-parameters".
3. Use the appropriate button to activate/deactivate the F-capability.
4. If you want to deactivate F-capability, confirm the "Turning off the F-activation" dialog with
"Yes".
Note
A change of the F-monitoring time of the F-CPU results in modifications to the safety
program when it is recompiled, and consequently, a new acceptance test may be
required.
Note
The "Base for PROFIsafe addresses" parameter has no influence on the following F-I/O:
SM 326; DI 8 x NAMUR (Order No. 6ES7326-1RF00-0AB0)
SM 326; DO 10 x DC 24V/2A (Order No. 6ES7326-2BF01-0AB0)
SM 336; AI 6 x 13 Bit (Order No. 6ES7336-1HE00-0AB0)
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal level to be transferred will
be captured on the sender side and transferred to the receiver if the signal level is pending
for at least as long as the assigned monitoring time. (S018)
Additional information can be found in Monitoring and response times (Page 523).
WARNING
In safety mode, no access may be granted by the CPU password when changes are made
in the standard user program, because changes can then also be made to the safety
program. To rule out this possibility, you must configure 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, then the
protection level "Write protection" or "Write/Read" 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). (See also Access protection (Page 49)) (S001)
Use the following procedure to configure the "Write protection for fail-safe blocks" protection
level:
1. Select the F-CPU in the device or network view, and select the "Properties" tab in the
inspector window.
2. Open the "Protection" area.
3. Set the corresponding protection level.
4. Enter a password for the write-read access in the fields designated for that purpose to
activate write protection.
For information on the password for F-CPU, refer to Access protection (Page 49). Pay
special attention to the warnings in Setting up access permission for the F-CPU (Page 54).
Introduction
You configure the ET 200S, ET 200eco, ET 200pro, ET 200iSP F-modules and the S7-300
F-SMs as usual in STEP 7 Professional:
After you have inserted the F-I/O in the work area of Device or network view, you access the
configuration dialogs by selecting the relevant F-I/O and the "Properties" tab.
Note
Note that channel-level 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 calculation
(http://support.automation.siemens.com/WW/view/en/49368678/133100)).
F-destination address
The F-destination address uniquely identifies the PROFIsafe destination (of the F-I/O).
Therefore, the F-destination address must be unique network-wide and station-wide (see the
following rules for address assignment).
To prevent incorrect parameter assignment, a station-wide unique F-destination address is
automatically assigned during placement of the F-I/O in the work area of the device or
network view.
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
"Base for PROFIsafe addresses" parameter (in the properties of the F-CPU) in SIMATIC
Safety F-systems differently, before placing the F-I/O in the various stations of a network.
Network-wide checking is only possible if the entire network is present in the project.
If you change the F-destination address, the station-wide uniqueness of the F-destination
address is checked automatically. You yourself must ensure the network-wide uniqueness of
the F-destination address.
You must set the F-destination address on the F-I/O using the DIP switch before installing
the F-I/O.
Note
For the following fail-safe S7-300 signal modules, the F-destination address = the start
address of the F-SM/8:
SM 326; DI 8 x NAMUR (Order No. 6ES7326-1RF00-0AB0)
SM 326; DO 10 x DC 24V/2A (Order No. 6ES7326-2BF01-0AB0)
SM 336; AI 6 x 13 Bit (Order No. 6ES7336-1HE00-0AB0)
As long as the start address of the F-SM lies in the process image, the F-destination address
is assigned automatically based on the "Base for PROFIsafe address" . Otherwise, the next
free start address and F-destination address is assigned for these F-SMs beginning with 1.
WARNING
* A network consists of one or more subnets. "Network-wide" means beyond the boundaries
of the subnet.
** "Station-wide" means for one device in the hardware and network editor (for example, a
SIMATIC S7-300 or an I-slave)
*** Provided that no PROFINET IO communication over several Ethernet subnets is used.
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal level to be transferred will
be captured on the sender side and transferred to the receiver if the signal level is pending
for at least as long as the assigned monitoring time. (S018)
Additional information can be found in Monitoring and response times (Page 523).
WARNING
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 (Order No. 6ES7326-1RF00-0AB0)
SM 326; DO 10 x DC 24V/2A (Order No. 6ES7326-2BF01-0AB0)
SM 336; AI 6 x 13 Bit (Order No. 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)
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.
Requirement
In order to use fail-safe DP standard slaves for SIMATIC Safety, these must be operated as
standard slaves on PROFIBUS DP and support the PROFIsafe bus profile. Fail-safe DP
standard slaves used in hybrid configurations on PROFIBUS DP and PROFINET IO based
on IE/PB link must support the PROFIsafe bus profile in V2 mode.
In order to use fail-safe standard I/O devices for SIMATIC Safety, the standard devices must
be on PROFINET IO and support the PROFIsafe bus profile in V2 mode.
Additional information
You will find the description of the parameters in the Help on fail-safe DP standard slaves
and standard I/O devices.
Requirement
The Safety Administration Editor is visible as a line in the project tree, if you have configured
a CPU as an F-CPU in the project, i.e., the "F-capability activated" option must be selected
(in the properties of the F-CPU).
To call the Safety Administration Editor, proceed as follows:
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 context
menu for the Safety Administration Editor.
Result
The Safety Administration Editor for your F-CPU is opened in the work area.
"Program signature"
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 assigned for
a safety program.
— The safety program status could not be determined.
See also
Deactivating Safety Mode (Page 190)
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.
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
● Offline 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
● Offline signature
● Online signature
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 183)".
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.
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.
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)
Maximum possible amount of local data as a function of local data requirement of main safety block
and higher-level standard user program
6WDQGDUGXVHUSURJUDP
6DIHW\SURJUDP
)UXQWLPHJURXS[
0DLQVDIHW\
2%[ EORFN
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 larger 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 Professional).
6WDQGDUGXVHUSURJUDP 6DIHW\SURJUDP
6WDQGDUG
XVHUSURJUDP$
)UXQWLPHJURXS[
)%)&
0DLQVDIHW\
EORFN
2%[ 6WDQGDUG
XVHUSURJUDP%
)%)&
Set the "Local data used in safety program" parameter to the value calculated for Case 1,
minus the local data requirement of the standard user program A (if the 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 Professional).
"Advanced settings"
If you deselect the "Safety mode can be disabled" option, you can prevent the deactivation of
safety mode for a safety program.
When you change the setting for this option, you must recompile the safety program and
download it to the F-CPU.
WARNING
Access to the SIMATIC Safety F-system without access protection is intended for test
purposes, commissioning, etc., when the plant is not in productive operation mode. You
must guarantee the safety of the plant through other organizational measures, for example,
restricted access to certain areas.
Before you transition into productive operation mode, you must have set up and activated
access protection. (S005)
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.
4.2 Setting up, changing and revoking access permission for the safety
program
Note
You cannot define the online password separately; the assigned offline password is
applied. The online password is used to identify the F-CPU. Following a change to the
offline password, the online and offline passwords may differ until the next time the offline
safety program is loaded to the F-CPU.
Note
Use different passwords for the F-CPU and the safety program to optimize access
protection.
NOTICE
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 password
protection 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 safety
program before leaving the programming device or PC. If this is not strictly
implemented, a screen saver equipped with a password accessible only to
authorized personnel must also be used.
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 Professional 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)
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 control 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
6WDQGDUGXVHUSURJUDP ,QVWUXFWLRQV
6DIHW\SURJUDP WDVNFDUG
*HQHUDO
3URFHVVLQJRI %LWORJLFRSHUDWLRQV
)EORFNVFUHDWHG 6DIHW\IXQFWLRQV
RULQVHUWHGE\ 7LPHURSHUDWLRQV
WKHXVHU &RXQWHURSHUDWLRQV
&RPSDUDWRURSHUDWLRQV
)'%[\ 0DWKIXQFWLRQV
0RYHRSHUDWLRQV
&RQYHUVLRQRSHUDWLRQV
3URJUDPFRQWURORSHUDWLRQV
:RUGORJLFRSHUDWLRQV
3URFHVVLQJRI 6KLIWDQGURWDWH
DXWRPDWLFDOO\ )ತ,2 2SHUDWRUFRQWURORSHUDWLRQV
DGGHG)EORFNV '%[\ $GGLWLRQDOLQVWUXFWLRQV
IDXOWFRQWURO
PHDVXUHV )6%V
6(1''3
6(1'6
&RPPXQLFDWLRQ
RSWLRQDO
3URFHVVLPDJH
RXWSXWLVZULWWHQ $XWRPDWL
WRWKHRXWSXWVRI FDOO\ )VKDUHG
WKH),2 JHQHUDWHG '%
)EORFNV
&DOOE\XVHU :ULWHUHDG
$XWRPDWLFDOO\FDOOHG )URP,QVWUXFWLRQVWDVNFDUG
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 OB)
● Possible additional F-FBs or F-FCs that you program using F-FBD or F-LAD, as needed
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 shared libraries
● F-system blocks F-SBs
● Automatically generated F-blocks
F-block Function
Main safety block The first step in programming of the safety program is the main safety block.
The main safety block is an F-FC or F-FB (with instance DB), which, by being
called by a standard block (recommendation: OB 35), becomes the main
safety block.
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 shared libraries
F-DB Optional fail-safe data blocks that can be read- and write-accessed within the
entire safety program.
F-I/O DB An F-I/O DB is automatically generated for each F-I/O when it is configured.
You can or you must access the tags of the F-I/O DB in conjunction with F-I/O
accesses.
Additional information
For a detailed description of the instructions for the safety program, refer to Overview of
instructions (Page 219).
Supported instructions
You will find the supported instructions in the description of the instructions (starting from
Overview of instructions (Page 219)).
Note
Preconnection of enable input EN or evaluation of enable output ENO is not possible.
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 local data element.
Make sure that the initialization of the local data element is not skipped over by JMP, JMPN.
or RET instructions (branching).
The "local data bit" should be initialized with the Assign ("=") (FBD) or ("--( )") (LAD)
instruction. Assign the local data bit 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. One of the following diagnostic events is
then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
,17
)B'$7$B9$/8(B$ ,1 )B'$7$B5(68/7
)B'$7$B9$/8(B% ,1
'%
231
1HWZRUN
,17
'%: ,1 '%;
'%: ,1
Rules
Note the following:
● The channels of an F-I/O can only be accessed from one 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 the F-runtime group from which the channels of this F-I/O are 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 can only be accessed from the F-runtime group in which the associated F-
FB is called.
● Individual tags of F-DBs (except the F-shared DB) can only be used in one F-runtime
group (however, an F-DB can be used in more than one F-runtime group).
● 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.
● The F-communication DB can only be accessed from one F-runtime group.
● F-blocks must not be called directly in an OB; rather, they must be inserted into a F-
runtime group.
● 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.
● Within a cyclic interrupt OB, the F-runtime group should be executed before the standard
user program; that is, 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.
● A main safety block may only be called once. In addition, you must not call it with different
instance DBs. Multiple calls are not permitted and can cause the F-CPU to go to STOP
mode.
● The process image input and output of standard I/O, bit memory, and data of DBs of the
standard user program may be accessed from more than one F-runtime group. (See also
Data exchange between standard user program and safety program (Page 105))
● 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 which 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 test.
Requirements
In your project you have selected an F-CPU from the "Hardware catalog" task card and
inserted it into the hardware and network editor. In the "Properties" tab of the F-CPU, the "F-
capability activated" check box is selected (default setting).
5. The F-CPU monitors the F-cycle time in the F-runtime group. For "Maximum cycle time of
F-runtime group", enter the maximum permitted time between two calls of this F-runtime
group (maximum of 1000 ms).
WARNING
The F-runtime group call interval is monitored for the maximum value; that is, monitoring
is performed to determine whether the call is executed often enough, but not whether it
is executed too often. For this reason, fail-safe timers must be implemented using the
TP, TON, or TOF instructions (Page 453) from the "Instructions" task card and not using
counters (OB calls). (S007)
6. If one F-runtime group is to provide data 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 Safety-Related Communication between
F-Runtime Groups of a Safety Program (Page 69))
7. Create an additional F-runtime group, by clicking 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.
9. If the main safety block is an F-FB, then assign an instance DB to the main safety block.
The instance DB is generated automatically in the project tree.
10.Execute the above-mentioned steps 3 and 4 to complete generation of the second 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 data as possible are exchanged between the F-runtime groups.
Note
The data read from another F-runtime group are as up-to-date as they were when the F-
runtime group providing the data finished processing before the start of the F-runtime group
reading the data.
If the furnished data undergo multiple changes while the F-runtime group furnishing the data
is being processed, the F-runtime group reading the data always receives the last change.
1
[ [ [
)$/*
W
)$/*
① Startup of F-system
Cycle time of the OB in which the F-runtime group is called.
... Data element of F-runtime group 1, written to DB for F-runtime group communication
of F-runtime group 1
data element 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
Reading of data from F-runtime group 1 that has a shorter OB cycle and higher priority than
F-runtime group 2
1
[ [ [ [ [ [ [ [
)$/*
[ [ [
)$/*
① Startup of F-system
Cycle time of the OB in which the F-runtime group is called.
... Data element of F-runtime group 1, written to DB for F-runtime group communication
of F-runtime group 1
... Data element 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
Note
If the F-runtime group whose DB for F-runtime group communication supplies the data to be
read is not processed (main safety block of the F-runtime group is not called), the F-CPU
goes to STOP mode. One of the following diagnostic events is then entered in the diagnostic
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"
Note
If you want to delete your 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 the F-capability for the F-CPU (see Configuring the F-CPU (Page 29)).
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.
Note
The main safety block must not contain any parameters, as they cannot be provided with
actual values when the block is called.
NOTICE
Editing the instance DB of F-FBs is not permitted online or offline and can cause the F-CPU
to go to STOP mode.
Note
Accesses to static parameters of instance DBs of other F-FBs are not permitted.
Note
Output parameters of F-FCs must always be initialized.
The F-CPU can go to STOP if this is not observed. One of the following diagnostic events is
then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
If you wish to assign an operand from the data area (data block) to a formal parameter of an
F-FC as an actual parameter, you must use fully qualified DB access.
Note
Note that access to the input parameters in an F-FB/F-FC is read-only, while access to the
output parameters is write-only.
Use an in/out parameter if you wish to have both read and write access.
Note
For greater clarity, assign unique symbolic names to the F-blocks you have created. These
symbolic names appear in the project tree and in the block interface. Symbolic names are
assigned in the same way as for standard blocks.
If you have inserted an instruction or an F-FB as a multi-instance, you must note the
following:
● You must not use static data of the multi-instance as an operand of an instruction or
actual parameter of an F-FB/F-FC.
● You may use inputs and outputs of the multi-instance only in the F-FB in which the multi-
instance is declared as operand of an instruction or actual parameter of an F-FB / F-FC.
Copying F-blocks
You can copy F-FBs, F-FCs, and F-DBs in exactly the same was as blocks of the standard
user program.
Exception:
Blocks from the "Program blocks > System blocks > STEP 7 Safety > Compiler blocks"
folder must not be copied
Introduction
You have the option to store F-blocks in global libraries or the project library.
Global libraries
In global libraries, you can store, among others, F-blocks that you would like to reuse across
projects. You must explicitly create global libraries. Additional information on global libraries
can be found in the help on STEP 7 Professional in "Using libraries".
Project library
In the project library, you can store elements that you would like to use repeatedly within the
project. The project library is created and stored automatically along with the project.
Additional information on project libraries can be found in the help on STEP 7 Professional in
"Using libraries".
Introduction
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 data blocks with F-attribute
are initialized with the values from the load memory - as is the case during a cold restart.
This means that saved error information is lost.
The F-system automatically reintegrates the F-I/O.
An operation 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 prevention 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)
See also
F-I/O DB (Page 82)
Implementing User Acknowledgment in the Safety Program of the F-CPU of a DP Master or
IO Controller (Page 99)
Implementing user acknowledgment in the safety program of the F-CPU of a I-slave or I-
device (Page 102)
Overview
The following describes how you can access the F-I/O and the special characteristics you
must consider when programming this access.
Note
Due to the special safety protocol, the F-I/O occupies a larger area of the process image
than is required for the channels that are actually present on the F-I/O. To find out the area
of the process image where the channel data (user data) are stored, refer to the relevant
manuals for the F-I/O. When the process image is accessed in the safety program, only the
channels that are actually present are permitted to be accessed.
Note that for certain F-I/O (such as S7-300 F-SMs and ET 200S fail-safe modules), a "1oo2
evaluation of the sensors can be specified. To find out which of the channels combined by
the "1oo2 evaluation of the sensors" you can access in the safety program, refer to the
relevant manuals for the F-I/O.
See also
Safety-Related I-Slave-Slave Communication - F-I/O Access (Page 153)
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
QBAD/QBAD_I_xx/QBAD_O_xx. (S009)
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. The F-system overwrites the associated PIQ with fail-safe values (0).
Note
Note that for channel faults in the F-I/O, channel-level 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 reintegrates all channels whose faults were eliminated;
faulty channels remain passivated.
See also
Configuring the F-I/O (Page 33)
6.3 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 or
must evaluate or 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.
Tags of an F-I/O DB
The following table shows the tags of an F-I/O DB:
PASS_ON
The PASS_ON tag allows you to enable passivation of an F-I/O, for example, as a function
of particular states in your safety program.
Using the PASS_ON tag in the F-I/O DB, you can passivate F-I/O; channel-level passivation
is not possible.
As long as PASS_ON = 1, passivation of the associated F-I/O occurs.
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, the relevant channels are passivated if channel-level passivation is
configured. 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
Note
The initial value for ACK_NEC is 1 following creation of the F-I/O DB. If you do not require
automatic reintegration, you must not write ACK_NEC.
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 are passivated. If channel faults are detected, the relevant channels are passivated if
channel-level passivation is configured. 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 elimination of faults requires a user acknowledgment with a positive edge at the
ACK_REI tag of the F-I/O DB:
● After every communication error
● After F-I/O faults or channel faults when ACK_NEC = 1 is assigned
Reintegration after channel faults reintegrates all channels whose faults were eliminated.
Acknowledgment is not possible until tag ACK_REQ = 1.
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 allowed. (S011)
Note
Alternatively, you can use the "ACK_GL" instruction 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 Advanced V11) (Page 295)).
IPAR_EN
The IPAR_EN tag corresponds to the iPar_EN_C tag in the PROFIsafe bus profile,
PROFIsafe Specification V1.20 and higher.
Fail-safe DP standard slaves/standard I/O devices
To find out when this tag must be set or reset when parameters of fail-safe DP standard
slaves/standard I/O devices are reassigned, consult the PROFIsafe Specification V1.20 or
higher or the documentation for the fail-safe DP standard slave/standard 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 "Enable HART communication" 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/channel fault (PASS_OUT = 0).
Example of enabling HART communication
1HWZRUN(QDEOH+$57FRPPXQLFDWLRQ
&21',7,21B )B)$,[%LWB
+$57,3$5B(1
&21',7,21B
1HWZRUN'HWHUPLQDWLRQRI(QDEOH+$57FRPPXQLFDWLRQ
(1$%/(B
)B)$,[%LWB +$57B&200
+$57,3$5B2.
56
1 5
('*(B%,7B0(025<
)B)$,[%LWB
6 4
+$57,3$5B(1
Further 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 online help on the module.
PASS_OUT/QBAD/QBAD_I_xx/QBAD_O_xx
If you have configured channel-level passivation for the F-I/O, then PASS_OUT = 1 and
QBAD = 1 indicate that at least one channel was passivated. QBAD_I_xx and QBAD_O_xx
indicate the input and output channels that were passivated.
If you have configured passivation of the entire F-I/O, tags PASS_OUT = 1 and QBAD = 1
indicate that passivation of the entire F-I/O has occurred.
The F-system sets PASS_OUT, QBAD, QBAD_I_xx, and QBAD_O_xx = 1, as long as the
fail-safe value is used instead of process data for the associated F-I/O or individual channels
of the F-I/O.
If you enable passivation via PASS_ON = 1, however, only QBAD, QBAD_I_xx, and
QBAD_O_xx = 1 are set. PASS_OUT does not change its value during passivation via
PASS_ON = 1. PASS_OUT can therefore be used for group passivation of additional F-I/O.
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-level passivation, the F-system sets ACK_REQ = 1
as soon as the channel fault is corrected. User acknowledgement 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 faults or channel faults may only be
possible some minutes after the fault has been eliminated due to necessary test signal
inputs (see F-I/O manuals).
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 DP standard slaves/standard I/O devices
To find out how to evaluate this tag when parameters of fail-safe DP standard slaves or
standard I/O devices are reassigned, consult the PROFIsafe Specification V1.20 or higher or
the documentation for the fail-safe DP standard slave/standard I/O device.
HART communication with SM 336; F-AI 6 x 0/4 ... 20 mA HART
See section "IPAR_EN"
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.
Note
In the safety program, you can use the MOVE instruction to assign this tag to a standard
data element.
Structure of DIAG
See also
Configuring the F-I/O (Page 33)
After F-I/O / channel faults (Page 94)
Group passivation (Page 97)
MOVE: Move value (STEP 7 Safety Advanced V11) (Page 327)
25
)BBB)B',B'&9
,1
4%$' 7DJB5HVXOW
7DJB9DOXH ,1 287
Overview
In the following you will find information on passivation and reintegration of F-I/O.
Note
The signal sequences shown refer to the status of signals in the user's safety program. If
the signals are evaluated in the standard user program before or after the safety program
is called in the same OB, the status change of the signals can be displaced by one cycle.
Contrary to what is shown in the signal charts, status changes between process data and
fail-safe values that are transmitted to the fail-safe outputs ("To Outputs" signal
sequence) can occur before the status change of the associated QBAD signal, if
necessary. The timing of the status change is dependent on whether F-I/O with outputs or
F-I/O with inputs and outputs were used.
Reintegration of F-I/O
Reintegration of the F-I/O, that is, the provision of process data in the PII or the transfer of
process data provided in the PIQ to the fail-safe outputs, takes place automatically no
sooner than the second cycle of the F-runtime group after startup of the F-system; this
happens regardless of the setting for the ACK_NEC tag. 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.
Signal sequence for passivation and reintegration of F-I/O after F-system startup
6WDUWXSRI)V\VWHP $XWRPDWLFUHLQWHJUD $XWRPDWLFUHLQWHJUD
SDVVLYDWLRQ WLRQHJWKLUGF\FOH ( WLRQHJILIWKF\FOH (
$
)DLOVDIHYDOXHV
3$( 3URFHVVYDOXHV
(
)DLOVDIHYDOXHV 3URFHVVYDOXHV
WRRXWSXWV
4%$' )DLOVDIHYDOXHVDUHRXWSXW $
4%$'B,B[[
4%$'B2B[[ (
3$66B287 3DVVLYDWLRQRXWSXWVHW
$
$&.B5(4
$&.B5(,
( IRU),2ZLWKLQSXWV
$ IRU),2ZLWKRXWSXWVRU),2ZLWKLQSXWVDQGRXWSXWV
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 data blocks with F-attribute
are initialized with the values from the load memory - as is the case during a cold restart.
This means that saved error information is lost.
The F-system automatically reintegrates the F-I/O.
A data handling 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)
See also
Programming startup protection (Page 76)
after communication errors (Page 92)
Reintegration of F-I/O
Reintegration of the relevant F-I/O, that is, provision of process data in the PII or transfer of
process data provided in the PIQ to the fail-safe 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 82) 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 Advanced V11)
(Page 295))
Signal sequence for passivation and reintegration of F-I/O after communication errors
Communication faults / No more communication fault
passivation Reintegration
( $
Fail-safe values
3$( Process values Process values
Fail-safe values
WRRXWSXWV Process values Process values
3$66B287 (
Acknowledgment request
$&.B5(4
User acknowledgement
$&.B5(,
DIAG bit set
',$*ELW[
See also
Implementing User Acknowledgment in the Safety Program of the F-CPU of a DP Master or
IO Controller (Page 99)
Implementing user acknowledgment in the safety program of the F-CPU of a I-slave or I-
device (Page 102)
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 transfer of process data provided in the PIQ to the fail-safe outputs,
takes place only when the following occurs:
● All F-I/O faults or channel faults have been eliminated.
If you have configured channel-level passivation for the F-I/O, the relevant channels are
reintegrated once the fault is corrected; any faulty channels remain passivated.
Reintegration takes place as follows, depending on your setting for the ACK_NEC tag:
● When ACK_NEC = 0, automatic reintegration takes place as soon as the F-system
detects that the fault has been eliminated. 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 place several minutes after completion of
necessary test signal inputs, which are used by the F-I/O to determine that the fault has
been eliminated.
● With ACK_NEC = 1, reintegration takes place only as a result of a user acknowledgement
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.
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.
If for this case, automatic reintegration is not permitted for the relevant process, you
must program startup protection by evaluating tags QBAD or QBAD_I_xx and
QBAD_O_xx 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)
Signal sequence for passivation and reintegration of F-I/O after F-I/O faults or channel faults when
ACK_NEC = 0 (for passivation of entire F-I/O after channel faults)
),2FKDQQHOIDXOWV $XWRPDWLFUHLQWHJUDWLRQRI
),2FKDQQHOIDXOWVSDVVLY HOLPLQDWLRQ FRPSOHWHGWHVWVLJQDOVZLWFKLQJ $
DWLRQ $XWRPDWLFUHLQWHJUDWLRQ PD\RFFXURQO\ZLWKLQPLQXWHV
(
$
)DLOVDIHYDOXHV
3$( 3URFHVVYDOXHV 3URFHVVYDOXHV
)DLOVDIHYDOXHV
WRRXWSXWV 3URFHVVYDOXHV 3URFHVVYDOXHV
$
)DLOVDIHYDOXHVDUHRXWSXW
4%$'
4%$'B,B[[ (
4%$'B2B[[ $
3DVVLYDWLRQRXWSXWVHW
3$66B287 (
$&.B1(&
$&.B5(4
$&.B5(,
',$*ELWVHW
$
',$*ELW (
( IRU),2ZLWKLQSXWV
IRU),2ZLWKRXWSXWVRU),2ZLWKLQSXWVDQGRXWSXWV
$ 6LJQDOVHTXHQFHGHSHQGVRQWKH),2XVHG
Signal sequence for passivation and reintegration of F-I/O after F-I/O faults and channel faults when
ACK_NEC = 1 (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 faults or
channel faults when ACK_NEC = 1 (initial value), see Passivation and reintegration of F-I/O
(Page 89).
Signal sequence for passivation and reintegration of F-I/O after channel faults when ACK_NEC = 1
(for channel-level passivation)
Example for an F-I/O with inputs:
1 2 3 4 5 6
)DLOVDIHYDOXH
3,,&KDQQHO 3URFHVVGDWD 3URFHVVGDWD
)DLOVDIHYDOXH
3,,&KDQQHO 3URFHVVGDWD 3URFHVVGDWD
)DLOVDIHYDOXHLVRXWSXWIRUFKDQQHO
4%$'B,B
)DLOVDIHYDOXHLVRXWSXWIRUFKDQQHO
4%$'B,B
$WOHDVWFKDQQHOLVSDVVLYDWHG
4%$'
3DVVLYDWLRQRXWSXWVHW
3$66B287
$&.B1(& $FNQRZOHGJPHQWUHTXHVW
&KDQQHO &KDQQHO
$&.B5(4
8VHUDFNQRZOHGJPHQWFKDQQHO 8VHUDFNQRZOHGJPHQWFKDQQHO
$&.B5(,
',$*ELWVHW
',$*ELW
See also
Programming startup protection (Page 76)
after communication errors (Page 92)
Implementing User Acknowledgment in the Safety Program of the F-CPU of a DP Master or
IO Controller (Page 99)
Implementing user acknowledgment in the safety program of the F-CPU of a I-slave or I-
device (Page 102)
!
)B30B(B)B'&9B$
3$66B287 ,1
)B30BBB',B'&9
3$66B21
)B30BB)B'2B'&9B$
3$66B21
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).
),2$ $FWLYDWHSDVVLYDWLRQ
3$66B21
)DLOVDIHYDOXHVDUHRXWSXW
$
4%$' (
4%$'B,B[[
4%$'B2B[[
3DVVLYDWLRQRXWSXWVHW
3$66B287
$FWLYDWHSDVVLYDWLRQ
),2%
3$66B21
)DLOVDIHYDOXHVDUHRXWSXW
4%$' $
4%$'B,B[[ (
4%$'B2B[[
3$66B287
( $
),2$
)DLOVDIHYDOXHV
3$( 3URFHVVYDOXHV 3URFHVVYDOXHV
)DLOVDIHYDOXHV
WRRXWSXWV 3URFHVVYDOXHV 3URFHVVYDOXHV
( $
),2%
)DLOVDIHYDOXHV
3URFHVVYDOXHV 3URFHVVYDOXHV
3$(
)DLOVDIHYDOXHV
WRRXWSXWV 3URFHVVYDOXHV 3URFHVVYDOXHV
( IRU),2ZLWKLQSXWV
$ IRU),2ZLWKRXWSXWVDQG),2ZLWKLQSXWVDQGRXSXWV
VLJQDOVHTXHQFHGHSHQGLQJRQWKH),2XVHG
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.
Consequently, it is recommended that you also provide for an acknowledgment by means of
an operator control and monitoring system, in order to acknowledge reintegration of an F-I/O
to which an acknowledgment key is connected.
Procedure for programming user acknowledgment by means of an operator control and monitoring
system
1. Select the "ACK_OP" instruction in the "Instructions" task card and place it in your safety
program. The acknowledgment signal is available at the OUT output of ACK_OP for
purposes of evaluating the user acknowledgments.
2. On your operator control and monitoring system, set up a field for manual entry of an
"acknowledgment value" of "6" (first step in acknowledgment) and an "acknowledgment
value" of "9" (second step in acknowledgment) in the instance DB of ACK_OP (input IN).
or
Assign function key 1 to transfer an "acknowledgment value" of "6" (first step in
acknowledgment) and function key 2 to transfer an "acknowledgment value" of "9"
(second step in acknowledgment) in the instance DB of ACK_OP (input IN).
3. Optional: on your operator control and monitoring system, evaluate output Q in the
instance DB of F_ACK_OP to indicate the time frame within which the second step in
acknowledgment must occur or to indicate that the first 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 deactivate safety mode, then
you must transfer an operand (memory word or DBW of a DB of the standard user program)
at input 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. The
memory word or DBW of a DB must not be written by the program.
Note
If you interconnect input IN with a memory word or DBW of a DB, this memory word or DBW
of a DB may be used only in an F-runtime group at the ACK_OP instruction and not in
another F-runtime group.
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 one program and using one
function key to trigger them!
Having two separate acknowledgement steps prevents erroneous triggering of an
acknowledgement by your non-fail-safe operator control and monitoring system. (S013)
WARNING
If your operator control and monitoring system can access multiple F-CPUs that use the
ACK_OP instruction for fail-safe acknowledgment, or if you have networked operator
control and monitoring systems and F-CPUs (with ACK_OP), you must be sure that the
correct F-CPU is in fact being addressed before executing the two acknowledgment steps:
In each F-CPU, store a network-wide unique name for the F-CPU in a DB of your
standard user program.
In your operator control and monitoring 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 operator control and monitoring 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)
WARNING
2. Optional: Evaluate the QBAD or QBAD_I_xx and QBAD_O_xx or DIAG tags in the
respective F-I/O DB to trigger an indicator light, if applicable, in the event of an error,
and/or generate error messages on your operator control and monitoring system in your
standard user program by evaluating QBAD or QBAD_I_xx and QBAD_O_xx or DIAG;
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 operator control and monitoring 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).
352),%86'3
)RUVDIHW\UHODWHGPDVWHU,
VODYHFRPPXQLFDWLRQIRU
DFNQRZOHGJHPHQWVLJQDO
)',
)',
(70
&RQWURODQGPRQLWRULQJV\VWHP
1. User acknowledgement by means of an operator control and monitoring system that you can use to
access the F-CPU of the I-slave/I-Device
For implementation of a user acknowledgment by means of an operator control and
monitoring system that you can use to access the F-CPU of the I-slave/I-Device, the
ACK_OP: Fail-safe acknowledgment (STEP 7 Safety Advanced V11) (Page 351) instruction
is required.
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 99)" under "Programming
Procedure ...".
From your operator control and monitoring system, you can then directly access the instance
DB of ACK_OP in the I-slave/I-Device.
2. User acknowledgment by means of an acknowledgment key at an F-I/O with inputs that is 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 operator control and monitoring 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 acknowledgment key at an F-I/O with inputs that is 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 also perform a user acknowledgment in the safety program of the
F-CPU of an I-slave/I-Device, 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 by means of safety-related master-I-slave/IO Controller-I-Device
communication.
Programming procedure
1. Place the SENDDP (Page 356) instruction in the safety program in the F-CPU of the DP
master/IO Controller.
2. Place the RCVDP (Page 356) 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).
5. Supply the corresponding input SUBBO_xx of RCVDP with the fail-safe value "VKE0" so
that an unintentional user acknowledgment is not triggered before communication is
established the first time after startup of the sending and receiving F-systems, or in the
event of a safety-related communication error. "VKE0" is available in the F-shared-DB. At
input SUBBO_xx, enter "F_GLOBDB".VKE0 fully qualified.
Note
If a communication error, an F-I/O fault, 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 operator control and monitoring 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, and 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 operator control and monitoring 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).
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, through
symbolic (fully qualified) accesses to the following:
● Instance DBs of the F-FBs
● F-DBs (for example, "Name F_DB".Signal_1)
● Process image input and process image output of F-I/O (for example,
"Emergency_Stop_Button_1" (I 5.0) )
Note
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 out the standard operating system update times, refer to the help on
STEP 7 Professional 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.
In addition, you can write safety program data directly to the standard user program (see
also table of supported operand areas in: Restrictions in the programming languages
FBD/LAD (Page 59)).
Bit memory
In order to write safety program data directly to the standard user program, you can also
write to bit memory in the safety program. However, written bit memory must not be read in
the safety program itself.
Data block
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 data element must not be read in the safety program
itself.
8.1.1 F-Shared DB
Function
The F-shared data block 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 of the safety program in the
standard user program.
WARNING
Because these data 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, data 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 the checks, all signals from the standard user program that are evaluated in the
safety program are included when the safety program is printed out.
Bit memory
In order to process data 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 data of the standard user program in the safety program, you can read
data blocks of the standard user program in the safety program. However, a read data
element must not be written in the safety program itself.
Reading data from the standard user program that can change during runtime of an F-runtime group
When you want to read data from the standard user program (bit memory, data of a standard
DB, or PII of standard I/O) in the safety program, and these data 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 (e.g., because your standard user program is
processed by a higher-priority cyclic interrupt), you must use bit memory or data of a
standard DB for this purpose. You must write the bit memory or data of a standard DB with
the data from the standard user program immediately before calling the F-runtime group.
You are then permitted to access only this bit memory or data 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 the information above is not observed. One of the following
diagnostic events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety Program: internal CPU fault; internal error information: 404"
Introduction
Here you receive an overview of the safety-related communication options in SIMATIC
Safety F-systems.
'3'3FRXSOHU
'3PDVWHU '3PDVWHU
$
% % %
352),%86 352),%86
6XEQHW 6XEQHW
&
,VODYH ,VODYH ,VODYH
'
'3VODYHZLWK)PRGXOHV
$6DIHW\UHODWHGPDVWHUPDVWHUFRPPXQLFDWLRQ &6DIHW\UHODWHG,VODYH,VODYHFRPPXQLFDWLRQ
%6DIHW\UHODWHGPDVWHU,VODYHFRPPXQLFDWLRQ '6DIHW\UHODWHG,VODYHVODYHFRPPXQLFDWLRQ
3131FRXSOHU
% % % '
352),1(7,2 352),1(7,2 352),%86
6XEQHW
$6DIHW\UHODWHG,2FRQWUROOHU,2FRQWUROOHUFRPPXQLFDWLRQ &6DIHW\UHODWHG,2FRQWUROOHU,VODYHFRPPXQLFDWLRQ
%6DIHW\UHODWHG,2&RQWUROOHU,'HYLFHFRPPXQLFDWLRQ '6DIHW\UHODWHG,VODYH,VODYHFRPPXQLFDWLRQ
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.
In the case of a CPU 416F-2 DP without an integrated PROFINET interface, you use a 443-1
Advanced-IT.
Note
Disable the "Data validity display DIA" parameter in the properties for the PN/PN coupler in
the hardware and network editor (same as default setting). Otherwise, safety-related IO
Controller-IO Controller communication is not possible.
,2&RQWUROOHU ,2&RQWUROOHU
+DUGZDUHDQGQHWZRUN +DUGZDUHDQGQHWZRUN
)&38 HGLWRU
)&38
HGLWRU
6DIHW\SURJUDP 6DIHW\SURJUDP
4DGGU ,DGGU
/HQJWKE\WHV /HQJWKE\WHV
6(1''3/$''5 5&9'3/$''5
,DGGU 4DGGU
/HQJWKE\WHV /HQJWKE\WHV
,DGGU 4DGGU
/HQJWKE\WHV /HQJWKE\WHV
5&9'3/$''5 6(1''3/$''5
4DGGU ,DGGU
/HQJWKE\WHV /HQJWKE\WHV
; ;
3131FRXSOHU
5. For bidirectional communication connections, i.e., each F-CPU is to send and receive
data, select the following modules from "IN/OUT" in the "Hardware catalog" task card
(with filter activated), and insert them into the "Device overview" tab in the device view of
PN/PN Coupler X1:
– One "IN/OUT 6 bytes/12 bytes" module, and
– One "IN/OUT 12 bytes/6 bytes" module
6. In the properties of the modules, assign the addresses outside the process image as
follows:
For "IN/OUT 6 bytes/12 bytes" module, e.g.:
– Output addresses: Start address 518
– Input addresses: Start address 518
For "IN/OUT 12 bytes/6 bytes" module, e.g.:
– Output addresses: Start address 530
– Input addresses: Start address 530
Note
Make sure that the values you assign for the start addresses of the output and input data
address areas are identical.
7. Next, define the modules and addresses for PN/PN Coupler X2. To do so, follow the
procedure just outlined. Use the same module types as those for X1. You must adapt the
addresses correspondingly. (See figure at the beginning of "Configuring address areas").
,2FRQWUROOHU ,2FRQWUROOHU
)&38 )&38
6DIHW\SURJUDP 6DIHW\SURJUDP
6(1''3 5&9'3
5&9'3 6(1''3
VDIHW\UHODWHG
3131FRXSOHU 352),1(7,2
Safety-related communication between the F-CPUs of the IO Controllers makes use of the
SENDDP and RCVDP instructions for sending and receiving, respectively. They can be used
to transfer a fixed amount of fail-safe data of data types BOOL and INT in a fail-safe manner.
You will 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 before calling the SENDDP instruction at the end of
the relevant F-runtime group execution.
A detailed description of the SENDDP and RCVDP instructions is found in SENDDP and
RCVDP: Send and receive data via PROFIBUS DP/PROFINET IO (STEP 7 Safety
Advanced V11) (Page 510).
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 510) 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 510) for receiving at the start of the main safety block.
3. Assign the start addresses of the output and input data address 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.
4. Assign the value for the respective address relationship to the DP_DP_ID inputs. This
establishes the communication relationship between the SENDDP instruction in a F-CPU
and the RCVDP instruction in the other F-CPU: The associated instructions receive the
same value for DP_DP_ID.
,2FRQWUROOHU ,2FRQWUROOHU
)&38 )&38
6DIHW\SURJUDP 6DIHW\SURJUDP
6(1''3'3B'3B,' 5&9'3'3B'3B,'
3131FRXSOHU
5&9'3'3B'3B,' 6(1''3'3B'3B,'
6(1''3'3B'3B,' 5&9'3'3B'3B,'
5&9'3'3B'3B,'
3131FRXSOHU
,2FRQWUROOHU
)&38
3131FRXSOHU
6DIHW\SURJUDP
5&9'3'3B'3B,'
6(1''3'3B'3B,'
6(1''3'3B'3B,'
WARNING
The value for each address relationship (input parameter DP_DP_ID; data type: INT) is
user-defined; however, it must be unique from all other safety-related communication
connections in the network. The uniqueness must be checked in the print-out of the
safety program during acceptance testing of the safety program. Additional information
can be found in Correctness of the communication configuration (Page 208).
You must supply inputs DP_DP_ID and LADDR with constant values when calling the
instruction. Direct read or write access to the associated instance DB is not permitted in
the safety program! (S016)
5. Supply the SD_BO_xx inputs of SENDDP with the send signals. To cut down on
intermediate signals when transferring 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 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).
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 data type BOOL, enter the "F_GLOBDB".VKE1 tag (fully
qualified) in 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 in the main safety block and at most
there can be one other RCVDP instruction. You must therefore assign appropriate
initial/actual 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 then be ensured (from a fail-safe standpoint) that a signal level to be
transferred will be captured on the sender side 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 523).
9. Optional: evaluate the ACK_REQ output of the RCVDP instruction, for example, in the
standard user program or on the operator control and monitoring 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.
12.Optional: Evaluate the ERROR output of the RCVDP or SENDDP instruction, for example,
in the standard user program or on the operator control and monitoring 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 deactivated safety
mode (Page 190).
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.
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.
'3PDVWHU '3PDVWHU
6DIHW\SURJUDP 6DIHW\SURJUDP
4DGGU ,DGGU
/HQJWKE\WHV /HQJWKE\WHV
6(1''3/$''5 5&9'3/$''5
,DGGU 4DGGU
/HQJWKE\WHV /HQJWKE\WHV
,DGGU 4DGGU
/HQJWKE\WHV /HQJWKE\WHV
5&9'3/$''5 6(1''3/$''5
4DGGU ,DGGU
/HQJWKE\WHV /HQJWKE\WHV
'3'3FRXSOHU
7. In the properties of the modules, assign the addresses outside the process image as
follows:
For "6 bytes I/12 Bytes Q consistent" module, e.g.:
– Output addresses: Start address 516
– Input addresses: Start address 516
For "12 bytes I/6 Bytes Q consistent" module, e.g.:
– Output addresses: Start address 528
– Input addresses: Start address 528
8. Next, define the addresses for the modules of F-CPU 2 with DP/DP coupler "Slave_2", as
just described. Note that you have to adjust the addresses accordingly (see figure at the
beginning of "Configuring address areas").
'3PDVWHU '3PDVWHU
)&38 )&38
6DIHW\SURJUDP 6DIHW\SURJUDP
6(1''3 5&9'3
5&9'3 6(1''3
VDIHW\UHODWHG
'3'3FRXSOHU 352),%86'3
Safety-related communication between the F-CPUs of the DP masters makes use of the
SENDDP and RCVDP instructions for sending and receiving, respectively. They can be used
to transfer a fixed amount of fail-safe data of data types BOOL and INT in a fail-safe manner.
You will 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 before calling the SENDDP instruction at the end of
the relevant F-runtime group execution.
A detailed description of the SENDDP and RCVDP instructions is found in SENDDP and
RCVDP: Send and receive data via PROFIBUS DP/PROFINET IO (STEP 7 Safety
Advanced V11) (Page 510).
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 510) for sending at the end of the main safety block.
2. In the safety program from which data are to be received, call the RCVDP instruction
(Page 510) for receiving at the start of the main safety block.
3. Assign the start addresses of the address 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.
4. Assign the value for the respective address relationship to the DP_DP_ID inputs. This
establishes the communication relationship between the SENDDP instruction in a F-CPU
and the RCVDP instruction in the other F-CPU: The associated instructions receive the
same value for DP_DP_ID.
'3PDVWHU '3PDVWHU
)&38 )&38
6DIHW\SURJUDP 6DIHW\SURJUDP
6(1''3'3B'3B,' 5&9'3'3B'3B,'
'3'3FRXSOHU
5&9'3'3B'3B,' 6(1''3'3B'3B,'
6(1''3'3B'3B,' 5&9'3'3B'3B,'
5&9'3'3B'3B,'
'3'3FRXSOHU
'3PDVWHU
)&38
'3'3FRXSOHU
6DIHW\SURJUDP
5&9'3'3B'3B,'
6(1''3'3B'3B,'
6(1''3'3B'3B,'
WARNING
The value for each address relationship (input parameter DP_DP_ID; data type: INT) is
user-defined; however, it must be unique from all other safety-related communication
connections in the network. The uniqueness must be checked in the print-out of the
safety program during acceptance testing of the safety program. Additional information
can be found in Correctness of the communication configuration (Page 208).
You must supply inputs DP_DP_ID and LADDR with constant values when calling the
instruction. Direct read or write access to the associated instance DB is not permitted in
the safety program! (S016)
5. Supply the SD_BO_xx inputs of SENDDP with the send signals. To cut down on
intermediate signals when transferring 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 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 (for
example, "Name RCVDP1".RD_BO_02).
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 data type BOOL, enter the "F_GLOBDB".VKE1 tag (fully qualified) in
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 in the main safety block and at most
there can be one other RCVDP instruction. You must therefore assign appropriate
initial/actual 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 then be ensured (from a fail-safe standpoint) that a signal level to be
transferred will be captured on the sender side 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 523).
9. Optional: evaluate the ACK_REQ output of the RCVDP instruction, for example, in the
standard user program or on the operator control and monitoring 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.
12.Optional: evaluate the ERROR output of the RCVDP or SENDDP instruction, for example,
in the standard user program or on the operator control and monitoring 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 deactivated safety
mode (Page 190).
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.
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 over IO
Controller-I-Device connections (F-CD) in PROFINET IO, same as in standard systems.
You do not need any additional hardware for IO Controller-I-Device communication.
,2&RQWUROOHU ,'HYLFH
)&38 +DUGZDUHDQG )&38
QHWZRUNHGLWRU
,'HYLFH
4
5&9'3/$''5 6(1''3/$''5
,2&RQWUROOHU
,
You assign the start addresses of the transfer areas to the LADDR parameter of the
corresponding SENDDP and RCVDP instructions in the safety programs.
5. In the transfer area you just created, click the arrow in order to change the transfer
direction to receiving from IO Controller (→).
,2FRQWUROOHU ,GHYLFH
)&38 )&38
6DIHW\SURJUDP 6DIHW\SURJUDP
6(1''3 5&9'3
5&9'3 6(1''3
VDIHW\UHODWHG
352),1(7,2
Programming procedure
The procedure for programming safety-related IO-Controller-I-Device communication is the
same as for programming safety-related IO-Controller-IO-Controller communication (see
Program safety-related IO controller-IO controller communication (Page 118)).
The assignment of the start addresses of the transfer areas for the LADDR parameter of the
SENDDP/RCVDP instructions can be obtained from the following table.
The figure below contains an example of how to specify the address relationships for the
inputs of the SENDDP and RCVDP instructions for four safety-related IO-Controller-I-Device
communication relationships.
,2FRQWUROOHU ,GHYLFH
)&38 )&38
6DIHW\SURJUDP 6DIHW\SURJUDP
6(1''3'3B'3B,' 5&9'3'3B'3B,'
5&9'3'3B'3B,' 6(1''3'3B'3B,'
6(1''3'3B'3B,'
,GHYLFH
5&9'3'3B'3B,'
)&38
6DIHW\SURJUDP
5&9'3'3B'3B,'
6(1''3'3B'3B,'
WARNING
The value for each address relationship (input parameter DP_DP_ID; data type: INT) is
user-defined; however, it must be unique from all other safety-related communication
connections in the network. The uniqueness must be checked in the print-out of the safety
program during acceptance testing of the safety program. Additional information can be
found in Correctness of the communication configuration (Page 208).
You must supply inputs DP_DP_ID and LADDR with constant values when calling the
instruction. Direct read or write access to the associated instance DB is not permitted in the
safety program! (S016)
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal level to be transferred will
be captured on the sender side 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 523).
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 any additional hardware for the master-I-slave communication.
'3PDVWHU ,VODYH
)&38 +DUGZDUHDQG )&38
QHWZRUNHGLWRU
6DIHW\SURJUDP 6DIHW\SURJUDP
0DVWHUDGGUHVV4
6(1''3/$''5 5&9'3/$''5
6ODYHDGGUHVV,
6ODYHDGGUHVV4
5&9'3/$''5 6(1''3/$''5
0DVWHUDGGUHVV,
You assign the start addresses of the transfer areas to the LADDR parameter of the
corresponding SENDDP and RCVDP instructions in the safety programs.
5. In the transfer area you just created, click the arrow in order to change the transfer
direction to receiving from DP master (→).
'3PDVWHU,VODYH ,VODYH
)&38 )&38
6DIHW\SURJUDP 6DIHW\SURJUDP
6(1''3 5&9'3
5&9'3 6(1''3
VDIHW\UHODWHG
352),%86'3
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 for programming safety-related master-master
communication (see Program safety-related master-master communication (Page 126)).
The assignment of the start addresses of the transfer areas for the LADDR parameter of the
SENDDP/RCVDP instructions can be obtained from the following table.
The figure below contains an example of how to specify the address relationships at the
inputs of SENDDP and RCVDP instructions for two safety-related master-I-slave and one I-
slave-I-slave communications.
'3PDVWHU ,VODYH
)&38 )&38
6DIHW\SURJUDP 6DIHW\SURJUDP
6(1''3'3B'3B,' 5&9'3'3B'3B,'
5&9'3'3B'3B,' 6(1''3'3B'3B,'
6(1''3'3B'3B,' 5&9'3'3B'3B,'
5&9'3'3B'3B,' 6(1''3'3B'3B,'
,VODYH
)&38
6DIHW\SURJUDP
5&9'3'3B'3B,'
6(1''3'3B'3B,'
5&9'3'3B'3B,'
0DVWHU,VODYHFRPPXQLFDWLRQ
,VODYH,VODYHFRPPXQLFDWLRQ 6(1''3'3B'3B,'
WARNING
The value for each address relationship (input parameter DP_DP_ID; data type: INT) is
user-defined; however, it must be unique from all other safety-related communication
connections in the network. The uniqueness must be checked in the print-out of the safety
program during acceptance testing of the safety program. Additional information can be
found in Correctness of the communication configuration (Page 208).
You must supply inputs DP_DP_ID and LADDR with constant values when calling the
instruction. Direct read or write access to the associated instance DB is not permitted in the
safety program! (S016)
WARNING
It can only then be ensured (from a fail-safe standpoint) that a signal level to be transferred
will be captured on the sender side 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 523).
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:
● 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
,VODYH ,VODYH
)&38 +DUGZDUHDQG +DUGZDUHDQG )&38
QHWZRUNHGLWRU QHWZRUNHGLWRU
6DIHW\SURJUDP 6DIHW\SURJUDP
2XWSXWDGGUHVV ,QSXWDGGUHVV
4 ,
6(1''3/$''5 5&9'3/$''5
,QSXWDGGUHVV 2XWSXWDGGUHVV
, 4
5&9'3/$''5 6(1''3/$''5
You assign the start addresses of the transfer areas to the LADDR parameter of the
corresponding SENDDP and RCVDP instructions in the safety programs.
6. 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 address areas in the I-slaves assigned outside of the process image
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.
In the "I-slave communication table" of both I-slaves, two transfer areas (type F-MS) for
the master CPU are created (disabled in display).
This completes the configuration for sending to F-CPU 2.
7. 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) (←).
8. 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 "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.
Reference
The description of the communication via SENDDP and RCVDP for safety-related I-slave-I-
slave communication can be found in Safety-related master-I-slave or I-slave-I-slave
communication via SENDDP and RCVDP (Page 139).
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 140).
The assignment of the start addresses of the transfer areas for the LADDR parameter of the
SENDDP/RCVDP instructions can be obtained from the following table.
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.
The process input image 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 153)).
Restrictions
Note
Safety-related I-slave-slave communication is possible for F-I/O in a DP slave that supports
safety-related I-slave-slave communication, e.g., for all ET 200S F-modules with IM 151-x
HIGH FEATURE and all S7-300 fail-safe signal modules with IM 153-2, as of order
no. 6ES7153-2BA01-0XB0, firmware > 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, after startup of the F-system, the F-I/O
are not reintegrated automatically. Rather, they are 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 errors (Page 92) and After startup of F-system (Page 90)).
,VODYH 6ODYH
+DUGZDUHDQGQHWZRUN
7HUPLQDWLRQPRGXOH
,0 30 )', )'2 30 0RWRUVWDUWHU
)&38 HGLWRU +,*+)($785( '
2XWSXW
DGGUHVV
3,4 4
Procedure for configuring using the example of an ET 200S with fail-safe modules as 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 in the project.
2. Insert a suitable DP slave, e.g., IM 151-1 HF, order no. 6ES7151-1BA0... from the
"Hardware catalog" task card into the network view of the hardware and network editor.
3. Assign a 4/8 F-DI module and a 4 F-DO-module in the device view of the ET 200S.
4. Activate the "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.
11.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/8 F-DO module.
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.
WARNING
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 523)).
Note that the Excel file for calculating response times does not support all of the conceivable
configurations.
Reference
In addition, the information on safety-related master-I-slave communication in Safety-related
master-I-slave communication (Page 136) also applies analogously.
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 Advanced-IT
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" parameter of the SENDS7 and RCVS7
instructions in the safety programs.
5&96 6(1'6
)&RPP'% )&RPP'%
ಯ5HFHLYHGDWDರ ಯ6HQGGDWDರ
,QGXVWULDO(WKHUQHW
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 will 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 V11) (Page 517).
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.
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.
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. One of the
following diagnostic events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
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 side.
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 of the receiver side, and change the name, if necessary.
Programming procedure
You program safety-related communication via S7 connections as follows:
1. Supply the tags in the F-communication DB of the sender side 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 of the receiver side (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 from which data are to be received, call the RCVS7 instruction 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 .
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.
&38)31'3 &38)'3
6DIHW\SURJUDP 6DIHW\SURJUDP
WARNING
The value for each address relationship (input parameter R_ID; data type: DWORD) is
user-defined; however, it must be an odd number and be unique from all other safety-
related communication connections in the network. 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)
9. Assign the TIMEOUT inputs of the SENDS7 and RCVS7 instructions with the required
monitoring time.
WARNING
It can only then be ensured (from a fail-safe standpoint) that a signal level to be
transferred will be captured on the sender side 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 523).
10.To reduce the bus load, you can temporarily shut down communication between the F-
CPUs at the EN_SEND input of the SENDS7 instruction. To do so, specify the
"F_GLOBDB".VKE0 tag (fully qualified) in the EN_SEND input (initial value = "TRUE"). 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 operator control and monitoring 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 operator control and monitoring 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 deactivated safety mode (Page 190).
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.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.
9.10.2 Communication with S7 Distributed Safety via PN/PN coupler (IO Controller-IO
Controller communication)
Communication functions between SENDDP/RCVDP instructions on the STEP 7 Safety V11
side and F_SENDDP/F_RCVDP F-application blocks on the S7 Distributed Safety side:
,2&RQWUROOHU ,2&RQWUROOHU
)&38 )&38
67(3bb6DIHW\b$GYDQFHGb9 6'LVWULEXWHG6DIHW\
VDIHW\SURJUDP VDIHW\SURJUDP
6(1''3 )B5&9'3
5&9'3 )B6(1''3
6DIHW\UHODWHG
3131FRXSOHU 352),1(7,2
'3PDVWHU '3PDVWHU
)&38 )&38
67(3bb6DIHW\b$GYDQFHGb9 6'LVWULEXWHG6DIHW\
VDIHW\SURJUDP VDIHW\SURJUDP
6(1''3 )B5&9'3
5&9'3 )B6(1''3
6DIHW\UHODWHG
'3'3FRXSOHU 352),%86'3
5&96 )B6(1'6
)&RPP'% )&RPP'%
5HFHLYHGDWD 6HQGGDWD
6(1'6 )B5&96
)&RPP'% )&RPP'%
6HQGGDWD 5HFHLYHGDWD
,QGXVWULDO(WKHUQHW
Program example:
1HWZRUN&RPPXQLFDWLRQZLWK67(3bb6DIHW\b$GYDQFHGb95B,'!&5&B,03
029(
)B5&96B
(1 287 '%&5&B,03
': ,1 (12
1HWZRUN&RPPXQLFDWLRQZLWK67(3bb6DIHW\b$GYDQFHGb95B,'!&5&B,03
029(
)B6(1'6B
(1 287 '%&5&B,03
': ,1 (12
6DIHW\SURJUDP 6DIHW\SURJUDP
67(36DIHW\$GYDQFHG9 6)6\VWHPV
5&96 )B6'6B%2
)&RPP'%
5HFHLYHGDWD
6(1'6 )B5'6B%2
)&RPP'%
6HQGGDWD
,QGXVWULDO(WKHUQHW
Program example:
1HWZRUN&RPPXQLFDWLRQZLWK67(3bb6DIHW\b$GYDQFHGb95B,'!&5&B,03
029(
)B5'6B%2B
(1 287 '%&5&B,03
': ,1 (12
1HWZRUN&RPPXQLFDWLRQZLWK67(3bb6DIHW\b$GYDQFHGb95B,'!&5&B,03
029(
)B6'6B%2B
(1 287 '%&5&B,03
': ,1 (12
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.
Introduction
To compile a safety program, follow the same basic procedure as for compiling a standard
user program. There are various points of entry to accomplish this in STEP 7 Professional.
The basics for compiling user programs can be found in the help on STEP 7 Professional.
We will show you the options for compiling the safety program later.
Select Safety Administration Menu "Edit > Compile" or Entire standard program and Consistent
Editor "Compile" button safety program
Select "Program blocks" folder in Menu "Edit > Compile" or Changes in the standard and Consistent
the project tree "Compile" button safety programs
"Compile" context menu:
"Software" Changes in the standard and Consistent
safety programs
"Software (rebuild all Entire standard program and Consistent
blocks)" safety program
Select user-created folder in the Menu "Edit > Compile" or All standard and F-blocks Inconsistent
project tree "Compile" button contained in the folder
User-created folder containing Menu "Edit > Compile" or All standard blocks contained in Consistent
all F-blocks "Compile" button the folder and complete safety
program
See also
Safety Administration Editor (Page 39)
Introduction
Once you have successfully compiled your safety program, you can download it to the F-
CPU. Follow the same basic procedure for downloading a safety program as for
downloading a standard user program using various points of entry in STEP 7 Professional.
● In the "Load preview" dialog, enter data (e.g., password for 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 Professional.
WARNING
If multiple F-CPUs are accessible over a network (e.g., Ind. Ethernet) by one programming
device or PC, you must take the following actions to ensure that the safety program is
downloaded to the correct F-CPU:
Use passwords specific to each F-CPU, e.g., a uniform password for the F-CPUs with the
respective Ethernet address as an extension (max. 8 characters) "PW_8".
Note the following:
A point-to-point connection must be used when assigning a password to an F-CPU for
the first time (analogous to assigning an MPI address to an F-CPU for the first time).
Before downloading a safety program to an F-CPU, you must first revoke existing
access permission for any other F-CPU.
After activation of the access protection and before the transition to productive mode,
you must download the safety program again to the F-CPU. (S021)
Note
If STEP 7 Safety V11 detects an inconsistent safety program during startup of the F-CPU,
the F-CPU cannot be started up, provided the F-CPU supports this detection function (see
Product Information for the particular F-CPU). The following diagnostic event is then entered
in the diagnostic buffer of the F-CPU:
"Inconsistent safety program"
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. One of the following
diagnostic events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You can perform the downloading of a consistent safety program only in STOP mode.
If you are downloading F-blocks only, the blocks in which the main safety blocks are called
(e.g., cyclic interrupt OB 35) are not downloaded. To do so, select the "Select" option under
"Standard software" in the preview dialog, and select the necessary blocks.
When downloading the safety program, ensure that the "Consistent download" action is set
for the "Safety program" selection in the "Load preview" dialog.
Verify that the "All CRCs are identical" message appears in the "Load results" dialog. On the
basis of the CRCs, the system checks after the download operation to determine whether all
F-blocks were correctly transferred to the F-CPU. If not, repeat the download operation.
Inconsistent downloading is only possible in deactivated safety mode.
Note
If STEP 7 Safety V11 detects an inconsistent safety program during startup of the F-CPU,
the F-CPU cannot be started up, provided the F-CPU supports this detection function (see
Product Information for the particular F-CPU). The following diagnostic event is then entered
in the diagnostic buffer of the F-CPU:
"Inconsistent safety program"
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. One of the following
diagnostic events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
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.
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 must not be
downloaded again to the F-CPU.
Downloading to an S7-PLCSIM
You can download the safety program with S7-PLCSIM (hardware simulation) similar to a
real F-CPU. For this purpose, use the menu command "Online > Simulation > Start" to start
S7-PLCSIM, same as in the standard system.
Estimation
You can estimate the work memory requirement for the safety program as follows:
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 kbytes),
RCVDP(0.3 kbytes), SENDS7 (0.6 kbytes), and RCVS7 (1.0 kbyte)
+ 0.7 kbytes per F-FC
+ 0.7 kbytes per F-I/O (for F-I/O DBs, etc.)
+ 4.5 kbytes
F-CPUs with memory card inserted (Flash Card or SIMATIC Micro Memory Card)
The following warnings apply when the safety program is transferred from a programming
device or PC to:
● F-CPUs with flash card inserted (e.g., CPU 416F-2)
● F-CPUs with SIMATIC Micro Memory Card
(e.g., CPU 317F-2 DP, CPU 315F-2 PN/DP or IM 151-7 F-CPU)
WARNING
If the function test of the safety program is not carried out in the target F-CPU, you must
comply with the following procedure when transferring the safety program to the F-CPU
with a PG/PC to ensure that the F-CPU does not contain an "old" safety program:
Load the safety program to the F-CPU.
Perform a program identification (that is, check to determine whether the collective F-
signatures match online and offline).
Perform a memory reset of the F-CPU using the mode selector 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 F-
CPUs 3xxF, IM-CPUs ET 200S und ET 200pro or Flash-Card for F-CPUs F-CPUs
4xxF). (S022)
WARNING
If multiple F-CPUs are accessible over a network (e.g., Ind. Ethernet) by one programming
device or PC, you must take the following actions to ensure that the safety program is
downloaded to the correct F-CPU:
Use passwords specific to each F-CPU, e.g., a uniform password for the F-CPUs with the
respective Ethernet address as an extension (max. 8 characters) "PW_8".
Note the following:
A point-to-point connection must be used when assigning a password to an F-CPU for
the first time (analogous to assigning an MPI address to an F-CPU for the first time).
Before downloading a safety program to an F-CPU, you must first revoke existing
access permission for any other F-CPU.
After activation of the access protection and before the transition to productive mode,
you must download the safety program again to the F-CPU. (S021)
WARNING
If the function test of the safety program is not carried out in the target F-CPU, you must
comply with the following procedure when transferring the safety program to the F-CPU
with a PG/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 selector or via the programming
device/PC.
Download the configuration and the safety program to the F-CPU.
Perform a program identification (that is, check to determine whether the collective F-
signatures match online and offline). (S023)
WARNING
If multiple F-CPUs are accessible over a network (e.g., Ind. Ethernet) by one programming
device or PC, you must take the following actions to ensure that the safety program is
downloaded to the correct F-CPU:
Use passwords specific to each F-CPU, e.g., a uniform password for the F-CPUs with the
respective Ethernet address as an extension (max. 8 characters) "PW_8".
Note the following:
A point-to-point connection must be used when assigning a password to an F-CPU for
the first time (analogous to assigning an MPI address to an F-CPU for the first time).
Before downloading a safety program to an F-CPU, you must first revoke existing
access permission for any other F-CPU.
After activation of the access protection and before the transition to productive mode,
you must download the safety program again to the F-CPU. (S021)
WARNING
In order to guarantee that no "old" safety program is in the F-controller, you must comply
with the following procedure when transferring the safety program into the F-controller with
a programming device/PC:
1. Perform a memory reset of 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 configuration to the WinAC RTX F (see Windows Automation Center RTX
WinAC RTX (F) 2010 (http://support.automation.siemens.com/WW/view/en/43715176)
manual).
3. Download the safety program (Page 171) to the WinAC RTX F.
If the function test of the safety program does not take place in the destination F-
controller, you must also follow points 4 and 5:
4. Perform a program identification (that is, check to determine whether the collective F-
signatures match online and offline).
5. Execute the F-system startup (Page 76).
Between the online program identification and the startup of the F-system, the
WinAC RTX F may not be closed (for example, through NETWORK OFF/NETWORK ON or
booting). (S024)
WARNING
Rules for plugging removable media (for example, SIMATIC Micro Memory Card, Flash Card or hard
disk) in the WinAC RTX F
WARNING
You must limit the access for the WinAC RTX F through an access protection to persons,
who are entitled for plugging removable media.
You must guarantee that the correct safety program is on the plugged removable media,
either through online program identification or other measures (for example, unique ID of
the removable medium). (S025)
WARNING
If the function test of the safety program is not carried out in the target F-CPU, you must
comply with the following procedure when transferring the safety program to the F-CPU
with a memory card (SIMATIC Micro Memory Card or Flash Card) to ensure that the F-CPU
does not contain an "old" safety program:
Turn off the power to the F-CPU. For F-CPUs with battery backup (e.g., CPU 416F-2),
remove the battery, if present. (To make sure that the F-CPU is de-energized, wait for
the buffer time of the power supply you are using or, if this is unknown, remove the F-
CPU.)
Remove the Memory Card (SIMATIC Micro Memory Card or Flash Card) with the old
safety program from the F-CPU.
Plug the Memory Card (SIMATIC Micro Memory Card or Flash 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.
You must make sure that the inserted memory card (SIMATIC Micro Memory Card or Flash
Card) contains the correct safety program. You can do so through a program identification
or other measures, such as a unique identifier on the memory card (SIMATIC Micro
Memory Card or Flash Card).
When downloading a safety program to a memory card (SIMATIC Micro Memory Card or
Flash Card), you must adhere to the following procedure:
Download the safety program to the memory card (SIMATIC Micro Memory Card or
flash card).
Perform a program identification - in other words, check whether the collective F-
signatures of all F-blocks with F-attribute in the offline block container and on the
memory card (SIMATIC Micro Memory Card or Flash Card) match.
Affix an appropriate label to the memory card (SIMATIC Micro Memory Card or Flash
Card).
The procedure outlined must be ensured through organizational measures. (S026)
Note
During the offline-online comparison, the comparison statuses may occasionally differ
between the comparison editor and status display in the project tree or 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.
Note
If you interrupt the connection to the F-CPU during the comparison, the comparison result
will be incorrect.
Both offline versions of the object are different The differences are indicated in the "Details" column.
Printing
You can print all important project data of the hardware configuration of the F-I/O and safety
program. As a result, you receive a "safety printout" that serves as a basis for the test for
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 printout
The safety printout provides documentation of the safety program provides support for the
acceptance test of the system.
Monitoring
In general, all read-only test functions (such as tag monitoring) are also available for safety
programs and in safety mode.
Modifying
Modifying safety program data and write accesses to the safety program are possible only
conditionally and in deactivated safety operation 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 deactivate safety mode of the safety program to
download changes to the safety program in RUN mode. Safety mode remains deactivated
until the F-CPU is next switched from STOP to RUN 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:
Deactivation of safety mode is intended for test purposes, commissioning, etc.
Whenever safety mode is deactivated, 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.
The deactivation of safety mode must be displayed.
In addition, the MODE tag in the F-shared-DB ("F_GLOBDB".MODE) is available, which
you can evaluate for reading out the operating mode (1 = deactivated safety mode).
Thus, not only is the deactivated safety mode displayed on the programming device or
PC in the dialog box for deactivating 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
operator control and monitoring system generated by evaluating the "Deactivated Safety
Mode" tag in the F-shared DB (Page 107).
It must be possible to verify that safety mode has been deactivated. A log is required, if
possible by recording messages to the operator control and monitoring system, but if
necessary, through organizational measures. In addition, it is recommended that
deactivation of safety mode be indicated on the operator control and monitoring system.
Safety mode is deactivated across the F-CPU only. You must take the following into
account for safety-related CPU-CPU communication: If the F-CPU with the SENDDP or
SENDS7 instruction is in deactivated safety mode, 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 values instead of the received data in the F-CPU with RCVDP or RCVS7
(Page 510) or SENDMODE by evaluating SENDMODE. (S027)
Note
If 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.
Note
To activate safety mode, the F-CPU must be switched from STOP to RUN mode.
Switching the F-CPU from STOP to RUN mode always activates safety mode, even if the
safety program has been modified or is not consistent. The MODE tag in the F-shared DB is
set to "0". Keep this in mind when you evaluate the MODE tag to read out the operating
mode.
If you have changed your safety program, but have not recompiled and downloaded it, the F-
CPU can revert to STOP mode.
WARNING
When the safety program is in deactivated safety mode, the "MODE" tag in the F-shared
DB is also evaluated in deactivated safety mode.
Even if the F-I/O are passivated in deactivated safety mode as a result of evaluation of the
"MODE" tag, system safety must be ensured in deactivated safety mode through other
organizational measures, such as operation monitoring and manual safety shutdown.
(S028)
Introduction
In deactivated safety mode, certain fault control measures of the safety program are
deactivated to enable online changes to be made to the safety program in RUN mode. In this
way, safety program data can be changed using standard tools of STEP 7 Professional
(watch table, monitoring in program editor).
Note
F-I/O can only be modified in RUN mode of the F-CPU. You must allocate a separate row in
the watch table for each channel to be modified; this means, for example, that digital
channels of data type BOOL cannot be modified on a byte-by-byte or word-by-word basis.
You can modify a maximum of 5 inputs/outputs from a watch table. You can use more than
one monitoring table.
You cannot modify configured F-I/O in which no single channel or tag from the associated F-
I/O DB has been used. Therefore, always use at least one tag from the associated F-I/O DB
or at least one channel of the F-I/O to be modified in your safety program.
As a trigger point, you must set "Begin scan cycle" or "End scan cycle", either "permanently"
or "once". However, note that 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.
For inputs (PII), 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.
WARNING
Constant modify requests for F-I/O can continue to remain active in the following cases:
The connection between the programming device or PC and F-CPU is interrupted (e.g.,
due to unplugging of bus cable)
if the watch table no longer responds
To delete constant modify requests in such cases, you must
Switch the relevant F-CPU from STOP to RUN when the connection to the programming
device or PC is interrupted,
or
Perform a memory reset on the relevant F-CPU (S029)
Note
A Modify function controlled by the F-system is only possible with the STEP 7 Safety
Advanced V11 optional package is installed. If tags are modified by means of an operator
control and monitoring system or modification occurs without an installed STEP 7
Safety Advanced V11 optional package, the modification request can cause the F-CPU to go
to STOP mode.
The test functions are selected using the standard tools of STEP 7 Professional (program
editor, watch table). An attempt to modify a safety program in safety mode is rejected with a
corresponding error message, or a dialog box for deactivating safety mode is provided. In
certain circumstances, a modify request can cause the F-CPU to go to STOP mode.
Note
If you use the watch table to test a safety program, this test does not detect all changes
you make in parallel using other editors in the F-CPU.
For example, if the collective F-signature is changed through a revision/modification while
safety mode is deactivated, the change may not be detected and an old collective F-
signature may continue to be displayed.
In such cases, close the watch table and restart it in order to work with updated data.
Note
If you would like to modify tags in S7-PLCSIM, you must deactivate safety mode
(Page 190) beforehand. Otherwise, S7-PLCSIM can go to STOP mode.
You can use the SENDDP, RCVDP, SENDS7, and RCVS7 instructions together with S7-
PLCSIM. Note, however, that the instructions constantly signal "communication errors"
when they are run in the simulation CPU.
Introduction
Changes to the safety program during operation (in RUN mode) can only be made in
deactivated safety mode (Page 190). 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-modules in FBD/LAD (Page 73).
Note
When downloading in deactivated 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 deactivated safety
mode.
WARNING
In safety mode, access by means of the CPU password must not be authorized when
making changes to the standard user program, since changes to the safety program can
also be made. To rule out this possibility, you must configure 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, then 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). (See also Access protection (Page 49)) (S001)
Deleting the entire safety program for F-CPUs with plugged 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. Select the F-CPU in the hardware and network editor, and deactivate the "F-capability
activated" option in the properties of the F-CPU.
3. Compile the hardware configuration.
The offline project no longer contains a safety program.
4. To delete a safety program on a 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.
5. Select the menu command "Project> SIMATIC Card Reader> Show SIMATIC Card
Reader" in the menu bar.
6. Open the "SIMATIC Card Reader" folder. You can now access the memory Card and can
delete the safety program.
You can then download the offline standard user program to the F-CPU.
Deleting the entire safety program for F-CPUs without plugged 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. Select the F-CPU in the hardware and network editor and deactivate the "F-capability
activated" option in the properties of the F-CPU.
3. Compile the hardware configuration.
The offline project no longer contains a safety program.
By performing a memory reset on the F-CPU (in the "Online tools" task card of the F-CPU),
you can delete the safety program.
Introduction
When a system undergoes an acceptance test, all standards relevant to the specific
application must be met. This also applies to systems that are not "subject to acceptance
testing". For the acceptance test, you must consider the documents in the Certification
Report (http://support.automation.siemens.com/WW/view/en/49368678/134200).
As a general rule, the acceptance test of an F-System is performed by an independent
expert.
We recommend the following procedure for the preparation of the acceptance test.
Safety printout
The safety printout is the documentation of the project that provides supports for the
acceptance test of the system.
Verification/function test
Already during the creation, you will test (Page 189) 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 plant.
In order 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 printout,
provided you have selected the "All" property for the printout.
The correct function of the safety program must be guaranteed by complete function tests
before it may be used productively. You should archive the test reports along with the safety
printout and the acceptance documents.
Times, for example, monitoring times (Page 523) and delay times can be verified through
function tests (Page 178) only with very poor efficiency. You should check these times
selectively to determine whether they are dimensioned correctly, for example, on the basis of
the safety printout.
Some of these times are itemized specially in the safety printout, 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 (parameter TIMEOUT). For the approximate
determination of these monitoring times, the Excel file for response time calculation is
available on the Internet
(http://support.automation.siemens.com/WW/view/en/49368678/133100).
Password protection
Verify that a password was assigned for both the safety program and the F-CPU, if other
organizational measures for access protection of the safety program were not taken.
For information about this, refer to section "General information" under "Access protection".
Additional notes
If required, review the "Notes" in section "General information", which provides additional
notes on the safety program that must be observed or addressed.
Introduction
If your safety program status including hardware configuration is ready for acceptance, you
can carry out and document additional tests on the basis of the safety printout. The safety
printout must be complete and belong to the safety program undergoing acceptance testing.
Introduction
The STEP 7 Safety Advanced V11 optional package contains LAD/FBD instructions that
have been created and tested by SIEMENS and certified by TÜV for use in programming
your safety program.
To check whether the instructions used match the TÜV certificate, these instructions are
listed in the safety printout in section "System library elements used in safety program" along
with their signatures and initial value signatures.
The same applies if you use shared libraries with F-blocks of other manufacturers.
Procedure
To check whether or not the utilized instructions match the TÜV certificate, proceed as
follows:
1. 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).
The versions of the instructions and F-blocks indicated in Annex 1 must match the
version numbers in the safety printout. Otherwise, you did not receive the appropriate
version of Annex 1 or a non-certified version of STEP 7 Safety Advanced V11 is present.
2. Compare the signature and initial value signature with that specified in Annex 1 for each
element itemized in the safety printout under "System library elements used in the safety
program".
3. In case of discrepancies, recheck whether you have the correct versions.
If you have the correct versions, but the signature of the instructions are different, you
should reinstall STEP 7 Safety Advanced V11 and compile and download the project
again, as the instructions may be corrupt.
Introduction
The hardware configuration is an essential component of the project to be accepted. With
the configuration of the hardware, you have undertaken settings that may influence the
safety of signals. You can use the safety printout to document these settings in detail, in
order to prove that you fulfill the safety requirements of your application.
The section "Hardware configuration of F-I/O" is available in the safety printout for this. This
section consists of several tables:
● a table with information about the F-CPU and the range of F-destination addresses used
● an overview table with the F-I/O used
● a table for each F-I/O with detailed specifications, for example, the configured parameter
values
Note
Note that will find F-I/O that you address via safety-related I-slave-slave communication in
the safety printout of the I-slave and not in the printout of the assigned DP master.
WARNING
In safety mode, access by means of the CPU password must not be authorized when
making changes to the standard user program, since changes to the safety program can
also be made. To rule out this possibility, you must configure 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, then
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). (See also Access protection (Page 49).)
(S001)
Note
Recommendation for the assignment of address ranges
For each F-CPU that you use in your system, assign a separate address area within the
network in such a way that none of them overlap. As a result, you only have to check for
the absence of overlapping in the respective safety printouts of the F-CPUs. If the areas
of several F-CPUs overlap one another, you must check the respective intersection area
individually for each PROFIsafe destination address for uniqueness.
WARNING
The following applies to PROFIBUS only subnets:
The PROFIsafe destination address and, thus, the switch setting on the address switch
of the F-I/O must be unique network-wide* and station-wide** (system-wide). For S7-
300 F-SMs and ET 200S, ET 200eco, ET 200pro, and ET 200iSP F-modules, you can
assign a maximum of 1022 different PROFIsafe destination addresses.
Exception: The F-I/O in different I-slaves may be assigned the same PROFIsafe
destination address, as they are only addressed within the station, that is, by the F-CPU
in the I-slave.
The following applies to Ethernet subnets and hybrid configurations of PROFIBUS and
Ethernet subnets:
The PROFIsafe destination address and, thus, the address switch setting on the F-I/O
have to be unique only*** within the Ethernet subnet, including all lower-level
PROFIBUS subnets, and station-wide** (system-wide). For S7-300 F-SMs and
ET 200S, ET 200eco, ET 200pro, and ET 200iSP F-modules, you can assign a
maximum of 1022 different PROFIsafe destination addresses.
Exception: The F-I/O in different I-slaves/I-Devices may be assigned the same
PROFIsafe destination address, as they are only addressed within the station, that is, by
the F-CPU in the I-slave/I-Device.
The networked nodes of an Ethernet subnet are characterized by having IP addresses
with the same subnet address, i.e., the IP addresses match in the digits that have the
value "1" in the subnet mask.
Example:
IP address: 140.80.0.2.
Subnet mask: 255.255.0.0 = 11111111.11111111.00000000.00000000
Meaning: Bytes 1 and 2 of the IP address define the subnet; subnet address = 140.80.
(S002)
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 DP
standard slaves/standard I/O devices.
Introduction
Safety-related communication is based on the mechanisms of the standard communication
of STEP 7 Professional. To detect errors in the standard communication configuration,
safety-related communication connections between F-CPU must be protected additionally.
For the acceptance test, you must document the restrictions (uniqueness) resulting from the
protection.
For this purpose, the "Parameters for safety-related CPU-CPU-communication" section is
available in the safety printout. In this section, there are up to two tables (for communication
via PROFIBUS DP or PROFINET IO and for communication via S7 connections).
Introduction
In addition, you must check a few more characteristics that are also relevant for the
acceptance test 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 signals that you are using in the safety program.
See also
Data Transfer from Standard User Program to Safety Program (Page 108)
Introduction
In general, you can adopt the same approach for the acceptance test of changes as the
initial acceptance test (see Overview of System Acceptance Test (Page 201)).
To avoid undergoing a new acceptance test of the entire system in the event of minor
changes, STEP 7 Safety V11 helps you to identify those parts of your safety program that
have changed.
For an acceptance test of changes, it is sufficient to test the following:
● the changed or newly added F-blocks
● the changed or newly added instructions and F-system blocks
● the safety-related parameters of the changed or newly added F-I/O
Then perform a function test of the changes.
Introduction
Pay attention to the following important notes on safety mode of the safety program.
WARNING
If you operate simulation devices or simulation programs that generate safety message
frames, e.g., 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.
If you use the S7-PLCSIM (Page 189) to simulate safety programs, these measures are not
necessary because S7-PLCSIM cannot establish an online connection to a real S7
component.
Note, for example, that a protocol analyzer is not permitted to perform any function that
reproduces recorded message frame sequences with correct time behavior. (S030)
WARNING
Switching from STOP to RUN mode using a programming device or PC interface, mode
selector, or communication function is not locked. For example, only one keystroke is
necessary to switch from STOP to RUN mode on a programming device or PC interface.
For this reason, a STOP that you have set by means of a programming device or PC, mode
selector, or communication function must not be regarded as a safety condition.
Therefore, you must program startup protection (see Programming startup protection
(Page 76)). (S031)
WARNING
A STOP state initiated by the "STP" instruction can be canceled very easily (and
unintentionally) from the programming device or PC. For this reason, a STOP initiated by
the STP instruction is not a safety-related STOP.
Therefore, you must program startup protection (see Programming startup protection
(Page 76)). (S032)
See also
Installation/uninstallation of the STEP 7 Safety Advanced V11 optional package (Page 21)
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 one recommendation.
Tip on RET_DPRD/RET_DPWR
The diagnostic information of the RET_DPRD/RET_DPWR parameters correspond to the
diagnostic information of the RETVAL parameter of the "DPRD_DAT" and "DPWR_DAT"
instructions. You will find the description in the help on STEP 7 Professional for the
"DPRD_DAT" and "DPWR_DAT" instructions.
Note
Preconnection of enable input EN or evaluation of enable output ENO is not possible.
13.2.1 General
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.
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 multi-instance, in which data of the inserted instruction are stored. After its
creation, 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 will 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.
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.
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:
ಯ7DJ,QBಯ
Description
Branches must be closed again at suitable places. When a branch is closed, any necessary
empty elements are added. 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.
3. A dashed line will appear as soon as the cursor is moved.
4. Drag the dashed line to a suitable place on the network. Permissible connections are
indicated by green lines.
5. Release the left mouse button.
13.2.2.1 ---| |---: Normally open contact (STEP 7 Safety Advanced V11)
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:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ
13.2.2.2 ---| / |---: Normally closed contact (STEP 7 Safety Advanced V11)
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:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ
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:
ಯ7DJ,QBಯ ಯ7DJ2XWಯ
127
ಯ7DJ,QBಯ ಯ7DJ,QBಯ
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:
Example
The following example shows how the instruction works:
Description
You can use the "Reset output" instruction to reset the signal state of a specified operand to
"0".
The instruction is only executed if the result of logic operation (RLO) at the input of the coil is
"1". 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
immediately to the output of the coil.
Note
If you want to use a formal parameter of an F-FB/F-FC for the operands of the instruction
then this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
If the operand area "local data" is used for the operand of the instruction then the local data
bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ
Description
You can use the "Set output" instruction to set the signal state of a specified operand to "1".
The instruction is only executed if the result of logic operation (RLO) at the input of the coil is
"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 instruction 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.
You can evaluate whether an F-I/O or channels of an F-I/O are passivated in the associated
F-I/O DB.
Note
If you want to use a formal parameter of an F-FB/F-FC for the operand of the instruction then
this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
If the operand area "local data" is used for the operand of the instruction then the local data
bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ
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-FB/F-FC for the operand of the instruction then
this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You cannot use the "process image input", "process image output", or "bit memory" operand
areas for the operands of the instruction.
If the operand area "local data" is used for the operand of the instruction then the local data
bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ65ಯ
ಯ7DJ,QBಯ 65 ಯ7DJ2XWಯ
6 4
ಯ7DJ,QBಯ
5
Operands "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 "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".
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-FB/F-FC for the operand of the instruction then
this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You cannot use the "process image input", "process image output", or "bit memory" operand
areas for the operands of the instruction.
If the operand area "local data" is used for the operand of the instruction then the local data
bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ56ಯ
ಯ7DJ,QBಯ 56 ಯ7DJ2XWಯ
5 4
ಯ7DJ,QBಯ
6
Operands "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 "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.2.9 --|P|--: Scan operand for positive signal edge (STEP 7 Safety Advanced V11)
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-FB/F-FC for the edge memory bit <Operand2>
of the instruction then this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You cannot use the "process image input", "process image output", or "bit memory" operand
areas for the edge memory bit <Operand2> of the instruction.
If operand area "local data" is used for the edge memory bit <Operand2> of the instruction
then the local data bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
13.2.2.10 --|N|--: Scan operand for negative signal edge (STEP 7 Safety Advanced V11)
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-FB/F-FC for the edge memory bit <Operand2>
of the instruction then this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You cannot use the "process image input", "process image output", or "bit memory" operand
areas for the edge memory bit <Operand2> of the instruction.
If operand area "local data" is used for the edge memory bit <Operand2> of the instruction
then the local data bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
13.2.2.11 P_TRIG: Scan RLO for positive signal edge (STEP 7 Safety Advanced V11)
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-FB/F-FC for the edge memory bit <Operand>
of the instruction then this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You cannot use the "process image input", "process image output", or "bit memory" operand
areas for the edge memory bit <Operand> of the instruction.
If operand area "local data" is used for the edge memory bit <Operand> of the instruction
then the local data bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ
The RLO from the previous bit logic operation is saved in edge memory bit "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.2.12 N_TRIG: Scan RLO for negative signal edge (STEP 7 Safety Advanced V11)
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,
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-FB/F-FC for the edge memory bit <Operand>
of the instruction then this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You cannot use the "process image input", "process image output", or "bit memory" operand
areas for the edge memory bit <Operand> of the instruction.
If operand area "local data" is used for the edge memory bit <Operand> of the instruction
then the local data bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ
The RLO of the previous bit logic operation is saved in edge bit memory "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.3.1 ESTOP1: Emergency Stop up to Stop Category 1 (STEP 7 Safety Advanced V11)
Description
This instruction implements an emergency STOP 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 up to Stop Category 1" 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., ESTOP1_DB_1) or a multi-instance (e.g.,
ESTOP1_Instance_1) for the "Emergency STOP up to Stop Category 1" instruction.
Following the creation step, you will 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 Professional.
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
Tag ACK_NEC 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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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: Only one emergency STOP signal (E_STOP) can be evaluated for the instruction. With
suitable configuration (type of sensor interconnection: 2-channel equivalent), Discrepancy
monitoring of the two NC contacts (when two channels are involved) in accordance with
Categories 3 and 4 as defined in EN 954-1 is performed directly by the F-I/O with inputs. 2-
channel equivalent) directly through the F-I/O with inputs. In order to keep the discrepancy
time from influencing the response time, during the configuration of discrepancy behavior,
you must. parameterize "provide 0 value".
Parameters
The following table shows the parameters of the instruction:
Instruction versions
Two versions are available for this instruction:
● Version 1.0
When projects that were created with S7 Distributed Safety V5.4 SP5 are migrated,
Version 1.0 of the instruction is used automatically.
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.
If you want to compile a migrated safety program with STEP 7 Safety Advanced V11 for
the first time, we recommend that you update the version of the ESTOP1 instruction to
Version 1.1 beforehand. You will then avoid number conflicts.
● Version 1.1
When a new project is created with STEP 7 Safety Advanced V11, Version V1.1 is preset
automatically. This version is functionally identical to Version V1.0, but does not require
the F_TOF block to have a particular number.
For more information on the use of instruction versions, refer to the help on STEP 7
Professional 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 1 to 5 are saved
until acknowledgment at input ACK.
Structure of DIAG
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
(6723
(6723
(1 4 "7DJ2XWB"
"7DJ,Q" (6723 4B'(/$< "7DJ2XWB"
758( $&.B1(& $&.B5(4 "7DJ2XWB"
7DJ,QB$&. $&. ',$*
7PV 7,0(B'(/ (12
(6723
(6723
(1 (12
"7DJ,Q" (6723 4 "7DJ2XWB"
Description
This instruction implements two-hand monitoring.
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. 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., TWO_HAND_DB_1) or a multi-instance (e.g., TWO_HAND_Instance_1) for
the "Two-hand monitoring" instruction. Following the creation step, you will 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 Professional.
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 (type of sensor interconnection: 2-channel 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 "Provide 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 input (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 79))
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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:
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
7:2B+$1'
7:2B+$1'
(1
7DJ,QB ,1
7DJ,QB ,1 4 7DJ2XW
7PV ',6&7,0( (12
7:2B+$1'
7:2B+$1'
(1 (12
7DJ,QB ,1 4 7DJ2XW
7DJ,QB ,1
7PV ',6&7,0(
13.2.3.3 TWO_H_EN: Two-hand monitoring with enable (STEP 7 Safety Advanced V11)
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. 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., TWO_H_EN_DB_1) or a multi-instance (e.g.,
TWO_H_EN_Instance_1) for the "Two-hand monitoring with enable" instruction. Following
the creation step, you will 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 Professional.
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 (type of sensor interconnection: 2-channel 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. parameterize "provide 0 value".
If a discrepancy is detected, a fail-safe value of 0 is entered in the process image input (PII)
for the pushbutton and QBAD or QBAD_I_xx = 1 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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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:
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.
Structure of DIAG
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
7:2B+B(1
7:2B+B(1
(1
7DJ,QB ,1
7DJ,QB !
7DJ,QB ,1 4 7DJ2XWB
7DJ,QB (1$%/( ',$*
7PV ',6&7,0( (12
7:2B+B(1
7:2B+B(1
(1 (12
7DJ,QB ,1 4 7DJ2XWB
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 "Muting" 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.,
MUTING_DB_1) or a multi-instance (e.g., MUTING_Instance_1) for the "Muting" instruction.
Following the creation step, you will 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 Professional.
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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:
Schematic sequence of error-free muting procedure with 4 muting sensors (MS_11, MS_12, MS_21,
MS_22)
1
06B 6HQGHU 06B 'DQJHU
DUHD
● 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 input with the QBAD or QBAD_O_xx signal of the associated F-I/O or
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).
2
06B 6HQGHU 06B 'DQJHU
DUHD
● 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).
3
06B 6HQGHU 06B 'DQJHU
DUHD
● 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).
4
06B 6HQGHU 06B 'DQJHU
DUHD
● 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 sensors are thus activated by the product in reverse order.
06B
06B
06B
06B
W',6&7,0 W',6&7,0
W7,0(B0$;
$&.
087,1*
)$8/7
$&.B5(4
06B 5HFHLYHU
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
Note
Following discrepancy errors and once the maximum muting time has been exceeded,
ACK_REQ is immediately 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.
Timing diagrams for discrepancy errors at sensor pair 1 or interruption of the light curtain (if MUTING
is not active)
1 2
)5((
06B W
06B
06B
06B
W ',6&7,0 W',6&7,0 3
Wุ',6&7,0 3 W7,0(B0$;
$&.
087,1*
4
)$8/7
$&.B5(4
① Sensor pair 1 (MS_11 and MS_12) is not activated within discrepancy time
DISCTIM1.
② The light curtain is interrupted even though the MUTING function is not active.
③ Acknowledgment
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.
Structure of DIAG
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
087,1*
087,1*
(1
7DJ,QB 06B
7DJ,QB 06B
7DJ,QB 06B
7DJ,QB 06B
7DJ,QB 6723
7DJ,QB )5(( 4 7DJ2XWB
087,1*
087,1*
(1 (12
7DJ,QB 06B 4 7DJ2XWB
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. 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., MUT_P_DB_1) or a multi-instance (e.g., MUT_P_Instance_1) for the "Parallel
muting" instruction. Following the creation step, you will 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 Professional.
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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:
Schematic sequence of error-free muting procedure with 4 muting sensors (MS_11, MS_12, MS_21,
MS_22)
1
06B 6HQGHU 06B 'DQJHU
DUHD
● 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 or QBAD_O_xx signal of the associated F-I/O or
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).
2
06B 6HQGHU 06B 'DQJHU
DUHD
● 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).
3
06B 6HQGHU 06B 'DQJHU
DUHD
● 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).
4
06B 6HQGHU 06B 'DQJHU
DUHD
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
direction and the muting sensors are thus activated by the product in reverse order.
06B
W',6&7,0
06B
W',6&7,0 W',6&7,0
06B
W',6&7,0
06B
W',6&7,0
W',6&7,0
W',6&7,0 W',6&7,0
W7,0(B0$;
$&.
087,1*
)$8/7
$&.B5(4
06B 5HFHLYHU
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 (at least one muting sensor is activated and ENABLE = 1)
Enable signal Q becomes 1 again, if:
● Errors, if present, 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 signals that FREE is necessary for error elimination and
for removal of the restart inhibit. Once FREE has occurred, the instruction resets ACK_REQ
to 0.
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)
Timing diagrams for discrepancy errors at sensor pair 1 or interruption of the light curtain (MUTING is
not active)
1 2
)5((
06B
06B
06B
06B
W ',6&7,0 4
3
WV
$&.
087,1*
4
)$8/7
$&.B5(4
(1$%/(
① 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
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)
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
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
087B3
087B3
(1
7DJ,QB 06B
7DJ,QB 06B
7DJ,QB 06B
7DJ,QB 06B
087B3
087B3
(1 (12
7DJ,QB 06B 4 7DJ2XWB
7DJ,QB 06B 087,1* 7DJ2XWB
7DJ,QB 06B $&.B5(4 7DJ2XWB
)$8/7 7DJ2XWB
7DJ,QB 06B
',$*
7DJ,QB 6723
7DJ,QB 7DJ,QB )5((
(1$%/(
)B)'2['&9B4%$'BB 4%$'B087
7DJ,QB
7DJ,QB$&. $&.
7PV ',6&7,0
7PV ',6&7,0
7V 7,0(B0$;
13.2.3.6 EV1oo2DI: 1oo2 evaluation with discrepancy analysis (STEP 7 Safety Advanced V11)
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.
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.,
OB35) 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. 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., EV1oo2DI_DB_1) or a multi-instance (e.g.,
EV1oo2DI_Instance_1) for the "1oo2 evaluation with discrepancy analysis" instruction.
Following the creation step, you will 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
Professional.
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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:
Example
For nonequivalent signals, you have to invert the input (IN1 or IN2) to which you have
assigned the sensor signal with a safe state of 1. You must also OR the sensor signal with
the QBAD or QBAD_I_xx tag of the associated F-I/O DB or channel, so that a signal state of
0 is present at input IN1 or IN2 (after inversion) if fail-safe values are output.
Network1: EV1oo2DI with nonequivalent signals
(9RR',
(9RR',
6HQVRUBB12 ! (1
"Sensor_1_(NC)" ,1 4 "7DJ2XWB"
)%B',['&94%$' ,1 $&.B5(4 "7DJ2XWB"
7PV ',6&7,0( ',6&B)/7 "7DJ2XWB"
758( $&.B1(& ',$*
"7DJ,QB$&." $&. (12
(9RR',
(9RR',
(1 (12
6HQVRUBB "Sensor_1_(NC)" 4
,1 "7DJ2XWB"
12
127 ,1 $&.B5(4 "7DJ2XWB"
7PV ',6&7,0( ',6&B)/7 "7DJ2XWB"
)%B',[
'&94%$' 758( $&.B1(& ',$*
"7DJ,QB$&." $&.
,1
,1
',6&B)/7
$&.B5(4
$&.
',$*%LW
',$*%LW
',6&7,0( ',6&7,0( ',6&7,0( ',6&7,0(
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 you 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.
Structure of DIAG
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
(9RR',
(9RR',
(1
"7DJ,QB" ,1 4 "7DJ2XWB"
(9RR',
(9RR',
(1 (12
"7DJ,QB" ,1 4 "7DJ2XWB"
"7DJ,QB" ,1 $&.B5(4 "7DJ2XWB"
7PV ',6&7,0( ',6&B)/7 "7DJ2XWB"
758( $&.B1(& ',$*
"7DJ,QB$&." $&.
Description
This instruction implements feedback monitoring.
To do this, the signal state of the output Q is checked for equality with 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 error from being detected and an acknowledgment from being required
when the F-I/O controlled by output Q are passivated, you must supply input QBAD_FIO with
the QBAD or QBAD_O_xx tag of the associated F-I/O.
Every call of the "Feedback monitoring" 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., FDBACK_DB_1) or a multi-instance (e.g., FDBACK_Instance_1) for the
"Feedback monitoring" instruction. Following the creation step, you will 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 Professional.
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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:
Interconnection example
)'2
1
3 9'&
3 2
0 . ',
.
① Standard DI
② Input FEEDBACK
③ Output Q
Instruction versions
Two versions are available for this instruction:
● Version 1.0
When projects that were created with S7 Distributed Safety V5.4 SP5 are migrated,
Version 1.0 of the instruction is used automatically.
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.
If you want to compile a migrated safety program with STEP 7 Safety Advanced V11 for
the first time, we recommend that you update the version of the FDBACK instruction to
Version 1.1 beforehand. You will then avoid number conflicts.
● Version 1.1
When a new project is created with STEP 7 Safety Advanced V11, Version V1.1 is preset
automatically. This version is functionally identical to Version V1.0, but does not require
the F_TOF block to have a particular number.
For more information on the use of instruction versions, refer to the help on STEP 7
Professional under "Using instruction versions".
Startup characteristics
After an F-system startup, the instruction does not have be acknowledged when no errors
are present.
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
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
)'%$&.
)'%$&.
(1
7DJ,QB 21
7DJ,QB )(('%$&. 4 7DJ2XWB
)B)'2['&9B4%$'BB 4%$'B),2 (5525 7DJ2XWB
758( $&.B1(& $&.B5(4 7DJ2XWB
7DJ,QB$&. $&. ',$*
7PV )'%B7,0( (12
)'%$&.
)'%$&.
(1 (12
7DJ,QB 21 4 7DJ2XWB
7DJ,QB )(('%$&. (5525 7DJ2XWB
)B)'2['&9B4%$'BB 4%$'B),2 $&.B5(4 7DJ2XWB
758( $&.B1(& ',$*
7DJ,QB$&. $&.
7PV )'%B7,0(
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 must supply inputs QBAD_IN1 or QBAD_IN2 with
the QBAD or QBAD_I_xx tag of the associated F-I/O or 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. 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., SFDOOR_DB_1) or a multi-instance (e.g., SFDOOR_Instance_1) for the
"Safety door monitoring" instruction. Following the creation step, you will 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 Professional.
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:
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.
6DIHW\GRRURSHQ
23(1
)',
96
6DIHW\GRRU
,1 &/26('
',
3RVLWLRQ
VZLWFK
DFWXDWHG
96
,1
',
3RVLWLRQ
VZLWFK
QRW
DFWXDWHG
6DIHW\GRRUFORVHG
23(1
)',
96
&/26('
,1
',
3RVLWLRQ 6DIHW\GRRU
VZLWFK
QRW
DFWXDWHG
96
,1
',
3RVLWLRQ
VZLWFK
DFWXDWHG
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 acknowledgement 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
Example
The following example shows how the instruction works:
6)'225
6)'225
(1
7DJ,QB ,1
7DJ,QB ,1
)B)',['&9B4%$'B,B 4%$'B,1
)B)',['&9B4%$'B,B 4%$'B,1 4 7DJ2XWB
758( 23(1B1(& $&.B5(4 7DJ2XWB
758( $&.B1(& ',$*
7DJ,QB$&. $&. (12
6)'225
6)'225
(1 (12
7DJ,QB ,1 4 7DJ2XWB
13.2.3.9 ACK_GL: Global acknowledgment of all F-I/O in an F-runtime group (STEP 7 Safety
Advanced V11)
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 99) with a positive edge at input ACK_GLOB is required for
reintegration. The acknowledgement occurs analogously to the user acknowledgment via the
ACK_REI tag of the F-I/O DB (Page 79), 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 for 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. 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., 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. Following the creation step, you will 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 Professional.
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:
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.
Example
The following example shows how the instruction works:
$&.B*/
$&.B*/
(1
"7DJ,Q" $&.B*/2% (12
$&.B*/
$&.B*/
(1 (12
"7DJ,Q" $&.B*/2%
Description
You can use the "Generate pulse" instruction to set output Q for an assigned period. The
instruction is started if the result of logic operation (RLO) changes from "0" to "1" (positive
edge) at input IN. The assigned 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.
The current time value can be queried at 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. 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., F_IEC_Timer_DB_1) or a multi-instance (e.g., F_IEC_Timer_Instance_1) for
the "Generate pulse" instruction. Following the creation step, you will 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 Professional.
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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)
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:
When a call is made with PT = 0 ms, the TP instance is not reset completely (initialized).
The instruction behaves in accordance with the timing diagrams: Only 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.
A call with PT < 0 ms resets outputs Q and ET. 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:
Pulse diagram
The following figure shows the pulse diagram of the instruction:
,1
4
37 37 37
(7
37
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
)B,(&B7LPHUB'%
73
7,0(
7DJ,QB 7DJ2XW
&8 4
706 37 (7 7DJB(7
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 development of operand "TagIn_1".
Operand "TagOut" at output Q has signal state "1" as long as the period is running. Operand
"Tag_ET" contains the current time value.
Description
You can use the "Generate on-delay" instruction to delay the setting of output Q by the
assigned period PT. The "Generate on-delay" instruction is started when the result of logic
operation (RLO) at input IN changes from "0" to "1" (positive edge). The assigned period PT
starts running when the instruction starts. When period PT has expired, output Q delivers the
signal state "1". Output Q remains set as long as start input delivers "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.
The current time value can be queried at 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. 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., F_IEC_Timer_DB_1) or a multi-instance (e.g., F_IEC_Timer_Instance_1) for
the "Generate on-delay" instruction. Following the creation step, you will 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 Professional.
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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)
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:
When a call is made with PT = 0 ms, the instance of the TON is not reset completely
(initialized). The instruction behaves in accordance with the timing diagrams: Only output
ET is reset. To restart the on-delay, a new rising signal edge at input IN is required once
PT is greater than 0 again.
A call with PT < 0 ms resets outputs Q and ET. To restart 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:
Pulse diagram
The following figure shows the pulse diagram of the instruction:
,1
4 37 37
(7
37
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
)B,(&B7LPHUB'%
721
7,0(
7DJ,QB 7DJ2XW
&8 4
76 37 (7 7DJB(7
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 "Tag_ET"
contains the current time value.
Description
You can use the "Generate off-delay" instruction to delay resetting 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. The assigned period PT starts when the signal state at input IN
changes back to "0". 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".
The current time value can be queried at output ET. The time value begins at T#0s and ends
when the value of period PT is reached.
Every call of the "Generate off-delay" instruction must be assigned a data area in which the
instruction data are stored. In addition, when the instruction is in inserted in the program, the
"Call options" dialog is automatically opened, where 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. Following the creation step, you will 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 Professional.
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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)
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:
When a call is made with PT = 0 ms, the instance of the TOF is not reset completely
(initialized). The instruction behaves in accordance with the timing diagrams: only 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.
A call with PT < 0 ms resets outputs Q and ET. 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:
Pulse diagram
The following figure shows the pulse diagram of the instruction:
,1
4
37 37
(7
37
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
)B,(&B7LPHUB'%
72)
7,0(
7DJ,QB 7DJ2XW
&8 4
706 37 (7 7DJB(7
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
"Tag_ET" contains the current time value.
Description
You can use the "Count up" instruction to increment the value at output CV. When the signal
state at input CU changes from "0" to "1" (positive signal edge), the instruction is executed
and the current count value at output CV is increased 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 output CV. When the high limit is reached, the signal state at input CU 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. 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.,
F_IEC_Counter_DB_1) or a multi-instance (e.g., F_IEC_Counter_Instance_1) for the "Count
up" instruction. Following the creation step, you will 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 Professional.
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:
Example
The following example shows how the instruction works:
)B,(&B&RXQWHUB'%
&78
ಯ7DJ,QBಯ ,17 ಯ7DJ2XWಯ
&8 4
ಯ7DJ,QBಯ
5 &9 ಯ7DJB&9ಯ
ಯ7DJB39ಯ 39
When the signal state of the "TagIn_1" operand changes from "0" to "1", the "Count up"
instruction is executed and the current count value of the "Tag_CV" operand is increased 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 parameter PV is taken as the limit for the determination of output "TagOut".
Output "TagOut" delivers the signal state "1" as long as the current count value is greater
than or equal to the value of operand "Tag_PV". In all other cases, output TagOut has signal
state "0".
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. In addition, when the instruction is inserted in the program, the
"Call options" dialog is automatically opened, where you can generate 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. Following the creation step, you will 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 Professional.
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:
Example
The following example shows how the instruction works:
)B,(&B&RXQWHUB'%
&7'
ಯ7DJ,QBಯ ,17 ಯ7DJ2XWಯ
&' 4
ಯ7DJ,QBಯ
/' &9 ಯ7DJB&9ಯ
ಯ7DJB39ಯ 39
If the signal state of the "TagIn_1" operand changes from "0" to "1", the "Count down"
instruction is executed and the current count value at output "Tag_CV" is decreased 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 "TagOut" delivers the signal state "1" as long as the current count value is less than
or equal to zero. In all other cases, output TagOut has signal state "0".
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 input CU changes from "0" to "1" (positive signal
edge), the current count value at output CV is increased 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. 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., F_IEC_Counter_DB_1) or a multi-instance (e.g., F_IEC_Counter_Instance_1)
for the "Count up and down" instruction. Following the creation step, you will 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 Professional.
The operating system resets the instances of the "Count up and down" instruction on a cold
restart of the F-system.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
)B,(&B&RXQWHUB'%
&78'
ಯ7DJ,QBಯ ,17 ಯ7DJ2XWB48ಯ
&8 48
ಯ7DJ,QBಯ
&' 4' ಯ7DJ2XWB4'ಯ
ಯ7DJ,QBಯ
5 &9 ಯ7DJB&9ಯ
ಯ7DJ,QBಯ
/'
ಯ7DJB39ಯ 39
When the signal state at input "TagIn_1" or at input "TagIn_2" changes from "0" to "1"
(positive signal edge), the "Count up and down" instruction is executed. When a positive
signal edge is present at input "TagIn_1", the current count value of the "Tag_CV" operand is
increased by one. When a positive signal edge is present at input "TagIn_2", the current
count value at output "Tag_CV" is decreased by one. The count value is increased on each
positive signal edge at input CU until it reaches the high limit of 32767. The count value is
decreased on each positive signal edge at input CD until it reaches the low limit of -32768.
Output "TagOut_QU" delivers the signal state "1" as long as the current count value is
greater than or equal to the value at input "Tag_PV". In all other cases, output TagOut_QU
has signal state "0".
Output "TagOut_QD" delivers the signal state "1" as long as the current count value is less
than or equal to zero. In all other cases, output TagOut_QD has signal state "0".
Description
You can use the "Equal" instruction to determine if the first comparison value (<Operand1>)
is equal to the second comparison value (<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".
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:
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:
ಯ7DJ9DOXHBಯ
ಯ7DJ,QBಯ ಯ7DJ,QBಯ ಯ7DJ2XWಯ
,17 6
ಯ7DJ9DOXHBಯ
Description
You can use the "Not equal" instruction to determine if the first comparison value
(<Operand1>) is not equal to the second comparison value (<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".
The RLO is linked to the RLO of the instruction 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:
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:
ಯ7DJ9DOXHBಯ
ಯ7DJ,QBಯ ಯ7DJ,QBಯ ! ಯ7DJ2XWಯ
,17 6
ಯ7DJ9DOXHBಯ
13.2.6.3 CMP >=: Greater than or equal (STEP 7 Safety Advanced V11)
Description
You can use the "Greater or equal" instruction to determine if the first comparison value
(<Operand1>) is greater than or equal to the second comparison value (<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".
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:
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:
ಯ7DJ9DOXHBಯ
ಯ7DJ,QBಯ ಯ7DJ,QBಯ ! ಯ7DJ2XWಯ
,17 6
ಯ7DJ9DOXHBಯ
13.2.6.4 CMP <=: Less than or equal (STEP 7 Safety Advanced V11)
Description
You can use the "Less or equal" instruction to determine if the first comparison value
(<Operand1>) is less than or equal to the second comparison value (<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".
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:
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:
ಯ7DJ9DOXHBಯ
ಯ7DJ,QBಯ ಯ7DJ,QBಯ ಯ7DJ2XWಯ
,17 6
ಯ7DJ9DOXHBಯ
Description
You can use the "Greater than" instruction to determine if the first comparison value
(<Operand1>) is greater than the second comparison value (<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".
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:
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:
ಯ7DJ9DOXHBಯ
ಯ7DJ,QBಯ ಯ7DJ,QBಯ ! ಯ7DJ2XWಯ
,17 6
ಯ7DJ9DOXHBಯ
Description
You can use the "Less than" instruction to determine if the first comparison value
(<Operand1>) is less than the second comparison value (<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".
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:
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:
ಯ7DJ9DOXHBಯ
ಯ7DJ,QBಯ ಯ7DJ,QBಯ ಯ7DJ2XWಯ
,17 6
ಯ7DJ9DOXHBಯ
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" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Note
If the result of the instruction is outside the range permitted for the data type, then the F-CPU
goes to STOP when the result is sent to an output at an F-I/O or to a partner F-CPU via
safety-related CPU-CPU communication.
One of the following diagnostic events is then
entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
You must therefore ensure that the permitted range for the data type is observed when
creating the program!
If this is not possible, 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 into it.
Note the following:
The result of the instruction behaves 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/134200)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Parameters
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:
Network 1:
$''
,17
(1 (12
ಯ7DJ9DOXHBಯ ,1
ಯ7DJ9DOXHBಯ ,1 287 ಯ7DJ5HVXOWಯ
Network 2:
29 ಯ7DJ2XWಯ
6
The "Add" instruction is always executed (regardless of the signal state at enable input EN).
The value of the "TagValue_1" operand is added to value of the TagValue_2 operand. The
result of the addition is stored in the "TagResult" 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.
See also
---| |--- OV: Get status bit OV (STEP 7 Safety Advanced V11) (Page 354)
---| / |--- OV: Get negated status bit OV (STEP 7 Safety Advanced V11) (Page 355)
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" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Note
If the result of the instruction is outside the range permitted for the data type, then the F-CPU
goes to STOP when the result is sent to an output at an F-I/O or to a partner F-CPU via
safety-related CPU-CPU communication.
One of the following diagnostic events is then
entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
You must therefore ensure that the permitted range for the data type is observed when
creating the program!
If this is not possible, 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 into it.
Note the following:
The result of the instruction behaves 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/134200)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Parameters
The following table shows the parameters of the instruction:
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:
Network 1:
68%
,17
(1 (12
ಯ7DJ9DOXHBಯ ,1
ಯ7DJ9DOXHBಯ ,1 287 ಯ7DJ5HVXOWಯ
Network 2:
29 ಯ7DJ2XWಯ
6
The "Subtract" instruction is always executed (regardless of the signal state at enable input
EN).
The value of operand "TagValue_2" is subtracted from the value of operand "TagValue_1".
The result of the addition is stored in operand "TagResult".
If 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.
See also
---| |--- OV: Get status bit OV (STEP 7 Safety Advanced V11) (Page 354)
---| / |--- OV: Get negated status bit OV (STEP 7 Safety Advanced V11) (Page 355)
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" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Note
If the result of the instruction is outside the range permitted for the data type, then the F-CPU
goes to STOP when the result is sent to an output at an F-I/O or to a partner F-CPU via
safety-related CPU-CPU communication.
One of the following diagnostic events is then
entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
You must therefore ensure that the permitted range for the data type is observed when
creating the program!
If this is not possible, 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 into it.
Note the following:
The result of the instruction behaves 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/134200)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Parameters
The following table shows the parameters of the instruction:
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:
Network 1:
08/
',17
(1 (12
ಯ7DJ9DOXHBಯ ,1
ಯ7DJ9DOXHBಯ ,1 287 ಯ7DJ5HVXOWಯ
Network 2:
29 ಯ7DJ2XWಯ
6
The "Multiply" instruction is always executed (regardless of the signal state at enable input
EN).
The value of the "TagValue_1" operand is multiplied by the value of the "TagValue_2"
operand. The result of the multiplication is stored in the "TagResult" operand.
If 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.
See also
---| |--- OV: Get status bit OV (STEP 7 Safety Advanced V11) (Page 354)
---| / |--- OV: Get negated status bit OV (STEP 7 Safety Advanced V11) (Page 355)
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" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Note
If the result of the instruction is outside the range permitted for the data type, then the F-CPU
goes to STOP when the result is sent to an output at an F-I/O or to a partner F-CPU via
safety-related CPU-CPU communication.
One of the following diagnostic events is then
entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
You must therefore ensure that the permitted range for the data type is observed when
creating the program!
If this is not possible, 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 into it.
Note the following:
The result of the instruction behaves 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/134200)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Note
If the divisor (input IN2) of a DIV instruction = 0, the quotient of the division (result of division
at output OUT) = 0. The result behaves like the corresponding instruction in a standard
block. The F-CPU does not go to STOP mode. The behavior occurs regardless of whether a
"Get status bit OV" instruction has been inserted in the next network.
Parameters
The following table shows the parameters of the instruction:
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:
Network 1:
',9
',17
(1 (12
ಯ7DJ9DOXHBಯ ,1
ಯ7DJ9DOXHBಯ ,1 287 ಯ7DJ5HVXOWಯ
Network 2:
29 ಯ7DJ2XWಯ
6
The "Divide" instruction is always executed (regardless of the signal state at enable input
EN).
The value of operand "TagValue_1" is divided by the value of operand "TagValue_2". The
result of the division is stored in operand "TagResult".
If 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.
See also
---| |--- OV: Get status bit OV (STEP 7 Safety Advanced V11) (Page 354)
---| / |--- OV: Get negated status bit OV (STEP 7 Safety Advanced V11) (Page 355)
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" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Note
If the result of the instruction is outside the range permitted for the data type, then the F-CPU
goes to STOP when the result is sent to an output at an F-I/O or to a partner F-CPU via
safety-related CPU-CPU communication.
One of the following diagnostic events is then
entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
You must therefore ensure that the permitted range for the data type is observed when
creating the program!
If this is not possible, 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 into it.
Note the following:
The result of the instruction behaves 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/134200)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Parameters
The following table shows the parameters of the instruction:
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:
Network 1:
1(*
',17
(1 (12
Network 2:
29 ಯ7DJ2XWಯ
6
The "Create twos 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
"TagOut_Value" operand.
If an overflow occurs during execution of the "Create twos 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.
See also
---| |--- OV: Get status bit OV (STEP 7 Safety Advanced V11) (Page 354)
---| / |--- OV: Get negated status bit OV (STEP 7 Safety Advanced V11) (Page 355)
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 identical operand widths can be specified for input IN and output OUT1.
Enable input "EN" or enable output "ENO" cannot be connected. The instruction is therefore
always executed (regardless of the signal state at enable input "EN").
Parameters
Example
The following example shows how the instruction works:
029(
(1 (12
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 "TagOut_Value".
13.2.8.2 WR_FDB: Write value indirectly to an F-DB (STEP 7 Safety Advanced V11)
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 diagnostic 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:
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:
:5B)'%
,17
(1
"7DJ,Q" ,1
")B'%".VAR_INT10 ,1,B$''5
")B'%".VAR_INT15 (1'B$''5
2))6(7 (12
13.2.8.3 RD_FDB: Read value indirectly from an F-DB (STEP 7 Safety Advanced V11)
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 diagnostic 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 Advanced V11)
(Page 328).
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:
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:
5'B)'%
,17
(1
")B'%".VAR_INT10 ,1,B$''5
")B'%".VAR_INT15 (1'B$''5 287
2))6(7 (12
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 output OUT.
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:
Example
The following example shows how the instruction works:
&219
,17 WR ',17
(1 (12
The instruction is always executed regardless of the signal state at enable input EN. The
content of the operand "TagIn_Value" is read and converted to an integer (32 bit). The result
is stored in operand "TagOut_Value".
13.2.9.2 BO_W: Convert 16 data elements of data type BOOL to a data element of data type
WORD (STEP 7 Safety Advanced V11)
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 ith 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").
Note: To supply inputs IN0 to IN15 with Boolean constants "0" and "1", you can access tags
"VKE0" and "VKE1" in the F-shared DB using a fully-qualified DB access
("F_GLOBDB".VKE0 or "F_GLOBDB".VKE1).
Parameters
Example
The following example shows how the instruction works:
%2B:
(1 (12
7DJ9DOXHB ,1 287 7DJ5HVXOW
7DJ9DOXHB ,1
7DJ9DOXHB ,1
7DJ9DOXHB ,1
The following table shows how the instruction works using specific operand values:
The values of operands "TagValue_0" to " TagValue_15" are combined to form data type
WORD and assigned to operand "TagResult".
13.2.9.3 W_BO: Convert a data element of data type WORD to 16 data elements of data type
BOOL (STEP 7 Safety Advanced V11)
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 ith bit of the WORD value is 0 (or 1).
Enable input "EN" or enable output "ENO" cannot be connected. The instruction is therefore
always executed (regardless of the signal state at enable input "EN").
Parameters
Example
The following example shows how the instruction works:
:B%2
(1 (12
7DJ9DOXH ,1 287 7DJ2XWB
287 7DJ2XWB
287 7DJ2XWB
287 7DJ2XWB
The following table shows how the instruction works using specific operand values:
The value of operand "TagValue" of data type WORD is converted to the 16 values
"TagOUT_0" to "TagOUT_15" of data type BOOL.
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. Following the creation step, you will 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 Professional.
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
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
7FFFH (for overflow) or 8000H (for underflow) in the PII for the safety program.
If other fail-safe values are to be output in this case, you must evaluate the QBAD tag in the
F-I/O DB (branch to output of an individual fail-safe value).
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 output of an individual fail-safe value by evaluating outputs
OUT_HI and OUT_LO, respectively.
Example
The following example shows how the instruction works:
6&$/(
(1 (12
7DJ,QB9DOXH ,1
287 7DJ2XWB9DOXH
+,B/,0 287B+,
/2B/,0 287B/2
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 340) (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
You are not permitted to program a SENDDP or SENDS7 call between a jump instruction
and the associated destination of the jump instruction.
Example
The following example shows how the instruction works:
1HWZRUN
ಯ7DJ,QBಯ &$6
-03
1HWZRUN
ಯ7DJ,QBಯ ಯ7DJ2XWBಯ
5
1HWZRUN
&$6
ಯ7DJ,QBಯ ಯ7DJ2XWBಯ
5
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.
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 340)
(LABEL). The designation of the jump label is specified in the placeholder above the
instruction box.
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 excuting in the next network.
Note
You are not permitted to program a SENDDP or SENDS7 call between a jump instruction
and the associated destination of the jump instruction.
Example
The following example shows how the instruction works:
1HWZRUN
ಯ7DJ,QBಯ &$6
-031
1HWZRUN
ಯ7DJ,QBಯ ಯ7DJ2XWBಯ
5
1HWZRUN
&$6
ಯ7DJ,QBಯ ಯ7DJ2XWBಯ
5
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.
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:
1HWZRUN
ಯ7DJ,QBಯ &$6
-03
1HWZRUN
ಯ7DJ,QBಯ ಯ7DJ2XWBಯ
5
1HWZRUN
&$6
ಯ7DJ,QBಯ ಯ7DJ2XWBಯ
5
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 Advanced V11) (Page 338)
---( JMPN ): Jump if RLO = 0 (STEP 7 Safety Advanced V11) (Page 339)
--(RET): Return (STEP 7 Safety Advanced V11) (Page 341)
Description
You can use the "Return" operation to stop the processing of a block.
If the result of logic operation (RLO) at the input of the "Return" instruction is "1", 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
You must not assign any RET instruction in the Main Safety Block.
Example
The following example shows how the instruction works:
ಯ7DJ,Qಯ 5/2
5(7
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 Advanced V11) (Page 338)
---( JMPN ): Jump if RLO = 0 (STEP 7 Safety Advanced V11) (Page 339)
LABEL: Jump label (STEP 7 Safety Advanced V11) (Page 340)
13.2.10.5 ---(OPN): Open global data block (STEP 7 Safety Advanced V11)
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 following 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 for 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" instruction, you must ensure that the DB
register is restored by repeating 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:
Example
The following example shows how the instruction works:
1HWZRUN
0RWRUB'%
231,
1HWZRUN
'%; 7DJB2XWSXW
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.
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:
Example
The following example shows how the instruction works:
$1'
:25'
(1 (12
7DJ9DOXHB ,1
7DJ9DOXHB ,1 287 7DJ5HVXOW
The instruction is always executed regardless of the signal state at enable input "EN". The
value of the "TagValue_1" operand and the value of the "TagValue_2" operand are ANDed.
The result is mapped bit-by-bit and output in the "TagResult" operand.
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").
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
25
:25'
(1 (12
7DJ9DOXHB ,1
7DJ9DOXHB ,1 287 7DJ5HVXOW
The instruction is always executed regardless of the signal state at enable input "EN". The
value of the "TagValue_1" operand and the value of the "TagValue_2" operand are ORed.
The result is mapped bit-by-bit and output in the "TagResult" operand.
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:
Example
The following example shows how the instruction works:
;25
:25'
(1 (12
7DJ9DOXHB ,1
7DJ9DOXHB ,1 287 7DJ5HVXOW
The instruction is always executed regardless of the signal state at enable input "EN". The
value of the "TagValue_1" operand and the value of the "TagValue_2" operand are logically
combined by EXCLUSIVE OR. The result is mapped bit-by-bit and output in the "TagResult"
operand.
Description
You can use the "Shift right" instruction to move the content of the operand at input IN bit-by-
bit to the right and query the result at output OUT. You use parameter N (low-byte) to specify
the number of bit positions by which the specified value is moved.
When the value at parameter N (low-byte) is "0", the value at input IN is copied into the
operand at output OUT.
When the value at parameter N (low-byte) is greater than the number of available bit
positions, the operand value at input IN is moved by the available number of bit positions to
the right.
The bit locations that are freed up in the left 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 right:
1 SRVLWLRQV
287
7KHELWORFDWLRQVWKDW 7KHVHVL[ELWVZLOO
DUHIUHHGXSDUHILOOHG EHORVW
ZLWK]HURV
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:
Example
The following example shows how the instruction works:
6+5
:25'
(1 (12
ಯ7DJ,QB9DOXHಯ ,1 287 ಯ7DJ2XWB9DOXHಯ
ಯ7DJ1XPEHUಯ 1
The following table shows how the instruction works using specific operand values:
N TagNumber 3
OUT 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 "TagIn_Value" is moved three bit positions to the right. The result is
output at output "TagOut_Value".
Description
You can use the "Shift left" instruction to move the content of the operand at input IN bit-by-
bit to the left and query the result at output OUT. You use parameter N (low-byte) to specify
the number of bit positions by which the specified value is moved.
When the value at parameter N (low-byte) is "0", the value at input IN is copied into the
operand at output OUT.
When the value at parameter N (low-byte) is greater than the number of available bit
positions, the operand value at input IN is moved by the available number of bit positions to
the left.
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:
1 SRVLWLRQV
287
7KHVHVL[ELWVZLOO 7KHELWORFDWLRQVWKDW
EHORVW DUHIUHHGXSDUHILOOHG
ZLWK]HURV
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:
Example
The following example shows how the instruction works:
6+/
:25'
(1 (12
The following table shows how the instruction works using specific operand values:
N TagNumber 4
OUT 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 "TagIn_Value" is moved four bit positions to the left. The result is
output at output "TagOut_Value".
13.2.13 Operating
Description
This instruction enables fail-safe acknowledgment from an operator control and monitoring
system. It allows, for example, reintegration of F-I/O to be controlled from the operator
control and monitoring system. Acknowledgment takes place in two steps:
● In/out parameter IN changes to a value of 6.
● In/out parameter IN changes to a value of 9 within 1 minute.
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 1 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 9 within 1 minute or
the change occurred before 1 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 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. 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., ACK_OP_DB_1) or a multi-instance (e.g., ACK_OP_Instance_1)
for the "Fail-safe acknowledgment" instruction. Following the creation step, you will 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 Professional.
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 mode if the information above is not observed. One of the
following diagnostic events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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
You can read out output Q by means of operator control and monitoring systems or, if
applicable, you can evaluate it in your standard user program.
You can supply in/out parameter IN with just a memory word or nothing at all. In the safety
program, read and write access to in/out parameter IN in the associated instance DB is not
permitted!
Parameters
The following table shows the parameters of the instruction:
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
$&.B23
$&.B23
(1 287 7DJ2XW
,1 4
(12
See also
Implementing User Acknowledgment in the Safety Program of the F-CPU of a DP Master or
IO Controller (Page 99)
Implementing user acknowledgment in the safety program of the F-CPU of a I-slave or I-
device (Page 102)
13.2.14.1 ---| |--- OV: Get status bit OV (STEP 7 Safety Advanced V11)
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 condition 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/134200)).
Example
The following example shows how the instruction works:
Network 1:
$''
,17
(1 (12
ಯ7DJ9DOXHBಯ ,1
ಯ7DJ9DOXHBಯ ,1 287 ಯ7DJ5HVXOWಯ
Network 2:
29 ಯ7DJ2XWಯ
6
The "Add" instruction is always executed (regardless of the signal state at enable input EN).
The value of the "TagValue_1" operand is added to value of the TagValue_2 operand. The
result of the addition is stored in the "TagResult" 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.2.14.2 ---| / |--- OV: Get negated status bit OV (STEP 7 Safety Advanced V11)
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. 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 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 calculation
(http://support.automation.siemens.com/WW/view/en/49368678/134200)).
Example
The following example shows how the instruction works:
1HWZRUN
$''
,17
(1 (12
ಯ7DJ9DOXHBಯ ,1
ಯ7DJ9DOXHBಯ ,1 287 ಯ7DJ5HVXOWಯ
1HWZRUN
29 ಯ7DJ2XWಯ
6
The "Add" instruction is always executed (regardless of the signal state at enable input EN).
The value of the "TagValue_1" operand is added to value of the TagValue_2 operand. The
result of the addition is stored in the "TagResult" 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.2.15 Communication
13.2.15.1 PROFIBUS/PROFINET
SENDDP and RCVDP: Send and receive data via PROFIBUS DP/PROFINET IO (STEP 7 Safety
Advanced V11)
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
Description
The SENDDP instruction sends 16 data elements of data type BOOL and 2 data elements of
data type INT 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. 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.,
RCVDP_DB_1) or a multi-instance (e.g., RCVDP_Instance_1) for this instruction. Following
the creation step, you will 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 Professional.
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.
With the RCVDP instruction, the data received are available at output RD_BO_xx or RD_I_xx
for additional processing by other F-blocks/instructions.
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 deactivated safety mode,
output SENDMODE = 1.
WARNING
The value for each address relationship (input parameter DP_DP_ID; data type: INT) is
user-defined; however, it must be unique from all other safety-related communication
connections in the network. The uniqueness must be checked in the print-out of the safety
program during acceptance testing of the safety program. Additional information can be
found in Correctness of the communication configuration (Page 208).
You must supply inputs DP_DP_ID and LADDR with constant values when calling the
instruction. Direct read or write access to the associated instance DB is not permitted in the
safety program! (S016)
Note
Within a safety program, you must assign a different start address 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.
The input and output parameters of the RCVDP instruction must not be supplied with
temporary or static local data of the main safety block.
The input parameters of the RCVDP instruction must not be initialized with output
parameters (using fully qualified DB accesses) of a RCVDP or RCVS7 instruction called in a
preceding network.
You must not use an actual parameter for an output parameter of a RCVDP, if it is already
being used for an input parameter of the same or another RCVDP or RCVS7 instruction. The
F-CPU can go to STOP if this is not observed. One of the following diagnostic events is then
entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You must not program any SENDDP instruction between a JMP or JMPN instruction and the
associated destination network of the JMP or JMPN instruction.
You must not program any RET instruction before a SENDDP instruction.
Placement
The RCVDP instruction must be inserted at the start of the main safety block and the
SENDDP instruction at the end.
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 SUBBI_xx.
The SENDDP and RCVDP instructions signal this at output SUBS_ON with 1. Output
SENDMODE has a default of 0 and is not updated, as long as output SUBS_ON = 1.
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) 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 RCVDP instructions, and the
bus connection. You also obtain information on possible error causes by evaluating outputs
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.
6(1'B'3
(5525
68%621
5&9'3
$&.B5(,
$&.B5(4
(5525
68%6B21
&RPPXQLFDWLRQHUURU $FNQRZOHGJPHQWRQ
GHWHFWHGE\5&9'3 5&9'3
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.
See also
Configuring and Programming Communication (Page 111)
Safety-related IO controller-IO controller communication (Page 114)
Safety-related master-master communication (Page 122)
Safety-related communication between I/O-controller and I-device (Page 130)
Safety-related master-I-slave communication (Page 136)
Safety-related IO Controller-I-slave communication (Page 154)
Communication with S7 Distributed Safety via PN/PN coupler (IO Controller-IO Controller
communication) (Page 162)
Communication with S7 Distributed Safety via DP/DP coupler (master-master
communication) (Page 163)
13.2.15.2 S7 communication
SENDS7 and RCVS7: Communication via S7 connections (STEP 7 Safety Advanced V11)
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 V11, 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 155).
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 for this reason when the instruction
is inserted in the program; in it 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
you have created the data block, you will 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 Professional.
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 158)".
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
deactivated safety mode, then output SENDMODE = 1.
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.
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 each address relationship (input parameter R_ID; data type: DWORD) is
user-defined; however, it must be an odd number and be unique from all other safety-
related communication connections in the network. 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)
Note
A separate instance DP 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 input and output parameters of the RCVS7 instruction must not be initialized with
temporary or static local data of the main safety block.
The input parameters of the RCVS7 instruction must not be initialized with output parameters
(using fully qualified DB accesses) of a RCVS7 or RCVDP instruction called in a preceding
network.
You must not use an actual parameter for an output parameter of an RCVS7 instruction, if it
is already being used for an input parameter of the same or another RCVS7 or RCVDP
instruction. The F-CPU can go to STOP if this is not observed. One of the following
diagnostic events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You must not program any SENDS7 instruction between a JMP or JMPN instruction and the
associated destination network of the JMP or JMPN instruction.
You must not program a RET instruction prior to a SENDS7 instruction.
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 at output SUBS_ON with 1. Output
SENDMODE (RCVS7 instruction) has a default of 0 and is not updated, as long as output
SUBS_ON = 1.
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, parameter assignment of the SENDS7 and 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.
6(1'6
(5525
68%621
5&96
$&.B5(,
$&.B5(4
(5525
68%6B21
&RPPXQLFDWLRQHUURU $FNQRZOHGJPHQWRQ
GHWHFWHGE\5&96 5&96
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.
Structure of DIAG
See also
Configuration (Page 25)
13.3.1 General
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.
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.
If the instruction acts as a function block (FB) internally, 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 multi-instance, in which data of the inserted instruction are stored. After its
creation, 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 will find it in the block interface in the "Static" section.
Result
The empty box is changed to the respective FBD element. Placeholders are inserted for the
parameters.
Description
You use branches to program parallel connections with the Function Block Diagram (FBD)
programming language. For this purpose, you use branches that you insert between the
boxes. 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 to "Basic instructions > General > Branch".
3. Use a drag-and-drop operation to move the element to the desired place in the network.
Example
The following figure provides an example of how to use branches:
ಯ7DJ,QBಯ
ಯ7DJ2XWBಯ
ಯ7DJ,QBಯ
ಯ7DJ2XWBಯ
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:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ
ಯ7DJ,QBಯ ಯ7DJ2XWಯ
ಯ7DJ,QBಯ
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 Advanced V11) (Page 374)
OR logic operation (STEP 7 Safety Advanced V11) (Page 376)
X: EXCLUSIVE OR logic operation (STEP 7 Safety Advanced V11) (Page 377)
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:
ಯ7DJ,QBಯ
ಯ7DJ,QBಯ
ಯ7DJ,QBಯ
!
ಯ7DJ2XWಯ
ಯ7DJ,QBಯ
ಯ7DJ,QBಯ
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.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ
ಯ7DJ2XWಯ
ಯ7DJ,QBಯ
Output "TagOut" is set when the signal state of operands "TagIn_1" and "TagIn_2" is "1".
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 Advanced V11) (Page 372)
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:
Example
The following example shows how the instruction works:
!
ಯ7DJ,QBಯ
ಯ7DJ2XWಯ
ಯ7DJ,QBಯ
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 Advanced V11) (Page 372)
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 is "1" if an odd-numbered quantity of queried operands returns the result
"1".
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
;
ಯ7DJ,QBಯ
ಯ7DJ2XWಯ
ಯ7DJ,QBಯ
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.
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 Signal state of the Signal state of the Result of logic operation
operand second operand third operand
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 Advanced V11) (Page 372)
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", 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 "Assign" instruction can be placed at any position in the logic operation sequence.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ
ಯ7DJ,QBಯ
!
ಯ7DJ2XWಯ
ಯ7DJ,QBಯ
Operand "TagOut" at the output of the "Assign" 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".
Description
You can use the "Reset output" instruction to reset the signal state of a specified operand to
"0".
The instruction is only executed if the result of logic operation (RLO) is "1" at the box input. If
the box input has signal state "1", 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 you want to use a formal parameter of an F-FB/F-FC for the operand of the instruction then
this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
If the operand area "local data" is used for the operand of the instruction then the local data
bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ
ಯ7DJ,QBಯ
!
ಯ7DJ2XWಯ
ಯ7DJ,QBಯ 5
Description
You can use the "Set output" instruction to set the signal state of a specified operand to "1".
The instruction is only executed if the result of logic operation (RLO) is "1" at the box input. If
the box input has signal state "1", 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 instruction 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.
You can evaluate whether an F-I/O or channels of an F-I/O are passivated in the associated
F-I/O DB.
Note
If you want to use a formal parameter of an F-FB/F-FC for the operand of the instruction then
this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
If the operand area "local data" is used for the operand of the instruction then the local data
bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ
ಯ7DJ,QBಯ
!
ಯ7DJ2XWಯ
ಯ7DJ,QBಯ 6
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 at 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 is "1" at input R1, 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 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-FB/F-FC for the operand of the instruction then
this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You cannot use the "process image input", "process image output", or "bit memory" operand
areas for the operands of the instruction.
If the operand area "local data" is used for the edge bit memory of the instruction then the
local data bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ65ಯ
65
ಯ7DJ,QBಯ 6
ಯ7DJ2XWಯ
ಯ7DJ,QBಯ 5 4
Operands "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 "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".
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-FB/F-FC for the operand of the instruction then
this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You cannot use the "process image input", "process image output", or "bit memory" operand
areas for the operands of the instruction.
If the operand area "local data" is used for the edge bit memory of the instruction then the
local data bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ56ಯ
56
ಯ7DJ,QBಯ 5
ಯ7DJ2XWಯ
ಯ7DJ,QBಯ 6 4
Operands "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 "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.3.2.9 P: Scan operand for positive signal edge (STEP 7 Safety Advanced V11)
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-FB/F-FC for the edge memory bit <Operand2>
of the instruction then this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You cannot use the "process image input", "process image output", or "bit memory" operand
areas for the edge memory bit <Operand2> of the instruction.
If operand area "local data" is used for the edge memory bit <Operand2> of the instruction
then the local data bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ
3
ಯ7DJB0ಯ
ಯ7DJ2XWಯ
ಯ7DJ,QBಯ
13.3.2.10 N: Scan operand for negative signal edge (STEP 7 Safety Advanced V11)
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-FB/F-FC for the edge memory bit <Operand2>
of the instruction then this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You cannot use the "process image input", "process image output", or "bit memory" operand
areas for the edge memory bit <Operand2> of the instruction.
If operand area "local data" is used for the edge memory bit <Operand2> of the instruction
then the local data bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ
1
ಯ7DJB0ಯ
ಯ7DJ2XWಯ
ಯ7DJ,QBಯ
13.3.2.11 P_TRIG: Scan RLO for positive signal edge (STEP 7 Safety Advanced V11)
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 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-FB/F-FC for the edge memory bit <Operand>
of the instruction then this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You cannot use the "process image input", "process image output", or "bit memory" operand
areas for the edge memory bit <Operand> of the instruction.
If operand area "local data" is used for the edge memory bit <Operand> of the instruction
then the local data bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ !
ಯ7DJ,QBಯ
&$6
3B75,*
ಯ7DJ2XWಯ &/. 4 -03
ಯ7DJB0ಯ
The RLO from the previous bit logic operation is saved in edge memory bit "Tag_M". If a
change in the RLO signal state from "0" to "1" is detected, the program jumps to jump label
CAS1.
13.3.2.12 N_TRIG: Scan RLO for negative signal edge (STEP 7 Safety Advanced V11)
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,
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-FB/F-FC for the edge memory bit <Operand>
of the instruction then this must be declared as an in/out parameter.
The F-CPU can go to STOP if this caution is not observed. One of the following diagnostic
events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You cannot use the "process image input", "process image output", or "bit memory" operand
areas for the edge memory bit <Operand> of the instruction.
If operand area "local data" is used for the edge memory bit <Operand> of the instruction
then the local data bit used must be initialized beforehand.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ !
ಯ7DJ,QBಯ
&$6
1B75,*
ಯ7DJ2XWಯ &/. 4 -03
ಯ7DJB0ಯ
The RLO of the previous bit logic operation is saved in edge bit memory "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.3.1 ESTOP1: Emergency Stop up to Stop Category 1 (STEP 7 Safety Advanced V11)
Description
This instruction implements an emergency STOP 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 up to Stop Category 1" 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., ESTOP1_DB_1) or a multi-instance (e.g.,
ESTOP1_Instance_1) for the "Emergency STOP up to Stop Category 1" instruction.
Following the creation step, you will 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 Professional.
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
Tag ACK_NEC 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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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: Only one emergency STOP signal (E_STOP) can be evaluated for the instruction. With
suitable configuration (type of sensor interconnection: 2-channel equivalent), Discrepancy
monitoring of the two NC contacts (when two channels are involved) in accordance with
Categories 3 and 4 as defined in EN 954-1 is performed directly by the F-I/O with inputs. 2-
channel equivalent) directly through the F-I/O with inputs. In order to keep the discrepancy
time from influencing the response time, during the configuration of discrepancy behavior,
you must. parameterize "provide 0 value".
Parameters
The following table shows the parameters of the instruction:
Instruction versions
Two versions are available for this instruction:
● Version 1.0
When projects that were created with S7 Distributed Safety V5.4 SP5 are migrated,
Version 1.0 of the instruction is used automatically.
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.
If you want to compile a migrated safety program with STEP 7 Safety Advanced V11 for
the first time, we recommend that you update the version of the ESTOP1 instruction to
Version 1.1 beforehand. You will then avoid number conflicts.
● Version 1.1
When a new project is created with STEP 7 Safety Advanced V11, Version V1.1 is preset
automatically. This version is functionally identical to Version V1.0, but does not require
the F_TOF block to have a particular number.
For more information on the use of instruction versions, refer to the help on STEP 7
Professional 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 1 to 5 are saved
until acknowledgment at input ACK.
Structure of DIAG
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
(6723
(6723
(1 4 "7DJ2XWB"
"7DJ,Q" (6723 4B'(/$< "7DJ2XWB"
758( $&.B1(& $&.B5(4 "7DJ2XWB"
7DJ,QB$&. $&. ',$*
7PV 7,0(B'(/ (12
(6723
(6723
(1 (12
"7DJ,Q" (6723 4 "7DJ2XWB"
Description
This instruction implements two-hand monitoring.
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. 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., TWO_HAND_DB_1) or a multi-instance (e.g., TWO_HAND_Instance_1) for
the "Two-hand monitoring" instruction. Following the creation step, you will 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 Professional.
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 (type of sensor interconnection: 2-channel 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 "Provide 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 input (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 79))
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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:
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
7:2B+$1'
7:2B+$1'
(1
7DJ,QB ,1
7DJ,QB ,1 4 7DJ2XW
7PV ',6&7,0( (12
7:2B+$1'
7:2B+$1'
(1 (12
7DJ,QB ,1 4 7DJ2XW
7DJ,QB ,1
7PV ',6&7,0(
13.3.3.3 TWO_H_EN: Two-hand monitoring with enable (STEP 7 Safety Advanced V11)
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. 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., TWO_H_EN_DB_1) or a multi-instance (e.g.,
TWO_H_EN_Instance_1) for the "Two-hand monitoring with enable" instruction. Following
the creation step, you will 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 Professional.
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 (type of sensor interconnection: 2-channel 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. parameterize "provide 0 value".
If a discrepancy is detected, a fail-safe value of 0 is entered in the process image input (PII)
for the pushbutton and QBAD or QBAD_I_xx = 1 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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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:
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.
Structure of DIAG
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
7:2B+B(1
7:2B+B(1
(1
7DJ,QB ,1
7DJ,QB !
7DJ,QB ,1 4 7DJ2XWB
7DJ,QB (1$%/( ',$*
7PV ',6&7,0( (12
7:2B+B(1
7:2B+B(1
(1 (12
7DJ,QB ,1 4 7DJ2XWB
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 "Muting" 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.,
MUTING_DB_1) or a multi-instance (e.g., MUTING_Instance_1) for the "Muting" instruction.
Following the creation step, you will 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 Professional.
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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:
Schematic sequence of error-free muting procedure with 4 muting sensors (MS_11, MS_12, MS_21,
MS_22)
1
06B 6HQGHU 06B 'DQJHU
DUHD
● 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 input with the QBAD or QBAD_O_xx signal of the associated F-I/O or
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).
2
06B 6HQGHU 06B 'DQJHU
DUHD
● 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).
3
06B 6HQGHU 06B 'DQJHU
DUHD
● 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).
4
06B 6HQGHU 06B 'DQJHU
DUHD
● 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 sensors are thus activated by the product in reverse order.
06B
06B
06B
06B
W',6&7,0 W',6&7,0
W7,0(B0$;
$&.
087,1*
)$8/7
$&.B5(4
06B 5HFHLYHU
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
Note
Following discrepancy errors and once the maximum muting time has been exceeded,
ACK_REQ is immediately 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.
Timing diagrams for discrepancy errors at sensor pair 1 or interruption of the light curtain (if MUTING
is not active)
1 2
)5((
06B W
06B
06B
06B
W ',6&7,0 W',6&7,0 3
Wุ',6&7,0 3 W7,0(B0$;
$&.
087,1*
4
)$8/7
$&.B5(4
① Sensor pair 1 (MS_11 and MS_12) is not activated within discrepancy time
DISCTIM1.
② The light curtain is interrupted even though the MUTING function is not active.
③ Acknowledgment
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.
Structure of DIAG
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
087,1*
087,1*
(1
7DJ,QB 06B
7DJ,QB 06B
7DJ,QB 06B
7DJ,QB 06B
7DJ,QB 6723
7DJ,QB )5(( 4 7DJ2XWB
087,1*
087,1*
(1 (12
7DJ,QB 06B 4 7DJ2XWB
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. 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., MUT_P_DB_1) or a multi-instance (e.g., MUT_P_Instance_1) for the "Parallel
muting" instruction. Following the creation step, you will 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 Professional.
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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:
Schematic sequence of error-free muting procedure with 4 muting sensors (MS_11, MS_12, MS_21,
MS_22)
1
06B 6HQGHU 06B 'DQJHU
DUHD
● 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 or QBAD_O_xx signal of the associated F-I/O or
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).
2
06B 6HQGHU 06B 'DQJHU
DUHD
● 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).
3
06B 6HQGHU 06B 'DQJHU
DUHD
● 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).
4
06B 6HQGHU 06B 'DQJHU
DUHD
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
direction and the muting sensors are thus activated by the product in reverse order.
06B
W',6&7,0
06B
W',6&7,0 W',6&7,0
06B
W',6&7,0
06B
W',6&7,0
W',6&7,0
W',6&7,0 W',6&7,0
W7,0(B0$;
$&.
087,1*
)$8/7
$&.B5(4
06B 5HFHLYHU
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 (at least one muting sensor is activated and ENABLE = 1)
Enable signal Q becomes 1 again, if:
● Errors, if present, 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 signals that FREE is necessary for error elimination and
for removal of the restart inhibit. Once FREE has occurred, the instruction resets ACK_REQ
to 0.
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)
Timing diagrams for discrepancy errors at sensor pair 1 or interruption of the light curtain (MUTING is
not active)
1 2
)5((
06B
06B
06B
06B
W ',6&7,0 4
3
WV
$&.
087,1*
4
)$8/7
$&.B5(4
(1$%/(
① 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
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)
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
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
087B3
087B3
(1
7DJ,QB 06B
7DJ,QB 06B
7DJ,QB 06B
7DJ,QB 06B
087B3
087B3
(1 (12
7DJ,QB 06B 4 7DJ2XWB
7DJ,QB 06B 087,1* 7DJ2XWB
7DJ,QB 06B $&.B5(4 7DJ2XWB
)$8/7 7DJ2XWB
7DJ,QB 06B
',$*
7DJ,QB 6723
7DJ,QB 7DJ,QB )5((
(1$%/(
)B)'2['&9B4%$'BB 4%$'B087
7DJ,QB
7DJ,QB$&. $&.
7PV ',6&7,0
7PV ',6&7,0
7V 7,0(B0$;
13.3.3.6 EV1oo2DI: 1oo2 evaluation with discrepancy analysis (STEP 7 Safety Advanced V11)
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.
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.,
OB35) 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. 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., EV1oo2DI_DB_1) or a multi-instance (e.g.,
EV1oo2DI_Instance_1) for the "1oo2 evaluation with discrepancy analysis" instruction.
Following the creation step, you will 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
Professional.
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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:
Example
For nonequivalent signals, you have to invert the input (IN1 or IN2) to which you have
assigned the sensor signal with a safe state of 1. You must also OR the sensor signal with
the QBAD or QBAD_I_xx tag of the associated F-I/O DB or channel, so that a signal state of
0 is present at input IN1 or IN2 (after inversion) if fail-safe values are output.
Network1: EV1oo2DI with nonequivalent signals
(9RR',
(9RR',
6HQVRUBB12 ! (1
"Sensor_1_(NC)" ,1 4 "7DJ2XWB"
)%B',['&94%$' ,1 $&.B5(4 "7DJ2XWB"
7PV ',6&7,0( ',6&B)/7 "7DJ2XWB"
758( $&.B1(& ',$*
"7DJ,QB$&." $&. (12
(9RR',
(9RR',
(1 (12
6HQVRUBB "Sensor_1_(NC)" 4
,1 "7DJ2XWB"
12
127 ,1 $&.B5(4 "7DJ2XWB"
7PV ',6&7,0( ',6&B)/7 "7DJ2XWB"
)%B',[
'&94%$' 758( $&.B1(& ',$*
"7DJ,QB$&." $&.
,1
,1
',6&B)/7
$&.B5(4
$&.
',$*%LW
',$*%LW
',6&7,0( ',6&7,0( ',6&7,0( ',6&7,0(
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 you 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.
Structure of DIAG
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
(9RR',
(9RR',
(1
"7DJ,QB" ,1 4 "7DJ2XWB"
(9RR',
(9RR',
(1 (12
"7DJ,QB" ,1 4 "7DJ2XWB"
"7DJ,QB" ,1 $&.B5(4 "7DJ2XWB"
7PV ',6&7,0( ',6&B)/7 "7DJ2XWB"
758( $&.B1(& ',$*
"7DJ,QB$&." $&.
Description
This instruction implements feedback monitoring.
To do this, the signal state of the output Q is checked for equality with 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 error from being detected and an acknowledgment from being required
when the F-I/O controlled by output Q are passivated, you must supply input QBAD_FIO with
the QBAD or QBAD_O_xx tag of the associated F-I/O.
Every call of the "Feedback monitoring" 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., FDBACK_DB_1) or a multi-instance (e.g., FDBACK_Instance_1) for the
"Feedback monitoring" instruction. Following the creation step, you will 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 Professional.
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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:
Interconnection example
)'2
1
3 9'&
3 2
0 . ',
.
① Standard DI
② Input FEEDBACK
③ Output Q
Instruction versions
Two versions are available for this instruction:
● Version 1.0
When projects that were created with S7 Distributed Safety V5.4 SP5 are migrated,
Version 1.0 of the instruction is used automatically.
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.
If you want to compile a migrated safety program with STEP 7 Safety Advanced V11 for
the first time, we recommend that you update the version of the FDBACK instruction to
Version 1.1 beforehand. You will then avoid number conflicts.
● Version 1.1
When a new project is created with STEP 7 Safety Advanced V11, Version V1.1 is preset
automatically. This version is functionally identical to Version V1.0, but does not require
the F_TOF block to have a particular number.
For more information on the use of instruction versions, refer to the help on STEP 7
Professional under "Using instruction versions".
Startup characteristics
After an F-system startup, the instruction does not have be acknowledged when no errors
are present.
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
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
)'%$&.
)'%$&.
(1
7DJ,QB 21
7DJ,QB )(('%$&. 4 7DJ2XWB
)B)'2['&9B4%$'BB 4%$'B),2 (5525 7DJ2XWB
758( $&.B1(& $&.B5(4 7DJ2XWB
7DJ,QB$&. $&. ',$*
7PV )'%B7,0( (12
)'%$&.
)'%$&.
(1 (12
7DJ,QB 21 4 7DJ2XWB
7DJ,QB )(('%$&. (5525 7DJ2XWB
)B)'2['&9B4%$'BB 4%$'B),2 $&.B5(4 7DJ2XWB
758( $&.B1(& ',$*
7DJ,QB$&. $&.
7PV )'%B7,0(
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 must supply inputs QBAD_IN1 or QBAD_IN2 with
the QBAD or QBAD_I_xx tag of the associated F-I/O or 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. 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., SFDOOR_DB_1) or a multi-instance (e.g., SFDOOR_Instance_1) for the
"Safety door monitoring" instruction. Following the creation step, you will 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 Professional.
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:
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.
6DIHW\GRRURSHQ
23(1
)',
96
6DIHW\GRRU
,1 &/26('
',
3RVLWLRQ
VZLWFK
DFWXDWHG
96
,1
',
3RVLWLRQ
VZLWFK
QRW
DFWXDWHG
6DIHW\GRRUFORVHG
23(1
)',
96
&/26('
,1
',
3RVLWLRQ 6DIHW\GRRU
VZLWFK
QRW
DFWXDWHG
96
,1
',
3RVLWLRQ
VZLWFK
DFWXDWHG
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 acknowledgement 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
Example
The following example shows how the instruction works:
6)'225
6)'225
(1
7DJ,QB ,1
7DJ,QB ,1
)B)',['&9B4%$'B,B 4%$'B,1
)B)',['&9B4%$'B,B 4%$'B,1 4 7DJ2XWB
758( 23(1B1(& $&.B5(4 7DJ2XWB
758( $&.B1(& ',$*
7DJ,QB$&. $&. (12
6)'225
6)'225
(1 (12
7DJ,QB ,1 4 7DJ2XWB
13.3.3.9 ACK_GL: Global acknowledgment of all F-I/O in an F-runtime group (STEP 7 Safety
Advanced V11)
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 99) with a positive edge at input ACK_GLOB is required for
reintegration. The acknowledgement occurs analogously to the user acknowledgment via the
ACK_REI tag of the F-I/O DB (Page 79), 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 for 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. 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., 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. Following the creation step, you will 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 Professional.
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:
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.
Example
The following example shows how the instruction works:
$&.B*/
$&.B*/
(1
"7DJ,Q" $&.B*/2% (12
$&.B*/
$&.B*/
(1 (12
"7DJ,Q" $&.B*/2%
Description
You can use the "Generate pulse" instruction to set output Q for an assigned period. The
instruction is started if the result of logic operation (RLO) changes from "0" to "1" (positive
signal edge) at input IN. The assigned 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.
The current time value can be queried at 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 for this reason
when the instruction is inserted in the program; in it 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 you have created the data block, you will 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 Professional.
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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)
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:
When a call is made with PT = 0 ms, the TP instance is not reset completely (initialized).
The instruction behaves in accordance with the timing diagrams: only 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.
A call with PT < 0 ms resets outputs Q and ET. 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:
Timing diagrams TP
,1
4
37 37 37
(7
37
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
)B,(&B7LPHUB'%
73
7,0(
7DJ,QB ,1 (7 7DJB(7
7DJ2XW
706 37 4
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 sequence of operand "TagIn_1".
Operand "TagOut" at output Q has signal state "1" as long as the period is running. Operand
"Tag_ET" contains the current time value.
Description
You can use the "Generate on-delay" instruction to delay the setting of output Q by the
assigned period PT. The "Generate on-delay" instruction is started when the result of logic
operation (RLO) at input IN changes from "0" to "1" (positive signal edge). The assigned
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 start input is set to signal state "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.
The current time value can be queried at 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 for this reason
when the instruction is inserted in the program; in it 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 you have created the data block, you will 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 Professional.
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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)
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:
When a call is made with PT = 0 ms, the instance of the TON is not reset completely
(initialized). The instruction behaves in accordance with the timing diagrams: only output
ET is reset. To restart the on-delay, a new rising signal edge at input IN is required once
PT is greater than 0 again.
A call with PT < 0 ms resets outputs Q and ET. To restart 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:
Pulse diagram
,1
4 37 37
(7
37
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
)B,(&B7LPHUB'%
721
7,0(
7DJ,QB ,1 (7 7DJB(7
7DJ2XW
76 37 4
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 is set to signal state "1" when the period has elapsed and
remains set as long as operand "TagIn_1" still has signal state "1". Operand "Tag_ET"
contains the current time value.
Description
You can use the "Generate off-delay" instruction to delay resetting output Q by the assigned
period PT. Output Q is set if the result of logic operation (RLO) changes from "0" to "1"
(positive signal edge) at input IN. The assigned period PT starts when the signal state at
input IN changes back to "0". 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".
The current time value can be queried at output ET. The time value begins at T#0s and ends
when the value of period PT is reached.
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 for this reason
when the instruction is in inserted in the program; in it 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 you have created the data block, you will 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 Professional.
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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)
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:
When a call is made with PT = 0 ms, the instance of the TOF is not reset completely
(initialized). The instruction behaves in accordance with the timing diagrams: only 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.
A call with PT < 0 ms resets outputs Q and ET. 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:
Pulse diagram
,1
4
37 37
(7
37
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
)B,(&B7LPHUB'%
72)
7,0(
7DJ,QB ,1 (7 7DJB(7
7DJ2XW
706 37 4
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
"Tag_ET" contains the current time value.
Description
You can use the "Count up" instruction to increment the value at output CV. When the signal
state at input CU changes from "0" to "1" (positive signal edge), the instruction is executed
and the current count value at output CV is increased 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 output CV. When the high limit is reached, the signal state at input CU 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 for this reason when the
instruction is inserted in the program; in it 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 you have created the data block, you will 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 Professional.
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:
Example
The following example shows how the instruction works:
)B,(&B&RXQWHUB'%
&78
,17
ಯ7DJ,QBಯ &8
When the signal state of the "TagIn_1" operand changes from "0" to "1", the "Count up"
instruction is executed and the current count value of the "Tag_CV" operand is increased 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 parameter PV is used as the limit for the determination of output "TagOut".
Output "TagOut" has the signal state "1" as long as the current count value is greater than or
equal to the value of operand "Tag_PV". In all other cases, output TagOut has signal state
"0".
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 for this reason
when the instruction is inserted in the program; in it you can generate 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 you have created the data block, you will 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 Professional.
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:
Example
The following example shows how the instruction works:
)B,(&B&RXQWHUB'%
&7'
,17
ಯ7DJ,QBಯ &'
If the signal state of the "TagIn_1" operand changes from "0" to "1", the "Count down"
instruction is executed and the current count value at output "Tag_CV" is decreased 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 "TagOut" has the signal state "1" as long as the current count value is less than or
equal to zero. In all other cases, output TagOut has signal state "0".
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 input CU changes from "0" to "1" (positive signal
edge), the current count value at output CV is increased 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 decremented.
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 has 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 for this reason
when the instruction is inserted in the program; in it 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 you have created the data block, you will 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 Professional.
The operating system resets the instances of the "Count up and down" instruction on a
startup of the F-system.
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
)B,(&B&RXQWHUB'%
&78'
,17
ಯ7DJ,QB&8ಯ &8
ಯ7DJ,QB&'ಯ &'
If the signal state at input "TagIn_CU" or at input "TagIn_CD" changes from "0" to "1"
(positive signal edge), the "Count up and down" instruction is executed. When a positive
signal edge at input "TagIn_CU" is detected, the current count value of the "Tag_CV"
operand is increased by one. When a positive signal edge is detected at input "TagIn_CD",
the current count value at output "Tag_CV" is decreased by one. The count value is
increased on each positive signal edge at input CU until it reaches the high limit of 32767.
The count value is decreased on each positive signal edge at input CD until it reaches the
low limit of -32768.
Output "TagOut_GU" delivers the signal state "1" as long as the current count value is
greater than or equal to the value at input "Tag_PV". In all other cases, output TagOut_QU
has signal state "0".
Output "TagOut_QD" delivers the signal state "1" as long as the current count value is less
than or equal to zero. In all other cases, output TagOut_QD has signal state "0".
Description
Using the "Equal" instruction you can query whether the value at input IN1 is equal to the
value at input IN2.
If the condition of the comparison is fulfilled, the instruction returns result of logic operation
(RLO) "1". If the condition is not fulfilled, the instruction returns RLO "0".
Parameters
The following table shows the parameters of the instruction:
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:
,17
ಯ7DJB9DOXHಯ ,1 ಯ7DJ,QBಯ ಯ7DJ2XWಯ
ಯ7DJB9DOXHಯ ,1 6
Description
Using the "Not equal" instruction you can query whether the value at input IN1 is not equal to
the value at input IN2.
If the condition of the comparison is fulfilled, the instruction returns result of logic operation
(RLO) "1". If the condition is not fulfilled, the instruction returns RLO "0".
Parameters
The following table shows the parameters of the instruction:
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:
!
,17
ಯ7DJB9DOXHಯ ,1 ಯ7DJ,QBಯ ಯ7DJ2XWಯ
ಯ7DJB9DOXHಯ ,1 6
13.3.6.3 CMP >=: Greater than or equal (STEP 7 Safety Advanced V11)
Description
Using the "Greater or equal" instruction you can query whether the value at input IN1 is
greater than or equal to the value at input IN2. Both comparison values must be of the same
data type.
If the condition of the comparison is fulfilled, the instruction returns result of logic operation
(RLO) "1". If the condition of the comparison is not fulfilled, the instruction returns RLO "0".
Parameters
The following table shows the parameters of the instruction:
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:
!
,17
ಯ7DJB9DOXHಯ ,1 ಯ7DJ,QBಯ ಯ7DJ2XWಯ
ಯ7DJB9DOXHಯ ,1 6
13.3.6.4 CMP <=: Less than or equal (STEP 7 Safety Advanced V11)
Description
Using the "Less or equal" instruction you can query whether the value at input IN1 is less
than or equal to the value at input IN2. Both comparison values must be of the same data
type.
If the condition of the comparison is fulfilled, the instruction returns result of logic operation
(RLO) "1". If the condition of the comparison is not fulfilled, the instruction returns RLO "0".
Parameters
The following table shows the parameters of the instruction:
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:
,17
ಯ7DJB9DOXHಯ ,1 ಯ7DJ,QBಯ ಯ7DJ2XWಯ
ಯ7DJB9DOXHಯ ,1 6
Description
Using the "Greater than" instruction you can query whether the value at input IN1 is greater
than the value at input IN2. Both comparison values must be of the same data type.
If the condition of the comparison is fulfilled, the instruction returns result of logic operation
(RLO) "1". If the condition of the comparison is not fulfilled, the instruction returns RLO "0".
Parameters
The following table shows the parameters of the instruction:
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:
!
,17
ಯ7DJB9DOXHಯ ,1 ಯ7DJ,QBಯ ಯ7DJ2XWಯ
ಯ7DJB9DOXHಯ ,1 6
Description
Using the "Less than" instruction you can query whether the value at input IN1 is less than
the value at input IN2. Both comparison values must be of the same data type.
If the condition of the comparison is fulfilled, the instruction returns result of logic operation
(RLO) "1". If the condition of the comparison is not fulfilled, the instruction returns RLO "0".
Parameters
The following table shows the parameters of the instruction:
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:
,17
ಯ7DJB9DOXHಯ ,1 ಯ7DJ,QBಯ ಯ7DJ2XWಯ
ಯ7DJB9DOXHಯ ,1 6
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" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Note
If the result of the instruction is outside the range permitted for the data type, then the F-CPU
goes to STOP when the result is sent to an output at an F-I/O or to a partner F-CPU via
safety-related CPU-CPU communication.
One of the following diagnostic events is then
entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
You must therefore ensure that the permitted range for the data type is observed when
creating the program!
If this is not possible, 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 into it.
Note the following:
The result of the instruction behaves 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/134200)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Parameters
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:
Network 1:
$''
,17
(1
7DJB9DOXH ,1 287 7DJB5HVXOW
Network 2:
7DJ2XW
29 6
The "Add" instruction is always run (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 "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.
See also
OV: Get status bit OV (STEP 7 Safety Advanced V11) (Page 509)
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" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Note
If the result of the instruction is outside the range permitted for the data type, then the F-CPU
goes to STOP when the result is sent to an output at an F-I/O or to a partner F-CPU via
safety-related CPU-CPU communication.
One of the following diagnostic events is then
entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
You must therefore ensure that the permitted range for the data type is observed when
creating the program!
If this is not possible, 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 into it.
Note the following:
The result of the instruction behaves 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/134200)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Parameters
The following table shows the parameters of the instruction:
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:
Network 1:
68%
,17
(1
7DJB9DOXH ,1 287 7DJB5HVXOW
Network 2:
7DJ2XW
29 6
The "Subtract" instruction is always run (regardless of the signal state at enable input EN).
The value of operand "Tag_Value2" is subtracted from the value of operand "Tag_Value1".
The result of the addition is stored in operand "Tag_Result".
If 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.
See also
OV: Get status bit OV (STEP 7 Safety Advanced V11) (Page 509)
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" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Note
If the result of the instruction is outside the range permitted for the data type, then the F-CPU
goes to STOP when the result is sent to an output at an F-I/O or to a partner F-CPU via
safety-related CPU-CPU communication.
One of the following diagnostic events is then
entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
You must therefore ensure that the permitted range for the data type is observed when
creating the program!
If this is not possible, 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 into it.
Note the following:
The result of the instruction behaves 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/134200)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Parameters
The following table shows the parameters of the instruction:
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:
Network 1:
08/
,17
(1
7DJB9DOXH ,1 287 7DJB5HVXOW
Network 2:
7DJ2XW
29 6
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 "Tag_Result" operand.
If 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.
See also
OV: Get status bit OV (STEP 7 Safety Advanced V11) (Page 509)
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" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Note
If the result of the instruction is outside the range permitted for the data type, then the F-CPU
goes to STOP when the result is sent to an output at an F-I/O or to a partner F-CPU via
safety-related CPU-CPU communication.
One of the following diagnostic events is then
entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
You must therefore ensure that the permitted range for the data type is observed when
creating the program!
If this is not possible, 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 into it.
Note the following:
The result of the instruction behaves 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/134200)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Note
If the divisor (input IN2) of a DIV instruction = 0, the quotient of the division (result of division
at output OUT) = 0. The result behaves like the corresponding instruction in a standard
block. The F-CPU does not go to STOP mode. The behavior occurs regardless of whether a
"Get status bit OV" instruction has been inserted in the next network.
Parameters
The following table shows the parameters of the instruction:
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:
Network 1:
',9
,17
(1
7DJB9DOXH ,1 287 7DJB5HVXOW
Network 2:
7DJ2XW
29 6
The "Divide" instruction is always executed (regardless of the signal state at enable input
EN).
The value of operand "Tag_Value1" is divided by the value of operand "Tag_Value2". The
result of the division is stored in operand "Tag_Result".
If 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.
See also
OV: Get status bit OV (STEP 7 Safety Advanced V11) (Page 509)
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" and enable output "ENO" cannot be connected. The instruction is
therefore always executed (regardless of the signal state at enable input "EN").
Note
If the result of the instruction is outside the range permitted for the data type, then the F-CPU
goes to STOP when the result is sent to an output at an F-I/O or to a partner F-CPU via
safety-related CPU-CPU communication.
One of the following diagnostic events is then
entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
You must therefore ensure that the permitted range for the data type is observed when
creating the program!
If this is not possible, 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 into it.
Note the following:
The result of the instruction behaves 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/134200)).
A warning is issued if you do not insert a "Get status bit OV" instruction.
Parameters
The following table shows the parameters of the instruction:
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:
Network 1:
1(*
,17
(1 287 7DJ2XWB9DOXH
7DJ,QB9DOXH ,1 (12
Network 2:
7DJ2XW
29 6
The "Create twos 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
"TagOut_Value" operand.
If an overflow occurs during execution of the "Create twos 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.
See also
OV: Get status bit OV (STEP 7 Safety Advanced V11) (Page 509)
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 identical operand widths 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").
Parameters
Example
The following example shows how the instruction works:
029(
(1 287 7DJ2XWB9DOXH
7DJ,QB9DOXH ,1 (12
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 "TagOut_Value".
13.3.8.2 WR_FDB: Write value indirectly to an F-DB (STEP 7 Safety Advanced V11)
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 diagnostic event ID 75E2, check to determine if
this condition is fulfilled.
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
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:
:5B)'%
,17
(1
"7DJ,Q" ,1
")B'%".VAR_INT10 ,1,B$''5
")B'%".VAR_INT15 (1'B$''5
2))6(7 (12
13.3.8.3 RD_FDB: Read value indirectly from an F-DB (STEP 7 Safety Advanced V11)
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 diagnostic event ID 75E2, check to determine if
this condition is fulfilled.
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 Advanced V11)
(Page 485).
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
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:
5'B)'%
,17
(1
")B'%".VAR_INT10 ,1,B$''5
")B'%".VAR_INT15 (1'B$''5 287
2))6(7 (12
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 output OUT.
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:
Example
The following example shows how the instruction works:
&219
,17 WR ',17
(1 287 7DJ2XWB9DOXH
7DJ,QB9DOXH ,1 (12
The instruction is always executed regardless of the signal state at enable input "EN". The
content of the operand "TagIn_Value" is read and converted to a double integer (32 bit). The
result is stored in operand "TagOut_Value".
13.3.9.2 BO_W: Convert 16 data elements of data type BOOL to a data element of data type
WORD (STEP 7 Safety Advanced V11)
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").
Note: To supply inputs IN0 to IN15 with Boolean constants "0" and "1", you can access tags
"VKE0" and "VKE1" in the F-shared DB using a fully-qualified DB access
("F_GLOBDB".VKE0 or "F_GLOBDB".VKE1).
Parameters
Example
The following example shows how the instruction works:
%2B:
(1
7DJ9DOXHB ,1
7DJ9DOXHB ,1
The following table shows how the instruction works using specific operand values:
The values of operands "TagValue_0" to " TagValue_15" are combined to form data type
WORD and assigned to operand "TagResult".
13.3.9.3 W_BO: Convert a data element of data type WORD to 16 data elements of data type
BOOL (STEP 7 Safety Advanced V11)
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" or enable output "ENO" cannot be connected. The instruction is therefore
always executed (regardless of the signal state at enable input "EN").
Parameters
Example
The following example shows how the instruction works:
:B%2
287 7DJ2XWB
287 7DJ2XWB
287 7DJ2XWB
(1 287 7DJ2XWB
7DJ9DOXH ,1 (12
The following table shows how the instruction works using specific operand values:
The value of operand "TagValue" of data type WORD is converted to the 16 values
"TagOUT_0" to "TagOUT_15" of data type BOOL.
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. The "Call options" dialog is automatically opened for this reason
when the instruction is inserted in the program; in it 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 you have created the data block, you will 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 Professional.
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
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
7FFFH (for overflow) or 8000H (for underflow) in the PII for the safety program.
If other fail-safe values are to be output in this case, you must evaluate the QBAD tag in the
F-I/O DB (branch to output of an individual fail-safe value).
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 output of an individual fail-safe value by evaluating outputs
OUT_HI and OUT_LO, respectively.
Example
The following example shows how the instruction works:
6&$/(
(1 287 7DJ2XWB9DOXH
7DJ,QB9DOXH ,1 287B+,
+,B/,0 287B/2
/2B/,0 (12
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 495) (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
You are not permitted to program a SENDDP or SENDS7 call between a jump instruction
and the associated destination of the jump instruction.
Example
The following example shows how the instruction works:
1HWZRUN
&$6
ಯ7DJ,QBಯ -03
1HWZRUN
ಯ7DJ2XWBಯ
ಯ7DJ,QBಯ 5
1HWZRUN
&$6
ಯ7DJ2XWBಯ
ಯ7DJ,QBಯ 5
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.
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 495)
(LABEL). The designation of the jump label is specified in the placeholder above the
instruction box.
The specified jump label must be in the same instruction in which the instruction is executed.
The name you specify can only occur once in the instruction.
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
You are not permitted to program a SENDDP or SENDS7 call between a jump instruction
and the associated destination of the jump instruction.
Example
The following example shows how the instruction works:
1HWZRUN
&$6
ಯ7DJ,QBಯ -031
1HWZRUN
ಯ7DJ2XWBಯ
ಯ7DJ,QBಯ 5
1HWZRUN
&$6
ಯ7DJ2XWBಯ
ಯ7DJ,QBಯ 5
When operand "TagIn_1" has signal state "0", instruction "Jump if RLO = 0" 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.
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:
1HWZRUN
&$6
ಯ7DJ,QBಯ -03
1HWZRUN
ಯ7DJ2XWBಯ
ಯ7DJ,QBಯ 5
1HWZRUN
&$6
ಯ7DJ2XWBಯ
ಯ7DJ,QBಯ 5
When operand "TagIn_1" has signal state "1", the "JMP: 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 Advanced V11) (Page 493)
JMPN: Jump if RLO = 0 (STEP 7 Safety Advanced V11) (Page 494)
RET: Return (STEP 7 Safety Advanced V11) (Page 496)
Description
You can use the "Return" operation to stop the processing of a block.
If the result of logic operation (RLO) at the input of the "Return" instruction is "1", 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.
Note
You must not program a "Return" instruction in the Main Safety Block.
Example
The following example shows how the instruction works:
ಯ7DJ,QBಯ !
5/2
ಯ7DJ,QBಯ 5(7
If either the "TagIn_1" or "TagIn_2" operand has the signal state "1", the "Return" instruction
is executed. Program execution in the called block is terminated and continues in the calling
block. Output ENO of the call function is reset to signal state "1".
See also
LABEL: Jump label (STEP 7 Safety Advanced V11) (Page 495)
JMPN: Jump if RLO = 0 (STEP 7 Safety Advanced V11) (Page 494)
JMP: Jump if RLO = 1 (STEP 7 Safety Advanced V11) (Page 493)
13.3.10.5 OPN: Open global data block (STEP 7 Safety Advanced V11)
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 for 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" instruction, you must ensure that the DB
register is restored by repeating the "Open global data block" instruction after 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:
Example
The following example shows how the instruction works:
Network 1
0RWRUB'%
231
Network 2
7DJB2XWSXW
'%;
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.
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:
Example
The following example shows how the instruction works:
$1'
:25'
(1
7DJB9DOXH ,1 287 7DJB5HVXOW
7DJB9DOXH ,1 (12
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 "Tag_Result" operand.
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").
Parameters
The following table shows the parameters of the instruction:
Example
The following example shows how the instruction works:
25
:25'
(1
7DJB9DOXH ,1 287 7DJB5HVXOW
7DJB9DOXH ,1 (12
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 "Tag_Result" operand.
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:
Example
The following example shows how the instruction works:
;25
:25'
(1
7DJB9DOXH ,1 287 7DJB5HVXOW
7DJB9DOXH ,1 (12
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
"Tag_Result" operand.
Description
You can use the "Shift right" instruction to move the content of the operand at input IN bit-by-
bit to the right and query the result at output OUT. You use parameter N (low-byte) to specify
the number of bit positions by which the specified value is moved.
When the value at parameter N (low-byte) is "0", the value at input IN is copied into the
operand at output OUT.
When the value at parameter N (low-byte) is greater than the number of available bit
positions, the operand value at input IN is moved by the available number of bit positions to
the right.
The bit locations that are freed up in the left 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 right:
1 SRVLWLRQV
287
7KHELWORFDWLRQVWKDW 7KHVHVL[ELWVZLOO
DUHIUHHGXSDUHILOOHG EHORVW
ZLWK]HURV
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:
Example
The following example shows how the instruction works:
6+5
:25'
(1
7DJ,QB9DOXH ,1 287 7DJ2XWB9DOXH
7DJB1XPEHU 1 (12
The following table shows how the instruction works using specific operand values:
N Tag_Number 3
OUT TagOut_Value 0000 0111 1111 0101
The content of the operand "TagIn_Value" is moved three bit positions to the right. The result
is output at output "TagOut_Value".
Description
You can use the "Shift left" instruction to move the content of the operand at input IN bit-by-
bit to the left and query the result at output OUT. You use parameter N (low-byte) to specify
the number of bit positions by which the specified value is moved.
When the value at parameter N (low-byte) is "0", the value at input IN is copied into the
operand at output OUT.
When the value at parameter N (low-byte) is greater than the number of available bit
positions, the operand value at input IN is moved by the available number of bit positions to
the left.
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:
1 SRVLWLRQV
287
7KHVHVL[ELWVZLOO 7KHELWORFDWLRQVWKDW
EHORVW DUHIUHHGXSDUHILOOHG
ZLWK]HURV
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:
Example
The following example shows how the instruction works:
6+/
:25'
(1
7DJ,QB9DOXH ,1 287 7DJ2XWB9DOXH
7DJB1XPEHU 1 (12
The following table shows how the instruction works using specific operand values:
N Tag_Number 4
OUT TagOut_Value 1111 1010 1111 0000
The content of the operand "TagIn_Value" is moved four bit positions to the left. The result is
output at output "TagOut_Value".
13.3.13 Operating
Description
This instruction enables fail-safe acknowledgment from an operator control and monitoring
system. It allows, for example, reintegration of F-I/O to be controlled from the operator
control and monitoring system. Acknowledgment takes place in two steps:
● In/out parameter IN changes to a value of 6.
● In/out parameter IN changes to a value of 9 within 1 minute.
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 1 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 9 within 1 minute or
the change occurred before 1 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 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 for
this reason when the instruction is inserted in the program; in it 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 you have created the data block, you will
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 Professional.
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 mode if the information above is not observed. One of the
following diagnostic events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
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 100 ms, a maximum of 20% of the (assigned) time value
– For time values greater than or equal to 100 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
You can read out output Q by means of operator control and monitoring systems or, if
applicable, you can evaluate it in your standard user program.
You can supply in/out parameter IN with just a memory word or nothing at all. In the safety
program, read and write access to in/out parameter IN in the associated instance DB is not
permitted!
Parameters
Timing imprecision resulting from the update time of the time base used in the instruction:
7 1 2
7%DVHB 7%DVHB
3
7LPHEDVHXSGDWH
&DOOWLPHRIDQLQVWUXFWLRQZLWKWLPHSURFHVVLQJ
① 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 portions of the safety
program 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 into account 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 prior to the time of the instruction call 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:
$&.B23
$&.B23
(1 287 7DJ2XW
,1 4
(12
See also
Implementing User Acknowledgment in the Safety Program of the F-CPU of a DP Master or
IO Controller (Page 99)
Implementing user acknowledgment in the safety program of the F-CPU of a I-slave or I-
device (Page 102)
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.
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/134200)).
Example
The following example shows how the instruction works:
Network 1:
$''
,17
(1
7DJB9DOXH ,1 287 7DJB5HVXOW
Network 2:
7DJ2XW
29 6
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 "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.3.15 Communication
13.3.15.1 PROFIBUS/PROFINET
SENDDP and RCVDP: Send and receive data via PROFIBUS DP/PROFINET IO (STEP 7 Safety
Advanced V11)
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
Description
The SENDDP instruction sends 16 data elements of data type BOOL and 2 data elements of
data type INT 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. 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.,
RCVDP_DB_1) or a multi-instance (e.g., RCVDP_Instance_1) for this instruction. Following
the creation step, you will 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 Professional.
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.
With the RCVDP instruction, the data received are available at output RD_BO_xx or RD_I_xx
for additional processing by other F-blocks/instructions.
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 deactivated safety mode,
output SENDMODE = 1.
WARNING
The value for each address relationship (input parameter DP_DP_ID; data type: INT) is
user-defined; however, it must be unique from all other safety-related communication
connections in the network. The uniqueness must be checked in the print-out of the safety
program during acceptance testing of the safety program. Additional information can be
found in Auto-Hotspot.
You must supply inputs DP_DP_ID and LADDR with constant values when calling the
instruction. Direct read or write access to the associated instance DB is not permitted in the
safety program! (S016)
Note
Within a safety program, you must assign a different start address 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.
The input and output parameters of the RCVDP instruction must not be supplied with
temporary or static local data of the main safety block.
The input parameters of the RCVDP instruction must not be initialized with output
parameters (using fully qualified DB accesses) of a RCVDP or RCVS7 instruction called in a
preceding network.
You must not use an actual parameter for an output parameter of a RCVDP, if it is already
being used for an input parameter of the same or another RCVDP or RCVS7 instruction. The
F-CPU can go to STOP if this is not observed. One of the following diagnostic events is then
entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You must not program any SENDDP instruction between a JMP or JMPN instruction and the
associated destination network of the JMP or JMPN instruction.
You must not program any RET instruction before a SENDDP instruction.
Placement
The RCVDP instruction must be inserted at the start of the main safety block and the
SENDDP instruction at the end.
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 SUBBI_xx.
The SENDDP and RCVDP instructions signal this at output SUBS_ON with 1. Output
SENDMODE has a default of 0 and is not updated, as long as output SUBS_ON = 1.
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) 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 RCVDP instructions, and the
bus connection. You also obtain information on possible error causes by evaluating outputs
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.
6(1'B'3
(5525
68%621
5&9'3
$&.B5(,
$&.B5(4
(5525
68%6B21
&RPPXQLFDWLRQHUURU $FNQRZOHGJPHQWRQ
GHWHFWHGE\5&9'3 5&9'3
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.
See also
Configuring and Programming Communication (Page 111)
Correctness of the communication configuration (Page 208)
Implementation of user acknowledgment (Page 99)
Safety-related IO controller-IO controller communication (Page 114)
Safety-related master-master communication (Page 122)
Safety-related communication between I/O-controller and I-device (Page 130)
Safety-related master-I-slave communication (Page 136)
Safety-related IO Controller-I-slave communication (Page 154)
Communication with S7 Distributed Safety via PN/PN coupler (IO Controller-IO Controller
communication) (Page 162)
Communication with S7 Distributed Safety via DP/DP coupler (master-master
communication) (Page 163)
13.3.15.2 S7 communication
SENDS7 and RCVS7: Communication via S7 connections (STEP 7 Safety Advanced V11)
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 V11, 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 Auto-
Hotspot.
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 for this reason when the instruction
is inserted in the program; in it 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
you have created the data block, you will 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 Professional.
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 "Safety-related communication via
S7 connections (Page 155)".
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
deactivated safety mode, then output SENDMODE = 1.
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.
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 each address relationship (input parameter R_ID; data type: DWORD) is
user-defined; however, it must be an odd number and be unique from all other safety-
related communication connections in the network. 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)
Note
A separate instance DP 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 input and output parameters of the RCVS7 instruction must not be initialized with
temporary or static local data of the main safety block.
The input parameters of the RCVS7 instruction must not be initialized with output parameters
(using fully qualified DB accesses) of a RCVS7 or RCVDP instruction called in a preceding
network.
You must not use an actual parameter for an output parameter of an RCVS7 instruction, if it
is already being used for an input parameter of the same or another RCVS7 or RCVDP
instruction. The F-CPU can go to STOP if this is not observed. One of the following
diagnostic events is then entered in the diagnostic buffer of the F-CPU:
"Data corruption in the safety program prior to output to F-I/O"
"Data corruption in the safety program prior to output to partner F-CPU"
"Safety program: internal CPU fault; internal error information: 404"
Note
You must not program any SENDS7 instruction between a JMP or JMPN instruction and the
associated destination network of the JMP or JMPN instruction.
You must not program a RET instruction prior to a SENDS7 instruction.
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 at output SUBS_ON with 1. Output
SENDMODE (RCVS7 instruction) has a default of 0 and is not updated, as long as output
SUBS_ON = 1.
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, parameter assignment of the SENDS7 and 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.
6(1'6
(5525
68%621
5&96
$&.B5(,
$&.B5(4
(5525
68%6B21
&RPPXQLFDWLRQHUURU $FNQRZOHGJPHQWRQ
GHWHFWHGE\5&96 5&96
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.
Structure of DIAG
See also
Configuration (Page 25)
Additional information
The monitoring and response times for the standard portion are calculated in SIMATIC
Safety in exactly the same way as for standard S7-300 and S7-400 automation systems and
are not addressed here. For a description of this calculation, refer to the hardware manuals
for the CPUs.
You do not have to configure the monitoring time for safety-related communication between
F-runtime groups.
WARNING
It can only be ensured (from a fail-safe standpoint) that a signal level to be transferred will
be captured on the sender side and transferred to the receiver if the signal level is pending
for at least as long as the assigned F-monitoring time. (S018)
A.1.2 Minimum monitoring time for safety-related communication between F-CPU and
F-I/O
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 minimum 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 additional 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
checked 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 after 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.
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.
Checklist
Legend:
● Stand-alone chapter 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 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.
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).
Category
Category as defined by EN 954-01
With SIMATIC Safety, use in → safety mode up to category 4 is possible.
Channel fault
Channel-related fault, such as a wire break or short circuit.
Collective F-signatures
The collective F-signatures uniquely identify a particular state of the → safety program and
the safety-related parameters of the F-CPU and F-I/O. They are important for the preliminary
acceptance test of the safety program, e.g., by → experts.
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.
Depassivation
→ Reintegration
Discrepancy analysis
Discrepancy analysis for equivalence or nonequivalence is used for fail-safe inputs to
determine errors based on 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 (for nonequivalence testing, when identical levels are detected). On expiration
of an assignable period (→ discrepancy time), a check is made to determine whether the
difference in levels has disappeared (for nonequivalence testing, whether the identicalness
of the levels has disappeared). If not, there is a discrepancy error. The discrepancy analysis
is performed between the two input signals of the 1oo2 sensor evaluation (→ 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).
Fail-safe modules
ET 200S, ET 200pro, and ET 200iSP modules that can be used for safety-related operation
(→ safety mode) in the ET 200S, ET 200pro, or ET 200iSP distributed I/O systems. These
modules are provided with integrated → safety functions. They operate in accordance with
IEC 61784-1: 2007 (fieldbus profile) and CP 3/3 and the PROFIsafe bus profile in
accordance with IEC 61784-3-3: 2007.
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.
F-Attribute
All → F-blocks that belong to a → safety program are provided with an F-attribute. Only the
blocks of the -> safety program have the F-attribute after the -> safety program is
successfully compiled.
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 shared 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-communication DBs
Fail-safe data blocks for the safety-related CPU-CPU communication via S7 connections.
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.
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-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-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
● → S7-300 fail-safe signal modules
● → Fail-safe modules for ET 200S
● → Fail-safe modules for ET 200pro
● → Fail-safe modules for ET 200iSP
● → Fail-safe DP standard slaves
● → Fail-safe standard I/O devices
F-I/O DB
Fail-safe data block for an → F-I/O in STEP 7 Safety Advanced V11. 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 F-I/O after communication errors, F-I/O faults, or channel faults
● If F-I/O are to be passivated as a result of particular safety program statuses (for example,
group passivation)
● For reassignment of parameters for fail-safe DP standard slaves/standard I/O devices or
enabling HART communication for the F-I/O with the corresponding functionality
● For evaluation of 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-modules
-> Fail-safe modules
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, if necessary → F-FBs/ → F-FCs, if necessary → F-DBs, → F-I/O DBs, F-
blocks of shared libraries, instance DBs, → F-SBs, and → automatically generated F-blocks.
F-SBs
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-shared DB
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-systems
→ Fail-safe systems
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.
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 DP standard slaves and → fail-safe standard I/O devices
I-slave
An "I-slave (intelligent DP slave) is a signal preprocessing field device. One its features is
that that the I/O area available for the DP master does not correspond to an actually
available I/O, but rather an I/O area that is imaged by a preprocessing CPU.
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) according to ISO 13849-1: 2006 or in accordance with EN ISO
13849-1: 2008
With SIMATIC Safety, use up to Performance Level (PL) e is possible in → safety mode.
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/PA and PROFINET IO according to IEC
61784-3-3: 2007 for communication between the → safety program and the → F-I/O in an →
F-system.
PROFIsafe address
The PROFIsafe addresses are used to uniquely identify the source and destination. For this
reason, every → F-I/O has two PROFIsafe addresses: a source address and a destination
address. The PROFIsafe source address is automatically assigned and is not displayed for
F-modules (except standard devices). You must configure the PROFIsafe destination
address in the hardware and network editor and set this address on the F-I/O via a switch.
Program signature
→ Collective F-signature
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
● Parameter assignment in the > F-I/O DB
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.
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
entirely in STEP 7 Professional, you do not require 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 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)
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 fault detection and reaction are activated. In safety mode, the safety
program cannot be modified during operation. Safety mode can be deactivated by the
user (→ deactivated safety mode).
Safety program
Safety-related user program
Safety protocol
→ Safety message frame
Safety-related communication
Safety-related communication is used to exchange fail-safe data.
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
Signature
→ F-collective signatures
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.
Startup of F-system
When an → F-CPU is switched from STOP to RUN mode, the standard user program starts
up in the normal way. When the → safety program is started up, all data blocks with an → F-
attribute 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.
AND, 374
Assignment, 227, 379
EXCLUSIVE OR, 377
= Insert binary input, 372
Invert RLO, 226, 373
=, 379 Normally closed contact, 225
Normally open contact, 224
OR, 376
A Reset output, 228, 380
Acceptance test Reset/set flip-flop, 232, 385
of safety-related changes, 210 Scan operand for negative signal edge, 236, 389
of system, 201 Scan operand for positive signal edge, 234, 387
Acceptance test for safety-relevant changes, 210 Scan RLO for negative signal edge, 239, 393
Access Scan RLO for positive signal edge, 237, 391
To tags of F-I/O DB, 88 Set output, 229, 381
Access permission Set/reset flip-flop, 230, 383
Canceling, 54 Bit memory, 105
Setting up for the safety program, 51 Block size of automatically generated F-blocks, 177
Setup for F-CPU, 54 BO_W, 332, 488
Validity, 51, 54
Access protection, 49
ACK_GL, 295, 451 C
ACK_NEC, 82 Category, 17
ACK_OP, 351, 506 Change
ACK_REI, 82 Acceptance test, 210
ACK_REQ, 82 Detecting, 210
Acknowledgment of the safety program in RUN mode, 197
Fail-safe, 351, 506 Changing
Activating Data of the safety program, 193
F-capability, 29 Channel fault, 33, 94
Safety mode, 191 Checking the program version, 209
Activating/deactivating F-capability, 29 Checklist, 529
Add, 317, 474 CMP <, 316, 473
ADD, 317, 474 CMP <=, 314, 471
Address assignment CMP <>, 312, 469
F-destination address, 36 CMP ==, 311, 468
AND, 344, 374, 499 CMP >, 315, 472
Approvals, 4 CMP >=, 313, 470
Assignment, 227, 379 Code review of the safety program, 202
Communication
Monitoring time, 526, 527
B Standard user program and safety program, 105,
Basis for PROFIsafe addresses, 30, 34 108
Behavior Communication error, 92, 356, 510
After communication errors, 92 SENDDP/RCVDP, 356, 510
After F-I/O faults or channel faults, 94 Comparator operations
After startup, 90 Equal, 311, 468
Bit logic operation Greater or equal, 313, 470
M O
Main safety block, 58, 73
Off delay, 303, 459
Math functions
Offline password, 51
Add, 317, 474
Offline-online comparison of safety programs, 183
Create twos complement, 325, 482
On delay, 300, 456
Divide, 323, 480
Online password, 51
Multiply, 321, 478
Open global data block, 497
Subtract, 319, 476
Operand
Maximum cycle time, 524, 528
Scan for negative signal edge, 236, 389
Memory Card, 178
Scan for positive signal edge, 234, 387
Memory reset, 178, 193
Operand area
Migrating projects
For safety program, 60
from S7 Distributed Safety, 22
Operating principle
Migration
RCVDP, 356, 510
from S7 Distributed Safety, 22, 158
RCVS7, 363, 517
Printout, 188
SENDDP, 356, 510
Modifying, 189
SENDS7, 363, 517
Safety program, 196
Operating system update, 214
Monitoring, 189
Scan for positive signal edge, 237, 391 Safety-related CPU-CPU communication, 25, 111, 363,
RS, 232, 385 517
Rules for testing, 193 Checking for correctness, 208
RUN, 197 F-communication DB, 158
RUN mode, 197 Options, 25
RCVDP, 356, 510
Restrictions in RUN mode, 197
S SENDDP, 356, 510
Safety-related IO Controller-I-Device communication
S, 229, 381
Configuring, 130
S7 connection
Data transfer limits, 135
Safety-related communication, 155
Programming, 134
S7-PLCSIM, 176, 189, 193
Safety-related IO controller-IO controller
Safety Administration Editor, 39
communication
Safety function, 17
Date transfer limits, 121
Calculation of response time, 528
Safety-related IO Controller-IO Controller
Example, 17
communication
Safety functions
Configuring, 114
ACK_GL, 295, 451
Programming, 118
ESTOP1, 240, 395
Safety-related IO Controller-I-slave
EV1oo2DI, 276, 432
communication, 154
FDBACK, 283, 439
Safety-related I-slave-I-slave communication
MUT_P, 265, 421
Configuring, 143
MUTING, 254, 410
Data transfer limits, 142
SFDOOR, 289, 445
Programming, 140
TWO_H_EN, 249, 405
Safety-related I-slave-slave communication
TWO_HAND, 246, 401
Configuring, 148
Safety Integrity Level, 17
Data transfer limits, 153
Safety mode
Safety-related master-I-slave communication
Activating, 191
Configuring, 136
Deactivating, 190
Data transfer limits, 142
Safety printout, 187, 201
Programming, 140
Safety program, 18
Safety-related master-master communication
Allow automatic generation, 31
Configuring, 122
Comparing, 183
Date transfer limits, 129
Compiling, 169
Programming, 126
Deleting, 72, 199
Safety-related parameters, 28
Downloading, 171
Scale
Function test, 189
Values, 336, 491
Instructions, 58
SCALE, 336, 491
Modifying, 189, 196
SENDDP, 117, 118, 125, 126, 133, 134, 139, 140, 190,
Monitoring, 189, 196
356, 510
Output of fail-safe values, 80
Behavior in the event of communication errors, 356,
Password, 51
510
Structuring, 56
Sending data, 356, 510
Testing, 193
Structure of DIAG, 356, 510
Work memory requirement, 177
Timing diagrams, 356, 510
Safety requirements, 7, 17
Sending and receiving data via S7 connections, 363,
Safety-related communication between F-runtime
517
groups, 69
SENDS7, 157, 158, 190, 363, 517
Safety-related communication via S7 connections
Service & Support, 7
Configuring, 155
SFDOOR, 289, 445
Data transfer limits, 161
T W
Tag W_BO, 334, 490
F-I/O DB, 82 Wiring test, 193
Monitoring/modifying, 193 Word logic operations
Tag table, 193 AND, 344, 499
Testing of safety program, 193 EXCLUSIVE OR, 346, 501
X
X, 377
XOR, 346, 501