PCS7 Basic Lib

SIMATIC
Process Control System PCS 7

Basic Library (V8.1)
General Information About

Block Description
Display for avoiding stop

without asset management
Icons for user-defined SFC

types
Family: CONTROL
Family: @System
Internal block
Appendix
Function Manual
07/2014
A5E32473002-AA
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products

Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
Siemens AG
Industry Sector
Postfach 48 48
90026 NRNBERG
GERMANY
A5E32473002-AA
07/2014 Subject to change
Copyright Siemens AG 2014.

All rights reserved
Table of contents
1
General Information About Block Description.............................................................................................11
Display for avoiding stop without asset management................................................................................15
Icons for user-defined SFC types...............................................................................................................17
Family: CONTROL.....................................................................................................................................19
4.1
4.1.1
4.1.2
FM_CO: Coordination of function blocks which read data records.............................................19

Description of FM_CO.................................................................................................................19
I/Os of FM_CO............................................................................................................................21
Family: @System.......................................................................................................................................23
5.1
5.1.1
5.1.2
5.1.3
CONEC: Monitoring the AS connection status............................................................................23

Description of CONEC................................................................................................................23
I/Os of CONEC............................................................................................................................25
Message texts and associated values of CONEC.......................................................................26
5.2
5.2.1
5.2.2
CPU_RT: Determination of the runtime of OBs...........................................................................27

Description of CPU_RT...............................................................................................................27
I/Os of CPU_RT...........................................................................................................................33
5.3
5.3.1
5.3.2
DIAG_AB: Evaluation of statusword AB7000..............................................................................35

Description of DIAG_OB..............................................................................................................35
I/Os of DIAG_AB.........................................................................................................................37
5.4
5.4.1
5.4.2
5.4.3
DPAY_V0: Monitoring DP/PA and Y-Link operating as V0 slave................................................38

Description of DPAY_V0.............................................................................................................38
I/Os of DPAY_V0.........................................................................................................................42
Message texts and associated values of DPAY_V0....................................................................44
5.5
5.5.1
5.5.2
DPAY_V1: Enabling blocks downstream of a DP/PA and Y-Link operating as V1 slave............45

Description of DPAY_V1.............................................................................................................45
I/Os of DPAY V1..........................................................................................................................47
5.6
5.6.1
5.6.2
DPAY_V1_PN: Enabling blocks downstream of a DP/PA and Y-link operating as a V1 Slave......47

Description of DPAY_V1_PN.......................................................................................................47
I/Os of DPAY_V1_PN..................................................................................................................48
5.7
5.7.1
5.7.2
DPDIAGV0: Monitoring the status of ET 200S modules acting as DPV0 slaves after the Y
link...............................................................................................................................................49
Description of DPDIAGV0...........................................................................................................49
I/Os of DPDIAGV0.......................................................................................................................51
5.8
5.8.1
5.8.2
5.8.3
DREP: Diagnostic Repeater in the DP master system................................................................52

Description of DREP...................................................................................................................52
I/Os of DREP...............................................................................................................................56
Message texts and associated values of DREP..........................................................................58
5.9
5.9.1
5.9.2
DREP_L: Diagnostic Repeater downstream of a Y-Link.............................................................59

Description of DREP_L................................................................................................................59
I/Os of DREP_L...........................................................................................................................63

Function Manual, 07/2014, A5E32473002-AA
Table of contents
5.9.3
Message texts and associated values of DREP_L......................................................................65
5.10
5.10.1
5.10.2
5.10.3
FFD_CIF: Monitoring FF slaves in CIF mode..............................................................................66

Description of FFD_CIF...............................................................................................................66
I/Os of FFD_CIF..........................................................................................................................68
Message texts and associated values of FFD_CIF.....................................................................69
5.11
5.11.1
5.11.2
FFDP_L1: Monitoring FF slaves with maximum 32 values.........................................................70

Description of FFDP_L1..............................................................................................................70
I/Os of FFDP_L1..........................................................................................................................72
5.12
5.12.1
5.12.2
5.12.3
FF_MOD32: Diagnostics of an FF slave (downstream from FF link DPV1)................................73

Description of FF_MOD32...........................................................................................................73
I/Os of FF_MOD32......................................................................................................................75
Message texts and associated values of FF_MOD32.................................................................76
5.13
5.13.1
5.13.2
5.13.3
FM_CNT: Programming and controlling FM 350 modules..........................................................78

Description of FM_CNT...............................................................................................................78
I/Os of FM_CNT..........................................................................................................................81
Message texts and associated values of FM_CNT.....................................................................82
5.14
5.14.1
5.14.2
5.14.3
IMDRV_TS: Transferring time-stamped process-signal changes...............................................83

Description of IMDRV_TS...........................................................................................................83
I/Os of IMDRV_TS.......................................................................................................................87
Message texts of IMDRV_TS......................................................................................................89
5.15
5.15.1
5.15.2
5.15.3
MOD_1: Monitoring up to 16 channels on S7-300/400 SM modules without diagnostic

capability.....................................................................................................................................90
Description of MOD_1.................................................................................................................90
I/Os of MOD_1/MOD_2...............................................................................................................93
Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64..............................95
5.16
5.16.1
5.16.2
5.16.3
MOD_2: Monitoring 32 channels on S7-300/400 SM modules without diagnostic capability......96

Description of MOD_2.................................................................................................................96
I/Os of MOD_1/MOD_2.............................................................................................................100
Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64............................102
5.17
5.17.1
5.17.2
5.17.3
MOD_3: Monitoring up to 16 channels on S7-200/300/400 SM modules without diagnostic

capability...................................................................................................................................103
Description of MOD_3...............................................................................................................103
I/Os of MOD_3...........................................................................................................................106
5.18
5.18.1
5.18.2
5.18.3
MOD_4: Monitoring ET 200S modules downstream of a Y-Link...............................................109

Description of MOD_4...............................................................................................................109
I/Os of MOD_4...........................................................................................................................112
Message texts and associated values of MOD_4.....................................................................114
5.19
5.19.1
5.19.2
5.19.3
MOD_64: Monitoring 64 channels on S7-300 SM modules without diagnostic capability.........115

Description of MOD_64.............................................................................................................115
I/Os of MOD_64.........................................................................................................................118
5.20
5.20.1
5.20.2
5.20.3
MOD_CENTRAL: Monitoring CPUs which are not capable of diagnostics...............................122

Description of MOD_CENTRAL................................................................................................122
I/Os of MOD_CENTRAL............................................................................................................122
Message texts and associated values of MOD_CENTRAL.......................................................124

Table of contents
5.21
5.21.1
5.21.2
5.21.3
MOD_CP: CP 341 diagnostics..................................................................................................125

Description of MOD_CP............................................................................................................125
I/Os of MOD_CP........................................................................................................................128
Message texts and associated values of MOD_CP..................................................................129
5.22
5.22.1
5.22.2
5.22.3
MOD_CP_PN: Monitoring of serial communication modules....................................................130

Description of MOD_CP_PN.....................................................................................................130
I/Os of MOD_CP_PN.................................................................................................................131
Message texts and associated values of MOD_CP_PN............................................................132
5.23
MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules with diagnostic

functions....................................................................................................................................133
Description of MOD_D1.............................................................................................................133
I/Os of MOD_D1/MOD_D2........................................................................................................139
Message texts and associated values of MOD_D1...................................................................141
5.23.1
5.23.2
5.23.3
5.24
5.24.1
5.24.2
5.24.3
5.25
5.25.1
5.25.2
5.25.3
5.26
MOD_D16_PN: Monitoring S7-300 SM modules with up to 16 channels and with diagnostics

functions....................................................................................................................................143
Description of MOD_D16_PN....................................................................................................143
I/Os of MOD_D16_PN/MOD_D24_PN ......................................................................................143
Message texts and associated values of MOD_D16_PN/MOD_D24_PN.................................145
MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with diagnostic
functions....................................................................................................................................149
I/Os of MOD_D1/MOD_D2........................................................................................................154
5.26.1
5.26.2
5.26.3

functions....................................................................................................................................158
Description of MOD_D24_PN....................................................................................................158
I/Os of MOD_D16_PN/MOD_D24_PN ......................................................................................159
Message texts and associated values of MOD_D16_PN/MOD_D24_PN.................................161
5.27
5.27.1
5.27.2
5.27.3
MOD_D3: Monitoring of hybrid modules with diagnostic capability...........................................165

I/Os of MOD_D3........................................................................................................................172
5.28
5.28.1
5.28.2
5.28.3

functions....................................................................................................................................175
Description of MOD_D8_PN......................................................................................................175
I/Os of MOD_D8_PN.................................................................................................................176
Message texts and associated values of MOD_D8_PN............................................................178
5.29
5.29.1
5.29.2
5.29.3
MOD_DRV: Monitoring of drive blocks with diagnostics functions............................................181

Description of MOD_DRV..........................................................................................................181
I/Os of MOD_DRV.....................................................................................................................183
Message texts and associated values of MOD_DRV................................................................185
5.30
5.30.1
5.30.2
5.30.3
MOD_HA: Monitoring device-specific diagnostics of HART field devices.................................186

Description of MOD_HA............................................................................................................186
I/Os of MOD_HA........................................................................................................................191
Message texts and associated values of MOD_HA..................................................................194
5.31
5.31.1
MOD_HA_PN: Monitoring Device-Specific Diagnostics of HART Field Devices.......................195

Description of MOD_HA_PN.....................................................................................................195

Table of contents
5.31.2
5.31.3
I/Os of MOD_HA_PN.................................................................................................................195
Message texts and associated values of MOD_HA_PN............................................................198
5.32
5.32.1
5.32.2
5.32.3
MOD_MS: Monitoring up to 16 channels on ET200S/X motor starter modules with

diagnostic functions...................................................................................................................199
Description of MOD_MS............................................................................................................199
I/Os of MOD_MS.......................................................................................................................203
Message texts and associated values of MOD_MS..................................................................205
5.33
5.33.1
5.33.2
5.33.3
MOD_SWT: Monitoring of Switch blocks with diagnostics functions.........................................207

Description of MOD_SWT.........................................................................................................207
I/Os of MOD_SWT.....................................................................................................................208
Message texts and associated values of MOD_SWT...............................................................210
5.34
MOD_PAL0: Diagnosing a DPV0 PA slave (via DP/PA coupler downstream of a DP/PA link
DPV1)........................................................................................................................................211
Description of MOD_PAL0........................................................................................................211
I/Os of MOD_PAL0....................................................................................................................213
Message texts and associated values of MOD_PAL0...............................................................215
5.34.1
5.34.2
5.34.3
5.35
5.35.1
5.35.2
5.35.3
MOD_PAX0: Diagnosing a DPV0 PA slave (via DP/PA coupler with connection to a DP

master system)..........................................................................................................................217
Description of MOD_PAX0........................................................................................................217
I/Os of MOD_PAX0...................................................................................................................219
Message texts and associated values of MOD_PAX0..............................................................222
5.36
5.36.1
5.36.2
5.36.3
OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics...............................................223

Description of OB_BEGIN.........................................................................................................223
I/Os of OB_BEGIN.....................................................................................................................227
Message texts and associated values of OB_BEGIN...............................................................229
5.37
5.37.1
5.37.2
5.37.3
OB_BEGIN_PN: CPU diagnostics.............................................................................................233

Description of OB_BEGIN_PN..................................................................................................233
I/Os of OB_BEGIN_PN..............................................................................................................233
Message texts and associated values of OB_BEGIN_PN.........................................................234
5.38
5.38.1
5.38.2
5.38.3
OB_BEGIN_HPN: H-CPU diagnostics......................................................................................238

Description of OB_BEGIN_HPN................................................................................................238
I/Os of OB_BEGIN_HPN...........................................................................................................239
Message texts and associated values of OB_BEGIN_HPN......................................................240
5.39
5.39.1
5.39.2
5.39.3
OB_DIAG1: OB diagnostics for avoiding stoppages in DPV1 master systems.........................245

Description of OB_DIAG1..........................................................................................................245
I/Os of OB_DIAG1.....................................................................................................................248
Message texts and associated values of OB_DIAG1................................................................250
5.40
5.40.1
5.40.2
5.40.3
OB_DIAG1_PN: OB diagnostics for avoiding stoppages in DPV1 master systems..................251

Description of OB_DIAG1_PN...................................................................................................251
I/Os of OB_DIAG1_PN..............................................................................................................251
Message texts and associated values of OB_DIAG1_PN.........................................................253
5.41
5.41.1
5.41.2
5.41.3
OB_DIAGF: Monitoring of the FF link and coupler....................................................................254

Description of OB_DIAGF.........................................................................................................254
I/Os of OB_DIAGF.....................................................................................................................255
Message texts and associated values of OB_DIAGF................................................................257
5.42
5.42.1
OB_END: Reset stack pointer of OB_BEGIN............................................................................258

Description of OB_END.............................................................................................................258

Table of contents
5.42.2
I/Os of OB_END........................................................................................................................259
5.43
OR_32_TS: OR value status of two redundant time-stamped signal modules, max. 32

channels....................................................................................................................................260
Description of OR_32_TS..........................................................................................................260
I/Os of OR_32_TS.....................................................................................................................261
5.43.1
5.43.2
5.44
5.44.1
5.44.2
5.44.3
5.45
5.45.1
5.45.2
5.45.3
5.46
5.46.1
5.46.2
5.46.3
5.47
OR_HA16C: OR value status of 2 redundant HART modules, max. 16 channels, module

granular.....................................................................................................................................263
Description of OR_HA16C.........................................................................................................263
I/Os of OR_M_8C / OR_M_16C / OR_M_32C / OR_HA16C.....................................................266
Message texts and associated values of OR_HA16C...............................................................268
OR_M_16C: OR value status of 2 redundant signal modules, max. 16 channels, channel
granular.....................................................................................................................................271
Description of OR_M_16...........................................................................................................271
Message texts and associated values of OR_M_16C...............................................................274
granular.....................................................................................................................................276
Description of OR_M_32C.........................................................................................................276
Message texts and associated values of OR_M_32C...............................................................279
5.47.1
5.47.2
5.47.3

granular.....................................................................................................................................282
Description of OR_M_8C...........................................................................................................282
Message texts and associated values of OR_M_8C.................................................................287
5.48
5.48.1
5.48.2
5.48.3
5.48.4
5.48.5
5.48.6
5.48.7
PADP_L0x: Monitoring DP/PA slaves.......................................................................................289

Description of PADP_L00..........................................................................................................289
I/Os of PADP_L00/PADP_L01/PADP_L02................................................................................292
Message texts and associated values of PADP_L00................................................................293
5.49
5.49.1
5.49.2
PADP_L10: Monitoring PA slaves downstream of DPV0 with up to 16 slots............................303

I/Os of PADP_L10.....................................................................................................................308
5.50
5.50.1
5.50.2
PADP_L10_PN: Monitoring PA slaves downstream of DPV0 with up to 16 slots.....................309

Description of PADP_L10_PN...................................................................................................309
I/Os of PADP_L10_PN..............................................................................................................310
5.51
5.51.1
5.51.2
5.51.3
PDM_MS: Monitoring of the maintenance status......................................................................311

Description of PDM_MS............................................................................................................311
I/Os of PDM_MS........................................................................................................................311
Message texts and associated values of PDM_MS..................................................................312
5.52
5.52.1
PO_UPDAT: Output Process Image.........................................................................................313

PO_UPDAT: Output Process Image.........................................................................................313
5.53
5.53.1
PS: Power supply monitoring....................................................................................................314

Description of PS.......................................................................................................................314

Table of contents
5.53.2
5.53.3
I/Os of PS..................................................................................................................................316
Message texts and associated values of PS.............................................................................317
5.54
5.54.1
5.54.2
5.54.3
RACK: Rack monitoring............................................................................................................318

Description of RACK.................................................................................................................318
I/Os of RACK.............................................................................................................................321
Message texts and associated values of RACK........................................................................322
5.55
5.55.1
5.55.2
5.55.3
RACK_PN: Rack monitoring......................................................................................................323

Description of RACK_PN...........................................................................................................323
I/Os of RACK_PN......................................................................................................................323
Message texts and associated values of RACK_PN.................................................................325
5.56
5.56.1
5.56.2
RED_F: Status processing of redundant F modules.................................................................326

Description of RED_F................................................................................................................326
I/Os of RED_F...........................................................................................................................328
5.57
5.57.1
5.57.2
5.57.3
SUBNET: DP master system monitoring...................................................................................329

Description of SUBNET.............................................................................................................329
I/Os of SUBNET........................................................................................................................332
Message texts and associated values of SUBNET...................................................................333
5.58
5.58.1
5.58.2
5.58.3
SUBNET_PN: Monitoring of the PN IO system.........................................................................334

Description of SUBNET_PN......................................................................................................334
I/Os of SUBNET_PN.................................................................................................................334
Message texts and associated values of SUBNET_PN............................................................336
Internal block............................................................................................................................................339
6.1
ChkREAL: Internal Block...........................................................................................................339
6.2
QC_CHNG: Internal block.........................................................................................................339
Appendix...................................................................................................................................................341
7.1
MODE settings for FF devices..................................................................................................341
7.2
MODE settings for SM modules................................................................................................341
7.3
OMODE settings for SM modules.............................................................................................351
7.4
MODE settings for field devices................................................................................................351
7.5
OMODE settings for field devices.............................................................................................353
7.6
Error Information of Output Parameter MSG_STAT..................................................................353
7.7
Addressing................................................................................................................................353
7.8
Message Classes......................................................................................................................355
7.9
Dependencies...........................................................................................................................356
7.10
7.10.1
7.10.2
Status displays..........................................................................................................................356
Maintenance Status of MS........................................................................................................356
PA field device status and diagnostics information...................................................................357
7.11
7.11.1
7.11.2
7.11.3
7.11.4
Text libraries..............................................................................................................................360
Text Library for MOD_PAL0, MOD_PAX0.................................................................................360
Text Library for PADP_L00, PADP_L01, PADP_L02................................................................360
Text Library for DREP, DREP_L...............................................................................................360
Text library for MOD_1, MOD_2, MOD_3, MOD_64, MOD_D2, MOD_CP................................361

Table of contents
7.11.5
7.11.6
7.11.7
7.11.8
7.11.9
7.11.10
7.11.11
Text Library for MOD_D1..........................................................................................................362

Text library for MOD_D3............................................................................................................364
Text library for MOD_D8_PN (FB197) / MOD_D16_PN (FB198) / MOD_D24_PN (FB199)......366
Text library for MOD_CP_PN (FB201)......................................................................................367
Text Library for MOD_MS..........................................................................................................369
Text Library for OB_BEGIN.......................................................................................................371
Text library for OB_BEGIN_PN (FB130) / OB_BEGIN_HPN (FB205).......................................371
Index.........................................................................................................................................................373

General Information About Block Description
The setup of the block description is always uniform and contains the following sections:
Header of the block description

Example: CTRL_PID: PID controller block
The header begins with the type name of the block (e.g., "CTRL_PID"). This symbol name is
entered in the symbol table and must be unique within the project.
In addition to the type name, you will also see a keyword indicating the purpose or function of
the block (e.g., "PID controller block").
Object name (type + number)

FB x
The object name for the block type is made up of the type of implementation (function block =
FB, function = FC) and the block number = x.
Links for displaying block I/Os

Example:
CTRL_PID block I/Os
Click the "Block I/Os" link to display a list of block I/Os for the designated block.
Links for displaying the block icon and faceplate

If the block is intended for operator control and monitoring and a block icon and faceplate exist,
the corresponding image and description can be displayed directly by clicking these links.
Example:
CTRL_PID block icon
CTRL_PID faceplate
Function
Here, you will find a brief description of the block function.
You will find additional information about complex blocks in the "How it works" section.
How it works
Here, you will find more detailed information, for example about the function of specific inputs,
operating modes or time sequences. You must be familiar with these relationships in order to
use the block effectively.

11
Calling OBs
Here you will find information on the organization blocks (OBs), in which the described block
must be installed. If the CFC is used, the block is automatically installed in the cyclic OB (cyclic
interrupt) and in the OBs listed in the block's task list (for eample in restart OB100).
CFC generates the required OBs during compilation. If you use the blocks without CFC, you
will have to program these OBs and call their instance within the blocks.
Error handling
The ENO Boolean block output indicates the error in the CFC chart.
The value is equivalent to the BIE (binary result in STEP 7 STL, after completion of the block)
or OK bit (in SCL notation) and indicates:
ENO = BIE = OK = 1 (TRUE) -> The result of the block is free of errors.
ENO = BIE = OK = 0 (FALSE) -> Invalid result or constraints (for example, input values and
modes).
The FBs also return the inverted BIE at the QERR output of the instance DB.
QERR = NOT ENO
The error message is generated in two separate operations:
The operating system detects a processing error (e.g. value overflow, system functions
called return an error ID with BIE = 0).
This is a system function and is not specifically mentioned in the block description.
The block algorithm checks for functional invalidity of values and operating modes. These
error events are logged in the block description.
You can evaluate the error display, for example, to generate messages or use substitute values
for invalid results. You will find more information about messages in the "Message blocks"
section.
Startup characteristics
The different startup behaviors are as follows:
Initial start
The block is called for the first time from the OB in which it has been inserted. This is usually
the OB that performs the standard, process-specific operations (for example, the cyclic
interrupt OB).
The block adopts a status that conforms to its input parameters. These may be default
values (additional information in "I/Os" section) or values you have already configured, for
example, in CFC. The initial startup characteristics are not described separately unless the
block does not conform to this rule.
Startup
The block is executed once during CPU startup. The block is called in the startup OB (where
it is additionally installed either automatically in the ES or manually in STEP 7). In this case,
the startup characteristics are described.
Please note that the block outputs have default values and that these can take effect during
the CPU startup with other blocks, if these are processed first.
The correct startup behavior of the blocks is the responsibility of the configuration engineer.
12

Time response
A block assigned this function must be installed in a cyclic interrupt OB. It calculates its time
constants/parameters on the basis of its sampling time (the time which elapses between two
consecutive cyclic operations).
In a CFC configuration on ES, the sampling time is also determined by the segmentation of
the runtime group, which ensures that the block is not executed during every OB run.
This sampling time is entered at the I/Os, in the SAMPLE_T parameter.
When configuring with CFC, this occurs automatically once the block has been inserted in the
OB and the runtime group. For this reason, this input is set to invisible in CFC.
During the STEP 7 configuration, you set the time response manually.
Time response is mentioned only if the block has been assigned this feature.
Message response
A block with message response reports various events to the higher level OS. Existing
parameters required for the generation of messages are documented.
Blocks without message response can be expanded with additional message blocks. A
reference to the message response is found in the description of the individual message blocks.
I/Os
The I/Os of the block represent its data interface. These I/Os can be used either to transfer
data to the block or to fetch results from the block.
I/O
(parameter)
Meaning
Data type
Default
U1
Addend 1
REAL
.....
The "I/O" table lists all I/O parameters of the block type. You can access these lists using the
engineering tools. They are in alphabetical order. Elements accessible only via the block
algorithm (internal variables) are not listed.
The meaning of the columns is as follows:
I/O
Name of the parameter, derived from the English, e.g. PV_IN = Process Variable INput
(process variable, controlled variable).
The SIMATIC naming conventions have been applied.
The block representation in CFC as supplied is as follows:
I/O name in bold characters = I/O is visible, regular = I/O is invisible.
Meaning
Function (possibly also short description)

13
Data type
S7 data type of the parameter (BOOL, REAL, etc.)
Default (default value)
The value of the parameter before the block runs for the first time (unless changed in the
configuration)
14

Display for avoiding stop without asset management
Block icon "OB_BEGIN_BASE" / "OB_BEGIN_PN_BASE" / "OB_BEGIN_HPN_BASE "

If your system does not have ASSET diagnostics, a separate block icon for the avoidance of
stop is provided on the OS in the template @TemplateBasisLibraryV8.
Configuration
You configure a corresponding block icon for each AS. You then interconnect each block icon
with the corresponding structure variable.
To achieve all the required interconnections to the block icon, it is best to use the PCS 7 WinCC
Wizard for interconnecting faceplates to process tags. In the tag dialog "List of all structure
variables", you can select the relevant block instance.
Note on the faceplate

In the OB_BEGIN/ OB_BEGIN_PN/OB_BEGIN_HPN and CPU_RT faceplates without asset
management, the message view, the performance view and the detailed views (OB3x and
OB8x/OB1) are displayed if SFC78 is supported on the AS. If SFC78 is not supported, only
the message view of the faceplate is displayed.
The identification view and parameter view are not shown.

15
Icons for user-defined SFC types
Icons for user-defined SFC types

The following icons are available in the template for user-defined SFC types
"@TemplateBasisLibraryV8".
For more information, refer to the manual SFC Visualization - Manual for S7 or in Simatic
Manager to the "SFC properties" dialog, "OS" tab or the "Properties for SFC type/SFC instance"
dialog, "Options" tab.

17
Family: CONTROL
4.1
FM_CO: Coordination of function blocks which read data records
4.1.1
Description of FM_CO

FB 79
FM_CO block I/Os (Page 21)
Function
The block coordinates the data record reading of the blocks
Block
Library
Module
FM_CNT
PCS 7 Basic Library
FM350-1, FM350-2
FMCS_PID
PCS 7 Library
FM355
FMT_PID
PCS 7 Library
FM355-2
REAS355P
PCS 7 Library
FM355, FM355-2
FmCont
PCS 7 APL
FM355
FmTemp
PCS 7 APL
FM355-2
The block is installed and the parameters interconnected by the driver generator.
Block
Configuration of the
coordination number
Interconnections between FM_CO and the data

record reading instance: FM_CO - DS reading
instance
FM_CNT,
FMCS_PID
CO_NO
EN_CO_x <-> EN_CO
FM_PID,
READ355P
CO_NO
ENCOx_yy <-> ENCO
FmCont,
FmTemp
CoordNo
EN_CO_x <-> EnCoord

ENCOx_yy <-> EnCoNum
Where:
x = Sequence of data record reading blocks (0 to 7)

yy = Coordination number within a sequence (0 to 63)
It is possible to include data record reading blocks of other modules in the coordination.

19
Family: CONTROL
4.1 FM_CO: Coordination of function blocks which read data records
How it works
The FM_CO block can start a maximum of 8 block sequences.
The blocks connected to the output structure EN_COx check whether the current coordination
number (EN_COx.CO_ACT) corresponds to their own coordination number (CO_NO/
CoordNo). If this is the case, they read their data records from the module and reduce the
coordination number EN_COx.CO_ACT by 1, so that the next block can read out its data
records.
If the current coordination number of a sequence (EN_COx.CO_ACT) has a value less than
1, the FM_CO block determines the highest number assigned in sequence x based on its inputs
ENCOx_yy. The data reading blocks supply the inputs ENCOx_yy with their respective
coordination number via an interconnection. The highest coordination number is the number
for which ENCOx_yy = yy still applies. The FM_CO module restarts the sequence in which it
sets EN_COx.CO_ACT to this value.
This algorithm ensures that no more than one read data record operation ever takes place at
any given time within the block sequence.
Calling OBs
The fastest cyclic interrupt OB of all OBs in which you have installed data reading block
instances and OB100 as well.
Use in CFC
When using the CFC function "Generate Module Drivers", the block is automatically installed
and the connections, such as those described under "Installation regulation" are made.
If you install, delete or move blocks of an existing block sequence in other OBs or runtime
groups, the driver generator must be called.
Should the sequence not start up as expected (after CPU restart) or not continue to run (after
downloading changes), you must set ACC_ID to 1.
Installation rules/capacity
One FM_CO is responsible for one DP master system and has 8 sequences with data record
reading block instances that are coordinated in parallel. The first block sequence contains
instances of the data recording reading blocks that relate to the DP slaves 1, 9, 17 and so on.
The second block sequence contains instances of the data recording reading blocks that relate
to the DP slaves 2, 10, 18 and so on. The same principle applies to the remainder of the eight
block sequences.
Note
When an instance is added to a sequence by a data recording reading block, the sampling
time of all instances in the sequence increases. If, for example, an instance from DP slave 9
is added to the sequence 1, then the sampling time of all instances of sequence 1 increases
including the instances from DP slave 1.
A sequence may contain up to 63 data recording reading instances of the following blocks:
20

Family: CONTROL
Block
Data record reading channels
Module
FM_CNT
One instance of FM_CNT is required for each

module. 4 channels are read with one data
record read operation per cycle
FM350-1, FM350-2
FMCS_PID, FMT_PID,
FmCont, FmTemp
The module has 4 controller channels. One

channel is read with one data record read
operation per cycle.
FM355, FM355-2
READ355P
Certain process values of all 4 channels are

read with one data record read operation per
cycle.
FM355, FM355-2
The FM_CO must always be installed before the first data record reading instance in the fastest
cyclic interrupt OB. The output structure EN_COx for the DP slave is connected to the input
structures EN_COx or EnCoord of all data record reading instances that communicate with
the controller modules of rack x. The output ENCO or EnCoNum of each data record reading
instance is connected to an input ENCOx_yy (yy corresponds to the coordination number
CO_NO or CoordNo assigned to each data recording reading instance) of the FM_CO block.
The selection of the cyclic interrupt OB depends on the CPU load. Note that the CPU has no
reserves for other "Read data record" jobs if operating with eight or more DP slaves because
only eight jobs can be buffered per DP master system. Simply inserting a module would lead
to an overflow. It is advisable to operate only up to six DP slaves on a DP master system. The
remaining DP slaves must be distributed on other DP master systems with further FM_CO
blocks.
When selecting the cyclic OB, remember that the new data will be available at the earliest after
two cycles. Make sure that the maximum runtime of this OB does not have any negative impact
on overall system runtime as a result of the number of blocks installed. If the data recording
reading block instances to be processed exceed the runtime limit, group the DP slaves with
the FM350/FM355 modules in fast and slow control loops.
EN_CO_x.CO_ACT = 1 is set at all outputs during startup (restart).
Time response
Not available
Message functionality
Not available
4.1.2
I/Os of FM_CO
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name
bold = I/O visible, I/O name normal = I/O not visible.

21
Family: CONTROL
You will find explanations of and information on abbreviations in the section: "General
Information About Block Description (Page 11)".
Input parameters
I/O
(parameter)
Meaning
Data type
Default
DIAG_BUF
Entry in diagnostic buffer (relevant for maintenance

personnel)
BOOL
ENCOx_yy
The coordination number yy is assigned in the rack x if the

input has the value yy (x = 0 - 7, yy = 1 - 64)
BYTE
I/O
(parameter)
Meaning
Data type
Default
EN_CO_x
Coordination number of the block that can read data records STRUCT
I/O
(parameter)
Meaning
Data type
Default
ACC_ID
Restart all sequences
BOOL
Output parameters
In/out parameters
22

Family: @System
5.1
CONEC: Monitoring the AS connection status
5.1.1
Description of CONEC

FB 88
CONEC Block I/Os (Page 25)
Area of application
The CONEC block monitors the status of AS connections, and reports the associated error
events.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 100
Warm restart
Use in CFC
With the "Generate module drivers" CFC function, the CONEC block is automatically installed
in the OBs listed above.
Function and method of operation

The CONEC block generates messages which are output at ALARM_8P to WinCC (see
"Message response"). For connection diagnostics, SFC 87 (C_DIAG) is called at intervals of
10 seconds in the cyclic interrupt OB 32. Up to 128 simple and up to 64 redundant connections
are monitored.
Note
The messages "Failure or loss of redundancy connection ID" are generated by each CPU of
the two connected AS except when the CPU (or both H-CPUs) of an AS fails.
The connection ID determines whether a message is output.
If the connection ID >= 16#C00 no message is generated.

23
Family: @System
5.1 CONEC: Monitoring the AS connection status
Generation of the maintenance status MS

If any connection in the CONEC block is detected as having failed, the "Maintenance alarm"
maintenance status is output.
If any connection in the CONEC block is detected as a redundancy loss, the "Maintenance
demanded" maintenance status is output.
If in the CONEC block the messages are disabled via the parameter EN_MSG , then the
maintenance status "Unchecked / Unknown" is output.
Error handling
Error handling for the block is limited to the evaluation of the error information of ALARM_8P.
You will find additional information in the
"Error Information of Output Parameter MSG_STAT" (Page 353) section.
The CONEC block initializes the messages of ALARM_8P.
If there is a CPU with SFC 87, connection diagnostics is initialized. After this, there is a wait
time of approx. 1 minute in the cyclic interrupt OB before the connection diagnostics messages
are generated.
Overload behavior
Not available
Time response
For additional information, refer to "Message response".
Message response
The block generates the following messages in the OBs listed below:
OB
Start Event
Message
OB 32
1 sec. cyclic interrupt or

alternative cyclic interrupt OB
Failure connection ID: xx incoming/outgoing

Loss of redundancy connection ID: xx entering/exiting state
If EN_MSG = FALSE, messaging is disabled.
Operator control and monitoring

If asset management is used in the project and the diagnostic screens have been generated,
the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station"
manual.
24

Family: @System
Additional information
For additional information, refer to the sections:
Message texts and associated values of CONEC (Page 26)
Maintenance status MS (Page 356)
5.1.2
I/Os of CONEC
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
Input parameters
I/O
(parameter)
Meaning
Data type
Default
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = Enable message
BOOL
EV_IDx
Message number for ALARM_8P_x
DWORD
(x = 1 - 24, assigned by the ES)

MS
Maintenance status
DWORD
SAMPLE_T
Sampling time OB in seconds
REAL
1.0
I/O
(parameter)
Meaning
Data type
Default
MSGSTAx
Output STATUS of the ALARM_8P_x (x = 1 - 24)
WORD
O_MS
Maintenance status
DWORD
QMSGERx
Error output of the ALARM_8P_x (x = 1 - 24)
BOOL
Output parameters
Message texts and associated values of CONEC (Page 26)

25
Family: @System
5.1.3
Message texts and associated values of CONEC
Assignment of message text and message class

Message block
ALARM_8P
Message
number
Default message text
Message
class
(Page 355)
EV_ID1 to EV_ID16
Failure connection ID: 16#@1%X@
EV_ID17 to EV_ID24 1
Loss of redundancy connection ID:

16#@1%X@

16#@2%X@

16#@3%X@

16#@4%X@

16#@5%X@

16#@6%X@

16#@7%X@

16#@8%X@
Assignment of associated values

Process control messages are generated with EV_ID1 up to EV_ID24 via ALARM_8P
associated values. The table below shows how the associated values are assigned to the block
parameters.
26
Message block
ALARM_8P
Associated
value
Block parameter
Data type
EV_ID1... EV_ID24
Connection_ID 1+x
WORD
Connection_ID 2+x
WORD
Connection_ID 3+x
WORD
Connection_ID 4+x
WORD
Connection_ID 5+x
WORD
Connection_ID 6+x
WORD

Family: @System
5.2 CPU_RT: Determination of the runtime of OBs
Message block
ALARM_8P
Associated
value
Block parameter
Data type
Connection_ID 7+x
WORD
Connection_ID 8+x
WORD
x = 0 for EV_ID1, x = 8 for EV_ID2, x = 16 for EV_ID3 etc. up to x = 120 for EV_ID16
x = 0 for EV_ID17, x = 8 for EV_ID18, x = 16 for EV_ID19 etc. up to x = 56 for EV_ID24
5.2
CPU_RT: Determination of the runtime of OBs
5.2.1
Description of CPU_RT

FB 128
CPU_RT block I/Os (Page 33)
Area of application
The CPU_RT block is installed by the CFC in OB 100, OB 1, in all OB 3x as well as OB 8x, if
this is used by the user program.
The CPU_RT determines the runtime of the individual OBs and their participation in the cycle
time. If there is CPU overload (OB 80 cycle time exceeded), it instigates suitable actions
selected by the user in limits to ensure operability of the AS.
This situation is designated as emergency operation and is made clearly visible by a process
control message. Buffered start events (OB 3x still executing) are also detected and displayed.
The loss of start events is reported as error.
Use in CFC
During compilation of the CFC, a chart is automatically created with the name @CPU_RT. The
CPU_RT block is already included in it.
Note
Never attempt to insert the CPU_RT block in a different block because it is a system block.

At CPU restart and when downloading changes the slowest OB 3x is determined with SZL ID
822 (data records of all assigned alarms of an alarm class).
Note: The slowest cyclic OB 3x (slowest OB) must also have the lowest priority set so that a
useful analysis is possible.

27
Family: @System
In OB-BEGIN, if there are implausible settings, a message EV_ID2 signal 3 "Priorities of cyclic
OBs do not conform to PCS 7" is output and the maintenance status (MS is set to "Maintenance
demand" = 16#00000005).
SFC78 is used to determine the OB runtimes. If it is not present, no warning limit will be output
as a message.
Note
Older CPUs do not support SFC78. Use SSL112 to check whether SFC78 is available.
Note
The status of CPU_RT is reset when you download.
Behavior at higher CPU load

If the average value of all net runtimes (in % of OB 3x, OB 8x + OB 1) exceeds the value
MAX_LIM, then in OB_BEGIN, the message EV_ID2- signal 1 "Net time consumption of all
OBs exceeds max limit" is output.
The maintenance status MS is set to "Maintenance demand" = 16#00000005 in OB_BEGIN.
The message and MS are cleared with a value less than MAX_LIM HYS.
Behavior in the event of OB request errors

If a programmable number of these OB 3x events has been exceeded or if an OB 1 event is
detected without an OB 1 having been processed, the message EV_ID3 Signal 2 "OB
request: OB 3x still being processed" is output in OB_BEGIN. The number of OB 3x events
can be set at the input "N_REG_ERR"; the default value = 4.
The maintenance status MS is set to "Uncertain maintenance demanded" = 16#00000006 in
OB_BEGIN.
If an OB 1 is then run through again, the MS is reset and this process control message will be
marked as "outgoing".
In the faceplate of OB_BEGIN, there is a display of the request error for each OB 3x. The first
occurrence of a request error is be displayed. These displays can be reset with the reset key.
Behavior when the maximum cycle time is exceeded

If the maximum cycle time is exceeded, a message EV_ID3 Signal 1 "Cycle time exceeded:
@1d@ OB@2d@" is output.
The maintenance status MS is set to "Bad or maintenance alarm" = 16#00000007 in
OB_BEGIN.
If an OB 1 is then run through again, the MS is reset and this process control message will be
marked as "outgoing".
28

Family: @System
Behavior to prevent stop

If the cycle time is exceeded twice without an OB 1 being processed, this results in Emergency
Operation with stop avoidance activated. The process control message EV_ID1 Signal 3
"Emergency operation, cycl. OBs will be reduced" will be output.
The maintenance status MS is set to "Bad or maintenance alarm" = 16#00000007.
If the CPU resumes normal operation after the problem has been eliminated, the MS is reset
and this process control message is marked as "outgoing".
Behavior during downloading

The status of CPU_RT is reset when you download.
Measures for avoiding stop

When the CPU is overloaded you can prevent the CPU from becoming inoperable by "load
shedding". Load shedding is achieved by suspending the cyclic levels and is an emergency
mode. The user can still exclude individual OBs for the first escalation stage, for example the
level with the F drivers.
To avoid a CPU stop, CPU_RT takes the following measures in OB 80 when reaching a cycle
overflow occurs:
Cycle time monitoring is triggered with an SFC43 call, to prevent a CPU stop.
A memory bit is set to detect the next immediate OB 80 call within an OB 1 call, so that, if
necessary, measures can be initiated that prevent an overload of the AS.
In OB 80, the measures to prevent the overload are initiated and they reversed in the slowest
OB.
Two escalation stages can be set:
1. Stage: None of the used OB 3x blocks will be processed for one cycle, unless they have
been excluded by the user (OB3x_ATTN = FALSE).
2. Stage: Now all previously excluded OB 3x blocks will likewise not be processed for one
cycle. If this does not have a steadying effect, whenever OB 3x blocks are executed their
execution will be suspended again for one cycle.
Assign the parameters in CPU_RT for each OB 3x at the following inputs:
OB3x_ATTN = TRUE
The OB is included in the measures to prevent overload. Default is "TRUE".
The maximum number of SFC43 calls can be set at the input MAX_RTRG. If the maximum
number x is exceeded, the CPU goes to stop.
The number x is reset when there is an OB 1 call again.
If you set MAX_RTRG = 0, then the function stop avoidance on overload function is deactivated.
If the measures are effective, in other words OB 1 is run through again, a calculation is made
at that point to determine whether canceling the measures would again result in overload. If
yes, the measures remain in effect. The measures are reduced step-by-step, when safe
operation is possible again.

29
Family: @System
Reversal of the measures for stop avoidance

To initiate a reversal the percentage sum of the cyclic OBs calculated back to a lower reduction
ratio, must be less than full CPU utilization.
Use the parameter MAX_VAL to set the value that corresponds to full CPU utilization. The
value "95" is default.
The calculation is made according to the following formula:
((NET30PERint * (OB30_N_START+1) / OB30_N_START)+
(NET31PERint * (OB31_N_START+1) / OB31_N_START)+
NET01PER)< MAX_VAL
NETxxPERint is the percentage share of a cyclic OB in the total runtime as a mean value and
(OB30_N_START+1) is the current reduction factor of the OB.
The net percentage values are also mean values, because in case of reduction, averaging is
a must.
For the calculation, a separate mean value generation was used that has a separate sample
factor (SAMPLE_RE).
If the condition is satisfied, then after a number of cycles in the slowest OB (parameter
"UndoCycle") the reduction factor is decremented by 1 for all OBs.
If the total sum of the OBs is still below MAX_VAL after this, then after a number of cycles in
the slowest OB (UndoCycle), the factor will continue to be decremented until the used cyclic
OBs have reached the reduction factor 1.
After this, for the OBs (OB3x_ATTN = FALSE) excluded by the user, the reduction ratio will
be set to 0.
Finally. the reduction ratio will be set to 0 for all other cyclic OBs.
If no SFC78 is present, then the time at which reversal of the stop avoidance measures can
be triggered cannot be calculated.
The reversal of reduction ratios is started when the slowest OB has again processed a number
of cycles (UndoCycle).
The value of the UndoCycle in this case should not be too low, to avoid a frequent back and
forth between stop avoidance measures and normal operation.
For the reduction ratio in the CFC, two parameters are available in the CPU_RT block for each
cyclic OB:
30
OB3x_N_START
The start value for reduction ratio is specified by the input OB3x_N of CPU_RT
and also in OB3x_N_CNT
OB3x_N_CNT
The counter is decremented in the CFC at each OB call. For OB3x_N_CNT <= 0
there is complete OB processing and OB3x_N_START will be re-entered in
OB3x_N_CNT.

Family: @System
The CPU block is also called when reduction becomes necessary, so that in emergency
operation an evaluation of the averaged cycle time is possible.
Utilization display with SFC78

When the block executes, the calling OB is determined. For every OB with the system function
SFC78, it reads the net runtime, LAST_RTxx, and the gross runtime LAST_Etxx of the last
completed OB processing. The absolute times are specified in milliseconds.
The mean value is generated for each OB (OB 3x and OB 8x) according to the formula
Mean value = mean value + (new value mean value ) / sample_AV
SAMPLE_AV is a parameter that is calculated separately for each OB 3x, OB 8x. If necessary,
you can adapt the precision of the mean value with this parameter that is based on the number
of measuring cycles, or on the influence of the new value on the mean value.
The default of SAMPLE_AV = 25 cycles, based on the slowest cyclic OB.
The actual sample factor for specific OBs is determined according to the following formula:
SampleOB3x = Sample * execution frequency of the slowest OB / execution frequency of OB3x
This ensures equally-weighted mean value generation over time for all cyclic OBs.
The sample factor for the total mean value of OB 1, and for OB 8x, is set to = sample, because
the basis for these values is also the execution frequency of the slowest OB.
Use the reset button on the faceplate of OB_BEGIN to reset mean value generation.
After the reset, the divisor "Sample" of 1 per cycle is incremented by 1.
This means that with the reset, mean value generation is initially imprecise and it becomes
more precise through the factor "sample". The influence of the new value on the mean value
initially is significant and diminishes as the "sample" factor becomes greater.
By resetting the data, a fresh measuring cycle can be started at anytime.
The reset of all mean values takes place in OB 1. Mean value generation does not take place
during this time.
Connection load display

The connection states of the configured connections from the CPU < V6 is queried through
the block. The data are evaluated for all connections*. The 5 connections with the highest load
are set at the CON1-5 block outputs.
Connection type
The connection type specifies the kind of connection involved. These are listed in the following
table:
CONx_TYPE
Type of connection
Invalid connection type
Fixed configured S7 connection
Fixed configured S7 connection (fault-tolerant)
T connection (TCP native)

31
Family: @System
4
T connection (UDP)
T connection (ISO-on-TCP)
Routed connection
PG connection
OP connection
OMS connection
10
Free connection
11
Free connection (TCP)
12
System connection
13
RPC7 connection
14
Connection for basic communication
Identification / partner
You can use this to recognize the connection involved. This connection must be unique.
Depending on the connection type, the ID and the partner are determined as follows:
Connection type
Text
tag
1-2
Local ID: a
a = User ID (hex)
3-5
AWP ID: 16# a
a = User ID (hex)
7-9
Partner address: a.b.c.d*
a..d = CONx_R_ADDR0..3*
10-11
12
Device ID 16# a R/S b/c
a = UserId (hex),
b = rackNr
c = slotNr
13-14
Partner address: a.b.c.d*
a..d = CONx_R_ADDR0..3*
* CONx_R_ADDR_LEN is used to determine the length of the CONx_R_ADDR0..3 = a..d to

be represented. Only the number of bytes actually addressed are displayed.
Last
This shows the load of the connection in percent, associated with the CONx_PER tag
Error handling
If the read-out of data from the cyclic OB fails for the CPU_RT block, then ERR_NUM = 1 is
set and processing of the CPU_RT block is abandoned, because these data are the basic
prerequisite for useful processing.
Calculations with SFC78 are restarted only after a number of cycles (RunUpCyc) after restart.
The RunUpCyles are counted down in the slowest cyclic OB.
Time response
Not applicable.
32

Family: @System
Message response
The block reports via OB_BEGIN (Page 223)
Operator control and monitoring:

If asset management is used in the project and the diagnostics screens have been generated,
the faceplate can be called via the block icon of the AS.
OB_BEGIN faceplate
Asset Management block icons (for additional information, refer to the "Process Control
System PCS 7; Maintenance Station" manual)
If no asset management is used in the project, the "OB-BEGIN" block icon is used to display
avoidance of stop.
You can find additional information on this subject in the following sections:
Message texts and associated values of OB_BEGIN (Page 229)
5.2.2
I/Os of CPU_RT
You can find explanations of and information on abbreviations in the section: "General
Input parameters
I/O
Meaning
Type
Defau
lt
DELTA_L
Flag for change compile
BOOL
DIAG_BUF
Entry in diagnostic buffer (relevant for maintenance personnel)
BOOL
HYS
Hysteresis of the max. total number
INT
MAX_LIM
Max. total number
REAL
75
MAX_RTRG
Max. number of calls (for SFC 43)
INT
50
MAX_VAL
Max. value for calculating the reset of reduction ratios
REAL
95
N_REQ_ERR
Number of OB 3x request errors
INT
OB3x_ATTN
(x = 0 8) OB 3x: 1 = participates in measures to prevent overloads
BOOL
RESET
Resets the mean values, minimum values, and maximum values
BOOL
RUNUPCYC
Number of start-up cycles
INT
SAMPLE_AV
Sample factor for mean value generation
INT
50

33
Family: @System
I/O
Meaning
Type
Defau
lt
SAMPLE_RE
Sample factor for mean value generation internal
INT
50
UNDO_CYC
Counter in the slowest OB for emergency operation
INT
100
Output parameters
I/O
Meaning
Type
Defau
lt
CON_LOAD_ACT
1 = I/O for loading function is available
BOOL
CONx_TYPE
(x = 1 - 5) I/O type
WORD
CONx_USER_ID
(x = 1 - 5) I/O ID from NetPro
WORD
CONx_INT_CN_ID
(x = 1 - 5) Unique internal name of I/O
WORD
CONx_DEVICE_ID
(x = 1 - 5) Low byte: Device I/O, high byte: Rack/Slot of the CP
WORD
CONx_MAXP
(x = 1 - 5) Maximum proportion of bytes, sent and received
INT
CONx_REM_ADDR_LEN
(x = 1 - 5) Length of the I/O address
WORD
CONx_REM_ADDR0..7
(x = 1 - 5) I/O address 0 to 7
BYTE
CONx_LOAD
(x = 1 - 5) Number of bytes sent and received during the sampling

time
DINT
CONx_PER
(x = 1 - 5) Percentage of total number of bytes
INT
CPU_RT_DATA
System structure: Performance data
STRUCT
DAT_PLAU
1 = slowest OB 3x has the lowest priority
BOOL
ERR_NUM
1 = occurrence of an error
INT
EXC_FR3x
(x = 0 8) execution cycle (in ms) of the OB 3x
INT
GRO3xAV
(x = 0 8) gross mean value
REAL
GRO3xCUR
(x = 0 8) gross current value
REAL
GRO3xMAX
(x = 0 8) gross maximum value
REAL
GRO3xMIN
(x = 0 8) gross minimum value
REAL
GRO3xPER
(x = 0 8) gross mean value (in %)
REAL
MAXCYCTI
Set scan cycle monitoring time
INT
N_OB1_CYC
Number of OB 1 calls during a cycle of the slowest OB
INT
NET01AV
Net mean value of OB 1 (in ms)
REAL
NET01CUR
Net current value of OB 1 (in ms)
REAL
NET01MAX
Net maximum value of OB 1 (in ms)
REAL
NET01MIN
Net minimum value of OB 1 (in ms)
REAL
NET01PER
Net mean value of OB 1 (in %)
REAL
NET3xAV
(x = 0 8) net mean value of OB 3x (in ms)
REAL
NET3xCUR
(x = 0 8) net current value of OB 3x (in ms)
REAL
NET3xMAX
(x = 0 8) net maximum value of OB 3x (in ms)
REAL
NET3xMIN
(x = 0 8) net minimum value of OB 3x (in ms)
DINT
NET3xPER
(x = 0 8) net mean value of OB 3x (in %)
REAL
NET8xAV
(x = 0 8) net mean value of OB 8x (in ms)
REAL
NET8xCUR
(x = 0 8) net current value of OB 8x (in ms)
REAL
34

Family: @System
5.3 DIAG_AB: Evaluation of statusword AB7000
I/O
Meaning
Type
Defau
lt
NET8xMAX
(x = 0 8) net maximum value of OB 8x (in ms)
REAL
NET8xPER
(x = 0 8) net mean value of OB 8x (in %)
REAL
OB3x_N_CNT
(x = 0 8) decrementing counter for reduction ratio
INT
OB3x_N_START
(x = 0 8) start value for reduction ratio
INT
REQ01ERR
(x = 0 8) OB request errors since the last reset
BOOL
REQ3xERR
(x = 0 8) OB request errors
BOOL
SFC78_EX
1 = SFC 78 available in CPU
BOOL
SL_OB
Slowest OB 3x
BYTE
SL_OB_EXC_FR
Number of calls of the slowest OB 3x
INT
TOTALAV
Total average value of all OB 1, OB 3x, OB 8x (in %)
DINT
TOTALCUR
Total current value of all OB 1, OB 3x, OB 8x (in %)
DINT
TOTALMAX
Total maximum value of all OB 1, OB 3x, OB 8x (in %)
DINT
TOTALMIN
Total minimum value of all OB 1, OB 3x, OB 8x (in %)
DINT
In/out parameters
I/O
Meaning
Type
Defau
lt
IDLE_CYC
CPU utilization display
INT
You can find additional information on this subject in the following sections:
5.3
DIAG_AB: Evaluation of statusword AB7000
5.3.1
Description of DIAG_OB

FB 414
DIAG_AB Block I/Os (Page 37)
Area of application
The DIAG_AB block evaluates the status word of an AB7000 slave and acknowledges newly
reported errors via the control word of the slave.

35
Family: @System
Calling OBs
The cyclic OB and OB 100.
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC
function:
The block is installed in the run sequence before the MOD_PAL0 or MOD_PAX0 block,
both of which are also installed by the driver generator. The install is executed in the same
cyclic OB as the associated signal processing blocks FF_A_xx.
Parameters are assigned to the LADDR_C input with the address of the control word of the
AB7000.
Parameters are assigned to the input LADDR_S with the address control word of the
AB7000.
The OUT structure CPU_DIAG of the OB_BEGIN block is interconnected with the IN_OUT
structures of the same name of DIAG_AB.
The input mode of the DIAG_AB block is interconnected with the output OMODE_00 of the
PADP_L10 or PADP_L01 block.
The input PA_DIAG of the DIAG_AB block is interconnected with the output PA_DIAG of
the PADP_L10 or PADP_L01 block.
The output OMODE of the DIAG_AB block is interconnected with the input MODE_00 of
the MOD_PAL0 or MOD_PAX0 block.
The output ODIAG of the DIAG_AB block is interconnected with the input PA_DIAG of the
MOD_PAL0 or MOD_PAX0 block.

The DIAG_AB block cyclically analyses the status word of the AB7000 slave,
If a Modbus device fails, or if there is a higher-level error at the MODE input, then the OMODE
and PA_DIAG outputs are set to "Bad":
Parameters
Value
Description
OMODE
16#40000001
Higher level error
ODIAG
16#00400000
Due to process no valid values
After an error exiting state the outputs are set to the status "Good":
Parameters
Value
Description
OMODE
16#80000001
Valid value
ODIAG
PA_DIAG
Diagnostics information from PADP_L10 or PADP_L01 block
The outputs SR_CODE and SR_DATA show the last values of a status tab sent by the AB7000.
The meaning of SR_DATA depends on SR_CODE:
36

Family: @System
SR_CODE
SR_DATA
Description
16#00
Number of retransmissions
Reading or writing an FIM tab needed to be executed again due

to an error
16#01
Address of the FIM No connection to the FIM
16#03
Address of the FIM The FIM has sent more data than expected
16#04
Address of the FIM An error has occurred, no more data is available
16#13
16#1F
No error if SR_DATA = 16#00; otherwise, failure of the FIM (with

the address in SR_DATA)
---
An error is no longer present
Error handling
The validity of input parameters is not checked.
Initialization of outputs OMODE with 16#80000001 ("valid value") and ODIAG with
16#00000000 ("no error")
Time response
Not available
Message response
Not available

Not available
5.3.2
I/Os of DIAG_AB
The factory setting of the block display in CFC is identified in the "I/O" column:
You will find explanations of and information on abbreviations in the section: General
Information About Block Description (Page 11).
Input parameters
I/O
Meaning
Type
Default
LADDR_C
Logical address of the control word
INT
LADDR_S
Logical address of the control word
INT

37
Family: @System
5.4 DPAY_V0: Monitoring DP/PA and Y-Link operating as V0 slave
I/O
Meaning
Type
Default
MODE
Value status
DWORD
16#80 000 000
PA_DIAG
Diagnostic information
DWORD
I/O
Meaning
Type
Default
ODIAG
Field devices diagnostics information
DWORD
Output parameters
OMODE
Value status of the slave
DWORD
SR_CODE
Code of the status tab
BYTE
SR_DATA
Data of the status tab
BYTE
I/O
Meaning
Type
Default
CPU_DIAG
CPU diagnostics (system structure)
STRUCT
In-out parameters
5.4
DPAY_V0: Monitoring DP/PA and Y-Link operating as V0 slave
5.4.1
Description of DPAY_V0

FB 108
DPAY_V0 Block I/Os (Page 42)
Area of application
Block DPAY_V0 monitors the status of a DP/PA or Y-Link as a V0 slave (IM 157) and reports
the corresponding error events.
The DP/PA link operates as a PA master for the lower-level PA field devices and as a slave
on the DP bus.
The Y-Link operates as a DP master for the lower-level DP field devices and as a slave on the
higher-level DP bus.
38

Family: @System
Calling OBs
OB 1
Cyclic program
OB 70
I/O redundancy error
OB 72
CPU redundancy error
OB 82
Diagnostic interrupt
OB 85
Program execution error
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:
The block is integrated in the run sequence downstream from the SUBNET block and
upstream from the PADP_L0x block.
RACK_NO (rack/station number) is configured.
SUBN_TYP (internal/external PROFIBUS interface) is set.
SUBN1_ID (ID of the master systems) is set.
SUBN2_ID (ID of the redundant master system) is set.
DADDR (diagnostic address of the DP/PA or Y-Link) is set.
DPPA_xx (slave xx address), 1st module (slot) address of slave xx in the link, number of
slots of slave xx are set.
The CPU_DIAG of the OB_BEGIN block and SUB_DIAG of the SUBNET block OUT
structures are interconnected with the IN_OUT structures of the same name of DPAY_V0.
In the case of PA or DP field devices, they are interconnected with PADP_L0x.

If redundancy losses and link failures occur, the DPAY_V0 block generates a control-system
error message for the OS. The block also indicates error events at active links (SUBN1ERR,
SUBN2ERR) and at the preferred channel (SUBN1ACT, SUBN2ACT) in the output status bar.
The output structure RAC_DIAG contains the geographic address of the link as well as the
group error information RACK_ERR. The corresponding link is not available if RACK_ERR =
1.
The block requires a PROFIBUS DP interface. This can either be integrated in the CPU or
provided by means of an external DP interface (CP). PROFIBUS DP is converted to
PROFIBUS PA by means of a SIMATIC DP/PA-Link.
The field devices of a link are always addressed at the higher-level DP bus via the DP address
of IM 157.
The AS addresses the field devices via the link, i.e., indirectly. The topological structure of the
PA bus is mapped in the flat structure of the slave interface. A maximum of 64 field devices

39
Family: @System
can be operated downstream from a link. Each field device can use any number of virtual slots
at the link, up to 223 maximum.
In order to enable the assignment of diagnostic data to the field devices, the block provides
each field device a DPPA_xx input structure consisting of 3 bytes with the following contents:
Byte (SLAV_NO) = node number (address) of the field device at the PA/DP master system
of the LINK
Byte (SLOT_NO) = 1st module address of the field device in the link
Byte (SLAV_SL) = number of slots of the field device
The "Generate module drivers" CFC function fetches this data from HW Config.
The start information is read from the CPU_DIAG I/O structure. This structure must be
interconnected to the CPU_DIAG structure of the OB_BEGIN block (carried out by the CFC
function "Generate module drivers").
The block generates a corresponding message (see "Message Response") on the basis of
the startup information of calling OBs, if the current instance is affected.
When operating with redundant PROFIBUS DP interfaces, the block determines the currently
active preferred channel (SUBN1ACT, SUBN2ACT) by evaluating the error events as well as
via the diagnostic address DADDR of the link.
SFC 13 (DPNRM_DG, read diagnostic data consistently) reads the diagnostic data (OB 82).
The reading process can take several cycles (OB 1). It is therefore possible in a few rare cases
that the triggering diagnostic event cannot be recognized.
Diagnostic user data contains information about the status of the link, and of connected field
devices. The structure DPPA_ST indicates the link status.
The status of a field device is entered in the structure DPA_M_xx.
A field device can have a maximum of 32 slots (modules). Three block types are available,
according to the number of slots on the field device:
PADP_L00 (field device with max. 7 slots)
The structure DPA_M_xx is interconnected to the structure DPA_M and the output EN_Mx with
EN of one of the PADP_Lxx blocks (carried out by the CFC function "Generate module
drivers").
The DPA_M_xx structure consists of two DWORD value (S_01 for modules 1 to 16 and S_02
for modules 17 to 32) and one BOOL value (S_ERR = DP/PA field device faulty). Two bits of
the DWORD are assigned to each slot of the DP/PA field device, whereby bit 0 and bit 1 belong
to slot 1 (module 1) of the DP/PA field device, etc. These bits are defined as follows:
40
Status Bit 0
Status Bit 1
Meaning
Module x OK (valid user data)
Module x error (invalid user data)
Wrong module x (invalid user data)
No module x (invalid user data)

Family: @System
If the diagnostics alarm applies to the entire DP/PA field device, then DPA_M_xx.S_ERR =
TRUE is set.
Note: If you want to change the SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection
to CPU 1) inputs online, you must set input ACC_ID = TRUE. This verifies the Link states and
updates output values.
Redundancy
The block supports redundant DP master systems in an H system (distributed I/Os only). The
SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs of the SUBNET
block are configured with the numbers of the redundant DP master systems. If the DP master
systems are not redundant, the remaining input is set to 16#FF (default).
Error handling
For additional information on this, refer to the section:
Error information of the MSG_STAT output parameter (Page 353)" section.
The block initializes the messages of ALARM_8P. Availability of the link is verified. In H
systems, determines the preferred channel of the link.
Overload behavior
The block counts OB 86 (no DP master system failure, see SUBNET block) and OB 82 calls.
Both counters are reset in OB 1. If more than five OB 86 events or more than five OB 82 events
in succession before the cycle control point is reached (OB 1), these events are discarded and
the message ""DP-Link DP-Master:x Rack:y: Multiple failure" or the message "DP-Link
Master:x Rack:y: Muktiple alarm (OB 82)" is output. 1 minute later the status of the link will be
re-checked.
Time response
Not available
Message response
After its call by OB 70, OB 72, OB 85 or OB 86, the block analyzes the status of its assigned
CPU, DP master and link. If the link loses redundancy or fails, the block outputs corresponding
messages via ALARM_8P.
The block generally reports only the events generated in the link that it monitors. Redundancy
loss and link failures which are caused by the failure of a DP masters or of a CPU, are initially
neither signaled nor indicated at the outputs SUBN1ERR and SUBN2ERR.
The DELAY input is used to delay the output of error messages for higher-priority outgoing
errors. This delay time is configurable. When the block recognizes an outgoing error at an

41
Family: @System
interconnected DP master, it initially assumes that there is a faulty assigned DP slave in the
link it monitors and sets the corresponding output SUBNxERR. The error status is not reset
until the DP slave returns (in this case: OB 86, OB 70). The blocks delay error messages
relevant to any slave failure states for a time in seconds as specified in DELAY, in order not
to trigger the output of surge of messages from DP slaves which are not yet synchronized after
the master has returned. An error message is only output to the OS when the DP slave has
not reported its return before this delay time has expired.
Do not set the value of DELAY too high, since messages reporting faulty DP slaves or their
removal during a master failure will be output too late to the OS after the DP master returns.
OB no.
Start Event
Message
OB 1
Cyclic processing
Repeat the update of ALARM_8P

outputs/messages, if necessary
OB 70
Redundancy loss
Link redundancy loss/return
OB 85
Link failure going
OB 86
Rack failure
Link failure coming/going
OB 100
Restart
Initialization of ALARM_8P

manual.
Message texts and associated values of DPAY_V0 (Page 44)
5.4.2
I/Os of DPAY_V0
I/Os
42

Family: @System
Input parameters
I/O
(parameter)
Meaning
Data type
Default
DADDR
Diagnostic address of the DP slave
INT
DELAY
Interrupt delay (s)
INT
15
DIAG_BUF

personnel)
BOOL
DPPA_xx
Information of the DP/PA slave (xx = 00 - 63)
STRUCT
EN_MSG
1 = enable message
BOOL
EV_ID
Message number
DWORD
MS
Maintenance status
DWORD
RACK_NO
Rack/station number
WORD
SUBN_TYP
1 = external DP interface
BOOL
SUBN1_ID
ID of the primary DP master system
BYTE
255
SUBN2_ID
ID of the redundant DP master system
BYTE
255
I/O
(parameter)
Meaning
Data type
Default
DPA_M_xx
Status of the DP/PA slave (xx = 00 - 63)
STRUCT
DPPA_ST
DP/PA/Y-Link status
STRUCT
EN_Mxx
1 = Enable modules (xx = 00 - 63)
BOOL
MSG_STAT
Message error information
WORD
O_MS
Maintenance status
DWORD
RAC_DIAG
Rack diagnostics
BOOL
SUBN1ACT
1 = Slave 1 is active
BOOL
SUBN1ERR
1 = Error in DP master system 1
BOOL
SUBN2ACT
BOOL
SUBN2ERR
BOOL
I/O
(parameter)
Meaning
Data type
Default
ACC_ID
1 = accept MODE settings
BOOL
CPU_DIAG
STRUCT
SUB_DIAG
OB startup information
STRUCT
Output parameters
In/out parameters

43
Family: @System
Message texts and associated values of DPAY_V0 (Page 44)
5.4.3
Message texts and associated values of DPAY_V0

Message no.
Message class
DP Link @1%d@/ @3%d@: Redundancy loss
DP Link @2%d@/ @3%d@: Redundancy loss
DP Link @1%d@/ @3%d@: Failure
DP Link @2%d@/ @3%d@: Failure
DP LINK @1%d@/ @3%d@: Multiple alarm (OB 82)
DP LINK @1%d@/ @3%d@: Multiple failure

Associated value
Block parameter
ID of the primary DP master system (SUBN1_ID)
ID of the redundant DP master system (SUBN2_ID)
Rack/station number (RACK_NO)
See also
Message Classes (Page 355)
44

Family: @System
5.5 DPAY_V1: Enabling blocks downstream of a DP/PA and Y-Link operating as V1 slave
5.5
DPAY_V1: Enabling blocks downstream of a DP/PA and Y-Link

operating as V1 slave
5.5.1
Description of DPAY_V1

FB 115
DPAY_V1 Block I/Os (Page 47)
Area of application
The DPAY_V1 block enables the field device-specific blocks downstream of the DP/PA or Y
links.
The DP/PA link acts as a PA master for the lower-level PA field devices, and as a slave on the
DP bus.
The Y link acts as a DP master for the lower-level DP field devices, and as a slave on the
higher-level DP bus.
Calling OBs
OB 1
Cyclic program
OB 55
Status interrupt
OB 56
Update interrupt
OB 57
Vendor-specific interrupts
OB 70
OB 72
OB 82
OB 83
Insert/remove module interrupt
OB 85
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:
The block is integrated in the run sequence after the OB_DIAG1 block.
SUBN_1ID (ID of primary DP master system) is configured.
SUBN_2ID (ID of secondary DP master system) is configured.

45
Family: @System
5.5 DPAY_V1: Enabling blocks downstream of a DP/PA and Y-Link operating as V1 slave
RACK_NO (rack/station number) is configured.
structures of the same name of DPAY_V1.
The OUT structure CPU_OB_5X of the OB_BEGIN block is interconnected with the IN_OUT
structures of the same name of DPAY_V1.
EN_Mxx are interconnected with EN of OB_DIAG1 and PADP_L10 for each field device.

The start information is read from the CPU_DIAG I/O structure. The structure must be
interconnected with the CPU_DIAG structure of OB_BEGIN (carried out by the CFC function
Generate module drivers). The affected downstream blocks will be enabled according to the
start information.
OB 5x characteristics
Enables the output for the affected field device.
Redundancy
The redundancy is evaluated in OB_DIAG1.
Error handling
The plausibility of input parameters is not checked.
The block initializes its outputs.
Overload behavior
OB_DIAG1 disables the block in response to an overload.
Time response
Not available
Message response
Not available

The block has no faceplate.
46

Family: @System
5.6 DPAY_V1_PN: Enabling blocks downstream of a DP/PA and Y-link operating as a V1 Slave
5.5.2
I/Os of DPAY V1
Input parameters
I/O
(parameter)
Meaning
Data type
Default
CPU_DIAG
STRUCT
CPU_OB_5X
OB_5x startup information
STRUCT
DPPA_xx
Information about the DP/PA slave (xx = 00 - 63)
STRUCT
RACK_NO
Rack/station number
WORD
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
I/O
(parameter)
Meaning
Data type
Default
CPU_DIAG
STRUCT
CPU_OB_5X
STRUCT
EN_Mxx
1 = Enable slave (xx = 00 - 63)
BOOL
Output parameters
5.6
DPAY_V1_PN: Enabling blocks downstream of a DP/PA and Y-link

operating as a V1 Slave
5.6.1
Description of DPAY_V1_PN

FB 204
I/Os of DPAY_V1_PN (Page 48)
Area of application
The DPAY_V1_PN block releases the field device-specific blocks downstream of the IE/PB
link.

47
Family: @System
5.6 DPAY_V1_PN: Enabling blocks downstream of a DP/PA and Y-link operating as a V1 Slave
The IE/PB link operates as a PA master for the lower-level PA field devices and as a slave on
the IE bus.
See also
General Information About Block Description (Page 11)
5.6.2
I/Os of DPAY_V1_PN
Input parameters
I/O
(parameter)
Meaning
Data type
DPPA_00
Information about the DP/PA slave (xx = 00 - 63)
STRUCT
RACK_NO
Rack number
BYTE
Default
SUBN1_ID
PN IO system 1 ID (100 - 115)
BYTE
255
SUBN2_ID
BYTE
255
I/O
(parameter)
Meaning
Data type
Default
EN_Mxx
1 = Enable slave (xx = 00 - 63)
BOOL
I/O (parameter)
Meaning
CPU_DIAG_PN
System structure: CPU diagnostics
STRUCT
CPU_OB_5X
STRUCT
Output parameters
In-out parameters
48
Data type
Default

Family: @System
5.7 DPDIAGV0: Monitoring the status of ET 200S modules acting as DPV0 slaves after the Y link
5.7
DPDIAGV0: Monitoring the status of ET 200S modules acting as DPV0

slaves after the Y link
5.7.1
Description of DPDIAGV0

FB 117
DPDIAGV0 Block I/Os (Page 51)
Area of application
The DPDIAGV0 block monitors the status of the modules of an ET 200S acting as a DPV0
slave (IM 151-1 High Feature) after a Y link.
Calling OBs
OB 1
Cyclic program
OB82
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:
The block is integrated in the run sequence after the OB_DIAG1 block.
The following inputs are configured:
SUBN_1ID (ID primary DP master system)
SUBN_2ID (ID secondary DP master system)
RACK_NO (rack/station number)
The following I/Os are interconnected:
The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK
block with the DPDIAGV0-block IN_OUT structures of the same name
EN_Mxx with EN of the OB_DIAG1 block and the DPDIAGV0 block of each ET 200S
The DPA_M_xx outputs with the DPA_M input and EN_Mxx output with EN of a MOD_4
block.

49
Family: @System

In the event of a diagnostic interrupt, the DPDIAGV0 block analyzes the ID-specific diagnostic
data, and the module status of an ET 200S in DPV0 mode after a Y link.
The upstream OB_DIAG1 block detects the failure/restart of an ET 200S.
The AS addresses the devices via the link, i.e., indirectly. The topological structure of the DP
bus is mapped in the flat structure of the slave interface. There may be up to 64 devices
downstream of a Link. Each device can be assigned any number of virtual slots (max. 223) of
the link. To assign the diagnostic data of an ET 200S, the block uses the following inputs of
data type BYTE with the meaning shown below:
SUBN1_ID = Primary ID of the master system
SUBN2_ID = Secondary ID of the master system
RACK_NO = Station number (address) of the DP master system of the link
PADP_ADR = Station number (address) of the ET 200S
SLAVE _NO = 1st module address of the ET 200S in the link
SLAVE_SL = Number of slots at the ET 200S
The "Generate module drivers" CFC function fetches this data from HW Config.
The useful diagnostic data contains information about the ET 200S status.
The status of an ET 200S module is entered in byte DPA_M_xx.
An ET 200S can have up to 64 slots (modules).
Bits 0 to 2 of DPA_M are defined as follows:
Status Bit 2
Status Bit 1
Status Bit 0
Meaning
ET 200S failure (invalid user data)
to CPU 1) inputs online, you must set input ACC_ID = TRUE. This verifies the Link states and
updates output values.
Redundancy
Only non-redundant devices may be used downstream of a Y link.
Error handling
The validity of input parameters is not checked.
The system verifies that the ET 200S is available.
50

Family: @System
Overload behavior
The overload behavior takes place in the upstream OB_DIAG1 block.
Time response
Not available
Message response
Not available

5.7.2
I/Os of DPDIAGV0
Input parameters
I/O
(parameter)
Meaning
Data type
Default
DADDR
Diagnostic address of the Y-Link
INT
DIAG_BUF

personnel)
BOOL
PADP_ADR
DP address ET 200S
BYTE
255
RACK_NO
Rack/station number
BYTE
SLAVE_NO
1. Slot number of the slave in the Y-link
BYTE
SLAVE_SL
Number of ET 200S slots
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255

51
Family: @System
5.8 DREP: Diagnostic Repeater in the DP master system
Output parameters
I/O
(parameter)
Meaning
Data type
Default
DPA_M_xx
Status of the DP/PA slave (xx = 00 - 63)
BYTE
EN_Mxx
1 = Enable modules (xx = 00 - 63)
BOOL
QRACKF
1 = ET 200S failure
BOOL
SUBNERR
1 = Y link failure
BOOL
I/O
(parameter)
Meaning
Data type
Default
ACC_ID
BOOL
CPU_DIAG
STRUCT
RAC_DIAG
Rack diagnostics of the DP slave downstream of
STRUCT
In/out parameters
Y link (system structure)
5.8
DREP: Diagnostic Repeater in the DP master system
5.8.1
Description of DREP

FB 113
DREP block I/Os (Page 56)
Area of application
The DREP block evaluates the diagnostic data from a SIMATIC diagnostic repeater for
PROFIBUS DP. This repeater must be connected to a DP master.
Calling OBs
52
OB 1
Cyclic processing
OB 82
OB 86
Rack failure
OB 100
Warm restart (startup, message initialization)

Family: @System
Use in CFC
function:
Block OB_DIAG1 is installed in the run sequence upstream of the DREP block.
The following addresses are configured:
The diagnostic address DADDR of the diagnostics repeater
The geographic address (SUBN_ID and PADP_ADR)
The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the
OB_DIAG1 block with the IN_OUT structures of the same name of the DREP block.
The EN input with the output of an AND block.
The inputs of the AND block with the EN_SUBx outputs (x = number of the DP master
system) of the OB_BEGIN block, with EN_Rxxx (xxx = rack/station number) of the
SUBNET block and with EN_F of the OB_DIAG1 block.
EN_DIAG with the EN_DIAG output of the OB_DIAG1 block.

The diagnostics repeater is assigned the following tasks:
Diagnostics function for two PROFIBUS segments (DP2 and DP3):
The diagnostics function returns the location and cause of line faults, such as a wire break
or missing terminating resistors.
The error location is output, including a reference to the relevant nodes, e.g., "Short-circuit
to shielding at signal line A, node 12 <-> 13".
Repeater function for three PROFIBUS segments (DP1, DP2, DP3):
The diagnostics repeater amplifies data signals on the bus and interconnects the relevant
RS-485 segments.
Galvanic/electrical isolation of the PG interface from other bus segments:
Even if the system is operating at higher transmission rates, interference due to the removal
or connection of PG cables is not to be expected at the other PROFIBUS DP segments.
The manual titled Diagnostic Repeaters for PROFIBUS DP contains information about the
structure of line error states at the DP1, DP2 and DP3 segments and describes the PG
interface.
Block DREP reports only the diagnostic events at segments DP2 and DP3 of the diagnostic
repeater.
Events of the DP1 segment are reported as general "Cable disturbance" group error.
The PG interface is not evaluated and does not result in a message.
Failure and return of the diagnostics repeater are detected by the upstream OB_DIAG1 block,
and are forwarded to the block to report "DR failure".
If an error occurs, an incoming "line error" group message is generated for each segment (DP2
or DP3) when a diagnostic repeater detects the error event (bits in the diagnostic message
frame indicating the cause of error):

53
Family: @System
Bit
Description
A.0
1: The location and cause of the error cannot be identified (possibly electromagnetic
interference)
A.1
CPU redundancy loss
A.2
1: - -
A.3
1: Further measurement circuits at the segment, the other diagnostic repeater is connected
to its segment DP2
A.4
to its segment DP3
A.5
1: - -
A.6
1: Cause of error is not clearly identified
A.7
1: Critical message frame error rate
B.0
1:- -.
B.1
1: - -
B.2
1: - -
B.3
1: - -
B.4
1: - -.
B.5
1: - -
B.6
1: - -.
B.7
1: - -
C.0
1: Segment automatically switched off due to continuous zero level on the line.
C.1
1: Segment automatically switched off due to constantly fluctuating line levels.
C.2
1: - -
C.3
1: - -
C.4
1: More than 32 nodes connected to the measurement segment.
C.5
1: The distance between the node and the diagnostic repeater exceeds the permitted
line length.
C.6
1: The maximum permitted number of diagnostic repeaters connected in series has been
exceeded.
C.7
1: - -
The outgoing message will be generated when all segment bits are equal to zero.
Call HW Config to analyze details of events output by the diagnostic repeater.
An appropriate incoming/outgoing message will be generated for each segment (DP2 or DP3)
in response to the following events detected by a diagnostic repeater:
54
Bit
Description
A.0
1: -
A.1
1:-
A.2
1: -
A.3
1: -
A.4
1: -
A.5
1: -
A.6
1: -
A.7
1:

Family: @System
Bit
Description
B.0
1: Wire break on signal line A.
B.1
1: Short-circuit to shield on signal line B.
B.2
1: -
B.3
1: Short-circuit to shield on signal line A.
B.4
1: Wire break on signal line B.
B.5
1: -
B.6
1: Wire break on signal line A and/or B, or the terminating resistor is missing.
B.7
1: Short-circuit between signal line A and/or B, or an additional terminating resistor

has been installed.
C.0
1: -
C.1
1: -
C.2
1: -
C.3
1: -
C.4
1: -
C.5
1: -.
C.6
1: -
C.7
1: -
Events detected by the diagnostics repeater are acquired synchronously in OB 82. Diagnostic
event data is fetched via SFB 54 in the OB_BEGIN block and written to the structure DINFO.
The function always sets just one bit to indicate the cause of an event-entering state. Bit C7
may also be set if the diagnostics repeater has detected further errors. In this case, all
previously reported events will be queued. DREP generates a corresponding group error
message via ALARM_8P. Flutter messages may occur, particularly in response to error causes
A.0.1 and A.6.1. They are suppressed as follows:
After an outgoing message, a new outgoing message will be delayed by the time in [s] set at
the DELAY parameter. If a further error is queued, the outgoing message will not be generated
until this error has been reported outgoing.
Error handling
The block evaluates the error information from ALARM_8P, and writes it to the corresponding
output parameters. You will find additional information about this in the "Error information of
output parameter MSG_STAT (Page 353)" section.
The block reports a diagnostic error if an error occurs while reading the diagnostic data, or if
any other fault corrupts diagnostic data.
ALARM_8P messages are initialized by the DREP block. This uses SFC13 (DPNRM_DG) to
read the latest diagnostic information from the diagnostic repeater.
Overload behavior
The interconnected OB_DIAG1 locks the call of DREP for diagnostics if an overload has
occurred.

55
Family: @System
Dynamic response:
Not available
Message response:
The multiple instances ALARM_8P are only called if a message is to be output by this instance.
It is only at this point that previously acknowledged messages are updated by the
corresponding ALARM block. If the connection to WinCC is down, each ALARM_8P instance
can hold up to two message statuses of its event ID. (Usually two messages maximum). Flutter
messages can be suppressed via the DELAY input.
The block generates the messages listed below:
OB no.
Start Event
Message
Cyclic processing
Call of ALARM_8P due to incomplete transfer or unacknowledged

message
82
Group message
100
Restart

manual.
Message texts and associated values of DREP (Page 58)
5.8.2
I/Os of DREP
56

Family: @System
Input parameters
I/O
(parameter)
Meaning
Type
Default
DADDR
Diagnostic address of the diagnostic repeater
INT
DELAY
Interrupt delay (s)
INT
DIAG_BUF
Entry in CPU diagnostic buffer
BOOL
EN_DIAG
1 = Queued diagnostic event
BOOL
EN_MSG
1 = enable message
BOOL
EV_IDx
Message number
DWORD
MS
Maintenance status
DWORD
PADP_ADR
DP/PA address of the diagnostic repeater
BYTE
255
SUBN_ID
DP master system ID
BYTE
255
I/O
(parameter)
Meaning
Type
Default
DINFO
Diagnostic information from the diagnostic repeater
STRUCT
MSG_ACKx
Message acknowledgment
WORD
MSG_STATx
WORD
O_MS
Maintenance status
DWORD
QDREPF
1 = Removed/faulty diagnostic repeater
BOOL
QERR
1 = program error
BOOL
I/O
(parameter)
Meaning
Type
Default
ACC_MODE
BOOL
CPU_DIAG
CPU diagnostics
STRUCT
RAC_DIAG
OB_DIAG1 diagnostics
STRUCT
Output parameters
In/out parameters
Message texts and associated values of DREP (Page 58)

57
Family: @System
5.8.3
Message texts and associated values of DREP
Assignment of message text and message class (Page 355)

Message block
ALARM_8P
Message no.
Messag
e
class
EV_ID1
DR @1%d@/@2%d@/ Segment DP2: Line fault
DR @1%d@/@2%d@/DP2: @5%d@.@6%d@m/wire
break A /@3%d@
@4%d@
DR @1%d@/@2%d@/DP2: @5%d@.@6%d@m/
short A/@3%d@
@4%d@
DR @1%d@/@2%d@/DP2: @5%d@.@6%d@m/wire
break B/@3%d@ @4%d@
DR @1%d@/@2%d@/DP2:
short B/@3%d@ @4%d@
DR @1%d@/@2%d@/DP2:
@5%d@.@6%d@m/
wire break AB or terminating resistor missing/@3%d@
@4%d@
@5%d@.@6%d@m/
DR @1%d@/@2%d@/DP2:
short AB or too many terminating resistors/@3%d@
@4%d@
DR @1%d@/@2%d@/ segment DP1: Line fault
DR @1%d@/@2%d@/ segment DP3: Line fault
DR @1%d@/@2%d@/DP3: @5%d@.@6%d@m/wire
break A /@3%d@
@4%d@
DR @1%d@/@2%d@/DP3: @5%d@.@6%d@m/
short A/@3%d@
@4%d@
DR @1%d@/@2%d@/DP3: @5%d@.@6%d@m/wire
break B/@3%d@ @4%d@
DR @1%d@/@2%d@/DP3:
short B/@3%d@ @4%d@
DR @1%d@/@2%d@/DP3:
@5%d@.@6%d@m/
wire break AB or terminating resistor missing/@3%d@
@4%d@
@5%d@.@6%d@m/
DR @1%d@/@2%d@/DP3:
short AB or too many terminating resistors/@3%d@
@4%d@
DR @1%d@/@2%d@: @7W%t#DREP_TXT@
EV_ID2
@5%d@.@6%d@m/
@5%d@.@6%d@m/
You will find the message texts and their text numbers in "Text library for DREP (Page 360)".
58

Family: @System
5.9 DREP_L: Diagnostic Repeater downstream of a Y-Link

Message block
ALARM_8P
Associat
ed
value
Block
parameter
Meaning
EV_ID1
SUBN_ID
DP master system ID (byte)
PADP_ADR
Address of diagnostic repeater (byte)
EV_ID2
Station x (segment DP2)
Station y (segment DP2)
Removal of diagnostic repeater (segment DP2)
SUBN_ID
PADP_ADR

Text number (Message 1 - 2) of DREP_TXT
5.9
DREP_L: Diagnostic Repeater downstream of a Y-Link
5.9.1
Description of DREP_L

FB 125
DREP_L Block I/Os (Page 63)
Area of application
The DREP_L block evaluates diagnostic data from a SIMATIC diagnostic repeater for
PROFIBUS DP. The diagnostic repeater (after DPV0) must be connected downstream of a YLink (after DPV1).
Calling OBs
OB 1
Cyclic processing
OB 82
OB 86
Rack failure
OB 100
Warm restart (startup, message initialization)

59
Family: @System
Use in CFC
function:
The OB_DIAG1 block is integrated into the run sequence upstream of DREP_L.
The following addresses are configured:
The diagnostic address of the DP/PA link (DADDR) is connected downstream of the
diagnostic repeater
The geographical address (SUBN1_ID, SUBN2_ID, RACK_NO and PADP_ADR)
The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the
OB_DIAG1 block with the DREP_L INOUT structures of the same name.
The EN input is interconnected with the output of an AND block.
The inputs of the AND block with the EN_SUBx outputs (x = number of the DP master
system) of the OB_BEGIN block, with EN_Rxxx (xxx = rack/station number) of the
SUBNET block and with EN_F of the OB_DIAG1 block.
EN_DIAG with the EN_DIAG output of the OB_DIAG1 block.

The diagnostics repeater is assigned the following tasks:
Diagnostics function for two PROFIBUS segments (DP2 and DP3):
The diagnostics function returns the location and cause of line faults, such as a wire break
or missing terminating resistors.
The error location is output, including a reference to the relevant nodes, e.g., "Short-circuit
to shielding at signal line A, node 12 <-> 13".
Repeater function for three PROFIBUS segments (DP1, DP2, DP3):
The diagnostics repeater amplifies data signals on the bus and interconnects the relevant
RS-485 segments.
Galvanic/electrical isolation of the PG interface from other bus segments:
Even if the system is operating at higher transmission rates, interference due to the removal
or connection of PG cables is not to be expected at the other PROFIBUS DP segments.
The manual titled Diagnostic Repeaters for PROFIBUS DP contains information about the
structure of line error states at the DP1, DP2 and DP3 segments and describes the PG
interface.
Block DREP_L only reports diagnostic events at segments DP2 and DP3 of the diagnostic
repeater.
Events of the DP1 segment are reported as general "Cable disturbance" group error.
The PG interface is not evaluated and does not result in a message.
Failure and return of the diagnostics repeater are detected by the upstream OB_DIAG1 block,
and are forwarded to the block to report "DR failure".
If an error occurs, an incoming "line error" group message is generated for each segment (DP2
or DP3) when a diagnostic repeater detects the error event (bits in the diagnostic message
frame indicating the cause of error):
60

Family: @System
Bit
Description
A.0
1: The location and cause of the error cannot be identified (possibly electromagnetic
interference)
A.1
CPU redundancy loss
A.2
1: - -
A.3
to its segment DP2
A.4
to its segment DP3
A.5
1: - -
A.6
1: Cause of error is not clearly identified
A.7
1: Critical message frame error rate
B.0
1:
B.1
1:
B.2
1: - -
B.3
1:
B.4
1:
B.5
1: - -
B.6
1:
B.7
1:
C.0
1: Segment automatically switched off due to continuous zero level on the line.
C.1
1: Segment automatically switched off due to constantly fluctuating line levels.
C.2
1: - -
C.3
1: - -
C.4
1: More than 32 nodes connected to the measurement segment
C.5
1: The distance between the node and the diagnostic repeater exceeds the permitted
line length
C.6
1: The maximum permitted number of diagnostic repeaters connected in series has been
exceeded
C.7
1: - -
The outgoing message will be generated when all segment bits are equal to zero.
Call HW Config to analyze details of events output by the diagnostic repeater.
An appropriate incoming/outgoing message will be generated for each segment (DP2 or DP3)
in response to the following events detected by a diagnostic repeater:
Bit
Description
A.0
1: -
A.1
1:-
A.2
1: -
A.3
1: -
A.4
1: -
A.5
1: -
A.6
1: -
A.7
1:

61
Family: @System
Bit
Description
B.0
1: Wire break at signal line A
B.1
1: Short-circuit to shielding at signal line B
B.2
1: -
B.3
1: Short-circuit to shielding at signal line A
B.4
1: Wire break at signal line B
B.5
1: -
B.6
1: Wire break at signal line A and/or B, or the terminating resistor is missing
B.7
1: Short-circuit between signal line A and/or B, or an additional terminating resistor has been
installed
C.0
1: -
C.1
1: -
C.2
1: -
C.3
1: -
C.4
1: -
C.5
1: -.
C.6
1: -
C.7
1: -
Events detected by the diagnostics repeater are acquired synchronously in OB 82. Diagnostic
event data is fetched via SFB 54 in the OB_BEGIN block and written to the structure DINFO.
The function always sets only one bit to indicate the cause of an incoming event. Bit C7 may
also be set if the diagnostics repeater has detected further errors. In this case, all previously
reported events will be queued. DREP_L generates a corresponding group error message via
ALARM_8P. Flutter messages may occur, particularly in response to error causes A.0.1 and
A.6.1. They are suppressed as follows:
After an outgoing message, a new outgoing message will be delayed by the time in [s] set at
the DELAY parameter. If a further fault is queued, the outgoing message will not be generated
until this fault is outgoing.
Error handling
The block evaluates the error information from ALARM_8P, and writes it to the corresponding
output parameters.
You will find additional information in the "Error information of output parameter MSG_STATx
(Page 353)" section.
The block reports a diagnostic error if an error occurs while reading the diagnostic data, or if
any other fault corrupts diagnostic data.
ALARM_8P messages are initialized by the DREP_L block The current diagnostics information
is read from the diagnostics repeater using SFB 52 (RDREC).
62

Family: @System
Overload behavior
In the event of an overload, the upstream OB_DIAG1 block prevents DREP_L being called for
diagnostics.
Dynamic response:
Not available
Message response:
can hold up to two message statuses of its event ID. Flutter messages can be suppressed via
the DELAY input.
The block generates the messages listed below:
OB no.
Start event
Message
Cyclic processing
Call of ALARM_8P due to incomplete transfer or unacknowledged

message
82
Group message
100
Restart

manual.
Message Texts and associated values of DREP_L (Page 65)
5.9.2
I/Os of DREP_L

63
Family: @System
Input parameters
I/O
(parameter)
Meaning
Type
Defa
ult
DADDR
Diagnostic address of the DP/PA link
INT
DELAY
Interrupt delay (s)
INT
DIAG_BUF

personnel)
BOOL
EN_DIAG
BOOL
EN_MSG
1 = enable message
BOOL
EV_IDx
Message number
DWORD
MS
Maintenance status
DWORD
PADP_ADR
DP/PA address of the diagnostic repeater
BYTE
255
RACK_NO
Number of the rack
BYTE
255
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
I/O
(parameter)
Meaning
Type
Defa
ult
DINFO
Diagnostic information from the diagnostic repeater
STRUCT
MSG_ACKx
WORD
MSG_STATx
WORD
O_MS
Maintenance status
DWORD
QDREPF
1 = Removed/faulty diagnostic repeater
BOOL
QERR
1 = program error
BOOL
I/O
(parameter)
Meaning
Type
Defa
ult
ACC_MODE
BOOL
CPU_DIAG
CPU diagnostics
STRUCT
RAC_DIAG
OB_DIAG1 diagnostics
STRUCT
Output parameters
In/out parameters
Message texts and associated values of DREP_L (Page 65)
64

Family: @System
5.9.3
Message texts and associated values of DREP_L

Message block Message no.
ALARM_8P
Messag
e
class
EV_ID1
DR @1%d@/@2%d@/@3%d@/ Segment DP2: Line fault
DR @1%d@/@2%d@/@3%d@/DP2:
@6%d@.@7%d@m/wire break A/ @4%d@
DR @1%d@/@2%d@/@3%d@/DP2:
@6%d@.@7%d@m/short A/@4%d@
DR @1%d@/@2%d@/@3%d@/DP2:
@6%d@.@7%d@m/wire break B/@4%d@
DR @1%d@/@2%d@/@3%d@/DP2:
@6%d@.@7%d@m/short B/@4%d@
DR @1%d@/@2%d@/@3%d@/DP2:
@6%d@.@7%d@m/wire break AB or terminating resistor
missing/@4%d@
@5%d@
DR @1%d@/@2%d@/@3%d@/DP2:
@6%d@.@7%d@m/short AB or too many terminating
resistors/@4%d@
@5%d@
DR @1%d@/@2%d@/@3%d@/ Segment DP1: Line fault S
EV_ID2
@5%d@
@5%d@
@5%d@
@5%d@
S
S
S
DR @1%d@/@2%d@/@3%d@/ Segment DP3: Line fault
DR @1%d@/@2%d@/@3%d@/DP3:
@6%d@.@7%d@m/wire break A/ @4%d@
DR @1%d@/@2%d@/@3%d@/DP3:
@6%d@.@7%d@m/short A/@4%d@
DR @1%d@/@2%d@/@3%d@/DP3:
@6%d@.@7%d@m/wire break B/@4%d@
DR @1%d@/@2%d@/@3%d@/DP3:
@6%d@.@7%d@m/short B/@4%d@
DR @1%d@/@2%d@/@3%d@/DP3:
@6%d@.@7%d@m/wire break AB or terminating resistor
missing/@4%d@
@5%d@
DR @1%d@/@2%d@/@3%d@/DP3:
@6%d@.@7%d@m/short AB or too many terminating
resistors/@4%d@
@5%d@
DR @1%d@/@2%d@/@3%d@: @8W
%t#DREP_L_TXT@
@5%d@
@5%d@
@5%d@
@5%d@
S
S
S
You will find the message texts and their text numbers in "Text library for DREP_L (Page 360)".

65
Family: @System
5.10 FFD_CIF: Monitoring FF slaves in CIF mode

Message block
ALARM_8P
Associated
value
Block
parameter
Meaning
EV_ID1
SUBN_ID1
RACK_NO
Rack/station number (byte)
PADP_ADR
EV_ID2
SUBN_ID1
RACK_NO
PADP_ADR
If SUBN_ID1 = 16#FF, SUBN_ID2 is used as associated value 1.
See also
5.10
FFD_CIF: Monitoring FF slaves in CIF mode
5.10.1
Description of FFD_CIF

FB 145
I/Os of FFD_CIF (Page 68)
Area of application and method of operation

The FFD_CIF blocks monitors the higher-level errors of a field device, such as failure/return.
The block runs acyclically.
The block FFD_CIF is enabled to run by the higher-level DPAY_V1 block. Start and diagnostic
information is read from the CPU_DIAG structure. The event to be evaluated is entered in the
start information (CPU_DIAG) of OB_BEGIN. The block FFD_CIF checks the geographic
address and SLOT_NO of the FF device to determine whether it is responsible for this event.
66

Family: @System
Byte 3 of the additional alarm information contains the slot number of the field device that
triggered the diagnostic interrupt. The corresponding slot is enabled.
The parameter EN_MSG_D = 1 is still set here. This means that the AS asset faceplate for the
FF device accesses this block; messages and maintenance state are generated here.
Use in CFC
function:
The FFD_CIF block is installed downstream from the DPAY_V1 block.
The RACK_NO, DADDR, EN_MSG_D, SUBN1_ID, SUBN2_ID, SLOT_NO and FFDP_ADR
inputs are configured.
The EN input is interconnected with the output of an AND block. These block inputs are
interconnected with the outputs EN_SUBx (x = number of the DP master system) of the
OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET block, with EN_Mx
(x= number of the FF device) of the DPAY_V1 block and EN_F of the OB_DIAGF block.
The CPU_DIAG OUT structure of the OB_BEGIN block and SUB_DIAG of the SUBNET
block are interconnected with the IN_OUT structures of the FFD_CIF block.
RAC_DIAG is interconnected with the OUT structure RAC_DIAG of OB_DIAGF block.
DINFO is interconnected with the OUT structure DINFO of the OB_DIAGF block.
The OUT structure FF_DIAG of OB_DIAGF is interconnected with the IN_OUT structure of
the same name of FFD_CIF.
Calling OBs
OB 1
Cyclic program
OB 72
CPU redundancy loss
OB 70
Redundancy loss
OB 82
OB 83
Remove/insert module interrupt (failure/return of a field device)
OB 86
Rack failure
OB 100
Restart

manual.

67
Family: @System
Message response
The DELAY input is used to delay the outputting of error messages for an outgoing, higherpriority error. For example, if the FFD_CIF block recognizes an outgoing error at a DP master
connected to it, it initially assumes that there is a faulty assigned DP slave in the rack it
monitors, and sets the corresponding output SUBNxERR. The error status is not reset until
the DP slave returns (in this case: OB 86, OB 70). The FFD_CIF blocks suppress the potential
slave failure states for DELAY seconds so as not to trigger a surge of messages from DP
slaves which are not yet synchronized when the master returns. An error message is only
output to the OS when the DP slave has not reported its return before this delay time has
expired.
Note: Do not set the value of DELAY too high, otherwise DP slaves that were removed during
the master failure or are defective will be signaled to the OS too late after the DP master returns.
5.10.2
I/Os of FFD_CIF
I/Os of FFD_CIF
The factory setting of the block display in the CFC is identified in the "I/O" column.
Input parameters
68
I/O (parameter)
Meaning
Data type
Default
DADDR
Diagnostic address of the FF link
INT
DELAY
Interrupt delay (s)
INT
15
DINFO
STRUCT
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = enable interrupt
BOOL
EN_MSG_D
1 = Enable message "Device failure"
BOOL
EV_ID
Message number
DWORD
FFDP_ADR
FF slave address
BYTE
16#FF
MS
Maintenance status
DWORD
RACK_NO
Rack number
BYTE
16#FF
SLOT_NO
Slot number
BYTE
16#FF
SUBN1_ID
BYTE
16#FF
SUBN2_ID
BYTE
16#FF
SUBN_TYP
BOOL

Family: @System
Output parameters
I/O (parameter)
Meaning
Data type
Default
MSG_ACK
WORD
MSG_STAT
Error message status
WORD
O_MS
Maintenance status
DWORD
OMODE
Channel 0 mode
DWORD
QMODF
1 = module removed/defective
BOOL
QRACKF
1 = Slave failure/faulty
BOOL
RETURN_CODE
Return value of the function
INT
SUBN1ACT
BOOL
SUBN2ACT
BOOL
SUBN1ERR
1 = Error in the primary DP master system
BOOL
SUBN2ERR
1 = Error in the redundant DP master system
BOOL
V1_MODE
1 = DPV1 mode of the DP master system
BOOL
I/O (parameter)
Meaning
Data type
Default
ACC_ID
BOOL
CPU_DIAG
STRUCT
FF_DIAG
Diagnostics of the FF device
STRUCT
RAC_DIAG
System structure RACK diagnostics
STRUCT
SUB_DIAG
System structure: SUBNET diagnostics
STRUCT
In/out parameters
5.10.3
Message texts and associated values of FFD_CIF
Message texts and associated values of FFD_CIF

Message block
Message no.
Message class
EV_ID1
(ALARM_8P)
Device @1%d@/ @2%d@/@3%d@: bad,

maintenance alarm
Device @1%d@/ @2%d@/@3%d@:

uncertain, maintenance request
Device @1%d@/ @2%d@/@3%d@: Multiple

alarm (OB 83)

alarm (OB 82)
Device @1%d@/ @2%d@/@3%d@: good,

maintenance required

69
Family: @System
5.11 FFDP_L1: Monitoring FF slaves with maximum 32 values
Message block
Message no.
Message class
No message
Device @1%d@/ @2%d@/@3%d@:

Configuration error: Name does not match
address
Device @1%d@/ @2%d@/@3%d@: Failure
Assignment of Associated Values

Associated value
Block parameters
DP master system ID (SUBN_ID)
FF slave address (FFDP_ADR)
5.11
FFDP_L1: Monitoring FF slaves with maximum 32 values
5.11.1
Description of FFDP_L1

FB 139
I/Os of FFDP_L1 (Page 72)

The FFDP_L1 block monitors the higher-level errors of a field device, such as failure/return
and runs acyclically.
The FFDP_L1 block is enabled to run by the higher-level DPAY_V1 block. The event to be
evaluated is entered in the start information (CPU_DIAG) of OB_BEGIN. The FFDP_L1 block
checks the geographic address and SLOT_NO of the FF device to determine whether it is
responsible for this event.
If a higher-level error goes away the diagnostics is read per SFC 13 from FF link (the data are
all located locally on the link and do not have to be retrieved by the FF device) and reported
accordingly.
The FFDP_L1 block monitors
FF devices downstream from an FF link (DPV1 slave)
It generates the MODE (FF_MODE) and the value status for the signal processing blocks. The
subordinate blocks FF_MOD32 are always enabled for processing and run cyclically. The
70

Family: @System
information is relayed via the structure FF_DIAG to the FF_MOD32. This structure outputs the
message.
Calling OBs
OB 1
Cyclic program
OB 72
CPU redundancy loss
OB 70
Redundancy loss
OB 82
OB 83
OB 85
OB 86
Rack failure
OB 100
Restart
Use in CFC
function:
The FFDP_L1 block is installed downstream from the DPAY_V1 block.
block are interconnected with the IN_OUT structures of the same name of block FFDP_L1.
RAC_DIAG is interconnected with the OUT structure RAC_DIAG of OB_DIAGF block.
The following will be configured:
Diagnostic address of the FF link DADDR
Geographical address (SUBN1_ID, SUBN2_ID, RACK_NO) of the FF device
SLOT_NO
FF address of the FF device (FFDP_ADR)
MODE_xy (mode of the FF device)
NUM_IODATA
The EN input is interconnected with the output of an AND block. These block inputs are
interconnected with the outputs EN_SUBx (x = number of the DP master system) of the
OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET block, with EN_Mx
(x= number of the FF device) of the DPAY_V1 block and EN_F of the OB_DIAGF block.
The QPERAF output is interconnected with the PERAF input of the FF_MOD32.
The QMODF output is interconnected with the MODF input of the FF_MOD32.
The FF_DIAG output is interconnected with the FF_DIAG input of the FF_MOD32.
DINFO is interconnected with the OUT structure DINFO of the OB_DIAGF block.

71
Family: @System
Message response
The DELAY input is used to delay the outputting of error messages for an outgoing, higherpriority error. For example, if the FFDP_L1 block recognizes an outgoing error at a DP master
connected with it, it initially assumes that there is a faulty assigned DP slave in the rack it
the DP slave returns (in this case: OB 86, OB 70). The FFDP_L1 blocks suppress the potential
slave failure states for DELAY seconds so as not to trigger a surge of messages from DP
slaves which are not yet synchronized when the master returns. An error message is only
output to the OS when the DP slave has not reported its return before this delay time has
expired.
5.11.2
I/Os of FFDP_L1
I/Os of FFDP_L1
Input parameters
72
I/O (parameter)
Meaning
Data type
Default
DADDR
INT
DELAY
Interrupt delay (s)
INT
15
DIAG_BUF

personnel)
BOOL
FFDP_ADR
Address of the FF device
BYTE
MODE
Device status
WORD
NUM_IODATA
Number of I/O data in the FF device
INT
RACK_NO
Number of the rack
BYTE
SLOT_NO
Number of the slot
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
16#FF
SUBN2_ID
BYTE
16#FF

Family: @System
5.12 FF_MOD32: Diagnostics of an FF slave (downstream from FF link DPV1)
Output parameters
I/O (parameter)
Meaning
Data type
Default
EN_D_Q
1 = Processing of the quality code
BOOL
FF_DIAG
FF device diagnostics
DWORD
OMODE
Operating mode slot
DWORD
QERR
1 = Error runtime
BOOL
QMODF
1 = Error/defect field device
BOOL
QPERAF
1 = Access error I/O
BOOL
QRACKF
BOOL
RAC_DIAG
System structure RACK diagnostics
STRUCT
RETURN_CODE_O
Return value
INT
SUBN1ACT
BOOL
SUBN2ACT
BOOL
SUBN1ERR
BOOL
SUBN2ERR
BOOL
V1_MODE
DPV1 mode of the DP master system
BOOL
In/out parameters
I/O (parameter)
Meaning
Data type
Default
ACC_MODE
BOOL
CPU_DIAG
CPU diagnostics
STRUCT
DINFO
STRUCT
FF_DIAG_I
STRUCT
SUB_DIAG
STRUCT
5.12
FF_MOD32: Diagnostics of an FF slave (downstream from FF link DPV1)
5.12.1
Description of FF_MOD32

FB 124
I/Os of FF_MOD32 (Page 75)

The block reports the maintenance status of an FF field device downstream from an FF link.
For diagnostics in the Maintenance Station, all error sources will be linked with OR and the

73
Family: @System
worst will be assigned to the MS output. The channel blocks (FbAnIn, FbAnOu, FbDiIn,
FbDiOu) will be controlled by quality codes.
The block analyses cyclically all events that affect an FF device and reports the following
events:
Evaluation of the RAC_DIAG info (from FFDP_L1): Device failure
Evaluation of the FF_DIAG info (from FFDP_L1): Diagnostics
Use in CFC
function:
The block is integrated in the run sequence upstream of the FbAxXx, FbDxXx block.
The SUBN1_ID, SUBN2_ID, RACK_NO, SLOT_NO, FFDP_ADR and NUM_IODATA inputs
are configured.
The block inputs are interconnected with the following outputs:
FF_DIAG with FF_DIAG output of the FFDP_L1 block
MODE_xy with OMODE_xy outputs of the FFDP_L1 block
MODF, PERAF with QMODF and QPERAF outputs of the FFDP_L1 block
RAC_DIAG with output structure RAC_DIAG of the OB_DIAGF block
QC_x input with icon of the FF field device
EN_D_Q with EN_DQ output of the FFDP_L1 block
The output parameter of DXCHG_xx is interconnected with the following channel block at
the DataXchg parameter.
The output parameter of O_MS is interconnected with the following channel block at the
MS parameter.
The output parameter of OMODE_xy is interconnected with the following channel block at
the OMODE_xy parameter.
structures of the same name of the FFDP_L1 block.
Calling OBs
OB no.
Start Event
OB 1
Cyclic program
OB 100
Warm restart
Message
The Alarm_8P is initialized at
startup (OB 100)

74

Family: @System
manual.
5.12.2
I/Os of FF_MOD32
I/Os of FF_MOD32
Input parameters
I/O (parameter)
Meaning
Data type
Default
EN_D_Q
1 = Processing of the quality code
BOOL
EN_MSG
1 = enable interrupt
BOOL
EV_ID1
Message number 1
DWORD
EV_ID2
Message number 2
DWORD
FFDP_ADR
Address of the FF device
BYTE
FF_DIAG
DWORD
MODE_xx
Device mode (xx = IOData 0 - 31)
DWORD
MODF
1 = field device error/fault
BOOL
MS
Maintenance status
DWORD
MS_REQ
1 = Request maintenance release
BOOL
NUM_IODATA
Number of I/O data in the FF device
INT
PERAF
1 = I/O access error
BOOL
QC_xx
Status of FF field device (x = channel 0 to 31)
BYTE
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBN1_ID
BYTE
16#FF
SUBN2_ID
BYTE
16#FF
Output parameter
I/O (parameter)
Meaning
Data type
B_QC
Quality code, bit-granular
STRUCT
DXCHG_xx
Bidirectional data exchange channel
DWORD
DWORD
DWORD
DXCHG1_xx
Default
(xx = 00 - 31)
DXCHG1

75
Family: @System
I/O (parameter)
Meaning
Data type
Default
EXT_STAT
Release for maintenance - extended status
DWORD
EXT_STAT_A
Extended Status Application
DWORD
Bit 0=1: ConditionMonitoring On

IODATA_ACTIVE
Channel active
DWORD
16#00000000
IODATA_EXIST
I/O data available
DWORD
IODATA_OK
I/O data OK
DWORD
MS_XCHG_00
Maintenance Status - Data exchange channel
DWORD
MS_XCHG_xx
DWORD
(xx = 00 - 31)
MSGSTAT1
Message error - information 1
WORD
MSGSTAT2
Message error - information 2
WORD
MSG_ACK1
Message acknowledgment 1
WORD
OMODE_xx
Value status FF field device (xx = IOData 0 to 31)
DWORD
O_MS
Maintenance status
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QPERAF
BOOL
QRACKF
BOOL
I/O (parameter)
Meaning
Data type
CPU_DIAG
CPU diagnostics
STRUCT
RAC_DIAG
STRUCT
In/out parameters
5.12.3
Default
Message texts and associated values of FF_MOD32
Message texts and associated values of FF_MOD32

76
Message block
Message no.
Message class
EV_ID1
(ALARM_8P)
Device @1%d@/ @2%d@/@3%d@: Bad,

maintenance alarm
Device @1%d@/ @2%d@/@3%d@:

Uncertain, maintenance demanded
Device @1%d@/ @2%d@/@3%d@: Good,

Device @1%d@/ @2%d@/@3%d@:

Access error

Family: @System
Message block
Message no.
Message class
Device @1%d@/ @2%d@/@3%d@:

Multiple alarm (OB 83)
Device @1%d@/ @2%d@/@3%d@: Failure S
Device @1%d@/ @2%d@/@3%d@:

Configuration error: Name does not match
address
8
EV_ID2
(NOTIFY_8P)
No message

assuming fail-safe position
SA

configuration has been changed
SA
Device @1%d@/ @2%d@/@3%d@:

Simulation
SA
Device @1%d@/ @2%d@/@3%d@:

Uncertain, process-related, no maintenance
SA
Device @1%d@/ @2%d@/@3%d@: Bad,

process-related, no maintenance
SA
Device @1%d@/ @2%d@/@3%d@: Local

operation/functional check
SA
Device @1%d@/ @2%d@/@3%d@: Device

passivated
SA
No message

Associated value
Block parameters
FF slave address (FFDP_ADR)

77
Family: @System
5.13 FM_CNT: Programming and controlling FM 350 modules
5.13
FM_CNT: Programming and controlling FM 350 modules
5.13.1
Description of FM_CNT

FB 126
FM_CNT Block I/Os (Page 81)
Area of application
Block FM_CNT is used to configure and control FM 350-1 and FM 350-2 modules. It writes
the counter levels, limits and comparison values of the FM 350-2 module.
Calling OBs
OB 100 and the cyclic OB (100 ms recommended) used for transmitting data.
Also note the assignments (Page 356) to the FM_CO block.
Use in CFC
function:
The block is installed in the cyclic OB upstream of the CH_CNT blocks.
The block runtime group is installed in OB 100 downstream of MOD_D1.
The LADDR, FM_MODE, RACK_NO, SUBN1_ID, SUBN2_ID, and SLOT_NO inputs are
configured.
The MODEx inputs are interconnected with the OMODEx outputs of the MOD_D1 block.
The FM_DATA output structure is interconnected with the structure of the same name of
the CH_CNT block.
The OMODEx output is interconnected with the MODE input of the CH_CNT block.
The OUT structure CPU_DIAG of OB_BEGIN is interconnected with the IN_OUT structure
of the same name of FM_CNT.
The EN_CO input structure is interconnected with the EN_CO_x output structure of the
FM_CO block (x = number of the rack).
The output ENCO is connected to the input ENCOx_yy of the FM_CO block (x = number
of the rack, yy = coordination number).
Addressing
The logical base address of the module is entered in the LADDR I/O by the CFC driver
generator.
78

Family: @System
Redundancy
Higher-level block MOD_D1 evaluates the redundancy of DP master systems operating in an
H system. Redundancy for two FM 350-1 or FM 350-2 modules is not supported, and must be
controlled by the user outside the block.
MODE Setting
Signal states of the MODE_xx input, or QMODE_xx output of the FM_CNT block are described
under the MODE settings.
MODE_xx input parameters are available for up to 8 signal channels. Their default setting is
"0" (no signal). For each signal channel xx, the operating mode of the FM 350 module must
be set at the MODE_xx input (the CFC driver generator does this for you).
The module recognizes the following modes:
Term
Coding
MODE
Description
Channel not used
16#0000
Channel of the FM 350 not used.
Continuous counting
16#xx01
The FM 350 counts continuously, starting with the

current counter level when the internal gate opens.
One-time counting
16#xx02
The FM 350 counts from the start value to the end value
when the internal gate opens.
Periodic counting
16#xx03
The FM 350 counts between the start value and the end
value when the internal gate opens.
Frequency measurement
16#xx04
The FM 350 determines the frequency pulse sequence

at the input.
Speed measurement
16#xx05
The FM 350 determines the speed of the device

connected to the input.
Period duration
measurement
16#xx06
The FM 350 determines the duration of the pulse

sequence at the input.
Dosing
16#xx07
Four channels of the FM 350-2 are used for dosing.
The count and measured values can be recorded with the FM 350-2 module, either via the
process image (fast update) or via "Read data record" (slower update).
If the count and measured values of a channel in the process image are made available, they
have to be in alignment in the process image. The following variants are possible.
Term
Coding
MODE
Description
Count and measured value are not

in the process image
16#Cxxx
Read count and measured values via data record
Only the count value is in the process 16#8xxx

image
Read measured value via data record and count

value in the process image
Only the measured value is in the

process image
16#4xxx
Read count values via data record and measured

value in the process image
Count and measured value are in the

process image
16#0xxx
Read count and measured value in the process

image
Data type DWORD count and

measured value
16#x0xx
Count value before measured value, both of the

data type DWORD

79
Family: @System
Term
Coding
MODE
Description
Data type WORD count value
16#x1xx
Count value of the the data type WORD before

measured value of the data type DWORD
Data type WORD measured value
16#x2xx
Count value of the data type DWORD before

measured value of the data type WORD
Data type WORD count and

measured value
16#x3xx
Measured value before count value, both of the

data type WORD
Data type DWORD count and

measured value
16#x8xx
Measured value before count value, both of the

data type DWORD
Data type WORD count value
16#x9xx
Measured value of the the data type DWORD

before count value of the data type WORD
Data type WORD measured value
16#xAxx
Measured value of the the data type WORD

before count value of the data type DWORD
Data type WORD count and

measured value
16#xBxx
Count value before measured value, both of the

data type WORD
MODE is formed by the linking the operating mode code, and the access type value.
Example: Count and measured value in "Dosing" mode of the the data type DWORD is not in
the process image MODE = 16#C007.
Error handling
Whenever the system or FM 350-1/FM 350-2 starts up, the block coordinates the restart with
the module. The CMP_VALx parameters are then loaded into the FM 350.
ALARM_8P is initialized.
Overload behavior
Not available
Time response
Not available
Message response
The block reports operating and data errors for the FM 350-1 module, and data errors for FM
350-2 using ALARM_8P. The message function can be disabled by setting EN_MSG = FALSE.
The MOD_D1 block reports diagnostic interrupts from the FM 350-1 or FM 350-2.

80

Family: @System
Message texts and associated values of FM_CNT (Page 82)
5.13.2
I/Os of FM_CNT
Input parameters
I/O
(parameter)
Meaning
Data type
Defau
lt
CO_NO
Coordination number for data record reading
INT
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = enable message
BOOL
EV_ID
Message number
DWORD
FM_MODE
0 = FM 350-1, >0 = FM 350-2
BYTE
LADDR
Logical address FM 350
INT
MODEx
Mode channel (x = 0 to 7)
DWORD
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
I/O
(parameter)
Meaning
Data type
Defau
lt
FM_DATA
Structure FM 350 data
STRUCT
MSG_ACK
WORD
MSG_STAT
WORD
OMODEx
Mode channel (x = 0 to 7)
DWORD
QDATA_ERR
1 = Data error
BOOL
QDONE
1 = Write new data
BOOL
QDONE_RD
1 = New data read
BOOL
QMODF
1 = Error FM 350
BOOL
QPARF
1 = Module not programmed
BOOL
Output parameters

81
Family: @System
I/O
(parameter)
Meaning
Data type
Defau
lt
QRD_ERR
1 = Error when reading data
BOOL
QWR_ERR
1 = Error read data
BOOL
STATUS_RD
Read status of data record
DWORD
STATUS_WR
Write status of data record
DWORD
I/O
(parameter)
Meaning
Data type
Defau
lt
ACC_MODE
BOOL
EN_CO
Current coordination number
STRUCT
ENCO
Coordination number
BYTE
CPU_DIAG
STRUCT
In/out parameters
Additional information is available in the section:
Message texts and associated values of FM_CNT (Page 82)
5.13.3
Message texts and associated values of FM_CNT
82
Message block
ALARM_8P
Message no.
Message class
EV_ID
FM 350 @1%d@/@2%d@/@3%d
@data error number@4%d@
FM 350 @1%d@/@2%d@/@3%d
@data error number @5%d@
No message
No message
No message
No message
No message
No message

Family: @System
5.14 IMDRV_TS: Transferring time-stamped process-signal changes

Message block
ALARM_8P
Associat
ed
value
Block parameters
Meaning
EV_ID
SUBN_ID
RACK_NO
SLOT_NO
Slot number (byte)
DA_ERR_W
Data error number
OT_ERR_B
Operator error number
See also
5.14
IMDRV_TS: Transferring time-stamped process-signal changes
5.14.1
Description of IMDRV_TS

FB 129
IMDRV_TS block I/Os (Page 87)
Area of application
The IMDRV_TS block transfers time-stamped process signal changes to the MSG_TS blocks,
and messages from the interface module (IM) to the OS.
Calling OBs
OB 1
Cyclic program
OB 40
Hardware interrupt
OB 100
Warm restart

83
Family: @System
Use in CFC
function:
The IMDRV_TS block is copied from the library and instantiated in a system chart. The
block is installed in its runtime group after the RACK block runtime group in the abovementioned OBs.
OR_32_TS is always interconnected between MSG_TS and IMDRV_TS.
The logical address LADDR is configured with the logical address of the IM (diagnostics
address). If you operate the DP master system in DPV1 mode, the input address of the IM
is entered.
The RAC_DIAG structure of the RACK block is interconnected with the structure of the
same name of the IMDRV_TS block.
The S_CH_xxx and TINF_xxx inputs of the TRIG_INF structure are set.
Every signal that is time-stamped by the IM has a unique assignment identified by the slot
of the module combined with the corresponding channel number. There are 128 inputs of
the WORD data type for 128 signals. The slot number of the relevant digital input module
is entered in the more significant byte and the channel number (signal of the digital input
module) is entered into the less significant byte. The slot and channel number of the process
signals are entered in the block inputs S_CH_xxx.
Example:
In HW Config, you have activated time-stamping for the digital signal of channel 10 of a
digital input module that is inserted in slot 5 of an ET 200M. The number 16#050A is entered
at the first available input S_CH_xxx of the IM_DRV_TS.
The information about the edge evaluation for the event entering state is stored in the
TINF_xxx parameters of the TRIG_INF structure.
0 means: 0 -> 1 is event entering state
1 means: 1 -> 0 is event entering state.
Description of the functions

The IMDRV_TS block reads the messages from the message buffers (up to 15 data records,
each with 20 messages) of an IM, and transfers them to a message block for time stamps
(MSG_TS). The MSG_TS sends the messages via an ALARM_8P block whose time stamps
for its 8 messages are entered in the 1st associated value in an ARRAY of BYTE.
84

Family: @System
How it works
Hardware interrupt (OB 40): The IM generates a hardware interrupt if there are new
messages. The time-stamp status, including the number of the IM data record to be fetched
and the number of messages in the data record, are fetched from the start information of
the process interrupt OB and stored for cyclic processing. The interrupt stack can hold up
to 17 process interrupts. If this maximum is exceeded, all new information will be lost. The
loss of information is indicated by the "Loss of message at IM (buffer overflow)" message.
Cyclic processing: If any messages are queued in the stack, SFB 52 (RDREC, read data
record) reads the relevant data record (message buffer). If there are several data records
to be fetched, it will fetch the record that contains the oldest messages (oldest hardware
interrupt). The block instance temporarily stores a maximum of 20 messages of a data
record.
The IM can enter new messages in a data record once it has been read. If all data records
are in use, the IM enters "Loss of message at IM (buffer overflow)" (incoming) as the last
message in the message buffer. "Loss of message at IM (buffer overflow)" (outgoing) is
then entered as the first message in the first free data record. Messages received within
the interval between a buffer overflow and the enabling of a record will be lost.
The slot number/channel number of the stored messages are compared with the input
parameters of the block for slot number/channel number (S_CH_xxx). If they match, the
message is written to the corresponding output (TS_xxx).
Errors occurring during data exchange between the block and IM are reported by the
ALARM_8P block (for example, an I/O access error).
Quality code for the time stamp TS_xxx.TS0/TS1

A quality code QC_TS is formed for the time stamp TS0/TS1, and entered in TS_xxx.
State
Quality code
TS_xxx.QC_TS
Valid value
16#80
Invalid value (higher level error)
16#40
Time-of-day frame failure

Stop the time stamp function
Message loss on IM (buffer overflow)
Loss of information with redundancy
Invalid value
16##00
Addressing
For general information, see also Addressing (Page 353)
The logical address of the IM obtained in HW Config (corresponds to the diagnostic address,
or the input address of the IM for a DP master system in DPV1 mode) is entered at the driver's
block input (LADDR) by the "Generate module driver" CFC function. Any change to the LADDR
block input will initiate a single check of the logical address according to the startup
characteristics of the block.
Process signals that require a time stamp and are detected via an IM must be configured
accordingly in HW Config.

85
Family: @System
Error handling
I/O access error:
QPERAF
The block could not access the IM. A data record could not be read.
Block processing error:

QERR
A block execution error has occurred.
Module parameter assignment error:

QPARF
Faulty block configuration: Incorrect logical basic address entered.
Parameter assignment error:

QBPARF
Faulty block configuration: The slot/channel number of an IM message does not match any
slot/channel number of the block input parameters.
Rack error:
QRACKF Failure of the rack containing the IM or IM failure.
IM Startup Characteristics
During startup/restart of the IM, the system will generate process interrupts once again for
those records which were occupied prior to restart but had not been fetched.
The message "Startup data (incoming)" is entered as the first message of the first free data
record. After restart, the system checks all monitored digital signals for changes, outputs a
message if appropriate. It finally generates the message "Startup data (outgoing)".
IMDRV_TS driver block startup characteristics

Initializes the ALARM_8P blocks using the data stored prior to the CPU transition to STOP.
During an initial startup, the signal state is set to "Zero".
During startup, the block verifies the existence of an IM at its logical address set in LADDR. If
this does not exist, it sets the QPARF output to TRUE, and does not access any I/Os in its
subsequent cycles. QPARF = FALSE and I/O access is enabled only after the correct module
has been inserted, or the logical address has been set correctly. Stored process interrupt data
which were not computed before the restart will be deleted.
Redundancy
Time stamping in H systems equipped with two IM units is redundant under the following
conditions:
Both IM units communicate via the communication (K) bus.
No error has occurred during the update of the active and passive IM.
86

Family: @System
The SUBNET and RACK blocks report loss of redundancy (failure of an IM), separately from
the IMDRV_TS block.
Time stamping is interrupted for the duration of the changeover between the active and passive
IM. This period of interruption is indicated by the message "Redundant changeover" (incoming/
outgoing state).
The active IM usually reports the current I/O status to the redundant IM. If this communication
is disrupted, the message "Loss of information with redundancy" (entering state) is output.
When the I/O statuses of the active and redundant IM are synchronized, the message "Loss
of information with redundancy" (outgoing) is output.
Time response
Not available
Message response
The block signals system messages from the IM via the ALARM_8P block. The time-stamped
hardware interrupts are forwarded to the MSG_TS IM message block via OR_32_TS.
Operator control and monitoring:

The block does not have a faceplate.
You will find more information in:
Message texts of IMDRV_TS (Page 89)
5.14.2
I/Os of IMDRV_TS
Input parameters
I/O
(parameter)
Meaning
Data type
Default
DIAG_BUF
Entry in diagnostic buffer (relevant for maintenance personnel)
BOOL
EV_ID
Message number for ALARM_8P
DWORD
EV_ID_00
Message number 0 for ALARM_8P
DWORD
LADDR
Logic address IM
INT

87
Family: @System
I/O
(parameter)
Meaning
Data type
Default
S_CH_xxx
Slot/channel number (xxx = 000 - 127)
WORD
TRIG_INF
Edge evaluation:
STRUCT
0 = trigger 0 -> 1, 1 = trigger 1 -> 0
Output parameters
I/O
(parameter)
Meaning
Data type
Default
M_ACK_00
WORD
Q_ERR_00
Message error
BOOL
QERR
1 = processing error block
BOOL
QPARF
1 = parameter assignment error module
BOOL
QBPARF
1 = parameter assignment error block
BOOL
QPERAF
BOOL
QRACKF
1 = rack error
BOOL
QTS_NCON
1 = TS_xxx is not interconnected
BOOL
STAT_00
Status output
WORD
TS_xxx
Time stamp (xxx = 000 127)
STRUCT
Bit 0: Message signal state (MsgSig)

Bit 1: Edge change information (TriInf)
Bit 2: Handshake (HdSh)
Byte 1:
Quality code of the time stamp (ST)
DWORD TS0:
Date/time stamp in ISP format (seconds)
DWORD TS1:
Date/time stamp in ISP format (fractions of seconds)
TS_C_xxx
TS communication (xxx = 000 - 127)
BYTE
Default
Bit 0: Acknowledgment of transfer (HS)

Bit 1: Interconnection check (LI)
In/out parameters
I/O
(parameter)
Meaning
Data type
RAC_DIAG
Rack status information
STRUCT
Message texts of IMDRV_TS (Page 89)
88

Family: @System
5.14.3
Message texts of IMDRV_TS

You will find more information in Message classes (Page 355)
Message block
Message no.
Message class
IM @1%d@@2%d@: Parameter assignment error

Slot=@3%d@ Channel=@4%d@
EV_ID
(ALARM_8P)
IM @1%d@@2%d@: I/O access error: Ret_Val@5%d@
IM @1%d@@2%d@: Parameter assignment error LADDR
IM @1%d@@2%d@: Output TS_xxx of S_CHxx:

Slot=@3%d@ Channel=@4%d@ is not interconnected
Reserve5
No message
Reserve6
No message
Reserve7
No message
Reserve8
No message
IM @3%d@@4%d@: Startup data
IM @3%d@@4%d@: Time-of-day frame failure
EV_ID_00
(ALARM_8P)
S
No message
IM @3%d@@4%d@: Time difference between the frame and the

internal clock may cause inaccuracy
IM @3%d@@4%d@: Stop the time stamp function
IM @3%d@@4%d@: Message loss on IM (buffer overflow)
IM @3%d@@4%d@: Redundant changeover
IM @3%d@@4%d@: Loss of information with redundancy
Note
The message "IM @1%d@@2%d@: Output TS_xxx of S_CHxx: Slot=@3%d@
Channel=@4%d@ is not interconnected" is generated when the time stamp of a signal could
not be forwarded. The reason for this could be configured but not interconnected time stamp
signals (e.g. missing channel block PCS7DiIT and missing message block EventTs).

89
Family: @System
5.15 MOD_1: Monitoring up to 16 channels on S7-300/400 SM modules without diagnostic capability
5.15
MOD_1: Monitoring up to 16 channels on S7-300/400 SM modules

without diagnostic capability
5.15.1
Description of MOD_1

FB 91
I/Os of MOD_1/MOD_2 (Page 93)
Area of application
The MOD_1 block monitors up to 16 channels on S7-300/400 SM modules without diagnostic
capability (no mixed modules). H systems support only the modules installed in switched racks.
The block can also be used to monitor the FM 350 counter module.
Calling OBs
OB 1
Cyclic program
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:
The MOD_1 block is installed in its runtime group downstream of the RACK block runtime
group in the above-mentioned OBs.
The MODE_xx inputs (mode of module channels xx) are configured.
The logical base address of the LADDR module is configured.
The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK block
are interconnected with the IN_OUT structures of the same name of MOD_1.
Its inputs are interconnected with the outputs EN_SUBx (x = number of the DP master
system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET
block and EN_Mxx (xx = module number) of the RACK block.
90

Family: @System
MS parameter.
Function
The MOD_1 block analyzes all events that affect a module and its channels acyclically. It
generates a channel-specific MODE (Page 341) and value status for the signal processing
blocks. ALARM_8P reports the events.
The block is enabled by the higher-level RACK block at runtime. The event to be evaluated
can be found in the CPU_DIAG start information of the OB_DIAG block. There is a MODE_xx
input for each signal channel of the module. The module channel configuration data created
in HW Config is reported here. The function writes MODE_xx to the low word of the
OMODE_xx (Page 351) output parameter. This occurs only during startup or if you set
ACC_MODE = TRUE. The current channel value status is written to the most significant byte.
If the result is positive, the system sets OMODE_xx = 16#80xxxxxx.
The following events lead to the value status "invalid value due to higher-level error"
(OMODE_xx = 16#40xxxxxx):
Events that are evaluated by the RACK block:
Rack failure (OB 86) (output parameter QRACKF = TRUE)
Events that are evaluated by the MOD block:
Program execution error (OB 85) (output parameter QPERAF = TRUE)
Module removed (OB 83) (output parameter QMODF = TRUE)
"Module removed" and "I/O access error" events are reported to the OS by ALARM_8P. The
diagnostics interrupt function distinguishes between module and channel errors, whereby each
channel is assigned a message ID.
The system verifies during startup that the module is available (plugged in). The module status
information that is read here is then available in the form of service output parameters
(MOD_INF).
You will find additional information about faults in the System Software for S7-300/400 System
and Standard Functions reference manual.
Redundancy
The higher-level RACK block monitors the redundancy of DP master systems operating in an
H system.

91
Family: @System
MODE setting
You will find additional information about this in the "MODE settings (Page 341)" section.
Note
If you make changes to the MODE_xx input configurations at runtime, they are not accepted
at the outputs until you set the ACC_MODE input to 1.
OMODE Structure
You will find additional information in the "OMODE (Page 351)" section.
Valid channel display

The available channels on a module are displayed in the CH_EXIST output by setting a bit in
the DWORD, starting at bit 0, for every existing channel. If the bit assigned to a channel = 0,
the channel is not available.
Output CH_OK displays the valid channels on a module by setting a bit to TRUE for every valid
channel, where bit 0 is assigned to channel 0, etc. If the bit assigned to a channel is 0, the
channel is faulty. If a module error occurs, all channels are disrupted.
Addressing
You will find additional information about this in the "Addressing (Page 353)" section.
Error handling
You will find additional information about error handling in the "Error information of output
parameter MSG_STAT (Page 353)" section.
Service Information
To analyze faults, the module status information entered during startup is read via the
MOD_INF structured output parameter. You will find additional information in the System
Software for S7-300/400 System and Standard Functions; System Status List, Module Status
Information reference manual.
After a restart/initial startup, the system verifies that the module is available under its logical
base address. A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx
(Page 351) outputs.
92

Family: @System
Time response
Not available
Message response
MOD_1 uses ALARM_8P to report module errors. The inputs DELAY1 and DELAY2 are used
to delay the output of I/O access error messages. DELAY1 allows you to enter a time in
seconds for which the block will wait for a higher-priority error (rack failure or removal/insertion)
following a program execution error (OB 85) before it outputs the message. The message is
output only under the condition that no higher-priority error is reported within this delay time.
DELAY2 determines the number of seconds the block waits after the higher-priority error has
been reported outgoing until it outputs the queued I/O access error as well. Both values are
set to 2 seconds by default.
The message function can be disabled by setting EN_MSG = FALSE.

manual.
Message texts and associated values of MOD_1 (Page 95)
You will find additional information on this in PCS 7 Advanced Process Library > Basics of APL
> General functions of the blocks > Operating, monitoring and reporting > Release for
maintenance
5.15.2
I/Os of MOD_1/MOD_2
The MOD_1 and MOD_2 block I/Os are identical with the exception of the number of MODE_xx
and OMODE_xx. The number of monitored channels determines the corresponding number
of I/O parameters (xx).

93
Family: @System
Input parameters
I/O
(parameter)
Meaning
Data type
Default
CHAN_NUM
Highest channel address
INT
DELAY1
Alarm delay 1 (s)
INT
DELAY2
Alarm delay 2 (s)
INT
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = Enable message
BOOL
EV_ID
Message number
DWORD
LADDR
Logical address of the module
INT
MODE_xx
Channel mode (xx = 00 - 15/00 - 31)
DWORD
MS
Maintenance status
DWORD
MS_REQ
BOOL
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Output parameters
I/O
(parameter)
Meaning
Data type Default
CH_ACTIVE
Channel active
DWORD
16#00000000
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
DXCHG_xx
Bidirectional data exchange channel (xx = 00 15)
DWORD
DWORD
Bit = 0: Release for maintenance

Bit 1 byte 0: Flutter suppression
Bit 2 to bit 7 byte 0: Reserved
Byte 1: Reserved
Byte 2: Reserved
Byte 3: Fluttering time
DXCHG1_XX
EXT_STAT
DWORD
EXT_STAT_A
DWORD

MOD_INF
System structure: Module parameter
STRUCT
MS_XCHG_xx
DWORD
(xx = 00 - 63)
94

Family: @System
I/O
(parameter)
Meaning
Data type Default
MSG_ACK
WORD
MSG_STAT
WORD
O_MS
Maintenance status
DWORD
OMODE_xx
Channel mode (xx = 00 - 15/00 - 31)
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QPERAF
BOOL
QRACKF
1 = rack/station error
BOOL
In/out parameters
I/O
(parameter)
Meaning
Data type Default
ACC_MODE
BOOL
CPU_DIAG
STRUCT
RAC_DIAG
System structure: Rack diagnostics
STRUCT
Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64 (Page 95)
5.15.3
Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64
Assignment of message text and message class to the block parameters of MOD_1/MOD_2/MOD_3/
MOD_64
Message
block
ALARM_8P
Message
number
EV_ID
Block
parameter
Messag
e
class
Module @1%d@/@2%d@/@3%d@:
Removed
QPERAF
Module @1%d@/@2%d@/@3%d@: Access

error
QMODF
Module @1%d@/@2%d@/@3%d@: @4W

%t#MOD_n_TXT@ (n = 1, 2, 3 or 64)
QMODF
Module @1%d@/@2%d@/@3%d@: @4W

%t#MOD_n_TXT@ (n = 1, 2, 3 or 64)

95
Family: @System
5.16 MOD_2: Monitoring 32 channels on S7-300/400 SM modules without diagnostic capability
Assignment of associated values to the block parameters of MOD_1/MOD_2/MOD_3

Message block
ALARM_8P
Associate Block parameters

d
value
Meaning
EV_ID
MOD_INF.SUBN_ID
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
Slot number (byte)

Text number from MOD_n_TXT
(n = 1, 2, 3 or 64) (Message 1)
You will find the message texts and their text numbers in the "Text library for MOD_1, MOD_2,
MOD_3, MOD_64 (Page 361)" section.
See also
5.16
MOD_2: Monitoring 32 channels on S7-300/400 SM modules without

diagnostic capability
5.16.1

FB 92
MOD_2 block I/Os (Page 100)
Area of application
The MOD_2 block monitors 32 channels on S7-300/400 SM modules without diagnostic
Calling OBs
96
OB 1
Cyclic program
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart

Family: @System
Use in CFC
function:
MS parameter.
Function
Block MOD_2 analyzes all events affecting a module and its channels in non-cyclic mode. It
The block is enabled to run by the higher-level RACK block. The event to be evaluated can
be found in the CPU_DIAG start information of the OB_DIAG block. There is a MODE_xx input
for each signal channel of the module. The module channel configuration data created in HW
Config is reported here. The function writes MODE_xx to the low word of the OMODE_xx
(Page 351) output parameter. This occurs only during startup or if you set ACC_MODE =
TRUE. The current channel value status is written to the most significant byte. If the result is
positive, the system sets OMODE_xx = 16#80xxxxxx.

97
Family: @System
(MOD_INF).
You will find additional information about errors in the System Software for S7-300/400; System
Redundancy
H system.
MODE setting
Note
If you change the parameter settings for the MODE_xx inputs at runtime, these changes will
not be accepted at the outputs until the ACC_MODE is set to 1.
OMODE Structure

Addressing
Error handling
98

Family: @System
Service Information
MOD_INF structured output parameter. You will find additional information about this in the
reference manual System Software for S7-300/400 System and Standard Functions; System
Status List, Module Status Information.
(Page 351) outputs.
Time response
Not available
Message response

manual.
maintenance

99
Family: @System
5.16.2
I/Os of MOD_1/MOD_2
The MOD_1 and MOD_2 block I/Os are identical with the exception of the number of MODE_xx
and OMODE_xx. The number of monitored channels determines the corresponding number
of I/O parameters (xx).
Input parameters
I/O
(parameter)
Meaning
Data type
Default
CHAN_NUM
INT
DELAY1
Alarm delay 1 (s)
INT
DELAY2
Alarm delay 2 (s)
INT
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = Enable message
BOOL
EV_ID
Message number
DWORD
LADDR
INT
MODE_xx
Channel mode (xx = 00 - 15/00 - 31)
DWORD
MS
Maintenance status
DWORD
MS_REQ
BOOL
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Output parameters
100
I/O
(parameter)
Meaning
Data type Default
CH_ACTIVE
Channel active
DWORD
16#00000000
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD

Family: @System
I/O
(parameter)
Meaning
Data type Default
DXCHG_xx
DWORD
DWORD

Byte 1: Reserved
Byte 2: Reserved
DXCHG1_XX
EXT_STAT
DWORD
EXT_STAT_A
DWORD

MOD_INF
STRUCT
MS_XCHG_xx
DWORD
(xx = 00 - 63)
MSG_ACK
WORD
MSG_STAT
WORD
O_MS
Maintenance status
DWORD
OMODE_xx
Channel mode (xx = 00 - 15/00 - 31)
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QPERAF
BOOL
QRACKF
BOOL
In/out parameters
I/O
(parameter)
Meaning
Data type Default
ACC_MODE
BOOL
CPU_DIAG
STRUCT
RAC_DIAG
STRUCT

101
Family: @System
5.16.3
MOD_64
Message
block
ALARM_8P
Message
number
EV_ID
Block
parameter
Messag
e
class
Module @1%d@/@2%d@/@3%d@:
Removed
QPERAF

error
QMODF
Module @1%d@/@2%d@/@3%d@: @4W

%t#MOD_n_TXT@ (n = 1, 2, 3 or 64)
QMODF
Module @1%d@/@2%d@/@3%d@: @4W

%t#MOD_n_TXT@ (n = 1, 2, 3 or 64)

Message block
ALARM_8P

d
value
Meaning
EV_ID
MOD_INF.SUBN_ID
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
Slot number (byte)

(n = 1, 2, 3 or 64) (Message 1)
See also
102

Family: @System
5.17 MOD_3: Monitoring up to 16 channels on S7-200/300/400 SM modules without diagnostic capability
5.17
MOD_3: Monitoring up to 16 channels on S7-200/300/400 SM modules

without diagnostic capability
5.17.1

FB 95
Area of application
The MOD_3 block monitors up to 16 channels on S7-300/400 SM mixed modules without
diagnostic capability (I/O modules). H systems support only the modules installed in switched
racks.
Supported are the ET 200M-HART modules:
6ES7331-7TB10-0AB0 -> AI2 HART
6ES7332-5TB10-0AB0 ->AO2 HART.
Calling OBs
OB 1
Cyclic program
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:
The MODE_xx inputs are configured.
The logical addresses LADDR and LADDR1 are configured.
The structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK block are
interconnected with the MOD_3 structures of the same name.

103
Family: @System
MS parameter.
Function
The MOD_3 block cyclically analyzes all events that affect a module. It generates a channelspecific MODE (Page 341) and value status for the signal processing blocks. ALARM_8P
reports the events. The message function can be disabled.
The block is enabled to run by the higher-level RACK block. The diagnostic event is entered
in the CPU_DIAG start information of the OB_BEGIN block.
There is a MODE_xx input for each signal channel of the module. The module channel
configuration data created in HW Config is reported here. MODE_00 to MODE_15 inputs are
available for encoding up to 16 input channels, and MODE_16 MODE_31 for encoding up
to 16 output channels.
The function writes MODE_xx to the low word of the OMODE_xx (Page 351) output parameter.
This occurs only during startup or if you set ACC_MODE = TRUE. The current channel value
status is written to the most significant byte. If the result is positive, the system sets OMODE_xx
= 16#80xxxxxx.
Program execution error (OB 85) (output parameter QRACKF = TRUE)
I/O access error (OB 85) (output parameter QPERAF = TRUE)
information read here makes this data available in the form of service output parameters
(MOD_INF).
You can find additional information about faults in the System Software for S7-300/400 System
Redundancy
Block MOD_3 supports segment redundancy of H systems operating with distributed I/Os. If
you want to use this function, you must configure the SUBN1_ID (connection to CPU 0) and
SUBN2_ID (connection to CPU 1) inputs of the SUBNET block with the numbers of the
redundant segments. If there is no segment redundancy, the remaining input must be set to
the (default) value 16#FF.
104

Family: @System
MODE setting
You can find additional information about this in the "MODE settings (Page 341)" section.
Note
OMODE Structure
You can find additional information in the "OMODE (Page 351)" section.

Addressing
You can find additional information about this in the "Addressing (Page 353)" section.
Error handling
You can find additional information about error handling in the "Error information of output
Service Information
MOD_INF structured output parameter. You can find additional information about this in the
(Page 351) outputs.

105
Family: @System
Time response
Not available
Message response
Block MOD_3 uses ALARM_8P to report module errors. The inputs DELAY1 and DELAY2 are
used to delay the output of I/O access error messages. DELAY1 allows you to enter a time in
following a program execution error (OB 85) before it outputs the message. DELAY2
determines the number of seconds the block waits after the higher-priority error has been
reported outgoing until it outputs the queued I/O access error as well. Both values are set to
2 seconds by default. The message function can be disabled by setting EN_MSG = FALSE.

manual.
You can find additional information on this in PCS 7 Advanced Process Library > Basics of
APL > General functions of the blocks > Operating, monitoring and reporting > Release for
maintenance
5.17.2
I/Os of MOD_3
Input parameters
106
I/O
(parameter)
Meaning
Data type
Defau
lt
CHAN_NUM
INT
DELAY1
Alarm delay 1 (s)
INT
DELAY2
Alarm delay 2 (s)
INT

Family: @System
I/O
(parameter)
Meaning
Data type
Defau
lt
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = Enable message
BOOL
EV_ID
Message number
DWORD
LADDR
Logical address of the input channels
INT
LADDR1
Logical address of the output channels
INT
MODE_xx
Channel xx mode
DWORD
MS
Maintenance status
DWORD
MS_REQ
BOOL
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Output parameters
I/O
(parameter)
Meaning
Data type Default
CH_ACTIVE
Channel active
DWORD
16#00000000
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
DXCHG_xx

(xx = 00 - 15)
DWORD
DXCHG1_XX
Bidirectional data exchange channel (xx = 00 - 15) DWORD
EXT_STAT
DWORD
EXT_STAT_A
DWORD

Byte 1: Reserved
Byte 2: Reserved

MOD_INF
STRUCT
MS_XCHG_xx
Maintenance Status - Data exchange channel (xx

= 00 - 63)
DWORD
MSG_ACK
WORD
MSG_STAT
WORD
O_MS
Maintenance status
DWORD
OMODE_xx
Channel xx mode
DWORD
QERR
1 = program error
BOOL

107
Family: @System
I/O
(parameter)
Meaning
Data type Default
QMODF
BOOL
QPERAF
BOOL
QRACKF
1 = failure of the rack
BOOL
In/out parameters
I/O
(parameter)
Meaning
Data type
Defau
lt
ACC_MODE
BOOL
CPU_DIAG
STRUCT
RAC_DIAG
STRUCT
5.17.3
MOD_64
108
Message
block
ALARM_8P
Message
number
EV_ID
Block
parameter
Messag
e
class
Module @1%d@/@2%d@/@3%d@:
Removed
QPERAF

error
QMODF
Module @1%d@/@2%d@/@3%d@: @4W

%t#MOD_n_TXT@ (n = 1, 2, 3 or 64)
QMODF
Module @1%d@/@2%d@/@3%d@: @4W

%t#MOD_n_TXT@ (n = 1, 2, 3 or 64)

Family: @System
5.18 MOD_4: Monitoring ET 200S modules downstream of a Y-Link

Message block
ALARM_8P

d
value
Meaning
EV_ID
MOD_INF.SUBN_ID
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
Slot number (byte)

(n = 1, 2, 3 or 64) (Message 1)
See also
5.18
MOD_4: Monitoring ET 200S modules downstream of a Y-Link
5.18.1

FB 119
Area of application
Block MOD_4 monitors modules (up to 16 channels) of an ET 200S acting as a DPV0 slave
(IM 151 High Feature) downstream of a Y link.
Calling OBs
OB 1
Cyclic program
OB 82
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart

109
Family: @System
Use in CFC
function:
Block MOD_4 is installed in its runtime group downstream of the OB_DIAG1 block, which
is used for the ET 200S downstream of a Y link, in the above-mentioned OBs.
The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the OB_DIAG1
blocks (for DP slave downstream of a Y link, and an OB_DIAG1 for each Y link) are
interconnected with the IN_OUT structures RAC_DIAG (DP slave) and RAC_DIAG_L (Y
link) of MOD_4.
whose inputs are interconnected with the outputs EN_SUBx (x = number of the DP master
block, EN_F of the OB_DIAG1 block for the Y link, EN_F of the OB_DIAG1 block for the ET
200S downstream of the Y link, and EN_Mxx (xx = module slot number in the ET 200S) of
the DPDIAGV0 block.
The DPA_M input is interconnected with the DPA_Mxx (xx= module slot number in the ET
200S) output of the DPDIAGV0 block.
MS parameter.
Function
Block MOD_4 analyzes all events related to an ET 200S module acyclically. It generates a
channel-specific MODE (Page 341) and value status for the signal processing blocks.
ALARM_8P reports events separately for each module.
The block enabled to run by the higher-level DPDIAGV0 block. The event to be evaluated is
available at input DPA_M. Possible byte assignments:
0000000 = Module OK
0000001 = Module error
0000010 = Wrong module
0000011 = Module missing
00001xx = ET 200S failure; x = irrelevant
configuration data created in HW Config is reported here. The function writes MODE_xx to the
low word of the OMODE_xx (Page 351) output parameter. This only occurs if the module status
changes during startup, or if you set ACC_MODE = TRUE. The current channel value status
is written to the most significant byte. If the result is positive, the system sets OMODE_xx =
16#80xxxxxx.
110

Family: @System
Events that are evaluated by the OB_DIAG1 block:
Rack failure (OB 86,OB 83) (output parameter QRACKF = TRUE)
Module diagnostics (OB 82) (output parameter QMODF = TRUE)
ALARM_8P is used to report "Module error ", "Wrong module " or "Module missing " events to
the OS.
Redundancy
You can not use redundant DP slaves downstream of a Y link.
MODE setting
Note
OMODE Structure

Addressing
Error handling
You will find additional information about error handling in

111
Family: @System
"Error information of output parameter MSG_STAT (Page 353)".
A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx (Page 351) outputs.
Time response
Not available
Message response
MOD_4 uses ALARM_8P to report module errors. The message function can be disabled by
setting EN_MSG = FALSE.
The block generates the maintenance status MS.

manual.
maintenance
5.18.2
I/Os of MOD_4
112

Family: @System
Input parameters
I/O
(parameter)
Meaning
Data type
Defau
lt
CHAN_NUM
INT
DPA_M
Module status
BYTE
EN_MSG
1 = Enable message
BOOL
EV_ID
Message number
DWORD
LADDR
INT
MODE_xx
Mode channel (xx = 00 - 15)
DWORD
MS
Maintenance status
DWORD
MS_REQ
BOOL
PADP_ADR
DP address of ET 200S
BYTE
255
RACK_NO
Rack number (Y-Link)
BYTE
SLOT_NO
Slot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Output parameters
I/O
(parameter)
Meaning
Data type Default
CH_ACTIVE
Channel active
DWORD
16#00000000
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
DXCHG_xx
Bidirectional data exchange channel (xx = 00 - 15)
DWORD
Byte 0:
Bit 0: Release for maintenance
Bit 1: Flutter suppression
Bit 2: Release for maintenance demanded
Byte 1: Reserved
Byte 2: Reserved
EXT_STAT
DWORD
MSG_ACK
WORD
MSG_STAT
WORD
O_MS
Maintenance status
DWORD
OMODE_xx
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QRACKF
BOOL

113
Family: @System
In/out parameters
I/O
(parameter)
Meaning
Data type
Defau
lt
0
ACC_MODE
BOOL
CPU_DIAG
STRUCT
RAC_DIAG
System structure: Rack diagnostics of the DP slave

downstream of Y link
STRUCT
RAC_DIAG_L
System structure: Rack diagnostics for the Y link
STRUCT
5.18.3
Message texts and associated values of MOD_4

Message block
ALARM_8P
Message
number
Message
class
EV_ID
Module @1%d@/@2%d@/@3%d@/@4%d@: Error
Module @1%d@/@2%d@/@3%d@/@4%d@: Wrong
Module @1%d@/@2%d@/@3%d@/@4%d@: Missing S

Message block
ALARM_8P
Associa
ted
value
Block
parameter
Meaning
EV_ID
SUBN_ID
RACK_NO
Rack/station number (byte) (Y link)
PADP_ADR
DP address of ET 200S
SLOT_NO
Slot number (byte)
See also
114

Family: @System
5.19 MOD_64: Monitoring 64 channels on S7-300 SM modules without diagnostic capability
5.19
MOD_64: Monitoring 64 channels on S7-300 SM modules without

diagnostic capability
5.19.1

FB 137
Area of application
The MOD_64 block monitors 64 channels on S7-300 SM modules without diagnostic capability
(no mixed modules). H systems support only the modules installed in switched racks.
Calling OBs
OB 1
Cyclic program
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:

115
Family: @System
MS parameter.
Function
The MOD_64 block analyzes all events that affect a module and its channels acyclically. It
The block is enabled to run by the higher-level RACK block. The event to be evaluated can
be found in the CPU_DIAG start information of the OB_DIAG block. There is a MODE_xx input
for each signal channel of the module. The module channel configuration data created in HW
Config is reported here. The function writes MODE_xx to the low word of the OMODE_xx
(Page 351) output parameter. This occurs only during startup or if you set ACC_MODE =
TRUE. The current channel value status is written to the most significant byte. If the result is
positive, the system sets OMODE_xx = 16#80xxxxxx.
(MOD_INF).
You will find additional information about errors in the System Software for S7-300/400; System
Redundancy
H system.
116

Family: @System
MODE setting
Note
OMODE Structure

The available channels on a module are displayed in the CH_EXIST or CH_EXIST_2 output
by setting a bit in the DWORD, starting at bit 0, for every existing channel. If the bit assigned
to a channel = 0, the channel is not available.
Output CH_OK or CH_OK_2 displays the valid channels on a module by setting a bit to TRUE
for every valid channel, where bit 0 is assigned to channel 0, etc. If the bit assigned to a channel
is 0, the channel is faulty. If a module error occurs, all channels are disrupted.
Addressing
Error handling
Service Information
(Page 351) outputs.

117
Family: @System
Time response
Not available
Message response

manual.
maintenance
5.19.2
I/Os of MOD_64
118

Family: @System
Input parameters
I/O
(parameter)
Meaning
Data type
Default
CHAN_NUM
INT
DELAY1
Alarm delay 1 (s)
INT
DELAY2
Alarm delay 2 (s)
INT
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = Enable message
BOOL
EV_ID
Message number
DWORD
LADDR
INT
MODE_xx
DWORD
MS
Maintenance status
DWORD
MS_REQ
BOOL
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Output parameters
I/O
(parameter)
Meaning
Data type Default
CH_ACTIVE
Channel active
DWORD
16#00000000
CH_ACTIVE_2
Channel active
DWORD
16#00000000
CH_EXIST
Channel exists (0 to 31)
DWORD
CH_EXIST_2
Channel exists (32 to 63)
DWORD
CH_OK
Channel OK (0 to 31)
DWORD
CH_OK_2
Channel OK (32 to 63)
DWORD
DXCHG_xx
DWORD
(xx = 00 - 15)
Byte 0:
Byte 1: Reserved
Byte 2: Reserved
DXCHG1_XX
Bidirectional data exchange channel (xx = 00

- 15)
DWORD
EXT_STAT
DWORD

119
Family: @System
I/O
(parameter)
Meaning
Data type Default
EXT_STAT_2
Release for maintenance - extended status 2 DWORD
EXT_STAT_A
DWORD

MOD_INF
STRUCT
MS_XCHG_xx

(xx = 00 - 63)
DWORD
MSG_ACK
WORD
MSG_STAT
WORD
O_MS
Maintenance status
DWORD
OMODE_xx
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QPERAF
BOOL
QRACKF
BOOL
In/out parameters
I/O
(parameter)
Meaning
Data type
Default
ACC_MODE
BOOL
CPU_DIAG
STRUCT
RAC_DIAG
STRUCT
Maintenance Status of MS (Page 356)
120

Family: @System
5.19.3
MOD_64
Message
block
ALARM_8P
Message
number
EV_ID
Block
parameter
Messag
e
class
Module @1%d@/@2%d@/@3%d@:
Removed
QPERAF

error
QMODF
Module @1%d@/@2%d@/@3%d@: @4W

%t#MOD_n_TXT@ (n = 1, 2, 3 or 64)
QMODF
Module @1%d@/@2%d@/@3%d@: @4W

%t#MOD_n_TXT@ (n = 1, 2, 3 or 64)

Message block
ALARM_8P

d
value
Meaning
EV_ID
MOD_INF.SUBN_ID
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
Slot number (byte)

(n = 1, 2, 3 or 64) (Message 1)
See also

121
Family: @System
5.20 MOD_CENTRAL: Monitoring CPUs which are not capable of diagnostics
5.20
MOD_CENTRAL: Monitoring CPUs which are not capable of diagnostics
5.20.1
Description of MOD_CENTRAL

FB 206
I/Os of MOD_CENTRAL (Page 122)
Area of application
The block is used for the integration of CP 443-x external, PROFIBUS/PROFINET (external),
IM 460/461 in the SIMATIC PCS 7 Maintenance Station.
MODE Configuration
Input parameters
PROFIBUS (DP-CPIO nodes)
PROFINET (IE-CPNetwork nodes)
PROFINET (IE-CP-IO
nodes)
Central IM-46x-x /
CP(Gateway)
MODE
16#00000001
16#00000002
16#00000004
16#00000003
For additional information, refer to the following sections:
Message texts and associated values of MOD_CENTRAL (Page 124)
See also
OMODE settings for SM modules (Page 351)
5.20.2
I/Os of MOD_CENTRAL
122

Family: @System
Input parameters
I/O
(parameter)
Meaning
Data type
Default
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = enable message
BOOL
EV_ID
Message number
DWORD
LADDR
INT
MODE
Operating mode
DWORD
MS
Maintenance status
DWORD
GBIT_ADR
Diagnostics address GBIT interface
INT
GBIT_PORT1_ADR
Diagnostics address GBIT PORT 1
INT
PNIO_ADR
Diagnostics address PN-IO interface
INT
PORT1_ADR
Diagnostics address PORT 1
INT
PORT1_CONNECT
1=Port 1 connected
BYTE
PORT2_ADR
INT
PORT2_CONNECT
1=Port 2 connected
BYTE
PORT3_ADR
INT
PORT3_CONNECT
1=Port 3 connected
BYTE
PORT4_ADR
INT
PORT4_CONNECT
1=Port 4 connected
BYTE
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBN_TYP
0 = central / 1 = external
BOOL
SUBN1_ID
CP: ID of subnet, if available. Otherwise, default

value IM 46x-x: always 0
BYTE
16#FF
Meaning
Data type
Default
0
Output parameters
I/O
(parameter)
EXT_STAT
Maintenance Release - Extended Status
DWORD
MOD_INF
STRUCT
MSG_ACK
WORD
MSG_STAT
WORD
OMODE
Operating mode
DWORD
O_MS
Maintenance status
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QRACKF
1 = rack error
BOOL

123
Family: @System
In/out parameters
I/O
(parameter)
Meaning
Data type
Default
0
ACC_MODE
BOOL
CPU_DIAG
STRUCT
RAC_DIAG
STRUCT
5.20.3
Message texts and associated values of MOD_CENTRAL

Message block
ALARM_8P
Message
number
Message
class
EV_ID
Module @1%d@/@2%d@/@3%d@: Failure
Module @1%d@/@2%d@/@3%d@:
Maintenance demanded
Module @1%d@/@2%d@/@3%d@:
Maintenance alarm
Module @1%d@/@2%d@/@3%d@:
Maintenance required
No message
No message
No message
No message

Message block
ALARM_8P
Associat
ed
value
Block parameters
Meaning
EV_ID
SUBN_ID
RACK_NO
SLOT_NO
Slot number (byte)
For additional information, see chapter: Message Classes (Page 355).
124

Family: @System
5.21 MOD_CP: CP 341 diagnostics
5.21
MOD_CP: CP 341 diagnostics
5.21.1
Description of MOD_CP

FB 98
MOD_CP block I/Os (Page 128)
Area of application
Block MOD_CP monitors a CP 341 serial communication module. H systems only support
modules in switched racks.
Calling OBs
OB 1
Cyclic program
OB 82
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:
The MOD_CP block is installed in its runtime group downstream of the RACK block runtime
The SUBN1_ID, SUBN2_ID, SUBN_TYP, RACK_NO, and SLOT_NO inputs are configured.
The logical base address LADDR of the module is configured.
are interconnected with the IN_OUT structures of the same name of MOD_CP.

125
Family: @System

Block MOD_CP analyzes all events that affect a module and its channels acyclically. and
generates a value status for the serial communication blocks (such as RCV_341). ALARM_8P
is used to report these events.
The higher-level RACK block enables the MOD_CP block to run. The event to be evaluated
is stored in the CPU_DIAG start and diagnostic information of the OB_BEGIN block. A
(MODE_00) is assigned to the communication channel of the module. The function writes
MODE_xx to the low word of the OMODE_xx (Page 351) output. This occurs only during startup
or if you set ACC_MODE = TRUE. The current value status of the communication channel is
written to the most significant byte. If the result is positive, the system sets OMODE_xx =
16#80xxxxxx.
Diagnostic interrupt (OB 82) Distinguishing between module errors and channel errors
The following events are module errors (QMODF = TRUE output parameter):
ALARM_8P is used to report "Module removed", "I/O access error" and "Diagnostic interrupt"
events to WinCC.
Redundancy
H system.

The existing channels on a module are displayed in the CH_EXIST output by setting a bit in
Error handling
126

Family: @System
(Page 351) outputs.
Overload behavior
The MOD_CP block counts the OB 82 calls. The counter is reset in OB1. If more than five OB
82 events occur in succession before the cycle control point is reached (OB 1), these events
are rejected and the message "OB 82 DP master failure: x Rack: y Slot: z" is output.
Time response
Not available
Message response
MOD_CP uses ALARM_8P to report module errors. The inputs DELAY1 and DELAY2 are
used to delay the output of I/O access error messages. DELAY1 allows you to enter a time in

manual.
Message texts and associated values of MOD_CP (Page 129)
See also
MODE settings for SM modules (Page 341)

127
Family: @System
5.21.2
I/Os of MOD_CP
Input parameters
I/O
(parameter)
Meaning
Data type
Default
DELAY1
Alarm delay 1 (s)
INT
DELAY2
Alarm delay 2 (s)
INT
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = enable message
BOOL
EV_ID
Message number
DWORD
LADDR
INT
MODE_00
Channel 1 mode
WORD
WORD
1: CP341
1: if the operating mode <> none
2: if the operating mode = none
MODE_01
Channel 2 mode
0: for CP341
1: if the operating mode <> none
2: if the operating mode = none
MS
Maintenance status
DWORD
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Output parameters
128
I/O
(parameter)
Meaning
Data type
Default
CH_ACTIVE
Channel active
DWORD
16#00000000
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
DIAG_INF
System structure: Diagnostic information
STRUCT
MOD_INF
STRUCT
MSG_ACK
WORD
MSG_STAT
WORD

Family: @System
I/O
(parameter)
Meaning
Data type
Default
O_MS
Maintenance status
DWORD
OMODE_00
Value status/channel 1 mode
DWORD
OMODE_01
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QPERAF
BOOL
QRACKF
1 = rack error
BOOL
I/O
(parameter)
Meaning
Data type
Default
ACC_MODE
BOOL
CPU_DIAG
STRUCT
RAC_DIAG
STRUCT
In/out parameters
Message texts and associated values of MOD_CP (Page 129)
5.21.3
Message texts and associated values of MOD_CP

Message block
ALARM_8P
Message
number
Block
parameter
Messa
ge
class
EV_ID
QMODF
CP @1%d@/@2%d@/@3%d@: Removed
QPERAF
CP @1%d@/@2%d@/@3%d@: Access error
CP @1%d@/@2%d@/@3%d@: @4W
%t#MOD_CP_TXT@
CP @1%d@/@2%d@/@3%d@:
Wrong parameter
CP @1%d@/@2%d@/@3%d@:
Wire break
CP @1%d@/@2%d@/@3%d@/2:
Wrong parameter

129
Family: @System
5.22 MOD_CP_PN: Monitoring of serial communication modules
Message block
ALARM_8P
Message
number
Block
parameter
Messa
ge
class
CP @1%d@/@2%d@/@3%d@/2: Wire break
CP @1%d@/@2%d@/@3%d@:
Multiple diagnostic interrupt
You will find the message texts and their text numbers in the "Text library for MOD_CP

Message block
ALARM_8P
Associat
ed
value
Block parameters
Meaning
EV_ID
SUBN_ID
RACK_NO
SLOT_NO
Slot number (byte)
SUBN_ID = SUBN1_ID. If SUBN1_ID = 16#FF, the associated value is substituted with

SUBN2_ID.
See also
5.22
MOD_CP_PN: Monitoring of serial communication modules
5.22.1
Description of MOD_CP_PN

FB 201
I/Os of MOD_CP_PN (Page 131)
Area of application
The MOD_CP_PN block monitors a serial communication module CP 341.
130

Family: @System
5.22.2
I/Os of MOD_CP_PN
Input parameters
I/O
(parameter)
Meaning
Data type
Default
DELAY1
Alarm delay 1 (s)
INT
DELAY2
Alarm delay 2 (s)
INT
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = enable message
BOOL
EV_ID
Message number ALARM_8P (assigned by the ES)
DWORD
LADDR
INT
MODE_00
Channel 1 mode
WORD
MODE_01
Channel 2 mode (CP 441 only)
WORD
MS
Maintenance status
DWORD
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBSL_NO
Subslot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
I/O
(parameter)
Meaning
Data type
Default
CH_ACTIVE
Channel active
DWORD
16#000
00000
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
DIAG_INF
STRUCT
MOD_INF
STRUCT
MSG_ACK
WORD
MSG_STAT
WORD
O_MS
Maintenance status
DWORD
OMODE_00
DWORD
OMODE_01
Value status/channel 2 mode (CP 441 only)
DWORD
QERR
1 = program error
BOOL
Output parameters

131
Family: @System
I/O
(parameter)
Meaning
Data type
Default
QMODF
BOOL
QPERAF
BOOL
QRACKF
1 = rack error
BOOL
I/O
(parameter)
Meaning
Data type
Default
ACC_MODE
BOOL
CPU_DIAG_PN
STRUCT
RAC_DIAG
STRUCT
In/out parameters
Message texts and associated values of MOD_CP_PN (Page 132)
5.22.3
Message texts and associated values of MOD_CP_PN

The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
132
Message block
ALARM_8P
Message
number
Message
class
EV_ID1
CP @1%d@/@2%d@/@3%d@: Withdrawn
CP @1%d@/@2%d@/@3%d@: Access error
CP @1%d@/@2%d@/@3%d@: @4W
%t#MOD_CP_TXT@
CP @1%d@/@2%d@/@3%d@:
Wrong parameter
CP @1%d@/@2%d@/@3%d@:
Wire break
CP @1%d@/@2%d@/@3%d@/2:
Wrong parameter
CP @1%d@/@2%d@/@3%d@/2: Wire break
CP @1%d@/@2%d@/@3%d@:

Family: @System
5.23 MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules with diagnostic functions
Associated values of ALARM_8P with EV_ID1
Associated
value
Block parameter
Meaning
SUBN_ID
ID of the PN IO system (bytes)
RACK_NO
SLOT_NO
Slot number (byte)
You will find the message texts and their text numbers in the section: "Text library for
MOD_CP_PN (FB201) (Page 367)"
5.23
MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules

with diagnostic functions
5.23.1
Description of MOD_D1

FB 93
MOD_D1 block I/Os (Page 139)
Area of application
The MOD_D1 block can monitor the following modules:
Power modules
ET200S counter modules
FM350 counter modules
up to 16 channels on S7-300/400 SM modules with diagnostic functions (no mixed modules)
and the power supplies of an ET 200iSP in a redundant configuration.
H systems support only the modules installed in switched racks.
Calling OBs
OB 1
Cyclic program
OB 82
OB 83
OB 85

133
Family: @System
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:
The MOD_D1 block is installed in its runtime group downstream of the RACK block runtime
The MODE_xx (mode of the channels xx of the module), SUBN1_ID, SUBN2_ID, and
SUBN_TYP inputs are configured.
are interconnected with the IN_OUT structures of the same name of MOD_D1.
MS parameter.

Block MOD_D1 analyzes all events that affect a module and its channels acyclically. It
blocks. ALARM_8P is used to report these events.
MOD_D1 monitors the redundant power supplies for ET 200iSP and reports the failure of a
power supply via the slot number of the interface module. The maintenance status (MS) of the
module shows, if the power supply fails "Maintenance: Requirement Moderate" an.
Block MOD_D1 is enabled by the higher-level RACK block at runtime. The event to be
evaluated is stored in the CPU_DIAG start and diagnostic information of the OB_BEGIN block.
low word of the OMODE_xx (Page 351) output parameter. This occurs only during startup or
if you set ACC_MODE = TRUE. The current channel value status is written to the most
significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx.
134

Family: @System
Rack failure (OB 86) (output parameter QPERAF = TRUE)
External auxiliary voltage missing
Front connector missing
Module not configured
Wrong parameter in module
Wrong/missing module
Communication error at a CPU module
Timeout (watchdog)
Loss of internal power at a module
Rack failure
CPU failure
EPROM error
RAM error
ADC/DAC error
Fuse tripped
Power supply 1: Error
The following events are channel errors (value status "invalid value", OMODE_xx = 16#00xxxx):
Configuration/parameter assignment error
Common-mode errors (analog I/Os only)
Short-circuit to P
Short circuit to M
Interruption at the output transistor
Wire break
Reference channel error (analog inputs only)
Measuring range underflow (analog inputs only)
Measuring range overflow (analog inputs only)

135
Family: @System
Missing load voltage (analog and digital outputs only)
Missing sensor power supply (digital outputs only)
Fuse tripped (digital outputs only)
Mass error (digital I/Os only)
Excess temperature (digital outputs only)
ALARM_8P is used to report "Module removed", "I/O access error", and "Diagnostic interrupt"
events to WinCC.
The diagnostics interrupt function distinguishes between module and channel errors, whereby
each channel is assigned a message ID. Only one incoming/outgoing event can be reported
for each channel. As long as an incoming message is queued at a channel, further messages
on new events at this channel will be lost.
If the event is defined uniquely in the diagnostic information, the corresponding text will be
entered in the message. If ambiguous entries exist, the text of the first set bit in the error byte
of the diagnostic information will be displayed. When using modules assigned diagnostic
functions and more than one error byte for diagnostic information, only the channel xx error
text will be output if the error information is not displayed in the first error byte.
(MOD_INF).
Detailed information about the errors is entered in the DIAG_INF output parameter of data type
STRUCT. You will find additional information about this in the reference manual System
Software for S7-300/400 System and Standard Functions; Diagnostic Data, Byte 0 to Byte 8,
Structure of Channel-Specific Diagnostic Data.
Note
If you run a HART module in HART MODE (Page 341) =16#070C, any HART protocol errors/
configuration changes will be masked by the MOD_D1 driver block, and will not be signaled
as channel errors.
Redundancy
H system.
MODE setting
Note
136

Family: @System
OMODE Structure

Addressing
You will find additional information about this in "Addressing (Page 353)".
HART modules with read/write access to the process image are configured in the same way
as input modules. The set I/O range must always be identical.
Example: SM 332 AO 2x0/4..20mA HART 332-5TB00-0AB0:
Address input range
(HW Config)
Address output range

(HW Config)
LADDR
(decimal/hex)
544
544
544 / 16#0220
Error handling
Service Information
Following a diagnostic interrupt, you will also find detailed module diagnostic information in
the MODDIAG0 to MODDIAG8 output parameters. You will find additional information in the
reference manual System Software for S7-300/400 System and Standard Functions;
Diagnostic Data, Byte 0 to Byte 8.
The CHDIAG00 to CHDIAG15 output parameters contain detailed channel-status information.
You will find additional information in the reference manual System Software for S7-300/400
System and Standard Functions; Structure of Channel-Specific Diagnostic Data.
The system resets this diagnostic information after a diagnostic interrupt has been reported
outgoing (no further channel or module errors are queued).

137
Family: @System
(Page 351) outputs.
Overload behavior
The MOD_D1 block counts the OB82 calls. The counter is reset in OB1. If more than two OB82
events occur in succession before the cycle control point is reached (OB1), these events are
rejected and the message "OB82 DP master failure: x Rack: y Slot: z" is output.
Time response
Not available
Message response
MOD_D1 uses ALARM_8P_1 to report module errors. The function also calls ALARM_8P_2
and ALARM_8P_3 which are intended for channel errors. The inputs DELAY1 and DELAY2
are used to delay the output of I/O access error messages. DELAY1 allows you to enter a time
in seconds for which the block will wait for a higher-priority error (rack failure or removal/
insertion) following a program execution error (OB 85) before it outputs the message. The
message is output only under the condition that no higher-priority error is reported within this
delay time. DELAY2 determines the number of seconds the block waits after the higher-priority
error has been reported outgoing until it outputs the queued I/O access error as well. Both
values are set to 2 seconds by default.
Flutter suppression
The "Flutter suppression" function is used to delay the outgoing of a message by a configurable
period.
The flutter time is entered at the channel block at the FlutTmIn parameter. The high byte of
the DXCHG parameter of the channel blocks contains the flutter time.
Flutter suppression comes into effect when FlutEN = 1 or FlutTmIn > 0 is set at the channel
block.
There is only one flutter message per module. The delay times and fault messages are channelspecific. The fault messages are extended by at least the delay time. Flutter exists if the fault
messages "Outgoing" and then "Incoming" are present within the delay time.
The last fluttering channel and its set delay time deactivates the flutter message.

manual.
138

Family: @System
Message texts and associated values of MOD_D1 (Page 141)
maintenance
5.23.2
I/Os of MOD_D1/MOD_D2
The MOD_D1 and MOD_D2 block I/Os are identical, with the exception of the number of
MODE_xx and OMODE_xx. The number of monitored channels determines the corresponding
number of I/O parameters (xx).
Input parameters
I/O
(parameter)
Meaning
Data type
Default
CHAN_NUM
INT
DELAY1
Alarm delay 1 (s)
INT
DELAY2
Alarm delay 2 (s)
INT
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = Enable message
BOOL
EV_IDx
Message number (x = 1 - 3)
DWORD
LADDR
INT
MODE_xx
Operating mode channel xx (xx = 00 - 15 / 00 - 31)
DWORD
MS
Maintenance status
DWORD
MS_REQ
BOOL
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255

139
Family: @System
Output parameters
I/O
(parameter)
Meaning
Data type
Default
CH_ACTIVE
Channel active
DWORD
16#000
00000
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
DIAG_INF
STRUCT
DM_ACTIVE
Fault delay
DWORD
16#0
DXCHG_xx
DWORD
DWORD

Byte 1: Reserved
Byte 2: Reserved
DXCHG1_XX

(xx = 00 - 15)
EXT_STAT
DWORD
EXT_STAT_A
DWORD
0
16#000
00000

FS_ACTIVE
Flutter suppression
DWORD
MOD_INF
STRUCT
MS_XCHG_xx
Maintenance Status - Data exchange channel (xx =

00 - 63)
DWORD
MSG_ACKx
Message acknowledgment (x = 1 - 3)
WORD
MSGSTATx
Message error information (x = 1 - 3)
WORD
O_MS
Maintenance status
DWORD
OMODE_xx
Channel mode (xx = 00 - 15/00 - 31)
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QPERAF
BOOL
QRACKF
1 = rack error
BOOL
Data type
Default
0
In/out parameters
I/O
(parameter)
140
Meaning
ACC_MODE
BOOL
CPU_DIAG
STRUCT

Family: @System
I/O
(parameter)
Meaning
Data type
Default
DataXchg
Bit 0 byte 0: MS_Release
DWORD
Bit 1 byte 0: FlutEn

Bit 2 byte 0: Fault delay
Bit 3 byte 0: Fault delay active
Bit 4 bit 7 byte 0 - Reserved
Byte 1 - Reserved
Byte 2 - Reserved
Byte 3: FlutTmIn/DelMsgTm
RAC_DIAG
STRUCT
5.23.3
Message texts and associated values of MOD_D1

Message block
ALARM_8P
Message
number
Block
parameter
Messag
e
class
EV_ID1
QMODF
Module @1%d@/@2%d@/@3%d@:
Removed
QPERAF
Module @1%d@/@2%d@/@3%d@:
Access error
QMODF
Module @1%d@/@2%d@/@3%d@:
@5W%t#MOD_D1_TXT@
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
@4W%t#MOD_D1_TXT@
Module @1%d@/@2%d@/@3%d@:
@4W%t#MOD_D1_TXT@
Module @1%d@/@2%d@/@3%d@:
@5W%t#MOD_D1_TXT@
8
EV_ID2

Module @1%d@/@2%d@/@3%d@:
Error channel 00 @4W%t#MOD_D1_TXT@
141
Family: @System
Message block
ALARM_8P
Message
number
Block
parameter
...
...
EV_ID3
Messag
e
class
...
...
...
...
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
...
...
...
...
Module @1%d@/@2%d@/@3%d@:
...
...
8
You will find the message texts and their text numbers in "Text library for MOD_D1
(Page 362)".

Message block
ALARM_8P

d
value
Meaning
EV_ID1
MOD_INF.SUBN_ID
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
EV_ID2
Text number (message 5) from MOD_D1_TXT
Text number (message 3) from MOD_D1_TXT
MOD_INF.SUBN_ID
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
Slot number (byte)
EV_ID3
Slot number (byte)
Text number (messages 1 - 8) from

MOD_D1_TXT
MOD_INF.SUBN_ID
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
Slot number (byte)

Text number (messages 1 - 8) from
MOD_D1_TXT
See also
142

Family: @System
5.24 MOD_D16_PN: Monitoring S7-300 SM modules with up to 16 channels and with diagnostics functions
5.24
MOD_D16_PN: Monitoring S7-300 SM modules with up to 16 channels

and with diagnostics functions
5.24.1
Description of MOD_D16_PN

FB 198
I/Os of MOD_D16_PN/MOD_D24_PN (Page 143)
Area of application
Block MOD_D16_PN monitors S7-300 SM modules with a maximum of 16 channels and with
diagnostics functions.
5.24.2
I/Os of MOD_D16_PN/MOD_D24_PN
Input parameters
I/O
(parameter)
Meaning
Data type
Default
CHAN_NUM
INT
DELAY1
Alarm delay 1 (s)
INT
DELAY2
Alarm delay 2 (s)
INT
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = Enable message
BOOL
EV_IDx
Message number ALARM_8P_x

(x = 1 - 2/1 - 3/1 - 4, assigned by the ES)
DWORD
FEATURE_xx
Feature parameter (xx = 01 - 04)
WORD
FEATURE_yy
Feature parameter (yy = 05 - 10)
DWORD
LADDR
Logic input address of the module
INT
LADDR1
Logical output address of the module (if output

address is not the same as input address).
INT

143
Family: @System
I/O
(parameter)
Meaning
Data type
Default
MODE_xx
Operating mode channel xx (xx = 00 - 07/00 - 15/00

- 23)
DWORD
MS
Maintenance status
DWORD
MS_REQ
BOOL
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBSL_NO
Subslot number
BYTE
SUBN_TYP
1 = external PN interface
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Output parameters
I/O
(parameter)
Meaning
Data type
Default
CH_ACTIVE
Channel active
DWORD
16#0000000
0
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
DIAG_INFx
STRUCT
DXCHG_xx
DWORD
DWORD

Byte 1: Reserved
Byte 2: Reserved
DXCHG1_XX
EXT_STATx
DWORD
EXT_STAT_A
DWORD
FS_ACTIVE
Flutter suppression active
DWORD
16#0000000
0
MOD_INF
STRUCT
MS_XCHG_xx

00 - 63)
DWORD
MSG_ACKx
Message acknowledgment (x = 1 - 2/1 - 3/1 - 4)
WORD
MSGSTATx
Message error information (x = 1 - 2/1 - 3/1 - 4)
WORD
144
O_MS
Maintenance status
DWORD
OMODE_xx

- 23)
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL

Family: @System
I/O
(parameter)
Meaning
Data type
Default
QPERAF
BOOL
QRACKF
1 = rack error
BOOL
In/out parameters
I/O
(parameter)
Meaning
Data type
Default
ACC_ID
BOOL
CPU_DIAG_PN
STRUCT
DWORD
DataXchg

Bit 3 bit to 7 byte 0 - Reserved
Byte 1 - Reserved
Byte 2 - Reserved
RAC_DIAG
STRUCT
Message texts and associated values of MOD_D16_PN/MOD_D24_PN (Page 145)
5.24.3
Message texts and associated values of MOD_D16_PN/MOD_D24_PN

Message block Message
ALARM_8P
number
Message
class
EV_ID1
Module @1%d@/@2%d@/@3%d@/@6%d@:
Withdrawn
Module @1%d@/@2%d@/@3%d@/@6%d@: Access

error
Module @1%d@/@2%d@/@3%d@/@6%d@: @5W

%t# MOD_D8_PN_TXT /MOD_D16_PN_TXT /
MOD_D24_PN_TXT@

145
Family: @System
ALARM_8P
number
Message
class
Module @1%d@/@2%d@/@3%d@/@6%d@: Multiple

diagnostics interrupt
Module @1%d@/@2%d@/@3%d@/@6%d@: @4W

MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/@6%d@: @4W

MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/@6%d@: @5W

MOD_D24_PN_TXT@
No
message

Associated value
Block parameter
Data type
ID of the PN IO system
BYTE
Rack/station number
BYTE
Slot number
BYTE
Text number (message 5) of MOD_D8_PN_TXT /

MOD_D16_PN_TXT /MOD_D24_PN_TXT
BYTE

BYTE
Subslot number
BYTE
146
Message block
ALARM_8P
Message
number
Message
class
EV_ID2

channel 00 @4W%t# MOD_D8_PN_TXT /
MOD_D16_PN_TXT /MOD_D24_PN_TXT @






Family: @System
Message block
ALARM_8P
Message
number
Message
class



Associated value
Block parameter
Data type
BYTE
Rack/station number
BYTE
Slot number
BYTE
Text number from MOD_D8_PN_TXT /MOD_D16_PN_TXT /

MOD_D24_PN_TXT
BYTE
Subslot number
BYTE
ALARM_8P
number
Message
class
EV_ID3

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

147
Family: @System
Associated value
Block parameter
Data type
BYTE
Rack/station number
BYTE
Slot number
BYTE

MOD_D24_PN_TXT
BYTE
Subslot number
BYTE
Process control messages for ALARM_8P with EV_ID4 are assigned as follows:
ALARM_8P
number
Message class
EV_ID_4
Module @1%d@/@2%d@/@3%d@/@5%d@:
Error channel 16 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:

Associated value
Block parameter
Data type
BYTE
Rack/station number
BYTE
Slot number
BYTE
Text number from MOD_D24_PN_TXT
BYTE
Subslot number
BYTE
You will find the message texts and their text numbers in the section Text library for
MOD_D8_PN (FB197) / MOD_D16_PN (FB198) / MOD_D24_PN (FB199) (Page 366).
148

Family: @System
5.25 MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with diagnostic functions
5.25
MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with

diagnostic functions
5.25.1

FB 94
Area of application
Block MOD_D2 monitors up to 32 channels on S7-300/400 SM modules with diagnostic
Calling OBs
OB 1
Cyclic program
OB 82
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:
The MOD_D2 block is installed in its runtime group downstream of the RACK block runtime

149
Family: @System
MS parameter.

Block MOD_D2 analyzes all events that affect a module and its channels acyclically. It
blocks. ALARM_8P is used to report these events. The message function can be disabled.
The block is enabled by the higher-level RACK block at runtime. The event to be evaluated is
stored in the CPU_DIAG start and diagnostic information of the OB_BEGIN block. There is a
MODE_xx input for each signal channel of the module. The module channel configuration data
created in HW Config is reported here. The function writes MODE_xx to the low word of the
Timeout (watchdog)
Rack failure
CPU failure
EPROM error
RAM error
150

Family: @System
ADC/DAC error
Fuse tripped
Short-circuit to P
Short circuit to M
Wire break
ALARM_8P is used to report "Module removed", "I/O access error", and "Diagnostic interrupt"
events to WinCC.
each channel is assigned a message ID. Only one incoming or outgoing event can be reported
information read here makes this data available in the form of service output parameters
(MOD_INF).
Redundancy
The block supports segment redundancy of CPU 417H for distributed I/Os. The SUBN1_ID
(connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs are configured with the

151
Family: @System
numbers of the redundant segments. If there is no segment redundancy, the remaining input
must be set to the (default) value 16#FF.
MODE setting
Note
OMODE Structure

Addressing
Error handling
Service Information
152

Family: @System
The CHDIAG00 to CHDIAG31 output parameters contain detailed channel status information.
(Page 351) outputs.
Time response
Not available
Message response
MOD_D2 uses ALARM_8P_1 to report module errors. In addition, the error blocks
ALARM_8P_2, ALARM_8P_3, ALARM_8P_4 and ALARM_8P_5 are called. The inputs
DELAY1 and DELAY2 are used to delay the output of I/O access error messages. DELAY1
allows you to enter a time in seconds for which the block will wait for a higher-priority error
(rack failure or removal/insertion) following a program execution error (OB 85) before it outputs
the message. The message is output only under the condition that no higher-priority error is
reported within this delay time. DELAY2 determines the number of seconds the block waits
after the higher-priority error has been reported outgoing until it outputs the queued I/O access
error as well. Both values are set to 2 seconds by default.
Flutter suppression
period.
block.


153
Family: @System
manual.
maintenance
5.25.2
I/Os of MOD_D1/MOD_D2
The MOD_D1 and MOD_D2 block I/Os are identical, with the exception of the number of
MODE_xx and OMODE_xx. The number of monitored channels determines the corresponding
number of I/O parameters (xx).
Input parameters
154
I/O
(parameter)
Meaning
Data type
Default
CHAN_NUM
INT
DELAY1
Alarm delay 1 (s)
INT
DELAY2
Alarm delay 2 (s)
INT
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = Enable message
BOOL
EV_IDx
DWORD
LADDR
INT
MODE_xx
Operating mode channel xx (xx = 00 - 15 / 00 - 31)
DWORD
MS
Maintenance status
DWORD
MS_REQ
BOOL
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255

Family: @System
Output parameters
I/O
(parameter)
Meaning
Data type
Default
CH_ACTIVE
Channel active
DWORD
16#000
00000
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
DIAG_INF
STRUCT
DM_ACTIVE
Fault delay
DWORD
16#0
DXCHG_xx
DWORD
DWORD

Byte 1: Reserved
Byte 2: Reserved
DXCHG1_XX

(xx = 00 - 15)
EXT_STAT
DWORD
EXT_STAT_A
DWORD
0
16#000
00000

FS_ACTIVE
Flutter suppression
DWORD
MOD_INF
STRUCT
MS_XCHG_xx

00 - 63)
DWORD
MSG_ACKx
WORD
MSGSTATx
WORD
O_MS
Maintenance status
DWORD
OMODE_xx
Channel mode (xx = 00 - 15/00 - 31)
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QPERAF
BOOL
QRACKF
1 = rack error
BOOL
Data type
Default
0
In/out parameters
I/O
(parameter)
Meaning
ACC_MODE
BOOL
CPU_DIAG
STRUCT

155
Family: @System
I/O
(parameter)
Meaning
Data type
Default
DataXchg
DWORD

Byte 1 - Reserved
Byte 2 - Reserved
RAC_DIAG
STRUCT
See also
MODE settings for SM modules (Page 341)
OMODE settings for SM modules (Page 351)
5.25.3

Message block
ALARM_8P
Message
number
Block
parameter
Messag
e
class
EV_ID1
QMODF
Module @1%d@/@2%d@/@3%d@:
Removed
QPERAF
Module @1%d@/@2%d@/@3%d@: Access S

error
QMODF
Module @1%d@/@2%d@/@3%d@:
@5W%t#MOD_D2_TXT@
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
@4W%t#MOD_D2_TXT@
Module @1%d@/@2%d@/@3%d@:
@4W%t#MOD_D1_TXT@
156

Family: @System
Message block
ALARM_8P
EV_ID2
Message
number
Block
parameter
...
EV_ID3
S
S
Module @1%d@/@2%d@/@3%d@:
Error channel 00
@4W%t#MOD_D2_TXT@
Module @1%d@/@2%d@/@3%d@:
Error channel 07
@4W%t#MOD_D2_TXT@
Module @1%d@/@2%d@/@3%d@: Error

channel 08
@4W%t#MOD_D2_TXT@
...
Module @1%d@/@2%d@/@3%d@:
Error channel 15
@4W%t#MOD_D2_TXT@
Module @1%d@/@2%d@/@3%d@:
Error channel 16
@4W%t#MOD_D2_TXT@
...
EV_ID5
Messag
e
class
...
...
EV_ID4
...
Module @1%d@/@2%d@/@3%d@:
Error channel 23
@4W%t#MOD_D2_TXT@
Module @1%d@/@2%d@/@3%d@:
Error channel 24
@4W%t#MOD_D2_TXT@
...
...
Module @1%d@/@2%d@/@3%d@:
Error channel 31
@4W%t#MOD_D2_TXT@
You will find the message texts and their text numbers in "Text library for MOD_D2
(Page 361)".

Message block Associa
ALARM_8P
ted
value
Block parameters
Meaning
EV_ID1
MOD_INF.SUBN_ID
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
Slot number (byte)
Text number (messages 1 - 3) of MOD_D2_TXT
MOD_INF.SUBN_ID
EV_ID2

157
Family: @System
Message block Associa
ALARM_8P
ted
value
EV_ID3
EV_ID4
EV_ID5
Block parameters
Meaning
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
Slot number (byte)
Text number (message 5) of MOD_D2_TXT
MOD_INF.SUBN_ID
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
Slot number (byte)
MOD_INF.SUBN_ID
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
Slot number (byte)
MOD_INF.SUBN_ID
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
Slot number (byte)
See also
5.26

5.26.1

FB 199
I/Os of MOD_D16_PN/MOD_D24_PN (Page 159)
Area of application
158

Family: @System
5.26.2
I/Os of MOD_D16_PN/MOD_D24_PN
Input parameters
I/O
(parameter)
Meaning
Data type
Default
CHAN_NUM
INT
DELAY1
Alarm delay 1 (s)
INT
DELAY2
Alarm delay 2 (s)
INT
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = Enable message
BOOL
EV_IDx

DWORD
FEATURE_xx
WORD
FEATURE_yy
DWORD
LADDR
INT
LADDR1

INT
MODE_xx

- 23)
DWORD
MS
Maintenance status
DWORD
MS_REQ
BOOL
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBSL_NO
Subslot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255

159
Family: @System
Output parameters
I/O
(parameter)
Meaning
Data type
Default
CH_ACTIVE
Channel active
DWORD
16#0000000
0
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
DIAG_INFx
STRUCT
DXCHG_xx
DWORD

Byte 1: Reserved
Byte 2: Reserved
DXCHG1_XX
DWORD
EXT_STATx
DWORD
EXT_STAT_A
DWORD
0
16#0000000
0

FS_ACTIVE
DWORD
MOD_INF
STRUCT
MS_XCHG_xx

00 - 63)
DWORD
MSG_ACKx
WORD
MSGSTATx
WORD
O_MS
Maintenance status
DWORD
OMODE_xx

- 23)
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QPERAF
BOOL
QRACKF
1 = rack error
BOOL
In/out parameters
160
I/O
(parameter)
Meaning
Data type
Default
ACC_ID
BOOL
CPU_DIAG_PN
STRUCT

Family: @System
I/O
(parameter)
Meaning
Data type
Default
DataXchg
DWORD

Bit 3 bit to 7 byte 0 - Reserved
Byte 1 - Reserved
Byte 2 - Reserved
RAC_DIAG
STRUCT
Message texts and associated values of MOD_D16_PN/MOD_D24_PN (Page 161)
5.26.3
Message texts and associated values of MOD_D16_PN/MOD_D24_PN

ALARM_8P
number
Message
class
EV_ID1
Module @1%d@/@2%d@/@3%d@/@6%d@:
Withdrawn

error
Module @1%d@/@2%d@/@3%d@/@6%d@: @5W

MOD_D24_PN_TXT@

Module @1%d@/@2%d@/@3%d@/@6%d@: @4W

MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/@6%d@: @4W

MOD_D24_PN_TXT @

161
Family: @System
ALARM_8P
number
7
Message
class
Module @1%d@/@2%d@/@3%d@/@6%d@: @5W

MOD_D24_PN_TXT@
No
message

Associated value
Block parameter
Data type
BYTE
Rack/station number
BYTE
Slot number
BYTE

BYTE

BYTE
Subslot number
BYTE
Message block
ALARM_8P
Message
number
Message
class
EV_ID2








162

Family: @System
Associated value
Block parameter
Data type
BYTE
Rack/station number
BYTE
Slot number
BYTE

MOD_D24_PN_TXT
BYTE
Subslot number
BYTE
ALARM_8P
number
Message
class
EV_ID3

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

Associated value
Block parameter
Data type
BYTE
Rack/station number
BYTE
Slot number
BYTE

MOD_D24_PN_TXT
BYTE
Subslot number
BYTE

163
Family: @System
ALARM_8P
number
Message class
EV_ID_4
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:

Associated value
Block parameter
Data type
BYTE
Rack/station number
BYTE
Slot number
BYTE
BYTE
Subslot number
BYTE
164

Family: @System
5.27 MOD_D3: Monitoring of hybrid modules with diagnostic capability
5.27
MOD_D3: Monitoring of hybrid modules with diagnostic capability
5.27.1

FB 134
Area of application
Block MOD_D3 monitors a maximum of up to 16 channels on S7-300 SM modules with
diagnostics functions. H systems support only the modules installed in switched racks.
MOD_D3 includes all the functionality of MOD_D1, plus additional functions for diagnostic
evaluation of multiple channel types in a diagnostic data record. The block also fully supports
4-byte channel-specific diagnostics.
Note: MOD_D1 only evaluated 8 selected bits of the 4-byte channel-specific diagnosis.
The modules supported are the ET 200PRO modules:
6ES7 148 4FC00 0AB0 -> 8DI/4DO
6ES7 148 4FA00 0AB0 -> 8/16 DI
and the ET 200M HART modules:
6ES7 331-7TF01-0AB0 -> AI8 HART
6ES7 332-8TF01-0AB0 -> AO8 HART
Calling OBs
OB 1
Cyclic program
OB 82
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:
The MOD_D3 block is installed in its runtime group downstream of the RACK-block runtime

165
Family: @System
MS parameter.

The MOD_D3 block analyzes all events affecting a module and its channels acyclically. It
blocks. ALARM_8P is used to report these events.
Execution of the MOD_D3 block is enabled by the higher-level RACK block. The event to be
evaluated is stored in the CPU_DIAG start and diagnostic information of the OB_BEGIN block.
low word of the OMODE_xx (Page 351) output parameter. This occurs only during startup or
if you set ACC_MODE = TRUE. The current channel value status is written to the most
significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx.
Rack failure (OB 86) (output parameter QPERAF = TRUE)
Timeout (watchdog)
166

Family: @System
Rack failure
CPU failure
EPROM error
RAM error
ADC/DAC error
Fuse tripped
Short-circuit to P
Short circuit to M
Wire break
Undervoltage
Overvoltage
Overload
Hardware interrupt
Actuator warning
Safety shutdown
Ambiguous error
Error 1 in actuator/sensor
Channel temporarily not available

167
Family: @System
ALARM_8P is used to report "Module removed", "I/O access error" and "Diagnostics interrupt"
events to the OS.
each channel is assigned a message ID. Only one incoming/outgoing event can be reported
(MOD_INF).
Note
Even if you run a HART module in HART MODE =16#070C, any HART protocol errors/
configuration changes that may occur will be masked by the MOD_D3 block, and not signaled
as channel errors.
Several channel types can occur in one diagnostic data record. If the "further channel types
exist" bit is set, MOD_D3 runs through the entire diagnostic evaluation and handles reporting
for each further channel type.
HART modules with the firmware update and the new additional channel type 16#66 for
measured value calibration are also supported.
The new HART channel type 66 can also occur in the diagnostic data record as a further
channel type.
The new diagnostic data ("channel being calibrated" and "channel temporarily not available")
are considered as channel errors and output. The detailed texts are output via the system text
library and a corresponding associated value.
Channel type 0x66:
1 byte channel diagnostics
Bit0 channel being calibrated
Bit1 channel temporarily not available
Firmware update
The firmware update for the listed HART modules is started by a diagnostic event "OB83
entering state" (remove module) followed directly by diagnostic event "OB83 exiting state"
(insert module). With "OB83 exiting state", byte 2 bit 2 is set in data record 0 (1 = STOP mode).
168

Family: @System
Once the firmware is completed, there is a repeated diagnostic event "OB83 entering state"
(remove module) followed directly by diagnostic event "OB83 exiting state" (insert module).
With "OB83 exiting state", byte 2 bit 2 is reset in data record 0 (0 = RUN mode).
In MOD_D3, after an "OB83 exiting state" (module removed) the data record 0 (DS0) is always
read extra in OB1 using SFC51 and SZL 00B1 to establish whether bit (1 = STOP mode) is
set. If this is the case, this is always recognized as a firmware update and the module continues
to be indicated as removed and not available. Only when there is an OB83 (module inserted)
with the information in DS0 (0 = RUN mode), is the module indicated as being inserted and
available again.
It is assumed that "Module change in run" is always set for the ET 200M head modules so that
a firmware update of the HART module always calls an OB83. This means that a firmware
update cannot trigger an OB86 diagnostic interrupt.
The "Generate module driver" function enters 16#0001 in the Feature01 parameter for both
HART modules. This means that DS0 is read extra when there is an OB 83 exiting state only
when Feature01 = 16#0001
The Feature parameters (FEATURE_01 .. FEATURE_10) are intended for future expansions
of the MOD_D3 block and for parameter settings for special module situations.
Currently only FEATURE_01 is used as an ID for HART module with a firmware update in RUN.
Redundancy
H system.
MODE Setting
Note
OMODE Structure
You will find additional information about this in the "OMODE settings (Page 351)" section.


169
Family: @System
Addressing
You will find additional information about this in "Addressing (Page 353)".
HART modules with read/write access to the process image are configured in the same way
as input modules. The set I/O range must always be identical.
Example: SM 332 AO 2x0/4..20mA HART 332-5TB00-0AB0:
Address input range (HW Config)
Address output range (HW Config)
LADDR (decimal/hex)
544
544
544 / 16#0220
Error handling
parameter MSG_STAT" (Page 353) section.
Service Information
base address. A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx outputs.
Overload Behavior
The MOD_D3 block counts the OB82 calls. The counter is reset in OB1. If more than two OB82
events occur in succession before the cycle control point is reached (OB1), these events are
rejected and the message "OB82 DP master failure: x Rack: y Slot: z" is output.
Time response
Not available
170

Family: @System
Message response
MOD_D3 uses ALARM_8P_1 to report module errors. The function also calls ALARM_8P_2
and ALARM_8P_3 which are intended for channel errors. The inputs DELAY1 and DELAY2
are used to delay the output of I/O access error messages. DELAY1 allows you to enter a time
in seconds for which the block will wait for a higher-priority error (rack failure or removal/
insertion) following a program execution error (OB 85) before it outputs the message. The
message is output only under the condition that no higher-priority error is reported within this
delay time. DELAY2 determines the number of seconds the block waits after the higher-priority
error has been reported outgoing until it outputs the queued I/O access error as well. Both
values are set to 2 seconds by default.
Flutter suppression
period.
block.

manual.
maintenance

171
Family: @System
5.27.2
I/Os of MOD_D3
Input parameters
I/O
(parameter)
Meaning
Data type
Defa
ult
CHAN_NUM
INT
DELAY1
Alarm delay 1 (s)
INT
DELAY2
Alarm delay 2 (s)
INT
DIAG_BUF
Entry in diagnostic buffer (relevant for maintenance personnel) BOOL
EN_MSG
1 = Enable message
BOOL
EV_IDx
DWORD
FEATURE_xx
WORD
FEATURE_yy
DWORD
LADDR
INT
LADDR1
Logical output address of the module (if output address is not

the same as input address).
INT
MODE_xx
Mode channel xx (xx = 00 - 15)
DWORD
MS
Maintenance status
DWORD
MS_REQ
BOOL
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
2
0
Output parameters
172
I/O
(parameter)
Meaning
Data type Default
CH_ACTIVE
Channel active
DWORD
16#00000000
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
DIAG_INF
STRUCT
DM_ACTIVE
Fault delay
DWORD
16#0

Family: @System
I/O
(parameter)
Meaning
Data type Default
DXCHG_xx

(xx = 00 - 15)
DWORD

Bit1 Byte0: Flutter suppression
Bit2 to Bit7 Byte0: Reserved
Byte 1: Reserved
Byte 2: Reserved
DXCHG1_XX

(xx = 00 - 15)
DWORD
EXT_STAT
DWORD
EXT_STAT_A
DWORD
0
16#00000000

FS_ACTIVE
Flutter suppression
DWORD
MOD_INF
STRUCT
MS_XCHG_xx
Maintenance Status - Data exchange channel (xx = 00

- 63)
DWORD
MSG_ACKx
WORD
MSGSTATx
WORD
O_MS
Maintenance status
DWORD
OMODE_xx
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QPERAF
BOOL
QRACKF
1 = rack error
BOOL
I/O
(parameter)
Meaning
Data type
Defa
ult
ACC_MODE
BOOL
CPU_DIAG
STRUCT
DataXchg
DWORD
In/out parameters

Byte 1 - Reserved
Byte 2 - Reserved
RAC_DIAG

STRUCT
173
Family: @System
5.27.3

Message block
ALARM_8P
Message
number
Block
parameter
Message
EV_ID1
QMODF
Module @1%d@/@2%d@/@3%d@: Removed
QPERAF
Module @1%d@/@2%d@/@3%d@: Access error
QMODF
Module @1%d@/@2%d@/@3%d@:
@5W%t#MOD_D3_TXT@
Module @1%d@/@2%d@/@3%d@: Multiple diagnostic

interrupt
Module @1%d@/@2%d@/@3%d@:
@4W%t#MOD_D3_TXT@
Module @1%d@/@2%d@/@3%d@:
@4W%t#MOD_D3_TXT@
Module @1%d@/@2%d@/@3%d@:
@5W%t#MOD_D3_TXT@
class
EV_ID2
...
...
EV_ID3
Module @1%d@/@2%d@/@3%d@:
...
...
...
...
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
...
...
...
...
Module @1%d@/@2%d@/@3%d@:
...
...
8
You will find the message texts and their text numbers in "Text library for MOD_D3"
(Page 364).
174

Family: @System

Message block
ALARM_8P
Associated
value
Block parameters
Meaning
EV_ID1
MOD_INF.SUBN_ID
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
Slot number (byte)
EV_ID2
MOD_INF.SUBN_ID
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
Slot number (byte)
4
EV_ID3
Text number (messages 1 - 8) from MOD_D3_TXT
MOD_INF.SUBN_ID
MOD_INF.RACK_NO
MOD_INF.SLOT_NO
Slot number (byte)
Text number (messages 1 - 8) from MOD_D3_TXT
See also
5.28

5.28.1

FB 198
I/Os of MOD_D8_PN (Page 176)
Area of application

175
Family: @System
5.28.2
I/Os of MOD_D8_PN
Input parameters
I/O
(parameter)
Meaning
Data type
Default
CHAN_NUM
INT
DELAY1
Alarm delay 1 (s)
INT
DELAY2
Alarm delay 2 (s)
INT
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = Enable message
BOOL
EV_IDx

DWORD
FEATURE_xx
WORD
FEATURE_yy
DWORD
LADDR
INT
LADDR1

INT
MODE_xx

- 23)
DWORD
MS
Maintenance status
DWORD
MS_REQ
BOOL
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBSL_NO
Subslot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Output parameters
176
I/O
(parameter)
Meaning
Data type
Default
CH_ACTIVE
Channel active
DWORD
16#0000000
0
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
DIAG_INFx
STRUCT

Family: @System
I/O
(parameter)
Meaning
Data type
Default
DM_ACTIVE
Fault delay
DWORD
16#0
DXCHG_xx
DWORD

Byte 1: Reserved
Byte 2: Reserved
DXCHG1_XX
DWORD
EXT_STATx
DWORD
EXT_STAT_A
DWORD
0
16#0000000
0

FS_ACTIVE
DWORD
MOD_INF
STRUCT
MS_XCHG_xx

00 - 63)
DWORD
MSG_ACKx
WORD
MSGSTATx
WORD
O_MS
Maintenance status
DWORD
OMODE_xx

- 23)
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QPERAF
BOOL
QRACKF
1 = rack error
BOOL
In/out parameters
I/O
(parameter)
Meaning
Data type
Default
ACC_ID
BOOL
CPU_DIAG_PN
STRUCT
DWORD
DataXchg

Bit 4 ... bit 7 byte 0 - Reserve
Byte 1 - Reserved
Byte 2 - Reserved
RAC_DIAG

STRUCT
177
Family: @System
Message texts and associated values of MOD_D8_PN (Page 178)
5.28.3
Message texts and associated values of MOD_D8_PN

ALARM_8P
number
Message
class
EV_ID1
Module @1%d@/@2%d@/@3%d@/@6%d@:
Withdrawn

error
Module @1%d@/@2%d@/@3%d@/@6%d@: @5W

MOD_D24_PN_TXT@

Module @1%d@/@2%d@/@3%d@/@6%d@: @4W

MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/@6%d@: @4W

MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/@6%d@: @5W

MOD_D24_PN_TXT@
No
message
178
Associated value
Block parameter
Data type
BYTE
Rack/station number
BYTE
Slot number
BYTE

BYTE

Family: @System
Associated value
Block parameter
Data type

BYTE
Subslot number
BYTE
Message block
ALARM_8P
Message
number
Message
class
EV_ID2









Associated value
Block parameter
Data type
BYTE
Rack/station number
BYTE
Slot number
BYTE

MOD_D24_PN_TXT
BYTE
Subslot number
BYTE

179
Family: @System
ALARM_8P
number
Message
class
EV_ID3

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

MOD_D24_PN_TXT @

Associated value
Block parameter
Data type
BYTE
Rack/station number
BYTE
Slot number
BYTE

MOD_D24_PN_TXT
BYTE
Subslot number
BYTE
180

ALARM_8P
number
Message class
EV_ID_4
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:

Family: @System
5.29 MOD_DRV: Monitoring of drive blocks with diagnostics functions
ALARM_8P
number
Message class
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:
Module @1%d@/@2%d@/@3%d@/@5%d@:

Associated value
Block parameter
Data type
BYTE
Rack/station number
BYTE
Slot number
BYTE
BYTE
Subslot number
BYTE
5.29
MOD_DRV: Monitoring of drive blocks with diagnostics functions
5.29.1
Description of MOD_DRV

FB 148
Block interfaces of MOD_DRV (Page 183)
Area of application
The MOD_DRV block creates a device-specific diagnostics function for blocks of the Drive
type.
The following events are processed in the MOD_DRV and the status messages reported in
WinCC:

181
Family: @System
SwitchType
Message text
Message class in
WinCC
Maintenance
State
Status (for each

interconnectable output)
SA
00
16#80
Ready for operation
SA
00
16#80
Error active
07
16#00
Telegram1/
Telegram20
(NAMUR off and
on)
Ready to switch on
Warning active
06
16#68
Telegram20
(NAMUR on)
Error in the controller/

software
07
16#00
Fault in the power supply

network
07
16#00
Overvoltage in the DC Link
07
16#00
Fault in the power supply
07
16#00
Temperature limiter converter S
07
16#00
Grounding fault
07
16#00
Motor overload
07
16#00
Error in the communication
07
16#00
External safety shutdown
06
16#68
Error in the speed

measurement
07
16#00
Error in the internal

communication
07
16#00
Fault in the infeed system
07
16#00
Other fault or error
07
16#00
Calling OBs
The cyclic OB 1 and OB 100.
In addition, the block is installed in the cyclic interrupt OB OB3x in which the following signal
processing driver block is installed.
Use in CFC
function:
The block is installed when the corresponding SlaveFamily 1 object exists
Further interconnection takes place in the same way as for the existing MODPAL/X0 blocks
of the PCS 7 Basis Library
The corresponding inputs are read out of HW Config and configured.
The block is interconnected with the corresponding Drive block through the DXCHG_00,
OMODE_00 and O_MS parameters.
Initialization of the ALARM_8P blocks and of the NOTIFY_8P blocks.
182

Family: @System
Message response
The block reports errors using ALARM_8P and NOTIFY_8P.
OB no.
Start event
Message
Cyclic processing
Have the ALARM_8P/NOTIFY_8P outputs/messages

updated, if necessary
100
Restart
MODE behavior
The block is informed by the MODE input about which function block or device type is involved.
A distinction is made between the device and type or profile respectively.
Only the Drive type is currently implemented. This has the mode XXXX0010.
5.29.2
I/Os of MOD_DRV
I/Os
Input parameters
Parameter
Description
Type
Defaul
t
EN_MSG
1 = Enable message
BOOL
EV_ID1
Message number 1
DWORD
16#00
EV_ID2
Message number 2
DWORD
16#00
LINK_ADR
Link address
BYTE
MS
Maintenance status
DWORD
16#00
MS_REQ
BOOL
PADP_ADR
Address of the PA field device
BYTE
16#00
SUBN1_ID
BYTE
16#FF
SUBN2_ID
BYTE
16#FF

183
Family: @System
In/out parameters
Parameter
Description
Type
CPU_DIAG
Struct (see
OB_BEGIN)
RAC_DIAG
System structure: RACK diagnostics
Struct (see
OB_DIAG1)
Output parameters
Parameter
Description
Type
Defaul
t
CH_ACTIVE
Channel active
DWORD
16#00
00000
0
CH_EXIST
Channel exists
DWORD
16#00
00000
0
CH_OK
Channel OK
DWORD
16#00
00000
0
DXCHG_00
DWORD
16#00
DXCHG1
DWORD
DXCHG1_00
DWORD
Error
Error message is active
BOOL
EXT_STAT
DWORD
16#00
EXT_STAT_A
DWORD
184
MS_XCHG_00
DWORD
MSG_ACK1
WORD
16#00
MSG_ACK2
WORD
16#00
MSGSTAT1
Message error information 1
WORD
16#00
MSGSTAT2
WORD
16#00
Namur1
Namur1 message is active
BOOL
Namur2
BOOL
Namur3
BOOL
Namur4
BOOL
Namur5
BOOL
Namur6
BOOL
Namur7
BOOL
Namur8
BOOL
Namur9
BOOL
Namur10
BOOL
Namur11
BOOL
Namur12
BOOL

Family: @System
5.29.3
Parameter
Description
Type
Defaul
t
Namur13
BOOL
Namur14
BOOL
Namur15
BOOL
Namur16
BOOL
O_MS
Maintenance status
DWORD
16#00
OMODE_00
Value status of the PA field device
DWORD
16#00
QERR
1 = program error
BOOL
QRACKF
1 = PA slave/DP master error
BOOL
Warning
Warning message is active
BOOL
Message texts and associated values of MOD_DRV
Messaging
Message block
Class
Event
EV_ID1:SIG1
AS process control message - fault
Device @1%d@/ @2%d@: Bad,

maintenance alarm
EV_ID1:SIG2
AS process control message - error
Device @1%d@/ @2%d@: Uncertain,

maintenance demanded
EV_ID1:SIG3
Preventive maintenance - general
Device @1%d@/ @2%d@:

Good, maintenance required
EV_ID1:SIG6

Failure
EV_ID2:SIG2
Status message - AS

Good, configuration has been changed
EV_ID2:SIG3
Status message - AS

Simulation
EV_ID2:SIG4
Status message - AS
Device @1%d@/ @2%d@: ready to

start
EV_ID2:SIG5
Status message - AS
Device @1%d@/ @2%d@: ready to

operate
EV_ID2:SIG6
Status message - AS
Device @1%d@/@2%d@:
local operation/functional check
EV_ID2:SIG7
Status message - AS
Device @1%d@/@2%d@:
Device passivated
All other messages are not assigned.

1. ALARM_8P
2. NOTIFY_8P

185
Family: @System
5.30 MOD_HA: Monitoring device-specific diagnostics of HART field devices

Associated value
Block parameter
Subnet
Address
See also
5.30
MOD_HA: Monitoring device-specific diagnostics of HART field devices
5.30.1
Description of MOD_HA

FB 97
MOD_HA block I/Os (Page 191)
Area of application
The MOD_HA module reports diagnostic events of an HART field device that is connected to
a channel of an ET 200M HART module or ET 200iSP HART module. HART modules of ET
200iS are not supported. H systems support only the modules installed in switched racks.
Calling OBs
186
OB 1
Cyclic program
OB 82
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart

Family: @System
Use in CFC
function:
The block is installed downstream of the diagnostic block that is responsible for the HART
module.
LADDR (logical base address of the HART module) is configured.
The geographic addresses SUBN1_ID, SUBN2_ID, RACK_NO, SLOT_NO, and CHAN_NO
(channel number of the HART module to which the HART field device is connected) are
configured.
The CPU_DIAG structures of the OB_BEGIN block are interconnected
The block inputs are interconnected with the outputs EN_SUBx (x = number of the DP
master system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the
SUBNET block, and EN_Mxx (xx = module number) of the RACK block and MODE with
OMODE_xx of the diagnostic block.
The DXCHG output parameter is interconnected with the following channel block at the
DataXchg parameter.
The O_MS output parameter is interconnected with the following channel block at the MS
parameter.

Block MOD_HA analyzes events relating to a HART field device acyclically. ALARM_8P is
used to report these events. The message function can be disabled.
The block is enabled to run by the higher-level RACK block. By default, MOD_HA requires
synchronous diagnostic data in OB 82 (additional alarm information with SFB 54 call by
OB_BEGIN). With an ET 200iSP HART module, the channel type 16#65 is generated during
diagnostics. Here, 2 bytes of diagnostics information are defined per channel of the module,
and the block signals the statuses of the 2nd bit of the 1st and 2nd byte for the relevant HART
field device.
Structure of byte 1 (ET 200iSP HART):
Bit
Meaning
Parameter assignment error (HART module)
HART communications error (HART module)
Readback error (HART module)
Short circuit (HART module)
Wire break (HART module)
No load voltage (HART module)
Overflow (HART module)
Underflow (HART module)
Structure of byte 2 (ET 200iSP HART):

187
Family: @System
Bit
Meaning
Primary variable outside limits (field device)
Secondary variable outside limits (field device)
Analog output saturated (field device)
Analog output current specified (field device)
More statuses available (field device)
Reserved for maintenance alarm (field device)
Reassignment the field device parameters
Malfunction of the field device
For an ET 200M with two-channel HART modules, channel type 16#61 or 16#63 is generated
during diagnostics. Bit 5 in byte 8 for channel 0 and byte 9 for channel 1 in the additional alarm
information means "HART channel error". If bit 5 = TRUE, the additional diagnostic data is
read with SFB 52 (RDREC) as follows:
with data record 128 for channel 0
with data record 129 for channel 1
Diagnostic data records 128 (for channel 0) and 129 (for channel 1) have the same structure.
and return detailed HART diagnostic information on the previous transfer. The table below
shows the individual error messages/warnings.
Byte/Bit No.
0: general
1= Mod.
No. of (triggering) client,
Polling address (of HART transducer),
comm.
when module comm. no. =0
always 0 for monodrop
Channel
fault
HART
HART
HART
command
error
Comma
nd
rejected
0 = Not used
slave
communic
ation
device
status <> 0
(e.g.,
configuratio
n changed)
more status
channel
fault
2
parity
overrun
error in
response
error in
response
framing
error in
response
wrong
checksum
in response
Wrong char
timing
too
many
chars in
respons
e
wrong
telegram
timing
1: fault groups
= group error
then
bytes
(L+,
DrBr)
-
2: HART cf =
HART
"communicatio access
not
n faults"
possible
Field device
for module
3 to 6: time
stamp
Broadcast system time: Milliseconds (10s and 100s), seconds, minutes, and hours in two-digit BCD code.
If the timestamp function is not used: Content = 0
7: HART/
module
last HART or module command
8: HART ce
"Communication error bits" of "slave", (first status byte)
"Command response" list - no errors, but warnings
9: HART ds
Device status bits (second status byte)
Two HART status bytes are reserved in the HART protocol to display errors and warnings.
These are entered in diagnostic data records 128 and 129 unchanged. The meaning of the
HART status bytes is defined in the HART Standard.
188

Family: @System
First HART status byte (meaning depends on bit 7):
Bit 7 = 1: Communication error during the transmission of a HART command to the field
device
Bit 7 = 0: Only warnings that the field device sends in response to a command
Bit 7/Bit No.
Either
parity error
overrun
in command error in
command
Bit 7 = 1:
HART
framing
error in
command
wrong
Reserved =
checksum
0
in command
too many
characters in
command
(undefin
ed)
(rx buffer
overflow)
"communication
error" from
module to field
device
or
The messages in bits 0 - 6 are coded as integers:
Bit 7 = 0:
0: No command-specific error
HART
1: Undefined
"response to a
command"
2: Invalid section
3: Transferred parameter too large
4: Transferred parameter too small
5: Too few data bytes received
6: Device-specific command error (rarely used)
7: In write-protected mode
8-15: Various meanings (see code commands)
16: Restricted access
28: Various meanings (see code commands)
32: Device is busy
64: Command not implemented
Code
8 *)
Commands
Alternative meanings
1,2,3,33,60,61,62,
"Update" error
110,34,55,64,48
set to nearest possible value,
35,65,36,37,43,52,45,46,67,68
Lower range limit too high,
"Update" being executed

9
"applied process" too high,

not in correct current mode
(fixed at 4 mA or 20 mA)
10
6,35,65,36,37,43,52
Multidrop is not supported

Lower range limit too low,
"applied process" too low,
11
35,65,40,45,46,66,67,68,53
Upper range limit too high,

In multidrop mode,
bad transmitter variable code
12
35,65,53,66,67,68
Upper range limit too low,

bad units code

189
Family: @System
Code
Commands
Alternative meanings
13
35,65,69
Both range limits outside the limit value,

bad transfer function code
14 *)
35,36,65,37
Span too limited,

"pushed" upper range limit outside the limit
15
65,66,67,68,69
Faulty code for the number of the analog output
28
65
bad code for the range unit

("range units code")
Second HART status byte: Device status of the HART field device in the event of a
communication error
(otherwise, byte = 0)
Bit No.
HART
device
status:
Malfunction
of the field
device
Reassignm
ent of
parameters:
Cold
restar
t
Further
status
available
Analog output
current
specified
Analog
output
saturated
Primary
variable
outside limits
"more
status"
("fixed)"
Nonprimary
variable
outside
limits
"field
device
status"
"configuratio
n changed
(CC)"
Process control messages are generated when "communication errors" and HART field device
errors (byte 9 <> 0) occur. Operating messages with acknowledgment are generated if bit 7 =
0 (byte 8) and the remaining bits <> 0. The last read data record 128 or 129 (depending on
the channel number) is written to the output structure DIAG_H.
Bytes 8 and 9 are evaluated and event messages generated in OB 1.
You will find additional information in "Message texts and associated values of MOD_HA
(Page 194)".
The MODE input is interconnected with the corresponding OMODE_xx output of the diagnostic
block. The module channel configurations set in HW Config are reported at these locations.
MODE (Page 341) is written to the low word of theOMODE (Page 351) output parameter. This
occurs only during startup or if you set ACC_MODE = TRUE. The current channel value status
is written to the most significant byte. If valid, OMODE = 16#80xxxxxx. The diagnostic block
contains the events that lead to a value status "invalid value due to higher-priority error"
(OMODE = 16#40xxxxxx), or to channel error (OMODE = 16#00xxxxxx).
Redundancy
The higher-level RACK block evaluates the redundancy of DP master systems operating in
an H system. Redundant HART field devices are not supported.
Error handling
A restart (OB 100) is reported via the LSB in byte 2 of the OMODE (Page 351) output.
190

Family: @System
ALARM_8P will be initialized.
Overload behavior
The MOD_HA block counts the OB 82 calls. The counter is reset in OB1. A diagnostic message
will not be generated if more than five OB 82 events occur before the cycle control point is
reached (OB 1). A "multiple diagnostic interrupt" message will not be generated, because the
diagnostic block performs this action.
Time response
Not available
Message response
MOD_HA reports diagnostic information from a HART field device by means of ALARM_8P or
NOTIFY_8P.

manual.
Message texts and associated values of MOD_HA (Page 194)
maintenance
5.30.2
I/Os of MOD_HA

191
Family: @System
Input parameters
I/O
Meaning
Type
CHAN_NO
Channel number
BYTE
DIAG_BUF
Entry in diagnostic buffer (relevant for maintenance personnel) BOOL
EN_MSG
1 = Enable message
BOOL
EV_ID
Message number
DWORD
LADDR
INT
MODE
Channel operating mode
DWORD
MS
Maintenance status
DWORD
MS_REQ
BOOL
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
(parameter)
Default
Output parameters
I/O
Meaning
Type
(parameter)
Default
CH_ACTIVE
Channel active
DWORD
16#00000000
CH_EXIST
Channel exists
DWORD
16#00000000
CH_OK
Channel OK
DWORD
16#00000000
DIAG_H
Diagnostic information of HART communication

channel
STRUCT
DM_ACTIVE
Fault delay
DWORD
16#0
DXCHG
DWORD
DWORD
EXT_STAT
DWORD
FS_ACTIVE
Flutter suppression
DWORD
16#00000000
MS_XCHG
DWORD
MSG_ACK
WORD
MSGSTAT
WORD
QERR
1 = program error
BOOL
O_MS
Maintenance status
DWORD

Byte 1: Reserved
Byte 2: Reserved
DXCHG1
192

Family: @System
I/O
Meaning
Type
De-
(parameter)
fault
OMODE
DWORD
QPERAF
BOOL
QREC_ERR
1 = Read diagnostic data error
BOOL
QREC_VAL
1 = Read diagnostic data
BOOL
STATUS
Read diagnostics status
DWORD
I/O
Meaning
In/out parameters
Type
(parameter)
Default
ACC_MODE
BOOL
CPU_DIAG
CPU diagnostics
STRUCT
DataXchg
Bit0 Byte 0: MS_Release
DWORD
Bit1 Byte0: FlutEn

Bit2 Byte0: Fault delay
Bit3 Byte0: Fault delay active
Bit4..Bit7 Byte0 Reserve
Byte 1 Reserve
Byte 2 Reserved
Byte3: FlutTmIn/DelMsgTm
DXCHG_IN
DWORD
MS_XCHG_IN
DWORD
Message texts and associated values of MOD_HA (Page 194)

193
Family: @System
5.30.3
Message texts and associated values of MOD_HA

Message block
Message no.
EV_ID
(ALARM_8P)
HART field device@1%d@/@2%d@/@3%d@/ S

@4%d@:
Communication errors

@4%d@:
Errors
HART field device@1%d@/@2%d@/@3%d@/ F

@4%d@:
Secondary var. outside range

@4%d@:
Primary var. outside range

@4%d@:
Analog value specified

@4%d@:
Analog value saturated

@4%d@:
Maintenance alarm

@4%d@:
Further status available
HART field device@1%d@/@2%d@/@3%d@/ SA

@4%d@:
Reassignment of parameters
HART field device@1%d@/@2%d@/@3%d@/ SA

@4%d@:
Cold restart
EV_ID1
(NOTIFY_8P)
194
Message
class
No message
No message
No message
No message
No message
No message

Family: @System
5.31 MOD_HA_PN: Monitoring Device-Specific Diagnostics of HART Field Devices

Message block
ALARM_8P
Associated
value
Block
parameter
Meaning
EV_ID
SUBN_ID
RACK_NO
SLOT_NO
Slot number (byte)
CHAN_NO
Channel error text number
SUBN_ID
RACK_NO
Rack/station number
SLOT_NO
CHAN_NO
EV_ID1
If SUBN1_ID = 16#FF, the associated value is substituted with SUBN2_ID.
See also
5.31
MOD_HA_PN: Monitoring Device-Specific Diagnostics of HART Field

Devices
5.31.1
Description of MOD_HA_PN

FB 200
I/Os of MOD_HA_PN (Page 195)
Area of application
The MOD_HA_PN module reports diagnostic events of an HART field device that is connected
to a channel of an ET 200M HART module. HART modules of ET 200iS are not supported. H
systems support only the modules installed in switched racks.
5.31.2
I/Os of MOD_HA_PN

195
Family: @System
Input parameters
I/O
Meaning
Type
Default
CHAN_NO
Channel number
BYTE
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = Enable message
BOOL
EV_IDx
Message number ALARM_8P_x (x = 1 - 2, assigned

by the ES)
DWORD
LADDR
Logical address of the channel
INT
(parameter)
MODE
WORD
MS
Maintenance status
DWORD
MS_REQ
BOOL
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Meaning
Type
Default
CH_ACTIVE
Channel active
DWORD
16#00000000
CH_EXIST
Channel exists
DWORD
16#00000000
CH_OK
Channel OK
DWORD
16#00000000
DIAG_H
Diagnostic information of HART communication

channel
STRUCT
DM_ACTIVE
Fault delay
DWORD
16#0
DXCHG
DWORD
Output parameters
I/O
(parameter)

Byte 1: Reserved
Byte 2: Reserved
196
DXCHG1
DWORD
EXT_STAT
DWORD

Family: @System
I/O
Meaning
Type
Default
FS_ACTIVE
Flutter suppression
DWORD
16#00000000
MS_XCHG
DWORD
MSG_ACK
WORD
MSGSTAT
Status output of ALARM_8P_x (x = 1-2)
WORD
QERR
1 = program error
BOOL
O_MS
Maintenance status
DWORD
OMODE
DWORD
QPERAF
BOOL
QREC_ERR
1 = Read diagnostic data error
BOOL
QREC_VAL
1 = Read diagnostic data
BOOL
STATUS
Read diagnostics status
DWORD
(parameter)
In/out parameters
I/O
Meaning
Type
Default
ACC_MODE
BOOL
CPU_DIAG_PN
CPU diagnostics
STRUCT
DXCHG_IN
DWORD
MS_XCHG_IN
DWORD
(parameter)
Message texts and associated values of MOD_HA_PN (Page 198)

197
Family: @System
5.31.3
Message texts and associated values of MOD_HA_PN

Process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block
Message no. Default message text
Message
class
EV_ID1
(ALARM_8P)
HART field device@1%d@/@2%d@/@3%d@/

@4%d@:
Communication errors

@4%d@:
Error

@4%d@:
Secondary var. outside range

@4%d@:
Primary var. outside range

@4%d@:
Analog value specified

@4%d@:
Analog value saturated

@4%d@:
Maintenance alarm

@4%d@:
Further status available

Associated value
Block parameter
Data type
BYTE
Rack/station number
BYTE
Slot number
BYTE
Channel number
BYTE
Message block
Message class
EV_ID2
(ALARM_8P)

@4%d@: Reassignment of parameters
SA

@4%d@: Cold restart
SA
198
No message

Family: @System
5.32 MOD_MS: Monitoring up to 16 channels on ET200S/X motor starter modules with diagnostic functions
Message block
Message class
No message
No message
No message

Associated value
Block parameter
Data type
ID of the primary PN IO system
BYTE
Rack/station number
BYTE
Slot number
BYTE
Channel number
BYTE
5.32
MOD_MS: Monitoring up to 16 channels on ET200S/X motor starter

modules with diagnostic functions
5.32.1
Description of MOD_MS

FB 96
MOD_MS block I/Os (Page 203)
Area of application
The MOD_MS block the up to 16-channel motor starter modules with diagnostic capability (ET
200S). H systems support only the modules installed in switched racks.
Calling OBs
OB 1
Cyclic program
OB 82
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart

199
Family: @System
Use in CFC
function:
The MOD_MS block is installed in its runtime group downstream of the RACK block runtime
The MODE_xx, SUBN1_ID, SUBN2_ID, and SUBN_TYP inputs are configured.
The logical addresses LADDR and LADDR1 are configured.
are interconnected with the IN_OUT structures of the same name of MOD_MS.
MS parameter.

Block MOD_MS analyzes all events that affect a module and its channels acyclically. It
blocks. ALARM_8P is used to report these events. The message function can be disabled.
The block is enabled to run by the higher-level RACK block. The event to be evaluated is stored
in the CPU_DIAG start and diagnostic information of the OB_BEGIN block. There is a
MODE_xx input for each signal channel of the module. The module channel configuration data
created in HW Config is reported here. The function writes MODE_xx to the low word of the
Program execution error (OB 85) (output parameter QRACKF = TRUE)
Diagnostic interrupt (OB 82)
The following events in OB 82 will lead to a module error, and are indicated with 16#40xxxxxx
("higher-priority error") in OMODE. At the same time, output parameter QMODF = TRUE:
Overload
Short circuit
200

Family: @System
Error
Actuator OFF
Wire break
Safety-related shutdown
High limit exceeded
Low limit undershot
Missing supply voltage
Switching element overload
External error
ALARM_8P is used to report "module removed", "I/O access error", and the above "OB 82
error" events to WinCC.
(MOD_INF).
STRUCT.
You will find additional information in the "Service Information" section, and in the System
Structure of Channel-Specific Diagnostic Data reference manual.
Redundancy
The block supports segment redundancy of CPU 417H for distributed I/Os. To use this function,
you must configure the SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU
1) inputs with the numbers of the redundant segments. If there is no segment redundancy, the
remaining input must be set to the (default) value 16#FF.
MODE setting
Note
OMODE Structure

201
Family: @System

The existing channels on a module are displayed in the CH_EXIST output by setting a bit in
Addressing
Error handling
You will find additional information about this in the "Error information of output parameter
MSG_STAT (Page 353)" section.
Service Information
Of the motor starter module channels, only channel 0 is assigned the diagnostic function. The
error code is stored in CHDIAG00 to CHDIAG03. You will find additional information about this
in the ET 200S, Motor Starter Safety Technology SIGUARD; Diagnostics and Monitoring via
the User Program reference manual.
(Page 351) outputs.
Time response
Not available
202

Family: @System
Message response
MOD_MS reports module and motor-starter errors by means of ALARM_8P_1 and
ALARM_8P_2. The DELAY1 and DELAY2 inputs are used to delay the I/O access error
message. DELAY1 allows you to enter a time in seconds for which the block will wait for a
higher-priority error (rack failure or removal/insertion) following a program execution error (OB
85) before it outputs the message. DELAY2 determines the number of seconds the block waits
after the higher-priority error has been reported outgoing until it outputs the queued I/O access
error as well. Both values are set to 2 seconds by default.

manual.
Message texts and associated values of MOD_MS (Page 205)
maintenance
5.32.2
I/Os of MOD_MS
Input parameters
I/O
(parameter)
Meaning
Data type
Default
DELAY1
Alarm delay 1 (s)
INT
DELAY2
Alarm delay 2 (s)
INT
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = enable message
BOOL
EV_IDx
Message number x
DWORD
LADDR
Logical address of the input channels
INT
LADDR1
Logical address of the output channels
INT

203
Family: @System
I/O
(parameter)
Meaning
Data type
Default
MODE_xx
WORD
MS
Maintenance status
DWORD
MS_REQ
BOOL
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
I/O
(parameter)
Meaning
Data type
Default
CH_ACTIVE
Channel active
DWORD
16#000000
00
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
DIAG_INF
STRUCT
DXCHG_xx
DWORD
Output parameters
Byte 0:
Byte 1: Reserved
Byte 2: Reserved
204
EXT_STAT
DWORD
MOD_INF
STRUCT
MSG_ACKx
Message acknowledgment x
WORD
MSGSTATx
Message error information x
WORD
O_MS
Maintenance status
DWORD
OMODE_xx
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QPERAF
BOOL
QRACKF
1 = failure of the rack
BOOL

Family: @System
In/out parameters
I/O
(parameter)
Meaning
Data type
Default
ACC_MODE
BOOL
CPU_DIAG
STRUCT
RAC_DIAG
STRUCT
Message texts and associated values of MOD_MS (Page 205)
5.32.3
Message texts and associated values of MOD_MS

Message block
ALARM_8P
Message
number
Block
parameter
Message class
EV_ID1
QMODF
Module @1%d@/@2%d@/@3%d@:
Removed
QPERAF
Module @1%d@/@2%d@/@3%d@:
Access error
Module @1%d@/@2%d@/@3%d@:
@4W%t#MOD_MS_TXT@
EV_ID2
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
@4W%t#MOD_MS_TXT@
Module @1%d@/@2%d@/@3%d@:
Short-circuit
Module @1%d@/@2%d@/@3%d@:
Overload
Module @1%d@/@2%d@/@3%d@:
Error
Module @1%d@/@2%d@/@3%d@:
High limit exceeded
Module @1%d@/@2%d@/@3%d@:
Low limit undershot
Module @1%d@/@2%d@/@3%d@:
Parameter assignment error
Module @1%d@/@2%d@/@3%d@:
Actuator OFF

205
Family: @System
Message block
ALARM_8P
Message
number
Block
parameter
Message class
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
External error
Module @1%d@/@2%d@/@3%d@:
Switching element overload
Module @1%d@/@2%d@/@3%d@:
Missing supply voltage
You will find the message texts and their text numbers in "Text library for MOD_MS
(Page 369)".

Message block Associate
ALARM_8P
d
value
Block
parameter
Meaning
EV_ID1
SUBN_ID
RACK_NO
SLOT_NO
Slot number (byte)
Text number (message 5) of MOD_MS_TXT
SUBN_ID
RACK_NO
SLOT_NO
Slot number (byte)
EV_ID2
See also
206

Family: @System
5.33 MOD_SWT: Monitoring of Switch blocks with diagnostics functions
5.33
MOD_SWT: Monitoring of Switch blocks with diagnostics functions
5.33.1
Description of MOD_SWT

FB 149
MOD_SWT block I/Os (Page 208)
Area of application
The MOD_SWT block creates the device-specific diagnostics function for blocks of the Switch
type.
The following events are processed in the MOD_SWT and the status messages reported in
WinCC:
SwitchType
FbSwtMMS
Message text
Message class in
WinCC
Maintenance
State
Status (for each

interconnectable output)
Backward
SA
00
16#80
Off
SA
00
16#80
Forward
SA
00
16#80
Overload warning
06
16#68
Error
07
16#00
Warning
06
16#68
Calling OBs
The cyclic OB 1 and OB 100.
Use in CFC
function:
The block is installed when the corresponding SlaveFamily 2 object exists
Further interconnection takes place in the same way as for the existing MODPAL/X0 blocks
of the PCS 7 Basis Library
The corresponding inputs are read out of HW Config and configured.
The block is interconnected with the corresponding Switch block through the DXCHG_00,
OMODE_00 and O_MS parameters.

207
Family: @System
Initialization of the ALARM_8P blocks and of the NOTIFY_8P blocks.
Message response
The block reports errors using ALARM_8P and NOTIFY_8P.
OB no.
Start event
Message
Cyclic processing
Have the ALARM_8P/NOTIFY_8P outputs/messages

updated, if necessary
100
Restart
MODE behavior
The block is informed by the "MODE" input about which function block or device type is involved.
5.33.2
I/Os of MOD_SWT
I/Os
Input parameters
208
I/O (parameter)
Meaning
Type
Default
EN_MSG
1 = Enable message
BOOL
EV_ID1
Message number 1
DWORD
16#00
EV_ID2
Message number 2
DWORD
16#00
MS
Maintenance status
DWORD
16#00
MS_REQ
BOOL
LINK_ADR
Link address
BYTE
PADP_ADR
BYTE
16#00
SUBN1_ID
BYTE
16#FF
SUBN2_ID
BYTE
16#FF

Family: @System
In/out parameters
I/O (parameter)
Meaning
Type
CPU_DIAG
Struct (see
OB_BEGIN)
RAC_DIAG
Struct (see
OB_DIAG1)
Output parameters
I/O (parameter)
Meaning
Type
Default
CH_ACTIVE
Channel active
DWORD
16#00000000
CH_EXIST
Channel exists
DWORD
16#00000000
CH_OK
Channel OK
DWORD
16#00000000
DXCHG_00
DWORD
16#00
DXCHG1
DWORD
DXCHG1_00
DWORD
EXT_STAT
Release for maintenance - extended

status
DWORD
16#00
EXT_STAT_A
DWORD

Error
Error message is active
BOOL
MS_XCHG_00
Maintenance Status - Data exchange

channel
DWORD
MSGSTAT1
WORD
16#00
MSGSTAT2
WORD
16#00
MSG_ACK1
WORD
16#00
MSG_ACK2
WORD
16#00
OMODE_00
Value status of the PA field device
DWORD
16#00
O_MS
Maintenance status
DWORD
16#00
Overload
Overload message is active
BOOL
QERR
1 = program error
BOOL
QRACKF
BOOL
Warning
Warning message is active
BOOL

209
Family: @System
5.33.3
Message texts and associated values of MOD_SWT
Messaging
Message block
Class
Event
EV_ID1:SIG1

maintenance alarm
EV_ID1:SIG2
AS process control message - error

maintenance demanded
EV_ID1:SIG3
Preventive maintenance - general

EV_ID1:SIG6

Failure
EV_ID2:SIG2
Status message - AS

EV_ID2:SIG3
Status message - AS

Simulation
EV_ID2:SIG6
Status message - AS
Device @1%d@/@2%d@:
local operation/functional check
EV_ID2:SIG7
Status message - AS
Device @1%d@/@2%d@:
Device passivated
EV_ID2:SIG8
Status message - AS
Device @1%d@/@2%d@ @4W

%t#MOD_SWT_TXT@
1 Running forwards
2 Stationary
3 Running backwards
All other messages are not assigned.

1. ALARM_8P
2. NOTIFY_8P

Associated value
Block parameter
Subnet
Address
See also
210

Family: @System
5.34 MOD_PAL0: Diagnosing a DPV0 PA slave (via DP/PA coupler downstream of a DP/PA link DPV1)
5.34
MOD_PAL0: Diagnosing a DPV0 PA slave (via DP/PA coupler

downstream of a DP/PA link DPV1)
5.34.1
Description of MOD_PAL0

FB 99
MOD_PAL0 block I/Os (Page 213)
Area of application
Block MOD_PAL0 reports the maintenance status of a PA field device that is used as a DPV0
slave downstream of a DP/PA link DPV1. The PA field devices must conform to the PROFIBUS
V3.0 profile.
Calling OBs
Use in CFC
function:
The block is integrated in the run sequence upstream of block PA_x
The SUBN1_ID, SUBN2_ID, RACK_NO, SLOT_NO, PADP_ADR, PROF_V30 inputs are
configured.
The block inputs are interconnected with the following outputs:
Output PA_DIAG of block PADP_L10
OMODEx outputs of block PADP_L10
QMODF and QPERAF outputs of block PADP_L10
with output structure RAC_DIAG of block OB_DIAG1
input QC_x with PA field device icon

211
Family: @System
MS parameter.
Note
The CFC function "Generate module drivers" can only be used if the PA field device
belongs to slave family 12.

Block MOD_PAL0 analyzes all events that affect the status of a PA field-device slot cyclically.
With modular PA field devices, the statuses of the slots are combined to form one status. The
acyclic diagnostic events of a PA field device are acquired by the PADP_L10 block. It then
stores them in the PA_DIAG parameter. The PA field-device status and the diagnostic
information are evaluated, and entered in the MS parameter.
For additional information on this, refer to the section:
"PA field device status and diagnostic information (Page 357)".
The statuses are generated with ALARM_8P for messages requiring acknowledgment, and
with NOTIFY_8P for those not requiring acknowledgment. The message function can be
disabled.
Input PROF_V30 must be set to zero if the PA field device used does not conform to profile
3.0 (this is done by the "Generate module drivers" CFC function).
For a diagnostic event, the block reports "Device xx: uncertain diagnosis".
The failure of a PA field device is identified in the upstream block OB_DIAG1, and is reported
via the RAC_DIAG structure. A message "Device xx: Failure" is also generated.
Redundancy
The higher-level block evaluates the redundancy of DP master systems operating in an H
system.
Error handling
Initialization of ALARM_8P and NOTIFY_8P.
Time response
Not available
212

Family: @System
Message response
The block reports by means of ALARM_8P and NOTIFY_8P.
OB no.
Start Event
Message
Cyclic processing
Have the ALARM_8P/NOTIFY_8P outputs/messages updated, if

necessary
100
Restart

manual.
Message texts and associated values for MOD_PAL0 (Page 215)
maintenance
5.34.2
I/Os of MOD_PAL0
I/Os
Input parameters
I/O (parameter)
Meaning
Type
Default
EN_DIAG
BOOL
EN_MSG
1 = Enable message
BOOL
EV_IDx
Message number x
DWORD
MODE_xx
Value status PA field device (xx = channel 16 to 31)
DWORD

213
Family: @System
I/O (parameter)
Meaning
Type
Default
MODF
1 = PA slave error
BOOL
MS
Maintenance status
DWORD
MS_REQ
BOOL
NUM_CHN
Number of channels of the PA device
INT
PA_DIAG
PA field device diagnostic information
DWORD
PADP_ADR
BYTE
PERAF
BOOL
PROF_V30
1 = PA slave profile V3.0
BOOL
QC_xx
Status of PA field device (xx = channel 16 to 31)
BYTE
RACK_NO
Number of the DP link
BYTE
SLOT_NO
Slot number of the PA field device in the DP link
BYTE
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Default
Output parameters
I/O
Meaning
Type
B_QC
Bit-granular status (channel 0 to 31)

of the PA field device
STRUCT
CH_ACTIVE
Channel active
DWORD
16#000
00000
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
DXCHG_xx
0
0

Byte 1: Reserved
Byte 2: Reserved
DXCHG1
DWORD
DXCHG1_xx
DWORD
DWORD
DWORD
(xx = 00 - 31)
EXT_STAT

EXT_STAT_A

214
FS_ACTIVE
Flutter suppression
DWORD
16#000
00000
MS_XCHG_00
DWORD
MSG_ACKx
WORD
MSGSTATx
WORD

Family: @System
I/O
Meaning
Type
Default
MS_XCHG_xx
DWORD
(xx = 00 - 31)
O_MS
Maintenance status
DWORD
OMODE_xx
Operating mode slot (xx = Slot 16 to 31)
DWORD
QERR
1 = program error
BOOL
QMODF
1 = PA slave error
BOOL
QPERAF
BOOL
QRACKF
BOOL
In/out parameters
I/O
Meaning
Type
Default
RAC_DIAG
STRUCT
Message texts and associated values for MOD_PAL0 (Page 215)
PA field device status and diagnostic information (Page 357)
5.34.3
Message texts and associated values of MOD_PAL0

Message class
EV_ID1
(ALARM_8P)
Device @1%d@/ @2%d@/@3%d@: Bad,

maintenance alarm
Device @1%d@/ @2%d@/@3%d@:


Device @1%d@/ @2%d@/@3%d@: Access

error
Device @1%d@/ @2%d@/@3%d@:

Uncertain diagnostics
No message
No message

215
Family: @System
Message class
EV_ID2
(NOTIFY_8P)

changes to fail-safe position
SA

configuration has been changed
SA
Device @1%d@/ @2%d@/@3%d@:

Simulation
SA
Device @1%d@/ @2%d@/@3%d@:

SA
Device @1%d@/ @2%d@/@3%d@: Bad,

SA
Device @1%d@/ @2%d@/@3%d@: Local

SA
Device @1%d@/ @2%d@/@3%d@: Device

passivated
SA
Device @1%d@/ @2%d@/@3%d@: @4W

%t#MOD_PAL0_TXT@
SA

Message block
Associated
value
Block
parameter
Meaning
EV_ID1
(ALARM_8P)
SUBN_ID
RACK_NO
PADPADR
PA field device address (byte)
SUBN_ID
RACK_NO
PADPADR
EV_ID2
(NOTIFY_8P)
Text number MOD_PAL0
If the PA field device is connected downstream from an inactive DP/PA-Link V1and SUBN1_ID
= 16#FF, the associated variable is substituted by SUBN2_ID.
You will find the message texts and their text numbers in
"Text library for MOD_PAL0 (Page 360)".
See also
216

Family: @System
5.35 MOD_PAX0: Diagnosing a DPV0 PA slave (via DP/PA coupler with connection to a DP master system)
5.35
MOD_PAX0: Diagnosing a DPV0 PA slave (via DP/PA coupler with

connection to a DP master system)
5.35.1
Description of MOD_PAX0

FB 112
MOD_PAX0 block I/Os (Page 219)
Area of application
Block MOD_PAX0 reports the maintenance status of a PA field device that is used as a DPV0
slave in a DP master system. The PA field devices must conform to the PROFIBUS V3.0 profile.
Calling OBs
Use in CFC
function:
The block is integrated in the run sequence upstream of the PA_x block.
The inputs SUBN1_ID, SUBN2_ID, PADP_ADR and PROF_V30 have parameters
assigned.
The inputs are interconnected with the following outputs:
Output PA_DIAG of block PADP_L10
OMODEx outputs of block PADP_L10
QMODF and QPERAF outputs of block PADP_L10
with output structure RAC_DIAG of block OB_DIAG1
Input QC_x is interconnected with the PA field device status icon.
Output OMODExx is interconnected with the MODE input of the PA_x block.
MS parameter.

217
Family: @System
Note
The CFC function "Generate module drivers" can only be used if the PA field device belongs
to slave family 12.

Block MOD_PAX0 analyzes all events relating to the status of a PA field device slot cyclically.
With modular PA field devices, the statuses of the slots are combined to form one status. The
acyclic diagnostic events of a PA field device are acquired by the PADP_L10 block. It then
stores them in the PA_DIAG parameter. The PA field-device status and the diagnostic
information are evaluated, and entered in the MS parameter.
You will find additional information in the "PA field device status and diagnostic information
Input PROF_V30 must be set to zero if the PA field device used does not conform to profile
3.0 (this is done by the "Generate module drivers" CFC function).
In the event of a diagnostic event, the block reports "PA field device diagnostics".
There is an input (MODE_xx (Page 341)) for each slot (module) on the PA field device that is
used to read in configuration settings made for the PA field device slots (module) in HW Config.
This occurs only during startup or if you set ACC_MODE = TRUE. The current slot value status
16#80xxxxxx. The following events lead to the value status "Invalid value due to higher-priority
error" (OMODE_xx = 16#40xxxxxx):
MODE setting for PA profiles

You will find additional information in "PA_MODE settings (Page 351)".
Note
OMODE Structure
Redundancy
system.
218

Family: @System
Error handling
Initialization of ALARM_8P and NOTIFY_8P
Time response
Not available
Message response
The block uses ALARM_8P and NOTIFY_8P
OB no.
Start Event
Message
Cyclic processing
Repeat the update of ALARM_8P outputs/messages, if necessary
100
Restart

manual.
Message texts and associated values for MOD_PAX0 (Page 222)
maintenance
5.35.2
I/Os of MOD_PAX0
I/Os

219
Family: @System
Input parameters
I/O
(parameter)
Meaning
Type
Default
EN_MSG
1 = Enable message
BOOL
EV_IDx
Message number x
DWORD
MODE_xx
Value status PA field device (xx = channel 16 to 31)
DWORD
MODF
1 = PA slave error
BOOL
MS
Maintenance status
DWORD
MS_REQ
BOOL
NUM_CHN
Number of channels of the PA device
INT
PA_DIAG
DWORD
PADP_ADR
BYTE
PERAF
BOOL
PROF_V30
BOOL
QC_xx
Status of PA field device (xx = channel 16 to 31)
BYTE
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Default
Output parameters
I/O
(parameter)
Meaning
Type
B_QC
Bit-granular status (channel 0 to 31) of the PA field

device
STRUCT
CH_ACTIVE
Channel active
DWORD
16#00000
000
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
DWORD
DWORD
DWORD
DWORD
DXCHG_xx

Byte 1: Reserved
Byte 2: Reserved
DXCHG1
DXCHG1_xx
(xx = 00 - 31)
EXT_STAT
220

Family: @System
I/O
(parameter)
Meaning
Type
Default
EXT_STAT_A
DWORD

FS_ACTIVE
Flutter suppression
DWORD
16#00000
0000
MS_XCHG_00
DWORD
MS_XCHG_xx
DWORD
(xx = 00 - 31)
MSG_ACKx
WORD
MSGSTATx
WORD
O_MS
Maintenance status
DWORD
OMODE_xx
Operating mode slot (xx = Slot 16 to 31)
DWORD
QERR
1 = program error
BOOL
QMODF
1 = PA slave error
BOOL
QPERAF
BOOL
QRACKF
BOOL
In/out parameters
I/O
(parameter)
Meaning
Type
Default
RAC_DIAG
STRUCT
Message texts and associated values for MOD_PAX0 (Page 222)
PA field device status and diagnostic information (Page 357)

221
Family: @System
5.35.3
Message texts and associated values of MOD_PAX0

Block
parameter
Message
class
EV_ID1
(ALARM_8P)

Bad, maintenance alarm



Access error

Undefined diagnostics

Failure
No
message
No
message

Good, changes to fail-safe position
SA

SA

Simulation
SA

SA

SA
Device @1%d@/ @2%d@: Local

SA
Device @1%d@/@2%d@:
Device passivated
SA
Device @1%d@/ @2%d@:@3W

%t#MOD_PAX0_TXT@
SA
EV_ID2
(NOTIFY_8P)
222

Family: @System
5.36 OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics

Message block
Associated
value
Block
parameter
Meaning
EV_ID1
(ALARM_8P)
SUBN_ID
PADPADR
SUBN_ID
PADPADR
EV_ID2
(NOTIFY_8P)
Text number MOD_PAXL0
If SUBN1_ID = 16#FF, the associated value is substituted with SUBN2_ID.

You will find the message texts and their text numbers in the section:
"Text library for MOD_PAL0 (Page 360)" section.
See also
5.36
OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics
5.36.1
Description of OB_BEGIN

FB100
OB_BEGIN block I/Os (Page 227)
Area of application
Block OB_BEGIN is used for CPU diagnostics of the automation system (AS). By installing the
block in CFC, the system creates all acyclic tasks (OBs) in which the driver blocks of PCS 7
Basis Library are executed.

223
Family: @System
Calling OBs
OB 1
Cyclic processing
OB 55
Status interrupt (only if a DP/PA slave is required)
OB 56
Update interrupt (only if a DP/PA slave is required)
OB 57
Vendor-specific alarm (only if a DP/PA slave is required)
OB 70
OB 72
OB 80
Timeout error
OB 81
Power supply error
OB 82
OB 83
Remove/insert interrupt
OB 84
CPU hardware error (only for CPU with this function)
OB 85
OB 86
Rack failure
OB 88
Stop avoidance
OB 100
Restart
OB 121
Programming error
OB 122
I/O access error
Use in CFC
With the "Generate module drivers" CFC function, the OB_BEGIN block is automatically
installed in the OBs listed above.

Block OB_BEGIN is used to report and display CPU events and statuses. It reads the start
information of the tasks (OBs), diagnostic data of the I/O and enables the relevant blocks for
processing on the basis of the start events.
OB_BEGIN reads the start information of SFC 6 (RD_SINFO) or SFB 54 (RALRM) to identify
the OB in which it is currently running.
If this information is not available, the block reads the logical basic address from the start
information and converts it into the geographic address. This is available at the relevant OBs
of the output structure CPU_DIAG the lower-level blocks can also access. On the basis of the
geographic address, OB_BEGIN enables the relevant SUBNET blocks for further evaluation
of the start information.
In the case of a diagnostic event (OB 82), the diagnostic data are simultaneously written to
the CPU_DIAG.OB 82 structure along with the start information, using SFB54. Diagnostic
(alarm) information of a length exceeding 59 bytes must contain the call of the relevant driver
blocks.
In H systems, the current status of the two H CPUs is read from the system status list 71
(SSL71) in OB 100. A detailed description of the SSL71 appears in the reference manual titled
224

Family: @System
System Software for S7-300/400 System and Standard Functions. The statuses of
SSL_71.MASTER_0/1 and SSL_71.CPU_ERR_0/1 are updated in OB 72.
OB_BEGIN provides the diagnostic information of OB 55, OB 56 and OB 57 to the downstream
blocks in its output structure CPU_OB_5X.
The block reports diagnostic events of an OB 88 block.
All OB 88 events are incoming events. OB 1 generates the relevant event message exiting
state after a delay of approximately 10 seconds in order to allow the reporting of a new OB 88
event.
Error handling
Block OB_BEGIN evaluates error information from ALARM_8P and writes it to the relevant
output parameters.
If the block installation sequence OB_BEGIN, xx blocks, ..., OB_END is not observed in an
OB, the message "OB_END installation error, no OB 8x processing" will be output and QERR
= TRUE set. In this case, the acyclic OBs do not evaluate the data. The downstream blocks
will not be enabled.
Error information at output parameter STATUS of SFB 54 (RALRM) is handled as follows:
The values 16#8096, 16#80A7, 16#80C0, 16#80C2, 16#80C3 or 16#80C4 at STATUS[2]
and STATUS[3] indicate temporary errors. STATUS[3] of the corresponding OB will be set
in the structure CPU_DIAG = 16#C4. Downstream blocks can read access the diagnostic
data asynchronously.
After any other error event, SFC 6 (RD_SINFO) reads the startup information once again
and the message "OB_BEGIN diagnostic error RALRM STATUS = xxxxxxxx" is output.
OB 1 generates the message exiting state once a delay of approximately 10 seconds has
expired.
Block OB_BEGIN initializes the messages of ALARM_8P. In H systems (CPU_DIAG.H_MODE
= TRUE), the current status of the two H CPUs is determined by reading SSL71 (see "Function
and method of operation").
Overload Behavior
Messages exiting state associated with OB 121, OB 122 and OB 88 are generated subject to
a delay of approx. 10 seconds. This on the one hand prevents blocking of the WinCC
connection due to a high message transfer volume of these OBs. On the other hand, OB events
may be due to the delay.
Time response
Not available

225
Family: @System
Message response
ALARM_8P multiple instances are only called if OB_BEGIN is to output a message. It is only
at this point that previously acknowledged messages are updated by the corresponding
ALARM block. If the connection to WinCC is down, each ALARM_8P can hold up to two
message statuses of its event ID.
The CPU generates a programming error (OB 121) only as an incoming event. OB 1 resets
the relevant message to status exiting state. In order to avoid an excessive number of
programming error messages, these will not be reported as outgoing until a delay time of 10
seconds has expired. The same applies to I/O access errors (OB 122) and OB 88 events.
OB
Start Event
Message
OB 1
Cyclic processing
Outgoing message with 10 s delay: Timeout

(OB 80/OB 84)
Program execution error (OB 80)
Programming error (OB 121)
Write I/O access error (OB 122)
Read I/O access error (OB 122)
Error code B#16#71: Nested stack error (OB 88)
Error code B#16#72: Master control relay stack error (OB 88)
Error code B#16#73: Synchronous error nesting depth exceeded (OB 88)
Error code B#16#74: U stack nesting depth exceeded in priority class stack
(OB 88)
Error code B#16#75: B stack nesting depth exceeded in priority class stack
(OB 88)
Error code B#16#76: Local data allocation error (OB 88)
Error code B#16#78: Unknown opcode (OB 88)
Error code B#16#7A: Code length error (OB 88)
OB 72
CPU redundancy loss
CPU redundancy loss/return
OB 80
Timeout error
Incoming message on timeout:

Cycle time exceeded
OB request: OBxx is busy
OB request: Overflow PRIOxx
TOD interrupt xx expired
OB 84
CPU hardware error
Interface error entering/exiting state;

Memory error detected and corrected by operating system.
Accumulation of detected and corrected memory errors.
Error in PC operating system.
Performance of an H-Sync coupling impaired.
Multiple-bit memory error detected and corrected.
OB 85
Incoming message on program-execution error:

OBxx not loaded
Access-error error xx: ...
226

Family: @System
OB
Start Event
Message
OB 88
Stop avoidance
Incoming message on OB 88 events:

Error code B#16#71: Nested stack error
Error code B#16#72: Master control relay stack error
Error code B#16#73: Nesting depth exceeded on synchronization errors
Error code B#16#74: U-stack nesting depth exceeded in the priority class
stack
Error code B#16#75: B-stack nesting depth exceeded in the priority class
stack
Error code B#16#76: Local data allocation error
Error code B#16#78: Unknown opcode
Error code B#16#7A: Code length error
OB 100
Restart
OB 121
Programming error
Programming error incoming
OB 122
I/O access error
Read I/O access, incoming

Write I/O access, entering state

manual.
OB_BEGIN faceplate
If no asset management is used in the project, the "OB-BEGIN" block icon is used to display
avoidance of stop.
5.36.2
I/Os of OB_BEGIN

227
Family: @System
Input parameters
I/O
(parameter)
Meaning
Data type
Defau
lt
DIAG_BUF

personnel)
BOOL
EN_MSG
Reserve
BOOL
EV_IDx

DWORD
MS
Maintenance status
DWORD
SUB0IDxx
DP master system 1 IDxx (xx = 00 - 15)
BYTE
255
SUB1IDxx
DP master system 2 IDxx (xx = 00 - 15)
BYTE
255
I/O
(parameter)
Meaning
Data type
Defau
lt
Output parameters
CPU_DIAG
STRUCT
CPU_OB_4X
Start information OB 40 - OB 47
STRUCT
CPU_OB_5X
Start information OB 55, OB 56, OB 57
STRUCT
CPU_OB_6X
STRUCT
CPUERR_0
1 = CPU error in rack 0 *)
BOOL
CPUERR_1
BOOL
EN_SUBx
Enable SUBNET x (x = 0 - 15)
BOOL
MASTER_0
1 = Master CPU in rack 0
BOOL
MASTER_1
BOOL
MSGSTATx
STATUS output of ALARM_8P_x (x = 1 - 4)
WORD
O_MS
Maintenance status
DWORD
QERR
1 = processing error
BOOL
QMSGERx
Error output of ALARM_8P_x (x = 1 - 4)
BOOL
SZL_71
System structure: SZL71
STRUCT
The structure of the CPU_DIAG is integrated as OUT in the OB_BEGIN block, and as IN_OUT
in all other blocks with this I/O.
*) You will find additional information about CPU errors in the CPU Manual.
228

Family: @System
5.36.3
Message texts and associated values of OB_BEGIN

Message block
ALARM_8P
Message
number
OB no.
Message
class
EV_ID1
OB 85
OB @7%d@ not loaded
No
message
OB 84
Interface error
Error installing OB_BEGIN/OB_END: No

OB@2%d@ processing of stack @1%d@
OB 85
Program execution error: @7%d@:

@10%2s@@8%d@/@9%d@
OB 122
I/O read access error: @4%2s@@5%d@

Address: @6%d@
OB 122
I/O write access error: @4%2s@@5%d@

Address: @6%d@
OB 84
Performance of an H-Sync coupling impaired S
Messages 1, 4, 5, 6, 7 and 8 are only incoming events. They are reset to "outgoing" status
during the normal run sequence (OB 1) of the block.
Associated Values of ALARM_8P with EV_ID1

Process control messages are generated with EV_ID1 and associated values via ALARM_8P.
The table below shows how the associated values are assigned to the block parameters.
Message block
ALARM_8P
Associated value Block parameters
Data type
EV_ID1
CPU_DIAG.OB_S_NUM_CNT
BYTE
TINFO_TOP_SI_NUM
BYTE
OB 72_supp_info 1
WORD
OB 122_BLK_TYP
WORD
OB 122_BLK_NUM
WORD
OB 122_MEM_ADDR
WORD
OB 85_supp_info 1
WORD
OB 85_HW_supp_info 2_3
WORD
OB 85_LW_supp_info 2_3
WORD
10
OB 85_DKZ2_3
WORD

229
Family: @System
Message block
ALARM_8P
Message
number
OB no.
Message class
EV_ID2
OB 80
Net consumption of all OBs exceeds

max. limit
OB 80
Emergency operation, cyclic OBs are

used
OB 80
Priorities of the cyclic OBs not PCS 7

conform
OB 84
Memory error detected and corrected

by operating system.
OB 84
Accumulation of detected and

corrected memory errors
OB 84
Error in PC operating system
OB 121 Programming error @1%d@:

@2%2s@@5%d@ /@6%d@/
@4%d@/@3%d@
OB 84
Multiple-bit memory error detected

and corrected
Messages 1 to 3 are generated in CPU_RT (Page 27) and forwarded to OB_BEGIN.

Messages 4, 5, 7 and 8 are only incoming events. They are reset to "outgoing" status during
the normal run sequence (OB 1) of the block.
Message 7 is to be interpreted as follows, in accordance with the error code number before
the colon:
OB 121_BLK_TYP/OB 121_BLK_NUM/OB 121_PRG_ADDR/OB 121_FLT_REG/
OB 121_RESERVED_1.
This is described in the reference manual titled System Software for S7-300/400 System and
Standard Functions.
Example: 10.05.00 10:30:45 Programming error 35: FB44/1234/5/9

230
Message block
ALARM_8P
Associated
value
Block parameters
Data type
EV_ID2
OB 121_SW_FLT
BYTE
OB 121_BLK_TYP
WORD
OB 121_RESERVED_1
BYTE
OB 121_FLT_REG
WORD
OB 121_BLK_NUM
WORD
OB 121_PRG_ADDR
WORD

Family: @System
ALARM_8P
number
OB
no.
Messag
e
class
EV_ID3
OB 80 Cycle time exceeded: @1%d@ms OB@2%d@
OB 80 OB request: OB3x still being processed
OB 80 TOD interrupt OB @3%d@ expired (TOD jump)
OB 80 TOD interrupt OB @4%d@ expired (Stop/Run)
OB 80 OB request: Overflow PRIO @5%d@
OB 80 Synchronous cycle interrupt-Timing error:

OB@6%d@ PRIO @7%d@
OB 80 Interrupt loss: OB@8%d@ PRIO @9%d@
OB 80 CiR synchronization time: @10%d@ ms
Message 2 is generated in CPU_RT (Page 27) and forwarded to OB_BEGIN.

Messages 1 to 8 are only incoming events. They are reset to "outgoing" status during the
normal run sequence (OB 1) of the block.

Message block
ALARM_8P
Associated
value
Block parameters
Data type
EV_ID3
Cycle time (OB 80_supp_info 1)
WORD
Cause OB (OB 80_1st byte supp_info 2_3)
BYTE
WORD
WORD
Priority class (OB 80_2nd byte supp_info 2_3)
BYTE
BYTE
BYTE
BYTE
BYTE
10
WORD
Message block
ALARM_8P
Message
number
Message class
EV_ID_4
OB 88(@6W%t#OB_BEGIN_TXT@):
OB@1%d@ PRIO@2%d@ @3%2s@@4%d@ /
@5%d@

No message
231
Family: @System
Message block
ALARM_8P
Message
number
Message class
No message
No message
No message
No message
No message
No message

Message block
ALARM_8P
Associated
value
Meaning
EV_ID4
Cause OB (M_OB 88.FLT_OB)
Priority class (M_OB 88.FLT_OB_PRIO)
Block type (M_OB 88.BLK_TYP)
Block number (M_OB 88.FLT_NUM)
MC7 command causing error

Relative address (M_OB 88.FLT_ADDR)
Error number in OB_BEGIN_TXT (M_OB 88.T_OB 88)
Status RALRM
You will find the message texts and their text numbers in "Text library for OB_BEGIN
(Page 371)".
See also
232

Family: @System
5.37 OB_BEGIN_PN: CPU diagnostics
5.37
OB_BEGIN_PN: CPU diagnostics
5.37.1
Description of OB_BEGIN_PN

FB 130
I/Os of OB_BEGIN_PN (Page 233)
Area of application
Block OB_BEGIN_PN is used for CPU diagnostics of the automation system (AS). By installing
the block in CFC, the system creates all acyclic tasks (OBs) in which the driver blocks of PCS
7 Basis Library are executed.
5.37.2
I/Os of OB_BEGIN_PN
Input parameters
I/O
(parameter)
Meaning
Data type
Defa
ult
DIAG_BUF

personnel)
BOOL
EN_MSG
Reserve
BOOL
EV_IDx

DWORD
MS
Maintenance status
DWORD
SUB0IDxx
DP master system 1 IDxx (xx = 00 - 15)/PN IO system 1

(100-115)
BYTE
255
SUB1IDxx
DP master system 2 IDxx (xx = 00 - 15)/PN IO system 2

(100-115)
BYTE
255

233
Family: @System
Output parameters
I/O
(parameter)
Meaning
Data type
CPU_DIAG
STRUCT
CPU_DIAG_PN
System structure: CPU diagnostics (PN)
STRUCT
CPU_OB_4X
STRUCT
CPU_OB_5X
STRUCT
CPU_OB_5X_PN
STRUCT
CPU_OB_6X
STRUCT
CPUERR_0
BOOL
Defa
ult
CPUERR_1
BOOL
EN_SUBx
Enable SUBNET x (DP: x = 0 - 15/PN: x = 100-115))
BOOL
MASTER_0
BOOL
MASTER_1
BOOL
MSGSTATx
WORD
O_MS
Maintenance status
DWORD
QERR
BOOL
QMSGERx
Error output of ALARM_8P_x (x = 1 - 4)
BOOL
SZL_71
STRUCT
The structure of the CPU_DIAG is integrated as OUT in the OB_BEGIN block, and as IN_OUT
in all other blocks with this I/O.
*) You will find additional information about CPU errors in the CPU Manual.
Message texts and associated values of OB_BEGIN_PN (Page 234)
5.37.3
Message texts and associated values of OB_BEGIN_PN

Message block
ALARM_8P
Message
number
OB no.
Message
class
EV_ID1
OB 85
OB @7%d@ not loaded
234
No
message

Family: @System
Message block
ALARM_8P
Message
number
OB no.
Message
class
OB 84
Interface error
Assembly error OB_BEGIN_PN/OB_END:

No OB@2%d@ processing stack @1%d@
OB 85
Access-error error: @7%d@:

@10%2s@@8%d@/@9%d@
OB 122

Addr: @6%d@
OB 122

Adr: @6%d@
No
message

Message block
ALARM_8P
Associated value Block parameter
Data type
EV_ID1
CPU_DIAG_PN.OB_S_NUM_CNT
BYTE
TINFO_TOP_SI_NUM
BYTE
OB 72_supp_info 1
WORD
OB 122_BLK_TYP
WORD
OB 122_BLK_NUM
WORD
OB 122_MEM_ADDR
WORD
OB 85_supp_info 1
WORD
WORD
WORD
10
OB 85_DKZ2_3
WORD
Message block
ALARM_8P
Message
number
OB no.
Message class
EV_ID2
OB 80

max. limit
OB 80

used
OB 80

conform
OB 84


235
Family: @System
Message block
ALARM_8P
Message
number
OB no.
Message class
OB 84

OB 84

@2%2s@@5%d@ /@6%d@/
@4%d@/@3%d@
OB 84

and corrected
Messages 1 to 3 are generated in CPU_RT (Page 27) and forwarded to OB_BEGIN_PN.

the colon:
OB 121_RESERVED_1.

Message block
ALARM_8P
Associated
value
Block parameter
Data type
EV_ID2
OB 121_SW_FLT
BYTE
OB 121_BLK_TYP
WORD
OB 121_RESERVED_1
BYTE
OB 121_FLT_REG
WORD
OB 121_BLK_NUM
WORD
OB 121_PRG_ADDR
WORD
236

ALARM_8P
number
OB
no.
Messag
e
class
EV_ID3

OB@6%d@ PRIO @7%d@

Family: @System
ALARM_8P
number
OB
no.
Messag
e
class
Message 2 is generated in CPU_RT (Page 27) and forwarded to OB_BEGIN_PN.


Message block
ALARM_8P
Associated
value
EV_ID3
Block parameter
Data type
OB 121_SW_FLT
BYTE
OB 121_BLK_TYP
WORD
OB 121_RESERVED_1
BYTE
OB 121_FLT_REG
WORD
OB 122_BLK_NUM
WORD
OB 121_PRG_ADDR
WORD
Message block
ALARM_8P
Message
number
Message class
EV_ID_4
OB 88(@6W%t#OB_BEGIN_PN_TXT@):
OB@1%d@ PRIO@2%d@ @3%2s@@4%d@ /
@5%d@
OB_BEGIN_PN: Diagnostics error RALRM

STATUS = @7%8X@

No message
No message
No message
No message
No message
No message
237
Family: @System
5.38 OB_BEGIN_HPN: H-CPU diagnostics

Message block
ALARM_8P
Associated
value
Meaning
EV_ID4

Status RALRM
You will find the message texts and their text numbers in the section "Text library for
OB_BEGIN_PN (FB130) / OB_BEGIN_HPN (FB205) (Page 371)"
5.38
OB_BEGIN_HPN: H-CPU diagnostics
5.38.1
Description of OB_BEGIN_HPN

FB 205
I/Os of OB_BEGIN_HPN (Page 239)
Area of application
Block OB_BEGIN_HPN is used for H-CPU diagnostics of the automation system (AS). By
installing the block in CFC, the system creates all acyclic tasks (OBs) in which the driver blocks
of PCS 7 Basis Library are executed.
Message texts and associated values of OB_BEGIN_HPN (Page 240)
238

Family: @System
5.38.2
I/Os of OB_BEGIN_HPN
Information About Block Description (Page 11) ".
Input parameters
I/O
(parameter)
Meaning
Data type
Defau
lt
CPU_RT_DATA
CPU_RT Performance data
STRUCT
DIAG_BUF
Entry in diagnostic buffer (relevant for

maintenance personnel)
BOOL
EN_MSG
Reserve
BOOL
EV_IDx
Message number ALARM_8P_x (x = 1 - 5,

assigned by the ES)
DWORD
MS
Maintenance status
DWORD
R0_PLUG_TRANS_0_ADDR
Address of Rack 0 Pluggable Transceiver 0
INT
INT
INT
INT
SUB0IDxx
DP master system 1 IDxx (xx = 00 - 15)/PN

IO system 1 (100 - 115)
BYTE
255
SUB1IDxx
DP master system 2 IDxx (xx = 00 - 15)/PN

IO system 2 (100 - 115)
BYTE
255
Output parameters
I/O
(parameter)
Meaning
Data type
Defau
lt
CPU_DIAG
STRUCT
CPU_DIAG_PN
STRUCT
CPU_OB_4X
STRUCT
CPU_OB_5X
STRUCT
CPU_OB_5X_PN
STRUCT
CPU_OB_6X
STRUCT
CPUERR_0
1 = CPU error in rack 0
BOOL
CPUERR_1
1 = CPU error in rack 1
BOOL
DIAG_INF
Module Diagnostic Information Structure
STRUCT
EN_SUBx
Enable SUBNET x (DP: x = 0 15 / PN: x = 100 - 115)
BOOL
EXT_STAT
Extended Status
DWORD
EXT_STAT_1
Extended Status
DWORD
MASTER_0
BOOL

239
Family: @System
I/O
(parameter)
Meaning
Data type
Defau
lt
MASTER_1
BOOL
MSGSTATx
STATUS-output of the ALARM_8P_x (x = 1 - 5)
WORD
O_MS
Maintenance status
DWORD
QERR
BOOL
QMSGERx
Output error of the ALARM_8P_x (x = 1 - 5)
BOOL
SZL_71
STRUCT
The structures of the CPU_DIAG and CPU_DIAG_PN are integrated in the block
OB_BEGIN_HPN as OUT, and in all other blocks with this connection as IN_OUT .
Message texts and associated values of OB_BEGIN_HPN (Page 240)
5.38.3
Message texts and associated values of OB_BEGIN_HPN

Message block
ALARM_8P
Message
number
OB no.
Message
class
EV_ID1
OB 85
OB @7%d@not loaded
No
message
OB 84
Interface error
Assembly error OB_BEGIN/OB_END: No

OB@2%d@ processing of stack @1%d@
OB 85
Program execution error: @7%d@:

@10%2s@@8%d@/@9%d@
OB 122

Addr. @6%d@
OB 122

Addr. @6%d@
No
message
240

Family: @System

Message block
ALARM_8P
Associated value Block parameters
Data type
EV_ID1
CPU_DIAG.OB_S_NUM_CNT
BYTE
TINFO_TOP_SI_NUM
BYTE
OB 72_supp_info 1
WORD
OB 122_BLK_TYP
WORD
OB 122_BLK_NUM
WORD
OB 122_MEM_ADDR
WORD
OB 85_supp_info 1
WORD
WORD
WORD
10
OB 85_DKZ2_3
WORD
Message block
ALARM_8P
Message
number
OB no.
Message class
EV_ID2
OB80

max. limit
OB80

used
OB80

conform
OB 84

OB 84

OB 84

@2%2s@@5%d@ /@6%d@/
@4%d@/@3%d@
OB 84

and corrected
Messages 1 to 3 are generated in CPU_RT (Page 27) and forwarded to OB_BEGIN_HPN .

the colon:
OB 121_RESERVED_1.

241
Family: @System

Process control messages are generated with EV_ID2 and associated values via ALARM_8P .
Message block
ALARM_8P
Associated
value
Block parameters
Data type
EV_ID2
OB 121_SW_FLT
BYTE
OB 121_BLK_TYP
WORD
OB 121_RESERVED_1
BYTE
OB 121_FLT_REG
WORD
OB 121_BLK_NUM
WORD
OB 121_PRG_ADDR
WORD
ALARM_8P
number
OB
no.
Messag
e
class
EV_ID3

OB@6%d@ PRIO @7%d@
Message 2 is generated in CPU_RT (Page 27) and forwarded to OB_BEGIN_HPN.


Process control messages are generated with EV_ID3 and associated values via ALARM_8P .
Message block
ALARM_8P
EV_ID3
242
Associated
value
Meaning
Cycle time
Originator OB
Cycle time
Cycle time
Priority class

Family: @System
Message block
ALARM_8P
Associated
value
Meaning
Originator OB
Priority class
Originator OB
Priority class
10
Cycle time

Message block
ALARM_8P
Message
number
Message class
EV_ID_4
OB 88(@6W%t#OB_BEGIN_HPN_TXT@):
OB@1%d@ PRIO@2%d@ @3%2s@@4%d@ /
@5%d@
Diagnostics error RALRM STATUS = @7%8X@
CPU loss of redundancy in rack @8%d@
No message
UR0/Transceiver 0: Maintenance alarm

Message block
ALARM_8P
Associated
value
Meaning
EV_ID4

Status RALRM
CPU rack number


243
Family: @System
Message block
ALARM_8P
Message
number
Message class
EV_ID_5
UR0/Transceiver 0: Maintenance required
UR0/Transceiver 0: Maintenance demanded

Message block
ALARM_8P
Associated
value
Meaning
EV_ID5
MC7 command causing the error

Error number in OB_BEGIN_HPN_TXT (M_OB 88.T_OB 88)
Status RALRM
You will find the message texts and their text numbers in the section "Text library for
OB_BEGIN_PN (FB130) / OB_BEGIN_HPN (FB205) (Page 371)".
244

Family: @System
5.39 OB_DIAG1: OB diagnostics for avoiding stoppages in DPV1 master systems
5.39
OB_DIAG1: OB diagnostics for avoiding stoppages in DPV1 master

systems
5.39.1
Description of OB_DIAG1

FB 118
OB_DIAG1 block I/Os (Page 248)
Area of application
Block OB_DIAG1 monitors the failure and recovery of DP or PA slaves (referred to as slaves
below). The slaves can be connected to a DPV0 or DPV1 master system, or to a DPV1 DP/
PA link (Y link). OB_DIAG1 blocks further evaluation if a slave is defective (frequent producer)
to prevent the CPU stopping. It indicates the preferred channel of the active slave in an H
system. The indicated preferred channel 1 (SUBN1ACT ) is always TRUE, if the slave is
downstream of a DP/PA link (Y link) and is active.
Calling OBs
OB 1
Cyclic program
OB 70
OB 72
OB 82
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart
OB 55
Status interrupt (only as required)
OB 56
Update interrupt (only as required)
OB 57
Manufacturer-specific alarms (only as required)
The driver generator only installs the block in OB 55, OB 56 and OB 57 if diagnostic messages
are to be expected from these locations; consequently OB 5x are not entered in this block's
task list.

245
Family: @System
Use in CFC
function:
Block OB_DIAG1 is installed downstream of the SUBNET/DPAY_V1 block (when used
downstream of a DP/PA or Y link).
The RACK_NO, LADDR, DADDR, EN_MSG_D, SUBN1_ID, SUBN2_ID, and SUBN_TYP
inputs are configured.
The block inputs will be interconnected with output EN_SUBx (x = DP master system ID)
of the OB_BEGIN block and with output EN_Rxxx (xxx = rack/station number) of the
SUBNET block.
block are interconnected with the IN_OUT structures of the same name of block OB_DIAG.
RAC_DIAG_I is interconnected with its own RAC_DIAG OUT structure when used in a DP
master system.
RAC_DIAG_I is interconnected with the RAC_DIAG OUT structure of the DPAY_V1 block
when used downstream of a Y link.

The DPA_LINK block input receives information on the operational status of the slave, in other
words whether it is in use on a DP master system (DPA_LINK = FALSE) or downstream of a
DP/PA link (Y link). If the slave is connected to a DP master system, a failure is reported in
OB 86. If the slave is connected downstream of a DP/PA link (Y link), the failure is reported in
OB 83.
The block counts the number of calls to an acyclic OB of a block instance before an OB 1 can
be executed.
OB_DIAG1 indicates higher-level errors of the CPU, DP master/slave (QRACKF, SUBN1ERR,
SUBN2ERR). It determines the preferred channel of connected DP slaves (SUBN1ACT,
SUBN2ACT). The group error message QRACKF indicates failure of the DP master or slave.
An active DP slave has lost redundancy if one of the output parameters SUBN1ERR or
SUBN2ERR = TRUE.
Start and diagnostic information is read from the CPU_DIAG structure, which is interconnected
with the CPU_DIAG structure of the OB_BEGIN block.
The block evaluates error events, and uses the diagnostic address DADDR of the slave (on
the DP master system only) to determine the currently active preferred channel (SUBN1ACT,
SUBN2ACT) of redundant PROFIBUS DP interface circuits.
The slaves downstream of a DP/PA link (Y link) are not always active. In this case, the
diagnostic address DADDR is the diagnostic address of the link. The active preferred channel
(SUBN1ACT, SUBN2ACT) is displayed here by the DP/PA link (Y link).
The DP master systems or DP/PA links (Y link) must be operated in DPV1 mode (V1-MODE
= TRUE).
Failure and return of a DP slave are reported with ALARM_8P. The message function for all
messages can be disabled with EN_MSG = FALSE.
246

Family: @System
The Device failure message can be disabled with EM_MSG_D = FALSE (see Message
Response).
Overload behavior
Block OB_DIAG1 counts the frequency of the calls to the acyclic OB 55, OB 56, OB 57, OB
82, and OB 86 blocks (except in the case of a DP master system failure, see SUBNET block).
If the block is downstream of a DP/PA or Y link, the calls will be counted in OB 83, rather than
in OB 86. The following section deals only with OB 86.
Each OB is assigned a counter that is checked for the condition > 5. If this condition is fulfilled,
the block sets EN_F = FALSE (disable function block). The counters are reset in OB 1. The
output EN_F = TRUE (enable function block) is set in all other OBs.
OB_DIAG1 reports failure of the blocks mentioned above in OB 1, OB 82 or OB 86, including
the geographic address of the slave.
OB 55, OB 56, OB 57 and OB 82 are locked in the event of an overload, however, so the event
is not evaluated in the downstream blocks. The outputs cannot correspond to the current slave
status. If an OB is locked and no more slave events have been reported after a delay of around
1 minute, if it is OB 86 that is disabled, the slave status is checked, and the outputs are updated.
It may take several cycles to update the slave status.
If it is OB 82 that is disabled, rather than OB 86, the EN_DIAG variable is set to TRUE after
around 1 minute. The interconnected DP slave block can then fetch the current diagnostic data
for the slave, and update its own data. The same applies to OB 55, OB 56, and OB 57.
The outgoing message about the fault is generated when the OB lock is canceled, and either
a new event has occurred for this OB or the wait time has elapsed.
Redundancy
The block supports redundant DP master systems in an H system (distributed I/Os only). The
SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs of the
OB_DIAG1 block are configured with the numbers of the redundant DP master systems. If the
DP master systems are not redundant, the remaining input is set to 16#FF (default).
The availability of the slave is checked. In H systems the preferred channel of the slave is
determined (active slaves only).
Error handling
The block evaluates the error information from ALARM_8P, and writes it to the relevant output
parameter.

247
Family: @System
Message response
can hold up to two message statuses of its event ID. (and generally no more than two
messages). The block generates the messages listed below:
OB no. Start Event
Message
Cyclic processing
Call of ALARM_8P due to incomplete transfer or

unacknowledged message
72
CPU redundancy loss
If no redundant diagnostic repeater is connected to this CPU,

the "Slave" failure/return message is output.
70
Redundancy loss
If there is no redundant slave connected to this DP master

system, message "Device" failure/return, otherwise message
"Slave" redundancy loss/return
83
Removal/insertion
Message "Slave" failure/return
86
Rack failure
Message "Slave" failure/return
100
Restart
If the diagnostic blocks (e.g., MOD_PAL0) of a device also report the failure of a device, the
"Device failure message can be disabled with EN_MSG_D = FALSE (this is done automatically
by the driver generator).

manual.
Message texts and associated values of OB_DIAG1 (Page 250)
5.39.2
I/Os of OB_DIAG1
248

Family: @System
Input parameters
I/O
(parameter)
Meaning
Data type
Default
DADDR
Diagnostic address of the slave or DP/PA link
INT
DIAG_BUF

personnel)
BOOL
DPA_LINK
Slave connection: 0 = DP master system 1 = Link
BOOL
EN_MSG
1 = enable message
BOOL
EN_MSG_D
BOOL
EV_ID
Message number
DWORD
LADDR
Logical basic address of the slave
INT
MS
Maintenance status
DWORD
PADP_ADR
Address of the PA/DP slave
BYTE
255
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number 0 of the slave at the DP/PA Link
BYTE
255
SUBN_TYP
1 = External DP interface
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Output parameters
I/O
(parameter)
Meaning
Data type
Default
EN_DIAG
1 = Read diagnostics with SFC 13
BOOL
EN_F
1 = Enable function/function block
BOOL
MOD_INF
System structure: Module diagnostics
STRUCT
MSG_ACK
WORD
MSG_STAT
WORD
O_MS
Maintenance status
DWORD
QRACKF
BOOL
RAC_DIAG
STRUCT
SUBN1ACT
BOOL
SUBN1ERR
BOOL
SUBN2ACT
BOOL
SUBN2ERR
BOOL
V1_MODE
1 = DPV1 mode of the DP master system
BOOL

249
Family: @System
In/out parameters
I/O
(parameter)
Meaning
Data type
Default
0
ACC_ID
1 = Accept MODE settings
BOOL
CPU_DIAG
STRUCT
CPU_OB_5X
OB_5x start information
STRUCT
RAC_DIAG_I
STRUCT
SUB_DIAG
STRUCT
Message texts and associated values of OB_DIAG1 (Page 250)
5.39.3
Message texts and associated values of OB_DIAG1

Message No.
Message
class
DP slave @4%d@/ @2%d@: Redundancy loss
DP slave @1%d@/ @2%d@: Failure
DP slave @1%d@/ @2%d@/@3%d@ : Multiple failure
Device @1%d@/ @2%d@/@3%d@: Multiple alarm (OB 82)
250
Associated value
Block parameters
ID of the primary DP master system (SUBN_ID)
Slot number (SLOT_NO)
Subnet ID of the master in the event of redundancy loss (SUBN2_ID)

Family: @System
5.40 OB_DIAG1_PN: OB diagnostics for avoiding stoppages in DPV1 master systems
See also
5.40
OB_DIAG1_PN: OB diagnostics for avoiding stoppages in DPV1 master

systems
5.40.1
Description of OB_DIAG1_PN

FB 202
I/Os of OB_DIAG1_PN (Page 251)
Area of application
Block OB_DIAG1_PN monitors the failure and recovery of all Profinet standard slaves and the
IE/PB-Link. The slaves can be connected to an IE/PB. To prevent the CPU stopping,
OB_DIAG1_PN blocks further evaluation if a slave is defective.
5.40.2
I/Os of OB_DIAG1_PN
Input parameters
I/O
(parameter)
Meaning
Data type
Default
DADDR
IE/PB link diagnostic address
INT
DIAG_BUF

personnel)
BOOL
DPA_LINK
Slave connection: 0 = PN-IO Master 1 = IE/PB link
BOOL
EN_MSG
1 = enable message
BOOL
EN_MSG_D
BOOL
EV_ID
DWORD
LADDR
Logical basic address of the slave
INT
MS
Maintenance status
DWORD
PADP_ADR
Diagnostic address of the PN IO device
BYTE
255

251
Family: @System
I/O
(parameter)
Meaning
Data type
Default
RACK_NO
Rack number
BYTE
SLOT_NO
Slot number of the slave at the IE/PB link
BYTE
255
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
I/O
(parameter)
Meaning
Data type
Default
EN_F
BOOL
MOD_INF
System structure: Module diagnostics
STRUCT
MSG_ACK
WORD
MSG_STATx
STATUS output of ALARM_8P_x (x = 1-2)
WORD
Output parameters
O_MS
Maintenance status
DWORD
QRACKF
BOOL
RAC_DIAG
STRUCT
SUBN1ACT
1 = PN IO device 1 active
BOOL
SUBN1ERR
1 = Error in the PN IO device 1
BOOL
SUBN2ACT
1 = PN IO device 2 active
BOOL
SUBN2ERR
1 = Error in the PN IO device 2
BOOL
I/O
(parameter)
Meaning
Data type
Default
0
In/out parameters
252
ACC_ID
BOOL
CPU_DIAG_PN
STRUCT
CPU_OB_5X
OB_5x start information
STRUCT
RAC_DIAG_I
STRUCT
SUB_DIAG
OB startup information
STRUCT

Family: @System
5.40.3
Message texts and associated values of OB_DIAG1_PN

Message block
ALARM_8P
Message
number
EV_ID1
Message
class
No
message
PN IO device @1%d@/ @2%d@: Failure
PN IO device @1%d@/ @2%d@/@3%d@ :

Multiple failure

alarm (OB 82)

alarm (OB 55)

alarm (OB 56)

alarm (OB 57)

Associated value
Block parameter
Data type
ID of the primary PN IO system (SUBN1_ID)
BYTE
BYTE
Slot number (SLOT_NO)
BYTE
See also

253
Family: @System
5.41 OB_DIAGF: Monitoring of the FF link and coupler
5.41
OB_DIAGF: Monitoring of the FF link and coupler
5.41.1
Description of OB_DIAGF

FB 146
I/Os of OB_DIAGF (Page 255)
Area of application
The OB_DIAGF block monitors the FF link and coupler for
Failure and return of FF link and coupler
Redundancy loss
diagnostic interrupts
and reports these events.
The OB_DIAGF block runs acyclically and is enabled to run by the higher-level SUBNET block.
Calling OBs
The block must be installed in the run sequence downstream from the SUBNET block in the
following OBs (this is done automatically in the CFC):
OB no.
Start Event
Cyclic processing
72
CPU redundancy loss
70
Redundancy loss
82
83
Removal/insertion
85
86
Module driver failure
100
Restart
Use in CFC
function:
The OB_DIAGF block is installed downstream from the SUBNET block.
The DADDR, SUBN1_ID, SUBN2_ID, RACK_NO, COUP_RED, and SLOT_NO inputs are
assigned parameters.
254

Family: @System
The EN input is interconnected with the output of an AND block. The block inputs will be
interconnected with output EN_SUBx (x = DP master system ID) of the OB_BEGIN block
and with output EN_Rxxx (xxx = rack/station number) of the SUBNET block.
block are interconnected with the IN_OUT structures of the same name of block OB_DIAGF.
Message response
The DELAY input is used to delay the outputting of error messages for an outgoing, higherpriority error. For example, if the OB_DIAGF block recognizes an outgoing error at a DP master
connected with it, it initially assumes that there is a faulty assigned DP slave in the rack it
the DP slave returns (in this case: OB 86, OB 70). The OB_DIAGF blocks suppress the potential
slave failure for DELAY seconds so as not to trigger a surge of messages from DP slaves
which are not yet synchronized when the master returns. An error message is only output to
the OS when the DP slave has not reported its return before this delay time has expired.

manual.
5.41.2
I/Os of OB_DIAGF
I/Os of OB_DIAGF
Input parameters
I/O
Meaning
Data type
Default
0 = No redundant structure
BYTE
16#FF
INT
(parameter)
COUP_RED
1 = Coupler redundancy
2 = Ring redundancy
DADDR

255
Family: @System
I/O
Meaning
Data type
Default
DIAG_BUF

personnel)
BOOL
DELAY
Interrupt delay (s)
INT
15
EN_MSG
1 = enable message
BOOL
EV_ID1
Message number
DWORD
EV_ID2
Message number
DWORD
MS
Maintenance status
DWORD
RACK_NO
Number of the rack
BYTE
16#FF
SUBN_TYP
BOOL
SUBN1_ID
BYTE
16#FF
SUBN2_ID
BYTE
16#FF
Meaning
Data type
Default
DINFO
STRUCT
EN_F
BOOL
FF_DIAG
STRUCT
MSG_ACK
WORD
MSG_STAT
Message error
WORD
O_MS
Maintenance status
DWORD
QRACKF
BOOL
RAC_DIAG
RACK diagnostics
STRUCT
RETURN_CODE_
O
Return value
INT
SUBN1ACT
BOOL
SUBN2ACT
BOOL
SUBN1ERR
BOOL
SUBN2ERR
BOOL
V1_MODE
1 = DPV1 mode of the DP master system active
BOOL
I/O
Meaning
Data type
Default
ACC_ID
BOOL
CPU_DIAG
STRUCT
SUB_DIAG
STRUCT
(parameter)
Output parameters
I/O
(parameter)
0
In/out parameters
(parameter)
256

Family: @System
5.41.3
Message texts and associated values of OB_DIAGF
Message texts and associated values of OB_DIAGF

Message block
ALARM_8P
Message
No.
EV_ID1
FF link @4%d@/@2%d@:Redundancy loss
FF link @1%d@/@2%d@: Failure
EV_ID2
Message
class
FF link @1%d@/@2%d@: Multiple failure
FF link @1%d@/@2%d@: Multiple alarm (OB 82)
Link @1%d@/@2%d@/2: Redundancy loss
Link @1%d@/@2%d@/3: Redundancy loss
FF-Link @1%d@/@2%d@/1:DIP switch has a different

DP address setting than at "power on" of the IM/
Redundant configuration, neighboring IM has a different
DP address.
FF link @1%d@/@2%d@/1: SDB_UUID does not

match saved UUID
Link @1%d@/@2%d@/2: Failure
Link @1%d@/@2%d@/2: Contrary to configuration:

Coupler configuration does not match the determined
configuration
Link @1%d@/@2%d@/2: External connection, short

circuit or wire break detected
Link @1%d@/@2%d@/2: Loss of redundancy in the

case of ring redundancy
Link @1%d@/@2%d@/3: Failure
Link @1%d@/@2%d@/3: Contrary to configuration:

Coupler configuration does not match the determined
configuration
Link @1%d@/@2%d@/3: External connection, short

circuit or wire break detected
Link @1%d@/@2%d@/3: Loss of redundancy in the

case of ring redundancy

Associated value
Block parameters

257
Family: @System
5.42 OB_END: Reset stack pointer of OB_BEGIN
5.42
OB_END: Reset stack pointer of OB_BEGIN
5.42.1
Description of OB_END

FC 280
OB_END block I/Os (Page 259)
Area of application
The OB_END block is used to reset the stack pointer of OB_BEGIN and OB_BEGIN_PN.
Calling OBs
The OB_END block is the final entry in the OB that contains an OB_BEGIN and/or an
OB_BEGIN_PN block.
OB 1
Cyclic processing
OB 55
Status interrupt (only as required)
OB 56
Update interrupt (only as required)
OB 57
Manufacturer-specific alarms (only as required)
OB 70
OB 72
OB 80
Timeout error
OB 81
Power supply error
OB 82
OB 83
OB 84
CPU hardware error (only for CPU with this function)
OB 85
OB 86
Rack failure
OB 88
Stop avoidance
OB 100
Restart
OB 121
Programming error
OB 122
I/O access error
Use in CFC
When the CFC function "Generate module drivers" is used, OB_END is automatically installed
in the above OBs of the run sequence.
258

Family: @System
5.42 OB_END: Reset stack pointer of OB_BEGIN
Function
The OB_END block decrements the stack pointer (NUM_CNT) of OB_BEGIN and
OB_BEGIN_PN. In the event of an interruption, it enters the last interrupted OB number read
from the CPU stack into the CPU_DIAG and CPU_DIAG_PN structure.
Error handling
Not available
Not available
Initial startup behavior

Not available
Time response
Not available
Message response
Not available

5.42.2
I/Os of OB_END
In-out parameters
I/O
(parameter)
Meaning
Data type
CPU_DIAG
STRUCT
CPU_DIAG_PN
System structure: CPU diagnostics (PN)
STRUCT

259
Family: @System
5.43 OR_32_TS: OR value status of two redundant time-stamped signal modules, max. 32 channels
5.43
OR_32_TS: OR value status of two redundant time-stamped signal

modules, max. 32 channels
5.43.1
Description of OR_32_TS

FB 138
OR_32_TS block I/Os (Page 261)
Area of application
The OR_32_TS block forms the resulting time stamp from two redundant time-stamped signal
modules.
Calling OBs
The block must be installed in OB 1.
Use in CFC
function:
The OR_32_TS block is installed in OB 1.
The TS1_xx inputs are interconnected with the TS_xx output of IMDRV_TS that is
responsible for the signal module with the lower address.
The TS2_xx inputs are interconnected with the TS_xx output of IMDRV_TS that is
responsible for the signal module with the higher address.
The TS_xx outputs are interconnected with the inputs of the MSG_TS channel blocks or
Pcs7InIT.

The OR_32_TS block forwards the time stamps of the channels of two redundant signal
modules to the MSG_TS channel blocks or Pcs7InIT and acts like an OR function.
If both channels are active, the time stamp of the signal module with the lower address is
always used.
If one channel is passivated, the time stamp of the redundant channel is forwarded.
If both channels are passivated, the time stamp of the signal module with the lower address
is entered.
260

Family: @System
Redundancy
Redundancy of the modules in an H system is monitored in the higher-level RED_STATUS
block.
Error handling
Not available
Message response
Not available

Not available
You will find more information in Description of IMDRV_TS (Page 83)
5.43.2
I/Os of OR_32_TS
Input parameters
I/O
Meaning
Type
Default
Status of the channels of the 2nd module; information

channel by channel
DWORD
DWORD
(parameter)
CH_INF_H
0 = passivated, 1 = operational
CH_INF_L
Status of the channels of the 1st module; information

channel by channel
0 = passivated, 1 = operational
RED
1 = with redundant time stamp
BOOL
RED_STAT
Return value from RED_STATUS
INT

261
Family: @System
I/O
Meaning
Type
Time stamp (xx = 00 - 31) from the module with the lower
address
STRUCT
Default
(parameter)
TS1_xx
Byte 0:
Byte 1:
DWORD TS0:
DWORD TS1:
TS2_xx
Time stamp (xx = 00 - 31) from the module with the higher
address
STRUCT
Byte 0:
Byte 1:
DWORD TS0:
DWORD TS1:
TS1_C_xx
TS communication (xx = 00 - 31) from the module with the

lower address
BYTE
BYTE
Meaning
Type
Default
CH_ALM
Channel failure Redundant pair
DWORD
CH_WRN
Channel redundancy loss
DWORD
QERR
1 = program error
BOOL

TS2_C_xx
TS communication (xx = 00 - 31) from the module with the

higher address
Output parameters
I/O
(parameter)
(module status not available)
262

Family: @System
5.44 OR_HA16C: OR value status of 2 redundant HART modules, max. 16 channels, module granular
I/O
Meaning
Type
Time stamp (xx = 00 - 31)
STRUCT
Default
(parameter)
TS_xx
Byte 0:
Byte 1:
DWORD TS0:
DWORD TS1:
TS_C_xx
TS communication (xx = 00 - 31)
BYTE

5.44
OR_HA16C: OR value status of 2 redundant HART modules, max. 16

channels, module granular
5.44.1
Description of OR_HA16C

FB 133
OR_HA16C block I/Os (Page 266)
Area of application
The OR_HA16C block is used to create a value status from two redundant signal modules,
and reports loss of redundancy for HART modules.

263
Family: @System
Calling OBs
The block must be installed in OB 100 and in the OB before the MOD_HA driver block that is
responsible for the relevant module.
Use in CFC
function:
The OR_HA16C block is installed before its interconnected MOD_HA driver block in its OB.
MODE1_xx inputs are interconnected with the OMODE_xx outputs of the MOD_x block in
the primary module.
the redundant module.
The MOD_INF1 input structure is interconnected with the MOD_INF output structure of the
MOD_x block in the primary module.
MOD_x block in the redundant module.
The ACTIV_H and ACTIV_L inputs are interconnected with the outputs of the same name
of the RED_STATUS block in the redundant module.
The OMODE_xx outputs are interconnected with the downstream MOD_HA.
structures of the same name of the OR_HA_16C block.
The inputs RACKF1 and RACKF2 are interconnected with the outputs QRACKF1 and
QRACKF2 of MOD_x.
The CH_INF_H and CH_INF_L inputs are interconnected with the outputs of the same name
of the RED_STATUS block.
MS parameter.

The value status of a signal module and of a redundant signal module are ORed by the
OR_HA16C block. Signal modules or signal channels set to passive mode by the system are
regarded as invalid. The "At least one channel pair does not match", "Redundancy loss" and
"Failure of the redundant I/O" events are reported by ALARM_8P. The message function can
be disabled.
When module signals are processed in different OB 3x, in very few cases, a faulty signal value
may be processed in one cycle by one of the channel blocks configured to process the module
signals following a process-control malfunction affecting the module. This can be avoided by
processing all channel blocks of a module in the OB 3x that also processes the process image
partition to which this module is assigned.
264

Family: @System
Depassivation can be triggered for a passivated block or channel by setting the DEPASS input.
For this the function RED_DEPA (FC 451) is called internally.
For OR_M_xxC / OR_HA16C blocks:
With channel-granular redundancy, "Loss of redundancy channel x" is reported if one channel
fails. If both channels fail, "Redundancy pair failure channel x" is reported.
With OR_HA16C, the message "Redundancy pair failure HART variable 01" to "Redundancy
pair failure HART variable 08" is output for HART signals 01 to 08. The message function can
be disabled.
For all OR blocks

For this, the RED_DEPA function (FC 451) is called internally.
Redundancy
Redundancy of the modules is monitored in a higher-level RED_STATUS block (FB 453).
Error handling
The OMODE_xx outputs are updated when the "Startup" bit is set. ALARM_8P will be initialized.
Time response
Not available
Message response
OR_HA16C uses ALARM_8P for reporting. The message function can be disabled by setting
EN_MSG = FALSE.

manual.
Note: Online help and the manual "PCS 7 FACEPLATES" are only available if the
"PCS 7 FACEPLATES" software package is installed.

265
Family: @System
Message texts and associated values of OR_HA16C (Page 268)
maintenance
5.44.2
I/Os of OR_M_8C / OR_M_16C / OR_M_32C / OR_HA16C

The OR_M_8C and OR_M_16C / OR_HA16C / OR_M_32C block I/Os are identical, with the
exception of the number of MODE1_xx and MODE2_xx and OMODE_xx.
Input parameters
I/O
(parameter)
Meaning
Data type
Default
ACTIV_H
1 = module with more significant address is active
BOOL
ACTIV_L
1 = module with less significant address is active
BOOL
CHAN_NUM
INT
CH_INF_H
Status of the channels on the 2nd module; info on a channelspecific basis

0 = passivated, 1 = in service
DWORD
CH_INF_L
Status of the channels on the 1st module; info on a channelspecific basis

DWORD
DEPASS
1 = depassivation
BOOL
DEPASS_EN
1 = enable depassivation
BOOL
EN_MSG
1 = Enable message
BOOL
EV_IDx
Message number (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
DWORD
MOD_STAT
Module status word from RED_STATUS
WORD
MODE1_xx
Channel mode (xx = 00 07 / 00 15 / 00 - 31) on the primary

module
DWORD
DWORD
HART variable mode x (x = 1 - 8) on the primary module

MODE2_xx
Channel mode (xx = 00 07 / 00 15 / 00 - 31) on the redundant

module
MS
Maintenance status
DWORD
RACKF1
1 = error rack 1
BOOL
HART variable mode x (x = 1 - 8) on the redundant module
266

Family: @System
I/O
(parameter)
Meaning
Data type
Default
RACKF2
1 = error rack 2
BOOL
RED_STAT
Value returned by the RED_STATUS block
INT
Output parameters
I/O
(parameter)
Meaning
Data type
Default
CH_ACTIVE
Channel active
DWORD
16#00000000
CH_ALM
DWORD
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
CH_WRN
DWORD
DXCHG_xx
Bidirectional data exchange channel (xx = 00 - 07 / 00 - 15 / 00 31 / 00 - 15)

Bit 0= Release for maintenance
Bit 1-31 = Reserve
DWORD
DXCHG_1_XX
DWORD
EXT_INFO
Supplemental info of RED_OUT
INT
EXT_STAT
DWORD
MS_REQ
BOOL
MS_XCHG_xx
Maintenance Status - Data exchange channel (xx = 00 - 63)
DWORD
MSG_ACKx
Message acknowledgment ALARM_8P_x

(x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
MSG_STATx
Message error information ALARM_8P_x

(x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
O_MS
Maintenance status
DWORD
OMODE_xx
Channel mode (xx = 00 07 / 00 15 / 00 - 31)

mode HART variable x (x = 1 - 8)
DWORD
QDISCREP
1 = At least one channel pair does not match
BOOL
QERR
1 = program error
(cannot determine module status)
BOOL
QMODF1
1 = error module 1
BOOL
QMODF2
1 = error module 2
BOOL
QPASS
1 = at least one module is passivated
BOOL
RETURN_VAL
Error information from RED_OUT
INT

267
Family: @System
In/out parameters
I/O
(parameter)
Meaning
Data type
Default
CPU_DIAG
STRUCT
DXCHG1_xx
Bidirectional data exchange channel 1
DWORD
DWORD
DWORD
xx = 00 to 07 (OR_M8C and OR_HA16C

xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
DXCHG11_xx
DXCHG2_xx

xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
DXCHG21_xx
DWORD
MOD_INF1
Module parameters module 1
STRUCT
MOD_INF2
STRUCT
MS_XCHG1_xx
DWORD
MS_XCHG2_xx
DWORD
Message texts and associated values of OR_M_8C (Page 287)
5.44.3
Message texts and associated values of OR_HA16C
Assignment of message text and message classes

You can find more information under Message classes (Page 355)
268
Message block
ALARM_8P
Message
number
Message
class
EV_ID1
Module @1%d@/@2%d@/@3%d@:
Failure module redundancy pair
Module @1%d@/@2%d@/@3%d@:
Modules loss of redundancy

Family: @System
Message block
ALARM_8P
EV_ID2
EV_ID3
EV_ID4

Message
number
Message
class
Module @1%d@/@2%d@/@3%d@:
Cannot determine module status
Module @1%d@/@2%d@/@3%d@:
Discrepancy time has expired for at least one
channel pair
Module @1%d@/@2%d@/@3%d@:
Failure redundancy pair channel 00
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Failure redundancy pair HART variable 01
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Redundancy loss channel 00
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
269
Family: @System
Message block
ALARM_8P
EV_ID5
Message
number
Message
class
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Redundancy loss HART variable 01
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:

Message block
ALARM_8P
Associat
ed
value
Block parameters
Meaning
EV_ID1 ... 5
SUBN_ID
RACK_NO
SLOT_NO
Slot number (byte)
Redundancy loss causes the geographic address of the failed module to be entered
dynamically.
If both modules fail, the message text always contains the geographic address of the primary
module.
270

Family: @System
5.45 OR_M_16C: OR value status of 2 redundant signal modules, max. 16 channels, channel granular
5.45
OR_M_16C: OR value status of 2 redundant signal modules, max. 16

channels, channel granular
5.45.1
Description of OR_M_16

FB 84
OR_M_16C block I/Os (Page 271)
The OR_M_16C block corresponds to OR_M_8C (Page 282), but with 16, rather than 8
channels.
For further information, refer to the following sections:
Maintenance status of MS (Page 356)
You will find more information on this in PCS 7 Advanced Process Library > Basics of APL >
General functions of the blocks > Operating, monitoring and reporting > Maintenance release
5.45.2

Input parameters
I/O
(parameter)
Meaning
Data type
Default
ACTIV_H
BOOL
ACTIV_L
BOOL
CHAN_NUM
INT
CH_INF_H

DWORD

271
Family: @System
I/O
(parameter)
Meaning
Data type
Default
CH_INF_L

DWORD
DEPASS
1 = depassivation
BOOL
DEPASS_EN
BOOL
EN_MSG
1 = Enable message
BOOL
EV_IDx
Message number (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
DWORD
MOD_STAT
WORD
MODE1_xx

module
DWORD
DWORD

MODE2_xx

module
MS
Maintenance status
DWORD
RACKF1
1 = error rack 1
BOOL
RACKF2
1 = error rack 2
BOOL
RED_STAT
INT
Output parameters
I/O
(parameter)
Meaning
Data type
Default
CH_ACTIVE
Channel active
DWORD
16#00000000
CH_ALM
DWORD
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
CH_WRN
DWORD
DXCHG_xx

Bit 1-31 = Reserve
DWORD
DXCHG_1_XX
DWORD
EXT_INFO
INT
EXT_STAT
DWORD
MS_REQ
BOOL
MS_XCHG_xx
DWORD
MSG_ACKx

(x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
MSG_STATx

(x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
O_MS
Maintenance status
DWORD
OMODE_xx
Channel mode (xx = 00 07 / 00 15 / 00 - 31)

DWORD
272

Family: @System
I/O
(parameter)
Meaning
Data type
Default
QDISCREP
BOOL
QERR
1 = program error
BOOL
QMODF1
1 = error module 1
BOOL
QMODF2
1 = error module 2
BOOL
QPASS
BOOL
RETURN_VAL
INT
Meaning
Data type
Default
In/out parameters
I/O
(parameter)
CPU_DIAG
STRUCT
DXCHG1_xx
DWORD
DWORD
DWORD

xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
DXCHG11_xx
DXCHG2_xx

xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
DXCHG21_xx
DWORD
MOD_INF1
STRUCT
MOD_INF2
STRUCT
MS_XCHG1_xx
DWORD
MS_XCHG2_xx
DWORD

273
Family: @System
5.45.3
Message texts and associated values of OR_M_16C

Message block
ALARM_8P
Message
number
Message
class
EV_ID1
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
channel pair
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
EV_ID2
EV_ID3
274

Family: @System
Message block
ALARM_8P
Message
number
Message
class
EV_ID4
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
EV_ID5

Message block
ALARM_8P
Associat
ed
value
Block parameters
Meaning
EV_ID1 ... 5
SUBN_ID
RACK_NO
SLOT_NO
Slot number (byte)
dynamically.
module.

275
Family: @System
See also
5.46

5.46.1
Description of OR_M_32C

FB85
Block OR_M_32C corresponds to the OR_M_8C (Page 282) block, but with 32 channels
instead of 8.
You will find more information on this in PCS 7 Advanced Process Library > Basics of APL >
General functions of the blocks > Operating, monitoring and reporting > Release for
maintenance
5.46.2

Input parameters
I/O
(parameter)
Meaning
Data type
Default
ACTIV_H
BOOL
ACTIV_L
BOOL
276

Family: @System
I/O
(parameter)
Meaning
Data type
Default
CHAN_NUM
INT
CH_INF_H

DWORD
CH_INF_L

DWORD
DEPASS
1 = depassivation
BOOL
DEPASS_EN
BOOL
EN_MSG
1 = Enable message
BOOL
EV_IDx
Message number (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
DWORD
MOD_STAT
WORD
MODE1_xx

module
DWORD
DWORD

MODE2_xx

module
MS
Maintenance status
DWORD
RACKF1
1 = error rack 1
BOOL
RACKF2
1 = error rack 2
BOOL
RED_STAT
INT
Output parameters
I/O
(parameter)
Meaning
Data type
Default
CH_ACTIVE
Channel active
DWORD
16#00000000
CH_ALM
DWORD
CH_EXIST
Channel exists
DWORD
CH_OK
Channel OK
DWORD
CH_WRN
DWORD
DXCHG_xx

Bit 1-31 = Reserve
DWORD
DXCHG_1_XX
DWORD
EXT_INFO
INT
EXT_STAT
DWORD
MS_REQ
BOOL
MS_XCHG_xx
DWORD
MSG_ACKx

(x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD

277
Family: @System
I/O
(parameter)
Meaning
Data type
Default
MSG_STATx

(x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
O_MS
Maintenance status
DWORD
OMODE_xx
Channel mode (xx = 00 07 / 00 15 / 00 - 31)

DWORD
QDISCREP
BOOL
QERR
1 = program error
BOOL
QMODF1
1 = error module 1
BOOL
QMODF2
1 = error module 2
BOOL
QPASS
BOOL
RETURN_VAL
INT
Meaning
Data type
Default
In/out parameters
I/O
(parameter)
CPU_DIAG
STRUCT
DXCHG1_xx
DWORD

xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
DXCHG11_xx
DWORD
DXCHG2_xx
DWORD

xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
DXCHG21_xx
DWORD
MOD_INF1
STRUCT
MOD_INF2
STRUCT
MS_XCHG1_xx
DWORD
MS_XCHG2_xx
DWORD
278

Family: @System
5.46.3

Message block
ALARM_8P
Message
number
Message class
EV_ID1
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
channel pair
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
EV_ID2
EV_ID3

279
Family: @System
Message block
ALARM_8P
EV_ID4
EV_ID5
EV_ID6
280
Message
number
Message class
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:

Family: @System
Message block
ALARM_8P
EV_ID7
EV_ID8
EV_ID9

Message
number
Message class
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
281
Family: @System
Message block
ALARM_8P
Message
number
Message class
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:

Message block
ALARM_8P
Associat
ed
value
Block parameters
Meaning
EV_ID1 ... 9
SUBN_ID
RACK_NO
SLOT_NO
Slot number (byte)
dynamically.
module.
See also
5.47

5.47.1
Description of OR_M_8C

FB 83
Area of application
The OR_M_8C block generates a channel-granular value status from two redundant signal
modules.
282

Family: @System
Calling OBs
The block must be installed in OB 100 and in the fastest OB upstream of the CH_x block that
is interconnected with OR_M_8C.
Use in CFC
function:
The OR_M_8C block is installed upstream in the OBs of the CH_x channel blocks that are
interconnected with it.
MODE1_x inputs are interconnected with the OMODE_xx outputs of the MOD_x block in
the primary module.
MODE2_x inputs are interconnected with the OMODE_xx outputs of the MOD_x block in
MOD_x block in the primary module.
MOD_x block in the redundant module.
The ACTIV_H and ACTIV_L inputs are interconnected with the outputs of the same name
of the RED_STATUS block in the redundant module.
The OMODE_xx outputs are interconnected with the relevant CH_x channel blocks.
structures of the same name of the OR_M_8C block.
The RACKF1 and RACKF2 inputs are interconnected with the QRACKF1 and QRACKF2
outputs of MOD_xx.
The CH_INF_H and CH_INF_L inputs are interconnected with the outputs of the same name
of the RED_STATUS block.
MS parameter.

The value statuses of a signal module and of a redundant signal module are ORed by the
OR_M_8C block. Signal modules or signal channels set to passive mode by the system are
regarded as invalid. For redundant digital input modules, when a signal discrepancy occurs,
no module or channel is set to passive after the discrepancy time has elapsed. The module
or channel whose signal does not change is then set to passive. The "At least one channel
pair does not match", "Redundancy loss" and "Failure of the redundant I/O" events are reported
by ALARM_8P. The message function can be disabled.
Note: When module signals are processed in different OB 3x, in very few cases, a faulty signal
value may be processed in one cycle by one of the channel blocks configured to process the
module signals following a process-control malfunction affecting the module. This can be

283
Family: @System
avoided by processing all channel blocks of a module in the OB 3x that also processes the
process image partition to which this module is assigned.
For OR_M_Cxx blocks:
With channel-granular redundancy, "Loss of redundancy channel x" is reported if one channel
fails. If both channels fail, "Redundancy pair failure channel x" is reported. The message
function can be disabled.
For all OR blocks:
This is done by calling the RED_DEPA FC451 function internally.
Redundancy
Redundancy of the modules in an H system is monitored in the higher-level RED_STATUS
block.
Error handling
The OMODE_xx (Page 351) outputs are updated when the "Startup" bit is set.
ALARM_8P will be initialized.
Message response
OR_M_8C uses ALARM_8P for reporting. The message function can be disabled by setting
EN_MSG = FALSE.

manual.
maintenance
284

Family: @System
5.47.2

Input parameters
I/O
(parameter)
Meaning
Data type
Default
ACTIV_H
BOOL
ACTIV_L
BOOL
CHAN_NUM
INT
CH_INF_H

DWORD
CH_INF_L

DWORD
DEPASS
1 = depassivation
BOOL
DEPASS_EN
BOOL
EN_MSG
1 = Enable message
BOOL
EV_IDx
Message number (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
DWORD
MOD_STAT
WORD
MODE1_xx

module
DWORD
DWORD

MODE2_xx

module
MS
Maintenance status
DWORD
RACKF1
1 = error rack 1
BOOL
RACKF2
1 = error rack 2
BOOL
RED_STAT
INT
Meaning
Data type
Default
CH_ACTIVE
Channel active
DWORD
16#00000000
CH_ALM
DWORD
CH_EXIST
Channel exists
DWORD
Output parameters
I/O
(parameter)

285
Family: @System
I/O
(parameter)
Meaning
Data type
Default
CH_OK
Channel OK
DWORD
CH_WRN
DWORD
DXCHG_xx

Bit 1-31 = Reserve
DWORD
DXCHG_1_XX
DWORD
EXT_INFO
INT
EXT_STAT
DWORD
MS_REQ
BOOL
MS_XCHG_xx
DWORD
MSG_ACKx

(x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
MSG_STATx

(x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
O_MS
Maintenance status
DWORD
OMODE_xx
Channel mode (xx = 00 07 / 00 15 / 00 - 31)

DWORD
QDISCREP
BOOL
QERR
1 = program error
BOOL
QMODF1
1 = error module 1
BOOL
QMODF2
1 = error module 2
BOOL
QPASS
BOOL
RETURN_VAL
INT
I/O
(parameter)
Meaning
Data type
Default
CPU_DIAG
STRUCT
DWORD
In/out parameters
DXCHG1_xx

xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
DXCHG11_xx
DWORD
DXCHG2_xx
DWORD

xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
DXCHG21_xx
DWORD
MOD_INF1
STRUCT
MOD_INF2
STRUCT
286

Family: @System
I/O
(parameter)
Meaning
Data type
Default
MS_XCHG1_xx
DWORD
MS_XCHG2_xx
DWORD
5.47.3

Message block
ALARM_8P
Message
number
Message
class
EV_ID1
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
channel pair
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
EV_ID2

287
Family: @System
Message block
ALARM_8P
EV_ID3
Message
number
Message
class
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:
Module @1%d@/@2%d@/@3%d@:

Message block
ALARM_8P
Associat
ed
value
Block parameters
Meaning
EV_ID1 / 2 / 3
SUBN_ID
RACK_NO
SLOT_NO
Slot number (byte)
dynamically.
module.
See also
288

Family: @System
5.48 PADP_L0x: Monitoring DP/PA slaves
5.48
PADP_L0x: Monitoring DP/PA slaves
5.48.1
Description of PADP_L00

FB 109
PADP_L00 block I/Os (Page 292)
Area of application
Block PADP_L00 monitors DP/PA field devices operating as DPV0 or DPV1 slaves
downstream of a DP/PA or Y-Link that is operated as a DPV0 slave. The PA field devices must
conform to the PROFIBUS V3.0 profile. There must be individual blocks available for the
diagnostics and signal processing for DP field devices. H systems support only the PA field
devices at an active DP/PA-Link.
Calling OBs
OB 1
Cyclic program
OB 82
OB 85
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:
Block PADP_L00 is integrated in the run sequence downstream of block DPAY_V0.
Parameters are assigned to the MODE_xx input (mode of slot xx of a field device).
The PADP_ADR input (DP/PA slave address downstream of the DP/PA link or Y link) is
configured.
The DPA_M input is interconnected with the DPA_M_xx output of the DPAY_V0 block.
The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the DPAY_V0
block are interconnected with the IN_OUT structures of the same name of PADP_L00.
The QMODF and PA_DIAG outputs are interconnected with the MOD_PAL0 block.

289
Family: @System
Note
to slave family 12.

Block PADP_L00 analyzes all events affecting a DP or PA field device and its slots acyclically.
It generates the relevant DP_MODE or PA_MODE, depending on the slot, and the value status
for the DP or PA signal processing blocks. The permitted PA_MODE (Page 351) is already
defined for the PA signal processing blocks. The DP_MODE must be defined individually for
the DP field device blocks. ALARM_8P is used to report these events. The message function
can be disabled.
The higher-level DPAY_V0 block enables the block to run. The diagnostic event is entered in
the start information (CPU_DIAG) of the OB_BEGIN block.
The data is already evaluated by the link block (DPAY_V0) if diagnostics are required. The
diagnostic information concerning the PA field device is stored in the DPA_M structure. The
structure consists of 2 DWORD (S_01 for module 1 to 16 and S_02 for module 17 to 32), and
1 BOOL (S_ERR = DP/PA field device faulty) variables. Two bits of the DWORD are assigned
to each slot of the DP/PA field device, whereby bit 0 and bit 1 belong to slot 1 of the DP/PA
field device, etc. Slots 1 to 7 are evaluated. The bit states are defined as follows:
Status Bit 0
Status Bit 1
Meaning
There is an input (MODE_xx) for each slot (module) on the DP/PA field device that is used to
read in configuration settings made for the PA field device slots (module) in HW Config.
For DP field devices, the user must do his own encoding at the MODE input.
16#80xxxxxx. The following events are evaluated by block DPAY_V0 and lead to the value
status Invalid value due to a higher-level error (OMODE_xx = 16#40xxxxxx):
Rack failure (OB 86)
(Output parameter QRACKF = TRUE)
Diagnostic interrupt that affects entire field

device (OB 82)
(Output parameter QMODF = TRUE,

if DPA_M.S_ERR = TRUE)
Diagnostic interrupt slot xx that affects a

field device (OB 82):
(Output parameter OMODE_xx =

Module (slot) error-specific DPA_M)
In the event of a diagnostic interrupt, the block reports field-device-specifically to WinCC by

means of ALARM_8P. We distinguish between the field device and its slots; each slot is
assigned a message ID.
290

Family: @System
The Device failure message can be disabled with EM_MSG_D = FALSE.
Redundancy
The higher-level block DPAY_V0 evaluates the redundancy of the DP master systems used
in an H system.
MODE Setting for PA Profiles

You will find additional information in "PA_MODE Settings (Page 351)".
Note
OMODE Structure
Error handling
After a restart or an initial start, the system verifies that the PA field device is available under
its logical base address. A restart (OB100) is reported via the LSB in byte 2 of the
OMODE_xx (Page 351) outputs.
Time response
Not available
Message response
The block signals field device errors using ALARM_8P, and generates the following messages
in the OBs listed below:
OB no.
Start Event
Message
OB 1
Cyclic processing
Repeat the update of ALARM_8P outputs/messages, if

necessary
OB 82
Device error incoming/outgoing

Device module xx error incoming/outgoing
Device module xx incorrect incoming/outgoing
Device module xx missing incoming/outgoing
OB 100
Restart

291
Family: @System

Message texts and associated values for PADP_L00 (Page 293)
5.48.2
I/Os of PADP_L00/PADP_L01/PADP_L02
I/Os
The I/Os of the PADP_L00, PADP_L01 and PADP_L02 blocks are identical save for the number
of MODE_xx and OMODE_xx. The number of monitored slots determines the number of
corresponding I/O parameters.
The default block view in the CFC is identified in the "I/O" column:
I/O name in bold = I/O is visible, standard I/O name = I/O is not visible.
Input parameters
I/O
(parameter)
Meaning
Data type
Defau
lt
DPA_M
DP/PA field device diagnostic information
STRUCT
EN_MSG
1 = enable message
BOOL
EN_MSG_D
1 = enable "Device failure" message
BOOL
EV_ID
Message number
DWORD
MODE_xx
Module mode (xx = 00 - 06 / 00 - 15 / 00 - 31)
WORD
PADP_ADR
DP/PA field device address
BYTE
I/O
(parameter)
Meaning
Data type
Defau
lt
MSG_ACK
WORD
MSGSTAT
WORD
OMODE_xx
Module mode (xx = 00 - 06 / 00 - 15 / 00 - 31)
DWORD
Output parameters
292
PA_DIAG
DWORD
QERR
1 = program error
BOOL

Family: @System
I/O
(parameter)
Meaning
Data type
Defau
lt
QMODF
BOOL
QRACKF
BOOL
I/O
(parameter)
Meaning
Data type
Defau
lt
ACC_MODE
BOOL
CPU_DIAG
CPU diagnostics
STRUCT
RAC_DIAG
1 = DPV1 mode
STRUCT
In-out parameters
5.48.3
Message texts and associated values of PADP_L00

Message block
ALARM_8P
Message
number
Block
parameter
Message
class
EV_ID
QMODF
Device @1%d@/ @2%d@/@3%d@:

Failure
Device @1%d@/ @2%d@/@3%d@:

Module 00 @4W%t#PADP_L00_TXT@
...
8
...
-
Device @1%d@/ @2%d@/@3%d@:

You will find the message texts and their text numbers in the
"Text library for PADP_L00 (Page 360)" section.

293
Family: @System

Message block
ALARM_8P
Associated
value
Block
parameter
Meaning
EV_ID
SUBN_ID
RACK_NO
PADP_ADR
DP/PA device address (byte)
4 - 10
Text number (message 2 - 8) from PADP_L00_TXT
See also
5.48.4

FB 110
Area of application
The PADP_L01 monitors DP/PA field devices that are used as DPV0 or DPV1 slaves,
downstream of a DP/PA or Y link that is used as a DPV0 slave. The PA field devices must
Calling OBs
The block must be installed in the run sequence in the following OBs (this is done automatically
in the CFC):
294
OB 1
Cyclic program
OB 82
OB 85
OB 86
Rack failure
OB 100
Warm restart

Family: @System
Use in CFC
function:
The PADP_L01 block is integrated in the run sequence downstream of block DPAY_V0.
configured.
The outputs QMODF and PA_DIAG are interconnected with the MOD_PAL0 block.
Note
to slave family 12.

can be disabled.
The higher-level DPAY_V0 block enables the block to run. The diagnostic event is entered in
the start information (CPU_DIAG) of the OB_BEGIN block.
Status Bit 0
Status Bit 1
Meaning
There is an input (MODE_xx (Page 341)) for each slot (module) on the DP/PA field device that
is used to read in configuration settings made for the PA field device slots (module) in HW
Config.

295
Family: @System

device (OB 82)



The block reports a diagnostic interrupt to the OS for a specific field device using ALARM_8P.
We distinguish between the field device and its slots; each slot is assigned a message ID.
Redundancy
in an H system.

Note
OMODE structure
Error handling
Time response
Not available
296

Family: @System
Message response
OB no.
Start Event
Message
OB 1
Cyclic processing

necessary
OB 82

OB 100
Restart

5.48.5

Message block
ALARM_8P
Message
number
Block
parameter
Message
class
EV_ID1
QMODF
Device @1%d@/ @2%d@/@3%d@:

Failure
Device @1%d@/ @2%d@/@3%d@:

Device @1%d@/ @2%d@/@3%d@:

Device @1%d@/ @2%d@/@3%d@:

Device @1%d@/ @2%d@/@3%d@:

Device @1%d@/ @2%d@/@3%d@:

EV_ID2
...
EV_ID3
...
...
7

...
-
Device @1%d@/ @2%d@/@3%d@:

297
Family: @System
You will find the message texts and their text numbers in the "Text library for PADP_L01

Message block
ALARM_8P
Associated
value
Block
parameter
Meaning
EV_ID1
SUBN_ID
RACK_NO
PADP_ADR
4-5
SUBN_ID
RACK_NO
PADP_ADR
4 - 10
SUBN_ID
RACK_NO
PADP_ADR
4 - 10
EV_ID2
EV_ID3
See also
5.48.6

FB 111
Area of application
The PADP_L02 monitors DP/PA field devices that are used as DPV0 or DPV1 slaves,
downstream of a DP/PA or Y link that is used as a DPV0 slave. The PA field devices must
298

Family: @System
Calling OBs
The PADP_L02 block must be installed in the run sequence in the following OBs:
OB 1
Cyclic program
OB 82
OB 85
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:
The PADP_L02 block is integrated in the run sequence downstream of block DPAY_V0.
configured.
The QMODF and PA_DIAG outputs are interconnected with the MOD_PAL0 block.

can be disabled.
The higher-level DPAY_V0 block enables the block to run. The event to be evaluated is entered
in the start information (CPU_DIAG) of OB_BEGIN.
Status Bit 0
Status Bit 1
Meaning

299
Family: @System
There is an input (MODE_xx) for each slot (module) on the DP/PA field device that is used to
read in configuration settings made for the PA field device slots (module) in HW Config.

device (OB 82)



The block reports a diagnostic interrupt to WinCC for a specific field device using ALARM_8P.
We distinguish between the field device and its slots; each slot is assigned a message ID.
Redundancy
in an H system.

Note
OMODE Structure
Error handling
300

Family: @System
Time response
Not available
Message response
OB no.
Start Event
Message
OB 1
Cyclic processing
Repeat the update of ALARM_8P outputs/messages,

if necessary
OB 82

OB 100
Restart

5.48.7

Message block
ALARM_8P
Message
number
Block
parameter
EV_ID1
QMODF
Device @1%d@/ @2%d@/@3%d@:

Failure
Device @1%d@/ @2%d@/@3%d@:

Device @1%d@/ @2%d@/@3%d@:

Device @1%d@/ @2%d@/@3%d@:

Device @1%d@/ @2%d@/@3%d@:


Message
class
301
Family: @System
Message block
ALARM_8P
Message
number
Block
parameter
EV_ID2
Device @1%d@/ @2%d@/@3%d@:

...
EV_ID3
Device @1%d@/ @2%d@/@3%d@:

Device @1%d@/ @2%d@/@3%d@:

...
Device @1%d@/ @2%d@/@3%d@:

Device @1%d@/ @2%d@/@3%d@:

...
EV_ID5
class
...
...
EV_ID4
Message
...
Device @1%d@/ @2%d@/@3%d@:

Device @1%d@/ @2%d@/@3%d@:

...
...
Device @1%d@/ @2%d@/@3%d@:

You will find the message texts and their text numbers in
"Text library for PADP_L02 (Page 360)".
Assignment of associated values to the block parameters of PADP_L02

Message block
ALARM_8P
Associated
value
Block
parameter
Meaning
EV_ID1
SUBN_ID
RACK_NO
PADP_ADR
4-7
SUBN_ID
RACK_NO
PADP_ADR
4 - 10
SUBN_ID
RACK_NO
PADP_ADR
4 - 10
SUBN_ID
RACK_NO
PADP_ADR
EV_ID2
EV_ID3
EV_ID4
302

Family: @System
5.49 PADP_L10: Monitoring PA slaves downstream of DPV0 with up to 16 slots
Message block
ALARM_8P
EV_ID5
Associated
value
Block
parameter
Meaning
4 - 10
SUBN_ID
RACK_NO
PADP_ADR
4 - 10
See also
5.49
PADP_L10: Monitoring PA slaves downstream of DPV0 with up to 16

slots
5.49.1

FB 116
Area of application
Block PADP_L10 monitors DPV0 PA field devices with a maximum of 32 slots, which are
operated as DPV0 slaves on a DP master system, either directly or via a DP/PA coupler. The
DP/PA coupler is connected downstream of a DPV1 DP/PA link. The PA field devices must
conform to the PROFIBUS V3.0 profile. H systems support only the PA field devices at an
active DP/PA-Link.
Calling OBs
The block must be installed in the run sequence downstream from the OB_DIAG1 block in the
following OBs (this is done automatically in the CFC):
OB 1
Cyclic program
OB 55
Status interrupt (only if a PA slave is required)
OB 56
Update interrupt (only if a PA slave is required)
OB 57
Vendor-specific interrupt (only if a PA slave is required)
OB 82

303
Family: @System
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:
Block OB_DIAG1 is installed in the run sequence upstream of PADP_L10.
The following are configured, depending on whether the PA field device is connected
directly to a DP master system or downstream of a DP/PA link:
the diagnostic address of the PA field device or of the DADDR DP/PA link
the geographic address (SUBN1_ID, SUBN2_ID, RACK_NO of the PA address of the
PA field device or the DP/PA link)
SLOT_NO = 0 or the geographic address of the PA field device in the DP/PA link
(SLOT0_NO = Slot 0 no. for the PA field device, SLOTS_NO = number of slots of the
PA field device)
SLOTS_NO = number of slots of the PA field device
the PA address of the PA field device (PADP_ADR)
MODE_xx (mode of slot xx of a PA field device)
The CPU_DIAG and CPU_OB_5X OUT structures of OB_BEGIN and RAC_DIAG of
OB_DIAG1 are interconnected with the IN_OUT structures of the same name of PADP_L10.
whose inputs are interconnected with the outputs EN_SUBx (x = number of the DP master
block, EN_Mx (x= number of the PA device) of the DPAY_V1 block, and EN_F of the
OB_DIAG1 block.
EN_DIAG is interconnected with output EN_DIAG of OB_DIAG1.
Output QPERAF is interconnected with input PERAF of MOD_PAX0 or MOD_PAL0.
Output QMODF is interconnected with input MODF of MOD_PAX0 or MOD_PAL0.
Output PA_DIAG is interconnected with input PA_DIAG of MOD_PAX0 or MOD_PAL0.
Note
to slave family 12.
304

Family: @System
Description of the functions

Block PADP_L10 analyzes all events affecting a PA field device acyclically. It generates the
slot-specific MODE (PA_MODE (Page 351)) and the value status for signal processing blocks.
The permitted PA_MODE is defined for PA field devices.
If you are using modular PA field devices (DPV0), the next block (MOD_PAX0/MOD_PAL0)
always reports the events in slot 0 of the PA field device in the DP/PA link. The affected
MOD_PAX0/MOD_PAL0 block is enabled.
How it works
Block PADP_L10 is enabled to run by the higher-level OB_DIAG1 block. The event to be
evaluated is entered in the start information (CPU_DIAG) of OB_BEGIN. Block PADP_L10
checks the geographic address and the number of slots (SLOT_NO) of the PA field device to
determine whether it is responsible for this event.
For a diagnostic event (OB 82, OB 55, OB 56, OB 57), SFB 54 is used to synchronously read
the data from OB_BEGIN.
If diagnostic data could not be read synchronously from OB_BEGIN or when requested by
OB_DIAG1 (EN_DIAG = TRUE), SFB 52 (RDREC) is used to read the current diagnostic data
asynchronously.
The following diagnostic data is interpreted as a higher-level error in the block:
Additional alarm information
Byte no.
DPV1 name
Bit no.
Byte 1 to 6
Byte 7
Byte 8
Value
Info
DDLM_SLAVE_DIAG
Header
Status_Type
Byte 9
Slot_number
Byte 10
Specifier
Bit 7
fixed
Bit 6
fixed
Bit 5 to bit 0
8 or optional
Length of diagnostic data
Bit 7
Status
Bit 6 to bit 0
126
Highest vendorspecific status,

will not be used in future
Slot number of the PB
The PB contains the

diagnostic data.
Bit 7 to bit 2
Reserved
Bit 1 to bit 0
1: status is displayed
depends on the content of

diagnostic data
2: status is not displayed

Byte 11 to 14
Diagnostics
optional
Bytes 11 to 20
With a DPV0 PA field device, the diagnostic data is always assigned to slot 0.
It is also possible to generate slot-specific diagnostics for DPV1 PA field devices. These have
not yet been defined. With a DPV1 field device, only the field-device slot that triggered the
diagnostics is enabled. Evaluation of the coding in the context of higher-level errors in the slotBasic Library (V8.1)
305
Family: @System
specific OMODE_xx (Page 351) outputs is based solely on the diagnostic information at slot
0.
MODE setting for PA profiles (PA_MODE)

For more information, refer to the section: "MODE settings for PA devices (Page 351)".
16#80xxxxxx. The following events lead to the value status "invalid value due to higher-level
error" (OMODE_xx = 16#40xxxxxx):
Failure/return of a field device (OB 83)
Slot-specific diagnostic interrupt (OB 82)
Bytes 11 to 14 of the additional interrupt information are evaluated to form the slot-specific
value status:
Byte
11
12
306
Bit
Mnemonics
Description
Display
class
DIA_HW_ELECTR
Electronic hardware failure
DIA HW MECH
Mechanical hardware failure
DIA_TEMP_MOTOR
Excess motor temperature
DIA TEMP ELECTR
Excess temperature at electronic circuit
DIA MEM CHKSUM
Memory error
DIA_MEASUREMENT
Measurement failure
DIA NOT INIT

DIA_INIT_ERR
Device not initialized

(no auto-calibration)
Auto-calibration error
DIA ZERO ERR
Zero error (limit position)
DIA_SUPPLY
No power supply (electr. pneum.)
DIA CONV INVAL
Invalid configuration
DIA_WARMSTART
Warm start executed
DIA COLDSTART
Complete restart executed
DIA MAINTENANCE
Maintenance necessary
DIA_CHARACT
Invalid identifier
IDENT NUMBER Violation
= 1, if the ID number of
the current cyclic data transfer
and the value of the IDENT NUMBER
parameter of the physical block are different

Family: @System
Byte
Bit
Mnemonics
Description
Display
class
13
DIA_MAINTENANCE_ALARM
Device error
DIA_MAINTENANCE_DEMANDED
Maintenance requested
DIA_FUNCTION_CHECK
Device is in a functional check or in simulation

or under local operator control (maintenance)
DIA_INV_PRO_COND
4 to 7
Reserved
The process conditions do not permit valid

values to be returned.
(Set if quality "Uncertain, process-related, no
maintenance" or "Bad, process-related, no
maintenance")
0 to 4
Reserved
Reserved for PNO use
PROFILE_SPECIFIC_EXTENSION
_AVAILABLE
= 0: For devices with this profile
MANUFACTURER_SPECIFIC
_EXTENSION_AVAILABLE
= 0: No further diagnostic information available

= 1: Further diagnostic information available in
DIAGNOSIS_EXTENSION
14
6
7
EXTENSION_AVAILABLE
Reserved for PNO, default 0
= 0: For devices with this profile
Display class R = incoming / outgoing events.

Display class A = incoming events that are reset by the field device after a few cycles. All
events in byte 11 and the events of bit 0, 1 and 2 in byte 12 lead to the value status Higherlevel error (OMODE_xx (Page 351) = 16#40xxxxxx).
Bytes 11, 12, 13, and 14 are entered in bytes 0 to 3 of the PA_DIAG parameter to generate
messages and MS in the MOD_PAX0/MOD_PAL0 block.
Special features of PA_AO and PA_DO field devices

With the field devices listed above, the PA profiles can be defined at two different slots. In this
case, the driver generator will assign the mode code of the PA field device to the first slot and
the mode code 16#8000 to the second at the corresponding MODE inputs of the block. The
diagnostic information of the first and of the second slot are linked by a logical OR operation,
which allows the generation of a uniform value status for the PA_x block.
Redundancy
system.
OMODE Structure
Addressing
You will find additional information in the "Addressing (Page 353)" section.

307
Family: @System
Error handling
A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx (Page 351) outputs.
Time response
Not available
Message response
Not available

5.49.2
I/Os of PADP_L10
Input parameters
308
I/O
Meaning
Type
Defa
ult
DADDR
Diagnostic address of the PA field device or DP/PA link
INT
DIAG_BUF

personnel)
BOOL
EN_DIAG
BOOL
MODE_xx
Mode slot (xx = 16 - 31)
WORD
PADP_ADR
BYTE
PROF_V30
BOOL
RACK_NO
Address of PA field device or rack number
BYTE
255
SLOT0_NO
Slot number 0 of the field device in the DP/PA or Y link, or

0 if there is no link
BYTE
SLOTS_NO
Number of slots of the field device
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255

Family: @System
5.50 PADP_L10_PN: Monitoring PA slaves downstream of DPV0 with up to 16 slots
Output parameters
I/O
Meaning
Type
Defa
ult
DINFO
Diagnostic status of the PA field device
STRUCT
EN_M_xx
Enable slot (xx = 0 - 31)
BOOL
OMODE_xx
DWORD
PA_DIAG
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QPERAF
BOOL
QRACKF
1 = (Link) rack/station error
BOOL
In/out parameters
I/O
Meaning
Type
Defa
ult
ACC_MODE
BOOL
CPU_DIAG
CPU diagnostics
STRUCT
CPU_OB_5X
STRUCT
RAC_DIAG
PA field device or link diagnostics
STRUCT
5.50
PADP_L10_PN: Monitoring PA slaves downstream of DPV0 with up to

16 slots
5.50.1
Description of PADP_L10_PN

FB 203
I/Os of PADP_L10_PN (Page 310)
Area of application
Block PADP_L10_PN monitors DPV0 PA field devices with a maximum of 16 slots which are
operated as DPV0 slaves on a DP master system, either directly or via a DP/PA coupler. The
DP/PA coupler is connected downstream of an IE/PB link. The PA field devices must conform
to the PROFIBUS V3.0 profile.

309
Family: @System
5.50 PADP_L10_PN: Monitoring PA slaves downstream of DPV0 with up to 16 slots
5.50.2
I/Os of PADP_L10_PN
Input parameters
I/O
Meaning
Type
Defa
ult
DADDR
Diagnostic address of the PN IO device
INT
DIAG_BUF

personnel)
BOOL
EN_DIAG
BOOL
MODE_xx
WORD
PADP_ADR
BYTE
PROF_V30
BOOL
RACK_NO
Rack number
BYTE
255
SLOT0_NO
Slot number 0 of the slave at the IE/PB link
BYTE
SLOTS_NO
Number of slots of the field device
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Output parameters
310
I/O
Meaning
Type
Defa
ult
DINFO
Diagnostic status of the PA field device
STRUCT
EN_M_xx
Enable slot (xx = 0 - 31)
BOOL
OMODE_xx
DWORD
PA_DIAG
DWORD
QERR
1 = program error
BOOL
QMODF
BOOL
QPERAF
BOOL
QRACKF
BOOL

Family: @System
5.51 PDM_MS: Monitoring of the maintenance status
In/out parameters
I/O
Meaning
Type
Defa
ult
ACC_MODE
BOOL
CPU_DIAG_PN
STRUCT
CPU_OB_5X
STRUCT
RAC_DIAG
STRUCT
5.51
PDM_MS: Monitoring of the maintenance status
5.51.1
Description of PDM_MS

FB 81
I/Os of PDM_MS (Page 311)
How it works
The block reports the Maintenance State supplied by PDM via the Maintenance Station.
You will find more detailed information in the section Message texts and associated values of
PDM_MS (Page 312).
5.51.2
I/Os of PDM_MS
Input parameters
I/O (parameter)
Meaning
Type
Default
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = enable message
BOOL

311
Family: @System
5.51 PDM_MS: Monitoring of the maintenance status
I/O (parameter)
Meaning
Type
Default
EV_IDx
Message number (x = 1, 2)
DWORD
MS
Maintenance status
DWORD
RUNUPCYC
Number of replacement run cycles
INT
CYCL_UPD
1 = Cyclic update active
BOOL
I/O (parameter)
Meaning
Type
Default
MSGSTATx
Message error information (x = 1, 2)
WORD
O_MS
Maintenance status
DWORD
QERR
1 = program error
BOOL
Output parameters
Additional information is available in the section:
Message texts and associated values of PDM_MS (Page 312)
5.51.3
Message texts and associated values of PDM_MS
Messaging
The statuses are generated with ALARM_8P for messages requiring acknowledgment, and
with NOTIFY_8P for those not requiring acknowledgment. The message function can be
disabled by setting EN_MSG = 0. In this case MS = 8 is set.

The process control messages of ALARM_8P with ED_ID1 are assigned as follows:
Message block
ALARM_8P
EV_ID1
Message number
Message class
Uncertain diagnostics
SA
Uncertain, maintenance demanded F
Bad, device out of service
No message
No message
No message
The process control messages of ALARM_8P with ED-ID2 are assigned as follows:
312

Family: @System
5.52 PO_UPDAT: Output Process Image
Message block
NOTIFY_8P
Message number
Message class
EV_ID2
Device passivated
SA
No message
Local operation/functional check
SA
Simulation
SA
Configuration change
SA
No message
No message
No message
Additional information is available in the section: Message Classes (Page 355)
5.52
PO_UPDAT: Output Process Image
5.52.1
PO_UPDAT: Output Process Image

FC 279
Area of application
The PO_UPDAT block safeguards the output module functions "Hold last value" and "Apply
substitute value" when a CPU is restarted (OB 100).
Run Sequence
With the "Generate module drivers" CFC function, the PO_UPDAT block is automatically
installed in OB 100 at the end.
Description of Functions
On a CPU restart (OB 100), the CH_DO and CH_AO blocks write the start values to the process
image. The PO_UPDAT block sends all process images (partitions) to the modules at the end
of OB 100 in order for these values to be active immediately when the CPU goes into RUN.
Output PO_MAP indicates the process image partitions which have been updated or are used
in the system (BIT0: Process image 0, BIT15: Process image partition 15).

313
Family: @System
5.53 PS: Power supply monitoring
5.53
PS: Power supply monitoring
5.53.1
Description of PS

FB 89
PS block I/Os (Page 316)
Area of application
The PS block monitors the status of a rack power supply, and reports the associated error
events.
Calling OBs
The PS block must be installed in the run sequence of the following OBs:
OB 1
Cyclic program
OB 81
Power supply error
OB 83
OB 100
Warm restart
Use in CFC
function:
The block is installed in the run sequence downstream of the RACK block.
The SLOT_NO input (slot number of the power supply) is configured.
Its inputs are interconnected with the output EN_SUBx of the OB_BEGIN block, the output
EN_Rxxx of the SUBNET block and the output EN_Mxx of the RACK block.
are interconnected with the IN_OUT structures of the same name of the PS block.
314

Family: @System

The PS block reports events of the power supply error OB 81 and OB 83 relating to the power
supply module. The module is installed to supply power to the central rack, and to each
expansion rack.
Note
Note the following:
If a battery fails, the battery must always be replaced with the power supply turned on.
Then press the "FMR" button. In all other situations, the block does not reset a reported
error.
For redundant power supply modules in a rack with a standard CPU, a corresponding
message is sent for both power supply modules in the event of a battery error or power
supply error. You can tell which module is affected by the "BATTF" LED that lights up.
Redundancy
In a redundant system, the block is also installed extra for the power supply of the redundant
rack.
Error handling
The error handling of the block is limited to the evaluation of the error information of ALARM_8P.
Refer to the section "Error information of output parameter MSG_STAT (Page 353)" for
additional information on error handling.
The PS block initializes the messages of the ALARM_8P.
Overload behavior
Not available
Time response
You will find additional information in the "Message response" section.
Message response
After OB 81 or OB 83 is called, the block analyzes the status of the power supply of the rack
assigned to it. It generates the "Backup battery failure", "Backup voltage failure" and "24 V
supply failure" or "Module removed" or "Wrong or faulty module" messages with ALARM_8P.

315
Family: @System

manual.
Message texts and associated values of PS (Page 317)
5.53.2
I/Os of PS
Input parameters
I/O
(parameter)
Meaning
Data type
Default
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = enable message
BOOL
EV_ID
Message number
DWORD
MS
Maintenance status
DWORD
SLOT_NO
Slot number of the power supply
BYTE
I/O
(parameter)
Meaning
Data type
Default
MSG_STAT
WORD
O_MS
Maintenance status
DWORD
Output parameters
316

Family: @System
In/out parameters
I/O
(parameter)
Meaning
Data type
CPU_DIAG
STRUCT
RAC_DIAG
System structure
STRUCT
Default
Message texts and associated values of PS (Page 317)
5.53.3
Message texts and associated values of PS

Message No.
Message class
@1%d@/ @2%d@/ @3%d@: Backup battery failure
@1%d@/ @2%d@/ @3%d@: Backup voltage failure
@1%d@/ @2%d@/ @3%d@: 24 V power supply failure
Module @1%d@/@2%d@/@3%d@: Removed
Module @1%d@/@2%d@/@3%d@: wrong or faulty
No message
No message
No message

Associated
value
Block parameters
DP master system ID of the rack of the power supply (RAC_DIAG.SUBN_ID)
Rack number of the power supply (RAC_DIAG.RACK_NO)
Slot number of the power supply (SLOT_NO)
See also

317
Family: @System
5.54 RACK: Rack monitoring
5.54
RACK: Rack monitoring
5.54.1
Description of RACK

FB 107
RACK block I/Os (Page 321)
Area of application
The RACK block monitors the status of a rack, and reports the associated error events.
Calling OBs
The block is installed in the run sequence in the following OBs:
OB 1
Cyclic program
OB 70
OB 72
OB 81
Power supply error
OB 82
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:
The RACK block is installed in the run sequence downstream of the SUBNET block.
The RACK_NO, DADDR, SUBN1_ID, SUBN2_ID, and SUBN_TYP inputs are configured.
whose inputs are interconnected to the EN_SUBx output of the OB BEGIN block, and to
the EN_Rxxx output of the SUBNET block.
block are interconnected with the IN_OUT structures of the same name of the RACK block.

The RACK block generates a process control error message for the OS in the event of
redundancy losses and rack/station failures. It also indicates internal errors of the rack/station
318

Family: @System
(SUBN1ERR, SUBN2ERR), and of the preferred channel (SUBN1ACT, SUBN2ACT) if there
are active DP slaves at its outputs. The output structure RAC_DIAG contains the geographic
address of the rack, and the group error information RACK_ERR.
If RACK_ERR = 1, the corresponding rack is not available.
The block is installed in the OBs listed above once at each station or local I/O device. The
SUBNET block enables the runtime group that contains the RACK block. Start and diagnostic
information is read from the CPU_DIAG IN_OUT structure, which is interconnected with the
CPU_DIAG structure of the OB_BEGIN block. The RACK block has one enable output for each
rack (station) slot.
The RACK block generates the number of a corresponding message (see "Message
Response") on the basis of the start information of the calling OBs if the current block is affected.
The block evaluates error events, and uses the diagnostic address DADDR of the DP slave
to determine the currently active preferred channel (SUBN1ACT, SUBN2ACT) of redundant
PROFIBUS DP interface circuits.
to CPU 1) inputs online, you must set input ACC_ID = TRUE. to update the output values.
Redundancy
In H systems with distributed I/Os, the RACK block supports redundancy of the DP Master
systems. If you want to use this function, you must configure the SUBN1_ID (connection to
CPU 0) and SUBN2_ID (connection to CPU 1) inputs of the RACK block with the numbers of
the redundant DP master systems. If there is no redundancy, the remaining input must be set
to the (default) value 16#FF.
Note
With redundant CPU racks, the two RACK blocks inserted in the system chart are only
responsible for enabling lower-level block chains. Their maintenance status MS is therefore
irrelevant. The "Good" and "Not redundant" state is always shown in the associated faceplate
and block icon because the bits 0 to 16 of the MS are always "0" in this case.
Error handling
You will find additional information about this in "Error information of output parameter
MSG_STAT (Page 353)".
The RACK block initializes ALARM_8P messages. It checks availability of the station and, in
H systems, determines the preferred channel of the station.
The SUB_DIAG.V1_MODE structure (0 = compatibility mode, 1 = DPV1 mode) is transferred
to the RAC_DIAG.V1_MODE structure.

319
Family: @System
Overload behavior
The RACK block counts the OB 86 calls (except in the case of a DP master system failure;
see SUBNET block). The counter is reset in OB1. If more than two OB 86 events occur in
succession before the cycle control point (OB 1) is reached, these will be rejected and the
message "Station...: Multiple failure" is output. When an OB 86 call is rejected, the rack (station)
is registered as having failed.
Time response
See "Message Response"
Message response
After it is called by OB 70, OB 72, OB 85 or OB 86, the block analyzes the status of its assigned
CPU, DP master and DP slave. If the rack (station) loses redundancy or fails, the block outputs
the corresponding messages by broadcasting an ALARM_8P. The message function can be
disabled by setting EN_MSG = FALSE.
The block generally reports only the events that were originally generated in the rack that it
monitors. Redundancy loss and station failures which are caused by the failure of a DP master
or CPU are initially neither signaled nor indicated at the SUBN1ERR and SUBN2ERR outputs.
The DELAY input is used to delay the outputting of error messages for an outgoing, higherpriority error. For example, if the RACK block recognizes an outgoing error at an interconnected
DP master, it initially assumes that there is a faulty assigned DP slave in the rack it monitors,
and sets the corresponding output SUBNxERR. The error status is not reset until the DP slave
returns (in this case: OB 86, OB 70). The RACK blocks suppress the potential slave failure
states for DELAY seconds so as not to trigger a surge of messages from DP slaves which are
not yet synchronized when the master returns. An error message is only output to the OS when
the DP slave has not reported its return before this delay time has expired.
The RACK block generates the following messages in the OBs listed below:
OB
Start event
Message
OB 1
Cyclic processing

necessary
OB 70
Redundancy loss
Station redundancy loss/return
OB 81
Power supply error
OB 85
Station failure, incoming/outgoing
OB 86
Rack failure
Station failure, incoming/outgoing
OB 100
Restart

320

Family: @System
manual.
Message texts and associated values of RACK (Page 322)
5.54.2
I/Os of RACK
Input parameters
I/O
(parameter)
Meaning
Data type
Default
DADDR
Diagnostic address of the DP slave
INT
DIAG_BUF

personnel)
BOOL
DELAY
Interrupt delay (s)
INT
15
EN_MSG
1 = enable message
BOOL
EV_ID
Message number
DWORD
MS
Maintenance status
DWORD
RACK_NO
Rack number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
I/O
(parameter)
Meaning
Data type
Default
EN_Mxx
1 = Enable module xx (xx = 0 - 63)
BOOL
MSG_STAT
WORD
O_MS
Maintenance status
DWORD
RAC_DIAG
System structure
STRUCT
SUBN1ACT
BOOL
SUBN1ERR
1 = Error in slave 1
BOOL
Output parameters

321
Family: @System
I/O
(parameter)
Meaning
Data type
Default
SUBN2ACT
BOOL
SUBN2ERR
BOOL
I/O
(parameter)
Meaning
Data type
Default
ACC_ID
BOOL
CPU_DIAG
STRUCT
SUB_DIAG
OB start information
STRUCT
In/out parameters
Message texts and associated values of RACK (Page 322)
5.54.3
Message texts and associated values of RACK

Message no.
Message class
Station @1%d@/ @3%d@: Redundancy loss
Station @1%d@/ @3%d@: Failure
No message
No message
No message
Station @1%d@/ @3%d@: Multiple failure
322
Associated value
Block parameters

Family: @System
5.55 RACK_PN: Rack monitoring
See also
5.55
RACK_PN: Rack monitoring
5.55.1
Description of RACK_PN

FB 90
I/Os of RACK_PN (Page 323)
Area of application
The RACK_PN block monitors the status of a rack, and reports the associated error events.
Message texts and associated values of RACK_PN (Page 325)
5.55.2
I/Os of RACK_PN
Input parameters
I/O
(parameter)
Meaning
Data type
Default
DADDR
Diagnostics address of the PN IO device
INT
DELAY
Interrupt delay (s)
INT
15
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = enable message
BOOL
EV_ID
DWORD

323
Family: @System
I/O
(parameter)
Meaning
Data type
Default
EV_ID1
DWORD
FEATURE_01
Property of the hardware parameter 01
WORD
IM_RED
1 = IM redundant
BYTE
MS
Maintenance status
DWORD
PNIO_ADR
Diagnostics address of the PN-IO interface
INT
PORT1_ADR
Diagnostics address of PORT 1
INT
PORT1_CONNECT
Port 1 Connection Status
BYTE
PORT2_ADR
Diagnostics address of PORT12
INT
PORT2_CONNECT
Port 2 Connection Status
BYTE
RACK_NO
Rack number
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Meaning
Data type
Default
EN_Mxx
1 = Enable rack xx (xx = 0 - 63)
BOOL
MSGSTATx
Status output of ALARM_8P_x (x = 1-2)
WORD
O_MS
Maintenance status
DWORD
QMSGERx
ERROR message of ALARM_8P_x (x = 1 - 2)
BOOL
RAC_DIAG
System structure
STRUCT
SUBN1ACT
BOOL
SUBN1ERR
BOOL
SUBN2ACT
BOOL
SUBN2ERR
BOOL
I/O
(parameter)
Meaning
Data type
Default
ACC_ID
BOOL
CPU_DIAG_PN
STRUCT
SUB_DIAG
OB start information
STRUCT
Output parameters
I/O
(parameter)
In/out parameters
Message texts and associated values of RACK_PN (Page 325)
324

Family: @System
5.55.3
Message texts and associated values of RACK_PN

The process control messages of ALARM_8P with EV_ID are assigned as follows:
Message no.
Message class
No message
No message
7
8
No message
Station @1%d@/ @3%d@: Multiple failure
Associated values of ALARM_8P with EV_ID

Associated value
Block parameter
Data type
BYTE
ID of the redundant PN IO system (SUBN2_ID)
BYTE
BYTE
Message no.
Message class
Station @4%d@/ @3%d@: Port 1 error
Station @4%d@/ @3%d@: Port 2 error
Station @4%d@ @3%d@: Uncertain, maintenance

demanded
Station @4%d@/ @3%d@: Good, maintenance required
No message
No message
No message
No message

325
Family: @System
5.56 RED_F: Status processing of redundant F modules
Associated value
Block parameter
Data type
BYTE
BYTE
BYTE
WORD
5.56
RED_F: Status processing of redundant F modules
5.56.1
Description of RED_F

FC 289
RED_F block I/Os (Page 328)
Area of application
The RED_F block is used to set up redundant F modules in safety mode.
Calling OBs
The block must be installed in the same OB before the OR block. It is also installed in OB 100.
Use in CFC
function:
The RED_F block is installed before the OR block in its OB.
the primary module.
The RACKF1 input is interconnected with the QRACKF output of the MOD_x block of the
primary module.
The RACKF2 input is interconnected with the QRACKF output of the MOD_x block of the
redundant module.
326

Family: @System
The MS1 input is interconnected with the O_MS output of the MOD_x block of the primary
module.
The MS2 input is interconnected with the O_MS output of the MOD_x block of the redundant
module.
The ACTIV_H and ACTIV_L outputs are interconnected with the inputs with the same name
in the OR block.
The CH_INF_H and CH_INF_L outputs are interconnected with the inputs with the same
name in the OR block.
The RETURN_VAL output is interconnected with the RED_STAT input of the OR block.
The MODUL_STATUS_WORD output is interconnected with the MOD_STAT input of the
OR block.

The RED_F block processes the status of all channels cyclically based on the outputs
OMODE_xx or the MOD_x blocks and then forms the information on redundancy of the OR
blocks.
Addressing
Not available
Error handling
Not available
Not available
Time response
Not available
Message response
Not available


327
Family: @System
5.56.2
I/Os of RED_F
I/O name in bold characters = I/O is visible; I/O name in standard characters = I/O is
hidden.
Input parameters
I/O
(parameter)
Meaning
Data type
Default
MODE1_xx
Channel mode (xx = 00 31)

on the primary module
DWORD
MODE2_xx
Channel mode (xx = 00 31)

on the redundant module
DWORD
MS1
Maintenance status (MS) 1
BOOL
MS2
Maintenance status (MS) 2
BOOL
RACKF1
1 = error rack 1
BOOL
RACKF2
1 = error rack 2
BOOL
Meaning
Data type
Default
Output parameters
I/O
(parameter)
ACTIV_H
BOOL
ACTIV_L
BOOL
CH_INF_H
1 = channel with more significant address is active
DWORD
CH_INF_L
1 = channel with less significant address is active
DWORD
MODUL_STATUS_WORD
Status information
WORD
RETURN_ VAL
Error information
INT
328

Family: @System
5.57 SUBNET: DP master system monitoring
5.57
SUBNET: DP master system monitoring
5.57.1
Description of SUBNET

FB 106
SUBNET block I/Os (Page 332)
Area of application
The SUBNET block is used to shorten acyclic OB processing times. Only the blocks that are
actually affected can be called in the case of an acyclic event.
Calling OBs
The SUBNET block must be installed in the run sequence in the following OBs:
OB 1
Cyclic program
OB 55
Status interrupt (only if a DP/PA slave is required)
OB 56
Update interrupt (only if a DP/PA slave is required)
OB 57
Vendor-specific alarm (only if a DP/PA slave is required)
OB 70
OB 72
OB 81
Power supply error
OB 82
OB 83
OB 85
OB 86
Rack failure
OB 100
Warm restart
Use in CFC
function:
Runtime groups with driver/system blocks are created and organized by rack.
The SUBN1_ID, SUBN2_ID and SUBN_TYP inputs are configured.
The EN_Rxxx outputs are interconnected with the relevant blocks (e.g., RACK).
The IN_OUT structure CPU_DIAG is interconnected with the OUT structure of the
OB_BEGIN block.

329
Family: @System
The IN_OUT structure SZL_71 is interconnected with the OUT structure of the OB_BEGIN
block.
The OUT structure SUB_DIAG is interconnected with the IN_OUT structures of the affected
blocks (such as RACK).

The SUBNET block monitors a DP master system, and enables the blocks (such as RACK)
for processing the connected DP slaves (such as ET 200M). Corresponding messages are
generated, and the SUBN1ERR and SUBN2ERR outputs are set if a DP master system fails
or loses redundancy. The SUB_DIAG output structure contains the geographic address of the
DP Master system 1 (and of DP Master system 2 in H systems), as well as the group error
information SUBN0_ERR (for DP master system 1) and SUBN1_ERR (for DP master system
2). If SUBN0_ERR = 1 or SUBN1_ERR = 1, the corresponding DP master system is not
available.
The SUBNET block is installed in each connected DP master system or in the OBs listed above
once for the local I/O devices. It is enabled by OB_BEGIN. Start and diagnostic information is
read from the CPU_DIAG structure. It is interconnected with the CPU_DIAG structure of the
OB_BEGIN. The SUBNET block is assigned one enable output for each connectable rack or
DP Master system (for each expansion rack for central I/Os). It uses the start information of
the calling OB to determine whether the reported event occurred at its DP master (or at the
central I/O), and then sets the output for the affected rack or DP master system (EN_Rxxx).
If redundant DP master systems are used (for H CPUs only), a rack (such as ET 200M) is
connected to the two DP masters, and is assigned the same station number at both. The
SUBNET block has two input parameters (SUBNx_ID), and the type identifier SUBN_TYP for
this function. If the integrated interface of the CPU module is the DP master, SUBN_TYP =
FALSE, otherwise SUBN_TYP = TRUE.
The MASTER_0 and MASTER_1 outputs indicate which CPU is currently the master.
If a DP master fails, the system sets all EN_Rxxx = TRUE, and reports a redundancy loss or
failure. The return of redundancy or the DP master is reported when a failed DP slave has
reestablished the connection.
The status of the DP master system, the set SUBNx_ID and type identifier are saved in the
output structure SUB_DIAG.
If a "power supply error" (OB 81) event occurs, the SUBNET block will enable only those RACK
blocks that are expansion racks, which is indicated by SUBNx_ID = 0.
to CPU 1) inputs online, you must set input ACC_ID = TRUE. to update the output values.
Redundancy
The SUBNET block supports redundancy of DP master systems of the 414-H/417-H CPU if
distributed I/Os are used. To use this function, you must configure the SUBN1_ID (connection
to CPU 0) and SUBN2_ID (connection to CPU 1) inputs with the numbers of the redundant DP
master systems. If there is no redundancy, the remaining input must be assigned the value
16#FF (default).
330

Family: @System
Error handling
Startup/initial startup behavior

The SUBNET block initializes the messages of ALARM_8P.
The operating mode of the DP Master system is checked, and entered in the
SUB_DIAG.V1_MODE structure with SSL 0X90H (0 = compatibility mode, 1 = DPV1 mode).
If DPV1 mode is active, the CPU_DIAG.MODE_V1 structure is also set to TRUE.
Overload behavior
The SUBNET block counts the OB 86 calls (failures only). The counter is reset in OB1. If more
than two OB 86 failure events occur in succession before the cycle control point (OB1) is
reached, these are rejected and a message "Failure OB 86 DP master system:x" is output. If
an OB 86 call is rejected, the DP master system is registered as having failed.
Time response
Not available
Message response
After being called by an OB 86, OB 70 and OB 72, the block analyzes the status of its assigned
DP master system, and generates the relevant messages for redundancy loss or DP master
system failure by broadcasting an ALARM_8P.
The SUBNET block generally reports only events triggered in the DP master system it monitors.
Exception: If a CPU fails in the H system, the following messages are generated:
in a non-redundant DP master system: DP master failure message
in a redundant DP master system: DP master redundancy loss message

manual.
Message Texts and associated values of SUBNET (Page 333)

331
Family: @System
5.57.2
I/Os of SUBNET
Input parameters
I/O
(parameter)
Meaning
Data type
Defau
lt
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = enable message
BOOL
EV_ID
Message number
DWORD
MS
Maintenance status
DWORD
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
I/O
(parameter)
Meaning
Data type
Defau
lt
EN_Rxxx
1 = Enable rack (xxx = 0 - 127)
BOOL
MASTER_0
BOOL
MASTER_1
BOOL
MSG_STAT
WORD
O_MS
Maintenance status
DWORD
SUB_DIAG
STRUCT
SUBN1ERR
BOOL
SUBN2ERR
BOOL
I/O
(parameter)
Meaning
Data type
Defau
lt
ACC_ID
BOOL
CPU_DIAG
CPU diagnostics
STRUCT
Output parameters
In/out parameters
332

Family: @System
I/O
(parameter)
Meaning
Data type
CPU_OB_5X
STRUCT
SZL_71
System structure SZL71
STRUCT
Defau
lt
Note
The maximum number of racks is determined by the address volume of PROFIBUS. All
available CPUs can thus be used. The entire address volume is used by the CPU 417-4.
Message Texts and associated values of SUBNET (Page 333)
5.57.3
Message texts and associated values of SUBNET

Message no.
Message class
DP master @1%d@: Redundancy loss
DP master @2%d@: Redundancy loss
DP master @1%d@: Failure
DP master @2%d@: Failure
DP master @2%d@: Multiple failure

Associated value
Block parameters
Multiple failure, ID of DP master system
See also

333
Family: @System
5.58 SUBNET_PN: Monitoring of the PN IO system
5.58
SUBNET_PN: Monitoring of the PN IO system
5.58.1
Description of SUBNET_PN

FB 82
I/Os of SUBNET_PN (Page 334)
Area of application
The SUBNET_PN block is used to reduce acyclic OB processing times. Only the blocks that
are actually affected can be called in the case of an acyclic event.
5.58.2
I/Os of SUBNET_PN
Input parameters
334
I/O
(parameter)
Meaning
Data type
Defa
ult
DADDR
Diagnostic address of the PN IO device - primary

subnet
INT
DADDR_1
Diagnostic address of the PN IO device - redundant

subnet
INT
DIAG_BUF

personnel)
BOOL
EN_MSG
1 = enable message
BOOL
EV_ID
DWORD
EV_ID1
DWORD
MS
Maintenance status
DWORD
PNIO_ADR
Diagnostic address of PN IO interface - primary subnet INT
PORT1_ADR
Diagnostic address of PORT 1 - primary subnet
INT
PORT2_ADR
Diagnostic address of PORT 2 - primary subnet
INT
PORT2_CONNECT
Port 2 connection status - primary subnet
BYTE
PNIO_ADR_1
Diagnostic address of PN IO interface - redundant

subnet
INT
PORT1_ADR_1
Diagnostic address of PORT 1 - redundant subnet
INT

Family: @System
I/O
(parameter)
Meaning
Data type
Defa
ult
PORT1_CONNECT_1
Port 1 connection status - redundant subnet
BYTE
PORT2_ADR_1
Diagnostic address of PORT 2 - redundant subnet
INT
PORT2_CONNECT_1
Port 2 connection status - redundant subnet
BYTE
SUBN_TYP
BOOL
SUBN1_ID
BYTE
255
SUBN2_ID
BYTE
255
Output parameters
I/O
(parameter)
Meaning
Data type
Defa
ult
EN_Rxxx
1 = Enable rack (xxx = 0 - 255)
BOOL
MASTER_0
BOOL
MASTER_1
BOOL
MSGSTATx
WORD
O_MS
Maintenance status
DWORD
QMSGERx
ERROR message of ALARM_8P_x (x = 1 - 2)
BOOL
SUB_DIAG
STRUCT
SUBN1ERR
BOOL
SUBN2ERR
BOOL
I/O
(parameter)
Meaning
Data type
Defa
ult
ACC_ID
BOOL
CPU_DIAG_PN
CPU diagnostics system structure
STRUCT
CPU_OB_5X_PN
STRUCT
SZL_71
System structure SZL71
STRUCT
In/out parameters
Message texts and associated values of SUBNET_PN (Page 336)

335
Family: @System
5.58.3
Message texts and associated values of SUBNET_PN

The process control messages of ALARM_8P with EV_ID are assigned as follows:
Message no.
Message class
PN IO system @1%d@: Redundancy loss
PN IO system @2%d@: Redundancy loss
PN IO system @1%d@: Failure
PN IO system @2%d@: Failure
PN IO system @2%d@: Multiple failure
No message
No message
Associated values of ALARM_8P with EV_ID

Associated value
Block parameter
Data type
BYTE
BYTE
ID of the multiple failure PN IO system
BYTE
CPU rack number
BYTE
Message no.
Message class
PN IO system @1%d@: Port 1 error
PN IO system @1%d@: Uncertain, maintenance demanded
PN IO system @1%d@: Good, maintenance required
PN IO system @2%d@: Uncertain, maintenance demanded
PN IO system @2%d@: Good, maintenance required
336

Family: @System
Associated value
Block parameter
Data type
BYTE
BYTE
WORD

337
Internal block
6.1
ChkREAL: Internal Block

FC260
This block is a system block and is only used internally. There is therefore no help available
for it.
6.2
QC_CHNG: Internal block

FB 135
This block is a system block and is only used internally. There is therefore no help available
for it.

339
Appendix
7.1
MODE settings for FF devices

MODE_xx input parameters are available for up to 32 values of a FF field device.
7.2
Block
I/O (parameters)
(cyclic data)
permitted combinations
and sequence
Input (I)/Output (O)

(PLS view)
MODE 16#xxyy
O=xx, I=yy
Analog input (FbAnIn)
OUT
16#0001
Analog output (FbAnOu)
SP
16#0100
Discrete input (FbDiIn)
OUT_D
16#0002
Discrete output (FbDiOu)
SP_D
16#0400
MODE settings for SM modules
Measuring range coding of the analog input modules

Depending on the measuring-range coding of the analog input modules, the parameter
MODE_xx (measuring-range coding) corresponding to the channel must be specified in
accordance with the table. When thermocouples are used there are various options for
combining the measuring type (coding A) with the measuring range (coding B). In this case,
the MODE_xx parameter must be calculated according to the following formula and the result
written to the MODE input as an INTEGER value:
Measuring range coding = 256 coding A + coding B
Please note: The table shows codes A and B in binary format, and as the result the measuring
range coding as a hexadecimal number.
Measuring type
Coding
(A)
Measuring range
Code (B) MODE

(256A+B)
2#0001
25 mV
2#1010
16#010A
50 mV
2#1011
16#010B
80 mV
2#0001
16#0101
250 mV
2#0010
16#0102
500 mV
2#0011
16#0103
1V
2#0100
16#0104
2.5 V
2#0101
16#0105
5V
2#0110
16#0106
Deactivated
Voltage

16#0000
341
Appendix
7.2 MODE settings for SM modules
Measuring type
4-wire measuring transducer
2#0010
Measuring range
Code (B) MODE

(256A+B)
1 to 5 V
2#0111
16#0107
0 to 10 V
2#1000
16#0108
10 V
2#1001
16#0109
100 mV
2#1100
16#010C
3.2 mA
2#0000
16#0200
5 mA
2#0101
16#0205
10 mA
2#0001
16#0201
0 to 20 mA
2#0010
16#0202
4 to 20 mA
2#0011
16#0203
20 mA
2#0100
16#0204
HART interface
2#0111
4 to 20 mA (variant 0) OMODE
settings for SM modules
(Page 351)
2#1100
16#070C
2-wire measuring transducer
2#0011
0 to 20 mA
2#0010
16#0302
4 to 20 mA
2#0011
16#0303
20 mA
2#0100
16#0304
Resistor 4-wire connection
Thermocouple + linear, 4-wire

connection
342
Coding
(A)
2#0100
2#0101
2#0110
2#1000
48
2#0000
16#0400
150
2#0010
16#0402
300
2#0100
16#0404
600
2#0110
16#0406
1000
2#0111
16#040E
3000
2#0111
16#0407
6000
2#1000
16#0408
PTC
2#1111
16#040F
48
2#0000
16#0500
150
2#0010
16#0502
300
2#0100
16#0504
600
2#0110
16#0506
1000
2#0111
16#050E
3000
2#0111
16#0507
6000
2#1000
16#0508
PTC
2#1111
16#050F
48
2#0000
16#0600
150
2#0010
16#0602
300
2#0100
16#0604
600
2#0110
16#0606
1000
2#0111
16#060E
3000
2#0111
16#0607
6000
2#1000
16#0608
PTC
2#1111
16#060F
Pt 100 climate range
2#0000
16#0800
2#0111
16#0807

Appendix
Measuring type

Coding
(A)
Measuring range
Code (B) MODE

(256A+B)
2#1000
16#0808
2#1001
16#0809
Ni 100 climate range
2#0001
16#0801
Ni 1000/LG-Ni 1000 climatic

range
2#1010
16#080A
Pt 100 standard range
2#0010
16#0802
2#0011
16#0803
2#0100
16#0804
2#0101
16#0805
Ni 100 standard range
2#1011
16#080B
Ni 1000/LG-Ni 1000 standard

range
2#0110
16#0806
2#1100
16#080C
2#1101
16#080D
Cu 10 climate range
2#1110
16#080E
Cu 10 standard range
2#1111
16#080F
2#10000 16#0810
2#10001 16#0811
2#10010 16#0812
2#10011 16#0813
Pt 10 GOST climatic
2#10100 16#0814
Pt 10 GOST standard (TC =

3910)
2#10101 16#0815
Pt 50 GOST climatic
2#10110 16#0816

3910)
2#10111 16#0817
Pt 100 GOST climatic
2#11000 16#0818

3910)
2#11001 16#0819
2#11010 16#081A

3910)
2#11011 16#081B
Cu 10 GOST climatic
2#11100 16#081C
Cu 10 GOST standard (TC =

426)
2#11101 16#081D
Cu 50 GOST climatic
2#11110 16#081E

426)
2#11111 16#081F
Cu 100 GOST climatic
2#10000 16#0820
0

426)
2#10000 16#0821
1
Ni 100 GOST climatic
2#10001 16#0822
0
343
Appendix
Measuring type

connection
Coding
(A)
2#1001
Measuring range
Code (B) MODE

(256A+B)
Ni 100 GOST standard
2#10001 16#0823
1

3850)
2#10101 16#0855
01

3850)
2#10101 16#0857
11

3850)
2#10110 16#0859
01

3850)
2#10110 16#085B
11

428)
2#10011 16#089D
101

428)
2#10011 16#089F
111

428)
2#10100 16#08A1
001
2#0000
16#0900
2#0111
16#0907
2#1000
16#0908
2#1001
16#0909
2#0001
16#0901

range
2#1010
16#090A
2#0010
16#0902
2#0011
16#0903
2#0100
16#0904
2#0101
16#0905
2#1011
16#090B

range
2#0110
16#0906
Ni 120 standard range (variant

0)
2#1100
16#090C
Ni 120 climate range (variant 0) 2#1101
16#090D
KTY83/110 (variant 1) OMODE

(Page 351)
KTY84/130 (variant 1) OMODE
(Page 351)
344
Cu10 climate range
2#1110
16#090E
Cu10 standard range
2#1111
16#090F
2#10000 16#0910
2#10001 16#0911
2#10010 16#0912

Appendix
Measuring type

connection

Coding
(A)
2#1111
Measuring range
Code (B) MODE

(256A+B)
2#10011 16#0913
Pt 10 GOST climatic
2#10100 16#0914

3910)
2#10101 16#0915
Pt 50 GOST climatic
2#10110 16#0916

3910)
2#10111 16#0917
2#11000 16#0918

3910)
2#11001 16#0919
2#11010 16#091A

3910)
2#11011 16#091B
Cu 10 GOST climatic
2#11100 16#091C

426)
2#11101 16#091D
Cu 50 GOST climatic
2#11110 16#091E

426)
2#11111 16#091F
Cu 100 GOST climatic
2#10000 16#0920
0

426)
2#10000 16#0921
1
Ni 100 GOST climatic
2#10001 16#0922
0
Ni 100 GOST standard
2#10001 16#0923
1

3850)
2#10101 16#0955
01

3850)
2#10101 16#0957
11

3850)
2#10110 16#0959
01

3850)
2#10110 16#095B
11

428)
2#10011 16#099D
101

428)
2#10011 16#099F
111

428)
2#10100 16#09A1
001
2#0000
16#0F00
2#0111
16#0F07
2#1000
16#0F08
2#1001
16#0F09
345
Appendix
Measuring type
Thermocouple, linear, reference

temperature 0 C / no reference
point
Thermocouple, linear, reference

temperature 50 C
346
Coding
(A)
2#1010
2#1011
Measuring range
Code (B) MODE

(256A+B)
2#0001
16#0F01

range
2#1010
16#0F0A
2#0010
16#0F02
2#0011
16#0F03
2#0100
16#0F04
2#0101
16#0F05
2#1011
16#0F0B

range
2#0110
16#0F06
2#1100
16#0F0C
2#1101
16#0F0D
Cu10 climate range
2#1110
16#0F0E
Cu10 standard range
2#1111
16#0F0F
2#10000 16#0F10
2#10001 16#0F11
2#10010 16#0F12
2#10011 16#0F13
Type B [PtRh-PtRh]
2#0000
16#0A00
Type N [NiCrSi-NiSi]
2#0001
16#0A01
Type E [NiCr-CuNi]
2#0010
16#0A02
Type R [PtRh-Pt]
2#0011
16#0A03
Type S [PtRh-Pt]
2#0100
16#0A04
Type J [Fe-CuNi IEC]
2#0101
16#0A05
Type L [Fe-CuNi DIN]
2#0110
16#0A06
Type T [Cu-CuNi IEC]
2#0111
16#0A07
Type K [NiCr-Ni]
2#1000
16#0A08
Type U [Cu-CuNi DIN]
2#1001
16#0A09
Type C
2#1010
16#0A0A
Type TXK/XK(L)
2#1011
16#0A0B
Type B [PtRh-PtRh]
2#0000
16#0B00
2#0001
16#0B01
Type E [NiCr-CuNi]
2#0010
16#0B02
Type R [PtRh-Pt]
2#0011
16#0B03
Type S [PtRh-Pt]
2#0100
16#0B04
2#0101
16#0B05
2#0110
16#0B06
2#0111
16#0B07
Type K [NiCr-Ni]
2#1000
16#0B08
2#1001
16#0B09

Appendix
Measuring type
Themocouple, fix. ref. temp
Thermocouple, linear, internal

compensation / internal
reference point
Thermocouple, linear, external

compensation / reference point
RTD(0)

Coding
(A)
2#1100
2#1101
2#1110
Measuring range
Code (B) MODE

(256A+B)
Type C
2#1010
16#0B0A
Type TXK/XK(L)
2#1011
16#0B0B
Type B [PtRh-PtRh]
2#0000
16#0C00
2#0001
16#0C01
Type E [NiCr-CuNi]
2#0010
16#0C02
Type R [PtRh-Pt]
2#0011
16#0C03
Type S [PtRh-Pt]
2#0100
16#0C04
2#0101
16#0C05
2#0110
16#0C06
2#0111
16#0C07
Type K [NiCr-Ni]
2#1000
16#0C08
2#1001
16#0C09
Type C
2#1010
16#0C0A
Type TXK/XK(L)
2#1011
16#0C0B
Type B [PtRh-PtRh]
2#0000
16#0D00
2#0001
16#0D01
Type E [NiCr-CuNi]
2#0010
16#0D02
Type R [PtRh-Pt]
2#0011
16#0D03
Type S [PtRh-Pt]
2#0100
16#0D04
2#0101
16#0D05
2#0110
16#0D06
2#0111
16#0D07
Type K [NiCr-Ni]
2#1000
16#0D08
2#1001
16#0D09
Type C
2#1010
16#0D0A
Type TXK/XK(L)
2#1011
16#0D0B
Type B [PtRh-PtRh]
2#0000
16#0E00
2#0001
16#0E01
Type E [NiCr-CuNi]
2#0010
16#0E02
Type R [PtRh-Pt]
2#0011
16#0E03
Type S [PtRh-Pt]
2#0100
16#0E04
2#0101
16#0E05
2#0110
16#0E06
2#0111
16#0E07
Type K [NiCr-Ni]
2#1000
16#0E08
2#1001
16#0E09
Type C
2#1010
16#0E0A
Type TXK/XK(L)
2#1011
16#0E0B
347
Appendix
Measuring type
Coding
(A)
Measuring range
Code (B) MODE

(256A+B)
Themocouple, dyn. ref. temp
2#0111
Type B [PtRh-PtRh] (variant 1)

OMODE settings for SM
modules (Page 351)
2#0000
16#0700
Type N [NiCrSi-NiSi] (variant 1)

modules (Page 351)
2#0001
16#0701
Type E [NiCr-CuNi] (variant 1)

modules (Page 351)
2#0010
16#0702
Type R [PtRh-Pt] (variant 1)

modules (Page 351)
2#0011
16#0703
Type S [PtRh-Pt] (variant 1)

modules (Page 351)
2#0100
16#0704
Type J [Fe-CuNi IEC] (variant 1) 2#0101

modules (Page 351)
16#0705
Type L [Fe-CuNi DIN] (variant

1) OMODE settings for SM
modules (Page 351)
2#0110
16#0706
Type T [Cu-CuNi IEC] (variant

1) OMODE settings for SM
modules (Page 351)
2#0111
16#0707
Type K [NiCr-Ni] (variant 1)

modules (Page 351)
2#1000
16#0708
Effect of the temperature coefficients on the measuring range

Setting TC = 3850 at GOST Standard Pt10, Pt50, Pt100, Pt500 sets Bit 7 in the measuring
range byte (0x40)
Setting TC = 428 at GOST Standard Cu10, Cu50, Cu100 sets Bit 8 in the measuring range
byte (0x80)
Measuring range coding of the analog output modules

Depending on the measuring-range coding of the analog output modules, the parameter
MODE_xx (measuring-range coding) corresponding to the channel must be specified in
accordance with the table.
Measuring type
Measuring range
MODE
Voltage
5V
16#0106
1 to 5 V
16#0107
0 to 10 V
16#0108
10 V
16#0109
0 to 20 mA
16#0202
Current
348

Appendix
Measuring type
HART interface
Measuring range
MODE
4 to 20 mA
16#0203
20 mA
16#0204
4 to 20 mA
16#070C
Mode: Celsius and Fahrenheit

Variant
Measuring range
0, 1
(depending on
the other
variant IDs)
0,1,2,4
Celsius
8, 9
(depending on
the other
variant IDs)
0,1,2,4
Fahrenheit
Mode: 16#090C and variant

Variant
Measuring range
0,1,2,4
0,1,2,4
KTY84/110
Mode: 16#090D and variant

Variant
Measuring range
0,1,2,4
0,1,2,4
KTY84/130
Mode: 16#07 (Coding A) and variant

Variant
Measuring range
0,1,2,4
HART interface
0,1,2,4
Thermocouple, dynamic reference temperature
MODE: 16#08, 16#0A, 16#0B, 16#0D, 16#0E (coding A) and variant

Table 7-1
PCS 7 as of V8.1: MODE parameter variant
Variant
Measuring range
0,1,2,4
S7-300 module
0,1,2,4
S7-300, ET 200M Ex I/O module

349
Appendix
Table 7-2
PCS 7 V7.x: MODE parameter variant
Variant
Mode
Measuring range
16#08, 16#0A,
S7-300 module
16#0B, 16#0D,
16#0E
1
16#18, 16#1A,
S7-300, ET 200M Ex I/O module
16#1B, 16#1D,
16#1E
Measuring-Range Coding of the Digital Input and Output Modules

With digital input modules and digital output modules, there is no measuring type and no
measuring range:
MODE = 16#FFFF (with DI)
MODE = 16#FFFE (with DO)
MODE: 1oo1 / 1oo2 evaluation for F-modules

Variant
Measuring range
0,1,2,4
1oo1 (1v1) evaluation
0,1,2,4
1oo2 (2v2) evaluation
Measuring range coding of the controller module

There is no measuring type and no measuring range for controller modules:
MODE = 16#FFFD
Measuring range coding of the communication module

There is no measuring type and no measuring range for communication modules:
MODE = 16#0001
350

Appendix
7.4 MODE settings for field devices
7.3
OMODE settings for SM modules
OMODE structure
The table below shows the structure and meaning of the outputs OMODE_xx of data type
DWORD:
Byte 3:
16#80: Value status "valid value"
Byte 2:
16#00: Value status "invalid value"
(Channel error)
(Higher-level error)
16#01: Restart (OB 100) has been carried out

16#02: Measuring-range overshoot
(Channel-error diagnostics)
16#04: Measuring range low limit exceeded
(Channel-error diagnostics)
16#xy: Variant identifier at multiple MODE_ assignment

(see below)
Byte 1, 0 (low word):
MODE (see above)
Example:
16#80010203 = value status "valid value", restart has been carried out, current 4 mA to 20mA
7.4
MODE settings for field devices

MODE_xx input parameters are available for a maximum of 32 slots of a PA/FF field device.
Their initial value is zero (no read/write access). You must set the combination selected from
the options of the PROFIBUS PA 3.0 profile at the MODE_xx input of each slot channel xx:
Block
I/O (parameters)
(cyclic data)
Input (I)/Output
(O)
(PLS view)
MODE
16#xxyy,
O=xx I=yy
Configuration
possible with
field device
permissible
combination
and sequence
Analog input (PA_AI/
FbAnIn)
OUT
16#0001
PA + FF
Totalizer (PA_TOT/
FbAnTot)
TOTAL
16#000F
PA
Totalizer (PA_TOT/
FbAnTot)
TOTAL
SET_TOT
I
O
16#070F
PA
Totalizer (PA_TOT/
FbAnTot)
TOTAL
SET_TOT
MODE_TOT
I
O
O
16#080F
PA
Analog output
(PA_AO/FbAnOu)
SP
16#0100
PA + FF
Analog output
(PA_AO/FbAnOu)
SP
READBACK
POS_D
O
I
I
16#0103
PA

351
Appendix
7.4 MODE settings for field devices
Block
I/O (parameters)
(cyclic data)
Input (I)/Output
(O)
MODE
16#xxyy,
O=xx I=yy
Configuration
possible with
field device
permissible
combination
and sequence
(PLS view)
Analog output
(PA_AO/FbAnOu)
SP
CHECK_BACK
O
I
16#0104
PA
Analog output
(PA_AO/FbAnOu)
SP
READBACK
POS_D
CHECK_BACK
O
I
I
I
16#0105
PA
Analog output
(PA_AO/FbAnOu)
RCAS_IN,
RCAS_OUT
O
I
16#0206
PA
Analog output
(PA_AO/FbAnOu)
RCAS_IN,
RCAS_OUT,
CHECK_BACK
O
I
I
16#0207
PA
Analog output
(PA_AO/FbAnOu)
SP
RCAS_IN
READBACK
RCAS_OUT
POS_D
CHECK_BACK
O
O
I
I
I
I
16#0308
PA
Discrete input
(PA_DI/FbDiIn)
OUT_D
16#0002
PA + FF
Discrete output
(PA_DO/FbDiOu)
SP_D
16#0400
PA + FF
Discrete output
(PA_DO/FbDiOu)
SP_D
READBACK_D
O
I
16#0409
PA
Discrete output
(PA_DO/FbDiOu)
SP_D
CHECKBACK_D
O
I
16#040A
PA
Discrete output
(PA_DO/FbDiOu)
SP_D
READBACK_D
CHECK_BACK_D
O
I
I
16#040B
PA
Discrete output
(PA_DO/FbDiOu)
RCAS_IN_D
RCAS_OUT_D
O
I
16#050C
PA
Discrete output
(PA_DO/FbDiOu)
RCAS_IN_D
RCAS_OUT_D
CHECK_BACK_D
O
I
I
16#050D
PA
Discrete output
(PA_DO/FbDiOu)
SP_D
RCAS_IN_D
READBACK_D
RCAS_OUT_D
CHECK_BACK_D
O
O
I
I
I
16#060E
PA
PA/FF device variant identifier
352
Variant
Field device
PA device
FF device

Appendix
7.7 Addressing
7.5
OMODE settings for field devices
OMODE Structure
The table below shows the structure and meaning of the outputs OMODE_xx of data type
DWORD:
Byte 3:
16#80: Value status "valid value"

(Channel error)
(Higher-level error)
Byte 2:
16#xy: Variant identifier at multiple

MODE_ assignment (see MODE
settings for field devices (Page 351))
Byte 1, 0 (low word):
MODE (see above)
Example:
16#80000001 corresponds to the value status "valid value", analog input, whereby parameter
Out supplies the cyclic data.
7.6
Error Information of Output Parameter MSG_STAT

The messages can be disabled by setting input EN_MSG = FALSE (output MSG_STAT(_x)
remains unchanged).
Block ALARM8_P(_x) is called in the acyclic OBs and in OB1 if message suppression is not
enabled. Error information of ALARM_8P(_x) - messages cannot be output - is indicated at
output parameter MSG_STAT(_x).
Details on the error information of output parameter MSG_STAT and on the acknowledgment
word MSG_ACK(_x) of ALARM_8P are found in the Online Help of SF B35 (ALARM_8P).
7.7
Addressing
Rules
If you do not use the CFC function Generate module drivers, you must set the logical basic
address of the module created with HW Config at the LADDR input parameter. If input
SUBN_TYP = FALSE, the RACK of the module is connected to an integrated DP interface
(distributed I/O device interface) of the CPU module by means of a line. Otherwise, you must
set SUBN_TYP = TRUE.
The following points are generally to be observed for all SM, PA and FF blocks:

353
Appendix
7.7 Addressing
The basic address of modules equipped only with inputs, i.e., modules which only write
data to the input range of the CPU process image, can be fetched directly from HW Config;
for example: The module SM 331 AI 8x12Bit 6ES7 331-7KF01-0AB0:
Address input range
(HW Config)

(HW Config)
LADDR
(decimal/hex)
512
512 / 16#0200
The MSB (most significant bit) must be set in the basic address fetched from HW Config
for modules equipped only with outputs, which means modules which only read data from
the output range of the CPU process image;
for example, module SM 332 AO 4x12Bit 6ES7 332-5HD01-0AB0:
Address input range
(HW Config)

(HW Config)
LADDR
(decimal/hex)
512
-32256 / 16#8200
The basic address of the input range must be set at input LADDR and the basic address
of the output range from HW Config must be set at input LADDR1 for mixed modules, which
means modules that write data to the input range and read data from the output range of
the CPU process image;
for example, module SM 323 DI/O 8x24V/05A 6ES7 323-1BH81-0AA0:
Address input range
(HW Config)

(HW Config)
LADDR
(decimal/hex)
LADDR1
(decimal/hex)
12
12
12 / 16# 000C
12 / 16# 000C
For FF devices which only write data to the input range of the CPU process image, the
lowest input address should be fetched from HW Config.
For FF devices which only write data to the output range of the CPU process image, the
lowest output address from HW Config should be set.
For FF devices which write the data in the input range of the CPU process image and read
from the output range of the CPU process image, you must set the lowest address of the
input/output range from HW Config at the DADDR input.
354
Address input range

(HW Config)

(HW Config)
DADDR
(decimal/hex)
512
512
512
16896 (16384 + 512)/ 16#4200
512
516
512
512
512
512
516
512
16896 (16384 + 512) / 16#4200

Appendix
7.8 Message Classes
7.8
Message Classes
Message classes
Message classes are used to group messages according to their cause. The following
message classes are used in the SIMATIC process control system:
Process messages triggered when process-specific monitoring values (for example,
alarms, warnings, high/low tolerances, general process messages) are reached or
exceeded.
Process control messages which are output by the control system (system messages) or
the I/O units (errors in the field), or for preventive maintenance.
Requests for operator input which, in the case of certain operation sequences, draw the
operator's attention to the necessity of an operator intervention (for example, request to
acknowledge a stepping operation manually in order to enable transition) or operation logs.
Table of message classes and their meaning
Message class
Meaning
With acknowledgment
AH
Alarm high (High High Alarm)
Yes
AL
Alarm low (Low Low Alarm)
Yes
WH
Warning high (High Alarm)
Yes
WL
Warning low (Low Alarm)
Yes
TH
Tolerance high (Tolerance High)
Yes
TL
Tolerance low (Tolerance Low)
Yes
AS process control message (error)
Yes
AS process control message (fault)
Yes
S*
OS process control message (fault)
Yes
Preventive maintenance (Maintenance)
Yes
PM
Process message (Process Message)
Yes
PM
Operating message
No
OR
Operator request (Operator Request)
No
OM *1)
Operator message (Operation Message)
No
SA
Status AS
No
SO
Status OS
No
*1) If the block is used for operation messages, the inputs I_1, ... have to be supplied with
pulses. Assignment of the static value "1" would lead to multiple messages.
See also

355
Appendix
7.10 Status displays
7.9
Dependencies
Dependency on the FM_CO block

The FM_CO block (PCS 7 Basic Library) coordinates the reading of data records for the
FM_CNT, FMCS_PID, FMT_PID, and READ355P blocks. Therefore, when installing these
blocks you must ensure that the driver generator installs FM_CO in the fastest cyclic-interrupt
OB of one of the blocks named above. This OB must not run slower than 30 s or faster than
25 ms.
Notes on reading data records

In an ET 200M with n controller blocks, reading of data records is activated every n+1 cycles
(ideally, when the installation sequence tallies with the interconnection).
This means that, in the worst case, a setpoint changed by means of a faceplate will only be
viewed by the operator after n+1 cycles (e.g. this would amount to 17 s for OB 32 (1,000 ms)
with 4 controller modules and 16 blocks).
The same applies for position feedback for the step controller. At the time of changeover
(manual/auto), the manipulated variable LMN is set to an out-of-date value.
Changing the visualization time

You can reduce the visualization time as follows:
Install the controller blocks in a faster OB
or
Distribute the controller modules over several ET 200 stations.
7.10
Status displays
7.10.1
Maintenance Status of MS
Layout of the maintenance status

The layout of the maintenance status MS (DWORD data type) is as follows:
356
Bit 0 to 7
Display of the MS
Bit 8 to 15
Display of the MS of the redundant partner
Bit 16
1 = Redundant partner available
Bit 17
0 = primary partner is master,

1 = redundant partner is master
Bit 18
PDM-MS worse than device status

Appendix
Bit 19 to 21
Reserve
Bit 22
PDM has detected status change
Bit 23
Block takes part in the cyclical updating of PDM
Bit 24 to 27
OS operation
Bit 28 to 31
PDM-MS
The MS is copied 1:1 to the output O_MS.

For more information, refer to the "Process Control System PCS 7; Maintenance Station"
manual.
7.10.2
PA field device status and diagnostics information
PA-Field-Device Status
PA Status
Meaning of PA Status
Message
Coding MS
Limits (Bit 1 + 0 irrelevant)

Quality
(bit 7 + 6)
Substatus
(bits 5 2)
10
0000
M = Message
Q = Must be
acknowledged
Good
10
0001
10
0010
Good, active warning
10
0011
Good, active interrupt
10
0100
Good, unacknowledged configuration change
10
0101
Good, unacknowledged warning
10
0110
Good, unacknowledged interrupt
10
1000
Good, device switches to fail-safe position
10
1001
Good, maintenance required is indicated

(more diagnostic data available)
10
1010
Good, maintenance demanded is indicated

10
1111
Good, self-test completed
01
0000
Uncertain, not specified
0
Q
01
0001
Uncertain, last valid value
01
0010
Uncertain, substitute value
01
0011
Uncertain, initial value
01
0100
Uncertain, measured value generation incorrect
0
6
01
0101
Uncertain, value outside defined range
01
0110
Uncertain, signal source uncertain
01
0111
Uncertain, configuration error
01
1000
Uncertain, measured value simulated
01
1001
Uncertain, sensor calibration

357
Appendix
PA Status
Meaning of PA Status
Message
Coding MS
Limits (Bit 1 + 0 irrelevant)

01
1010

01
1100
Uncertain, simulation started
01
1101
Uncertain, simulation ended
01
1110
00
0000
Bad, not specified
00
0001
Bad, configuration error
00
0010
Bad, not connected
00
0011
Bad, device error
00
0100
Bad, sensor error
00
0101
Bad, no connection - last valid value
00
0110
Bad, no connection - no valid value
00
0111
00
1000

(no diagnostic data, passivated)
00
1001

00
1010
Bad, process-related, no maintenance
00
1111
Bad, local operation/functional check
You will find additional information about status icons for the maintenance status (MS) in the
"Maintenance status MS (Page 356)" section.
358

Appendix
The structure of the PA_DIAG parameter is as follows:
Byte
Bit position
PROFIBUS - diagnostic significance
Message
MS
Electronic hardware failure
Mechanical hardware failure
Excess motor temperature
Excess temperature at electronic circuit
Memory error
Measurement failure
Device not initialized (no auto-calibration)
Auto-calibration error
Zero error (limit position)
No power supply (electr. pneum.)
Invalid configuration
Warm start executed
Complete restart executed
Maintenance necessary
Invalid identifier
Invalid ID number
Device error
Maintenance requested
Device is in a functional check or in simulation or under

local operator control (maintenance)
4-7
The process conditions do not allow the valid values to

be returned; this is set when the quality is uncertain,
process-related, no maintenance or bad, processrelated, no maintenance
0
0
Reserved for PNO, default 0

3
0-4
Reserved for PNO use
= 0: for devices of the corresponding profile
= 0: for devices of the corresponding profile
= 0: no further information available

= 1: Further diagnostic information available in
DIAGNOSIS_EXTENSION

359
Appendix
7.11 Text libraries
7.11
Text libraries
7.11.1
Text Library for MOD_PAL0, MOD_PAX0

The following table lists the text-library message texts and their numbers for the blocks
MOD_PAL0 (FB99) and MOD_PAX0 (FB112):
7.11.2
Text no.
Message text
Warm restart
Cold restart
PA field device diagnostics
Memory error
Text Library for PADP_L00, PADP_L01, PADP_L02

The following table lists the text-library message texts and their numbers for the blocks
PADP_L00 (FB 109), PADP_L01 (FB 110), PADP_L02 (FB 111):
7.11.3
Text No.
Message Text
Module error
Wrong module
Module missing
Text Library for DREP, DREP_L

The following table lists the text-library message texts and their numbers for the blocks DREP
(FB 113) and DREP_L (FB 125):
360
Text No.
Message Text
Failure
Diagnostics

Appendix
7.11 Text libraries
7.11.4
Text library for MOD_1, MOD_2, MOD_3, MOD_64, MOD_D2, MOD_CP

The following table lists the message texts and their text numbers from the text library for the
MOD_1 (FB 91) / MOD_2 (FB 92) / MOD_3 (FB 95) / MOD_64 (FB 137) / MOD_D2 (FB 94) /
MOD_CP (FB 98) blocks :
Text
No.
Message Text
Common mode error
Short-circuit to P
Short circuit to M
Wire break
Reference channel error
Measuring range violation low
Measuring range violation high
Load voltage missing
10
Chassis ground error
11
Sensor supply missing
12
Excess temperature
13
Module OK
14
Internal error
15
External error
16
17
18
No configuration
19
Wrong module parameters
20
Wrong/missing user module
21
Communication error
22
Operating mode RUN/STOP
23
Timeout
24
Failed module int. supply voltage
25
Battery depleted
26
Total backup failure
27
CPU failure
28
EPROM error
29
RAM error
30
ADC/DAC error
31
Fuse tripped
32
Process interrupt lost
33
Removed
34
Plugged
35
Wrong module type plugged
36
Faulty module inserted
37
Module inserted (parameter error)

Remark
RUN: going STOP: coming
361
Appendix
7.11 Text libraries
7.11.5
Text
No.
Message Text
38
Chatter error
39
Changeover contact diagnostics
40
CIR parameter assignment
41
CIR parameter assignment not successful
Remark
Text Library for MOD_D1

The following table lists the text-library message texts and their numbers for the block MOD_D1
(FB 93):
362
Text
no.
Message text
Common mode error
Short-circuit to P
Short circuit to M
Wire break
10
11
12
Excess temperature
13
Module OK
14
Internal error
15
External error
16
17
18
No configuration
19
20
21
Communication error
22
23
Timeout
24
25
Battery depleted
26
27
CPU failure
28
EPROM error
29
RAM error
Remark

Appendix
7.11 Text libraries
Text
no.
Message text
30
ADC/DAC error
31
Fuse tripped
32
33
Removed
34
Plugged
35
36
37
Module inserted (parameter assignment error)
38
Chatter error
39
40
Sensor or load voltage loss
41
Faulty fuse
42
AI error hardware
43
AI wire break
44
AI below measuring range
45
AI above measuring range
46
AO wire break
47
AO short-circuit
48
49
50
Signal A faulty
51
Signal B faulty
52
Signal N faulty
53
Faulty value supplied to the channels
54
Sensor supply 5.2 V/8.2 V faulty
55
Sensor supply 24 V faulty
56
Namur sensor signal line error
57
Readback error
58
59
60
Actuator OFF
61
Discrepancy error

Remark
363
Appendix
7.11 Text libraries
7.11.6
Text library for MOD_D3

The following table lists the text library message texts and their numbers for the block MOD_D3
(FB134):
364
Text
no.
Message text
Common mode error
Short-circuit to P
Short circuit to M
Wire break
10
11
12
Excess temperature
13
Module OK
14
Internal error
15
External error
16
17
18
No configuration
19
20
21
Communication error
22
23
Timeout
24
25
Battery depleted
26
27
CPU failure
28
EPROM error
29
RAM error
30
ADC/DAC error
31
Fuse tripped
32
33
Removed
34
Plugged
35
36
37
Module inserted (parameter assignment error)
Remark

Appendix
7.11 Text libraries
Text
no.
Message text
38
Chatter error
39
40
41
Faulty fuse
42
AI error hardware
43
AI wire break
44
45
46
AO wire break
47
AO short-circuit
48
49
50
Signal A faulty
51
Signal B faulty
52
Signal N faulty
53
Faulty value supplied to the channels
54
55
56
57
Readback error
58
59
60
Actuator OFF
61
Undervoltage
62
Overvoltage
63
Overload
64
Reserve
65
Hardware interrupt
66
Actuator warning
67
Safety shutdown
68
Ambiguous error
69
70
71
Channel temporarily not available
72
Channel is being calibrated
73
Discrepancy error
74
Overcurrent at output driver
75
P-output driver defective
76
Internal P short circuit
77
External P short circuit/cross fault
78
Internal error in the read circuit/test circuit
79
Short circuit of the output to M or output driver defective

Remark
365
Appendix
7.11 Text libraries
7.11.7
Text
no.
Message text
80
Switching frequency exceeded
81
PROFIsafe communications error
Remark
Text library for MOD_D8_PN (FB197) / MOD_D16_PN (FB198) / MOD_D24_PN

(FB199)
The following table lists the message texts and their numbers from the text library for the block
MOD_D8_PN (FB197) / MOD_D16_PN (FB198) / MOD_D24_PN (FB199):
366
Text
no.
Message text
Common mode error
Short circuit to P
Short circuit to M
Wire break
Measuring range/low limit violated
Measuring range/high limit violated
10
Ground error
11
12
Excess temperature
13
Module OK
14
Internal error
15
External error
16
17
18
Missing parameters
19
Wrong parameters in module
20
21
Communication error
22
23
Time monitoring addressed
24
25
Battery depleted
26
Total backup battery failure
27
Processor failure
28
EPROM error
29
RAM error
30
ADC/DAC error
Remark
RUN: going, STOP: coming

Appendix
7.11 Text libraries
7.11.8
Text
no.
Message text
31
Fuse blown
32
Hardware interrupt lost
33
Withdrawn
34
Plugged
35
36
Faulty module plugged
37
Module plugged (parameter assignment error)
38
Chatter error
39
40
Front connector missing or sensor/load voltage missing
41
Fuse defective
42
AI hardware error
43
AI wire break
44
45
46
AO wire break
47
AO short-circuit
48
49
50
Signal A faulty
51
Signal B faulty
52
Signal N faulty
53
Incorrect value transferred between channels
54
55
56
57
Readback error
58
59
60
Actuator switch off
61
Undervoltage
Remark
Text library for MOD_CP_PN (FB201)

The following table lists the message texts and their numbers from the text library for the block
MOD_CP_PN (FB201):
Text
no.
Message text
Common mode error

Remark
367
Appendix
7.11 Text libraries
368
Text
no.
Message text
Short circuit to P
Short circuit to M
Wire break
Below measuring range
Above measuring range
10
Ground error
11
12
Excess temperature
13
Module OK
14
Internal error
15
External error
16
17
18
No parameter assignment
19
20
21
Communication problem
22
23
Time monitoring addressed
24
25
Battery depleted
26
Total backup battery failure
27
Processor failure
28
EPROM error
29
RAM error
30
ADC/DAC error
31
Fuse blown
32
Hardware interrupt lost
33
Withdrawn
34
Plugged
35
36
Faulty module plugged
37
Module plugged (parameter assignment error)
38
Chatter error
39
40
41
42
Error
Common mode error
Remark

Appendix
7.11 Text libraries
7.11.9
Text
no.
Message text
Short circuit to P
Short circuit to M
Wire break
Below measuring range
Above measuring range
10
Ground error
11
12
Excess temperature
13
Module OK
14
Internal error
15
External error
16
17
18
No parameter assignment
19
20
Remark
Text Library for MOD_MS

The following table lists the text-library message texts and their numbers for the block
MOD_MS (FB 96):
Text
No.
Message Text
Common mode error
Short-circuit to P
Short circuit to M
Wire break
10
11
12
Excess temperature
13
Module OK
14
Internal error
15
External error

Remark
369
Appendix
7.11 Text libraries
370
Text
No.
Message Text
16
17
18
No configuration
19
Wrong module parameters
20
21
Communication error
22
23
Timeout
24
25
Battery depleted
26
27
CPU failure
28
EPROM error
29
RAM error
30
ADC/DAC error
31
Fuse tripped
32
33
Removed
34
Plugged
35
36
37
Module inserted (parameter error)
38
Chatter error
39
40
41
Faulty fuse
42
Undervoltage
43
Overvoltage
44
Actuator warning
45
Actuator OFF
46
47
Unknown error
48
Short-circuit
49
Error
50
51
Remark

Appendix
7.11 Text libraries
7.11.10
Text Library for OB_BEGIN

The following table lists the text-library message texts and their numbers for the block
OB_BEGIN (FB 100):
7.11.11
Text No. Message Text
Remark
Nested stack error
Error code B#16#71:
Master control relay stack error
Error code B#16#72:
Max. nesting depth for synchronous errors exceeded
Error code B#16#73
U-stack nesting depth exceeded
Error code B#16#74
B-stack nesting depth exceeded
Error code B#16#75
Local data allocation error
Error code B#16#76
Unknown opcode
Error code B#16#78
Code length error
Error code B#16#7A
Text library for OB_BEGIN_PN (FB130) / OB_BEGIN_HPN (FB205)

The following table lists the message texts and their text numbers from the text library for the
block OB_BEGIN_PN (FB130) / OB_BEGIN_HPN (FB205):
Text No. Message Text
Remark
Nested stack error
Error code B#16#71:
Master control relay stack error
Error code B#16#72:
Max. nesting depth for synchronous errors exceeded
Error code B#16#73
U-stack nesting depth exceeded
Error code B#16#74
B-stack nesting depth exceeded
Error code B#16#75
Local data allocation error
Error code B#16#76
Unknown opcode
Error code B#16#78
Code length error
Error code B#16#7A

371
Index
Description of
OB_BEGIN, 223
OB_BEGIN_HPN, 238
OB_BEGIN_PN, 233
I/Os of
IMDRV_TS, 87
OB_BEGIN
Description, 223
OB_BEGIN_HPN
Description, 238
OB_BEGIN_PN
Description, 233
Text library for
MOD_D3, 364
MOD_PAX0, 360
A
Addressing, 353
B
Block icons
OB_BEGIN_BASE, 15
OB_BEGIN_HPN_BASE , 15
OB_BEGIN_PN_BASE , 15
C
ChkREAL, 339
Description, 339
CONEC, 23, 25
Description, 23
I/Os, 25
Coordination of FMCS_PID/FMT_PID, 19
CPU_RT, 27, 33
Description, 27
I/Os, 33
D
Description
OR_32_TS, 260

Description of, 23, 27, 45, 49, 52, 59, 78, 90, 96, 103,
109, 115, 122, 125, 133, 149, 186, 199, 207, 211, 217,
245, 254, 258, 271, 282, 289, 294, 298, 303, 311, 313,
314, 318, 323, 329, 334
ChkREAL, 339
CONEC, 23
CPU_RT, 27
DIAG_AB, 35
DPAY_V0, 38
DPAY_V1, 45
DPDIAGV0, 49
DREP, 52
DREP_L, 59
FM_CNT, 78
FM_CO, 19
IMDRV_TS, 83
MOD_1, 90
MOD_2, 96
MOD_3, 103
MOD_4, 109
MOD_64, 115
MOD_CENTRAL, 122
MOD_CP, 125
MOD_D1, 133, 165
MOD_D2, 149
MOD_HA, 186
MOD_MS, 199
MOD_PAL0, 211
MOD_PAX0, 217
OB_DIAG1, 245, 254
OB_END, 258
OR_HA16C, 263
OR_M_16C, 271
OR_M_32C, 276
OR_M_8C, 282
PADP_L00, 289
PADP_L01, 294
PADP_L02, 298
PADP_L10, 303
PO_UPDAT, 313
PS, 314
QC_CHNG, 339
RACK, 318, 323
RED_F, 326
SUBNET, 329
SUBNET_PN, 334
Description of MOD_DRV, 181
Description of: MOD_SWT, 207
Description of: PDM_MS, 311
373
Index
DIAG_AB
Description, 35
I/Os, 37
DPAY V1, 47
I/Os, 47
DPAY V1_PN, 48
I/Os, 48
DPAY_V0, 42
Description, 38
I/Os, 42
DPAY_V1, 45
Description, 45
DPDIAGV0, 49, 51
Description, 49
I/Os, 51
DREP, 52, 56
Description, 52
I/Os, 56
DREP_L, 59, 63
Description, 59
I/Os, 63
E
Error Information of Output Parameter MSG_STAT,
353
F
FM_CNT, 78, 81
Description, 78
I/Os, 81
FM_CO
Description, 19
I/Os, 21
G
General information about the block description, 11
I
I/Os of, 25, 33, 42, 47, 48, 51, 56, 63, 81, 93, 100, 106,
112, 118, 122, 128, 131, 139, 154, 183, 191, 195, 203,
208, 213, 219, 227, 233, 239, 248, 251, 259, 292, 308,
310, 316, 321, 323, 332, 334
CPU_RT, 33
DIAG_AB, 37
DPAY V1, 47
DPAY V1_PN, 48
374
DPAY_V0, 42
DPDIAGV0, 51
DREP, 56
DREP_L, 63
FM_CNT, 81
FM_CO, 21
MOD_1, 93, 100
MOD_2, 93, 100
MOD_3, 106
MOD_4, 112
MOD_64, 118
MOD_CENTRAL , 122
MOD_CP, 128
MOD_CP_PN, 131
MOD_D1, 139, 154
MOD_D2, 139, 154
MOD_D3, 172
MOD_HA, 191
MOD_HA_PN, 195
MOD_MS, 203
MOD_PAL0, 213
MOD_PAX0, 219
OB_BEGIN, 227
OB_BEGIN_HPN, 239
OB_BEGIN_PN, 233
OB_DIAG1, 248
OB_DIAG1_PN, 251
OB_END, 259
OR_32_TS, 261
OR_HA16C, 266, 271, 276, 285
OR_M_16C, 266, 271, 276, 285
OR_M_32C, 266, 271, 276, 285
OR_M_8C, 266, 271, 276, 285
PADP_L00/L01/L02, 292
PADP_L10, 308
PADP_L10_PN, 310
PS, 316
RACK, 321
RACK_PN, 323
RED_F, 328
SUBNET, 332
SUBNET_PN, 334
I/Os of: MOD_DRV, 183
I/Os of: MOD_SWT, 208
IMDRV_TS
Description, 83
I/Os, 87
Message texts, 89
M
Maintenance status MS, 356

Index
Message classes, 355

Message texts of
IMDRV_TS, 89
MOD_ CP_PN
Text library, 367
MOD_1, 90, 93, 100, 361
Description, 90
I/Os, 93, 100
Text library, 361
MOD_2, 93, 96, 100, 361
Description, 96
I/Os, 93, 100
Text library, 361
MOD_3, 103, 106, 361
Description, 103
I/Os, 106
Text library, 361
MOD_4, 109, 112
Description, 109
I/Os, 112
MOD_64, 115, 118, 361
Description, 115
I/Os, 118
Text library, 361
MOD_CENTRAL, 122
Description, 122
I/Os, 122
MOD_CP, 125, 128, 361
Description, 125
I/Os, 128
Text library, 361
MOD_CP_PN, 131, 367
I/Os, 131
MOD_D1, 133, 139, 154, 362
Description, 133
I/Os, 139, 154
Text library, 362
MOD_D16_PN, 366
Text library, 366
MOD_D2, 139, 149, 154, 361
Description, 149
I/Os, 139, 154
Text library, 361
MOD_D24_PN, 366
Text library, 366
MOD_D3
Description, 165
I/Os, 172
Text library, 364
MOD_D8_PN, 366
Text library, 366
MOD_DRV, 181, 183

MOD_DRV: I/Os, 183

MOD_HA, 186, 191
Description, 186
I/Os, 191
MOD_HA_PN, 195
I/Os, 195
MOD_MS, 199, 203, 369
Description, 199
I/Os, 203
Text library, 369
MOD_PAL0, 211, 213, 360
Description, 211
I/Os, 213
Text library, 360
MOD_PAX0, 217, 219, 360
Description, 217
I/Os, 219
Text library, 360
MOD_SWT, 207, 208
MOD_SWT: Description, 207
MOD_SWT: I/Os, 208
MODE, 341
MODE settings for PA/FF field devices, 351
MODE Settings for SM Modules, 341
MSG_STAT, 353
O
OB_BEGIN, 227, 371
I/Os, 227
Text library, 371
OB_BEGIN_HPN, 239
I/Os, 239
OB_BEGIN_PN, 233, 371
I/Os, 233
Text library, 371
OB_DIAG1, 245, 248, 251, 254
Description, 245, 254
I/Os, 248
OB_DIAG1_PN
I/Os, 251
OB_END, 258, 259
Description, 258
I/Os, 259
OMODE settings for SM modules, 351
OR_32_TS
Description , 260
I/Os, 261
OR_HA16C
Description, 263
I/Os, 266, 271, 276, 285
OR_M_16C, 271
375
Index
Description, 271
I/Os, 266, 271, 276, 285
OR_M_32C
Description, 276
I/Os, 266, 271, 276, 285
OR_M_8C, 282
Description, 282
I/Os, 266, 271, 276, 285
P
PA field device status and diagnostics information,
357
PA/FF device
Variant identifier, 352
PA/FF field devices
Settings, 351
PADP_L00, 289, 360
Description, 289
Text library, 360
PADP_L00/L01/L02, 292
I/Os, 292
PADP_L01, 294, 360
Description, 294
Text library, 360
PADP_L02, 298, 360
Description, 298
Text library, 360
PADP_L10, 303, 308, 310
Description, 303
I/Os, 308
PADP_L10_PN
I/Os, 310
PDM_MS, 311
PDM_MS: Description, 311
PO_UPDAT, 313
Description, 313
PS, 314, 316
Description, 314
I/Os, 316
RACK_PN, 323
I/Os, 323
RED_F
Description, 326
I/Os, 328
S
SUBNET, 329, 332
Description, 329
I/Os, 332
SUBNET_PN, 334
Description, 334
I/Os, 334
T
Text library for, 360, 361, 362, 367, 369, 371
DREP, 360
DREP_L, 360
MOD_ CP_PN , 367
MOD_1, 361
MOD_2, 361
MOD_3, 361
MOD_64, 361
MOD_CP, 361
MOD_D1, 362
MOD_D16_PN, 366
MOD_D2, 361
MOD_D24_PN, 366
MOD_D8_PN, 366
MOD_MS, 369
MOD_PAL0, 360
OB_BEGIN, 371
OB_BEGIN_PN, 371
PADP_L00, 360
PADP_L01, 360
PADP_L02, 360
V
Q
QC_CHNG, 339
Description, 339
Variant identifier
PA/FF device, 352
R
RACK, 318, 321, 323
Description, 318, 323
I/Os, 321
376


PCS7 Basic Lib

Uploaded by

Copyright:

Available Formats

PCS7 Basic Lib

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PCS7 Basic Lib

Uploaded by

Copyright:

Available Formats

What are the different types of warnings mentioned in the document?

What are the different types of warnings mentioned in the document?

What are some of the blocks described in the document?

What are some of the blocks described in the document?

SIMATIC

Process Control System PCS 7

General Information About

Display for avoiding stop

Icons for user-defined SFC

Proper use of Siemens products

Copyright Siemens AG 2014.

General Information About Block Description.............................................................................................11

Display for avoiding stop without asset management................................................................................15

Icons for user-defined SFC types...............................................................................................................17

FM_CO: Coordination of function blocks which read data records.............................................19

CONEC: Monitoring the AS connection status............................................................................23

CPU_RT: Determination of the runtime of OBs...........................................................................27

DIAG_AB: Evaluation of statusword AB7000..............................................................................35

DPAY_V0: Monitoring DP/PA and Y-Link operating as V0 slave................................................38

DPAY_V1: Enabling blocks downstream of a DP/PA and Y-Link operating as V1 slave............45

DPAY_V1_PN: Enabling blocks downstream of a DP/PA and Y-link operating as a V1 Slave......47

DREP: Diagnostic Repeater in the DP master system................................................................52

DREP_L: Diagnostic Repeater downstream of a Y-Link.............................................................59

Basic Library (V8.1)

Message texts and associated values of DREP_L......................................................................65

FFD_CIF: Monitoring FF slaves in CIF mode..............................................................................66

FFDP_L1: Monitoring FF slaves with maximum 32 values.........................................................70

FF_MOD32: Diagnostics of an FF slave (downstream from FF link DPV1)................................73

FM_CNT: Programming and controlling FM 350 modules..........................................................78

IMDRV_TS: Transferring time-stamped process-signal changes...............................................83

MOD_1: Monitoring up to 16 channels on S7-300/400 SM modules without diagnostic

MOD_2: Monitoring 32 channels on S7-300/400 SM modules without diagnostic capability......96

MOD_3: Monitoring up to 16 channels on S7-200/300/400 SM modules without diagnostic

MOD_4: Monitoring ET 200S modules downstream of a Y-Link...............................................109

MOD_64: Monitoring 64 channels on S7-300 SM modules without diagnostic capability.........115

MOD_CENTRAL: Monitoring CPUs which are not capable of diagnostics...............................122

Basic Library (V8.1)

MOD_CP: CP 341 diagnostics..................................................................................................125

MOD_CP_PN: Monitoring of serial communication modules....................................................130

MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules with diagnostic

MOD_D16_PN: Monitoring S7-300 SM modules with up to 16 channels and with diagnostics

MOD_D24_PN: Monitoring S7-300 SM modules with up to 24 channels and with diagnostics

MOD_D3: Monitoring of hybrid modules with diagnostic capability...........................................165

MOD_D8_PN: Monitoring S7-300 SM modules with up to 8 channels and with diagnostics

MOD_DRV: Monitoring of drive blocks with diagnostics functions............................................181

MOD_HA: Monitoring device-specific diagnostics of HART field devices.................................186

MOD_HA_PN: Monitoring Device-Specific Diagnostics of HART Field Devices.......................195

Basic Library (V8.1)

MOD_MS: Monitoring up to 16 channels on ET200S/X motor starter modules with

MOD_SWT: Monitoring of Switch blocks with diagnostics functions.........................................207

MOD_PAX0: Diagnosing a DPV0 PA slave (via DP/PA coupler with connection to a DP

OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics...............................................223

OB_BEGIN_PN: CPU diagnostics.............................................................................................233

OB_BEGIN_HPN: H-CPU diagnostics......................................................................................238

OB_DIAG1: OB diagnostics for avoiding stoppages in DPV1 master systems.........................245

OB_DIAG1_PN: OB diagnostics for avoiding stoppages in DPV1 master systems..................251

OB_DIAGF: Monitoring of the FF link and coupler....................................................................254

OB_END: Reset stack pointer of OB_BEGIN............................................................................258

Basic Library (V8.1)

OR_32_TS: OR value status of two redundant time-stamped signal modules, max. 32