Application & Control Module Guide
Application & Control Module Guide
Issue 9
January 2018
HA084012U003
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Contents
HA084012U003 Contents
Issue 9 January 2018 Page Contents - i
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Contents HA084012U003
Page Contents - ii Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
CHAPTER 1 INTRODUCTION
This manual describes the Application Modules and Control Modules available within the LIN environment. These
control modules can be used in conjunction with existing LIN blocks to perform a wide range of control tasks. This
manual consists of,
Application Module details
Control Module details
Application modules can be utilised for specific activities such as combustion control, load management and pump set
control.
Control Modules consist of common devices such as Controls, Motors and Valves.
HA084012U003 Chapter 1
Issue 9 January 2018 Page 1 - 1
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
DG_IN
CloseLS
DG_IN
CloseLS
AN_CONN
Interface
DG_IN
CloseLS
ACTION DG_OUT
DG_IN MyValve Demand
OpenLS
Compound
Auxiliary
Logic
The following table details some of the advantages these module have to offer.
Chapter 1 HA084012U003
Page 1 - 2 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
1.2.2 Faceplates
Faceplates provide an operational summary of the Application Module or Control Module in the form of an instrument
faceplate and may allow some operator interaction with the device. Faceplates may be displayed on the supervisory
computer as a sub-window or be placed directly onto a mimic graphic at configuration time.
All faceplates are based on a generic display.
Device tagname
DATADATAD
Mode.
AUTO
Auto, Manual, Maintenance
PV ###.#
Device Status Area
Read Out/Device state.
Assigned to analogue or
digital point.
Bargraph
(If applicable)
∧
Soft buttons
∨ Interactive Area
DATADATAD
Device description
HA084012U003 Chapter 1
Issue 9 January 2018 Page 1 - 3
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
If the current user is logged into a sufficiently privileged account and the CONFIRM - Alarm Reset Request
button is confirmation enabled, then a confirmation message dialog is
CANCEL
displayed. Each soft button may be individually configured to display a
CONFIRM
confirmation prompt or take immediate action.
The operation is only performed if the user first selects CONFIRM and
then single clicks the Enter soft button. Selection of the CANCEL option,
no option selection or a single click to the Cancel soft button results in no
operation being performed.
OK Cancel
OK
The soft buttons follow the standard Windows convention of being START
‘Greyed Out’ when not available. A single click to a ‘Greyed Out’ soft
Active action soft button
button has no effect.
START
Inactive (Greyed Out)
action soft button
1.2.5 Icons
An icon is a graphical object which is configured on a supervisory
computer mimic and linked to a single module. The icon displays key M
information about the current status of a device.
The icon tags are configured as two lines of text. The tags may be hidden
LCV
on a per mimic basis to reduce complexity. 100
Each icon provides a mechanism to display the control module faceplate Selection of the upper part of the
icon activates the appropriate
and engineer page. engineer page of the device
LCV
100
Chapter 1 HA084012U003
Page 1 - 4 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
DBase
Alarms
Name of LIN Instrument Block Type Each alarm state and
the device is local to Device tag name Module Type priority
Description
40 character description
of device
Other fields contained in engineer page are dependent upon the module type.
Each field in a module engineer page is assigned to one of the three security levels, which define the level of operator
interaction, if any, of the field. This assignment is fixed for all instances of the module,
Read only. These fields cannot be altered from the engineer page.
LIN Operator Access. These fields may be written to by users whose accounts contain either the ‘Eurotherm
LIN Operator Access’, ‘Eurotherm LIN Supervisor Access’, or ‘Eurotherm LIN Engineer Access’ application
features. The fields are read only to all other users.
LIN Supervisor Access. These fields may be written to only by users whose accounts contain ‘LIN Supervisor
Access’ application feature. The fields are read only to all other users.
The engineer page also contains a faceplate for the device. The faceplate is loaded dynamically from the file whose name
corresponds to the module ‘FpltType’ field. If this file is not present the default faceplate is loaded.
HA084012U003 Chapter 1
Issue 9 January 2018 Page 1 - 5
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
1.2.7 Compatibility
Configuration of the Application Module or Control Module into a LIN instrument database requires LINtools
Engineering Studio. This is because this version of LINtools includes a MAKE dialog that can include new groupings of
templates, e.g. Valves, Motors etc.
To place a module LIN block using the LINtools,.
Make an appropriate header block for the target instrument as usual e.g. ‘Tactician’, ‘T800’, or ‘Eycon-10’
Select MAKE from the LINtools menu bar
Select CtrlModules as the Target
Select the required Category (e.g. Valves)
Select the appropriate Template (e.g. Vlv1In)
Place, drag and drop, on the work sheet
Full support for Application Module and Control Module LIN blocks is available in the following instruments.
Instrument Version
If a database were built with five ‘BigValve’ blocks and seven “BigMotor” blocks, the memory consumed would be 2245
+ 1896 + 5x97 + 7x113 = 5417 bytes. To get a total database size the instance sizes of the header and any other blocks
used would have to be added to the total figure.
BigValve 2245 97
Chapter 1 HA084012U003
Page 1 - 6 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
It is required to force a pump to stop on detection of a low flow. This could be achieved using a control module interlock.
However, further measures must be taken to allow the pump to restart following a low flow detection. This is necessary
because during starting there will be a low flow detected which would then activate the interlock causing the pump to
stop. The desired functionality is achieved using LINtools.
Add a DG_IN, an AND block and a PULSE
block and name them ‘LowFlow’, ‘SetInlk’
DG_IN
and ‘DsblInlk’ respectively.. OpenLS Mtr3In DG_OUT
MyPump Demand
Connect the ‘Out’ of ‘Low Flow’ to the
‘In_1’ of ‘SetInlk’. This asserts ‘SetInlk’ DG_IN IntlockP
when low flow is detected provided the CloseLS
other conditions are conducive. Out In_3 In
It is required that a discrepancy alarm be self-resetting such that no operator reset is required before being permitted to
re-start a pump following a trip. The desired functionality is achieved using LINtools.
Connect from the ‘Out’ field of ‘AutoRst’
DG_IN
to the ‘Reset’ field of ‘MyPump’. This OpenLS Mtr3In DG_OUT
resets the ‘Discrepancy’ alarm when MyPump Demand
‘AutoRst’ is asserted. This removes the
DG_IN
need for an operator to reset the module. CloseLS StateAct. Status.
Connect from the ‘Status.Discrepancy’ Stopped Discrepancy
HA084012U003 Chapter 1
Issue 9 January 2018 Page 1 - 7
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Example 3
It may be required to force a valve closed on a hardware fault detection. This is not an inherent function of any of the
standard control modules. However, the Vlv2In block does include a hardware alarm that is raised if any bit in the
‘Hardware’ bitfield is set and also includes interlocks to force the demand to a given position. The desired functionality
is achieved using LINtools.
Connect each Hardware alarm in the
DG_IN and DG_OUT blocks to the
‘Hardware’ bitfield in the module. This Hardware
ensures that if a DG_IN block detects a
hardware fault it will cause the Hardware DG_IN
OpenLS Vlv2In DG_OUT
alarm to be raised in ‘MyValve’. MyValve Demand
Set the ‘Hardware’ alarm fields to the IntlockP
DG_IN Alarms.
desired priority. An alarm priority of zero CloseLS Hardware
disables the alarm and, hence, prevents
this configuration from functioning
correctly.
Connect from the ‘Hardware’ alarm of ‘MyValve’ back in to the ‘IntlockP’ field of ‘MyValve’. This causes the
primary interlock to be asserted when the ‘Hardware’ alarm is raised.
Set the ‘InlkValP’ parameter of ‘MyValve’ to ‘FALSE’. This ensures that, when the primary interlock is
asserted, the control module demand is set FALSE and, hence, the valve is closed.
Chapter 1 HA084012U003
Page 1 - 8 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Example 4
It is required to change the Valve Icon dynamo such that the colour is black for Closed, red for Open and grey at other
times. The desired functionality is achieved using the T3500 Draw package.
Paste down the required dynamo.
Using the ‘Dynamo’ menu, select ‘Convert to Objects’.
Double click the icon and change the foreground colours as desired. The presented dialog lists the colour for
each of the enumerations of the ‘State’ field, e.g. for a valve the values 0, 1, 2, 3, 4 and 5 correspond to the
states Open, Closed, Opening, Closing, LSFault and Unknown respectively.
2 Current Alarm
3
Threshold
4 Add...
5
Modify...
OK Cancel Help
HA084012U003 Chapter 1
Issue 9 January 2018 Page 1 - 9
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Example 5
When using control modules to interface with plant devices requiring pulsed outputs, it is sometimes desirable after a re-
download of the database to have the device state match the demand.
This is achieved by setting the Options.FrcPulse’ bit to True in LINtools Engineering Studio. When the database is re-
downloaded and during its first scan, a pulsed output is transmitted to the plant device making its state match the control
module demand.
Note: This implementation is not recommended for systems requiring plant devices to stay put after a database re-
download. When using the RaiseLwr control module in a T640, bear in mind that if the travel time for the
control device is, for example, equal to 12 seconds and the loop scan time is 420 milliseconds, the maximum
achievable accuracy can be slightly greater than 0.42* 100/12, i.e. 3.5% at best. Better resolution can be
achieved with slower control devices. The RaiseLwr application module includes an ErrLim field (deadband)
which can be set to a value such that hunting is stopped.
Chapter 1 HA084012U003
Page 1 - 10 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
1.3.1 TagName
This is the user-entered (16-character max.) block Tagname (default ‘NoName’), which identifies and distinguishes the
block from other blocks of the same Type. Tagname appears as a label on the block icon, below its Type identifier. The
Tagname is usually related to the LIN Name unless it exceeds 8 characters, but can differ entirely by changing the Tag
settings configuration using View > Options > Settings > Tags, in LINtools Engineering Studio.
Note: A Strategy cannot be saved unless the TagName has been entered for all blocks in the LIN Database.
1.3.2 Type
This read-only field shows the Template Function block category mnemonic, e.g. AN_IP, PID, SIM, etc. which also
appears as a label on the block icon, above its Tagname. The remaining chapters in this manual are related to block type.
1.3.3 Task
This defines the Task in which this block will be run. Each task number corresponds to a specific repeat rate so all blocks
assigned to this Task number are updated at the interval defined by the relevant ‘Period ms’ parameter.
Note: In a cached block, Dbase specifies the name of the remote LIN Database containing the ‘real’ block.
‘Local’ means that this block operates in the LIN Database in this Instrument.
‘Layer’ indicates that the block is local to the base.dbf in this LIN Database, but is on another layer and is referenced
only to make connections.
‘Remote’ means that this block operates in a LIN Database in a LIN Instrument at a different LIN Node address. This
remote database is referenced to gain access to field values and to make connections. When selected, Dbase and Node
Address parameters become available.
1.3.6 Rate
This is used to defined the minimum update rate (cycle time in milliseconds) of either a single or a group of remote
(cached) function blocks, at which an individual cached block is transmitted across the LIN. The default is 10ms
minimum, i.e. 100Hz maximum. Rate can be set between 10ms and 64s. These rate values are minimum update times
only, and heavily loaded networks may not be able to attain the faster update rates.
Note: For the system to run correctly, a database of the selected name must reside at the specified node, and must
contain a corresponding real block of the same type as the local cached block.
HA084012U003 Chapter 1
Issue 9 January 2018 Page 1 - 11
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
1.4 ALARMS
This field displays the name of the most significant alarm in the block (most significant/Combined Alarm is defined
below). Alarms can also be subject to a suppression condition, refer to the Alarm Suppression User Guide, HA030272.
The Alarms field also accesses a window with three columns - Name, Value, and Priority. The Name column lists the
names of all the block alarms, e.g. Software, Hardware, etc. The Value column displays for each current alarm condition
a message dependant upon ‘Alarm Priority Number’ setting as follows, ‘In Ack’, ‘In Unack’ or ‘Out UnAck’ where ‘In’
indicates an active Alarm condition and ‘Out UnAck’ indicates an Alarm that has cleared awaiting Acknowledgement.
By ‘right-clicking’ in this field, unacknowledged Alarms can be Acknowledged. The Priority column shows the user-
specified priority number for each alarm and is the only read/write field in the Alarms window.
NOTE: In instruments without integral displays, the Alarms window can be seen using the Terminal Configurator
attached to the instrument via Ethernet (ELIN), via a block cached in a display-type instrument (e.g.
Eycon™ 10/20 Visual Supervisor) or via ELIN on a PC running LINtools’ ‘Connect’ facility.
1.4.2 Priorities 1 to 5
Specifies ‘self-acknowledging’ alarms. For these, the ‘In Ack’ message appears when the alarm condition occurs, and
disappears when the alarm has cleared without the need to acknowledge the alarm.
1.4.3 Priorities 6 to 15
Specifies ‘acknowledging’ alarms. For these the ‘In UnAck’ message appears when the alarm condition occurs. To
acknowledge the alarm, ‘right-click’ in the field and select ‘Acknowledge’ from the drop down menu and the field now
displays ‘In Ack’. When the alarm condition clears the ‘In Ack’ message disappears. However, if the alarm condition
clears and the Alarm has not been acknowledged (‘In UnAck’), the ‘Out UnAck’ message appears indicating that the
Alarm has cleared but is awaiting acknowledgement.
Note: For certain legacy instruments, priorities 11 to 15 set a special bit in the Configuration (Header) block and
activate a hardware alarm relay. (Not supported in current instruments.)
1.4.4 Software.
All LIN function blocks have a Software alarm (and a Combined) alarm, as a minimum and cannot be suppressed. A
Software alarm (default priority 1) is generated upon sumcheck failure in a block, i.e. corruption of its database. For
cached, S6000, and TAN blocks, failure of communications to the principal block also activates the alarm
1.4.5 Hardware.
A hardware alarm is generated when any of the bits in the Status parameter are set, e.g. in the event of a power
interruption, incorrect module type, hardware fault, etc.
A hardware alarm also causes the respective I/O module LED to turn off, located at the top of each module. Also any
other relevant LEDs fitted to a module will also indicate a Hardware fault condition, e.g. AI2 module.
Chapter 1 HA084012U003
Page 1 - 12 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
1.4.7 Combined.
All blocks have a Combined alarm (and a Software) alarm, as a minimum. A Combined alarm is generated as a copy of
the most significant alarm in the block and inherits the same Value message and Priority number. Consequently the name
of this most significant alarm is displayed in the Alarms field of the Specification menu.
When several alarms are active, the most significant alarm is chosen in accordance to the following list of attributes:
1. Any unacknowledged Alarm is chosen in preference to any Acknowledged Alarm.
2. If there is more than one Alarm as described in step 1 above, then the Alarm with the highest priority number
is chosen.
3. For Unacknowledged Alarms only; If there is more than one, then alarms that are currently active are chosen
in preference to those Alarms currently not active.
4. If there is more than one Alarm (Acknowledged or Unacknowledged) with the same priority number, then the
lowest numbered alarm (highest/first position in the alarms field list of names) is chosen.
HA084012U003 Chapter 1
Issue 9 January 2018 Page 1 - 13
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Chapter 1 HA084012U003
Page 1 - 14 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
HA084012U003 Chapter 2
Issue 9 January 2018 Page 2 - 1
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Chapter 2 HA084012U003
Page 2 - 2 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
IB_PLI SFC_CON
PRO1C1 RE6010AH
SFC_DISP
DE6010AH
To/From
Phase Controller IB_PLI.LoadPhas to
(InBatch, LIN Sequence, SFC_CON.Load and SFC_MON
ME6010AH
or User Screen) SFC_CON.Run
The block is designed to operate with the Wonderware InBatch software, but can also be executed from any other
Phase Controller, e.g. an SFC or User Screen. InBatch software is used to control and manage the Batch process
(Recipe).
This block is an interface between any Phase Controller, i.e. InBatch software on the Supervisory Control And Data
Acquisition, SCADA system, and the Sequence (SFC) of the strategy in the instrument. It is connected to and from
specific fields in the SFC_CON block to provide seamless control and management of the Batch in progress.
Note An SFC is linked to a FBD via the SFC_CON block. The SFC_MON block and SFC_DISP block are
optional but provide online monitoring and runtime control, display and monitoring of a remote SFC
respectively.
A Batch is a product of a system derived from an individual Phase or a combination of Phases produced from a recipe
running on a unit. A recipe is a list of ingredients or steps used to create the product. For example, a bakery may have
a basic cookie dough recipe that lists all of the ingredients required to make plain cookies and all of the optional
ingredients such as nuts, fruit, and chocolate chips, that can be added to the basic recipe to make various kinds of
cookies. In a steel mill, a recipe might be a collection of machine setup parameters. For batch processors, a recipe
can be used to describe the various steps in the batch process. Recipe values can be configured using the A0 to A15
(floating-point variables), I0 and I1 (Signed long integer variables) and the Word0 to Word5 (16-bit digital variables)
fields.
Each IB_PLI block used in the database provides an interface to each Phase relating to a specific SFC generated from
the Shell PLI (Phase Logic Interface) SFC. The Shell PLI SFC is supplied as a Generic SFC (described in the
LINtools help file) and is used in the generic form. This provides a template for the repeated use of a configured Phase
but can be copied and edited to suit each individual Phase.
IMPORTANT Only add the logic required to provide Interlock, Critical Alarm, Running, and Held control to the
SFC as new Actions, but do not edit any Step name in the Sequence. Edit Transitions to provide
an indication that all configured states have been obtained and the Step is complete.
Examples
Interlock Logic
(*
Action: ZZ_IntLk
This action should have any code required to derive interlocks that are not
derived in the LIN FBD and wired to the PLI Block Interlock inputs. The
result, or results should be assigned into free bits within the PLI block
IntLocks field.
If there are no interlocks then state that and assign false.
ZZ_PLI.Intlocks.Ilk0 := 0;
*)
Cleaning.CurrStep:=65535;
(*
Action: ZZ_CrtAl
This action should have any code required to derive Critical Alarms that
are not derived in the LIN FBD and wired to the PLI Block Critical Alarm
inputs. The result, or results should be assigned into free bits within
the PLI block CritAlms field.
If there are no Critical Alarms then state that and assign 0 (false).
ZZ_PLI.CritAlrm.Bit0 := 0;
*)
Running Logic
(*Set the Set Point for the temperature control in the kitchen tank*)
TIC102.SL:=TempKitch.A0;
Held Logic
LeakTest.Control.Hold:=1;
Desinf.Control.Hold:=1;
Dosing.Control.Hold:=1;
TempKitch.Control.Hold:=1;
Transf.Control.Hold:=1;
Cleaning.Control.Hold:=1;
Ste.Control.Hold:=1;
CIPBATCH.Command:="HOLD";
Phase n
IB_PLI To/From
PRO1C1
SFC_CON
block
Phase n
IB_PLI
PRO1C9 To/From
SFC_CON
block
Note The Select Required button is used to indicate that Tags are required for only the manually selected
Phase Control and Phase Status fields.
Figure 2-2:
RESTART HOLD
Example
Phase 2
Phase 3
Phase 4
Phase 5
Phase 5 IB_PLI
PRO1C9 To/From
SFC_CON
block
Block operation
This block operates by receiving a Start request (Control.Start set TRUE). This loads and starts the SFC specified in
the SFC_CON block in the Interlock state, Status.Intlcked set TRUE after checking all interlocks and writing the
values back to this block. When no interlocks exist (Status.Intlcked set FALSE), the SFC continues to the Ready State
(Status.Ready set TRUE) and on to the Running state (Status.Running set TRUE). If interlocks have not cleared, the
SFC remains in the Interlocked state, allowing the SFC to progress to the Ready state and wait for this block to
indicate that another Start Request (Control.Start set TRUE) is received.
If Hold logic is required, e.g. to stop a product setting in a reactor (some heat and mix) actions can be added to the
Held state. In these cases, the Running logic in this block may have to record what Step was occurring so the Held
logic can determine the next function. Similarly, the Hold logic may have to record what Step was occurring to
provide a position to re-start as determined by CurrStep, NextStep and ReStStep (re-start step), allowing the Phase
to continue until it is complete, or Aborted, Control.Abort set TRUE.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Reset ABORTED
Buttons. Bitfields providing control of the current Phase via a user interface.
Btn1, Btn2. These bitfields can be linked to User Screens in a visualisation instrument or a SCADA system
to provide additional button control of the Phase.
CritAlrm. Bitfields that can be assigned to up to 16 variables that are external to the database and critical to the
Phase.
Alm0 to Alm15. If any bitfield is set TRUE the current Phase enters HOLD mode.
Intlocks. Bitfields that can be assigned to up to 16 variables that are external to the database and disable the Phase
operation.
Ilk0 to Ilk15. TRUE, if set by the assigned variable. If any bitfield is set TRUE the Phase will not start.
Status. Bitfield used to indicate the Phase status.
Ready. TRUE, shows the Phase is ready to run. This will set FALSE if any external variables assigned to
the Intlocks bitfields are TRUE.
Running. TRUE, shows the Phase is in operation.
Held. TRUE, shows the Phase is frozen at the current position.
Done. TRUE, shows the Phase has completed successfully.
Aborted. TRUE, shows the Phase was manually terminated.
Intlcked. TRUE, shows the Phase could not start because variable external to the database have set at least
one Intlocks bitfield TRUE.
eStatus. (Ready/Running/Held/Done/Aborted/Intlckd). Enumerated version of the Status bitfields. These can be
used to display the current state on a visualisation instrument or SCADA system, see Status.
UnitCtrl. Bitfield used to control a unit connected to this block. The unit is specified by the recipe. A sequence of
Phases create a recipe that is run in a Batch on a Unit.
Hold. Set TRUE to freeze the unit at its current position.
ReStart. Set TRUE to restart the unit from the Hold mode
Abort. Set TRUE to terminate the Batch running on the unit.
LoadPhse. Set TRUE to load the Phase SFC. Wire this to Load and Run of the SFC_CON block in the database.
LoadTim. Used to configure the time limit allowed to load the Phase SFC called by the SFC_CON block. If this
period is exceeded Alarms.LoadFile is set TRUE.
LoadTmr. Shows the time remaining until the T
Alarms.LoadFile set
TRUE if LoadTmr
Phase has been loaded. If this count exceeds the Status.Ready
exceeds LoadTim
time configured in LoadTim, Alarms.LoadFile is F
set TRUE. T
Control.Start
F
LoadErr. Shows the status of the Phase called
T
by the SFC_CON block. TRUE shows the Phase LoadPhas LoadTmr
is not loaded, set FALSE when the Phase has F
loaded. Normally this will be wired from the T
LoadErr
SFC_CON Alarms.Combined bitfield to assert an F
alarm in this block.
LoadTim Phase loaded
Time
A0 to A15. 16 (sixteen) floating-point variables that can be used as recipe values for the Phase. These can be
inputs or outputs via the strategy.
I0 to I1. 2 (two) signed long integer variables that can be used as recipe values for the Phase. These can be inputs
or outputs via the strategy.
Word0 to Word5. 6 (six) Word fields containing 16-bit digital variables, Bit0 to Bit15, that can be used as
recipe values for the Phase. These can be inputs or outputs via the strategy.
Bit0 to Bit15. Individual 16-bit digital variables per Word field.
HA084012U003 Chapter 3
Issue 9 January 2018 Page 3 - 1
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Chapter 3 HA084012U003
Page 3 - 2 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Deviatn Compare
+ HiHi
Hi
PV Hysteresis
HiDev
TrueCond
LoDev
Hyst Lo
LoLo
SetInAlm
AlmOnTim
Compare
Alarms
8
CurrCond HardwrTmr Hardware
0 LastCond HiHi
AlmOfTim
Hi
DisableA HiDev
DisableB LoDev
Lo
LoLo
Input
The AN_ALM_2 block generates HiHi, Hi, Lo and LoLo Absolute alarms, Hi and Lo Deviation alarms, a Hardware
alarm which could be used for sensor health and finally, a general purpose Input alarm. An adjustable hysteresis band
is provided common to the absolute and deviation alarms. All alarms have On and Off separately adjustable delays.
Each type of delay and therefore its associated delay value is common to all alarms. Each alarm can be masked
(turned off) by either one of two available Disable bits.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
DisableA, DisableB. Alarm disabling (masking) fields. A TRUE on any input turns off the named alarm. If
unacknowledged, the alarm will still require acknowledging after it has been disabled. DisableA and DisableB
operate in an ‘OR’ fashion such that a TRUE in either disables the corresponding alarm.
Param1, Param2. Optional parameters. Associate additional floating-point data with the block.
Alarms.
Software. Sumcheck error in block’s RAM data.
EvalFail. Evaluation failure in block’s internal logic.
Hardware. Raised when the field Options.SetHwAlm is TRUE. This alarm is intended to allow the
associated I/O point failure to be flagged. Typically connected from the I/O block’s Combined alarm with the
I/O block’s Hardware and OutRange alarms enabled.
HiHi. Raised when PV is greater than HiHi. It will not clear until PV has fallen below HiHi by more than the
hysteresis Hyst.
Hi. Raised when PV is greater than Hi. It will not clear until PV has fallen below Hi by more than the
hysteresis Hyst.
HiDev. Raised when Deviatn is greater than HiDev. It will not clear until Deviatn has fallen below HiDev by
more than the hysteresis Hyst.
LoDev. Raised when Deviatn is less than LoDev. It will not clear until Deviatn has risen above LoDev by
more than the hysteresis Hyst.
Lo. Raised when PV is less than Lo. It will not clear until PV has risen above Lo by more than the hysteresis
Hyst.
LoLo. Raised when PV is less than LoLo. It will not clear until PV has risen above LoLo by more than the
hysteresis Hyst.
Input. Raised when the field Options.SetInAlm is TRUE.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the highest priority active alarm in the block.
HardwTmr, HiHiTmr, HiTmr, HiDevTmr, LoDevTmr, LoTmr, LoLoTmr, InTmr. Alarm delay timers.
Every time the block is processed CurrCond is updated with the current alarm condition based upon PV, SetPoint,
limits and disables. If CurrCond is different from LastCond, the appropriate xxxxxTmr field is loaded with the value
of AlmOnTim (if CurrCond is TRUE) or AlmOfTim (if CurrCond is FALSE). When the timer has reached zero, the
alarm state is updated from CurrCond.
TrueCond. Subfields corresponding to the Alarms subfields show which condition is actually occurring, regardless
of timers and disables.
CurrCond. Subfields corresponding to the Alarms subfields show condition is set after all disables have been taken
into consideration.
LastCond. Subfields corresponding to the Alarms subfields show the status of CurrCond at the previous iteration.
LastAlrm. This subfield shows the latest status the alarms were updated to after the time delays and the disables
have been applied.
Timer Restarted
Implementation notes
If AN_ALM_2 control modules are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 2694 bytes and by 226 bytes for each
instance of the control module.
Alarms
DnStDen
Density HAA Hi
False
MeasDen LAA Lo
A
MeasDen A-B
Dev
Calculate True Dev
MeasDen
False
AlmDev
SetDev
DiffPress
SpHtRat
CalcDen
UpStrTmp
Zline ManDen
True
UpStrPrs MolWt True
True
Mode
True
DerivDen False
False
False
False
RelDen SelCalc SelMan
This block generates an up-stream density for use with the ISO5167O block or the ISO5167V block. It generates
density figures by calculation, allows a live density to be wired in and an overall switch is provided to select the
desired density.
The block assumes that pressure and temperature inputs are in barG and degC, respectively. These are then converted to barA and
K for use in the appropriate calculations.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
HAA, LAA. In use density high and low alarm limits in kg/m3 see Alarms.
Density. Upstream density in kg/m3 derived from any of the four density fields below depending on the block’s
mode. This is intended to be passed to the ISO5167O block type.
ManDen. Upstream density in kg/m3. Can be an Operator entry used during calibration to set the density output
of the block.
CalcDen. Calculated upstream density in kg/m3. This is the result of the calculation below
CalcDen = (UpStrPrs+1.01325)*MolWt / (Zline*R*(UpStrTmp+273.15))
Where R is the universal gas constant (0.0831434 bar.m3/kmol/degK).
DerivDen. Calculated upstream density in kg/m3. This is the result of the calculation below
DerivDen = (RelDen*1.22550)*288.15*(UpStrPrs+1.01325)*Zbase /
((UpStrTmp+273.15)*1.01325*Zline)
MeasDen. This value is used as the measured density in kg/m3. If Options.DnStrDen is FALSE, MeasDen is
equal to LiveDen. Otherwise MeasDen is obtained from the calculation below
MeasDen = LiveDen*((UpStrPrs+1.01325)/
(UpStrPrs+1.01325-DiffPrs/1000))^(1/SpHtRat)
Status. Bitfield showing status of the calculations.
Hi. Follows the status of the Hi alarm. This bit is set and cleared irrespective of alarm priority.
Lo. Follows the status of the Lo alarm. This bit is set and cleared irrespective of alarm priority.
Dev. Follows the status of the Dev alarm. This bit is set and cleared irrespective of alarm priority.
Options. Bitfield for selecting the different operational options of the block.
DnStrDen. Used in the derivation of the measured density, see MeasDen.
AlmDev. Used in the derivation of the deviation alarm, see Alarms.
SetDev. Used in the derivation of the deviation alarm when Options.AlmDev = Ext, see Alarms.
Param1, Param2. Optional parameters. Associate additional floating-point data with the block.
FpltType. Faceplate type. Associates a faceplate type or other alphanumeric string with the block.
Implementation notes
If GasDens control module blocks are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 1574 bytes and by 180 bytes for each
instance of the control module.
P T
DP
FLOW
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
P T
DP
FLOW
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Implementation notes
If ISO5167V custom LIN blocks are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 1812 bytes and by 186 bytes for each
instance of the custom LIN blocks.
PV LoLo Alarm
Lo Alarm
Hi Alarm
PV_Mode HiHi Alarm
HiHiType
a b
Adjusting Hyst
Cal_PV
-999999
Adjusting Alarms
HiHi
AdjMssge CalState
Hi
Hold_PVi Lo
Calibration
LoLo
CalComnd
AdjType AdjValue
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following the
table.
Alarms
Software Block RAM data sumcheck error/network failure T/F
EvalFail Evaluation failure in block’s internal logic T/F
Hardware Hardware alarm T/F
Bad_Cal Bad calibration alarm T/F
HiHi High high alarm (absolute or deviation) T/F
Hi High alarm (absolute or deviation) T/F
Lo Low alarm (absolute or deviation) T/F
LoLo Low low alarm (absolute or deviation) T/F
Input Input alarm T/F
PV_Held Process value held alarm T/F
CalWarng Calibration warning alarm T/F
Combined OR-ing of all alarm bits T/F
Method Reserved for future use. Block’s ST update routine (default = Template) Menu
PV_Mode The PV update source (LiveData/Hold) Menu
PV Process variable EngA
HR Engineering high range EngA
LR Engineering low range EngA
ChainIn Chain input (A)BCD hex
Init An initialise input T/F 1
CritAlm Chained input critical alarm status T/F 2
D
WarnAlm Chained input warning alarm status T/F 4
NewAlmA Chained input new alarm A status T/F 8
NewAlmB Chained input new alarm B status T/F 1
NewAlmC Chained input new alarm C status T/F 2
RsetNewA Chained input reset new alarm A status T/F
C
4
RsetNewB Chained input reset new alarm B status T/F 8
RsetNewC Chained input reset new alarm C status T/F 1
2
B
4
8
Table 3-1: Block parameters
iStatusM Input PV status mask, with bit names matching iStatus ABCD hex
Input PV alarms, normally wired from the associated AI_UIO block Alarms
iAlarms (AB)CD hex
field
OutRange I/O block Out of Range alarm In Alarm status T/F 1
PVError I/O block PV Error alarm In Alarm status T/F 2
D
OCctDel I/O block Open Circuit Delay In Alarm status T/F 4
CharErr I/O block Characterisation Error alarm In Alarm status T/F 8
NotAuto I/O block Not Automatic alarm In Alarm status T/F 1
ModBlock I/O block Module Block alarm In Alarm status T/F 2 C
4
8
iAlarmsM Input PV alarms mask, with bit names matching iAlarms. (AB)CD hex
iOptions Provides options for the processing of the input PV and associated alarms (AB)CD hex
SetHard1 T/F 1
SetHard2 T/F 2
TRUE sets the Hardware alarm D
SetHard3 T/F 4
SetHard4 T/F 8
HoldPV_1 T/F 1
HoldPV_2 A TRUE on any HoldPV_n bit indicates that an external calibration related T/F
to the Input PV, or some other action that invalidates the PV is in progress
2 C
HoldPV_3 and will cause PV_Mode to be “Hold” T/F 4
HoldPV_4 T/F 8
CalState Calibration state (OK/Warning/Bad/Checking/Adjusting) Menu
CalComnd Commands to set the calibration state to control the calibration process (AB)CD hex
StartAdj Start adjusting T/F 1
StartChk Start checking T/F 2
D
SetOk Set state Ok T/F 4
SetBad Set state Bad T/F 8
Restore Restore factory calibration T/F 1
Confirm User confirmation for “2 point” or “3 point” calibration adjustment T/F 2 C
Abort Used to cancel/abort the calibration adjustment process T/F 4
AuditChk Used by the HMI to trigger the logging of an audit check T/F 8
Cal_PV Calibration process variable EngA
Cal_AI Calibration Analogue Input, typically the electrical input EngB
AdjType Calibration adjustment type (Disabled/User/2 Point/3 Point) Menu
AdjMssge Adjustment message to guide the user through the adjustment process
AdjValue Adjustment value, entered by the user during calibration EngA
ExtEnabl External adjustment value enable
ExtValue External adjustment value
a Calibration slope
b Calibration offset
CalDate Calibration date DD/MM/YY
Days Calibration warning interval
DaysLeft Calibration warning days left count down
iPV_Lo Calibration input reading low value EngA
Val_Lo Calibration source low value EngA
iPV_MdUp Calibration input reading mid value (going up, low to mid) EngA
Table 3-1: Block parameters
Note: * Bit-fields marked with an asterisk share the same field names as ThisAlm.
RsetNewA, RsetNewB, RsetNewC. Chained Output Reset New Alarm status. A copy of
ChainIn.ResetNewA/B/C.
Alarms.
Software. Sumcheck error in block’s RAM data.
EvalFail. Evaluation failure. Raised if there is an internal evaluation error in the function block update
method.
Hardware. Raised if any input options bit iOptions.SetHard1 to iOptions.SetHard4 is TRUE or any bit
within iStatus or iAlarms is TRUE and the corresponding include mask bit is TRUE in iStatusM or iAlarmsM
respectively.
Bad_Cal. Bad Calibration. Raised if the user determines there is doubt with the calibration (eg a replacement
transmitter has been installed) and opts to ‘set bad’ calibration. See “Calibration” on page 33 for information
on the Calibration State Machine.
HiHi. The High High process alarm. Raised according to the High High alarm type (HiHiType) of absolute or
deviation when the input is compared to limit HiHi with configurable on-delay time (HiHi_OnT). The alarm is
raised as soon as the limit is breached, but only clears when the alarm value recovers by at least the hysteresis
margin (Hyst). For absolute alarms, the input is PV; for deviation alarms, the input is the calculated deviation
(Deviatn).
Hi. The High process alarm. See HiHi description.
Lo. The Low process alarm. See HiHi description.
LoLo. The Low Low process alarm. See HiHi description.
Input. Follows the state of Options.SetInAlm subject to configurable on-delay time (In_OnT).
PV_Held. Raised when PV_Mode is Hold.
CalWarng. Calibration Warning alarm. Raised when calibration due days (Days) reaches zero to flag a
calibration is due. This does not necessarily mean the calibration is bad, but merely that a calibration check is
due. Note that if the real time clock can’t be read or the calibration date (CalDate) is set to the invalid date
setting (??/??/??), then DaysLeft will be zero and the alarm will be raised.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the highest priority active alarm in the block.
ThisAlm. This Alarm State. A 16-bit subfield with bit names reflecting the state of the like-named alarms as listed
below. These are used in the derivation of critical alarm, warning alarm and new alarm flags. If used, these bits are
usually wired from the block’s own Alarms field (this then takes account of alarm suppression).
Hardware. Hardware “In Alarm” status after alarm suppression.
Bad_Cal. Bad Calibration “In Alarm” status after alarm suppression.
HiHi. High High “In Alarm” status after alarm suppression.
Hi. High “In Alarm” status after alarm suppression.
Lo. Low “In Alarm” status after alarm suppression.
LoLo. Low Low “In Alarm” status after alarm suppression.
Input. Input “In Alarm” status after alarm suppression.
PV_Held. PV Held “In Alarm” status after alarm suppression.
CalWarng. Calibration Warning “In Alarm” status after alarm suppression.
Note: Software, EvalFail and Combined alarms are not included in this list. If Software or EvalFail alarms
are raised then the behaviour of these bits and the associated functionality cannot be defined so their
inclusion is not relevant.
CritAlmM. Critical Alarm Mask. This has one subfield for each alarm that can be included into the critical alarm
status (Status.CritAlm). If the mask bit is TRUE and the alarm is raised (as flagged in ThisAlm) the critical alarm
Note: Normally only one alarm enabled by the mask changes FALSE to TRUE in any database (task) scan,
and so there is a pulse for each FALSE to TRUE new alarm transition and its width is set by the
database execution time. If new alarms included in the mask occur on consecutive scans of the
database, then the bit will remain TRUE for more than one database scan. Similarly, if two new alarms
occur on the same database scan, then only a single New Alarm pulse is generated (ie, output pulses
do not represent a “new alarm count”).
bit being set will raise the Hardware alarm. This allows selective I/O status bits to be included or excluded from the
Hardware alarm.
iAlarms. Input PV Alarms. Normally wired from the associated AI_UIO block Alarms field with bit names as
below.
OutRange. I/O block Out of Range alarm In Alarm status.
PVError. I/O block PV Error alarm In Alarm status.
OCctDel. I/O block Open Circuit Delay alarm In Alarm status.
CharErr. I/O block Characterisation Error alarm In Alarm status.
NotAuto. I/O block Not Automatic alarm In Alarm status.
ModBlock. I/O block Module Block alarm In Alarm status.
iAlarmsM. Input PV Alarms Mask. A 16-bit subfield with bit names matching iAlarms. When a mask bit is TRUE,
the corresponding input alarm bit being set will raise the Hardware alarm. This allows selective I/O alarms to be
included or excluded from the Hardware alarm.
iOptions. This 16-bit subfield provides options for the processing of the input PV and associated alarms.
SetHard1, SetHard2, SetHard3, SetHard4. TRUE sets the Hardware alarm. If SetHard1,
SetHard2, SetHard3 and SetHard4 are all FALSE, iStatus, iStatusM, iAlarms, and iAlarmM determine the
Hardware alarm state. These could be used with I/O being gathered by other means (for example,
communications) rather than AI_UIO blocks to trigger a hardware alarm if the input fails in some way.
HoldPV_1, Hold_PV2, Hold_PV3, Hold_PV4. A TRUE on any HoldPV_n bit indicates that an
external calibration related to the Input PV, or some other action that invalidates the PV is in progress and will
cause the PV_Mode to be Hold. This might be used if two real inputs are being used to form a differential
pressure input and one or both of them are being calibrated.
CalState (Ok/Warning/Bad/Checking/Adjusting). This enumeration defines the calibration state of
the function block. See “Calibration” on page 33 for details of the calibration state machines.
Ok. The last calibration check performed resulted in the user defining the calibration to be “OK” and no
subsequent expiry of the Calibration Warning timer has occurred.
Warning. The calibration state has been set to OK, but the Calibration Warning timer has expired and the
CalWarng alarm has been raised. This state is driven from the “In Alarm” status and so the CalWarng alarm
must be enabled to get a warning indication. This ensures only users who want a warning alarm will receive
the warning state.
Bad. The user has chosen to set the calibration state to Bad in order to flag that equipment should not be used
until a satisfactory calibration check is performed following a transmitter change, for example.
Checking. The user has started a routine calibration check or has completed a calibration adjustment and is
now checking the calibration before choosing to set the stater to Ok or Bad.
Adjusting. The user has started an adjustment. The adjustment process follows the specified adjustment
type, AdjType setting, and automatically moves the user to Checking upon completion.
CalComnd. Provides commands to set the calibration state of the block and so control the calibration process.
Commands are set TRUE by the user, processed if relevant at this time, and cleared FALSE automatically by the
function block. Only one command should be set TRUE at any time; if more than one command it set TRUE, then
all commands are cleared.
StartAdj. Start Adjusting.
StartChk. Start Checking.
SetOk. Set State Ok.
SetBad. Set State Bad.
Restore. Restore factory calibration a=1.0, b=0.0 and clear adjustment settings (iPV_* and iVal_* set to 0.0).
Confirm. Used to advance the “2 Point” or “3 Point” calibration adjustment process as each step is
acknowledged as complete by the user.
Note: The above iPV_Lo, iPV_Hi, Val_Lo, and Val_Hi fields apply to both 2 Point and 3 Point adjustment
types; they are forced to zero for the User adjustment type.
Note The above iPV_MdUp,Val_MdUp, iPV_MdDn, and Val_MdDn fields apply only to the 3 Point
adjustment type; they are forced to zero for the 2 Point and User adjustment types.
Calibration
The VLV3WAY function block provides services to facilitate calibration checking and adjustment. Throughout this
section, the term “calibration checking” refers to the process of verifying the calibration, and “calibration
adjustment” refers to the process of adjusting the calibration constants to comply with calibration standards.
CALIBRATION STATE MACHINE
In a typical system, the function block calibration state machine normally resides in the OK state. The state changes
automatically to Warning when a calibration warning is flagged (if the CalWarng alarm is enabled).
The Adjusting, Checking and Bad states are all selected by the user as part of the calibration process. The user
interacts with preset commands from the subfield bit list of the CalComnd field to drive the calibration process. The
following figure shows an overview of the calibration state machine (the CalComnd subfield name is omitted from
the figure for clarity).
Bad
Set Bad
Warning
When in Adjusting or Checking, the value of PV is not updated and the PV_Mode indicates Hold (the actual input
would be disconnected from the real process during these states). For any other state (Ok, Warning, and Bad), the
PV_Mode indicates LiveData (the actual input would be connected to the real process during these states). This
allows use of the PV_Mode field to remove data from long-term data processing functions at the HMI (mean kinetic
temperature, and averages, for example), when PV_Mode is not set to LiveData.
When the state is Bad, Alarms.Bad_Cal is continuously raised. This alarm only clears under user control on the
transition from Checking to Ok (Set Ok command).
When the state is Checking, no specific calibration actions are undertaken by the function block. Instead, the
Checking state can be reported to the HMI for user information whilst the user performs their site-specific calibration
checks. The reading of calibration PV (Cal_PV) and calibration input (Cal_AI) are useful in this state because the
main block PV is held. In this checking mode, the user can make as many checks as they like, logging some or all
points to the HMI audit trail as desired.
When an adjustment is enabled (AdjType is not Disabled), and a Start adjustment command is issued (StartAdj) has
been requested, the adjustment is handled by the state machine (refer to the next section). No matter how the
adjustment process completes (normal end, or an abort), the state moves automatically to Checking and the user must
follow their checking procedures and then make the choice to “Set Bad”, or “Set Ok”.
CALIBRATION ADJUSTING STATE MACHINE
Calibration adjustment is usually the least used of the calibration states because most calibration checks pass with
the result Ok and adjustment is not required. The calibration adjustment process is used to explicitly flag that changes
are planned and in-progress to the calibration constants (a and b). Calibration adjustment cannot be started if
adjustment is disabled (AdjType is Disabled).
During calibration adjustment, the calibration PV (Cal_PV) is forced to -999999 to indicate it is invalid (it cannot be
sensibly updated when the calibration contents are being changed).
The following state transition figure shows an outline of the calibration adjustment procedure.
Start
2 or 3 Point
User Adjust
Adjust (*)
End
The following figure shows the Adjustment State Machine, which is implemented when AdjType is 2 Point or 3
Point (* in the previous figure).
Always
Confirm
The user enters the Low value read from the validated
Enter_Lo independent measurement point (optionally automatically
copied from ExtValue if ExtEnabl is TRUE).
“3 Point” AdjType?
Confirm
The user enters the Mid point value read from the validated
independent measurement point (optionally automatically
Enter_MdU copied from ExtValue if ExtEnabl is TRUE).
The user enters the High point value read from the
Enter_Hi validated independent measurement point (optionally
automatically copied from ExtValue if ExtEnabl is TRUE).
“3 Point” AdjType?
Confirm
The user enters the Mid point value read from the validated
independent measurement point (optionally automatically
Enter_MdD copied from ExtValue if ExtEnabl is TRUE).
The calculation of the calibration constants depend upon the adjustment type of 2 Point or 3 Point. The block’s PV
is related to the input PV (iPV) and the calibration constants (a and b) by definition by the following equation.
PV = a * iPV + b
Val_Hi
Hi
Val_Lo
Lo
LR
From the above graph, the gradient (a), or slope, is given by:
(Val_Hi – Val_Lo)
a=
(iPV_Hi – iPV_Lo)
Substitution of a point-pair (for example, the low point-pair as used within the block) into the main equation for PV
and rearranging yields the offset (b):
b = Val_Lo – a * iPV_Lo
The following figure shows the three iPVs plotted against the AdjValues.
HR
Val_Hi Hi
Val_Mid Mid
Val_Lo Lo
LR
The point Mid on the graph is the average of Mid Up and Mid Down:
and:
Val_Hi – Val_Lo
a= and b1 = Val_Lo – a * iPV_Lo
iPV_Hi – iPV_Lo
Finally:
Typical wiring connections are shown in the following two tables. The header block’s Status.TmpPFail is typically
wired to the EMS_AN_ALM block’s Options.Init field, as shown in the first table. This would ensure the
Options.Init field is pulsed once at database start to initialise the alarm on-delay timers at start up.
The Warning Alarm, Critical Alarm and New Alarm (x3) status bits (and hence the status chaining - ChainIn and
ChainOut) rely upon the current alarm status being wired back from the block into the ThisAlm field. This
arrangement ensures that any applied alarm suppression is taken into account when these status bits are derived (if
an alarm is suppressed, then it will not be able to set the related status bit). The typical wiring is shown in the
following table.
Typical wiring between the AI_UIO block and the EMS_AN_ALM block is shown in the following table. There are
connections in both directions between the two blocks which should both be assigned to the same task (normally task
3, in a T2550 instrument).
This arrangement of wires allows the EMS_AN_ALM block to act as the main interface block for the sensor point.
Hardware-related alarms and status are copied from the AI_UIO block, and ranging data is passed from the
EMS_AN_ALM block to the AI_UIO block, so there is often no requirement to directly visualise the AI_UIO block
to the operator HMI. The AI_UIO block would typically only be used for diagnostics via LINtools.
HA084012U003 Chapter 4
Issue 9 January 2018 Page 4 - 1
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Chapter 4 HA084012U003
Page 4 - 2 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
DoubleXL Demand
DblXLva
Z/s A
Air_PV A/B A/B
B B
ExcssAir
Z/X +
StchAirA + FxdLoadB
X/s
FuelA_PV
CV_B
MJ/X +
CV_A X
MW HSS + ÷
X
FuelB_SP
MW
+
+ A/B FxdLdFuel
HSS + ÷
CV_B X
FuelA_SP
FuelB_PV
Z/Y
StchAirB + FxdLoadA
This block uses a heat demand to generate remote setpoints, for up to two fuel flow controllers and a combustion air
controller, based on a cross-limiting combustion algorithm.
In manual mode, the heat demand may be set directly by an operator. In automatic mode, the heat demand may be
set by a profiling sequence or a master controller.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
FuelBStt. Current state of fuel B. Input used to determine if the fuel is firing. Used in combination with the current
state of fuel A to evaluate the combustion state. May be input connected or controlled by option bits.
AirStt. Current state of the combustion air. Currently has no effect on the combustion algorithm.
AutoDmnd. Automatic Demand. Controls the demand in Automatic mode.
Claims. Resource Management Claims. Used to request sole control of the control module. The motor resource
may be controlled by up to eight sequences or other control module users.
Acks. Resource Management Acknowledgements. Indicates acceptance of a claim.
FuelDmd. Total fuel heat demand. Calculated from cross-limiting algorithm.
FuelA_SP. Fuel flow setpoint for fuel A. Calculated from cross-limiting algorithm.
FuelB_SP. Fuel flow setpoint for fuel B. Calculated from cross-limiting algorithm.
Air_SP. Combustion air flow setpoint. Calculated from cross-limiting algorithm.
CurHeat. Current total heat. The heat calculated as being currently generated from the current fuel flows.
StchAir. Calculated stoichiometric Air Flow. This is based only on the current fuel flows.
Alarms.
Software. Sumcheck error in block’s RAM data.
EvalFail. Evaluation Failure Alarm. Evaluation failure in block’s internal logic.
hardware. Hardware Alarm. Hardware failure flagged by an input or output block associated with the
motor.
Afault. Fuel A Fault Alarm. The state of Fuel A indicates fault.
Bfault. Fuel B Fault Alarm. The state of Fuel B indicates fault.
TooRich. Combustion Mixture Too Rich Alarm. The current air to fuel ratio is lower than that required by
the cross-limiting algorithm.
BthModlt. Both Fuels Modulating Alarm. The fixed load fuel has had to start modulating because the
modulating fuel could not satisfy the demand.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the highest priority active alarm in the block.
Demand. Heat demand. Maintained demand for the required heat.
ExcssAir. Excess air requirement. Percentage air required in excess of stoichiometric combustion for use in the
cross-limiting algorithm.
Bias. Fuel load, fuel bias. The bias applied between the two fuels when the fixed load fuel needs to modulate to
satisfy the demand.
DblXLval. Double cross-limiting value. The percentage headroom when double cross-limiting is enabled for the
combustion air setpoint to increase above that calculated by the cross-limiting algorithm.
ModDmnd. Modulating fuel heat demand. Required for internal use only. The demand less the current fuel fixed
load value.
FxdLoadA. Fixed load heat demand for fuel A. The heat demand required from fuel A when fuel B is the
modulating fuel and can satisfy its heat demand.
FxdLoadB. Fixed load heat demand for fuel B. The heat demand required from fuel B when fuel A is the
modulating fuel and can satisfy its heat demand.
State. Current state derived from the current state of both fuels.
StateAct. Active state derived from the current state of both fuels. Only one state bit is active at any one time.
Purge. Purge is in progress.
Bth>Fire. Both fuels are firing.
A>StrtB. Fuel A is firing and fuel B is starting.
B>StrtA. Fuel B is firing and fuel A is starting.
A>Fire. Only fuel A is firing.
B>Fire. Only fuel B is firing.
StrtBth. Both fuel A and fuel B are starting.
StrtA. Fuel A is starting. Fuel B is stopped.
StrtB. Fuel B is starting. Fuel A is stopped.
Idle. Neither fuel is starting or firing.
Fault. Both fuels are in fault.
Status. This bitfield shows the status of the control module.
BalSP. Force fuel flow controller SP balance. Pulses high on a demand or fixed load fuel change.
DampenA. Restrict fuel A’s ability to increase. High indicates that the fuel A flow controller should be
limited such that increases in fuel flow setpoint are rate limited. This gives a modulating fuel B time to respond
to load changes before fuel A moves off its fixed load value.
DampenB. Restrict fuel B’s ability to increase. High indicates that the fuel B flow controller should be
limited such that increases in fuel flow setpoint are rate limited. This gives a modulating fuel A time to
respond to load changes before fuel B moves off its fixed load value.
Options. This bitfield allows inputs to control the operation of the control module.
AuDmdTrk. Automatic Demand Track. TRUE forces the automatic demand to track the demand when not
operating in auto or when interlocked.
Avail1, Avail2. Available is allowed. FALSE prevents the block from signalling that it is available for
automatic control.
NtAvail1, NtAvail2. Available is not allowed. TRUE prevents the block from signalling that it is
available for automatic control.
Availble. Available. TRUE when control module is available for automatic control, i.e. in automatic mode and
availability options not prohibitive.
Master. Optional Parameter. Associates additional floating-point data with the control module.
Implementation notes
If CmbnCtrl control modules are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 2882 bytes and by 186 bytes for each
instance of the control module.
1+
DblXLVal X
MW Z/s Y/s
BiasCL - Low X X Air_SP
High
Options.Lambda
Demand
True
False
CV
Vh
÷
StchAir
MW Y/s
÷ ÷ Air_PV
MW
FuelDmnd
1-
X X/s
High ÷ Fuel_SP
Low
+
CV
X/s MW
Fuel_PV X CurHeat
Z/s Y/s
X CurStAir
StchAir ÷ CurExAir
CurLambd
This block is an interface to single-fuel burners and is used to generate setpoint values for air flow and fuel flow
control modules. Fuel flow and air flow feedback signals are applied to analogue input modules, the outputs of which
are wired to the CMBNXLIM block’s Fuel_PV and Air_PV inputs. These inputs are used, together with a Demand
input (typically controlled by the LOOP_PID block), to derive fuel flow and air flow setpoint values. These values
are wired from the block’s Fuel_SP and Air_SP outputs to the PV inputs of the analogue output modules controlling
Fuel flow and Air flow
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
FuelDmd. Shows the total fuel heat demand used to determine Fuel_SP. Calculated from cross-limiting algorithm
and BiasCL (cross-limiting bias). DblXLval is included in the algorithm if Options.DoubleXL is TRUE.
CurHeat. Shows the current total heat. The heat currently being generated from the current fuel flow.
CurStAir. Shows the current Stoichiometric air flow. This is the air flow currently required for ideal combustion.
CurExAir. Shows the current percentage of excess air in the chamber. This requirement is for use in the cross-
limiting algorithm derived from Fuel_PV and Air_PV. Using more air than the Stoichiometric amount in the
combustion chamber increases the chances of complete combustion.
CurLambd. Shows the amount of air flow above or below the Stoichiometric (Lambda) (i.e. the quantity of air in
the combustion process relative to the ideal amount). A Lambda value of 1.0 means that exactly the theoretical
quantity of air needed for complete combustion is present.
Alarms.
Software. Sumcheck error in block’s RAM data.
EvalFail. Evaluation Failure Alarm. Evaluation failure in block’s internal logic.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the highest priority active alarm in the block.
ExcssAir. Shows the Excess air requirement. This is the percentage of air required of air in excess of the
Stoichiometric combustion for use in the cross-limiting algorithm. This is derived from Fuel_PV and Air_PV. If
Options.Lambda is TRUE this value is calculated from Lambda.
Lambda. Shows the Lambda air requirement. This is the ratio of air required of air in excess of the Stoichiometric
combustion for use in the cross-limiting algorithm. A Lambda value of 1.0 means that exactly the theoretical quantity
of air needed for complete combustion is present. If Options.Lambda is FALSE this value is calculated from
ExcssAir. A lambda of >1 means there is more air than required; a lambda of < 1 means there is insufficient air.
BiasCL. Shows the cross-limiting bias. This is the bias applied to prevent small increases in fuel flow from affecting
the Air_SP value, and small decreases in air flow from affecting the Fuel_SP value.
DblXLval. Shows the double cross-limiting value to be applied when Options.DoublXL is TRUE. This is the%
value to which the combustion air setpoint is held back, above that calculated by the cross-limiting algorithm, whilst
demand is increasing, and also the% value to which the fuel setpoint is held back, above that calculated by the cross-
limiting algorithm, whilst demand is decreasing.
CV. Shows the calorific value of the fuel. The units applied to this value must correspond to the units used in
Fuel_SP.
StchAir. Stoichiometric air requirements for combustion of fuel.
Note Air flow and fuel flow calculations must use the same units of measurement.
Fuel_SP. Fuel flow setpoint for fuel. Calculated from cross-limiting algorithm.
Air_SP. Combustion air flow setpoint. Calculated from cross-limiting algorithm.
Options. This bitfield controls the operation of the block.
Lambda. Excess air method control. TRUE enables the value shown in ExcssAir to be displayed in
Lambda. FALSE enables the value shown in ExcssAir to be displayed as a% (percentage).
DoublXL. Double cross-limiting control. TRUE enables the use of the value configured in DblXLval
(double cross-limiting value).
Implementation notes
If CMBNXLIM control modules are included in the configuration, the block is included in the database as a ‘foreign’
template. The runtime database size is increased by a template overhead of 2882 bytes and by 186 bytes for each
instance of the control module.
This block provides an interface to any actuator with two digital inputs, one for ‘Raise’ and one for ‘Lower’. Both
signals are based upon an incremental algorithm from a single set of three term settings. The block state is derived
from limit switches and accumulator value.
In Manual, the block’s output can be adjusted by manually issuing ‘Raise’ or ‘Lower’ signals. If Auto is selected,
the block is automatically updated by the corresponding PID algorithm. Hold, Track and Forced Manual are
available for interlocking purposes. Track and Forced Manual are used to drive the actuator to its limits. There is no
facility to request a Track position other than those.
The RAISELWR block is intended to be used as part of the SETPOINT / 3_TERM / MAN_STAT / MODE
combination of control blocks.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Alarms.
Software. Sumcheck error in block’s RAM data.
EvalFail. Evaluation failure in block’s internal logic.
LSFault. Limit switches indicate actuator is both ‘Open’ and ‘Closed’.
FlToOpen. Actuator has not responded to an ‘Open’ demand. Alarm is latched.
FlToClse. Actuator has not responded to a ‘Close’ demand. Alarm is latched.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the highest priority active alarm in the block.
State (Open/Closed/Opening/Closing/LsFault/StayPut). Current position state. Derived from the
limit switches and the value of Acc.
StateAct. Bitfield indicating the block's active position, i.e. the value of the State parameter. Only one StateAct
bit can be active at one time.
Raise. Real digital output representing the block’s ‘Raise’ demand.
Lower. Real digital output representing the block’s ‘Lower’ demand.
MnRptTmr. Minimum repeat countdown timer in seconds used internally to record a time exceeding the minimum
repeat time MnRptTim.
MnRptTim. Minimum repeat time in seconds. In Auto, reissuing of consecutive output pulses is disabled until a
time greater than MnRptTim has elapsed.
ManPsTmr. Manual pulse countdown timer in seconds. Internally set to record if a manually issued pulse has
exceeded the minimum pulse length MinPulse.
MinPulse. Minimum pulse length in seconds. If |Acc| > MinPulse, a Raise/Lower pulse is started.
TrvlTime. Travel time from 0% to 100% in seconds.
ErrLim. Error limit. dAcc is set to zero if the error magnitude (|Error|) is less than ErrLim.
IntgrLim. Integral limit used to adjust the ratio of integration rate to travel rate, typically set to 1.2. The value
entered in this field should be between 1.0 and 1.4.
Options. Bitfield for selecting the different operational options of the block.
SelTrack. Select track mode. When TRUE, this bitfield forces the output to the ‘Closed’ position if
FrcOpen is FALSE or to the ‘Open’ position if FrcOpen is TRUE. Normally wired in from the associated
MAN_STAT block.
SelHold. Select hold mode. When TRUE, freezes the output at its current position by switching off the
output pulses. Normally wired in from the associated MAN_STAT block.
SelMan. Select manual mode. When TRUE, enables manual adjustment of the output through the option
bits ManRaise, ManLower, RemRaise and RemLower. Normally wired in from the associated MAN_STAT
block.
ForceOP. ForceOP TRUE, causes the block to go into a ‘safe’ position, before manual mode takes over. In
this transient mode, OP adopts a value that depends on the state of FrcOpen. See FrcOpen below. ForceOP is
normally wired in from the associated MAN_STAT block.
FrcOpen. Used to derive the force or track position. ‘Closed’ (OP = 0%) if TRUE, ‘Open’ (OP = 100%) if
FALSE. Normally wired in from the associated MAN_STAT block (SafeHigh field).
ManRaise, ManLower. Used to manually generate Raise/Lower outputs when in manual (e.g. from a
T640 front panel). Internally reset to FALSE.
RemRaise, RemLower. Offers similar functionality as ManRaise and ManLower. Can be used to
manually generate Raise/Lower outputs from a supervisory computer. Internally reset to FALSE.
Implementation note
If RaiseLwr control modules are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 2396 bytes and by 158 bytes for each
instance of the control module.
HA084012U003 Chapter 5
Issue 9 January 2018 Page 5 - 1
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Chapter 5 HA084012U003
Page 5 - 2 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA082375U003). Additional parameter information is given in the Block specification menu section following.
[S] ‘Static’ data, only read if a ‘reset’ occurs in either master or slave. Other data are read/written every comms cycle.
Alarms. There are a number of alarms in this block, six of which (HiHi, Hi, HiDev, LoDev, Lo and LoLo) are
process alarms.
The deviation alarms (HiDev and LoDev) are always derived locally to the block, and use the calculated ‘Deviatn’
value (PV-SP) and the ‘Hyst’ value entered in the relevant configuration field.
If ‘Options.AlmDvLcl’ = True, the four absolute alarms (HiHi, Hi, Lo and LoLo) are derived locally, using the alarm
thresholds entered in the appropriate configuration fields. If ‘Options.AlmDvLcl’ = False, these configuration
values are ignored, and the alarms derived remotely from the 2500 alarm status word.
Software. Sumcheck error in block’s RAM data.
Comms. Asserted if any communications error is detected in the 2500, e.g. Timeout value exceeded.
Config. Asserted if any communication configuration error, or invalid profile is detected, e.g. incorrect Port
configuration.
Reset. For future use.
Snsr_Brk. Asserted if a Sensor Break has occurred (LoopSw.Snsr_Brk or Options.SetSnsrB).
LoopBrk. Asserted if a Loop Break has occurred (LoopSw.Loop_Brk or Options.SetLoopB).
HiHi If ‘Options.AlmDvLcl’ = True the alarm is active when the PV value exceeds the configured value
‘HiHi’and remains active until the PV value falls below (HiHi-Hyst). If ‘Options.AlmDvLcl’ = False, the
alarm status is derived from the 2500 Alarm status word.
LoLo. If ‘Options.AlmDvLcl’ = True the alarm is active when the PV value falls below the configured value
‘LoLo’and remains active until the PV value rises above (LoLo+Hyst). If ‘Options.AlmDvLcl’ = False, the
alarm status is derived from the 2500 Alarm status word.
Hi, Lo. Similar to HiHi and LoLo respectively, but use the configured values for ‘Hi’ and ‘Lo’ instead of
‘HiHi’ and ‘LoLo’.
HiDev, LoDev. Asserted if Deviatn > HiDev, and Deviatn< LoDev, respectively, where ‘Deviatn’ = PV-
SP. The alarms do not clear until Deviatn < HiDev-Hyst, and Deviatn > LoDev+Hyst, respectively. Deviation
alarms are always derived locally and are therefore unaffected by the status of ‘AlmDvLcl’.
EvalFail. Evaluation failure in block’s internal logic.
Combined. Asserted if any alarm is active in the block. Adopts the same status message and priority
number as the block’s highest priority active alarm.
AlarmSW. Loop alarm status word.
Alm1_Act to Alm4_Act. Shows the active status of Loop Alarms 1 to 4 (see note below).
Alm1_Ack to Alm4_Ack. Shows the acknowledgement status of Loop Alarms 1 to 4 (see note below).
Note: ‘Alm1_Act’ and ‘Alm_1Ack’ refer to the ‘HiHi’ alarm. Alm_2Act/Ack refer to the ‘Hi’ alarm.
Alm3_Act/Ack refer to the ‘Lo’ alarm and Alm4_Act/Ack refer to the ‘LoLo’ alarm.
UNITS
Some of the block parameters show their default units as EngA, EngB, EngC and so on.
Changing say, ‘EngA’ for one parameter, immediately changes all other parameters’ EngA entries in the block as
well. This not only speeds up the configuration process, it also ensures that a coherent set of units is used across the
block. For example if a PV’s units were to be entered as ‘mmHg’, then the alarm threhold units (amongst others)
would automatically be changed to ‘mmHg’ as well.
HA084012U003 Chapter 6
Issue 9 January 2018 Page 6 - 1
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Chapter 6 HA084012U003
Page 6 - 2 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
State
DevState Device
FrcStby A A_Run
FrcFail
B_AuDscrp B
A
CgOvrTim
Manual Input
(Direct write to
Demand)
Man/Maint
Demand
AutoDmnd
Auto
Please refer to the schematic. The DutyStby block generates a demand to a pair of on/off motor control modules, by
using one device to act as a standby to the device selected as duty.
In manual mode, the motors may be run as a duty/standby pair or stopped by the operator. In automatic mode, the
motors may be run as a duty/standby pair or stopped by a controlling sequence. The individual motors cannot be
directly started or stopped from this module.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Implementation notes
Note If DutyStby control modules are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 2808 bytes and by 164 bytes for each
instance of the control module.
F F
E Au_Dscrp
A_State E
A_StateD D
C
A_Cpcity
A_State C
B
A_Cpcity Scheduled A_Run B
A_State Algorithm
A_LagPty
A_Cpcity A_Run
A_State
A A
A_LagPty
A_Cpcity A_Run
A_LagPty
A_State
A_Cpcity A_Run
A_LagPty
A_Cpcity
A_LagPty A_Run
Service
A_LagPty
Stop
&
&
OR
+ RnCpcity >
+
<
Hyst +
Manual Input
Ø =0
(Direct write to
Demand)
HystTmr
Man HystTim
Demand
AutoDmnd
Auto
Please refer to the schematic. The DmdSchdl block generates a demand to up to six on/off devices by using a lag
priority to determine the schedule order. Devices may be declared as lead or lag. All available lead devices are run
wherever there is ad demand to be met.
In manual mode, the demand, which ultimately determines the number of running devices, may be set directly by an
operator. In automatic mode, the demand may be set by a controlling sequence or master controller.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Service CD hex
A Service of device A T/F
B Service of device B T/F
C Service of device C T/F
D Service of device D T/F
E Service of device E T/F
F Service of device F T/F
Ø Ø Ø Ø Ø Ø Ø Ø
HystTmr. Hysteresis Timer. Internally set to the hysteresis time before a new device is scheduled to start or stop.
HystTim. Hysteresis Time. The tine in seconds from which the demand must remain above the threshold value for
a new device to be scheduled to start or stop.
OP.
A_Run to F_Run. TRUE runs the specified device.
Status.
A_Runng to F_Runng. TRUE indicates that the specified device state is ‘Running’.
A_Stoppd to F_Stoppd. TRUE indicates that the specified device state is ‘Stopped’.
HystTmng. TRUE indicates that the demand is being tested against the threshold value by the hysteresis timer.
StartReq. The demand is such that a start is required.
StopReq. The demand is such that a stop is required.
Bit15. Optional status bit. Associated Boolean data with the control module.
Options. This bitfield allows inputs to control the operation of the motor.
AfrcLead to FfrcLead. TRUE forces the specified device to assume ‘Lead’ service.
AuDmdTrk. TRUE forces the automatic demand to track the demand when not operating in auto or when
interlocked.
Avail1, Avail2. FALSE prevents the block from signalling that it is available for automatic control.
NtAvail1, NtAvail2. TRUE prevents the block from signalling that it is available for automatic control.
FrcNewLd. TRUE forces a new lead device to start.
CyclLead. Cycle the current service so that the next device assumes ‘lead’ service.
LdMstRun. TRUE selects the lead devices to always run i.e. the lead devices are never stopped regardless
of the demand.
Bit14-Bit15. Optional option bits. Associates additional Boolean data with the control module.
Reset. TRUE resets any of the latched alarms. Internally set FALSE after the reset action.
Availble. TRUE when control module is available for automatic control, i.e. in automatic mode, at least one
device not indicating an automatic discrepancy and availability options not prohibitive.
Claims. Used to request sole control of the control module. The control module resource may be controlled by up
to eight sequences or other control module users.
Acks. Acknowledgements. Indicates acceptance of a claim.
FpltType. Faceplate Type. Associate a faceplate type or other alphanumeric string with the control module.
Allows control modules of this type to be represented by different supervisory computer faceplates.
Param1, Param2. Optional Parameter. Associates additional floating-point data with the control module.
Implementation notes
Note If DmdSchdl control modules are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 3324 bytes and by 174 bytes for each
instance of the control module.
HA084012U003 Chapter 7
Issue 9 January 2018 Page 7 - 1
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Chapter 7 HA084012U003
Page 7 - 2 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Bit15
Invert.Bit15 Mask.Bit15
Bit2
Invert.Bit2 Mask.Bit2
Bit1
Invert.Bit1 Mask.Bit1
Bit0 AND16/ Not_Out
Invert.Bit0 Mask.Bit0 OR16
-1 Not_Out
True True
-1
In.Bit0
False False
Excluded from
AND/OR
Please refer to the schematic in Figure AND16/OR16. This shows one of the 16 block input bits in detail. The
diagram shows that each input bit has a dedicated Invert command and an additional Mask command to include, or
exclude a channel from the block logic.
The 16 bit subfield input bits permit bussed wiring, e.g. between DG_CONN, Action style block types and the Digital
Module (MOD_DI_UIO, and MOD_DO_UIO) block types.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
1
Bit0 to 2
T/F D to A
Bit15 4
8
Invert Individual Invert for each input bit ABCD hex
1
Bit0 to 2
T/F D to A
Bit15 4
8
Mask Individual inclusion command for each input bit ABCD hex
1
Bit0 to 2
T/F D to A
Bit15 4
8
Alarms ABCD hex
Software Block RAM data sumcheck error/network failure T/F
EvalFail .sto file evaluation failure in block’s internal logic T/F
Out Follows OUT T/F
NOT_OUT Follows NOT_OUT T/F
Combined OR-ing of all alarm bits T/F
Out Output T/F
Not_Out Complementary output Secs
Note This is derived from the LIN database when the block is activated.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data, or Network failure.
EvalFail. Embedded .sto file evaluation failure. It is normally recommended that this alarm be enabled to a
alarm priority 6 or more.
Out. This is derived from Out. TRUE, if Out is set TRUE.
Not_Out. This is derived from Not_Out. TRUE, if Not_Out is set TRUE.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
Out. Output from Boolean operation, see table below.
Not_Out. Equal to logical NOT Out. Complementary form of the block output, see table below.
Note The table below shows an example of the resulting outputs, Out and Not_Out, derived using the Invert and Mask
subfields.
Channel 15
Invert_1.Bit0 Mask_1.Bit0
Channel 1
Invert_1.Bit0 Mask_1.Bit0 Out.Bit15
Channel 0
Invert_1.Bit0 Mask_1.Bit0
True True
Out.Bit1
-1
In_1.Bit0 Out.Bit0
False False
True True
-1
Not_Out.Bit0
In_2.Bit0
False False
Excluded from
AND/OR/XOR
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
1
Bit0 to 2
T/F D to A
Bit15 4
8
Invert_1 Individual Invert for each input bit in the first set ABCD hex
1
Bit0 to 2
T/F D to A
Bit15 4
8
Mask_1 Individual inclusion command for each input bit in the first set ABCD hex
1
Bit0 to 2
T/F D to A
Bit15 4
8
In_2 Second set of individual input bits ABCD hex
1
Bit0 to 2
T/F D to A
Bit15
4
8
Invert_2 Individual Invert for each input bit in the second set ABCD hex
1
Bit0 to 2
T/F D to A
Bit15
4
8
Mask_2 Individual inclusion command for each input bit in the second set ABCD hex
1
Bit0 to 2
T/F D to A
Bit15
4
8
Alarms ABCD hex
Software Block RAM data sumcheck error/network failure T/F
EvalFail .sto file evaluation failure in block’s internal logic T/F
Out Follows OUT T/F
NOT_OUT Follows NOT_OUT T/F
Combined OR-ing of all alarm bits T/F
Out Output T/F
Not_Out Complementary output Secs
Note This is derived from the LIN database when the block is activated.
Note The BITWISE_AND16 block has only one Mask field associated with both In_1 and In_2 input bits
because by the nature of this block two masks would be simply ANDed together.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data.
EvalFail. Embedded .sto file evaluation failure. It is normally recommended that this alarm be enabled to a
alarm priority 6 or more.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
Out. 16 Output bits from Boolean operation, see table below.
Not_Out. Equal to bitwise NOT Out. Complementary form of the block output, see table below.
Note The table below shows an example of the resulting outputs, Out and Not_Out, derived using the Invert_1 and
Invert_2 and Mask subfields.
Date2Err
Earlier
-1 NtErlier
Later
-1 NotLater
DateOut Equal
Date1
Compare -1 NotEqual
Date1 = Date2
Date1 > Date2
Earlier
Date1 < Date2
Date2
-1 NtErlier
Compare
POSIXout Later
-1 NotLater
Time1
Compare
Equal
Time1 = Time2
Time1 > Time2 -1 NotEqual
Time1 < Time2
Time2
TimeOut Time1Err
Time2Err
Earlier
-1 NtErlier
Later
-1 NotLater
Equal
-1 NotEqual
Please refer to Figure DT_COMPARE-1. This block is similar to the analogue Compare block as it provides a date
and time compare function with outputs for earlier, equal, and later with complementary inverted outputs. It offers
two sets of date and time fields, not linked to the system clock, so that arbitrary dates and times can be compared as
required.
A comparison is made Time1/Date1 relative to Time2/Date2, e.g. if Time1 is 09:12:00 and Time2 is 14:45:12, the
resulting Time comparison would be ‘Earlier’. Each set individually provides the ability to convert between LIN
string forms of date/time and integer forms of the date/time and vice-versa.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Note This is derived from the LIN database when the block is activated.
SourceT1, SourceT2. (Time/HrMinSec/POSIX). Defines the update format for each time set.
When SourceT1 or SourceT2 show Time, the source is continuously derived from Timex, where x is the set number,
and automatically updates Hoursx, Minsx and Secsx on each block execution. If Timex shows ??:??:??,
Status.TimeErrx and Alarms.TimeErrx are set TRUE, and the Hoursx, Minsx and Secsx are forced to -1.
Hoursx Hoursx
TimeOptn.
AplyHMSx
Minsx Minsx
Pulsed
When SourceT1 or SourceT2 show HrMinSec, the source is derived on-demand from Hoursx, Minsx and Secsx
where x is the set number. TimeOptn.AplyHMSx is used to update Timex. If invalid source data is detected, e.g. Secsx
> 59, Status.TimeErrx and Alarms.TimeErrx are set TRUE, Timex shows ??:??:??, and Hoursx, Minsx and Secsx do
not change.
Note When SourceT1 or SourceT2 show POSIX, Hoursx, Minsx and Secsx are set to -1, and
TimeOut.TimexErr sets TRUE. POSIX Combined Date/Time sources are not currently supported.
Note Remember to consider failure modes, i.e. invalid times, relevant to the application, e.g. including the
TimeOut.TimexErr in ‘event’ generation may be useful.
Earlier, Later, NtErlier, NtEqual, NotLater. TRUE identifies how Time1 and Time2 differ, see
Time1Err, Time2Err.
Equal. TRUE when Time1 shows a time equal to that shown in Time2, including secs. This will only set
TRUE for one second, but may never set TRUE if the database execution time exceeds 1 second. Using the
TimeOut.Later allows a maximum of a 1 second delay.
POSIX_1, POSIX_2. Combined Date/Time sets not currently supported.
Alarms. See page 11-6 in the LIN Block Reference Manual.
Software. Sumcheck error in block’s RAM data.
EvalFail. Asserted, if Embedded .sto file evaluation failure, e.g. MOD operator used on non integer
arguments. It is normally recommended that this alarm be enabled to a alarm priority 6 or more.
Date1Err, Date2Err, Time1Err, Time2Err. Asserted, if DateOut.Date1Err, or DateOut.Date2Err, or,
TimeOut.Time1Err, or TimeOut.Time2Err shows TRUE respectively.
Time. Asserted, if TimeOptn.SetAlmTa and/or TimeOptn.SetAlmTb show TRUE.
Date. Asserted, if DateOptn.SetAlmDa and/or DateOptn.SetAlmDb show TRUE.
DateTime. Asserted, if POSIXopt.SetAlDa and/or POSIXopt.SetAlDTb show TRUE.
Combined. Asserted, if any alarm is active in the block. Adopts the same status message and priority
number as the block’s highest priority active alarm.
SourceD1, SourceD2. (Date/DayMonYr/Posix). Defines the update format for each date set.
When SourceD1 or SourceD2 show Date, the source is continuously derived from Datex, where x is the set number,
and automatically updates Daysx, Monthsx and Yearsx on each block execution. If Datex shows ??/??/??,
Status.DateErrx and Alarms.DateErrx are set TRUE, and the Daysx, Monthsx and Yearsx are forced to -1.
When SourceD1 or SourceD2 show DayMonYr, the source is derived on-demand from Daysx, Monthsx and Yearsx
Daysx Daysx
DateOptn.
AplyDMYx
Monthsx Monthsx
Pulsed
where x is the set number. DateOptn.AplyDMYx is used to update Datex. If invalid source data is detected, e.g.
Monthsx > 12, Status.DateErrx and Alarms.DateErrx are set TRUE, Datex shows ??/??/??, and Daysx, Monthsx and
Yearsx do not change.
Note When SourceD1 or SourceD2 show POSIX, Daysx, Monthsx and Yearsx are set to -1, and
DateOut.DatexErr sets TRUE. POSIX Combined Date/Time sources are not currently supported.
Note Remember to consider failure modes, i.e. invalid dates, relevant to the application, e.g. including the
DateOut.DatexErr in ‘event’ generation may be useful.
LeapYr1, LeapYr2. Used internally to validate leap year data in Yearsx when SourceDx shows
DayMonYr. Will always show FALSE.
POSIXopt. POSIX Combined Date/Time conversion and alarm options.
SetAIDTa, SetAIDTb. TRUE sets Alarms.DateTime TRUE
POSIXout. POSIX combined Date/Time compare status.
Note Remember to consider failure modes, i.e. invalid dates and times, relevant to the application, e.g.
including the TimeOut.TimexErr or DateOut.DatexErr in ‘event’ generation may be useful.
Earlier, Equal, Later, NtErlier, NtEqual, NotLater. TRUE identifies how Date1/Time1 differs
from Date2/Time2.
HA084012U003 Chapter 8
Issue 9 January 2018 Page 8 - 1
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Chapter 8 HA084012U003
Page 8 - 2 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Note Older LIN based Instruments may be configured using the T500/T550 LINtools software, refer to the
T500/T550 LINtools Product Manual (Part no. HA 082 377 U999) for detailed information on
configuring structured text actions.
The block provides eight unsigned long integer variables, eight signed long integer variables and 1 (16 bit) ‘word’
field that can be used by the action as either inputs or outputs, and fields specifying the action’s qualifier and
associated qualifier time (where appropriate). A digital input provides the means to enable the action, and the elapsed
time since the action was enabled is available as an output.
The ActUI8I8 block is very similar to the ACTION block, described in the LIN Block Reference Manual and has several identical
parameters.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Note A FALSE-to-TRUE transition on EN is parallel to the activation of a step in a sequence, and a TRUE-
to-FALSE transition is parallel to the step’s deactivation.
UI0 to UI7. Eight unsigned long integer variables that can be incorporated into the structured text defining the
action. These variables can be inputs or outputs via the control strategy.
D. Bitfields containing 16 digital variables, Bit0 to Bit15, that can be incorporated into the structured text defining
the action. These variables can be inputs or outputs via the strategy.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data.
NoAction. Asserted if the block cannot find the action named in ActName.
BadActn. Asserted if an evaluation error occurs during the running of the action.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
T
P (Initial) Run once, rising edge EN
F
T
N (Normal) Run repeatedly, whilst EN TRUE
F
T
L (Limited) Run repeatedly for QualTime after rising edge EN
F
T
D (Delayed) Run repeatedly after delay QualTime till EN FALSE
F
T
E (Event) Run once after delay QualTime
F
T
F (Final) Run once, on falling edge EN
F
QualTime
Time
QualTime. Time value associated with the L, D, and E action qualifiers, with units specified by TimeBase.
QualTime specifies a running time or delay for the action, and operates during the period that the EN parameter is
TRUE, as shown in the figure above.
TimeBase. (Secs/Mins/Hours) Specifies time units for the T and QualTime parameters.
I0 to I7. Eight signed long integer variables that can be incorporated into the structured text defining the action.
These variables can be inputs or outputs via the strategy.
Implementation notes
If ActUI8I8 custom LIN blocks are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 816 bytes and by 170 bytes for each
instance of the control module.
When creating action code for the ActUI8I8 block using ST operators on the 32-bit integer variables, accuracy
(resolution), but not magnitude can be lost.
The unsigned long integers are 32 bits giving a range of 0 to 4294967295, which is 9½ digits of resolution.
The signed long integers are 32 bits giving a range of –2147483648 to 2147483647, which is 9½ digits of resolution.
The floating point number format used is the LIN database is IEEE single precision floating point format giving a
range of approximately ±1E±36 but with only 6½ digits of resolution.
This loss of accuracy when manipulating the signed and unsigned long integers occurs when operators such as * and
/ are executed. When the data is read from the block to be used in operations that may have a non-integer result, the
values are converted internally to single precision floating point format and then back to integers when writing into
the block. Therefore, a test on the full numeric range of the used variables should be carried out to check that the
action code is behaving as required.
Note Older LIN based Instruments may be configured using the T500/T550 LINtools software, refer to the
T500/T550 LINtools Product Manual (Part no. HA 082 377 U999) for detailed information on
configuring structured text actions.
The block provides 15 floating-point variables, 2 (16 bit) ‘word’ fields and 2 (8 bit) ‘byte’ fields that can be either
input or output used by the action, and fields specifying the action’s qualifier and associated qualifier time (where
appropriate). A digital input provides the means to enable the action, and the elapsed time since the action was
enabled is available as an output.
The Act15A3W block is very similar to the ACTION block, described in the LIN Block Reference Manual (Part no.
HA 082 375 U003) and has several identical parameters.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Note A FALSE-to-TRUE transition on EN is parallel to the activation of a step in a sequence, and a TRUE-
to-FALSE transition is parallel to the step’s de-activation
A0 to A7. Eight floating-point variables that can be incorporated into the structured text defining the action.
These variables can be inputs or outputs via the strategy.
Word0 to Word1. Bitfields containing 16 digital variables, Bit0 to Bit15, that can be incorporated into the
structured text defining the action. These variables can be inputs or outputs via the strategy.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data.
NoAction. Asserted if the block cannot find the action named in ActName.
BadActn. Asserted if an evaluation error occurs during the running of the action.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
Qual. (P(Initial)/N(Normal)/L(Limited)/D(Delayed)/E(Event)/F(Final)) The action qualifier. Qual specifies
when the action is to run during the time that the enabling input EN is TRUE, as shown in the figure below.
T
EN F
T
P (Initial) Run once, rising edge EN
F
T
N (Normal) Run repeatedly, whilst EN TRUE
F
T
L (Limited) Run repeatedly for QualTime after rising edge EN
F
T
D (Delayed) Run repeatedly after delay QualTime till EN FALSE
F
T
E (Event) Run once after delay QualTime
F
T
F (Final) Run once, on falling edge EN
F
QualTime
TIme
QualTime. Time value associated with the L, D, and E action qualifiers, with units specified by TimeBase.
QualTime specifies a running time or delay for the action, and operates during the period that the EN parameter is
TRUE, as shown in the figure above.
TimeBase. (Secs/Mins/Hours) Specifies time units for the T and QualTime parameters.
A8 to A14. Seven floating-point variables that can be incorporated into the structured text defining the action.
These variables can be inputs or outputs via the strategy.
Byte0 to Byte1. Two bitfields containing 8 digital variables, Bit0 to Bit7 that can be incoporated into the
structured text defining the action. These variables can be inputs or outputs via the strategy.
Implementation notes
If Act15a3w custom LIN blocks are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 922 bytes and by 170 bytes for each
instance of the control module.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Note A FALSE-to-TRUE transition on EN is parallel to the activation of a step in a sequence, and a TRUE-
to-FALSE transition is parallel to the step’s de-activation.
Word0 to Word31. 32 (thirty-two) Word fields containing 16-bit digital variables, Bit0 to Bit15, that can be
incorporated into the structured text defining the action. These variables can be inputs or outputs via the strategy.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data.
NoAction. Asserted if the block cannot find the action named in ActName.
BadActn. Asserted if an evaluation error occurs during the running of the action.
Combined. Asserted if any alarm is active in the block. Adopts the same status message and priority
number as the block’s highest priority active alarm.
Byte0 and Byte1. Two Byte fields containing 8-bit digital variables, Bit0 to Bit7, that can be incorporated into
the structured text defining the action. These variables can be inputs or outputs via the strategy.
Qual. (P(Initial)/N(Normal)/L(Limited)/D(Delayed)/E(Event)/F(Final)). The action qualifier. Qual specifies
when the action is to run during the time that the enabling input EN is TRUE, as shown in see Figure 8-1:.
QualTime. Time value associated with the L, D, and E action qualifiers, with units specified by TimeBase.
QualTime specifies a running time or delay for the action, and operates during the period that the EN parameter is
TRUE, as shown in see Figure 8-1:.
TimeBase. (Secs/Mins/Hours) Specifies time units for the T and QualTime parameters.
APPLICATION NOTES
This block is designed for use if multiple digital bit sets that must be processed using an identical method. It offers
32 Word (16-bit) and 2 Byte (8-bit) fields that provide 528 digital input and/or output bits. Individually configuring
these bits would rapidly exceed the maximum Action code space.
The following Structured Text examples illustrate the use of Logic operators for performing bitwise functions.
Example 1
(*
Provide a bitwise invert on 16 input bits
Word0 = 16 INPUT BITS
Word16 = 16 INVERTED INPUT BITS
*)
Example 2
(*
Provide a start burner command for each of the 16 burners. Each single burner
is started [Start = True] if the specific burner enabled input is True and the
corresponding burner heat demand is above 10%
Word10 = 16 BURNER ENABLES [TRUE = ENABLED]
Word11 = 16 BURNERS HEAT DEMANDS >10% [TRUE = >10%]
Word16 = 16 BURNER START COMMANDS [TRUE = START]
*)
Function block memory use can be reduced in comparison to the use of multiple discrete Logic blocks, e.g. AND4,
OR4, etc., by configuring Actions using the principles illustrated in the examples. When working with bit sets and
bitwise processing, subfield bussed wiring can provide a fast and efficient way of making connections in the
database.
Implementation notes
If WORD_ACT custom LIN blocks are included in the configuration, the block is included in the database as a
foreign template. The runtime database size is increased by a template overhead of 1284 bytes and by 170 bytes for
each instance of the Action block.
HA084012U003 Chapter 9
Issue 9 January 2018 Page 9 - 1
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Chapter 9 HA084012U003
Page 9 - 2 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Note Older LIN based Instruments may be configured using the T500/T550 LINtools software, refer to the
T500/T550 LINtools Product Manual (Part no. HA 082 377 U999).
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
A Structured Text Action, as generated in LINtools, or as part of a User Screen, can be used to set a defined block
parameter, shown below. This example shows the number ‘1’, sets field TRUE in LINtools, assigned to a defined
block and field, see LINtools Help for Structured Text details.
Tip! In ST expressions, use Assign, :=, to configure a defined field with a specified value. The logical
comparison functions, e.g. = (Equal), < (Less Than), > (Greater Than), <= (Less Than Or Equal To),
>= (Greater Than Or Equal To), <> (Not Equal), is used to compare the result for a particular scenario.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
Note Older LIN based Instruments may be configured using the T500/T550 LINtools software, refer to the
T500/T550 LINtools Product Manual (Part no. HA 082 377 U999).
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
A Structured Text Action, as generated in LINtools, or as part of a User Screen, can be used to set a defined block
parameter, shown below. This example shows the number ‘100’ assigned to a defined block and field, see LINtools
Help for Structured Text details.
bytes.Val1 :=100
Note In ST expressions, use Assign, :=, to configure a defined field with a specified value. The logical comparison
functions, e.g. = (Equal), < (Less Than), > (Greater Than), <= (Less Than Or Equal To), >= (Greater Than Or
Equal To), <> (Not Equal), is used to compare the result for a particular scenario.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
Note Older LIN based Instruments may be configured using the T500/T550 LINtools software, refer to the
T500/T550 LINtools Product Manual (Part no. HA 082 377 U999).
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
A Structured Text Action, as generated in LINtools, or as part of a User Screen, can be used to set a defined block
parameter, shown below. This example shows the time ‘01/07/07’ assigned to a defined block and field, see LINtools
Help for Structured Text details.
dates.Val1 :="01/07/07"
Tip! In ST expressions, use Assign, :=, to configure a defined field with a specified value. The logical
comparison functions, e.g. = (Equal), < (Less Than), > (Greater Than), <= (Less Than Or Equal To),
>= (Greater Than Or Equal To), <> (Not Equal), is used to compare the result for a particular scenario.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
Note Older LIN based Instruments may be configured using the T500/T550 LINtools software, refer to the
T500/T550 LINtools Product Manual (Part no. HA 082 377 U999).
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
A Structured Text Action, as generated in LINtools, or as part of a User Screen, can be used to set a defined block
parameter, shown below. This example shows the number ‘12’ assigned to a defined block and field, see LINtools
Help for Structured Text details.
integers.Val15 := 12;
rcp_line.RecipeNo := integer.Val15;
Note In ST expressions, use Assign, :=, to configure a defined field with a specified value. The logical comparison
functions, e.g. = (Equal), < (Less Than), > (Greater Than), <= (Less Than Or Equal To), >= (Greater Than Or
Equal To), <> (Not Equal), is used to compare the result for a particular scenario.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
Note Older LIN based Instruments may be configured using the T500/T550 LINtools software, refer to the
T500/T550 LINtools Product Manual (Part no. HA 082 377 U999).
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
A Structured Text Action, as generated in LINtools, or as part of a User Screen, can be used to set a defined block
parameter, shown below. This example shows the number ‘1234567890’ assigned to a defined block and field, see
LINtools Help for Structured Text details.
longs.Val15:=1234567890;
rcp_line.RecipeNo := longs.Val15;
Note In ST expressions, use Assign, :=, to configure a defined field with a specified value. The logical comparison
functions, e.g. = (Equal), < (Less Than), > (Greater Than), <= (Less Than Or Equal To), >= (Greater Than Or
Equal To), <> (Not Equal), is used to compare the result for a particular scenario.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
Note Older LIN based Instruments may be configured using the T500/T550 LINtools software, refer to the
T500/T550 LINtools Product Manual (Part no. HA 082 377 U999).
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
A Structured Text Action, as generated in LINtools, or as part of a User Screen, can be used to set a defined block
parameter, shown below. This example shows the number ‘0.00358’ assigned to a defined block and field, see
LINtools Help for Structured Text details.
singles.Val1 := 0.00358
Tip! In ST expressions, use Assign, :=, to configure a defined field with a specified value. The logical
comparison functions, e.g. = (Equal), < (Less Than), > (Greater Than), <= (Less Than Or Equal To),
>= (Greater Than Or Equal To), <> (Not Equal), is used to compare the result for a particular scenario.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
Note Older LIN based Instruments may be configured using the T500/T550 LINtools software, refer to the
T500/T550 LINtools Product Manual (Part no. HA 082 377 U999).
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
A Structured Text Action, as generated in LINtools, or as part of a User Screen, can be used to set a defined block
parameter, shown below. This example shows the phrase ‘Batch 7’ assigned to a defined block and field, see LINtools
Help for Structured Text details.
Tip! In ST expressions, use Assign, :=, to configure a defined field with a specified value. The logical
comparison functions, e.g. = (Equal), < (Less Than), > (Greater Than), <= (Less Than Or Equal To),
>= (Greater Than Or Equal To), <> (Not Equal), is used to compare the result for a particular scenario.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
Note Older LIN based Instruments may be configured using the T500/T550 LINtools software, refer to the
T500/T550 LINtools Product Manual (Part no. HA 082 377 U999).
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
A Structured Text Action, as generated in LINtools, or as part of a User Screen, can be used to set a defined block
parameter, shown below. This example shows that various bits, or complete bytes or words, have been assigned to a
defined block and field, see LINtools Help for Structured Text details.
sub16bit.Val1:=16#F31B;
sub16bit.Val2:=1;
sub16bit.Val3.bit0:=1;
sub8bit.Val1:=16#0F;
sub8bit.Val2:=2#01101011;
sub8bit.Val3.bit0:=1;
Note In ST expressions, use Assign, :=, to configure a defined field with a specified value. The logical comparison
functions, e.g. = (Equal), < (Less Than), > (Greater Than), <= (Less Than Or Equal To), >= (Greater Than Or
Equal To), <> (Not Equal), is used to compare the result for a particular scenario.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
Note Older LIN based Instruments may be configured using the T500/T550 LINtools software, refer to the
T500/T550 LINtools Product Manual (Part no. HA 082 377 U999).
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
A Structured Text Action, as generated in LINtools, or as part of a User Screen, can be used to set a defined block
parameter, shown below. This example shows the time ‘14:00:00’ assigned to a defined block and field, see LINtools
Help for Structured Text details.
times.Val1 :="14:00:00"
Tip! In ST expressions, use Assign, :=, to configure a defined field with a specified value. The logical
comparison functions, e.g. = (Equal), < (Less Than), > (Greater Than), <= (Less Than Or Equal To),
>= (Greater Than Or Equal To), <> (Not Equal), is used to compare the result for a particular scenario.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
widestr24s.Val1 :=”aBcXYz”;
Note In ST expressions, use Assign ‘:=’ to configure a defined field with a specified value.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data or caching error.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Note: It is not possible to enter non-printable characters directly from a data entry window, e.g. using LINtools.
For example <carriage return><linefeed> is only permitted when encoded as $R$L.
Example
A Structured Text Action, as generated in LINtools, or as part of a User Screen, can be used to set a defined block
parameter, shown below. This example shows assignment of the text ‘xyz’ and includes an ‘STX’ and ‘ETX’
character. See LINtools Help for Structured Text details.
byteseq48s.Val1 :=”$02xyz$03”;
Note: In ST expressions, use Assign ‘:=’ to configure a defined field with a specified value.
Alarms. See section 1.4 of this document(Control Modules User Guide, HA084012) for a general description of
the Alarms field.
Software. Sumcheck error in block’s RAM data or caching error.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the block’s highest priority active alarm.
HA084012U003 Chapter 10
Issue 9 January 2018 Page 10 - 1
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Chapter 10 HA084012U003
Page 10 - 2 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Disable OnDelay
Compare InitLast
In CurrCond InxTmr
Out
LastCond
OffDelay Initial Not_Out
The DGDELAY8 block generates delayed outputs. The block allows eight digital inputs to be delayed by use of two
- On and Off - separately adjustable delays. Each type of delay and therefore its associated delay value is common to
all alarms. Each alarm can be masked (turned off) by a corresponding Disable bit. A Not_Out field is also available
to provide a complementary delayed output.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
In0Tmr to In7Tmr. Delay timers. Every time the block is processed Current is updated with the current condition
based upon In and disables. If Current is different from Last, the appropriate InxTmr field is loaded with the value of
OnDelay (if Current is TRUE) or OffDelay (if Current is FALSE). When the timer has reached zero, the output is
updated from Current.
Current. This subfield shows which input is set after all disables have been taken into consideration.
Last. This subfield shows the status of Current at the previous iteration.
Out. This subfield shows the output status after the time delays and the disables have been applied. If the
corresponding input has changed state before the associated timer has elapsed, the InxTmr field is loaded with the
opposite delay value and the timing is restarted.
Timer Restarted
T
Current F
T
Out
F
Implementation notes
If DGDELAY8 control modules are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 1800 bytes and by 154 bytes for each
instance of the control module.
CtlFpAA
HA084012U301
Issue 2
CtlFpAB
HA084012U302
Issue 2
CtlIcnAA
HA084012U303
Issue 2
CtlIcnAB
HA084012U304
Issue 2
Table 11-1: Supported block permutations
HA084012U003 Chapter 11
Issue 9 January 2018 Page 11 - 1
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Chapter 11 HA084012U003
Page 11 - 2 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
HA084012U003 Chapter 11
Issue 9 January 2018 Page 11 - 3
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Chapter 11 HA084012U003
Page 11 - 4 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Mode
Manual, Maint, Auto XCV1ØØ
MANUAL ALM
Open
Device State Device Interlocked
Open, Closed,
39.6
Unknown, LSFault Interlocked
Hardware Fault
Limit Switch Fault
Alarms
Discrepancy
Faceplate Template
Hardware Fault Hardware
Limit Switch Fault LSFault
Discrepancy Discrep
Soft Buttons
Auto = A
Manual = M
RESET
Reset = R
A
M
Configuration
Dynamo Properties
Property Function
Enter Tag: Specifies the supervisory computer node and control module tag.
Specifies the security area that the operator must have access rights to in
Enter Security Area:
order to be able to use the soft buttons. String must be in quotation marks.
Specifies the soft buttons for which a confirmation prompt is required.
Enter Prompt String: Contained within quotation marks are the key letters for each button where
confirmation is required.
Table 11-1: Dynamo Properties
Mode
Manual, Maint, Auto XCV1ØØ
MANUAL ALM
TRUE
Device Interlocked
Demand
True, False
Interlocked
Hardware Fault
Discrepancy
Alarms
Faceplate Template
Hardware Fault Hardware
Discrepancy Discrep
Soft Buttons
Start = S
Stop = P
Auto = A RESET
Manual = M
Reset = R A START
M STOP
Configuration
Dynamo Properties
Property Function
Enter Tag: Specifies the supervisory computer node and control module tag.
Specifies the security area that the operator must have access rights to in order to be
Enter Security Area: able to use the soft buttons. String must be in quotation marks.
Specifies the soft buttons for which a confirmation prompt is required. Contained
Enter Prompt String: within quotation marks are the key letters for each button where confirmation is
required.
False Text: Specifies the text that appears on the stop soft button.
True Text: Specifies the text that appears on the start soft button.
Table 11-1: Dynamo Properties
Background
XISM Blue = Maintenance mode
Transparent = Normal
Line 1 100
Line 2
This icon is available in a number of orientations. These are collected within a common dynamo library, ICN_CT.
The dynamos are named as indicated below.
I D M
0.00
CTLICNAA BARG
LCV
100
Configuration
Dynamo Properties
Line 1 LCV
Line 2 100
Dynamo Properties
Enter Faceplate Security Area “”
Property Function
Enter Tag: Specifies the supervisory computer node and control module tag.
Line 1/Line 2: Textural control module tag or description.
Specifies the security area that the operator must have access rights to in order to be
Enter Faceplate Security Area:
able to activate the control module faceplate. String must be in quotation marks.
Specifies an alias name to the faceplate. The supervisory computer ensures that no
Enter Faceplate Nickname:
two faceplates with the same alias may be simultaneously displayed.
Enter Faceplate BDF Filename: Specifies the file that is activated as the control module faceplate.
Specifies the security area that the operator must have access rights to in order to be
Enter Prm Page Security Area:
able to activate the control module engineer page. String must be in quotation marks.
Enter Prm Page BDF Filename: Specifies the file that is activated as the control module engineer page.
Table 11-2: Dynamo Properties
I D M Background
Demand Description
Transparent = Normal
CLOSE Blue = Maintenance mode
LCV Demand
100 Red = False
Line 1
Green = True
Line 2
This icon is available in a number of orientations. These are collected within a common dynamo library, ICN_CT. The dynamos
are named as indicated below.
I D M
CLOSE
CTLICNAB
LCV
100
Configuration
Dynamo Properties
Line 1 LCV
Line 2 100
Dynamo Properties
Enter Faceplate Security Area “”
Property Function
Enter Tag: Specifies the supervisory computer node and control module tag.
Line 1/Line 2: Textural control module tag or description.
Specifies the security area that the operator must have access rights to in order to be
Enter Faceplate Security Area:
able to activate the control module faceplate. String must be in quotation marks.
Specifies an alias name to the faceplate. The supervisory computer ensures that no
Enter Faceplate Nickname:
two faceplates with the same alias may be simultaneously displayed.
Enter Faceplate BDF Filename: Specifies the file that is activated as the control module faceplate.
Specifies the security area that the operator must have access rights to in order to be
Enter Prm Page Security Area:
able to activate the control module engineer page. String must be in quotation marks.
Enter Prm Page BDF Filename: Specifies the file that is activated as the control module engineer page.
True Demand Text: Specifies the text that appears on the open demand.
False Demand Text: Specifies the text that appears on the close demand.
Table 11-2: Dynamo Properties
OpLimSw
Evaluate
State Evaluate
ClLimSw Set
Discrep
Latch Discrep
Reset
DscrpTmr
Reset
SetDscrp
InlckValS InlckValP
IntlockP
IntlockS
Man/Maint
Demand
Limit by HL, LL
IntlockP
AutoDmnd IntlockS
Auto
This block generates a demand to a single input analogue device. Where the device has dual limit switches, the block
derives a device state that is used to evaluate a discrepancy.
In manual mode, the analogue demand may be set within configured limits by an operator. In automatic mode, the
analogue demand may be set within configured limits by a controlling sequence or other analogue device user.
Maintenance mode is often used to indicate caution in operation but functions identically to manual mode.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Alarms
Software Block RAM data sumcheck error/network failure T/F
EvalFail Evaluation failure in block’s internal logic T/F
Hardware I/O hardware fault T/F
LSFault Limit switch fault T/F
Discrep Latched discrepancy T/F
Combined OR-ing of all alarm bits T/F
Demand Position demand Eng
DscrpTmr Discrepancy countdown timer Secs
DscrpTim Discrepancy (travel) time Secs
PulseTim Output pulse time Secs
StateAct CD hex
Open Open position T/F
Closed Closed position T/F
Opening Opening position T/F
Closing Closing position T/F
LSFault Limit switch fault position T/F
Unknown Unknown position T/F
Ø Ø Ø Ø Ø Ø Ø Ø
Implementation notes
If AnManSt control modules are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 2264 bytes and by 154 bytes for each
instance of the control module.
Auto
Avail1
Avail2
& Availble
NotAvail1
Evaluate
SetDscrp Set
Discrep
Latch Discrep
Reset
Reset
InlckValS InlckValP
IntlockP
IntlockS
Man/Maint
Demand
Limit by HL, LL
IntlockP
AutoDmnd IntlockS
Auto
Please refer to the schematic. The DgManSt block generates a demand to a single input digital device.
In manual mode, the digital demand may be set by an operator. In automatic mode, the digital demand may be set
by a controlling sequence or other digital device user. Maintenance mode is often used to indicate caution in
operation but functions identically to manual mode.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Alarms
Software Block RAM data sumcheck error/network failure T/F
EvalFail Evaluation failure in block’s internal logic T/F
Hardware I/O hardware fault T/F
Discrep Latched discrepancy T/F
Combined OR-ing of all alarm bits T/F
Demand Position demand Eng
Status Operational stsus bitfields ABCD hex
CDiscrep* Current discrepancy T/F 1
AuDiscrp* Cannot respond to automatic control T/F 2
D
Intlcked* Interlocked T/F 4
Bit4 User status #4 T/F 8
LastDmnd* Demand at last iteration T/F 1
Bit5 User status #5 T/F 2
Bit6 User status #6 T/F
C
4
Bit7 User status #7 T/F 8
Bit8 User status #8 T/F 1
Bit9 User status #9 T/F 2
B
Bit10 User status #10 T/F 4
Bit11 User status #11 T/F 8
Bit12 User status #12 T/F 1
Bit13 User status #13 T/F 2
A
Bit14 User status #14 T/F 4
Discrep* Latched discrepancy T/F 8
Hardware I/O hardware failure input CD hex
Bit0 Hardware failure #0 T/F
Bit1 Hardware failure #1 T/F
Bit2 Hardware failure #2 T/F
Bit3 Hardware failure #3 T/F
Bit4 Hardware failure #4 T/F
Bit5 Hardware failure #5 T/F
Bit6 Hardware failure #6 T/F
Bit7 Hardware failure #7 T/F
Ø Ø Ø Ø Ø Ø Ø Ø
Hardware. Hardware failure flagged by an input or output block associated with the digital device.
Discrep. Digital device has not responded to the demand. Alarm is latched.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the highest priority active alarm in the block.
Demand. Maintained demand for the position of the digital device.
Status. This bitfield shows the status of the digital device.
CDiscrep. Current Discrepancy. TRUE when the digital device is actually in discrepancy.
AuDiscrp. Automatic Discrepancy. TRUE when the digital device is not available. May be used by a
controlling sequence or other digital device users to determine if the automatic demand is active.
Intlcked. TRUE indicates an asserted interlock.
Discrep. Latched TRUE when the digital device is in discrepancy. Set FALSE during the reset action.
Bit4, Bit6-Bit14. Optional status bits. Associates additional Boolean data with the digital device.
Hardware. Asserts hardware alarm if one or more of the bits are TRUE.
Options. This bitfield allows inputs to control the operation of the digital device.
AuDmdTrk. TRUE forces the automatic demand to track the demand when not operating in auto or when
interlocked.
SetDscrp. TRUE asserts the discrepancy alarm regardless of the demand. Allows external logic to
implement the discrepancy functionality. Internally set FALSE after the reset action.
Avail1, Avail2. FALSE prevents the block from signalling that it is available for automatic control.
NtAvail1, NtAvail2. TRUE prevents the block from signalling that it is available for automatic control.
Bit6-Bit15. Optional option bits. Associates additional Boolean data with the digital device.
Reset. TRUE resets the discrepancy alarm. Internally set FALSE after the reset action.
Availble. TRUE when digital device is available for automatic control, i.e. in automatic mode, no latched
discrepancy alarm and availability options not prohibitive.
FpltType. Faceplate Type. Associate a faceplate type or other alphanumeric string with the digital device. Allows
digital devices of this type to be represented by different supervisory computer faceplates.
Implementation notes
If DgManSt control modules are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 1488 bytes and by 100 bytes for each
instance of the control module.
MtrFPAA
HA084012U201
Issue 2
PMPlcnAA_ha
HA084012U202
Issue 2
PMPlcnAA_hl
HA084012U202
Issue 2
Table 12-1: Supported block permutations
HA084012U003 Chapter 12
Issue 9 January 2018 Page 12 - 1
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Chapter 12 HA084012U003
Page 12 - 2 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Mode
Manual, Maint, Auto XCV1ØØ
MANUAL ALM
Open
Device State Device Interlocked
Running, Stopped,
39.6
Starting, Stopping Interlocked
Hardware Fault
Limit Switch Fault
Alarms
Discrepancy
Faceplate Template
Hardware Fault Hardware
Discrepancy Discrep
Soft Buttons Fail to Stop FlToStrt
Start = S Fail to Start FlToStop
Stop = P
Auto = A
Manual = M RESET
Reset = R
A START
M STOP
Configuration
Dynamo Properties
Property Function
Enter Tag: Specifies the supervisory computer node and control module tag.
Specifies the security area that the operator must have access rights to in
Enter Security Area:
order to be able to use the soft buttons. String must be in quotation marks.
Specifies the soft buttons for which a confirmation prompt is required.
Enter Prompt String: Contained within quotation marks are the key letters for each button where
confirmation is required.
Table 12-1: Dynamo Properties
Background
XISM Blue = Maintenance mode
Transparent = Normal
Line 1 100
Line 2
This icon is available in a number of orientations. These are collected within a common dynamo library, ICN_PMP.
The dynamos are named as indicated below.
I D M
PmpIcnAA_ha
XISM
100
I D M
PmpIcnAA_vl
XISM
100
Configuration
Dynamo Properties
Line 1 XISM
Line 2 100
Dynamo Properties
Enter Faceplate Security Area “”
Property Function
Enter Tag: Specifies the supervisory computer node and control module tag.
Line 1/Line 2: Textural control module tag or description.
Specifies the security area that the operator must have access rights to in order to be
Enter Faceplate Security Area:
able to activate the control module faceplate. String must be in quotation marks.
Specifies an alias name to the faceplate. The supervisory computer ensures that no
Enter Faceplate Nickname:
two faceplates with the same alias may be simultaneously displayed.
Enter Faceplate BDF Filename: Specifies the file that is activated as the control module faceplate.
Specifies the security area that the operator must have access rights to in order to be
Enter Prm Page Security Area:
able to activate the control module engineer page. String must be in quotation marks.
Enter Prm Page BDF Filename: Specifies the file that is activated as the control module engineer page.
Table 12-2: Dynamo Properties
Auto
Avail1
DscrpTim Avail2
& Availble
NotAvail1
State LSFault
CDiscrep NotAvail2 Discrep
Running Evaluate
State Evaluate
Set
Discrep
Latch Discrep
Reset
DscrpTmr
SetDscrp Reset
FrcPulse PulseTim
Demand
StrtPls
>0
PulseTmr
OR
StopPls
True Demand
Ready Discrep
+
Running
&
Manual Input
(Direct write
False
to Demand) False
Healthy
InlckValS InlckValP
IntlockP
Demand
IntlockS
Man/Maint
Healthy
AutoDmnd IntlockP
Auto IntlockS
Please refer to the schematic. The Mtr3In block generates a demand to an on/off motor. A choice of maintained output
(Demand) or pulsed outputs (StateAct.StartPls, StateAct.StopPls) is provided. A single pulse time applies to both start
and stop pulses.
In manual mode, the motor may be started and stopped by an operator. In automatic mode, the motor is started and stopped by a
controlling sequence or other motor user. Maintenance mode is often used to indicate caution in operation but functions identically
to manual mode.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Alarms.
Software. Sumcheck error in block’s RAM data.
EvalFail. Evaluation failure in block’s internal logic.
Hardware. Hardware failure flagged by an input or output block associated with the motor.
Discrep. Motor has not responded to the demand or has changed state without a change of demand. Alarm
is latched.
FlToStrt. Motor has not responded to a ‘Start’ demand. Alarm is latched.
FlToStop. Motor has not responded to a ‘Stop’ demand. Alarm is latched.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the highest priority active alarm in the block.
Demand. Maintained demand for the position of the motor. FALSE = ‘Stop’; TRUE = ‘Start’.
DscrpTmr. Discrepancy Timer. Internally set to the discrepancy time on demand change. The discrepancy alarm
is raised if this timer counts down to zero and the motor has not reacted to the demand.
DscrpTim. Discrepancy Time. The time given to the motor to react before a discrepancy alarm is raised.
PulseTmr. Pulse Timer. Internally set to the pulse time on demand change. Output pulse is asserted while the timer
is counting down to zero.
PulseTim. Pulse Time. The minimum time for which a pulsed output is maintained.
State. (Stopped/Running/Starting/Stopping/Unknown). Current motor state. Derived from the running signal.
Status. This bitfield shows the status of the motor.
CDiscrep. Current Discrepancy. TRUE when the motor is actually in discrepancy.
AuDiscrp. Automatic Discrepancy. TRUE when the motor is not available or the automatic demand is not
equal to the demand. May be used by a controlling sequence or other motor users to determine if the automatic
demand is active.
Intlcked. TRUE indicates an asserted interlock.
Trvlling. Internal flag asserted when motor is starting or stopping.
LastDmnd. Internal flag indicating demand at last iteration.
Discrep. Latched TRUE when the motor is in discrepancy. Set FALSE during the reset action.
Bit5-Bit14. Optional status bits. Associates additional Boolean data with the motor.
Hardware. Asserts hardware alarm if one or more of the bits are TRUE.
Options. This bitfield allows inputs to control the operation of the motor.
AuDmdTrk. TRUE forces the automatic demand to track the demand when not operating in auto or when
interlocked.
FrcPulse. TRUE forces the control module to re-transmit the last output pulse. Internally set FALSE after
the output pulse is started.
Avail1, Avail2. FALSE prevents the block from signalling that it is available for automatic control.
NtAvail1, NtAvail2. TRUE prevents the block from signalling that it is available for automatic control.
Bit6-Bit15. Optional option bits. Associates additional Boolean data with the motor.
Reset. TRUE resets any of the latched alarms. Internally set FALSE after the reset action.
Availble. TRUE when motor is available for automatic control, i.e. in automatic mode, no latched discrepancy
alarm and availability options not prohibitive.
FpltType. Faceplate Type. Associate a faceplate type or other alphanumeric string with the motor. Allows motors
of this type to be represented by different supervisory computer faceplates.
Implementation notes
If Mtr3In control modules are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 2198 bytes and by 134 bytes for each
instance of the control module.
VlvFPAA
HA084012U101
Issue 2
VlvFPAB
HA084012U102
Issue 2
VlvlcnAA_ha
HA084012U103
Issue 2
VlvlcnAA_vl
HA084012U103
Issue 2
VlvlcnAA_vr
HA084012U103
Issue 2
VlvlcnAB_v1
HA084012U105
Issue 2
VlvlcnAB_v2
HA084012U104
Issue 2
Table 13-1: Supported block permutations
HA084012U003 Chapter 13
Issue 9 January 2018 Page 13 - 1
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Chapter 13 HA084012U003
Page 13 - 2 Issue 9 January 2018
APPLICATION MODULE AND CONTROL MODULE BLOCK REFERENCE MANUAL
Mode
Manual, Maint, Auto XCV1ØØ
MANUAL ALM
Open Device Interlocked
Device State
Open, Opening, Interlocked
Closed, Closing,
Unknown, LSFault Hardware Fault
Limit Switch Fault
Alarms
Discrepancy
Faceplate Template
Fail To Start Hardware Fault Hardware
FailTto Stop Limit Switch Fault LSFault
Discrepancy Discrep
Soft Buttons Fail to Stop FlToStrt
Open = O Fail to Start FlToStop
Close = C
Auto = A
Manual = M RESET
Reset = R
A START
M STOP
Configuration
Dynamo Properties
Property Function
Enter Tag: Specifies the supervisory computer node and control module tag.
Specifies the security area that the operator must have access rights to in
Enter Security Area:
order to be able to use the soft buttons. String must be in quotation marks.
Specifies the soft buttons for which a confirmation prompt is required.
Enter Prompt String: Contained within quotation marks are the key letters for each button where
confirmation is required.
Table 13-1: Dynamo Properties
Mode
Manual, Maint, Auto XCV1ØØ
MANUAL ALM
Open Device Interlocked
Device State
Open1, Open2, Interlocked
Closed, ToOpen1,
ToOpen2, ToClose, Hardware Fault
Unknown, LSFault Limit Switch Fault
Alarms
Discrepancy
Faceplate Template
Fail To Start Hardware Fault Hardware
FailTto Stop Limit Switch Fault LSFault
Discrepancy Discrep
Soft Buttons Fail to Open FlToOpen
Open1 = 1 Fail to Close FlToClse
Open2 = 2
Close = C
Auto = A RESET
Manual = M
Reset = R A START
M STOP
Configuration
Dynamo Properties
Property Function
Enter Tag: Specifies the supervisory computer node and control module tag.
Specifies the security area that the operator must have access rights to in
Enter Security Area:
order to be able to use the soft buttons. String must be in quotation marks.
Specifies the soft buttons for which a confirmation prompt is required.
Enter Prompt String: Contained within quotation marks are the key letters for each button where
confirmation is required.
Table 13-1: Dynamo Properties
Interlocked Discrepancy
Mode
Icon M = Manual
Red = Normal A = Auto
Green = Maintenance mode I D M M (Blue Background) = Maintenance mode
Yellow = Closing, Opening,
Unknown, LSFault
Grey = Not Communicating Background
Blue = Maintenance mode
Flashing = Block Alarm
LCV Transparent = Normal
Line 1 100
Line 2
This icon is available in a number of orientations. These are collected within a common dynamo library, ICN_VLV.
The dynamos are named as indicated below.
I D M
VlvIcnAA_ha
LCV
100
D M
I
VlvIcnAA_vl
LCV
100
M D
I
VlvIcnAA_vr
LCV
100
Configuration
Dynamo Properties
Line 1 LCV
Line 2 100
Dynamo Properties
Enter Faceplate Security Area “”
Property Function
Enter Tag: Specifies the supervisory computer node and control module tag.
Line 1/Line 2: Textural control module tag or description.
Specifies the security area that the operator must have access rights to in order to be
Enter Faceplate Security Area:
able to activate the control module faceplate. String must be in quotation marks.
Specifies an alias name to the faceplate. The supervisory computer ensures that no
Enter Faceplate Nickname:
two faceplates with the same alias may be simultaneously displayed.
Enter Faceplate BDF Filename: Specifies the file that is activated as the control module faceplate.
Specifies the security area that the operator must have access rights to in order to be
Enter Prm Page Security Area:
able to activate the control module engineer page. String must be in quotation marks.
Enter Prm Page BDF Filename: Specifies the file that is activated as the control module engineer page.
Table 13-2: Dynamo Properties
Interlocked Discrepancy
Icon Mode
M = Manual
Red-Green = Open1
A = Auto
= Open2
Yellow = ToOpen1, ToOpen2,
I D M M (Blue Background) = Maintenance mode
This icon is available in a number of orientations. These are collected within a common dynamo library, ICN_VLV.
The dynamos are named as indicated below.
I D M I D M
Open1 Open2
I D M I D M
Open1 Open2
Configuration
Dynamo Properties
Line 1 XCV
Line 2 100
Dynamo Properties
Enter Faceplate Security Area “”
Property Function
Enter Tag: Specifies the supervisory computer node and control module tag.
Line 1/Line 2: Textural control module tag or description.
Specifies the security area that the operator must have access rights to in order to be
Enter Faceplate Security Area:
able to activate the control module faceplate. String must be in quotation marks.
Specifies an alias name to the faceplate. The supervisory computer ensures that no
Enter Faceplate Nickname:
two faceplates with the same alias may be simultaneously displayed.
Enter Faceplate BDF Filename: Specifies the file that is activated as the control module faceplate.
Specifies the security area that the operator must have access rights to in order to be
Enter Prm Page Security Area:
able to activate the control module engineer page. String must be in quotation marks.
Enter Prm Page BDF Filename: Specifies the file that is activated as the control module engineer page.
Table 13-2: Dynamo Properties
Auto
Avail1
DscrpTim Avail2
& Availble
NotAvail1
State LSFault
CDiscrep NotAvail2 Discrep
Evaluate
State Evaluate
Set
Discrep
Latch Discrep
Reset
DscrpTmr Reset
FrcPulse PulseTim
Demand
OpenPls
>0
PulseTmr
OR
ClosePls
True Demand
Manual Input
(Direct write
to Demand)
InlckValS InlckValP
IntlockP
IntlockS
Man/Maint
Demand
Limit by HL, LL
AutoDmnd IntlockP
Auto IntlockS
The Vlv1In block generates a demand to a single limit switch on/off valve. A choice of maintained output (Demand)
or pulsed outputs (StateAct.OpenPls, StateAct.ClosePls) is provided. A single pulse time applies to both open and
close pulses.
In manual mode, the valve may be opened and closed by an operator. In automatic mode, the valve is opened and closed by a
controlling sequence or other valve user. Maintenance mode is often used to indicate caution in operation but functions identically
to manual mode.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Alarms. See page 11-5 in the LIN Block Reference Manual for a general description of the Alarms field.
Software. Sumcheck error in block’s RAM data.
EvalFail. Evaluation failure in block’s internal logic.
Hardware. Hardware failure flagged by an input or output block associated with the valve.
Discrep. Valve has not responded to the demand or has moved off its limit. Alarm is latched.
FlToOpen. Valve has not responded to an ‘Open’ demand. Alarm is latched.
FlToClse. Valve has not responded to a ‘Close’ demand. Alarm is latched.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority
number as the highest priority active alarm in the block.
Demand. Maintained demand for the position of the valve. FALSE = ‘Close’; TRUE = ‘Open’.
DscrpTmr. Discrepancy Timer. Internally set to the discrepancy time on demand change. The discrepancy alarm
is raised if this timer counts down to zero and the valve has not reacted to the demand.
DscrpTim. Discrepancy Time. The time given to the valve to react before a discrepancy alarm is raised.
PulseTmr. Pulse Timer. Internally set to the pulse time on demand change. Output pulse is asserted while the
timer is counting down to zero.
PulseTim. Pulse Time. The minimum time for which a pulsed output is maintained.
State. (Open/Closed/Opening/Closing/LSFault /Unknown). Current valve state. Derived from the limit
switches.
Status. This bitfield shows the status of the valve.
CDiscrep. Current Discrepancy. TRUE when the valve is actually in discrepancy.
AuDiscrp. Automatic Discrepancy. TRUE when the valve is not available or the automatic demand is not
equal to the demand. May be used by a controlling sequence or other valve users to determine if the automatic
demand is active.
Intlcked. TRUE indicates an asserted interlock.
Trvlling. Internal flag asserted when valve travelling.
LastDmnd. Internal flag indicating demand at last iteration.
Discrep. Latched TRUE when the valve is in discrepancy. Set FALSE during the reset action.
Bit5-Bit14. Optional status bits. Associates additional Boolean data with the valve.
Hardware. Asserts hardware alarm if one or more of the bits are TRUE.
Options. This bitfield allows inputs to control the operation of the valve.
AuDmdTrk. TRUE forces the automatic demand to track the demand when not operating in auto or when
interlocked.
FrcPulse. TRUE forces the control module to re-transmit the last output pulse. Internally set FALSE after
the output pulse is started.
Avail1, Avail2. FALSE prevents the block from signalling that it is available for automatic control.
NtAvail1, NtAvail2. TRUE prevents the block from signalling that it is available for automatic control.
Bit7-Bit15. Optional option bits. Associates additional Boolean data with the valve.
Reset. TRUE resets any of the latched alarms. Internally set FALSE after the reset action.
Availble. TRUE when valve is available for automatic control, i.e. in automatic mode, no latched discrepancy
alarm and availability options not prohibitive.
FpltType. Faceplate Type. Associate a faceplate type or other alphanumeric string with the valve. Allows valves
of this type to be represented by different supervisory computer faceplates.
Implementation notes
If Vlv1In control modules are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 2294 bytes and by 132 bytes for each
instance of the control module.
Auto
Avail1
DscrpTim Avail2
& Availble
NotAvail1
State LSFault
CDiscrep NotAvail2 Discrep
OpLimSw Evaluate
State Evaluate
ClLimSw Set
Discrep
Latch Discrep
Reset
DscrpTmr Reset
FrcPulse PulseTim
Demand
OpenPls
>0
PulseTmr
OR
ClosePls
True Demand
Simulate
Demand
Manual Input
(Direct write
to Demand)
Please refer to the schematic. The Vlv2In block generates a demand to a dual limit switch on/off valve. A choice of
maintained output (Demand) or pulsed outputs (StateAct.OpenPls, StateAct.ClosePls) is provided. A single pulse
time applies to both open and close pulses.
In manual mode, the valve may be opened and closed by an operator. In automatic mode, the valve is opened and
closed by a controlling sequence or other valve user. Maintenance mode is often used to indicate caution in operation
but functions identically to manual mode.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
Alarms. See page 11-5 in LIN Block Reference Manual for a general description of the Alarms field.
Software. Sumcheck error in block’s RAM data.
EvalFail. Evaluation failure in block’s internal logic.
Hardware. Hardware failure flagged by an input or output block associated with the valve.
LSFault. Limit switches indicate valve is both ‘Open’ and ‘Closed’.
Discrep. Valve has not responded to the demand or has moved off its limit. Alarm is latched.
FlToOpen. Valve has not responded to an ‘Open’ demand. Alarm is latched.
FlToClse. Valve has not responded to a ‘Close’ demand. Alarm is latched.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority
number as the highest priority active alarm in the block.
Demand. Maintained demand for the position of the valve. FALSE = ‘Close’; TRUE = ‘Open’.
DscrpTmr. Discrepancy Timer. Internally set to the discrepancy time on demand change. The discrepancy alarm
is raised if this timer counts down to zero and the valve has not reacted to the demand.
DscrpTim. Discrepancy Time. The time given to the valve to react before a discrepancy alarm is raised.
PulseTmr. Pulse Timer. Internally set to the pulse time on demand change. Output pulse is asserted while the
timer is counting down to zero.
PulseTim. Pulse Time. The minimum time for which a pulsed output is maintained.
State. (Open/Closed/Opening/Closing/LSFault /Unknown). Current valve state. Derived from the limit switches.
Status. This bitfield shows the status of the valve.
CDiscrep. Current Discrepancy. TRUE when the valve is actually in discrepancy.
AuDiscrp. Automatic Discrepancy. TRUE when the valve is not available or the automatic demand is not
equal to the demand. May be used by a controlling sequence or other valve users to determine if the automatic
demand is active.
Intlcked. TRUE indicates an asserted interlock.
Trvlling. Internal flag asserted when valve travelling.
LastDmnd. Internal flag indicating demand at last iteration.
Discrep. Latched TRUE when the valve is in discrepancy. Set FALSE during the reset action.
Bit5-Bit14. Optional status bits. Associates additional Boolean data with the valve.
Hardware. Asserts hardware alarm if one or more of the bits are TRUE.
Options. This bitfield allows inputs to control the operation of the valve.
AuDmdTrk. TRUE forces the automatic demand to track the demand when not operating in auto or when
interlocked.
HandVlv. TRUE forces the demand to change automatically in response to the valve moving off its limit.
Permits the block to interface to a hand valve, where a discrepancy alarm is required when the valve travelling
time exceeds the discrepancy time.
FrcPulse. TRUE forces the control module to re-transmit the last output pulse. Internally set FALSE after
the output pulse is started.
Avail1, Avail2. FALSE prevents the block from signalling that it is available for automatic control.
NtAvail1, NtAvail2. TRUE prevents the block from signalling that it is available for automatic control.
Bit7-Bit15. Optional option bits. Associates additional Boolean data with the valve.
Reset. TRUE resets any of the latched alarms. Internally set FALSE after the reset action.
Availble. TRUE when valve is available for automatic control, i.e. in automatic mode, no latched discrepancy
alarm and availability options not prohibitive.
FpltType. Faceplate Type. Associate a faceplate type or other alphanumeric string with the valve. Allows valves
of this type to be represented by different supervisory computer faceplates.
Implementation notes
If Vlv2In control modules are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 2298 bytes and by 132 bytes for each
instance of the control module.
VLV3WAY: THREE WAY VALVE; THREE I/PS, MAINTAINED OR PULSED O/PS BLOCK
Block function
Auto
Avail1
DscrpTim Avail2
& Availble
NotAvail1
State LSFault
CDiscrep NotAvail2 Discrep
OpLimSw Evaluate
State Evaluate
ClLimSw Set
Discrep
Latch Discrep
Reset
DscrpTmr Reset
FrcPulse PulseTim
Demand
OpenPls
>0
PulseTmr
OR
ClosePls
True Demand
Simulate
Demand
Manual Input
(Direct write
to Demand)
Please refer to the schematic. The Vlv3Way block generates a demand to a triple limit switch three-way valve. A
choice of maintained output (Open1Act, Open2Act, CloseAct) or pulsed outputs (Open1Pls, Open2Pls, ClosePls) is
provided. A single pulse time applies to all pulses.
In manual mode, the valve may be moved by an operator. In automatic mode, the valve is moved by a controlling sequence or
other valve user. Maintenance mode is often used to indicate caution in operation but functions identically to manual mode.
Block parameters
Symbols used in the Block parameter table are explained in Chapter 1 of the LIN Block Reference Manual (Part no.
HA 082 375 U003). Additional parameter information is given in the Block specification menu section following.
InlkValS. (Open1/Open2/Close). Secondary Interlock Value. Controls the demand when the secondary interlock
is asserted.
Claims. Used to request sole control of the valve. The valve resource may be controlled by up to eight sequences
or other valve users.
Acks. Acknowledgements. Indicates acceptance of a claim.
Param1, Param2. Optional Parameter. Associates additional floating-point data with the valve.
Alarms.
Software. Sumcheck error in block’s RAM data.
EvalFail. Evaluation failure in block’s internal logic.
Hardware. Hardware failure flagged by an input or output block associated with the valve.
LSFault. Limit switches indicate valve is both ‘Open’ and ‘Closed’.
Discrep. Valve has not responded to the demand or has moved off its limit. Alarm is latched.
FlToMove. Valve has not responded to a change in demand. Alarm is latched.
Combined. TRUE if any alarm is active in the block. Adopts the same status message and priority number
as the highest priority active alarm in the block.
Demand. (Open1/Open2/Close). Maintained demand for the position of the valve.
DscrpTmr. Discrepancy Timer. Internally set to the discrepancy time on demand change. The discrepancy alarm
is raised if this timer counts down to zero and the valve has not reacted to the demand.
DscrpTim. Discrepancy Time. The time given to the valve to react before a discrepancy alarm is raised.
PulseTmr. Pulse Timer. Internally set to the pulse time on demand change. Output pulse is asserted while the
timer is counting down to zero.
PulseTim. Pulse Time. The minimum time for which a pulsed output is maintained.
State. (Open1/Open2/Closed/Opening/Closing/LSFault /Unknown). Current valve state. Derived from the limit
switches.
Status. This bitfield shows the status of the valve.
CDiscrep. Current Discrepancy. TRUE when the valve is actually in discrepancy.
AuDiscrp. Automatic Discrepancy. TRUE when the valve is not available or the automatic demand is not
equal to the demand. May be used by a controlling sequence or other valve users to determine if the automatic
demand is active.
Intlcked. TRUE indicates an asserted interlock.
Trvlling. Internal flag asserted when valve travelling.
LastOP1,LastOP2,LastCls. Internal flags indicating demand at last iteration.
Open1Avl,Open2Avl,CloseAvl. Indicates the next realisable demand based upon the ‘OnOffOn’
option setting.
Hardware. Asserts hardware alarm if one or more of the bits are TRUE.
Options. This bitfield allows inputs to control the operation of the valve.
AuDmdTrk. TRUE forces the automatic demand to track the demand when not operating in auto or when
interlocked.
HandVlv. TRUE forces the demand to change automatically in response to the valve moving off its limit.
Permits the block to interface to a hand valve, where a discrepancy alarm is required when the valve travelling
time exceeds the discrepancy time.
FrcPulse. TRUE forces the control modules to re-transmit the last output pulse. Internally set FALSE after
the output pulse is started.
Avail1, Avail2. FALSE prevents the block from signalling that it is available for automatic control.
NtAvail1, NtAvail2. TRUE prevents the block from signalling that it is available for automatic control.
OnOffOn. TRUE specifies that the valve has a centre off position.
Bit7-Bit15. Optional option bits. Associates additional Boolean data with the valve.
Reset. TRUE resets any of the latched alarms. Internally set FALSE after the reset action.
Availble. TRUE when valve is available for automatic control, i.e. in automatic mode, no latched discrepancy
alarm and availability options not prohibitive.
FpltType. Faceplate Type. Associate a faceplate type or other alphanumeric string with the valve. Allows valves
of this type to be represented by different supervisory computer faceplates.
Implementation notes
If Vlv3Way control modules are included in the configuration, the block is included in the database as a foreign
template. The runtime database size is increased by a template overhead of 2668 bytes and by 138 bytes for each
instance of the control module.
Index
Symbols L
.sto file ...............................................7-5, 7-9, 7-15, 8-8, 8-12 Ladder Diagram 9-5, 9-7, 9-9, 9-11, 9-13, 9-15, 9-17, 9-19,
9-21, 9-23
A LIN
ACTION Block ..................................................................... 8-11 cached block ...............................................................1-11
Action qualifier ................................................................... 8-11 LINtools 9-5, 9-7, 9-9, 9-11, 9-13, 9-15, 9-17, 9-19, 9-21, 9-
AGA8DATA block .............................................................. 3-12 23
Alarm LoDev ..............................................................................5-6, 5-7
Acknowledging ........................................................... 1-12 LOGIC Block Library ............................................................ 7-1
Algorithm .....................................................................4-3, 4-13
M
B MATHS Block Library .......................................................... 8-1
BATCH Block Library ........................................................... 2-1 Modbus ..............9-5, 9-7, 9-9, 9-11, 9-13, 9-15, 9-17, 9-19
MOTOR CONTROL Block Library ...................................12-1
C
O
Cached
block .............................................................................. 1-11 Orifice plate metering system ........................................3-15
Calculations ...................................................... 3-15, 3-19, 8-1
Density ............................................................................ 3-9 P
Mass flowrate ....................................................3-15, 3-19 Profibus communication .................................................... 5-5
Reynolds number .............................................3-15, 3-19
Combined alarm ................................................................ 1-13 S
Combustion .................................................................4-3, 4-11 Sequence 9-5, 9-7, 9-9, 9-11, 9-13, 9-15, 9-17, 9-19, 9-21,
CONDITION Block Library ................................................. 3-1 9-23
CONTROL Block Library ..................................................... 4-1 SIMPLE VARIABLE Block Library ....................................... 9-1
CONTROL MODULE Block Library ................................ 11-1 BYTESEQ1020 ..............................................................9-23
BYTESEQ256S ..............................................................9-23
D BYTESEQ48S .................................................................9-23
DCM (Devolved Control Module) Block Library ......... 5-1 WIDESTR128S ..............................................................9-21
Density calculation .............................................................. 3-9 WIDESTR24S ................................................................9-21
DUTY Block Library ............................................................. 6-1 WIDESTR510 ................................................................9-21
Software
E Alarm .............................................................................1-12
EMS Analogue Input Alarm Block ................................. 3-23 Stoichiometric .....................................................................4-13
Structured Text (ST) 8-7, 8-11, 9-5, 9-7, 9-9, 9-11, 9-13, 9-
F 15, 9-17, 9-19, 9-21, 9-23
Flow Calculation For Orifice Plate block ..................... 3-15 T
G TIMING Block Library ........................................................10-1
Gas Density block 3-3, 3-9, 11-13, 12-7, 13-11, 13-19, 13- U
27
User Screen Editor 9-5, 9-7, 9-9, 9-11, 9-13, 9-15, 9-17, 9-
I 19
ISO5167O block .3-3, 3-9, 3-12, 3-15, 11-13, 12-7, 13-11, V
13-19, 13-27
ISO5167V block .................................................................... 3-9 VALVE CONTROL Block Library .....................................13-1
Venturi metering system .................................................3-19
HA084012 Index
Issue 9 January 2018 Page Index - 1
Rear Cover (Master)
Eurotherm Ltd
Faraday Close
Durrington
Worthing
West Sussex
BN13 3PL
Phone: +44 (0) 1903 268500
www.eurotherm.co.uk
Schneider Electric, Life Is On, Eurotherm, EurothermSuite, Wonderware, InTouch, eCAT, EFit, EPack, EPower,Eycon,
Eyris, Chessell, Mini8, nanodac, optivis, piccolo, and versadac are trademarks of Schneider Electric SE, its subsidiaries
and affiliated companies. All other trademarks are the property of their respective owners.