6ES7658-...05-.... - Siemens

Contents

Notes 1

Signal blocks and diagnostic

drivers 2

PROFIBUS PA - Blocks 3

Appendix

Appendix A

Index

SIMATIC

Process Control System PCS 7

Driver Blocks

Reference Manual

Edition 10/2001

A5E00127662-01

04.10.200109.10.200109.10.2001

The reproduction, transmission or use of this document or its contents

is not permitted without express written authorit y. Offende rs will be

liable for damages. All rights, including rights created by patent grant

or registration of a utility model or design, are reserved.

Siemens AG

Bereich Automatisierungs- und Antriebstechnik

Geschae fts gebi et Ind ustrie-A utom a tisier u ngssysteme

Postfach 48 48, D- 90 327 Nuern be rg

Disclaimer of Liabili ty

We have checked the contents of this manual for agreement with the

hardware and software described. Since deviations cannot be

precluded entirely, we cannot guarantee full agreement. However, the

data in this manual are reviewed regularly and any necessary

corrections included in subsequent editions. Suggestions for

improvement are wel com e d.

©Siemens AG 2001

Technical data subject to change.

Siemens Aktiengesellschaft A5E00127662

Safety Guidelines

This manual contai ns notices whic h you shoul d observe t o ensure your own personal safety, as well as to

protect the product and c onnect ed equipment. These notices are highlighted in the manual by a warning

triangle and are marked as fol l ows according to the level of danger:

!Danger

indicates that death, severe personal injury or substantial property damage will result if proper

precautions are not taken.

!Warning

indicates that death, severe personal injury or substantial propert y dam age can result i f proper

precautions are not taken.

!Caution

indicat es that minor personal i nj ury or propert y damage can result if proper precautions are not taken.

Note

draws your attention to part icul arl y important information on the product, handli ng the product , or to a

particular part of the documentati on.

Qualified Personnel

Only qualified personnel should be allowed to install and work on this equipment. Qualif i ed persons are

defined as persons who are authorized to commission, to ground, and to tag circuits, equi pm ent, and

syst ems in accordance with established safety practices and standards.

Correct Usage

Note the following:

!Warning

This device and its components may only be used for the applications described in the catalog or the

technical descri ptions, and only in connecti o n with devic es or com ponents from other manufacturers

which have been approved or recommended by Siem ens.

This product can only f unction correctly and safely if it is trans ported, stored, set up, and installed

correct l y, and operated and maintained as recomm ended.

Trademarks

SIMATIC®, SI MATIC HMI® and SIMATIC NET® are registered trademarks of SIEMENS AG.

Some of other desi gnations used in these documents are also registered trademarks ; t h e owner's right s m ay

be violated if they are us ed by thi rd parties for thei r own purposes.

04.10.200109.10.200109.10.2001

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 iii

Contents

1Notes

1.1 Notes on Using Driver Blocks...........................................................................1-1

1.2 General information on the block description....................................................1-2

2 Signal blocks and diagnostic drivers

2.1 OB_BEGIN: CPU diagnostics and AS connection diagnostics.........................2-1

2.1.1 Connections of OB_BEGIN...............................................................................2-5

2.1.2 Assignment of the control system messages of the OB_BEGIN......................2-6

2.2 OB_END: Reset stack pointer of the OB_BEGIN...........................................2-10

2.2.1 Connections of OB_END ................................................................................2-11

2.3 OB_DIAG: OB diagnostics to avoid CPU stop................................................2-12

2.3.1 Connections of OB_DIAG...............................................................................2-14

2.4 SUBNET: Runtime group control for driver blocks .........................................2-16

2.4.1 SUBNET: DP Master system monitoring........................................................2-16

2.4.2 Connections of SUBNET.................................................................................2-19

2.4.3 Message texts and auxiliary process values of SUBNET...............................2-20

2.5 RACK: Signal rack failure................................................................................2-20

2.5.1 RACK: Rack monitoring..................................................................................2-20

2.5.2 Connections of RACK.....................................................................................2-24

2.5.3 Message texts and auxiliary process values of RACK ...................................2-24

2.6 PO_UPDAT: Update process image...............................................................2-25

2.7 IM_DRV: Transferring time-stamped process signal changes .......................2-26

2.7.1 Connections of IM_DRV..................................................................................2-31

2.7.2 Message texts and auxiliary process values of the IM_DRV..........................2-31

2.7.3 Interface IM .....................................................................................................2-33

2.8 MOD_1: Diagnostic driver for S7-300/400 SM modules which cannot be

diagnosed with 16 channels............................................................................2-36

2.8.1 MOD_1: Monitoring of S7-300/400 SM modules which cannot

be diagnosed with 16 channels maximum......................................................2-36

2.8.2 Connections of MOD_1 / MOD_2 ...................................................................2-39

2.8.3 Message texts and auxiliary process values of MOD_1 / MOD_2..................2-40

2.9 MOD_2: Diagnostic driver for S7-300/400 SM modules which cannot

be diagnosed with 32 channels.......................................................................2-41

2.9.1 MOD_2: Monitoring of S7-300/400 SM modules which cannot

be diagnosed with 32 channels.......................................................................2-41

2.10 MOD_D1: Diagnostic driver for S7-300/400 SM modules which can be

diagnosed with 16 channels............................................................................2-45

2.10.1 MOD_D1: Monitoring of S7-300/400 SM modules which can be

diagnosed with 16 channels maximum...........................................................2-45

2.10.2 Connections of MOD_D1 / MOD_D2..............................................................2-51

2.10.3 Message texts and auxiliary process values of MOD_D1 ..............................2-52

04.10.200104.10.200104.10.200109.10.200109.10.2001

Contents

Process Cont rol System PCS 7, Driver Block s

iv A5E00127662-01

2.11 MOD_D2: Diagnostic driver for S7-300/400 SM modules which can be

diagnosed with 32 channels............................................................................2-53

2.11.1 MOD_D2: Monitoring of S7-300/400 SM modules which can be

diagnosed with 32 channels............................................................................2-53

2.11.2 Message texts and auxiliary process values of MOD_D2...............................2-59

2.12 CH_AI: Analog value input..............................................................................2-61

2.12.1 Connections of CH_AI.....................................................................................2-64

2.13 CH_AO: Analog va lue out put..........................................................................2-66

2.13.1 Connections of CH_AO...................................................................................2-69

2.14 CH_DI: Digital va lue in put...............................................................................2-70

2.14.1 Connections of CH_DI ....................................................................................2-72

2.15 CH_DO: Digital value output...........................................................................2-73

2.15.1 Connections of CH_DO...................................................................................2-75

2.16 CH_U_AI: Analo g val ue in put (Uni versal).......................................................2-76

2.16.1 Connections of CH_U_AI................................................................................2-80

2.17 CH_U_AO: Analog value output (Universal)...................................................2-82

2.17.1 Connections of CH_U_AO..............................................................................2-85

2.18 CH_U_DI: Digital value input (Universal)........................................................2-86

2.18.1 Connections of CH_U_DI................................................................................2-89

2.19 CH_U_DO Digital va lue output (Uni vers a l).....................................................2-90

2.19.1 Connections of CH_U_DO..............................................................................2-93

3 PROFIBUS PA blocks

3.1 PA_AI: Analog value input PROFIBUS PA.......................................................3-1

3.1.1 PA_AI: Analog Input PROFIBUS PA.................................................................3-1

3.1.2 Connections of PA_AI.......................................................................................3-4

3.1.3 Message texts and auxiliary process values of PA_AI .....................................3-6

3.2 PA_AO: Analo g val ue outpu t PROF IB US PA...................................................3-6

3.2.1 PA_AO: Analo g Out put PROFIB US P A............................................................3-6

3.2.2 Connections of PA_AO.....................................................................................3-9

3.2.3 Message texts and auxiliary process values of PA_AO..................................3-12

3.3 PA_DI: Digital val ue in put PROF IB US PA......................................................3-13

3.3.1 PA_DI: Discrete Input PROFIBUS PA ............................................................3-13

3.3.2 Connections of PA_DI.....................................................................................3-15

3.3.3 Message texts and auxiliary process values of PA_DI...................................3-17

3.4 PA_DO: Digital value output PROFIBUS PA..................................................3-17

3.4.1 PA_DO: Discrete Output PROFIBUS PA........................................................3-17

3.4.2 Connections of PA_DO...................................................................................3-20

3.4.3 Message texts and auxiliary process values of PA_DO .................................3-22

3.5 PADP_L0x: Monitoring of DP/PA slaves.........................................................3-23

3.5.1 PADP_L00: Monitoring of DP/PA slaves with up to 7 slots ............................3-23

3.5.2 Message texts and auxiliary process values of PADP_L00............................3-27

3.5.3 PADP_L01: Monitoring of DP/PA slaves with up to 16 slots ..........................3-27

3.5.4 Message texts and auxiliary process values of PADP_L01............................3-31

3.5.5 PADP_L02: Monitoring of DP/PA slaves with up to 32 slots ..........................3-32

3.5.6 Message texts and auxiliary process values of PADP_L02............................3-36

3.5.7 Connections of PADP_L0x..............................................................................3-38

3.6 DPAY_V0: Monitoring of DP/PA-Link and Y-Link as V0 slave .......................3-38

3.6.1 DPAY_V0: Monitoring of DP/PA-Link and Y-Link as V0 slave .......................3-38

3.6.2 Connections of DPAY_V0...............................................................................3-43

3.6.3 Message texts and auxiliary process values of DPAY_V0 .............................3-44

3.7 PA_TOT : Totalizer PRO FIBU S P A.................................................................3-45

3.7.1 Connections of PA_TOT.................................................................................3-48

3.7.2 Message texts and auxiliary process values of PA_TOT ...............................3-50

04.10.200104.10.200104.10.200109.10.200109.10.2001

Contents

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 v

A Appendix

A.1 Addressing ....................................................................................................... A-1

A.2 Error information of the MSG_STAT output parameter ................................... A-2

A.3 MODE settings for Signal Modules.................................................................. A-2

A.4 MODE settings for PA Devices........................................................................ A-7

A.5 Text Library for Signal Modules ....................................................................... A-8

A.6 Text Libraries for DP-/PA-Slaves after a PA-/Y-LINK DP V0........................... A-9

A.7 Technical data................................................................................................ A-10

Index

04.10.200104.10.200104.10.200109.10.200109.10.2001

Contents

Process Cont rol System PCS 7, Driver Block s

vi A5E00127662-01

04.10.200104.10.200104.10.200109.10.200109.10.2001

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 1-1

1 Notes

1.1 Notes on Using Driver Blocks

General

• The OBs in which the blocks are installed are given in the description of the

driver blocks. Please note that not all OBs listed here are generated in all

CPUs. Relevant information can be found in the Online Help of the respective

OBs.

• In the event that the driver blocks of PCS 7 Driver Blocks V52 are used by the

driver generator, a firmware version V3.0 or faster is required in the target

system.

Signal Processing Blocks

Three types of channel blocks for signal processing are available in this library of

the driver blocks:

1. Standard Channel Blocks:

CH_AI, CH_AO, CH_DI, CH_DO.

They are used exclusively for signal processing of S7-300/400 SM modules.

Please use these standard blocks if you want to achieve memory and run-time

optimization and do not need to process any PA devices.

2. Universal Channel Blocks:

CH_U_AI, CH_U_AO, CH_U_DI, CH_U_DO.

These blocks are used for signal processing of S7-300/400 SM modules or a

PA field device. The advantage of these blocks is that you can create CFC

charts regardless of the hardware peripherals to be used later. As a

disadvantage, the universal blocks require more memory and run-time.

3. PA Channel Blocks:

PA_AI, PA_AO, PA_DI, PA_DO, PA_TOT

These blocks are designed especially for use with PA field devices. They are

used mainly where the special features of these devices should be used. In

contrary to the CH blocks, the PA channel blocks process not only the signal

itself, but also all variables according to the desired configuration of the

hardware of the device.

09.10.2001

Notes

Process Cont rol System PCS 7, Driver Block s

1-2 A5E00127662-01

1.2 General information on the block description

The block descriptions always have the same structure. The number of sections

may vary depending on the block functions. The most common sections have the

following meanings:

Heading of the block description

Example: RACK: Rack Monitoring

The header begins with the type name of the block (RACK). This name is entered

in the symbol name and has to be unique within your project.

The type name also includes information on the task/function of the block (Rack

Monitoring).

Object name (Type + Number)

FB x

The object name for the block type is made up of the realization type

Function block = FB, Function = FC and the Block number = x.

Command button for the displaying the block connections

Example:

You can jump directly to the list of block connections of the designated block by

clicking on the "Block Connections" command button. The preceding block symbol

is used as an eye-catcher in order to find the command button rapidly.

Note: The button is not visable in the paper printout.

Area of Application

You can see here which tasks the block should accept and other information about

its use in CFC if necessary.

Callin g OBs

Here you will find information relating to the organization blocks (OBs), in which the

described block must be installed. When using the CFC installation is carried out in

the cyclic OB (watchdog interrupt) and automatically into the OBs which are listed

in the task list of the block (for example in OB100 for restarting).

CFC creates the required OBs while compiling. If you use the blocks without CFC,

you have to program these OBs and call the instance of the block in them.

09.10.2001

Notes

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 1-3

Use in CFC

If it is not already mentioned under "Area of Application", you can find the

information here accepted by the driver generator. (the driver generator is called in

SIMATIC manager by the selected chart folder and with the menu command

Options > Charts > Generate Module Drivers... or as an option in the dial og box

of the CFC "Compile Charts as Program").

Function and Operating principle

This briefly describes the function of the block.

Detailed information is displayed on complex blocks e.g. on the function of

individual inputs, operating modes, time sequences etc..

Error handling

You will find the error display in the CFC chart at the Boolean block output ENO.

The value corresponds to the BIE (Binary result in STEP 7-STL after ending the

block) or the OK bit (in SCL notation) and means:

ENO=BIE=OK=1 (TRUE) ->The result of the block is OK.

ENO=BIE=OK=0 (FALSE) ->The result or the conditions for its calculation (e.g.

input values, operating modes, etc.) are not valid.

In addition, for FBs, you will find the inverted BIE in output QERR of the instance

DB:

QERR=NOT ENO

The error display arises by two independent routes:

The operating system recognizes a processing error (for example: value overflow,

called system functions supply an error code with binary input bit=0).

This is a system utility and is not mentioned specifically in the individual block

description.

The block algorithm checks values and operating modes for their functional legality.

These error cases are documented in the description of the block.

The evaluation of the error indication can be used, for example, to generate

messages (refer to the section on alarm blocks) or to utilize substitute values for

invalid results.

Start-up characteristics

A difference is made between:

• Initial start

The block is called for the first time from the OB, in which it is installed. As a

rule this is the OB in which normal, process-specific processing occurs (for

example: the watchdog interrupt OB).

The block enters the status corresponding to the input parameters. These can

be initial values (also refer to the Connections) or values which you have

already been configured, for example in CFC. The initial-start behavior is not

described separately unless the block deviates from this rule.

09.10.2001

Notes

Process Cont rol System PCS 7, Driver Block s

1-4 A5E00127662-01

• Start-up

The block is executed once during a CPU start-up. This is achieved by calling

the block from the start-up OB (where it is additionally installed either

automatically via ES or manually by you via STEP 7). In this case the start-up

characteristics are described.

Time response

The block with these characteristics must be installed into a watchdog interrupt OB.

Reference is then made to the time characteristic when instructed by the block.

Message characteristics

The block with these characteristics signals various events to the higher-ranking

OS. If they exist, the parameters required to generate messages are documented.

Blocks not having message characteristics can be complemented by additional

alarm blocks. A reference to the message characteristics in contained in the

description of the individual blocks with signaling capabilities.

Connections of ...

The connections provide the data interface of the block. In addition you can

transfer data to the block and fetch results from the block.

Connection

(parameter) Meaning Data type Default I/O OC&M

SUBN1ERR 1=Erro r in DP master system BOOL 0 O +

.....

The "Connections" table lists all the input and outputs of the block type, which the

user can access with the configuration tools. They are alphabetically. Elements

which can only be accessed from the algorithm of the block are not listed (so-called

internal variables).

The columns have the following meaning:

Connection = Name of parameter, derived from the English designation.

Wherever laid down by SIMATIC conventions, the same name rules have been

used.

The state of delivery of the block display in CFC is identified as follows: Connection

name bold = Connection displayed, normal = Not displayed.

Meaning = Function (possibly short description)

Data type = S7 data type of the param eter (BOO L, REAL, etc.).

Initial (Default) = The value of the parameter before the block is executed for the

first time (unless changed by configuration).

I/O = Type of access of the block algorithm to the parameter. Differentiates

between inputs, non-interacting inputs and outputs (see table)

09.10.2001

Notes

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 1-5

Abbre-

viation I/O

I Input. Initialize block with parameters (representation in CFC: left-hand block side).

O Output. Output value (representation in CFC: right-hand block side).

IO Input/output. Non-interacting input which is written and which can be written back

from the block (representation in CFC: left-hand block side).

OC&M= Parameters marked with "+" can be operator controlled and monitored via

the corresponding OS block.

Operator control and monitoring

The blocks from this library do not have preconfigured faceplates which control and

monitor the OS. If individual faceplates are used for specific diagnostic blocks, the

predetermined variables are transferred from the instance block to the OS. This

has to be set for the driver generator in the dialog box "Settings – Generate Module

Drivers" where the option "Operate C and M capability for diagnostic blocks" can

be set. Default: Option is not set.

09.10.2001

Notes

Process Cont rol System PCS 7, Driver Block s

1-6 A5E00127662-01

09.10.2001

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-1

2 Signal blocks and diagnostic drivers

2.1 OB_BEGIN: CPU diagnostics and AS connection

diagnostics

Object name (Type + Number)

FB 100

Area of Application

The block is used for CPU diagnostics and connection diagnostics of the

automation systems (AS). Installing the block in CFC creates all the acyclic priority

classes (OBs) in which the blocks of the Driver Blocks library run.

If the CFC function "Generate Module Driver" is used, the OB_BEGIN is installed

automatically.

Callin g OBs :

OB1 Cyclic processing

OB32 Watchdog interrupt (connection diagnostics with SFC 87) *)

OB70 I/O redundancy error

OB72 CPU redundancy error

OB80 Timeout

OB81 Power failure fault

OB82 Diagnostic interrupt

OB83 Withdrawn/plugged alarm

OB84 CPU hardware error

OB85 Program execution error

OB86 Rack failure

OB100 Restart:

OB121 Programming error

OB12 2 I/O access error

*) If you do not position the OB_BEGIN with the function "Create Module Driver" in the

CFC chart, but insert it manually into a CFC chart, it is installed in the OB specified by

"Predecessor for Installation". This may not be the OB32.

Please note that only one watchdog interrupt OB is allowed.

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-2 A5E00127662-01

Function and Operating principle

The block is used to signal and display CPU events and states. It reads the starting

information of the priority classes (OBs), the diagnostic data of the I/O devices and

enables the respective blocks on the basis of the start events.

From the starting information of the SFC6 (RD_SINFO) or SFB 54 (RALRM) the

OB_BEGIN determines the current OB in which it is running.

In as far as it does not exist, it converts the logical basic address from the starting

information into the geographic address. It is contained in the respective OBs of the

output structure CPU_DIAG, which the downstream blocks can access. On the

basis of the geographic address it enables the respective SUBNET blocks for

further evaluation of the starting information.

With the SFB 54 the diagnostic data are saved synchronously with the starting

information in the CPU_DIAG.OB82 structure in a diagnostic case (OB82).

Diagnostic (alarm) information longer than 59 bytes have to call the respective

driver blocks themselves.

The OB_BEGIN generates messages which are emitted with ALARM_8P to

WinCC (see message characteristics). The SFC 87 C_DIAG is called in a

watchdog interrupt OB (OB32) after 10 cycles have expired for connection

diagnosis. Up to 64 connections are monitored.

In the case of H systems the current state of the two H-CPUs is determined in the

same watchdog interrupt OB by reading the system state list 71 (SSL71). For a

detailed description of the meaning of the SSL71 please refer to the reference

manual "System Software for S7-300/400 System and Standard Functions".

Note

The messages "Failure or redundancy loss connection ID" are generated at every

CPU of the two connected AS. Exception at the failure of the CPU (or both

H-CPUs) of an AS.

Error handling

The block evaluates the error information of ALARM_8P and writes it to the

corres pondi ng out put parameters .

See Error information of the MSG_STAT output parameter.

The block may only be installed in a watchdog interrupt OB. Otherwise QERR =

TRUE is set and operation is continued with the watchdog interrupt OB which first

called the block after the restart/initial start.

If the block installation sequence OB_BEGIN, xx blocks, ..., OB_END is not

observed, the message "Incorrect installation OB_END, no OB8x processing" is

output and QERR = TRUE is set. In this case no evaluation is carried out in the

acyclic OBs. The downstream blocks are not enabled.

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-3

Start-up characteristics

The OB_BEGIN initializes the messages of ALARM_8P. In the case of H systems

(CPU_DIAG.H_MODE = TRUE) the current state of the two H-CPUs is determined

by reading the SSL71 (see Function).

In as far as a CPU with SFC 87 exists, the connection diagnosis is initialized. The

system then waits for 120 cycles in the watchdog interrupt OB until the connection

diagnosis messages are generated.

Initi al- start behavior

The starting information is read with SFC 6.

Time response

The block is installed into the required OBs (refer to the Function section)

automatically during structuring by the ES, including into the watchdog interrupt

OB32. The latter OB installations can be changed as required.

Message characteristics

The ALARM_8P multiple-instances are only called when a message of the

OB_BEGIN is to be emitted. Effected acknowledgments of preceding messages

are not updated by the respective ALARM block until this moment. If the

connection to WinCC is interrupted, each ALARM_8P can save a maximum of two

message states of an Event-ID.

A programming error (OB121) is only generated by the CPU as a coming event.

In the OB1 the respective generated coming message "Programming error" is reset

as going. In order to avoid an overload of programming error messages these are

counted within an interval of 1 minute. If more than 5 programming errors are noted

within one minute, the subsequent ones are rejected. The maximum of 5

"Programming error" messages are then not generated until at least one minute

has passed.

Messages of the OB_DIAG block

The OB-DIAG blocks are connected to the system structure OB_LOCK. If the

OB82 is blocked by the OB_DIAG block, a message "OB82 failure SUBNET:xx

RACK:yy SLOT:zz" is generated. If the OB86 is blocked by the OB_DIAG block, a

message "OB86 failure SUBNET:xx RACK:yy SLOT:zz" is generated.

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-4 A5E00127662-01

The block generates the following messages in the OBs listed below:

OB Starting event Message

OB1 Cyclic processing Going message:

- Timeout

- Program execution error

- Programming error

OB32 1 sec. watchdog interrupt or alternative

watchdog interrupt OB Failure connection ID: xx coming/going

Redundancy loss connection ID: xx coming/going

OB72 CPU redundancy loss CPU redundancy loss/return

OB80 Timeout Coming message at timeout:

- Cycle time exceeded

- OB request: OBxx still being processed

- OB request: Overflow PRIOxx

- Time interrupt xx expired

OB81 Power failure fault - Central controller battery failure

coming/going

- Central controller backup voltage failure

coming/going

- Central controller 24 V supply failure

coming/going

- Redundant central controller battery

failure coming/going

- Redundant central controller backup

voltage failure coming/going

- Redundant central controller 24 V supply

failure coming/going

OB84 CPU hardware error MPSS error coming/going

OB85 Program execution error Coming message at program execution error

- OBxx not loaded

- Access-error error xx: ...

OB100 Restart: Initializing ALARM_8P

OB121 Programming error Programming error coming

Operator control and monitoring

The block does not have a faceplate (display block).

Note:

In "Connection of OB_BEGIN" the variables are identified (with a "+" in the column

OCM ) which are transferred from this instance block to the OS when the option

"Operator C and M capability for diagnostic blocks" in the "Generate Module

Driver" settings is selected. Default: option is not set.

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-5

2.1.1 Connections of OB_BEGIN

The state of delivery of the block display in the CFC is marked in the "Connection"

column: Connection name bold = Connection displayed, normal = Not displayed.

Connection

(parameter) Meaning Data

type Initial I/O OC

&M Valid

values

CPU_DIAG System Structure CPU-Diagnosis STRUCT O

CPUERR_0 1=CPU Failure in Rack 0 BOOL 0 O +

CPUERR_1 1=CPU Failure in Rack 1 BOOL 0 O +

EN_SUBx Enable SUBNET x (xx=00 - 14) BOOL 0 O

EV_IDx EVENT IDx

Message Number ALARM_8P_x

(x = 1 - 19)

DWORD 0 I (is assigned by

ES)

MASTER_0 1=Master CPU i n Rack 0 BOOL 0 O +

MASTER_1 1=Master CPU i n Rack 1 BOOL 0 O +

MSGSTATx Message Status Output

STATUS output of the ALARM_8P_x

(x = 1 - 19)

WORD 0 O

OB_LOCK LOCKED OB STRUCT O

QERR 1=Error BOOL 1 O

QMSGERx Message Error

Error output of the ALARM_8P_x

(x = 1 - 19)

BOOL 0 O

SUB0IDxx SUBNET primary ID (xx = 00 - 14) BYTE 255 I

SUB1IDxx SUBNET secondary ID (xx=00 - 14) BYTE 255 I

SZL_71 System Structure SSL71 STRUCT O

The structure of the CPU_DIAG is implemented as OUT in the OB_BEGIN, and in

all other blocks with this connection as IN_OUT (column: I/O).

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-6 A5E00127662-01

2.1.2 Assignment of the control system messages of the OB_BEGIN

The control system messages are assigned as follows with ALARM_8P at EV_I D1

Message block

ALARM_8P Mess.

No. OB No. Default message text Message

class

EV_ID1 1 OB80 Cycle time exceeded: OB@1%d@ms OB@2%d@ S

2 OB86 OB86 Failure SUBNET:@7%d@ RACK:@8%d@ S

3 OB84 MPI error S

4 - Error installation OB_BEGIN/OB_END:

No OB@10%d@ Processing Stack @9%d@ -

5- Reserve -

6 OB122 Read error I/O device:

@4%2s@@5%d@ Addr: @6%d@ S

7 OB122 Write error I/O device:

@4%2s@@5%d@ Addr: @6%d@ S

8 OB72 CPU redundancy loss in Rack @3%d@ S

Messages 1, 6 and 8 are only coming events. They are reset as "going" during a

normal run (OB1) of the block.

Auxiliary process values of the EV_ID1

The control system messages are generated via ALARM_8P with EV_ID1 with six

auxiliary process values. The table shows the assignment of the auxiliary process

values to the block parameters.

Message block

ALARM_8P Auxiliary

process

value

Block parameter Data type

EV_ID1 1 OB80_Supplem ent ary _Info 1 WORD

2 OB80_1. Byte supplementary info 2_3 BYTE

3 Rack No. of the CPU BYTE

4 OB122_BLK_TYP WORD

5 OB122_BLK_NUM WORD

6 OB122_MEM_ADDR WORD

7 OB86 Subnet_ID BYTE

8 OB86 RACK_NO BYTE

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-7

The control system messages are assigned as follows with ALARM_8P at EV_I D2

Message block

ALARM_8P Mess.

No. OB

No. Default message text Message

class

EV_ID2 S

1 OB81 Battery failure CPU in Rack 0 S

2 OB81 Battery failure CPU in Rack 1 S

3 OB81 Backup voltage failure CPU in Rack 0 S

4 OB81 Backup voltage failure CPU in Rack 1 S

5 OB81 24V supply failure CPU in Rack 0 S

6 OB121 24V supply failure CPU in Rack 1 S

7 OB121 Programming error @1%d@: @2%2s@@5%d@

/@6%d@/@4%d@/@3%d@ S

8 OB82 OB82 Failure SUBNET:@7%d@ RACK:@8%d@

SLOT:@9%@ S

Message 7 is only a coming event. It is reset as "going" during a normal run (OB1)

of the block. It is to be interpreted as follows in accordance with the error code

number before the colon:

OB121_BLK_TYP/OB121_BLK_NUM/OB121_PRG_ADDR/OB121_FLT_REG/OB121_RES

ERVED_1.

For a description please refer to the reference manual "System Software for S7-

300/400 System and Standard Functions".

Example: 10.05.00 10:30:45 Programming error 35: FB44/1234/5/9

Auxiliary process values of the EV_ID2

The control system messages are generated via ALARM_8P with EV_ID2 with six

auxiliary process values. The table shows the assignment of the auxiliary process

values to the block parameters.

Message block

ALARM_8P Auxiliary

process

value

Block parameter Data type

EV_ID2 1 OB121_SW_FLT BYTE

2 OB121_BLK_TYP WORD

3 OB121_RESERVED_1 BYTE

4 OB121_FLT_REG WORD

5 OB121_BLK_NUM WORD

6 OB121_PRG_ADDR WORD

7 OB82 SUBNET_ID BYTE

8 OB82 RACK_NO BYTE

9 OB82 SLOT_NO BYTE

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-8 A5E00127662-01

The control system messages are assigned as follows with ALARM_8P at EV_I D3

Message block

ALARM_8P Mess.

No. OB No. Default message text Message

class

EV_ID3 1 OB80 OB request: OB@2%d@ still being processed S

2 OB80 OB request: Overflow PRIO@3%d@ S

3 OB80 Time interrupt OB@1%d@ expired S

4 OB85 OB @4%d@ not loaded S

5 OB85 Access-error error @4%d@:

@7%2s@@5%d@/@6%d@ S

6- Reserve -

7- Reserve -

8- Reserve -

Messages 1, 2, 3, 4 and 5 are only coming events. They are reset as "going"

during a normal run (OB1) of the block.

Auxiliary process values of EV_ID3

The control system messages are generated via ALARM_8P with EV_ID3 with six

auxiliary process values. The table shows the assignment of the auxiliary process

values to the block parameters.

Message block

ALARM_8P Auxiliary

process

value

Block parameter Data type

EV_ID3 1 OB80_Supplem ent ary _Info 1 WO R D

2 OB80_1. Byte supplementary info 2_3 BYTE

3 OB80_2. Byte supplementary info 2_3 BYTE

4 OB85_Supplem ent ary _Info 1 WO RD

5 OB85_HW_Supplementary_Info 2_3 WORD

6 OB85_LW_Supp lem entary _I nfo 2_3 WORD

7 OB85_DKZ2_3 WORD

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-9

The control system messages are assigned as follows with ALARM_8 at EV_ID4

to EV_ID19:

Message block

ALARM_8P Mess.

No. Default message text Message

class

EV_ID4 to EV_ID11 1 Failure connection ID: @1%d@ S

2 Failure connection ID: @2%d@ S

3 Failure connection ID: @3%d@ S

4 Failure connection ID: @4%d@ S

5 Failure connection ID: @5%d@ S

6 Failure connection ID: @6%d@ S

7 Failure connection ID: @7%d@ S

8 Failure connection ID: @8%d@ S

EV_ID12 to EV_ID191 Redundancy loss connection ID: @1%d@ S

2 Redundancy loss connection ID: @2%d@ S

3 Redundancy loss connection ID: @3%d@ S

4 Redundancy loss connection ID: @4%d@ S

5 Redundancy loss connection ID: @5%d@ S

6 Redundancy loss connection ID: @6%d@ S

7 Redundancy loss connection ID: @7%d@ S

8 Redundancy loss connection ID: @8%d@ S

Auxiliary process values from EV_ID4 to EV_ID19

The control system messages are generated via ALARM_8P with EV_ID4 to

EV_ID19 with eight auxiliary process values. The table shows the assignment of

the auxiliary process values to the block parameters.

Message block

ALARM_8P Auxiliary process value Block parameter Data type

EV_ID4... EV_ID19 1 Connection_ID 1+x WORD

2 Connection_ID 2+x WORD

3 Connection_ID 3+x WORD

4 Connection_ID 4+x WORD

5 Connection_ID 5+x WORD

6 Connection_ID 6+x WORD

7 Connection_ID 7+x WORD

8 Connection_ID 8+x WORD

x = 0 at EV_ID4, x = 8 at EV_ID5, x = 16 at EV_ID6 etc. to x = 56 at EV_ID12

x = 0 EV_ID13, x = 8 at EV_ID14, x = 16 at EV_ID15 etc. to x = 56 at EV_ID19

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-10 A5E00127662-01

2.2 OB_END: Reset stack pointer of the OB_BEGIN

Object name (Type + Number)

FC 280

Area of Application

The block is used to reset the stack pointer of the OB_BEGIN.

Callin g OBs

The OB_END has to be installed at the end of the OB in which an OB_BEGIN is

installed. An OB_END may not be installed in OBs in which no OB_BEGIN is

installed.

If the CFC function "Generate Module Driver" is used, the OB_END is installed

automatically in the OBs of the run sequence.

OB1 Cyclic processing

OB32 Watchdog interrupt (connection diagnostics) *)

OB70 I/O redundancy error

OB72 CPU redundancy error

OB80 Timeout

OB81 Power failure fault

OB82 Diagnostic interrupt

OB83 Withdrawn/plugged alarm

OB84 CPU hardware error

OB85 Program execution error

OB86 Rack failure

OB100 Restart:

OB121 Programming error

OB12 2 I/O access error

*) If you do not position the OB_END block with the function "Create Module Driver" in

the CFC chart, but insert it manually into a CFC chart, it is installed in the OB specified

by "Predecessor for Installation". This may not be the OB32.

Ensure that you use the watchdog interrupt OB of the OB_BEGIN.

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-11

Function and Operating Principle

The block decrements the stack pointer (NUM_CNT) of the OB_BEGIN. In case of

an interruption it enters the last interrupted OB number from the CPU stack into the

structu r e CPU_DIAG.

Error handling

Does not exist

Start-up characteristics

Do not exist

Initi al- start behavior

Does not exist

Time response

Does not exist

Message characteristics

Do not exist

Operator control and monitoring

The block does not have a faceplate (display block).

2.2.1 Connections of OB_END

Connection

(parameter) Meaning Data type I/O

CPU_DIAG CPU diagnostics (Syste m Structure) STRUCT I/O

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-12 A5E00127662-01

2.3 OB_DIA G: OB diagnostics to avoid CPU stop

Object name (Type + Number)

FC 281

Area of Application

The block is used in order to avoid a CPU stop when there is a defective DP slave.

It recognizes a DP slave failure. If DP slaves are activated in the H system, it

indicates the preferred channel of the DP slave.

Callin g OBs

The block has to be installed in the following OBs in the run sequence (is carried

out automatically in CFC):

OB1 Cyclic program

OB70 I/O redundancy error

OB72 CPU redundancy error

OB82 Diagnostic interrupt

OB83 Withdrawn/plugged interrupt

OB85 Program execution error

OB86 Rack failure

OB100 Restart (warm start)

Use in the CFC

If the CFC function "Generate Module Driver" is used, the following steps are

carried out automatically:

• The OB_DIAG block is installed after the SUBNET block.

• Configuration of

- The inputs RACK_NO, DADDR, SUBN1_ID, SUBN2_ID and SUBN_TYP.

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-13

• Interconnection of

- The EN input with the output of an AND block. Its inputs are interconnected

to the output EN_SUBx (x = No. of the DP Master System) of the OB

BEGIN block and to the output EN_Rxxx (xxx = Rack/Station Number) of

the SUBNET block.

- The OUT structure CPU_DIAG of the OB_BEGIN and SUB_DIAG of the

SUBNET block with the INOUT structures of the same name of the

OB_D IAG block.

Function and Operating principle

The block counts the frequency of the calls of an acyclic OB of a block instance

before an OB1 can be executed.

OB_DIAG displays higher-level errors of the CPU, DP Master and DP Slave

(SUBN1ERR, SUBN2ERR). If DP slaves are activated, it determines the preferred

channel (SUBN1ACT, SUBN2ACT). The group error information RACK_ERR

displays the failure of the DP Master and the failure of the DP Slave. This means if

RACK_ERR = 1, the corresponding DP Slave has failed, if SUBN1ERR or

SUBN2ERR = FALS E.

The start and diagnostic information is read from the structure CPU_DIAG which is

interconnected to the structure CPU_DIAG of the block OB_BEGIN.

The block determines the currently active preferred channel (SUBN1ACT,

SUBN2ACT) in the case of redundant PROFIBUS DP interfaces by evaluating the

error events and, if required, the diagnostic address ADDR of the DP slave.

If the DP Slave is connected to a DP Master system which is operated in the DP

V1 Mode, V1-MODE = TRUE is set.

Overload behavior

The OB_DIAG counts the frequency of the calls of the acyclic OB82 and OB86

(exception DP Master system failure, see SUBNET block). If the counter

DIAG82_CNT > 5 or DIAG86_CNT > 5, EN_F = FALSE is set (disable function

block). The counters are reset in the OB1. In all the other OBs the output EN_F =

TRUE (enable function block) is set.

If there is a malfunction of the OB82 or of the OB86, the OB_BEGIN block then

signals this malfunction with geographic address of the DP Slave in the OB1 or

OB82 or OB86 respectively.

The event is not evaluated due to the disabling of the OB82 or OB86 respectively

at an overload. The outputs cannot correspond to the current state of the DP

Slave. After a waiting period of approx. 1 minute the state of the DP Slave is

checked and the variable EN_86DIAG is set to TRUE in case of the OB86 failure.

Updating of the state of the DP Slave can take several cycles.

If there is an OB82 failure, the variable EN_82DIAG is set to TRUE. The

interconnected DP Slave block can then fetch the current diagnostic data of the DP

Slave.

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-14 A5E00127662-01

Redundancy

The block supports the redundancy of the DP Master systems at an H system (only

distributed I/O devices). To this purpose the inputs of the OB_DIAG block

SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) are to be

configured with the numbers of the redundant DP Master systems. If there is no

redundancy of the DP Master systems, the remaining input must have the value

16#FF (default) assigned.

Start-up characteristics

A check whether the DP Slave is available is carried out. In the case of H systems

the preferred channel of the DP Slave is determined.

Error handling

No plausibility checks are carried out with reference to the input parameters.

Time response

Does not exist.

Message characteristics

See OB_BEGIN block

Operator control and monitoring

The block has no faceplate.

2.3.1 Connections of OB_DIAG

The state of delivery of the block display in the CFC is marked in the "Connection"

column: Connection name bold = Connection displayed, normal = Not displayed.

Connection

(parameter) Meaning Data type Initial I/O

ACC_ID 1=Accept MODE settings BOOL 0 I/O

CPU_DIAG System Structure: CPU d iagnostics STRUCT I/O

DADDR Diagnostic Address of DP-Slave INT 0 I/O

EN_82DIAG 1=Read Diagnosis (OB82) BOOL 0 O

EN_86DIAG 1=Read Diagnosis (OB86) BOOL 0 O

EN_F 1= Enable Function/Function Block BOOL 0 O

LOCK_82 1= Locked OB82 BOOL 0 I/O

LOCK_86 1= Locked OB86 BOOL 0 I/O

LOCK_82_TM Delay Time Locked OB82 DINT 0 I/O

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-15

Connection

(parameter) Meaning Data type Initial I/O

LOCK_86_TM Delay Time Locked OB86 DINT 0 I/O

MSTR1ERR Reserve BOOL 0 I/O

MSTR2ERR Reserve BOOL 0 I/O

OB82_CNT Counter OB82 INT 0 I/O

OB86_CNT Counter OB86 INT 0 I/O

OB_LOCK System Structure: Locked OB STRUCT I/O

PARA Reserved BOOL 0 I/O

QRACKF 1=Rack Error BOOL 0 O

RACKF Reserve BOOL 0 I/O

RACK_NO Rack Number BYTE 0 I/O

SL1ERR Reserve BOOL 0 I/O

SL2ERR Reserve BOOL 0 I/O

SUB_DIAG OB_Start Information STRUCT I/O

SUBN_TYP 1=External DP interface BOOL 0 I/O

SUBN1_ID ID of Primary DP master system BYTE 255 I/O

SUBN1ACT 1=Slave 1 Active BOOL 0 O

SUBN1ERR 1= Primar y DP master system failure BOOL 0 O

SUBN2_ID ID of Redundant DP master syst em BYT E 255 O

SUBN2ACT 1=Slave 2 Active BOOL 0 O

SUBN2ERR 1= Redundant DP maste r system failure BOOL 0 O

SSL75 Reserve BOOL 0 I/O

SSL92a Reserve BOOL 0 I/O

SSL92b Reserve BOOL 0 I/O

V1_MODE 1=DPV1-Mode BOOL 0 O

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-16 A5E00127662-01

2.4 SUBNET: Runtime gr oup contr ol for driver blocks

2.4.1 SUBNET: DP Master system monitoring

Object name (Type + Number)

FB 106

Area of Application

The block is used to reduce the acyclic OB processing times. Only the blocks

actually affected can be called in case of an acyclic event.

Callin g OBs

The block has to be installed in the following OBs in the run sequence (is carried

out automatically in CFC):

OB1 Cyclic program

OB70 I/O redundancy error

OB72 CPU redundancy error

OB81 Power failure fault

OB82 Diagnostic interrupt

OB83 Withdrawn/plugged interrupt

OB85 Program execution error

OB86 Rack failure

OB100 Restart (warm start)

Use in the CFC

If the CFC function "Generate Module Driver" is used, the following steps are

carried out automatically:

• Creating runtime groups with driver blocks organized by racks.

• Configuration of

- The inputs SUBN1 _ID, SUB N2_ ID and SUB N+TYP.

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-17

• Interconnection of

- The outputs EN _Rxxx with the respective blocks (for example RACK).

- The INOUT structure CPU_DIAG with the OUT structure of the OB_BEGIN

block.

- The OUT structure SUB_DIAG with the INOUT structures of the respective

blocks (for example RACK).

Function and Operating principle

The SUBNET block monitors a DP Master system and enables the blocks (for

example RACK) for executing the connected DP Slaves (for example ET200M).

Corresponding messages are generated and the output variables SUBN1ERR and

SUBN2ERR set at a failure or redundancy loss of a DP master system. The output

structure SUB_DIAG contains the geographic address of the DP Master system

(and DP Master system 2 at H systems) as well as the group area 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 per connected DP Master system or once for the

centrally plugged I/O devices into the OBs listed above and is enabled by the

OB_BEGIN block. The start and diagnostic information is read from the I/O

structure CPU_DIAG. It has to be interconnected to the structure CPU_DIAG of the

OB_BEGIN block (is implemented automatically with the CFC function "Generate

Module Driver"). The SUBNET block has one enable output per connectable rack

or DP Master system (per expansion rack in the case of centralized I/O devices). It

uses the starting information of the calling OB to determine whether the signaled

result has occurred at its DP Master (or at the centrally plugged I/O devices) and

then sets the output for the respective rack or for the DP Master system (EN_Rx).

If redundant DP Master systems are used (only for H-CPUs), a rack (for example

ET200M) is connected to the two DP Masters and has the same station number at

both. The SUBNET block has two inputs (SUBNx_ID) and the type identifier

SUBN_TYP. If the DP Master is the integrated interface of the CPU module,

SUBN_TYP = FALSE is to be set. Otherwise SUBN_TYP = TRUE is to be set.

If a DP line fails, all EN_Rxxx are set to TRUE and the redundancy loss or failure is

signaled. The redundancy or DP Master return is signaled as soon as a failed DP

slave has established the connection again.

The state of the DP Master system, the set SUBNx_ID with type identifier, is saved

in the output structure SUB_DIAG.

If the event "Power failure fault" (OB81) occurs, the SUBNET block only enables

the RACK blocks if they are expansion racks. Expansion racks exist if

SUBNx_ID = 0.

If you want to change the inputs SUBN 1_I D (conn ec tion to CPU 0) and SUBN 2_I D

(connection to CPU 1) online without using the CFC function "Generate Module

Driver", you have to set the input ACC_ID = TRUE. This updates the output values.

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-18 A5E00127662-01

Redundancy

The SUBNET block supports the redundancy of DP Master systems of the

CPU 417H in case of distributed I/O devices. To this purpose the inputs SUBN1_ID

(connection to CPU 0) and SUBN2_ID (connection to CPU 1) are to be configured

with the numbers of the redundant DP Master systems. If there is no redundancy,

the remaining input must have the value 16#FF (default) assigned.

Error handling

Error handling of the block is limited to the error information of ALARM_8P. Refer

to Error information of the MSG_STAT output parameter

Start-up/In it i al- start behavior

The SUBNET block initializes the messages of ALARM_8P.

The operating mode of the DP Master system is sampled and entered in the

structure SUB_DIAG.V1_MODE with SSL 0X90H (0 = compatibility mode, 1=

DPV1 mode). If the DPV1 mode is active, the structure CPU_DIAG.MODE_V1 is

also set to TRUE.

Overload behavior

The SUBNET block counts the OB86 calls (only failures). The counter is reset in

the OB1. If more than two OB86 failure events occur successively before the cycle

checkpoint (OB1) is reached, these are rejected and a message "Failure OB86 DP

Master system:x" is emitted. If an OB86 call is rejected, the DP Master system is

registered as having failed.

Time response

Does not exist.

Message characteristics

After being called by an OB86, OB70 and OB72 the block analyzes the state of the

DP master system assigned to it and generates the corresponding messages for

redundancy loss and DP Master s ystem failure b y em itting an AL ARM _8 P.

Messaging can be de-activated by using EN_MSG = FALSE.

The SUBNET block generally only signals events whose cause lies within the DP

Master system monitored by it.

Exception C PU failur e in the H system :

- Non-redundant DP Master system: Message "DP Master failure".

- Redundant DP Master system: Message "DP Master redundancy loss".

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-19

Operator Control and Monitoring

The block has no faceplate.

Note:

In "Connection of SUBNET" the variables are identified (with a "+" in the column

OCM ) which are transferred from this instance block to the OS when the option

"Operator C and M capability for diagnostic blocks" in the "Generate Module

Driver" settings is selected. Default: option is not set.

2.4.2 Connections of SUBNET

The state of delivery of the block display in the CFC is marked in the "Connection"

column: Connection name bold = Connection displayed, normal = Not displayed.

Connection

(parameter) Meaning Data type Initial I/O OC&M

ACC_ID 1=Accept MODE settings BOOL 0 I/O

CPU_DIAG CPU diagnostics STRUCT I/O

EN_MSG 1=Enable message BOOL 1 I

EN_Rxxx 1=Enable Rack xxx BOOL 0 O

EV_ID Message ID DWORD 0 I

MSG_STAT Message Failure WORD 0 O

SUB_DIAG System Structure: CPU d iagnostics STRUCT O

SUBN_TYP 1=External DP-Interface BOOL 0 I/O

SUBN1_ID ID of Primary DP master system BYTE 25 5 I/O

SUBN1ERR 1= Error in primary DP Master system BOOL 0 O +

SUBN2_ID ID of Redundant DP master syst em BYTE 255 I/O

SUBN2ERR 1= Error in Redundant DP master system BOOL 0 O +

Note

The number of racks possible results from the address volume of PROFIBUS. All

available CPUs can thus be used. The entire address volume is used by the

CPU 417-4.

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-20 A5E00127662-01

2.4.3 Message texts and auxiliary process values of SUBNET

Assignment of message text and message class

Message No. Default message text Message class

1 DP master @1%d@: Redundancy loss S

2 DP master @2%d@: Redundancy loss S

3 DP master @1%d@: Failure S

4 DP master @2%d@: Failure S

5 Multiple line failure @2%d@OB86 lock

Assignment of the auxiliary values

Value Block parameter

1 Primary DP Master system number (SUBN1_ID)

2 Redundant DP Master system numb er (SUBN2_ID)

2.5 RA CK: Signal rack failure

2.5.1 RACK: Rack monitoring

Object name (Type + Number)

FB 107

Area of Application

The block monitors the state of a rack, a DP/PA or Y-Link DP V1 and signals the

corres pondi ng err or events .

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-21

Callin g OBs

The block has to be installed in the following OBs in the run sequence (is carried

out automatically in CFC):

OB1 Cyclic program

OB70 I/O redundancy error

OB72 CPU redundancy error

OB81 Power failure fault

OB82 Diagnostic interrupt

OB83 Withdrawn/plugged interrupt

OB85 Program execution error

OB86 Rack failure

OB100 Restart (warm start)

Use in the CFC

If the CFC function "Generate Module Driver" is used, the following steps are

carried out automatically:

• The RACK block is installed automatically in the run sequence after the

SUBNET block.

• Configuration of

- The inputs RACK_NO, DADDR, SUBN1_ID, SUBN2_ID and SUBN_TYP.

• Interconnection of

- The EN input with the output of an AND block. Its inputs are interconnected

to the output EN_SUBx of the OB BEGIN block and to the output EN_Rxxx

of the SUBNET block.

- The OUT structure CPU_DIAG of the OB_BEGIN and SUB_DIAG of the

SUBNET block with the INOUT structures of the same name of the RACK

block.

- OS operation: (LINK_MAN = 0): Low-speed and high-speed operation can

be switched on via the input SP1_ON and SP2_ON repectively and the

input MOT_OFF stops the operation. The enablings (S1_OP_EN,

S2_OP_EN or OFFOP_EN) have to be available.

Function and Operating principle

The RACK block generates a process control system fault message for the OSs in

case of redundancy losses and rack or stations failures. In addition it indicates

faults within the rack/the station (SUBN1ERR, SUBN2ERR) and the preferred

channel (SUBN1ACT, SUBN2ACT) when the DP slaves are activated at the

outputs. The output structure RAC_DIAG contains the geographic address of the

rack as well as the group error information RACK_ERR.

If RACK_ERR = 1, the corresponding rack is not available.

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-22 A5E00127662-01

The block is installed into the OBs listed above for each connected station and

once for the centrally plugged I/O devices. The runtime groups, in which the RACK

block is installed is enabled by the SUBNET block. The start and diagnostic

information is read from the I/O structure CPU_DIAG. It has to be interconnected to

the structure CPU_DIAG of the OB_BEGIN block (is implemented automatically

with the CFC function "Generate Module Driver"). The RACK block has one enable

output per slot of the rack (station).

The RACK block generates the number of a corresponding message (see

Message Behavior) on the basis of the start information of the calling OBs if the

current block is affected.

The block determines the currently active preferred channel (SUBN1ACT,

SUBN2ACT) in the case of redundant PROFIBUS DP interfaces by evaluating the

error events and, if required, the diagnostic address ADDR of the DP slave.

If you want to change the inputs SUBN 1_I D (conn ec tion to CPU 0) and SUBN 2_I D

(connection to CPU 1) online without using the CFC function "Generate Module

Driver", you have to set the input ACC_ID = TRUE. This updates the output values.

Redundancy

The RACK block supports the redundancy of DP Master systems within the H

systems in case of distributed I/O devices. To this purpose the inputs of the RACK

block SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) are

to be configured with the numbers of the redundant DP Master systems. If there is

no redundancy, the remaining input must have the value 16#FF (default) assigned.

Error handling

Error handling of the block is limited to the error information of ALARM_8P.

Refer to Error information of the MSG_STAT output parameter

Start-up characteristics

The RACK block initializes the messages of ALARM_8P. A check whether the

station is available is carried out. In the case of H systems the preferred channel of

the station is determined.

The structure SUB_DIAG.V1_MODE (0 = compatibility mode, 1= DPV1 mode) is

transferred to the structure RAC_DIAG.V1_MODE.

Overload behavior

The RACK block counts the OB86 calls (exception DP Master system failure, see

SUBNET block). The counter is reset in the OB1. If more than two OB86 events

occur successively before the cycle checkpoint (OB1) is reached, these are

rejected and a message "Failure OB86 DP Master:x Rack:y" is emitted. If an OB86

call is rejected, the rack (station) is registered as having failed.

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-23

Time response

See Message characteristics

Message characteristics

After being called by OB70, OB72, OB85 or OB86 the block analyzes the state of

the CPU, DP master and DP slaves assigned to it. If necessary, it generates the

corresponding messages for redundancy losses and rack (station) failures in the

rack by emitting an ALARM_8P. Messaging can be de-activated by using EN_MSG

= FALSE.

The block generally only signals events whose cause lies within the rack monitored

by it. Redundancy loss and station 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 allows a signal delay, which can be configured, for an outgoing

higher-order error. If, for example, the RACK block recognizes an outgoing error in

a DP master connected to it, it initially assumes that there is a faulty assigned DP

slave in the rack monitored by it and sets the corresponding output SUBNxERR.

The error is not canceled until the DP slave returns (in this case: OB86, OB70).

The RACK blocks suppress the potential slave failure for DELAY seconds in order

not to trigger a wave of messages from the DP slaves which are not synchronized

yet after the master returns. An error message is not output to the OSs unless a

DP slave does not report its return before this period expires.

Note

You should not set the value of DELAY too high. Otherwise DP slaves which were

removed during the master failure or which are defective will be reported back to

the OSs after the master returns with a correspondingly high delay period.

The RACK block generates the following messages in the OBs listed below:

OB Starting event Message

OB1 Cyclic processing Repeat updating ALARM_8P outputs / messages, if necessary

OB70 Redundancy loss DP Slave redundancy loss/return

OB81 Power failure fault - Rack battery failure coming/going - Rack backup voltage failure

coming/going - Rack 24 V supply failure coming/going

OB85 I/O a ccess err or Rack failure going

OB86 Rack monitoring Rack failure coming/going

OB100 Restart: Initializing ALARM_8P

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-24 A5E00127662-01

2.5.2 Connections of RACK

The state of delivery of the block display in the CFC is marked in the "Connection"

column: Connection name bold = Connection displayed, normal = Not displayed.

Connection

(parameter) Meaning Data type Initial I/O O&M

ACC_ID 1=Accept MODE settings BOOL 0 I/O

CPU_DIAG CPU diagnostics (Syste m Structure) STRUCT I/O

DADDR Diagnostic Address of DP-Slave INT 0 I

DELAY Alarm Delay (s) INT 15 I

EN_MSG 1 = Enable message BOOL 1 I

EN_Mxx 1=Enable module xx (xx = 00 – 30) BOOL 1 I

EV_ID Message number DWORD 0 I

MSG_STAT Message error information WORD 0 O

RAC_DIAG System Structure (reserve): STRUCT I

RACK_NO Rack Number BYTE 0 I

SUB_DIAG OB_Start Information STRUCT I/O

SUBN_TYP 1=External DP interface BOOL 0 I/O

SUBN1_ID ID of Primary DP master system BYTE 255 I /O

SUBN1ACT 1=Slave 1 Active BOOL 0 O +

SUBN1ERR 1=Error in Primary DP master system BOOL 0 O +

SUBN2_ID ID of Redundant DP master syst em BYTE 2 55 I/O

SUBN2ACT 1=Slave 2 Active BOOL 0 O +

SUBN2ERR 1=Error in Redundant DP master system BOOL 0 O +

2.5.3 Message texts and auxiliary process values of RACK

Assignment of message text and message class

Message No. Default message text Message class

1 Station @1%d@/ @3%d@: Redundancy loss S

2 Station @2%d@/ @3%d@: Redundancy loss S

3 Station @1%d@/ @3%d@: Failure S

4 Station @2%d@/ @3%d@: Failure S

5 Station @1%d@/ @3%d@: Backup battery failure S

6 Station @1%d@/ @3%d@: Backup voltage failure S

7 Station @1%d@/ @3%d@: 24 V supply failure S

8 Multiple line failure @1%d@/ @3%d@ OB86 Lock S

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-25

Assignment of the auxiliary values

Value Block parameter

1 Primary DP Master system number (SUBN1_ID)

2 Redundant DP Master system numb er (SUBN2_ID)

3 Rack or station number (RACK_NO)

Special case at OB81 (Power failure fault): If SUBN1_ID = 16#FF, auxiliary

process value 1 = SUBN2_ID is set.

2.6 PO_UPDAT: Update process image

Object name (Type + Number)

FC 279

Area of Application

The block ensures the functions "Hold last value" and "Apply substitution value" of

the output modules when a CPU is restarted (OB100).

Callin g OBs

The block must be installed at the end of the OB100. This is carried out for you by

the CFC function "Generate Module Driver".

Functional descripti on

When a CPU is restarted (OB100), the CH_AO, CH U AO, CH_DO and CH_U_DO

blocks write the start values to the process image. The PO_UPDAT block sends all

the (part) process images to the modules at the end of the OB100 in order for

these values to be active immediately when the CPOU passes to RUN. The output

PO_MAP indicates the part process images updated or used in the system (BIT0:

Process image 0, BIT15: Part process image 15).

Connections of PO_UPDAT

Connection

(Parameter) Meaning Data type Defalt. Type

PO_MAP (Part) Process images updated or used in system (BIT0:

OB1 process image, BIT1 - 15: part process image

1 - 15)

WORD 0 O

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-26 A5E00127662-01

2.7 IM_DRV: Transferring time-stamped process signal

changes

Object name (Type + Number)

FB 90

Callin g OBs

If you use CFC, the block is installed automatically in the run sequence.

OB1 Cyclic program

OB40 Process interrupt 0

OB100 Restart (warm start)

Alternatively to OB40 the block can also be installed in another process interrupt

(OB41 to OB47).

Area of Application

The block is used to transfer time-stamped process signal changes and non-signal-

specific events (special messages) to the OS.

Functional description and Operating principle

In an AS the block forms the interface between an IM151-2 or IM153-2 and the OS

(WinCC). It reads the messages from the message buffers (max. of 20 messages

each) of an IM and uses the pseudo message function ALARM_T to transfer these

to the OSs.

• Process interrupt: The IM creates a process interrupt when there are new

messages. The status of the time stamp with the number of the record to be

fetched of the IM and the number of messages in the record are stored for

cyclic processing from the start information of the process interrupt OB (refer to

the process interrupt data). The information of up to 17 process interrupts can

be stored. If the maximum number is exceeded, the new information is lost.

• Cyclic processing: If messages are ready to be fetched, the respective record

(message buffer) is read by the SFC 59/RD_REC (read record). If several

records are to be fetched, the record with the oldest messages (oldest process

interrupt) is fetched. A maximum of 20 messages of a record (current number

of messages is listed in the process interrupt data) are saved temporarily in the

instance of the block

As soon as a record has been read, new messages can be entered again from

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-27

the IM. If all the records are occupied, the IM enters the special message

"Buffer overflow coming" into the message buffer. The special message "Buffer

overflow going" is entered as the first message into the first free record.

Messages which occur between the occurrence of a buffer overflow and the

enabling of a record are lost.

The slot no./channel no. of the stored messages are compared with the input

parameters of the block for the slot no./channel no. (S_C H_xxx). If they agree,

the message is assigned to the corresponding event ID (EV_ID_xxx) and

signal number (1 to 8) of the pseudo ALARM_T (ALARM_8P) block. The time

stamp of the message (8 bytes) is entered in the ARRAY of byte (index

corresponding to the signal number of the pseudo ALARM_T). When all the

messages have been assigned, the pseudo ALARM_T blocks which are to

transfer the new messages to OSs are called up. The return signals of the

pseudo ALARM_T and of the process control system message block

ALARM_8P (STAT_xx, M_ACK_xx) are available at the block output. If

STAT_xx = 11 (previous job not yet completed) the pseudo ALARM_T or

ALARM_8P is called again in the next cycle. In all other cases messages can

be lost. If no agreement can be found with the input parameters at a message,

the output QBPARF is set TRUE for one cycle (see error handling). The event

is signaled (see Message characteristics).

Addressing/Configuration

Also refer to Addressing

The logical address of the IM determined with HW Config (corresponds to the

diagnostic address) is entered at the block input (LADDR) of the driver. Each

change to the LADDR block input leads to a single check corresponding to the

start-up characteristics of the block. Saved process interrupt data are deleted.

If you run the DP master system in the DPV1 mode, you have to enter the E

address of the IM at the block input (LADDR).

The RACK into which the IM is plugged is monitored by the RACK block. You have

to connect the input RAC_DIAG with the output RAC_DIAG of the corresponding

RACK block. The rack number is set at the RACK block.

Process signals which are to be provided with a time stamp and are detected via

an IM must be configured correspondingly in the HW Config.

Each signal which is provided with a time stamp from the IM has a unique

assignment through its slot in combination with the corresponding channel number.

There are 128 inputs of data type WORD for 128 signals. The slot number of the

respective digital input module is entered in the higher-value byte and the channel

number (signal of the digital input module) in the lower-value byte. The slot and

signal number of the process signals are entered in the block inputs (S_CH_xxx)

(hexadecimal format).

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-28 A5E00127662-01

Example:

You have set the digital signal 10 of a digital input module plugged into slot 5 of an

ET200M to 10 ms exact time stamp by means of HW Config. You have to enter

the number 16#050A at the first free input S_CH_xxx of the IM_DRV.

Error handling

I/O access error:

QPERAF The block could not access IM. A record could not be read.

If it is not stored in the IM, these messages are lost.

Block processing error:

QERR An error has occurred while the bl ock was being processed.

Module configuration error:

QPARF Incorrect module configuration (incorrect logical basic address entered).

Configuration error:

QBPARF The block was configured incorrectly. The slot/channel number of an IM message

does not agree with any slot/channel number of the block input parameters

(message is lost).

Rack error:

QRACKF Failure of the rack in which the IM is plugged or a failure of IM

Start-up characteristics of the IM

When the IM is started up/restarted process interrupts are emitted again for those

records which were occupied before restarting but had not been fetched.

The special message "Begin start-up data" is entered as the first message into the

first free record. Then all the digital signals to be monitored are checked for

changes after the restart and a message is triggered, if appropriate. The special

message "End start-up data" is generated finally.

Start-up characteristics of the driver block IM_DRV

Initialization of the ALARM_8P and the pseudo ALARM_T blocks with the data

stored before the STOP state of the CPU. At a start-up the signal state is initialized

to "Zero".

At a start-up/initial start the driver checks whether there is an IM under the logical

address LADDR. Otherwise the driver sets its output QPARF = TRUE and does not

carry out any further I/O accesses in the subsequent cycles. Not until the right

module has been plugged or until after new configuration does QPARF = FALSE

and is the I/O access enabled. Stored process interrupt data which were not

processed before the restart are deleted.

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-29

Redundancy

In the case of H systems with two IM units redundancy exists with regard to the

time stamp if

• The communication between the two IM units runs via the communication bus,

• Updating of the active and passive IM has been completed free of errors

A redundancy loss (failure of an IM) is signaled outside the IM_DRV by means of

the SUBNET and RACK blocks.

The time stamp function is interrupted during a changeover between the active and

passive IM. The interruption period is displayed with the special message

"Changeover at redundancy beginning/end".

In a normal case the active informs the passive IM of the current I/O device state.

If this communication is faulty, the special message "Redundancy_Info_Loss

coming" is output. As soon as the I/O device state between the active and passive

IM has been compared, the special message "Redundancy_Info_Loss going" is

output.

Time response

Does not exist.

Message characteristics

The block uses one ALARM_8P and 17 pseudo ALARM_T blocks which are

installed as multiple instances. Transferring of the 8 time-stamp values per pseudo

ALARM_T call is carried out via an ARRAY [0..65] of BYTE. The ARRAY is

structured as follows:

BYTE 0 – 1: Format identifier of the following date/time stamp

BYTE 2 – 9: Date/time stamp for Signal_1

BYTE 10 – 17: Date/time stamp for Signal_2

BYTE 58 – 65: Date/time stamp for Signal_8

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-30 A5E00127662-01

The format identifier of the bytes 0 -1 specifies the bit coding of the time stamp

structure (8 bytes are assigned to one time stamp value):

Format identifier: 0 Date/time in SIMATIC S7 BCD format ( DATE_AND_TIME)

1 Date/time in ISP format

Year Month

Day hours

Minutes Seconds

1/10 s 1/100 s 1/1000 s Weekday

Time stamp in ISP format

Complete time by ISP method (time since 1.1.1900; 00:00 h). The 4 bytes for

seconds allows the time which has passed since 1.1.1900; 0:00 h to be expressed

in seconds.

BYTE 0 Seconds (4 Bytes)

4 Second fragments (4 Bytes)

The time stamps provided by IM were passed on unchanged by the driver in ISP

format.

In cyclic operation of the driver the pseudo ALARM_T blocks and the process

control system message block ALARM_8P are only called when the signal states

have changed. This reduces unnecessary runtimes.

Operator control and monitoring

The block does not have a faceplate (display block).

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-31

2.7.1 Connections of IM_DRV

The state of delivery of the block display in the CFC is marked in the "Connection"

column: Connection name bold = Connection displayed, normal = Not displayed.

Connection

(parameter) Meaning Data type Initial I/O

EV_ID Message ID for ALARM_8P DWORD 0 I

EV_ID_xx Message ID for ALARM_T_xx (xx = 00 – 16) DWORD 0 I

LADDR Logical Address IM WORD 0 I

M_ACK_xx Message acknowledge (xx = 00 – 16) x WORD 0 I

Q_ERR_xx Message failure (xx = 00 – 16) BOOL 0 O

QBPARF 1: Param. failure block BOOL 0 O

QERR 1: Block processing error (inverted value of ENO) BOOL 1 O

QPARF 1: Param. failure module BOOL 0 O

QPERAF 1: I/O access failure BOOL 0 O

QRACKF 1:Rack Failure BOOL 0 O

RAC_DIAG Rack Status Info rmation STRUCT I/O

S_CH_xxx Slot-/ch anne l-No.(xxx = 000 – 127) WORD 0 I

STAT_xx STATUS Output (xx = 00 – 16) WORD 0 O

2.7.2 Message texts and auxiliary process values of the IM_DRV

Assignment of message texts and message classes to the signal and special

messages

An ALARM_8P block is used for the process control system messages in the

following table. The geographic address of the IM is entered in Auxiliary Process

Value 1 = Slot number of the message, Auxiliary Process Value 2 = Channel

number of the message and Auxiliary Process Value 3 = RET_VAL of the SFC 59

(RD_REC) at an I/O access error.

ALARM_8P_16

Message No. Output

parameter Default message text Message class

1 QBPARF Error S_CHxx: Slot=@1%d@ Channel=@2%d@ S

2 QPERAF I/O access error: Ret_Val@3%d@ S

3 QPARF Parameter assignment error S

The following special messages which can be contained in the message buffer are

generated with ALARM_8P_00 (multiple-instanced call of the pseudo ALARM_T)

The format identifier and the 8 time-stamp values are entered in the first auxiliary

value

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-32 A5E00127662-01

ALARM_8P_00

Message No. Default message text Message

class

1 Start-up data BEGINNING/END S

2 Time-of-day message failure COMING/GOING S

3Time difference between message and internal clock endangers

precision S

4 Time difference between message and internal clock > 1 second

POSITIVE/NEGATIVE S

5 STOP of the functionality time stamp COMING/GOING S

6 Message loss at IM (buffer overflow) COMING/GOING S

7 Changeover at redundancy BEGINNING/END S

8 Redundancy_Info_Loss COMING/GOING S

ALARM_8P_01 to ALARM_8P_16 (multiple-instanced call of the pseudo

ALARM_T) can generate the following signal messages. The format identifier and

the 8 time-stamp values are entered in the first auxiliary value

ALARM_8P_01 Message No. Default message text Message clas s

1 TEXT S_CH_000 S

2 TEXT S_CH_001 S

3 TEXT S_CH_002 S

4 TEXT S_CH_003 S

5 TEXT S_CH_004 S

6 TEXT S_CH_005 S

7 TEXT S_CH_006 S

8 TEXT S_CH_007 S

......

ALARM_8P_16 Message No. Default message text Message clas s

1 TEXT S_CH_120 S

2 TEXT S_CH_121 S

3 TEXT S_CH_122 S

4 TEXT S_CH_123 S

5 TEXT S_CH_124 S

6 TEXT S_CH_125 S

7 TEXT S_CH_126 S

8 TEXT S_CH_127 S

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-33

2.7.3 Interface IM

The IM 153-2 / IM151-2 triggers a process interrupt when it wants to send

messages to the AS. The user data of the IM are specified in the start information

of the process interrupt as follows.

Hardware Interrupt Data

Element Data type Meaning

0 BYTE Event class and identifiers: B#16#11 = Interrupt is active

1 BYTE B#16#41 = Interrupt via interrupt line

B#16#42 = Interrupt via interrupt line 2 (only for S7-400)

B#16#43 = Interrupt via interrupt line 3 (only for S7-400)

B#16#44 = Interrupt via interrupt line 4 (only for S7-400)

2 BYTE Configured priority class: Default values: 16 (OB 40) to 23 (OB 47)

3 BYTE OB No. (40 to 47)

4 BYTE Reserved

5 BYTE Input module: B#16#54

Output module: B#16#55

6 WORD Logical basic address of the module which triggers the interrupt

7 BYTE State of the time stamp (interrupt cause from the view of the time stamp)t

Bit 7: State of the synchronization via time message

= 0: No synchronization exists

= 1: Synchronization exists

Bit 6: (only 1 ms) State of the synchronization via optical fiber synch ronization

signal

= 0: No optical fiber signal exists

= 1: Optical fiber signal exists

Bit 5: Renewed starting of the time stamp

= 0: No renewed starting

= 1: Renewed starting just started

Bit 4: REDUNDANCY: Redundancy operation active/not active

= 0: No redundant operation (no redundant plant or

single operating mode or passive IM not yet ready)

= 1: Redundant operation running (station in data

exchange between active <-> passive IM)

Bit 3: REDUNDANCY: active IM

= 0: Right-hand IM active,

= 1: Left-hand IM active

Bit 2 = 1: Buffer overflow "internal" (messages are lost)

Bit 1: = 1: Buffer overflow "external" (warning: message loss will occur soon)

Bit 0: = 1: Message buffer is ready for fetching on the IM

8 BYTE Record number if a record (message buffer) is to be fetched

9 BYTE Number of messages contained in the record n: 1 – 20

10 BYTE Reserved

11 DATE_AND

_TIME Date and time at which the OB was requested

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-34 A5E00127662-01

The IM_DRV only evaluates Bit 5 in Byte 7 (status of the time stamp function). If

the bit = 1, all the process interrupts which have been received before but not

processed are rejected.

The bit is only set by the IM in the first process alarm after renewed starting.

Examples for renewed starting:

* REDUNDANCY: Changeover state active <-> passive IM

* Restarting of the time stamp function after a total failure

Record (message buffer)

An IM153-2 has 15 records (message buffers). Access to a record is specified by

the record number supplied in the process interrupt data.

Structure of a record (message buf f er) in the IM

Date Number of bytes Remarks

Message1 12 Signal or special message

. .

Message20 12 Signal or special message

A maximum of 20 signal or special messages can be stored in a message buffer.

Structure of a special message from IM

Element Meaning Data type Remarks

1 Slot number of

the header

module

BYTE Fixed = 2

2 Identifier of the

special message BYTE 01h: Start-up data (a)

02h: Time message failure Subsequent signal messages may

have a precision worse than 10ms (b)

03h: Synchronization signal failure: Subsequent signal

messages may have a precision worse than 1ms (b)

04h: Time difference between message and internal clock > 1

second (d)

05h: STOP of the functionality time stamp (b)

06h: Buffer overflow: Subsequent signal messages are lost

until the buffer is free again (b)

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-35

Element Meaning Data type Remarks

3 Characteristic of

special message BYTE For further specification of the event

01h: BEGINNING 00h: END (a) or

01h: COMING 00h: GOING (b) (c) or

01h: POSITIVE 00h: NEGATIVE (d)

positive: Internal clock lost and was reset

negative: Internal clock gained and was reset:

4 Reserved BYTE Not used at present

5 Time of the

signal change ISP time

(8 BYTES) Complete time by ISP method (time since 1.1.1900; 00:00 h)

Structure of a signal message from IM

Element Meaning Data type Remarks

1 Slot number of the

module BYTE In connection with the channel number for address

referencing of the digital signal. Range of values:

0, 1, 2, 3 Not assigned

4 ... 11 Slot number of the DI module

12 ... 255 Not assi gned

2 Channel number

of the module BYTE In connection with the slot number for address referencing

of the digital signal. Range of values:

0, 1, ... 15 Channel number of the DI module

16 … 255 Not assigned

3 Signal state BYTE Bit 7 = 1: Signal coming

= 0: Signal going

Bit 6 ... Bit 0: Not used

4 Reserve BYTE Not used at present

5 Time of the signal

change ISP time

(8 BYTE) Complete time by ISP method (time since 1.1.1900; 00:00

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-36 A5E00127662-01

2.8 MOD_1: Diagnosti c driver for S7-300/400 SM modules

w hich cannot be diagnosed with 16 channel s

2.8.1 MOD_1: Monitoring of S7-300/400 SM modules which cannot be

diagnosed with 16 channels maximum

Object name (Type + Number)

FB 91

Area of Application

The block monitors S7-300/400 SM modules with 16 channels maximum which

cannot be diagnosed (no mixed modules).

Callin g OBs

The block has to be installed in the following OBs in the run sequence (is carried

out automatically in CFC):

OB1 Cyclic program

OB70 I/O redundancy error

OB72 CPU redundancy error

OB83 Withdrawn/plugged interrupt

OB85 Program execution error

OB86 Rack failure

OB100 Restart (warm start)

Use in the CFC

If the CFC function "Generate Module Driver" is used, the following steps are

carried out automatically:

• The MOD_1 block is installed behind the RACK block in the OBs mentioned

above of the respective runtime group of the rack (station).

• Configuration of

- The MODE_xx inputs (mode of the channels xx of the module).

- The logical basic address of the LADDR module.

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-37

• Interconnection of

- The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG

of the RACK block with the INOUT structures of the same name of the

MOD_1.

- The EN input with the output of an AND block.

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.

Function and Operating Principle

The block analyzes all the events which affect a module and its channels

acyclically. It forms the MODE and value status (quality code) for the signal

processing blocks channel-specifically. Events are signaled with ALARM_8P.

The block is enabled for running by the higher-level RACK block. The event to be

evaluated is entered in the start information (CPU_DIAG) of the OB_DIAG block.

Each signal channel of the module has an input (MODE_xx). Here the

configurations carried out with HW Config are signaled to the module channels.

MODE_xx is read into the low word of the output OMODE_xx. This is only carried

out during the start-up/initial start or if ACC_MODE = TRUE. The current value

status of the channel is entered in the highest-value byte. If good, OMODE_xx =

16#80xxxxxx is set.

The following events lead to a value status "invalid value due to higher-level error"

(OMODE_xx = 16#40xxxxxx):

• CPU redundancy loss (OB72) (if not switched,

output parameter QRACKF = TRUE)

• I/O access error (OB70) (if not switched,

output parameter QRACKF = TRUE)

• Rack failure (OB86) (output parameter QRACKF = TRUE)

The above events are evaluated by the RACK block. The following ones by the MOD

block:

• I/O access error (OB85) (output parameter QPERAF = TRUE)

• Module withdrawn (OB83) (output parameter QMODF = TRUE)

The events "Module withdrawn" and "I/O access error" are signaled to the OSs by

means of ALARM_8P. In the case of a diagnostic interrupt a difference is made

between module and channel faults, whereby a message number is assigned to

each channel.

During starting up the system checks whether the module is available (plugged).

The module state information read here is available in the form of service output

parameters (MOD_INF).

For detailed information on the faults: Please refer to the manual "System Software

for S7-300/400 – System and Standard Functions".

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-38 A5E00127662-01

Redundancy

Redundancy monitoring of the DP Master systems on an H system is carried out in

the higher-level RACK block.

MODE setti ng

The inputs MODE_xx are available for a maximum of 16 signal channels. The initial

value is "Zero" (no signal). Depending on the signal channel xx you have to set the

type and, if appropriate, the coding of the measuring range of an analog module at

the MODE_xx input.

Refer to MODE

Note

If you change the configuration of the MODE_xx inputs during operation, the

change does not become active until the input ACC_MODE = 1 has been set at

the outputs.

OMODE structure

Refer to OMODE

Addressing

Refer to Addressing

In the case of HART modules which access the process image in reading and

writing mode configuration is carried out as for input modules. It is generally not

permissible to specify different input and output ranges.

Example: SM332 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

No plausibility checks are carried out with reference to the input parameters.

Also refer to: Error information of the output MSG_STAT parameter

Service information

In order to analyze faults you can read the module state information, which is

entered during starting up, via the structured output parameter MOD_INF (refer to

the reference manual "System software for S7-300/400 – System and standard

functions", system state list, module state information).

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-39

Start-up characteristics

After a restart or an initial start the system checks whether the module is available

under the logical base address. A restart (OB100) is signaled via the LSB in Byte 2

of the outputs OMODE_xx.

Time response

Does not exist.

Message characteristics

MOD_1 signals module faults by means of ALARM_8P. The inputs DELAY1 and

DELAY2 are used to delay signaling of the I/O access error. DELAY1 is used to

specify the time in seconds which the block waits after an I/O access error (OB85)

for a higher-level error (rack failure or withdrawn/plugged), before it outputs the

message. The message is turned off only when no higher-level fault is detected

after the set time expires. DELAY2 determines the number of seconds which the

block waits until it signals the I/O access error still existing after a higher-level error

has passed. Both values have a default value of 2 seconds.

Messaging can be de-activated by using EN_MSG = FALSE.

Operator control and monitoring

The block does not have a faceplate (Display block).

Note: Under "Connections of …" the variables are marked (column OC&M "+")

which are transferred to the OS, if the option "Can be operator controlled and

monitored" is set in the object properties of the block in CFC. Default: Option not

set.

2.8.2 Connections of MOD_1 / MOD_2

The connections of the blocks MOD_1and MOD_2 are identical with the exception

of the number of the MODE_xx and OMODE_xx. The number of channels to be

monitored determines the number of the respective input and outputs (xx).

The state of delivery of the block display in the CFC is marked in the "Connection"

column: Connection name bold = Connection displayed, normal = Not displayed.

Connection

(parameter) Meaning Data type Initial I/O OC&M

ACC_MODE 1=Accept MODE Settings BOOL 0 I/O

CPU_DIAG System Structure STRUCT I/O

DELAY1 Alarm Delay 1 (s) INT 2 I

DELAY2 Alarm Delay 2 (s) INT 2 I

EN_MSG 1=Enable Message BOOL 1 I

EV_ID Message ID DWORD 0 I

LADDR Logical Address of Module INT 0 I

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-40 A5E00127662-01

Connection

(parameter) Meaning Data type Initial I/O OC&M

MOD_INF System Structure:Module Information STRUCT O

MODE_xx Mode Channel xx WORD 0 I

MSG_ACK Message Acknowledged WORD 0 O

MSGSTAT Message Failure WORD 0 O

OMODE_xx Mode Channel xx DWORD 0 O +

QERR 1=Program Error BOOL O

QMODF 1=Module Withdrawn/Out of Order BOOL 0 O +

QPERAF 1=Module I/O Access Failure BOOL 0 O

QRACKF 1=Rack/Station Fai lure BOOL 0 O

RAC_DIAG Rack diagnostics (System Structure) STRUCT I/O

RACK_NO Rack Number BYTE 0 I

SLOT_NO Slot Number BYTE 0 I

SUBN_TYP 1=External DP interface BOOL 0 I

SUBN1_ID ID of Primary DP master system BYTE 255 I

SUBN2_ID ID of Redundant DP master syst em BY TE 255 I

2.8.3 Message texts and auxiliary process values of MOD_1 / MOD_2

Assignment of message texts and cl asses to the block parameters of MOD_1 /

MOD_2

Message

block

ALARM_8P

Message

number Block

parameter Default message text Message

class

EV_ID 1 Module @1%d@/@2%d@/@3%d@: Withdrawn S

2 QPERAF Module @1%d@/@2%d@/@3%d@: Access

error S

3 QMODF Module @1%d@/@2%d@/@3%d@:

@4W%t#MOD_n_TXT@ (n = 1 or 2) S

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

A5E00127662-01 2-41

Assignment of the auxiliary process values for the block parameters of MOD_1 /

MOD_2

Message block

ALARM_8P Auxiliary

process

value

Block parameter Meaning

EV_ID 1 MOD_INF.SUBN_ID Number DP Master system ( byte)

2 MOD_INF.RACK_NO Rack / Station number (byte)

3 MOD_INF.SLOT_NO Slot number (byte)

4 Text number from MOD_n_TXT (n =1or 2)

(Message 1)

The event class/event number, the corresponding message texts and their text

numbers of the text library MOD_n_TXT are listed in the text library for signal

modules

2.9 MOD_2: Diagnosti c driver for S7-300/400 SM modules

w hich cannot be diagnosed with 32 channel s

2.9.1 MOD_2: Monitoring of S7-300/400 SM modules which cannot be

diagnosed with 32 channels

Object name (Type + Number)

FB 92

Area of Application

The block monitors S7-300/400 SM modules with 32 channels maximum which

cannot be diagnosed (no mixed modules).

09.10.2001

Signal blocks and diagnostic drivers

Process Cont rol System PCS 7, Driver Block s

2-42 A5E00127662-01

Callin g OBs

The block has to be installed in the following OBs in the run sequence (is carried

out automatically in CFC):

OB1 Cyclic program

OB70 I/O redundancy error

OB72 CPU redundancy error

OB83 Withdrawn/plugged interrupt

OB85 Program execution error

OB86 Rack failure

OB100 Restart (warm start)

Use in the CFC

If the CFC function "Generate Module Driver" is used, the following steps are

carried out automatically:

• The MOD_2 block is installed behind the RACK block in the OBs mentioned

above of the respective runtime group of the rack (station).

• Configuration of

- The MODE_xx inputs (mode of the channels xx of the module)

- The logical basic address of the LADDR module.

• Interconnection of

- The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG

of the RACK block with the INOUT structures of the same name of the

MOD_2.