Read Messages text version

Preface, Content General System messages

1 2 3 4 5 6

SIMATIC Automation system BRAUMAT/SISTARClassic V5.3 Messages

Manual

User messages On-screen message functions Messages with WinCC What to do on errors?

This manual is part of the documentation package with the order number: 6FD7680-0PH03

Edition 11/2007

A5E00239391-04

Safety Guidelines

This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring to property damage only have no safety alert symbol. The notices shown below are graded according to the degree of danger.

! ! !

Danger

indicates that death or severe personal injury will result if proper precautions are not taken.

Warning

indicates that death or severe personal injury may result if proper precautions are not taken.

Caution

with a safety alert symbol indicates that minor personal injury can result if proper precautions are not taken.

Caution

without a safety alert symbol indicates that property damage can result if proper precautions are not taken.

Attention

indicates that an unintended result or situation can occur if the corresponding notice is not taken into account. If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage.

Qualified Personnel

The device/system may only be set up and used in conjunction with this documentation. Commissioning and operation of a device/system may only be performed by qualified personnel. Within the context of the safety notices in this documentation qualified persons are defined as persons who are authorized to commission, ground and label devices, systems and circuits in accordance with established safety practices and standards.

Prescribed Usage

Note the following:

!

Warning

This device and its components may only be used for the applications described in the catalog or the technical description, and only in connection with devices or components from other manufacturers which have been approved or recommended by Siemens. Correct, reliable operation of the product requires proper transport, storage, positioning and assembly as well as careful operation and maintenance.

Trademarks

All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.

Copyright Siemens AG 2007 All rights reserved

The distribution and duplication of this document or the utilization and transmission of its contents are not permitted without express written permission. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved

Disclaimer of Liability

We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions.

Siemens AG

Automation and Drives Postfach 4848, D- 90327 Nuernberg, Germany

©Siemens AG 2007 Technical data subject to change.

Siemens Aktiengesellschaft

A5E00239391-04

Preface

Purpose of the Manual

This manual describes the message system with BRAUMAT/SISTAR Classic 5.3 and it gives you an overview of the following topics: Philosophy of Message System messages User Messages Viewing messages Messaging with WinCC This manual is intended for those responsible for configuring, commissioning and servicing automation systems.

Required Basic Knowledge

You require a general knowledge in the field of automation engineering to be able to understand this manual. In addition, you should know how to use computers or devices with similar functions (e.g programming devices) under Windows 2000 Prof./Windows 2000 Server or Windows XP Prof./Windows Server 2003 operating systems. Since BRAUMAT/SISTAR Classic V5.3 is based on the STEP 7 software, you should also know how to operate it. This is provided in the manual "Programming with STEP 7 V5.3". Please read always the file "readme.wri" to the current version of BRAUMAT/SISTARClassic before an installation of BRAUMAT/SISTARClassic components.

Where is this Manual valid?

This manual is valid for the software package BRAUMAT/SISTARClassic

from Version V5.3 SP2.

The offered electronic manual is most largely identical with the contents of the on-line help. Due to a technically necessary editorial deadline for the generation of electronic manuals occasionally smaller deviations can give up opposite the on-line helps. The statements in the on-line helps are primary to those of the manual.

Place of this Documentation in the Information Environment

This manual forms part of the BRAUMAT/SISTAR Classic V5.3 documentation package. The following schematic of the document architecture show the individual manuals as well as their thematic grouping within the entire program package

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

iii

Document structure

Description of the System

Installation and Configuration

Administration

Communication

Engineering 'based on S7' EPE-creation

Recipe System

Batchprocessing Dosing and Weigher Serve & Watch 'based on S7'

Operation & Control batches

Batch curves

Application for 'based on S7'

Logging

Messages

Building block library : Basics

Building block library: Route Control Serve & Watch Routes

Building block description S7

Building block description S5

Engineering of the Route Control

iv

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

Further Support If you have any technical questions, please get in touch with your Siemens representative or agent responsible. You will find your contact person at: http://www.siemens.com/automation/partner You will find a guide to the technical documentation offered for the individual SIMATIC Products and Systems here at: http://www.siemens.com/simatic-tech-doku-portal The online catalog and order system is found under: http://mall.automation.siemens.com/

Training Centers Siemens offers a number of training courses to familiarize you with the SIMATIC S7 automation system. Please contact your regional training center or our central training center in D 90327 Nuremberg, Germany for details: Telephone: +49 (911) 895-3200.

Internet: http://www.sitrain.com

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

v

Technical Support

You can reach the Technical Support for all A&D products · · · Via the Web formula for the Support Request http://www.siemens.com/automation/support-request Phone: Fax: + 49 180 5050 222 + 49 180 5050 223

Additional information about our Technical Support can be found on the Internet pages http://www.siemens.com/automation/service

Service & Support on the Internet In addition to our documentation, we offer our Know-how online on the internet at: http://www.siemens.com/automation/service&support where you will find the following: · · · · · The newsletter, which constantly provides you with up-to-date information on your products. The right documents via our Search function in Service & Support. A forum, where users and experts from all over the world exchange their experiences. Your local representative for Automation & Drives. Information on field service, repairs, spare parts and more under "Services".

vi

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

Content

1 General 1.1 1.2 1.3 1.4 1-1 Overview .................................................................................................1-1 Principle with ,based on S7' ....................................................................1-3 Principle for use in WinCC ......................................................................1-5 Types, categories and classes................................................................1-6 1.4.1 File MsgClass.ini ........................................................................1-7 1.4.2 Message classes and sequence overview .................................1-8 Message structure ..................................................................................1-8 Structure of the message definition files.................................................1-9 ICM allocation .......................................................................................1-11 1.7.1 Allocation to the unit .................................................................1-11 1.7.2 Allocation to a group.................................................................1-13 Lock messages .....................................................................................1-14 2-1 Overview .................................................................................................2-1 Messages of the block 'SEQU'................................................................2-1 Messages of the block ICM.....................................................................2-2 Message of the block 'AIN'......................................................................2-2 Messages of the block 'PID'....................................................................2-2 Messages of the block 'ThreStep' ...........................................................2-3 Message of the block 'SEQS'..................................................................2-3 Messages of the block 'DFMx' ................................................................2-3 Further system messages.......................................................................2-4 3-1 Overview .................................................................................................3-1 Initiation via the MSG-block ....................................................................3-1 Initiation via FC713 .................................................................................3-2 4-1 Overview .................................................................................................4-1 PCU server as message window ............................................................4-1 Message archive.....................................................................................4-2 Message faceplates ................................................................................4-2 4.4.1 Loop-In-Alarm .............................................................................4-2 4.4.2 Configuring the image attribute ..................................................4-2 5-1 Overview .................................................................................................5-1 5.1.1 Assignment of Braumat Messages to WinCC Alarm Message Class and Message Type .......................................................................5-1 WinCC channel Configuration.................................................................5-3 5.2.1 Configuration file "SistarNLL.ini".................................................5-3 5.2.2 Configuration file ,,MELD_WINCC.DEF"....................................5-4 Working with SIMATIC-WinCC ...............................................................5-6 5.3.1 Configuration steps in WinCC Alarm logging .............................5-7 5.3.2 Configure Process Images .........................................................5-9 Example - Message window .................................................................5-12 6-1

vii

1.5 1.6 1.7

1.8 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3 3.1 3.2 3.3 4 4.1 4.2 4.3 4.4

System messages

User messages

On-screen message functions

5

Messages with WinCC 5.1

5.2

5.3

5.4 6

What to do on errors?

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

6.1

Problems ................................................................................................ 6-1

viii

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

General

1 General

1.1 Overview

In the BRAUMAT/SISTAR Classic 5.3 system, you nedd to configure only the user messages. This is not required for messages of technological blocks, of the recipe sytem and of the route control. When specific operational errors or disturbances occur, the automation system generates correponding error messages and outputs them via the FIFO buffer to the IOSes. When the SCADA system WinCC is integrated in BRAUMAT/SISTAR Classic 5.3 operation, messages are recorded in the WinCC message system and visualized with WinCC. The basics on WinCC are found in the corresponding documentation. The messages are sent via FIFOs to the IOSes, the message type 3 is configured in their See also: Blocks S7 FIFO1 to FIFO6 - PCU-System datas - General). FIFO ( Therefore it is possible to send the messages only to the IOSes which require them. By removing the message type 3 in FIFO all messages for this IOS are blocked. The IOS which receives the messages the messages are filed in the message archive. The message archives can be processed in the application 'Message archive'. There is the possibility to select and print the messages according to specific criterias. If the PCU-server window is opened at the IOS and the view ,Messages' is selected, the last current message will be output at the bottom of the window. See also: Message functions at the screen

There are three types of messages:

PCU system messages IOS messages User messages PCU system messages are created by a PCU, the message text is based on the files 'Systexte.txt', 'Melddef.txt' and `Melddef3.txt' located in the folder '...\windcs\texte.x\' of the IOS. These files are preset by the system and needn't to be changed. The PCU creates system status messages and system fault messages. A system status message is e.g. a step selection for a unit or the switchover of a controller. A system fault message is e.g. the exceeding of the monitoring time of an unit or an individual control element. IOS messages are created by the system on the IOS, the text is preconfigured. User messages are created on demand (user triggers initial flag). The texts of the user messages are parametrizable. Status messages, fault messages, errors (faults) and control messages are distinguished between.

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04 1-1

General

The texts for the incoming and going message are configured in the application 'text parameterization' and are related to that PCU, in which the messages are created (files 'Meldkom.txt' and 'Meldgeh.txt', folder 'windcs\PCU.xxx\Texte'). The indication if the message is supposed to be output as status message, fault message, error or control message is configured at the function block MELD. See also: Blocks S7 MELD - Message block (MELD1 and MELD2)

1-2

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

General

1.2 Principle with ,based on S7'

Application message archive

message faceplate

PCU-Server

Telegram Type3

Engineering (text files) message structure (meld.def)

PCU1

PCU...

message types (melddef.txt)

message archive

Details PCU Techn. blocks FIFO Server1

FIFO Server2

Adding batches and sequencer assignment

Seq.-control FC 716 RCScontrol

Sequencer data viewing the message buffers

user messages

overviewS7.vsd

The raw data of messages are created by the technological blocks, by the sequencer control or by the route control in the PCU. The raw data are sent via a message of type 3 from the PCU to the IOS. The message type 3 need to be configured in the FIFO-head data. Besides of the PCU-messages raw data messages are also created from the recipe and route control in BRAUMAT/SISTAR Classic 5.3. These messages also create messages, they are also of the message type 3.

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04 1-3

read

S5channel

S7channel

RecipeServer

RCSServer

prot_003

General

These messages are handled by a IOS function within the prot_003.dll, which creates the real, readable message based on this raw data. The files meld.def and melddef.txt are necessary and are used for that.

Visualization

The visualization is possible via: Message view of the PCU server window Application 'Message archive' Message faceplate in process images Message faceplate in the unit overview

Reference/assignment of messages

In this type all messages are related to a batch as well as to a unit.

The batch relation consists of:

Batch year Recipe category of the batch Job number of the batch Batch number

Standard unit reference

All reporting blocks can be assigned to a unit. Based on this assignment, the batch reference is retrieved at the time a message is created. The unit reference is part of the message.

Unit reference with RCS

A route can be assigned to a unit whereby all messages of RCS are assigned to this unit. The PCU number of the reporting object and the PCU number of the unit which controls a route can be different.

1-4

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

General

1.3 Principle for use in WinCC

message archive

Tag Logging

message system

engineering message handling

Norm DLL

message view in PCU-Server

Raw variable

BRAUMAT/ SISTAR channel

WinCC Data manager

PCU-Server

S5channel

S7channel

recipeServer

RCSServer

prot_003

Telegram Type3

Logging (text files) messsage archive

message structure (meld.def) PCU1 PCU...

message types (melddef.txt)

Details PCU Techn. blocks FIFO Server1

FIFO Server2

Adding batches and sequencer assignment

Seq.-control FC 716 RCScontrol

sequenzer data viewing the message buffers

user messages

overviewPCS7.vsd

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

1-5

General

Messages of the recipe system and route controls are generated as in type "based on S7" and are also passed to the WinCC channel of BRAUMAT/SISTAR. Messages are written to the WinCC message archive by means of the raw data variable and standardization DLL.

Reference / assignment of messages

In this type all messages are recorded related to a batch.

The batch reference consists of:

Batch-ID Batchname The configuration and operation of that use case ist further described in chapter Messages with WinCC of this manual.

1.4 Types, categories and classes

The organization in types, categories and classes are only available in the ,based on S7' system use case.

message class

msgclass.ini

message category

message type

melddef.txt

msgclass.vsd

Message classes

A message class can consist of several message groups. Available message classes are E - errors, W - warnings, M - process messages, O - operator request.

The following table shows the descriptors as well as the allocation of message classes and assigned message types

Msg class

E (F) *) W M O

Description

Error / failure Warnings Process Messages Operation Request - no class assigned -

Msg type

F S W M B O P

Description

User fault message System fault message Warning User status message Operation message Operating Request IOS-Message BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

1-6

General

*) F = Displayed-Shortcut at language 10 (=English S88) This assignments as well as the following settings are defined in the system configuration file `...\windcs\sys\MsgClass.ini': Displayed shortcut character Assigned message types Flashing behaviour Reset behaviour Deletion behaviour Each message is assigned a message type. The message type is displayed as the first character next to the time field in the message row. The whole number of messages and their configuration is distinguished as follows:

System message types

BRAUMAT/SISTAR Classic 5.3 knows 2 times 64 message types. The standard system messages of the technological blocks, the recipe control and the route control are created via the following definition files: Message types 1 ­ 64 by means of `...windcs\texte.x\MELDDEF.TXT' Message types 129 ­ 192 by means of `...windcs\texte.x\MELDDEF3.TXT'

User message types

Additionally there are 64 message types for the user. These messages need to be triggered via the block FC713. Message types 65 ­ 128 by means of `...\windcs\texte.x\MELDUSR.TXT' For every user message type the structure of the message can be configured. See also: User messages

1.4.1 File MsgClass.ini

For every message class an section exists in the file MsgClass.ini where the following settings are defined: SignalChar= describes the sign that will be displayed in the plant overview with the defined message type. SignalChar10= describes the sign that is displayed in the plant overview with the defined message type. Insert this line only if the output is language-dependent. If this line is entered this will be taken instead of the signs defined in the SignalChar-line. The number after the SignalChar describes the language. Displayed= describes the allocation of a message type of this message class. Several message types are registered by commas separately. Flushing= describes that of the assigned message types flushing is supposed to be indicated.

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04 1-7

General

Reset= describes which of the assigned message types are supposed to be reset by activating the corresponding button in the plant overview. Deleted= describes which message text of the assigned message type is deleted from the plant overview by resetting.

1.4.2 Message classes and sequence overview

The acknowledgement of the individual unit-related messages maybe done in the sequence control application or via the `SmartUnit' control within process pictures.

Delete the buffer for message class ,Fault/Error''

Delete the buffer for the message class ,Warning'

Delete the buffer for message class ,Process message'

1.5 Message structure

The structural message layout is defined by the system file `...\windcs\texte.x\Meld.def'. All messages are structured from the left to the right from the following components:

Column

Time: Type: Recipetype: Order: Batch: UnPCU: Unit: UnName: PCU-No: Module: No: Name: Text:

Format

Char 8 Char 1 Char 16 Char 6 Char 6 Char 3 Char 3 Char 16 Char 3 Char 8 Char 4 Char 16 Char 48

Contents

hh:mm:ss = hour, minute, second. Shortcut of message type (see above) Name of the recipe type for which the message had been transmitted (e.g. product, CIP ...). Job number for which the message had been transmitted. Batch number for which the message had been transmitted. PCU-number of the unit to which the message is assigned. Unit (Number) to which the message is assigned. Unit name. PCU-number of the reporting object Name of the block which deposited the message (e.g. Unit, ICM ...) Record number (1 ... 255) Configured name of the data record (16 characters) General message name free configurable text (48 characters) for incoming and outgoing message in case of user messages unique number of the message within the object that generates the message (message object = PCU, module and instance number) State of the message (coming or going) Message class that are used when the message is transmit to WinCC BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

MsgID: Status: MsgClass: 1-8

Char 5 Char 2 Char 2

General

BatchYear: Text_WinCC: RT-Nr.:

Char 2 Char 48 Char 6

Year when batch is created Possible text for the WinCC message Recipe category number

As mentioned earlier, we distinguish between system messages and user-configurable messages. The system messages are generated from system blocks as ICM, PID controller, TA etc. The user messages are generated by the FC713. This FC block is called in a equipment operatoin (EOP) or a FB and supplied with corresponding parameters. Output of the messages in the format describe earlier is based on the message definition files in "windcs\texte.x". In these files, the various message types (depending on the module, e.g. ICM, controller, TA etc.) are assigned message definitions. For user messages, an ID of the message definition must be passed to the FC blocks.

Note:

User messages, which are created by means of the system block MELD have a fixed layout defined already by the system. Only the text fields for the incoming and outgoing message are to be configured (see chapter `Initiation via the ').

1.6 Structure of the message definition files

Assignment of the message definition files to the message types

Melddef.txt Melddef3.txt Meldusr.txt System messages 1 - 64 System messages 129 - 192 User messages 65 - 128

General structure of the definition files for the message types

Each message type occupies two lines in the file and is numbered continuously. The first and second line in file "meldusr.txt" determins message type 65 (= first user message), for example, the next two lines determine message type 66, and so forth. The character or start-position of each textfield must match exactly the message-definition as described in the previous chapter, but without the first time field, as this is created automaticly by the system.

Structure of the odd lines

The odd lines may consist of fixed text or placeholders. The column position in within the line determines the text or placeholder position. The placeholders are numbered continuously, and each one requires a definition in the next line. Example:

Column Odd line:

123456789012345678901234567890 F @ @ abc

The message type character is permanently written to column position 1 (`F' for example), and the text "abc" beginning at column position 21. The text of the first placeholder is written starting at column position 3, and for the second at column position 15. Placeholder and following space characters determines and delimits the stringlength of the substituted parameters. Column seperating spaces have to be considered here too.

Structure of the even lines

The even lines contains the definitions for the placeholders of the previous odd line.

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04 1-9

General

Structure:

Column

1 2 3 4 5

Character

/ + or Q or space S or space /

Meaning

Initial character Incoming or outpgoing message Message with compulsory acknowledgement Error message End character placeholder definitions for substitution, in the same sequence as in the odd lines.

6 ... and following ...

Definition of placeholders

The definition describes the conversion of raw data (structure of datagram type 3) in in a text. Syntax: <address type><addresse><data type><length><text file>

<address type> DW = data word DR = right data word DL. = left data word <address> <Data type> represents the DW number in the datagram. I = Integer number S, T = global text substitution (following textfile see below) t = PCU-specific text substitution. The PCU-specific text substitution always refers to the object from which the essage originates (datagram origin). If this is not so, which is possible with RCS messages, the PCU name appended to the file name can be defined in more detai, i.e. the address must be configured in the datagram that contains the PCU number. f.e. DW11t16SEQUENCE(PCU=DL12) <length> <file name> length of the value or text written to the message line. The file name must be defined without *.txt extension. Depending on the data type the following folders are valid: `t' `T' `S' `...\windcs\PCU.nnn\texte' `...\windcs\texte.x' `...\windcs\sys\msg'

Example: Definition of a Systemmessage

Line 1: [email protected]@[email protected]@[email protected]@[email protected] [email protected].... [email protected].... [email protected] Line 2: /SQ/DR4T16RTYP DW6I6 DW7I6 DR0I3 DW11I3 DW11t16SEQUENCE DR0I3 DW9I4 DW9t16ESG1 DL4I2 DR4I6 Erleuterungen der Platzhalter:

1-10

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

General

What is defined here is a fault message ­ with acknowledging, with text `ICM1monitoring time fault start' DW4T16RTYP The value is read from DW4 of the datagram and is then interpreted as index. The indexed text line of the shared text file "rtyp.txt" substitutes the first @ placeholder. The text has a length of 16 characters with one separating Blank to the next @ placeholder. DR0I3 From DW 0 (LSB), the value is entered with a length of three characters. DW11t16SEQUENCE The value is read from DW11 of the the datagram and is used as index into the PCU-specific text file"teilanl.txt". The textline replaces the @ placeholder with a length of 16 characters.

Structure of the datagram type 3 DW

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 3 Year Day Minute Recipe type nummer Recipe number Order number Batch number Message type Message number Depends on the message type (usually a system message text number) Depends on the message type (usually an assigned unit) Depends on the message type Depends on the message type Depends on the message type Depends on the message type

DL

PCU number Month Hour Second

DR

1.7 ICM allocation

Every ICM has been assigned in a specific unit. See also: Blocks S7 ICM With an error of this ICM one message is created in which the recipe type, the job number and the batch number of the assigned unit will be entered. In order to retrace which unit was concerned by the ICM-error by an evaluation of the message archive later. This is an important condition in order to guarantee the safety of the product.

1.7.1 Allocation to the unit

If ICMs are used by different units to different times the configured and assigned unitnumber should be changed according to the unit that uses the ICM.

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04 1-11

General

Only then the recipe type, the job number and the batch number will be entered in the message with an ICM error that also shows an error. The user can change the configured and assigned unit-number in the user program. Two functions are provided: All ICMs of one manual group are assigned to a specific unit: This is e.g. the case if two CIP-units are available and both use the same ICMs. In this way it will be guaranteed that the correct recipe type, the right job- and batch number will be entered and for the ICMs of the manual group depending on which unit is just active it is considered that the assigned unit-number should be rewritten. An ICM is assigned to a specific unit: If individual ICMs are used by different units to different times the configured and assigned unit-number should be changed according to the unit that uses the ICM. For the implementation of the function 1 the block FC723 is provided for the user for the SIMATIC S7. The function 2 works without a function block for the SIMATIC S7 since it can be taken access on all parameter of the data record by the opening the data blocks as well as the UDTs slight symbolically.

Function FC723:

By calling the function FC723 two parameter are to be transferred. Formal operands of the FC723:

FC723

ITA IHGrp := := Unit-number Manual group

Example: Call of the FC723 for the function 1:

All ICMs of the manual group 4 are supposed to be assigned to the unit 7 in the EOP 31.

Call of the FC723 in the FC1031: FC1031

UN SPB CALL ITA IHGrp NEXT: M 102.2 NEXT FC 723 :=7 :=4 EOP Start Jump Call of the FC 723 'GRP_TA_FC' Unit number 7 Manual group 4

Example: Implementation of the function 2 by a symbolic access on the parameter 'byTA' of the ICMs

The ICM no. 125 of the ICM group 1 should be assigned to the unit 13 in the EOP 15.

Writing parameters 'byTA' of the ICM 5 in the FC 1015 on TA=13 FC 1015

UN SPB 1-12 M 102.2 NEXT EOP Start Jump BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

General

L T

13 "ICM".au[125].byTA

Unit-number 13 Access on DB "ICM1" (DB 726) on the field (array) of the 125th ICMs on the parameter byTA (from ICM UDT)

NEXT:

Example: Implementation of the function 2 but for 100 ICMs in a loop with the use of the FC 500 'ATTRIB_PTR_FC'

The ICM No. 100 to 200 of the ICM group 1 should be assigned in the unit 44 in the GOP15. The FC 500 'ATTRIB_PTR_FC' calculates the pointer on a data record attribute and this one will be transferred in the AR1 register.

Parameter byTA the ICMs 100 to 200 in the FC1015 on TA=44 write FC1015

UN SPB ONTO L T NEXT: CALL IDB Irecord IRelByteOffset IRetVal L T L + T L <=I SPB NTZ: NEXT 44 DBB[AR1,P#0.0] #iESGNR 1 #iESGNR 200 Processing ICMs in 200 As long as there aren't all processed Process next ICM no. M 102.2 NTZ "ICM1" 100 #iESGNR FC500 :=726 :=#iESGNR :=5 :=iRETVAL EOP Start Jump Looking up "ICM1" (DB726) From ICM 100 Presetting variables Call FC500 DB 726 Current ICM no. ByTA is the 5.Byte in the UDT Value = 0 => no error Unit-number 44 Writing value on byTA ICM no. Increment

1.7.2 Allocation to a group

The unit allocation in the blocks can also be used for the allocation to a group. All allocations are possible for PCU-crossed units. The current recipe type, the current recipe number, the job number and the batch number of the assigned unit are transferred via the cross coupling. In order to switch the unit allocation to a group the allocation number should be more than 100. The group number results from the allocation number minus 100. The user should consider that there are the current data of recipe type, recipe number, job number and batch number in this block 'GRP_TA'. Only then it is guaranteed that a fault signal can be assigned correctly later. See also:

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

Blocks S7

GRUP_TA - Group block

1-13

General

Group block 'GRUP_TA' DB723 Setup of the data block DB723

DBW4 DBW8 From DBW20 DBB20 DBB21 DBW22 DBW24 DBW26 From DBW28 Extend 8 bytes per data record Number of the data records 1.data record Year for Rtyp, JobNo, BatchNo Recipe type Recipe number Job number Batch number 2. Data record

Unit allocation Unit assignment

0 1-100 101-255

Function

No unit ­ allocation Unit-number 1...64 Allocation to a group Groupid = Unit-allocation ­100

1.8 Lock messages

In addition there is still the possibility to lock the messages via the module 'BLOCK'. The messages of the type B, M, S, F can lock separately See also: Blocks S7 LOCK - PCU message block

1-14

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

System messages

2 System messages

2.1 Overview

The following system messages are transmitted by the individual BRAUMAT/SISTAR Classic 5.3 blocks. You will find more detailed information about the message structure or to the message types in the corresponding chapters. In addition you will find more detailed information about the meaning of the description for the individual blocks (see chapter 'block'). See also: S7 blocks / S5 blocks

2.2 Messages of the block 'SEQU'

SEQU Abort: if the unit is set to step 0.

12:05:23 Production B 00122 03421 002 SEQU 007 LB1 unit message abort

SEQU step selection: if a step is selected manually.

12:07:15 Production B 00122 03421 002 SEQU 007 LB1 unit message step selection

SEQU error TUET-time: if the monitoring time ran out and the control bit FTUE (M101.7) is set (see block 'SEQU'). See also: Blocks S7 SEQU - Plant section

12:09:28 S Production 00122 03421 002 SEQU 007 LB1 error monitoring time beginning

SEQU sequence Stop / sequence enabled: by changing Enabled/Stop by the user

12:10:03 Production B 00122 03421 002 SEQU 007 LB1 unit message sequence stop 12:10:47 Production B 00122 03421 002 SEQU 007 LB1 unit message sequence enabled

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

2-1

System messages

SEQU Manual operation ON/OFF: Setting/resetting the flag bit for the assigned manual group

12:11:10 Production B 00122 03421 002 SEQU 007 LB1 unit message Manual mode on 12:11:15 Production B 00122 03421 002 SEQU 007 LB1 unit message Auto mode on

SEQU continuous conditions OFF: if no unit conditions are queued (change ON OFF).

12:05:05 Production B 00122 03421 002 SEQU 007 unit message LB1: continuous condition On

Configuration error SEQU: if a false DFM type is configured. See also: Blocks S7 DFM Parameterization

12:05:23 Production B 00122 03421 002 SEQU 007 LB1 unit message Parameterization error

2.3 Messages of the block ICM

ICM-error: if the error memory QSP is set. This message is a fault message

12:15:23 S Production 00122 03420 002 ICM1 003 ICM1 monitoring time V312 error. Beginning 12:18:27 S Production 00122 03423 002 ICM2 014 ICM2 monitoring time W157 error. Beginning

2.4 Message of the block 'AIN'

AIN-error: if from the analog module the variable error bit is set, and the inhibit bit isn't set in the AIN-data record (Fault message)

12:18:43 S Production 00122 03421 002 AIN 012 measured value monitoring TempWK1 error. Beginning

AIN-Limit violation: if the determined values for upper-, or lower limit are exceeded or fallen below and the enabling bit for error upper- or lower limit will be set in the AIN -data record respectively.

12:18:43 S Production 00122 03421 002 AIN 012 TempWK1 upper limit measured value monitoring exceeded 12:18:43 S Production 00122 03421 002 AIN 012 TempWK1 low limit measured value monitoring fell

2.5 Messages of the block 'PID'

Manual operation PID ON/OFF: by switching over from manual to automatic and vice versa (Status message)

12:21:18 production B 00122 03421 002 PID 017 controller operating mode WK:Temp manual on 12:21:55 production B 00122 03421 002 PID 017 WK:Temp automatics controller operating mode on 2-2 BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

System messages

Internal operation PID ON/OFF: by switching over from external to internal and reverse (Status message)

12:22:15 Production B 00122 03421 002 PID 017 WK:Temp controller operating mode Internal 12:23:01 Production B 00122 03421 002 PID 017 WK:Temp controller operating mode External

2.6 Messages of the block 'ThreStep'

ThreStep manual operation ON/OFF: by switching over from manual to automatic and reverse (Status message).

12:34:22 Production B 00122 03421 002 ThreStep 005 controller operating mode HWT:Niv manual on 12:37:46 Production B 00122 03421 002 ThreStep 005 HWT.Niv controller operating mode automatic on

ThreStep - Internal operation ON/OFF: by switching the controller on/off from external to internal ­ operation and reverse (Status message)

12:38:29 Production B 00122 03421 002 ThreStep 005 HWT:Niv controller operating mode Intern 12:38:43 Production B 00122 03421 002 ThreStep 005 HWT.Niv controller operating mode Extern

ThreStep controller ON/OFF: by switching the controller on/off (Status message)

12:44:22 Production B 00122 03421 002 ThreStep 005 HWT:Niv controller controller operating mode from 12:45:46 Production B 00122 03421 002 ThreStep 005 HWT.Niv controller controller operating mode a

2.7 Message of the block 'SEQS'

Start error: if the unit can't be started (manual, no continuous condition, not step 0) (Fault message)

12:46:35 S Production 00122 03421 002 SEQS 013 WK sequence start fault start

Configuration-error: wrong transfer of the target-/source parameter (Status message)

12:48:13 S Production 00122 03421 002 SEQS 013 WK sequence start configuration error

2.8 Messages of the block 'DFMx'

Configuration error: General configuration errors See also: S7 blocks DFM configuration

12:48:13 S Production 00122 03421 002 DFM0 013 IDM-027 BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04 2-3

System messages

2.9 Further system messages

Message reporting failure of the IOS/PCU communication: (monitoring of the Online connection)

13:08:18 S 001 IOS 003 SINEC-H1 communication error

Messages of the weekly program: When the weekly program is enabled / stopped b the operator (SIMATIC S5 only)

Weekly program runtime enabled Weekly program runtime Stop

12:46:35 B Production 00122 03421 002 WOP 12:49:57 B Production 00122 03421 002 WOP

Messages reporting access to functions /operations protected by the operator / programmer / system CODE: Example of the configuration function

12:46:35 P 12:48:21 P PARAM PARAM xyz Login xyz Logout

2-4

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

User messages

3 User messages

3.1 Overview

There are two possibilities in order to create user messages: Initiating via block MSG (Standard interface) Initiating via FC713 (SIS_BAS library)

3.2 Initiation via the MSG-block

User messages are transmitted to a specific time by the user. The text field is configurable by the user. It is distinguished between operating messages and fault messages. The text for the incoming and outgoing message may be configured with the application 'text configuration' for the PCU in which the messages are transmitted in the files 'Meldkom.txt' and 'Meldgeh.txt'. These files are located in the catalog '...windcs\PCU.xxx\Texte'. The individual message type ist configured with the parameterization of the block MSG. The following types are supported:

EnableW/Op

0 0 1 1

S/BM

0 1 0 1

Type

M F B W

Description

Operation message Fault message Operating message Warning

See also:

Blocks S7

MSG - Message block

You will find more detailed information in the chapter 'Message structure'.

Messages of the block 'MSG'

Take saccharification test Initiation of the message via setting the corresponding flag in the Equipment operation or in the user programs operating message

12:21:55 Production M 00122 03421 002 MSG 053 operating start take saccharification sample 12:24:53 Production M 00122 03421 002 MSG 053 operating end take saccharification sample BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04 3-1

User messages

Motor protective case of a drive Initiation of the message via setting the corresponding flags in the equipment operations or in the user programs), fault message

14:44:56 F Production 00122 03421 002 MSG 054 fault start motor protection drive 47M1 14:56:13 F Production 00122 03421 002 MSG 054 fault end motor protection drive 47M1

3.3 Initiation via FC713

Free user-configurable messages can be initiated with the standard-block FC713 via the message system. The message layout ist described in chapter `Message structure'

Parameterization

The user configures the file 'Meldusr.txt' (delivered as template) the definitions for the messages that are to be initiated. In that case the same structuring rules are valid as for the system messages (see chapter Structure of the message definition files).

Example:

Line 1: M._Recipetype······_J-No.·_B-No.·_16·_SQ·_SQ-Name········016· _FC713···0068·_MELDUSR.TXT-68··_free·user-processmessage· incoming·······_FC713··00068·C··PM·05·_user-processmessage·incoming ···_BC=M·/·WinCC=PM·_RTYPN¶ Line 2: ¶ What is defined here, is the Message No. 68 ­ a user operation massage (Type ,,M") with text fields only, that means no placeholders (,,@") are necessary. Therefore the second line contains only <CRLF>

Call interface of Block FC713:

Call parameters:

Name

iTaNr

Type

INT;

Description

//=Unit-No (0, 1 ... 64) When `iTANr' = 0 the definition of message type is irrelevant. However the message will be created anyway

iMsgType

INT;

Message types //= (1, 2, 5, 6) sets the corresponding bit of the configured message type in the unit data record. If the corresponding bit is set the corresponding button for message class will be enabled by the MsgClass.ini for message class in order to acknowledge the message. 1 - Error 2 - Process message 5 - Warning 6 - Operation

iMsgDef

INT;

//=iMsgType, message definition, DW8(64...127) Index for the message definition in file `meldusr.txt'

3-2

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

User messages

byValDL4 byValDR4 iValDW5 iValDW6 iValDW7 iValDW9 iValDW10 iValDW11 wValDW12 wValDW13 wValDW14

BYTE; BYTE; INT; INT; INT; INT; INT; INT; WORD; WORD; WORD;

//=byTa_Year, year at the moment not usable //=byRecType, recipe type //=iRecipe, recipe //=iOrder, job //=iBach, charge //=iRecord, data record, instance //=iSysTxt, error text //=iTA, unit //=w24, Res.1 //=w26, Res.2 //=w28, Res.3

iValDxx:

Process value or index allocation for indicated text output.

If an output value isn't needed anymore the corresponding transfer value of the column with the default value is allocated (Default value).

The FC713 should be called edge-triggered as one message is created with each call. //_free user-operation message incoming U FP M M 3078.2 3079.2

SPBNB M005 CALL "FC713" :=0 // =sequence-No. 0; 1 to 64 // 1=Fault; 2=Processmessage; // Line in MELDUSR.TXT between 64 to // Year; actually not supported // Recipetype // Recipe // Job // Batch // Datarecord, Instance // Faulttext // Sequence // Res.1 // Res.2 // Res.3

iTaNr

iMsgType:=2 5=Warning; 6=Operation iMsgDef :=68 max. 127 byValDL4:=B#16#0 byValDR4:=B#16#0 iValDW5 :=0 iValDW6 :=0 iValDW7 :=0 iValDW9 :=0 iValDW10:=0 iValDW11:=0 wValDW12:=W#16#0 wValDW13:=W#16#0 wValDW14:=W#16#0 M005: NOP 0

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

3-3

User messages

Display of the User Message in process picture (MSG.OCX):

3-4

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

On-screen message functions

4 On-screen message functions

4.1 Overview

You have three options of on-screen message output: PCU server as message window shared by remote clients Utilization of the message archive Implementation of message faceplates in the process images

4.2 PCU server as message window

The PCU server outputs the last active message in the bottom line, starting from the left. This function is enabled by a setting in 'windcs\sys\pcu_serv.ini'. File: Entry: Key: windcs\sys\pcu_serv.ini [Remote] ShowRemoteMsg=1

To ensure that messages are output, the FIFOs must be programmed to output message frames type 3 to the IOS. Message types to be received may not be locked in the `LOCK' block of the transmitting PCU. See also: S7 blocks FIFO / LOCK. Select "Message output to screen" at the PCU server. The messages appear in a certain color that is determined by the message type.

Assignment of colors to the message types: PCU system messages

System messages Error message B Blue on white S Red on white

User messages

M Green on white F Violet on white

IOS messages

P Yellow on white P Yellow on white

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

4-1

On-screen message functions

4.3 Message archive

The daily messages of IOS, which are also enabled for message logging, can be output by means of the `Message archive' program. This message archive can be further processed by means of the 'Selection' function, so that a message can be selected based on any of its elements. See also: Message structure

4.4 Message faceplates

To enable visualization in message faceplates, the message paths to the message servers must be defined in 'windcs\sys\sys.ini' directly or via 'SiteCfg.exe' configuration-Tool. File: Entry: Key: windcs\sys\sys.ini [Paths] MSG=

You can define values such as logical drives, e.g. "x:\windcs", or a station name such as "\\ios01\c\windcs". The message faceplate assigned the "Loop-In-Alarm" function allows users to branch off to other process images or programs.

4.4.1 Loop-In-Alarm

The Loop-In-Alarm functionality is a tool which allows users to configure jumps to other programs, based on the generated error message. You can call this function either by means of the shortcut menu of the faceplate with right-click, or by double-clicking a message line. The shortcut menu shows the corresponding command, which is configured in the new "Image" attribute. When the image string ends with the extension ".bik", this string is used as parameter for calling the process image.

4.4.2 Configuring the image attribute

This attribute is configured in the text configuration tool. In the dialog box, select File -> Open to select the relevant PCU, and from the "Type" selection box the "Image file" attribute. The overview window shows the text files of the relevant objects. If no text file is found, you first need to generate these, for example, in the Explorer and then save them in PCU.xxx\Image\KLASSE.txt. The name of the text files must correspond with the name of the relevant objects, e.g. ESG1.txt, ANA.txt etc. Proceed as described earlier after you have created the new text files. When you initially open a new text file, it is registered in 'DefText.ini'. This INI file is generated if it does not exist.

Example of 'ESG1.txt'

c:\windcs\bilder\kieselgur.bik c:\windcs\bilder\kieselgur.bik c:\windcs\bilder\kieselgur.bik c:\windcs\bilder\kieselgur.bik c:\winnt\system32\calc.exe c:\winnt\system32\calc.exe c:\windcs\bilder\kieselgur.bik c:\windcs\bilder\kieselgur.bik

4-2

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

On-screen message functions

The path of the programs which are to be executed or the corresponding process image name with the extension *.bik is written to the text files. The saved data are sorted by lines. The number of characters is limited to 128. To allow you to work with multiclient functionality, the path name must define the relevant station name.

Example of 'ESG1.txt'

\\IOS1\c\windcs\bilder\kieselgur.bik \\IOS1\c\windcs\bilder\kieselgur.bik \\IOS1\c\windcs\bilder\kieselgur.bik \\IOS1\c\windcs\bilder\kieselgur.bik \\IOS1\c\winnt\system32\calc.exe \\IOS1\c\winnt\system32\calc.exe \\IOS1\c\windcs\bilder\kieselgur.bik \\IOS1\c\windcs\bilder\kieselgur.bik

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

4-3

Messages with WinCC

5 Messages with WinCC

5.1 Overview

In this use case of BRAUMAT/SISTAR Classic 5.3, the messages are recorded and visualized by the WinCC Alarm system. Basics are found in the corresponding system documentation in `WinCC Information System', chapter `Setting up an Alarm System' and should not be described here. Basic concepts of this use case were already introduced in chapter `Principle for use in WinCC'. The functions of the channel dll and format dll for carrying on the messages created within BRAUMAT/SISTAR Classic 5.3 into WinCC were pointed out there also.

Note:

The WinCC channel option of BRAUMAT/SISTAR Classic 5.3 must be installed separately. See also: ( Channel'). Installation and configuration Optional software package 'WinCC

At that time, the files Sistar.CHN (channel-DLL) Sistar.NLL (format-DLL) are copied into the folder `...\Program Files\Siemens\WinCC\bin'.

5.1.1 Assignment of Braumat Messages to WinCC Alarm Message Class and Message Type

All messages created in the BRAUMAT/SISTAR Classic 5.3 Basic system already contains the 2 character wide "MsgClass" shortcut field, by which the assignment is made to the WinCC message number and with it the definition of the acknowledging strategy and colouring of the individual messages. Reproducing a complete assignment table of all system messages here would blow up the scope of this manual - as there are over 530 different messages defined by the system. Therefore only the user messages created by means of the standard MSG block should be shown here ­ while messages created with user message block FC713 have to be configured individually via the `MsgClass' field in the `meldusr.txt' configuration file.

EnableW/Op S/BM Type Description

0 0 BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04 0 1 M F Process message Error

MsgClass WinCC Msg Type (Shortc.)

PM AH Process message Alarm High 5-1

Messages with WinCC

1 1

0 1

B W

Operator message Warning

IM WH

Operator message Warning High

Abbreviations: S/BM Error / Process message Warning / Operator message

Enable W/Op

5-2

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

Messages with WinCC

5.2 WinCC channel Configuration

The BRAUMAT/SISTAR Classic 5.3-Format-DLL for WinCC represents the connecting link between PCU server and the alarm system of WinCC and is responsible for a correct allocation of the message data fields in WinCC Alarm logging. This DLL needs two more configuration files for generating the WinCC message, which will be described in the next two chapters.

5.2.1 Configuration file "SistarNLL.ini"

The assignment between a message created in Braumat and the WinCC message class/message type is made via the system configuration file `...\windcs\sys\sistarnll.ini'. Here the short symbol located in every message will be `translated' into the WinCC Message number. A range of message numbers between 1..10 are selected per default, as these are usually not occupied by other Step 7 or PCS 7 tools. The following table gives an overview of the WinCC message classes/types used with BRAUMAT/SISTAR Classic 5.3 as well as the assigned message numbers and Braumat short symbols. The information serves as a foundation for the WinCC Alarm logging configuration too, which is described in the next chapters

Msg number

1 2 3 4 5 6 7 8 9 10

Message classe

1-Alarm 1-Alarm 2-Warning 2-Warning 7-Process message 9-Operator request 10-Operator message 11-SISTAR_ALARM 12-SISTAR_WARNING 13-SISTAR_PROCESS_MSG

Message type

1-Alarm High 2-Alarm Low 19-Warning High 20-Warning Low 106-Process message 139-Operator request 156-Operator message 161-ALARM_HIGH_PRIO 177-WARNING_HIGH_PRIO 193-PROCESS_MSG

Abbr

AH AL WH WL PM IR IM SH SW SP

Table 1: Assignment WinCC-Message classes >> Sistar-Abbreviation/Message number

The shaded area marks message classes/types which have been created automaticly by the OS project editor If the message number range 1..10 is occupied by other applications, this may be altered. The section [MsgClass] contains the assignments, where each row contains one message number: [MsgClass] AH=1 AL=2 WH=3 WS=4 PM=5 IR=6 IM=7 SH=8

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04 5-3

Messages with WinCC

SW=9 SP=10

5.2.2 Configuration file ,,MELD_WINCC.DEF"

The different information fields of each created message row, have to be transferred into the according fields of the WinCC message. For that, certan fields are transferred into process values of type text according the configuration file `...\windcs\sys\meld_wincc.def'. The structure of the definition file is described in the following:

Length

0 9 19 21 38 45 52 60 56 77 90 81 95 112 144 161 167 170 173 176 208 225

Message information

DATE TIME TYPE RECIPETYPE ORDER BATCH UNIT_PCU UNIT_NAME UNIT PCU NO MODULE NAME TEXT_SISTAR_1 TEXT_SISTAR_2 MSG_ID STATUS MSG_CLASS BATCH_YEAR TEXT_WINCC_1 TEXT_WINCC_2 RECIPETYPE_NO

Message type

CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR

Characters

8 8 1 16 6 6 3 16 3 3 4 8 16 32 16 5 2 2 2 32 16 6

Process value

MBW4

MBW6

MBW5 MBW7

Table 2:Meld_Wincc.def

The total number of process values that determine the structure of the message in WinCC are defined as follows. Associated values in greyed lines have a fix preset.

Process value

1

Description

Batch name (2-digit batch year + 3-digits recipe category +"/" + 6-digit order number + 5-digit batch number) Not used Batch ID: Batch number (3-digit;1-999) + 103 * order number ( 3-digit;1-999)

2 3

5-4

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

Messages with WinCC

+ 106 * batch year (1 digit) + 107 * recipe category (3-digit; 1-255) Example: 0162044001 (order 44, batch 1 of recipe type 16 in 2002) 4 5 6 7 8 9 10 Table 3: Process values Default: recipe category Default: block name Unit name Instance name Message text (first 32 chars) Message text (additional 16 chars) Internal use

The Standard-WinCC-message information should be formed from the measured values as followed:

WinCC-Message informationen (alarm list column)

Origin Area Event Batch name

Associated message value

Instance name / block (MBW7 / MBW5) Recipe category / unit name (MBW4 / MBW6) Message texts (MBW8 + MBW9) Batch name (MBW1)

Table 4: Message information assignment >> Associated message value:

For that, in WinCC Alarm Logging the messages used by BRAUMAT/SISTAR Classic 5.3 have to be configured as follows (Procedure see next chapter):

No

1 2 3 4 5 6 7 8 9 10

Origin

@5%[email protected] / @7%[email protected] @5%[email protected] / @7%[email protected] @5%[email protected] / @7%[email protected] @5%[email protected] / @7%[email protected] @5%[email protected] / @7%[email protected] @5%[email protected] / @7%[email protected] @5%[email protected] / @7%[email protected] @5%[email protected] / @7%[email protected] @5%[email protected] / @7%[email protected] @5%[email protected] / @7%[email protected]

Area

@4%[email protected] / @6%[email protected] @4%[email protected] / @6%[email protected] @4%[email protected] / @6%[email protected] @4%[email protected] / @6%[email protected] @4%[email protected] / @6%[email protected] @4%[email protected] / @6%[email protected] @4%[email protected] / @6%[email protected] @4%[email protected] / @6%[email protected] @4%[email protected] / @6%[email protected] @4%[email protected] / @6%[email protected]

Event

Batch name

Operation

@8%[email protected]@9%[email protected] @1%[email protected] @8%[email protected]@9%[email protected] @1%[email protected] @8%[email protected]@9%[email protected] @1%[email protected] @8%[email protected]@9%[email protected] @1%[email protected] @8%[email protected]@9%[email protected] @1%[email protected] @8%[email protected]@9%[email protected] @1%[email protected] @1%[email protected] @8%[email protected]@9%[email protected] @1%[email protected] @8%[email protected]@9%[email protected] @1%[email protected] @8%[email protected]@9%[email protected] @1%[email protected] @8%[email protected]@9 %[email protected]

Tabelle 5: Configuring the process values

Notes:

The concepts "associated message values" und "process value" are equivalent here. By an activated WinCC-Project the format-DLL monitors the write access on MELD_WINCC.DEF. Changes at the assignment instructions can be recognized and being effective by an activated WinCC-Project immediately.

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

5-5

Messages with WinCC

The implemented monitoring methods response in the above-mentioned folder with every write access and checks the "LastWriteTime" by MELD_WINCC.DEF. If this has been changed the new assignment guidelines from MELD_WINCC.DEF are read in and will be used with receiving the next PCU-messages. In order to prevent an unnecessary processor burden no files, whose content changes continuously, shouldn't be filed in the above-defined folder (*.LOG, *.DB etc.)

5.3 Working with SIMATIC-WinCC

BRAUMAT/SISTAR Classic 5.3 on the one hand uses different default message classes/types which are predefined by PCS 7, on the other hand, three additional classes/types must be created, described as SISTAR_xxx in the following table. The default classes are available not before finishing the OS Project Editor. That tool, on the other hand, is available only if the `WinCC Options for process control' are installed which is true in case of using the PCS 7 OS software package. When the OS Project Editor is not available, the whole quantity of classes/types of the following table have to be created manually.

Message classe

Message type

Acknowl Color . B=Back strategy T=Text *1)

AckCI AckCI AckCI AckCI AckCI (no ack.) w/o WO AckCI w/o WO AckCI w/o WO AckCI w/o WO B: rd T: wht B: rd T: wht B: ye T: blk B: ye T: blk B: cy T: wht B: prp T:wht B: prp T:wht B: wht T: rd B: blk T: ye B: wht T: blu

Abb Msg r no.

AH AL WH WL PM IR IM SH SW SP 1 2 3 4 5 6 7 8 9 10

1-Alarm 1-Alarm 2-Warning 2-Warning 7-Process message 9-Operator request 10-Operator message 11-SISTAR_ALARM 12-SISTAR_WARNING 13SISTAR_PROCESS_MSG

1-Alarm High 2-Alarm Low 19-Warning High 20-Warning Low 106-Process message 139-Operator request 156-Operator message 161ALARM_HIGH_PRIO 177WARNING_HIGH_PRIO 193-PROCESS_MSG

Table 6: Summary of Alarm Logging configuration

*) Notes on configuration 1. Property page of message class Tab ,Acknowledgment' AckCI = Acknowledgment Came In AckWO = Acknowledgment Went Out w/oWO = Message Without Status Went Out 2. Property page of message type Background color / Text colol 3. Property page of the message Tab Text / Info Field

5-6 BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

Messages with WinCC

The shaded area marks message classes/types which have been created automaticly by the OS project editor

5.3.1 Configuration steps in WinCC Alarm logging

Creating Messages

The following section describes the necessary configuration steps within the ,Alarm logging' application by outline. Detailed instructions can be found in the `WinCC Information System' section `Working with WinCC Setting Up an Alarm System Configuring the Message system' Configuration takes place in the following steps: Create one raw data variable named MELD in WinCC Datamanager under channel folder SISTAR Sistar Unit #1 xxxxxx (`xxxxxxx' as defined at installation) Create the message classes and configure the acknowledge strategy according the above table Create the message types and configure the coloring according the above table Create message numbers 1..10 and configure class/type assignment and other column information from the process values. This step is done via the Import function in menue `Messages Import single messages...' and selection of the configuration file `...\Windcs\sys\MSG_BL_1.TXT'. The option `Overwrite Messages and Import new Messages' should be selected in this dialog. After the import the message numbers should be displayed from 1-10 in the tabular list (compare Fig. 1).

Fig. 1: Message numbers after successful import

The individual messages (1-10) need to be checked regarding to their correctness by the corresponding property dialog, which includes 3 register tabs.

Notes:

In WinCC Alarm-Logging the language of the messages may be selected by menu `View / Language...' If the language selected here does not correspond with the actually configured Runtime language, then the additionally created message classes are not visible f.e. in the property dialogs of the Alarm Control. After adding new message classes the Selection properties of Alarm controls may be necessary. This is described in chapter `User defined message views with the WinCC Alarm Control'

Archive configuration

The following screenshot shows the standard archive configuration when using the OS Project Editor. It should be adapted to the individual plant project needs.

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

5-7

Messages with WinCC

5-8

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

Messages with WinCC

5.3.2 Configure Process Images

The standard OS runtime window provides a message bar at the top edge and additional message windows that can be opened by clicking in the toolbar. For more detailed information on the functionality and configuration of the message windows, refer to the "PCS 7 ­ OS Process control" manual, Chapter 8 "Message system, diagnostics of the process".

Note:

If the standalone `WinCC Scada' product and not the PCS 7 OS Station is used, you can skip the following chapter.

5.3.2.1 Message views in Process Control Runtime

Three additional message classes/types named `SISTAR xxxxx' were entered into the WinCC AlarmLogging configuration. These classes have to be additionally enabled in the filtercriteria of the message lists of Process Control Runtime. Please pay attention to the following: The additional filter configuration should be made for all message lists except the `Operator input list' as noted in the chapter 8.3 `Message lists in PCS 7' of the manual mentioned above. In the opened message list window, click on the `Open Selections dialog' button in the icon bar Expand the Message classes group and select the SISTAR Alarm, SISTAR Warning and SISTAR Process classes additionally The Option `Persistance in CS and RT' should be selected before leaving the dialog with the OK button The procedure for adjusting the filter selections is described in detail in chapter 8.6 ,Options and use of message filters' of the manual ,PCS 7 ­ OS Process' control'.

5.3.2.2 User defined message views with the WinCC Alarm Control

Individual configured message views on the process pictures may be created by the user with the WinCC Alarm Control. By double clicking on a previously included control the user is able to customize the detailed behaviour at runtime. These aspects are described in detail in the documentation `WinCC Information system' chapter `Working with WinCC Setting Up an Alarm System Displaying Messages in Runtime'. At least for BRAUMAT/SISTAR Classic 5.3 the following settings are recommended from the variety of the possible settings of the control alarm: The following adjustments should be selected on configuration: General / Active list upon open picture = `Short term archive list' Message blocks / Selection ... select all message blocks which should be available in the `message lists' register tab (see next item) Message lists / Selected message blocks = ... select all desired Blocks to be viewed as columns in the message window Message lists / Data preparation / Selection = ... select the desired message classes and filter criteria including the SISTAR classes The following table shows a detailed list of recommended configuration setting of the alarm control, but of course they may be adapted to individual demands.

RegisterTab

General General BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

Range

Active List upon Open picture Server selection

Setting

Message list All Servers

Comment

5-9

Messages with WinCC

Parameters Parameters Parameters Parameters Parameters Toolbar Toolbar Toolbar Toolbar Toolbar Toolbar Toolbar Toolbar Toolbar Toolbar Toolbar Toolbar Toolbar Status Bar Status Bar Status Bar Status Bar Status Bar Status Bar Status Bar Message Blocks

Selection Select using Column properties Column properties Other Keyboard functions Keyboard functions Keyboard functions Keyboard functions Keyboard functions Keyboard functions Keyboard functions Keyboard functions Keyboard functions Keyboard functions Keyboard functions Keyboard functions Display toolbar Elements of the status bar Elements of the status bar Elements of the status bar Elements of the status bar Elements of the status bar Elements of the status bar Display Status Bar <default>

Line Color change Column title Change Column with Sort by Column Heading Message list Short-term archive list Long-term archive list Single acknowledgment Group acknowledgment Selection dialog Print message report Print current view First message Last message Next message Previous message Date Time Number of messages in the list Number of messages in the window Number of messages not yet acknowledged Lock Default = <not selected> Should be enabled, if enough space available Selection is taken over from alarm logging configuration Date Time Number Type Batch Name Message number (1..10) Message type 16 Chars, Format: yyrrr/jjjjjbbbbb yy batch year (2 Ch) rrr Recipetype (3 Ch) jjjjj Job.No. (5 Ch) bbbbb Batch no. (5 Ch) R-Type / Unitname Block / Instance Messagetexts (48 Ch) ,,C / G" SQL-Syntax: Active only with message list Active only with message list

Message lists Message lists Message lists Message lists Message lists

Selected message blocks Selected message blocks Selected message blocks Selected message blocks Selected message blocks

Message lists Message lists Message lists Message lists Message lists

Selected message blocks Selected message blocks Selected message blocks Selected message blocks Selection

Area Source Event Status Message class/Alarm

5-10

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

Messages with WinCC

CLASS IN(1, 2, 7, 9, 10, 11, 12, 13) AND TYPE IN(1, 2, 19, 20, 106, 139, 156, 161, 177, 193) Message lists Message lists Message lists Message lists Message lists Message lists Message lists Hit list Persistence Selection Selection Selection Selection Selection Selection Selection <default> <default> Message class/Warning Message class/Process message Message class/Request for Operator Input Message class/Operator Input Message Message class/SISTAR Alarm Message class/SISTAR Warning Message class/SISTAR Process not used

The selected message blocks in the shaded area are representing the essential BRAUMAT specific message information. The message views already created by the OS-Project editor (see previous chapter) may serve as further examples which are available as separate files named ,@Alarmxxxxx.pdl' in the Graphics Designer folder of the project.

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

5-11

Messages with WinCC

5.4 Example - Message window

A WinCC standard-message window complete by the SISTAR - messages it can look like as followed:

All SISTAR will be entered in the SISTAR-messages 1:1 after WinCC as an incoming messages. This is only a suggestion the WinCC-message-window, the message classes and message types can be adapted basically anyway. As Standard-view for BRAUMAT/SISTAR Classic 5.3 with WinCC, this configuration has been considered as the most convenient.

5-12

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

What to do on errors?

6 What to do on errors?

6.1 Problems

No. Error

1 In WinCC no messages appear

Remdy

Testing of the entries in the file 'windcs\sys\sistarnll.ini' Name and path of the file meld.def under ,settings '.

2

According to the import of the messages those ones are missing in the joint piece 'text' of the message the entries of the process values (@1%@ ...)

The import function references ID on text s.. The import file returned by the system starts from ID's which were assigned during the first transfer. The assignment of the same ID's can not be guaranteed, however. Remedial action For the 8 messages of BRAUMAT/SISTAR Classic 5.3 the entries must be carried out manual.

BRAUMAT/SISTAR Classic 5.3 Messages A5E00239391-04

6-1

Information

Messages

47 pages

Report File (DMCA)

Our content is added by our users. We aim to remove reported files within 1 working day. Please use this link to notify us:

Report this file as copyright or inappropriate

479978


You might also be interested in

BETA
Messages