PCS 7 Advanced Process Library (V9.1 SP2) 2-Basics of APL (47-390)
PCS 7 Advanced Process Library (V9.1 SP2) 2-Basics of APL (47-390)
Note
If you have set the parameters for the advance warning time WarnTiMan and the idle
time IdleTime to values higher than 0, the control will only take effect once the set times have
elapsed.
Note
With block VlvAnl, the warning time is ignored in tracking MV_TrkOn = 1 and in forced
tracking MV_ForOn.
The Enabling direct changeover between forward and reverse (Page 158) Feature bit has no
effect when forcing the operating modes of the MotRevL and MotSpdCL blocks. Direct
switchover between forward and reverse is always possible.
Messaging
No messages are assigned to the forcing of operating modes. However, if you want to have
corresponding messages, you can use the freely interconnectable input parameters to generate
the messages. Refer also to the Generating instance-specific messages (Page 234) section for
more on this.
Note
"Small" blocks do not feature protection (Protect).
The RdyToReset output signals when a reset can be carried out via the RstLi input parameter
or the automatic commands.
There are different ways to reset the block:
• Reset by interconnection (input RstLi).
• Reset by the operator using a button in the faceplate (input RstOp).
• Reset with a 0-1 edge transition in the corresponding automatic or local signal (except with
motor protection). Refer to the following sections for more information.
Note
The reset via input RstLi or RstOp does not depend on the selected operating mode.
The operator must have the appropriate authorization to use the reset function in the faceplate
(OS_Perm). After a reset, the output parameter P_Rst is set for a cycle.
Note
Note for VlvMotL and VlvPosL
After resetting the block, in the case of interlocks or errors, the valve position will always be
tracked, depending on FbkOpen and FbkClose.
Resetting monitoring errors, external errors and interlocks using the "Forcing operating states"
function
With "Forcing operating states", monitoring errors, external errors, interlocks or the motor
protection function are reset under the following conditions and a reset pulse is output at
the P_Rst output:
• The block is in an operating mode in which a reset is necessary and
• a monitoring error, an external error, a "Protection" interlock or the motor protection function
is ready to be reset. This can be seen in the faceplate with the reset button or with the Request
0/1 indicator in the faceplate. When Feature.Bit19 = 1, the block is ready to reset as soon
as the protection (Protect = 0) or motor protection (Trip = 0) interlock is set,
whereby enabled motor protection prevents the motor from starting.
See also the following chapter: Forcing operating modes (Page 47).
Neutral position for continuous controllers (does not apply to controller modules)
• Only the limits or a special analog value for the manual value are taken into consideration for
the neutral position with continuous controllers.
The input parameter SafePos is used to specify the neutral position:
– SafePos = 0 corresponds to the low limit (ManLoLim or MV_LoLim for PIDConS)
– SafePos = 1 corresponds to the high limit (ManHiLim or MV_HiLim for PIDConS)
• The input parameters SafePos and SafePos2 are used to determine the neutral position:
x: Not relevant
Neutral position for step controllers (does not apply to controller modules)
You can use the input parameter SafePos to determine if the step controller should close, open
or stop the valve when it enters the neutral position:
SafePos = 0: close valve
SafePos = 1: open valve
SafePos = 2: stop valve
When the neutral position (fully opened or fully closed) is reached and a limit stop signal
(FbkOpened or FbkClosed) is set, the valve is stopped (Stop = 1).
The neutral position is adopted:
• during start-up if the Feature bit Set startup characteristics (Page 150) and the Feature
bit Neutral position manipulated variable takes effect at startup (Page 179) are set.
• in the "Out of service" mode if the Feature bit Neutral position manipulated variable takes
effect with "out of service" operating mode (Page 179) is set.
2.1.1.5 Specifying warning times for control functions at motors and valves
A corresponding warning is not output if the warning times (WarnTiMan or WarnTiAut) are
specified with a smaller value than the SampleTime parameter.
Note
In this case, the warning time is only active if the block is controlled from the de-energized state.
Disabling warnings
Configure each parameter with 0 seconds to generate no warnings.
Note
The pulse signal is available only for the "large" blocks.
Fwd
P_Fwd
PulseW idth
Rev
P_Rev
PulseW idth
P_Stop
PulseW idth
Note
Almost all output parameters for pulse control, for example P_Fwd, P_Rev, P_Ctrl, have a
positive effective direction, i.e. a 0→1→0 pulse triggers activation.
The only exception is the P_Stop output parameter with a negative effective direction, i.e. a
1→0→1 pulse triggers activation.
)HHGEDFNHUURU
0RQ[[[(UU
*URXSHUURU
!
*URXSIDXOWWDNLQJLQWRDFFRXQW
([WHUQDOHUURU
*US(UU ZLWK&6) )HDWXUH%LW
&6)
)HDWXUH%LW $XWR
([WHUQDOHUURU !
)DXOW([W
0RWRUSURWHFWLRQ
7ULS
5HDG\WRSRZHUXSLQDXWRPDWLF
:DLWWLPHIRUUHVWDUWH[SLUHG
ODUJHEORFNVRQO\
%ORFNLQDXWR
5G\7R6WDUW
$XW$FW
)RUFLQJRSHUDWLQJPRGHV
ODUJHEORFNVRQO\
[)RUFH,QSXW$FWLYH
%ORFNQRWLQWHUORFNHG
/RFN$FW
5DSLGVWRSQRWDFWLYH
ODUJHEORFNVRQO\
5B6WS$FW
Figure 2-1 Output signal for start readiness for motors
*URXSHUURU
)HHGEDFNHUURU
0RQ[[[(UU
9OY0RW/0RWRUSURWHFWLRQ
7ULS ! *US(UU
([WHUQDOHUURU
&6)
([WHUQDOHUURU
)DXOW([W
*URXSIDXOWWDNLQJLQWRDFFRXQW
0RQ6DIH3RVDQG)HDWXUH%LW
0RQ6DIH3RV
!
)HDWXUH%LW $XWR
5HDG\WRSRZHUXSLQDXWRPDWLF
9OY0RW/:DLWWLPHIRUUHVWDUW
H[SLUHG
%ORFNLQDXWR
5G\7R6WDUW
$XW$FW
)RUFLQJRSHUDWLQJ
PRGHV
ODUJHEORFNVRQO\
[)RUFH,QSXW$FWLYH
%ORFNQRWLQWHUORFNHG
/RFN$FW
9OY0RW/5DSLGVWRSQRW
DFWLYH
5B6WS$FW
Figure 2-2 Output signal for start readiness for valves
([WHUQDOHUURU )DXOW([W !
([WHUQDOHUURU &6) *US(UU
5HDG\WRSRZHUXSLQDXWRPDWLF
)HDWXUH%LW $XWR
%ORFNLQDXWR
5G\7R6WDUW
$XW$FW
)RUFLQJRSHUDWLQJ
PRGHV
[)RUFH,QSXW$FWLYH
%ORFNQRWLQWHUORFNHG
/RFN$FW
'RVLQJVWDWXV
1RWUDFNLQJ
'RV5HOD[
1RQH
8QGHUGRVLQJ
'4B$/B$FW
4XDQWLW\QRWUHDFKHG !
'4B2XW'4B63
5HVHWWLQJWKHGRVDJH
TXDQWLW\DWGRVDJHVWDUW
)HDWXUH%LW
([WHUQDOHUURU *US(UU
&6)
5HDG\WRRSHUDWH
5G\7R6WDUW
)RUFHGPDQLSXODWHG
YDULDEOHQRWDFWLYH
09B)RU2Q
Figure 2-4 Output signal for start readiness for software controllers
0RGXOHHUURU
0RG(UU
*URXSHUURU
!
,2DFFHVVHUURU
*US(UU
3HU$FF(UU
&RQILJXUDWLRQHUURU
3DU)0B(UU
([WHUQDOHUURU
&6)
5HDG\WRVWDUWLQDXWRPDWLF
5G\7R6WDUW
)RUFHGPDQLSXODWHG
YDULDEOHQRWDFWLYH
09B6DIH2Q
Figure 2-5 Output signal for start readiness for hardware controllers
Simulating signals
Simulation means the manipulation of a signal regardless of the actual source of the signal or
logic that generates this signal.
Simulation is carried out either at the field device (externally from the control system) itself or
at a block (internally in the control system).
In either case, the associated status in the signal is set to the simulation value (see also Forming
and outputting signal status for blocks (Page 118)).
During the simulation, every block is considered in isolation. There are two different forms of
simulation here, namely:
• Block-external simulation and
• Block-internal simulation.
Block-external simulation
Block-external simulation is characterized by the fact that:
• The simulation function is not executed in the block itself and
• A signal whose status has the simulation state, for example, a simulation of the signal at
another block or directly in the I/O device, is applied at an input parameter.
The block-external simulation has the following effects on the functionality of the block:
• The technological functions are not influenced
• All the process-relevant output signals do not receive the simulation status. In the case of
technologic blocks, process-related output signals are parameters that actively affect the
process, e.g. "Start" for block MotL.
• In the case of blocks with operator control or monitoring functions (for example faceplates),
these signals are identified in the faceplate with the status for the simulation as follows:
• Blocks with one or more input parameters for signals with "Generate status from individual
status" receive a group status in accordance with the priority table. This group status is
displayed in the status bar of the block icon and of the faceplate with the simulation status
as follows:
Block-internal simulation
Block-internal simulation is characterized by the "simulation" function being run in the block
itself.
With operator control and monitoring blocks, all process values that cannot be controlled (e.g.
PV, AV, In) can be simulated. This is used primarily as an aid for commissioning and servicing
of the system. For example, the control settings of a motor can be simulated and the feedback
values corrected without the monitoring functions being active.
For specific technological blocks (e.g. large blocks) that can be operated and monitored,
simulation can take place via the faceplate as well as interconnectable inputs:
- SimLiOp = 0: The simulation is activated/deactivated via faceplate (parameter view) at the
input SimOn.
- SimLiOp = 1: The simulation is activated/deactivated via the input SimOnLi. The
interconnectable simulation values (e.g. SimPV_Li, SimAV_Li, SimInLi) will become
effective in the process. In this case, the inputs SimOn, SimPV, SimAV, SimIn, SimRbk are
written back with SimOnLi, SimPV_Li, SimAV_Li, SimInLi, SimRbkLi.
The Feature bit Activating the run time of feedback signals (Page 166) can be used to delay
tracking of the feedback signals for motors and valves (for example, Fbkxxx).
Simulation can also be carried out for blocks (such as channel blocks) that cannot be controlled
and monitored by the operator.
The control is simulated in the CFC by setting parameters directly in the block with the input
parameters SimOn = 1 and Simxxxx = for the desired simulation value (e.g. SimPV , SimAV
or SimIn).
Note
With channel blocks, ensure that the Mode parameter is set correctly during simulation.
Note
If the block is not in simulation, the simulation values (SimPV, SimAV, SimIn, SimRbk) are
updated to the process values (PV, AV, In, Rbk).
Simulation is triggered during runtime in the faceplate's parameter view by clicking on the
"Simulation" button.
This simulation is characterized by the fact that:
• The simulation can only be enabled / disabled with the operator authorization level for
system authorization.
• The technological functions are not influenced.
• All the process-related output signals receive the "simulation" status. In the case of
technologic blocks, process-related output signals are parameters that actively affect the
process, e.g. "Start" for block MotL.
• In the case of blocks with operator control or monitoring functions (for example faceplates),
these signals are identified in the faceplate with the status for the simulation as follows:
• The group status of the block is displayed in the status bar of the block icon and of the
faceplate with the simulation status as follows:
• All the process values displayed in the faceplate that cannot be operated-controlled in normal
operation (e.g. PV).
• When the block control can be manipulated, the readback and feedback values (for
example Rbk, FbkSpd1) are adjusted according to the manipulation of the control.
• Associated values (for example UserAna1) cannot be simulated.
• The interlocking functions of the block are activated in accordance with input
parameter BypProt = 0 or deactivated (BypProt = 1). This is shown as follows in the
faceplate and block icon:
Enabled
Disabled
Note
If you switch a controller block to block-internal simulation during automatic mode and the
controller is connected to the actual process on the actuator side, you will open the control loop
as a result.
The actuating signals calculated on the basis of the simulated actual value are switched to the
process, but the resulting motion in the process is no longer visible in terms of the controller
actual value, as a copy of the setpoint is present at this point instead, where it takes the form of
a simulated actual value. The process could move away from the setpoint without the controller
doing anything to counteract this and without you seeing this happen in the controller faceplate.
Manipulated variable step changes occur during switchover to automatic mode if an error signal
was already present before the switchover.
Dead band
To suppress values fluctuating around zero, you can set a dead band (Deadband):
39B2XW
>'HDGEDQG@
39
>'HDGEDQG@
6\VWHPDUHD 8VHUDUHDൺ0HDVXULQJSRLQWWHPSODWH
$66(7)DFHSODWH 2SHUDWRUUHTXHVWH[WHUQDOPHVVDJH
2SHUDWRUUHTXHVW
06B5HT ([W0VJ[
&RQQHFWWRWKH
06B5(4 ';&+*B;; ';&+*B;; H[WHUQDOPHVVDJH
$3/
'LDJQRVWLFGULYHU $3/LQSXW
WHFKQRORJLFDO
02' FKDQQHOEORFN
EORFN
• The output parameter MS_Req of the channel block will be set to 1 when an operator issues
a maintenance request in Maintenance view of the ASSET faceplate.
• The output parameter MS_Req has to be connected to the input parameter ExtMsgx of the
desired technological block for which the user wants to issue an operator request message.
• The operator has to configure the "Message class" and enter a suitable text in the "Event"
field for the operator request message in the "PCS 7 Message Configuration" window of the
technological block.
• With the configured message and issued maintenance release, the maintenance operator
can start the maintenance.
• The operator request message stays active until the user changes to "In service" or "Cancel"
mode in the Maintenance view of ASSET faceplate.
• Once the maintenance is done, the operator can change the mode to "Completed". This
will deactivate the "In service" mode (OosAct = 0).
Note
The block must be in either "Manual," "On" or "Out of service" mode to set the release for
maintenance.
You set the release for maintenance (operator control permission "System control" required) in
the parameter view using the input parameter MS_RelOp = 1. A release for maintenance is
then made available via the interconnectable output parameter MS_Release = 1 for further
processing. In order to make this information of the Maintenance Station available, you have to
interconnect the output parameter MS_Release of the technologic block with the input
parameter MS_Releaseof the corresponding channel block.
The issuing of a release for maintenance does not have any influence on the function of the
block. An operation message is generated.
Display Meaning
In progress
• The channel block signals the release for maintenance to the diagnostics block via the DXCHG
parameter.
• The release for maintenance is only signaled to the Maintenance Station once all 0 bits of the
parameter DXCHG_XX are set on the diagnostics block.
• The channel block determines the "in progress" state of the Maintenance Station using
the MS input parameter and makes this information available at the OosAct output
parameter.
• On the technologic block, the "working" state is displayed at input parameter OosLi and
forwarded for display to the faceplate.
6\VWHPDUHD 8VHUDUHDà3URFHVVWDJWHPSODWH
202'(B 0RGH
39B2XW 39
202'(B ';FKJ
06 ';&+*B
'HWHUPLQHLQSURJUHVV
';&+*B 09
VWDWXVIURP06
$3/
$3/LQSXW
WHFKQRORJLFDO
'LDJQRVWLFGULYHU FKDQQHOEORFN EORFN
02'
3,,
(;7B67$7 06B5HOHDVH
39B2XW
202'(B 0RGH
202'(B ';FKJ
06 ';&+*B
'HWHUPLQHLQSURJUHVV
';&+*B
VWDWXVIURP06
2B06 06 2RV$FW
39B,Q
$3/RXWSXW
'LDJQRVWLFGULYHU FKDQQHOEORFN
02'
3,4
Key to diagram:
Note
For additional information on the topic of maintenance please refer to PCS 7 OS process
management.
Flutter suppression
The time-controlled "Flutter suppression" function is used to delay the outgoing of a message by
a configurable period.
Flutter suppression is used for
• OB82 events - diagnostic messages
• OB83 events - fault
used.
The flutter time is entered at the channel block at the FlutTmIn parameter. The high byte of the
DataXchg parameter of the channel blocks contains the flutter time.
Flutter suppression comes into effect when FlutEN = 1 and FlutTmIn > 0 is set at the channel
block.
There is only one flutter message per module. The delay times and fault messages are channel-
specific. The fault messages are extended by at least the delay time. Flutter occurs when the
status of fault messages changes from "Outgoing" back to "Incoming" within the delay time.
The last fluttering channel and its set delay time deactivates the flutter message.
Note
Note that the operating modes are realized differently in the individual block families.
2.1.2.2 On
outgoing messages are generated. The only function still possible is an operating mode
switchover.
All outputs for motors and valves are set to the neutral position in this operating mode.
The timer for the function "Restart disable after the shutoff of motor (Page 1774)" is reset in this
mode.
Note
Notes on VlvMotL and VlvPosL
If the neutral position of is "Closed" or "Open", the corresponding control outputs "Closed" or
"Open" are set. The control outputs are reset after reaching the neutral position or with an active
torque signal. The "Seal valve" function (Feature.Bit8) is a component.
Note
Note on VlvMotL
If the timer of the "Restart disable after the shutoff of motor (Page 1774)" function is running and
the block is not in the neutral position, it is not possible to switch to "Out of service" mode.
Note
For the RbkOut.ST parameter, the status is set to "Out of service (OOS)" in the moment of
change and not in every cycle of OOS.
For controllers, the neutral position manipulated variable (high or low manual limit of the
manipulated variable) is only used if the Feature bit Neutral position manipulated variable
takes effect at startup (Page 179) is active. Otherwise the manipulated variable remains at the
latest value like all the other output parameters.
See also the section Neutral position for motors, valves and controllers (Page 56) for more on
this.
The last value available is output permanently for all other blocks.
Display Meaning
In progress
See also the section Release for maintenance (Page 72) for more on this.
6HOHFWLRQRIPDQXDODXWRPDWLFRSHUDWLQJPRGHZLWK
0RG/L2S 0RG/L2S
0DQXDOPRGH $XWRPDWLFPRGH
Switchover initiated in the faceplate (ModLiOp = 0): The switchover between operating
modes is carried out in the standard view of the faceplate. In the function block, the parameters
ManModOp for "manual mode" and AutModOp for "automatic mode" are used.
If both signals (ManModOp =1, AutModOp = 1 ) are set, ManModOp = 1 has priority.
Switchover per interconnection (CFC or SFC instance) (ModLiOp = 1): The switchover
between the operating modes is carried out with an interconnection on the function block. The
parameters ManModLi for "manual mode" and AutModLi for "automatic mode" are used in
pushbutton operation. In switching mode (requirement: Feature.Bit4 = 1, see Setting
switch or button mode (Page 180)) connection AutModLi is used exclusively.
If both signals (ManModLi =1, AutModLi = 1 ), the previous operating mode is retained and
the ErrorNum output is assigned with the error number 51.
Note
You can access the variable parameters AutModOp and ManModOp from a normal SFC (in
contrast to the instance of an SFC type). The SFC can thus change the operating mode without
revoking the access rights of the operator (i.e. without setting ModLiOp = 1).
2.1.2.5 Manual and automatic mode for motors, valves and dosers
6HOHFWLRQRIPDQXDODXWRPDWLFRSHUDWLQJPRGHZLWK
0RG/L2S 0RG/L2S
0DQXDOPRGH $XWRPDWLFPRGH
Note
The two selections (manual and automatic) cannot both be set to "1" in switching mode.
Switchover using faceplates (ModLiOp = 0): The switchover between operating modes is
carried out in the standard view of the faceplate. In the function block, the parameters
ManModOp for "manual mode" and AutModOp for "automatic mode" are used.
Switchover per interconnection (CFC or SFC instance) (ModLiOp = 1): The switchover
between the operating modes is carried out with an interconnection on the function block. The
parameters ManModLi for "manual mode" and AutModLi for "automatic mode" are used in
Note
The Feature.Bit4 is available only for the "large" blocks.
Note
You can access the variable parameters AutModOp and ManModOp from a normal SFC (in
contrast to the instance of an SFC type). The SFC can thus change the operating mode without
revoking the access rights of the operator (i.e. without setting ModLiOp = 1).
Note
For VlvAnL, the bumplessness of the switchover depends on the parameter MV_TrkExt.
Note
The output parameters ManAct or AutAct display the mode to which the controller changes
with a 1 - 0 edge transition.
The output parameter AdvCoRdy = 1 indicates if the PID controller is ready to switch to
program mode. At a central control block, you can use an AND operation for all AdvCoRdy
signals of the downstream controllers to enable central switchover.
The output parameter AdvCoAct = 1 indicates of the block is in program mode.
Note
Differences between "Large" and "Small" blocks
The operating mode described here is valid for "Large" blocks. For "Small"
blocks, LocalSetting can be configured only on a limited basis. For more information, refer
to the respective description for the operating modes of the blocks.
VlvAnL: The auxiliary valve is controlled via internal tracking of the feedback
signals FbkAuxVCloseOut and FbkAuxVOpenOut. The control of the main valve via
the feedback value Rbk is not affected by this.
The texts for labeling the command buttons in the faceplates of the motor and valve blocks can
now be assigned for each specific instance.
The configuration of the texts is performed with the "Text 1" property of the respective control
inputs of the motor and valve blocks in the CFC.
If no instance-specific text is configured, the previous default texts are used and displayed in the
faceplate.
The following table shows the assignment of the command buttons to the corresponding block
input:
The interlock functions of the block are deactivated.
2XWRIVHUYLFH
0DQXDO
2Q
3URJUDP /RFDO
PRGH
$XWRPDWLF
* This operating mode is used for motors, valves, and dosing units.
** This operating mode is used for controllers only.
Note
The message classes Alarm, Warning and Tolerance are not valid for user-configured message
classes. Please take into consideration the validity of terms for user-configured message classes
(Page 47).
Note
Special note for "Small" blocks
"Small" blocks provide only the monitoring for alarms and warnings.
39B2XW
39B;;B/LP
39B+\VW
3URFHVVYDOXH
39B<<B/LP 39B+\VW
7LPH
39B;;B$FW
39B<<B$FW
You can use Feature.Bit29 Signaling limit violation (Page 184) to determine whether the
output parameter triggers limit monitoring with the value "0" or "1".
You can use Feature.Bit28 Disabling operating points (Page 158) to disable limit monitoring
when message suppression is enabled (MsgLock = 1).
Message suppression
Hysteresis
You can specify a hysteresis (PV_Hyst) for the limits, for example, to suppress signal flutter.
Refer to the Limit monitoring with hysteresis (Page 106) chapter for more on this.
Alarm delays
You can set alarm delays for incoming and outgoing alarms, warnings and tolerances. Refer to
the Area of application of the alarm delays (Page 229) chapter for more on this.
See also
Two time values per limit pair (Page 231)
Two time values for each individual limit (Page 232)
User-configured message classes (Page 47)
Note
Monitoring the limits
The limits monitored depend on the direction of counting:
• In Mode 1 (summing up or integrating), the high limits are monitored:
– OutAH_Lim
– OutWH_Lim
– OutTH_Lim
• In Mode 2 (summing down or integrating), the low limits are monitored:
– OutAL_Lim
– OutWL_Lim
– OutTL_Lim
Message suppression
The corresponding message is suppressed using the parameters:
• OutAH_MsgEn = 0: Alarm (high) messages are suppressed
• OutAL_MsgEn = 0: Alarm (low) messages are suppressed
• OutWH_MsgEn = 0: Warning (high) messages are suppressed
• OutWL_MsgEn = 0: Warning (low) messages are suppressed
• OutTH_MsgEn = 0: Tolerance (high) messages are suppressed
• OutTL_MsgEn = 0: Tolerance (low) messages are suppressed
The output of messages is not suppressed when the block is installed (all xx_MsgEn parameters
are preset to 1). Messages can only be output if limit monitoring of the additional analog value
has been enabled.
See also
User-configured message classes (Page 47)
Note
The AV block and the technologic block must be built into the same cyclic interrupt OB.
$9B2XW
$9B;;B/LP
$9B+\VW
$QDORJYDOXH
$9B<<B/LP $9B+\VW
7LPH
$9B;;B$FW
$9B<<B$FW
You can use Feature.Bit29 Signaling limit violation (Page 184) to determine whether the
output parameter triggers limit monitoring with the value "0" or "1".
You can use Feature.Bit28 Disabling operating points (Page 158) to disable limit monitoring
when message suppression is enabled (MsgLock = 1).
Message suppression
The corresponding message is suppressed at the block AV using the parameters:
• AV_AH_MsgEn = 0: Alarm (high) messages are suppressed
• AV_AL_MsgEn = 0: Alarm (low) messages are suppressed
• AV_WH_MsgEn = 0: Warning (high) messages are suppressed
• AV_WL_MsgEn = 0: Warning (low) messages are suppressed
• AV_TH_MsgEn = 0: Tolerance (high) messages are suppressed
• AV_TL_MsgEn = 0: Tolerance (low) messages are suppressed
The output of messages is not suppressed when the block is installed (all xx_MsgEn parameters
are preset to 1). Messages can only be output if limit monitoring of the additional analog value
has been enabled.
Hysteresis
You can specify a hysteresis (AV_Hyst) at the technologic block for the limits, for example, to
suppress signal flutter. Refer to the Limit monitoring with hysteresis (Page 106) chapter for more
on this.
Alarm delays
You can set alarm delays for incoming and outgoing alarms, warnings and tolerances. Refer to
the Area of application of the alarm delays (Page 229) chapter for more on this.
See also
User-configured message classes (Page 47)
Message suppression
The corresponding message is suppressed using the parameters:
• RbkWH_MsgEn = 0: Messages from the high limit monitoring are suppressed
• RbkWL_MsgEn = 0: Messages from the low limit monitoring are suppressed
The output of messages is not suppressed when the block is installed (for example,
RbkWH_MsgEn = 1). Messages can only be output if limit monitoring of the position feedback
has been enabled.
Hysteresis
You can specify a hysteresis (RbkHyst) for the limits, for example, to suppress signal flutter.
Refer also to chapter Limit monitoring with hysteresis (Page 106) for more on this.
See also
User-configured message classes (Page 47)
When the limits are reached or exceeded, messages that can be suppressed are output.
You can use Feature.Bit29 Signaling limit violation (Page 184) to determine whether the
output parameter triggers limit monitoring with the value "0" or "1".
You can use Feature.Bit28 Disabling operating points (Page 158) to disable limit monitoring
when message suppression is enabled (MsgLock = 1).
Message suppression
The corresponding message is suppressed using the parameters:
• ER_AH_MsgEn = 0: Messages from the high limit monitoring are suppressed
• ER_AL_MsgEn = 0: Messages from the low limit monitoring are suppressed
The output of messages is not suppressed when the block is installed (for example,
ER_AH_MsgEn = 1). Messages can only be output if limit monitoring has been enabled.
Note
With the MotSpdCL block, messages are only output if you have enabled Feature.Bit5 (Alarm
setpoint difference (Page 184)).
Hysteresis
You can specify a hysteresis (ER_Hyst) for these limits, for example, in order to suppress signal
flutter . Refer also to chapter Limit monitoring with hysteresis (Page 106) for more on this.
Alarm delays
You can set alarm delays for incoming and outgoing alarms. Refer to the Area of application of
the alarm delays (Page 229) chapter for more on this.
See also
User-configured message classes (Page 47)
2.1.3.4 Feedbacks
Feedback monitoring
You can use the following monitoring functions:
• Monitoring the start-up and stop characteristics for motors or the runtime of valves
• Monitoring the operation of motors or the maintenance of the position of valves
• Disabling feedback
This monitoring function is enabled via the Monitor = 1 input.
Static and dynamic errors are reset by disabling the monitoring (Monitor = 0). If you
reactivate monitoring during the plant runtime, only dynamic monitoring (MonTiDynamic)
will be performed.
Note
In Manual mode with Reset functionality deactivated (Feature.Bit31 = 0), you can control all
the valves (including the motor valve but not the motors) despite the setting MonSafePos = 1
and with "Monitoring error" without reaching the neutral position.
Monitoring the start-up and stop characteristics for motors or the runtime of valves
Monitoring of the startup characteristics is implemented using the parameter MonTiDynamic.
The monitoring time specifies the period within which the feedback value, for
example, FbkStart with motors, must be available in response to a control signal. If this is not
the case, the text "Control error" is displayed in the standard view of the faceplate. An error
message is generated at the same time. The block then goes to its neutral position. In the case
of motors, this is always the stop state. With other blocks, this is an neutral position you have
specified (SafePos parameter). The block signals this at the corresponding output parameter
of the error message with 1, for example, with MonDynErr = 1 for motors.
With the motors MotL, MotRevL, MotSpdL, MotSpdCL and the motor valve VlvMotL, the
Feature.Bit13 can be set to use a separate monitoring time MonTiDyStop for the stop
behavior. The monitoring time for the stop behavior is displayed at the MonDynStopErr output.
Parameters are set in seconds.
Note
Please note that MonTiDynamic ≥ MonTiStatic and MonTiDynamic ≥ SampleTime
have to be configured. If something is set outside these limits, the block always returns the
respective limit at the input.
If SampleTime changes, MonTiDynamic may be tracked to the new value for SampleTime.
MonTiStatic is tracked if MonTiDynamic < MonTiStatic changes. With MonTiStatic
= 0, each feedback change without change of the control immediately results in a runtime error.
After a static monitoring error (e.g.: MonStaErr =1), an impulse output control is set to drive
the motor or the valve in rest position even if the block is already in rest position.
When Monitoring Error occurs, STOP output pin value remains 0 until the error state got
rectified and reset.
When Trip, FaultExt, CSF(with Feature.Bit18 = 1) becomes active and error
occurs, STOP outpin pin is set to 1, even at the error state and before reset.
The following applies for "Small" blocks: These blocks operate like "Large" blocks; however, the
monitoring time is set to 0 within the block and cannot be changed. Any change is displayed
immediately at the output parameter MonStaErr with 1.
Note
This function is only supported by "Large" blocks.
2.1.4.1 Interlocks
Interlocks at blocks
A maximum of three types of interlock can be used depending on the block. Three separate
inputs named Permit, Intlock and Protect are available for these functions.
• Activation enable ("Permission"): The activation enable makes it possible to switch the
motor in the direction which is enabled. The activation disable is displayed with a padlock in
the standard view. The motor cannot switch in the direction which is disabled.
• Interlock without reset ("Interlock"): An active interlock condition puts the block to the
neutral position (Intlock = 0). After the interlock condition has gone, the currently active
control function becomes active again in automatic or local mode. In manual mode, the
faceplate can be operated again after the interlock condition has gone.
• Interlock with reset ("Protection"): An active interlock condition puts the block to the
neutral position (input Protect = 0). Once the interlock condition is cleared, a reset is
necessary. Refer to the Resetting the block in case of interlocks or errors (Page 49)section for
more information.
• Permission for safe position ("Permit neutral pos." or "Permission stop"):
- The activation enable ("PermitSafePos = 0") prevents stop command to the motor.
- The activation enable ("PermitSafePos = 0") prevents the control in safe position direction
for VlvL & VlvAnL.
- The activation enable ("PermitSafePos = 0") & Feature2.Bit16 = 0 prevents the control in safe
position direction for VlvMotL & VlvPosL.
- The activation enable ("PermitSafePos = 0") & Feature2.Bit16 = 1 prevents the stop
command for VlvMotL & VlvPosL.
Note
Interlocks for "small" blocks and controller blocks
Ensure that "small" blocks and controller blocks PIDConL and PIDConR have only the Intlock
parameter. The other two interlocks are not included in these block variants.
Permission stop for VlvPosL
Permission stop does not restrict manipulated variable when position control is active.
Permission stop for MotRevL & MotSpdCL
Permission stop does not restrict the direct changeover between forward and revrese direction
(Feature.Bit7 = 1)
The blocks MotRevL, MotSpdL, VlvMotL, VlvPosL, VlvAnL and MotSpdCL with
Feature2.Bit16 = 1 (see section Separate interlock for each direction, position, or speed
(Page 183)) have inputs for interlock functionality with direction:
The block icon indicates the prioritized group status according to the active operating state. See
also the section Forming the group status for interlock information (Page 115) for more on this.
The faceplate visualizes the state of each interlock type separately.
The padlock is not shown in the block icon if all parameters for enabling the button are set to 0
or all parameters have the signal status 16#FF.
Note
Motors and values are not put into the neutral position if one of the interlock inputs is active (for
example Intlock = 0) and the corresponding signal status is 16#FF
(Intlock.ST = 16#FF).
Note
The LockAct parameter is not set despite a pending interlock, if a value in the block is forced.
See also the section Forcing operating modes (Page 47) for more on this.
Messaging
No messages are assigned to the interlock types. However, if you want to have a message when
an interlock condition is violated, you can use the freely interconnectable input parameters to
generate the messages. See also the section Generating instance-specific messages (Page 234)
for more on this.
See also
Neutral position for motors, valves and controllers (Page 56)
Note
"Small" blocks have only the Intlock parameter
With "Small" blocks, you can only assign parameters to "Interlock without reset" (input
parameter Intlock or for the deactivation of the interlock for the input parameter Intl_En).
Disabling of all the interlocks (only for local operation and for simulation)
You can use the input parameter BypProt = 1 to disable all the interlocks, irrespective of the
parameter assignment of the individual interlock, in local mode as well as for the "simulation"
function.
Signal status "Bad, device related" (value 16#00) or "Bad, process related" (value 16#28)
An interlock signal with this status is always processed as an active interlock signal in the block
and displayed with the following icons in the faceplate:
for 16#00 or
A motor protection signal (Trip parameter) with signal status 16#00 or 16#28 is used to
activate motor protection. This is indicated by "Motor protection" in the standard view of the
faceplates.
A torque-monitoring signal (TorqOpen, TorqClose parameters) with signal status 16#00 or
16#28 is used to activate torque monitoring for motor valve VlvMotL.
Signal status ≠ "Simulation" as well as "Bad, device related" and "Bad, process related"
Only signal states "Simulation", "Bad, device related" and "Bad, process related" have an effect on
the processing in the block; all others are only displayed with their relevant icon in the faceplate.
0 1 1 16#28 Visible
0 1 1 16#60 Visible
Comments on table:
• X: The value is irrelevant for the display of the icon.
• : Blocks with directional interlock and Feature2.Bit16 = 1: "Perm_En", "Intl_En",
2)
If the Separate evaluation for excluded and simulated interlock signals (Page 164) function is
enabled (Feature bit =1), the bypass signals in the structures Permission, Protection, and
Interlock are evaluated. The bypass signals can be read from the upstream interlock block at the
output Bypass.
Excluded interlock signals are shown in the faceplate as follows:
Comments on table:
• X: The value is irrelevant for the display of the icon.
• 1): Icon corresponding to the status of the interlock signal (for 16#80 no icon)
• : Blocks with directional interlock and Feature2.Bit16 = 1: "Perm_En", "Intl_En",
2)
Note
"Small" blocks do not feature rapid stop.
The "rapid stop" function is supported only by "Large" blocks.
You issue the command for rapid stop state using the RapidStp = 1 input parameter.
When you click on the "Rapid Stop" button in the faceplate, the drive stops immediately, shown
as follows in the faceplate:
5DSLGVWRS
The R_StpAct = 1 output parameter is set to implement the rapid stop function for local
mode. You need to interconnect this parameter with the corresponding channel block and in the
I/O to realize the rapid stop function in the hardware.
Rapid stop is unlocked for all operating modes using the "Reset" button in the faceplate
(RstOp = 1); in CFC it is unlocked using the RstLi = 1 input parameter. In automatic mode,
the unlocking can also be performed via a 0-1 edge transition in the control if Feature.Bit9
= 1.
Rapid stop can be selected even with the motor in stop state. In this case, the motor start is
prevented.
Bypassing signals
With this function, you can flag a block as bypassed. If the bypass function is active, the output
parameter BypassAct will be set from the block. With a connection from BypassAct to an
input parameter BypLixx of an interlock block, you can bypass the corresponding input of the
interlock block.
If the block is set to bypass, the bypass information bit of the process output and the limit switch
points listed in the following table are set. If you connect one of this listed parameter with bypass
information bit to an interlock input Inx, you can use the bypass information bit to switch the
interlock signal in bypass. For this in the interlock block the corresponding bypass enable bit
BypEn.Inx and the Feature.Bit2 Separate evaluation for excluded and simulated
interlock signals (Page 164) have to set.
Additionally, you can define over the Feature bit Substitution value is active if the block is in
bypass (Page 202) if the block shall use the process value or a substitution value in case of an
active bypass.
Block Process value/ Process value/ Parameter with bypass information bits
signal signal
MonAnL PV_Out BypPV PV_Out, PV_AH_Act, PV_WH_Act,
PV_TH_Act, PV_AL_Act, PV_WL_Act,
PV_TL_Act, GradHUpAct,
GradHDnAct, GradLAct
PIDConL, PID‐ PV_Out BypPV PV_Out, PV_AH_Act, PV_WH_Act,
ConR, and PID‐ PV_TH_Act, PV_AL_Act, PV_WL_Act,
StepL PV_TL_Act, ER_AH_Act, ER_AL_Act
MonDiL Out BypIn Out
TotalL Out BypOut Out, OutAH_Act, OutWH_Act,
OutTH_Act, OutAL_Act, OutWL_Act,
OutTL_Act
With the parameter BypLiOp, you can decide whether the switching on/off will be done by the
input parameters which are connected in CFC or by the faceplate from an operator.
• BypLiOp = 0: In the "Parameter view", the operator can switch on/off the bypass function
over the parameter BypPVOp or RstBypOp. If BypLock = 1, you cannot make any change
to the parameters BypPVOp or ResBypOp. The button for switching the bypass functionality
on/off in the "Parameter view" is deactivated.
• BypLiOp = 1: With a connection of the parameter BypPVLi or RstBypLi, the bypass
function will be switched on/off.
The blocks are grouped into the following function block groups:
• Technologic blocks (Page 119)
• Digital logic blocks (Page 121)
• Analog logic blocks (Page 122)
• Redundancy blocks (Page 123)
• Blocks with configurable status prioritization (Page 124)
• Interlock blocks (Page 126)
• Mathematical blocks (Page 128)
• PCS 7 channel blocks (Page 129)
• Channel blocks for field devices (Page 129)
All blocks of a group use the same priority specifications and form the signal status of the process
outputs based on them.
Note
The status / quality of control inputs for logic functions and parameters have no influence on the
status / quality of process values and logic functions of the blocks.
The status / quality of process values inherit the results of mathematic and logic functions, which
are directly related to the process value.
The status/quality of process values immediately inherit the results of monitoring and limiting
functions directly related to the process value.
2.1.5.2 Forming and outputting the signal status for technologic blocks
6 16#80 Good
Interconnectable output parameters for limits (for example, PV_AH_Act) that can be
influenced directly by an interconnectable input parameter (for example, PV) inherit the status
from the associated output parameter (for example, PV_Out).
If an output parameter for limits is influenced directly by several interconnectable input
parameters (limit monitoring), it receives the status of the input parameter with the highest
priority (see overview above). Thus, for example, the control deviation is formed from the
setpoint (SP) and the process value (PV). The output parameter for limits ER_AH_Act, for
example, which signals an active violation of the high limit for the error signal, has a signal status
based on the group status formed from the process value and setpoint (ER).
• If the input signal has "Simulation" status and the input signal is therefore inactive (for
example, Protect = 0), the input signal in this case is interpreted as a simulated signal and
is displayed by the icon for simulation:
• If the input signal has the "Bad, device related" or "Bad, process related" signal status, this is
evaluated as an active input signal, regardless of its value, i.e. safety interlock signal
(Protect = 1) that is inactive due to its value, triggers a safety interlock when its status is
"Bad, device related" or "Bad, process related".
Display of the signal status in the faceplate and block icon for technology blocks
The signal status is displayed for each individual input parameter in the faceplate next to the
process values or the interlock buttons. The group status is displayed in the block icon and in the
group display of the faceplate.
Note
The interlocks and additional values are not included in the formation of the group status.
2.1.5.3 Forming and outputting the signal status of digital logic blocks
6 16#80 Good
The group status is set to 16#68 (uncertain, device-related), with an undefined signal status at
a control input that is involved in forming the group status.
A signal status 16#FF at a control input is not used for the calculation of the group status. If all
relevant control inputs are 16#FF, the group status is 16#80.
If only one process input is decisive for calculating the output value, the status of the process
input is transferred to the status of the output.
2.1.5.4 Forming and outputting the signal status of analog logic blocks
6 16#80 Good
The output value is generated based on the signal status of the process value with the above
table of priorities. In addition, the output parameters SimAct, Uncertain, and LossRed are
still set according to the signal status.
2.1.5.6 Forming and outputting the signal status for blocks with configurable status
prioritization
Forming the signal status for blocks with configurable status priority
For more general information on forming the status signal, refer to the section: Forming and
outputting signal status for blocks (Page 118).
The SelPrio parameter is used for this block to define the priority setting for linking the
individual states. You have the option between the following specifications:
Note
The parameter SelPrio can take a value from 0 to 7 . SelPrio = 6 is set by default.
If you enter a value greater than 7, the setting for 7 is used. If you enter a value lower than 0,
the setting for 0 is used.
For information on evaluating the status of the process value inputs, refer to the section
MuxAn03 functions (Page 2351).
2.1.5.7 Forming and outputting the signal status for interlock blocks
General rules
• If a given input causes a signal change at the output, the signal status of the input with the
highest priority (worst signal status) is set at the output, since each input can influence the
output:
– Logical AND operation (logic = 1):
If the output value is 1, it has the signal status with the highest priority of all
interconnected input signals.
– Logical OR operation (logic = 0):
If the output value is 0, it has the signal status with the highest priority of all
interconnected input signals.
• If several inputs have the same priority and the output therefore cannot be changed, the
signal status of the input with the lowest priority (highest signal status) is set at the output,
since the output is uniquely determined by the signal with the best signal status:
– Logical AND operation (logic = 1):
If the output value is 0, it has the signal status with the lowest priority of all
interconnected input signals, which have a value of 0.
Note
With Feature.Bit23 = 1 (evaluation signal status), input signals with a bad signal
status (16#28 or 16#00) are processed with the value 0, regardless of their actual value
Display of the signal status in the faceplate and block icon for interlocking blocks
The signal status is displayed for each individual parameter (except for the analog values) in the
faceplate next to the process values.
If you bypass a signal, it is displayed in the faceplate of the interlocking block next to the button
for excluding, as well as in the block icon as follows.
Note
If an excluded interlock signal can become switchover-relevant, the status of the output Out.ST
is set to simulation 16#60, as long as it is not forced by other interlock inputs to Bad, device-
related 16#00 or Bad, process-related 16#28.
An excluded interlock input has no influence on the status when the Separate evaluation for
excluded and simulated interlock signals (Page 164) function is enabled.
The currently valid status for the output signal is also displayed in the faceplate.
2.1.5.8 Forming and outputting the signal status for mathematical blocks
6 16#80 Good
The group status is set to 16#68 (uncertain, device-related), with an undefined signal status at
a control input that is involved in forming the group status.
A 16#FF signal status at a control input is not used for the calculation of the group status. If all
relevant control inputs are 16#FF, the group status in the search for the worst group status is
16#80 and 16#00 in the search for the best group status.
If only one process input is decisive for calculating the output value, the status of the process
input is transferred to the status of the output.
Note
Special notes for the Integral mathematical block
Due to its application area (time integral, I-component for the configuration of a controller), the
Integral block generates the signal status like the technological blocks.
Special notes for the mathematical blocks Addxx, Mulxx, Div02 and Sub02
If the result of the mathematic operation is a floating-point number that cannot be displayed,
the result of the status is set to 16#28. Floating-point numbers that cannot be displayed are
labeled in the CFC with #+Inf (+ infinite), #-Inf (- infinite) or with #NaN (not a number).
2.1.5.9 Forming and outputting the signal status for PCS 7 channel blocks
2.1.5.10 Forming and outputting the signal status for channel blocks for field devices
Error handling
The channel and technologic blocks feature error handling routines. A distinction must be made
between the following areas:
• Error numbers
• External process control error (CSF)
• Process-specific errors
• Invalid signal states
• Mode switchover error
• Errors in channel blocks
Error numbers
Most blocks have an output parameter ErrorNum that can be used to output internal error
states of the block as error numbers.
With some blocks, input parameters are checked for permissible values. They are therefore only
used to prevent the output value from remaining invalid when the input value is once again in
the valid range. If an invalid value is detected, and the corresponding output value is held at the
last displayed value instead of an invalid value being displayed. If blocks do not have this check,
an invalid value can appear at the output. However, a valid value is displayed again at the output
as soon as the input values of the block have changed correspondingly.
Any value set over an interconnection or as a result of a parameter assignment that is outside the
range of values (e.g. "Not a Number") is not processed by the block algorithm. The last valid value
is processed instead.
In addition to the errors stated above, a limit violation is also signaled for example. Each error
number is assigned to a specific error.
If there is more than one error, all error numbers have the same priority. The routine always
displays the error number of the error most recently detected in a block cycle.
Process-specific errors
Process-specific errors can have the following causes:
• Runtime monitoring: If the feedback signals do not match the control settings after a selected
time has expired, a process-related error is output.
• Feedback monitoring: Refer to the Monitoring the feedbacks (Page 106) section for more on
this.
If the block algorithm detects a monitoring error while monitoring is enabled, the corresponding
output parameter is set to 1 in the block. The "$$BlockComment$$ Feedback error xxx" error
message is also output, where xxx, for example, stands for the valve.
This state is visualized in the group display by an "S" character in the faceplate overview and in
the block icon.
The block must be reset after the monitoring error was cleared and if automatic mode is set.
If the block algorithm detects an invalid combination of input signals, an error number
(ErrorNum) is output that depends on the block type.
In the case of motors, valves and batches, the faceplates’ standard view will additionally output
the text “invalid signal”.
Note
The signal status of the individual signals is not taken into consideration for forming the group
error. The outputs therefore always have the status, 16#80.
3RVLWLYHFKDQJH 1HJDWLYHFKDQJH
,QSXWYDOXHFXUYH
2XWSXWYDOXHFXUYH
2XWSXWYDOXHFXUYH
,QSXWYDOXHFXUYH
Use the SP_RmpModTime input parameter or the ramp view of the faceplate to specify whether
the setpoint ramp is defined by time or by gradients:
• If you select time (SP_RmpModTime = 1): The ramp of the setpoint is calculated
automatically by the block so that after the ramp has started (SP_RmpOn = 1), the setpoint
will reach the target setpoint (SP_RmpTarget) after the selected time (SP_RmpTime).
• If you select gradients (SP_RmpModTime = 0): The inclination of the ramp matches the
selected rates of change SP_UpRaLim (positive) or SP_DnRaLim (negative).
Once the setpoint has reached the target setpoint, the function is terminated automatically
(SP_RmpOn = 0). The ramp trip can be prematurely aborted in the faceplate by setting
SP_RmpOn = 0.
Requirements for using a setpoint ramp
If the requirements are not fulfilled during the ramp trip, the ramp trip is automatically canceled.
Note
Special note for the MotSpdCL block
In the case of an interlock, a monitoring error, motor protection or rapid stop, the motor is
switched off and the internal ramp setpoint is reset to the starting setpoint of the ramp trip.
Note
ParametersSP_UpRaLim and SP_DnRaLim are always evaluated according to their magnitude.
With the Feature Bit Gradient limitation with time duration (Page 199), you can also use the
parameters SP_RmpModTime and SP_RmpTime in the gradient limit function. If this Feature
Bit = 1 and SP_RmpModTime = 1 is parameterized, the ramp rate is calculated with a change of
setpoint such that the new value of the setpoint will reach after the time of SP_RmpTime.
External setpoint
If the external setpoint (SP_ExtAct.Value = 1) is switched on, the linkable values
SP_LiUpRaLim, SP_LiDnRaLim, SP_LiRmpTime, of SP_UpRaLim, SP_DnRaLim,
SP_RmpTime respectively will be used. The values will be active only if they are connected
(SP_LiX.ST <> 16#FF).
3RVLWLYHFKDQJH 1HJDWLYHFKDQJH
,QSXWYDOXHFXUYH
2XWSXWYDOXHFXUYH
2XWSXWYDOXHFXUYH
,QSXWYDOXHFXUYH
Use the MV_RmpModTime input parameter or the ramp view of the faceplate to specify whether
the manipulated variable ramp is defined by time or by gradients:
• If you select time (MV_RmpModTime = 1): The gradients of the manipulated variable are
calculated automatically by the block so that after the ramp has started (MV_RmpOn = 1),
the manipulated variable will reach the target value (MV_RmpTarget) after the configured
time (MV_RmpTime).
• Specification with gradients (MV_RmpModTime = 0): The ramp slope matches the
configured rates of change MV_UpRaLim (positive) or MV_DnRaLim (negative).
Once the manipulated variable has reached the target value, the function is terminated
automatically (MV_RmpOn = 0). The ramp trend can be prematurely aborted in the faceplate
by setting MV_RmpOn = 0.
If the requirements are not fulfilled during the ramp trip, the ramp trip is automatically canceled.
Note
Parameters MV_UpRaLim and MV_DnRaLim are always evaluated according to their magnitude.
With the Feature Bit Gradient limitation with time duration (Page 199), you can also use the
parameters MV_RmpModTime and MV_RmpTime in the gradient limit function. If this Feature
Bit = 1 and MV_RmpModTime = 1 is parameterized, the ramp rate is calculated with a change of
manipulated variable such that the new value of the manipulated variable will reach after the
time of MV_RmpTime.
2.1.8.1 Applying the dynamically activated dead band during the PV settling time
Feature bit
Number of the Feature bit: 30.
Note
If Feature.Bit30 = 1 is set, the ConPerMon block has to be connected with the controller. The
blocks PIDConL or PIDConR monitor this by checking the status signal of MeanMV.ST. In case
of Feature.Bit30 = 1 and MeanMV.ST = 16#78 the dynamic deactivation of deadband is not
possible and the output ErrorNum will be set to 52.
63B/L2S
63B/L2S 63B/L2S
63B,QW 63B([W
First you define whether the setpoint specification is to be carried out by means of a CFC/SFC
program or by means of the faceplate. In the next step you specify whether the internal or the
external setpoint is to be used.
Setpoint specification by means of faceplate or interconnection
With the SP_LiOp parameter, you define whether the setpoint will be set by a CFC/SFC program
or using the faceplate.
• Parameterize Sp_LiOp with 0 so that the setpoint specification is carried out by means of the
faceplate.
• Parameterize SP_LiOp with 1 so that the setpoint specification is carried out by means of a
CFC / SFC program.
Setpoint specification internal & external
You have to set the corresponding parameters depending on how the setpoint specification is to
be carried out.
If the setpoint is set in the faceplate (SP_LiOp = 0), you have to set the parameter:
• SP_IntOp = 1 in order to achieve an internal setpoint specification by means of the
faceplate.
• SP_ExtOp = 1 to have an external setpoint set in the faceplate.
If both signals are set, SP_IntOp = 1 has priority.
If the setpoint is set by a CFC / SFC program (SP_LiOp =1), you have to set the parameter:
1. SP_IntLi = 1 to have an internal setpoint set by a CFC / SFC program.
2. SP_ExtLi = 1 in order to achieve an external setpoint specification by means of a CFC / SFC
program.
Note
For PIDConL, PIDStepL, FmCont, FmTemp: If both signals are set, SP_IntLi = 1 has
priority.
If no auxiliary valve is used for operation, the external manipulated variable is used for automatic
mode and the internal manipulated variable is used for manual mode. It is not possible to switch
between internal and external.
Note
If no auxiliary valve is used and either the "Open" or "Close" command is active, a new
manipulated variable (internal or external) only takes effect after the change. In automatic
mode, the manipulated variable is ignored as long as the "Open" or "Close" command is pending.
Note
It is only possible to switch between internal and external when operating with a auxiliary valve.
See also
Flow setpoints in percent (Page 159)
Use an internal or external setpoint for the absolute fine dosing quantity (Page 166)
Polygon functions (Page 2310)
Feature bit
Number of the Feature bit: 11
Feature bit
Number of the Feature Bit: 6
Failure handling
Use this Feature bit to configure "Failure handling" in the case of device failure.
The default setting is 0.
Bit = 0: Commands Local and Ackn only active
Bit = 1: All commands active
See also
Configurable functions using the Feature I/O (Page 141)
Feature bit
Number of the Feature bit: 0
Note
This Feature bit has no function in the "Out of service" operating mode. The process tag
remains in the "Out of service" operating mode after a warm restart of the CPU.
Note
The message classes Alarm, Warning and Tolerance are not valid for user-configured message
classes. Please take into consideration the validity of terms for user-configured message classes
(Page 47).
Note
With a Run-Stop-Run transition of the CPU and internally pending messages, non-stuck-through
messages with time stamps and auxiliary values beginning with RunUpCycle occur for blocks
with the startup characteristic Feature bit = 0 after expiration of the RunUpCycle counter
in the following cases:
• Alarm, warning or tolerance messages from the operating points (motor, valve, dosing,
controller and analog monitoring blocks)
• Feedback errors (motor and valve blocks)
• Output signals of digital process tags (MonDiL, MonDi08)
• Flutter limits violated (MonDiL)
The restart routines of the blocks reset the following outputs in OB100:
• Operating point outputs xx_AH_Act, xx_AL_Act, xx_WH_Act, xx_WL_Act,
xx_TH_Act, xx_TL_Act or GradHUpAct, GradHDnAct, GradLAct
• Feedback error outputs MonDynErr and MonStaErr
• Output binary signals Out, Out1..8 for MonDiL or MonDi08
• Flutter suppression FlutAct for MonDiL
This causes an outgoing message when initializing Alarm8_P in OB100 and an incoming
message after expiration of the RunUpCycle counter on the cyclic interrupt level.
Note
During a complete download with AS stop, the blocks (with Feature.Bit0 = 1) cannot resume
operation in their previous mode and control when restarted.
Bit = 1: Starting the block with the last stored values, in other words in the last operating mode
set (manual, automatic or local mode) and at the last valid position.
Note
Special note following complete download to the CPU
Following a complete download to the CPU, the motor protection signal Trip is evaluated
during the initial run as good (=1).
When a motor protection signal is pending, this causes a non-struck-through message with time
stamp and auxiliary values beginning with RunUpCycle after the complete download and after
expiration of the RunUpCycle counter.
Note
Advanced configuration of the startup characteristics for the dosing block
Note that you can further affect the startup characteristics of the dribbling quantity via
the Feature2.Bit7 as a function of this Feature.Bit0. Refer to the sectionUse the last
value following a complete download as the current value during startup of the block
(Page 167)
Note
Advanced configuration of the startup characteristics for the counter blocks
Note that you can further affect the startup characteristics via the Feature.Bit5 as a function
of this Feature.Bit0. Refer to the section Use the last value following a complete download
as the current value during startup of the block (Page 167).
See also
User-configured message classes (Page 47)
2.1.9.5 Applying the dynamically activated dead band during the PV settling time
Feature bit
Number of the Feature bit: 30.
Note
If Feature.Bit30 = 1 is set, the ConPerMon block has to be connected with the controller. The
blocks PIDConL or PIDConR monitor this by checking the status signal of MeanMV.ST. In case
of Feature.Bit30 = 1 and MeanMV.ST = 16#78 the dynamic deactivation of deadband is not
possible and the output ErrorNum will be set to 52.
Feature bit
Number of the Feature bit: 23
Family
Family: Operate number of the Feature bit: 5
Family: Control, drives, dosage number of the Feature2 bit: 5
Feature bit
Number of the Feature bit: 12
Feature bit
Number of the Feature bit: 6
Note
Special note for the summing unit
Note that the characteristics of the block as a summing unit (Feature.Bit6 = 0) can be further
affected via the Feature.Bit7.
Refer to the section: Summing characteristics continuous or triggered (Page 187).
Feature bit
Number of the Feature bit: 21
Feature bit
Number of the Feature Bit: 5
See also
Configurable functions using the Feature I/O (Page 141)
Feature bit
Number of the Feature bit: 7
Feature bit
Number of the Feature bit: 10
Bit = 0: Not forwarded
Bit = 1: forwarded
Feature bit
Number of the Feature bit: 10
Feature bit
Number of the Feature bit: 28
Feature bit
Number of the Feature bit: 7
You can reverse the motor direction directly. The motor block reverses the direction
automatically. The motor is stopped and is started in the other direction when the time set in the
IdleTime parameter has elapsed.
Note
In case of automatic / local mode and Bit = 0:
If additional Feature2.Bit3 =1 Control priority in the event of invalid or not plausible input
commands is active, an automatic / local command for reverse direction is still possible. The
motor stops for the time of IdleTime (minimum one cycle) then the reverse automatic / local
command is plausible and a change of direction take place automatically.
Feature bit
Number of the Feature bit: 5
Feature bit
Number of the Feature bit: 15
2.1.9.19 Specifying the influence of the signal status on the dosing process
Feature bit
Number of the Feature bit: 23
Feature bit
Number of the Feature bit: 8
Feature bit
Number of the Feature bit: 28
Note
This Feature bit is only used when "Telegram type 20" and the "PZD 6" parameter are active.
Feature Bit
Number of the Feature Bit: 5
Feature bit
Number of the Feature bit: 30
Feature bit
Number of the Feature bit: 8
See also
Output invalid raw value (Page 188)
Outputting last valid value if raw value is invalid (Page 167)
Feature bit
Number of the Feature bit: 6
See also
Configurable functions using the Feature I/O (Page 141)
Feature bit
Number of the Feature bit: 29
Bit = 0: If there is an invalid raw value or the device is in the initialization phase, the substitute
value is not output.
Bit = 1: If there is an invalid raw value or the device is in the initialization phase, the substitute
value is output. The signal status of the output value is set to "Manipulated value (for example,
substitute value, simulation, last valid value).
If there is an invalid raw value or the device is in the initialization phase, the output parameter
Bad = 1 is set automatically.
Feature Bit
Number of the Feature bit: 31
Feature bit
Number of the Feature bit: 14
2.1.9.29 Activating error state for external process control error CSF
Feature bit
Number of the Feature bit: 18
Feature bit
Number of the Feature bit: 15
Feature bit
Number of the Feature2 bit: 2
Note
If the Feature Bit is enabled, the signal cannot be inverted via CFC during interconnections at
the inputs, as, otherwise, the bypass display would not update.
The interlocking inputs of the following blocks are affected:
• Intlk02, Intlk04, Intlk08, Intlk16: In01, In02, …
• DoseL, Vlv2WayL: Permit, Interlock, Protect
• MotL, VlvL: Permit, Interlock, Protect,PermitSafePos
• MotRevL, MotSpdCL: Permit, Interlock, Protect , PermRev, IntlRev,
ProtRev, PermitSafePos
• MotSpdL: Permit, Interlock, Protect , PermSp2, IntlSp2, ProtSp2,
PermitSafePos
• VlvAnL,VlvMotL, VlvPosL: Permit, Interlock, Protect , PermCls, IntlCls,
ProtCls, PermitSafePos
• MotS, VlvS, OpDi01, OpDi03, PIDConL, PIDConR: Interlock
The inversion of the interlocking signals occurs via the InvIn01, InvIn02, … inputs on the
interlocking blocks.
See also
OpDi01 functions (Page 433)
OpDi03 functions (Page 448)
Intlk02 functions (Page 1970)
Intlk04 functions (Page 1984)
Intlk16 functions (Page 2016)
Intlk08 functions (Page 1999)
MotL functions (Page 1388)
MotS functions (Page 1425)
MotRevL functions (Page 1454)
MotSpdL functions (Page 1573)
Vlv2WayL functions (Page 1665)
2.1.9.32 Use an internal or external setpoint for the absolute fine dosing quantity
Feature Bit
Number of the Feature bit: 8
Use an internal and external setpoint for the absolute fine dosing quantity
Use this Feature bit to determine whether the doser processes the internal and external
setpoint for the fine dosing quantity in an absolute manner and is displayed or operated in an
absolute manner in the faceplate.
The default setting is 0.
Bit = 0: Deactivated. The internal and external I/Os as well as the display and operation of the
fine dosing quantity setpoint are processed in the % unit.
Bit = 1: Activated: The internal and external I/Os as well as the display and operation of the fine
dosing quantity setpoint are processed in the unit that was set using the parameter DQ_Unit.
Feature Bit
Number of the Feature bit: 11
Feature bit
Number of the Feature bit: 30
2.1.9.35 Use the last value following a complete download as the current value during startup
of the block
Feature bit
Number of the Feature bit: 5
Number of the Feature2 bit: 7
Use the last value during startup of the block after a complete download of the CPU
You can use this Feature bit to define the startup characteristics of the block as a function of
the Feature bit 0.
Note
If you want to use this function, you must read back the marked parameters in addition to the
operated and monitored parameters before a complete download.
Feature bit
Number of the Feature bit: 5
Activate LowCutOff
You use this Feature bit to activate the use of LowCutOff bits.
The default setting is 0.
Bit = 0: Low signal cut-off - OFF (default)
Bit = 1: Low signal cut-off - ON
Feature Bit
Number of the Feature bit: 27
Feature bit
Number of the Feature bit: 8
Reporting with BATCH parameters
You can use this Feature bit to specify whether the block transfers the BATCH parameters
• BatchID: Batch ID
• BatchName: Batch name
• StepNo: Batch step number
Are transferred as associated values to the OS during messaging.
The default setting is 0.
Bit = 0: The block does not transfer any BATCH parameters to the OS.
Bit = 1: The block transfers BATCH parameters to the OS.
Note
Information about the setting "Bit = 1:
The Event block can no longer transfer the In8.ST or AV8.Value as an associated value.
The EventTS block can no longer transfer the signal status of the signal In7 and In8 or InTS7
and InTS8 as an associated value.
Feature bit
Number of the Feature bit: 12
2.1.9.40 Display only input values that are interconnected in the faceplate
Feature bit
Number of the Feature bit: 5
Feature bit
Number of the Feature bit: 5
With XXX:
Block OS_Perm.BitX
Intlk02 16-17
Intlk04 16-19
Intlk08 16-23
Intlk16 16-31
Feature bit
Number of the Feature bit: 6
Note
Feature bit 6 = 1 only when Feature bit 5 = 0
Feature bit
Number of the Feature bit: 24
Feature bit
Number of the Feature bit: 19
Bit = 1: The block can be used for program mode. The operator control elements required for this
are then visible in the faceplate.
Note
This Feature bit only applies to the PIDConR block.
Feature bit
Number of the Feature bit: 22
Feature bit
Number of the Feature bit: 13
Bit = 1: If the error signal is outside the control zone, the I component is frozen internally. When
it enters the control zone, the controller starts with the value of the I component that was in
effect when it left the control zone.
The reaction depends on additional Feature bits and controller settings. See also the following
section:
• Using control zones (Page 224)
Feature bit
Number of the Feature bit: 12
Feature Bit
Number of the Feature bit: 2
Bit = 0: The control commands are not reset by the block. If there are two pending control
commands for changing mode, the mode is not changed. In this case, the note text "Invalid
command" is displayed in the faceplate.
Bit = 1: The control commands are reset by the block. This, for example, ensures that if a control
command is sent from the SFC, the command is reset automatically after a step is exited.
Feature bit
Number of the Feature bit: 3
Feature bit
Number of the Feature bit: 6
Feature bit
Number of the Feature bit: 16
See also
Neutral position for motors, valves and controllers (Page 56)
Neutral position manipulated variable takes effect at startup (Page 179)
Use the last value following a complete download as the current value during startup of the
block (Page 167)
2.1.9.53 Resetting via input signals in the event of interlocking (Protection) or errors
Feature Bit
Number of the Feature bit: 9
2.1.9.54 Set reset depending on the operating mode or the LiOp parameter
Feature Bit
Number of the Feature Bit: 30
Set reset depending on the operating mode (motor, valve and dosing blocks)
When the "Protection" interlock, feedback error ("Status error", "Control error") or "Motor
protection" signal is present again, use this Feature bit to specify if a reset can be made
depending on the mode only by the operator in manual mode or only by the automatic I/Os in
automatic mode.
Resetting to manual mode is enabled with Feature.Bit31 (Activating reset of protection /
error in manual mode (Page 178)). Also refer to the Resetting the block in case of interlocks or
errors (Page 49) chapter.
Note
Rapid stop is unlocked for all operating modes using the "Reset" button in the faceplate
(RstOp = 1); in CFC it is unlocked using the RstLi = 1 input parameter.
Note
The local operating mode does not depend on this Feature Bit and has a separate reset
mechanism.
Resetting the dosing mode depending on the operating mode (dosing blocks)
You can also use this Feature bit to set whether or not the reset of the dosing quantity is
dependent on the operating mode.
The default setting is 0.
Bit = 0: Reset does not depend on the operating mode
Bit = 1:In manual mode, only a manual reset by the operator is possible at the input RstDQ_Op.
In automatic mode, a reset is only possible by a 0-1 edge transition at the input RstDQ_Li.
Note
The operating mode Local is independent of this Feature bit. The dosing quantity can be reset
by the operator at the input RstDQ_Op or via a 0-1 edge transition at the input RstDQ_Li.
LiOp =1: Setting or resetting to a default value can only be made at the parameter for
interconnections.
Feature bit
Number of the Feature bit: 31
Note
Rapid stop is unlocked for all operating modes using the "Reset" button in the faceplate
(RstOp = 1); in CFC it is unlocked using the RstLi = 1 input parameter.
Note
The local operating mode has a separate reset mechanism.
Feature Bit
Number of the Feature bit: 19
Feature Bit
Number of the Feature bit: 16
2.1.9.58 Neutral position manipulated variable takes effect with "out of service" operating
mode
Feature Bit
Number of the Feature bit: 15
Neutral position manipulated variable takes effect with "out of service" operating mode
You can use this Feature bit to specify if the block should go to the neutral position when it
transitions to the "Out of service" operating mode.
Default position is "0".
Bit = 0: The block does not go to the neutral position at the transition to the "out of service"
operating mode.
Bit = 1: The block goes to the neutral position at the transition to the "out of service" operating
mode.
Refer to the Neutral position for motors, valves and controllers (Page 56) section for more
information.
Feature bit
Number of the Feature bit: 4
Setting switch or button mode (input signal as pulse signal or as static signal)
You can use this Feature bit to determine whether a separate interconnectable 1-active control
input has to be used for every automatic command of the block or two automatic commands are
assigned to a control input.
The Feature bit impacts the following control inputs for automatic mode in the form of a pulse
(push-button operation) or a static signal (switch operation):
• Starting and stopping a motor
• Opening and closing a valve
• Switching modes: Automatic and Manual (parameters AutModLi and ManModLi)
• Setpoint specification: Internal and External (parameters SP_ExtLi and SP_IntLi)
is given in the form of a pulse (pushbutton operation) or a static signal (switching mode).
Note
The input commands are checked for plausibility. For more information, see Error handling
(Page 130), e.g. MotL error handling (Page 1396) and Feature2.Bit3 (Control priority in the
event of invalid or not plausible input commands (Page 189)).
You can find the commands for controlling the block in the relevant section on block operating
modes. They are always the parameters that are used for the automatic operation of a block.
Bit = 0: Button mode: Each automatic command is assigned to a control input. This has a latching
reaction and is 1-active.
Example with a motorMotRevL: In this case, use the interconnectable input parameters.
• FwdAut = 1 for the command "Start forward"
• RevAut = 1 for the command "Start backwards"
• StopAut = 1 for the stop command and
• AutModLi = 1 for setting "Automatic" operating mode
• ManModLi = 1 for setting "Manual" operating mode
Bit = 1: Switching mode: two static automatic commands are assigned to a control input.
Example with a motorMotRevL: In this case, use the interconnectable input parameters.
• FwdAut = 1 for the command "Start forward"
• RevAut = 1 for the command "Start backwards" and
• FwdAut = 0 and RevAut = 0 for the stop command
Feature Bit
Number of the Feature bit: 5
Note
This Feature bit is only used with the SwOverTi > 0 parameter. Refer also to the MotSpdL
functions (Page 1573) section for more on this.
Feature Bit
Number of the Feature bit: 13
Note
Creep rate is the flow in the states "End", "Off", and "Pause".
Feature bit
Number of the Feature bit: 14
Note
SafeV0, SafeV1, SafeV2 and DefPos1, DefPos2 are only used for configuring the icon
displays in the OS.
Feature bit
Number of the Feature bit: 13
Feature bit
Number of the Feature2 bit: 16
Feature bit
Number of the Feature bit: 8
See also
User-configured message classes (Page 47)
Two time values per limit pair (Page 231)
Feature bit
Number of the Feature bit: 29
Note
To learn about the parameters with which you can influence this behavior, refer to the
description of the connections for the respective blocks.
Feature bit
Number of the Feature bit: 5
2.1.9.69 Setpoint specification with separate display area and custom unit
Feature bit
Number of the Feature bit: 16
Feature Bit
Number of the Feature bit: 5
2.1.9.71 Enabling bumpless change to the proportional gain, derivative time and
amplification of the differentiator
Feature Bit
Number of the Feature bit: 20
Enabling bumpless change to the proportional gain, derivative time and amplification of the
differentiator
Use this Feature bit to enable bumpless change to proportional gain Gain, derivative action
time TD and gain of the differentiator in automatic mode.
The default setting is 0.
Bit = 0: The bumpless switchover is deactivated.
Bit = 1: The bumpless switchover is activated.
Feature bit
Number of the Feature bit: 21
Feature Bit
Number of the Feature bit: 18
Changeover with or without P step change when the internal setpoint is not in tracking mode
Use this Feature bit to specify if a changeover should occur with or without a P step change
when the internal setpoint (SP_TrkPv = 0) does not track the process value.
The default setting is 0.
Bit = 0: Changeover without P step change (bumpless)
Bit = 1: Changeover with P step change (not bumpless)
For more detailed information, refer to the description of Manual and automatic mode for
control blocks (Page 81).
2.1.9.74 Enabling bumpless switchover to automatic mode for valves, motors, and dosers
Feature bit
Number of the Feature bit: 17
Bumpless switchover
You can use this Feature bit to enable the bumpless switchover from local/manual mode to
automatic mode.
Default setting is 0
Bit = 0: Bumpless switchover is disabled. You can switch from local/manual mode to automatic
mode at any time.
Feature bit
Number of the Feature bit: 7
Feature Bit
Number of the Feature bit: 25
Feature bit
Number of the Feature bit: 28
Note
FbAnOu
With V9.1 SP2, the channel block supports also the output of an invalid raw value for inputs Rbk,
PosD, RCasOut. To ensure backward compatibility the default is "0" and not "1".
Feature bit
Number of the Feature bit: 29
2.1.9.79 Control priority in the event of invalid or not plausible input commands
Feature2 Bit
Number of the Feature2 bit: 3
Note
To Bit = 1:
A change of direction in automatic / local mode with block MotRevL, MotSpdCL is possible
although the Feature.Bit7 =0 Enabling direct changeover between forward and reverse is
not parameterized. The motor stops for the time of IdleTime (minimum one cycle) then the
reverse automatic / local command is plausible and a change of direction take place
automatically.
Feature Bit
Number of the Feature Bit: 21
2.1.9.82 Reaction of the switching points in the "Out of service" operating mode
Feature Bit
Number of the Feature bit: 26
Note
The Feature "Changes signal status of outputs in OOS" has higher priority over the Feature
"Reaction of the switching points in the "Out of service" operating mode".
Feature bit
Number of the Feature bit: 1
A 1-0 edge transition at the input parameter OosLi has no influence on the reaction of the
technologic block, the previous status is retained.
See also the section Release for maintenance (Page 72) for more on this.
Feature bit
Number of the Feature bit: 10
For more detailed information, refer to the description of Local mode (Page 88).
Note
Functionality of "Feature.Bit10" is supressed over "Feature.Bit17"
When Feature.Bit17=1 and Feature.Bit10=1 , after a change from “Automatic Mode” to
“Local Mode” the block leaves the “Local Mode” in case of not matching commands to "Manual
Mode" and not to "Automatic mode".
Feature bit
Number of the Feature bit: 27
Note
A decreasing motor protection (Trip.Value=0) is displayed at the output
parameter LockAct, regardless of the Feature bit setting.
This Feature bit is also applicable for the LocalSetting 5 in VlvS.
Feature2 bit
Number of the Feature2 bit: 6
Feature2 bit
Number of the Feature2 bit: 24
Feature bit
Number of the Feature bit: 6 (7 for VlvAnL)
Ramp gradient changes if new ramp target value is at the other side of the start point. Ramp Trip
is not aborted.
Bit = 1:
Ramp rate is calculated with the actual SP or MV and the new ramp target value.
Ramp mode =Gradient:
Ramp gradient stays Constant . Ramp Trip is not aborted,if new ramp target value crosses the
instantaneous ramp trip value.
2.1.9.89 SP following PV in open loop has no priority over SP_Ext and SP limits
Feature bit
Number of the Feature bit: 23
2.1.9.90 With accelerated return of the integral action from the manipulated variable limit
Feature bit
Number of the Feature bit: 17
With accelerated return of the integral action from the manipulated variable limit
When switching to the automatic mode (manually, by tracking, forced tracking, or program
mode with manipulated variable specification) or when the controller is initialized by
the InitPid input, the integral action (reset) is moved to preserve bumpless operation in case
of an impending control deviation. The greater the control deviation and the controller gain, the
greater is this shift. The result may be that the integral action is set far outside the manipulated
variable limits. If the control deviation decreases after switching to the automatic mode, it may
happen that in controllers with large TI values, the manipulated variable stays within the limit
for a longer duration.
You can use this Feature bit to accelerate the return of the integral action from the limit. In case
of a pending control deviation, the integral action is moved only in the direction of the control
range to the extent that the manipulated variable can remove itself quickly and bumplessly from
the manipulated variable limits (MV_HiLim/MV_LoLim).
The default setting is 0.
Bit = 0: Without accelerated return of the integral action.
Bit = 1: With accelerated return of the integral action when the integral action and the
manipulated variable are outside or at the manipulated variable limits.
Note
In regular control mode, the integral action cannot move outside the manipulated variable limits
because the manipulated variable is limited first and then fed back to the reset memory (see also
anti-windup in PIDConR functions (Page 1109)).
Feature bit
Number of the Feature bit: 6
LiOp = 0 Selection of In01 to In16 is internal; SelInt is active and can be used via faceplate.
LiOp = 1 Selection of In01 to In16 is external; SelExt is active and can be used via inter‐
connection.
• Bit = 1:
LiOp = 0 With the input parameter SelIntOp or SelExtOp, you can change the selection
between internal (SelInt) and external (SelExt) via faceplate.
LiOp = 1 With the input parameter SelIntLi or SelExtLi, you can change the selection
between internal (SelInt) and external (SelExt) via interconnection.
Feature2 bit
Number of the Feature2 bit: 4
Setting switch or button mode for local commands (input signal as pulse signal or as static signal)
You can use this Feature2 bit to determine whether a separate interconnectable 1-active
control input has to be used for every local command of the block or two local commands are
assigned to a control input.
The Feature2 bit affects the following control inputs for local mode in the form of a pulse
(pushbutton operation) or a static signal (switching mode):
• Starting and stopping a motor
• Opening and closing a valve
Note
• The input commands are checked for plausibility. For more information, see Error handling
(Page 130), e.g. MotL error handling (Page 1396) and Feature2.Bit3 (Control priority in
the event of invalid or not plausible input commands (Page 189)).
• With Feature2.Bit9 =1 (Button mode with triggered local control commands
(Page 212)), the local input commands for button mode always need a 0->1 trigger to
activate the control output signal.
You can find the commands for controlling the block in the relevant section on block operating
modes. They are always the parameters that are used for the local operation of a block.
Bit = 0: Button mode: Each local command is assigned to a control input. This has a latching
reaction and is 1-active.
1. Example with a motor MotRevL: In this case, use the interconnectable input parameters.
• FwdLocal = 1 for the command "Start forward"
• RevLocal = 1 for the command "Start backwards"
• StopLocal = 1 for the stop command
Bit = 1: Switching mode: two static local commands are assigned to a control input.
2. Example with a motor MotRevL: In this case, use the interconnectable input parameters.
• FwdLocal = 1 for the command "Start forward"
• RevLocal = 1 for the command "Start backwards"
• FwdLocal = 0 and RevLocal = 0 for the stop command
The StopLocal control input is irrelevant in this case.
3. Example with motor MotSpdL: In this case, use the interconnectable input parameters.
• Spd1Local = 1 for the command Motor to run with Speed1
• Spd2Local = 1 for the command Motor to run with Speed2
• Spd1Local = 0 and Spd2Local = 0 for the stop Command
4. Example with motor MotSpdCL: In this case, use the interconnectable input parameters.
• FwdLocal = 1 for the command "Start forward"
• RevLocal = 1 for the command "Start backwards"
• FwdLocal = 0 and RevLocal = 0 for the stop command
5. Example with VlvPosL: In this case, use the interconnectable input parameters.
• OpenLocal = 1, Command for Valve to "Open”
• CloseLocal = 1, Command for Valve to "Close”
• OpenLocal = 0 and CloseLocal = 0 for the stop command
6. Example with Vlv2WayL: In this case, use the interconnectable input parameters.
• Pos1Local = 1, Command for Valve1 to "Open"
• Pos2Local = 1, Command for Valve2 to "Open"
• Pos1Local = 0 and Pos2Local = 0, Command for "Position 0" (neutral position),
7. Example with VlvL
• OpenLocal = 1, Command for Valve to "Open"
• OpenLocal = 0, Command for Valve to "Close"
With Feature2.Bit4 = 1, two static local commands are assigned to a control input.
Feature bit
Number of the Feature bit:
• 11 for PIDConL, PIDConR, and PIDStepL
• 12 for MotSpdCL, VlvAnL, and OpAnL
Feature bit
Number of the Feature bit: 7
Bit = 1: Operator can change the value of analog input 1 (In01) if the input is not connected and
OS_Perm.Bit22 is set to 1.
2.1.9.95 Operator can change the setpoint via faceplate also in the "Local" mode
Feature2 bit
Number of the Feature2 bit: 6
Operator can change the setpoint via faceplate also in the "Local" mode
You can use this Feature2 bit to enable the input of a setpoint for the operator in the "Local"
mode.
The default setting is 0.
Bit = 0: Operator cannot change the setpoint in the "Local" mode.
Bit = 1: Operator can change the setpoint via faceplate in the "Local" mode.
2.1.9.96 Define the setpoint after stop and start of the motor
Feature2 bit
Number of the Feature2 bit: 7
2.1.9.97 Retain last output value in case of bad input signal status
Feature bit
Number of the Feature bit: 5
Feature2 bit
Number of the Feature2 bit: 8
2.1.9.99 Motor stop in end position depends only on the corresponding feedback signal
Feature bit
Number of the Feature bit: 15
Motor stop in end position depends only on the corresponding feedback signal
With this Feature bit, you can specify whether the motor stop in end position depends only on
the corresponding feedback signal or on both feedback signals.
The default setting is 0.
Bit = 0: Motor stop in end position depends on two feedback signals (FbkOpen and FbkClose).
For example, motor stop in the end position "Open" depends on both feedback signals "Opened"
and "Closed". In this case, FbkOpen = 1 and FbkClose = 0 are parameterized such that the drive
output control of the motor "Open" is reset.
Bit = 1: Motor stop in end position depends only on the corresponding feedback signal. For
example, motor stop in the end position "Open" depends only on the feedback signal "Opened".
In this case, only FbkOpen = 1 is parameterized such that the drive output control of the motor
"Open" is reset.
Feature bit
Number of the Feature bit: 9
Feature bit
Number of the Feature bit: 9
Feature/Feature2 bit
Number of the Feature/Feature2 bit: 10
Bit = 1: A bad signal status (16#00 or 16#28) in the automatic commands or external values will
be considered from the block. The block goes to a defined neutral position.
Feature bit
Number of the Feature bit: 20
Feature bit
Number of the Feature bit: 8
Inverter enable
You can use this Feature bit to specify whether, after the activation of Feature.Bit15
(Feature.Bit15 = 1), a frequency converter with a separate device infeed is to be used or the
inverter enable.
The default setting is 0.
Bit = 0: Frequency converter with separate device infeed
Bit = 1: Inverter enable
Feature bit
Number of the Feature bit: 14
Feature bit
Number of the Feature bit: 8
Feature bit
Number of the Feature bit: 8
2.1.9.108 Suppress MsgLock and “Out of service” mode for a connected message block
Feature/Feature2 bit
Number of the Feature2 bit: 11
Suppress MsgLock and “Out of service” mode for a connected message block
With this Feature/Feature2 bit, you can suppress the message lock with the
parameter MsgLock and the switchover to the “Out of service” mode for a connected message
block (EventTs, Event16Ts). Only the connected block over the parameter EventTsIn is
concerned. This allows generating messages also in the case of MsgLock = 1 or during a
switchover to the "Out of Service" mode in the main block. For example, if the main block goes
to the “Out of service” mode, the switchover can be messaged over a connection from the main
block output OosAct to an input Inx of EventTs/Event16Ts.
The default setting is 0.
Bit = 0: No suppression.
Bit = 1: A message lock with the parameter MsgLock and a switchover to the “Out of service”
mode are supressed for connected message block over EventTsIn.
Feature bit
Number of the Feature bit: 8
Note
If you change the variant of calculation, the limits CPI_AL_Lim and CPI_WL_Lim may have to
be adapted.
Feature bit
Number of the Feature bit: 6
Feature bit
Number of the Feature bit: 7
Feature bit
Number of the Feature bit: 8
Feature bit
Number of the Feature bit: 29
Note
FbAnOu
With V9.1 SP2, the channel block supports also the output a substitute value for Rbk. In case of
a invalid Rbk raw value the substitute vakue SubstRbk is output.
Feature bit
Number of the Feature bit: 29
Feature bit
Number of the Feature bit: 14
Bit = 1: After start of scale dosing the controls are deactivated during scale is in taring mode
(StandStill = 0).
Note
After start of scale dosing during taring mode (StandStill = 0) the display area in the
standard view shows "Taring".
Feature bit
Number of the Feature bit: 27
Feature bit
Number of the Feature bit: 9
Feature bit
Number of the Feature bit: 23
Blocks: CntOhSc, CountOh, CountScL, TotalL, MonAnL, MonAnS, MotL, MotRevL, MotSpdCL,
MotSpdL, VlvAnL, VlvMotL, and VlvPosL
Number of the Feature bit: 16
Blocks: DoseL
Number of the Feature bit: 31
Blocks: FmCont, FmTemp, PIDConL, PIDConR, PIDConS, PIDStepL, and ConPerMon
Bit = 1: Limits are visible but disabled in faceplate when disabled from block.
Feature bit
Number of the Feature bit: 31
Feature bit
Number of the Feature bit: 14
Feature/Feature2 bit
Number of the Feature bit:
• 3 for SelA16In, SelAn16L
• 4 for CntOhSc, CountScL, CountOh, TotalL
• 5 for PIDConS, PIDConR, PIDConL, PIDStepL, FmTemp, FmCont, MPC 10x10, KalFit,
ModPreCon, TimeTrig, AV, MonAnL, MonAnS, MonDiL, MonDi08, MonDiS
Number of the Feature2 bit:
• 1 for MotL, MotS, MotRevL, MotSpdL, MotSpdCL, VlvS, VlvL, Vlv2WayL, VlvMotL, VlvAnL,
VlvPosL
• 6 for DoseL
Refer the section "Out of service mode" of the respective blocks to know about the applicable
outputs.
Note
Number of the Feature bit is different for various families of the blocks. The Feature
"Changes signal status of outputs in OOS" has higher priority over the Feature "Reaction of the
switching points in the "Out of service" operating mode".
Feature bit
Number of the Feature bit: 7
Feature2 bit
Number of the Feature2 bit: 9
Feature bit
Number of the Feature bit: 11
2.1.9.125 Disable limit act output when limit value message is disabled
Feature/Feature2 bit
Number of the Feature2 bit: 12
Feature bit
Number of the Feature2 Bit: 13
Resetting Pending Error in Local Mode 1 & 3.
With this Feature bit, you define you can define whether the Pending Errors can be resetted by
using the faceplate/RstLi or not.
The default setting is 0.
Bit = 0: Resetting of pending errors cannot be possible via faceplate/RstLi.
Bit = 1: Resetting of pending errors can be possible via faceplate/RstLi.
Feature bit
Number of the Feature bit: 5
Timestamp calculation
The calculation of the time stamp TS_Out has been improved. You can select
via Feature.Bit5 whether the CPU time or the IO time is used.
• Bit5=0: IO time stamp (default setting)
• Bit5=1: CPU time stamp
Note
Modifications are done in the Pcs7DiIT block prevent invalid time stamping error messages.
Feature bit
Number of the Feature bit: 5
Feature bit
Number of Feature Bit: 6
Enable External time
With this function you can enable/disable External time.
Default = 0.
Bit = 0: External time is enabled to be used for trigger.
Bit = 1: External time is disabled.
Feature bit
Number of Feature Bit: 7
Switch over to AS time when Signal status of External time is bad i.e., if if ExtTimeQc <> 16#80
or 16#60
With this function you can switch to AS time if the signal status of the external time is bad.
Default = 0.
Bit = 0: No switch to AS time.
Bit = 1: Switch to AS time.
Feature bit 7 is effective only when External time is enabled (Feature bit6 =1).
Feature bit
Number of Feature Bit: 8
AS time enable or Disable.
With this function you can activate AS Time or the CPU time.
Default = 0.
Bit = 0: AS time disabled.
Bit = 1: AS time enabled.
Feature bit
Number of the Feature bit: 7
Use connectable inputs OpenLi, StopLi, CloseLi with CtrlLiOp
You can use this Feature bit to specify whether the block uses the inputs OpenLi, StopLi,
CloseLi as a function of CtrlLiOp or ModLiOp.
The default setting is 0.
Bit = 0: OpenLi, StopLi, CloseLi are used as a function of ModLiOp.
Bit = 1: OpenLi, StopLi, CloseLi are used as a function of CtrlLiOp.
Feature bit
Number of the Feature bit: 12
With Feature.Bit12 = 1 and NamurOff = 1
• Exceeding of the limit defined at input parameter HighLimit, leads to PV_HiAct.Value=1.
• Undershooting of the limit defined at input parameter LowLimit, leads
to PV_LoAct.Value=1.
Regardless Feature.Bit12, PV_HiAct.Value and PV_LoAct.Value will be set in case of
nominal range is left.
Feature bit
Number of the Feature bit: 3
With this Feature bit you can use both connected bypass information BypLix, Inx to bypass an
interlock input.
The default setting is 0
Bit3 = 0: BypLix.Value is used to bypass an interlock input.
Prerequisite: BypLix <> 16#FF
With a change of BypLix.Value the bypass of an interlock input BypInx is set to
BypLix.Value.
Bit3 = 1: BypLix.Value, Inx.Bit1 are used to bypass interlock inputs.
Prerequisite: BypLix <> 16#FF, Feature Bit2 =1, BypEn.Inx = 1
With a change of BypLix.Value, Inx.Bit1 the bypass of an interlock input BypInx is set to
"BypLix.Value OR Inx.Bit1". Both inputs are false to reset the bypass. After that operator
can change bypass over faceplate.
With changes of BypLix.Value or Inx.Bit1 the input BypInx is tracked. After that operator can
change again bypass over faceplate.
Feature/Feature2 Bit
Number of the Feature bit: 17
Drives (Feature2bit17) : MotL, MotRevL, MotSpdL, MotSpdCL, VlvL, VlvMotL, VlvAnL, VlvPosL
Operate blocks (Featurebit17): OpDi01, OpDi03, OpAnL
You can use the Feature bit "Resynchronization after startup" to track controls and block
state after CPU startup through feedback signals and readback value.
The default setting is 0.
Bit = 0: Startup without Resynchronization
Bit = 1: Startup with Resynchronization: The control outputs and block state are tracked through
the feedback signals and readback value.
Feature/Feature2 Bit
Number of the Feature bit: 18
Drives: MotL, MotRevL, MotSpdL, MotSpdCL, VlvL, VlvMotL, VlvAnL, VlvPosL
After leaving "Out of service" mode or after leaving simulation function you can use the
Feature2 bit to track controls and block state through feedback signals and readback value.
Operate blocks: OpDi01, OpDi03, OpAnL
After leaving "Out of service" mode you can use the Feature bit to track controls and block state
through feedback signals and readback value.
Feature2 Bit
Number of the Feature bit: 19
Drives: MotL, MotRevL, MotSpdL, MotSpdCL, VlvL, VlvMotL, VlvAnL, VlvPosL
After a control system fault (input CSF 1->0) you can use the Feature2 bit to track controls and
the block state through feedback signals and readback value.
The default setting is 0.
Bit = 0: Without Resynchronization
Bit = 1: Resynchronization after a control system fault
Feature/Feature2 Bit
Number of the Feature bit: 20
Drives (Feature2bit20) : MotL, MotRevL, MotSpdL, MotSpdCL, VlvL, VlvMotL, VlvAnL, VlvPosL
Operate blocks (Featurebit20): OpDi01, OpDi03, OpAnL
After a trigger (0->1) at StateTrkOn input, you can use the feature bit to track controls and the
block state through feedback signals and readback value.
The default setting is 0.
Bit = 0: Without Resynchronization
Bit = 1: Resynchronization after a trigger with StateTrkOn input
Feature2 Bit 21
Feature2 bit: MotL, MotRevL, MotSpdL, MotSpdCL, VlvL
Number of the feature bit: 21
Sometimes after a resynchronization it is not possible to see in which position and condition the
valve or the motor is, because the feedback signals are not plausible. In this case you have the
opportunity with Feature2 Bit21 Control with output StopCtrl and state “No Cmd” to
parameterize that the drive can control the position/state “No Cmd”.
Feature bit
Number of the Feature2 bit: 14
Feature2 bit: MotRevL, MotSpdCL, MotSpdL, VlvMotL, VlvPosL, VlvAnL
Stop position if direction of command changes to an interlocked direction/speed
For the function direction/speed-dependent interlocking (Feature2 Bit16 =1), you can use this
Feature bit to specify the behavior of control after a change of command from one direction/
speed in an interlocked one.
The default setting is 0.
Bit = 0: The drive continues to run in the current direction/speed.
Bit = 1: The drive changes in the Stop position.
Feature/Feature2 bit
Number of the Feature2 bit: 15
Difference MV-Rbk is monitored also in end position
You can use this feature bit to monitore the difference MV-Rbk in end positions. Valve with large
monitored end position ranges are possible.
The default setting is 0.
Bit = 0: Without monitoring the difference MV-Rbk in end positions
Bit = 1: With monitoring the difference MV-Rbk in end positions
The PosReached output depends on the feature bit. With Feature2 Bit15 =1 only if the
difference MV-Rbk is also within the PosDeadBand, the end position is reached.
Alarm delay for blocks with the function "Delay alarm for control deviation at setpoint step changes"
This type of alarm delay is used when temporary violations of set alarm thresholds of the control
deviation are to be suppressed at setpoint step changes. The alarm delay is parameterized at the
following inputs:
The effective delay time is calculated from the delay factor and the setpoint difference and is
specified at the output parameter:
Parameter Explanation
ER_A_DCOut Effective delay time at setpoint step changes for incoming alarms during
control deviation monitoring
Note
After a setpoint jump the function "Delay alarm for control deviation at setpoint step
changes" always only affects the limit to the direction of the setpoint jump and not to the
opposite limit. If the deviation value ER reaches the opposite limit (loop is overshooting), the
switch-on delay of the opposite side acts ER_A_DCOut =ER_A_DC, ER_AH_DC.
Pending alarms
Pending alarms are output at the output parameters ER_AL_Act and ER_AH_Act.
(5
>'HDGEDQG@
6339B2XW(5B([W
>'HDGEDQG@
A dead zone in the controller can help reduce the movements of the actuator and thus reduce
the energy consumption and wear of the actuator. This applies especially to mechanical
actuators, such as valves and pumps. The dead zone may also required in order to avoid small,
stable, continuous oscillations (working movement), which are caused by the quantization of
the control actions in the control loop.
Note
Calming the control signals via dead band is only possible when no structure splitting is active,
i.e. when PropFacSP = 1 and DiffToFbk = 0. Controller actions in the feedback branch
directly process the measured actual value instead of the control deviation and are therefore not
affected by the dead band.
• Remaining control deviations smaller than the dead band are ignored by the controller, i.e.
it does nothing even it can. Therefore, steady states of the actual value can occur, the average
time of which significantly differs from the setpoint.
• When such steady states occur at the edges of the dead zone, it must be expected that even
the smallest problems will cause control intervention (i.e. actuator energy consumption).
• Large dead zones have a negative effect on the control response of the control loop for
setpoint changes. This is because the controller "stops work", for example, in the rising phase
of a positive step response when entering the dead band. This can lead to creeping settling
time, or cause the controller to be activated again when the actual value exceeds the high
limit of the dead band in the form of an overshoot.
• After a fault event that leads to exiting the dead band, the controller brings the actual value
back only to the edge of the dead band, which has the above-mentioned disadvantages.
By setting Feature.Bit30, you can activate dynamic adjustment of the dead band. This
allows you to benefit from the advantages of a dead band without having to tolerate the above-
mentioned disadvantages.
When large control deviations occur (i.e. the dead band is exited), it is temporarily deactivate
until the controller returns the actual value to the proximity of the setpoint. The controller also
demonstrates control response for setpoint changes without a dead band in this way.
There is then a wait until it can be assumed that the process has settled on operating point. Only
then is the dead band activated again. When it is reactivated, the manipulated variable is set to
the mean of a sliding time window. This ensures that the actual value to be controlled settles
more in the middle of the dead band than at the edges. This avoids unnecessary shifting of the
mean value of the controlled variable from the setpoint, and thus poor stationary control
performance. The probability that the controlled variable is within the dead zone time is
increased, and further control actions are no longer necessary. This leads to reduced wear and
less energy consumption.
Note
If Feature.Bit30 = 1 is set, the ConPerMon block has to be connected with the controller. The
blocks PIDConL or PIDConR monitor this by checking the status signal of MeanMV.ST. In case
of Feature.Bit30 = 1 and MeanMV.ST = 16#78 the dynamic deactivation of deadband is not
possible and the output ErrorNum will be set to 52.
ErrorNum parameter. When the control zone is enabled, the controller operates according to
the following algorithm:
• If the process value PV exceeds the setpoint SP by more than ConZone, the value MV_LoLim
is output as the manipulated variable (controlled mode, in order to return to the control zone
as fast as possible).
• If the process value PV falls below the setpoint SP by more than ConZone, MV_HiLim is
output (controlled mode).
• (Only possible with PIDConL, not with FmTemp) In controlled mode of the control zone and
when the I component is enabled (TI<>0), the I component can be set in a variety of ways
when the control zone is entered, depending on three Feature bits:
x = any
The I component is always set to MV_Offset when the I component is disabled (TI=0). I.e.: The
control zone operates with the specified I_Part := MV_Offset with P or PD controlling.
Freezing of the I component with IntHoldPos or IntHoldNeg has no effect during
controlled mode due to the control zone.
• If the process value PV stays within the control zone (ConZone), the manipulated variable
assumes the value of the PID algorithm (automatic closed-loop mode).
Note
The change from controlled closed-loop mode to automatic closed-loop mode is based on a
hysteresis of 20% of the control zone. Make sure that the control zone has an adequate width
before you manually activate the control zone. An insufficient width of the control zone leads
to oscillation of the manipulated variable and of the process value.
overshoot or undershoot if the value of the output minimum or maximum manipulated variable
is a long way from the stationary manipulated variable required for the new operating point.
Note
This function is not available for the FmCont, FmTemp, and ModPreCon blocks.
See also
Forcing operating modes (Page 47)
The disturbance variable is connected to the FFwd Parameter. It is limited to the FFwdHiLim and
FFwdLoLim limits. If the disturbance variable is outside or at the limits, this is indicated by the
FFwdHiAct = 1 or FFwdLoAct = 1 output parameters.
3URS)DF63
B
*DLQ 7, 3URFHVV
63 V 09 39
3URS)DF63
7' V 'LII7R)EN
2.1.11 Messaging
Area of application
A sensible area of application for setting alarm delays can, for example, be a motor. When it is
started, an elevated starting current can occur and this could be reported depending on the
configured limit. Since this usually settles down to a value below the set limit, the alarm would
not make sense. In this case, the alarm delay that is intended to bridge the duration of the active
alarm is used.
Note
Alarms that are really wanted are, naturally, also delayed when an alarm delay is used. Therefore
select the delay period prudently!
Note
An alarm delay is displayed with the following symbol in the limit view and in the faceplate
overview:
Blocks with one time value for the alarm delay per limit pair
The alarm delay is used when brief violations of the set alarm thresholds are to be suppressed.
Note
The message classes Alarm, Warning and Tolerance are not valid for user-configured message
classes. Please take into consideration the validity of terms for user-configured message classes
(Page 47).
Pending alarms
Pending alarms, warnings, or tolerances are output at the corresponding output parameters:
• XXX_AH_Act = 1: Alarm limit (high) reached or violated
• XXX_AL_Act = 1: Alarm limit (low) reached or violated
• XXX_WH_Act = 1: Warning limit (high) reached or violated
• XXX_WL_Act = 1: Warning limit (low) reached or violated
If a message is active at one of these outputs, this is indicated by a 1.
See also
User-configured message classes (Page 47)
Blocks with two time values for the alarm delay per limit pair
The alarm delay is used when brief violations of the set alarm thresholds are to be suppressed.
Note
The message classes Alarm, Warning and Tolerance are not valid for user-configured message
classes. Please take into consideration the validity of terms for user-configured message classes
(Page 47).
Pending alarms
Pending alarms, warnings, or tolerances are output at the corresponding output parameters:
• XXX_AH_Act = 1: Alarm limit (high) reached or violated
• XXX_AL_Act = 1: Alarm limit (low) reached or violated
• XXX_WH_Act = 1: Warning limit (high) reached or violated
• XXX_WL_Act = 1: Warning limit (low) reached or violated
• XXX_TH_Act = 1: Tolerance limit (high) reached or violated
• XXX_TL_Act = 1: Tolerance limit (low) reached or violated
If a message is active at one of these outputs, this is indicated by a 1.
See also
User-configured message classes (Page 47)
Alarm delay for blocks with two time values for each individual limit
This form of alarm delay is used for the blocks PIDConL, PIDConR, and MonAnL.
Note
The message classes Alarm, Warning and Tolerance are not valid for user-configured message
classes. Please take into consideration the validity of terms for user-configured message classes
(Page 47).
The alarm delay is used when brief violations of the set alarm thresholds are to be suppressed.
The alarm delay is configured at the following inputs:
Pending alarms
Pending alarms, warnings, or tolerances are output at the corresponding output parameters:
• XX_AL_Act = 1: Alarm limit (low) reached or violated
• XX_AH_Act = 1: Alarm limit (high) reached or violated
• XX_WL_Act = 1: Warning limit (low) reached or violated
• XX_WH_Act = 1: Warning limit (high) reached or violated
• XX_TL_Act = 1: Tolerance limit (low) reached or violated
• XX_TH_Act = 1: Tolerance limit (high) reached or violated
If a message is active at one of these outputs, this is indicated by a 1.
See also
User-configured message classes (Page 47)
Separate delay times for each alarm (Page 183)
You can specify the following messages for these instance-specific messages:
• Message class
• Priority of the message
• Message text
• Message auxiliary value
• Acknowledge behavior
Additional information is available in the descriptions of the message functionality of the
individual blocks and in the PCS 7 Configuration Manual Operator Station under "How to
configure the user-specific messages".
See also
Time stamp (Page 235)
Note
With the block OpAnL, this function is independent of Feature.Bit25.
Time stamp
The time stamp is the assignment of time information to the status change of a binary process
signal. The status change of the signal is signaled together with the time information.
Use the EventTS block to report time stamped signals.
For more information on time stamping and how to configure it, please refer to the "PCS 7 - High-
Precision Time Stamping Function Manual".
Areas of application
Areas of application of the time stamp are for example:
• Accurately-timed detection of problems in process-related equipment. The time stamp
enables you to explicitly identify signals that indicate the cause of the failure of a process unit.
• Analysis of system-wide interrelationships
• Detection and reporting of the sequence of time-critical signal changes
Error handling
The system block ImDrvTs recognizes when the time stamp function in the I/O devices is
defective and forwards this information to the Pcs7DiIT block. This then forms the time stamp
using the current CPU time and sets the signal status of TS_Out output parameter to "Bad, due
to device". The EventTS block then uses the current time of the CPU as the time stamp. You can
find additional information in the "PCS 7 - High-Precision Time Stamping Function Manual".
2.1.12.1 Display and operator input area for process values and setpoints
Display and operator input area for process values and setpoints
You specify the upper and lower area limits in the faceplate using interconnectable input
parameters for the following:
• Display areas (bar display)
• Operator input area (for example setpoint and manipulated value)
• Input area for the limit values
– Up to 7 numbers (including a decimal separator and a minus sign) are possible in the
faceplates
The interconnectable input parameter is a structured variable that contains two analog values.
Refer to the descriptions of the individual blocks for the relevant input parameters.
Note
"Small" blocks
With "Small" blocks, you can call up only one faceplate from the standard view.
Note
You can only configure the button in the standard view (SelFp1) with interlock blocks. There
are no buttons with the GainSched block.
Button label
You can change the button labels in the "OS additional text" attribute to "SelFp1"/"SelFp2".
Note
There is also an alternative solution for labeling the buttons:
• Open the process picture in WinCC GraphicsDesigner.
• Open the object properties of the block icon.
• Under Configurations, assign the desired text to the attribute UserButtonText1 or
UserButtonText2.
The main difference between this solution and the first solution is that the labels are only
specified when the faceplate above the block icon is opened. This solution is therefore outdated.
Note
Interconnection of the Out output parameter to multiple blocks is not permitted. The reason for
this is that a direct relationship must be established between the button in the faceplate and the
faceplate to be opened by it.
To do this, you need to specify how the buttons are labeled yourself using the attributes "Text0"
and "Text1" in the object properties of the block. These texts are displayed in the standard view
and preview of the faceplate.
Note
Special notes for channel blocks PCS7AnIn, PCS7AnOu, FbAnIn and FbAnOu
You can use the S7_enum attribute to display the unit in plain text in the CFC editor for these
blocks.
Note
In block icons, the update/refresh time of the units is 1 h. If the unit is changed from CFC, the new
unit will be visible in the block icon after 1 hour or if the process picture is reloaded. In faceplates,
the update/refresh time of the units is 5 seconds, so the new unit will be visible after 5 s.
Customer-specific units
It is possible to use units which differ from the IEC 61158-2 standard. You can define your own
units in the range 1 to 199 in an XML file.
The name of the XML should be APLCustomerUnits.xml and should be placed in the project path
in the folder "GraCS" on both server and client.
Below is an example to describe the content of the XML file APLCustomerUnits.xml:
The "Unit id" value should be given to XXX_Unit parameter in the function blocks.
Note
The XML is read in only once when WinCC runtime is activated. If any changes are done in the
XML later, you must deactivate, close, and activate the WinCC runtime again to reflect the
changes.
Using the unit of measure with controllers for the ConPerMon block
For controller blocks, the current unit of measure is output via output parameter XX_UnitOut .
If you use the ConPerMon block, you must switch this output parameter with the corresponding
input parameter XXX_Unit on the ConPerMon block.
Note
Due to space constraints on the system, not all units referred to can be displayed in totality. The
display of the measurement units is left-aligned. If you want to abbreviate the unit of
measurement, use the function Customer-specific units.
List of all units of measure in accordance with specification PROFIBUS PA Profile for Process
Control Devices up to version PNO V3.02.
1625 gf/cm2g
1626 kgf/cm2a
1627 kgf/cm2g
1628 SD4°C Standard density at 4°C
1629 SD15°C Standard density at 15°C
1630 SD20°C Standard density at 20°C
1631 PS Metric horsepower
1632 ppt Parts per trillion = 1012
1633 hl/s Hectoliters per second
1634 hl/min Hectoliters per minute
1635 hl/h Hectoliters per hour
1636 hl/d Hectoliters per day
1637 bbl (liq)/s Barrels (US liquid) per second
1638 bbl (liq)/min Barrels (US liquid) per minute
1639 bbl (liq)/h Barrels (US liquid) per hour
1640 bbl (liq)/d Barrels (US liquid) per day
1641 bbl (fed) Barrel (U.S. federal) = 31 gallons
1642 bbl (fed)/s Barrels (US federal) per second
1643 bbl (fed)/min Barrels (US federal) per minute
1644 bbl (fed)/h Barrels (US federal) per hour
1645 bbl (fed)/d Barrels (US federal) per day
1997 none None
1998 Unknown unit To be used when the unit of meas‐
ure is not known during configura‐
tion
1999 Special Special units
2000 inch/s2 Inch per square second
2001 g Grams
2002 mils Milli inch
1
A notation different to the PA profile must be used in order to represent this unit in conformity
with the system.
2
"m2" is used instead of "m3" in the Chinese and Japanese documentation.
2.1.14 Resynchronization
With a resynchronization the control outputs and the state of a block are adapted to a running
process. This is acheived by tracking the control outputs for one cycle through the actual
feedback signals (FbkXxx) or readback values (Rbk, PV_In).
The resynchronization is enabled over feature bits.
In the first cycle after OB100 commands, block state and control outputs are tracked through the
feedback signals and readback values from the process. If they are not available or plausible, the
controls are put on hold.
In the first cycle after leaving "Out of service" commands, block state and control outputs are
tracked through the feedback signals and readback values from the process. If they are not
available or plausible, the actual position is not changed. In the standard view and preview the
operator can see which state the block would assume after leaving "Out of service" mode.
In the first cycle after leaving simulation function commands, block state and control outputs are
tracked through the feedback signals and readback values from the process. If they are not
available or plausible, the actual position is not changed. In the standard view and preview the
operator can see which state the block would assume after leaving simulation function.
In the first cycle after leaving control system fault (CSF 1->0) commands, block state and control
outputs are tracked through the feedback signals and readback values from the process. If they
are not available or plausible, the actual position is not changed. In the standard view and
preview the operator can see which state the block would assume after leaving control system
fault.
After a trigger (0->1) at StateTrkOn input commands, block state and control outputs are tracked
through feedback signals and readback value. If they are not available or plausible, the actual
position is not changed. In the standard view and preview the operator can see which state the
block would assume after a trigger of StateTrkOn input.
09B+L/LP
RSHQ
LQWHUPHGLDWH
3RV'L2SHQ
3RV'L&ORVH
09B/R/LP FORVH
095EN
Over Feature2 Bit15 the monitoring can switch on also in the end positions.
Note
@PCS7TypicalsAPLV7.PDL and @TemplateAPLV7.PDL is no longer supplied with the Setup
There are two types of block icons (V9.0), those with a display of the instance-specific name and
those without:
Block icon of MotL without instance-specific name The toolbar only shows the information
that is actually available.
Block icon of PIDConL without instance-specific name The toolbar only shows the infor‐
mation that is actually available.
The old block icons are located in the template "@PCS7TypicalsAPLV7.pdl" and
"@TemplateAPLV7.PDL".
There are two types of block icons (V7.1), those with a display of the instance-specific name and
those without:
Block icon of MotRevL without instance-specific name The toolbar only shows the infor‐
mation that is actually available.
Block icon of PIDConL without instance-specific name The toolbar only shows the infor‐
mation that is actually available.
You can select one of these block icons. See section Configuring the block icons (Page 272) for
more information.
A block icon has several display areas:
• CPU stop
• Instance-specific name
• Icon for the block
• Analog value display
• Status bar for the block status
NoteView documents
You can configure a maximum of three files per block symbol instance, which can be selected in
the memo view during the process control and are displayed in a separate window.
These files must be located in the GraCS folder in the NoteView subdirectory.
The file names are configured at the block icon at the attributes NoteView1, NoteView2 and
NoteView3. Only .mht file formats are supported and the file extension ".mht" must be given (for
exmaple, " File1.mht") at the configuration.
Note
1. A maximum of three files are configured per block instance.
2. Only .mht file formats are permitted.
3. The file extension *.mht must be given at the configuration.
4. In multi-projects, all relevant files are stored in the path of the server project (OS project path
>> GraCS >> NoteView >> (files in MHT format)).
5. If the files are not configured at the block icon, the file selection and the "Open" button are
deactivated in the memo view (that is, grayed out).
6. If the file formats other than .mht files are configured, the error message "Invalid file format"
is displayed when the file is opened.
7. The maximum allowed file size is 25 MB. If a file exceeds this size, the error message "File size
exceeded" is displayed when the file is opened.
Instance-specific name
The name of the associated block is shown in the instance-specific name, for example for the
PIDConL block:
You can change this name in the object properties of the instance block.
There are block icons with or without display of the instance-specific name. Refer to the
individual block descriptions to learn about them.
You can reach the visible display for blocks without display of the instance-specific name in two
different ways:
• Displaying individual instance-specific names: Click on the block icon while holding down
the Shift key: The name remains visible as long as the process picture is displayed.
• Displaying all instance-specific names at once: All instance-specific names can be made
visible in a process picture at once by clicking a button. To do this, copy this button into the
process picture of the chart from the @TemplateAPLV9.PDL or insert this button in the
"button area" of WinCC. If you insert it into the button area, read the manual section "PCS 7
OS Process Control " > "Layout of the User Interface".
The instance-specific names are hidden once more by clicking the button again.
This symbol can be positioned at various locations, 0°, 90°, 180° and 270°. Refer to the
Configuring the block icons (Page 272) section for more on this. You can change the operating
mode of the block by right-clicking on the status display. Refer to the Operation via the block icon
(Page 274) section for more on this.
Note
Block icons for motors and valves are available in various mounting positions and forms of
representation. However, a general state icon is always displayed in the faceplates that does not
consider the mounting position and form of representation in the block icons.
Refer to the Configuring the block icons (Page 272) section for more on this.
These analog values can be controlled according to the Operator control permissions
(Page 290). See also the section Operation via the block icon (Page 274) for more on this.
As of V9.0 block icons, when the actual values are displayed with limit monitoring in the analog
value displays, the background and font colors for an alarm, warning or tolerance correspond to
the message colors.
Note
As of V9.0 block icons, when the actual values are displayed with limit monitoring in the analog
value displays, the background and font colors for an alarm, warning or tolerance, control
system fault or control system fault correspond to the message colors.
If the analoge value display shows *****, the display field is too small for the parameterized
format specification. In this case, adapt the format specification AnalogValueFormatx in the
block icon APL_BLOCK_ICON.
For specification of the format, refer to Decimal points for the analog value display (Page 282).
The arrangement of icons in the following tables is prioritized from high to low.
The following elements can be displayed:
Icon Meaning
No messages are output.
An alarm is triggered.
An warning is triggered.
A tolerance violation for the high tolerance limit has been triggered.
A tolerance violation for the low tolerance limit has been triggered.
Note
The message classes Alarm, Warning and Tolerance are not valid for user-configured message
classes. Please take into consideration the validity of terms for user-configured message classes
(Page 47).
Note
For user-configured message classes, the symbols for high/low alarm, warning and tolerance
limits are displayed only for limit violations which are triggered within the APL blocks with the
colors of the user-configured message classes.
Operating modes
Refer to the Overview of the modes (Page 78) section for more on this.
Icon Meaning
The block is in automatic mode.
Note
No symbol is displayed for the "On" operating mode (no green "O" displayed) if the block only has
the operating modes "On" and "Out of service".
Icon Meaning
Setting the setpoint internally
Signal status
Refer to the Forming and outputting signal status for blocks (Page 118) section for more on this.
Icon Meaning
The block is in simulation.
Icon Meaning
At least one value has been forced
Value is tracked
Interlocks
Refer to the Interlocks (Page 109) section for more on this.
Icon Meaning
Block is not interlocked.
Block is interlocked.
Bypass protection.
Memo display
Icon Meaning
A message is available in the memo view.
Customer-specific icons
In the block icons, the icons can be replaced with customer-specific icons. A subdirectory must
therefore be created in the OS project directory "GraCS" and the customer-specific icons must be
inserted there with the same name as before. The name of the subdirectory must be adapted in
the block icon in the "PictureDirectory" property ("Configurations" group). The icons in the
subdirectory are not changed by the OS project editor or a new version of APL faceplates.
Note
• The "PictureDirectory" property is an instance-specific property. This means that the
adaptations of block icons already configured in the process pictures are not changed by an
update of the block icons in the process picture.
• We recommend that you adapt this property in the process picture and not in the
"@PCS7TypicalsAPLVx.pdl" or "@TemplateAPLVx.PDL" pictures. The "@" pictures are system
pictures and are replaced by the new version of APL faceplates. Customer changes will be
lost.
• In the WinCC Graphics Designer, the PCS 7 "Export Objects" wizard can be used to generate
a list of adaptations of instance-specific properties in the block icons. The "PictureDirectory"
property can be changed in the exported list and collectively transferred back into the block
icons with the PCS 7 "Import Objects" wizard.
• It is possible to use several subdirectories. This can be useful to create different variants of
block icons in the process pictures.
See also
Motor protection function (Page 108)
Forming the group status for interlock information (Page 115)
User-configured message classes (Page 47)
The new block icons are in the template picture "@PCS7TypicalsAPLV9.PDL" and
"@TemplateAPLV9.PDL".
Note
@PCS7TypicalsAPLV7.PDL and @TemplateAPLV7.PDL is no longer supplied with the Setup.
If you still use the V7 block icons in your project and they should continue to be used, the V7
template "@PCS7TypicalsAPLV7.PDL" must be present in the OS project directory (GraCS). In
addition, you must delete the newer template images "@PCS7TypicalsAPLV9.PDL" or
"@PCS7TypicalsAPLV8.PDL" from the OS project directory.
Deselect also the update for the V9 template in the OS project editor on the basic data tab.
2&0SRVVLEOH
2SHUDWLQJDQGPRQLWRULQJ
&UHDWHEORFNLFRQ
0(6UHOHYDQW
You can find the names (numerical entry) of the respective block icons in the description for the
blocks (Operator Control and Monitoring section).
If you do not enter a number for a block icon, the number 1 is always used for the block icon. The
template for automatically generated block icons is @PCS7TypicalsAPLV9.PDL.
Additional information
• Manual Process Control System PCS 7; Engineering System
You can find information on exporting/importing and updating these objects in the WinCC
Information System, section "Graphic Object Update Wizard". Use the "TemplateControlAPL.cfg"
configuration file for these wizards.
Note
• The procedure for changing the tooltip text of the block icons is described in the APL Style
Guide. Otherwise, this property may not be changed.
• Process value (black, with and without decimal places, with and without color change at limit
violations)
• Setpoint (blue, with decimal places)
• Feedback value (red, with decimal points), not available for types 3 and 4
With FmCont and FmTemp as a step controller without feedback, there is no feedback value
• "Ramp active" indication is not available in FMCont and FMTemp blocks.
• only PIDStepL: Position feedback value (green, with decimal points), not available for types
3 and 4
• Interlock without reset (only for PIDConR and PIDConL)
Additional information on the block icon and the control options in the block icon is available in
the following sections:
• Configuring the block icons (Page 272)
• Block icon structure (Page 265)
• Operation via the block icon (Page 274)
Properties of the block icon for interlock blocks Intlk02, Intlk04, Intlk08, Intlk16
A variety of block icons are available with the following functions:
• Signal status
• Memo display
• Output signal
1 Intlk04
1 Intlk08
1 Intlk16
2 Intlk02
2 Intlk04
2 Intlk08
2 Intlk16
1 Intlk04
1 Intlk08
2 Intlk02
2 Intlk04
2 Intlk08
2 Intlk16
3 Intlk02
3 Intlk04
3 Intlk08
3 Intlk16
SFC-Plan
2. Status indicators:
0 0 0 1 .SFC_STATE RUN
0 0 1 0 .SFC_STATE COMPLETED
0 0 1 1 .SFC_STATE HELD
0 1 0 0 .SFC_STATE ABORTED
0 1 0 1 .SFC_STATE STARTING
0 1 1 0 .SFC_STATE COMPLETING
0 1 1 1 .SFC_STATE ERROR_COMPLETING
1 0 0 0 .SFC_STATE HOLDING
1 0 0 1 .SFC_STATE RESUMING
1 0 1 0 .SFC_STATE ERROR
1 0 1 1 .SFC_STATE HELD_ERROR
1 1 0 0 .SFC_STATE RESU_ERROR
1 1 0 1 .SFC_STATE ABORTING
1 1 1 0 .SFC_STATE STOPPING
1 1 1 1 .SFC_STATE STOPPED
See also
Block icon structure (Page 265)
Configuring the block icons (Page 272)
Operation via the block icon (Page 274)
Note
The static picture components for the valves are visible here above the valve icon.
Note that all the block icons of the APL are located on layer 0 of the process picture. Layer 1 is
intended for the static picture component. This ensures that the static picture component is
always over the block icon. If you have changed this layer of the block icon, the static picture
component should always be placed in a higher layer.
Note
If the analoge value display shows *****, the display field is too small for the parameterized
format specification. In this case, adapt the format specification AnalogValueFormatx in the
block icon APL_BLOCK_ICON.
Note
You must reopen the faceplate after changing the scale value. Already opened faceplate will not
be scaled if the scale value is changed.
Note
Some of the illustrations of the faceplate views and block icons in the help for the PCS 7
Advanced Process Library are examples or offline representations. The representations on
runtime may vary.
The views differ depending on the block functions. All blocks that have faceplates provide a
status bar where you can see the most important information relating to the block status. There
are additional functions available that are described in the next sections.
Note
Display elements of block inputs with 16#FF as their status default, are only shown when their
block inputs are interconnected (status ≠ FF). Exception: The values for Gain, TI and TD are
always displayed for controller blocks.
Note
The message classes Alarm, Warning and Tolerance are not valid for user-configured message
classes. For user-configured message classes, message types depend on the project-specific
setting. Please take into consideration the validity of terms for user-configured message classes
(Page 47).
This display shows you the active delay time. You will find more detailed information in section Display of delay
times (Page 293).
The "dead band" function is temporarily deactivated.
Icon Identifier
Standard view
Message view
Trend view
Ramp view
Preview
Memo view
Batch view
Setpoint view
Parameter view 4
Quantity view
Flow view
Note
The buttons are unavailable when views cannot be selected.
Note
You can learn about additional operator controls in the descriptions of the individual blocks.
Note
Exceptions to the uses described above are listed in the descriptions of the individual views.
Each operation is assigned with an operator authorization level in the faceplates. This fixed
assignment can be changed for each instance at the "operator authorization level" property of
an I/O in the AS block (for example, SP_Int with PIDConL). The following assignment applies:
Operator authorization level in the user man‐ Value "Operator authorization level" property
agement
Process controls 1
Higher process controls 2
Highest process controls 3
Extended operation 1 4
Extended operation 2 5
Note
• The free three assignments in the upper table can be changed in the block icon at the
properties "OperationLevel1_backup", "OperationLevel2_backup" and
"OperationLevel3_backup". Any operator authorization level from the user management can
be assigned the values 1 to 3. This type of instance-specific configuration is still available only
for reasons of downward compatibility and should no longer be used in new projects.
• The controls for the message system (e.g. acknowledge messages) and trend display (e.g.
export) are fixed across the system and cannot be changed via the AS block.
The "Lock messages" control can be changed per OS Server/ Station via the internal variable
"@LockMessageAuthLevel" with the value of the operator authorization level from the
user management (for example, value "6" for "Higher process controls").
Note
If you interconnect a parameter that is also listed in OS_Perm as a parameter, you have to reset
the corresponding OS_Perm bit.
See also
Enabling local operator authorization (Page 172)
Requirements
You can change the operating state, operating mode and other parameters if needed in
faceplates if you have the corresponding operator control permission (OS_Perm). This operator
control permission can be configured in the engineering system (ES).
(1) The mouse cursor changes when you place it over the following button:
When you click on the button with the mouse pointer, the bottom of the faceplate expands. You
now see the field for changing the operating mode, for example.
(2) Field for changing the operating mode, operating state etc. This example describes changing
the operating mode.
If the indicators for the operating state is currently located in this field and you have configured
text for specific instances, this text is also shown. You can find more information about this in the
section Labeling of buttons and text (Page 239).
(3) The text on this button is gray. You cannot select this operating mode due to the following
reasons:
• This operator control permission for this operating mode cannot be configured in the
engineering system (ES).
or
• The operating mode is already selected at this time.
or
• Due to the technology, you cannot switch from the operating mode currently set and the
desired operating mode.
(4) The text on this button is black. You can switch to this operating mode.
How to change the operating mode (using the PIDConL block in standard view as an example)
1. Click one of the selectable buttons in the operating mode field.
2. Confirm your selection by clicking "OK".
3. If you do not want to apply your selection, click "Cancel".
After clicking the "OK" or "Cancel" button, the faceplate is reduced again to its original form.
Requirements
You can change the values in faceplates and in the block icons if you have the corresponding
operator authorization (OS_Perm). This operator permission can be configured in the
engineering system (ES). The following example shows how values are changed via the
faceplate.
(1) The background color of the input box is white. You can change the value. The mouse pointer
changes when you place it over the input box:
(2) The background color of the input box is gray. You cannot change the value.
(3) If you click on the input box, the bottom of the faceplate expands. You now see the field for
changing values.
Note
When the interlock is active, the High and Low limits of the operation area are considered for
VlvPosL and VlvAnL blocks.
Note
Analog value format should be configured to accommodate the smallest change triggered by
operating range and DirectOperationValue. This ensures proper operation and no
disabling of direct operation in operation area.
• Example 1:
Operating range: 0 ~ 1
Direct Operation Value: 0.5%
Smallest possible change is 0.005.
Hence AnalogValueFormat should have atleast 3 decimal places - ##0.000.
• Example 2:
Operating range: 0 ~ 100
Direct Operation Value: 0.5%
Smallest possible change is 0.5.
Hence AnalogValueFormat should have atleast 1 decimal place - ##0.0Properties
DirectOperationValue: Block Icon>Object
Properties>Configurations>DirectOperationValue
AnalogValueFormat: Block Icon>Object Properties>Configurations>AnalogValueFormat
If text is configure for these commands, it is displayed as additional text and as button labels for
command selection. You can find more information about this in chapter Labeling of buttons
and text (Page 239)
(3) High and low scale range for the process value
These values provide information on the display range (PV_OpScale) for the bar graph of the
process value. The scale range is defined in the Engineering System.
(7) Display and change the manipulated variable including signal status
This area shows the current "Manipulated variable" (MV) with the corresponding signal status.
Refer to chapter Changing values (Page 296) for information on changing the manipulated
variable. You can only make a change in manual mode.
This area shows the current position feedback in the form of a bar graph. The visible area in the
bar graph depends on the configuration in the Engineering System (ES).
(11) Navigation button for switching to the standard view of the ConPerMon block
Use this navigation button to reach the standard view of the ConPerMon block. The visibility of
this navigation button depends on the configuration in the Engineering System (ES).
Refer also to chapter Opening additional faceplates (Page 238) for more on this.
(12) Navigation button for switching to the standard view of any faceplate
Use this navigation button to reach the standard view of a block configured in the Engineering
System. The visibility of this navigation button depends on the configuration in the Engineering
System (ES).
Refer also to chapter Opening additional faceplates (Page 238) for more on this.
Note
"Ramp active" indication is not available for FMCont and FMTemp blocks in the Standard view.
YY X
X_ Y
Z
YX
YW [
\
X` Z
X^ ]
^
X]
_
X\ ]
X[
`
XZ XW
XY XX
Refer to the Switching operating states and operating modes (Page 294) chapter for information
on switching the setpoint specification.
For more information on the setpoint specification, refer to the Setpoint specification - internal/
external (Page 138) chapter.
(3) High and low scale range for the process value
These values provide information on the display range (PV_OpScale) for the bar graph of the
process value. The scale range is defined in the Engineering System.
(7) Display and change the manipulated variable including signal status
This area shows the current "Manipulated variable" (MV) with the corresponding signal status.
Refer to chapter Changing values (Page 296) for information on changing the manipulated
variable. You can only make a change in manual mode.
This area shows the current position feedback in the form of a bar graph. The visible area in the
bar graph depends on the configuration in the Engineering System (ES).
(11) Button for switching to the standard view of the ConPerMon block
Use this button for the standard view of the ConPerMon block. The visibility of this button
depends on the configuration in the Engineering System (ES).
Refer also to chapter Opening additional faceplates (Page 238) for more on this.
Note
"Ramp active" indication is not available for FMCont and FMTemp blocks in the Standard view.
See also
Labeling of buttons and text (Page 239)
Refer to the Switching operating states and operating modes (Page 294) chapter for information
on switching the setpoint specification.
For more information on the setpoint specification, refer to the Setpoint specification - internal/
external (Page 138) chapter.
(3) High and low scale range for the process value
These values provide information on the display range (PV_OpScale) for the bar graph of the
process value. The scale range is defined in the Engineering System.
(7) Display and change the manipulated variable including signal status
This area shows the current "Manipulated variable" (MV) with the corresponding signal status.
Refer to chapter Changing values (Page 296) for information on changing the manipulated
variable. You can only make a change in manual mode.
This area shows the current position feedback in the form of a bar graph. The visible area in the
bar graph depends on the configuration in the Engineering System (ES).
(11) Button for switching to the standard view of the ConPerMon block
Use this button for the standard view of the ConPerMon block. The visibility of this button
depends on the configuration in the Engineering System (ES).
Refer also to chapter Opening additional faceplates (Page 238) for more on this.
Note
"Ramp active" indication is not available for FMCont and FMTemp blocks in the Standard view.
See also
Labeling of buttons and text (Page 239)
X_
X^
X
XY
Y
X]
X\ Z
[
X[ \
Z
XZ
XY
X_
]
XX
^
XW
`
_
(3) High and low scale range for the process value
These values provide information on the display range (PV_OpScale) for the bar graph of the
process value. The scale range is defined in the Engineering System.
If text is configured for these commands, it is displayed as status text and as button labels for
command selection. You can find more information about this in section Labeling of buttons and
text (Page 239)
Note
"Ramp active" indication is not available for FMCont and FMTemp blocks in the Standard view.
See also
Opening additional faceplates (Page 238)
(1), (9) Switching between the input values 1 to 8 and 9 to 16 (for Intlk16 only)
The buttons (1) or (9) are displayed depending on the view you are in. These buttons are only
available for the Intlk16 block.
The Intlk16 block provides two views:
• When you are in the first view, the input values 1 to 8 are available in the area (12). The button
(9) is displayed. You switch to the second view by clicking on the button (9).
• When you are in the second view, the input values 9 to 16 are available in the area (12). The
button (1) is displayed. You switch back to the first view by clicking on the button (1).
Logic
Color of the field AND OR
Gray Block is not used (only for display in the faceplate,
interlock logic still enabled), set using
the NotUsed = 1 parameter
Blue Excluded (bypass)
Yellow Simulated
Red Interlocked
Green Not interlocked
For more information on the operation, refer to the section Switching operating states and
operating modes (Page 294).
Note
This function can only be executed in the faceplate with "high-level operating permission".
Note
Operator permissions via OS_Perm do not depend on the Feature.Bit5 setting. You can find
additional information in section Activate OS_Perm bits (Page 170).
You can reset the first-in (initial) signal with the button (10).
Note
This function can only be executed in the faceplate with "process control" operating permission.
You can find additional information on this in the section Recording the first signal for interlock
blocks (Page 60).
For more information on the operation, refer to the section Switching operating states and
operating modes (Page 294).
(8) Display of input values (BOOL) with signal status (in front of the field)
These fields show the interlock information associated with the analog value (13) with a signal
status:
• 1 = "Good" state
• 0 = "Locked"
(11) Navigation button for switching to the standard view of any faceplate
Use this navigation button to open the standard view of a block configured in the engineering
system. The visibility of this navigation button depends on the configuration in the engineering
system (ES).
You can find additional information on this in the section Opening additional faceplates
(Page 238).
Note
If a text is added to the "OS additional text" field of the input parameter (INxx), this text will be
displayed even if the "Identifier" text field of the input parameter (AVxx) is not empty. If the "OS
additional text" field of the input parameter (INxx) is empty, the "Identifier" text of the input
parameter (AVxx) is displayed.
The number of input values may vary depending on the selected interlock block:
• Intlk02: the input values 1 and 2 are available.
• Intlk04: the input values 1 to 4 are available.
• Intlk08: the input values 1 to 8 are available.
• Intlk16: the input values 1 to 8 are available. The input values 9 to 16 become available by
pressing the button (9). You can find additional information on this topic in the description
for (1) and (9).
This display can be used only if Feature2.Bit2 Separate evaluation for excluded and
simulated interlock signals (Page 164) is active. If additionally the input BypEn.Inx = 1, this
interlock input will be set in bypass.
(2) "Settings"
You can activate the following functions for the controller in this area:
• "PID optimization": ☑ (OptimEn) With pushing the button “Start Controller Optimization” in
the tool “PCS7 PID-Tuner” a controller optimization will be activated.
• "SP := PV in manual mode": ☑ Bumpless switchover from manual mode to automatic mode
• "SP := SP external": ☑ Bumpless switchover of the setpoint for setpoint switchover from
"external" to "internal". The internal setpoint is tracked to the external one.
– With the PIDConR block, this area is only visible if you have set the Feature bit Switching
operator controls for external setpoint to visible (Page 156) to 1.
(3) "Parameters"
In this area, you change parameters and therefore influence the controller. Refer to
the Changing values (Page 296) section for more on this.
You can influence the following parameters:
• "Gain": Proportional gain
• "P in feedforw path" : Proportional action to the feedback path (0 to 1),
– 0 = Proportional action is completely in the feedback path
– 1 = Proportional action is completely in the feedforward path
(only with PIDConL, PIDConR, and PIDStepL)
• "Integral time": Integral action time in [s]
• "Derivative time TD": Derivative action time in [s]
• "Derivative gain": Gain of the derivative action
• "D in feedback path": Derivative action is moved to the feedback path (only with PIDConL,
PIDConR, and PIDStepL)
• "Dead band": Width of dead band
Dead band is temporarily disabled
• "Control zone": Width of the control zone (only with PIDConL block)
• "Motor actuating time": Motor actuating time [s] (for PIDStepL block only)
• "Minimum pulse duration": Minimum pulse duration [s] (for PIDStepL block only)
• "Minimum break duration": Minimum break duration [s] (for PIDStepL block only)
(5) "Service"
You can select the following functions in this area:
• "Bypass" (only with PIDConL, PIDConR, and PIDStepL)
• "Simulation"
• "Release for maintenance" (with display for a maintenance request)
Refer to the Switching operating states and operating modes (Page 294) section for more on
this.
You can find information on this area in the section:
• Bypassing signals (Page 117) (for PIDConL, PIDConR, and PIDStepL)
• Simulating signals (Page 66)
• Release for maintenance (Page 72)
(2) "Settings"
You can activate the following functions for the controller in this area:
• "SP := PV in manual mode": ☑ Bumpless switchover from manual mode to automatic mode
• "SP := SP external": ☑ Bumpless switchover of the setpoint for setpoint switchover from
"external" to "internal" The internal setpoint is tracked to the external one.
(3) "Parameters"
In this area, you change parameters and therefore influence the controller. Refer to
the Changing values (Page 296) section for more on this.
You can influence the following parameters:
• "Gain": Proportional gain
• "Integral time" Integral action time in [s]
• "Derivative time TD": Derivative action time in [s]
• "Derivative gain": Gain of the derivative action
• "Dead band": Width of dead band
• "Control zone": Width of the control zone (for block FmTemp only)
• "Motor actuating time": Motor actuating time [s]
• "Minimum pulse duration": Minimum pulse duration [s]
• "Minimum break duration": Minimum break duration [s]
(4) "Service"
You can activate the following functions in this area:
• "Simulation"
• "Release for maintenance" (with display for a maintenance request)
Refer to the Switching operating states and operating modes (Page 294) section for more on
this.
You can find information on this area in the section:
• Simulating signals (Page 66)
• Release for maintenance (Page 72)
Parameter view for MotL, MotRevL, MotS, MotSpdL, VlvL and VlvS with Feature.Bit13 = 0.
Parameter view for MotL, MotRevL, MotS, MotSpdL, VlvL and VlvS with Feature.Bit13 = 1.
(2) "Monitoring"
In this area, you change parameters and therefore influence the motor. Refer to the Changing
values (Page 296) section for more on this.
You can influence the following parameters:
• "Control": Monitoring time during startup and shutdown of the motor (dynamic)
• "Control stop": Monitoring time during shutdown of the motor (dynamic)
only for MotL, MotRevL, MotSpdL and MotS with Feature.Bit13 = 1
• "Control start": Monitoring time during startup of the motor (dynamic)
only for MotL, MotRevL, MotSpdL and MotS with Feature.Bit13 = 1
"End position": Monitoring time during permanent operation of the motor (static)
• "Status": Monitoring time during permanent operation of the motor (static)
The state is not displayed for small blocks.
Enabling "Monitoring"
You can enable monitoring by selecting the check box (☑)
You can find additional information on this in the section Monitoring the feedbacks (Page 106).
(3) "Service"
You can select the following functions in this area:
• "Simulation"
• "Release for maintenance" (with display for a maintenance request)
Refer to the Switching operating states and operating modes (Page 294) section for more on
this.
You can find information on this area in the section:
• Simulating signals (Page 66)
• Release for maintenance (Page 72)
See also
Description of VlvS (Page 1740)
Note
The symbols displayed are not valid for user-configured message classes. Take into consideration
the validity of terms for User-configured message classes (Page 47)
Note
The symbols displayed are not valid for user-configured message classes. Take into consideration
the validity of terms for User-configured message classes (Page 47).
Note
The symbols displayed are not valid for user-configured message classes. Take into consideration
the validity of terms for User-configured message classes (Page 47).
(1) High and low scale range for the additional value
These values provide information on the display range for the bar graph of the additional value.
The scale range is defined in the engineering system.
You can find additional information about this in the Bar graph (Page 381) section.
Preview of FM controllers
The preview shows you the parameters that you, as an OS operator, can control in the entire
block. You cannot control anything in this view, however.
• "Tracking value": Effective manipulated variable for "Track manipulated variable at block"
• "Safety mode": safety mode in the FM module (value is 1)
• "Safety value": effective manipulated variable for "Safety mode"
(3) Navigation button for switching to the standard view of any faceplate
Use this navigation button to reach the standard view of a block configured in the engineering
system. The visibility of this navigation button depends on the configuration in the engineering
system (ES).
See also the Opening additional faceplates (Page 238) section for more on this.
Ramp view
If there is a difference between the target manipulated variable and the currently effective
manipulated variable, an orange "G" may be displayed at the bar in the standard view of VlvAnl
with parameter assignment of MV_RateTarget (target manipulated variable for gradient
limit).
The gradient limitation includes the Ramp function (Page 133). You can set the ramp mode in
the following two ways:
• Gradient
• Duration [s]
Message view
(1) Toolbar
If the short-term archive list is selected, a new button appears in the toolbar:
You can use this button to toggle between the "History" and "Operator messages" views.
You must be registered with the "Higher process control" operating permission in order to export
and hide messages.
(2) Display area for alarms
For additional information about the alarm view, refer to the WinCC Information System Online
Help.
(3) "Hide messages" button
Messages can be displayed and/or hidden with this button. The view of this button changes
accordingly:
Show messages
Hide messages
"Higher process controlling" operating permission is required and manual hiding must be active.
You can find additional information in the manual "Process Control System PCS 7 Operator
Station".
Batch view
This area shows a display of the batch that is currently running (Batchview).
You can use the internal tag "@APLBatchEnable" to enable/disable the "Batch" button in the
toolbar.
Value of @APLBatchEnable Operating the "Batch" button in Icon of the "Batch" button in the
the toolbar toolbar
0 Disabled
1 Enabled
(1) "Enabled"
This area shows you if the block is enabled for operation via SIMATIC BATCH (BatchEn = 1).
(2) "Allocated"
This area shows if the block is currently in use by SIMATIC BATCH (Occupied = 1).
Memo view
You can leave temporary messages for other OS operators in this view. Messages are entered in
the text box, and saved and activated by selecting the check box in the lower right corner of the
faceplate.
Note
• Files that are configured for NoteVew should be saved with UTF-8 encoding. This is applicable
to all the intermediate files also, before they are converted to .mht files.
• Jump instruction within the file in NoteView window will not work in the OS Client, Web
Server and Web Client.
• No permission levels are required for combo box and open button in the APL_Memo.PDL.
• Document - internal skip marks are not supported.
(1) Window Title: indicates the title of Window and name of the file opened as well.
(2) Indicates the loading status of the selected MHT document
(3) NoteView display area: displays content of the selected file.
Advised maximum size of the file is <= 25 MB for a smooth operation.
Note
• This window cannot be resized but it is movable.
• This window is not supported by the "screen composition" functionality.
All the .mht files (NoteView documents) should be placed in the "OS project path\Gracs
\NoteView". In case of a Multiproject, standard server(SSM) holds all .mht files and these files are
not available in the client. If SSM is not configured then files should be placed in local project
folder of client
Error Handling
• If selected file is not found in the folder path, an error message is shown as “File not found”.
• If configured file format is other than .mht, an error message is shown as "Invalid file format".
• If selected file is more than 25 MB and if tried to open same, an error is shown as “File size
exceeds 25 MB”.
• If file name length exceeds 32 characters, an error is shown as "File name length exceeded
32 characters".
The next time the faceplate is opened or there is a process picture change, you can see in the
status bar of the block icon and the faceplate that there is a new message for you.
Clearing the check box deletes the indicators in the status bars.
The message is not deleted automatically.
Trend view
(1) Toolbar
(2) Display area for trends
(3) Status bar
(4) Button for switching between archive tags and online tags. The status bar shows if the trend
view is working with online data or archive data.
(5) Button for opening the "Scatter plot" window
(6) Button for “Automatic scaling”: This button enables automatic calculation of the range of
values. This change is temporary and will revert to original setting when the view is changed, or
the faceplate is reopened.
The Export button is only visible and operable with the "Higher-level process control" operating
permission.
For additional information about the trend view, refer to the WinCC Information System Online
Help.
2. Simple display:
Display area consisting of two coordinate systems:
• Setpoint trend, actual value trend;
• Manipulated variable;
If you want to use the simple display, you need to enter the following in the block icon under
Trends in the WinCC Graphics Designer:
TrendPictureName =@pg_apl_trendPID.pdl
Note
Alarms for the device specific view can be displayed in message view of the block but there will
not be any indication in the overview or block icon.
Configuration:
• To create an additional view, a new picture must be created in the GraCS project directory
with the file name @PG_xxx_AddOn.pdl. Where xxx denotes "Blocktype" of the AddOn view.
For example, @PG_MyType_AddOn.pdl can be used for displaying an additional view of the
"Mytype" block.
• In the CFC, connect the input AddOn of the APL block with any output of the block whose
additional view is to be displayed.
After compiling and loading the OS and AS, the additional view in the APL faceplate is available.
Following are the blocks that support additional view:
Note
For the Web Navigator, when a new value is added, the Trend Control always displays only the
online value. You can switch to display the archived values through the buttons "Monday",
"Tuesday", and so on.
For information on adding additional values to the AOTC window, refer to (10) Adding
additional values.
Family Blocks
Drives MotL, MotRevL, MotSpdCL, MotSpdL, MotS, VlvL, VlvS, Vlv2WayL, VlvAnL, VlvMotL,
VlvPosL
Operate OpDi01, OpTrig, OpDi03
Monitor MonDiL, MonDiS, MonDi08
Example: If you perform Ctrl key + left-click operation on the MotL block icon, the AOTC window
opens showing its current status taken from the parameter FbkRunOut.Value. After opening
the AOTC window, if you perform Ctrl key + left-click operation on any other block then the
parameter corresponding to that block is added to the AOTC window.
For information on adding additional values to the AOTC window, refer to (10) Adding
additional values.
1. Title
2. Trend group description
3. Tag row
4. Time range selection
5. WinCC online trend control
6. Value axis
7. Toolbar of the trend window
8. Enabling/disabling a trend
9. Opening a faceplate
10.Adding additional values
11.Block comment
12.Enabling/disabling a value axis
13.Saving a trend group
14.Opening a separate message window
15.Printing screenshot of the AOTC window
16.Help button
17.Deleting a trend
18.Closing the AOTC window
(1) Title
The title displays the name of the AOTC. If the trend group is not saved, the default title "APL
Operator Trend Control" is displayed. If a saved trend group is opened, title displays the group
name.
• "High limit":
This field displays the high limit of the trend. The high limit is taken from the tag
"XX_OpScale#High". If the tag is not present, the value is taken automatically by the Trend
Control and the high limit field displays "Auto".
• "Ruler value":
This field displays the ruler value of the trend where the ruler intersects with the trend in the
Trend Control.
• "Ruler time":
This field displays the ruler time of the trend where the ruler intersects with the trend in the
Trend Control.
• Button to delete the trend:
Click this button to delete the trend. For more information, refer to the description of (15)
Deleting a trend.
7LPHUDQJHVHWWRPLQ
Perform the following steps to configure additional values to the AOTC window:
1. Click the [+] button which is available in the right corner of a configured parameter. The
"Additional Values" window opens which displays a list of parameters of the corresponding
function block.
2. Select a value from the list and click OK to configure the selected value in the AOTC window.
Note
• You can select only one value at a time. Multiple selections are disabled.
• Additional value buttons are visible only if the number of trends configured is less than the
maximum number of trends allowed (8 values).
• Additional value buttons will be disabled if the configured values in the AOTC reaches its
maximum allowed limit.
• Unit of the parameter added from the "Additional Values" window will not be displayed.
The AOTC full screen display is used to display configured trend groups on a dedicated screen.
The AOTC full screen window has four quadrants which means you can display four different
trend groups at a time. This window is termed as “Quad trend window” or “Full screen display”.
Perform the following steps to display the trend groups in "Full screen display":
1. Click the AOTC full screen display button at the bottom of the WinCC runtime window.
The AOTC full screen display opens with four empty quadrants and with four buttons at the
bottom to select a saved trend group for each quadrant.
2. Click the "(open trend group)" button at the bottom of the AOTC full screen display for the
quadrant in which you want to display a particular trend group. A window opens with a list
of saved trend groups.
3. Select a trend group from the list and click "Display" to load the trend group into the
corresponding quadrant.
4. Use all four buttons to load four different trend groups into the different quadrants of the full
screen display.
In the online mode, only the actual messages (all active messages, acknowledged and
unacknowledged) will be displayed.
If you select a time range displaying values from the archive, the message window will display
all the messages within this time range.
Messages only from the enabled trend will be displayed. If a trend is enabled or disabled and the
message window is open, the corresponding messages will be displayed or not displayed
accordingly. Similarly if a trend is deleted, the corresponding messages will disappear from the
messages window.
If two or more trends of the same block type are added to the AOTC window, and one of them
is disabled, the corresponding messages will not be removed from message window. All the
trends should be disabled or deleted to remove the corresponding messages from the message
window.
Only one message window can be opened at a time. If one more AOTC window is opened and
you want to display the messages for the values in that window, the already opened message
view should be closed and opened again from the specific AOTC window.
Operator permissions
The operator permissions are similar to the existing online trend function.
The following fields are enabled only if the area authorization is available:
1. Delete buttons to delete trends.
2. Save button to open the pop-up window to save the trend group.
Note
The functions for example, disable/enable trend, disable/enable value axis, delete trend, open
message window, print AOTC screenshot, select private trend group, need no operation area or
quitting function. The feature "Save Trend Group" needs an operation area where only 3 step
operation is possible. It does not support 2 step operation.
Symbol Meaning
Alarm
Warning
Tolerance
Note
The text displayed at the labels for the limit fields in limit view depends on the setting of the PCS
7 message system.
If the “User-configured message classes (Page 47)” is activated then the displayed text is taken
from the “TextOp” property of the limit object else it is taken from property “AnaText”
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Type block icons
index tion paren‐ (RGB) name ute name]
cy
200 1 0 B6B6B6 Gray Background: Back‐ BackgroundColor Block icons with
ground color analog values
201 1 0 DADADA Very light Background: Fill pattern BackgroundFillPattern‐ Block icons with
gray color Color analog values
202 1 0 B6B6B6 Gray Tag display: Background TagBackColor All block icons with
color tag display
203 1 0 DADADA Very light Tag display: Fill pattern TagFillColor All block icons with
gray color tag display
204 1 0 919191 Dark gray Tag display: Border col‐ TagBorderColor All block icons with
or tag display
205 1 0 000000 Black Tag display: Font color TagFontColor All block icons with
tag display
206 1 0 00FFFA Pure cyan Tag highlight: Back‐ BlockIconHighlight‐ All block icons
ground color BackColor
207 1 0 5CC2BC Medium cy‐ Tag highlight: Fill pat‐ BlockIconHighlightFill‐ All block icons
an tern color Color
208 1 0 FFFFFF White Tag highlight: Font col‐ BlockIconHighlight‐ All block icons
or FontColor
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Type block icons
index tion paren‐ (RGB) name ute name]
cy
209 1 0 B6B6B6 Gray Display of high limit: LimitObjectHighBack‐ Block icons with
Background color Color display of the high
limit
210 1 0 DADADA Very light Display of high limit: Fill LimitObjectHighFill‐ Block icons with
gray pattern color Color display of the high
limit
211 1 0 B6B6B6 Gray Display of the low limit: LimitObjectLowBack‐ Block icons with
Background color Color display of the low
limit
212 1 0 DADADA Very light Display of the low limit: LimitObjectLowFillCol‐ Block icons with
gray Fill pattern color or display of the low
limit
213 1 0 B6B6B6 Gray Empty rectangle: Back‐ EmptyRectBackColor"1 Block icons with
ground color status bar
214 1 0 DADADA Very light Empty rectangle: Fill EmptyRectFillColor1 Block icons with
gray pattern color status bar
215 1 0 808080 Dark gray Empty rectangle: Bor‐ EmptyRectBorderCol‐ Block icons with
der color or1 status bar
216 1 0 FFFFFF White Process value: Back‐ Value1BackColorVal‐ Block icons with
ground color ue10BackColor analog value
217 1 0 000000 Black Process value: Font col‐ Value1FontColorVal‐ Block icons with
or ue10FontColor analog value
218 1 100 C0C0C0 None Setpoint: Background Value2BackColor Block icons with
(transpar‐ color analog value
ent)
219 1 0 0000FF Pure blue Setpoint: Font color Value2FontColor Block icons with
analog value
220 2 100 C0C0C0 None Changed variable: Back‐ Value3BackColor Block icons with
(transpar‐ ground color analog value
ent)
221 2 0 F24F00 Pure orange Changed variable: Font Value3FontColor Block icons with
color analog value
222 2 100 C0C0C0 None Read-back value: Back‐ Value3BackColor Val‐ Block icons with
(transpar‐ ground color ue4BackColor analog value
ent)
223 2 0 008080 Dark cyan Read-back value: Font Value3FontColor Val‐ Block icons with
color ue4FontColor analog value
224 2 100 B6B6B6 None Unit2, process value/ UnitBackColor, Block icons with
(transpar‐ setpoint: Background Unit1BackColor- analog value
ent) color Unit4BackColor
225 2 0 494949 Very dark Unit, process value/ UnitFontColor, Block icons with
gray setpoint: Font color Unit1FontColor- analog value
Unit4FontColor
226 2 100 B6B6B6 None Unit2, changed variable: Unit2BackColor Block icons with
(transpar‐ Background color analog value
ent)
227 2 0 494949 Very dark Unit, changed variable: Unit2FontColor Block icons with
gray Font color analog value
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Type block icons
index tion paren‐ (RGB) name ute name]
cy
228 2 100 B6B6B6 None Unit2, read-back value: Unit1BackColor, Block icons with
(transpar‐ Background color Unit2BackColor analog value
ent)
229 2 0 494949 Very dark Unit, read-back value: Unit1FontColor, Block icons with
gray Font color Unit2FontColor analog value
230 2 0 6D6D6D Very dark "Not used" state: back‐ BackColorOn1 Interlock
gray ground color
231 2 0 919191 Dark gray "Not used" state: fill pat‐ FillColorOn1 Interlock
tern color
232 2 0 0000FF Pure blue "Bypassed" state: back‐ BackColorOn2 Interlock
ground color
233 2 0 00A2E8 Pure blue "Bypassed" state: fill pat‐ FillColorOn2 Interlock
tern color
234 2 0 E4D400 Pure yellow "Simulation" state: back‐ BackColorOn3 Interlock
ground color
235 2 0 FFFF00 Pure yellow "Simulation" state: fill FillColorOn3 Interlock
pattern color
236 2 0 00B500 Bright lime "Unlocked" state: back‐ BackColorOn4 Interlock
green ground color
237 2 0 00FF00 Pure lime "Unlocked" state: fill pat‐ FillColorOn4 Interlock
green tern color
238 2 0 E60000 Pure red "Locked" state: back‐ BackColorOn5 Interlock
ground color
239 2 0 FF0000 Pure red "Locked" state: fill pat‐ FillColorOn5 Interlock
tern color
240 3 0 00B500 Bright lime "On" state: Background BackColorOn, OnBack‐ Family counter /
green color Color MonDi08/ MonDiL‐
MonDiS (type 1
and 4) / OpDi03 /
ShrdResS/ Time‐
Trig/ TotalL
241 3 0 00FF00 Pure lime "On" state: Fill pattern FillColorOn, OnFillCol‐
green color or
242 3 0 00FF00 Pure lime "On" state: Background Value2BackColor OpDi01, OpTrig
green color
243 3 0 000000 Black "On" state: Font color Value2FontColor OpDi01, OpTrig
244 3 0 FFFFFF White "On" state: Background Value2BackColor MonDiL-MonDiS
color (types 2, 3 and 5)
245 3 0 000000 Black "On" state: Font color Value2FontColor MonDiL-MonDiS
(types 2, 3 and 5)
246 3 0 FFFFFF White "On" state: Font color FontColorOn MonDiL-MonDiS
(type 4)
247 3 0 B6B6B6 Gray "Off" state: Background BackColorOff, BackCo‐
color lorOn
248 3 0 DADADA Very light "Off" state: Fill pattern FillColorOff, FillColor‐
gray color On
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Type block icons
index tion paren‐ (RGB) name ute name]
cy
249 3 0 DADADA Very light "Off" state: Background BackColorOff Family counter,
gray color MonDi08, TimeTrig
250 3 0 FFFFFF White "Off" state: Fill pattern FillColorOff Family counter,
color MonDi08, TimeTrig
251 3 0 FFFFFF White "Off" state: Background Value1BackColor MonDiLMonDiS
color (types 2, 3 and 5)
252 3 0 000000 Black "Off" state: Font color Value1FontColor MonDiLMonDiS
(types 2, 3 and 5)
253 3 0 000000 Black "Off" state: Font color FontColorOff MonDiLMonDiS
(type 4)
254 3 0 B6B6B6 Gray "Not used" state: Back‐ BackColorNA MonDi08
ground color
255 3 0 000000 Black "No operation" state: ForeColorValue OpStations
Font color
256 3 0 C0C0C0 Light gray Display of the selected Value2BackColor SelA16In
analog value: Back‐
ground color
257 3 0 6D6D6D Very dark Display of the selected Value2FontColor SelA16In
gray analog value: Font color
258 3 0 494949 Very dark ISO/DIN symbols: Line BorderColor
gray color
1
New property
2
Note: The pattern in the block icon must be changed to "single color" for the color to take effect.
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Types views/
index tion paren‐ (RGB) name ute name] objects
cy
259 3 0 AFAFAF Gray View: Background color BackColor Views in all face‐
plates
260 4 0 DEDEDE Very light View: Fill pattern color FillColor Views in all face‐
gray plates
261 4 0 62ACAA Dark cyan Operating area: Back‐ BackColor Total operating
ground color area
262 4 0 AACFCD Gray cyan Operating area: Fill pat‐ FillColor Total operating
tern color area
263 4 0 000000 Black Title or label of operat‐ ForeColor All static texts in
ing area: Font color the operating area
264 4 0 C0C0C0 Light gray Slider operating area: BackColor, BackColor‐ Operating area
Background color Top, BackColorBottom, "@PG_APL_OA_An‐
ButtonColor, HighLi‐ alogwithli‐
mitColor, LowLimitCol‐ mits100.PDL"
or
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Types views/
index tion paren‐ (RGB) name ute name] objects
cy
265 4 0 FFFFFF White Slider operating area: BorderBackColor Operating area
Border background col‐ "@PG_APL_OA_An‐
or alogwithli‐
mits100.PDL"
266 4 0 000000 Black Slider operating area: BorderColor Operating area
Border color "@PG_APL_OA_An‐
alogwithli‐
mits100.PDL"
267 4 0 DADADA Very light Block comment: Fill pat‐ FillColor Header in all face‐
gray tern color plates
268 4 0 808080 Dark gray Block comment: Border BorderColor Header in all face‐
color plates
269 4 0 000000 Black Block comment: Font FontColor Header in all face‐
color plates
270 4 0 B6B6B6 Gray Empty rectangle over‐ BackColor Header in all face‐
view: Background color plates
271 4 0 DADADA Very light Empty rectangle over‐ FillColor Header in all face‐
gray view: Fill pattern color plates
272 4 0 808080 Dark gray Empty rectangle over‐ BorderColor Header in all face‐
view: Border color plates
273 4 0 C0C0C0 Light gray Group display overview: BackColor Header in all face‐
Background color plates [1]
274 4 0 C0C0C0 Light gray Toolbar button: Back‐ BackColor Header in all face‐
ground color plates
275 4 0 BABABA Gray Toolbar button: Fill pat‐ FillColor Header in all face‐
tern color plates
276 4 0 808080 Dark gray Toolbar button: Border BorderColor Header in all face‐
color plates
277 4 0 000000 Black Toolbar button: Font FontColor Header in all face‐
color plates [2]
278 4 0 C0C0C0 Light gray Header button[3]: Back‐ BackColor Header in all face‐
ground color plates
279 4 0 808080 Dark gray Toolbar button: Border BorderColor 8 Header in all face‐
color plates
280 5 0 000000 Black Title or label in views: TextFontColor, Font‐ Views with static
Font color Color, ForeColor, Left‐ text and APL ob‐
HandTextFontColor[4] jects with type
ID=17-20, 22-24,
27, 29, 64, 120,
130
281 5 0 AFAFAF Gray Button in views/operat‐ BackColor Views with APL ob‐
ing areas: Background jects with type
color ID=30-34, 50-52
282 5 0 CECECE Light gray Button in views/operat‐ FillColor Views with APL ob‐
ing areas: Fill pattern jects with type
color ID=30-34, 50-52
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Types views/
index tion paren‐ (RGB) name ute name] objects
cy
283 5 0 808080 Dark gray Button in views/operat‐ BorderColor Views with APL ob‐
ing areas: Border color jects with type
ID=30-34, 50-52
284 5 0 FFFFFF White Button in views/operat‐ BorderColorTop Views with APL ob‐
ing areas: 3D border col‐ jects with type
or ID=30-34, 50-52
285 5 0 808080 Dark gray Button in views/operat‐ BorderColorBottom Views with APL ob‐
ing areas: 3D shadow jects with type
color ID=30-34, 50-52
286 5 0 000000 Black Button in views/operat‐ ForeColor Views with APL ob‐
ing areas: Font color jects with type
ID=30-34, 50-52
287 5 0 DADADA Very light Analog value enabled in EnabledBackColor, Views with I/O
gray views/operating areas: BackColor, BackCol‐ fields (also exten‐
Background color or_OK ded) and APL ob‐
jects with type
ID=20, 22-24, 27,
28-29, 130
288 5 0 FFFFFF White Analog value enabled in EnabledFillColor, Fill‐ Views with I/O
views/operating areas: Color, FillColor_OK fields (also exten‐
Fill pattern color ded) and APL ob‐
jects with type
ID=20, 22-24, 27,
28-29, 130
289 5 0 B6B6B6 Gray Analog value disabled DisabledBackColor, Views with I/O
in views/operating BackColor, BackCol‐ fields (also exten‐
areas: Background color or_OK ded) and APL ob‐
jects with type
ID=20, 22-24, 27,
28-29, 91¹³,92,130
290 5 0 DADADA Very light Analog value disabled DisabledFillColor, Fill‐ Views with I/O
gray in views/operating Color, FillColor_OK fields (also exten‐
areas: Fill pattern color ded) and APL ob‐
jects with type
ID=20, 22-24, 27,
28-29, 91¹³,92,130
291 5 0 000000 Black Analog value or unit in ValueFontColor, Fore‐ Views with I/O
views/operating areas: Color, ForeColor_OK fields (also exten‐
Font color ded) and APL ob‐
jects with type
ID=16, 20, 22-24,
27, 28-29, 91, 130
292 5 0 00B500 Bright lime Analog process value: LineColor, BorderColor Views with I/O
green Border color fields (also exten‐
ded) and APL ob‐
jects with type
ID=20, 24
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Types views/
index tion paren‐ (RGB) name ute name] objects
cy
293 5 0 0000FF Pure blue Analog setpoint: Border LineColor, BorderColor Views with I/O
color fields (also exten‐
ded) and APL ob‐
jects with type
ID=20, 28
294 5 0 D27A00 Bright or‐ Changed analog varia‐ LineColor, BorderColor Views with I/O
ange ble: Border color fields (also exten‐
ded) and APL ob‐
jects with type
ID=20, 24, 28
295 5 0 008582 Dark cyan Analog read-back value: LineColor, BorderColor Views with I/O
Border color fields (also exten‐
ded) and APL ob‐
jects with type
ID=20
296 5 0 808080 Dark gray Analog parameter/ LineColor, BorderColor Views with I/O
range value: border col‐ fields (also exten‐
or ded) and APL ob‐
jects with type
ID=20, 22-24, 27,
28, 90, 92, 130
297 5 0 000000 Black Analog limit (no alarm), LineColor, BorderColor In
input value, offset, gra‐ "@PG_CntOhSc_Li
dient: border color mit.PDL",
"@PG_Mo‐
nAnL_Stand‐
ard.PDL", "@PG_Ra‐
tio_Standard.PDL",
"@PG_To‐
talL_Stand‐
ard.PDL" APL ob‐
jects with type
ID=20, 24, 28, 29
and HMIStaticText
298 5 0 808080 Dark gray Empty analog value dis‐ BorderColor Views with APL ob‐
plays jects with type
ID=21, 25, 26
299 5 0 00B500 Bright lime Binary value on: Back‐ OnBackColor, Views with APL ob‐
green ground color State1BackColor jects with type
ID=17,18¹³,120
300 6 0 00FF00 Pure lime Binary value on: Fill pat‐ OnFillColor, State1Fill‐ Views with APL ob‐
green tern color Color jects with type
ID=17,18¹³,120
301 6 0 FFFFFF White Binary value on: Font OnFontColor, Views with APL ob‐
color State1FontColor jects with type
ID=17,18¹³,120
302 6 0 FFFFFF White Binary value off: Back‐ OffBackColor, Views with APL ob‐
ground color State2BackColor jects with type
ID=17,18¹³,120
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Types views/
index tion paren‐ (RGB) name ute name] objects
cy
303 6 0 DADADA Very light Binary value off: Fill pat‐ OffFillColor, State2Fill‐ Views with APL ob‐
gray tern color Color jects with type
ID=17,18¹³,120
304 6 0 000000 Black Binary value off: Font OffFontColor, Views with APL ob‐
color State2FontColor jects with type
ID=17,18¹³,120
305 6 0 808080 Dark gray Binary value: Border col‐ BorderColor Views with APL ob‐
or jects with type
ID=17,18¹³,120
306 6 0 B6B6B6 Gray Binary value preview: BackColor Preview, APL ob‐
Background color jects with type
ID=14
307 6 0 DADADA Very light Binary value preview: FillColor Preview, APL ob‐
gray Fill pattern color jects with type
ID=14
308 6 0 000000 Black Binary value preview: FontColor Preview, APL ob‐
Font color jects with type
ID=14
309 6 0 808080 Dark gray Binary value preview: BorderColor Preview, APL ob‐
Border color jects with type
ID=14
310 6 0 00B500 Bright lime Status display "On" State1BackColor… Standard view, APL
green mode: background color State7BackColor objects with type
ID=11
311 6 0 00FF00 Pure lime Status display "On" State1FillColor… Standard view, APL
green mode: fill pattern color State7FillColor objects with type
ID=11
312 6 0 FFFFFF White Status display "On" State1FontColor… Standard view, APL
mode: font color State7FontColor objects with type
ID=11
313 6 0 FFFFFF White Status display "Manual" State1BackColor… Standard view, APL
mode: background color State7BackColor objects with type
ID=11
314 6 0 CECECE Light gray Status display "Manual" State1FillColor… Standard view, APL
mode: fill pattern color State7FillColor objects with type
ID=11
315 6 0 000000 Black Status display "Manual" State1FontColor… Standard view, APL
mode: font color State7FontColor objects with type
ID=11
316 6 0 00FF00 Pure lime Status display "Automat‐ State1BackColor… Standard view, APL
green ic" mode: background State7BackColor objects with type
color ID=11
317 6 0 008500 Dark lime Status display "Automat‐ State1FillColor… Standard view, APL
green ic" mode: fill pattern col‐ State7FillColor objects with type
or ID=11
318 6 0 FFFFFF White Status display "Automat‐ State1FontColor… Standard view, APL
ic" mode: font color State7FontColor objects with type
ID=11
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Types views/
index tion paren‐ (RGB) name ute name] objects
cy
319 6 0 00CECA Bright cyan Status display "Local" State1BackColor… Standard view, APL
mode: background color State7BackColor objects with type
ID=11
320 7 0 00FFFA Pure cyan Status display "Local" State1FillColor… Standard view, APL
mode: fill pattern color State7FillColor objects with type
ID=11
321 7 0 000000 Black Status display "Local" State1FontColor… Standard view, APL
mode: font color State7FontColor objects with type
ID=11
322 7 0 0000FF Pure blue Status display "Pro‐ State1BackColor… Standard view, APL
gramm MV/SP" mode: State7BackColor objects with type
background color ID=11
323 7 0 98BDFF Very light Status display "Pro‐ State1FillColor… Standard view, APL
blue gramm MV/SP" mode: State7FillColor objects with type
fill pattern color ID=11
324 7 0 FFFFFF White Status display "Pro‐ State1FontColor… Standard view, APL
gramm MV/SP" mode: State7FontColor objects with type
font color ID=11
325 7 0 919191 Dark gray Status display "Out of State1BackColor… Standard view, APL
service" mode: back‐ State7BackColor objects with type
ground color ID=11
326 7 0 CECECE Light gray Status display "Out of State1FillColor… Standard view, APL
service" mode: fill pat‐ State7FillColor objects with type
tern color ID=11
327 7 0 000000 Black Status display "Out of State1FontColor… Standard view, APL
service" mode: font col‐ State7FontColor objects with type
or ID=11
328 7 0 808080 Dark gray Status display operating BorderColor Standard view, APL
mode: Border color objects with type
ID=11
329 7 0 FFFFFF White Status display control State1BackColor… Mostly standard/
command State7BackColor parameter view/
"Stop"/"Close"/"Off"/"Pau preview, APL ob‐
se"/"Cancel"/"Reques‐ jects with type
ted"/"No": background ID=10, 11, 15
color
330 7 0 DADADA Very light Status display control State1FillColor… Mostly standard/
gray command State7FillColor parameter view/
"Stop"/"Close"/"Off"/"Pau preview, APL ob‐
se"/"Cancel"/"Reques‐ jects with type
ted"/"No": fill pattern col‐ ID=10, 11, 15
or
331 7 0 000000 Black Status display control State1FontColor… Mostly standard/
command State7FontColor parameter view/
"Stop"/"Close"/"Off"/"Pau preview, APL ob‐
se"/"Cancel"/"Reques‐ jects with type
ted"/"No": font color ID=10, 11, 15
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Types views/
index tion paren‐ (RGB) name ute name] objects
cy
332 7 0 00B500 Bright lime Status display control State1BackColor… Mostly standard/
green command State7BackColor parameter view/
"Start"/"Open"/"On"/"Co preview, APL ob‐
ntinue"/"Ac‐ jects with type
tive"/"ready"/"Yes": back‐ ID=10, 11, 15, 19
ground color
333 7 0 00FF00 Pure lime Status display control State1FillColor… Mostly standard/
green command State7FillColor parameter view/
"Start"/"Open"/"On"/"Co preview, APL ob‐
ntinue"/"Ac‐ jects with type
tive"/"ready"/"Yes": fill ID=10, 11, 15, 19
pattern color
334 7 0 FFFFFF White Status display control State1FontColor… Mostly standard/
command State7FontColor parameter view/
"Start"/"Open"/"On"/"Co preview, APL ob‐
ntinue"/"Ac‐ jects with type
tive"/"ready"/"Yes": font ID=10, 11, 15, 19
color
335 7 0 FF0000 Pure red Status display control State1BackColor… Standard view, APL
command "Rapid stop": State7BackColor objects with type
background color ID=10, 15
336 7 0 FF8296 Very light Status display control State1FillColor… Standard view, APL
red command "Rapid stop": State7FillColor objects with type
fill pattern color ID=10, 15
337 7 0 000000 Black Status display control State1FontColor… Standard view, APL
command "Rapid stop": State7FontColor objects with type
font color ID=10, 15
338 7 0 FFFFFF White Status display control State1BackColor… Standard view, APL
command "Internal": State7BackColor objects with type
background color ID=11
339 7 0 CECECE Light gray Status display control State1FillColor… Standard view, APL
command "Internal": fill State7FillColor objects with type
pattern color ID=11
340 8 0 000000 Black Status display control State1FontColor… Standard view, APL
command "Internal": State7FontColor objects with type
font color ID=11
341 8 0 0000FF Pure blue Status display control State1BackColor… Standard view, APL
command "External": State7BackColor objects with type
background color ID=10, 11, 15
342 8 0 98BDFF Very light Status display control State1FillColor… Standard view, APL
blue command "External": fill State7FillColor objects with type
pattern color ID=10, 11, 15
343 8 0 FFFFFF White Status display control State1FontColor… Standard view, APL
command "External": State7FontColor objects with type
font color ID=10, 11, 15
344 8 0 808080 Dark gray Status display control BorderColor Standard view, APL
command: Border color objects with type
ID=10, 11, 15
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Types views/
index tion paren‐ (RGB) name ute name] objects
cy
345 8 0 000000 Black Status display error BackColor, State1Back‐ Standard view,
("End position error", Color…State7BackCol‐ mostly APL objects
"Control error", "Invalid or with type ID=12
Signal", "Changeover er‐
ror", "Motor protection",
"Torque active", "Exter‐
nal error", "CPI invalid",
"Changeover error",
"Fluttering"): Back‐
ground color
346 8 0 919191 Dark gray Status display error FillColor, State1FillCol‐ Standard view,
("End position error", or… State7FillColor mostly APL objects
"Control error", "Invalid with type ID=12
Signal", "Changeover er‐
ror", "Motor protection",
"Torque active", "Exter‐
nal error", "CPI invalid",
"Changeover error",
"Fluttering"): Fill pattern
color
347 8 0 FFFF00 Pure yellow Status display error FontColor, State1Font‐ Standard view,
("End position error", Color…State7FontCol‐ mostly APL objects
"Control error", "Invalid or with type ID=12
Signal", "Changeover er‐
ror", "Motor protection",
"Torque active", "Exter‐
nal error", "CPI invalid",
"Changeover error",
"Fluttering"): Font color
348 8 0 919191 Dark gray Status display AS block BackColor, State1Back‐ Standard view,
state ("Forced", "Re‐ Color…State7BackCol‐ mostly APL objects
quest 0/1", "Tracking", or with type ID=12,
"Optimizing", "Output 13
…"[5], "Fuzzy...", "Safety
mode", "End", "Taring",
"Dribbling", "Paused",
"Off"[6], "… Trigger",
"Disabled", "SP/MV ramp
active"): Background
color
349 8 0 DADADA Very light Status display AS block FillColor, State1FillCol‐ Standard view,
gray state ("Forced", "Re‐ or… State7FillColor mostly APL objects
quest 0/1", "Tracking", with type ID=12,
"Optimizing", "Output 13
…"[7], "Fuzzy...", "Safety
mode", "End", "Taring",
"Dribbling", "Paused",
"Off"[8], "… Trigger",
"Disabled", "SP/MV ramp
active"): Fill pattern col‐
or
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Types views/
index tion paren‐ (RGB) name ute name] objects
cy
350 8 0 000000 Black Status display AS block FontColor, State1Font‐ Standard view,
state ("Forced", "Re‐ Color…State7FontCol‐ mostly APL objects
quest 0/1", "Tracking", or with type ID=12,
"Optimizing", "Output 13
…"[9], "Fuzzy...", "Safety
mode", "End", "Taring",
"Dribbling", "Paused",
"Off"[10], "… Trigger",
"Disabled", "SP/MV ramp
active"): Font color
351 8 0 FF0000 Pure red Status display alarm BackColor, State1Back‐ Standard view,
("Flow", "Underdosed", Color…State7BackCol‐ mostly APL objects
"Overdosed"): Back‐ or with type ID=12,
ground color 13
352 8 0 FFFFFF White Status display alarm FillColor, State1FillCol‐ Standard view,
("Flow", "Underdosed", or… State7FillColor mostly APL objects
"Overdosed"): Fill pat‐ with type ID=12,
tern color 13
353 8 0 000000 Black Status display alarm FontColor, State1Font‐ Standard view,
("Flow", "Underdosed", Color…State7FontCol‐ mostly APL objects
"Overdosed"): Font color or with type ID=12,
13
354 8 0 00B500 Dark lime Status display enabled BackColor, State1Back‐ Standard view,
green ("On"[11],"Enabled","… Color…State7BackCol‐ mostly APL objects
dosing"): Background or with type ID=12,
color 13, 15
355 8 0 00FF00 Pure lime Status display enabled FillColor, State1FillCol‐ Standard view,
green ("On"[12],"Enabled","… or… State7FillColor mostly APL objects
dosing"): Fill pattern col‐ with type ID=12,
or 13, 15
356 8 0 FFFFFF White Status display enabled FontColor, State1Font‐ Standard view,
("On"[13],"Enabled","… Color…State7FontCol‐ mostly APL objects
dosing"): Font color or with type ID=12,
13, 15
357 8 0 DADADA Very light Status display disabled BackColor, State1Back‐ Standard view,
gray ("Off"[14]): Background Color…State7BackCol‐ mostly APL objects
color or with type ID=12,
13, 15
358 8 0 FFFFFF White Status display disabled FillColor, State1FillCol‐ Standard view,
("Off"): Fill pattern color or… State7FillColor mostly APL objects
with type ID=12,
13, 15
359 8 0 000000 Black Status display disabled FontColor, State1Font‐ Standard view,
("Off"): Font color Color…State7FontCol‐ mostly APL objects
or with type ID=12,
13, 15
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Types views/
index tion paren‐ (RGB) name ute name] objects
cy
360 9 0 FFFA00 Pure yellow Status display impor‐ BackColor, State1Back‐ Standard/parame‐
tant AS block informa‐ Color…State7BackCol‐ ter view, mostly
tion ("Simulation", or APL objects with
"Process excitation", type ID=12, 13
"Time delay"): Back‐
ground color
361 9 0 FFFFFF White Status display impor‐ FillColor, State1FillCol‐ Standard/parame‐
tant AS block informa‐ or… State7FillColor ter view, mostly
tion ("Simulation", APL objects with
"Process excitation", type ID=12, 13
"Time delay"): Fill pat‐
tern color
362 9 0 000000 Black Status display impor‐ FontColor, State1Font‐ Standard/parame‐
tant AS block informa‐ Color…State7FontCol‐ ter view, mostly
tion ("Simulation", or APL objects with
"Process excitation", type ID=12, 13
"Time delay"): Font color
363 9 0 0000FF Pure blue Status display mainte‐ BackColor, State1Back‐ Standard view,
nance ("Maintenance"): Color…State7BackCol‐ mostly APL objects
Background color or with type ID=12,
13
364 9 0 96BBFF Very light Status display mainte‐ FillColor, State1FillCol‐ Standard view,
blue nance ("Maintenance"): or… State7FillColor mostly APL objects
Fill pattern color with type ID=12,
13
365 9 0 000000 Black Status display mainte‐ FontColor, State1Font‐ Standard view,
nance ("Maintenance"): Color…State7FontCol‐ mostly APL objects
Font color or with type ID=12,
13
366 9 0 808080 Dark gray Status display error, ..., BorderColor Standard view /
Maintenance: Border preview, mostly
color APL objects with
type ID=11-13, 15
367 9 0 DADADA Very light Interlock, display of in‐ BackColor Standard view in‐
gray put values (BOOL): terlock, APL ob‐
Background color jects with type
ID=100
368 9 0 CECECE Light gray Interlock, display of in‐ FillColor Standard view in‐
put values (BOOL): Fill terlock, APL ob‐
pattern color jects with type
ID=100
369 9 0 000000 Black Interlock, display of in‐ FontColor Standard view in‐
put values (BOOL): Font terlock, APL ob‐
color jects with type
ID=100
370 9 0 808080 Dark gray Interlock, display of in‐ BorderColor Standard view in‐
put values (BOOL): Bor‐ terlock, APL ob‐
der color jects with type
ID=100
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Types views/
index tion paren‐ (RGB) name ute name] objects
cy
371 9 0 919191 Dark gray Interlock, display of in‐ SeparatorBackColor Standard view in‐
put values (BOOL): terlock, APL ob‐
Background color sepa‐ jects with type
rator ID=100
372 9 0 00FF00 Pure lime Interlock, status "1" for SetBackColor Standard view in‐
green further processing: terlock, APL ob‐
Background color jects with type
ID=101
373 9 0 00B500 Dark lime Interlock, status "1" for SetFillColor Standard view in‐
green further processing: Fill terlock, APL ob‐
pattern color jects with type
ID=101
374 9 0 FFFFFF White Interlock, status "0" for ResetBackColor Standard view in‐
further processing: terlock, APL ob‐
Background color jects with type
ID=101
375 9 0 B6B6B6 Gray Interlock, status "0" for ResetFillColor Standard view in‐
further processing: Fill terlock, APL ob‐
pattern color jects with type
ID=101
376 9 0 0000FF Pure blue Interlock, status "By‐ BypassBackColor Standard view in‐
passed" (excluded) for terlock, APL ob‐
further processing: jects with type
Background color ID=101
377 9 0 00A2E8 Pure blue Interlock, status "By‐ BypassFillColor Standard view in‐
passed" (excluded) for terlock, APL ob‐
further processing: Fill jects with type
pattern color ID=101
378 9 0 FFFFFF White Interlock, status for fur‐ ForeColor Standard view in‐
ther processing: Font terlock, APL ob‐
color jects with type
ID=101
379 9 0 6D6D6D Very dark Interlock, status for fur‐ BorderColor Standard view in‐
gray ther processing: Border terlock, APL ob‐
color jects with type
ID=101
380 10 0 B6B6B6 Gray Interlock, "Not used" sta‐ Set5BackColor Standard view in‐
tus of the output signal terlock, APL ob‐
of the interlock block: jects with type
Background color ID=103
381 10 0 DADADA Very light Interlock, "Not used" sta‐ Set5FillColor Standard view in‐
gray tus of the output signal terlock, APL ob‐
of the interlock block: jects with type
Fill pattern color ID=103
382 10 0 0000FF Pure blue Interlock, "Not used" sta‐ Set4BackColor Standard view in‐
tus of the output signal terlock, APL ob‐
of the interlock block: jects with type
Background color ID=103
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Types views/
index tion paren‐ (RGB) name ute name] objects
cy
383 10 0 00A2E8 Pure blue Interlock, "Not used" sta‐ Set4FillColor Standard view in‐
tus of the output signal terlock, APL ob‐
of the interlock block: jects with type
Fill pattern color ID=103
384 10 0 E4D400 Pure yellow Interlock, "Simulation" Set2BackColor Standard view in‐
status of the output sig‐ terlock, APL ob‐
nal of the interlock jects with type
block: Background color ID=103
385 10 0 FFFF00 Pure yellow Interlock, "Simulation" Set2FillColor Standard view in‐
status of the output sig‐ terlock, APL ob‐
nal of the interlock jects with type
block: Fill pattern color ID=103
386 10 0 00B500 Bright lime Interlock, "Unlocked" Set1BackColor Standard view in‐
green status of the output sig‐ terlock, APL ob‐
nal of the interlock jects with type
block: Background color ID=103
387 10 0 00FF00 Pure lime Interlock, "Unlocked" Set1FillColor Standard view in‐
green status of the output sig‐ terlock, APL ob‐
nal of the interlock jects with type
block: Fill pattern color ID=103
388 10 0 E60000 Pure red Interlock, "Locked" sta‐ Set3BackColor Standard view in‐
tus of the output signal terlock, APL ob‐
of the interlock block: jects with type
Background color ID=103
389 10 0 FF0000 Pure red Interlock, "Locked" sta‐ Set3FillColor Standard view in‐
tus of the output signal terlock, APL ob‐
of the interlock block: jects with type
Fill pattern color ID=103
390 10 0 000000 Black Interlock, status of the ForeColor Standard view in‐
output signal of the in‐ terlock, APL ob‐
terlock block: Font color jects with type
ID=103
391 10 0 919191 Dark gray Interlock, status of the BorderColor Standard view in‐
output signal of the in‐ terlock, APL ob‐
terlock block: Border jects with type
color ID=103
392 10 0 850082 Dark ma‐ Interlock, "First signal" BackColor Standard view in‐
genta status display: Back‐ terlock, APL ob‐
ground color jects with type
ID=102
393 10 0 CD51FF Light purple Interlock, "First signal" FillColor Standard view in‐
status display: Fill pat‐ terlock, APL ob‐
tern color jects with type
ID=102
394 10 0 808080 Dark gray Interlock, "First signal" BorderColor Standard view in‐
status display: Border terlock, APL ob‐
color jects with type
ID=102
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Types views/
index tion paren‐ (RGB) name ute name] objects
cy
395 10 0 00B500 Bright lime Interlock, "Unlocked" OnStateColor Standard view in‐
green status of the block out‐ terlock, APL ob‐
put: Line color jects with type
ID=104
396 10 0 FFFFFF White Interlock, "Locked" sta‐ OffStateColor Standard view in‐
tus of the block output: terlock, APL ob‐
Line color jects with type
ID=104
397 10 0 B6B6B6 Gray Interlock, block rectan‐ BackgroundColor Standard view in‐
gle: Background color terlock, HMIRec‐
tangle
398 10 0 DADADA Very light Interlock, block rectan‐ FillPatternColor Standard view in‐
gray gle: Fill pattern color terlock, HMIRec‐
tangle
399 10 0 919191 Dark gray Interlock, block rectan‐ BorderColor Standard view in‐
gle: Border color terlock, HMIRec‐
tangle
400 11 0 00B500 Bright lime Bar chart, analog proc‐ ValueColor Standard/setpoint
green ess value: Background view, APL objects
color with type ID=71
401 11 0 00FF00 Pure lime Bar chart, analog proc‐ ValueFillColor Standard/setpoint
green ess value: Fill pattern view, APL objects
color with type ID=71
402 11 0 0000FF Pure blue Bar chart, analog set‐ ValueColor, FontColor Standard/setpoint
point: Background col‐ view, APL objects
or, foreground color with type ID=70,
80, 81
403 11 0 98BDFF Very light Bar chart, analog set‐ ValueFillColor Standard/setpoint
blue point: Fill pattern color view, APL objects
with type ID=70
404 11 0 D27A00 Bright or‐ Bar chart, changed ana‐ ValueColor, FontColor Standard view, APL
ange log variable: Back‐ objects with type
ground color, fore‐ ID=72, 82, 83
ground color
405 11 0 FFC848 Light or‐ Bar chart, changed ana‐ ValueFillColor Standard view, APL
ange log variable: Fill pattern objects with type
color ID=72
406 11 0 008582 Dark cyan Bar chart, analog read- ValueColor Standard view, APL
back value: Background objects with type
color ID=71, 73
407 11 0 00CECA Bright cyan Bar chart, analog read- ValueFillColor Standard view, APL
back value: Fill pattern objects with type
color ID=71, 73
408 11 0 008582 Dark cyan Bar chart, predicted val‐ ValueColor Standard view, APL
ue: Background color objects with type
ID=75
409 11 0 00CECA Bright cyan Bar chart, predicted val‐ ValueFillColor Standard view, APL
ue: Fill pattern color objects with type
ID=75
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Types views/
index tion paren‐ (RGB) name ute name] objects
cy
410 11 0 000000 Black Bar chart, message gra‐ ValueColor, AlarmCol‐ Standard view, APL
dient value or limit or, WarningColor objects with type
(without alarm): Back‐ ID=74 or 71[15]
ground color
411 11 0 6D6D6D Very dark Bar chart, gradient val‐ ValueFillColor Standard view, APL
gray ue: Fill pattern color objects with type
ID=74
412 11 0 808080 Dark gray Bar chart: Border color BorderColor Standard/setpoint
view, APL objects
with type ID=7075
413 11 0 62ACAA Mostly un‐ Selection rectangle op‐ BackgroundColor All views with oper‐
saturated eration: Background col‐ ation, HMIRectan‐
dark cyan or gle object name
"rect_selectionBor‐
der"
414 11 0 B1CFCD Gray cyan Selection rectangle op‐ FillColor All views with oper‐
eration: Fill pattern col‐ ation, HMIRectan‐
or gle object name
"rect_selectionBor‐
der"
415 11 0 808080 Dark gray Selection rectangle op‐ BorderColor All views with oper‐
eration: Border color ation, HMIRectan‐
gle object name
"rect_selectionBor‐
der"
416 11 0 808080 Dark gray Dividing line: Border col‐ BorderColor All views with di‐
or viding line, HMI‐
Line
[1] Note: Also types without messages have an empty group display
[2] Note: Only important for the "Next" button
[3] "Lock"/"Acknowledgement"/"Attach"/"Back to process picture" buttons; "Attach" button in the
operating area
[4] In the standard view Ratio
[5] Used in type ID = 17, 18, 120
[6] In the standard view DoseL
[7] In the standard view Ratio
[8] In the standard view DoseL
[9] In the standard view Ratio
[10] In the standard view DoseL
[11] In the standard view OpDi01, OpDi03, display the confirmation of the command
[12] In the standard view OpDi01, OpDi03, display the confirmation of the command
[13] Not used, only in @PCS7ElementsAPL.pdl
[14] In the standard view OpDi01, OpDi03, display the confirmation of the command
[15] In @PG_CntOhSc_Standard.PDL
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Type block icons
index tion paren‐ (RGB) name ute name]
cy
417 11 0 00CE00 Bright lime Actual value TrendColor1 - Trend‐ Trend view
green Color12
418 11 0 0000FF Pure blue Setpoint TrendColor1 - Trend‐ Trend view
Color12
419 11 0 E69100 Pure orange Changed variable TrendColor1 - Trend‐ Trend view
Color12
420 12 0 008582 Dark cyan Read-back value TrendColor1 - 1Trend‐ Trend view
Color12
421 12 0 00CE00 Bright lime Controller, closed loop TrendColor8 Trend view control‐
green ler
422 12 0 000000 Black Controller, input for con‐ TrendColor7 Trend view control‐
trol performance index ler
(CPI)
423 12 0 000000 Black Controller, binary mes‐ TrendColor3, TrendCol‐ Trend view control‐
sage "violated"1 or4, TrendColor9, ler
TrendColor10
424 12 0 B100B5 Bright ma‐ Controller, control per‐ TrendColor1 Trend view ConPer‐
genta formance index (CPI) Mon
425 12 0 E69100 Pure orange Ratio, analog input "In" TrendColor1 Trend view Ratio
426 12 0 00FF00 Pure lime Ratio, input for process TrendColor2 Trend view Ratio
green variable "InPV"
427 12 0 0000FF Pure blue Ratio, process value of TrendColor3 Trend view Ratio
the secondary compo‐
nent "SecComPV"
428 12 0 B100B5 Bright ma‐ Ratio, output "Out" TrendColor4 Trend view Ratio
genta
429 12 0 FF0000 Pure red Ratio, current ratio "Ra‐ TrendColor5 Trend view Ratio
tioPV"
430 12 0 6D6D6D Very dark Ratio, applied ratio (Ra‐ TrendColor6 Trend view Ratio
gray tioInt or RatioExt) "Ra‐
tioOut"
431 12 0 009D00 Dark lime Dosing, dosing amount TrendColor3 Trend view Dosing
green
432 12 0 FF0000 Pure red Monitoring, gradient TrendColor2 Trend view Mo‐
value nAnL
433 12 0 E69100 Pure orange Monitoring, output 1 TrendColor1 Trend view Mon‐
Di08, MonDiL,
MonDiS
434 12 0 00CE00 Bright lime Monitoring, output 2 TrendColor2 Trend view Mon‐
green Di08
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Type block icons
index tion paren‐ (RGB) name ute name]
cy
435 12 0 0000FF Pure blue Monitoring, output 3 TrendColor3 Trend view Mon‐
Di08
436 12 0 B100B5 Bright ma‐ Monitoring, output 4 TrendColor4 Trend view Mon‐
genta Di08
437 12 0 FF0000 Pure red Monitoring, output 5 TrendColor5 Trend view Mon‐
Di08
438 12 0 494949 Very dark Monitoring, output 6 TrendColor6 Trend view Mon‐
gray Di08
439 12 0 543500 Very dark Monitoring, output 7 TrendColor7 Trend view Mon‐
orange Di08
440 13 0 005400 Very dark Monitoring, output 8 TrendColor8 Trend view Mon‐
lime green Di08
441 13 0 00CE00 Bright lime Monitoring, flutter val‐ TrendColor2 Trend view MonDiL
green ue
442 13 0 E69100 Pure orange Operation, binary out‐ TrendColor1 Operation, trend
put / binary output 1 view binary
443 13 0 494949 Very dark Operation, binary out‐ TrendColor2 Operation, trend
gray put 2 view binary
444 13 0 0000FF Pure blue Operation, binary out‐ TrendColor3 Operation, trend
put 3 view binary
445 13 0 B100B5 Bright ma‐ Operation, binary feed‐ TrendColor4 Operation, trend
genta back 1 view binary
446 13 0 FF0000 Pure red Operation, binary feed‐ TrendColor5 Operation, trend
back 2 view binary
447 13 0 00CE00 Bright lime Operation, binary feed‐ TrendColor2, TrendCol‐ Operation, trend
green back / binary feedback 3 or6 view binary
448 13 0 0000FF Pure blue Actuators, valve control TrendColor1 - Trend‐ Trend view Valve
output Color4, TrendColor6
449 13 0 000000 Black Actuators, valve feed‐ TrendColor1 Trend view Valve
back open
450 13 0 6D6D6D Very dark Actuators, valve feed‐ TrendColor2 Trend view Valve
gray back close
451 13 0 005400 Very dark Actuators, valve feed‐ TrendColor1, TrendCol‐ Trend view
lime green back or3, TrendColor5, Vlv2WayL
TrendColor7
452 13 0 E69100 Pure orange Actuators, open valve TrendColor1 Trend view
output VlvMotL
453 13 0 00CE00 Bright lime Actuators, close valve TrendColor2 Trend view
green output VlvMotL
454 13 0 0000FF Pure blue Actuators, valve feed‐ TrendColor3 Trend view
back open VlvMotL
455 13 0 B100B5 Bright ma‐ Actuators, valve feed‐ TrendColor4 Trend view
genta back close VlvMotL
456 13 0 FF0000 Pure red Actuators, valve feed‐ TrendColor5 Trend view
back open VlvMotL
457 13 0 005400 Very dark Actuators, valve feed‐ TrendColor6 Trend view
lime green back close VlvMotL
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Type block icons
index tion paren‐ (RGB) name ute name]
cy
458 13 0 E69100 Pure orange Actuators, motor start TrendColor1 Trend view
output MotL/MotS
459 13 0 00CE00 Bright lime Actuators, motor feed‐ TrendColor2 Trend view
green back MotL/MotS
460 14 0 E69100 Pure orange Drives, motor start TrendColor1 Trend view
Speed1 / forward MotSpdL/MotRevL/
MotSpdCL
461 14 0 00CE00 Bright lime Drives, motor start TrendColor2 Trend view
green Speed2 / reverse MotSpdL/MotRevL/
MotSpdCL
462 14 0 0000FF Pure blue Drives, feedback TrendColor3 Trend view
Speed1 / forward MotSpdL/MotRevL
463 14 0 B100B5 Bright ma‐ Drives, feedback TrendColor4 Trend view
genta Speed2 / reverse MotSpdL/MotRevL
464 14 0 00FFFA Pure cyan Drives, feedback for‐ TrendColor3 Trend view
ward MotSpdCL
465 14 0 B100B5 Bright ma‐ Drives, feedback reverse TrendColor4 Trend view
genta MotSpdCL
466 14 0 E69100 Pure orange Count: Output TrendColor1 Trend view Counter
467 14 0 E69100 Pure orange Count / time: Unit on TrendColor1 CountOh / TimeTrig
468 14 0 005400 Very dark Count / time: Count type TrendColor7 CountOh / TimeTrig
lime green
469 14 0 E69100 Pure orange Count / time: Count type TrendColor1 Trend view
CntOhSc
470 14 0 00CE00 Bright lime Count / time: Unit on TrendColor2 Trend view
green CntOhSc
471 14 0 005400 Very dark Count: Service life TrendColor7 Trend view
lime green CntOhSc
472 14 0 6D6D6D Very dark Count: Count TrendColor8 Trend view
gray CntOhSc
473 14 0 0000FF Pure blue Statusdisplay operation State1BackColor Mostly In Parame‐
command - Release for ter view APL ob‐
Maintenance” (“Yes”): jects with Type‐
background color ID=11
474 14 0 FFFFFF White Statusdisplay operation State1FillColor Mostly In Parame‐
command - Release for ter view APL ob‐
Maintenance” (“Yes”): jects with Type‐
filling pattern color ID=11
475 14 0 FFFFFF White Statusdisplay operation State1FontColor Mostly In Parame‐
command -Release for ter view APL ob‐
Maintenance (“Yes”): jects with Type‐
font color ID=11
476 14 0 919191 Dark gray Statusdisplay (“Not State1BackColor… Mostly In ShrdResS
Ready”, “None”, “No”): State7BackColor Standard \Preview
background color view APL objects
with TypeID=11,19
Color Sec‐ Trans‐ HTML code Color Description Property(ies) [attrib‐ Type block icons
index tion paren‐ (RGB) name ute name]
cy
477 14 0 DADADA Very light Statusdisplay (“Not State1FillColor… Mostly In ShrdResS
gray Ready”, “None”,”No”): State7FillColor Standard \Preview
filling pattern color view APL objects
with TypeID=11,19
478 14 0 000000 Black Statusdisplay (“Not State1FontColor… Mostly In ShrdResS
Ready”, “None”,”No”): State7FontColor Standard \Preview
font color view APL objects
with TypeID=11,19
479 14 0 757575 Gray Analog value in views FontColor Mostly In Standard
for high and low scale. \Limit view I/O
fields (also exten‐
ded)
1
For example, PIDConL "PV_ToleHi#Value", ".MV_HiAct#Value"
2
ModPreCon=@PG_APL_TrendMPC.PDL; MPC10x10=@PG_APL_TrendMPC_L.PDL
Note
If these colors were changed only via the OS project editor, the default values can be assigned
again.
D
E
This area shows the current "Process value" in the form of a bar graph. You can also see the high
low limits of the bar graph’s scale. The visible area in the bar graph depends on the
configuration in the engineering system (ES).
Note
The value displayed can be different for different blocks. For example, the Bar graph display other
than "Process Value" are as follows
Note
• The symbols displayed are not valid for user-configured message classes. Please take into
consideration the validity of terms for User-configured message classes.
• The limit triangles visibility depends on the configuration in engineering system (ES).
– If a limit is not enabled (e.g. PV_AH_En = 0 & Feature.Bit23 =0) then triangle for
corresponding limit (high alarm in this example) will not be visible.
– If a limit is not supported by a block, then the corresponding limit triangle is not displayed.
E.g. DoseL block only has Alarm high and Alarm low limits. So, limit triangles for Warning
and Tolerence will not be visible.
– For TotalL, CountOh and CountScL, in counting mode "count up", only the colored
triangles of the upper limits are visible; and in counting mode "count down", only the
colored triangles of the lower limits are visible.
– For MotSpdCL, only the warning high and low limit triangles for readback value are
displayed.
– For CntOhSc, only the high limit triangles are available for the following configured
limits in the respective bar graph:
Red: High limit 1
Yellow: High limit 2
– For ConPerMon, only the low limit triangles are available for the following configured
limits in the respective bar graph:
Red: Low alarm limit
Yellow: Low warning limit
For PumpMon, only the high and low limit triangles for Alarms and warnings for readback
value are displayed.
D
E
F
G
Gradient monitoring is displayed when the gradient value PV_Grad ≠ 0 and one of the following
monitoring functions is activated:
• Gradient monitoring for positive changes (GradHUpEn = 1)
• Gradient monitoring for negative changes (GradHDnEn = 1)
• Gradient monitoring (GradLEn = 1)
(2) Bar graph for the gradient
This area shows the current gradient value in the form of a bar graph. The visible area in the bar
graph depends on the configuration in the engineering system (ES).
The bar graph is displayed when gradient monitoring is activated for positive (GradHUpEn = 1)
or negative changes (GradHDnEn = 1).
(3) Display of limits in the bar graph
This area shows you the specified limits.
The display only appears when the bar for the gradients is also displayed.
• 3a: Limit (high) for positive gradients (GradHUpLim)
• 3b, 3c: Limit (low) for positive and negative gradients (GradLLim)
• 3d: Limit (high) for negative gradients (GradHDnLim)
D
E
Note
For Ratio block, this area shows you the current value for the ratio (RatioOut).
Note
For Ratio block, these blue triangles show the configured High and low range limits for the ratio.
D E
Note
For Ratio block this display graphically represents the output value, Out
Note
For Ratio block limits are for output value Out.
(4) Display for the target manipulated variable of the manipulated variable ramp
This display [R] shows the target setpoint and is only visible if you have enabled ramp generation
in the Ramp view (Page 339).
(5) Display for the target manipulated variable of the manipulated variable gradient ramp
This display [G] shows the target setpoint and is only visible if you have enabled gradient ramp
generation in the Ramp view (Page 339).
(6) Display of the manipulated variable for automatic mode
The display [A] is only visible when the block is not in automatic mode. In Automatic mode, it is
displayed when it needs to be reset or when tracking or forced tracking is enabled.
This display shows the manipulated variable that would apply if you were to switch to automatic
mode or if you were to reset in automatic mode or disable tracking or forced tracking.
D E
D E
Note
The limit triangles visibility depends on the configuration in engineering system (ES).
If a limit is not enabled (e.g. RbkWH_En= 0 & Feature.Bit31 =0 for PIDConL) then triangle
for corresponding limit (Warning high limit in this example) will not be visible.
(3) The limits for the "open" and "close" positions (for VlvAnL)
• 3a: limits for the "close" position
• 3b: limits for the "open" position
1)
RstLi.Val
ue or
2) By Auto
Commands
Manual 0 1 1 0 0 Possible by
forced com‐
mands
0 0 1 0 0 Possible
by
RstLi.Val
ue
Local 0 0 0 0 1 Reset is pos‐
sible only via
Faceplate
hence not
recommen‐
ded to Re‐
move
the
OS_Perm.B
it7
Overview
The "PCS 7 measuring point browser" window displays all relevant status information of the APL
function blocks.
On mode
Manual mode
Automatic mode
Program mode
Local mode
External setpoint
Ramp active
Bad, device-related
Bad, process-related
Uncertain, device-related
Uncertain, process-related
Maintenance request
In progress
Forcing
Bypass
Interlock disabled
Rapid stop
Reset request
Suppressed messages
Internal error
Group error