Professional Documents
Culture Documents
Blocks application
definition
Experion PKS
Blocks application definition
Release: System Release 710
09/2007
PMD Builder_Blocks_Eng.doc
Section: 3-
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
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
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
Enter the credentials and press OK. The PMD Builder opens in a
System view.
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
Experion PKS Blocks application definition with the Block Builder • 3 - 3
Blocks application definition 09/2007
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.
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?
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.
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.
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
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 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
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.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).
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.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.
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.
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.
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.
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.
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.
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.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.
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.
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.
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.
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
will cause the block to be displayed in the first vacant block site
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.
3 - 36 • Blocks Experion PKS
Blocks application definition 09/2007
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.
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 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.
4.10 Search
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.2 Insert
The Pins menu’s Insert function is used to define all the pins
required by a block.
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-
Experion PKS Pins • 3 - 43
Blocks application definition 09/2007
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.
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
system. See document Localization.
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.
The Cancel push button closes the window without saving the
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
Experion PKS Pins • 3 - 45
Blocks application definition 09/2007
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.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.
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
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.
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:
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.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.
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.
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
system. See document Localization.
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.
The Cancel push button closes the window without saving the
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.
XPR-A
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.
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.
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:
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.
Use the Top block field to define the hierarchical block below which
the cycles are to be changed. This will also change the cycle of the top
block.
Use the Top block field to define the hierarchical block below which
the priorities are to be changed. This will also change the priority of
the top block.
Use the Beginning block field to define the hierarchical block below
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.
Use the Beginning block field to define the hierarchical block below
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,
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’ 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.
To activate the change, press the OK push button. The Cancel push
button closes the window without making the change.
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.
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.
Rounded buttons.
Square buttons.
Flat buttons.
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.
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 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.
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.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.
11.2 Contents
The Help menu’s Contents function displays a help window with the
Block Builder user instructions.
To close the window, click on the toolbar’s Close push button with
the mouse.
Note! Some data defined in the Setting initial Face Plate values
window should be localized by using the localization tools of the
system. See document Localization.
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 79
Blocks application definition 09/2007
12.2 Measurement (Measure)
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
Blocks application definition 09/2007
The Info tab with the standard pins affecting it in the Measurement faceplate extension.
*) Data definition is made in the Setting initial Face Plate values window.
**) 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
AP2 Application specific parameter 2
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 81
Blocks application definition 09/2007
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
3 - 82 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
12.3 Control (Control)
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.
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 83
Blocks application definition 09/2007
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.
*) Data definition is made in the Setting initial Face Plate values window.
**) Data definition is made in the Header window.
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.
Input pins Output pins
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
3 - 84 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
Input pins Output pins
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
AP1 Application specific parameter 1
AP2 Application specific parameter 2
RMP Application specific ramping value
DEA Control deviation alarm limit dev Control deviation alarm
Use the header definition’s Setting Initial Face Plate Values window
to define the data for the following fields in the Control faceplate:
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.
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 85
Blocks application definition 09/2007
Name of field Definition Explanation
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
be collected. Collection options:
See also section 0 = Standard history
Trend collection categories and 1 = Fast history
collection data. 2 = Extended history
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]
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:
Parameter (AP2) upper limit 99999
Parameter (AP2) lower limit -99999
3 - 86 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
Name of field Definition Explanation
example
Parameter (AP2) label text AP2:
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:
The Interlocking causes tab with the definitions affecting it in the One-way motor faceplate
extension.
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 87
Blocks application definition 09/2007
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
faceplate extension.
The Info tab with the definitions affecting it in the One-way motor faceplate extension.
*) Data definition is made in the Setting initial Face Plate values window.
**) Data definition is made in the Header window.
3 - 88 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
The table below contains the standard pins used in the tag block
definitions of one-way motor.
Input pins Output pins
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
mol Mode interlocked
ist Inhibited start
isp Inhibited stop
pst Protective start
psp Protective stop
lcs Local control
dil Function disabled
srv On service
pas Bypass
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 89
Blocks application definition 09/2007
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:
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)
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
be collected. Collection options:
See also section 0 = Standard history
Trend collection categories and 1 = Fast history
collection data. 2 = Extended history
Default mode (0,1) 1 0 = manual, 1 = automatic
Manual mode text Manual
Automatic mode text 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
button of the faceplate
State1 txt: rng=0, cst=1 Starting Text is shown in the upper push
button of the faceplate
State1 txt: rng=1, cst=1 Running Text is shown in the upper push
button of the faceplate
State0 txt: rng=1, cst=1 Stop Text is shown in the lower push
button of the faceplate
State0 txt: rng=1, cst=0 Stopping Text is shown in the lower push
button of the faceplate
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
Parameter (AP1) upper limit 99999
Parameter (AP1) lower limit -99999
Parameter (AP1) label text AP1:
Parameter (AP2) upper limit 99999
3 - 90 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
Name of field Definition Explanation
example
Parameter (AP2) lower limit -99999
Parameter (AP2) label text AP2:
Device picture in faceplate PMC_LCP_ImgM1
Way.gif
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.
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 91
Blocks application definition 09/2007
The Interlocking targets tab with the definitions affecting it in the Two-way / Two-speed
motor faceplate extension.
The Application specific tab with the standard pins affecting it in the Two-way / Two-speed
motor faceplate extension.
The Info tab with the definitions affecting it in the Two-way / Two-speed motor faceplate
extension.
*) Data definition is made in the Setting initial Face Plate values window.
**) Data definition is made in the Header window.
3 - 92 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
The table below contains the standard pins for use in the tag block
definitions of Two-way / Two-speed motor.
Input pins Output pins
mde Mode Man/Auto alr Alarm
ser Application specific mode oks Alarm acknowledgement
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.
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
mol Mode interlocked
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
dil Function disabled
srv On service
pas Bypass
Open/close valve and Three-way valve faceplate and the standard pins affecting it.
*) Data definition is made in the Setting initial Face Plate values window.
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 95
Blocks application definition 09/2007
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.
3 - 96 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
The Info tab with the definitions affecting it in the Open/close valve or Three-way valve
faceplate extension.
*) Data definition is made in the Setting initial Face Plate values window.
**) Data definition is made in the Header window.
The table below contains the standard pins used in the tag block
definition of open/close or three-way valve.
Input pins Output pins
mde Mode Man/Auto alr Alarm
ser Application specific mode oks Alarm acknowledgement
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
AP2 Application specific parameter 2 dil Function disable
pas Bypass
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 97
Blocks application definition 09/2007
Use the header definition’s Setting initial Face Plate values window
to define the data for the following fields in the Open/close and
Three-way valve faceplate:
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)
Trend collection (pin, 0/1/2) 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
Default mode (0,1) 1 0 = manual, 1 = automatic
Manual mode text Manual
Automatic mode text 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: lsc=1, cst=0 Closed Text is shown in the lower push
button of the faceplate
State1 txt: lso=0, cst=0 Open Text is shown in the upper push
button of the faceplate
State1 txt: lso=0, cst=1 Opening Text is shown in the upper push
button of the faceplate
State1 txt: lso=1, cst=1 Open Text is shown in the upper push
button of the faceplate
State0 txt: lsc=0, cst=1 Close Text is shown in the lower push
button of the faceplate
State0 txt: lsc=0, cst=0 Closing Text is shown in the lower push
button of the faceplate
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.
Application specific text 1 E.g. electric or instrument ID.
Application specific text 2
Parameter (AP1) upper limit 99999
Parameter (AP1) lower limit -99999
Parameter (AP1) label text AP1:
Parameter (AP2) upper limit 99999
Parameter (AP2) lower limit -99999
Parameter (AP2) label text AP2:
Device picture in faceplate PMC_LCP_ImgValv
e.gif
3 - 98 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
12.7 Motor valve (MValve)
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.
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 99
Blocks application definition 09/2007
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 the Setting initial Face Plate values window.
**) Data definition is made in Header window.
The table below contains the standard pins for use in the tag block
definition of motor valve.
Input pins Output pins
mde Mode Man/Auto alr Alarm
ser Application specific mode oks Alarm acknowledgement
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
AP2 Application specific parameter 2
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 101
Blocks application definition 09/2007
Name of field Definition example Explanation
State0 txt: lsc=0, cs2=1 Closing Text is shown in the lowest push
button of the faceplate.
State2 txt: rng=1 Stop Text is shown in the middle push
button of the faceplate.
State2 txt: rng=0 Stopped Text is shown in the middle push
button of the faceplate.
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.
Application specific text 1 E.g. electric or instrument ID.
Application specific text 2
Parameter (AP1) upper limit 99999
Parameter (AP1) lower limit -99999
Parameter (AP1) label text AP1:
Parameter (AP2) upper limit 99999
Parameter (AP2) lower limit -99999
Parameter (AP2) label text AP2:
Device picture in faceplate PMC_LCP_ImgMot
orValve.gif
The Interlocking causes tab with the definitions affecting it in the Control switch faceplate
extension.
3 - 102 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
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
faceplate extension.
The Info tab with the definitions affecting it in the Control switch faceplate extension.
*) Data definition is made in the Setting initial Face Plate values window.
**) Data definition is made in the Header window.
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 103
Blocks application definition 09/2007
The table below contains the standard pins used in the tag block
definition of control switch .
Input pins Output pins
mde Mode Man/Auto alr Alarm
ser Application specific mode oks Alarm acknowledgement
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
AP1 Application specific parameter 1 mol Mode interlocked
AP2 Application specific parameter 2 dil Function disable
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:
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)
Default mode (0,1) 1 0 = manual, 1 = automatic
Manual mode text Manual
Automatic mode text Automatic
Applic. spec. mode (ser) text
3 - 104 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
Name of field Definition Explanation
example
Ack. for manual control Y Y = manual control must be
acknowledged
N = manual control need no
acknowledgement
State0 txt: off=1, cst=0 Off Text is shown in the lower push
button of the faceplate
State1 txt: onn=0, cst=0 On Text is shown in the upper push
button of the faceplate
State1 txt: onn=0, cst=1 To on Text is shown in the upper push
button of the faceplate
State1 txt: onn=1, cst=1 On Text is shown in the upper push
button of the faceplate
State0 txt: off=0, cst=1 Off Text is shown in the lower push
button of the faceplate
State0 txt: off=0, cst=0 To off Text is shown in the lower push
button of the faceplate
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.
Application specific text 1 E.g. electric or instrument ID.
Application specific text 2
Parameter (AP1) upper limit 99999
Parameter (AP1) lower limit -99999
Parameter (AP1) label text AP1:
Parameter (AP2) upper limit 99999
Parameter (AP2) lower limit -99999
Parameter (AP2) label text AP2:
Device picture in faceplate PMC_LCP_ImgCsw
itch.gif
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 105
Blocks application definition 09/2007
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.
*) Data definition is made in the Setting initial Face Plate values window.
The Application specific tab with the standard pins affecting it in the Device control faceplate
extension.
3 - 106 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
The Info tab with the definitions affecting it in the Device control faceplate extension.
*) Data definition is made in the Setting initial Face Plate values window.
**) Data definition is made in the Header window.
The table below contains the standard pins used in the tag block
definitions of device control.
Input pins Output pins
mde Mode Man/Auto alr Alarm
ser Application specific mode oks Alarm acknowledgement
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
AP2 Application specific parameter 2 mol Mode interlocked
dil Function disable
pas Bypass
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 107
Blocks application definition 09/2007
Device control states are:
• State1 = direction 1
• State2 = direction 2
• State2 = middle position
Use the header definition’s Setting initial Face Plate values window
to define the data for the following fields in the Device control
faceplate:
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)
Number of states (2, 3) 2
Default mode (0,1) 1 0 = manual, 1 = automatic
Manual mode text Manual
Automatic mode text Automatic
Applic. spec. mode (ser) text
Ack. for manual control Y Y = manual control must be
acknowledged
N = manual control need no
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
uppermost push button.
State2 txt: ls2=1,cs2=1 State2 Text is shown in the faceplate
uppermost push button.
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
shown in the faceplate middle push
button.
State3 txt: ldm=1 State3 (Only for 3-state device control) Text is
shown in the faceplate middle push
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)
Application specific text 1 E.g. electric or instrument ID.
Application specific text 2
3 - 108 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
Name of field Definition Explanation
example
Parameter (AP1) upper limit 99999
Parameter (AP1) lower limit -99999
Parameter (AP1) label text AP1:
Parameter (AP2) upper limit 99999
Parameter (AP2) lower limit -99999
Parameter (AP2) label text AP2:
Title for interlockings Tag name
Title for description Description
Title for target 1 Target 1
Title for target 2 Target 2
Title for target 3 Target 3
Title for target 4 Target 4
Title for target 5 Target 5
Title for target 6 Target 6
Title for target 7 Target 7
Title for target 8 Target 8
Device picture in faceplate PMC_LCP_ImgDCT
woState.gif
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 109
Blocks application definition 09/2007
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.
3 - 110 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
Use the header definition’s Setting initial Face Plate values window
to define the header names, header locations and the color to show
activated data.
Name of field Definition example Explanation
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)
Title1 text Start 1
Title1 color #0000FF
Title1 pos. (left=0, right=1) 0
Title2 text Start 2
Title2 color #008000
Title2 pos. (left=0, right=1) 0
Title3 text Stop 1
Title3 color #FF0000
Title3 pos. (left=0, right=1) 1
Title4 text Stop 2
Title4 color #FFFF00
Title4 pos. (left=0, right=1) 1
Title5 text
Title5 color
Title5 pos. (left=0, right=1)
Title6 text
Title6 color
Title6 pos. (left=0, right=1)
Title7 text
Title7 color
Title7 pos. (left=0, right=1)
Title8 text
Title8 color
Title8 pos. (left=0, right=1)
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.
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 111
Blocks application definition 09/2007
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
3 - 112 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
Binary faceplate and the standard pins affecting it.
*) Data definition is made in the Setting initial Face Plate values window.
The Signals tab with the standard pins affecting it in the Binary faceplate extension.
*) Data definition is made in the Setting initial Face Plate values window.
The table below contains the standard pins used in a binary tag block
definition.
Input pins Output pins
dis Alarm disable oks Alarm acknowledgement
si1 Signal 1 ou1 Input 1
si2 Signal 2 ou2 Input 2
PAR Application-specific parameter
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 113
Blocks application definition 09/2007
If the following pins are provided with a purpose –based definition
in the tag block definition, then they will display, when active, the
following information text over the faceplate.
Pin Text displayed
dis Alarms disabled
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.
3 - 114 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
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
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 115
Blocks application definition 09/2007
The Info tab in the Sequence faceplate extension.
**) Data definition is made in the Header window.
The table below contains the pins used in the definition of a sequence
tag block.
Input pins Output pins
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)
3 - 116 • Defining faceplates and standard pins for tag blocks Experion PKS
Blocks application definition 09/2007
The texts to be displayed in a Sequence faceplate are defined in the
header definition’s Setting initial Face Plate values window.
Name of field Definition example Explanation
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)
Trend collection (pin,0/1/2) 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
Experion PKS Defining faceplates and standard pins for tag blocks • 3 - 117
Blocks application definition 09/2007
13 Block Simulator / Block
Monitor User Manual
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.
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.3 Print
The Print function is not in use.
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.
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 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
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 window can also be used to define the presentation form for the
pin data.
3 - 124 • Block Simulator / Block Monitor User Manual Experion PKS
Blocks application definition 09/2007
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.
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.
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.
The Cancel push button closes the window without saving the
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.
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