Process Control System PCS 7

Basics of APL 1
SIMATIC PCS 7 Advanced Process Library V71

______________
Operator control blocks 2
______________
Generator blocks 3
______________
Control blocks 4
SIMATIC ______________
Motor and valve blocks 5
Process Control System PCS 7
______________
Channel blocks 6
PCS 7 Advanced Process Library ______________ 7
V71 Conversion blocks
______________ 8
Message blocks
Function Manual ______________ 9
Dosing blocks
______________ 10
______________
Mathematical blocks
11
______________
Interlock blocks
12
______________
Monitoring blocks
13
______________
Counter blocks
14
______________
Logical analog blocks
15
______________
Logical digital blocks
16
______________
Maintenance blocks
17
______________
System blocks
PCS 7 Advanced Process
18
______________
Control Templates
19
______________
Definitions
03/2009
A5E02102723-01
Legal information
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.
CAUTION
without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.
NOTICE
indicates that an unintended result or situation can occur if the corresponding information is not taken into
account.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The device/system may only be set up and used in conjunction with this documentation. Commissioning and
operation of a device/system may only be performed by qualified personnel. Within the context of the safety notes
in this documentation qualified persons are defined as persons who are authorized to commission, ground and
label devices, systems and circuits in accordance with established safety practices and standards.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be adhered to. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this
publication may be trademarks whose use by third parties for their own purposes could violate the rights of the
owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
Siemens AG A5E02102723-01 Copyright © Siemens AG 2009.

Industry Sector Ⓟ 01/2009 Technical data subject to change
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents
1 Basics of APL .......................................................................................................................................... 25

1.1 Block modes.................................................................................................................................25
1.1.1 Overview of the modes ................................................................................................................25
1.1.2 On ...............................................................................................................................................27
1.1.3 Out of service ...............................................................................................................................27
1.1.4 Manual and Automatic mode for control blocks...........................................................................29
1.1.5 Manual and automatic mode for motors, valves and dosers .......................................................32
1.1.6 Program mode for closed-loop controllers...................................................................................34
1.1.7 Local mode...................................................................................................................................36
1.1.8 Status diagram for the operating modes......................................................................................39
1.2 General functions of the blocks....................................................................................................42
1.2.1 Operating, monitoring and reporting ............................................................................................42
1.2.1.1 Display and operator input area for process values and setpoints..............................................42
1.2.1.2 Calling further faceplates .............................................................................................................43
1.2.1.3 Operator permissions...................................................................................................................45
1.2.1.4 Generating instance-specific messages ......................................................................................46
1.2.1.5 Maintenance release....................................................................................................................47
1.2.1.6 Time stamp ..................................................................................................................................51
1.2.1.7 Displaying auxiliary values...........................................................................................................52
1.2.1.8 Selecting a unit of measure .........................................................................................................53
1.2.2 Monitoring functions.....................................................................................................................70
1.2.2.1 Monitoring functions at the Advanced Process Library ...............................................................70
1.2.2.2 Limit monitoring............................................................................................................................70
1.2.2.3 Alarm delays ................................................................................................................................79
1.2.2.4 Feedbacks....................................................................................................................................83
1.2.3 Signals .........................................................................................................................................86
1.2.3.1 Output signal as a static signal or pulse signal............................................................................86
1.2.3.2 Recording the first signal for interlock blocks ..............................................................................87
1.2.3.3 Forming and outputting signal status for blocks ..........................................................................88
1.2.3.4 Selecting signals for processing ..................................................................................................93
1.2.3.5 Simulating signals ........................................................................................................................93
1.2.3.6 Setpoint input - internal and external ...........................................................................................96
1.2.3.7 Using a setpoint ramp ..................................................................................................................98
1.2.3.8 Deadband.....................................................................................................................................99
1.2.4 Interlocking functions .................................................................................................................100
1.2.4.1 Interlocks....................................................................................................................................100
1.2.4.2 Trip function ...............................................................................................................................102
1.2.4.3 Rapid stop for motors.................................................................................................................102
1.2.4.4 Influence of the signal status on the interlock............................................................................103
1.2.4.5 Forming the group status for interlock information ....................................................................105
1.2.4.6 Disabling interlocks ....................................................................................................................107
PCS 7 Advanced Process Library V71

Function Manual, 03/2009, A5E02102723-01 3
Table of contents
1.2.5 General functions for controllers ............................................................................................... 108

1.2.5.1 Ramp limiting of the setpoint..................................................................................................... 108
1.2.5.2 Inverting the control sense ........................................................................................................ 108
1.2.5.3 Control error generation and deadband.................................................................................... 109
1.2.5.4 Using control zones................................................................................................................... 109
1.2.5.5 Setpoint limiting for external setpoints ...................................................................................... 110
1.2.5.6 Setpoint tracking the process variable in manual mode ........................................................... 110
1.2.5.7 Tracking and limiting a manipulated value................................................................................ 111
1.2.5.8 Activating and limiting disturbance variable .............................................................................. 113
1.2.5.9 Structure segmentation at controllers ....................................................................................... 113
1.2.6 Forcing operating states............................................................................................................ 115
1.2.7 Error handling............................................................................................................................ 117
1.2.8 Resetting the block in case of interlocks or errors .................................................................... 119
1.2.9 Safe position for motors, valves and controllers ....................................................................... 120
1.2.10 Specifying warning times for control functions at motors and valves ....................................... 122
1.2.11 SIMATIC BATCH functionality .................................................................................................. 122
1.3 General functions of the faceplates .......................................................................................... 123
1.3.1 Structure of the faceplate .......................................................................................................... 123
1.3.2 Switching operating states and operating modes ..................................................................... 127
1.3.3 Changing values ....................................................................................................................... 129
1.3.4 Standard view of FM controllers (analog) ................................................................................. 131
1.3.5 Standard view of FM controllers (pulse controller) ................................................................... 135
1.3.6 Standard view of FM controllers (step controller with position feedback)................................. 139
1.3.7 Standard view of FM controllers (step controller without position feedback)............................ 143
1.3.8 Standard view of interlock blocks.............................................................................................. 147
1.3.9 Parameter view of PID controllers ............................................................................................ 151
1.3.10 Parameter view of FM controllers ............................................................................................. 153
1.3.11 Parameter view for motors and valves...................................................................................... 155
1.3.12 Limit value view of FM controllers............................................................................................. 157
1.3.13 Limit value view of PID controllers ............................................................................................ 160
1.3.14 Limit value view of motors......................................................................................................... 163
1.3.15 Preview of FM controllers.......................................................................................................... 165
1.3.16 Ramp view................................................................................................................................. 167
1.3.17 Message view ........................................................................................................................... 169
1.3.18 Batch view ................................................................................................................................. 170
1.3.19 Memo view ................................................................................................................................ 171
1.3.20 Trend view................................................................................................................................. 172
1.4 General functions of the block icons ......................................................................................... 174
1.4.1 Block icon structure................................................................................................................... 174
1.4.2 Configuring the block icons ....................................................................................................... 180
1.4.3 Operation via the block icon...................................................................................................... 181
1.4.4 Block icons for PID and FM controller....................................................................................... 181
1.4.5 Block icon for interlock blocks ................................................................................................... 184

4 Function Manual, 03/2009, A5E02102723-01
Table of contents
1.5 Selectable block response .........................................................................................................186

1.5.1 Functions that can be set via the Feature I/O............................................................................186
1.5.2 Stopping dosing at a flow alarm.................................................................................................187
1.5.3 Setting the startup response ......................................................................................................187
1.5.4 Automatic dribble correction for underdosing in automatic mode..............................................188
1.5.5 Switching operator controls for external setpoint to visible........................................................189
1.5.6 Enabling direct changeover between forward and reverse .......................................................189
1.5.7 Specifying the dosing type .........................................................................................................189
1.5.8 Unit for the rate of change .........................................................................................................190
1.5.9 Issuing substitute value if raw value is invalid ...........................................................................190
1.5.10 Activating recording of the first signal ........................................................................................191
1.5.11 Issuing last valid value if raw value is invalid.............................................................................191
1.5.12 Selecting values associated with messages..............................................................................192
1.5.13 Enabling rapid stop via faceplate ...............................................................................................192
1.5.14 Enabling program mode.............................................................................................................192
1.5.15 Update acknowledgment and error status of the message call.................................................193
1.5.16 Resetting the commands for changing the mode ......................................................................193
1.5.17 Enabling resetting of commands for the control settings...........................................................193
1.5.18 Resetting the dosing quantity when dosing starts .....................................................................194
1.5.19 Resetting via input signals in the event of interlocks or errors ..................................................194
1.5.20 Setting switch or button mode....................................................................................................195
1.5.21 Creep rate is always detected in the dosing quantity ................................................................195
1.5.22 Safety value of the manipulated variable effective at startup ....................................................196
1.5.23 Safety manipulated variable with "out of service" operating mode in effect ..............................196
1.5.24 Activating bumpless changes to proportional gain ....................................................................196
1.5.25 Disabling bumpless changeover to automatic mode for controllers ..........................................197
1.5.26 Enabling bumpless changeover to automatic mode for valves, motors, and dosers ................197
1.5.27 Output invalid raw value.............................................................................................................198
1.5.28 Reaction to the out of service mode ..........................................................................................199
1.5.29 Exiting local mode......................................................................................................................199
2 Operator control blocks.......................................................................................................................... 201
2.1 OpAnL- check and output analog signals ..................................................................................201
2.1.1 Description of OpAnL.................................................................................................................201
2.1.2 OpAnL modes ............................................................................................................................203
2.1.3 OpAnL functions ........................................................................................................................204
2.1.4 OpAnL error handling.................................................................................................................206
2.1.5 OpAnL messaging .....................................................................................................................207
2.1.6 OpAnL I/Os ................................................................................................................................209
2.1.7 OpAnL block diagram ................................................................................................................214
2.1.8 Operator control and monitoring ................................................................................................214
2.1.8.1 Views of OpAnL .........................................................................................................................214
2.1.8.2 OpAnL standard view.................................................................................................................215
2.1.8.3 OpAnL parameter view ..............................................................................................................217
2.1.8.4 OpAnL preview...........................................................................................................................218
2.1.8.5 Block icon for OpAnL .................................................................................................................219
2.2 OpTrig - Manipulating a digital value (1 pushbutton) .................................................................222
2.2.1 Description of OpTrig .................................................................................................................222
2.2.2 OpTrig modes ............................................................................................................................224
2.2.3 OpTrig functions.........................................................................................................................225
2.2.4 OpTrig error handling.................................................................................................................227
2.2.5 OpTrig messaging......................................................................................................................227
2.2.6 OpTrig I/Os.................................................................................................................................228
2.2.7 OpTrig block diagram.................................................................................................................230

Table of contents
2.2.8 Operator control and monitoring ............................................................................................... 230

2.2.8.1 Views of OpTrig......................................................................................................................... 230
2.2.8.2 OpTrig standard view ................................................................................................................ 231
2.2.8.3 OpTrig preview.......................................................................................................................... 232
2.2.8.4 Block symbol for OpTrig............................................................................................................ 233
2.3 OpDi01 - Manipulating a digital value (2 pushbuttons) ............................................................. 234
2.3.1 Description of OpDi01 ............................................................................................................... 234
2.3.2 OpDi01 modes .......................................................................................................................... 236
2.3.3 OpDi01 functions....................................................................................................................... 237
2.3.4 OpDi01 error handling............................................................................................................... 239
2.3.5 OpDi01 messaging.................................................................................................................... 239
2.3.6 OpDi01 I/Os .............................................................................................................................. 240
2.3.7 OpDi01 block diagram............................................................................................................... 243
2.3.8.1 Views of OpDi01 ....................................................................................................................... 243
2.3.8.2 OpDi01 standard view............................................................................................................... 244
2.3.8.3 OpDi01 preview......................................................................................................................... 246
2.3.8.4 Block symbol for OpDi01........................................................................................................... 248
2.4 OpDi03 - Manipulating a digital value (3 pushbuttons) ............................................................. 249
2.4.1 Description of OpDi03 ............................................................................................................... 249
2.4.2 OpDi03 modes .......................................................................................................................... 251
2.4.3 OpDi03 functions....................................................................................................................... 252
2.4.4 OpDi03 error handling............................................................................................................... 255
2.4.5 OpDi03 messaging.................................................................................................................... 256
2.4.6 OpDi03 I/Os .............................................................................................................................. 257
2.4.7 OpDi03 block diagram............................................................................................................... 260
2.4.8.1 Views of OpDi03 ....................................................................................................................... 261
2.4.8.2 OpDi03 standard view............................................................................................................... 261
2.4.8.3 OpDi03 preview......................................................................................................................... 263
2.4.8.4 Block symbol for OpDi03........................................................................................................... 265
3 Generator blocks ................................................................................................................................... 267
3.1 NoiseGen - Rauschgenerator ................................................................................................... 267
3.1.1 Description of NoiseGen ........................................................................................................... 267
3.1.2 NoiseGen I/Os........................................................................................................................... 268
4 Control blocks ........................................................................................................................................ 269
4.1 ConPerMon - monitoring of the control performance of control loops ...................................... 269
4.1.1 Description of ConPerMon ........................................................................................................ 269
4.1.2 ConPerMon modes ................................................................................................................... 274
4.1.3 ConPerMon functions................................................................................................................ 275
4.1.4 ConPerMon error handling........................................................................................................ 286
4.1.5 ConPerMon messaging............................................................................................................. 287
4.1.6 ConPerMon I/Os ....................................................................................................................... 289
4.1.7 ConPerMon block diagram........................................................................................................ 295
4.1.8.1 ConPerMon views ..................................................................................................................... 295
4.1.8.2 ConPerMon standard view........................................................................................................ 296
4.1.8.3 ConPerMon limit value view...................................................................................................... 298
4.1.8.4 ConPerMon parameter view ..................................................................................................... 300
4.1.8.5 ConPerMon preview.................................................................................................................. 302
4.1.8.6 ConPerMon's setpoint view....................................................................................................... 303
4.1.8.7 Block symbol for ConPerMon.................................................................................................... 305

Table of contents
4.2 FmCont - Interface to module FM 355.......................................................................................306

4.2.1 Description of FmCont ...............................................................................................................306
4.2.2 FmCont modes...........................................................................................................................310
4.2.3 FmCont functions.......................................................................................................................311
4.2.4 FmCont error handling ...............................................................................................................321
4.2.5 FmCont messaging....................................................................................................................323
4.2.6 FmCont I/Os...............................................................................................................................326
4.2.7 FmCont block diagram...............................................................................................................340
4.2.8.1 FmCont views ............................................................................................................................342
4.3 FmTemp - Interface to temperature controller modules FM 355-2............................................343
4.3.1 Description of FmTemp..............................................................................................................343
4.3.2 FmTemp modes .........................................................................................................................347
4.3.3 FmTemp functions .....................................................................................................................348
4.3.4 FmTemp error handling .............................................................................................................358
4.3.5 FmTemp messaging ..................................................................................................................360
4.3.6 FmTemp I/Os .............................................................................................................................363
4.3.7 FmTemp block diagram .............................................................................................................378
4.3.8.1 FmTemp views...........................................................................................................................380
4.4 GainSched - Adapting parameter values for a PID controller....................................................381
4.4.1 Description of GainSched ..........................................................................................................381
4.4.2 GainSched modes .....................................................................................................................384
4.4.3 GainSched functions..................................................................................................................385
4.4.4 GainSched error handling ..........................................................................................................385
4.4.5 GainSched messaging...............................................................................................................386
4.4.6 GainSched I/Os..........................................................................................................................387
4.4.7 GainSched block diagram..........................................................................................................390
4.4.8.1 GainSched views .......................................................................................................................390
4.4.8.2 GainSched standard view ..........................................................................................................391
4.4.8.3 GainSched parameter view........................................................................................................392
4.5 ModPreCon - Model predictive controller ..................................................................................393
4.5.1 Description of ModPreCon.........................................................................................................393
4.5.2 ModPreCon modes ....................................................................................................................397
4.5.3 ModPreCon functions ................................................................................................................398
4.5.4 ModPreCon error handling.........................................................................................................409
4.5.5 ModPreCon messaging .............................................................................................................410
4.5.6 ModPreCon I/Os ........................................................................................................................411
4.5.7 ModPreCon block diagram ........................................................................................................419
4.5.8.1 ModPreCon views......................................................................................................................419
4.5.8.2 ModPreCon standard view.........................................................................................................420
4.5.8.3 ModPreCon parameter view ......................................................................................................423
4.5.8.4 Parameter view channel 1 to 4 of ModPreCon ..........................................................................425
4.5.8.5 ModPreCon preview ..................................................................................................................427
4.5.8.6 Block icon for ModPreCon .........................................................................................................429

Table of contents
4.6 PIDConL - Continuous PID controller ....................................................................................... 431

4.6.1 Description of PIDConL............................................................................................................. 431
4.6.2 PIDConL modes........................................................................................................................ 435
4.6.3 PIDConL functions .................................................................................................................... 436
4.6.4 PIDConL error handling ............................................................................................................ 445
4.6.5 PIDConL messaging ................................................................................................................. 446
4.6.6 PIDConL I/Os ............................................................................................................................ 449
4.6.7 PIDConL block diagram ............................................................................................................ 460
4.6.8.1 PIDConL views.......................................................................................................................... 462
4.6.8.2 Standard view of PIDConL and PIDConR ................................................................................ 463
4.6.8.3 Preview of PIDConL and PIDConR .......................................................................................... 467
4.7 PIDConR - Continuous PID controller with external reset ........................................................ 469
4.7.1 Description of PIDConR ............................................................................................................ 469
4.7.2 PIDConR modes ....................................................................................................................... 475
4.7.3 PIDConR functions.................................................................................................................... 478
4.7.4 PIDConR error handling............................................................................................................ 489
4.7.5 PIDConR messaging................................................................................................................. 490
4.7.6 PIDConR I/Os ........................................................................................................................... 493
4.7.7 PIDConR block diagram............................................................................................................ 504
4.7.8.1 PIDConR views ......................................................................................................................... 504
4.8 PIDStepL - step controller ......................................................................................................... 505
4.8.1 Description of PIDStepL............................................................................................................ 505
4.8.2 PIDStepL modes ....................................................................................................................... 509
4.8.3 PIDStepL functions ................................................................................................................... 510
4.8.4 PIDStepL error handling............................................................................................................ 519
4.8.5 PIDStepL messaging ................................................................................................................ 521
4.8.6 PIDStepL I/Os ........................................................................................................................... 524
4.8.7 PIDStepL block diagram ........................................................................................................... 536
4.8.8.1 PIDStepL views......................................................................................................................... 540
4.8.8.2 Standard view of PIDStepL without position feedback ............................................................. 541
4.8.8.3 Standard view of PIDStepL with position feedback .................................................................. 545
4.8.8.4 PIDStepL preview ..................................................................................................................... 549
4.9 Ratio - ratio controlling .............................................................................................................. 551
4.9.1 Description of Ratio................................................................................................................... 551
4.9.2 Ratio modes .............................................................................................................................. 553
4.9.3 Ratio functions .......................................................................................................................... 554
4.9.4 Ratio error handling................................................................................................................... 557
4.9.5 Ratio messaging ....................................................................................................................... 558
4.9.6 Ratio I/Os .................................................................................................................................. 559
4.9.7 Ratio block diagram .................................................................................................................. 563
4.9.8.1 Ratio views ................................................................................................................................ 563
4.9.8.2 Ratio standard view................................................................................................................... 564
4.9.8.3 Ratio parameter view ................................................................................................................ 567
4.9.8.4 Ratio preview ............................................................................................................................ 569
4.9.8.5 Block symbol for ratio................................................................................................................ 570

Table of contents
4.10 SplRange - signal splitter ...........................................................................................................572

4.10.1 Description of SplRange ............................................................................................................572
4.10.2 SplRange modes .......................................................................................................................574
4.10.3 SplRange functions....................................................................................................................575
4.10.4 SplRange error handling ............................................................................................................578
4.10.5 SplRange messaging.................................................................................................................578
4.10.6 SplRange I/Os............................................................................................................................579
4.10.7 SplRange block diagram............................................................................................................581
5 Motor and valve blocks .......................................................................................................................... 583
5.1 MotL - Motor...............................................................................................................................583
5.1.1 Description of MotL ....................................................................................................................583
5.1.2 MotL modes ...............................................................................................................................587
5.1.3 MotL functions............................................................................................................................589
5.1.4 MotL error handling....................................................................................................................594
5.1.5 MotL messaging.........................................................................................................................595
5.1.6 MotL I/Os....................................................................................................................................597
5.1.7 MotL block diagram....................................................................................................................604
5.1.8.1 MotL views .................................................................................................................................604
5.1.8.2 MotL standard view....................................................................................................................605
5.1.8.3 MotL preview..............................................................................................................................608
5.1.8.4 Block symbol for MotL................................................................................................................611
5.2 MotRevL - Reversible motor ......................................................................................................613
5.2.1 Description of MotRevL..............................................................................................................613
5.2.2 MotRevL modes.........................................................................................................................617
5.2.3 MotRevL functions .....................................................................................................................619
5.2.4 MotRevL error handling .............................................................................................................625
5.2.5 MotRevL messaging ..................................................................................................................627
5.2.6 MotRevL I/Os .............................................................................................................................629
5.2.7 MotRevL block diagram .............................................................................................................637
5.2.8.1 MotRevL views...........................................................................................................................637
5.2.8.2 MotRevL standard view .............................................................................................................638
5.2.8.3 MotRevL preview .......................................................................................................................641
5.2.8.4 Block icon for MotRevL ..............................................................................................................644
5.3 MotSpdCL - Controllable motor with two directions of rotation..................................................646
5.3.1 MotSpdCL description................................................................................................................646
5.3.2 MotSpdCL modes ......................................................................................................................651
5.3.3 MotSpdCL functions...................................................................................................................653
5.3.4 MotSpdCL error handling...........................................................................................................659
5.3.5 MotSpdCL messaging................................................................................................................661
5.3.6 MotSpdCL I/Os...........................................................................................................................663
5.3.7 MotSpdCL block diagram...........................................................................................................672
5.3.8.1 MotSpdCL views ........................................................................................................................672
5.3.8.2 MotSpdCL standard view...........................................................................................................673
5.3.8.3 Limit view for readback values of MotSpdCL.............................................................................678
5.3.8.4 MotSpdCL parameter view ........................................................................................................679
5.3.8.5 MotSpdCL preview.....................................................................................................................681
5.3.8.6 Block symbol for MotSpdCL.......................................................................................................684

Table of contents
5.4 MotSpdL - Two-speed motor..................................................................................................... 687

5.4.1 Description of MotSpdL............................................................................................................. 687
5.4.2 MotSpdL modes ........................................................................................................................ 691
5.4.3 Functions of MotSpdL ............................................................................................................... 693
5.4.4 MotSpdL error handling............................................................................................................. 699
5.4.5 MotSpdL messaging ................................................................................................................. 701
5.4.6 MotSpdL I/Os ............................................................................................................................ 703
5.4.7 MotSpdL block diagram ............................................................................................................ 710
5.4.8.1 MotSpdL views.......................................................................................................................... 711
5.4.8.2 MotSpdL standard view............................................................................................................. 712
5.4.8.3 MotSpdL preview ...................................................................................................................... 715
5.4.8.4 Block symbol for MotSpdL ........................................................................................................ 718
5.5 Vlv2WayL - Two-way valve ....................................................................................................... 720
5.5.1 Description of Vlv2WayL ........................................................................................................... 720
5.5.2 Vlv2WayL modes ...................................................................................................................... 724
5.5.3 Vlv2WayL functions................................................................................................................... 726
5.5.4 Vlv2WayL error handling........................................................................................................... 731
5.5.5 Vlv2WayL messaging................................................................................................................ 733
5.5.6 Vlv2WayL I/Os .......................................................................................................................... 735
5.5.7 Vlv2WayL block diagram........................................................................................................... 743
5.5.8.1 Vlv2WayL views ........................................................................................................................ 743
5.5.8.2 Vlv2WayL standard view........................................................................................................... 744
5.5.8.3 Vlv2WayL parameter view ........................................................................................................ 747
5.5.8.4 Vlv2WayL preview..................................................................................................................... 749
5.5.8.5 Block symbol for Vlv2WayL....................................................................................................... 752
5.6 VlvL - Valve ............................................................................................................................... 754
5.6.1 Description of VlvL .................................................................................................................... 754
5.6.2 VlvL modes ............................................................................................................................... 758
5.6.3 VlvL functions............................................................................................................................ 760
5.6.4 VlvL error handling .................................................................................................................... 765
5.6.5 VlvL messaging......................................................................................................................... 766
5.6.6 VlvL I/Os.................................................................................................................................... 768
5.6.7 VlvL block diagram.................................................................................................................... 775
5.6.8 Control and monitoring.............................................................................................................. 775
5.6.8.1 VlvL views ................................................................................................................................. 775
5.6.8.2 VlvL standard view .................................................................................................................... 776
5.6.8.3 VlvL preview.............................................................................................................................. 779
5.6.8.4 VlvL block icon .......................................................................................................................... 782
5.7 VlvMotL - Motor valve ............................................................................................................... 785
5.7.1 Description of VlvMotL .............................................................................................................. 785
5.7.2 VlvMotL modes ......................................................................................................................... 789
5.7.3 VlvMotL functions...................................................................................................................... 791
5.7.4 VlvMotL error handling .............................................................................................................. 797
5.7.5 VlvMotL messaging................................................................................................................... 799
5.7.6 VlvMotL I/Os.............................................................................................................................. 801
5.7.7 VlvMotL block diagram.............................................................................................................. 809
5.7.8.1 VlvMotL views ........................................................................................................................... 809
5.7.8.2 VlvMotL standard view .............................................................................................................. 810
5.7.8.3 VlvMotL preview........................................................................................................................ 813
5.7.8.4 Block symbol for VlvMotL.......................................................................................................... 816

Table of contents
6 Channel blocks ...................................................................................................................................... 821

6.1 Notes on using driver blocks......................................................................................................821
6.2 FbAnIn - Analog input driver for field devices ............................................................................822
6.2.1 Description of FbAnIn ................................................................................................................822
6.2.2 FbAnIn modes............................................................................................................................823
6.2.3 FbAnIn functions ........................................................................................................................824
6.2.4 FbAnIn error handling ................................................................................................................827
6.2.5 FbAnIn messaging .....................................................................................................................828
6.2.6 FbAnIn I/Os ................................................................................................................................829
6.2.7 FbAnIn block diagram ................................................................................................................831
6.3 FbAnOu - Analog output driver for field devices ........................................................................832
6.3.1 Description of FbAnOu...............................................................................................................832
6.3.2 FbAnOu modes ..........................................................................................................................835
6.3.3 FbAnOu functions ......................................................................................................................836
6.3.4 FbAnOu error handling ..............................................................................................................838
6.3.5 FbAnOu messaging ...................................................................................................................839
6.3.6 FbAnOu I/Os ..............................................................................................................................839
6.3.7 FbAnOu block diagram ..............................................................................................................844
6.4 FbDiIn - Digital input driver for field devices ..............................................................................845
6.4.1 Description of FbDiIn .................................................................................................................845
6.4.2 FbDiIn modes.............................................................................................................................847
6.4.3 FbDiIn functions .........................................................................................................................847
6.4.4 FbDiIn error handling .................................................................................................................850
6.4.5 FbDiIn messaging ......................................................................................................................851
6.4.6 FbDiIn I/Os .................................................................................................................................851
6.4.7 FbDiIn block diagram .................................................................................................................854
6.5 FbDiOu - Digital output driver for field devices ..........................................................................855
6.5.1 Description of FbDiOu................................................................................................................855
6.5.2 FbDiOu modes ...........................................................................................................................858
6.5.3 FbDiOu functions .......................................................................................................................858
6.5.4 FbDiOu error handling ...............................................................................................................860
6.5.5 FbDiOu messaging ....................................................................................................................861
6.5.6 FbDiOu I/Os ...............................................................................................................................862
6.5.7 FbDiOu block diagram ...............................................................................................................866
6.6 Pcs7AnIn - Analog input driver ..................................................................................................867
6.6.1 Description of Pcs7AnIn.............................................................................................................867
6.6.2 Pcs7AnIn modes........................................................................................................................869
6.6.3 Pcs7AnIn functions ....................................................................................................................869
6.6.4 Pcs7AnIn error handling ............................................................................................................874
6.6.5 Pcs7AnIn messaging .................................................................................................................875
6.6.6 Pcs7AnIn I/Os ............................................................................................................................875
6.6.7 Pcs7AnIn block diagram ............................................................................................................878
6.7 Pcs7AnOu - Analog output driver ..............................................................................................879
6.7.1 Description of Pcs7AnOu...........................................................................................................879
6.7.2 Pcs7AnOu modes ......................................................................................................................881
6.7.3 Pcs7AnOu functions ..................................................................................................................882
6.7.4 Pcs7AnOu error handling...........................................................................................................884
6.7.5 Pcs7AnOu messaging ...............................................................................................................885
6.7.6 Pcs7AnOu I/Os ..........................................................................................................................885
6.7.7 Pcs7AnOu block diagram ..........................................................................................................888

Table of contents
6.8 Pcs7DiIn - Digital input driver.................................................................................................... 889

6.8.1 Description of Pcs7DiIn............................................................................................................. 889
6.8.2 Pcs7DiIn modes ........................................................................................................................ 891
6.8.3 Pcs7DiIn functions .................................................................................................................... 891
6.8.4 Pcs7DiIn error handling............................................................................................................. 893
6.8.5 Pcs7DiIn messaging ................................................................................................................. 893
6.8.6 Pcs7DiIn I/Os ............................................................................................................................ 894
6.8.7 Pcs7DiIn block diagram ............................................................................................................ 896
6.9 Pcs7DiIT - Digital input driver with time stamp ......................................................................... 897
6.9.1 Description of Pcs7DiIT............................................................................................................. 897
6.9.2 Pcs7DiIT modes........................................................................................................................ 899
6.9.3 Pcs7DiIT functions .................................................................................................................... 899
6.9.4 Pcs7DiIT error handling ............................................................................................................ 901
6.9.5 Pcs7DiIT messaging ................................................................................................................. 901
6.9.6 Pcs7DiIT I/Os ............................................................................................................................ 902
6.9.7 Pcs7DiIT block diagram ............................................................................................................ 904
6.10 Pcs7DiOu - Digital output driver................................................................................................ 905
6.10.1 Description of Pcs7DiOu ........................................................................................................... 905
6.10.2 Pcs7DiOu modes ...................................................................................................................... 907
6.10.3 Pcs7DiOu functions................................................................................................................... 907
6.10.4 Pcs7DiOu error handling........................................................................................................... 909
6.10.5 Pcs7DiOu messaging................................................................................................................ 910
6.10.6 Pcs7DiOu I/Os .......................................................................................................................... 910
6.10.7 Pcs7DiOu block diagram........................................................................................................... 912
6.11 Annex for channel blocks .......................................................................................................... 913
6.11.1 Mode Settings for SM Modules................................................................................................. 913
6.11.2 Mode settings for PA field devices............................................................................................ 920
6.11.3 Mode settings for FF field devices ............................................................................................ 921
7 Conversion blocks ................................................................................................................................. 923
7.1 StruAnIn - separating an analog structured variable ................................................................ 923
7.1.1 Description of StruAnIn ............................................................................................................. 923
7.1.2 StruAnIn modes ........................................................................................................................ 924
7.1.3 StruAnIn functions..................................................................................................................... 924
7.1.4 StruAnIn error handling ............................................................................................................. 925
7.1.5 StruAnIn messaging.................................................................................................................. 925
7.1.6 StruAnIn I/Os............................................................................................................................. 926
7.1.7 StruAnIn block diagram............................................................................................................. 927
7.2 StruAnOu - creating an analog structured variable................................................................... 928
7.2.1 Description of StruAnOu ........................................................................................................... 928
7.2.2 StruAnOu modes....................................................................................................................... 929
7.2.3 StruAnOu functions ................................................................................................................... 929
7.2.4 StruAnOu error handling ........................................................................................................... 930
7.2.5 StruAnOu messaging ................................................................................................................ 930
7.2.6 StruAnOu I/Os........................................................................................................................... 931
7.2.7 StruAnOu block diagram ........................................................................................................... 932

Table of contents
7.3 StruDiIn - separating a digital structured variable......................................................................933

7.3.1 Description of StruDiIn ...............................................................................................................933
7.3.2 StruDiIn modes ..........................................................................................................................934
7.3.3 StruDiIn functions.......................................................................................................................934
7.3.4 StruDiIn error handling...............................................................................................................935
7.3.5 StruDiIn messaging....................................................................................................................935
7.3.6 StruDiIn I/Os...............................................................................................................................936
7.3.7 StruDiIn block diagram...............................................................................................................937
7.4 StruDiOu - creating a digital structured variable ........................................................................938
7.4.1 Description of StruDiOu .............................................................................................................938
7.4.2 StruDiOu modes ........................................................................................................................939
7.4.3 StruDiOu functions.....................................................................................................................939
7.4.4 StruDiOu error handling .............................................................................................................940
7.4.5 StruDiOu messaging..................................................................................................................940
7.4.6 StruDiOu I/Os.............................................................................................................................941
7.4.7 StruDiOu block diagram.............................................................................................................942
7.5 StruScIn - separating a display area into two variables.............................................................943
7.5.1 Description of StruScIn ..............................................................................................................943
7.5.2 StruScIn modes .........................................................................................................................944
7.5.3 StruScIn functions......................................................................................................................944
7.5.4 StruScIn error handling ..............................................................................................................945
7.5.5 StruScIn messaging...................................................................................................................945
7.5.6 StruScIn I/Os..............................................................................................................................946
7.5.7 StruScIn block diagram..............................................................................................................947
7.6 StruScOu - merging two variables into a display area...............................................................948
7.6.1 Description of StruScOu ............................................................................................................948
7.6.2 StruScOu modes........................................................................................................................949
7.6.3 StruScOu functions ....................................................................................................................949
7.6.4 StruScOu error handling ............................................................................................................950
7.6.5 StruScOu messaging .................................................................................................................950
7.6.6 StruScOu I/Os ............................................................................................................................951
7.6.7 StruScOu block diagram ............................................................................................................952
7.7 STIn - separating the signal status into individual binary displays ............................................953
7.7.1 Description of STIn ....................................................................................................................953
7.7.2 STIn modes................................................................................................................................954
7.7.3 STIn functions ............................................................................................................................954
7.7.4 STIn error handling ....................................................................................................................955
7.7.5 STIn messaging .........................................................................................................................955
7.7.6 STIn I/Os ....................................................................................................................................956
7.7.7 STIn block diagram ....................................................................................................................957
7.8 STOu - merging individual binary signals into a signal status ...................................................958
7.8.1 Description of STOu...................................................................................................................958
7.8.2 STOu modes ..............................................................................................................................959
7.8.3 STOu functions ..........................................................................................................................959
7.8.4 STOu error handling ..................................................................................................................960
7.8.5 STOu messaging .......................................................................................................................960
7.8.6 STOu I/Os ..................................................................................................................................961
7.8.7 STOu block diagram ..................................................................................................................962

Table of contents
7.9 MSTIn - separating the maintenance status into individual status displays ............................. 963
7.9.1 Description of MSTIn................................................................................................................. 963
7.9.2 MSTIn modes............................................................................................................................ 964
7.9.3 MSTIn functions ........................................................................................................................ 964
7.9.4 MSTIn error handling ................................................................................................................ 965
7.9.5 MSTIn messaging ..................................................................................................................... 965
7.9.6 MSTIn I/Os ................................................................................................................................ 966
7.9.7 MSTIn block diagram ................................................................................................................ 967
7.10 MSTOu - merging individual status displays into a maintenance status .................................. 968
7.10.1 Description of MSTOu............................................................................................................... 968
7.10.2 MSTOu modes .......................................................................................................................... 969
7.10.3 MSTOu functions ...................................................................................................................... 969
7.10.4 MSTOu error handling............................................................................................................... 970
7.10.5 MSTOu messaging ................................................................................................................... 970
7.10.6 MSTOu I/Os .............................................................................................................................. 971
7.10.7 MSTOu block diagram .............................................................................................................. 972
8 Message blocks ..................................................................................................................................... 973
8.1 Event - Creating messages....................................................................................................... 973
8.1.1 Description of Event .................................................................................................................. 973
8.1.2 Event modes ............................................................................................................................. 976
8.1.3 Event functions.......................................................................................................................... 977
8.1.4 Event error handling.................................................................................................................. 979
8.1.5 Event messaging....................................................................................................................... 980
8.1.6 Event I/Os.................................................................................................................................. 982
8.1.7 Event block diagram.................................................................................................................. 986
8.2 EventNck - Generating messages without acknowledgment.................................................... 987
8.2.1 Description of EventNck............................................................................................................ 987
8.2.2 EventNck modes ....................................................................................................................... 990
8.2.3 EventNck functions ................................................................................................................... 991
8.2.4 EventNck error handling............................................................................................................ 993
8.2.5 EventNck messaging ................................................................................................................ 994
8.2.6 EventNck I/Os ........................................................................................................................... 996
8.2.7 EventNck block diagram ......................................................................................................... 1000
8.3 EventTs - Creating messages with time stamp....................................................................... 1001
8.3.1 Description of EventTs ............................................................................................................ 1001
8.3.2 EventTs modes ....................................................................................................................... 1004
8.3.3 EventTs functions.................................................................................................................... 1005
8.3.4 EventTs error handling............................................................................................................ 1007
8.3.5 EventTs messaging................................................................................................................. 1008
8.3.6 EventTs I/Os ........................................................................................................................... 1010
8.3.7 EventTs block diagram............................................................................................................ 1015

Table of contents
9 Dosing blocks ...................................................................................................................................... 1017

9.1 DoseL - Dosing device.............................................................................................................1017
9.1.1 Description of DoseL................................................................................................................1017
9.1.2 DoseL modes ...........................................................................................................................1021
9.1.3 DoseL functions .......................................................................................................................1023
9.1.4 DoseL error handling ...............................................................................................................1034
9.1.5 DoseL messaging ....................................................................................................................1036
9.1.6 DoseL I/Os ...............................................................................................................................1039
9.1.7 DoseL block diagram ...............................................................................................................1053
9.1.8 Operator control and monitoring ..............................................................................................1053
9.1.8.1 Views of DoseL ........................................................................................................................1053
9.1.8.2 DoseL standard view ...............................................................................................................1054
9.1.8.3 DoseL limit value view .............................................................................................................1058
9.1.8.4 DoseL parameter view .............................................................................................................1060
9.1.8.5 Flow setpoint view of DoseL ....................................................................................................1062
9.1.8.6 Quantity setpoint view of DoseL ..............................................................................................1064
9.1.8.7 DoseL preview .........................................................................................................................1066
9.1.8.8 Block symbol for DoseL ...........................................................................................................1069
10 Mathematical blocks ............................................................................................................................ 1071
10.1 Add04 - Adder with 4 values ....................................................................................................1071
10.1.1 Description of Add04................................................................................................................1071
10.1.2 Add04 modes ...........................................................................................................................1073
10.1.3 Add04 functions .......................................................................................................................1073
10.1.4 Add04 error handling ...............................................................................................................1074
10.1.5 Add04 messaging ....................................................................................................................1074
10.1.6 Add04 I/Os ...............................................................................................................................1075
10.1.7 Add04 block diagram ...............................................................................................................1076
10.2 Add08 - Adder with 8 values ....................................................................................................1077
10.2.1 Description of Add08................................................................................................................1077
10.2.2 Add08 modes ...........................................................................................................................1079
10.2.3 Add08 functions .......................................................................................................................1079
10.2.4 Add08 error handling ...............................................................................................................1080
10.2.5 Add08 messaging ....................................................................................................................1080
10.2.6 Add08 I/Os ...............................................................................................................................1081
10.2.7 Add08 block diagram ...............................................................................................................1082
10.3 Average - mean value calculation............................................................................................1083
10.3.1 Description of Average.............................................................................................................1083
10.3.2 Average modes ........................................................................................................................1084
10.3.3 Average functions ....................................................................................................................1085
10.3.4 Average error handling ............................................................................................................1086
10.3.5 Average messaging .................................................................................................................1087
10.3.6 Average I/Os ............................................................................................................................1088
10.3.7 Average block diagram ............................................................................................................1089
10.4 DeadTime - delayed signal output ...........................................................................................1090
10.4.1 Description of DeadTime .........................................................................................................1090
10.4.2 DeadTime modes.....................................................................................................................1093
10.4.3 DeadTime functions .................................................................................................................1093
10.4.4 DeadTime error handling .........................................................................................................1094
10.4.5 DeadTime messaging ..............................................................................................................1095
10.4.6 DeadTime I/Os .........................................................................................................................1096
10.4.7 DeadTime block diagram .........................................................................................................1097

Table of contents
10.5 Derivative - Obtaining a derivative .......................................................................................... 1098

10.5.1 Description of Derivative ......................................................................................................... 1098
10.5.2 Derivative modes .................................................................................................................... 1099
10.5.3 Derivative functions................................................................................................................. 1100
10.5.4 Derivative error handling ......................................................................................................... 1101
10.5.5 Derivative messaging.............................................................................................................. 1102
10.5.6 Derivative I/Os......................................................................................................................... 1103
10.5.7 Derivative block diagram......................................................................................................... 1104
10.6 Div02 - division of two values.................................................................................................. 1105
10.6.1 Description of Div02 ................................................................................................................ 1105
10.6.2 Div02 modes ........................................................................................................................... 1107
10.6.3 Div02 functions........................................................................................................................ 1107
10.6.4 Div02 error handling................................................................................................................ 1108
10.6.5 Div02 messaging..................................................................................................................... 1108
10.6.6 Div02 I/Os................................................................................................................................ 1109
10.6.7 Div02 block diagram................................................................................................................ 1111
10.7 Integral - Generating a time integral ....................................................................................... 1112
10.7.1 Description of Integral ............................................................................................................. 1112
10.7.2 Integral modes ........................................................................................................................ 1114
10.7.3 Integral functions..................................................................................................................... 1115
10.7.4 Integral error handling ............................................................................................................. 1117
10.7.5 Integral messaging.................................................................................................................. 1118
10.7.6 Integral I/Os............................................................................................................................. 1118
10.7.7 Integral block diagram............................................................................................................. 1120
10.8 Lag - Low-pass filter................................................................................................................ 1121
10.8.1 Description of Lag ................................................................................................................... 1121
10.8.2 Lag modes .............................................................................................................................. 1123
10.8.3 Lag functions........................................................................................................................... 1124
10.8.4 Lag error handling ................................................................................................................... 1125
10.8.5 Lag messaging........................................................................................................................ 1126
10.8.6 Lag I/Os................................................................................................................................... 1126
10.8.7 Lag block diagram................................................................................................................... 1127
10.9 MeanTime - Averaging............................................................................................................ 1128
10.9.1 Description of MeanTime ........................................................................................................ 1128
10.9.2 MeanTime modes ................................................................................................................... 1129
10.9.3 MeanTime functions................................................................................................................ 1130
10.9.4 MeanTime error handling ........................................................................................................ 1131
10.9.5 MeanTime messaging............................................................................................................. 1132
10.9.6 MeanTime I/Os........................................................................................................................ 1132
10.9.7 MeanTime block diagram........................................................................................................ 1133
10.10 Mul04 - Multiplier with 4 values............................................................................................... 1134
10.10.1 Description of Mul04 ............................................................................................................... 1134
10.10.2 Mul04 modes........................................................................................................................... 1135
10.10.3 Mul04 functions ....................................................................................................................... 1136
10.10.4 Mul04 error handling ............................................................................................................... 1136
10.10.5 Mul04 messaging .................................................................................................................... 1137
10.10.6 Mul04 I/Os ............................................................................................................................... 1137
10.10.7 Mul04 block diagram ............................................................................................................... 1138

Table of contents
10.11 Mul08 - Multiplier with 8 values................................................................................................1139

10.11.1 Description of Mul08 ................................................................................................................1139
10.11.2 Mul08 modes............................................................................................................................1140
10.11.3 Mul08 functions ........................................................................................................................1141
10.11.4 Mul08 error handling ................................................................................................................1141
10.11.5 Mul08 messaging.....................................................................................................................1142
10.11.6 Mul08 I/Os................................................................................................................................1142
10.11.7 Mul08 block diagram................................................................................................................1144
10.12 Polygon - Converting the first signal (non-linear).....................................................................1145
10.12.1 Description of Polygon .............................................................................................................1145
10.12.2 Polygon modes ........................................................................................................................1147
10.12.3 Polygon functions.....................................................................................................................1148
10.12.4 Polygon error handling.............................................................................................................1149
10.12.5 Polygon messaging..................................................................................................................1149
10.12.6 Polygon I/Os.............................................................................................................................1150
10.12.7 Polygon block diagram.............................................................................................................1153
10.13 Smooth - low pass filter............................................................................................................1155
10.13.1 Description of Smooth..............................................................................................................1155
10.13.2 Smooth modes .........................................................................................................................1156
10.13.3 Smooth functions .....................................................................................................................1157
10.13.4 Smooth error handling .............................................................................................................1158
10.13.5 Smooth messaging ..................................................................................................................1159
10.13.6 Smooth I/Os .............................................................................................................................1159
10.13.7 Smooth block diagram .............................................................................................................1160
10.14 Sub02 - subtracting two values................................................................................................1161
10.14.1 Description of Sub02................................................................................................................1161
10.14.2 Sub02 modes ...........................................................................................................................1162
10.14.3 Sub02 functions .......................................................................................................................1163
10.14.4 Sub02 error handling ...............................................................................................................1163
10.14.5 Sub02 messaging ....................................................................................................................1164
10.14.6 Sub02 I/Os ...............................................................................................................................1165
10.14.7 Sub02 block diagram ...............................................................................................................1166
11 Interlock blocks.................................................................................................................................... 1167
11.1 Intlk02 - Interlock display with 2 input signals..........................................................................1167
11.1.1 Description of Intlk02 ...............................................................................................................1167
11.1.2 Intlk02 modes...........................................................................................................................1170
11.1.3 Intlk02 functions .......................................................................................................................1171
11.1.4 Intlk02 error handling ...............................................................................................................1173
11.1.5 Intlk02 messaging ....................................................................................................................1174
11.1.6 Intlk02 I/Os ...............................................................................................................................1174
11.1.7 Intlk02 block diagram ...............................................................................................................1177
11.1.8.1 Views of interlock blocks..........................................................................................................1177
11.2 Intlk04 - Interlock display with 4 input signals..........................................................................1178
11.2.1 Description of Intlk04 ...............................................................................................................1178
11.2.2 Intlk04 modes...........................................................................................................................1181
11.2.3 Intlk04 functions .......................................................................................................................1181
11.2.4 Intlk04 error handling ...............................................................................................................1184
11.2.5 Intlk04 messaging ....................................................................................................................1185
11.2.6 Intlk04 I/Os ...............................................................................................................................1185
11.2.7 Intlk04 block diagram ...............................................................................................................1188

Table of contents
11.2.8 Operator control and monitoring ............................................................................................. 1188

11.2.8.1 Views of interlock blocks ......................................................................................................... 1188
11.3 Intlk08 - Interlock display with 8 input signals ......................................................................... 1189
11.3.1 Description of Intlk08............................................................................................................... 1189
11.3.2 Intlk08 modes.......................................................................................................................... 1192
11.3.3 Intlk08 functions ...................................................................................................................... 1193
11.3.4 Intlk08 error handling .............................................................................................................. 1195
11.3.5 Intlk08 messaging ................................................................................................................... 1196
11.3.6 Intlk08 I/Os .............................................................................................................................. 1196
11.3.7 Intlk08 block diagram .............................................................................................................. 1201
11.4 Intlk16 - Interlock display with 16 input signals ....................................................................... 1202
11.4.1 Description of Intlk16............................................................................................................... 1202
11.4.2 Intlk16 modes.......................................................................................................................... 1207
11.4.3 Intlk16 functions ...................................................................................................................... 1207
11.4.4 Intlk16 error handling .............................................................................................................. 1210
11.4.5 Intlk16 messaging ................................................................................................................... 1210
11.4.6 Intlk16 I/Os .............................................................................................................................. 1211
11.4.7 Intlk16 block diagram .............................................................................................................. 1217
12 Monitoring blocks................................................................................................................................. 1219
12.1 AV - displaying and monitoring additional value ..................................................................... 1219
12.1.1 Description of AV .................................................................................................................... 1219
12.1.2 AV modes................................................................................................................................ 1221
12.1.3 AV functions ............................................................................................................................ 1221
12.1.4 AV error handling .................................................................................................................... 1223
12.1.5 AV messaging ......................................................................................................................... 1224
12.1.6 AV I/Os .................................................................................................................................... 1226
12.1.7 AV block diagram .................................................................................................................... 1228
12.2 MonAnL - Monitoring of an analog process tag ...................................................................... 1229
12.2.1 Description of MonAnL............................................................................................................ 1229
12.2.2 MonAnL modes ....................................................................................................................... 1232
12.2.3 MonAnL functions ................................................................................................................... 1233
12.2.4 MonAnL error handling............................................................................................................ 1238
12.2.5 MonAnL messaging ................................................................................................................ 1239
12.2.6 MonAnL I/Os ........................................................................................................................... 1242
12.2.7 MonAnL block diagram ........................................................................................................... 1247
12.2.8.1 Views of MonAnL .................................................................................................................... 1248
12.2.8.2 MonAnL standard view............................................................................................................ 1249
12.2.8.3 MonAnL limit value view.......................................................................................................... 1252
12.2.8.4 MonAnL parameter view ......................................................................................................... 1254
12.2.8.5 MonAnL preview ..................................................................................................................... 1255
12.2.8.6 Block symbol for MonAnL ....................................................................................................... 1256
12.3 MonDiL - Monitoring of a digital process tag........................................................................... 1258
12.3.1 Description of MonDiL............................................................................................................. 1258
12.3.2 MonDiL modes ........................................................................................................................ 1262
12.3.3 MonDiL functions .................................................................................................................... 1263
12.3.4 MonDiL error handling............................................................................................................. 1266
12.3.5 MonDiL messaging ................................................................................................................. 1267

Table of contents
12.3.6 MonDiL I/Os .............................................................................................................................1269

12.3.7 MonDiL block diagram .............................................................................................................1272
12.3.8.1 Views of MonDiL ......................................................................................................................1272
12.3.8.2 MonDiL standard view .............................................................................................................1273
12.3.8.3 MonDiL parameter view ...........................................................................................................1275
12.3.8.4 MonDiL preview .......................................................................................................................1277
12.3.8.5 Block symbol for MonDiL .........................................................................................................1278
12.4 MonDi08 - Monitoring 8 digital process tags............................................................................1279
12.4.1 Description of MonDi08............................................................................................................1279
12.4.2 MonDi08 modes.......................................................................................................................1282
12.4.3 MonDi08 functions ...................................................................................................................1283
12.4.4 MonDi08 error handling ...........................................................................................................1285
12.4.5 MonDi08 messaging ................................................................................................................1286
12.4.6 MonDi08 I/Os ...........................................................................................................................1288
12.4.7 MonDi08 block diagram ...........................................................................................................1291
12.4.8.1 Views of MonDi08 ....................................................................................................................1292
12.4.8.2 MonDi08 standard view ...........................................................................................................1293
12.4.8.3 MonDi08 parameter view .........................................................................................................1294
12.4.8.4 MonDi08 preview .....................................................................................................................1296
12.4.8.5 Block symbol for MonDi08 .......................................................................................................1297
13 Counter blocks..................................................................................................................................... 1299
13.1 CountScL - Counter with up and down counting direction.......................................................1299
13.1.1 Description of CountScL ..........................................................................................................1299
13.1.2 CountScL modes .....................................................................................................................1304
13.1.3 CountScL functions..................................................................................................................1305
13.1.4 CountScL error handling ..........................................................................................................1308
13.1.5 CountScL messaging...............................................................................................................1309
13.1.6 CountScL I/Os..........................................................................................................................1311
13.1.7 CountScL block diagram..........................................................................................................1314
13.1.8.1 Views of CountScL...................................................................................................................1315
13.1.8.2 CountScL standard view ..........................................................................................................1316
13.1.8.3 CountScL limit value view ........................................................................................................1318
13.1.8.4 CountScL parameter view........................................................................................................1319
13.1.8.5 CountScL preview....................................................................................................................1320
13.1.8.6 Block icon for CountScL...........................................................................................................1321
13.2 CountOh - determining runtime................................................................................................1322
13.2.1 Description of CountOh............................................................................................................1322
13.2.2 CountOh modes.......................................................................................................................1327
13.2.3 CountOh functions ...................................................................................................................1328
13.2.4 CountOh error handling ...........................................................................................................1331
13.2.5 CountOh messaging ................................................................................................................1332
13.2.6 CountOh I/Os ...........................................................................................................................1334
13.2.7 CountOh block diagram ...........................................................................................................1339
13.2.8.1 Views of CountOh ....................................................................................................................1339
13.2.8.2 CountOh standard view ...........................................................................................................1340
13.2.8.3 CountOh limit value view .........................................................................................................1342
13.2.8.4 CountOh parameter view .........................................................................................................1343
13.2.8.5 CountOh preview .....................................................................................................................1345
13.2.8.6 Block icon for CountOh ............................................................................................................1346

Table of contents
14 Logical analog blocks .......................................................................................................................... 1347

14.1 Limit - Limiting an analog value .............................................................................................. 1347
14.1.1 Description of Limit.................................................................................................................. 1347
14.1.2 Limit modes ............................................................................................................................. 1350
14.1.3 Limit functions ......................................................................................................................... 1350
14.1.4 Limit error handling ................................................................................................................. 1351
14.1.5 Limit messaging ...................................................................................................................... 1351
14.1.6 Limit I/Os ................................................................................................................................. 1352
14.1.7 Limit block diagram ................................................................................................................. 1353
14.2 MuxAn03 - Selection of an analog value to increase availability / certainty ........................... 1354
14.2.1 Description of MuxAn03 .......................................................................................................... 1354
14.2.2 MuxAn03 modes ..................................................................................................................... 1355
14.2.3 MuxAn03 functions.................................................................................................................. 1355
14.2.4 MuxAn03 error handling.......................................................................................................... 1357
14.2.5 MuxAn03 messaging............................................................................................................... 1357
14.2.6 MuxAn03 I/Os ......................................................................................................................... 1358
14.2.7 MuxAn03 block diagram.......................................................................................................... 1359
14.3 RateLim - Signal ramp ............................................................................................................ 1360
14.3.1 Description of RateLim............................................................................................................ 1360
14.3.2 RateLim modes ....................................................................................................................... 1361
14.3.3 RateLim functions ................................................................................................................... 1362
14.3.4 RateLim error handling............................................................................................................ 1364
14.3.5 RateLim messaging ................................................................................................................ 1365
14.3.6 RateLim I/Os ........................................................................................................................... 1365
14.3.7 RateLim block diagram ........................................................................................................... 1367
14.4 SelA02In - Output of two analog values.................................................................................. 1368
14.4.1 Description of SelA02In........................................................................................................... 1368
14.4.2 SelA02In modes...................................................................................................................... 1370
14.4.3 SelA02In functions .................................................................................................................. 1370
14.4.4 SelA02In error handling .......................................................................................................... 1372
14.4.5 SelA02In messaging ............................................................................................................... 1372
14.4.6 SelA02In I/Os .......................................................................................................................... 1373
14.4.7 SelA02In block diagram .......................................................................................................... 1374
14.5 SelA16In - Output of 16 analog values ................................................................................... 1375
14.5.1 Description of SelA16In........................................................................................................... 1375
14.5.2 SelA16In modes...................................................................................................................... 1377
14.5.3 SelA16In functions .................................................................................................................. 1378
14.5.4 SelA16In error handling .......................................................................................................... 1380
14.5.5 SelA16In messaging ............................................................................................................... 1381
14.5.6 SelA16In I/Os .......................................................................................................................... 1381
14.5.7 SelA16In block diagram .......................................................................................................... 1385
14.5.8.1 Views of SelA16In ................................................................................................................... 1386
14.5.8.2 SelA16In standard view .......................................................................................................... 1387
14.5.8.3 SelA16In preview .................................................................................................................... 1389
14.5.8.4 Block icon for SelA16In ........................................................................................................... 1391

Table of contents
15 Logical digital blocks............................................................................................................................ 1393

15.1 And04 - Forming an AND signal from 4 binary input signals...................................................1393
15.1.1 Description of And04................................................................................................................1393
15.1.2 And04 modes ...........................................................................................................................1394
15.1.3 And04 functions .......................................................................................................................1394
15.1.4 And04 error handling ...............................................................................................................1395
15.1.5 And04 messaging ....................................................................................................................1395
15.1.6 And04 I/Os ...............................................................................................................................1396
15.1.7 And04 block diagram ...............................................................................................................1397
15.2 And08 - Forming an AND signal from 8 binary input signals...................................................1398
15.2.1 Description of And08................................................................................................................1398
15.2.2 And08 modes ...........................................................................................................................1399
15.2.3 And08 functions .......................................................................................................................1399
15.2.4 And08 error handling ...............................................................................................................1400
15.2.5 And08 messaging ....................................................................................................................1400
15.2.6 And08 I/Os ...............................................................................................................................1401
15.2.7 And08 block diagram ...............................................................................................................1402
15.3 Or04 - Forming an OR signal from 4 binary input signals .......................................................1403
15.3.1 Description of Or04 ..................................................................................................................1403
15.3.2 Or04 modes .............................................................................................................................1405
15.3.3 Or04 functions..........................................................................................................................1405
15.3.4 Or04 error handling..................................................................................................................1406
15.3.5 Or04 messaging.......................................................................................................................1406
15.3.6 Or04 I/Os..................................................................................................................................1407
15.3.7 Or04 block diagram..................................................................................................................1408
15.4 Or08 - Forming an OR signal from 8 binary input signals .......................................................1409
15.4.1 Description of Or08 ..................................................................................................................1409
15.4.2 Or08 modes .............................................................................................................................1410
15.4.3 Or08 functions..........................................................................................................................1411
15.4.4 Or08 error handling..................................................................................................................1411
15.4.5 Or08 messaging.......................................................................................................................1412
15.4.6 Or08 I/Os..................................................................................................................................1413
15.4.7 Or08 block diagram..................................................................................................................1414
15.5 Not01 - Inversion of an input signal .........................................................................................1415
15.5.1 Description of Not01 ................................................................................................................1415
15.5.2 Not01 modes............................................................................................................................1416
15.5.3 Not01 functions ........................................................................................................................1416
15.5.4 Not01 error handling ................................................................................................................1417
15.5.5 Not01 messaging .....................................................................................................................1417
15.5.6 Not01 I/Os ................................................................................................................................1418
15.5.7 Not01 block diagram ................................................................................................................1419

Table of contents
16 Maintenance blocks ............................................................................................................................. 1421

16.1 MuxMST - Determination of the worst maintenance status .................................................... 1421
16.1.1 Description of MuxMST........................................................................................................... 1421
16.1.2 MuxMST modes ...................................................................................................................... 1422
16.1.3 MuxMST functions .................................................................................................................. 1422
16.1.4 MuxMST error handling........................................................................................................... 1423
16.1.5 MuxMST messaging ............................................................................................................... 1423
16.1.6 MuxMST I/Os .......................................................................................................................... 1424
16.1.7 MuxMST block diagram .......................................................................................................... 1425
16.2 MuxST- Determination of the worst signal status ................................................................... 1426
16.2.1 Description of MuxST.............................................................................................................. 1426
16.2.2 MuxST modes ......................................................................................................................... 1427
16.2.3 MuxST functions ..................................................................................................................... 1427
16.2.4 MuxST error handling.............................................................................................................. 1428
16.2.5 MuxST messaging .................................................................................................................. 1428
16.2.6 MuxST I/Os ............................................................................................................................. 1429
16.2.7 MuxST block diagram ............................................................................................................. 1430
17 System blocks...................................................................................................................................... 1431
17.1 AddInt64 - Addition of two 64-bit integer variables ................................................................. 1431
17.1.1 Description of AddInt64........................................................................................................... 1431
17.2 AddR64 - Addition of two 64-bit REAL variables .................................................................... 1432
17.2.1 Description of AddR64 ............................................................................................................ 1432
17.3 DiToInt64 - Converting from DINT to Int64 ............................................................................. 1432
17.3.1 Description of DiToInt64.......................................................................................................... 1432
17.4 Int64ToDi - Converting from Int64 to DINT ............................................................................. 1433
17.4.1 Description of Int64ToDi.......................................................................................................... 1433
17.5 NegInt64 - Negation of an Int64 variable ................................................................................ 1433
17.5.1 Description of NegInt64........................................................................................................... 1433
17.6 NegR64 - Negation of a Real64 variable ................................................................................ 1434
17.6.1 Description of NegR64 ............................................................................................................ 1434
17.7 PIDCoefR - Calculation of coefficients.................................................................................... 1434
17.7.1 Description of PIDCoefR ......................................................................................................... 1434
17.8 R64ToReal - Converting Real64 to REAL .............................................................................. 1435
17.8.1 Description of R64ToReal ....................................................................................................... 1435
17.9 RealToR64 - Converting REAL to Real64 .............................................................................. 1435
17.9.1 Description of RealToR64 ....................................................................................................... 1435
17.10 SelST16 - Output of the best or worst signal status ............................................................... 1436
17.10.1 Description of SelST16 ........................................................................................................... 1436
17.11 ShLeInt64 - Left shift of an Int64 variable ............................................................................... 1436
17.11.1 Description of ShLeInt64......................................................................................................... 1436
17.12 ShRiInt64 - Right shift of an Int64 variable ............................................................................. 1437
17.12.1 Description of ShRiInt64 ......................................................................................................... 1437
17.13 PIDKernR - calculation of the manipulated variable ............................................................... 1437
17.13.1 Description of PIDKernR ......................................................................................................... 1437

Table of contents
18 PCS 7 Advanced Process Control Templates...................................................................................... 1439

18.1 Process tag types (insertible templates)..................................................................................1439
18.1.1 Introduction to process tag types.............................................................................................1439
18.1.2 PID controller (PIDConLean) ...................................................................................................1442
18.1.3 PID controller with safety logic and control loop monitoring (PIDConL_ConPerMon).............1442
18.1.4 PIDConR with safety logic and control loop monitoring (PIDConR_ConPerMon)...................1443
18.1.5 PID - control with operating-point-oriented parameter control (GainScheduling)....................1443
18.1.6 PID controller with dynamic feedforward control (FfwdDisturbCompensat) ............................1445
18.1.7 PID controller with Smith predictor (SmithPredictorControl)....................................................1448
18.1.8 Step controller with direct access to the actuator and without position feedback
(StepControlDirect) ..................................................................................................................1449
18.1.9 Step controller with assigned actuator block and position feedback (StepControlActor) ........1449
18.1.10 Split-range control....................................................................................................................1450
18.1.11 Ratio control .............................................................................................................................1452
18.1.12 Ratio control with PIDConR (RatioR).......................................................................................1453
18.1.13 Cascade control .......................................................................................................................1454
18.1.14 Cascade control with PIDConR (CascadeR) ...........................................................................1456
18.1.15 Source chart for GainSched function block (gain scheduling).................................................1456
18.1.16 Override control........................................................................................................................1457
18.1.17 Override control with PIDConR (OverrideR)............................................................................1459
18.1.18 Model-based predictive control (ModPreCon) .........................................................................1459
18.1.19 Monitoring of a digital process tag (DigitalMonitoring).............................................................1460
18.1.20 Monitoring eight digital process tags (Digital8Monitoring) .......................................................1460
18.1.21 Monitoring an analog process tag (AnalogMonitoring) ............................................................1461
18.1.22 Dosing (DoseLean) ..................................................................................................................1461
18.1.23 Motor (MotorLean) ...................................................................................................................1462
18.1.24 Two-speed motor (Motor2Speed) ............................................................................................1462
18.1.25 Reversing motor (MotorReversible) .........................................................................................1462
18.1.26 Reversing motor with controllable speed (MotorSpeedControlled) .........................................1463
18.1.27 Motor with an additional analog value and time-stamped signals (Motor_AV_EventTs).........1463
18.1.28 Valve (ValveLean)....................................................................................................................1465
18.1.29 Two-way valve (Valve2Way)....................................................................................................1465
18.1.30 Motor valve (ValveMotor).........................................................................................................1466
18.2 Example project APL_Example_xx ..........................................................................................1467
18.2.1 Introduction to the PCS 7 example project for Advanced Process Control .............................1467
18.2.2 Process simulation including noise generator .........................................................................1468
18.2.3 Cascade control of a temperature by using the heat flow .......................................................1470
18.2.4 Control loop monitoring with simulation of colored noise ........................................................1472
18.2.5 Feedforward control to compensate a measurable disturbance variable................................1473
18.2.6 Operating point-oriented adaptation of parameters (gain scheduling) for non-linear
processes.................................................................................................................................1474
18.2.7 Override control on a pipeline ..................................................................................................1474
18.2.8 Smith predicator for a dead time controlled system.................................................................1475
18.2.9 Filtering of noisy measured values in a control loop................................................................1475
18.2.10 Predictive control of a 2x2 multi-variable controlled system....................................................1476
18.2.11 Predictive control of a non-linear process................................................................................1477

Table of contents
19 Definitions............................................................................................................................................ 1479
19.1 Batch process ......................................................................................................................... 1479
19.2 Approximation ......................................................................................................................... 1479
19.3 Prediction horizon ................................................................................................................... 1479
19.4 Trajectory ................................................................................................................................ 1479
19.5 Maverick .................................................................................................................................. 1480
19.6 Ergodic process ...................................................................................................................... 1480
19.7 Conti process .......................................................................................................................... 1480
19.8 Multivariable controller ............................................................................................................ 1481
19.9 non-phase minimum................................................................................................................ 1481
Index.................................................................................................................................................... 1483

Basics of APL 1
1.1 Block modes
1.1.1 Overview of the modes
Overview of the individual modes

The available operating modes are assigned to the block families:
● Motors, valves and dosers
● Controllers
● Blocks without "Manual" and "Automatic" modes
You can find an overview below. Click on one of the operating modes to go directly to the
relevant detailed description.
You can find a status diagram for the operating modes (Page 39) at the end of this section.
Operating modes for motors, valves and dosers

The following operating modes are available:
1. Local mode (Page 36)
2. Automatic mode (Page 32)
3. Manual mode (Page 32)
4. Out of service (Page 27)
The mode with the lowest number in the list above has the highest priority. "Manual" and
"Automatic" modes have the same priority. General information on the individual modes is
available in the following sections. The sections also include block-specific information, for
example, non-standard parameter assignment. Refer to the description and function of the
relevant blocks.

Basics of APL
1.1 Block modes
Operating modes for controllers

1. Automatic mode (Page 29)
2. Manual mode (Page 29)
3. Program mode for closed-loop controllers (Page 34)
The mode with the lowest number has highest priority. "Manual" and "Automatic" modes
have the same priority. General information on the individual modes is available in the
following sections. The sections also include block-specific information, for example, non-
standard parameter assignment. Refer to the description and function of the relevant blocks.
Operating modes for blocks without "Manual" and "Automatic" operation

1. On (Page 27)
The mode with the lowest number has highest priority. General information on the individual
modes is available in the following sections. The sections also include block-specific
information, for example, non-standard parameter assignment. Refer to the description and
function of the relevant blocks.
Note
Please note that the operating modes are realized differently in the individual block families.

Basics of APL
1.1 Block modes
1.1.2 On
"On" operating mode

The "On" operating mode tells you that the block algorithm is being processed (output
parameter OnAct = 1). This mode is only present in the case of blocks that have
faceplates, but not the following, which have operating modes:
● Manual mode or
● Automatic mode or
● Local mode
The "On" mode can only be activated via a control on the faceplate (input parameter
OnOp = 1). The block must be in the "Out-of-service" operating mode for this to be possible.
1.1.3 Out of service
Using the "out of service" operating mode

The "Out of service" operating mode is available to all blocks that have an operating mode
changeover and a direct connection to the process (with a connection to a process tag, for
example).
It is intended for maintenance and service purposes (to replace the device, for example), as
all messages and functions of the block are switched off. The only function still possible is an
operating mode changeover.
All outputs for motors and valves are set to the safe position in this operating mode.
For controllers, the safety manipulated variable (high or low manual manipulated variable) is
only used if the Feature bit Safety value of the manipulated variable effective at startup
(Page 196) is active. Otherwise the manipulated variable remains at the latest value like all
the other output parameters.
Refer also to the Safe position for motors, valves and controllers (Page 120) section for more
on this.
The last value available is output permanently for all other blocks.
Requirement for the "out of service" mode

Prerequisite for switching to this operating mode is that the block is in "Manual mode" or
"On" mode.
Switching on the out of service operating mode by using the faceplate

The "Out of service" operating mode can only be switched on by using the faceplate when it
is in the standard block view (OosOp = 1 parameter) and even then, only if ModLiOp = 0.
To change over the operating mode by using the faceplate, please refer to the descriptions
relating to the standard view of the individual blocks.

Basics of APL
1.1 Block modes
Switching on the Out of service operating mode by using the interconnection

The "Out of service" operating mode is switched on by using the configurable parameter
OosLi = 1. This is only possible if the block was previously in manual mode or "on" mode
and the Feature bit Reaction to the out of service mode (Page 199) was set to 1.
Regardless of operating mode, the parameter view of the faceplate will always display the
status of the parameter OosLi =1 with the symbol for the status "In progress" (see table)
next to the Maintenance enable button.
Display Meaning
In progress
Refer also to the Maintenance release (Page 47) section for more on this.
Exiting the "Out of service" operating mode

From this operating mode, a block can only be switched by an operator action at the
faceplate into the following operating modes:
● "On"
● "Manual mode"

Basics of APL
1.1 Block modes
1.1.4 Manual and Automatic mode for control blocks
"Manual" and "Automatic" modes for control blocks

In "manual mode", the control settings for the device are made manually by the operator.
The operator decides how to change the block's manipulated variable (output signal). The
manipulated variable can be analog or binary.
In "automatic mode", the control settings for the controller are made automatically as
calculated by the block algorithm.
Changing between operating modes

The switchover between manual and automatic modes takes place as shown in the following
schematic:
6HOHFWLRQRIPDQXDODXWRPDWLFRSHUDWLQJPRGHZLWK
0RG/L2S 0RG/L2S
)DFHSODWH RU6)& &)&6)&
$XW0RG2S
0DQ0RG2S 0DQ0RG/L $XW0RG/L

$XW0RG/L 0DQ0RG/L
0DQXDOPRGH $XWRPDWLFPRGH
Switchover initiated in the faceplate (ModLiOp = 0): The changeover 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.

Basics of APL
1.1 Block modes
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 switch mode (requirement: Feature Bit 4 = 1, see
Setting switch or button mode (Page 195)) connection ManModLi is used exclusively.
If both signals (ManModLi =1, AutModLi = 1 ) are set, ManModLi = 1 has priority.
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).
Switchover from automatic mode to manual mode

When changing over from "automatic mode" to "manual mode", the last valid control settings
(Manipiulated Value MV) for the controller set in "automatic mode" remain valid until you
change the control settings manually.

Basics of APL
1.1 Block modes

The switchover from manual to automatic mode can take place with or without the internal
setpoint tracking the process value. You specify this behavior on the SP_TrkPV I/O, which
can also be operated from the faceplate in the parameter view (Option "SP = PV"). For the
blocks PIDConL and PIDStepL you can also change the behavior for the switchover via the
parameter Feature bit Disabling bumpless changeover to automatic mode for controllers
(Page 197):
● Switchover with internal setpoint tracking process variable (SP_TrkPV = 1) means that
in "Manual" mode the setpoint (SP) tracks the process variable (PV) (bumpless
switchover). After switching back to "Automatic" mode, the manipulated variable remains
constant until the setpoint value (SP) is changed or the process value (PV) changes.
● Switchover without internal setpoint tracking process variable (SP_TrkPV = 0) means
that the block immediately recalculates the value of the manipulated variable based on
the setpoint and process value (PV) when the mode is changed. The Feature parameter
is used to choose between the two variants:
– Switchover without P step (standard setting, Feature bit = 0):
During switchover, the I action of the controller is set in such a way that the switchover
is carried out without a P step (virtually bumpless referring to the manipulated
variable). A control deviation is only regulated via the I action.
– Switchover with P step (Feature bit = 1):
During switchover, the I action of the controller is set in such a way that the switchover
is carried out with a P step (not bumpless referring to the manipulated variable). A
control deviation is regulated via the P and the I action.
Note
Points to note about switchovers with a P step change:
• The P action must be active for the setting "Switchover with P step"
(PropSel = 1)
• If the P action is in the feedback (PropFacSP = 0), the "Switchover with P step"
setting has no effect.
• If the switchover function with the internal setpoint tracking the process variable is
active (SP_TrkPV = 1), the "Switchover with P step" setting has no effect.
Reaction of signals when operating mode is changed

Using the Feature bit Resetting the commands for changing the mode (Page 193), you can
choose whether the block automatically resets the signal for changing the operating mode.
Switch on program mode

A few control blocks allow you to operate in program mode. Please consult the section on
functions of the individual control blocks to find out whether a control block allows program
mode.
Please also refer to the section Program mode for closed-loop controllers (Page 34) for
information on program mode.

Basics of APL
1.1 Block modes
1.1.5 Manual and automatic mode for motors, valves and dosers
Manual and automatic mode for motors, valves and dosers

In "manual mode", the control settings for the device are made manually by the operator.
The operator decides how to change the block's manipulated variable (output signal). The
manipulated variable can be analog or binary in accordance with the function block.
In "automatic mode", the control settings for the device are made by the block algorithm via
interconnected inputs or inputs controlled by SFC.
Changing between operating modes

The switchover between "manual and automatic mode" takes place as shown in the
following schematic:
6HOHFWLRQRIPDQXDODXWRPDWLFRSHUDWLQJPRGHZLWK
0RG/L2S 0RG/L2S
)DFHSODWH RU6)& &)&6)&
$XW0RG2S
0DQ0RG2S 0DQ0RG/L $XW0RG/L

$XW0RG/L 0DQ0RG/L
0DQXDOPRGH $XWRPDWLFPRGH

Basics of APL
1.1 Block modes
Switchover using faceplates (ModLiOp = 0): The changeover 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 pushbutton operation. In switch mode (requirement: Feature Bit 4 = 1, see
Setting switch or button mode (Page 195)) connection AutModLi is used exclusively.
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).

When changing over from "automatic mode" to "manual mode", the last valid control settings
for the block set in "automatic mode" remain valid until you change the control settings
manually.
Switchover from manual to automatic mode

You can set the following options for changing over from "manual mode" to "automatic
mode" using the Feature bit Bumpless switchover to automatic mode (Page 197). Refer to
the I/O descriptions for the relevant block.
● A switchover from manual to automatic mode is possible at any time (standard setting,
Feature bit = 0). The control settings for the automatic mode become effective
immediately.
● Switchover from manual to automatic mode is only possible if the control settings for the
manual and automatic modes match (bumpless switchover), (Feature bit = 1). An error
message is output if they do not match. In this case, you will need to adapt the control
settings in "manual mode" to the control settings in "automatic mode".
Reaction of signals when operating mode is changed

Using the Feature bit Resetting the commands for changing the mode (Page 193), you can
choose whether the block automatically resets the signal for changing the operating mode.
Resetting the commands for the control settings

With the Feature bit Enabling resetting of commands for the control settings (Page 193),
you select how the block handles commands for the control settings (for example motor on)
via the interconnected input parameters.

Basics of APL
1.1 Block modes
1.1.6 Program mode for closed-loop controllers
Program mode for closed-loop controllers - interface for higher-level control functions
The interface for primary controller functions (external Advanced Control software package)
provides primary controller functions, which run on an external PC as an OPC client, the
option of using the control from the controller function block and specifying the setpoint or
manipulated variable from a remote location. This procedure is called program mode.
You can use the feature bit Enabling program mode (Page 192) to specify whether or not the
controller block is intended for program mode.
Program mode requires an enable signal (input parameter AdvCoEn = 1) from a central
control block. If this enable signal goes from 1 to 0, for example, due to errors in the OPC
communication, the controller block returns to the operating mode it had before program
mode.
You activate program mode in the standard view of the controller faceplate. In addition to
switching from manual to automatic mode, you are also given the option of using program
mode as the operating mode. You exit program mode by operator input or by switching back
into manual or automatic mode.
A 0-1 edge transition of the interconnectable input parameter AdvCoMstrOn activates
program mode depending on the conditions described below. You can use this to put an
entire group of downstream controller blocks into program mode at the same time from a
central control block. Both the input parameter AdvCoOn and the interconnectable input
parameter AdvCoMstrOn can be used at the same time, since the parameter
AdvCoMstrOn only reacts to edges of the binary signal.
Program mode is deactivated 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.

Basics of APL
1.1 Block modes
Selecting the type of program mode

There are two types of program mode:
● Program mode with setpoint (in automatic mode only)
● Program mode with setpoint (in manual mode only, not for step controllers without
position feedback)
Program mode with setpoint: If you set the input parameter AdvCoModSP = 1, the analog
value provided by the OPC client (AdvCoMV) is used as an external setpoint for the
controller. The controller and faceplate otherwise react as they do with automatic mode and
an external setpoint. Refer to section Setpoint input - internal and external (Page 96) for
more about this.
Requirements for program mode with setpoint:
● AdvCoModSP = 1,
● AdvCoEn = 1,
● The controller is in automatic mode.
Program mode with manipulated value: If you set the input parameter AdvCoModSP = 0,
the analog value provided by the OPC client (AdvCoMV) is used as an external manipulated
value for the controller. The algorithm of the PID controller is bypassed. The controller and
faceplate otherwise react as they do with tracking (MV_TrkOn = 1). Refer to section
Tracking and limiting a manipulated value (Page 111) for more about this.
Requirements for program mode with manipulated value:
● AdvCoModSP = 0,
● AdvCoEn = 1,
● The controller is in manual mode.
Note
Program mode with setpoint is not available for step controllers without position feedback
(available in PIDStepL, FmCont and FmTemp). ErrorNum = 50 is output on the control
block and the controller cannot switch into program mode (AdvCoAct=0).

Basics of APL
1.1 Block modes
1.1.7 Local mode
Areas of application for local mode

This operating mode is used for motors, valves and dosing units. The control settings are
made directly or via a control station that is located "locally". In addition, you can set different
control strategies with the parameter LocalSetting.
With LocalSetting = 0, you prevent a change to "local mode".
Changing to local mode

Changing to local mode is only possible from the manual and automatic operating modes.
The change to this mode is initiated by:
● An operation on the faceplate (input parameter LocalOp = 1, valid if
LocalSetting = 3 or LocalSetting = 4 and ModLiOp = 0) or
● The interconnected input parameter (LocalLi = 1, valid if LocalSetting = 1 or
LocalSetting = 2).
Exiting local mode

You leave local mode using:
● An operation on the faceplate (LocalSetting = 3 or LocalSetting = 4 and
ModLiOp = 0) or
● The interconnected input parameter (LocalSetting = 1 or LocalSetting = 2).
In order to exit local mode via the interconnected input parameter, you can configure
various reactions using a Feature bit Exiting local mode (Page 199).
Operator input in "local mode" using a faceplate

You are not permitted to functionally operate the block in local mode. You can only use the
faceplate to exit local mode if you have also activated "local mode" using the faceplate. The
rules you specified for exiting "local mode" apply here.

Basics of APL
1.1 Block modes
Input in "local mode" via interconnected inputs

In "local mode", the way the block functions is influenced via interconnected input
parameters according to the settings of the LocalSetting parameter. You have the
following options:
● LocalSetting = 1 and LocalSetting = 3
– The control settings for the block are adjusted (tracking) via an interconnected input
parameter. The interconnected input parameter includes the control signal for the local
operating station on the system.
– The runtime monitoring of the block is effective in accordance with your configuration.
– The configured interlocking functions of the block are activated in accordance with
input parameter BypProt = 0 or deactivated (BypProt = 1).
● LocalSetting = 2 and LocalSetting = 4
– The control settings for the block are made based on internal adjustment of the
feedback value.
– The configured runtime monitoring of the block is deactivated.
Note: The configured runtime monitoring is deactivated for motor feedback of the
VlvMotL motor valve. Opening and closing of the motor value continues to be
monitored.
– The configured interlock functions of the block are disabled.

Basics of APL
1.1 Block modes
Overview of behavior in local mode
LocalSetting = 0 1 2 3 4
Switch on operating Cannot be set CFC/SFC CFC/SFC Faceplate Faceplate
mode
Changing the - CFC/SFC CFC/SFC - -
operating mode:
Local mode/to
manual mode only
(Feature = 0)
Changing the - CFC/SFC CFC/SFC - -
operating mode:
Local mode/previous
mode
(Feature = 1)
Operating in the - Not supported Not supported Change the Change the
faceplate operating mode operating mode
only only
Tracking via an - Yes No Yes No
external input
Reaction of the block - Monitoring the Adjustment of the Monitoring the Adjustment of the
feedback value feedback value feedback value feedback value
Interlock activated - Yes: No Yes: No
(BypProt = 0) (BypProt = 0)
No: No:
(BypProt = 1) (BypProt = 1)

Basics of APL
1.1 Block modes
1.1.8 Status diagram for the operating modes
Status diagram for the operating modes
2XWRIVHUYLFH
0DQXDO
2Q

3URJUDP /RFDO
PRGH

$XWRPDWLF
Figure 1-1 Status diagram for the operating modes
* This operating mode is used for motors, valves, and dosing units.
** This operating mode is used for controllers only.

Basics of APL
1.1 Block modes
Number in Condition for status change

graphic (top)
(1) Manual (on) → Out of service
• Via faceplate (OosOp = 1) if ModLiOp = 0 or
• Via edge transition 0 → 1 of OosLi if Feature bit Reaction to the out of service
mode (Page 199) = 1
(2) Out of service → Manual (on)
• Via faceplate (ManModOp = 1)
(3) Local mode → Manual
• Via faceplate (ManModOp = 1) if ModLiOp = 0 and LocalSetting = 3 or
LocalSetting = 4 or
• Via LocalLi = 0 if LocalSetting = 1 or LocalSetting = 2. See section
Exiting local mode (Page 199) for more conditions.
(4) Automatic → Manual
• Via faceplate (ManModOp = 1) if ModLiOp = 0 or
• Via ManModLi = 1 if ModLiOp = 1 and Feature bit Setting switch or button
mode (Page 195) = 0 or
• Via AutModLi = 0 if ModLiOp = 1 and Feature bit Setting switch or button
mode (Page 195) = 1
(5) Manual → Automatic
• Via faceplate (AutModOp = 1) if ModLiOp = 0 or
• Via AutModLi = 1 if ModLiOp = 1
(6) Manual → Local mode
• Via faceplate (LocalOp = 1) if ModLiOp = 0 and LocalSetting = 3 or
LocalSetting = 4 or
• Via LocalLi = 1 if LocalSetting = 1 or LocalSetting = 2
(7) Automatic → Local mode
• Via faceplate (LocalOp = 1) if ModLiOp = 0 and LocalSetting = 3 or
LocalSetting = 4 or
• Via LocalLi = 1 if LocalSetting = 1 or LocalSetting = 2
(8) Local mode → Automatic
• Via faceplate (AutModOp = 1) if ModLiOp = 0 and LocalSetting = 3 or
LocalSetting = 4 or
• Via LocalLi = 0 if LocalSetting = 1 or LocalSetting = 2. See section
Exiting local mode (Page 199) for more conditions.
(9) Program mode → Automatic
• Via faceplate (AutModOp = 1) if ModLiOp = 0 or
• Via AutModLi = 1 if ModLiOp = 1 or
• Via edge transition 1 → 0 of AdvCoMstrOn if automatic is set before program
mode.
(10) Automatic → Program mode
Requirement for changeover in program mode: AdvCoEn = 1
• Via faceplate (AdvCoOn = 1) if ModLiOp = 0 or
• Via AdvCoMstrOn = 1

Basics of APL
1.1 Block modes
Number in Condition for status change

graphic (top)
(11) Manual → Program mode
Requirement for changeover from manual to program mode: AdvCoEn = 1 and
AdvCoModSP = 0
• Via faceplate (AdvCoOn = 1) if ModLiOp = 0 or
• Via AdvCoMstrOn = 1
(12) Program mode → Manual
• Via faceplate (ManModOp = 1) if ModLiOp = 0 or
• Edge transition 1 → 0 of AdvCoMstrOn if manual is set before program mode.

Basics of APL
1.2 General functions of the blocks
1.2.1 Operating, monitoring and reporting
1.2.1.1 Display and operator input area for process values and setpoints
Display and control field 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 range for limits (maximum 7 numbers possible in the faceplates)
The interconnectable input parameter is a structured variable that contains two analog
values. Please refer to the descriptions of the individual blocks for the relevant input
parameters.
Using a structured variable for scaling

There are three possibilities with which you can influence the contents of the structured
variables, namely with:
● The corresponding channel function block, for example, the FbAnIn block
● A conversion block, for example, the StruScIn block
● Direct parameter assignment at the block input
Additional information on data types is available in the documentation of CFC and STEP 7.

Basics of APL
1.2.1.2 Calling further faceplates
Opening additional faceplates

You can open standard views of other faceplates from various faceplate views. Here, you
have the following options:
● Two buttons that you can assign freely and that are used to call faceplates of other
blocks.
● Two predefined buttons for calling faceplates with a fixed assignment to the controller
blocks.
● Buttons predefined for interlock functions
Freely assignable buttons

From the standard view and from the preview, you can use a button to open the standard
view of a block that can be selected freely. In order to use this function, in the CFC you need
to interconnect the SelFp1 input parameter for the button in the standard view or SelFp2
for the button in the preview to any given output parameter of the block whose faceplate is to
be opened. This makes the buttons in the faceplates visible.
Button label
You can change button labels as follows:
● 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.
Predefined buttons for controller blocks

You can open the standard view for the following blocks from a controller standard view or
parameter view (for example PIDConL):
● ConPerMon (can be called from the standard view)
– To do this, you need to interconnect the output parameter CPI of the ConPerMon
block to the input parameter CPI_In of the controller block.
● GainSched (can be called from the parameter view)
– To do this, you need to interconnect the output parameter Link2Gain of the
GainSched block to the input parameter Gain of the controller block.
The labels of the buttons cannot be changed here.

Basics of APL
Predefined buttons for interlocks

You can open the following interlock blocks from the standard view of the technological
blocks:
● Activation enable
● Interlock without reset (interlock)
● Interlock with reset (protection)
The buttons intended for this are visible when the relevant input parameter (Permit,
Intlock or Protect) is interconnected to an interlock block.
You can open the standard view for the following faceplates from the standard view of the
interlock blocks:
● The blocks interconnected to the input values.
● The block interconnected to the output value.
The buttons intended for this are visible when the input parameters (for example In01) or
the Out output parameter of the interlock block is interconnected to a block that has a
faceplate.
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.

Basics of APL
1.2.1.3 Operator permissions
Operator control permissions for blocks

Four conditions apply to operator control permissions:
1. User administration in the PCS 7 OS:
The following operator control permissions are used in APL:
– Process controlling (for example manual /automatic mode changeover, changing
setpoints and manipulated variables).
With this operator control permission, operations can be performed in the standard
view of all blocks and input can be made in the memo view.
– Higher process controlling (for example, changing limits, controller parameters, and
monitoring times).
With this operator control permission, all operations in all views of all blocks are
possible, with the exception of those listed under "Highest process controlling".
– Highest process controlling (simulate process values and release of process tag for
maintenance).
With this operator control permission, simulation can be switched on and off in the
parameter view and the process tag for maintenance work can be released.
Exceptions to the operator control permissions described above are listed in the
descriptions of the individual views.
2. You can execute various functions depending on the block mode. These permissions are
stored in the block algorithm and are determined dynamically in online mode.
3. The block is either controlled by the operator or by the controller, depending on
parameter settings or on the interconnection. Manual mode can be changed to automatic
mode by the operator or by a master control system, for example. These permissions are
stored in the block algorithm and are determined dynamically in online mode.
4. Controllable blocks have the OS_Perm input parameter which allows you to implement
individual operator control strategies by setting the operator control permissions. A
pressure relief valve, for example, can only be opened by the master control system. The
operator may only close the valve. These authorizations are defined during configuration.
These operator control permissions are displayed in the preview view of the faceplate.
For information about setting the individual operator control permissions (OS_Perm)
please refer to the description of the functions of the individual blocks.
The relevant operator controls are enabled if the operator has suitable permissions. The
block algorithm processes the input data.

Basics of APL
1.2.1.4 Generating instance-specific messages
Generating instance-specific messages

● You can generate instance-specific messages for a binary signal of every block.
The number of interconnectable input parameters that can be used freely varies with relation
to the blocks. The X in the parameter name designates the position.
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 51)

Basics of APL
1.2.1.5 Maintenance release
Issuing a maintenance release

The maintenance release serves as information about a process tag at which maintenance,
service or calibration should be carried out. You can use the signal for maintenance release
to transfer the information about the enabling of a process tag from the OS to a Maintenance
Station.
Note
The block must be in either "Manual," "On" or "Out of service" mode to set the maintenance
release.
You set the maintenance release (operator control permission "System control" required) in
the parameter view using the input parameter MS_RelOp = 1. A maintenance release 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 technological block with the input
parameter MS_Releaseof the corresponding channel block.
The issuing of a maintenance release does not have any influence on the function of the
block. An operation message is generated.
Use of the state "In progress" on the Maintenance Station

The status "In progress" is implemented on the Maintenance Station for a process tag or a
field device using the channel blocks and the interconnectable output parameter
OosAct = 1. You can interconnect the output parameter OosAct of the channel block with
the input parameter OosLi of a technological block.
Use the Feature bit Reaction to the out of service mode (Page 199) to specify, in case the
input parameter is OosLi = 1, if:
● there is a changeover to the "out of service" mode and the symbol for the "In progress"
(see table) status is displayed. You can change to manual mode at any time.
● only the display "In progress" (see table) in the block icon and in the faceplate of the
assigned technological block is to be carried out.
Display Meaning
In progress

Basics of APL
Function sequence in the APL

● The OS operator issues the maintenance release (MS_RelOp = 1) in the technological
block's parameter view.
● The technological block then sets the MS_Release = 1 output parameter.
● The channel driver's MS_Rel input is now also 1.
● The channel driver signals the maintenance release to the diagnostic driver via the
DXCHG parameter.
● The maintenance release is only signaled to the Maintenance Station once all 0 bits of
the parameter DXCHG_XX are set on the diagnostic driver.
● The channel driver determines the "in progress" state of the Maintenance Station using
the MS input parameter and makes this information available at the OosAct output
parameter.

Basics of APL
● On the technological block, the "working" state is displayed at input parameter OosLi and
forwarded for display to the faceplate.
6\VWHPUDQJH 8VHUDUHDSURFHVVWDJWHPSODWH
(;7B67$7 37B5HOHDVH 37B5HO2S 37B5HOHDVH
202'(B 0RGH
39B2XW 39
202'(B ';FKJ
37 ';&+*B
*HWLQSURJUHVVVWDWXV
';&+*B 09
IURPSURFHVVWDJ
2B37 37 2RV$FW 2RV/L

ุ 2RV2S
39B,Q
$3/
$3/LQSXW
7HFKQRORJLFDO
'LDJQRVWLFGULYHU &KDQQHOGULYHU %ORFN
02'
3,,
(;7B67$7 37B5HOHDVH
39B2XW
202'(B 0RGH
202'(B ';FKJ
37 ';&+*B
*HWLQSURJUHVVVWDWXV
';&+*B
IURPSURFHVVWDJ
2B37 37 2RV$FW
39B,Q
$3/RXWSXW
'LDJQRVWLFGULYHU &KDQQHOGULYHU
02'
3,4
Figure 1-2 Maintenance release

Basics of APL
Key to diagram:
PII Process image of inputs

PIQ Process image of outputs
Black lines Automatic system connections
Green lines Process value connections made by the planner
Blue lines Connections for maintenance release made by the planner
Note
For additional information on the topic of maintenance please refer to PCS 7 OS process
management.

Basics of APL
1.2.1.6 Time stamp
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
Forming the time information

The time information is generated by one of the following methods and is specified at the
block by means of the input parameter TimeStampOn:
● TimeStampOn = 0: Time stamping is carried out in the EventTS block (default when
installed in the chart)
● TimeStampOn = 1: The high-precision time stamp is carried out in the process I/O
suitable to this purpose.
Time stamping in the EventTS block

Connect the binary output parameter of another block (e.g. Pcs7DiIn) with a message input
Inx (x = 1 ... 8) of the EventTS block.
When the EventTS block recognizes a change in the signal state at this message input, it
uses the current time of the CPU as the time stamp. Only the signal changes that are slower
than the cycle time of the block can be detected.

Basics of APL
High-precision time stamp in the process I/O

You have configured the hardware of your system for high-precision time stamping as
explained in the "PCS 7 - High-Precision Time Stamping Function Manual". The signal
changes are recognized in the I/O devices and the time stamp assigned to them. This data is
available at the output parameter TS_Out of the Pcs7DiIT block.
The high-precision time stamp is independent of the cycle time of the blocks. The actual time
resolution for two different status changes depends on your plant configuration and the
hardware you are using.
Interconnect the output parameter TS_Out of Pcs7DiIT with a message input
InTSx(x = 1 ... 8) of the EventTS block.
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".
1.2.1.7 Displaying auxiliary values
Displaying auxiliary values

Up to two auxiliary values can be displayed in the standard view of some faceplates. This
feature can be used, for example, with motors to indicate the motor current and winding
temperature.
To do so interconnect the value that you want to have displayed with the input parameters
UserAna1 or UserAna2.
In the object properties (I/Os > Identifier) of the block in CFC, you can specify the text to be
displayed for these parameters in the standard view of the faceplate.

Basics of APL
1.2.1.8 Selecting a unit of measure
Coded unit of measure

The parameter XXX_Unit is used to specify the unit of measure for the corresponding input
parameter (XXX stands for a specific parameter, for example, PV_Unit). Entry is carried out
in the form of a code. Exactly one unit of measure is assigned to each code and is displayed
on the faceplate.
You can interconnect the XXX_Unit input parameter of a technological block with the
XXXUnit output parameter of an analog input driver. At the analog input driver, enter the
unit of measure at the XXXUnit input parameter (XXX stands for a specific parameter, for
example PV_InUnit, PVOutUnit).
Using the unit of measure with controllers for the ConPerMon block
For control 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.
Using the S7_unit attribute

If you set the xxx_Unit parameter to 0, the entry is displayed by the S7_Unit attribute in
the faceplate and in the block icon.
Overview of the units of measure

The units of measure are listed in the following tables:
Short list of the units of measure most commonly used in accordance with the specifications
"PA-Profile for Process Device" of "Profibus and Profinet International"
Value Display Description

1000 K Kelvin
1001 °C Degrees Celsius
1002 °F Degrees Fahrenheit
1005 ° Degree
1006 ' Minute
1007 '' Second
1010 m Meter
1013 mm Millimeter
1018 ft Foot
1023 m2 Square meter
1038 L Liter
1041 hl Hectoliter
1054 s Second
1058 min Minute
1059 h Hour
1060 d Day

Basics of APL

1061 m/s Meters per second
1077 Hz Hertz
1081 kHz Kilohertz
1082 1/s Per second
1083 1/min Per minute
1088 kg Kilogram
1092 t Metric ton
1100 g/cm3 Grams per cubic centimeter
1105 g/L Grams per liter
1120 N Newton
1123 mN Millinewton
1130 Pa Pascal
1133 kPa Kilopascal
1137 bar Bar
1138 mbar Millibar
1149 mmH2O Millimeters of water
1175 W·h Watt hour
1179 kW·h Kilowatt hour
1181 kcalth Kilocalorie
1190 kW Kilowatt
1209 A Ampere
1211 mA Milliampere
1221 A·h Ampere hour
1240 V Volt
1349 m3/h Cubic meters per hour
1353 L/h Liters per hour
1384 mol Mole
1422 pH pH value

Basics of APL
Listing of all the units of measure in accordance with the specifications "PA-Profile for
Process Device" of "Profibus and Profinet International"

1000 K Kelvin
1001 °C Degrees Celsius
1002 °F Degrees Fahrenheit
1003 °R Degree Rankine
1004 rad Radian
1005 ° Degree
1006 ' Minute
1007 '' Second
1008 gon Gon
1009 r Revolution
1010 m Meter
1011 km Kilometer
1012 cm Centimeter
1013 mm Millimeter
1014 μm Micrometer
1015 nm Nanometer
1016 pm Picometer
1017 Å angstrom
1018 ft Foot
1019 in Inch
1020 yd Yard
1021 mile Mile
1022 nautical mile Nautical mile
1023 m2 Square meter
1024 km2 Square kilometer
1025 cm2 Square centimeter
1026 dm2 Square decimeter
1027 mm2 Square millimeter
1028 a Are
1029 ha Hectare
1030 in2 Square inch
1031 ft2 Square foot
1032 yd2 Square yard
1033 mile2 Square mile
1034 m³ Cubic meter
1035 dm3 Cubic decimeter
1036 cm3 Cubic centimeter
1037 mm3 Cubic millimeter
1038 L Liter

Basics of APL

1039 cl Centiliter
1040 ml Milliliter
1041 hl Hectoliter
1042 in3 Cubic inch
1043 ft3 Cubic foot
1044 yd3 Cubic yard
1045 mile3 Cubic mile
1046 pint Pint
1047 quart Quart
1048 gal US gallon
1049 ImpGal Imperial gallon
1050 bushel Bushel
1051 bbl Barrel = 42 gallons
1052 bbl(liq) Liquid barrel = 31.5 gallons
1053 ft3 Standard cubic foot
1054 s Second
1055 ks Kilosecond
1056 ms Millisecond
1057 μs Microsecond
1058 min Minute
1059 h Hour
1060 d Day
1061 m/s Meters per second
1062 mm/s Millimeters per second
1063 m/h Meters per hour
1064 km/h Kilometers per hour
1065 knot Knot
1066 in/s Inches per second
1067 ft/s Feet per second
1068 yd/s Yards per second
1069 in/min Inches per minute
1070 ft/min Feet per minute
1071 yd/min Yards per minute
1072 in/h Inches per hour
1073 ft/h Feet per hour
1074 yd/h Yards per hour
1075 mi/h Miles per hour
1076 m/s2 Meter/second squared
1077 Hz Hertz
1078 THz Terahertz
1079 GHz Gigahertz
1080 MHz Megahertz

Basics of APL

1081 kHz Kilohertz
1082 1/s Per second
1083 1/min Per minute
1084 rad/s Revolutions per second
1085 r/min Revolutions per minute
1086 rad/s Radians per second
1087 1/s2 Per second squared
1088 kg Kilogram
1089 g Gram
1090 mg Milligram
1091 Mg Megagram
1092 t Metric ton
1093 oz Ounce
1094 lb Pound
1095 STon US ton (short ton)
1096 LTon British ton (long ton)
1097 kg/m3 Kilograms per cubic meter
1098 Mg/dm3 Megagrams per cubic meter
1099 kg/dm3 Kilograms per cubic decimeter
1100 g/cm3 Grams per cubic centimeter
1101 g/m3 Grams per cubic meter
1102 t/m3 Metric tons per cubic meter
1103 kg/L Kilogram per liter
1104 g/ml Grams per milliliter
1105 g/L Grams per liter
1106 lb/in3 Pounds per cubic inch
1107 lb/ft3 Pounds per cubic foot
1108 lb/gal Pounds per US gallon
1109 STon/yd3 US tons per cubic yard
1110 °Twd Degree Twaddell
1111 °Baum (hv) Degree Baumé (heavy)
1112 °Baum (lt) Degree Baumé (light)
1113 °API Degrees API
1114 SGU Specific gravity units
1115 kg/m Kilograms per meter
1116 mg/m Milligrams per meter
1117 tex Tex
1118 kg·m2 Kilograms per square meter
1119 kg·m/s Kilograms per meter per second
1120 N Newton
1121 MN Meganewton
1122 kN Kilonewton

Basics of APL

1123 mN Millinewton
1124 μN Micronewton
1125 kg·m2/s Kilograms per square meter per second
1126 N·m Newton meter
1127 MN·m Meganewton meter
1128 kN·m Kilonewton meter
1129 mN·m Millinewton meter
1130 Pa Pascal
1131 GPa Gigapascal
1132 MPa Megapascal
1133 kPa Kilopascal
1134 mPa Millipascal
1135 μPa Micropascal
1136 hPa Hectopascal
1137 bar Bar
1138 mbar Millibar
1139 torr Torr
1140 atm Atmosphere
1141 psi Pounds per square inch
1142 psia Pounds per square inch (absolute)
1143 psig Pounds per square inch (gauge)
1144 g/cm2 Grams per square centimeter
1145 kg/cm2 Kilograms per square centimeter
1146 inH2O Inches of water
1147 inH2O (4°C) Inches of water at 4 degrees Celsius
1148 inH2O (68°F) Inches of water at 68 degrees Fahrenheit
1149 mmH2O Millimeters of water
1150 mmH2O (4°C) Millimeters of water at 4 degrees Celsius
1151 mmH2O (68°F) Millimeters of water at 68 degrees
Fahrenheit
1152 ftH2O Feet of water
1153 ftH2O (4°C) Feet of water at 4 degrees Celsius
1154 ftH2O (68°F) Feet of water at 68 degrees Fahrenheit
1155 inHg Inches of mercury
1156 inHg (0°C) Inches of mercury at 0 degrees Celsius
1157 mmHg Millimeters of mercury
1158 mmHg (0°C) Millimeters of mercury at 0 degrees
Celsius
1159 Pa·s Pascal second
1160 m2/s Square meters per second
1161 P Poise
1162 cP Centipoise
1163 St Stokes

Basics of APL

1164 cSt Centistokes
1165 N/m Newtons per meter
1166 mN/m Millinewtons per meter
1167 J Joule
1168 EJ Exajoule
1169 PJ Petajoule
1170 TJ Terajoule
1171 GJ Gigajoule
1172 MJ Megajoule
1173 kJ Kilojoule
1174 mJ Millijoule
1175 W·h Watt hour
1176 TW·h Terawatt hour
1177 GW·h Gigawatt hour
1178 MW·h Megawatt hour
1179 kW·h Kilowatt hour
1180 calth Calorie (thermochemical)
1181 kcalth Kilocalorie (thermochemical)
1182 Mcalth Megacalorie (thermochemical)
1183 Btuth British thermal unit
1184 datherm Decatherm
1185 ft·lb Foot pound
1186 W Watt
1187 TW Terawatt
1188 GW Gigawatt
1189 MW Megawatt
1190 kW Kilowatt
1191 mW Milliwatt
1192 μW Microwatt
1193 nW Nanowatt
1194 pW Picowatt
1195 Mcalth/h Megacalorie per hour
1196 MJ/h Megajoule per hour
1197 Btuth/h British thermal units per hour
1198 hp Horsepower
1199 W/(m·K) Watts per meter kelvin
1200 W/(m2·K) Watts per (square meter kelvin)
1201 m2·K/W Square meters kelvin per Watt
1202 J/K Joules per kelvin
1203 kJ/K Kilojoules per kelvin
1204 J/(kg·K) Joules per (kilogram kelvin)
1205 kJ/(kg·K) Kilojoules per (kilogram kelvin)

Basics of APL

1206 J/kg Joules per kilogram
1207 MJ/kg Megajoules per kilogram
1208 kJ/kg Kilojoules per kilogramm
1209 A Ampere
1210 kA Kiloampere
1211 mA Milliampere
1212 μA Microampere
1213 nA Nanoampere
1214 pA Picoampere
1215 C Coulomb
1216 MC Megacoulomb
1217 kC Kilocoulomb
1218 μC Microcoulomb
1219 nC Nanocoulomb
1220 pC Picocoulomb
1221 A·h Ampere hour
1222 C/m3 Coulombs per cubic meter
1223 C/mm3 Coulombs per cubic millimeter
1224 C/cm3 Coulombs per cubic centimeter
1225 kC/m3 Kilocoulombs per cubic meter
1226 mC/m3 Millicoulombs per cubic meter
1227 μC/m3 Microcoulombs per cubic meter
1228 C/m2 Coulombs per square meter
1229 C/mm2 Coulombs per square millimeter
1230 C/cm2 Coulombs per square centimeter
1231 kC/m2 Kilocoulombs per square meter
1232 mC/m2 Millicoulombs per square meter
1233 μC/m2 Microcoulombs per square meter
1234 V/m Volts per meter
1235 MV/m Megavolts per meter
1236 kV/m Kilovolts per meter
1237 V/cm Volts per centimeter
1238 mV/m Millivolts per meter
1239 μV/m Microvolts per meter
1240 V Volt
1241 MV Megavolt
1242 KV Kilovolt
1243 mV Millivolt
1244 μV Microvolt
1245 F Farad
1246 mF Millifarad
1247 μF Microfarad

Basics of APL

1248 nF Nanofarad
1249 pF Picofarad
1250 F/m Farad per meter
1251 μF/m Microfarad per meter
1252 nF/m Nanofarad per meter
1253 pF/m Picofarad per meter
1254 C·m Coulomb meter
1255 A/m2 Amperes per square meter
1256 MA/m2 Megaamperes per square meter
1257 A/cm2 Amperes per square centimeter
1258 kA/m2 Kiloamperes per square meter
1259 A/m Amperes per meter
1260 kA/m Kiloamperes per meter
1261 A/cm Amperes per centimeter
1262 T Tesla
1263 mT Millitesla
1264 μT Microtesla
1265 nT Nanotesla
1266 Wb Weber
1267 mWb Milliweber
1268 Wb/m Webers per meter
1269 kWb/m Kilowebers per meter
1270 H Henry
1271 mH Millihenry
1272 μH Microhenry
1273 nH Nanohenry
1274 pH Picohenry
1275 H/m Henries per meter
1276 μH/m Microhenries per meter
1277 nH/m Nanohenries per meter
1278 A·m2 Ampere square meters
1279 N·m2/A Newton meter squared per ampere
1280 Wb·m Weber meter
1281 Ω Ohm
1282 GΩ Gigaohm
1283 MΩ Megaohm
1284 kΩ Kiloohm
1285 mΩ Milliohm
1286 μΩ Microohm
1287 S Siemens
1288 kS Kilosiemens
1289 mS Millisiemens

Basics of APL

1290 μS Microsiemens
1291 Ω·m Ohm meter
1292 GΩ·m Gigaohm meter
1293 MΩ·m Megaohm meter
1294 kΩ·m Kiloohm meter
1295 Ω·cm Ohm centimeter
1296 mΩ·m Milliohm meter
1297 μΩ·m Microohm meter
1298 nΩ·m Nanoohm meter
1299 S/m Siemens per meter
1300 MS/m Megasiemens per meter
1301 kS/m Kilosiemens per meter
1302 mS/cm Millisiemens per centimeter
1303 μS/mm Microsiemens per millimeter
1304 1/H Per henry
1305 sr Steradian
1306 W/sr Watts per steradian
1307 W/(sr·m2) Watts per (steradian square meter)
1308 W/(m2) Watts per square meter
1309 lm Lumen
1310 lm·s Lumen second
1311 lm·h Lumen hour
1312 lm/m2 Lumens per square meter
1313 lm/W Lumens per watt
1314 lx Lux
1315 lx·s Lux second
1316 cd Candela
1317 cd/m2 Candela per square meter
1318 g/s Grams per second
1319 g/min Grams per minute
1320 g/h Grams per hour
1321 g/d Grams per day
1322 kg/s Kilograms per second
1323 kg/min Kilograms per minute
1324 kg/h Kilograms per hour
1325 kg/d Kilograms per day
1326 t/s Metric tons per second
1327 t/min Metric tons per minute
1328 t/h Metric tons per hour
1329 t/d Metric tons per day
1330 lb/s Pounds per second
1331 lb/min Pounds per minute

Basics of APL

1332 lb/h Pounds per hour
1333 lb/d Pounds per day
1334 STon/s US tons per second
1335 STon/min US tons per minute
1336 STon/h US tons per hour
1337 STon/d US tons per day
1338 LTon/s British tons per second
1339 LTon/min British tons per minute
1340 LTon/h British tons per hour
1341 LTon/d British tons per day
1342 % Percent
1343 % sol/wt Percentage solids per weight unit
1344 % sol/vol Percentage solids per volume unit
1345 % stm qual Percentage steam quality
1346 °Plato Degree plato
1347 m3/s Cubic meters per second
1348 m3/min Cubic meters per minute
1349 m3/h Cubic meters per hour
1350 m3/d Cubic meters per day
1351 L/s Liters per second
1352 L/min Liters per minute
1353 L/h Liters per hour
1354 L/d Liters per day
1355 ML/d Megaliters per day
1356 ft3/s Cubic feet per second
1357 ft3/m Cubic feet per minute
1358 ft3/h Cubic feet per hour
1359 ft3/d Cubic feet per day
1360 ft3/min std Standard cubic feet per minute
1361 ft3/h std Standard cubic feet per hour
1362 gal/s US gallons per second
1363 gal/min US gallons per minute
1364 gal/h US gallons per hour
1365 gal/d US gallons per day
1366 Mgal/d Mega US gallons per day
1367 ImpGal/s Imperial gallons per second
1368 ImpGal/min Imperial gallons per minute
1369 ImpGal/h Imperial gallons per hour
1370 ImpGal/d Imperial gallons per day
1371 bbl/s Barrels per second
1372 bbl/min Barrels per minute
1373 bbl/h Barrels per hour

Basics of APL

1374 bbl/d Barrels per day
1375 W/m2 Watts per square meter
1376 mW/m2 Milliwatts per square meter
1377 μW/m2 Microwatts per square meter
1378 pW/m2 Picowatts per square meter
1379 Pa·s/m3 Pascal seconds per cubic meter
1380 N·s/m Newton seconds per meter
1381 Pa·s/m Pascal seconds per meter
1382 B Bel
1383 dB Decibel
1384 mol Mole
1385 kmol Kilomole
1386 mmol Millimole
1387 μmol Micromole
1388 kg/mol Kilograms per mole
1389 g/mol Grams per mole
1390 m3/mol Cubic meters per mole
1391 dm3/mol Cubic decimeters per mole
1392 cm3/mol Cubic centimeters per mole
1393 L/mol Liters per mole
1394 J/mol Joules per mole
1395 kJ/mol Kilojoules per mole
1396 J/(mol·K) Joules per mole kelvin
1397 mol/m3 Moles per cubic meter
1398 mol/dm3 Moles per cubic decimeter
1399 mol/L Moles per liter
1400 mol/kg Moles per kilogram
1401 mmol/kg Millimoles per kilogram
1402 Bq Becquerel
1403 MBq Megabecquerel
1404 kBq Kilobecquerel
1405 Bq/kg Becquerels per kilogram
1406 kBq/kg Kilobecquerels per kilogram
1407 MBq/kg Megabecquerels per kilogram
1408 Gy Gray
1409 mGy Milligray
1410 rd Rad
1411 Sv Sievert
1412 mSv Millisievert
1413 rem Rem
1414 C/kg Coulombs per kilogram
1415 mC/kg Millicoulombs per kilogram

Basics of APL

1416 R Röntgen
1417 1/Jm3 Density of magnetic energy
1418 e/Vm3
1419 m3/C Cubic meters per coulomb
1420 V/K Volts per kelvin
1421 mV/K Millivolts per kelvin
1422 pH pH value
1423 ppm Parts per million
1424 ppb Parts per billion
1425 ppth Parts per trillion
1426 °Brix Degrees Brix
1427 °Ball Degrees Balling
1428 proof/vol Proof per volume
1429 proof/mass Proof per mass
1430 lb/ImpGal Pounds per Imperial gallon
1431 kcalth/s Kilocalories per second
1432 kcalth/min Kilocalories per minute
1433 kcalth/h Kilocalories per hour
1434 kcalth/d Kilocalories per day
1435 Mcalth/s Megacalorie per second
1436 Mcalth/min Megacalories per minute
1437 Mcalth/d Megacalories per day
1438 kJ/s Kilojoules per second
1439 kJ/min Kilojoules per minute
1440 kJ/h Kilojoule per hour
1441 kJ/d Kilojoules per day
1442 MJ/s Megajoules per second
1443 MJ/min Megajoules per minute
1444 MJ/d Megajoules per day
1445 Btuth/s British thermal units per second
1446 Btuth/min British thermal units per minute
1447 Btuth/d British thermal units per day
1448 μgal/s Micro US gallons per second
1449 mgal/s Milli US gallons per second
1450 kgal/s Kilo US gallons per second
1451 Mgal/s Mega US gallons per second
1452 μgal/min Micro US gallons per minute
1453 mgal/min Milli US gallons per minute
1454 kgal/min Kilo US gallons per minute
1455 Mgal/min Mega US gallons per minute
1456 μgal/h Micro US gallons per hour
1457 mgal/h Milli US gallons per hour

Basics of APL

1458 kgal/h Kilo US gallons per hour
1459 Mgal/h Mega US gallons per hour
1460 μgal/d Micro US gallons per day
1461 mgal/d Milli US gallons per day
1462 kgal/d Kilo US gallons per day
1463 μImpGal/s Micro Imperial gallons per second
1464 mImpGal/s Milli Imperial gallons per second
1465 kImpGal/s Kilo Imperial gallons per second
1466 MImpGal/s Mega Imperial gallons per second
1467 μImpGal/min Micro Imperial gallons per minute
1468 mImpGal/min Milli Imperial gallons per minute
1469 kImpGal/min Kilo Imperial gallons per minute
1470 MImpGal/min Mega Imperial gallons per minute
1471 μImpGal/h Micro Imperial gallons per hour
1472 mImpGal/h Milli Imperial gallons per hour
1473 kImpGal/h Kilo Imperial gallons per hour
1474 MImpGal/h Mega Imperial gallons per hour
1475 μImpgal/d Micro Imperial gallons per day
1476 mImpgal/d Milli Imperial gallons per day
1477 kImpgal/d Kilo Imperial gallons per day
1478 MImpgal/d Mega Imperial gallons per day
1479 μbbl/s Microbarrels per second
1480 mbbl/s Millibarrels per second
1481 kbbl/s Kilobarrels per second
1482 Mbbl/s Megabarrels per second
1483 μbbl/min Microbarrels per minute
1484 mbbl/min Millibarrels per minute
1485 kbbl/min Kilobarrels per minute
1486 Mbbl/min Megabarrels per minute
1487 μbbl/h Microbarrels per hour
1488 mbbl/h Millibarrels per hour
1489 kbbl/h Kilobarrels per hour
1490 Mbbl/h Megabarrels per hour
1491 μbbl/d Microbarrels per day
1492 mbbl/d Millibarrels per day
1493 kbbl/d Kilobarrels per day
1494 Mbbl/d Megabarrels per day
1495 μm3/s Cubic micrometers per second
1496 mm3/s Cubic millimeters per second
1497 km3/s Cubic kilometers per second
1498 Mm3/s Cubic megameters per second
1499 μm3/min Cubic micrometers per minute

Basics of APL

1500 mm3/min Cubic millimeters per minute
1501 km3/min Cubic kilometers per minute
1502 mm3/min Cubic megameters per minute
1503 µm3/h Cubic micrometers per minute
1504 mm3/h Cubic millimeters per minute
1505 km3/h Cubic kilometers per minute
1506 Mm3/h Cubic megameters per minute
1507 µm3/d Cubic micrometers per day
1508 mm3/d Cubic millimeters per day
1509 km3/d Cubic kilometers per day
1510 Mm3/d Cubic megameters per day
1511 cm3/s Cubic centimeters per second
1512 cm3/min Cubic centimeters per minute
1513 cm3/h Cubic centimeters per hour
1514 cm3/d Cubic centimeters per day
1515 kcalth/kg Kilocalories per kilogram
1516 Btuth/lb British thermal units per pound
1517 kl Kiloliter
1518 kl/min Kiloliters per minute
1519 kl/h Kiloliters per hour
1520 kl/d Kiloliters per day
1551 S/cm Siemens per centimeter
1552 µS/cm Microsiemens per centimeter
1553 mS/m Millisiemens per meter
1554 µS/m Microsiemens per meter
1555 MΩ · cm Megaohm centimeter
1556 kΩ · cm Kiloohm centimeter
1557 Weight% Weight percent
1558 mg/L Milligram per liter
1559 µg/L Microgram per liter
1560 %Sat -
1561 vpm -
1562 %vol Volume percent
1563 ml/min Milliliters per minute
1564 mg/dm3 Milligrams per cubic centimeter
1565 mg/L Milligram per liter
1566 mg/m3 Milligrams per cubic meter
1567 ct Carat (jewels) = 200.0·10-6 kg
1568 lb (tr) Pound (troy or apothecary) =
0.3732417216 kg
1569 oz (tr) Ounce (troy or apothecary) = 1/12 lb (tr)
1570 fl oz (U.S.) Ounce (U.S. fluid) = (1/128) gal

Basics of APL

1571 cm3 Cubic centimeter = 10-6 m3
1572 af acre foot = 43560 ft3
1573 m3 normal Cubic meter
1574 L normal Liter
1575 m3 std. Standard cubic meter
1576 L std. Standard liter
1577 ml/s Milliliters per second
1578 ml/h Milliliters per hour
1579 ml/d Milliliters per day
1580 af/s Acre foot per second
1581 af/min Acre foot per minute
1582 af/h Acre foot per hour
1583 af/d Acre foot per day
1584 fl oz (U.S.)/s Ounces per second
1585 fl oz (U.S.) /min Ounces per minute
1586 fl oz (U.S.)/h Ounces per hour
1587 fl oz (U.S.)/d Ounces per day
1588 m3/s normal Standard cubic meters per second
1589 m3/min normal Standard cubic meters per minute
1590 m3/h normal Standard cubic meters per hour
1591 m3/d normal Standard cubic meters per day
1592 L/s normal Standard liters per second
1593 L/min normal Standard liters per minute
1594 L/h normal Standard liters per hour
1595 L/d normal Standard liters per second
1596 m3/s std. Standard cubic meters per second
1597 m3/min std. Standard cubic meters per minute
1598 m3/h std. Standard cubic meters per hour
1599 m3/d std. Standard cubic meters per day
1600 L/s std. Standard liters per second
1601 L/min std. Standard liters per minute
1602 L/h std. Standard liters per hour
1603 L/d std. Standard liters per day
1604 ft3/s std. Standard cubic feet per second
1605 ft3/d std. Standard cubic feet per day
1606 oz/s Ounces per second
1607 oz/min Ounces per minute
1608 oz/h Ounces per hour
1609 oz/d Ounces per day
1610 Paa Pascal (absolute)
1611 Pag Pascal (gauge)
1612 GPaa Gigapasacal (absolute)

Basics of APL

1613 GPag Gigapascal (gauge)
1614 MPaa Megapascal (absolute)
1615 MPag Megapascal (gauge)
1616 kPaa Kilopascal (absolute)
1617 kPag Kilopascal (gauge)
1618 mPaa Millipascal (absolute)
1619 mPag Millipascal (gauge)
1620 μPaa Micropascal (absolute)
1621 μPag Micropascal (gauge)
1622 hPaa Hectopascal (absolute)
1623 hPag Hectopascal (gauge)
1624 gf/cm2a
1625 gf/cm2g
1626 kgf/cm2a
1627 kgf/cm2g
1628 SD4°C Standard density at 4°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 x 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
1998 Unknown unit Use in configuration when the unit of
measure is not known
1999 Special Special units

Basics of APL
1.2.2 Monitoring functions
1.2.2.1 Monitoring functions at the Advanced Process Library
Monitoring functions in the Advanced Process Library

This and the following section encompass the standard monitoring functions in the Advanced
Process Library. The monitoring functions include:
● Limit value monitoring
● Alarms at limit violations
● Time delays for alarms, warnings and tolerances
● Feedback monitoring
● Suppression of messages for alarms, messages and tolerances
For further and detailed information please refer to the following section. For the block-
specific monitoring functions, also refer to the description for the respective block.
1.2.2.2 Limit monitoring
Limit monitoring of the process value

You can monitor the process value to the following high and low alarm, warning and
tolerance limits:
● PV_AH_Lim: Limit for high alarm
● PV_AL_Lim: Limit for low alarm
● PV_WH_Lim: Limit for high warning
● PV_WL_Lim: Limit for low warning
● PV_TH_Lim: Limit for the high tolerance
● PV_TL_Lim: Limit for the low tolerance

Basics of APL
Result of the limit monitoring

The result of limit monitoring is made available at the interconnectable output parameters:
● PV_AH_Act = 1:: Limit for high alarm reached or exceeded
● PV_AL_Act = 1:: Limit for low alarm reached or undershot
● PV_WH_Act = 1:: Limit for high warning reached or exceeded
● PV_WL_Act = 1:: Limit for low warning reached or undershot
● PV_TH_Act = 1:: Limit for high tolerance reached or exceeded
● PV_TL_Act = 1:: Limit for low tolerance reached or undershot
made available (see figure). The SumMsgAct = 1 output parameter is also set when at
least one limit is reached or violated. This parameter can also be 1 if the limit for the position
feedback value or the limit for the control error was reached or exceeded.
39B2XW
39B;;B/LP
39B+\VW
3URFHVVYDOXH
39B;;B/LP 39B+\VW
7LPH
39B;;B$FW
39B;;B$FW
;; $+IRUDODUPKLJK ;; :+IRUZDUQLQJKLJK ;; 7+IRUWROHUDQFHKLJK

;; $/IRUDODUPORZ ;; :/IRUZDUQLQJORZ ;; 7/IRUWROHUDQFHORZ

Basics of APL
Switching on the limit monitoring

Monitoring is always enabled using the input parameters:
● PV_AH_En = 1: Monitoring of the high alarm limits
● PV_AL_En = 1: Monitoring of the low alarm limits
● PV_WH_En = 1: Monitoring of the high warning limits
● PV_WL_En = 1: Monitoring of the low warning limits
● PV_TH_En = 1: Monitoring of the high tolerance limits
● PV_TL_En = 1: Monitoring of the low tolerance limits
Predefinition: When the block is installed, monitoring of the tolerance limits is disabled,
meaning that the parameters are configured with 0. To activate monitoring, assign 1 to these
parameters.
All other monitoring functions are enabled.
Message suppression
The corresponding message is suppressed using the parameters:
● PV_AH_MsgEn = 0: Alarm (high) messages are suppressed
● PV_AL_MsgEn = 0: Alarm (low) messages are suppressed
● PV_WH_MsgEn = 0: Warning (high) messages are suppressed
● PV_WL_MsgEn = 0: Warning (low) messages are suppressed
● PV_TH_MsgEn = 0: Tolerance (high) messages are suppressed
● PV_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.

Basics of APL
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 78) section for more on this.
Alarm delays
You can set alarm delays for coming and going alarms, warnings and tolerances. Refer to
the Area of application of the alarm delays (Page 79) section for more on this.
Operating in the faceplate

You can also change the limits and the hysteresis using the faceplate. Refer to the Limit
operation and display in the faceplate (Page 78) section for more on this.
See also
Two time values per limit pair (Page 80)
Two time values for each individual limit (Page 81)
Limit monitoring of an additional analog value
Limit monitoring of an additional analog value

Limit monitoring is performed for an additional analog value on the basis of the AV block, see
Description of AV (Page 1207) section.
You can monitor an additional analog value to the following high and low limits for alarms
warnings and tolerances at the technological block:
● AV_AH_Lim: Limit for high alarm
● AV_AL_Lim: Limit for low alarm
● AV_WH_Lim: Limit for high warning
● AV_WL_Lim: Limit for low warning
● AV_TH_Lim: Limit for the high tolerance
● AV_TL_Lim: Limit for the low tolerance

Basics of APL
Result of the limit monitoring

The result of limit monitoring is made available at the interconnectable output parameters of
the AV block:
● AV_AH_Act = 1:: Limit for high alarm reached or exceeded
● AV_AL_Act = 1:: Limit for low alarm reached or undershot
● AV_WH_Act = 1:: Limit for high warning reached or exceeded
● AV_WL_Act = 1:: Limit for low warning reached or undershot
● AV_TH_Act = 1:: Limit for high tolerance reached or exceeded
● AV_TL_Act = 1:: Limit for low tolerance reached or undershot
made available (see figure).
$9B2XW
$9B;;B/LP
$9B+\VW
$QDORJYDOXH
$9B;;B/LP $9B+\VW
7LPH
$9B;;B$FW
$9B;;B$FW
;; $+IRUDODUPKLJK ;; :+IRUZDUQLQJKLJK ;; 7+IRUWROHUDQFHKLJK

;; $/IRUDODUPORZ ;; :/IRUZDUQLQJORZ ;; 7/IRUWROHUDQFHORZ

Basics of APL

Monitoring is always enabled using the input parameters of the AV block:
● AV_AH_En = 1: Monitoring of the high alarm limits
● AV_AL_En = 1: Monitoring of the low alarm limits
● AV_WH_En = 1: Monitoring of the high warning limits
● AV_WL_En = 1: Monitoring of the low warning limits
● AV_TH_En = 1: Monitoring of the high tolerance limits
● AV_TL_En = 1: Monitoring of the low tolerance limits
Predefinition: When the block is installed, monitoring of the tolerance limits is disabled,
meaning that the parameters are configured with 0. To activate monitoring, assign 1 to these
parameters.
All other monitoring functions are enabled.
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 technological block for the limits, for example,
to suppress signal flutter. Refer to the Limit monitoring with hysteresis (Page 78) section for
more on this.
Alarm delays
You can set alarm delays for coming and going alarms, warnings and tolerances. Refer to
the Area of application of the alarm delays (Page 79) section for more on this.

You can also change the limits and the hysteresis using the faceplate. Refer to the Limit
operation and display in the faceplate (Page 78) section for more on this.

Basics of APL
Limit monitoring of the feedback
Limit monitoring of position feedback

The position feedback of the manipulated variable can be monitored for the following high
and low warning limits:
● RbkWH_Lim: Limit for high warning
● RbkWL_Lim: Limit for low warning
Result of limit monitoring of the position feedback

The result of limit monitoring of the position feedback is made available at the
interconnectable output parameters:
● RbkWH_Act = 1: High limit reached or exceeded
● RbkWL_Act = 1: Low limit reached or undershot
. The SumMsgAct = 1 output parameter is also set when at least one limit value is reached
or violated. This parameter can also be 1 if the limit for the process value or the limit value
for the control error was reached or exceeded.
When the limits are reached or exceeded, messages that can be suppressed are output.

Monitoring is always enabled using the input parameters:
● RbkWH_En = 0: Monitoring of the high warning limit is disabled
● RbkWL_En = 0: Monitoring of the low warning limit is disabled
Predefinition: When the block is installed, monitoring is disabled (default is 1).
Message suppression
● 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.
Please also refer to the section Limit monitoring with hysteresis (Page 78).
Alarm delays (only for the PIDConR and MotSpdCL blocks)

You can set alarm delays for coming and going warnings. Please refer to the section Area of
application of the alarm delays (Page 79).

Basics of APL

You can also change the limits and the hysteresis using the faceplate. Please refer to the
section Limit operation and display in the faceplate (Page 78).
Monitoring the error signal limits
Limit monitoring of control error

The control error of the manipulated variable can be monitored for the following high and low
alarm limits:
● ER_AH_Lim: Limit for high alarm
● ER_AL_Lim: Limit for low alarm
Result of limit monitoring of the control error

The result of limit monitoring of the control error is made available at the interconnectable
output parameters:
● ER_AH_Act =1: High limit violated (reached or exceeded)
● ER_AL_Act =1: Low limit (reached or undershot)
. The SumMsgAct = 1 output parameter is also set when at least one limit value is reached
or violated. This parameter can also be 1 if the limit for the position feedback or the limit for
the process value was reached or exceeded.
When the limits are reached or exceeded, messages that can be suppressed are output.
Enabling limit monitoring of the control error

Alarm monitoring is enabled using the input parameters:
● ER_AH_En = 1: Monitoring of the high alarm limit
● ER_AL_En = 1: Monitoring of the low alarm limit
Predefinition: When the block is installed, monitoring is disabled.
Message suppression
● 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 of the control error has
been enabled.

Basics of APL
Hysteresis
You can specify a hysteresis (ER_Hyst) for these limits, for example, in order to suppress
signal flutter. Please also refer to the section Limit monitoring with hysteresis (Page 78).
Alarm delays
You can set alarm delays for coming and going alarms. Please refer to the section Area of
application of the alarm delays (Page 79).

You can also influence the limits and the hysteresis by means of the faceplate. Please refer
to the section Limit operation and display in the faceplate (Page 78).
Limit monitoring with hysteresis
Limit monitoring with hysteresis

You can additionally define a hysteresis for all limit monitoring functions (parameter
xxx_Hyst, xxx can, for example, be PV for the process value). You use the hysteresis, for
example, to suppress signal flutter.
Enter the hysteresis as a physical variable at the block and faceplate (if you have the
appropriate operator control permissions (WinCC)).
For the WinCC operator control permissions, please refer to the help on WinCC.
Limit operation and display in the faceplate

The limit value view of the faceplate can be used to modify limits and the hysteresis if the
corresponding operator control permission (higher process controlling) is available. The
limits are displayed graphically in the standard view of the faceplate.
If the limits are reached or exceeded,, a message of the alarm class is, for example,
triggered. This is indicated graphically as follows:

Basics of APL
1.2.2.3 Alarm delays
Area of application of the alarm delays
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!
Alarm delays in the Advanced Process Library

There are three block types with a different application of the alarm delay for:
● One time value for all limits (Page 79)
● Two time values per limit pair (Page 80)
● Two time values for each individual limit (Page 81)
One time value for all limits
Blocks with one time value for the alarm delay

This form of alarm delay is used for blocks without a unit designation, for example,
ConPerMon.
The alarm delay is used when brief violations of the set alarm thresholds are to be
suppressed. The duration of the time delay is parameterized at the input AlmDelay.
Parameter assignment is always carried out in seconds.
Activating the alarm delay

The alarm delay is disabled by default (AlmDelay = 0). To use the function, set a delay
time [s] with the AlmDelay parameter.

Basics of APL
Two time values per limit pair
Blocks with two time values for the alarm delay per limit pair
This form of alarm delay is used for blocks with an L in the unit designation. You recognize
these blocks by the character L at the end of the block name, for example, MotL.
suppressed. The alarm delay is parameterized at the following inputs:
Parameter for the delay time Explanation

XXX_A_DC Delay time for coming events of the class
• Alarm
XXX_Alarm_DelayComing
XXX: Value to be monitored
XXX_A_DG Delay time for going events of the class
• Alarm
XXX_Alarm_DelayGoing
XXX_W_DC Delay time for coming events of the class
• Warning
XXX_Warning_DelayComing
XXX_W_DG Delay time for going events of the class
• Warning
XXX_Warning_DelayGoing
XXX_T_DC Delay time for coming events of the class
• Tolerance
XXX_Tolerance_DelayComing
XXX_T_DG Delay time for going events of the class
• Tolerance
XXX_Tolerance_DelayGoing

By default, the alarm delay is disabled for each individual pair, meaning that each individual
parameter has 0 [s] pre-assigned.
To use the function, set a delay time [s] for each parameter.

Basics of APL
Alarms due to be dealt with

Alarms, warnings, or tolerances due to be dealt with are output at the corresponding output
parameters:
● XXX_A_Act = 1: Alarm limit reached or violated
● XXX_W_Act = 1: Warning limit reached or violated
● XXX_T_Act = 1: Tolerance limit reached or violated
If a message is active at one of these outputs, this is indicated by a 1.
Two time values for each individual limit
Alarm delay for blocks with two time values for each individual limit
This form of alarm delay is used for blocks with an R in the unit designation. These blocks
are identified by the character R at the end of the block name, e.g. PIDConR.
suppressed. The alarm delay is parameterized at the following inputs:

XX_AH_DC Delay time for coming events of the class
• Alarm (for high limit)
XX_AlarmHigh_DelayComing
XX: Value to be monitored
XX_AH_DG Delay time for going events of the class
• Alarm (for high limit)
XX_AlarmHigh_DelayGoing
XX_AL_DC Delay time for coming events of the class
• Alarm (for low limit)
XX_AlarmLow_DelayComing
XX_AL_DG Delay time for going events of the class
• Alarm (for low limit)
XX_AlarmLow_DelayGoing
XX_WH_DC Delay time for coming events of the class
• Warning (for high limit)
XX_WarningHigh_DelayComing
XX_WH_DG Delay time for going events of the class
• Warning (for high limit)
XX_WarningHigh_DelayGoing

Basics of APL

XX_WL_DC Delay time for coming events of the class
• Warning (for low limit)
XX_WarningLow_DelayComing
XX_WL_DG Delay time for going events of the class
• Warning (for low limit)
XX_WarningLow_DelayGoing
XX_TH_DC Delay time for coming events of the class
• Tolerance (for high limit)
XX_ToleranceHigh_DelayComing
XX_TH_DG Delay time for going events of the class
• Tolerance (for high limit)
XX_ToleranceHigh_DelayGoing
XX_TL_DC Delay time for coming events of the class
• Tolerance (for low limit)
XX_ToleranceLow_DelayComing
XX_TL_DG Delay time for going events of the class
• Tolerance (for low limit)
XX_ToleranceLow_DelayGoing

By default, the alarm delay is disabled for each individual limit, meaning that each individual
parameter has 0 [s] pre-assigned.
To use the function, set a delay time [s] for each parameter.
Alarms due to be dealt with

Alarms, warnings, or tolerances due to be dealt with 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.

Basics of APL
1.2.2.4 Feedbacks
Monitoring the feedbacks
Feedback monitoring
You can use the following monitoring functions:
● Monitoring the start-up and stop characteristics for motors or the run time of valves
● Monitoring the operation of motors or the maintenance of the position of valves
● Disabling feedbacks
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.
Monitoring the start-up and stop characteristics for motors or the run time 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. At
the same time, an error message is generated. The block then goes to its safe position. In
the case of motors, this is always the stop state. With other blocks, this is a safe position you
have specified (parameter SafePos). The block signals this at the corresponding output
parameter of the error message with 1, for example, with MonDynErr = 1 for motors. In
automatic mode, you will have to reset the monitoring error using the Reset button (RstOp
= 1 or via the interconnectable input parameter RstLi = 1). Use the Feature bit
Resetting via input signals in the event of interlocks or errors (Page 194) to enable an
automatic reset (bit = 1) at an edge transition. This is not necessary in manual mode.
Parameters are set in seconds.

Basics of APL
Monitoring the operation of motors or the maintenance of the position of valves

Monitoring of the operation or the maintenance of the position of valves is implemented
using the parameter MonTiStatic. The monitoring time specifies the period in which the
feedback value can change its value briefly without an error message being output. An
example would be a running motor with the feedback via the input parameter FbkStart.
This parameter should be static in accordance with the control function. However, its value
can change within the monitoring time. If the change in the FbkStart parameter takes
longer than the monitoring time, the text "Runtime error" for motors or "Control error" for
valves is displayed in the standard view of the faceplate. At the same time, an error message
is generated. The block then goes to its safe position. In the case of motors, this is always
the stop state. With other blocks, this is a safe position you have specified (parameter
SafePos). The block signals this at the corresponding output parameter of the error
message with 1, for example, with MonStaErr = 1 for motors. In automatic mode, you will
have to reset the monitoring error using the Reset button (RstOp = 1 or via the
interconnectable input parameter RstLi = 1) . Use the Feature bit Resetting via input
signals in the event of interlocks or errors (Page 194) to enable an automatic reset (bit = 1)
at an edge transition. This is not necessary in manual mode.
Parameters are set in seconds.
Note
Please note that MonTiDynamic ≥ MonTiStatic has to be configured.
Restarting after monitoring errors

There are different procedures depending on the operating mode for restarting after
monitoring errors:
● Manual mode
● Automatic mode
● Local mode
Manual mode
The monitoring error cannot be reset when the control and feedback signals do not match.
When the control and feedback signals match, the monitoring error is automatically reset.
Automatic mode
The Reset button in the faceplate is disabled.
When the control and feedback signals match, the reset is made depending on the setting
made at the Feature bit Resetting via input signals in the event of interlocks or errors
(Page 194).

Basics of APL
Local mode
The monitoring error can only occur in local mode if you have set 1 or 3 for the input
parameter LocalSetting (see Local mode (Page 36)). No monitoring error is output when
LocalSetting is configured with 2 or 4.
When the control and feedback signals match, the monitoring error is reset by stopping
(StopLocal = 1) the drive.
Disabling feedbacks
You can also disable feedback completely. Please refer to section Disabling feedback for
valves (Page 85) for further information.
Disabling feedback for valves
Disabling monitoring of feedback for valves

You can operate a block without feedback. To do this, set the NoFbkxxx = 1 parameter,
whereby xxx stands for the respective function, for example, NoFbkOpen for the valve. This
means, for example, that you do not have any feedbacks for the opened state of the valve.
Monitoring is thus disabled for this feedback. The feedback at the block is adjusted
according to the control signal.

Basics of APL
1.2.3 Signals
1.2.3.1 Output signal as a static signal or pulse signal
Output signal as a static signal or pulse signal

When using motors, valves, dosers and digital operator control blocks (for example,
OpDi01), you can output the control signals as:
● Static signal or as a
● Pulse signal with configurable pulse length.
You can find the signals in the I/O table of the individual blocks.
Note
This function is also available for the following blocks:
• Dose (Out and Out2 parameters)
• OpDi01
• OpDi03
Output signal as a static signal

The control settings are made available as a static signal in the blocks in the form of
interconnectable output parameters. The MotRevL block, for example, provides these as
static signals via the alternative output parameters Fwd, Rev and Run.

Basics of APL
Output signal as a pulse signal

The control is made available as pulse signals at the blocks using interconnectable output
parameters. You specify the pulse length of the output signals in seconds using the input
parameter PulseWidth. The MotRevL block, for example, provides these as pulse signals
via the output parameters P_Fwd, P_Rev and P_Stop.
Fwd
P_Fwd PulseW idth
Rev
P_Rev
PulseW idth
P_Stop
PulseW idth
1.2.3.2 Recording the first signal for interlock blocks
Recording the first signal

You activate the function described below using the Feature bit " Activating recording of the
first signal (Page 191)".
The number of the input that caused the last output signal change from 1 to 0 (good state to
locked) is displayed for you in bit coding at the FirstIn output. The cause may be:
● A signal change at the input or a change in inversion
Example: With an OR logic operation, the single 1 changes to 0. The output then
changes from 1 to 0.
● A change to the I/O
Example: Excluding the single 1 then results in an output of 0 with an OR logic operation.
● FirstIn is not changed if the following events occur, despite a change to the output:
– Change in output value from or to DefaultOut
If several signals are at the same time responsible for the change, all responsible inputs are
indicated in the faceplate and output in bit coding in the FirstIn output. If the input signals
change without this causing the signal at the output to change, FirstIn does not change.
Inputs which are not interconnected or which are excluded are not taken into account.
You can reset FirstIn to 0 if you set the RstLi input from 0 to 1 (positive edge) or you
can operate the RstOp input using the faceplate ("Reset" button).
If at least one bit in FirstIn is set, other signal changes are not taken into account.

Basics of APL
1.2.3.3 Forming and outputting signal status for blocks
Outputting the signal status of the block

The process values of the function blocks are generated and transferred along with a signal
status as a structured variable. This contains a statement about the signal quality. The
function blocks determine the appropriate signal status for their process outputs depending
on the signal status of the process inputs. The signal status is transferred via
interconnections of the process signals. The signal status can be formed in the following
ways within:
● Technological blocks, for example, controller and motor blocks
● Logical blocks
● Interlock blocks
● Channel driver blocks
● Driver blocks for field devices
Forming the signal status in technological blocks

In technological blocks, a group status is formed from the input parameters (see description
of the relevant blocks) according to the priority table below (highest priority is 0). This group
status is displayed in the status bar of the faceplate and of the block icon.
Signal
status Priority Value Meaning
icon
0 16#60 Local functional check / simulation
1 16#00 Bad, device related
2 16#28 Bad, process related
3 16#68 Unknown, device related
4 16#78 Unknown, process related
5 16#A4 Maintenance request
6 16#80 Good

Basics of APL
Interconnectable output parameters (for example, PV_AH_Act) that can be influenced

directly by an interconnectable input parameter (for example, PV) inherit the following status
from this input parameter:
● Good
● Bad, process related
● Bad, device related
If an output parameter is influenced directly by several interconnectable input parameters
(limit monitoring), it receives the status of the input parameter having the highest priority (see
the overview above). Thus, for example, the system deviation is formed from the setpoint
(SP) and the process value (PV). The output parameter ER_AH_Act, for example, that
signals an active violation of the high limit, has a signal status based on the group status
formed from the process value and setpoint.
Feedback signals (Fbk) and position feedbacks (Rbk) that have a direct influence on the
block function and are monitored (for example, runtime monitoring), do not have any
influence on the status of output signals.
Evaluation of the signal status in case of interlocks in technological blocks

The signal states of the interconnectable input parameters of the interlocking and protective
signals are treated exactly like process values with the following exceptions:
● The signal status is displayed in the faceplate at the buttons for calling the series-
connected interlocking blocks.
● If the input signal has the signal status for a simulation and if the interlocking condition is
fulfilled (for example, Protect = 1), the input signal is interpreted in this case as a
bypassed signal and is displayed using the icon for bypassing.
● If the input signal has the signal status for a simulation and if the interlocking condition is
not fulfilled (for example, Protect = 0), the input signal is interpreted in this case as a
simulated signal and is displayed using the icon for simulating:
● If the input signal has the signal status for the state "Bad, device related" state or "Bad,
device related", this is evaluated as an unfulfilled interlocking condition (for example
Protect = 0), regardless of its value (for example, Protect = 1).
Display of the signal status in the faceplate and block icon for technological blocks
The signal status is displayed for each individual parameter (except for the additional values)
in the faceplate next to the process values. The group status is displayed in the block icon
and in the group display of the faceplate.

Basics of APL
Generating the signal status within logical blocks

Within logical blocks, a group status is generated from all input parameters, according to a
priority table (highest priority is 0). The parameter SelPrio is used to define the priority
specification used to carry out interlinking of the individual states (default setting is usually
0). You have the option between the following specifications:
Priority SelPrio = 0 SelPrio = 1 SelPrio = 2 SelPrio = 3 SelPrio = 4 SelPrio = 5 SelPrio = 6 SelPrio = 7

0
16#60 16#60 16#60

16#80 16#A4 16#80 16#A4 16#80
1
16#00 16#00 16#00 16#A4 16#80 16#80 16#A4 16#80

2
16#60 16#60
16#28 16#28 16#28 16#A4 16#78 16#A4
3
16#68 16#68 16#68 16#00 16#00 16#00 16#68 16#78

4
16#78 16#78 16#78 16#28 16#28 16#28 16#28 16#68

5
16#60 16#60
16#A4 16#68 16#68 16#68 16#00 16#28
6
16#60
16#80 16#A4 16#80 16#78 16#78 16#78 16#00
Note
The SelPrio parameter can take a value from 0 to 7. If you enter a value greater than 7,
the setting for 7 is used. If you select a value less than 0, the setting for 0 is used.

Basics of APL
Evaluation of the signal status in the case of interlocking blocks (such as Intlk02)
The block determines the signal status of the output signal, based on the signal status of the
input values, the logic operation, and the output value in accordance with the following rules:
General rules
● The best/worst signal status is generated according to the priority table for technological
blocks.
● The signal status of the output is generated from the best (lowest priority) or worst
(highest priority) signal status of those input signals (highest priority is 0), which are
interconnected and not excluded (relevant input signals) in accordance with the logic
operation and its result.
● If all inputs are excluded or not interconnected, the signal status of the output is set to
simulation (16#60).
AND operation
● If the output value is 1, it has the worst signal status of all relevant input signals.
● If the output value is 0, it has the best signal status of the relevant input signals with a
value of 0.
● If the output value is 1 and at least one input is excluded, the signal status of the output is
set to simulation (16#60).
OR operation
● If the output value is 1, it has the best signal status of the relevant input signals with a
value of 1.
● If the output value is 0, it has the worst signal status of all relevant input signals.
● If the output value is 0 and at least one input is excluded, the signal status of the output is
set to simulation (16#60).
Signal
status Priority Value Meaning
icon
0 16#00 Bad, device related
1 16#28 Bad, process related
2 16#60 Local functional check / simulation
3 16#68 Unknown, device related
4 16#78 Unknown, process related
5 16#A4 Maintenance request
No icon 6 16#80 Good

Basics of APL
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 exclude 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:
The currently valid status for the output signal is also displayed in the faceplate.
Forming the signal status for PCS7 channel blocks

The signal status for PCS7 channel blocks can assume the following values:
Value Meaning
16#80 Good
16#78 Unknown, process related:
Limitation of input parameter PV_In is active (analog output drivers only)
16#60 Simulation, substitute value or last valid value
16#00 Bad, device related (value not valid)
Forming the signal status for Fb channel blocks (field devices)

The signal status of Fb channel blocks for field devices can assume the following values:
Value Meaning
16#80 Good
16#78 Unknown, process related
16#68 Unknown, device related
16#60 Simulation, substitute value or last valid value
16#28 Bad, process related
16#00 Bad, device related (value not valid)
16#A4 Maintenance demand, maintenance request

Basics of APL
1.2.3.4 Selecting signals for processing
Selecting signals for processing

Using the SelInput input parameter, you select the number of interconnectable input
parameters to be used for processing in the block. The selected number denotes the input
parameters used In1 ... Inn.
If, for example, you set this input parameter to SelInput = 3, the input parameters In1,
In2 and In3 will be used for processing.
1.2.3.5 Simulating signals
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 status of the signal is set to the simulation value (see also Forming and
outputting signal status for blocks (Page 88)).
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.

Basics of APL
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 receive the simulation status, for example, signals
for further processing in other blocks.
● 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 status generate a group status
from the individual states in accordance with the priority table. This group status is
displayed in the status bar of the block icon and of the operator block with the simulation
status as follows:
● The interlocking functions of the block are not influenced.
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.
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.
Otherwise this is displayed on the Bad = 1 output parameter with a higher-level error.
Simulation takes place in runtime using operator input in the faceplate's parameter view by
clicking on the "Simulation" button.

Basics of APL
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-relevant output signals receive the simulation status, for example, signals
for further processing in other blocks.
● 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
operator block 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 control function of the block can be manipulated, the read-back and feedback
values (for example Rbk, FbkSpd1) are adjusted according to the manipulation of the
control settings
● Associated values (for example UserAna1) cannot be simulated.
● The interlocking functions of the block are disabled and are displayed using the
corresponding icon in the faceplate and in the block icon as follows:

Basics of APL
1.2.3.6 Setpoint input - internal and external
Setpoint specification internal & external

Some blocks have a function that allows setpoints to be specified. This specification is
carried out either by means of a CFC/SFC program or by means of the faceplate (operator).
With doser blocks and frequency converters, the operator can specify the internal setpoint
value (SP_Int) or a higher-level open-loop control will specify an external setpoint value
(SP_Ext). In principle, the blocks operate according to the same scheme:
63B/L2S
63B/L2S 63B/L2S
)DFHSODWH &)&6)&
63B([W2S
63B,QW2S 63B,QW/L 63B([W/L
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.

Basics of APL
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.
If both signals are set, SP_IntLi = 1 has priority.
Bumpless switchover from external to internal setpoint

The parameter SP_TrkExt = 1 is used so that the internal setpoint tracks the external
setpoint to achieve a bumpless switchover from the external to the internal setpoint. This
allows unwanted jumps at the output parameter to be avoided.

Basics of APL
1.2.3.7 Using a setpoint ramp
Using setpoint ramp

Starting at the current internal setpoint, the setpoint can be set to a target setpoint value over
a ramp-shaped function. In the faceplate, you can start the function in ramp view (SP_RmpOn
= 1)).
3RVLWLYHFKDQJH 1HJDWLYHFKDQJH
&XUYHRILQSXW

YDOXH
&XUYHRIRXWSXW
YDOXH
&XUYHRIRXWSXW
YDOXH
&XUYHRILQSXW

YDOXH
Use the SP_RmpModTime input parameter or the ramp view of the faceplate to specify
whether the setpoint ramp is defined over time or over the ramp:
● 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_Target) after the selected time
(SP_RmpTime).
● If you select ramp (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. The ramp trip is aborted automatically if automatic mode with an internal
setpoint is ended.
Note
The setpoint ramp can only be used if the setpoint was selected internally.

Basics of APL
1.2.3.8 Deadband
Dead band
To suppress values fluctuating around zero, you can set a dead band (Deadband):
Deadband = 0: Dead band is disabled
Deadband ≠ 0: Dead band is enabled
39B2XW
'HDGEDQG
39
'HDGEDQG

Basics of APL
1.2.4 Interlocking functions
1.2.4.1 Interlocks
Interlocks at blocks
A maximum of three types of interlock can be used depending on the block. Three separate
inputs named Intlock, Protect and Permit are available for these functions. The
following interlock types exist:
● Activation enable (Permission): The activation enable (input Permit = 1) makes it
possible to leave the safe position of the block in response to operator input or a
command from the program (CFC/SFC). The activation enable signal has no effect if the
block is not in the safe position.
● Interlock without reset (Interlock): An active interlock condition brings the block to the safe
position (input 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 brings the block to the safe
position (input Protect = 0). After the interlock conditions are cleared, the operator or
an activation sequence must reset the control functions again to match the input
parameters (only in automatic mode). The parameter Features can be used to specify
the reset reaction of the block:
– Feature Bit = 0: Reset is carried out either by operation in the faceplate, or using the
interconnectable input parameter (RstLi = 1) at the block.
– Feature Bit = 1: It is also possible to reset with a 0-1 edge change in the control signal
in automatic mode.
For additional information, refer to the description of the Feature bit Resetting via input
signals in the event of interlocks or errors (Page 194).

Basics of APL
Display of the interlock in the faceplate and in the block icon

The interlock state is visualized in the faceplate and in the block icon by a status display
(padlock) as follows:
● Open padlock: No active interlock
● Closed padlock: One or more interlocks are activate
● No padlock: Individual interlocks are not active
– Perm_En = 0 or Permit.ST = 16#FF: of the input parameter Permit has no
effect, the button in the faceplate is invisible
– Prot_En = 0 or Protect.ST = 16#FF: of the input parameter Protect has no
– Intl_En = 0 or Intlock.ST = 16#FF: of the input parameter Intlock has no
The block icon indicates the prioritized group status according to the active operating state.
See also the Forming the group status for interlock information (Page 105) section 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 (Perm_En = 0, Prot_En = 0, Intl_En = 0) or all parameters have the signal
status 16#FF (Permit.ST = 16#FF, Protect.ST = 16#FF, Intlock.ST =
16#FF).
Note
Motors and values are not put into the safe position if one of the interlock inputs is active
(e.g. Intlock = 0) and the corresponding signal status is 16#FF
(Intlock.ST = 16#FF).
Influence of the signal status on the interlock

Refer to the Influence of the signal status on the interlock (Page 103) section 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 Generating instance-specific messages
(Page 46) section for more on this.

Basics of APL
1.2.4.2 Trip function
Trip function
The trip function is used to turn off the motor if there is heat overload (Trip = 0,
interconnectable input parameter). The function can be deactivated with the BypProt = 1
parameter in local mode and in the simulation status.
If the motor is turned off by the trip function, a message (process control message) is
generated. This is indicated in the faceplate with the "Trip" text.
In automatic mode, you will have to reset the trip using the Reset button (RstOp = 1 or via
the interconnectable input parameter RstLi = 1) . This is not necessary in manual mode.
1.2.4.3 Rapid stop for motors
Rapid stop for motors

Rapid stop has the highest priority in all operating modes (manual and automatic mode as
well as local mode) and operating states (such as the forcing of states). It is activated via the
faceplate. This depends on the setting at the Feature bit Enabling rapid stop via faceplate
(Page 192).
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 to the corresponding driver block and in the
I/O to realize the rapid stop function in the hardware.
Rapid stop is unlocked for all operating modes with the "Reset" button in the faceplate
(ResetOp = 1); in CFC it is unlocked with the ResetLi = 1 input parameter.

Basics of APL
1.2.4.4 Influence of the signal status on the interlock
Influence of the signal status on the interlock

There are three ways in which the signal status affects the interlocks:
● Simulation signal status (value 16#60)
● Signal status "Bad, device related" (value 16#00) or "Bad, process related" (value 16#28)
● Signal status ≠ "Simulation" and "Bad, device related"
"Simulation" signal status (value 16#60)

If the interlock signal with the status 16#60 brings about a cancellation of the interlock, this is
processed as a bypass of the interlock in the block and displayed with the following icons in
the faceplate:
If the interlock signal with the status 16#60 does not cancel the interlock, this is executed as
a simulation in the block and displayed with the following icons in the faceplate:

Basics of APL
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
for 16#28 and
A motor protection signal (Trip parameter) with signal status 16#00 or 16#28 is used to
activate motor protection. This is indicated by means of "Trip" in the standard view of the
faceplates.
Signal status ≠ "Simulation" and "Bad, device related"

Only signal states "Simulation" and "Bad, device related" affect processing in the block; all
others are displayed simply with their relevant icon in the faceplate.

Basics of APL
1.2.4.5 Forming the group status for interlock information
Forming the group status for interlock information

A group status for interlock information is required for:
● Interlock state for:
– Interlocked
– Not interlocked
– Deactivated
Group status for the interlock state

All the effective interlock states are combined and displayed in the block icon. The interlock
states are displayed with the following prioritization:
1. Function interlocked, shown in the block icon with a closed padlock
2. Function not interlocked, shown in the block icon as an open padlock
3. Function disabled, shown in the block icon as a crossed-out, closed padlock

Basics of APL
Overview: Display for the interlock status in faceplate

Interlocks are shown in the faceplate as follows:
Parameter: Parameter: Value: Status: Button Icon Icon

BypProt Perm_En or Permission or Permission or
Prot_En or Protection or Protection or
Intl_En Intlock Intlock
x x X 16#FF - - -
x 0 x x - - -
0 1 1 16#00 Visible
0 1 1 16#28 Visible
0 1 0 16#60 Visible
0 1 1 16#60 Visible
0 1 0 ≠ 16#FF Visible Status based

on priority
0 1 1 ≠ (16#FF, Visible Status based
16#60, 16#00, on priority
16#28)
1 (for local 1 x ≠ 16#FF Visible Status based
mode and on priority
simulation only)
Comments on table:
● X: The value is irrelevant for the display of the icon.
Note
If values are forced in the block, this is indicated in the block icon by a crossed-out,
closed padlock.

Basics of APL
1.2.4.6 Disabling interlocks
Disabling individual interlocks

You can disable the block interlocks that are implemented using the input parameters
Intlock, Protect and Permit.
If you want to disable the block interlock, you have to set the following parameters:
● Perm_En = 0 or Permit.ST = 16#FF: The Permit input parameter has no effect
● Prot_En = 0 or Protect.ST = 16#FF: The Protect input parameter has no effect
● Intl_En = 0 or Intlock.ST = 16#FF: The Intlock input parameter has no effect
LockAct = 0 is included in the conditions mentioned above.
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.

Basics of APL
1.2.5 General functions for controllers
1.2.5.1 Ramp limiting of the setpoint
Gradient limit of the setpoint

The gradient limit is activated via the SP_RateOn = 1 input parameter.
The values are set at the SP_UpRaLim and SP_DnRaLim parameters.
● SP_UpRaLim sets the upper gradient limit
● SP_DnRaLim sets the lower gradient limit
Note
ParametersSP_UpRaLim and SP_DnRaLim are always evaluated according to their
magnitude.
Displaying active limitation

A gradient limit is indicated at the following output parameters:
● SP_UpRaAct = 1: Gradient has an upper limit
● SP_DnRaAct = 1: Gradient has a lower limit
1.2.5.2 Inverting the control sense
Inverting the control action

For some processes (for example cooling processes), negative control gain is necessary.
This is achieved by the inverting the control action by means of the input parameter
NegGain = 1. The gain is always entered positively at the input parameter Gain . If there
is an inversion, this is indicated at the output parameter GainEff by a negative number.

Basics of APL
1.2.5.3 Control error generation and deadband
Control error generation and dead band

The control error is formed from the effective setpoint SP and the process
valuePV (ER = SP - PV_Out) and is available at the ER output.
To suppress disturbances in the steady state, you can assign a dead band (Deadband):
● Deadband = 0: Dead band is disabled
● Deadband ≠ 0: Dead band is enabled
(5
'HDGEDQG
6339B2XW
'HDGEDQG
1.2.5.4 Using control zones
Using control zones

The control zone function is mainly used for temperature processes.
If ConZone ≠ 0, the controller works with a control zone; if ConZone = 0, the "control
zone" function is deactivated. This means that the controller operates based on the following
algorithm:
● If the process value PV exceeds the setpoint SP by more than the value defined for
ConZone, the value MV_LoLim is output as the manipulated value (controlled closed-
loop mode).
● If the process value PV falls below the setpoint SP by more than ConZone, MV_HiLim is
output (controlled closed-loop mode).
● If the manipulated value PV stays within the control zone (ConZone), the manipulated
value 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.
Advantages of the control zone:

Once the control zone is entered, the manipulated variable is quickly reduced by the applied
D action. The control zone is therefore only useful if the D action is activated. Without the
control zone, only the reducing P action would reduce the manipulated variable to any
degree. The control zone speeds up settling without 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.

Basics of APL
1.2.5.5 Setpoint limiting for external setpoints
Setpoint limiting for external setpoints

With this function you can limit the external setpoint to a range by means of the parameters
SP_ExHiLim (high limit) and SP_ExLoLim (low limit). If the setpoint lies outside the range
defined by you, it is limited to the valid range.
If the external setpoint lies on or above the limit SP_ExHiLim, this is displayed at the output
SP_ExHiAct = 1.
If the external setpoint lies on or below the limit of SP_ExLoLim, this is displayed at the
output SP_ExLoAct = 1.
The external setpoint limits can be tracked internally via the interconnection of the output
parameters SP_InHiOut or SP_InLoOut following SP_ExHiLim or SP_ExLoLim. You can
control the two limit pairs from the faceplate.
1.2.5.6 Setpoint tracking the process variable in manual mode
Tracking setpoint in manual mode

To allow a bumpless transfer to automatic mode, the setpoint tracks the process value.
When tracking,(SP_TrkPV = 1) the internal setpoint SP_Int is tracked to the process
value PV.
Additional information on setpoint tracking is available in Manual and Automatic mode for
control blocks (Page 29).

Basics of APL
1.2.5.7 Tracking and limiting a manipulated value
Manipulated variable tracking

You adjust the manipulated value (tracking) in order to implement a bumpless switchover of
controllers. A typical use case is cascade control: If the assigned secondary controller is no
longer in automatic mode with external setpoint, the primary controller must track it.
To adjust the manipulated variable (tracking), you have to set the parameter MV_TrkOn =
1. Now the manipulated variable is taken from the interconnected tracking value MV_Trk
and passed to the output MV.
Manual mode takes priority over tracking to allow a plant operator to set the controller to
manual mode using the faceplate even when tracking the manipulated variable and therefore
continue to normal operation.
The text "Tracking" is displayed additionally in the standard view of the faceplate.
Activating forced tracking mode for the manipulated variable

Forced tracking is used to set the controller output of a higher-level controller to a value that
can be specified.
You can use forced tracking, for example, to implement a centralized emergency stop in the
plant. This can be put into effect regardless of the operating mode the controller is currently
in.
To force adjustment of the manipulated variable (tracking), you have to set the parameter
MV_ForOn = 1. Now the manipulated variable is taken from the interconnected tracking
value MV_Forced and passed to the output MV.
With forced tracking, it is not possible to limit the manipulated variable, nor can the plant
operator change to manual mode in the faceplate. The text "Forced tracking" is displayed
additionally in the standard view of the faceplate.
Note
This function is not available for the FmCont, FmTemp, and ModPreCon blocks.
Limiting the value of a manipulated variable in automatic mode

In automatic mode, the manipulated variable is set to its automatic manipulated variable
limits as specified by the input parameters MV_HiLim and MV_LoLim and output at the
output parameter MV. Reaching the limit is then displayed at the output parameter MV_HiAct
= 1 for the high limit and MV_LoAct = 1 for the low limit.
Interconnecting the output parameter ManHiOut or ManLoOut to MV_HiLim or MV_LoLim
allows the automatic manipulated variable limits to tracked to manual manipulated variable
limits. You can keep both limit pairs in synch and control the manual manipulated variable
limits in the faceplate.

Basics of APL
Limiting the value of a manipulated variable in manual mode

In manual mode, the manipulated variable is set to its manual manipulated variable limits as
specified by the input parameters ManHiLim and ManLoLim and output at the output
parameter MV.
See also
Forcing operating states (Page 115)

Basics of APL
1.2.5.8 Activating and limiting disturbance variable
Feedforward control and limitation

The feedforward control is used in order to compensate measurable disturbance variables,
such as temperature or pressure, that can have an effect on the process. In automatic mode,
the disturbance variable is added to the result of the PID algorithm.
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.
1.2.5.9 Structure segmentation at controllers
Structure segmentation at controllers

In order to avoid jumps at the manipulated value (controller output) during setpoint changes,
proportional and derivative actions can be switched into the feedback path. I.e.: The
proportional action (proportionally) and the derivative action are then only influenced by the
process value.
Switching proportional action into the feedback path

A proportion of the P action can be placed in the feedback using the PropFacSP parameter.
Setpoint jumps then only affect the derivative action proportionally.
PropFacSP = 0: Proportional action is completely in the feedback path
PropFacSP = 1: Proportional action is not in the feedback path (default setting)
,'

63 09

3URS
39 3
)DF63
3URS
3 )DF63

Basics of APL
Switching derivative action into the feedback path

The parameter DiffToFbk can be used to switch the D action into the feedback path.
Setpoint jumps then no longer affect the derivative action directly.
DiffToFbk = 0: Derivative action is not in the feedback path (default setting).
DiffToFbk = 1: Derivative action is in the feedback path.
63 , 0:
*DLQ(II
7,
'LII7R)EN
'
*DLQ(II
39B2XW

Basics of APL
1.2.6 Forcing operating states
Forcing operating states

The forcing of operating states function lets you set the function block into a different
operating state using interconnectable input parameters, regardless of the currently active
control. This can, for example, be:
● Forced tracking in closed-loop controllers
● Enabling and disabling at motors
● Opening and closing of valves
Forcing of operating states is only possible in the manual and automatic modes. Forcing
operating states has the highest priority over both operating modes.
Note
It is not possible to force operating states in local mode.
Forcing operating states at closed-loop controllers

In control engineering, this procedure is also known as forced tracking of values. Please also
refer to the section Tracking and limiting a manipulated value (Page 111).
Forcing operating states at motors and valves

The input parameter xxxxForce = 1 (for example OpenForce and CloseForce at a
valve) is used for forced controlling of the function block and thus an intervention in the
function of the block, irrespective of currently active controls and interlock conditions. If the
input parameters are inconsistent (for example OpenForce = 1 and CloseForce = 1 at
valves), an error number (Page 117) is output at the parameter ErrorNum and the control
remains unchanged.

Basics of APL
Display in the faceplate and in the block icon

If an operating state is forced, this is displayed in the block icon and in the standard view of
the faceplate:
Block icon: In the block icon, the display for motors, valves and dosers involves the use of a
red F and a crossed-out padlock.
There is no display for closed-loop controllers.
Faceplate: An information text on the forced operating state is displayed in the standard view
of the faceplate, for example, "Forced stop" at motors. This is also indicated by a crossed-
out padlock:
Messaging
No messages are assigned to the forcing of operating states. However, if you want to have
corresponding messages, you can use the freely interconnectable input parameters to
generate the messages. See also the Generating instance-specific messages (Page 46)
section for more on this.

Basics of APL
1.2.7 Error handling
Error handling
The driver and technological blocks feature error handling routines. A distinction must be
made between the following areas:
● Error numbers
● External control system fault (CSF)
● Process-specific errors
● Invalid signal states
● Mode changeover error
● Error in channel driver blocks (e.g. Pcs7AnIn)
● Error in channel driver blocks (e.g. FbAnIn)
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.
External control system fault (CSF)

An external control system fault always lies outside the process - it exists in the form of
device or other hardware faults. If, for example, a run-time error occurs at a valve, there is an
error or fault in the pneumatic system.
A control system fault is output if an external fault is set at the input CSF. You can enable this
output function, for example, by interconnecting output Bad of the driver block with input CSF
of the technological block.
The error message "$$BlockComment$$ External error occurred" is output at CSF = 1.
This state is visualized in the group display by an "S" character in the faceplate overview and
in the block icon.

Basics of APL
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: Please refer to the section Monitoring the feedbacks (Page 83).
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.
Invalid input signals

This error is output if inconsistencies are detected between associated I/Os. The close and
open commands cannot be output simultaneously to the valve, for example.
If the block algorithm detects an invalid combination of input signals, an error number
(ErrorNum) is output that depends on the block type.
The text "Invalid signal" is output in the standard view of the faceplate.
Mode changeover error

This error is reported if you change the mode of the block from:
● Manual to automatic mode or
● Local mode to automatic mode
and the previous and target state are inconsistent (bumpless changeover). You can only
change the block mode if the subsequent state corresponds with the previous state.
Bumpless changeover can be activated / deactivated using the Feature connection on the
Enabling bumpless changeover to automatic mode for valves, motors, and dosers
(Page 197) or Disabling bumpless changeover to automatic mode for controllers (Page 197)
bit.
Bumpless changeover from local to automatic mode is undertaken using the
LocalSetting parameter, as described in section Local mode (Page 36).
In the standard view of the faceplate, the text "Mode switch fail" is displayed in the event of
an unwanted changeover with bumps.
The block retains local mode if the operator changes the mode from local to automatic and
the error mentioned above occurs. The block changes to manual mode if the mode is
changed from local to automatic over interconnected inputs and the error mentioned above
occurs.

Basics of APL
Error in channel driver blocks (e.g. Pcs7AnIn)

The following errors can be displayed by the channel driver blocks:
● Channel error
● Higher-level error
● Invalid measuring range
Error in channel driver blocks (e.g. FbAnIn)

The following errors can be displayed by the driver blocks:
● Device or module fault
● Higher-level error
● Invalid measuring range
1.2.8 Resetting the block in case of interlocks or errors
Resetting the block

A block reset is only relevant in automatic mode. It has no influence in manual mode or in
local mode and is disabled in these modes.
The block must be reset when an interlock has been set via the Protect input or an error
has occurred.
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 change in the relevant automatic signal.
The operator must have the appropriate authorization to use the reset function in the
faceplate (OS_Perm). To enable a block reset via the 0-1 edge change in the automatic
signal, the response must be set in the parameters for the Feature bit Resetting via input
signals in the event of interlocks or errors (Page 194). Refer to the relevant block description.

Basics of APL
1.2.9 Safe position for motors, valves and controllers
Safe position for motors, valves and controllers

The safe position always represents the deenergized state.
Safe position for motors

Safe position for motors is always the stopped motor.
Safe position for valves

There are different forms of the deenergized state for valves:
● Valve is closed at a deenergized state
● Valve is open at a deenergized state
● Valve is stopped at a deenergized state (motor valve)
The input parameter SafePos is used to set these properties of the valve:
● SafePos = 0: Valve is closed at a deenergized state
● SafePos = 1: Valve is open at a deenergized state
● SafePos = 2: Valve is stopped in a deenergized state (motor valve)
The safe position is adopted when:
● The runtime monitoring function was addressed (see Setting the startup response
(Page 187))
● One of the interlock conditions is active (see Interlocks (Page 100))
The safe position is adopted if at least one of these interlock conditions is present
("Protection" [Protect] or "Interlock" [Intlock], see Interlocks (Page 100)).
Note
The motor valve will not be put into the safe position for monitoring errors (Runtime error and
Control error).

Basics of APL
Safe position for continuous controller (does not apply to controller modules)
Only the limits for the manual value are taken into consideration for the safe position with
continuous controllers. The input parameter SafePos is used to specify the safe position:
● SafePos = 0 corresponds to the low limit (ManLoLim)
● SafePos = 1 corresponds to the high limit (ManHiLim)
The safe position is adopted:
● during start-up if the Feature bit Setting the startup response (Page 187) and the
Feature bit Safety value of the manipulated variable effective at startup (Page 196) are
set.
● in the "Out of service" mode if the Feature bit Safety manipulated variable with "out of
service" operating mode in effect (Page 196) is set.
Safe position for step controller (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 travels to the safe position:
SafePos = 0: close valve
SafePos = 1: open valve
SafePos = 2: stop valve
When the safe position (fully opened or fully closed) is reached and a limit signal
(FbkOpened or FbkClosed) is set, the valve is stopped (Stop = true).
The safe position is adopted:
● during start-up if the Feature bit Setting the startup response (Page 187) and the
Feature bit Safety value of the manipulated variable effective at startup (Page 196) are
set.
● in the "Out of service" mode if the Feature bit Safety manipulated variable with "out of
service" operating mode in effect (Page 196) is set.
Safety control for controllers of the FM 355 or FM 355-2 modules

The controller modules have their own mechanism for feedforwarding a safety value (see
Temperature Controller FM 355-2 manual or Controller Module FM 355 manual)

Basics of APL
1.2.10 Specifying warning times for control functions at motors and valves
Specifying warning times for control functions at motors and valves

You can generate warning signals when, for example, motors are started or valves are
opened. Warning signals can be generated in the following modes:
● Manual mode (input parameter WarnTiMan)
● Automatic mode (input parameter WarnTiAut)
You specify the warning times in seconds using the input parameters WarnTiMan and
WarnTiAut. If, for example, a motor is started then, this is displayed at the output parameter
with WarnAct = 1. The motor then starts after the set warning time has expired.
A corresponding warning is not output if the warning times (WarnTiMan or WarnTiAut) are
specified with a smaller value than the SampleTime parameter.
Disabling warnings
Configure each parameter with 0 seconds to generate no warnings.
1.2.11 SIMATIC BATCH functionality
SIMATIC BATCH functionality

Some blocks have an interface to SIMATIC BATCH. You use them when you connect
BatchEn, BatchID, BatchName, StepNo and Occupied I/Os to the corresponding
SIMATIC BATCH blocks. Refer to the SIMATIC BATCH documentation.
Please refer to the descriptions of the individual blocks for information about whether a block
supports the SIMATIC BATCH functionality.

Basics of APL
1.3 General functions of the faceplates
1.3.1 Structure of the faceplate
General functions of the faceplates

This section provides general information that applies to all faceplates.
Recommended screen resolution

The faceplates are shown in full on the screen with a resolution of 1280 x 1024.
Use the F11 key to switch to full screen mode if the screen resolution is set lower.
Opening the faceplate

Click on the block icon in WinCC to open the faceplate with the standard view; in this
example this is the standard view of PIDConL:
2SHUDWLQJPRGH 0DQXDO
6HWSRLQW ([WHUQDO

3URFHVVYDOXH r&
6HWSRLQW r&

0DQLSXODWHGYDULDEOH
5HDGEDFNYDOXH

6LPXODWLRQ
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.

Basics of APL
Displays and operator controls

The faceplate provides the following display and operator controls:

(1) Group display
(2) Lock alarms
(3) Suppress alarms
(4) Acknowledge alarms
(5) Worst signal status
(6) Batch display
(7) Not used
(8) Maintenance request and release
(9) Memo display
(10) Open views of the block
(11) Return to block icon
(12) Pin block
(13) Instance name of the block
(1) Group display

The group display shows the information that is transferred from ALARM_8P of the block
instance to WinCC.
● Alarms
● Warnings
● Tolerances
● Faults
● Operator prompts

Basics of APL
(2) Lock/unlock alarms

You can use this button to lock or unlock block alarms.
If you lock the alarms of the block, it is shown in the group display of alarms as a white x.
When alarms are locked, the block instance does not send any new alarms. Previous alarms
are also no longer displayed in the alarm view of the faceplate.
The alarms are displayed again in the group view when you unlock the block's alarms. The
block instance then resumes sending new alarms. Alarms generated in the locked phase are
displayed when you enable the alarm function.
You can hide this button from specific users / user groups using the permissions in PCS 7-
OS. Refer to the PCS 7-OS help system.
(3) Suppress alarms

Alarm suppression indicates whether or not the "Suppress process alarms" function in the
AS block is activated with the MsgLock parameter. If alarm suppression is activated, all
alarms in this block instance – except for process control alarms – are suppressed.
(4) Acknowledge alarms

You can acknowledge all alarms from the block instance using this button.
You can hide this button from specific users / user groups using the permissions in PCS 7-
OS. Refer to the Process Control System PCS 7; OS Process Control documentation for
more on this.
(5) Display for worst signal status

This display shows the worst signal status currently present. Refer to the Forming and
outputting signal status for blocks (Page 88) section for more on this.
(6) Batch display

The batch display shows whether or not the block instance is in use by SIMATIC BATCH.
Refer to the SIMATIC BATCH functionality (Page 122) section for more on this.
(7) Not used

This field is currently not used.
(8) Maintenance request and release

This display shows you if a maintenance request or release has been made for this block.
Refer to the Maintenance release (Page 47) section for more on this.
(9) Memo display

This display shows you if a message has been left in the memo view for you. Refer to the
Memo view (Page 171) section for more on this.

Basics of APL
(10) Open views of a block

You can use this field to open the various views of a block. Refer to the block description to
learn of the available views.
You can select from the following typical views here:
Icon Term
Standard view
Alarm view
Limits view (several limit value views within a block are possible)
Trend view
Ramp view
Parameter view (several parameter views within a block are possible)
Preview
Memo view
Batch view
Note
Some blocks feature block-specific views. They are not listed here.
(11) Return to block icon

Use this button to return to the block icon in the process image of the corresponding
faceplate. You can use this function, for example, when you have pinned a block (12) and
the process picture has changed in the meantime.
(12) Pin block

You can pin the faceplate on top of the user interface using this button. This allows you to
switch to another picture or area without closing the faceplate.
Note
You can learn about additional operator controls in the descriptions of the individual blocks.

Basics of APL
1.3.2 Switching operating states and operating modes
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).
6HWSRLQW ([WHUQDO

3URFHVVYDOXH r&
6HWSRLQW r&

0DQLSXODWHGYDULDEOH
5HDGEDFNYDOXH

6LPXODWLRQ
2SHUDWLQJPRGH
$XWRPDWLF 0DQXDO 3URJUDP

2XWRIVHUYLFH
([HFXWLRQ 2. &DQFHO


Basics of APL
(1) The mouse pointer changes when you place it over the following button:
The mouse pointer now looks as follows:
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.
(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.

Basics of APL
1.3.3 Changing values
Requirements
You can change the values in faceplates and in the block icons if you have the
corresponding operator control permission (OS_Perm). This operator control permission can
be configured in the engineering system (ES). The following example shows how values are
changed via the faceplate.
9DOXH

$GGLWLRQDOYDOXH r&

(QDEOHRSHUDWLRQV $GGLWLRQDOYDOXHOLPLWV
+DODUP r&
+ZDUQLQJ r&
+\VWHUHVLV r&
/ZDUQLQJ r&
/DODUP r&
+ZDUQLQJ

'LUHFWFRQWURO

([HFXWLRQ 2. &DQFHO

(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.

Basics of APL
How to change values in faceplates

You have three options for changing values:
● Direct control: Click on a button such as "-2.5" in the box (6). The value is immediately
changed and applied. It is no longer necessary to confirm this value.
● Changing values using the slide control (5): move the slide control until the desired value
is shown in the box. Then confirm the value using the enter key or by clicking "OK". Read
the section "Setting the multiple step operation".
● Change the values in the input box (4): Click the input box and enter the new value. Then
confirm the value using the enter key or by clicking "OK". Read the section "Setting the
multiple step operation".
Setting the multiple step operation

You can use the internal @APLCommandExecutionSteps tag in the Tag Management of the
WinCC Explorer to specify if values are to be changed in two or three steps.
Follow the steps outlined below:
1. Double-click on the internal @APLCommandExecutionSteps tag
2. Change the start value to 2 or 3 in the Limits/Reporting tab.
Start value = 2: It is no longer necessary to confirm the value in the faceplate by clicking
"OK", values are applied immediately.
Start value = 3: Each value change in the faceplate, except for direct operation, needs to
be confirmed with "OK".

Basics of APL
1.3.4 Standard view of FM controllers (analog)
Standard view (analog) of FM controllers


6HWSRLQW ,QWHUQDO

(5
3URFHVVYDOXH r&

6HWSRLQW r&

0DQLSXODWHGYDULDEOH
5HDGEDFNYDOXH

)DFHSODWH &RQWUROSHUIRUP
(1) Display and switch the operating mode

This area provides information on the currently valid operating mode. The following operating
modes can be shown here:
● Manual mode (Page 29)
● Automatic mode (Page 29)
● Program mode for closed-loop controllers (Page 34)
● Out of service (Page 27)
Refer to the Switching operating states and operating modes (Page 127) section for
information on switching the operating mode.

Basics of APL
(2) Display and switch the setpoint specification

This area shows how to specify the setpoint. The setpoint can specified as follows:
● By the application (External, CFC/SFC)
● By the user direct in the faceplate (Internal).
information on changing the setpoint specification.
For more information on the setpoint specification, refer to the Setpoint input - internal and
external (Page 96) section.
(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.
(4) Display of the process value including signal status

This area provides information on the current process value (PV) with the corresponding
signal status.
(5) Display and change the setpoint including signal status

This area provides information on the current setpoint (SP) with the corresponding signal
status.
Refer to the Changing values (Page 129) section for information on changing the setpoint.
The setpoint specification (2) also needs to be set to "Internal" for this block.
(6) High and low scale range for the setpoint

This area is already set and cannot be changed.
(7) Display and change the manipulated variable including signal status
This area provides information on the current manipulated variable (MV) with the
corresponding signal status.
Refer to the Changing values (Page 129) section for information on changing the
manipulated variable. You can only make a change in manual mode.
(8) Display of the position feedback including signal status

This area provides information on the current readback value of the manipulated variable
with the corresponding signal status. This display is only available when the readback value
in the box is interconnected to the Rbk input parameter.

Basics of APL
(9) Bar graph for the manipulated variable

This area provides information on the current manipulated variable in the form of a bar graph
(MV_OpScale). The visible area in the bar graph depends on the configuration in the
(10) Bar graph for the position feedback

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).
See also the Calling further faceplates (Page 43) section 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).
(13) Display area for states of the block

This area provides additional information on the operating state of the block:
● Maintenance
Additional information on the display area for states of the block is available in section
Maintenance release (Page 47).

● Simulation
Additional information is available in the section Simulating signals (Page 93).

This area provides additional information on the operating state of the block (from high to low
according to priority):
● Fuzzy Optim. (FmCont only)
● Tracking FB
● Tracking FM
● Safe position FM
● Fuzzy control (FmCont only)

Basics of APL
(16) Limit display

These colored triangles indicate the configured limits in the respective bar graph:
● Red: Alarm
● Yellow: Warning
● Blue: Tolerance
(17) Bar graph for the process value

This area shows the current process value in the form of a bar graph. The visible area in the
bar graph depends on the configuration in the engineering system (ES).
(18) Bar graph for the setpoint

This area shows the current setpoint in the form of a bar graph. The visible area in the bar
graph depends on the configuration in the engineering system (ES).
(19) Display for external setpoint

This display [E] is only visible when you have selected "internal" setpoint specification. It
shows the external setpoint that would apply if you were to change the setpoint specification
to "external".
(20) Display for the target setpoint of the setpoint ramp

This display [R] shows you the target setpoint and is only visible if you have enabled ramp
generation in the Ramp view (Page 167).
(21) Limit display for the setpoint

These triangles show the SP_HiLim and SP_LoLim setpoint limits configured in the ES.

Basics of APL
1.3.5 Standard view of FM controllers (pulse controller)
Standard view (pulse) of FM controllers


6HWSRLQW ,QWHUQDO

(5
3URFHVVYDOXH r&

6HWSRLQW r&

0DQLSXODWHGYDULDEOH
$FWXDWLQJVLJQDOV 2SHQ
5HDGEDFNYDOXH



Basics of APL


signal status.

status.

This area provides information on the current manipulated variable (MV) with the
(8) Display of the actuating signal

This area shows the current feedback of the actuating signal.
● Open
● Close

Basics of APL

This area shows the current feedback of the manipulated variable with the corresponding
signal status. This display is only available when the readback value in the box is
interconnected to the Rbk input parameter.


See the section Calling further faceplates (Page 43) for more information.

● Maintenance

● Simulation

Basics of APL

● Tracking FB
● Tracking FM
(17) Limit display

● Red: Alarm
● Yellow: Warning
● Blue: Tolerance



to "external".

This display [R] shows the target setpoint and is only visible if you have enabled ramp


Basics of APL
1.3.6 Standard view of FM controllers (step controller with position feedback)
Standard view with position feedback of FM controllers


6HWSRLQW ,QWHUQDO

(5
3URFHVVYDOXH r&

6HWSRLQW r&

0DQLSXODWHGYDULDEOH
$FWXDWLQJVLJQDOV 6WRS
5HDGEDFNYDOXH



Basics of APL


signal status.

status.

This area provides information on the current manipulated variable (MV)with the
(8) Display of the actuating signal

● Open
● Stop
● Close

Basics of APL

This area shows the current feedback of the manipulated variable with the corresponding
signal status. This display is only available when the readback value in the box is
interconnected to the Rbk input parameter.



● Maintenance

● Simulation

Basics of APL

● Tracking FB
● Tracking FM
(17) Limit display

● Red: Alarm
● Yellow: Warning
● Blue: Tolerance



to "external".



Basics of APL
1.3.7 Standard view of FM controllers (step controller without position feedback)
Standard view without position feedback of FM controllers


6HWSRLQW ,QWHUQDO

(5
3URFHVVYDOXH r&

6HWSRLQW r&

$FWXDWLQJVLJQDOV 6WRS
/LPLWVWRSVLJQDO &ORVHG



Basics of APL


signal status.

status.
(6) Operating and displaying the actuating signal

● Open
● Stop
● Close
The button is shown next to the display in manual mode. You can influence the actuating
signal here. Refer to the Switching operating states and operating modes (Page 127) section
for more on this.
(7) Display of the limit stop value including signal status

This area shows the limit stop signal with the corresponding signal status.
● Open
● Closed

Basics of APL

● Maintenance

● Simulation

● Tracking FB
● Tracking FM
(13) Limit display

● Red: Alarm
● Yellow: Warning
● Blue: Tolerance

Basics of APL



to "external".



Basics of APL
1.3.8 Standard view of interlock blocks
Standard view of interlock blocks Intlck02, Intlck04, Intlck08, Intlck16

The number of the displayed input values depends on the interlock block you have selected.
The operation and functions are identical for all interlock blocks and do not depend on the
number of input values.
The Intlck16 interlock block has two additional buttons for switching between the input
values 1 to 8 and 9 to 16.

9DOXH

>8QLW@

9DOXH

>8QLW@
9DOXH
>8QLW@
9DOXH

>8QLW@

9DOXH

>8QLW@
9DOXH

>8QLW@

9DOXH

>8QLW@
)DFHSODWH 5HVHW
(1), (10) Switching among the input values 1 to 8 and 9 to 16 (for Intlck16 only)
The buttons (1) or (9) are displayed depending on the view you are in. These buttons are
only available for the Intlck16 block.
The Intlck16 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 (9) button.
● 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).

Basics of APL
(2) Status of the output signal of the interlock block

This area (2) shows the status of the output signal of the interlock block (priority from high to
low). You can configure the logic in the engineering system (ES).
Logic
Color of the field AND OR
Gray Interlock signal not used by the technological
block.
Blue Excluded (bypass)
Yellow Simulated
Red Interlocked
Green Not interlocked
(3) Exclude input values

You can use the button (3) to exclude input values from processing. Depending on the
previous settings, you can Set or Reset this property.
If the input value has been excluded, the following icon appears in the field (8):
For more information on the operation, refer to the section Switching operating states and
operating modes (Page 127).
(4) Status display First in

The following icon is displayed next to an input value, if this input value has caused the last
output signal change from 1 to 0 (good state to locked):
You can reset the first-in (initial) signal with the button (10).
You can find additional information on this in the Recording the first signal for interlock
blocks (Page 87) section.
For more information on the operation, refer to the section Switching operating states and
operating modes (Page 127).
(5) Open faceplate of the output value

When you press the button (5), you can open the faceplate associated with the output value.
The function of this button depends on the configuration in the engineering system (ES). See
also the Calling further faceplates (Page 43) section for more on this.

Basics of APL
(6) Status of the block output

The line color indicates the status of the block output:
Color of the line Output status

Green Output is enabled
Gray Output is disabled
(7) Output of the signal status

This field shows you the signal status provided with the output signal of the interlock block.
(8) Display the status for further processing

The icon shows the status for further processing of the input values:
Icon Further processing

The input value will be further processed
(value=1).
The input value is excluded from further
processing.
The input value is not connected (value=0).
(9) 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"
Changing the display

You can change the displays for 0 and 1 in the CFC in the object properties of the Interlock
block:
● Navigate to the I/Os (object properties).
● Change the default for the input parameters (Inxx) in the Text 0 and Text 1 columns to
what you later want to see in runtime.
(10) Switching input values

Read point (1) for this.

Basics of APL
(11) Reset the settings for further processing

When you press the button (10), you can Reset all input values:
● Reset exclusions: the exclusions of the input values are reset.
● Reset first in: First-in detection / status display (4) is reset.
You can find additional information on this in the Recording the first signal for interlock
blocks (Page 87) section.
You can find additional information on this in the Calling further faceplates (Page 43) section.
(13) Displaying analog input values

The interconnected analog input values (AVxx) are displayed in this area. Set a unit of
measure (AVxx_Unit as shown in the picture with [Unit]) for each input in the engineering
system (ES).
Changing the display

You can change the displays for 0 and 1 in the CFC in the object properties of the Interlock
block:
● Navigate to the I/Os (object properties).
● In the Identifier column, change the default for the input parameter (AVxx) to what you
later want to see in runtime.
The number of input values may vary depending on the selected interlock block:
● Intlck02: input values 1 and 2 are available.
● Intlck04: input values 1 to 4 are available.
● Intlck08: input values 1 to 8 are available.
● Intlck16: 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).
(14) Open faceplate of the input value

When you press the button (13), you can open the faceplate associated with each input
value. The function of this button depends on the configuration in the engineering system
(ES). See also the Calling further faceplates (Page 43) section for more on this.

Basics of APL
1.3.9 Parameter view of PID controllers
Parameter view of PID controllers
(QDEOHRSHUDWLRQV 6HWWLQJV
3,'RSWLPL]DWLRQ
63 39LQPDQXDOPRGH
63 63H[WHUQDO
3DUDPHWHU
*DLQ
,QWHJUDODFWLRQWLPH V
'HULYDWLYHWLPH7' V
'HULYDWLYHJDLQ
'HDGEDQG r&
&RQWURO]RQH r&

0RWRUDFWXDWLQJWLPH V
0LQLPXPSXOVHWLPH V
0LQLPXPEUHDNWLPH V
6HUYLFH
6LPXODWLRQ 2II

0DLQWHQDQFHUHOHDVH 1R
*DLQ6FKHG
(1) Enable operations

This area shows all operations for which special operator control permissions are assigned.
They depend on the configuration in the engineering system (ES) that applies to this block.
Symbols for the operator control enables:
● Green check mark: the OS operator can control this parameter
● Gray check mark: the OS operator cannot control this parameter at this time due to the
process
● Red cross: the OS operator cannot control this parameter due to the configured operator
control permissions.

Basics of APL
(2) Settings
You can activate the following functions for the controller in this area:
● PID optimization: ☑ activate controller optimization
● 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 189) to 1.
(3) Parameter
In this area, you change parameters and therefore influence the controller. Refer to the
Changing values (Page 129) section for more on this.
You can influence the following parameters:
● Gain: Proportional gain
● Integral action time: Integral action time in [s]
● Derivative action 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 (only with PIDConL block)
● Motor actuating time: Motor actuating time [s] (for PIDStepL block only)
● Minimum pulse time: Minimum pulse time [s] (for PIDStepL block only)
● Minimum break time: Minimum break time [s] (for PIDStepL block only)
(4) Service
You can select the following functions in this area:
● Simulation
● Maintenance release (with display for a maintenance request)
Refer to the Switching operating states and operating modes (Page 127) section for more on
this.
You can find information on this area in the section:
● Simulating signals (Page 93)
● Maintenance release (Page 47)
(5) Navigation button for the GainSched block

You can use this navigation button to reach the GainSched block configured in the

Basics of APL
1.3.10 Parameter view of FM controllers
Parameter view of FM controllers
63 39LQPDQXDOPRGH
63 63H[WHUQDO
3DUDPHWHU
*DLQ
,QWHJUDODFWLRQWLPH V
'HULYDWLYHWLPH7' V
'HULYDWLYHJDLQ
'HDGEDQG r&
&RQWURO]RQH r&

0RWRUDFWXDWLQJWLPH V
0LQLPXPSXOVHWLPH V
0LQLPXPEUHDNWLPH V
6HUYLFH
6LPXODWLRQ 2Q

0DLQWHQDQFHUHOHDVH <HV
*DLQ6FKHG

process

Basics of APL
(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) Parameter
● Gain: Proportional gain
● Integral action time: Integral action time in [s]
● Derivative action 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 FmTemp block only)
● Motor actuating time: Motor manipulating time [s]
● Minimum pulse time: Minimum pulse duration [s]
● Minimum break time: Minimum break time [s]
(4) Service
● Simulation
this.
(5) Navigation button for the GainSched block

You can use this navigation button to reach the GainSched block configured in the

Basics of APL
1.3.11 Parameter view for motors and valves
Parameter view of motors
(QDEOHRSHUDWLRQV 0RQLWRULQJ
&RQWURO V

5XQ7LPH V
0RQLWRULQJ
6HUYLFH
6LPXODWLRQ 2II
0DLQWHQDQFHUHOHDVH 1R

process
(2) Monitoring
In this area, you change parameters and therefore influence the motor. Refer to the
● Control: Monitoring time during startup and shutdown of the motor (dynamic)
● Runtime: Monitoring time during permanent operation of the motor (static)
Enable monitoring
You can enable monitoring by clicking the check box (☑)
You can find additional information on this in the Monitoring the feedbacks (Page 83)
section.

Basics of APL
(3) Service
● Simulation
this.

Basics of APL
1.3.12 Limit value view of FM controllers
Limit value view of FM controllers

Several values are set in this view by default:
● Process value limits
● Control error limits
● Readback value limits
● Setpoint operation range
The toolbars of the faceplate and the block icon indicate when the limit(s) is reached or
exceeded.
(QDEOHRSHUDWLRQV 3URFHVVYDOXHOLPLWV 39
+DODUP r&
+ZDUQLQJ r&
+WROHUDQFH r&
+\VWHUHVLV

/WROHUDQFH r&
/ZDUQLQJ r&
/DODUP r&
&RQWUROHUURUOLPLWV (5
+DODUP r&
+\VWHUHVLV

/DODUP r&
5HDGEDFNYDOXHOLPLWV 5EN
+ZDUQLQJ
+\VWHUHVLV
/ZDUQLQJ
6HWSRLQWRSHUDWLRQUDQJH 63
+UDQJH r&

/UDQJH r&
0DQLSXODWHGYDULDEOHRSHUDWLQJUDQJH 09
+UDQJH

/UDQJH

Basics of APL

process
control permissions
(2) Process value limits

In this area, you can enter the limits for the process value. Refer to the Changing values
You can change the following limits:
● H alarm: Alarm high
● H warning: Warning high
● H tolerance: Tolerance high
● Hysteresis
● L tolerance: Tolerance low
● L warning: Warning low
● L alarm: Alarm low
(3) Control error limits

In this area, you can enter the limits for the control error. Refer to the Changing values
● Hysteresis
(4) Readback limits (Rbk)

In this area, you can enter the limits for the readback value. Refer to the Changing values
● Hysteresis

Basics of APL
(5) Setpoint operation range (SP)

In this area, you can enter the limits for the setpoint operation range. Refer to the Changing
values (Page 129) section for more on this.
● H range: Range limit high
● L range: Range limit low
(6) Manipulated variable operating range (MV)

In this area, you can enter the limits for the manipulated variable operation range. Refer to
the Changing values (Page 129) section for more on this.

Basics of APL
1.3.13 Limit value view of PID controllers
Limit value view of PID controllers

Several values are set in this view by default:
● Process value limits
● Control error limits
● Readback value limits
● Setpoint operation range
exceeded.
(QDEOHRSHUDWLRQV 3URFHVVYDOXHOLPLWV 39
+DODUP r&
+ZDUQLQJ r&
+WROHUDQFH r&
+\VWHUHVLV

/WROHUDQFH r&
/ZDUQLQJ r&
/DODUP r&
&RQWUROHUURUOLPLWV (5
+DODUP r&
+\VWHUHVLV

/DODUP r&
5HDGEDFNYDOXHOLPLWV 5EN
+ZDUQLQJ
+\VWHUHVLV
/ZDUQLQJ
6HWSRLQWRSHUDWLRQUDQJH 63
+UDQJH r&

/UDQJH r&
0DQLSXODWHGYDULDEOHRSHUDWLQJUDQJH 09
+UDQJH

/UDQJH

Basics of APL

process
control permissions
(2) Process value limits

In this area, you can enter the limits for the process value. Refer to the Changing values
● Hysteresis
(3) Control error limits

In this area, you can enter the limits for the control error. Refer to the Changing values
● Hysteresis
(4) Readback limits (MV)

In this area, you can enter the limits for the readback value. Refer to the Changing values
● Hysteresis

Basics of APL
(5) Setpoint operation range (SP)

In this area, you can enter the limits for the setpoint operation range. Refer to the Changing
values (Page 129) section for more on this.
(6) Manipulated variable operating range (MV)

In this area, you can enter the limits for the manipulated variable operation range. Refer to
the Changing values (Page 129) section for more on this.

Basics of APL
1.3.14 Limit value view of motors
Limit value view of motors

The limit value view for motors is only available when an AV block has been interconnected
to the motor.
exceeded.

$GGLWLRQDOYDOXH r&

(QDEOHRSHUDWLRQV $GGLWLRQDOYDOXHOLPLWV
+DODUP r&
+ZDUQLQJ r&
+WROHUDQFH r&
+\VWHUHVLV
r&
/WROHUDQFH r&
/ZDUQLQJ r&
/DODUP r&

(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.
(2) Display of the additional value including signal status

This area shows the current additional value with the corresponding signal status.

Basics of APL
(3) Bar graph for the additional value

In this area, you can enter the limits for the additional value. Refer to the Changing values
● Hysteresis

process
control permissions
(5) Bar graph for the additional value

This area show you the current additional 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 colored triangles indicate the specified limits (3) for the additional value.

Basics of APL
1.3.15 Preview of FM controllers
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.
63H[WHUQDO r&

63LQWHUQDO r&
&RQWUROHUURU r&
3URJUDPPRGH r&
'LVWXUEDQFHYDULDEOH

7UDFNLQJ)0
7UDFNLQJ)%
7UDFNLQJYDOXH
6DIHW\PRGH
6DIHW\YDOXH
(QDEOHRSHUDWLRQV
&ORVH $XWRPDWLF
2SHQ 0DQXDO
6WRS 2XWRIVHUYLFH
63H[WHUQDO
63LQWHUQDO
&KDQJH63
&KDQJH09
3URJUDPPRGH
)DFHSODWH

Basics of APL
(1) Preview area

This area shows you a preview for the following values:
● SP external: currently applicable external setpoint
● SP internal: currently applicable internal setpoint
● Control error: Current control error
● Program mode: Specified value for program mode
● Disturbance: additive value for feedforward control
● Tracking FM: track a manipulated variable in the FM module (value is 1)
● Tracking FB: track manipulated variable at the driver block (value is 1)
● Tracking value: effective manipulated variable for "Track manipulated variable at driver
block"
● Safety mode: safety mode in the FM module (value is 1)
● Safety value: effective manipulated variable for "Safety mode"

process
control permissions

Basics of APL
1.3.16 Ramp view
Ramp view
(QDEOHRSHUDWLRQV
*UDGLHQWOLPLW
*UDGLHQW r& V

*UDGLHQW r& V
5DPSIXQFWLRQ *UDGLHQW
7LPHGXUDWLRQ V

7DUJHWVHWSRLQW r&

5DPS ,QDFWLYH

process
control permissions
(2) Gradient limit on

Use this check box to enable gradient limit of the setpoint. The gradient limit can be set
separately for positive or negative setpoint changes (Gradient + or Gradient -). Refer to the
(3) Ramp function

In this area, you can set the type of ramp function for the setpoint.
You can set the following types of ramp functions:
● Time duration
● Target setpoint
You can set the time duration and the target setpoint. Refer to the Changing values

Basics of APL
(4) Ramp on
You can use this control to enable or disable the configured function in the ramp function for
the setpoint change.
You can only enable this when the setpoint specification is set to "Internal" in the standard
view of the block. The enable is only valid for one setpoint change and is subsequently
disabled again.

Basics of APL
1.3.17 Message view
Alarm view
The alarm view is based on these areas:
(1) Toolbar
(2) Display area for alarms
(3) Status bar
For additional information about the alarm view, refer to the WinCC Information System
Online Help.

Basics of APL
1.3.18 Batch view
Batch view
Batch view appears as follows:
%DWFKDOORFDWLRQ
(QDEOHG
$OORFDWHG
%DWFKQDPH

%DWFK,'
%DWFKVWHS
(1) Enabled
This area show 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).
(3) Batch name

This area shows the name of the batch that is currently running (Batchname).
(4) Batch ID
This area shows the identification number of the batch that is currently running (BatchID).
(5) Batch step

This area shows the step number of the batch that is currently running (StepNo).

Basics of APL
1.3.19 Memo view
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.
1RWHV
$FWLYHPHPR
(1) Text box for notes

(2) Check box for activating the note
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.
Note
The content of the memo view is deleted when you perform a full compilation and download
of the OS.

Basics of APL
1.3.20 Trend view
Trend view
The trend view is based on these areas:
(1) Toolbar
(2) Display area for trends
(3) Status bar

For additional information about the trend view, refer to the WinCC Information System
Online Help.
You can switch between the online data and archive data using the first user button (number
1) in the toolbar. The status bar shows if the trend view is working with online data or archive
data.
Special considerations for controllers

You can select two different representations for the display area:
1. Detailed display (default setting):

Display area consisting of three coordinate systems:
● Setpoint, actual value trend;
● Manipulated variable, control performance index trend;
● Binary trend via automatic/manual, manipulated variable at high or low limit
Open the scatterplot diagram with the second user button (number 2) in the toolbar. It shows
a coordinate system with the process value on the value axis and the manipulated values or
position feedback on the X axis. A new value pair is entered into the coordinate system with
each cycle.
If you want to use the detail display, you need to enter the following in the block icon under
Trends in the WinCC Graphics Designer:
TrendPictureName = @pg_apl_trendPID_Statistic.pdl

Basics of APL
2. Simple display:
Display area consisting of two coordinate systems:
● Setpoint, actual value trend;
● Manipulated variable, control performance index trend;
If you want to use the detail display, you need to enter the following in the block icon under
Trends in the WinCC Graphics Designer:
TrendPictureName =@pg_apl_trendPID.pdl
Notes on step controllers with position feedback:

If you use a step controller with position feedback as the controller type, you need to enter
the following in the block icon under Trends in the WinCC Graphics Designer:
TrendConfiguration5 = *.MV#Value;...
TrendConfiguration6 = .RbkOut#Value;...
The following applies to all other controller types (default setting):

TrendConfiguration5 = .MV#Value;...
TrendConfiguration6 = *.RbkOut#Value;...

Basics of APL
1.4 General functions of the block icons
1.4.1 Block icon structure
Block icon structure

There are two types of block icons, those with a display of the instance-specific name and
those without:
Block icon of MotRevL with instance-specific name
Block icon of PIDConL with instance-specific name
Block icon of MotRevL 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 information that is actually available.
You can select one of these block icons. See section Configuring the block icons (Page 180)
for more information.
A block icon has several display areas:
● Instance-specific name
● Icon for the block
● Analog value display
● Status bar for the block status

Basics of APL
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: Left-click on the block icon while pressing
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 @PCS7TypicalsAPL.PDL or insert this button in
the "Key area" of WinCC. If you insert it into the key 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.
Icon for the block

Block icons for technological blocks have their own operable icons (for example, for the
MotRevL block) and represent a status display of the block.
0
This icon can be positioned at various locations, 0°, 90°, 180° and 270°. Refer to the
Configuring the block icons (Page 180) 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 181) section for more on this.
Analog value display

For block icons with analog value displays (for example, for the PIDConL block), there are
four basic settings that differ depending on the analog value display and the display of the
associated unit of measure.
Refer to the Configuring the block icons (Page 180) section for more on this.
These analog values can be controlled according to the Operator permissions (Page 45).
See also the Operation via the block icon (Page 181) section for more on this.

Basics of APL
Status bar for the block status

The status bar of the block icon provides an overview of the overall status of the block (see
figure below).
The arrangement of icons in the following tables is prioritized from high to low.
The following elements can be displayed:
Alarms, warnings, tolerances, and messages

Refer to the Monitoring functions at the Advanced Process Library (Page 70) section for
more on this.
Icon Meaning
No messages are output.
A fault has occurred.
An alarm is triggered.
An alarm for the high alarm limit is triggered.
An alarm for the low alarm limit is triggered.
An warning is triggered.
An warning for the low alarm limit is triggered.
An warning for the high alarm limit is triggered.
A tolerance violation has occurred.
An tolerance violation for the high tolerance limit has been triggered.
An tolerance violation for the low tolerance limit has been triggered.
The block has an operator prompt.
There is a process status determination.

Basics of APL
Operating modes
Refer to the Overview of the modes (Page 25) section for more on this.
Icon Meaning
The block is in automatic mode.
The block is in the "On" operating mode.
The block is in manual mode.
A program is running.
The block is in local mode.
The block is in the "Out-of-service" operating mode.

In this operating mode, no other icons are displayed and no values are shown in the
analog value display except for:
- Display for an active message in the memo view
- Display for the maintenance enable
Internal or external setpoint

Refer to the section Setpoint input - internal and external (Page 96).
Icon Meaning
Internal setpoint specification
External setpoint specification

Basics of APL
Signal status
Refer to the Forming and outputting signal status for blocks (Page 88) section for more on
this.
Icon Meaning
The block is in simulation.
Signal status is "Bad, device related".
Signal status is "Bad, process related".
Signal status is "Uncertain, device related".
Signal status is "Uncertain, process related".
A maintenance request is pending.
Block is released for maintenance
Tracking and forcing of values and bypasses

See sections Forcing operating states (Page 115) , Interlocks (Page 100) and Manual and
Automatic mode for control blocks (Page 29).
Icon Meaning
At least one value has been forced
Value is tracked
There is a bypass of an interlock or a bypass condition of an upstream Intlock FB.
Interlocks
Refer to the Interlocks (Page 100) section for more on this.
Icon Meaning
Block is not interlocked.
Block is interlocked.
Bypass protection

Basics of APL
Memo display
Icon Meaning
A message is available in the memo view.
See also
Trip function (Page 102)
Forming the group status for interlock information (Page 105)

Basics of APL
1.4.2 Configuring the block icons
Configuring the block icons

There are two ways to configure your block icons:
● Automatically
● Manually
Automatic configuration of block icons

There is a variety of block icons, which you can select for a block. You select a block icon by
entering the number of the block icon in the field OCM possible > Create block icon in the
object properties of the block instance:
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 picture for automatic generation of block icons is @PCS7TypicalsAPL.PDL.
Additional information
● Manual Process Control System PCS 7; Engineering System
Manual configuration of block icons

You can configure block icons manually by copying the @TemplateAPL.PDL template and
inserting it into plant pictures.
The connection to the process tag is established with the "Connect faceplate with process
tag" Wizard, see WinCC Information System, section "Making Process Pictures Dynamic"
and "Standard Dynamics".
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.

Basics of APL
1.4.3 Operation via the block icon
Operation via the block icon

The block icon can be used to operate all elements displayed there if a relevant operator
control permission (OS_Perm) is available. This operator control permission can be
configured in the engineering system (ES).
The operation is performed by right-clicking on the element involved. The operable elements
in the block icon include:
● Switching the operating mode
● Internal and external setpoint specification
● Changing the process value, setpoint and manipulated variable
● Changing the operating state
The operation is then performed in the same way as in the faceplate. Refer to the section
Switching operating states and operating modes (Page 127) as well as Changing values
(Page 129).
1.4.4 Block icons for PID and FM controller
Block icons for PID and FM controller

A variety of block icons are available with the following functions:
● Process tag type
● Limits (high/low)
● Violation of alarm, warning, and tolerance limits as well as the control system fault CSF
● Operating modes
● Signal status, maintenance release
● Memo display
● Process value (black, with and without decimal places)

Basics of APL
● Setpoint (blue, with and without decimal places)

● Feedback value (red, with and without decimal places)
Icons Selection of the block icon in Special features

CFC
1 Block icon in the full display

Basics of APL

CFC
- Block icon in the "Out of
service" mode (example with
type 1 block icon)
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 180)
● Block icon structure (Page 174)
● Operation via the block icon (Page 181)

Basics of APL
1.4.5 Block icon for interlock blocks
Properties of the block icon for interlock blocks Intlk02, Intlk04, Intlk08, Intlk16
● Signal status
● Memo display
● Output signal
Icons Selection of the block icon in Block icon for

CFC
1 Intlk02
1 Intlk04
1 Intlk08
1 Intlk16
2 Intlk02
2 Intlk04
2 Intlk08
2 Intlk16
3 Intlck02
3 Intlck04
3 Intlck08
3 Intlck16
Block icons (mini) without display of instance-specific names

These icons only show the output signal. They take the form of a small rectangle.

Basics of APL
Display of the output signal

The display can show the following states for the output signal (priority from high to low):
● Gray: No inputs interconnected at the interlock block, the block is not used
● Blue: The output signal is 1, at least one input signal is bypassed. There is no gray state.
● Yellow: The signal status is 16#60; the output signal is simulated. There are no gray and
blue states.
● Red: The output signal is 0; there is an interlock. There are no gray, blue, and yellow
states.
● Green: The output signal is 1; the block is in the good state. There are no gray, blue,
yellow, and red states.
Addtional information on the block icon is available in the following sections:

Basics of APL
1.5 Selectable block response
1.5.1 Functions that can be set via the Feature I/O
Configurable functions with the Feature I/O

Some blocks have an input called Feature. This input can be used to influence the way in
which the block works.
The Feature bits are assigned in the following order:
Bit number Meaning

0 Setting the startup response (Page 187)
1 Reaction to the out of service mode (Page 199)
2 Resetting the commands for changing the mode (Page 193)
3 Enabling resetting of commands for the control settings (Page 193)
4 Setting switch or button mode (Page 195)
5 Specifying the dosing type (Page 189)
6 Resetting the dosing quantity when dosing starts (Page 194)
7 Enabling direct changeover between forward and reverse (Page 189)
8 Unit for the rate of change (Page 190)
9 Resetting via input signals in the event of interlocks or errors (Page 194)
10 Exiting local mode (Page 199)
11 Stopping dosing at a flow alarm (Page 187)
12 Automatic dribble correction for underdosing in automatic mode (Page 188)
13 Creep rate is always detected in the dosing quantity (Page 195)
14 Enabling rapid stop via faceplate (Page 192)
15 Safety manipulated variable with "out of service" operating mode in effect
(Page 196)
16 Safety value of the manipulated variable effective at startup (Page 196)
17 Enabling bumpless changeover to automatic mode for valves, motors, and dosers
(Page 197)
18 Disabling bumpless changeover to automatic mode for controllers (Page 197)
19 Enabling program mode (Page 192)
20 Activating bumpless changes to proportional gain (Page 196)
21 Switching operator controls for external setpoint to visible (Page 189)
22 Update acknowledgment and error status of the message call (Page 193)
23 - 26 Not allocated
27 Selecting values associated with messages (Page 192)
28 Output invalid raw value (Page 198)
29 Issuing substitute value if raw value is invalid (Page 190)
30 Issuing last valid value if raw value is invalid (Page 191)
31 Activating recording of the first signal (Page 191)

Basics of APL
1.5.2 Stopping dosing at a flow alarm
Stopping dosing at a flow alarm

You can use this feature bit to enable stopping dosing at a flow alarm.
The default setting is 0.
Bit = 0: Disabled, dosing is not stopped when a flow alarm occurs
Bit = 1: Enabled, dosing is stopped when a flow alarm occurs
1.5.3 Setting the startup response
Setting the startup response

With this Feature bit, you set the startup response of the function blocks, for example, for:
● Motors, valves and controllers
● Channel blocks
● Monitoring blocks, e.g. MonAnL and MonDiL.
● Mathematical, logical analog blocks and the OpAnL block
● The OpAnL block
● Counter blocks
● The Average block
Defining startup characteristics for motors, valves and controllers

Bit = 0: Starting the block in manual mode and in safe position. With controllers, the setpoint
is set to (SP_Int) internally. See also the Safe position for motors, valves and controllers
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.
Defining the startup characteristics for channel blocks

Bit = 0: The channel block uses either the process value PV_In or the value of SimPV_In
as the startup value, depending on the setting of the input parameter SimOn
(PV_In = PV_Out or SimPV_In = PV_Out).
Bit = 1: The channel block uses the value StartVal as the startup value
(StartVal = PV_Out).

Basics of APL
Defining the startup characteristics for monitoring blocks

Bit = 0: The most recently stored value is reset on startup.
Bit = 1: The most recently used value at the output parameter Out is output on startup.
Define startup characteristics for mathematical and logical analog blocks

Bit = 0: The Out output parameter is reset to 0 on startup.
Bit = 1: The most recently saved value is output at the Out output parameter on startup.
Defining startup characteristics for the OpAnL block

Bit = 0: The internal setpoint is used for startup.
Bit = 1: The most recently saved value is output at the Out output parameter on startup.
Defining the startup characteristics for counter blocks

Bit = 0: On startup, the counter is stopped and reset to the value specified in the PresetVal
input parameter (for the CountScL block) or PresetTime (for the CountOh block).
Bit = 1: On startup, counting continues with the most recently stored values.
Defining startup characteristics for the Average block

Bit = 0: At startup, averaging begins with the value that is currently at the input parameter
(Out = In, NumCycles = 1).
Bit = 1: When starting-up, the last Out and NumCycles values saved are used as the last
value for averaging (Out ≠ In).
1.5.4 Automatic dribble correction for underdosing in automatic mode
Automatic dribble correction for underdosing in automatic mode

Use this Feature bit to enable automatic dribble correction for underdosing in automatic
mode.
Bit = 0: Disabled, no automatic dribble correction is started for underdosing in automatic
mode.
Bit = 1: Enabled, automatic dribble correction is started for underdosing in automatic mode.

Basics of APL
1.5.5 Switching operator controls for external setpoint to visible
Switching operator controls for external setpoint to visible

Use this Feature bit to switch all operator controls for the external setpoint to visible in the
faceplates for the OS operator. This is always required when the external setpoint should
actually be used, for example, for slave controllers in cascade and ration controlling.
The default setting is 0, which keeps the faceplate as clear as possible for simple
applications.
Bit = 0: The operator controls for the external setpoint are not visible in the faceplate.
Bit = 1: The operator controls for the external setpoint are visible in the faceplate.
1.5.6 Enabling direct changeover between forward and reverse
Direct changeover between forward and reverse

With this Feature bit, you can enable direct reversal of the direction of motors.
Bit = 0: Direct reversal of the direction is disabled.
You can only change the direction of the motor by first stopping and starting the motor again
in the required direction. The motor can only be started again after the time set in the
IdleTime parameter has elapsed.
Bit = 1: Direct changeover is enabled.
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.
1.5.7 Specifying the dosing type
Specifying the dosing type

You can specify the dosing type to be used for the block using this Feature bit.
Bit = 0: Flow
Bit = 1: Scales

Basics of APL
1.5.8 Unit for the rate of change
Specifying the unit for the rate of change

You can use this Feature bit to specify the unit for the rate of change:
Bit = 0: unit for the rate of change in the unit of measurement to or from the field device
Bit = 1: unit for the rate of change as a percentage to or from the field device
1.5.9 Issuing substitute value if raw value is invalid
Output substitute value if raw value is invalid

Use this Feature bit to activate output of the substitute value for channel driver blocks
(input parameter SubsPV_In) if there is no valid raw value.
Bit = 0: The substitute value is not output.
Bit = 1: The substitute value is output. The signal status of the output value is set to "Local
functional check / simulation".
If there is no valid raw value the output parameter Bad = 1 is set automatically.
Prioritizing the Feature bits for driver blocks:

You need to configure three Feature bits for the response to an invalid raw value for the
driver blocks.
If more than one of these Feature bits are set (=1), the following priority applies:
● Output invalid raw value (Page 198) (Feature bit 28 = highest priority)
● Output substitute value if raw value is invalid (Feature bit 29)
● Issuing last valid value if raw value is invalid (Page 191) (Feature bit 30 = lowest
priority)
If none of the Feature bits 28, 29 and 30 are set (=0), the block sets Feature bit 28 (=1).

Basics of APL
1.5.10 Activating recording of the first signal
Activating recording of the first signal

Use this Feature bit to activate recording of the first signal with interlock blocks. Please
also refer to the section Recording the first signal for interlock blocks (Page 87).
Default setting is 0
Bit = 0: Recording of the first signal is deactivated.
Bit = 1: Recording of the first signal is activated.
1.5.11 Issuing last valid value if raw value is invalid
Issuing last valid value if raw value is invalid

Use this Feature bit to activate output of the last valid value for channel driver blocks if
there is no valid raw value.
Bit = 0: If there is no valid raw value the last valid value is not output.
Bit = 1: If there is no valid raw value the last valid value is output. The signal status of the
output value is set to Local "functional check / simulation".

driver blocks.
● Output invalid raw value (Page 198) (Feature bit 28 = highest priority)
● Issuing substitute value if raw value is invalid (Page 190)(Feature bit 29)
● Output the last valid value if raw value is invalid (Feature bit 30, lowest priority)

Basics of APL
1.5.12 Selecting values associated with messages
Selecting values associated with messages

Use this Feature bit to select which values associated with messages are to be output.
Bit = 0: The signal status of the binary input is output as the value associated with
messages.
Bit = 1: The associated analog value is output as the value associated with messages.
1.5.13 Enabling rapid stop via faceplate
Enabling rapid stop via faceplate

You can use the Feature bit "Enable rapid stop via faceplate" to specify if the OS operator
can use rapid stop for the block via the standard view of the faceplate.
Bit = 0: The "Rapid stop" button is not visible in the faceplate.
Bit = 1: The OS operator can use the button for rapid stop.
1.5.14 Enabling program mode
Enabling program mode

You can use this feature bit to specify whether or not the controller block should be used for
program mode.
Default setting is 0.
Bit = 0: The block is not intended for program mode.
Bit = 1: The block can be used for program mode. The operator control elements required for
this are then visible in the faceplate.
What is the program mode?

Program mode provides primary controller functions (external Advanced Control software
package), which run on an external PC as an OPC client, the option of using the control from
the controller function block and specifying the setpoint or manipulated variable from a
remote location.

Basics of APL
1.5.15 Update acknowledgment and error status of the message call
Update acknowledgment and error status of the message call

You can use the Feature bit to determine if the acknowledgment and error status of the
message call at the block output should be updated.
● Bit = 0
The block outputs MsgErr, MsgStat and MsgAckn are set to the default setting and not
updated. The block will run faster with this setting.
● Bit = 1
The block outputs MsgErr, MsgStat and MsgAckn are updated based on the feedback
of the lower level message blocks. The lower level message blocks are called every other
cycle as long as an acknowledgment is expected or error information is pending.
1.5.16 Resetting the commands for changing the mode
Resetting the commands for changing the mode

Using this Feature bit, you define how the block handles the incoming control commands
SP_IntLi, SP_ExtLi (for controllers) as well as AutModLi and ManModLi .
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 text "Invalid
signal" 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.
1.5.17 Enabling resetting of commands for the control settings
Enabling resetting of commands for the control settings

With this Feature bit, you select how the block handles commands for the control settings
(for example motor on) via the interconnected input parameters.
Bit = 0: The control commands are not reset by the block. If there are two commands relating
to the control settings at the same time, the status of the control settings is retained. In this
case, the "Invalid signal" message is displayed in the standard view of 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.

Basics of APL
1.5.18 Resetting the dosing quantity when dosing starts
Resetting the dosing quantity when dosing starts

Use this feature bit to enable resetting the dosing quantity when dosing starts.
Bit = 0: Disabled, the dosing quantity is not reset when dosing starts
Bit = 1: Enabled, the dosing quantity is reset when dosing starts
1.5.19 Resetting via input signals in the event of interlocks or errors
Enabling block reset via input signals in the event of interlocks or errors
With this Feature bit, you define how automatic control is to be re-enabled after an active
interlock.
Bit = 0: After an interlock or an error, the system can only be started again using a reset
command. Reset is initiated either by operator input in the faceplate or via the
interconnectable input parameter (RstLi = 1) in the block. Following this, the currently
pending command is effective in automatic mode, whereas in manual mode, you must
initiate the next control action yourself.
Bit = 1: It is also possible to reset with a 0-1 edge change in the control signal in automatic
mode. In manual mode, you will need to initiate the next control action manually.

Basics of APL
1.5.20 Setting switch or button mode
Setting switch or button mode (input signal as pulse signal or as static signal)
Use this Feature bit to define whether the command for controlling the module, for
example:
● starting and stopping a motor
● Opening and closing a valve
● switching modes (parameters AutModLi and ManModLi)
● Setpoint input internal and external (parametersSP_ExtLi and SP_IntLi)
is given in the form of a pulse (pushbutton operation) or a static signal (switch operation).
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: The signals from the logic applied to the input parameters take the
form of a pulse signal. (evaluation only of 0-1 edge)
Example with a motorMotRevL: In this case, use the interconnectable input parameters
FwdAut, RevAut and StopAut or AutModLi and ManModLi.
Bit = 1: Switch mode: The signal from the upstream logic that is applied to an input
parameter takes the form of a static signal (evaluation of the signal state).
Example with a motorMotRevL: In this case, use the interconnectable input parameters
FwdAut (FwdAut = 1: the motor runs forward, FwdAut = 0: the motor is off or RevAut =
1: the motor runs in reverse, RevAut = 0: the motor is off) and AutModLi.
1.5.21 Creep rate is always detected in the dosing quantity
Enable: Creep rate is always detected in the dosing quantity

Use the Feature bit to specify the response for detecting the creep rate in the dosing
quantity.
Bit = 0: Disabled, the creep rate is only detected in the dosing quantity over the limit
CR_AH_Lim (high alarm for creep rate). With CR_AH_En = 0, the creep rate has no effect
on the dosing quantity calculation.
Bit = 1: Enabled, the creep rate is always detected in the dosing quantity.
Note
Creep rate is the flow in the states "End", "Off", and "Pause".

Basics of APL
1.5.22 Safety value of the manipulated variable effective at startup
Safety value of the manipulated variable effective at startup

With the safety position value bit Feature bit, you decide whether or not a controller changes
to the safety position during startup.
Bit = 0: The controller does not change to the safety position during startup
Bit = 1: The controller changes to the safety position during startup
Please also refer to the section Safe position for motors, valves and controllers (Page 120).
1.5.23 Safety manipulated variable with "out of service" operating mode in effect
Safety manipulated variable with "out of service" operating mode in effect

With the feature bit "Safety manipulated variable with "out of service" operating mode in
effect", you specify whether or not a controller travels to the safe position during startup.
Default position is "0".
Bit = 0: The controller does not travel to the safe position with the transition to the "out of
service" operating mode.
Bit = 1: The controller travels to the safe position with the transition to the "out of service"
operating mode.
Refer to the Safe position for motors, valves and controllers (Page 120) section for more
information.
1.5.24 Activating bumpless changes to proportional gain
Activating bumpless changes to proportional gain

Use this Feature bit to activate bumpless changes to proportional gain Gain in automatic
mode.
Bit = 0: The bumpless changeover is deactivated.
Bit = 1: The bumpless changeover is activated.

Basics of APL
1.5.25 Disabling bumpless changeover to automatic mode for controllers
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.
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 29).
1.5.26 Enabling bumpless changeover to automatic mode for valves, motors, and dosers
Bumpless changeover
You can use this Feature bit to enable the bumpless changeover from local/manual mode
to automatic mode.
Bit = 0: Bumpless changeover is disabled. You can switch from local/manual mode to
automatic mode at any time.
Bit = 1: Bumpless changeover from local/manual mode to automatic mode is enabled. A
changeover from local/manual mode to automatic mode is only possible if the control
settings of the local/manual mode and automatic modes match.
Please also refer to the section Manual and automatic mode for motors, valves and dosers
(Page 32).

Basics of APL
1.5.27 Output invalid raw value
Output invalid raw value

Use this Feature bit to activate output of the invalid raw value for channel driver blocks.
The default setting is 1(!).
Bit = 0: The invalid raw value is not output. Either the substitute value (Feature bit Issuing
substitute value if raw value is invalid (Page 190)) or the last valid value (Feature bit
Issuing last valid value if raw value is invalid (Page 191)) is output.
Bit = 1: The invalid raw value is output. The signal status of the output value is set to "Bad,
device related" or "Bad, process related".

driver blocks.
● Output invalid raw value (Feature bit 28 = highest priority)
● Issuing substitute value if raw value is invalid (Page 190)(Feature bit 29)
● Issuing last valid value if raw value is invalid (Page 191) (Feature bit 30 = lowest
priority)

Basics of APL
1.5.28 Reaction to the out of service mode
Reaction to the out of service mode

With this Feature bit, you decide the reaction of the technological block depending on the
interconnectable input parameter OosLi = 1.
● Bit = 0: The symbol for the "In progress" status (see above) appears in the block icon and
in the faceplate of the assigned technological block. A 0-1 edge transition at the input
parameter OosLi has no further influence on the reaction of the technological block; the
previous status is retained. No switch to the "Out of service" mode is performed.
● Bit = 1: The mode changes to "out of service" assuming that the block is on or manual
mode. If this is not the case, the mode does not change. The symbol for the "In progress"
(see below) status also appears in the block icon and in the faceplate of the assigned
technological block regardless of the mode change. No message is output to indicate
whether or not the mode change took place.
The status display for "In progress" appears as follows:
A 1-0 edge transition at the input parameter OosLi has no influence on the reaction of the
technological block, the previous status is retained.
See also the Maintenance release (Page 47) section for more on this.
1.5.29 Exiting local mode
Reaction to exiting local mode

Use this Feature bit to define how the "Local mode" is to be exited with
LocalSetting = 1 or LocalSetting = 2 and if the mode is not specified by
AutModLi or ManModLi.
Bit = 0: Exiting local mode in manual mode (bumpless because the control signals are
continuously adjusted).
Bit = 1: When local mode is exited, the mode changes back to the last mode that was active
prior to local mode (not bumpless).
For more detailed information, refer to the description of Local mode (Page 36).

Basics of APL

Operator control blocks 2
2.1 OpAnL- check and output analog signals
2.1.1 Description of OpAnL
Object name (type + number) and family

Type + number: FB 1865
Family: Operate
Area of application for OpAnL

The block is used for the following applications:
● Checking and transferring analog input values
How it works
The block checks incoming, internal (entered in the faceplate) or external (CFC/SFC) analog
signals in terms of their limits at the input SP_Int or SP_Ext and forwards them to the
output SP, depending on the setting of the input parameter SP_LiOp.
Configuration
Use the CFC editor to install the block in a cyclic interrupt OB (OB30 to OB38). The block is
also installed automatically in the startup OB (OB 100).
Startup characteristics
Use the Feature bit Setting the startup response (Page 187) to define the startup
characteristics of this block.
The messages are suppressed after startup for the number of cycles set at RunUpCyc.

Operator control blocks
Status word allocation for Status1 parameter

The description for each parameter can be found in the OpAnL I/Os (Page 209) section.
Status bit Parameter

0 Occupied
1 BatchEn
2 Not used
3 OosAct.Value
4 OosLi.Value
5 Not used
6 OnAct.Value
7 Not used
8 SP_ExtAct.Value
9 SP_LoAct.Value
10 SP_HiAct.Value
11 - 13 Not used
14 SP_RmpOn
15 SP_RmpModTime
16 - 31 Not used
See also
OpAnL functions (Page 204)
OpAnL messaging (Page 207)
OpAnL block diagram (Page 214)
OpAnL error handling (Page 206)
OpAnL modes (Page 203)

2.1.2 OpAnL modes
OpAnL modes
The block can be operated using the following modes:
● On (Page 27)
"On"
General information on the "On" mode is available in the section On (Page 27).
"Out of service"
You will find general information about the "Out of service" mode in the Out of service
(Page 27) section.
See also
OpAnL I/Os (Page 209)
Description of OpAnL (Page 201)
Manual and Automatic mode for control blocks (Page 29)
Local mode (Page 36)

2.1.3 OpAnL functions
Functions of OpAnL
The functions for this block are listed below.
Internal or external setpoint selection

This block provides the standard function Setpoint input - internal and external (Page 96).
Setpoint limitation
Use the SP_HiLim and SP_LoLim input parameters to limit the setpoint to maximum and
minimum limits. If a limit is violated, the setpoint is limited to the limits you have set. If the
limits are infringed, the output parametersSP_HiAct and SP_LoAct display 1.
Using setpoint ramp

This block provides the standard function Using a setpoint ramp (Page 98).

This block provides the standard function Ramp limiting of the setpoint (Page 108).
Forming the signal status for blocks

This block provides the standard function Forming and outputting signal status for blocks
(Page 88).
The worst signal status ST_Worst for the block is formed from the following parameters:
● SP_Out.ST
● PV_In.ST
The signal status of output parameter SP is always equivalent to the signal status of input
parameter SP_Ext or SP_Int, depending on how the setpoint is specified. If the internal
setpoint SP_Int is used, the signal status is always output as 16#80.
Selecting a unit of measure

This block provides the standard function Selecting a unit of measure (Page 53).

Configurable reactions using the Feature parameter

You can find an overview of all reactions provided by the Feature parameter in the
Functions that can be set via the Feature I/O (Page 186) section. The following functionality
is available for this block at the relevant bits:
Bit Function
Operator control permissions via parameter OS_Perm

The block has the following Operator permissions (Page 45) for the OS_Perm parameter:
Bit Function
0 Not allocated
1 1 = Operator can switch to On mode
2 Not allocated
3 1 = Operator can switch to out of service mode
4-9 Not allocated
10 1 = Operator can switch to internal
11 1 = Operator can switch to external
12 1 = Operator can perform bumpless switchover
13 1 = Operator can change SP_Int
14 1 = Operator can enable SP_RateOn
15 1 = Operator can change SP_UpRaLim
16 1 = Operator can change SP_DnRaLim
17 1 = Operator can activate the setpoint ramp (SP_RmpOn)
18 1 = Operator can switch between specification of the duration (SP_RmpTime) and
gradient (SP_DnRaLim, SP_UpRaLim) for calculating the ramp slope
19 1 = Operator can change the time for the setpoint ramp (SP_RmpTime)
20 1 = Operator can change the target setpoint (SP_RmpTarget)
21-31 Not allocated
Specifying the display area for process and setpoint values as well as operations
The block provides the standard function Display and operator input area for process values
and setpoints (Page 42).

The block provides the standard function Calling further faceplates (Page 43).


The block provides the standard function SIMATIC BATCH functionality (Page 122).
See also
2.1.4 OpAnL error handling
OpAnL troubleshooting
Please refer to the section Error handling (Page 117) in the basic instructions.
The following errors can be displayed for this block:
● Error numbers
Overview of error numbers

The ErrorNum I/O can be used to output the following error numbers:
Error number Meaning of the error number

-1 Predefined value when inserting the block, the block is not processed.
0 There is no error.
51 Invalid signal.
SP_LiOp = 1 and SP_ExtLi = 1 and SP_IntLi = 1.
See also

2.1.5 OpAnL messaging
Messaging
The following messages can be generated for this block:
● Process messages
Process messages
Message Message identifier Message class Event

instance
MsgEvId SIG 1 AS process control message - fault $$BlockComment$$
External message 1
SIG 2 AS process control message - fault $$BlockComment$$
External message 2
External message 3
External message 4
SIG 5 Reserved $$BlockComment$$
Reserved
Reserved
Reserved
Reserved
Explanation:
$$BlockComment$$: Content of the instance-specific comment

Associated values for message instance MsgEvId
Associated value Block parameters

1 BatchName
2 StepNo
3 BatchID
4 ExtVa104
5 ExtVa105
6 ExtVa106
7 ExtVa107
The associated values 4 ... 7 are allocated to the parameters ExtVa104 ... ExtVa107 and
can be used by yourself. Additional information is available in the "Process Control System
PCS 7 - Engineering System" manual.
See also

2.1.6 OpAnL I/Os
OpAnL I/Os
Input parameters
Parameter Description Type Default

BatchEn 1 = Enable allocation BOOL 0
BatchID Batch ID DWORD 16#00000000
BatchName Batch name STRING[32] ''
EN 1 = Called block will be BOOL 1
processed
ExtMsg1 Binary input for freely STRUCT -
selectable message 1 • Value: BOOL • 0
• ST: BYTE • 16#80
• ST: BYTE • 16#80
• ST: BYTE • 16#80
• ST: BYTE • 16#80
ExtVa104 Associated value 4 for ANY
messages (MsgEvID1)
messages (MsgEvID1)
messages (MsgEvID1)
messages (MsgEvID1)
Feature I/O for additional functions STRUCT -
(Page 204) • Bit 0: BOOL • 0
• ... • 0
• Bit 31: BOOL • 0
MsgEvId Message number (assigned DWORD 16#FF
automatically)
Occupied 1 = Occupied by batch BOOL 0
control
OnOp 1 = "On" mode via operator BOOL 0


OosLi 1 = Out of service, via STRUCT -
interconnection or SFC (0-1 • Value: BOOL • 0
edge transition)
• ST: BYTE • 16#80
OosOp 1 = Out of service, via OS BOOL 0
operator
OS_Perm I/O for operator control STRUCT -
permissions (Page 204) • Bit 0: BOOL • 1
• ... • 1
• Bit 31: BOOL • 1
PV_In Process value STRUCT -
• Value: REAL • 0.0
• ST: BYTE • 16#80
PV_Unit Unit of measure for process INT 0
value
RunUpCyc Number of cycles in startup; INT 3
messages are suppressed
during these cycles
SampleTime Sampling time [s] (assigned REAL 0.1
automatically)
SP_DnRaLim Limit (low) for ramp of REAL 100.0
setpoint [SP_Unit/s]
SP_Ext external setpoint - (to STRUCT -
interconnection) • Value: REAL • 0.0
• ST: BYTE • 16#80
SP_ExtLi 1 = Select internal setpoint STRUCT -
(via interconnection) • Value: BOOL • 0.0
• ST: BYTE • 16#80
SP_ExtOp 1 = Select external setpoint BOOL 0
(via operator)
SP_HiLim Limit (high) of setpoint REAL 100.0
SP_LoLim Limit (low) of setpoint REAL 0.0
SP_Int Internal setpoint for REAL 0.0
operation
SP_IntLi 1 = Select internal setpoint STRUCT -
(via interconnection) • Value: BOOL • 0
• ST: BYTE • 16#80
SP_IntOp 1 = Select internal setpoint BOOL 1
(via operator)
SP_LiOp Select setpoint source STRUCT -
(internal/external): • Value: BOOL • 0
1 = Via interconnection • ST: BYTE • 16#80
0 = Via operator


SP_OpScale OS display range for setpoint STRUCT -
• High: REAL 100.0
• Low: REAL 0.0
SP_RateOn 1 = Activate limitation of BOOL 0
setpoint gradients
SP_RmpModTime 1 = Use time (SP_RmpTime) BOOL 0
for setpoint ramp,
0 = Use gradient
SP_RmpOn 1 = Activate setpoint ramp to BOOL 0
target setpoint
SP_RmpTarget
SP_RmpTarget Target setpoint for setpoint REAL 0.0
ramp
SP_RmpTime Time for setpoint ramp [s] REAL 0.0
from current SP up to
SP_RmpTarget
SP_TrkExt 1 = Bumpless switchover BOOL 0
from external to internal
setpoint active
SP_Unit Unit of measure for setpoint INT 0
SP_UpRaLim Gradient limit (high) for REAL 100.0
SelFp1 Call a block saved in this ANY -
parameter as an additional
faceplate (Page 43) in the
standard view
preview
StepNo Batch step number DWORD 16#00000000
UserStatus Freely assignable user area BYTE 16#00
for status word

Output parameters

ENO 1 = Block algorithm completed without errors BOOL 0
ErrorNum Output of current error number. For error INT -1
numbers that can be output by this block, see
MsgAckn Message acknowledgement status (output WORD 16#0000
STATUS of first ALARM_8P)
MsgErr 1 = Alarm error (output ERROR of first BOOL 0
ALARM_8P)
MsgStat Alarm status (output ERROR of first ALARM_8P) WORD 16#0000
OnAct 1 = "On" mode enabled STRUCT -
• Value: BOOL • 1
• ST: BYTE • 16#80
OosAct 1 = Block is "Out of service" STRUCT -
• ST: BYTE • 16#80
OS_PermLog Display of OS_Perm with settings changed by the DWORD 16#FFFFFFFF
block algorithm
OS_PermOut Display of OS_Perm DWORD 16#FFFFFFFF
SP_Out Setpoint used by controller STRUCT -
• ST: BYTE • 16#80
SP_DnRaAct 1 = Negative gradient limiting of setpoint is active STRUCT -
• ST: BYTE • 16#80
SP_ExtAct 1 = External setpoint is active STRUCT -
0 = Internal setpoint is active • Value: BOOL • 0
• ST: BYTE • 16#80
SP_HiAct High limit for SP_Ext or SP_Int reached or STRUCT -
exceeded • Value: BOOL • 0
• ST: BYTE • 16#80
SP_LoAct Low limit for SP_Ext or SP_Int reached or STRUCT -
exceeded • Value: BOOL • 0
• ST: BYTE • 16#80
SP_UpRaAct 1 = Positive gradient limiting of setpoint is active STRUCT -
• ST: BYTE • 16#80
ST_Worst Worst signal status BYTE 16#80
Status1 Status word (Page 201) DWORD 16#00000000

See also

2.1.7 OpAnL block diagram
OpAnL block diagram

A block diagram is not provided for this block.
See also
2.1.8 Operator control and monitoring
2.1.8.1 Views of OpAnL
Views of the OpAnL block

The block OpAnL provides the following views:
● OpAnL standard view (Page 215)
● Message view (Page 169)
● Trend view (Page 172)
● Ramp view (Page 167)
● OpAnL parameter view (Page 217)
● OpAnL preview (Page 218)
● Memo view (Page 171)
● Batch view (Page 170)
● Block icon for OpAnL (Page 219)
Refer to the sections Structure of the faceplate (Page 123) and Block icon structure
(Page 174) for general information on the faceplate and block icon.

2.1.8.2 OpAnL standard view
OpAnL standard view

2SHUDWLQJPRGH 2Q
6HWSRLQW ,QWHUQDO

(5
3URFHVVYDOXH r&
6HWSRLQW r&

)DFHSODWH

● On (Page 27)

You can find additional information on this in the Setpoint input - internal and external
(Page 96) section.
These values provide information on the display range for the bar graph of the process
value. The scale range is defined in the engineering system.


This area shows the current process value with the corresponding signal status.

This area shows the current setpoint with the corresponding signal status.
The setpoint specification also needs to be set to "Internal" for this block.



to "external".

(11) Display for limits


2.1.8.3 OpAnL parameter view
OpAn parameter view
63 63H[WHUQDO

process
(2) Settings
● SP := SP external: ☑ Bumpless switchover of setpoint from external to internal. The
internal setpoint is tracked to the external one.

2.1.8.4 OpAnL preview
OpAn preview
(QDEOHRSHUDWLRQV
63H[WHUQDO 2Q
63LQWHUQDO 2XWRIVHUYLFH
&KDQJH63
)DFHSODWH

process
control permissions
The following operator control enables are shown here:
● SP external: You can connect to the external setpoint.
● SP internal: You can connect to the internal setpoint.
● Change SP: You can change the setpoint.
● On: You can switch to On operating mode.
● Out of service: You can switch to the Out of service operating mode.
Refer also to the Calling further faceplates (Page 43) section for more on this.

2.1.8.5 Block icon for OpAnL
Properties of the OpAnL block icon

● Violation of alarm, warning, and tolerance limits
● Operating modes
● Memo display


● Setpoint (blue, with and without decimal places)
Icons Selection of the block Special features

icon in CFC
- Block icon in the "Out of service"

mode (example with type 1 block
icon)

● Operation via the block icon (Page 181).

2.2 OpTrig - Manipulating a digital value (1 pushbutton)
2.2.1 Description of OpTrig

Family: Operate
Area of application for OpTrig

● Generation of a pulse signal (trigger)
How it works
Operator control block is used to implement single pushbutton control (comparable with
RESET pushbutton).
Configuration
Use the CFC editor to install the block in a cyclic interrupt OB (OB30 to OB38).
The block does not have any startup characteristics.

For a description of the individual parameters, see the OpTrig I/Os (Page 228) section.

0-2 Not used
3 OosAct.Value
4 OosLi.Value
5 Not used
6 OnAct.Value
7 Out.Value
8 LiOpAct.Value
9 FbkIn.Value
10 - 31 Not used

See also
OpTrig functions (Page 225)
OpTrig messaging (Page 227)
OpTrig block diagram (Page 230)
OpTrig error handling (Page 227)
OpTrig modes (Page 224)

2.2.2 OpTrig modes
OpTrig operating modes

The block can be operated using the following modes
● On (Page 27)
"On"
"Out of service"
You can find general information about the "Out of service" mode in the section Out of
service (Page 27).
See also
OpTrig I/Os (Page 228)
Description of OpTrig (Page 222)

2.2.3 OpTrig functions
Functions of OpTrig
Issuing trigger signal internally or externally

Use the parameter LiOp to define whether the trigger signal is to be output by
interconnection or by the OS operator:
LiOp = 0: Trigger signal by OS operator (input parameter InOp)
LiOp = 1: Trigger signal by interconnection (input parameter InLi)
Input parameter for feedback value

This block has a FbkIn input parameter for displaying a feedback value in the faceplate.

This block provides the standard function Calling further faceplates (Page 43).

(Page 88).
● FbkIn.ST
● Out.ST

Bit Function
0 Not allocated
2 Not allocated
4 1 = Operator can set the input parameter In
5-31 Not allocated


You can find an overview of all reactions provided by the Feature parameter in the section
Functions that can be set via the Feature I/O (Page 186). The following functionality is
available for this block at the relevant bits:
Bit Function
See also

2.2.4 OpTrig error handling
OpTrig error handling

The block does not report any errors.
See also
2.2.5 OpTrig messaging
Messaging
The block does not offer messaging.
See also

2.2.6 OpTrig I/Os
OpTrig I/Os
Input parameters

EN 1 = Called block will be processed BOOL 1
FbkIn Input for feedback STRUCT -
• ST: BYTE • 16#80
Features I/O for additional functions (Page 225) STRUCT -
• Bit 0: BOOL • 0
• ... • 0
• Bit 31: BOOL • 0
InLi Interconnectable binary input STRUCT -
• ST: BYTE • 16#80
InOp Binary input for operator BOOL 0
LiOp Switchover of operating mode between: STRUCT -
1 = Interconnection • Value: BOOL • 0
0 = Operator • ST: BYTE • 16#80
OosLi 1 = Out of service, via interconnection STRUCT -
or SFC • Value: BOOL • 0
• ST: BYTE • 16#80
OosOp 1 = Out of service, via OS operator BOOL 0
OS_Perm I/O for operator control permissions STRUCT -
(Page 225) • Bit 0: BOOL • 1
• ... • 1
• Bit 31: BOOL • 1
SelFp1 Call a block saved in this parameter as ANY -
additional faceplate (Page 43) in
standard view
SelFp2 Call a block saved in this parameter as ANY -
additional faceplate (Page 43) in the
preview
UserStatus Freely assignable user area for status BYTE 16#00
word

Output parameters

ENO 1 = Block algorithm completed without BOOL 0
errors
ErrorNum Reserved
LiOpAct Operator/interconnection is active STRUCT -
• ST: BYTE • 16#80
OosAct 1 = Block is out of service STRUCT -
• ST: BYTE • 16#80
• ST: BYTE • 16#80
OS_PermLog Display of OS_Perm with settings DWORD 16#FFFFFFFF
changed by the block algorithm
Out Output STRUCT -
• ST: BYTE • 16#80
Status Status word (Page 222) DWORD 16#00
See also

2.2.7 OpTrig block diagram
OpTrig block diagram

This block does not come with a block diagram.
See also
2.2.8.1 Views of OpTrig
Views of the OpTrig block

The block OpTrig provides the following views:
● OpTrig standard view (Page 231)
● OpTrig preview (Page 232)
● Block symbol for OpTrig (Page 233)

2.2.8.2 OpTrig standard view
OpTrig standard view
2SHUDWLQJPRGH 2Q
)DFHSODWH 6HW

● On (Page 27)
You can find additional information on this in the Switching operating states and operating
modes (Page 127) section.
(2) Set
By clicking "Set", a pulse signal with the length of the cycle time is output at the Out output.

2.2.8.3 OpTrig preview
OpTrig preview
(QDEOHRSHUDWLRQV
6HWLQSXW 2Q
2XWRIVHUYLFH
,QSXWVDQG2XWSXWV
2XWSXW

)HHGEDFN
)DFHSODWH

process
control permissions
● Set input: You can set the input.
● Out of service: You can switch to the "Out of service" mode.
(2) Display of current inputs and outputs

This area shows the most important parameters for this block with the current selection:
● Output: 1= Digital output value set
● Feedback: 1= Feedback set

2.2.8.4 Block symbol for OpTrig
Properties of the OpTrig block icon

● Operating modes
● Memo display

CFC

type 1 block icon)

2.3 OpDi01 - Manipulating a digital value (2 pushbuttons)
2.3.1 Description of OpDi01

Family: Operate
Area of application for OpDi01

● Manipulating a digital value
How it works
A digital value is manipulated by interconnection or via the faceplate.
Configuration


For a description of the individual parameters, see the OpDi01 I/Os (Page 240) section.

0-2 Not used
3 OosAct.Value
4 OosLi.Value
5 Not used
6 OnAct.Value
7 Out.Value
8 LiOp
9 FbkIn.Value
10 - 15 Not used
16 1 = Intlock is active
17 - 22 Not used
23 "Interlock" button is enabled
24-25 Not used
26 Bypass information from previous function block
27 - 31 Not used
See also
OpDi01 functions (Page 237)
OpDi01 messaging (Page 239)
OpDi01 block diagram (Page 242)
OpDi01 error handling (Page 239)
OpDi01 modes (Page 236)

2.3.2 OpDi01 modes
OpDi01 operating modes

● On (Page 27)
"On"
"Out of service"
You can find general information about the "Out of service" mode in the section Out of
service (Page 27).
See also
OpDi01 I/Os (Page 240)
Description of OpDi01 (Page 234)

2.3.3 OpDi01 functions
Functions of OpDi01
Internal or external digital value

Use the LiOp input parameter to define whether the digital value is set (0-1, parameter
SetOp or SetLi) or is reset (1-0, parameter RstOp or RstLi) via the faceplate or an
interconnection.
LiOp = 0: Specification of digital value by faceplate (SetOp or RstOp)
LiOp = 1: Specification of digital value by interconnection (SetLi or RstLi)
Interlocks
Use the Intl_En = 1 and Intlock.ST ≠ 16#FF input parameters to activate the
interlock function on this block.
An active interlock condition brings the block to the safe position (Intlock.Value = 0 or
Intlock.ST = 16#00 input). Output parameter Out is set to 0. When the interlocking
condition no longer applies, the digital value currently valid is output again.

This block has a FbkIn input parameter for displaying a feedback value in the faceplate.


(Page 88).
● Out.ST
● FbkIn.ST
● Intlock.ST


Bit Function
0 Not allocated
2 Not allocated
4 1 = Operator can set the digital value
5 1 = Operator can reset the digital value
6-31 Not allocated

Functions of blocks > Functions that can be set via the Feature I/O (Page 186).
The following functionality is available for this block at the relevant bits:
Bit Function
0 Not used
2 - 31 Not used
See also

2.3.4 OpDi01 error handling
OpDi01 trouble shooting

● Error numbers


-1 Default value when implementing the block; block will not be processed.
51 SetLi = 1 and RstLi = 1 and LiOp = 1
See also
2.3.5 OpDi01 messaging
Messaging
The block does not have any message functionality.
See also

2.3.6 OpDi01 I/Os
OpDi01 I/Os
Input parameters

FbkIn Input for feedback STRUCT -
• ST: BYTE • 16#80
Features I/O for additional functions (Page 237) STRUCT -
• ... • 0
• Bit 31: BOOL • 0
Intlock 0 = Interlocking without reset is effective; you can STRUCT -
operate the block without reset once the interlocking • Value: BOOL • 1
condition has disappeared
• ST: BYTE • 16#FF
1 = Good state
Intl_En 1 = Interlock without reset (interlock, parameter BOOL 1
Intlock) can be used
OosLi Edge transition (0-1) = Out of service, via STRUCT -
interconnection or SFC • Value: BOOL • 0
• ST: BYTE • 16#80
OS_Perm I/O for operator control permissions (Page 237) STRUCT -
• ... • 1
• Bit 31: BOOL • 1
RstLi Reset via interconnection STRUCT -
• ST: BYTE • 16#80
RstOp Reset by the operator BOOL 0
SelFp1 Call a block saved in this parameter as an additional ANY -
faceplate (Page 43) in the standard view
SelFp2 Call a block saved in this parameter as an additional ANY -
faceplate (Page 43) in the preview


SetLi Connected digital input STRUCT -
• ST: BYTE • 16#80
SetOp Digital input for operator BOOL 0
UserStatus Freely assignable user area for status word BYTE 16#00
Output parameters

errors
ErrorNum Output of current error number. For INT -1
error numbers that can be output by this
block, see OpDi01 error handling
(Page 239)
• ST: BYTE • 16#80
• ST: BYTE • 16#80
Out Digital output value STRUCT -
• ST: BYTE • 16#80
See also

2.3.7 OpDi01 block diagram
OpDi01 block diagram

See also
2.3.8.1 Views of OpDi01
Views of the OpDi01 block

The block OpDi01 provides the following views:
● OpDi01 standard view (Page 243)
● OpDi01 preview (Page 245)
● Block symbol for OpDi01 (Page 247)
Refer to the Structure of the faceplate (Page 123) and Block icon structure (Page 174)
sections for general information about the faceplate and block icon.

2.3.8.2 OpDi01 standard view
OpDi01 standard view
2SHUDWLQJPRGH 2Q
2II &RPPDQG 2II
)DFHSODWH ,QWHUORFN

● On (Page 27)
(2) Display and switch the command

This area shows you the current selection. You can output a continuous signal as follows:
● On: Continuous signal is output
● Off
(3) Display area for interlock functions of the block

You can use this button to control the interlock functions of the block. You can find additional
information on this in the Interlocks (Page 100) section.

(5) Display the feedback of the command

This area shows you the currently valid command. The following commands can be shown
here:
● On
● Off

2.3.8.3 OpDi01 preview
OpDi01 preview
(QDEOHRSHUDWLRQV
2Q 2Q
2II 2XWRIVHUYLFH
,QSXWVDQG2XWSXWV
,QWHUORFN

2XWSXW
)HHGEDFN
)DFHSODWH

process
control permissions
● On: You can set the digital value (0-1 edge).
● Off: You can set the digital value (1-0 edge).
● Out of service: You can switch to the "Out of service" mode.


● Interlock:
– 0 = Interlocking without reset is effective; you can operate the block without reset once
the interlocking condition has disappeared
– 1 = Good state
● Output: 1= Digital output value set
● Feedback: 1= Feedback set

2.3.8.4 Block symbol for OpDi01
Properties of the OpDi01 block icon

● Operating modes
● Bypass
● Interlocks
● Output signal
● Memo display

CFC

type 1 block icon)

2.4.1 Description of OpDi03

Family: Operate
Area of application for OpDi03

● Manipulating a digital value (3 pushbuttons)
How it works
A digital value is manipulated at three possible outputs by interconnection or via the
faceplate.
If two or three input parameters are set for an interconnection (Parameter SetLix), the
input parameter with the highest index will be set to the corresponding output parameter. For
example, if the SetLi1 and SetLi2 input parameters are set (=1), Out2 will be set (=1).
Configuration


For a description of the individual parameters, see the OpDi03 I/Os (Page 256) section.

0-2 Not used
3 OosAct.Value
4 OosLi.Value
5 Not used
6 OnAct.Value
7 Out1.Value
8 Out2.Value
9 Out3.Value
10 LiOp.Value
11 Fbk1In.Value
12 Fbk2In.Value
13 Fbk3In.Value
14-15 Not used
16 1 = Intlock is active
17 - 22 Not used
23 "Interlock" button is enabled
24-25 Not used
26 Bypass information from previous function block
27 - 31 Not used
See also

2.4.2 OpDi03 modes
OpDi03 operating modes

● On (Page 27)
"On"
You can find general information about the "On" mode in the On (Page 27) section.
"Out of service"
You can find general information about the "Out of service" mode in the Out of service
(Page 27) section.
If you switch to out of service mode, the Out3 output parameter is set (=1).
See also

2.4.3 OpDi03 functions
Functions of OpDi03
Internal or external digital value

Use the LiOp input parameter to define whether the digital value is set (0-1) or reset (1-0,
input parameter RstOut) using the faceplate or an interconnection by selecting 1 from 3.
LiOp = 0: Specification of digital value by faceplate. One of the input parameters SetOp1,
SetOp2 or SetOp3 is now led to the relevant output Out1, Out2 or Out3. For example if
SetOp2 = 1, then Out2 = 1.
LiOp = 1: Specification of digital value by interconnection. One of the input parameters
SetLi1, SetLi2 or SetLi3 is now led to the relevant output Out1, Out2 or Out3. For
example if SetLi2 = 1, then Out2 = 1.
The reset (1-0) is always undertaken using the RstOut input parameter.
Interlocks
Use the Intl_En = 1 and Intlock.ST ≠ 16#FF input parameters to activate the
interlock function on this block.
An active interlock condition brings the block to the safe position (Intlock.Value = 0 or
Intlock.ST = 16#00 input). Output parameter Out is set to 0. When the interlocking
condition no longer applies, the digital value currently valid is output again.

This block has three input parameters Fbk1In, Fbk2In and Fbk3In for displaying three
feedback values in the faceplate.
Resetting all output values

You can reset all output parameters (Out1 to Out3) by setting all interconnected input
parameters to be set (SetLi1 to SetLi3) or operable input parameters to be set (SetOp1
to SetOp3) to 0.
A 0-1 edge at the RstOut parameter then resets the three output parameters Out1 to Out3.



(Page 88).
● Out1.ST
● Out2.ST
● Out3.ST
● Fbk1In.ST
● Fbk2In.ST
● Fbk3In.ST
● Intlock.ST

Bit Function
0 Not allocated
2 Not allocated
4 1 = Operator can set the digital value SetOp1
7-31 Not allocated


Functions of blocks > Functions that can be set via the Feature I/O (Page 186).
The following functionality is available for this block at the relevant bits:
Bit Function
0 Not used
2 - 31 Not used
See also

2.4.4 OpDi03 error handling
OpDi03 troubleshooting
● Error numbers


51 The value 1 is set at two or more inputs.
(SetLi1 = 1 and SetLi2 = 1) or (SetLi2 = 1 and SetLi3 = 1) or (SetLi1
= 1 and SetLi3 = 1) and LiOp = 1
See also

2.4.5 OpDi03 messaging
Messaging
The block does not offer messaging.
See also

2.4.6 OpDi03 I/Os
OpDi03 I/Os
Input parameters

Fbk1In Feedback for In1 input STRUCT -
• ST: BYTE • 16#80
• ST: BYTE • 16#80
• ST: BYTE • 16#80
Feature I/O for additional functions (Page 251) STRUCT -
• ... • 0
• Bit 31: BOOL • 0
Intlock 0 = Interlocking without reset is effective; you STRUCT -
can operate the block without reset once the • Value: BOOL • 1
interlocking condition has disappeared
• ST: BYTE • 16#80
1 = Good state
Intl_En 1 = Interlock without reset (interlock, parameter BOOL 1
Intlock) can be used
OosLi 1 = Out of service, via interconnection or SFC STRUCT -
• ST: BYTE • 16#80
OS_Perm I/O for operator control permissions (Page 251) STRUCT -
• ... • 0
• Bit 31: BOOL • 0
RstOut Reset by the operator STRUCT -
• ST: BYTE • 16#80


SelFp1 Call a block saved in this parameter as an ANY -
additional faceplate (Page 43) in the standard
view
additional faceplate (Page 43) in the preview
SetLi1 Connected digital input 1 STRUCT -
• ST: BYTE • 16#80
• ST: BYTE • 16#80
• ST: BYTE • 16#80
SetOp1 Digital input 1 for operator BOOL 0
UserStatus User status bits BYTE 16#00

Output parameters

ErrorNum Output of current error number. For error INT -1
numbers that can be output by this block, see
• ST: BYTE • 16#80
• ST: BYTE • 16#80
OS_PermLog Display of OS_Perm with settings changed by DWORD 16#FFFFFFFF
the block algorithm
OS_PermOut Display of OS_Perm DWORD 16#FF
Out1 Digital output value 1 BOOL 0
See also

2.4.7 OpDi03 block diagram
OpDi03 block diagram

See also

2.4.8.1 Views of OpDi03
Views of the OpDi03 block

The block OpDi03 provides the following views:
● OpDi03 standard view (Page 260)
● OpDi03 preview (Page 262)
● Block symbol for OpDi03 (Page 264)
2.4.8.2 OpDi03 standard view
OpDi03 standard view
2SHUDWLQJPRGH 2Q
2II &RPPDQG 2II
2II &RPPDQG 2II
2II &RPPDQG 2Q
)DFHSODWH ,QWHUORFN

● On (Page 27)

(2) Display and switch the commands 1 to 3

This area shows you the current selection. You can output a continuous signal at the outputs
Out1 to Out3 as follows:
● On: Continuous signal is output
● Off
(3) Display area for interlock functions of the block

You can use this button to control the interlock functions of the block. You can find additional
information on this in the Interlocks (Page 100) section.
(5) Display feedback from commands 1 to 3

This area shows you the current valid selection from Out1 to Out3.

2.4.8.3 OpDi03 preview
OpDi03 preview
(QDEOHRSHUDWLRQV
2Q 2Q
2Q 2XWRIVHUYLFH
2Q
,QSXWVDQG2XWSXWV
,QWHUORFN )HHGEDFN
2XWSXW )HHGEDFN
2XWSXW )HHGEDFN
2XWSXW
)DFHSODWH

process
control permissions
● On 1 to 3: You can set the digital value (0-1 edge) for each.
● On (operating mode): You can switch to On operating mode.
● Out of service (operating mode): You can switch to the Out of service operating mode.


● Interlock:
– 0 = Interlocking without reset is effective; you can operate the block without reset once
the interlocking condition has disappeared
– 1 = Good state
● Output 1 to 3: 1= Digital output value set
● Feedback 1 to 3: 1= Feedback set

2.4.8.4 Block symbol for OpDi03
Properties of the OpDi03 block icon

● Operating modes
● Bypass
● Interlocks
● Output signal
● Memo display

CFC

type 1 block icon)

Generator blocks 3
3.1 NoiseGen - Rauschgenerator
3.1.1 Description of NoiseGen

Object name: FB 1863
Family: Genrator
Area of application for NoiseGen

● Noise generator
You do not need this block.
How it works
This block serves to generate signal noise. It is used for demonstration purposes in the
example project so that the simulated signals react naturally.
You can employ it for simulation examples, demonstrations, trade fair models etc. It is never
needed in real plants because real measuring devices always supply signals with noise.
There is an example project for the NoiseGen block (APL_Example_xx, xx refers to the
language variant) with an application scenario for this block, which explains how the block
works.
Application scenario in the example project:
● Process simulation including noise generator (Page 1456)
See also
NoiseGen I/Os (Page 266)

Generator blocks
3.1 NoiseGen - Rauschgenerator
3.1.2 NoiseGen I/Os
NoiseGen I/Os
Input parameters

Enable 1 = generate noise signals BOOL 1
Offset Mean temporal value of the Noise output signal REAL 20.0
Restart 1 = block restart BOOL 1
StdDev Standard deviation of the noise signal REAL 1.0
Output parameters

Noise Generated noise signal STRUCT -
• ST: BYTE • 16#80
See also
Description of NoiseGen (Page 265)

Control blocks 4
4.1 ConPerMon - monitoring of the control performance of control loops
4.1.1 Description of ConPerMon

Family: Control
Area of application for ConPerMon

● Permanent monitoring of control performance of control loops for early detection of
problems as they develop
The block calculates:
● Stochastic characteristics of the control performance with the process in a steady state
– Mean value, variance and standard deviation of controlled variable
– Mean value of the manipulated variable and control deviation
– Control performance index
– Estimated steady state process gain
● Deterministic characteristics of the control performance with step changes in the setpoint
– Response time and settling time and the settling ratio
– Overshoot absolute and relative to the step height
Other statistical and graphic evaluations of the signals in the control loop over longer, freely
selectable periods are available in the faceplate of the ConPerMon block.
In an overview representation of a plant or unit, you can obtain a clear picture of the status of
all control loops based on ConPerMon block icons (indicator light function).
The aim is to detect problems as they develop and to focus the attention of the user on the
control loops in a plant that are no longer operating correctly.

Control blocks
How it works
The ConPerMon block evaluates the setpoint and process value signals and the manipulated
variable of the PID controller in a sliding time window. The mode of the controller is also
taken into account.
With the process in a steady state, the detected stochastic characteristics are compared with
the reference values obtained during commissioning. If there is a step change in the
setpoint, the stochastic characteristics are by definition irrelevant and are temporarily frozen.
Instead, the monitoring of the deterministic characteristics is automatically activated.
If the control performance falls below a defined limit a message is generated. This is also the
case when a defined limit for overshoot is exceeded when there is a step change in the
setpoint.
Configuration
Each PID controller has a ConPerMon block assigned to it that is installed in the same CFC
chart and interconnected with the controller. This already takes place with the corresponding
process tag types.
You can open the standard view for the ConPerMon block from the standard view of a
controller (for example PIDConL). Additional information on this topic is available in the
section Calling further faceplates (Page 43).
After successful commissioning and optimization of the PID controller to be monitored, the
ConPerMon block is initialized while the process is in a steady state and it stores the
corresponding characteristic values as reference values.
Follow the steps outlined below:
● Change the PID controller you want to monitor to automatic mode and set the setpoint to
the typical operating point. This operating status is intended to represent the normal
operation of the process; in other words, the entire plant/unit should be running under
production conditions. Monitor the process with a trend writer (CFC trend in the
Engineering-System or WinCC Online-Trend-Control on the Operator Station) and wait
until the process has settled
● To specify the length TimeWindow of the sliding time window, monitor the PV_Variance
block output of the ConPerMonblock in a trend. The time window should be long enough
to keep the variance fairly constant in the relevant decimal places. If the selected time
window is too short in relation to the time constants in the control loop and the
disturbance signal spectrum, the variance will have too much noise and no useful
information.
If the selected time window is too long, it takes longer before any deterioration of the
control quality is detected by the ConPerMon block. It also takes longer following a step
change in the setpoint before the monitoring of the stochastic characteristics can be
resumed. A good starting value for the TimeWindow parameter is 10 times as long as the
longest process time constant or 20 times as long as the reset time of the PID controller.

Control blocks
● If the controller
– is set perfectly,
– has achieved a steady state,
– the time window has been defined and filled with values from the steady state,
the ConPerMon block can be initialized. You do this by clicking the "Initialize" button in
the parameter view of the ConPerMon faceplate or by setting the InitRefVar = 1
parameter in the CFC block. This saves the PV_Variance parameter in the current time
window as a reference value for calculating the control quality in the block along with
reference values for manipulated variable and process variable.
The Control Performance IndexCPI should now be approximately at 100% and therefore
indicate that the control loop is operating correctly. Due to stochastic fluctuations, the CPI
can also temporarily exceed the 100% mark. If, however, the CPI drops by a significant
amount over a longer period, this indicates deterioration of the control performance.
For more detailed information on interpreting the calculation results of the block, refer to the
section ConPerMon functions (Page 273).
Note
If the length of the time window is changed during runtime, the CPI will temporarily deviate
considerably from its old value and then gradually settle to the new steady value. It is
advisable to reinitialize the ConPerMon block after the CPI value has settled to a constant
level.
The ConPerMon faceplate is opened from the faceplate of the assigned PID controller so
that the ConPerMonicon pictures do not need to be installed separately in each OS picture. It
is, in fact, advisable to group all ConPerMon block icons of a plant or unit in one overview
picture at the appropriate hierarchy level.
You can expand this overview picture with the trend display of the control quality of all
control loops over a longer time to allow you to recognize gradual deterioration (for example
reflecting wear and tear). You can also display a further view of the message archive
(WinCC AlarmLogging Control) as a hit list sorted according to the frequency in which they
occur. In this list, the control loops that caused the most alarms will be shown at the top.
For the ConPerMon block, the Advanced Process Library contains templates for process tag
types as examples with various application scenarios for this block.
Examples of process tag types:
● PID controller with dynamic feedforward control (FfwdDisturbCompensat) (Page 1433)
● PID - control with operating-point-oriented parameter control (GainScheduling)
(Page 1431)
● PID controller with safety logic and control loop monitoring (PIDConL_ConPerMon)
(Page 1430)
● PIDConR with safety logic and control loop monitoring (PIDConR_ConPerMon)
(Page 1431)
● Ratio control (Page 1440)
● Ratio control with PIDConR (RatioR) (Page 1441)

Control blocks
● PID controller with Smith predictor (SmithPredictorControl) (Page 1436)

● Step controller with direct access to the actuator and without position feedback
(StepControlDirect) (Page 1437)
When the CPU starts up, the block is reinitialized but the stored reference values are
retained. The messages are suppressed after startup for the number of cycles set at
RunUpCyc.

0 Occupied
1 BatchEn
2 Not allocated
3 OosAct.Value
4 OosLi.Value
5 PID_AutAct.Value
6 OnAct.Value
15 CPI_Suppress

0 MsgLock
1 OvsAH_Act.Value
2 OvsWH_Act.Value
3-4 Not allocated
5 CPI_WL_Act.Value
6 CPI_AL_Act.Value
7 OvsAH_En
8 OvsWH_En
11 CPI_WL_En
12 CPI_AL_En
13 OvsAH_MsgEn
14 OvsWH_MsgEn
17 CPI_WL_MsgEn

Control blocks

18 CPI_AL_MsgEn
See also
ConPerMon messaging (Page 285)
ConPerMon I/Os (Page 287)
ConPerMon block diagram (Page 293)
ConPerMon error handling (Page 284)
ConPerMon modes (Page 272)

Control blocks
4.1.2 ConPerMon modes
ConPerMon operating modes

● On (Page 27)
"On"
You can find general information about the "On" mode in the On (Page 27) section.
"Out of service"
You can find general information about the "Out of service" mode in the Out of service
(Page 27) section.
See also
ConPerMon functions (Page 273)
Description of ConPerMon (Page 267)

Control blocks
4.1.3 ConPerMon functions
Functions of ConPerMon
Monitoring of stochastic characteristics of the control performance

The mean value of a variable relating to an ergodic stochastic process (Page 1468) can be
determined from a sliding time window with the length n = TimeWindow / SampleTime,
for example for the y = PV controlled variable:
1 n
y= ∑ y(i)
n i =1
A recursive formulation of this calculation is included in the MeanTime block that is called by
the ConPerMonblock. Most steady-state time series can be considered as being ergodic so
that the expected value can be estimated by averaging over a window of finite length.
The mean control deviation is ER_Mean = SP - PV_Mean. A mean steady-state control
deviation ≠ 0 at a constant setpoint is an indication for problems in the control loop if the
controller has I action. You should then check the following potential causes:
● The actuator does not have sufficient capacity. As a result, the controller's manipulated
signal constantly approaches its limit. This can be caused by unsuitably dimensioned
actuators or may simply by wear and tear.
● The manipulated variable demanded by the controller does not take effect in the process,
for example because the actuator is defective.
If a steady-state reference operating point (MV_Ref PV_Ref) is known, this can be used to
estimate the current mean steady state gain of a linear process model if it is assumed that
only disturbances with zero mean have an effect:
PVMean − PVRe f
StatGain =
MVMean − MVRe f
Normally the reference operating point is obtained during the initialization of the ConPerMon
block. Estimation of the steady state gain is then, however, impossible precisely at this
operating point. As an alternative, you can also enter the reference values PV_Ref and
MV_Ref manually at the appropriate block inputs. Typical steady-state operating points are
often known in advance, for example
● Flow control: PV = 0 for MV = 0, in other words, valve closed,
● Temperature control: PV = PV_Ambient for MV = 0, in other words, ambient
temperature
If the steady state gain changes gradually as time progresses, this is an indication of wear
phenomena in the process, such as deposits on heat exchangers, valves or shutters, failing
efficiency of process plant, etc.

Control blocks
If, for example, a temperature regulation circuit is closed by a heat exchanger and a deposit
forms on the exchanger surfaces, the heat transfer coefficient, and consequently the process
gain, is reduced. Within certain limits, this can be compensated by a closed control loop (so
that the controller initially disregards the problem). Although the original control loop
dynamics can be restored (to a certain extent) by suitable increase of the controller gain as
the pollution increases, it is advisable to eliminate the cause of the problem; in other words,
to clean the heat exchanger.
If the estimated steady state gain changes suddenly and temporarily, this tends to point to an
external disturbance. This may be a normal occurrence in the operation of the process. If,
however, these occurrences become more frequent, it is worth finding out the cause.
Due to the approach, the variance PV_Variance as second moment requires the
calculation of differences of each current measured value from (constant !) mean value:
1 n 2 1⎛ n 2 ⎞ 2
σ2y = ∑ ( y (i ) − y ) = ∑ y (i) ⎟⎠ − y
n − 1 i =1 n ⎜⎝ i =1
Within the function block, however, a variant of the calculation is used that saves computing
time. The standard deviation
PV _ StdDev = σ y = σ2y
as the square root of the variance is easier to interpret because it has the same physical unit
as the measured value.
The control performance index CPI (Control Performance Index) in the unit [%] describes the
current variance of the controlled variable relative to a benchmark (benchmark). It is defined
as
σ2ref
ς= 100%
σ2y
The CPI moves in the 0 < ς ≤ 100% range. If the current variance corresponds to the
benchmark, the index reaches the value 100. If, on the other hand, the current variance
increases, the control performance index drops accordingly. Ideally, the benchmark is
obtained in a defined good state of the control loop and stored when the ConPerMon block is
initialized. It does not matter if the CPI temporarily reaches values higher than 100%. A CPI
> 100% only means that the variance of the controlled variable is currently somewhat lower
than in the reference state. Other alternatives for determining the benchmark will be
explained in a separate section.
If you consider that the calculated CPI signal is too strongly affected by noise, you can
smooth it using the integrated level pass filter (parameter CPI_FiltFactor) with the filter
time constant TimeWindow · CPI_FiltFactor.
The disadvantage of these stochastic characteristics is that they assume an ergodic
(Page 1468) or steady state in the process - at least in a statistical sense. Each step change
in the standpoint in a controller is an elementary violation of this requirement and leads
temporarily to incorrect statements of the stochastic characteristics, for example variances
increasing too much. The basic principle of the combined approach implemented in the
ConPerMonblock is to use both stochastic and deterministic characteristics for the control
performance and to select the suitable characteristics automatically depending on the
operating state.

Control blocks
If a step change in the setpoint is detected in a control loop, the ConPerMon block freezes
the CPIvalue and automatically suppresses all messages relating to this. As the user, you
can also force the suppression of the messages manually via the ManSupprCPI = 1 binary
input. This setting is useful to avoid false alarms when known disturbances occur, for
example at a load change in a Conti process (Page 1468) or a dosing procedure in a Batch
process (Page 1467). In such cases the variance of the controlled variable usually rises
momentarily. This should not be interpreted as a worsening of the control performance.
Monitoring of deterministic characteristics of the control performance

Assessment of the control performance based on the response to a step change in the
setpoint is relatively simple. In the sense of automatic monitoring, the ConPerMon block is
capable of determining the essential characteristics of the control performance directly from
the signal changes so that when necessary a message or an alarm can be generated
automatically by the system.
The first thing to look for is always the overshoot if it is present and clearly distinct from the
noise level. For a positive step response,
OverAbso = max(PV) - SP > 0
is output where is for a negative step response (step response down), and negative values
OverAbso = min(PV) - SP < 0
are also output. For normalization, the absolute overshoot is related to the height of the step
change in the setpoint and is therefore always positive. The relative overshoot (Overshoot)
as a percentage is a measure of the damping of the control loop. If this is more than 20 or
30%, the loop gain (gain of the controller multiplied by the gain of the control system) is
generally too high either because the controller was badly set from the beginning or because
the properties of the control system have changed over the course of time. If overshoot is
significantly too high, the control loop is generating weakly damped oscillations in the plant.
The block sends a message to this effect if the relative overshoot is above a specified limit.

Control blocks

2YHU$EVR
7ROH+L39
7ROH/R39

6WHS+HLJKW

.H\
39

63

5LVH7LPH
6HWWOL7LPH
In every control loop, there is a general correlation between overshoot and phase reserve:
The higher the overshoot, the lower the phase reserve. If the response of the closed control
loop can be described approximately by a 2nd order transfer function
PV(s) 1
g cl (s) = =
SP(s) 1 2 δ
2
s + 2 s +1
ω0 ω0
the following relationships are known:
● If δ ≥ 1, the overshoot is equal to zero and the settling response is asymptotic.
● if δ < 1, overshoot and oscillations occur.

Control blocks
The damping of the closed loop can be determined approximately from the overshoot:
⎛ Overshoot ⎞
− ln ⎜ ⎟
δ= ⎝ 100% ⎠
⎛ Overshoot ⎞ 2
ln 2 ⎜ ⎟+π
⎝ 100% ⎠
'DPSLQJ

2YHUVKRRW>@
An optimum controller setting typically aims for overshoot between 5 and 25%, which means
damping between 0.7 and 0.4.
If overshoot is too high, it is often helpful to reduce the gain of the controller.
While overshoot primarily serves to check controller gain, there is a further characteristic that
provides information on the setting of the I action: If the setting of the reset time is
unsuitable, the process value will creep towards the new setpoint following a step change in
the setpoint. To allow normalization, the settling time SettliTime is related to the rise time
RiseTime of the step response of the control loop. If the settling ratio, in other words the
quotient of the rise time and settling time, is less than approximately 25%, it can generally be
assumed that the reset time of the controller is too slow. To determine the rise time and
settling time, a 3σ tolerance band is placed around the setpoint and is also displayed in the
faceplate of the ConPerMon block. The absolute values of the settling time and rise time can
be assessed in terms of the concrete requirements of the process control for a specific
application.

Control blocks
During a step change in the setpoint, larger mathematical variances of the controlled variable
are bound to occur compared with the steady state so that generating alarms due to the
variance limits being exceeded needs to be suppressed until the settling process has neared
completion following the step change in the setpoint. The calculated deterministic
characteristics are output and the stochastic evaluation is activated again.
Alternatives for determining the benchmark

During planned commissioning of a plant with integrated ConPerMon, following controller
optimization, the ConPerMon block is initialized for every control loop and the calculated
variance stored as the benchmark for calculating the CPI.
As an alternative, a benchmark can set via the RefVarExt input parameter by setting
RefVarExtOn = 1. There are various ways of obtaining numeric values for the benchmark:
● Take the lowest variance that was ever measured in this control loop since the
initialization of the ConPerMon block. This is displayed at the PV_VarMin output
parameter. This value is only useful when the control loop has been in a stable and
desirable operating state for a longer period of time at least once since the initialization of
the ConPerMon block.
● Take the variance of the control loop with a theoretical minimum variance controller as
can be obtained based on archived data using another supplier's CPM application. This
depends only on the process dead time and the disturbance model. This form of CPI is
known as the Harris index and represents a lower barrier that can generally not be
reached by a PID controller which is why CPI seldom reaches the value 100% even by
well tuned controllers. Low CPI values provide the first indication that the controller
settings could be improved. You should, however, bear in mind that the minimum
variance is only a theoretically achievable value and that the minimum variance controller
has characteristics that are not desired in the real application, for example extremely high
manipulated variable amplitudes. With minimum variance-based CPI, therefore, it is not
worth making every effort to bring this as close as possible to 100%.
Cascade control
In a cascade control, you should only use the ConPerMon block for the primary controller
and not for the secondary controller. The ConPerMon block cannot make any useful
statements about the control performance of the secondary controller because
● the variance of the process value in the secondary control loop depends directly on the
variance of the setpoint that is set as the manipulated variable by the primary controller,
● there are neither operating phases with a constant setpoint nor defined step changes in
the setpoint.
Apart from this, from the perspective of process control, the primary control loop is, of
course, the one whose control performance should be monitored while the control
performance of the secondary loop is of secondary importance. It is nevertheless advisable
to set the secondary controller carefully before optimization and monitoring of the primary
controller is started because a poor response by the secondary controller cannot be
compensated by the primary controller.
For additional information read about the process tag template Cascade control
(Page 1442).

Control blocks
Split-range control
The split-range function block contains two separate (static) characteristics for both
actuators. Any significant difference between the two actuators in terms of performance (in
other words, different process gains for heating and cooling) can be compensated by setting
different gradients for the characteristics, so that the controller is presented with a linear
process response (regardless of the sign) as far as possible. It this does not work, the
control performance will differ slightly in the two areas. The initialization of the ConPerMon
block should then be performed in the worse area to avoid error alarms.
For additional information read about the process tag template Split-range control
(Page 1438).
PID controller with gain scheduler

The aim of gain scheduling is to achieve consistent control performance over the entire
operating range. If this does not work perfectly, the initialization of the ConPerMon block
should be performed in an operating point with worse control performance to avoid error
alarms. We recommend that you expand the alarm limits somewhat at ConPerMon-Baustein:
permit lower CPIs and higher overshoot.
For additional information read about the process tag template PID - control with operating-
point-oriented parameter control (GainScheduling) (Page 1431).
Override control
For change-over control, different controllers are active depending on the process state; their
control performances differ, of course. We recommend using control loop monitoring only for
the primary controller, and to suppress it using the ManSuprCPI input parameter if limit
controlling is activated.
For additional information read about the process tag template Override control (Page 1445).
Feedforward control
The task of feedforward control is to avoid or at least to reduce degradation of the control
performance caused by a measurable disturbance variable. Control loop monitoring
therefore can basically be used as it is used for simple control loop. When the disturbance
variable is quiet for a time and then acts up for a brief period, the resulting fluctuations of the
control performance cannot be ruled out. The reason behind it is that feedforward control
represents a model-based intervention, and a model is never a perfect reflection of reality.
For additional information read about the process tag template PID controller with dynamic
feedforward control (FfwdDisturbCompensat) (Page 1433).
Smith predictor
The Smith predictor enables higher control performance than a simple PI controller in control
loops with dead time. Control loop monitoring therefore can basically be used as it is used
for simple control loop. If the dead time changes during ongoing operation, control
performance will most likely go down.
For additional information read about the process tag template PID controller with Smith
predictor (SmithPredictorControl) (Page 1436).

Control blocks
Ratio control
With ratio controlling, the control loop monitoring should only be used in the primary control
loop if the setpoints are to be determined for combined components from the actual value of
the primary component. In this case, you can expect continuous setpoint changes in the
control loops for the combined components - similar to sequential control loop of a cascade.
If the setpoints for combined components are to be determined from the setpoint of the
primary component, the lower-level control loops can be monitored as well.
For additional information read about the process tag template Ratio control (Page 1440).
Multivariable controller
The mathematical concept of the ConPerMon block is intended for monovariable control
loops. If the variance in a control loop is found to be too high, the block cannot determine
whether the actual cause is within the control loop or whether influences are being brought in
due to interactions from the outside. If, therefore, you notice strong interactions between
various control loops in your plant or even use multivariable controllers, the information
provided by the ConPerMon block should be treated with caution.
It can nevertheless make sense to equip a multivariable controller such as the ModPreCon
block with control loop monitoring to establish whether the control performance achieved
during commissioning of the controller is also retained in runtime. In this case, each
controller channel of the multivariable controller has a separate ConPerMon block. Several
additional logic functions need to be configured upstream from the ManSuprCPI input
parameter as shown in the corresponding specimen project Predictive control of a 2x2 multi-
variable controlled system (Page 1464):
● If one or more other channels for the multivariable controller is in a non steady state (for
example step change in the setpoint) indicated by the CPI_SupRoot = 1 output
parameter, the temporarily increased variance cannot be avoided in this controller
channel and should not cause a CPI message.
● If one or more other channels of the multivariable controller have higher variances (poor
control performance) indicated by the appropriate output CPI_WrnAct = 1, due to the
interaction, these variances cause a higher variance in this controller channel as well that
cannot be avoided and should not lead to a CPI warning. It is possible to find the actual
cause of a disturbance in a multivariable system as follows: The channel that first detects
higher variances, set the alarm while subsequent alarms in adjacent channels are
suppressed.
Note
In the case of multivariables, the estimated process gains from the monovariable
observation are irrelevant. By setting the input parameter StGainValid = 0 , this
status is also displayed in the faceplate as "Uncertain, process related".
If a PID controllers is remotely controlled in program mode (Page 34), it should be treated
similar to a secondary controller for a cascade connection in regard to control performance
monitoring, i.e. monitoring is usually impractical in this case.
If program mode is the typical operating mode of the controller involved, the corresponding
ConPerMon block can be completely removed. If the controller involved is often used in
automatic mode, however, monitoring can be temporarily disabled during program mode by
connecting the output parameter AdvCoAct of the PIDConL block to the input parameter
ManSupprCPI of the ConPerMon block.

Control blocks

The block provides the standard function Selecting a unit of measure (Page 53).

The block provides the standard function Forming and outputting signal status for blocks
(Page 88).
The worst signal status for the block is formed by the following parameters:
● SP_Mon.ST
● PV_Mon.ST
● MV_Mon.ST
● ER_Mean.ST
● In addition, the ConPerMon block has the following special functions for determining
status values:
● If you use a step controller without position feedback there is no manipulated variable that
you could interconnect with the input parameterMV_Mon. Unlike most other input
parameters, MV_Mon does not have the preset signal status "Uncertain, process related"
(16#78). If there is no interconnected value, this status is transferred to the calculated
output parameters MV_Mean and StatGain.
● StGainValid: Set this input to 0 if you use a multivariable controller or observe strong
interactions between neighboring control loops. This gives the calculated output
parameter StatGain the signal status "Uncertain, process related". If known
disturbances affect your process, for example dosing procedures in a batch process, you
can also set this input temporarily using the recipe control.
● Under normal circumstances the output parameter StatGain accepts the worse signal
status of PV_Mon and MV_Mon. Other possible causes of uncertain status for StatGain
are:
– the process is currently very close to the reference operating point, or
– the process is currently in transition, e.g. step change in the setpoint.
● The signal status of the CPI output parameter is dependent on output parameter
CPI_Suppress: If CPI_Suppress=1, the control performance index CPI is uncertain.
Apart from this, the CPI can also become uncertain in occasional situations when there
are numeric problems in the calculation of the variance. Under normal circumstances the
CPI signal status is the same as the PV_Mon signal status.
● The signal status of the OverAbso output parameter is set to invalid when step changes
in the setpoint are evaluated whose step change height is too low in relation to the noise
level.

Control blocks

Bit Function
Operator control permissions via parameters OS_Perm and OS1Perm

The block has the following operator control permissions (Page 45) for the parameter
OS_Perm:
Bit Function
0-1 Not allocated
3-27 Not allocated
28 1 = Operator can initialize the block
29 1 = Operator may input a value for the time window, the reference value for the controlled
variable and the reference value of the manipulated variable
30-31 Not allocated
The block has the following operator control permissions for the OS1Perm parameter:
Bit Function
0 1 = Operator can alter the limit (overshoot) for high alarm
1 1 = The operator can change the limit (process value) for the high warning
2 Not allocated
3 1 = Operator may change a value for the CPI hysteresis.
4 Not allocated
5 1 = The operator can change the limit (control performance index) CPI for the low
warning
6 1 = Operator can alter the limit (control performance index CPI) for low alarm
Alarm delays with one time value

The block provides the standard function One time value for all limits (Page 79).
This function is used only for monitoring the control performance index CPI.

This block provides the standard function Limit operation and display in the faceplate
(Page 78).

Control blocks

The block provides the standard function Generating instance-specific messages (Page 46)
without the time stamp function in the I/O devices.


This block provides the standard function SIMATIC BATCH functionality (Page 122).
See also

Control blocks
4.1.4 ConPerMon error handling
ConPerMon error handling

● Error numbers


-1 Predefined value when inserting the block, the block is not processed.
2 SampleTime < 0.001
10 TimeWindow < 20 · SampleTime
See also

Control blocks
4.1.5 ConPerMon messaging
Messaging
If the control performance falls below a defined limit a message is generated. This is also the
case when a defined limit for overshoot is exceeded when there is a step change in the
setpoint.
If the CPI temporarily exceeds the configured warning and alarm limits, it is not necessary to
trigger an alarm immediately. The main aim of the control loop monitoring is to signal the
need for maintenance or optimization measures in individual control loops. With the alarm
delay, you can make sure that an alarm is triggered only after the cause exists for longer
than a configured period AlmDelay.
● Instance-specific messages
Process messages
Message Message Message class Event

instance identifier
MsgEvID SIG 1 Alarm - high $$BlockComment$$
Overshoot - high alarm limit
violated
SIG 2 Warning - high $$BlockComment$$
Overshoot - high warning limit
violated
SIG 3 Warning - low $$BlockComment$$
CPI - low warning limit violated
SIG 4 Alarm - low $$BlockComment$$
CPI - low alarm limit violated
Explanation:

Control blocks
Instance-specific messages
You can use up to three instance-specific messages with this block.

instance identifier
MsgEvID SIG 5 AS process control message - fault $$BlockComment$$
External message 1
Status 16#@5%x@
External message 2
Status 16#@6%x@
External message 3
Status 16#@7%x@
Explanation:
Associated values for message instance MsgEvID

1 BatchName
2 StepNo
3 BatchID
4 CPI (control performance index)
ExtMsg1.ST
ExtMsg2.ST
ExtMsg3.ST
8 ExtVa108
9 ExtVa109
10 Reserved
The associated values 8 and 9 are assigned to the parameters ExtVa108 ... ExtVa109 and
can be used by yourself. Additional information is available in the "Process Control System
See also

Control blocks
4.1.6 ConPerMon I/Os
ConPerMon I/Os
Input parameters

AlmDelay Alarm delay time [s] for monitoring the REAL 0.0
control performance index CPI
0 = Alarm delay deactivated
BatchEn 1 = Enable allocation for batch control BOOL 0
BatchID Current batch ID DWORD 16#00000000
BatchName Current batch designation STRING[32] ''
BreakSuppress 1 = Cancel suppression of the control BOOL 0
performance alarm at the end of the
step response
CPI_AlmHys Alarm hysteresis of the control REAL 5.0
performance index [%]
CPI_AL_En 1 = Activate alarm (low) for monitoring BOOL 1
of control performance
CPI_AL_Lim Low alarm limit for control performance REAL 30.0
[%]
CPI_FiltFactor Low-pass filter for CPI, filter time REAL 10.0
constant = TimeWindow
·CPI_FiltFactor
CPI_WL_En 1 = Activate warning (low) for BOOL 1
monitoring of control performance
CPI_WL_Lim Low warning limit for control REAL 50.0
performance [%]
CPI_AL_MsgEn 1 = Activate alarm message for: BOOL 0
• Low limit for control performance
CPI_WL_MsgEn 1 = Activate warning message for: BOOL 0
• Low limit for control performance
ExtMsg1 Binary input for freely selectable STRUCT -
message 1 • Value: BOOL • 0
• ST: BYTE • 16#80
• ST: BYTE • 16#80
• ST: BYTE • 16#80

Control blocks

ExtVa108 Associated value 8 for messages ANY
(MsgEvID)
(MsgEvID)
• ... • 0
• Bit 31: BOOL • 0
InitRefVar 1 = Initialization of the block. The BOOL 0
benchmark of the controlled variable
and the reference values of the
controlled variable and manipulated
variable are measured in the steady
state.
ManSupprCPI 1 = Manual suppression of the CPI STRUCT -
calculation and message, e.g. during • Value: BOOL • 0
known disturbances
• ST: BYTE • 16#80
MsgEvId Message number (assigned DWORD 16#FFFFFFFF
automatically)
MsgLock 1 = Suppress process messages STRUCT -
• ST: BYTE • 16#80
MV_Mon Manipulated variable of the controller STRUCT -
for monitoring • Value: REAL • 1.0
• ST: BYTE • 16#80
MV_Ref Reference value of the manipulated REAL 0.0
variable
MV_Unit Unit of measure for manipulated INT 1342
variable
Occupied 1 = Occupied by batch control BOOL 0
OosLi 1 = Edge transition (0-1) = Out of STRUCT -
service, via interconnection or SFC • Value: BOOL 0
• ST: BYTE 16#80
(Page 273) • Bit 0: BOOL • 1
• ... • 1
• Bit 31: BOOL • 1
OS1Perm I/O for operator control permissions STRUCT -
(Page 273) • Bit 0: BOOL • 1
• ... • 1
• Bit 31: BOOL • 1
OvsAH_En 1 = Activate alarm (high) for overshoot BOOL 1

Control blocks

OvsAH_Lim Overshoot alarm limit [%] REAL 25.0
OvsAH_MsgEn 1 = Enable alarm message for BOOL 0
overshoot
OvsWH_En 1 = Activate warning (high) for BOOL 1
overshoot
OvsWH_Lim Overshoot warning limit [%] REAL 20.0
OvsWH_MsgEn 1 = Enable warning message for BOOL 0
overshoot
PID_AutAct 1 = Controller is in auto mode STRUCT -
• ST: BYTE • 16#80
PV_Mon Controlled variable for monitoring STRUCT -
• ST: BYTE • 16#80
PV_Ref Reference value for controlled variable REAL 0.0
PV_Unit Unit of measure for process value INT 1001
RefVarExt Reference value for PV_Variance in REAL 0.0
control loop "good" status
ReVaExOn 1 = Use the external reference value of BOOL 0
RefVarExt
RefVariance Variance of controlled variable in REAL 100.0
control loop "good" status
RunUpCyc Number of start cycles in which INT 32000
automatically)
SelFp1 1 = Call a block saved in this parameter ANY -
as an additional faceplate (Page 43) in
the standard view
SelFp2 1 = Call a block saved in this parameter ANY -
as an additional faceplate (Page 43) in
the preview
SP_Mon Setpoint of the corresponding controller STRUCT -
for monitoring • Value: REAL • 0.0
• ST: BYTE • 16#80
StGainValid 0 = Output parameter StatGain BOOL 1
systematically invalid, e.g. for multi-
variable processes
TimeWindow Width of the sliding time window [s] for REAL 120.0
statistical evaluations
UserStatus Freely assignable bits for use in BYTE 16#00
faceplate

Control blocks
Output parameters

CPI Control performanceindex STRUCT -
• ST: BYTE • 16#80
CPI_AL_Act 1 = Control performance alarm is active STRUCT -
• ST: BYTE • 16#80
CPI_Suppress 1 = Message for the control BOOL 1
performance index is suppressed;
retain last valid CPI value
CPI_SuRoot 1 = CPI message suppression is locally STRUCT -
active in this control loop • Value: BOOL • 0
• ST: BYTE • 16#80
CPI_WL_Act 1 = Control performance warning is STRUCT -
active for CPI • Value: BOOL • 0
• ST: BYTE • 16#80
errors
ER_Mean Mean value of the control deviation in STRUCT -
the time window [PV_Unit] • Value: REAL • 0.0
• ST: BYTE • 16#80
ErrorNum Output of current error number. For INT -1
block, see ConPerMon error handling
(Page 284)
MsgAckn ALARM_8P: Output ACK_STATE; WORD 0
message acknowledgment state
MsgErr 1 = Message processing error occurred BOOL 0
MsgStatus ALARM_8P: STATUS output WORD 0
Error information of ALARM_8P
MV_Mean Mean value of the manipulated variable STRUCT -
in the time window [MV_Unit] • Value: REAL • 0.0
• ST: BYTE • 16#80
• ST: BYTE • 16#80
OosAct 1 = Block is "Out of service" STRUCT -
• ST: BYTE • 16#80

Control blocks

OS1PermOut Display of OS1Perm DWORD 16#FFFFFFFF
OS1PermLog Display of OS1Perm with settings DWORD 16#FFFFFFFF
OverAbso Absolute overshoot of the step STRUCT -
response [PV_Unit] • Value: REAL • 0.0
• ST: BYTE • 16#80
Overshoot Relative overshoot of the step response STRUCT -
with respect to the step change height • Value: REAL • 0.0
[%]
• ST: BYTE • 16#80
OvsAH_Act 1 = Alarm due to overshoot is active STRUCT -
• ST: BYTE • 16#80
OvsWH_Act 1 = Warning due to overshoot is active STRUCT -
• ST: BYTE • 16#80
PV_Mean Mean value of the controlled variable in STRUCT -
the time window [PV_Unit] • Value: REAL • 0.0
• ST: BYTE • 16#80
PV_StdDev Standard deviation of the controlled STRUCT -
variable • Value: REAL • 0.0
• ST: BYTE • 16#80
PV_ToleHi Limit (high) of 3-sigma band around the REAL 0.0
setpoint is calculated when a
ConPerMon block is connected
PV_ToleLo Limit (low) of 3-sigma band around the REAL 0.0
setpoint is calculated when a
PV_Variance Variance of the controlled variable STRUCT -
• ST: BYTE • 16#80
PV_VarMin Minimum observed value of the process REAL 1.000000e+004
variance (slave pointer)
RefStdDev Standard deviation of controlled STRUCT -
variable in control loop "good" status • Value: REAL • 0.0
• ST: BYTE • 16#80
RiseTime Rise time of the step response [s] REAL 0.0
SettlRatio Ratio = Rise time / settling time *100% REAL 0.0
SettliTime Settling time of the step response [s] REAL 0.0
StatGain Steady-state process gain [PV_Unit / STRUCT -
MV_Unit] • Value: REAL • 0.0
• ST: BYTE • 16#80
Status1 Status word 1 (Page 267) DWORD 16#00000000

Control blocks

StepPhase Phase of the step response: INT 0
0 = Waiting
1 = Rising
2 = Overshoot
3 = Settled
See also

Control blocks
4.1.7 ConPerMon block diagram
ConPerMon block diagram

A block diagram is not provided for this block.
See also
4.1.8.1 ConPerMon views
Views of the ConPerMon block

The block ConPerMon provides the following views:
● ConPerMon standard view (Page 294)
● ConPerMon limit value view (Page 296)
● ConPerMon parameter view (Page 298)
● ConPerMon preview (Page 300)
● ConPerMon's setpoint view (Page 301)
● Block symbol for ConPerMon (Page 303)

Control blocks
4.1.8.2 ConPerMon standard view
ConPerMon standard view
2SHUDWLQJPRGH 2Q

&3,

2YHUVKRRW

39VWDQGDUGGHY r&
(5PHDQYDOXH r&

09PHDQYDOXH
&3,YDOLG 6WHDG\VWDWHJDLQ
)DFHSODWH

● On (Page 27)
(2) Display area for control performance

This area shows the current control performance index.
(3) Display area for the overshoot

This area shows you the relative overshoot based on a step change [%].

Control blocks
(4) Display area for the static evaluation of the current time window (TimeWindow)
This area shows you the statistical evaluation of the current time window. The following
values are evaluated:
● PV standard dev.: Standard deviation of the controlled variable
● ER mean value: Mean value of the control error
● MV mean value: Mean value of the manipulated variable
● Steady state gain: Steady-state process gain
(6) Display for CPI valid / CPI invalid

This area shows you if the control performance index is valid or invalid:
● CPI valid: Control performance is valid
● CPI invalid: Control performance is invalid
You set the limits for the control performance index in the limits views, depending on the
configuration in the engineering system (ES).
(7) Limit display

These colored triangles show you the configured limits in the respective bar graph.
(8) Bar graph for control performance index

This area shows you the current CPI control performance index in the form of a bar graph.
The visible area in the bar graph depends on the configuration in the engineering system
(ES).
See also
ConPerMon limit value view (Page 296)
ConPerMon parameter view (Page 298)
ConPerMon's setpoint view (Page 301)

Control blocks
4.1.8.3 ConPerMon limit value view
ConPerMon limit value view
(QDEOHRSHUDWLRQV &3,OLPLWV
+\VWHUHVLV
/ZDUQLQJ
/DODUP
2YHUVKRRWOLPLWV
+ZDUQLQJ

+DODUP
(1) CPI limits

In this area, you can enter the limits for the CPI control performance index. Refer to the
● Hysteresis
(2) Overshoot limits

In this area, you can enter the limits for the overshoot. Refer to the Changing values

Control blocks

process
control permissions
See also
ConPerMon standard view (Page 294)

Control blocks
4.1.8.4 ConPerMon parameter view
ConPerMon parameter view
(QDEOHRSHUDWLRQV 3DUDPHWHU
7LPHZLQGRZ V

39UHIYDULDQFH r&
39UHIVWGGHY r&
39UHIHUHQFH r&
09UHIHUHQFH
&3,
)DFHSODWH ,QLWLDOL]H
(1) Parameters
● Time window: Set the time window here, in which the statical evaluation for the following
values is to be performed:
– Standard deviation of the controlled variable
– Mean value of the control error
– Mean value of the manipulated variable
– Steady-state process gain
● PV reference: Reference value for controlled variable
● MV reference: Reference value of the manipulated variable
(2) Initialize button

Clicking this button initializes the block. The benchmark of the controlled variable and the
reference values of the controlled variable and manipulated variable are measured in the
steady state.

Control blocks

process
control permissions
See also

Control blocks
4.1.8.5 ConPerMon preview
ConPerMon preview
(QDEOHRSHUDWLRQV
2Q

2XWRIVHUYLFH
)DFHSODWH

process
control permissions
Additional information is available in the section Calling further faceplates (Page 43).

Control blocks
4.1.8.6 ConPerMon's setpoint view
Setpoint view of ConPerMon
6WHSHYDOXDWLRQ $EVROXWHRYHUVKRRW r&
2YHUVKRRW
6HWWOLQJWLPH V

6HWWOLQJUDWLR

'RQH &DQFHOHYDOXDWLRQ
(1) Absolute overshoot

The absolute overshoot is given in the physical unit of the actual value
(2) Overshoot
Output of the relative overshoot base on a step change.
(3) Settling time

Settling time of the step response in seconds
(4) Settling time ratio

The settling time ratio is formed from the ramp time by the settling time.
(5) Cancel evaluation button

You can use the button to show the evaluation of the step response.
(6) and (7) - (10) and : Status of the step response

The following states are shown here:
● (6) Textual display of the states
● (7) Ready (stationary state)
● (8) Rising phase (from the initial state to the first time setpoint is reached)
● (9) Overshoot
● (10) Steady state, i.e. the actual value is within the tolerance range of the setpoint

Control blocks
(11) Display: Evaluation of the step response in progress:

● Step evaluation
● Constant PV
See also

Control blocks
4.1.8.7 Block symbol for ConPerMon
Properties of the ConPerMon block icon

● Limits (high/low)
● Violation of alarm, warning, and tolerance limits
● Operating modes
● Memo display

CFC

type 1 block icon)

Control blocks
4.2 FmCont - Interface to module FM 355
4.2.1 Description of FmCont

Family: Control
Area of application for FmCont

● Fixed setpoint control
● Cascade control
● Ratio control
● Split-range control
How it works
Block FmCont is used to interface the FM 355 controller modules.
FmCont can be used for the C (continuous controllers) and S (step and pulse controllers)
module types. It contains the algorithms of the setpoint ramp, the setpoint rise limitation, and
the limit monitoring of the process value, the control error, and the position feedback. Limit
monitoring is not used on the module. The control function itself (e.g. PID algorithm) is
processed on the module.
You can use the FmCont block to monitor all relevant process values and to change all
relevant controller parameters.
Application examples of the FM 355 and detailed descriptions of the associated input and
output parameters can be found in the manual of the FM 355 controller module.
Process values such as temperatures, levels and flows can be controlled. However,
pressure processes which are not excessively fast are also possible.

Control blocks
Configuration
also installed automatically in the startup OB (OB 100). Set the input parameter LogAddr to
the module address from HW Config and the input parameter Channel to the desired
controller channel (1..4).
When the CFC function "Generate module drivers" is used, the following occurs
automatically:
● The parameter CoordNo is set
● The parameter FM355 is set in accordance with the module type C/S
● The in/out parameter EnCoord is interconnected with the output EN_CO_x of the
FM_CO block of the basic library (x = number of the rack)
● The output parameter EnCoNum is interconnected with the input ENCOx_yy of the
FmCont block (x = number of the rack, yy = coordination number).
For the control loop monitoring to work as planned in the trend view of the controller
faceplates, the
S7_xarchive:='Value,shortterm;'
attributes in the process tag types for control loops at the controller function block must be
set for the following tags:
● Input parameters:
– CPI_In
● Output parameters
– MV
– MV_HiAct
– MV_LoAct
– AutAct
– SP
– PV_Out
– PV_ToleHi
– PV_ToleLo
Use the Setting the startup characteristics (Page 187) feature to define the startup
characteristics of this block.

Control blocks

For a description of the individual parameters see the section I/Os of FmCont (Page 324).

0 Occupied
1 BatchEn
2 SimOn
3 OosAct.Value
4 OosLi.Value
5 AutAct.Value
6 Not allocated
7 ManAct.Value
8 SP_ExtAct.Value
9 MV_SafeOn.Value
10 MV_TrkOn.Value
11 MV.Value > ManLoLim for continuous or pulse controller
NOT FbkClosed.Value for step controller with/without position feedback
12 Open.Value
13 Close.Value
14 Stop.Value
15 FbkOpened.Value
16 FbkClosed.Value
19 AdvCoAct
20 1 = Input parameter Rbk is not interconnected (RbkOut.ST = 16#FF)
21 NegGain
22 MV_TrkAct.Value
23 FuzCon
24 OptimOcc OR FuzOptAct
28 1 = Analog controller (FM355 = 1 )
29 1 = Pulse controller (FM355 = 0 ANDStepCon = 0)
30 1 = Step controller with position feedback
(FM355 = 0 AND StepCon = 1 AND WithRbk = 1 )
31 1= Step controller without position feedback
(FM355 = 0 AND StepCon = 1 AND WithRbk = 0 )

Control blocks

0 MsgLock
1 PV_AH_Act.Value
2 PV_WH_Act.Value
3 PV_TH_Act.Value
4 PV_TL_Act.Value
5 PV_WL_Act.Value
6 PV_AL_Act.Value
7 PV_AH_En
8 PV_WH_En
9 PV_TH_En
10 PV_TL_En
11 PV_WL_En
12 PV_AL_En
13 PV_AH_MsgEn
14 PV_WH_MsgEn
15 PV_TH_MsgEn
16 PV_TL_MsgEn
17 PV_WL_MsgEn
18 PV_AL_MsgEn
19 ER_AH_Act.Value
20 ER_AL_Act.Value
21 ER_AH_En
22 ER_AL_En
23 ER_AH_MsgEn
24 ER_AL_MsgEn
25 RbkWH_Act.Value
26 RbkWL_Act.Value
27 RbkWH_En
28 RbkWL_En
29 RbkWH_MsgEn
30 RbkWL_MsgEn
31 MS_RelOp
See also
FmCont messaging (Page 321)
FmCont block diagram (Page 338)
FmCont modes (Page 308)
FmCont error handling (Page 319)
FmCont functions (Page 309)

Control blocks
4.2.2 FmCont modes
FmCont operating modes

The next section provides additional block-specific information relating to the general
descriptions.
Automatic mode
You can find general information on "Automatic mode", switching modes and bumpless
switchover in the Manual and Automatic mode for control blocks (Page 29) section.
Manual mode
You can find general information on "Manual mode", switching modes and bumpless
Program mode for controllers

General information on "Program mode for controllers" is available in the section Program
mode for closed-loop controllers (Page 34).
Out of service
(Page 27) section.
See also
FmCont I/Os (Page 324)
Description of FmCont (Page 304)

Control blocks
4.2.3 FmCont functions
Functions of FmCont
Module types
FmCont can be used for the C (continuous controllers) and S (step controllers with and
without position feedback and pulse controllers) module types. You can use the following
parameters to identify which module type and controller type has been set:
FM355 StepCon WithRbk Module type, controller type

1 or C - - FM 355 C: Continuous controller
0 or S 1 1 FM 355 S: Step controller with position feedback
0 or S 1 0 FM 355 S: Step controller without position feedback
0 or S 0 - FM 355 S: Pulse controller
You must set input parameter StepCon if you want to set the step controller with/without
position feedback as the controller type.

Control blocks
Generating manipulated variables for continuous controllers, step controllers with position feedback,
or pulse controllers
The manipulated variable MV and the actuating signals Open, Close and Stop are
generated as follows:
MV_SafeOn MV_FmTrkOn ManAct MV_TrkOn AdvCoAct MV = Limitation State Open,

AND NOT of the mani- Close, Stop
AdvCoMod pulated
SP variable
1 - - - - MV_Safe MV_HiLim Tracking to Cont.

MV_LoLim
safety value controller:
0 1 - - - Prepared MV_HiLim Tracking to Open,
MV_LoLim Close,
FM analog an FM
input analog Stop =
input False
0 0 1 - - Man ManHiLim Manual Step
ManLoLim controller
mode, set
by the with
operator position
feedback:
0 0 0 1 - MV_Trk MV_HiLim Tracking to
MV_LoLim
block input Depending
MV_Trk on Rbk and
0 0 0 0 1 AdvCoMV MV_HiLim Higher-level MV, the
MV_LoLim output
program
mode signals
Open,
0 0 0 0 0 P_Part + MV_HiLim Automatic
MV_LoLim Close and
I_Part + mode (PID Stop are
D_Part + algorithm) generated
FFwd
using the
algorithm of
a
positioner.
Pulse
controller:
Depending
on MV, the
output
signals
Open and
Close are
generated
using the
algorithm of
a pulse
controller
(Stop = 0).

Control blocks
Generating manipulated signals for step controllers without position feedback (WithRbk = 0)
The manipulated variable signals Open, Close and Stop can be generated as follows:
ManAct Open, Close, Stop State

1 The output signals are generated using Manual mode, set by the operator
input signals OpenOp/Li, CloseOp/Li
or StopOp/Li.
0 The output signals are generated using Automatic mode (PID algorithm)
PID output parameters P_Part,
I_Part, D_Part and FFwd.
Tracking and limiting a manipulated variable (cont. controller, step controller with position feedback
and pulse controller)
The block provides the standard function Tracking and limiting a manipulated value
(Page 111).
Safe position
The controller modules have their own mechanism for feedforwarding a safety value (see
Temperature Controller FM 355-2 manual or Controller Module FM 355 manual)
"Actuator active" information

For continuous and pulse controllers: If the manipulated variable MV is greater than the
minimum manual limit ManLoLim, this is recognized as actuator active.
For step controllers: If the parameter FbkClosed = 0, this is known as "Actuator active".
This status can be used to display a custom icon in the process image, for example, and is
saved in the status word (see Status word section in Description of FmCont (Page 304)).
Limit monitoring of position feedback (cont. controller, step controller with position feedback and pulse
controller)
The block provides the standard function Limit monitoring of the feedback (Page 76).
External/internal setpoint specification

The block provides the standard function Setpoint input - internal and external (Page 96).

The block provides the standard function Setpoint limiting for external setpoints (Page 110).

The block provides the standard function Ramp limiting of the setpoint (Page 108).

Control blocks
Using setpoint ramp

The block provides the standard function Using a setpoint ramp (Page 98).

The block provides the standard function Setpoint tracking the process variable in manual
mode (Page 110).
Simulating signals
The block provides the standard function Simulating signals (Page 93).
You can simulate the following values:
● Process value (SimPV)
● Position feedback (SimRbk)
Note
The simulated process value SimPV only affects alarm processing and not the PID
algorithm in the controller module.

The block provides the standard function Limit monitoring of the process value (Page 70).

The block provides the standard function Control error generation and deadband (Page 109).

The block provides the standard function Monitoring the error signal limits (Page 77).
Inverting control direction

The block provides the standard function Inverting the control sense (Page 108).

Control blocks
Physical standardization of setpoint, manipulated variable and process value

Controller gain Gain is entered either using a physical variable or as standardized value.
● Gain as a physical variable:
The standardized variables retain their default values:
– NormPV.High = 100 and NormPV.Low = 0
– NormMV.High = 100 and NormMV.Low = 0
For step controllers with/without position feedback and pulse controllers, the values of
NormMV.High and NormMV.Low are not taken into account. The algorithm uses default
values 0 and 100 for internal calculations.
The effective gain is: GainEff = Gain
● Entering a standardized gain (dimensionless):
Change the standardized variables to the actual range of the process values and
manipulated variables.
– Internal and external setpoints; the process value and corresponding parameters are
entered according to the physical measuring range of the process value.
Continuous controller, pulse controller:
– The manual value, the tracking value of the manipulated variable, feedforward control
and the corresponding parameters are set according to the physical measuring range
of the manipulated variable.
Step controller with position feedback:
and the corresponding parameters are entered as a percentage between 0 ... 100.
Step controller without position feedback:
– No physical measuring range available.
The effective gain is:
– Step controller with/without position feedback:
GainEff = 100,0 / (NormPV.High - NormPV.Low) · Gain
– Continuous controller, pulse controller:
GainEff = (NormMV.High - NormMV.Low)/(NormPV.High - NormPV.Low)
· Gain

Control blocks

PID algorithm
The manipulated variable is generated in automatic mode according to the following
algorithm:
MV = Gain · (1 + 1/TI · s) + TD/( 1 + TD/DiffGain · s) · ER
Where: s = Complex number
The following step response occurs:
09
09B+L/LP
*DLQ 7'
7LPH/DJ6DPSOH7LPH
*DLQ
(5 W *DLQ
*DLQ
W
7,
09B/R/LP
,QSXWMXPS(5 W ` LIW
LIW!
Note
This formula describes a standard application where the P, I and D actions are activated and
the P and D actions are not in the feedback circuit (PropSel = 1, TI ≠ 0D_InSel =
0and P_FbkSel = 0).
The D action delay is derived from TD/DiffGain.

● The P action can be shut down by PropSel = 0.
● The I action can be shut down by TI = 0.
● The D action can be shut down by TD = 0.

The PID controller algorithm of FM355 features structure segmentation. It is activated via the
P_FbkSel and D_InSel parameters. The precise functionality is described in the FM355
manual.
Anti-windup
The PID control algorithm of FM355 has an anti-windup function. The I action is frozen or
tracked after the manipulated variable has reached its limits (MV_HiLim or MV_LoLim).

Control blocks
Activating and limiting disturbance variables

The block provides a function for activating the disturbance variable. The precise
functionality is described in the FM355 manual.

(Page 88).
● Rbk.ST
● FFwdOut.ST
● ER.ST
● MV.ST

Bit Function

Control blocks

OS_Perm:
Bit Function
0 1 = Operator can switch into automatic mode AutModOp
1 1 = Operator can switch into manual mode ManModOp
2 1 = Operator can switch into "out of service" mode OosOp
3 1 = Operator can switch into program mode AdvCoEn
4 1 = Operator can switch the setpoint to external SP_ExtOp
5 1 = Operator can switch the setpoint to internal SP_IntOp
6 1 = Operator can change the internal setpoint SP_Int
7 Continuous controllers, pulse controllers or step controllers with position feedback:
1 = Operator can change the manual parameter Man
1 = Operator can change the manual operation signals OpenOp, StopOp, CloseOp
8 1 = Operator can change maximum usage limit of the setpoint SP_InHiLim
9 1 = Operator can change minimum usage limit of the setpoint SP_InLoLim
10 1 = Operator can change maximum usage limit of the manipulated variable ManHiLim
11 1 = Operator can change minimum usage limit of the manipulated variable ManLiLim
12 1 = Operator can use the setpoint's gradient limitation function SP_RateOn
13 1 = Operator can change the setpoint's high limit for the ramp SP_UpRaLim
14 1 = Operator can change the setpoint's low limit for the ramp SP_DnRaLim
15 1 = Operator can change between the time value or the value for the ramp
SP_RmpModTime
16 1 = Operator can change the ramp time SP_RmpTime
17 1 = Operator can change the target setpoint SP_RmpTarget for the setpoint ramp
18 1 = Operator can activate the setpoint ramp function SP_RmpOn
19 Not allocated
20 1 = Operator can activate the track setpoint in manual mode function SP_TrkPV
21 1 = Operator can activate the bumpless changeover from external to internal function
SP_TrkExt
22 1 = Operator can change the gain parameter Gain
23 1 = Operator can change the integral action time parameter TI
24 1 = Operator can change the derivative action time parameter TD
25 1 = Operator can change the derivative gain parameter DiffGain
26 1 = Operator can change the dead band parameter DeadBand
27 Not allocated
28 1 = Operator can change the integral action time parameter MotorTime
29 1 = Operator can change the integral action time parameter PulseTime
30 1 = Operator can change the integral action time parameter BreakTime
31 Not allocated

Control blocks
Bit Function
0 1 = Operator can change the limit (process value) for the high alarm PV_AH_Lim
1 1 = Operator can change the limit (process value) for the high warning PV_WH_Lim
2 1 = Operator can change the limit (process value) for the high tolerance PV_TH_Lim
3 1 = Operator can change the hysteresis (process value) PV_Hyst
4 1 = Operator can change the limit (process value) for the low tolerance PV_TL_Lim
5 1 = Operator can change the limit (process value) for the low warning PV_WL_Lim
6 1 = Operator can change the limit (process value) for the low alarm PV_AL_Lim
7 1 = Operator can change the limit (control error) for the high alarm ER_AH_Lim
8 1 = Operator can change the hysteresis (control error) ER_Hyst
9 1 = Operator can change the limit (control error) for the low alarm ER_AL_Lim
10 1 = Operator can change the limit (position feedback) for the high warning RbkWH_Lim
11 1 = Operator can change the hysteresis (position feedback) RbkHyst
12 1 = Operator can change the limit (position feedback) for the low warning RbkWL_Lim
16 1 = Operator can activate the simulation function SimOn
17 1 = Operator can activate the maintenance release function MS_RelOp
Maintenance release
The block provides the standard function Maintenance release (Page 47).

This block provides the standard function Display and operator input area for process values



Control blocks
See also
Two time values per limit pair (Page 80)
Safety value of the manipulated variable effective at startup (Page 196)
Out of service (Page 27)
Safe position for motors, valves and controllers (Page 120)

Control blocks
4.2.4 FmCont error handling
FmCont error handling

● Error numbers

The ErrorNum output parameter can be used to output various error numbers. An overview
of all error numbers is available in the section "Functions of blocks > Error handling
(Page 117)".
Error numbers output by this block:

30 The value of PV can no longer be displayed in the REAL number field.
31 The value of SP_Ext can no longer be displayed in the REAL number field.
33 The value of MV_Trk can no longer be displayed in the REAL number field.
35 The value of Rbk can no longer be displayed in the REAL number field.
36 The value of MV can no longer be displayed in the REAL number field.
50 The controller cannot be switched in program mode, because program mode with
setpoint specification (AdvCoModSP=false) is not possible with step controllers
without position feedback (WithRbk=false).
60 |Tl| < SampleTime/2
61 |TD| < SampleTime
62 DiffGain < 1 oder DiffGain > 10
63 TD/DiffGain < SampleTime/2
64 PropFacSP < 0 or PropFacSP > 1
66 NormPV_High = NormPV_Low
67 MotorTime < SampleTime
68 PulseTime < SampleTime
69 BreakTime < SampleTime
70 Channel < 1 or Channel > 4
71 (D_InSel < 0 or D_InSel > 4)
and D_InSel ≠ 17

Control blocks
See also
Setting switch or button mode (Page 195)

Control blocks
4.2.5 FmCont messaging
Messaging
● Control system fault
Control system fault

The following control system error messages can be output:

instance identifier
MsgEvId2 SIG 6 AS process control message - fault $$BlockComment$$
External error has occurred
Explanation:
You can interconnect an external fault (signal) to input parameter CSF. If this signal changes
to CSF = 1, a control system fault is triggered (MsgEvId2, SIG 6).
Process messages

instance
MsgEvId1 SIG 1 Alarm - high $$BlockComment$$
PV - high alarm limit violated
PV - high warning limit violated
SIG 3 Tolerance - high $$BlockComment$$
PV - high tolerance limit violated
SIG 4 Tolerance - low $$BlockComment$$
PV - low tolerance limit violated
PV - low warning limit violated
PV - low alarm limit violated
SIG 7 Alarm - high $$BlockComment$$
ER - high alarm limit violated
ER - low alarm limit violated

Control blocks

instance
MsgEvId2 SIG 7 Warning - high $$BlockComment$$
Rbk - high warning limit violated
Rbk - low warning limit violated
Explanation:
You can use up to four instance-specific messages with this block.

instance
MsgEvId2 SIG 1 AS process control message - $$BlockComment$$
fault External message 1
Status 16#@5%x@
SIG 2 AS process control message - $$BlockComment$$
Status 16#@6%x@
Status 16#@7%x@
Status 16#@8%x@
Explanation:

Control blocks
Associated values for message instance MsgEvId1

1 BatchName
2 StepNo
3 BatchID
4 Process value PV_Out
5 Control error ER
6 ExtVa106
7 ExtVa107
8 Not allocated
9 Not allocated
10 Not allocated
you can use them. Additional information is available in the "Process Control System PCS 7
- Engineering System" manual.

1 BatchName
2 StepNo
3 BatchID
4 Position feedback Rbk
5 Signal status ExtMsg1
9 ExtVa209
10 ExtVa210
The associated values 9 and 10 are assigned to the parameters ExtVa209 ... ExtVa210
and you can use them. Additional information is available in the "Process Control System
See also

Control blocks
4.2.6 FmCont I/Os
FmCont I/Os
Input parameters

AccMode 1 = Transfer of operating parameters BOOL 1
SubN1_ID, SubN2_ID, RackNo, SlotNo and
Channel to internal processing
AdvCoEn 1 = Enable program mode via interconnection STRUCT -
• ST: BYTE • 16#80
AdvCoModSP Type of program mode: BOOL 1
1 = Setpoint specification
0 = Manipulated variable specification
AdvCoMstrOn Activate (0-1) or deactivate (1-0) program STRUCT -
mode via edge transition • Value: BOOL • 0
• ST: BYTE • 16#80
AdvCoMV Specified value from the external program REAL 0.0
AdvCoOn 1 = Enable program mode via faceplate BOOL 0
AutModLi 1 = Automatic mode via interconnection or STRUCT -
SFC (controlled via ModLiOp = 1) • Value: BOOL • 0
• ST: BYTE • 16#80
AutModOp 1 = Automatic mode by operator (controlled via BOOL 0
ModLiOp = 0)
BatchEn 1 = Enable allocation for batch control BOOL 0
BreakTime Minimum break time [s] REAL 1.0
Channel Controller channel number (1..4) INT 1
CloseLi 1 = Close via interconnection or CFC STRUCT -
• ST: BYTE • 16#80
CloseOp 1 = Close via operator BOOL 0
CoordNo Coordination number INT 0
CPI_In Input for control performance index, which is STRUCT -
calculated by the assigned ConPerMon block • Value: REAL • 0.0
• ST: BYTE • 16#78
CSF 1 = External error (control system error) STRUCT -
• ST: BYTE • 16#80

Control blocks

D_InSel Input for differentiator: INT 0
0 = Control error
1..4 = Channel 1..4
17 = Actual value to feedback
DeadBand Width of dead band REAL 0.0
DiffGain Gain of differentiator [1...10] DiffGain = STRUCT -
TD/(delay time of D action) • Value: REAL • 5.0
• ST: BYTE • 16#80
ER_A_DC Delay for incoming alarms during control error REAL 0.0
monitoring
ER_A_DG Delay for outgoing alarms during control error REAL 0.0
monitoring
ER_AH_En 1 = Activate alarm (high) for control error BOOL 1
monitoring
ER_AH_Lim Alarm limit (high) for control error monitoring REAL 100.0
ER_AH_MsgEn 1 = Activate messages for alarm (high) for BOOL 1
control error monitoring
ER_AL_En 1 = Activate alarm (low) for control error BOOL 1
monitoring
ER_AL_Lim Alarm limit (low) for control error monitoring REAL -100.0
ER_AL_MsgEn 1 = Activate messages for alarm (low) for BOOL 1
ER_Hyst Alarm hysteresis for control error REAL 1.0
ExtMsg1 Binary input for freely selectable message 1 STRUCT -
• ST: BYTE • 16#80
• ST: BYTE • 16#80
• ST: BYTE • 16#80
• ST: BYTE • 16#80
ExtVa106 Associated value 6 for messages (MsgEvID1) ANY
(MsgEvID2)

Control blocks

FbkClosed Low limit stop signal of position feedback STRUCT -
• Value: BOOL 0
• ST: BYTE 16#80
FbkOpened High limit stop signal of position feedback STRUCT -
• ST: BYTE • 16#80
• ... • 0
• Bit 31: BOOL • 0
FM355 Module type: BOOL 0
0: FM 355 S; 1: FM 355 C
FuzOptOn Fuzzy optimization BOOL 0
Gain Proportional gain STRUCT -
Gain.ST = 16#FF: Operable in faceplate • Value: REAL • 1.0
LogAddr Logical address FM 355 INT 0
Man Manual specification for the manipulated REAL 0.0
variable
ManHiLim Limit (high) for manual parameter Man REAL 100.0
ManLoLim Limit (low) for manual parameter Man REAL 0.0
ManModLi 1 = Manual mode via interconnection or SFC STRUCT -
(controlled via ModLiOp = 1) • Value: BOOL • 0
• ST: BYTE • 16#80
ManModOp 1 = Manual mode via OS operator (controlled BOOL 1
via ModLiOp = 0)
Mode Operating mode DWORD 16#0
ModLiOp Operating mode switchover between: STRUCT -
0 = Operator • Value: BOOL • 0
1 = Interconnection or SFC • ST: BYTE • 16#80
MotorTime Motor manipulating time [s] REAL 30.0
MS_RelOp 1 = Maintenance release by OS operator BOOL 0
MsgEvId1 Message number (assigned automatically) DWORD 16#FFFFFFFF
MsgEvId2 Message number (assigned automatically) DWORD 16#FFFFFFFF
MsgLock 1 = Suppress process messages STRUCT -
• ST: BYTE • 16#80
MV_FmTrkOn 1 = Manipulated variable tracking in the FM STRUCT -
• ST: BYTE • 16#80

Control blocks

MV_HiLim Limit (high) for manipulated variable MV STRUCT -
• ST: BYTE • 16#80
MV_LoLim Limit (low) for manipulated variable MV STRUCT -
• ST: BYTE • 16#80
MV_OpScale OS display range for manipulated variable MV STRUCT -
• High: REAL • 100.0
• Low: REAL • 0.0
MV_Safe Safety manipulated variable REAL 0.0
MV_SafeOn 1 = Output safety manipulated variable STRUCT -
MV_Safe at output MV • Value: BOOL • 0
• ST: BYTE • 16#80
MV_Trk Tracking value for the manipulated variable MV STRUCT -
• ST: BYTE • 16#80
MV_TrkOn 1 = Tracking of manipulated variable MV STRUCT -
• ST: BYTE • 16#80
MV_Unit Unit of measure for manipulated variable INT 1342
NegGain 0 = Positive controller gain: ER = Gain · (SP - STRUCT -
PV) • Value: BOOL • 0
1 = Negative controller gain: ER = Gain · (PV - • ST: BYTE • 16#80
SP)
NormMV Manipulated variable range (MV) for STRUCT -
standardizing the proportional gain (GAIN) • High: REAL • 100.0
NormPV Process value range (PV) for standardizing the STRUCT -
proportional gain (GAIN) • High: REAL • 100.0
Occupied Occupied by batch control BOOL 0
OosLi Edge transition (0-1) = Out of service, via STRUCT -
• ST: BYTE • 16#80
OP_Sel Operation via OP BOOL 0
0 = Off (P bus)
1 = On (K bus)
OpenLi 1 = Open via interconnection or CFC STRUCT -
• ST: BYTE • 16#80
OpenOp 1 = Open via operator BOOL 0

Control blocks

OptimEn 1 = Enable optimization of PID parameters by BOOL 0
PID tuner
OptimOcc 1 = Optimization running BOOL 0
(Page 309) • Bit 0: BOOL • 1
• ... • 1
• Bit 31: BOOL • 1
OS1Perm I/O for operator control permissions STRUCT -
(Page 309) • Bit 0: BOOL • 1
• ... • 1
• Bit 31: BOOL • 1
P_FbkSel 1 = P action in feedback BOOL 0
PropSel 1 = Activate P action BOOL 1
PulseTime Minimum pulse duration [s] REAL 1.0
PV_A_DC Delay time for incoming PV alarms [s] REAL 0.0
PV_A_DG Delay time for outgoing PV alarms [s] REAL 0.0
PV_AH_En 1 = Enable PV alarm limit (high) BOOL 1
PV_AH_Lim PV alarm limit (high) REAL 95.0
PV_AH_MsgEn 1 = Enable message for PV alarm (high) BOOL 1
PV_AL_En 1 = Enable PV alarm limit (low) BOOL 1
PV_AL_Lim PV alarm limit (low) REAL 5.0
PV_AL_MsgEn 1 = Enable message for PV alarm (low) BOOL 1
PV_Hyst Hysteresis for PV alarm, warning and REAL 1.0
tolerance limits
PV_OpScale Limit for scale in PV bar graph of faceplate STRUCT -
• High: REAL • 100.0
PV_T_DC Delay time for incoming PV tolerance REAL 0.0
messages [s]
PV_T_DG Delay time for outgoing PV tolerance REAL 0.0
messages [s]
PV_TH_En 1 = Enable PV tolerance limit (high) BOOL 0
PV_TH_Lim PV tolerance message limit (high) REAL 85.0
PV_TH_MsgEn 1 = Enable message for PV tolerance BOOL 1
message (high)
PV_TL_En 1 = Enable PV tolerance limit (low) BOOL 0
PV_TL_Lim PV tolerance message limit (low) REAL 15.0
PV_TL_MsgEn 1 = Enable message for PV tolerance BOOL 1
message (low)
PV_Unit Unit of measure for process value INT 1001
PV_W_DC Delay time for incoming PV warnings [s] REAL 0.0
PV_W_DG Delay time for outgoing PV warnings [s] REAL 0.0
PV_WH_En 1 = Enable PV warning limit (high) BOOL 1

Control blocks

PV_WH_Lim PV warning limit (high) REAL 90.0
PV_WH_MsgEn 1 = Enable message for PV warning (high) BOOL 1
PV_WL_En 1 = Enable PV warning limit (low) BOOL 1
PV_WL_Lim PV warning limit (low) REAL 10.0
PV_WL_MsgEn 1 = Enable message for PV warning (low) BOOL 1
RackNo Rack number BYTE 16#FF
Rbk Position feedback for display on OS STRUCT -
RbkHyst Alarm hysteresis for position feedback REAL 1.0
RbkWH_En 1 = Enable warning (high) for position BOOL 1
feedback
RbkWH_Lim Limit for position feedback of warning (high) REAL 100.0
RbkWH_MsgEn 1 = Enable messages for warning (high) for BOOL 1
position feedback
RbkWL_En 1 = Enable warning (low) for position feedback BOOL 1
RbkWL_Lim Limit for position feedback of warning (low) REAL 0.0
RbkWL_MsgEn 1 = Enable messages for warning (low) for BOOL 1
position feedback
RefStdDevIn Reference value of PV standard deviation STRUCT -
(sigma) in defined "good" state of control loop • Value: REAL • 0.0
• ST: BYTE • 16#78
RunUpCyc Number of cycles in startup; messages are INT 3
suppressed during these cycles
S_RbkOnPIDTun Simulation of position feedback on; BOOL 0
For PCS 7 PID tuner only
S_RbkPIDTun Simulated position feedback REAL 50.0
SampleTime Sampling time [s] (assigned automatically) REAL 0.1
additional faceplate (Page 43) in the standard
view
additional faceplate (Page 43) in the preview
SimOn 1 = Simulation on BOOL 0
SimPV Process value used for SimOn = 1 REAL 0.0
SimRbk Position feedback used for SimOn = 1 REAL 0.0
SlotNo Slot number BYTE 16#FF
SP_DnRaLim Limit (low) for ramp of setpoint [SP_Unit/s] REAL 100.0
SP_ExHiLim Limit (high) for external setpoint STRUCT -
• ST: BYTE • 16#80

Control blocks

SP_ExLoLim Limit (low) for external setpoint STRUCT -
• ST: BYTE • 16#80
SP_Ext External setpoint of - (to interconnection) STRUCT -
• ST: BYTE • 16#80
SP_ExtLi 1 = Select external setpoint (via STRUCT -
interconnection) • Value: BOOL • 0.0
• ST: BYTE • 16#80
SP_ExtOp 1 = Select external setpoint (via operator) BOOL 0
SP_InHiLim Limit (high) of internal setpoint REAL 100.0
SP_InLoLim Limit (low) of internal setpoint REAL 0.0
SP_Int Internal setpoint for operation REAL 0.0
SP_IntLi 1 = Select internal setpoint (via STRUCT -
interconnection) • Value: BOOL • 0.0
• ST: BYTE • 16#80
SP_IntOp 1 = Select internal setpoint (via operator) BOOL 0
SP_LiOp Select setpoint source (internal/external): STRUCT -
1 = Via interconnection • Value: BOOL • 0.0
0 = Via operator • ST: BYTE • 16#80
SP_RateOn 1 = Activate limitation of setpoint gradients BOOL 0
SP_RmpModTime 1 = Use time (SP_RmpTime) for setpoint ramp, BOOL 0
0 = Use gradient
SP_RmpOn 1 = Activate setpoint ramp to target setpoint BOOL 0
SP_RmpTarget
SP_RmpTarget Target setpoint for setpoint ramp REAL 0.0
SP_RmpTime Time for setpoint ramp [s] from current SP up REAL 0.0
to SP_RmpTarget
SP_TrkExt 1 = Bumpless switchover from external to BOOL 1
internal setpoint active
SP_TrkPV 1 = Setpoint follows PV in manual mode and BOOL 0
with tracking
SP_UpRaLim Gradient limit (high) for setpoint [SP_Unit/s] REAL 100.0
StepCon Controller type in the FM 355 S: BOOL 0
0 = Pulse controller
1 = Step controller
StopLi 1 = Stop via interconnection or CFC STRUCT -
• ST: BYTE • 16#80
StopOp 1 = Stop via operator BOOL 0
SubN1_ID ID of the primary DP master system BYTE 16#FF

Control blocks

SubN2_ID ID of the redundant DP master system BYTE 16#FF
TD Derivative action time [s] STRUCT -
TD.ST = 16#FF: Operable in faceplate • Value: REAL • 0.0
TI Integral action time [s] STRUCT -
TI.ST = 16#FF: Operable in faceplate • Value: REAL • 100.0
UserStatus Freely assignable bits for use in faceplate BYTE 16#00
In/out parameters

EnCoord Current coordination number STRUCT -
• CO_ACT : INT • 0

Control blocks
Output parameters

AdvCoAct 1 = Program mode is active STRUCT -
• ST: BYTE • 16#80
AdvCoRdy 1 = Program mode available STRUCT -
• ST: BYTE • 16#80
AutAct 1 = Automatic mode is active STRUCT -
0 = Manual mode is active • Value: BOOL • 0
• ST: BYTE • 16#80
ChFM_Err 1 = Channel error on the module BOOL 0
Close Control output: STRUCT -
1 = Closed is active • Value: BOOL • 0
• ST: BYTE • 16#80
EnCoNum Coordination number BYTE 16#0
errors
ER Control error STRUCT -
• ST: BYTE • 16#80
ER_AH_Act 1 = Alarm limit (high) for control error STRUCT -
violated • Value: BOOL • 0
• ST: BYTE • 16#80
ER_AL_Act 1 = Alarm limit (low) for control error STRUCT -
• ST: BYTE • 16#80
ErrorNum Output of present error number, for INT -1
block, see FmCont error handling
(Page 319)
FbkClsOut 1 = Low limit stop of the position STRUCT -
feedback reached • Value: BOOL • 0
• ST: BYTE • 16#80
FbkOpnOut 1 = High limit stop of the position STRUCT -
• ST: BYTE • 16#80
FFwdOut Disturbance variable generated in the STRUCT -
FM Value: REAL 0.0
ST: BYTE 16#80

Control blocks

FuzCon Controller type: BOOL 0
0 = PID controller
1 = Fuzzy controller
FuzOptAct 1 = Optimization of fuzzy controller BOOL 0
active
FuzSP_PV_Act Fuzzy controller display: BOOL 0
Setpoint < actual value
GainEff Effective proportional gain, depends on REAL 1.0
Gain and NormPV
ManAct 1 = Manual mode active STRUCT -
• ST: BYTE • 16#80
ManARW_Act 1 = Tracking mode or anti-reset windup STRUCT -
by secondary controller • Value: BOOL • 0
• ST: BYTE • 16#80
ManHiOut Limit (high) for manual mode, STRUCT -
corresponds to the input parameter • Value: REAL • 100.0
ManHiLim
• ST: BYTE • 16#80
ManLoOut Limit (low) for manual mode, STRUCT -
ManLoLim
• ST: BYTE • 16#80
ModErr 1 = Module error STRUCT -
• ST: BYTE • 16#80
MS_Release Maintenance release: 1 = Release for STRUCT -
OS operator • Value: BOOL • 0
• ST: BYTE • 16#80
MsgAckn1 Alarm acknowledgement status 1 WORD 16#0000
(output STATUS of first ALARM_8P)
MsgAckn2 Alarm acknowledgement status 2 WORD 16#0000
(output STATUS of second ALARM_8P)
MsgErr1 Alarm error 1 (output ERROR of first BOOL 0
ALARM_8P)
MsgErr2 Alarm error 2 (output ERROR of second BOOL 0
ALARM_8P)
MsgStat1 Alarm status 1 (output ERROR of first WORD 16#0000
ALARM_8P)
MsgStat2 Alarm status 2 (output ERROR of WORD 16#0000
second ALARM_8P)
MV Manipulated variable STRUCT -
• ST: BYTE • 16#80

Control blocks

MV_FmTrkAct 1 = Tracking a manipulated variable in STRUCT -
the FM is active • Value: BOOL • 0
• ST: BYTE • 16#80
MV_HiAct 1 = Limit (high) of manipulated variable STRUCT -
• ST: BYTE • 16#80
MV_LoAct 1 = Limit (low) of manipulated variable STRUCT -
• ST: BYTE • 16#80
MV_SafeAct 1 = Safety manipulated variable of the STRUCT -
FM is active • Value: BOOL • 0
• ST: BYTE • 16#80
MV_SpliA Manipulated variable A of split-range STRUCT -
function • Value: REAL • 0.0
• ST: BYTE • 16#80
MV_SpliB Manipulated variable B of split-range STRUCT -
• ST: BYTE • 16#80
MV_UnitOut Unit of measure for manipulated INT 0
variable, for interconnecting to
MV_Unit input parameter of the
ConPerMon block
OosAct 1 = Block is "out of service" STRUCT -
• ST: BYTE • 16#80
Open Control output STRUCT -
1 = Open is active • Value: BOOL • 0
• ST: BYTE • 16#80
OS1PermOut Display of OS_Perm1 DWORD 16#FFFFFFFF
ParFM_Err 1 = Direct parameter-assignment error BOOL 0
of the FM or input Channel configured
incorrectly
PerAccErr 1 = I/O access error BOOL 0
PV_AH_Act 1 = PV alarm (high) active STRUCT -
• ST: BYTE • 16#80

Control blocks

PV_AL_Act 1 = PV alarm (low) active STRUCT -
• ST: BYTE • 16#80
PV_Out Output for process value STRUCT -
• ST: BYTE • 16#80
PV_TH_Act 1 = PV tolerance message (high) active STRUCT -
• ST: BYTE • 16#80
PV_TL_Act 1 = PV tolerance message (low) active STRUCT -
• ST: BYTE • 16#80
PV_ToleHi Limit (high) of 3-sigma band around the STRUCT -
setpoint is calculated when a • Value: REAL • 0.0
• ST: BYTE • 16#80
PV_ToleLo Limit (low) of 3-sigma band around the STRUCT -
• ST: BYTE • 16#80
PV_UnitOut Unit of measure for process value, for INT 0
interconnecting with PV_Unit input
parameter of the ConPerMon block
PV_WH_Act 1 = PV warning (high) active STRUCT -
• ST: BYTE • 16#80
PV_WL_Act 1 = PV warning (low) active STRUCT -
• ST: BYTE • 16#80
RbkClsOut Output for high limit stop signal of STRUCT -
position feedback • Value: BOOL • 0
• ST: BYTE • 16#80
RbkOpnOut Output for low limit stop signal of STRUCT -
• ST: BYTE • 16#80
RbkOut Output for position feedback STRUCT -
• ST: BYTE • 16#80
RbkWH_Act 1 = Warning (high) for position feedback STRUCT -
active • Value: BOOL • 0
• ST: BYTE • 16#80
RbkWL_Act 1 = Warning (low) for position feedback STRUCT -
• ST: BYTE • 16#80

Control blocks

RetValue Return value of WRREC/RDREC WORD 16#0
SP Setpoint used by controller STRUCT -
• ST: BYTE • 16#80
SP_DnRaAct 1 = Negative gradient limiting of STRUCT -
setpoint is active • Value: BOOL • 0.0
• ST: BYTE • 16#80
SP_ExHiAct 1 = Limit (high) for external setpoint has STRUCT -
been reached • Value: BOOL • 0
• ST: BYTE • 16#80
SP_ExLoAct 1 = Limit (low) for external setpoint has STRUCT -
been reached • Value: BOOL • 0
• ST: BYTE • 16#80
0 = Internal setpoint is active • Value: BOOL • 0
• ST: BYTE • 16#80
SP_ExtOut External setpoint, corresponds to input STRUCT -
parameter SP_Ext • Value: REAL • 0.0
• ST: BYTE • 16#80
SP_InHiOut Limit (high) for SP_Int corresponds to STRUCT -
input parameter SP_InHiLim • Value: REAL • 100.0
• ST: BYTE • 16#80
SP_InLoOut Limit (low) for SP_Int corresponds to STRUCT -
input parameter SP_InLoLim • Value: REAL • 0.0
• ST: BYTE • 16#80
SP_UpRaAct Positive gradient limiting of setpoint is STRUCT -
• ST: BYTE • 16#80
SplitRange 1 = Split-range function has been BOOL 0
activated
Stop Control output STRUCT -
1 =Stopped is active • Value: BOOL • 0
• ST: BYTE • 16#80

Control blocks

SumMsgAct 1 = Active process alarm STRUCT -
• ST: BYTE • 16#80
WithRbk Controller type: BOOL 0
0 = Step controller without position
feedback
1 = Step controller with position
feedback
See also

Control blocks
4.2.7 FmCont block diagram
FmCont block diagram
63B([+L$FW 63B([W/L 6SB([W,QW

/LPLW
63B([W 63B([/R$FW 63B,QW/L /LQN
63B([W$FW
63B([W2S 2SHUDWRU
63B([W2XW
63B,QW2S /RJLF 63B7UN39$1' 09B)RU2Q
63B/L2S 63B5DWH2Q 250DQ$FW2509B7UN2Q
63B([+L/LP
63B([/R/LP
63B5PS2Q
5HMHFW
5DPS
63B5PS7DUJHW 39
*UDGLHQW
63B,Q+L/LP
63B,Q/R/LP 63B5PS0RG7LPH
63B5PS7LPH
63B8S5D/LP 63B8S5D$FW
63B8S5D/LP
/LPLW 63B'Q5D/LP 63B'Q5D$FW
63B'Q5D/LP
$GY&R09
$GY&R$FW$1'
$GY&R0RG63
63B,Q+L/LP
63B,Q/R/LP $GY&R2Q

$GY&R(Q $GY&R0VWU2Q
$
5HMHFW 09B7UN2Q 1
63B,QW ' /LQN
09B)RU2Q $
LVOLPLWHG 2SHUDWRU
$GY&R0RG63 1
DQGWUDFNHG 2 $GY&R$FW
' /RJLF
$GY&R0RG63 $ 5
63B,Q+L/LP 63B,Q+L2XW 1
63B,Q/R/LP 63B,Q/R2XW 0DQ$FW $GY&R5G\
'
5HMHFW
0DQ
0DQ+L/LP 0DQ+L2XW
0DQ/R/LP 0DQ/R2XW 0DQ$FW
09B7UN2Q

09B7UN

0DQ$FW
2
09B7UN2Q 5
$GY&R$FW
$GY&R0RG63 $1'

Control blocks
39B287
6LP2Q 39B$+B$FW
39B:+B$FW
6LP39 $ODUP
39B7+B$FW
:ULWH39B287WR
39B7/B$FW
6LP39ZKHQ
DSSOLFDEOH6LP2Q 39B:/B$FW
39B$/B$FW
39B[+B/LP39B[/B/LP39B+\VW
39B[+B(Q39B[/B(Q
39B[+B0VJ(Q39B[+B0VJ(Q
39B[B'&39B[B'*
[ $:7
$ODUP
(5B$+B$FW
)0
2SHUDWLQJ 2XWSXW (5B$/B$FW
$XW0RG/L 0DQ$FW SDUDPHWHU SDUDPHWHUV
/LQN
0DQ0RG/L
2SHUDWRU 127 63B5( 63 63 (5B$+B/LP(5B$/B/LP(5B+\VW
$XW0RG2S $XW$FW
/RJLF /01B5( 39 (5B$+B(Q(5B$/B(Q
0DQ0RG2S (5B$+B0VJ(Q(5B$/B0VJ(Q
/01B5(21 (5
7UN2Q)0 /0175.21 ',69 ))ZG2XW (5B$B'&(5B$B'*
2SHQ/L 2SHQ 09B6DIH2Q 09
6$)(B21 /01
&ORVH/L 6[2SHQ 2SHQ
&ORVH 5EN2SHQHG /015+65(
6WRS/L 6WRS &ORVH
6[&ORVH 5EN&ORVHG /015/65( 4/0183 $
2SHQ2S 6WRS
/RJLF /0162321 4/01'1 1
&ORVH2S
6WRS2S /0183B23 '
/01'1B23 /01B$
0RG/L2S 09B6SOL% 09B6SOL$
6B5EN2Q3,'7XQ /0156B21 /01B%
)8=,'B21 5EN2XW
)X]2SW2Q
63B([W$FW 3DU)0B(UU
43$5B)
$ODUP 5EN:+B$FW
4&+B) &K)0B(UU
63B([+L/LP &RQWUROOHU 5EN
5EN:/B$FW
63B,Q+L/LP SDUDPHWHU 4,' )X]2SW$FW
4)8==< )X]&RQ
63B([/R/LP 3URS6HO 3B6(/
463/(39 )X]63B39B$FW 5EN:+B/LP
63B,Q/R/LP 3B)GE6HO 3)'%B6(/
'B(/B6(/ 5EN:/B/LP
'B,Q6HO
63B+/0 4/016$)( 09B6DI$FW 5EN+\VW
63B//0 4/0175. 09B7UN$FW 5EN:+B(Q
'HDG%DQG '($'%B: 4/01B5( 09B([W$FW 5EN:/B(Q

*DLQ(II *$,1 5EN:+B0VJ(Q
*DLQ
SK\V 7, 7, 4/015B+6 5EN2SQ2XW 5EN:/B0VJ(Q
7' 7' 4/015B/6 5EN&OV2XW
1HJ*DLQ 7''LII*DLQ 70B/$*
1RUP39 09B6DIH /01B6$)( 4/015B21 :LWK5EN
/01B+/0 4635 6SOLW5DQJH
$XW$FW )0 $
/01B//0
0RWRU7LPH 075B70 40$1B)& 0DQ$5:B$FW 6WHS&RQ 1
09B+L/LP '
3XOVH7LPH 38/6(B70
0DQ+L/LP
%UHDN7LPH %5($.B70

09B/R/LP
0DQ/R/LP 23B6HO 23B6(/

See also

Control blocks
4.2.8.1 FmCont views
Views of the FmCont block

The block FmCont provides the following views:
● Standard view of FM controllers (analog) (Page 131)
● Standard view of FM controllers (pulse controller) (Page 135)
● Standard view of FM controllers (step controller with position feedback) (Page 139)
● Standard view of FM controllers (step controller without position feedback) (Page 143)
● Limit value view of FM controllers (Page 157)
● Ramp view (Page 167)
● Parameter view of FM controllers (Page 153)
● Preview of FM controllers (Page 165)
● Block icons for PID and FM controller (Page 181)

Control blocks
4.3 FmTemp - Interface to temperature controller modules FM 355-2
4.3.1 Description of FmTemp

Family: Control
Area of application for FmTemp

● Fixed setpoint control
● Cascade control
● Ratio control
● Split-range control
How it works
Block FmTemp is used to interface the FM 355-2 temperature controller modules.
FmTemp can be used for the C (continuous controllers) and S (step and pulse controllers)
module types. It contains the algorithms of the setpoint ramp, the setpoint rise limitation, and
the limit monitoring of the process value, the control error, and the position feedback. Limit
monitoring is not used on the module.
The control function itself (e.g. PID algorithm) is processed on the module. You can use the
FmTemp block to monitor all relevant process values and to change all relevant controller
parameters.
Application examples of the FM 355-2 and detailed descriptions of the associated input
and output parameters can be found in the manual of the FM 355-2 temperature controller.
It is primarily used for controlling temperature processes, but can also control level and flow
processes which are not excessively fast, for example.
Module FM 355-2 features online optimization of the PID parameters. You can set the
corresponding parameters for performing online optimization in the CFC chart at block
FmTemp.

Control blocks
Configuration
also installed automatically in the startup OB (OB 100). Set the input LogAddr to the
module address from HW Config and the input Channel to the desired controller channel
(0..3).
When the CFC function "Generate module drivers" is used, the following occurs
automatically:
● The parameter CoordNo is set
● The parameter FM355_2 is set in accordance with the module type C/S
● The in/out parameter EnCoord is interconnected with the output EN_CO_x of the
FM_CO block of the basic library (x = number of the rack)
● The output EnCoNum is interconnected with the input ENCOx_yy of the FM_CO block
(x = number of the rack, yy = coordination number).
For the control loop monitoring to work as planned in the trend view of the controller
faceplates, the
S7_xarchive:='Value, shortterm;'
attributes in the process tag types for control loops at the controller function block must be
set for the following tags:
● Input parameters:
– CPI_In
● Output parameters
– MV
– MV_HiAct
– MV_LoAct
– AutAct
– SP
– PV_Out
– PV_ToleHi
– PV_ToleLo
Use the Setting the startup response (Page 187) feature to define the startup characteristics
of this block.

Control blocks

For a description of the individual parameters see the section FmTemp I/Os (Page 361).

0 Occupied
1 BatchEn
2 SimOn
3 OosAct.Value
4 OosLi.Value
5 AutAct.Value
6 Not allocated
7 ManAct.Value
8 SP_ExtAct.Value
9 MV_SafeOn.Value
10 MV_TrkOn.Value
11 MV.Value > ManLoLim for continuous or pulse controller
NOT FbkClosed.Value for step controller with/without position feedback
12 Open.Value
13 Close.Value
14 Stop.Value
15 FbkOpened.Value
16 FbkClosed.Value
19 AdvCoAct
20 1 = Input parameter Rbk is not interconnected (RbkOut.ST = 16#FF)
21 NegGain
28 1 = Analog controller (FM355_2 = 1 )
29 1 = Pulse controller (FM355_2 = 0 ANDStepCon = 0)
30 1 = Step controller with position feedback
(FM355_2 = 0 AND StepCon = 1 AND WithRbk = 1 )
31 1= Step controller without position feedback
(FM355_2 = 0 AND StepCon = 1 AND WithRbk = 0 )

Control blocks

0 MsgLock
1 PV_AH_Act.Value
2 PV_WH_Act.Value
3 PV_TH_Act.Value
4 PV_TL_Act.Value
5 PV_WL_Act.Value
6 PV_AL_Act.Value
7 PV_AH_En
8 PV_WH_En
9 PV_TH_En
10 PV_TL_En
11 PV_WL_En
12 PV_AL_En
13 PV_AH_MsgEn
14 PV_WH_MsgEn
15 PV_TH_MsgEn
16 PV_TL_MsgEn
17 PV_WL_MsgEn
18 PV_AL_MsgEn
19 ER_AH_Act.Value
20 ER_AL_Act.Value
21 ER_AH_En
22 ER_AL_En
23 ER_AH_MsgEn
24 ER_AL_MsgEn
25 RbkWH_Act.Value
26 RbkWL_Act.Value
27 RbkWH_En
28 RbkWL_En
29 RbkWH_MsgEn
30 RbkWL_MsgEn
31 MS_RelOp
See also
FmTemp functions (Page 346)
FmTemp messaging (Page 358)
FmTemp modes (Page 345)
FmTemp error handling (Page 356)
FmTemp block diagram (Page 376)

Control blocks
4.3.2 FmTemp modes
FmTemp operating modes

The next section provides additional block-specific information relating to the general
descriptions.
Automatic mode
You can find general information on "Automatic mode", switching modes and bumpless
Manual mode
You can find general information on "Manual mode", switching modes and bumpless
Program mode for controllers

General information on "Program mode for controllers" is available in the section Program
mode for closed-loop controllers (Page 34).
Out of service
(Page 27) section.
See also
Description of FmTemp (Page 341)
FmTemp I/Os (Page 361)

Control blocks
4.3.3 FmTemp functions
Functions of FmTemp
Module types
FmTemp can be used for the C (continuous controllers) and S (step controllers with and
without position feedback and pulse controllers) module types. You can use the following
parameters to identify which module type and controller type has been set:
FM355 StepCon WithRbk Module type, controller type

1 or C - - FM 355-2 C: Continuous
controller
0 or S 1 1 FM 355-2 S: Step controller
with position feedback
0 or S 1 0 FM 355-2 S: Step controller
without position feedback
0 or S 0 - FM 355-2 S: Pulse controller

Control blocks
Generating manipulated variables for continuous controllers, step controllers with position feedback,
or pulse controllers
The manipulated variable MV and the actuating signals Open, Close, and Stop are
generated as follows:
MV_SafeOn MV_FMTrkOn ManAct MV_TrkOn AdvCoAct MV = Limitation State Open,

AND NOT of the mani- Close, Stop
AdvCoMod pulated
SP variable
1 - - - - MV_Safe MV_HiLim Tracking to Cont.

MV_LoLim
safety value controller:O
0 1 - - - Prepared MV_HiLim Tracking to pen,
MV_LoLim Close,
FM analog an FM
input analog Stop =
input False
0 0 1 - - Man ManHiLim Manual Step
ManLoLim controller
mode, set
by the with
operator position
feedback:
0 0 0 1 - MV_Trk MV_HiLim Tracking to
MV_LoLim
block input Depending
MV_Trk on Rbk and
0 0 0 0 1 AdvCoMV MV_HiLim Higher-level MV, the
MV_LoLim output
program
mode signals
Open,
0 0 0 0 0 P_Part + MV_HiLim Automatic
MV_LoLim Close and
I_Part + mode (PID Stop are
D_Part + algorithm) generated
FFwd
using the
algorithm of
a
positioner.
Pulse
controller:
Depending
on MV, the
output
signals
Open and
Close are
generated
using the
algorithm of
a pulse
controller
(Stop = 0).

Control blocks
Generating manipulated signals for step controllers without position feedback (WithRbk = 0)
The manipulated variable signals Open, Close and Stop can be generated as follows:
ManAct Open, Close, Stop State ManAct

1 The output signals are Manual mode, set by the 1
generated using input operator
signals OpenOp/Li,
CloseOp/Li or StopOp/Li.
0 The output signals are Automatic mode (PID 0
generated using PID output algorithm)
parameters P_Part,
I_Part, D_Part and FFwd
Tracking and limiting a manipulated variable (cont. controller, step controller with position feedback
and pulse controller)
The block provides the standard function Tracking and limiting a manipulated value
(Page 111).
Safe position
The controller groups have their own mechanism for connecting a safety value (see manual
for Temperature Controller FM 355-2).
"Actuator active" information

For continuous and pulse controllers: If the manipulated variable MV is greater than the
minimum manual limit ManLoLim, this is recognized as actuator active.
For step controllers: If the parameter FbkClosed = 0, this is known as "Actuator active".
This status can be used to display a custom icon in the process image, for example, and is
saved in the status word (see Status word section in Description of FmTemp (Page 341)).
Limit monitoring of position feedback (cont. controller, step controller with position feedback and pulse
controller)
The block provides the standard function Limit monitoring of the feedback (Page 76).
External/internal setpoint specification

The block provides the standard function Setpoint input - internal and external (Page 96).

The block provides the standard function Setpoint limiting for external setpoints (Page 110).

Control blocks
Limitation of rate of change of setpoint

The block provides the standard function Ramp limiting of the setpoint (Page 108).
Using setpoint ramp

The block provides the standard function Using a setpoint ramp (Page 98).

The block provides the standard function Setpoint tracking the process variable in manual
mode (Page 110).
Simulating signals
The block provides the standard function Simulating signals (Page 93).
You can simulate the following values:
● Process value (SimPV)
● Position feedback (SimRbk)
Note
The simulated process value SimPV only affects alarm processing and not the PID
algorithm in the controller module.

The block provides the standard function Limit monitoring of the process value (Page 70).

The block provides the standard function Control error generation and deadband (Page 109).

The block provides the standard function Monitoring the error signal limits (Page 77).
Inverting control direction

The block provides the standard function Inverting the control sense (Page 108).

Control blocks
Physical standardization of setpoint, manipulated variable and process value

Controller gain Gain is entered either using a physical variable or as standardized value.
● Gain as a physical variable:
The standardized variables retain their default values:
– NormPV.High = 100 and NormPV.Low = 0
– NormMV.High = 100 and NormMV.Low = 0
For step controllers with/without position feedback and pulse controllers, the values of
NormMV.High and NormMV.Low are not taken into account. The algorithm uses default
values 0 and 100 for internal calculations.
The effective gain is: GainEff = Gain
● Entering a standardized Gain (dimensionless):
Change the standardized variables to the actual range of the process values and
manipulated variables.
– Internal and external setpoints; the process value and corresponding parameters are
entered according to the physical measuring range of the process value.
Continuous controller, pulse controller:
and the corresponding parameters are set according to the physical measuring range
of the manipulated variable.
Step controller with position feedback:
and the corresponding parameters are entered as a percentage between 0 ... 100.
– No physical measuring range available.
The effective gain is:
– Step controller with/without position feedback:
GainEff = 100,0 / (NormPV.High - NormPV.Low) · Gain
– Continuous controller, pulse controller:
GainEff = (NormMV.High - NormMV.Low)/(NormPV.High - NormPV.Low)
· Gain


Control blocks
PID algorithm
The manipulated variable is generated in automatic mode according to the following
algorithm:
MV = Gain · (1 + 1/(TI · s) + TD/( 1 + TD/DiffGain · s) · ER
Where: s = Complex number
The following step response occurs:
09
09B+L/LP
*DLQ 7'
7LPH/DJ6DPSOH7LPH
*DLQ
(5 W *DLQ
*DLQ
W
7,
09B/R/LP
,QSXWMXPS(5 W ` LIW
LIW!
Note
This formula describes a standard application where P, I and D action is activated and the P
and D actions are not in the feedback circuit (PropSel = 1, TI ≠ 0 D_InSel = 0 and
PropFacSP = 1).
The D action delay is derived from TD/DiffGain.

● The P action can be shut down by PropSel = 0.
● The I action can be shut down by TI = 0.
● The D action can be shut down by TD = 0.

The PID controller algorithm of FM355 features structure segmentation. It is activated via the
PropFacSel and D_InSel parameters. The precise functionality is described in the FM355
manual.

Control blocks
Online optimization of the PID controller parameters

● Optimization sequence
The optimization sequence is as follows:
– Create a stationary state
– Set PID_On = 1 (if PID parameters are required)
– Set TunD_MV / TunC_MVLMN
– Set TunOn = 1 (phase 1, ready for optimization)
– Start the optimization using a step change in the setpoint or by setting TunStart
If you have not made any configuration errors, the controller optimization is now in phase
2 and StatusH is 0.
– When the point of inflection has been reached (PHASE ≥ 3), evaluate the diagnostics
display at the StatusH parameter. Phase 0 is reached in a few cycles for process
type I and the optimization is completed in full. For process types II and III, the
optimization goes to phase 7 (checking the process type). If StatusH > 20000, a
valuation error has occurred or the point of inflection has not been reached. In this
case, repeat the procedure.
● Result
– Once optimization is completed, the parameters PropFacSP, GAIN, TI, TD,
DiffGain and ConZone are updated (for both the module and at FmTemp).
Furthermore, the PI or PID parameter sets are saved on the FM 355-2.
– The precise procedure is described in the FM 355-2 manual of the temperature
controller module.
● Permanent backup of optimized controller parameters
– Save, compile and download the hardware configuration; the optimized controller
parameters are now in the system data block (SDB).
– Transfer the modified parameters to the offline data management of the CFC via Chart
> Readback....
Anti-windup
The PID control algorithm of FM355 has an anti-windup function. The I action is frozen or
tracked after the manipulated variable has reached its limits (MV_HiLim or MV_LoLim).
Activating and limiting disturbance variables

The block provides a function for activating the disturbance variable. The precise
functionality is described in the FM355-2 manual.
Control zone
The block provides the standard function Using control zones (Page 109).

Control blocks

(Page 88).
● ER.ST
● FFwdOut.ST
● Rbk.ST
● MV.ST

Bit Function

OS_Perm:
Bit Function
0 1 = Operator can switch into automatic mode AutModOp
1 1 = Operator can switch into manual mode ManModOp
2 1 = Operator can switch into "out of service" mode OosOp
3 1 = Operator can switch into program mode AdvCoEn
4 1 = Operator can switch the setpoint to external SP_ExtOp
5 1 = Operator can switch the setpoint to internal SP_IntOp
6 1 = Operator can change the internal setpoint SP_Int
7 Continuous controllers, pulse controllers or step controllers with position feedback:
1 = Operator can change the manual parameter Man
1 = Operator can change the manual operation signals OpenOp, StopOp, CloseOp
8 1 = Operator can change maximum usage limit of the setpoint SP_InHiLim
9 1 = Operator can change minimum usage limit of the setpoint SP_InLoLim
10 1 = Operator can change maximum usage limit of the manipulated variable ManHiLim
11 1 = Operator can change minimum usage limit of the manipulated variable ManLiLim

Control blocks
Bit Function
12 1 = Operator can use the setpoint's gradient limitation function SP_RateOn
13 1 = Operator can change the setpoint's high limit for the ramp SP_UpRaLim
14 1 = Operator can change the setpoint's low limit for the ramp SP_DnRaLim
15 1 = Operator can change between the time value or the value for the ramp
SP_RmpModTime
16 1 = Operator can change the ramp time SP_RmpTime
17 1 = Operator can change the target setpoint SP_RmpTarget for the setpoint ramp
18 1 = Operator can activate the setpoint ramp function SP_RmpOn
19 Not allocated
20 1 = Operator can activate the track setpoint in manual mode function SP_TrkPV
21 1 = Operator can activate the bumpless changeover from external to internal function
SP_TrkExt
22 1 = Operator can change the gain parameter Gain
23 1 = Operator can change the integral action time parameter TI
24 1 = Operator can change the derivative action time parameter TD
25 1 = Operator can change the derivative gain parameter DiffGain
26 1 = Operator can change the dead band parameter DeadBand
27 1 = Operator can change the control zone parameter ConZone
28 1 = Operator can change the integral action time parameter MotorTime
29 1 = Operator can change the integral action time parameter PulseTime
30 1 = Operator can change the integral action time parameter BreakTime
31 Not allocated
Bit Function
0 1 = Operator can change the limit (process value) for the high alarm PV_AH_Lim
1 1 = Operator can change the limit (process value) for the high warning PV_WH_Lim
2 1 = Operator can change the limit (process value) for the high tolerance PV_TH_Lim
3 1 = Operator can change the hysteresis (process value) PV_Hyst
4 1 = Operator can change the limit (process value) for the low tolerance PV_TL_Lim
5 1 = Operator can change the limit (process value) for the low warning PV_WL_Lim
6 1 = Operator can change the limit (process value) for the low alarm PV_AL_Lim
7 1 = Operator can change the limit (control error) for the high alarm ER_AH_Lim
8 1 = Operator can change the hysteresis (control error) ER_Hyst
9 1 = Operator can change the limit (control error) for the low alarm ER_AL_Lim
10 1 = Operator can change the limit (position feedback) for the high warning RbkWH_Lim
11 1 = Operator can change the hysteresis (position feedback) RbkHyst
12 1 = Operator can change the limit (position feedback) for the low warning RbkWL_Lim
16 1 = Operator can activate the simulation function SimOn
17 1 = Operator can activate the maintenance release function MS_RelOp

Control blocks
Maintenance release
The block provides the standard function Maintenance release (Page 47).

This block provides the standard function Display and operator input area for process values


See also
Safety value of the manipulated variable effective at startup (Page 196)
Out of service (Page 27)
Operator permissions (Page 45)

Control blocks
4.3.4 FmTemp error handling
FmTemp troubleshooting
● Error numbers

The ErrorNum output parameter can be used to output various error numbers. An overview
of all error numbers is available in the section "Functions of blocks > Error handling
(Page 117)".
Error numbers output by this block:

30 The value of PV can no longer be displayed in the REAL number field.
31 The value of SP_Ext can no longer be displayed in the REAL number field.
33 The value of MV_Trk can no longer be displayed in the REAL number field.
35 The value of Rbk can no longer be displayed in the REAL number field.
36 The value of MV can no longer be displayed in the REAL number field.
50 The controller cannot be switched in program mode, because program mode with
setpoint specification (AdvCoModSP=false) is not possible with step controllers
without position feedback (WithRbk=false).
60 |Tl| < SampleTime/2
61 |TD| < SampleTime
62 DiffGain < 1 or DiffGain > 10
63 TD/DiffGain < SampleTime/2
64 PropFacSP < 0 or PropFacSP > 1
66 NormPV_High = NormPV_Low
67 MotorTime < SampleTime
68 PulseTime < SampleTime
69 BreakTime < SampleTime
70 Channel < 0 or Channel > 3
71 (D_InSel < 0 or D_InSel > 4)
and D_InSel ≠ 17

Control blocks
See also
Setting switch or button mode (Page 195)

Control blocks
4.3.5 FmTemp messaging
Messaging
● Control system fault
Control system fault

The following control system error messages can be output:

instance identifier
MsgEvId2 SIG 6 AS process control message - fault $$BlockComment$$
External error has occurred
Explanation:
You can interconnect an external fault (signal) to input parameter CSF. If this signal changes
to CSF = 1, a control system fault is triggered (MsgEvId2, SIG 6).
Process messages

instance
MsgEvId1 SIG 1 Alarm - high $$BlockComment$$
PV - high alarm limit violated
PV - high warning limit violated
SIG 3 Tolerance - high $$BlockComment$$
PV - high tolerance limit violated
SIG 4 Tolerance - low $$BlockComment$$
PV - low tolerance limit violated
PV - low warning limit violated
PV - low alarm limit violated
SIG 7 Alarm - high $$BlockComment$$
ER - high alarm limit violated
ER - low alarm limit violated

Control blocks

instance
MsgEvId2 SIG 7 Warning - high $$BlockComment$$
Rbk - high warning limit violated
Rbk - low warning limit violated
Explanation:
You can use up to four instance-specific messages with this block.

instance
MsgEvId2 SIG 1 AS process control message - $$BlockComment$$
Status 16#@5%x@
Status 16#@6%x@
Status 16#@7%x@
Status 16#@8%x@
Explanation:

Control blocks

1 BatchName
2 StepNo
3 BatchID
4 Process value PV_Out
5 Control error ER
6 ExtVa106
7 ExtVa107
8 Not allocated
9 Not allocated
10 Not allocated
you can use them. Additional information is available in the "Process Control System PCS 7
- Engineering System" manual.

1 BatchName
2 StepNo
3 BatchID
4 Position feedback Rbk
9 ExtVa209
10 ExtVa210
The associated values 9 and 10 are assigned to the parameters ExtVa209 ... ExtVa210
and you can use them. Additional information is available in the "Process Control System
See also

Control blocks
4.3.6 FmTemp I/Os
FmTemp I/Os
Input parameters

AccMode 1 = Transfer of operating BOOL 1
parameters SubN1_ID,
SubN2_ID, RackNo,
SlotNo and Channel to
internal processing
AdvCoEn 1 = Enable program mode STRUCT -
via interconnection • Value: BOOL • 0
• ST: BYTE • 16#80
AdvCoModSP Type of program mode: BOOL 1
1 = Setpoint specification
0 = Manipulated variable
specification
AdvCoMstrOn Activate (0-1) or deactivate STRUCT -
(1-0) program mode via edge • Value: BOOL • 0
transition
• ST: BYTE • 16#80
AdvCoMV Specified value from the REAL 0.0
external program
AdvCoOn 1 = Enable program mode BOOL 0
via faceplate
AutModLi 1 = Automatic mode via STRUCT -
(controlled via ModLiOp = 1)
• ST: BYTE • 16#80
AutModOp 1 = Automatic mode by BOOL 0
operator (controlled via
ModLiOp = 0)
BatchEn 1 = Enable allocation for BOOL 0
batch control
BreakTime Minimum break time [s] REAL 1.0
Channel Controller channel number INT 0
(0..3)
CloseLi 1 = Close via interconnection STRUCT -
or CFC • Value: BOOL • 0
• ST: BYTE • 16#80
CloseOp 1 = Close via operator BOOL 0
ConZone Control zone REAL 0.0

Control blocks

CoordNo Coordination number INT 0
CPI_In Input for control performance STRUCT -
index, which is calculated by • Value: REAL • 0.0
the assigned ConPerMon
• ST: BYTE • 16#78
block
CSF 1 = External error (control STRUCT -
system error) • Value: BOOL • 0
• ST: BYTE • 16#80
D_InSel Input for differentiator: INT 0
0 = Control error
1..4 = Channel 0..3
17 = Actual value to
feedback
DeadBand Width of dead band REAL 0.0
DiffGain Gain of differentiator [1...10] STRUCT -
DiffGain = TD/(delay time • Value: REAL • 5.0
of D action)
• ST: BYTE • 16#80
EN 1 = Called block will be BOOL 1
processed
ER_A_DC Delay for incoming alarms REAL 0.0
during control error
monitoring
ER_A_DG Delay for outgoing alarms REAL 0.0
during control error
monitoring
ER_AH_En 1 = Activate alarm (high) for BOOL 1
ER_AH_Lim Alarm limit (high) for control REAL 100.0
error monitoring
ER_AH_MsgEn 1 = Activate messages for BOOL 1
alarm (high) for control error
monitoring
ER_AL_En 1 = Activate alarm (low) for BOOL 1
ER_AL_Lim Alarm limit (low) for control REAL -100.0
error monitoring
ER_AL_MsgEn 1 = Activate messages for BOOL 1
alarm (low) for control error
monitoring
ER_Hyst Alarm hysteresis for control REAL 1.0
error
• ST: BYTE • 16#80

Control blocks

• ST: BYTE • 16#80
• ST: BYTE • 16#80
• ST: BYTE • 16#80
messages (MsgEvID1)
messages (MsgEvID1)
messages (MsgEvID2)
messages (MsgEvID2)
FbkClosed Low limit stop signal of STRUCT -
• ST: BYTE • 16#80
FbkOpened High limit stop signal of STRUCT -
• ST: BYTE • 16#80
Feature I/O for additional functions STRUCT -
(Page 346) • Bit 0: BOOL • 0
• ... • 0
• Bit 31: BOOL • 0
FM355_2 Module type: BOOL 0
0: FM 355-2 S; 1:
FM 355-2 C
Gain Proportional gain STRUCT -
Gain.ST = 16#FF: Operable • Value: REAL • 1.0
in faceplate • ST: BYTE • 16#FF
LoadPID Load optimized PI/PID BOOL 0
parameters
LogAddr Logical address FM 355 INT 0
Man Manual specification for the REAL 0.0
manipulated variable
ManHiLim Limit (high) for manual REAL 100.0
parameter Man
ManLoLim Limit (low) for manual REAL 0.0
parameter Man

Control blocks

ManModLi 1 = Manual mode via STRUCT -
(controlled via ModLiOp = 1)
• ST: BYTE • 16#80
ManModOp 1 = Manual mode via OS BOOL 1
operator (controlled via
ModLiOp = 0)
Mode Operating mode DWORD 16#0
ModLiOp Operating mode switchover STRUCT -
between: • Value: BOOL • 0
1 = Interconnection or SFC
MotorTime Motor manipulating time [s] REAL 30.0
MS_RelOp 1 = Maintenance release by BOOL 0
OS operator
MsgEvId1 Message number (assigned DWORD 16#FFFFFFFF
automatically)
MsgEvId2 Message number (assigned DWORD 16#FFFFFFFF
automatically)
MsgLock 1 = Suppress process STRUCT -
messages • Value: BOOL • 0
• ST: BYTE • 16#80
MV_FmTrkOn 1 = Manipulated variable STRUCT -
tracking in the FM • Value: BOOL • 0
• ST: BYTE • 16#80
MV_HiLim Limit (high) for manipulated STRUCT -
variable MV • Value: REAL • 100.0
• ST: BYTE • 16#80
MV_LoLim Limit (low) for manipulated STRUCT -
variable MV • Value: REAL • 0.0
• ST: BYTE • 16#80
MV_OpScale OS display range for STRUCT -
manipulated variable MV • High: REAL • 100.0
MV_Safe Safety manipulated variable REAL 0.0
MV_SafeOn 1 = Output safety STRUCT -
manipulated variable • Value: BOOL • 0
MV_Safe at output MV
• ST: BYTE • 16#80
MV_Trk Tracking value for the STRUCT -
manipulated variable MV • Value: REAL • 0.0
• ST: BYTE • 16#80
MV_TrkOn 1 = Tracking of manipulated STRUCT -
variable MV • Value: BOOL • 0
• ST: BYTE • 16#80

Control blocks

MV_Unit Unit of measure for INT 1342; %
manipulated variable
NegGain 0 = Positive controller gain: STRUCT -
ER = Gain (SP - PV) • Value: BOOL • 0
1 = Negative controller gain: • ST: BYTE • 16#80
ER = Gain (PV - SP)
NormMV Manipulated variable range STRUCT -
(MV) for standardizing the • High: REAL • 100.0
proportional gain (GAIN)
NormPV Process value range (PV) for STRUCT -
standardizing the • High: REAL • 100.0
proportional gain (GAIN)
Occupied Occupied by batch control BOOL 0
OosLi Edge transition (0-1) = Out of STRUCT -
service, via interconnection • Value: BOOL • 0
or SFC
• ST: BYTE • 16#80
OosOp 1 = Out of service, via OS BOOL 0
operator
OpenLi 1 = Open via interconnection STRUCT -
• ST: BYTE • 16#80
OpenOp 1 = Open via operator BOOL 0
OS_Perm I/O for operator control STRUCT -
• ... • 1
• Bit 31: BOOL • 1
OS1Perm I/O for operator control STRUCT -
• ... • 1
• Bit 31: BOOL • 1
PID_On 1 = PID mode on BOOL 0
PropFacSP Applying the P action to the REAL 1.0
feedback [0..1]. 0 = P action
fully in feedback
PropSel 1 = Activate P action BOOL 1
PulseTime Minimum pulse duration [s] REAL 1.0
PV_A_DC Delay time for incoming PV REAL 0.0
alarms [s]
PV_A_DG Delay time for outgoing PV REAL 0.0
alarms [s]
PV_AH_En 1 = Enable PV alarm limit BOOL 1
(high)
PV_AH_Lim PV alarm limit (high) REAL 95.0

Control blocks

PV_AH_MsgEn 1 = Enable message for PV BOOL 1
alarm (high)
PV_AL_En 1 = Enable PV alarm limit BOOL 1
(low)
PV_AL_Lim PV alarm limit (low) REAL 5.0
PV_AL_MsgEn 1 = Enable message for PV BOOL 1
alarm (low)
PV_Hyst Hysteresis for PV alarm, REAL 1.0
warning and tolerance limits
PV_OpScale Limit for scale in PV bar STRUCT -
graph of faceplate • High: REAL • 100.0
PV_T_DC Delay time for incoming PV REAL 0.0
tolerance messages [s]
PV_T_DG Delay time for outgoing PV REAL 0.0
tolerance messages [s]
PV_TH_En 1 = Enable PV tolerance limit BOOL 0
(high)
PV_TH_Lim PV tolerance message limit REAL 85.0
(high)
PV_TH_MsgEn 1 = Enable message for PV BOOL 1
tolerance message (high)
PV_TL_En 1 = Enable PV tolerance limit BOOL 0
(low)
PV_TL_Lim PV tolerance message limit REAL 15.0
(low)
PV_TL_MsgEn 1 = Enable message for PV BOOL 1
tolerance message (low)
PV_Unit Unit of measure for process INT 1001; OC
value
PV_W_DC Delay time for incoming PV REAL 0.0
warnings [s]
PV_W_DG Delay time for outgoing PV REAL 0.0
warnings [s]
PV_WH_En 1 = Enable PV warning limit BOOL 1
(high)
PV_WH_Lim PV warning limit (high) REAL 90.0
PV_WH_MsgEn 1 = Enable message for PV BOOL 1
warning (high)
PV_WL_En 1 = Enable PV warning limit BOOL 1
(low)
PV_WL_Lim PV warning limit (low) REAL 10.0
PV_WL_MsgEn 1 = Enable message for PV BOOL 1
warning (low)
RackNo Rack number BYTE 16#FF
RatioFac Ratio factor REAL 0.0

Control blocks

Rbk Position feedback for display STRUCT -
on OS • Value: REAL • 0.0
RbkHyst Alarm hysteresis for position REAL 1.0
feedback
RbkWH_En 1 = Enable warning (high) for BOOL 1
position feedback
RbkWH_Lim Limit for position feedback of REAL 100.0
warning (high)
RbkWH_MsgEn 1 = Enable messages for BOOL 1
warning (high) for position
feedback
RbkWL_En 1 = Enable warning (low) for BOOL 1
position feedback
RbkWL_Lim Limit for position feedback of REAL 0.0
warning (low)
RbkWL_MsgEn 1 = Enable messages for BOOL 1
warning (low) for position
feedback
RefStdDevIn Reference value of PV STRUCT -
standard deviation (sigma) in • Value: REAL • 0.0
defined "good" state of
• ST: BYTE • 16#78
control loop
RunUpCyc Number of cycles in startup; INT 3
during these cycles
automatically)
SavePar 1 = Save PID controller BOOL 0
parameters
standard view
preview
SimOn 1 = Simulation on BOOL 0
SimPV Process value used for REAL 0.0
SimOn = 1
SimRbk Position feedback used for REAL 0.0
SimOn = 1
SlotNo Slot number BYTE 16#FF
SP_DnRaLim Limit (low) for ramp of REAL 100.0

Control blocks

SP_ExHiLim Limit (high) for external STRUCT -
setpoint • Value: REAL • 100.0
• ST: BYTE • 16#80
SP_ExLoLim Limit (low) for external STRUCT -
setpoint • Value: REAL • 0.0
• ST: BYTE • 16#80
SP_Ext External setpoint of - (to STRUCT -
interconnection) • Value: REAL • 0.0
• ST: BYTE • 16#80
SP_ExtLi 1 = Select external setpoint STRUCT -
• ST: BYTE • 16#80
SP_ExtOp 1 = Select external setpoint BOOL 0
(via operator)
SP_InHiLim Limit (high) of internal REAL 100.0
setpoint
SP_InLoLim Limit (low) of internal REAL 0.0
setpoint
SP_Int Internal setpoint for REAL 0.0
operation
SP_IntLi 1 = Select internal setpoint STRUCT -
• ST: BYTE • 16#80
SP_IntOp 1 = Select internal setpoint BOOL 0
(via operator)
SP_LiOp Select setpoint source STRUCT -
(internal/external): • Value: BOOL • 0.0
1 = Via interconnection • ST: BYTE • 16#80
0 = Via operator
SP_RateOn 1 = Activate limitation of BOOL 0
setpoint gradients
SP_RmpModTime 1 = Use time (SP_RmpTime) BOOL 0
for setpoint ramp,
0 = Use gradient
SP_RmpOn 1 = Activate setpoint ramp to BOOL 0
target setpoint
SP_RmpTarget
SP_RmpTarget Target setpoint for setpoint REAL 0.0
ramp
SP_RmpTime Time for setpoint ramp [s] REAL 0.0
from current SP up to
SP_RmpTarget
SP_TrkExt 1 = Bumpless switchover BOOL 1
from external to internal
setpoint active

Control blocks

SP_TrkPV 1 = Setpoint follows PV in BOOL 0
manual mode and with
tracking
SP_UpRaLim Gradient limit (high) for REAL 100.0
StopLi 1 = Stop via interconnection STRUCT -
• ST: BYTE • 16#80
StopOp 1 = Stop via operator BOOL 0
SubN1_ID ID of the primary DP master BYTE 16#FF
system
SubN2_ID ID of the redundant DP BYTE 16#FF
master system
TD Derivative action time [s] STRUCT -
TD.ST = 16#FF: Operable in • Value: REAL • 0.0
faceplate • ST: BYTE • 16#FF
TI Integral action time [s] STRUCT -
TI.ST = 16#FF: Operable in • Value: REAL • 100.0
faceplate • ST: BYTE • 16#FF
TunC_MV Delta manipulated variable REAL -20.0
for cooling optimization
TunC_Start Start cooling optimization BOOL 0
TunD_MV Delta manipulated variable REAL 20.0
for process excitation
TunOn Enable controller BOOL 0
optimization
TunStart Start controller optimization BOOL 0
UndoPar Undo controller parameter BOOL 0
changes
UserStatus Freely assignable bits for BYTE 16#00
use in faceplate

Control blocks
In/out parameters

EnCoord Current coordination number STRUCT -
• CO_ACT : INT • 0
Output parameters

AdvCoAct 1 = Program mode is active STRUCT -
• ST: BYTE • 16#80
AdvCoRdy 1 = Program mode available STRUCT -
• ST: BYTE • 16#80
AutAct 1 = Automatic mode is active STRUCT -
0 = Manual mode is active • Value: BOOL • 0
• ST: BYTE • 16#80
ChFM_Err 1 = Channel error on the module BOOL 0
Close Control output: STRUCT -
1 = Closed is active • Value: BOOL • 0
• ST: BYTE • 16#80
EnCoNum Coordination number BYTE 16#0
errors
ER Control error STRUCT -
• ST: BYTE • 16#80
ER_AH_Act 1 = Alarm limit (high) for control error STRUCT -
• ST: BYTE • 16#80
ER_AL_Act 1 = Alarm limit (low) for control error STRUCT -
• ST: BYTE • 16#80
ErrorNum Output of present error number, for error INT -1
numbers that can be output by this
block, see FmTemp error handling
(Page 356)
FFwdOut Disturbance variable generated in the STRUCT -
FM • Value: REAL • 0.0
• ST: BYTE • 16#80

Control blocks

FbkClsOut 1 = Low limit stop of the position STRUCT -
• ST: BYTE • 16#80
FbkOpnOut 1 = High limit stop of the position STRUCT -
• ST: BYTE • 16#80
GainEff Effective proportional gain, depends on REAL 1.0
Gain and NormPV
ManAct 1 = Manual mode active STRUCT -
• ST: BYTE • 16#80
ManARW_Act 1 = Tracking mode or anti-reset windup STRUCT -
by secondary controller • Value: BOOL • 0
• ST: BYTE • 16#80
ManHiOut Limit (high) for manual mode, STRUCT -
ManHiLim
• ST: BYTE • 16#80
ManLoOut Limit (low) for manual mode, STRUCT -
ManLoLim
• ST: BYTE • 16#80
ModErr 1 = Module error STRUCT -
• ST: BYTE • 16#80
MS_Release Maintenance release: 1 = Release for STRUCT -
OS operator • Value: BOOL • 0
• ST: BYTE • 16#80
MsgAckn1 Alarm acknowledgement status 1 (output WORD 16#0000
STATUS of first ALARM_8P)
MsgAckn2 Alarm acknowledgement status 2 (output WORD 16#0000
STATUS of second ALARM_8P)
MsgErr1 Alarm error 1 (output ERROR of first BOOL 0
ALARM_8P)
MsgErr2 Alarm error 2 (output ERROR of second BOOL 0
ALARM_8P)
MsgStat1 Alarm status 1 (output ERROR of first WORD 16#0000
ALARM_8P)
MsgStat2 Alarm status 2 (output ERROR of WORD 16#0000
second ALARM_8P)
MV Manipulated variable STRUCT -
• ST: BYTE • 16#80

Control blocks

MV_FmTrkAct 1 = Tracking a manipulated variable in STRUCT -
the FM is active • Value: BOOL • 0
• ST: BYTE • 16#80
MV_HiAct 1 = Limit (high) of manipulated variable STRUCT -
• ST: BYTE • 16#80
MV_LoAct 1 = Limit (low) of manipulated variable STRUCT -
• ST: BYTE • 16#80
MV_SafeAct 1 = Safety manipulated variable of the STRUCT -
FM is active • Value: BOOL • 0
• ST: BYTE • 16#80
MV_SpliA Manipulated variable A of split-range STRUCT -
• ST: BYTE • 16#80
MV_SpliB Manipulated variable B of split-range STRUCT -
• ST: BYTE • 16#80
MV_UnitOut Unit of measure for manipulated INT 0
variable, for interconnecting to MV_Unit
input parameter of the ConPerMon block
OosAct 1 = Block is "out of service" STRUCT -
• ST: BYTE • 16#80
Open Control output STRUCT -
1 = Open is active • Value: BOOL • 0
• ST: BYTE • 16#80
OS1PermOut Display of OS_Perm1 DWORD 16#FFFFFFFF
ParFM_Err 1 = Direct parameter-assignment error of BOOL 0
the FM or input Channel configured
incorrectly
PerAccErr 1 = I/O access error BOOL 0
Phase Phase of auto-tuning [0..7] INT 0
PV_AH_Act 1 = PV alarm (high) active STRUCT -
• Value: BOOL 0
• ST: BYTE 16#80

Control blocks

PV_AL_Act 1 = PV alarm (low) active STRUCT -
• ST: BYTE • 16#80
PV_Out Output for process value STRUCT -
• ST: BYTE • 16#80
PV_TH_Act 1 = PV tolerance message (high) active STRUCT -
• ST: BYTE • 16#80
PV_TL_Act 1 = PV tolerance message (low) active STRUCT -
• ST: BYTE • 16#80
PV_ToleHi Limit (high) of 3-sigma band around the STRUCT -
• ST: BYTE • 16#80
PV_ToleLo Limit (low) of 3-sigma band around the STRUCT -
• ST: BYTE • 16#80
PV_UnitOut Unit of measure for process value, for INT 0
interconnecting with PV_Unit input
parameter of the ConPerMon block
PV_WH_Act 1 = PV warning (high) active STRUCT -
• ST: BYTE • 16#80
PV_WL_Act 1 = PV warning (low) active STRUCT -
• ST: BYTE • 16#80
RbkOut Output for position feedback STRUCT -
• ST: BYTE • 16#80
RbkWH_Act 1 = Warning (high) for position feedback STRUCT -
• ST: BYTE • 16#80
RbkWL_Act 1 = Warning (low) for position feedback STRUCT -
• ST: BYTE • 16#80
RetValue Return value of WRREC/RDREC WORD 16#0
SP Setpoint used by controller STRUCT -
• ST: BYTE • 16#80

Control blocks

SP_DnRaAct 1 = Negative gradient limiting of setpoint STRUCT -
is active • Value: BOOL • 0.0
• ST: BYTE • 16#80
SP_ExHiAct 1 = Limit (high) for external setpoint has STRUCT -
been reached • Value: BOOL • 0.0
• ST: BYTE • 16#80
SP_ExLoAct 1 = Limit (low) for external setpoint has STRUCT -
been reached • Value: BOOL • 0.0
• ST: BYTE • 16#80
0 = Internal setpoint is active • Value: BOOL • 0.0
• ST: BYTE • 16#80
SP_ExtOut External setpoint, corresponds to input STRUCT -
parameter SP_Ext • Value: REAL • 0.0
• ST: BYTE • 16#80
SP_InHiOut Limit (high) for SP_Int corresponds to STRUCT -
input parameter SP_InHiLim • Value: REAL • 100.0
• ST: BYTE • 16#80
SP_InLoOut Limit (low) for SP_Int corresponds to STRUCT -
input parameter SP_InLoLim • Value: REAL • 0.0
• ST: BYTE • 16#80
SP_UpRaAct Positive gradient limiting of setpoint is STRUCT -
active • Value: BOOL • 0.0
• ST: BYTE • 16#80
SplitRange 1 = Split-range function has been BOOL 0
activated
StatusC Status of cooling optimization INT 16#00
StatusD Status of controller design INT 16#00
StatusH Status of heating optimization INT 16#00
StepCon 1 = Step controller BOOL 0
Stop Control output STRUCT -
1 =Stopped is active • Value: BOOL • 0
• ST: BYTE • 16#80
SumMsgAct 1 = Active process alarm STRUCT -
• ST: BYTE • 16#80
TunAct 1 = Optimization running BOOL 0

Control blocks

WithRbk Controller type: BOOL 0
0 = Step controller without position
feedback
1 = Step controller with position
feedback
ZoneTun Controller channels grouped in one zone WORD 16#0
for parallel optimization
See also

Control blocks
4.3.7 FmTemp block diagram
FmTemp block diagram
63B([+L$FW 63B([W/L 6SB([W,QW

/LPLW
63B([W 63B([/R$FW 63B,QW/L /LQN
63B([W$FW
63B([W2S 2SHUDWRU
63B([W2XW
63B,QW2S /RJLF 63B7UN39$1' 09B)RU2Q
63B/L2S 63B5DWH2Q 250DQ$FW2509B7UN2Q
63B([+L/LP
63B([/R/LP
63B5PS2Q
5HMHFW
5DPS
63B5PS7DUJHW 39
*UDGLHQW
63B,Q+L/LP
63B,Q/R/LP 63B5PS0RG7LPH
63B5PS7LPH
63B8S5D/LP 63B8S5D$FW
63B8S5D/LP
/LPLW 63B'Q5D/LP 63B'Q5D$FW
63B'Q5D/LP
$GY&R09
$GY&R$FW$1'
$GY&R0RG63
63B,Q+L/LP
63B,Q/R/LP $GY&R2Q

$GY&R(Q $GY&R0VWU2Q
$
5HMHFW 09B7UN2Q 1
63B,QW ' /LQN
09B)RU2Q $
LVOLPLWHG 2SHUDWRU
$GY&R0RG63 1
DQGWUDFNHG 2 $GY&R$FW
' /RJLF
$GY&R0RG63 $ 5
63B,Q+L/LP 63B,Q+L2XW 1
63B,Q/R/LP 63B,Q/R2XW 0DQ$FW $GY&R5G\
'
5HMHFW
0DQ
0DQ+L/LP 0DQ+L2XW
0DQ/R/LP 0DQ/R2XW 0DQ$FW
09B7UN2Q

09B7UN

0DQ$FW
2
09B7UN2Q 5
$GY&R$FW
$GY&R0RG63 $1'

Control blocks
39B287
6LP2Q 39B$+B$FW
39B:+B$FW
6LP39 $ODUP
39B7+B$FW
:ULWH39B287WR
39B7/B$FW
6LP39ZKHQ
DSSOLFDEOH6LP2Q 39B:/B$FW
39B$/B$FW
39B[+B/LP39B[/B/LP39B+\VW
39B[+B(Q39B[/B(Q
39B[+B0VJ(Q39B[+B0VJ(Q
39B[B'&39B[B'*
[ $:7
$ODUP
(5B$+B$FW
)0
2SHUDWLQJ 2XWSXW (5B$/B$FW
$XW0RG/L 0DQ$FW SDUDPHWHU SDUDPHWHUV
/LQN
0DQ0RG/L
2SHUDWRU 127 63B5( 63 63 (5B$+B/LP(5B$/B/LP(5B+\VW
$XW0RG2S $XW$FW
/RJLF /01B5( 39 (5B$+B(Q(5B$/B(Q
0DQ0RG2S /01B5(21 (5 (5B$+B0VJ(Q(5B$/B0VJ(Q
7UN2Q)0 /0175.21 ',69 ))ZG2XW (5B$B'&(5B$B'*
2SHQ/L 2SHQ 09B6DIH2Q 09
6$)(B21 /01
&ORVH/L 6[2SHQ 2SHQ
&ORVH 5EN2SHQHG /015+65(
6WRS/L 6WRS &ORVH
6[&ORVH 5EN&ORVHG /015/65( 4/0183 $
2SHQ2S 6WRS
/RJLF /0162321 4/01'1 1
&ORVH2S
/0183B23 '
6WRS2S
/01'1B23 /01B$
0RG/L2S 09B6SOL% 09B6SOL$
6B5EN2Q3,'7XQ /0156B21 /01B%
)8=,'B21 5EN2XW
)X]2SW2Q
63B([W$FW 3DU)0B(UU
43$5B)
$ODUP 5EN:+B$FW
4&+B) &K)0B(UU
63B([+L/LP &RQWUROOHU 5EN
5EN:/B$FW
63B,Q+L/LP SDUDPHWHU 4,' )X]2SW$FW
4)8==< )X]&RQ
63B([/R/LP 3URS6HO 3B6(/
463/(39 )X]63B39B$FW 5EN:+B/LP
63B,Q/R/LP 3B)GE6HO 3)'%B6(/
'B(/B6(/ 5EN:/B/LP
'B,Q6HO
63B+/0 4/016$)( 09B6DI$FW 5EN+\VW
63B//0 4/0175. 09B7UN$FW 5EN:+B(Q
'HDG%DQG '($'%B: 4/01B5( 09B([W$FW 5EN:/B(Q

*DLQ(II *$,1 5EN:+B0VJ(Q
*DLQ
SK\V 7, 7, 4/015B+6 5EN2SQ2XW 5EN:/B0VJ(Q
7' 7' 4/015B/6 5EN&OV2XW
1HJ*DLQ 7''LII*DLQ 70B/$*
1RUP39 09B6DIH /01B6$)( 4/015B21 :LWK5EN
/01B+/0 4635 6SOLW5DQJH
$XW$FW )0B $
/01B//0
0RWRU7LPH 075B70 40$1B)& 0DQ$5:B$FW 6WHS&RQ 1
09B+L/LP '
3XOVH7LPH 38/6(B70
0DQ+L/LP
%UHDN7LPH %5($.B70

09B/R/LP
0DQ/R/LP 23B6HO 23B6(/

See also

Control blocks
4.3.8.1 FmTemp views
Views of the FmTemp block

The block FmTemp provides the following views:
● Standard view of FM controllers (analog) (Page 131)
● Standard view of FM controllers (pulse controller) (Page 135)
● Standard view of FM controllers (step controller with position feedback) (Page 139)
● Standard view of FM controllers (step controller without position feedback) (Page 143)
● Limit value view of FM controllers (Page 157)
● Parameter view of FM controllers (Page 153)
● Preview of FM controllers (Page 165)
● Block icons for PID and FM controller (Page 181)

Control blocks
4.4 GainSched - Adapting parameter values for a PID controller
4.4.1 Description of GainSched

Family: Control
Area of application for GainSched

● Continuous adaptation of the parameter values of a PID controller to the current
operating point of a non-linear process
● Controller gain
● Integral action time
● Derivative action time
How it works
If your process requires different PID controller parameters due to its non-linear response at
different operating points, you can store optimum parameter sets for up to three different
operating points in theGainSched block in the form of a table ("timetable"). The current
operating point is represented by a continuously measurable variable X, typically by the
actual value of the controller itself. The block ensures that the suitable optimum parameters
Gain(j), TI(j) and TD(j) are made available to the controller for each operating point X(j).
If the process is between two operating points, the parameters are calculated by linear
interpolation between the optimum values of the two nearest operating points. This allows a
bumpless, continuous adaptation of the controller parameters while the process moves from
one operating point to another.
The block should be considered a supplementary function for a PID controller to improve the
control performance of the PID controller in non-linear processes. The GainSched faceplate
is called from the parameter view of the corresponding PID controller using the "Gain
scheduler" button.

Control blocks
In contrast to all other function blocks, the GainSched block is implemented as a CFC chart
and is generated with the "Compile chart as block type" function. The source chart
"FbGainSchedLim" is supplied with the library so that you have more options open to you:
● You can use the precompiled function block GainSched from the library if the standard
functionality is adequate for your needs.
● If you require special additional functions for gain scheduling in your application (for
example more than three operating points, additional logic functions for selecting the
parameters), you will need to modify the CFC source chart and compile it as a block type
with a different FB number.
If the current value of input parameter X is below the lowest value X1 in the table or above
the highest value X3, precisely the controller parameters which are specified at the relevant
boundary point X1 or X3 in the table are output.
Configuration
The GainSched block is placed in the same CFC chart as the assigned controller and
interconnected with it as shown in the corresponding template: The output parameters
Link2Gain, Link2TI and Link2TD are connected to the inputs Gain, TI and TD of the
PID controller. The X input of GainSched is supplied with the measured value for the
operating point, typically with the same value as PV of the controller.
You can open the standard view for the GainSched block from the parameter view of a
controller (for example PIDConL). Additional information on this topic is available in the
section Calling further faceplates (Page 43).
To specify the parameters for gain scheduling, run separate controller optimizations at each
of the intended operating points, for example with a tool such as the PID tuner. Use
amplitudes as small as possible to excite the process to capture the approximately linear
response in the area of the operating point under investigation. The optimum parameter
values calculated by the PID tuner are entered in the relevant row belonging to the operating
point in the table of the GainSched block. The table is clearly displayed in the standard view
of the faceplate. Make sure that the numeric values are also permanently stored in the data
management of the engineering system by reading back the numeric values of the
parameters from AS to the ES or enter them manually at the inputs of the CFC block.
For the GainSched block, the Advanced Process Library contains a template for process tag
types as an example with an application scenario for this block.
Example of process tag types:
● PID - control with operating-point-oriented parameter control (GainScheduling)
(Page 1431)

Control blocks
Gain scheduling for batch processes

A typical area of application for gain scheduling is in batch processes that, in contrast to
continuous processes, cannot be linearized around a fixed operating point because they
need to be moved backwards and forwards between different operating points during the
course of the batch. Here, there are three application scenarios:
● The controller parameters depend on a single continuously measurable variable that is
representative of the operating point, for example, the reactor temperature. This is the
normal use case for the GainSched block: The management of the controller parameters
is handled in the block and is independent of batch recipes.
● The controller parameters depend on a continuously measurable variable that is
representative of the operating point, but there is also a dependency on the materials
used in the reaction. Suitable parameter sets for gain scheduling can then be anchored in
the recipe and transferred by SIMATIC Batch to the GainSched block.
● The controller parameters depend only the current phase of the batch. They can then be
written directly from the Batch package to the PID controller and no gain scheduling block
is necessary. The disadvantage of this is that there is bump in the controller parameters
at the transfer from one phase to the next. The controller should be put into manual mode
temporarily at the time of the transfer to avoid a bump in the manipulated variable.
● the recipe only specifies which of the controller parameter sets 1 to 3 is currently required
from the GainSched block. The numerical values of the parameter, however, are not
anchored in the recipe. In this case input variable X of the GainSched block can then be
used as the number of the required data record and assigned by the recipe instead of
being linked with a measurable process variable. In this case, there are only three
discrete values for X and the precautions against a change of controller parameters with
bump outlined above must be taken because the interpolation abilities of the GainSched
block are not used.
In general, it is not necessary to manage the batch parameters (batch ID, batch name etc.)
in theGainSched block because no separate messages are generated and there is always a
1:1 relationship with a controller block that recognizes the batch parameters.
Status word allocation for Status parameter

This block does not provide the Status parameter.
See also
GainSched functions (Page 383)
GainSched messaging (Page 384)
GainSched I/Os (Page 385)
GainSched block diagram (Page 388)
GainSched error handling (Page 383)
GainSched modes (Page 382)

Control blocks
4.4.2 GainSched modes
GainSched modes
● Automatic mode
● Manual mode
Automatic mode
In automatic mode (ManParOn = 0), the controller parameters correspond to the settings in
the automatic area of the parameter view determined through a polygon.
Manual mode
In manual mode (ManParOn = 1), the controller parameters correspond to the settings in
the manual area.
See also
GainSched block diagram (Page 388)
GainSched I/Os (Page 385)
GainSched messaging (Page 384)
GainSched error handling (Page 383)
GainSched functions (Page 383)
Description of GainSched (Page 379)


Process Control System PCS 7

Uploaded by

Copyright:

Available Formats

Process Control System PCS 7

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Process Control System PCS 7

Uploaded by

Copyright:

Available Formats

Basics of APL 1

SIMATIC PCS 7 Advanced Process Library V71

Siemens AG A5E02102723-01 Copyright © Siemens AG 2009.

1 Basics of APL .......................................................................................................................................... 25

PCS 7 Advanced Process Library V71

1.2.5 General functions for controllers ............................................................................................... 108

PCS 7 Advanced Process Library V71

1.5 Selectable block response .........................................................................................................186

PCS 7 Advanced Process Library V71

2.2.8 Operator control and monitoring ............................................................................................... 230

PCS 7 Advanced Process Library V71

4.2 FmCont - Interface to module FM 355.......................................................................................306

PCS 7 Advanced Process Library V71

4.6 PIDConL - Continuous PID controller ....................................................................................... 431

PCS 7 Advanced Process Library V71

4.10 SplRange - signal splitter ...........................................................................................................572

PCS 7 Advanced Process Library V71

5.4 MotSpdL - Two-speed motor..................................................................................................... 687

PCS 7 Advanced Process Library V71

6 Channel blocks ...................................................................................................................................... 821

PCS 7 Advanced Process Library V71

6.8 Pcs7DiIn - Digital input driver.................................................................................................... 889

PCS 7 Advanced Process Library V71

7.3 StruDiIn - separating a digital structured variable......................................................................933

PCS 7 Advanced Process Library V71

PCS 7 Advanced Process Library V71

9 Dosing blocks ...................................................................................................................................... 1017

PCS 7 Advanced Process Library V71

10.5 Derivative - Obtaining a derivative .......................................................................................... 1098

PCS 7 Advanced Process Library V71

10.11 Mul08 - Multiplier with 8 values................................................................................................1139

PCS 7 Advanced Process Library V71

11.2.8 Operator control and monitoring ............................................................................................. 1188

PCS 7 Advanced Process Library V71

12.3.6 MonDiL I/Os .............................................................................................................................1269

PCS 7 Advanced Process Library V71

14 Logical analog blocks .......................................................................................................................... 1347

PCS 7 Advanced Process Library V71

15 Logical digital blocks............................................................................................................................ 1393

PCS 7 Advanced Process Library V71

16 Maintenance blocks ............................................................................................................................. 1421

PCS 7 Advanced Process Library V71

18 PCS 7 Advanced Process Control Templates...................................................................................... 1439

PCS 7 Advanced Process Library V71

PCS 7 Advanced Process Library V71

1.1.1 Overview of the modes

Overview of the individual modes

Operating modes for motors, valves and dosers

PCS 7 Advanced Process Library V71

Operating modes for controllers

Operating modes for blocks without "Manual" and "Automatic" operation

PCS 7 Advanced Process Library V71

"On" operating mode

1.1.3 Out of service

Using the "out of service" operating mode

Requirement for the "out of service" mode

Switching on the out of service operating mode by using the faceplate

PCS 7 Advanced Process Library V71

Switching on the Out of service operating mode by using the interconnection

Exiting the "Out of service" operating mode

)DFHSODWH RU6)& &)&6)&

0DQ0RG2S 0DQ0RG/L $XW0RG/L

)DFHSODWH RU6)& &)&6)&

0DQ0RG2S 0DQ0RG/L $XW0RG/L