Programmable Safety Systems

PSS-Range

ST SB FE MBS
Error Evaluation with PX(T) Text Displays
Operating Manual
Item No. 19 406-05

The spirit of safety.

All rights to this manual are reserved by Pilz GmbH & Co. Copies may be made for internal
purposes.

While every effort has been made to ensure that the information in this manual is accurate,
no responsibility can be accepted for errors or omissions contained within it.

We reserve the right to amend specifications without notice. We are grateful for any
feedback on the contents of this manual.

The names of products, goods and technologies used in this manual are trademarks of the
respective companies.
Contents

Introduction 1-1

Overview of manual 1-2

Terminology 1-2
Definition of symbols 1-3

Overview 2-1

Software package 2-1

Range 2-2
System requirements 2-3
Programmable safety system 2-3
Usable operator devices 2-4

Safety 3-1

Safety guidelines 3-1

Use of qualified personnel 3-1
Warranty and liability 3-1
Application guidelines 3-2
Intended use 3-2

Commissioning 4-1

Procedure 4-1

Operating Manual: ST SB FE MBS 1

Contents

Function Description 5-1

Error evaluation 5-1

Principle function of the software package 5-2
Fault diagnostic concept 5-3
Internal errors 5-3
Error processing 5-3
Error stack 5-4
Evaluating the error stack 5-4
Assigning error numbers to error classes 5-5
External errors 5-6
Input parameter SSNR 5-7
Administration data blocks from the failsafe section 5-7
Configuration data block in the standard section 5-8
Structure and contents of a data word in the configuration data block 5-9
List of protection circuit types 5-10
Evaluation sequence for internal and
external errors 5-12
Error from the error stack: 5-13
Error from an MBS SB: 5-13
Evaluation sequence including errors
from decentralised I/O modules 5-14
PSS error from the error stack: 5-15
Error from a decentralised I/O module (SafetyBUS p): 5-15
Error from an MBS SB: 5-15
Temporary flag range 5-16
Operator guidance, message texts and
variables 5-17
Operator guidance and diagnostics with a Pilz
operator device 5-17
Message texts for error stack messages 5-18

2 Operating Manual: ST SB FE MBS

 Message texts for error stack messages of
decentralised I/O modules 5-19
Message texts for error messages from MBS standard
function blocks 5-20

Standard Function Blocks 6-1

SB 050 (FS-FE-PX): Decoding the error

stack messages 6-1
Block header 6-1
Input parameters 6-1
Output parameters 6-2
Function 6-2
Setting parameters 6-2
Temporary flags used 6-3
Blocks required 6-3
SB 052 (MBS_FE_9): Evaluating the error
messages from the error stack and MBS
standard function blocks 6-4
Block header 6-4
Input parameters 6-4
Output parameters 6-6
Function 6-6
Setting parameters 6-6
Temporary flags used 6-7
Blocks required 6-7
SB 053 (SB_Error): Evaluating the error stack
messages of decentralised I/O modules 6-8
Block header 6-8
Input parameters 6-8
Output parameters 6-9

Operating Manual: ST SB FE MBS 3

Contents

Function 6-9
Assignment of I/O module error classes to error numbers: 6-9
Setting parameters 6-10
Temporary flags used 6-10
Blocks required 6-10

Example 7-1

Application example 7-1

Connection cable between PSS and text display 7-2
Initialising the PSS user interface 7-2
Incorporating SB 052 (MBS_FE_9), PSS standard
section 7-4
Incorporating SB 053 (SB_Error), PSS standard
section, only in conjunction with SafetyBUS p 7-6
Transferring message numbers to a display 7-8
User-defined message numbers 7-9
Error message numbers have priority 7-9
User-defined messages have priority 7-9
Program listing 7-10

Appendix 8-1

Standard function blocks: current versions 8-1

Amendment list 8-2
SB 050 (FS-FE-PX): Decoding the error stack messages 8-2
Changes from Version 1.0 to Version 1.1 8-2
Changes from Version 1.0 to Version 1.2 8-2
Changes from Version 1.1 to Version 1.3 8-3
Changes from Version 1.3 to Version 1.4 8-3

4 Operating Manual: ST SB FE MBS

 SB 052: Evaluating the error messages from the error
stack and MBS standard function blocks 8-3
Changes from Version 1.0 to Version 1.1 8-3
Changes from Version 1.1 to Version 1.2 8-4
Changes from Version 1.2 to Version 2.0 8-4
SB 053: (SB_Error): Evaluating the error messages
from the error stack on decentralised I/O modules 8-5
Changes from Version 1.0 to Version 1.1 8-5
Amendments to text files 8-5
Changes in the documentation 8-6
Changes from Version III to Version IV 8-6
Changes in Version 19406-05 8-6

Operating Manual: ST SB FE MBS 5

Contents

6 Operating Manual: ST SB FE MBS

Introduction

This operating manual describes the software package for displaying error
messages from a PSS programmable safety system via text displays and
line-based operator terminals. It contains all the information required for
the proper application of the software package.

To fully understand this manual you will need to be conversant with the
information found in the general documentation for the PSS-range
(System Manual, Installation Manual for the modular PSS and
Programming Manual).

Further information is also available in the documentation for SafetyBUS p

and the MBS packages.

This installation manual is intended for instruction and should be retained

for future reference.

Operating Manual: ST SB FE MBS 1-1

Introduction

Overview of manual

This manual is divided into the following chapters:

1 Introduction
The introduction is designed to familiarise you with the contents,
structure and specific order of this manual.
2 Overview
This chapter gives a brief overview of the software package’s
application range and describes its contents.
3 Intended Use
This chapter must be read as it contains important information on
safety and intended use.
4 Commissioning
This chapter contains a concise description of the steps you must take
in order to be able to use the software package.
5 Function Description
The function description contains detailed information on how the
software package operates.
6 Standard Function Blocks
This chapter provides information about the function of standard
function blocks SB 050, SB 052 and SB 053.
7 Example
This chapter contains an application example.
8 Appendix
The appendix contains details about the current version status of the
standard function blocks and about changes in the documentation.

Terminology

• In this documentation, the term “PSS” is used as the generic term for all
programmable safety systems from Pilz GmbH & Co.
• In this documentation, the term “MBS” is used as an abbreviation for the
Modular Block System from Pilz GmbH & Co.
• In this documentation, the term “SB” is used as an abbreviation for
standard function block.

1-2 Operating Manual: ST SB FE MBS

Definition of symbols

Information in this manual that is of particular importance can be identified

as follows:

DANGER!
This warning must be heeded! It warns of a hazardous situation that
poses an immediate threat of serious injury and death and indicates
preventive measures that can be taken.

WARNING!

This warning must be heeded! It warns of a hazardous situation that

could lead to serious injury and death and indicates preventive
measures that can be taken.

CAUTION!

This refers to a hazard that can lead to a less serious or minor injury plus
material damage, and also provides information on preventive measures
that can be taken.

NOTICE
This describes a situation in which the unit(s) could be damaged and also
provides information on preventive measures that can be taken.

INFORMATION
This gives advice on applications and provides information on special
features, as well as highlighting areas within the text that are of particular
importance.

Operating Manual: ST SB FE MBS 1-3

Introduction

Notes

1-4 Operating Manual: ST SB FE MBS

Overview

The software package ST SB FE MBS “Error Evaluation with PX(T) Text

Displays” enables messages from a PSS-range programmable safety
system to be evaluated and displayed. Messages can be displayed from
the following areas:
• From the CPU error stack
• From MBS blocks
• From the error stack of decentralised I/O modules

Software package

The standard function blocks within the package must be linked into the
application program of the standard section of the PSS.

PSS
Control andvon
monitoring of Steuerung
Control of und
Steuerung Fail-safe- Standard- Regelung von
safety-related
sicherheitsgerichteten Failsafe Standard non-safety-related
nicht
tasks
Aufgaben Section Section tasks sicherheitsgerichteten
Teil Teil Aufgaben
e.g.: diagnostics, etc.
e.g.:
z. B.:E-STOP
NOT-AUS circuits,
usw. etc. z. B.: Diagnose usw.

Fig. 2-1: Structure of the PSS

Pilz PSS programmable safety systems have been designed for use in
plant and machinery safety circuits. They consist of a failsafe (FS) section
and a standard (ST) section.

The software package ST SB FE MBS is exclusively for use in the

standard section of a PSS programmable safety system.

The software package ST SB FE MBS does not take into account the
specific error messages of the PSS(1) SF CPU (selective shutdown).

INFORMATION
To drive a Pilz operator device you will also require the software package
ST SB PXT “Drivers for PX/PXT”).
To transfer texts to the operator terminal you will need the configuration
tool PX-PRO.

Operating Manual: ST SB FE MBS 2-1

Overview

Range

The software package consists of:

• One CD and
• One operating manual:
ST SB FE MBS Error Evaluation with PX(T) Text Displays .

The CD contains:
• Standard function block SB 050 FS-FE-PX
Decoding the error stack messages
• Standard function block SB 052 MBS_FE_9
Evaluating the error messages from the error stack and MBS standard
function blocks
• Standard function block SB 053 SB_Error
Evaluating the error stack messages of decentralised I/O modules
(SafetyBUS p)
• Standard function block SB056 (DOMAIN_0)
Reads Domain 0 (Error Domain)
• Standard function block SB 254 StBsCall
Calls up the operating system
• Configuration data block DB 015* in the standard section of a PSS
Temporary storage for evaluation of error messages
• Data block DB 019* DOM_0_S
Data block for the usable data from Domain 0
• Data block DB 020* DOM_0_T
Data block for the edited data from Domain 0
• Message text files for Pilz PX(T) text displays
In German and English
• German documentation as a PDF file
ST SB FE MBS Fehlerauswertung mit Textanzeigen PX(T),
Operating Manual, Item No. 19 405
• English documentation as a PDF file
ST SB FE MBS Error Evaluation with PX(T) Text Displays,
Operating Manual, Item No. 19 406
• A sample program
• Acrobat Reader
* These blocks can be renamed by the user.

2-2 Operating Manual: ST SB FE MBS

System requirements

Programmable safety system

Messages can be displayed with the following CPU versions:

• Internal PSS errors and external (MBS) errors

CPU From version

PSS CPU 1.7
PSS1 CPU 1.1
PSS 3056 2.3
PSS 3056-1 1.6
PSS 3056-2 1.6
PSS 3032 1.0
PSS 3046 1.0
PSS 3074 1.0
PSS SB CPU 1.0
PSS1 SB CPU 1.0
PSS SB 3006 CN-A 1.0
PSS SB 3006 DP-S 1.0
PSS SB 3006 ETH 1.0
PSS SB 3006 IBS-S 1.5
PSS SB 3056 1.0
PSS CPU2 1.0
PSS1 CPU2 1.0
PSS CPU3 1.0
PSS1 CPU3 1.0
PSS SB CPU3 1.0
PSS1 SB CPU3 1.0

Operating Manual: ST SB FE MBS 2-3

Overview

• Errors on decentralised I/O modules (SafetyBUS p)

CPU From version

PSS SB CPU 1.6
PSS1 SB CPU 1.6
PSS SB 3006 CN-A 1.0
PSS SB 3006 DP-S 1.0
PSS SB 3006 ETH 1.0
PSS SB 3006 IBS-S 1.5
PSS SB 3056 1.3
PSS SB CPU3 1.0
PSS1 SB CPU3 1.0

Usable operator devices

You can use the following text displays and line-based operator terminals:

• PX20
• PX30
• PX120
• PXT5
• PXT132
• PXT208
• PXT216
• PXT305

INFORMATION
Please note the guidelines in the section entitled “Software package”.

2-4 Operating Manual: ST SB FE MBS

Safety

Safety guidelines

These safety guidelines are an important part of this manual.

Failure to keep to these guidelines will render all warranty and liability
claims invalid.
All rules and regulations for accident prevention relating to the specific
area of application must be met. In particular, VDE and all local
regulations regarding safety measures should also be taken into account.
Please make sure you read the information in the “Installation Manual”
regarding the use of I/O modules. You should also be familiar with the
details provided in the PSS “Safety Manual”.

Use of qualified personnel

It is the company’s responsibility only to employ personnel who:

• Are familiar with the basic regulations concerning health and safety /
accident prevention
• Have read and understood the safety guidelines given in this manual.
Programming and commissioning must only be carried out by competent,
qualified personnel.

Warranty and liability

All claims to warranty and liability will be rendered invalid if:

• Standard function blocks are used contrary to the purpose for which they
are intended
• Damage can be attributed to not having followed the guidelines in the
manual
• Operating personnel are not suitably trained or sufficiently qualified.

Operating Manual: ST SB FE MBS 3-1

Safety

Application guidelines

• The instructions given in the “Safety Manual” and in the “Installation

Manual” must be followed.
• Please read the information on intended use in chapter 3.

Intended use

The software package ST SB FE MBS “Error Evaluation with PX(T) Text

Displays” is designed for use with Pilz programmable safety systems
(PSS-range). Using the software package it is possible:
• To decode error messages from the error stack of the programmable
safety system and decentralised I/O modules (SafetyBUS p)
• To decode error messages from blocks in the Modular Block System
(e.g. MBS E-STOP, MBS Tank Farms, MBS Eccentric Presses etc.)
• To display the message texts that correspond to the error messages on
a Pilz operator terminal and transfer the corresponding variables to the
operator terminal.

INFORMATION
Use of standard function blocks outside the specifications described here
will be deemed as improper use.

3-2 Operating Manual: ST SB FE MBS

Commissioning

This chapter describes the procedure for the necessary installations.

Detailed descriptions of the individual steps can be found in the chapters
that follow.

Procedure

The CD contains text files for Pilz text displays and line-based operator
terminals.

• Load the required text file into the configuration tool PX-PRO.
• Transfer the data into the operator device. The necessary information
can be found in the “PX-PRO Operating Manual” and the manual for the
operator device you are using.

The PSS requires the data blocks and standard function blocks supplied
on the CD for communication with the operator device.

• In your ST application program, call up standard function block SB 052

as part of each cycle; if you want to evaluate errors from decentralised
I/O modules, you will also need SB 053.

INFORMATION
SB 053 must be called after SB 052.

• Set the block parameters to suit your requirements (see Chapter 6) or

use one of the sample programs supplied on the CD (see Chapter 7).

NOTICE
- Do not use flags from the temporary flag range for your own
applications.
Malfunctions may occur if you use the temporary flag range M59.00 ...
M63.31 for your own applications.
- If it is absolutely necessary to use this flag range, under no
circumstances should you use the flags as input parameters for
standard function blocks.

Operating Manual: ST SB FE MBS 4-1

Commissioning

• Import the standard function blocks that are required as drivers from the
software package ST SB PXT. Set their parameters to suit your
requirements. The exact procedure can be found in the “ST SB PX(T)
Operating Manual”.
• Make the settings in the configuration data block as described in chapter
5.
• Transfer the project (all blocks) to the program memory of the standard
section of your PSS.

All the necessary preparations have now been carried out. Operation can
start.

• Connect the PSS to the operator device. The layout of the connection
cable is described in Chapter 7.
• As soon as both devices are ready for operation, the base message “No
error message” will appear, or, if there is an error, the corresponding
error text.

4-2 Operating Manual: ST SB FE MBS

Function Description

Error evaluation

Fault diagnostics is an important task in the operation of plant and

machinery. This is why Pilz GmbH &Co. provides a well co-ordinated error
evaluation system.

The software package ST SB FE MBS “Error Evaluation with PX(T) Text

Displays” is designed to make faults transparent.
It detects messages from the error stack of the PSS and decentralised I/O
modules (on SafetyBUS p), and also recognises error messages from the
standard function blocks of the MBS Modular Block System. An error that
has arisen can be displayed as a message text on an operator device (text
display or line-based operator terminal).

The software package ST SB FE MBS “Error Evaluation with PX(T) Text

Displays” does not take into account the specific error messages of the
PSS SF CPU (see System requirements in Chapter 2).

Operating Manual: ST SB FE MBS 5-1

Function Description

Principle function of the software package

Failsafe section PSS Standard section

PSS error
Error
SafetyBUS p error stack
(I/O-Devices) SB052
MBS_FE_9

DB015 SB050
FS-FE-PX DB015
Administr-
MBS SB ation SB254 Configura-
DB StBsCall tion DB

SB053
SB_Error

PILZ

Fig. 5-1: Operating principle of software package ST SB FE MBS

5-2 Operating Manual: ST SB FE MBS

Fault diagnostic concept

On the PSS, a distinction is made between internal and external errors.

Internal errors

Internal errors include program errors and system errors. These also
include errors that affect SafetyBUS p and errors from the decentralised
I/O modules.
These errors are entered in the error stack (see FS System Description,
Chapter 7).

Error processing

Failsafe section PSS Standard section

SB052
MBS_FE_9

Error stack SB050

FS-FE-PX

SB053
SB_Error

Message
number

e.g.: SB130

PILZ

Fig. 5-2: Sequence diagram for internal errors

Operating Manual: ST SB FE MBS 5-3

Function Description

Error stack

The error stack can record a maximum of 16 error entries. It is organised

as a ring memory. The error stack indicator always points to the data word
containing the error class of the current error. If more than 16 errors
occur, the first entry will be overwritten.

Evaluating the error stack

The error stack stores various parameters for each error:

• Error class
The error class describes the error in coded form. The error class is
displayed on the CPU display (see System Description). The
corresponding message number in the operator device is established via
the error class; some error classes may also require the error number.
• Error number
With error classes 06 (module error) and 82 (clock error), SB 050 also
requires the error number in order to establish the corresponding
message number in the operator device.
• Error location
This entry contains the Bit address of the faulty input or output. Not all
errors contain this entry.
• Error parameter
This entry contains the slot address. Not all errors contain this entry.

5-4 Operating Manual: ST SB FE MBS

Assigning error numbers to error classes

Error class Error number Key

F01...F05 01...05 —-
F06 51...169 Module error
F07 07 —-
F08 08 —-
F09 09 —-
F0C 11 —-
F12...F29 12...29 —-
F30...F35 170...190 SafetyBUS p
F41 41 —-
F70...F79 30...39 —-
F80...F81 40...41 —-
F82 191...193 Cycle error
F83...F84 43...44 —-
FB7 194 —-
FD6 176 —-
—- 48 Wrong error class
—- 49 Error in the stack cannot be found
—- 50 FS in stop mode through switch

INFORMATION
A detailed description of the error classes can be found in the “Error List”
in the “System Manual for the modular/compact PSS”.

Operating Manual: ST SB FE MBS 5-5

Function Description

External errors

External errors include hardware and operator errors from the MBS SBs.
These are errors that are detected while controlling and monitoring safety
devices (e.g. standard function block for feedback loop monitoring from
the MBS E-STOP package).

Failsafe section PSS Standard section

DB015 SB 052
MBS_FE_9
DW0001
.. DB015
SB of
MBS .
DW0200 DW0001
..
.
(Error code) SB254 DW0600
StBsCall
(Protection
circuit
type)

DB016 DB017

DW0001
.. DW0001
.. Message
. . number
DW0200 DW0200

e.g.: SB130

PILZ

Fig. 5-3: Sequence diagram for external errors

5-6 Operating Manual: ST SB FE MBS

 The relevant standard function block enters the external errors in
administration data blocks DB 015, DB 016 and DB 017 of the failsafe
section; the errors are then evaluated and processed.

Input parameter SSNR

A safety subroutine number (SSNR) must be assigned to each SB in the

MBS.
The input parameter SSNR is available within all the MBS standard
function blocks. It is required to manage the common DB 015 in the
failsafe section (see also Fig. 5-3).
Each SSNR must occur only once within a project. Further information on
the SSNR is available in the operating manuals for the respective MBS
package.

Administration data blocks from the failsafe section

The administration data blocks from the failsafe section are permanently
specified within the modular block system (MBS). Data words DW0001 ...
DW0200 contain information for hardware and operator errors (see also
Fig. 5-3).
Further information on administration data blocks DB 015, DB 016 and
DB 017 is available in the operating manuals for the respective MBS
packages.

Operating Manual: ST SB FE MBS 5-7

Function Description

Configuration data block in the standard section

The configuration data block in the standard section is required to evaluate

the error messages from the MBS SBs.
The configuration data block must be defined in the standard section of the
PSS. It must contain 1024 data words and be READ/WRITE.
When supplied, the configuration data block is set as DB 015 as a default.

DB 015
DW0000 Reserved
123456789012345678901234567890121234567890123456789
123456789012345678901234567890121234567890123456789
123456789012345678901234567890121234567890123456789
DW 0001 600 data words
to (DW number
DW 0600 SSNR)
123456789012345678901234567890121234567890123456789
123456789012345678901234567890121234567890123456789
DW 1001 DW for temporary
to data storage
DW 1023

The set parameters will depend on the plant configuration:

• SSNR
In the configuration data block, the data word number (DW0001 ...
DW0600) corresponds to the SSNR of the standard function block used
(MBS).
• Type of protection circuit
For each SSNR that is used, an identification code (type no.) must be
entered as a fixed point number in the corresponding data word (see List
of protection circuit types).
• Serial number of protection circuit type
(see section entitled “Structure and contents of a data word in the
configuration data block”).

NOTICE
DW 1001 to DW 1023 are reserved for temporary data storage.
These data words contain information that is absolutely essential for
correct functionality. For this reason, never use these data words in your
own applications.

5-8 Operating Manual: ST SB FE MBS

 Structure and contents of a data word in the configuration data block

Data word no. Coding Data contents

0001...0600 Data Left (DL): Data Right (DR):
Type no. of Serial no. of
protection circuit protection circuit
DW SSNR KY 001 ... 255 , 000 ... 255

Example:

Data word Data contents

DL DR
DW0014: 003, 010

Serial number of protection circuit type

In this case: Safety gate number 10

Type of protection circuit

In this case: SB 066 Safety gate

Data word number / SSNR

It is possible to expand the system using customised protection circuit

types or to edit existing types. The following relationship exists between
the type numbers and message numbers:

Message number (record) = (Type no. - 1) x 16 + Error bit + 200 + Offset

Type no. = 1...n

Error bit = 0...15
Offset = 100 for the supplied error text files

A maximum of 16 messages are possible for each protection circuit type.

In accordance with the SSNR, the error bits are read from data words
001...200 of the administration data blocks from the failsafe section.

Operating Manual: ST SB FE MBS 5-9

Function Description

List of protection circuit types

The description column contains the error texts that are stored under that
type number. Some SBs may be used differently.

Type no. Description SB

1 E-STOP to category 2 SB 060
2 E-STOP to category 4 SB 061
3 Safety gate SB 064/
SB 066
4 Safety gate SB 061
5 ESPE cycle SB 068
6 ESPE guard SB 066
7 ESPE SB 061
8 E-STOP to category 4 SB 062/
SB 063
9 Start-up disabler/reset lock SB 061
10 2-Hand SB 059
11 Foot switch SB 059
12 Operating mode selector switch SB 051/
SB 052
13 Feedback loop SB 065/
SB 067
14 PSV SB 080/
SB 081
15 Camshaft SB 074
16 Broken shearpin SB 077
17 Safety block SB 066
18 Pressure monitor SB 060
19 Cooling SB 060
20 Deadman switch SB 140
21 Gas detection plant SB 141
22 Monitoring ball valves SB 142
23 Level monitoring SB 143
24 Sequence control on presses SB 056

5-10 Operating Manual: ST SB FE MBS

 Type no. Description SB
25 Failsafe communication: receiver SB 111
26 Safety barrier SB 066
27 ESPE muting SB 072
28 Camshaft misalignment SB 079
29 Manual drive of PSV SB 084
30 Hydraulic valves SB 087,
SB 088,
SB 089
31 Enable switch SB 092
32 Hydraulic enable SB 058
33 Flame monitoring SB 150
34 Transient suppression SB 151
35 Burners: start and operator elements SB 152
36 Position monitoring of flap SB 153
37 Position monitoring of flaps/valves SB 154
38 Pre-purge SB 155
39 Tightness control SB 156
40 Ignition SB 158
41 Run SB 159
42 Blower SB 160
43 ESPE guard SB 069
44 Monitoring analogue values SB 104
45 Monitoring 2 from 3 SB 190
46 Monitoring analogue limit values SB 191
47 AKAS press brake protection SB 230
48 ESPE/AOPD monitoring SB 095
49 Monitoring muting lamps SB 097

Operating Manual: ST SB FE MBS 5-11

Function Description

Evaluation sequence for internal and external errors

Failsafe section PSS Standard section

Error
stack

Program cycle DB015 Program cycle

DB016
DB017 SB138
Adminis- OB001 Set
SB tration parameters
OB101 from DB for user
MBS DW0001 interface
..
.
SB DW0200
from
MBS (Error code)
DB015
SB052
MBS_FE_9 Configura-
tion-DB
SB050 DW0001
FS-FE-PX ..
.
DW0600

Message
number
+
Variables

e.g.: SB130

Call up
message
number

Program cycle Operator

Write to … device
PILZ
Read from …
The direction of the arrow shows the direction of data flow

Fig. 5-4: Error evaluation sequence from error stack and MBS SBs

5-12 Operating Manual: ST SB FE MBS

 SB 052 is the central block for error evaluation. It becomes active as soon
as an error is present from the error stack or one of the MBS SBs.

Error from the error stack:

• SB 052 activates SB 050 (FS-FE-PX) in the PSS standard section

• SB 050 (FS-FE-PX) reads the current error from the error stack.
• SB 050 (FS-FE-PX) uses the error code to establish the error class, the
error number, the error location (if available) and the error parameter (if
available).
• SB 050 (FS-FE-PX) uses the error code to calculate the message’s error
number.
The SB uses the offset (input parameter OSet) to calculate the message
number under which the corresponding message text is stored in the
display system.
• SB 052 establishes the message number of the message text, including
the corresponding variables.

Error from an MBS SB:

• SB 052 (MBS_FE_9) browses data words DW 0001 ... DW 0200 in the

administration data blocks (failsafe section). It is possible to browse a
maximum of 50 data words per cycle.
• SB 052 (MBS_FE_9) reads in the error (SSNR and error code).
• SB 052 uses the user-specific settings in the configuration data block to
establish the message number, including the corresponding variables.

Operating Manual: ST SB FE MBS 5-13

Function Description

Evaluation sequence including errors from decentralised

I/O modules

Failsafe section PSS Standard section

PSS error
Error
SafetyBUS p error stack
(I/O-Devices)
Program cycle
DB015 SB138
DB016
DB017 Set para-
Program cycle meters for
Adminis- OB001
tration user interface
OB101 SB from DB
MBS
DW0001
..
SB from . SB052 DB015
MBS DW0200 MBS_FE_9
Configura-
(Error code) SB050 tion-DB
FS-FE-PX
DW0001
..
.
SB254 DW0600

SB053
SB_Error
SB056
DOMAIN_0

Message
number
+
Variables

e.g.: SB130

The direction of the arrow Call up

message
shows the direction of data flow number

Program cycle
Write to … Display
Read from … PILZ

Fig. 5-5: Evaluation sequence including errors from decentralised I/O modules

5-14 Operating Manual: ST SB FE MBS

 SB 052 is the central block for error evaluation. It becomes active as soon
as an error is present from the error stack or one of the MBS SBs.

PSS error from the error stack:

• SB 052 activates SB 050 (FS-FE-PX) in the PSS standard section

• SB 050 (FS-FE-PX) reads the current error from the error stack.
• SB 050 (FS-FE-PX) uses the error code to establish the error class, the
error number, the error location (if available) and the error parameter (if
available).
If error class F-31 or F-32 is detected, there is a SafetyBUS p error
present (see below).
• SB 050 (FS-FE-PX) uses the error code to calculate the message’s error
number.
The SB uses the offset (input parameter OSet) to calculate the message
number under which the corresponding message text is stored in the
display.
• SB 052 establishes the message number of the message text, including
the corresponding variables.

Error from a decentralised I/O module (SafetyBUS p):

• SB 053 (SB_Error) checks whether there is an error of error class F-31

or F-32 present. If there is, Domain 0 of the affected I/O module will be
requested via the block SB 056.
• SB 053 evaluates the current error stack entry by error class and
parameter information and issues the message number, including the
corresponding variables.

Error from an MBS SB:

• SB 052 (MBS_FE_9) browses data words DW 0001 ... DW 0200 in the

administration data blocks (failsafe section). It is possible to browse a
maximum of 50 data words per cycle.
• SB 052 (MBS_FE_9) reads in the error (SSNR and error code).
• SB 052 uses the user-specific settings in the configuration data block to
establish the message number, including the corresponding variables.

Operating Manual: ST SB FE MBS 5-15

Function Description

Temporary flag range

Standard function blocks from the software package ST SB FE MBS

“Error Evaluation with PX(T) Text Displays” use the flag range M59.00 ...
M63.31 as temporary flags for storing information. This information is
updated and overwritten by the corresponding standard function blocks.

NOTICE
• Do not use flags from the temporary flag range for your own
applications.
Malfunctions may occur if you use the temporary flag range M59.00 ...
M63.31 for your own applications.
• If it is absolutely necessary to use this flag range, under no
circumstances should you use the flags as input parameters for standard
function blocks.

5-16 Operating Manual: ST SB FE MBS

Operator guidance, message texts and variables

Operator guidance and diagnostics with a Pilz operator device

A Pilz text display or operator terminal can be connected to the PSS user
interface (RS 232 C) for operator guidance and diagnostics. The operator
device is used to display error stack messages or error messages from the
MBS SBs as message texts. All message texts are stored in the operator
device. A message text may contain a maximum of two variables.

Message text files are available for certain Pilz text displays and operator
terminals (e.g. PX 30, PX 120). These message text files match the error
messages from the error stack and MBS SBs. The message text files are
ready to use and need only to be transferred to the operator device. The
message texts start from message number 100. They are therefore
designed for an offset OSet = 100 (see also SB 052).

The software package ST SB PXT “PSS Drivers for PX/PXT” is available

for the serial drive of Pilz operator devices.

In SB 052 there is an integral function enabling the device to scroll

automatically to the next error message after a preset time. Alternatively,
scrolling may also be carried out manually through a key operation.

Operating Manual: ST SB FE MBS 5-17

Function Description

Message texts for error stack messages

When evaluating the error stack, the parameters “Error location” and
“Error parameter” will be transferred, among others, if these entries are
available (see also “Evaluating the error stack” in the section entitled
“Fault diagnostic concept”).
These two parameters are transferred to the corresponding message text
as Variable 1 and Variable 2 and are inserted in the display (Fig. 5-6).

Fault on DOZ wire

on slot 2.21

Pilz

Variable 2
Error location: >Bit address<
Variable 1
Error parameter: >Slot address<

Fig. 5-6: Sample message text (internal error)

Note on Variable 2 (Bit address):

If this variable has the value 99, there is no valid information present for
the Bit address.
If several Bit addresses are affected when an error occurs, only the first
Bit address to be detected will be displayed.

5-18 Operating Manual: ST SB FE MBS

Message texts for error stack messages of decentralised I/O modules

If entries are available, parameters are transferred when evaluating the

error stack (see also “Evaluating the error stack” in the section entitled
“Fault diagnostic concept”).
The parameters are transferred to the corresponding message text as
Variable 1 and Variable 2 and are inserted in the display (Fig. 5-7).

Short circuit to +24 V

or 0V, output 35.02

Pilz

Variable 2
Error location: >Bit address<
Variable 1
Error parameter: Device address<

Fig. 5-7: Sample message text (SafetyBUS p error)

Operating Manual: ST SB FE MBS 5-19

Function Description

Message texts for error messages from MBS standard function blocks

When evaluating the configuration data block (standard section), the serial
number of the protection circuit type is transferred (see also section
entitled “Configuration data block in the standard section”, in this chapter).
The serial number of the protection circuit type is transferred to the
corresponding message text in the display as a variable. On error
messages from MBS SBs, only one variable is tranferred.

E-STOP 017
Operated

Pilz

Variable 1
Serial number of protection circuit type

Fig. 5-8: Sample message text (external error)

5-20 Operating Manual: ST SB FE MBS

Standard Function Blocks

SB 050 (FS-FE-PX): Decoding the error stack messages

Block header

SB050
FS-FE-PX

W- SBG1 FeNr - W
W- SBG2 PARA - W
W- GRP1 ORT - W
W- GRP2
W- OSet

Input parameters

SBG1: Status of I/O-Groups 0...15 (flag word 1)

(RUN or STOP condition of SafetyBUS p I/O-Groups)
This is where the status of SafetyBUS p I/O-Groups 0...15,
determined via flag word MW 116.00, is transferred to the
block (see section entitled “Setting parameters”).
(If SafetyBUS p is not used: SBG1 = KH0000)
SBG2: Status of I/O-Group 16...31 (flag word 2)
This is where the status of SafetyBUS p I/O-Groups 16...31,
determined via flag word MW 116.16, is transferred to the
block (see section entitled “Setting parameters”).
(If SafetyBUS p is not used: SBG2 = KH0000)
GRP1: I/O-Groups in the range 0...15 (word 1)
Enter all the configured SafetyBUS p I/O-Groups in the range
0...15 (see section entitled “Setting parameters”).
(If SafetyBUS p is not used: GRP1 = KH0000)
GRP2: I/O-Groups in the range 16...31 (word 2)
Enter all the configured SafetyBUS p I/O-Groups in the range
16...31 (see section entitled “Setting parameters”).
(If SafetyBUS p is not used: GRP2 = KH0000)

Operating Manual: ST SB FE MBS 6-1

Standard Function Blocks

OSet: Offset input

The offset determines the message number in the operator
device from which the error texts from the error stack begin
(failsafe operating system messages).
The message texts supplied with the software package are
made for an offset = 100.

Output parameters

FeNr: Message number

Offset + established error number = Message number in the
text display
PARA: Parameter
Provided a parameter is stated in the error stack, this output
parameter will contain the slot address of the faulty PSS
module or stopped I/O-Group.
ORT: Location information
Provided this parameter is stated in the error stack, this output
parameter will contain the bit address of the faulty input/output
or the address of the faulty I/O-Device.

Function

The SB decodes the error messages from the error stack. It reads the
error parameters stored in the error stack for each error, and calculates
the message number that corresponds to the error in the operator device.

Setting parameters

• The following I/O-Group assignment is valid for input parameters SBG1,

SBG2, GRP1 and GRP2:

6-2 Operating Manual: ST SB FE MBS

 Bit: 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
SBG1 and GRP1: I/O-Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I/O-Group
15 0
SBG2 and GRP2: I/O-Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I/O-Group
31 16

• Input parameters SBG1 and SBG2 cannot be assigned directly to the

I/O-Group status flags (flag words MW116.00 and MW116.16). Instead,
transfer the status flags to freely definable flag words and assign the
input parameters SBG1 and SBG2 to these flag words.
• Each configured I/O-Group must have a logic 1 stated in the actual
parameters for GRP1 and GRP2.
• If you are not using SafetyBUS p, input parameters SBG1, SBG2, GRP1
and GRP2 must be assigned the value 0 (KH0000).
• Initialise the actual parameters at the output parameters before calling
up the block.

Temporary flags used

M59.00 ... M63.31

INFORMATION
Malfunctions may occur if you use the temporary flag range for your own
applications.
These flags are not suitable in your own applications for use as:
• Input and output parameters on SB 050 (FS-FE-PX)
• Global flags

Blocks required
None

Operating Manual: ST SB FE MBS 6-3

Standard Function Blocks

SB 052 (MBS_FE_9): Evaluating the error messages from the error stack
and MBS standard function blocks

Block header

SB052
MBS_FE_9

D - DB SATZ + W
W - SBG1 VAR1 + W
W - SBG2 VAR2 + W
W - GRP1
W - GRP2
X - MBS
X - XMBS
W - OSet
X - AuSc
X - SCRO
Z - TIME
W - TVal

Input parameters

• DB : Configuration data block

Range: 10...255; Format: D (data block)
Length of DB: 1024 words (read/write)
We recommend you use the supplied data block DB015.
• SBG1 : Status of I/O-Groups 0...15 (flag word 1) (RUN or STOP
condition of SafetyBUS p I/O-Groups)
This is where the status of SafetyBUS p I/O-Groups 0...15,
determined via flag word MW 116.00, is transferred to the
block (see section entitled “Setting parameters”).
(If SafetyBUS p is not used: SBG1 = KH0000)
• SBG2 : Status of I/O-Group 16...31 (flag word 2)
This is where the status of SafetyBUS p I/O-Groups 16...31,
determined via flag word MW 116.16, is transferred to the
block (see section entitled “Setting parameters”).
(If SafetyBUS p is not used: SBG2 = KH0000)

6-4 Operating Manual: ST SB FE MBS

 • GRP1 : SafetyBUS p I/O-Groups in the range 0...15 (word 1)
Enter all the configured SafetyBUS p I/O-Groups in the range
0...15 (see section entitled “Setting parameters”).
(If SafetyBUS p is not used: GRP1 = KH0000)
• GRP2 : I/O-Groups in the range 16...31 (word 2) Enter all the
configured SafetyBUS p I/O-Groups in the range 16...31 (see
section entitled “Setting parameters”).
(If SafetyBUS p is not used: GRP2 = KH0000)
• MBS: Select evaluation of MBS messages
This input determines whether the error stack alone is
evaluated or the MBS messages also.
MBS = 0: Evaluate error stack only
MBS = 1: Evaluate error stack and MBS messages
• XMBS Select evaluation of MBS messages in data blocks DB016 and
DB017 (expanded MBS)
This input determines whether DB015 alone (SSNR 1-200) is
evaluated or DB016 and DB017 (SSNR 201-600) also.
XMBS = 0: Evaluate DB015 only
XMBS = 1: Evaluate DB015, DB016 and DB017
• OSet : Offset input
The offset determines the message number from which the
error texts begin in the display system.
If you are using the supplied error texts, set this parameter to
KF000100.
• AuSc : Autoscroll input
This input is used to determine whether to scroll to the next
error message automatically after a preset time or manually via
the scroll input. Scrolling will only occur if the FS section is in a
RUN condition.
AuSc = 0: Manual scrolling via input SCRO
AuSc = 1: Automatic scrolling via timer
• SCRO : Scroll input
The scroll input SCRO can be used to scroll to the next error
message if the FS section is in a RUN condition.
SCRO = 0/1-pulse edge: Look for next error message.
SCRO = 0: Scrolling is not required

Operating Manual: ST SB FE MBS 6-5

Standard Function Blocks

• TIME: Timer to set the interval for automatic scrolling

This parameter should be assigned an available timer from the
range T000...T063.
• TVal: Time value to set the interval for automatic scrolling in seconds
We recommend you set this parameter to KF000006
(6 seconds).

Output parameters

• SATZ : Established message number

• VAR1 : Variable 1 belonging to the established message number
• VAR2 : Variable 2 belonging to the established message number

Function

SB 052 evaluates the error messages from the MBS SBs.

SB 052 establishes the message number that corresponds to the error
message, including any accompanying variables.

Setting parameters

• The following I/O-Group assignment is valid for input parameters SBG1,

SBG2, GRP1 and GRP2:

Bit: 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
SBG1 and GRP1: I/O-Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I/O-Group
15 0
SBG2 and GRP2: I/O-Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I/O-Group
31 16

• Input parameters SBG1 and SBG2 cannot be assigned directly to the

I/O-Group status flags (flag words MW116.00 and MW116.16). Instead,
transfer the status flags to freely definable flag words and assign the
input parameters SBG1 and SBG2 to these flag words.
• Each configured I/O-Group must have a logic 1 stated in the actual
parameters for GRP1 and GRP2.

6-6 Operating Manual: ST SB FE MBS

 • If you are not using SafetyBUS p, input parameters SBG1, SBG2, GRP1
and GRP2 must be assigned the value 0 (KH0000).
• Initialise the actual parameters at the output parameters before calling
up the block.

Temporary flags used

M59.00 ... M63.31

INFORMATION
Malfunctions may occur if you use the temporary flag range for your own
applications.
These flags are not suitable in your own applications for use as:

• Input and output parameters on SB 052 (MBS_FE_9)

• Global flags

Blocks required

• DB 015: Administration data block (PSS failsafe section)

(Required if MBS = 1)
• DB 016/DB 017: Administration data block (PSS failsafe section)
(Required if XMBS = 1[expanded MBS])
• DB XXX:Configuration data block (PSS standard section)
• SB 050 (FS-FE-PX): Decoding the error stack messages
• SB 254 (StBsCall): For calling up the operating system

Operating Manual: ST SB FE MBS 6-7

Standard Function Blocks

SB 053 (SB_Error): Evaluating the error stack messages of

decentralised I/O modules

Block header

SB053
SB_Error

W- Err SATZ - W
W- Dev VAR1 - W
W- DB_S VAR2 - W
W- DB_T
W- OSet

Input parameters

• Err : Error
Error code (record number) generated by SB 052 (output
parameter SATZ of SB 052)
• Dev : Device
Device address of the affected I/O module (output parameter
VAR2 of SB 052)
• DB_S : DataBlock Source
Data block in which the unformatted error stack of the I/O-
Device is stored (source DB)
Range: 10...255; Format: B (Byte)
Length of DB: 1024 words (Read/Write)
• DB_T : DataBlock Target
Data block in which the formatted error stack of the I/O-Device
is stored (target DB)
Range: 10...255; Format: B (Byte)
Length of DB: Min. 96 words (Read/Write)

INFORMATION
Different data blocks must be stated for input parameters DB_S and
DB_T. The configuration data block may not be used as an input
parameter.

6-8 Operating Manual: ST SB FE MBS

 OSet: Offset
The offset determines the message number from which the
error texts begin in the operator device.

Output parameters

• SATZ : Established message number

• VAR1 : Variable 1 belonging to the established message number
(Device address or cycle number)
• VAR2 : Variable 2 belonging to the established message number (Bit
information input/output or I/O-Group)

Function

SB 053 is an add-on block for SB 052, for PSS systems with SafetyBUS p
and decentralised I/O modules.
SB 053 will only run on SafetyBUS p-compatible PSS CPUs.

Assignment of I/O module error classes to error numbers:

Error class/ Error- Key

no. number
F-08 178 Power-on
F-63 179 Configuration error
F-64/0-6 180...186 I/O error
F-67 188 Supply voltage is missing
F-69/0 189 Group start
F-69 187 Bridge error
F-E3 179 Configuration error
F-E4/0-6 180...186 I/O error
F-E7 188 Supply voltage is missing
F-E9 187 Bridge error
Other 190 Bus, configuration or internal error
177 No SafetyBUS p communication

Operating Manual: ST SB FE MBS 6-9

Standard Function Blocks

Setting parameters

• The block must be called in each cycle, after SB 052.

• The actual parameters at output parameters SATZ and VAR2 of SB 052
should be stated as input parameters Err and Dev and output
parameters SATZ and VAR2 on SB 053.
• Input parameter OSet and output parameter VAR1 must also be the
same on both blocks.

Temporary flags used

M59.00 ... M63.31

INFORMATION
Malfunctions may occur if you use the temporary flag range for your own
applications.
These flags are not suitable in your own applications for use as:
• Input and output parameters on SB 053 (SB_Error)
• Global flags

Blocks required

• DB_S: Data block with a length of 1024 words (Read/Write)

• DB_T: Data block with a minimum length of 96 words (Read/Write)
• SB 056 (DOMAIN_0): Reading Domain 0 of a SafetyBUS p subscriber
• SB 254 (StBsCall): For calling up the operating system

6-10 Operating Manual: ST SB FE MBS

Example

Application example

The example is intended to help you integrate the software package ST

SB FE MBS into your own application.
The following features are considered in the application below:

• Initialisation of the user interface with SB 138 (INIT)

• Error evaluation with SB 052 (MBS_FE_9)
• Driving a text display with SB 130 (PX_30) via the RS 232-C user
interface on a PSS
• Transfer of message text numbers and variables

Blocks required:

• SB 050 (FS-FE-PX), PSS standard section

• SB 052 (MBS_FE_9), PSS standard section
• SB 130 (PX_30), PSS standard section
from the software package ST SB PXT
• SB 138 (INIT), PSS standard section
from the software package ST SB PXT
• SB 254, PSS standard section
• DB 015, configuration data block in the PSS standard section

INFORMATION
Flags that are used to set the SB parameters should be viewed as
examples. All available flags can be used to set the block parameters.

Operator guidance and diagnostics do not have to be routed via a

text display or line-based operator terminal. The message numbers and
their corresponding variables may be processed using a different method
(e.g. via a bus system etc.).

INFORMATION
The CD contains another application example for use with a PXT operator
terminal. This example uses SB 221 from the software package ST SB
PXT.

Operating Manual: ST SB FE MBS 7-1

Example

Connection cable between PSS and text display

Serial drive of the text display (PX 30/PX120) is via the PSS user interface
(RS 232-C interface). The layout of the connection cable is as follows:

PSS Display
Male 9-pin D-Sub connector Male 9-pin D-Sub connector

RxD 2 3 TxD
TxD 3 2 RxD
Ground 5 5 Ground
DTR 4 4 DTR
DSR 6 6 DSR
RTS 7 7 RTS
CTS 8 8 CTS

Screening Screening

Fig. 7-1: Connection cable

A ready-made cable is available from Pilz under order no. 301 965.

Initialising the PSS user interface

The PSS user interface must be set to the same parameters as the text
display. Initialisation can be performed via SB 138 (INIT). SB 138 is a
component part of the software package ST SB PXT “PSS Drivers for
PX/PXT”.

Initialise the interface with the following input parameters:

• BAUD: 9600 KBit/s

• PARI: No parity
• STOP: 1 stop bit
• DAT: 8 data bits

7-2 Operating Manual: ST SB FE MBS

 • HS: Without handshake
• PROT: Communicate with ISI protocol

SB138
INIT

M00.00 - INOK SATZ - MW10.00

KF6 - BAUD
KF0 - PARI
KF0 - STOP
KF3 - DAT
KF0 - HS
KF1 - PROT

Fig. 7-2: Initialising the user interface

A flag bit (in this case M00.00) must be assigned to input parameter INOK.
This flag bit can be selected at will.

INFORMATION
Reset the flag bit of input parameter INOK before SB 138 is called for the
first time (e.g. in OB 020).

Call SB 138 at the start of OB 001. This will ensure that the user interface
is initialised when you drive the display via your application program.

Output parameter SATZ should be assigned the same flag word that will
be used to store the message number of the display text in your
application program (in this case MW 10.00). This will simplify your
application program.

Operating Manual: ST SB FE MBS 7-3

Example

Incorporating SB 052 (MBS_FE_9), PSS standard section

SB 052 evaluates the error stack messages and the error messages from
the MBS SBs. It establishes the message number in the display that
corresponds to the error message.

For this reason, SB 052 accesses several different blocks. These blocks
must be available within the application program and have their
parameters set correctly:
• Browse DB 015, DB 016 and DB 017 (failsafe section)/DW0001 ...
DW0200 to determine the error code and SSNR
(MBS = 1 and XMBS = 1)
• Access DB 015 (standard section)/DW0000 ... DW0600
- Contents: user-specific plant data (SSNR, protection circuit type and
serial number of protection circuit.)
The serial number of the protection circuit is always inserted into the
message text as a variable.
- Required to establish the error messages from the MBS SBs
Further information can be found in Chapter 5, under “Configuration data
block DB 015 from the standard section”.
• Call SB 050 (FS-FE-PX) internally
- Required for the error stack messages

INFORMATION
SB 050 (FS-FE-PX) is called automatically via SB 052. You do not need to
incorporate SB 050 (FS-FE-PX) into your application program.

7-4 Operating Manual: ST SB FE MBS

 :L MW 116.00 .SBus_Gr. MW_00 SBUSp Status-MW I/O-Group 00...15,
RUN = 1
:T MW 016.00 .SB-Groups00
:L MW 116.16 .SBus_Gr.MW_16 SBUSp Status-MW I/O-Group 16...31,
RUN = 1
:T MW 016.16 .SB-Groups16
:CAL SB052

SB052
MBS_FE_9

DB 015 - D - DB SATZ -W- MW 010.00

MW 016.00 - W- SBG1 VAR1 -W- MW 010.16
MW 016.16 - W- SBG2 VAR2 -W- MW 011.00
KM 00000000 00010100 - W- GRP1
KM 00000000 00010000 - W- GRP2
M 110.01 - X - MBS
M 110.01 - X - XMBS
KF 000100 - W- OSet
E 00.00 - X - AuSc
E 00.01 - X - SCRO
T 000 - Z - TIME
KF 000006 - W- TVal

• Configured I/O-Groups: 2, 4, 20

Operating Manual: ST SB FE MBS 7-5

Example

Incorporating SB 053 (SB_Error), PSS standard section, only in conjunction with

SafetyBUS p

SB 053 is an add-on block for SB 052, for PSS systems with SafetyBUS p
and decentralised I/O modules. If SB 052 has detected errors on
SafetyBUS p, this block will evaluate the error stack on the affected I/O
module.

For this reason, SB 053 accesses several different blocks. These blocks
must be available within the application program and have their
parameters set correctly:
• Access DB_S (in this case DB 019 in the standard section)
The unformatted device error stack is stored in this data block.
• Access DB_T (in this case DB 020 in the standard section)
The formatted error stack is stored in this data block.
• Call SB 056 (DOMAIN_0) internally
Reads and formats the device error stack.

INFORMATION
SB 056 is called automatically via SB 053. You do not need to incorporate
SB 056 into your application program separately.

7-6 Operating Manual: ST SB FE MBS

 :CAL SB 053

SB053
SB_Error

MW 010.00 - Err SATZ - MW 10.00

MW 011.00 - Dev VAR1 - MW 10.16
KB 019 - DB_S VAR2 - MW 11.00
KB 020 - DB_T
KF 000100 - OSet

INFORMATION
Different data blocks must be stated for input parameters DB_S and
DB_T. The configuration data block may not be used as an input
parameter.

The actual parameters at output parameters SATZ and VAR2 of SB 052

should be stated as input parameters Err and Dev and output parameters
SATZ and VAR2 on SB 053. Input parameter OSet and output parameter
VAR1 must also be the same on both blocks.

Operating Manual: ST SB FE MBS 7-7

Example

Transferring message numbers to a display

It is possible to call up a message text on a text display (PX 30/PX120) via

the message number and to insert any corresponding variables into the
message text.
Serial drive of the text display is via SB 130.

SB130
PX_30

M00.00 - INOK FEHL - MW11.16

MW10.00 - SATZ
KB10 - DB
KF1 - SLAV
KF0 - SBET
MW10.16 - Var1
MW11.00 - Var2

Fig. 7-3: Setting parameters for SB 130

• DB: You will need to generate the DB (in this case DB 010). It must
be at least 13 data words in length.
• SLAV: In this case the display was assigned Slave number 1 (KF1).
• SBET: In this case the display was assigned no special operating
mode (KF0).

INFORMATION
Provided no user-specific message texts are to be called:
Incorporate SB 052, SB 053 and SB 130 one after the other at the end of
your application program in the PSS standard section.

7-8 Operating Manual: ST SB FE MBS

 PX 30 and PX 120 text displays have text files available which match the
error messages from the error stack and MBS SBs. These text files are
ready to use and need only to be transferred to the text display. The
message texts start from message number 100. They are therefore
designed for an offset OSet = 100 (see also SB 052).

User-defined message numbers

If you wish to call up other (user-defined) messages on the text display in

addition to the error messages, you will need to prioritise the message
numbers. This means you must decide which message numbers are to be
handled as a priority.

We recommend one of the following procedures:

Error message numbers have priority

• If no error is present, SB 052 issues the base message (prompt: “Is an

error present?”).
In the example, this is message number 298.
Message: “No error message present”
• Provided no error is present, input parameters SATZ, Var1 and Var2
from SB 130 may be overwritten by user-defined message numbers and
variables (in this case: MW10.00, MW10.16 and MW11.00).
• If an error is present, SB 052 transfers the message number including
variables to SB 130.

User-defined messages have priority

• Prompt: “Is a user-defined message text to be called up?”

• Yes: Message number is transferred to the display via SB 130
• No: Message number from SB 052 is transferred to the text display via
SB 130

Operating Manual: ST SB FE MBS 7-9

Example

Program listing

OB001
ST-PROG

V24.-INIT : Segment 00
// Initialising the V24 user interface on the PSS
// Resetting the INOK flag M 00.00 on PSS cold start/warm start

:L M 112.03 .ST_status_03 status ST, warm start ST STOP > RUN

:O M 112.04 .ST_status_03 status ST, cold start FS OFF > RUN
:R M 000.00
:CAL SB 138

SB138
Init

M 000.00 - X - INOK SATZ - W - MW 010.00

KF 000006 - W - BAUD
KF 000000 - W - PARI
KF 000000 - W - STOP
KF 000003 - W - DAT
KF 000000 - W - HS
KF 000001 - W - PROT

******************************************************************************************************************************
* M 112.03 .ST_status_03 status ST, warm start ST STOP > RUN *
* M 112.04 .ST_status_04 status ST, cold start FS OFF > RUN *
*****************************************************************************************************************************

Program : Segment 01
// ST application program follows at this point
:
:

7-10 Operating Manual: ST SB FE MBS

FE evaluation: Segment 02
// Evaluating the errors from the MBS blocks and FS error stack
// E 00.00 Input for selecting manual/automatic scrolling
// E 00.01 Input for scrolling error messages that are present
// MW 10.00 Flag word containing the record number to be issued
// MW 10.16 Variable 1 belonging to the record number to be issued
// MW 11.00 Variable 2 belonging to the record number to be issued

// Configured I/O-Groups: 2, 4, 20
// Parameters set for SafetyBUS p group flag words only when using CPUs
// with SafetyBUS p!
// When using CPUs without SafetyBUS p, input parameters
// SBG1, SBG2, GRP1 and GRP2 must be assigned KH0000.

:L MW 116.00 .SBus_Gr. MW_00SBUSp group flag word Gr. 0 to 15

:T MW 016.00 .SB-Groups00
:L MW 116.16 .SBus_Gr.MW_16 SBUSp group flag word Gr. 16 to 31
:T MW 016.16 .SB-Groups16
:CAL SB 052

SB052
MBS_FE_9

DB 015 - D - DB SATZ -W- MW 010.00

MW 016.00 - W- SBG1 VAR1 -W- MW 010.16
MW 016.16 - W- SBG2 VAR2 -W- MW 011.00
KM 00000000 00010100 - W- GRP1
KM 00000000 00010000 - W- GRP2
M 110.01 - X - MBS
M 110.01 - X - XMBS
KF 000100 - W- OSet
E 000.00 - X - AuSc
E 000.01 - X - SCRO
T 000 - Z - TIME
KF 000006 - W- TVal

Operating Manual: ST SB FE MBS 7-11

Example

DIO-Stack :Segment 03
// Call DIO-Stack evaluation only required when using SafetyBUS p
// Output parameters SATZ and VAR2 from SB 052 are transferred to
// SB 053 as input parameters.
// The actual parameters at output parameters SATZ, VAR1 and VAR2
// must be identical on both blocks!
// The values at input parameter OSet must also be the same.

:CAL SB 053

SB053
SB-Error

MW 010.00 .Record - W- Err SATZ - W - MW 010.00 .Record

MW 011.00 .Variable2 - W- Dev VAR1 - W - MW 010.16 .Variable1
KB 019 -B - DB_S VAR2 - W - MW 011.00 .Variable2
KB 020 -B - DB_T
KF 000100 - W- OSet

Text display : Segment 04

// Serial drive of PX 30 / PX 120 text display

:CAL SB 130

SB 130
PX_30

M 000.00 -X - INOK FEHL - W - MW 011.16

MW 010.00 - W- SATZ
KB 010 -B - DB
KB 001 -B - SLAV
KB 000 -B - SBET
MW 010.16 - W- Var1
MW 011.00 - W- Var2

Block end : Segment 04

:BE

7-12 Operating Manual: ST SB FE MBS

 Notes

Operating Manual: ST SB FE MBS 7-13

Example

Notes

7-14 Operating Manual: ST SB FE MBS

Appendix

Standard function blocks: current versions

INFORMATION
Please note:
Details of any final version changes that were too late to be included in this
documentation can be found in the “release.txt” file on the supplied CD.

INFORMATION
This manual is intended exclusively for use with the standard function
block versions listed below.

Older SB versions may differ from the description given in this manual. A
description of the changes made during a version upgrade can be found in
the section entitled “Amendment list”.

The version number can be determined from the information stated in an

SB’s block header (date and time).

SB No. Name Date Time Version

SB 050 (ST)* FS-FE-PX 22.07.03 14:28 1.4
SB 052 (ST)* MBS_FE_9 18.07.03 14:49 2.0
SB 053 (ST)* SB_Error 18.07.03 14:49 1.1
SB 056 (ST)* DOMAIN_0 03.08.01 09:53 1.0
* Encrypted block

INFORMATION
Always use the current version of the standard function block for your
application program.

Operating Manual: ST SB FE MBS 8-1

Appendix

Amendment list

INFORMATION
When imported into existing projects, new parameters must be set for
standard function blocks in which input or output parameters have been
amended (additional I/O parameters, notation changed, description
changed etc.).

Please note:

STOP
An SB version marked with this symbol can only replace the
previous SB version in an existing application program if new
parameters are set for it once imported.

SB 050 (FS-FE-PX): Decoding the error stack messages

Version Date Time

1.0 24.04.96 14:14
1.1 28.05.97 16:04
1.2 03.08.00 10:17
1.3 25.01.02 11:49 STOP

1.4 22.07.03 14:28

Changes from Version 1.0 to Version 1.1

• Internal optimisation

Changes from Version 1.1 to Version 1.2

• Integration of error class F-29

• Integration of error classes F30...F-34, F-D6 (SafetyBus p), F-B7
(system error)
• Evaluation of cycle errors (F-82) improved

8-2 Operating Manual: ST SB FE MBS

 Changes from Version 1.2 to Version 1.3

• New input parameters SBG1, SBG2, GRP1 and GRP2, which are used
to transfer the configured I/O-Groups plus the status of the I/O-Groups.
The SafetyBUS p error message is reset if all configured I/O-Groups are
active.

Changes from Version 1.3 to Version 1.4

• Update of evaluated error classes/error numbers.

SB 052: Evaluating the error messages from the error stack and MBS standard
function blocks

Version Date Time

1.0 26.09.97 09:52
1.1 31.05.00 09:11
1.2 10.12.01 12:03 STOP

2.0 18.07.03 14:49 STOP

Changes from Version 1.0 to Version 1.1

• “No error message” now hidden when scrolling. It jumps straight to the
first message.
• Block SB 050 is now also run if the FS section is in RUN mode. Nothing
is displayed if the last message is FS-20 cold start. This means that
SafetyBUS messages are also displayed if the FS section is in RUN
mode.
• Scrolling has been expanded. If a message that does not stop the FS
section is stored in the error stack, the scroll input can be used to poll the
existing MBS error messages. The last error stack entry will reappear
after the last MBS message. It is not possible to scroll when the FS
section is in STOP. The last error stack entry is displayed.
• The reserved data word range in DB 015 has been expanded to include
DW 208.
• SB 062 (E-STOP Category 4) has been defined as protection circuit type
8. The previous protection circuit type 8 (safety mat) has been removed
without replacement.
• Two new protection circuit types have been included: 43 ESPE guard
(SB 069) and 44 Remanent data (SB 253).

Operating Manual: ST SB FE MBS 8-3

Appendix

Changes from Version 1.1 to Version 1.2

• New input parameters SBG1, SBG2, GRP1 and GRP2, which are used
to transfer the configured I/O-Groups plus the status of the I/O-Groups.
• Faulty operation of SB 052 when a 1-signal was applied to input
parameter SCRO at the same time a SafetyBUS error occurred has now
been rectified. An incorrect initialisation meant that, if these conditions
arose, SB 052 no longer functioned correctly.

Changes from Version 1.2 to Version 2.0

• Range of SSNRs that are checked was expanded to 600. Data blocks
DB015, DB016 and DB017 in the PSS FS section are examined.
• The number of data words checked each PSS cycle was increased from
25 to 50.
• New input parameter to select the configuration data block. The supplied
configuration data block DB015 was expanded to 1024 data words and
new types of protection circuit were added. Data words DW1001 to
DW1023 are used for internal data.
• New input parameter MBS, used to select evaluation of MBS messages.
• New input parameter XMBS, used to select evaluation of data blocks
DB016 and DB017, in which the error words for SSNR 201 to 600 are
stored.
• New input parameter to select the automatic time-controlled scrolling
function for error messages:
AuSc: Select time-controlled scrolling
TIME: Timer for the scroll interval
TVal: Time value for the scroll interval

8-4 Operating Manual: ST SB FE MBS

SB053: (SB_Error): Evaluating the error messages from the error stack of
decentralised I/O modules

Version Date Time

1.0 21.02.02 15:20
1.1 18.07.03 14:49

Changes from Version 1.0 to Version 1.1

• The error stack on the selected device is read and evaluated at fixed
intervals. The values that are output are therefore updated regularly.

Amendments to text files

The following changes have been made to the message text files from the
previous version:

• Protection circuit type 44 (remanent data) has been removed.

• The following protection circuit types have been introduced:
Type 44 Recording analogue values (SB104) Record nos. 988-1003
Type 45 Select 2 from 3 (SB190) Record nos. 1004-1019
Type 46 Monitoring limit values (SB191) Record nos. 1020-1035
Type 47 AKAS (SB230) Record nos. 1036-1051
Type 48 Muting (SB095) Record nos. 1052-1067
Type 49 Monitoring muting lamps (SB097) Record nos. 1068-1083
• The following protection circuit types have been adapted:
Type 03 Safety gate: Adapted for SB064 Record nos. 338-339
Type 08 E-Stop: Also suitable for SB063
Type 13 Feedback loop: Adapted for SB065 Record no. 501
• Record numbers 108, 109, 141, 268, 275 expanded / corrected (error
stack messages)

Operating Manual: ST SB FE MBS 8-5

Appendix

Changes in the documentation

Changes from Version III to Version IV

The manual was completely revised and restructured.

Changes in Version 19 406-05

The manual was completely revised and restructured.

8-6 Operating Manual: ST SB FE MBS

A DK IRL PRC
Pilz Ges.m.b.H. Pilz Skandinavien K/S Pilz Ireland Industrial Automation Pilz China Representative Office
Modecenterstraße 14 Ellegaardvej 25 L Cork Business and Technology Park Rm. 302
1030 Wien 6400 Sonderborg Model Farm Road No. 88 Chang Shu Road
Austria Denmark Cork Shanghai 200040
Telephone: 01 7986263-0 Telephone: 74436332 Ireland China
Telefax: 01 7986264 Telefax: 74436342 Telephone: 021 4346535 Telephone: 021 62493031
E-Mail: [email protected] E-Mail: [email protected] Telefax: 021 4804994 Telefax: 021 62493036
E-Mail: [email protected] E-Mail: [email protected]

AUS E
Pilz Australia Pilz lndustrieelektronik S.L. J ROK
Industrial Automation LP. Camí Ral, 130 Pilz Japan Co., Ltd. Pilz Korea Office
9/475 Blackburn Road Polígono Industrial Palou Nord Shin-Yokohama Fujika Building 5F 402 Samsung Midas Officetel
Mt. Waverley, Melbourne VIC 3149 08400 Granollers 2-5-9 Shin-Yokohama 775-1, Janghang-Dong,
Australia Spain Kohoku-ku Ilsan-Gu, Koyang-Si
Telephone: 03 95446300 Telephone: 938497433 Yokohama 222-0033 Kyungki-Do 411-837
Telefax: 03 95446311 Telefax: 938497544 Japan Korea
E-Mail: [email protected] E-Mail: [email protected] Telephone: 045 471-2281 Telephone: 031 8159541
Telefax: 045 471-2283 Telefax: 031 8159542
E-Mail: [email protected] E-Mail: [email protected]
B L F
Pilz Belgium Pilz France Electronic
Bijenstraat 4 1, rue Jacob Mayer MEX SE
9051 Gent (Sint-Denijs-Westrem) BP 12 Pilz de Mexico, S. de R.L. de C.V. Pilz Skandinavien K/S
Belgium 67037 Strasbourg Cedex Circuito Pintores # 170 Energigatan 10 B
Telephone: 09 3217570 France Cd. Satelite 43437 Kungsbacka
Telefax: 09 3217571 Telephone: 03 88104000 C.P. 53100 Sweden
E-Mail: [email protected] Telefax: 03 88108000 Naucalpan de Juarez, Edo. de Mexico Telephone: 0300 13990
E-Mail: [email protected] Mexico Telefax: 0300 30740
Telephone: 55 5572 1300 E-Mail: [email protected]
BR Telefax: 55 5572 4194
Pilz do Brasil Sistemas Eletrônicos FIN E-Mail: [email protected]
Industriais Ltda. Pilz Skandinavien K/S TR
Rua Ártico, 123 - Jd. do Mar Pakilantie 61 Pilz Elektronik Güvenlik Ürünleri
09726-300 00660 Helsinki NL ve Hizmetleri Tic. Ltd. †ti.
São Bernardo do Campo - SP Finland Pilz Nederland Tan i‡ Merkezi
Brazil Telephone: 09 27093700 Postbus 186 Kükürtlü Caddesi No: 67
Telephone: 11 4337-1241 Telefax: 09 27093709 4130 ED Vianen C-Blok Daire: 1
Telefax: 11 4337-1242 E-Mail: [email protected] Netherlands 16080 Bursa
E-Mail: [email protected] Telephone: 0347 320477 Turkey
Telefax: 0347 320485 Telephone: 0224 2360180
GB E-Mail: [email protected] Telefax: 0224 2360184
CH Pilz Automation Technology E-Mail: [email protected]
Pilz lndustrieelektronik GmbH Willow House, Medlicott Close
Gewerbepark Hintermättli Oakley Hay Business Park NZ
Postfach 6 Corby Pilz New Zealand USA
5506 Mägenwil Northants NN18 9NF 3 Kohanga Road Pilz Automation Safety L.P.
Switzerland United Kingdom Managere Bridge 7150 Commerce Boulevard
Telephone: 062 88979-30 Telephone: 01536 460766 Auckland Canton
Telefax: 062 88979-40 Telefax: 01536 460866 New Zealand Michigan 48187
E-Mail: [email protected] E-Mail: [email protected] Telephone: 09-6345350 USA
Telefax: 09-6345350 Telephone: 734 354-0272
E-Mail: [email protected] Telefax: 734 354-3355
D I E-Mail: [email protected]
Pilz GmbH & Co. KG Pilz ltalia Srl
Sichere Automation Via Meda 2/A P
Felix-Wankel-Straße 2 22060 Novedrate (CO) Pilz Industrieelektronik S.L.
73760 Ostfildern Italy R. Eng Duarte Pacheco, 120
Germany Telephone: 031 789511 4 Andar Sala 21
Telephone: 0711 3409-0 Telefax: 031 789555 4470-174 Maia
Telefax: 0711 3409-133 E-Mail: [email protected] Portugal
E-Mail: [email protected] Telephone: 229407594
Telefax: 229407595
E-Mail: [email protected]

... www
In many countries we are www.pilz.com
represented by sales partners.

Please refer to our Homepage

for further details or contact our
headquarters.
19 406-05-07/03 Printed in Germany

Pilz GmbH & Co. KG

Sichere Automation
Felix-Wankel-Straße 2
73760 Ostfildern, Germany
Telephone: +49 711 3409-0
Telefax: +49 711 3409-133
E-Mail: [email protected]