Eio0000002093 06
Eio0000002093 06
Eio0000002093 06
EIO0000002093 01/2018
PlantStruxure General
Purpose Library for Unity
Process Components User Guide
01/2018
EIO0000002093.06
www.schneider-electric.com
The information provided in this documentation contains general descriptions and/or technical
characteristics of the performance of the products contained herein. This documentation is not
intended as a substitute for and is not to be used for determining suitability or reliability of these
products for specific user applications. It is the duty of any such user or integrator to perform the
appropriate and complete risk analysis, evaluation and testing of the products with respect to the
relevant specific application or use thereof. Neither Schneider Electric nor any of its affiliates or
subsidiaries shall be responsible or liable for misuse of the information contained herein. If you
have any suggestions for improvements or amendments or have found errors in this publication,
please notify us.
No part of this document may be reproduced in any form or by any means, electronic or
mechanical, including photocopying, without express written permission of Schneider Electric.
All pertinent state, regional, and local safety regulations must be observed when installing and
using this product. For reasons of safety and to help ensure compliance with documented system
data, only the manufacturer should perform repairs to components.
When devices are used for applications with technical safety requirements, the relevant
instructions must be followed.
Failure to use Schneider Electric software or approved software with our hardware products may
result in injury, harm, or improper operating results.
Failure to observe this information can result in injury or equipment damage.
© 2017 Schneider Electric. All Rights Reserved.
2 EIO0000002093 01/2018
Table of Contents
Safety Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Part I Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 1 Process Unity Components . . . . . . . . . . . . . . . . . . . . . . 27
List of Function Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Chapter 2 General Function Block Concepts . . . . . . . . . . . . . . . . . 31
Modularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Function Block Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Set-Point Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Simulation and Interlocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Part II Signal Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Chapter 3 AISignalCond1 and AISignalCondReal1 - Analog
Input Signal Conditioning . . . . . . . . . . . . . . . . . . . . . . . . 41
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
EFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Obtaining the Module Status When Mapped to X80 I/O Module . . . . . 46
Chapter 4 AOSIGNALCOND - Analog Output Signal conditioning. . . 49
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Chapter 5 CounterSignalCondUInt and CounterSignalCon-
dUDInt - Counter Signal Conditioning . . . . . . . . . . . . . . 55
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
EFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Chapter 6 DISignalCond1 - Digital Input Signal Conditioning . . . 61
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
EFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
EIO0000002093 01/2018 3
Chapter 7 DOSIGNALCOND - Digital Output Signal Conditioning. . . . 67
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Chapter 8 AHISIGNAL - HART Device Signal Mapping . . . . . . . . . . 73
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Chapter 9 AISignalHart1 - HART Input Signal Conditioning
(M580) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
EFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Chapter 10 ACALC - Analog Calculations . . . . . . . . . . . . . . . . . . . . . . 87
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Chapter 11 AALARM - Analog Alarms . . . . . . . . . . . . . . . . . . . . . . . . . 95
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Chapter 12 AINPUT - Analog Input Conditioning . . . . . . . . . . . . . . . . 103
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4 EIO0000002093 01/2018
Chapter 13 AINPUT1 - Configurable-Range Analog Input
Conditioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Chapter 14 ALINEAR - Linear Interpolation. . . . . . . . . . . . . . . . . . . . 119
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Chapter 15 AOUTPUT - Analog Output Conditioning . . . . . . . . . . . . . 125
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Chapter 16 AOUTPUTLP - Local Panel for Analog Output Conditioning 135
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Chapter 17 DCALC - Digital Calculation . . . . . . . . . . . . . . . . . . . . . . . 147
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
EIO0000002093 01/2018 5
Chapter 18 DINPUT - Digital Input Conditioning . . . . . . . . . . . . . . . . . 153
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Chapter 19 DOUTPUT - Digital Output Conditioning . . . . . . . . . . . . . . 161
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Chapter 20 MAINPUT1 - Conditioning of Multiple Analog Inputs with
Configurable Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Chapter 21 STAHL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
21.1 STAHLAI8CH for STAHL 8-Channel Analog Input Modules . . . . . . . . 180
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
21.2 STAHLAO8CH for STAHL 8-Channel Analog Output Modules . . . . . . . 185
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
21.3 STAHLDI16CH for STAHL 16-Channel Digital Input Modules . . . . . . . 190
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6 EIO0000002093 01/2018
21.4 STAHLDO8 for STAHL 8-Channel Digital Output Modules. . . . . . . . . . 195
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
21.5 STAHLHARTVal4 - Processing of Four HART Values . . . . . . . . . . . . 200
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
21.6 STAHLHARTVal8 - Processing of Eight HART Values . . . . . . . . . . . . 205
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Chapter 22 TOTAL - Totalizing Function . . . . . . . . . . . . . . . . . . . . . . 211
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Part III On/Off Device Control. . . . . . . . . . . . . . . . . . . . . . . . 229
Chapter 23 DEVCTL - On-Off Device. . . . . . . . . . . . . . . . . . . . . . . . . 231
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Chapter 24 DEVLP - Local Panel for Controlling On-Off Devices . . . 245
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
EIO0000002093 01/2018 7
Chapter 25 DEVMNT - On-Off Device Maintenance . . . . . . . . . . . . . . . 257
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Chapter 26 DUALOP - Dual Output . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Decription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Chapter 27 HVALVE - Manual Valve . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Chapter 28 MOTOR2 - 2-Speed/2-Rotation Direction Motor . . . . . . . . 281
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Chapter 29 MOTOR2LP - Local Panel for Controlling 2-Speed/2-
Rotation Direction Motors . . . . . . . . . . . . . . . . . . . . . . . . . 299
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
8 EIO0000002093 01/2018
Chapter 30 MVALVED - Discrete Motorized Valve . . . . . . . . . . . . . . . 311
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Chapter 31 MVALVEDLP - Local Panel for Controlling Motorized On-
Off Valves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Part IV Analog Device Control . . . . . . . . . . . . . . . . . . . . . . . 333
Chapter 32 CVALVE - Control Valve with Position Feedback . . . . . . 335
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Chapter 33 CVALVELP - Local Panel for Controlling Control Valves. 347
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Chapter 34 MVALVE - Motorized Valve with Positioner . . . . . . . . . . . 359
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
EIO0000002093 01/2018 9
Chapter 35 MVALVELP - Local Panel for Controlling Motorized Valves 371
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Chapter 36 SDDEVCTL - Device with Variable Speed Drive . . . . . . . . 383
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Chapter 37 SDDEVLP - Local Panel for Controlling Devices with a
Variable-Speed Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Part V Process Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Chapter 38 ARAMP - RAMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Chapter 39 IMCTL - IMC Controller with Monitoring Interface . . . . . . 425
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
10 EIO0000002093 01/2018
Chapter 40 LDLGCTL - Lead-Lag Controller with Monitoring Interface 437
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Chapter 41 PIDCTL - PIDFF Regulator with Monitoring Interface. . . 447
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Chapter 42 PIDMUX - Multiplexer for 2 Groups of PIDCTL Parameters 457
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Chapter 43 PWMCTL - Pulse-Width Modulated Controller . . . . . . . . . 465
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Chapter 44 RATIOCTL - Ratio Controller . . . . . . . . . . . . . . . . . . . . . 473
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
EIO0000002093 01/2018 11
Chapter 45 SPLRGCTL - Split-Range Controller . . . . . . . . . . . . . . . . . 481
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Chapter 46 STEP3CTL - 3 Step Controller/Positioner . . . . . . . . . . . . . 489
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Part VI Sequential Control . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Chapter 47 Sequential Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Description of Sequential Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
Definition of Status and Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Status Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Status Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Chapter 48 SEQCTL1 - Advanced Sequential Control. . . . . . . . . . . . . 509
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Chapter 49 Auxiliary Functions of Sequential Control. . . . . . . . . . . . . 519
49.1 SEQTRANS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
49.2 SEQFAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
49.3 SEQSTABLESTEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
12 EIO0000002093 01/2018
49.4 SEQSTEPDESC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Chapter 50 SEQPARxx - Sequence Parameter Management . . . . . . 537
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Chapter 51 SEQCTL1 - Example of Use . . . . . . . . . . . . . . . . . . . . . . 545
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Reusable Sequence Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Part VII Batch Phase Manager . . . . . . . . . . . . . . . . . . . . . . . 555
Chapter 52 Batch Phase Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Description of Batch Phase Manager . . . . . . . . . . . . . . . . . . . . . . . . . 558
Definition of Phase Statuses, Batch Phase Statuses, Phase
Commands and Batch Phase Commands . . . . . . . . . . . . . . . . . . . . . 560
Status Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
Status Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Chapter 53 IBPHASE - Individual Batch Phase Manager . . . . . . . . . 567
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Chapter 54 Auxiliary Functions of Batch Phase . . . . . . . . . . . . . . . . 585
54.1 IBTRANS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
54.2 IBFAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
EIO0000002093 01/2018 13
54.3 IBSTABLESTEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
54.4 IBSTEPDESC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
Chapter 55 IBPARxx - Batch Phase Parameter Management . . . . . . 603
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Chapter 56 USERPHASExx - User Defined Process Logic . . . . . . . . . 611
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
Chapter 57 IBPHASE - Example of Use . . . . . . . . . . . . . . . . . . . . . . . 615
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Reusable Phase Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
Part VIII Auxiliary Functions . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Chapter 58 ASELECT - Analog Signal Selector . . . . . . . . . . . . . . . . . 627
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
Chapter 59 ASELECT1 - Selector for Analog Signals with Monitoring
Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
14 EIO0000002093 01/2018
Chapter 60 CONDSUM - Summary of Conditions . . . . . . . . . . . . . . . . 641
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Chapter 61 CONDSUM1 - Interlock Condition Summary . . . . . . . . . . . 649
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Chapter 62 MSGBOX - Messages to the Operator . . . . . . . . . . . . . . . 657
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
Public Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
Index ......................................... 667
EIO0000002093 01/2018 15
16 EIO0000002093 01/2018
Safety Information
Important Information
NOTICE
Read these instructions carefully, and look at the equipment to become familiar with the device
before trying to install, operate, or maintain it. The following special messages may appear
throughout this documentation or on the equipment to warn of potential hazards or to call attention
to information that clarifies or simplifies a procedure.
EIO0000002093 01/2018 17
PLEASE NOTE
Electrical equipment should be installed, operated, serviced, and maintained only by qualified
personnel. No responsibility is assumed by Schneider Electric for any consequences arising out of
the use of this material.
A qualified person is one who has skills and knowledge related to the construction and operation
of electrical equipment and its installation, and has received safety training to recognize and avoid
the hazards involved.
WARNING
UNGUARDED EQUIPMENT
Do not use this software and related automation equipment on equipment which does not have
point-of-operation protection.
Do not reach into machinery during operation.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
This automation equipment and related software is used to control a variety of industrial processes.
The type or model of automation equipment suitable for each application will vary depending on
factors such as the control function required, degree of protection required, production methods,
unusual conditions, government regulations, etc. In some applications, more than one processor
may be required, as when backup redundancy is needed.
Only you, the user, machine builder or system integrator can be aware of all the conditions and
factors present during setup, operation, and maintenance of the machine and, therefore, can
determine the automation equipment and the related safeties and interlocks which can be properly
used. When selecting automation and control equipment and related software for a particular
application, you should refer to the applicable local and national standards and regulations. The
National Safety Council's Accident Prevention Manual (nationally recognized in the United States
of America) also provides much useful information.
In some applications, such as packaging machinery, additional operator protection such as point-
of-operation guarding must be provided. This is necessary if the operator's hands and other parts
of the body are free to enter the pinch points or other hazardous areas and serious injury can occur.
Software products alone cannot protect an operator from injury. For this reason the software
cannot be substituted for or take the place of point-of-operation protection.
18 EIO0000002093 01/2018
Ensure that appropriate safeties and mechanical/electrical interlocks related to point-of-operation
protection have been installed and are operational before placing the equipment into service. All
interlocks and safeties related to point-of-operation protection must be coordinated with the related
automation equipment and software programming.
NOTE: Coordination of safeties and mechanical/electrical interlocks for point-of-operation
protection is outside the scope of the Function Block Library, System User Guide, or other
implementation referenced in this documentation.
CAUTION
EQUIPMENT OPERATION HAZARD
Verify that all installation and set up procedures have been completed.
Before operational tests are performed, remove all blocks or other temporary holding means
used for shipment from all component devices.
Remove tools, meters, and debris from equipment.
Failure to follow these instructions can result in injury or equipment damage.
Follow all start-up tests recommended in the equipment documentation. Store all equipment
documentation for future references.
Software testing must be done in both simulated and real environments.
Verify that the completed system is free from all short circuits and temporary grounds that are not
installed according to local regulations (according to the National Electrical Code in the U.S.A, for
instance). If high-potential voltage testing is necessary, follow recommendations in equipment
documentation to prevent accidental equipment damage.
Before energizing equipment:
Remove tools, meters, and debris from equipment.
Close the equipment enclosure door.
Remove all temporary grounds from incoming power lines.
Perform all start-up tests recommended by the manufacturer.
EIO0000002093 01/2018 19
OPERATION AND ADJUSTMENTS
The following precautions are from the NEMA Standards Publication ICS 7.1-1995 (English
version prevails):
Regardless of the care exercised in the design and manufacture of equipment or in the selection
and ratings of components, there are hazards that can be encountered if such equipment is
improperly operated.
It is sometimes possible to misadjust the equipment and thus produce unsatisfactory or unsafe
operation. Always use the manufacturer’s instructions as a guide for functional adjustments.
Personnel who have access to these adjustments should be familiar with the equipment
manufacturer’s instructions and the machinery used with the electrical equipment.
Only those operational adjustments actually required by the operator should be accessible to
the operator. Access to other controls should be restricted to prevent unauthorized changes in
operating characteristics.
20 EIO0000002093 01/2018
About the Book
At a Glance
Document Scope
This document provides an operating information of a project developed by using Unity Pro and
PlantStruxure General Purpose Library for Unity.
This document does not cover any development procedures and internal functionality details.
Users of the Unity Pro services are supposed to have a working knowledge in the employment of
Unity Pro.
Validity Note
This document has been updated with the release of PlantStruxure General Purpose Library for
Unity 2018.
PlantStruxure General Purpose Library for Unity process components support the following
software versions of Unity Pro:
Unity Pro V11
EIO0000002093 01/2018 21
Product Related Information
WARNING
LOSS OF CONTROL
Perform a Failure Mode and Effects Analysis (FMEA) of your application, and apply preventive
and detective controls before implementation.
Provide a fallback state for undesired control events or sequences.
Provide separate or redundant control paths wherever required.
Supply appropriate parameters, particularly for limits.
Review the implications of transmission delays and take actions to mitigate.
Review the implications of communication link interruptions and take actions to mitigate.
Provide independent paths for control functions (for example, emergency stop, over-limit
conditions, and fault conditions) according to the safety analysis and applicable codes, and
regulations.
Apply local accident prevention and safety regulations and guidelines. 1
Test each implementation of this library for proper operation before placing it into service.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
NOTE: For additional information, refer to NEMA ICS 1.1 (latest edition), Safety Guidelines for the
Application, Installation, and Maintenance of Solid State Control and to NEMA ICS 7.1 (latest
edition), Safety Standards for Construction and Guide for Selection, Installation and Operation of
Adjustable-Speed Drive Systems or their equivalent governing your particular location.
The application of this product requires expertise in the design and operation of control systems.
WARNING
UNINTENDED EQUIPMENT OPERATION
Allow only authorized personnel with expertise in the design and operation of control systems
to program, install, alter, and apply this product.
Follow local and national safety codes and standards.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
22 EIO0000002093 01/2018
Examples described in this manual are provided for information only.
WARNING
UNINTENDED EQUIPMENT OPERATION
Adapt examples that are given in this manual to the specific functions and requirements of your
industrial application before you implement them.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
EIO0000002093 01/2018 23
24 EIO0000002093 01/2018
PlantStruxure General Purpose Library for Unity
Overview
EIO0000002093 01/2018
Part I
Overview
Overview
Overview
The PlantStruxure General Purpose Library for Unity software provides the function blocks (EFBs
and DFBs) that are pre-configured and tested by Schneider Electric and that are designed for
automating a large variety of processes.
The Unity Pro components for process control provide the common required functions, facilitating
the development of control systems.
To automate and simplify the implementation process of control systems, you can use these DFBs
together with tools for code generation and for the synchronization of control and monitoring
subsystems.
This document describes the basic concepts and details behind each one of the function blocks
(EFBs and DFBs) for implementing the common cross-process and cross-market Control
functions.
EIO0000002093 01/2018 25
Overview
26 EIO0000002093 01/2018
PlantStruxure General Purpose Library for Unity
Process Unity Components
EIO0000002093 01/2018
Chapter 1
Process Unity Components
List of Families
The function blocks described in this document are grouped by family.
EIO0000002093 01/2018 27
Process Unity Components
Description
The table lists the function blocks of each family:
28 EIO0000002093 01/2018
Process Unity Components
EIO0000002093 01/2018 29
Process Unity Components
30 EIO0000002093 01/2018
PlantStruxure General Purpose Library for Unity
General Concepts
EIO0000002093 01/2018
Chapter 2
General Function Block Concepts
Overview
This chapter describes the basic concepts that the process Unity Pro components implement.
EIO0000002093 01/2018 31
General Concepts
Modularity
Overview
The function blocks are designed in such a way that the functions they implement are cumulative.
This way, you can incorporate the functions required for each specific case into the system.
Example
An example featuring three function blocks connected to each other to provide the necessary
functions to set up an on-off motor with interlocking and maintenance. A DEVCTL block (core
service) provides on-off motor functionalities. Additionally, you can integrate CONDSUM block
(optional service) to achieve interlock functionalities and DEVMNT block (optional service) to
provide maintenance functionalities (number of switch operations and hours of operation).
32 EIO0000002093 01/2018
General Concepts
Overview
The function blocks for Process provide an interface that allows them to be configured, monitored,
and controlled both from the monitoring subsystem and the control subsystem (continuous and/or
sequential control).
The following interfaces are provided:
Basic Configuration
Continuous Control
Sequential Control
States and Monitoring
Basic Configuration
DFB input pins are usually connected to static data and recognized in engineering time (for
example, input channel range or limit switch enabling on an on-off device).
Continuous Control
DFB input and output pins:
allow receiving commands from other blocks.
provide block status to other blocks to enable implementing switching operations (for example,
remote set-point -RSP-), detected alarms (for example, high-level alarm -HIHI-), interlocking
(for example, activation of interlocking ILCK, or interlocking set-point -ILCKSP-), and so on.
Sequential Control
SC public and structured variable publishes the block status and allows its control from the control
sequences (commands not kept).
EIO0000002093 01/2018 33
General Concepts
Illustration
The following figure illustrates the previous provided interface.
34 EIO0000002093 01/2018
General Concepts
Set-Point Management
Overview
The blocks for device control manage the set-points coming from the following sources according
to the owner:
Operator
Program
To avoid unwanted transitions in the set-point, continuously set the local set-points (Operator or
Program) to match the selected set-point.
In principle, the owner (Operator or Program) of the function block is not modified from the control
subsystem (through the program in the PLC) because the control subsystem is mechanism that
stops the Program from affecting the block. This is to confirm that the commands send towards the
block are those generated from the monitoring subsystem.
Operator
Operator/Local set-point commands received from the monitoring subsystem (Supervision). These
commands arrive at the function blocks.
EIO0000002093 01/2018 35
General Concepts
Program
Commands generated from the control program (Control).
Two different possible sources within the Program are as follows:
Continuous Control (usually identified as a Program/Remote or Program/Cascade set-point):
The set-points generated from the Continuous Control strategies report to the function blocks
through a specific pin which is usually identified as Remote Set-Point (RSP). These commands
are given by level.
Sequential Control (Local Set-Point): The set-points generated from the control sequences (for
example, for starting a continuous process section or a batch process stage) send the
commands to the function blocks through the public data structure of the block (SC – Sequential
Control – variable).
36 EIO0000002093 01/2018
General Concepts
Simulation
Function blocks connected to physical inputs (digital or analog) feature a simulation mode that
enables you to enter the value that needs to be considered as an input through the Supervision
system during operation.
This simulates the position of the associated device (DEVCTL and SDDEVCTL blocks) as the
position defined by the setpoint or interlock, regardless of the actual state of the physical inputs.
You can use this operating mode:
In case an input loop is not working properly.
To perform programming tests when the signals and instruments associated with the function
block are not available.
Interlocking
You can interlock function blocks that are connected to physical outputs (digital or analog) at a
determined configurable position.
EIO0000002093 01/2018 37
General Concepts
38 EIO0000002093 01/2018
PlantStruxure General Purpose Library for Unity
Signal Processing
EIO0000002093 01/2018
Part II
Signal Processing
Signal Processing
Overview
This part provides a detailed description of the functions, pins, pin layout, and variables of the
function blocks of the signal processing family.
These function blocks do not reflect any specific installation.
WARNING
LOSS OF CONTROL
Perform a Failure Mode and Effects Analysis (FMEA) of your application, and apply preventive
and detective controls before implementation.
Provide a fallback state for undesired control events or sequences.
Provide separate or redundant control paths wherever required.
Supply appropriate parameters, particularly for limits.
Review the implications of transmission delays and take actions to mitigate.
Review the implications of communication link interruptions and take actions to mitigate.
Provide independent paths for control functions (for example, emergency stop, over-limit
conditions, and fault conditions) according to the safety analysis and applicable codes, and
regulations.
Apply local accident prevention and safety regulations and guidelines. 1
Test each implementation of this library for proper operation before placing it into service.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
1For additional information, refer to NEMA ICS 1.1 (latest edition), Safety Guidelines for the
Application, Installation, and Maintenance of Solid State Control and to NEMA ICS 7.1 (latest
edition), Safety Standards for Construction and Guide for Selection, Installation and Operation of
Adjustable-Speed Drive Systems or their equivalent governing your particular location.
EIO0000002093 01/2018 39
Signal Processing
40 EIO0000002093 01/2018
PlantStruxure General Purpose Library for Unity
AISignalCond1 and AISignalCondReal1
EIO0000002093 01/2018
Chapter 3
AISignalCond1 and AISignalCondReal1 - Analog Input Signal Conditioning
Overview
This chapter describes the AISignalCond1 and AISignalCondReal1 EFBs.
EIO0000002093 01/2018 41
AISignalCond1 and AISignalCondReal1
Description
General
PlantStruxure General Purpose library for Unity uses the hardware abstraction layer for signal
objects coming from the field to controllers.
The EFB allows processing the signal value and signal quality data. Depending on the data type
of the signal, this is either AISignalCond1 (for Int data type) or AISignalCondReal1 (for
Real data type).
42 EIO0000002093 01/2018
AISignalCond1 and AISignalCondReal1
EFB Representation
Representation
These EFBs have been specifically designed for use with the FBD language of the controller.
EIO0000002093 01/2018 43
AISignalCond1 and AISignalCondReal1
Inputs
44 EIO0000002093 01/2018
AISignalCond1 and AISignalCondReal1
Outputs
EIO0000002093 01/2018 45
AISignalCond1 and AISignalCondReal1
Overview
The SignalFailure parameter indicates the health of each channel signal. When the signal is
mapped to an X80 I/O module, the value of the variable that is connected to the ModuleStatus
input of the signal conditioning EFB is true by default (the value is REF (PES_CONST_TRUE)). You
need to modify the generated logic to use the value of the MOD_HEALTH variable of the DDDT that
is created instead. This applies to the digital and analog input and output signal conditioning EFBs.
If you want to obtain the module status using module health, follow this procedure.
Module Status
After refine online of the control project, update the control project from the topological manager.
Use the module health provided by DDDT (Device Derived Data Types) variables for obtaining the
module status.
You can locate the MOD_HEALTH as shown in the following figure:
46 EIO0000002093 01/2018
AISignalCond1 and AISignalCondReal1
You can map the module health variable (MOD_HEALTH) in the following ways:
Recommended method: By using the variable connected to the ModuleStatus pin of the
signal conditioning EFB. You can use the MOVE EFB to move the value of the MOD_HEALTH
variable to the variable that holds the module status (variable with S suffix)..
By replacing the variable holding the module status, which is connected to the ModuleStatus
pin of the signal conditioning EFB with the module health variable of the DDDT.
EIO0000002093 01/2018 47
AISignalCond1 and AISignalCondReal1
48 EIO0000002093 01/2018
PlantStruxure General Purpose Library for Unity
AOSIGNALCOND
EIO0000002093 01/2018
Chapter 4
AOSIGNALCOND - Analog Output Signal conditioning
Overview
This chapter describes the AOSIGNALCOND DFB.
EIO0000002093 01/2018 49
AOSIGNALCOND
Description
General
PlantStruxure General Purpose library for Unity uses the hardware abstraction layer for signal
objects coming from the field to controllers.
The AOSIGNALCOND DFB allows processing the analog (Int data type) signal value and signal
quality data.
The AOSIGNALMOVE DFB allows processing the signal value only.
50 EIO0000002093 01/2018
AOSIGNALCOND
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
EIO0000002093 01/2018 51
AOSIGNALCOND
Inputs
52 EIO0000002093 01/2018
AOSIGNALCOND
Outputs
EIO0000002093 01/2018 53
AOSIGNALCOND
54 EIO0000002093 01/2018
PlantStruxure General Purpose Library for Unity
CounterSignalCondUInt and CounterSignalCondUDInt
EIO0000002093 01/2018
Chapter 5
CounterSignalCondUInt and CounterSignalCondUDInt - Counter Signal Conditioning
Overview
This chapter describes the CounterSignalCondUInt and CounterSignalCondUDInt EFBs.
EIO0000002093 01/2018 55
CounterSignalCondUInt and CounterSignalCondUDInt
Description
General
PlantStruxure General Purpose library for Unity uses the hardware abstraction layer for signal
objects coming from the field to controllers.
The EFB allows processing the signal value and signal quality data. Depending on the counter
channel data type of the signal, this is either CounterSignalCondUDInt (for UDINT data type)
or CounterSignalCondUInt (for UINT data type).
56 EIO0000002093 01/2018
CounterSignalCondUInt and CounterSignalCondUDInt
EFB Representation
Representation
These EFBs have been specifically designed for use with the FBD language of the controller.
EIO0000002093 01/2018 57
CounterSignalCondUInt and CounterSignalCondUDInt
Inputs
58 EIO0000002093 01/2018
CounterSignalCondUInt and CounterSignalCondUDInt
Outputs
EIO0000002093 01/2018 59
CounterSignalCondUInt and CounterSignalCondUDInt
60 EIO0000002093 01/2018
PlantStruxure General Purpose Library for Unity
DISignalCond1
EIO0000002093 01/2018
Chapter 6
DISignalCond1 - Digital Input Signal Conditioning
Overview
This chapter describes the DISignalCond1 EFB.
EIO0000002093 01/2018 61
DISignalCond1
Description
General
PlantStruxure General Purpose library for Unity uses the hardware abstraction layer for signal
objects coming from the field to controllers.
The DISignalCond1 EFB allows processing the digital signal value and signal quality data.
62 EIO0000002093 01/2018
DISignalCond1
EFB Representation
Representation
EIO0000002093 01/2018 63
DISignalCond1
Inputs
64 EIO0000002093 01/2018
DISignalCond1
Outputs
EIO0000002093 01/2018 65
DISignalCond1
66 EIO0000002093 01/2018
PlantStruxure General Purpose Library for Unity
DOSIGNALCOND
EIO0000002093 01/2018
Chapter 7
DOSIGNALCOND - Digital Output Signal Conditioning
Overview
This chapter describes the DOSIGNALCOND DFB.
EIO0000002093 01/2018 67
DOSIGNALCOND
Description
General
PlantStruxure General Purpose library for Unity uses the hardware abstraction layer for signal
objects coming from the field to controllers.
The DOSIGNALCOND DFB allows processing the digital signal value and signal quality data.
The SIGNALMOVE DFB allows processing the digital signal value only.
68 EIO0000002093 01/2018
DOSIGNALCOND
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
EIO0000002093 01/2018 69
DOSIGNALCOND
Inputs
70 EIO0000002093 01/2018
DOSIGNALCOND
Outputs
EIO0000002093 01/2018 71
DOSIGNALCOND
72 EIO0000002093 01/2018
PlantStruxure General Purpose Library for Unity
AHISIGNAL
EIO0000002093 01/2018
Chapter 8
AHISIGNAL - HART Device Signal Mapping
Overview
This chapter describes the AHISIGNAL DFB.
EIO0000002093 01/2018 73
AHISIGNAL
Description
Overview
The AHISIGNAL DFB is used for HART devices that communicate with the controller through the
Advantys Island.
The function block maps the channel information from the Advantys to the device if the channel is
enabled and connected.
74 EIO0000002093 01/2018
AHISIGNAL
DFB Representation
Representation
The FBD is designed for use with the FBD language of the controller.
The figure shows the AHISIGNAL DFB:
EIO0000002093 01/2018 75
AHISIGNAL
Inputs
76 EIO0000002093 01/2018
AHISIGNAL
Outputs
EIO0000002093 01/2018 77
AHISIGNAL
78 EIO0000002093 01/2018
AHISIGNAL
EIO0000002093 01/2018 79
AHISIGNAL
Public Variables
Timing diagram:
80 EIO0000002093 01/2018
PlantStruxure General Purpose Library for Unity
AISignalHart1
EIO0000002093 01/2018
Chapter 9
AISignalHart1 - HART Input Signal Conditioning (M580)
Overview
This chapter describes the AISignalHart1 EFB.
EIO0000002093 01/2018 81
AISignalHart1
Description
General
The AISignalHart1 EFB is used to read DTM generated extended HART data from BMEAHI
and BMEAHO modules.
82 EIO0000002093 01/2018
AISignalHart1
EFB Representation
Representation
The EFB is designed for use with the FBD language of the controller.
EIO0000002093 01/2018 83
AISignalHart1
Inputs
84 EIO0000002093 01/2018
AISignalHart1
Outputs
EIO0000002093 01/2018 85
AISignalHart1
86 EIO0000002093 01/2018
PlantStruxure General Purpose Library for Unity
ACALC
EIO0000002093 01/2018
Chapter 10
ACALC - Analog Calculations
Overview
This chapter describes the ACALC DFB.
EIO0000002093 01/2018 87
ACALC
Description
General
The ACALC DFB is used to perform calculations based on an analog signal.
The DFB can perform the following calculations:
Derivative Rate of Change (ROC)
Totalizing (integral with the trapezoidal rule)
Average
Minimum
Maximum
The DFB memorizes up to a maximum of 20 samples of the measurement (Present Value PV), and
calculations are performed based on them.
This DFB can supplement the General Purpose Library AINPUT DFB providing calculations based
on previously scaled analog inputs.
In turn, the DFB can provide calculated data to AINPUT DFBs (configured with an external PV
input) to provide the standard interface to the monitoring subsystem so that these calculations can
be represented in the user interface or detected alarms can be applied through AALARM-type
DFBs.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Derivative The slope of the measurement development is calculated with linear regression.
Totalizing The totalization (for example, for flows) is calculated with the trapezoidal rule algorithm.
Average Calculates the average of the values memorized in the DFB.
Maximum Calculates the maximum value of the measurement among those stored in the DFB.
Minimum Calculates the minimum value of the measurement among those stored in the DFB.The DFB
allows alarm monitoring to be enabled/disabled individually.
NOTE: The function block uses the Freerun function for time calculations. Therefore, the ACALC
DFB is only available if the controller CPU supports this function.
88 EIO0000002093 01/2018
ACALC
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
EIO0000002093 01/2018 89
ACALC
Inputs
90 EIO0000002093 01/2018
ACALC
Outputs
Where:
KROC Conversion factor applied to the derivative calculation. Refer to the KTOTAL input
(see page 90).
n Number of samples (up to 20 after the whole internal sample table is loaded).
t Relative time elapsed from the first sample to the sample used in the calculation (corresponding
PV value).
PV Sample value.
Calculation formula for the totalization:
¤ PV PV0 ³
KTOTAL r t1
t0 r ¥ 1 ´µ
¦ 2
Where:
KTOTAL Refer to the KROC input (see page 90).
t1 Time in which the current sample is taken.
t0 Time in which the previous sample was taken.
PV1 Value of the current measurement.
PV0 Value of the previous measurement.
EIO0000002093 01/2018 91
ACALC
The calculation is carried out with a value relative to 0, that is, values under 0 will be deducted from
the cumulative calculation. The calculation is only performed if it is enabled and resetting is
available (refer to the SC public variable (see page 93)).
92 EIO0000002093 01/2018
ACALC
Public Variables
ACALC_SC_DDT Type
EIO0000002093 01/2018 93
ACALC
94 EIO0000002093 01/2018
PlantStruxure General Purpose Library for Unity
AALARM
EIO0000002093 01/2018
Chapter 11
AALARM - Analog Alarms
Overview
This chapter describes the AALARM DFB.
EIO0000002093 01/2018 95
AALARM
Description
General
The AALARM DFB is used to evaluate detected timed alarms associated with an analog signal.
The DFB provides detected alarm functions by level (very high, high, low and/or very low) and by
deviation in relation to a set-point value.
This evaluation can be activated/deactivated individually according to the specific needs of the
process both from the continuous and sequential control strategies implemented in the controller
as well as from the monitoring system.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Level alarm Evaluates detected timed alarms by level. The detected alarm connection can
be timed. Timing and/or hysteresis can be applied to the disconnection.
Deviation Evaluates the detected alarm for maximum deviation in relation to a set-point.
alarm
Enabling The DFB allows detected alarm monitoring to be enabled/disabled
individually.
96 EIO0000002093 01/2018
AALARM
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
EIO0000002093 01/2018 97
AALARM
Inputs
98 EIO0000002093 01/2018
AALARM
AALARM_CFG Type
EIO0000002093 01/2018 99
AALARM
Outputs
NOTE: Each detected alarm is timed independently according to the configuration of the TONSP
(for detected alarm activation) and TOFFSP (for detected alarm deactivation) inputs. For
disconnection purposes, the configured hysteresis is also considered.
Inputs/Outputs
Public Variables
AALARM_SC_DDT Type
Chapter 12
AINPUT - Analog Input Conditioning
Overview
This chapter describes the AINPUT DFB.
Description
General
The AINPUT DFB is used for conditioning an analog signal that usually comes from a physical
input.
The DFB provides linear scaling, cut-off, diagnosis, and simulation functions.
You can supplement AINPUT with two other DFBs of the General Purpose library:
AALARM: Allows you to incorporate functions to evaluate the alarms associated with the
measurement.
ACALC: Allows you to incorporate calculations on the analog input.
Function Description
The main functions of the DFB are described in the table:
Function Description
Scaling The DFB scales the input signal (usually in raw data) to engineering units through a linear
function.
Cut-Off You can configure a minimum value, which is called the cut-off value. If the measured value
received from the transmitter is below the cut-off value, the measured value is non-useable.
In such case, the cut-off value is being considered.
Diagnosis The DFB manages the diagnostic status of the signal if the peripherals used provide the
signal, and assigns the value that is to be used if the signal is not working properly.
Simulation You can configure the DFB to allow you to enter the value that needs to be used (in
engineering units).
This option enables you to conduct tests on the programming associated with the DFB from
the Supervision system.
External PV The DFB enables you to connect a signal that is already in engineering units (and therefore
does not need scaling, diagnosis, or cut-off operations) while maintaining the simulation
function.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
The table describes how the DFB calculates the measurement value PV based on the value of the
inputs and the AINPUT_ST input/output:
If the resulting value of the calculation is less than cut-off (and the signal comes from the CHIN
input), the PV output is matched to the LOPV input.
Inputs/Outputs
AINPUT_ST_DDT Type
AINPUT_CFG_DDT Type
Public Variables
AINPUT_SC_DDT Type
Chapter 13
AINPUT1 - Configurable-Range Analog Input Conditioning
Overview
This chapter describes the AINPUT1 DFB.
Description
General
The AINPUT1 DFB is used to condition an analog signal normally coming from a physical input. In
contrast to the AINPUT, the AINPUT1 DFB allows you to configure the corresponding range from
the Supervision system.
The DFB provides linear scaling, cut-off, diagnosis, and simulation functions.
You can supplement AINPUT1 with two other DFBs of the General Purpose library:
AALARM: Allows you to incorporate functions to evaluate the alarms associated with the
measurement.
ACALC: Allows you to incorporate calculations on the analog input.
Function Description
The main functions of the DFB are described in the table:
Function Description
Scaling The DFB scales the input signal (usually in raw data) to engineering units by using a linear
function.
You can configure the signal range externally (normally through the Supervision system)
within the range that is configured in the program, which is running in the controller. Enter
values in engineering units.
Cut-Off You can configure a minimum value, which is called the cut-off value. If the measured value
received from the transmitter is below the cut-off value, the measured value is non-useable.
In such case, the cut-off value is being considered.
You can configure the cut-off value externally; normally through the Supervision system.
Enter a value in engineering units within the range that is configured in the program, which
is running in the controller
Diagnosis The DFB manages the diagnostic status of the signal if the peripherals used provide this
signal and assigns the value that is to be used if the signal is not working properly.
You can externally configure the value (normally through the Supervision system) that is to
be used if the signal is not working properly. Enter a value in engineering units within the
range that is configured in the program, which is running in the controller.
Simulation You can configure the DFB to allow you to enter the value that needs to be used (in
engineering units).
This option enables you to conduct tests on the programming associated with the DFB from
the Supervision system.
External PV The DFB allows you to connect a signal that is already in engineering units (and therefore
does not need scaling, diagnosis, or cut-off operations) while maintaining the simulation
function.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
The table describes how the DFB calculates the measurement value PV based on the value of the
inputs and the AINPUT1_ST input/output:
If the resulting value of the calculation is less than AINPUT1_CFG.CUTOFFPV (and the signal
comes from the CHIN input), the PV output is set to match the AINPUT1_CFG.CLOPV input/output.
Inputs/Outputs
AINPUT1_ST_DDT Type
AINPUT1_CFG_DDT Type
Public Variables
AINPUT1_SC_DDT Type
Chapter 14
ALINEAR - Linear Interpolation
Overview
This chapter describes the ALINEAR DFB.
Description
General
The ALINEAR DFB is used to transform a signal by means of a linear characterization function.
The characterization function is defined with the use of points (up to 5).
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Chapter 15
AOUTPUT - Analog Output Conditioning
Overview
This chapter describes the AOUTPUT DFB.
Description
General
The AOUTPUT DFB is used to condition an analog signal usually associated with a physical output.
The DFB provides linear scaling, interlocking, diagnosis, and owner management functions.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Scaling The DFB scales the input signal in engineering units (for example, %) to raw data through a
linear function.
Diagnosis The DFB manages the diagnostic status of the signal if the periphery used provides the signal.
Interlocking The DFB enables to move to the defined position if an active interlock that requires this move
is detected. An interlocking bypass function is available.
Owner The DFB manages control system level, which is the owner (Operator or Program). As a
result, it is responsible for setting the set-point to the desired position.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
> LOSP and < HISP Is calculated with the following linear formula.
>= HISP HIRAW
SP REAL Current set-point.
Set-point calculation based on the value of the input value and the AOUTPUT_ST
input/output is detailed in the following table:
OWNER (OFF: Program, ON: REM SP
Operator)
OFF OFF SC.LSP
OFF ON RSP
ON - AOUTPUT_CFG.LSP
OP REAL Output in engineering units.
Set-point calculation based on the SC.ILCKD public variable value is detailed in the
following table:
SC.ILCKD OP
ON ILCKSP
OFF SP
TRACK BOOL Determines whether the remote set-point (RSP input) is one being considered (0) or
not (1) for the CHOUT output calculation.
1 = Report whether the control loop is open to the algorithm connected to the RSP
input (for example, a PID) so that it can readjust itself based on the output that is
really taking place (the one present at the OP output).
ILCKD OWNER REM TRACK is calculated
as:
ON - - ON
OFF OFF OFF ON
OFF OFF ON OFF
OFF ON - ON
Inputs/Outputs
AOUTPUT_ST_DDT Type
AOUTPUT_CFG_DDT Type
Public Variables
AOUTPUT_SC_DDT Type
Chapter 16
AOUTPUTLP - Local Panel for Analog Output Conditioning
Overview
This chapter describes the AOUTPUTLP DFB.
Description
General
The main objective of the AOUTPUTLP DFB is to manage a local panel that controls an analog
output implemented by means of an AOUTPUT function DFB.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Mode Switch Optionally manages the signals coming from an operating mode switch in a local
panel with the following configuration: Local - Zero - Control System. The Zero mode
signal is optional. However the user can enable Local/Control System mode from the
faceplate also, when VirtualLPEN input pin signal is high and MODESignalsEN
signal is low in the DFB.
Push buttons The DFB manages up to two signals coming from OPEN and CLOSE push buttons
giving the CLOSE push button signal higher priority.
Owner Management The DFB enables to configure whether the Program needs to be the analog output
owner or not, after switching to the Control System mode again.
Owner Locking The DFB enables to configure whether the monitoring (HMI) system needs to block
access to the drop-down list or not. It disables to change the owner
(Operator/Program) while the analog output is controlled from the Local Panel.
Set-point Lock The DFB enables to configure whether or not the monitoring (HMI) system needs to
block access to the drop-down list or not. It disables to change the set-point
(Operator/Program) while the analog output is controlled from the Local Panel.
Push button The push buttons on the Local Panel can be enabled/disabled through the DFB
Enabling/Disabling configuration (input pin) and/or from control sequences.
Enabled Panel The DFB provides a signal that can be used to illuminate a light source on the Local
Signaling Panel to indicate when the push buttons are enabled for operation.
Virtual Panel This signal enables the operator to select the Local/Control System mode of
Enabling/Disabling operation from the HMI so that the push button signals are enabled for operation.
NOTE: VirtualLPEN input pin signal is applicable when PlantStruxure General
Purpose Library for Unity is used along with PlantStruxure General Purpose Library
for WSP.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
AOUTPUT_CFG.DDT Type
AOUTPUT_ST.DDT Type
AOUTPUTLP_ST.DDT Type
AOUTPUT_ST.CFGW Word
The following table describes the AOUTPUT_ST.CFGW word:
AOUTPUTLP_ST.CFGW Word
AOUTPUTLP_ST.STW Word
Read-only access. Status word. The following table describes the AOUTPUTLP_ST.STW word:
Public Variables
AOUTPUTLP_SC_DDT Type
Chapter 17
DCALC - Digital Calculation
Overview
This chapter describes the DCALC DFB.
Description
General
The DCALC DFB is used to perform calculations based on a digital signal; the calculations
performed are frequency and totalizing calculations.
The DFB memorizes up to 20 time samples with rising edges in the measurement (PV - Present
Value) based on which the calculations are performed.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Frequency The frequency at which the input signal oscillates is calculated.
Totalizing The totalization is calculated by counting pulses and scaling to engineering units.
NOTE: The function block uses the FREERUN function for time calculations. Therefore, the DCALC
DFB is only available if the controller CPU supports this function.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Where:
KFREQ Conversion factor applied to the frequency calculation. Refer to the KREQ input
(see page 150).
n Number of samples (up to 20 after the whole internal sample table is loaded).
t Relative time elapsed from the first edge to the corresponding edge.
Public Variables
DCALC_SC_DDT Type
Chapter 18
DINPUT - Digital Input Conditioning
Overview
This chapter describes the DINPUT DFB.
Description
General
The DINPUT DFB is used to condition a digital signal usually coming from a physical input.
The DFB provides timing functions for the connection and/or disconnection, simulation, and can
use the signal status as an alarm function.
Function Description
The main functions of the DFB are described in the table:
Function Description
Timing The input signal is timed to evaluate an output logic signal that
absorbs rapid changes in the input signal.
Alarm You can enable/disable the evaluation of an alarm and indicate the
status that needs to be considered for the alarm. .
You need to incorporate an external logic to evaluate this alarm.
Diagnosis The DFB manages the diagnostic status of the signal if the
peripherals used provide it and assigns the value that is to be used if
the signal is not working properly.
Simulation You can configure the DFB to allow you to enter the value that needs
to be used (in engineering units).
This option enables you to conduct tests on the programming
associated with the DFB from the Supervision system.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
DINPUT_ST_DDT Type
Public Variables
DINPUT_SC_DDT Type
Chapter 19
DOUTPUT - Digital Output Conditioning
Overview
This chapter describes the DOUTPUT DFB.
Description
General
The DOUTPUT DFB is used to condition a digital signal usually associated with a physical output.
The DFB provides interlocking, diagnosis, and owner management functions.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Diagnosis The DFB manages the diagnostic status of the signal if the periphery used provides it.
Interlocking The DFB enables to move to the defined position if an active interlock that requires
this move is detected. An interlock bypass function is available.
Owner The DFB manages control system level, which is the owner (Operator or Program).
As a result, it is responsible for setting the set-point to the desired position.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
DOUTPUT_ST_DDT Type
Public Variables
DOUTPUT_SC_DDT Type
Chapter 20
MAINPUT1 - Conditioning of Multiple Analog Inputs with Configurable Range
Overview
This chapter describes the MAINPUT1 DFB.
Description
General
The MAINPUT1 DFB is used to condition up to four analog signals normally coming from physical
inputs and allows selecting one of them based on the chosen criterion. You can configure the range
from the Supervision system.
The DFB provides linear scaling, cut-off, diagnosis, and simulation functions.
You can supplement MAINPUT1 with two other DFBs of the General Purpose library:
AALARM: Allows you to incorporate functions to evaluate the alarms associated with the
measurement.
ACALC: Allows you to incorporate calculations on the analog input.
Function Description
The main functions of the DFB are described in the table:
Function Description
Scaling Scales the input signals (normally in raw data) to engineering units by using a linear function.
You can configure the range of the signals externally (normally from the Supervision system)
within the range that is configured in the program, which is running in the controller. Enter
values in engineering units.
Cut-Off You can configure a minimum value, which is called the cut-off value. If the measured value
received from the transmitter is below the cut-off value, the measured value is not useable.
In such case, the cut-off value is considered.
You can configure the cut-off value externally; normally through the Supervision system.
Enter a value in engineering units within the range that is configured in the program, which
is running in the controller
Diagnosis The DFB manages the diagnostic status of the signal if the peripherals used provide this
signal, and assigns the value that is to be used if the signal is not working properly.
You can configure the value (normally through the Supervision system) that is to be used if
the signal is not working properly externally. Enter a value in engineering units within the
range that is configured in the program, which is running in the controller.
Simulation You can configure the DFB to allow you to enter the value that needs to be used (in
engineering units).
This option enables you to conduct tests on the programming associated with the DFB from
the Supervision system.
Selection The DFB allows you to select one analog signal among the input signals based on one of
the following criteria:
Priority
Direct selection
Median
Average
Minimum
Maximum
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
If the resulting value of the calculation is less than MAINPUT1_CFG.CUTOFFPV (and the signal
comes from the CHINx input), the PVx output is set to match the MAINPUT1_CFG.CLOPV
input/output.
Inputs/Outputs
MAINPUT1_ST_DDT Type
MAINPUT1_CFG_DDT Type
Public Variables
MAINPUT1_SC_DDT Type
Chapter 21
STAHL
STAHL
Overview
This chapter describes the DFBs to process data of modules of the STAHL IS1 Remote
I/O system.
Section 21.1
STAHLAI8CH for STAHL 8-Channel Analog Input Modules
Overview
This section describes the STAHLAI8CH DFB.
Description
General
The STAHLAI8CH DFB allows reading analog input signal values and signal quality data of STAHL
8-channel analog input modules.
DFB Representation
Representation
The following figure shows the STAHLAI8CH DFB as it appears in an FBD section:
Inputs
Outputs
Section 21.2
STAHLAO8CH for STAHL 8-Channel Analog Output Modules
Overview
This section describes the STAHLAO8CH DFB.
Description
General
The STAHLAO8CH DFB allows writing the analog output signal value to STAHL 8-channel analog
output modules. It also reads the signal quality data from each channel.
DFB Representation
Representation
The following figure shows the STAHLAO8CH DFB as it appears in an FBD section:
Inputs
Outputs
Section 21.3
STAHLDI16CH for STAHL 16-Channel Digital Input Modules
Overview
This section describes the STAHLDI16CH DFB.
Description
General
The STAHLDI8CH DFB allows reading the digital input signal value and signal quality data of
STAHL 16-channel digital input modules.
DFB Representation
Representation
The following figure shows the STAHLDI16CH DFB as it appears in an FBD section:
Inputs
Outputs
Section 21.4
STAHLDO8 for STAHL 8-Channel Digital Output Modules
Overview
This section describes the STAHLDO8CH DFB.
Description
General
The STAHLDO8CH DFB allows writing digital output signal values to STAHL 8-channel digital output
modules. It also reads the signal quality data from each channel.
DFB Representation
Representation
The following figure shows the STAHLDO8CH DFB as it appears in an FBD section:
Inputs
Outputs
Section 21.5
STAHLHARTVal4 - Processing of Four HART Values
Overview
This section describes the STAHLHARTVal4 DFB.
Description
General
The STAHLHARTVal4 DFB allows processing four HART values through a STAHL 8-channel
analog input module HART. For each HART value, the DFB converts the high and low register
values into one output value of data type Real.
DFB Representation
Representation
The following figure shows the STAHLHARTVal4 DFB as it appears in an FBD section:
Inputs
Outputs
Section 21.6
STAHLHARTVal8 - Processing of Eight HART Values
Overview
This section describes the STAHLHARTVal8 DFB.
Description
General
The STAHLHARTVal8 DFB allows processing eight HART values through a STAHL 8-channel
analog input module HART. For each HART value, the DFB converts the high and low register
values into one output value of data type Real.
DFB Representation
Representation
The following figure shows the STAHLHARTVal8 DFB as it appears in an FBD section:
Inputs
Outputs
Chapter 22
TOTAL - Totalizing Function
Overview
This chapter describes the TOTAL DFB.
Description
General
The objective of TOTAL block is to perform totalizer calculation based on 3 inputs (analog signal,
digital pulses, counter).
Function Description
The main functions of the DFB are described in the following table:
Function Description
Control Controls start and stop of totalization of the input from field
equipment/instrument.
Owner selection The DFB manages the control system level, as to which is the owner (operator
or program). As a result, it is responsible for setting the setpoint for the desired
position.
Totalizing The totalization is done using trapezoidal rule algorithm for analog inputs,
while it is summation for digital as well as counter values.
Monitoring Enables the user to monitor the totalized value, last totalized value, setpoint
and active operation state.
Processing states and The DFB processes the commands received from Supervision function and
Commands determines the active operation state.
Local and remote setpoint Enables to monitor totalized value with the setpoint that is determined through
a setpoint selector (local or remote). The local set-point is assigned to the
sequential control or to command received from the monitoring system. At the
same time, remote setpoint is assigned to DFB control from the logic
implemented in continuous control.
State Chart
State chart explains the totalization operation
Command State
DFB initialization IDLE
Start IDLE → RUNNING
Hold RUNNING → HELD
HELDFORERROR → HELD
FAIL Input Pin Last Active State Command Current Active State
Value
0 IDLE Start RUNNING
0 RUNNING Hold HELD
0 RUNNING Stop STOPPED
0 HELD Restart RUNNING
0 STOPPED Reset IDLE
1 IDLE Start HELDFORERROR
1 RUNNING - HELDFORERROR
1 HELDFORERROR Hold HELD
1 HELDFORERROR Stop STOPPED
1 HELD - HELD
1 STOPPED - STOPPED
1 STOPPED Reset IDLE
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller
Inputs
For example,
Case 1
SCANRATE = 1s
Constant flow rate = 1 Litre per hour at 9.00 AM.
Case 2
Scanrate = 500ms
Constant Flow rate = 1 Litre per hour at 9.00 AM.
User wants to see totalized value in Litres at 11.00 AM.
AuxTotal is considered to be internal variable. Total is the output
of DFB.
AuxTotal = 14400 [(L× 500ms)/hr.]
K to be configured as (millisecond/hour).
[(500 × 0.001)/3600] = 0.000139
Total = AuxTotal × K
Total = 14400 × 0.000139
Total=2 Litres.
NOTE: Priorities are set based on the inputs that are selected for totalization.
Default priorities set for the inputs:
PVFLOW = 0
PVPULSE = 1
PVCOUNT_UDINT = 2
PVCOUNT_UINT = 3
Lower the value, higher the priority, that is, 0 is the maximum priority. If more than one input is
connected, detected configuration error occurs. During detected configuration error, totalization
continues without any interruption based on the priorities of inputs that are set. Only during IDLE
state the user can change the input priorities.
Outputs
SP Calculation
Inputs/Outputs
TOTAL_ST_DDT Type
TOTAL_CFG_DDT Type
Public Variables
TOTAL_SC_DDTType
Part III
On/Off Device Control
Overview
This part provides a detailed description of the functions, pins, pin layout, and variables of the
function blocks of the on/off device control family.
These function blocks do not reflect any specific installation.
WARNING
LOSS OF CONTROL
Perform a Failure Mode and Effects Analysis (FMEA) of your application, and apply preventive
and detective controls before implementation.
Provide a fallback state for undesired control events or sequences.
Provide separate or redundant control paths wherever required.
Supply appropriate parameters, particularly for limits.
Review the implications of transmission delays and take actions to mitigate.
Review the implications of communication link interruptions and take actions to mitigate.
Provide independent paths for control functions (for example, emergency stop, over-limit
conditions, and fault conditions) according to the safety analysis and applicable codes, and
regulations.
Apply local accident prevention and safety regulations and guidelines. 1
Test each implementation of this library for proper operation before placing it into service.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
1For additional information, refer to NEMA ICS 1.1 (latest edition), Safety Guidelines for the
Application, Installation, and Maintenance of Solid State Control and to NEMA ICS 7.1 (latest
edition), Safety Standards for Construction and Guide for Selection, Installation and Operation of
Adjustable-Speed Drive Systems or their equivalent governing your particular location.
Chapter 23
DEVCTL - On-Off Device
Overview
This chapter describes the DEVCTL DFB.
Description
General
The DEVCTL DFB is used to manage on-off device-type control modules, such as on-off actuated
valves and discrete motors (without variable-frequency drives).
The DFB allows management of the associated devices from the sequential control, the continuous
control, and/or the monitoring subsystem. It depends on their configuration and the system needs.
Likewise, you can supplement the DFB with the DEVMNT DFB from the General Purpose Library.
This allows the incorporation of totalizing functions for operating hours and switching operations.
Thus, the maintenance of the device is facilitated.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Control Controls the digital control signal of the element based on the configuration and the
commands that the DFB receives according to the functions.
Position detection Between 0 and 2 limit switches or digital detectors (configurable) that enables to
determine the actual position of the element to be controlled and monitored.
Local and remote Enables to control the DFB with a setpoint that is determined through a setpoint
setpoint selector (local or remote). The local set-point is assigned to the sequential control or
to the command received from the monitoring system. At the same time, the remote
setpoint is assigned to the DFB control from the logic implemented in the continuous
control.
Interlocking The DFB gives the device a command to move to the defined position if an active
interlock that requires this move is detected. An interlock bypass function is available.
Owner selection The DFB manages the control system level, which is the owner (Operator or
Program). As a result, it is responsible for setting the setpoint for the desired position.
Simulation The DFB can be switched to simulation mode. Thus, the actual position of the
controlled device is considered to be the same as its desired position regardless of
the signals received from the position detectors.
The optional functions of the DFB are described in the following table:
Function Description
Inoperable device A digital signal that enables to determine if the control DFB is not operational in
monitoring.
Commonly used for detecting whether or not the motor switch tripped due to thermal
overload.
Detection of not Detected error confirmation monitoring can be activated after a configurable time is
confirmed operation elapsed.
Manual resetting Allows you to configure the device to move to its position and reset manually after the
detection of an inoperable device condition or a not confirmed operation.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
OP Calculation
The evaluation of the device control depending on the interlock status, the current set-point, and if
the DFB requires resetting is shown in the following table:
WARNING
UNINTENDED EQUIPMENT OPERATION
The CONFREARMEN pin has to be set to 1 for the OP pin to become 0, under non-confirmed
operations.
The FAILREARMEN pin has to be set to 1 for the OP pin to become 0, under detected fail
conditions.
Changes to the configuration of these parameters have to be performed by competent
personnel only.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
FAILEN input FAILREARMEN input OP output when FAIL = 1 OP output when FAIL = 1 (assume
(assume OP = 1 before the OP = 0 before the detected failure)
detected failure)
0 0 1 0
0 1 1 0
1 0 1 0
1 1 0 0
SP Calculation
The signal evaluation depending on the SC.REM and RSP inputs and the
DEVCTL_ST.CFGW.OWNER input/output is shown in the following table:
ZSHPOS Calculation
The signal evaluation depending on the ZSHEN and ZSLEN inputs and the
DEVCTL_ST.CFGW.SIMMD input/output is shown in the following table:
ZSLPOS Calculation
The signal evaluation depending on the ZSHLEN and ZSLEN inputs and the
DEVCTL_ST.CFGW.SIMMD input/output is shown in the following table:
FAILD Calculation
The signal evaluation depending on the FAIL and FAILEN inputs is shown in the following table:
AAlarm Behavior
Monitoring is carried out on the detector signals after they have been evaluated (ZSHPOS and
ZSLPOS) according to the DFB configuration. It is activated when the control signal (OP output)
switches (0 to 1 or 1 to 0) as long as the timer preselection value is greater than 0 (TIMEOUT input
in msec) and the device is not being controlled externally (EXTCTLD to 1). After the control signal
switching has occurred, the DFB internal timer is activated. As long as the timer is running, the
position of the device is not monitored. Once the time has elapsed, inoperable device condition
causes the alarm to be activated.
The detected error signal is maintained for a minimum of SCANTIME (msec). After the time has
elapsed, the signal is recovered in the following conditions:
If the detectors position (HIGHPOS and LOWPOS) becomes the desired position (according to the
OP value) or
If the device is reset (through the DEVCTL_ST.CFGW.REARM input/output, and as long as the
CONFREARMEN input is 1)
In both cases, the internal timer is restarted with the TIMEOUT value.
Inputs/Outputs
DEVCTL_ST_DDT Type
9 EXTCTLD Device status. Read-only access. Refer to EXTCTLD input pin (see page 235).
NOTE: The outputs (SP and OP) are de-energized when the device is in an out-of-service state
even if an interlock that requests the device to be started is active.
Public Variables
DEVCTL_SC_DDT Type
Chapter 24
DEVLP - Local Panel for Controlling On-Off Devices
Overview
This chapter describes DEVLP DFB.
Description
General
The DEVLP DFB is used to manage a local panel that controls an on-off device (for example, an
on-off motor) implemented with a DEVCTL (device control) function DFB and with signals that are
connected to the controller so that the latter defines the target position of the device.
Function Description
The main functions of the module are described in the following table:
Function Description
Mode Switch Optionally manages the signals coming from an operating mode switch in a local
panel with the following configuration: Local - Zero - Control System. The Zero mode
signal is optional. However the user can enable Local/Control System mode from the
faceplate also, when VirtualLPEN input pin signal is high and MODESignalsEN
signal is low in the DFB.
Push buttons The DFB manages up to two signals coming from OFF and ON push buttons of local
panel, giving the OFF push button higher priority.
Owner Management The DFB enables to configure whether the Program needs to be the device owner or
not, after switching to the Control System mode again.
Owner Locking The DFB enables to configure whether the monitoring (HMI) system needs to block
access to the drop-down list or not, it disables the access to change the owner
(Operator/Program) while the device is controlled from the Local Panel.
Set-point Lock The DFB enables to configure whether the monitoring (HMI) system needs to block
access to the drop-down list or not. It disables to change the set-point while the
device is controlled from the Local Panel.
Push button The push button signals from the Local Panel can be enabled/disabled through the
Enabling/Disabling DFB configuration (input pin) and/or from control sequences.
Enabled Panel The DFB provides a signal that can be used to illuminate a light source on the Local
Signaling Panel to indicate when the push buttons are enabled for operation.
Virtual Panel This signal enables the operator to select the Local / Control System mode of
Enabling/Disabling operation from the HMI so that the push button signals are enabled for operation.
NOTE: VirtualLPEN input pin signal is applicable when PlantStruxure General
Purpose Library for Unity is used along with PlantStruxure General Purpose Library
for WSP.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
DEVCTL_ST.CFGW Type
The following table describes the logic applied to the signals controlled from the DEVLP DFB:
DEVCTL_ST.CFGW Word
The following table describes the DEVCTL_ST.CFGW word:
DEVLP_ST.CFGW Word
DEVLP_ST_DDT Type
DEVLP_ST.STW Word
Read-only access. Bits word with input conditions (refer to the CONDxx inputs) and their evaluation
summary (refer to the ILCK output). The following table describes the DEVLP_ST.STW word:
Public Variables
DEVLP_SC_DDT Type
Chapter 25
DEVMNT - On-Off Device Maintenance
Overview
This chapter describes the DEVMNT DFB.
Description
General
The DEVMNT DFB is used to provide data that is useful for device maintenance.
You can use this DFB as a supplement to the DEVCTL DFB or independently. This DFB allows the
incorporation of totalizing functions for hours of operation and switching operations.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Switching Operation Counts the number of switching operations that have been performed
Totalization on the device since the totalizer last reset.
Hours of Operation Counts the number of hours of operation that the device has been in
Totalization operation since the totalizer last reset.
Reset The DFB allows to reset the described totalizers individually.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
DEVMNT_ST_DDT Type
Public Variables
DEVMNT_SC_DDT Type
Chapter 26
DUALOP - Dual Output
Overview
This chapter describes the DUALOP DFB.
Decription
General
The DUALOP DFB is used to manage start/stop or open/ close of the devices. The control function
DUALOP can be connected with DEVCTL (device control) to generate two outputs based on one
logical input.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Single input to dual output The DFB can generate two outputs based on one logical input.
Operating modes The DFB provides five operating modes that facilitate various application
requirements by using the device output and limit switches. The DFB outputs
can be continuous or pulse type depending on the mode selection.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Mode 1: Pulse based on continuous input signal (pulse type start/open or stop/close
command).
When input OP is set to true, OPH is set to true for the defined pulse duration
(OPHPulseTime).
When input OP is set to false, OPL is set to true for the defined pulse duration
(OPLPulseTime).
Outputs (OPH or OPL) should always follow the state of input (OP) signal condition.
After initialization, outputs are triggered based on the input signal.
Mode 2: Pulse based on input rising/falling trigger (pulse type start/open or stop/close
command).
When input OP is set to true, OPH is set to true for the defined pulse duration
(OPHPulseTime).
When input OP is set to false, OPL is set to true for the defined pulse duration
(OPLPulseTime).
After initialization, outputs (OPH or OPL) are set to low. The outputs are triggered by getting
new command/transition in the input.
Mode 3: Till position is confirmed (release the start/open or stop/close command once the
position is reached).
When input OP is set to true, OPH is set to true until the high position (ZSHPOS) is reached.
When input OP is set to false, OPL is set to true until the low position (ZSLPOS) is reached.
After initialization, outputs (OPH or OPL) are triggered based on the input signal and
position feedback signals.
Mode 4: Till position is confirmed + extra time (release the start/open or stop/close command
once the position is reached + extra pulse time to stroke the output)
When input OP is set to true, OPH is set to true until the high position (ZSHPOS) is reached
+ defined pulse time duration (OPHPulsetime).
When input OP is set to false, OPL is set to true until the low position is reached (ZSLPOS)
+ defined pulse time duration (OPLPulsetime).
After initialization, outputs (OPH or OPL) are triggered based on the input signal and
position feedback signals.
NOTE: For invalid entry of Mode (for example, Mode < 0 or Mode > 4) the DFB defaults to
Mode 0.
Switch- TIME This input is used to set a delay between output switching. Default value will be 0 seconds. For
Delay the delay duration set in this input, both the outputs will be low. Then after the delay, output (OPH
or OPL) gets triggered based on the selected mode and input signal condition.
Outputs
Chapter 27
HVALVE - Manual Valve
Overview
This chapter describes the HVALVE DFB.
Description
General
The main objective of the HVALVE DFB is to manage valves without actuators and with 1 or 2 limit
switches or any other type of positioner with 2 final positions.
You can supplement this DFB with DINPUT DFBs from the General Purpose Library. It enables you
to incorporate conditioning functions for the digital signals of the limit switches.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Position Detection A total of 1 to 2 limit switches that enable to determine the actual
position of the valve are monitored.
Simulation The DFB enables you to simulate the position of the valve.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
HVALVE_ST_DDT Type
Public Variables
HVALVE_SC_DDT Type
Chapter 28
MOTOR2 - 2-Speed/2-Rotation Direction Motor
Overview
This chapter describes the MOTOR2 DFB.
Description
General
The MOTOR2 DFB is used to control on-off motors with 2 rotation directions (forward/reverse) or
with 2 speeds (for example, slow speed and fast speed).
The DFB allows the management of associated motors from the sequential control, the continuous
control, and/or the Supervision system depending on their configuration and the system needs.
Likewise, you can supplement this DFB with the DEVMNT DFB from the General Purpose Library.
This allows the incorporation of totalizing functions for hours of operation and number of switching
operations. Thus, the maintenance of the motor is facilitated.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Control Controls the digital control signal of the element based on the configuration and
commands that the DFB receives according to the functions.
Position detection Up to 2 running digital confirmation signals (configurable) that allow to determine the
actual statuses of the switching operation of the element to be controlled are
monitored.
Inoperable motor Up to 2 digital signals (configurable), which enables to determine whether or not the
control module has changed, are monitored.
Commonly used for detecting whether or not the switch of the motor switch has
tripped due to thermal overload.
Local and remote Enables the DFB to be controlled through setpoints (stop/run and speed/rotation
setpoint direction) that are determined through a selector (local or remote). The local set-
points are assigned to the sequential control or to the commands received from the
monitoring system while the remote setpoints are assigned to the DFB control from
the logic implemented in the continuous control.
Setpoint blocking You can configure the DFB to avoid the activation of a certain setpoint (rotation
direction or speed) depending on the conditions evaluated outside the DFB (for
example, to avoid reverse speeds from being activated when the motor is already
rotating in the forward direction).
Interlocking The DFB gives the motor the command to move to the defined position if an active
interlock requiring this move is detected. An interlock bypass function is available.
Owner selection The DFB manages control system level, which is the owner (operator or program).
As a result, it is responsible for setting the setpoint for the desired position.
Simulation You can switch the DFB to Simulation mode. Thus, the operation confirmations for
the controller motor are considered to be the same as the desired confirmations
regardless of the actual signals for detection of not confirmed operation and
inoperable device.
The optional functions of the DFB are described in the following table:
Function Description
Detection of not You can activate detected error confirmation monitoring after a
confirmed operation configurable time is passed.
Manual resetting Allows configuring the motor to move to its inactive position (de-
energized outputs) and to manually reset after the detection of an
inoperable device condition or a not confirmed operation.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
When STW.8 is ON, OP1 and OP2 are OFF. When STW.8 is OFF and ILCKD is OFF, the following
table shows the status of OP1 and OP2:
WARNING
UNINTENDED EQUIPMENT OPERATION
The CONFREARMEN pin has to be set to 1 for the OPx (x = 1 or 2) pin to become 0, under non-
confirmed operations.
The FAILREARMEN pin has to be set to 1 for the OPx (x = 1 or 2) pin to become 0, under
detected fail conditions.
Changes to the configuration of these parameters have to be performed by competent
personnel only.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
FAILEN input FAILREARMEN input OPx output when FAIL = 1 OPx output when FAIL = 1
(assume OP = 1 before the (assume OP = 0 before the
detected failure) detected failure)
0 0 1 0
0 1 1 0
1 0 1 0
1 1 0 0
NOTE: x=1 or 2
The following table shows how the ILCKD variable is calculated in the public variables section:
The evaluation of the motor position depending on the configuration implemented with the ZSH1EN
and ZSL2EN inputs and on the MOTOR2_ST.CFGW.SIMMD input/output is shown in the following
table:
ALARM1 Output
This variable is a boolean.
Indicates if the detection of a not confirmed operation has occurred on device 1. Monitoring is done
on operation confirmation signals.
Based on the DFB configuration, it is activated when the control signal (OP1 output) is switched (0
to 1 or 1 to 0) as long as the timer preselection value is greater than 0 (TIMEOUT input in msec)
and the device is not being controlled externally (EXTCTLD to 1).
After the control signal is switched, the DFB internal timer is activated.
As long as the timer is running, the operation confirmations are not monitored. When the time has
elapses, any detection of not confirmed operation causes the alarm to be generated. The detected
alarm is also activated if the UNPOS signal is active after the TIMEOUT time has elapsed (msec).
The detected error signal is maintained for a minimum of SCANTIME (msec).
After the time has elapsed, the alarm is deactivated based on the following conditions:
if the operation confirmation signal becomes the desired signal (according to the OP1 value) or
if the motor is reset (through the MOTOR2ST.CFGW.REARM input/output, and as long as the
CONFREARMEN input is 1).
In both cases, the internal timer is restarted with the TIMEOUT value.
ALARM2 Output
This variable is a boolean.
Indicates if the detection of a not confirmed operation has occurred on device 2. Monitoring is done
on operation confirmation signals.
Based on the DFB configuration, it is activated when the control signal (OP2 output) is switched (0
to 1 or 1 to 0) as long as the timer preselection value is greater than 0 (TIMEOUT input in msec)
and the device is not being controlled externally (EXTCTLD to 1).
After the control signal is switched, the DFB internal timer is activated. As long as the timer is
running, the operation confirmations are not monitored.
After the time has elapsed, any detection of not confirmed operation causes the alarm to be
generated. The alarm is also activated if the UNPOS signal is active after the TIMEOUT time has
elapsed (msec).
The detected error signal is maintained for a minimum of SCANTIME (msec).
Once the time has elapsed, the detected alarm is deactivated based on the following conditions:
if the operation confirmation signal becomes the desired signal (according to the OP2 value) or
if the motor is reset (through the MOTOR2ST.CFGW.REARM input/output, and as long as the
CONFREARMEN input is 1).
In both cases, the internal timer is restarted with the TIMEOUT value.
The signal evaluation depending on the FAILx and FAILxEN inputs is shown in the following table:
UNPOS Output
The evaluation of the ZSH1POS, ZSH2POS, and UNPOS signals depending on the EXTCTLD,
ZSH1EN and ZSH2EN inputs and the MOTOR2ST.CFGW.SIMMD input/output is shown in the
following table:
Inputs/Outputs
MOTOR2_ST_DDT Type
MOTOR2_ST.STW Word
The following table describes the MOTOR2_ST.STW word:
MOTOR2_ST_DDT.CFGW Word
The following table describes the MOTOR2_ST_DDT.CFGW word:
NOTE: The outputs (SP and OP) are de-energized when the device is in an out-of-service state
even if an interlock that requests the device to be started is active.
Public Variables
MOTOR2_SC_DDT Type
Chapter 29
MOTOR2LP - Local Panel for Controlling 2-Speed/2-Rotation Direction Motors
Overview
This chapter describes the MOTOR2LP DFB.
Description
General
The objective of the MOTOR2LP DFB is to manage a local panel that controls a motor with 2
directions of rotation or 2 speeds. This motor is implemented with a MOTOR2 DFB and with signals
that are wired to the controller so that the latter determines the target position for the device.
Function Description
The main functions of the module are described in the following table:
Function Description
Mode Switch Optionally manages the signals coming from an operating mode switch in a local
panel with the following configuration: Local - Zero - Control System. The Zero mode
signal is optional. However the user can enable Local/Control System mode from the
faceplate also, when VirtualLPEN input pin signal is high and MODESignalsEN
signal is low in the DFB.
Push buttons The DFB manages up to three signals coming from OFF, ON - forward direction of
rotation/speed 1 and ON - reverse direction of rotation/speed two push buttons. The
priority is given to the OFF push button signal and then to the closing (ON) push
button signal.
Owner Management The DFB enables to configure whether the Program needs to be the valve owner or
not, after switching to the Control System mode again.
Owner Locking The DFB enables to configure whether the monitoring (HMI) system needs to block
access to the drop-down list or not, it disables the access to change the owner
(Operator/Program) while the valve is controlled from the Local Panel.
Set-point Lock The DFB enables to configure whether the monitoring (HMI) system needs to block
access to the drop-down list or not. It disables to change the set-point while the
analog output is controlled from the Local Panel.
Push button The push button signals from the Local Panel can be enabled/disabled through the
Enabling/Disabling DFB configuration (input pin) and/or from control sequences.
Enabled Panel The DFB provides a signal that can be used to illuminate a light source on the Local
Signaling Panel to indicate when the push buttons are enabled for operation.
Virtual Panel This signal enables the operator to select the Local / Control System mode of
Enabling/Disabling operation from the HMI so that the push button signals are enabled for operation.
NOTE: VirtualLPEN input pin signal is applicable when PlantStruxure General
Purpose Library for Unity is used along with PlantStruxure General Purpose Library
for WSP.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
MOTOR2_ST.DDT Type
MOTOR2LP_ST.DDT Type
MOTOR2_ST.CFGW Word
The following table describes the MOTOR2_ST.CFGW word:
MOTOR2LP_ST.CFGW Word
MOTOR2LP_ST.STW Word
Read-only access. Status word. The following table describes the MOTOR2LP_ST.STW word:
Public Variables
MOTOR2LP_SC_DDT Type
Chapter 30
MVALVED - Discrete Motorized Valve
Overview
This chapter describes the MVALVED DFB.
Description
General
The MVALVED DFB is designed to control a motorized valve, or a gate, with 2 limit switches (open-
valve and closed-valve) and a 2-rotation-directions-motor based control.
As a result, you can combine the MVALVED DFB with the following Unity Pro components from the
General Purpose Library:
MOTOR2
DINPUT
Function Description
The main functions of the DFB are described in this table:
Function Description
Control Controls the digital control signal of the element based on the configuration and the
commands that the block receives according to the functions that are described below.
Position A total of 0...2 limit switches or digital detectors (configurable) that allow to determine the
detection actual position of the element to be controlled are monitored.
Inoperable Optionally, one digital signal is monitored that allows determining if the control module has
device responded.
Detection of not Optionally, this monitoring function can be activated after a configurable time has elapsed.
confirmed
operation
Manual resetting Optionally, enables you to configure the device to move to its position and require manual
resetting if the device does not respond or when the monitoring function is activated.
Local and Enables the DFB to control the module through a setpoint that is determined with a
remote setpoint setpoint selector (local or remote). The local setpoint is assigned to the sequential control
or to the command received from the Supervision system, while the remote setpoint is
assigned to the module control from the logic implemented in the continuous control.
Interlocking The DFB gives the device the command to move to the defined position if an active
interlock that requires this move is detected. An interlock bypass function is available.
Owner selection The module manages the control system level (operator or program), which is the owner.
As a result, it is responsible for setting the setpoint for the target position.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
WARNING
UNINTENDED EQUIPMENT OPERATION
The CONFREARMEN pin has to be set to 1 for the SP_MOTOR2 pin to become 0, under non-
confirmed operations.
Changes to the configuration of these parameters have to be performed by competent
personnel only.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Inputs/Outputs
MVALVED_ST_DDT Type
MVALVED_ST.STW Type
MVALVED_ST.CFGW Type
Public Variables
MVALVED_SC_DDT Type
Chapter 31
MVALVEDLP - Local Panel for Controlling Motorized On-Off Valves
Overview
This chapter describes the MVALVEDLP DFB.
Description
General
The objective of the MVALVEDLP DFB is to manage a local panel that controls a motorized on-off
valve. This valve is implemented with an MVALVED DFB and with signals that are wired to the
controller so that the latter defines the target position for the device.
Function Description
The main functions of the module are described in the following table:
Function Description
Mode Switch Optionally manages the signals coming from an operating mode switch in a local
panel with the following configuration: Local - Zero - Control System. The Zero mode
signal is optional. However the user can enable Local/Control System mode from the
faceplate also, when VirtualLPEN input pin signal is high and MODESignalsEN
signal is low.
Push buttons The DFB manages up to three signals coming from OFF, OPEN and CLOSE push
buttons. The highest priority is given to the OFF push button signal followed by the
CLOSE push button signal.
Owner Management The DFB enables to configure whether the Program needs to be the valve owner or
not, after switching to the Control System mode again.
Owner Locking The DFB enables to configure whether the monitoring (HMI) system needs to block
access to the drop-down list or not, it disables the access to change the owner
(Operator/Program) while the valve is controlled from the Local Panel.
Set-point Lock The DFB enables to configure whether the monitoring (HMI) system needs to block
access to the drop-down list or not. It disables to change the set-point while the valve
is controlled from the Local Panel.
Push button The push button signals from the Local Panel can be enabled/disabled through the
Enabling/Disabling DFB configuration (input pin) and/or from control sequences.
Enabled Panel The DFB provides a signal that can be used to illuminate a light source on the Local
Signaling Panel to indicate when the push buttons are enabled for operation.
Virtual Panel This signal enables the operator to select the Local / Control System mode of
Enabling/Disabling operation from the HMI so that the push button signals are enabled for operation.
NOTE: VirtualLPEN input pin signal is applicable when PlantStruxure General
Purpose Library for Unity is used along with PlantStruxure General Purpose Library
for WSP.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
MVALVED_ST.DDT Type
MVALVEDLP_ST.DDT Type
MVALVE_ST.CFGW Word
The following table describes the MVALVED_ST.CFGW word:
MVALVEDLP_ST.CFGW Word
MVAVEDLP_ST.STW Word
Read-only access. Status word. The following table describes the MVALVEDLP_ST.STW word:
Public Variables
MVALVEDLP_SC_DDT Type
Part IV
Analog Device Control
Overview
This part provides a detailed description of the functions, pins, pin layout, and variables of the
function blocks of the analog device control family.
These function blocks do not reflect any specific installation.
WARNING
LOSS OF CONTROL
Perform a Failure Mode and Effects Analysis (FMEA) of your application, and apply preventive
and detective controls before implementation.
Provide a fallback state for undesired control events or sequences.
Provide separate or redundant control paths wherever required.
Supply appropriate parameters, particularly for limits.
Review the implications of transmission delays and take actions to mitigate.
Review the implications of communication link interruptions and take actions to mitigate.
Provide independent paths for control functions (for example, emergency stop, over-limit
conditions, and fault conditions) according to the safety analysis and applicable codes, and
regulations.
Apply local accident prevention and safety regulations and guidelines. 1
Test each implementation of this library for proper operation before placing it into service.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
1For additional information, refer to NEMA ICS 1.1 (latest edition), Safety Guidelines for the
Application, Installation, and Maintenance of Solid State Control and to NEMA ICS 7.1 (latest
edition), Safety Standards for Construction and Guide for Selection, Installation and Operation of
Adjustable-Speed Drive Systems or their equivalent governing your particular location.
Chapter 32
CVALVE - Control Valve with Position Feedback
Overview
This chapter describes the CVALVE DFB.
Description
General
The main objective of the CVALVE DFB is to manage control valves with optional position feedback
(position and/or limit switches).
You can supplement this DFB with DINPUT DFBs from the General Purpose Library. This DFB
enables to incorporate conditioning functions for the digital signals of the limit switches.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Owner The DFB manages the control system level which is the owner (Operator or Program). As
a result, it is responsible for setting the set-point and activation for the control.
Interlocking The DFB enables you to assign the defined position if an active interlock that requires this
move is detected. An interlock bypass function is available.
Set-point The DFB enables to work under a remote (normally set from the continuous control) or
local (set from the program or by the operator depending on the active owner) set-point.
Simulation The target position of the valve is used as the current position in simulation mode. The
position limits that are normally determined based on the limit switches are simulated
based on the analog position.
Tracking The DFB activates monitoring for tracking the actual position in relation to the target
position.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
> LOSP and < HISP Refer to the following linear scaling formula.
>= HISP HIRAW
SP REAL Current valve set-point.
The SP calculation is shown in the following table:
OWNER (OFF: Program, REM SP is calculated as:
ON: Operator)
OFF OFF SC.LSP
OFF ON RSP
ON - CVALVE_CFG.LSP
OP REAL Valve positioning output in engineering units.
The OP calculation is shown in the following table:
SC.ILCKD OP is calculated as:
ON ILCKSP
OFF SP
PV REAL Current valve position in engineering units.
PVOPEN BOOL 1 = Indicates the open-valve position has been reached. This is verified by
checking whether or not the analog input falls within the threshold specified by
means of the HITHRESHOLD input.
PVCLOSED BOOL 1 = Indicates the closed-valve position has been reached. This is verified by
checking whether or not the analog input falls within the threshold specified by
means of the LOTHRESHOLD input.
ZSHPOS BOOL 1 = Indicates the open-valve position has been reached based on the limit switch
connected to ZSHPOS. If ZSHPOS is not operational, PVOPEN is used as a basis
for the indication instead.
ZSLPOS BOOL 1 = Indicates the closed-valve position has been reached based on the limit
switch connected to ZSLPOS. If ZSLPOS is not operational, PVCLOSED is used as
a basis for the indication instead.
ALARM BOOL 1 = Indicates a follow-up detected fault (1) has occurred. The analog position
signal is monitored. Refer to the MAXDEV and MAXDEV and TMAXDEV inputs
(see page 338).
Inputs/Outputs
CVALVE_CFG_DDT Type
CVALVE_ST_DDT Type
Public Variables
CVALVE_SC_DDT Type
Chapter 33
CVALVELP - Local Panel for Controlling Control Valves
Overview
This chapter describes CVALVELP DFB.
Description
General
The main objective of the CVALVELP DFB is to manage a local panel that controls a control valve
with position feedback. This valve is implemented with a CVALVE function block and with signals
that are wired to the controller so that the latter defines the target position for the device.
Function Description
The main functions of the module are described in the following table:
Function Description
Mode Switch Optionally manages the signals coming from an operating mode switch in a local
panel with the following configuration: Local - Zero - Control System. The Zero mode
signal is optional. However the user can enable Local/Control System mode from the
faceplate also, when VirtualLPEN input pin signal is high and MODESignalsEN
signal is low.
Push buttons The DFB manages up to two signals coming from OPEN and CLOSE push buttons,
giving the CLOSE push button higher priority.
Owner Management The DFB enables to configure whether the Program needs to be the valve owner or
not, after switching to the Control System mode again.
Owner Locking The DFB enables to configure whether the monitoring (HMI) system needs to block
access to the drop-down list or not, it disables the access to change the owner
(Operator/Program) while the valve is controlled from the Local Panel.
Set-point Lock The DFB enables to configure whether the monitoring (HMI) system needs to block
access to the drop-down list or not. It disables to change the set-point while the valve
is controlled from the Local Panel.
Push button The push button signals from the Local Panel can be enabled/disabled through the
Enabling/Disabling DFB configuration (input pin) and/or from control sequences.
Enabled Panel The DFB provides a signal that can be used to illuminate a light source on the Local
Signaling Panel to indicate when the push buttons are enabled for operation.
Virtual Panel This signal enables the operator to select the Local / Control System mode of
Enabling/Disabling operation from the HMI so that the push button signals are enabled for operation.
NOTE: VirtualLPEN input pin signal is applicable when PlantStruxure General
Purpose Library for Unity is used along with PlantStruxure General Purpose Library
for WSP.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
CVALVE_CFG.DDT Type
CVALVE_ST.DDT Type
CVALVE_ST.CFGW Word
The following table describes the CVALVE_ST.CFGW word:
CVALVELP_ST.CFGW Word
CVALVELP_ST.DDT Type
CVALVELP_ST.STW Word
Read-only access. Status word. The following table describes the CVALVELP_ST.STW word:
Public Variables
CVALVELP_SC_DDT Type
Chapter 34
MVALVE - Motorized Valve with Positioner
Overview
This chapter describes the MVALVE DFB.
Description
General
The MVALVE DFB is designed to control a motorized valve, or a gate with position feedback and 2-
rotational-direction-motor-based control.
As a result, combine the MVALVE DFB with the following Unity Pro components from the General
Purpose Library:
AINPUT
MOTOR2
DINPUT
Function Description
The main functions of the DFB are described in the following table:
Function Description
STEP3 The DFB includes and incorporates the functions provided by the STEP3 controller
from the standard CONT_CTL Unity library.
Owner The DFB manages the control system level which is the owner (Operator or Program).
As a result, it is responsible for setting the set-point and activation for the control
Interlocking The DFB enables you to assign the defined position if an active interlock that requires
this move is detected. An interlock bypass function is available.
Set-point The DFB enables to work under a remote (normally set from the continuous control)
or local (set from the program or by the operator depending on the active owner) set-
point.
Mode You can enable (START = 1) the STEP3CTL module to operate as described in the
STEP3 module in Automatic mode or disable (START = 0), in which case the module
continues calculating but forces the outputs to 0.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
SP REAL Current set-point is used by the STEP3 algorithm. The manner in which the block
calculates the set-point is based on the signal statuses, is given below:
OWNER REM SP is calculated as:
OFF OFF OFF
OFF ON RSP
ON – MVALVE_ST.SP.
You can modify the set-point directly
from the monitoring subsystem while
this mode is active.
WARNING
UNINTENDED EQUIPMENT OPERATION
The CONFREARMEN pin has to be set to 1 for the SP_MOTOR2 pin to become 0, under non-
confirmed operations.
Changes to the configuration of these parameters have to be performed by competent
personnel only.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Inputs/Outputs
MVALVE_CFG_DDT Type
TARGETSP REAL Valid read access. This variable indicates the current set-point status before
interlocking.
MVALVE_ST_DDT Type
MVALVE_ST_STW Type
MVALVE_ST_CFGW Type
Public Variables
MVALVE_SC_DDT Type
Chapter 35
MVALVELP - Local Panel for Controlling Motorized Valves
Overview
This chapter describes the MVALVELP DFB.
Description
General
The objective of the MVALVELP DFB is to manage a local panel that controls a motorized valve.
This valve is implemented with an MVALVE DFB and with signals that are wired to the controller so
that the latter defines the target position for the device.
Function Description
The main functions of the module are described in the following table:
Function Description
Mode Switch Optionally manages the signals coming from an operating mode switch in a local
panel with the following configuration: Local - Zero - Control System. The Zero mode
signal is optional. However the user can enable Local/Control System mode from the
faceplate also, when VirtualLPEN input pin signal is high and MODESignalsEN
signal is low.
Push buttons The DFB manages up to six signals coming from OFF, ON, OPEN, CLOSE, OPEN
QUICKLY and CLOSE QUICKLY push buttons. The priority is given to the OFF push
button and then to the closing function push buttons.
Owner Management The DFB enables to configure whether the Program needs to be the valve owner or
not, after switching to the Control System mode again.
Owner Locking The DFB enables to configure whether the monitoring (HMI) system needs to block
access to the drop-down list or not, it disables the access to change the owner
(Operator/Program) while the valve is controlled from the Local Panel.
Set-point Lock The DFB enables to configure whether the monitoring (HMI) system needs to block
access to the drop-down list or not. It disables to change the set-point while the valve
is controlled from the Local Panel.
Push button The push button signals from the Local Panel can be enabled/disabled through the
Enabling/Disabling DFB configuration (input pin) and/or from control sequences.
Enabled Panel The DFB provides a signal that can be used to illuminate a light source on the Local
Signaling Panel to indicate when the push buttons are enabled for operation.
Virtual Panel This signal enables the operator to select the Local / Control System mode of
Enabling/Disabling operation from the HMI so that the push button signals are enabled for operation.
NOTE: VirtualLPEN input pin signal is applicable when PlantStruxure General
Purpose Library for Unity is used along with PlantStruxure General Purpose Library
for WSP.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
MVALVE_ST.DDT Type
MVALVE_CFG.DDT Type
MVALVELP_ST.DDT Type
MVALVE_ST.CFGW Word
The following table describes the MVALVE_ST.CFGW word:
MVALVELP_ST.CFGW Word
MVAVELP_ST.STW Word
Read-only access. Status word. The following table describes the MVALVELP_ST.STW word:
Public Variables
MVALVEDLP_SC_DDT Type
Chapter 36
SDDEVCTL - Device with Variable Speed Drive
Overview
This chapter describes the SDDEVCTL DFB.
Description
General
The SDDEVCTL DFB is used to manage control modules for motors with a variable speed drive
whether the speed drive is switched through communication, I/O wiring, or a mix of both.
The DFB allows managing associated devices from the sequential control, the continuous control,
and/or the Supervision system depending on their configuration and on the system needs.
Likewise, you can supplement this DFB with the DEVMNT DFB from the General Purpose Library.
This allows the incorporation of totalizing functions for operating hours and switching operations.
Thus, maintenance of the device is facilitated.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Control Forward/reverse rotation direction.
Multispeed Enables to select between speed configurable through an analog signal or between
3 preset speeds in the speed drive.
Position detection Up to 2 limit switches or digital detectors (configurable) that allow determining the
actual position of the element to be controlled are monitored.
Local and remote Enables to control the DFB with a setpoint that is determined through a set-point
setpoint selector (local or remote).
The local setpoint is assigned to the sequential control or to the command received
from the Supervision system while the remote setpoint is assigned to the DFB control
from the logic implemented in the continuous control.
Interlocking The DFB gives the device the command to move to the defined position if an active
interlock that requires this move is detected. An interlock bypass function is available.
Owner selection The DFB manages control system level which is the owner (operator or program). As
a result, it is responsible for setting the setpoint for the desired position.
Simulation You can switch the DFB to simulation mode so that the actual position of the
controlled device is considered to be the same as its desired position, regardless of
the signals received from the position detectors.
The optional functions of the DFB are described in the following table:
Function Description
Inoperable device A digital signal that enables to determine if the control module that is in detected error
state is monitored.
Commonly used for detecting whether or not the motor switch has tripped due to
thermal overload.
Detection of not You can activate the detection of not confirmed operations after a configurable time
confirmed operation has elapsed.
Manual resetting Allows to configure the device to move to its position and reset manually when the
device does not respond or when the monitoring function is active.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
The table shows the value of the coding based on the status of the SPSELD, S1SELD, S2SELD, and
S3SELD outputs:
The evaluation of this signal depending on the configuration implemented on the RUNEN input and
on the SDDEVCTLST.CFGW.SIMMD input/output is shown in the table:
OWNER REM SP
OFF OFF Speed selected (in terms of the SC.LSP, SC.LSPSEL public variables and the
S1, S2, and S3 inputs) from the sequential control
OFF ON Speed selected from the continuous control (in terms of the RSP, RSPSEL, S1,
S2, and S3 inputs).
ON - Speed selected from the continuous control (in terms of the
SDDEVCTL_ST.CFGW.LSP and LSPSEL inputs/outputs and the S1, S2, and S3
inputs.
The table shows the FAILD signal evaluation depending on the FAIL and FAILEN inputs:
OP Calculation
WARNING
UNINTENDED EQUIPMENT OPERATION
The CONFREARMEN pin has to be set to 1 for the OP pin to become 0, under non-confirmed
operations.
The FAILREARMEN pin has to be set to 1 for the OP pin to become 0, under detected fail
conditions.
Changes to the configuration of these parameters have to be performed by competent
personnel only.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
FAILEN input FAILREARMEN input OP output when OP output when FAIL = 1 (assume
FAIL = 1 (assume OP = OP = 0 before the detected failure)
1 before the detected
failure)
0 0 1 0
0 1 1 0
1 0 1 0
1 1 0 0
ALARM Behavior
Monitoring is carried out on the RUNNING output signal and is activated when one of the control
signals (FORWARD and REVERSE outputs) is switched (0 to 1 or 1 to 0) as long as the
preselection value of the timer is greater than 0 (TIMEOUT input) and the speed drive is not being
controlled from outside the control system (EXTCTLD to 1).
After the control switching has occurred, the DFB internal timer is activated.
As long as the timer is running, the position of the speed drive is not monitored (RUN input).
After the time has elapsed, any detection of not confirmed operation causes the alarm to be
generated immediately.
The detected error signal is maintained for a minimum of SCANTIME (msec).
After this time has elapsed, the signal is recovered (0) based on the following conditions:
f the position becomes correct (RUNNING output) according to the control status (FORWARD
and REVERSE outputs) or
f the device is reset (through the SDDEVCTLST.CFGW.REARM input/output and as long as the
CONFREARMEN input is 1).
In both cases, the internal timer is restarted with the TIMEOUT value.
Inputs/Outputs
SDDEVCTL_ST_DDT Type
NOTE: The outputs (SP and OP) are de-energized when the device is in an out-of-service state;
even if an interlock that requests the device to be started is active.
SDDEVCTL_CFG_DDT Type
Public Variables
SDDEVCTL_SC_DDT Type
Chapter 37
SDDEVLP - Local Panel for Controlling Devices with a Variable-Speed Drive
Overview
This chapter describes the SDDEVLP DFB.
Description
General
The objective of the SDDEVLP DFB is to manage a local panel that controls a motor with a variable-
speed drive. This variable-speed drive is implemented with an SDDEVCTL DFB and with signals
that are wired to the controller so that the latter defines the target position for the device.
Function Description
The main functions of the module are described in the following table:
Function Description
Mode Switch Optionally manages the signals coming from an operating mode switch in a local
panel with the following configuration: Local - Zero - Control System. The Zero mode
signal is optional. However the user can enable Local/Control System mode from the
faceplate also, when VirtualLPEN input pin signal is high and MODESignalsEN
signal is low.
Push buttons The DFB manages up to eight signals coming from OFF, Forward ON, Reverse ON,
Increase speed, Decrease speed, S1 set-point pre-established, S2 set-point pre-
established, and S3 set-point pre-established push buttons, giving the OFF push
button signal priority.
Owner Management The DFB enables to configure whether the Program needs to be the owner of the
speed driver-equipped motor or not, after switching to the Control System mode
again.
Owner Locking The DFB enables to configure whether the monitoring (HMI) system needs to block
access to the drop-down list or not, it disables the access to change the owner
(Operator/Program) while the speed driver-equipped motor is controlled from the
Local Panel.
Set-point Lock The DFB enables to configure whether the monitoring (HMI) system needs to block
access to the drop-down list or not. It disables to change the set-point while the
speed driver-equipped motor is controlled from the Local Panel.
Push button The push button signals from the Local Panel can be enabled/disabled through the
Enabling/Disabling DFB configuration (input pin) and/or from control sequences.
Enabled Panel The DFB provides a signal that can be used to illuminate a light source on the Local
Signaling Panel to indicate when the push buttons are enabled for operation.
Virtual Panel This signal enables the operator to select the Local / Control System mode of
Enabling/Disabling/ operation from the HMI so that the push button signals are enabled for operation.
NOTE: VirtualLPEN input pin signal is applicable when PlantStruxure General
Purpose Library for Unity is used along with PlantStruxure General Purpose Library
for WSP.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
SDDEVCTL_CFG.DDT Type
SDDEVCTL_ST.DDT Type
SDDEVLP_ST.DDT Type
SDDEVCTL_ST.CFGW Word
The following table describes the SDDEVCTL_ST.CFGW word:
SDDEVLP_ST.CFGW Word
SDDEVLP_ST.STW Word
Read-only access. Status word. The following table describes the SDDEVLP_ST.STW word:
Public Variables
SDDEVLP_SC_DDT Type
Part V
Process Control
Process Control
Overview
This part provides a detailed description of the functions, pins, pin layout, and variables of the
function blocks of the process control family.
These function blocks do not reflect any specific installation.
WARNING
LOSS OF CONTROL
Perform a Failure Mode and Effects Analysis (FMEA) of your application, and apply preventive
and detective controls before implementation.
Provide a fallback state for undesired control events or sequences.
Provide separate or redundant control paths wherever required.
Supply appropriate parameters, particularly for limits.
Review the implications of transmission delays and take actions to mitigate.
Review the implications of communication link interruptions and take actions to mitigate.
Provide independent paths for control functions (for example, emergency stop, over-limit
conditions, and fault conditions) according to the safety analysis and applicable codes, and
regulations.
Apply local accident prevention and safety regulations and guidelines. 1
Test each implementation of this library for proper operation before placing it into service.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
1For additional information, refer to NEMA ICS 1.1 (latest edition), Safety Guidelines for the
Application, Installation, and Maintenance of Solid State Control and to NEMA ICS 7.1 (latest
edition), Safety Standards for Construction and Guide for Selection, Installation and Operation of
Adjustable-Speed Drive Systems or their equivalent governing your particular location.
Chapter 38
ARAMP - RAMP
ARAMP - RAMP
Overview
This chapter describes the ARAMP DFB.
Description
General
The ARAMP DFB is used to generate rising or falling set-point ramps for other control modules, such
as PID regulators, direct analog outputs, and so on.
The ARAMP DFB is based on and internally instantiates a standard ARAMP DFB from the Control
library.
The DFB provides tracking functions (for example, for set-points or measurements, as required),
temporary ramp shutdown due to maximum deviation, management of set-points from monitoring
and/or control, and so on.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Ramp The DFB allows to generate rising and/or falling ramps with different slopes as required.
Maximum Optionally, configure the DFB so that the ramp is held until the deviation between the
Deviation measurement and the set-point is less than the maximum deviation allowed.
Tracking While the ramp DFB is not in operation, the signal on one of its pins is tracked (normally the
pin connected to the measurement that needs to be controlled or to the last position of the
control element – for example, a control valve).
Owner The DFB manages control system level, which is the owner (Operator or Program).
Therefore, it is responsible for setting the ramp set-points.
Local/Remote If the Program is the owner, you can set the ramp set-point from continuous control (with
Set-point the input pin designated for this purpose) or from the sequence (with the SC public variable).
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
The following configuration data is considered according to the operating mode selected:
ARAMP_ST.CFGW.OWNER SC.REM TARGET SET-POINT and
RUN COMMAND
OFF (Program) OFF (Local) SC.LTARGETSP and SC.LSTART
OFF ON (Remote/Cascade - RTARGETSP and RSTART
applicable while the
Program is the OWNER)
ON (Operator) - ARAMP_CFG.LTARGETSP and
ARAMP_ST.CFGW.LSTART
RUNNING BOOL 1 = Indicates that the ramp is active. This signal responds to the xSTART command
depending on the operating mode that is running.
The RUNNING signal calculation based on the DFB operating mode is detailed in
the following table:
OWNER REM RUNNING
OFF OFF SC.LSTART
OFF ON RSTART
ON - ARAMP_CFG .CFGW.LSTART
HELD BOOL 1 = Indicates that the ramp is held. The ramp is held if a maximum deviation greater
than 0.0 (ARAMP_CFG.MAXDEV) has been configured and the distance between
the set-point (SP) and the measurement (PV) is greater than this deviation. While
this signal is active, the set-point is maintained at its last value and the ramp does
not go on.
The calculation of the HELD signal based on the DFB operating mode is detailed in
the following table:
ARAMP_CFG.MAXDEV RUNNING HELD
- OFF OFF
0.0 - OFF
>0.0 ON Distance between PV and SP greater
than ARAMP_CFG.MAXDEV
DONE BOOL 1 = Indicates that the set-point (SP output) has reached the set target. The module
stays active even if this signal is activated so that if the target set-point is modified,
the necessary ramp (rising or falling) is generated in order to reach it.
The DONE signal calculation based on the DFB operating mode is detailed in the
following table:
RUNNING DONE
OFF OFF
ON PV = RTARGETSP
STATUS WORD Status word generated by the standard Control RAMP DFB instantiated within the
ARAMP DFB. Refer Control Help for more details.
Inputs/Outputs
ARAMP_ST_DDT Type
The following table describes the ARAMP_ST_DDT type:
ARAMP_CFG_DDT Type
Public Variables
ARAMP_SC_DDT Type
Chapter 39
IMCTL - IMC Controller with Monitoring Interface
Overview
This chapter describes the IMCTL DFB.
Description
General
The IMCTL DFB is used to condition the signals associated with the control of a standard Control
library IMC controller (Internal Model Controller). This helps to monitor and control the controller
easily from the monitoring subsystem and to provide the operating modes used in the rest of the
General Purpose library process function blocks.
The IMC internal model controller is specifically designed to control processes with pure delays as
well as non-linear processes.
Function Description
The main functions of the DFB are described in the following table:
Function Description
IMC The DFB includes and incorporates functions provided by the IMC controller from the
standard CONT_CTL library. You can directly configure the IMC controller functions that
have not been shown through the DFB interface by accessing the DFB configuration
parameters (for example, FeedForward, variable gain, and so on). Refer to the Control
Help for more details.
Owner The DFB manages the control system level, which is the owner (Operator or Program). As
a result, it is responsible for setting the set-point to the target position (in the Auto mode
of the IMC controller ) or the manual output (in the Manual mode of the IMC controller).
Interlocking The DFB enables to move to the defined position if an active interlock that requires this
move is detected. An interlock bypass function is available.
Set-point The DFB enables to work under a remote (usually set from the continuous control) or local
(set from the program or by the operator depending on the active owner) set-point.
Override You can combine several IMCTL or other DFBs to control one single control module. This
way, the DFB that is not controlling this DFB at a certain point of time works with an
external output, that is, calculating the new output based on the position of control module
instead of the last position calculated by the DFB itself.
These functions are internally provided by the standard IMC controller.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
The set-point calculation that the DFB performs based on the signal status is detailed in the
following table:
Inputs/Outputs
IMCTL_CFG_DDT Type
IMCTL_ST_DDT Type
Public Variables
IMCTL_SC_DDT Type
Chapter 40
LDLGCTL - Lead-Lag Controller with Monitoring Interface
Overview
This chapter describes the LDLGCTL DFB.
Description
General
The LDLGCTL DFB is used to condition the signals associated to the control of a LEAD-LAG
controller. This DFB helps to monitor and control the controller easily from the monitoring
subsystem and to provide the operating modes used in the rest of the General Purpose library
process function blocks.
Function Description
The main functions of the DFB are described in the following table:
Function Description
LEAD-LAG The DFB includes and incorporates functions provided by the LEAD-LAG controller
from the standard CONT_CTL Control library.
Owner The DFB manages control system level, which is the owner (Operator or Program).
As a result, it is responsible for setting the set-point to the desired position (in the Auto
mode of the LEAD-LAG controller) or the manual output (in the Manual mode of the
LEAD-LAG controller).
Interlocking The DFB enables to move to the defined position if an active interlock that requires
this move is detected. An interlock bypass function is available.
Set-point The DFB enables you to work under a remote (usually set from the continuous
control) or local (set from the program or by the operator depending on the active
owner) set-point.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
LDLGCTL_CFG_DDT Type
LDLGCTL_ST_DDT Type
Public Variables
LDLGCTL_SC_DDT Type
Chapter 41
PIDCTL - PIDFF Regulator with Monitoring Interface
Overview
This chapter describes the PIDCTL DFB.
Description
General
The PIDCTL DFB is used to condition the signals associated with the control of a PIDFF-type
controller. This DFB helps to monitor and control the controller easily from the monitoring
subsystem and to provide the operating modes used in the rest of the General Purpose library
process function blocks.
Function Description
The main functions of the DFB are described in the following table:
Function Description
PIDFF The DFB includes and incorporates functions provided by the PIDFF controller from
the standard CONTR_CTL library. You can directly configure the PIDFF controller
functions that have not been shown through the DFB interface by accessing its
configuration parameters (for example, FeedForward, variable gain, and so on).
Owner The DFB manages control system level, which is the owner (Operator or Program).
As a result, it is responsible for setting the set-point to the desired position (in the
Auto mode of the PID controller) or the manual output (in the Manual mode of the
PID controller).
Interlocking The DFB enables to move to the defined position if an active interlock that requires
this move is detected. An interlock bypass function is available.
Set-point The DFB enables to work under a remote (usually set from the continuous control)
or local (set from the program or by the operator depending on the active owner) set-
point.
Override You can combine several PIDCTL or other DFBs to control one single control
module. This way, the DFB that is not controlling this DFB at a certain point in time
works with an external output, that is, calculating the new output based on the
position of control module instead of the last position calculated by the DFB itself.
These functionalities are internally provided by the standard PIDFF controller.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
The set-point calculation that the DFB performs based on the signal status is detailed in the
following table:
Inputs/Outputs
PIDCTL_CFG_DDT Type
PIDCTL_ST_DDT Type
Public Variables
PIDCTL_SC_DDT Type
Chapter 42
PIDMUX - Multiplexer for 2 Groups of PIDCTL Parameters
Overview
This chapter describes the PIDMUX DFB.
Description
General
The PIDMUX DFB is used to multiplex 2 different parameter configurations that affect a single PID
controller. This way, you can use one single PID controller with different configurations (for
example, split-range PID for cooling or heating).
You can monitor and control the DFB from the monitoring subsystem.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Parameter Switching During a scan cycle, the DFB activates the RCPY signal. This enables you to use the
signal to set the PIDCTL controller so that it uses an external output during the
parameter configuration change. This way, the controller initializes its integral term
and any jumps when switching outputs are stopped.
Owner The DFB manages control system level, which is the owner (Operator or Program).
Therefore, it is responsible for setting the active parameter set.
Parameter Selection You can control the parameter selector remotely (normally set from the continuous
control) or locally (set from the program or by the operator depending on the active
owner).
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
PIDMUX_CFG_DDT Type
PIDMUX_ST_DDT Type
Public Variables
PIDMUX_SC_DDT Type
Chapter 43
PWMCTL - Pulse-Width Modulated Controller
Overview
This chapter describes the PWMCTL DFB.
Description
General
The PWMCTL DFB is used to condition the signals associated with pulse-width modulated (PWM)
control.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Owner The DFB manages control system level, which is the owner (Operator or Program).
As a result, it is responsible for setting the set-point and activation for the controller.
Interlocking The DFB enables to move to the defined position if an active interlock that requires
this move is detected. An interlock bypass function is available.
Set-point The DFB enables to work under a remote (normally set from the continuous control)
or local (set from the program or by the operator depending on the active owner) set-
point.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
The DFB performs the set-point calculation based on the signal status. The set-point calculation is
detailed in the following table:
Inputs/Outputs
PWMCTL_CFG_DDT Type
PWMCTL_ST_DDT Type
Public Variables
PWMCTL_SC_DDT Type
Chapter 44
RATIOCTL - Ratio Controller
Overview
This chapter describes the RATIOCTL DFB.
Description
General
The RATIOCTL DFB is used to condition the signals associated to a standard Control library
RATIO controller. This helps to monitor and control the controller from the monitoring subsystem
and to provide the operating modes used in the rest of the General Purpose library process
function blocks.
The RATIO controller sets a set-point based on a measurement signal and the ratio that needs to
be maintained between them (that is, between the measurement signal and the set-point). This
DFB is especially used for dosing materials that should have a certain ratio in relation to one
another.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Ratio The DFB includes and incorporates functions provided by the RATIO controller from the
standard CONT_CTL Control library.
Owner The DFB manages control system level, which is the owner (Operator or Program). As a
result, it is responsible for setting the set-point and activation for the controller.
Interlocking The DFB enables to move to the defined position if an active interlock that requires this
move is detected. An interlock bypass function is available.
Set-point The DFB enables to work under a remote (normally set from the continuous control) or
local (set from the program or by the operator depending on the active owner) set-point.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
The DFB performs the ratio coefficient calculation based on the signal statuses. The ratio
coefficient calculation is detailed in the following table:
Inputs/Outputs
RATIOCTL_CFG_DDT Type
RATIOCTL_ST_DDT Type
Public Variables
RATIOCTL_SC_DDT Type
Chapter 45
SPLRGCTL - Split-Range Controller
Overview
This chapter describes the SPLRGCTL DFB.
Description
General
The SPLRGCTL DFB is used to condition the signals associated to the standard Control library
SPLRG DFB. This helps to monitor and control the controller from the monitoring subsystem and to
provide the operating modes used in the rest of the General Purpose library process function
blocks.
The standard Control library SPLRG DFB is used for split-range controllers (for example, cold/heat)
because it enables to generate 2 output signals based on a single signal that could come, for
instance, from the output of a PID controller.
You can combine this DFB with the PIDCTL and PIDMUX DFBs when you want to control a process
with 2 control modules (for example, 2 modulating valves) and PID control.
Function Description
The main functions of the DFB are described in the following table:
Function Description
SPLRG The DFB includes and incorporates functions provided by the SPLRG controller from
the standard CONT_CTL library.
Owner The DFB manages control system level, which is the owner (Operator or Program).
As a result, it is responsible for setting the set-point and activation for the controller.
Interlocking The DFB enables to move to the defined position if an active interlock that requires
this move is detected. An interlock bypass function is available.
Set-point The DFB enables to work under a remote (normally set from the continuous control)
or local (set from the program or by the operator depending on the active owner) set-
point.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
SPLRGCTL_CFG_DDT Type
SPLRGCTL_ST_DDT Type
Public Variables
SPLRGCTL_SC_DDT Type
Chapter 46
STEP3CTL - 3 Step Controller/Positioner
Overview
This chapter describes the STEP3CTL DFB.
Description
General
The STEP3CTL DFB is used to condition the signals associated with the control of a STEP3-type
controller. This helps to monitor and control the controller easily from the monitoring subsystem
and to provide the operating modes used in the rest of the General Purpose library process
function blocks.
The STEP3CTL DFB is designed for controlling process variables through discrete control modules
(for example, temperature control through hot liquid/cold liquid on-off valves) or for positioning of
analog components with discrete drives (for example, a motorized valve or a gate with position and
control feedback through a 2-direction motor). Because of this, combine the STEP3CTL DFB with
other library components such as AINPUT, DEVCTL, MOTOR2, DOUTPUT, and so on.
Function Description
The main functions of the DFB are described in the following table:
Function Description
STEP3 The DFB includes and incorporates functions provided by the STEP3 controller from the
standard CONT_CTL library.
Owner The DFB manages control system level, which is the owner (Operator or Program). As a
result, it is responsible for setting the set-point and activation for the controller.
Interlocking The DFB enables to move to a defined set-point if an active interlocking that requires this
move is detected. An interlock bypass function is available.
Set-point The DFB enables to work under a remote (usually set from the continuous control) or local
(set from the program or by the operator depending on the active owner) set-point.
Mode You can enable the STEP3CTL DFB (Start=1) to operate as described in the STEP3 DFB
in automatic mode, or disable (Start=0). In this case, the DFB continues calculating but
forces the outputs to 0.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
STEP3CTL_CFG_DDT Type
Highlight particular operation of the controller and the configuration of the three parameters above;
going through the operation graph is recommended.
For example, in case of temperature regulation with a cold liquid valve and a hot liquid valve (the
cold liquid valve is connected to OPDEC and the hot liquid valve to OPINC), the following
assumption is made:
the set-point is 21° (SP).
a maximum detected error of 1° above and below with a hysteresis of 0.5% is being considered
(DEVHL=1, DEVLL=1, HYS=0.5).
In this initial case, PV-SP = -11 (<DEVLL), and, as a result, OPINC=1 (output that corresponds to
increasing PV).
As PV increases, the detected error decreases in absolute value until the detected error is less than
-0.5, that is, DEVLL+HYS=-1+0.5=-0.5, when OPINC becomes 0. Verify that the output stops at the
DEVLL+HYS threshold and not at DEVLL.
Hysteresis will be achieved if the detected error drops below the DEVLL value, at which point the
OPINC will return to the value of 1.
On the positive side of the detected error, you can consider the event in which the temperature is
30º with the same DEVHL, DEVLL, and HYS values.
In this initial case PV-SP = 9 (>DEVHL), and, as a result, OPDEC=1 (output that corresponds to
decreasing PV).
As PV drops, the detected error decreases in absolute value, until the detected error is less than
0.5, that is DEVHL-HYS=1-0.5=0.5, at which point OPDEC becomes 0. Verify that the output stops
at the DEVLL+HYS threshold and not at DEVLL.
Hysteresis will be achieved if the detected error rises above the DEVLL value, at which time the
OPINC will return to a value of 1.
STEP3CTL_ST_DDT Type
STEP3CTL_ST.STW Word
STEP3CTL_ST.CFGW Word
Public Variables
STEP3CTL_SC_DDT Type
The following table describes the STEP3CTL_SC_DDT type:
Part VI
Sequential Control
Sequential Control
Overview
This part provides a detailed description of the functions, pins, pin layout, and variables of the
function blocks of the sequential control family.
These function blocks do not reflect any specific installation.
WARNING
LOSS OF CONTROL
Perform a Failure Mode and Effects Analysis (FMEA) of your application, and apply preventive
and detective controls before implementation.
Provide a fallback state for undesired control events or sequences.
Provide separate or redundant control paths wherever required.
Supply appropriate parameters, particularly for limits.
Review the implications of transmission delays and take actions to mitigate.
Review the implications of communication link interruptions and take actions to mitigate.
Provide independent paths for control functions (for example, emergency stop, over-limit
conditions, and fault conditions) according to the safety analysis and applicable codes, and
regulations.
Apply local accident prevention and safety regulations and guidelines. 1
Test each implementation of this library for proper operation before placing it into service.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
1For additional information, refer to NEMA ICS 1.1 (latest edition), Safety Guidelines for the
Application, Installation, and Maintenance of Solid State Control and to NEMA ICS 7.1 (latest
edition), Safety Standards for Construction and Guide for Selection, Installation and Operation of
Adjustable-Speed Drive Systems or their equivalent governing your particular location.
Chapter 47
Sequential Control
Sequential Control
Overview
This chapter describes the sequential control management.
Overview
The operation of the function block that is available for sequence control is described in this
chapter.
The SEQCTL1 DFB belongs to the General Purpose library and is used to monitor and manage
control sequences. The module is based on the ISA-S88 Standard, Part 1 (S88.01) and
implements the status controller defined in this standard for controlling procedure model
components (phases, operations, and so on).
Function Description
You can use this DFB to change states in the process. In compliance with ISA-S88.01I, you can
use this DFB in continuous processes to initiate start, stop or emergency sequences. In batch
processes, this DFB can be used to set up phases and operations.
The DFB implements sequence state management and processes the commands received from:
The Supervision system (when sequences are manually controlled by the operator)
The batch control subsystem (in which case the subsystem sends the commands and checks
the status of the sequence to determine what action to take)
Other control sequences
For example, sequences that implement operations defined in the ISA-S88 standard can control
the phases and can also be implemented through sequences managed from the component.
The table compares the functions that are available in the DFB:
Function SEQCTL1
Management of state machine and commands according to ISA-S88 x
Management of messages for the operator integrated with the sequence –
Management of operating modes according to ISA-S88: Manual (enables to x
change from one sequence step to any other sequence step), Semi (step
advance with confirmation from the operator), and Auto
Owner Management: Operator/Program x
Step time automatically calculated by the control block x
Automatic management of transitions through the SEQTRANS function block x
Automatic management of sequence detected failure through the SEQFAILED x
function block
Automatic management of sequence steady-step marking through the x
SEQSTABLESTEP function block
Possibility of displaying the sequence graphically (active step and next level of x
transitions and steps) from the monitoring subsystem
NOTE: ‘x’ indicates that the functions are available in the DFB.
Program the steps and transitions that the sequences implement (through ST or SFC language)
while the component (SEQCTL or SEQCTL1) allows the programmer to:
manage the statuses of the sequence and
process the commands received from other levels as described above.
Function Description
Processing States and The DFB processes the commands received and determines the status of
Commands the control sequence with the objective of determining the subsequences
(normal, hold, continue, abort, so on.) and which step needs to run in each
cycle of the program.
Managing Entry Points in the The DFB enables to retain the step number with which the execution of the
Sequence normal sequence (Running) needs to be restarted (Restart) after being
restarted from held status (Held).
Handling of Detected Failures The component manages controller detected failures (without user
intervention from the Supervision system). The component manages this
detected failure and triggers the execution of the detected failure handling
subsequence.
Statuses
The table describes the possible sequence statuses along with the code that identifies each status:
The (Held) status can also be reached (without receiving a command) if the control sequence itself
detects a problem situation. The DFB has a signal that allows this situation to be communicated.
The DFB has the necessary means to be able to restart the Running sequence from the last steady
step in which the initial run was held by a Hold command.
Commands
The table describes the commands that can be sent to the sequence along with the code and
description of each command:
Status Matrix
Description
The following table describes the finite status controller that the DFB implements:
The Held status can also be reached (without receiving a command) if the control sequence itself
encounters a detected error. The block has a signal that allows this situation to be communicated.
The block has the necessary means to be able to restart the Running sequence from the last
steady step in which the initial run was held by a Hold command.
Status Controller
Description
The following diagram describes the possible statuses and commands that the Unity Pro
component manages according to the ISA-S88 standard:
Next to the transition arrows, the commands that the component receives (from the Supervision
system or another higher level sequence) are shown in black, and the flags that the sequence itself
generates are shown in red in parentheses.
Operating Modes
Mode Table
The following table provides the description of the sequence operating modes of SEQCTL1 DFB:
Chapter 48
SEQCTL1 - Advanced Sequential Control
Overview
This chapter provides a detailed description of the functions, pins, pin layout, and variables of the
SEQCTL1 DFB.
Description
Initialization
If the sequence status is unknown, it is initialized as Idle regardless of whether a controller has
restarted or not. This initialization is done automatically.
DFB Representation
Representation
The DFB that is used in the program has the following aspect at the section level when
imported.You can use it in any of the programming languages, although it is designed for use with
the FBD language.
The figure shows an example of the SEQCTL1 DFB instance:
Implement the sequence logic that controls the component in ST language to take advantage of
the sequence control potentials making the sequence reusable. That is, you can run
simultaneously several instances of the sequence that you have implemented. This reduces
engineering and maintenance efforts when it is necessary to set up the same control sequences
in several process units.
Inputs/Outputs
SEQCTL1_ST_DDT Type
SEQCTL1_ST.STW Word
In this word, the SEQTRANS auxiliary DFB is used to load the status of the transitions (maximum of
6) from the current step of the sequence to the steps in the next level of the sequence where 0
means that the conditions in the transition are not fulfilled and 1 means that they are fulfilled.
Bit Description
0 Status of the first transition
1 Status of the second transition
... ...
5 Status of the sixth transition
SEQCTL1_ST.CFGW Word
The following table describes the SEQCTL1_ST.CFGW word:
SEQCTL1_CFG_DDT Type
Public Variables
SEQCTL1_SC_DDT Type
The following elements (status) are described in the Status Controller section (see page 507). The
Definition of Statuses and Commands (see page 504) shows the sequence finite state controller.
Chapter 49
Auxiliary Functions of Sequential Control
Overview
This section describes the function blocks that supplement the SEQCTL1 DFB and that have the
objective of facilitating the programming of the control sequence.
Section 49.1
SEQTRANS
SEQTRANS
Overview
This section describes the SEQTRANS DFB.
Description
General
The main objective of SEQTRANS DFB is to set up the control sequence transitions based on the
condition to be evaluated and the next step to be executed when this expression is fulfilled.
Additionally, the DFB manages the information necessary to graphically represent the state of the
transitions and steps following the current step (DEST and DESTW fields of the SEQCTL1_ST_DDT
sequence state structure).
Include call to this function in the logic of the steps (normally in ST language) to program the
transitions between the sequence steps.
Function Call
The function call is carried out from the steps of the control subsequences (Running, Restarting,
Holding, and so on) normally in ST language to program the transitions between these steps.
If several SEQTRANS calls are included in the same step and if more than one of them is fulfilled in
the same step execution cycle, the step corresponding to the transition that is fulfilled and was
programmed first will run. The number of SEQTRANS calls from one single step is limited to 6.
TRANS (CONDITION := (*BOOL*),
DESC := (*string[22]*),
NEXTSTEP := (*INT*),
SEQCTL1_SC := (*SEQCTL1_SC_DDT*)
SEQCTL1_ST := (*SEQCTL1_ST_DDT*),
SEQCTL1_CFG := (*SEQCTL1_CFG_DDT*))
A function call example is included below:
4: (Wait for end of reactive dosing)
if SSC.ONENTRY then
BISEN2_REACT.REM:=false;
BISEN2_REACT.LSP:=true;
end_if;
BISEN2_REACT.LSPSEL:=(OP01 < (IP01 - 10.0)); (Speed 1 or 2)
TRANS ((IP01 - COLA_REACT) <= OP01, 'Dosing finished?', SSC.CSTEP+1, SSC,
SST, SCFG);
In the previous example, the TRANS call included in step 4 of the sequence corresponds to a
SEQTRANS block instance to which the following parameters are passed:
(IP01 - COLA_REACT) <= OP01OS: Corresponds to the expression of the condition that
needs to be fulfilled for the transition to be executed. You can include complex expressions that
result in a Boolean value (true or false).
Dosing finished?: Corresponds to the description of the transition.
SSC.CSTEP+1: Corresponds to the next step that needs to be executed when the transition is
fulfilled. In this case, the next step (step 5) is executed after the current step (step 4). You can
include any expression jumping to an existing step in the sequence.
SSC: Corresponds to the SC public variable of the SEQCTL1 block instance that is controlling the
sequence execution.
SST: Corresponds to the DDT_ST variable of the SEQCTL1 block instance that is controlling the
sequence execution.
SCFG: Corresponds to the DDT_CFG variable of the SEQCTL1 block instance that is controlling
the sequence execution.
Inputs
Inputs/Outputs
Section 49.2
SEQFAILED
SEQFAILED
Overview
This section describes the SEQFAILED DFB.
Description
General
The main objective of the SEQFAILED DFB is to report detected errors to the sequence
management block (SEQCTL1) during sequence execution so that the HoldingFE subsequence
is triggered.
Function Call
The function call is made from the Running, Restarting, Pausing, or Paused control subsequence
steps normally in ST language with the purpose of reporting detected errors in the process that is
being controlled. The detected error requires the hold sequence to be executed (HoldingFE).
A function call example is included below:
(Detected failure condition monitoring after initializations)
if SEQCTL1.CSTEP > 0 and CONDFALLO then
FAILED (SeqCtl1); (Trigger execution of the Hold sequence)
end_if;
In the previous example, the FAILED call that is included in the logic monitors the detected error
conditions in each execution cycle (in this particular case, but could be associated with a specific
step) corresponds to a SEQFAILED DFB block instance to which the following parameters are
passed:
Seqctl1: Corresponds to the name of the SC public variable of the SEQCTL1 block instance
that is controlling the execution of the sequence.
Inputs/Outputs
Section 49.3
SEQSTABLESTEP
SEQSTABLESTEP
Overview
The section describes the SEQSTABLESTEP DFB.
Description
General
The main objective of the SEQSTABLESTEP DFB is to report to the sequence management block
(SEQCTL1) that the current running sequence step corresponds to a step, that is, the re-entry point
in the normal execution (Running) sequence executes after restarting execution (Restarting).
Function Call
The function call is performed from the Running control subsequence steps normally in ST
language for the purpose of reporting. The current step is the entry point to which the program
should return when the Running subsequence is resumed after finishing the Restarting
subsequence. Basically, it enables to resume the sequence execution that verifies the appropriate
actions are performed or not.
For example, suppose a valve has to be opened. After the valve is opened, the next step involves
turning on a pump. While waiting for the valve to open, a detected failure that makes the sequence
stop occurs (Holding subsequence execution). You can resume execution by running the restart
(Restarting) subsequence. After this, the program returns to the normal running subsequence
(Running). After the program goes back to this Running subsequence, the intention is to make
another attempt at opening the valve (because most likely, it has been closed during the Holding
subsequence) not to start the pump in proceeding directly. Therefore, in the valve opening step,
the step is marked and does not call the function SEQSTABLESTEP in the pump starting step.
The following is an example of a function call:
0: (End Water dosing)
if SeqCtl1.ONENTRY then
RAMP_AGUA.LSTART:=false;
FIC_AGUA.REM:=false;
FIC_AGUA.MAN:=true;
FIC_AGUA.LOP:=0.0;
VALV_AGUA.LSP:=false;
STABLESTEP (SeqCtl1);
end_if;
TRANS (VALV_AGUA.LOWPOS, SEQCTL1.CSTEP+1, SeqCtl1);
In the previous example, the STABLESTEP call included in the logic that monitors detected failure
conditions in each execution cycle (in this particular case, but it could be associated with a specific
step) corresponds to a SEQSTABLESTEP DFB block instance to which the following parameters are
passed:
Seqctl1: Corresponds to the name of the SC public variable of the SEQCTL1 block instance
that is controlling the sequence execution.
Inputs/Outputs
Section 49.4
SEQSTEPDESC
SEQSTEPDESC
Overview
This section describes the SEQSTEPDESC DFB.
Description
General
The main objective of the SEQSTEPDESC DFB is to assign descriptions to the steps that are defined
in the sequence to allow you to monitor them from the Supervision system.
Function Calls
The function call is made from the control subsequence steps (Running, Restarting, Holding, and
so on) at the beginning of the code to provide the description of the subsequence steps for their
representation in the monitoring program. It is normally written in ST language.
Include as many SEQSTEPDESC calls as there are steps defined in the subsequence or as there
are steps that need to be represented in the Supervision system.
The syntax of the function is the following:
STEPDESC (STEPNUMBER := (INT),
DESC := (string[18]),
SEQCTL1_SC := (SEQCTL1_SC_DDT),
SEQCTL1_ST := (SEQCTL1_ST_DDT),
SEQCTL1_CFG := (SEQCTL1_CFG_DDT),
The following is an example of a function call:
(Running or Pausing Subsequence (302 / 314))
(Step descriptions)
STEPDESC (1, 'Init', SSC, SST, SCFG);
STEPDESC (2, 'Valves ON', SSC, SST, SCFG);
STEPDESC (3, 'Wait Valves ON', SSC, SST, SCFG);
STEPDESC (4, 'Dosing Reactive', SSC, SST, SCFG);
STEPDESC (5, 'Motor OFF', SSC, SST, SCFG);
STEPDESC (6, 'Waiting for queue', SSC, SST, SCFG);
(Steps and Transitions)
case SSC.CSTEP of
1: (#RunningStep0# Initial Step)
(Check initial conditions)
if IC_FAIL then
FalloCI := true;
FAILED (SSC); (Initial conditions not satisfied)
else
FalloCI := false;
(Initialization)
In the above example, the STEPDESC calls included at the beginning of the subsequence
correspond to a SEQSTEPDESC DFB block instance to which the following parameters are passed
in case of the first call:
1: Corresponds to step number 1.
Init: Corresponds to the definition of the step.
SSC: Corresponds to the SC public variable of the SEQCTL1 block instance that is controlling the
sequence execution.
SST: Corresponds to the DDT_ST variable of the SEQCTL1 block instance that is controlling the
sequence execution.
SCFG: Corresponds to the DDT_CFG variable of the SEQCTL1 block instance that is controlling
the sequence execution.
Inputs
Inputs/Outputs
Public Variables
Chapter 50
SEQPARxx - Sequence Parameter Management
Overview
This chapter describes the SEQPARxx DFB.
Description
General
The SEQPAR05, SEQPAR10 and SEQPAR16 DFBs manage up to 5, 10, and 16 sequence
parameters (input, output, and reports) respectively. The DFBs facilitate the management of
parameters from advanced control sequences implemented with the General Purpose Library
SEQCTL1 DFB.
These DFBs manage the sequence parameters with a data structure (DDT) making it easier to
implement reusable control sequences (the number of pins in a DFB is limited to 32 input pins and
32 output pins) because a single variable is used to provide access to the data that the sequence
manages.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Input Parameter Optionally, the DFB initializes the values of the input parameters with a value (-0.0)
Consistency that enables to determine whether or not the applicable parameters of the sequence
have been correctly downloaded onto the controller. This way, the sequence can be
stopped from starting with an incomplete or inconsistent set of input parameters.
Owner The DFB manages control system level, which is the owner (Operator or Program)
based on the owner of the associated sequence. As a result, it is responsible for
defining the input parameters of the sequence.
Output Parameters The DFB manages the output parameters generated from the control sequence.
Report Parameters The DFB copies the output parameters to report parameters when the sequence
ends and maintains them until the next sequence end. This facilitates the acquisition
of these parameters from the monitoring subsystem to generate reports.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
SEQPARxx_ST_DDT Type
Public Variables
SEQPARxx_SC_DDT Type
Chapter 51
SEQCTL1 - Example of Use
Overview
This chapter describes the example use of the SEQCTL1DFB.
Description
General
This chapter gives an example of an advanced control sequence controlled by the SEQCTL1,
SEQTRANS, SEQSTABLESTEP, SEQFAILED, and SEQSTEPDESC DFBs.
The objective of the sequence is to control the loading of water in a process unit. For this purpose,
a reusable component (DFB) is created so that you can use this sequence in different process units
by only changing the connections of the component pins.
NOTE: Declaration of the auxiliary components manages the transitions (SEQTRANS), steady-step
flags (SEQSTABLESTEP), and notifications to trigger the holding subsequence (SEQFAILED).
DFB Representation
Representation
The following diagrams include the calls to the sequence created by the user as well as to the
control block that will control it (SEQCTL1).
NOTE: The call to the block controls the execution of the advanced control sequence.
NOTE: The call to the functional block implements the control sequence of the user and will reuse
for different process units if needed.
NOTE: The evaluation priority for these transitions is the order in which they are shown (up down;
these transitions are not functional, and have only been included as an example in this case). You
can define a maximum of 6 transitions.
3: (Wait for open valve)
TRANS (VALV_AGUA.HIGHPOS, 'Valve open?', SSC.CSTEP+1, SSC, SST, SCFG);
(Next step)
4: (Wait for end of Water dosing)
if SSC.ONENTRY then
RAMP_AGUA.REM := false; (Setpoint flow ramp)
RAMP_AGUA.LTARGETSP:=IP02; (Target set-point)
RAMP_AGUA.LSTART:=true
FIC_AGUA.REM:=true;
FIC_AGUA.AUTO:=true;
FIC_AGUA.LSP:=IP02; (Flow regulation)
end_if;
TRANS ((IP01 - COLA_AGUA) <= OP01, 'Dosing finished?', SSC.CSTEP + 1,
SSC, SST, SCFG);
5: (End Water dosing)
if SSC.ONENTRY then
RAMP_AGUA.LSTART:=false;
FIC_AGUA.REM:=false;
FIC_AGUA.MAN:=true;
FIC_AGUA.LOP:=0.0;
VALV_AGUA.LSP:=false;
STABLESTEP (SSC); (In this step, execution will restart in the event of Hold/Continue)
end_if;
TRANS (VALV_AGUA.LOWPOS, 'Valve Closed?', SSC.CSTEP+1, SSC, SST, SCFG);
6: (Wait for Water queue)
if SSC.ONENTRY then
(Wait for COLA_AGUA (Water queue) to fall)
STABLESTEP (SSC); (In this step, execution will restart in the event of Hold/Continue)
end_if;
TRANS (SSC.ETIME >= 50, 'Waiting for queue', -1, SSC, SST, SCFG); (End of
sequence)
NOTE: Complete sequence (go to COMPLETE) when the transition condition is met.
end_case;
(Actions common to several steps)
(Detected failure condition monitoring after initializations)
if SSC.CSTEP > 0 and FC then
FAILED (SSC); (Trigger execution of the Hold sequence)
end_if;
(Holding Subsequence (316/326))
STEPDESC (1, 'Init', SSC, SST, SCFG);
STEPDESC (1, 'Closing Valves', SSC, SST, SCFG);
Steps and Transitions)
case SSC.CSTEP of
1: (Initial Step)
if FalloCI then
dosif_agua:=false;
end_if;
TRANS (FalloCI, 'Not InitCond', -1, SSC, SST, SCFG); (End of sequence)
TRANS (NOT FalloCI, 'InitCond OK', SSC.CSTEP+1, SSC, SST, SCFG); (Next step)
2:
if SSC.ONENTRY then
VALV_AGUA.LSP:=false;
RAMP_AGUA.LSTART:=false;
FIC_AGUA.MAN:=true;
FIC_AGUA.LOP:=0.0; (Close control valve)
end_if;
If (dosif_agua) AND SSC.ETIME >= 50 then
dosif_agua:=false;
end_if;
TRANS (SSC.ETIME >= 50 or not dosif_agua, 'Waiting for queue', -1, SSC,
SST, SCFG); (End of sequence)
end_case;
(Restarting subsequence(318))
STEPDESC (1, 'Init', SSC, SST, SCFG);
(Steps and Transitions)
case SSC.CSTEP of
1: (Initial Step)
TRANS (true, 'True', -1, SSC, SST, SCFG); (End of sequence)
end_case;
(Aborting subsequence(310))
STEPDESC (1, 'Closing Valves', SSC, SST, SCFG);
(Steps and Transitions)
case SSC.CSTEP of
1: (Initial Step)
VALV_AGUA.REM:=false;
VALV_AGUA.LSP:=false;
RAMP_AGUA.LSTART:=false;
FIC_AGUA.MAN:=true;
FIC_AGUA.LOP:=0.0; (Close control valve)
dosif_agua:=false;
TRANS (true, 'True', -1, SSC, SST, SCFG); (End of sequence)
end_case;
(Stopping subsequence(312))
STEPDESC (1, 'Closing Valves', SSC, SST, SCFG);
STEPDESC (2, 'Waiting for queue', SSC, SST, SCFG);
Steps and Transitions)
case SSC.CSTEP of
1: (Initial Step)
VALV_AGUA.REM:=false;
VALV_AGUA.LSP:=false;
RAMP_AGUA.LSTART:=false;
FIC_AGUA.MAN:=true;
FIC_AGUA.LOP:=0.0; (Close control valve)
Common
Common actions to be executed after the sequence execution.
NOTE: No default actions are defined in this section. However, if any action has to be taken after
execution of section, it has to be added here.
Part VII
Batch Phase Manager
Overview
This part provides a detailed description of the functions, pins, pin layout, and variables of the
function blocks of the Batch phase manager.
These function blocks do not reflect any specific installation.
WARNING
LOSS OF CONTROL
Perform a Failure Mode and Effects Analysis (FMEA) of your application, and apply preventive
and detective controls before implementation.
Provide a fallback state for undesired control events or sequences.
Provide separate or redundant control paths wherever required.
Supply appropriate parameters, particularly for limits.
Review the implications of transmission delays and take actions to mitigate.
Review the implications of communication link interruptions and take actions to mitigate.
Provide independent paths for control functions (for example, emergency stop, over-limit
conditions, and fault conditions) according to the safety analysis and applicable codes, and
regulations.
Apply local accident prevention and safety regulations and guidelines. 1
Test each implementation of this library for proper operation before placing it into service.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
1For additional information, refer to NEMA ICS 1.1 (latest edition), Safety Guidelines for the
Application, Installation, and Maintenance of Solid State Control and to NEMA ICS 7.1 (latest
edition), Safety Standards for Construction and Guide for Selection, Installation and Operation of
Adjustable-Speed Drive Systems or their equivalent governing your particular location.
Chapter 52
Batch Phase Manager
Overview
This chapter describes the Batch phase management.
Overview
The operation of the function block that is available for Batch Phase Manager is described in this
chapter.
The IBPHASE DFB belongs to the General Purpose Library and is used to monitor and manage
control phases with InBatch tool. The module is based on the ISA-S88 Standard, Part 1 (S88.01i)
and implements the status controller defined in this standard for controlling procedure model
components (phases, operations, and so on). Prior knowledge about the InBatch tool will facilitate
to understand the Batch phase manager block.
Function Description
You can use this DFB to change states in the process. In compliance with ISA-S88.01i, you can
use this DFB to initiate start, stop or emergency phases. In batch processes, this DFB can be used
to set up phases and operations.
The DFB implements phase state management and processes the commands received from:
The Supervision system (when phases are manually controlled by the operator)
The batch control subsystem (in which case the subsystem sends the commands and checks
the status of the phase to determine what action to take)
Other control phases
The table compares the functions that are available in the DFB:
Function IBPHASE
Management of state machine and commands according to ISA-S88 x
Management of operating modes according to ISA-S88: Manual (enables to change from one x
phase step to any other phase step), Semi (step advance with confirmation from the
operator), and Auto
Owner Management: Operator/Program x
Step time automatically calculated by the control block x
Automatic management of transitions through the IBTRANS function block x
Automatic management of phase detected failure through the IBFAILED function block x
Automatic management of phase steady-step marking through the IBSTABLESTEP function x
block
Possibility of displaying the phase graphically (active step and next level of transitions and x
steps) from the monitoring subsystem
NOTE: ‘x’ indicates that the functions are available in the DFB.
Program the steps and transitions that the phases implement (through ST or SFC language) while
the component (IBPHASE) allows the programmer to:
Manage the statuses of the phase and
Process the commands received from other levels as described above.
Function Description
Processing States and The DFB processes the commands received and determines the status of the
Commands control phase with the objective of determining the subphases (normal, hold,
continue, abort, so on.) and which step needs to run in each cycle of the
program.
Managing Entry Points in the The DFB enables to retain the step number with which the execution of the
Phase normal phase (Running) needs to be restarted (Restart) after being restarted
from held status (Held).
Handling of Detected The component manages controller detected failures (without user
Failures intervention from the Supervision system). The component manages this
detected failure and triggers the execution of the detected failure handling
subphase.
Auto reset disable Automatic reset (STOPPED →IDLE, automatically performs reset operation
without consuming any extra execution cycle) can be disabled by setting the
input pin (AUTORESETDIS) to a logical high when Owner is Operator.
Definition of Phase Statuses, Batch Phase Statuses, Phase Commands and Batch
Phase Commands
Statuses
The table describes the phase statuses and their descriptions:
Status Description
Idle Inactive operation. Waiting for command to start (Start) running.
Running Normal operation.
Held Operation put on hold. Waiting for command to Restart (Restart) to get operation to
running.
HeldForError Operation put on hold due to detected fail condition. Waiting for command to Restart
(Restart) to get operation to running.
Stopped Operation stopped. Waiting for command to get state (Reset) to Idle.
Paused Operation paused. Waiting for command to get state (Resume) to running.
Aborted Operation canceled. Waiting for command to get state (Reset) to get operation to Idle.
Complete Normal operation has finished. Requires an initialization order (Reset) to return to the Idle
status.
Holding A hold (Hold) command is received and the phase that allows the process to be changed
to a known status is executed. After this phase is finished, it automatically goes to the held
(Held) status.
HoldingForError A detected failure is automatically detected in the process (for example, a detected failure
in a control module), and the phase that allows the process to be changed to a known
status is executed. After this phase is finished, it automatically goes to the held
(HeldForError) status.
Restarting A restart command (Restart) is received while the phase is being held (Held). The phase
returns to the normal operation phase (Running). The normal operation status (Running)
is set automatically after the phase is complete.
Pausing A pause (Pause) command is received for a short period while the normal operation was
being executed (Running). The normal phase runs until it automatically goes to paused
(Paused) status.
Stopping An order to stop (Stop) has been received. To finish the phase in a controlled way is
executed (it is not possible to continue with it). The stopped operation status (Stopped) is
automatically activated after the phase is complete.
Aborting An order to end (Abort) has been received. A fast stop, which is not necessarily controlled
is executed. The aborted operation status (Aborted) is automatically activated after the
phase is completed.
Interlocked Operation cannot start as initial conditions are not met.
The (Held) status can also be reached (without receiving a command) if the control phase itself
detects a problem situation. The DFB has a signal that allows this situation to be communicated.
The DFB has the necessary means to be able to restart the Running phase from the last steady
step in which the initial run was held by a Hold command.
IBSTATE Description
IBREADY Ready for operation. The phase state is in Idle.
IBRUN Normal operation. The phase can be in Running, Restarting, Stopping, Aborting,
Holding, Pausing and Paused states.
IBHELD Operation put on hold. The phase state is in Held.
IBABORTED Operation canceled. The phase can be in Stopped or Aborted states.
IBDONE Normal operation has finished. The phase state is in Completed.
IBINTERLOCKED Operation cannot start from InBatch tool as initial conditions are not met or Owner is
Operator. The phase state is in Interlocked.
Commands
The table describes the phase commands and their descriptions:
Status Description
Start Allows the normal operation of the phase (Running) to be started.
Hold Allows the phase state to be put on hold (Holding, HoldingForError).
Restart Allows the phase state for continuing the operation (Restarting) and resume normal operation
(Running).
Stop Allows the phase state to be stopped (Running, Pausing, Paused, Holding, Held, or Restarting)
and the transition of state from running to stopping (Stopping).
Reset Triggers the transition to idle status (in Complete, Aborted, or Stopped status).
Pause Allows normal execution (Running) to be paused in the next steady phase status.
Resume Allows normal operation of the phase (Running) to be resumed from the paused (Paused)
status.
Abort Allows the phase state to be aborted (in any status except Idle, Complete, Aborting, and
Aborted) and the aborting state achieved from running (Aborting).
Completed Allows phase state to reach quiescent states or final state from certain transient states.
Stablestep 1 = Sends a command to mark the current step as a steady step, that is, the step with which
the phase will resume after its is held or the step on which the phase will be held after the phase
is paused.
0 = The signal is automatically set to 0 by the DFB after the signal is processed.
IBCOMMAND Description
IBSTART Allows the normal operation of the phase (IBRUN) to be started.
IBHOLD Allows the InBatch to be put on hold (IBHELD).
IBRESTART Allows the InBatch for continuing the operation and resume normal operation (IBRUN).
IBRESET Triggers the transition to Ready status IBREADY when batch phase state is in IBDONE
or IBABORTED. The command is automatically triggered by InBatch tool when
IBSTATE is Done or Aborted.
IBABORT Allows the InBatch to be aborted (in any batch phase status except Ready, Done, Run
(Aborting phase state) and Aborted).
Status Matrix
Description
The following table describes the phase status controller that the DFB implements:
The Held status can also be reached (without receiving a command) if the control phase itself
encounters a detected error. The block has a signal that allows this situation to be communicated.
The block has the necessary means to be able to restart the Running phase from the last steady
step in which the initial run was held by a Hold command.
Status Controller
Description
The following diagram describes the possible phases statuses and phase commands that the Unity
Pro component manages according to the ISA-S88 standard:
Next to the transition arrows, the phase commands that the component receives (from the
Supervision system or another higher level phase) are shown in black, and status/commands that
phase obtains from other blocks (for example, user logic) are shown in parenthesis.
Operating Modes
Mode Table
The following table provides the description of the phase operating modes of IBPHASE DFB:
Chapter 53
IBPHASE - Individual Batch Phase Manager
Overview
This chapter provides a detailed description of the functions, pins, pin layout, and variables of the
IBPHASE DFB.
Description
Initialization
If either the phase status is unknown or unlike any of the normal states or section is beginning with
the execution then normal state is initialized as Idle, regardless of whether a controller has
restarted or not. This initialization is done automatically.
DFB Representation
Representation
The DFB that is used in the program has the following aspect at the section level when
imported.You can use it in any of the programming languages, although it is designed for use with
the FBD language.
The figure shows an example of the IBPHASE DFB instance:
Implement the phase logic that controls the component in ST language to take advantage of the
phase control potentials making the phase reusable. That is, you can run simultaneously several
instances of the phase that you have implemented. This reduces engineering and maintenance
efforts when it is necessary to set up the same control phases in several process units.
Inputs
Inputs/Outputs
IBPHASE_ST_DDT Type
IBPHASE_CFG_DDT Type
Public Variables
IBPHASE_SC_DDT Type
Chapter 54
Auxiliary Functions of Batch Phase
Overview
This section describes the function blocks that supplement the IBPHASE DFB and that have the
objective of facilitating the programming of the control batch phase.
Section 54.1
IBTRANS
IBTRANS
Overview
This section describes the IBTRANS DFB.
Description
General
The main objective of IBTRANS DFB is to set up the control phase transitions based on the
condition to be evaluated and the next step to be executed when this expression is fulfilled.
Additionally, the DFB manages the information necessary to graphically represent the state of the
transitions and steps following the current step (DEST and DESTW fields of the IBPHASE_ST_DDT
phase state structure).
Include call to this function in the logic of the steps (normally in ST language) to program the
transitions between the phase steps.
Function Call
The function call is carried out from the steps of the control subphases (Running, Restarting,
Holding, and so on) normally in ST language to program the transitions between these steps.
If several IBTRANS calls are included in the same step and if more than one of them is fulfilled in
the same step execution cycle, the step corresponding to the transition that is fulfilled and was
programmed first will run. The number of IBTRANS calls from one single step is limited to 6.
TRANS (CONDITION := (*BOOL*),
DESC := (*string[22]*),
NEXTSTEP := (*INT*),
IBPHASE_SC := (*IBPHASE_SC_DDT*)
IBPHASE_ST := (*IBPHASE_ST_DDT*),
IBPHASE_CFG := (*IBPHASE_CFG_DDT*))
A function call example is included below:
4: (Wait for end of reactive dosing)
if IBSC.ONENTRY then
BISEN2_REACT.REM:=false;
BISEN2_REACT.LSP:=true;
end_if;
BISEN2_REACT.LSPSEL:=(OP01 < (IP01 - 10.0)); (Speed 1 or 2)
TRANS ((IP01 - COLA_REACT) <= OP01, 'Dosing finished?', IBSC.CSTEP+1,
IBSC, IBST, IBCFG);
In the previous example, the TRANS call included in step 4 of the phase corresponds to a IBTRANS
block instance to which the following parameters are passed:
(IP01 - COLA_REACT) <= OP01OS: Corresponds to the expression of the condition that
needs to be fulfilled for the transition to be executed. You can include complex expressions that
result in a Boolean value (true or false).
Dosing finished?: Corresponds to the description of the transition.
IBSC.CSTEP+1: Corresponds to the next step that needs to be executed when the transition is
fulfilled. In this case, the next step (step 5) is executed after the current step (step 4). You can
include any expression jumping to an existing step in the phase.
IBSC: Corresponds to the SC public variable of the IBPHASE block instance that is controlling
the phase execution.
IBST: Corresponds to the DDT_ST variable of the IBPHASE block instance that is controlling the
phase execution.
IBCFG: Corresponds to the DDT_CFG variable of the IBPHASE block instance that is controlling
the phase execution.
Inputs
Inputs/Outputs
Section 54.2
IBFAILED
IBFAILED
Overview
This section describes the IBFAILED DFB.
Description
General
The main objective of the IBFAILED DFB is to report detected errors to the batch phase
management block (IBPHASE) during phase execution so that the HoldingFE subphase is
triggered.
Function Call
The function call is made from the Running, Restarting, Pausing, or Paused control sub phase
steps normally in ST language with the purpose of reporting detected errors in the process that is
being controlled. The detected error requires the hold phase to be executed (HoldingFE).
A function call example is included below:
(Detected failure condition monitoring after initializations)
if IBPHASE.CSTEP > 0 and FAILCOND then
FAILED (IBSC); (Trigger execution of the Hold phase)
end_if;
In the previous example, the FAILED call that is included in the logic monitors the detected error
conditions in each execution cycle (in this particular case, but could be associated with a specific
step) corresponds to a IBFAILED DFB block instance to which the following parameters are
passed:
IBPhase: Corresponds to the name of the SC public variable of the IBPHASE block instance
that is controlling the execution of the phase.
Inputs/Outputs
Section 54.3
IBSTABLESTEP
IBSTABLESTEP
Overview
The section describes the IBSTABLESTEP DFB.
Description
General
The main objective of the IBSTABLESTEP DFB is to report to the batch phase management block
(IBPHASE) that the current running phase step corresponds to a step, that is, the re-entry point in
the normal execution (Running) phase executes after restarting execution (Restarting).
Function Call
The function call is performed from the Running control sub phase steps normally in ST language
for the purpose of reporting. The current step is the entry point to which the program should return
when the Running sub phase is resumed after finishing the Restarting sub phase. Basically, it
enables to resume the phase execution that verifies the appropriate actions are performed or not.
For example, suppose a valve has to be opened. After the valve is opened, the next step involves
turning on a pump. While waiting for the valve to open, a detected failure that makes the phase
stop occurs (Holding sub phase execution). You can resume execution by running the restart
(Restarting) sub phase. After this, the program returns to the normal running sub phase (Running).
After the program goes back to this Running sub phase, the intention is to make another attempt
at opening the valve (because most likely, it has been closed during the Holding sub phase) not to
start the pump in proceeding directly. Therefore, in the valve opening step, the step is marked and
does not call the function IBSTABLESTEP in the pump starting step.
The following is an example of a function call:
0: (End Water dosing)
if IBSC.ONENTRY then
RAMP_AGUA.LSTART:=false;
FIC_AGUA.REM:=false;
FIC_AGUA.MAN:=true;
FIC_AGUA.LOP:=0.0;
VALV_AGUA.LSP:=false;
STABLESTEP (IBSC);
end_if;
TRANS (VALV_AGUA.LOWPOS, 'Valve Closed?', IBSC.CSTEP+1, IBSC, IBST,
IBCFG);
In the previous example, the STABLESTEP call included in the logic that monitors detected failure
conditions in each execution cycle (in this particular case, but it could be associated with a specific
step) corresponds to a IBSTABLESTEP DFB block instance to which the following parameters are
passed:
IBPhase: Corresponds to the name of the SC public variable of the IBPHASE block instance
that is controlling the phase execution.
Inputs/Outputs
Section 54.4
IBSTEPDESC
IBSTEPDESC
Overview
This section describes the IBSTEPDESC DFB.
Description
General
The main objective of the IBSTEPDESC DFB is to assign descriptions to the steps that are defined
in the phase to allow you to monitor them from the Supervision system.
Function Calls
The function call is made from the control sub phase steps (Running, Restarting, Holding, and so
on) at the beginning of the code to provide the description of the sub phase steps for their represen-
tation in the monitoring program. It is normally written in ST language.
Include as many IBSTEPDESC calls as there are steps defined in the sub phase or as there are
steps that need to be represented in the Supervision system.
The syntax of the function is the following:
STEPDESC STEPNUMBER := (INT),
DESC := (string[18]),
IBPHASE_SC := (IBPHASE_SC_DDT),
IBPHASE_ST := (IBPHASE_ST_DDT),
IBPHASE_CFG := (IBPHASE_CFG_DDT),
The following is an example of a function call:
(Running or Pausing Sub phase (302 / 314))
(Step descriptions)
STEPDESC (1, 'Init', IBSC, IBST, IBCFG);
STEPDESC (2, 'Valves ON', IBSC, IBST, IBCFG);
STEPDESC (3, 'Wait Valves ON', IBSC, IBST, IBCFG);
STEPDESC (4, 'Dosing Reactive', IBSC, IBST, IBCFG);
STEPDESC (5, 'Motor OFF', IBSC, IBST, IBCFG);
STEPDESC (6, 'Waiting for queue', IBSC, IBST, IBCFG);
(Steps and Transitions)
case IBSC.CSTEP of
1: (#RunningStep0# Initial Step)
(Check initial conditions)
if IC_FAIL then
FalloCI := true;
FAILED (IBSC); (Initial conditions not satisfied)
else
FalloCI := false;
(Initialization)
In the above example, the STEPDESC calls included at the beginning of the sub phase correspond
to a IBSTEPDESC DFB block instance to which the following parameters are passed in case of the
first call:
1: Corresponds to step number 1.
Init: Corresponds to the definition of the step.
IBSC: Corresponds to the SC public variable of the IBPHASE block instance that is controlling
the phase execution.
IBST: Corresponds to the DDT_ST variable of the IBPHASE block instance that is controlling the
phase execution.
IBCFG: Corresponds to the DDT_CFG variable of the IBPHASE block instance that is controlling
the phase execution.
Inputs
Inputs/Outputs
Public Variables
Chapter 55
IBPARxx - Batch Phase Parameter Management
Overview
This chapter describes the IBPARxx DFB.
Description
General
The IBPAR05, IBPAR10 and IBPAR16 DFBs manage up to 5, 10, and 16 phase parameters (input
and output) respectively. The DFBs facilitate the management of parameters from advanced
control phases implemented with the General Purpose Library IBPHASE DFB.
These DFBs manage the phase parameters with a data structure (DDT) making it easier to
implement reusable control phases (the number of pins in a DFB is limited to 32 input pins and 32
output pins) because a single variable is used to provide access to the data that the phase
manages.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Input Parameter Optionally, the DFB initializes the values of the input parameters with a value (-0.0)
Consistency that enables to determine whether or not the applicable parameters of the phase
have been correctly downloaded onto the controller. This way, the phase can be
stopped from starting with an incomplete or inconsistent set of input parameters.
Owner The DFB manages control system level, which is the owner (Operator or Program)
based on the owner of the associated phase. As a result, it is responsible for defining
the input parameters of the phase.
Output Parameters The DFB manages the output parameters generated from the control phase.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
IBPARxx_ST_DDT Type
Public Variables
IBPARxx_SC_DDT Type
Chapter 56
USERPHASExx - User Defined Process Logic
Overview
This chapter describes the USERPHASExx DFB.
Description
General
It is an unprotected function block in which user can add the logic to manage phase states,
strategies depending upon the process controlled by the user. Sample codes are available in the
function block for the user reference.
Inputs
Inputs/Outputs
Chapter 57
IBPHASE - Example of Use
Overview
This chapter describes the example use of the IBPHASE DFB.
Description
General
This chapter gives an example of Batch phase manager controlled by the IBPHASE, IBTRANS,
IBSTABLESTEP, IBFAILED, and IBSTEPDESC DFBs.
The objective of the phase is to control the loading of water in a process unit. For this purpose, a
reusable component (DFB) is created so that user can use this phase in different process units by
only changing the connections of the component pins.
NOTE: Declaration of the auxiliary components manages the transitions (IBTRANS), steady-step
flags (IBSTABLESTEP), and notifications to trigger the holding sub phase (IBFAILED).
DFB Representation
Representation
The following diagrams include the calls to the phase created by the user as well as to the control
block that will control it (IBPHASE).
NOTE: The call to the block controls the execution of the advanced equipment module.
NOTE: The call to the functional block implements the control phase of the user and will reuse for
different process units if needed.
NOTE: The evaluation priority for these transitions is the order in which they are shown (up down;
these transitions are not functional, and have only been included as an example in this case). You
can define a maximum of 6 transitions.
3: (Wait for open valve)
TRANS (WATER_VALVE.HIGHPOS, 'Valve open?', IBSC.CSTEP + 1, IBSC, IBST,
IBCFG); (Next step)
4: (Wait for end of Water dosing)
if IBSC.ONENTRY then
if PARAM05.IP01 = 2.0 then (Dose)
WATER_RAMP.REM := false; (Set point of flow ramp)
WATER_RAMP.LTARGETSP:=PARAM05.IP03; (Desired set point)
WATER_RAMP.LSTART:=true;
WATER_FIC.REM:=true;
WATER_FIC.AUTO:=true;
WATER_FIC.LSP:=PARAM05.IP03; (Flow regulation)
end_if;
end_if;
TRANS ((PARAM05.IP02 - WATER_QUEUE) <= PARAM05.OP01, 'Dosing finished?',
IBSC.CSTEP + 1, IBSC, IBST, IBCFG);
5: (End Water dosing)
if IBSC.ONENTRY then
if PARAM05.IP01 = 2.0 then
WATER_RAMP.LSTART:=false;
WATER_FIC.REM:=false;
WATER_FIC.MAN:=true;
WATER_FIC.LOP:=0.0;
else
WATER_FCV.LSP:=0.0;
end_if;
WATER_VALVE.LSP:=false;
STABLESTEP (IBSC); (In this step, it will initialize the execution in case of Stop/Continue)
end_if;
Part VIII
Auxiliary Functions
Auxiliary Functions
Overview
This part provides a detailed description of the functions, pins, pin layout, and variables of the
function blocks of the auxiliary functions family.
Auxiliary function blocks can be used in conjunction with other DFBs to provide additional services
and data.
These function blocks do not reflect any specific installation.
WARNING
LOSS OF CONTROL
Perform a Failure Mode and Effects Analysis (FMEA) of your application, and apply preventive
and detective controls before implementation.
Provide a fallback state for undesired control events or sequences.
Provide separate or redundant control paths wherever required.
Supply appropriate parameters, particularly for limits.
Review the implications of transmission delays and take actions to mitigate.
Review the implications of communication link interruptions and take actions to mitigate.
Provide independent paths for control functions (for example, emergency stop, over-limit
conditions, and fault conditions) according to the safety analysis and applicable codes, and
regulations.
Apply local accident prevention and safety regulations and guidelines. 1
Test each implementation of this library for proper operation before placing it into service.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
1 For additional information, refer to NEMA ICS 1.1 (latest edition), Safety Guidelines for the
Application, Installation, and Maintenance of Solid State Control and to NEMA ICS 7.1 (latest
edition), Safety Standards for Construction and Guide for Selection, Installation and Operation of
Adjustable-Speed Drive Systems or their equivalent governing your particular location.
Chapter 58
ASELECT - Analog Signal Selector
Overview
This chapter describes the ASELECT DFB.
Description
General
The ASELECT DFB elects an analog signal from among a maximum of four signals based on the
chosen selection criterion.
This DFB can supplement the PIDCTL and AOUTPUT DFBs from the General Purpose Library.
Function Description
The main functions of the DFB are summarized in the following table:
Function Description
Selection The DFB selects the analog signal from among the input signals according to one of the
following criteria:
Maximum
Minimum
Direct selection
Feedback The DFB generates the signals needed to report to the DFBs. These DFBs generate the
analog signals whether or not their signals have been selected. This functionality is especially
useful when PID control is implemented in Override mode.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Chapter 59
ASELECT1 - Selector for Analog Signals with Monitoring Variables
Overview
This chapter describes the ASELECT1 DFB.
Description
General
The ASELECT1 DFB features the same functionalities of the ASELECT component except for the
fact that it has variables designed for monitoring the DFB and owner management purposes.
The component is designed to select an analog signal from among a maximum of 4 signals
depending on the chosen selection criterion.
You can supplement this DFB with the PIDCTL and AOUTPUT (as well as other) DFBs from the
General Purpose Library.
Function Description
The main functions of the DFB are summarized in the following table:
Function Description
Selection The DFB selects the analog signal from among the input signals according to one of the
following criteria:
Maximum
Minimum
Direct selection
Feedback The DFB generates the signals needed to report to the DFBs. These DFBs generate the
analog signals whether or not their signals have been selected. This functionality is especially
useful when PID control is implemented in Override mode.
Owner The DFB manages control system level, which is the owner (Operator or Program). Therefore,
it is responsible for selecting the signal.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
ASELECT1_ST_DDT Type
ASELECT1_CFG_DDT Type
Public Variables
ASELECT1_SC_DDT Type
Chapter 60
CONDSUM - Summary of Conditions
Overview
This chapter describes the CONDSUM DFB.
Description
General
The CONDSUM DFB is used to evaluate up to 15 signals that can be used, for example, as interlocks
or initial conditions. The DFB allows to evaluate the logic OR of these conditions to be evaluated.
Each of them can require individual resetting or be ignored according to the DFB configuration.
You can use this DFB as a supplement to the rest of the General Purpose Library DFBs to evaluate
their interlocking inputs.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Summary Condition Evaluation The DFB ORs the conditions.
Manual Reset Reset Conditions Conditions configured this way require resetting from the monitoring
system.
Bypass Enables the corresponding condition (one by one) to be ignored when
evaluating the expression.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
CONDSUM_ST_DDT Type
Bit Description
0 COND01
1 COND02
... ...
14 COND15
15 RESULT
Bit Description
0 BYPASS01
1 BYPASS02
... ...
14 BYPASS15
Bit Description
0 REARMREQ01
1 REARMREQ02
... ...
14 REARMREQ15
Public Variables
CONDSUM_SC_DDT Type
Chapter 61
CONDSUM1 - Interlock Condition Summary
Overview
This chapter describes the CONDSUM1 DFB.
Description
General
The features of the CONDSUM1 DFB are similar to those of the CONDSUM DFB. The CONDSUM1 DFB
is used to evaluate up to 7 conditions to implement interlocking strategies. The DFB allows to
evaluate the logic OR of these conditions. Each of them can require individual resetting or be
ignored (bypassed) according to the DFB configuration.
You can link this DFB to other DFBs of the General Purpose library to evaluate their interlocking
inputs and positions.
The table compares the functions of the CONDSUMx DFBs:
Function Description
The main functions of the DFB are described in the following table:
Function Description
Interlock Evaluation The DFB ORs the conditions giving Condition 1 priority over
Condition 2, Condition 2 priority over Condition 3, and so on.
Evaluation of interlock positions Each condition has a discrete position associated with it. The DFB
evaluates the position of each condition based on the active
conditions evaluated according to priority.
Interlocks Featuring Manual Resetting Process conditions configured this way require resetting from the
Supervision system.
Bypass Allows to bypass interlock conditions one by one.
The DFB allows to configure conditions that can be bypassed and
others that cannot.
Active Interlock Indication The DFB features output signals that report the state of each
interlock condition after internal logic has been applied (resetting
and bypassing). These signals can be used to implement program
logic, or to select the analog position for other DFBs that require it
(for example, AOUTPUT) by using an external multiplexer (for
example, ASELECT1).
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
CONDSUM_ST_DDT Type
Bit Description
0 Interlock 01. Refer to the ILCK01 (see page 653) output pin.
1 Interlock 02. Refer to the ILCK02 (see page 653) output pin.
... ...
6 Interlock 07. Refer to the ILCK07 (see page 653) output pin.
15 Resulting interlock. Refer to the ILCK (see page 653) output pin.
Bit Description
0 Active bypass (1) for interlock 01
1 Active bypass (1) for interlock 02
... ...
6 Active bypass (1) for interlock 07.
Bit Description
0 Interlock 01 requires resetting (1) or does not require resetting (0). Interlock 01 is reset by setting it to 0.
1 Interlock 02 requires resetting (1) or does not require resetting (0). Interlock 02 is reset by setting it to 0.
... ...
6 Interlock 07 requires resetting (1) or does not require resetting (0). Interlock 07 is reset by setting it to 0.
Public Variables
CONDSUM1_SC_DDT Type
Chapter 62
MSGBOX - Messages to the Operator
Overview
This chapter describes the MSGBOX DFB.
Description
General
The MSGBOX DFB offers a standard user interface mechanism and allows messages to be
displayed for the operator. This DFB enables to request confirmations and/or data without having
to configure customized interfaces to channel the messages
The DFB combined with the PlantStruxure General Purpose library for Unity function blocks allows
you to configure the format of the message for the operator so that you can format the message
from the program in Control incorporating icons, buttons, and/or data entry fields.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Message Display The DFB allows the message display to be activated/aborted. Only one message is
Management managed at a time. Therefore, the number of MSGBOX DFBs instantiated needs to be
equal to the number of simultaneous messages required per processing unit.
Icons Allows you to select the icon that needs to be shown on the user interface.
Enables to display the following icons:
Stop: To show diagnostics messages, for example.
Question mark: To show request messages for data entry, for example.
Exclamation mark: To show alert messages, for example.
Information: To show steps, or the status of the process in general, for example.
DFB Representation
Representation
This DFB has been specifically designed for use with the FBD language of the controller.
Inputs
Outputs
Inputs/Outputs
MSGBOX_ST_DDT Type
MSGBOX_CFG_DDT Type
The following table describes the MSGBOX_CFG_DDT type:
Public Variables
MODE Signal
Enables to configure the type of message that needs to be displayed and configure the icons (Stop,
Question, Exclamation, or information), buttons (OK and/or Cancel), and/or additional data (up to
2) that needs to be shown together with the message. The configuration loaded in this signal is
transferred to the low byte under the MSGBOX_ST.STW status word the moment that message
activation (SC.SHOW = 1) is requested.
The MODE signal is defined by adding the codes associated with the different format types to those
that can be shown in the message.
The codes as well as an example of their use is included in the following table:
Code Format
1 (2 0) Enable the OK button
Index
A ARAMP
DFB representation, 417
AALARM
function description, 416
DFB representation, 97
general description, 416
function description, 96
inputs, 418
general description, 96
inputs/outputs, 421
inputs, 98
outputs, 419
inputs/outputs, 101
public variables, 423
outputs, 100
ASELECT
public variables, 102
DFB representation, 629
ACALC
function description, 628
inputs, 90
general description, 628
advanced/process control
inputs, 630
ARAMP, 415
outputs, 631
IMCTL, 425
ASELECT1
LDLGCTL, 437
DFB representation, 635
PIDCTL, 447
function description, 634
PWMCTL, 465
general description, 634
RATIOCTL, 473
inputs, 636
SPLRGCTL, 481
inputs/outputs, 638
STEP3CTL, 489
outputs, 637
AHISIGNAL
public variables, 640
description, 74
auxiliary functions
DFB representation, 75
AALARM, 95
inputs, 76
AOUTPUTLP, 135
outputs, 77
ASELECT, 627
public variables, 80
ASELECT1, 633
analog devices control
CONDSUM, 641
CVALVE, 335
CONDSUM1, 649
MValveWithPos, 359
CVALVELP, 347
SDDEVCTL, 383
DEVCTL, 231
AOUTPUTLP
DEVLP, 245
DFB representation, 137
DEVMNT, 257
function description, 136
IBPARxx, 603
general description, 136
MOTOR2LP, 299
inputs, 138
MVALVEDLP, 321
inputs/outputs, 143
MVALVELP, 371
outputs, 141
PIDMUX, 457
public variables, 146
SDDEVLP, 399
SEQPARxx, 537
C D
commands DCALC
Batch phase control, 561 DFB representation, 149
sequential control, 505 function description, 148
CONDSUM general description, 148
DFB representation, 643 inputs, 150
function description, 642 outputs, 151
general description, 642 public variables, 152
inputs, 644 DEVCTL
inputs/outputs, 646 DFB representation, 234
outputs, 645 general description, 232
public variables, 648 inputs, 235
CONDSUM1 inputs/outputs, 241
DFB representation, 651 outputs, 237
function description, 650 public variables, 243
general description, 650 DEVLP
inputs, 652 DFB representation, 247
inputs/outputs, 654 function description, 246
outputs, 653 general description, 246
public variables, 656 inputs, 248
inputs/outputs, 253
outputs, 251
public variables, 256
DEVMNT G
DFB representation, 259
general
function description, 258
general function block concepts, 31
general description, 258
general concepts
inputs, 260
function block interface, 33
inputs/outputs, 262
modularity, 32
outputs, 261
set-point management, 35
public variables, 263
DINPUT
DFB representation, 155 H
function description, 154
HVALVE
general description, 154
DFB representation, 275
inputs, 156
function description, 274
inputs/outputs, 158
general description, 274
outputs, 157
inputs, 276
public variables, 160
inputs/outputs, 278
DOUTPUT
outputs, 277
DFB representation, 163
public variables, 279
function description, 162
general description, 162
inputs, 164
inputs/outputs, 166
I
outputs, 165 IBFAILED
public variables, 167 function call, 592
general description, 592
inputs/outputs, 593
E IBPARxx
DFB representation, 605, 607
EMCTL
function description, 604
public variables, 578
general description, 604
equipment module
public variables, 610
IBPHASE - example of use, 615
IBPHASE
description, 568
F DFB representation, 569
inputs, 570
function block interface
inputs/outputs, 571
basic configuration, 33
IBPHASE - example of use
continuous control, 33
DFB representation, 617
illustration, 34
reusable phase definition, 616
overview, 33
reusable phase logic, 618
sequential control, 33
IBPHASE-example of use
states and monitoring, 33
general description, 616
IBSTABLESTEP
function call, 595
general description, 595
inputs/outputs, 596
IBSTEPDESC
description, 598
M
MAINPUT1
function calls, 598
function description, 170
inputs, 600
general description, 170
inputs/outputs, 601
miscellaneous functions
public variables, 602
MSGBOX, 657
IBTRANS
modularity
function call, 587
example, 32
general description, 587
overview, 32
inputs, 589
MOTOR2
inputs/outputs, 590
DFB representation, 284
IMCTL
general description, 282
DFB representation, 427
inputs, 285, 293
function description, 426
outputs, 287
general description, 426
public variables, 296
inputs, 428
MOTOR2LP
inputs/outputs, 431
DFB representation, 301
outputs, 430
function description, 300
public variables, 434
general description, 300
InBatch
inputs, 302
auxiliary functions of InBatch, 585
inputs/outputs, 307
definition of statuses and commands, 560
outputs, 305
IBPHASE, 567
public variables, 310
operating modes, 565
MSGBOX
status controller, 564
DFB representation, 659
status matrix, 563
inputs, 660
InBatchl
inputs/outputs, 662
function description, 558
outputs, 661
overview, 558
public variables, 664
interlocking
MVALVE
function description, 37
DFB representation, 361
function description, 360
L general description, 360
inputs, 362
LDLGCTL
inputs/outputs, 367
DFB representation, 439
outputs, 365
function description, 438
public variables, 369
general description, 438
MVALVED
inputs, 440
DFB representation, 313
outputs, 441
function description, 312
public variables, 444
general description, 312
inputs, 314
inputs/outputs, 317
outputs, 316
public variables, 319
MVALVEDLP PWMCTL
DFB representation, 323 DFB representation, 467
function description, 322 function description, 466
general description, 322 general description, 466
inputs, 324 inputs, 468
inputs/outputs, 329 inputs/outputs, 470
outputs, 327 outputs, 469
public variables, 332 public variables, 472
MVALVELP
DFB representation, 373
function description, 372 R
general description, 372 RATIOCTL
inputs, 374 DFB representation, 475
inputs/outputs, 379 function description, 474
outputs, 377 general description, 474
public variables, 382 inputs, 476
inputs/outputs, 478
outputs, 477
O public variables, 480
on/off devices control
HVALVE, 273
MOTOR2, 281 S
MVALVED, 311 SDDEVCTL
DFB representation, 386
function description, 384
P general description, 384
PIDCTL inputs, 387
DFB representation, 449 inputs/outputs, 393
function description, 448 outputs, 390
general description, 448 public variables, 396
inputs, 450 SDDEVLP
inputs/outputs, 452 DFB representation, 401
outputs, 451 function description, 400
public variables, 455 general description, 400
PIDMUX inputs, 402
DFB representation, 459 inputs/outputs, 407
function description, 458 outputs, 405
general description, 458 public variables, 411
inputs, 460 SEQCTL1
inputs/outputs, 462 description, 510
outputs, 461 DFB representation, 511
public variables, 464 inputs/outputs, 512
process Unity component public variables, 515
list of function blocks, 27
statuses
InBatch, 560
sequential control, 504
STEP3CTL, 494
DFB representation, 491
function description, 490
general description, 490
inputs, 492
inputs/outputs, 495
public variables, 498
U
USERPHASExx
inputs, 613
inputs/outputs, 614