simatic automation system braumat/sistarclassic v5 ......preface, contents equipment operations and...

Preface, Contents Equipment operations and functions

1 EPE as S7-FC Block 2

SIMATIC

Automation system BRAUMAT/SISTARClassic V5.3 EPE Engineering Manual

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

Edition 11/2007 A5E00239378-04

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 Siemens AG Automation and Drives Postfach 4848, D- 90327 Nuernberg, Germany

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 2007 Technical data subject to change.

Siemens Aktiengesellschaft A5E00239378-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.

BRAUMAT/SISTAR Classic V5.3 iii EPE Engeneering A5E00239378-04

Preface Purpose of the Manual

The abbreviation EPE stands for "Equipment Procedural Elements". These are equipment operations and functions in connection with BRAUMAT/SISTAR Classic V5.3.

This manual describes the generation of equipment operations and functions and gives you an overview of the following topics:

Basics of equipment functions and operations (EPEs)

Status transition of an EPE

Comparison of the EPE-generation possibilities

EPEs as SIMATIC S7 FC-block

Interface of an EPE with generation as S7-FC

Generation with PCS7 CFC / SFC

BF+ compatible configuration

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

iv BRAUMAT/SISTAR Classic V5.3 EPE Engeneering

A5E00239378-04

Document structure

Building blocklibrary: Route

Control

Serve & WatchRoutes

Engineering of theRoute Control

Serve & Watch'based on S7'

Application for'based on S7'

Message

Installation andConfiguration

Administration

Communication

Description of theSystem

Recipe System

Batch-processing

Operation &Control batches

Building blocklibrary :Basics

Engineering'based on S7'

EPE-creation

Dosing andWeigher

Building blockdescription S7

Building blockdescription S5

Batch curves

Logging

BRAUMAT/SISTAR Classic V5.3 v EPE Engeneering A5E00239378-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

http://www.siemens.com/automation/partner

http://www.siemens.com/simatic-tech-doku-portal

http://mall.automation.siemens.com/

http://www.sitrain.com/

vi BRAUMAT/SISTAR Classic V5.3 EPE Engeneering

A5E00239378-04

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: + 49 180 5050 222

• Fax: + 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".

http://www.siemens.com/automation/support-request

http://www.siemens.com/automation/service

http://www.siemens.com/automation/service&support

BRAUMAT/SISTAR Classic V5.3 vii EPE Engeneering A5E00239378-04

Contents 1 Equipment operations and functions 1-1

1.1 What is an EPE? ......................................................................... 1-1 1.1.1 EOP (Equipment Operation) ........................................... 1-2 1.1.2 EPH (Equipment Function).............................................. 1-2 1.1.3 Division EOP and EPH.................................................... 1-2 1.1.4 EPE statements............................................................... 1-2

1.2 State transition of an EPEs ......................................................... 1-2 1.2.1 State explanation............................................................. 1-3 1.2.2 Commands ...................................................................... 1-4

2 EPE as S7-FC Block 2-1

2.1 General ....................................................................................... 2-1 2.2 EPE interface .............................................................................. 2-1 2.3 Sequencer interface .................................................................... 2-1

2.3.1 Global flag interface ........................................................ 2-2 2.3.2 Global Variable SEQ.u .................................................... 2-4

2.4 RCS-Interface ............................................................................. 2-5 2.4.1 Overview ......................................................................... 2-6

2.5 ICM-interface............................................................................... 2-7 2.5.1 General notes.................................................................. 2-7

2.6 Interface Digital Values ............................................................... 2-8 2.7 Interface to PE ............................................................................ 2-8 2.8 DFM-Interface ............................................................................. 2-8

2.8.1 Call of the DFM processing ............................................. 2-8 2.9 Measured value interface............................................................ 2-8 2.10 Controller interface...................................................................... 2-8 2.11 Interface to the batch system ...................................................... 2-9

2.11.1 Change batch state ....................................................... 2-9 2.11.2 Create batch................................................................ 2-10 2.11.3 Call interface FC714.................................................... 2-12

2.12 EOP-generation with S88-states............................................... 2-13 2.12.1 Structure of a STL EOP............................................... 2-13 2.12.2 Maximum extension .................................................... 2-13 2.12.3 Minimum extension ..................................................... 2-18 2.12.4 BRAUMAT/SISTAR Classic V5.3 Extension ............... 2-18 2.12.5 Compatibility to V4.x.................................................... 2-18

2.13 Engineering of alternative branch for recipe.............................. 2-18 2.14 Engineering of jumps in the recipe............................................ 2-18 2.15 EOP followed by an AND synchronization ................................ 2-19

Equipment operations and functions

BRAUMAT/SISTAR Classic V5.3 1-1 EPE Engeneering A5E00239378-04

1 Equipment operations and functions

1.1 What is an EPE? The abbreviation EPE stands for‚Equipment Procedural Elements‘.

These are equipment operations and functions in the connection with BRAUMAT/SISTAR Classic V5.3 EPEs are implemented as SIMATIC FC-Program or SFC-Program in AG and called by the recipe control.

Process Cell

Unit

EquipmentOperation

Equipmentphase

Unitprocedure

RecipeOperation

Recipefunction

Physical Modell

belegt

benutzt

benutzt

RecipeProcedure

eqm_mod.vsd

Area

TechnicalProcedural Elements

(EPEs)

Controlmodule

TechnicalEquipment

Procedural Elementsof the recipe

Note! EPE Equipment phase hasn't yet supported by the Version BRAUMAT/SISTAR Classic V5.3

See also: Description of the system Physical model


BRAUMAT/SISTAR Classic V5.3 EPE Engeneering

A5E00239378-04

1-2

1.1.1 EOP (Equipment Operation) One EOP is assigned to a unit and can use all sub-objects of a unit. A EOP is used by a recipe operation. A operation conducts a chemical or physical change of a batch.

1.1.2 EPH (Equipment Function) One EPH could be directly assigned to a unit or to an equipment module. One EPH uses only and typically control modules and is used by recipe functions. Functions are less in a functional way in contrast to operations.

1.1.3 Division EOP and EPH There is no explicit separation between EPH and EOP. You can divide most tasks of a process cell according to above-mentioned definitions. There are always borderline-cases, which make a clear separation between EPH and EOP impossible.

1.1.4 EPE statements An EPE should capsule a function

An EPE is assigned to a unit

An EPE does only use signals and sub-objects of a unit

An EPE consists of action blocks and step transition state

An EPE can react to S88-states

An EPE uses no global signals

The more precise a unit is structured and the better the operations and functions are capsuled the better is the conversion for created EPEs to other units. Only, in this way you can fulfill the automatic conversions and reuse.

1.2 State transition of an EPEs There is defined a state transition for equipment operations and functions in the norm. The system supports all states and transitions. In addition the state ‚Starting‘ and ‚Completing‘ is supported by the system.



Complete

Idle(Initial State) Running

Aborting

Aborted

Stopping

Stopped

Restarting Held Holding

Pausing

Paused

Final conditions

Intermediateconditions

Transition conditions

Abort

Pause

Hold

Resume

Reset

Restart

Reset

Reset

Stop

Starting

S88_state.vsdP.C.: Process condition

Start

Completing

P.C.

P.C. P.C.

P.C.

P.C.

P.C.

P.C.

P.C.

A state change occurs by orders, which could happen by manual operation, automatic or user programs. Leaving intermediate (‚ing‘-states) are controlled by EPE itself by evaluating process operations.

1.2.1 State explanation Idle

The procedural element waits for a Start-command which causes a transition to the state ‚Running‘.

Starting

Starting phase of the procedural element, which operates before it 'runs'.

Running

Normal operation.

Completing

Final phase of the procedural element which operates only one time at the end.

Complete

Function of the normal operation is finished. The procedural element waits to the command‚Reset‘, which causes a transition to the state ‚Idle‘.

This state isn't supported by BRAUMAT/SISTAR Classic V5.3. All actions should be made in the 'Complete' state.

Pausing

The procedural element has received a ‚Pausing‘- command. This causes, that the procedural element stops at the next determined position which is also safe and stable in his normal ‚Running‘- Logic. The state passes automatically over to ‚Passing‘.

Paused

If the procedural element was paused, the operating state changes to operating state. This state is valid usually for short-termed pausings. The command‚Continue‘ induces the



A5E00239378-04

1-4

transition to the ‚Run‘- State, where the normal processing is started behind the designed Abort position again.

Holding

The procedural element has received a ‚Hold‘-command and conducts its ‚Completing‘- Logic, in command to lead the procedural element to a designed state. If no sequence is available, the procedural element enters immediately in the ‚Holding‘- State.

Held

The procedural element has finished its ‚Held‘- Logic and is in a designed or known state. This state is usually used for a long-term interruption. The procedural element waits for any further commands for continuing.

Restarting

The procedural element receives in the state ‚holding‘ an command to ‚Restart‘. It operates a Restart-Logic in command to return to the state ‚Run‘ . If no sequence is available , the procedural element will immediately pass over to the ‚Run‘- State.

Stopping

The procedural element receives a ‚Stop‘-command and conducts the logic ‚Stopping‘, which relieves a controlled Stopping. If no sequence is available, the procedural element will immediately pass over to the ‚Stopped‘- state.

Stopped

The procedural element has finished the logic for ‚Stopped‘. It waits for the command ‚Reset‘, in command to change to the state ‚Idle' operation‘.

This state is not supported by BRAUMAT/SISTAR Classic V5.3. Alle actions should be made in the state Stoppend.

Aborting

The procedural element receives the command ‚Aborting‘ and conducts the logic ‚Aborting‘, after that an abnormal stopping, that is more rapid and necessarily controlled, will be introduced. If no sequence is available the procedural element passes immediately over to the ‚Aborted‘ state.

Aborted

The procedural element has finished the logic ‚Aborted‘. It waits for the command ‚Reset‘ in command to change to the state ‚Idle‘.

This state isn't supported by BRAUMAT/SISTAR Classic V5.3. All actions should be made in the state 'Aborted'.

1.2.2 Commands Start

This command induces the procedural element to execute the normal logic ‚Running‘. This command is only valid , if the procedural element is in the state ‚Idle‘.

Stop

This command induces the procedural element to execute the logic ‚Stoppend‘. The command is valid, if the procedure element is in the state ‚Runs‘, ‚Pausing‘, Paused‘, ‚Holding‘, ‚Held‘ oder ‚Restartend‘.

Hold

This command induces the procedural element to execute the logic ‚Holding‘. The command is valid, if the procedural element is in the state ‚Runs‘, ‚Pausing‘, Paused‘, or ‚Restartend‘.



Restart

This command induces the procedural element to execute the ‚Restartend‘- Logic, which makes a safe return to the state ‚Run‘. The command is only valid, if the procedural element is in the state ‚Held‘.

Abort

This command induces the procedural element to execute the logic ‚Aborting‘. The command is allowed in each state, besides in ‚Idle‘, ‚Completing‘, ‚Aborting‘ and ‚Aborted‘.

Reset

This command induces a transition to the state ‚Idle‘. It is valid from the state ‚Complete‘, ‚Aborted‘ and ‚stopped‘.

This command is not supported by BRAUMAT/SISTAR Classic V5.3.

Pause

This command induces the procedural element to stop at the next pausing position, which is determined first within a procedural logic and to wait for a command ‚Continue‘ to over run. The command is only allowed in the state ‚Running‘.

Resume

This command induces the procedural element, which was paused as a result of a command ‚Pause‘ at a designed connector‚Paused‘ to continue the execution. The command is only valid, if the procedural element is in the state ‚Paused‘.

EPE as S7-FC Block


2 EPE as S7-FC Block

2.1 General In BRAUMAT/SISTAR Classic V5.3, the EPE must be available in the PCU. It is created as S7 FC block in the programming language STL or SCL.

2.2 EPE interface An EPE has mainly the following interfaces:

to the Sequencer

to the induvidual control modules of the unit

to the control modules of the unit

to the setpoints of the unit

Overview of the EPE interface

Interface Step 7

Sequencer interface Global flags SEQ.u

RCS interface SEQ.uRCS

Interface final control element ESG flag + inputs

Interface digital values Timer

Parameter elements PE block

DFMs Global flag / DS

Measurement value MESS

Controller PID

Job system FC714

2.3 Sequencer interface The interface to the sequencer is realised via global flags and the Variable 'u' in the data block DB 725 This interface type makes it possible to work with the support of the STEP 7-Symbolic function. Before each EPE-processing, the interface is built up from the stored sequence data and after processing the data are safed.

EPE as S7-FC Block


A5E00239378-04

2-2

SequencerData record

GlobalInterface

Seq <-> EOPC

opy

EOPFC

Cop

y

read

write

Ope

ratio

n ca

ll

3

1

2

eop_call.vsd

Sequencer FB

FB c

all read

write

456

7temporary copy

of the datarecord

Variable 'u'

1

The global flag interface is restaurated from the sequencer data record. In addition the complete data record is copied in the temporary variable ‚u‘ of the sequencer data building block before calling the EOP.

2 Call Sequencer-function block, with the identifier ‚Start‘.

3 User program reads and writes signals of the flag interface.

4 Call of the operation by sequence control.

5 User programs of the EOP reads and writes signals of the flag interface.

6 Call the Sequencer Function block, with the identifier ‚End‘.

7 The whole data record of the temporary variable is written back in the sequencer data record. The complete data record is written back completely from the temporary variable ‚u‘, after having called the operations and the sequencer-FBs. Afterwards parts of the flag interface are transferred in the sequence data record.

2.3.1 Global flag interface Access

S1 : one-time setting

R1: one-time resetting

W: written and reading access

R: only reading access

Overview global flag interface

Address Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

EPE as S7-FC Block


99 HUP

100 SeqRes

101 FTUE BEDA ZGEA FBGO SRDR TVERZ TUET

102 HAND DB PSPR TSTA GSTO GSTA ATL PLUS

103

104

105

106

107 HUPS

General Signals

Symbol Comment Address Access HUP HUPsignalevent

Is set by sequence of monitoring time (TUE) . Processing and resetting by the user.

M99.4 R1/R

TUET Monitoring time (TUE) Unit Result display of the monitoring time of the unit. 0 / 1 = Time hasn't run out/Time has run out

M101.0 R

TVERZ Waiting/Delay time is started by EOP-Start Time runs: TVERZ = 0 Time run out: TVERZ = 1 For Signal change TF/S from 0 to 1 (Display “-“ after “+“, from STOP to (ENABLED) Time is triggered again.

M101.1 R

SRDR Start to automatic printing of the step log. By EOP-input SRDR is always = 0.

M 101.2 S1/R1 W

FBGO Flag for TA-FB: PostPre= 0: Call FBs before EOP-processing Exclusively DFM-processing! PostPre= 1: Call FBs after EOP-processing

M101.4 R

ZGEA Set sequence bits of the user. M 101.5 W

BEDA Set operator prompt. M 101.6 W

FTUE Enabling a message by exceeding monitoring time. The sequence control sets bit always to 1.The user program (EOP) could reset. RelTMsg=1: By exceeding the step monitoring time, the unit control signals error (display+message). RelTMsg=0: By exceeding the step monitoring time, the unit control doesn't signal any error.

M 101.7 W

PLUS Sequencer is not in hold M102.0 R

ATL Sequencer is running This Bits are stored in Flag range M656.0 – M661.7 additionally

M 102.1 R

GSTA First runtime cycle of the EOP M 102.2 R

GSTO Last runtime cycle of the EOP M102.3 R

TSTA Start impulse Sequencer. This bit has the value 1 for the first operation, otherwise always 0.

M 102.4 R

PSPR Block log input. M 102.5 W

EPE as S7-FC Block


A5E00239378-04

2-4

DisProt=1 stops a log input with EOP-End. With EOP start resets the sequence control. (DisProt=0)

DB Permanent condition display M 102.6 R

HAND Display of the hand operation of the sequence M 102.7 R

HUPS (HUPS)

Alarm horn flag Is set at ICM-, AIN-, MSG- und Teilanl(TUE)-disturbance, processing and reset by the user

M107.1 R1/R

SeqRes Reserved Not to be used

MB100 W

2.3.2 Global Variable SEQ.u Interface

Symbol Kommentar Zugriff CTRL.ReloadPara New tansmission of the setpoint values to the DFM W

CTRL.boRemainHolding Remain in the state 'holding'. The flag must be set by the EOP, in case the 'holding' state should be remain after 'hold' command. If the flag is reset the next state 'held' will be reached.

W

CTRL.boCMDHold Command 'Hold' This flag signals the state 'held' in combination with 'boRemainHolding'=0.

R

CTRL.boRemainRestarting Remain in the state 'restarting'. The flag must be set by the EOP, in case the 'restarting' state should be remain after 'restart' command. If the flag is reset the next state 'running' will be reached.

W

CTRL.boCMDRestart Command 'restart' R

CTRL.boIsRunning EOP is in 'running' state. R

CTRL.boRemainPausing Remain in the state 'pausing'. The flag must be set by the EOP, in case the 'pausing' state should be remain after 'paused' command. If the flag is reset the next state 'paused' will be reached.

W

CTRL.bCMDPause Command 'paused' This flag signals the state 'paused' in combination with boRemainPausing=0.

R

CTRL.boRemainAborting Remain in the state 'aborting'. The flag must be set by the EOP, in case the 'aborting' state should be remain after 'abort' command. If the flag is reset the next state 'aborted' will be reached.

W

CTRL.boCMDAbort Command 'abort' This flag signals the state 'aborted' in combination with boRemainAborting=0.

R

CTRL.boRemainStopping Remain in the state 'stopping'. The flag must be set by the EOP, in case the 'stopping' state should be remain after 'stop' command. If the flag is reset the next state stopped' will be reached.

W

CTRL.boCMDStop Command 'stop' This flag signals the state 'stopped' in combination

R

EPE as S7-FC Block


with boRemainStopping=0.

Batch- and Step information

The batch and step information aren't ranged on global flags. These data could be read / written via the Variable ‚u‘ in sequencer data building block (DB725).

Symbol Comment Variable Access InewStep new step counter u.iNewStep R

ByYear year of the batch u.byYear R

ByRecType recipe category of the batch

u.byRecType R

Irecipe recipe number u.iRecipe R

Iorder order number u.iOrder R

Ibatch batch number u.iBatch R

SnBA_Name batch name u.snBA_Name R

DiBA_ID batch ID u.diBA_ID R

DiStep_ID step ID u.diStep_ID R

ByAlterResult Alternative result A GOP (alternative producer) retruns the unit control the number value of the required alternative (number 1..255 from the recipe procedure). The value 0 is invalid Jump destination The jump destination (derived from the recipe procedure) must be stored at this location.

u.byAlterResult W

2.4 RCS-Interface The interface is realised via the global Variable Seq.uRCS. The type of the variable is RC_ROUTE_CM_UDT (UDT 110).

EPE as S7-FC Block


A5E00239378-04

2-6

2.4.1 Overview

DB 725H

eade

r dat

a

Copy of the actual SeqDS

RCS data(Copied data of the Route

DB)

DS 1R_ID

R_ID

RCS DS

Route DB (R_ID)

copy

copy

by R_ID

DS 1

DS ...

EOP_FC

"SEQ".uRCS"SEQ".u.

rcs_db_725.vsd

The Variable SEQ. uRCS is stored in the header of DB725 ("SEQ"). Via this variable the data exchange with the Route Control is done.

Read data by the Route block

Defined data are read by the Route block before the EOP is called. This is only made, if the value of the Route-ID is not zero. The Route-ID is read out the sequencer data record Variable "SEQ".u.iROUT_ID.

Write data to the Route block

After having called the EOP, defined data are written back in the route block. The route block is defined by the Variable "SEQ".u.iROUT_ID. There is only an transmission made if

"SEQ".uRCS.REQ or "SEQ".uRCS.RON display the value 1.

Route request with dynamic Route_ID allocation

The System can allocate the Route-ID to the time of the Route request. For this function the Route-ID must have the value 0. The user program in the EOP must set the Route-ID to the value 0. For the next call of the EOP a Route-ID is allocated by the System.

See also: RCS Projektierung Dynamic route ID allocation

Interface

Symbol Comment

FUNC_ID Function-ID

TRANS_ORDER Job number for the transport of the Route

REQ Route Request

RON Switch on Route

HOLD Hold Route

IGN_ERR Ignore error

SOLID Route is a solid transport

ACK Acknowledgement of time monitoring errors

GETXPE Read External Parameter elements

EPE as S7-FC Block


SET_MAT Set Material-ID

MATERIAL ID of the transporting material

SOURCE Source destination of the Route

VIA1 .. VIA10 Via destination of the Route

DEST Target destination of the Route

MODE_TBL Function catalogue number of the Route

MODE_01 .. 32 Function control 1 to 32

QRET_VAL Return value

QDIAG Diagnosis value

QREQ_RC Route request state

QINTERN Internal (Automatic) External (Manual operation)

QREQ Route request error

QON Switch on display Route

QHOLD Hold display Route

QMODE_01 .. 32 Acknowledgement of the functions 1 to 32

QRESTPOS_01 .. 32 Position of rest error display of the functions 1 to 32

QMON_ERR_01 .. 32 Monitoring time error display of the functions 1 to 32

QFLT_ERR_01 .. 32 Error time display of the functions 1 bis 32

QGRP_ERR_01 .. 32 Composite error display of the functions 1 to 32

QMON_TOU Composite error display monitoring error times

QFLT_TOU Composite error display error time

QERR Composite error display

QMAT_ERR Error with testing the material sequence

QMAT_OK Test of the material sequence successful

QACTIVE Route is activated

GETXSTS State of the external parameter elements

GETXDIAG Diagnosis information for the state of the external parameter elements.

IROUTE_STATE Status of the Route

IRET_VAL_TRANS Error number of the allocation block FB830

BoDATA_VALID Allocated data are valid

2.5 ICM-interface

2.5.1 General notes ICMs are addressed via the global flags. These flags are listed in the documentation 'blocks S7'.

See also: Blocks S7 ICM

There are flag interfaces for

CA Control Automatic

FOn Feedback on

FOff Feedback off

EPE as S7-FC Block


A5E00239378-04

2-8

2.6 Interface Digital Values Version based on S7

Digital values are addressed via the block SE-timer in the instance. This interface includes:

Input signals

Output signals positive

Output signal negative

2.7 Interface to PE Parameter elements can be addressed via the PE-blocks (DB97) .

The allocation of the values must be made by the user program.

2.8 DFM-Interface The DFM-setpoints are supplied by the recipe system. Actual values are determinated dependand on the DFM type.

Process values are read via a source indication of the DFM-block. The source indication must be configured via the parameterisation .

Result flag

The DFM result flags are stored in a global flag interface. These flags are listed in the documentation Blocks S7.

See also: Blocks S7 DFM - Digital Function Modules

2.8.1 Call of the DFM processing The DFM processing must be made in the SequenzerFB. This is required, as there is only the guarantee at this location that the result flag has the correct value. This is especially important for the step change in PCU-cycle.

Note!

In command to guarantee a correct DFM-result, the interface block must be called at least twice as often like in the sequencer processing (in 500 ms OB). Only then, you can guarantee that the process value in the DFM data record corresponds to the actual one at the source block.

2.9 Measured value interface The measuremen value interface includes:

underride the lower limit

override the upper limit

There is the possibility to determinate the allocation of the flag in the description 'Block S7'.

See also: Blocks S7 AVA - Measured value recording

2.10 Controller interface The controller interface includes:

EPE as S7-FC Block


Correction flag YN

There is the possibility to determinate the allocation of the flag in the description 'Block S7'.

See also: Blocks S7 PID - Controller

2.11 Interface to the batch system The sequencer or the EOP can influence the job system of the server. You must create telegrams of the type 15.These telegrams can be sent via the call of FC 714.

You can execute the following actions :

Action 50: Enable batch

Action 51: Disable batch

Action 52: Set batch for 'ready'

Action 60: Create batch

2.11.1 Change batch state This concerns the messages 50,51 und 52.

2.11.1.1 Direct indication of the batch You can indicate the batch directly.

The values of year, recipe type, job- and batch number specify the batch.

The parameter Condition must have the value 0.

2.11.1.2 No direct indication of the batch You can also set the value of year, recipe type, job and batch number ( Inputs at FC714 are called: byYear, byRecType, iOrder; iBatch;) to the value 0. This means that there is a search for a corresponding batch in the batch list. The state of the first suitable batch is set.

Example:

Year = 0; Recipe type = 2; Job number = 0; Batch number = 0; You take the first batch of the year 0 and the recipe type 2 and set the batch state.

Furthermore you can restrict the influencing batch via the parameter 'State', 'Index' and 'Value' (Inputs at FC714 are called: byState, Index and value).

Values of the batch can be compared with the value of the parameter Value.

The comparison function is indicated via the parameter ‚State‘.

State

BatchVal: Value of the parameter in the job list

TeleVal: Value which is in the message

1: BatchVal equal TeleVal

2: BatchVal inequal TeleVal

3: BatchVal more TeleVal

4: BatchVal more or equal to TeleVal

5: BatchVal less TeleVal

6: BatchVal less than or equal to TeleVal

EPE as S7-FC Block


A5E00239378-04

2-10

Index

Index Meaning

0 Invalid

1 – 221 Job parameter

1000 Line number

2.11.2 Create batch This function uses the message 60, 61 or 62.

2.11.2.1 Meaning of the parameter Parameter Type Meaning

byYear Bit Year of the batch byRecType Bit Recipe type of the batch iRecipe Bit Recipe of the batch iorder Bit Job number of the batch iBatch Bit Batch number of the batch iRecord Bit Not used iNachricht Bit 60 = Create batch iSpaltenIdx Bit Line number byCondition Bit Batch state with creating unused Bit Start modi wValue_High Bit Start time (Second value since 1970) High

part wValue_Low Bit Start time Low part

2.11.2.2 Batch state The state is always filed in the Parameter 'State' .

Value Status

‚R‘ (82) Enabled

‚V‘ (86) Ready for enabled

‚L‘ (76) Disabled

See also: Operation & control of batches Batchstates

2.11.2.3 Indication of the line / stream Lines-/Streams numbers must be transferred in the parameter 'Column index'.

For recipes without line configuration you must always transfer with 0. Then the default line of the job type is set.

For stream recipes you must add the value 10000 to the stream.

2.11.2.4 Indication of the Startmodi and start time Startmodi

Value Startmode

2 As soon as possible

EPE as S7-FC Block


3 After time

4 After result

5 After time with automatic time adaptation

See also: Operation & control of batches Startmodes

Start time

The indication is the second value since 1.1.1970.

972.914.400 correspond to 30.10.00 14:00

in Hex 39FD 7E2E.

2.11.2.5 Default values The rest of the parameter are presetted

Parameter Presetting

Batch size Nominal batch size from the recipe header

EPE as S7-FC Block


A5E00239378-04

2-12

2.11.3 Call interface FC714

CALL FC 714 byYear :=B#16#0 byRecType :=B#16#1 iRecipe :=2 iCommand :=2002 iBatch :=1 iRecord :=30 iMessage :=60 iColumnIdx :=10001 byStartmodi :=B#16#3 byState :=B#16#76 wValue_High :=W#16#39F0 wValue_Low :=W#16#7E2E

EPE as S7-FC Block


2.12 EOP-generation with S88-states In the chapter the state transition and the necessary reaction within STL-EOP are described. The usage of the the states and the transitions depending on the process cell and client inquiry.

Therefore, it will be considered the principle EPE structure in AWL. In the view of the EPE-Editor in the following version, you should consider a few rules. Therefore, it will be considered the principle EPE structure in AWL.

2.12.1 Structure of a STL EOP Action blocks and step complete transition

An EPE consists of a sequence of action blocks. The last network is the step over transition. The step over transition closes the running-branch.

EPE

Action block

Action block 2

Action block n

WSB

epe_block.vsd

General structure

EPE

StartingBlock

Running Block

Completing Block

WSB

Action blocks for S88-Conditions

Held Block

Restarting Block

Action blocks

Every action block consists of an input transition. The input transition creates a binary result. This binary result could be assigned directly or used by conditional jumps.

Each action block should be programmed in a network. The action blocks are the S88-states. The action blocks could also be user-defined conditional blocks by the function.

An action block consists of

Input transition (creates a binary result)

Optional assignments of the binary result

Optional instructions that are only operated with the result 1 or 0.

A edge-evaluation is necessary for recognizing a new state. This evaluation is made in the sequential control and the EOP is made available. The global flag has the Symbol ‚NewState‘.

2.12.2 Maximum extension One EPE is listed with all supported states in the listed network.

The user program is simulated by the sequencer user flag in the examples.

2.12.2.1 Enter starting state On the start request GSTA the request it is set not to leave the starting state. The input state is only fulfilled one time.

EPE as S7-FC Block


A5E00239378-04

2-14

The operation request and the additional item is the user program in this example. NETWORK TITLE ="Start block " // TRANS U "GSTA" UN "SEQ".u.CTRL.boStarting // VKE SPB StrT SPA StrE StrT: S "SEQ".u.CTRL.boStarting // request starting state R "SEQ".u.CTRL.boAborted // user program S "BEDA" S "ZGEA" // continue with starting state StrE: NOP 0

2.12.2.2 Execute and leave starting state It is displayed via the "SEQ".u.CTRL.bo, that the starting state is present. The input transition displays the end criterion for the starting state. After having left the starting state the running state is accepted.

The end criterion of the user program is the removal of the additional item. //--------------------------------------------------------------------- NETWORK TITLE = "Starting block" // TRANS "Starting" U "SEQ".u.CTRL.boStarting; UN "SEQ".u.STATUS.boUserBit; // userstate terminates starting block // leave starting FALSE SPB StgT // user program SPA StgE // make starting TRUE StgT: R "SEQ".u.CTRL.boStarting // leave starting state // user program // continue with run state StgE: NOP 0;

2.12.2.3 Running state The running state is always, if there aren't any other states.

The running state is left by:

Step complete transition (Complete)

Request Hold

Request Paused

Request Abort

Request Stop //--------------------------------------------------------------------- NETWORK TITLE = "Normal Run block" //TRANS run UN "SEQ".u.CTRL.boStarting UN "SEQ".u.STATUS.boEopStrt UN "SEQ".u.STATUS.boEopStp UN "SEQ".u.CTRL.boPaused UN "SEQ".u.CTRL.boPausing UN "SEQ".u.CTRL.boHeld UN "SEQ".u.CTRL.boHolding UN "SEQ".u.CTRL.boRestart UN "SEQ".u.CTRL.boRestarting UN "SEQ".u.CTRL.boAborted UN "SEQ".u.CTRL.boAborting UN "SEQ".u.CTRL.boStopped UN "SEQ".u.CTRL.boStopping // VKE // user program // actions when FALSE SPB RunT NOP 0 // user program SPA RunE // actions when TRUE RunT: NOP 0 // user program RunE: NOP 0

EPE as S7-FC Block


2.12.2.4 Enter paused state One signal is set on the signal "SEQ".u.CTRL.boPaused (Request Paused), in command to keep the paused state.

Setting the additional item is an example for the user program. //--------------------------------------------------------------------- NETWORK TITLE = "Reaction to Paused request" //TRANS "goto pausing" U "SEQ".u.CTRL.boPaused UN "SEQ".u.CTRL.boPausing // VKE SPB PsrT SPA PsrE PsrT: S "SEQ".u.CTRL.boPausing // user program S "SEQ".u.STATUS.boUserBit S "ZGEA" PsrE: NOP 0

2.12.2.5 Execute and leave paused state It is displayed via the bit "SEQ".u.CTRL.boPausing, that the Startend-state is present. The input transition displays the Pausing-state. After having left the Pausing-state, the Pausing-state is accepted.

The removal of the additional item is the end operation. //--------------------------------------------------------------------- NETWORK TITLE = "pausing block" // TRANS "Pausing" U "SEQ".u.CTRL.boPaused U "SEQ".u.CTRL.boPausing UN "SEQ".u.STATUS.boUserBit // user state terminates pausing state // actions when FALSE SPB PsgT // user program during pausing SPA PsgE; // actions when TRUE PsgT: R "SEQ".u.CTRL.boPausing // leave pausing state // user program // continue with pausing state PsgE: NOP 0

2.12.2.6 Execute and leave paused state The paused-state will leave the operation 'New start'. The following state is 'Run'. . //--------------------------------------------------------------------- NETWORK TITLE = "Paused block" // TRANS "Pausing" U "SEQ".u.CTRL.boPaused UN "SEQ".u.CTRL.boPausing U "SEQ".u.CTRL.boRestart // operator request restart (=termiante paused state) // leave paused FALSE SPB PsdT // user program during paused // continue with run state SPA PsdE // actions when TRUE PsdT: NOP 0 // user program when paused // user program PsdE: NOP 0

2.12.2.7 Enter Hold-state On the signal "SEQ".u.CTRL.boHold (Request Hold), the signal is set to keep the Hold-state.

Setting the additional items is an example for the user program. //--------------------------------------------------------------------- NETWORK TITLE = "Reaction to hold request" //TRANS "goto holding" U "SEQ".u.CTRL.boHeld UN "SEQ".u.CTRL.boHolding // VKE

EPE as S7-FC Block


A5E00239378-04

2-16

SPB HlrT SPA HlrE HlrT: S "SEQ".u.CTRL.boHolding // user program S "SEQ".u.STATUS.boUserBit S "ZGEA" HlrE: NOP 0

2.12.2.8 Execute and leave Hold-state It is displayed via the bit "SEQ".u.CTRL.boHolding , the Hold-state is present. The input transition displays the end criterion for the Hold-state. After having left the Hold-state 'Hold' is accepted.

In the example the end state is the removal of the additional item. //--------------------------------------------------------------------- NETWORK TITLE = "Holding block" // TRANS "Pausing" U "SEQ".u.CTRL.boHeld U "SEQ".u.CTRL.boHolding UN "SEQ".u.STATUS.boUserBit // user state terminates holding state // actions when FALSE SPB HlgT // user program during holding SPA HlgE // actions leaving Holding HlgT: R "SEQ".u.CTRL.boHolding // leave holding state // user program // continue with holding state HlgE: NOP 0

2.12.2.9 Leave held state The Held-state is left by the operation 'Restart'. The sequential state is 'Restartend'. If you keep the state 'Restartend', the bit "SEQ".u.CTRL.boRestarting must be set. //--------------------------------------------------------------------- NETWORK TITLE = "Held block" // TRANS "Held" U "SEQ".u.CTRL.boHeld UN "SEQ".u.CTRL.boHolding UN "SEQ".u.CTRL.boRestart // operator request restart (=termiante held state) UN "SEQ".u.CTRL.boRestarting // leave hold FALSE SPB HldT S "SEQ".u.CTRL.boRestarting // user program leaving hold S "SEQ".u.CTRL.boUserBit S "ZGEA" // continue with restarting state SPA HldE // actions when held TRUE HldT: NOP 0 // user program when held HldE: NOP 0

2.12.2.10 Leave restarting state It is displayed via the bit "SEQ".u.CTRL.boRestarting that there is the 'restarting'- state. The input transition displays the end criterion for the 'restarting'-state. After having left the Restarting-state the state Run is accepted.

In the example the removal of the additional item is the end state. //--------------------------------------------------------------------- NETWORK TITLE = "Restarting block" // TRANS "Pausing" U "SEQ".u.CTRL.boRestarting UN "SEQ".u.STATUS.boUserBit // user state terminates restarting state // actions when FALSE SPB RtgT // user program during restarting SPA RtgE // actions when TRUE RtgT: R "SEQ".u.CTRL.boRestarting // user program leaving restarting // continue with run state

EPE as S7-FC Block


RtgE: NOP 0

2.12.2.11 Enter stopping state On the signal "SEQ".u.CTRL.boStop (Request Stop), the signal is set to keep the stopping-state.

Setting the additional item is example for the user program. //--------------------------------------------------------------------- NETWORK TITLE = "Reaction to stop request" //TRANS "goto stopping" U "SEQ".u.CTRL.boStopped UN "SEQ".u.CTRL.boStopping // VKE SPB StpT SPA StpE StpT: S "SEQ".u.CTRL.boStopping // user program S "SEQ".u.STATUS.boUserBit S "ZGEA" StpE: NOP 0

2.12.2.12 Execute and leave stopping state It is displayed via the bit "SEQ".u.CTRL.boStopping, that there is the Stopping state. The input transition displays the end criterion for the Stopping state. After having left the Stopping state, the state stopped is accepted.

The removal of the additional item is the end operation. //--------------------------------------------------------------------- NETWORK TITLE = "Stopping block" // TRANS "Stopping" U "SEQ".u.CTRL.boStopped U "SEQ".u.CTRL.boStopping UN "SEQ".u.STATUS.boUserBit // user state terminates stopping state // actions when FALSE SPB StoT // user program SPA StoE // actions when TRUE StoT: R "SEQ".u.CTRL.boStopping // leave stopping state // user program // continue with complete StoE: NOP 0

2.12.2.13 Enter abort state On the signal "SEQ".u.CTRL.boAbort (Request Abort), the signal is set to keep the Abort-state.

Setting the additional item is an example for the user program. //--------------------------------------------------------------------- NETWORK TITLE = "Reaction to abort request" //TRANS "goto abort" U "SEQ".u.CTRL.boAborted UN "SEQ".u.CTRL.boAborting // VKE SPB AbtT SPA AbtE AbtT: S "SEQ".u.CTRL.boAborting // user program S "SEQ".u.STATUS.boUserBit S "ZGEA" AbtE: NOP 0

2.12.2.14 Execute and leave aborting state It is displayed via the bit "SEQ".u.CTRL.boAborting that a Aborting-state is present. The input transition displays the end criterion for the Aborting-state. After having left the Aborting-state, the 'Aborting' state is accepted.

In the example the removal of the additional item is the end operation. //--------------------------------------------------------------------- NETWORK

EPE as S7-FC Block


A5E00239378-04

2-18

TITLE = "Aborted block" // TRANS "Aborted" U "SEQ".u.CTRL.boAborted U "SEQ".u.CTRL.boAborting UN "SEQ".u.STATUS.boUserBit // user state terminates aborting state // actions when FALSE SPB AboT // user program SPA AboE // actions when TRUE AboT: R "SEQ".u.CTRL.boAborting // leave aborting state // user program // continue with complete AboE: NOP 0

2.12.2.15 Enter stop state The last network of the EPE has the state Stop. (Step complete transition).

The state is transferred by the BR (binary result).

2.12.3 Minimum extension The minimum extension of the EPE can only include the Run state and the step enabling state. In this case the EPE doesn't react to any state requests.

2.12.4 BRAUMAT/SISTAR Classic V5.3 Extension The structure includes:

Starting-branch

Running-branch

Held-branch

Restarting-branch

Completing-branch

2.12.5 Compatibility to V4.x You can continue to operate EOPs which is created with the Version V4.x without any re-configuration. These EOPs support only the states which are available in the Version V4.x.

2.13 Engineering of alternative branch for recipe To insert a alternative in the recipe procedure a specified EOP must engineered as alternative producer. This must be made in the recipe editor as well in the EOP engineering.

See also: Recipe system Configuration of the plant data

The EOP before the reicpe alternative must produce a result. The calculation of the result depends on the requested function. The result must be stored in the global byte MB 100.

The result is only checked, when the EOP leave the FC with the binary result BR=1.

Valid range for the alternative result: 1 - 255

2.14 Engineering of jumps in the recipe Only with PCUs of Type Simatic S7: To insert a jump in the recipe procedure a specified EOP must be engineered as label producer. This must be made in the recipe editor as well in the EOP engineering.

EPE as S7-FC Block


See also: Recipe system Configuration of the plant data

The EOP before the recipe jump must produce a result. The calculation of the result is plant specific. The result must be stored in the global variable 'SEQ.u.byAlterResult'.

If no according label to the result is found in the recipe unit procedure, the following step to the jump is executed. The jump is made in one PCU-cycle.

Valid range for the alternative result: 1 - 255

2.15 EOP followed by an AND synchronization If an EOP is followed by an AND synchronization, its processing may continue even though it has met the conditions for the next step.

Example:

Let us assume the step condition " U TUET" (next step when step monitoring time is reached) is assigned to the "Crushing" and "Mashing" EOPs. Let the "Crushing" monitoring time" be five seconds, but with a "Mashing" time of only three seconds. "Mashing" is therefore faster than "Crushing".

Resultant states :

EOP "Crushing" EOP "Mashing" Time index

[s]

GSTA GSTO S88-Status GSTA GSTO S88 status

0 1 0 Idle 1 0 Idle 1 0 0 Running 0 0 Running 2 0 0 Running 0 0 Running 3 0 0 Running 0 0 Running 4 0 0 Running 0 0 Completing 5 0 0 Running 0 0 Running 6 0

0 0 1

Completing Completing

0 0

0 1

Running Completing

As shown, processing of the "faster" EOP of the Braumat recipe system is continued until the "slower" EOP is also completed. This feature may be desirable for heating processes, i.e. if the temperature drops below the setpoint, heating must be restarted. The program logic of the EOP must be prepared to continue processing, regardless whether it has met the step condition.

Note: Recipe steps following a logical AND synchronizazion are not processed unless all EOPs participating in the synchronization process simultaneously report that they have met the conditions for the next step.

simatic automation system braumat/sistarclassic v5 ......preface, contents equipment operations and...

Documents