PCS 7 F-Systems

Process Safety

Architecture

Integration
Program Execution
Hardware Architecture
PROFIsafe

Copyright-2017

Seite 1
 PCS 7 F-Systems

Control System and Safety System

Systemsdesign
System Design ENG HMI SIMATIC S7-400FH ENG

Software Interfaced Gateway

ES Settings DCS Gateway SIS
Hardware
Settings
SIMATIC PCS
F-User ENG
7 ES & OS HMI SIMATIC S7-400FH
Program
Safety- Integrated
Mechanism
DCS SIS
SDW/MOS

Communication
SIMATIC PCSENG
7 HMI
SIMATIC S7-400FH
ES & OS
Common

DCS SIS
Std. I/O

Copyright-2017
Page 3

PCS 7 F-Systems

Systems Connected via Gateway

Systemsdesign
System Design Interfaced
 Higher Wiring Costs
Software
 Two Engineering Stations
ES Settings  Higher Engineering Costs
Hardware  Gateway Engineering F/PLS
Settings
 Configure Diagnostics separately
F-User
Program  Different HW, Network, Vendors and Responsible
Safety-
Mechanism

SDW/MOS
ES OS ES

Communication

PCS 7 Gateway SIS

Copyright-2017
Page 4

Seite 2
 PCS 7 F-Systems

Integrated Systems

Systemsdesign
System Design  1 Plant bus (direct Communication)
 1 ES
Software
 1 OS
ES Settings  minimized Effort for Engineering and Training
Hardware
Settings
 Equal HW Components
F-User
Program  Automatic Integration of Process Diagnostics
Safety-
Mechanism

SDW/MOS
ES OS

Communication

PCS 7 SIS (S7-F)

Copyright-2017
Page 5

PCS 7 F-Systems

Common

Systemsdesign
System Design  1 Plant bus (direct Communication)
 1 ES
Software
 1 OS
ES Settings  minimized Effort for Engineering and Training
Hardware
Settings
 Equal HW Components
F-User
Program  Automatic Integration of Process Diagnostics
Safety-  Common HW
Mechanism
 Partial Plant oriented Engineering
SDW/MOS
ES OS

Communication

PCS 7
SIS (S7-F)

Copyright-2017
Page 6

Seite 3
 PCS 7 F-Systems

Program Architecture

Systemsdesign
System Design
F-User Program
Standard-
Software
User F-User Blocks F-Control
Program Blocks
ES Settings F-Standard- F-System-
Blocks Blocks
Hardware Program Program
Settings Execution Execution
F-User
Program Communication Self tests

Safety-
Mechanism

SDW/MOS

Communication Safety-relevant sections of the operating system

Standard – OS F-Access Safety-relevant Safety-relevant
CPU Protection System Function. Self tests
Calls

Copyright-2017
Page 7

PCS 7 F-Systems

Assignment of PROFIsafe
 Standard and Fail Safe Program in one Control System
Systemsdesign
System Design  Communication with Fail Safe I/O Modules via PROFIsafe Protocol
Software  F-diagnostics will detect safety-related failures (RAM/CPU failure)
 Shut down-Logic is disabling F-Program
ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism
(PROFIsafe)
SDW/MOS F - I/O
ET200M
Communication S7-400H CPU (F)

I/O
Standard Program ET200M

F - I/O
Failsafe Program ET200S
Copyright-2017
Page 8

Seite 4
 PCS 7 F-Systems

PROFIsafe Communication

Systemsdesign
System Design A valid current frame must arrive at the CPU with a valid
consecutive number within a parameterizable monitoring time
Software

ES Settings
Master Slave 1 Master Slave 2 Master
Master Slave
Slave
4 3 Master Slave 4
Hardware Slave 1 Master Slave 2 Master Slave
Slave 34 Master
Master Slave 4 Master
Settings
F-User
Program
Master
Safety-
Mechanism
Failsafe- User data Status / CRC Consequent
SDW/MOS Monitor byte Number
Slave 1
Standard Via
Communication Source
F-User data
Slave 2 based
and
Counter
Standard F-Parameter

Slave 3
Max. 12 / 122 Bytes 1 Byte 3/4 Bytes *) 1 Byte
Failsafe
*) 3 Byte for max. 12 Byte F I/O data
Slave 4 4 Byte for max. 122 Byte F I/O data

Standard
Copyright-2017
Page 9

PCS 7 F-Systems

Failsafe Inputs

Systemsdesign
System Design  Discrepancy Test in the Module
 Evaluation of Test Signals
Software
1oo2 Vote in Module
ES Settings 2 Channels 2 Channels
Sensor supply Equivalent Non Equivalent
Hardware
Settings
F-User
Program Status
Data
Safety- uP 1
Mechanism CRC

SDW/MOS Test signal

Communication

uP 2

Input data

Copyright-2017
Page 10

Seite 5
 PCS 7 F-Systems

Failsafe Outputs

Systemsdesign
System Design  Read back the Output signals
 Intrusion of Test signals
Software
 Redundant disconnection facility
ES Settings

Hardware Status
Output Driver
Settings
F-User
Program M
uP 1
Safety-
Mechanism
Main switch
SDW/MOS
uP 2
Read back
Communication

Diagnostic

FAQ 40791595 : 2BF10 with two “diode” output/channel instead of one “diode” and one “non diode”
output. Copyright-2017
Page 11

PCS 7 F-Systems

Integrated Safety Communication

Systems Design
Systemdesign

Software

ES Settings

Hardware SIMATIC S7-300F

Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 12

Seite 6
 PCS 7 F-Systems

Remote I/Os in single Mode

Systemsdesign
System Design Overvoltage protection via ET 200M Separator module
AS 41X F
IM 153-2
Software
ET 200M
ES Settings
Standard-I/O
Hardware
Settings PROFIBUS-DP IM 153-2
F-User Copper
Program ET200M
Safety- SIL 2
Mechanism Failsafe-I/O

SDW/MOS
IM 153-2
Communication Separator Module IM 153-2
Separator Module
!

ET200M !

SIL 3 ET 200M ET200M

Failsafe-I/O
Standard-I/O Failsafe-I/O
Active Bus module for
Active Bus module for
Separator module
Separator module
Copyright-2017
Page 13

PCS 7 F-Systems

Remote I/Os in redundant Mode

Systemsdesign
System Design Overvoltage protection via ET200M Separator module
AS 41x FH

Software 2x IM 153-2

ES Settings

Hardware ET 200M
Settings Standard-I/O
F-User
Program
PROFIBUS-DP 2x IM 153-2
Safety- Copper
Mechanism

SDW/MOS
SIL 2
F-I/O
Communication
2x IM 153-2 2x IM 153-2
SIL 3 Separator Module Separator Module

! !
ET 200M ET200M

F-I/O Standard-I/O F-I/O

Active Bus module for Active Bus module for Copyright-2017

Separator module Separator module
Page 14

Seite 7
Exercise F-1
Retrieve and configure the Standard Project

 Retrieve “Safety_M.zip“ ( D:\Project Master )

 Configure/Check the AS Hardware only ( ignore the

IO modules at this time )

 Compile and download the Station / Networks

 Compile and Download the Standard CFC

 Compile and start the OS and make sure it is

connected

Copyright-2017

Software

Licenses

Compatibility

Copyright-2017

Seite 8
 PCS 7 F-Systems

Necessary Licenses

Systems Design
Order number Description License type
6ES7 833-1CC26-0YA5 S7 F-SYSTEMS V6.2 FLOATING LICENSE
Software
FÜR 1 USER
ES Settings
6ES7 833-4CC26-0YE5 S7 F-SYSTEMS V6.2 UPGRADE (V6.0 AUF V6.1)
Hardware FLOATING LICENSE
Settings
F-User
FÜR 1 USER
Program
Safety-
6ES7 833-1CC00-6YX0 S7 F-SYSTEMS RT COPY LICENSE
Mechanism LICENSE per AS-SYSTEM
SDW/MOS
6ES7 833-1SM02-0YA5 Safety Matrix SINGLE LICENSE
Communication V6.2 SP2 UPD1 for 1 INSTALLATION

6ES7 833-1SM62-0YA5 Safety Matrix Viewer SINGLE LICENSE

V6.2 for 1 INSTALLATION
6ES7 833-1SM42-0YA5 Safety Matrix Editor SINGLE LICENSE
V6.2 for 1 INSTALLATION
Copyright-2017
Page 17

PCS 7 F-Systems

Necessary Licenses
Product Article number

SIMATIC S7 F Systems V6.2

Systems Design Programming and configuration environment for creating and operating safety-related STEP 7 programs
2-languages (German, English), software class A, runs on ES under Windows 7 SP1 64-bit (Professional,
Enterprise, Ultimate) or Windows Server 2008R2 SP1 Standard 64-bit; on OS also under Windows 7 SP1 32-bit
Software (Enterprise, Ultimate), Windows 10 Enterprise 2015 LTSB 64-bit or Windows Server 2012 R2 Standard 64-bit,
floating license for 1 user
Delivery form package 6ES7833-1CC26-0YA5
ES Settings License key USB stick and certificate of license, bundled with 1× SIMATIC S7 F Systems Software Media Package
for each order item
Delivery form online 6ES7833-1CC26-0YH5
Hardware License key download, online certificate of license, combined with SIMATIC S7 F Systems Software Media
Settings Package (software download and online certificate of license)
Note: E-mail address required
F-User SIMATIC S7 F Systems Software Media Package V6.2
Program Installation software without license, 2-languages (German, English), software class A, runs on ES under Windows
7 SP1 64-bit (Professional, Enterprise, Ultimate) or Windows Server 2008R2 SP1 Standard 64-bit; on OS also
Safety- under Windows 7 SP1 32-bit (Enterprise, Ultimate), Windows 10 Enterprise 2015 LTSB 64-bit or Windows Server
2012 R2 Standard 64-bit, floating license for 1 user
Mechanism Note: Can only be used in conjunction with a valid license!

SDW/MOS Delivery form package 6ES7833-4CC26-0YT8

Software on DVD and Certificate of License
Delivery form online 6ES7833-4CC26-0YG8
Software download and online certificate of license
Communication Note: E-mail address required!

SIMATIC S7 F Systems V6.2 Upgrade Package

For S7 F System upgrade from V6.0/V6.1 to V6.2
2-languages (German, English), software class A, runs on ES under Windows 7 SP1 64-bit (Professional,
Enterprise, Ultimate) or Windows Server 2008R2 SP1 Standard 64-bit; on OS also under Windows 7 SP1 32-bit
(Enterprise, Ultimate), Windows 10 Enterprise 2015 LTSB 64-bit or Windows Server 2012 R2 Standard 64-bit,
floating license for 1 user
Delivery form package 6ES7833-1CC26-0YE5
License key USB stick and certificate of license, bundled with 1× SIMATIC S7 F Systems Software Media Package
for each order item
Delivery form online 6ES7833-1CC26-0YK5
License key download, online certificate of license, combined with SIMATIC S7 F Systems Software Media
Copyright-2017
Package (software download and online certificate of license)
Page 18 Note: E-mail address required!

Seite 9
 PCS 7 F-Systems

Necessary Licenses

Product Article number

Systems Design

Software
SIMATIC S7 Safety Matrix Software Media Package
ES Settings V6.2
Installation software without license, 2 languages
Hardware (English, German), software class A, runs with Windows
Settings XP Professional 32-bit, Windows Server 2003/2003 R2
F-User Standard 32-bit, Windows 7 Ultimate 32/64-bit or
Program Windows Server 2008 R2 Standard 64-bit; SIMATIC S7
Safety- Safety MatrixViewer also runs with Windows Server
Mechanism 2012 R2 Standard 64-bit or Windows 10 Enterprise 2015
LTSB 64-bit
SDW/MOS
Note: Can only be used in conjunction with a valid
license.
Communication

Delivery form package 6ES7833-4SM26-0YT8

Software on DVD
Delivery form online 6ES7833-4SM26-0YG
Software download
Note: E-mail address required!

Copyright-2017
Page 19

PCS 7 F-Systems

Compatibility F-Systems and PCS 7

Systems Design

Software
At the customer support homepage you‘ll find up to date information‘s
about the compatibility of PCS 7 and other software packages
ES Settings
http://support.automation.siemens.com/WW/view/en/22761505
Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 20

Seite 10
 ES Settings

Access Protection

CFC

Copyright-2017

PCS 7 F-Systems

Access Protection
Failsafe System must be protected against unauthorized Access
Systems Design

Software  With PCS7 V7.0 onwards, AS-Projects (e.g. F-Program) can be

protected against unauthorized Access via SIMATIC Logon Services.
ES Settings

Hardware
Settings  The safety password is required
F-User - To open a safety CFC
Program
- To create a safety CFC (insert the first F-Function block)
Safety-
Mechanism - To compile the failsafe program
SDW/MOS - To change hardware configuration of safety modules
- To add safety modules in HW-Config
Communication

 Since F-Systems V6.1 together with PCS 7 V7.1 SP1, CPU Parameters
can also be protected by the safety password via selectable option.

 The CPU password is necessary for download to CPU.

Copyright-2017
Page 22

Seite 11
 PCS 7 F-Systems

Settings in the CFC

Systems Design Settings in the CFC-Editor (Options > Settings >

Compile/Download)
Software

ES Settings  For F-Programs we recommend to set up a

Hardware Warning if there are more then 250 blocks
Settings
in one runtime group. (Standard 50)
F-User
Program
Safety-  FC’s between 1 and 60 are reserved.
Mechanism
Anyway, they can be changed according
SDW/MOS
to specified requirements.
Communication
 FAQ: 32202152

Copyright-2017
Page 23

Hardware

Hardware Overview

CPU

I/Os

Voting

Copyright-2017

Seite 12
 PCS 7 F-Systems

Failsafe Controller
 TÜV certified
Systems Design  SIL 3
Software
 Decentralized I/Os (DI, DO, AI)
 F- I/Os along with Standard I/Os
ES Settings
 PROFISAFE Communication
Hardware  IEC 61131 conform (CFC)
Settings
F-User  Integrated Solution for PCS 7
Program
Safety-
Mechanism

SDW/MOS

Communication

S7-410-5H

Copyright-2017
Page 25

PCS 7 F-Systems

CPU Settings

Systems Design Protection

Software
 Protection Level
ES Settings - Access Protection
Hardware - Removable with Password
Settings
F-User
Program  Safety program
Safety- - activate
Mechanism

SDW/MOS
 Protect all CPU Parameters
Communication in HW Config
- activate

Copyright-2017
Page 26

Seite 13
 PCS 7 F-Systems

CPU Settings

Systems Design Cyclic Interrupts

Software
 Priority:
ES Settings - >15 for OBs including F-Program
Hardware - Highest Priority for fastest
Settings Cyclic Interrupt with F-Program
F-User  Execution:
Program
Safety- - min 100ms, if Safety Matrix is used.
Mechanism  Phase offset is not allowed for F-OB
SDW/MOS  Process Image Partition (PIPx):
- Not used for failsafe I/Os:
Communication
(PROFIsafe- Communication)

 Note:

Copyright-2017
Page 27

PCS 7 F-Systems

CPU Settings

Systems Design

Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Examples fm Compendium B Page 29,30,31

Copyright-2017
Page 28

Seite 14
 PCS 7 F-Systems

CPU Settings

Systems Design
H-Parameter (Use of redundant CPUs):

Software
 Test cycle time:
ES Settings - Self test (RAM etc.)
- 90-720min
Hardware
Settings
F-User  Special Handling:
Program
- OB with Priority >15
Safety-
Mechanism
 Monitoring times:
SDW/MOS
- Calculated automatically
Communication - To Update the Reserve

 Redundant Standard Periphery:

- By Channel
- By Module

Copyright-2017
Page 29

PCS 7 F-Systems

Update the Standby

Systems Design Calculation of Monitoring Times

Software
 Program parameter
ES Settings - Runtime
Hardware - Memory
Settings
F-User
Program  Process Data
Safety- - F-SM monitoring time
Mechanism

SDW/MOS
 Monitoring Times
Communication - Calculated automatically

Copyright-2017
Page 30

Seite 15
 PCS 7 F-Systems

Update the Standby

Systems Design

Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 31

PCS 7 F-Systems

Failsafe Peripheries for PCS 7 F-Systems

Systems Design

Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 32

Seite 16
 PCS 7 F-Systems

Failsafe Peripheries

Systems Design Failsafe I/Os for PROFIsafe Communication

Software I/O DI DO AI Motor starter Features

ES Settings ET 200M X X X --- The modular I/O for high-
Hardware channel applications with
Settings up to 24 channels per
F-User module
Program ET 200S X X --- X Motor starter up to 7,5 KW
Safety-
Mechanism
ET 200pro X X --- IP 67 – disconnection
SDW/MOS Module
ET 200eco X -- -- ---
Communication
ET 200iSP X X X --- Ex certificate zone 1

Copyright-2017
Page 33

PCS 7 F-Systems

ET 200S Failsafe

Systems Design ET 200S is used in Single Systems.

Software
Module Features
ES Settings 4/8 F-DI 24 V DC 4 Channels SIL3
Hardware 8 Channels SIL2
Settings
F-User 4 F-DO 24 V DC/2A 4 Outputs
Program sinking/sourcing SIL3
Safety-
Mechanism PM-E F PP 24 V DC Safety Relays 10A
 SIL2 for Standard DO’s
SDW/MOS
PM-E F PM 24 V DC 2 Outputs sinking/sourcing,
Communication SIL2 without Safety Relays for 10A
SIL3 with Safety Relays for 10A

Copyright-2017
Page 34

Seite 17
 PCS 7 F-Systems

ET 200iSP Failsafe Modules

Systems Design ET 200isP – Safety suitable for direct installation in Zone1
Software Module Features
ES Settings

Hardware
Settings
8 F-DI Ex NAMUR 4 inputs 2-channels pair, SIL3
F-User 6ES7138-7FN00-0AB0 8 inputs 1-Channel, SIL2
Program
Safety- 4 F-DO 17.4 VDC/40mA 4 outputs current sourcing/sourcing, SIL3
Mechanism 6ES7138-7FD00-0AB0
SDW/MOS
4 F-AI Ex HART/ 4 analog inputs, 1 channel – SIL3
Communication 0/4-20mA
6ES7138-7FA00-0AB0

Copyright-2017
Page 35

PCS 7 F-Systems

ET 200M Failsafe

Systems Design Use: Singular or Redundant Mode.

Module Features
Software
SM 326 DI24 24 V DC Max. 12 x 2-channel Inputs, SIL 3
6ES7 326-1BK02-0AB0
ES Settings Max. 24 x 1-channel Input, SIL 2
Hardware SM 326 DI8 NAMUR 4 x 2-channel Inputs, SIL 3
Settings 6ES7 326-1RF00-0AB0 *2 8 x 1-channel Input, SIL 2
F-User
Program SM 326 DO10 24V DC/2A 10 x Outputs
Safety- 6ES7 326-2BF10-0AB0 *1 current sourcing/sourcing, SIL 3
Mechanism
SM 326 DO 8 x DC 24V/2A PM 8 x Outputs
SDW/MOS 6ES7 326-2BF41-0AB0 (No Module redundancy)
current sourcing/sinking, SIL 3
Communication SM 336; F-AI 6 x 0/4 ... 20 mA HART 6 x 1-channel Inputs, SIL 3,
6ES7 336-4GE00-0AB0 *1 0/4 - 20 mA HART

Separator module Overvoltage protection between F and

6ES7195-7KF00-0XA0
Standard Modules to reach SIL 3.

*1 40mm wide module

*2 for SIL3, Separator module required Copyright-2017
Page 36

Seite 18
 PCS 7 F-Systems

Failsafe I/Os

Systems Design
OLD FAI module (80mm) New FAI HART module (40mm)
Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 37

PCS 7 F-Systems

Failsafe I/Os

With enabled HART communication the F-AI is rendered passive and the diagnostics buffer displays error message
Systems Design 16#F580:0F01. You can prevent this by parameterizing the "HART gateway".
You are using an F-AI 6ES7336-4GE00-0AB0 and HART communication. The F-AI is rendered passive. The diagnostics buffer
has the following entries:
Software
Event ID 16# F580:0F01
Processor failure (no relevance for user:114,221)
ES Settings

Hardware This event is connected with the "HART gateway" which you use to enable HART communication. The attempt by F-AI to
Settings establish communication with a sensor which does not support the HART protocol causes a high communication load on the
reserve channels. This might lead to blocking of the internal "HART gateway" test. Since the "HART gateway" parameter acts
F-User module-wide as a fail-safe "main switch", the F-AI is rendered passive in this case.
Program Each of the following measures is an improvement for avoiding the behavior described above.
Safety- Parameterize the "HART gateway" as "switchable".
The HART communication can be switched on and off from the safety program as long as the modules are in RUN. Only
Mechanism switch the HART communication on when needed.

SDW/MOS Note: When HART communication is switched off, no diagnostics data can be sent to the PCS 7 Alarm Management.

Switch off HART communication for channels not using HART (reserve channels or channels connected to sensors which do
Communication not support the HART protocol).

Per Compendium B: when enabling Hart operation in the SIS, the hart device must be write protected.

Copyright-2017
Page 38

Seite 19
 PCS 7 F-Systems

MTA’s (Marshaled Termination Assemblies)

Module parameterization
Systems Design
 Deactivate “Sensor supply via Module”
Software  4WMT (for F-AI)
ES Settings

Hardware
Special F-AI
Settings  F-AI Channel Short circuit maybe detected as Wire break.
F-User
Program  Channel is electronic fuse
Safety-
Mechanism
SIL-Certification
SDW/MOS
 SIL 2 (Relays Output)
Communication  SIL 3

Fuse
 1.5A fuse for 4WMT (recommendation for Ex-Barriers)
 0.1A fuse for 2WMT
Copyright-2017
Page 39

PCS 7 F-Systems

ET200M MTA’s

Systems Design
MTA’s are available for

Software
 Standard- and F-Signal modules
ES Settings  Singular and redundant Connection
Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Advantages:
 Reduce Effort and Costs for Wiring/Commissioning
 Avoidance of Wiring Failures

https://support.industry.siemens.com/cs/document/29289048/updating-marshalled- Copyright-2017
Page 40 termination-assemblies-(mtas)?dti=0&lc=en-WW

Seite 20
 PCS 7 F-Systems

Parameterization of the F-SM’s

Redundancy
Systems Design
 Parameterization as
Software for Standard I/Os (only old FAI)

ES Settings
Module parameter
Hardware
Settings
F-User  Operating Mode
Program  F_Dest_Address
Safety-
Mechanism
 F-monitoring time
 Diagnose
SDW/MOS
 Measuring Type
Communication  Measuring Range
 Discrepancy

Copyright-2017
Page 41

PCS 7 F-Systems

Parameterization of the F-SM’s

Module/Module Redundancy
Systems Design

Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication Redundant F_AI modules has no

discrepancy function, so the two may Redundant F_DI modules will output
have differences in value and system a “1” on discrepancy i.e if both are at
will not know. #80 ( good ) status.

Copyright-2017
Page 42

Seite 21
 PCS 7 F-Systems

Parameterization of the F-SM’s

Module/Module Redundancy
Systems Design

Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 43

PCS 7 F-Systems

Parameterization of the F-SMs

Systems Design F-Parameters

Software
 Operating Mode ->Safety Mode (F_DI: SIL2 / SIL3)
ES Settings  F_dest_address (e.g. 1022)
Hardware  DIP-Switch setting -> binary View of the F_dest_address
Settings  F_Monitoring time
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 44

Seite 22
 PCS 7 F-Systems

Parameterization of the F-SM’s

Systems Design Module parameters – F-DI Sensor Type

 Type of Sensor interconnection
Software Two Sensors One
- 1oo1
non Sensor
ES Settings - 1oo2 (1-channel) equivalent equivalent
Hardware - 1oo2 (2-channel equivalent) +V +V +V
Settings
- 1oo2 (2-channel non equivalent) CH0
F-User CH0
Program  Discrepancy +V
Safety- - “last valid Value” or CH12
Mechanism CH12
- Supply “0”
SDW/MOS
- Supply “1“( between redundant modules )
Communication

Module parameters – F-DO

 Safety Mode SIL2 / SIL3
 Dark test (cyclic switch off < 1ms)
 Light test (cyclic switch on < 1ms) deactivated 
SIL2
Copyright-2017
Page 45

PCS 7 F-Systems

Parameterization of the F-SM’s

Systems Design

Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 46

Seite 23
 PCS 7 F-Systems

Parameterization of the F-SM’s

Systems Design
Module parameters – Old F AI ( 80mm wide type )

Software
 Measuring Type SM 336; SIL 3
AI 6 x 13Bit 1

ES Settings - 1 Sensor 2 2-wire meas. 2-wire meas.

L+
M
3 transducer transducer
- 2 Sensors - + - +
Hardware CH0 MI0+ 5

Settings - Measuring Range M0- 6 M

SIL 2
F-User 4-20mA only CH1 MI1+
M1-
8
9
2-wire meas.
transducer
Program MANA 10 - +

Safety- CH2 MI2+

 Discrepancy
12
M2-
Mechanism 13

- Time CH3 MI3+ 15

SDW/MOS M3- 16

- Tolerance CH4
MI4+
M4-
17
18
MI5+
Communication - Value CH5
M5-
19
20

- maximal Value
- minimal Value

Copyright-2017
Page 47

PCS 7 F-Systems

Parameterization of the F-SM’s

Systems Design Module parameters – New F AI Hart (40mm Wide )

Software
 Sensor supply per channel (40mA)
ES Settings

Hardware  Measuring Type

Settings
- 1 Sensor
F-User
Program - 2 Sensors
Safety-
Mechanism
 Measuring Range
SDW/MOS
- 0-20mA
Communication - 4-20mA HART

 Additional LED’s
- Channel failure
- HART-State
Copyright-2017
Page 48

Seite 24
 PCS 7 F-Systems

CiR / H-CiR

Systems Design CiR:

 F parameters can be changed in Run via CiR, but during the hardware
Software download, the F module will be passivated.
ES Settings

Hardware H-CiR:
Settings
Parametrierung  Adding / Removing of entire failsafe Modules
F-User
Program  F parameters can be changed in Run via CiR, but during the hardware
Safety- download, the F module will be passivated.
Mechanism  “Blue” CPU parameters can be download in run.
SDW/MOS

Communication Further Information:

 Manual “Modifying the System During Operation via CiR “

Copyright-2017
Page 49

PCS 7 F-Systems

Voting F_DI 1oo2

Systems Design Voting in the Module SIL 3

 E.g. Emergency Stop
Software
- Sensor
ES Settings - 2-channel non equivalent
Hardware - 1oo2 Voting
Settings
- Wire break / Sensor-Short Circuit
F-User
Program - Discrepancy error
F-DI
Safety- Left Right
Ch 0..11 Ch 0..11
Mechanism Sensor 1
0 0 CPU
SDW/MOS 1 oo 2
SIL 3 Evaluation
F_ CH_DI Logic
Communication SIL 3
F-DI
Left Right
Ch 0..11 Ch 0..11
Sensor 1 Sensor 2
0 0 CPU
SIL 2 1 oo 2 SIL 2
Evaluation
F_ CH_DI Logic
SIL 3

Copyright-2017
Page 50

Seite 25
 PCS 7 F-Systems

Voting logic in the CPU

Systems Design Voting in the CPU SIL 3

Software
 E.g. Emergency Stop
ES Settings - Sensor
Hardware - 2-channel non equivalent
Settings
- 1oo2 Voting
F-User
Program - CFC
Safety- - Safety Matrix
Mechanism
- Wire break / Sensor-Short Circuit
SDW/MOS
- Failure Recording Manually in CFC
Communication

SIL 2 SIL 2
SIL 3

Copyright-2017
Page 51

PCS 7 F-Systems

Voting F_DI NAMUR

Systems Design Voting in the CPU SIL 3

Software
 Channel Diagnostic
ES Settings - Wire break / Sensor-Short Circuit
Hardware - 10k Ohm-Parallel Circuit
Settings
- 1k Ohm-Series Connection
F-User
Program
Safety-
Mechanism

SDW/MOS F-DI
Left Right
Ch 0 ..3 Ch 4 .. 7
Communication Sensor 1 Sensor 2 CPU
0 4
F_ CH _ DI 1oo 2
Voting
SIL 2 SIL 2 Logic

SIL 3

Copyright-2017
Page 52

Seite 26
 PCS 7 F-Systems

Voting F_AI 2oo3

Voting in the CPU SIL 3

Systems Design

Software  E.g. Pressure Measuring

ES Settings
- 3 Sensors
 1-channel
Hardware
Settings - 2oo3 Voting
F-User  CFC
Program
Safety-
 Safety Matrix
Mechanism - Wire break / Sensor-Short Circuit
SDW/MOS  Failure Recording Manually in CFC

Communication

Copyright-2017
Page 53

Exercise F-2.1
Configure PCS 7 F-Systems

 Finish the Hardware configuration

Module F_dest_address I/O Address
F- DI 8xNamur ( EEx ib ) 1 8
F-DI 24 2 14
F-DO 10 3 24
F-AI 6 68 544

 Parameterize the first Channel of each F-Module.

 Create symbolic Names
 Archive your Project ( for backup)

F_dest_address may not be changeable in some new

modules. Use system default assignment is OK.
Logical IO address should follow exercise table for easy
checking.
Copyright-2017

Seite 27
 F-User Program

Program structure

CFC / Block types

Shut down Groups

Shut down Logic

Compile / Download

Safety Program / Comparison

Copyright-2017

PCS 7 F-Systems

Failsafe Blocks

Systems Design F-User Program in CFC according to IEC1311

Software
 Libraries
ES Settings - Lib 1_3
Hardware - Lib 1_2 (old)
Settings
F-User
Program  Blocks are TÜV certified
Safety- - Easy acceptance Test
Mechanism

SDW/MOS
 Master Data Library
Communication - Use for engineering (PCS 7 standard)
- No use for block update

Copyright-2017
Page 56

Seite 28
 PCS 7 F-Systems

F-Data types

Systems Design Standard- and F-Blocks have different Data types

 F-Data types are Structures
Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication  Structure
- DATA (user relevant)
- PAR_ID (Program wide ID)
- COMPLEM (Complement of Data)

Copyright-2017
Page 57

PCS 7 F-Systems

Transferring Data Standard <-> F-Program

Systems Design Special Converter blocks are required

Software F-CPU Standard CFC => F-CFC

F-Program

ES Settings
Converter blocks
not Safety related
Hardware
Settings
Standard Program
F-User
Program
Safety-
Mechanism F-CFC => Standard CFC
SDW/MOS

Communication

Copyright-2017
Page 58

Seite 29
 PCS 7 F-Systems

Example: Limit Value Processing

Systems Design F-CFC Standard CFC

Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

 Standard FB’s and F-FB’s in different Runtime Groups

 Connection of QBAD
 Standard Outputs of the F-Blocks can be connected directly
Copyright-2017
Page 59

PCS 7 F-Systems

Failsafe SIF (Safety Instrumented Function Group)

Systems Design F-blocks and Standard blocks must be inserted in different

Runtime Groups
Software

ES Settings continuously failsafe signal transfer

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Inserted in another Runtime Group Copyright-2017

Page 60

Seite 30
 PCS 7 F-Systems

Program structure

Systems Design
Program structure in the Run time editor

Software

ES Settings

Hardware
Settings
 F_RTG
F-User
Program  F_PSG1
Safety-
Mechanism  F_PSG2
SDW/MOS

Communication

 F_RTG = Runtime Group (no Standard blocks)

 F_PSG = Partial Shut down Group

Copyright-2017
Page 61

PCS 7 F-Systems

Behavior for Invalid Numbers

Systems Design Invalid Numbers

 Overflow (± infinitely)
Software
 Denormalized Floating Point numbers (± 0)
ES Settings  Invalid Floating Point numbers (NaN):
Hardware
Settings
Reaction
F-User
Program
Safety-  Output Results to forward them
Mechanism
 Failure indication
SDW/MOS
 Output of Substituted Values
Communication

Copyright-2017
Page 62

Seite 31
 PCS 7 F-Systems

Compile / Download the F-Program

Compilation
Systems Design

Software  Starts with Standard-Compilation

ES Settings  First Compile
- Set up the Cycle time
Hardware
Settings - Build up the Shut down logic
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 63

PCS 7 F-Systems

Compile / Download the F-Program

Systems Design

Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 64

Seite 32
 PCS 7 F-Systems

Download the F-Program

Systems Design Download

Software
 Safety Program in CPU is activated.
ES Settings  Access is granted
Hardware  Changes are evaluated
Settings
F-User Download CPU in CPU in RUN Safety CPU in RUN Safety
Program STOP Mode active Mode is inactive
Safety-
Mechanism entire Program
X
SDW/MOS
Changes in Standard-
Communication Program X X
Changes in Safety
Program X

Copyright-2017
Page 65

PCS 7 F-Systems

Download the F-Program

Systems Design Safety

Mode
Software
Inactive
ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 66

Seite 33
 PCS 7 F-Systems

Download the F-Program

Download
Systems Design
In
Software
Changes
ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 67

Exercise F-2.2
Configuration of PCS 7 F-Systems

 Create CFC-Charts due to Hierarchy folders

 Place one Channel driver per F-Module corresponding

the symbol table

 First Compile of the F-Program

- maximal Cycle time
(leave 3000ms)

 Download the Program

Copyright-2017

Seite 34
 PCS 7 F-Systems

Shut down logic

The Shut down logic is created within the first compile
Systems Design

Software  OS-Messages for

- Safety Mode is deactivated (Message interval is to be set up)
ES Settings
- Partial /Full Shut down (Priority 16)
Hardware
Settings
 Entry in the Diagnostic buffer for
F-User
Program - Safety Mode deactivated (E ID 16#7xDB)
Safety- - Partial / Full Shut down
Mechanism

SDW/MOS  Program Signature

 Shut down behavior
Communication
 Restart
 Safety Mode
 Force a Shut down
 Alarm update

Copyright-2017
Page 69

PCS 7 F-Systems

Safety Mode
Mechanism for Failure detection and -reaction are active.
Systems Design

Software  Change/Display in Dialog “Edit Safety Program”

 Output SAFE_M (1=Safety active, 0=Deactivated)
ES Settings
at the F_SHUTDN Block.
Hardware
Settings
F-User
Program
Safety-
 Unknown Safety Mode
Mechanism - Missing Online Connection
SDW/MOS - F_TestM Block in @F_TestMode is not found online
- Different Programs
Communication
- Safety program stopped - F STOP
( red ! mark in F block )

Copyright-2017
Page 70

Seite 35
 PCS 7 F-Systems

Edit Safety Program

Select CPU with the F-Program
Systems Design
 Button “ Edit Safety Program “
Software  Options => Edit Safety Program

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 71

PCS 7 F-Systems

Safety Program

Systems Design

Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 72

Seite 36
 PCS 7 F-Systems

Comparison
Compare between
Systems Design

Software

ES Settings Result of the

Hardware
Comparison
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 73

PCS 7 F-Systems

Safety Program - Printout Check

Systems Design

Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 74

Seite 37
 PCS 7 F-Systems

Safety Program – Printout Check

Systems Design

Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 75

Exercise F-2.3
Save Reference

 Save the Reference for the current F-Program

Copyright-2017

Seite 38
 Exercises F-3.1 / F-3.2 / F-3.3
F-User Program

 ESD
Emergency Shut Down-Function for the Agitator
„HS_103“

 Pressure SIF
Pressure Monitoring with „PT_110“ and „PT_111“

 Level SIF
Level Monitoring „LT_100“

Copyright-2017

Exercises F-3.1 / F-3.2 / F-3.3

 “SIF_Agitation” - Emergency Shut Down-Function for HS-103 motor

Copyright-2017

Seite 39
 Exercises F-3.4
F-Compare

 Compare the saved Reference with the current

Program

Copyright-2017

PCS 7 F-Systems

Block Types

Systems Design  Rules for F-block types

Software
 Create in separated “dummy” F-AS
ES Settings  Only F Blocks of the same Library
Hardware  Except for
Settings
- Drivers blocks
F-User
Program - Communication blocks
Safety- - SDW ( Secure Data Write ) blocks
Mechanism
- F-System blocks (except F_START)
SDW/MOS
 Chart I/Os
Communication - Standard and failsafe
- Connect an output of the F-Block with only one chart I/Os
 Optimize the Run sequence manually
 Name with Format F_xxx

Copyright-2017
Page 80

Seite 40
 PCS 7 F-Systems

Block Types

Systems Design  Compile Chart as Block type

Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 81

PCS 7 F-Systems

Block Types
Creating F Chart in Block for F Use. - Expert Comments.
Systems Design
 You have to create the block in a 41x-H CPU in a project (not in a library, which can't contain a hardware item),
with the CPU's HW configuration saying it contains a safety program, otherwise CFC will still compile the thing
Software OK, but the blocks end up grey and not safety-certified. This is obvious immediately you drag the block onto a
chart, of course.
ES Settings
 Also, if your chart-to-block chart (the source chart) has chart inputs or outputs (which it pretty much must have
Hardware to be useful), you cannot then compile the entire CPU to make a working program, because the chart-to-block
chart won't have any interconnections to its chart I/O - after all, the chart wasn't intended to be run as a chart.
Settings
F-User  Leaving the source chart there is OK for a standard chart-to-block source chart, but the safety program won't
Program allow the source chart to live there with no connections to its chart I/O in a safety program.
Safety-
Mechanism  So you then have to copy the compiled safety block to another 41x-H CPU which is the "real" CPU for the safety
program, or for ease of use, copy it into a library so you can browse to it from within CFC.
SDW/MOS
 Also, although you *can* use a standard-to-safety-BOOL (or REAL or whatever) block within your source chart,
and it will compile OK, at runtime it always seems to deliver a passivated safety output. I tried to do this for
Communication testing (ie, use ordinary bits in the PLCSIM, and turn them into safety inputs for testing the safety blocks).

 If I leave the BO->F-BO block naked on the chart, it works fine at runtime;
 if I compiled it into a block, the resulting block compiles OK and is yellow but all the safety-BOOL outputs
passivate at runtime.

 There was a cryptic comment about using these blocks that, after the event, seemed to indicate that this was
correct behaviour, but until I saw the behaviour, the meaning of the comment remained obscure.

Copyright-2017
Page 82

Seite 41
 Safety-Mechanism
F-Stop

Shut down behavior

Restart Protection

Passivation / Depassivation

Reintegration

Safety Mode

Copyright-2017

PCS 7 F-Systems

Failure reaction Single System

Systems Design No Failure Failure in the F-Program (F-Stop)

Software

ES Settings

Hardware
Settings
F-User Failure in the RAM
Program
Safety-
Mechanism

SDW/MOS

Communication

= Stop
= Standard Program
= F-Program Copyright-2017
Page 84

Seite 42
 PCS 7 F-Systems

Failure reaction Redundant System

Systems Design No Failure RAM Failure in the Master (M)

Software M R M
ES Settings

Hardware
Settings
F-User RAM Failure in the Reserve (R)
Program
Safety- M
Mechanism

SDW/MOS

Communication
= Stop
= Standard Program Failure in the F-Program (F-Stop)
= F-Program
M
M/R = Master / Reserve

Copyright-2017
Page 85

PCS 7 F-Systems

Startup of the F-Program

Systems Design The F-Program starts

 After CPU Stop
Software
- Warm start
ES Settings

Hardware  After F-Stop (At "F_SHUTDN" RESTART = 1)

Settings
- Just failure free Parts of the safety program are restarted (PSG)
F-User
Program
Safety-  F_START displays the F-Start
Mechanism
- COLDSTRT = 1
SDW/MOS
( for one OBxx scan only )
Communication

 Due to the Process, the avoidance of an automatic restart of the

F-Program is necessary

Copyright-2017
Page 86

Seite 43
 PCS 7 F-Systems

Passivation of F-I/Os

In Case of an Failure, Channels are taken into the failsafe State

Systems Design

Software  Channel failure (e.g. defective Sensor)

ES Settings
- involved Channels are passivated

Hardware
Settings  Module failure (e.g. Communications failure)
F-User - All Channels of the Module are passivated.
Program
Safety-
Mechanism  Cognition of a Passivation
SDW/MOS - Quality Code
- QBAD = 1
Communication
- PASS_OUT = 1

Copyright-2017
Page 87

PCS 7 F-Systems

Behavior during Passivation

Systems Design Passivation of F_DO

 Outputs are without voltage/current ( *** )
Software
 Quality Code 16#48
ES Settings  *** new F-DO has selection feature “to hold last state” when passivated.
This is NOT a safety Feature and the loop is no longer a safety loop.
Hardware – usually required in FGS application.
Settings
F-User
Program Passivation of F_DI
Safety-  Substitution value 0 is output/Last valid Value
Mechanism
 Quality Code 16#48
SDW/MOS

Communication Passivation of F_AI

 for SUBS_ON = 1  For SUBS_ON = 0
- Substitution values are output - Last valid Value
- Quality Code 16#48 - Quality Code 16#44 (only FAI has this code)
- QSUBS = 1
Copyright-2017
Page 88

Seite 44
 PCS 7 F-Systems

Manual Passivation

Systems Design With PASS_ON a Passivation can be activated via logic

Software
 Group Passivation
ES Settings  Startup Protection
Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

 PASS_ON = 1, Channel is passivated

 PASS_OUT is activated if there is a channel failure

Copyright-2017
Page 89

PCS 7 F-Systems

Reintegration of F-I/Os

Systems Design
Read in and output valid Process values again

Software Channel Failure Module Failure

ES Settings

Hardware
Settings 1
ACK_NEC ACK_REQ
F-User
Program
Safety-
0 1
Mechanism

SDW/MOS ACK_REI

1
Communication
OK

 Change of PASS_ON 1  0
- automatic Reintegration

Copyright-2017
Page 90

Seite 45
 PCS 7 F-Systems

Build up the Reintegration

The Reintegration of the I/Os is done via
Systems Design

Software  F_CH_DI (Hardware Button)

- Easy to engineer
ES Settings
- Deactivated after Module Failures
Hardware
Settings  F_QUITES (OS Button Operation)
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 91

PCS 7 F-Systems

F_Quites

Systems Design F_QUITES is to acknowledge a failsafe System with a non

failsafe System (ES/OS).
Software

ES Settings
 Change Input IN from 0  6 (6 = 0110 bit)
- Q changes from 0  1 for 60 Seconds
Hardware
Settings
F-User  Change Input IN from 6  9 if Q = 1 (9=1001 bit )
Program
Safety- - OUT changes for one Cycle from 0  1
Mechanism

SDW/MOS  Activate the attribute “Control and monitor” in the properties.

Communication
Note: SF LED of SM – Diagnostic Info

Copyright-2017
Page 92

Seite 46
 PCS 7 F-Systems

F_Quites
Input IN of F_Quites is set to 6 and 9 with an OS-Button in a
Systems Design defined time (60s)
Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 93

Exercise F-4
User Confirmation

 Acknowledge Request on yellow signal lamp

 Insert F_QUITES in the CFC

 Create the OS-Buttons

Copyright-2017

Seite 47
 SDW
MOS
Safety Data Write

Maintenance Override Switch

Copyright-2017

PCS 7 F-Systems

Safety Data Write

Change failsafe Parameters via the OS

Systems Design

Software
 Changes are done via Safety protocol
ES Settings
- Changes (Transaction) are done with a special operation
Hardware
Settings
Sequence
F-User - Within a special time
Program
Safety- - SIL3 due to IEC 61508
Mechanism

SDW/MOS
 Operation
Communication
- Two User „second set of Eyes“

Copyright-2017
Page 96

Seite 48
 PCS 7 F-Systems

Safety Data Write

 User 1
Systems Design - Initiate change of Parameters
Software - Parameter confirmation

ES Settings
 Valid for the time value of TIMEOUT
Hardware
Settings
F-User  Conditions
Program - Initialization of User 1 is valid
Safety-
Mechanism - New Parameter is known (not displayed)
SDW/MOS
 User 2
Communication
- Repeat the Change of the Parameter
- Parameter Confirmation

 The Change of the Parameter is active

 Message in the OS Copyright-2017

Page 97

PCS 7 F-Systems

Safety Data Write

Systems Design Two blocks for F_REAL- and F_BOOL-Parameters in CFC

Software
 Safe_ID1
ES Settings - Unique in CPU
Hardware  Safe_ID2
Settings
- Unique in System
F-User
Program
Safety-  Range
Mechanism
- MIN
SDW/MOS
- MAX
Communication - MAX_DELTA

 EN_CHG

Copyright-2017
Page 98

Seite 49
 PCS 7 F-Systems

Safety Data Write

Systems Design Adjust the Block symbol

Software
 Block symbols are derived
ES Settings  Set up the Safe_IDs
Hardware  User rights
Settings
F-User
Program  Save Parameters
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 99

PCS 7 F-Systems

Maintenance Override concept

Systems Design Maintenance Override FB offers possibility to change up to 3

values in the safety program of the OS. (e.g. setting bypasses)
Software

ES Settings  Changes are done via Safety protocol

Hardware - Changes (Transaction) are done with a special operation
Settings
F-User
Sequence
Program - Within a special time
Safety-
Mechanism - SIL3 due to IEC 61508
SDW/MOS

 Operation
Communication
- Two User “second set of Eyes“

Copyright-2017
Page 100

Seite 50
 PCS 7 F-Systems

AS-Engineering
Four F blocks
Systems Design

Software  F_SWC_MOS – HMI interface

ES Settings  F_SWC_BO – change Bool Value
 F_SWC_R – change real value
Hardware
Settings  F_SWC_P - ( only one per OB )
F-User
Program
Safety- Chart in Chart
Mechanism
 SWC_TR ( optional, for time
SDW/MOS control maintenance overide )

Communication

For Bool Simulation use

With a F_SWC_BO

Real Simulation value

Copyright-2017
Page 101

PCS 7 F-Systems

OS-Engineering

Systems Design Block symbols were placed automatically

Software

ES Settings System identifier (AKZ)

Look of the OS-Faceplates CPU Settings
Hardware
Settings
F-User CFC-Block name
Program of 1. F_SWC_BO Block

Safety-
Mechanism CFC-Block name
of 2. F_SWC_BO Block
SDW/MOS
CFC-Block name
of 3. F_SWC_BO Block
Communication
For changing simulation
value either Real OR Bool
(optional)

Maintenance Overide time

which can be “retriggered”
before it lapsed ( optional )

Copyright-2017
Page 102

Seite 51
 PCS 7 F-Systems

Bypass operation with two operators

 The initiator
Systems Design initiates the bypass on the F-Channel driver. This user must have the authorization
for initiating the Bypass, LevelBypass, and LevelBypassValue but not for confirming
Software them. The authorization corresponds to the "InitiatorAuthorization" attribute in the
properties for the block icon. The default setting is No. 5, Operator-process
ES Settings communications.
Hardware
Settings  The confirmer
F-User verifies and confirms the change. This operator must have the necessary
Program authorization for confirming the change, LevelBypass, and LevelBypassValue but
Safety- not for initiating them. The authorization corresponds to the "ConfirmerAuthorization"
Mechanism attribute in the properties for the block icon. The default setting is No. 6, Higher-level
operator-process communications.
SDW/MOS

Communication

Copyright-2017
Page 103

Exercise F-5
Use MOS function to manipulate F_CH_AI
PT_110 and PT_111

 For simulation mode and

 Simulation value
 With Limit Simulation time
 Warning before time runs out
 Visualize simulation and process value

Copyright-2017

Seite 52
 Communication

Between Shut down Groups

Between S7 400 F-Controller

Between S7 F-Systems and Distributed Safety

Copyright-2017

PCS 7 F-Systems

F-Shut down Groups

Systems Design F-Shut down Groups consist of F-Runtime Groups of one OB

Software
 Partial Shut down of the F-User Programs
ES Settings

Hardware  All F-Channel drivers of one F-Module needs to

Settings
F-User Be in the same Shut down Group
Program
Safety-
Mechanism

SDW/MOS
 F-blocks in different F- Shut down Groups must
Communication
not be connected directly to each other

 Creation of Shut down Groups with F_PSG_M

Copyright-2017
Page 106

Seite 53
 PCS 7 F-Systems

Communication across Shut down Groups

Systems Design Because of the Shut down behavior, Parameters in different

Shut down Groups cannot be connected directly.
Software

ES Settings  Send blocks

Hardware - F_S_BO (10 x Boolean)
Settings - F_S_R (5 x Real)
F-User
Program
Safety-  Receive blocks
Mechanism
- F_R_BO
SDW/MOS
- F_R_R
Communication
 The Value for TIMEOUT needs to be calculated.
- In Case of an failure, Substitution values are output.

Copyright-2017
Page 107

PCS 7 F-Systems

Communication between CPUs S7 400

Failsafe AS Communication for 20 Parameters
Systems Design

Software  Send blocks

- F_SENDBO
ES Settings
- F_SENDR
Hardware
Settings
 Receive blocks
F-User
Program - F_RCVBO
Safety- - F_RCVR
Mechanism

SDW/MOS  Connection
- Connection ID from Netpro
Communication
- Same ID for Sender & Receiver
- Subnet ID (in Netpro)
- R_ID is an odd value you set
- TimeOUT needs to be calculated and identical
- No using “unspecified connection” ( in Netpro )
Copyright-2017
Page 108

Seite 54
 PCS 7 F-Systems

Performance for Communication

Performance Consideration for communication of each CPU

Systems Design
Example: CPU 417-4H (V4.1) with CP 443-1
Software
 Estimate Capacity : 97 Communication jobs per Second
ES Settings

Hardware  Each Alarm_8P, U_SEND, U_RCV block takes one Communication job per call.
Settings
The CPU executes the Communications jobs according to the FIFO Principe, i.e.
F-User without Priority of failsafe Communication.
Program
Safety-
Mechanism  If Communication is to high, failsafe telegrams might be not sent as expected 
Loss of Communication to receiver CPU, might result in a shutdown.
SDW/MOS

Communication  Therefore, Cycle time for Communication Blocks is essential:

1 x F_SENDBO in the 100ms Cycle takes 10 Communication jobs in 1s
i.e. estimate: 10% of the reserve.

http://support.automation.siemens.com/WW/view/en/2446042

Copyright-2017
Page 109

PCS 7 F-Systems

Communication Between F-Systems – Distributed Safety

Send 32 F-Bool between S7 300F(DS) & S7 400F(F-Systems)
Systems Design

Software  F-Systems  CFC

- Send block F_SDS_BO
ES Settings
- Receive block F_RDSBO
Hardware
Settings
F-User  Distributed Safety FUP
Program
- F_RCVS7
Safety-
Mechanism - F_SENDS7
SDW/MOS
 Connection
Communication
- Connection ID from Netpro
- Same ID for Sender & Receiver
- Subnet ID (in Netpro)
- R_ID is an odd value you set
- TimeOUT needs to be calculated and identical
- No using “unspecified connection” ( in Netpro ) Copyright-2017
Page 110

Seite 55
 PCS 7 F-Systems

Communication Between F-Systems and DS – Digital Only

Systems Design

Software

ES Settings

Hardware
Settings
F-User
Program
Safety-
Mechanism

SDW/MOS

Communication

Copyright-2017
Page 111

Questions?

Seite 56