PCEquipmentLib 1.3-0 Engineering Guidelines 3BEL300674D8007 Rev A PDF

ATPA Industrial
IT
System Program
800xA - Process Control Equipment Library
Version 1.3-0
Engineering Guidelines
Engineering Guidelines
ATPA Industrial
IT
System Program
800xA - Process Control Equipment Library
Version 1.3-0
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.
3BEL300674D8007 Rev. A 5
TABLE OF CONTENTS
About This Book
Use of Warning, Caution, Information, and Tip Icons .................................................... 11
Document Conventions ...................................................................................................12
Terminology.....................................................................................................................13
Related Product Guides ...................................................................................................16
Section 1 - Introduction
Product 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
Table of Contents
6 3BEL300674D8007 Rev. A
PhaseBasicTemplate........................................................................................................ 45
Functional overview ............................................................................................ 45
Faceplate overview.............................................................................................. 46
Control Module Overview................................................................................... 47
General rules for parameters & data types........................................................... 54
PhaseBasicTemplate, Step by step instruction..................................................... 55
Section 4 - Prompts (Engineering Principles)
Introduction..................................................................................................................... 59
Control Module Type Prompt ......................................................................................... 61
Description........................................................................................................... 61
How to Use .......................................................................................................... 62
Parameters & Data types...................................................................................... 63
User Permissions.................................................................................................. 65
Faceplate Element List Of Prompts ................................................................................ 66
Introduction.......................................................................................................... 66
How to Use .......................................................................................................... 68
Section 5 - Timers (Engineering Principles)
Introduction..................................................................................................................... 69
Control Module Type EqTimer ....................................................................................... 73
Description........................................................................................................... 73
How to Use .......................................................................................................... 75
Parameters & Data types...................................................................................... 77
User Permissions.................................................................................................. 80
Faceplate Element List Of Timers................................................................................... 81
Introduction.......................................................................................................... 81
How to Use .......................................................................................................... 83
Appendix A - Equipment Control Module Reference
EqCore Control Module Type......................................................................................... 86
Introduction.......................................................................................................... 86
Control Module Parameters & Variables ............................................................. 87
Table of Contents
3BEL300674D8007 Rev. A 7 3BEL300674D8007 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........................................................................................................123
How to use..........................................................................................................125
pccILockBatch Control Module Type ...........................................................................126
Introduction........................................................................................................126
How to use..........................................................................................................129
User Permissions................................................................................................130
pccThrowExecption Control Module Type ...................................................................131
Introduction........................................................................................................131
How to use..........................................................................................................133
TaskPointer Control Module Type ................................................................................138
Introduction........................................................................................................138
How to use..........................................................................................................141
User Permissions................................................................................................149
Table of Contents
8 3BEL300674D8007 Rev. A
Appendix C - Graphic Tools
Faceplate Element List Of Devices............................................................................... 152
Introduction........................................................................................................ 152
How to use ......................................................................................................... 156
Faceplate Element List Of Equipment .......................................................................... 162
Introduction........................................................................................................ 162
How to use ......................................................................................................... 165
Faceplate Element List Of Phases................................................................................. 166
Introduction........................................................................................................ 166
How to use ......................................................................................................... 169
Appendix D - Configuration
Logical Colors............................................................................................................... 171
NLS (Native Language Support) .................................................................................. 172
PCEquipmentLib Project Constants.............................................................................. 173
Global configuration ..................................................................................................... 175
3BEL300674D8007 Rev. A 9
Safety Summary
3BEL300674D8007 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 3BEL300674D8007 Rev. A
Safety Summary
3BEL300674D8007 Rev. A 11
About This Book
Use of Warning, Caution, Information, and Tip Icons
This publication includes Warning, Caution, and Information where appropriate
to point out safety related or other important information. It also includes Tip to
point out useful hints to the reader. The corresponding symbols should be
interpreted as follows:
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
comply fully with all Warning and Caution notices.
Warning icon indicates the presence of a hazard which could result in personal
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
Document Conventions About This Book
12 3BEL300674D8007 Rev. A
Document Conventions
The 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 CTRL key while
pressing the C key (to copy a selected object in this case).
Press ESC E C indicates 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 Start menu name always refers to the Start menu on the Windows
Task 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 as
follows in the procedure:
TIC132
Variables are shown using lowercase letters.
sequence name
About This Book Terminology
3BEL300674D8007 Rev. A 13
Terminology
The 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 modules as defined by IEC 61512,
ANSI/ISA S88.01. Devices chosen in order not to mix
Control 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 basis
functions.
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.
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.
Command to open/start device or start the equipment specific
PriCmd1 function.
Command to open/start device, or to start the equipment
specific PriCmd2 function.
PriCmdStop
PriCmdAbort
PriCmdHold
PriCmdPause
PriCmdReset
PCC commands that can be sent to Produce IT Batch Units
Phases or SharedEquipmentModules from PCDeviceLib input
devices in order to cause state change in the batch engine. See
also: Batch Control Module Reference, page 119.
About This Book Terminology
3BEL300674D8007 Rev. A 15
ILockStop
ILockAbort
ILockHold
ILockRestart
ILockResume
ILockStart
ILockReset
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
Related Product Guides About This Book
16 3BEL300674D8007 Rev. A
Related Product Guides
The following is a listing of documentation relevant as supplementary reading to PC
Equipment Library.
Category Title Description
System
Administration
800xA Production management
Batch management
System Version 4.0
Configuration
ABB Doc. No.: 3BUA000146R4001
Use of ProduceITBatchLib and
BatchAdvTemplateLib.
Section 3 Equipment Configuration
(Batch Advanced Templates)
Appendix C Configuring a Graphic
Appendix G AC 800M/C Controller
(Batch Advanced Templates)
Software PCDeviceLib User Documentation
ABB Doc. No.: 3BG001947D0077
User documentation.
BatchAdvTemplateLib Help file for the library
BatchAdvTemplatesLib.
Describes the use of functionality in
both ProduceITBatchLib and the
templates in BatchAdvTemplateLib.
Help file locate C:\Program Files\ABB
Industrial IT Engineer IT Control
Builder m Professional
x.x\Help\UserHelp.
To open the help file. Open Control
Builder Professional Place the curser
on the BatchAdvTemplateLib and Press
F1
3BEL300674D8007 Rev. A 17
Section 1 Introduction
Product Overview
This 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 SharedEquipmentModuleTemplate Control
Module Type.
The SharedEquipmentModuleTemplate is not intended to be instantiated inside
Unit (UnitTemplate from BatchAdvTemplateLib).
PCEquipmentLib Equipment modules and BatchAdvTemplateLib
SharedEquipmentModuleTemplate is not the same !
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 several
basis functions also called Mode Of Operations.
Examples of Mode Of Operations can be:
Ramp Temp / Hold Temp
Add medium A / Add medium B
Pull vacuum / Release vacuum
Section 1 Introduction Product Overview
3BEL300674D8007 Rev. A 19
This encapsulation of devices in equipment modules makes reuse of device control
possible.
Same Mode Of Operation can be activated from different states in the
same phase (Running, Holding, Stopping).
Same Mode Of Operation can 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 type of 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.
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 1
Equipment module (Discharging)
Unit
Equipment module (Temp. cont.)
Equipment module (Agitation)
Equipment module (Charging)
Phase 1
Phase 2
Unit
Unit
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)
Prerequisites and Requirements Section 1 Introduction
22 3BEL300674D8007 Rev. A
Prerequisites and Requirements
PCEquipmentLib 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, parameter
naming conventions, parameter usage as well as the PCC concept.
Section 1 Introduction Support
3BEL300674D8007 Rev. A 23
Support
Please 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 new
library versions).
Support Section 1 Introduction
24 3BEL300674D8007 Rev. A
3BEL300674D8007 Rev. A 25
Section 2 Equipment (Engineering Principles)
Introduction
This 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 of
EqBasicTemplate to create project specific equipment control module types.
The EqBasicTemplate contains
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.
Functional overview Section 2 Equipment (Engineering Principles)
26 3BEL300674D8007 Rev. A
Functional overview
EqBasicTemplate is build around EqCore (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 in Running state the equipment module executes the selected Mode Of
Operation.
When in Stopped state the 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 state and stopped state and
selection of Mode Of Operation is controlled by logic)
Manual mode (change between running state and stopped state and
selection of Mode Of Operation is controlled by user from the faceplate)
The EqBasicTemplate is 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 Operation is 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.
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 are
integrated 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 Stopped Mode Of Operation if any Priority Command is received.
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
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 Module
Type 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)
30 3BEL300674D8007 Rev. A
Control Module overview
This section describes the overall structure of the EqBasicTemplate control 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)
Section 2 Equipment (Engineering Principles) Control Module overview
3BEL300674D8007 Rev. A 31
Ad 1, Figure 3, page 30:
The equipment module is encapsulated in a control module type in order to be
reused as type (single point of maintenance) and to be able to generate graphics
automatic.
EqCore: Control module type which controls modes, states and provides
graphic to faceplate as well as entry point for faceplate buttons and status
indications. See also EqCore Control Module Type, page 86.
EqDeviceSummary: Control module type which collects and presents status
information. See also:
EqBasicTemplate: Faceplates, page 28.
EqDeviceSummary Control Module Type, page 112.
EqModeControl: Control module type which control the mode on all devices
depending on the modes and state of the equipment. See also EqModeControl
Control Module Type, page 115.
Ad 5, Figure 3, page 30: Devices controlled by the equipment module.
Ad 6, Figure 3, page 30: PCC control modules used to collect PCC commands
and forward these to the EqCore Control Module. Use of PCC concept from
PCDeviceLib, which brings:
Automatic generated Graphical presentation of the exception conditions.
Unified implementation and user interface
Lower the required test effort.
See also: How to use Priority Commands & Interlocks, page 104.
Control Module overview Section 2 Equipment (Engineering Principles)
32 3BEL300674D8007 Rev. A
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 a Interlock1. This is done in
order to demonstrate how to collect and convert a boolean expression to a
PCC command.
Section 2 Equipment (Engineering Principles) Control Module overview
3BEL300674D8007 Rev. A 33
The EqBasicTemplate uses an sequential function chart (Figure 4, page 33) with one
branch for each Mode Of Operation (including one for Stopped) See. The EqCore is
configured to use SFC.Reset, -Hold, -Disable action to control the MOP_sfc when a
change of state (running/stopped), mode (manual/auto) or change of Mode Of
Operation is detected.
Figure 4. EqBasicTemplate: Mode Of Operation SFC
EqBasicTemplate, Step by step instruction Section 2 Equipment (Engineering Principles)
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 template EqBasicTemplate form 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 libraries BasicLib, PCDeviceLib, PCDeviceSupportLib and
PCEquipmentLib to ProjectEqLib.
3. Copy the Control Module Type EqBasicTemplate from PCEquipmentLib to
ProjectEqLib.
4. Rename the copy EqBasicTemplate to an appropriate name (NewEq).
5. Copy the data types EqBasicPar, EqBasicIO and EqBasicDevicesPar from
PCEquipmentLib to ProjectEqLib.
6. Rename the copy of EqBasicPar, EqBasicIO and EqBasicDevicesPar to
appropriate names (NewEqPar, NewEqIO and NewEqDevicesPar).
7. Replace the data types EqBasicPar, EqBasicIO, EqBasicDevicesPar with
NewEqPar, NewEqIO, NewEqDevicesPar on variables and parameters in
NewEq.
Section 2 Equipment (Engineering Principles) EqBasicTemplate, Step by step instruction
3BEL300674D8007 Rev. A 35
How to populate NewEq with devices (valves, motors etc.)
1. Open NewEq, Delete and/or Replace Control Module Type on the Valve1,
TotalizerRealIO, Transmitter Control Module. Create the remaining
PCDeviceLib devices which have to be controlled by the NewEq equipment
module.
2. Update the NewEqIO data type with the IO-data type for all devices in the
NewEq equipment module
3. Update the NewEqDevicesPar data type with the xxxPar data type for all
PCDeviceLib devices in the NewEq equipment module
4. Open the NewEq code tab DeviceStatus_st and complete programming as
described in the code tab.
5. Open the CMD editor for NewEq and zoom to level 2 by pressing Ctrl Num
+ and resolve any errors (Due to delete of Transmitter,
TotalizerRealIO1,Valve1)
6. Connect the parameter NewEqIO.xxx to the IO parameter on all devices.
7. Connect each element of the local variable DevPar to the parameter
InteractionPar on the associated PCDeviceLib device.
8. Apply appropriate unique Name and Description on all contained
PCDeviceLib devices (If the EqNew Control Module Type is going to be used
several times in the application, - expose each device Name parameter 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 3BEL300674D8007 Rev. A
How to extent the Mode Of Operations.
1. Open the MOP_sfc code tab in the EqNew Control Module (Figure 5).
2. Create one branch below step sIdle for 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 step xxx_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 5 ref. C) The P1 code 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 the P1/P0 code tabs in order to avoid
loops).
A)
B)
C)
Section 2 Equipment (Engineering Principles) EqBasicTemplate, Step by step instruction
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 the EqModeControl Control Module.
2. Apply an appropriate value to the parameter TrackModeConf (Ref.
EqModeControl Control Module Type, page 115).
3. Open the code tab ModeControl_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 the EqCore Control Module.
2. Verify that the settings on the parameters MOPPriCmdMan0Conf,
MOPPriCmd0Conf, MOPPriCmd1Conf and MOPPriCmd2Conf is a correct
Mode Of Operation response to the associated Priority Commands
How to finalize Faceplate & graphic configuration
1. Open the faceplate element EqControl and Parameters and apply equipment
specific data.
2. Deploy all graphic aspects on the NewEq Control Module
General rules for Parameters & data types Section 2 Equipment (Engineering Principles)
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
configuration of the equipment. They must not be 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
3BEL300674D8007 Rev. A 39
Rule 4:
The data direction on parameters must be obeyed:
IN parameters Write Only from logic.
OUT parameters Read only from logic.
EqBasicTemplate parameters & data types
The EqBasicTemplate control module type have the following parameters and data
types 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
EqBasicTemplate parameters & data types Section 2 Equipment (Engineering Principles)
40 3BEL300674D8007 Rev. A
Table 2. EqBasicTemplate: Common elements in the InteractionPar data type
Cmd1 Bool IN True=Command to start the equipment module
Cmd1Stat Bool OUT True = Equipment module is running
MOP DInt IN Mode of operation to start when equipment module is
running
MOPStat DInt OUT Current active mode of operation.
If Equipment module is in Manual Mode MOPStat will
reflect the operators selection
MOPCompleteStat DInt )OUT MOP no. completed by Equipment, 0=Pending,
n=Completed MOP no. (Note MOPCompleteStat may be
different from MOP if Eq is in manual
Modes EqModes IN OUT Equipment module modes & commands
(See EqBasicTemplate: Common elements in the Modes
data type, page 41)
DeviceSummary EqDeviceSummaryType OUT Summarized status information for the contained
devices (See EqDeviceSummary Control Module Type,
page 112).
AEMOP EqAlarmEventType1 IN OUT MOP Completed Time-out Alarm, Event &
Actions
Section 2 Equipment (Engineering Principles) EqBasicTemplate parameters & data types
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 to
EqCore.
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 3BEL300674D8007 Rev. A
3BEL300674D8007 Rev. A 43
Section 3 Phase & Unit (Engineering Principles)
Introduction
This 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 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 equipment Eq1 from Phase1 is done by connecting the Figure 6, ref.
D) parameter InteractionPar from the equipment to the phase.
Control of Eq1 is done by means of the Eq1Par.Cmd1 and Eq1Par.MOP (Mode Of
Operation).
Figure 7. Unit overview: Multiple equipment control
Phase 1
Phase 2
Unit
Section 3 Phase & Unit (Engineering Principles) PhaseBasicTemplate
3BEL300674D8007 Rev. A 45
PhaseBasicTemplate
This section describes the functionality of the PhaseBasicTemplate as well as use of
PhaseBasicTemplate to create project specific phase control module types.
Functional overview
PhaseBasicTemplate is based on the PhaseTemplate from BatchAdvTemplateLib but
extended with the offerings from PCEquipmentLib. Status indication, buttons etc. as
configured from BatchAdvTemplateLib is left unchanged.
The PhaseBasicTemplate comes with pre configured faceplate
The PhaseBasicTemplate demonstrates 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.
Faceplate overview Section 3 Phase & Unit (Engineering Principles)
46 3BEL300674D8007 Rev. A
Faceplate overview
The normal faceplate and the extended faceplate presented below illustrates how the
different control modules can be utilized to implement the faceplate of an phase
control module. The numbered items in the figure are all items inherited from
PCEquipmentLib. The other parts is inherited from PhaseTemplate & PhaseCore, -
and do not require further engineering.
Figure 8. Phase faceplate layout & implementation
Ad 1, Figure 8, page 46) Presentation of equipment-, batch- and phase name.
Ad 2, Figure 8, page 46) Presentation of current task as well as selection of
restarting point (See TaskPointer Control Module Type, page 138).
Ad 3, Figure 8, page 46) Presentation and inhibit of Priority Commands and
Interlocks (See pccILockBatch Control Module Type, page 126).
Ad 4, Figure 8, page 46) Presentation and access to interaction with process
timers contained in the phase (See Timers (Engineering Principles), page 69).
Ad 5, Figure 8, page 46) Presentation and access to operator prompts contained
in the phase (See Prompts (Engineering Principles), page 59).
Ad 6, Figure 8, page 46) Link to alarm and event list, summarizing all phase
alarms and events.
1)
2) 3) 4) 5)
6)
Section 3 Phase & Unit (Engineering Principles) Control Module Overview
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 the PhaseBasicTemplate control 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 of ProduceITLib.
Figure 9, ILockBatch: To demonstrate integration of BatchPCC. ILockBatch:
module transfers batch PCC interlocks to the Core control 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 3BEL300674D8007 Rev. A
Figure 9, pccExceptionBatch: To demonstrate integration of BatchPCC. The
pccExceptionBatch launches a Hold exception when PCC Hold command is
recieved.
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 from Idle
to Running. 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 of
equipment control = in Local, has Object Error, Forced IO ect.
Control of the prompt is done in the Running SFC step sInitialize.
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 the Running SFC, Subsequence
Task 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 the Running SFC step sInitialize.
Figure 9, SP: To demonstrate the transfer of phase parameter to equipment
module. Assignment is done in the Running SFC step sInitialize.
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 the Running SFC subsequence
PhaseComplete.
3BEL300674D8007 Rev. A 49
Code tab usage
This describes the purpose and usage of the various code tabs in the
PhaseBasicTemplate.
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 with PCC).
A) B)
C)
D)
E)
50 3BEL300674D8007 Rev. A
Figure 10, ref. B)
The structure of the Running code 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 only when the associated S88 state is
active.
The use of all states is not mandatory. The code taps for unused S88 states
can 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) The Monitor code tab is a container to be used by the project
for logic that needs to be executed contineously when the phase is either Idle or
Not Idle.
3BEL300674D8007 Rev. A 51
SFC structure in the Running Code tab
This section describes purpose with the structure of the Figure 11, SFC in the
Running code 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, - the Running code tab is enabled and execution
will start from the sRunningEmpty Step. The branch in Ref. A) ensures that
sInitialize is only executed the first time the phase is started and not after a
Restart (after Hold).
A)
B)
D)
C)
52 3BEL300674D8007 Rev. A
Figure 11, ref. B) The step sInitialize is intented to be used to conduct checks
the first time the phases starts (such as condition of devices etc.) in order to
document as well as inform the operator that actions is needed before the phase
is able to start. In the PhaseBasicTemplate the step sInitialize is 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) The Running SFC 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 Task1 will be executed prior to Task2 which will be executed prior
to PhaseComplete. To work with restarting points see TaskPointer Control
Module Type, page 138
3BEL300674D8007 Rev. A 53
Batch Priority commands and Interlocks
The PhaseBasicTemplate is configured so phases based on the template can respond
to a Held command issued at unit level as a PCC command by any of the
PCDeviceLib modules like Transmitter, Totalizer, Digital Input ect. or even
equipment modules based on the EqBasicTemplate.
This is made possible by the modules pccILockBatch and pccExecptionBatch. The
modules are connected to each other graphically through the CMD editor and then
connected to a parameter defined as a Node (In order to make it possible to connect
to this graphically as for the rest of the PCC modules).
Figure 12. PhaseBasicTemplate: Connection of PCC modules graphically
If batch exceptions with unit scope are implemented, the corresponding batch
priority command and interlock for the exception condition must be included in
the PCC parameter. Otherwise the condition is not displayed in the phase
faceplate. See pccThrowExecption Control Module Type, page 131 as well as the
other batch PCC control modules.
General rules for parameters & data types Section 3 Phase & Unit (Engineering Principles)
54 3BEL300674D8007 Rev. A
General rules for parameters & data types
The parameters of an equipment phase control module are divided into a number of
structured 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
3BEL300674D8007 Rev. A 55
PhaseBasicTemplate, Step by step instruction
This section describes the overall steps necessary to create a phase module by
means of the template PhaseBasicTemplate form PCEquipmentLib
How to create new phase from template
1. Create and/or open a project specific Control Builder Library
(ProjectPhaseLib).
2. Connect the libraries BasicLib, PCDeviceLib, PCDeviceSupportLib and
PCEquipmentLib, ProduceITBatchLib to ProjectPhaseLib.
3. Copy the control module type PhaseBasicTemplate from PCEquipmentLib to
ProjectPhaseLib.
4. Rename the copy PhaseBasicTemplate to an appropriate name (NewPhase).
5. Add parameters to the NewPhase control module, one for each equipment
module to be controlled by the NewPhase (Same principle as for the Eq1Par
parameter).
6. Delete the parameter Eq1Par.
7. Delete the use of Eq1Par from the Running code tab.
8. Apply the required batch parameters through the BatchPhase aspect.
PhaseBasicTemplate, Step by step instruction Section 3 Phase & Unit (Engineering Principles)
56 3BEL300674D8007 Rev. A
How to extend the phase running logic.
1. Open the Running code tab in the NewPhsse Control Module (Figure 13).
2. Create one subsequence below step sTaskSwitch for each Task.
3. Extend each subsequence with the required number of steps and transitions.
Section 3 Phase & Unit (Engineering Principles) PhaseBasicTemplate, Step by step instruction
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 the NewPhase parameter PCC .
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 in Holding code.
How to finalize Faceplate & graphic configuration
1. Deploy all graphic aspects on the NewPhase Control Module.
PhaseBasicTemplate, Step by step instruction Section 3 Phase & Unit (Engineering Principles)
58 3BEL300674D8007 Rev. A
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)
60 3BEL300674D8007 Rev. A
The prompt concept consists of the:
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 Object
containing the Aspect Faceplate 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
3BEL300674D8007 Rev. A 61
Control Module Type Prompt
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
&
Name
Msg
AEConf
AEClass
AESev
&
Alarm
How to Use Section 4 Prompts (Engineering Principles)
62 3BEL300674D8007 Rev. A
How to Use
Create an instance of the Control Module Type Prompt at the desired position in the
application. Use structured data type InteractionPar to 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 15 below.
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
NameY
Prompt message Y
Ack Reject
1.00
Value: Unit
oo o ooo
Section 4 Prompts (Engineering Principles) Parameters & Data types
3BEL300674D8007 Rev. A 63
Parameters & Data types
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) presented
in 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)
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.
Table 4. Prompt Control Module Type Parameters
Section 4 Prompts (Engineering Principles) User Permissions
3BEL300674D8007 Rev. A 65
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
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
Faceplate Element List Of Prompts Section 4 Prompts (Engineering Principles)
66 3BEL300674D8007 Rev. A
Faceplate Element List Of Prompts
Introduction
The Aspect Faceplate Element List Of Prompts is used to present prompts to the
operator in the faceplate.
To integrate prompts in the Control Builder Application See How to Use, page 62.
When the aspect is created on an object, the Faceplate Element will automatically
be populated with all the instances of the Control Module Type Prompt 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 Prompt1, -2 & -3
If placed on Unit1. The list will contain Prompt1 & -2
If placed on Unit2. The list will contain Prompt3
Figure 16. Where to place Faceplate Element List Of Prompts
Area1
Unit1
Unit2
Prompt1
Prompt3
Prompt1,-2 & -3
Prompt1 & -2
Prompt3
Prompt2
Section 4 Prompts (Engineering Principles) Introduction
3BEL300674D8007 Rev. A 67
When used the faceplate element will display the following information.
Figure 17. Faceplate Element List Of Prompts.
The faceplate element supports two different views of the prompts, selected radio
buttons Show All and Sorted By Time. Interaction with the radio buttons is not
restricted by any permissions.
The radio button Show All will 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 time will only display prompts waiting for operator
acknowledge. The Prompts will be sorted by the time, where the request for
operator acknowledgement became active.
Prompts
Sorted by time Show all
Weigh and add xxx to yyy. Enter amount:
Description...
Description...
Description...
...
How to Use Section 4 Prompts (Engineering Principles)
68 3BEL300674D8007 Rev. A
How to Use
A Faceplate Element List Of Prompts is created by:
1. Select an aspect / object in one of the following structures:
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 click on the Aspect Object.
3. Select menu-item New Aspect.
4. Check mark in List Presentation.
5. Scroll down to the Aspect Faceplate Element List Of Prompts.
6. Press Create.
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)
70 3BEL300674D8007 Rev. A
The process timer concept consists of the:
Control Module Type EqTimer with faceplate for manual and automatic
operation.
Aspect Faceplate Element List Of Timers.
The Control Module Type EqTimer can 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 Aspect Faceplate Element List Of Timers can be used in Faceplates or Graphics
in order to show all Process Timers in the Control Structure below the Object
containing the Aspect Faceplate Element List Of Timers.
The use of these elements is described in details in the following sections.
Section 5 Timers (Engineering Principles) Introduction
3BEL300674D8007 Rev. A 71
The faceplates use the following icons for presentation:
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
72 3BEL300674D8007 Rev. A
Stop timer button or status indication
Reset button or status indication
Icon Description
Section 5 Timers (Engineering Principles) Control Module Type EqTimer
3BEL300674D8007 Rev. A 73
Control Module Type EqTimer
Description
This Control Module is used to represent the process timer inside the Control
Builder application.
To present process timers in faceplates or Process Graphic see How to Use, page 83
The EqTimer module can be in 2 modes:
Automatic mode (Process timer is controlled from logic).
Manual mode (start , stop, reset, entering of preset time is controlled by the
user from the faceplate).
Change of modes and status information concerning current mode is described in
Figure 18.
Figure 18. EqTimer, Logic diagram for Modes associated parameters
Conversion and selection of preset time depending on modes is done as described in
Figure 19
Figure 19. EqTimer, Logic diagram selection of Preset Time
HSIAuto
HSIMan
IPar.Modes.LockAuto
IPar.Modes.LockMan
IPar.Modes.ManStat
IPar.Modes.AutoStat
>=
InitAuto (Startup)
S
R
>=
IPar.Modes.ManStat
HSIPT
IPar.PT
IPar.Modes.AutoStat
HSIPT
Conversion
to Time IPar.PT_Minuts
IPar.PT_Seconds
IPar.PT_Hours
IPar.PT_Days
IPar.PT
IPar.ParError
Description Section 5 Timers (Engineering Principles)
74 3BEL300674D8007 Rev. A
Start, Stop and reset of timer depending on mode and timer type is done as described
in Figure 20
Figure 20. EqTimer, Logic diagram for timer control
IPar.PT
IPar.CompleteStat
HSIReset
IPar.Reset
>=
>=
IPar.ET
TimerStart
TimerReset IPar.ResetStat
&
HSICmd0
IPar.Cmd1Stat
>=
S
R
IPar.Cmd1
&
IPar.HSICmd1
IPar.Modes.ManStat
&
IPar.Modes.AutoStat
&
>=
&
IPar.Modes.ManStat
IPar.Modes.AutoStat
IPar.Cmd1
<>
&
3
TimerType
IPar.PT
-
Elapsed
Time
IPar.ET
IPar.RT
IPar.CompleteStat
IPar.Cmd1Stat
Section 5 Timers (Engineering Principles) How to Use
3BEL300674D8007 Rev. A 75
How to Use
Create an instance of the Control Module Type EqTimer in the application.
Figure 21 below demonstrates how:
The use of Interactionpar (IPar) to control the process timer in a sequence.
How to transfer preset timer from a phase parameter to the process timer.
The launch the Process Timers faceplate from the Faceplate Element List Of
Timers.
The dynamic information in the Faceplate Element List Of Timers aspect.
Figure 21. Integration of EqTimer Control Module Type in application
EqTimer
Control
module
Alarmlist
Control
builder
sequence
IPar.Cmd1 = True
Start
timer
Idle
IPar.Reset
IPar.Cmd1 = False
Stop
timer
IPar.CompleteStat TrTimerComplete
? TrHeld
IPar.Cmd1 = True
Resume
timer
? TrResume
? TrStart
(*Transfer of Preset Time from phase paramter to Process Timer*)
IPar.PT_Hours := _bPhaseParHours.Value;
IPar.PT_Minuts := _bPhaseParMin.Value;
How to Use Section 5 Timers (Engineering Principles)
76 3BEL300674D8007 Rev. A
The name of the EqTimer Control Module (Contents of name parameter). Has to
be unique. If not the alarm launched by the EqTimer module will not work
Section 5 Timers (Engineering Principles) Parameters & Data types
3BEL300674D8007 Rev. A 77
Parameters & Data types
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 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 9 page 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
3BEL300674D8007 Rev. A 79
Table 9. EqTimerModes Data Type
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)
80 3BEL300674D8007 Rev. A
User Permissions
does not have the listed permissions.
Override Aspect on:
on all instances.
Table 10. EqTimer User permissions
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
3BEL300674D8007 Rev. A 81
Faceplate Element List Of Timers
Introduction
The Aspect Faceplate Element List Of Timers is 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 aspect Faceplate Element List Of Timers is created on an object, the
Faceplate 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 place Faceplate Element List Of Timers
Area1
Unit1
Unit2
EqTimer1
EqTimer3
EqTimer1,-2 & -3
EqTimer1 & -2
EqTimer3
EqTimer2
82 3BEL300674D8007 Rev. A
When used the faceplate element will display the following information.
Figure 23. Faceplate Element List Of Timers.
The faceplate element supports two different views of the process timers, selected
radio buttons Show All and Sorted By Time. Interaction with the radio buttons is
not restricted by any permissions.
The radio button Show All will display all process timers. This setting can be used
during commissioning to verify the configuration.
The radio button Sorted by time will only display process timers which are started.
The process timers will be sorted by the starting time.
For each timer either the elapsed- or remaining timer will be presented depending
on the type of timer (Parameter TimerType). The presentation format is intelligent
only 2 most significant parts of days, hours, minutes, seconds different from 0 will
be presented. The icons are similar to the icons used in the faceplate.
Section 5 Timers (Engineering Principles) How to Use
3BEL300674D8007 Rev. A 83
How to Use
A Faceplate Element List Of Timers is created by:
Library Group,
5. Scroll down to the Aspect Faceplate Element List Of Timers.
6. Press Create.
How to Use Section 5 Timers (Engineering Principles)
84 3BEL300674D8007 Rev. A
3BEL300674D8007 Rev. A 85
Appendix A Equipment Control Module Reference
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
86 3BEL300674D8007 Rev. A
EqCore Control Module Type
Introduction
This chapter describes EqCore Control Module. The EqCore Control 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.
The EqCore control module contains the following aspects:
PriorityInterlockCmd: Faceplate element aspect 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 in Faceplate Elements (See Faceplate Elements building blocks
(ModeOfOperation *R*C), page 96).
ModeOfOperation: Graphic building block for faceplate elements aspects
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 element aspect 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
3BEL300674D8007 Rev. A 87
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
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
How to use Mode Of Operation Appendix A Equipment Control Module Reference
88 3BEL300674D8007 Rev. A
How to use Mode Of Operation
Different alternative technical functions 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
One Mode Of Operation can be associated with one of the PCC commands
PriCmd0, - 1, - 2 or PriCmdMan0.
Mode Of Operation is integrated in the EqCore module in order to provide a number
of graphic building blocks to be used when building Faceplate Elements
Control Builder Logic in the equipment module
Mode Of Operation is 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.
Mode Of Operation must always start with the integer value 1 and must succeed
with 2, 3, 4 etc. depending of the numbers of supported Modes Of Operations.
Appendix A Equipment Control Module Reference How to use Mode Of Operation
3BEL300674D8007 Rev. A 89
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.
End Transitions. 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 order
to 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
SFCReset
SFCHold
SFCDisableActions
EqCore:
MOPStat
MOPCompleteStat
MOP completion
feedback
Control of
MOP selection
Control of
SFC execution
Application Control &
Monitoring of devices
Cmd1Stat
90 3BEL300674D8007 Rev. A
EqCore Mode Of Operation Logic Diagrams
The internal logic of EqCore concerning Mode Of Operations is split in two logic
diagrams. This is done in order to show how the MOPStat output parameter depends
on the configuration parameters MOPPriCmd*Conf & MOPStoppedConf
Figure 25. EqCore, Logic diagram for Mode Of Operation associated parameters
MOPStat MOPStat:New
MOPStat:Old MOPStat:New
R_TrigMOP
SFCReset
SFCHold
SFCDisableAction
<>
MOPStat:New
MOPStat:Old
False
True
0
MOPCompleteStat
CompleteStat ==
MOPCompleteStat
MOPStat
3BEL300674D8007 Rev. A 91
Figure 26. EqCore, Logic diagram for MOPStat & HSIMOP parameters
ManStat
HSIMOP
MOP
AutoStat
HSIMOP
MOPPriCmdMan0Conf
>
0
&
MOPPriCmdMan0Conf
PriCmdMan0Stat
MOPPriCmd0Conf
>
0
&
MOPPriCmd0Conf
PriCmd0Stat
MOPPriCmd1Conf
>
0
&
MOPPriCmd1Conf
PriCmd1Stat
MOPPriCmd2Conf
>
0
&
MOPPriCmd2Conf
PriCmd2Stat
MOPStat
MOPStoppedConf
==
0
0
MOPStoppedConf
>
0
MOPStoppedConf
&
Cmd1Stat
PriCmdMan0Stat
PriCmd0Stat
PriCmd1Stat
PriCmd2Stat
92 3BEL300674D8007 Rev. A
Table 11. EqCore Mode Of Operation associated parameters & variables
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
0; None
>0; Cmd1Stat = False & MOPStat = MOPPriCmdMan0Conf
3BEL300674D8007 Rev. A 93
MOPPriCmd0Conf Dint IN Equipment module action on PCC = PriCmd0
<0; Cmd1Stat = False
0; None
>0; Cmd1Stat = False & MOPStat = MOPPriCmd0Conf
MOPPriCmd1Conf Dint IN Equipment module action on PCC = PriCmd1
<0: Cmd1Stat = True
0: None
>0: Cmd1Stat = True & MOPStat = MOPPriCmd1Con
MOPPriCmd2Conf Dint DintIN Equipment module action on PCC = PriCmd2
<0: Cmd1Stat = True
0: None
>0: Cmd1Stat = True & MOPStat = MOPPriCmd2Conf
MOPStoppedConf Dint IN Configuration of actual MOP when Cmd1Stat= false
<0; Freeze MOPStat
0; MOPStat = 0 (Idle)
>0; MOPStat = MOPStoppedConf
Table 11. EqCore Mode Of Operation associated parameters & variables
94 3BEL300674D8007 Rev. A
Faceplate Elements building blocks (ModeOfOperation)
The EqCore Control Module Type contains a Graphic Element aspects
ModeOfOperation, which can be integrated in Faceplate Elements aspects to allow
the operator to:
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 bad
quality.
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
3BEL300674D8007 Rev. A 95
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.
4. Press Browse Button.
5. Find and select the instance of the EqCore Control Module.
6. Press Ok button.
7. Select the ModeOfOperation Graphic elements.
8. Press Add Element button.
How to define Mode Of Operations texts
1. Go to the Library Structure... PCEquipmentLib Custumizations.
2. Right mouse click on the Template MOP_NewEquipmentModule aspect
3. Select Copy.
4. Right mouse click and select Paste
5. Right mouse click on Copy of Template MOP_NewEquipmentModule aspect
6. Select Config View
7. Follow the instructions written inside this template aspect
8. No further configuration is required.
The HTML aspect can handle ISO 8859-1 characters. Complete list can be found
at http://www.htmlhelp.com/reference/charset/
Valid values of MOP:
The Mode Of Operation has to start with 1. If the number is not continues an error
message will be presented.
96 3BEL300674D8007 Rev. A
Faceplate Elements building blocks (ModeOfOperation *R*C)
The EqCore Control Module Type contains a number of Graphic Element aspects
Mode Of Operation *R*C which can be integrated in Faceplate Elements aspects to
allow the operator to:
view The mode of Operation on the Equipment Module,
change Mode Of Operation, if the user has the requested permission and
the equipment module is in manual mode.
The graphic element will:
show bad OPC data, - in case any of the subscribed data returns bad
quality,
show out of range, - in case the value of Mode Of Operation exceeds the
configured number of inputs,
automatic resize to fit the width of standard faceplate,
automatic resize to fit the height according to the configured number of
inputs.
When in Manuel mode: the mode that the operator has overridden is
presented with bold.
Figure 28. Mode Of Operation, Manual / Auto mode presentation
Appendix A Equipment Control Module Reference How to use MOP supervision alarm
3BEL300674D8007 Rev. A 97
Faceplate Element (ModeOfOperationConfPar)
The EqCore Control Module Type contains a Faceplate Element aspect
ModeOfOperationConfPar which can be integrated in the main faceplate on
equipment modules in order to present which Mode Of Operations that are
associated with the different Priority Commands.
Figure 29. EqCore: Faceplate Element ModeOfOperationConfPar
How to use MOP supervision alarm
EqCore is able to supervise the change from one Mode Of Operation to another
Mode Of Operation.
Presentation of MOP-numbers before the MOP text is controlled from the Config aspect.
See Global configuration, page 175.
To configure Mode Of Operations texts, see How to use Mode Of Operation, page 88
How to use MOP supervision alarm Appendix A Equipment Control Module Reference
98 3BEL300674D8007 Rev. A
If the change is not done within the time specified by the parameter
AEMOP.FilterTime an alarm or event might be launched.
The configuration No alarm / Alarm / Event is depending on the AEMOPConf.
Faceplate Elements building blocks (ModeOfOperationTimeOutPar)
Mode Of Operation change over supervision is supported by the Graphic Element
aspects ModeOfOperationTimeOutPar.
ModeOfOperationTimeOutPar can be integrated in Faceplate Elements aspects.
It allows the operator to:
Enable / Disable alarm supervision when changing Mode Of Operation.
Maintain the max time allowed to change from one Mode Of Operation to
another before an alarm is launched.
and will:
quality.
Figure 30. EqCore: Alarm supervision Mode Of Operation change
See also User Permissions, page 111.
Appendix A Equipment Control Module Reference How to use MOP supervision alarm
3BEL300674D8007 Rev. A 99
Figure 31. Logic diagram MOP Supervision alarm / event
AEMOP.Enable
& AEMOP.EnStat
Cmd1Stat
MOPStat
MOPCompleteStat
<>
R_TrigMOP
&
AlarmCondM
Signal CondState
AckRule
AckCond
DisCond
EnCond
SrcName
Message
Severity
Class
SimpleEventDetector
Signal
SrcName
Message
Severity
Class
AEMOP.Stat
AEMOP.AICond
AEMOP.FilterTime
AEMOPConf
Name
AEMOPMsg
AEClass
AEMOPSev
1
&
1
&
>
>
0
=
1
&
=
2
1
=
3
//
EventTxtOn
EventTxtOff
Conca
tenate
//
Timer
Run Elapsed
Reset
Hold
AEMOPAckRule
AlarmAck
HSIMOPTimeOutEnable
How to use States Appendix A Equipment Control Module Reference
100 3BEL300674D8007 Rev. A
How to use States
The EqCore Control Module supports 2 different States:
Running State.
Stopped State.
When State Running State is active the devices should be controlled in accordance
with the selected Mode Of Operation.
When in Stopped State all the devices should be in there safe state.
Figure 32. EqCore, Logic diagram for States associated parameters & variables
MOPStoppedConf parameter can be used to activate a certain Mode Of Operation
when the equipment module is stopped.
HSICmd0
Cmd1Stat
>= S
R
Cmd1
&
HSICmd1
ManStat
&
R_TrigCmd1
R_TrigCmd0
AutoStat
&
>=
&
ManStat
AutoStat
Cmd1
Appendix A Equipment Control Module Reference How to use States
3BEL300674D8007 Rev. A 101
Table 12. EqCore States associated parameters & variables
HSICmd0 Bool IN True = Stop command from faceplate (Connect to start button in
faceplate, reset inside EqCore)
HSICmd1 Bool IN True = Start command from faceplate (Connect to stop button in
faceplate, reset inside EqCore).
Cmd1 Bool IN True = Start command from logic (False = Stop)
Cmd1Stat Bool OUT True = Running (False = Stopped) status of the equipment module
independent of source of control.
R_TrigCmd0 Bool OUT True on the transition (Cmd1Stat) from stopped (False) to running
(True) .
R_TrigCmd1 Bool OUT True on the transition (Cmd1Stat) from running (True) to stopped
(False)
ManStat
AutoStat
See Table EqCore Modes associated parameters & variables, page 103
CMD1Stat: Use this parameter to control devices depending of the running / stopped
statue of the equipment module.
How to use Modes Appendix A Equipment Control Module Reference
102 3BEL300674D8007 Rev. A
How to use Modes
The equipment module can be in 2 modes:
Manual mode (change between running state and stopped state and selection of
Mode Of Operation is controlled from logic).
Automatic mode (change between running state and stopped state and selection
of Mode Of Operation is controlled by user from the faceplate).
Change to Manual Mode is integrated in the PCC concept. When a PriCmdMan0
(Stop equipment module and change to manual mode) command becomes inactive a
change to manual mode will occur. If inhibit is used to suppress the PriCmdMan0
command whilst this is active, no change to manual mode will occur, - instead the
Cmd1 command will take over the control the running / stopped state of the
equipment.
Figure 33. EqCore, Logic diagram for Modes associated parameters
HSIAuto
HSIMan
LockAuto
LockMan
ManStat
AutoStat
>=
InitAuto (Startup)
S
R
PCC
PriCmdMan0
&
InhStat
==
>=
Appendix A Equipment Control Module Reference How to use Modes
3BEL300674D8007 Rev. A 103
Table 13. EqCore Modes associated parameters & variables
HSIAuto Bool IN True = Change to automatic mode command from faceplate.
HSIMan Bool IN True = Change to manual mode command from faceplate.
LockMan Bool IN
Raising edge = Change to Manual mode.
Steady State True = Lock Mode to Manual by disabling the Automatic
mode button in faceplate.
LockAuto Bool IN
Raising edge = Change to Automatic mode.
Steady State True = Lock Mode to Automatic by disabling the Manual
mode button in faceplate.
InitAuto Bool IN True = When controller is cold restarted start equipment in automatic
mode (False = manual mode).
AutoStat OUT True = Equipment module is controlled by the application logic.
ManStat OUT True = Equipment module is controlled by the operator from
faceplate.
PCC
PriCmdMan0
InhStat
See table EqCore, Priority Commands & Interlocks, page 104
How to use Priority Commands & Interlocks Appendix A Equipment Control Module Reference
104 3BEL300674D8007 Rev. A
How to use Priority Commands & Interlocks
The EqCore Control module (EqCore) uses & implements the PCDeviceLib PCC
concept as described in PCDeviceLib User Documentation. All the PCDeviceLib
PCC control modules are therefore compatible with EqCore.
See ref. PCDeviceLib User Documentation, for a detailed description of the PCC
concept.
The EqCore control module is intended to drive modes and states and forward
priority commands and interlocks from surrounding control modules to devices
integrated within the equipment module.
Principle use of the EqCore is demonstrated in Figure 35, page 108 and Figure 36,
page 109.
The EqCore Control Module supports Priority Commands and Interlocks listed in
Table 14.
Table 14. EqCore, Priority Commands & Interlocks
PCC command Description
ILock0 Stop of equipment module is prevented.
ILock1 Start of equipment module is prevented.
PriCmdMan0 The equipment module is stopped and when the PriCmdMan0
command is released mode is changed to Manual.
PriCmd0 The equipment module is stopped.
PriCmd1 User defined action.
PriCmd2 User defined action.
Appendix A Equipment Control Module Reference How to use Priority Commands & Interlocks
3BEL300674D8007 Rev. A 105
As illustrated in Figure 34 & Table 15, page 107 the EqCore Control Module has
one PCC input parameter (PCC) and 4 output parameters (PriCmdMan0, PriCmd0, -
1, - 2). The EqCore Control Module will forward any active command if not
suppressed by Inhibit. Interlocks are used internally in the EqCore Control Module
to prevent start and stop of the equipment module.
Figure 34. EqCore PCC Logic Diagram (Priority Commands)
Notice that PCC commands can be associated with a specific Mode Of Operation
by means of the parameters:
MOPPriCmd0Conf
MOPPriCmd1Conf
MOPPriCmd2Conf
MOPPriCmdMan0Conf
See description in How to use Mode Of Operation, page 88
PCC
PriCmdMan0
==
PCC
PriCmd0
==
PCC
PriCmd1
==
PCC
PriCmd2
==
Inh
PriCmd1 (PCC)
PriCmd0 (PCC)
PriCmd2 (PCC)
&
&
InhStat &
HSIInh
PriCmd0Stat
PriCmd1Stat
PriCmd2Stat
PriCmdStat
PCC
ILock0
==
PCC
ILock1
==
ILock0Stat
ILock1Stat
&
&
ILockStat >=
PriCmdMan0 (PCC)
PriCmdMan0Stat
&
&
>=
106 3BEL300674D8007 Rev. A
3BEL300674D8007 Rev. A 107
Table 15. EqCore: PCC associated parameters and variables
Inh Bool IN True = Suppress any Priority Commands and Interlocks.
HSIInh Bool IN True = Suppressed by operator from faceplate.
InhStat Bool OUT True = Priority Commands and Interlocks are suppressed from logic
(Inh) or from faceplate by the operator (HSIInh).
ILockStat Bool OUT True when PCC = ILock0 or ILock1 is active and not suppressed by
inhibit (InhStat = True).
ILock0Stat Bool OUT True when PCC = ILock0 is active and not suppressed by inhibit
(InhStat = True).
ILock1Stat Bool OUT True when PCC = ILock1 is active and not suppressed by inhibit
(InhStat = True).
PCC PCC IN Priority- & Interlocks command to Equipment module.
PriCmdMan0 PCC OUT PCC output containing an active PriCmdMan0 command when PCC
= PriCmdMan0 and not suppressed by inhibit (InhStat = True).
PriCmd0 PCC OUT PCC output containing an active PriCmd0 command when PCC =
PriCmd0 and not suppressed by inhibit (InhStat = True).
PriCmdMan0Stat OUT True when PCC = PriCmdMan0 is active and not suppressed by
inhibit (InhStat = True)
PriCmd0Stat Bool OUT True when PCC = PriCmd0 is active and not suppressed by inhibit
(InhStat = True)
PriCmd1Stat Bool OUT True when PCC = PriCmd1 and not suppressed by inhibit (InhStat =
True).
PriCmd2Stat Bool OUT True when PCC = PriCmd2 and not suppressed by inhibit (InhStat =
True).
108 3BEL300674D8007 Rev. A
How to use
The PCC output parameters PriCmdMan0, PriCmd0, -1, -2 are intended to be
connected to the devices controlled by the equipment module (See Figure 35). The
figure demonstrates how to share the PriCmd0 output to the devices by means of the
pccSplit4 Control Module from PCDeviceLib.
If the devices need respond differently the safe state can be configured on the
pccSplit4 Control Module
Figure 35. EqCore PCC connection to device 1
Assuming that the devices in an equipment module should be able to respond to
both PriCmd0 and PriCmd1 from the equipment module the configuration will look
as illustrated in Figure 36, page 109. The pccOr4 Control Modules from
PCDeviceLib is used to collect from 2 different sources and a pccSplit4 control
module to define the control actions for PriorityCmd0 and PriorityCmd1
respectively.
EqCore
PCC
PriCmd0
PriCmd1
PriCmd2
pccSplit4
Motor
PCC
Valve
PCC
Valve
PCC
PriCmdMan0
3BEL300674D8007 Rev. A 109
Figure 36. EqCore PCC connections to device 2
Remember that the name (Contents of the Control Module Name Parameter) of
all control module instances having a PCC connection, - has to be unique in the
aspect system. If not so the automatic generated faceplate might not work.
Remember to run NameUploader and then PCC Uploader after adding/deleting
or changing name on any of the control modules participating in PCC
EqCore
PCC
PriCmd0
PriCmd1
PriCmd2
pccSplit4
Motor
PCC
Valve
PCC
Valve
PCC
pccOr4
pccOr4
pccOr4
pccSplit4
PriCmdMan0
110 3BEL300674D8007 Rev. A
The EqCore Control Module contains a predefined faceplate element (Figure 37) to
be used building equipment modules. The faceplate will be automatic updated with
all Priority Commands and Interlocks sent to the equipment module. through the
faceplate the operator has the possibility to suppress all Priority Command and
Interlocks by means of the Inhibit Prioritycmd and interlock check box.
Figure 37. EqCore: Priority- & Interlock faceplate element
Appendix A Equipment Control Module Reference User Permissions
3BEL300674D8007 Rev. A 111
User Permissions
Override Aspect on:
on all instances.
The instance in the Control Structure to override permissions of the instance.
Table 16. pccILockBatch User permissions
HSIAuto Operate Change of mode to Automatic.
HSIMan Operate Change of mode to Manual.
HSICmd0 Operate Stop of equipment module.
HSICmd1 Operate Start of equipment module.
HSIMOP Operate Change of Mode Of Operation.
HSIInh Tune Suppress of Interlocks and Priority Commands.
HSIMOPTimeOutEnable Tune Enable / Disable alarm supervision of Mode Of Operation
change over.
AEMOP.FilterTime Tune Change of filter time for alarm supervision of Mode Of
Operation change over
EqDeviceSummary Control Module Type Appendix A Equipment Control Module Reference
112 3BEL300674D8007 Rev. A
EqDeviceSummary Control Module Type
Introduction
The EqDeviceSummary is a Control Module Type with a graphic aspect that
contains the summarized status information about the devices.
Purpose:
To standardize the presentation of summarized status information for all
devices contained inside a parent object (devices in an equipment
module/devices in an unit)
To be used in the faceplate on Units, Phases, Equipment or any other
container of devices.
To keep the operator informed about devices with fault or devices not
controllable from the application.
The Device Summary retrieves information from the Control Module Type
EqDeviceSummary. The Control Module Type EqDeviceSummary is not only
limited to be used together with PCDeviceLib.
.
Figure 38. Device Summary graphic elements
Appendix A Equipment Control Module Reference How to use
3BEL300674D8007 Rev. A 113
How to use
Making Control Builder Application
1. Create an instance of EqDeviceSummary Control Module type inside the
equipment module.
2. Create code In order to support the EqDeviceSummary with information about
the different status of the devices as illustrated in Figure 39.
3. Connect the InteractionPar. DeviceSummary to the DeviceSummary parameter
on the EqDeviceSummary Control Module Instance.
Figure 39. EqDeviceSummery: Example code
Logical Colors Appendix A Equipment Control Module Reference
114 3BEL300674D8007 Rev. A
Making graphic
1. Create the faceplate element that should present mode of operation
2. Open the faceplate element in Visual Basic
4. Press Browse Button
5. Find and select the instance of the EqDeviceSummary Control Module
6. Press Ok button
7. Select EqDeviceSummary Graphic element
8. Press Add Element button
9. Press F4 to open the Visual Basic properties of the Graphic Element in order to
configure the presentation of Internal status.
Logical Colors
The Graphic Element uses the following logical colors. The used colors are selected
in order to be consistent with the presentation in PCDeviceLib Graphic elements
(six squared boxes)
Table 17. Used Colors
Logical Color Definition Color Usage
AC800 MC Colors OnColor Used to indicate on, active etc.
LocalIndicationColor Used to indicate local mode.
ForcedIndicationColor Used to indicate forced mode
ManIndicationColor Used to indicate Object Error
Faceplate Colors Alarm Used to indicate Object Error
PCDeviceLib Colors TripILockIndicationColor Used to indicate PriorityCmd and
Interlocks
InhibitIndicationColor Used to indicate Inhibit
Appendix A Equipment Control Module Reference EqModeControl Control Module Type
3BEL300674D8007 Rev. A 115
EqModeControl Control Module Type
Introduction
This chapter describes the functionality of the mode control module
EqModeControl.
The module is used to handle change to and lock of manual / auto / external /
internal mode for devices and equipment modules in a unified way, in order to
implement strategy for operator interventions while the plant is running.
Figure 40. EqModeControl Logic diagram 1
TrackModeConf
1
==
2
3
LockAuto
Cmd1Stat
TrackModeConf
TrackModeConf
11
Cmd1Stat
ExtLockAuto
==
&
==
&
Cmd1Stat
&
TrackModeConf
==
TrackModeConf
12
Cmd1Stat
ExtLockAuto
==
&
13
TrackModeConf
==
&
ExtLockAuto
=>
Introduction Appendix A Equipment Control Module Reference
116 3BEL300674D8007 Rev. A
Figure 41. EqModeControl Logic diagram 2
TrackModeConf
1
==
2
3
LockExternal
Cmd1Stat
TrackModeConf
TrackModeConf
11
Cmd1Stat
ExtLockExternal
==
&
==
&
Cmd1Stat
&
TrackModeConf
==
TrackModeConf
12
Cmd1Stat
ExtLockExternal
==
&
13
TrackModeConf
==
&
ExtLockExternal
=>
Appendix A Equipment Control Module Reference How to use
3BEL300674D8007 Rev. A 117
How to use
1. Create an instance of EqModeControl Control Module type in the equipment
module
2. Connect the LockExternal Parameter to the
InteractinoPar.Modes.LockExternal parameter on the PCDeviceLib devices
that supports External mode.
3. Connect the LockAuto Parameter to the InteractinoPar.Modes.LockAuto on the
PCDeviceLib devices that supports Automatic mode.
4. Connect the Cmd1Stat Parameter to the Parameter Cmd1Stat on the EqCore
Control Module Instance
5. Use the TrackModeConf to select the strategy for mode change.
6. Use the ExtLockExternal and ExtLockAuto to apply project specific conditions
to the change of modes
How to use Appendix A Equipment Control Module Reference
118 3BEL300674D8007 Rev. A
3BEL300674D8007 Rev. A 119
Appendix B Batch Control Module Reference
This appendix contains detailed description of the following Control Modules Type
from PCEquipmentLib library:
pccOr4Batch
pccOr16Batch
pccILockBatch
pccInhibitBatch
pccThrowException
TaskPointer
This family of Control Modules are intended to be used as building block in phases,
unit and equipment modules based on the templates from BatchAdvTemplateLib
See Section 3, Phase & Unit (Engineering Principles) page 43.
Appendix B Batch Control Module Reference
120 3BEL300674D8007 Rev. A
These Control Modules comprise a way of letting input devices from PCDeviceLib
generate the following batch priority commands and to interlock batch commands to
the batch core modules (PhaseCore, UnitCore, EquipmentCore).
PriCmdPause - Batch Priority Command Pause
PriCmdHold - Batch Priority Command Hold
PriCmdStop - Batch Priority Command Stop
PriCmdAbort - Batch Priority Command Abort
ILockStart - Batch Interlock Start
ILockRestart - Batch Interlock Restart
ILockReset - Batch Interlock Reset
ILockResume - Batch Interlock Resume
ILockPause - Batch Interlock Pause
ILockHold - Batch Interlock Hold
ILockStop - Batch Interlock Stop
ILockAbort - Batch Interlock Abort
.
Use of these Priority Commands and Interlocks must be done by means of the
project constant described in PCEquipmentLib Project Constants, page 173
Batch Priority Commands and Interlocks can be used together with the following
PCDeviceLib Devices: pccSplit4, - 16, pccBoolToPCC, Transmitter,
Totalizer200IB16, TotalizerRealIO, TotalizerDP820, DigitalInput
Batch Priority Commands and Interlocks can not be used together with the
following PCDeviceLib Control Modules: pccTOn, pccAnd4, pccAnd16,
pccOr4, pccOr16.
Appendix B Batch Control Module Reference pccOr4- pccOr16Batch Control Module Type
3BEL300674D8007 Rev. A 121
pccOr4- pccOr16Batch Control Module Type
Introduction
The pccOrBatch control modules are used to add active batch priority commands
and interlocks together from several input devices and forward the result to one
output. The pccOrBatch modules can be nested to any depth.
The pccOr4Batch control module can handle a maximum of four input devices and
the pccOr16Batch control module can handle a maximum of sixteen input devices.
Figure 42. pccOr4- pccOr16Batch Logic diagram
The pccOr4 and pccOr16 Control Modules from PCDeviceLib cannot handle batch
Priority Commands and interlocks. Batch Priority Commands and Interlocks will be not
passed through the these Control Modules.
Table 18. pccOr4Batch, pccOr16Batch parameters
Name String[20] IN Name of the object.
Description String[40] IN Exception description.
In1 PCC IN NODE, Device 1 Batch Priority commands and Interlocks.
Out PCC OUT NODE, Batch Priority commands and Interlocks.
In1.Action
Out.Action
In4.Action/16.Action
...
Forward the inputs
where In.Action
(Execute) is active
How to use Appendix B Batch Control Module Reference
122 3BEL300674D8007 Rev. A
How to use
1. Create an instance of pccOr4Batch / pccOr16Batch Control Module Type.
2. Connect all PCC inputs - if more than four PCC inputs are used than
pccOr16batch is required.
3. Connect the PCC output to the PCC input on the next Control Module.
4. Connect unique names and descriptions to all modules newly created
all Control Module instances having a PCC connection, - has to be unique in the
aspect system. If not so the the automatic generated faceplate might not work.
Remember to run NameUploader then PCCUploader after adding/deleting or
changing name on any of the control modules participating in PCC
Appendix B Batch Control Module Reference pccInhibitBatch Control Module Type
3BEL300674D8007 Rev. A 123
pccInhibitBatch Control Module Type
Introduction
The pccInhibitBatch Control Module:
Is used to inhibit all Priority Commands and Interlocks sent to the
Equipment Control Module while the phase is active.
Can be used together with PhaseCore, UnitCore and EquipmentCore from
ProduceITBatchLib.
In batch applications equipment can be controlled from one of two sources, either
from an active phase or running standalone. This requires exceptions being
implemented both for the batch state machine and for other logic.
The pccInhibitBatch Control Module has to be inserted just before the PCC input of
an Equipment Control Module, all Priority Commands and Interlocks to the
Equipment Control Module will be inhibited during the time the equipment is
controlled by the phase. When the equipment is running standalone, all priority
commands and interlocks are forwarded to the equipment module.
Figure 43. pccInhibitBatch Logic Diagram
Out.Action (bit 0 - bit 27)
IN.Action (bit 0 - bit 27)
=>
CurrentState = Idle (0)
CurrentState = Complete (2)
CurrentState = OutOfService (12)
&
IN.Action (Execute)
Out.Action (Execute)
& Out.Action (Status)
Out.Action (Inhibit)
IN.Action (Execute)
CurrentState = Running (1)
CurrentState = Pausing (3)
CurrentState = Paused (4)
CurrentState = Holding (5)
CurrentState = Held (6)
CurrentState = Restarting (7)
CurrentState = Stopping (8)
CurrentState = Stopped (9)
CurrentState = Aborting (10)
CurrentState = Aborted (11)
&
>=
Introduction Appendix B Batch Control Module Reference
124 3BEL300674D8007 Rev. A
Table 19. pccInhibitBatch parameters
Description String[40] IN Description of object
CurrentState Dint IN Connect to batch core parameter Status.CurrentState
In PCC IN NODE, PCDeviceLib Priority command and interlock
Out PCC OUT NODE, PCDeviceLib command and interlock
Appendix B Batch Control Module Reference How to use
3BEL300674D8007 Rev. A 125
How to use
The Use Case described in Figure 44, demonstrates the inside of Phase or Unit
Control Module type based on the BatchAdvTemplateLib.
It shows the Control Module and the PCC connections required to have the same
condition (level alarm on Transmitter) to cause the phase to do the exception
handling when the Equipment1 is under phase control and let the Transmitter1 act
directly on the Equipment1 when not under phase control..
Figure 44. pccInhibitBatch: Use Case
aspect system. If not so the the automatic generated faceplate might not work.
pccILockBatch Control Module Type Appendix B Batch Control Module Reference
126 3BEL300674D8007 Rev. A
pccILockBatch Control Module Type
Introduction
The pccILockBatch Control Module is used to extract Batch Interlocks from the
PCC input and set the corresponding interlock parameter to the batch core module.
Only batch interlocks relevant according to the current state of the Batch Core will
be extracted from the PCC input and forwarded.
The pccILockBatch control module contains the aspects:
PriorityInterlockCmd: A Faceplate Element for presentation and inhibit of
Priority Commands & Interlocks (See Figure 45).
Figure 45. pccILockBatch: PriorityCmdInterlock faceplate element
The pccILockBatch Control Module can be used to interface PhaseCore,
UnitCore or SharedEquipModuleCore Control Module Types from
ProduceITBatchLib.
The text describing the Batch Priority Commands & Interlocks can be altered.
These are defined in the NLS resource manager for PCDeviceLib with the
NLSID_PCC_Bit14 - 21 and NLSID_PCC_Bit25 - 28
Appendix B Batch Control Module Reference Introduction
3BEL300674D8007 Rev. A 127
Figure 46. pccILockBatch: Logic Diagram
The term Inhibit is used differently in PCDeviceLib and ProduceITBatchLib.
Inhibit in ProduceITBatchLib corresponds to interlock in PCDeviceLib, e.g.
InhibitRestart in ProduceITBatchLib is the same as ILockRestart. In
PCDeviceLib Inhibit is used to suppress active Interlocks (ILocks) and Priority
Commands (PriCmds). PCEquipmentLib uses terminology and functionality
similar to PCDeviceLib.
Currentstate = (Complete,
Stopped, Stopping, Aborted,
Aborting)
PCC.Action (ILockStart)
InhStat
Currentstate = (Idle) InhibitStart
PCC.Action (Execute)
InhibitPause
InhibitHold
InhibitStop
InhibitAbort
InhibitResume
InhibitRestart
InhibitReset
PCC.Action (ILockPause)
Currentstate = (Running)
&
&
&
&
&
&
&
&
PCC.Action (ILockReset)
&
Currentstate = (Stopped, Stopping,
Held, Holding)
&
&
PCC.Action (ILockHold)
&
PCC.Action (ILockStop)
&
PCC.Action (ILockRestart)
&
PCC.Action (ILockAbort)
PCC.Action (ILockResume)
Currentstate = (Paused, Pausing)
&
&
HSIInh
Inh
>=
Currentstate = (Paused, Pausing,
Held, Holding, Restarting, Running)
Held, Holding, Running, Stopped,
Stopping, Restarting)
Held, Holding, Running, Stopped,
Stopping, Restarting, Aborted,
Aborting)
&
128 3BEL300674D8007 Rev. A
Table 20. pccILockBatch parameters & variables
Description String[40] IN Exception description
PCC PCC IN Batch PCC Priority Commands and Interlocks to Batch
Core module
CurrentState Dint IN Current state. Connect to batch core parameter
Status.CurrentState
HSIInh Bool VARIABLE Inhibit activated by the operator
Inh Bool IN Inhibit of PriorityCommands & Interlocks from
application logic
InhStat Bool OUT Inhibit Active from Faceplate or Application logic
InhibitStart Bool OUT Connect to Phase/Unit Core.InhibitStart
InhibitPause Bool OUT Connect to Phase/Unit Core.InhibitPause
InhibitHold Bool OUT Connect to Phase/Unit Core.InhibitHold
InhibitStop Bool OUT Connect to Phase/Unit Core.InhibitStop
InhibitAbort Bool OUT Connect to Phase/Unit Core.InhibitAbort
InhibitResume Bool OUT Connect to Phase/Unit Core.InhibitResume
InhibitRestart Bool OUT Connect to Phase/Unit Core.InhibitRestart
InhibitReset Bool OUT Connect to Phase/Unit Core.InhibitReset
3BEL300674D8007 Rev. A 129
How to use
The following example shows how to let one of the alarm HHH/LLL alarm
conditions on PCDeviceLib transmitters cause an interlock of state change in a
phase / unit / shared equipment based on one of the templates from
In the following the term Batch Core is a synonym for one of the PhaseCore,
UnitCore, SharedEquipmentCore Control Modules from ProduceITBatchLib used
in the templates.
1. Create an instance of pccILockBatch Control Module Type inside the phase,
unit or shared equipment module based on one of the templates from
2. Connect one of the PCC parameters Transmitter:PCCHHH /
Transmitter:PCCLLL to the Parameter pccILockBatch:PCC.
3. Configure the Batch Interlock command that the transmitter has to send by
connecting by assigning a Batch PCC project constant to the
Transmitter:PCCHHHConf / Transmitter:PCCLLLConf parameter (See
PCEquipmentLib Project Constants, page 173)
4. Connect the pccILockBatch.Inhibitxxx parameters to the BatchCore.
5. Connect the pccILockBatch:CurrentState Parameter to the
BatchCore:Status.CurrentState parameter.
Remember to run NameUploader and then PCCUploader after adding/deleting or
User Permissions Appendix B Batch Control Module Reference
130 3BEL300674D8007 Rev. A
Figure 47. pccILockBatch: Use Case
User Permissions
dont have the listed permissions.
If the permission / authentication configuration is insufficient, the permission
Override Aspect on:
on all instances.
Table 21. pccILockBatch User permissions
Name Permission Description
HSIInh Tune Inhibit activated by the operator
Appendix B Batch Control Module Reference pccThrowExecption Control Module Type
3BEL300674D8007 Rev. A 131
pccThrowExecption Control Module Type
Introduction
The pccExceptionBatch module is used to throw a batch exception and forward a
corresponding interlock to the batch core module.
The interlock can be used to interlock a state change command to return to normal
state as long as the exception condition is active.
The pccExceptionBatch module shall be configured to monitor a batch priority
command. When the priority command is active on the input, an exception with
target state according to the priority command is thrown. A batch interlock will be
activated on the output as long as the priority command is active on the input.
The exception control module can e.g. be configured to monitor the priority
command PriCmdStop and forward the interlock ILockRestart. When the priority
command is active, an exception with target state Stop is thrown and the interlock
ILockRestart is activated on the output in order to prevent the user to reenter the
state while the condition is active.
Figure 48. pccThrowException Logic diagram
Out.Action
Activate
Batch Interlock
PCCExceptionConf
ExceptionSeverity
ExceptionID
Description
PCCExceptionConf
Throw
Batch Execption
& In.Action (bit 0 - 27)
In.Action (Execute)
PCCILockConf
PCCExceptionConf
& In.Action (bit 0 - 27)
In.Action (Execute)
In.Action
=>
Exception
132 3BEL300674D8007 Rev. A
Table 22. pccThrowException parameters
Description String[40] IN Exception description
ExceptionID String[10] IN ID of the Exception
ExceptionSev DInt IN The severity within TargetState
Exception BatchException IN OUT To be connected to the Exception parameter of Batch
Core module
In PCC IN NODE, Batch Priority command and interlock
PCCExceptionConf DWord IN Exception condition is active when this batch priority
command is active together with execute on input
(PriCmdPause, PriCmdHold, PriCmdStop, PriCmdAbort)
Out PCC OUT NODE, Batch Priority command and interlock
PCCIlockConf DWord IN Interlock activated on output when exception condition is
active (IlockResume, IlockRestart, IlockReset)
3BEL300674D8007 Rev. A 133
How to use
134 3BEL300674D8007 Rev. A
Single exception
1. Create an instance of pccExceptionBatch Control Module Type
2. Connect the PCC input e.g. HHH from a transmitter
3. Connect the PCC output to the next module
4. Connect the batch priority command being monitored and triggered the batch
exception
5. Connect the batch interlock forwarded to the batch core module
6. Connect the Severity, Identity and Description
7. Connect the Exception parameter to batch core module
8. Connect unique name
Figure 49. pccThrowException: Single Exception
3BEL300674D8007 Rev. A 135
Multiple exceptions
If multiple batch exceptions are implemented the exceptions should normally have
parallel PCC connections as shown in the example below. In this example, both of
the pccExceptionBatch control modules can monitor different exception conditions
with the same batch priority command, e.g. PriCmdStop. The implementation can
utilize the supported function to throw exceptions with different exception
parameters, i.e. different exception severity, exception identity or exception
description.
Note! Parallel PCC connections can handle multiple sets of exception parameters,
one set for each branch.
Figure 50. pccThrowException: Multiple batch exceptions in parallel branches
Multiple batch exceptions can be implemented using a serial PCC connection as
shown in the example below in the following configurations:
If the pccExceptionBatch control modules monitors different batch priority
commands.
If batch exceptions are implemented using identical exception parameters for
the same target state.
136 3BEL300674D8007 Rev. A
Figure 51. Multiple batch exceptions in a serial PCC connection
3BEL300674D8007 Rev. A 137
Multiple conditions
It is possible to configure one batch exception to be triggered by multiple exception
conditions as shown in the example below. In this example, the pccOrBatch control
module is used to add the batch priority commands together and the
pccExceptionBatch control module will be monitoring the result from the addition.
Figure 52. Multiple exception conditions
TaskPointer Control Module Type Appendix B Batch Control Module Reference
138 3BEL300674D8007 Rev. A
TaskPointer Control Module Type
Introduction
The TaskPointer Control Module can be used for 2 different purposes:
1. Show name of the active step in the phase Running SFC, - even if the phase
contains parallel execution.
2. Allow the operator to select between predefined restarting points in the phase
Running SFC when reentering the phase Running SFC. Restarting points are
created by dividing the phase Running SFC into a number of subsequences.
Each subsequence is called a Task. Each Task can be used as a restarting point.
The TaskPointer Control Module contains 2 graphic building blocks, intended to be
used in the phase faceplates:
TaskPointer Interaction (both change and presentation of current Task).
TaskPointer Presentation (only presentation of current Task).
Figure 53. TaskPointer faceplate graphical building blocks
If the phase is in state Held or interaction is enabled, the operator can select a
specific Task from the dropdown list as the restarting point, when the phase returns
to state Running.
In the controller each Task is identified by an integer value. The associated text is
defined in an aspect in the Libraries structure, PCEquipmentLib custumization in
order to make number of Tasks configurable and not to load to controller with text
handling.
Trough a parameter on the TaskPointer control module one or more Tasks can be
removed from the dropdown list and this preventing the operator from selecting
certain Tasks as restarting points. This Interlocking can be altered runtime.
Appendix B Batch Control Module Reference Introduction
3BEL300674D8007 Rev. A 139
See also PhaseBasicTemplate section Phase & Unit (Engineering Principles), page
43.
Figure 54. TaskPointer Logic diagram
Table 23. TaskPointer parameters
Name string[20] IN EDIT Name of the TaskPointer
InteractionPar TaskPointerPar IN OUT Runtime interaction parameters to/from logic
CurrentStat dint IN Connect to parameter Status.CurrentState on
PhaseCore/UnitCore/SharedEquipmentCore control module
type
==
&
6
CurrentState
==
1
IPar.EnableHSIConf
&
IPar.EnableHSI
==
2
IPar.EnableHSIConf
=> HSIEnabled
IPar.TP
HSITP
PreviusTP
HSITP
IPar.TP
Note: "IPar" is short for "InteractionPar"
140 3BEL300674D8007 Rev. A
Table 24. Elements in TaskPointerPar
TP dint IN OUT TaskPointer / Restarting point set by control logic /
HSI depending on EnableHSIConf and EnableHSI
ILockTP String[140] IN Space separated string (e.g. 1 2 5) containing the
restarting points which has to be removed from selection list
in HSI
EnableHSIConf dint IN 1= Selection from the dropdown list is enabled if
CurrentState = 6 (Held)
2 = Selection from the dropdown list is enabled when
EnableHSI = true
EnableHSI bool IN True Selection from drop down is enabled (see Par.
EnableHSIConf)
3BEL300674D8007 Rev. A 141
How to use
Runtime change of InteractionPar.ILockTP parameter
Be aware that the enable/disable of the Tasks will be updated with a delay equal
to OPC server transfer time of strings.
If the parameter InteractionPar.ILockTP is changed while the phase faceplate
containing the TaskPointer Interaction graphic is open and the transfer time is 10
seconds the selection list will be out of sync with the controller for 10 seconds.
Solutions:
Disable user interaction by means of the parameters InteractionPar.EnableHSI and
InteractionPar.EnableHSIConf in a period equal to the OPC string transfer time
every time the InteractionPar.ILockTP changes.
Change the string OPC transfer time to an appropriate time (Should be used with
caution , - can load the connectivity server significantly)
The set of integer values defining a Task set must always start with the value 1
and succeed with 2, 3, 4 etc. If this is not the case error message will be presented
in the associated graphics
142 3BEL300674D8007 Rev. A
TaskPointer used to define phase restarting points
This section describes how to use the TaskPointer Control Module to define and
present phase restarting points, in order to let the operator change which part of the
Running logic that has to be executed when the phase returns to state Running from
state Held.
See also section Faceplate Elements building block (TaskPointer Interaction), page
144.
The contents of Figure 55 is a screen dump of State Running SFC logic in the
PhaseBasicTemplate (Phase & Unit (Engineering Principles), page 43).
Figure 55. Part of phase running logic with restarting points
1. (Figure 55 ref. A,B,C) The sequential running logic of the phase is divided into
a number of subsequences each representing a Task (Figure 55 ref. I)) and
thereby also a restarting point.
2. Even though the Figure 55 SFC looks parallel,- it will be executed sequential
as demonstrated by the red arrow. If definition of restarting points is required
inside parallel executing SFCs the application engineer has to ensure that not
F) IPar.TP=1
H) IPar.TP=3
D) IPar.TP:=2;
G) IPar.TP=2
A) B) C)
I)
3BEL300674D8007 Rev. A 143
valid restarting points are interlocked by means of the parameter
InteractionPar.ILockTP. Alternatively use several TaskPointer Control
Modules.
3. When the state of the phase is different from Running, The Running SFC is
disabled. When the Running state becomes active the first active step will be
the initial step and not the last active step. This causes the execution of the SFC
to pass trough the Figure 55 step sTaskSwitch. To enter a certain Task, - the
value of the InteractionPar.TP needs to be equal to the value representing the
Task (Figure 55 ref. F, G, H). This ensures that only logic from the selected
Task and forward will be executed.
4. (Figure 55 ref. D) The last step in each Task sets the integer value of the next
task and then makes unconditional jump to the sTaskSwitch step (Figure 55 ref.
E).
5. (Figure 55 ref. F, G, H) IPar is an internal variable connected to the
InteractionPar parameter on the TaskPointer Control Module.
6. Define project constants to represent Tasks in order to make the code more
maintainable.
TaskPointer used to present phase step
This section describes how to use the TaskPointer Control Module to show the
name of the active SFC step in faceplates.
See also section Faceplate Elements building block (TaskPointer Presentation), page
146.
When using the TaskPointer Control Module for presentation purpose only, there is
no requirement to the layout of the SFC or even to use of an SFC !.
The faceplate element building block TaskPointer Presentation will show the text
associated with the value of the parameter InteractionPar.TP.
144 3BEL300674D8007 Rev. A
Faceplate Elements building block (TaskPointer Interaction)
The TaskPointer Control Module contains a Graphic Element aspect TaskPointer
Interaction, which can be integrated in Faceplate Elements aspects to allow the
operator to:
View current Task.
Change Task, if the user have the requested permission and the phase is in
state Held (parameter InteractionPar.EnableHSIConf = 1) or parameter
EnableHSI = True (InteractionPar.EnableHSIConf = 2) and inhibited
(Parameter. InteractionPar.ILockTP) can not be selected
The graphic element :
Contains 2 lines of information:
Line 1: Show active Task.
Line 2: Drop Down box for manual selection of Tasks.
quality.
Show error message, - if parameter InteractionPar.TP have a value
without any text assignment.
Have a fixed size that fits the width of standard faceplate,
Can be configured to show the integer value in front of the text.
Presentation or not of the integer value is control by the Library
Structure... PCEquipmentLib Custumizations config aspect entry
TaskPointerNumbersVisible
caption TaskPointer, can be changed either through NLS (affects all
instances) or on an instance to instance basis trough the Visual Basic
property ABB_Caption on the graphical element.
Figure 56. TaskPointer Interaction
3BEL300674D8007 Rev. A 145
How to use
1. Create new or select an existing faceplate element.
5. Find and select the instance of the TaskPointer Control Module.
6. Press Ok button.
7. Select the TaskPointer Interaction Graphic elements.
9. If the caption has to be instance specific modify the property ABB_Caption.
146 3BEL300674D8007 Rev. A
Faceplate Elements building block (TaskPointer Presentation)
The TaskPointer Control Module Type contains Graphic Element aspects
TaskPointer Presentation, which can be integrated in Faceplate Elements aspects to
allow the operator to view current Task.
The graphic element :
quality.
Show error message, - if parameter InteractionPar.TP have a value
without any text assignment.
Configured to show the integer value in front of the text. Presentation of
integer value is control by the Library Structure... PCEquipmentLib
Custumizations config aspect entry TaskPointerNumbersVisible
caption TaskPointer can changed either trough NLS (affects all instances)
or on an instance to instance basis trough the Visual Basic property
ABB_Caption on the graphical element.
Figure 57. TaskPointer Presentation
3BEL300674D8007 Rev. A 147
How to use
1. Create or select and existing faceplate element.
5. Find and select the instance of the TaskPointer Control Module.
6. Press Ok button.
7. Select the TaskPointer Presentation Graphic elements.
9. If the caption has to be instance specific modify the property ABB_Caption.
148 3BEL300674D8007 Rev. A
How to define Task texts :
1. Go to the Library Structure... PCEquipmentLib Custumizations.
2. Right mouse click on the Template TP_NewTaskPointerModule aspect.
3. Select Copy.
4. Right mouse click and select Paste.
5. Right mouse click on the copy of Template TP_NewTaskPointerModule aspect.
6. Select Config View.
7. Follow the instructions written inside this template aspect.
8. If only one TaskPointer control module is used per Phase globally in the
application then right mouse click on the copy of Template
TP_NewTaskPointerModule and select Rename. Give the aspect the name of
the TP_ + Phase Control Module Type Name of which the TaskPointer are
contained in.
9. Go to the Library Structure... PCEquipmentLib Custumizations select the
Config aspect and ensure that the entry TaskPointerSearchMethod=1.
10. Go to step 13.
11. If several TaskPointer Control Modules is used per Phase. Right mouse click
on the copy of Template TP_NewTaskPointerModule and select Rename and
give the aspect a name equal to the TP_ + instance name of the TaskPointer
control module in the phase control module.
12. Go to the Library Structure... PCEquipmentLib Custumizations select the
Config aspect and ensure that the entry TaskPointerSearchMethod=2.
13. No further configuration is required.
The HTML aspect can handle ISO 8859-1 characters. Complete list can be found
at http://www.htmlhelp.com/reference/charset/
Appendix B Batch Control Module Reference User Permissions
3BEL300674D8007 Rev. A 149
User Permissions
The internal variables listed in the Table 25 are updated from faceplate by user.
If the permission / authentication configuration is insufficient, the permission
Override Aspect on:
on all instances.
The instance in the Control Structure to override permissions of the specific
instance.
Table 25. TaskPointer User permissions
HSITP Tune Command from faceplate to change current TP.
User Permissions Appendix B Batch Control Module Reference
150 3BEL300674D8007 Rev. A
3BEL300674D8007 Rev. A 151
Appendix C Graphic Tools
This appendix describes a number of aspect used to present all devices, equipment
or phases located in the structure below.
Faceplate Element List Of Devices Appendix C Graphic Tools
152 3BEL300674D8007 Rev. A
Faceplate Element List Of Devices
Introduction
The Faceplate Element List Of Devices is an aspect that shows :
Name
Current Modes & States (Activated, Deactivated, Manual, Local, Track
(PID-Controller), Internal (PID-Controller), Test)
Summarized alarms
Presence of any Priority Command, Interlocks or Forced IO
Provides link to the faceplates of the device (by mouse click on the line in
the list).
The Faceplate Element List Of Devices is generated runtime. This can results in
long callup times. To build a list containing:fs
107 devices takes 12 seconds
18 devices takes 3 seconds.
Appendix C Graphic Tools Introduction
3BEL300674D8007 Rev. A 153
As a list containing all the devices that exist in the Control Structure below the
Object of the Faceplate Element List of Devices Aspect.
Figure 58. List Of Devices example
List Of Devices is pre configured to present devices from PCDeviceLib, but the
List Of Devices can easily be configured to show project developed devices as
well (See Presentation of Project Specific devices, page 157)
If device name = Dummy, - the device will not appear in the Faceplate Element
List Of Devices.
Introduction Appendix C Graphic Tools
154 3BEL300674D8007 Rev. A
The Faceplate Element List Of Devices uses the following icons for presentation.
Icon Description Icon Description
Visible when device is Stopped /
Closed
Visible when device is Running /
Open
Visible when Manual Mode or
Locked in Manual is active.
Visible when Interlock 0 or - 1 is
active
Visible when Priority Command 0, -1
or -2 is active
Visible when Inhibit is active.
Visible when Test mode is active
(Test mode= Output to device
suppressed and feedback from device
is simulated in accordance with the
command that the Device is
receiving from HSI or Control Logic.
Visible when the equipment contains
one of the following alarms Active
unacknowledged, not active not
acknowledge, active and
acknowledge, auto disabled.
If the alarm is disabled by the the
operator the icon will be invisible
Visible when Forced IO is present Visible when device is controlled
locally from the field.
Visible when the PID-Controller is in
Internal mode
Visible when the PID controller is in
Track mode
3BEL300674D8007 Rev. A 155
When the Aspect Faceplate Element List Of Devices is created on an object, the
Faceplate Element will automatically be populated with the devices that exist as
childs to the object in the Control Structure. The principle is described in the
following figure.
If placed on Unit1. The list will contain Valve 1, -2 & -3
If placed on Eq1. The list will contain Valve 1 & -2
If placed on Eq2. The list will contain Valve 3
Where to place Faceplate Element List Of Devices
Unit1
Eq1
Eq2
Valve1
Valve3
Valve 1,-2 & -3
Valve 1 & -2
Valve 3
Valve2
How to use Appendix C Graphic Tools
156 3BEL300674D8007 Rev. A
How to use
Faceplate Element
A Faceplate Element List Of Devices is created by:
Library Group,
5. Scroll down to the Aspect Faceplate Element List Of Devices.
6. Press Create.
Appendix C Graphic Tools How to use
3BEL300674D8007 Rev. A 157
Presentation of Project Specific devices
The Faceplate Element List Of Devices contains all instances of the device types
which are listed in the configuration aspect described in Figure 59
Figure 59. Faceplate Element List Of Devises configuration aspect
To edit the configuration aspect
1. Select on the Device Definition aspect from Figure 59
2. Right mouse click and select Config View
Remember to backup the Figure 59 Device Definitions aspect together with the
project if modified.
158 3BEL300674D8007 Rev. A
To create a project specific device in the configuration aspect.
1. Insert the contents of the Table 27 in the Device Definition aspect
2. Delete the "ABB_" entries not to be used, - but observe that:
ABB_Unit, - Value, - Fraction: has either to be together or not used.
ABB_FB012Conf: Must be used if ABB_FB0, - FB1 or FB2 is used.
3. Do not delete any of the special characters like "" </> used in the template.
4. See Table 28 concerning mapping of entries to icons and expected data types of
connected OPC properties.
Table 27. Device Template
<DeviceType Name="Control Builder Object Type Definition name"
ABB_AlarmState="Object Path: Aspect name: Property name"
ABB_AutoMode="Object Path:Aspect name: Property name"
ABB_DeviceName="Object Path:Aspect name: Property name"
ABB_FB012Conf="Object Path:Aspect name: Property name"
ABB_FB0="Object Path:Aspect name: Property name"
ABB_ForcedIO="Object Path:Aspect name: Property name"
ABB_ExternalMode="Object Path:Aspect name: Property name"
ABB_LocalMode="Object Path:Aspect name: Property name"
ABB_PriCmd="Object Path:Aspect name: Property name"
ABB_ILock="Object Path:Aspect name: Property name"
ABB_Inhibit="Object Path:Aspect name: Property name"
ABB_TrackMode="Object Path:Aspect name: Property name"
ABB_Unit="Object Path:Aspect name: Property name"
ABB_Value="Object Path:Aspect name: Property name"
ABB_Fraction="Object Path:Aspect name: Property name"
/>
3BEL300674D8007 Rev. A 159
The Faceplate Element List Of Equipment uses the following icons for presentation.
Table 28. Device Definition: Mapping of icons
Device Definition
Entry
Icon Comment
ABB_DeviceName Name of
device
Datatype string.
ABB_Value
ABB_Unit
ABB_Fraction
Value
associated
with device
Datatype real
Datatype string
Datatype dint
These entries make it possible to show a number to the left of the
Device Name with the specified unit and fraction.
ABB_Unit and ABB_Fraction is mandatory when ABB_Value is
used.
ABB_AutoMode Datatype bool.
Icon visible when ABB_AutoMode = False.
If manual mode not used on device set ABB_AutoMode = False
ABB_AlarmState Datatype dint.
ABB_Inhibit Datatype bool. Icon visible when true.
.
ABB_PriCmd Datatype bool. Icon visible when true.
ABB_ILock Datatype bool. Icon visible when true.
160 3BEL300674D8007 Rev. A
ABB_FB012Conf
ABB_FB0
ABB_FB1
ABB_FB2
Datatype dint
Datatype bool.
Datatype bool.
Datatype bool.
These 4 entries are used to control the activated and deactivated
icons.
ABB_FB012Conf is used to configure how the information
retrieved through ABB_FB0, - FB1, - FB2 is used.
Valid values of ABB_FB012Conf is:
1:
Deactivate icon visible when ABB_FB1 = false
Activate icon visible when ABB_FB1 = True
10:
Deactivate icon visible when ABB_FB0 = True
Activate icon visible when ABB_FB1 = True
120:
Deactivate icon visible when ABB_FB0 = True
Activate icon visible when ABB_FB1 = True or ABB_FB2 =
True
ABB_ForcedIO Datatype bool. Icon visible when true.
ABB_LocalMode Datatype bool. Icon visible when true.
ABB_TestMode Datatype bool. Icon visible when true.
Device Definition
Entry
Icon Comment
3BEL300674D8007 Rev. A 161
ABB_ExternalMode Datatype bool. Icon visible when ABB_ExternalMode = False.
If internal mode not used on device set ABB_ExternalMode =
False
ABB_TrackMode Datatype bool. Icon visible when true
Device Definition
Entry
Icon Comment
Faceplate Element List Of Equipment Appendix C Graphic Tools
162 3BEL300674D8007 Rev. A
Faceplate Element List Of Equipment
Introduction
The Faceplate Element List Of Equipment is an aspect that shows:
Name
Mode Of Operation as text and number (see Global configuration, page
175 and Faceplate Elements building blocks (ModeOfOperation), page
94)
Current Modes & States
Summarized alarms
Presence of any Priority Command or Interlocks
Provides link to the faceplates of the equipment (by mouse click on the
line in the list).
As a list containing all the equipment modules that exist in the Control Structure
below the Object of the Faceplate Element List of Equipment Aspect.
Figure 60. List Of Equipment example with and without mode of operation
3BEL300674D8007 Rev. A 163
The Faceplate Element List Of Equipment uses the following icons for presentation.
Table 29. Faceplate Element List Of Equipment Icons
Icon Description Icon Description
Visible when equipment module is
Stopped.
Visible when equipment module is
Running.
Visible when Manual Mode or
Locked in Manual is active.
Visible when any Interlock is active
Visible when any Priority Command
is active
Visible when Inhibit is active.
Visible when the equipment contains
one of the following alarms Active
164 3BEL300674D8007 Rev. A
When the Aspect Faceplate Element List Of Equipment is created on an object, the
Faceplate Element will automatically be populated with the equipment modules that
exist as childs to the object in the Control Structure. The principle is described in the
following figure.
If placed Area1. The list will contain Equipment 1, -2 & -3
If placed on Unit1. The list will contain Equipment 1 & -2
If placed on Unit2. The list will contain Equipment 3
Figure 61. Where to place Faceplate Element List Of Equipmentok
Area1
Unit1
Unit2
Eq1
Eq3
Eq1,-2 & -3
Eq1 & -2
Eq3
Phase1
Eq2
3BEL300674D8007 Rev. A 165
How to use
Control Module
Faceplate Element
A Faceplate Element List Of Equipment is created by:
Library Group,
5. Scroll down to the Aspect Faceplate Element List Of Equipment.
6. Press Create.
When building the equipment modules the following rules must be observed if the
Faceplate Element List Of Equipment shall work as described.
EqCore Control Module Type must be used to control modes and states.
The Equipment module itself must have an Alarm List Aspect by the name Alarm
List.
The Alarm List must be configured to filter for Object and decendents in
structure:Control Structure
Faceplate Element List Of Phases Appendix C Graphic Tools
166 3BEL300674D8007 Rev. A
Faceplate Element List Of Phases
Introduction
The Faceplate Element List Of Phases is an aspect that shows:
Name
Modes & States
Summarized alarms
Provides link to the faceplates of the Phase (by mouse click on the line in
the list).
As a list containing all the phases that exist in the Control Structure below the
Object of the Faceplate Element List of Phases Aspect.
Figure 62. List Of Phases example
3BEL300674D8007 Rev. A 167
The Faceplate Element List Of Phases uses the same icons as Produce IT Batch Lib
for presentation.
Table 30. Faceplate Element List Of Phases Icons
Icon Description
Visible when the Phase is acquired
(From Recipe, Faceplate or
Application)
Visible when the Phase is in manual
control from its faceplate.
Visible when the Phase is Completed Visible when the alarms contain one
of the following alarms: active
Visible when the Phase is Running or
Restarting
Visible when the Phase is Stopping or
Stopped
Visible when the Phase is Holding or
Held
Visible when the Phase is Pausing or
Paused
Visible when the Phase is Aborting
or Aborted
168 3BEL300674D8007 Rev. A
When the Aspect Faceplate Element List Of Phases is created on an object, the
Faceplate Element will automatically be populated with the phase modules that
exist as childs to the object in the Control Structure. The principle is described in the
following figure.
If placed Area1. The list will contain Phase 1, -2 & -3
If placed on Unit1. The list will contain Phase 1 & -2
If placed on Unit2. The list will contain Phase 3
Figure 63. Where to place Faceplate Element List Of Phases
Area1
Unit1
Unit2
Phase1
Phase3
Phase 1,-2 & -3
Phase 1 & -2
Phase 3
Phase2
3BEL300674D8007 Rev. A 169
How to use
A Faceplate Element List Of Phases is created by:
Library Group,
5. Scroll down to the Aspect Faceplate Element List Of Phases.
6. Press Create.
When building phases the following rules must be observed, if the Faceplate Element List
Of Phases shall work as described.
The Phase must be based up on the Control Module Type PhaseTemplate from
BatchAdvTemplateLib Control Module Type (The Faceplate Element List of Phases
searches for the PhaseCore Control Module Type).
The Phase object must have an Alarm List Aspect by the name Alarm List.
The Alarm List must be configured to filter for Object and decendents in
structure:Control Structure
170 3BEL300674D8007 Rev. A
3BEL300674D8007 Rev. A 171
Appendix D Configuration
Logical Colors
PCEquipmentLib uses existing logical color definitions in the system.
Table 31. Used Colors
Logical Color Definition Color Usage
Process Graphic Color FaceplateFg Foreground color in faceplates
FaceplateBg Background color in faceplates
AC800 MC Colors OnColor Used to indicate on, active etc.
LocalIndicationColor Used to indicate local mode.
ForcedIndicationColor Used to indicate forced mode
ManIndicationColor Used to indicate Object Error
Faceplate Colors Alarm Used to indicate Object Error
PCDeviceLib Colors TripILockIndicationColor Used to indicate PriCmd and Interlocks
NLS (Native Language Support) Appendix D Configuration
172 3BEL300674D8007 Rev. A
NLS (Native Language Support)
PCEquipmentLib supports NLS on all text presented in graphics and faceplates. All
text subject for translation is defined in the NLS Resource Manager aspect on
PCEquipmentLib object in the Object Type Structure.
This release only supports English (United States).
When other languages is required, please contact support (See Support, page 23) in
order to coordinate language implementation.
Figure 64. PCEquipmentLib NLS Resource Manager aspect
Some of the faceplate elements are inherited from ProduceITBatchLib and
PCDeviceLib. Change of language has to be done in the NLS resource managers
for these libraries.
Appendix D Configuration PCEquipmentLib Project Constants
3BEL300674D8007 Rev. A 173
PCEquipmentLib Project Constants
PCEquipmentLib uses project constants for configuration and inside logic to ensure
quality.
Project constants are grouped according to there expected use. The group
cPCEqLibPublic contains project constant intended to be used by the projects.
Figure 65. PCEquipmentLib Project Constant Groups
The group W (Writable) contains project constants which the application is
supposed to modify as a part of the configuration
The group RO (Read) contains project constants which the application is
supposed to use in the application, - but must under no circumstances be
modified.
The group cPCEqLibPrivate contains project used internally in PCEquipmentLib.
These are not to be used by the projects.
PCEquipmentLib Project Constants Appendix D Configuration
174 3BEL300674D8007 Rev. A
Table 32. PCEquipmentLib Project Constant Group BatchPCC
PCEquipmentLib expands the PCDeviceLib PCC Concept to also be able to issue
Batch state commands as well as interlock. The project constants in the group
BatchPCC has to be used to issue such commands and interlocks.
The project constants:
ILockxxx will prevent state changes to the mentioned state,
PriCmdxxx will cause a state change the to mentioned state, - if the command
is valid according to the current state of the phase, unit or equipment that the
command is issued to.
Appendix D Configuration Global configuration
3BEL300674D8007 Rev. A 175
Global configuration
In the Library Structure PCEquipmentLib contains an aspect by the name Config.
This aspect is used to make a general runtime configuration of PCEquipmentLib.
Figure 66. PCEquipmentLib Config aspect
Global configuration Appendix D Configuration
176 3BEL300674D8007 Rev. A
The following settings can be altered trough the Config aspect.
MOPVisibleFaceplateElementListOfEquipment:
This setting affect all instances of Faceplate Element List Of Equipment.
True = The aspect will contain 2 lines of information for each equipment module.
Line 1: Equipment name
Line 2: Current Mode Of Operation
False = The aspect will contain 1 line of information for each equipment module.
Line 1 = Equipment name
MOPNumbersVisible:
This setting is affect all instances of the aspects
EqCore:ModeOfOperation
EqCore:ModeOfOperationConfPar
FaceplateElementListOfEquipment
True = Both the MOP number and the MOP Text will be visible.
False = Only MOP text is visible.
Presentation of the MOP number together with MOP text can be very useful during
test and commissioning.
3BEL300674D8007 Rev. A. Printed in Sweden DraftMonth Year
Copyright 1999 by ABB. All Rights Reserved
Registered Trademark of ABB.
Trademark of ABB.
Automation Technology Products
Mannheim, Germany
www.abb.de/processautomation
email: marketing.control-products@de.abb.com
Vsters, Sweden
www.abb.com/processautomation
email: processautomation@se.abb.com
Wickliffe, Ohio, USA
www.abb.com/processautomation
email: industrialitsolutions@us.abb.com
http://www.abb.com/control

PCEquipmentLib 1.3-0 Engineering Guidelines 3BEL300674D8007 Rev A PDF

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

PCEquipmentLib 1.3-0 Engineering Guidelines 3BEL300674D8007 Rev A PDF

Caricato da

Copyright:

Formati disponibili

ATPA Industrial

Potrebbero piacerti anche