Modicon Libraries Devices Components User Guide
Modicon Libraries Devices Components User Guide
EIO0000002092 04/2020
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.
You agree not to reproduce, other than for your own personal, noncommercial use, all or part of
this document on any medium whatsoever without permission of Schneider Electric, given in
writing. You also agree not to establish any hypertext links to this document or its content.
Schneider Electric does not grant any right or license for the personal and noncommercial use of
the document or its content, except for a non-exclusive license to consult it on an "as is" basis, at
your own risk. All other rights are reserved.
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.
© 2020 Schneider Electric. All rights reserved.
2 EIO0000002092 04/2020
Table of Contents
Safety Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Part I General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 1 General Overview of Device Components . . . . . . . . . . . 19
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 2 Overview of Device Resources. . . . . . . . . . . . . . . . . . . . 21
List of Function Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Chapter 3 Overview of Supervision Services . . . . . . . . . . . . . . . . . 27
Function Blocks (DFB) Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Set-Point Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Part II Special Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter 4 Special Cards - Quantum . . . . . . . . . . . . . . . . . . . . . . . . 35
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Chapter 5 Special Cards - M340 . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Part III Circuit Breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Chapter 6 COMPACT Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Diagnostics Information Management . . . . . . . . . . . . . . . . . . . . . . . . . 71
EIO0000002092 04/2020 3
Chapter 7 MASTERPACT Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Diagnostics Information Management . . . . . . . . . . . . . . . . . . . . . . . . . 98
Chapter 8 HWCIRCUITBREAKER . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Diagnostics Information Management . . . . . . . . . . . . . . . . . . . . . . . . . 109
Chapter 9 OperationLimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Part IV Digital Protection Relays . . . . . . . . . . . . . . . . . . . . . 117
Chapter 10 SEPAM Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Diagnostics Information Management . . . . . . . . . . . . . . . . . . . . . . . . . 151
Part V Motor Controllers and Starters . . . . . . . . . . . . . . . . . 153
Chapter 11 TeSys T Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Diagnostics Information Management . . . . . . . . . . . . . . . . . . . . . . . . . 188
4 EIO0000002092 04/2020
Chapter 12 Tesys U Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Diagnostics Information Management . . . . . . . . . . . . . . . . . . . . . . . . . 214
Part VI Power Monitoring Devices . . . . . . . . . . . . . . . . . . . . 217
Chapter 13 PM Profile - Power Monitoring Profile. . . . . . . . . . . . . . . 219
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Diagnostic Information Management . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Chapter 14 Smart UPS Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Diagnostic Information Management . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Chapter 15 ACCUSINE PCS Profile . . . . . . . . . . . . . . . . . . . . . . . . . 259
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Diagnostic Information Management . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Communication Needs And/Or Requirements . . . . . . . . . . . . . . . . . . 277
EIO0000002092 04/2020 5
Part VII Progressive Starters. . . . . . . . . . . . . . . . . . . . . . . . . 279
Chapter 16 ATS Progressive Starter Profile . . . . . . . . . . . . . . . . . . . . 281
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Diagnostic Information Management . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Part VIII Variable Speed Drives . . . . . . . . . . . . . . . . . . . . . . . 305
Chapter 17 ATV Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
DFB Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Diagnostics Information Management . . . . . . . . . . . . . . . . . . . . . . . . . 363
Chapter 18 EMATVWarn - Extended Warnings of Process Drives
(Supports 9 Alarm registers) . . . . . . . . . . . . . . . . . . . . . . 367
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Chapter 19 EMATVWarn1 - Extended Warnings of Process Drives
(Supports 12 Alarm registers) . . . . . . . . . . . . . . . . . . . . . 405
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Part IX Weighing Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Chapter 20 Weighing Module Profile . . . . . . . . . . . . . . . . . . . . . . . . . 453
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
6 EIO0000002092 04/2020
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Diagnostic Information Management . . . . . . . . . . . . . . . . . . . . . . . . . 469
Configuration of PMESWT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
PMESWT DFB Work Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Part X Safety Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Chapter 21 XPSMC - XPSMC Reader (16 Inputs/ 32 Inputs) . . . . . . 483
DFB Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Public Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Part XI Communication Technologies. . . . . . . . . . . . . . . . . . 503
Chapter 22 Ethernet Technology. . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
22.1 CommunicationOK Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
22.2 ATV71/61 Control Block on Ethernet with IO Scanning . . . . . . . . . . . 508
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Preparing the Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
ATV 71/61 IO Scanner Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 511
Modifying the ATV7161 IOScanner Configuration. . . . . . . . . . . . . . . . 514
Configuring the IO Scanning of the Controller . . . . . . . . . . . . . . . . . . . 517
22.3 Tesys T Control Block on Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Tesys T Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Preparing the Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Configuring the IO Scanning of the Controller . . . . . . . . . . . . . . . . . . . 523
22.4 Modbus Devices Used Through Gateway . . . . . . . . . . . . . . . . . . . . . . 525
Modbus Devices Used Through Gateway . . . . . . . . . . . . . . . . . . . . . . 526
TSXETG100 Gateway Configuration Description . . . . . . . . . . . . . . . . 529
Control Program Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
22.5 Configuration Procedure for Device DTM . . . . . . . . . . . . . . . . . . . . . . 533
Configuring Device DTM for Communication with Device Control
Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Selection of Profile/Parameter in Device DTM . . . . . . . . . . . . . . . . . . 549
22.6 Modbus TCPIP - Implicit with IOScanning. . . . . . . . . . . . . . . . . . . . . . 553
Creating an Application using Modbus TCPIP Communication
Technology (Implicit with NOE/CPU). . . . . . . . . . . . . . . . . . . . . . . . . . 553
EIO0000002092 04/2020 7
22.7 Modbus TCPIP - Implicit with Device DTM . . . . . . . . . . . . . . . . . . . . . 562
Modbus TCPIP - Implicit with Device DTM . . . . . . . . . . . . . . . . . . . . . 562
22.8 Modbus TCPIP - Explicit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Creating an Application using Modbus TCPIP Communication
Technology (Explicit).. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
22.9 Modbus TCPIP - Explicit with Gateway . . . . . . . . . . . . . . . . . . . . . . . . 584
Modbus Serial - Explicit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Chapter 23 Modbus over ULP Technology . . . . . . . . . . . . . . . . . . . . . 591
Creating a Project with $MASTERPACTMTZMBU for IFM connected to
Masterpact MTZ and Modbus Serial RJ45 Ports . . . . . . . . . . . . . . . . . 592
Creating a Project with $MasterpactMTZMBU for IFE or IFE stacked
with IFM connected to Masterpact MTZ and Modbus Ethernet RJ45
Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Chapter 24 Modbus Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
24.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Modbus Technology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Determining Timeout Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
24.2 Configuring the Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
ATV 31, ATV 312, and ATV 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
ATV 71 and ATV 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Tesys U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
Tesys T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
ATS 22 and ATS 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
SEPAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Compact and Masterpact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
24.3 Modbus Serial - Explicit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
Creating an Application using Modbus Communication Technology
Using M340/ M580 on Local Rack. . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
Creating an Application using Modbus Communication Technology
using Quantum Controller on X80 drop . . . . . . . . . . . . . . . . . . . . . . . . 620
Creating an Application using Modbus Communication Technology
using M580 Controller on X80 drop . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Chapter 25 Profibus Technology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
25.1 Profibus Communication Using PRM. . . . . . . . . . . . . . . . . . . . . . . . . . 630
Profibus Communication Using PRM. . . . . . . . . . . . . . . . . . . . . . . . . . 630
Chapter 26 CANOpen Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
26.1 Advantys Communication using IO Scanning . . . . . . . . . . . . . . . . . . . 654
Advantys Communication Using IO Scanning . . . . . . . . . . . . . . . . . . . 654
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
8 EIO0000002092 04/2020
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, service, 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.
EIO0000002092 04/2020 9
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.
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.
10 EIO0000002092 04/2020
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.
WARNING
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 death, serious 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.
EIO0000002092 04/2020 11
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.
12 EIO0000002092 04/2020
About the Book
At a Glance
Document Scope
This document describes Control Expert components of Modicon Libraries General Purpose and
its functionality.
This document does not cover any development procedures and internal functionality details.
Users of the Control Expert services are supposed to have a working knowledge in the
employment of Control Expert.
Validity Note
This document has been updated with the release of Modicon Libraries - General Purpose 2020.
General Purpose Library of device components support the following software versions of
Control Expert:
Control Expert V14.0 and V14.1.
EIO0000002092 04/2020 13
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.
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.
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.
14 EIO0000002092 04/2020
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.
EIO0000002092 04/2020 15
16 EIO0000002092 04/2020
Modicon Libraries General Purpose
General
EIO0000002092 04/2020
Part I
General
General
Overview
This part explains general overview of General Purpose device library and concepts implemented
for controlling devices.
EIO0000002092 04/2020 17
General
18 EIO0000002092 04/2020
Modicon Libraries General Purpose
General Overview of Device Components
EIO0000002092 04/2020
Chapter 1
General Overview of Device Components
Introduction
The Modicon Libraries General Purpose provides DFBs that have been pre-configured and tested
by Schneider Electric and that are designed specifically for automating the control of Schneider
Electric devices such as variable-speed drives, starters, and power meters.
The Control (functional blocks, components, and libraries) and the monitoring resources
(components for Supervision) provide common required functions, facilitating the development of
control systems.
The system provides Control function blocks (DFB) for control.
To automate and simplify the implementation of control systems of the electrical devices, you can
use these resources with the tools for massive code generation and for the synchronization of
control and monitoring subsystems.
You can link the resources that are specifically designed for device control purposes with other
generic resources for discrete, continuous, and/or batch process management included in
Modicon Libraries - General Purpose. You can use device control function with communication
objects (TCP, EIP, Modbus) for data monitoring and control.
This document describes the basic concepts and details of each function blocks (DFBs) to
implement the device control functions.
EIO0000002092 04/2020 19
General Overview of Device Components
20 EIO0000002092 04/2020
Modicon Libraries General Purpose
General Overview of Device Resources
EIO0000002092 04/2020
Chapter 2
Overview of Device Resources
Overview
This chapter lists the resources designed for device control automation purposes.
WARNING
UNINTENDED EQUIPMENT OPERATION
Only authorized and suitably trained personnel have to implement an industrial control scheme
or application using these function blocks.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
EIO0000002092 04/2020 21
General Overview of Device Resources
22 EIO0000002092 04/2020
General Overview of Device Resources
EIO0000002092 04/2020 23
General Overview of Device Resources
24 EIO0000002092 04/2020
General Overview of Device Resources
EIO0000002092 04/2020 25
General Overview of Device Resources
26 EIO0000002092 04/2020
Modicon Libraries General Purpose
Supervision Services
EIO0000002092 04/2020
Chapter 3
Overview of Supervision Services
Overview
This chapter describes the concepts implemented by the resources used for device Supervision
purposes.
EIO0000002092 04/2020 27
Supervision Services
Overview
The Control function blocks for devices provide an interface that allows the DFBs to be configured,
monitored, and controlled both from the monitoring subsystem and from the control subsystem
itself.
The following interfaces are provided:
Basic Configuration
Control
States and Monitoring
Variables
Basic Configuration
DFB public variables for static and identified data are in engineering time (for example, range for
an input channel, refreshing communication variables and so on).
Control
DFB input and output pins:
enable issuing commands from other program blocks or sections.
provide the DFB status to allow implementing switching operations (for example, device
controlled from HMI/SCADA system, ExtControlled output pin), detected failures (for
example, communication interruption), alarm (for example, thermal trip alarm), and so on.
28 EIO0000002092 04/2020
Supervision Services
Variables
Variables communicate with devices. If you use components with or Ethernet-based
communications, the DFBs have an Inputs input DDT and an Outputs output DDT to
communicate with the actual physical device. Allocate these variables (%MWX) to the memory
segment reserved for communications so that the device control mechanisms work correctly.
When you use Modbus-based communications, use a Modbus port that serializes the requests
sent to the devices on the bus (messaging).
EIO0000002092 04/2020 29
Supervision Services
Set-Point Management
Overview
The blocks used for device control purposes 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 issued towards
the block are those generated from the monitoring subsystem.
NOTE: The dynamic symbols and the faceplates corresponding to the General Purpose library
devices are used to implement the control function for block resetting (as long as the block is in
Operator mode). If you want to perform additional control actions (Run, QuickStop, and so on)
from faceplates, use the control blocks included in the General Purpose library for process.
Program
Generates commands from the control program (Control). The DFBs receive these commands
through the input and output pins of the DFBs. The Owner variable is implemented in the devices
in the ***_ST.CFGW.1 and is set to 0 to specify program-based control.
30 EIO0000002092 04/2020
Supervision Services
Monitoring
Overview
The function blocks in the General Purpose library have Monitoring mode (which you can select by
setting the ControlCommand input to FALSE) that allows the device to be monitored in a
communications-based manner independently of the state of the control inputs. This way, the
control block only performs read operations on the device and updates the output variables of the
block without sending any commands.
You can use the operating mode if switching operations are carried out on the device locally
through a physical screw terminal.
NOTE: If the block is in Monitoring mode (ControlCommand set to FALSE), it resets
communication interruptions through the program or HMI/SCADA system.
If you configure the device to be controlled and monitored completely by the PLC in a
communications-based manner, set this variable to TRUE.
EIO0000002092 04/2020 31
Supervision Services
32 EIO0000002092 04/2020
Modicon Libraries General Purpose
Special Cards
EIO0000002092 04/2020
Part II
Special Cards
Special Cards
Overview
This part provides the detailed description, pin layout, pin description, operator screen of the device
control blocks of the Special Cards family.
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.
EIO0000002092 04/2020 33
Special Cards
34 EIO0000002092 04/2020
Chapter 4
Special Cards - Quantum
Overview
This chapter describes the quantum special cards.
35
Description
General
The Q140EHC10500 special inrack card DFB is the control block to manage a high speed counter
with 5 channels. It uses 5 equivalent, independently usable counters. The mapping value is 12
%IW-3X and 12 %MW-4X
The Q140EHC20200 special inrack card DFB is the control block to manage a high speed counter
with 2 channels. It is a two-channel module suited for high-speed counting applications up to
500 kHz or for applications that require a quadrature counter interface. The mapping value is 6
%IW-3X and 6 %MW-4X.
These DFBs are specific for the particular special card model to handle the data transfer and
conditioning. These DFBs receive the initial addresses of the configured STATE RAM memory
areas plus the mapping model (1X versus 3X) to transfer the data from/to the special card.
36
DFB Representation
Representation
The following figure represents functional modules of special card Quantum:
Parameter Components
Q140EHC10500 Q140EHC20200
Input Channel X –
37
Inputs
38
Outputs
39
Inputs/Outputs
40
Modicon Libraries General Purpose
Special Cards - M340
EIO0000002092 04/2020
Chapter 5
Special Cards - M340
Overview
This chapter describes the special cards.
EIO0000002092 04/2020 41
Special Cards - M340
Description
General
The special inrack cards, that are used for high speed counting are available with M340 controller.
There are 2 control blocks supporting 2 and 8 channels respectively, which can be configured to
perform different functions.
The 2 control blocks are:
BMXEHC0200: This high-speed control blocks supports 2 channels. Each of these high speed
counter channels supports up to 9 functions.
BMXEHC0800: This high-speed control blocks supports 8 channels. Each of these high speed
counter channels supports up to 6 functions.
Function Description
The control blocks that are available supports 2 IO DDTs to obtain the information from the
hardware, T_SIGN_CPT_BMX and T_UNSIGN_CPT_BMX.
You have to select the I/O DDT type from the respective application template of the module. The
function block is generated based on the selection of I/O DDT. This block packages the data for
operator information.
42 EIO0000002092 04/2020
Special Cards - M340
DFB Representation
Representation
This DFB is designed for the use of packaging signed data from the T_SIGN_CPT_BMX and
T_UNSIGN_CPT_BMX counter block.
This figure represents T_SIGN_CPT_BMX DFB in Control Expert:
EIO0000002092 04/2020 43
Special Cards - M340
Inputs
N/A
44 EIO0000002092 04/2020
Special Cards - M340
Outputs
N/A
EIO0000002092 04/2020 45
Special Cards - M340
Inputs/Outputs
For structure of I/O DDT, refer to standard Control Expert Help file.
46 EIO0000002092 04/2020
Modicon Libraries General Purpose
Circuit Breakers
EIO0000002092 04/2020
Part III
Circuit Breakers
Circuit Breakers
Overview
This part provides the detailed description, pin layout, pin description, operator screen of the device
control blocks of the Circuit Breakers.
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.
EIO0000002092 04/2020 47
Circuit Breakers
48 EIO0000002092 04/2020
Modicon Libraries General Purpose
COMPACT Profile
EIO0000002092 04/2020
Chapter 6
COMPACT Profile
COMPACT Profile
Overview
This chapter describes the DFBs of Compact profile.
EIO0000002092 04/2020 49
COMPACT Profile
Description
General
The COMPACTNSX profile is the control function to manage Compact NSX electrical protection
circuit breakers.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Remote Resetting Allows resetting of the device.
Open/Close Allows circuit breaker to open and close.
Monitoring Allows the device measurement data to be monitored.
50 EIO0000002092 04/2020
COMPACT Profile
DFB Representation
Representation
The following figure represents the function module of COMPACTNSX profile:
NOTE:
The underlined parameters are specific for some components.
Data type of WarningOrderCode output pin for MBCOMPACTNSX is COMPACTWARNINGORDER.
Similarly, for MBUCOMPACTNSX the data type is INT
EIO0000002092 04/2020 51
COMPACT Profile
Parameters Components
Modbus Modbus over ULP
MBCOMPACTNSX MBUCOMPACTNSX
Inputs ModBusAddress X –
IFMModBusAddress – X
X : Parameter is available
– : Parameter is not available
NOTE:
If IFMModbusAddress is not configured then default value of 255 is considered.
For how to create project using CompactNSX circuit breakers,refer Communication
technologies (see page 591).
IFM v2 and above hardware supports these control functions.
52 EIO0000002092 04/2020
COMPACT Profile
Inputs
EIO0000002092 04/2020 53
COMPACT Profile
54 EIO0000002092 04/2020
COMPACT Profile
Outputs
EIO0000002092 04/2020 55
COMPACT Profile
56 EIO0000002092 04/2020
COMPACT Profile
EIO0000002092 04/2020 57
COMPACT Profile
58 EIO0000002092 04/2020
COMPACT Profile
EIO0000002092 04/2020 59
COMPACT Profile
60 EIO0000002092 04/2020
COMPACT Profile
EIO0000002092 04/2020 61
COMPACT Profile
62 EIO0000002092 04/2020
COMPACT Profile
Info Structure
Code with the information shown on the Control operator screen.The following table describes the
Info structure:
EIO0000002092 04/2020 63
COMPACT Profile
Timing diagram:
64 EIO0000002092 04/2020
COMPACT Profile
Inputs/Outputs
COMPACT_ST_DDT Type
COMPACT_CFG_DDT Type
EIO0000002092 04/2020 65
COMPACT Profile
Bit Description
0 Unknown device status or communication interruption. No variable refreshing.
1 Not ready.
2 Refer to the Closed status in the Status output pin (see page 55).
3 Inoperable device.
4 Alarm on device or repetitive detected fault alarm requires resetting.
5 communication interruption.
6 Requires resetting. A ResetFail is required.
7 Externally controlled.
8 Refer to the Reseting output pin (see page 55).
9 Refer to the EnableDFB input pin (see page 53).
Bit Description
0 Refer to the ResetFail input pin (see page 53).
1 Owner.
3 Refer to the Closed status in the Status output pin (see page 55).
6 Refer to the Open status in the Status output pin (see page 55).
7 Refer to the ControlCommand input pin (see page 53).
Bit Description
0 Refer to the Open status in the Status output pin (see page 55).
1 Refer to the Closed status in the Status output pin (see page 55).
2 Refer to the Trip status in the Status output pin (see page 55).
3 Refer to the TripElec status in the Status output pin (see page 55).
4 Refer to the NotAvailable status in the Status output pin (see page 55).
5 Refer to the MotorAvailable status in the Status output pin (see page 55).
6 Refer to the MotorMode status in the Status output pin (see page 55).
66 EIO0000002092 04/2020
COMPACT Profile
Bit Description
0 Refer to the Alarm201 code in the WarningCode output pin (see page 55).
1 Refer to the Alarm202 code in the WarningCode output pin (see page 55).
2 Refer to the Alarm203 code in the WarningCode output pin (see page 55).
3 Refer to the Alarm204 code in the WarningCode output pin (see page 55).
4 Refer to the Alarm205 code in the WarningCode output pin (see page 55).
5 Refer to the Alarm206 code in the WarningCode output pin (see page 55).
6 Refer to the Alarm207 code in the WarningCode output pin (see page 55).
7 Refer to the Alarm208 code in the WarningCode output pin (see page 55).
8 Refer to the Alarm209 code in the WarningCode output pin (see page 55).
9 Refer to the Alarm210 code in the WarningCode output pin (see page 55).
10 Refer to the LongTimeProtection code in the WarningCode output pin (see page 55).
11 Refer to the EarthLeakage code in the WarningCode output pin (see page 55).
12 Refer to the GroundFault code in the WarningCode output pin (see page 55).
Bit Description
0 Refer to the Order code in the WarningOrderCode output pin (see page 55).
1 Refer to the WrongPassword code in the WarningOrderCode output pin (see page 55).
2 Refer to the MbPadLocked code in the WarningOrderCode output pin (see page 55).
3 Refer to the InternalWarning code in the WarningOrderCode output pin (see page 55).
4 Refer to the OutOfOrder code in the WarningOrderCode output pin (see page 55).
5 Refer to the NeedReset code in the WarningOrderCode output pin (see page 55).
6 Refer to the AlreadyClosed code in the WarningOrderCode output pin (see page 55).
7 Refer to the AlreadyOpen code in the WarningOrderCode output pin (see page 55).
8 Refer to the AlreadyReset code in the WarningOrderCode output pin (see page 55).
9 Refer to the ManualMode code in the WarningOrderCode output pin (see page 55).
10 Refer to the NotPresent code in the WarningOrderCode output pin (see page 55).
11 Refer to the InProgress code in the WarningOrderCode output pin (see page 55).
12 Refer to the ResetForbidden code in the WarningOrderCode output pin (see page 55).
EIO0000002092 04/2020 67
COMPACT Profile
Bit Description
0 Refer to the OrderUnsuccessful code in the WarningOrderCode2 output pin (see page 55).
1 Refer to the WrongPassword code in the WarningOrderCode output pin (see page 55).
2 Refer to the ManualMode code in the WarningOrderCode output pin (see page 55).
3 Refer to the AlreadyClosed code in the WarningOrderCode output pin (see page 55).
4 Refer to the AlreadyOpen code in the WarningOrderCode output pin (see page 55).
5 Refer to the AlreadyReset code in the WarningOrderCode output pin (see page 55).
6 Refer to the ResourceNotPresent code in the WarningOrderCode output pin (see page 55).
7 Refer to the InhibitModeOn code in the WarningOrderCode output pin (see page 55).
8 Refer to the OutOfOrder code in the WarningOrderCode output pin (see page 55).
9 Refer to the NeedReset code in the WarningOrderCode output pin (see page 55).
10 Refer to the InProgress code in the WarningOrderCode output pin (see page 55).
11 Refer to the ResetForbidden code in the WarningOrderCode output pin (see page 55).
12 Refer to the IFMPadlocked code in the WarningOrderCode output pin (see page 55).
68 EIO0000002092 04/2020
COMPACT Profile
Public Variables
EIO0000002092 04/2020 69
COMPACT Profile
70 EIO0000002092 04/2020
COMPACT Profile
Overview
The diagnostic codes that the device can return are read on the FailCode output variable.
This code indicates that communications have not been established between IFE and TRIP UNIT
and can be reset:
FailCode[0]: 16#0004
FailCode[1]: 16#0000
FailCode[2]: 16#0004
or
FailCode[0]: 16#0007
FailCode[1]: 16#0200
FailCode[2]: 16#0001
or
FailCode[0]: 16#01FF
FailCode[1]: 16#0200
FailCode[2]: 16#0001
After the communications have been established, check Modbus client diagnostic codes for
FailCode [0] and FailCode [1]. The components make a distinction between detected read
request problems and write request problems:
FailCode[2]: 16#0001 Read
FailCode[2]: 16#0002 Write
EIO0000002092 04/2020 71
COMPACT Profile
72 EIO0000002092 04/2020
Modicon Libraries General Purpose
MASTERPACT Profile
EIO0000002092 04/2020
Chapter 7
MASTERPACT Profile
MASTERPACT Profile
Overview
This chapter describes the DFBs of the MASTERPACT profile.
EIO0000002092 04/2020 73
MASTERPACT Profile
Description
General
The MASTERPACT profile is used to manage the Masterpact and Masterpact draw-out/chassis
electrical protection circuit breakers.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Remote resetting Allows resetting of the device.
Open/Close Allows circuit breaker to open and close.
Monitoring Allows the device measurement data to be monitored.
74 EIO0000002092 04/2020
MASTERPACT Profile
DFB Representation
Representation
The following figure represents the function module of Masterpact profile:
NOTE:
The underlined parameters are specific to profiles supported by DFB.
Datatype of WarningOrderCode output pin for MBMASTERPACT and MBMASTERPACTC is
MASTERPACTSTATUS. Similarly, for MBUMASTERPACTMTZ, MBUMASTERPACTMTZC,
MBUMASTERPACTNx and MBUMASTERPACTNxC the datatype is INT
EIO0000002092 04/2020 75
MASTERPACT Profile
Parameters Components
Modbus Modbus over ULP
MBMAS- MBMAS- MBUMAS- MBUMASTER- MBUMAS- MBUMAS-
TER- TERPACTC TERPACT- PACTMTZC TERPACTNx TERPACT-
PACT MTZ NxC
Inputs ModBusAddress X X – – – –
IFMModBusAddress – – X X X X
Outputs ConnectedCE – X – X – X
DisconnectedCD – X – X – X
TestPositionCT – X – X – X
X : Parameter is available
– : Parameter is not available
NOTICE
COMMUNICATION INTERRUPTION
Provide possible combination of communication interruptions between Masterpact chassis and
PLC. Otherwise, it leads to loss of data.
Failure to follow these instructions can result in equipment damage.
76 EIO0000002092 04/2020
MASTERPACT Profile
The IO module rotary position has to be set to have Cradle Management for Masterpact BCM-
ULP.
NOTE:
If a configuration of IO module is changed the EnableDFB pin has to be reset.
MBMasterPactC, MBUMasterPactMTZC and MBUMasterPactNxC has to be used only if IO
module is configured for cradle management application.
Cradle management is always IO1 for EIFE.
For how to create project using Masterpact MTZ/Masterpact Nx circuit breakers,refer
Communication technologies (see page 591).
If IFMModbusAddress is not configured then default value of 255 is considered.
IFM v2 and above hardware supports these control functions.
EIO0000002092 04/2020 77
MASTERPACT Profile
Inputs
78 EIO0000002092 04/2020
MASTERPACT Profile
EIO0000002092 04/2020 79
MASTERPACT Profile
Outputs
80 EIO0000002092 04/2020
MASTERPACT Profile
EIO0000002092 04/2020 81
MASTERPACT Profile
82 EIO0000002092 04/2020
MASTERPACT Profile
84 EIO0000002092 04/2020
MASTERPACT Profile
EIO0000002092 04/2020 85
MASTERPACT Profile
86 EIO0000002092 04/2020
MASTERPACT Profile
EIO0000002092 04/2020 87
MASTERPACT Profile
88 EIO0000002092 04/2020
MASTERPACT Profile
Info
Code with the information shown on the Control operator screen.The following table describes the
Info structure:
TrippingCause
The register used to record the cause of a trip operation gives information regarding the cause of
a trip operation for basic protective functions. If a bit is set in this register, it means that the device
has tripped. The following table describes the reasons for tripping:
EIO0000002092 04/2020 89
MASTERPACT Profile
TrippingCauseExt
If bit 8 of TrippingCause is active, the following table describes the reasons for trip operation:
Bit TrippingCauseExt
0 Current imbalance.
1 Overcurrent, phase 1.
2 Overcurrent, phase 2.
3 Overcurrent, phase 3.
4 Overcurrent on neutral.
5 Undervoltage.
6 Overvoltage.
7 Voltage imbalance.
8 Excessive power.
9 Reverse power.
10 Underfrequency.
11 Overfrequency.
12 Phase rotation.
13 Load shedding based on current.
14 Load shedding based on power.
Timing diagram:
90 EIO0000002092 04/2020
MASTERPACT Profile
Inputs/Outputs
MASTERPACT_ST_DDT Type
MASTERPACT_CFG_DDT Type
EIO0000002092 04/2020 91
MASTERPACT Profile
Bit Description
0 Unknown device status or communication interruption. No variable refreshing.
1 Not ready.
2 Refer to the Closed status in the Status output pin (see page 80).
3 Inoperable device.
4 Alarm on the device or repetitive detected fault alarm requires resetting.
5 Communication interruption.
6 Requires resetting. A ResetFail is required.
7 Externally controlled.
8 Refer to the Reseting output pin (see page 80).
9 Refer to the EnableDFB input pin (see page 78).
10 TestPositionCT.
11 Charged.
12 Refer to the ReadyToClose status in the Status output pin (see page 80).
13 ConnectedCE.
14 Refer to the Open status in the Status output pin (see page 80).
15 Refer to the Trip status in the Status output pin (see page 80).
Bit Description
0 Refer to the ResetFail input pin (see page 78).
1 Owner.
3 Refer to the Closed status in the Status output pin (see page 80).
6 Refer to the Open status in the Status output pin (see page 80).
7 Refer to the ControlCommand input pin (see page 78).
92 EIO0000002092 04/2020
MASTERPACT Profile
Bit Description
0 Refer to the Open status in the Status output pin (see page 80).
1 Refer to the Closed status in the Status output pin (see page 80).
2 * Refer to the TestPositionCT status in the output pin (see page 80).
3 Refer to the TripSD status in the Status output pin (see page 80).
4 Refer to the TripSDE status in the Status output pin (see page 80).
5 Refer to the Discharged status in the Status output pin (see page 80).
6 Refer to the Charged status in the Status output pin (see page 80).
7 Refer to the NotReadyToClose status in the Status output pin (see page 80).
8 Refer to the ReadyToClose status in the Status output pin (see page 80).
9 Refer to the NotAvailable status in the Status output pin (see page 80).
10* Refer to the ConnectedCE status in the output pin (see page 80).
11* Refer to the DisconnectedCD status in the output pin (see page 80).
*
: Available only for MBMASTERPACTC, MBUMASTERPACTMTZC, MBUMASTERPACTNx and
MBUMASTERPACTNxC.
Bit Description
0 Refer to the LongTimePickUp code in the WarningCode output pin (see page 80).
1 Refer to the CurrentUnbalance code in the WarningCode output pin (see page 80).
2 Refer to the MaxCurrentPhase1 code in the WarningCode output pin (see page 80).
3 Refer to the MaxCurrentPhase2 code in the WarningCode output pin (see page 80).
4 Refer to the MaxCurrentPhase3 code in the WarningCode output pin (see page 80).
5 Refer to the MaxCurrentNeutral code in the WarningCode output pin (see page 80).
6 Refer to the MinVoltage code in the WarningCode output pin (see page 80).
7 Refer to the MaxVoltage code in the WarningCode output pin (see page 80).
8 Refer to the VoltageUnbalance code in the WarningCode output pin (see page 80).
9 Refer to the MaxPower code in the WarningCode output pin (see page 80).
10 Refer to the ReversePower code in the WarningCode output pin (see page 80).
11 Refer to the MinFrequency code in the WarningCode output pin (see page 80).
12 Refer to the MaxFrequency code in the WarningCode output pin (see page 80).
EIO0000002092 04/2020 93
MASTERPACT Profile
Bit Description
13 Refer to the PhaseRotation code in the WarningCode output pin (see page 80).
14 Refer to the LoadSheddingCurrent code in the WarningCode output pin (see page 80).
15 Refer to the LoadSheddingPower code in the WarningCode output pin (see page 80).
Bit Description
0 Refer to the GroundFault code in the WarningCode output pin (see page 80).
1 Refer to the EarthLeakage code in the WarningCode output pin (see page 80).
Bit Description
0 Refer to the Order code in the WarningOrderCode output pin (see page 80).
1 Refer to the WrongPassword code in the WarningOrderCode output pin (see page 80).
2 Refer to the InternalWarning code in the WarningOrderCode output pin (see page 80).
3 Refer to the ManualMode code in the WarningOrderCode output pin (see page 80).
4 Refer to the IncorrectCoilValue code in the WarningOrderCode output pin (see page 80).
5 Refer to the IncorrectNbrOfParam code in the WarningOrderCode output pin (see page 80).
94 EIO0000002092 04/2020
MASTERPACT Profile
Bit Description
0 Refer to the Order code in the WarningOrderCode output pin (see page 80).
1 Refer to the WrongPassword code in the WarningOrderCode output pin (see page 80).
2 Refer to the IFEPadLocked code in the WarningOrderCode output pin (see page 80).
3 Refer to the IFMPadLocked code in the WarningOrderCode output pin (see page 80).
4 Refer to the ResourceNotExist code in the WarningOrderCode output pin (see page 80).
5 Refer to the TimeoutDuringCommand code in the WarningOrderCode output pin (see page 80).
6 Refer to the ResetBeforeCommand code in the WarningOrderCode output pin (see page 80).
7 Refer to the InProgress code in the WarningOrderCode output pin (see page 80).
8 Refer to the AlreadyOpen code in the WarningOrderCode output pin (see page 80).
9 Refer to the AlreadyReset code in the WarningOrderCode output pin (see page 80).
10 Refer to the ManualMode code in the WarningOrderCode output pin (see page 80).
11 Refer to the NotPresent code in the WarningOrderCode output pin (see page 80).
12 Refer to the InhibitModeOn code in the WarningOrderCode output pin (see page 80).
EIO0000002092 04/2020 95
MASTERPACT Profile
Public Variables
96 EIO0000002092 04/2020
MASTERPACT Profile
Scalefactor REAL Scale factor for Masterpact NT/NW and Compact NSX Micrologix
5.0, 6.0 0r 7.0 trip units is 1.
Scale factor for Compact NSX Micrologix 5.2, 5.3, 6.2, 7.2 or 7.3 trip
units is 10.
NOTE: Public parameters are applicable only for MBMASTERPACT, and MBMASTERPACTC.
EIO0000002092 04/2020 97
MASTERPACT Profile
Overview
The diagnostic codes that the device can return are read on the FailCode output variable.
This code indicates that communications have not been established between IFE and TRIP UNIT
and can be reset:
FailCode[0]: 16#0004
FailCode[1]: 16#0000
FailCode[2]: 16#0004
or
FailCode[0]: 16#0007
FailCode[1]: 16#0200
FailCode[2]: 16#0001
or
FailCode[0]: 16#01FF
FailCode[1]: 16#0200
FailCode[2]: 16#0001
This code indicates that communications have not been established between IFE and IO modules
and can be reset:
FailCode[0]: 16#0005
FailCode[1]: 16#0000
FailCode[2]: 16#0004
After the communications have been established, check Modbus client diagnostic codes for
FailCode [0] and FailCode [1]. Components make a distinction between detected read
request problem and write request problem:
FailCode[2]: 16#0001 Read
FailCode[2]: 16#0002 Write
98 EIO0000002092 04/2020
MASTERPACT Profile
EIO0000002092 04/2020 99
MASTERPACT Profile
Chapter 8
HWCIRCUITBREAKER
HWCIRCUITBREAKER
Overview
This chapter describes the DFB of the Hardwired Circuit Breaker.
Description
General
The HWCIRCUITBREAKER control function is used to manage hardwired circuit breakers such as
MASTERPACT, COMPACT and other third-party circuit breakers.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Remote resetting Allows resetting of the device.
Open/Close Allows circuit breaker to open and close.
Monitoring Allows the device status to be monitored.
DFB Representation
Representation
The following figure represents the function module of Hardwired circuit breaker.
Inputs
Outputs
Inputs/Outputs
HWCB_ST_DDT
HWCB_CFG_DDT
Bit Description
1 Control Function is not ready to send command.
2 Circuit breaker is in closed state.
3 Control Function is in Fail state due to trip.
4 Control Function is in Warning state due to feedback
not obtained after command is sent.
6 Reset is required as control function is in Fail state.
7 Control function is externally controlled.
8 Reseting is in progress.
9 EnableDFB pin status.
10 Test position.
11 Spring is charged.
12 Breaker is ready to close.
13 Chassis is connected to breaker.
14 Circuit breaker is in opened state.
15 Trip status (SD as well as SDE).
Bit Description
0 ResetFail command obtained from HMI.
1 Owner
3 Close command
6 Open command
7 Control command
Bit Description
0 Circuit breaker is in opened state.
1 Circuit breaker is in closed state.
2 SD trip status.
3 SDE trip status.
4 Chassis connected status.
5 Chassis disonnected status.
6 Chassis test position status
7 Spring charged status.
8 Ready to close status
Overview
Diagnostic information describes the type of detected fail, by displaying diagnostic codes on the
FailCode output variable.
This code indicates that the device has SDE Electrical Trip:
FailCode[0]: 16#0002
FailCode[1]: 16#0000
FailCode[2]: 16#0005
Chapter 9
OperationLimit
OperationLimit
Overview
This chapter describes the Operation Limit DFB which helps you limit the number of commands
issued to HWCIRCUITBREAKER control function within the configured time.
Description
General
The OperationLimit control function is used to limit the number of commands to manage opening
and closing operation of hardwired circuit breaker.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Open/Close Limits the open and close commands issued to circuit breaker
control function.
Retries Number of command Retries.
Alert An alert is issued if the number of commands exceed the
configured Retries.
For example, if you configure the WatchTime as 4 seconds and Retries as 3 seconds, then you
can issue a total of 7 commands considering both open and close within 4 seconds.
DFB Representation
Representation
The following figure represents the function module of Operation limit.
Inputs
NOTE:
If EngParam is not connected then a default value of 60 seconds as WatchTime and 3
Retries are considered.
If EngParam is connected and WatchTime is 0 seconds, then there are no restrictions on
commands.
Outputs
Part IV
Digital Protection Relays
Chapter 10
SEPAM Profile
SEPAM Profile
Overview
This chapter describes the DFBs of SEPAM profile.
Description
General
The SEPAM profile is used to manage Sepam 20, 40, and 80 digital protection devices in a
communications-based manner.
The Sepam20MB is classified into two variants:
The MBSEPAM20CSTM DFB is the control block to manage the Sepam 20 digital protection
devices on a Modbus network for S (Substation),T (Transformer), M (Motor) variants of the
product.
The MBSEPAM20CB DFB is the control block to manage the Sepam 20 digital protection devices
on a Modbus network for B (Busbar) variant of the product.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Remote resetting Allows resetting of the device.
Opening/Closing Allows the element controlled by the Sepam to be opened or
closed.
Monitoring Allows the required parameter devices to be monitored.
DFB Representation
Representation
The following figure represents the functional module of Sepam profile:
WARNING
UNINTENDED EQUIPMENT OPERATION
When you configure the Last value parameter of the I/O scanner line, take into consideration
the behavior of the DFB when a communication interruption occurs.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Parameters Components
SEPAM 20 SEPAM 40 SEPAM 80
MB- MB- MB- MB- ESE-
SEPAM20CB SEPAM20CSTM SEPAM40C SEPAM80C PAM80C
Inputs ModBusAddress X X X X –
IOScannerStatus – – – – X
StatisticSelector X X X X –
InputRead1 – – – – X
InputRead2 – – – – X
InputRead3 – – – – X
Outputs Status X X – – –
(SEPAM20STATUS)
Status – – X – –
(SEPAM40STATUS)
Ststus – – – X X
(SEPAM80STATUS)
InputsMap X X – – –
IOMap – – X – –
(SEPAM40IOMAP)
IOMap – – – X X
(SEPAM80IOMAP)
StatisticConnector X X X X –
SEPAM_IO20 X X – – –
SEPAM_IO40 – – X – –
SEPAM_IO80 – – – X X
SEPAM_AMEA – X – – –
SEPAM_VMEA X – – – –
SEPAM_MEA – – X X X
CommunicationOK – – – – X
OutputData – – – – X
X: Parameter is available.
–: Parameter is not available.
Inputs
Outputs
Info
The code with the information is shown on the Control Expert operator screen. The following table
describes the Info:
Bit Description
0 Refer to the ModbusSecurity status in the Status output pin.
1 Refer to the RemoteSettings status in the Status output pin.
2 Refer to the CapacitiveInductive status in the Status output pin.
Bit Description
0 Shows the state of the output 01.
1 Shows the state of the output 02.
2 Shows the state of the output 03.
3 Shows the state of the output 04.
4 Shows the state of the output 05.
5 Shows the state of the output 0101.
6 Shows the state of the output 0102.
7 Shows the state of the output 0103.
8 Shows the state of the output 0104.
9 Shows the state of the output 0105.
10 Shows the state of the output 0106.
Bit Description
0 Shows the state of the digital input 11.
1 Shows the state of the digital input 12.
2 Shows the state of the digital input 13.
3 Shows the state of the digital input 14.
4 Shows the state of the digital input 21.
5 Shows the state of the digital input 22.
6 Shows the state of the digital input 23.
7 Shows the state of the digital input 24.
8 Shows the state of the digital input 25.
9 Shows the state of the digital input 26.
Timing diagram:
Bit Description
0 Shows the state of the digital input I101.
1 Shows the state of the digital input I102.
2 Shows the state of the digital input I103.
3 Shows the state of the digital input I104.
4 Shows the state of the digital input I105.
5 Shows the state of the digital input I106.
6 Shows the state of the digital input I107.
7 Shows the state of the digital input I108.
8 Shows the state of the digital input I109.
9 Shows the state of the digital input I110.
10 Shows the state of the digital input I111.
11 Shows the state of the digital input I112.
12 Shows the state of the digital input I113.
13 Shows the state of the digital input I114.
Bit Description
0 Shows the state of the LED 1.
1 Shows the state of the LED 2.
2 Shows the state of the LED 3.
3 Shows the state of the LED 4.
4 Shows the state of the LED 5.
5 Shows the state of the LED 6.
6 Shows the state of the LED 7.
7 Shows the state of the LED 8.
8 Shows the state of the LED 9.
9 Shows the state of the LED 10.
Timing diagram:
Inputs/Outputs
SEPAM_ST_DDT Type
SEPAM_CFG_DDT Type
Bit Description
0 Unknown device status or communication interruption. No variable
refreshing.
1 Not ready.
2 Module is running.
3 Inoperable device problem.
4 Alarm on the device or DFB (follow-up or screw terminal-based
control).
5 Communication interruption.
6 Requires resetting. ResetFail is required.
8 Refer to the Reseting output pin (see page 126).
9 Refer to the EnableDFB input pin (see page 124).
Bit Description
0 Refer to the ResetFail input pin (see page 124).
1 Owner.
3 Refer to the Close input pin (see page 124).
6 Refer to the Open input pin (see page 124).
7 Refer to the ControlCommand input pin (see page 124).
Bit Description
0 Refer to the Fault status in the Status output pin (see page 126).
1 Refer to the Opened status in the Status output pin
(see page 126).
2 Refer to the Closed status in the Status output pin
(see page 126).
3 Refer to the Trip status in the Status output pin (see page 126).
4 Refer to the LocalRemote status in the Status output pin
(see page 126).
5 Refer to the SettingAActive status in the Status output pin
(see page 126).
6 Refer to the SettingBActive status in the Status output pin
(see page 126).
7 Refer to the TimeOutdated status in the Status output pin
(see page 126).
8 Refer to the SettingMode status in the Status output pin
(see page 126).
9 Refer to the SynchronizationLost status in the Status output
pin (see page 126).
10 Refer to the DataLoss1Event status in the Status output pin
(see page 126).
11 Refer to the Event1Zone status in the Status output pin
(see page 126).
12 Refer to the PartialFault status in the Status output pin
(see page 126).
13 Refer to the MajorFault status in the Status output pin
(see page 126).
14 Refer to the DataLoss2Event status in the Status output pin
(see page 126).
15 Refer to the Event2Zone status in the Status output pin
(see page 126).
Bit Description
0 Refer to the Order in the WarningCode output pin (see page 126).
Public Variables
Timing diagram:
Overview
The diagnostic codes that the device can return are read on the FailCode output variable.
After the communications have been established, check Modbus client diagnostic codes for
FailCode [0] and FailCode [1]. The components make a distinction between detected read
request problem and write request problem:
FailCode[2]: 16#0001 Read
FailCode[2]: 16#0002 Write
It can be reset.
Part V
Motor Controllers and Starters
Overview
This part provides the detailed description, pin layout, pin description, operator screen of the device
control blocks of the Motor Controllers and Starters 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.
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 11
TeSys T Profile
TeSys T Profile
Overview
This chapter describes the DFBs of TeSys T profile.
Description
General
The TeSys T profile is used to manage TeSys T motor management system on different
communication networks (Ethernet network based on IO scanning, Ethernet network using fast IO
scanning, Ethernet network using messaging, Modbus network, Advantys STB I/O island or
Profibus using PRM gateway/PRM master).
Function Description
The main functions of the DFB are described in the following table:
Function Description
Control Device operation.
Address Forward/reverse direction of rotation.
Speed This function enables the change of speed (fast or slow) if you are
working with a 2-speed motor start (double winding).
Device status Displays the status of the device.
indication
Remote resetting Allows resetting of the device.
Control or Monitoring Enables you to control or monitor the device.
Owner Manages the control system which is the owner (Operator or
Program). Therefore, it is responsible for setting the control.
NOTE:
ETESYST and EIOSTESYST DFBs do not support corresponding device DTM for M340
controllers.
For establishing the communication with TesysT devices through IOScanning or by using DTM,
the device Unit ID for TesysT varies for different firmware versions. Hence default value is set
to 1, as it supports most of the firmware versions. In case of unsuccessful communication, you
may need to configure the correct device Unit ID in the configuration parameter.
DFB Representation
Representation
The following figure represents the functional module of TeSys T profile:
WARNING
UNINTENDED EQUIPMENT OPERATION
When you configure the Last value parameter of the I/O scanner line, take into consideration
the behavior of the DFB when a communication interruption occurs.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Parameters Components
Ethernet Mod- Advantys Profib-
Normal IO Fast IO Messaging bus (TESYS- sus (TE-
scanning (EIO- scanning (EMESTE- (MBTE- TCTL) SYSPB)
STESYST) (ETE- SYST) SYST)
SYST)
Inputs ModbusAddress – – – X – –
DeviceAddress – – X – – –
IOScannerStatus X X – – – X
CommunicationOK – – – – X –
StatisticSelector – – X X – –
Inputs X X – – X X
DTMInputs X X – – – –
Outputs CommunicationOK X X – – – X
StatusExt X X X X X X
(TESYSTSTATUSEXT)
AverageCurrent X – X X – X
TESYST_MEA X – X X – –
TESYST_MEAEXT X – X X – –
TESYST_MEAEXT1 – – – X – –
TESYST_MEAEV40 X – X X – –
StatisticConnector – – X X – –
Outputs X X – – X X
DTMOutputs X X – – – –
Inputs/ WorkMemory – – X X – –
Outputs
X: Parameter is available.
–: Parameter is not available.
Inputs
If the device is reset and Run pin is active, then the device will auto start. If manual start of the
device is required, then reset the Run pin followed by device.
NOTICE
UNINTENDED EQUIPMENT OPERATION
Reset the Run variable before resuming operation.
Failure to follow these instructions can result in equipment damage.
*
: Parameter is available for specific components.
1
: Parameter is available only for Ethernet normal IO scanning.
2: Parameter is available for Ethernet fast IO scanning.
3
: Parameter is available for Advantys components.
4
: Parameter is available only for Profibus components.
StatisticSelector
Variable is used to obtain statistics for the Modbus network (requests carried out, time between
requests, so on). This data provides information for using StatisticConnector pin within the
StatisticCounter DFB in General Purpose library for communication.
Outputs
Outputs* ANY_ARRAY_INT Holds an array structure with data sent to the device.
You can control the starter/controller with this output
variable. This variable is reserved for the DFB, and
You cannot use this variable directly. For the control
block to work properly, allocate the structure (%MWx).
Refer to the Communications Technologies
(see page 503).
The following table describes the OUTPUTSstructure:
Parameter Type Description
Outputs [0] INT Output control.
Outputs [1] INT System control.
Outputs [2] INT Reserved.
Outputs3 ANY_ARRAY_INT Data sent to the actuator.
*: Parameter is available only for specific components.
1
: Parameter is available only for Ethernet normal IO scanning.
2
: Parameter is available for Ethernet fast IO scanning.
3
: Parameter is available for Advantys components.
4
: Parameter is available only for Profibus components.
TESYST_MEA_DDT Type
TESYST_MEA is a data structure with device information. The following table describes the
TESYST_MEA_DDT:
TESYST_MEAEXT_DDT Type
TESYST_MEAEXT is a data structure with extended information about the device on Modbus
communications. The following table describes the TESYST_MEAEXT_DDT:
TESYST_MEAEV40_DDT Type
TESYST_MEAEV40 is a data structure with information about the device with an EV40 expansion
module on Modbus communications. The following table describes the TESYST_MEAEV40_DDT:
TESYST_MEAEXT1_DDT Type
TESYST_MEAEXT1 is a data structure with extended information on the device with Modbus
communications.
STATISTICCONNECTOR
StatisticConnector is information data used with Ethernet communication to obtain statistics
on the Ethernet network (requests carried out, time between requests, and so on). This structure
has been created to be used with the StatisticCounter DFB in General Purpose for
communication.
State
The following table describes the State variable:
Info
The following table describes the Info variable:
Inputs/Outputs
TESYST_ST_DDT Type
TESYST_ST is a device data structure that holds the minimum information required for performing
control and monitoring functions. The information used by the operator screen is readable/writable
from the HMI/SCADA system.
Bit Description
0 Unknown technological module status. No variable refreshing.
1 Not ready.
2 Technological module is running.
3 Inoperable device.
4 Alarm on the device or repetitive detected fault alarm requires resetting.
5 Communication interruption.
Bit Description
6 Requires resetting. ResetFail is required.
7 Refer to the ExtControlled output pin (see page 171).
8 Refer to the Reseting output pin (see page 171).
9 Refer to the EnableDFB input pin (see page 159).
Bit Description
0 Refer to the ResetFail input pin (see page 159).
1 Owner.
3 Refer to the Direction input pin (see page 159).
6 Refer to the Run input pin (see page 159).
7 Refer to the ControlCommand input pin (see page 159).
11 Refer to the LowFastSpeed input pin (see page 159).
12 Refer to the ThermalTest input pin (see page 159).
NOTE: The Owner bit enables to control the block from the TESYST_ST_DDT input/output
structure ignoring the input signals of the block. It enables control from a monitoring system (HMI,
SCADA, operator screen) in the Manual mode without using the programmed switching operation.
TESYST_CFG_DDT Type
TESYST_CFG is a data structure with device information. The information used by the operator
screen is readable from the HMI/SCADA system.
Bit Description
0 Refer to the Ready status in the Status output pin (see page 171).
1 Refer to the Activated status in the Status output pin (see page 171).
2 Refer to the Fail status in the Status output pin (see page 171).
3 Refer to the Warning status in the Status output pin (see page 171).
4 Refer to the Trip status in the Status output pin (see page 171).
5 Refer to the ResetAuth in the Status output pin (see page 171).
6 Refer to the ControlledPower status in the Status output pin (see page 171).
7 Refer to the MotorRunning status in the Status output pin (see page 171).
8 Refer to the HMIControlled status in the Status output pin (see page 171).
9 Refer to the MotorStarting status in the Status output pin (see page 171).
10 Refer to the AutoResetActive status in the StatusExt output pin (see page 171).
11 Refer to the FaultRequested status in the StatusExt output pin (see page 171).
12 Refer to the RapidCicleLockout in the StatusExt output pin (see page 171).
13 Refer to the LoadSheding in the StatusExt output pin (see page 171).
14 Refer to the HMILostComms in the StatusExt output pin (see page 171).
15 Refer to the MotorTransitionLockout in the StatusExt output pin (see page 171).
Bit Description
2 Refer to the Ground in the WarningCode output pin (see page 171).
3 Refer to the Thermal in the WarningCode output pin (see page 171).
5 Refer to the Jam in the WarningCode output pin (see page 171).
6 Refer to the Phase in the WarningCode output pin (see page 171).
7 Refer to the UnderCurrent in the WarningCode output pin (see page 171).
8 Refer to the Order in the WarningCode output pin (see page 171).
Bit Description
9 Refer to the ForcedLocalMode in the WarningCode output pin (see page 171).
10 Refer to the HMIPort in the WarningCode output pin (see page 171).
11 Refer to the InternalTmp in the WarningCode output pin (see page 171).
12 Refer to the Internal in the WarningCode output pin (see page 171).
15 Refer to the Network in the WarningCode output pin (see page 171).
Bit Description
0 Status of the digital input I1 on a controller base.
1 Status of the digital input I2 on a controller base.
2 Status of the digital input I3 on a controller base.
3 Status of the digital input I4 on a controller base.
4 Status of the digital input I5 on a controller base.
5 Status of the digital input I6 on a controller base.
6 Status of the digital input I7 on a controller base.
7 Status of the digital input I8 on a controller base.
8 Status of the digital input I9 on a controller base.
9 Status of the digital input I10 on a controller base.
Bit Description
0 Status and command of the output O1 on a controller base.
1 Status and command of the output O2 on a controller base.
2 Status and command of the output O3 on a controller base.
3 Status and command of the output O4 on a controller base.
Public Variables
Timing diagram:
Overview
The diagnostics codes the device can return are read from the FailCode output variable.
During the above detected FailCode the function block does not process any inputs and the
function blocks output displays the last processed state.
This detected FailCode can be reset by a rising edge to the EnableDFB input pin after correcting
the configuration of the function block.
Chapter 12
Tesys U Profile
Tesys U Profile
Overview
This chapter describes the DFBs of Tesys U profile.
Description
General
The Tesys U profile is used to manage the TesysU family of devices on different communications
networks (Modbus network or Advantys STB I/O island).
Function Description
The main functions of the template are described in the following table:
Function Description
Control Forward/reverse direction of rotation.
Device status Displays the status of the device.
indication
Remote resetting Allows resetting of the device.
Control or Monitoring Enables you to control and monitor the device.
Owner Manages the control system which is the owner (Operator or
Program). Therefore, it is responsible for setting the control.
DFB Representation
Representation
The following figure represents the functional module of TESYS U profile:
Inputs
If the device is reset and Run pin is active, then the device will auto start. If manual start of the
device is required, then reset the Run pin followed by device.
NOTICE
UNINTENDED EQUIPMENT OPERATION
Reset the Run variable before resuming operation.
Failure to follow these instructions can result in equipment damage.
Outputs
Status* TESYSUSTATUSST Holds data containing the information that the module
extracts from the status variable of starters or controllers
with advanced or multifunction control blocks.
The following table describes the status information:
Parameter Type Description
Ready BOOL 1 = Switch in ON position. Device is
operational.
PoleClosed BOOL 1 = Contacts are closed on power base.
Fault BOOL 1 = An inoperable device.
Warning BOOL 1 = An alarm is present on device.
Trip BOOL 1 = The Tesys protection has tripped.
State INT Numerical code corresponding to the state of
the starter.
Info INT Numerical code with the information on
statuses and required actions.
*: Parameter is available for specific components.
State
The following table describes the State variable:
Info
The following table describes the Info variable:
TESYSU_MEC_DDT Word
The following table describes the TESYSU_MEC_DDT word structure:
MecStatus Word
The following table describes the MecStatus word structure:
IOMap
The following table describes the IOMap variable:
Inputs/Outputs
TESYSU_ST_DDT Type
TESYSU_CFG_DDT Type
Bit Description
0 Unknown device status or communication interruption. No variable
refreshing.
1 Not ready.
2 Technological module is running.
3 Inoperable device.
4 Alarm on the device or repetitive detected fault alarm requires
resetting.
5 Communication interruption.
6 Requires resetting. ResetFail is required.
7 Refer to the ExtControlled output pin (see page 199).
8 Refer to the Reseting output pin (see page 199).
9 Refer to the EnableDFB input pin (see page 196).
Bit Description
0 Refer to the ResetFail input pin (see page 196).
1 Owner.
3 Refer to the Direction input pin (see page 196).
6 Refer to the Run input pin (see page 196).
7 Refer to the ControlCommand input pin (see page 196).
NOTE: The Owner bit enables to control the block from the TESYSU_ST_DDT input/output
structure ignoring the input signals of the block. It enables control from a monitoring system (HMI,
SCADA, operator screen) in the Manual mode without using the programmed switching operation.
Bit Description
0 Refer to the Ready status in the Status output pin (see page 199).
1 Refer to the PoleClosed status in the Status output pin
(see page 199)
2 Refer to the Fault status in the Status output pin (see page 199).
3 Refer to the Warning status in the Status output pin
(see page 199).
4 Refer to the Trip status in the Status output pin (see page 199).
10 Refer to the OA1 in the IOMap output pin (see page 199).
11 Refer to the OA3 in the IOMap output pin (see page 199).
12 Refer to the LO1 in the IOMap output pin (see page 199).
13 Refer to the LI1 in the IOMap output pin (see page 199).
14 Refer to the LI2 in the IOMap output pin (see page 199).
Bit Description
2 Refer to the Ground in the WarningCode output pin
(see page 199).
3 Refer to the Thermal in the WarningCode output pin
(see page 199).
4 Refer to the LongStart in the WarningCode output pin
(see page 199).
5 Refer to the Jam in the WarningCode output pin (see page 199).
6 Refer to the Phase in the WarningCode output pin (see page 199).
7 Refer to the UnderCurrent in the WarningCode output pin
(see page 199).
8 Refer to the Order in the WarningCode output pin (see page 199).
9 Refer to the ForcedLocalMode in the WarningCode output pin
(see page 199).
10 Refer to the Communication in the WarningCode output pin
(see page 199).
11 Refer to the InternalTmp in the WarningCode output pin
(see page 199).
Bit Description
12 Refer to the Internal in the WarningCode output pin
(see page 199).
15 Refer to the Module in the WarningCode output pin
(see page 199).
NOTE: All control blocks cannot show alarm codes. Check the device manual and the
WarningCode output variable.
Public Variables
Refresh* TIME Refresh time for device data on serial Modbus communications.
NOTE: This refresh operation is carried out on read variables. Write
requests are carried out when needed and have maximum priority.
ScanTime TIME Allows the time that the alarm signals are kept active to be configured.
Helps the monitoring subsystem to acquire the data for the alarms that
are automatically reset.
ResetMode BOOL Enables to configure the type of reset. This type of reset is used for
communication interruption and inoperable device.
The time defined in CommandCtrlWindow is used to define the
interval after which a reset needs to be carried out. The first reset is
carried out after the time defined in CommandCtrlWindow elapses.
The second reset is carried out after CommandCtrlWindow * 2
elapses, so on. If the value of CommandCtrlWindow is 0 s, its value
is not used and is instead replaced with a value of 1 s.
The following table describes the type of the reset:
Variable Description
value
FALSE Communications are/the device is reset with the ResetFail variable.
TRUE Communications are/the device is reset automatically.
MaxResetTime TIME When in automatic ResetMode, this variable is used to define the
maximum time that can elapse between 2 consecutive resets.
Refer to the Timing diagram below.
*: Parameter is available for specific components.
Timing diagram:
Overview
The detected error codes the device can return are read from the FailCode output variable.
During the above detected FailCode the function block does not process any inputs and the
function blocks output displays the last processed state.
This detected FailCode can be reset by a rising edge to the EnableDFB input pin after correcting
the configuration of the function block.
The inoperable device can be reset as long as ControlCommand is TRUE. Otherwise, it can be
reset only on the controllers through the screw terminal with the appropriate parameter
configuration.
NOTE: The diagnostics codes of device are available for Tesys, except for those that communicate
through the Advantys STB.
Part VI
Power Monitoring Devices
Overview
This part provides the detailed description, pin layout, pin description, operator screen of the device
control blocks of the Power Monitoring Devices 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.
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 13
PM Profile - Power Monitoring Profile
Overview
This chapter describes the DFBs of Power Monitoring profile.
Description
General
The PM profile is used to manage the Power logic series power meters on different communication
networks (Modbus or Ethernet).
The power meter is a multifunction, digital instrumentation and data acquisition device. It can
replace various meters, relays, transducers, and other components. You can install the power
meter at multiple locations within a facility.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Remote resetting Allows resetting of the device.
Monitoring Allows the device parameters to be monitored.
DFB Representation
Representation
The following figure represents the functional module of PM profile:
WARNING
UNINTENDED EQUIPMENT OPERATION
When you configure the Last value parameter of the I/O scanner line, take into consideration
the behavior of the DFB when a communication interruption occurs.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Parameters Components
Modbus Ethernet
MB- MB- MBPM MB- MBPM EPM800 EMPM800 EMPM EMPM
PM700 PM800 1200 PM9C 5350 (Depre- (Depre- 53xx 82xx
(Depre- (Dep- (Depre- cated) cated)
cated) recat- cated)
ed)
Inputs ModbusAd- X X X X X – – – –
dress
DEVICEAD- – – – – – – X X X
DRESS
IOSCAN- – – – – – X – – –
NERSTATUS
INPUTDA- – – – – – X – – –
TA1
INPUTDA- – – – – – X – – –
TA2
INPUTDA- – – – – – X – – –
TA3
Outputs Communi- – – – – – X – – –
cationOK
Statis- X X X X X – X X X
ticCon-
nector
Warning X X – – X X X X –
Warning- X X – – X X X X –
Code
PM_MEA X X – – X X X – –
PM9C_MEA – – – X – – – – –
PM1200_ – – X X – – – – –
sMEA
PM53xx- – – – – – – – X –
_MEA
PM82xx- – – – – – – – – X
_MEA
X: Parameter is available.
–: Parameter is not available.
Parameters Components
Modbus Ethernet
MB- MB- MBPM MB- MBPM EPM800 EMPM800 EMPM EMPM
PM700 PM800 1200 PM9C 5350 (Depre- (Depre- 53xx 82xx
(Depre- (Dep- (Depre- cated) cated)
cated) recat- cated)
ed)
Inputs/ WorkMemo- X X X X X – X X X
Outputs ry
PM_ST_DDT X X X X X X X X X
PM_CFG – – – – – – – X –
(PM_CF-
G_DDT)
PM_CFG – – – – – – – – X
(PM82xx-
_CFG_DDT)
PM_CFG – – X – – – – – –
(PM1200_C
FG_DDT)
PM_CFG – – – X – – – – –
(PM9C_CF-
G_DDT)
X: Parameter is available.
–: Parameter is not available.
Inputs
1
Parameter available only for MBPM800, MBPM5350,MBPM9C, MBPM1200,MBPM710.
2
Parameter available only for EMPM800, EMPM53xx (PM5320,PM5340) and EMPM82xx (PM8240,PM8244)
3
Parameter available only for EPM800
Outputs
Timing diagram:
Inputs/Outputs
PM_ST_DDT Type
PM_CFG_DDT Type
PM82xx_CFG_DDT
PM1200_CFG_DDT Type
PM9C_CFG_DDT Type
Bit Description
0 Unknown device status or communication interruption. No variable
refreshing.
1 Not ready.
2 Module is running.
3 Inoperable device.
4 Alarm on the device or repetitive detected fault alarm requires
resetting.
NOTE: Not applicable for EMPM82xx
5 Communication interruption.
6 Requires resetting. ResetFail is required.
8 Refer to the Reseting output pin (see page 225).
9 Refer to the EnableDFB input pin (see page 224).
Bit Description
0 Refer to the ResetFail input pin (see page 224).
1 Owner.
Public Variables
Timing diagram:
Overview
The diagnostic codes the device can return are read from the FailCode output variable.
Chapter 14
Smart UPS Profile
Overview
This chapter describes the DFB of Smart UPS profile.
Description
General
The MBSMARTUPS DFB is the control block to manage SMART UPS uninterrupted power supplies
based on a Modbus.
NOTE: The MBSMARTUPS DFB requires a Smart UPS device connected through an AP9622
communication card.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Device detected failure Monitors the inoperable devive.
Remote resetting Enables you to reset communicationinterruptions.
Monitoring Allows the device parameters to be monitored.
DFB Representation
Representation
The following figure represents MBSMARTUPS DFB in Control Expert:
Inputs
Outputs
SMARTUPS_DeviceStatus
The following table describes the SMARTUPS_DeviceStatus variables:
SMARTUPS_Warning
The following table describes the SMARTUPS_Warning variables:
SMARTUPS_Fail
The following table describes the SMARTUPS_Fail variables:.
Inputs/Outputs
SMARTUPS_ST_DDT Type
SMARTUPS_CFG_DDT Type
Bit Description
0 Refer to the ResetFail input pin (see page 246).
1 Owner.
Bit Description
0 Refer to the OnLine status in the Status output pin (see page 247).
1 Refer to the OnBattery status in the Status output pin (see page 247).
2 Refer to the Bypass status in the Status output pin (see page 247) .
3 Refer to the Warning status in the Status output pin (see page 247).
4 Refer to the Fail status in the Status output pin (see page 247).
5 Refer to the AVRBoost status in the Status output pin (see page 247).
6 Refer to the AVRTrim status in the Status output pin (see page 247).
7 Refer to the TurningOn status in the Status output pin (see page 247).
8 Refer to the BypassInternalFault status in the Status output pin (see page 247).
9 Refer to the GoingBypass status in the Status output pin (see page 247).
10 Refer to the BypassCmd status in the Status output pin (see page 247).
11 Refer to the Returning status in the Status output pin (see page 247).
12 Refer to the BypassMan status in the Status output pin (see page 247).
13 Refer to the ReadyToPower status in the Status output pin (see page 247).
14 Refer to the ReadyToProvide status in the Status output pin (see page 247).
Bit Description
0 Refer to the ReplaceBattery output pin (see page 247).
1 Refer to the LowBattery output pin (see page 247).
2 Refer to the Overload output pin (see page 247).
Bit Description
0 Refer to the LowBattShutdown status in the FailStatus output pin (see page 247).
1 Refer to the OverloadFault status in the FailStatus output pin (see page 247).
2 Refer to the RelayMalfunction status in the FailStatus output pin (see page 247).
3 Refer to the SleepMode status in the FailStatus output pin (see page 247).
4 Refer to the ShutdownMode status in the FailStatus output pin (see page 247).
5 Refer to the BatteryChargerFailure status in the FailStatus output pin (see page 247).
6 Refer to the BypassRelayMalfunction status in the FailStatus output pin
(see page 247).
7 Refer to the TemperatureFault status in the FailStatus output pin (see page 247).
8 Refer to the FanFailure status in the FailStatus output pin (see page 247).
9 Refer to the IsolationFanFailure status in the FailStatus output pin (see page 247).
10 Refer to the BypassSupplyFailure status in the FailStatus output pin (see page 247).
11 Refer to the OutputFailure status in the FailStatus output pin (see page 247).
12 Refer to the UPSFault status in the FailStatus output pin (see page 247).
13 Refer to the NoBatteriesAttached status in the FailStatus output pin (see page 247).
14 Refer to the AVRFault status in the FailStatus output pin (see page 247).
15 Refer to the InverterFault status in the FailStatus output pin (see page 247).
Bit Description
5 Refer to the Overload in the WarningCode output pin (see page 247).
6 Refer to the Low battery in the WarningCode output pin (see page 247).
7 Refer to the Replace battery in the WarningCode output pin (see page 247).
Public Variables
Timing diagram:
Overview
The diagnostic codes the device can return are read from the ErrorCode output variable.
Chapter 15
ACCUSINE PCS Profile
Overview
This chapter describes the DFB of Accusine PCS profile.
Description
General
The EACCUSINE DFB is the control block to manage family ACCUSINE PCS harmonic filters
based on an Ethernet network.
NOTE: To use the EACCUSINE DFB, the Magelis HMI has to be running Active Filter Runtime
Application version 5.1.12.1205 or higher.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Control Run/Stop command.
Monitoring Allows the device parameters to be monitored.
Remote resetting Allows resetting of the communication interruption.
Owner Manages the control system which is the owner (Operator or
Program). Therefore, it is responsible for setting the control.
For DFBs communicating by I/O scanning, variables read from the device retain their last value
when a communication interruption occurs. For details, refer to the description of the
corresponding output parameter (see page 126).
WARNING
UNINTENDED EQUIPMENT OPERATION
When you configure the Last value parameter of the I/O scanner line, take into consideration
the behavior of the DFB when a communication interruption occurs.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
DFB Representation
Representation
The following figure represents EACCUSINE DFB in Control Expert:
Inputs
Outputs
EACCUSINE_DeviceStatus
The following table describes the EACCUSINE_DeviceStatus variable:
EACCUSINE_Alarm
The following table describes the EACCUSINE_Alarm variable:
EACCUSINE_CriticalFail
The following table describes the EACCUSINE_CriticalFail variable:
EACCUSINE_NonCriticalFail
The following table describes the EACCUSINE_NonCriticalFail variable:
State
The following table describes the State variable:
Info
The following table describes the Info variable:
Timing diagram:
Inputs/Outputs
ACCUSINE_ST_DDT Type
ACCUSINE_CFG_DDT Type
Bit Description
0 Unknown device status or communication interruption. No variable refreshing.
1 Not ready.
2 Module is running.
3 Inoperable device.
4 Alarm on the device or repetitive detected fault alarm requires resetting.
5 Communication interruptions.
6 Requires resetting. ResetFail is required.
7 Refer to the ExtControlled output pin (see page 265).
8 Refer to the Reseting output pin (see page 265).
9 Refer to the EnableDFB input pin (see page 262).
Bit Description
0 Refer to the ResetFail input pin (see page 262).
1 Owner.
6 Refer to the Run input pin (see page 262).
7 Refer to the ControlCommand input pin (see page 262).
Bit Description
0 Refer to the Running status in the Status output pin (see page 267).
1 Refer to the EnableRemote status in the Status output pin (see page 267).
2 Refer to the Warning status in the Status output pin (see page 267) .
3 Refer to the Fail status in the Status output pin (see page 267).
4 Refer to the MaxCapacity status in the Status output pin (see page 267).
5 Refer to the ThermalLimit status in the Status output pin (see page 267).
6 Refer to the LowOrderHarmonic status in the Status output pin (see page 267).
Bits Description
0 Refer to the Fail_5V_OV(CR) in the CriticalFail output pin (see page 268).
1 Refer to the Fail_5V_UV(CR) in the CriticalFail output pin (see page 268).
2 Refer to the Fail_P15V_UV in the CriticalFail output pin (see page 268).
3 Refer to the Fail_L15V_UV in the CriticalFail output pin (see page 268).
4 Refer to the UserSetup in the CriticalFail output pin (see page 268).
5 Refer to the TimeOut in the CriticalFail output pin (see page 268).
6 Refer to the AutoDetect in the CriticalFail output pin (see page 268).
7 Refer to the HMILost in the CriticalFail output pin (see page 268).
8 Refer to the InvalidRating in the CriticalFail output pin (see page 268).
9 Refer to the PhaseRotation in the CriticalFail output pin (see page 268).
10 –
11 Refer to the DCBusOverV in the CriticalFail output pin (see page 268).
12 Refer to the DCBusLowV in the CriticalFail output pin (see page 268).
13 Refer to the EnclosureUnderT in the CriticalFail output pin (see page 268).
14 Refer to the F110COverT in the CriticalFail output pin (see page 268).
15 Refer to the BoardOverT in the CriticalFail output pin (see page 268).
Bit Description
0 Refer to the ACLineLoss in the NonCriticalFail output pin (see page 268).
1 Refer to the ACPhaseLoss in the NonCriticalFail output pin (see page 268).
2 Refer to the ACImbalance in the NonCriticalFail output pin (see page 268).
3 Refer to the ACOverVolt in the NonCriticalFail output pin (see page 268).
4 Refer to the ACFreq in the NonCriticalFail output pin (see page 268).
5 Refer to the Sensor in the NonCriticalFail output pin (see page 268).
6 Refer to the Frequency in the NonCriticalFail output pin (see page 268).
7 Refer to the IGBTA in the NonCriticalFail output pin (see page 268).
8 Refer to the IGBTB in the NonCriticalFail output pin (see page 268).
9 Refer to the IGBTC in the NonCriticalFail output pin (see page 268).
10 Refer to the IGBT1OverT in the NonCriticalFail output pin (see page 268).
Bit Description
11 Refer to the IGBT2OverT in the NonCriticalFail output pin (see page 268).
12 Refer to the IGBT3OverT in the NonCriticalFail output pin (see page 268).
13 Refer to the PhaseOverT in the NonCriticalFail output pin (see page 268).
14 Refer to the Filter in the NonCriticalFail output pin (see page 268).
15 Refer to the EnclosureOverT in the NonCriticalFail output pin (see page 268).
Bit Description
0 Refer to the MaxCapacity in the WarningCode output pin (see page 267).
1 Refer to the ThermalLimit in the WarningCode output pin (see page 267).
2 Refer to the LowOrderHarmonic in the WarningCode output pin (see page 267).
Public Variables
Overview
The diagnostic codes, the device can return are read from the ErrorCode output variable.
IOSCAN Communications
The EACCUSINE component needs 3 IOScan lines:
First IOScan line:
This IOScan line needs to be configured as follows:
UnitID: 255
Slave Syntax: Index
RD Ref Slave: 1
RD Length: 11
Last value (Input): Set to 0
WR Ref Slave: 0
WR Length: 0
The EACCUSINE section needs the input/output values (RD/WR Master Object) and heart bit of
the IOScan line.
RD Master Object:
The EACCUSINE DFB needs the Inputs1, Inputs2, and Inputs3. In the diagram given
above, Inputs1 (11 words) is mapped to %MW101, Inputs2 (2 words) is mapped to %MW112,
and Inputs3 (4 words) is mapped to %MW114 but the values needs to be filled from 3 different
variable sections of EACCUSINE memory.
WR Master Object:
The EACCUSINE DFB needs the outputs. In the diagram given above, outputs is mapped to
%MW100. This value is only used in the third IOScan line.
Part VII
Progressive Starters
Progressive Starters
Chapter 16
ATS Progressive Starter Profile
Overview
This chapter describes the DFBs of ATS Progressive Starter profile.
Description
General
The ATS progressive starter profile is used to manage ATS soft starters on a Modbus network.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Control Start/Stop command.
Inoperable device Monitors the inoperable device.
Remote resetting Allows resetting of the device.
Control Enables you to monitor the device.
You can control from the controller or with the wired
inputs/outputs of the speed driver.
DFB Representation
Representation
The following figure represents the functional module of ATS profile:
Parameters Components
Modbus
MBATS22 MBATS48
Inputs EnableDevice – X
QuickStop – X
Outputs WarningCode (ATS22WARNING) X –
WarningCode (ATSWARNING) – X
Status (ATS22STATUS) X –
Status (ATSSTATUS) – X
IOMAP (ATS22IOMAP) X –
IOMAP (ATSIOMAP) – X
Current – X
CurrentL1 X –
CurrentL2 X –
CurrentL3 X –
Torque – X
ActivePower – X
ThermicStatus – X
CosPhi – X
Frequency X –
Voltage X –
TotalStarts X –
TotalRunTime X –
LastStartTime X –
LastStartMaxC X –
TripCurrent X –
Inputs/Outputs ATS22_ST X –
ATS_ST – X
ATS22_CFG – X
ATS_CFG – X
X: Parameter is available.
–: Parameter is not available.
Inputs
Public variable values are loaded during the first enabling cycle.
EnableDevice * BOOL 1 = Valid if the EnableDFB variable is active.
The starter has to be enabled in order to be controlled.
* These parameters are available only with specific components.
If the device is reset and Run pin is active, then the device will auto start. If manual start of the
device is required, then reset the Run pin followed by device.
NOTICE
UNINTENDED EQUIPMENT OPERATION
Reset the Run variable before resuming operation.
Failure to follow these instructions can result in equipment damage.
QuickStop* BOOL 1 = Stops the starter quickly with fast stop ramp. It is state-based.
If there is a QuickStop, the Run bit has to be reset to resume
operation.
ModbusAddress INT Device address within the Modbus network.
* These parameters are available only with specific components.
Outputs
IOMap * ATSIOMAP Holds a data structure that contains information on the state
of the starter inputs and outputs.
The following table describes the IOMap:
Parameter Type Description
LIRUN BOOL 1 = The state of the digital input LIRUN.
LISTOP BOOL 1 = The state of the digital input LISTOP.
LI3 BOOL 1 = The state of the digital input LI3.
LI4 BOOL 1 = The state of the digital input LI4.
LO1 BOOL 1 = The state of the digital output LO1.
LO2 BOOL 1 = The state of the digital output LO2.
R1 BOOL 1 = The state of the digital output R1.
R2 BOOL 1 = The state of the digital output R2.
R3 BOOL 1 = The state of the digital output R3.
AO INT Range (0-10000). Shows the state of the
analog output.
TotalStarts* INT Number of times that the ATS 22 has started (W 274).
TotalRuntime* INT Total time (in hours) during which the ATS 22 has been
operating (W 273).
TripCurrent* INT Current present when last tripping event occurred (W 280).
StatisticConnector STATISTICCONNECTOR Information data is used with Modbus communications to
obtain statistics on the Modbus network (requests carried out,
time between requests, so on).
This structure has been created to be used within
StatisticCounter DFB in General Purpose library for
communication.
Parameter Type Description
Start BOOL 1 = The operation has started.
EndOk BOOL 1 = The operation has ended correctly.
EndNOk BOOL 1 = The operation has ended with a detected
error.
PartialTime DINT Partial time.
* These parameters are available only with specific components.
Info
The following table describes the Info variable of MBATS22:
Timing diagram:
Inputs/Outputs
ATS_CFG* ATS_CFG_DDT Device data structure with device information. Information used by
(see page 296) the operator screen is readable from the HMI or SCADA system.
WorkMemory ANY_ARRAY_INT The array is used in Modbus communications.
This variable is meant for use with a Modbus port that serializes
Modbus requests in an optimum manner.
*
These parameters are available only with specific components.
ATS22_ST_DDT Type
ATS_ST_DDT Type
ATS_CFG_DDT Type
ATS22_CFG_DDT Type
Bit Description
0 Unknown technological module status. No variable refreshing.
1 Not ready.
2 Device is running.
3 Inoperable device.
4 Alarm on the device (follow-up requires resetting).
5 Communication interruption.
6 Requires resetting. ResetFail is required.
7 Refer to the ExtControlled output pin (see page 287).
8 Refer to the Reseting output pin (see page 287).
9 Refer to the EnableDFB input pin (see page 285).
Bit Description
0 Unknown technological module status. No variable refreshing.
1 Not ready.
2 Device is running.
3 Inoperable device.
4 Alarm on the device or DFB (follow-up or screw terminal-based
control).
5 Communication interruption.
6 Requires resetting. ResetFail is required.
7 Refer to the ExtControlled output pin (see page 287).
8 Refer to the Reseting output pin (see page 287).
9 Refer to the EnableDFB input pin (see page 285).
Bit Description
0 Refer to the ResetFail input pin (see page 285).
1 Owner.
6 Refer to the Run input pin (see page 285).
7 Refer to the ControlCommand input pin (see page 285).
NOTE: The Owner bit enables to control the block from the ***_ST_DDT input/output structure
ignoring the input signals of the block. It enables control from a monitoring system (HMI, SCADA,
operator screen) in the Manual mode without using the programmed switching operation.
Bit Description
0 Refer to the ResetFail input pin (see page 285).
1 Owner.
4 Refer to the QuickStop input pin (see page 285)
5 Refer to the EnableDevice input pin (see page 285).
6 Refer to the Run input pin (see page 285).
7 Refer to the ControlCommand input pin (see page 285).
Bit Description
0 Refer to the Ready status in the Status output pin (see page 287).
1 Refer to the Running status in the Status output pin (see page 287).
2 Refer to the Trip status in the Status output pin (see page 287).
3 Refer to the Alarm status in the Status output pin (see page 287).
14 Refer to the ForcedLocalMode status in the Status output pin (see page 287).
15 Refer to the Ramping status in the Status output pin (see page 287).
Bit Description
0 Refer to the ReadyToSwitchOn status in the Status output pin (see page 287).
1 Refer to the SwitchedOn status in the Status output pin (see page 287).
2 Refer to the OperationEnabled status in the Status output pin (see page 287).
3 Refer to the Malfunction status in the Status output pin (see page 287).
4 Refer to the VoltageEnabled status in the Status output pin (see page 287).
5 Refer to the QuickStop status in the Status output pin (see page 287)
6 Refer to the SwitchOnDisabled status in the Status output pin (see page 287).
7 Refer to the Alarm status in the Status output pin (see page 287).
8 Refer to the ForcedLocalMode status in the Status output pin (see page 287).
9 Refer to the ResetAuthorization status in the Status output pin (see page 287).
10 Refer to the Running status in the Status output pin (see page 287).
11 Refer to the Accelerating status in the Status output pin (see page 287).
12 Refer to the Decelarating status in the Status output pin (see page 287).
Bit Description
0 Refer to the LI1 output pin (see page 287).
1 Refer to the LI2 output pin (see page 287).
2 Refer to the LI3 output pin (see page 287).
3 Refer to the R1 output pin (see page 287).
4 Refer to the R2 output pin (see page 287).
Public Variables
Timing diagram:
Overview
The diagnostic codes the device can return are read from the FailCode output variable.
The inoperable device can be reset as long as ControlCommand is RUE. Otherwise, it can be
reset on the starter through the screw terminal with the appropriate parameter configuration.
Part VIII
Variable Speed Drives
Overview
This part provides the detailed description, pin layout, pin description, operator screen of the device
control blocks of the Variable Speed Drives 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.
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 17
ATV Profile
ATV Profile
Overview
This chapter describes the DFBs of ATV profile.
Description
General
The ATV profile is used to manage the Altivar variable speed drives on different communication
networks.
Function Description
The main functions of the DFB are described in the following table:
Function Description
Control Forward/reverse direction of rotation.
Speed Allows the speed set-point of the device to be sent.
Device status indication Displays the status of the device.
Remote resetting Allows resetting of the device.
Control or Monitoring Enables you to monitor the device.
You can control the command or set-point from the controller or through the wired
inputs/outputs of the speed drive. Also allows the command and set-point to be
controlled separately.
Owner Manages the control system which is the owner (Operator or Program). Therefore,
it is responsible for setting the control.
Torque Allows the drive to run based on Torque set point.
Function Block Modbus ID Read Address Read Length Write Address Write Length
ATV7161 255 0 9 0 7
ATV6xx 255 0 12 0 5
ATV9xx 255 0 12 0 6
EATV32 255 0 7 0 5
ATV6xxx 255 0 14 0 6
NOTE: ATV blocks are designed for DRIVECOM profile. In the Command and reference
parameter, CHCF (Channel configuration) is set to Combined channel mode as current value.
DFB Representation
Representation
The following figure represents the function module of ATV profile:
NOTE:
The underlined parameters are specific for some components.
ATV blocks do not support corresponding device DTM for M340 controllers.
For DFBs communicating by I/O scanning, variables read from the device retain their last value
when a communication interruption occurs. For details, refer to the description of the
corresponding output parameter (see page 126).
WARNING
UNINTENDED EQUIPMENT OPERATION
When you configure the Last value parameter of the I/O scanner line, take into consideration
the behavior of the DFB when a communication interruption occurs.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Parameters Compo-
nents
Modbus Advantys Ethernet Profibus
STB
All All I/O scanning Mes- All
ATV7 EAT ATV9 ATV6x ATV6x saging
161 V32 xx x xx
Inputs DeviceAddress – – X – – – - X –
IOScannerStatus – – X X X X X – X
ModBusAddress X – – – – – - – –
CommunicationOK – X – – – – - – –
OutputsMap – – X X – – - – –
(ATVOUTPUTS)
OutputsMapExt – – X X – – - – –
(ATVOUTPUTSEXT)
OutputsMap – – – – – X - – –
(ATV6xxOUTPUTS)
OutputsMapExt – – – – – X – – –
(ATV6xxOUTPUTSEXT)
OutputsMap – – – – – – X – –
(ATV6xxxOUTPUTS)
X: Parameter is available.
–: Parameter is not available.
Parameters Compo-
nents
Modbus Advantys Ethernet Profibus
STB
All All I/O scanning Mes- All
ATV7 EAT ATV9 ATV6x ATV6x saging
161 V32 xx x xx
OutputsMapExt – – – – – – X – –
(ATV6xxxOUTPUTSEXT)
OutputsMap – – – – X – – – –
(ATV9xxOUTPUTS)
OutputsMapExt – – – – X – – – –
(ATV9xxOUTPUTSEXT)
TorqueSetpoint – – – – X – X – –
AO1 – – X X – X - – –
AO2 – – X – – X - – –
AQ1 – – – – X – X – –
AQ2 – – – – X – X – –
StatisticSelector X – – – – – - X –
ExternalError – – – – X X X – –
C515 – – – – X X X – –
Inputs – X X X – – - – X
(ANY_ARRAY_INT)
Inputs – – – – – X – – –
(ATV6xx_IN_DDT)
Inputs – – – – – – X – –
(ATV6xxx_IN_DDT)
Inputs Inputs – – – – X – – – –
(ATV9xx_IN_DDT)
DTMInputs – – – X – – – – –
(ATV32_IN_NOCETH)
DTMInputs – – X – – – – – –
(ATV7161_IN_NOCETH)
DTMInputs – – – – – X – – –
(ATV6xxE_IN_NOCETH)
DTMInputs – – – – – – X – –
(ATV6xxxE_IN_
NOCETH)
X: Parameter is available.
–: Parameter is not available.
Parameters Compo-
nents
Modbus Advantys Ethernet Profibus
STB
All All I/O scanning Mes- All
ATV7 EAT ATV9 ATV6x ATV6x saging
161 V32 xx x xx
DTMInputs – – – – X – – – –
(ATV9xxE_IN_NOCETH)
Outputs WarningCode X X X X – – – X X
(ATVWARNING)
WarningCode – – – – – X – – –
(ATV6xxWARNING)
WarningCode – – – – – – X – –
(ATV6xxxWARNING)
WarningCode – – – – X – – – –
(ATV9xxWARNING)
CommunicationOK – – X – X X X – X
Status (ATVSTATUS) X X X X – – – X X
Status – – – – – X – – –
(ATV6xxSTATUS)
Status – – – – – – X – –
(ATV6xxxSTATUS)
Status – – – – X – – – –
(ATV9xxSTATUS)
CommandStatus – – – – – – X – –
InputsMap – – X X – – – – –
(ATVINPUTS)
InputsMapExt – – X X – – – – –
(ATVINPUTSEXT)
InputsMap – – – – – X – – –
(ATV6xxINPUTS)
InputsMap – – – – – – X – –
(ATV6xxxINPUTS)
InputsMapExt – – – – – X – – –
(ATV6xxINPUTSEXT)
InputsMapExt – – – – – – X – –
(ATV6xxxINPUTSEXT)
X: Parameter is available.
–: Parameter is not available.
Parameters Compo-
nents
Modbus Advantys Ethernet Profibus
STB
All All I/O scanning Mes- All
ATV7 EAT ATV9 ATV6x ATV6x saging
161 V32 xx x xx
InputsMap – – – – X – – – –
(ATV9xxINPUTS)
InputsMapExt – – – – X – – – –
(ATV9xxINPUTSEXT)
Current – – X X X X X – –
Torque – – X X X X X – –
Outputs Power – – – – X X X – –
AI1 – – X – X X X – –
AI2 – – X – X X X – –
AI3 – – – – X X X – –
StatisticConnector X – – – – – – – –
Outputs – X X X – – – – X
(ANY_ARRAY_INT)
Outputs – – – – – X – – –
(ATV6xx_OUT_DDT)
Outputs – – – – – – X – –
(ATV6xxx_OUT_DDT)
Outputs – – – – X – – - –
(ATV9xx_OUT_DDT)
DTMOutputs – – – X – – – – –
(ATV32_OUT_NOCETH)
DTMOutputs – – X – – – – – –
(ATV7161_OUT_
NOCETH)
DTMOutputs – – – – – X – – –
(ATV6xxE_OUT_
NOCETH)
DTMOutputs – – – – – – X – –
(ATV6xxxE_OUT_
NOCETH)
X: Parameter is available.
–: Parameter is not available.
Parameters Compo-
nents
Modbus Advantys Ethernet Profibus
STB
All All I/O scanning Mes- All
ATV7 EAT ATV9 ATV6x ATV6x saging
161 V32 xx x xx
DTMOutputs – – – – X – – – –
(ATV9xxE_OUT_
NOCETH)
ATV_IO (ATV_IO_EXT) – – X X – – – – –
ATV_IOEXT – – X X – – – – –
(ATV_IOEXT_DDT)
ATV_IO – – – – – X – – –
(ATV6xx_IO_EXT)
ATV_IO – – – – – – X – –
(ATV6xxx_IO_EXT)
ATV_IOEXT – – – – – X – – –
(ATV6xx_IOEXT_DDT)
ATV_IOEXT – – – – – – X – –
(ATV6xx_IOEXT_DDT)
ATV_IO – – – – X – – – –
(ATV9xx_IO_DDT)
ATV_IOEXT – – – – X – – – –
(ATV9xx_IOEXT_DDT)
Inputs/ ATV_ST (ATV_ST_DDT) X X X X – – – X X
outputs
ATV_ST – – – – – X – – –
(ATV6xx_ST_DDT)
ATV_ST – – – – – – X – –
(ATV6xxx_ST_DDT)
ATV_ST – – – – X – – – –
(ATV9xx_ST_DDT)
ATV_CFG X X X X – – – X X
(ATV_CFG_DDT)
X: Parameter is available.
–: Parameter is not available.
Parameters Compo-
nents
Modbus Advantys Ethernet Profibus
STB
All All I/O scanning Mes- All
ATV7 EAT ATV9 ATV6x ATV6x saging
161 V32 xx x xx
ATV_CFG – – – – – X – – –
(ATV6xx_CFG_DDT)
ATV_CFG – – – – – – X – –
(ATV6xxx_CFG_DDT)
ATV_CFG – – – – X – – – –
(ATV9xx_CFG_DDT)
Workmemory X – – – – – – X –
X: Parameter is available.
–: Parameter is not available.
Inputs
Public variable values are loaded during the first enabling cycle.
EnableDevice BOOL 1 = Enables the devices if the EnableDFB variable is active.
The speed drive has to be enabled in order to be controlled.
If the device is reset and Run pin is active, then the device will auto start. If manual start of the
device is required, then reset the Run pin followed by device.
NOTICE
UNINTENDED EQUIPMENT OPERATION
Reset the Run variable before resuming operation.
Failure to follow these instructions can result in equipment damage.
NOTICE
UNINTENDED EQUIPMENT OPERATION
Configure the Torque setpoint through the drive.
Failure to follow these instructions can result in equipment damage.
TorqueSetPoint 5and 6 REAL The torque set-point is requested from the speed drive.
*: Parameters are available only for specific components.
1
: Parameter is available only for ATV7161.
2: Parameter is available only for EATV32.
3
: Parameter is available only for ASATV31 and ASATV7161.
4
: Parameter is available only for PBATV7161.
5
: Parameter is available only for ATV9xx.
6
: Parameter is available only for ATV6xx, ATV9xx and ATV6xxx.
7
: Parameter is applicable only for Ethernet messaging.
8: Parameter is available only for ATV6xx.
OutputsMapExt* ATVOUTPUTSMAPEXT Holds a data structure that is used to control the speed
driver outputs for ATV61 and ATV71 on Ethernet networks
and for ATV32 extended cards on Ethernet networks.
You can only control the outputs of the speed driver with
this input variable. You cannot control the outputs of the
speed driver from the HMI/SCADA system.
The following table describes the OutputsMapExt:
Output Type Description
R3 BOOL 1 = The state of the R3 relay output.
R4 BOOL 1 = The state of the R4 relay output.
LO1 BOOL 1 = The state of the LO1 digital output.
LO2 BOOL 1 = The state of the LO2 digital output.
LO3 BOOL 1 = The state of the LO3 digital output.
LO4 BOOL 1 = The state of the LO4 digital output.
*
: Parameters are available only for specific components.
1: Parameter is available only for ATV7161.
2
: Parameter is available only for EATV32.
3: Parameter is available only for ASATV31 and ASATV7161.
4
: Parameter is available only for PBATV7161.
5
: Parameter is available only for ATV9xx.
6
: Parameter is available only for ATV6xx, ATV9xx and ATV6xxx.
7
: Parameter is applicable only for Ethernet messaging.
8: Parameter is available only for ATV6xx.
Inputs3 ANY_ARRAY_INT Holds an array structure with the data obtained from the
device. You can control the speed driver with this input
variable. This input variable is reserved for the DFB, and
you cannot use this variable directly. To make the control
block to work properly, allocate the structure (%MWx). Refer
to the Communications Technologies (see page 503).
The information available for speed drivers on an Advantys
STB is shown in the following table:
Parameter Type Description
Inputs [0] INT Status word (ETA).
Inputs [1] INT Control effort (rpm).
Inputs4 ARRAY [0..27] OF BYTE Holds a structure with the data obtained from the inverter.
Outputs
*
: Parameters are available for specific components.
1
: Parameter is available only for ATV7161.
2
: Parameter is available only for EATV32.
3
: Parameter is available only for ASATV31 and ASATV7161.
4: Parameter is available only for PBATV7161.
5
: Parameter is available only for ATV6xx.
6
: Parameter is available only for ATV9xx and ATV6xxx.
7
: Parameter is available only for MBATV212.
NOTE:
Drive is in ready state, default forward
status will be active.
Drive is in run state, status gets updated as
per direction selection.
ReservedReferenceChannel BOOL 1 = The drive reference channel is reserved by
DTM (Control Expert, SoMove) or WEB server
(W8441.15) CRC.
ReservedCommandChannel BOOL 1 = The drive command channel is reserved by
DTM (Control Expert, SoMove) or WEB server
(W8442.15) CCC.
State INT Numerical code corresponding to the state of
the speed driver.
Refer to the State (see page 348) table.
Info INT Numerical code with the information on
statuses and required actions.
Refer to the Info (see page 349) table.
InputsMap* ATV6xxINPUTS/ATV9xxINPUTS/ Holds a data structure with the information on the state
ATV6xxxINPUTS of the inputs of the speed driver.
The following table describes the InputsMap:
Parameter Type Description
DI1 BOOL 1 = State of the digital input DI1.
DI2 BOOL 1 = State of the digital input DI2.
DI3 BOOL 1 = State of the digital input DI3.
DI4 BOOL 1 = State of the digital input DI4.
DI5 BOOL 1 = State of the digital input DI5.
DI6 BOOL 1 = State of the digital input DI6.
*
: Parameters are available for specific components.
1
: Parameter is available only for ATV7161.
2
: Parameter is available only for EATV32.
3: Parameter is available only for ASATV31 and ASATV7161.
4
: Parameter is available only for PBATV7161.
5: Parameter is available only for ATV6xx.
6
: Parameter is available only for ATV9xx and ATV6xxx.
7
: Parameter is available only for MBATV212.
InputsMapExt5,6 ATV6xxINPUTSEXT/ Holds a data structure with the information on the state
ATV9xxINPUTSEXT/ of the inputs of the speed driver.
ATV6xxxINPUTSEXT The following table describes the InputsMapExt:
Current * REAL Present motor current in percentage (%). You can find
this value on speed drives on ATV61 and ATV71 units
on Ethernet networks and on speed drivers on ATV32
unit on Ethernet networks..
Torque* REAL Current motor torque in 0.1 A increment. You can find
this value on ATV61 and ATV71 on Ethernet networks
and on ATV32 unit on Ethernet networks..
ATV_IO * ATV_IO_DDT (see page 350) Device data structure holds the information for
performing monitoring functions. The information used
by the operator screen is readable from HMI or
SCADA system.
ATV_IOEXT* ATV_IOEXT_DDT (see page 350) Device data structure holds the information for
performing monitoring functions. The information used
by the operator screen is readable from HMI or
SCADA system.
ATV_IO5,6 ATV6xx_IO_DDT Device data structure holds the information for
(see page 350)/ATV9xx_IO_DDT performing monitoring functions. The information used
(see page 350)/ATV6xxx_IO_ by the operator screen is readable from HMI or
DDT (see page 350) SCADA system.
Outputs1 ANY_ARRAY_INT Holds an array structure with data sent to the device.
You can control the speed driver with this output
variable. This variable is reserved for the DFB, and
you cannot use this variable directly. To make the
control block work properly, allocate the structure
(%MWx). Refer to the Communications Technologies
(see page 503).
The following table describes the ANY_ARRAY_INT
information available for EATV61 and EATV71 units on
Ethernet networks:
Parameter Type Description
Outputs [0] INT Control word (CMD).
Outputs [1] INT Speed set-point (LFRD).
Outputs [2] INT Logic output states (OL1R).
Outputs [3] INT Analog output 1 physical value (AO1C).
Outputs [4] INT Analog output 2 physical value (AO2C).
Outputs [5] INT Analog output 3 physical value (AO3C).
*:
Parameters are available for specific components.
1
: Parameter is available only for ATV7161.
2:
Parameter is available only for EATV32.
3
: Parameter is available only for ASATV31 and ASATV7161.
4: Parameter is available only for PBATV7161.
5: Parameter is available only for ATV6xx.
6
: Parameter is available only for ATV9xx and ATV6xxx.
7: Parameter is available only for MBATV212.
Outputs 3 ANY_ARRAY_INT Holds an array structure with data sent to the device.
You can control the speed driver with this output
variable. This variable is reserved for the DFB, and
you cannot use this variable directly. To make the
control block work properly, allocate the structure
(%MWx). Refer to the Communication Technologies
(see page 503).
The information available for speed drivers on an
Advantys STB is shown in the following table:
Parameter Type Description
Outputs [0] INT Control word (CWD).
Outputs [1] INT Speed set-point.
Outputs4 ARRAY [0..27] OF BYTE Holds an array structure with data sent to the inverter.
(Reserved for DFB usage).
*
: Parameters are available for specific components.
1
: Parameter is available only for ATV7161.
2: Parameter is available only for EATV32.
3
: Parameter is available only for ASATV31 and ASATV7161.
4
: Parameter is available only for PBATV7161.
5: Parameter is available only for ATV6xx.
6
: Parameter is available only for ATV9xx and ATV6xxx.
7
: Parameter is available only for MBATV212.
State
The following table describes the State variable:
Info
The code with the information is shown on the Control Expert operator screen. This variable is for
informational purposes only. Do not use it to program switching operations. The following table
describes the Info variable:
ATV_IO_DDT Type
ATV_IOEXT_DDT Type
ATV6xx_IO_DDT/ATV9xx_IO_DDT/ATV6xxx_IO_DDT Type
ATV6xx_IOEXT_DDT/ATV9xx_IOEXT_DDT/ATV6xxx_IOEXT_DDT Type
Bit Description
0 R1 output state (OutputsMap.R1 (see page 316))
1 R2 output state (OutputsMap.R2 (see page 316)).
2 R3 output state (OutputsMap.R3 (see page 316)).
3 R4 output state (OutputsMapExt.R4 (see page 316)).
4 R5 output state (OutputsMapExt.R5 (see page 316)).
5 R6 output state (OutputsMapExt.R6 (see page 316)).
8 DQ1 output state (OutputsMapExt.DQ1 (see page 316)).
12 DQ11 output state (OutputsMapExt.DQ11 (see page 316)).
13 DQ12 output state (OutputsMapExt.DQ12 (see page 316)).
Bit Description
0 R1 output state (OutputsMap.R1)
1 R2 output state (OutputsMap.R2).
2 R3 output state (OutputsMap.R3) for ATV 71 and ATV 61.
3 R4 output state (OutputsMap.R4) for ATV 71 and ATV 61.
4 LO1 output state (OutputsMapExt.LO1) for ATV 71 and ATV 61.
5 LO2 output state (OutputsMapExt.LO2) for ATV 71 and ATV 61.
6 LO3 output state (OutputsMapExt.LO3) for ATV 71 and ATV 61.
7 LO4 output state (OutputsMapExt.LO4) for ATV 71 and ATV 61.
Bit Description
0 Value of the digital input DI1 (InputsMap.DI1).
1 Value of the digital input DI2 (InputsMap.DI2).
2 Value of the digital input DI3 (InputsMap.DI3).
3 Value of the digital input DI4 (InputsMap.DI4).
4 Value of the digital input DI5 (InputsMap.DI5).
5 Value of the digital input DI6 (InputsMap.DI6).
6 Value of the digital input DI7 (InputsMap.DI7).
7 Value of the digital input DI8 (InputsMap.DI8).
10 Value of the digital input DI11 (InputsMap.DI11).
11 Value of the digital input DI12 (InputsMap.DI12).
12 Value of the digital input DI13 (InputsMap.DI13).
13 Value of the digital input DI14 (InputsMap.DI14).
14 Value of the digital input DI15 (InputsMap.DI15).
15 Value of the digital input DI16 (InputsMap.DI16).
Timing diagram:
Bit Description
0 Value of the digital input L1 (InputsMap.L1).
1 Value of the digital input L2 (InputsMap.L2).
2 Value of the digital input L3 (InputsMap.L3).
3 Value of the digital input L4 (InputsMap.L4).
4 Value of the digital input L5 (InputsMap.L5).
5 Value of the digital input L6 (InputsMap.L6).
6 Value of the digital input L7 (InputsMap.L7).
7 Value of the digital input L8 (InputsMap.L8).
8 Value of the digital input L9 (InputsMap.L9).
9 Value of the digital input L10 (InputsMap.L10).
10 Value of the digital input L11 (InputsMap.L11).
11 Value of the digital input L12 (InputsMap.L2).
12 Value of the digital input L13 (InputsMap.L13).
13 Value of the digital input L14 (InputsMap.L14).
14 Value of the digital input L15 (InputsMap.L15).
Inputs/Outputs
ATV_ST_DDT Type
ATV_CFG_DDT Type
ATV6xx_ST_DDT/ATV9xx_ST_DDT/ATV6xxx_ST_DDT Type
TorqueSetPoint* REAL Torque set-point variable is requested from the speed driver.
*
: Parameters are available for 9xx and 6xxx.
ATV6xx_CFG_DDT/ATV9xx_CFG_DDT/ATV6xxx_CFG_DDT Type
Bit Description
0 Unknown technological module status. No variable refreshing.
1 Not ready.
2 Technological module is running.
3 Inoperable device.
4 Alarm on the device or DFB (follow-up or screw terminal-based control).
5 Communication interruption.
6 Requires resetting. ResetFail is required.
7 Refer to the ExtControlled output pin (see page 332).
8 Refer to the Resetting output pin (see page 332).
9 Refer to the EnableDFB input pin (see page 316).
15 Direction of rotation.
Bit Description
0 Refer to the ResetFail input pin (see page 316).
1 Owner.
3 Refer to the Direction input pin (see page 316).
4 Refer to the QuickStop input pin (see page 316).
5 Refer to the EnableDevice input pin (see page 316).
6 Refer to the Run input pin (see page 316).
7 Refer to the ControlCommand input pin (see page 316).
8 Refer to the ControlSetPoint input pin (see page 316).
Bit Description
0 Refer to the ResetFail input pin (see page 316).
1 Owner.
3 Refer to the Direction input pin (see page 316).
4 Refer to the QuickStop input pin (see page 316).
5 Refer to the EnableDevice input pin (see page 316).
6 Refer to the Run input pin (see page 316).
7 Refer to the ControlCommand input pin (see page 316).
8 Refer to the ControlSetPoint input pin (see page 316).
9 Refer to the ExternalError input pin (see page 316).
NOTE: The Owner bit enables to control the block from the ***_ST_DDT input/output structure
ignoring the input signals of the block. It enables control from a monitoring system (HMI, SCADA,
Operator screen) in the Manual mode without using the programmed switching operation.
ATV_CFG.DataStatus/ATV6xx_CFG.DataStatus/ATV9xx_CFG.DataStatus/ATV6xxx_CFG.Dat
aStatus Word Structure
Bit Description
0 Refer to the ReadyToSwitchOn status in the Status output pin (see page 332).
1 Refer to the SwitchedOn status in the Status output pin (see page 332).
2 Refer to the OperationEnabled status in the Status output pin (see page 332).
3 Refer to the Malfunction status in the Status output pin (see page 332).
4 Refer to the VoltageEnabled status in the Status output pin (see page 332).
5 Refer to the QuickStop status in the Status output pin (see page 332).
6 Refer to the SwitchOnDisabled status in the Status output pin (see page 332).
7 Refer to the Alarm status in the Status output pin (see page 332).
8 Refer to the ForcedLocalMode status in the Status output pin (see page 332).
9 Refer to the ReferenceReached status in the Status output pin (see page 332).
10 Refer to the ReferenceExceeded status in the Status output pin (see page 332).
11 Refer to the StopImposed status in the Status output pin (see page 332).
12 Refer to the FowardReverseRotation status in the Status output pin (see page 332).
Bit Description
0 Refer to the OutputFailure status in the Status output pin (see page 332).
1 Refer to the Tripped status in the Status output pin (see page 332).
2 Refer to the Alarm status in the Status output pin (see page 332).
3 Refer to the MOFF status in the Status output pin (see page 332).
4 Refer to the MotorSelectionTHR status in the Status output pin (see page 332).
5 Refer to the PIControl status in the Status output pin (see page 332).
6 Refer to the AccelerationPattern status in the Status output pin (see page 332).
7 Refer to the DCBraking status in the Status output pin (see page 332).
9 Refer to the ForwardReverseRotation status in the Status output pin (see page 332).
10 Refer to the Run status in the Status output pin (see page 332).
11 Refer to the CoastStop status in the Status output pin (see page 332).
12 Refer to the EmergencyStop status in the Status output pin (see page 332).
13 Refer to the StandbyST status in the Status output pin (see page 332).
Bit Description
14 Refer to the Standby status in the Status output pin (see page 332).
15 Refer to the LocalRemote status in the Status output pin (see page 332).
Bit Description
0 Refer to the ReservedReferenceChannel status in the Status output pin (see page 332).
1 Refer to the ReservedCommandChannel status in the Status output pin (see page 332).
Bit Description
0 Refer to the ReservedReferenceChannel status in the Status output pin (see page 332).
1 Refer to the ReservedCommandChannel status in the Status output pin (see page 332).
2 Refer to the MVCBReadyToClose status in the Status output pin (see page 332).
3 No command selected. Refer to CommandStatus output pin (see page 332).
4 Remote command selected. Refer to CommandStatus output pin (see page 332)
5 Local command selected. Refer to CommandStatus output pin (see page 332)
6 Panel command selected. Refer to CommandStatus output pin (see page 332)
Bit Description
1 Refer to the Device in the WarningCode output pin (see page 332).
2 Refer to the Order in the WarningCode output pin (see page 332).
3 Refer to the ForcedLocalMode in the WarningCode output pin (see page 332).
ATV6xx_CFG.WarningCode/ATV9xx_CFG.WarningCode/ATV6xxx_CFG.WarningCode Word
Structure
Bit Description
1 Refer to the Device in the WarningCode output pin (see page 332).
2 Refer to the Order in the WarningCode output pin (see page 332).
3 Refer to the ForcedLocalMode in the WarningCode output pin (see page 332).
4 Refer to ReservedReferenceChannel in the WarningCode output pin (see page 332).
5 Refer to ReferenceCommandChannel in the WarningCode output pin (see page 332).
Public Variables
For operating the motor at different rpm, LowRangeEngUnit has to be less than the
HighRangeEngUnit. If both the values are same, motor operates at HighRangeEngUnit.
NOTICE
UNEXPECTED EQUIPMENT BEHAVIOR
Do not configure LowRangeEngUnit to be same as HighRangeEngUnit.
Failure to follow these instructions can result in equipment damage.
LowRangeEngUnit REAL Low range for the measurement in engineering units (Refer to
the SetPoint input pin (see page 316)).
NOTE: The parameter value has to be higher than
LowRangeRpm.
ResetMode BOOL Enables to configure the type of reset. This type of reset is used
for communication interruption and device interruptions.
The time defined in CommandCtrlWindow is used to define the
interval after which a reset has to be carried out. The first reset
is carried out after the time defined in CommandCtrlWindow
elapses. The second reset is carried out after
CommandCtrlWindow * 2 elapses, so on. If the value of
CommandCtrlWindow is 0 s, its value is not used and is instead
replaced with a value of 1 s.
The following table describes the type of the reset:
Variable Description
value
FALSE Communications with the device is reset with the ResetFail
variable.
TRUE Communications with the device is reset automatically.
MaxResetTime TIME When in automatic ResetMode, this variable is used to define
the maximum time that can elapse between 2 consecutive
resets.
Refer to the Timing diagram below.
ScalingFactorCurrent REAL Define scaling factor for current depending on drive rate.
Timing diagram:
Overview
The diagnostic codes that the device can return are read on the FailCode output variable.
During the above detected FailCode the function block does not process any inputs and the
function blocks output displays the last processed state.
This detected FailCode can be reset by a rising edge to the EnableDFB input pin after correcting
the configuration of the function block.
After the communications have been established, check Ethernet client diagnostic codes for
FailCode [0] and FailCode [1]. The components make a distinction between detected read
request and write request interruptions:
FailCode[2]: 16#0001 Read
FailCode[2]: 16#0002 Write
The inoperable device can be reset if ControlCommand is TRUE. If this condition is not met, the
detected failure can be reset on the speed driver or through the screw terminal with the correct
parameter configuration.
NOTE: The diagnostic codes of the device are available for speed drives, except for those that
communicate through the Advantys STB Island.
Chapter 18
EMATVWarn - Extended Warnings of Process Drives (Supports 9 Alarm registers)
Overview
This chapter describes the features of Extended Warnings of Process Drives (ATV6xx and
ATV9xx) which shall be accessible through the EMATVWarn DFB.
Description
General
The EMATVWarn block is part of the device control block family. Its objective is to manage
Extended Warnings of Process Drives (ATV9xx and ATV6xx) using Explicit Communication.
NOTE: Warnings association to the warning groups has to be configured in device DTM. Refer
ATV6xx/ATV9xx Device DTM User Manual to configure the warnings.
Function Description
The DFB main functions are summarized below:
Function Description
Monitoring Makes it possible to monitor the device warnings in Control Expert.
Device Status Displays the status of the device.
Indication
Remote Allows resetting of the function block.
resetting
Monitoring Enables you to monitor the device.
DFB Representation
Representation
The following figure represents the function module of EMATVWarn DFB.
Inputs
Outputs
Inputs/Outputs
EMATVWarn_ST_DDT Type
EMATVWarn_CFW_DDT Type
WarningStatus[0] Description
Bit 0 Fallback frequency reaction.
Bit 1 Speed maintained.
Bit 2 Type of stop.
Bit 3 Reference frequency warning.
Bit 4 Life cycle warning 1.
Bit 5 Life cycle warning 2.
Bit 6 Drive running warning.
Bit 7 Low flow warning.
Bit 8 High flow warning.
Bit 9 Inlet pressure warning.
Bit 10 Outlet pressure low warning.
Bit 11 Outlet pressure high warning.
Bit 12 Pump cycle warning.
Bit 13 Anti jam warning.
WarningStatus[0] Description
Bit 14 Pump low flow.
Bit 15 Low pressure warning.
Bit 16 Flow limit activated.
Bit 17 PID error warning.
Bit 18 PID feedback warning.
Bit 19 PID high feedback warning.
Bit 20 PID low feedback warning.
Bit 21 Regulation warning.
Bit 22 Limit switch reached.
Bit 23 Rope slack detection.
Bit 24 Dynamic load warning.
Bit 25 AI2 thermal sensor warning.
Bit 26 AI3 thermal sensor warning.
Bit 27 AI4 thermal sensor warning.
Bit 28 AI5 thermal sensor warning.
Bit 29 AI1 4-20 loss warning.
Bit 30 AI2 4-20 loss warning.
Bit 31 AI3 4-20 loss warning.
WarningStatus[1] Description
Bit 0 AI4 4-20 loss warning.
Bit 1 AI5 4-20 loss warning..
Bit 2 Drive thermal state warning.
Bit 3 IGBT thermal warning.
Bit 4 Fan counter warning.
Bit 5 Fan feedback warning.
Bit 6 Braking resistor overload alarm is raised.
Bit 7 External error warning.
Bit 8 Undervoltage warning.
Bit 9 Preventive undervoltage active.
Bit 10 Drive in forced run.
Bit 11 Motor frequency high threshold reached.
Bit 12 Motor frequency low threshold reached.
WarningStatus[1] Description
Bit 13 Motor frequency high threshold 2 reached.
Bit 14 Motor frequency low threshold 2 reached.
Bit 15 High speed reached.
Bit 16 Reference frequency high threshold reached.
Bit 17 Reference frequency low threshold reached.
Bit 18 Second frequency threshold reached.
Bit 19 Current threshold reached.
Bit 20 Low current threshold reached.
Bit 21 High torque threshold reached.
Bit 22 Low torque threshold reached.
Bit 23 Process under load warning.
Bit 24 Process overload warning.
Bit 25 Torque current limitation warning.
Bit 26 Torque regulation warning.
Bit 27 Drive thermal threshold reached.
Bit 28 Motor thermal threshold reached.
Bit 29 Moto2 thermal threshold reached.
Bit 30 Motor3 thermal threshold reached.
Bit 31 Motor4 thermal threshold reached.
WarningStatus[2] Description
Bit 0 Power high threshold reached.
Bit 1 Power low threshold reached.
Bit 2 Customer warning 1.
Bit 3 Customer warning 2.
Bit 4 Customer warning 3.
Bit 5 Customer warning 4.
Bit 6 Customer warning 5.
Bit 7 Intelligent rectifier warning.
Bit 8 Power consumption warning.
Bit 9 Outlet pressure high switch warning.
Bit 10 Ethernet internal warning.
Bit 11 Device replacement activated but not plugged.
WarningStatus[2] Description
Bit 12 Device replacement transfer failure.
Bit 13 Multi-pumps capacity alarm.
Bit 14 Water: multi pump lead alarm.
Bit 15 Not available.
Bit 16 Level control low alarm
Bit 17 Level control low alarm
Bit 18 Slipping warning.
Bit 19 Not available.
Bit 20 Load movement warning.
Bit 21 Brake contact warning.
Bit 22 AI1 thermal sensor warning.
Bit 23 Back spin controls control is active.
Bit 24 Not available.
Bit 25 Not available.
Bit 26 Not available.
Bit 27 Not available.
Bit 28 Not available.
Bit 29 Not available.
Bit 30 Not available.
Bit 31 Not available.
WarningStatus[3] Description
Bit 0 Not available.
Bit 1 Not available.
Bit 2 Not available.
Bit 3 Not available.
Bit 4 Not available.
Bit 5 Not available.
Bit 6 Not available.
Bit 7 Not available.
Bit 8 Not available.
Bit 9 Not available.
Bit 10 Not available.
WarningStatus[3] Description
Bit 11 Not available.
Bit 12 Not available.
Bit 13 Not available.
Bit 14 Not available.
Bit 15 Not available.
Bit 16 Not available.
Bit 17 Not available.
Bit 18 Not available.
Bit 19 Not available.
Bit 20 Not available.
Bit 21 Not available.
Bit 22 Not available.
Bit 23 Not available.
Bit 24 Not available.
Bit 25 Not available.
Bit 26 Not available.
Bit 27 M/S device alert.
Bit 28 Backlash sequence: Alarm.
Bit 29 Encoder module thermal warning.
Bit 30 BU: Fan running time.
Bit 31 BU: Fan frequency.
WarningStatus[4] Description
Bit 0 BY: Sensor thermal state.
Bit 1 Multidrive: communication link between safe and drive loss (PWM disable).
Bit 2 Not available.
Bit 3 Not available.
Bit 4 Not available.
Bit 5 Not available.
Bit 6 Not available.
Bit 7 Not available.
Bit 8 Not available.
Bit 9 Not available.
Bit 10 Not available.
Bit 11 Not available.
Bit 12 Not available.
Bit 13 Not available.
Bit 14 Not available.
Bit 15 Not available.
Bit 16 Not available.
Bit 17 Not available.
Bit 18 Not available.
Bit 19 Not available.
Bit 20 Not available.
Bit 21 Not available.
Bit 22 Not available.
Bit 23 Not available.
Bit 24 Not available.
Bit 25 Not available.
Bit 26 Not available.
Bit 27 Not available.
Bit 28 Not available.
Bit 29 Not available.
Bit 30 Not available.
Bit 31 Not available.
Public Variables
Chapter 19
EMATVWarn1 - Extended Warnings of Process Drives (Supports 12 Alarm registers)
Overview
This chapter describes the features of Extended Warnings of Process Drives (ATV6xxx) which
shall be accessible through the EMATVWarn1 DFB.
Description
General
The EMATVWarn1 block is part of the device control block family. Its objective is to manage
Extended Warnings of Process Drives (ATV6xxx) using Explicit Communication.
NOTE: Warnings association to the warning groups has to be configured in device DTM. Refer
ATV6xxx Device DTM User Manual to configure the warnings.
Function Description
The DFB main functions are summarized below:
Function Description
Monitoring Makes it possible to monitor the device warnings in Control Expert.
Device Status Displays the status of the device.
Indication
Remote Allows resetting of the function block.
resetting
Monitoring Enables you to monitor the device.
DFB Representation
Representation
The following figure represents the function module of EMATVWarn1 DFB.
Inputs
Outputs
Inputs/Outputs
EMATVWarn1_ST_DDT Type
EMATVWarn1_CFW_DDT Type
WarningStatus[0] Description
Bit 0 Fallback frequency reaction.
Bit 1 Speed maintained.
Bit 2 Type of stop.
Bit 3 Reference frequency warning.
Bit 4 Life cycle warning 1.
Bit 5 Life cycle warning 2.
Bit 6 Drive running warning.
Bit 7 Mot applicable.
Bit 8
Bit 9
Bit 10
Bit 11
Bit 12 Pump cycle warning.
WarningStatus[0] Description
Bit 13 Not applicable.
Bit 14
Bit 15
Bit 16
Bit 17 PID error warning.
Bit 18 PID feedback warning.
Bit 19 PID high feedback warning.
Bit 20 PID low feedback warning.
Bit 21 Regulation warning.
Bit 22 Not applicable.
Bit 23
Bit 24
Bit 25
Bit 26 AI3 thermal sensor warning.
Bit 27 AI4 thermal sensor warning.
Bit 28 AI5 thermal sensor warning.
Bit 29 AI1 4-20 loss warning.
Bit 30 Not applicable.
Bit 31 AI3 4-20 loss warning.
WarningStatus[1] Description
Bit 0 AI4 4-20 loss warning.
Bit 1 AI5 4-20 loss warning..
Bit 2 Drive thermal state warning.
Bit 3 Not applicable.
Bit 4 Fan counter warning.
Bit 5 Fan feedback warning.
Bit 6 Not applicable.
Bit 7 External error warning.
Bit 8 Undervoltage warning.
Bit 9 Preventive undervoltage active.
Bit 10 Drive in forced run.
Bit 11 Motor frequency high threshold reached.
WarningStatus[1] Description
Bit 12 Motor frequency low threshold reached.
Bit 13 Motor frequency high threshold 2 reached.
Bit 14 Motor frequency low threshold 2 reached.
Bit 15 High speed reached.
Bit 16 Reference frequency high threshold reached.
Bit 17 Reference frequency low threshold reached.
Bit 18 Second frequency threshold reached.
Bit 19 Current threshold reached.
Bit 20 Low current threshold reached.
Bit 21 High torque threshold reached.
Bit 22 Low torque threshold reached.
Bit 23 Process under load warning.
Bit 24 Process overload warning.
Bit 25 Torque current limitation warning.
Bit 26 Torque regulation warning.
Bit 27 Drive thermal threshold reached.
Bit 28 Motor thermal threshold reached.
Bit 29 Moto2 thermal threshold reached.
Bit 30 Motor3 thermal threshold reached.
Bit 31 Motor4 thermal threshold reached.
WarningStatus[2] Description
Bit 0 Power high threshold reached.
Bit 1 Power low threshold reached.
Bit 2 Customer warning 1.
Bit 3 Customer warning 2.
Bit 4 Customer warning 3.
Bit 5 Customer warning 4.
Bit 6 Customer warning 5.
Bit 7 Not applicable.
Bit 8 Power consumption warning.
Bit 9 Not applicable.
Bit 10
Bit 11
Bit 12
Bit 13
Bit 14
Bit 15
Bit 16
Bit 17
Bit 18 Slipping warning.
Bit 19 Not available.
Bit 20 Load movement warning.
Bit 21 Brake contact warning.
Bit 22 AI1 thermal sensor warning.
Bit 23 Not applicable.
Bit 24
Bit 25
Bit 26
Bit 27
Bit 28
Bit 29
Bit 30
Bit 31
WarningStatus[3] Description
Bit 0 IO function: Digital warning A.
Bit 1 IO function: Digital warning B.
Bit 2 IO function: Digital warning C.
Bit 3 IO function: Digital warning D.
Bit 4 IO function: Cabinet warning A.
Bit 5 IO function: Cabinet warning B.
Bit 6 IO function: Cabinet warning C.
Bit 7 IO function: Thermal input warning A.
Bit 8 IO function: Thermal input warning B.
Bit 9 IO function: Thermal input warning C.
Bit 10 IO function: Thermal input warning D.
Bit 11 Not available.
Bit 12
Bit 13
Bit 14
Bit 15
Bit 16
Bit 17
Bit 18
Bit 19
Bit 20
Bit 21
Bit 22 Cabinet overheating alarm.
Bit 23 Not available.
Bit 24
Bit 25
Bit 26
Bit 27 M/S device alert.
Bit 28 Backlash warning.
Bit 29 Encoder module thermal warning.
Bit 30 Not available.
Bit 31
WarningStatus[4] Description
Bit 0 Not available.
Bit 1
Bit 2
Bit 3 Power cells over-braking light overvoltage warning.
Bit 4 Mains input ground voltage warning.
Bit 5 Motor output ground voltage warning.
Bit 6 PLC cabinet warning 1.
Bit 7 PLC cabinet warning 2.
Bit 8 PLC cabinet warning 3.
Bit 9 PLC cabinet warning 4.
Bit 10 PLC cabinet warning 5.
Bit 11 PLC cabinet warning 6.
Bit 12 PLC cabinet warning 7.
Bit 13 PLC cabinet warning 8.
Bit 14 PLC cabinet warning 9.
Bit 15 PLC cabinet warning 10.
Bit 16 PLC cabinet warning 11.
Bit 17 PLC cabinet warning 12.
Bit 18 PLC cabinet warning 13.
Bit 19 PLC cabinet warning 14.
Bit 20 PLC cabinet warning 15.
Bit 21 PLC cabinet warning 16.
Bit 22 PLC cabinet warning 17.
Bit 23 PLC cabinet warning 18.
Bit 24 PLC cabinet warning 19.
Bit 25 PLC cabinet warning 20.
Bit 26 PLC cabinet warning 21.
Bit 27 PLC cabinet warning 22.
Bit 28 PLC cabinet warning 23.
Bit 29 PLC cabinet warning 24.
Bit 30 PLC cabinet warning 25.
Bit 31 PLC cabinet warning 26.
WarningStatus[5] Description
Bit 0 PLC cabinet warning 27.
Bit 1 PLC cabinet warning 28.
Bit 2 PLC cabinet warning 29.
Bit 3 PLC cabinet warning 30.
Bit 4 PLC cabinet warning 31.
Bit 5 PLC cabinet warning 32.
Bit 6 PLC application ETO warning 1.
Bit 7 PLC application ETO warning 2.
Bit 8 PLC application ETO warning 3.
Bit 9 PLC application ETO warning 4
Bit 10 PLC application ETO warning 5.
Bit 11 PLC application ETO warning 6.
Bit 12 PLC application ETO warning 7.
Bit 13 PLC application ETO warning 8.
Bit 14 PLC application ETO warning 9.
Bit 15 PLC application ETO warning 10.
Bit 16 PLC application ETO warning 11.
Bit 17 PLC application ETO warning 12.
Bit 18 PLC application ETO warning 13.
Bit 19 PLC application ETO warning 14.
Bit 20 PLC application ETO warning 15.
Bit 21 PLC application ETO warning 16.
Bit 22 Motor parameter scaling warning.
Bit 23 Not available.
Bit 24
Bit 25
Bit 26
Bit 27
Bit 28
Bit 29
Bit 30
Bit 31
Part IX
Weighing Module
Weighing Module
Chapter 20
Weighing Module Profile
Overview
This chapter describes the DFB of Weighing module profile.
Description
General
EIPMPMESWT is a high performance weighing module controller which is used for vessels and silos
weighing, dosing process and dynamic weighing application on Ethernet IP using Explicit
unconnected messaging.
Function Description
Function Description
Control and Monitoring When owner is program, functional commands (Tare, Cancel Tare and Zero
Adjustment) are executed through user sequence DFB.
Also it enables you to monitor the device.
You can control the functional commands from the user sequence DFB.
Device status Displays the status of the device.
indication
Remote resetting Allows resetting of the device.
Owner Manages the control system which is the owner (Operator or Program).
Failure management Fail output pin will be high based on the following conditions. It requires
ResetFail/Reseting when failure occurred.
Inoperable Device
Communication interruption
Configuration interruption
DFB Representation
Representation
The following figure represents the functional module of EIPMPMESWT.
Inputs
NOTE:
DTM calibration window allows you to configure µdef and
N.m unit. This measurement unit is mainly used in strain
gauge and torque based applications respectively. Since
this control function will be used for weighing application.
µdef and N.m unit are not taken into consideration.
If user enters other than predefined engineering unit, then
control function will consider the last configured
engineering unit.
Timing Diagram
Outputs
Inputs/Outputs
PMESWT_ST_DDT
PMESWT_CFG_DDT
PMESWT_CFG.MeasurementStatus Structure
Bit Description
0 Measurement is OK.
1 Gross weight is less than negative Maximum capacity.
2 Gross weight is greater than maximum capacity.
3 Converter saturation or Analog signal out of A/D input range.
4 0 = Measurement is unstable.
1 = Measurement is stable.
5 Measurement out of ¼ division flag.
6 0 = Memory Ok.
1 = Detected memory failure.
7 0 = none.
1 = At least one preset tare is processed.
8 0 = Logical Input I0 state is disabled.
1 = Logical Input I0 state is enabled.
9 0 = Logical Input I1 state is disabled.
1 = Logical Input I1 state is enabled
10 0 = Logical Output S0 state is disabled.
1 = Logical Output S0 state is enabled.
11 0 = Logical Output S1 state is disabled.
1 = Logical Output S1 state is enabled.
12 0 = Logical Output S2 state is disabled.
1 = Logical Output S2 state is enabled.
13 0 = Logical Output S3 state is disabled.
1 = Logical Output S3 state is enabled
14 Tare process flag.
15 Zero/Tare process flag.
PMESWT_CFG.DeviceStatus Structure
Bit Description
0 User dosing cycle in progress.
1 At least one user calibration is processed.
2 Physical calibration is set.
3 Theoretical calibration is set.
4 Load cell wiring mode:
0 = 4 wire
1 = 6 wire
PMESWT_CFG.ResponseStatus Structure
Bit Description
0 Ready to accept a new command.
1 Command execution in progress.
2 Command execution complete.
3 Detected error during command execution.
PMESWT_ST.STW Structure
Bit Description
0 Unknown state.
1 Not ready.
2 -
3 Inoperable device.
4 Detected warning.
5 Communication interruption.
6 Requires Reseting.
7 -
8 Reseting.
9 Enable DFB.
10 SignalFailure.
11 Stability.
12 Cancel calibration disable.
13 REARM enable.
14 ExtCalibration - If OOS not enabled & calibration parameters are modified. Then this bit is
triggered to enable Accept Device Values.
PMESWT_ST.CFGW Structure
Bit Description
0 Reset Fail.
1 Owner.
0 - Program
1 - Operator
2 Tare command.
3 Cancel tare command.
4 Zero adjustment command.
5 Physical calibration command.
6 Validation step calibration.
7 Cancel calibration command.
10 Accept new values.
15 OOS mode. Enables to determine whether the device is out of service (1) or in use (0).
Bit Description
0 Refer to Device in the WarningCode (see page 459) output pin .
1 Refer to Order in the WarningCode (see page 459) output pin.
Public Variables
PMESWT_SC_DDT
Overview
The diagnostic codes the device can return are read from the FailCode output variable.
The above mentioned parameter configuration diagnostic codes occurs due to the given below
conditions:
If user enters other than predefined engineering units through other source (DTM).
If there is a difference in calibrated calibration parameters from device register parameters and
when Out Of Service mode is not enabled.
When Out Of Service mode is enabled to start the calibration operation.
After the communications have been established, check EthernetIP client diagnostic codes for
FailCode [0] and FailCode [1]. The components make a distinction between detected read
request and write request interruptions:
FailCode[2]: 16#0001 Read
FailCode[2]: 16#0002 Write
The above mentioned device diagnostic codes occurs due to the given below conditions:
Detected Memory failure.
Gross weight is less than negative maximum capacity.
Gross weight is greater than maximum capacity.
Converter saturation or analog signal out of A/D input range.
Step Action
1 Create new Control Expert project by selecting M580 CPU.
2 Add PME SWT module by right clicking on empty slot of M580 Ethernet backplane and select PME SWT
module from new device window.
NOTE: Verify that you have not selected slot number 2, 8, 10 and 11 to add PME SWT device as Ethernet
Port is absent in those slots.
Step Action
3 Navigate to PLC bus (Project Browser →Configuration →PLC bus). Click on the Ethernet Port available
on the CPU which opens the port configuration. On the Security tab, click the Unlock Security button to
enable FTP, TFTP and HTTP communication.
4 Open DTM browser screen from Menu Tools → DTM Browser. Right click the master DTM in the DTM
browser and select PME SWT 0100 device DTM and click Add DTM.
Step Action
5 Provide the Alias name for the DTM of your choice and click OK on Properties of device window.
Step Action
6 In the DTM browser, right click on the CPU master DTM and click Open. The Master DTM properties window
opens.
Step Action
7 In the Master DTM properties window, navigate to Device List → PMESWT, select Address Setting tab to
configure the device IP address and address server configuration and then click Apply.
8 Build and transfer the Control Expert configuration file to the PLC.
9 In the DTM browser, right click on the M580 CPU DTM and then select Connect.
Step Action
10 In the DTM browser, right click on the PMESWT device DTM and then navigate to Device menu →
Additional functions → Transfer to FDR Server.
11 After successful transfer of FDR, device will become healthy and the following message window displays.
12 To verify that the device is connected or not, In the DTM browser, right click on the PMESWT device DTM
and select Connect. Now, the IP address and name of PMESWT module appears in bold lettering, indicating
both devices are connected.
Step Action
1 In the DTM browser, right click on the PMESWT device DTM and then navigate to Device menu →
Additional functions → Calibration.
Step Action
2 In the DTM calibration window, click Save calibration from device to FDR server.
Step Action
1 During rising edge of EnableDFB or first download, control function is set to Owner (Program) and
Mode (In-Service).
2 Once the device is ready for operation, control function reads the measurement values and
calibration parameters from the device and process the EU conversion accordingly.
3 If you want to perform calibration, then you need to set Owner (Operator) and Mode (Out Of
Service). For execution of calibration commands refer Weighing Module Calibration Commands
Flow Chart (see page 479).
4 For execution of functional commands refer Weighing Module Functional Commands Flow Chart
(see page 480).
5 During operation, if you perform calibration from external source (DTM), then control function will
generate detected configuration failure because the last calibrated value and new value read from
device register are different (calibration parameter mismatch). In such scenario, if you have
performed calibration through external source (DTM), then Accept Device Values button in the
calibration faceplate gives flexibility to accept the calibrated values. Accept Device Values button
is enabled only when there is calibrated parameter mismatch (detected configuration failure).
You can clear this detected failure by clicking Accept Device Values button or start calibration
procedure from the faceplate, by taking the object in Out Of Service mode.
NOTE:
Initially you have to configure the weighing module through DTM.
It is suggested to perform the calibration from the faceplate only.
Before the start of calibration you need to verify that calibration parameters are entered
properly.
In Load acquisition state (after zero acquisition done) during calibration you need to verify that
a physical load is placed on the load cell.
At the end of each calibration, once the device reset is performed and before giving ResetFail
you need to verify that the physical device is healthy.
In Step Calibration = 6, the last calibrated values are returned back to the device register.
Part X
Safety Module
Safety Module
Chapter 21
XPSMC - XPSMC Reader (16 Inputs/ 32 Inputs)
Overview
This chapter describes the XPSMC DFB.
DFB Representation
Representation
The following figure represents XPSMC DFB in Control Expert:
Inputs
Outputs
InputMapExt
The following table describes the InputMapExt variable:
Bit Description
0 Status of the extended input I17 on a controller base.
1 Status of the extended input I18 on a controller base.
2 Status of the extended input I19 on a controller base.
3 Status of the extended input I20 on a controller base.
4 Status of the extended input I21 on a controller base.
5 Status of the extended input I22 on a controller base.
6 Status of the extended input I23 on a controller base.
7 Status of the extended input I24 on a controller base.
8 Status of the extended input I25 on a controller base.
9 Status of the extended input I26 on a controller base.
10 Status of the extended input I27 on a controller base.
11 Status of the extended input I28 on a controller base.
12 Status of the extended input I29 on a controller base.
13 Status of the extended input I30 on a controller base.
14 Status of the extended input I31 on a controller base.
15 Status of the extended input I32 on a controller base.
InputErrorMapExt
The following table describes the InputErrorMapExt variable:
Bit Description
0 Status of the detected error in the extended input I17 on a controller base.
1 Status of the detected error in the extended input I18 on a controller base.
2 Status of the detected error in the extended input I19 on a controller base.
3 Status of the detected error in the extended input I20 on a controller base.
4 Status of the detected error in the extended input I21 on a controller base.
5 Status of the detected error in the extended input I22 on a controller base.
6 Status of the detected error in the extended input I23 on a controller base.
7 Status of the detected error in the extended input I24 on a controller base.
8 Status of the detected error in the extended input I25 on a controller base.
9 Status of the detected error in the extended input I26 on a controller base.
10 Status of the detected error in the extended input I27 on a controller base.
11 Status of the detected error in the extended input I28 on a controller base.
12 Status of the detected error in the extended input I29 on a controller base.
13 Status of the detected error in the extended input I30 on a controller base.
14 Status of the detected error in the extended input I31 on a controller base.
15 Status of the detected error in the extended input I32 on a controller base.
Inputs/Outputs
XPSMC_ST_DDT Type
XPSMC_CFG_DDT Type
Bit Description
0 Unknown device status or communication interruption. No variable refreshing.
1 Not ready.
4 Alarm on the device or repetitive detected fault alarm requires resetting.
5 Communication interruption.
6 Requires resetting. ResetFail is required.
9 Refer to the EnableDFB input pin (see page 485).
Bit Description
0 Refer to the ResetFail input pin (see page 485).
1 Owner.
NOTE: The Owner bit enables to control the block from the XPSMC_ST_DDT input/output structure
ignoring the input signals of the block. It enables control from a monitoring system (HMI, SCADA,
operator screen) in the Manual mode without using the programmed switching operation.
Bit Description
0 Refer to the Run in the Status output pin (see page 486).
1 Refer to the LoadingConfiguration in the Status output pin (see page 486).
2 Refer to the InternalError in the Status output pin (see page 486).
3 Refer to the ExternalError in the Status output pin (see page 486).
4 Refer to the Stop in the Status output pin (see page 486).
5 Refer to the FromRunToStop in the Status output pin (see page 486).
Bit Description
6 Refer to the RebootSwitch in the Status output pin (see page 486).
7 Refer to the DeviceActive in the Status output pin (see page 486).
8 Refer to the XPSMC in the Status output pin (see page 486).
9 Refer to the Checking in the Status output pin (see page 486).
10 Refer to the ConfigurationOK in the Status output pin (see page 486).
11 Refer to the OrderStop in the Status output pin (see page 486).
Bit Description
0 Status of the standard input I1 on a controller base.
1 Status of the standard input I2 on a controller base.
2 Status of the standard input I3 on a controller base.
3 Status of the standard input I4 on a controller base.
4 Status of the standard input I5 on a controller base.
5 Status of the standard input I6 on a controller base.
6 Status of the standard input I7 on a controller base.
7 Status of the standard input I8 on a controller base.
8 Status of the standard input I9 on a controller base.
9 Status of the standard input I10 on a controller base.
10 Status of the standard input I11 on a controller base.
11 Status of the standard input I12 on a controller base.
12 Status of the standard input I13 on a controller base.
13 Status of the standard input I14 on a controller base.
14 Status of the standard input I15 on a controller base.
15 Status of the standard input I16 on a controller base.
Bit Description
0 Status of the output O1 on a controller base.
1 Status of the output O2 on a controller base.
2 Status of the output O3 on a controller base.
3 Status of the output O4 on a controller base.
4 Status of the output O5 on a controller base.
5 Status of the output O6 on a controller base.
6 Status of the output R1 on a controller base.
7 Status of the output R2 on a controller base.
Bit Description
0 Status of the detected errors in the standard input I1 on a controller base.
1 Status of the detected errors in the standard input I2 on a controller base.
2 Status of the detected errors in the standard input I3 on a controller base.
3 Status of the detected errors in the standard input I4 on a controller base.
4 Status of the detected errors in the standard input I5 on a controller base.
5 Status of the detected errors in the standard input I6 on a controller base.
6 Status of the detected errors in the standard input I7 on a controller base.
7 Status of the detected errors in the standard input I8 on a controller base.
8 Status of the detected errors in the standard input I9 on a controller base.
9 Status of the detected errors in the standard input I10 on a controller base.
10 Status of the detected errors in the standard input I11 on a controller base.
11 Status of the detected errors in the standard input I12 on a controller base.
12 Status of the detected errors in the standard input I13 on a controller base.
13 Status of the detected errors in the standard input I14 on a controller base.
14 Status of the detected errors in the standard input I15 on a controller base.
15 Status of the detected errors in the standard input I16 on a controller base.
Bit Description
0 Status of the detected errors in the output C1 on a controller base.
1 Status of the detected errors in the output C2 on a controller base.
2 Status of the detected errors in the output C3 on a controller base.
3 Status of the detected errors in the output C4 on a controller base.
4 Status of the detected errors in the output C5 on a controller base.
5 Status of the detected errors in the output C6 on a controller base.
6 Status of the detected errors in the output C7 on a controller base.
7 Status of the detected errors in the output C8 on a controller base.
Public Variables
Timing diagram:
Part XI
Communication Technologies
Communication Technologies
Overview
This part describes the communication technologies used in the Devices library.
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 22
Ethernet Technology
Ethernet Technology
Overview
This chapter describes configuration details of Ethernet technology on various devices.
Section 22.1
CommunicationOK Variable
CommunicationOK Variable
Description
Declaring a variable as an IODDT enables to obtain an indicator of the communication status for
each IOScanning row.
NOTE: Templates generated with an Ethernet communications network by the SGStudio program
have the Ethernet variable correctly declared and allocated. If a user template is used, declare this
variable.
In the case of the Quantum Copro platform, the IODDT variable is not used. System words are
used instead (%SW160 to %SW167). For example, IOScanning line 1 corresponds to %SW160.0.
In the case of the Quantum NOE platform, the IODDT variable is not used. System words are used
instead (%IW1 to %IW8). For example, IOScanning line 1 corresponds to %IW1.0.
For example, if you use the SG Workbench template, the CommunicationOK input is shown as
Ethernet.REFRESH_IO_X, which has to be replaced with Ethernet.REFRESH_IO_1.0 for line 1.
The IODDT variable has to be addressed with %cha.b.c, where:
a = Rack number
b = Number of slots inside the PLC
c = Number of channels in the Ethernet module
In the following example, the address for the IODDT variable is %CH0.2.0.
As for the device defined on the first IOScanning line: Ethernet.REFRESH_IO_1.
Section 22.2
ATV71/61 Control Block on Ethernet with IO Scanning
Overview
This section provides the configuration and setup details involving the Altivar 71 and Altivar 61
variable speed drives connected through Modbus TCP (Ethernet) in the Modicon M340, M580, and
Quantum automation platforms.
Introduction
The Device library currently incorporates many elements with Ethernet technology. One example
is the ATV 71 and ATV 61 speed drivers and the Tesys T motor protection devices. You can use
any device in serial Modbus mode by using a serial Modbus–Modbus TCP gateway and the
EGtwMB block from the Communication library.
You can operate both ATV 61 and ATV 71 devices and Tesys T devices with messaging or IO
scanning. This documentation refers explicitly to device configurations designed to work with
IOScanning because working with messaging requires the exact same steps until the step of
assigning an IP address to the device. After assigning an IP address to the device is completed,
the address has to be fed to the DeviceAddress input on each one of the devices.
WARNING
UNINTENDED EQUIPMENT OPERATION
Adapt the below examples to configure device or communication network parameters before you
implement them.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Refer to the configuration manual for communication networks and Control devices.
This figure represents the hardware configuration:
Introduction
Configure each Altivar 71/61 device in such a way that it is on the same network as the PLC that
controls it.
Overview
To implement I/O exchange operations between the speed driver and the PLC, both the
ATV 61/ATV 71 IO Scanner and I/O scanning of the controllers have to be configured.
Change the configuration to match the inputs and outputs expected by the
device defined in Control.
The configuration required corresponds to the inputs (ATV7161_IN_DDT)
and outputs (ATV7161_OUT_DDT).
Procedure
After the IOScanner is configured, follow the procedure to modify the IOScanner configuration:
NOTE: You can change this password but store it in the memory to modify
this configuration in future.
2 After entering the IO SCANNER home screen with disable option appears:
password, disable
IO SCANNER by
selecting No from
IO Scanner list.
4 After you have This action causes the speed driver to store the new configuration in its
finished setting the memory.
configuration, click
Save button.
NOTE: If you have followed the above steps, the IO SCANNER home screen with the data
configured in the speed driver appears when it is activated.
Description
To control the speed driver, configure the I/O scanning of the controller.
This configuration is different for each module and needs to match corresponding IO Scanner
configuration of the devices.
In the Modicon M340 automation platform, IO scanning is only available if the hardware
configuration features a NOE communications module.
This parameter configuration is used to define the relationship between the function I/Os and the
device I/Os, which are configured with the IO Scanner.
The ATV7161 function requires 8 input words in the ***_Inputs variable (ANY_ARRAY_INT) and
6 output words for the ***_Outputs variable (ANY_ARRAY_INT).
The first I/O scanning word is reserved, this means that an I/O Scanning row with 9 read words and
7 write words has to be configured.
The following table describes data variables:
When this configuration is used, the data used by the controller is as follows
The following figure shows configuration data used by the controller:
Section 22.3
Tesys T Control Block on Ethernet
Overview
This section provides the complete connection and setup details of TeSys T devices connected
through Modbus TCP (Ethernet) on Modicon M340, M580, or Quantum automation platforms.
WARNING
UNINTENDED EQUIPMENT OPERATION
Adapt the below examples to configure device or communication network parameters before you
implement them.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Refer to the configuration manual for communication networks and Control devices.
The following figure represents the hardware configuration of the Tesys T devices:
Introduction
Configure each Tesys T devices on the same network as the PLC that controls it.
After you are connected, you have to define the options that appear in the following figure.
Description
To control the Tesys T, configure the I/O scanning of the controller.
In the Modicon M340 automation platform, IO Scanning is only available if the hardware
configuration features a NOE communications module.
This parameter configuration is used to define the relationship between the function I/Os and the
device I/Os.
2 different Tesys T functions use I/O scanning. A function (ETESYST) uses limited amount of words
that are refreshed very quickly and the other function (EIOSTESYST) reads a large portion of the
words available but at lower speeds.
The ETESYST function requires 4 input words in the Inputs variable (ANY_ARRAY_INT structure)
and 3 output words in the Outputs variable (ANY_ARRAY_INT structure). The input words are
read starting on word 2502, and the write words are written starting on word 2506.
The EIOSTESYST function requires 64 input words in the Inputs variable (ANY_ARRAY_INT
structure) and 5 output words in the Outputs variable (ANY_ARRAY_INT structure). The input
words are read starting on word 451, and the output words are read starting on word 700. The
refresh rate has to be more than or equal to 200 ms.
The data used in the controller by the ETESYST DFB is as follows::
Section 22.4
Modbus Devices Used Through Gateway
Overview
This section provides the complete connection details of several devices on an Ethernet network
using an M340 controller and a TSXETG100 gateway.
M340 Controller
This section includes an example that shows how to connect several devices on an Ethernet
network using M340 controller and a TSXETG100 gateway. Refer to the hardware manual and the
Communication library manual for more details regarding the elements used in this example.
This figure represents the hardware configuration of M340 controller:
Configuration Procedure
This table describes the procedure to configure the IP address within the Ethernet network:
2 Configure the Configure the new IP address (which needs to be within the working range),
gateway address. the media type (type of cable), and the baud rate for communicating with the
devices on the Ethernet network.
This figure represents the IP address configuration:
General
The TSXETG100 gateway can operate either in Master mode or in Slave mode. Normally, it needs
to operate in the Master mode for SGU solutions.
Master Mode
The gateway function as the Master for the Modbus network under it, forcing a communication
speed and parity for the entire network that it controls and a time out in case of a communications
interruption.
Timeout
The configurable TimeOut time is the Hardware time out.
Slave Mode
This gateway model can also work in Slave mode, in which case it serves as an additional slave in
the Modbus network. This is useful in networks in which the network Master is a PLC on a Modbus
network . To this you can connect an Ethernet slave, that is, the exact opposite route when
compared to the one described in this manual.
Polarity
Regarding the polarization of the Modbus network and the addition of terminating resistors, the
EGT100 gateway has micro switches available for their configuration.
This figure shows the gateway with Polarization circuit:
Program Procedure
The control program for the 2 variable speed drives and for the ATS 48 starter using the CPUs own
Ethernet port is as follows.
This table describes the declaration and configuration of the parameters for the devices on the
Modbus network.
2 Declare and configure the The second speed driver is configured with address 2.
second speed driver with This figure represents the configured second speed driver.
address 2.
4 Insert EGtwMB DFB. The IP address needs to be entered in the GatewayAddress input
variable.
This figure represents the EGtwMB DFB:
NOTE: The name of the EGtwMB_MBWorkMemory variable needs to match in the ATV, ATS, and
EGtwMB.
NOTE: The name of the EPortM_EWorkMemory variable needs to match in the EGtwMB and
EPortM.
Section 22.5
Configuration Procedure for Device DTM
Overview
This section describes the procedure to add and configure device DTM to communicate with
device control function.
Overview
In this section, ATV6171 is taken as reference for the user. This example has to be used while
configuring other devices. For each device, user has to select the respective device IO
profile/parameter in DTM, which is mentioned in the section (see page 549).
Prerequisites
Download and install the supported DTM version from Schneider website.
Example: How to Add and Configure ATV61/71 DTM and Communicate with the Control Function
Supported DTM Version for ATV61/71
The following DTM version is required while communicating with ATV61/71:
ATV71 v 2.0.1.0
ATV61 v 2.0.0.9
NOTE: For required DTM version of other device (see page 549)
Step Action
1 Install the supported DTM version.
2 Navigate to Tools menu, select Hardware Catalog.
NOTE: For the M580 controller, Navigate to Tools → Project Settings → Build setting, and
select the Enhanced as a Property value from the drop-down menu for the Property Label I/O
Scanning mode. Then click OK or Apply.
Step Action
3 In the Hardware Catalog window, navigate to DTM Catalog tab. Check if the ATV71 or ATV61
DTM is visible. If yes, click Update.
Step Action
4 Navigate to TOOLS → DTM Browser.
Step Action
6 Navigate to Project Browser, double-click Variables & FB Instances to view ATV71 or ATV61
structure variables, which comprise of element configured in IO Scanner table.
Step Action
7 Perform the following mapping of ATV71 or ATV61 DTM structure variable to ATV7161 DFB:
Map ATV71.Inputs ↔ DTMInputs
Map ATV71.Outputs ↔ DTMOutputs
Map ATV71.Freshness ↔ IOScannerStatus
Step Action
1 Right click Master DTM → Add
Step Action
3 Select Required protocols as Modbus over TCP in the Protocol information tab and click OK.
Step Action
6 Navigate to Parameters tab, select Input scanner and uncheck Enable IO scanner) option.
Configure Input IO scanner table as shown in the following figure. Then, check the Enable IO
Scanner option.
7 Navigate to Parameters tab, select Output canner and uncheck Enable IO Scanner) option.
Configure Output IO scanner table as shown in the following figure. Then, check the Enable IO
Scanner option.
Adding Device DTM using Field Bus Discovery and Configuring IO Scanner Table (Online Mode)
Step Action
1 In the Master DTM configuration window, change the IP address to local system IP address in
the Source IP address. Set the Modbus network detection range to the device IP address range
and click OK.
Step Action
4 Right-click on master DTM and select Field bus discovery.
Step Action
6
In the Field bus directory window, select the ATV71 device and click symbol. Click OK.
Step Action
7 In DTM Browser window, right-click on the added ATV71 or ATV61 device and click Connect.
8 In the DTM Browser window, right click on ATV71 or ATV61 and click Load data from device.
Step Action
9 In the Parameters tab, select Input Scanner and uncheck Enable IO Scanner option. Configure
Input IO Scanner table as shown in the following figure. Then, check the Enable IO Scanner
option.
Step Action
10 In the Parameters tab, select Output Scanner and uncheck Enable IO Scanner option.
Configure Output IO Scanner table as shown in the following figure. Then, check the Enable IO
Scanner) option.
Overview
This section describes the profile/parameter that needs to be selected in addition to common
configuration defined in the above section, for different device DTM while communicating with the
respective device control function.
Section 22.6
Modbus TCPIP - Implicit with IOScanning
Overview
In this section, ATV71 and Quantum controller are taken as reference for the user. This example
has to be used for creating an application with any other Modbus TCPIP devices or controller.
Prerequisite
Configure the device for Ethernet communication with appropriate settings. Verify that device is
ready and is communicating with controller and the PC used for configuration.
Supported Architecture
Configuration
Configure Ethernet communication networks for NOE and CPU with I/O scanning enabled as
shown in the following figures:
Step Action
1 Set the IP address, read write addresses (%MW) and length of data being exchanged as shown
in the following figure (Mandatory). The IP address and IO scanner configuration are show in
the following figures.
Step Action
2 Key parameters to be set (same for IO scanning with NOE except for health block address)
IP address - Define the IP address of the actual device.
Unit ID - This associates the slave address of the device connected to Modbus/Ethernet
gateway to the IP address of the gateway. For this example, set the value to 255 (default
value).
Health timeout (0-65535 ms) - Maximum time allowed for the device to respond to assert
healthiness. The device will be invalid if it exceeds the maximum health timeout value.
Set the health timeout value to 1000ms (default value is equal to1500ms). Health timeout
should be greater than repetitive rate for NOE and should be greater than scan time for CPU.
Repetitive rate (0 to 65535ms in multiples of repetitive step: 0 to 200ms) - Rate at which
data is scanned from the device. Set the value as 60ms (default value).
RD master object - Destination address in the master controller/PLC where data has to
be stored (%MWxx).
RD slave ref - Source address in the slave/remote device (slave syntax dependent which
is usually %MWxx).
Read length - Number of words to be read (9 in case of ATV71)
Last value - Value to be set in the event of a detected error related to access of the device.
Set to 0 = Values fall back to 0.
Hold = Holds the previous value.
WR master object - Source address of the controller/PLC whose data is being written in
the remote device (%MWxx).
WR slave ref - The address of the first word written in the remote device (%MWxx).
WR length - Number of words to be written.
Device control block - Defines the value 101 to 108 (default).
Health block (%IW- available only for NOE) - This address sets the starting address of
the health word for devices. Each bit in the word indicates the health status of the device.
For example, %IW1.15 has the health status of device 1 (ATV71E). This has to be mapped
to IO scanner variable.
In the example, health block address id is set as %IW1.
Instantiation
Step Action
1 Instantiate ATV7161 DFB in FBD section and add variables as shown in the following figure:
2 Declare ATV71E_1_ATV_FailCode variable and link to the Failcode pin of the DFB
(Mandatory).
3 Declare variables ATV71E_1_ATV_IOSSts and link to pin IOScannerStatus (Mandatory)
Step Action
4 Create DDT types ATV7161_IN_DDT, ATV7161_OUT_DDT (Mandatory).
NOTE: These DDTs are specific to ATV71E DFB.
Step Action
7 Mapping addresses:
Define the address for variable ATV71E_1_ATV_IOSSts as %IW1.15. This is the
IOScanner address that indicates the health of the device. In case of IO scanning with NOE
health word can be defined (%IW).
NOTE: Address format to be defined (see page 559).
Input Variable Mapping
Map variable ATV71E_1_ATV_INData1 to address %MW319. Address value to be
entered as per IO scanner is RD master object address +1 as defined for reading data in
IO scanning.
Output Variable Mapping
Map ATV71E_1_ATV_OUTData1 to address %MW312. Address Value to be entered as
per IO scanner is WR Master Object address +1 as defined for writing data in IO
scanning.
Step Action
1 After configuring the device, build and transfer the program to controller.
2 With controller in Run mode, reset failures (RESETFAIL_USER), configure the variable values
for direction input (DIRECTION_USER) and set point (SETPOINT_USER).
3 Start the drive (RUN_USER) and check if it is working. Reset failures if any using
RESETFAIL_USER variable connected to Resetfailinput of the DFB.
Section 22.7
Modbus TCPIP - Implicit with Device DTM
Overview
This document explains the process of creating an application using Modbus TCPIP implicit
Communication Technology through NOC. ATV7161 is used as a reference. However, same
procedure can be used for creating an application with other devices.
Prerequisites
Download and install the supported DTM version from Schneider website.
The following DTM version is required while communicating with ATV61/71:
ATV71 v 2.0.1.0
ATV61 v 2.0.0.9
Supported Architecture
Configuration
Reserve sufficient memory based on the length of data required for the device connected to NOC
through Ethernet.
User has to set, read write addresses (%MW - 9 read and 7 write for ATV7161) and length of data
being exchanged as shown in the following graphics.
Step Action
1 Install the supported DTM version.
2 Navigate to Tools menu, select Hardware Catalog.
Step Action
3 In the Hardware Catalog window, navigate to DTM Catalog tab. Check if the ATV71 or ATV61
DTM is visible. If yes, click Update.
Step Action
4 Navigate to TOOLS → DTM Browser.
Step Action
6 Navigate to Project Browser, double-click Variables & FB Instances to view ATV71 or ATV61
structure variables, which comprise of element configured in IO Scanner table.
Step Action
1 In DTM Browser, Right-click Master DTM → Add.
Step Action
3 Select Protocol Required as Modbus over TCP in the Protocol information tab and click OK.
Step Action
6 Navigate to Parameters tab, select Input scanner and clear Enable IO scanner option.
Configure Input IO scanner table as shown in the following figure. Then, check the Enable IO
Scanner option.
7 Navigate to Parameters tab, select Output scanner and clear Enable IO Scanner option.
Configure Output IO scanner table as shown in the following figure. Then, check the Enable IO
Scanner option.
Adding Device DTM using Field Bus Discovery and Configuring IO Scanner Table (Online Mode)
Step Action
1 In the Master DTM configuration window, change the IP address to local system IP address in
the Source IP address. Set the Modbus network detection range to the device IP address range
and click OK.
Step Action
4 Right-click on Master DTM and select Field bus discovery.
Step Action
6
In the Field bus directory window, select the ATV71 device and click symbol. Click OK.
Step Action
7 In DTM Browser window, right-click on the added ATV71 or ATV61 device and click Connect.
8 In the DTM Browser window, right click on ATV71 or ATV61 and click Load data from device.
Step Action
9 In the Parameters tab, select Input Scanner and clear Enable IO Scanner option. Configure
Input IO Scanner table as shown in the following figure. Then, check the Enable IO Scanner
option.
Step Action
10 In the Parameters tab, select Output Scanner and clear Enable IO Scanner option. Configure
Output IO Scanner table as shown in the following figure. Then, check the Enable IO Scanner
option.
Instantiation
Step Action
1 Instantiate ATV7161_0 DFB in FBD section and add variables as shown in the following figure:
2 Declare ATV71E_1_ATV_FailCd variable and link to the Failcode pin of the DFB (Mandatory).
3 Mapping variable:
ATV71Inputs
Quantum DTMInputs (In this example, ATV71EXX.Inputs is created by DTM addition)
M580/M340 DTMInputs (In this example, ATV71EXX.Inputs is created by DTM addition)
ATV71Outputs
Quantum DTMInputs (In this example, ATV71EXX.Outputs is created by DTM addition).
M580/M340 DTMInputs (In this example, ATV71EXX.Outputs is created by DTM addition)
ATV71Freshness
Quantum NOC hardware healthiness - NOCVariable_IN_HEALTH_BITS_IN[0].n for nth
device. (In this example for 1st device, Q_NOC78000_IN.HEALTH_BITS_IN[0].0)
M580/M340 DTMInputs (In this example, ATV71EXX.Freshness is created by DTM addition)
4 Map variables ATV71.Freshness and link to pin IOScannerStatus (Mandatory)
5 Map variable ATV71.Inputs of type ATV7161XX_IN and link the variable to DTMInputs pin.
6 Map variable ATV71.Outputs of type ATV7161XX_OUT and link the variable to DTMOutputs pin.
Step Action
1 Once the device is configured as explained above, build and transfer the program to controller.
2 With controller in Run mode, reset failures (RESETFAIL_USER), configure the variable values
for direction input (DIRECTION_USER) and set point (SETPOINT_USER).
3 Start the drive (RUN_USER) and check if it is working. Reset failures if any using
RESETFAIL_USER variable connected to Resetfail input of the DFB.
Read/Write Devices
Now you should be able to read/write devices.
Section 22.8
Modbus TCPIP - Explicit
Overview
In this section, ATV71 and Quantum controller is taken as reference for the user. This example has
to be used for creating an application with any other ModBus TCPIP devices or Controller.
Supported Architecture
Instantiation
Step Action
1 Instantiate EMESATV7161, ModbusEthernetPortQ and SDDEVCTL DFBs (see page 582).
NOTE: Select respective Port DFB based on the controller family.
2 Declare Failcode variable and link to the Failcode pin of the DFB (Mandatory).
3 Declare Workmemory variable and verify the same variable is linked to the devices and port
DFB.
4 Declare LocatedArea variable, allocate the memory address (%MWx) and link to the Port
DFB.
Here we are communicating with agitator (EMESATV7161 DFB) using port DFB
(ModBusEthernetPortQ)
NOTE: All device DFB communicating to port block should be executed before port DFB executes.
Example: Execution order of DFBs has to be DFB1...DFBn → Port DFB
Configuration
Step Action
1 Define device address pin of ModBus TCPIP device DFB (see page 581).
NOTE: Follow the syntax '{XXX.XXX.XXX.XXX}xx' ('{IP Address}UnitID')
2 Define the public variable PortAddress of port DFB as shown in the following figure.
Step Action
1 Build and transfer project to PLC.
2 Check the value of WantedArraySize of Port DFB.
3 Change array size of Workmemory variable to the value equal to WantedArraySize and
transfer the changes to PLC.
Read/write devices
Now you should be able to read/write devices.
Section 22.9
Modbus TCPIP - Explicit with Gateway
Description
This section describes the procedure to create an application using Modbus serial communication
technology (Explicit). In this example ATV71 and Quantum controller is used as reference.
However, same procedure can be followed for creating an application with any other Modbus serial
devices or controller.
Prerequisite
Verify that the device is configured for Ethernet communication with appropriate settings. Verify
that device is ready and is available for communicating with gateway.
Supported Architecture
Instantiation
Step Action
1 Instantiate DFB MBATV7161, ModBusGateway and ModbusEthernetPortQ (see page 587).
2 Declare Failcode variable and link to the Failcode pin of the DFB (Mandatory).
3 Declare WorkmemoryMB variable, verify the same variable is linked to the devices WorkMemory
pin of MBATV7161 DFB and WorkMemoryRS485 pin of ModbusGateway DFB.
Declare variable WorkMemory and link it to pin WorkMemoryEthernet (ModbusGateway
DFB) and pin WorkMemory (ModbusEthernetPortQ DFB).
4 Declare LocatedArea variable, allocate the memory address (%MWx) and link to the port DFB.
NOTE: Applicable only for ModbusEthernetPortQ DFB.
Syntax
NOTE: User can communicate using either CPU or NOE with address as per the above format. In
this example NOE at slot 6 has been used and hence value 6 has to be set to port address.
Configuration
Step Action
1 Define ModBusAddress pin of Modbus serial device DFB after instantiation as shown in the
above figure..
NOTE: Follow the syntax - XXX (Example 10).
2 Define GatewayAddress pin of ModBus gateway device DFB (see page 585).
NOTE: Follow the syntax - '{XXX.XXX.XXX.XXX}' (i.e '{IP Address}').
3 Define public variable PortAddress of port DFB.
NOTE: Syntax to be followed (see page 588).
Step Action
4 Defining variables and array size for WorkMemory and WorkMemoryRS485 pins for port DFB
and gateway DFB:
1. Build and transfer project to PLC.
2. Check the value of WantedArraySize of port DFB and gateway DFB.
3. Disconnect project from PLC and change array size to variable WorkMemoryMB connected
to WorkMemoryRS485 pin (ModbusGateway DFB) and WorkMemory pin (ATV7161MB
DFB), array size has to be equal to WantedArraySize (Calculated by ModbusGateway
DFB in first program scan). In this example wanted array size is 109 and hence the array
size of the variable WorkMemoryMB is ARRAY[1..109] OF INT.
Controller Family
Read/Write devices
Now you should be able to read/write devices.
Chapter 23
Modbus over ULP Technology
Step Action
1 Instantiate MBUMASTERPACTMTZ and ModbusPortM so that ModbusPortM DFB should have
higher execution order than MBUMASTERPACTMTZ DFB.
NOTE: The variable connected to WorkMemory should have size greater than or equal to wanted
array size.
Creating a Project with $MasterpactMTZMBU for IFE or IFE stacked with IFM
connected to Masterpact MTZ and Modbus Ethernet RJ45 Ports
Step Action
1 Instantiate MBUMASTERPACTMTZ, ModbusGateway and ModbusEthernetPortM so
that ModbusEthernetPortM DFB should have higher execution order than
ModbusGateway DFB and ModbusGateway DFB should have higher execution
order than MBUMASTERPACTMTZ DFB.
NOTE: The variable connected to WorkMemory should have size greater than or
equal to wanted array size.
Chapter 24
Modbus Technology
Modbus Technology
Overview
This chapter describes the configuration and setup details of the devices connected through
Modbus on the Modicon M340 automation platform.
Section 24.1
General
General
Overview
This section describes the complete configuration and setup details of the devices connected
through Modbus on the Modicon M340 automation platform.
Modbus Technology
WARNING
UNINTENDED EQUIPMENT OPERATION
Adapt the below examples to configure device or communication network parameters before you
implement them.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Refer to the configuration manual for communication networks and Control devices.
This figure shows the complete configuration and setup details for the devices connected through
Modbus on the Modicon M340 automation platforms.
Introduction
This section provides guidelines for correctly selecting Timeout and Refresh times based on the
known parameters by using an example with a Modbus connection close to 10 ATV 31 devices:
Hardware Timeout
The timeout setting is selected on the MB physical port (PCMCIA or module). During this time, the
PLC HW uses as the maximum permissible time that can elapse before indicating a detected
failure if it does not receive a response to any sent request.
With a Modbus TSX SCY21601 module, for example, the module Timeout is 3 seconds (1 second
x 3 retries). When connecting 10 ATV31 devices on Modbus, a good setting would be to set the
time to 200 ms and 1 retry (400 ms).
Software Timeout
The timeout setting is selected on the serializer (ModbusPort - component that manages the
Modbus port). During this time, the SW uses as the maximum permissible time that can elapse
before indicating a detected failure if it does not receive a response from any of the devices.
The following is the minimum time that needs to be selected:
With Hardware Timeout = tHW
Software Timeout > tHW x No. of simultaneous send operations (Modbus port Simultane-
ousSends public parameter).
The default number of simultaneous requests managed by the ModbusPort is 4. (The SGS on the
Modbus port function generates a value of 4 for simultaneous transmissions.)
Device Timeout
This timeout is selected on the speed driver. During this time, the device uses as the maximum
permissible time that can elapse before indicating a detected failure if it does not receive any
requests. It tends to be a large number, but as a guideline:
Device Timeout > tHW x No. of devices connected to the Modbus port
For instance , if the network has 10 ATV 31devices, check the timeout value that is configured in
the parameters of each communications menu of the ATV 31:
Device Timeout > 400msec x 10 devices → Device Timeout > 4 s
The guidelines are as follows:
The value of this timeout depends on the conditions that you establish for the ATV 31 when
operating it. That is, a timeout of 4 seconds for each ATV 31 means that if the ATV 31 ceases
to communicate, it stops or indicate a detected failure after 4 seconds.
If there is a communications interruption with an ATV 31, the master attempts to establish
communications with the device, and with that device only, during the time specified in the
Hardware Timeout.
In this example, the master attempts to establish communications with the ATV 31 that is having
a communication interruption of 400 ms.
As a result, if the device Timeout < Hardware Timeout (that is, lower than 400 ms in this
example), the remaining network devices begins to drop out (indicate a detected error)
consequently due to a timeout while the master is attempting to establish communications with
the first ATV 31.
NOTE: The device Timeout need to be higher than the Refresh time (Refresh).
Refresh
Refresh is the data refresh time, that is, the time between the cyclic requests sent to each one of
the devices.
This time must be sufficient for the data to be refreshed quickly but not so short as to saturate the
bus with cyclic requests.
An estimated value between 200 and 1500 is necessary to refresh their data depending on the type
of devices and the number of requests.
Section 24.2
Configuring the Devices
Overview
This section explains the configuration of the devices.
Description
The speed drives are connected to Modbus networks through an RJ45 connector.
Configure each Altivar 31, Altivar 312, and Altivar 12 devices with the same baud rate and with a
different station number so that each device is uniquely identified on the Modbus bus.
From the actual ATV without a programming console, in the Con menu for ATV 31 units and the
Conf → FULL → Con menu for ATV 312 and ATV 12 units:
PrO : Protocol (Modbus RTU)
Adrc or Add: Modbus address
Bdr or tpr: Baud rate (19.2 = 19200 bps)
Tfo: Communications mode (normally 8E1)
tto : Communications Timeout (10 s by default)
NOTE: Communication parameters are recognized after the device is energized, that is, when the
parameters are edited, the device has to be power cycled so that the parameters are applied.
Description
The ATV 71/61 speed driver is also connected to the Modbus network through a RJ45 connector.
That is, you can use an infrastructure identical to that used for the ATV 31.
Configure each Altivar 71 device with the same baud rate and with a different station number so
that each device is uniquely identified on the Modbus bus.
From the actual ATV without a programming console, in the menu; or from the 1.9
COMMUNICATION menu if there is a parameter configuration console:
Add : Modbus address
Tbr : Baud rate (19.2 = 19200bps)
Tfo : Format (8-N-1 by default)
tto : Communications Timeout (10 s by default)
Tesys U
Description
The LULC033 is the communications module for Tesys U starters and controllers that is used for
communicating with the M340 platform directly on the Modbus.
The Tesys U communications module is connected to the Modbus network through an RJ45
connector.
The available protection and control information depends on the control unit with which the Modbus
communications module is associated.
The Tesys U communications module has 3 types of control unit:
Standard (reference: LUCA)
Advanced (references: LUCB/C/D, LUCBT/DT)
Multifunction (references: LUCM/MT)
The following table shows the information and controls that can be accessed with each type of
control unit:
The range of accepted values goes from 1 to 31, and the address code is binary. The least
significant bit is on the right and is indicated with .
NOTE: Addressing is recognized after the communications module is energized.
The control block implemented in the SGU is programmed to work with the factory default
configuration.
The parameter configuration of the communications module enables you to define the following:
The operating mode
The reset mode for a reset due to a thermal overload event
The correspondence between the communication module outputs and the LUTM controller
inputs
The parameter configuration registers (Modbus protocol) can be accessed in read/write mode or
with the Power Suite software.
The following table shows factory default values:
Recovery mode after stop 688 0 The outputs revert to the state before the
power supply interrupted.
Controller
If a controller is used, 7 inputs are used in a configuration by using a communications module.
Tesys T
Description
To connect a Tesys T device on a Modbus network, the following communication parameters need
to be configured.
Parameter Value
Network Modbus (Device Settings menu)
Address From 1 to 247 (Network Port menu)
Baud rate From 1200 bps to 19200 bps (Network Port menu)
Parity Even or No Parity (Network Port menu)
Description
NOTE: A reference to the ATS 48 unit is also referred to the ATS 22 unit unless otherwise
specified.
The ATS 48 starter is connected to the Modbus network through an RJ45 connector.
Configure each ATS 48 device with the same baud rate and with a different station number so that
each device is uniquely identified on the Modbus bus.
Access the COP menu and configure the following:
Parameter Description
Add ATS 48 Modbus address within the Modbus network.
Address from 0 to 31 for ATS 48 units and from 0 to 247 for ATS 22 units.
tbr Network baud rate at 4800, 9600, or 19200 bps.
FOr Configure the amount of communication bits (8 bits), parity (even, odd, or no parity),
and 1 or 2 Stop bits.
TLP/TTO (TTO for ATS 22 units) Time out. You can configure with a value of 0.1 to 60.0 in 0.1 s
increments.
Ctrl Only for ATS 22 units. Enables you to configure whether control is Modbus-based or
screw terminal-based. Configure dbS for Modbus-based control.
The timeout configured on the ATS 48 device has to be longer than the time configured in the
Refresh variable of the generated component.
NOTE: Communication parameters are recognized after the device is energized.
To use PLC-based control, the following connection needs to be made.
SEPAM
Description
Modbus communication allows connecting Sepam units to a monitor that is equipped with a master
Modbus communications path.
To connect this unit, an ACE949-2 (2-wire RS485 network connection interface) or ACE949 (4-wire
RS485 network connection interface) interface module with a 12 VCC or 24 VCC power supply is
required.
This figure shows the Sepam series 80 configuration:
Parameter Value
Bus Modbus
Address From 1 to 247
Baud Rate From 1200 bps to 19200 bps
Parity Even, odd, or no parity
PM
Description
Configure each PM device with the same baud rate and with a different station number so that each
device is uniquely identified on the Modbus bus.
After accessing the internal menu of the signal analyzer, configure the following:
Description
Both Compact and Masterpact units are configured the same way in the Modbus section. This
configuration is implemented with the TRV00210 device.
This device automatically detects the baud rate of the bus as long as it is working with 8 bits, even
parity, and 1 stop bit.
The rotary selectors on the front of the device are used to configure the Modbus node address
(address from 1 to 99). To control the device remotely, the last selector has to be pointing at the
open lock symbol.
Section 24.3
Modbus Serial - Explicit
Overview
This section describes the procedure to create an application using Modbus communication
technology (Explicit).
Overview
In this example ATV71 and M580 controller is used as a reference. However, same procedure can
be followed for creating an application with any other Modbus devices or controller.
Architecture
Instantiation
Step Action
1 Instantiate MBATV7161, ModbusPortM and SDDEVCTL DFBs.
2 Declare Failcode variable and link to the Failcode pin of the DFB (Mandatory).
3 Declare Workmemory variable, verify the same variable is linked to the devices and port DFB.
NOTE: All device DFBs communicating to port block should be executed before port DFB
executes.
In this example we are communicating with ATV71 (MBATV6171) using port DFB (ModbusPortM).
Example: Execution order of DFBs has to be DFB1...DFBn → Port DFB
Configuration
Step Action
1 Define Modbus address pin of Modbus device DFB. Refer to the above figure.
2 Define public variable PortAddress of Port DFB (see page 618).
NOTE: Follow the syntax - 'XX.XX.X' ('Rack.Slot.Channel')
In this example we are using M580 family NOM for Modbus serial communication.
Step Action
1 Build and transfer project to PLC.
2 Check the value of WantedArraySize of port DFB.
3 Change array size of Workmemory variable to the value equal to WantedArraySize and
transfer the changes to PLC.
Read/Write Devices
Now you should be able to read/write devices.
Overview
In this example ATV71 and Quantum controller with X80 Drop (BMECRA31210) and NOM is used
as a reference. However, same procedure can be followed for creating an application with any
other Modbus devices or Quantum Controller with other X80 Drops (BMXCRA31210).
Architecture
Instantiation
Step Action
1 Instantiate MBATV7161, ModbusPortQX80, CONDSUM, CONDSUM1 and Motor2 DFBs
2 Declare Failcode variable and link to the Failcode pin of the DFB (Mandatory).
3 Declare Workmemory variable, verify the same variable is linked to the devices and port DFB.
NOTE: All device DFBs communicating to port block should be executed before port DFB
executes.
In this example we are communicating with one ATV71 (MBATV6171) using port DFB
ModbusPortQX80.
Example:Execution order of DFBs has to be DFB1...DFBn → Port DFB
Configuration
Step Action
1 Define Modbus address pin of Modbus device DFB. Refer to the above figure.
2 Define public variable EthPortAddress of Port DFB.
NOTE: Follow the syntax - '1.XX.1' ('1.Slot.1').
3 Define public variable CRAIPAddress of Port DFB.
NOTE: Follow the syntax - 'XXX.XXX.XXX.XXX'.
4 Define public variable MBPortAddress of Port DFB.
NOTE: Follow the syntax - 'XX.XX.X' ('Rack.Slot.Channel').
In this example we are using Quantum family with X80 Drop with NOM for Modbus serial
communication
Step Action
1 Build and transfer project to PLC.
2 Check the value of WantedArraySize of port DFB.
3 Change array size of Workmemory variable to the value equal to WantedArraySize and
transfer the changes to PLC.
Read/Write Devices
Now you should be able to read/write devices.
Overview
In this example ATV71 and M580 controller with X80 Drop (BMECRA31210) and NOM is used as
a reference. However, same procedure can be followed for creating an application with any other
Modbus devices or M580 Controller with other X80 Drops (BMXCRA31210).
Architecture
Instantiation
Step Action
1 Instantiate MBATV7161, ModBusPortM58X80, CONDSUM, CONDSUM1 and Motor2 DFBs
2 Declare Failcode variable and link to the Failcode pin of the DFB (Mandatory).
3 Declare Workmemory variable, verify the same variable is linked to the devices and port DFB.
NOTE: All device DFBs communicating to port block should be executed before port DFB
executes.
In this example we are communicating with one ATV71 (MBATV6171) using port DFB
ModBusPortM58X80.
Example:Execution order of DFBs has to be DFB1...DFBn → Port DFB
Configuration
Step Action
1 Define Modbus address pin of Modbus device DFB. Refer to the above figure.
2 Define public variable EthPortAddress of Port DFB.
NOTE: Follow the syntax - 'XX.XX.X' ('Rack.Slot.Channel').
3 Define public variable CRAIPAddress of Port DFB.
NOTE: Follow the syntax - 'XXX.XXX.XXX.XXX'.
4 Define public variable MBPortAddress of Port DFB.
NOTE: Follow the syntax - 'XX.XX.X' ('Rack.Slot.Channel').
In this example we are using M580 family with X80 Drop with NOM for Modbus serial communication
Step Action
1 Build and transfer project to PLC.
2 Check the value of WantedArraySize of port DFB.
3 Change array size of Workmemory variable to the value equal to WantedArraySize and
transfer the changes to PLC.
Read/Write Devices
Now you should be able to read/write devices.
Chapter 25
Profibus Technology
Profibus Technology
Section 25.1
Profibus Communication Using PRM
Overview
This document guides in creating an application using Profibus communication technology.
TESYST and M580 Controller is used as a reference. However, same procedure can be followed
for creating an application with any other Profibus device or controller
Architecture
Step Action
1 Install the supported DTM version.
2 Navigate to Tools menu, select Hardware Catalog.
Step Action
3 In the Hardware Catalog window, navigate to DTM Catalog tab and click Update.
Step Action
4 Navigate to TOOLS → DTM Browser.
Step Action
7 Configure public parameters of instance of PRMMgtX.
How to Configure PRM Master DTM and IO Scanner Table Using Quantum CPU/M340 CPU/NOE
Prerequisite: User needs to make sure IP address of Quantum CPU/M340 CPU/NOE module is
configured to PRM Master with which it communicates.
Step Action
1 Right-click Host PC of DTM Browser and click Add.
Step Action
3 Navigate to Protocol information tab, select Profibus DVP1 in the Protocol supported list and click
OK.
Step Action
5 Navigate to General Settings tab, configure IP and MAC Address table as shown in the following
figure. Then, click Apply.
Example:
Step Action
8 Add PRM_Master DTM for the configured IOScanning line and click OK.
Step Action
10 If update is successful, the Device DDT generate by Control Expert is shown in the image below.
Step Action
11 Perform Store data to Device of PRM Master.
Step Action
1 Right-click on Master under which the user wants to have PRM Gateway DTM and click Add.
Step Action
2 Select PRM Gateway DTM and click Add DTM.
Step Action
3 Select the protocol as shown in the figure below.
Step Action
4 Open the Master DTM to configure Source IP Address in Channel Properties tab.
Step Action
6 Configure Gateway DTM according as per user requirements.
Step Action
1 Add gsd file into library, as shown in following figure:
2 While PRM Gateway is online, perform FieldBusDiscovery and then add device.
Step Action
3 Open TesysT DTM to select the profile and click Add.
Step Action
5 After update is successful, the generated Device DDT variables are as shown in figure below.
Step Action
6 After performing Store data to device as shown in step 7 (see page 641), Map pins of DFB with
device DTM variables:
Inputs: LTMR_Tesys_T_Profibus.Inputs.MMC_R_IN_1
Outputs: LTMR_Tesys_T_Profibus.Outputs.MMC_R_OUT_1
Step Action
7 Transfer the project to PLC and change the state of controller to RUN.
Chapter 26
CANOpen Technology
CANOpen Technology
Section 26.1
Advantys Communication using IO Scanning
Overview
This document explains the steps to be followed for configuring Advantys island in Control Expert
using IOScanning. ATV61 is used as a reference. However, same procedure can be used for
creating an application with other devices.
Architecture
Step Action
1 Open the created Ethernet network and enable IOScanning option in Communication
configuration.
2 Create an IOScanning line for the device to communicate. This example shows Advantys with
IP address 192.168.1.114. Read/write address and length has to be entered in the
IOScanning line. Read/Write length required would change depending on the module used in
the Advantys island. For more details refer Advantys user manual
3 Click the icon highlighted in the following figure to select the Adavantys island in Control Expert.
Step Action
4 Select the Device type as STB from the drop-down list as shown in the following figure.
5 Enter the Device name and click the Launch Advantys Configuration Software option to enable
user operation and to open Advantys Island software.
Step Action
6 The architecture shown in the following figure is configured with a Digital input module
and CANOpen extension module. Two ATV drives ATV31 and ATV61 are selected under
CANOpen extension manual.
Step Action
7 Perform Build all and click Download into the island as shown in the following figure. On
completion of download the status Island is healthy will be displayed.
Step Action
8 Close the Advantys page in Control Expert, the popup shown in the following figure appears.
Select Yes, the modifications made will be reflected in Control Expert and Control Expert will
change to Not Build state.
9 Instantiate DFB ASATV7161 DEVCTL and create variable for Failcode pin of the DFB
(Mandatory).
10 The Inputs and Outputs variables highlighted in the following figure are used to transfer data
to the device. The CommunicationOK variable is used to know the communication status of
the device. Create pins as per the requirement.
NOTE: For address format to be used with the above pins (see page 662).
11 Inputs pin is used to provide the Status word of the device to be communicated.
For address format to be used with the above pins. (see page 662)
Step Action
12 Outputs pin is used to provide the Control word of the device to be communicated.
For address format to be used with the above pins. (see page 662)
NOTE: Create a variable with the data type "array of int" of size 2.
13 Create the required variables and perform Build all. Download the project to control the motor
using DFB.
Address Format
. . .
. . .
Device 128 %SW167.15 %IW8.0
Value Value
0 = Error 0 = Error
1 = Healthy 1 = Healthy
. .
. .
Device 12 %MW224
Index
A 553
Profibus Communication Using PRM, 630
Advantys Communication using IO Scanning
Compact
Advantys Communication using IO Scan-
Modbus communication configuration,
ning, 654
601
Altistart
Configuration Procedure for Device DTM
Modbus communication configuration,
Configuration Procedure for Device DTM,
601
533
Altivar
configuring the devices
Modbus communication configuration,
ATV 31, ATV 312 and ATV 12, 602
601
Altivar 71/61
configuring Altivar71/61 Ethernet commu- D
nication, 508
devices
Advantys Communication using IO Scan-
C ning , 654
Configuration Procedure for Device DTM,
circuit breakers
533
MBCOMPACTNSX, 49
configuring Altivar71/61 Ethernet commu-
communication
nication, 508
Advantys Communication using IO Scan-
configuring device Ethernet communica-
ning, 654
tion, 505
Configuration Procedure for Device DTM,
configuring device Modbus communica-
533
tion, 595
configuring Altivar71/61 Ethernet commu-
configuring Ethernet communication with
nication, 508
Modbus devices, 525
configuring device Ethernet communica-
configuring TeSys T Ethernet communi-
tion, 505
cation, 519
configuring device Modbus communica-
Modbus Serial - Explicit, 615
tion, 595
Modbus TCPIP - Explicit, 580
configuring Ethernet communication with
Modbus TCPIP - Explicit with Gateway,
Modbus devices, 525
584
configuring TeSys T Ethernet communi-
Modbus TCPIP - Implicit with Device
cation, 519
DTM, 562
Modbus Serial - Explicit, 615
Modbus TCPIP - Implicit with IOScanning,
Modbus TCPIP - Explicit , 580
553
Modbus TCPIP - Explicit with Gateway,
Profibus Communication Using PRM ,
584
630
Modbus TCPIP - Implicit with Device
digital protective relays
DTM, 562
SEPAM Profile, 119
Modbus TCPIP - Implicit with IOScanning,
E M
Ethernet MASTERPACT, 73
Configuration Procedure for Device DTM, Masterpact
533 Modbus communication configuration,
configuring Altivar71/61 Ethernet commu- 601
nication, 508 Modbus
configuring device Ethernet communica- configuring device Ethernet communica-
tion, 505 tion, 595
configuring Ethernet communication with configuring Ethernet communication with
Modbus devices, 525 Modbus devices, 525
configuring TeSys T Ethernet communi- device configuration details, 601
cation, 519 Modbus Serial - Explicit, 615
Modbus TCPIP - Explicit, 580 Modbus Serial - Explicit
Modbus TCPIP - Explicit with Gateway, Modbus Serial - Explicit, 615
584 Modbus TCPIP - Explicit
Modbus TCPIP - Implicit with Device Modbus TCPIP - Explicit, 580
DTM, 562 Modbus TCPIP - Explicit with Gateway,
Modbus TCPIP- Implicit with IOScanning, 584
553 Modbus TCPIP - Implicit
Ethernet technology Modbus TCPIP - Implicit with Device
CommunicationOK Variable, 506 DTM, 562
Modbus TCPIP - Implicit with IOScanning
Modbus TCPIP - Implicit with IOScanning,
G 553
gateway Modbus technology
configuring Ethernet communication with general, 596
Modbus devices, 525 Motor controllers and starters
general TeSys T Profile, 155
device resources overview, 21 motor controllers and starters
general overview of device components, Tesys U Profile, 191
19
supervision services, 27
general concepts O
function block interface, 28 OperationLimit, 111
monitoring, 31
set-point management, 30
General Purpose library automation system P
introduction, 19 Power Meter
Modbus communication configuration,
601
H power monitoring devices
Hardwired Circuit Breaker, 101 PM profile, 219
ACCUSINE PCS Profile, 259
Smart UPS Profile, 243
Profibus
Advantys Communication using IO Scan-
ning , 654
Profibus Communication Using PRM, 630
Profibus Communication Using PRM
Profibus Communication Using PRM ,
630
progressive starters
ATS Progressive Starter , 281
PSx General Purpose library for
Control Expert
list of function blocks, 21
S
safety module
XPSMC, 483
Sepam
Modbus communication configuration,
601
T
TeSys T
configuring TeSys T Ethernet communi-
cation, 519
Modbus communication configuration,
601
TeSys U
Modbus communication configuration,
601
V
variable speed drives
ATV Profile, 307
EMATVWarn - Extended Warnings of
Process Drives, 367
EMATVWarn1 - Extended Warnings of
Process Drives (Supports 12 Alarm regis-
ters), 405