PCEquipmentLib 1.3-0 Engineering Guidelines 3BEL300674D8007 Rev A.pdf

8/10/2019 PCEquipmentLib 1.3-0 Engineering Guidelines 3BEL300674D8007 Rev A.pdf

1/177

ATPA IndustrialITSystem Program800xA - Process Control Equipment Library

Version 1.3-0

Engineering Guidelines


2/177


3/177

Engineering Guidelines

ATPA IndustrialITSystem Program800xA - Process Control Equipment Library

Version 1.3-0


4/177

NOTICE

The information in this document is subject to change without notice and should not be construed

as a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this

document.

In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages

of any nature or kind arising from the use of this document, nor shall ABB be liable for incidental

or consequential damages arising from use of any software or hardware described in this docu-

ment.

This document and parts thereof must not be reproduced or copied without written permission

from ABB, and the contents thereof must not be imparted to a third party nor used for any unau-thorized purpose.

The software or hardware described in this document is furnished under a license and may be used,

copied, or disclosed only in accordance with the terms of such license.

Copyright 1999 ABB

All rights reserved.

Release: Februar 2005

Document number: 3BEL300674D8007 Rev. A

TRADEMARKS

Registrations and trademarks used in this document include:

Windows Registered trademark of Microsoft Corporation.

ActiveX Registered trademark of Microsoft Corporation.

PostScript Registered trademark of Adobe Systems Inc.

Acrobat Reader Registered trademark of Adobe Systems Inc.

Industrial IT Trademark of ABB.


5/177

3BEL300674D8007 Rev. A 5

TABLE OF CONTENTS

About This BookUse of Warning, Caution, Information, and Tip Icons ....................................................11

Document Conventions ...................................................................................................12

Terminology.....................................................................................................................13

Related Product Guides ...................................................................................................16

Section 1 - IntroductionProduct Overview............................................................................................................17

New in this release ...............................................................................................21

Prerequisites and Requirements ......................................................................................22

Intended User...................................................................................................................22

Support ............................................................................................................................23

Section 2 - Equipment (Engineering Principles)

Introduction .....................................................................................................................25

EqBasicTemplate.............................................................................................................25

Functional overview.............................................................................................26

Faceplate overview...............................................................................................28

Control Module overview ....................................................................................30

EqBasicTemplate, Step by step instruction ..........................................................34

General rules for Parameters & data types...........................................................38

EqBasicTemplate parameters & data types..........................................................39

Section 3 - Phase & Unit (Engineering Principles)

Introduction .....................................................................................................................43

Process unit overview......................................................................................................43


6/177


7/177

Table of Contents

3BEL300674D8007 Rev. A 73BEL300674D8007 Rev. A 7

How to use Mode Of Operation ...........................................................................88

How to use MOP supervision alarm ....................................................................97

How to use States ...............................................................................................100

How to use Modes..............................................................................................102

How to use Priority Commands & Interlocks ....................................................104

User Permissions................................................................................................111

EqDeviceSummary Control Module Type ....................................................................112

Introduction ........................................................................................................112

How to use..........................................................................................................113

Logical Colors....................................................................................................114

EqModeControl Control Module Type..........................................................................115

Introduction ........................................................................................................115

How to use..........................................................................................................117

Appendix B - Batch Control Module Reference

pccOr4- pccOr16Batch Control Module Type ..............................................................121

Introduction ........................................................................................................121

How to use..........................................................................................................122

pccInhibitBatch Control Module Type ..........................................................................123

Introduction ........................................................................................................123How to use..........................................................................................................125

pccILockBatch Control Module Type ...........................................................................126

Introduction ........................................................................................................126

How to use..........................................................................................................129


pccThrowExecption Control Module Type ...................................................................131

Introduction ........................................................................................................131

How to use..........................................................................................................133

TaskPointer Control Module Type ................................................................................138

Introduction ........................................................................................................138

How to use..........................................................................................................141



8/177


9/177

3BEL300674D8007 Rev. A 9

Safety Summary3BEL300674D8007 Rev. A

SPECIFIC

CAUTIONS

Page 38 The contents of the IO-parameters must under no circumstances be read or

written from application logic. This can lead to unexpected activation of

devices. The parameters has to be connected to the equipment module.


10/177

10 3BEL300674D8007 Rev. A

Safety Summary


11/177

3BEL300674D8007 Rev. A 11

About This Book

Use of Warning, Caution, Information, and Tip IconsThis publication includes Warning, Caution, and Informationwhere appropriate

to point out safety related or other important information. It also includes Tipto

point out useful hints to the reader. The corresponding symbols should be

interpreted as follows:

Although Warninghazards are related to personal injury, and Cautionhazards are

associated with equipment or property damage, it should be understood that

operation of damaged equipment could, under certain operational conditions, resultin degraded process performance leading to personal injury or death. Therefore,

comply fully with all Warningand Cautionnotices.

Warning icon indicates the presence of a hazard which could result inpersonal

injury.

Caution icon indicates important information or warning related to the concept

discussed in the text. It might indicate the presence of a hazard which could

result in corruption of software or damage to equipment/property.

Information icon alerts the reader to pertinent facts and conditions.

Tip icon indicates advice on, for example, how to design your project or how to

use a certain function


12/177

Document Conventions About This Book

12 3BEL300674D8007 Rev. A

Document ConventionsThe following conventions are used for the presentation of material:

The words in names of screen elements (for example, the title in the title bar of

a window, the label for a field of a dialog box) are initially capitalized.

Capital letters are used for the name of a keyboard key if it is labeled on the

keyboard. For example, press the ENTER key.

Lowercase letters are used for the name of a keyboard key that is not labeled on

the keyboard. For example, the space bar, comma key, and so on.

Press CTRL+C indicates that you must hold down the CTRLkey while

pressing the C key (to copy a selected object in this case).

Press ESCECindicates that you press and release each key in sequence (to

copy a selected object in this case).

The names of push and toggle buttons are boldfaced. For example, click OK.

The names of menus and menu items are boldfaced. For example, the File

menu.

The following convention is used for menu operations: MenuName >

MenuItem > CascadedMenuItem. For example: select File> New> Type.

The Startmenu name always refers to the Startmenu on the WindowsTask Bar.

System prompts/messages are shown in the Courier font, and user

responses/input are in the boldfaced Courier font. For example, if you enter a

value out of range, the following message is displayed:

Entered value is not valid. The value must be 0 to 30.

You may be told to enter the string TIC132 in a field. The string is shown asfollows in the procedure:

TIC132

Variables are shown using lowercase letters.

sequence name


13/177

About This Book Terminology

3BEL300674D8007 Rev. A 13

TerminologyThe following is a list of terms associated with PCEquipmentLib that you should be

familiar with. The list contains terms and abbreviations that are unique to ABB or

have an usage or definition that is different from standard industry usage.

Term/Acronym Description

Devices Equals Control modulesas defined by IEC 61512,ANSI/ISA S88.01. Devices chosen in order not to mixControl Builder Control Modules with IEC 61512,ANSI/ISA S88.01Control Modules

Equipment module Several devices may be grouped to form an equipment module

as defined IEC 61512, ANSI/ISA S88.01.

This grouping of devices is useful when he devices are

working together and realizing finite number of basisfunctions.

Each device must only be part of one equipment module.

Mode of operation Different alternative technical function of the same equipment

module are named Mode Of Operation E.g.: Equipment for

temp. control, - mode of operation could be: Fixed setpoint,

ramping setpoint

MOP

See Mode Of Operation

PCC Priority Command Connection.

Name of PCDeviceLib data type used to connect input devices

to output devices in order to let process conditions on input

devices (like level alarms or abnormal signals) to activate

interlocks and priority commands on output devices.The output devices will contain an automatic generated

faceplate element with dynamic information about all the

input devices causing Priority Commands and Interlocks. The

faceplate also provides link to the faceplate of all the listed

devices.


14/177

Terminology About This Book

14 3BEL300674D8007 Rev. A

Interlock Command to a device or equipment which prevents the device

or the equipment from being command to a certain position

see also ILock0, ILock1, ILock2.

ILock0 Interlock 0. See also: PCC.

Command that prevents the device or equipment from

becoming closed/stopped.

ILock1 Interlock 1. See also: PCC.

Command that prevents the device from start/open or the

equipment to start.

PriCmd0 PriorityCommand0. See also: PCC.

Command to close/stop device or stop the equipment.

PriCmd1 PriorityCommand1. See also: PCC.Command to open/start device or start the equipment specific

PriCmd1 function.

PriCmd2 PriorityCommand2. See also: PCC.

Command to open/start device, or to start the equipment

specific PriCmd2 function.

PriCmdStopPriCmdAbort

PriCmdHold

PriCmdPause

PriCmdReset

PCC commands that can be sent to Produce IT Batch UnitsPhases or SharedEquipmentModules from PCDeviceLib input

devices in order to cause state change in the batch engine. See

also: Batch Control Module Reference, page 119.



15/177

About This Book Terminology

3BEL300674D8007 Rev. A 15

ILockStop

ILockAbort

ILockHold

ILockRestart

ILockResume

ILockStartILockReset

ILockPauset

PCC Interlocks used to prevent reentering the named state.

Can be sent from PCDeviceLib input devices to Produce IT

Batch Units Phases or SharedEquipmentModules. See also:

Batch Control Module Reference, page 119.

Task The control logic in one phase can be devided into several

tasks.

Each task defines valid point of restart after Hold



16/177


17/177

3BEL300674D8007 Rev. A 17

Section 1 Introduction

Product OverviewThis document is the Engineering Guideline for Process Control Equipment Library

(PCEquipmentLib).

The ATPA PCEquipmentLib has been prepared as a library for use within ATPA

BAUs.

PCEquipmentLib is a control builder library containing S88-equipment modules.

Implementation is done by means of Control Builder Professional Control Modules

Type, - no equivalent Function Block exists.

PCEquipmentLib can be used with or without 800xA Batch Management.

The BatchAdvTemplateLib defines a SharedEquipmentModuleTemplateControl

Module Type.

The SharedEquipmentModuleTemplateis notintended to be instantiated inside

Unit (UnitTemplate from BatchAdvTemplateLib).

PCEquipmentLibEquipmentmodules and BatchAdvTemplateLib

SharedEquipmentModuleTemplate is not the same !


18/177

Product Overview Section 1 Introduction

18 3BEL300674D8007 Rev. A

Figure 1. Definition of equipment in a process unit

PCEquipmentLib defines equipment modules at a level equal to the grouping in

Figure 1.

A device (valve, motor...) can only be a part of one equipment module.

The devices in an equipment module are working together, realizing one of severalbasis functions also calledMode Of Operations.

Examples ofMode Of Operationscan be:

Ramp Temp / Hold Temp

Add medium A / Add medium B

Pull vacuum / Release vacuum


19/177

Section 1 Introduction Product Overview

3BEL300674D8007 Rev. A 19

This encapsulation of devices in equipment modules makes reuse of device control

possible.

SameMode Of Operationcan be activated from different states in the

same phase (Running, Holding, Stopping).

SameMode Of Operationcan be used by several different phases inside a

unit.

Different types of process units can use the equipment module type.

By reuse means that each typeof equipment module only needs to be documented &

tested once before it is integrated in the application.

This reuse leads to:

Lower implementation time by minimizing document & test effort.

Common applications design concerning device control and exception

handling.

Common HSI on all equipment modules.

Equipment modules are highly customer specific.

Due to this, PCEquipmentLib is just as focused on the engineering process as well

as delivering specific equipment modules.

The focus on the engineering process can be demonstrated by some of the features

of PCEquipmentLib:

Able to produce graphical lists runtime containing: Devices, Equipment,

phases, process timers, request for operator input.

Modes, states as well as exception handling is contained in one control

module, in order to be reused in all equipment modules.

PCEquipmentLib are able to produce graphical presentation of the

exception logic driving phases/units or equipment modules.


20/177

Product Overview Section 1 Introduction

20 3BEL300674D8007 Rev. A

The Equipment module concept can be used in various ways:

Use case: Simple Phases

Each equipment module is encapsulated in one phase. This leads to larger,

more complex recipes but retains its flexibility.

Use case: Advanced Phases

Equipment modules and phases are implemented at the same level in the unit,

in order to allow one phase to control several equipment modules at the same

time.

Use case: Without 800xA Batch Management

The equipment modules are placed in the unit and no phases are present to

interface Produce IT.

Phase 1Equipment module (Discharging)

Unit

Equipment module (Temp. cont.)

Equipment module (Agitation)

Equipment module (Charging)

Equipment module (Discharging)

Phase 1

Phase 2

Unit





Unit


21/177

Section 1 Introduction New in this release

3BEL300674D8007 Rev. A 21

New in this release

No changes are done to existing functionality. PCEquipmentLib version 1.3-0 is

fully compatible with PCEquipmentLib version 1.2-0 and 1.2-1.

Description of functional changes is listed in PCEquipmentLib 1.3-0 Release Notes.

The following sections contains important updated or new information :

TaskPointer Control Module Type, page 138(new section)

Phase & Unit (Engineering Principles), page 43(rewritten due to presense of

templates)

Equipment (Engineering Principles), page 25(rewritten due to presense of

templates)

Faceplate Element List Of Devices, page 152(Data concerning expected callup

time added)
http://engguidelines.pdf/http://engguidelines.pdf/


22/177

Prerequisites and Requirements Section 1 Introduction

22 3BEL300674D8007 Rev. A

Prerequisites and RequirementsPCEquipmentLib is released and tested with:

Industrial IT 800xA System Version 4.0

Intended User

This engineering guideline is intended for the application programmer making

graphics as well as the control logic.

PCDeviceLib Version 4.0-0 has to be installed before installing PCEquipmentLib

PCEquipmentLib requires that system is created and the following system extensions are

loaded before installation

AC 800M/C Connect

Batch Management (Only necessary if batch management has to be used)

Batch Advanced Templates (Only necessary if batch management has to be used)

Good knowledge and understanding about PCDeviceLib is required, because

PCEquipmentLib is based upon PCDeviceLib and uses same terminology, parameternaming conventions, parameter usage as well as the PCC concept.


23/177

Section 1 Introduction Support

3BEL300674D8007 Rev. A 23

SupportPlease feel free to contact:

Lars Zwicky-Hauschild, ABB Denmark

By posting a mail to PCEquipmentLib Support@ABB_DK01

In case you: need to extend the functionality of PCEquipmentLib

need product support,

need to report errors,

need implementation of new languages,

want to become a registrated user (As an registred user you will recieve newlibrary versions).


24/177

Support Section 1 Introduction

24 3BEL300674D8007 Rev. A


25/177

3BEL300674D8007 Rev. A 25

Section 2 Equipment (Engineering Principles)

IntroductionThis section describes the implementation of equipment control modules by means

of the deliverable templates from PCEquipmentLib.

EqBasicTemplate

This section describes the functionality of the EqBasicTemplate as well as use ofEqBasicTemplate to create project specific equipment control module types.

TheEqBasicTemplatecontains

Pre configured faceplate containing operation and configuration.

Control Builder logic for modes, state and exception handling.

The implementation of the template is based on the control module types from

PCEquipmentLib and PCDeviceLib, - the changes required to build project specific

equipment modules are limited to:

Applying necessary device control associated with the various Modes Of

Operation

Applying input fields for equipment specific parameters in the faceplate.

The EqBasicTemplate can be downloaded to the controller in order to review

faceplate as well as Control Builder functionality.

l ( l )


26/177

Functional overview Section 2 Equipment (Engineering Principles)

26 3BEL300674D8007 Rev. A

Functional overview

EqBasicTemplateis build aroundEqCore(See EqCore Control Module Type, page 86)

as the central Control Module taking care of Modes, States and Mode Of Operation

States:The equipment module can be in 2 different states:

Running state

Stopped state

Mode Of Operation:

When inRunning statethe equipment module executes the selected Mode Of

Operation.

When in Stopped statethe equipment module executes the Mode Of Operation

Stopped (This can be configured).

Modes:The equipment module can be in 2 modes:

Automatic mode(change between running stateandstopped stateandselection ofMode Of Operationis controlled by logic)

Manual mode(change between running state and stopped state and

selection ofMode Of Operationis controlled by user from the faceplate)

TheEqBasicTemplateis configured to generate alarm if the completion of a selected

Mode Of Operation is not done within a time that can configured.

EqBasicTemplate is designed to contain all the devices used by the equipment

module. Any activation / deactivation of devices from the outside has to be done by

selecting an appropriate Mode Of Operation and followed by a start of the

equipment module. This makes it possible to automatic generate dynamic list of

devices in graphics, - as well as reuse the same equipment Control Module several

places in the application.

Mode Of Operationis an integer. The described principles can be extended to

cover any equipment. This makes it possible to implement a common user- as

well as application interface to all kinds of equipment modules.

S ti 2 E i t (E i i P i i l ) F ti l i


27/177

Section 2 Equipment (Engineering Principles) Functional overview

3BEL300674D8007 Rev. A 27

EqBasicTemplate contains a totalizer, transmitter and a Valve from PCDeviceLib.

This is done in order to demonstrate common use. The use of these devices areintegrated in the various Mode Of Operations.

The following use of devices are implemented.

Valve:

Activation / deactivation and use of feedback

Transmitter: Expose the transmitter value to the outside of the equipment module as an

InteractionPar element (To let other equipment modules or phases use the

value).

Expose the transmitter HH condition as a PCC connection (To

demonstrate how an internal condition can trigger other equipment

modules or phases). Transmitter + Totalizer:

How to connect and use a totalizer as well as exposing the totalized value

outside of the equipment (To let other equipment modules or phases use

the value).

EqBasicTemplate is configured to force mode on all devices to Automatic during

start.Concerning Exception handling the PCC concept is used internally to prevent start

(Interlock1) if any of the contained devices is not controllable from application

(Local mode, Object Error etc. active).EqBasicTemplate has a PCC input command

in order to be able to respond to external exceptions. EqBasicTemplate is configured

to activate the StoppedMode Of Operation if any Priority Command is received.

Faceplate overview Section 2 Equipment (Engineering Principles)


28/177

Faceplate overview Section 2 Equipment (Engineering Principles)

28 3BEL300674D8007 Rev. A

Faceplate overview

The Faceplate & Extended Faceplate presented below illustrates how the different

control modules can be utilized implementing the faceplate of an equipment

module. The numbered items in the figure are all items inherited from

PCEquipmentLib, - and do not require further engineering.

Figure 2. EqBasicTemplate: Faceplates

5) 6)

7)

8)

4)

9)

2)

1)

3)

Section 2 Equipment (Engineering Principles) Faceplate overview


29/177

Section 2 Equipment (Engineering Principles) Faceplate overview

3BEL300674D8007 Rev. A 29

Ad 1, Figure 2, page 28)

Status and indication icons: All connected to OPC variable in the Control

Module Type EqCore.


Configuration of Mode Of Operation supervision alarm.


Command buttons: All connected to OPC variables in the Control ModuleType EqCore.


Link to Alarm & Event list, summarizing all alarms and events for the

equipment module and contained devices.


Presentation and inhibit as well as Priority Commands and Interlocks. See How

to use Priority Commands & Interlocks, page 104.


Presentation and link to all devices controlled by the equipment module. See

Faceplate Element List Of Devices, page 152.


Presentation and selection of Mode Of Operation. See How to use Mode Of

Operation, page 88.


Presentation of summarized status information for all devices controlled by the

equipment module. See EqDeviceSummary Control Module Type, page 112.


Configuration of PCC and Stop linkage to Mode Of Operations.

Control Module overview Section 2 Equipment (Engineering Principles)
http://engguidelines.pdf/http://engguidelines.pdf/


30/177


30 3BEL300674D8007 Rev. A

Control Module overview

This section describes the overall structure of theEqBasicTemplatecontrol module

type.

The Figure EqBasicTemplate: Control Builder overview, page 30, The following

references describe in details the overall structure.

Figure 3. EqBasicTemplate: Control Builder overview

Some of the screen dumps show the implementation by means of the CMD-editor

(Control Builder Professional Graphic Editor for Control Modules). Use of the

CMD editor is not mandatory.

1)2)

3)

4)

5)

6)

7)

8)

9)


31/177



32/177

32 3BEL300674D8007 Rev. A

Ad 7,Figure 3, page 30:

The equipment module has PCC input parameter in order to be able to

respond to exception commands.


Exposure of HH condition from the transmitter as a PCC command in

order to demonstrate how condition inside the equipment module can

drive external PCC modules.


If any of the contained devices is not controllable from logic, start of the

equipment module is prevented by raising aInterlock1. This is done in

order to demonstrate how to collect and convert a boolean expression to a

PCC command.


33/177

EqBasicTemplate, Step by step instruction Section 2 Equipment (Engineering Principles)


34/177

34 3BEL300674D8007 Rev. A

EqBasicTemplate, Step by step instruction

This section describes the overall steps necessary to create an equipment module by

means of the templateEqBasicTemplateform PCEquipmentLib

How to create new equipment Control Module from template

1. Create and/or open a project specific Control Builder Library (ProjectEqLib).

2. Connect the librariesBasicLib, PCDeviceLib, PCDeviceSupportLibandPCEquipmentLib toProjectEqLib.

3. Copy the Control Module TypeEqBasicTemplatefromPCEquipmentLibto

ProjectEqLib.

4. Rename the copyEqBasicTemplateto an appropriate name (NewEq).

5. Copy the data typesEqBasicPar, EqBasicIO andEqBasicDevicesParfrom

PCEquipmentLibtoProjectEqLib.6. Rename the copy ofEqBasicPar, EqBasicIO andEqBasicDevicesPar to

appropriate names (NewEqPar, NewEqIOandNewEqDevicesPar).

7. Replace the data typesEqBasicPar, EqBasicIO,EqBasicDevicesParwith

NewEqPar, NewEqIO,NewEqDevicesPar on variables and parameters in

NewEq.

Section 2 Equipment (Engineering Principles) EqBasicTemplate, Step by step instruction


35/177

3BEL300674D8007 Rev. A 35

How to populateNewEqwith devices (valves, motors etc.)

1. OpenNewEq, Deleteand/or Replace Control Module Typeon the Valve1,

TotalizerRealIO, TransmitterControl Module. Createthe remaining

PCDeviceLib devices which have to be controlled by theNewEqequipment

module.

2. Update theNewEqIOdata type with the IO-data type for all devices in the

NewEqequipment module

3. Update theNewEqDevicesPardata type with the xxxPar data type for all

PCDeviceLib devices in theNewEqequipment module

4. Open theNewEqcode tabDeviceStatus_st and complete programming as

described in the code tab.

5. Open the CMD editor forNewEq andzoom to level 2 bypressing Ctrl Num

+ and resolve any errors (Due to delete of Transmitter,

TotalizerRealIO1,Valve1)

6. Connect the parameterNewEqIO.xxxto the IO parameter on all devices.

7. Connect each element of the local variableDevPar to the parameter

InteractionParon the associated PCDeviceLib device.

8. Apply appropriate unique Name and Description on all contained

PCDeviceLib devices (If theEqNewControl Module Type is going to be used

several times in the application, - expose each deviceNameparameter as an

NewEq Parameter).

9. Update the Control Builder configuration of each device in accordance with

project requirement.

EqBasicTemplate, Step by step instruction Section 2 Equipment (Engineering Principles)


36/177

36 3BEL300674D8007 Rev. A

How to extent the Mode Of Operations.

1. Open theMOP_sfccode tab in theEqNewControl Module (Figure 5).

2. Create one branch below stepsIdlefor each Mode Of Operation (use Figure 5

ref. A as template).

3. Extent each branch with the required number of steps and transitions.Observe

that stepxxx_Complete(Figure 5, ref. B) is kept as the last step and trFalsex is

kept as the last transition with transition criteria = False.

4. (Figure 5ref. C) The P1code tab of First step in each branch (e.g.

sMOP_stopping,sMOP2_Active). Put all devices in a inactive/safe position

(Also those not used by this Mode Of Operation)

5. Complete the control of device (use theP1/P0code tabs in order to avoid

loops).

Figure 5. EqBasicTemplate: Mode Of Operation SFC

A)

B)

C)

Section 2 Equipment (Engineering Principles) EqBasicTemplate, Step by step instruction


37/177

3BEL300674D8007 Rev. A 37

How to define Mode Of Operation texts.

1. See Faceplate Elements building blocks (ModeOfOperation), page 94

How to control man-/auto mode of device during equipment starts

1. Open the connection list for theEqModeControlControl Module.

2. Apply an appropriate value to the parameter TrackModeConf(Ref.

EqModeControl Control Module Type, page 115).

3. Open thecode tabModeControl_st and complete programming as described in

the code tab.

How to configure PCC (Exception handling and associated Mode of operation):

1. Open the connection list on theEqCoreControl Module.

2. Verify that the settings on the parametersMOPPriCmdMan0Conf,MOPPriCmd0Conf, MOPPriCmd1Conf andMOPPriCmd2Conf is a correct

Mode Of Operation response to the associated Priority Commands

How to finalize Faceplate & graphic configuration

1. Open thefaceplate elementEqControl andParameters and apply equipment

specific data.2. Deploy all graphic aspects on theNewEqControl Module

General rules for Parameters & data types Section 2 Equipment (Engineering Principles)


38/177

38 3BEL300674D8007 Rev. A

General rules for Parameters & data types

The parameters of an equipment module are divided into a number of structured

data types as well as simple parameters depending of their purpose.

Rule 1:

Parameters of simple data types like, boolean, integer, strings etc. are for

configurationof the equipment. They must notbe used in application

logic.

The parameters are kept at simple data types in order to allow

configuration by means of Bulk Data Manager.

Rule 2:

The parameter with the name IO is intended to be connected to the IO.

The data type shall be specific to the equipment module and has to contain

all the IO data types for the devices contained in the equipment module.

Rule 3:

The InteractionPar parameter shall contain all status information and

commands that can be used in application logic.

The data type should be specific to the equipment module.

The InteractionPar data type should as a minimum have the parameters

described in EqBasicTemplate: Common elements in the InteractionPar

data type, page 40.

The contents of the IO must under no circumstances be read or written from

application logic. This can lead to unexpected activation of devices.

Section 2 Equipment (Engineering Principles) EqBasicTemplate parameters & data types


39/177

3BEL300674D8007 Rev. A 39

Rule 4:

The data direction on parameters must be obeyed:

IN parameters Write Onlyfrom logic.

OUT parameters Read onlyfrom logic.

EqBasicTemplate parameters & data types

TheEqBasicTemplatecontrol module type have the following parameters and datatypes are intended to be the same on all equipment modules.

Table 1. EqBasicTemplate: Common parameters

Name Data type Description

Name string[14] IN EDIT Name of the equipment module. Edit For Alarm

Description string[30] IN Equipment description

AEClass Dint IN EDIT Class, used for all Alarms/Events, from 1 to 9999.

Edit for Alarm

InteractionPar EqBasicPar IN OUT Runtime interaction parameters to/from logic or

devices

IO EqBasicIO IN OUT Input & Output Signals, connect to hardware, do not

use in logic

PCC PCC IN NODE PriorityCommand/Interlock to equipment module


40/177

Section 2 Equipment (Engineering Principles) EqBasicTemplate parameters & data types


41/177

3BEL300674D8007 Rev. A 41

Table 3. EqBasicTemplate: Common elements in the Modes data type


AutoStat Bool OUT True = Equipment module is in Automatic mode (Connect to EqCore)

ManStat Bool OUT True = Equipment module is in Manual mode (Connect to EqCore)

LockAuto Bool IN True = Mode is changed and locked to Automatic mode. Connect toEqCore.

LockMan Bool IN True = Mode is changed and locked to Manual mode. Connect to EqCore.

Inh Bool IN True = Suppress any Priority Commands and Interlocks. Connect to

EqCore.

InhStat Bool OUT True = Priority Commands and Interlocks are suppressed from

application or from faceplate by the operator. Connect to EqCore.

PriCmdStat Bool OUT True = One PriCmdMan0, PriCmd0, PriCmd1, PriCmd2 is active.

Connect to EqCore.

ILockStat Bool OUT True = One of the ILock0 or ILock1 is active. Connect to EqCore.

Test Bool IN True = activate Test mode on all devices controlled by the equipment

module. (To be connected to the InteractionPar.Modes.Test on the

PCDeviceLib devices)

EqBasicTemplate parameters & data types Section 2 Equipment (Engineering Principles)


42/177

42 3BEL300674D8007 Rev. A


43/177

3BEL300674D8007 Rev. A 43

Section 3 Phase & Unit (Engineering Principles)

IntroductionThis section describes the implementation of Phase & Unit control modules by

means of the deliverable template from PCEquipmentLib.

Process unit overview

At the moment PCEquipmentLib does not contain a process unit template.

This section describes the proposed structure in units where each phase controls

several equipment modules.

A)

B)

C)

D)

Process unit overview Section 3 Phase & Unit (Engineering Principles)


44/177

44 3BEL300674D8007 Rev. A

Figure 6. Process unit: overview

The Figure 6, ref. A) process unit contains one phase and one equipment control

module as child control modules to the unit (Figure 6, ref. B, C). This is done in

order to let each phase control multiple equipment modules at the same time (see

also Figure 7).

Control of the equipmentEq1fromPhase1is done by connecting the Figure 6, ref.

D) parameterInteractionParfrom the equipment to the phase.Control ofEq1is done by means of theEq1Par.Cmd1andEq1Par.MOP(Mode Of

Operation).

Figure 7. Unit overview: Multiple equipment control





Phase 1

Phase 2

Unit

Section 3 Phase & Unit (Engineering Principles) PhaseBasicTemplate


45/177

3BEL300674D8007 Rev. A 45

PhaseBasicTemplate

This section describes the functionality of thePhaseBasicTemplateas well as use of

PhaseBasicTemplateto create project specific phase control module types.

Functional overview

PhaseBasicTemplateis based on thePhaseTemplatefromBatchAdvTemplateLibbut

extended with the offerings fromPCEquipmentLib. Status indication, buttons etc. as

configured from BatchAdvTemplateLib is left unchanged.

ThePhaseBasicTemplatecomes with pre configured faceplate

ThePhaseBasicTemplatedemonstrates how to:

Implement process timers.

Implement prompts.

Implement Phase restarting points (Tasks. See also Terminology, page 13).

Transfer of phase parameters to the equipment module.

Control of equipment modules (See Equipment (Engineering Principles), page

25)

Implement BatchPCC exception handling and related equipment control.


46/177

Section 3 Phase & Unit (Engineering Principles) Control Module Overview


47/177

3BEL300674D8007 Rev. A 47

Control Module Overview

Purpose of sub control modules

This chapter describes the overall structure of an phase control module.

The figure below shows the structure of thePhaseBasicTemplatecontrol module.

Figure 9. PhaseBasicTemplate: Control module overview

The purpose of the varius control modules and function blocks are as follows:

Figure 9,Core: Controls S88 states of the phase and interfaces the

BatchManager. Part ofProduceITLib.

Figure 9,ILockBatch: To demonstrate integration of BatchPCC.ILockBatch:

module transfers batch PCC interlocks to the Corecontrol module. See also:

pccILockBatch Control Module Type, page 126.

Some of the screen dumps show the implementation by means of the CMD-editor

(Control Builder M Professional Graphic Editor for Control Modules). Use of the

CMD editor is not mandatory.

Control Module Overview Section 3 Phase & Unit (Engineering Principles)


48/177

48 3BEL300674D8007 Rev. A

Figure 9,pccExceptionBatch: To demonstrate integration of BatchPCC. The

pccExceptionBatchlaunches a Hold exception when PCC Hold command isrecieved.

Figure 9, TaskPointer: To demonstrate use of the taskpointer / restarting

concept. See description later in this chapter, see also TaskPointer Control

Module Type, page 138.

Figure 9,PromptNotReady:

To demonstrate the use of prompts.

This prompt might be activated during the first phase transition fromIdle

toRunning. The prompt is activated if the equipment module is in

Interlock / Priority Command or Manual mode. The prompt infoms the

operator that one of the used equipment modules is out of phase control.

The operator can then fix the problem before acknowledge and thereby

continue the phase execution. The equipment module will apply a ILock1

(= Interlock Start) if one of the devices in equiopment module is out ofequipment control = in Local, has Object Error, Forced IO ect.

Control of the prompt is done in theRunningSFC stepsInitialize.

See also Prompts (Engineering Principles), page 59.

Figure 9,ProcessTimer: To demonstrate the use of Process timers.

Control of the process timer is done in theRunningSFC, SubsequenceTask 2. See also Timers (Engineering Principles), page 69.

Figure 9,ProcessTimeSP: To demonstrate the transfer of phase parameter to

the process timer. Assignment is done in theRunningSFC stepsInitialize.

Figure 9, SP: To demonstrate the transfer of phase parameter to equipment

module. Assignment is done in theRunningSFC stepsInitialize.

Figure 9, TerminateState: Controls S88 states and interfaces the BatchManager.Part of ProduceITBatchLib

Figure 9, StorePDL: To demonstrate how to save batch related runtime data in

the PDL structure of the Information manager from control logic. Activation of

the function block is done in the theRunningSFC subsequence

PhaseComplete.



49/177

3BEL300674D8007 Rev. A 49

Code tab usage

This describes the purpose and usage of the various code tabs in thePhaseBasicTemplate.

Figure 10. PhaseBasicTemplate: Code tab purpose

Figure 10, ref. A) executes once during application startup. Used to create and

assign unique names to sub control module. Control network unique names are

required for control modules containing alarms or participating in PCC (control

module name prefixed withPCC).

A) B) C)

D)E)



50/177

50 3BEL300674D8007 Rev. A

Figure 10, ref. B)

The structure of theRunningcode tab is described in details later.

Common for Figure 10, ref. B & C)

One code tab for each of the asociated S88 states.

The code tab will be activated onlywhen the associated S88 state is

active.

The use of all states is not mandatory. The code taps for unused S88 statescan be deleted.

Figure 10, ref. D) The aborting logic should be left empty without any kind of

logic at all, - in order to give the operator a backdoor which terminates the

phase unconditionally.

Figure 10, ref. E) TheMonitorcode tab is a container to be used by the project

for logic that needs to be executed contineously when the phase is eitherIdleorNot Idle.



51/177

3BEL300674D8007 Rev. A 51

SFC structure in the Running Code tab

This section describes purpose with the structure of the Figure 11, SFC in theRunningcode tab.

Figure 11. PhaseBasicTemplate: SFC Structure in the Running code tab

Figure 11,ref. A) The moment the phase is started either from its faceplate or

through the batch manager, - theRunningcode tab is enabled and execution

will start from thesRunningEmpty Step. The branch in Ref. A) ensures that

sInitializeis only executed the first time the phase is started and not after a

Restart (after Hold).

A)

B)

D)

C)



52/177

52 3BEL300674D8007 Rev. A

Figure 11, ref. B) The stepsInitializeis intented to be used to conduct checks

the first time the phases starts (such as condition of devices etc.) in order todocument as well as inform the operator that actions is needed before the phase

is able to start. In thePhaseBasicTemplatethe stepsInitializeis used to verify

that the equipment module is not prevented from being controlled by the phase

due to active interlocks or priority commands. If the phase is out of control of

the equipment module a prompt is launced (In order to allow the operator to

resolve any problems before letting the phase continue. The phase will

continue when the operator acknowledge the prompt, - even if the problem

remains).

Figure 11, ref. C) TheRunningSFC are broken into subsequences each

representing a proper restarting point after Hold. This breaking into

subsequences looks parallel it is sequential as the arrow indicates. This

means that Task1will be executed prior to Task2which will be executed prior

toPhaseComplete. To work with restarting points see TaskPointer Control

Module Type, page 138


53/177

General rules for parameters & data types Section 3 Phase & Unit (Engineering Principles)

G l l f t & d t t


54/177

54 3BEL300674D8007 Rev. A

General rules for parameters & data types

The parameters of an equipment phase control module are divided into a number ofstructured data types as well as simple parameters depending of their purpose. The

same rules apply for PCDeviceLib.

Rule 1:

Parameters of simple data types like Boolean, integer, string etc. are for

configuration of the equipment phase. They are not intended to be used

runtime from application logic.

The parameters are simple data types in order to allow configuration using

the BulkDataManager.

Section 3 Phase & Unit (Engineering Principles) PhaseBasicTemplate, Step by step instruction

PhaseBasicTemplate Step b step instr ction


55/177

3BEL300674D8007 Rev. A 55

PhaseBasicTemplate, Step by step instruction

This section describes the overall steps necessary to create a phase module bymeans of the templatePhaseBasicTemplateformPCEquipmentLib

How to create new phase from template

1. Create and/or open a project specific Control Builder Library

(ProjectPhaseLib).

2. Connect the librariesBasicLib, PCDeviceLib, PCDeviceSupportLibandPCEquipmentLib, ProduceITBatchLib toProjectPhaseLib.

3. Copy the control module typePhaseBasicTemplatefromPCEquipmentLibto

ProjectPhaseLib.

4. Rename the copyPhaseBasicTemplateto an appropriate name (NewPhase).

5. Add parameters to theNewPhase control module, one for each equipment

module to be controlled by theNewPhase(Same principle as for theEq1Par

parameter).

6. Delete the parameterEq1Par.

7. Delete the use of Eq1Par from theRunningcode tab.

8. Apply the required batch parameters through theBatchPhaseaspect.

PhaseBasicTemplate, Step by step instruction Section 3 Phase & Unit (Engineering Principles)

How to extend the phase running logic


56/177

56 3BEL300674D8007 Rev. A

How to extend the phase running logic.

1. Open theRunningcode tab in theNewPhsse Control Module (Figure 13).

2. Create one subsequence below stepsTaskSwitchfor each Task.

3. Extend each subsequence with the required number of steps and transitions.

Figure 13. EqBasicTemplate: Mode Of Operation SFC

Section 3 Phase & Unit (Engineering Principles) PhaseBasicTemplate, Step by step instruction

How to define TaskPointer texts


57/177

3BEL300674D8007 Rev. A 57

How to define TaskPointer texts

1. See Faceplate Elements building block (TaskPointer Interaction), page 144

How to configure PCC

1. In the unit, connect the PCC inputs (Alarm limits from transmitters, digital

inputs, equipment modules etc.) to theNewPhaseparameterPCC.

2. Ensure that PCC inputs are configured to send PriCmdHold ( = connected to

the project constant cPCEqPublic.RO.BatchPCC.PriCmdHold).

3. Ensure that sufficient control of equipment modules is applied inHoldingcode.

How to finalize Faceplate & graphic configuration

1. Deploy all graphic aspects on theNewPhaseControl Module.

PhaseBasicTemplate, Step by step instruction Section 3 Phase & Unit (Engineering Principles)


58/177

58 3BEL300674D8007 Rev. A


59/177

3BEL300674D8007 Rev. A 59

Section 4 Prompts (Engineering Principles)

Introduction

This section describes how to use the prompt concept to:

Automatically present the request for operator action in faceplates or graphic.

Retrieve operator input, based on control logic conditions.

Use the retrieved operator input in the control logic

Prompts

Sorted by time Show all

Weigh and add xxx to yyy. Enter amount:

Description...

Description...

Description...

...

Introduction Section 4 Prompts (Engineering Principles)

The prompt concept consists of the:


60/177

60 3BEL300674D8007 Rev. A

Control Module Type Prompt.

Aspect Faceplate Element List Of Prompts.

The Control Module Type Prompt can be configured to:

generate alarm when operator action is required.

request for different kinds of input:

One button (Ok / Acknowledge)

Two buttons (Yes, No, Approve, Reject, Ok, Cancel)

Input field for real number, with range check and Ok button.

The Aspect Faceplate Element List Of Prompts can be used in Faceplates or

Graphics in order to show all prompts in the Control Structure below the Objectcontaining the AspectFaceplate Element List Of Prompts.

The use of these elements is described in details in the following sections.

Section 4 Prompts (Engineering Principles) Control Module Type Prompt

Control Module Type Prompt


61/177

3BEL300674D8007 Rev. A 61

yp p

Description

This Control Module is used to represent and configure the prompt inside the

Control Builder application.

To present prompts in faceplates or Process Graphic see How to Use, page 68

Figure 14. Logic Diagram, Control Module Type Prompt

Activation of Reject Button

InteractionPar.ShowPrompt

InteractionPar.RejectStat

InteractionPar.PromptWaitingStat

Activation of Ack. Button InteractionPar.AckStat

InteractionPar.InputVal

&

=>

&

Operator Real Input

Input Output

&

NameMsg

AEConf

AEClass

AESev

&

Alarm

How to Use Section 4 Prompts (Engineering Principles)

How to Use


62/177

62 3BEL300674D8007 Rev. A

Create an instance of the Control Module Type Prompt at the desired position in theapplication. Use structured data typeInteractionParto activate / deactivate the

prompt and to read the value entered by the operator.

Integration of an instance of the Prompt Control Module Type in an application can

be done as shown in Figure 15below.

Figure 15. Integration of Prompt Control Module Type in application

The name of the Prompt Control Module (Contents of name parameter). Has to

be unique. If not the alarm launched by the Prompt module will not work

Prompt

Control

module

Attract Attention Code (if needed)

InteractionPar

Alarmlist (filtered for prompts)...date&time NameY Prompt message Y...

.ShowPrompt := On

.ShowPrompt := Off

Step

n

.AckStat Tr n+1

Control

builder

sequence

.RejectStat Tr n+1

=>

...

.PromptWaitingStat

...

AttentionToPrompts

Prompt message X

Prompt message Y

Prompt message Z

NameYPrompt message Y

Ack Reject

1.00Value: Unit

ooo ooo

Section 4 Prompts (Engineering Principles) Parameters & Data types

Parameters & Data types


63/177

3BEL300674D8007 Rev. A 63

Table 4. Prompt Control Module Type Parameters

Parameter Name Datatype Description

Name string[20] IN EDIT Name of the prompt module

InteractionPar PromptPar IN OUT Runtime interaction parameters to/from logic

Description String[40] IN Prompt message to operator (e.g. Prepare P-5510AB) presentedin faceplate and the in alarm

AEConf Dint IN EDIT Prompt Alarm Conf (0=Alarm disabled, 1=Alarm

generated when prompt becomes active)

AEClass Dint IN EDIT, Class for Alarm from 1 to 9999

AESev Dint IN EDIT Severity Alarm, from 1 to 1000

PromptTypeConf Dint IN Type of prompt.

0=One button will be present. Text on button controlled by

parameter AckButtonTxtConf

1=Real input field and Acknowledge will be present. Text on button

controlled by parameter AckButtonTxtConf

2=Two buttons. Text on button controlled by the parameters

AckButtonTxtConf and RejectButtonTxtConf

SortOrder Dint IN Sort order in faceplate (ascending) when several prompts are

shown

Max Real IN Max allowed value entered by operator in the faceplate when

PromptTypeConf = 1

Min Real IN Min allowed value entered by operator in the faceplate when

PromptTypeConf = 1

Fraction Dint IN Number of decimals shown on real input field in the faceplate

when PromptTypeConf = 1

Unit String[10] IN Unit for value entered by operator in the faceplate when

PromptTypeConf = 1

Parameters & Data types Section 4 Prompts (Engineering Principles)

Table 4. Prompt Control Module Type Parameters


64/177

64 3BEL300674D8007 Rev. A

AckButtonTxtConf Dint IN Label for the acknowledge button. The numbers 1-10 determine

which of the following NLS entries to show:

Prompt_Txt01_Ack,

Prompt_Txt02_Reject,

Prompt_Txt03_Ok,

Prompt_Txt04_Cancel,

Prompt_Txt05_Yes,

Prompt_Txt06_No,

Prompt_Txt07_Confirm,

Prompt_Txt08_Spare,

Prompt_Txt09_Spare,

Prompt_Txt10_Spare.

RejectButtonTxtConf Dint IN Label for the Reject button. The numbers 1-10 determine which

of the following NLS entries to show:

Prompt_Txt01_Ack,

Prompt_Txt02_Reject,

Prompt_Txt03_Ok,

Prompt_Txt04_Cancel,

Prompt_Txt05_Yes,

Prompt_Txt06_No,

Prompt_Txt07_Confirm,

Prompt_Txt08_Spare,

Prompt_Txt09_Spare,

Prompt_Txt10_Spare.


Section 4 Prompts (Engineering Principles) User Permissions

User Permissions


65/177

3BEL300674D8007 Rev. A 65

The internal variables listed in the table are updated from faceplate by user.

The input / activation from faceplate will be disabled if security is activated and user

dont have the listed permissions.

If the permission / authentication configuration is insufficient. The permission

association can be overruled by applying and configuring the Property Attribute

Override Aspect on:

The Control Module Type in the Object Type Structure to override the permissions

on all instances.

The instance in the Control Structure to override permissions on the instance.

Table 5. Prompt User permissions

Variable Permission Description

HSIAck Operate Acknowledge button activated by the operator

HSIReject Operate Reject button activated by the operator

HSIInput Operate Real value entered by the operator


66/177

Section 4 Prompts (Engineering Principles) Introduction

When used the faceplate element will display the following information.


67/177

3BEL300674D8007 Rev. A 67

Figure 17. Faceplate Element List Of Prompts.

The faceplate element supports two different views of the prompts, selected radio

buttons Show Alland Sorted By Time. Interaction with the radio buttons is not

restricted by any permissions.

The radio button Show Allwill display both prompts waiting for operator

acknowledge as well as prompts which are inactive or acknowledged. This setting

can be used during commissioning to verify the configuration.

The radio button Sorted by timewill only display prompts waiting for operator

acknowledge. The Prompts will be sorted by the time, where the request foroperator acknowledgement became active.

Prompts

Sorted by time Show all

Weigh and add xxx to yyy. Enter amount:

Description...

Description...

Description...

...


68/177


69/177

3BEL300674D8007 Rev. A 69

Section 5 Timers (Engineering Principles)

Introduction

This section describes how to use the Timer concept to:

Automatically present process timers in faceplates or graphic.

Use the process timers in the control logic

Introduction Section 5 Timers (Engineering Principles)

The process timer concept consists of the:

C t l M d l T E Ti ith f l t f l d t ti


70/177

70 3BEL300674D8007 Rev. A

Control Module TypeEqTimerwith faceplate for manual and automaticoperation.

AspectFaceplate Element List Of Timers.

The Control Module TypeEqTimercan be configured to:

Count up endless or count up/down from preset time.

Generate alarm or event when the preset time have elapsed.

Generate events when the process timer is started, stopped and reset

The AspectFaceplate Element List Of Timerscan be used in Faceplates or Graphics

in order to show all Process Timers in the Control Structure below the Object

containing the AspectFaceplate Element List Of Timers.

The use of these elements is described in details in the following sections.

Section 5 Timers (Engineering Principles) Introduction

The faceplates use the following icons for presentation:


71/177

3BEL300674D8007 Rev. A 71

Table 6. Faceplate Element List Of Devices Icons

Icon Description

Manual Mode button or status indication

Locked in Manual status indication

Automatic Mode button or status indication

Locked in Automatic status indication

Count down from preset time button or status indication

(Parameter TimerType = 1)

Count up to preset time button or status indication


Count up endless button or status indication


Introduction Section 5 Timers (Engineering Principles)

Table 6. Faceplate Element List Of Devices Icons

I D i ti


72/177

72 3BEL300674D8007 Rev. A

Stop timer button or status indication

Reset button or status indication

Icon Description


73/177

Description Section 5 Timers (Engineering Principles)

Start, Stop and reset of timer depending on mode and timer type is done as described

in Figure 20


74/177

74 3BEL300674D8007 Rev. A

Figure 20. EqTimer, Logic diagram for timer control

IPar.PTIPar.CompleteStat

HSIResetIPar.Reset

>=

>=IPar.ET

TimerStart

TimerReset IPar.ResetStat

&

HSICmd0

IPar.Cmd1Stat

>=

SR

IPar.Cmd1

&

IPar.HSICmd1IPar.Modes.ManStat

&

IPar.Modes.AutoStat

&

>=

&

IPar.Modes.ManStat

IPar.Modes.AutoStatIPar.Cmd1

&

3TimerType

IPar.PT -

Elapsed

Time IPar.ET

IPar.RT

IPar.CompleteStatIPar.Cmd1Stat


75/177

How to Use Section 5 Timers (Engineering Principles)

The name of theEqTimerControl Module (Contents of name parameter). Has tobe unique If not the alarm launched by the EqTimer module will not work


76/177

76 3BEL300674D8007 Rev. A

be unique. If not the alarm launched by theEqTimermodule will not work

Section 5 Timers (Engineering Principles) Parameters & Data types

Parameters & Data types


77/177

3BEL300674D8007 Rev. A 77

Table 7. EqTimer Control Module Type Parameters


Name string[20] IN EDIT Name of the Timer. Edit For Alarm

Description string[40] IN Timer description for faceplate

InteractionPar EqTimerPar IN OUT Runtime interaction parameters to/from logic (See Table 8

page 78)

AEAckRule Dint IN EDIT Timer AEAcknowledge rule. 1=Normal ack. 2=No ack.,

3=Ack. reset condition state

AEClass Dint IN EDIT Timer AE Class, from 1 to 9999.

AEConf Dint IN EDIT Timer AE Conf. 0=AE disabled, 1x=Complete Event,2x=Complete Alarm, x1=Start,Stop,Reset events

AESev Dint IN EDIT Timer AE Severity, from 1 to 1000.

InitAutoMode bool IN True=Timer placed in Auto mode after a cold start,

False=Manual mode

MsgComplete string[47] IN Timer Complete Alarm & Event text

MsgReset string[47] IN Timer Reset Event text

MsgStart string[47] IN Timer Start Event text

MsgStop string[47] IN Timer Stop Event text

PT_Seconds dint IN INIT Preset Time seconds fraction (Range 0-3599 seconds)

PT_Minuts dint IN INIT Preset Time minuets fraction (Range 0-1439)

PT_Hours dint IN INIT Preset Time hours fraction (Range > 0)

PT_Days dint IN INIT Preset Time days fraction (Range > 0)

TimerType dint IN 1=Count down from Preset Time, 2=Count up to Preset Time,

3=Count up

Parameters & Data types Section 5 Timers (Engineering Principles)


78/177

78 3BEL300674D8007 Rev. A

Table 8. EqTimerPar Data Type

Name Datatype Description

AlarmAck bool IN Alarm Acknowledge

Cmd1 bool IN True = Start timer, False = Hold timer, command from logic

Cmd1Stat bool OUT True = Timer is active (e.g Running, Held or Complete)

Modes EqTimerMode IN OUT Modes and States Parameters (See Table 9page 79)

Reset bool IN True = Reset timer

ResetStat bool OUT True = Timer is reset from application or HSI

CompleteStat bool OUT True = Elapsed Time (ET) > Preset Time (TP)

ET time OUT Elapsed time since timer start

RT time OUT Remaining time (Only valid for TimerType = 1 or 2)

ParError bool OUT True if range exceeded on

PT_Seconds, PT_Hours, PT_Minuts, PT_Seconds

PT time OUT Preset time

(Conversion of PT_Days, _Hours, _Minuets, _Seconds)

PT_Seconds dint IN Preset Time seconds fraction (Range 0-3599)

PT_Minuts dint IN Preset Time minuets fraction (Range 0-1439)

PT_Hours dint IN Preset Time hours fraction (Range >= 0)

PT_Days dint IN Preset Time days fraction (Range >= 0)

Section 5 Timers (Engineering Principles) Parameters & Data types

Table 9. EqTimerModes Data Type


79/177

3BEL300674D8007 Rev. A 79

Name Datatype Description

AutoStat bool OUT Timer in Automatic or Locked in Automatic mode

LockAuto bool IN Change to locked automatic mode, lock is released when LockAuto=false

LockMan bool IN Change to locked manual mode, lock is released when LockMan=false

ManStat bool OUT Timer controlled from Faceplate

User Permissions Section 5 Timers (Engineering Principles)

User Permissions

The internal variables listed in the table are updated from faceplate by user.The input / activation from faceplate will be disabled if security is activated and user


80/177

80 3BEL300674D8007 Rev. A

The input / activation from faceplate will be disabled if security is activated and user

does not have the listed permissions.

If the permission / authentication configuration is insufficient. The permission

association can be overruled by applying and configuring theProperty Attribute

OverrideAspect on: The Control Module Type in the Object Type Structure to override the permissions

on all instances.

The instance in the Control Structure to override permissions on the instance.

Table 10. EqTimer User permissions

Variable Permission Description

HSIAuto Operate Command from faceplate to change to Auto mode

HSICmd0 Operate Command from faceplate to Stop timer

HSICmd1 Operate Command from faceplate to Start timer

HSIMan Operate Command from faceplate to change to Manual mode

HSIPT Operate Preset time from faceplate

HSIReset Operate Command from faceplate to reset timer

Section 5 Timers (Engineering Principles) Faceplate Element List Of Timers

Faceplate Element List Of Timers

Introduction


81/177

3BEL300674D8007 Rev. A 81

The AspectFaceplate Element List Of Timersis used to present process timers to

the operator in the faceplate.

To integrate process timers in the Control Builder Application See How to Use,

page 75.

When the aspectFaceplate Element List Of Timersis created on an object, theFaceplate Element will automatically be populated with all the instances of the

Control Module Type EqTimers that exist as child to the object in the application

(Control Structure). The principle is described in the following figure.

If placed Area1. The list will contain EqTimer1, -2 & -3

If placed on Unit1. The list will contain EqTimer1 & -2

If placed on Unit2. The list will contain EqTimer3

Figure 22. Where to placeFaceplate Element List Of Timers

Area1

Unit1

Unit2

EqTimer1

EqTimer3

EqTimer1,-2 & -3

EqTimer1 & -2

EqTimer3

EqTimer2


82/177

Section 5 Timers (Engineering Principles) How to Use

How to Use

AFaceplate Element List Of Timersis created by:1. Select an aspect / object in one of the following structures:


83/177

3BEL300674D8007 Rev. A 83

Control Structure: Control Network, Control Network,

Object Type Structure: Control system/Object Type Group, Libraries/

Library Group,

Object Type Structure: Control system/Application-defined Type,

Application Type Group.

2. Right mouse clickon the Aspect Object.

3. Select menu-item New Aspect.

4. Check mark in List Presentation.

5. Scroll down to the AspectFaceplate Element List Of Timers.

6. Press Create.

How to Use Section 5 Timers (Engineering Principles)


84/177

84 3BEL300674D8007 Rev. A

Appendix A Equipment Control Module Reference


85/177

3BEL300674D8007 Rev. A 85

pp q p

This appendix contains detailed description of the following Control Modules Type

from PCEquipmentLib library: EqCore (See EqCore Control Module Type, page 86)

EqDeviceSummary (See EqDeviceSummary Control Module Type, page 112)

EqModeControl (See EqModeControl Control Module Type, page 115)

This family of Control Modules is intended to be used as building block in

Equipment Control Modules See Equipment (Engineering Principles), page 25.

EqCore Control Module Type Appendix A Equipment Control Module Reference

EqCore Control Module Type

Introduction

Thi h t d ib E C C t l M d l Th E C C t l M d l


86/177

86 3BEL300674D8007 Rev. A

This chapter describesEqCoreControl Module. TheEqCoreControl Module:

Contains the core logic, common to all types of equipment control modules.

Handles Modes, States & Mode Of Operation including the internal

dependencies and priorities between these.

Contains logic for exception handling (Priority Commands & Interlocks).

Contains status variables for presenting of faceplate status information.

Contains variables to receive commands for Modes, State & Mode Of

Operation from the faceplate.

TheEqCorecontrol module contains the following aspects:

PriorityInterlockCmd:Faceplate elementaspect for presentation and inhibit

with Priority Commands & Interlocks (See EqCore: Priority- & Interlock

faceplate element, page 110).

ModeOfOperationxR2C: Graphic presentation of Mode Of Operation to be

used inFaceplate Elements(See Faceplate Elements building blocks

(ModeOfOperation *R*C), page 96). ModeOfOperation: Graphic building block forfaceplate elementsaspects

concerning presentation and interaction with Mode Of Operation. Presentation

with dropdown box. This element will always have same size independent of

the number of Mode Of Operations (See Faceplate Elements building blocks

(ModeOfOperation), page 94).

ModeOfOperationConfPar:Faceplate elementaspect for presentation of the

association between Mode Of Operation and Priority Commands (See

Faceplate Element (ModeOfOperationConfPar), page 97).

ModeOfOperationTimeOutPar: Graphic building block for faceplate elements

concerning Mode Of Operation supervision alarm. Gives the operator the

options to set filtertime and enable/disable the alarm (See How to use MOP

supervision alarm, page 97).

Appendix A Equipment Control Module Reference Control Module Parameters & Variables

Control Module Parameters & Variables

See the related chapters for logic diagrams as well as parameter, variable

descriptions.

Chapter: How to use Mode Of Operation page 88


87/177

3BEL300674D8007 Rev. A 87

Chapter: How to use Mode Of Operation, page 88

HSIMOP

MOP, MOPStat, MOPComplete, MOPCompleteStat

SFCReset, SFCDisableAction, SFCHold

Chapter: How to use States, page 100

Cmd1, Cmd1Stat

HSIStart, HSIStop

Chapter: How to use Modes, page 102

HSIMan, HSIAuto

AutoStat, ManStat

LockAuto, LockMan

Chapter: How to use Priority Commands & Interlocks, page 104

HSIInh

Inh, InhStat

ILockStat, ILock0Stat, ILock1Stat

PCC

PriCmd0, PriCmdMan0, PriCmd1, PriCmd2

PriCmd0Stat, PriCmdMan0Stat, PriCmd1Stat, PriCmd2Stat


88/177

Appendix A Equipment Control Module Reference How to use Mode Of Operation

EqCore supports control of the actual Equipment Module MOP handling by

controlling the execution of an ordinary SFC (See Figure 24)

The SFC must be implemented in the following manner:

Each branch corresponds to one specific Mode Of Operation.


89/177

3BEL300674D8007 Rev. A 89

Each branchcorresponds to one specific Mode Of Operation.

EndTransitions. Always = False. Termination of the branch is done by the

EqCore parameters SFCReset.

Select_MOP_?Transitions:MOPStat = 1,2,3....

Last step in each branch has to contain MOPCompleteStat := MOPStat in orderto stop alarm supervision of MOP change over (only necessary if parameter

AEMOPConf 0).

MOPStoppedConf = 0

Figure 24. How to interface EqCore inside the equipment module

SFCResetSFCHold

SFCDisableActions

EqCore:

MOPStat

MOPCompleteStat

MOP completion

feedback

Control of

MOP selection

Control ofSFC execution

Application Control &

Monitoring of devices

Cmd1Stat


90/177


MOP

AutoStat

HSIMOP


91/177

3BEL300674D8007 Rev. A 91

Figure 26. EqCore, Logic diagram for MOPStat & HSIMOP parameters

ManStatHSIMOPMOP

MOPPriCmdMan0Conf>

0&

MOPPriCmdMan0Conf

PriCmdMan0Stat

MOPPriCmd0Conf>

0&

MOPPriCmd0Conf

PriCmd0Stat

MOPPriCmd1Conf>

0&

MOPPriCmd1Conf

PriCmd1Stat

MOPPriCmd2Conf>

0&

MOPPriCmd2Conf

PriCmd2Stat

MOPStat

MOPStoppedConf==

0

0

MOPStoppedConf>

0

MOPStoppedConf

&

Cmd1StatPriCmdMan0StatPriCmd0StatPriCmd1StatPriCmd2Stat

How to use Mode Of Operation Appendix A Equipment Control Module Reference

Table 11. EqCore Mode Of Operation associated parameters & variables



92/177

92 3BEL300674D8007 Rev. A

HSIMOP DInt IN The Mode Of Operation selected from faceplate.

MOP DInt IN The Mode Of Operation set from application logic.

MOPStat DInt OUT The active mode of operation depending of source of

control (ManStat/AutoStat).

R_TrigMOP Bool OUT True one scan every time Mode Of Operation is changed

either from logic (MOP) Or faceplate (HSIMOP).

ManStat

AutoStat

See table EqCore Modes associated parameters & variables, page

103

SFCReset Bool OUT Reset external State SFC (connect to: Sequence Name.

Reset), Note the parameter has the same value as R_TrigMOP

SFCDisableAction Bool OUT Reset external State SFC (connect to:

SequenceName.Reset), Note the parameter has the same value as

R_TrigMOP

SFCHold Bool OUT Hold external State SFC (connect to:

SequenceName.Hold), Note the parameter has the same value as

R_TrigMOP

CompleteStat Bool OUT Status to HSI. Commanded and achieved

ModeOfOperation corresponding (MOPStat =

MOPCompleteStat)

MOPCompleteStat Dint IN OUT Eq. module MOP feedback: Must be set =MOPStat

externally when final MOP state is reached (Reset by EqCore,

when MOPStat is changed)

MOPPriCmdMan0Conf Dint IN Equipment module action on PCC = PriCmdMan0

0; Cmd1Stat = False & MOPStat = MOPPriCmdMan0Conf


MOPPriCmd0Conf Dint IN Equipment module action on PCC = PriCmd0

0 C d1S F l

Table 11. EqCore Mode Of Operation associated parameters & variables



93/177

3BEL300674D8007 Rev. A 93

0; Cmd1Stat = False & MOPStat = MOPPriCmd0Conf

MOPPriCmd1Conf Dint IN Equipment module action on PCC = PriCmd10: Cmd1Stat = True & MOPStat = MOPPriCmd1Con

MOPPriCmd2Conf Dint DintIN Equipment module action on PCC = PriCmd2

0: Cmd1Stat = True & MOPStat = MOPPriCmd2Conf

MOPStoppedConf Dint IN Configuration of actual MOP when Cmd1Stat= false

0; MOPStat = MOPStoppedConf

How to use Mode Of Operation Appendix A Equipment Control Module Reference

Faceplate Elements building blocks (ModeOfOperation)

TheEqCoreControl Module Type contains a Graphic Elementaspects

ModeOfOperation, which can be integrated inFaceplate Elementsaspects to allow

the operator to:

view The mode of Operation on the Equipment Module


94/177

94 3BEL300674D8007 Rev. A

view The mode of Operation on the Equipment Module,

change Mode Of Operation, if the user have the requested permission and

the equipment module is in manual mode.

The graphic element will:

contain 3 lines of information:

Line 1: Presentation of current active Mode Of Operation.

Line 2: Drop Down box for manual selection of Mode Of Operation.

Line 3: Presentation of the Mode Of Operation selected from logic.

Show bad OPC data, - in case any of the subscribed data returns badquality.

Show out of range, - in case the value of Mode Of Operation exceeds the

configured number of inputs,

Have a fixed size to fit the width of standard faceplate,

When in Manuel mode: the drop down is enabled in order to let the the

operator select mode of operation

Figure 27. Mode Of Operation with drop down, Manual / Auto mode presentation


How to use

1. Create the faceplate element that should present mode of operation.

2. Open the faceplate element in Visual Basic.

3. Open the Element Browser.


95/177

3BEL300674D8007 Rev. A 95

4. Press BrowseButton.

5. Find and select the instance of the EqCore Control Module.

6. Press Okbutton.

7. Select theModeOfOperationGraphic elements.

8. Press Add Elementbutton.

How to define Mode Of Operations texts

1. Go to theLibrary Structure... PCEquipmentLib Custumizations.

2. Right mouse clickon the Template MOP_NewEquipmentModuleaspect

3. SelectCopy.

4. Right mouse clickand select

Documents

PCEquipmentLib 1.3-0 Engineering Guidelines 3BEL300674D8007 Rev A.pdf