ABB Control ProcMan

ControlITAC 800M/C Version 3.2

Binary Process ControlObjects and Design

www.cadfamily.com EMail:[email protected] document is for study only,if tort to your rights,please inform us,we will delete

www.cadfamily.com


www.cadfamily.com

Binary Process ControlObjects and Design

ControlITAC 800M/C

Version 3.2


www.cadfamily.com

NOTICEThe information in this document is subject to change without notice and should not beconstrued as a commitment by ABB. ABB assumes no responsibility for any errors thatmay appear in this document.

In no event shall ABB be liable for direct, indirect, special, incidental or consequentialdamages of any nature or kind arising from the use of this document, nor shall ABB beliable for incidental or consequential damages arising from use of any software or hard-ware described in this document.

This document and parts thereof must not be reproduced or copied without written per-mission from ABB, and the contents thereof must not be imparted to a third party nor usedfor any unauthorized purpose.

The software or hardware described in this document is furnished under a license andmay be used, copied, or disclosed only in accordance with the terms of such license.

Copyright © 1999 ABB All rights reserved.

Release: September 2002Document number: 3BSE 028 810 R101 Rev A

TRADEMARKSRegistrations 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.


www.cadfamily.com

wwwThe

TABLE OF CONTENTS

About This BookGeneral ..............................................................................................................................7

Target Group...........................................................................................................7

Purpose, Scope, and Intended Use .........................................................................7

Document Conventions .....................................................................................................9

Terminology.....................................................................................................................10

Section 1 - Process Object LibrariesIntroduction .....................................................................................................................13

The Concept .........................................................................................................13

Choosing a Process Object...................................................................................16

Basic and Extended Libraries ..........................................................................................17

Process Object Basic Libraries ........................................................................................18

Overview .............................................................................................................18

About Core Objects..............................................................................................18

UniCore .. .............................................................................................................20

BiCore .... .............................................................................................................31

DriveCore .............................................................................................................46

Process Object Extended Library ....................................................................................49

Overview .............................................................................................................49

About the Extended Process Objects ...................................................................50

Uni.......... .............................................................................................................51

ValveUni. .............................................................................................................56

Bi ............ .............................................................................................................60

MotorUni .............................................................................................................66

MotorBi .. .............................................................................................................72

3BSE 028 810 R101 Rev A 5.cadfamily.com EMail:[email protected] document is for study only,if tort to your rights,please inform us,we will delete

www.cadfamily.com

Table of Contents

wT

Section 2 - Object HandlingGeneral ............................................................................................................................ 78

Basic Faceplate Elements .................................................................................... 82

Bi Faceplate Elements.......................................................................................... 86

MotorBi Faceplate Elements................................................................................ 88

MotorUni Faceplate Elements ............................................................................. 91

Uni Faceplate Elements ....................................................................................... 94

ValveUni Faceplate Elements .............................................................................. 96

Section 3 - Object Handling ExamplesAdding Functionality to a Process Object in Control Builder ........................................ 98

Creating a New Library and Copying an Object.................................................. 98

Adding Functionality ......................................................................................... 102

Editing a Faceplate in Process Portal A ........................................................................ 105

Copying and Deploying Aspects ....................................................................... 105

Editing a Faceplate............................................................................................. 108

Using a Faceplate in Online Mode..................................................................... 114

Appendix A - Displaying Element Icons

Appendix B - Signal ObjectsGeneral .......................................................................................................................... 119

Faceplate Elements........................................................................................................ 119

SignalBool ......................................................................................................... 120

SignalInBool ...................................................................................................... 122

SignalInReal....................................................................................................... 124

SignalOutBool ................................................................................................... 128

SignalOutReal .................................................................................................... 130

SignalReal .......................................................................................................... 134

INDEX

6 3BSE 028 810 R101 Rev Aww.cadfamily.com EMail:[email protected] document is for study only,if tort to your rights,please inform us,we will delete

www.cadfamily.com

wwwThe

About This Book

General

Target Group

This document is primarily intended for those who use Control Builder M to develop control systems. It is assumed that the user has general knowledge regarding the design of control systems, as well as basic knowledge on how to use Control Builder M.

Purpose, Scope, and Intended Use

This publication is intended as a reference manual when using the Process Object libraries.

Refer to Control Builder M, when Control Builder is mentioned in this manual.


www.cadfamily.com

Purpose, Scope, and Intended Use About This Book

wT

Use of Warning, Caution, Information, and Tip IconsThis publication includes Warning, Caution, and Information icons where appropriate to point out safety related or other important information. It also includes Tip icons to point out useful hints to the reader. The corresponding symbols should be interpreted as follows:

Although Warning notices are related to personal injury, and Caution notices are associated with equipment or property damage, it should be understood that the operation of damaged equipment could, under certain operational conditions, result in impaired process performance leading to personal injury or death. It is, therefore, imperative that you comply fully with all Warning and Caution notices.

The electrical warning icon indicates the presence of a hazard that could result in electrical shock.

The warning icon indicates the presence of a hazard that could result in personal injury.

The caution icon indicates important information or warnings related to the concept discussed in the text. It might indicate the presence of a hazard that could result in corruption of software or damage to equipment/property.

The information icon alerts the reader to pertinent facts and conditions.

The tip icon indicates advice on, for example, how to design your project or how to use a certain function


www.cadfamily.com

About This Book Document Conventions

wwwThe

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

• The words in names of screen elements (for example, the title in the title bar of a window, the label of 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 in boldface 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 should 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 Courier font, and user responses/input are shown in 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 instructed to enter the string TIC132 in a field. The string is shown as follows in the procedure:

TIC132

Variables are shown using lowercase italicized letters.

SequenceName


www.cadfamily.com

Terminology About This Book

wT

TerminologyThe following is a list of terms associated with Binary Process Control, that you should be familiar with. The list contains terms and abbreviations that are unique to ABB or have a usage or definition that is different from standard industry usage.

Term Description

AC 800M/C Connect A software package used to integrate Control Software for AC 800M/C with the Aspect Integrator Platform (AIP). AC 800M/C Connect can be installed from the ControlIT for AC 800M/C Products CD-ROM.

Applications Applications contain the program code to be compiled and downloaded for execution in the controller. Applications are displayed in the Project Explorer.

Aspect An aspect is a description of some properties of an Aspect Object. Examples of aspects are name, circuit diagram, process display, and control logic.

Aspect Objects A computer representation of a real object such as a pump, a valve, an order or a virtual object such as a service or an object type. An Aspect Object is described by its aspects and is organized in structures.

Control Builder M The programming tool described in this manual, referred to as Control Builder throughout this document.

Control module Control modules are program units that support object-oriented data flow programming with code sorting, free-layout graphical programming and static parameter connections. Instances of control modules are created from control module types.

Display Element A graphic element, which illustrates an object (motor, regulator etc.). Generally, clicking the element will show a faceplate for supervision and control of the object.

Faceplate A configurable type of graphic interface normally used by operators for process supervision and control.


www.cadfamily.com

About This Book Terminology

wwwThe

Plant Explorer Similar to the Internet Explorer and used to create Aspect Objects. You can also use it to browse and search among the structures of the plant.

Process Portal A Name of the collection of products for daily operation and supervision of an automated process.

Program A program contains execution code.

Project Explorer The part of the Control Builder user interface used to create, modify and navigate a project. All objects such as data types, functions and function block types can be selected and displayed in an editor. All software and hardware is configured in the Project Explorer

ST Structured Text, one of the five languages defined in the IEC-61131 standard.

Structure A hierarchical tree organization of aspect objects that describes the dependencies between the real objects. An aspect object can exist in multiple structures, for example, both in a functional structure and in a location structure,

Type The type is a general description of a unit that defines the behavior of an instance of the type.

Term Description


www.cadfamily.com

Terminology About This Book

wT


www.cadfamily.com

wwwThe

Section 1 Process Object Libraries

IntroductionThe Process Object libraries provide function blocks and control modules to define valve and motor objects in your application. ProcessObjBasicLib and ProcessObjExtLib, form parts of the Control Builder, Basic, Standard, or Professional products. The Process Portal A user interface is part of the AC 800M/C Connect product.

The Concept

Within the field of automation, there is a need for scalability, even down to single process objects. Objects must be so small and fit so smoothly, that they do not interfere with a programmers own valve or motor parameters, but still intelligent enough to work directly by themselves, without any additional programming costs. There is a need for a general function block base, a core function that fits all valve and motor objects in all industrial control applications. Since all valve and motor objects need at least uni- or bi-directional control, objects with these properties make up the core of all our process objects.

Process objects can be used directly in the application as they are, but are intended to be used as templates, when new valve or motor object types are to be created in your own library or application.

The smallest common denominator is the BiCore function block type, for the uni-directional object types (see BiCore on page 31), and the UniCore function block type, for the bi-directional object types (see UniCore on page 20). Furthermore, there are other object type templates, designed on the BiCore and UniCore types, with greater functionality. This makes it easier for the user to define his or her own object types, for example, motor types.


www.cadfamily.com

The Concept Section 1 Process Object Libraries

wT

The Core object (of BiCore or UniCore type) is protected and is part of all object types, so the core is not copied when a process object type is copied. The Core refers (points) to its type in ProcessObjBasicLib. This means that the Core is updated when the Control Builder is upgraded.

Figure 1. The core functionality in ProcessObjExtLib and in a user’s own library.

When a new process object type is to be defined, select an appropriate process object type template (see Choosing a Process Object on page 16) and copy it to a user’s created library. It is then possible to add extra functionality to the copied object type and/or adjust the faceplate to suit the application.

To avoid problems when upgrading, place the copy of the process object type in your own library and then make the changes.

ProcessObjBasicLib must always be included in your project together with the process object types you have created. ProcessObjExtLib may be excluded.

The user’s own created library

Note! Must always be included

May be excluded


www.cadfamily.com

Section 1 Process Object Libraries The Concept

wwwThe

Each process object type in ProcessObjExtLib has a faceplate displaying graphics in the Process Portal A. The process object types and faceplates are connected to each other. There are two options.

• Do not create a new type (use one from ProcessObjExtLib), in which case you may not change the faceplate of the type.

• Create your own type from an object type template, allowing you to design your own faceplates.

If a function block or control module is created directly from a type in ProcessObjExtLib and the faceplate of its type is changed in Process Portal A, the faceplate may be corrupted by upgrades of Control Builder versions. It is therefore recommended that you not edit the existing faceplate elements of the original process object types directly, but add your own faceplate elements (or delete existing ones). You may edit or add functionality to the graphics of these faceplate elements (tabs). This is described in Editing a Faceplate in Process Portal A on page 105.


www.cadfamily.com

Choosing a Process Object Section 1 Process Object Libraries

wT

Choosing a Process Object

In choosing a process object, you must first decide whether a function block type or a control module type is to be used.

If the process object is intended to be applied to a bi-directional object (an object with three states) and it is a motor, choose the MotorBi type. If it is a bi- directional object, but not a motor, choose the Bi type.

If the process object is to be used for a uni-directional object, (an object with two states) several choices are possible. If it is not a motor or a valve, choose the Uni object type. If it is a uni-directional motor object, choose MotorUni and if it is a uni-directional valve object, choose MotorValve.

Figure 2. Flowchart of possible process object type choices.

Bi/Uni

Motor/Valve

Motor

Bi

Uni

NoBi

MotorBi

Yes

No Uni

Yes

No ValveUni

MotorValve

Yes

Motor


www.cadfamily.com

Section 1 Process Object Libraries Basic and Extended Libraries

wwwThe

Basic and Extended LibrariesProcess objects are contained in two libraries:

• Process Object Basic Library

• Process Object Extended Library

The Basic Library contains core types for process objects, that is types for calculations (BiHSI and UniHSI), uni- or bi-directional control (UniCore and BiCore) and DriveCore for ABB drives.

The Extended Library is the more comprehensive library of the two. It comprises ready-to-use valve and motor objects, alarm handling functionality and templates for user-designed valve and motor objects. There is an additional selection of control modules for high-level graphical configuration; they are integrated with both Control Builder Professional and Process Portal A faceplates.

Many parameters are common to all objects, and are therefore referred to and explained only in the Core section. The reader is therefore advised to start by reading the UniCore and BiCore sections, and then continue by reading about specific parameters in the description of the extended library.

It is only possible to use control modules in Control Builder Professional.


www.cadfamily.com

Process Object Basic Libraries Section 1 Process Object Libraries

wT

Process Object Basic Libraries

Overview

This library contains the core objects for all process objects. The code that may not be changed by the programmer is located in a protected sub-object, denoted by the suffix “Core”.

The following core objects can be applied in process objects:

• UniCore, for uni-directional objects:

– UniHSI, for uni-directional HSI support

• BiCore, for bi-directional objects:

– BiHSI, for bi-directional HSI support

• DriveCore for ABB Drive Control

About Core Objects

All core objects (sub-objects) have protected code. The user can neither see nor access the code, modify it nor change it; instead the function blocks have parameters for providing a means of interaction in the code.

The two basic function blocks, UniCore and BiCore, do not contain any Control Builder graphics or Process Portal A graphics. However, they have parameters for interaction with the graphics operator panel. UniCore and BiCore are used to provide Process Portal A graphics with the necessary signal information.

UniCore and BiCore are used in two new function blocks (see Uni and Bi in Process Object Extended Library on page 49) that include an alarm and a Control Builder graphics interaction window, as well as a Process Portal A graphics icon (display element) and faceplates. Control Builder graphics interaction windows are connected to local variables in function blocks and these variables are then connected to parameters for manual interaction in the basic function block.


www.cadfamily.com

Section 1 Process Object Libraries About Core Objects

wwwThe

Function blocks (Uni and Bi) with alarms and graphics do not provide functions for manual interaction like, such as Set to Manual mode, and therefore changes cannot be made in the code (only from the graphics window in Control Builder or from Process Portal A graphics).

One parameter Set object in Auto mode is accessible from within the code. The function blocks UniHSI and BiHSI can then be used to access the information to be displayed in faceplates and to display elements on an operator workstation.

Edge Detection

Edge detection takes place on the positive rising edge. When using the two basic function blocks UniCore and BiCore, with operator interactions connected to parameters, the programmer must reset signals to false.

In function blocks with an alarm, the signals are reset inside the function block, as it is a local variable connected to the Control Builder graphics or Process Portal A graphics.


www.cadfamily.com

UniCore Section 1 Process Object Libraries

wT

UniCore

This process object should be used for uni-directional objects (objects with two states). UniCore can be used to control a generic process object via a number of predefined outputs and feedback signals (inputs). Uni means that the process object can be either activated or deactivated. For a valve (or a motor) this would mean running in one direction (uni-directional) or being closed (stopped).

UniCore parameters are divided into the following types:

• Operation

– Mode

– Configuration of feedback signals

– Simulation

• Interlocking

– Ilock

– Safety command

– Inhibit

• Object Error

UniCore function block


www.cadfamily.com

Section 1 Process Object Libraries UniCore

wwwThe

OperationThis subsection describes the operational parameters of the UniCore object. Users may configure feedback signals, set object error time, and disable error handling. The PulseOut parameter governs whether outputs should be pulsed or level, depending on the hardware used for the process object in question.

• Mode

UniCore has five different operation modes: Disable, Manual, Auto, Panel, and Local.

Only Manual mode and Auto mode have output parameters (ManMode and AutoMode). The ManMode or the AutoMode parameter is always set (even if the object is in another mode). One of these modes (Manual or Auto, depending on which parameter is set) will resume control after returning from another mode. AutoMode is equal to NOT ManMode.

ManMode has a retain attribute, which allows the status to be retained at warm start.

Manual mode is set as the default start-up mode using the parameter ManModeInit. The initial value is set to true, meaning that Manual will be the default mode. The parameter ManModeInit is copied to the parameter ManMode at every cold start.

– Disable Mode - Deactivates the object

The object is deactivated when the Enable parameter is set to false, signifying that the function block will not be executed. The output parameters Out1, Out0, Out1Level, StatAct, StatDeact, and ObjErr will all be reset to false, independent of the status of other signals. The object can be activated or deactivated in all modes.

– Manual Mode - A user operates the object from a workstation

To change to Manual mode, trigger the SetMan parameter and the ManMode parameter will automatically be set to true. Output signals (Out1, Out0, Out1Level) will retain their status from the previous mode.

In the Manual mode, the status of the output signal is controlled by the parameters ManCmd1 and ManCmd0. These parameters have rising edge detection.

All parameters mentioned above (SetMan, ManCmd0, ManCmd1) are normally connected to the operator faceplate via the application.


www.cadfamily.com


wT

– Auto Mode - The program controls the object

Auto mode is set by means of the parameter SetAuto. The status of the output signals (Out1, Out0, Out1Level) in Auto mode is controlled by the parameters AutoCmd1 and AutoCmd0. AutoCmd0 has higher priority than AutoCmd1.

The AutoCmd1 and AutoCmd0 parameters are level detected, therefore these parameters affect the output signal, as long as they are active. The programmer is required to reset these parameters from the application program outside the function block. These parameters act on Out1Level according to diagram below.

Figure 3. Status relations for Out1Level and the Auto commands.

When returning to Auto mode from another mode, the status of the output signals will be returned from the previous mode, but adjusted directly by the signals AutoCmd1 or AutoCmd0, if one or both are set to true.

– Panel Mode - The object is controlled locally from an LCP (Local Control Panel), via the UniCore function block

The function block has a set of signals for maneuvering the object from an LCP. Setting the PanMode parameter activates Panel mode. The PanMode parameter is level detected.

AutoCmd1

AutoCmd0

Out1Level

*

* Reset after function block in application program. AutoCmd0 has priority.


www.cadfamily.com


wwwThe

This mode is active only as long as the PanMode parameter is true. If PanMode is changed to false, the system exits Panel mode immediately, and return to the previous Auto or Manual mode.

Whether or not Panel mode is used depends on comprehensive the application is. The question is whether you prefer to initiate control (the parameter PanMode) of the object from a workplace, or from a switch on an LCP. The latter is a natural choice for smaller applications. The PanMode parameter is connected to the switch on the LCP; PanCmd1 and PanCmd0 are connected to the Start/Stop buttons (see Figure 4).

Figure 4. Control steps in Panel mode. This solution is recommended for small applications, where all three panel parameters are connected from an LCP.

However, in large applications, this option can cause a number of undesirable events. In this case, the best solution is to connect the PanMode parameter, via variables, to a faceplate at the operator workplace. The PanCmd1 and PanCmd0 parameters are still connected to the physical Start/Stop buttons. Changes in the Panel mode are therefore approved centrally, that is, a local operator must first obtain permission from the central control operator (see Figure 5).

LCP

PanMode

PanCmd1

PanCmd0

Process objectMotor

Start

Stop

Controller

Switch


www.cadfamily.com


wT

Figure 5. Control steps in Panel mode. This solution is recommended for large applications, where

the PanMode parameter is connected to an operator workplace.

When Panel mode is active, the LCP takes control of the object and errors are calculated based on status signals from the LCP. The output signal retains its status from the previous mode.

The status of the object is controlled by the signals PanCmd1 and PanCmd0, which are level signals and function in the same way as AutoCmd signals, as illustrated in Figure 3. The PanCmd1 and PanCmd0 parameters should be connected to push buttons. It may be advisable to use an R_Trig function block (trigger, parameter and push button) between PanCmd1 and PanCmd0, in case the push button malfunctions.

LCP

PanMode

PanCmd1

PanCmd0

Process objectMotor

Operator workplace

Switch on screen

Start

Stop

Controller


www.cadfamily.com


wwwThe

– Local Mode - The object is controlled locally from a Local Control Panel (LCP), bypassing the UniCore function block

Local mode is used when the object is controlled locally from an LCP and the function block does not have any signals for controlling the object from the LCP. All signals from the LCP are physically connected directly to the object (motors, valves, etc.), see Figure 6.

In this mode, the object status is not updated inside the function block, even if it is changed in reality. SafetyCmd signals may still change the object status. All error calculation is disabled. Objects return to the previous mode when local mode is disabled.

Figure 6. Control steps in Local mode.

The object status is not updated in Local mode. This means that after leaving Local mode, the output signal status is the same as before entering Local mode.

If the status of the function block tracks feedback signals, this must be implemented outside the function block, for example by setting the corresponding Safety Command signal.

LCPMotor

Start

Stop

Switch

LocMode

Process object


www.cadfamily.com


wT

• Configuration of Feedback Signals

The parameter FBConfig informs the function block how feedback is configured, by transferring the combination of feedback signals of the object to the function block. Possible combinations of feedback signals are listed in the table below:

The values of the feedback signals FB1 and FB0 are transferred to the StatAct and StatDeact output parameters respectively, in condition with Out1Level.

If an object has no, or only a single, feedback signal, StatAct and StatDeact will still be set. The signals StatAct and StatDeact are set to zero if double feedback is used and both are true at the same time.

• Output Settings

The output signals include Out1, Out0 and Out1Level. Out1 and Out0 can be configured as pulsed command or level-detected command, by means of the PulseOut parameter.

The pulse is sustained by the parameters Out1 and Out0, until the corresponding feedback is detected or the maximum object error time is exceeded.

Out1Level is intended to indicate the output state when the Out1 and Out0 parameters are pulsed.

Table 1. Possible combinations of feedback signals

FBConfig Feedback from activated position Feedback from deactivated position

0 FB1 FB0

1 FB1 (none)

2 FB1 inverted (none)

3 FB1 inverted FB0 inverted

4 (none) FB0

5 (none) FB0 inverted

6 (none) (none)


www.cadfamily.com


wwwThe

If there is no feedback from a position, the pulse duration is set to the object error time. Only one pulse is generated upon each status change.

• Simulation

When the parameter Simulate is activated, the object error calculation is disabled and the Out1 and Out0 signals are set to false. The signals StatAct and StatDeact are set according to the status of Out1Level.

Interlocking

This subsection describes the safety parameters for the UniCore object. The main purpose of the interlocking parameters is accurate and safe operation with critical process values, such as high levels and temperatures, MCC interface, safety devices etc.

• Ilock - Prevents the object from entering a certain state

The Ilock1 and Ilock0 signals block manual interactions in Manual and Panel mode (not in Auto mode) to switch the object to the activated and deactivated state respectively. The Inhibit signal will reset interlock signals, when true.

• Safety Command - Compels the object to enter a certain state

The SafetyCmd1 and SafetyCmd0 signals force the output to the respective status with priority over other signals, except when the Inhibit signal is set to true. When these signals disappear, the status from safety state is transferred to the current mode.

• Inhibit - Cancels all Ilock and SafetyCmd signals

When the Inhibit signal is set to true, the program will ignore all Ilock and SafetyCmd signals. This parameter can be used when there is an absolute need for running the object, although all Ilock and SafetyCmd signals are cancelled. When the Inhibit signal returns to false, the Ilock and SafetyCmd are re-activated to their former state.

When simulation is deactivated, the status of the object reverts to that in the mode prior to simulation and the Out0 signal is set to true.


www.cadfamily.com


wT

Object Error

The object error (ObjErr) is supervised in all modes except Disable and Local mode, based on the values of the parameters Out1Level, FB1 and FB0.

The object error is calculated by the ACOF (Automatic Check Of Feedback) function block, from the standard SystemLib library, and the error signal from the parameter ExtErr (external error) to give the parameter ObjErr.

The parameter ExtErr provides the possibility of connecting other errors to the object. This parameter does not affect the object status. If required, it must be implemented outside the UniCore, for example, by connecting a variable to both parameters ExtErr and SafetyCmd0. See the Uni function block section for an example.

The information required for the object error calculation is the object error time and the number of feedbacks: these two parameters have to be configured by the user (the parameters OETime and FBConfig).

OETime has an initial value of 5 seconds. In the Extended Library a variable is connected the value of which overrides the initial value. The value of OETime can be altered online, in the interaction windows (Control Builder) or in the Process Portal A faceplate. The connected variable has a cold retain attribute to retain the value following cold or warm restarts.

• Alarm - Not available for UniCore

Interaction Windows

Not available for UniCore.

Faceplate Elements

Not available for UniCore.


www.cadfamily.com


wwwThe

UniHSI

UniHSI is a basic function block which supports the faceplate and display elements for UniCore in the Process Portal A graphical environment. This function block calculates the information to be presented in display elements and faceplates in the operator graphical environment. The function block is used in the control modules or function blocks, together with UniCore, when an operator display element is to be used.

The UniHSI function block must be executed before the UniCore itself.

All input parameters to the UniHSI function block that have the same names as the input parameters to UniCore (for example FBConfig, FB1, FB0 etc.) should contain the same information as in the UniCore.

Note that AutoMode for UniHSI is to be connected to the AutoMode output parameter at the UniCore.

In normal cases, the bool type parameter that obtains input from the hardware I/O, is connected via a variable/parameter with BoolIO data type, for example, FB1 and Out1. The BoolIO data type is a structured data type with Value, IOValue and Force as the components. The value is connected to the FB1 parameter and forced to FB1Forced.

Figure 7. Connection diagram forUniHSI, UniCore and BoolIO.

UniHSI function block

BoolIOFB1

FB1Forced

FB1

UniHSI

UniCoreValue

Forced

FB1.Forced

FB1.ValueFB1


www.cadfamily.com


wT

• Effective Feedback

The EffectiveFB1 and EffectiveFB0 parameters, of the in/out type, give the calculated result from FBConfig and the values of FB1 and FB0.

Effective feedback signals are connected to the faceplate and are displayed under the Status tab.

• Output IOLevel

The parameter Out1IOLevel, of the in/out type, is the result calculated from the actual values of the binary I/O (Out1IO, Out0IO), in relation to the selected pulse functionality.

Figure 8. OutputIOLevel state diagram.

The output signals are connected and displayed in the Process Portal A faceplate.

• Interlock

The parameter Interlock, of the in/out type, is the sum of parameters SafetyCmd and Ilock. The Interlock parameter provides information when any type of interlocking is active (for example, SafetyCmd or Ilock).

The interlock signals are connected and displayed in the Process Portal A faceplate.

• Forced Action

The parameter Forced, of the in/out type, indicates the forced status of the Out0IO and Out1IO signals at FB0 or FB1. If one of these four I/O signals is blocked/forced, the parameter Forced, of the in/out type, will be true.

Out1IO

Out1IOLevel

Out0IO


www.cadfamily.com

Section 1 Process Object Libraries BiCore

wwwThe

BiCore

This process object is intended to be applied to two- directional objects, that is, objects with three states (for example (0) stop, (1) start/forward and (2) start/back).

The object has pulse output selection and feedback configuration, to allow configuration of the number of feedbacks and inversions.

Examples of applications are two-speed motors and forward/backward motors.

BiCore function block


www.cadfamily.com

BiCore Section 1 Process Object Libraries

wT

Operation

This subsection describes the operational parameters of the BiCore function block. You can configure feedback signals, set object error time and disable error handling. The PulseOut parameter governs whether the outputs are pulsed or level, depending on the hardware used for the process object in question.

• Mode

The BiCore function block has the same operation modes as the UniCore, see UniCore on page 20.

Only Manual mode and Auto mode have output parameters (ManMode and AutoMode). The ManMode or AutoMode parameter is always set, (even if the object is in another mode). One of these modes (ManMode or AutoMode) will resume control upon returning from another mode. AutoMode is equivalent to NOT ManMode.

ManMode has a retain attribute, which means the status is retained following a warm restart.

The Manual mode is set as default at start-up by setting the parameter ManModeInit to true. The parameter ManModeInit is copied to the parameter ManMode following cold start.

– Disable Mode - Deactivates the object

The object is deactivated when the Enable parameter is set to false, signifying that the function block is not executed. The output parameters Out1, Out2, Out0, Out1Level, Out2Level, StatAct1, StatAct2, StatDeact, and ObjErr are all reset to false, regardless of the status of other signals. The object can be activated or deactivated in all mode.s


www.cadfamily.com


wwwThe

– Manual Mode - A user controls the object from a workstation

To change to Manual mode, trigger the SetMan parameter and the ManMode parameter will automatically be set to true. The output signals (Out1, Out2, Out0, Out1Level, Out2Level) will retain their status from the previous mode.

In Manual mode the status of the output signal is controlled by the parameters ManCmd1, ManCmd2 and ManCmd0. These parameters have rising edge detection.

All the parameters above (SetMan, ManCmd0, ManCmd1, ManCmd2) are normally connected in the application to the operator faceplate.

– Auto Mode - The program controls the object

The Auto mode is set by the parameter SetAuto. The status of the output signals (Out1, Out2, Out0, Out1Level, Out2Level) in Auto mode are controlled by the parameters AutoCmd1, AutoCmd2, and AutoCmd0. AutoCmd0 has higher priority than both AutoCmd1 and AutoCmd2.

The AutoCmd1, AutoCmd2 and AutoCmd0 parameters are level detected, and therefore these parameters affect the output signal as long as they are active. The programmer is required to reset these parameters from the application program outside the function block. These parameters act on Out1Level or Out2Level according to Figure 9.


www.cadfamily.com


wT

Figure 9. Status relations of Out1Level and the Auto Commands.

When returning to Auto mode from another mode, the status of the output signals is retained from the previous mode, but adjusted directly by the signals AutoCmd1, AutoCmd2 or AutoCmd0, if one or more is set to true.

– Panel Mode - The object is controlled locally from an LCP (Local Control Panel), via the BiCore function block

The function block has a set of signals allowing control of the object from an LCP. Setting the PanMode parameter, which is level detected, activates Panel mode.

This mode is active only as long as the PanMode parameter is true. If PanMode is changed to false, the system exits Panel mode immediately and returns to the previous Auto or Manual mode.

Whether or not Panel mode is used depends on how comprehensive the application is. The question is whether you prefer to initiate control (the parameter PanMode) of the object from a workplace, or from a switch on an LCP.

The latter is a natural choice for smaller applications. The PanMode parameter is connected to the switch on the LCP; PanCmd1, PanCmd2 and PanCmd0 are connected to the Start/Stop buttons (see Figure 10)

AutoCmd1

AutoCmd0

Out1Level

AutoCmd0 has priority.

AutoCmd2

Out2Level


www.cadfamily.com


wwwThe

Figure 10. The Panel mode control diagram. A general solution for smaller applications, where all

four Panel parameters are connected from an LCP.

However, in large applications this option can cause a number of undesirable events. In this case, the best solution is to connect the PanMode parameter, via variables to a faceplate at the operator workplace. The PanCmd1, PanCmd2 and PanCmd0 parameters are still connected to the physical Start/Stop buttons. Changes in the Panel mode are therefore approved centrally, that is, a local operator must first obtain permission from the central control operator (see Figure 11).

PanMode

LCP Process objectMotor

Stop

Forward

Switch

Reverse

PanCmd1

PanCmd2

PanCmd0

Controller


www.cadfamily.com


wT

Figure 11. The Panel mode control diagram. A general solution for large applications, where the PanMode parameter is connected to an operator workplace.

When the Panel mode is active, the LCP takes control of the object and errors are calculated according to the status signals from the LCP. The output signal retains its status from the previous mode.

The status of the object is controlled by the signals PanCmd1, PanCmd2 and PanCmd0, which are level detected signals and function in the same way as AutoCmd signals, as illustrated in Figure 3. The PanCmd1, PanCmd2 and PanCmd0 parameters should be connected to push buttons. It may be advisable to use an R_Trig function block (trigger parameter and push button) between PanCmd1, PanCmd2 and PanCmd0, in case the push button malfunctions.

LCP

Process object

Motor

Stop

Reverse

PanCmd1

PanCmd2

PanCmd0

PanMode

Operator Workplace

Switch on screen

Controller

Forward


www.cadfamily.com


wwwThe

– Local Mode - The object is controlled locally from an LCP (Local Control Pane), bypassing the BiCore function block

Local mode is used when the object is controlled locally by LCP and the function block does not have any signals for maneuvering the object from the LCP. All signals from the LCP are physically connected directly to the object (for example, two directional motor, spring-return valve etc.).

In this mode, the object status is not updated inside the function block, even if it is changed in reality (see Figure 12). SafetyCmd signals may still change the object status. Error calculation is disabled. Objects return to the previous mode when Local mode is disabled.

Figure 12. The Local mode control diagram.

The object status is not updated in Local mode. This means that after leaving Local mode, the output signal status is the same as before entering Local mode.

If the status in the function block tracks feedback signals, this must be implemented outside the function block, for example, by setting the corresponding safety command signal.

Motor

LocMode

Process objectLCP

Stop

Forward

Reverse

Controller


www.cadfamily.com


wT

• Configuration of Feedback Signals

The parameter FBConfig informs the function block how the feedbacks are configured, by transferring the combination of feedback signals of the object to the function block. Possible combinations of feedback signals are listed in the table below:

The values of the feedback signals FB1, FB2 and FB0 are transferred to StatAc1, StatAct2, and StatDeact parameters respectively, conditioned with Out1Level, Out2Level.

If an object has no, or only two, feedback signals, StatAct1, StatAct2 and StatDeact are still set. The signals StatAct1, StatAct2, and StatDeact are set to false, if FBConfig = 0, 1, 2 or 3, and more than one feedback is true at the same time.

Table 2. Possible combinations of feedback signals

FBConfig Position 1 Position 2 Deactivated position

0 FB1 FB2 FB0

1 FB1 FB2 (none)

2 FB1 inverted FB2 inverted (none)

3 FB1 inverted FB2 inverted FB0 inverted

4 (none) (none) (none)


www.cadfamily.com


wwwThe

• Output Settings

The output signals include Out1, Out2, Out0, Out1Level and Out2Level.

Out1, Out2, and Out0 can be configured as pulsed command or level-detected command, by means of the PulseOut parameter.

The pulse is sustained by the parameters Out1, Out2, and Out0, until the corresponding feedback is detected or the maximum object error time is exceeded.

Out1Level and Out2Level are intended indicate the output state when Out1 and Out0 are pulsed.

If there is no feedback from a position, the pulse duration is set to the object error time. Only one pulse is generated upon each status change.

• Simulation

When the parameter Simulate is activated, the object error calculation is disabled and the Out1, Out2, and Out0 signal are set to false. The signals StatAct1, StatAct2, and StatDeact are set according to the status of Out1Level and Out2Level.

When simulation is deactivated, the status of the object reverts to that in the mode prior to simulation and the Out0 signal is set to true.


www.cadfamily.com


wT

• Change-over Action

The main difference between the UniCore and BiCore function blocks is their directional functionality as the BiCore function block can change from one active state to another. Changes can be made in all operation modes.

For implementation of a bi-directional motor, the BiCore function block has a parameter named ChangOverTime (Time data type). The ChangeOverTime parameter is used for large motors in order to secure safe operation (switching forward/reverse). The parameter ChangeOverTime sets a delay time, before the direction can be changed (see Figure 13).

The ChangeOverTime parameter has an initial value of 5 seconds.

Figure 13. Change-over action state diagram

ChangeOverTime is only applicable to the parameters Out1, Out2, and Out0. It is not applicable to Out1Level or Out2Level, as these two parameters present the actual command.

Out1(not pulsed)

Out2(not pulsed)

xxxCmd1

xxxCmd0

xxx = AutoCmd, ManCmd, PanCmd

xxxCmd2

ChangeOverTime

ChangeOverTime


www.cadfamily.com


wwwThe

Interlocking

This subsection describes the safety parameters for the BiCore function block. The main purpose of the interlocking parameters is accurate and safe operation with critical process values, such as high levels and temperatures, Motor Control Centre interface, safety devices etc.


Ilock1, Ilock2 and Ilock0 signals blocks manual interactions in Manual and Panel mode (not in Auto mode) to switch the object to activated and deactivated state respectively. The Inhibit signal will resets interlock signals when true.

Figure 14. Manual maneuvers interlock signals.

(A) - Condition for jump to state 0: State 0-maneuver and NOT Ilock0.

(B) - Condition for jump to state 1: State 1-maneuver and NOT Ilock1.

(C) - Condition for jump to state 2: State 2-maneuver and NOT Ilock2.

(D) - Condition for jump to state 1: State 1-maneuver and NOT Ilock1.

(E) - Condition for jump to state 2: State 2-maneuver and NOT Ilock2.

(F) - Condition for jump to state 0: State 0-maneuver and NOT Ilock0.

State 1

State 0

State 2

(A)(Stop)

(Start/Forward) (Start/Reverse)

(B)

(F)

(E)

(D)

(C)


www.cadfamily.com


wT


The SafetyCmd1, SafetyCmd2, and SafetyCmd0 signals force the output to the respective status, with higher priority than other signals, except when the Inhibit signal is set to true. When these signals disappear, the status from safety state is transferred to the current mode.

SafetyCmd0 has the highest priority of the three safety commands and affects Out0. Similarly SafetyCmd1 and SafetyCmd2 affect Out1 and Out2.

Figure 15. State diagram showing safety command priorities andoutput signals with the effect of Inhibit.

The Inhibit signal overrules all safety commands, so when the Inhibit signal is active, the object ignores the status of SafetyCmd (the safety commands do not affect the output signals).

• Inhibit - Cancels all Ilock and SafetyCmd signals

When the Inhibit signal is set to true, the program ignores all Ilock and SafetyCmd signals. This parameter can be used when you want to run the object although all Ilock and SafetyCmd signals are cancelled. When the Inhibit signal returns to false, the Ilock and SafetyCmd signals are re-activated to their former state.

Safety1

Safety2

Safety0

Inhibit

Out1

Out2

Out0


www.cadfamily.com


wwwThe

Object Error

The object error is supervised in all modes, except Disable and Local mode. It is based upon the values of the parameters Out1Level, Out2Level, FB1, FB2 and FB0.

The object error is calculated by the ACOF (Automatic Check Of Feedback) function block from the standard SystemLib library.

The information required for the object error calculation is the object error time and the number of feedbacks: these two parameters have to be configured by the user (OETime and FBConfig).

OETime has an initial value of 5 seconds. In the extended library a variable is connected the value of which overrides the initial value. The value of OETime can be altered online in the interaction windows or in the Process Portal A faceplate. The connected variable has a cold retain attribute, to retain the value following cold or warm restarts.

The parameter ExtErr (external error) provides a possibility to connect other errors to the object. The signal is added together with an error signal from object supervision (ACOF) to the parameter ObjErr.

The ObjErr parameter does not affect the object status. If required, it has to be implemented outside the BiCore, for example by connecting a variable to the parameters ExtErr and SafetyCmd0. See the MotorBi function block, for an example.

• Alarm - Not available for BiCore.

Interaction windows

Not available for BiCore.

Faceplate Elements

Not available for BiCore.


www.cadfamily.com


wT

BiHSI

BiHSI is a basic function block which supports the faceplate and display elements for BiCore in the Process Portal A graphical environment. This function block calculates the information to be presented in display elements and faceplates in the operator graphical environment. The function block is used in the control modules or function blocks together with BiCore, when an operator display element is to be used.

The BiHSI function block must be executed before the BiCore itself.

All input parameters to the BiHSI function block that have the same names as the input parameters to BiCore (for example FBConfig, FB1, FB0 etc.) should contain the same information as in the BiCore.

Note that Automode for BiHSI, is to be connected to the AutoMode output parameter at the BiCore.

In normal cases, the bool type parameter that obtains input from the hardware I/O, is connected via a variable/parameter with BoolIO data type, for example, FB1, FB2, Out1 and Out2. The BoolIO data type is a structured data type with Value, IOValue and Force as the components. The value is connected to the FB1 parameter and forced to FB1Forced and FB2Forced.

Figure 16. Connection diagram for BiHSI, BiCore and BoolIO.

BiHSI function block

FB1

FB1Forced

FB1

BiHSI

BiCoreFB1.Forced

FB1.Value

FB2ForcedFB2.Forced

FB2

FB2

FB2.ValueBoolIO

ValueForced

FB1

BoolIO

ValueForced

FB2


www.cadfamily.com


wwwThe

• Effective Feedback

The EffectiveFB1, EffectiveFB2, and EffectiveFB0 parameters, of the in/out type, give the calculated result from FBConfig and the values of FB1, FB2, and FB0.

Effective feedback signals are connected to the faceplate and displayed under the Status tab.

• Output IOLevel

The parameter Out1IOLevel, of the in/out type, is the result calculated from the actual values of the binary I/O (Out1IO, Out0IO) in relation to the selected pulse functionality.

Figure 17. OutputIOLevel state diagram.

The output signals are connected and displayed in the Process Portal A faceplate.

• Interlock

The parameter Interlock, of the in/out type, is the sum of SafetyCmd and Ilock. The Interlock parameter provides information when any type of interlocking is active (for example, SafetyCmd or Ilock).

The interlock signals are connected and displayed in the Process Portal A faceplate.

• Forced Action

The parameter Forced, of the in/out type, indicates the forced status of the Out0IO and Out1IO signals at FB0 or FB1. If one of these four I/O signals is blocked/forced, the parameter Forced, of the in/out type, will be true.

Out1IO

Out1IOLevel

Out0IO

Out2IO

Out2IOLevel


www.cadfamily.com

DriveCore Section 1 Process Object Libraries

wT

DriveCore

DriveCore is a basic function block, that can be used as a basis for control of ABB Standard Drives and their corresponding ABB Engineered Drives. DriveCore is normally used together with the UniCore function block. Therefore the start order parameter (Start) is a level signal with hold function.

The DriveCore function block gives the user possibility to start and stop a drive at a chosen setpoint, according to the local state machine in drive. The states are controlled by the function block through manipulation of the drives status and control word.

Status and Control Word

The SW, Ref1, Ref2, CW, Act1, and Act2 parameters are to be connected to the drive, independent of the media with which the data is transferred. The drive communicates with the controller though drive data sets and the parameters are to be connected to the drive according to the table below.

Drive Data Set 1 Drive Data Set 2

Data Words Data Words

1.1 1.2 1.3 2.1 2.2 2.3

CW Ref1 Ref2 SW Act1 Act2

The drive data set number can differ between different types of ABB Drives, see the manual for the relevant drive.

DriveCore function block


www.cadfamily.com

Section 1 Process Object Libraries DriveCore

wwwThe

Emergency Stop

The Drive function block type has two parameters that can cause an emergency stop, Off2 and Off3. If the application demands an emergency stop through one of the parameters, the drive stops according to the local emergency settings on the drive. The priority for emergency stops is controlled by the drive. The higher priority is higher than that of the stop and start commands.

The Off2 and Off3 parameters do not have any effect on the drive, if it is in remote state (locally controlled drive).

Controlling the Drive

When a start order is given by the Start parameter, the drive starts at the chosen setpoint, if the drive is ready to start and no stop order is given. Both start and stop orders support the ramp functionality, according to local settings in the drive. When both start and stop orders are given though the input parameters, the stop order has the higher priority.

In order to prepare the drive for start, the following must be fulfilled:

• The drive must be configured to receive commands from the Fieldbus

• Communication must running (Drive – Controller)

• No activated emergency stop (Off2, Off3)

• After drive fault, the reset command must have been given


www.cadfamily.com

DriveCore Section 1 Process Object Libraries

wT

Scaling of Drive Values

It is possible to scale all reference and setpoint values according to the local settings in the drive unit. Even the format used in communication should be treated. The value of the scale parameters should be calculated according to:

Scale factor = Field reference scaling value / Max_Min_Value

where:

Scale factor is the value used for the scaling values (ScaleSP1, ScaleSP2, ScaleAct1, and ScaleAct2).

Field reference scaling value is the value corresponding to the scaling value in the drive (value received from the drive). For further information, consult the relevant drive manual.

Max_Min_Value corresponds to the unit chosen in the drive. For example, in a standard Drive (ACS600Std), if speed is given in the unit % and the Max_Min_Value is 100 the Scale factor will be 200 and if the unit is in r.p.m. with a maximum of 1500 r.p.m. the Scale factor will be 13.3.


www.cadfamily.com

Section 1 Process Object Libraries Process Object Extended Library

wwwThe

Process Object Extended Library

Overview

The Extended library contains function block types and control module types based on either UniCore or BiCore (and their corresponding HSICore or BiHSI). The function block and control module types also includes alarm and graphics functionality.

The following Process objects from the Extended library can be applied to an application:

• Uni, based on UniCore

• ValveUni, based on Uni type, but simpler. Controls a uni-directional valve.

• Bi, based on BiCore

• MotorUni, based on the Uni type, but more complex. Controls a uni-directional motor.

• MotorBi, based on the Bi type, but more complex. Controls a bi-directional motor.


www.cadfamily.com

About the Extended Process Objects Section 1 Process Object Libraries

wT

About the Extended Process Objects

The Extended library is more comprehensive than the Basic library. It comprises ready-to-use valve and motor objects, alarm handling functionality and templates for user-designed valve and motor objects. It includes additional control modules for high-level graphical configuration, which are integrated with both Control Builder Professional and Process Portal A faceplates.

Function Blocks or Control Modules?

In simple applications (or small ones) that will not need to be modified at a later date, traditional function block solutions are the most rational choice. In more complex applications, control modules are preferred.

One of the benefits of using control modules, is that they allow the user to insert many similar objects, as the code sorting routine ensures that variables are dealt within the correct order. The more objects to be inserted, the more you gain by using control modules.

Function block parameters are copied at each call, while control module parameters are defined at compilation and set up once, prior to execution. Control modules have a performance advantage, especially when large structures (for example, structured data types) are used as parameters, of the in and/or out type, in function blocks, or when parameters are transferred through deep hierarchies.

It is only possible to use control modules in Control Builder Professional.


www.cadfamily.com

Section 1 Process Object Libraries Uni

wwwThe

Uni

This process object is an example of an UniCore application. It includes an alarm function, Control Builder interaction windows and the graphical Process Portal A interface.

The UniHSI function block is implemented together with the UniCore function block, supporting the faceplate and displaying elements for the Uni process object in the Process Portal A

graphical environment.

Many parameters are the same throughout this section and are therefore referred to and explained only in the corresponding core section. For further information, see UniCore on page 20.

Uni function block


www.cadfamily.com

Uni Section 1 Process Object Libraries

wT

Operation

Several interaction parameters in the UniCore function block, for example ManCmd1 etc., are not connected to parameters in this block. Inside this function block, local variables are used for communication between the graphics window and corresponding parameters in the UniCore function block.

• Mode

– Disable Mode

See Disable Mode - Deactivates the object on page 21.

– Manual Mode

The manual mode is designed to be set from the Control Builder interaction window or the operator workplace faceplate, via SetMan, ManCmd1, and ManCmd0. No parameters for manual control are provided in this object.

See also, Manual Mode - A user operates the object from a workstation on page 21.

– Auto Mode

The setting of the Auto mode can be set from the program, interaction windows or faceplate. Since Auto mode results in automatic operation, the program controls the object, via AutoCmd1 and AutoCmd0.

See also, Auto Mode - The program controls the object on page 22.

– Panel Mode

See Panel Mode - The object is controlled locally from an LCP (Local Control Panel), via the UniCore function block on page 22..

For Uni, it is possible to control Panel mode of the object from both a workplace, and from a switch on an LCP. The faceplate has a button (connected to a local variable) that can toggle the Panel mode. There is also a parameter (PanMode) intended to be connected to an activation signal from the panel. If you connect PanMode to the panel it is still possible to use the button in the faceplate to activate the Panel mode. It is, however, not possible to deactivate Panel mode from the faceplate if it has been activated from the LCP.


www.cadfamily.com


wwwThe

– Local Mode

See Local Mode - The object is controlled locally from a Local Control Panel (LCP), bypassing the UniCore function block on page 25.

• FeedBack Configuration

See Configuration of Feedback Signals on page 26.

• Output Settings

See Output Settings on page 26.

Interlocking

See Interlocking on page 27.

Object Error


The ExtErr parameter is connected directly to the corresponding parameter in UniCore.

Object error time is connected to the Control Builder interaction window and the Process Portal A faceplate, via a local variable. This results in the user being able to change the value from the corresponding graphical window. The local variable has a cold retain attribute and the value is thus retained following a cold restart.

See also Object Error on page 28.


www.cadfamily.com

Uni Section 1 Process Object Libraries

wT

• Alarm

The alarm function uses the AlarmCond function block, with acknowledge rule (AckRule=1). This acknowledge rule includes six possible alarm states. For further information about the alarm state, see Control Builder online help for more information on the AlarmCond function block. The alarm is activated by the object error in UniCore function block (as described above).

The AlarmCond function block incorporates an alarm Control Builder interaction window, displayed by a clicking the alarm icon in the Control Builder interaction window of the Uni object. See Figure 18.

Figure 18. An alarm Control Builder interaction window.

If the object is in Disabled or in Local mode, or if the object error is disabled, the alarm function is disabled.

An alarm can be acknowledge from the program via the parameter AlarmAck, the LCP (in Panel mode) via parameter PanAck, from the alarm Control Builder interaction window, or from the Process Portal A faceplate.

• Error Text String

The error text string is handled by the OETextUni function block. This function block generates the text message from feedback and output signals of the AlarmCond function block. The text message is displayed in the Alarm Control Builder interaction window.

This text contains the Name of the object, followed by -OE: and the status of the activated output signal, 0 or 1, at the time of the error (for example, Out1=1). The status of the selected feedback combination, for example, FB1=1; FB0=0; is also displayed. If the error has been generated from an ExtErr parameter, an External error text is also displayed.


www.cadfamily.com


wwwThe

Control Builder Interaction Window

The Uni object has two Control Builder interaction windows, one for manual control and one for indications (see Figure 19). The main interaction window is displayed first. The extended interaction window is displayed by a click on the information icon in the main interaction window.

Figure 19. The Control Builder interaction windows of the Uni object.

Main interaction window

Extended interaction window


www.cadfamily.com

ValveUni Section 1 Process Object Libraries

wT

ValveUni

This process object is a simple example of the UniCore function block. ValveUni includes an alarm function, Control Builder interaction windows and the Process Portal A graphical interface.

The UniHSI function block is implemented together with the UniCore function block, supporting the faceplate and displaying ValveUni elements, in the Process Portal A graphical environment.

The ValveUni object is incorporated with only one output I/O for open command.

Many parameters are the same throughout this section and are therefore referred to and explained only in the corresponding UniCore section. For further information see UniCore on page 20.

ValveUni function block


www.cadfamily.com

Section 1 Process Object Libraries ValveUni

wwwThe

Operation

Several interaction parameters in the UniCore function block, for example, ManCmd1 etc., are not connected to parameters in this block. Inside this block, local variables are used for communication between the graphics window and corresponding parameters on the UniCore function block.

• Mode

The ValveUni object has a reduced number of operation modes, Disable, Manual, and Auto mode.

– Disable Mode


– Manual Mode

The manual mode is designed to be set from the Control Builder interaction window or the operator workplace faceplate, via SetMan, ManCmd1, and ManCmd0. No parameters for manual control are provided in this object.

See also Manual Mode - A user operates the object from a workstation on page 21.

– Auto Mode

Auto mode can be set from the program, interaction windows or faceplate. ValveUni has only one Auto command, AutoCmd1 with level detection (reduced number of parameter).

See also Auto Mode - The program controls the object on page 22.



• Output Settings

Since the object is intended to control a simple valve, only one output is provided (Out1) which is not pulsed.


www.cadfamily.com

ValveUni Section 1 Process Object Libraries

wT

Interlocking

The interlocking parameters (Ilock and SafetyCmd) are very similar to those in UniCore, only being that Inhibit is not implemented.

See also Interlocking on page 27.

Object Error

The object error is calculated only by the ACOF (Automatic Check Of Feedback) function block, from the standard SystemLib library and indicated via the parameter ObjErr.

The ExtErr parameter from UniCore is not used.


See also Object Error on page 28.

• Alarm

The alarm function uses the AlarmCond function block, with acknowledge rule (AckRule=1). This acknowledge rule includes six possible alarm states. For further information about the alarm state, see Control Builder online help for AlarmCond function block. The alarm is activated by the object error in the UniCore function block (as described above).

The AlarmCond function block incorporates an alarm Control Builder interaction window, displayed by clicking on the alarm icon in the ValveUni Control Builder interaction window. See Figure 20.

Figure 20. An alarm Control Builder interaction window.


www.cadfamily.com

Section 1 Process Object Libraries ValveUni

wwwThe

The alarm function is disabled, only if the object error calculation is disabled.

An alarm can be acknowledge from the program via the parameter AlarmAck, from the alarm Control Builder interaction window and from the Process Portal A faceplate.


The error text string is handled by the OETextUniOut1 function block. This function block generates the message text from feedback and output signals of the AlarmCond function block. The text message is displayed in the Alarm Control Builder interaction window.

This text contains the Name of the object, followed by -OE: and the status of the activated output signal, 0 or 1, at the time of the error (for example, Out1=1). The status of the selected feedback combination, for example, FB1=1; FB0=0; is also displayed. If the error has been generated from an ExtErr parameter, there is also an External error text displayed.


The ValveUni object has two Control Builder interaction windows, one for manual control and one for indications (see Figure 21). The main interaction window is displayed first. The extended interaction window is displayed by a click on the information icon in the main interaction window.

Figure 21. The Control Builder interaction windows of the ValveUni object.


Main interactionwindow


www.cadfamily.com

Bi Section 1 Process Object Libraries

wT

Bi

This process object is an example of a BiCore application. It includes with an alarm function, Control Builder interaction windows and Process Portal A graphical interface.

The BiHSI function block is implemented together with the BiCore function block, supporting the faceplate and displaying elements for the Bi process object in the Process Portal A graphical environment.

Many parameters are the same throughout this section and are therefore referred to and explained only in the corresponding BiCore section. For further information, see BiCore on page 31.

Bi function block


www.cadfamily.com

Section 1 Process Object Libraries Bi

wwwThe

Operation

Several interaction parameters in BiCore function block, for example, ManCmd1 etc. are not connected to parameters in this block. Inside this block local variables are used for communication between the graphics window and the corresponding parameters on the BiCore function block.

• Mode

– Disable Mode


– Manual Mode

The Manual mode is designed to be set from the Control Builder interaction window or the faceplate in Operator workplace via SetMan, ManCmd1, ManCmd2, and ManCmd0. No parameters for manual control are provided in this object.

See also about Manual Mode - A user controls the object from a workstation on page 33.

– Auto Mode

Auto mode can be set from the program, interaction windows or faceplate. Since Auto mode results in automatic operation, the program controls the object via AutoCmd1, AutoCmd2 and AutoCmd0.

See also about Auto Mode - The program controls the object on page 33.


www.cadfamily.com


wT

– Panel Mode

See Panel Mode - The object is controlled locally from an LCP (Local Control Panel), via the BiCore function block on page 34.

Local Mode

See Local Mode - The object is controlled locally from an LCP (Local Control Pane), bypassing the BiCore function block on page 37.



• Output Settings



The Bi object has a five-seconds, built-in change-over time function, inside BiCore. This setting. cannot be changed.

See also Change-over Action on page 40.

Interlocking

See Interlocking on page 41.

For Bi, it is possible to control Panel mode of the object from both a workplace, and from a switch on an LCP. The faceplate has a button (connected to a local variable) that can toggle the Panel mode. There is also a parameter (PanMode) intended to be connected to an activation signal from the panel. If you connect PanMode to the panel it is still possible to use the button in the faceplate to activate the Panel mode. It is, however, not possible to deactivate Panel mode from the faceplate if it has been activated from the LCP.


www.cadfamily.com


wwwThe

Object Error


The ExtErr parameter is connected directly to the corresponding parameter in BiCore.


See also about Object Error on page 43.

• Alarm

The alarm function uses AlarmCond function block, with acknowledge rule (AckRule=1). This acknowledge rule includes six possible alarm states. For further information about the alarm state, see Control Builder online help for AlarmCond function block. The alarm is activated by the object error in the BiCore function block (as described above).

The AlarmCond function block incorporates Control Builder interaction window for alarm, displayed by clicking the alarm icon in the Control Builder interaction window of the Bi process object. See Figure 22.

Figure 22. The alarm Control Builder interaction window of the Bi object.


www.cadfamily.com


wT


The error text string is handled by the OETextBi function block. This function block generates the message text from feedback and output signals of the AlarmCond function block. The text message is displayed in the Alarm Control Builder interaction window.

This text contains the Name of the object, followed by -OE: and the status of the activated output signal, 0 or 1, at the time of the error, (for example, Out1=1). The status of the selected feedback combination, for example, FB1=1; FB0=0; is also displayed. If the error has been generated from an ExtErr parameter, an External error text is also displayed.


www.cadfamily.com


wwwThe


The Bi process object has two Control Builder interaction windows, one for manual control and one for indications (see Figure 23). The main interaction window is displayed first. The extended interaction window is displayed by a click on the information icon in the main interaction window.

Figure 23. The Control Builder interaction windows of the Bi object.




www.cadfamily.com

MotorUni Section 1 Process Object Libraries

wT

MotorUni

This process object is an improved example of the UniCore application. It includes an alarm function, Control Builder interaction windows and Process Portal A graphical interface.

The UniHSI function block is implemented together with the UniCore function block, supporting the faceplate and displaying elements for the MotorUni process object in the Process Portal A graphical environment.

Many parameters are the same throughout this section and are therefore referred to and explained only in the corresponding BiCore section. For further information, see UniCore on page 20.

MotorUni function block


www.cadfamily.com

Section 1 Process Object Libraries MotorUni

wwwThe

Operation

Several interaction parameters in UniCore, for example, SetMan etc. are not connected to parameters in this block. Inside this block local variables are used for communication between the graphics window and the corresponding parameters in the UniCore.

• Mode

– Disable Mode

See also, Disable Mode - Deactivates the object on page 21.

– Manual Mode

The Manual mode can be set from the Control Builder interaction window or the operator workplace faceplate, via SetMan, ManCmd1, ManCmd2 and ManCmd0. No parameters for manual control are provided in this object.

See also, Manual Mode - A user operates the object from a workstation on page 21.

– Auto Mode

Auto mode can be set from the program, interaction windows or the faceplate. Since Auto mode implies automatic operation, the program controls the object via AutoCmd1 and AutoCmd0.

Each of these parameters is supplied with a value of OETime, connected to the Control Builder interaction window and the Process Portal A faceplate, via local variables. The value of OETime can be changed from the corresponding graphical window. The local variables have the cold retain attribute to retain the values following a cold restart. OETime for AutoCmd1 has the same setting as AutoCmd1 and AutoCmd0, because the same local variable is used.



www.cadfamily.com


wT

– Panel Mode

See Panel Mode - The object is controlled locally from an LCP (Local Control Panel), via the UniCore function block on page 22.

– Local Mode

See Local Mode - The object is controlled locally from a Local Control Panel (LCP), bypassing the UniCore function block on page 25.



• Output Settings


Interlocking

Modification of the interlocking function is performed to extend some parameters, to apply user-defined text and to implement the combination of SafetyCmd0 and an alarm function via ExtErr. Further improvement is possible based on this example.


The MotorUni object has four parameters: Ilock01, Ilock02, Ilock11, and Ilock12 that set the condition of Ilock0 or Ilock1 in the UniCore function block. The Ilock0 condition is set by Ilock01 or Ilock02. Similarly, the Ilock1 condition is set by Ilock11 or Ilock12.

For MotorUni, it is possible to control Panel mode of the object from both a workplace, and from a switch on an LCP. The faceplate has a button (connected to a local variable) that can toggle the Panel mode. There is also a parameter (PanMode) intended to be connected to an activation signal from the panel. If you connect PanMode to the panel it is still possible to use the button in the faceplate to activate the Panel mode. It is, however, not possible to deactivate Panel mode from the faceplate if it has been activated from the LCP.


www.cadfamily.com


wwwThe


The SafetyCmd0 parameter is divided into three parameter: SafetyCmd01, SafetyCmd02, and SafetyCmd03. Each of these parameters has associated parameters: SafetyCmd01Txt, SafetyCmd02Txt, and SafetyCmd03Txt, to provide a descriptive text in the alarm list and the Process Portal A faceplate. The Text is displayed in the Safety Interlock menu area.

The extended SafetyCmd0 (-Cmd01, -Cmd02 and -Cmd03) have a hold function with an alarm. When the safety command is active, the object error is generated by an alarm and can only be released by alarm acknowledge or inhibit.

• Inhibit - Cancel all Ilock and SafetyCmd signals

The Inhibit signal for MotorUni process object works exactly the same as described earlier in the UniCore section, with one exception; Inhibit releases an object error, activated by the SafetyCmd0.

Object Error

The object error is calculated by the ACOF (Automatic Check Of Feedback) function block, from the standard SystemLib library, and the error signal from the parameter ExtErr (external error) to parameter ObjErr.

The ExtErr parameter in UniCore is the sum of SafetyCmd01, SafetyCmd02, SafetyCmd03 and the corresponding ExtErr parameter in the MotorBi process object.

For further information, see Object Error on page 28.


www.cadfamily.com


wT

• Alarm

The Alarm is activated by the object error in the UniCore function block.

The AlarmCond function block incorporates an alarm Control Builder interaction window, displayed by a simple click on the alarm icon in the Control Builder interaction window of the MotorUni. See Figure 24.

Figure 24. The alarm Control Builder interaction window of the MotorUni object.


The error text string is handled by the OETextUni function block. This function block generates the text message from the feedback and output signal of the AlarmCond function block. The text message is displayed in the alarm Control Builder interaction window.

This text contains the Name of the object, followed by -OE: and the status of the activated output signal, 0 or 1, at the error occasion, (for example, Out1=1). The status of the selected feedback combination, for example FB1=1; FB0=0; is also displayed. If the error is generated from an ExtErr parameter, an External error text is also displayed.


www.cadfamily.com


wwwThe


The MotorUni object has two Control Builder interaction windows, one for manual control and one for indications (see Figure 27). The main interaction window is displayed first. The extended interaction window is displayed by a click on the information icon in the main interaction window.

Figure 25. The Control Builder interaction window of the MotorBi object.




www.cadfamily.com

MotorBi Section 1 Process Object Libraries

wT

MotorBi

This process object is an improved example of the BiCore application. It includes an alarm function, Control Builder interaction windows and Process Portal A graphical interface.

The BiHSI function block is implemented together with the BiCore function block, supporting the faceplate and displaying elements for MotorBi process object in the Process Portal A graphical environment.

Many parameters are the same throughout this section and are therefore referred to and explained only in the corresponding BiCore section. For further information, see BiCore on page 31.

MotorBi function block


www.cadfamily.com

Section 1 Process Object Libraries MotorBi

wwwThe

Operation

Several interaction parameters in the BiCore function block, for example, SetMan etc. are not connected to parameters in this block. Inside this block local variables are used for communication between the graphics window and the corresponding parameters in the BiCore function block.

• Mode

– Disable Mode

See also, Disable Mode - Deactivates the object on page 32.

– Manual Mode

The Manual mode is set from the Control Builder interaction window or the operator workplace faceplate, via SetMan, ManCmd1, ManCmd2 and ManCmd0. No parameters for manual control are provided in this object.

See also, Manual Mode - A user controls the object from a workstation on page 33.

– Auto Mode

Auto mode can be set from the program, interaction windows or the faceplate. Since Auto mode is the automatic operation, the program controls the object via AutoCmd1, AutoCmd2 and AutoCmd0.

Each of these parameters is supplied with an OnDelayTime parameter, connected to the Control Builder interaction window and the Process Portal A faceplate, via local variables. The value of OnDelayTime can be changed in the corresponding graphical window. The local variables have the cold retain attribute to retain their values following a cold restart. OnDelay for AutoCmd1 and AutoCmd2 has the same setting as AutoCmd1, AutoCmd2 and AutoCmd0, because the same local variable is used.



www.cadfamily.com


wT

– Panel Mode

See Panel Mode - The object is controlled locally from an LCP (Local Control Panel), via the BiCore function block on page 34.

– Local Mode

See Local Mode - The object is controlled locally from an LCP (Local Control Pane), bypassing the BiCore function block on page 37.



• Output Settings



The MotorBi object implements the change-over function from the BiCore function block. One parameter is provided for setting the change-over time, and it is connected to the corresponding parameter in BiCore.

This change-over time is also connected to the Control Builder interaction window and the Process Portal A faceplate, via local variables. This results in the user being able to change the value in the corresponding graphical window. The local variables have the cold retain attribute to retain the values following a cold restart.

See also, Change-over Action on page 40.

For MotorBi, it is possible to control Panel mode of the object from both a workplace, and from a switch on an LCP. The faceplate has a button (connected to a local variable) that can toggle the Panel mode. There is also a parameter (PanMode) intended to be connected to an activation signal from the panel. If you connect PanMode to the panel it is still possible to use the button in the faceplate to activate the Panel mode. It is, however, not possible to deactivate Panel mode from the faceplate if it has been activated from the LCP.


www.cadfamily.com


wwwThe

Interlocking

Modification of the interlocking function is performed to extend some parameters, to apply user-defined text and to implement the combination of SafetyCmd0 and alarm functions via ExtErr. Further improvement is possible based on this example.


The MotorBi object has four parameters: Ilock01, Ilock02, Ilock11, and Ilock12 that set the condition of Ilock0 or Ilock1 in the BiCore function block. The Ilock0 condition is set by Ilock01 or Ilock02. Similarly, the Ilock1 condition is set by Ilock11 or Ilock12.

Ilock2 has no extended parameter and is connected directly to the corresponding parameter in the BiCore process object.


The SafetyCmd0 parameter is divided into three parameters: SafetyCmd01, SafetyCmd02, and SafetyCmd03. Each of these parameters has associated parameters: SafetyCmd01Txt, SafetyCmd02Txt, and SafetyCmd03Txt, to provide a descriptive text in the alarm list and the Process Portal A faceplate. The Text is displayed in the Safety Interlock menu area.

SafetyCmd1 and SafetyCmd2 have no extended parameters and is connected directly to the corresponding parameters in the BiCore function block.

The indication of SafetyCmd1 and SafetyCmd2 in the Process Portal A faceplate is separated from SafetyCmd0 in the Process Interlock menu area.

The extended SafetyCmd0 parameters (-Cmd01, -Cmd02 and -Cmd03) have a hold function with an alarm. When the safety command is active, the object error is generated by an alarm and can only be released by alarm acknowledge or inhibit.

• Inhibit - Cancel all Ilock and SafetyCmd signals

The Inhibit signal for MotorBi process object works exactly the same as described earlier in the BiCore section, with one exception; Inhibit releases an object error, activated by the SafetyCmd0.


www.cadfamily.com


wT

Object Error

The object error is calculated by the ACOF (Automatic Check Of Feedback) function block, from the standard SystemLib library, and the error signal from the parameter ExtErr (external error) to parameter ObjErr.

The ExtErr parameter in BiCore is the sum of SafetyCmd01, SafetyCmd02, SafetyCmd03 and the corresponding ExtErr in the MotorBi process object.

For further information, see Object Error on page 43.

• Alarm

The Alarm is activated by the object error in the BiCore function block.

The AlarmCond function block incorporates an alarm Control Builder interaction window, displayed by a simple click on the alarm icon in the Control Builder interaction window of the MotorBi. See Figure 26.

Figure 26. The alarm Control Builder interaction window of MotorBi object.


The error text string is handled by the OETextBi function block. This function block generates the text message from the feedback and output signal of the AlarmCond function block. The text message is displayed in the Alarm Control Builder interaction window.

This text contains the Name of the object, followed by -OE: and the status of the activated output signal, 0 or 1, at the error occasion, (for example, Out1=1). The status of the selected feedback combination, for example, FB1=1; FB0=0; is also displayed. If the error is generated from an ExtErr parameter, an External error text is also displayed.


www.cadfamily.com


wwwThe


The MotorBi object has two Control Builder interaction windows, one for manual control and one for indications (see Figure 27). The main interaction window is displayed first. The extended interaction window is displayed by a click on the information icon in the main interaction window.

Figure 27. The Control Builder interaction window of the MotorBi object.




www.cadfamily.com

General Section 2 Object Handling

wT

Section 2 Object Handling

GeneralAll process objects in processobjextlib have a faceplate. The faceplate of an object type consists of a number of faceplate elements. There are four basic faceplate elements, which are adapted to suit the intended process object. These faceplate elements are:• Command• Parameters• LevelDetection• TrimCurve1

The Command, Parameters and LevelDetection elements refer to the processobjextlib folder and the TrimCurve1 refers to the Libraries folder, that is, the faceplate elements used for the process object types point to elements in these folders.

The graphics in a basic faceplate element is adapted to a faceplate element of an object type by setting the visibility of the graphics (in MS Visual Basic). There are various ways of setting the visibility of the graphics.

In the Command faceplate element (see the Example 1 below) graphics for signals and texts are only displayed in the faceplate element if the signals and/or texts are connected to the graphics.

In the Parameters faceplate element (see the Example 2 below) the visibility properties are set to display different graphics in the faceplate element depending on whether the property is true or false.


www.cadfamily.com

Section 2 Object Handling General

wwwThe

Example 1: Command in ValveUni Object Type

The Command faceplate element of ValveUni type contains only the Auto Command as a frame text (Frame0), the connected signal AutoCmd1.QualityOk (Frame0Cmd0OPC) and the text, Open (ACmd 0).

Figure 28. The basic Command faceplate element and the corresponding one in the ValveUni type

In the Expression Builder of MS Visual Basic, you can see that CaptionFr0 (Frame0) is connected to e_Frame0Caption; CaptionFr1 (Frame1), CaptionFr2 (Frame2) and CaptionFr3 (Frame3) is connected to e_empty, and Frame0Cmd0String (ACmd 0) are connected to e_Frame0Command0.

Frame0Cmd0OPC (the signal) is connected to AutoCmd1.QualityOk.

ValveUni Command faceplate elementBasic Command faceplate element


www.cadfamily.com

General Section 2 Object Handling

wT

Figure 29. The Command faceplate element of ValveUni object type, in Expression Builder.

In the Edit variables tab, these variables have the following texts:• e_empty - (no text at all, that is, no text is displayed)• e_Frame0Command0 - Open• e_Frame0Caption - Auto Command

Figure 30. Variables in Expression Builder of the ValveUni object type Command faceplate element.


www.cadfamily.com

Section 2 Object Handling General

wwwThe

Example 2: Parameters in Bi Object Type

The Parameters faceplate element of Bi type only contains the text, Object Error Time and the connected signal InteractionPar.OETime (ObjectErrorTime) and InteractionPar.OETime.QualityOk (OPCOkPbjectErrorTime).

Figure 31. The basic Parameters faceplate element and the corresponding one in the Bi type.

In the Properties window, the Motor Type property is set to False to make the OnDelayTime and Off Delay Time rows invisible. The BiMotorType property is set to False to make the Change Over Time row invisible.

Figure 32. The properties window.

Basic Parameters faceplate element Bi Parameters faceplate element


www.cadfamily.com

Basic Faceplate Elements Section 2 Object Handling

wT

Basic Faceplate Elements

The basic faceplate elements contain the graphics as displayed below.

Table 3. The basic faceplate elements

Name of Faceplate Element Graphics of Faceplate Element

Command

Parameters


www.cadfamily.com

Section 2 Object Handling Basic Faceplate Elements

wwwThe

LevelDetection

TrimCurve1

Table 3. The basic faceplate elements (continued)



www.cadfamily.com

Basic Faceplate Elements Section 2 Object Handling

wT

Up to six different faceplate elements may be connected to each faceplate of a process object type. These faceplate elements consist of the basic elements according to the table below.

Table 4. The basic faceplate elements used in the faceplatesof the process objects

Faceplate Elements

Command Parameters LevelDetection TrimCurve1

Bi

Command X

Interlock X

Parameters X

RedInterlock*

Status X

MotorBi

Command X

Interlock X

Parameters X X

RedInterlock*

Status X

TrimCurve X


www.cadfamily.com

Section 2 Object Handling Basic Faceplate Elements

wwwThe

* RedInterlock cannot refer to another faceplate element, that is, it is unique in each faceplate.

MotorUni

Command X

Interlock X

Parameters X X

RedInterlock*

Status X

TrimCurve X

Uni

Command X

Interlock X

Parameters X X

RedInterlock*

Status X

ValveUni

Command X

Interlock X

Parameters X X

RedInterlock*

Status X

Table 4. The basic faceplate elements used in the faceplatesof the process objects (continued)

Faceplate Elements

Command Parameters LevelDetection TrimCurve1


www.cadfamily.com

Bi Faceplate Elements Section 2 Object Handling

wT

Bi Faceplate Elements

The Bi faceplate elements contain the signal connections and graphics as displayed below.

Table 5. The Bi faceplate elements


Command(Auto and Panel mode signals)Auto CommandAuto Command 1 AutoCmd1Auto Command 2 AutoCmd2Auto Command 0 AutoCmd0Panel CommandPan Command 1 PanCmd1Pan Command 2 PanCmd2Pan Command 0 PanCmd0

Interlock(Interlocking signals for accurate and safe operation with critical process values)Safety InterlockForced to Position 1 SafetyCmd1Forced to Position 2 SafetyCmd2Forced to Position 0 SafetyCmd0Start/Stop InterlockPosition 1 Ilock1Position 2 Ilock2Position 0 Ilock0OthersOE Disabled OEDisabledInhibit Inhibit


www.cadfamily.com

Section 2 Object Handling Bi Faceplate Elements

wwwThe

Parameters(Alarm handling)Object Error Time InteractionPar.OETime

RedInterlock Inhibit

Status(Output and feedback signal status)Out StatusOut 1 Out1Out 2 Out2Out 0 Out0Feedback StatusOut 1 EffectiveFB1Out 2 EffectiveFB2Out 0 EffectiveFB0

Table 5. The Bi faceplate elements (continued)



www.cadfamily.com

MotorBi Faceplate Elements Section 2 Object Handling

wT

MotorBi Faceplate Elements

The MotorBi faceplate elements contain the signal connections and graphics as displayed below.

Table 6. The MotorBi faceplate elements


Command(Auto and Panel mode signals)Auto CommandLow AutoCmd1High AutoCmd2Stop AutoCmd0Panel CommandLow PanCmd1High PanCmd2kStop PanCmd0

Interlock(Interlocking signals for accurate and safe operation with critical process values)Process InterlockForced to Low SafetyCmd1Forced to High SafetyCmd2Safety Interlock

SafetyCmd01 SafetyCmd02 SafetyCmd03

Start/Stop InterlockLow Ilock11 or Ilock12High Ilock2Stop Ilock01 or Ilock02OthersOE Disabled OEDisabledInhibit Inhibit


www.cadfamily.com

Section 2 Object Handling MotorBi Faceplate Elements

wwwThe

Parameters(Alarm handling and level detection parameters)Object Error Time InteractionPar.OETimeOn Delay Time InteractionPar.OnDelayTimeOff Delay Time InteractionPar.OffDelayTimeChange Over Timer InteractionPar.ChangeOverTimeEnable supervision InteractionPar.EnableLevelDetectionValue MotorValue.ValueLevel InteractionPar.LevelHysteresis InteractionPar.HysteresisStart Delay InteractionPar.StartDelayFilter Time InteractionPar.FilterTimeFraction Fraction


Table 6. The MotorBi faceplate elements (continued)



www.cadfamily.com

MotorBi Faceplate Elements Section 2 Object Handling

wT

Status(Output and feedback signal status)Out StatusLow Out1High Out2Stopped Out0Feedback StatusLow EffectiveFB1High EffectiveFB2kStopped EffectiveFB0OthersPulse Out PulseOut

TrimCurve(Trime curve of motor value)In1Max MotorValue.Parameters.MaxIn1Min MotorValue.Parameters.MinIn1Value MotorValue.ValueLeftScaleFraction MotorValue.Parameters.FractionTimeScaleMin TrimCurveTime

Table 6. The MotorBi faceplate elements (continued)



www.cadfamily.com

Section 2 Object Handling MotorUni Faceplate Elements

wwwThe

MotorUni Faceplate Elements

The MotorUni faceplate elements contain the signal connections and graphics as displayed below.

Table 7. The MotorUni faceplate elements

Name of Faceplate Element and Connected Signals

Graphics of Faceplate Element

Command(Auto and Panel mode signals)Auto CommandStart AutoCmd1Stop AutoCmd0Panel CommandStart PanCmd1Stop PanCmd0

Interlock(Interlocking signals for accurate and safe operations with critical process values)Process InterlockForced to Running SafetyCmd1Safety Interlock

SafetyCmd01 SafetyCmd02 SafetyCmd03k

Start/Stop InterlockStart Ilock11 or Ilock12Stop Ilock01 or Ilock02OthersOE Disabled OEDisabledInhibit Inhibit


www.cadfamily.com

MotorUni Faceplate Elements Section 2 Object Handling

wT

Parameters(Alarm handling and level detection parameters)Object Error Time InteractionPar.OETimeOn Delay Time InteractionPar.OnDelayTimeOff Delay Time InteractionPar.OffDelayTimeEnable supervision InteractionPar.EnableLevelDetectionValue MotorValue.ValueLevel InteractionPar.LevelHysteresis InteractionPar.HysteresisStart Delay InteractionPar.StartDelayFilter Time InteractionPar.FilterTimeFraction Fraction


Table 7. The MotorUni faceplate elements (continued)




www.cadfamily.com

Section 2 Object Handling MotorUni Faceplate Elements

wwwThe

Status(Output and feedback signal status)Out StatusStarted Out1Stopped Out0Feedback StatusRunning EffectiveFB1Idle EffectiveFB0OthersPulse Out PulseOut

TrimCurve(Trime curve of motor value)In1Max MotorValue.Parameters.MaxIn1Min MotorValue.Parameters.MinIn1Value MotorValue.ValueLeftScaleFraction FractionTimeScaleMin TrimCurveTime

Table 7. The MotorUni faceplate elements (continued)




www.cadfamily.com

Uni Faceplate Elements Section 2 Object Handling

wT

Uni Faceplate Elements

The Uni faceplate elements contain the signal connections and graphics as displayed below.

Table 8. The Uni faceplate elements


Command(Auto and Panel mode signals)Auto CommandAuto Command 1 AutoCmd1Auto Command 0 AutoCmd0Panel CommandPan Command 1 PanCmd1Pan Command 0 PanCmd0

Interlock(Interlocking signals for accurate and safe operations with critical process values)Process InterlockOpen Ilock1Close Ilock0Safety InterlockForced to Open SafetyCmd1Forced to Close SafetyCmd0OthersOE Disabled OEDisabledInhibit Inhibit


www.cadfamily.com

Section 2 Object Handling Uni Faceplate Elements

wwwThe



Status(Output and feedback signal status)Out 1 Out1Out 0 Out0Feedback StatusOut 1 EffectiveFB1Out 0 EffectiveFB0OthersPulse Out PulseOut

Table 8. The Uni faceplate elements (continued)



www.cadfamily.com

ValveUni Faceplate Elements Section 2 Object Handling

wT

ValveUni Faceplate Elements

The ValveUni faceplate elements contain the signal connections and graphics as displayed below.

Table 9. The ValveUni faceplate elements


Command(Auto mode signal)Auto CommandOpen AutoCmd1

Interlock(Interlocking signals for accurate and safe operations with critical process values)Process InterlockOpen Ilock1Close Ilock0kSafety InterlockForced to Open SafetyCmd1Forced to Close SafetyCmd0OthersOE Disabled OEDisabled


www.cadfamily.com

Section 2 Object Handling ValveUni Faceplate Elements

wwwThe


RedInterlockObjErr

Status(Output and feedback signal status)Out StatusOpen Out1Feedback StatusOpen EffectiveFB1Close EffectiveFB0

Table 9. The ValveUni faceplate elements (continued)



www.cadfamily.com

Adding Functionality to a Process Object in Control Builder Section 3 Object Handling Examples

wT

Section 3 Object Handling Examples

Adding Functionality to a Process Object in Control Builder

It is possible to change and add functionality to a process object type in the Control Builder. The procedure for doing this, is to first make a copy of the appropriate object type to your own library, and then to make the desired changes in this copy.

Changes can be made in a control module type used in the copied process object type, for example, the type of interaction window. To do this, the control module type must first be copied. You then also replace the type of the control module in the copied process object type with the new type. See the step-by-step description below.

Creating a New Library and Copying an Object

1. In the Project Explorer right click on the Libraries folder and select New Library...

2. Type the desired name of the library to be created in the Name text field, for example, MotorLib. Click the OK button.

3. Choose the object to be changed in ProcessObjExtLib, for example, MotorBi (in the Function Block Types folder) or MotorBiM (in the Control Module Types folder).

4. Right-click on the desired object and select Copy (Ctrl+C).

5. Right-click on the Function Block Types or the Control Module Types folder in the new created library (in this example MotorLib), depending on wether the copied object is a function block type or a control module type. Select Paste (Ctrl+V).


www.cadfamily.com

Section 3 Object Handling Examples Creating a New Library and Copying an Object

wwwThe

The default name of the copied object, is the name of the copied original object type followed by underscore and a number, for example, a copy of MotorBi is named MotorBi_1. To change the name of the object proceed as follows:

6. Right-click on the object and select Rename...

7. Type the desired name of the object, in the New name text field, in this example, Motor_2. Click the OK button.

Figure 33. Copying of object types to a new library, MotorLib.

The process object types in ProcessObjExtLib include a number of control modules, for example, the FplateMtrBiAlGM1 control module, which can be used as an interaction window for the MotorBi process object type. The control modules refer (or point) to their types in ProcessObjExtLib. If these control module types are to be changed, they must also to be copied. The type of control module used in the copied process object type (the one that refers to the control module type in the ProcessObjExtLib), has to be replaced by the copied control module type.

Newly created library

Renamed motor object type

A copy of the MotorBi type pasted into the MotorLib (by default named MotorBi_1).


www.cadfamily.com

Creating a New Library and Copying an Object Section 3 Object Handling Examples

wT

8. Expand the folder of the copied process object type and identify the control module types that refer to the control modules used in the process object type. For example, the control module type FaceplateMotorBi refers to control module FplateMtrAlGBiM1 used in the MotorBi process object type.

Figure 34. The control module type is copied to your own created library.

9. In the Control Module Types folder under ProcessObjExtLib, select the control module type that is to be changed for the copied process object type.

10. Right-click on the control module type and select Copy (Ctrl+C).

11. Right-click on the Control Module Types folder in the newly created library (in this example MotorLib). Select Paste (Ctrl+V). (See steps 6 and 7 if you wish to change the name of an object type.)

Figure 35. The Control Module Types folder in which the copied type is pasted.


www.cadfamily.com

Section 3 Object Handling Examples Creating a New Library and Copying an Object

wwwThe

12. Select the control module type that is to be replaced, under the process object type, in your own created library (MotorLib), in this example, FPlateMtrBiAlGM1 under MotorBi_1. See Figure 34 above.

13. Right-click and select Replace Type.

14. In the Libraries/Application pane, select your own created library and in the Control module type pane, select the control module type that is to replace the original type. (It is possible to rename the control module in the Instance name field). Click the OK button.

Figure 36. Replace Control Module Type dialog box.


www.cadfamily.com

Adding Functionality Section 3 Object Handling Examples

wT

Adding Functionality

It is also possible to change and add your own functionality to the copied object types. In the example below, a level detection for motor speed is added to the object type that was copied above, MotorBi_1.

1. In the Function Block Types folder in MotorLib, right-click on the MotorBi_1 type and select Editor (ENTER).

2. Place the cursor in the code pane and choose Edit>Find... (Ctrl+F) in the menu. Search for the text level detection.

3. Make a copy of the code concerning ***Compute the level detection on the associated analog input signal*** and paste it into the code pane.

4. According to Figure 37 below, declare the new function block (LevelDetectionSpeed), change the function block name in the code pane and declare the required variables. Connect the parameters by right-clicking on the function block in the code pane and selecting Edit>Parameter list (Ctrl+M).

5. Select Editor>Apply and Close (Ctrl+U) to implement the changes made in the MotorBi_1 object type.

In this example, no functionality for alarm text handling has been added.


www.cadfamily.com

Section 3 Object Handling Examples Adding Functionality

wwwThe

Figure 37. Level detection functionality added to the MotorBi_1 function block type

It is now possible to use the MotorBi_1 function block type in a program, with the new added functionality.

6. In the Program folder under Applications, right-click on a program, for example Program2, and select Editor (ENTER).

7. Declare a function block of the type MotorBi_1 (in this example called MotorBi).

8. Insert the function block in the code pane, connect the desired parameters and declare the required variables. (In this example the Function Block Diagram language is used).


www.cadfamily.com

Adding Functionality Section 3 Object Handling Examples

wT

Figure 38. MotorBi function block with connections to variables.

9. Select Editor>Apply and Close (Ctrl+U) to implement the changes.


www.cadfamily.com

Section 3 Object Handling Examples Editing a Faceplate in Process Portal A

wwwThe

Editing a Faceplate in Process Portal AIn Process Portal A, the faceplate of a process object type can be edited and adjusted in the to suit the current application. For example, graphics for the presentation of a value can be added to a faceplate element.

Copying and Deploying Aspects

Before editing the faceplate, you must copy the faceplate, and faceplate and graphic elements from the same type in the processobjextlib to the copied object type and implement them (make deploy).

1. Open Plant Explorer Workplace in Process Portal A and select Object Type Structure in the drop-down list.

2. Select the MotorBi_1 object type in Control System>AC 800M/C Connect>Libraries>MotorLib.

3. Compare the aspects of MotorBi_1 with aspects of MotorBi in the library processobjextlib (Control System>AC 800M/C Connect>Libraries> processobjextlib>Function Block Types>MotorBi).

To avoid problems following upgrades, do not change in faceplate elements of the process object type directly. It is recommended that you add your own tabs to the faceplate (or delete existing ones) and edit/add your own graphics for value presentation in these tabs etc.

Make sure that objects are mirrored to the Aspect Server in the Control Builder (the check box should be checked in Tools>Mirroring to Aspect Server).


www.cadfamily.com

Copying and Deploying Aspects Section 3 Object Handling Examples

wT

Figure 39. Aspects of MotorBi_1 and MotorBi

As you can see, MotorBi_1 does not have any faceplates, graphic and faceplate element aspects. These have to be copied from MotorBi in processobjextlib to MotorBi_1 in MotorLib.

4. In the object structure of Control System>AC 800M/C Connect>Libraries> processobjextlib>Function Block Types>MotorBi, make copies of the aspects (see below) and paste them into Control System>AC 800M/C Connect>Libraries> MotorLib>MotorBi_1.

Aspects to be copied:AlarmControl, Command, Display Element Icon, Display Element Tag, Interlock, MainFacePlate, Parameters, RedInterlock, Status and TrimCurve.


www.cadfamily.com

Section 3 Object Handling Examples Copying and Deploying Aspects

wwwThe

Repeat steps a and b for all the aspects.

a. Right-click on an aspect of MotorBi to be copied and select Copy.

b. Right-click in the aspect window of MotorBi_1 and select Paste.

All the copied graphics aspects must be deployed before they can be edited or used.

5. In the Start menu of the PC, select Programs>ABB Industrial IT>Process Portal A> Display Tool.

6. Choose Object Type Structure in the drop-down list.

7. Make sure that the radio button Deploy Required is selected and select all aspects belonging to MotorBi_1.

Figure 40. The Display Tool for deploying objects.


www.cadfamily.com

Editing a Faceplate Section 3 Object Handling Examples

wT

8. Click the Deploy Selected button. It will take a few seconds for all the objects to be deployed. All the selected aspects have been deployed when they disappeared from the Display Tool window.

9. Close the Display Tool window.

Editing a Faceplate

After all the required aspects have been copied and deployed, it is possible to edit the faceplate of the object.

In this example, the level detection functionality that was added in the example above (Adding Functionality to a Process Object in Control Builder on page 98) is added as graphics in the faceplate of MotorBi_1.

The easiest way to add graphics for the level detection functionality is to copy the faceplate element of Parameters and edit it so that it contains the appropriate graphics.

1. Right-click on the faceplate element of Parameters and select Copy.

2. Right-click in the aspect window of MotorBi_1 and select Paste.

3. Right click on one of the faceplate elements of Parameters and select Rename.

4. Enter the new name of the faceplate element, for example, ParametersSpeed.

5. Right-click on the faceplate element of ParametersSpeed and select Edit to opens MS Visual Basic.

6. In this faceplate, only graphics for the level detection values is to be displayed. Right-click on the top of the faceplate element and select Delete to remove graphics for the other parameters.


www.cadfamily.com

Section 3 Object Handling Examples Editing a Faceplate

wwwThe

Figure 41. Deletion of a graphics element.

7. In the Properties window, set top value to 3 (moves the LevelDetection graphics to the top of the background).

Figure 42. The LevelDetection graphics moved to the top of the background.


www.cadfamily.com


wT

8. In the Expression Builder window, all the connections in the expressions from the signals used in the LevelDetection function block are changed to the signals used in the LevelDetectionSpeed function block. For example, the signal in the expression for MotorEnable is to be changed from EnableLevelDetection to EnableLevelDetectionSpeed (see the figure below).

Figure 43. Changing the signals from EnableLevelDetection to EnableLevelDetectionSpeed in the Expression Builder window.


www.cadfamily.com


wwwThe

9. Change all the other signal connections in the same way.

Figure 44. All the connections have been made to the LevelDetectionSpeed inthe Expression Builder

10. Make deploy .

11. Exit MS Visual Basic.


www.cadfamily.com


wT

12. Click on the No button in the Save dialog box.

13. In the Plant Explorer Workplace, right-click on the MainFaceplate aspect of MotorBi _1 and select Config View.

14. Select the Element tab and choose Extended in the drop-down list.

15. Click on the Add button to add a new line.

16. Click in the Aspect column of the new line and choose the ParametersSpeed aspect from the drop-down list.

Figure 45. Adding the ParametersSpeed aspect as a new tab in the extended MainFaceplate.


www.cadfamily.com


wwwThe

17. Click in the Tab group column of the new line and enter 2 (1 = left part of the faceplate and 2 = right part of the faceplate).

18. Click in the Caption column of the new line to enter a label to the new tab. In the Label field of the Caption dialog box, enter the label name, for example, Speed Detection.

19. Click in the UserRoles column of the new line and choose EveryOne from the drop-down list.

Figure 46. The ParametersSpeed aspect added as the Speed Detection tab.

20. Click on the Apply button to implement the changes and close the window.

21. Right-click on the MainFaceplate aspect and select Extended Faceplate.

22. Select the Speed Detection tab in the right part of the faceplate to view the newly added graphics.


www.cadfamily.com

Using a Faceplate in Online Mode Section 3 Object Handling Examples

wT

Figure 47. The new added Speed Detection tab in the extended faceplate

Using a Faceplate in Online Mode

If all the connections have been made correctly it is possible to view the values of LevelDetectionSpeed in online mode.

1. In the Control Builder, select Download Project and Go Online.

2. In the Plant Explorer Workplace of Process Portal A, select the Control Structure in the drop-down list.

3. In Root>Control Network>ProcessObj>Applications>Application_1> Programs>Program2, select MotorBi_1 of MotorBi type.

4. Right-click on the MainFaceplate aspect and select Extended Faceplate.


www.cadfamily.com

Section 3 Object Handling Examples Using a Faceplate in Online Mode

wwwThe

5. Select the Speed Detection tab in the right part of the faceplate to view the values in online mode.

Figure 48. MainFacePlate of the MotorBi_1 type in online mode.


www.cadfamily.com

Using a Faceplate in Online Mode Appendix A Displaying Element Icons

wT

Appendix A Displaying Element Icons

A Display Element Icon aspect, representing the object type is associated with each process object type. There are a number of standard icon types associated with each Display Element Icon of a process object type. (For more information about display elements, see also AC800M/C Connect, Installation and Configuration manual).

Table 10. Standard icon types associated with each Display Element Iconof a process object type

Bi MotorBi MotorUni Uni ValveUni

0 - Text 0 - Text 0 - Text 0 - Text 0 - Text

1 - General icon 1 - Motor With M 1 - Motor With M 1 - General icon 1 - 2D valve No Actuator

2 - 3D button 2 - Motor Without M 2 - Motor Without M 2 - 3D diamond 2 - 2D valve Hand1


www.cadfamily.com

Appendix A Displaying Element Icons Using a Faceplate in Online Mode

wwwThe

3 - Pump 3 - Pump 3 - 2D valve Hand 2

4 - Fan 4 - Fan 4 - 2D valve Actuator

5 - Compressor 5 - Compressor 5 - 2D valve Motor

6 - Feeder 6 - Feeder 6 - 2D valve Solenoid

7 - Sensor Screw 7 - Sensor Screw 7 - 2D valve Piston

Table 10. Standard icon types associated with each Display Element Iconof a process object type (continued)



www.cadfamily.com

Using a Faceplate in Online Mode Appendix A Displaying Element Icons

wT

8 - Rotary 8 - Rotary 8 - 2D valve Diaphragm

9 - Conveyor 9 - Conveyor 9 - 3D valve

10 - Reamer 10 - Reamer

11 - Screw 11 - Screw

12 - 3D motor 12 - 3D motor

Table 10. Standard icon types associated with each Display Element Iconof a process object type (continued)



www.cadfamily.com

Appendix B Signal Objects General

wwwThe

Appendix B Signal Objects

GeneralThe library SignalLib contains signal object function block types. These function block types extend the functionality of I/O signals (analog and digital input and output signals), and application variables with alarm and event handling. See the Control Builder online help, for more information about the function block types.

Faceplate ElementsThe graphics in the faceplate elements of a signal object type is adjusted by setting the visibility of the graphics (in MS Visual Basic). In this appendix, the faceplate elements show the default settings only, that is, some graphics are not visible. However, there are descriptions of all the signals that can be connected and displayed in the faceplate element.

Up to six different faceplate elements can be connected to each faceplate of a signal object type.

The TrimCurve faceplate element in all signal object faceplates refers (points) to the TrimeCurve1 in the processobjextlib folder. The Limits faceplate in SignalOutReal refers to Controller Limits in the Libraries folder.


www.cadfamily.com

SignalBool Appendix B Signal Objects

wT

SignalBool

The SignalBool faceplate elements contain the signal connections and graphics as displayed below.

Table 11. The SignalBool faceplate elements

Signal Description Graphics of Faceplate Element (default)

Enable Diff Alarm/EventVisible: AEConfigDiff>0,1,0Check ErrorVisible: AEConfigErr>0,1,0Filter TimeOpcOK: InteractionPar.AEFilterTime

Enable

InOpcOK: InVisible: InteractionPar.Man or ForceError or not InIn NormalOpcOK: InNormalDiff NormalOpcOK: DiffNormalError ModeCaption: ErrorInt InteractionPar.ErrorMode=0,"Through", InteractionPar.ErrorMode=1,"Freeze", InteractionPar.ErrorMode=2,"Predetermined"

Faceplate


www.cadfamily.com

Appendix B Signal Objects SignalBool

wwwThe

ThroughValue: InteractionPar.ErrorMode=0,true,falseFreezeValue: InteractionPar.ErrorMode=1,true,falsePredeterminedValue: InteractionPar.ErrorMode=2,true,falsePredetermined valueValue: InteractionPar.PredeterminedValue,1,0

Parameters

InOpcOK: InVisible: InteractionPar.Man or ForceError or not In

RedFaceplate

In1Value: In,0.9,0.1In2Value: Out,0.9,0.1TimeScaleMax: 0TimeScaleMin: TrimCurveTime

TrimCurve

Table 11. The SignalBool faceplate elements (continued)



www.cadfamily.com

SignalInBool Appendix B Signal Objects

wT

SignalInBool

The SignalInBool faceplate elements contain the signal connections and graphics as displayed below.

Table 12. The SignalInBool faceplate elements


Enable Diff Alarm/EventVisible: AEConfigDiff>0,1,0Filter TimeOpcOK: InteractionPar.AEFilterTime

Enable

InOpcOK: In.IOValueVisible: In.ForcedIn NormalOpcOK: InNormalDiff NormalOpcOK: DiffNormal

Faceplate


www.cadfamily.com

Appendix B Signal Objects SignalInBool

wwwThe

InOpcOK: In.IOValueVisible: In.Forced or not In.IOValue

RedFaceplate

In1Value: In.IOValue,0.9,0.1In2Value: Out,0.9,0.1TimeScaleMax: 0TimeScaleMin: TrimCurveTime

TrimCurve

Table 12. The SignalInBool faceplate elements (continued)



www.cadfamily.com

SignalInReal Appendix B Signal Objects

wT

SignalInReal

The SignalInReal faceplate elements contain the signal connections and graphics as displayed below.

Table 13. The SignalInReal faceplate elements


HHHLevelOpcOK: InteractionPar.LevelHHHVisible: AEConfigHHH>0,1,0HHLevelOpcOK: InteractionPar.LevelHHVisible: AEConfigHH>0,1,0HLevelOpcOK: InteractionPar.LevelHVisible: AEConfigH>0,1,0LLevelOpcOK: InteractionPar.LevelLVisible: AEConfigL>0,1,0LLLevelOpcOK: InteractionPar.LevelLLVisible: AEConfigLL>0,1,0LLLLevelOpcOK: InteractionPar.LevelLLLVisible: AEConfigLLL>0,1,0ErrorVisible: AEConfigErr>0,1,0HysteresisOpcOK: InteractionPar.AEHysteresisFilter TimeOpcOK: InteractionPar.AEFilterTime

Enable


www.cadfamily.com

Appendix B Signal Objects SignalInReal

wwwThe

Vertical BarEnd Value: VScaleMaxStart Value: VScaleMinManOpcOK: In.ValueVisible: In.ForcedInOpcOK: AnalogInOpcOKVisible: In.Forced or In.Status<>1OutOpcOK: Out.QualityOkStatusCaption: In.Status=-4029,"Underflow",In.Status=-4030,"Overflow",In.Status=-4031,"Unit error"In.Status=-4032,"Channel error"Error modeCaption: InteractionPar.ErrorMode=0,"Through",InteractionPar.ErrorMode=1,"Freeze",InteractionPar.ErrorMode=2,"Predetermined"Error indicatorOpcOK: OutHorizontal ScaleEndValue: HScaleMaxStartValue: HScaleMin

Faceplate

Table 13. The SignalInReal faceplate elements (continued)



www.cadfamily.com

SignalInReal Appendix B Signal Objects

wT

Filter timeOpcOK: InteractionPar.FilterTimeThroughValue: InteractionPar.ErrorMode=0,true,falseFreezeValue: InteractionPar.ErrorMode=1,true,falsePredeterminedValue: InteractionPar.ErrorMode=2,true,falsePredetermined valueOpcOK: InteractionPar.PredeterminedValueOut rate inc/decOpcOK: InteractionPar.OutIncDecLimFractionOpcOK: Fraction

Parameters

InOpcOK: In.IOValueVisible: In.Forced or In.Status<>1ManOpcOK: In.ValueVisible: In.ForcedOutOpcOK: Out

RedFaceplate




www.cadfamily.com

Appendix B Signal Objects SignalInReal

wwwThe

In1Max: In.Parameters.MaxIn1Min: In.Parameters.MinIn1Value: In.IOValueIn2Max: In.Parameters.MaxIn2Min: In.Parameters.MinIn2Value: OutIn3Max: In.Parameters.MaxIn3Min: In.Parameters.MinIn3Value: In.ValueIn3Visible: In.ForcedLeftScaleFraction: FractionTimeScaleMax: 0TimeScaleMin: TrimCurveTime

TrimCurve




www.cadfamily.com

SignalOutBool Appendix B Signal Objects

wT

SignalOutBool

The SignalOutBool faceplate elements contain the signal connections and graphics as displayed below.

Table 14. The SignalOutBool faceplate elements


Enable Diff Alarm/EventVisible: AEConfigDiff>0,1,0Filter TimeOpcOK: InteractionPar.AEFilterTime

Enable

InOpcOK: InVisible: Out.ForcedOut NormalOutNormalDiff NormalDiffNormal

Faceplate


www.cadfamily.com

Appendix B Signal Objects SignalOutBool

wwwThe

InOpcOK: InVisible: Out.Forced or not In

RedFaceplate

In1Value: In,0.9,0.1In2Value: Out.IOValue,0.9,0.1TimeScaleMax: 0TimeScaleMin: TrimCurveTime

TrimCurve

Table 14. The SignalOutBool faceplate elements (continued)



www.cadfamily.com

SignalOutReal Appendix B Signal Objects

wT

SignalOutReal

The SignalOutReal faceplate elements contain the signal connections and graphics as displayed below.

Table 15. The SignalOutReal faceplate elements



Enable


www.cadfamily.com

Appendix B Signal Objects SignalOutReal

wwwThe

Vertical BarEnd Value: VScaleMaxFraction: FractionStart Value: VScaleMinInOpcOK: In.QualityOkVisible: Out.ForcedOutOpcOK: AnalogOutOpcOKStatusCaption: Out.Status=-4031,"Unit error",Out.Status=-4032,"Channel error",Error modeCaption: InteractionPar.ErrorMode=0,"Through",InteractionPar.ErrorMode=1,"Freeze",InteractionPar.ErrorMode=2,"Predetermined"Error indicatorOpcOK: AnalogOutOpcOKHorizontal ScaleEndValue: HScaleMaxFraction: FractionStartValue: HScaleMin

Faceplate

Table 15. The SignalOutReal faceplate elements (continued)



www.cadfamily.com

SignalOutReal Appendix B Signal Objects

wT

Fraction: FractionLimit: InteractionPar.LimitOutputLimitMax: InteractionPar.OutMaxLimitLimitMaxOpcOK: InteractionPar.OutMaxLimitLimitMin: InteractionPar.OutMinLimitLimitMinOpcOK: InteractionPar.OutMinLimitRangeMax: Out.Parameters.MaxRangeMin: Out.Parameters.MinRangeUnit: Out.Parameters.Unit

Limits

FractionOpcOK: Fraction

Parameters




www.cadfamily.com

Appendix B Signal Objects SignalOutReal

wwwThe

InOpcOK: In.QualityOkVisible: Out.Forced or not InOutOpcOK: Out.Forced, Out.IOValue, Out.Value

RedFaceplate

In1Max: Out.Parameters.MaxIn1Min: Out.Parameters.MinIn1Value: InIn2Max: Out.Parameters.MaxIn2Min: Out.Parameters.MinIn2Value: Out.Forced, Out.IOValue, Out.ValueLeftScaleFraction: FractionTimeScaleMax: 0TimeScaleMin: TrimCurveTime

TrimCurve




www.cadfamily.com

SignalReal Appendix B Signal Objects

wT

SignalReal

The SignalReal faceplate elements contain the signal connections and graphics as displayed below.

Table 16. The SignalReal faceplate elements



Enable


www.cadfamily.com

Appendix B Signal Objects SignalReal

wwwThe

Vertical BarEnd Value: VScaleMaxStart Value: VScaleMinManOpcOK: InteractionPar.ManValueVisible: InteractionPar.ManInOpcOK: AnalogInOpcOKVisible:InteractionPar.Man or ForceErrorOutOpcOK: Out.QualityOkError modeCaption: InteractionPar.ErrorMode=0,"Through",InteractionPar.ErrorMode=1,"Freeze",InteractionPar.ErrorMode=2,"Predetermined"Error indicatorOpcOK: OutHorizontal ScaleEndValue: HScaleMaxStartValue: HScaleMin

Faceplate

Predetermined valueOpcOK: InteractionPar.PredeterminedValueOut rate inc/decOpcOK :InteractionPar.OutIncDecLimRangeMaxOpcOK: InteractionPar.RangeMaxRangeMinOpcOK: InteractionPar.RangeMinFractionOpcOK: Fraction

Parameters

Table 16. The SignalReal faceplate elements (continued)



www.cadfamily.com

SignalReal Appendix B Signal Objects

wT

InOpcOK: InVisible: InteractionPar.Man or ForceErrorManOpcOK: InteractionPar.ManValueVisible: InteractionPar.ManOutOpcOK: Out

RedFaceplate

In1Max: InteractionPar.RangeMaxIn1Min: InteractionPar.RangeMinIn1Value: InIn2Max: InteractionPar.RangeMaxIn2Min: InteractionPar.RangeMinIn2Value: OutIn3Max: InteractionPar.RangeMaxIn3Min: InteractionPar.RangeMinIn3Value: InteractionPar.ManValueIn3Visible: InteractionPar.ManLeftScaleFraction: FractionTimeScaleMax: 0TimeScaleMin: TrimCurveTime

TrimCurve

Table 16. The SignalReal faceplate elements (continued)



www.cadfamily.com

INDEX

wwwThe

Aadding functionality

Control Builder 102alarm

Bi 63MotorBi 76MotorUni 70Uni 54ValveUni 58

auto modeBi 61BiCore 33MotorBi 73MotorUni 67Uni 52UniCore 22ValveUni 57

Bbasic library 17, 18

core objects 18edge detection 19

Bi 60alarm 63auto mode 61change-over action 62disable mode 61error text string 64faceplate elements 86feedback configuration 62interaction window 65interlocking 62local mode 62

Bi 60 (cont.)manual mode 61mode 61object error 63operation 61output settings 62panel mode 62

BiCore 31auto mode 33change-over action 40configuration feedback signals 38disable mode 32Ilock 41inhibit 42interlocking 41local mode 37manual mode 33mode 32object error 43operation 32output settings 39panel mode 34safety command 42simulation 39

BiHSI 44effective feedback 45forced action 45interlock 45output IOLevel 45


www.cadfamily.com

Index

wwwThe

Cchange-over action

Bi 62BiCore 40MotorBi 74

choosing process object 16configuration feedback signals

BiCore 38UniCore 26

Control Builderadding functionality 102creating a library 98

control wordDriveCore 46

controlling a DriveDriveCore 47

copying an object 98Control Builder 98

copying aspectsProcess Portal A 105

core objects 18creating a library

Control Builder 98

Ddeploying aspects

Process Portal A 105disable mode

Bi 61BiCore 32MotorBi 73MotorUni 67Uni 52UniCore 21ValveUni 57

display element iconsprocess object 116

DriveCore 46control word 46controlling a Drive 47emergency stop 47scaling Drive values 48status 46

Eedge detection 19edit

faceplate 108editing a faceplate

Process Portal A 105effective feedback

BiHSI 45UniHSI 30

emergency stopDriveCore 47

error text stringBi 64MotorBi 76MotorUni 70Uni 54ValveUni 59

extended library 17, 49function blocks or control modules 50

extended process objects 50

Ffaceplate 78

edit 108general 78online mode 114


www.cadfamily.com

Index

wwwThe

faceplate elementsBi 84, 86Command 84LevelDetection 84MotorBi 88MotorUni 85, 91Parameters 84signal object 119SignalBool 120SignalInBool 122SignalInReal 124SignalOutBool 128SignalOutReal 130SignalReal 134TrimCurve1 84Uni 94ValveUni 96

feedback configurationBi 62MotorBi 74Uni 53ValveUni 57

feedfack configurationMotorUni 68

forced actionBiHSI 45UniHSI 30

IIlock

BiCore 41MotorBi 75MotorUni 68UniCore 27

inhibitBiCore 42MotorBi 75MotorUni 69UniCore 27

interaction windowBi 65MotorBi 77MotorUni 71Uni 55ValveUni 59

interlockBiHSI 45UniHSI 30

interlockingBi 62BiCore 41MotorBi 75MotorUni 68Uni 53UniCore 20, 27ValveUni 58

Llocal mode

Bi 62BiCore 37MotorBi 74MotorUni 68Uni 53UniCore 25

Mmanual mode

Bi 61BiCore 33MotorBi 73MotorUni 67Uni 52UniCore 21ValveUni 57


www.cadfamily.com

Index

wwwThe

modeBi 61BiCore 32MotorBi 73MotorUni 67Uni 52ValveUni 57

MotorBi 72, 84alarm 76auto mode 73change-over action 74disable mode 73error text string 76faceplate elements 88feedback configuration 74Ilock 75inhibit 75interaction window 77interlocking 75local mode 74manual mode 73mode 73object error 76operation 73output settings 74panel mode 74safety command 75

MotorUni 66alarm 70auto mode 67disable mode 67error text string 70faceplate elements 91feedback configuration 68feedfack configuration 68Ilock 68inhibit 69interaction window 71interlocking 68local mode 68

MotorUni 66 (cont)mode 67object error 69operation 67output settings 68panel mode 68safety command 69

MotorUni manual mode 67

Oobject error

Bi 63BiCore 43MotorBi 76Uni 53UniCore 20, 28ValveUni 58

online modefaceplate 114

operationBi 61BiCore 32MotorBi 73MotorUni 67Uni 52UniCore 20, 21ValveUni 57

operation modeUniCore 21

output IOLevelBiHSI 45UniHSI 30

output settingsBi 62BiCore 39MotorBi 74MotorUni 68Uni 53UniCore 26ValveUni 57


www.cadfamily.com

Index

wwwThe

Ppanel mode

Bi 62BiCore 34MotorBi 74MotorUni 68Uni 52UniCore 22

process object 13display element icons 116

Process Portal Acopying aspects 105deploying aspects 105editing a faceplate 105

Ssafety commands

BiCore 42MotorBi 75MotorUni 69UniCore 27

scaling Drive valuesDriveCore 48

signal objectsfaceplate elements 119

SignalBoolfaceplate elements 120

SignalInBoolfaceplate elements 122

SignalOutBoolfaceplate elements 128

SignalOutRealfaceplate elements 130

SignalRealfaceplate elements 134

simulationBiCore 39UniCore 27

statusDriveCore 46

Tterminology 10

UUni 51, 85

alarm 54auto mode 52disable mode 52error text string 54faceplate elements 94feedback configuration 53interaction window 55interlocking 53local mode 53manual mode 52mode 52object error 53operation 52output settings 53panel mode 52

UniCore 20auto mode 22configuration feedback signals 26disable mode 21Ilock 27inhibit 27interlocking 20, 27local mode 25manual mode 21object error 20, 28operation 20, 21operation mode 21output settings 26panel mode 22safety command 27simulation 27


www.cadfamily.com

Index

wT

UniHSI 29effective feedback 30forced action 30output IOLevel 30

UniHSI interlock 30

VValveUni 56, 85

alarm 58auto mode 57disable mode 57error text string 59faceplate elements 96feedback configuration 57interaction window 59interlocking 58manual mode 57mode 57object error 58operation 57output settings 57


www.cadfamily.com

3BSE 028 810 R101 Rev A. Printed in Sweden September 2002Copyright © 1999 by ABB. All Rights Reserved® Registered Trademark of ABB.™ Trademark of ABB.

Automation Technology ProductsMannheim, Germanywww.abb.de/processautomationemail: [email protected]

Automation Technology Products Västerås, Swedenwww.abb.com/processautomationemail: [email protected]

Automation Technology ProductsWickliffe, Ohio, USAwww.abb.com/processautomationemail: [email protected]

http://www.abb.com/control


www.cadfamily.com

ABB Control ProcMan

Documents