PMD Builder - Blocks

Experion PKS
Blocks application
definition
Experion PKS
Blocks application definition
Release: System Release 710
09/2007
PMD Builder_Blocks_Eng.doc
Section: 3-
Notices, Copyright, and Trademarks

While this information is presented in good faith and believed to be
accurate, Honeywell disclaims the implied warranties of
merchantability and fitness for a particular purpose and makes no
express warranties except as may be stated in its written agreements
with and for its customers. In no event is Honeywell liable to anyone
for any indirect, special or consequential damages.
The information and specifications in this document are subject to
change without notice.
© Copyright 1989 – 2007 by Honeywell Oy. No part of this
publication may be reproduced or translated, stored in a database or
retrieval system, or transmitted in any form or by any means,
electronic, mechanical, photocopying, recording, or otherwise,
without the prior written permission of Honeywell Oy.
Experion ® Process Knowledge System (PKS) is a registered
trademark of Honeywell International Inc. All other brand or product
names mentioned in the document are trademarks of their respective
owners.
Honeywell Oy
Viestikatu 1-3
FIN-70600 Kuopio, Finland
Phone +358 20752 2000
Telefax +358 20752 2400
http://www.honeywell.fi
Contents
1 Blocks application definition with the Block Builder 1
1.1 Purpose of Blocks application definition ............................................................................1
1.2 Starting up the Blocks application definition .....................................................................2
1.3 Creating block definitions.....................................................................................................3
1.3.1 Hierarchical blocks, model blocks, type blocks and basic blocks......................3
1.3.2 Menu bar and Toolbar.............................................................................................4
1.3.3 Block Builder workspace.........................................................................................5
1.3.4 Browse window........................................................................................................6
1.3.5 Selecting functions from the menu ........................................................................9
1.3.6 Selecting functions from the toolbar....................................................................10
1.3.7 Defining colors .......................................................................................................10
2 File 12
2.1 File menu description ..........................................................................................................12
2.2 Open.......................................................................................................................................12
2.3 Save ........................................................................................................................................14
2.4 Simulate.................................................................................................................................14
2.5 Print........................................................................................................................................15
2.6 Print preview ........................................................................................................................17
2.6.1 Selecting the Print preview function options from the instant menu.............18
2.7 Load .......................................................................................................................................18
2.8 Load type...............................................................................................................................19
2.9 Monitor ..................................................................................................................................20
2.10 Delete ..................................................................................................................................21
3 Edit 22
3.1 Edit menu description .........................................................................................................22
3.2 Copy.......................................................................................................................................22
3.3 Back and Forward ................................................................................................................23
4 Blocks 24
4.1 Blocks menu description .....................................................................................................24
4.2 Header ...................................................................................................................................24
4.2.1 Hierarchical block Header ....................................................................................25
4.2.2 Hierarchical block Execution data (priority, phase and execution cycle) ......28
4.2.3 Setting initial Face Plate values for hierarchical blocks ....................................32
4.2.4 Type block Header.................................................................................................33
4.3 Description............................................................................................................................34
4.4 Insert ......................................................................................................................................34
4.4.1 Inserting hierarchical blocks and basic blocks ...................................................34
4.4.2 Inserting steps into a STEPX sequence block .....................................................35
4.5 Insert type .............................................................................................................................36
4.6 Delete .....................................................................................................................................36
4.7 Rename ..................................................................................................................................37
4.8 Export ....................................................................................................................................37
4.9 Import ....................................................................................................................................38
Experion PKS Contents • 3 - i

Blocks application definition 09/2007
4.10 Search ..................................................................................................................................40
4.11 Delete from system ..............................................................................................................40
5 Pins 41
5.1 Pins menu description .........................................................................................................41
5.2 Insert ......................................................................................................................................41
5.2.1 Defining pins for a hierarchical block .................................................................41
5.2.2 Defining pins for a sequence step block..............................................................46
5.2.3 Defining pins for a type block ..............................................................................48
5.3 Delete .....................................................................................................................................49
5.4 Change...................................................................................................................................50
6 Connections 51
6.1 Connections menu description...........................................................................................51
6.2 Link ........................................................................................................................................51
6.3 Connect with flags ...............................................................................................................52
6.4 Connect with name ..............................................................................................................53
6.5 Delete .....................................................................................................................................54
6.6 Show connections.................................................................................................................55
6.7 Invert......................................................................................................................................55
6.8 Constant.................................................................................................................................56
6.9 Variable..................................................................................................................................57
6.10 Show values ..........................................................................................................................58
6.11 Name ..................................................................................................................................58
6.11.1 Deleting the pin data name given by the Name function.................................59
6.12 Search ..................................................................................................................................59
6.13 Pin I/O and Pin description push buttons .......................................................................60
6.13.1 Pin I/O.....................................................................................................................60
6.13.2 Pin description........................................................................................................61
7 Execution 62
7.1 Execution menu description ...............................................................................................62
7.2 Show.......................................................................................................................................62
7.3 Change...................................................................................................................................63
7.3.1 Change / Order......................................................................................................63
7.3.2 Change / Modules.................................................................................................64
7.3.3 Change / Phases ....................................................................................................64
7.3.4 Change / Cycles.....................................................................................................65
7.3.5 Change / Priority...................................................................................................65
7.3.6 Change / Basic blocks ...........................................................................................66
7.3.7 Change / Face Plate names ..................................................................................67
7.3.8 Change / Departments .........................................................................................67
7.3.9 Change / Alarms output manner........................................................................68
8 Tools 69
8.1 Tools menu description.......................................................................................................69
8.2 Pascal .....................................................................................................................................69
9 Options 70
9.1 Options menu description ..................................................................................................70
9.2 Language ...............................................................................................................................70
9.3 Toolbar...................................................................................................................................71
9.4 Text case ................................................................................................................................71
9.5 Font ........................................................................................................................................71
9.6 Colors.....................................................................................................................................71
3 - ii • Contents Experion PKS

9.7 Menu bitmaps.......................................................................................................................73
10 Window 74
10.1 Window menu description .................................................................................................74
10.2 Arrange..................................................................................................................................74
10.3 Tile horizontal.......................................................................................................................74
10.4 Tile vertical............................................................................................................................74
10.5 Cascade..................................................................................................................................74
10.6 Close ..................................................................................................................................74
10.7 Close all .................................................................................................................................75
10.8 The name list of opened windows.....................................................................................75
11 Help 76
11.1 Help menu description........................................................................................................76
11.2 Contents.................................................................................................................................76
11.3 Search for help on.................................................................................................................77
11.4 Basic blocks ...........................................................................................................................77
11.5 System status messages.......................................................................................................77
11.6 About PMD Block Builder ..................................................................................................78
12 Defining faceplates and standard pins for tag blocks 79

12.1 Purpose of faceplates ...........................................................................................................79
12.1.1 Trend collection categories and collection data .................................................79
12.2 Measurement (Measure) .....................................................................................................80
12.3 Control (Control)..................................................................................................................83
12.4 One-way motor and Pump (M1Way)................................................................................87
12.5 Two-way and Two-speed motor (M2Way, M2Speed)....................................................91
12.6 Open/close valve and Three-way valve (Valve) .............................................................95
12.7 Motor valve (MValve) .........................................................................................................99
12.8 Control switch (CSwitch) ..................................................................................................102
12.9 Device control (Device) .....................................................................................................105
12.10 General logic (Genlog).......................................................................................................109
12.11 Binary (Binary) ...................................................................................................................112
12.12 Sequence (Sequence)..........................................................................................................115
13 Block Simulator / Block Monitor User Manual 118

13.1 Activation and operation of the Block Simulator / Block Monitor.............................118
13.2 Block menu..........................................................................................................................120
13.2.1 Open.......................................................................................................................120
13.2.2 Back and Next.......................................................................................................120
13.2.3 Print........................................................................................................................120
13.2.4 Run and Stop ........................................................................................................121
13.2.5 Speed......................................................................................................................121
13.2.6 Cycle ......................................................................................................................122
13.2.7 Test settings ..........................................................................................................122
13.2.8 Save variables .......................................................................................................123
13.2.9 Public pins.............................................................................................................123
13.3 Fields menu.........................................................................................................................123
13.3.1 Handle ...................................................................................................................124
13.3.2 Delete all................................................................................................................125
13.3.3 Settings ..................................................................................................................125
13.4 Return ................................................................................................................................126
14 Converting Block Builder Applications to XML files 127

14.1 Converting Block Builder Applications to XML files....................................................127
Experion PKS Contents • 3 - iii

1 Blocks application definition
with the Block Builder
1.1 Purpose of Blocks application definition

The Blocks application definition is used to define Experion PKS
with PMD Controller automation system’s measurements, controls,
motor and valve controls, logic, group start-ups and calculations, i.e.
all actual process control functions and their associated faceplate
data. Alarms and process history collection (trends) are also partly
defined in the Blocks application definition.
Selecting Blocks application definition in the PMD Builder opens the
Block Builder. The Block Builder uses the control of a specific process
to generate a block hierarchy that comprises various blocks. The
highest block in the block diagram is generated and named
automatically in accordance with the department definition made on
the PMD Builder’s Main Page. Departments are divided further into
smaller sections, i.e. hierarchical blocks that represent the various
process sections, machine groups, etc. Within each hierarchical block,
16 new blocks can be generated. When creating a hierarchy in the
downwards direction, the lowermost level is used to accommodate
the tag blocks, e.g. for measurements, controls and motors.
The tag blocks are mainly configured from pre-programmed basic
blocks. The ready made or project-specific type blocks can also be
used in tag blocks. In addition, the Block Builder’s high-level
language can be used to configure application-specific blocks which
are not included in the basic blocks. The high-level language used in
Block Builder is a Pascal programming language.
The tag blocks, new type blocks and model blocks are tested by a
Block Simulator activated via the Block Builder, immediately after
the block definition in question has been completed.
If a design module is connected to the system, it is also possible to
download the blocks into the system from the Block Builder and test
the system-loaded blocks with the Block Monitor. The tag blocks are
mainly downloaded into the automation system’s process modules
(PMD Controllers and XPR-A-based process modules) for execution.
Experion PKS Blocks application definition with the Block Builder • 3 - 1

1.2 Starting up the Blocks application definition
The Blocks application definition is started up from the PMD Builder
Main Page. Open the PMD Builder either by double-clicking the
PMD Builder icon on the desktop or by selecting
Start/Programs/PMD/PMD Builder.
If there are no existing project definitions or department definitions,
then create them by using the Create New function in the File menu
of the PMD Builder Main Page. For instructions, see document PMD
Builder.
If project and department definitions have been done, the

department is shown in the Connect window. Select the department
and press Connect.
Enter the credentials and press OK. The PMD Builder opens in a
System view.
3 - 2 • Blocks application definition with the Block Builder Experion PKS

Select the Blocks tab in the upper left corner of the PMD Builder
window. (If the tree view shows only the department name, pressing
the + sign in front of the department name opens the block
hierarchy.) To open the Block Builder, either:
• Double-click directly on the name of an individual block
with the left-hand mouse button, or
• Click on the name of an individual block with the right-
hand mouse button and select Edit from the menu
opened.
If the builder is started up at a specific block, then the block’s existing
definition will be displayed in the Block Builder.
Select the System tab to exit the Block Builder. The Block Builder
closes automatically and System definition opens.
1.3 Creating block definitions
1.3.1 Hierarchical blocks, model blocks, type blocks and basic blocks
The Block Builder is used to generate a block hierarchy from the
control of a specific process. The blocks of a block hierarchy are
divided into hierarchical blocks, model blocks, type blocks and basic
blocks.
A hierarchical block only contains inner hierarchical blocks or basic
blocks and type blocks. Those hierarchical blocks which contain basic
blocks and type blocks are called tag blocks. Tag blocks can also be
defined with the Block Builder’s high-level language.
When a tag block is saved as a model block, it can be used as a
template for new identical blocks or similar tag blocks. Note! Model
blocks are not available in system release 710.
Type blocks are also defined by the Block Builder, like tag blocks.
Type blocks are used like tag blocks, i.e. to execute the function
defined for the block. Type blocks can contain basic blocks and/or
other type blocks and they can be defined with the Block Builder’s
high-level language. A set of ready-made type blocks are available
for systems, for the purpose of implementing advanced control
methods, such as fuzzy logic, neural networks, optimization,
statistical process control, and the control of hydraulic directional
valves.
Basic blocks are always ready-made and included in the system
delivery.
Certain basic blocks and type blocks contain so many pins that they
cannot be shown simultaneously by the Block Builder. The bottom
edge of such blocks is provided with an extra box; placing the
pointer on the box and double-clicking the left-hand mouse button
displays the hidden pins for examination. The hidden pins cannot be
connected through wiring. An example of such a block is the PID
block whose nine hidden input pins can be displayed three pins at a
time.
Some basic blocks are provided with a triangle at their bottom edge,
indicating that pins may be added to them. To add pins, place the
pointer on the lowermost pin, depress the left-hand mouse button
and drag the mouse downwards. Once a suitable number of pins is
displayed, release the button. Correspondingly, pins are deleted by
dragging the mouse upwards.
The ADD block is an example of this block type.
1.3.2 Menu bar and Toolbar

The PMD Block Builder has a menu bar and toolbar which contain all
the functions required for block definition creation, testing and
downloading. The Block Builder’s workspace, in turn, always
contains the block to which all the functions are targeted. In addition
the block hierarchy being designed as well as the available libraries
are displayed on the left.

1.3.3 Block Builder workspace
All Block Builder menu functions and toolbar push button functions
are targeted at the block which is open in the Block Builder
workspace. The block name is displayed in the window title bar.
When several levels have been defined for a department’s block
hierarchy, instant opening can be used in the Block Builder
workspace, to move upwards or downwards in the hierarchy, one
level at the time. Instant opening can only be used for hierarchical
blocks, not for model, type or basic blocks.
• To open a block below an open block in the hierarchy in
the Block Builder, place the pointer on the block name
and double-click the left-hand mouse button.
• To open a block above an open block in the hierarchy in
the Block Builder, place the pointer on the Block Builder
title bar and double-click the left-hand mouse button.
It is also possible to open a block in the Block Builder workspace by
selecting it from the Browse window, or by using the menu bar
functions or toolbar functions.

Blocks that are inside the block being edited can be moved almost
freely from one Block Builder workspace site to another as follows:
1. Place the pointer with the mouse on the name of the block
to be moved and depress the left-hand mouse button. This
causes a rectangle to be displayed at the available block
sites.
2. Keeping the button depressed, move the block to the
selected block site and release the button.
Selecting functions from the Block Builder workspace

Click the right-hand mouse button on the Block Builder workspace to
open the following menu:
1.3.4 Browse window

The Browse window contains both the block hierarchy for the
department being designed and the available libraries.
The Browse window contains four tabs:
• The block hierarchy of the department being

defined.
• Basic block selection
• Type block selection connected to the system being

defined
• Model block selection connected to the system

being defined. Model blocks are not available in system
release 710.

To open a selected tab, place the pointer on the tab name and click
the left-hand mouse button.
The Hierarchy tab shows the block hierarchy of the department
being defined. The highest block in the hierarchy is always generated
automatically and has the same name as the department. The blocks
defined can be displayed from below the department block, until the
tag blocks are reached. The various block types are indicated by their
own symbols in the hierarchy.
Block symbols (Bitmaps):
The block hierarchy is browsed with the mouse. To activate a desired

block, place the pointer on its name and click the left-hand mouse
button. The currently active block in the hierarchy is indicated by a
blue background color. The plus sign (+) in front of a block name
indicates that the block contains sub-blocks. To display the sub-
blocks, place the pointer on the plus sign and click the left-hand
mouse button. Correspondingly, an opened block is closed by
clicking on the minus (-) sign in front of the block name.
Double-clicking on a block name with the left-hand mouse button
opens the block in question in the Block Builder workspace for
editing. At the same time, the block’s possible sub-blocks are
displayed in the hierarchy.
If changes have been made to a block opened in the Block Builder
workspace, without saving the changes, the Block Builder will ask:
Save the changes?. If the reply is:
• Yes : The changes will be saved and the selected block will
open in the Block Builder workspace.
• No : The changes will not be changed and the selected block
will open in the Block Builder workspace.
• Cancel : The new block will not open and the previous block
will remain in the Block Builder workspace.
The Basic tab contains the basic blocks.
Basic blocks may be added to a tag block being edited in the Block
Builder workspace by double-clicking on the name of the basic block
to be added with the left-hand mouse button. This will move the

basic block to the first vacant block site in the Block Builder
workspace.
Tip! Basic blocks that already exist in the Block Builder workspace
can be copied by depressing the CTRL key and clicking the desired
block with the left-hand mouse button. The copy of the block appears
to the first vacant block site in the Block Builder workspace.
The Type tab contains the type blocks that have been saved to the
type block directory of the project in question.
A type block is added to a tag block being edited in the Block Builder
workspace by double-clicking on the name of the type block.
After the type block has been added, double-clicking the mouse on
the type block name opens the type block in the Block Builder
workspace.
The Model tab contains the blocks saved to the model block
directory of the project in question. Note! Model blocks are not
available in system release 710.
Selecting functions from the Browse window

Click the right-hand mouse button on the Browse window to open
the following menu:
Monitor - Opens the Block Monitor

Simulate - Opens the Block Simulator
Load - Loads an individual block into the system, depending on
which of them has been selected from the hierarchical tree structure.
Mass operations (system) - Opens the following menu. For example,
the Load all command is used to load the selected block plus all the
blocks below it in the block hierarchy, from the Design Module to the
PMD server and further from the PMD server to the modules
(usually to the PMD Controllers) that execute the application.

The commands Expand One Level, Expand Branch, Expand All and
Collapse Branch can be used to expand or collapse the block
hierarchy.
The View command opens the following menu for selecting
information to be shown in the hierarchical tree structure.
1.3.5 Selecting functions from the menu

The Block Builder menus and their functions are activated either by
the mouse or via the keyboard. Part of the menu functions can also
be executed through the toolbar push buttons.
The functions are always targeted at the block, which is open in the
Block Builder workspace.
With the mouse:

1. To open a menu, place the pointer on the menu name and
click the left-hand mouse button.
2. To activate a function, click the left-hand mouse button on
the name of the function.
Via the keyboard:
1. To open a menu, depress simultaneously the Alt key and
the letter key underlined on the menu name.
2. To activate a function:
Use the arrow keys to select the desired function and

press the Enter key or
press the letter key underlined on the function name.
1.3.6 Selecting functions from the toolbar

The Block Builder is also provided with a toolbar. The toolbar push
buttons activate the same functions as those selected from the menu
bar menus.
The current availability of push buttons depends on the Block

Builder function being executed. Should a push button not be
available, its display symbol will be dim on the screen.
Correspondingly, the symbols of available push buttons are clearly
visible.
Toolbar push buttons:
Insert Name Forward
Open Constant Simulate
Save Variable Monitor
Print Invert Pascal
Load Show values Information
Delete Show connections Font
Link Pin IO Color
Connect with flags Pin description Description
Connect with name Back Contents
To activate a desired push button, click on it with the left-hand

mouse button.
1.3.7 Defining colors

Some Block builder definitions contain color definitions. Color
definitions are required e.g. when a General logic or a Binary
faceplate is selected for a tag block.
Colors are specified by using RGB color codes. An RGB color code
consists of three two-digit hexadecimal numbers specifying the
intensity of the corresponding color.
For example, red is the RGB color code #FF0000.
The following table lists the colors supported as of Internet Explorer
4.0

Table of RGB color codes:

2 File
2.1 File menu description

The File menu functions are targeted at tag blocks, model blocks and
type blocks. Among other things, the menu functions can be used to
save a block to the design module, activate the block simulator,
output block definitions to a printer, and download a block to the
system.
2.2 Open
The File menu’s Open function is used to open hierarchical blocks,
type blocks and model blocks.
In addition, the Open function is used to begin the creation of new
type blocks and model blocks.
New hierarchical blocks cannot be created with the Open function;
instead, a new hierarchical block is added to the block hierarchy by
using the Blocks menu’s Insert function.
See also section Hierarchical blocks, model blocks, type blocks and
basic blocks.
If changes have been made to the block currently open in the Block
Builder workspace without saving the changes, then the builder will
ask: Save changes?
3 - 12 • File Experion PKS

Yes : The changes will be saved and the Open/Save a block window
displayed.
No : The changes will not be changed and the Open/Save a block
window will be displayed.
Cancel : The Open function will be cancelled and the previous block
will remain in the Block Builder workspace.
Use the Open/Save a block window’s entry field to write the name of
the block to be opened. A hierarchical block to be opened may reside
higher or lower in the block hierarchy than the block currently open
in the Block Builder workspace.
If the block to be opened does not exist, the builder will display a
window requesting the type for the new block. New blocks may be
type blocks or model blocks. Creation of new basic blocks is not
possible at the configuration stage.
The Type block is a block assembled from a number of basic blocks

and/or other type blocks or it can be defined with the Block Builder's
high-level language. The type block is defined in the same way as a
hierarchical tag block. (Hierarchical blocks are added to the block
hierarchy by selecting Blocks/Insert from the menu bar.)
The name length of a type block is, however, seven characters. The
builder provides the 8th character as the version number, which is 0
in the case of a new block.
If the version number is not entered when opening the type block,
then the latest version is opened. If the version number entered is
other than the latest, the builder will display the latest version
number and request whether to open this version or not.
Note! Model blocks are not available in system release 710.
The Model block is an all-purpose block formed from a number of
basic blocks and type blocks. A model block is defined by the Block
Builder like a hierarchical block. However, model blocks cannot
Experion PKS File • 3 - 13
contain sub-blocks. Tag blocks are copied with the aid of model
blocks.
Basic blocks cannot be created at the configuration stage.
Model blocks and type blocks are not hierarchical, which is why they
are not visible in the block hierarchy. The type blocks saved to the
project directory are, however, visible on the Type tab in the Browse
window. Correspondingly, model blocks are displayed on the
Browse window’s Model tab.
2.3 Save
The File menu’s Save function is used to save the block, which is
currently in the Block Builder workspace, to the design module
memory. The function displays the following Save as window in the
builder.
Select Hierarchical if the block to be saved is one of the blocks in the

department’s block hierarchy, e.g. a tag block.
Hierarchical saves as hierarchical all the blocks contained in a
department’s block hierarchy, e.g. tag blocks.
Note! Model blocks are not available in system release 710.
Select Model if the block to be saved will be used as a model block,
i.e. it will be copied and used in many tag blocks.
Note! High-level language defined blocks cannot be saved through

the Save function. They must always be saved by the Program
Builder.
2.4 Simulate
The File menu’s Simulate function opens the Block simulator to
simulate and test blocks which have been marked as complete. It is
also possible to start simulation from the Browse window by clicking
on the block name with the right-hand mouse button and selecting
Simulate from the menu opened.
Type block simulation must be activated from a hierarchical block
which uses a type block.
Simulation means functional testing and examination of a block at
the design module. Block pin states can be monitored and have

desired values entered. In simulation, the testable block’s data
updates can be stopped on the screen at desired times, for more
accurate analysis of the test situation, for example. Following this,
updating of the block’s data can be re-activated.
The Block simulator’s user instructions are provided at the end of
this document, see section Block Simulator / Block Monitor User
Manual.
The Block Simulator and Block Monitor have a joint user manual,
due to the fact that their functions are almost identical. The Block
Simulator is used to test the blocks’ functions once they have been
completed. Simulation takes place at the design module and the pin
data items are entered either manually or through copying from a
simple process model. Monitoring, in turn, is used to test system-
loaded blocks which means that their pin data items are updated by
the system’s process modules (PMD Controllers and XPR-A-based
process modules).
2.5 Print
The File menu’s Print function outputs data from the defined block
hierarchy to a printer. The function displays a selection window to
select the content for printing.
When selecting any of the first five options, and accepting the choice
by pressing the OK push button, the following window is shown in
the display. In this window you can select the output options.

The Beginning block must be defined if the Cross reference list
(inputs and outputs) or the Cross reference list (outputs) is to be
printed.
If the option Ascii File or Html File is selected from the alternatives
of the Direct Output To, then the file path and file name can be
defined by writing them in the entry field, or by selecting them from
the Save as window opened by pressing the push button located on
the right of the entry field.
When selecting a Block document as the print content, printing is
targeted at the block being edited in the Block Builder workspace.
The print function can only be used to print the Block document on
the printer defined as the design module’s default printer.
To print the block document, the builder requests the following
additional definitions:
The All pages selection outputs the entire documentation of the

block being edited in the Block Builder workspace.
The First page only selection outputs the block documentation’s
front page only. The front page contains the data displayed in the
Block Builder workspace, plus the header table. The header table
displays the block name, the save date and the data written in the
Print window’s ID data fields.

In addition to the block residing in the Block Builder workspace, the
All blocks selection outputs all the sub-blocks contained in the block.
The All connections selection, in turn, extends printing to all the
blocks to which references are made to the block’s public pins.
The Pascal selection outputs the code written in the high-level
language.
2.6 Print preview

The File menu’s Print preview function displays the Block document
as it will be printed, i.e. the data shown in the Block Builder
workspace, plus the document header table.
The project related information (customer data) in the header table

are given in conjunction with the Block document definition in the
File / Print function. See section Print.

2.6.1 Selecting the Print preview function options from the instant
menu
The options of the Print preview function are selected via an instant
menu. The instant menu is displayed by clicking on the block
document with the left-hand mouse button. The available options
are:
Print
See section Print.
Style
Alcont Outputs the header table used in Alcont projects.
Printa Outputs the header table used in Printa projects.
Honeywell Outputs the general Honeywell header table.
Size
Default Block document is shown in the block document window in
size that can be correctly printed on the punched A4-size
paper.
Maximized Block document is shown in the block document window in
maximized size.
Resize After this selection you can resize the block document
window by dragging it with the mouse.
Pin badge
The texts, which are defined for the pins in the Pin data definition
window’s Badge field, are output to the block document.
Save as…
Opens the Save as window, which is used to save the block
document with the desired file name to the desired folder.
Color…
You can use the Color function to change the Print preview window
colors.
See section Colors.
2.7 Load
The File menu’s Load function is used to load the block being edited
into the PMD Server. Before loading, the block must be marked as
ready and its execution data (module, cycle, phase and priority) must
be defined by using the Blocks menu’s Header function. In addition,
the block must be saved by using the File menu’s Save function, to

enable the creation of a loadable software version.
The Load function displays the following message window.
If the block to be loaded is a type block, then loading can be

targeted either at all the modules in the department or at selected
modules only, due to the fact that type blocks do not have a specific
execution module. If the department’s system definitions have been
completed, the module names will be displayed in the Loading a
type block window.
The type block is loaded into all modules simultaneously when the
option To all modules is selected and loading activated by pressing
the OK push button.
If the type block is to be loaded into selected modules only, then
loading will take place one module at a time. Select the module from
the list field by clicking on the module name with the left-hand
mouse button. This will cause the name to settle in the To module
field. Then activate loading by pressing the OK push button.
The Cancel push button closes the window without loading the
block.
2.8 Load type

The File menu’s Load type function loads type blocks to the PMD
server. The function displays the Load types window.

All the type blocks contained in the list are loaded simultaneously to
the PMD server when the selection All blocks is made and the OK
push button pressed.
To load just some of the type blocks from the list to the PMD server,
load the blocks one by one. To select the block to be loaded, click on
its name with the left-hand mouse button on the list field. This will
cause the block name to be displayed in the Block field. To activate
loading, press the OK push button.
The Cancel push button closes the window without loading a block.
2.9 Monitor
The File menu’s Monitor function can only be used for blocks loaded
in the system. The function opens the Block Monitor where a block
loaded in the system can be tested. The block pins are updated
directly from the process modules. It is also possible to start the
monitor function from the Browse window by clicking on the block
name with the right-hand mouse button and selecting Monitor from
the menu opened.
Type block monitoring must be activated from a hierarchical block
which uses the type block.
The Block Monitor’s user instructions are provided at the end of this
document, see section Block Simulator / Block Monitor User Manual.
The Block Simulator and Block Monitor have a joint user manual,
due to the fact that their functions are almost identical. The Block
Simulator is used to test the blocks’ functions once they have been
completed. Simulation takes place at the design module and the pin
data items are either entered manually or they are produced by a
simple process model. Monitoring, in turn, is used to test system-
loaded blocks which means that their pin data items are updated by
the system’s process modules (PMD Controllers and XPR-A-based
process modules).

2.10 Delete
The File menu’s Delete command can be used to delete model blocks
and type blocks from the design module libraries. The function does
not delete type blocks from the system. The function displays the
following selection window.
To select the block to be deleted, either click on its name in the list
field (the name outputs to the Block field) or write the name in the
Block field.
Accept delete by pressing the OK push button. The Cancel push
button closes the window without deleting the block.

3 Edit
3.1 Edit menu description

The Edit menu’s functions can be used to copy a block from the Block
Builder workspace to the clipboard or a printer, and scroll the blocks
opened for editing.
3.2 Copy
The Edit menu’s Copy function can be used to copy data shown in
the Block Builder workspace to the clipboard or a printer.
The Copy / Clipboard function can be used to copy the data shown
in the Block Builder workspace to a printer. The function opens a
Print window, to activate printing and change printers if necessary.
The Copy / Printer function can be used to copy the data shown in
the Block Builder workspace to a printer. The function opens a Print
window, to activate printing and change printers if necessary.
The Setup push button opens the printer’s selection window.

The OK push button accepts printing and sends to the selected
printer.
The Cancel push button closes the window without printing.
3 - 22 • Edit Experion PKS

3.3 Back and Forward
The Edit menu’s Back and Forward function can be used to move
between blocks, after several blocks have been opened in the Block
Builder workspace.
The Back and Forward function can also be activated by the

toolbar push buttons.
Experion PKS Edit • 3 - 23

4 Blocks
4.1 Blocks menu description

The Blocks menu’s functions are used to handle hierarchical blocks,
type blocks and basic blocks.
4.2 Header
The Blocks menu’s Header function determines a block’s ID code and
execution data, a possible faceplate, and any of the faceplate-related
data items, in cases where a hierarchical block is being edited.
If the block being edited is a type block, then the function will
display the Header of Type Block window.
3 - 24 • Blocks Experion PKS

4.2.1 Hierarchical block Header
A block can be provided with three Ids for various user groups.
The Id 1 field automatically displays the name that was given to the
block when it was added to the block hierarchy. Id 1 is generally
used as the tag block’s ID in the faceplate.
The Id 2 and Id 3 fields can be defined as per project. Generally these
fields are used for electric tag IDs and instrument tag IDs.
If you want to show Id 2 or Id 3, instead of Id 1, as the tag block’s ID
in the faceplate, use the ID parameter in the Setting initial Face Plate
values window to define that.
Id 1, Id 2 and Id 3 are shown in the Info tab of the faceplate.
The Name field is used to enter the long name (maximum length is
30 characters) for the block. The letters A – Z and a - z, numbers 0 - 9
and the following characters: !, #, $, %, &, (, ), +, -, ˆ and _ are allowed
in name.
The name is shown in the title bar and in the Info tab of the faceplate.
The Name 2 field is used in Printa systems only to enter an
additional description with a maximum length of 30 characters.
The Description field is automatically checked (selected) after the
functional description has been written for the block in question by
using the Blocks menu’s Description function. A functional
description may have a maximum of 2000 characters.
The Model field automatically shows the name of the model block
used in the block. The model block’s name can be deleted from the
field, in cases where the block has been changed to such a degree that
it no longer sufficiently resembles the model block. Note! Model
blocks are not available in system release 710.
The Serial interface block field is not used in system release 710.
Experion PKS Blocks • 3 - 25

Face Plate is selected, for example, for those blocks that carry out
measurements, controls, or motor controls. The faceplate is used to
show block’s pin values on the user interface. To select a faceplate,
place the pointer on the faceplate name in the list field and click the
left-hand mouse button. The name of the selected faceplate outputs
into the Face Plate field. The faceplate name can also be written in the
field. For detailed faceplate descriptions, see section Defining
faceplates and standard pins for tag blocks.
The list below sets out the faceplate options, as per the control types,
contained in the Block Builder, arranged per the control type.
Type Faceplate name
Measurement Measure
Control Control
Motor M1Way, M2Way, M2Speed
Valve Valve, MValve
Control switch CSwitch
Device control Device
General logic Genlog
Binary Binary
Sequence Sequence
The Extension field is selected to edit a faceplate’s initial values. A

Setting initial Face Plate values window is only displayed after
accepting the Header window definitions by pressing the OK push
button and closing the Execution data window by pressing either the
OK or the Cancel push button. See section Setting initial Face Plate
values for hierarchical blocks.
The Tag field in the Header window must be selected for a
hierarchical block, to display the block ID as an identifier for the
alarms generated by this block. (Alarms are displayed in the Alarm
Summary display on the user interface.) If the Tag field is not
selected, then the block ID of the first block, (above the block in
question) which has the Tag field selected, will be displayed in the
Alarm summary display.
The Ready field is selected after the block definitions, such as
connections, have been completed. Once the block has been marked
as being ready, the editor will compile the block data in conjunction
with saving. The block must be marked as ready, before Program
Builder activation, before block testing with the Block Simulator, and
before loading blocks into the system.
The Associated Pages function can be used only for blocks having a
faceplate selected. The Associated Pages function is used to define
displays, faceplates, popups and other documents (text or picture
files), which you want to get out from the Associated pages tab in the
faceplate extensin of the block in question.
In addition, the first defined display can be called up on the Alarm
summary display through the alarms generated by this block. (Right-
click on a alarm row and select the Associated display from the menu
opened).

The Associated Pages push button opens the definition window:
You can define maximum of 10 associated pages (displays,

faceplates, popups and other documents) for a block having a
faceplate. (The order of the pages in the Associated Pages tab will be
the same as the order you greate the pages in this window.)
Note! The source directory of the displays and popups must be
C:\Program files\Honeywell\Experion PKS\Client\Abstract
The source directory of the documents (text and picture files) must
be the PMD Server's shared directory
C:\Program files\Honeywell\PMDC\Descriptions\[Department
name]
In the Name of page field write the name of the page to be associated
with the block being defined. The maximum length of the name is 30
characters. Note! When defining a document, the name must contain
the extension (for example .txt, .doc, .pdf, .ppt, .gif).
Select the Page type that is correct for the page.
In the Description field write the description for the page. This
description will be diplayed in the Associated Pages tab.
The maximum length of the description is 30 characters.
Note! Because the description is one of the texts that can be localized,
see document Localization for instructions of the allowed characters.
Use the Location X and Y fields to define the location, where the
faceplate, popup or document is output on the user interface screen
(origo is the top left corner of the display, unit pixel)
Note! The default coordinates X=0 and Y=0 will output the page so
that its top left corner has coordinates 200, 200.
Press the Add push button to move the page definition into the
Name: T:X,Y field.
The Change push button allows you to change the definition that is
selected in the Name: T:X,Y field.
The Delete push button removes the definition that is selected in the
Name: T:X,Y field.
Press the OK push button to save the definitions and to close the
window.
Press the Cancel push button to closes the window without saving
the definitions.

The Version, Author, Date and Control fields are updated
automatically.
Press the OK push button to accept the header definitions. This will
cause the Execution data window to be displayed on the screen.
The Cancel push button closes the Header window without
accepting the definitions made.
4.2.2 Hierarchical block Execution data (priority, phase and execution

cycle)
Defining priority, phase and execution cycle for blocks executed
by PMD Controllers and XPR-A processors.
The Module field is used to define the name of the module (PMD
Controller or XPR-A-based process module) where the block will be
loaded for execution. The lower field is used to define the name of
the back-up controller, if a redundant PMD Controller is used.
(The module names are defined by the PMD Builder’s System
definition. See document System definitions.)
Once the module is defined for a block in the higher hierarchy level
the name will output, as default, to blocks in the lower hierarchy
level.
The Cycle (s) list is used to select the execution cycle for the block.
The options range from 0.02 to 180 seconds. See the following
paragraph for permitted cycles as per high, medium and low
priority.
Note! An application with a maximum of 2000 hierarchical blocks
can be loaded into a redundant PMD Controller. A maximum of 100
blocks can have the execution cycle of 20 ms, the rest of the blocks
must have an execution cycle > = 100 ms.
Always consider carefully when selecting the fastest execution
cycles. For example, if the execution cycle of a priority’s fastest block
is reduced from 0.5 to 0.02 s, then the basic load of application
execution will be multiplied by 25.
The cycle should be the same for all blocks in a sequence.

The Priority options are high, medium and low.
The recommendation is to
• Use high priority for the execution of fast-cycle blocks
that contain simple calculations, e.g. logic.
Permitted cycles are 0,02, 0,06 ja 0,1 s.
• Use medium priority for execution of other, normal
blocks. Permitted cycles are >/= 0,1 s.
• Use low priority for the execution of blocks that permit
slower execution intervals, complex blocks, e.g. model
blocks and complicated neural networks.
Permitted cycles are >/= 0,5 s.
The various priorities are fully independent of each other. This
means that blocks with different priorities are independent of each
other with regard to the execution order. Each priority can be
regarded as if it were an independent module. Therefore, it is not
possible to interconnect blocks with different priorities through
wiring or flags. Connecting by name establishes normal data
communication between the connections which are affected by the
data transfer cycle. If the sub-block priority is different from the tag
block priority, then the sub-block must not have visible pins on an
upper level.
The priority must be the same for all blocks in a sequence.
The blocks with high priority definitions will be executed first. The
blocks with medium priority definitions will be executed if there is
nothing to execute with a high priority. The blocks of low priority
will be executed when there is nothing to be executed with high or
medium priority. A higher priority may interrupt the execution of
lower priorities at any time, even during block execution.
Each priority receives a basic cycle automatically.
The base cycle is the cycle that is used to read the process interface
data within the priority. The base cycle is either the execution cycle
of the fastest block within the priority, or faster, so that the cycles of
the blocks within the priority can be executed at multiples of the base
cycle. In other words, for example, if the priority contains blocks
whose execution cycle is 0.02 s, then the priority’s base cycle will be
0.02 s.
With high priority the slowest possible base cycle is 0.1 s.
Each priority handles its process interfaces at its own base cycle.
The high priority handles always the process interface data used by
the other modules.
Note! If the cycle of the fastest block within the priority is 0.06 s, then
both the cycle of the fastest block and the base cycle will be 0.05 s.

Cycle of the fastest block, s Base cycle, s
(within the priority)
0.02 0.02
0.06 -----> 0.05 0.05
0.1 0.1
0.2 0.1
0.5 0.5
1 1
2 1
5 5
10 10
30 30
60 60
180 180
The Phase field in the list is used to select the block phase, i.e. Fixed
or Auto.
Phasing enables module load stabilization as per priority.
In other words, the execution process corresponding to the priority
assigns the execution of the blocks executable at a lower cycle than
the base cycle to various phases, i.e. to the multiples of the base cycle.
The phase is selected automatically for blocks the phase definition of
which is Auto. The Auto-phased blocks’ sub-blocks with the phase
Fixed are executed in the same phase with the Auto-phased block.
This is a means to implement entities of several hierarchical blocks
within which the execution order of the blocks is precisely defined.
Going downwards in the block hierarchy onto a specific level, e.g.
the tag block level, the blocks’ phase is defined as Auto. Below this
level, the blocks’ phase will be defined as Fixed. This means that the
system will automatically phase the execution of control entities as
per priority. Within these entities, however, in the case of tag blocks,
for example, the blocks will always have the defined order of
execution.
If necessary you can implement an entity of several tag level blocks
and their sub-blocks with a fixed execution order by selecting Fixed
as the phase for the tag level blocks and Auto for the block above the
tag level. The maximum number of Fixed blocks under the biggest
Auto-phased block allowed is 96.
Note! In a sequece the STEPX block's phase must be defined as Auto
and the step blocks’ phase must be defined as Fixed.

Use the OK push button to accept the definitions made in the
Execution data window. Pressing the OK has the following effects
• The Header window and the Execution data window will
close, and the block will be ready to be loaded into the
process module, provided that the Extension field has not
been selected in the Header window.
• The Header window and the Execution data window will
close and the Setting initial Face Plate values window
displayed, provided that the Extension field has been
selected in the Header window.
The Cancel push button closes the Execution data window without
saving the definitions. The Setting initial Face Plate values window
will be displayed, provided that the Extension field has been selected
in the Header window.

4.2.3 Setting initial Face Plate values for hierarchical blocks
The Setting initial Face Plate values window is used to determine the
process area and the definable faceplate texts for the faceplate
selected in the Header window.
Use the Process area field to write the name of the process area for
which the faceplate is to be saved. The process areas are defined by
the PMD Builder’s System tool.
The Texts to be defined depend on the faceplate selected. For
example, the measurement upper and lower limit, measurement unit
and any connections to other tag blocks are defined for a
measurement faceplate. Naturally, a faceplate’s texts and limit values
must comply with the values of the tag block being defined.
The definable texts of each faceplate are described in detail in the
section Defining faceplates and standard pins for tag blocks.
When a Setting initial Face Plate values window opens on the screen,
the text’s first line is already active and is displayed in the edit field
in the lower section of the window. Write a desired text in the Text
field and press the OK push button to accept. This automatically
activates the next line.
Having defined all the texts necessary, close the window by pressing
the End push button. This also saves the definitions made.
Pressing the Cancel push button closes the window without saving.

4.2.4 Type block Header
If the block being edited is a type block, then the Blocks menu’s
Header function will display the Header of Type Block window.
The ID field automatically displays the block name and version

number. Here, the ID cannot be changed.
The Description box will automatically be marked as having been
selected if a functional description has been written for the block by
using the Blocks menu’s Description function. A functional
description has a maximum of 2000 characters.
The Pascal box is selected if the block is to be implemented in the
high-level language.
The Ready box is selected if the block definitions, such as
connections, are ready-made. If a block is to be made in the high-
level language, it must be marked as being ready. The reason is that
the Program Builder cannot be activated unless the block has been
marked as ready. Similarly, the block must be marked as ready
before it can be tested with the Block simulator, and before being
loaded into the system. A block is compiled at the saving stage, only
if it has been marked as ready.
Initial value of running state after PM/MM cold-start: Running is
the default option. However, if type block activation is not desired
after a cold-start for some reason, then the Stopped option must be
selected.
The Version, Author and Date fields are updated automatically.
Press OK to accept the Header data.
The Cancel push button closes the window without saving the
definitions made.

4.3 Description
The Blocks menu’s Description function displays a window that can
be used to write a function description for the block. The description
may have a maximum length of 2000 characters. To save the
description written, press the Close push button located at the right-
hand end of the title bar .
4.4 Insert
The Blocks menu’s Insert function is used to add hierarchical blocks
and basic blocks to the block hierarchy. This function is also used to
add step blocks into the STEPX sequence block. The function opens
the Insert blocks selection window.
Tip! You can open the Insert blocks selection window also by
pressing the Insert key on the keyboard.
4.4.1 Inserting hierarchical blocks and basic blocks
To insert a hierarchical block, write the name, which the block is to

receive, in the entry field in the window. Name must be unique
inside the department. Hierarchical block names, with the exception
of sequence blocks, have a maximum length of 40 characters. The
names of sequences have a maximum length of 38 characters. If
needed, the maximum length of block names can be defined during
server installation separately for each department.
Note! The maximum length of tag block names is in practice 20

characters, because longer names do not fit in the faceplates. The
faceplate name outputs in two rows, each of which has a maximum
length of 10 characters.
Note also! The name of a block which will have a faceplate must
have at least one alpha character.
Permissible characters are: A - Z, a - z, 0 - 9, !,#, %, &, (, ), -, $, and _ .

Name cannot contain any of the following characters: Space, Tab,
Period (.), Comma (,), Forward slash (/), Back slash (\), Less than (<),
Greater than (>), Single quote ('), Double quote ("), Asterisk (*),
Question mark (?), Vertical bar (|), Colon (:) and Semi-colon (;).
Names are not case-sensitive, e.g. STA015 and sta015 are the same.
The Block Builder will change lower case letters into upper case.
Accept the block insertion by pressing the OK push button, which

will cause the block to be displayed in the first vacant block site
available.
To insert a basic block, select the desired block from the list shown
in the Insert a block window by clicking on the block name. The list
contains all the basic blocks available. The list can be scrolled by
means of the scroll bar. You can also write the block name into the
entry field.
Accept the block insertion by pressing the OK push button which
available in the Block Builder workspace.
Having inserted the desired blocks, close the Insert a block window
by pressing the Cancel push button.
Note! For a single tag block, you may define alarm blocks only either
in its tag-level or in a single hierarchical sub-block that has not been
marked as a tag-level block in its header definition.
Tip! It is possible and an easy way to add basic blocks by double-

clicking them in the Browse window. See Browse window / Basic
tab.
Note! A type block cannot receive all the basic blocks, e.g. logic
packages blocks, alarm blocks or send blocks. If an attempt is made
to insert an illegal block in a type block, the Block Builder will issue
an error message.
4.4.2 Inserting steps into a STEPX sequence block

When editing a STEPX sequence block, the Insert function will
display the Insert a step window.
Use the entry field to write the number of the step being inserted.
Numbers 1-253 can be used. Accept the number by pressing the OK
push button. The number outputs to the step list of the STEPX block
in the Block Builder workspace. A total of 40 steps can be inserted in
a STEPX sequence block, including the BEGIN and END blocks.
Having inserted the desired steps, close the Insert a step window by
pressing the Cancel push button.

4.5 Insert type
The Blocks menu’s Insert type function is used to insert a type block
in the block being edited. The block to be inserted must have been
saved in the type block directory of the project in question. The
function displays the following selection window.
To insert a type block, select the desired block from the list shown in
the Insert a type block window by clicking on the block name. The
list can be scrolled by means of the scroll bar arrows and the square.
Accept the block insertion by pressing the OK push button which
available in the Block Builder workspace.
You can also write the block name into the entry field.
Having inserted the desired blocks, close the Insert a type block
window by pressing the Cancel push button.
Tip! It is possible and an easy way to add type blocks by double-
clicking them in the Browse window. See Browse window / Type
tab.
4.6 Delete
The Blocks menu’s Delete function deletes blocks from the block
being edited as follows:
• Place the pointer on the name of the block to be deleted
and click the left-hand mouse button. This changes the
block's color indicating that it is active.
• Select the Delete function.
In conjunction with deletion, all connections made to the block will
also be lost. In addition, any blocks residing below the block being
deleted will also be deleted. Should several blocks be active
simultaneously, the Delete function will delete the most recently
activated block first.
When editing a STEPX sequence block, the Delete function deletes
the step block selected from the step list.
The block will disappear from the design module in conjunction with
saving.
If the block deleted has been loaded into the system, the deletion
must be done by using the Blocks menu's Delete from system
function. See section Delete from system.
4.7 Rename
The Blocks menu’s Rename function is used to change block names
as follows:
Place the pointer on the block to be renamed and click the left-hand
mouse button to activate the block.
Select the Rename function. A definition window appears.
Enter the new name and accept it by pressing the OK push button.
(Pressing the Cancel push button closes the window without
renaming the block.)
The program outputs the following question window:
Answer Yes to rename the block and to change the new block name
also into all the Connect with name connections.
Note! Depending on the size of the application, it may take quite a
long time when the program goes through the application and
updates the connections.
Answer No just to rename the block.
4.8 Export
The Blocks menu’s Export function can be used to copy a desired
portion of the application to a diskette and transfer it to the block
hierarchy of another design module. The copied application portion
is combined with the block hierarchy of the other design module by
using the Import function.
To copy a portion of the application, take the following steps:
In the Block Builder workspace place the pointer on the name of the
block to be copied and click the left-hand mouse button to activate
the block. All blocks residing below the selected block in the block
hierarchy will also be exported.
Select the Export function. The definition window outputs.

If you select Default in the Select license field, the application is
copied using the license of the department in question.The possible
other licenses are library licenses used in application library
development. Those licences are usually not needed in normal
projects.
Write in the Export Block(s) to folder field the folder name to which
the blocks will be copied, or use the Browse button to browse the
location.
If the block is Pascal type, select Block pascal source to copy also the
Pascal codes.
Select OK to to copy the blocks.
4.9 Import
The Blocks menu’s Import function combines with the block
hierarchy those application portions that have been copied by the
Export function to diskettes. The parts to be combined must not
contain blocks with identical names.
Note! A license is needed to import blocks from another department.

If the required license has not been installed, a notification window
opens and the import function will not proceed.
Note also! If you want to import blocks from an older system than
R710, the blocks have to be converted to XML files before they are
merged. See 14 Converting Block Builder Applications to XML files.
Use the Import function as follows:

Open into the Block Builder workspace the block to which you want
to import the new part and select Blocks/ Import, thus causing a
Import definition window to be displayed.

In the Import Block(s) from folder field, type the folder in which the
blocks to be merged are located. Alternatively, use the Browse
button to search the desired folder.
Select the block name in the Select highest block field. The blocks
that are under the block in the block hierarchy will also be combined.
Select the No Change field if the block IDs are not to be changed in
conjunction with the Import function.
Select the Change characters option if only some of the characters are
to be changed. Changing will be possible if the blocks being
combined have been named in a suitable fashion, i.e. if the characters
to be changed are the same in the ID of the highest block and sub-
blocks.
Select the Change string option if the whole character string is to be
changed. The function changes all the characters which are used in
the ID of the highest block. If the IDs of the sub-blocks are longer
than the ID of the highest block, the extra characters are not changed
or deleted. For example, if the character A is used as an identifier of
alarm sub-blocks, it will remain.
This option is mainly used when merging model tag blocks or
application portions within the project specific application.
Select OK to merge the blocks.

Merging the blocks can take some time, depending on the amount of
the blocks to be merged.
Note! Save all blocks before loading them to system.
4.10 Search
You can search with the Blocks/Search function, which hierarchical

blocks use the certain type block. When you enter the type block
name in the Name field, a list opens showing the locations where the
type block is used.
4.11 Delete from system

The Blocks menu’s Delete from system function is used to delete a
single hierarchical block or type block from the PMD server. This
function only deletes the selected block from the system, and none of
the blocks contained below it in the block hierarchy.
The type block is automatically deleted from its execution module.
Open the block to be deleted in the Block Builder workspace and
select the Delete from system function. This will output the selection
window.
Select the block type being deleted and activate function by pressing
the OK push button.
Pressing the Cancel push button closes the window without deleting
the block.

5 Pins
5.1 Pins menu description

The Pins menu functions are used to define the pins through which
all the messages are relayed to and from the block in question.
5.2 Insert
The Pins menu’s Insert function is used to define all the pins
required by a block.
5.2.1 Defining pins for a hierarchical block

Note! If the definable block, such as measurement, control, motor or
valve tag block has been provided with a faceplate by the Blocks
menu’s Header function, then pins with certain names must be
defined for the block. These pins automatically relay the data from
the tag block to the faceplate. For detailed instructions for faceplates
and the pins they require, see the end of this document, section
Defining faceplates and standard pins for tag blocks.
When defining a hierarchical block, the Pins menu’s Insert function

displays the following window.
Experion PKS Pins • 3 - 41

Use the Name field to enter the pin name. The maximum pin name
length is 3 characters. Permissible as characters are letters A–Z,
numbers 0-9 and the _ character.
The name may be written with lower case or upper case letters. Once
the pin definition is accepted, the Block Builder will generate the
name in compliance with the pin type presentation form. (See
explanation for Type.)
The Description field can be used to write a pin description with a
maximum length of 30 characters.
This description is printed in the block document and is shown next
to the pin in the Block Builder workspace by pressing the toolbar’s
Pin description push button .
The Badge field can be used to write an additional 10-character
description which is printed in the documentation if the pin is an I/O
pin.
Select Input to define an input pin. Input pins are displayed on the
left-hand side of the Block Builder workspace. Correspondingly,
select Output to define an output pin, displayed on the right-hand
side of the Block Builder workspace.
Select Vector if the pin is to relay data in a vector form. The Block
Builder will request the vector length once the pin definition is
accepted. Vectors can be used by the blocks executed in high-level
language, and by those blocks which use vector blocks that are
included in the basic block selection.
3 - 42 • Pins Experion PKS

Type:
Signal Integer 0...255.
Real Real number. Absolute value 3.4128237E38 and the lowest
absolute value, other than 0, is 3.4128237E-38. Accuracy 7
digits.
Word Integer 0...65535.
LongReal Value range approx. (+/-)1.113E-308, 0 and (+/-)1.113E308.
Accuracy 16 digits.
Char Character
Integer Integer with a sign -32768...32767. Two bytes.
LongInt Integer with a sign -2147483648...2147483647. Four bytes.
The pins will be displayed in the Block Builder workspace in

accordance with the selected type as follows:
Type Presentation form Example
Signal All letters in lower case Swi
Real All letters in upper case SET
Others Upper case initial letter, others in Cn1 (Word)
lower case Rec (Vector)
If an input pin is selected and the Type is Real, then the Block Builder
will turn the pin into a variable which is saved automatically and
will request the initial value once the pin definition is accepted. It is
not advisable to make automatically saved variables of those pins
which receive their values from another module (the external
setpoint value of a cascade control, RSE, for example). This is due to
the fact that the value of an automatically saved variable is saved in
the PMD server whenever the value receives a change from another
module or the Block monitor. The pin will not become one which is
saved automatically, if the window that requests the variable’s initial
value is closed by pressing the Cancel push button or the Esc key on
the keyboard. The value of a non-automatically-saved variable is
saved in the PMD server via the Block monitor’s Block menu’s Save
variables function.
Defining pins for various purposes:
A pin is defined as a public pin if the data contained in it is to be
connected to a faceplate and displays or the data is to be used in
other blocks. The pin will not be visible on a higher hierarchical level
and cannot, therefore, be wired on this level. All pins connected to
faceplates are public.
A pin is defined as a pin visible on a higher level if it is to be
displayed on a higher hierarchical level where it may also be
connected to other blocks through wiring or flags. A pin that is
visible on a higher level cannot be connected to a faceplate or
displays.
The type of an analog I/O pin will automatically be Word once the
pin definitions are accepted. Correspondingly, the type of a binary
I/O pin will automatically be Signal. I/O pins are used to connect
blocks to process interfaces. The I/O pin names are attached to
process interface device I/O channels by the PMD Builder’s System
tool. To indicate an I/O pin, a thick line is displayed at the pin’s left-
hand side in the Block Builder workspace. I/O pins cannot be
connected to faceplates or displays.
The rng pin and motor run data are examples of pins which are both
public and I/O pins. Here, the pin data can be connected to both the
process interface and the faceplate.
The RSE pin and cascade controls’ external setpoint values are
examples of public pins visible on a higher level. Such a pin can be
connected between two blocks on a higher hierarchical level and
shown in the faceplate as well.
Register I/O pins connect a block to a process interface provided
with a register interface. The register I/O pin type will be
determined automatically, provided that the definition has been
made by the PMD Builder. If the pin definition does not exist, an
error message will be displayed. If the pin is accepted as being ready
after the error message has been acknowledged, the pin type will be
Signal. However, this type does not necessarily comply with future
I/O definitions and the connection will not function. The External
option will also be selected automatically once the Register I/O pin
definition is accepted.
Select the Creates an interlock option if the data relayed by the pin
causes an interlock or a control disable state in the block being
defined, and if you want to show the cause of the interlock/disable
in the block’s faceplate extension on the user interface.
A data item that interlocks a motor in the halt state is an example.
The following definition window will output after you have selected
the option Creates an interlock and pressed the OK push button in
the Pin data window.
The Description field is used to write a description of the interlock or

control disable. This information will be shown in the faceplate
extension. It is recommended to write the description in English and,
if required, localize the text by using the localization tools of the
system. See document Localization.
The TagName field is used to write the name of the tag block that
issues the interlock or control disable. This information will be
shown in the faceplate extension.

Select the Interlock inverted option if the interlock is valid when the
data value is zero.
The Definition options are only significant when making device
control or general logic tag blocks.
• When defining a device control tag block, the Definition
options are used to specify in detail the causes of an
interlock. Causes are shown in the faceplate. For a
description of the Device control faceplate, see section
Device control (Device).
If you are using the device control tag block to control a
hydraulic directional valve, see a separate Hydraulic and
Pneumatic Control Toolbox User Manual.
• When defining a general logic tag block, the Definition
options are used to define the faceplate’s title(s), under
which the data of the Description and TagName fields
will be displayed. For a description of the General logic
faceplate, see section General logic (Genlog).
Select the Target of interlock option if the pin data creates an
interlock or a control disable state for one or more blocks, and a
description of the interlock targets should be visible in the block’s
faceplate extension.
the option Target of interlock and pressed the OK push button in the
Pin data window.
Use the Description and Tag name fields to write, one by one, the
description and block name of the tag blocks where the pin will
cause an interlock or a control disable state.
It is recommended to write the description in English and, if
required, localize the text by using the localization tools of the
Accept the entered description and block name by pressing the OK
push button which causes them to be displayed in the list field.
The Add push button adds an empty line above the active line.
The Delete push button deletes the active line.
The Save push button saves the definitions accepted in the list field
and closes the window.
definitions made.
Select the Interlock inverted option if the interlock is to be valid
when the data value is zero.
The Block able to write to its input option can only be selected for
the pins of a high-level language block or a sequence step, such as
the Wait time counter (Wtc) and the SWAIT control (Wco).
(See also document Basic blocks, section SWAIT.)
The Pin to be copied in testing field can be used to write, for the
input pin, the name of the output pin whose value is to be relayed to
the input pin. The Inverted option can be selected for a pin of the
signal type.
Trend record option is not used in the Experion PKS with PMD
Controller automation system.
The Activate task pin must always be a public WORD-type pin.
5.2.2 Defining pins for a sequence step block

When defining a sequence steps (i.e. steps inside a STEPX sequence
block), the Pins menu’s Insert function displays the following
window.
Note! When defining the pins of a sequence step, the conditions-of-

progress option is displayed instead of the trend record option in the
Pin data window of a hierarchical block. All other options are the
same. (See section Defining pins for a hierarchical block.) Therefore
only conditions-of-progress option is explained in this section.
Condition of progress means that sequence execution will continue

only when the step’s progress conditions are valid. Each step can
have a maximum of ten progress condition pins.
the option conditions-of-progress and pressed the OK push button in
the Pin data window.

The Connection and Transmission Cycle fields are used to define the
progress condition source.
The Explanation field is used to enter the condition text, which must
be valid before the sequence can proceed. The explanation has a
maximum length of 10 characters and it is shown in the sequence
faceplate as the progress condition explanation.
It is recommended to write the explanation in English and, if
required, localize it by using the localization tools of the system. See
document Localization.
The Condition name can be selected to be either the block name that
sends data to the pin or the pin explanation defined for the pin in the
Pin data window.
Select the Condition inverse option, if the condition is to be valid
when the data value is zero.
The Condition can be by-passed option is selected if the condition
can be by-passed via the user interface.
Note! If you select the can be by-passed option, you must also define
The by-passing must be deleted property. The alternatives are:
At step re-execution The condition by-pass is removed automatically

when the sequence proceeds to the step in question.
At sequence startup The condition by-pass is removed automatically at
sequence startup.
Via the keyboard The user must by-pass the condition by clicking the
Note! If you don't select any condition line and acknowledging the command by
of the by-passing must be pressing OK on the message window.
deleted options, the system
selects this option as default.
Press the OK push button to accept the pin’s progress condition

definition.
The Cancel push button closes the window without saving the pin
definition.
The Get push button shows the progress condition, that was saved as
the default condition.
The Save push button saves the complete progress condition
definition as the default condition.
5.2.3 Defining pins for a type block
When defining a type block, the Pins menu’s Insert function displays
the following window.
The Name, Input or Output, Vector and Description options are

defined in the same way as the pins of a hierarchical block.
Type:
Signal Integer 0...255.
Real Real number. The highest absolute value is 3.4128237E38 and
the lowest absolute value, other than 0, is 3.4128237E-38.
Accuracy 7 digits.
Word Integer 0...65535.
LongReal Value range approx. (+/-)1.113E-308, 0 and (+/-)1.113E308.
Accuracy 16 digits.
Char Character
Record Not supported in the system. The records must be described as
byte vectors.
StringVector A table formed of fixed-length character strings. The Block
Builder requests the length and number of character strings.
Integer Integer with a sign -32768...32767. Two bytes.
LongInt Integer with a sign -2147483648...2147483647. Four bytes.
LongWord Integer without a sign 0...4294967295. Four bytes.
It is also possible to define several types for a high-level block pin at

the same time. This means that the pin becomes a so-called type
group pin. To be able to process a type group pin in the high-level
language, it is necessary to select, for the pin, the Address and type
of parameter are passed option.
The options Binary I/O, analog I/O and Visible on the higher level
have the same effects as the pins defined for a hierarchical block.
Use the Space reserving pin to connect a constant value that
indicates the number of elements in the reserved memory space, or
another space reserving pin (e.g. the PIDEL block’s LEN pin).
The Limitation options are used to determine whether a constant
value or a variable, or both, may be connected to the pin in question.

The Hidden option must be reserved for connection to the hidden
pin of a basic block residing within a type block. The pins defined as
hidden pins will not be seen in a hierarchical block that uses the type
block. Hidden pins are used to save the data that is retained beyond
the execution cycle (the previous value of an input signal, for
example).
The Preserved output must be selected when the output pin of a
basic block or type block has to be retained beyond the execution
cycle (e.g. when the output is read before writing, or if the output is
not updated during each execution cycle) and when there is an
additional requirement for the pin to be visible. A type block’s
internal pin data resides in the execution process stack and is,
therefore, not preserved beyond the execution cycle.
The Address and type of parameter are passed option must be
selected if the block must be able to write to its own input. The
option must also be selected for the type group pins. A type group
pin is a pin for which more than one type have been selected. The pin
type is only attached at the editing stage. For this purpose, a high-
level language block may also receive the pin type data item.
The pins that are selected via the Shown when asked option will pile
up in the user block, thus reducing the space available to the block.
Select the No double copying option if the pin value is not to be
copied from one processor to another when using a process module
provided with processor redundancy.
5.3 Delete
The Pins menu’s Delete function is used to delete an inserted pin
from a block as follows:
1. Place the pointer on the pin to be deleted, and click the
left-hand mouse button to activate the pin.
2. Select the Delete function, thus causing the pin to be
deleted.

5.4 Change
The Pins menu’s Change function can be used to change pin data as
follows:
1. Place the pointer on the pin whose data is to be changed,
and click the left-hand mouse button to activate the pin.
2. Select the Change function. This displays the Pin data
window on the screen.
(The window can also be opened by directly double-
clicking on the pin with the left-hand mouse button.)
3. Change the pin definitions as required and save the
changes by pressing the OK push button.
Note! It is not possible to change all data items of a connected pin or

a pin defined to be visible on the higher level. The Block Builder will
issue an error message if the change in question is not permissible.
Acknowledge the message window by pressing the OK push button.

6 Connections
6.1 Connections menu description

The Connections menu’s functions are used to link block pins to one
another. These connections are made either by linking, with flags, or
with names. A connection can be inverted. A constant value or a
variable can be defined instead of a pin connection.
6.2 Link
The Connections menu’s Link function is used to connect pins to one
another by drawing a wire between them. This function can also be
activated through the Link push button on the toolbar. The
function will remain valid for as long as it is reselected, or another
function selected.
To link pins, take the following steps:
1. Activate the Link function, whereupon the pointer turns
into an arrow.
2. Place the pointer on the pin to be linked and click the left-
hand mouse button. This will activate the pin.
3. Place the pointer on the pin to be connected to the other
end of the wire and click the left-hand mouse button. This
Experion PKS Connections • 3 - 51

will activate the pin and generate a wire between the two
pins.
Links between signal-type pins are displayed as dashed lines and
links between other type pins with uniform lines. Links between
vector pins are indicated by thick uniform lines. The default color for
links that connect I/O pins is blue. If necessary, the link colors may
be changed by using the Options menu’s Color function. See Colors.
6.3 Connect with flags

The Connections menu’s Connect with flags function connects two
pins to one another by displaying a flag adjacent to both pins
provided with the same character for identification. It is advisable to
use the Connect with flags function, if there is a great number of pin-
to-pin connections and if the connecting by links makes the block
diagram confused.
This function can also be activated through the Connect with
flags push button on the toolbar. The function will remain valid until
it is reselected or another function selected.
To connect pins with flags, take the following steps:

1. Activate the Connect with flags function, whereupon
the pointer turns into an arrow.
2. Place the pointer on the pin to be linked and click the
left-hand mouse button. This will activate the pin.
3. Place the pointer on the pin to be connected with and
click the left-hand mouse button. This will activate the
pin and generate flags next to both pins.
3 - 52 • Connections Experion PKS

6.4 Connect with name
The Connections menu’s Connect with name function is used to
connect a pin (except input and output pins) of the block being
edited with a pin that resides in the same process module, in another
process module, or even in another department’s process module.
This function can also be activated through the Connect with
name push button on the toolbar.
Note ! A type block cannot have connections with name.

Note also! If the Connect with name function is used to write to a pin
of another module, then the pin in question cannot be read back to
the module which used for the writing. This is due to the fact that, in
this data transfer type, reading and writing are targeted at the same
data number which may cause data items to be overwritten.
Activate the pin to which the connection is to be made by clicking the

left-hand mouse button. Activate the Connection with name
function. This will display the Data of other block definition window.
As a default, the Department field has the department of the block

being edited. If the pin to be connected is in another department,
then change the department name.
Use the Block field to write the name of the block to whose pin the
connection will be made.
Use the Name of data field to define the pin, which can be
• A pin of a basic block or a type block that is inside a
hierarchical block.
• A hierarchical block's public input or output pin,
for example:
Department: XPRDEP
Block: LIC112
Name of data: MES
• A hierarchical block's pin that has been named by the
Name function. For example, a pin named as CONN1:
Department: XPRDEP
Block: LIC112
Name of data CONN1
Use from the Transmission Cycle field to select the desired

transmission cycle in cases where
• The connectable pin resides in the same process module
but in a block that has a different priority than the block
being edited.
• The connectable pin resides in another process module.
If the connectable pin resides in the same process module in a block
with the same priority as the block being edited, then the data will be
transmitted between the pins at the execution cycle of the block being
edited.
Select the Creates an interlock option if the pin is to receive a data
item that creates an interlock in the block being edited. Use the
Description field to write the interlock cause and use the Tag block
field to write the name of the block where the interlock data come
from. Description and block name are shown in the tag block’s
Note! It is recommended to write the description in English and, if
required, localize it by using the localization tools of the system. See
document Localization.
Select the Trigger by application option if you don't want to transfer
the data cyclically, but on an event-driven basis by using some data
transmission block, for example TRIGG basic block.
Note! The Data storage connection option is not be used within the
Experion PKS with PMD Controller automation system. Data storage
connections are defined by using PMD server functions.
A connection with name is indicated by an arrow next to the pin.
The arrow will turn red, if the defined block or pin can not be found
from the defined department. The Block Builder's Information
window will show the detailed error description.
6.5 Delete
The Connections menu’s Delete function is used to delete
connections as follows:

1. Place the pointer on the pin whose connection is to be
deleted and click the left-hand mouse button to
activate the pin.
2. Activate the Delete function.
Note! A pin name given by the Name function must be deleted by

using the Name function.
6.6 Show connections

The Connections menu’s Show connections function shows in the
Block Builder workspace the connections made with the Connect
with name function.
This function can also be activated through the Show connections

push button on the toolbar.
6.7 Invert
The Connections menu’s Invert function inverts the logic state of the
connection. This function can also be activated through the Invert
push button on the toolbar.
To invert a connection, take the following steps:
1. Place the pointer on the pin which you want to invert and
click the left-hand mouse button to activate the pin.
2. Activate the Invert function thus causing the small circle
to be displayed within the pin, to indicate inversion.
Real numbers can also be inverted. Inverting a real number changes
the sign in front of it.
Hierarchical block's input and output pins cannot be inverted.

6.8 Constant
The Connections menu’s Constant function is used to connect a
constant value to a pin.
The Constant definition window can be opened in two ways:
1. Place the pointer on the pin to which the constant is to be
connected and click the left-hand mouse button to activate
the pin.
Select the Connections menu's Constant function or
click the Constant push button on the toolbar.
2. Depress the Shift key and double-click on the pin to be
defined with the left-hand mouse button.
Define the constant value and save it by pressing the OK push

button. The Cancel push button closes the window without saving.
The pins of certain blocks (e.g. Move basic block) can receive several
types of data. To connect a constant value to such a pin, the Block
Builder displays a window that is used to define the data type. If the
pin is a vector, then the vector length must also be entered.

6.9 Variable
The Connection menu’s Variable function can be used to connect a
variable value to a pin.
Note!. A type block cannot have variables.
The Variable definition window can be opened in two ways:

1. Place the pointer on the pin to which the variable is to be
connected and click the left-hand mouse button to activate
the pin.
Select the Connections menu's Variable function or
click the Variable push button on the toolbar.
2. Double-click on the pin to be defined with the left-hand
mouse button.
Define the variable value and save it by pressing the OK push

button. The Cancel push button closes the window without saving.
The variable value can be changed via the Block Monitor.
The pins of certain blocks (e.g. Move) can receive several types of
data. To connect a constant value to such a pin, the Block Builder
displays a window that is used to define the data type. If the pin is a
vector, then the vector length must also be entered.

6.10 Show values
Activation of the Connections menu’s Show values function displays
the values of the pins defined as constants or variables. This function
can also be activated through the Show values push button on
the toolbar. The pin values will be visible until the function is
deactivated by reselecting it. The function is not active if an asterisk
(*) is displayed at the pins defined as constants and variables,
indicating that a constant or variable has been connected to them.
6.11 Name
The Connections menu’s Name function is used to make a
hierarchical block’s pin, that is not a input or output pin, a public
pin. This function can also be activated through the Name push
button on the toolbar.
In other words, when there is a need to make a direct connection
from another hierarchical block to a pin of a basic block, type block
or inner hierarchical block within the block being edited, the pin data
will be named. This means that the pin will become a public pin and
its data can be directly connected (by using the given name) to a
display or other block's pin, for example.
In the Block Builder workspace a named pin is indicated by

an arrow.
To name a pin data, take the following steps:
1. Place the pointer on the pin which data is to be named
and click the left-hand mouse button to activate the pin.
2. Activate the Name function. A window will be displayed,
to name the pin.
3. Write the name for pin data and save it by pressing the
OK push button. The Cancel push button closes the
window without saving.
The Target of interlock option can only be selected for a Signal type
output pin. The Target of interlock option is selected if the pin data
creates an interlock or a control disable state for one or more blocks,
and a description of the interlock targets should be visible in the
block’s faceplate extension.

the option Target of interlock and pressed the OK push button.
Use the Description and Tag name fields to write, one by one, the
description and block name of the tag blocks where the pin will
cause an interlock or a control disable state.
It is recommended to write the description in English and, if
required, localize the text by using the localization tools of the
Accept the entered description and block name by pressing the OK
push button which causes them to be displayed in the list field.
The Add push button adds an empty line above the active line.
The Delete push button deletes the active line.
The Save push button saves the definitions accepted in the list field
and closes the window.
definitions made.
Select the Interlock inverted option if the interlock is to be valid
when the pin data value is zero.
6.11.1 Deleting the pin data name given by the Name function
To delete a name given by the Name function, take the following
steps:
1. Place the pointer on the pin whose naming is to be deleted
and double-click the left-hand mouse button. The pin will
be activated and the definition window (that was also
used to give the name) will be displayed.
2. Click on the Delete push button to delete the naming.
6.12 Search
The Connections menu’s Search command searches the data of the
pins connected to the selected pin. The selected pin can be a input or
output pin or a named pin. If a pin has not been selected, then the
Search function will display a window that requests the pin whose
connections are to be searched.

In the case of an I/O pin, it is possible to choose whether to search
the process interface data (process module name, card slot, card type
and channel) or connections to other blocks.
All the connections of the block being edited can be searched by
selecting the Connections of all pins option.
6.13 Pin I/O and Pin description push buttons
6.13.1 Pin I/O

The toolbar’s Pin I/O push button shows the interface data,
which is defined for a pin in the PMD Builder’s System tool.
The following figures show examples of I/O data visible in the Block
Builder
XPR-A
I/O card in XPR-A based process module's own rack
I/O extension rack connected to XPR-A based process module

PMD Controller
PMD Controller and I/O extension rack (IOC)
PMD Controller and PROFIBUS fieldbus
PMD Controller and PROFIBUS fieldbus of the I/OWeb Link
PMD Controller and CANopen fieldbus of the I/OWeb Link
6.13.2 Pin description

The toolbar’s Pin description push button displays the texts
written in the Pin data window’s Description field at the pin
definition stage.

7 Execution
7.1 Execution menu description

The Execution menu’s functions are used to show and change the
properties of blocks displayed in the Block Builder workspace.
7.2 Show
The Execution menu’s Show function shows the block execution
order, execution modules, phases, execution cycles, faceplate names,
model blocks, file names, block symbols and pin connection numbers
of the blocks displayed in the Block Builder workspace.
The Show / Orders function shows the blocks’ execution order. This
order can be changed by using the Execution menu’s Change /
Order function.
The Show / Modules function shows the blocks' execution modules.
The Show / Phases function shows the phases defined for the blocks.
A block phase is defined in the header definition’s Execution data
window.
The Show / Cycles function shows the execution cycles defined for
the blocks. A block execution cycle is defined in the header
definition’s Execution data window.
The Show / Priority function shows the priorities defined for the
blocks. A block priority is defined in the header definition’s
Execution data window.
3 - 62 • Execution Experion PKS

The Show / Face Plates function shows the faceplate names defined
for the blocks. A block that executes e.g. a measurement or valve
control has a faceplate selected in the header definition.
The Show / Areas function shows the process areas to which the
blocks have been connected. A tag block is always connected to a
process area in the Setting initial Face Plate values definition
window.
The Show / Bitmaps function shows the block drawing symbols.
Separate symbols are available for hierarchical blocks, high-level
language blocks, motors, valves, etc.
The Show / Connection numbers function shows the connections
between the block pins by means of numbers.
7.3 Change
The Execution menu’s Change function changes the execution order,
department or the alarm output mode of the blocks displayed in the
Block Builder workspace. In addition, the Change basic block
function can be used to change certain basic blocks in conjunction
with system updates, and replace existing faceplates by new ones in
conjunction with faceplate updates.
7.3.1 Change / Order

The Change / Order function can be used to change the execution
order for the blocks residing in the Block Builder workspace. The
execution order must be checked and defined for those blocks whose
phase is Fixed, and which have identical priorities. See section
Hierarchical block Execution data (priority, phase and execution
cycle).
If the blocks’ valid execution order numbers have been called up via
the Execution menu’s Show / Order function, then they will
disappear once the Change Order function is selected.
The Change / Order function outputs the Order of Execution
window.
Define a new execution order by selecting the blocks in accordance
with the new execution order. To select the blocks, click on their
names with the left-hand mouse button. The new execution order
number will be displayed next to each block after selection.
To accept the new execution order, press the OK push button. The
Cancel push button closes the window without changing the
execution order.
If an attempt is made to accept the new execution order before all the
blocks have received a number, an error message will be displayed:
Experion PKS Execution • 3 - 63

Provide all the blocks with an execution number. Acknowledge the
message window by pressing the OK push button.
7.3.2 Change / Modules

The Change / Modules function can be used to change the execution
modules defined for the blocks.
Use the Old Module field to enter the name of the module being
changed.
Write the new module’s name in the New Module 1 field.
Use the Beginning block field to define the hierarchical block below
which the module is to be changed. This will also change the module
of the beginning block.
Press the OK push button to activate the change. The Cancel push
button closes the window without changing the window.
Note! Following a change of modules, the STEPX sequence blocks

that have received a new module definition must be reloaded and
the high-level language blocks compiled and saved again by the
Program Builder.
7.3.3 Change / Phases

The Change / Phases function can be used to change the phases
defined for the blocks.

Use the Top block field to define the hierarchical block below which
the phases are to be changed. This will also change the phase of the
top block.
7.3.4 Change / Cycles

The Change / Cycles function can be used to change the cycles
the cycles are to be changed. This will also change the cycle of the top
block.
7.3.5 Change / Priority

The Change / Priority function can be used to change the priorities
the priorities are to be changed. This will also change the priority of
the top block.

7.3.6 Change / Basic blocks
The Change / Basic blocks function is only used in conjunction with
system updates. The function is used to change either the alarm
blocks or the SEND and SENDX blocks.
which the blocks are to be updated.
The Old TPA alarm blocks option changes ALARMS blocks to
ALARSD blocks, ALARM blocks to ALARMD blocks, ALRMCD
blocks to ALARCD blocks, CTRCHA blocks to CTRCHD blocks,
MVCHA blocks to MVCHD blocks, and ALARMV blocks to
ALARVD blocks.
The Old TPA SEND blocks option updates the contents of all SEND
and SENDX blocks.
The SEND blocks TPA -> PMD option updates the contents of all
SEND blocks compatible with Experion PKS with PMD Controller
automation system.
The SEND blocks PMD -> TPA option updates the contents of all
SEND blocks compatible with TotalPlant Alcont and Printa
automation systems.
To activate the selected change, press the OK push button. The
Cancel push button closes the window without making the changes.

7.3.7 Change / Face Plate names
The Change / Face Plate names function is only used in conjunction
with faceplate updates. A precondition for using this function is that
the new and old faceplates are fully compatible since only the
faceplate name will be changed as a result of the update.
which the blocks are to be updated.
Use the Old Face Plate field to write the name of the faceplate to be
changed.
The New Old Face Plate field is used to write the name of the new
faceplate.
To activate the change, press the OK push button. The Cancel push
button closes the window without making the change,
7.3.8 Change / Departments

The Change / Departments function can be used to change the
department names for external connections. The function is used to
change a department name, for example, when blocks have been
combined with the block hierarchy by copying from another
department.
Use the Old department field to write the name of the department to
be changed.
The New department field is used to write the name of the new
department.

The Beginning block field is used to define the block below which the
blocks’ department is to be changed. This means that the Beginning
block’s department will not be changed.
button closes the window without changing the department.
7.3.9 Change / Alarms output manner

Note! Function has no effect on within the Experion PKS with PMD
The Change / Alarms output manner function can be used to change

the alarm output modes defined for the blocks.
The Beginning block field is used to define the block below which the
blocks’ alarm output mode is to be changed. This means that the
Beginning block’s department will not be changed.
The Manner of output field is used to write the number of the new
output mode.
button closes the window without making the change.

8 Tools
8.1 Tools menu description

The Block type menu is used to activate the Program Builder. The
Serial Interface Editor is not used in Experion PKS with PMD
8.2 Pascal
The Tools menu’s Pascal function activates the Program Builder
whose Pascal-based high-level language can be used to define type
blocks and application specific tag blocks.
To define a high-level language block, take the following steps:
1. Add to the block hierarchy the block to which the high-
level language code is to be written for.
2. Open the block in the Block Builder workspace and define
its required block pins. The block will use these pins to
connect to other blocks.
3. Mark the block as being ready and select the Pascal
function.
For detailed definition instructions, see the document Program
Builder.
An existing high-level language block can be edited by first opening
the block in the Block Builder workspace and then selecting the
Pascal function.
Experion PKS Tools • 3 - 69

9 Options
9.1 Options menu description

The Options menu’s functions are used to define the Block Builder
properties as well as the presentation features of Block Builder edited
blocks.
9.2 Language
The Options menu’s Language function can be used to change the
design module language (i.e. the PMD Explorer and the editors
accessed through it) from Finnish to English and vice versa. The
current language version is indicated by the v sign.
Note! The language version of the system is selected in connection

with the design module software installation.
Should the language version be changed after application definitions
have been made for the department in question and loaded to the
system, then the design module software must be reinstalled and the
desired language must be selected in this connection. After this all
system messages must be reloaded. Further, make needed actions to
change the language in application and faceplates.
3 - 70 • Options Experion PKS

9.3 Toolbar
The Options menu’s Toolbar functions are used to change the
appearance of the toolbar push buttons.
Rounded buttons.
Square buttons.
Flat buttons.
9.4 Text case

The Options menu’s Text case function can be used to change the
texts displayed in the Block Builder workspace into upper case or
lower case letters.
The Default option shows the pin names written in accordance with
the pin type appearance:
• Signal – all letters in lower case
• Real numbers – all letter in upper case
• Types other than signal or real number – upper case
initial letter, the rest in lower case.
The Lower case option turns all characters into lower case.
The Upper case option turns all characters into upper case.
9.5 Font
The Options menu’s Font function can be used to change the font for
the texts displayed in the Block Builder workspace. This function
opens a selection window to define the settings. The default font is
Courier, style Regular, and point size 9.
9.6 Colors
The Options menu’s Colors function can be used to change the
background colors and text colors for the blocks and pins displayed
in the Block Builder workspace, in accordance with several selection
criteria. Similarly, it is possible to change the connection colors, and
the background and text colors of the field that shows the pin values,
for example. The function can be used, for example, to define
separate colors for the basic blocks and type blocks of the block being
edited. Similarly, it is possible to define a specific color for the block
pins that contain interlock data.
This function first displays the Colors selection window with four
directly selectable color options for blocks and pins.
Experion PKS Options • 3 - 71

The Mono option displays the blocks and pins in black and
white only.
The Alcont 2 option displays the blocks and pins with blue
frames.
The Alcont 3000x option displays gray blocks and pins with
blue frames.
The TotalPlant option displays the blocks and pins on a

gray background.
To accept a selected option, click on the OK push button.
The Customize push button opens another definition window which
contains a number of color options. These options are used to
customize the color for the Block Builder workspace displayed
blocks, pins and connections and their texts and data items as
required.
The Change push button displays a color chart to select a new color
for a selected target.
The Default push button returns the default colors to the Block
Builder workspace.
The Cancel push button closes the window without changing the
colors.
The OK push button is used to accept the selections made.
3 - 72 • Options Experion PKS

9.7 Menu bitmaps
Activation of the Options menu’s Menu bitmaps function displays a
picture symbol in front of those function names that can also be
activated through the toolbar. Naturally, the picture symbol is the
same as that of the push button. Below as an example the Options
menu’s Font and Color functions.
Experion PKS Options • 3 - 73

10 Window
10.1 Window menu description

The Window menu functions are used to handle the windows
opened in the Block Builder.
10.2 Arrange
The Window menu’s Arrange function returns the windows opened
in the Block Builder to their defined default size and location.
10.3 Tile horizontal

The Window menu’s Tile horizontal function arranges the windows
opened in the Block Builder as a vertical row.
10.4 Tile vertical

The Window menu’s Tile vertical function arranges the windows
opened in the Block Builder adjacent to one another.
10.5 Cascade
The Window menu’s Cascade function superimposes the windows
opened in the Block Builder.
10.6 Close
The Window menu’s Close function is a forthcoming feature with no
definition to date.
3 - 74 • Window Experion PKS

10.7 Close all
The Window menu’s Close all function is a forthcoming feature with
no definition to date.
10.8 The name list of opened windows

The Window menu’s bottom edge displays the names of all windows
opened in the Block Builder. The name of an active window is
indicated by the v sign in front of it.
Experion PKS Window • 3 - 75

11 Help
11.1 Help menu description

The Help menu’s functions display a help window or a data window
on the screen.
11.2 Contents
The Help menu’s Contents function displays a help window with the
Block Builder user instructions.
3 - 76 • Help Experion PKS

11.3 Search for help on
The Help menu’s Search for help on function displays a help window
with the index based Block Builder user instructions.
11.4 Basic blocks

The Help menu’s Basic blocks function displays a help window with
the basic block descriptions.
11.5 System status messages

The Help menu’s System status messages function displays a help
window that contains the system’s status message descriptions.
Experion PKS Help • 3 - 77

11.6 About PMD Block Builder
The Help menu’s About PMD Block Builder function displays a
window that shows the Block Builder versions data.
To close the window, click on the toolbar’s Close push button with
the mouse.
3 - 78 • Help Experion PKS

12 Defining faceplates and
standard pins for tag blocks
12.1 Purpose of faceplates

Faceplates are ready-made pictures developed for the Experion PKS
with PMD Controller automation system. They are used to display
the data of commonest tag blocks, such as measurements, controls,
motors and valves on the user interface monitor.
A desired faceplate is attached to a tag block by the Blocks menu’s
Header function in the Block Builder (See section Header). Part of the
faceplate texts and faceplate extension texts are defined in the header
definition’s Setting initial Face Plate values window. When defining
a tag block, it is necessary to use the standard pins required by the
selected faceplate. These pins automatically relay the data from the
tag block definition to the faceplate.
The following is a description of the various faceplates, their
extensions and the standard pins that automatically relay the data
from the block definition to the faceplate. For detailed faceplate
operator instructions, see the document Operator's Guide.
Note! Some data defined in the Setting initial Face Plate values
window should be localized by using the localization tools of the
12.1.1 Trend collection categories and collection data

Trend collection category History interval Number of samples Total collection time
Fast (1) 1 to 30-second snapshots 8652 2 hours to 72 hours
Standard (0) 1 min snapshot 1442 24 h
6 min average 1682 1 week
1 hour average 170 1 week
8 hour average 281 3 months
24 hour average 368 1 year
Extended (2) 1 hour snapshot 170 1 week
8 hour snapshot 281 3 months
24 hour snapshot 368 1 year
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 79
12.2 Measurement (Measure)
Measurement faceplate and the standard pins affecting it.

*) Data definition is made in the Setting initial Face Plate values window.
The Limits tab with the standard pins affecting it in the Measurement faceplate extension.
The Application specific tab with the standard pins affecting it in the Measurement faceplate
extension.
3 - 80 • Defining faceplates and standard pins for tag blocks Experion PKS
The Info tab with the standard pins affecting it in the Measurement faceplate extension.
**) Data definition is made in the Header window.
The Tuning tab with the standard pins affecting it in the Measurement faceplate extension.
The table below sets out the standard pins used in a measurement
tag block definition.
Input pins Output pins
dis Alarm disabling MES Measurement value
maw Maintenance MED Measurement disconnected
dct Disconnect measurement oks Alarm acknowledgement
FIL Measurement filter constant
ULL Upper interlock limit usa Upper sensor alarm
LLL Lower interlock limit lsa Lower sensor alarm
UAL Upper alarm limit uas Upper limit alarm
LAL Lower alarm limit las Lower limit alarm
UWL Upper warning limit uws Upper limit warning
LWL Lower warning limit lws Lower limit warning
MUL Measurement range upper limit
MLL Measurement range lower limit
PAR Application specific parameter
AP1 Application specific parameter 1
If the following pins are provided with purpose-based definitions at
the tag block definition stage, then they will display, when active, the
following information text over the faceplate.
Pin Text displayed
dis Alarms disabled
dct PV disconnected
maw Maintenance
The header definition’s Setting initial Face Plate values window is

used to define the data for the following Measurement faceplate
fields:
Name of field Definition Explanation
example
ID 1 The option selected is visible as tag ID
in the faceplate
1 = ID 1 (block name)
2 = ID 2 (e.g. electric tag ID)
3 = ID 3 (e.g. instrument tag ID)
Engineering unit kg/s
Decimal count in faceplate 2
Measurement bar type 0 0 = plot from bottom upwards (from
lower limit to upper limit).
1= plot from top downwards
(from upper limit to lower limit).
2 = plot from zero upwards and
downwards, if
lower limit < 0 and upper limit > 0.
Trend collection (pin,0/1/2) MES,0;PAR,0 Use semicolon (;) to separate values to
be collected. Collection options:
See also section 0 = Standard history
Trend collection categories and 1 = Fast history
collection data. 2 = Extended history
Connection to block 1 FIC-124
Connection to block 2 FIC-313
Meas. filt. (FIL) upper limit 1 Value between 0 … 1
Meas. filt. (FIL) lower limit 0 Value between 0 … 1
Parameter (PAR) upper limit 99999
Parameter (PAR) lower limit -99999
Parameter (PAR) label text PAR:
Parameter (AP1) upper limit 99999
Parameter (AP1) lower limit -99999
Parameter (AP1) label text AP1:
12.3 Control (Control)
Control faceplate and the standard pins affecting it.

The Interlocking causes tab with the standard pins affecting it in the Control faceplate
extension.
The Limits tab with the standard pins affecting it in the Control faceplate extension.
The Application specific tab with the standard pins affecting it in the Control faceplate
extension.
The Info tab with the standard pins affecting it in the Control faceplate extension.
The Tuning tab with the standard pins affecting it in the Control faceplate extension.
The table below sets out the standard pins used in a control tag block
definition.
mde Mode Man/Auto MES Measurement value
csm Cascade mode MED Measurement disconnected
cmm Computer mode oks Alarm acknowledgement
ser Application specific mode
dis Alarm disabling
maw Maintenance
dct Measurement disconnect
FIL Measurement filtering constant
ULL Upper interlock limit usa Upper sensor alarm
LLL Lower interlock limit lsa Lower sensor alarm
UAL Upper alarm limit uas Upper limit alarm
LAL Lower alarm limit las Lower limit alarm
UWL Upper warning limit uws Upper limit warning
LWL Lower warning limit lws Lower limit warning
SET Setpoint value CON Control value
RSE External setpoint value coa Control value alarm
GNF Gain factor
INT Integration time mol Mode interlocked
DER Derivation time los Control interlocked
MUL Measurement range upper limit
MLL Measurement range lower limit pas Bypass
PAR Application specific parameter
RMP Application specific ramping value
DEA Control deviation alarm limit dev Control deviation alarm
If the following pins are provided with purpose-based definitions at

the tag block definition stage, then they will display, when active, the
Pin Text displayed
dis Alarms disabled
dct PV disconnected
maw Maintenance
mol Mode interlocked
los OP interlocked
pas Bypass
Use the header definition’s Setting Initial Face Plate Values window
to define the data for the following fields in the Control faceplate:
example
in the faceplate
Engineering unit kg/s
Decimal count in faceplate 2
Measurement bar type 0 0 = plot from bottom upwards (from
lower limit to upper limit).
1= plot from top downwards
(from upper limit to lower limit).
2 = plot from zero upwards and
downwards, if
lower limit < 0 and upper limit > 0.
example
Control bar type 0 0 = analog value plot.
1 = digital value plot (not supported
by this system release)
Plot from bottom upwards, if
lower limit < upper limit
lower limit => 0
upper limit > 0
Plot from top downwards, if
lower limit < upper limit
lower limit < 0
upper limit =< 0
Plot from zero upwards and
downwards, if
lower limit < 0
upper limit > 0.
Trend collection (pin,0/1/2) MES,0;CON,0 Use semicolon (;) to separate values to
Default mode (0,1,2,3) 1 0 = manual, 1 = automatic,
2 = computer, 3 = cascade
Manual mode text Manual
Automatic mode text Automatic
Computer mode text Computer
Cascade mode text Cascade
Applic. spec. mode (ser) text Ramping
Control (CON) upper limit 100
Control (CON) lower limit 0
Connection from block LIC-313 E.g. remote setpoint tag block
Connection to block FFC-1020 E.g. controlled tag block
Ack. value change by dragging Y Value changes made by dragging with
the mouse
Y = must be acknowledged
N = need no acknowledgement.
Meas. filt. (FIL) upper limit 1 Value between 0 … 1
Meas. filt. (FIL) lower limit 0 Value between 0 … 1
Gain factor (GNF) upper limit 99999
Gain factor (GNF) lower limit -99999
Integration (INT) upper limit 99999 [min]
Integration (INT) lower limit -99999 [min]
Derivation (DER) upper limit 99999 [min]
Derivation (DER) lower limit -99999 [min]
example
Ramping (RMP) upper limit 99999
Ramping (RMP) lower limit 0
Ramping (RMP) label text RMP:
Deviation (DEA) upper limit 99999
Deviation (DEA) lower limit -99999
Deviation (DEA) label text DEA:
12.4 One-way motor and Pump (M1Way)
One-way motor faceplate and the standard pins affecting it.

The Interlocking causes tab with the definitions affecting it in the One-way motor faceplate
extension.
The Interlocking targets tab with the definitions affecting it in the One-way motor faceplate
extension.
The Application specific tab with the standard pins affecting it in the One-way motor
The Info tab with the definitions affecting it in the One-way motor faceplate extension.
The table below contains the standard pins used in the tag block
definitions of one-way motor.
mde Mode Man/Auto alr Alarm
ser Application specific mode oks Alarm acknowledgement
dis Alarm disable cst Control state
maw Maintenance ist Disable start
mst Manual start isp Disable stop
msp Manual stop pst Protective start
MUL *) Current measurement upper psp Protective stop
limit
MLL *) Current measurement lower lcs Local control state
limit
UAL *) Current measurement alarm mol Mode interlocked
limit
rng Run data (I/O) dil Function disabled
AP1 Application specific parameter 1 MES *) Current measurement
AP2 Application specific parameter 2 uas *) Current measurement alarm
srv Service (motor center) pas Bypass
*) Only for motors which have the current measurement. When these
pins are defined, the numerical value of current measurement is
shown in the faceplate automatically. The engineering unit and
indicator are defined in the Setting initial Face Plate values window;
parameters Engineering unit, Current measurement and Logarithmic
current meas.
If a purpose-based definition is made for the following pins in the tag
block definition, then they will display, when active, the following
information text over the faceplate.
Pin Text displayed
dis Alarms disabled
maw Maintenance
ist Inhibited start
isp Inhibited stop
pst Protective start
psp Protective stop
lcs Local control
dil Function disabled
srv On service
pas Bypass
One-way motor control states are:

• State0 = motor stopped
• State1 = motor running
Use the header definition’s Setting initial Face Plate values window
to define the data for the following fields in the One-way motor
faceplate:
example
in the faceplate
Current measurement (indicator) Y Y = Current measurement indicator
visible
N = Current measurement indicator
not visible
Engineering unit %
Logarithmic current meas. (indicator) N Y = Logarithmic current measurement
indicator
N = Linear current measurement
indicator.
Trend collection (pin, 0/1/2) MES, 0 Use semicolon (;) to separate values to
Default mode (0,1) 1 0 = manual, 1 = automatic
Applic. spec. mode (ser) text
Ack. for manual control Y Y = manual control must be
acknowledged
N = manual control need no
acknowledgement
State0 txt: rng=0, cst=0 Stopped Text is shown in the lower push
button of the faceplate
State1 txt: rng=0, cst=0 Start Text is shown in the upper push
State1 txt: rng=0, cst=1 Starting Text is shown in the upper push
State1 txt: rng=1, cst=1 Running Text is shown in the upper push
State0 txt: rng=1, cst=1 Stop Text is shown in the lower push
State0 txt: rng=1, cst=0 Stopping Text is shown in the lower push
Text when ist = 1 Inhibited start Text is shown on the faceplate.
Text when isp = 1 Inhibited stop Text is shown on the faceplate.
Text when pst = 1 Protective start Text is shown on the faceplate.
Text when psp = 1 Protective stop Text is shown on the faceplate.
Application specific text 1 E.g. electric or instrument ID.
Application specific text 2
example
Device picture in faceplate PMC_LCP_ImgM1
Way.gif
12.5 Two-way and Two-speed motor (M2Way, M2Speed)
Two-way motor faceplate and the Two-speed motor faceplate and the
standard pins affecting it. standard pins affecting it.
*) Data definition is made in the *) Data definition is made in the
Setting initial Face Plate values Setting initial Face Plate values
window. window.
The Interlocking causes tab with the definitions affecting it in the Two-way / Two-speed
motor faceplate extension.
The Interlocking targets tab with the definitions affecting it in the Two-way / Two-speed
The Application specific tab with the standard pins affecting it in the Two-way / Two-speed
The Info tab with the definitions affecting it in the Two-way / Two-speed motor faceplate
extension.
The table below contains the standard pins for use in the tag block
definitions of Two-way / Two-speed motor.
dis Alarm disable cs1 Control state 1
maw Maintenance cs2 Control state 2
mt1 Manual start 1 it1 Disable start 1
mt2 Manual start 2 it2 Disable start 2
msp Manual stop isp Disable stop
MUL *) Current measurement upper limit pt1 Protective start 1
MLL *) Current measurement lower limit pt2 Protective start 2
UAL *) Current measurement alarm limit psp Protective stop
rn1 Run data 1 (I/O) lcs Local control state
rn2 Run data 2 (I/O) mol Mode interlocked
AP1 Application specific parameter 1 dil Function disable
AP2 Application specific parameter 2 MES *) Current measurement
srv Service (motor center) uas *) Current measurement alarm
pas Bypass
*) Only for motors which have the current measurement. When these
pins are defined, the numerical value of current measurement is
shown in the faceplate automatically. The engineering unit and
indicator are defined in the Setting initial Face Plate values window;
parameters Engineering unit, Current measurement and Logarithmic
current meas.
Pin Text displayed
dis Alarms disabled
maw Maintenance
it1 Inhibited start 1
it2 Inhibited start 2
isp Inhibited stop
pt1 Protective start 1
pt2 Protective start 2
psp Protective stop
lcs Local control
srv On service
pas Bypass
Two-way / Two-speed motor control states are:

• State0 = motor stopped
• State1 = motor running direction 1 / speed 1
• State2 = motor running direction 2 / speed 2
to define the data for the following fields in the Two-way / Two-
speed motor faceplate:
example
in the faceplate
Current measurement Y Y = Current measurement indicator
visible
N = Current measurement indicator
not visible
Engineering unit %
Logarithmic current meas. N Y = Logarithmic current measurement
indicator
N = Linear current measurement
indicator.
Trend collection (pin, 0/1/2) MES, 0 Use semicolon (;) to separate values to
acknowledged
acknowledgement
Change (0:without stop,1:stop) 0 Way/Speed change:
0 = without stop
1= with stop
State0 txt: rn1=0, rn2=0 Stopped Text is shown in the M2Way faceplate
middle push button and in the
M2Speed faceplate lowest push
button.
State1 txt: rn1=0, cs1=0 Start1 Text is shown in the M2Way faceplate
uppermost push button and in the
M2Speed faceplate middle push
button.
State1 txt: rn1=0,cs1=1 Starting1 Text is shown in the M2Way faceplate
button.
State1 txt: rn1=1, cs1=1 Running1 Text is shown in the M2Way faceplate
button.
State0 txt when running Stop Text is shown in the M2Way faceplate
button.
State0 txt when stopping Stopping Text is shown in the M2Way faceplate
example
button.
State2 txt: rn2=0, cs2=0 Start2 Text is shown in the M2Way faceplate
lowest push button and in the
M2Speed faceplate uppermost push
button.
State2 txt: rn2=0,cs2=1 Starting2 Text is shown in the M2Way faceplate
button.
State2 txt: rn2=1, cs2=1 Running2 Text is shown in the M2Way faceplate
button.
Text when it1 = 1 Inhibited start1 Text is shown on the faceplate.
Text when it2 = 1 Inhibited start2 Text is shown on the faceplate.
Text when isp = 1 Inhibited stop Text is shown on the faceplate.
Text when pt1 = 1 Protective start1 Text is shown on the faceplate.
Text when pt2 = 1 Protective start2 Text is shown on the faceplate.
Text when psp = 1 Protective stop Text is shown on the faceplate.
Device picture in faceplate PMC_LCP_ImgM1
Way.gif
12.6 Open/close valve and Three-way valve (Valve)
Open/close valve and Three-way valve faceplate and the standard pins affecting it.
The Interlocking causes tab with the definitions affecting it in the Open/close valve or Three-
way valve faceplate extension.
The Interlocking targets tab with the definitions affecting it in the Open/close valve or Three-
way valve faceplate extension.
The Application specific tab with the standard pins affecting it in the Open/close valve or
Three-way valve faceplate extension.
The Info tab with the definitions affecting it in the Open/close valve or Three-way valve
definition of open/close or three-way valve.
dis Alarm disable cst Control state
maw Maintenance lcs Local control state
mop Manual control open iop Disable open
mcl Manual control close icl Disable close
lso Limit data open (I/O) pop Protective open
lsc Limit data closed (I/O) pcl Protective close
AP1 Application specific parameter 1 mol Mode interlocked
pas Bypass

Pin Text displayed
dis Alarms disabled
maw Maintenance
iop Inhibit open
icl Inhibit close
pop Protective open
pcl Protective close
lcs Local control
pas Bypass
Open/close and three-way valve control states are:

• State0 = close
• State1 = open
to define the data for the following fields in the Open/close and
Three-way valve faceplate:
example
in the faceplate
Trend collection (pin, 0/1/2) Use semicolon (;) to separate values to
acknowledged
acknowledgement
State0 txt: lsc=1, cst=0 Closed Text is shown in the lower push
State1 txt: lso=0, cst=0 Open Text is shown in the upper push
State1 txt: lso=0, cst=1 Opening Text is shown in the upper push
State1 txt: lso=1, cst=1 Open Text is shown in the upper push
State0 txt: lsc=0, cst=1 Close Text is shown in the lower push
State0 txt: lsc=0, cst=0 Closing Text is shown in the lower push
Text when iop = 1 Inhibited open Text is shown on the faceplate.
Text when icl = 1 Inhibited close Text is shown on the faceplate.
Text when pop = 1 Protective open Text is shown on the faceplate.
Text when pcl = 1 Protective close Text is shown on the faceplate.
Device picture in faceplate PMC_LCP_ImgValv
e.gif
12.7 Motor valve (MValve)
Motor valve faceplate and the standard pins affecting it.

The Interlocking causes tab with the definitions affecting it in the Motor valve faceplate
extension.
The Interlocking targets tab with the definitions affecting it in the Motor valve faceplate
extension.
The Application specific tab with the standard pins affecting it in the Motor valve faceplate
extension.
The Info tab with the definitions affecting it in the Motor valve faceplate extension.
**) Data definition is made in Header window.
The table below contains the standard pins for use in the tag block
definition of motor valve.
maw Maintenance MES *) Position measurement
dis Alarm disable cs1 Control state open
mop Manual control open cs2 Control state close
mcl Manual control close lcs Local control state
msp Manual stop iop Disable open
MUL *) Position meas. upper limit icl Disable close
MLL *) Position meas. lower limit pop Protective open
lso Limit data open (I/O) pcl Protective close
lsc Limit data close (I/O) mol Mode interlocked
rng Run data (I/O) dil Function disable
AP1 Application specific parameter 1 pas Bypass
*) Only for motor valves which have the position measurement.

When these pins are defined, the numerical value of position
measurement is shown in the faceplate automatically. The
engineering unit and indicator are defined in the Setting initial Face
Plate values window; parameters Engineering unit and Position
measurement.
Pin Text displayed
dis Alarms disabled
maw Maintenance
iop Inhibited open
icl Inhibited close
pop Protective open
pcl Protective close
lcs Local control
pas Bypass
Motor valve control states are:

• State0 = closed
• State1 = open
• State2 = stopped
to define the data for the following fields in the Motor valve
faceplate:
Name of field Definition example Explanation
in the faceplate
Position measurement Y Y = Position measurement indicator
visible
N = Position measurement indicator
not visible.
Engineering unit %
acknowledged
acknowledgement
State0 txt: lsc=1, cs2=1 Closed Text is shown in the lowest push
button of the faceplate.
State1 txt: lso=0, cs1=0 Open Text is shown in the uppermost push
State1 txt: lso=0 cs1=1 Opening Text is shown in the uppermost push
State1 txt: lso=1, cs1=1 Open Text is shown in the uppermost push
State0 txt: lsc=0, cs2=0 Close Text is shown in the lowest push
State0 txt: lsc=0, cs2=1 Closing Text is shown in the lowest push
State2 txt: rng=1 Stop Text is shown in the middle push
State2 txt: rng=0 Stopped Text is shown in the middle push
Text when iop = 1 Inhibited open Text is shown on the faceplate.
Text when icl = 1 Inhibited close Text is shown on the faceplate.
Text when pop = 1 Protective open Text is shown on the faceplate.
Text when pcl = 1 Protective close Text is shown on the faceplate.
Device picture in faceplate PMC_LCP_ImgMot
orValve.gif
12.8 Control switch (CSwitch)
Control switch faceplate and the standard pins affecting it.

The Interlocking causes tab with the definitions affecting it in the Control switch faceplate
extension.
The Interlocking targets tab with the definitions affecting it in the Control switch faceplate
extension.
The Application specific tab with the standard pins affecting it in the Control switch
The Info tab with the definitions affecting it in the Control switch faceplate extension.
definition of control switch .
maw Maintenance cst Control state
dis Alarm disable lcs Local control state
mon Manual control on ion Disable on
mof Manual control off iof Disable off
onn Switch on (I/O) pon Protective on
off Switch off (I/O) pof Protective off
pas Bypass

Pin Text displayed
dis Alarms disabled
maw Maintenance
ion *)
iof *)
pon *)
pof *)
lcs Local control
pas Bypass
*) The text is defined in the Setting initial Face Plate values window.
Control switch states are:
• State0 = switch off
• State1 = switch on
Use the header definition’s Setting initial values window to define
the data for the following fields in the Control switch faceplate:
example
in the faceplate
example
acknowledged
acknowledgement
State0 txt: off=1, cst=0 Off Text is shown in the lower push
State1 txt: onn=0, cst=0 On Text is shown in the upper push
State1 txt: onn=0, cst=1 To on Text is shown in the upper push
State1 txt: onn=1, cst=1 On Text is shown in the upper push
State0 txt: off=0, cst=1 Off Text is shown in the lower push
State0 txt: off=0, cst=0 To off Text is shown in the lower push
Text when ion = 1 Inhibited on Text is shown on the faceplate.
Text when iof = 1 Inhibited off Text is shown on the faceplate.
Text when pon = 1 Protective on Text is shown on the faceplate.
Text when pof = 1 Protective off Text is shown on the faceplate.
Device picture in faceplate PMC_LCP_ImgCsw
itch.gif
12.9 Device control (Device)

Note! If you are using the Device control faceplate to control a
hydraulic directional valve, see also the document Hydraulic and
Pneumatic Control Toolbox. This document describes in detail the
definitions to be made for the tag block as well as the use of faceplate
and standard pins.
Two-state Device control faceplate and the Three-state Device control faceplate and the
standard pins affecting it. standard pins affecting it.
*) Data definition is made in the Setting initial *) Data definition is made in the Setting initial
Face Plate values window. Face Plate values window.
The Interlocking causes tab with the definitions affecting it in the Device control faceplate
extension.
The Application specific tab with the standard pins affecting it in the Device control faceplate
extension.
The Info tab with the definitions affecting it in the Device control faceplate extension.
definitions of device control.
dis Alarm disable cs1 Control state 1
maw Maintenance cs2 Control state 2
md1 Manual state1 id1 Disable state1
md2 Manual state2 id2 Disable state2
mdm Manual state3 idm Disable state3
ls1 Limit state1 pd1 Protective state1
ls2 Limit state2 pd2 Protective state2
lsm Limit state3 (only for 3-state pdm Protective state3 (only for 3-
device control) state device control)
AP1 Application specific parameter 1 lcs Local control state
dil Function disable
pas Bypass

Pin Text displayed
dis Alarms disabled
maw Maintenance
id1 Inhibited state 1
id2 Inhibited state 2
idm Inhibited state 3
pd1 Protective state 1
pd2 Protective state 2
pdm Protective state 3
lcs Local control
pas Bypass
Device control states are:
• State1 = direction 1
• State2 = direction 2
• State2 = middle position
to define the data for the following fields in the Device control
faceplate:
example
in the faceplate
Number of states (2, 3) 2
acknowledged
acknowledgement
State1 txt: ls1=1,cs1=1 State1 Text is shown in the faceplate lowest
push button.
State2 txt: ls2=0,cs2=0 State2 Text is shown in the faceplate
uppermost push button.
State2 txt: ls2=0,cs2=1 To State2 Text is shown in the faceplate
State2 txt: ls2=1,cs2=1 State2 Text is shown in the faceplate
State1 txt: ls1=0,cs1=0 State1 Text is shown in the faceplate lowest
push button.
State1 txt: ls1=0,cs1=1 To State1 Text is shown in the faceplate lowest
push button.
State3 txt: ldm=0 State3 (Only for 3-state device control) Text is
shown in the faceplate middle push
button.
State3 txt: ldm=0,cs1=1/cs2=1 To State3 (Only for 3-state device control) Text is
button.
State3 txt: ldm=1 State3 (Only for 3-state device control) Text is
button.
Text when id1=1 Inhibited state1
Text when id2=1 Inhibited state2
Text when idm=1 Inhibited state3 (Only for 3-state device control)
Text when pd1=1 Protective state1
Text when pd2=1 Protective state2
Text when pdm=1 Protective state3 (Only for 3-state device control)
example
Title for interlockings Tag name
Title for description Description
Title for target 1 Target 1
Device picture in faceplate PMC_LCP_ImgDCT
woState.gif
12.10 General logic (Genlog)

General logic faceplate can be used for a number of various
purposes. The application method is defined as per project. A
General logic faceplate can be used, for example, to present the status
data of a specific process entity, or the states of logical inputs and
outputs.
The General logic faceplate can show a maximum of 60 data items
that have been defined under 1-8 headers. If necessary, a single data
item can be defined under several headers. This means that each data
presentation location corresponds to one data item in the faceplate.
General logic faceplate and the definitions affecting it.

The Info tab in the General logic faceplate extension.
**) Data definition is made in Header window.
The data items residing under the headers in the faceplate are
defined by using the Block Builder’s Pins menu’s Insert function.
The pin is defined as the creator of an interlock. This displays the

Interlock data window on the screen. Write the data description and
tag block ID and select from the Definition field the header numbers
under which the data will be placed in the faceplate.
to define the header names, header locations and the color to show
activated data.
ID 1 The option selected is visible as tag
ID in the faceplate
Title1 text Start 1
Title1 color #0000FF
Title1 pos. (left=0, right=1) 0
Title2 text Start 2
Title2 color #008000
Title3 text Stop 1
Title3 color #FF0000
Title4 text Stop 2
Title4 color #FFFF00
Title5 text
Title5 color
Title5 pos. (left=0, right=1)
Title6 text
Title6 color
Title7 text
Title7 color
Title8 text
Title8 color
This means that 1-8 headers can be defined for each faceplate. The
name has a maximum length of 20 characters. Each header can be
located in the faceplate’s left-hand or right-hand column.
The color definition means that the background color of the data
residing under the header in question will change in accordance with
the color definition when the data is activated.
The color is defined by using the RGB color codes. The color
definition is described in detail in the section Defining colors. In the
following table there are some most common RGB color codes:
Color Code
Black #000000
White #FFFFFF
Red #FF0000
Green #008000
Blue #0000FF
Yellow #FFFF00
Gray #EEEEEE
Pink #FFC0CB
Light green #90EE90
Light blue #ADD8E6
Light yellow #FFFFE0
Blueviolet #8A2BE2
Fuchsia #FF00FF
Orange #FFA500
12.11 Binary (Binary)

Binary faceplate can be user for a number of various purposes. The
application method is defined as per project. A Binary faceplate can
be used, for example, to present the limit data for various processes,
e.g. pressure limits, surface level limits (upper and lower) and
position data (home positions/work positions, up/down, etc.).
Two data items (ou1 and ou2) can be presented in a Binary faceplate.
Each data item can be separately provided with description and
header. It is also possible to define the background color for both
signal states of the data items.
In addition, a Binary faceplate offers freely definable signals (si1 and
si2) to the two data items. You can define purpose-based headers and
information texts for the signals. The active status of a signal displays
a definable text over the faceplate. All faceplate texts are defined in
the block’s header definition, in the Setting initial Face Plate values
window.
Binary faceplate and the standard pins affecting it.
The Signals tab with the standard pins affecting it in the Binary faceplate extension.
The Info tab in the Binary faceplate extension.

The table below contains the standard pins used in a binary tag block
definition.
dis Alarm disable oks Alarm acknowledgement
si1 Signal 1 ou1 Input 1
si2 Signal 2 ou2 Input 2
PAR Application-specific parameter
If the following pins are provided with a purpose –based definition
in the tag block definition, then they will display, when active, the
Pin Text displayed
dis Alarms disabled
The texts to be displayed in a Binary faceplate are defined in the

header definition’s Setting initial Face Plate values window.
ID in the faceplate
Trend collection (pin,0/1/2) Use semicolon (;) to separate values
to be collected. Collection options:
Input1 label text Input 1
Input1 state text State 1
Input1 back color: ou1=0 #FFFFFF
Input1 back color: ou1=1 #00FF00
Signal1 (SI1) label text SI1
Signal1 (SI1) information text SI1 On Information text shown over the
faceplate
Input2 label text Input 2
Input2 state text State 2
Input2 back color: ou1=0 #FFFFFF
Input2 back color: ou1=1 #00FF00
Signal2 (SI2) label text SI2
Signal2 (SI2) information text SI2 On Information text shown over the
faceplate
PAR engineering unit %
The colors are defined by using the RGB color codes. Use RGB color
codes to define desired colors for Input1 back color: ou1=0,
Input1 back color: ou1=1, Input1 back color: ou12=0 and
Input1 back color: ou2=1.
The color definition is described in detail in the section Defining
colors. In the following table there are some most common RGB color
codes:
Color Code
Black #000000
White #FFFFFF
Red #FF0000
Green #008000
Blue #0000FF
Yellow #FFFF00
Gray #EEEEEE
Pink #FFC0CB
Light green #90EE90
Light blue #ADD8E6
Light yellow #FFFFE0
Blueviolet #8A2BE2
Fuchsia #FF00FF
Orange #FFA500
12.12 Sequence (Sequence)
Sequence faceplate and the definitions affecting it.

The Info tab in the Sequence faceplate extension.
The table below contains the pins used in the definition of a sequence
tag block.
mde Mode, Man/Auto (B) omd *) Mode Man/Auto (B)
ser Application specific mode act *) Sequence being executed
Yes/No (B)
sta Start (B) rng *) Sequence state
running/stopped (B)
stp Stop (B) pau *) Sequence in wait state (B)
enx Finish (B) ena *) Start enable (B)
Ste Step number (W) Ost *) Step number (W)
Sst Stop step (W) Oss *) Stop step (W)
Nxt Next step (W) Ctc *) Timeout (W)
ctr Time counter reset (B) cte *) Timeout alarm (B)
oks Alarm acknowledgement (B) Wtc *) Wait time (W)
Pas Pins to be by-passed (B10) Lim *) Disables and limitations (W)
Dst Display step (W) Ods *) Display step (W)
Con *) Progress condition states (B10)
*) The pin has an effect for the faceplate.

If the following pins are provided with a purpose –based definition
in the tag block definition, then they will display, when active, the
Pin Text displayed
Lim Disable stop
ena Disable start
The texts to be displayed in a Sequence faceplate are defined in the
header definition’s Setting initial Face Plate values window.
ID in the faceplate
Trend collection (pin,0/1/2) Use semicolon (;) to separate values
to be collected. Collection options:

Wait mode text Press start to continue
acknowledged
acknowledgement
State0 txt: rng=0 Stopped
State1 txt: rng=0,sta=0 Start
State1 txt: rng=0,sta=1 Starting
State1 txt: rng=1 Running
State0 txt: rng=1,stp=0 Stop:
State0 txt: rng=1,stp=1 Stopping
13 Block Simulator / Block
Monitor User Manual
13.1 Activation and operation of the Block Simulator /

Block Monitor
The Block Simulator and Block Monitor can be activated either via
the Block Builder or via the PMD Builder’s Browse window.
To activate via the Block Builder, use the File menu’s Simulate and
Monitor functions, or use the corresponding toolbar push buttons.
To activate via the Browse window, click on the name of the desired
block with the right-hand mouse button and select Simulate or
Monitor from the menu opened.
Once the Block Simulator and Block Monitor are activated, the block
which has been selected for editing in the Block Builder, or selected
in the Explorer’s hierarchical tree structure, will always be displayed
for testing.
Note! Type block simulation/monitoring must be activated via a

hierarchical block that uses the type block in question.
3 - 118 • Block Simulator / Block Monitor User Manual Experion PKS

To display the value of a desired pin, take the following steps:
1. Place the pointer on the name of the pin and press the left-
hand mouse button. This will cause the pin to be
surrounded by a dashed line.
2. Keeping the mouse button depressed, move the pointer to
the location where the pin name and value are to be
displayed. Release the mouse button, thus causing the pin
data to be displayed in the selected location.
To delete a data item from monitoring, place the pointer on the pin
data to be deleted and click the right-hand mouse button. This will
cause the pin data to be deleted from the monitor screen.
Moving within the block hierarchy
You can use the Block Simulator and Block Monitor to move up and
down in accordance with the block hierarchy. To move down, place
the pointer on the name of a hierarchical block and double-click the
left-hand mouse button. Correspondingly, to move up, place the
pointer on the header bar of the Block Simulator or Block Monitor
and double-click the left-hand mouse button. A precondition for
moving to an upper hierarchical block is that simulation has been
activated from an upper hierarchical block.
Menu bar and toolbar
The Block Simulator and Block Monitor are provided with a menu
bar and a toolbar that contains all the functions required for block
testing.
The menus and push buttons are operated similarly to those of the
Block Builder, for example.
Data window
The Block Simulator and Block Monitor have a data window that is
always open and shows the block execution cycle. The block
execution cycle can be changed by using the Block cycle function.
The window’s header bar indicates whether the block being tested is
running or halted. The Block Monitor’s header bar also indicates the
definitions made through the Test settings function (E/I/C). In
addition, the window shows the load of the process module that
executes the block.
Experion PKS Block Simulator / Block Monitor User Manual • 3 - 119

13.2 Block menu
The Block menu’s functions are used to define the blocks and their
functions during testing.
13.2.1 Open
The Block menu’s Open function opens a selection window to open
another block for testing.
The window’s list field will display the names of the blocks that have
been opened during the current simulation or monitoring session.
The Open function can also be activated through the toolbar.
Note! In the Block Monitor you can open loaded blocks only. If you
try to open a block that is not loaded, the system outputs a message.
13.2.2 Back and Next

The Block menu’s Back and Next functions can be used to quickly
move between the blocks, after having opened several blocks in the
Block Simulator or Block Monitor.
The Back and Next functions can also be activated through

the toolbar.
13.2.3 Print
The Print function is not in use.

13.2.4 Run and Stop
The Block menu’s Run function starts block execution.
Correspondingly, the Stop function stops block execution
Once these functions are selected, the Block Monitor will display a
window that requests verification for the function selected.
If the reply is:

OK : the function will be executed.
Cancel : the function will not be executed and the program returns to
testing.
The Run and Stop functions can also be activated through

the toolbar.
13.2.5 Speed
The Block menu’s Speed function is only available in the Block
Simulator. The function displays a selection window to change the
block simulation speed.
The default simulation speed is the same as the block’s defined

execution cycle. This speed can be slowed down, however. The
slower speed options are the real speed divided by 2, 10, 50, 100, or
500. It is also possible to enter a desired value as the slow-down
value.
The speed function can also be activated through the toolbar.

13.2.6 Cycle
The Block menu’s Cycle function displays a selection window to
change the block’s defined execution cycle.
When selected from the Block Simulator, the Cycle function will
change the execution cycle in the design module. When selected from
the Block Monitor it will change the execution cycle in the process
module.
The Cycle function can also be activated through the toolbar.
13.2.7 Test settings

The Block menu’s Test settings function is only available in the Block
Monitor. The function displays the following selection window.
The Disconnection of external pins selection will disconnect the

block’s connections with names, to enable the entry of values for the
pins.
The Disconnection of I/O input selection will disconnect the block’s
I/O pin connections, to enable the entry of values for the pins.
The Copy pins selection is used to activate the copying of another
pin’s data to those pins that been defined to receive a pin copy. To
copy a pin, use the Copy pins option displayed in the Block Builder’s
Test setting window.

13.2.8 Save variables
The Block menu’s Save variables function is only available in the
Block Monitor. The function will save the variable values of the block
in the Block Monitor from the process module to the database of the
PMD server.
The Block Builder requests verification for the function. If the reply is
OK, then the variables will be saved and, once the saving has been
completed, the Block Builder will display the following message
window
Acknowledge this window by pressing the

OK push button.
The Save variables function can also be activated through the

toolbar.
13.2.9 Public pins

This function is mainly required for the testing of high-level
language blocks, due to the fact that high-level language code can
contain public pins which are not displayed as block pins in high-
level language tag blocks.
The Block menu’s Public Pins function displays a window showing
the block’s public pins.
To transfer the pins to testing from the list, activate a desired by
clicking on it with the left-hand mouse button and then press the
window’s OK push button.
13.3 Fields menu

The Fields menu’s functions are used to define, among other things,
the output mode for the values being monitored, plus potential data
transfer to other software packages.

13.3.1 Handle
The Fields menu’s Handle function displays the following selection
window on the screen.
The Display freeze option will freeze the updating of pin data in the
display. This enables the saving of momentary test situations for
detailed analysis at a later stage. Regardless of the display being
frozen, block execution continues normally in other respects.
The Insert option enables the entry of new values to the pin data. In
simulation, the values are transmitted to the design module, and to
the process module for monitoring. One or several values can be
entered at a time.
1. Place the pointer on the pin data which is to receive a new
value and click the left-hand mouse button. The frame
color of the pin data will change to indicate that a new
value may be entered.
2. Enter the new value. Pressing the Enter key will transmit
the new value to the design module or process module. In
cases where there are several values to be transmitted
simultaneously, press the Enter key only after you have
selected the last value.
The Display and Insert selections will remain valid until they are
reselected.
The Handle function can also be activated through the toolbar.

Attaching pin data:
If necessary, the pin data can be attached so as to remain on the
screen, in spite of moving to another block. When attaching pin data,
the Handle function’s Insert option must not be selected.
To attach a pin data item, double-click on it with the left-hand mouse
button. A selection window will be displayed on the screen, to select
the Fixed field option.
The window can also be used to define the presentation form for the
pin data.
The Windows data transfer option (DDE) is selected for a pin whose
data is to be collected by another Windows program, e.g. Excel. To
activate the data transfer, use the Settings function.
The Info push button outputs a window which shows the value field
data. This data is needed only by system software specialists.
13.3.2 Delete all

The Fields menu’s Delete all function deletes from the screen all the
pin data items retrieved for monitoring.
The Delete all function can also be activated through the toolbar.
13.3.3 Settings
The Fields menu’s Settings function is used to define the output
mode for the values being monitored. New settings are displayed by
those pin data items that are opened after defining new settings. The
function displays a selection window.
The Settings functions can also be activated through the toolbar.
The Width field is used to define the number of characters to be

displayed.
For signals, four presentation forms are available: bit/LSB, binary,
decimal and hex. For example, a signal whose decimal value is 51 is
displayed in the various presentation forms as follows:
Bit/LSB 1
Binary 00110011
Decimal 51
Hex 33
For the Real and Longreal real numbers, the number of decimals can
be defined, in addition to the number of characters.

The Hidden pins option will display any hidden pins contained in
the blocks. Hidden pins are used in logical package blocks, for
example. Correspondingly, the Running order option will display
the blocks’ execution numbers.
The definitions made for the Data transmission to other Windows
programs (DDE) option can be used to transfer data from the Block
monitor via a DDE link to other Windows–based applications, to the
Matlab software package, for example. This means that the Block
Monitor, for example, can be used to collect data process data for a
file or an Excel table, for example.
The Application field is used to define the data collection target. The
Document field defines the file where the data will be saved. For
example
• Application = Excel and Document = trend.xls
• Application = File and Document = A:\data.ate
Before the data transfer may be activated, it is necessary to define the
pins to be included in the collection. This is done by opening the
fields of the desired pins in the Block Simulator / Block Monitor by
marking the All fields option as having been selected.
Individual pins can also be defined for collection through the Value
field window. See the Handle function / Attaching pin data.
Selecting the Active option will activate data collection.
Note! The software package that will receive the collected data must
be activated before collection is started.
The Handling field’s Save push button saves the definitions made in
the Application and Document fields as default values. Thus, the
said values will be available when the Block Simulator / Block
Monitor is subsequently activated. The Defaults push button
retrieves the fault values to the Application and Document fields.
The OK push button saves the definitions made in the window and
closes the window.
definitions made.
13.4 Return
The Return menu’s Return function closes the Block Simulator or
Block Monitor and the software will take the user back to the Block
Builder.

14 Converting Block Builder
Applications to XML files
14.1 Converting Block Builder Applications to XML files

If you want to merge blocks to R7XX system from R6XX system, the
blocks must first be converted to XML files. After converting the
blocks to XML files you can use the Blocks / Import function.
Launch ConvertBLS.exe. The program is located in the directory
C:\Program Files\Honeywell\PMDC\PMDBuilder.
Experion PKS Converting Block Builder Applications to XML files • 3 - 127

Select type: Select the type of the blocks to be converted. The
alternatives are Basic, Type, Model or Hierarchy.
Select language: Select the block language. The function is available
for basic blocks and type blocks and the alternatives are English,
Finnish, German or French.
Select source folder: Select the folder in which the blocks to be
converted are located.
• When converting hierarchic blocks, select the project folder,
e.g. C:\AC_CONF\APPL\PMDTEST5\000.
• When converting type blocks, select the CONTTYPS folder,
e.g. C:\AC_CONF\APPL\PMDTEST5\CONTTYPS.
Select destination folder: Select the folder to which the converted
blocks will be saved.
Select license: Select the license to be used.This field shows the
licenses to which the project has conversion rights.
Analyze: After making the selections, press the Analyze button to
analyze the blocks. The analysis solves block hierarchies and type
block names.
Convert: When the selections have been made press Convert to start
converting the blocks to XML.
If the program was not able to convert all blocks, a list of those blocks
is displayed after conversion. Note! If the block hierarchy has not
3 - 128 • Converting Block Builder Applications to XML files Experion PKS

been totally converted, the following error messages may be
displayed:
• “Duplicate blocks. Newer file is selected”.
The error message means that several blocks having the
same name has been found in the block hierarchy. Then the
program selects the newest block version and ignores the
others.
• “Block conversion error”
The error message means that block conversion to XML did
not succeed. If this error occurs in the conversion, the
converted block hierarchy is broken. If the error occurs
during type block conversion, single type blocks are not
available.
The following picture shows an example of converted type blocks.
The following picture shows an example of XML block hierarchy.
Experion PKS Converting Block Builder Applications to XML files • 3 - 129


PMD Builder - Blocks

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PMD Builder - Blocks

Încărcat de

Drepturi de autor:

Formate disponibile

Experion PKS

Notices, Copyright, and Trademarks

Experion PKS Contents • 3 - i

3 - ii • Contents Experion PKS

12 Defining faceplates and standard pins for tag blocks 79

13 Block Simulator / Block Monitor User Manual 118

14 Converting Block Builder Applications to XML files 127

Experion PKS Contents • 3 - iii

1.1 Purpose of Blocks application definition

Experion PKS Blocks application definition with the Block Builder • 3 - 1

If project and department definitions have been done, the

3 - 2 • Blocks application definition with the Block Builder Experion PKS

1.3 Creating block definitions

The ADD block is an example of this block type.

1.3.2 Menu bar and Toolbar

3 - 4 • Blocks application definition with the Block Builder Experion PKS

Experion PKS Blocks application definition with the Block Builder • 3 - 5

Selecting functions from the Block Builder workspace

1.3.4 Browse window

• The block hierarchy of the department being

• Basic block selection

• Type block selection connected to the system being

• Model block selection connected to the system

3 - 6 • Blocks application definition with the Block Builder Experion PKS

The block hierarchy is browsed with the mouse. To activate a desired

Experion PKS Blocks application definition with the Block Builder • 3 - 7

Selecting functions from the Browse window

Monitor - Opens the Block Monitor

3 - 8 • Blocks application definition with the Block Builder Experion PKS

1.3.5 Selecting functions from the menu

With the mouse:

Experion PKS Blocks application definition with the Block Builder • 3 - 9

1.3.6 Selecting functions from the toolbar

The current availability of push buttons depends on the Block

Insert Name Forward

Open Constant Simulate

Save Variable Monitor

Print Invert Pascal

Load Show values Information

Delete Show connections Font

Link Pin IO Color

Connect with flags Pin description Description

Connect with name Back Contents

To activate a desired push button, click on it with the left-hand

1.3.7 Defining colors

3 - 10 • Blocks application definition with the Block Builder Experion PKS

Experion PKS Blocks application definition with the Block Builder • 3 - 11

2.1 File menu description

3 - 12 • File Experion PKS

The Type block is a block assembled from a number of basic blocks

Select Hierarchical if the block to be saved is one of the blocks in the

Note! High-level language defined blocks cannot be saved through

3 - 14 • File Experion PKS

Experion PKS File • 3 - 15

The All pages selection outputs the entire documentation of the

3 - 16 • File Experion PKS

2.6 Print preview

The project related information (customer data) in the header table

Experion PKS File • 3 - 17

3 - 18 • File Experion PKS

If the block to be loaded is a type block, then loading can be

2.8 Load type

Experion PKS File • 3 - 19