03 3BHS161562-612 MinLib Loop Objects
03 3BHS161562-612 MinLib Loop Objects
V ER S I ON 6 . 1/ 2
Contents
1. Summary ..................................................................................................................................... 4
1.1. Loop Control connection .......................................................................................................... 4
1.1.1. Backtracking Examples............................................................................................. 7
1.2. Operation...................................................................................................................................... 8
1.2.1. Graphic Elements: Bar .............................................................................................. 8
2. PIDCtrl ........................................................................................................................................ 11
2.1. Basic Description ....................................................................................................................... 11
2.2. Control .......................................................................................................................................... 11
2.2.1. Library location......................................................................................................... 11
2.2.2. Modes ......................................................................................................................... 12
2.2.3. Automatic Alarm Disabling with PCC .................................................................. 12
2.2.4. Diagram Graphical Representation...................................................................... 12
2.2.5. Parameter Description ............................................................................................ 13
2.2.6. Data Type description............................................................................................. 21
2.2.7. Project Constants ................................................................................................... 24
2.2.8. Behavior of PIDCtrl with MV Signal Error ........................................................... 24
2.2.9. PCC Interlock Limitations for PIDCtrl ................................................................. 24
2.3. Operation.................................................................................................................................... 26
2.3.1. Graphic Element PIDCtrl ........................................................................................ 26
2.3.2. Graphic Element PIDIncDecButton ..................................................................... 29
2.3.3. Graphic Element PIDActuator .............................................................................. 30
2.3.4. Graphic Element MVBar ......................................................................................... 30
2.3.5. Graphic Element PIDLimitAndUnit ...................................................................... 30
2.3.6. Faceplate .................................................................................................................... 31
2.3.7. Faceplate Control Permission .............................................................................. 50
2.3.8. Alarm & Event List ................................................................................................... 50
3. PIDAdvCtrl ................................................................................................................................ 55
3.1. Basic Description ...................................................................................................................... 55
3.2. Control ......................................................................................................................................... 55
3.2.1. Library location........................................................................................................ 55
3.2.2. Diagram Graphical Representation..................................................................... 55
3.2.3. Parameter Description ........................................................................................... 55
3.2.4. Data Type description.............................................................................................61
3.2.5. Tracking Options for Setpoint ............................................................................. 65
3.2.6. Behavior with Out LCC ........................................................................................... 65
3.3. Operation.................................................................................................................................... 65
3.3.1. Graphic Elements .................................................................................................... 65
3.3.2. Faceplate ................................................................................................................... 65
3.3.3. Faceplate Permissions ........................................................................................... 76
3.3.4. Alarm & Event List ................................................................................................... 78
4. RatioCtrl.....................................................................................................................................79
4.1. Control ......................................................................................................................................... 79
4.1.1. Library location........................................................................................................ 79
4.1.2. Modes ........................................................................................................................ 79
4.1.3. Diagram Graphical Representation..................................................................... 79
5. SplitRange ................................................................................................................................ 90
5.1. Control ......................................................................................................................................... 90
5.1.1. Library location........................................................................................................ 90
5.1.2. Diagram Graphical Representation..................................................................... 90
5.1.3. Parameter Description ........................................................................................... 90
5.1.4. Data Type description............................................................................................ 90
5.1.5. Project Constants ....................................................................................................91
5.1.6. Backtracking Behavior ............................................................................................91
5.2. Operation.....................................................................................................................................91
5.2.1. Graphic Element OUT1andUnit, OUT2andUnit..................................................91
5.2.2. Graphic Element SplitRangeLimitAndUnit ........................................................ 92
5.2.3. Faceplate ................................................................................................................... 92
5.2.4. Faceplate Permissions ........................................................................................... 95
6. Revisions ................................................................................................................................... 96
1. Summary
This document contains a detailed description of the following Loop objects:
– PIDCtrl
– PIDAdvCtrl
– RatioCtrl
– SplitRange
LoopControlData is split into Data transferred Forward, e.g. the Setpoint from PIDCtrl to
MOTP, and Backward, e.g. the Actuator Position. To have basic compatibility with the Stand-
ard Libraries, the Control Part of Type ControlConnection is defined as additional Level with
its own Forward/Backward Part.
LoopControlData; components
LoopControlForward; components
LoopControlBackward; components
2 Tripped bool retain false false NOT USED: Tripped Indication from
Value Consumer (Signal Error or Motor
Tripped).
For a detailed Description of the ControlConnection Datatype, please refer the “AC800M Bi-
nary and Analog Handling” Manual (3BSE035981).
Following Figure shows an example for a Cascade PID Loop with two Actuators in SplitRange
Configuration. Besides the Group and I/O Parameter Connections, only Connections of type
LoopControlConnection need to be used, e.g. to connect the Setpoint from PIDAdvCtrl at
OUTCC to the SplitRange In Port and from the SplitRange Out1 and Out2 to the External Set-
point Reference Input on the Actuator Blocks:
Parameters of Type LoopControlConnection can only be connected from one Block producing
an Analog Setpoint or Value, e.g. a PIDAdvCtrl, to a Consumer of an Analog Setpoint, e.g. an
Actuator. The Consumer can itself have Output Parameters of Type LoopControlConnection,
connected to other Consumers, e.g. for a Cascade Control Loop, but there must never be a
Feedback Loop Connection in the Control Application.
Range and Unit of the Setpoint can be transferred in both directions, where the Forward Di-
rection always takes priority if the Values differ. PIDCtrl and RatioCtrl Blocks allow to over-
write the Range and Unit for the Output from the Faceplate as well.
The Actuator Position is transferred backwards as well and shown in the Faceplate for infor-
mation to the Operator as well. Range and Unit for the Actuator Position are always defined
equal to the Output Range and Unit.
Navigation between the Blocks connected by LoopControlConnection is available for the Op-
erator in the Faceplate. Any Alarm State of the Actuator with corresponding Color is shown
for the related Output Value in the Controller Faceplate as well.
While the Weighfeeder is stopped (or tripped, local etc.), the PIDCtrl can stay in Auto Mode
but keeps the Weighfeeders’ Start Speed Setpoint (can be configured on the Weighfeeder as
constant, last Setpoint while running or set from the Application Logic). The Output of the
PIDCtrl will start changing again from the Start Speed Setpoint as soon as the Weighfeeder is
running again.
If the PIDCtrl is in Manual Mode (Output Reference given in PIDCtrl Setpoint), Backtracking
can either overwrite the Manual Output Reference, or the PIDCtrl ignores the Backtracking
and continues with the given Reference Setpoint, depending on the “Man Backtracking” Op-
tion set in the Faceplates “OUT Limits” Tab.
1.2. Operation
1.2.1. Graphic Elements: Bar
Presents the analogue value as bar graph. Alarm or process limits are graphical shown and
different bar graph appearances are possible. The Color of the Bar depends on the indicated
Value and can be customized, here the default for MV, green, is shown
Presentation
Vertical Bar This is the standard appearance of the bar graph. The
value will be indicated in relation to the maximum and
minimum range. The green bar will always start from the
minimum range.
Horizontal Bar This is the standard appearance of the bar graph. The
value will be indicated in relation to the maximum and
minimum range. The green bar will always start from the
minimum range.
Status
Limit Alarm or process limit ex- Colored Alarm band on one side.
ceeded.
Labels
Description Indication
Signal blocked
Limit High 2
Limit High 1
Limit Low 1
Limit Low 2
Rate of Change
Example:
Properties
EnableLogicalColor Boolean True If EnableLogicalColor is true, then all used colors are
logical colors. The logical color reference is equal to the
default logical color used in the color properties. To use
an individual color set it to false.
EnableManualRange Boolean False If set to true, the bar’s range can be set manually
SubscriptionRate Integer 0 The update rate for all aspect object properties sub-
scribed for
SymbolSize Integer 14 Symbol size in pixel: Little = 8, Small = 12, Standard = 14,
Large = 18, XXL = 22
VerticalBar Boolean True VerticalBar: True = vertical appearance, false = horizon-
tal appearance.
The Action Property controls whether the button has direct or applied (two step operation)
action. If you choose Action = Applied you must confirm your action after clicking the button
with the enter-key or an apply-button on the graphic display. The System Default can be set in
Graphic Profile Values PG2 in the User Structure.
2. PIDCtrl
The PIDCtrl module for closed loop control, has the following options:
– 2 external set point references, that can be written from the application
– 2 external controller output references, that can be written from the application
– Limit supervision of measured value and deviation, with integrated alarm annunciation
– Event logging for control mode changes and set point changes
– FF (Foundation Fieldbus) support: set FF Device to Cascade Mode automatically when re-
quested from faceplate or from the FF Function Block.
– Status of MV, ActuatorPos and OUTP signals. All Substatus for DP, PA and FF Field Devices
will generate error control when quality is Bad or Uncertain for MV and OUTP
– Operator Station Interface (graphic element and faceplate) including detailed alarm and
interlock indications, separated between the object and its TagName
2.2. Control
2.2.1. Library location
The Control Module Type for PIDCtrl is located in the library BMIStandard, its corresponding
Structured Data Types are defined in BMIConstAndVar.
2.2.2. Modes
The PIDCtrl module has 2 different control modes Manual and Automatic, these modes are
selectable from the operator station. Additionally, a Balancing Mode is provided to handle Er-
ror State which is automatically triggered by Signal Error depending on the Configuration.
The controller output is set either from the operator station, via the faceplate (OUT) or from
the superior application program (E1M or E2M).
The controller output is calculated according to the deviation between the set point and the
measured value, which means that the PID controller is regulating.
Set point can either be set from the operator station, via the faceplate (SP) or from the supe-
rior application program (E1A or E2A).
While the PIDCtrl Module supports external Setpoints from the Application Logic, it
can not be used for Cascade Control Loops because of Limitations in the Back-
tracking support. For Cascade Control Loops, the PIDAdvCtrl Module shall be used
instead.
The controller output is set to the Balancing Reference Value, in case the Process Feedback
Measured Value or the Output Signal is in Error, or from the Application Logic. By Default, Bal-
ancing Mode is kept for 10 seconds only, this can be changed with the Project Constant
cBMI.PID1.ClampToBalWhileSigErr, to stay in Balancing Mode until the Signal Quality is ok
again.
cBMI.Std_Type: 0
Motor is not running, NC Valve is closed, NO Valve is Open, for PCC connected to Group: if
Group is not started
cBMI.Std_Type: 1
Same as Std_Type 0 but always alarm on all Objects if Group is started and Consumer prese-
lected. In case object is standby preselected alarm priority is automatically reduced from Fail-
ure to Warning.
PCCAEListFrcEn = true
Automatic alarm disabling switched off. This option shall be used in cases a signal has to
alarm independent from the status of its parent.
1 Name string[24] ‘Name’ 1 in INIT: Tag name of the PIDCtrl ((allowed delimi-
nators are “.” and “-“, no blanks “:” or “;” al-
lowed)
8 MV_FieldDevice dword 16#80C0 0 in IN: 2nd DWORD for MV Field Device Status Su-
Status pervision e.g. Profibus PA Devices etc. If value
equals 16#80C0 the FPL indication is hidden
9 OUTP RealIO default 0 out IN/OUT: Output signal of the PID Loop to I/O
(Use IO.<GRP>.<PID>.Out.OUTP for glue logic)
10 OUTCC LoopCon- default 1 out OUT: Output signal of the PID Loop for con-
trolData nection to Consumer
17 GrpPreSelec- string[50] cBMI.Empty_str 1 in IN: PreBins the consumer is assigned to. Syn-
tion1 tax: P1&P2|P3&N4 (= P1 AND P2 OR P3 AND
NOT P4). AND before OR. Max 5x OR. No
Spaces allowed.
21 GrpPreSelec- string[50] cBMI.Empty_str 1 in IN: PreBins the consumer is assigned to. Syn-
tion2 tax: P1&P2|P3&N4 (= P1 AND P2 OR P3 AND
NOT P4). AND before OR. Max 5x OR. No
Spaces allowed.
25 GrpPreSelec- string[50] cBMI.Empty_str 1 in IN: PreBins the consumer is assigned to. Syn-
tion3 tax: P1&P2|P3&N4 (= P1 AND P2 OR P3 AND
NOT P4). AND before OR. Max 5x OR. No
Spaces allowed.
27 AfterBalMode dint 1 1 in IN: After balance set mode. [0= Last Mode,
1=Man, 2=Auto, 3=ExtMan1, 4=ExtMan2, 5=Ex-
tAuto1, 6=ExtAuto2]
29 EnMan bool true 0 in IN true: Manual mode enabling (open loop con-
trol)
30 EnAuto bool true 0 in IN true: Auto mode enabling (closed loop con-
trol)
35 ExtMan1Txt string[35] cBMI.Empty_str 0 in IN: Description text for ExtMan1 Mode, for NLS
support use ||AE_NLS_ 15oolea and no space in
the text
36 ExtMan2Txt string[35] cBMI.Empty_str 0 in IN: Description text for ExtMan2 Mode, for NLS
support use ||AE_NLS_ 15oolea and no space in
the text
37 ExtAuto1Txt string[35] cBMI.Empty_str 0 in IN: Description text for ExtAuto1 Mode, for
NLS support use ||AE_NLS_ 15oolea and no
space in the text
38 ExtAuto2Txt string[35] cBMI.Empty_str 0 in IN: Description text for ExtAuto2 Mode, for
NLS support use ||AE_NLS_ 15oolea and no
space in the text
45 ModeTr bool true 0 in IN: True enables events on mode change [Man,
Auto, Ext, etc.]
47 EnExtPIDSet- bool false 0 in IN: false = settings from Faceplate, true = ex-
tings ternal settings can be used (Auto Tuning will
not work
48 PID_ASPTrackin bool true 0 in COLD INIT true: Init Par.for PID auto setpoint
g tracking. [true = auto setpoint is tracking the
MV or ExtRefAuto]
49 PID_ASPSpeed real 25.0 0 in COLD INIT 25.0: Initial value for the maximum
change rate of the setpoint in closed loop
mode [%/s]
50 PID_ASPTrackin bool true 0 in COLD INIT: Faceplate parameter for PID auto
gExtAuto setpoint tracking when leaving ExtAutoModes
[true = auto setpoint is tracking the MV]
51 PID_BumpFree bool true 0 in COLD INIT true: Init par. BumpFree transition
on mode changes. [true = ASPSpeed used for
SP mode changes]
52 PID_MOUTPTrac bool true 0 in COLD INIT true: Init Par.for PID Manual Output
king tracking. [true = manual ouput is tracking the
OUTP or ExtRefMan]
53 PID_OUTPSpeed real 25.0 0 in COLD INIT 25.0: Initial value for the maximum
change rate of the output signal [% / s], Mini-
mum value can be 0.1
55 PID_Direct bool false 0 in COLD INIT false: If direct = true output is in-
creasing (decreasing) on increasing (decreas-
ing) input
56 PID_Gain real 1.0 0 in COLD INIT 1.0: Initial value for the normalized
controller gain
57 PID_Ti real 20.0 0 in COLD INIT 20.0: Initial value for the integration
time
58 PID_Td real 0.0 0 in COLD INIT 0.0: Initial value for the derivation
time
59 PID_DerFilterTi real 0.0 0 in COLD INIT 0.0: Initial value for the Filter for the
me D-part.
60 PID_MVFilterTim real 0.0 0 in COLD INIT 0.0: Initial value for the measured
e value input filter.
61 PID_DeadZone real 0.0 0 in COLD INIT 0.0: Initial value for the dead zone of
the control error
62 PID_FfGain real 0.0 0 in COLD INIT 0.0: Initial value for the feedforward
gain
64 PID_Offset real 50.0 0 in COLD INIT 0.0: Initial value for the offset of the
output for P- and PD-controller
65 EnExtLimits bool false 0 in IN: false = MV / DEV limit settings from Face-
plate, true = COLD INIT can be used as external
limits
66 MV_ErrCtrl bool false no in IN: Action in case of Signal Error on MV: false =
no action; true = MV.Value is forced to Err_Val
67 MV_ErrVal real 99999 no in IN: Error Value used in case of Err_Ctrl = true
68 MV_HiLim2 real 100 0 in COLD INIT: Initial limit for High2 alarm.
69 MV_BlkHiLim2 bool false 0 in COLD INIT: Initial value for blocking of the limit
high 2 handling
72 MV_HiLim1 real 100 0 in COLD INIT: Initial limit for High1 alarm.
73 MV_BlkHiLim1 bool false 0 in COLD INIT: Initial value for blocking of the limit
high 1 handling
76 MV_PhiLim real 90 0 in COLD INIT: Initial limit for Process High alarm.
77 MV_BlkPHiLim bool true 0 in COLD INIT: Initial value for blocking of the limit
Process High handling
80 MV_PloLim real 10 0 in COLD INIT: Initial limit for Process Low alarm.
81 MV_BlkPLoLim bool true 0 in COLD INIT: Initial value for blocking of the limit
Process Low handling
85 MV_BlkLoLim1 bool false 0 in COLD INIT: Initial value for blocking of the limit
low 1 handling
89 MV_BlkLoLim2 bool false 0 in COLD INIT: Initial value for blocking of the limit
low 2 handling
93 MV_AlarmDelay time 0s 0 in COLD INIT: Initial time delay for the MV limit
level supervision
94 MV_EnIndividual bool cBMI.PID1.EnIndi 0 in IN: Enables the individual alarm delay setting
AlarmDelays vid- for all the 6 limits in the faceplate. If True,
ualAlarmDelays AlarmDelay has only effect for upgrade.
95 DEV_HiLim real 50 0 in COLD INIT: Initial limit for deviation high alarm
in [%]
98 DEV_LoLim real -50 0 in COLD INIT: Initial limit for deviation Low alarm
in [%]
102 DEV_AlarmDelay time 0s 0 in COLD INIT: Initial time delay for the deviation
limit level supervision
103 IntlkStartInhibit time 0s 0 in INIT: Bypass Interlock for a certain time after
start of PCC parent (MOTx, VLVx), Start by Ord
instead of Run where the IntlkDir is DirFB#
104 IntlkLocStar- bool false 0 in INIT: Bypass Interlock in LOC mode if LCBStart
tOverride is continuously pushed. All PCC parents need
to be in LOC.
105 EnExtSPLimits bool false 0 in IN: false = SP limit settings from Faceplate,
true = COLD INIT Values can be used as exter-
nal limits
106 SP_HiLim real 100 0 in COLD INIT: Initial limit for setpoint high limit
107 SP_LoLim real 0 0 in COLD INIT: Initial limit for setpoint low limit
108 EnExtOUTLimits bool false 0 in IN: false = OUT limit settings from Faceplate,
true = COLD INIT Values can be used as exter-
nal limits
109 OUT_HiLim real 100 0 in COLD INIT: Initial limit for output high limit
110 OUT_LoLim real 0 0 in COLD INIT: Initial limit for output low limit
111 EnConPu bool false 0 in IN: enabling of ConPu 3 state position control-
ler. (Actuator Position required !!)
112 EnExtPUSet- bool false 0 in IN: false = settings from Faceplate, true = ex-
tings ternal PU settings can be used
113 PU_DecIfNotEna bool false 0 in IN: true = Send a decrease command for dura-
bled tion of PU_TravelTime in case CON PU is disa-
bled
114 PU_OrdInc bool false 1 out OUT: connection to 19oolean signal for in-
creasing of setpoint
115 PU_OrdDec bool false 1 out OUT: connection to 19oolean signal for de-
creasing of setpoint
117 PU_ReCalcTime time time#10s 0 in COLD INIT: Cycle time for re-calculation of
pulse length. If 0, calculation of pulse every
task cycle
119 PU_GapTime time time#0s 0 in COLD INIT: Actuator gap. time which is added
to the pulse when direction is changed
120 PU_TravelTime time time#1m 0 in COLD INIT: Total setpoint “travel” time (de-
fined as time to change the setpoint from 0 to
100 %)
121 PU_DirChgTime time cBMI.Time2s 0 in IN INIT: Waiting time when changing direction
(INC/DEC). If 0, down time is one task cycle
122 PU_GainInc real 1.0 0 in COLD INIT: Gain for pulse length calculation
when increasing the setpoint
123 PU_GainDec real 1.0 0 in COLD INIT: Gain for pulse length calculation
when decreasing the setpoint
125 GrpStep1Over- bool true 0 in IN true: If true, group does not go to hold if
ride PID is not in requested mode.
126 GrpStep2Over- bool true 0 in IN true: If true, group does not go to hold if
ride PID is not in requested mode.
127 GrpStep3Over- bool true 0 in IN true: If true, group does not go to hold if
ride PID is not in requested mode.
128 GrpReadyOnSi- bool false 0 in IN false: If true, group shows ready even if a
gError signal error exists.
129 ProcessRunFor- bool true 0 in IN true: Used to disable simulation from Pro-
Sim cess conditions (used for Direct Closed Loops)
For Details on the PCC Interlock see Basic Objects Manual, chapter PCC, Interlock Bus (Pro-
cess Control Connection)
PIDCtrlData; components
PIDCtrlInput; components
3 MV_EnPHiLim bool retain nosort true IN true: Enables Process High Limit
4 MV_EnPLoLim bool retain nosort true IN true: Enables Process Low Limit
7 AEListEn bool retain nosort true IN true: External Alarm List Enabling of AIS, tempo-
rary disabling of unack alarming and entries in
alarmlist, NOTE: Overwritten by PCC
8 AlarmEn bool retain true IN true: External Enabling of PIDCtrl Limit and Devia-
tion Supervision, used to te
9 PreSelStep1 bool retain hidden true IN true: true = PID is pre-selected for GrpStep1, con-
nected to PreBinData.PreSel in case parameterized
PreSelection is not used.
10 PreSelStep2 bool retain hidden true IN true: true = PID is pre-selected for GrpStep2, con-
nected to PreBinData.PreSel in case parameterized
PreSelection is not used.
11 PreSelStep3 bool retain hidden true IN true: true = PID is pre-selected for GrpStep3, con-
nected to PreBinData.PreSel in case parameterized
PreSelection is not used.
12 SetMan bool retain hidden IN pulse: Set operation mode to Manual (open loop
with output reference from FPL)
13 SetAuto bool retain hidden IN pulse: Set operation mode to Auto (closed loop
control with setpoint reference from FPL)
14 SetExtMan1 bool retain hidden IN pulse: Set operation mode to external manual 1
(open loop control with external output reference)
15 SetExtMan2 bool retain hidden IN pulse: Set operation mode to external manual 2
(open loop control with external output reference)
16 SetExtAuto1 bool retain hidden IN pulse: Set operation mode to external auto 1
(closed loop control with external output reference)
17 SetExtAuto2 bool retain hidden IN pulse: Set operation mode to external auto 2
(closed loop control with external output reference)
19 EnModChng bool retain true IN true: External enabling of mode changes from
FPL, used to temporary disable mode changes
20 ExtRefMan1 real retain 0.0 IN: EXTernal REFerence Manual 1. Value is used as
output if open loop control ExtMan1 is selected.
21 ExtRefMan2 real retain 0.0 IN: EXTernal REFerence Manual 2. Value is used as
output if open loop control ExtMan2 is selected.
22 ExtRefAuto1 real retain 0.0 IN: EXTernal REFerence Auto 1. Value is used as PID
setpoint if closed loop control ExtAuto1 is sele
23 ExtRefAuto2 real retain 0.0 IN: EXTernal REFerence Auto 2. Value is used as PID
setpoint if closed loop control ExtAuto2 is sele
PIDCtrlOutput; components
2 WSP RealIO retain nosort OUT: Actual working setpoint of the PID CTRL
3 OUTP RealIO retain nosort OUT: Actual output of the PID CTRL, can be
connected to parameter OUTP in case no AOS
is used !!
4 PU_Dev real retain nosort OUT: Deviation from integrated three state
CON PU controller
5 PU_OrdInc bool retain nosort OUT: connection to 23oolean signal for in-
creasing of setpoint
6 PU_OrdDec bool retain nosort OUT: connection to 23oolean signal for de-
creasing of setpoint
21 OUTP_H bool retain nosort OUT: Indication of output signal high limiting.
22 OUTP_L bool retain nosort OUT: Indication of output signal low limiting.
25 DEV_H BoolAL retain nosort OUT: Indication of DEViation > High alarm
limit
26 DEV_L BoolAL retain nosort OUT: Indication of DEViation < Low alarm limit
29 ActPosErr bool retain nosort OUT: Indication Actuator Position Signal Error,
this stops CON PU
31 FirstOrMax- string[32] retain nosort ‘’ Tag Name of the IO Device with the first or
AETag highest Alarm or Event causing an action on
the Motor, Group or Valve
4 cBMI.PID1.DisabledIntMaxIndTr dint 13
For (forced) setting PCC Interlocks with Signal Error, use MV_ErrCtrl and MV_ErrVal instead.
Note that the Error Value will be applied internally for the MV Value only, and not written out-
side to the MV Parameter unlike the AIS behaviour with ErrCtrl and ErrVal Parameters.
PIDCtrl is not supporting the Option “Fast” assigned to MV limits and Deviation limits. If any
IntlkDir is configured with “Fast” (e.g. DirXFast, DirFBXFast), the Interlock will onlz work as
configured without Fast.
“Fast” interlock direction option will be removed from H2, H1, Phi, Plo, L1, L2, DEVH and DEVL
limits as in following example:
The “noAck” interlock direction option does not change the behavior for Phi and Plo limits
since these limits do not support Alarms, so no Acknowledge is needed for these Interlocks
to release in the standard configuration already.
2.3. Operation
Four graphic elements are available for the PIDCtrl:
Presentation
To change the PIDCtrl presentation in common, change the Common NG Properties as de-
scribed in MinLib Overview Getting Started Configuration (3BHF004109).
However, it is possible to change the settings per graphic item individual: Set the Customize
property value to true, to enable the Customize properties. If Customize is false, the Custom-
ize properties (EnableDescription, EnableStatus, EnableTagName, EnableValue#Ind) have no
impact on the graphic item.
Property Example
EnableValue1Ind = true
EnableValue2Ind = true
EnableValue1Ind = true
EnableValue2Ind = true
EnableValue3Ind = true
EnableValue1Ind = true
EnableValue2Ind = true
EnableValue3Ind = true
EnableValue4Ind = true
Note: The type e.g. SP, MV, OUT etc. of the presented value can be selected by the property
Value#Indication see properties.
Enabled
Disabled
Note: Direct entry for set point / output is possible when direct entry is enabled in the Com-
mon NG Properties.
Labels
Labels Example
Backtracking
Properties
Customize Boolean False InitOnly False = General settings are used. True =
Customized settings are used.
EnableMode-Caption- Boolean True InitOnly If true, the mode caption will be taken
OPC from OPC. If false, the default NLS will
be taken.
SubscriptionRate Integer 0 Dynamic The update rate for all aspect object
properties subscribed for
For common settings please refer to MinLib Overview Getting Started Configuration
(3BHF004109).
Properties
LimitValueEnum
Value Description
2.3.6. Faceplate
The PID Faceplate is divided into a Default View that includes only the basic information and
two extended views, one for all the operations (Limits, Groups) and the second for all the reg-
ulation settings (P, I, D, DeadZone, …)
Default View
Loop Settings
Value Indication
Graphical Bar
Control Output
Extended View
Normal View
Abbr. Description
Block Limit Any MV Limit Value Alarm is disabled from Application or by PCC Parent
Abbr. Description
MV Measured value
SP Setpoint value
Normal View
The faceplate first extended view gives more detailed info about the PIDCtrl, such as
Tab Description
Trend Online trend of measured value, controller output and setpoint value
Group Corresponding Drive Group settings and link to the Group Sequence
IOStatus Substatus for DP, PA and FF Field Devices connected to Output and Actuator value
Mode
Selected Mode
Setpoint Entry
Modes Description
Auto Set point is entered from the faceplate. PID controller is regulating.
Manual Controller output is set directly via the faceplate. PID controller is not regulating.
E1A External Reference Auto 1. Set point is written from the application and enabled if the parame-
ter ExtAuto1 is true. PID controller is regulating.
E2A External Reference Auto 2. Set point is written from the application and enabled if the parame-
ter ExtAuto2 is true. PID controller is regulating.
E1M External Reference Manual 1. Controller output is written from the application and enabled if
the parameter ExtMan1 is true. PID controller is not regulating.
E2M External Reference Manual 2. Controller output is written from the application and enabled if
the parameter ExtMan2 is true. PID controller is not regulating.
Trend
On-Line trend with measure value, setpoint and control output value. Moving over the trend
area a curser will appear, showing enabled traces’ value and record time.
Show/Hide Trace
MV: Filtered Signal
IO: Signal
ROC: Rate of Change
Record Time
Show/Hide Grid
Figure 11 - Trend Indication
MV Limits
Figure - 12 MV Limits
MV Limits Description
B Indication that the corresponding alarm limit has been blocked. Yellow means that the
alarm limit is blocked (disabled)
Alarm Delay Time delay in sec. before alarm message will be send to the operator station
When alarm limits are changed from the faceplate, you must take into consideration that
these values will be overwritten again with the initial values when a cold restart / reset is per-
formed and the coldretain files are not available for the corresponding controller.
To avoid this, you need to update the initial values for the corresponding PIDCtrl control mod-
ule instance with Control Builder, after changing the values from the Faceplate.
SP Limits
ROC Limitation
for SP
SP Limits Description
Enable Auto Calc Auto Calculation sets the Stepsize to a multiple of 10 times 1 or 5 dependent on the
for Inc/Dec Step Range of the Setpoint
Inc/Dec Step If “Enable Auto Calc for Inc/Dec Step” is not set, the Stepsize used for the Inc/Dec But-
tons and the Direct Entry Window can be set manually
Enable relative If set, the Max Increase / Decrease Values are enforced
Limits for Entry
Window
Max Increase The Direct Entry Window’s high limit is set to the current Value plus the Value given here
Max Decrease The Direct Entry Window’s low limit is set to the current Value minus the Value given
here
ASP Tracking Parameter for PID auto setpoint tracking. (true = auto setpoint is tracking the MV)
ASP Tracking Ext Parameter for PID auto setpoint tracking. (true = auto setpoint is tracking the ExtRe-
Auto fAuto1 or 2)
When limits are changed from the faceplate, you must take into consideration that these val-
ues will be overwritten again with the initial values when a cold restart / reset is performed
and the coldretain files are not available for the corresponding controller.
To avoid this, you need to update the initial values for the corresponding PIDCtrl control mod-
ule instance with Control Builder, after changing the Values from the Faceplate.
OUT Limits
ROC Limitation
for Output
Enable Auto Calc for Auto Calculation sets the Stepsize to a multiple of 10 times 1 or 5 dependent on
Inc/Dec Step the Range of the Output Value
Inc/Dec Step If “Enable Auto Calc for Inc/Dec Step” is not set, the Stepsize used for the Inc/Dec
Buttons and the Direct Entry Window can be set manually
Enable relative Limits If set, the Max Increase / Decrease Values as set here are enforced
for Entry Window
Max Increase The Direct Entry Window’s high limit is set to the current Value plus the Value
given here
Max Decrease The Direct Entry Window’s low limit is set to the current Value minus the Value
given here
Man Tracking OUT Parameter for PID manual output tracking. (true = manual output setpoint is
tracking the actual output)
Man Backtracking In Manual Mode, the OUT Value set from Faceplate is following the Backtracking
Value in case the PIDCtrl is in Backtracking
When limits are changed from the faceplate, you must take into consideration that these val-
ues will be overwritten again with the initial values when a cold restart / reset is performed
and the coldretain files are not available for the corresponding controller.
To avoid this, you need to update the initial values for the corresponding PIDCtrl control mod-
ule instance with Control Builder, after changing the Values from the Faceplate
Dev Limits
Delay Time delay in sec. before alarm message will be send to the operator station
When limits are changed from the faceplate, you must take into consideration that these val-
ues will be overwritten again with the initial values when a cold restart / reset is performed
and the coldretain files are not available for the corresponding controller.
To avoid this, you need to update the initial values for the corresponding PIDCtrl control mod-
ule instance with Control Builder, after changing the Values from the Faceplate.
Block / Override
Block Alarm
Block Description
Block Input The analog input for the MV will be “forced” on controller hardware level.
The alarm limits remain active. Note in case PIDCtrl is in simulation, no value can be entered
even while the input is blocked.
Block Alarm All 4 alarm limits for the MV will be blocked. They are not taken into account anymore.
PCC
The PCC interlock configuration tab shows the actual configuration and a link to the parent
object.
There is a PCC parameter error handling for MV limits and Deviation limits. If any parameter
“IntlkType” or “IntlkDir” connected to the control module have incorrect Dint values, a yellow
colored error message “PCC Intlk Param Error” will appear.
Group
Control Mode 1st sequential mode order of the PID con- Delay for Preselection Condition
for Step 1 troller within the Drive Group Step 1 e.g P4
Control Mode 2nd sequential mode order of the PID Delay for Preselection Condition
for Step 2 controller within the Drive Group Step 2 e.g P5
Control Mode 3rd sequential mode order of the control- Delay for Preselection Condition
for Step 3 ler within the Drive Group Step 3 e.g P2 & P1 | P3 & ! P1
(P2 and P1) or (P3 and not P1)
An Aspect Link giving access to the “Device Management” Object can be configured via the
“BMI DTM Link” General Properties Aspect.
The “Device Management” Button will be shown only if the Properties are not empty Strings.
OUT Range
This Tab is only relevant in case the OUTCC is connected to a Block that does not feed back
the Range itself, like RatioCtrl or SplitRange. In these cases, the OUT Range can be defined
from the Faceplate by setting the “Override Range” Checkbox.
It is not allowed to connect both OUTCC and OUTP at the same time, as the Param-
eters defined in OUTCC are written to OUTP as well. In case OUTP is connected to a
Hardware Output Channel directly, “Override Range” should not be used as this will
overwrite the Settings made in the Hardware Unit and leads to problems on subsequent
downloads because the Values will be overwritten from the Channel again.
Range Description
Override Range Set the OUTCC Range forwarded by the Values on this Tab
Extended View
The faceplate extended view gives more detailed info about the PID, such as.
Tab Description
Par PU1 Built in Three State Controler configuration (only used in case loop is controlled by two digi-
tal output signals increase / decrease)
Par PU2 Built in Three State Controler configuration (only used in case loop is controlled by two digi-
tal output signals increase / decrease)
Par
Par Description
Offset Value for the offset of the output for P- and PD-controllers
Bump Free Bump Free transition on mode changes. (true = ASPSpeed used for SP mode changes)
When PID parameters are changed from the faceplate, you must take into consideration that
these values will be overwritten again with the initial values when a cold restart / reset is per-
formed and the coldretain files are not available for the corresponding controller.
To avoid this, you need to update the initial values for the corresponding PIDCtrl control mod-
ule instance with Control Builder, after changing the Values from the Faceplate.
Par_PU1
Par_PU1 Description
Travel Time Total setpoint "travel" time (defined as time to change the setpoint from 0 to 100 %)
Gain Inc Gain for pulse length calculation when increasing the setpoint
Gain Dec Gain for pulse length calculation when decreasing the setpoint
DeadBand PU deadband in units, no corrective action if actual value - setpoint is within deadband
Recalc Time Cycle time for re-calculation of pulse length. If 0, calculation of pulse every task cycle
Gap Time Actuator gap time which is added to the pulse when direction is changed.
Set new Times Used for recalculated the CON PU timers without download (warm restart). This is a pre-
condition to adjust CON-PU parameters from the faceplate.
When ConPu parameters are changed from the faceplate, you must take into consideration
that these values will be overwritten again with the initial values when a cold restart / reset is
performed and the coldretain files are not available for the corresponding controller.
To avoid this, you need to update the initial values for the corresponding PIDCtrl control mod-
ule instance with Control Builder, after changing the Values from the Faceplate.
Par_PU2
Par_PU2 Description
Con Pu In this mode, a three state controller intended to control, by mean of pulses (increase, de-
crease), a process via an integrating actuator such as a shifting motor or a solenoid valve.
Time Based In this mode, the Actuator Position is simulated according to the travel time. If limit switches
are reached or WorkingSetpoint is on the upper or lower limit, the ActuatorPosition is adap-
tative corrected. This mode works fine in cases where a PID control in Auto Mode is used as
Working setpoint.
Fix Pulse In this mode, increase and decrease may be manually controlled by 3 buttons (Inc, Dec, Stop)
in the faceplate. Pulses with length of 1% of travel time and period of 3% of travel time are
sent to the IO’s as long as increment or decrement is active. This mode is preferably used in
cases where INC/DEC are directly connected to the PID (e.g. speed controlled drives)
When the ConPu modes are changed from the faceplate, you must take into consideration
that these values will be overwritten again with the initial values when a cold restart / reset is
performed and the coldretain files are not available for the corresponding controller.
To avoid this, you need to update the initial values for the corresponding PIDCtrl control mod-
ule instance with Control Builder, after changing the values from the Faceplate.
Autotuning
PV Max and PV Min Measured Value is not inside configured Range or Range Parameters are not correct
not properly set – correct the Parameter Settings for MV
PV far from SP Too big Deviation between MV and SP – get the loop in a stable state then start the
Auto-tuning again
Control Signal too Make sure the “Max relay amplitude” is set so that the Control Loop doesn’t get to a
close to limit Range Limit during the Auto-tuning process
Load Disturbance Problem with the Measurement or Unstable Control Loop behavior – get the loop in
Controller Direction a stable state then start the Auto-tuning again
might be wrong
Tuning stopped
Large Noise Level
To be able to force the MV Value in the Faceplate, Write permission for MV.IOValue and
MV.Forced is needed, these are not set on IntPar Variables.
For the PIDCtrl the events that are tracked are for example, the mode changes (manual, auto,
auto external 1, auto external 2, manual external 1, manual external 2, balance mode), forced
conditions and actual value tracking which depends on the mode selection.
– Notice that the list you open from the faceplate will show only the alarms and events of
that PIDCtrl.
Notice that the structure of the event message is always the same.
For the alarm list, differently from the event list, shows only the active alarm. This means that
when all alarm conditions are off the list will be blank.
The severity of the alarm can be changed thru the following parameters:
Following the same rule for Analog/Digital input and output objects, the following rule is
valid for the alarm treatment:
Notice that alarms for the PIDCtrl are created only in the following cases:
– Deviation alarm, where it calculates the deviation from the actual setpoint to the meas-
ured value and checks if this value is higher than the limit defined in the faceplate over
Lim2 tab.
Object status and modes are presented on the event list. Whenever the object changes its
status or mode the complete information of the object at the time of the change is logged in
the event list.
The PIDCtrl event message has a dynamic structure, this means that it can change depending
on the case you have.
The first case regards to mode changes. When a mode is changed from one type to the other,
and event is set and the structure for that case is the following:
[MODE] Description
The MODE VALUE depends on which mode the Object currently is in. This means that when
you select a specific mode the event message will show the value that is relevant for that
mode, which are
Value for Aut Auto setpoint value set from the faceplate
Value for Man Actual output value from its last mode
The second case for events means when the relevant value for the mode changes. So for ex-
ample, an event is created when new setpoint value is set in Auto mode. In this case the event
message has the following structure:
In this case the same modes described right before are valid. Also OLD VALUE and NEW
VALUE is the value relevant for the specific active mode.
The third case for eventing is when some limit value is changed for some limits from the face-
plate. In this case the structure for the event message is the following:
L1 Low limit 1
L2 Low limit 2
H1 High limit 1
H2 High limit 2
The next case is when some limit is blocked from the faceplate. The structure for the event
message is the following:
– FRC Deselected
Alarm Messages
– Limit H2 or L2
– Limit H1 or L1
Notice that Process Limit (Plim) does not create any alarm. The maximum indication treat-
ment for the Process Limit is 0 (Event) as described in the parameter description in Control
Builder.
Dev High Deviation limit between MV (measured value) and SP (setpoint) is higher than defined over
Lim2 Tab
Dev Low Deviation limit between MV (measured value) and SP (setpoint) is lower than defined over
Lim2 Tab
Limit Value is the value defined in the Lim1 and Lim2 Tab for each Limit Type
3. PIDAdvCtrl
The PIDAdvCtrl does not have a CON_PU Pulse Controller, for digital 3-state Control the
PIDCtrl Module should be used instead.
3.2. Control
3.2.1. Library location
The Control Module Type for PIDCtrl is located in the library BMIAdvancedAnalog, its corre-
sponding Structured Data Types are defined in BMIConstAndVar.
1 Name string[24] 'Name' yes in INIT: Tag name of the PIDCtrl (allowed delimi-
nators are "." and "-", no blanks ":" or ";" al-
lowed)
4 Group GrpDrvCon default yes in_out IN/OUT: Connection to control module GROUP
left (sequencer)
7 E1ARef LoopCon- default yes in IN: External Setpoint for External Auto Mode 1
trolData
8 E2ARef LoopCon- default no in IN: External Setpoint for External Auto Mode 2
trolData
10 MV_FieldDevice dword 16#80C0 no in IN: 2nd DWORD for MV Field Device Status Su-
Status pervision e.g. Profibus PA Devices etc. If value
equals 16#80C0 the FPL indication is hidden
11 WSP LoopCon- default no out IN/OUT: Actual working setpoint of the PID
trolData CTRL
14 OUTP RealIO default no out IN/OUT: Output signal of the PID to connect at
AOX (only enabled if OUTCC is not connected!)
15 OUTCC LoopCon- default yes out IN/OUT: Output signal of the PID Loop
trolData
18 GrpStep1 dint cBMI.DINT_ yes in IN: Group Step 1 to to activate GrpMode1 (dur-
0 ing starting 1..999, during stopping 1001-1999,
0 not used.
20 GrpStep1Delay time cBMI.Time0 yes in IN: Activation / Deactivation delay for Group
s Step 1
21 GrpPreSelec- string[50] cBMI.Empty yes in IN: PreBins the consumer is assigned to. Syn-
tion1 _str tax: P1&P2|P3&N4 (= P1 AND P2 OR P3 AND
NOT P4). AND before OR. Max 5x OR. No
Spaces allowed.
24 GrpPreSelec- string[50] cBMI.Empty no in IN: PreBins the consumer is assigned to. Syn-
tion2 _str tax: P1&P2|P3&N4 (= P1 AND P2 OR P3 AND
NOT P4). AND before OR. Max 5x OR. No
Spaces allowed.
28 GrpPreSelec- string[50] cBMI.Empty no in IN: PreBins the consumer is assigned to. Syn-
tion3 _str tax: P1&P2|P3&N4 (= P1 AND P2 OR P3 AND
NOT P4). AND before OR. Max 5x OR. No
Spaces allowed.
30 AfterBalMode dint 1 no in IN: After balance set mode. [0= Last Mode,
1=Man, 2=Auto, 3=ExtMan1, 4=ExtMan2, 5=Ex-
tAuto1, 6=ExtAuto2]
32 EnMan bool TRUE no in IN true: Manual mode enabling (open loop con-
trol)
33 EnAuto bool TRUE no in IN true: Auto mode enabling (closed loop con-
trol)
36 ExtMan1Txt string[35] cBMI.Empty no in IN: Description text for ExtMan1 Mode, for NLS
_str support use ||AE_NLS_ prefix and no space in
the text
37 ExtMan2Txt string[35] cBMI.Empty no in IN: Description text for ExtMan2 Mode, for NLS
_str support use ||AE_NLS_ prefix and no space in
the text
38 ExtAuto1Txt string[35] cBMI.Empty no in IN: Description text for ExtAuto1 Mode, for
_str NLS support use ||AE_NLS_ prefix and no
space in the text
39 ExtAuto2Txt string[35] cBMI.Empty no in IN: Description text for ExtAuto2 Mode, for
_str NLS support use ||AE_NLS_ prefix and no
space in the text
46 ModeTr bool TRUE no in IN: True enables events on mode change [Man,
Auto, Ext, etc.]
49 EnExtPIDSet- bool FALSE no in IN: false = settings from Faceplate, true = ex-
tings ternal settings can be used (but no AutoTune
or GainScheduling)
50 PID_ASPTrackin bool TRUE no in COLD INIT true: Init Par.for PID auto setpoint
g tracking. [true = auto setpoint is tracking the
MV or ExtRefAuto]
51 PID_SPRampInc real 25 no in COLD INIT 25.0: Initial value for the speed of
the setpoint ramping function [%/s]
52 PID_SPRampDec real 25 no in COLD INIT 25.0: Initial value for the speed of
the setpoint ramping function [%/s]
53 PID_ASPTrackin bool TRUE no in COLD INIT: Faceplate parameter for PID auto
gExtAuto setpoint tracking when leaving ExtAutoModes
[true = auto setpoint is tracking the MV]
55 PID_MOUTPTrac bool TRUE no in COLD INIT true: Manual Setpoint Output track-
king ing. [true = output setpoint is tracking the
OUTP or ExtRefMan]
56 MV_ErrCtrl bool TRUE no in IN: Action in case of Signal Error on MV: false =
no action; true = MV.Value is forced to Err_Val
57 MV_ErrVal real 99999 no in IN: Error Value used in case of Err_Ctrl = true
59 MV_FilterTime real 0 no in COLD INIT 0.0: Initial value for the measured
value input filter.
60 MV_HiLim2 real 100 no in COLD INIT: Initial limit for High2 alarm.
61 MV_BlkHiLim2 bool FALSE no in COLD INIT: Initial value for blocking of the limit
high 2 handling
64 MV_HiLim1 real 100 no in COLD INIT: Initial limit for High1 alarm.
65 MV_BlkHiLim1 bool FALSE no in COLD INIT: Initial value for blocking of the limit
high 1 handling
68 MV_PHiLim real 90 no in COLD INIT: Initial limit for Process High alarm.
69 MV_BlkPHiLim bool TRUE no in COLD INIT: Initial value for blocking of the limit
Process High handling
72 MV_PLoLim real 10 no in COLD INIT: Initial limit for Process Low alarm.
73 MV_BlkPLoLim bool TRUE no in COLD INIT: Initial value for blocking of the limit
Process Low handling
77 MV_BlkLoLim1 bool FALSE no in COLD INIT: Initial value for blocking of the limit
low 1 handling
81 MV_BlkLoLim2 bool FALSE no in COLD INIT: Initial value for blocking of the limit
low 2 handling
86 DEV_HiLim real 50 no in COLD INIT: Initial limit for deviation high alarm
in [%]
89 DEV_LoLim real -50 no in COLD INIT: Initial limit for deviation Low alarm
in [%]
93 DEV_AlarmDelay time 0s no in COLD INIT: Initial time delay for the deviation
limit level supervision
97 SP_HiLim real 100 no in COLD INIT: Initial limit for setpoint high limit
98 SP_LoLim real 0 no in COLD INIT: Initial limit for setpoint low limit
99 EnExtOUTLimits bool FALSE no in IN: false = OUT limit settings from Faceplate,
true = COLD INIT Values can be used as exter-
nal limits
100 OUT_HiLim real 100 no in COLD INIT: Initial limit for output high limit
101 OUT_LoLim real 0 no in COLD INIT: Initial limit for output low limit
102 OUT_SpeedInc real 25 no in COLD INIT 25.0: Initial value for the maximum
change rate of the output signal [% / s]
103 OUT_SpeedDec real 25 no in COLD INIT 25.0: Initial value for the maximum
change rate of the output signal [% / s]
105 GrpStep1Over- bool TRUE no in IN true: If true, group does not go to hold if
ride PID is not in requested mode.
106 GrpStep2Over- bool TRUE no in IN true: If true, group does not go to hold if
ride PID is not in requested mode.
107 GrpStep3Over- bool TRUE no in IN true: If true, group does not go to hold if
ride PID is not in requested mode.
108 GrpReadyOnSi- bool FALSE no in IN false: If true, group shows ready even if a
gError signal error exists.
For Details on the PCC Interlock Parameters, see Basic Objects Manual, chapter PCC, Interlock
Bus (Process Control Connection)
PIDAdvCtrlData; components
PIDAdvCtrlInput; components
7 AEListEn bool retain true IN true: External Alarm List Enabling of AIS, temporary
nosort disabling of unack alarming and entries in alarmlist,
NOTE: Overwritten by PCC
8 AlarmEn bool retain true IN true: External Enabling of PIDCtrl Limit and Deviation
Supervision, used to te
9 PreSelStep1 bool retain true IN true: true = PID is pre-selected for GrpStep1, con-
hidden nected to PreBinData.PreSel in case parameterized Pre-
Selection is not used.
10 PreSelStep2 bool retain true IN true: true = PID is pre-selected for GrpStep2, con-
hidden nected to PreBinData.PreSel in case parameterized Pre-
Selection is not used.
11 PreSelStep3 bool retain true IN true: true = PID is pre-selected for GrpStep3, con-
hidden nected to PreBinData.PreSel in case parameterized Pre-
Selection is not used.
12 SetMan bool retain IN pulse: Set operation mode to Manual (open loop with
hidden output reference from FPL)
13 SetAuto bool retain IN pulse: Set operation mode to Auto (closed loop con-
hidden trol with setpoint reference from FPL)
16 SetExtAuto1 bool retain IN pulse: Set operation mode to external auto 1 (closed
hidden loop control with external output reference)
17 SetExtAuto2 bool retain IN pulse: Set operation mode to external auto 2 (closed
hidden loop control with external output reference)
19 EnModChng bool retain true IN true: External enabling of mode changes from FPL,
used to temporary disable mode changes
20 ExtRefMan1 real retain 0.0 IN: EXTernal REFerence Manual 1. Value is used as out-
put if open loop control ExtMan1 is selected.
21 ExtRefMan2 real retain 0.0 IN: EXTernal REFerence Manual 2. Value is used as out-
put if open loop control ExtMan2 is selected.
PIDAdvCtrlOutput; components
16 OUTP_H bool retain nosort OUT: Indication of output signal high limiting.
17 OUTP_L bool retain nosort OUT: Indication of output signal low limiting.
20 DEV_H BoolAL retain nosort OUT: Indication of DEViation > High alarm limit
21 DEV_L BoolAL retain nosort OUT: Indication of DEViation < Low alarm limit
24 ActPosErr bool retain nosort OUT: Indication Actuator Position Signal Error,
this stops CON PU
26 OscDetect bool retain nosort OUT: Set true when oscillation is detected
27 Slug- bool retain nosort OUT: Set true when sluggish behaviour is de-
gishDetect tected
29 ATWarn bool retain nosort OUT: true if Warning from Autotuner (tuning
failed)
30 FirstOrMax- string[32] retain nosort '' Tag Name of the IO Device with the first or high-
AETag est Alarm or Event causing an action on the Mo-
tor, Group or Valve
31 FirstOrMax- dint retain nosort 0 Indication treatment of the first or highest Alarm
AEIndTr or Event causing an action accroding to Minerals
Library Alarm Indication Standards
Auto Setpoint ASP Tracking ASP Tracking Ext Auto ASP Tracking
For the OUT Value in Manual Mode, the “Man Backtracking” Option decides if the internal Set-
point Value is tracking the Backtracking Value from OUTCC while in state Backtracking, other-
wise the OUT Value is kept on the current Setpoint.
For Min Reached / Max Reached state, in addition to the Backtracking behaviour the Out
Value is limited to the Backtracking Value as well.
3.3. Operation
3.3.1. Graphic Elements
The Graphic Elements are equal to PIDCtrl, please refer Chapter Error! Reference source not
found. .
3.3.2. Faceplate
Default View
Abbr. Description
Block Limit Any MV Limit Value Alarm is disabled from Application or by PCC Parent
Abbr. Description
MV Measured value
SP Setpoint value
Ramping of
Setpoint Drop
Down Tab
Current
Setpoint
for
Linked to E1Mode
consumer
controlled by
this PI-
DAdvCntrl
The Tabs on the right side of the faceplate first extended view are same as PIDCtrl Tabs:
Tab Description
Trend Online trend of measured value, controller output and setpoint value
Group Corresponding Drive Group settings and link to the Group Sequence
IOStatus Substatus for MV, OUT ACT and Field Devices connected to MV
OUT Range Output Range Parameter Override settings
Active Parameter
Gain Scheduling
Enable/Disable-
Limit Values for
Gain Shedule
the Reference
Value to select
the Active Set
Selected for
Par/feedforward
Bargraph indi-
cating the Refer-
Selected PV Value ence Value : Ac-
tive Set1 Seleted
GS Description
Abbr. Description
Pv Measured value
Sp Setpoint value
Parameters
NOTE: If Gain Scheduling is enabled, these settings are for the currently selected Set only.
Par Description
Controller Type Enable / Disable the Gain Scheduling Function. On Disabling, the Parameters
from the currently active set will be kept only.
Cont Sp Weight Setpoint Weight Factor (β) for Proportional Action in External Auto Mode
Discont Sp Weight Setpoint Weight Factor (β) for Proportional Action in Auto Mode
Derivation filter time Time constant for first order Filter on MV for Derivative Action
pPI dead time Controller Dead Time Parameter for PPI Controller Type
Feedforward
NOTE: If Gain Scheduling is enabled, these settings are for the currently selected Set only.
Par 2 Description
Feedforward adaption Adaptive Controller based on Feedforward value (changes Controller Param-
eters during Runtime)
Tune Description
Tune Method The Autotuner Method used, Standard is “Relay”, “Step” method is only advisable after
Relay Tuning to compensate for dead time in the process
Reset If set, the last used relay amplitude and noise level are discarded, otherwise they are
used as initial Values for the Auto-Tuning which can speed up the Tuning Process
Max relay amp Restrict the maximum change of the Output during Auto-tuning (for Relay method)
Max SP step Restrict the maximum change of the Setpoint during Auto-tuning (for Step method)
Warning time The PIDAdvCtrl will issue a Warning if the Auto-tuning process doesn’t finish in the con-
figured time
Max sample time The maximum Task Cycle Time the Control Loop should be executed, this equals 1/8 of
the Process Oscillation Time determined by the Autotuning
Tune Results
Controller De- Type of the Controller, defined by the Auto-tuning but can be changed later with the Pro-
sign posed Parameters being adjusted accordingly
Response Choose “Slow”, “Normal” or “Fast” to adjust the Proposed Parameters to the required Con-
troller reaction
Parameters Description
Direction Reverse Controller reaction Direct (OUT increase for positive Deviation) or Reverse (OUT
increase for negative Deviation)
Offset Adjustment Automatically adjust the Offset to get Bumpless Transfer on Mode or Parameter
changes, applicable for Controller Type P and PD only
Max pPI dead time Maximum Limit for dead time Parameter, used for Controller Type pPI only
MV Filter Time constant for First-order Low Pass Filter on Measured Value
ASP tracking Auto Setpoint will track Measured Value while in Manual, ExtMan1 or ExtMan2
Mode
ASP tracking ExtAuto Auto Setpoint will track current Setpoint while in ExtAuto1 or ExtAuto2 Mode
Man tracking OUT Manual Mode OUT Value will track the current OUT Value while not in Manual Mode
Man Backtracking In Manual Mode, the OUT Value as set from Faceplate will track the Backtracking
Value while in Backtracking Mode
4. RatioCtrl
The RatioCtrl Module calculates an LCC Connection Setpoint from an Input Value with Gain
and Offset.
– Full LCC Support for Backtracking from the Output back to the Input Value
– Auto and Manual Mode (Output Value Reference can be overwritten from Faceplate)
– Internal and External (from Control Application) Setpoint Mode independent for both Gain
and Offset
– Configurable First order Low Pass Filter, Range and Change Rate Limitation on the Output
Value
4.1. Control
4.1.1. Library location
The Control Module Type for RatioCtrl is located in the library BMIAdvancedAnalog, its corre-
sponding Structured Data Types are defined in BMIConstAndVar.
4.1.2. Modes
Auto: The OUT Value is defined by IN * Gain + Offset in this Mode.
Manual (Man): The OUT Value is defined from the Setpoint given in the RatioCtrl Faceplate it-
self, Gain and Offset are ignored in this Mode.
External Gain (G Ext): The Gain is defined from the Application at IO.In.GainRef
External Offset (OfExt): The Offset is defined from the Application at IO.In.OffsetRef
1 Name string[24] in yes 'Name' INIT: Tag name of the RatioCtrl (allowed
deliminators are "." and "-", no blanks ":" or
";" allowed)
5 Out LoopControlData out yes default OUT(IN): Output Setpoint from Ratio
21 EnExtOutLimits bool in no false IN: false = limit settings from Operate IT,
true = COLD INIT can be used as external
limits
22 Out_HiLim real in no 100 COLD INIT: External and initial high limit
for output limitation
23 Out_LoLim real in no 0 COLD INIT: External and initial low limit for
output limitation
RatioCtrlData; components
RatioCtrlInput; components
1 SetMan bool retain IN: Set Manual Mode (Internal OUT Refer-
ence from Faceplate)
2 SetAuto bool retain IN: Set Auto Mode (Out = In * Gain + Off-
set)
3 SetGainInt bool retain IN: Set Gain Internal Mode (Gain set from
Faceplate)
4 SetGainExt bool retain IN: Set Gain External Mode (Gain set from
IO.In.ExtGainRef)
5 SetOffsetInt bool retain IN: Set Offset Internal Mode (Offset set
from Faceplate)
6 SetOffsetExt bool retain IN: Set Offset External Mode (Offset set
from IO.In.ExtOffsetRef)
RatioCtrlOutput; components
1 Man bool retain nosort false OUT: true if Output is defined from Face-
plate
2 Auto bool retain nosort false OUT: true if Output is In * Gain + Offset
3 GainExt bool retain nosort false OUT: true if Gain is defined from
IO.In.ExtGainRef, otherwise from FPL
4 OffsetExt bool retain nosort false OUT: true if Offset is defined from
IO.In.ExtOffsetRef, otherwise from FPL
6 HLim bool retain nosort false OUT: Out High Limit reached
7 LLim bool retain nosort false OUT: Out Low Limit reached
8 SigErr bool retain nosort false OUT: Input Signal Error (forwarded to
Output)
Setpoint (connected to OUT) need to support Backtracking as well. In Manual Mode, Back-
tracking can be controlled via the “Man Backtracking” Option from the Faceplate.
Backtracking
The internal Value is initialized with the Backtracking Value, Ramp and Filter will therefore
start from the Backtracking Value again. Note that the RatioCtrl will apply the Filter and
Ramp independent of the Input supporting Backtracking, in order to allow implementing
Bumpless behavior for Loops without Backtracking by connecting a RatioCtrl in between. In
case the Output Object is Backtracking, the Output Value can therefore deviate from the cal-
culated Output with the Input Value.
In Manual mode, while the “Man Backtracking” Option is set the Manual Setpoint will track
the Backtracking Value, otherwise the Backtracking Value is ignored.
In addition to the Backtracking behavior, the Out Value is limited to the Backtracking Value as
well.
4.2. Operation
4.2.1. Graphic Element for ration Control
Only one graphic element is available for the RatioCtrl:
Properties
EnableBackAppearance Boolean False Switch on the value and unit back appearance
EnableLogicalColor Boolean True If its true, then all used colors are logical colors. The
logical color ref is equal to the default logical color
used in the color properties. To use an individual
color set it to false.
4.2.2. Faceplate
Default View
Normal View
Abbr. Description
IN Input value
Normal View
RatioCtrl is in
Auto Mode
Backtracking
Enabled
Mode
Selected Mode
Selected Inter-
nal Gain Value
Selected Inter-
nal Offset Value
Trend
Record Time
Show/Hide
Trace
Show/Hide Grid
OUT Limits
ROC Limitation
for Output
Filter Time Time Constant for First Order Low Pass Filter on OUT
Man Tracking OUT Manual OUT Setpoint to follow OUT Value while in Auto Mode
Man Backtracking Manual OUT Setpoint to follow Backtracking Value while Backtracking
OUT Range
Scale to OUT Range Scale OUT Value from Internal Range (In Range * Gain Range or below defined
Range if “Override Range” is selected) to Range defined backwards via LCC Con-
nection
Override Range Select to override the Range and Unit for OUT with the Values defined in Faceplate
Range Min Range Minimum Limit for OUT – active only if Override Range is selected
Range Max Range Maximum Limit for OUT – active only if Override Range is selected
Unit Engineering Unit for OUT – active only if Override Range is selected
Number of Decimals Number of Decimals shown for OUT – active only if Override Range is selected
The RatioCtrl event message has a dynamic structure, this means that the structures change
depending on the status. If the RatioCtrl is not in Backtracking status, the Event Message
looks like:
[MODE] Description
In case the RatioCtrl is Backtracking, the event message has the following structure:
[STATUS] Description
Backtracking The Value connected on the OUT Port is in Backtracking mode and the Backtrack-
ing Value is used as Setpoint
5. SplitRange
The SplitRange Control Module divides an LCC Connection Input, e.g. from a PIDCtrl, into two
Setpoints to e.g. two Actuator Objects in a Valve Split-Range Configuration.
5.1. Control
5.1.1. Library location
The Control Module Type for SplitRange is located in the library BMIAdvancedAnalog, its cor-
responding Structured Data Types are defined in BMIConstAndVar.
SplitRangeData; components
If only one of the Outputs is in Backtracking, the In will be limited to the configured Range of
the still working Output (Min Reached / Max Reached is sent if outside the Range), independ-
ent of the Backtracking Value of the Output.
If both Outputs are in Backtracking, the Value of Out1, scaled to the corresponding input
value, is sent for Backtracking to In, while Out2 is ignored. In this situation, if Out2 is released
(not Backtracking anymore) while Out1 is still Backtracking, the Backtracking Value is modi-
fied to keep Out2 Value continuous.
5.2. Operation
Three graphic elements are available for the SplitRange
Properties
EnableBackAppearance Boolean False Switch on the value and unit back appearance
EnableLogicalColor Boolean True If EnableLogicalColor is true, then all used colors are
logical colors. The logical color reference is equal to
the default logical color used in the color properties.
To use an individual color set it to false.
LimitValueEnum
Value Description
5.2.3. Faceplate
The following aspect view buttons are available on Actuator Faceplates
Default View
Output to
Input to Split Range Second Valve
Normal View
Reduced View
Normal View
Function Plot
Out 2
Out 1
Input
This Plot shows the Values for OUT1 (left side vertical Axis) and OUT2 (right side vertical Axis)
for all possible Input Values (Bottom, horizontal Axis). The Bar Elements show the current Val-
ues.
OUT1 Settings
Input for OUT min Value for IN (in percentage) where OUT1 will be set to its minimum Range Value (0%
OUT)
Input for OUT max Value for IN (in percentage) where OUT1 will be set to its maximum Range Value
(100% OUT)
Override Range Select to override the Range and Unit for OUT1 with the Values defined in Faceplate
Range Min Range Minimum Limit for OUT1 – active only if Override Range is selected
Range Max Range Maximum Limit for OUT1 – active only if Override Range is selected
Unit Engineering Unit for OUT1 – active only if Override Range is selected
Fraction Number of Decimals shown for OUT1 – active only if Override Range is selected
The Values for Range Min/Max, Unit and Number of Decimals can only be edited while Over-
ride Range is set, otherwise they are overwritten with the currently active Values.
OUT2 Settings
Input for OUT min Value for IN (in percentage) where OUT2 will be set to its minimum Range Value
(OUT2 at 0%)
Input for OUT max Value for IN (in percentage) where OUT2 will be set to its maximum Range Value
(OUT2 at 100%)
Override Range Select to override the Range and Unit for OUT2 with the Values defined in Faceplate
Range Min Range Minimum Limit for OUT2 – active only if Override Range is selected
Range Max Range Maximum Limit for OUT2 – active only if Override Range is selected
Unit Engineering Unit for OUT2 – active only if Override Range is selected
Fraction Number of Decimals shown for OUT2 – active only if Override Range is selected
6. Revisions
Rev. Page (P) Description Date Dept./Init.
Chapt. (C)