Micom C264 en Um E50.5

MiCOM C264
Bay Control and Protection Unit

User Manual
Version: C264/EN UM/E50.5
06/2022
Legal Information
The Schneider Electric brand and any trademarks of Schneider Electric SE and its subsidiaries
referred to in this guide are the property of Schneider Electric SE or its subsidiaries. All other
brands may be trademarks of their respective owners.
This guide and its content are protected under applicable copyright laws and furnished for
informational use only. No part of this guide may be reproduced or transmitted in any form or by
any means (electronic, mechanical, photocopying, recording, or otherwise), for any purpose,
without the prior written permission of Schneider Electric.
Schneider Electric does not grant any right or license for commercial use of the guide or its
content, except for a non-exclusive and personal license to consult it on an "as is" basis.
Schneider Electric products and equipment should be installed, operated, serviced, and
maintained only by qualified personnel.
As standards, specifications, and designs change from time to time, information contained in this
guide may be subject to change without notice.
To the extent permitted by applicable law, no responsibility or liability is assumed by Schneider

Electric and its subsidiaries for any errors or omissions in the informational content of this material
or consequences arising out of or resulting from the use of the information contained herein.
Disclaimer
No responsibility is assumed by Schneider Electric for any consequences arising out of the use of
this guide. This guide is not intended as an instruction manual for untrained persons. The guide
cannot cover all conceivable circumstances or include detailed information on all topics. In the
event of questions or specific issues, do not take any action without proper authorisation. Contact
Schneider Electric and request the necessary information.
There may be websites linked to and from this site that are operated or created by organizations
outside of Schneider Electric. Those organizations are solely responsible for the operation and
information (including the right to display such information) found on their respective websites.
The linking to or from this site does not imply on the part of Schneider Electric any endorsement or
guarantee of any of the organizations or information (including the right to display such
information) found on their respective websites.
Schneider Electric does not assume and is not responsible for any liability whatsoever for the
linking of any of these linked websites, the operation or content (including the right to display such
information) of any of the linked websites, nor for any of the information, interpretation, comments
or opinions expressed in any of the linked websites. Any comments or inquiries regarding the
linked websites are to be directed to the particular organization for whom the particular website is
being operated.
Contact information
Schneider Electric
35 rue Joseph Monier

92500 Rueil Malmaison
France
+33 (0) 1 41 29 70 00
https://www.se.com
Safety Information
Important Information
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 bulletin or on the equipment to warn of potential
hazards or to call attention to information that clarifies or simplifies a procedure.
The addition of either symbol to a "Danger" or "Warning" safety label

indicates that an electrical hazard exists which will result in personal
injury if the instructions are not followed.
This is the safety alert symbol. It is used to alert you to potential personal
injury hazards. Obey all safety messages that follow this symbol to avoid
possible injury or death.
DANGER
DANGER indicates a hazardous situation which, if not avoided, will result in death or serious
injury.
Failure to follow these instructions will result in death or serious injury.
WARNING
WARNING indicates a hazardous situation which, if not avoided, could result in death or
serious injury.
Failure to follow these instructions could result in death, serious injury or equipment
damage.
CAUTION
CAUTION indicates a hazardous situation which, if not avoided, could result in minor or
moderate injury.
Failure to follow these instructions could result in injury or equipment damage.
NOTICE
NOTICE is used to address practices not related to physical injury.
Failure to follow these instructions could result in equipment damage.

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, installation,
and operation of electrical equipment and has received safety training to recognize and avoid the
hazards involved.
Secure Disposal
It is recommended that incineration and disposal to water courses is avoided. The

equipment should be disposed of in a safe manner and with a secure disposal of
confidential embedded information.
Secure disposal refers to the process and result by which information, including
information held on the equipment, is irreparably destroyed so as to maintain the
security of the equipment and information during the process and up to the point of
irremediable destruction.
Any equipment containing batteries should have them removed before disposal,
taking precautions to avoid short circuits. Particular regulations within the country of
operation, may apply to the disposal of the equipment.
Announcement
EcoStruxure™ Power Automation System (EPAS)
In case of former brand names such as “EcoStruxure Substation Operation”, “ESO” or “PACiS”,
are lingered in this documentation, please consider them as linked to "EcoStruxure™ Power
Automation System".
Communication Gateway
The communication gateway offer has been rebranded to “EcoStruxure™ Power Automation
System Gateway” (EPAS-Gateway). In case any of former brand names are inadvertently
lingered in, please consider them as linked to “EcoStruxure™ Power Automation System” and/or
“EcoStruxure™ Power Automation System Gateway”.
MiCOM C264 - User Manual Table of Contents
Table of Contents
Legal Information 2
Disclaimer 3
Safety Information 4
Announcement 6
Table of Contents 7
1 Overview 45
1.1 About this guide 46
1.1.1 Document updates 46
1.2 What's new? 47
1.2.1 Current guide revision 47
1.2.2 Previous guide revisions 47
1.2.2.1 Revision number: E50.4 (03/2022) 47
1.3 Document organization and content 49
1.4 How to use this document ? 50
1.5 How to read this document ? 51
1.6 Introduction to MiCOM range 52
1.7 Introduction to MiCOM C264 applications 53
1.7.1 MiCOM C264 Computers 53
1.7.2 Applications and Scope 53
2 Safety and Handling 55
2.1 Symbols and External Labels on the Equipment 56
2.2 Installing, Commissioning and Servicing 57
2.2.1 Qualified Persons 57
2.2.2 Earth / Ground 57
2.2.3 Mounting 58
2.2.4 Servicing and maintenance 59
2.2.5 UL and CSA / CUL Listed or Recognized equipment 60
2.2.6 Storage 61
2.3 Decommissioning and Disposal 62
2.4 Technical Specifications for Safety 63
2.4.1 Protective fuse rating 63
2.4.2 Protective Class 63
2.4.3 Installation Category 63
2.4.4 Environment 63
2.5 Compliance Marking for Applicable European Directives 64
2.6 Recognized and Listed Marks for North America 65
2.7 Recognized and Listed Mark for Custom Union and Russian Federation 66
2.8 Typical Labels 67
2.8.1 Labels for standard LED indicators and menu navigation keys 67
C264/EN UM/E50.5 7
Table of Contents MiCOM C264 - User Manual
2.8.2 General Labels 68

2.9 Handling of Electronic Equipments 71
2.10 Guarantees 72
2.11 Copyrights & Trademarks 73
2.11.1 Copyrights 73
2.11.2 Trademarks 73
2.12 Warnings Regarding use of Schneider Electric Products 74
3 Technical Data 75
3.1 Firmware technical data 76
3.1.1 MiCOM C264: Elements limits 76
3.1.2 MiCOM C264 with two extension racks with IED 78
3.2 Current transformer compatibility with MiCOM C264P 83
3.2.1 Introduction to current transformers 88
3.2.1.1 Current transformer magnetization 89
3.2.1.2 Limiting secondary voltage (Vk) 89
3.2.1.3 Rated accuracy limit factor 89
3.2.1.4 Primary winding current rating 90
3.2.1.5 Secondary winding current rating 90
3.2.2 Current Transformer Standards and Classes 90
3.2.2.1 Types 90
3.2.2.2 IEC 60044-1 standard 91
3.2.2.2.1 Class P CTs 91
3.2.2.2.2 Class PX 91
3.2.2.3 IEC 60044-6 standard 92
3.2.2.3.1 Class TPS 92
3.2.2.3.2 Class TPX 92
3.2.2.3.3 Class TPY 92
3.2.2.3.4 Class TPZ 93
3.2.3 Current transformer requirements for MiCOM C264P 93
3.2.3.1 Protection 93
3.2.4 Appendix A: Converting to a Limiting Secondary Voltage 95
3.2.5 Appendix B: Converting to IEEE Standard Voltage Rating 96
3.2.6 Appendix C: Use of METROSIL Non-linear Resistors 97
4 Functional Description 100
4.1 MiCOM C264 management 111
4.1.1 Operating mode management 111
4.1.1.1 Initialization mode 111
4.1.1.2 Operational mode 112
4.1.1.2.1 Normal mode 112
4.1.1.2.2 Downgraded mode 113
4.1.1.3 Maintenance mode 113
4.1.1.4 Simul mode and DSPIO Maintenance Mode 114
4.1.1.5 Test mode 116
4.1.1.6 Faulty mode 117
8 C264/EN UM/E50.5
4.1.1.7 Halt mode 117

4.1.1.8 Summary of modes, tests, transitions, and faults 117
4.1.1.9 Redundancy Mode management 118
4.1.2 Database management 121
4.1.2.1 General 121
4.1.2.2 How to upload a database through ethernet 123
4.1.2.3 How to switch the databases 123
4.1.2.4 How to do a check of the database 124
4.1.2.5 How to modify the database 124
4.1.2.6 How to modify a parameter setting in the current DB 124
4.1.2.7 How to consult a parameter setting in the current DB 124
4.1.3 Self-tests 125
4.1.4 Time management 125
4.1.4.1 External clock 126
4.1.4.2 Clock synchronization message from a SCADA gateway 127
4.1.4.3 SNTP Client and Servers 127
4.1.4.4 Time set by an operator 128
4.1.4.5 Local clock update 128
4.1.4.6 Management of loss of external time reference 129
4.1.4.7 Update method 129
4.1.4.8 Limits and performances 130
4.1.4.9 Precision Time Protocol 1588 130
4.1.4.9.1 Performance and limits 136
4.2 Communications 137
4.2.1 Telecontrol bus - TBUS 137
4.2.2 Legacy bus - LBUS 138
4.2.3 Station bus - SBUS 139
4.2.3.1 Exchanges 139
4.2.3.2 IEC 61850 compliances 140
4.2.3.3 Controls 140
4.2.4 Inter-rack Ethernet communication 140
4.2.4.1 Internal Ethernet architecture 141
4.2.4.2 External network behaviour 141
4.2.4.3 Ethernet failure 143
4.2.4.4 Other Ethernet rupture 144
4.2.4.5 Ethernet Routing table 144
4.2.5 Ethernet port management on CPU275 145
4.2.6 Telecontrol Bus redundancy 146
4.3 Direct process access 148
4.3.1 Input check 148
4.3.2 Output check 148
4.3.3 Time stamping 148
4.3.4 Digital input acquisition (DI) 148
4.3.4.1 DI acquisition 148
C264/EN UM/E50.5 9
4.3.4.2 DI Debouncing and filtering 149

4.3.5 Counter acquisition (CT) 149
4.3.5.1 Single counter (SCT) 150
4.3.5.2 Double counter (DCT) 150
4.3.6 Digital measurement (DM) 151
4.3.6.1 Acquisition without Read inhibit signal 151
4.3.6.2 Acquisition with Read inhibit signal 152
4.3.6.3 Encoding 153
4.3.7 Analogue Input acquisition (AI) 154
4.3.7.1 4.7.1 Input ranges 154
4.3.7.2 4.7.2 Acquisition cycle 154
4.3.8 Digital outputs (DO) 154
4.3.9 Digital Setpoints 154
4.3.9.2 Read Inhibit 155
4.3.10 Analog Setpoints 156
4.3.10.1 Output range 156
4.3.10.2 Output management 156
4.3.10.3 AOU Watchdog management 157
4.4 Data processing 158
4.4.1 Binary input processing 158
4.4.1.1 Binary input definition 158
4.4.1.2 Common processing of Binary Input 158
4.4.1.2.1 Toggling Input 158
4.4.1.2.2 Suppression 159
4.4.1.2.3 Substitution 159
4.4.1.2.4 Forcing 159
4.4.1.2.5 Transmission 159
4.4.1.3 Processing of Single Point Status 160
4.4.1.3.1 Persistence filtering 160
4.4.1.3.2 SPS resulting state 161
4.4.1.3.3 Mapping of SPS states on IEC 61850 station bus 162
4.4.1.3.4 DI/DO association for SPS 163
4.4.1.4 Processing of Double Point Status 163
4.4.1.4.1 Motion filtering 164
4.4.1.4.2 DPS persistence filtering 165
4.4.1.4.3 DPS resulting states 166
4.4.1.4.4 Mapping of DPS states on IEC 61850 station bus 167
4.4.1.4.5 DI/DO association for DPS 169
4.4.1.5 Processing of Multiple Point 169
4.4.1.5.1 Multiple Point filtering 169
4.4.1.5.2 MPS resulting state 170
4.4.1.5.3 Mapping of MPS states on IEC 61850 station bus 170
4.4.1.6 System Inputs (SI) 171
10 C264/EN UM/E50.5
4.4.1.7 IED binary inputs 171

4.4.1.8 Group processing 172
4.4.1.9 SBMC Mode Processing 173
4.4.1.10 BI sent to automation features 174
4.4.1.11 Toggling signal detection 174
4.4.1.12 Missing Signaling Voltage (MSV) 174
4.4.2 Measurement Input Processing 175
4.4.2.1 Analogue Measurement Processing 175
4.4.2.1.1 Open circuit management 175
4.4.2.1.2 Scaling 176
4.4.2.1.3 Zero value suppression 176
4.4.2.2 Digital Measurement Processing 177
4.4.2.3 TMU2XX: CT/VT measurement processing 177
4.4.2.3.1 TMU2XX: CT/VT Calculations - General 178
4.4.2.3.2 TMU220: CT/VT Calculations – Inputs Configuration 181
4.4.2.3.3 TMU220: CT /VT Calculations - Inputs: samples 181
4.4.2.3.4 TMU220: CT/VT Calculations – Outputs: set of measurements 182
4.4.2.3.5 TMU220: Measurements - General 183
4.4.2.3.6 TMU220: List of Measurements 183
4.4.2.3.7 TMU220: Algorithms 187
4.4.2.3.8 TMU210: CT/VT Calculations - Inputs: Configuration 190
4.4.2.3.9 TMU210: CT/VT Calculations - Inputs: Samples 190
4.4.2.3.10 TMU210: CT/VT Calculations – Outputs: Set of measurements 191
4.4.2.3.13 TMU210: Algorithms 194
4.4.2.3.14 Treshold detection 203
4.4.2.3.15 Manual suppression 204
4.4.2.3.17 Forcing an invalid measurement 204
4.4.2.3.18 Measurement resulting states 205
4.4.2.3.19.1 Periodic transmission 206
4.4.2.3.19.2 Transmission upon variation 206
4.4.2.3.19.3 Transmission upon trigger 206
4.4.2.3.19.4 Limits and performances 206
4.4.3 Tap Position Indication (TPI) measurement processing 207
4.4.3.1 Acquisition from Digital Inputs 207
4.4.3.2 Acquisition from Analogue Inputs 207
4.4.3.3 Manual suppression 208
4.4.3.4 Substitution 208
4.4.3.5 Forcing an invalid TPI 208
4.4.3.6 Transmission 209
C264/EN UM/E50.5 11
4.4.4 Accumulator Input Processing 209

4.4.5 Energy counting 209
4.4.6 Basic data manipulation 210
4.4.6.1 Simul mode enhancements 210
4.4.6.2 Controls management from PSL 211
4.5 Control sequences 213
4.5.1 Description 213
4.5.1.1 General 213
4.5.1.1.1 Device control configuration 213
4.5.1.1.2 Types of devices 214
4.5.1.2 Control sequence phase management 214
4.5.1.3 Direct Execute mode 217
4.5.1.4 SBO once mode 219
4.5.1.4.1 Selection phase in "SBO once" mode 219
4.5.1.4.2 Execution phase in "SBO once" mode 221
4.5.1.5 SBO many mode 222
4.5.1.5.1 Selection phase in SBO many mode 222
4.5.1.5.2 Execution phase in SBO many mode 223
4.5.1.5.3 Unselection phase in SBO many mode 224
4.5.1.6 Generic selection checks 225
4.5.1.6.1 Inter-control delay 227
4.5.1.6.2 Computer mode 227
4.5.1.6.3 Substation and bay mode control 227
4.5.1.6.4 Interlock control 227
4.5.1.6.5 Automation running control 227
4.5.1.6.6 Device selectable 228
4.5.1.6.7 Locked device control 228
4.5.1.6.8 Current status of the device 228
4.5.1.6.9 Uniqueness 228
4.5.1.7 Selection behavior 229
4.5.1.8 Generic execution checks 230
4.5.1.9 Execution behavior 230
4.5.1.9.1 Execution via I/O boards 231
4.5.1.9.2 Execution via IED communication 231
4.5.1.9.3 System controls execution 231
4.5.1.10 Controls time sequencing 231
4.5.1.10.1 Direct execute time sequencing 232
4.5.1.10.2 SBO once time sequencing 232
4.5.1.10.3 SBO many time sequencing 234
4.5.1.11 Bay/Module/xPC order running 234
4.5.1.12 Controlling xPC by xPS change of state 235
4.5.2 Control of non synchronized breakers 237
4.5.2.1 Non synchronized circuit breaker features 237
4.5.2.2 Control sequence of non synchronized circuit breakers 238
12 C264/EN UM/E50.5
4.5.3 Control of synchronized breakers 238

4.5.3.1 Synchronized circuit breaker features 238
4.5.3.2 Circuit breakers with external synchrocheck 240
4.5.3.2.1 Close CB by external synchrocheck with automatic set on 240
4.5.3.2.2 Close CB by external synchrocheck with manual set on 244
4.5.3.2.3 Close synchronized circuit breakers with forcing 247
4.5.3.2.4 Cancel Close CB with external synchrocheck 248
4.5.3.3 Circuit breakers with internal synchrocheck 249
4.5.3.3.1 Close CB with internal synchrocheck with automatic set on 250
4.5.3.3.2 Close CB with internal synchrocheck with manual set on 255
4.5.3.3.3 Close CB with internal synchrocheck with forcing 256
4.5.4 Control of disconnectors 258
4.5.4.1 Disconnectors features 258
4.5.4.2 Control sequence of disconnectors 258
4.5.5 Control of transformers 258
4.5.5.1 Transformer features 258
4.5.5.2 Control sequence of transformers 259
4.5.5.2.1 Control of transformer with TCIP 259
4.5.5.2.2 Control of transformer without TCIP 261
4.5.5.2.3 Suppression, Forcing or Substitution of the TPI 262
4.5.6 Control of Intelligent Electrical Devices (IED) 262
4.5.6.2.1 Selection phase 263
4.5.6.2.2 Execution phase 263
4.5.7 System controls 263
4.5.8 Kinds of control sequences 264
4.5.9 Control sequences checks 264
4.5.9.1 Mode Management 264
4.5.9.2 IED connected 265
4.5.9.3 Control mode 265
4.5.9.4 Uniqueness of control 265
4.5.9.5 Inter-control delay 265
4.5.9.6 Status of the device 265
4.5.9.7 Locked device 265
4.5.9.8 Running Automation 265
4.5.9.9 Interlocking 266
4.5.10 HV Control Sequences 266
4.5.10.1 Circuit breaker 266
4.5.10.2 Disconnector 266
4.5.10.3 Transformer 266
4.6 Automation 267
4.6.1 Safety information 267
C264/EN UM/E50.5 13
4.6.2 Built-in Automation functions 267

4.6.2.1 Auto-Recloser (AR) 267
4.6.2.2 Introduction 267
4.6.2.2.1 Behavior 268
4.6.2.2.1.1 In Service / Out of service 269
4.6.2.2.1.2 Analysis of the receiving trip 269
4.6.2.2.1.3 Waiting CB opening 270
4.6.2.2.1.4 Launch cycle timer 270
4.6.2.2.1.5 Closing the CB 271
4.6.2.2.1.6 Launch recovering time 271
4.6.2.2.1.7 Particular treatments 271
4.6.2.2.2 Information and parameters 272
4.6.2.3 Trip Circuit Supervision 274
4.6.2.4 Circuit breaker condition monitoring (I²t) 276
4.6.2.4.1 Acquisition and computation 276
4.6.2.4.2 Reset 277
4.6.2.4.3 Monitoring 277
4.6.2.4.4 Inhibition 277
4.6.2.4.5 Storage 277
4.6.2.5 Automatic Voltage Regulation–AVR 278
4.6.2.5.1 Presentation 278
4.6.2.5.1.1 Role 278
4.6.2.5.1.2 Topologies 278
4.6.2.5.1.3 Modes 278
4.6.2.5.1.4 Interfaces for a single transformer 279
4.6.2.5.1.5 Hardware architecture 279
4.6.2.5.1.6 Exchanges over the bus 280
4.6.2.5.2 Moving a tap changer 280
4.6.2.5.2.1 Actual voltage 280
4.6.2.5.2.2 Target voltage 281
4.6.2.5.2.3 Regulation 282
4.6.2.5.3 Additional monitoring functions 283
4.6.2.5.3.1 Tap Changer position on Voltage Loss 283
4.6.2.5.3.2 Fast Tap Changer move AFTER Voltage Loss and Voltage
recovery 283
4.6.2.5.3.3 Abnormal Voltage signalization 284
4.6.2.5.3.4 Tap Changer Failure supervision – Tap Blocking 284
4.6.2.5.3.5 Tap Changer Lowest / Highest position 285
4.6.2.5.3.6 Run away protection 285
4.6.2.5.3.7 OverVoltage Detection 285
4.6.2.5.3.8 UnderVoltage Detection 286
4.6.2.5.3.9 OverCurrent detection 286
4.6.2.5.3.10 Tap Changer Maintenance: Tap Counting 286
4.6.2.5.4 Line drop compensation 287
14 C264/EN UM/E50.5
4.6.2.5.5 Other functions 288

4.6.2.5.5.1 Additional Measurements (Optional) 288
4.6.2.5.5.2 Raise lower control and voltage target from external signals 288
4.6.2.5.5.3 Reverse Power Flow (RPF) 289
4.6.2.5.6 Transformers in parallel 291
4.6.2.5.6.1 Master Followers method 291
4.6.2.5.6.2 Standalone regulation 292
4.6.2.6 Automatic voltage regulation–ATCC 294
4.6.2.6.1.1 Topologies 294
4.6.2.6.1.2 Situations requiring ATCC 295
4.6.2.6.1.3 Definitions and main attributes 295
4.6.2.6.1.4 Capacity 296
4.6.2.6.1.5 Alarm conditions 296
4.6.2.6.2 Monitoring logic 297
4.6.2.6.2.1 Modes 297
4.6.2.6.2.2 Conditions for an active automatic voltage regulation 297
4.6.2.6.2.3 Transformers status logic 298
4.6.2.6.2.4 Busbars status logic 298
4.6.2.6.2.5 Group status logic 298
4.6.2.6.3 Moving tap changers 299
4.6.2.6.3.2 Voltage is outside of the Target Voltage Deadband 300
4.6.2.6.3.3 Timeouts 301
4.6.2.6.3.4 Homing 303
4.6.2.6.4 Calculation modes for a busbars group 304
4.6.2.7 Synchrocheck 308
4.6.2.7.1 Synchrocheck – General 308
4.6.2.7.2 Synchrocheck Schemes 309
4.6.2.7.3 Synchrocheck Algorithm 310
4.6.2.7.4 Synchrocheck Applications 310
4.6.2.7.5 Synchrocheck Circuit Breaker Closure types 310
4.6.2.7.6 Synchrocheck Type 1 and Type 2 311
4.6.2.7.7 Synchrocheck Hardware constraints and use 311
4.6.2.7.8 Synchrocheck Calculation 311
4.6.2.7.9 Synchrocheck Introduction to Harmonics 311
4.6.2.7.10 Synchrocheck – Check Synchronizing – Locking Mode 312
4.6.2.7.11 Synchrocheck – System Synchronizing – Coupling Mode 312
4.6.2.7.12 Synchrocheck Scheme LL: Live Line, Live Bus: Real Time Sequences312
4.6.2.7.12.1 Locking allowed / coupling not allowed by configuration 312
4.6.2.7.12.2 Locking allowed / coupling allowed by configuration 313
4.6.2.7.13 Synchrocheck Schema with VLINE and NOT(VBUSBAR) voltage
controls 315
C264/EN UM/E50.5 15
4.6.2.7.14 Synchrocheck Schema with NOT(VLINE) and VBUSBAR voltage

controls 315
4.6.2.7.15 Synchrocheck Schema with NOT(VLINE) and NOT(VBUSBAR)
voltage control 315
4.6.2.7.16 Synchrocheck Schemes that use VLINE and VBUSBAR voltage
control 315
4.6.2.7.16.1 Locking scheme ( synchronous mode ) 315
4.6.2.7.16.2 Coupling scheme ( asynchronous mode ) 316
4.6.2.7.17 Synchrocheck Type 1 - Logic of Interlock Authorization 317
4.6.2.7.19 Synchrocheck Bypass 318
4.6.2.7.20 Synchrocheck Bypass - Purpose 318
4.6.2.7.21 Synchrocheck Bypass - Functional Description 318
4.6.2.7.22 Phase-to-Phase Synchrocheck with the TMU210 319
4.6.2.7.23 Phase-to-Phase Synchrocheck with the TMU210 - General 319
4.6.2.7.24 Phase-to-Phase Synchrocheck with the TMU210 - Description 321
4.6.2.7.25 Phase-to-Phase Synchrocheck with the TMU210 - Configuration 321
4.6.2.7.26 Synchrocheck Close request 321
4.6.2.7.27 Synchrocheck General Configuration 322
4.6.2.7.28 Synchrocheck Voltage control 322
4.6.2.7.29 Synchrocheck Schemes control 323
4.6.2.7.30 Synchrocheck Parameters of the TMU2xx board 323
4.6.2.7.31 Synchrocheck Internal parameters 323
4.6.2.7.32 Synchrocheck Digital Output (DO) of the circuit breaker 325
4.6.2.7.33 Voltage reference selection and Double busbar configuration 326
4.6.2.8 Fast Load Shedding ( FLS ) 326
4.6.2.9 Synchroscope and Power Synchronizer 326
4.6.2.9.1 General 326
4.6.2.9.1.1 Monitoring 327
4.6.2.9.1.2 Convergence 327
4.6.2.9.1.3 Closing 328
4.6.2.9.1.4 Connection schema 330
4.6.2.9.2 HMI 330
4.6.2.9.2.1 MiCOM C264’s Screens 330
4.6.2.9.2.2 Navigation in MiCOM C264 332
4.6.2.9.3 Main MiCOM C264’s behavior 333
4.6.2.9.4 Error management in MiCOM C264 334
4.6.2.9.5 Performances 334
4.6.2.10 MiCOM C264 in eLSU application 334
4.6.2.10.1 Purpose 334
4.6.2.10.2 MiCOM C264 eLSU configuration 335
4.6.2.10.2.1 Shed Reflex 335
4.6.2.10.3 Shed automation 336
4.6.2.10.3.1 Control Type of Shed Automation 337
16 C264/EN UM/E50.5
4.6.2.10.3.2 MiCOM C264 specific configuration for MiCOM C264 eLSU 339
4.6.3 Fast automation: Programmable Scheme Logic (PSL) 340
4.6.3.1 Interlocking equations as particular case of PSL 340
4.6.3.1.1 Introduction 340
4.6.3.1.2 Interlocking bypass 340
4.6.3.1.3 Timer before interlock evaluation 341
4.6.3.1.4 Simulation and test of interlocking equations 341
4.6.3.2 PSL/interlocking inputs 341
4.6.3.3 PSL interlocking outputs 341
4.6.3.4 Functions 341
4.6.3.5 Validity of data 342
4.6.3.6 Computation 342
4.6.4 Slow automation Programmable Logic Control (PLC) 342
4.6.4.1 Inputs 343
4.6.4.2 Outputs 343
4.6.4.3 PLC Behaviour 344
4.6.5 PSL/PLC behavior in case of MiCOM C264 redundancy 345
4.7 Records 346
4.7.1 Permanent records storage 346
4.7.1.1 Data storage 346
4.7.1.2 Waveform Recording: General 346
4.7.1.3 Events 346
4.7.1.4 Fast Waveform Recording 346
4.7.1.5 Slow Waveform Recording 347
4.7.1.6 Slow Waveform Recording – Hypothesis 348
4.7.1.7 Disturbance Recorder 349
4.7.2 Non-permanent data storage of alarm 350
4.7.2.1 Definitions 350
4.7.2.1.1 Definition of an alarm 350
4.7.2.1.2 Types of alarmed data 350
4.7.2.1.3 Alarm states definition 351
4.7.2.1.4 Parameters associated to an alarm 351
4.7.2.2 Alarm processing 352
4.7.2.2.1 Acknowledgment 354
4.7.2.2.2 Clearing 355
4.8 Protection Functions 356
4.8.1 Undervoltage (ANSI code 27) 356
4.8.1.1 Description of the protection 356
4.8.1.2 Characteristics of the protection 356
4.8.2 Earth Wattmetric Protection (ANSI code 32N) 357
4.8.3 Undercurrent protection (ANSI code 37) 358
C264/EN UM/E50.5 17

4.8.4 Negative sequence OC protection (ANSI code 46) 359
4.8.5 Thermal overload protection (ANSI code 49) 360
4.8.6 Overvoltage (ANSI code 59) 361
4.8.7 Residual overvoltage / neutral displacement (ANSI code 59N) 362
4.8.8 Directional / Non-directional phase OC protection (ANSI code 67/50/51) 363
4.8.9 Dir. / Non-dir. Neutral / Ground / Earth OC protection (ANSI code 67N/50N/51N)365
4.8.10 Overfrequency (ANSI codes 81O) 367
4.8.11 Rate of change of frequency (ANSI code 81R) 368
4.8.12 Underfrequency (ANSI codes 81U) 369
4.8.13 VT supervision (ANSI code 60FL) 369
4.8.14 Inrush current blocking (ANSI code H2) 371
4.8.15 Extra functions 372
4.8.15.1 Circuit breaker failure (50BF or TCS) 372
4.8.15.1.1 Description of the protection 372
4.8.15.1.2 Characteristics of the protection 372
4.8.15.2 Cold load start 372
4.8.15.2.1 Description of the function 372
4.8.15.2.2 Characteristics of the function 372
4.8.15.3 RSE 373
4.8.15.4 Trip management 373
4.9 Protection Curves 374
18 C264/EN UM/E50.5
4.9.1 IDMT Curves 374

4.9.1.1 Mathematical formula 374
4.9.1.1.1 IDMT threshold 374
4.9.1.1.2 Reset timer 375
4.9.1.2 IEC Curves 378
4.9.1.3 RI Curves 384
4.9.1.4 IEEE/ANSI & CO Curves 385
4.9.2 Thermal overload curves 391
4.9.2.2 10.2.2 Tripping curve 392
5 Hardware 393
5.1 Hardware conformity 397
5.2 Range description 398
5.2.1 Rack styles 399
5.2.1.1 mechanical specification 399
5.2.1.2 Rack 40TE mechanical details 400
5.2.1.2.1 Drawings 400
5.2.1.2.1.1 Without CT/VT 400
5.2.1.2.1.2 With CT/VT 400
5.2.1.2.2 Rear panel 401
5.2.1.2.2.1 Without CT/VT 401
5.2.1.2.2.2 With CT/VT 401
5.2.1.2.3 Fastening holes 402
5.2.1.3.1 Drawings 402
5.2.1.3.1.1 Without CT/VT 402
5.2.1.3.1.2 With CT/VT 403
5.2.1.3.2 Rear panel 403
5.2.1.3.2.1 Without CT/VT 403
5.2.1.3.2.2 With CT/VT 404
5.2.1.4.1 Drawings 405
5.2.1.4.1.1 Without CT/VT 405
5.2.1.4.1.2 With CT/VT 406
5.2.1.4.2 Rear panel 406
5.2.1.4.2.1 Without CT/VT 406
5.2.1.4.2.2 With CT/VT 406
5.2.2 Front panels 407
5.2.3 Basic functions/components 408
5.2.4 Product configuration 409
5.2.4.1 40TE slot configuration 410
C264/EN UM/E50.5 19

5.2.5 Environment conditions 412
5.2.6 Power supply 413
5.2.7 Consumption 413
5.2.8 Reliability 414
5.2.9 environmental characteristics 414
5.3 Connection of the protective conductor (Earth) 418
5.3.1 Earthing 418
5.3.2 Cable fitting 419
5.4 Electronic hardware description 421
5.4.1 Board addressing 422
5.4.2 Coating 422
5.4.3 Input/Output connector block 422
5.4.4 CT/VT connector block (MiDOS) 422
5.4.5 BIU241 board – Power supply 423
5.4.5.1 Description 423
5.4.5.2 Port 1 jumper configuration 424
5.4.5.4 Technical characteristics 427
5.4.5.5 Rear panel connector 428
5.4.5.6 Redundancy wiring 430
5.4.6 BIU261 board – dual source power supply 431
5.4.6.1 description 431
5.4.6.2 Jumper configuration 432
5.4.7 CPU275 board - Central Processing Unit and base communications board 436
5.4.7.2 Configuration / options 436
5.4.7.5 Accessories 438
5.4.7.5.1 ECU200 – RS 232 to Optical converter 438
5.4.7.5.2 ECU201 – RS 232 to RS 485 / RS 422 converter 440
5.4.8 DIU200 board - Digital Input Unit 441
20 C264/EN UM/E50.5
5.4.10 CCU200 board - Circuit breaker Control Unit 449

5.4.11 CCU211 board – Circuit breaker Control Unit (multi-voltages) 453
5.4.12 DOU201 board - Digital Output Unit 458
5.4.13 AIU211 board - DC Analog Input Unit 460
5.4.14 AOU200 board – Analog Output Unit 462
5.4.15 - AC Analog Input Unit + DSPIO 466
5.4.15.3 technical characteristics 466
5.4.16 DSP211 board 469
5.4.17 TMU220 board - AC Analog Input Unit 472
5.4.18 DSP200 board 477
C264/EN UM/E50.5 21

5.4.19 SBU200 board – Smart terminal Block Unit 477
5.4.19.4 Rear panel connectors 479
5.4.20 SBU400 board – optical Smart terminal Block Unit 479
5.4.21 SWU20x board - Ethernet-based SWitch Unit 481
5.4.22 SWR212 board - Ethernet-based SWitch Redundant Unit 485
5.4.22.4 Optical fiber budget calculations 488
5.4.22.6 Wiring between two SWR212 489
5.4.23 SWS212 board - Ethernet-based SWitch RSTP compatible 490
5.4.24 REU20X board – Redundant Ethernet-Unit – PRP/HSR/RSTP 493
5.5 Terminal technical data 497
5.5.1 PC Maintenance Interface 497
5.5.2 Ethernet LAN (installed on the CPU275 board) 497
5.5.3 IRIG-B interface (standard NF S 87-500, May 1987), installed on the CPU275
board 497
5.5.4 Conventional communication links 497
5.5.5 Input /Output or power supply modules 497
5.5.6 Current-measuring and Voltage-measuring inputs 497
6 Human Machine Interface 498
6.1 The Front Panel 500
6.1.1 Overview 500
22 C264/EN UM/E50.5
6.1.2 LED’s management 501

6.1.2.1 First LEDs 501
6.1.2.2 Other LEDs 502
6.1.2.3 Example: AVR dedicated MiCOM C264 503
6.1.3 Configuration data 504
6.1.3.1 General display management 505
6.1.3.2 Language support 508
6.1.3.3 Time and date displaying 508
6.1.3.3.1 Time 508
6.1.3.3.2 Date 508
6.1.3.3.3 State of date and time 508
6.1.3.4 Bay panels 509
6.1.3.4.1 Case 1: display for specific CT/VT measurement 510
6.1.3.4.2 Case 2: other measurements 511
6.1.3.4.3 State sub-panel 512
6.1.3.4.4 Measurements, counters and TPI sub-panel 513
6.1.3.4.4.1 Display of measurements 514
6.1.3.4.4.2 Display of counters 514
6.1.3.4.4.3 Display of TPI 514
6.1.3.4.5 Control sub-panel 515
6.1.3.4.6 Interlocking sub-panel 517
6.1.3.5 AVR Panel 518
6.1.3.6 Generic Measurements Panel 520
6.1.3.6.1 Navigation 520
6.1.3.6.2 Main Page 521
6.1.3.6.3 Measurements display 522
6.1.3.6.4 Bargraph MV selection 523
6.1.3.6.5 Secondary pages 524
6.1.3.6.6 Empty pages 524
6.1.3.6.7 Selection persistence 525
6.1.3.6.8 Automatic return to the default panel 525
6.1.3.7 Events panel 525
6.1.3.7.1 Display mechanism for the first page 526
6.1.3.7.2 Display mechanism for an intermediate page: 526
6.1.3.7.3 Display mechanism for the last page: 526
6.1.3.8 Faults panel 527
6.1.3.9 Alarm panel 527
6.1.3.10 Disturbance record panel 529
6.1.3.11 Configuration panel 530
6.1.3.11.1 Boards panel 531
6.1.3.11.2 External devices panel 532
6.1.3.11.3 Service information panel 534
6.1.3.12 Display of binary input information 535
6.1.3.13 Display of binary output information 536
C264/EN UM/E50.5 23
6.1.3.14 Menu tree 538

6.1.3.14.1 menu tree in operational or simulation mode (example) 539
6.1.3.14.2 menu tree in maintenance mode 540
6.1.3.15 Controls (subject to privilege) 540
6.1.3.15.1 Local / Remote control of bay 541
6.1.3.15.2 Commands of circuit breakers, disconnecting switches and generic
devices 541
6.1.3.15.2.1 SBO command 541
6.1.3.15.2.2 DE command 542
6.1.3.15.2.3 Interlocking bypass 542
6.1.3.15.2.4 Synchrocheck bypass 542
6.1.3.15.2.5 Interface with the operator on local control panel 543
6.1.3.15.3 Tap changer control request 543
6.1.3.15.5 Data base switch 544
6.1.3.15.6 Reset operating hours 545
6.1.3.15.7 Time and date setting 545
6.1.3.15.8 Manual value change of counters 545
6.1.3.15.9 Acknowledgement of alarms 545
6.1.3.15.9.1 Global acknowledge 546
6.1.3.15.9.2 Alarm per alarm acknowledge 546
6.1.3.15.10 Alarms clearing 546
6.1.3.15.10.1 Global clear 546
6.1.3.15.10.2 Alarm per alarm clear 547
6.1.3.15.11 Activate test mode 547
6.1.3.16 Password management 547
6.2 The Computer Administration Tool (CAT) 550
6.3 Printers 551
6.3.1 Inputs 551
6.3.2 Outputs 551
6.3.3 Printer management 551
6.3.3.1 Header & footer 551
6.3.3.2 Chronology & time stamp 552
6.3.3.3 Printer out of service 552
6.3.3.4 Circular FIFO management 552
7 Application 555
7.1 BCPU configuration scope 565
7.1.1 General EPAS system configuration 565
7.1.2 MiCOM C264 configuration in general EPAS system configuration 565
7.2 Defining BCPU configuration in system architecture 567
7.2.1 Setting general system configuration relevant to MiCOM C264 567
7.2.2 Adding a MiCOM C264 in the system architecture 569
7.2.3 Setting general attributes of MiCOM C264 571
7.2.3.1 Configuring binary input (BI) filtering 572
24 C264/EN UM/E50.5
7.2.3.2 Configuring measurement acquisition and transmission 573

7.2.3.3 Configuring counter acquisition 573
7.2.3.4 Configuring internal fault characteristics 573
7.2.3.5 Locating computer in a substation (mandatory) 574
7.2.3.6 Configuration of SNTP Server 574
7.2.3.7 Defining a redundant computer (optional) 575
7.2.4 Adding BCPU hardware components 577
7.2.4.1 Adding boards 577
7.2.4.2 Setting specific attributes to BCPU boards 578
7.2.4.2.1 Setting common attributes to computer board 578
7.2.4.2.2 Setting specific features of the GHU2xx board 579
7.2.4.2.3 Setting attributes of a TMU220 board 580
7.2.4.2.4 Setting specific features of BIU2x1 board 581
7.2.4.2.5 Setting specific features of a TMU210 board 582
7.2.4.3 Configuring a communication channel 586
7.2.4.4 Configuring an AI channel 588
7.2.4.5 Adding a printer 590
7.2.4.6 Configuring an AO channel 592
7.2.5 MiCOM C264 IP address and routing table definition 594
7.2.5.1 MiCOM C264 as a gateway connected to a router and a remote IEC 60870-
5-104 SCADA 595
7.2.5.1.1 MiCOM C264 Routing table parameters 595
7.2.5.1.2 IEC 60870-5-104 protocol configuration 596
7.2.5.1.3 MiCOM C264 IP address definition 596
7.2.5.1.4 MiCOM C264 IP Parameters 597
7.2.5.1.5 Router-PC configuration (case of PC under Microsoft-windows) 597
7.2.5.1.6 Particular case of DHCP network 598
7.2.5.2 MiCOM C264 as a gateway directly connected to a remote DNP3 SCADA 598
7.2.5.3 MiCOM C264 as a gateway connect maximum of 4 DNP-IP SCADA
Protocols 599
7.2.6 Networking BCPU on a Station Bus network 600
7.2.6.1 Adding an IEC 61850 Station Bus Process Bus in the system architecture 600
7.2.6.2 Connecting a BCPU to an IEC 61850 Station Bus network 600
7.2.6.3 Connecting a BCPU to others station bus devices 601
7.2.7 Networking IED on computer legacy network 602
7.2.7.1 Creating a legacy network of IED 602
7.2.7.1.1 Adding a legacy network 602
7.2.7.1.2 Setting general attributes of a legacy network 603
7.2.7.1.2.1 Serial Port communication 603
7.2.7.1.2.2 Ethernet/IP communication 603
7.2.7.1.3 Setting acquisitions attributes of a IEC 60870-5-103 legacy network 604
7.2.7.2 Setting acquisition attributes of a IEC 60870-5-101 legacy network 604
7.2.7.2.1 Setting acquisition attributes of a Modbus legacy network 606
7.2.7.2.2 Setting acquisition attributes of a DNP3 legacy network 607
C264/EN UM/E50.5 25
7.2.7.2.3 Adding an IED to a legacy network 607

7.2.7.2.4 Setting attributes of a legacy IED 609
7.2.7.2.4.1 Specific attributes for legacy DNP3 over IP IEDs 610
7.2.7.2.4.2 Specific attributes for legacy T104 IEDs 611
7.2.7.2.5 Adding an IED acquisition type to a legacy network 611
7.2.7.2.6 Setting attributes of a IEC 60870-5-103 acquisition type 612
7.2.7.2.7 Setting attributes of a MODBUS acquisition type 613
7.2.7.2.8 Setting attributes of a DNP3 acquisition type 614
7.2.7.2.9 Adding Serial Tunneling 614
7.2.7.2.10 Setting acquisition attributes of a IEC 60870-5-104 legacy network 615
7.2.7.3 Defining addressing mapping of a legacy IED 617
7.2.7.3.1 Defining an IED address for an SPS datapoint 618
7.2.7.3.2 Defining an IED address for a DPS datapoint 621
7.2.7.3.3 Defining an IED address for an MV datapoint 623
7.2.7.3.4 Defining an IED address for a Counter datapoint 626
7.2.7.3.5 Defining an IED address for an SPC datapoint 628
7.2.7.3.6 Defining an IED address for a DPC datapoint 630
7.2.7.3.7 Defining an IED address for a SetPoint datapoint 633
7.2.8 Networking SCADA on computer SCADA network 637
7.2.8.1 Creating a SCADA network 637
7.2.8.1.1 Adding a SCADA network 637
7.2.8.1.2 Setting general attributes of a SCADA network 638
7.2.8.1.3 Setting general attributes of a IEC 60870-5-101 SCADA network 639
7.2.8.1.4 Setting specific attributes of a IEC 60870-5-101 SCADA network 639
7.2.8.1.5 Setting general attributes of a DNP3 SCADA network 641
7.2.8.1.5.1 How to Set the General Attributes of a DNP3-IP SCADA Network 641
7.2.8.1.7 Setting specific attributes of a MODBUS SCADA network 646
7.2.8.2 Defining addressing mapping of SCADA network 646
7.2.8.2.1 Defining a SCADA address for an SPS datapoint 647
7.2.8.2.2 Defining a SCADA address for a DPS datapoint 649
7.2.8.2.3 Defining a SCADA address for a MV datapoint 652
7.2.8.2.4 Defining a SCADA address for a Counter datapoint 653
7.2.8.2.5 Defining a SCADA address for a SPC datapoint 655
7.2.8.2.6 Defining a SCADA address for a DPC datapoint 657
7.2.8.2.7 Defining a SCADA address for a SetPoint datapoint 659
7.2.8.2.8 Defining a SCADA address for bypass synchrocheck 661
7.2.8.3 How to configure a mapping of a SCADA network 662
7.2.8.4 Addressing datapoint on SCADA legacy network 664
7.2.9 Defining a time synchronization for an EPAS network 665
7.2.9.1 Setting a SNTP time synchronization 665
7.2.9.2 Setting an IEC 61588 time synchronization 666
7.2.10 Defining wave record file management 667
7.2.10.1 Defining management of disturbance file for IED 667
26 C264/EN UM/E50.5
7.2.10.2 Defining IEC 60870-5-103 IED extra information for disturbance file 667
7.2.10.2.1 Adding an analog channel definition 667
7.2.10.2.2 Adding a digital channel definition 669
7.2.10.3 Defining management of wave record file for computer CT/VT board 669
7.2.10.3.1 Defining fast waveform recording 670
7.2.10.3.2 Defining slow waveform recording 673
7.2.11 Defining a computer klaxon 678
7.2.12 Setting system information for computer components 678
7.2.12.1 Setting general system information of a computer 679
7.2.12.2 Setting system information of board 684
7.2.12.3 Setting system information of legacy IED 685
7.2.12.4 Setting system information of serial printer 686
7.2.12.5 Setting system information of a SCADA network 687
7.3 Defining datapoint 689
7.3.1 Creating a datapoint 689
7.3.1.1 Defining SPS datapoint 690
7.3.1.2 Defining DPC datapoint 691
7.3.1.3 Defining MPS datapoint 692
7.3.1.4 Defining MV datapoint 693
7.3.1.5 Defining TPI datapoint 696
7.3.1.6 Defining counter datapoint 698
7.3.1.7 Overview of control sequence processing 699
7.3.1.8 Defining SPC datapoint 700
7.3.1.8.1 Defining an SPC feedback 701
7.3.1.9.1 Defining a DPC feedback 703
7.3.1.10 Overview of SetPoint processing 705
7.3.1.11 Defining SetPoint datapoint 706
7.3.1.11.1 Defining SetPoint feedback 708
7.3.2 Linking a datapoint to a profile 708
7.3.2.1 Defining an SPS profile 709
7.3.2.1.1 Setting 'General attributes' of an SPS profile 709
7.3.2.1.2 Setting 'State labels' attributes of an SPS profile 710
7.3.2.1.3 Setting 'State treatment' attributes of an SPS profile 710
7.3.2.1.4 Setting 'Alarms' attributes of an SPS profile 711
7.3.2.1.5 Setting 'Interlocking' attributes of an SPS profile 712
7.3.2.2 Defining a DPS profile 712
7.3.2.2.1 Setting 'General' attributes of a DPS profile 712
7.3.2.2.2 Setting 'State labels' attributes of a DPS profile 713
7.3.2.2.3 Setting 'State treatment' attributes of a DPS profile 713
7.3.2.2.4 Setting 'Alarms' attributes of a DPS profile 714
7.3.2.2.5 Setting 'Interlocking' attributes of a DPS profile 715
7.3.2.3 Defining an MPS profile 716
7.3.2.4 Setting 'General' attributes of an MPS profile 716
C264/EN UM/E50.5 27
7.3.2.4.1 Setting 'State labels' attributes of an MPS profile 717

7.3.2.4.2 Setting 'State treatments' attributes of an MPS profile 717
7.3.2.4.3 Setting 'Alarms' attributes of an MPS profile 717
7.3.2.4.4 Setting 'Interlocking' attributes of an MPS profile 718
7.3.2.5 Defining an MV profile 719
7.3.2.5.1 Setting 'General' attributes of an MV profile 719
7.3.2.5.2 Setting 'State labels' attributes of an MV profile 720
7.3.2.5.3 Setting 'State treatments' attributes of an MV profile 720
7.3.2.5.4 Setting 'Alarms' attributes of an MV profile 721
7.3.2.5.5 Setting 'Interlocking' attributes of an MV profile 722
7.3.2.6 Defining a counter profile 722
7.3.2.6.1 Setting 'General' attributes of a counter profile 722
7.3.2.6.2 Setting 'State labels' attributes of a counter profile 722
7.3.2.6.3 Setting 'State treatments' attributes of a counter profile 723
7.3.2.6.4 Setting 'Alarms' attributes of a counter profile 723
7.3.2.6.5 Setting 'Mean value' attributes of a counter profile 724
7.3.2.7 Defining an SPC profile 724
7.3.2.7.1 Setting 'General attributes' of an SPC profile 725
7.3.2.7.2 Setting 'Order labels' attributes of an SPC profile 725
7.3.2.7.3 Setting 'State treatments' attributes of an SPC profile 726
7.3.2.7.4 Setting 'Alarms' attributes of an SPC profile 726
7.3.2.7.5 Setting 'Interlocking and FBD' attributes of an SPC profile 727
7.3.2.8 Defining a DPC profile 727
7.3.2.8.1 Setting 'General' attributes of a DPC profile 728
7.3.2.8.2 Setting 'Order labels' attributes of a DPC profile 728
7.3.2.8.3 Setting 'State treatments' attributes of a DPC profile 729
7.3.2.8.4 Setting 'Alarms' attributes of a DPC profile 729
7.3.2.8.5 Setting 'Interlocking and FBD' attributes of a DPC profile 730
7.3.2.9 Defining a Setpoint profile 731
7.3.2.9.1 Setting 'General' attributes of setpoint profile 731
7.3.2.9.2 Setting 'Treatments on event' attributes of setpoint profile 732
7.3.2.9.3 Setting 'Alarms' attributes of setpoint profile 732
7.3.3 Defining computer local archiving of datapoint events 733
7.3.4 Defining computer local archiving of datapoint alarms 733
7.3.5 Defining computer local logging of datapoint events and alarms 733
7.3.6 Defining acquisition source for inputs datapoints 734
7.3.6.1 Acquiring input datapoint via input channels 734
7.3.6.1.1 Wiring an SPS datapoint via one DI channel 734
7.3.6.1.2 Wiring a DPS datapoint via two DI channels 735
7.3.6.1.3 Wiring a MPS datapoint via N DI channels 736
7.3.6.1.4 Wiring MV and TPI datapoint via N DI channels 736
7.3.6.1.5 Wiring a Counter datapoint 737
7.3.6.2 Acquiring input datapoint via an IED legacy network 738
7.3.6.3 Acquiring input datapoint via non-EPAS IEC 61850 communicant IED 739
28 C264/EN UM/E50.5
7.3.6.4 Producing input datapoint 740

7.3.6.4.1 Implicit production of system input datapoint via system decomposition 740
7.3.6.4.2 Implicit production of electrical input datapoint via built-in function 740
7.3.6.4.3 Explicit production of electrical input datapoint via user function 740
7.3.6.4.4 Explicit electrical input datapoint via CT/VT computation 741
7.3.7 Defining control source for output datapoints 742
7.3.7.1 Controlling output datapoint via output channels 742
7.3.7.1.1 Wiring a SPC datapoint via one DO channel 742
7.3.7.1.2 Wiring DPC datapoint via two or four DO channels 742
7.3.7.1.3 Wiring SetPoint datapoint 743
7.3.7.1.4 Wiring from CCU datapoint 744
7.3.7.2 Controlling output datapoint via an IED legacy network 744
7.3.7.3 Controlling output datapoint via non-EPAS IEC 61850 communicant IED 745
7.3.7.4 Producing output datapoint 746
7.3.7.4.1 Implicit production of system output datapoint via system
decomposition 746
7.3.7.4.2 Implicit production of electrical output datapoint via built-in function 746
7.3.7.4.3 Explicit production of output datapoint via user function 746
7.3.7.5 Acknowledgment definition in case of simultaneous
ordersAcknowledgment definition in case of simultaneous orders 747
7.3.8 Defining datapoint association 747
7.3.8.1 Adding a target datapoint 748
7.3.8.2 Linking the target datapoint to the original datapoint 748
7.3.8.3 Defining the states associations 749
7.4 Defining BCPU configuration in electrical architecture 751
7.4.1 Defining an electrical topology 751
7.4.1.1 Defining a Site 752
7.4.1.2 Defining a Substation 753
7.4.1.2.1 Adding a substation generic datapoint 753
7.4.1.2.2 Defining Local/Remote for substation 754
7.4.1.2.3 Defining Taking Control for substation and SCADA links 755
7.4.1.2.4 Adding a user function to a substation 757
7.4.1.3 Defining a Voltage level 757
7.4.1.3.1 Adding voltage level generic datapoint 758
7.4.1.3.2 Adding user function to voltage level 758
7.4.1.4 Defining a Bay 758
7.4.1.4.1 Adding bay generic datapoint 760
7.4.1.4.2 Defining Local Remote for bay 761
7.4.1.4.3 Defining SBMC for bay 762
7.4.1.4.4 Adding a user function to a bay 764
7.4.1.4.5 Adding toggling signal detection 764
7.4.1.4.6 Adding Missing Signaling Voltage 765
7.4.1.5 Defining Module 766
7.4.1.5.1 Adding a module generic datapoint 768
C264/EN UM/E50.5 29
7.4.1.5.2 Adding a user function to a module 768

7.4.1.5.3 Defining a lockable module 769
7.4.1.5.4 Defining withdrawable circuit-breaker or switchgear 770
7.4.1.5.5 Defining a circuit-breaker 770
7.4.1.5.6 Defining an I²t built-in function (relay folder) 774
7.4.1.5.7 Defining a switchgear 777
7.4.1.5.8 Defining a transformer 778
7.4.2 Defining a Synchrocheck function 780
7.4.2.1 Completing circuit-breaker definition for synchrocheck 780
7.4.2.2 External synchrocheck behavior 785
7.4.2.3 Internal synchrocheck behavior 785
7.4.2.4 Automation description of internal synchrocheck 785
7.4.2.5 Creating a synchrocheck function 788
7.4.2.5.1 Setting default settings of internal synchrocheck 790
7.4.2.5.2 Adding synchrocheck specific datapoints 793
7.4.2.5.3 Management of the 5th VT on TMU220: Double Busbar 794
7.4.2.5.4 Voltage reference selection 795
7.4.3 Defining an Auto-recloser built-in function 796
7.4.4 Defining a Tap changer built-in function 806
7.4.4.1 Tap changer behavior 806
7.4.4.2 Creating a tap changer built-in function 807
7.4.5 Defining an automatic voltage regulation–AVR built-in function 809
7.4.5.1 Creating an AVR function 809
7.4.5.2 AVR behaviour 819
7.4.6 Defining an automatic voltage regulation–ATCC built-in function 819
7.4.6.1 ATCC behavior 819
7.4.6.2 Creating an ATCC function 819
7.4.6.2.1 Defining ATCC function at substation level 820
7.4.6.2.2 Defining ATCC function needs at voltage level 824
7.4.6.2.3 Defining ATCC function needs at busbar level 825
7.4.6.2.4 Defining ATCC function needs at transformer level 827
7.4.6.2.5 Defining an electrical topology for ATCC function 830
7.4.7 Defining an electrical regulation by user function 833
7.4.7.1 Defining an FBD fast automation 834
7.4.7.1.1 Creating an FBD fast automation (header definition) 834
7.4.7.1.2 Creating FBD input plug (header definition) 835
7.4.7.1.3 Creating FBD output plug (header definition) 836
7.4.7.1.4 Using FBD editor (body definition) 837
7.4.7.1.5 Linking datapoints to FBD inputs and outputs 838
7.4.7.1.6 Creating FBD timer plugs 839
7.4.7.2 Defining an ISaGRAF® slow automation 843
7.4.7.2.1 Creating an ISaGRAF® slow automation (header definition) 843
7.4.7.2.2 Adding specific datapoints to slow automation (interface definition) 844
7.4.7.2.3 Creating ISaGRAF® client link (interface definition) 845
30 C264/EN UM/E50.5
7.4.7.2.4 Linking a datapoint to an ISaGRAF® client link 845

7.4.7.2.4.1 Defining ISaGRAF® IO prefix for an input 845
7.4.7.2.4.2 Creating ISaGRAF® server link (interface definition) 846
7.4.7.2.4.3 Linking a datapoint to an ISaGRAF® server link 846
7.4.7.2.4.4 Defining ISaGRAF® IO prefix for an output 847
7.4.7.2.4.5 Using ISaGRAF® editor (body definition) 848
7.4.7.3 Defining a group 848
7.4.7.5 Producing a DPS from two SPS 851
7.4.7.6 Defining interlocking 851
7.4.7.7 Defining an automatic/manual dependency 852
7.4.8 Defining a Fast Load Shedding application 853
7.4.8.1 Data flow 854
7.4.8.2 Priority Setpoints 855
7.4.8.3 Load Shedding Preselection (LSP) 855
7.4.8.4 Graphical animation with LSP 857
7.4.8.5 Use of LSP in PSL 857
7.4.8.6 Use of LSP in ISaGRAF® scheme 859
7.4.8.6.1 Set_LSP() ISaGRAF® function 859
7.4.8.6.2 Is_connected_to() ISaGRAF® function 860
7.4.8.7 Datapoints 860
7.4.8.8 MASK object and xPS triggers 860
7.4.8.8.1 MASK object 860
7.4.8.8.2 Trigger definition 860
7.4.8.9 Topology calculation 862
7.4.9 Defining a Synchroscope built-in function 863
7.4.9.1 Synchroscope behavior 863
7.4.9.2 Creating a Synchroscope built-in function 863
7.4.9.3 Limitations 866
7.5 Defining Protection Functions 867
7.5.1 General 867
7.5.1.1 General architecture 867
7.5.1.2 Defining a protection function 868
7.5.2.2 Defining Undervoltage protection function 870
7.5.3.2 Defining earth wattmetric protection function 872
7.5.4.2 Defining Undercurrent protection function 874
C264/EN UM/E50.5 31
7.5.5.2 Defining Negative Sequence Overcurrent protection function 876

7.5.6.2 Defining Thermal overload protection function 878
7.5.7.2 Defining overvoltage protection function 880
7.5.8.2 Defining Zero Sequence Overvoltage protection function 881
7.5.9.2 Defining [67] Directional overcurrent protection function 883
7.5.10 Dir. / Non-dir. Neutral / Ground / Earth OC protection (ANSI code
67N/50N/51N) 884
7.5.10.2 Defining [67N] Directional Earth/ground Fault protection function 885
7.5.11.2 Defining Overfrequency protection function 887
7.5.12.2 Defining Range Frequency protection function 889
7.5.13.2 Defining Underfrequency protection function 891
7.5.14.2 Defining a VT supervision protection function 893
7.5.15.2 Defining Inrush current blocking protection function 894
7.5.16 Defining automation of protection functions 895
7.5.16.1 General 895
7.5.16.2.1 Adding automation function 896
7.5.16.3 Protection setting groups 897
7.5.16.3.1 Description 897
7.5.16.3.2 Setting “2 protection group” automation functions 897
7.5.16.4 [50BF] breaker failure 897
7.5.16.4.2 Setting “[50BF] breaker failure” automatism functions 898
7.5.16.5 Blocking protection 899
32 C264/EN UM/E50.5
7.5.16.5.2 Setting ‘Blocking protection’ automation functions 899

7.5.16.6.2 Setting ‘Cold load start’ automation function 900
7.5.16.7 Logic selectivity 900
7.5.16.7.2 Setting ‘Logic selectivity’ automation function 901
7.5.16.8 Maintenance 901
7.5.16.8.2 Setting ‘Maintenance’ automatism menu 902
7.5.16.9 Miscellaneous 902
7.5.16.9.2 Setting ‘Miscellaneous’ automation menu 903
7.5.16.10.2 Setting ‘Trip management’ automation menu 904
7.6 Defining MiCOM C264 Local HMI 906
7.6.1 Defining a bitmap table 906
7.6.2 Defining a computer workspace 908
7.6.2.1 Settings LHMI labels 908
7.6.2.2 Creating a workspace 910
7.6.3 Defining a computer bay mimic 910
7.6.3.1 Creating a computer bay mimic 910
7.6.3.2 Defining static: part line, bitmap, fixed text 914
7.6.3.2.1 Adding a line 914
7.6.3.2.2 Adding a bitmap 916
7.6.3.2.3 Adding a fixed text 917
7.6.3.3 Defining dynamic part: pre-defined dynamic text, generic module
representation, transformer representation 918
7.6.3.3.1 Adding time information 918
7.6.3.3.2 Positioning Local/Remote status, Synchrocheck bypass or Interlock
bypass 919
7.6.3.3.3 Adding SBMC information 920
7.6.3.3.4 Adding a generic module representation 921
7.6.3.3.5 Adding a transformer representation 923
7.6.3.4 Assigning MV to bay mimic 925
7.6.4 Defining the generic measurements panel 927
7.6.4.1 Defining the presence of the main and secondary pages 927
7.6.4.2 Defining the MV display options 927
7.6.4.3 MV Bargraph 929
7.6.5 Displaying datapoint status with Led 929
8 Installation 931
8.1 Requirements 933
8.1.1 MiCOM C264 933
C264/EN UM/E50.5 33
8.1.2 Personal Computer 933

8.1.3 Communication wiring 933
8.2 Delivery reception 935
8.2.1 Packing inspection and opening 935
8.2.2 Delivery form checking 935
8.3 Mechanical mounting 936
8.3.1 Rack mounting 936
8.3.2 Panel mounting 936
8.4 Wiring installation 937
8.4.1 General wiring 937
8.4.2 Power supply wiring 937
8.4.3 I/O board wiring 937
8.4.4 Networks wiring 937
8.4.4.1 Serial communication 938
8.4.4.2 Optical communication 939
8.5 MiCOM C264 power up 940
8.6 MiCOM C264 installation 941
8.6.1 Introduction 941
8.6.2 Prequisites 941
8.6.4 MiCOM C264 installation 943
8.6.4.1 Note for secured installation 943
8.6.4.2 Note for authentication certificate 943
8.6.4.3 MiCOM C264 installing from scratch 944
8.6.4.3.1 Establish computer connection with CAT 945
8.6.4.3.2 Set computer boot parameter to “Bootprom boot” mode 948
8.6.4.3.3 Update new release of VxWorks BOOTROM 949
8.6.4.3.4 Format flash memory of CPU 957
8.6.4.3.5 Update new release of MiCOM C264 application 959
8.6.4.3.6 Set computer boot parameter to “Flash boot” mode 963
8.6.4.4 MiCOM C264 updating 965
8.6.4.5 MiCOM C264 roll-back 965
8.6.5 CAT installation 966
8.6.5.2 Prequisites 966
8.6.5.4 CAT installing from scratch 966
8.6.5.4.1 Framework NET 3.5 SP1 installation 967
8.6.5.4.2 WinpCap 4.1.3 driver installation 968
8.6.5.4.3 CAT installation 970
8.6.5.5 CAT updating 973
8.6.5.6 CAT roll-back 973
8.6.6 CAT: How to use it? 974
8.6.6.1 Human Machine Interface 974
8.6.6.2 Language selection 974
34 C264/EN UM/E50.5
8.6.6.3 Operator's record folders 975

8.6.6.4 Settings 975
8.6.6.5 Scan 975
8.6.6.6 Connection to a computer 979
8.6.6.7 Work pane 979
8.6.6.8 Modes and permitted operations 981
8.6.6.9 Routine operations 982
8.6.6.9.1 Display status and monitoring 982
8.6.6.9.2 Manage database (subject to privilege) 984
8.6.6.9.3 Edit settings (subject to privilege) 986
8.6.6.9.4 Manage events and states (subject to privilege) 986
8.6.6.9.4.1 Events 986
8.6.6.9.4.2 Latest datapoint values 989
8.6.6.9.5 Display errors and agency logs 990
8.6.6.9.6 Display AVR data 990
8.6.6.9.7 Waveforms 991
8.6.6.10 Expert Functions 992
8.6.6.10.1 Manage date and time (read, and change depending on profile) 992
8.6.6.10.2 Manage boot and network parameters 994
8.6.6.10.3 Manage communication ports 995
8.6.6.10.4 Load application software 996
8.6.6.10.5 Load bootrom software 996
8.6.6.10.6 Browse computer files 996
8.6.6.10.7 Launch a SSH session 997
8.6.6.11 REU board 997
8.6.6.11.1 REU Initial configuration with CAT 997
8.6.6.11.2 REU configuration with CAT 997
8.6.6.11.2.1 REU settings 997
8.6.6.11.2.2 REU firmware upgrade 1002
8.7 Uploading a security configuration with Cybersecurity Admin Expert 1004
8.8 Uploading database with CAT 1005
8.9 After computer installation 1006
8.10 Optional installation 1007
8.10.1 External master clock connection 1007
8.10.2 Printer installation 1007
9 Settings 1008
9.1 Setting via local LCD 1009
9.1.1 Tree Panel Navigation 1009
9.1.2 Tree Panel Parameters 1009
9.2 Setting via MiCOM S1 - PACiS software and CAT application 1016
9.2.1 General presentation of parameters in MiCOM S1 - PACiS 1016
9.2.1.1 ARPCCN parameters 1017
9.2.1.2 AVR parameters 1018
9.2.1.3 Auto-Recloser (Type 1) parameters 1019
C264/EN UM/E50.5 35
9.2.1.4 I²t parameters 1020

9.2.1.5 Internal Synchrocheck (Type 1) parameters 1020
9.2.1.6 FBD parameters 1022
9.2.1.7 Activate de-Activate protection function trip 1023
9.2.2 Upload a setting file to MiCOM C264 1023
9.2.3 Download a setting file from MiCOM C264 1029
9.2.4 Setting transfer’s dependence on computer modes 1035
9.2.5 MiCOM S1 - PACiS acknowledge 1035
10 Communication 1037
10.1 SCP Communication 1041
10.1.1 Communication on Station bus 1041
10.1.1.1 Finality 1041
10.1.1.2 Inputs 1042
10.1.1.2.1 Information: MiCOM C264 application / SCP 1042
10.1.1.2.2 Information: SCP / MiCOM C264 application 1042
10.1.1.3 Supported services 1042
10.1.1.4 Supported data objects 1042
10.2 Inter-rack Communication 1044
10.2.1 Main1-Main2 communication 1044
10.2.2 Main-Extension communication 1044
10.3 SCADA Communication 1045
10.3.1 Overview 1045
10.3.2 SCADA common functionality 1045
10.3.2.1 Interface to SCADA 1045
10.3.2.2 BCU 1045
10.3.2.2.1 Input 1045
10.3.2.2.2 Output 1046
10.3.2.3 Behaviour and specific treatments 1046
10.3.2.3.1 Initialization 1046
10.3.2.3.2 General interrogation 1046
10.3.2.3.3 Clock synchronisation 1047
10.3.2.3.4 Database downloading and switching 1047
10.3.2.3.5 Local/remote mode 1047
10.3.2.3.6 Taking Control 1047
10.3.2.3.7 SBMC mode 1047
10.3.2.3.8 Redundancy 1048
10.3.2.3.9 Automatic synchrocheck 1048
10.3.2.4 Data sent to SCADA 1048
10.3.2.4.1 Binary inputs 1048
10.3.2.4.2 Measurements 1048
10.3.2.4.3 Counters 1048
10.3.2.4.4 Tap position 1048
10.3.2.4.5 Computer disturbance file 1049
10.3.2.4.6 Sequence Of Events file (SOE) 1049
36 C264/EN UM/E50.5
10.3.2.4.7 Synchronization status 1049

10.3.2.5 Data sent to MiCOM C264 1049
10.3.2.5.1 Digital Controls or setpoints 1049
10.3.2.5.2 Counter commands 1050
10.3.2.5.3 Synchronization 1050
10.3.3 Slave DNP3 profile (serial or over IP) 1050
10.3.4 Slave IEC 60870-5-101 profile 1050
10.3.5 Slave IEC 60870-5-104 Server profile 1050
10.3.6 Slave Modbus (MODICON) profile 1050
10.4 IED Communication 1051
10.4.2 IED Common functionality 1051
10.4.2.1 Interface to IEDs 1051
10.4.2.1.1 Input 1051
10.4.2.1.2 Output 1052
10.4.2.2 Behavior 1052
10.4.2.2.1 Network supervision 1052
10.4.2.2.2 Time synchronization 1052
10.4.2.2.3 Polling of IED 1053
10.4.2.2.4 Monitoring of an IED 1053
10.4.2.3 Data received from IEDs 1056
10.4.2.3.1 Digital inputs 1057
10.4.2.3.3 Counters 1057
10.4.2.3.4 Tap position 1057
10.4.2.3.5 Disturbance File 1057
10.4.2.4 Data sent to IEDs 1057
10.4.2.4.1 Controls 1057
10.4.2.4.2 Setpoints 1058
10.4.2.5 Tunneling 1058
10.4.3 MODBUS communication 1059
10.4.3.1 Scope of this section 1059
10.4.3.2 Generic MODBUS Communication 1059
10.4.3.2.1 Polling and connection test 1060
10.4.3.2.2 Data received from IEDs 1060
10.4.3.2.2.1 AIs 1060
10.4.3.2.2.2 DIs 1061
10.4.3.2.3 Data sent to IEDs 1061
10.4.3.2.3.1 Connection check 1061
10.4.3.2.3.2 Clock synchronization 1061
10.4.3.2.3.3 DOs 1062
10.4.3.2.4 Error management 1062
10.4.3.2.5 Limits and specifications 1062
10.4.3.3 Schneider Electric MODBUS COMMUNICATION 1062
C264/EN UM/E50.5 37
10.4.3.3.1 Status byte 1063

10.4.3.3.1.1 Events buffer management 1064
10.4.3.3.1.2 M300 1064
10.4.3.3.1.3 MiCOM S40 (Px4x series) 1064
10.4.3.3.2.1 AIs 1065
10.4.3.3.2.2 M300 1066
10.4.3.3.2.3 MiCOM Px2 series and Px4 series 1068
10.4.3.3.2.4 DIs 1069
10.4.3.3.2.5 IED synchronized 1069
10.4.3.3.2.6 IED NOT synchronized 1069
10.4.3.3.2.7 Disturbance files 1071
10.4.3.3.2.8 M300 1073
10.4.3.3.2.9 MiCOM Px2 series and MiCOM Px4 series 1074
10.4.3.3.2.10 Events 1079
10.4.3.3.2.11 File upload 1083
10.4.3.3.3.2 Commands 1088
10.4.3.3.3.3 AOs 1093
10.4.3.3.3.4 Settings of the current relays 1094
10.4.3.3.3.5 Error management 1094
10.4.3.3.3.6 Limits and specifications 1095
10.4.3.4 IED SPECIFIC MODBUS 1096
10.4.3.4.1 M230 1096
10.4.3.4.2 Rish Pro M01 1097
10.4.3.4.3 Flexgate 1099
10.4.3.4.4 SEPAM 1100
10.4.3.4.5 WAGO 1101
10.4.4 DNP 3.0 Communication 1101
10.4.4.1.1 Input 1101
10.4.4.1.2 Output 1102
10.4.4.2 Behavior 1102
10.4.4.5 Master DNP3 Profile 1104
10.4.4.6 DNP3 Level 3 Implementation Table 1104
10.4.5 IEC 60870-5-103 Communication 1110
10.4.5.1.1 Input 1110
10.4.5.1.2 Output 1111
10.4.5.2 Behavior 1112
38 C264/EN UM/E50.5
10.4.5.2.2 Polling 1112

10.4.5.2.3 IED monitoring 1112
10.4.5.2.4 Tunneling mode 1112
10.4.5.2.5 Station Interlocking 1112
10.4.5.2.6 REG D 1113
10.4.5.2.7 Tapcon260 1113
10.4.5.3.3 Bitstring 32-bits : 1114
10.4.5.3.4 Analog protection signal (ASDU 49) : 1114
10.4.5.3.5 Energy counter (ASDU 79) : 1114
10.4.5.4.1 Controls 1115
10.4.5.4.2 Setpoints Controls : 1116
10.4.5.4.3 Read protection parameter : 1116
10.4.5.4.4 ASDU 232 / 105 management 1116
10.4.6.1 Purpose 1117
10.4.6.2 Master IEC 60870-5-101 profile 1117
10.4.7.1 Purpose 1117
11 Commissioning 1119
11.1 Scope 1120
11.1.1 Responsabilities 1120
11.1.3 Definition 1120
11.1.4 Commissioning the product 1120
11.1.5 Setting familiarization 1121
11.3 Commissioning Tests with GHU20x (with LCD) 1123
11.3.1 Preparation 1123
11.3.2 Check version & number 1123
11.3.4 Check the boards status 1124
11.3.5 Check the binary signal inputs 1125
11.3.6 Checking the output relays 1126
11.3.7 Testing the communication with external devices 1127
11.3.8 Testing the control functions 1127
11.3.9 Switching from local to remote control 1127
11.3.9.1 Local control 1127
11.3.9.2 Remote control 1127
11.3.10 Protection Commissioning Test environment 1128
11.3.10.1 Injection test sets 1128
C264/EN UM/E50.5 39
11.3.10.2 Protection Commissioning test sheets 1128

11.3.10.3 Use of a Core Balance CT for earth faults 1129
11.3.10.3.1 Cable shields and core CT 1129
11.3.10.3.2 Core CT polarity 1129
11.3.10.3.3 Protection parameters check 1130
11.3.10.3.4 Settings 1130
11.3.10.3.6 MiCOM C264P procedure 1130
11.3.10.4 Thresholds validation 1131
11.3.10.4.1 MiCOM C264P protection parameters 1131
11.3.10.4.2 MiCOM C264P Overcurrent parameters 1131
11.3.10.4.2.1 Phase overcurrent I> threshold test 1132
11.3.10.4.2.2 Phase to phase (phase to neutral) over-voltage U> threshold
test 1135
11.3.10.4.2.3 Earth fault overcurrent and residual over voltage test. 1135
11.3.10.4.3 MiCOM C264P frequency parameters 1137
11.3.10.4.3.1 Over and Underfrequency test 1137
11.3.10.4.3.2 Rate of change of frequency test 1138
11.4 Commissioning Tests with GHU21x (without LCD) 1140
12 Record Sheet 1141
12.1 Commissioning Record 1142
12.2 Maintenance Record Sheet 1143
13 Maintenance 1144
13.1 Responsibilities 1145
13.2 Standard Maintenance Operation 1146
13.2.1 Level 1 diagnosis facilities 1146
13.2.1.1 Front panel LED indications 1146
13.2.1.2 Front panel LCD indications 1149
13.2.1.3 Adjustment of the brightness of the front panel LCD 1149
13.2.2 Maintenance period 1150
13.2.3 Method of repair 1150
13.2.3.1 Replacing and installing a complete MiCOM C264 1150
13.2.3.2 Replacing a board 1152
13.2.3.2.1 Replacement of the Binary Input Unit (BIU241/261) 1155
13.2.3.2.2 Replacement of the main processor board (CPU2xx) 1155
13.2.3.2.3 Replacement of the Ethernet switch boards (SWU20x or SWR20x) 1155
13.2.3.2.4 Replacement of the I/O boards (DIU200, DIU211, DOU201,
CCU200, CCU211, AIU210, AIU211, AOU200 ) 1155
13.2.3.2.5 Replacement of the Transducerless Measurements Unit (TMU) 1156
13.2.3.2.6 Refit the MiCOM C264 1156
13.3 Cleaning 1157
13.4 Engineering Maintenance Operation 1158
14 Cyber Security 1159
14.1 Documentation Reference 1160
40 C264/EN UM/E50.5
14.2 Cybersecurity Policy 1161

14.2.1 Applicability 1161
14.2.2 Banner 1161
14.2.3 Password 1162
14.2.3.1 NERC CIP compliance for MiCOM C264 1163
14.2.3.2 Privileges and Default password 1163
14.2.3.3 Security Policy 1163
14.2.4 Security Logs 1164
14.2.5 Hardening 1165
14.2.6 Reset to Factory 1165
14.2.7 Patch Management 1166
14.2.8 Authentication Configuration for RADIUS Client/Server 1166
14.2.9 Authentication Certificate for MiCOM C264 1170
14.2.10 Firmware Signature for MiCOM C264 1170
14.2.10.1 LOG (alarm) 1170
14.2.10.2 HMI (alarm) 1171
14.2.10.3 LED (alarm) 1171
14.2.10.4 Datapoint (alarm) 1171
15 Annex 1172
15.1 Introduction 1176
15.1.1 MiCOM Ethernet Device Series 1176
15.1.2 MiCOM C264Ethernet switch boards 1176
15.1.3 MiCOM Ethernet Redundant REU20x 1176
15.2 Glossary and Definitions 1177
15.3 SWR21x Range – Dual Ring Architecture 1179
15.3.1 Fast redundant ring capability 1179
15.3.1.1 Self healing ring 1179
15.3.1.2 Ethernet switch with Self-healing ring facilities 1179
15.3.1.3 Schneider Electric Ethernet ring redundancy 1180
15.3.1.4 Ethernet system performances 1181
15.3.1.5 Max time of end to end delay 1181
15.3.1.6 Benefits 1182
15.3.2 SNMP Management 1182
15.3.2.1 SWR21x - MIB Structure 1182
15.3.2.2 SNMP Client Software 1184
15.3.3 SWR21x Leds 1184
15.3.4 Settings 1185
15.3.4.1 Internal Jumpers 1185
15.3.4.2 Address of the board 1186
15.3.4.3 How to configure the address ? 1186
15.3.4.4 IP Address of the repeater 1186
15.3.5 Connections: J14 Fault signal output 1187
15.4 SWD21x Range – Dual Homing Architecture 1188
15.4.1 Dual homing typical architecture 1188
C264/EN UM/E50.5 41
15.4.2 Dual homing Switch Description 1189

15.4.3 Dual homing Features 1189
15.4.3.1 10Base T and 100Base Tx 1189
15.4.3.2 Power management 1189
15.4.3.3 Address look up 1189
15.4.3.4 Back pressure for half duplex 1189
15.4.3.5 Auto Negotiation and Speed-Sensing 1189
15.4.3.6 Forwarding 1190
15.4.3.7 Priority tagging 1190
15.4.3.8 Flow control 1190
15.4.5 SWD21x Leds 1190
15.5 SWU20x Range – Star Architecture 1193
15.5.1 Ethernet Port Characteristics 1193
15.5.1.1 10/100BaseTx Port 1193
15.5.1.2 100BaseFx Multi Mode Port 1193
15.5.1.3 100BaseFx Single or Mono Mode Port 1193
15.5.2 Ethernet Port Switching Features 1194
15.5.2.1 10Base Tx and 100Base Tx 1194
15.5.2.2 100Base Fx 1194
15.5.3 Ethernet Management 1194
15.5.3.2 Buffering 1194
15.5.3.3 Back off operation 1194
15.5.3.5 Broadcast storm protection 1194
15.6 SWS21X Range – Star Architecture 1196
15.6.1 Capability 1196
15.6.1.1 Principle 1196
15.6.1.2 Schneider Electric RSTP compatibility 1196
15.6.1.3 Configuration constraints 1196
15.6.2 Functional composition 1197
15.6.3 Power management 1198
15.6.4.2 100Base Fx 1198
15.6.5.1 Address lookup 1198
42 C264/EN UM/E50.5
15.6.5.2 Auto-negociation and speed-sensing 1198

15.6.6.1 SWS21 MIB Structure 1199
15.6.7 Technical Data 1200
15.6.7.1 SWS21 Range 1200
15.6.7.2 Ethernet Port Characteristics 1201
15.6.7.2.1 10/100BaseTx Port 1201
15.6.7.2.2 100BaseFx Multi Mode Port 1201
15.6.7.2.3 100BaseFx Single Mode Port 1201
15.6.7.3 General Characteristics 1201
15.6.8 SWS21x Leds 1202
15.6.9.1.1 JP1 1204
15.6.9.1.2 J10 (board number) 1204
15.6.10 Connections 1206
15.6.10.1 Ethernet connection 1206
15.6.10.1.1 Ethernet cable type 1206
15.6.10.1.2 Ethernet optical fiber 1206
15.6.10.2 Internal connectors 1207
15.6.10.2.1 MiCOM C264 BUS (J13) 1207
15.6.10.2.2 10/100BaseTx ports 1 to 4 (J3) 1207
15.6.10.2.3 Fault signal output (J14) 1208
15.7 REU20x Range –Architecture with PRP, HSR and RSTP 1209
15.7.1 Functional Description 1210
15.7.1.1 Product Range 1210
15.7.1.2 PRP/HSR/RSTP Architecture 1210
15.7.1.4 Ethernet Ports 1213
15.7.1.5 IEEE 1588 PTP 1213
15.7.2 Technical data 1214
15.7.2.1 REU20x Range 1214
15.7.2.2 Board Architecture 1214
15.7.2.2.1 10/100BaseTx port characteristics 1215
15.7.2.3.1 Protocols supported 1215
15.7.2.3.2 Status Relay 1215
15.7.2.3.3 Ethernet Management 1216
15.7.2.3.5 Interoperability 1216
15.7.2.4 Environmental Characteristics 1217
C264/EN UM/E50.5 43
15.7.2.4.1 Definitions 1217

15.7.2.4.2 Insulation 1217
15.7.2.4.3 Electromagnetic Compatibility 1217
15.7.2.4.4 Climatic 1219
15.7.2.4.5 Mechanical 1219
15.7.3 Connections and Led meaning 1221
15.7.3.1 Led meaning 1222
15.7.3.2 Status connector 1222
15.7.4 Installation 1222
15.7.4.1 Status output 1223
15.7.4.2 Ethernet Connection 1224
15.7.5 Maintenance 1224
15.7.5.1 Uninstalling REU20x board 1224
15.7.5.2 Reinstalling REU20x board 1225
15.8 Fiber Optic budget calculation 1226
15.8.1 Example 1: between devices 1226
15.8.2 Example 2: between devices with patch panel 1226
44 C264/EN UM/E50.5
MiCOM C264 - User Manual 1 Overview
1 Overview
This chapter contains the following topics:
1.1 About this guide 46

1.1.1 Document updates 46
1.2 What's new? 47
1.2.1 Current guide revision 47
1.2.2 Previous guide revisions 47
1.3 Document organization and content 49
1.4 How to use this document ? 50
1.5 How to read this document ? 51
1.6 Introduction to MiCOM range 52
1.7 Introduction to MiCOM C264 applications 53
1.7.1 MiCOM C264 Computers 53
1.7.2 Applications and Scope 53
C264/EN UM/E50.5 45
1 Overview MiCOM C264 - User Manual
1.1 About this guide

This guide is intended for Application Engineers, System Integrators, or other qualified personnel
who are responsible for designing, installing, configuring, maintaining, and using MiCOM C264
device.
This guide is not a tutorial, it was written with the assumption that you have been trained in the
deployment and use of MiCOM C264.
This guide does not discuss the planning, design, and operation of the electrical power system
that is being monitored.
1.1.1 Document updates

This document is available online through the Schneider Electric website. We may update the
online version over time to improve clarity and accuracy. If you see differences between your local
copy and the online version, use the online version as your reference.
46 C264/EN UM/E50.5
1.2 What's new?

1.2.1 Current guide revision
Revision Number: E50.5
Release Date: 06/2022
Content changes:
Chapter Topic Change

"Hardware" on "DOU201 board - Digital
Added making capacity for the DOU201 Board
page 393 Output Unit" on page 458
"Functional
"Missing Signaling Voltage Modified explanations for Missing
Description" on
(MSV)" on page 174 Signaling Voltage
page 100
"Application" on "Defining MV datapoint" on Added information for definition of Scaling
page 555 page 693 attribute for MV datapoint
"Functional
"Bay/Module/xPC order Added wired limitation for 'on/off order'
Description" on
running" on page 234 SPS
page 100
Modified organization of document for html
Global
output
1.2.2 Previous guide revisions

1.2.2.1 Revision number: E50.4 (03/2022)
Content changes:

"Cyber Security" on "Security Logs" on page Withdrawal of Security Administration Manager (SAM)
page 1159 1164 reference

Content changes:

"Human Machine
added CR2247 - selection of MSC panels from graphical
Interface" on page "Bay panels" on page 509 bay panel
498
"Setting specific features of a
"Application" on page 555 added CR4385 - Phase wise fault information
TMU210 board" on page 582
C264/EN UM/E50.5 47

Content changes:

"Overview" on Added statement of compliance with SL1 according to IEC
"What's new?" on page 47 62443-4-1 and IEC 62443-4-2.
page 45
"Annex" on page "SWR21x Leds" on page
Corrected FR40422
1172 1184
48 C264/EN UM/E50.5
1.3 Document organization and content

This document is organized by the following chapters:
Chapter Description
"Overview" on page 45 • Document overview
• safety instructions for MiCOM C264
• handling and reception of MiCOM C264

Safety and Handling
• packing and unpacking parts of MiCOM C264
• Copyrights and Trademarks of MiCOM C264

• technical data of MiCOM C264 firmware
Technical Data • information associated with compatibility of current transformers
for MiCOM C264P
Functional Description • Functional Description of MiCOM C264
• compiling technical data, hardware description and connection
Hardware
diagrams about MiCOM C264 hardware
• operator interface description of MiCOM C264 front panel, with
menu tree organization, navigation and Led management
Human Machine
Interface • Computer Administration Tool software for MiCOM C264 (CAT)
• Printer interface
Installation • installation procedures of MiCOM C264
Settings • list of settings of MiCOM C264 with default values and range
• protocols supported by MiCOM C264 with SCADA via
Communication
Telecontrol BUS, IED via Legacy BUS or IEC 61850 Station BUS
• instructions on MiCOM C264 commissioning, comprising checks
Commissioning
on the settings and functionality of the device
• diagnostic of MiCOM C264 status
Maintenance
• recommended actions to repair MiCOM C264
Application • configuration of MiCOM C264 using EPAS-SCE
Cyber Security • recommendations for Cyber Security of MiCOM C264
Annex • instructions on how to set the networks for MiCOM C264
Record Sheet • record sheet to follow the maintenance of MiCOM C264
Lexicon • description of acronyms and definitions.
C264/EN UM/E50.5 49
1.4 How to use this document ?

The best way to use this document is by using document bookmarks and the introductory pages
for each chapter. Use the Bookmarks to navigate to the chapter introduction, and then use the
chapter link page to navigate to the content you are looking for. Much of the content contains
hyperlinks to connect related content.
You can also use the table of contents to navigate through the document, or use Find to search
for specific content.
50 C264/EN UM/E50.5
1.5 How to read this document ?

C264 (respectively C264P) is a common abbreviation of MiCOM C264 (respectively
MiCOM C264P) used in this guide.
This guide is applicable for both MiCOM C264 and MiCOM C264P ranges. By default
MiCOM C264 stands generically for MiCOM C264 or MiCOM C264P.
If necessary, these icons will be used throughout the different topics only as follows:
Icon Description
A green circle with the white check mark next C264 icon means that the
information is applicable ONLY on MiCOM C264.
A red circle with the white cross next C264 means that the information is NOT
applicable on MiCOM C264.
A green circle with the white check mark next C264P icon means that the
information is applicable ONLY on MiCOM C264P.
A red circle with the white cross next C264P means that the information is NOT
applicable on MiCOM C264P
C264/EN UM/E50.5 51
1.6 Introduction to MiCOM range

MiCOM is a comprehensive solution capable of meeting all electricity supply requirements. It
comprises a range of components, systems and services from Schneider Electric.
Central to the MiCOM concept is flexibility.
MiCOM provides the ability to define an application solution and, through extensive
communication capabilities, to integrate it with your power supply control system.
The components within MiCOM are:

• P range protection relays;
• C range control products;
• M range measurement products for accurate metering and monitoring;
• S range versatile PC support and substation control packages.
• A range industrial PC.
MiCOM products include extensive facilities for recording information on the state and behavior of
the power system using disturbance and fault records. They can also provide measurements of
the system at regular intervals to a control center enabling remote monitoring and control to take
place.
The MiCOM range will continue to be expanded. The general features of MiCOM will also be
enhanced, as we are able to adopt new technology solutions.
52 C264/EN UM/E50.5
1.7 Introduction to MiCOM C264 applications

Schneider Electric philosophy is to provide a range of computers (MiCOM C264 and Easergy C5),
EPAS-Gateway and IEDs products. Each of these products can be used independently, or can be
integrated to form an EcoStruxure™ Power Automation System (EPAS system), a Digital Control
System (DCS) or a SCADA system.
1.7.1 MiCOM C264 Computers

Driven by the requirements around the world for advanced applications in SCADA, Digital Control
Systems, Automation, control and monitoring, Schneider Electric has designed and developed a
complete range of computer productsMiCOM C264 specifically for the power process
environment and electric utility industry. It allows building a personalized solution for Control,
Monitoring, Measurement and Automation of electrical processes.
MiCOM C264 computers range are designed to address the needs of a wide range of
installations, from small to large and customer applications. Emphasis has been placed on strong
compliance to standards, scalability, modularity and openness architecture. These facilitate use
in a range of applications from the most basic to the most demanding. They also ensure
interoperability with existing components and, by providing building computers, PLC or IEDs
approach, provide a comprehensive upgrade path, which allows EPAS capabilities to track
customer requirements.
Key features are that this computer family is based on an Ethernet client/server architecture. It is a
modular computer that offers a large variety of applications such as Bay Computer, Remote
Terminal Unit, Sequence of Event Recorder, Data Concentrator and Programmable Logic
Controller.
Phase in time, dedicated computer available for each application will be purposed.
1.7.2 Applications and Scope

The MiCOM C264 modular bay controller, RTU or PLC is used to control and monitor switchbays.
The information capacity of the MiCOM C264 is designed for controlling operated switchgear
units equipped with electrical check-back signalling located in medium-voltage or high-voltage
substations.
External auxiliary devices are largely obviated by the integration of binary inputs and power
outputs that are independent of auxiliary voltages, by the direct connection option for current and
voltage transformers, and by the comprehensive interlocking capability.
This simplifies handling of bay protection and control technology from planning to station
commissioning. During operation, the user-friendly interface makes it easy to set the unit and
allows safe operation of the substation by preventing non-permissible switching operations.
Continuous self-monitoring reduces maintenance costs for protection and control systems.
A built-in liquid crystal display (optional front face with LCD) shows not only switchgear settings
but also measured data and monitoring signals or indications.
The bay is controlled interactively by using the control keys and the display.
Adjustment to the quantity of information required is made via the EcoStruxure™ Power
Automation System - System Configuration Editor(EPAS-SCE).
C264/EN UM/E50.5 53
The MiCOM C264 can be connected to a higher control level, local control level or lower levels by
way of a built-in communications interface.
The next figures show some typical cases that can be mixed to face specific constraints.
• The first case uses several MiCOM C264 linked together on SBUS Ethernet. A
EPAS-Gateway grants access to a SCADA.
• The second case uses one MiCOM C264 linked to various IEDs from MiCOM and SEPAM
ranges and possibly to a remote SCADA (Stand-alone approach).
- Figure 1 - MiCOM C264 application use case #1
- Figure 2 - MiCOM C264 application use case #2
54 C264/EN UM/E50.5
MiCOM C264 - User Manual 2 Safety and Handling
2 Safety and Handling

2.1 Symbols and External Labels on the Equipment 56

2.2 Installing, Commissioning and Servicing 57
2.2.1 Qualified Persons 57
2.2.2 Earth / Ground 57
2.2.3 Mounting 58
2.2.4 Servicing and maintenance 59
2.2.5 UL and CSA / CUL Listed or Recognized equipment 60
2.2.6 Storage 61
2.3 Decommissioning and Disposal 62
2.4 Technical Specifications for Safety 63
2.4.1 Protective fuse rating 63
2.4.2 Protective Class 63
2.4.3 Installation Category 63
2.4.4 Environment 63
2.5 Compliance Marking for Applicable European Directives 64
2.6 Recognized and Listed Marks for North America 65
2.7 Recognized and Listed Mark for Custom Union and Russian Federation 66
2.8 Typical Labels 67
2.8.1 Labels for standard LED indicators and menu navigation keys 67
2.8.2 General Labels 68
2.9 Handling of Electronic Equipments 71
2.10 Guarantees 72
2.11 Copyrights & Trademarks 73
2.11.1 Copyrights 73
2.11.2 Trademarks 73
2.12 Warnings Regarding use of Schneider Electric Products 74
C264/EN UM/E50.5 55
2 Safety and Handling MiCOM C264 - User Manual
2.1 Symbols and External Labels on the Equipment

The explanation of symbols and labels, installed on the equipment or used in the product
documentation, is given below.
Symbol Description
Caution
The text associated with this symbol warns against incorrect use or handling
of the product which can damage the equipment. Please Refer to equipment
documentation.
Caution: risk of electric shock
This symbol warns against the risk of electric shock.
Protective Conductor (Earth) terminal
See NOTE (2)
Functional/Protective Conductor (Earth) terminal
See NOTE (3)
Caution: Risk of eye injure
NOTE: THE TERM EARTH USED THROUGHOUT THIS TECHNICAL GUIDE IS THE DIRECT
EQUIVALENT OF THE NORTH AMERICAN TERM GROUND.
NOTE: (2) This symbol indicates a Protective Conductor Terminal that have to be connected to
earth / ground before operating the equipment helps to protect against electrical shock in case of
a fault.
NOTE: (3) This symbol may also be used for a Protective Conductor Terminal if that terminal is
part of a terminal block or sub-assembly e.g. power supply.
56 C264/EN UM/E50.5
2.2 Installing, Commissioning and Servicing

2.2.1 Qualified Persons
Only qualified personnel, equipped with appropriate individual protection equipment, may work on
or operate the equipment. Qualified personnel are individuals who:
• Are familiar with the installation, commissioning, and operation of the equipment and of the
system to which it is being connected.
• Are able to safely perform switching operations in accordance with accepted safety
engineering practices and are authorized to energize and de-energize equipment and to
isolate, earth/ground, and label it.
• Are trained in the care and use of safety apparatus in accordance with safety engineering
practices.
• Are trained in emergency procedures (first aid).
DANGER
HAZARD OF ELECTRIC SHOCK, EXPLOSION OR ARC FLASH BEFORE PERFORMING
ANY INTERVENTION
• Turn off all power supplying the MiCOM C264 and the equipment in which it is installed
before working on it.
• Always use a properly rated voltage sensing device to confirm that power is off.
• Replace all devices, doors, and covers before turning on power to this equipment.
• Apply appropriate personal protective equipment and follow safe electrical work practices.
See local regulation.
2.2.2 Earth / Ground
DANGER
HAZARD OF ELECTRIC SHOCK, EXPLOSION OR ARC FLASH
• Connect the ground terminal of the equipment to the protective earth / ground.
• Comply with national and local electrical standards with respect to the earth / ground of each
equipment.
• Check equipotential earthing / grounding network and test earth / ground during installation.
• The recommended minimum protective conductor (earth) wire size is 2.5 mm² (3.3 mm² for
North America) unless otherwise stated in the technical data section of the equipment
documentation, or otherwise required by local or country wiring regulations.
• The protective conductor (earth) connection must be low-inductance and as short as
possible.
C264/EN UM/E50.5 57
2.2.3 Mounting
DANGER
HAZARD OF FIRE
• Insufficient tightening causes loose and ineffective connections with high contact resistance
and overheating with current and fire hazard in extreme cases.
• The clamping screws of all terminal block connectors, for field wiring, using M4 screws that
shall be tightened to a nominal torque of 1.3 Nm.
• To ensure that wires are correctly terminated the correct crimp terminal and tool for the wire
size should be used.
DANGER
• Equipment intended for rack or panel mounting is for use on a flat surface of a Type 1
enclosure, as defined by Underwriters Laboratories (UL).
• Removal of the equipment front panel/cover may expose hazardous live parts, which must
not be touched until the electrical power is removed.
• Voltage and current connections shall be made using insulated crimp terminations to ensure
that terminal block insulation requirements are maintained for safety.
• All connections to the equipment must have a defined potential. Connections that are pre-
wired, but not used, should preferably be grounded when binary inputs and output relays are
isolated. When binary inputs and output relays are connected to common potential, the pre-
wired but unused connections should be connected to the common potential of the ground
connections.
• The equipment must be connected in accordance with the appropriate connection diagram.
• It is possible to change current or voltage settings on some equipment by direct physical
adjustments e.g. adjustment of a plug-bridge setting. The electrical power should be
removed before making any change, to avoid the risk of electric shock.
• Before energizing the equipment, the following should be checked:
• Voltage rating / polarity (rating label / equipment documentation),
• CT circuit rating (rating label) and integrity of connections,
• Protective fuse rating,
• Integrity of the protective conductor (earth) connection (where applicable)
• Voltage and current rating of external wiring, applicable to the application.
58 C264/EN UM/E50.5
NOTICE
HAZARD OF DAMAGE TO ELECTRONICS AND LIFETIME REDUCTION
The equipment is intended for indoor installation and use only. If it is required for use in an
outdoor environment then it must be mounted in specific cabinet or housing which will enable it
to meet the requirements of IEC 60529 with the classification of degrees of protection IP54
(dust and splashing water protected).
Failure to follow these instructions can result in equipment damage.
2.2.4 Servicing and maintenance
DANGER
• If there is unlocked access to the rear of the equipment, care should be taken by all
personnel to avoid electric shock or energy hazards.
• Voltage and current connections shall be made using insulated crimp terminations to ensure
that terminal block insulation requirements are maintained safely.
• Removal of the equipment front panel / cover may expose hazardous live parts, which must
not be touched until the electrical power is removed.
• Do not open the secondary circuit of a live CT. The secondary of the line CT must be shorted
before opening any connections to it.
• Insulation testing may leave capacitors charged up to a hazardous voltage. At the end of
each part of the test leads are disconnected.
• Where internal batteries are fitted they should be replaced with the recommended type and
be installed with the correct polarity.
• Where external resistors, including voltage dependent resistors (VDRs), are fitted to the
equipment, these may present a risk of electric shock or burns, if touched.
• All connections to the equipment must have a defined potential. Connections that are pre-
wired, but not used, should preferably be grounded when binary inputs and output relays are
isolated. When binary inputs and output relays are connected to common potential, the pre-
wired but unused connections should be connected to the common potential of the ground
connections.
• The equipment must be connected in accordance with the appropriate connection diagram.
C264/EN UM/E50.5 59
CAUTION
HAZARD OF FIRE, DAMAGE TO ELECTRONICS OR MALFUNCTION
• Do not withdraw the device if you are not authorized.
• If you are authorized to withdraw the device: disconnect the power supply before removing
or replacing a module or the withdrawable part of the device; never touch electronics parts
(risk of damage due to electrostatic discharge); before replacing the withdrawable part,
visually check the cleanliness and the absence of foreign objects into the case, the
withdrawable part and the connectors.
• In case of module or withdrawable part replacement, perform the commissioning operations
before using the device.
• Extender cards are available for some equipment. If an extender card is used, this should
not be inserted or withdrawn from the equipment whilst it is energized.
• Modules and PCB cards must not be inserted into or withdrawn from the equipment whilst it
is energized, since this may result in damage.
Failure to follow these instruction can result in injury or equipment damage.
2.2.5 UL and CSA / CUL Listed or Recognized equipment
DANGER
• To maintain UL and CSA / CUL Listing / Recognized status for North America the equipment
should be installed using UL or CSA Listed or Recognized parts for the following items:
connection cables, protective fuses / fuseholders or circuit breakers, insulation crimp
terminals and replacement internal battery, as specified in the equipment documentation.
• For external protective fuses a UL or CSA Listed fuse shall be used. The listed type shall be
a Class J time delay fuse, with a maximum current rating of 15 A and a minimum DC rating
of 250, for example type AJT15.
• Where UL or CSA Listing of the equipment is not required, a high rupture capacity (HRC)
fuse type with a maximum current rating of 16 Amps and a minimum DC rating of 250 VDC
may be used, for example Red Spot type NIT or TIA.
CAUTION
HAZARD OF BLINDING
Never look into the end of the fiber optics
Failure to follow these instruction can cause serious injury.
60 C264/EN UM/E50.5
2.2.6 Storage
NOTICE
HAZARD OF DAMAGE TO ELECTRONICS AND LIFETIME REDUCTION
• Do not expose the products to sustained humidity during storage.
• Power on the products within three months after unpacking.
• Where electrical equipment is being installed, allow sufficient time for acclimatization to the
ambient temperature of the environment before powering on.
Failure to follow these instructions can result in equipment damage.
C264/EN UM/E50.5 61
2.3 Decommissioning and Disposal
DANGER
• The supply input (auxiliary) for the equipment may include capacitors across the supply to
earth. To avoid electric shock or energy hazards, after completely isolating the supplies to
the equipment (both poles of any DC supply), the capacitors should be safely discharged via
the external terminals prior to decommissioning.
62 C264/EN UM/E50.5
2.4 Technical Specifications for Safety

Unless otherwise stated in the equipment technical manual, the following data is applicable.
2.4.1 Protective fuse rating
DANGER
CTs must not be fused since open circuiting them may produce lethal hazardous voltage.
The recommended maximum rating of the external protective fuse for equipments is 16A, high
rupture capacity (HRC) Red Spot type NIT, or TIA, or equivalent. Unless otherwise stated in
equipment technical manual, the following data is applicable. The protective fuse should be
located as close to the unit as possible.
2.4.2 Protective Class
IEC 60255-27: 2013 Class I (unless otherwise specified in the equipment

documentation). This equipment requires a protective conductor
EN 60255-27: 2014 (earth) connection to ensure user safety.
2.4.3 Installation Category

Installation Category III (Overvoltage Category III):
IEC 60255-27: 2013 Distribution level, fixed installation.
EN 60255-27: 2014 Equipment in this category is qualification tested at 5 kV peak,

1.2/50 µs, 500 W, 0.5 J, between all supply circuits and earth and
also between independent circuits
2.4.4 Environment
Pollution Degree - Pollution
Degree 2
Compliance is demonstrated by reference Altitude - Operation up
IEC 60255-27: 2013 to 2000m to safety standards.
EN 60255-27: 2014
C264/EN UM/E50.5 63
2.5 Compliance Marking for Applicable European Directives

The following European directives may be applicable to the equipment, if so it will carry the
relevant marking(s) shown below:
Compliance with all relevant European Community directives:
Marking
Product safety:
Low Voltage Directive Compliance demonstrated via a Technical File, with reference to
(LVD) 2014/35/EU product safety standards.
EN 60255-27: 2014
Electromagnetic
Compatibility Directive
(EMC) 2014/30/EU
The following Product Compliance demonstrated via a Technical File, with reference to
Specific Standard was EMC standards.
used to establish
compliance:
EN 60255-26: 2013
Where applicable:
The equipment is compliant with Article 1(2) of European

directive 2014/24/EU. It is approved for operation outside an
ATEX hazardous area. It is however approved for connection to
Increased Safety, “Ex e”, motors with rated ATEX protection,
Equipment Category 2, to ensure their safe operation in gas
Zones 1 and 2 hazardous areas.
CAUTION – Equipment with this marking is not itself suitable for

ATEX Potentially Explosive
operation within a potentially explosive atmosphere.
Atmospheres directive
2014/24/EU, for equipment. Compliance demonstrated by Notified Body certificates of
compliance.
64 C264/EN UM/E50.5
2.6 Recognized and Listed Marks for North America

CSA - Canadian Standards Association
UL - Underwriters Laboratory of America
If applicable, the following marks will be present on the equipment:
– UL Recognized to UL (USA) requirements
– UL Recognized to UL (USA) and CSA (Canada) requirements
– UL Listed to UL (USA) requirements
– UL Listed to UL (USA) and CSA (Canada) requirements
– Certified to CSA (Canada) requirements
C264/EN UM/E50.5 65
2.7 Recognized and Listed Mark for Custom Union and Russian
Federation
If applicable, the following marks will be present on the equipment:
– Eurasian conformity mark to all technical regulations of the

Eurasian Customs Union
66 C264/EN UM/E50.5
2.8 Typical Labels

2.8.1 Labels for standard LED indicators and menu navigation keys
LED labels
Trip
Alarm
Out of service
Healthy
Protection Available
Power
Inst (Instantaneous)
Parallel
Serial
Accept/Read
Set
Reset
Setting Group
Aux Timer
Select/Reset
Power Swing
Menu key labels
Enter
Read
Clear
Edit mode
C264/EN UM/E50.5 67
2.8.2 General Labels
68 C264/EN UM/E50.5
1. nnnn - identifying number of the Notified Body which demonstrated manufacturing Quality
Assurance compliance to EN 13980, e.g. 0891.
2. Ex logo - signifies compliance with European ATEX directive 2014/24/EU.
3. Name - Notified Body which carried out the EC Type Examination of the equipment design
and construction, e.g. PTB.
4. yy - year certificate issued e.g. 03 for 2003.
5. ATEX - compliance with European ATEX directive 2014/24/EU.
6. xxxx - approval number given by the Notified Body for the EC Type Examination of the
equipment, e.g. 3043.
7. (2) - The equipment is compliant with Article 1(2) of directive 2014/24/EU. It is approved
for operation outside an ATEX hazardous area. It is however approved for connection to
“Increased Safety” motors with rated ATEX protection, Equipment Category 2, to ensure
their safe operation in gas Zones 1 and 2 hazardous areas.
Typical rating label
C264/EN UM/E50.5 69
70 C264/EN UM/E50.5
2.9 Handling of Electronic Equipments

A person’s normal movements can easily generate electrostatic potentials of several thousand
volts.
Discharge of these voltages into semiconductor devices when handling circuits can cause serious
damage, which often may not be immediately apparent but the reliability of the circuit will have
been reduced.
The electronic circuits of Schneider Electric products are immune to the relevant levels of
electrostatic discharge when housed in their cases. Do not expose them to the risk of damage by
withdrawing modules unnecessarily.
Each module incorporates the highest practicable protection for its semiconductor devices.
However, if it becomes necessary to withdraw a module, the following precautions should be
taken in order to preserve the high reliability and long life for which the equipment has been
designed and manufactured.
1. Before removing a module, ensure that you are a same electrostatic potential as the
equipment by touching the case.
2. Handle the module by its front-plate, frame, or edges of the printed circuit board. Avoid
touching the electronic components, printed circuit track or connectors.
3. Do not pass the module to any person without first ensuring that you are both at the same
electrostatic potential. Shaking hands achieves equipotential.
4. Place the module on an antistatic surface, or on a conducting surface, which is at the same
potential as you.
5. Store or transport the module in a conductive bag.
If you are making measurements on the internal electronic circuitry of any equipment in service, it
is preferable that you are earthen to the case with a conductive wrist strap.
Wrist straps should have a resistance to ground between 500k – 10M Ohms. If a wrist strap is not
available you should maintain regular contact with the case to prevent the build up of static.
Instrumentation which may be used for making measurements should be earthen to the case
whenever possible.
C264/EN UM/E50.5 71
2.10 Guarantees
The media on which you received Schneider Electric software are guaranteed not to fail executing
programming instructions, due to defects in materials and workmanship, for a period of 90 days
from date of shipment, as evidenced by receipts or other documentation. Schneider Electric will,
at its option, repair or replace software media that do not execute programming instructions if
Schneider Electric receive notice of such defects during the guaranty period. Schneider Electric
does not guaranty that the operation of the software shall be uninterrupted or error free.
A Return Material Authorisation (RMA) number must be obtained from the factory and clearly
marked on the package before any equipment acceptance for guaranty work. Schneider Electric
will pay the shipping costs of returning to the owner parts, which are covered by warranty.
Schneider Electric believe that the information in this document is accurate. The document has
been carefully reviewed for technical accuracy. In the event that technical or typographical errors
exist, Schneider Electric reserves the right to make changes to subsequent editions of this
document without prior notice to holders of this edition. The reader should consult Schneider
Electric if errors are suspected. In no event shall Schneider Electric be liable for any damages
arising out of or related to this document or the information contained in it.
Expect as specified herein,Schneider Electric makes no guaranties, express or implied and

specifically disclaims and guaranties of merchantability or fitness for a particular purpose.
Customer's rights to recover damages caused by fault or negligence on the part Schneider
Electric shall be limited to the amount therefore paid by the customer. Schneider Electric will not
be liable for damages resulting from loss of data, profits, use of products or incidental or
consequential damages even if advised of the possibility thereof. This limitation of the liability of
Schneider Electric will apply regardless of the form of action, whether in contract or tort, including
negligence. Any action against Schneider Electric must be brought within one year after the cause
of action accrues. Schneider Electric shall not be liable for any delay in performance due to
causes beyond its reasonable control. The warranty provided herein does not cover damages,
defects, malfunctions, or service failures caused by owner's failure to follow the Schneider Electric
installation, operation, or maintenance instructions. Owner's modification of the product; owner's
abuse, misuse, or negligent acts; and power failure or surges, fire, flood, accident, actions of third
parties, or other events outside reasonable control.
72 C264/EN UM/E50.5
2.11 Copyrights & Trademarks

2.11.1 Copyrights
Under the copyright laws, this publication may not be reproduced or transmitted in any form,
electronic or mechanical, including photocopying, recording, storing in an information retrieval
system, or translating, in whole or in part, without the prior written consent of Schneider Electric.
2.11.2 Trademarks
EcoStruxure™ Power Automation System (EPAS), PACiS and PACiS SCE are trademarks of
Schneider Electric. Product and company names mentioned herein are trademarks or trade
names of their respective companies.
C264/EN UM/E50.5 73
2.12 Warnings Regarding use of Schneider Electric Products

Schneider Electric products are not designed with components and testing for a level of reliability
suitable for use in connection with surgical implants or as critical components in any life support
systems whose failure to perform can reasonably be expected to cause significant injuries to a
human.
In any application, including the above reliability of operation of the software products can be
impaired by adverse factors, including - but not limited - to fluctuations in electrical power supply,
computer hardware malfunctions, computer operating system, software fitness, fitness of
compilers and development software used to develop an application, installation errors, software
and hardware compatibility problems, malfunctions or failures of electronic monitoring or control
devices, transient failures of electronic systems (hardware and/or software), unanticipated uses
or misuses, or errors from the user or applications designer (adverse factors such as these are
collectively termed "System failures").
Any application where a system failure would create a risk of harm to property or persons
(including the risk of bodily injuries and death) should not be reliant solely upon one form of
electronic system due to the risk of system failure to avoid damage, injury or death, the user or
application designer must take reasonably steps to protect against system failure, including - but
not limited - to back-up or shut-down mechanisms, not because end-user system is customized
and differs from Schneider Electric testing platforms but also a user or application designer may
use Schneider Electric products in combination with other products. These actions cannot be
evaluated or contemplated by Schneider Electric; Thus, the user or application designer is
ultimately responsible for verifying and validating the suitability of Schneider Electric products
whenever they are incorporated in a system or application, even without limitation of the
appropriate design, process and safety levels of such system or application.
74 C264/EN UM/E50.5
MiCOM C264 - User Manual 3 Technical Data
3 Technical Data
3.1 Firmware technical data 76

3.1.1 MiCOM C264: Elements limits 76
3.1.2 MiCOM C264 with two extension racks with IED 78
3.2 Current transformer compatibility with MiCOM C264P 83
3.2.1 Introduction to current transformers 88
3.2.1.1 Current transformer magnetization 89
3.2.1.2 Limiting secondary voltage (Vk) 89
3.2.1.3 Rated accuracy limit factor 89
3.2.1.4 Primary winding current rating 90
3.2.1.5 Secondary winding current rating 90
3.2.2 Current Transformer Standards and Classes 90
3.2.2.1 Types 90
3.2.2.2 IEC 60044-1 standard 91
3.2.2.2.1 Class P CTs 91
3.2.2.2.2 Class PX 91
3.2.2.3 IEC 60044-6 standard 92
3.2.2.3.1 Class TPS 92
3.2.2.3.2 Class TPX 92
3.2.2.3.3 Class TPY 92
3.2.2.3.4 Class TPZ 93
3.2.3 Current transformer requirements for MiCOM C264P 93
3.2.3.1 Protection 93
3.2.4 Appendix A: Converting to a Limiting Secondary Voltage 95
3.2.5 Appendix B: Converting to IEEE Standard Voltage Rating 96
3.2.6 Appendix C: Use of METROSIL Non-linear Resistors 97
C264/EN UM/E50.5 75
3 Technical Data MiCOM C264 - User Manual
3.1 Firmware technical data

The full performance of the MiCOM C264 is less than the sum of the performances for each
component.
3.1.1 MiCOM C264: Elements limits
Limits for one MiCOM C264 with its

Element
extension racks
Number of IEC 61850 servers for
32
aMiCOM C264 client
Number of IEC 61850 clients for a
16
MiCOM C264 server
128 binary inputs per goose
GOOSE size (IEC 61850)
64 measurements per goose
Measurements / Wired MV 2400 / 48
Receiving flux of MV 200 values / sec
4
IEC 60870-5-104 server protocols with 4 client managed by each
only 1 is active at one time
2
IEC 60870-5-101 protocol
with 1 client managed by each.
2
MODBUS protocol
with 1 client managed by each
4
IEC 60870-5-104 protocol
with 4 clients managed by each
2
DNP3 serial protocol
4
DNP3 over IP protocol
2000 datapoints
140 logical schemes
Custom logic (PSL/FBD equations) 800 logical gates
200 flip-flops
100 overall timers and 12 accurate timers

Printers at MiCOM C264 level 1 (only on rear RS port)
Serial Communication port (for SCADA and/or
4
legacy protocols)
76 C264/EN UM/E50.5

Element
extension racks
Serial/Ethernet: 2
SCADA protocols
Ethernet IEC 104, T104: 4
Master legacy protocols (for IED
4
communication)
IEDs allowed for each Legacy Bus 16 with a max of 64 per MiCOM C264
Voltage level 2 per MiCOM C264 if ATCC used
128
Bays
Up to 12 bays shown on the local HMI
Circuit breakers 128
Disconnectors 512
Transformers 128
managed datapoints (server) 4000
Input status datapoints (Single Point Status ,
Double Point Status , Multiple Point Status) 5600
(server and client)
Output control datapoints (Single Point Control
, Double Point Control) 1200
(server and client)
Tap Position Indicator
128
(server and client)
Measurements
2400
(server and client)
Counter
128, 8 wired
(server and client)
Setpoint
256
(server and client)
512 Single Point Status / Double Point Status
512 Multiple Point Status
512 Measurement Value
Slow programmable automation (ISaGRAF) 128 Tap Position Indicator
128 Counter
256 Single Point Control / Double Point Control
256 Set Point
C264/EN UM/E50.5 77

Element
extension racks
Time discrimination and tagging of events 1 ms
100 alarms / s
Input Bandwidth
100 events /s
480 cycles for 8 analogue values
Fast waveform (disturbance) file storage
+ 128 logical status
capacity
32 samples/period
3.1.2 MiCOM C264 with two extension racks with IED
The MiCOM C264 connects through Ethernet Port 1 to the SBUS and uses protocol IEC 61850
The MiCOM C264 connects through Ethernet Port 2 to the two extension racks
Each extension rack connects through the LBUS to the IEDs
Each MiCOM C264 includes a CPU board.
The full performance of the MiCOM C264 is less than the sum of the performances for each
component.
Global Limits for the MiCOM C264 connected to the two extension racks and to the IEDs:
Element Maximum Number (NB) Limits

Including the system BI
BI Total 2800
(approximately 500 )
2800 minus wired DI, minus system
DI IED
BI
SP 256
TPI 128
Command 1200
CT Total:
Total maximum 128
wired+IED
16 CT at 20 Hz for each extension
rack Total frequency for the 16 counters is
CT wired
8 CT at 20 Hz for the MAIN rack 160 Hz
128 CT for a full MiCOM C264
CT IED 128
78 C264/EN UM/E50.5

AI TOTAL 600
Wired DI & AI limits of the hardware
AI IED 600
If you have 4 or more extension
Extension racks 16 racks, make sure that the MAIN rack
has no I/O boards.
More than for a MiCOM C264 with no
extension rack. For the best
IED Total 128
performance, we recommend a
maximum of 10 IEDs for each link.
Including wired DI, IED DI, system BI
State / bay 2300
& MPS
Including wired AI, IED AI, TPI and
Analogue bay 221
counter
Command / bay 430 Including CO and SP
10 digital inputs per rack change
Sending of BI state 12 times in 10 s (16 * 10 * 12 =
1920 status changes in 10 s)
1 change of value of all
Sending of
measurements in 1 second ( at same Read cycle of wired AI = 1 second
measurement
time than previous status changes)
C264/EN UM/E50.5 79
Limits for the MiCOM C264 MAIN Rack

BI Total 5600 Including the system BI
Wired DI limits of the hardware
DI IED
5300
IEC 61850
SP 256
TPI 128
Command 1200
CT Total 8 CT at 20 Hz
AI TOTAL 600
Wired AI limits of the hardware
AI IED 600
Extension racks 16 racks, make sure that the MAIN rack
has no I/O boards.
DIU 15
DOU 15
CCU 15
AIU 6
CT/VT 1
AOU 4
serial lines 4
Serial/Ethernet: 2
SCADA
Ethernet IEC 104, T104: 4
IED Total 0
Including wired DI, IED DI, system BI
State / bay 2300
and MPS
Including wired AI, IED AI, TPI and
Analogue bay 221
counter
Command / bay 430 Including CO and SP
1 (EPAS 128 xPS per GOOSE
GOOSE Tx version < 5.2.7) 64 MV per GOOSE
4 1521 bytes per GOOSE frame
128 128 xPS per GOOSE

GOOSE Rx 64 MV per GOOSE
1521 bytes per GOOSE frame
80 C264/EN UM/E50.5

For example:
PSL 256 items (see NOTE (1))
256 elements (see NOTE (2))
128 TPI
256 CO
256 SP
Isagraf 512 CT
512 MPS
512 MV
512 SPS / DPS
NOTE: (1) Item: for the interlock / PSL, an item is the output of an Interlock / PSL, or an
intermediate variable used as an output (such as for the TON/TOFF/SR latch operators). In an
interlock equation, an interlock output is equal to one item.
NOTE: (2) Element: After the decomposition of the equation into the sum of multiplications, an
element is the operand of an operator.
C264/EN UM/E50.5 81
Limits for the Extension Racks:

General BLANK racks, make sure that the MAIN rack
has no I/O boards
Wired DI limits of the hardware
DI IED 1000
SP 128
TPI 128
Command 1200
CT Total 128
16 CT at 20 Hz for each extension
rack Total frequency for the 16 counters is
CT wired
8 CT at 20 Hz for the MAIN 1 rack 160 Hz
128 CT for a full MiCOM C264
CT IED 128
AI TOTAL 600
Wired AI limits of the hardware
AI IED 600
DIU 15
DOU 15
CCU 15
CT/VT 0
AIU 6
AOU 4
serial lines 4
SCADA 0
For the best performance, we
IED 64 recommend a maximum of 10 IEDs
for each link
82 C264/EN UM/E50.5
3.2 Current transformer compatibility with MiCOM C264P
The following abbreviations are used in this section:
Symbol Description
ALF Accuracy Limit Factor
ANSI American National Standards Institute
C IEEE standard C57.13 "C" classification
CT Current Transformer
DIN Deutsches Institut für Normung (German standards body)
DT Definite Time
E/F Earth Fault
IDMT Inverse Definite Minimum Time
IEC International Electrotechnical Commission
IEEE Institute of Electrical and Electronics Engineers
MCB Mini Circuit Breaker
Metrosil Brand of non-linear resistor produced by M&I Materials Ltd.
O/C Overcurrent
ph Phase
REF Restricted Earth Fault
rms Root mean square
SEF Sensitive Earth Fault
SIR Source Impedance Ratio
VA Current transformer rated burden
VT Voltage Transformer
C264/EN UM/E50.5 83
The following terms are used in the equations in this section:
Symbol Description Units

As well as the usual “less
< than”, this symbol also depicts N/A
undercurrent
As well as the usual “greater
> than”, this symbol also depicts N/A
overcurrent
system angular frequency rad
Minimum required operating

Hz
frequency
Minimum required operating

Hz
frequency
Nominal operating frequency Hz
Maximum internal secondary

fault current (may also be A
expressed as a multiple of In)
Second stage current setting

of short circuit element In
(overcurrent)
Current setting of first stage

A
biased differential
Maximum secondary through

A
fault current
Maximum secondary fault

A
current (same for all feeders)
Maximum secondary
contribution from a feeder to A
an internal fault
84 C264/EN UM/E50.5
Maximum secondary phase

fault current at Zone 1 reach A
point
Maximum secondary through

A
fault earth current
Maximum secondary earth

fault current at Zone 1 reach A
point
Maximum prospective
secondary earth fault current
A
or 31 x I> setting (whichever is
lowest)
Maximum prospective
secondary phase fault current
A
or 31 x I> setting (whichever is
lowest)
Current transformer nominal

A
secondary current
Earth fault current setting A
Second knee-point bias

current threshold setting of
A
P63x biased differential
element
Reference current of P63x

calculated from the reference A
power and nominal voltage
Value of stabilizing current A
Differential current pick-up

setting of biased differential A
element
C264/EN UM/E50.5 85
Bias current threshold setting

A
of biased differential element
Rated secondary current (I

A
secondary nominal)
Stage 2 and 3 setting A
Motor start up current referred

A
to CT secondary side
Dimensioning factor None
Lower bias slope setting of

%
biased differential element
Higher bias slope setting of

%
biased differential element
Dimensioning factor for earth

None
fault
Maximum dimensioning factor None
Dimensioning factor for reach

None
point accuracy
Dimensioning factor
dependent upon through fault None
current
Short circuit current coefficient

None
or ALF
Dimensioning factor
dependent upon operating None
time
86 C264/EN UM/E50.5

Lower bias slope setting of
P63x biased differential None
element
Higher bias slope setting of
P63x biased differential None
element
Rotating plant rated single

W
phase power
Secondary winding resistance W
Resistance of single lead from

W
relay to current transformer
Resistance of any other

protective relays sharing the W
current transformer
Resistance of relay neutral

W
current input at 30In
Resistance of relay phase

W
current input at 30In
Value of stabilizing resistor W
Duration of first current flow

s
during auto-reclose cycle
Primary system time constant s
Auto-reclose dead time s
Current differential operating

s
time
C264/EN UM/E50.5 87
Secondary system time

s
constant
Theoretical maximum voltage

produced if CT saturation did V
not occur
Input voltage e.g. to an opto-

V
input
Nominal voltage V
Required CT knee-point
V
voltage
Value of stabilizing voltage V
Primary system
None
reactance/resistance ratio
Primary system
reactance/resistance ratio for None
earth loop
Transformer reactance (per

p.u.
unit)
3.2.1 Introduction to current transformers

The role of current transformers in the transmission and distribution of electrical energy is
extremely important. They are used to enable accurate metering and effective protection of
transmission and distribution circuits.
Current transformers isolate the secondary circuits, which are used for relaying and metering,
from the primary circuit, which carries the power. They also provide quantities in the secondary
which are proportional to those in the primary. The role of current transformers in protective
relaying is not as specific as for metering and instrumentation. The role of a measuring
88 C264/EN UM/E50.5
transformer is to deliver from its secondary winding a voltage or current waveform that accurately
represents that of the primary side. The role of a protecting transformer, however, varies
depending on the type of protection it is designed to offer.
There is no major difference between a protective voltage transformer and a measuring voltage
transformer, the difference being only in the nature of the voltage transformed. Normally the
same transformer can serve both purposes. This cannot be said for current transformers,
however, as the requirements for protective current transformers are often radically different from
those of measuring current transformers. Occasionally the same transformer may serve both
purposes but in modern practice this is rare. The main difference is that a measuring current
transformer must be accurate over the normal range of load currents, whereas a protective
current transformer must be capable of providing an adequate output over a wide range of fault
conditions, from a fraction of full load to many times full load.
3.2.1.1 Current transformer magnetization

The primary current contains two components:
1. The secondary current referred to the primary
2. The excitation current, which supplies the core magnetization, eddy currents and hysteresis
losses.
The excitation current flows in the primary winding only and is therefore the cause of transformer
errors. The amount of excitation current drawn by a current transformer depends on the core
material and the amount of flux that must be developed in the core to satisfy the burden
requirements of the current transformer.
It is, therefore, not sufficient to assume a value of secondary current and to work backwards to
determine the value of primary current by using the constant ampere-turns rule, since this
approach does not take into account the excitation current. When the core saturates, a
disproportionate amount of primary current is required to magnetize the core and the secondary
current does not accurately reflect the primary current.
3.2.1.2 Limiting secondary voltage (Vk)

IEC 60044-6 defines the limiting secondary voltage of the excitation characteristic as the point at
which a 10% increase in secondary voltage requires a 50% increase in excitation current. This is
also commonly referred to as the knee-point voltage. The knee-point may be regarded as the
practical limit beyond which a specified current ratio may not be maintained, as the current
transformer enters saturation. Since the shunt admittance is not linear in this region, both the
excitation and secondary currents depart from their sinusoidal form. ANSI and IEEE have a
different definition of the knee-point voltage.
3.2.1.3 Rated accuracy limit factor

A current transformer is designed to maintain its ratio within specified limits up to a certain value of
primary current, expressed as a multiple of its rated primary current. This multiple is known as the
current transformer’s rated accuracy limit factor (ALF).
C264/EN UM/E50.5 89
3.2.1.4 Primary winding current rating

The current transformer primary rating is usually chosen to be equal to or greater than the normal
full load current of the protected circuit. This avoids overloading and consequent overheating of
the CT. Standard primary ratings are specified in IEC 60044-1. The maximum ratio of current
transformers is typically limited to 3000:1 for two reasons:
1. Size limitation of the current transformer
2. Maximum safe open circuit voltage
Some transformers, like large turbo alternators, have very high primary ratings (e.g. 5000A). In
such cases it is standard practice to use a cascade arrangement. For example a 5000:20A in
series with a 20:1A interposing auxiliary current transformer.
3.2.1.5 Secondary winding current rating

The total secondary burden of a current transformer includes the internal impedance of the
secondary winding, the impedance of the connected instruments and relays and the impedance
of the secondary leads. A typical value of rated secondary current is 5A, provided that the length
of the leads between the current transformers and the connected apparatus does not exceed 25
meters. Up to this length the lead resistance is small in relation to the total output of the
transformer. In installations with longer lead lengths, transformers with 1A secondary windings
are used to keep the lead losses within reasonable limits. Power losses vary as the square of the
current, thus losses in 1A windings are 1/25th of losses in 5A windings.
3.2.2 Current Transformer Standards and Classes

3.2.2.1 Types
Generally, there are three different types of CT:
1. High-remanence
2. Low-remanence
3. Non-remanence
Remanence is the magnetization left behind in a medium after an external magnetic field is
removed. In our case, the amount of residual magnetization left in the core.
High-remanence CT
The high-remanence type has no given limit for the remanent flux. The CT has a magnetic core
without any air gaps and the remanent flux is very high. The remanent flux can be up to 70-80%
of the saturation flux. Examples of high-remanent type CTs are:
• IEC 60044-1 classes P, PX
• IEC 60044-6 classes TPS and TPX
Low-remanence CT
The low-remanence type has a specified limit for the remanent flux. The magnetic core is
provided with small air gaps to reduce the remanent flux to a level that does not exceed 10% of
the saturation flux. Examples of low-remanent type CTs are:
90 C264/EN UM/E50.5
• IEC 60044-1 class PR
• IEC 60044-6 class TPY
Non-remanence CT
The non-remanence type has a negligible level of remanent flux. The magnetic core has
relatively large air gaps, which reduce the remanent flux to practically zero level. An example of a
non-remanent type CT is:
• IEC 60044-6 class TPZ
IEC 60044-1 and IEEE C57.13 specify the behavior of inductive current transformers for steady
state symmetrical AC currents. The more recent standard IEC 60044-6 specifies the
performance of inductive current transformers (classes TPX, TPY and TPZ) for currents
containing exponentially decaying DC components.
3.2.2.2 IEC 60044-1 standard

The IEC 60044-1 standard defines class P and class PX current transformers.
3.2.2.2.1 Class P CTs

Class P CTs are high remanence types, typically used for general applications, such as
overcurrent protection. What happens after the relay has been tripped is of no consequence, so
there is no point in having a secondary accuracy limit greatly in excess of the value needed to
cause relay operation. A rated accuracy limit of 5 is therefore usually adequate (Secondary
current accurately reflects primary current for primary currents of 5 times greater than its rating).
When relays (such as instantaneous ‘high set’ overcurrent relays) are set to operate at high
values of overcurrent (say 5 to 15 times the rated current of the transformer), the accuracy limit
factor must be at least as high as the value of the setting current used in order to ensure fast relay
operation.
Rated output burdens higher than 15VA and rated accuracy limit factors higher than 10 are not
recommended for general purposes. It is possible, however, to combine a higher rated accuracy
limit factor with a lower rated output and vice versa. When the product of these two exceeds 150,
the resulting current transformer may be uneconomical or unduly large.
Class P CTs are defined such that the current, phase and composite errors do not exceed the
values given in the table below, at the rated frequency and burden.
Composite Error at
Current Error at Rated Phase Displacement at
Accuracy Class Rated Accuracy Limit
Primary Current Rated Primary Current
Primary Current
±60 minutes (±0.018
5P ±1% 5%
radians)
±60 minutes (±0.018
10P ±3% 10%
radians)
3.2.2.2.2 Class PX
Class PX CTs are typically used for high impedance circulating current protection. They are also
suitable for most other protection applications.
C264/EN UM/E50.5 91
Class PX CTs have high remanence and low leakage reactance. To assess their performance in
relation to the protective relay system in which they are to be used, you only need knowledge of:
• the transformer secondary excitation characteristic
• the secondary winding resistance
• the secondary burden resistance
• the turns ratio
Class PX is the IEC 60044-1 definition for quasi-transient current transformers, formerly covered
by BS 3938 class X.
3.2.2.3 IEC 60044-6 standard

The IEC 60044-6 standard defines current transformers in the classes TPS, TPX, TPY and TPZ.
3.2.2.3.1 Class TPS

Class TPS CTs are high remanence types. They are typically used for high impedance circulating
current protection, and are generally applied to unit systems where the balancing of outputs from
each end of the protected plant is vital.
This balance, or stability during through-fault conditions, is essentially of a transient nature and
thus the extent of the unsaturated (or linear) zones is of paramount importance. Using heavy
current test results, it is normal to derive a formula stating the lowest permissible value of Vk for
stable operation to be guaranteed.
IEC 60044-6 defines the performance of low secondary reactance, TPS class current
transformers for transient performance. They are specified in terms of each of the following
characteristics:
• Rated primary current
• Turns ratio (the error in turns ratio cannot exceed ±0.25%)
• Secondary limiting voltage
• Resistance of secondary winding
3.2.2.3.2 Class TPX

The basic characteristics for class TPX current transformers are generally similar to those of class
TPS current transformers except for the different error limits prescribed and possible influencing
effects which may necessitate a physically larger construction. Class TPX CTs have no air gaps
in the core and therefore a high remanence factor (70-80% remanent flux). The accuracy limit is
defined by the peak instantaneous error during the specified transient duty cycle.
Class TPX CTs are typically used for line protection.
3.2.2.3.3 Class TPY

Class TPY CTs have a specified limit for the remanent flux. The magnetic core is provided with
small air gaps to reduce the remanent flux to a level that does not exceed 10% of the saturation
flux. They have a higher error in current measurement than TPX during unsaturated operation
and the accuracy limit is defined by peak instantaneous error during the specified transient duty
cycle.
Class TPY CTs are typically used for line protection with auto-reclose function.
92 C264/EN UM/E50.5
3.2.2.3.4 Class TPZ

For class TPZ CTs the remanent flux is negligible due to large air gaps in the core. These air gaps
also minimize the influence of the DC component from the primary fault current, but reduce the
measuring accuracy in the unsaturated (linear) region of operation. The accuracy limit is defined
by the peak instantaneous alternating current component error during a single excitation, with
maximum DC offset at a specified secondary loop time constant.
Class TPZ CTs are typically used for special applications such as differential protection of large
generators.
3.2.3 Current transformer requirements for MiCOM C264P

The current transformer requirements are based on a maximum fault current of 40 x In and the
relay having an instantaneous setting of 20 x In. These CT requirements are designed to provide
operation of all protection elements.
Accuracy Limit Limiting Lead

Nominal Rating Nominal Output Accuracy Class
Factor (ALF) Resistance
1A 2.5VA 10P* 20 1.30W
5A 7.5VA 10P* 20 0.11W
NOTE: If a better accuracy than 10P20 is requested, the internal MiCOM C264P CT inputs are
able to support CT : 5P20 .
Where the criteria (for a specific application) are in excess of those detailed above, or the actual
lead resistance exceeds the limiting values, the CT requirements may need to be increased
according to the formulae in the following sections. For specific applications such as SEF, refer to
the sections below for CT accuracy class and knee-point voltage requirements as appropriate.
3.2.3.1 Protection
Protection type Knee-point voltage

Non-directional/directional DT/IDMT overcurrent and earth fault protection
Time-delayed phase overcurrent
Time-delayed earth fault overcurrent
Non-directional instantaneous overcurrent and earth fault protection
Instantaneous phase overcurrent
C264/EN UM/E50.5 93
Instantaneous earth fault overcurrent
Directional instantaneous overcurrent and earth fault protection
Instantaneous phase overcurrent
Instantaneous earth fault overcurrent
Non-directional/directional DT/IDMT SEF protection - residual CT connection
Non-directional time delayed SEF
Directional time delayed SEF
Non-directional instantaneous SEF
Directional instantaneous SEF
Non-directional/directional DT/IDMT SEF protection - core-balance CT connection
Core-balance current transformers of metering class accuracy are required and should
have a limiting secondary voltage satisfying the formulae given below:
Non-directional time delayed SEF
Directional time delayed SEF
94 C264/EN UM/E50.5
Non-directional instantaneous SEF
Directional instantaneous SEF
3.2.4 Appendix A: Converting to a Limiting Secondary Voltage

The suitability of a standard protection current transformer can be checked against the limiting
secondary voltage requirements, specified in this document.
An estimated limiting secondary voltage can be obtained as follows:
If Rct is not available, then the second term in the above equation can be ignored as it typically
only adds a small amount to the estimated secondary limiting voltage.
To ensure that the current transformer has a high enough rating for the relay’s burden it is
necessary to work out the current transformer’s continuous VA rating using the following formula:
Example 1:
An estimate of the secondary limiting voltage of a 400/5A current transformer of class 5P 10 with a
rated output burden of 15VA and a secondary winding resistance of 0.2Ω will be:
Example 2:
For a particular application of a 1A MiCOM overcurrent relay it is required to determine the most
appropriate class P current transformer to be used. The secondary limiting voltage required has
been calculated at 87.3V using a current transformer secondary winding resistance of 2Ω.
The current transformer rated output burden must be:
C264/EN UM/E50.5 95
= 1.025VA
The nearest rating above this will be 2.5VA.
The accuracy limit factor required can be determined by:
The nearest accuracy limit factor above 19.4 is 20.
Therefore the current transformer required to supply the MiCOM overcurrent relay will be a 2.5VA
10P 20. (i.e. 2.5VA is the rated burden, 10 (%) is the nominal accuracy class, 20 is the ALF).
3.2.5 Appendix B: Converting to IEEE Standard Voltage Rating

The MiCOM C264P are compatible with ANSI/IEEE CTs as specified in the IEEE C57.13
standard. The applicable class for protection is class "C", which specifies a non air-gapped core.
The CT design is identical to IEC class P but the rating is specified differently.
The IEEE C class standard voltage rating required will be lower than an IEC knee-point voltage.
This is because the IEEE voltage rating is defined in terms of useful output voltage at the
terminals of the CT, whereas the IEC knee-point voltage includes the voltage drop across the
internal resistance of the CT secondary winding added to the useful output. The IEC knee-point is
also typically 5% higher than the IEEE knee-point.
Where IEEE standards are used to specify CTs, the C class voltage rating can be checked to
determine the equivalent knee-point voltage (Vk) according to IEC. The equivalence formula is:
96 C264/EN UM/E50.5
NOTE: IEEE CTs are always 5A secondary rated, i.e. In =5A, and are defined with an accuracy
limit factor of 20, i.e. Kssc =20.
The following table allows C57.13 ratings to be converted to a typical IEC knee-point voltage:
CT Ratio Rct* Vk - C50 Vk - C100 Vk - C200 Vk-- C400 Vk - C800

100/5 0.04W 56.5V 109V 214V 424V 844V
200/5 0.08W 60.5V 113V 218V 428V 848V
400/5 0.16W 68.5V 121V 226V 436V 856V
800/5 0.32W 84.5V 137V 242V 452V 872V
1000/5 0.40W 92.5V 145V 250V 460V 880V
1500/5 0.60W 112.5V 165V 270V 480V 900V
2000/5 0.80W 132.5V 185V 290V 500V 920V
3000/5 1.20W 172.5V 225V 330V 540V 960V
* Assuming 0.002 ohms per turn typical secondary winding resistance for 5A CTs.
3.2.6 Appendix C: Use of METROSIL Non-linear Resistors

“Metrosils” (non-linear resistors) are used to limit the peak voltage developed by the current
transformers under internal fault conditions, to a value below the insulation level of the current
transformers, relay and interconnecting leads, which are normally able to withstand 3000V peak.
The following formulae should be used to estimate the peak transient voltage (Vp) that could be
produced for an internal fault. The peak voltage produced during an internal fault will be a
function of the current transformer knee-point voltage and the prospective voltage (Vf) that would
be produced for an internal fault if current transformer saturation did not occur.
When the value given by the formulae is greater than 3000V peak, Metrosils should be applied.
They are connected across the relay circuit and serve the purpose of shunting the secondary
current output of the current transformer from the relay in order to prevent very high secondary
voltages.
Metrosils are externally mounted and take the form of annular discs. Their operating
characteristics follow the expression:
with:
C264/EN UM/E50.5 97
V = Instantaneous voltage applied to the Metrosil
C = Characteristic constant of the Metrosil
I = Instantaneous current through the Metrosil
With a sinusoidal voltage applied across the Metrosil, the rms current would be approximately
0.52 times the peak current. This current value can be calculated as follows:
Where
Vsin(rms) = rms value of the sinusoidal voltage applied across the Metrosil.
This is due to the fact that the current waveform through the metrosil is not sinusoidal but
appreciably distorted.
For satisfactory application of a Metrosil, it's characteristic should be such that it complies with the
following requirements:
At the relay voltage setting, the Metrosil current should be as low as possible, and no greater than
» 30mA rms for 1A CTs and » 100mA rms for 5A CTs.
At the maximum secondary current, the Metrosil should limit the voltage to 1500V rms or 2120V
peak for 0.25s. At higher relay voltage settings, it is not always possible to limit the fault voltage to
1500V rms, so higher fault voltages may have to be tolerated.
The following tables show the typical Metrosil types that will be required, depending on relay
current rating, REF voltage setting etc.
Metrosil units for relays using 1A CTs
The Metrosil units for 1A CTs have been designed to comply with the following restrictions:
At the relay voltage setting, the Metrosil current should be less than 30mA rms.
At the maximum secondary internal fault current the Metrosil should limit the voltage to 1500V rms
if possible.
The Metrosil units normally recommended for use with 1A CTs are as shown in the following
table:
Nominal Characteristic Recommended Metrosil Type

Relay Voltage
Single Pole
Setting C b Triple Pole Relay
Relay
Up to 125V rms 450 0.25 600A/S1/S256 600A/S3/1/S802
125 - 300V rms 900 0.25 600A/S1/S1088 600A/S3/1/S1195
98 C264/EN UM/E50.5
NOTE: Single pole Metrosil units are normally supplied without mounting brackets unless
otherwise specified by the customer.
Metrosil units for relays using 5A CTs
These Metrosil units have been designed to comply with the following requirements:
At the relay voltage setting, the Metrosil current should be less than 100mA rms (the actual
maximum currents passed by the units is shown below their type description).
At the maximum secondary internal fault current the Metrosil unit should limit the voltage to 1500V
rms for 0.25s. At the higher relay settings, it is not possible to limit the fault voltage to 1500V rms
hence higher fault voltages have to be tolerated (indicated by *, **, ***).
The Metrosil units normally recommended for use with 5A CTs and single pole relays are as
shown in the following table:
Secondary Recommended Metrosil Type

Internal
Relay Voltage Setting
Fault
Current Up to 200V rms 250V rms 275V rms 300V rms
600A/S1/S1213 C 600A/S1/S1214 600A/S1/S1214 C 600A/S1/S1223 C

50A rms = 540/640 C = 670/800 = 670/800 50mA = 740/870*
35mA rms 40mA rms rms 50mA rms
600A/S2/P/S1217 600A/S2/P/S1215 600A/S2/P/S1215 600A/S2/P/S1196
100A rms C = 470/540 70mA C = 570/670 C = 570/670 C = 620/740*
rms 75mA rms 100mA rms 100mA rms
600A/S3/P/S1219 600A/S3/P/S1220 600A/S3/P/S1221C 600A/S3/P/S1222C
150A rms C = 430/500 C = 520/620 = 570/670** 100mA = 620/740***
100mA rms 100mA rms rms 100mA rms
* 2400V peak, ** 2200V peak, *** 2600V peak
In some situations single disc assemblies may be acceptable. Metrosil units for higher relay
voltage settings and fault currents can also be supplied if required. Contact Schneider Electric for
detailed applications.
NOTE: The Metrosil unit recommended for use with 5A CTs can also be applied for use with
triple pole relays and consist of three single pole units mounted on the same central stud but
electrically insulated from each other. To order these units please specify "Triple pole Metrosil
type", followed by the single pole type reference.
C264/EN UM/E50.5 99
4 Functional Description MiCOM C264 - User Manual
4 Functional Description
4.1 MiCOM C264 management 111

4.1.1 Operating mode management 111
4.1.1.1 Initialization mode 111
4.1.1.2 Operational mode 112
4.1.1.2.1 Normal mode 112
4.1.1.2.2 Downgraded mode 113
4.1.1.3 Maintenance mode 113
4.1.1.4 Simul mode and DSPIO Maintenance Mode 114
4.1.1.5 Test mode 116
4.1.1.6 Faulty mode 117
4.1.1.7 Halt mode 117
4.1.1.8 Summary of modes, tests, transitions, and faults 117
4.1.1.9 Redundancy Mode management 118
4.1.2 Database management 121
4.1.2.1 General 121
4.1.2.2 How to upload a database through ethernet 123
4.1.2.3 How to switch the databases 123
4.1.2.4 How to do a check of the database 124
4.1.2.5 How to modify the database 124
4.1.2.6 How to modify a parameter setting in the current DB 124
4.1.2.7 How to consult a parameter setting in the current DB 124
4.1.3 Self-tests 125
4.1.4 Time management 125
4.1.4.1 External clock 126
4.1.4.2 Clock synchronization message from a SCADA gateway 127
4.1.4.3 SNTP Client and Servers 127
4.1.4.4 Time set by an operator 128
4.1.4.5 Local clock update 128
4.1.4.6 Management of loss of external time reference 129
4.1.4.7 Update method 129
4.1.4.8 Limits and performances 130
4.1.4.9 Precision Time Protocol 1588 130
4.1.4.9.1 Performance and limits 136
4.2 Communications 137
4.2.1 Telecontrol bus - TBUS 137
4.2.2 Legacy bus - LBUS 138
4.2.3 Station bus - SBUS 139
4.2.3.1 Exchanges 139
4.2.3.2 IEC 61850 compliances 140
4.2.3.3 Controls 140
100 C264/EN UM/E50.5

MiCOM C264 - User Manual 4 Functional Description
4.2.4 Inter-rack Ethernet communication 140

4.2.4.1 Internal Ethernet architecture 141
4.2.4.2 External network behaviour 141
4.2.4.3 Ethernet failure 143
4.2.4.4 Other Ethernet rupture 144
4.2.4.5 Ethernet Routing table 144
4.2.5 Ethernet port management on CPU275 145
4.2.6 Telecontrol Bus redundancy 146
4.3 Direct process access 148
4.3.1 Input check 148
4.3.2 Output check 148
4.3.3 Time stamping 148
4.3.4 Digital input acquisition (DI) 148
4.3.4.1 DI acquisition 148
4.3.4.2 DI Debouncing and filtering 149
4.3.5 Counter acquisition (CT) 149
4.3.5.1 Single counter (SCT) 150
4.3.5.2 Double counter (DCT) 150
4.3.6 Digital measurement (DM) 151
4.3.6.1 Acquisition without Read inhibit signal 151
4.3.6.2 Acquisition with Read inhibit signal 152
4.3.7 Analogue Input acquisition (AI) 154
4.3.7.1 4.7.1 Input ranges 154
4.3.7.2 4.7.2 Acquisition cycle 154
4.3.8 Digital outputs (DO) 154
4.3.9 Digital Setpoints 154
4.3.9.2 Read Inhibit 155
4.3.10 Analog Setpoints 156
4.3.10.1 Output range 156
4.3.10.2 Output management 156
4.3.10.3 AOU Watchdog management 157
4.4 Data processing 158
4.4.1 Binary input processing 158
4.4.1.1 Binary input definition 158
4.4.1.2 Common processing of Binary Input 158
4.4.1.2.1 Toggling Input 158
4.4.1.2.2 Suppression 159
4.4.1.2.4 Forcing 159
4.4.1.3 Processing of Single Point Status 160
C264/EN UM/E50.5 101

4.4.1.3.1 Persistence filtering 160

4.4.1.3.2 SPS resulting state 161
4.4.1.3.3 Mapping of SPS states on IEC 61850 station bus 162
4.4.1.3.4 DI/DO association for SPS 163
4.4.1.4 Processing of Double Point Status 163
4.4.1.4.1 Motion filtering 164
4.4.1.4.2 DPS persistence filtering 165
4.4.1.4.3 DPS resulting states 166
4.4.1.4.4 Mapping of DPS states on IEC 61850 station bus 167
4.4.1.4.5 DI/DO association for DPS 169
4.4.1.5 Processing of Multiple Point 169
4.4.1.5.1 Multiple Point filtering 169
4.4.1.5.2 MPS resulting state 170
4.4.1.5.3 Mapping of MPS states on IEC 61850 station bus 170
4.4.1.6 System Inputs (SI) 171
4.4.1.7 IED binary inputs 171
4.4.1.8 Group processing 172
4.4.1.9 SBMC Mode Processing 173
4.4.1.10 BI sent to automation features 174
4.4.1.11 Toggling signal detection 174
4.4.1.12 Missing Signaling Voltage (MSV) 174
4.4.2 Measurement Input Processing 175
4.4.2.1 Analogue Measurement Processing 175
4.4.2.1.1 Open circuit management 175
4.4.2.1.2 Scaling 176
4.4.2.1.3 Zero value suppression 176
4.4.2.2 Digital Measurement Processing 177
4.4.2.3 TMU2XX: CT/VT measurement processing 177
4.4.2.3.1 TMU2XX: CT/VT Calculations - General 178
4.4.2.3.2 TMU220: CT/VT Calculations – Inputs Configuration 181
4.4.2.3.3 TMU220: CT /VT Calculations - Inputs: samples 181
4.4.2.3.4 TMU220: CT/VT Calculations – Outputs: set of measurements 182
4.4.2.3.7 TMU220: Algorithms 187
4.4.2.3.8 TMU210: CT/VT Calculations - Inputs: Configuration 190
4.4.2.3.9 TMU210: CT/VT Calculations - Inputs: Samples 190
4.4.2.3.10 TMU210: CT/VT Calculations – Outputs: Set of measurements 191
4.4.2.3.13 TMU210: Algorithms 194
4.4.2.3.14 Treshold detection 203
4.4.2.3.15 Manual suppression 204
102 C264/EN UM/E50.5


4.4.2.3.17 Forcing an invalid measurement 204
4.4.2.3.19.1 Periodic transmission 206
4.4.2.3.19.2 Transmission upon variation 206
4.4.2.3.19.3 Transmission upon trigger 206
4.4.2.3.19.4 Limits and performances 206
4.4.3 Tap Position Indication (TPI) measurement processing 207
4.4.3.1 Acquisition from Digital Inputs 207
4.4.3.2 Acquisition from Analogue Inputs 207
4.4.3.3 Manual suppression 208
4.4.3.4 Substitution 208
4.4.3.5 Forcing an invalid TPI 208
4.4.3.6 Transmission 209
4.4.4 Accumulator Input Processing 209
4.4.5 Energy counting 209
4.4.6 Basic data manipulation 210
4.4.6.1 Simul mode enhancements 210
4.4.6.2 Controls management from PSL 211
4.5 Control sequences 213
4.5.1 Description 213
4.5.1.1 General 213
4.5.1.1.1 Device control configuration 213
4.5.1.1.2 Types of devices 214
4.5.1.2 Control sequence phase management 214
4.5.1.4.1 Selection phase in "SBO once" mode 219
4.5.1.4.2 Execution phase in "SBO once" mode 221
4.5.1.5.1 Selection phase in SBO many mode 222
4.5.1.5.2 Execution phase in SBO many mode 223
4.5.1.5.3 Unselection phase in SBO many mode 224
4.5.1.6 Generic selection checks 225
4.5.1.6.1 Inter-control delay 227
4.5.1.6.3 Substation and bay mode control 227
4.5.1.6.4 Interlock control 227
4.5.1.6.5 Automation running control 227
4.5.1.6.6 Device selectable 228
4.5.1.6.7 Locked device control 228
C264/EN UM/E50.5 103

4.5.1.6.8 Current status of the device 228

4.5.1.6.9 Uniqueness 228
4.5.1.7 Selection behavior 229
4.5.1.8 Generic execution checks 230
4.5.1.9 Execution behavior 230
4.5.1.9.1 Execution via I/O boards 231
4.5.1.9.2 Execution via IED communication 231
4.5.1.9.3 System controls execution 231
4.5.1.10 Controls time sequencing 231
4.5.1.10.1 Direct execute time sequencing 232
4.5.1.10.2 SBO once time sequencing 232
4.5.1.10.3 SBO many time sequencing 234
4.5.1.11 Bay/Module/xPC order running 234
4.5.2 Control of non synchronized breakers 237
4.5.2.1 Non synchronized circuit breaker features 237
4.5.2.2 Control sequence of non synchronized circuit breakers 238
4.5.3 Control of synchronized breakers 238
4.5.3.1 Synchronized circuit breaker features 238
4.5.3.2 Circuit breakers with external synchrocheck 240
4.5.3.2.1 Close CB by external synchrocheck with automatic set on 240
4.5.3.2.2 Close CB by external synchrocheck with manual set on 244
4.5.3.2.3 Close synchronized circuit breakers with forcing 247
4.5.3.2.4 Cancel Close CB with external synchrocheck 248
4.5.3.3 Circuit breakers with internal synchrocheck 249
4.5.3.3.1 Close CB with internal synchrocheck with automatic set on 250
4.5.3.3.2 Close CB with internal synchrocheck with manual set on 255
4.5.3.3.3 Close CB with internal synchrocheck with forcing 256
4.5.4 Control of disconnectors 258
4.5.4.1 Disconnectors features 258
4.5.4.2 Control sequence of disconnectors 258
4.5.5 Control of transformers 258
4.5.5.1 Transformer features 258
4.5.5.2 Control sequence of transformers 259
4.5.5.2.1 Control of transformer with TCIP 259
4.5.5.2.2 Control of transformer without TCIP 261
4.5.5.2.3 Suppression, Forcing or Substitution of the TPI 262
4.5.6 Control of Intelligent Electrical Devices (IED) 262
4.5.6.2.1 Selection phase 263
4.5.6.2.2 Execution phase 263
104 C264/EN UM/E50.5

4.5.7 System controls 263

4.5.8 Kinds of control sequences 264
4.5.9 Control sequences checks 264
4.5.9.1 Mode Management 264
4.5.9.2 IED connected 265
4.5.9.3 Control mode 265
4.5.9.4 Uniqueness of control 265
4.5.9.5 Inter-control delay 265
4.5.9.6 Status of the device 265
4.5.9.7 Locked device 265
4.5.9.8 Running Automation 265
4.5.9.9 Interlocking 266
4.5.10 HV Control Sequences 266
4.5.10.1 Circuit breaker 266
4.5.10.2 Disconnector 266
4.5.10.3 Transformer 266
4.6 Automation 267
4.6.1 Safety information 267
4.6.2 Built-in Automation functions 267
4.6.2.1 Auto-Recloser (AR) 267
4.6.2.2.1 Behavior 268
4.6.2.2.1.1 In Service / Out of service 269
4.6.2.2.1.2 Analysis of the receiving trip 269
4.6.2.2.1.3 Waiting CB opening 270
4.6.2.2.1.4 Launch cycle timer 270
4.6.2.2.1.5 Closing the CB 271
4.6.2.2.1.6 Launch recovering time 271
4.6.2.2.1.7 Particular treatments 271
4.6.2.2.2 Information and parameters 272
4.6.2.3 Trip Circuit Supervision 274
4.6.2.4 Circuit breaker condition monitoring (I²t) 276
4.6.2.4.1 Acquisition and computation 276
4.6.2.4.2 Reset 277
4.6.2.4.3 Monitoring 277
4.6.2.4.4 Inhibition 277
4.6.2.4.5 Storage 277
4.6.2.5 Automatic Voltage Regulation–AVR 278
4.6.2.5.1.1 Role 278
4.6.2.5.1.2 Topologies 278
4.6.2.5.1.3 Modes 278
4.6.2.5.1.4 Interfaces for a single transformer 279
C264/EN UM/E50.5 105

4.6.2.5.1.5 Hardware architecture 279

4.6.2.5.1.6 Exchanges over the bus 280
4.6.2.5.2 Moving a tap changer 280
4.6.2.5.2.1 Actual voltage 280
4.6.2.5.2.3 Regulation 282
4.6.2.5.3 Additional monitoring functions 283
4.6.2.5.3.1 Tap Changer position on Voltage Loss 283
4.6.2.5.3.2 Fast Tap Changer move AFTER Voltage Loss and Voltage recovery 283
4.6.2.5.3.3 Abnormal Voltage signalization 284
4.6.2.5.3.4 Tap Changer Failure supervision – Tap Blocking 284
4.6.2.5.3.5 Tap Changer Lowest / Highest position 285
4.6.2.5.3.6 Run away protection 285
4.6.2.5.3.7 OverVoltage Detection 285
4.6.2.5.3.8 UnderVoltage Detection 286
4.6.2.5.3.9 OverCurrent detection 286
4.6.2.5.3.10 Tap Changer Maintenance: Tap Counting 286
4.6.2.5.4 Line drop compensation 287
4.6.2.5.5 Other functions 288
4.6.2.5.5.1 Additional Measurements (Optional) 288
4.6.2.5.5.2 Raise lower control and voltage target from external signals 288
4.6.2.5.5.3 Reverse Power Flow (RPF) 289
4.6.2.5.6 Transformers in parallel 291
4.6.2.5.6.1 Master Followers method 291
4.6.2.5.6.2 Standalone regulation 292
4.6.2.6 Automatic voltage regulation–ATCC 294
4.6.2.6.1.1 Topologies 294
4.6.2.6.1.2 Situations requiring ATCC 295
4.6.2.6.1.3 Definitions and main attributes 295
4.6.2.6.1.4 Capacity 296
4.6.2.6.1.5 Alarm conditions 296
4.6.2.6.2 Monitoring logic 297
4.6.2.6.2.1 Modes 297
4.6.2.6.2.2 Conditions for an active automatic voltage regulation 297
4.6.2.6.2.3 Transformers status logic 298
4.6.2.6.2.4 Busbars status logic 298
4.6.2.6.2.5 Group status logic 298
4.6.2.6.3 Moving tap changers 299
4.6.2.6.3.2 Voltage is outside of the Target Voltage Deadband 300
4.6.2.6.3.3 Timeouts 301
4.6.2.6.3.4 Homing 303
106 C264/EN UM/E50.5

4.6.2.6.4 Calculation modes for a busbars group 304

4.6.2.7 Synchrocheck 308
4.6.2.7.1 Synchrocheck – General 308
4.6.2.7.2 Synchrocheck Schemes 309
4.6.2.7.3 Synchrocheck Algorithm 310
4.6.2.7.4 Synchrocheck Applications 310
4.6.2.7.5 Synchrocheck Circuit Breaker Closure types 310
4.6.2.7.6 Synchrocheck Type 1 and Type 2 311
4.6.2.7.7 Synchrocheck Hardware constraints and use 311
4.6.2.7.8 Synchrocheck Calculation 311
4.6.2.7.9 Synchrocheck Introduction to Harmonics 311
4.6.2.7.10 Synchrocheck – Check Synchronizing – Locking Mode 312
4.6.2.7.11 Synchrocheck – System Synchronizing – Coupling Mode 312
4.6.2.7.12 Synchrocheck Scheme LL: Live Line, Live Bus: Real Time Sequences 312
4.6.2.7.12.1 Locking allowed / coupling not allowed by configuration 312
4.6.2.7.12.2 Locking allowed / coupling allowed by configuration 313
4.6.2.7.13 Synchrocheck Schema with VLINE and NOT(VBUSBAR) voltage controls 315
4.6.2.7.14 Synchrocheck Schema with NOT(VLINE) and VBUSBAR voltage controls 315
4.6.2.7.15 Synchrocheck Schema with NOT(VLINE) and NOT(VBUSBAR) voltage
control 315
4.6.2.7.16 Synchrocheck Schemes that use VLINE and VBUSBAR voltage control 315
4.6.2.7.16.1 Locking scheme ( synchronous mode ) 315
4.6.2.7.16.2 Coupling scheme ( asynchronous mode ) 316
4.6.2.7.19 Synchrocheck Bypass 318
4.6.2.7.20 Synchrocheck Bypass - Purpose 318
4.6.2.7.21 Synchrocheck Bypass - Functional Description 318
4.6.2.7.22 Phase-to-Phase Synchrocheck with the TMU210 319
4.6.2.7.23 Phase-to-Phase Synchrocheck with the TMU210 - General 319
4.6.2.7.24 Phase-to-Phase Synchrocheck with the TMU210 - Description 321
4.6.2.7.25 Phase-to-Phase Synchrocheck with the TMU210 - Configuration 321
4.6.2.7.26 Synchrocheck Close request 321
4.6.2.7.27 Synchrocheck General Configuration 322
4.6.2.7.28 Synchrocheck Voltage control 322
4.6.2.7.29 Synchrocheck Schemes control 323
4.6.2.7.30 Synchrocheck Parameters of the TMU2xx board 323
4.6.2.7.31 Synchrocheck Internal parameters 323
4.6.2.7.32 Synchrocheck Digital Output (DO) of the circuit breaker 325
4.6.2.7.33 Voltage reference selection and Double busbar configuration 326
4.6.2.8 Fast Load Shedding ( FLS ) 326
4.6.2.9 Synchroscope and Power Synchronizer 326
4.6.2.9.1 General 326
C264/EN UM/E50.5 107

4.6.2.9.1.1 Monitoring 327

4.6.2.9.1.2 Convergence 327
4.6.2.9.1.3 Closing 328
4.6.2.9.1.4 Connection schema 330
4.6.2.9.2 HMI 330
4.6.2.9.2.1 MiCOM C264’s Screens 330
4.6.2.9.2.2 Navigation in MiCOM C264 332
4.6.2.9.3 Main MiCOM C264’s behavior 333
4.6.2.9.4 Error management in MiCOM C264 334
4.6.2.10 MiCOM C264 in eLSU application 334
4.6.2.10.1 Purpose 334
4.6.2.10.2 MiCOM C264 eLSU configuration 335
4.6.2.10.2.1 Shed Reflex 335
4.6.2.10.3 Shed automation 336
4.6.2.10.3.1 Control Type of Shed Automation 337
4.6.2.10.3.2 MiCOM C264 specific configuration for MiCOM C264 eLSU 339
4.6.3 Fast automation: Programmable Scheme Logic (PSL) 340
4.6.3.1 Interlocking equations as particular case of PSL 340
4.6.3.1.1 Introduction 340
4.6.3.1.2 Interlocking bypass 340
4.6.3.1.3 Timer before interlock evaluation 341
4.6.3.1.4 Simulation and test of interlocking equations 341
4.6.3.2 PSL/interlocking inputs 341
4.6.3.3 PSL interlocking outputs 341
4.6.3.4 Functions 341
4.6.3.5 Validity of data 342
4.6.3.6 Computation 342
4.6.4 Slow automation Programmable Logic Control (PLC) 342
4.6.4.1 Inputs 343
4.6.4.2 Outputs 343
4.6.4.3 PLC Behaviour 344
4.6.5 PSL/PLC behavior in case of MiCOM C264 redundancy 345
4.7 Records 346
4.7.1 Permanent records storage 346
4.7.1.1 Data storage 346
4.7.1.2 Waveform Recording: General 346
4.7.1.3 Events 346
4.7.1.4 Fast Waveform Recording 346
4.7.1.5 Slow Waveform Recording 347
4.7.1.6 Slow Waveform Recording – Hypothesis 348
4.7.1.7 Disturbance Recorder 349
4.7.2 Non-permanent data storage of alarm 350
108 C264/EN UM/E50.5

4.7.2.1 Definitions 350

4.7.2.1.1 Definition of an alarm 350
4.7.2.1.2 Types of alarmed data 350
4.7.2.1.3 Alarm states definition 351
4.7.2.1.4 Parameters associated to an alarm 351
4.7.2.2 Alarm processing 352
4.7.2.2.1 Acknowledgment 354
4.7.2.2.2 Clearing 355
4.8 Protection Functions 356
4.8.9 Dir. / Non-dir. Neutral / Ground / Earth OC protection (ANSI code 67N/50N/51N) 365
C264/EN UM/E50.5 109


4.8.15 Extra functions 372
4.8.15.1 Circuit breaker failure (50BF or TCS) 372
4.8.15.1.1 Description of the protection 372
4.8.15.1.2 Characteristics of the protection 372
4.8.15.2.1 Description of the function 372
4.8.15.2.2 Characteristics of the function 372
4.8.15.3 RSE 373
4.9 Protection Curves 374
4.9.1 IDMT Curves 374
4.9.1.1.1 IDMT threshold 374
4.9.1.1.2 Reset timer 375
4.9.1.2 IEC Curves 378
4.9.1.3 RI Curves 384
4.9.1.4 IEEE/ANSI & CO Curves 385
4.9.2 Thermal overload curves 391
4.9.2.2 10.2.2 Tripping curve 392
110 C264/EN UM/E50.5

4.1 MiCOM C264 management

The computer manages its own mode, configuration (Databases), and time.
4.1.1 Operating mode management

The computer operates in the modes that follow:
• Initialization mode
• Operational mode
Normal mode
Downgraded mode
• Simul mode
• Faulty mode
• Halt mode
Computer detected faults include:

• Anomaly: a downgrade in the behavior of the computer. There are hardware and/or software
anomalies, as follows:
Board inoperable
Loss of synchronization
Loss of communication.
• Software error detected: a major software error, that causes the computer to go into the
detected error mode.
• Vital hardware error detected: an error that causes a software halt and causes the computer
to stop the application software. Vital hardware error detected include:
CPU inoperable
Power supply inoperable
Bus inoperative
Permanent interruption
4.1.1.1 Initialization mode

After a power on or a manual reset event occurs, the computer goes into the initialization mode.
The computer performs different types of tests and checks, as follows:
• Vital hardware tests
Flash memory test: in event of a problem, the computer tries to repair this flash memory. If a
vital hardware test fails, the computer goes out of the initialization mode and into the Halt
mode.
• Non-vital hardware tests
The computer performs non-vital hardware tests only on those boards installed in the
computer, and on the peripheral devices connected to the computer:
C264/EN UM/E50.5 111

Input and output boards:
To determine the number and the type of the installed input and output boards;
To do a check for the presence of the previously installed input and output boards and to
determine if a board is absent;
To do a check for the serviceability of the installed input and output boards and to
determine if a board is unserviceable.
Communication boards: the computer performs this test within the communication
protocol;
Displays, such as the LCD and LEDs: the computer does a single test for the presence of
the HMI board;
Peripheral devices, such as the printer, external clock, and so on: the computer uses
timeouts to do a check for the presence of the peripheral devices.
If one of these non-vital hardware tests fails, the computer goes into the related downgraded
mode.
• Software tests (database coherency tests)
At each restart of the computer, the computer performs these database coherency tests.
These tests make sure that the database is compatible with the hardware and with the
software of the computer, and that the database does not contain incoherent configuration
data. The database coherency tests include:
Check for the presence of a database
Check of the DB/ software compatibility
This check makes sure that the computer software and the database are coherent and
compatible. The computer contains in its static data, a database version number and
revision number that indicate which version of the database it can interpret. The database
must have the same version number and revision number for the computer to accept it.
Check of the DB/ equipment compatibility
This check makes sure that the database is compatible with the device on which it was
downloaded. The computer compares the type and the number of the device contained in
the heading of the database, with the type and the number of the device contained in the
static data of the software.
Check of the validity of the data of the database
This check makes sure that the configured inputs and outputs are present and that the
number of devices and signals, such as bays, digital inputs, and so on, stays within
acceptable limits.
If any one of these checks fails, the computer goes into the Maintenance mode.
4.1.1.2 Operational mode

4.1.1.2.1 Normal mode
This is the nominal operating mode of the active computer. In this mode the computer activates
the watchdog relay and all of the computer functions are available. A detection of an error and in
agreement with the cause and the severity of the failure, can cause the computer to go into the
112 C264/EN UM/E50.5

related Downgraded mode, to the Faulty mode or to the Halt mode.
In the Normal mode, you can use the local Human Machine Interface (HMI) or upper level
maintenance request, to request a transition to the Maintenance mode.
In the Normal mode, you can use the local (HMI) or upper level simulation request, to request a
transition to the Simul mode.
In the Normal mode, you can do these database operations:

• Download a standby database,
• Swap the databases: the computer automatically restarts,
• Modify a database,
• Show database information.
The computer transmits the results of the Simul mode to the local HMI and to the upper level
remote control point (RCP).
4.1.1.2.2 Downgraded mode

In event of an anomaly, the computer goes into the Downgraded mode. In this mode, the
operation of the computer is not very disturbed because only few functions are degraded. The
computer activates the watchdog relay.
The type of downgraded mode depends on the hardware configuration of the computer. The
different events that cause a downgraded mode include:
• Operation without DO on a board,
• Operation without DI on a board,
• Operation without AI on a board,
• Operation without communication with some relays,
• Operation without communication with some station-bus devices,
• A combination of two, or more, of these events.
When the operator or the computer resolve the cause of the transition into the Downgraded mode,
the computer returns to the Normal mode.
4.1.1.3 Maintenance mode

In Maintenance mode, the station-bus communication layer is operational, and can be used to
manage the database. The Maintenance mode is shown on the local HMI (LED and LCD) and is
available on the upper level via station-bus communication.
The computer deactivates the watchdog relay.
In this mode, you can manage the database:

• Download a database,
• Swap the databases,
• Modify a database,
• Show database information.
C264/EN UM/E50.5 113

In the Maintenance mode, you can use the local Human Machine Interface (HMI) or upper level
active request, to request a transition to the Operational mode. The Operational mode includes
the Normal mode and the Degraded mode.
4.1.1.4 Simul mode and DSPIO Maintenance Mode

To simulate the function of distributed automatic events, such as interlocks, you request to set the
computer to Simul mode. In Simul mode, the computer operates normally but the output relays
are not active. When you send a command, the computer does not activate the output relay:
instead, if the command is valid, the computer sends a TEST OK message to the substation
control point (SCP). If the command is not valid, the computer sends a TEST NOK message to the
SCP.
NOTE: To perform the tests and create the test conditions, force manually BI or Measurements
on different computers to. When you see the test conditions, you can send a command. Look at
the SCP level (HMI) to see if the result is the expected result.
The Simul mode is shown on the local HMI (LED and LCD) and on the upper level.
In the Simul mode, you can use the local HMI or upper level end-of-simulation request, to request
a transition to the Operational mode. The Operational mode includes the Normal mode and the
Degraded mode.
For MiCOM C264P, the Simul mode puts the embedded DSPIO firmware in DSPIO Maintenance
mode.
The behavior of the CPU and the DSP in agreement with the MiCOM C264P mode shows in the
table that follows. This table is true only if there is no Programmable Scheme Logic (PSL),
managed by the CPU, between the start/operate BI and the DSPIO trip relay.
114 C264/EN UM/E50.5

- Figure 3 - Computer CPU Operating Mode versus Commands Received by the CPU
C264/EN UM/E50.5 115

4.1.1.5 Test mode

To test the IEC communication network, the computer can be switched in test mode, as defined in
IEC 61850 part 7-4. Switching to test mode is done through the front panel of the BCPU.
In test mode, the computer will:

• publish all its outputs with the test quality,
• not execute commands,
• send negative acknowledgment in response to command without the test quality,
• send positive acknowledgment in response to command with the test quality,
• process as valid any data whose quality identifier "Test" is set to "FALSE",
• process as valid any data whose quality identifier "Test" is set to "TRUE",
• process as invalid any data whose quality identifier "Validity" is set to "Invalid".
MODE/BEHAVIOUR On On-blocked Test Test/blocked Off

Function behind LN ON ON ON ON OFF
Output to the Process
(Switchgear) via a non-
IEC 61850 link (for
YES NO YES NO NO
example wire) and digital
outputs of fusion IED (LN
LPDO)
Value is Value is
Value is Value is Value is
relevant relevant
Output of FC ST, MX relevant relevant relevant
Q is Q is
Q=test Q=test Q=invalid
relevant relevant
Response to (Normal) A+ A+ A- A- A-
command from client (a+
/ a- acknowledgment) Pos. ack Pos. ack Pos. ack Pos. ack Pos. ack
Response to Test A- A- A+ A+ A-
command from client (a+
/ a- acknowledgment) Neg. ack Neg. ack Pos. ack Pos. ack Neg. ack
Incoming data with Processed Processed Processed Processed as Not

q=normal as valid as valid as valid valid processed
q=operatorBlocked as blocked as blocked as blocked blocked processed
q=test as invalid as invalid as valid valid processed
q=test+operatorBlocked as invalid as invalid as blocked blocked processed
116 C264/EN UM/E50.5

MODE/BEHAVIOUR On On-blocked Test Test/blocked Off

q=invalid as invalid as invalid as invalid invalid processed
Non IEC 61850 binary
(relay, contact) inputs
Not
and analogue Processed Processed Processed Processed
processed
(instruments
transformers) inputs
All data with the test quality will be treated as valid only by an IED in test mode.
Test mode is shown on the local HMI (LED).
4.1.1.6 Faulty mode

In any mode, when a fault occurs to prevent the proper operation of the software, the computer
goes into the Faulty mode.
When the computer detects a failure on the DO boards, and if the configuration allows, the
computer goes into the Faulty mode. Each time the computer goes into the Faulty mode, an
internal counter increments itself.
There are only two ways to go out of the Faulty mode:

• A transition to the Initialisation mode and an automatic reset of the counter,
• A transition to the Halt mode.
If the value of the internal counter remains lower than the Max_Fault parameter defined during the
configuration step, the computer goes into the Initialisation mode. When the elapsed time since
the last increment of the internal counter equals the value Fault_Detection_Lasting parameter
defined during the configuration step, the value of the counter is reset.
When the value of the internal counter reaches Max_Fault, the computer goes into the Halt mode.
4.1.1.7 Halt mode

In this mode, the computer deactivates the watchdog relay and all the output relays. The
computer does not operate anymore. The only way to go out of this mode is to perform a manual
reset.
4.1.1.8 Summary of modes, tests, transitions, and faults

The different modes, tests, transitions, and faults of the computer show in the figure that follows:
C264/EN UM/E50.5 117

4.1.1.9 Redundancy Mode management
Two identical computers with the same hardware and the same database versions manage the
main 1 rack redundancy.
For the MiCOM C264:
The two redundant computers are the main#1 computer and the main#2 computer. The computer
that performs the bay management is the “active” computer; the other one is the “standby”
computer. In this configuration, the redundant computer can be:
• Main#1 computer in active mode,
• Main#1 computer in standby mode,
118 C264/EN UM/E50.5

• Main#2 computer in active mode,
• Main#2 computer in standby mode.
During the boot time, and if both computers operate, the main#1 computer is the “active”
computer.
The two computers perform the same functions at the same time: inputs acquisition and
processing, archiving, automation. But, at a given time, only the “active” computer sends controls
to the electrical process or on the SBUS. EPAS IEC 61850 client receives data from the two
computers: this client processes only the data it receives from the “active” computer. Only the
“active” computer manages the communication with IED or SCADA.
This switch from the active mode to the standby mode, and from the standby mode to the active
mode, is performed automatically as follows:
- Figure 4 - Redundancy management
The two computers exchange data with:

• The SBUS, to give their internal status (IS),
• 2 pairs of DI/DO of the BIU board:
• DI1/DO1 to indicate the Active Status: DO1 is closed if the computer is Active,
• DI2/DO2 to indicate a Station Bus failure: DO2 is open in event of failure.
A value is given to each type of computer failure: the computer IS is calculated by summing all
failure values. The healthiest computer has the minimal internal status. The healthiest computer is
active.
Computer failure Value

DOU board failure 0x20
CCU board failure 0x10
CT/VT board failure 0x08
DIU board failure 0x04
BIU board failure 0x02
AIU board failure 0x01
The algorithm to elect the Active computer shows in the table that follows.
C264/EN UM/E50.5 119

The initial state is “Initialization” (state 0) and the “DI1¹1” event is generated.
“L_IS” is the internal status of the computer, “R_IS” is the internal status of the redundant one.
The “confirmed DI2 ¹ 1” event is a detection of a Station Bus failure on the other computer (DI2 =
0) confirmed for 20 seconds.
T1 is the timer of Active status confirmation during the computer initialization (default value: 5
seconds for the Main#1 computer, marked in configuration, 30 seconds for the Main#2 computer).
T2 is the timer of master election (default value: 5 seconds).
State 1:
Waiting end State 3: State 5:
State 0: of State 2: Standby / State 4: Standby
Initialization initialization Standby T2 timer Active mode on-
/ T1 timer on on-going going
going
≠ T1 timer ≠ close ≠ stop T2
launching DO1 timer
DI1≠1 / / /
≠ go to state ≠ go to ≠ go to
1 state 4 state 4
≠ open
≠ stop T1 DO1
timer ≠ stop T2 go to state
DI1=1 go to state 2 / /
≠ go to state timer 5
2 ≠ go to
state 2
≠ T2 timer
launching
“confirmed” ≠ close
/ / / / /
DI2≠1 DO1
≠ go to
state 3
If (L_
If (L_IS<R_
IS>R_IS)
IS) then
then
≠ T2 timer
≠ stop T2
launching
Remote IS / / timer / /
≠ close
≠ open
DO1
DO1
≠ go to
≠ go to
state 3
state 2
120 C264/EN UM/E50.5

State 1:
Waiting end State 3: State 5:
State 0: of State 2: Standby / State 4: Standby
Initialization initialization Standby T2 timer Active mode on-
/ T1 timer on on-going going
going
If DI1≠1 then:
≠ T2 timer
launching
End of T1 ≠ close DO1 not not
/ / /
timer ≠ go to state possible possible
3 else:
≠ go to state
2
End of T2 go to state
/ / / / /
timer 4
open DO1 if
conditions
to enter
standby
mode are
End of not true
standby not not not anymore
/ not possible
mode going- possible possible possible then
on ≠ T2 timer
launching
≠ go to
state 3 else
≠ go to
state 2
4.1.2 Database management

4.1.2.1 General
MiCOM C264 uses structured databases to manage data. The main principle is that the computer
will only operate with other EPAS devices if their database versions are identical.
A database (DB) is a file that includes the description of the whole of the electric process, and all
of the devices that the computer is likely to communicate with: IED, HMI, and so on. The database
also includes some parameter settings for the software and for the transmission protocols. Use a
separateEPAS tool, the System Configuration Editor (SCE), to create and version the databases.
Each database has a related VDBS (System Baseline Version).
You can upload a standby database even if the computer is in operation: use the filename.adb
format.
C264/EN UM/E50.5 121

You upoad a database into the flash memory of the computer by using Computer Administration
Tool (CAT) software, over Ethernet. Operators generally uses WebCAT only to upload a first
database. This database becomes the new Standby database.
At any moment, the BCPU stores up to two DBs in its flash memory. The two DBs and their
related VDBS have the labels DB1, VDBS1; and DB2, VDBS2.
Each database of the BPCU, DB1 and DB2, has one of the states that follow:
• Missing: the DB is not present in the flash memory of the computer
• Standby: the DB was downloaded into the non-volatile memory of the computer, but the
software does not acknowledge this version
• Current: the software acknowledges the downloaded DB
• Current Modified: the DB had a change to a parameter setting and the software currently
acknowledges the DB
• Standby Modified: the DB had a change to a parameter setting and the software does not
acknowledge the DB.
In the computer, the life cycle of the DBs shows in the figure that follows:
- Figure 5 - The different status of a database
At any moment, there is only one DB either in the Current state, or Current Modified state. In the
same way, there is only one DB either in the Standby state, or Standby Modified state.
For the two downloaded DBs, DB 1 and DB 2, the four possible states show in the table that
follows:
122 C264/EN UM/E50.5

Database State 1 State 2 State 3 State 4

DB1 and VDBS1 Current Current Modified Current Current Modified
DB2 and VDBS2 Standby Standby Standby Modified Standby Modified
A file descriptor with the label DB context, stored in the flash memory of the computer, includes
the configuration of the DB installed on the device.
Database descriptors are shown in CAT interface.
When rebooting the computer the considered current database is the last current one.
4.1.2.2 How to upload a database through ethernet

To upload a database through Ethernet, use CAT software (refer to chapter "Human Machine
Interface" on page 498)
4.1.2.3 How to switch the databases

A request to switch the DB can be sent on station-bus via Computer Administration Tool (CAT).
This request specifies the version of the standby DB and related Vdbs to become current.
- Figure 6 - Database switching
When the computer receives the switch command, the computer downloads the database to the
other racks.
When this series of downloads is successful, the computer switches the databases in all the
racks.
After a DB switch, and if the DB is coherent with the software, the computer automatically reboots
and goes into Operational Mode.
C264/EN UM/E50.5 123

4.1.2.4 How to do a check of the database

At each reboot, the computer does a check of the DB.
With the MiCOM C264 local Operator Interface, with the Human Machine Interface (HMI) front
panel, or with the maintenance laptop computer and the Computer Administration Tool (CAT),
you can set the time and date.
4.1.2.5 How to modify the database

With the local HMI, you can only modify a parameter setting on the current DB: that is, the Current
or Current Modified DB. You can modify only certain data parameters. To modify the parameters
of the DB, you modify some configuration values in the DB. The modified DB stores the new
parameter settings. The computer increments the internal index of the parameter setting file and
calculates again the checksum of the file. The database takes the Current Modified state.
4.1.2.6 How to modify a parameter setting in the current DB

To modify the parameter setting in the current DB, use the computer to:
1. Do a check of the coherence of the request:
Is the object known to the computer, that is, is the object really present in the database?
Can the computer set the data?
Is the value of the parameter setting compatible with the type of data conveyed: does
the value belong to the acceptable range?
2. If the request is incoherent, the computer sends a negative report to the device that sent the
request.
3. Write the current value of the data in the DB;
4. Write the date that you modified the data in the DB;
5. Compute the checksum and to write it in the DB;
6. Assign the state Current Modified to the DB;
7. Send a positive report to the device that sent the request;
8. Update the file descriptor, that is the Context database, in the flash memory.
4.1.2.7 How to consult a parameter setting in the current DB

To manage a request to consult a parameter setting in the current DB from the Operator Station,
use the computer to:
1. Do a check of the coherence of the request:
Is the object known to the computer, that is, is the object really present in the database?
Can the computer set the data?
Is the value of the parameter setting compatible with the type of data conveyed: does
the value belong to the acceptable range?
2. If the request is incoherent, the computer sends a negative report to the device that sent the
request;
124 C264/EN UM/E50.5

3. Develop the response to include the parameter setting and to send it to the device that sent
the request.
4.1.3 Self-tests
The computer performs these self-tests:
• Hardware at start-up and cyclically.
• Software cyclically to make sure that software tasks are active and do not take all the CPU
time
• Database coherency at start-up
• Acquisition and output at start-up and cyclically.
4.1.4 Time management

The main purposes of the time management include:
• To synchronize the internal clock in the computer (referred to as the local clock) with:
The external clock,
SCADA,
SBUS or LBUS,
Operator;
• To update the local clock;
• To synchronize other devices through the SBUS with the local clock.
The local clock can be synchronized with an external time reference from four sources:
• External clock sends an IRIG-B signal1 or through SBUS,
• SCADA sends a clock message through the TBUS and through the gateway1,
• The system master clock sends a clock message through the SBUS - SNTP2 ,
• An operator who sets the time2.
There is a priority rule for these four external time references. If the external clock operates, it
locks out changes from the three other sources: you cannot make modifications to the local clock
in these ways:
• Locked out: SCADA sends a clock message through the TBUS and through the gateway,
• Locked out: The system master clock sends a clock message through the SBUS
• Locked out: An operator who sets the time.
For the MiCOM C264 Multirack system, the main rack delivers time synchronization to the
extension racks.
In event an external clock disconnects or does not operate, there is a priority order for the three
external time references that remain:
1For all MiCOM C264 computers
2For all MiCOM C264 computers except MiCOM C264 Standalone computers
C264/EN UM/E50.5 125

a. SCADA sends a clock message through the TBUS and through the gateway
or
b. The system master clock sends a clock message through the SBUS
have priority over:
c. An operator who sets the time.
Just after the local clock is synchronized, and if it is the master system clock of the LBUS, the
computer synchronizes the Intelligent Electronic Device (IED) in agreement with the
synchronization procedure of the protocol. If the local clock is not synchronized, the computer
synchronizes periodically the IED all the same.
When the local clock is synchronized, all events and measurements include a time tag with a
synchronized attribute. If the synchronization is lost, or was never achieved, the attributes indicate
that the time tag is not synchronized.
For a substation, the EPAS architecture can synchronize as many as 120 devices, such as the
MiCOM C264, HMI, gateways, IED Relays, IEC 61850 Relays.
- Figure 7 - Time management
4.1.4.1 External clock

The external clock receives the synchronization signal through one of several protocols: GPS,
DCF77, and so on. Periodically, the external clock sends the synchronization signal, that includes
the hour and the date, to the dedicated IRIG-B input of the MiCOM C264 computer.
126 C264/EN UM/E50.5

Each computer has its own local clock. The local clock synchronizes with the signal from the
external clock. In this system architecture, the local clock operates as the System Master Clock.
In event of the loss of the radio signal from the external clock, two events can occur:
• Some external clocks include a very accurate oscillator. After a loss of radio signal, these
external clocks can synchronize the computer for 8 hours. The external clock sends two
messages thru the protocol. The text of the messages is in agreement with the manufacturer
specifications. For example:
no radio received,
loss radio signal since more 8 hours.
The local clock remains synchronized with the external clock until the message "loss radio
signal since more 8 hours" activates. The status of the local clock now shows as not-
synchronized.
• Some external clocks do not have the internal accuracy to support the radio signal. In this
event, when the confirmation of loss radio signal occurs in a few minutes, the status of the
local clock shows as not-synchronized.
If the computer operates as the system master clock for the other devices in the substation, then it
continues to send the clock synchronization message to the other devices, even if the local clock,
or system master clock, is not synchronized with an external time reference. A binary input is
dedicated to monitor the status of the external clock.
4.1.4.2 Clock synchronization message from a SCADA gateway

The acquisition of a SCADA clock synchronization message is a SCADA gateway specification.
The SCADA clock synchronization depends on the protocol. The clock synchronization message
goes directly thru the SCADA link to the MiCOM C264 computer.
The clock synchronization message from the SCADA gateway is in Universal Time Coordinated
(UTC) time.
From the SCADA, the clock synchronization message goes to the “local clock update” function in
the computer. The computer does a check of the frame of the clock synchronization message,
removes the control fields, and transmits the clock synchronization message.
When the SCADA gateway operates as the external time reference in agreement with the priority,
the computer receives the clock synchronization messages from the SCADA. An interruption
relates to the arrival of the frame: the computer can acquire the clock synchronization message
from the SCADA gateway. The delay in the transmission from the SCADA gateway is
compensated.
The clock synchronization message from the SCADA gateway must contain:
Day / month / year / hour / minutes / seconds / milliseconds.
To update the computer local clock, please refer to 2.3.5 Local Clock Update.
4.1.4.3 SNTP Client and Servers

On an IEC 61850 network, the clock synchronization uses the Simple Network Time Protocol
(SNTP). On any Station bus of a EPAS system, you can define up to two station bus devices as
System Master Clock: they become main and backup SNTP servers. All other devices connected
C264/EN UM/E50.5 127

on the same Station bus become SNTP potential clients. If the main SNTP server is non-
operational, the SNTP clients automatically connect to the backup SNTP server.
MiCOM C264 supports SNTP client and server mode.
The synchronization performance of the system depends on the accuracy of the SNTP server.
A MiCOM C264, that is configured as an SNTP server, can be redundant. Its backup can be
defined as the backup SNTP server.
4.1.4.4 Time set by an operator

If an external time reference operates, such as the external clock, the SCADA clock or the system
master clock, you the operator cannot set the time.
If the system master clock synchronizes any other device in a EPAS system architecture, you
cannot set the time for that device. However, in event the system master clock is out of service or
the connection fails, you can set the time for the device.
synchronization messages from the external clock, from the SCADA gateway, or from the system
master clock, you are allowed to set the time manually.
Normally, you must manually set only the system master clock. You must use the correct tool for
the specific system master clock.
With the MiCOM C264 local Operator Interface, with the Human Machine Interface (HMI) front
panel, or with the maintenance laptop computer via the Computer Administration Tool (CAT), the
time and date can be set independently. The computer makes a record of all operator actions.
4.1.4.5 Local clock update

Each computer has its own local clock. Each local clock has its own quartz drift: a deviation of the
internal oscillator of the computer. You must synchronize the local clock periodically to agree with
an external time reference.
The time data includes:

• Loss of the external clock, loss of SCADA gateway clock synchronization message, or loss of
the system master clock;
• An indication that the local clock was roughly synchronized. This indication shows any time
difference, between the local clock and the clock synchronization message, that is greater
than the fixed value: Dthreshold = 20 millisecond. The computer sends a message about the
discrepancy, prints the message, and archives the event.
• Indication that the operator performed a manual time set. This “manual time set” indication is
required to time-tag the events that occur.
The internal time format for the local clock is Universal Time Coordinate (UTC). The time
difference between UTC and the local time is set during configuration.
The local clock operates automatically:

• For all dates including leap years thru to 2037,
• For seasonal time changes: it uses the values for Daylight Savings Time (DST) as shown in
the Time Zone Adjustment Table (TZTAB) file. The TZTAB file shows the differences between
UTC and local time.
128 C264/EN UM/E50.5

If the DST rules change, you can set the new rules in the computer.
The computer manages the milliseconds with its own quartz.
The Local Clock Update function manages the synchronization status of the computer as follows:
• Not synchronized: this is the status at initialization, the computer has never been
synchronized since booting or rebooting. Date and time are invalid,
• Synchronized: the computer receives periodically the date and time. Date and time are valid.
Or the computer is master clock on the Ethernet network for other equipment.
synchronized with the local clock. This status remains the same until you send a control message
to the initialization driver to receive synchronization frames from an external time reference. When
the control is OK and at the reception of the first external clock message, the synchronization
upon external clock is declared valid and the external clock is considered connected.
This synchronization with the external clock could fall back to invalid: for example, in event the
computer did not receive an external synchronization message for N minute(s). This can indicate
an external clock failure, such as a disconnect or a message that contains invalid data. The value
of this timing is 300 seconds.
In event of an external clock failure, the local clock maintains the frequency in effect before the
external clock failed. The computer generates an internal signal or alarm and declares the system
master clock invalid. When this occurs, the computer makes a non-synchronization mark against
each event, for as long as the synchronization with the external clock remains invalid.
When a device on the SBUS does not receive a clock synchronization message in 180 seconds, it
raises an alarm. The events processed by this device are tagged with a special mark and with the
time, and the device stops the transmission of the synchronization frame to the IEDs.
4.1.4.6 Management of loss of external time reference

As the local clock update function receives the external time reference, it manages a loss of the
external time reference as follows:
• If the external clock is lost, then the local clock update shows the loss of the external clock,
• If the clock message from the SCADA gateway is lost, then the local clock update shows the
loss of the SCADA gateway clock message,
• If the system master clock is lost, then the local clock update shows the loss of the system
master clock.
4.1.4.7 Update method

When the computer validates the external clock acquisition, the computer manages the
synchronization of the internal system master clock to the external time reference as follows:
If a difference between the local clock value and the external time reference value transmitted
exists, [C Local – C External] differs from 0.
If [C Local – C External] < 1 ms, the local clock is not modified.
If [C Local – C External] > 1ms, two different events are processed:
1. If [C Local – C External] £ D Threshold (20 ms), the value of the local clock is progressively
corrected (reduced or increased). This compensation is performed in a set time (t1=60 s).
C264/EN UM/E50.5 129

2. If [C Local – C External] ³ D Threshold (20 ms), the hour in the local clock is updated
roughly.
If an operator gets the external clock time, the operator must update the local clock.
4.1.4.8 Limits and performances

The computer local clock has a small drift per day. This quartz drift, that is the deviation of the
internal oscillator of the computer, is less than 0,5 s/day (that is, ≤ 5,8 ms/s). This quartz drift is the
same through the entire operating temperature range of the computer. The operator must set the
time periodically or synchronize the local clock with a master clock.
4.1.4.9 Precision Time Protocol 1588

The Precision Time Protocol (PTP) is a protocol used to synchronize clocks throughout
a computer network. On a local area network, it achieves clock accuracy in the sub-microsecond
range, making it suitable for measurement and control systems.
Standard IEC PAS 61850-9-3:2015(E) specifies a precision time protocol (PTP) profile of
IEC 61588:2009 applicable to power utility automation.
Reference Description
Precision Clock Synchronization Protocol for
IEC 61588:2009 ed2
Networked Measurement and Control Systems
Communication networks and systems for
power utility automation
IEC 61850-9-3-06-2015
Part 9-3: Precision time protocol profile for
power utility automation
Grand Master Clock
The IEEE1588 algorithm is supported by MiCOM C264.
The GMC is synchronized with external clock source like a GPS, IRIG-B, NTP, SCADA. The clock
accuracy depends of source.
All clock devices (IEEE1588 compliant) are synchronized by GMC.
The clock Priority is set by Operator on SCE. The Operator defines the priority list depending of
the clock source accuracy.
Example of external GPS elected as GMC
In the following use case, M600 GPS Receiver is elected as Grand Master Clock and all devices
are synchronized by it.
The IEEE1588 external clock GPS receiver is elected as the best master clock compared to IRIG-
B, NTP, SCADA, OPERATOR.
130 C264/EN UM/E50.5

- Figure 8 - GPS Receiver is elected as GMC
Example of IED synchronized by IRIG-B elected as GMC
In case of no IEEE1588 External clock (see figure below), IRIG-B clock is elected as the best
master clock compared to NTP, SCADA, OPERATOR by all the IEDS which using the 1588
algorithm.
In case of 2 same clock accuracy, the mac address determines which clock is elected by all the
IEDS which using the 1588 algorithm.
In the following use case, C264_1 is elected as Grand Master Clock and all devices connected on
the same network are synchronized by it.
C264/EN UM/E50.5 131

- Figure 9 - C264_1 is elected as GMC
Example of IED synchronized by NTP elected as GMC
In case of no IEEE1588 External clock and no IRIG-B, NTP clock is elected as the best master
clock compared to SCADA, OPERATOR by all the IEDS using the 1588 algorithm.
132 C264/EN UM/E50.5

Example of IED synchronized by SCADA elected as GMC
In case of no IEEE1588 External clock, no IRIG-B and no NTP, SCADA clock is elected as the
best master clock compared to OPERATOR by all the IEDS using the 1588 algorithm.
C264/EN UM/E50.5 133

Example of IED synchronized by Operator elected as GMC
In case of no IEEE1588 External clock, no IRIG-B, no NTP and no SCADA, OPERATOR clock is
elected as the best master clock by all the IEDS using the 1588 algorithm.
134 C264/EN UM/E50.5

Example of GMC not elected in the network
Using a configuration parameter, the user can force the MiCOM C264 to not be elected. This
MiCOM C264 is synchronized by a Grand Master Clock but is never elected as Grand Master
Clock.
In the following use case, C264_6 is not elected as Grand Master Clock and C264_7 is not
synchronized by it. The clock given by the OPERATOR is used.
C264/EN UM/E50.5 135

- Figure 13 - C264_6 is not elected as GMC
4.1.4.9.1 Performance and limits
Clock source Clock accuracy Limits

The accuracy of C264 is 1 ms, so the
External
1 µs system synchronization accuracy is 1
IEC 61588
ms.
The accuracy of C264 is 1 ms, so the
IRIG-B 100 µs system synchronization accuracy is 1
ms.
The system synchronization
NTPB 1 ms
accuracy is 1 ms.
SCADA 10 ms
accuracy is 10 ms.
OPERATOR 1s
accuracy is 1 s.
136 C264/EN UM/E50.5

4.2 Communications
The MiCOM C264 includes different types of communications:
• Telecontrol Bus (TBUS),
• Legacy Bus (LBUS),
• Station Bus (SBUS),
• Inter-rack Ethernet communications.
For the MiCOM C264, the possible combinations of protocols follow:
number of
Protocols on the number of Protocols on the LBUS Total number of protocols allowed
TBUS
2 Up to 2
1 Up to 3 4 or less
0 Up to 4
The basic communications follow:
- Figure 14 - Communications
4.2.1 Telecontrol bus - TBUS

You can connect a MiCOM C264 through the TBUS to the SCADA. The TBUS can use a
maximum of two of these protocols:
MiCOM C264
Protocol Protocol Type link type
behaves as
Serial, Over IP
DNP3 Master / Slave Slave
(TCP/IP & UDP)
MODBUS Master / Slave Slave Serial
C264/EN UM/E50.5 137

MiCOM C264
Protocol Protocol Type link type
behaves as
Master / Slave or
T101 Slave Serial
Balanced
T104 Balanced Slave Over IP
MiCOM C264 connects direct or through a modem with SCADA.
Physical layer:
• DNP3, MODBUS, T101 : RS 232, RS 422, RS 485,
• DNP3 over IP (TCP/IP & UDP), T104: Ethernet 10 or 100 Mb/s: RJ45 connector or optical
fibre (multimode or monomode).
On the MiCOM C264, you can configure as many as 2 different serial telecontrol protocols. If you
use the Ethernet T104 protocol, you can connect as many as 4 independent clients.
The redundancy is not available for T104, DNP3 over IP, and MODBUS.
4.2.2 Legacy bus - LBUS

MiCOM C264 behaves as a master.
Protocols:
• IEC 60870-5-103 (T103) : Serial,
• IEC 60870-5-101 (T101) : Serial,
• ModBus: Serial,
• DNP3: Serial or IP,
• IEC 60870-5-104 (T104) : IP.
Devices connected to: IEDs
Physical layer:
• RS 232, RS 422, RS 485,
• Optical fiber: via ECU converter,
• DNP3 over IP: Ethernet 10 or 100 Mb/s: RJ45 connector (multi-mode or mono-mode optical
fibre via Ethernet switch board),
• T104 over IP: Ethernet 10 or 100 Mb/s: RJ45 connector (multi-mode or mono-mode optical
fiber via Ethernet switch board).
NOTE: If any extension rack is present, then all the LBUS shall mandatory be placed on
extension racks.
There is no redundancy for the LBUS.
Limitations
The following table describes the limitations of the Legacy networks.
138 C264/EN UM/E50.5

LBUS Protocol supported by MiCOM C264

Maximum number of LBUS links 4
Maximum number of IED(s) connected per LBUS link 16
Master Protocol T104

Maximum number of IED(s) connected to LBUS network per MiCOM C264 64
4.2.3 Station bus - SBUS

The station bus interface uses IEC 61850 protocol edition 1 or 2 on ethernet layer up to 1Gb/s,
with GOOSE and REPORT capabilities. It allows data exchanges between EPAS subsystems
(Bay Control and Protection Unit, EPAS-Gateway, EPAS-EcoSUI) and also third-party IEC 61850
devices.
In GOOSE mode, the MiCOM C264 can be publisher or subscriber.
In REPORT mode, the MiCOM C264 can be server or client.
The MiCOM C264 supports both modes simultaneously.
The available physical supports are: copper twisted pair (RJ45 connector) or optical fiber (multi-
mode or mono-mode)
The optical port is optional. To increase the number of Ethernet port, four Ethernet switch boards
are available:
• SWU with 4 RJ45 ports and up 2 optical ports (multi-mode or mono-mode)
• SWR with 4 RJ45 ports and 2 optical ports for a redundant ring (multi-mode or mono-mode)
• SWS with 4 RJ45 ports and 2 optical ports for a redundant ring using RSTP protocol
• REU with 1 RJ45 ports and 2 redundant combo ports, each composed by an optical and a
RJ45 port for a redundant ring using HSR/PRP or RSTP protocol
4.2.3.1 Exchanges
MiCOM C264 computer acquires & sends data on IEC 61850 network using REPORT/ GOOSE.
The REPORT is specific between a server and one client, it provides:

• data value
• data state or quality attribute (validity and several kind of invalid state)
• time tag of last data value change
• time tag quality attribute (server synchronized or not when event has occurred)
Data quality defines data validity or invalidity (unknown when disconnected, Saturated,
Undefined…)
REPORTS are sent/received with their RFI (Reason For Inclusion): periodic, spontaneous
state/value change or following control.
The GOOSE is a short message (data value and quality) sent in multicast to all SBUS equipment.
C264/EN UM/E50.5 139

GOOSE exchanges are faster than Report ones. GOOSE exchanges are mainly used in
distributed automation or in case of IEC 61850 device limitation (IED capabilities restriction)
Data quality defines if data is valid or several kinds of invalidity: unknown when disconnected,
Saturated, Undefined… REPORTS are sent/received with their RFI (Reason For Inclusion):
periodic, spontaneous state/value change or following control.
The GOOSE is a short message (data value and quality) sent in multicast to all SBUS equipment,
this is quicker than Report.
MiCOM C264 computer can provide BRCB (buffered report) to its IEC 61850 clients. Total BRCB
client is limited to 4. These clients are generally EPAS-EcoSUI or EPAS-Gateway.
MiCOM C264 records only ST events in buffer to generate buffered report. Buffers are cyclical,
FIFO and unitary event replacement. The buffer capacity is 100 ST events
NOTE: Data are buffered only after connection established once between MiCOM C264 BRCB
server and its client.
4.2.3.2 IEC 61850 compliances

Refer to the PICS, MICS, PIXIT and TICS documentation of MiCOM C264.
NOTE: A MiCOM C264 client can have 32 numbers of IEC 61850 servers and a MiCOM C264
server can have 16 numbers of IEC 61850 clients. GOOSE BCPU size is restricted to 128 binary
inputs and 64 measurements.
4.2.3.3 Controls
MiCOM C264 supports Common Data Classes control expressed with SPC, DPC, INC and APC
configured as Direct Execute or SBO.
NOTE: With the standard IEC 61850-8-1 edition 1, 2 the BYPASS attribute is suppressed and is
replaced by the CHECK attribute. For e.g the BYPASS ALL is replaced by CHECK_NONE.
4.2.4 Inter-rack Ethernet communication
140 C264/EN UM/E50.5

4.2.4.1 Internal Ethernet architecture
The internal communication on the Ethernet MiCOM C264 network uses proprietary protocol with
unicast messages. All messages used by the computer for internal data exchanges remain inside
the MiCOM C264. These messages do not pollute the external network reserved for the SCADA
interface.
Furthermore, the CAT tool uses also the Ethernet broadcast to identify racks. This tool is used
only for maintenance purpose (Software and configuration downloading).
Acquisition and front-end racks must have the same group number when they are attached to the
same MiCOM C264. This group number is defined using the CAT and is limited to 16.
4.2.4.2 External network behaviour

Due to the connection of the MiCOM C264 with the external network for the SCADA
communication (T104) a precaution shall be taken in order to avoid Ethernet loops. External
switches of the upstream communication must be able to use the spanning tree algorithm to
prevent Ethernet loops.
The Spanning Tree (802.1D) or the Fast Spanning Tree (802.1W) algorithm of the external
switches identifies the Ethernet ring created with the external and internal Ethernet infrastructure
and computes the appropriate path avoiding Ethernet Loops.
C264/EN UM/E50.5 141

The computation of the network tree is done only one time by the spanning tree algorithm of
External switches.
142 C264/EN UM/E50.5

4.2.4.3 Ethernet failure

Ethernet ring opening
The consequence of the ring opening involves to lose the communication between the Main 1
rack and the Main 2 rack.
Consecutively we have:
• Data transfer from extension rack #1 through the External Ethernet infrastructure (outside the
MiCOM C264 Ethernet network) to the Main 2 rack.
• Ethernet ring opening and rebuilding of routine table ordered by the spanning tree algorithm
(> 30 s if 802.1D used)
C264/EN UM/E50.5 143

4.2.4.4 Other Ethernet rupture
The other events of rupture of the Ethernet MiCOM C264 network do not involve:
• Data Routine outside of the internal Standalone Ethernet network,
• Starting of the spanning tree algorithm (Ethernet ring maintained).
All data produced by the insulated rack are defined in an unknown state.
The other racks of the MiCOM C264 (remaining on Ethernet continuity) are fully operational. Data
transferred to the Main racks through the Standalone private communication do not use the
external Ethernet infrastructures.
4.2.4.5 Ethernet Routing table

MiCOM C264 connects to a router and a remote T104 SCADA
144 C264/EN UM/E50.5

4.2.5 Ethernet port management on CPU275

The CPU275 Ethernet ports can be configured as follows:
N° Port 1 Port 2 Comments

SCADA 2 independent SCADA protocols
1 IEC 61850 SBUS + SCADA IP 1
IP 2 with different database
SCADA 2 independent SCADA protocols
2 SCADA IP 1
IP 2 with different database
SCADA
3 IEC 61850 SBUS
IP
IEC 61850 Station Bus, if configured, is always on port 1.
One or 2 IP SCADA protocols can be configured on port 1 and/or 2.
The existing SCADA protocols are DNP3 and T104. DNP3 is mono-client. T104 is multi-clients
(as many as 4 clients) with only one active at one time. Bind one protocol on one, and only one,
Ethernet port. If you use two Ethernet ports, make sure that the IP addresses of the Ethernet ports
are on two different sub-networks. The two Ethernet ports can share the same physical network.
Use the CAT tool to configure the Ethernet ports.
C264/EN UM/E50.5 145

- Figure 15 - CAT showing two Ethernet ports
4.2.6 Telecontrol Bus redundancy
The MiCOM C264 may be redundant in the EPAS system in order to ensure the quality of service
in case of a communication failure.
The MiCOM C264 communication with the SCADA uses Serial links or Ethernet link.
The management of Telecontrol Bus (TBUS) redundancy is driven by SCADA.
There are 2 TBUS redundancy types:
146 C264/EN UM/E50.5

• Link Redundancy: 2 lines (main and auxiliary) for one protocol in one MiCOM C264,
• Protocol Redundancy: via a redounded MiCOM C264, where everyone of the couple supports
a line with the SCADA.
C264/EN UM/E50.5 147

4.3 Direct process access

The BCPU acquires digital and analogue input, counters, digital measurements. Configuration
parameters, filtering and triggering are applied to these inputs and depend on their type.
4.3.1 Input check

Input data coming from the physical BCPU boards or from the different communication networks
are periodically checked.
Invalidity status of these data is internally fixed for:

• Self-test (DI, board self-test failure)
• Unknown (DI, communication failure to remote acquisition like IED)
• Toggling (DI, X change of state in given time)
• Undefined (Digital Measurement or Counter with invalid DI coding)
• Over-range (AI, saturation of its transducer, or Counter value reaching limits)
• Open Circuit (AI kind 4-20 mA with current value under 4mA)
4.3.2 Output check

Digital Output boards are periodically checked at their logical level. In the event of a logical circuit
test fail the board is set faulty, controls on this board or upon disconnected IEDs are refused.
4.3.3 Time stamping

All physical input data are time tagged at 1 ms accuracy. All internal logic data are time stamped
at 1 ms accuracy.
Analogue Inputs acquisition is done periodically, the period cycle is 100ms.
Information coming from IED are time tagged by IED itself if it has this facility otherwise it is
performed at MiCOM C264 level when receiving the data.
4.3.4 Digital input acquisition (DI)

4.3.4.1 DI acquisition
The DIU200/DIU211 (16 DIs) or CCU200, CCU211 (8 DIs + 4 DOs) boards acquire the binary
data.
Digital Input (DI) can have the value 1 or 0. The value 1 shows the presence of an external
voltage. The value 0 shows the absence of the external voltage.
When the external voltage is above or below a threshold, the hardware writes the value 1 or 0.
The hardware specification document shows the value of the threshold.
A transition from the value 0 to 1 or from 1 to 0 is usually followed by a succession of transitions

(bounces) before the value stabilizes. The software has to filter these bounces.
Each change-of-state of a digital input is time-stamped with a resolution better than 1 ms.
148 C264/EN UM/E50.5

- Figure 16 - digital input processing
4.3.4.2 DI Debouncing and filtering

A filter is applied on the digital inputs as follows:
- Figure 17 - digital input filtering and debouncing
T0 is the instant of detection of the first transition.
T1 is the instant of validation of the change of state.
T2 is the end of the filtering: the signal remained stable from T1 thru T2. The change of state is
time stamped at T0.
A value of 0 means that no filter is applied: a change of state is validated as soon as it is detected.
Three couples (debouncing / filtering) of delays are defined:

• one for all DI that will be used as BI
• one for all DI that will be used as DM
• one for all DI that will be used as counters
4.3.5 Counter acquisition (CT)

The counters are acquired on the same boards as the DIs. There are two types of counters SCT
(Single counter) and DCT (Double counters).
This interface allows acquisitions of pulses delivered from energy metering devices
corresponding to a calibrated quantity of energy.
Each valid pulse increments the value of an accumulator used to compute the quantity of energy
delivered during a given period.
Counter values are stored in static memory (secured with a capacitor, > 48h autonomy). The
counters are kept for more than 48 hours when the BCPU power supply is off.
C264/EN UM/E50.5 149

The pulse frequency should be 20 Hz as a maximum. So, the debouncing and filtering values
must be chosen in consequence.
You can acquire as many as 16 counters (wired) for each Extension Rack. The maximum
acquisition frequency does not exceed 20 Hz and the total frequency for the 16 counters does not
exceed 160Hz.
You can define a maximum of 128 counters for a complete MiCOM C264. You can wire as many
as eight counters on the main 1 rack with no modifications.
4.3.5.1 Single counter (SCT)

An SCT is acquired on a single contact.
The value of the accumulator is incremented after a low to high transition, confirmed after a
filtering time (Tcount). Tcount is defined for the whole system, with a step of 5 ms: the chosen value
must be coherent with the pulse frequency (that is, all counters of a system use the same Tcount).
A subsequent pulse can be taken into account only after a high to low transition.
- Figure 18 - single counter chronogram
4.3.5.2 Double counter (DCT)

A double counter is acquired on two contacts. One is called the true contact (TC), the other is the
complemented contact (CC). Normally these contacts should have complementary states.
Pulses are detected in the same manner as for SCT, on the TC variations, using the Tcount delay
(the same Tcount value is used for SCT and DCT).
A subsequent pulse is only considered after a high to low transition on TC (and so a low to high
transition on CC).
The difference is that both contacts should be in opposite states for transitions to be detected and
validated. The counter is invalid if there exists a non-complementarity between the 2 contacts
during a delay Tdef. This delay is defined for the whole system (that is, all DCT use the same
delay).
150 C264/EN UM/E50.5

- Figure 19 - Double counter chronogram
4.3.6 Digital measurement (DM)

The digital measurements (DM) are derived from the Digital Inputs. They are acquired on the
same boards as the DIs.
This interface, allowing acquisitions of a digital measurement, is a digital value coded on N wired
inputs. Each wired input represents a bit of the value and can take only one of two values: low or
high.
Digital Measurements are used to process the measurements and tap position indications.
A Digital Measurement can be associated to a Read Inhibit (RI) signal. The acquisition process is
different depending of the presence of this signal.
4.3.6.1 Acquisition without Read inhibit signal

The DM is calculated at each change of state of one of its bits.
A stability processing is applied at each calculation to confirm the value:
if the difference between the current value and the previous confirmed value is less or equal than
Vstab (value defined in configuration), then the current value is confirmed
if the difference is greater than Vstab, then the Tstab delay is launched (value defined in
configuration, from 0 to 60s, with a 10 ms step). If a Tstab delay is already launched, this one is
cancelled. At the end of the delay, the DM value is confirmed.
C264/EN UM/E50.5 151

- Figure 20 - DM value confirmed
Furthermore, an invalidity processing is applied: at the first change of state of one bit following a
confirmed DM value, the TInv delay is launched (value defined in configuration, from 0 to 300s,
with a 10 ms step). If the value is not confirmed at the end of this delay, the DM is declared
UNDEFINED.
- Figure 21 - DM undefined
If Vstab is equal to 0, there is no stability processing: all DM values are sent at each calculation.
4.3.6.2 Acquisition with Read inhibit signal

When the RI signal changes to set state, the Tinh delay is launched. If the signal is always set at
the end of the delay, the DM is declared UNDEFINED. Otherwise, if the RI signal changes to reset
state before the end of the delay, the current DM value is transmitted.
- Figure 22 - Acquisition with ri
If the RI signal is invalid, the DM will be invalid.
152 C264/EN UM/E50.5

4.3.6.3 Encoding
The following codes are allowed for DM:
CODE Number of bits (max. 64) Range of value

4 (1 BCD decade) 0 to 9
8 (2 BCD decades) 0 to 99
BCD
16 (4 BCD decades) 0 to 9,999
32 (8 BCD decades) 0 to 99,999,999
64 (16 BCD decades) 0 to 9,999,999,999,999,999
Binary n 0 to 2n-1
Gray n 0 to 2n-1
16
(1 bit among 6 for the tens, 0 to 69
1 among 10 for the units)

32
(1 bit among 4 for the

thousands,
1 bit among 9 for the 0 to 4,999

hundreds,
1 bit among 9 for the tens,
1 bit among 10 for the units)

64
Decimal
(1 bit among 9 for the millions,
1 bit among 9 for the hundreds

of thousands,
1 bit among 9 for the tens of

thousands,
0 to 9,999,999
1 bit among 9 for the
thousands,
1 bit among 9 for the

hundreds,

1 among N n 0 to n
You can use one supplementary bit for the sign (0 indicates a positive value, 1 indicates a
negative value).
Capability extension for the Tap Position Indication only:
C264/EN UM/E50.5 153

CODE Number of bits Range of value

2 0 to 2
1 among N
to 64 to 0 to 64
4.3.7 Analogue Input acquisition (AI)

Acquisition of AC voltages and currents coming from the electrical network is done with the
TMU2xx board.
Acquisition of DC currents signal is done with AIU211 (8 AIs) boards. For those AI an input range
and an acquisition cycle are defined in configuration.
4.3.7.1 4.7.1 Input ranges

For current inputs: 0 - 1 mA, ± 1 mA, 0 - 5 mA, ± 5 mA, 0 - 10 mA, ± 10 mA, 4 - 20 mA,
0 - 20 mA, ± 20 mA.
The saturation value depends on the selected range.
4.3.7.2 4.7.2 Acquisition cycle

The analogue inputs are acquired on a periodical basis (short or long cycle, defined in
configuration).
There can be maximum 48 Wired MV for a MiCOM C264. and 200 MV/sec receiving flux for a
MiCOM C264.
4.3.8 Digital outputs (DO)

Digital outputs are used to apply a switching voltage to an external device in order to execute
single or dual, transient or permanent commands. The applied voltage is fed from an external
power supply. The external voltage is connected to the controlled device by a relay, thus isolating
the logic part of the board from the external power supply.
Two types of Digital Outputs are available for the MiCOM C264:
• CCU200 boards for controls (8 DIs+4 normally open DOs), this board allows double pole
switching controls.
• DOU201 boards for alarms (8 normally open DOs + 2 normally open/normal close DOs).
4.3.9 Digital Setpoints

Digital setpoints are digital values sent on multiple parallel wired outputs. Each wired output
represents a bit of the value. Digital setpoints are used to send instruction values to the process or
to auxiliary devices.
The Digital Setpoints are processed on the same boards as the Digital Outputs. The Digital
Outputs characteristics described above apply on Digital Setpoints. Use only standard DO boards
with single pole N/O relays.
4.3.9.1 Encoding
The codes that follow are allowed:
154 C264/EN UM/E50.5

CODE Number of bits (max. 48) Range of value

4 (1 BCD decade) 0 to 9
BCD
16 (4 BCD decades) 0 to 9,999
32 (8 BCD decades) 0 to 99,999,999
48 (12 BCD decades) 0 to 999,999,999,999
Binary n 0 to 2n-1
Gray n 0 to 2n-1
16
(1 bit among 6 for the tens, 0 to 69
32
(1 bit among 4 for the thousands,
1 bit among 9 for the hundreds, 0 to 4,999
Decimal 48
(1 bit among 2 for the hundreds of
thousands,
1 bit among 9 for the tens of
thousands, 0 to 299,999
1 bit among 9 for the thousands,
1 bit among 9 for the hundreds,
1 among N n 0 to n
You can use a supplementary bit for the sign (0 indicates a positive value, 1 indicates a negative
value).
4.3.9.2 Read Inhibit

You can use a dedicated binary output to allow or forbid the reading of the value by the external
device.
There is one (or none) Read Inhibit (RI) output per value.
If the RI output is a logical one (external polarity applied), the reading is permitted.
To output a value with a RI output, do the steps that follow:

• Reset the RI output to a logical 0: read forbidden
• Wait for N ms
• Output the value
C264/EN UM/E50.5 155

• Wait for N ms
• Set the RI output to a logical 1: read permitted
The 0 to 1 transition on the RI output can be used by the external device as a trigger, indicating
that a new value is available.
4.3.10 Analog Setpoints

Analog setpoints are measurement values sent on the Analog Output board.
These setpoint commands (with analog indication) are received from the Station Control Point
(SCP), Remote Control Point (RCP), or from the local HMI (with LCD).
Analog Setpoints are used to interface auxiliary devices requiring analog inputs (ex:
measurement viewers, Generator), and in ISaGRAF® automation.
The Analog output values are secured with an external power supply that allows you to keep the
analog output value in event of MiCOM C264 shutdown or power off.
A quality indication is available with the additional Read Inhibit output relays (NO) associated to
each analog output.
4.3.10.1 Output range

The various Analog output range in currents are:
• ± 5 mA,
• 0 - 5 mA,
• ± 10 mA,
• 0 - 10 mA,
• 4 - 20 mA,
• 0 - 20 mA,
• ± 20 mA.
4.3.10.2 Output management

Each current output is individually managed in 2 modes:
• Maintained mode: in event of computer shut down or power off, the output level is maintained
(and the Read inhibit relay is set). Only the reception of a new setpoint will lead to an output
value modification.
• Un-maintained Mode: in event of computer shut down or power off, the output is set
to 0.
The Analog Output is stable 100ms after the order. During the Analog output value modification,
the “Read Inhibit” relay is reset (Open) and indicates that the analog output value is not to be
used.
156 C264/EN UM/E50.5

- Figure 23 - Diagram of AOU channel
4.3.10.3 AOU Watchdog management

The AOU board is monitored and the AOU Watchdog (NO relay) resets when:
• The external power supply is off,
• The MiCOM C264 is not operational or powered off (no communication with the CPU board),
• An AOU internal fault is present.
Otherwise, the analog output function is valid and the AOU watchdog relay is set.
C264/EN UM/E50.5 157

4.4 Data processing

BCPU treatment entries can be Binary Inputs or Analogue Inputs. They are issued from
• IO boards
• BCPU internal data: System Input, automation
• Communication acquisition: from an IEC 61850 IED or another computer from SBUS
4.4.1 Binary input processing

4.4.1.1 Binary input definition
A Binary Input (BI) stands for filtered data entered into the BCPU data processing layer that
becomes SPS, DPS, MPS or TPI with time tag and quality attributes.
Binary Inputs (BI) regroup:

• Single Point Status (SPS): usually processed from one digital input;
• Double Point Status (DPS): usually processed from two digital inputs;
• Multiple Point Status (MPS): usually processed from multiple digital inputs;
• Tap Position Indicator (TPI) processed from multiple digital inputs;
• System Input (SI): information related to the system, to configurable and built-in automation or
to electrical process but without acquisition possibilities. By extension, SI is of SPS, DPS or
MPS type depending on its associated states;
• Group: logical combination of SPS and DPS, that produces a SPS;
• SPS/DPS/MPS produced by user-defined slow automation;
• SPS produced by user-defined fast automation;
• SPS/DPS/MPS issued from IEC 61850 IED through the IEC 61850 station bus.
• By extension, input data acquired on IED connected to computer via a serial/ethernet link,
producing SPS, DPS or MPS depending on its associated states and legacy IED address(es);
At computer level, BI issued from other IEC 61850 IED are said “BI client”, otherwise “BI server”.
“BI server” is globally managed by the computer in term of value and quality. At computer level,
Binary Input processing concerns “BI server”.
4.4.1.2 Common processing of Binary Input

4.4.1.2.1 Toggling Input
Toggle Filtering concerns only BI server acquired from digital inputs.
After the acquisition on its digital input boards, the computer performs toggle filtering. When an
input has an erratic behaviour, such as more than N state changes during a given duration, toggle
filtering avoids charging the computer itself or other equipment.
A digital input is said to be toggling if its state has changed more than N times in a given period T1.
A toggling DI returns in the normal state if its state has not changed within another period T2.
N, T1 and T2 are parameters determined at configuration time on a per system basis.
SPS associated with a toggling Binary Input is in the TOGGLING state.
158 C264/EN UM/E50.5

DPS or an MPS whose one of the associated DI is toggling, is in the TOGGLING state.
4.4.1.2.2 Suppression
A binary input can be suppressed by an order issued from an operator. No subsequent change of
state on a suppressed BI can trigger any action: for example, display, alarm, transmission. The BI
takes the “SUPPRESSED” state. When the operator un-suppresses the BI, this one takes its
actual state.
4.4.1.2.3 Substitution
A BI can be substituted to a manual set state by an operator (state “SUBSTITUTED xxx”). The BI
stays in the state determined by the operator until he un-substitutes it. When a BI is substituted,
no changes of state are transmitted, and computations, for instance groupings, are made with the
substituted state. When the BI is un-substituted, the actual state is transmitted to higher control
levels and subsequent changes of state are transmitted again.
4.4.1.2.4 Forcing
When data is invalid: that is, SELFCHECK ERROR DETECTED, TOGGLING, UNDEFINED or
UNKNOWN; it can be manually forced by an operator (state “FORCED xxx”). This feature is
similar to the substitution, but the data is automatically updated when valid data is available again.
A SUPPRESSED or SUBSTITUTED datapoint cannot be forced. The forcing could also be
automatic: in this event, the invalid data is automatically replaced by the state defined in
configuration.
4.4.1.2.5 Transmission
BI server can be transmitted on the IEC 61850 station bus using the two modes:
• Report (client/server) based mode: in this mode, a confirmed change of status is
spontaneously transmitted to the clients with the time stamping and the reason for change.
The Report mode is used to transmit filtered data for displaying, printing and archiving.
• GOOSE (subscriber/submitter) based mode: in this mode, the change of status is transmitted
in multicast to the configured subscribers. On IEC 61850 network, all types of BI can be
transmitted using GOOSE. Only the BI unfiltered states are transmitted with their time
stamping, the reason for change is not. The GOOSE mode is used to transmit data as soon
as possible after their acquisition and as quickly as possible, for automation purpose.
EPAS-SCE uses predefined rules during “Data model and data flow update” treatment to select
the proper services to be used between IEC 61850 devices. For example, in automation
(interlock, PSL, PLC, and built in functions), GOOSE exchanges are favored by EPAS-SCE.
Refer to the chapter “Application” of EPAS-SCE user manual for details.
During a loss of communication, the events detected on the computer are not buffered.
C264/EN UM/E50.5 159

4.4.1.3 Processing of Single Point Status
- Figure 24 - single point status processing
4.4.1.3.1 Persistence filtering

A preliminary treatment is applied to specific Single Points Status (SPS) in order to confirm the
state on a certain period. If the opposite transition occurs before this delay, both transitions are
discarded.
This treatment is called persistent filtering.
The status is timestamped with the time of the transition.
Two time-out values can be associated with each SPS:

• TS: delay for the SET state confirmation,
• TR: delay for the RESET state confirmation.
Both delays are in the range 0 to 120 s by step of 100 ms. A value of 0 means that no filter is
applied.
The time tag is user-selectable:

• Mode 1: the status is timestamped with the time of the transition,
• Mode 2: the status is timestamped at the end of the persistent filtering.
160 C264/EN UM/E50.5

- Figure 25 - persistence filtering
4.4.1.3.2 SPS resulting state

The SPS resulting states are:
States
RESET
SET
TOGGLING
SELFCHECK FAULTY
UNKNOWN
SUPPRESSED
FORCED RESET
FORCED SET
SUBSTITUTED RESET
SUBSTITUTED SET
Each SPS state is configurable to be seen by automation in False, True or Invalid state.
C264/EN UM/E50.5 161

4.4.1.3.3 Mapping of SPS states on IEC 61850 station bus

On IEC 61850 station bus, the SPS states are mapped on IEC 61850 value/quality and seen by
IEC 61850 client as follows:
(N/A: Not Applicable)
162 C264/EN UM/E50.5

4.4.1.3.4 DI/DO association for SPS
CAUTION
UNEXPECTED "XPS/XPC ASSOCIATION" EXECUTION OF CONTROL
Carefully evaluate the impact of "xPS / xPC ASSOCIATION" automation before usage.
The aim of this automation is to create a direct association between a Single Point and a Digital
Output: a state change on the input produces the opening of the closure of the output.
The relation between the state and the order is defined during the configuration phase.
4.4.1.4 Processing of Double Point Status

DPS is derived from two Digital Inputs. One is called the Closed contact, the other one is the Open
contact.
- Figure 26 - double point status processing
DPS are commonly used for all switchgear position. From board valid acquisition the two contacts
are Close and Open (set by configuration when voltage is present). The position of the switch is:
Close Contact Open Contact DPS State

Below motion delay, the state
is valid motion. For REPORT
no transmission of the
0 0 transitory state.
After Motion filtering, state is

invalid JAMMED
0 1 OPEN
1 0 CLOSE
UNDEFINED after a
1 1
permanent filtering
C264/EN UM/E50.5 163

4.4.1.4.1 Motion filtering

A preliminary treatment (motion filtering) for some DPS is applied to filter the MOTION state on a
certain period. This avoids the transmission of this (normally) transient state.
Two time-out values can be associated with each DPS:

• T00: delay for the MOTION00 state filtering,
• T11: delay for the MOTION11 state filtering.
Both delays are in the range 0 to 60 s by step of 100 ms. A value of 0 means that no filter is
applied.

• Mode 1: the valid state (OPEN or CLOSE) is time-stamped with the time of the beginning of
the MOTION state,
• Mode 2: the valid state (OPEN or CLOSE) is time-stamped with the time of this valid
transition.
This time stamping can be superseded if a persistence filtering applies.
If the MOTION state is confirmed, it is always time-stamped with the time of the beginning of the
MOTION state. Furthermore, the BI takes the state JAMMED (in event of confirmed MOTION00
state) or UNDEFINED (in event of confirmed MOTION11 state). In this case, the following valid
state (OPEN or CLOSE) is always time-stamped with the time of this valid transition (depending
on the persistence filtering feature).
164 C264/EN UM/E50.5

- Figure 27 - motion filtering
4.4.1.4.2 DPS persistence filtering

For some DPS, a valid state (OPEN or CLOSE) is confirmed on a certain period. If a transition
occurs before this delay, the state is discarded.
Two time-out values can be associated with each DPS:

• TC: delay for the CLOSE state confirmation,
• TO: delay for the OPEN state confirmation.
Both delays are in the range 0 to 60 s by step of 100 ms. 0 means that no filter is applied.

• Mode 1: the status is time-stamped with the time of the transition,
• Mode 2: the status is time-stamped at the end of the delay.
NOTE: If a persistence filtering is applied, the OPEN or CLOSE state cannot be time-stamped
from the beginning of non-complementarity: that is, mode 1 of motion filtering cannot apply.
C264/EN UM/E50.5 165

- Figure 28 - DPS persistence filtering
4.4.1.4.3 DPS resulting states

The DPS resulting states are:
States
JAMMED
MOTION
OPEN
CLOSE
UNDEFINED
TOGGLING
SELFCHECK FAULTY
UNKNOWN
SUPPRESSED
FORCED JAMMED
FORCED OPEN
FORCED CLOSED
SUBSTITUTED JAMMED
166 C264/EN UM/E50.5

States
SUBSTITUTED OPEN
SUBSTITUTED CLOSED
Each DPS state is configurable to be seen by automation in False, True or Invalid state.
MOTION states are the valid intermediate states of the Double Point Status (DPS), when the DPS
state changes from OPEN to CLOSE or from CLOSE to OPEN. MOTION states are not managed
in event of REPORT data transmission.
4.4.1.4.4 Mapping of DPS states on IEC 61850 station bus

On IEC 61850 station bus, the DPS states are mapped on IEC 61850 value/quality and seen by
C264/EN UM/E50.5 167

168 C264/EN UM/E50.5

4.4.1.4.5 DI/DO association for DPS
CAUTION
The aim of this automation is to create a direct association between a Double Point and a Digital
Output: a state change on the input produces the opening or the closure of the output.
The relation between the state and the order is defined during the configuration phase.
4.4.1.5 Processing of Multiple Point

A Multiple Point (MP) is derived from N Digital Inputs. It could be also called “1 among N” BIs.
Transient filtering is also added on acquisition for the events where no digital Inputs is SET or
more than one digital Inputs are SET. After this delay, the MP becomes UNDEFINED.
N is fixed by BCPU configuration from 2 to 32. There is no GOOSE transmission mechanism.
You can use an MP in two ways:

• As a status where N is limited to 16;
this kind of MP is called Multiple Point Status (MPS).
• As a value, only for TPI where N is limited to 64;
this kind of MP corresponds to a Tap Position Indicator (TPI)
- Figure 29 - Multi point status processing
The TPI (MP as value) resulting states are defined in chapter Tap Position Indication (TPI)
measurement processing.
4.4.1.5.1 Multiple Point filtering

MP is not being considered in the UNDEFINED state if the position has changed by more than
one step.
C264/EN UM/E50.5 169

MP is UNDEFINED after a user selectable time filtering (from 0 to 60 seconds, step 100 ms) when
no DI is in the SET state (all RESET) or if more than one are in the SET state:
- Figure 30 - Multiple Point filtering
The MP is time-tagged with the date of the last BI change.
4.4.1.5.2 MPS resulting state

The MPS resulting states, following the various filters that can be applied, are:
States
STATE0 ..
STATE15
UNDEFINED
TOGGLING
SELFCHECK FAULTY
UNKNOWN
SUPPRESSED
FORCED STATE0 .. FORCED STATE15
SUBSTITUTED STATE0 ..
SUBSTITUTED STATE15
4.4.1.5.3 Mapping of MPS states on IEC 61850 station bus

On IEC 61850 station bus, the MPS states are mapped on IEC 61850 value/quality and seen by
170 C264/EN UM/E50.5

4.4.1.6 System Inputs (SI)

System inputs (SI) are binary information related to:
• An equipment or system internal state, such as inoperative hardware or system faults
• A configurable or built-in automation (status of the automation, binary input created by the
automation, …)
• Electrical process data that have no acquisition possibilities: no acquisition through DI or
through serial communication. However, they have to be managed by BCPU. The status of
those data is saved in non-volatile memory.
An SI is of SPS, DPS or MPS type and can belong to any type of group.
The processing of a SI is given in the SPS / DPS / MPS data flow.
4.4.1.7 IED binary inputs

Binary inputs can be acquired from IEDs or protective relays via serial links.
C264/EN UM/E50.5 171

If they are not time tagged by the IED, they are by the computer at the time of reception. This must
be configured for each IED.
An IED binary input is of SPS, DPS or MPS type.
Double inputs can be processed in IEDs. If they are not, the computer receives each individual
input and perform the DPS processing. This must be configured for each IED.
The processing of an IED binary input is given in the SPS / DPS / MPS data flow.
4.4.1.8 Group processing

A group is a logical OR, AND, NOR (NOTxOR) or NAND (NOTxAND) combination of SPS or
DPS.
A group is calculated with filtered BIs (persistent filtering or motion filtering if configured).
A group is processed as a SPS. It is time stamped with the date / time of the last SPS/DPS that
has modified the group status. SPS/DPS composing a group can be “BI server” or “BI client”. In
this last case, time stamping is taken at the source given by IEC 61850 repots.
A group SPS can be a component of another group SPS.
The binary inputs states are considered as follows:
Single Point Status treated in a group as

SET, FORCED SET,
SET
SUBSTITUTED SET
RESET, FORCED RESET, SUBSTITUTED
Reset
RESET
Selfcheck Faulty, Toggling, Unknown Invalid
Suppressed Suppressed
Double Point Status treated in a group as

Close, FORCED CLOSE, SUBSTITUTED
Set
CLOSE
Open, FORCED OPEN, SUBSTITUTED
Reset
OPEN
FORCED JAMMED, SUBSTITUTED
JAMMED, Selfcheck Faulty, Toggling, Invalid
Unknown
Jammed, Undefined VALID (*)
Suppressed Suppressed
(*): VALID means the DPS keeps its previous state. So, there is no impact on the result.
172 C264/EN UM/E50.5

OR Set Reset Invalid Suppressed

Set Set Set Set Set
Reset Set Reset Invalid Reset
Invalid Set Invalid Invalid Invalid
Suppressed Set Reset Invalid Suppressed
AND Set Reset Invalid Suppressed

Set Set Reset Invalid Set
Reset Reset Reset Reset Reset
Invalid Invalid Reset Invalid Invalid
Suppressed Set Reset Invalid Suppressed
NOR Set Reset Invalid Suppressed

Set RESet RESet RESet RESet
Reset RESet set Invalid set
Invalid RESet Invalid Invalid Invalid
Suppressed RESet set Invalid Suppressed
NAND RESet set Invalid Suppressed

Set RESet set Invalid RESet
Reset set set set set
Invalid Invalid set Invalid Invalid
Suppressed RESet set Invalid Suppressed
SPS/DPS from different hierarchical levels can be mixed, for instance a group at substation
computer level can be composed of SPS/DPS acquired at bay computer level or at substation
computer level.
4.4.1.9 SBMC Mode Processing

When a Bay is in Site Based Maintenance Control (SBMC) mode, the status of the Binary Inputs
(related to this Bay and defined as “SBMC dependant”), takes the forced state defined in the
configuration.
This forced information is delivered to the Remote Control Point (RCP) as long as the SBMC
mode is active on the Bay.
C264/EN UM/E50.5 173

For a group a special feature is implemented: a BI belonging to a group, that is dependent of

SBMC bay state, is not taken into account in group computation if the bay is set in SBMC mode. If
all the BI of a group belong to one or more bays, that are all in SBMC mode, the group is then in
the suppressed state. At the end of a bay SBMC mode, all groups owning BI of this bay are re-
computed.
4.4.1.10 BI sent to automation features

In event that an automation operates on a client computer, with BI information coming from a
server computer, BI are generally transmitted in the IEC 61850 GOOSE based mode. When
GOOSE are not available (for instance BI coming from IEC 61850 third-party device not
supporting GOOSE), IEC 61850 Reports are used to retrieve BI client information.
When GOOSE based mode and report based mode are used at the same time, the BI information
used is the one received by GOOSE (faster transmission than reports).
4.4.1.11 Toggling signal detection

The Toggling Signals SPS is a computed SPS belonging to a bay.
The Toggling Signals SPS is used to know if there is at least one datapoint with quality “toggling”
in the bay. While there is one or more datapoint in the quality “toggling”, the Toggling Signals SPS
value is TRUE.
While there is none datapoint in the quality “toggling”, the Toggling Signals SPS is FALSE.
If a datapoint in “Toggling” state is forced, substituted or suppressed, it shall be considered not

toggling anymore for the elaboration of the “Toggling Signals” SPS.
For more information, refer to chapter AP Defining a Bay/Adding toggling signal detection.
4.4.1.12 Missing Signaling Voltage (MSV)

The Missing Signaling Voltage (MSV) is an SPS acquired locally and physically by the bay
computer.
This MSV SPS is used to monitor the presence of a voltage polarity.
When the polarity is missing, the value of the MSV SPS is “0” (RESET).
When the polarity is present, the MSV SPS value is “1” (SET).
Datapoints, locally and physically acquired by the bay computer, such as SPS, DPS, MPS and
MV, can be linked to an MSV SPS.
Computation of quality of the datapoints linked to MSV SPS:
MSV SPS Linked Datapoints

Value Quality Quality
SET VALID(1) Normally computed
SET INVALID SELF-CHECK FAULT
RESET VALID(1) SELF-CHECK FAULT
RESET INVALID SELF-CHECK FAULT
(1): FORCED, SUBSTITUTED and SUPPRESSED qualities count as VALID
174 C264/EN UM/E50.5

If a change of Value or Quality of the MSV SPS brings a change of Quality for the linked
datapoints, this change is timestamped with the Value or Quality change of the MSV SPS.
For more information, refer to chapter AP Defining a Bay/Adding Missing Signaling Voltage.
4.4.2 Measurement Input Processing

Measurement Values (MV) can be Analogue measurements or Digital Measurements. MV are
acquired:
• For DC: AIU211
• For AC: TMU2xx
• Via IEDs connected to computer with a serial/ethernet link
We examine the following processing features:

• Open circuit management
• Scaling
• Zero value suppression
• Threshold detection
• CT/VT calculations
These features are sequenced as described in this figure:
- Figure 31 - Process of a Measurement Value
4.4.2.1 Analogue Measurement Processing

4.4.2.1.1 Open circuit management
For 4-20 mA transducers, a special feature is implemented to avoid fleeting values around
4 mA:
• in the range [0 .. 3 mA ], the measurement value is set to 0 and the status is set to OPEN
CIRCUIT,
• in the range [3 .. 4 mA], the analogue input is equal to 0 mA.
C264/EN UM/E50.5 175

4.4.2.1.2 Scaling
The real value represented by the measurement can be computed by a linear or a quadratic
transformation:
• Linear, single slope:
Value = A*X + B,
• Linear, multi-segments:
Value = Ai*X + Bi with Xi≤X<Xi+1 .
As many as 20 configurable segments [Xi .. Xi+1],

• Standard quadratic:
Value = A +B
• Quadratic with offset:
Value = ,
Transformation law and A / B coefficients are defined in configuration.
4.4.2.1.3 Zero value suppression

The function Y=f( X) representative of this processing is defined as follows:
• if XÎ[ -deadband/2, +deadband/2] Þ Y=0 and state = VALID,
• if XÏ[ -deadband/2, +deadband/2] Þ Y=X and state = VALID.
where:
• X is an analogue measurement,
• deadband is a percentage of the full scale value of the measurement. These two parameters
are set during the configuration of the computer.
176 C264/EN UM/E50.5

- Figure 32 - Zero value suppression
4.4.2.2 Digital Measurement Processing

A Digital Measurement is derived from a Digital input. Digital Measurements are used for process
measures or Tap indications.
For the conditions that follow, the DM is UNDEFINED:

• The value is not stable,
• BCD: a quartet is more than 9,
• Decimal: no bit is set or more than one for tens or unit.
Two other bits can be used:

• For read inhibit: in this event, the DM is acquired when the Read Inhibit bit is set,
• For the sign.
4.4.2.3 TMU2XX: CT/VT measurement processing

It is impossible to plug the computers directly into the high voltage electric network. The
computers receive the data from the Current Transformers (CT) and from Voltage Transformers
(VT) installed on the TMU2XX boards.
The purposes of the CT and VT include:

• To deliver current and voltage data that gives a reliable picture of what happens in the high
voltage part of an electrical substation,
• To make the galvanic insulation between the high voltage part and the measurement and
protection circuits,
• To protect the measurement circuits against damage when a fault comes onto the high
voltage network.
A given electrical network sends current (I) and voltage (V) data to a CT / VT inputs acquisition
function installed on a TMU2XX board.
C264/EN UM/E50.5 177

From the output of the CT / VT inputs acquisitions function, these samples become inputs of the
CT / VT calculation function.
The CT / VT calculation functions performs basic mathematical processing on the memorized

samples and gives this set of computed measurements, such as power, frequency, and so on, to
the MiCOM C264 main CPU, the Power PC (PPC).
These measurements are used for the protection function and for the Internal Synchrocheck,
Type 1.
- Figure 33 - Overview: TMU220 board - CT/VT calculations
- Figure 34 - Overview: TMU210 board - CT/VT calculations
4.4.2.3.1 TMU2XX: CT/VT Calculations - General

The voltage measurements come from the VT installed on the TMU2XX boards. There are 2
possibilities for the number of busbar voltages and protection attributes of the computer.
178 C264/EN UM/E50.5

CTVT Number of Wired Protection Busbar selection for Synchrocheck

Board Busbar voltages Attributes synchrocheck(*) type
TMU210 1 Yes External Type 1 and 2
TMU220 2 No Internal Type 1
(*): Via specific SPS datapoint on synchrocheck function that is managed internally for TMU220,
or is wired for TMU210.
CT / VT measurements are provided by 2 couples or combinations of boards:

• DSPIO + TMU210 (4 CT and 4 VT), referred to as the DSPIO211 board installed on TMU210,
• DSP + TMU220 (4 CT and 5 VT), referred to as the DSP200 board installed on TMU220,
The TMU boards have the same hardware attributes, except that TMU220 has one more VT.
TMU220
The DSP board computes the samples from the TMU220 and sends the set of computed
measurements to the PPC.
- Figure 35 - Detail: TMU220 boards - CT / VT Calculations
TMU220 BOARDS – Signals, Ratings, and Range:

• Va, Vb, Vc, Vbusbar1, Vbusbar2 range: 57V thru 480V
• Ia, Ib, Ic, Ir rating: 1A or 5A
TMU210
TMU210 board is oriented towards protection. The DSPIO board computes the samples from the
TMU210 analogue inputs, and from the digital inputs and digital outputs located on the DSPIO
board. The DSPIO Board sends the set of computed measurements to the CPU275 board of the
MiCOM C264.
C264/EN UM/E50.5 179

- Figure 36 - Detail: TMU210 boards - CT / VT Calculations
TMU 210 BOARDS

Signals Rating Range
Va, Vb, Vc, Vo,
NA 57V to 130V
Vbusbar
Ia, Ib, Ic, 1A or 5A 0.1 to 40 In
Io normal: 1A or 5A
Io normal:
0.1 to 40 Ion
Normal
Io normal:
0.01 to 8 Ion
Sensitive
Io normal: Very
0.002 to 1 Ion
sensitive
CT / VT Functions
These functions use the measurements from the TMU2XX boards:

• Internal synchrocheck: Type 1 and Type 2,
• Protection,
• Waveform.
The CT/VT measurements can be included in the waveform function. Two types of waveform are
defined: fast waveform and slow waveform.
180 C264/EN UM/E50.5

Internal Internal Fast

Slow
Board synchrocheck synchrocheck Protection waveform
waveform
Type 1 Type 2 (Disturbance)
DSPIO+TMU210 X X X X
DSP+TMU220 X X X
4.4.2.3.2 TMU220: CT/VT Calculations – Inputs Configuration

Depending on the electrical system configuration, these parameters are defined:
• Nominal Network frequency: 50 or 60 Hz,
• Nominal voltage of the VT: 57-130V or 220-480V,
• Nominal current of the CT: 1A or 5A,
• Connection type: star or delta,
• Reading cycle measurement: from the UC,
• Measurement quality when missing: FAULTY or VALID value 0,
• Reference voltage,
• Phase reference side for synchrocheck,
• Voltage ref change mode for frequency tracking: current or default.
4.4.2.3.3 TMU220: CT /VT Calculations - Inputs: samples

The inputs of the CT / VT Calculation function (issued from the conventional CT/VT inputs)
include:
In case of star coupling:

• Samples of Ia,
• Samples of Va,
• Samples of Ib,
• Samples of Vb,
• Samples of Ic,
• Samples of Vc,
• Samples of Io or Ibb1,
• Samples of Vbb1 (Vr) or VBUSBAR in event of the presence of the synchrocheck function,
• Samples of Vbb2 or VBUSBAR2 in event of presence of the synchrocheck function,
• Validity of each sample.
In case of delta coupling:

• Samples of Ia,
• Samples of Ib,
• Samples of Ic,
• Samples of Io or Ibb1,
C264/EN UM/E50.5 181

• Samples of Vab,
• Samples of Vbc,
• Samples of Vca,
• Samples of VBUSBAR1 or Vbb1,
• Samples of VBUSBAR2 or Vbb2,
• Validity of each sample.
Per period, 64 samples are available.
4.4.2.3.4 TMU220: CT/VT Calculations – Outputs: set of measurements

The CT / VT calculation function delivers:
• RMS currents and voltages,
• Frequency,
• Active power P (Watts – total and on a per phase basis),
• Reactive power Q (Vars – total and on a per phase basis),
• Apparent power S (VA – total and on a per phase basis),
• Power factor pf (total and on a per phase basis) – pf = P / S,
• Sequence components: Id, Ii, Io, Vd, Vi,
• Phase angles,
• Total Harmonic Distortion (THD) & Total Demand Distortion (TDD) – Harmonics are
evaluated through to the 15th order (for the 3 Vpn, the 3 currents for each phase, and the 3
Vpp),
• Fundamental (H1 harmonic) of phase A current,
• Fundamental (H1 harmonic) of phase B current,
• Fundamental (H1 harmonic) of phase C current,
• Fundamental (H1 harmonic) of phase A voltage,
• Fundamental (H1 harmonic) of phase B voltage,
• Fundamental (H1 harmonic) of phase C voltage,
• Fundamental measurements,
• Synchrocheck data: ΔF,ΔV, ΔΦ,
• With the synchrocheck option, the values that follow are computed:
• Slip frequency,
• Amplitude,
• Phase difference,
• Synchrocheck voltage.
These measurements are delivered at every measurement reading cycle defined by the
configuration.
182 C264/EN UM/E50.5

By a configuration option (measurement quality when missing at computer level), two different
behaviors when all the Input signals disappear: all below the minimum thresholds, 10V for voltage
and 100mA for current:
• Behavior 1: the measures associated to the acquired signals are set to value 0 and state
VALID,
• Behavior 2: the measures associated to the acquired signals are set to state FAULTY.
4.4.2.3.5 TMU220: Measurements - General

Whatever the signal frequency, 64 samples are available for all the input signals.
All these samples are gathered in a revolving list stored in active memory.
A timer is adapted permanently to the frequency of the signal and provides the frequency
measurement.
The primary measurements that follow are derived from sample values:
• RMS Current and Voltage,
• P: Active Power (Watts),
• Q: Vars (Using Active Power calculation method with the voltage samples retarded by 90°).
The measurements that follow are obtained from the Fourier of sample values or the Fourier
values of the above-derived measurements (DFT).
• V Sequence Components,
• I Sequence Components,
• Fundamental and harmonics,
• Phase angles,
• Power Factor,
• S Apparent power in VA,
• Total Harmonics Distortion (THD) and Total Demand Distortion (TDD),
• Specials (for products with check-sync.).
4.4.2.3.6 TMU220: List of Measurements
Accuracy (
Measurements Star delta Unit
TMU220)
RMS current
F < 70hz:
phase
I< In: 0.2% of In
Ia
I>In: 0.2% of I Ampere
Ib samples samples
F>70Hz:
Ic
I< In: 4% of In
Ir
I>In: 4% of I
Ibusbar1
C264/EN UM/E50.5 183

Accuracy (
TMU220)
F<70Hz
RMS Volt phase U<45V: 0.3% of

45
Va samples
45v<U<200v:
Vb samples
0.2% of U
Vc samples Not available Volts
U>200V: 0.3%of
Vr computed U
Vbusbar1 samples F>70Hz
Vbusbar2 samples U<45V: 4% of 45
U>45V: 4% of U
F<70Hz
RMS volt phase U<45V: 0.3% of

45
Vab samples
Computed 45v<U<200v:
Vbc samples
Computed 0.2% of U
Vca samples Volts
Computed U>200V: 0.3%of
Vr computed U
Computed
Vbusbar1 samples F>70Hz
Vbusbar2 samples U<45V: 4% of 45
U>45V: 4%of U
Frequency computed computed Hertz
Power Phase A
Active power ( P )
Samples Watts
Reactive power
(Q) Samples 0.5 % (Phi = 0 °) Vars
Not available
Apparent power Computed VA
(S)
Computed
Cos phi
computed Degree
angle
184 C264/EN UM/E50.5

Accuracy (
TMU220)
Power Phase B
Active power ( P )
Samples Watts
Reactive power
Not available
(S)
Computed
Cos phi
computed Degree
angle
Power Phase C
Active power ( P )
Samples Watts
Reactive power
Not available
(S)
Computed
Cos phi
computed Degree
angle
Power r
Active power ( P )
Samples Watts
Reactive power
(Q) Samples Vars
Not available
(S)
Computed
Cos phi
computed Degree
angle
Power total
Active power ( P )
Watts
Reactive power
(Q) Vars
computed computed
Apparent power VA
(S)
Cos phi
Degree
angle
C264/EN UM/E50.5 185

Accuracy (
TMU220)
V Sequence
components
Direct
DFT computed Not available volts
Inverse
Homopolar
ratio
I Sequence
components
Direct
DFT computed DFT computed Ampere
Inverse
Homopolar
ratio
Harmonics for Va
Fundamental
DFT DFT Volts
15 Harmonic
distortion ration
Harmonics for Vb
Fundamental
DFT DFT Volts
15 Harmonic
distortion ratio
Harmonics for Vc
Fundamental
DFT DFT Volts
15 Harmonic
distortion ratio
Harmonics for
Vab
Fundamental DFT DFT Volts

15 Harmonic
distortion ration
186 C264/EN UM/E50.5

Accuracy (
TMU220)
Harmonics for
Vbc

15 Harmonic
distortion ratio
Harmonics for
Vca

15 Harmonic
distortion ratio
Harmonics for Ia
Fundamental
DFT DFT Ampere
15 Harmonic
distortion ratio
Harmonics for Ib
Fundamental
DFT DFT Ampere
15 Harmonic
distortion ratio
Harmonics for Ic
Fundamental
DFT DFT Ampere
15 Harmonic
distortion ratio
Delta F computed computed Hertz
Delta phi computed computed Degree
Delta V computed computed Volts
4.4.2.3.7 TMU220: Algorithms

The computation uses 2 methods to calculate the frequency:
• The FFT computation (by default),
• The zero crossing method.
Use the EPAS-SCE frequency tracking algorithm parameter to choose the method
Frequency
The frequency is directly computed through the timer frequency.
The reference phase used to set the timer frequency is chosen in the configuration (“reference
phase”).
C264/EN UM/E50.5 187

Frequency tracking is performed according to the following order:
1. on reference voltage defined in configuration ( higher priority ),
2. Vbusbar,
3. Vbusbar_bis (if TMU220 is used),
4. VB and then VC if the reference voltage if VA,VC and then VA if the reference voltage if VB,VA
and then VB if the reference voltage if VC,
5. I1,
6. I2,
7. I3,
8. I4 (lower priority),
A configuration option (“voltage ref change mode”) allows choosing 2 different behaviors of the
frequency tracking:
• Behavior 1 – Default Voltage Reference:
• When the signal with the highest priority disappears, the frequency tracking is performed on
the signal with next priority,
• When a signal with a higher priority appears, the frequency tracking is performed on this
signal, even if the current reference signal is still present.
• Behavior 2 – Current Voltage Reference:
• When the signal with the highest priority disappears, the frequency tracking is performed on
the signal with next priority,
• Even when a signal with a higher priority appears, the frequency tracking remains on the
current reference signal.
During the reference change computation, all the measurements are considered as INVALID
(SELFCHECK FAULT).
Frequency computation
Algorithm calculates period by zero crossing method, on leading edge and on trailing edge,
average result of this both measurement generated frequency used. The frequency computation
is filtered with period numbers setup with SCE (75 periods by default or 1.5 s for 50 Hz).
Fourier Transform
At each period, the DFT (Discrete Fourier Transform) is performed. This gives (among other
things) the value of the phase angle and the magnitude of the fundamental.
RMS values
Powers phase in star coupling
Active power: Pa, Pb, Pc
188 C264/EN UM/E50.5

Reactive power: Qa, Qb, Qc
The reactive power is computed by taking the values of the current a quarter of period before [ sin
(x) = cos (x – pi/2) ]
Star Coupling: Total Power
Delta Coupling: Total Active Power
Delta Coupling: Total Reactive Power
The reactive power is computed by taking the values of the current a quarter of period before [
sin(x) = cos (x – pi/2) ]
Apparent power:
Power factor:
Angle:
Harmonics
Harmonic values are directly issued from the DFT.
Sequence components
The sequence component computation is based on the fundamental values of phase and
magnitude (from the DFT): that is its imaginary part and real part.
C264/EN UM/E50.5 189

• Direct component
• Inverse component
• Homopolar component
Synchrocheck measurements:
DF = | Fline – Fbusbar |
DV = | Vline – Vbusbar |
Dj= | jVline – j Vbusbar
4.4.2.3.8 TMU210: CT/VT Calculations - Inputs: Configuration

Depending on the electrical system configuration, the following parameters are defined:
• Nominal Network frequency (50 or 60 Hz),
• Nominal phase voltage of the VT (57-130V),
• Nominal earth voltage of the VT (57-130V),
• Nominal phase current of the CT (1A or 5A),
• Nominal earth current of the CT (1A or 5A),
• Earth current origin (computed or wired),
• Sensitivity of the earth CT (normal, sensitive, very sensitive),
• CT ratio of the EPATR tore,
• Connection type (3Vpn,3Vpn+Vo, 2Vpn+Vo, 2Vpp+Vo,3Vpp+Vo, 3Vpn+Vb, 3Vpp+Vo),
• Reading cycle measurement (from the PPC).
4.4.2.3.9 TMU210: CT/VT Calculations - Inputs: Samples

With the TMU210 board with respect to the type of connection, some restrictions exist because of
the fourth VT.
At this time, please refer to the topic Phase-to-Phase Synchrocheck with the TMU210 – General
and to the Table: TMU210 Type of Connection: Direct or Indirect.
190 C264/EN UM/E50.5

The inputs of the CT / VT Calculation function (issued from the Conventional CT/VT inputs)
includes up to 4 current and 4 voltage analogue measurements. By configuration, these analogue
measurements can be phase to phase or single phase depending on delta or star coupling and
the fourth voltage analogue measurement can be associated to the busbar voltage.
32 samples per period are available.
4.4.2.3.10 TMU210: CT/VT Calculations – Outputs: Set of measurements

The CT / VT calculation function delivers:
• RMS currents and voltages,
• Frequencies,
• Fundamental measurement and Derived value,
• Current – voltage angle,
• Total Active power P,
• Total Reactive power Q,
• Power factor Pf or cos phi,
• Thermal status,
• I2t measurement,
• Synchrocheck data: ΔF ΔV ΔΦ,
• With the synchrocheck option, the values that follow are computed:
• Slip frequency,
• Amplitude,
• Phase difference,
• Synchrocheck voltage.
These measurements are delivered at every measurement reading cycle defined by the
configuration.
4.4.2.3.11 TMU210: Measurements - General

Whatever the signal frequency, 32 samples are available for all the input signals.
All these samples are gathered in a revolving list stored in active memory.
A timer is adapted permanently to the frequency of the signal and provides the frequency
measurement.
The primary measurements that follow are derived directly from sample values:
• RMS: Current and Voltage,
• It and I2t measurements,
• Thermal status.
The following measurements are obtained from the Fourier of sample values or from the Fourier
values of the derived measurements (DFT ):
C264/EN UM/E50.5 191

• DFT: Current and Voltage,
• DFT Sequence Components: Current and Voltage (positive and negative),
• Current voltage angle,
• Active phase Power,
• Active earth Power,
• Reactive phase power,
• Power Factor,
• Synchrocheck measurements.
4.4.2.3.12 TMU210: List of Measurements
Measurements Accuracy Unit

RMS current
phase
Rms_Ia
2% In
Rms_Ib
Rms_Ic
Rms_Io
RMS Voltage
phase
Rms_Va_Vab
Rms_Vb_Vbc 2% Volts
Rms_Vc_Vca
Rms_Vo
Rms_Vbusbar
Frequency
F: frequency 0.01Hz
tracking
Hertz
F81: frequency
Hertz
used by 81
Index of F
Index of F81
0.03Hz/sec Hertz/sec
Rate of
frequency_81
192 C264/EN UM/E50.5


DFT current
phase
In
Ia
In
Ib
2% In
Ic
Ion
Io
Ion
Io_computed
ampere
EPATR Io
DFT Voltage
phase
UA
UB
UC
2% Volts
UAB
UBC
UCA
Uo
Ubusbar
DFT Sequence
voltage
volts
U_positive
U_negative
DFT Sequence
current
In
I_positive
I_negative
Total power
Active phase
power ( P )
Watts
Active earth
<3% watts
power(Po)
<3% Vars
Reactive power
(Q)
Cos phi
C264/EN UM/E50.5 193


Thermal status %
IT measurement
IT phase A
IT phase B Ampere / second
IT phase C
IT total
I2t measurement
I2T phase A
I2T phase B Ampere²/second
I2T phase C
I2T total
Synchrocheck
Delta F
Hertz
Delta V
Volts
Delta phi
Degree
Freq line
Hertz
Freq bar
Hertz
Phase Angle
Degree
Anticipation
angle Degree
Shift freq %
Acceleration shift %
freq
4.4.2.3.13 TMU210: Algorithms

The computation uses the zero crossing method to calculate the frequency:
Calibration
3 calibration parameters are stored in EEPROM for each input:

• Amplitude,
• Phase,
• Offset.
The offset correction has to be re-evaluate in real time and not in static way.
So, the offset correction is made by a low pass filter (0.5Hz) and the offset parameter stored in
EEPROM is not used.
The amplitude offset is used at each acquisition cycle.
194 C264/EN UM/E50.5

Frequencies
Frequency tracking
The frequency tracking is made by calculating the frequency of a voltage or current channel. For
each channel a minimum threshold is used to validate the signal (1 volt for VT, 0.1A pour CT).
If a tracking is done on a channel, there is no change until the value of this channel becomes
lower than the threshold. There is no hysteresis on them. The channel changing respects the
following list:
• Vbusbar (first),
• V1
• V2,
• V3,
• I1,
• I2,
• I3 (last).
Frequency computation
Algorithm calculates period by zero crossing method, on leading edge and on trailing edge,
average result of this both measurement generated frequency used. The frequency computation
is filtered with period numbers setup with EPAS-SCE (75 periods by default or 1.5 s for 50 Hz).
The first phase voltage channel over minimum threshold (Umin_F_enable) is selected, then a
filter FIR is applied to reject harmonic. Between 2 computations of the frequency, if the frequency
change is more than 20Hz/s (equals to a brutal step 400mHz at 50Hz), then the frequency
calculation will be frozen and INVALID during 7 cycles (for example, at 50Hz the frequency will be
frozen during 120ms)
Frequency81 and frequency rating computation
According to the configuration parameter “VT_connection”, there are 2 events:

• VT_connection = 3Vpn or 3Vpn+Vo or 2 Vpn+Vo or 2Vpp+Vo or 3Vpp+Ve
→ Frequency81 computation without priority

• VT_connection = 3Vpn +Vb or 3Vpp+Vb
→ Frequency81 computation with priority
Frequency81 computation without priority
The first voltage upper than the threshold (Umin_F_enable, SEE GPS 8) is given as reference.
When this voltage goes down the threshold, the next voltage is tested as reference.
The cycle of reference test is V1, V2, V3, V1, V2 …etc
Frequency81 computation with priority
In priority, V4 (bus bar voltage) is used for reference comparing to the threshold. If this voltage
goes down the threshold, a valid line voltage is searched. When the bus bar voltage is detected
back over the threshold, the bus bar VT is reassigning to be the frequency tracking reference.
RMS measurements
C264/EN UM/E50.5 195

The RMS measurement of the last period recorded is calculated as the square root of the square
sum of the samples in the period divided by the number of samples examined.
The square sum is calculated every period (32 samples recordings).
3Vpn 3Vpn+Vo 2Vpn+Vo 2Vpp+Vo 3Vpp+Vo 3Vpn+Vb 3Vpp+Vb

Rms_IA Rms_IA
Rms_IA Rms_IB
Rms_IC Rms_IC
Rms_Io Rms_Io
Rms_UA_ Rms_ Rms_
Rms_UA Rms_UA Rms_UA Rms_UA Rms_UAB
UAB UAB UAB
Rms_UB_ Rms_ Rms_
Rms_UB Rms_UB Rms_UB Rms_UB Rms_UBC
UBC UBC UBC
Rms_UC_ NOT NOT Rms_
Rms_UC Rms_UC Rms_UC Rms_UCA
UCA VALID VALID UCA
NOT NOT NOT
Rms_Uo Rms_Uo Rms_Uo Rms_Uo Rms_Uo
VALID VALID VALID
Rms_U_ NOT NOT NOT NOT NOT Rms_u_ Rms_u_
busbar VALID VALID VALID VALID VALID busbar busbar
Fundamental measurements
General
The instantaneous direct effective fundamental measurement, to be utilised by the protections, is

supplied every samples reception frame, in terms of both module and phase as well as that for the
real part and the imaginary part of the current vector. This is calculated using the Fourier
transform (DFT), applied to the samples of the last period recorded (32 samples) and expressed
in ADC points.
So, a multiplier coefficient is necessary to scale them in the appropriated unit.

Mod_IA Direct
Mod IB Direct
Mod IC Direct
Mod Io Direct
Mod_UA Direct Direct Direct Derived Derived Direct Not valid
Mod _UB Direct Direct Direct Derived Derived Direct Not valid
196 C264/EN UM/E50.5


Mod _UC Direct Direct Derived Derived Derived Direct Not valid
Mod _UAB Derived Derived Derived Direct Direct Derived Direct
Mod _UBC Derived Derived Derived Direct Direct Derived Direct
Mod _UCA Derived Derived Derived Derived Direct Derived Direct
Mod _Uo Derived Direct Direct Direct Direct Derived Not valid
Mod _U_
Not valid Not valid Not valid Not valid Not valid Direct Direct
busbar
Mod_I1 Derived
Mod_I2 Derived
Mod_V1 Derived
Mod_V2 Derived
Ioc Derived
Conversion
• KUADC is the number of ADC points corresponding to a phase voltage of 1V to the secondary
side.
• KUoADC is the number of ADC points corresponding to an earth voltage of 1V to the
secondary side.
• KIADC is the number of ADC points corresponding to the nominal phase current to the
secondary side.
• KIoADC is the number of ADC points corresponding to the nominal earth current to the
secondary side.
• X is the value of the module expressed in ADC points (X = I, Io, Uxy, Uo)
• X” is the effective value of the module expressed in voltage or ampere to the primary side (X =
I, Io, Uxy, Uo).
Direct measurements
The real and the imaginary part are determined using the DFT method.
C264/EN UM/E50.5 197

The real part and the imaginary part of every received valid sample are calculated.
Derived measurements
Voltages
3Vpn 3Vpn+Vo 2Vpn+Vo 2Vpp+Vo 3Vpp+Vo 3Vpp+Vb 3Vpn+Vb
(kVo +2V1 – (kVo +V1

UA V1 V1 V1 Not valid V1
V2)/3 – V3)/3
(kVo +V2 (kVo +V2
UB V2 V2 V2 Not valid V2
–V1)/3 – V1)/3
kVo – V1- (kVo-V1 + (kVo-V3 +
UC V3 V3 Not valid V3
V2 2V2)/3 V2)
UAB V1-V2 V1-V2 V1-V2 V1 V1 V1 V1-V2
2V2+V1-
UBC V2-V3 V2-V3 V2 V2 V2 V2-V3
kVO
kVO-2V1-
UCA V3-V1 V3-V1 V1-V2 V3 V3 V3-V1
V2
k-1 k-1 k-1
UO (V (V Not valid (V
1+V2+V3) 1+V2+V3) 1+V2+V3)
k-1
U
(V Not valid Not valid Not valid Not valid
busbar
1+V2+V3)
k The earth to phase adaptation coefficient - (necessary for expressing the earth ADC points
in phase ADC points) amounting to:
Positive and negative sequence current
The definition of positive sequence current, I1, indicates the current vector obtained by the sum of
the phase A vector, plus the phase B vector rotated by 120° in advance plus the phase C vector
rotated by a lag of 120°.
The definition of the negative sequence current, I2, indicates the current vector obtained by the
sum of the phase A vector, plus the phase B vector rotated by a lag of 120° plus the phase C
vector rotated by 120° in advance.
Derived vectors:
198 C264/EN UM/E50.5

Positive sequence current I1 IA+(IB-120°)+(IC+120°)

Negative sequence current I2 IA+(IB+120°)+(IC-120°)
Where the writing <IB/C+/-120°> points out that the vector is considered rotated of +/- 120°
Positive and negative sequence voltage
Derived vectors:
3Vpn, 3Vpn+Vo, 2Vpn+Vo 3Vpp+Vo, 2Vpp+Vo,

3Vpn+Vb 3Vpp+Vb
Positive sequence (UA+(UB+120°)+ (UA+(UB+240°)+
U1
voltage (IC+240°))/3 (IC+120°))/3
Negative sequence
U2 (UA-(UB-120°))/3 (UA-(UB+120°))/3
voltage
Where the writing <UB/C+/-alfa> points out that the vector is considered rotated of +/- alfa
Computed Homopolar current
In order to use the protective function 67N in several specific conditions, the Homopolar current
must be computed from the values of the 3 phase currents:
The generic current vector
Re(…) The operator that returns the real part of a generic vector;
Im(…) The operator that returns the imaginary part of a generic vector;
k The earth to phase adaptation coefficient - (necessary for expressing the earth ADC points in
phase ADC points) amounting to:
The real and imaginary part of the derived current vectors, expressed in ADC points, will be given
by:
Io
c
Phase and earth current - voltage angle measurement
The instantaneous angle between the generic phase current and the phase-phase quadrature
voltage, to be used for protection purposes is obtained as the relative angle between the involved
vectors.
The formulas are:
C264/EN UM/E50.5 199

Where:
IÛ is the angle between the generic phase current and the phase-phase quadrature voltage.
is the generic current vector.
is the generic voltage vector (phase-phase).
Re(…) is the operator that returns the real part of a generic vector.
Im(…) is the operator that returns the imaginary part of a generic vector;
Active earth power
With any type of phase voltage insertion it is always possible to derive the vectors of the earth
voltage’s fundamentals that, together with the earth current, allow the active earth power
calculation. The formula is:
Where:
Po The active earth power expressed in ADC points.
Active three-phase power
With any type of phase voltage insertion, it is always possible to derive the vectors of the phase-
phase voltage’s fundamental.
Therefore, it is quite easy to calculate the three-phase active power by using the Aaron method;
the formulas are:
Where:
P is the active triple phase power expressed in ADC points;
200 C264/EN UM/E50.5

Pn is the nominal three phase power to the secondary side, amounting to:
Since In and Un are respectively the nominal current and the voltage to the secondary side;
P” is the active three phase power to the secondary side, expressed in Watt;
P’ is the active three phase power to the primary side expressed in Watt;
Reactive three-phase power
With whatever type of phase voltage insertion, it is always possible to draw the vectors of the
phase-phase voltage’s fundamental.
Therefore, it is easy to calculate the reactive three-phase power by using the Aaron method; the
formulas are:
Where:
Q is the three phase reactive power expressed in ADC points;
Qn is the nominal three phase active power to the secondary side, amounting to:
Since In and Un are respectively the nominal current and the voltage to the secondary side;
Q” is the active three phase power to the secondary side, expressed in Qn;
Q’ is the active three phase power to the primary side expressed in VAR;
Power factor
The power factor is an instantaneous value, used only for visualising purposes. Indicated by:
P the three phase active power expressed in ADC points;
Q the three phase reactive power expressed in ADC points;
The power factor, or three phase cosf, is calculated according to the following algebraic function:
The sign of three phases cosf is determined according to the following conventions:
C264/EN UM/E50.5 201

P positive P negative
Q positive +L -C
Q negative +C -L
Thermal status
It can be demonstrated that, for dt=0.02s, the thermal status can be estimated according to the
following equation:
Where:
IMAX is the maximum of the three instantaneous values of the three phase RMS currents.
t is the thermal constant of the device to be protected.
Iq is the base current of the device to be protected (ratio between the device’s nominal current –
in other words the current that, at full operation, implies over-temperature by 100% - and the
nominal current of the TA).
Iq = K * Ith
q is the thermal status or over-temperature of the device (over-temperature in p.u. in relation to

the temperature reached by the device at full operation, when subjected to a current equal to the
base current).
The thermal status must reside in a non-volatile variable (SRAM) to allow its recovery in event of
auxiliary voltage loss.
To avoid the unwanted trip of the thermal protection, on power-on, the thermal status is reinstated
up to a maximum equalling 90% of the greater between the thermal thresholds to then evolve
normally according to the above equation.
The thermal status can be reset (q(t) = 0) through a PPC CO.
I2T Measurements
There are 8 measurements dividable in 3 sets:

• 3 IT phase measurements,
• 3 I2T phase measurements,
• 2 measurements computer by the sum of the IT phase measurements and I2T phase
measurements.
These measurements are always valid.
IT phase measurements
3 measurements based on the samples of the current phase:
202 C264/EN UM/E50.5

where:
• nb is the number of samples,
• T is the period of the signal,
• 32 is the number of samples by period.
These measurements must reside in a non-volatile variable (SRAM) to allow its recovery in event
of auxiliary voltage loss.
I2T phase measurements
3 measurements based on the samples of the current phase
These measurements must reside in a non-volatile variable (SRAM) to allow its recovery in event
of auxiliary voltage loss.
IT and I2T sum measurements
These 2 measurements are computed by the sum of the IT phase measurements and I2T phase
measurements.
4.4.2.3.14 Treshold detection

Six thresholds can be defined for each measurement: 3 upper thresholds and 3 lower thresholds.
A hysteresis value configured on a per measurement basis is associated to the threshold

management. This value is a percentage of the full-scale value of the measurement.
C264/EN UM/E50.5 203

- Figure 37 - tresholds detection
4.4.2.3.15 Manual suppression

A measurement can be assigned to the suppressed state by an order issued from an operator. No
subsequent change of value or state on a "suppressed" measurement can trigger any action: for
example, display, alarm, transmission. The measurement takes the SUPPRESSED state. When
the operator "un-suppresses" the measurement, this one takes its actual state.
4.4.2.3.16 Substitution
The value of a measurement can be substituted by an operator (state “SUBSTITUTED”, value
defined by the operator). The measurement stays in this state until he un-substitutes it.
When a measurement is substituted, no change of value nor state is transmitted, and

computations are made with the substituted state. When the measurement is un-substituted, the
actual state and value are transmitted to higher control levels and subsequent changes of state
and value are transmitted again.
4.4.2.3.17 Forcing an invalid measurement

When a measurement is invalid: that is, SELFCHECK ERROR DETECTED, UNDEFINED, OPEN
CIRCUIT, SATURATED or UNKNOWN); it can be manually forced by a user (state “FORCED”,
value defined by the operator). This feature is similar to the substitution, but the information is
automatically updated when valid information is available again.
The forcing could also be automatic: in this event, the invalid information takes automatically the
FORCED state and the value defined in configuration.
The forced/substituted data are saved in SRAM (kept for minimum 48h without BCPU power
supply).
The modified states are not reset by a BCPU reboot.
A database switch (or evolution) reset the forced/substituted data.
204 C264/EN UM/E50.5

4.4.2.3.18 Measurement resulting states

The Measurement resulting states, following the various filters, that you can apply include:
State Meaning
VALID Not in one of the following states
SELFCHECK FAULTY Inoperative acquisition board
SUBSTITUTED Operator action set MV value as valid state
FORCED Automatic valid state and configured value when MV is invalid
SUPPRESSED Operator set MV in this invalid state
UNKNOWN MV is acquired via a transmission link, and the link is disconnected
SATURATED MV is beyond its nominal input range
MV is Digital Measurement with invalid coding or computation on
UNDEFINED
analogue leads to error
MV is DC 4-20 mA with invalid coding or computation on analogue
OPEN CIRCUIT
leads to error
OVERSHOOT[1..3] One of the 3 overshoot values has been crossed
UNDERSHOOT[1..3] One of the 3 undershoot values has been crossed
4.4.2.3.19 Transmission
By configuration, the measurement values and their states can be transmitted on IEC 61850
SBUS:
• In report mode, the measurement is transmitted to the subscribers with its value, status,
timestamp and the reason for change.
• In GOOSE mode, the measurement value and status are transmitted in multicast to the
configured receivers.
NOTE: A MiCOM C264 client can have 32 numbers of IEC 61850 servers and a MiCOM C264
server can have 16 numbers of IEC 61850 clients; GOOSE size is restricted to 128 binary inputs
and 64 measurements
During a loss of communication between a client and a server, all server measurements are set to
UNKNOWN on the client.
The measurement information transmitted in a report include:

• The real value: that is, after scaling
• The resulting state: mapped on the quality field on IEC 61850
• The time stamping: in GMT time; and time quality
• The reason for the change:
Change of quality: set if the measurement resulting state has changed
Cyclic change: set if the measurement value has changed, without modification of the
resulting state
C264/EN UM/E50.5 205

A Measurement value can be transmitted periodically or upon variation (% of nominal), and

anyway on state change.
4.4.2.3.19.1 Periodic transmission
Two periods are defined in database, on a per BCPU computer basis:

• a short period from 0,1 to 60 seconds (step 0,1 second)
• a long period, from 0,5 to 60 seconds (step 0,5 second)
Each measurement is associated to one of the two periods. All measurements of one period are
transmitted at the beginning of each cycle.
All measurements values transmitted within one transmission cycle are the latest acquired
values.
4.4.2.3.19.2 Transmission upon variation
Measurements can be transmitted upon variation: a value is sent if the acquired value (Vacq) is
different from more than a specified amount ∆V from the previously transmitted value (Vt) (i.e
|Vacq-Vt| > ∆V).
∆V is computed either from the last transmitted value (mode 1) or from the full-scale value (mode
2):
∆V = (p/1000) * |Vt| where p is a value in the range 0 .. 255 and Vt is the last transmitted value.
or
∆V = (p/1000) * |Vmax| where p is a value in the range 0 .. 255 and Vmax is the full-scale value.
4.4.2.3.19.3 Transmission upon trigger
One or more measurements can be associated to a single or double BI “trigger”. When the BI
goes to the state SET / CLOSED (or FORCED SET, SUBSTITUTED SET, FORCED CLOSED /
SUBSTITUTED CLOSED) all associated measurements are transmitted immediately. The same
behavior if the BI is in this state at the initialization of the computer. As much the BI is in this state
the associated measurements are transmitted after change of state or according to the
configuration (periodically, upon variation, threshold variation)
4.4.2.3.19.4 Limits and performances
To secure the proper accuracy for calculations, the sampling frequency must be exactly adapted
to the signal frequency that fluctuates around the basic frequency (50 / 60 Hz).
The required accuracy shows in the table that follows:
ITEM TMU210 TMU220

Current accuracy
(with • 0.2 % In (0.2 A to In)
2% In
measurement • 0.2 % measurement (In to 4 In)
CT)
206 C264/EN UM/E50.5

ITEM TMU210 TMU220

• 0.3 % 45 V (< 20 V),
• 0.2 % 45 V (20 V to 45 V),

Voltage accuracy
• 0.2 % measurement (45 V to 200
(with voltage 2% Vn
droppers) V),
• 0.3 % measurement (200 V to
550 V)
Frequency
± 0.01Hz ± 0.01Hz
accuracy
Phases-shift
± 2° ± 1°
accuracy
Time 1 ms 1 ms
Up to x harmonic 10th 15th
0.5 % (Phi = 0 °)
Note: The accuracy is not applicable

Power accuracy in this case:
(with
1% Active / Reactive
measurement Operating range
Power Value
CT)
1A < 0.72 W / VA
5A < 3.2 W / VA
NOTE: The accuracy is applied for the temperature operating range of MiCOM C264
4.4.3 Tap Position Indication (TPI) measurement processing

4.4.3.1 Acquisition from Digital Inputs
The tap position is acquired on digital input boards. It could be:
• A Multiple Point, if so, the resulting states are considered as values
• A digital measurement using one of the following encoding:
Decimal
Gray
BCD
4.4.3.2 Acquisition from Analogue Inputs

The tap position is acquired by measuring a current input.
A minimum value Imin (mA) corresponds to the lowest position 1 of the tap, and a maximum value
Imax corresponds to the highest value N.
The input current should take only discrete values:
Ik =Imin + (K -1)(Imax-Imin)/(N-1) , with K the position of the tap.
C264/EN UM/E50.5 207

However the tap is considered in the position K if the current is in the range [Ik-DI/2 .. Ik+DI/2],
with DI = N% of (Imax – Imin). The N percentage is defined in configuration.
The tap position is considered UNDEFINED outside of this range.
4.4.3.3 Manual suppression

A TPI can be suppressed by an order issued from an operator. No subsequent change of value or
state on a suppressed TPI can trigger any action: for example, display, alarm, transmission. The
TPI takes the “SUPPRESSED” state. When the operator unsuppresses the TPI, this one takes its
actual state.
4.4.3.4 Substitution
The value of a TPI can be substitute by an operator (state “SUBSTITUTED”, value defined by the
operator). The TPI stays in this state until he unsubstitutes it.
When a TPI is substituted, no changes of value nor state is transmitted, and computations, for
instance groupings, are made with the substituted state. When the TPI is unsubstituted, the actual
state and value are transmitted to higher control levels and subsequent changes of state and
value are transmitted again.
4.4.3.5 Forcing an invalid TPI

When a TPI is invalid: that is, SELFCHECK ERROR DETECTED, UNDEFINED or UNKNOWN; it
can be manually forced by a user (state “FORCED”, value defined by the operator). This feature is
similar to the substitution, but the information is automatically updated when valid information is
available again.
The automatic forcing function is not provided for TPI.
4.4.3.5.1 Measurement resulting states

The Measurement resulting states, following the various filters, that you can apply include:
State Meaning
VALID Not in one of the following states
SELFCHECK FAULTY Inoperative acquisition board
SUBSTITUTED Operator action set MV value as valid state
FORCED Automatic valid state and configured value when MV is invalid
SUPPRESSED Operator set MV in this invalid state
UNKNOWN MV is acquired via a transmission link, and the link is disconnected
SATURATED MV is beyond its nominal input range
MV is Digital Measurement with invalid coding or computation on
UNDEFINED
analogue leads to error
MV is DC 4-20 mA with invalid coding or computation on analogue
OPEN CIRCUIT
leads to error
OVERSHOOT[1..3] One of the 3 overshoot values has been crossed
UNDERSHOOT[1..3] One of the 3 undershoot values has been crossed
208 C264/EN UM/E50.5

4.4.3.6 Transmission
The TPI are transmitted on a client-server basis on the IEC 61850 network using the report
mechanism.
During a loss of communication between a client and a server, all server TPI are set to
UNKNOWN on the client.
The TPI is transmitted as soon as a value change or a status change is detected. The TPI
information transmitted in a report are:
• The TPI value,
• The resulting state: mapped on the quality field on IEC 61850,
• The time stamping: in UTC time; and time quality,
• The reason for the change:
Change of data: set if the value changed,
Change of quality: set if the quality changed,
Change due to control: set if the state or quality change is due to a control.
The TPI information transmitted in a GOOSE is the same than in a report, except for the "reason
for change" and the time-stamping.
4.4.4 Accumulator Input Processing

The accumulator stores its current value in a static memory volatile memory (secured with a
capacitor, >48h autonomy). At configured sample an accumulated value is extracted for inner
computation and transmission (Common Data Class BCR on IEC 61850).
Digital Inputs are used to count pulses. There is Single counter (SCT) based on one DI and
Double Counter (DCT) based on two DIs that count complementary states.
At processing level special persistent and complementary filters eliminate non-stable pulses. The
integer counter (also transmitted) can be scaled (among of energy of valid pulse).
4.4.5 Energy counting

The energy counting function aims to calculate exported and imported active energy (in kWh) and
exported and imported reactive energy (in kVarh) from active and reactive power issued from
CT/VT calculation, digital, analogue boards measurements or IED measurements.
Calculation of the energy is done periodically. The period is defined either by an external pulsed
applied on a digital input, or by the internal clock of the computer. The choice of the origin of the
periodic signal is defined during the configuration phase on a per computer basis.
Whatever is the origin of an integrated measurement, the integration is done after scaling with a
step of one second.
The integration method used is the trapezium one:
C264/EN UM/E50.5 209

With:
E = total Energy counter value (continuous register),
Ei = Integration result at time ti,
Sf = Scaling Factor (defined during the configuration phase),
Mi = absolute value of the Measurement at time ti,
ti – ti-1 = 1 second.
For a given measurement, the integration can be done only after receiving two consecutive valid
values with the same sign of the measurement. The integration result (Ei) is added to the
associated export or import counter according to the sign of the measurement.
The integration is stopped as soon as the power measurement becomes invalid or changes of
sign. The integration is restarted as soon as two consecutive valid measurement values with the
same sign are received.
Current values of energy counters are stored in secured memory ( 48h autonomy when power
supply is off). Current values of energy counters can be modified by an operator.
Values of energy counters are transmitted on a client-server basis on the IEC 61850 network
using mechanism through the LN MMTR.
During a loss of communication between a client and a server, all server energy counters are set
to UNKNOWN state on the client.
NOTE: Do not use the energy counter values for the billing application.
4.4.6 Basic data manipulation

4.4.6.1 Simul mode enhancements
The MiCOM C264 Simul mode allows you to deactivate the DOU/CCU relays output in event of
control sequence.
The enhancements allow to:

• manage the Simul mode in event of MiCOM C264 redundancy (Simul mode is managed only
if the computer is in active mode, so a computer in standby mode can't be set in Simul mode),
• manage the control feedback datapoints.
In event of computer redundancy, the Simul mode activation is performed independently for each
MiCOM C264 (Main 1 rack and Main 2 rack) from Computer Administration Tool (CAT). If the
Active MiCOM C264 is set in Simul mode, it remains Active. A Standby MiCOM C264 cannot be
set in Simul mode.
If the control is related to a datapoint: that is, feedback datapoint defined in configuration; this one
takes the control value in Simul mode:
• Open / Reset order => Open state for DPS, Reset state for SPS,
• Close / Set order => Close state for DPS, Set state for SPS.
210 C264/EN UM/E50.5

To leave the Simul mode, the user, through the CAT, changes the MiCOM C264 mode to
Operational. The MiCOM C264 automatically goes in Maintenance mode (transient) before going
in Operational mode.
The user of the Simul mode owns all responsibility of controls performed during the Simul mode,
and before leaving the Simul mode, he owns all responsibility to restore the system. In Simul
mode, all controls performed may impact ISaGRAF® or PSL automation.
LIMITATIONS:
• Digital and Analogue Setpoint with measurement feedback are not managed in Simul mode:
that is, they are managed as in Operational mode.
• IEC 61850 exchanges (reports, gooses) are not impacted by the MiCOM C264 Simul mode.
That means that a control done in Simul mode, that is sent to another computer that is not in
simul mode or to an IED (legacy or not) may be fully and physically executed on this device.
4.4.6.2 Controls management from PSL

A control issued from a PSL (or an DI/DO association) will be accepted even if another control is
already on-going on the same output. In this event, the previous control is stopped, and the new
control is launched (except if the new one is the same order than the previous one: in this event,
the new control is refused).
There are three ways to manage. PSL refers to PSL or DI/DO association, and Operator refers to
IEC 61850 / ISaGRAF® / local HMI:
• Control 1 from PSL and Control 2 from Operator,
• Control 1 from Operator and Control 2 from PSL,
• Control 1 from PSL and Control 2 from PSL.
The event « Control 1 from Operator and Control 2 from Operator » is already managed: in this
event, the control 2 is rejected.
Events – Control 2 different from Control 1
Control 1 Control 2 Action Acknowledgement

n/a (no ack managed in
PSL Operator Control 1 cancelled
PSL)
Operator PSL Control 1 cancelled Ack “Operator cancel”
PSL PSL Control 1 cancelled
PSL)
Ack “Control in
Operator Operator Control 2 ignored
progress”
Events – Control 2 identical to Control 1

Ack “Control in
PSL Operator Control 2 ignored
progress”
C264/EN UM/E50.5 211


Operator PSL Control 2 ignored
PSL)
PSL PSL Control 2 ignored
PSL)
Ack “Control in
Operator Operator Control 2 ignored
progress”
212 C264/EN UM/E50.5

4.5 Control sequences

4.5.1 Description
A Control Sequence is a basic built-in function on a module (switch, relay, and function). It
receives control order, sending back acknowledgement. After checks, control sequence sends
control (protocol or DO), and check correct execution with feedback from protocol or from DI.
4.5.1.1 General
BCPU allows the following functions:
• Control of switching devices (circuit breaker, switch, …)
• Control of transformers
• Control of secondary devices
• Locking of switching devices
• Control of IED
• Control of automatisms
These types of controls are allowed:

• Select control request
• Execute control request
• Unselect control request
• Cancel control request
Upon reception of one of these requests, the computer behavior is different according to:
• The configuration of the device control,
• The type of the device,
• The computer operating mode.
4.5.1.1.1 Device control configuration

By configuration, at SCE level, a control may be executed in one of the following modes:
• “Direct Execute” mode: usually for ancillary devices a control may be performed directly
without the selection phase.
• “Select Before Operate once” mode” (SBO once): usually for circuits breakers and
disconnectors. The device has to be selected before allowing the execution. In that event the
device is managed in two phases: selection and execution. Device deselection is done
automatically by the computer.
• “Select Before Operate many” (SBO many): usually for transformers. The device has to be
selected before execute one or more controls before reaching the expected position
(low/raise). In that event the device is managed in three phases: selection, execution and
deselection. The execution phase is repeated for every new control. To end the controls
sequence, the initiator of the request has to send an “deselection” request.
By configuration, each DPC order (close order or open order) and each SPC can activate
simultaneously two DO contacts.
C264/EN UM/E50.5 213

4.5.1.1.2 Types of devices

Every control sequence may be different according to the type of the device to control. The
complexity of the control sequence may be important depending on the device:
• Synchronised or not synchronised circuit breakers, disconnectors and earthing/grounding
switches: They are managed in “Direct execute” mode or “SBO once” mode with optional
hardware selection of the device in SBO mode.
• Transformers: They are managed in the three modes: “Direct Execute”, “SBO once” and
“SBO many” mode with optional hardware selection of the device in SBO mode.
• Ancillary devices: they are usually managed in “Direct Execute” mode but can be managed
also in “SBO once” mode.
• System Controls: System outputs are used to activate or inactivate automatic functions on the
computer: for example, Auto-recloser ON/OFF; change operating modes; and so on.
• Controls via Setpoints: are managed in “Direct Execute” mode and in “SBO once” mode.
4.5.1.2 Control sequence phase management

According to the configuration of the device control, a control sequence is performed in one, two,
or three phases. Each phase of a control sequence (selection, execution and deselection) may
have a normal or abnormal termination and positive or negative acknowledgement is sent to the
IEC 61850 clients subscribed during the configuration process.
• One phase – “Direct Execute” mode:
Execution phase: If the execution phase ends normally the computer generates a positive
acknowledgement and the control sequence ends. In event of abnormal termination, the
control sequence is aborted and the computer generates a negative acknowledgement. The
hardware selection of the device in “Direct Execute” mode is not allowed.
• Two phases – “SBO once” mode:
Selection phase: In the selection phase for a normal termination the computer generates a
positive acknowledgement and proceeds to the next phase of the sequence (execution
phase).
acknowledgement and the control sequence ends. In event of abnormal termination, the
control sequence is aborted and the computer generates a negative acknowledgement.
• Three phases – “SBO many” mode:
Selection phase: In the selection phase for a normal termination the computer generates a
positive acknowledgement and proceeds to the next phase of the sequence (execution
phase)
acknowledgement and waits a new execution request. In event of abnormal termination, the
control sequence is aborted and the computer generates a negative acknowledgement.
Unselection phase: The computer proceeds to the deselection of the device and ends control
sequence sending positive acknowledgement. In event of fail deselecting the device the
computer sends a negative acknowledgement.
The following figures show the three control modes of the computer:
214 C264/EN UM/E50.5

- Figure 38 - control modes of the computer (1)
C264/EN UM/E50.5 215

- Figure 39 - control modes of the computer (2)
216 C264/EN UM/E50.5

4.5.1.3 Direct Execute mode

In this mode a control of device is directly executed without need to be previously selected.
Usually concerns ancillary devices managed via I/O boards (SPC, DPC, and Setpoints) or via
IED.
The ”Direct Execute” sequence ends normally after reception of the expected position information
of the device or correct value (if setpoint control). Abnormally if the received position or value is
unexpected, or not received in the predefined delay by configuration.
Note that a “cancel” request in ”Direct Execute” mode has no guarantee to be performed before
the execution of the request. An “deselect” request has no meaning in ”Direct Execute” mode.
C264/EN UM/E50.5 217

- Figure 40 - execution phase for direct execute mode
218 C264/EN UM/E50.5

4.5.1.4 SBO once mode

4.5.1.4.1 Selection phase in "SBO once" mode
During the selection phase initialised by a selection request of the control, the computer performs
selection checks in order to verify if the device is selectable or not.
If no fail occurs during these checks, the device is selected, and positive acknowledgement is
sent. Otherwise the selection request is refused, and a negative acknowledgement is sent giving
the cause of the failure. If the selection of the device is accepted, the computer starts a delay and
waits for:
• An execution request: open/close, low/raise
• A cancel of the selection request.
At the end of this delay if the execution or the cancel request is not sent, the device is
automatically deselected, and a negative acknowledgement is sent. The selection delay is
defined during the configuration step.
Note that only one selection is allowed at a time for a device. When a device is already selected
any other selection is not considered (none acknowledgement is sent) whichever of the initiator.
The diagram that follows shows the selection phase of a device configured in SBO once mode.
C264/EN UM/E50.5 219

- Figure 41 - Selection phase in SBO once mode
220 C264/EN UM/E50.5

4.5.1.4.2 Execution phase in "SBO once" mode

The execution phase can start only after reception of an execution request and if the device has
been selected before.
In this phase, the computer performs the execution checks, and if no fail, it proceeds to the
execution according to the configuration, via the IO boards or IED communication.
If the execution ends normally, a positive acknowledgement is sent, and the control sequence
ends. In event of fail the control sequence is aborted and the computer sends a negative
acknowledgement.
During this phase a “cancel” request is not guaranteed except for synchronised circuit breakers
devices (refer to specifics treatments for synchronised circuit breakers below).
C264/EN UM/E50.5 221

- Figure 42 - Execution phase on SBO once mode
4.5.1.5 SBO many mode

This mode allows you to perform one or more control executions after the selection phase. It is
usually used for the tap positioning process in where many controls are sent before reaching the
desired position.
4.5.1.5.1 Selection phase in SBO many mode

The selection phase is identical to the “SBO once” mode selection phase.
222 C264/EN UM/E50.5

4.5.1.5.2 Execution phase in SBO many mode

The difference with the SBO once mode is that after having performed an “execution request”, the
computer stays in execution phase waiting a new execution order or an “deselect” request. The
execution phase ends only after an “deselect” request or “cancel” request by the initiator.
Upon reception of an “deselect” request the computer ends the execution phase and goes to the
selection phase.
C264/EN UM/E50.5 223

- Figure 43 - Execution phase in SBO many mode
4.5.1.5.3 Unselection phase in SBO many mode

The computer deselects the device and sends a positive acknowledgement.
224 C264/EN UM/E50.5

- Figure 44 - Deselection phase in SBO many mode
4.5.1.6 Generic selection checks

Checks performed during the selection phase Include:
• Inter-control delay
• Computer mode
• Substation and bay mode states
• Interlock and topological interlocking states
• Automation running control
• Device selectable
• Locked device state
• Status of the device
• Uniqueness
In event of fail, the initiator of the request may bypass the checks that follow:
• Uniqueness
C264/EN UM/E50.5 225

- Figure 45 - Selection checks for SBO device
226 C264/EN UM/E50.5

4.5.1.6.1 Inter-control delay

You can define a user-selectable delay during which a new order to the same device is forbidden.
If this delay is configured and not expired since the last order, the request is refused with negative
acknowledgement.
4.5.1.6.2 Computer mode

Control requests are accepted or not depending on the operating mode of the computer.
• Maintenance mode: control requests are not accepted if the computer is in maintenance
mode except system controls concerning control mode or database management.
• Inoperable mode: no control is accepted when the computer is in this mode.
• Changing mode:
From “operational” mode to “maintenance” mode: all device controls in progress are
aborted and no acknowledgment is sent.
From “operational” mode to “test” mode: the specific control “test” mode is refused if at
least one control is in progress.
From “test” mode to “operational” mode: the specific control “test” mode is refused if at
least one control is in progress.
4.5.1.6.3 Substation and bay mode control

A device control may be dependant or not to the substation mode and bay mode. For every device
control the configuration gives the dependency or not to the following modes:
• Substation mode dependency (local/remote)
• SBMC mode dependency (bay in maintenance or not)
• Bay mode dependency (local/remote)
Bay mode is checked by the computer managing the device if the bay mode dependency is
configured for this device.
Substation and SBMC modes are checked by the computer having slave protocols and only for
controls coming from SCADA and if substation mode dependency is configured for this device.
If the request is refused the selection sequence is aborted with negative acknowledgment.
4.5.1.6.4 Interlock control

The configuration process allows to assign or not a logical equation to each order (close and
open) of the device. If configured by the user, its state (true/false) may affect the control
sequence. If is false, the selection is refused, excepted if bypass is set.
In event of fail, the sequence is aborted with a negative acknowledgement.
4.5.1.6.5 Automation running control

Each device may be locked by the presence of an input information (digital input, IED input etc)
assigned during configuration. A “system input information” giving automation state
(active/inactive) can be used to prevent manually control execution in event an automatism is
active for device monitoring.
In this event the sequence is aborted with a negative acknowledgement, except if the user asks to
bypass this check.
C264/EN UM/E50.5 227

4.5.1.6.6 Device selectable

A device is selectable if during configuration step its control is described to be managed in “SBO
once” or “SBO many” mode and is not already selected. Otherwise the selection request is
refused with negative acknowledgement.
4.5.1.6.7 Locked device control

The user may lock a device in order to avoid any wrong move. If the selection concerns a locked
device the request is refused, except if the user force to this control in the selection request.
In event the device is locked the sequence is aborted with a negative acknowledgement.
4.5.1.6.8 Current status of the device

The status check of the device is optional. It is given by a binary input or computed using more
than one binary input (event of circuit breakers). Its behaviour can be chosen (during the
configuration step) among one of the four following events: it is given by a binary input or
computed using more than one binary input (event of circuit breakers).
• The request is accepted whatever the status of the device (no check)
• The request is accepted only if the device is in the opposite state and valid
• The request is accepted only if the device is in the opposite state, jammed or undefined
• The request is refused only if the device is in the same state and valid. In any event, if the
request is refused, a negative acknowledgement is sent back
4.5.1.6.9 Uniqueness
It is possible by configuration to prevent to have more than one control at a time.
• For the whole substation
• Inside a bay
The following figure describes the algorithm used between computers.
228 C264/EN UM/E50.5

- Figure 46 - Check of uniqueness
If a device is under control and another control is sent on this device, the second one is ignored.
In event of uniqueness of the command at least to one of these levels the selection is refused,
with negative acknowledgement. The user may bypass this control during selection request.
4.5.1.7 Selection behavior

In SBO once and SBO many modes, the configuration process allows to describe optionally, a
device selection to control the device.
The following configurations have to be considered:

• Configuration 1: device with a control for selection and its associated selection position
information.
• Configuration 2: device with a control for selection (without input selection information).
Whatever the request control (select open/select close, select raise/select low) the selection of
the device is performed as follows:
• Configuration 1:
The computer
a. verifies the selection position information, it have to be open: if it is close, it is an abnormal

situation, the selection sequence is stopped with a negative acknowledgment.
b. sends a “close” order of the selection control (via I/O boards or IED) and waits the
selection position information in a given delay (by configuration).
C264/EN UM/E50.5 229

If the selection control has been normally executed, and the selection position information
of the device become “set” in the given delay, the selection sequence ends sending a
positive acknowledgment. The computer starts its execution sequence. In event of fail of
the execution of the selection control or if the selection position information remains open
in the given delay the selection sequence ends abnormally sending a negative
acknowledgment.
• Configuration 2:
For this configuration, in which only the output control of the selection is configured, the
computer: sends a “close” order of the selection control (via I/O boards or IED). If the
selection control has been normally executed, the selection sequence ends by sending a
positive acknowledgment and the computer start its execution sequence.
In event of fail of the execution of the selection control, the sequence ends abnormally by
sending a negative acknowledgment.
4.5.1.8 Generic execution checks

During the execution phase, whatever the execution mode (SBO once, SBO many or Direct
Execute) the computer, before proceeding to the execution of the request, performs the following
checks:
• Inter-control delay
• Computer mode
• Device selectable (SBO mode only)
• Current status of the device
• Uniqueness
Execution checks and bypasses are identical to those of the selection phase. Moreover, in event
of ”SBO once” mode or ”SBO many” mode the computer verifies that the device was previously
selected.
The checks of the execution phase in “SBO many” mode are identical as above but they are
repeated for every execution request (low/raise).
In “Direct Execute” mode the device selection is not verified because it is not allowed.
4.5.1.9 Execution behavior

On this stage the control request is executed via:
• I/O boards
• System supervisor of the computer for system outputs
• IED communication
The execution via I/O boards is performed only if the computer is in “operational” mode.
230 C264/EN UM/E50.5

4.5.1.9.1 Execution via I/O boards

According to the devices features the execution of the control via I/O boards may be performed
using:
• Single Points Control (SPC)
• Double Control Points (DPC)
• Digital Setpoints (SP)
Single Point Control and Double Point Control
However, the execution control sequence depends on the activation mode of the xPC. By
configuration, this activation mode of SPC and DPC may be “transient”, “permanent” or
“permanent until feedback until feedback”.
• Transient: the contact is closed and then re-opened automatically after a delay (defined
during the configuration of the xPC). For a DPC, configuration gives two delays need to be
configured, one for open and one for close.
• Permanent: For this type of output control, the contact is held in the requested position state
until a reverse order is received.
• Permanent until feedback: The contact is held in the requested position state until
confirmation of the position of the device or after timeout awaiting the new position of the
device. In this event, the input information of the device status has to be configured.
Digital Setpoints
Digital and Analogue Setpoints
Digital Setpoints are executed via Digital Output boards. This type of control is managed in “Direct
Execute mode” only.
Analogue Setpoints are executed via Analogue Output boards. This type of control is managed in
“Direct Execute mode” only.
BCPU can have 256 numbers of Digital Setpoints.
4.5.1.9.2 Execution via IED communication

When an execution request is performed via IED communication, the requested order is
converted to a message to be sent to the IEDs, according the communication protocol.
4.5.1.9.3 System controls execution

For systems outputs the computer activate/deactivate the associated function (computer mode,
etc) and if a specific system input (SPS or DPS) is configured for this control, it takes the
requested state and it stored in non-volatile memory.
4.5.1.10 Controls time sequencing

Time sequencing of control is dependent of its configuration:
• Control mode: Direct Execute, SBO once, SBO many
• Device features: selection control wired/not wired, selection position wired/not wired, device
position wired/not wired and so on
• Output control type: permanent, pulse
C264/EN UM/E50.5 231

• Destination: I/O board
• Time-out delays: selection phase time-out, selection Feedback delays, open/close Feedback
delay and so on.
4.5.1.10.1 Direct execute time sequencing

The chronogram shows an example of normal termination on Direct Execute sequence.
- Figure 47 - Normal termination of direct execute sequence
The chronogram that follows shows an abnormal termination of Direct Execute sequence. The
device hasn’t taken the expected position in the given delay.
- Figure 48 - Abnormal termination of direct execute sequence
4.5.1.10.2 SBO once time sequencing

The configurations below are given as examples
Device Configuration A: the optional selection control and Selection position information are
configured
The chronogram that follows shows a normal termination of the control sequence.
232 C264/EN UM/E50.5

- Figure 49 - Normal termination of the control sequence

• Stage 1: device selection (closing the associated output control)
• Stage 2: the selection is confirmed by the associated input information in the feedback delay
(0 – 1-sec user selectable)
• Stage 3: close the device before the end of the selection timeout delay (0 – 10 MN user
selectable)
• Stage 4: the device has taken the expected position (close) in the feedback delay (0–60 sec
user selectable). The computer deselects the device (open selection output control)
• Stage 5: confirmation of the deselecting of the device in the same given delay than stage 2.
The chronogram that follows shows controls sequence that is aborted after time-out of the
selection delay.
- Figure 50 - Aborted control sequence

• Stage 2: the selection is confirmed by the associated input information in the feedback delay.
C264/EN UM/E50.5 233

• Stage 3: timeout of the delay - the device is deselected
• Stage 4: confirmation of the deselecting of the device
Device Configuration B: the optional selection control is configured, and Selection position
information is not configured
The chronogram that follows shows a normal termination of the control sequence.
- Figure 51 - Normal termination of the control sequence

• Stage 2: close the device before the end of the selection timeout delay (0 – 10 min user
selectable)
• Stage 3: The device has taken the expected position (close) in the feedback delay (0–1-sec
user selectable). The computer deselects the device (open selection output control)
4.5.1.10.3 SBO many time sequencing

SBO many mode is exclusively used for control of transformers. Refer to associated section.
4.5.1.11 Bay/Module/xPC order running

Order running management is available for computers:
• At Bay level
• At Module level (optional)
• At SPC datapoint level (optional)
• At DPC datapoint level (optional)
At bay respectively module level the order running SPS is SET as soon as a control is in progress
on the bay respectively module managed by the computer.
At SPC datapoint level:
234 C264/EN UM/E50.5

• In event of Direct Execute control, the order running SPS (on/off order SPS) is:
SET as soon as the MiCOM C264 accepts the control: that is, after the control checks,
RESET when the final control acknowledgment is sent.
NOTE: The on/off order SPS can only be added to an SPC directly wired on one of the
MiCOM C264.
• In event of SBO control, this SPS is:
SET as soon as the MiCOM C264 accepts the control selection: that is, after the selection
checks,
At DPC datapoint level two distinct order running SPS exist, one for open order ("Open order
SPS”) and one for close order ("Close order SPS”) with the previously described behavior.
Moreover, two more optional SPS for DPC are available: "Open Control SPS" and “Close control
SPS” with the following behavior:
• In event of Direct Execute control, this SPS is:
SET as soon as the execute control is received by the MiCOM C264: that is, before the
checks,

• In event of SBO control, this SPS is:
SET as soon as the control selection is received by the MiCOM C264: that is, before the
checks,
In event of direct negative acknowledgment, those SPS may be SET then RESET with the same
time stamping.
4.5.1.12 Controlling xPC by xPS change of state

SPS/DPS datapoints permit to launch a device control sequence (operator control from a
hardwired mimic for example). These xPS datapoints activate the control as it is currently
performed when the control comes from the IEC 61850 or the local MiCOM C264 HMI. The
sequence cancel is not allowed. Only Direct Execute (DE) control types are allowed.
By configuration, the generic execution checks described can be bypassed (see "Generic
execution checks" on page 230).
The control is launched after xPS filtering (Debouncing, filtering, toggling described in "Binary
input definition" on page 158).
Control Originator Fields on IEC 61850 Station Bus
In case of controls launched by an xPS, the mandatory Control Originator fields on IEC 61850 are:
• orCat = Bay level,
• orIdent = xPS label.
C264/EN UM/E50.5 235

NOTE: Usage of order labels in profile for SPC in SCE, "order on" and "order off" should be
"Yes", and “Control Sequence Activating” attribute for SPC and DPC should be "Yes".
For further information on orCat / orIdent refer to the documentation of IEC 61850 international
standard.
Control Sequence launched by xPS priority management
An optional « synoptic Local/Remote (L/R) » SPS is defined at bay level to manage control
sequences priority. The priority between the actual « Bay L/R » and the « Synoptic L/R » is
configurable on a per bay basis.
L/R bay Priority 1 Local Remote

L/R
Priority 2 n/a Local
synoptic
Control
authorized - LCD xPS
>
Control is authorized by computer LCD and not by SPS when Bay L/R is priority 1 and operates in
local mode; and Synoptic L/R is priority 2 with operating mode not taken into account by
MiCOM C264.
Control is authorized by xPS and not by computer LCD when Bay L/R is priority 1 and operates in
Remote mode; and Synoptic L/R is priority 2 and operating in Local Mode.
L/R bay Priority 2 n/a Local

L/R
Priority 1 Local Remote
synoptic
Control
authorized - xPS LCD
>
Control is authorized by xPS and not by computer LCD when Bay L/R is priority 2 with operating
mode not taken into account by MiCOM C264 and Synoptic L/R is priority 1and operating in Local
Mode.
Control is authorized by computer LCD and not by xPS when Bay L/R is priority 2 and operates in
local mode; and Synoptic L/R is priority 1 operating in Remote Mode.
The configuration of the Synoptic L/R priority in EPAS-SCE:
236 C264/EN UM/E50.5

- Figure 52 - Configuration of Synoptic L/R priority in Control Sequence
If the “synoptic L/R” is not configured, the control issued from an xPS is accepted whatever is the
Bay L/R mode.
4.5.2 Control of non synchronized breakers

4.5.2.1 Non synchronized circuit breaker features
For the circuit breakers, the table that follows gives the inputs and outputs that are controlled by
the computer:
THREE PHASED CIRCUIT BREAKERS

OUTPUTS OUTPUTS INPUTS
CB TYPE A CB TYPE B (4) CB ALL TYPES
DPS physical position
of the device (1
SPC control for open phase)
DPC control for of device
SPS (optional) phase
DEVICE CONTROL open/close of device SPC control for close not together
of device information
system DPS the

feedback of the
control (1)
SPC /DPC (optional) SPC /DPC (optional) SPS /DPS (optional)
DEVICE SELECTION control of device control of device device selection
selection selection position information
ONE PHASED CIRCUIT BREAKERS

OUTPUTS OUTPUTS INPUTS
CB TYPE A CB TYPE B (4) CB ALL TYPES
C264/EN UM/E50.5 237

ONE PHASED CIRCUIT BREAKERS

SPS/ DPS physical
position of phase A
DPC control for open
phase A SPS/ DPS physical
position of phase B
DPC control for open
DPC control for phase B (pulse) SPS/ DPS physical
open/close of device position of phase C
DEVICE CONTROL DPC control for open
phase C system SPS phase
not together
DPC control for close
information (2)
of device
system DPS: the
feedback of the
control (3)
SPC /DPC (optional) SPC /DPC (optional) SPS /DPS (optional)
DEVICE SELECTION control of device control of device device selection
selection selection position information
1. The computed double signal is equal to the physical status if the “phase not together” status
is equal to “false” otherwise the computed signal is equal to “jammed”.
2. The computed “phases not together” is equal to “false” if all phases are in the same position
else it is equal to “true”.
3. The computed signal is equal to the phase A status if the phase not together status is equal
to “false” else the computed signal is equal to “jammed”.
4. Only the “DPC close “ is known by the other IEC 61850 equipment:
• For open the device they send the “DPC close” with “open” request
• For close the device they send the “DPC close” with “close” request
4.5.2.2 Control sequence of non synchronized circuit breakers

Circuit breakers devices are managed in ”Direct Execute” mode and in “SBO once” mode. Refer
to the generic description in "Non synchronized circuit breaker features" on page 237.
4.5.3 Control of synchronized breakers

Circuit breakers devices are managed in “SBO once” mode only. The following paragraph
describes the specific features of synchronized circuit breakers whether are synchronized by an
external or internal synchrocheck module.
4.5.3.1 Synchronized circuit breaker features

For the circuit breakers, the table that follows gives the inputs and outputs that are controlled by
the computer:
238 C264/EN UM/E50.5

THREE PHASED CIRCUIT BREAKERS

OUTPUTS CB TYPE OUTPUTS CB TYPE INPUTS CB ALL
A B (6) TYPES
SPS/DPS physical
SPC control for open position of the device
DPC control for of device (1 phase)
open/close of device SPC control for close SPS (optional) phase
DEVICE CONTROL SPC/DPC control for of device not together
close with information
SPC/DPC control for
synchrocheck (5) close with system DPS optional):
synchrocheck (5) the feedback of the
control (1)
SPS (optional) device
SPC (optional) control SPC (optional) control
DEVICE SELECTION selection position
of device selection of device selection
information
SPS/DPS (optional)
SPC/DPC (optional) SPC/DPC (optional)
SYNCHROCHECK ON/OFF
control of ON/OFF control of ON/OFF
SET ON/SET OFF (4) synchrocheck
synchrocheck synchrocheck
information
ONE PHASED CB
OUTPUTS (6) TYPE OUTPUTS (6) TYPE
OUTPUTS TYPE B INPUTS ALL TYPES
A A
SPS/DPS physical
SPC/DPC control for position of phase A
open phase A
SPS/DPS physical
SPC/DPC control for position of phase B
DPC control for open phase B DPC control for
open/close of device SPS/DPS physical open/close of device
SPC/DPC control for position of phase C
SPC/DPC control for open phase C SPC/DPC control for
close with system SPS/DPS close with
synchrocheck (5) SPC/DPC control for phase not together synchrocheck (5)
close of device information (2)
SPC control for close system DPS: the

with synchrocheck feedback of the
control (3)
SPS (optional) device
SPC (optional) control SPC (optional) control SPC (optional) control
selection position
of device selection of device selection of device selection
information
SPS/DPS /DPS
SPC/DPC (optional) SPC/DPC (optional) SPC/DPC (optional)
(optional) ON/OFF
control of ON/OFF control of ON/OFF control of ON/OFF
synchrocheck
synchrocheck synchrocheck synchrocheck
information
C264/EN UM/E50.5 239

1. The computed double signal is equal to the physical status if the phase not together status is
equal to “false” else the computed signal is equal to “jammed”.
2. The computed “phases not together” is equal to “false” if all phases are in the same position
3. The computed signal is equal to the phase A status if the phase not together status is equal
4. Wired SPC and SPS for external synchrocheck and system SPC and SPS for internal
synchrocheck. If is not configured the external synchrocheck module or the synchrocheck
automation is considered always “set on”. DPC and DPS are used only for manual
synchrocheck.
“Open” control sequence of synchronized circuit breakers remains identical to the non-
synchronized circuit breakers.
“Close” control sequence is different according to the configuration the synchrocheck type:
• External synchrocheck: The closure of the device is assumed by an external synchrocheck
module,
• Internal synchrocheck: The closure of the device is assumed by an internal synchrocheck
automation.
A Close control sequence can be configured with:

• Manual set on of the external synchrocheck module or internal synchrocheck automation,
• Automatic set on of the external synchrocheck module or internal synchrocheck automation.
Furthermore, waiting closes the CB by the external module the initiator of the request may:
• Cancel the request,
• Close the device by forcing request.
4.5.3.2 Circuit breakers with external synchrocheck

4.5.3.2.1 Close CB by external synchrocheck with automatic set on
The following scheme shows a “close” control for a device in which the external synchrocheck
module is set on automatically by the computer.
240 C264/EN UM/E50.5

- Figure 53 - Close cb by external synchrocheck with automatic set on
The “close” control sequence performed on the MiCOM C264 is done as follows:
Selection phase:
1. If the control is configured, set on synchrocheck module,
2. If configured, verify synchrocheck on/off information related to the output,
3. If configured, close the device selection output to select the device,
4. If configured, verify selection device input information associated to the output,
5. Wait for the execution request or timeout selection.
In event of fail of one of these operations, the controls sequence is stopped with a negative
acknowledgment
Execution phase:
6. Close the device using synchrocheck output control,
7. Verify the device position become close in the given delay,
8. Set off synchrocheck module if it previously set on,
9. Deselect the device if it previously selected.
The chronogram that follows shows a successful control sequence ”close with synchrocheck”.
C264/EN UM/E50.5 241

- Figure 54 - Chronogram of a successful "close with synchrocheck"
242 C264/EN UM/E50.5

The chronogram that follows shows an abnormal termination of control sequence ”close with
synchrocheck”. The device has not taken the expected position “close” in the given delay. The
control sequence is aborted with negative acknowledgment, deselecting previously synchrocheck
and device.
- Figure 55 - abnormal termination of "close with synchrocheck"
C264/EN UM/E50.5 243

4.5.3.2.2 Close CB by external synchrocheck with manual set on

By configuration the “close” control of the device may be done in two or three control sequences:
Two sequences:
• A “Direct Execute” sequence to put in service the external synchrocheck module,
• An SBO once sequence to close the CB by the synchrocheck module and put out of service
the synchrocheck module.
Three sequences:
• A “Direct Execute” sequence to put in service the external synchrocheck module,
• An SBO once sequence to close the CB by the synchrocheck module,
• A “direct execute” sequence to put out service the external synchrocheck module,
The scheme that follows shows a close control request where an operator at the HMI or gateway
manually manages the external synchrocheck module.
- Figure 56 - Close control request
First sequence (DIRECT EXECUTE): Set on the external synchrocheck module:
1. Close “set on/setoff” output control of the synchrocheck module,
2. Verify that the synchrocheck module is set (if on/off synchrocheck input information is
configured).
In event of fail of one of these operations, the sequence ends with a negative acknowledgment
Second sequence (SBO ONCE): Close the device with synchrocheck:
Selection phase:
1. Close device selection output to select the device (if is configured),
2. Verify selection device input information associated to the output (if is configured),
3. Wait for the execution request or timeout selection,
244 C264/EN UM/E50.5

4. In event of fail of one of these operations the controls sequence is stopped with a negative
acknowledgment.
5. Close the device via the “close with synchrocheck” control,
7. Set off the synchrocheck module if is configured to be set off automatically,
Third sequence (DIRECT EXECUTE): set off the external synchrocheck module
This sequence takes place only if the setting off of the synchrocheck module is configured
“manual”
1. Open “set on/setoff” output control of the synchrocheck module,
2. Verify that the synchrocheck module is set on (if on/off synchrocheck input information is
configured).
The chronogram that follows shows a successful control sequence ”close with synchrocheck”
performed in three sequences. In event of automatic “setting off” of the synchrocheck module the
chronogram remains identical. It is performed at the end of the SBO sequence.
C264/EN UM/E50.5 245

- Figure 57 - Successful close with synchrocheck
NOTE: During SBO sequence after step 5 the initiator of the request may force the closing of the
device.
246 C264/EN UM/E50.5

4.5.3.2.3 Close synchronized circuit breakers with forcing

The chronogram that follows shows controls sequence ”close with synchrocheck” with “forcing
close request”. The SBO sequence is performed in the same way whether the synchrocheck
module is set on manually or automatically.
Awaiting the device be closed by the external synchrocheck module, the initiator of the request
force to “close without synchrocheck”.
C264/EN UM/E50.5 247

- Figure 58 - ”Close with synchrocheck” with “forcing close request”
4.5.3.2.4 Cancel Close CB with external synchrocheck

Awaiting close the device (0 to 60 minutes) by the external synchrocheck module, the initiator of
the close request may cancel this one by a “cancel request”.
The chronogram that follows shows a cancel close request awaiting close the device by the
external synchrocheck module.
248 C264/EN UM/E50.5

- Figure 59 - Cancel close request
4.5.3.3 Circuit breakers with internal synchrocheck

On this configuration synchrocheck is assumed by an internal computer automation, that
proceeds to the synchrocheck voltage calculations and gives or not the authorization to close the
device.
C264/EN UM/E50.5 249

The controls sequence remains similar with the external synchrocheck instead of the setting
on/off of the synchrocheck and close with synchrocheck output control that do not exist on this
configuration.
4.5.3.3.1 Close CB with internal synchrocheck with automatic set on

The following sequence describes a “close” request of circuit breaker with internal synchrocheck
in “SBO once” mode. Synchrocheck automation is set on automatically.
In “Direct Execute” mode the processing remain similar without selection of the device.
- Figure 60 - Close cb by internal synchrocheck with automatic set on
Selection phase:
3. Wait for the execution close request or timeout selection.
In event of fail of one of these operations, the device is deselected and the controls sequence is
aborted with a negative acknowledgment.
Execution phase:
4. Active the associated internal synchrocheck automation for authorization to close the
device,
5. Wait authorization to close:
Event 1: Synchrocheck automation respond OK before the time-out of the given delay
Close the device,
Deselect the device (if it was previously selected),
Send a positive acknowledgment.
Event 2: Synchrocheck automation responds NO before the time-out of the given delay
250 C264/EN UM/E50.5

Deselect the device (if it was previously selected);
Send a negative acknowledgment.
Event 3: time-out of the given delay without synchrocheck response
Stop the synchrocheck automation,
Event 4: reception of cancel request awaiting synchrocheck response
Stop the synchrocheck automation,
The chronogram that follows shows a successful control sequence ”close with internal
synchrocheck”.
C264/EN UM/E50.5 251

- Figure 61 - Chronogram of a successful "close with internal synchrocheck"
252 C264/EN UM/E50.5

The chronogram that follows shows an abnormal termination of control sequence ”close with
internal synchrocheck”.
C264/EN UM/E50.5 253

- Figure 62 - Abnormal termination of a "close with internal synchrocheck"
254 C264/EN UM/E50.5

4.5.3.3.2 Close CB with internal synchrocheck with manual set on

The following sequence describes a “close” request of circuit breaker with internal synchrocheck
in “SBO once” mode. Synchrocheck automation is set on by a separate direct execute control.
- Figure 63 - Close cb by internal synchrocheck with manual set on
First sequence (DIRECT EXECUTE): Set on the internal synchrocheck automation:
1. Set on synchrocheck automation for the device,
2. Set system input “on/off synchrocheck” (if its is configured).
Second sequence (SBO ONCE): close the device with synchrocheck”
Selection phase:
3. Wait for the execution request or timeout selection,
4. In event of fail of one of these operations the controls sequence is stopped with a negative
acknowledgment.
Execution phase:
1. Ask to the internal automation to close the device,
Note that the initiator of the request may force the closing of the device.
3. Set off the synchrocheck automation if is configured to be set off automatically,
Third sequence (DIRECT EXECUTE): set off the internal synchrocheck automation
This sequence occurs only if the setting of the synchrocheck automation is configured “manual”
C264/EN UM/E50.5 255

1. Set off synchrocheck automation,
2. Reset system input “on/off synchrocheck” (if it is configured).
4.5.3.3.3 Close CB with internal synchrocheck with forcing

Awaiting authorization from the internal synchrocheck for closing the device, the initiator of the
request may force the closing.
After time-out of the given delay without synchrocheck response:

• Stop the synchrocheck automation,
• Close the device,
• Deselect the device (if it was previously selected),
• Send a positive acknowledgment.
256 C264/EN UM/E50.5

- Figure 64 - ”close with internal synchrocheck” with “forcing close request”
C264/EN UM/E50.5 257

4.5.4 Control of disconnectors

4.5.4.1 Disconnectors features
MiCOM C264 computers manage all types of disconnecting switches such as:
• Disconnectors,
• Earthing switch,
• Quick break switch.
DISCONNECTORS SWITCHES
OUTPUTS TYPE A INPUTS ALL TYPES
DEVICE
DPC control for open/close of device DPS physical position of the device
CONTROL
DEVICE SPC (optional) control of device SPS (optional) device selection
SELECTION selection position information
4.5.4.2 Control sequence of disconnectors

The control sequence of disconnectors is identical to control sequence of the non-synchronized
circuit breakers.
4.5.5 Control of transformers

4.5.5.1 Transformer features
OUTPUTS INPUTS
TPI value
TRANFORMER
DPC: raise/lower SPS (optional) tap change in
CONTROL
progress (TCIP)
TRANSFORMER SPC (optional) transformer SPS (optional) selection position
SELECTION selection information
TRANFORMER
Double wound or Auto-wound
TYPE
where transformer type (auto-wound or double-wound) is user selectable.
Double wound (or two winding transformer) is a transformer with galvanic isolation between
primary and secondary coil. Tap Changer (with additional winding) is usually located at HV-
neutral side for economic reasons. Tapping-up (raise order) reduces primary winding and
increases LV voltage.
Auto-wound (or auto-transformer or single wound) is a transformer without galvanic isolation

between primary and secondary. Secondary coil follows primary coil, (windings are serial). Tap
Changer (with tap of additional winding) is serial. Increasing tap position (raise order) acts
simultaneously on primary and secondary, it reduces transformer ratio then voltage at LV side.
258 C264/EN UM/E50.5

4.5.5.2 Control sequence of transformers

You can control the transformers in the three modes “Direct Execute”, “SBO once” and “SBO
many”.
In addition to the selection and execution checks described in the previous paragraphs the
following checks are performed:
• A “raise” control is refused if the current tap position value corresponds to the maximum
position of the tap.
• A “lower” control is refused if the current tap position value corresponds to the minimum
• In event of “go to min”, “go to max” or “go to position x” request, an internal automatism
(via ISaGRAF®) has to be added. This automation generates the desired controls sequences
in order to reach automatically the expected position. It may generate “Direct execute”, “SBO
once” or “SBO many” sequences according the configuration of the device
NOTE: If the command of a transformer is configured in SBO many mode, it is impossible to

configure the requests “go to min”, “go to max”
TCIP feature: The TCIP input information (tap change in progress), is used to confirm the right
execution of the low/raise execution. Two delays are given by the configuration for the TCIP
management:
• TCIP apparition delay: The TCIP information have to appear before the time-out of this delay.
• TCIP disappearance delay: The TCIP information have to disappear before the time-out of
this delay.
TPI feature: Because the TCIP input information is not always configured, the tap control is
performed using only the Tap Position Indication (TPI) value to verify the right execution of the
request. The TPI value have to change in the given delay.
The following examples are given in “SBO many” mode that is the more complex. The main
difference with the “SBO once” mode remains to the possibility to execute many “raise” or “low”
controls before ending the sequence. Moreover, the device is not deselected automatically but
only after an deselect order is sent by the initiator of the control request.
4.5.5.2.1 Control of transformer with TCIP

In this mode, when the TCIP input information is configured, the selection and execution phases
are performed as follows: It is possible by configuration to prevent having more than one control at
a time.
Selection phase:
1. Close device selection output to select the device (if configured)
2. Verify selection device input information associated to the output (if is configured)
3. Wait for the execution request (low/raise) or timeout selection
In event of fail of one of these operations, the device is deselected, and the controls
sequence is aborted with a negative acknowledgment.
Execution phase:
C264/EN UM/E50.5 259

4. In agreement with the request “raise or lower” and the type of device, execute the associate
control
5. Wait for the TCIP data and TIP value to confirm execution. Two events:
• Event 1: The TCIP information appears and is disappears in the given delays, the TPI takes
the expected value: The computer sends a positive acknowledgment and waits a new request
(execution or deselection).
• Event 2: Timeout awaiting the TCIP appearance or disappearance, or the TPI value is wrong:
The device is deselected (if it was previously selected), and the sequence is aborted with a
negative acknowledgment.
6. Wait for the new execution request or deselection request to deselect the device
• In event of new request, the computer repeat the steps 4 and 5.
• In event of deselection request the computer deselects the device (if it was previously
selected), and ends the sequence with a positive acknowledgment
The chronogram that follows shows a successful sequence with device selection, two “raise”
controls and device deselection
The TPI should take the expected value at least at the end of TCIP disappearance.
The chronogram that follows shows an abnormal termination of tap changer control sequence
due to absence TCIP confirmation. In this event the device is automatically deselected, and the
sequence ends with a negative acknowledgment
260 C264/EN UM/E50.5

4.5.5.2.2 Control of transformer without TCIP

In event the TCIP input information is not configured, the selection and execution phase are
performed as follows:
Selection phase:
1. Close the device selection output to select the device (if configured)
2. Verify selection device input information associated to the output (if configured)
3. Wait for the execution close request or timeout selection
In event of fail of one of these operations, the device is deselected, and the controls
sequence is aborted with a negative acknowledgment.
Execution phase:
4. In agreement with the request “raise or lower” and the type of device, execute the related
control
5. Wait for the TPI data and compare with the previous value. The difference has to confirm the
“low” or “raise” execution. Two events:
Event 1: The TPI value confirms in the given delay the execution request: The computer
sends a positive acknowledgment and waits for a new request (execution or deselection)
from the initiator.
Event 2: Timeout awaiting the TPI value or unexpected TPI value: The device is deselected
(if it was previously selected), and the sequence is aborted with a negative
acknowledgment.
6. Wait for the new execution request or deselection request to deselect the device
In event of new request, the computer repeat the steps 4 and 5.
In event of deselection request the computer deselects the device (if it was previously
selected) and ends the sequence with a positive acknowledgment.
The chronogram that follows shows a successful sequence with device selection, a raise control
and device deselection
C264/EN UM/E50.5 261

The chronogram that follows shows an abnormal termination due to the absence of change of the
TPI value in the given delay. The device is automatically deselected, and the sequence is aborted
with negative acknowledgment.
4.5.5.2.3 Suppression, Forcing or Substitution of the TPI

In the event of suppress or substitution of TPI value the control sequence is aborted with negative
Acknowledgment. When Forcing the TPI value, the sequence is not aborted but the value of TPI
taken in account during the control sequence is the forced value.
4.5.6 Control of Intelligent Electrical Devices (IED)

Control requests to manage device via IEDs may be performed in the three modes (DE, SBO
once, SBO many).
262 C264/EN UM/E50.5

4.5.6.1 Direct Execute mode

If execution checks are successful
1. The computer sends the control (open/close, low/raise, setpoint) via the communication
protocol to IED.
2. Expects IED’s control acknowledgment in the given delay (If is supported by the protocol).
3. Expects the reception of the feedback of the request (device position SPS, DPS, TPI) in the
given delay (if is configured).
In event of fail in step 2 or 3 the sequence ends with a negative acknowledgment. Otherwise the
sequence ends with a positive acknowledgment.
4.5.6.2 SBO once mode

This mode can be configured only if is supported by the protocol.
4.5.6.2.1 Selection phase

After you perform the selection checks
1. The computer sends a selection request to the IED,
2. Expects selection acknowledgment from IED in the given delay,
3. Generates a positive or negative selection acknowledgment according to the result of the

selection phase,
4. If positive acknowledgment, the computer starts selection time-out and waits execution
request, otherwise ends the controls sequence.
4.5.6.2.2 Execution phase

If execution checks are successful
1. The computer sends the control, such as the open/close, low/raise, setpoint; thru the
communication protocol to the IED.
2. The computer expects the IED, if supported by the protocol, to send the control
acknowledgment within the given delay.
3. The computer expects the reception of the feedback of the request, such as the device
position SPS, DPS, TPI; within the given delay, if it is configured.
If successful, the sequence ends with a positive acknowledgment. In event of a failure in step 6 or
7, the sequence ends with a negative acknowledgment.
4.5.6.3 SBO many mode

In comparison with the “SBO once” mode, in this mode execution phase is repeated until an
deselection request. Unselection request allows you to end the sequence in the computer, and it
is not sent to the IED.
4.5.7 System controls

System control is used to activate or deactivate automatic functions, change computer’s mode,
bay mode, database management, etc.
C264/EN UM/E50.5 263

A system output control remains internal on the computer (has no digital or IED output) and may
generate a system input information. They are managed in “Direct Execute” mode only. A
hardware selection has no meaning.
For some uses, such as automation activation/deactivation, it is necessary to generate a system

input, that gives the state of the controlled function: for example, ATCC ON/OFF. This system
input may be able to be used by the control sequence or enter to an interlocking equation etc. The
configuration process allows the user to assign or not a system input, that may include an SPS or
DPS. System inputs generated by system outputs are stored in non-volatile memory. In event of
the computer’s initialization, they are restored.
4.5.8 Kinds of control sequences

The control sequences automation receives three kinds of input triggers (as orders from the
higher level) with selection, execution and deselection. Control orders may have a normal or
abnormal termination with positive or negative acknowledgment to operator and to
communication.
By configuration, each DPC order (close order or open order) and each SPC can activate
simultaneously two DO contacts at the same time.
4.5.9 Control sequences checks

Receiving control, the control sequence executes configured checks:
Operational conditions
• MiCOM C264 mode management (Operational, Test, Maintenance...),
• IED connected,
• Substation control mode (Remote/Local),
• Bay control mode,
• SBMC mode,
• Uniqueness of control inside the substation.
Module conditions
• Inter-control delay,
• Status of the device,
• Lock condition,
• Automation already running (AR, AVR, ATCC, …),
• Interlock equations (substation, bay, local of the module).
Execution conditions
• Delays upon selection feed back, start moving, final position reached.
4.5.9.1 Mode Management

Control sequences are only performed if the computer mode is in operational mode. In simul
mode, control sequences are allowed but digital outputs are not set.
264 C264/EN UM/E50.5

4.5.9.2 IED connected

If a control has to be sent to an IED, it is only accepted if this IED is connected to the computer.
4.5.9.3 Control mode

This control sequence receives requests from the various control points:
• Automation (Auto Recloser, voltage regulation, PLC),
• MiCOM C264 Local Control Display,
• MiCOM C264 TBUS communication from SCADA,
• Station BUS (other computer in distributed automation, EPAS Operator Interface,

EPAS-Gateway).
To avoid conflict between the control points, substation and bay modes are checked. Each control
sequence can be subject or not to these checks. The switches Remote/Local can be hardware or
software (saved in non-volatile memory).
The SBMC Site Based Maintenance Control allows controlling one specific bay from Local
Display or Operator interface even if substation is in remote. This feature is dedicated to
commissioning or maintenance and has also the possibility to filter data transmitted from the bay
to SCADA.
4.5.9.4 Uniqueness of control

It is possible by configuration to prevent having more than one control at a time:
• For the whole substation,
• Inside a bay.
If a device is under control and another control is sent on this device, the second one is ignored.
In event of uniqueness of the command at least to one of these levels the selection is refused,
with negative acknowledgment. The user may bypass this control during selection request.
4.5.9.5 Inter-control delay

It is possible by configuration to define an inter-control delay that is a minimum delay between two
consecutive controls on the same device.
4.5.9.6 Status of the device

If the status of the device is not valid, it is possible by configuration to prevent control.
4.5.9.7 Locked device

Controls are not allowed on a locked device.
4.5.9.8 Running Automation

If there is a related automation in operation, controls are not allowed on a device.
For example, controls issued from EPAS HMI or gateway are not allowed on a transformer
controlled by voltage regulation.
C264/EN UM/E50.5 265

4.5.9.9 Interlocking
The operation of a switching device, such as circuit breakers; traditional disconnecting switches;
disconnecting switches with abrupt rupture; and ground disconnecting switches; is directly related
to the nature of the switch and to its environment.
To operate these devices, you must respect some conditions. These conditions, called
interlocking, are managed by logical equations within the MiCOM C264.
Interlocking prohibits a control sequence that may violate the device operating condition: for
example, break capability, isolation, and so on; or plant operating condition.
4.5.10 HV Control Sequences

4.5.10.1 Circuit breaker
Several kind of circuit breaker (CB) can be managed:
• Three phase or triple phase circuit breaker,
• Single phase circuit breaker,
• Synchronized or non-synchronized circuit breaker, with internal or external synchrocheck,
• Circuit breaker with or without Auto Recloser.
Single Phase CB stands when the 3 phases are individually wired, while triple Phase CB stands
when only the resulting position of the breaker (3 phases) is wired. For single phase breaker each
phase DPS is provided separately and it is managed globally by single (grouped) control and
global DPS position. Pole Discrepancy management is available.
4.5.10.2 Disconnector
The control sequence of disconnectors is identical to single non-synchronized circuit breakers.
4.5.10.3 Transformer
Transformer position is determined using TPI (Tap Position Indication). TPI can be a Digital
Measurement or Analogue Measurement (from DC Analogue Input).
The transformer is the only device that supports the SBO Many control sequences. It is linked to
voltage regulation; its Raise and Lower controls are defined for secondary voltage (and not tap
position). For a classic transformer, requesting a raise will raise the tap, while for an
autotransformer it will lower the tap.
266 C264/EN UM/E50.5

4.6 Automation
BCPU provides three different ways to perform programmable automation functions:
• Programmable Scheme Logic (PSL) via Function Block Diagram editor (FBD editor),
• Programmable Logic Controller (PLC) via ISaGRAF® workbench.
• Built-in automation functions,
4.6.1 Safety information
CAUTION
UNEXPECTED PSL EXECUTION OF CONTROL
Carefully evaluate the impact of PSL automation before usage.
CAUTION
UNEXPECTED PLC EXECUTION OF CONTROL
Carefully evaluate the impact of PLC automation before usage.
4.6.2 Built-in Automation functions

Within the MiCOM C264, some built-in automation functions are available:
• Auto-Recloser,
• Trip Circuit Supervision,
• Circuit Breaker Condition Monitoring (I2t),
• xPS/xPC Association,
• Pole Discrepancy,
• Automatic Voltage Regulation (AVR),
• Automatic Tap Change Control (ATCC),
• Synchrocheck.
4.6.2.1 Auto-Recloser (AR)
4.6.2.2 Introduction
80-90% of faults on the electrical network are transient, such as lightning or insulator flashover.
When a fault occurs, the Circuit Breaker is tripped in order to protect the system.
C264/EN UM/E50.5 267

The Auto-Recloser function is then used to close the circuit breaker after a set time, a time that is
long enough to allow the fault to clear. This duration is called cycle delay and is defined in the
database during the configuration phase.
But, as permanent fault can occur, an auto-recloser scheme has to be provided in order to allow
the elimination of a transient fault by an open/close sequence (auto-reclosing cycle) and the
elimination of permanent fault by, after a defined number of auto-reclosing cycle (4 cycles
maximum), leaving the circuit breaker in the open state by closing the trip relay.
A transient fault, such as a lightning strike, is one that is cleared by immediate tripping of one or
more CB’s to isolate the fault and does not recur when the line is re-energised.
This means that in most fault incidents, if the faulty line is immediately tripped out, and if time is
allowed for the arc to de-ionise, reclosure of the CB will result in the line being successfully re-
energised (Closed/Open/Closed cycle).
However, some faults will be permanent (such as a line fallen to earth). In this event the auto-
recloser must be able to react to the permanent fault, and on the first reclose and detection of the
permanent fault open the CB’s and, if required lock out the auto-reclose functionality
(Closed/Open/Closed/Open cycle).
Auto-recloser (AR) schemes are implemented to carry out this duty automatically.
4.6.2.2.1 Behavior
The general diagram of the auto-recloser function follows:
268 C264/EN UM/E50.5

- Figure 65 - Auto-Recloser scheme logic
4.6.2.2.1.1 In Service / Out of service
The auto-recloser function can be in or out of service due to an operator control (through the
station bus, the computer local HMI or a BI).
If the auto-recloser is out of service, no cycle is authorized.
If an out of service request is received during an auto-reclosing cycle, the cycle is immediately
stopped.
4.6.2.2.1.2 Analysis of the receiving trip
This analysis allows you to detect the type of auto-recloser cycle, that can be:
C264/EN UM/E50.5 269

• The first single-phase cycle,
• The first 3-phase fast cycle,
• The second 3-phase slow cycle,
• The third 3-phase slow cycle,
• The fourth 3-phase slow cycle.
This detection is done by using:

• The current cycle number,
• The TRIP_1P_X or TRIP signal sent by the protection relay (single-phase trip / 3-phase trip),
• The configured auto-recloser cycles.
During this phase, if the CB_HEALTHY signal is not in the SET state, the cycle is not authorized,
and the automation re-initializes to wait for the first cycle. The CB_HEALTHY BI is optional: if it
does not exist, no check is done.
4.6.2.2.1.3 Waiting CB opening
As soon as the trip has been detected, a 150 ms timer is launched to wait for the circuit breaker
opening.
For a 3 single poles CB:

• If the CB position is on a per pole basis:
• In a single-phase cycle, only one phase position is awaited in the OPEN state (CB_STATE_
1P_X),
• In a 3-phase cycle, each one phase positions is awaited in the OPEN state.
• If the CB position is given globally:
• In a single-phase cycle, the position (CB_STATE) is awaited in the MOTION00 state,
• In a 3-phase cycle, the position (CB_STATE) is awaited in the OPEN state.
For a triple pole CB:

• Whatever was the cycle, the 3-phase position is awaited in the OPEN state (CB_STATE).
For a 3-phase cycle, the DO “AR_TRIP_3P” is closed (if configured) as soon as the CB is
detected as open.
The auto-recloser function is locked if the CB is not opened at the end of the timer.
4.6.2.2.1.4 Launch cycle timer
As soon as the CB is detected as open, the timer associated to the current auto-recloser phase is
launched.
During the single-phase cycle, the trip signal must disappear: if not, the auto-recloser function will
be locked. Furthermore, a 3-phase trip could appear. In this event, the current cycle is stopped,
and the second 3-phase slow cycle is launched.
270 C264/EN UM/E50.5

4.6.2.2.1.5 Closing the CB
At the end of the cycle timer, the AR_BLOCKING BI is tested: if it is in RESET state, a close order
is sent to the Circuit Breaker. Note that, if present, the synchrocheck function is used to control the
breaker during the second, third and fourth 3-phase slow cycles. The use of the synchrocheck
function during the first 3-phase fast cycle is configurable.
If the AR_BLOCKING BI is in another state, the automation is re-initialized to wait for the first
cycle.
4.6.2.2.1.6 Launch recovering time
As soon as all concerned CB phases are closed, the Reclaimc recovering timer is launched. If the
CB remains closed during the timer, the reclosing is considered to be successful and the cycle
number is set to 0. The “AR_STATE” signal is set at AR_RECLAIMC state during this timer.
If a new trip occurs during the timer, the next configured cycle is launched. If the trip occurs during
the last cycle, the auto-recloser is locked.
4.6.2.2.1.7 Particular treatments
Reclaim time on manual close
If the CB becomes closed (through an external maneuver) during an auto-recloser cycle, the
Reclaim delay timer is launched during which the auto-recloser function is inhibited and the “AR_
STATE” signal is set at the AR_RECLAIMMC state.
CB closing failure
If the CB closing order fails, due to DO hardware failure, interlocking scheme, or synchrocheck
inhibition, the AR_FAIL signal is set.
This BI is reset as soon as the CB is closed.
Lock of the auto-recloser
The conditions that lead to an auto-recloser locking are:

• A trip during the last auto-recloser cycle (in this event, the AR_STATE signal is set at the AR_
BAR_SHOTS state),
• A lock signal through the AR_LOCK Binary Input at the SET state,
• Trip BI state is Invalid (this BI cannot be suppressed, forced or substituted),
• CB position BI(s) state is (are) Invalid,
• The Trip BI is always set at the end of the cycle timer,
• There is no pole discordance at the end of the single-phase cycle: that is, the three phases
are opened,
• 2 phases are in an opened state at the end of the single-phase cycle without 3-phase trip
signal,
• The CB is not opened at the end of the 150 ms timer.
The AR_STATE signal is set at the AR_BAR_LOCK state if the auto-recloser function is locked,
and the cycle counter is set to 0.
C264/EN UM/E50.5 271

There are two configurable methods to unlock the function. These methods are selected during
the configuration phase and can be used separately or together:
1. A manual closing of a circuit breaker: in this event, the Reclaimmc timer is launched.
2. An “AR_LOCK” signal at the RESET, received either through a BI or an operator order.
If none of these methods are selected, the auto-recloser is automatically unlocked if no lock
condition is set and circuit breaker is closed. In this event, the Unlock delay timer is launched. If
the CB is not closed at the end of this timer, the auto-recloser is locked again.
4.6.2.2.2 Information and parameters
Information Description Type

CB_STATE_1P_
CB status, on a per pole basis BI (DP)
x
CB_STATE CB status (global) BI (DP)
TRIP_1P_x Trip status, on a per pole basis BI (SP)
TRIP 3-phase Trip status BI (SP)
Request to put in / out of service the
AR_IS/OS BI (DP) or operator control
auto-recloser
BI (SP, Group) or output of a
Signal to lock / unlock the auto-
AR_LOCK configurable automation or operator
recloser
control
Availability of the breaker to be
CB_HEALTHY BI (SP)
closed
Signal to block the closure of the BI (SP, Group) or output of a
AR_BLOCKING
circuit breaker configurable automation
CB_ORDER_
CB order, on a per pole basis DO
1P_x
CB_ORDER CB order (global) DO
This information can be wired to a
AR_TRIP_3P 3-phase trip forcing order DO or can be used as an internal
signal.
Auto-recloser status: In / Out Of
AR_IS/OS SI (DP)
Service
AR_STATE Auto-recloser current state SI (MP)
values list:
Indicate the auto-recloser is in
AR_READY service, unlocked and no cycle is in State0
progress
AR_WAIT_FOR_ Indicate the auto-recloser is waiting
State1
OPEN_CB CB opening
272 C264/EN UM/E50.5

Information Description Type

AR_FIRST_ Indicate the first single-phase cycle
State2
CYCLE_1P is in progress
AR_FIRST_ Indicate the first 3-phase cycle is in
State3
CYCLE_3P progress
AR_SECOND_ Indicate the second 3-phase cycle is
State4
CYCLE_3P in progress
AR_THIRD_ Indicate the third 3-phase cycle is in
State5
CYCLE_3P progress
AR_FOURTH_ Indicate the fourth 3-phase cycle is in
State6
CYCLE_3P progress
AR_WAIT_FOR_ Indicate the auto-recloser is waiting
State7
CLOSE_CB CB closing
Indicate the Reclaimc timer is
AR_RECLAIMC State8
launched
AR_BAR_ Indicate an auto-recloser locking due
State9
SHOTS to a max number of reclosing cycles
AR_BAR_LOCK Indicate an auto-recloser locking State10
AR_ Indicate the reclaimml timer is
State11
RECLAIMML launched
AR_ Indicate the reclaimmc timer is
State12
RECLAIMMC launched
AR_FAIL Failure of the close order: SI (MP)
Values list:
AR_SYNC_NOK Due to the synchrocheck State0
Due to hardware failure, lock of
AR_HARD_
device or another running State1
ERROR
automation linked to the device
AR_ILOCK_NOK Due to interlocking function State2
AR_NO_FAULT No failure State3
Parameter Description Value

Auto-recloser type o cycle
AR_TYPE Mono / Tri
configuration
AR_CYCLE_
Number of cycles 1, 2, 3 or 4
NUMBER
1P_CYCLE1_ From 10 ms to 5 seconds, with a 10
Timer of the first single-phase cycle
TIMER ms step
C264/EN UM/E50.5 273

Parameter Description Value

3P_CYCLE1_ From 10 ms to 60 seconds, with a 10
Timer of the first 3-phase cycle
TIMER ms step
3P_CYCLE2_ From 1 to 3600 seconds, with a 1
Timer of the second 3-phase cycle
TIMER second step
Timer of the third 3-phase cycle
TIMER second step
Timer of the fourth 3-phase cycle
TIMER second step
RECLAIM_ From 1 to 600 seconds, with a 1
Reclaim timer
TIMER second step
RECLAIMMC_ From 1 to 600 seconds, with a 1
Reclaimmc timer
TIMER second step
RECLAIMML_ From 1 to 600 seconds, with a 1
Reclaimml timer
TIMER second step
UNLOCKING_ None, manual close, unlock signal,
Method to unlock the auto-recloser
METHOD both
Use the synchrocheck function
SYNC_ENABLE Yes / No
during the 3-phase first cycle
4.6.2.3 Trip Circuit Supervision

The trip circuit supervision monitors the trip circuit wiring continuity irrespective of CB position but
only when the trip relay is not activated. Activation of the trip relay is indicated to the MiCOM C264
by a separate input and inhibits the detection of continuity.
For the DIU211/CCU211 boards, the Trip Circuit Supervision function is not available.
The MiCOM C264 computer supports these two diagrams used in Trip Circuit Supervision (see
following figures):
• Trip Circuit Supervision with one Digital Input + external resistor,
• Trip Circuit Supervision with two Digital Inputs without external resistor.
For the Trip Circuit Supervision with one Digital Input + external resistor, the resistor (R) in the trip
circuit supervision scheme should have a value in agreement with 2 limits:
1. High enough so that once the CB is open, the tripping coil powered via the resistor has no
magnetic effect anymore so that the tripping mechanism is released (within a possible delay
due to inductive effect of the coil).
2. Low enough so that the MiCOM C264 input powered via the resistor (and the tripping coil) is
detected active.
Therefore:
1. It is assumed that 10% of nominal voltage applied on the tripping coil makes its magnetic
effect low enough to release the tripping mechanism after activation. Taking into account
274 C264/EN UM/E50.5

normal tolerance on power supply, this leads to a minimum value of R being approximately
10 to 12 times the resistance of the tripping coil.
2. The input was tested to operate with a series resistor up to 40kOhm, still leaving voltage
across the input above the minimum. Taking into account tolerances, this defines a
maximum value for the resistor of 20kOhm.
We recommend the value in the middle of the range (geometrically). If Rc is the resistance of the
tripping coil, then:
R / 12xRc = 20kOhm / R
The power rating of the resistor must be such that it withstands permanent application of
maximum trip circuit voltage. Therefore:
P = (1.2 x Uaux)2 / R
- Figure 66 - Trip circuit supervision with one DI
C264/EN UM/E50.5 275

- Figure 67 - Trip circuit supervision with two DI
Use this previous diagram for inputs that have a detection threshold > 55% for the "set" state: for
example, CCU200 A07.
4.6.2.4 Circuit breaker condition monitoring (I²t)

The MiCOM C264 makes records of various statistics related to each circuit breaker trip
operation. This allows you to make a more accurate assessment of the condition of the circuit
breaker. The MiCOM C264 mainly calculates the sum of the switched current over a period.
The MiCOM C264 can separately evaluate each phase current and estimate each CB pole wear.
The CB manufacturers usually provide the maximum number of permissible CB operations in

relation to the disconnection current characteristics.
When an overcurrent event causes a circuit breaker to trip, then the MiCOM C264 performs the I²t
function.
4.6.2.4.1 Acquisition and computation

The MiCOM C264 accumulates from the latest reset:
• The current - time integrals per pole,
• The square current - time integrals per pole,
• The current - time integrals of all the poles,
• The square current - time integrals of all the poles.
Each integral is calculated between the trip command time and the time when the RMS value is
less than 0.1A.
Example:
276 C264/EN UM/E50.5

- Figure 68 - Integration time
4.6.2.4.2 Reset
All the stored values can be simultaneously reset. This control can be available at all control
points.
4.6.2.4.3 Monitoring
The MiCOM C264 can monitor each accumulated value with two thresholds settable
independently and display an overrun event on the local mimic or activate a LED.
The information can feed in any local or distributed automation scheme.
4.6.2.4.4 Inhibition
The function can be disabled through a setting.
To prevent the sums from accruing, for example during a test, use:
• The pre-defined “blocking SPS” existing with protective function,
• The pre-defined “blocking control” existing with protective function,
• The MiCOM S1 - PACiS.
4.6.2.4.5 Storage
The values are stored in a non-volatile memory to save them in event of auxiliary power outage.
A dedicated procedure allows you to set the stored values with the CAT on a per measurement
basis.
The switch of any new configuration database does not reset any of the stored values, but a
software download does.
In event of a MiCOM C264 redundancy, the stored values in the standby computer are exchanged
from Main to Standby after each calculation.
C264/EN UM/E50.5 277

4.6.2.5 Automatic Voltage Regulation–AVR

4.6.2.5.1 Presentation
4.6.2.5.1.1 Role
MiCOM C264 with AVR (Automatic Voltage Regulation) is a compact Voltage Regulation solution
for Electrical Substations; it automatically regulates the voltage level on the secondary side of
HV/MV and/or MV/MV transformers.
It is able to automatically send commands (Raise, Lower) to the Tap Changer, fully aware of the
transformer characteristics (voltage,…), the Tap Changer characteristics (position number, inter
tap timers,…), the voltage targets and the various transformer or tap changer alarms.
NOTE: the AVR function cannot be used on one MiCOM C264 together with another built-in
function.
4.6.2.5.1.2 Topologies
Two MiCOM C264 types are defined to address specific AVR issues:
• Type 1 for a single transformer,
• Type 2 for transformers in parallel (secondary poles are interconnected in pairs) – mode
Master-Followers (up to 4 followers MiCOM C264 with AVR).
4.6.2.5.1.3 Modes
The operator decides on the LHMI how to operate the AVR:

• Manual (open loop): the operator forcefully issues Raise/Lower commands to the tap changer
from the LHMI,
• Automatic (closed loop): the AVR algorithm issues Raise/Lower commands to the tap
changer when the voltage is outside limits and tap changer conditions permit; the operator
can still deactivate the algorithm from the LHMI.
The possibility of other manual controls in automatic mode depends on the parameter manual
controls allowed:
• Not allowed,
• Only when AVR is locked (whether it is due to the External regulation locking or to an AVR
additional features: overcurrent detection, tap changer blocking),
• Always.
278 C264/EN UM/E50.5

4.6.2.5.1.4 Interfaces for a single transformer
4.6.2.5.1.5 Hardware architecture
The MiCOM C264 includes in a 40 TE rack:

• An LCD screen, a BIU2xx board and a CPU275 board
• A DIU2xx board to acquire 16 Digital Inputs:
5 Tap Position Indications (typically on 6 bits with BCD encoding, up to 64 bits with BCD,
Gray, binary codes,),
2 CB positions,
1 VT Fuse,
1 Tap Changer fault (option),
+7 customizable DIs (Bay L/R, AVR Auto/Manu, AVR on/off, alarms, external lock,
voltage target selection).
• A DOU20x board to control 10 powerful Digital Output relays:
2 Raise/Lower controls,
1 AVR fault (WatchDog),
1 AVR Mode Auto/Manu,
1 AVR ON/OFF,
1 Master /Follower signal (type 2 only),
1 Minimize Circulating Current signal (type 2 only),
+3 (type 1) or 5 (type 2) customizable DOs (I>, V>, alarms, locking, …).

• A TMU220 board (4 CTs / 5 VTs) for direct acquisition of currents and voltages:
CT: 1 thru 3 phases (type 1), 3 phases (type 2) + 1 earth,
VT: 1 thru 3 phases (type 1), 3 phases (type 2) + 2 customizable inputs.

• An AIU board (option) to acquire Tap positions, voltages… (4-20 mA)
C264/EN UM/E50.5 279

• An AOU board (option) for analogue outputs (4-20 mA) to repeat the Tap changer positions or
measurement values (voltages, circulating currents…),
4.6.2.5.1.6 Exchanges over the bus
The IEC 61850 bus can convey additional data:

• TPI and Tap changer status, “tap pulse duration”,
• power factor,
• target voltages and target voltage setpoint, compounding method,
• topology information from IEDs (in place of serial bus) or other MiCOM C264,
• settings from MiCOM S1 - PACiS,
• measurements and commands when several transformers are involved.
Each transformer is controlled by one computer but the AVR function is only activated on one
computer. The figure exemplifies an architecture that controls two transformers:
AVR function is activated on computer C264-1. This computer gets analogue values through the
station bus from computers C264-2 and C264-3 and issues tap changer commands through the
station bus.
4.6.2.5.2 Moving a tap changer

In this part, the settings name and values are surrounded with quote marks (“…”), while the first
letters of status labels are capitalized. The former are set, the latter positioned.
4.6.2.5.2.1 Actual voltage
Depending on the “Regulation types”, the actual (i.e. measured) voltage can be:
• either a “phase voltage Van” (Vpn on the first schematic),
• or a “compound voltage Ubc” (Vpp on the first schematic).
The actual voltage can include a Line Drop Compensation (see further).
280 C264/EN UM/E50.5

For double wound transformer (“double wound” set to Yes), according to the setting “double
wound voltage”, the automatic voltage regulation applies to the:
• voltage and current of one winding (voltage 1),
• voltage and current of the other winding (voltage 2),
• average voltage and current of the 2 windings (average voltage).
If the difference between the 2 voltages is larger than a set value (“double wound voltage
difference”), the signal Double wound voltage difference is positioned.
4.6.2.5.2.2 Target voltage
Depending on the Target voltage management, the target voltage can be:
Locally or Remotely
The Remote / Local target voltage management mode is running when the Target Voltage
Management Mode is set to Remote/Local and the AVR is in automatic mode. The target voltage
used by the AVR is either a remote target voltage received from a remote control point, or a local
target voltage used in the case of unavailable remote target voltage (invalidity, loss of
connection).
The remote target voltage comes from a remote control point (setpoint from any client by IEC
61850 or other available protocol); to be valid, it is subjected to min, max, max difference; until the
end of the confirmation delay, the latest valid remote target voltage value is used.
In event of invalid remote target received, the local target voltage takes over. The local target
voltage is configured with SCE and can be modified with MiCOM S1 - PACiS.
Controlled
The remote / local target voltage is selected through controls.
In local target voltage mode, the AVR can treat an incoming remote target voltage value (in order
to return to the remote target voltage mode). If a received remote target voltage value is valid, the
remote target voltage becomes the new target voltage mode, following the transition local to
remote conditions:
• At AVR start up, the local target voltage mode is active for a defined delay (end of local target
voltage delay).
• If a valid remote target voltage value is received before the end of the delay, the remote target
voltage mode is set at the end of the delay.
• If a valid remote target voltage value is received after the end of the delay, the remote target
voltage mode is set immediately.
When the target voltage mode changes from remote to local, the same delay is launched, and the
behavior is identical.
An operator can, with a dedicated control, forcefully put the target voltage mode to local target
voltage. In this event, the mode is set immediately.
Period dependent
For example:
C264/EN UM/E50.5 281

4.6.2.5.2.3 Regulation
The actual voltage is compared to the target voltage.
If the actual voltage remains outside of the “regulation deadband” for an “initial tap time delay”
(TA1), the MiCOM C264 with AVR commands a tap change.
Any voltage swing that passes through the complete deadband, causes the “initial tap time delay”
to be reset and a new time cycle to be started.
If more than one tap change is required to bring back the voltage within the deadband, the second
tap changer is activated after TA2 (“inter tap time delay”), where TA2 < TA1.
If applicable, the last tap changing is delayed by an “end tap delay”.
The command occurs only if the following conditions prevail:

• AVR mode is automatic,
• voltage is above the “voltage presence threshold”,
• “Primary CB state”, Circuit Breaker position on the primary side of the transformer is set to
CLOSED,
• No VT fuse information positioned,
• No regulation locking signal (External Lock or Tap Changer fault) positioned.
282 C264/EN UM/E50.5

4.6.2.5.3 Additional monitoring functions
4.6.2.5.3.1 Tap Changer position on Voltage Loss
The actual voltage is present/missing (lost) whether it is above/under the “voltage presence
threshold”.
According to the “voltage loss position tap”, the AVR can:

• either move the tap changer “on a defined tap”,
• or “lock the automatic” regulation if the voltage is missing.
In the first case, the “tap changer position (on voltage loss) behavior” can be set to:
• keep the tap changer on the “current tap” (no tap control performed),
• move the tap changer to the “preset tap”,
• move the tap changer to the “lowest tap”.
The function sets the tap changer on the “defined tap” position, only if the following conditions
prevail:
• The AVR mode is automatic,
• “Tap changer position on voltage loss” function is active,
• The “Primary CB state”, Circuit Breaker position on the primary side of the transformer is set
to OPEN,
• No other regulation locking information is set,
• No VT fuse information positioned.
Sequencing of commands: the subsequent command occurs not earlier than the “preset tap
delay”.
4.6.2.5.3.2 Fast Tap Changer move AFTER Voltage Loss and Voltage recovery
When the “Fast tap changer move after voltage loss” function is set, the AVR issues Lower/Raise
commands TA3 after the voltage has overrun the “voltage presence threshold“.
The command occurs only if the following conditions prevail:

• The AVR mode is automatic,
• “Fast tap changer move after voltage loss” function is active,
C264/EN UM/E50.5 283

• The “Primary CB state”, Circuit Breaker position on the primary side of the transformer is set
to CLOSED,
• No VT fuse information positioned,
• No regulation locking signal (External Lock or Tap Changer fault) positioned.
If all the above conditions prevail, and the voltage is present (voltage above “voltage present
threshold“) longer than the “voltage present delay” (Ta), the first tap delay is bypassed for TA3
(first tap delay bypass delay). The first tap control activation is delayed by TA2.
If the “fast tap changer move after voltage loss” function is NOT active, when the voltage is
detected, the first tap control activation is delayed by TA1.
4.6.2.5.3.3 Abnormal Voltage signalization
The voltage is considered as “abnormal” if, till the confirmation time expires, the actual voltage is
moving outside the range: [Vtarget x (1- β%) ; Vtarget x (1+ β%)] , β% is the “abnormal voltage
(threshold)“. This range is wider than the deadband. Refer to the preceding schematic.
In this event, the signalization is positioned after the “abnormal voltage delay”.
Any return of the voltage into the normal range resets the delay and deactivates the abnormal
voltage signal.
4.6.2.5.3.4 Tap Changer Failure supervision – Tap Blocking
The Tap Position Indication value may be wired on digital inputs (or optional analog inputs).
If the Current Tap value is not valid, all the functions using this information are locked.
The signalization indicates the kind of problem on the tap changer.
The signalization Tap Changer Fault results from one of these conditions:
• the tap value is undefined (coding error),
• after the “TCIP time out delay”, the TCIP (Tap Changer In Progress) signalization is not
positioned (on tap control sequence),
• after the “TCIP end time out delay”, the TCIP signalization input is not reset (on tap control
sequence),
284 C264/EN UM/E50.5

• after the TCIP signalization reset, the tap has not the expected value,
• after the global sequence delay (start on 1st tap control), the voltage is not normal yet,
or, if the “tap changer fault function” is on,

• an external signalization indicates a tap changer fault.
When the signalization Tap Changer Fault is positioned, the tap control or the sequence of tap
controls in progress is canceled, and no more tap control is accepted (whether it is manual or
automatic).
Depending on the “tap changer fault behavior”, when a tap changer fault occurs, AVR can:
• position the Tap Changer Fault signalization, and reset it when none of the faulty condition
prevail (automatic reset),
• position the Tap Changer Fault signalization, and keep it set until an operator deactivates the
automatic regulation and activates it again (manual reset).
If the “tap changer blocking activation” is on, a Tap changer Blocked is positioned in event the Tap
command is issued for a time longer than the “tap changer blocking delay”. This means that the
tap position is not reached during this time and this is considered abnormal.
A signalization Voltage Regulation Fault is positioned with the corresponding status, when:
• a VT fuse is detected,
• an abnormal voltage is detected,
• a voltage or current acquisition failure is detected,
• a Tap Changer is blocked.
When none of the above problems is detected, the signalization Voltage Regulation Fault status is
OK.
4.6.2.5.3.5 Tap Changer Lowest / Highest position
MiCOM C264 with AVR monitors the pair Tap changer Lowest/Highest reached position.
• When the current tap equals the “highest/lowest tap value”, the indication Highest/Lowest Tap
reached is positioned.
• If the Tap Position Indication value is not valid, The Lowest / Highest Tap reached indications
are not valid.
4.6.2.5.3.6 Run away protection
MiCOM C264 with AVR monitors if the Tap changer operates without valid commands or if tap
changer operation causes Tap Changer to move further away from the set values.
If it occurs, after the “runaway tap delay”, an alarm is raised and the AVR can be blocked.
4.6.2.5.3.7 OverVoltage Detection
The “overvoltage detection activation” is settable; it can also be done by an operator control.
If the value of the voltage is larger than the “overvoltage threshold” for more than the “overvoltage
delay”, the Overvoltage signalization is positioned.
C264/EN UM/E50.5 285

If the value of the voltage becomes lower than the “overvoltage threshold”, the Overvoltage
signalization is reset.
The regulation locking information can be positioned/reset depending on the Overvoltage

signalization.
If the voltage value is not valid, the overvoltage detection is not running.
Depending on the “Overvoltage detection behavior” value, the AVR can:

• position/reset the Overvoltage signalization,
• position/reset the Overvoltage signalization AND the Regulation Locking information.
4.6.2.5.3.8 UnderVoltage Detection
“Undervoltage detection activation” is settable; it can also be done by an operator control.
If the value of the voltage is lower than the “undervoltage threshold” for more than the
“undervoltage delay”, the Undervoltage signalization is positioned. If the value of the voltage
becomes larger than the “undervoltage threshold”, the Undervoltage signalization is reset.
The regulation locking information can be positioned /reset depending on the Undervoltage
signalization.
If the voltage value is not valid, the undervoltage detection is not running.
Depending on the “Undervoltage detection behavior” value, the AVR can:

• position/reset the Undervoltage signalization,
• position/reset the Undervoltage signalization AND the Regulation Locking information.
4.6.2.5.3.9 OverCurrent detection
“Line overcurrent detection activation” is settable.
If the value of the current is larger than the “overcurrent threshold” for more than the “overcurrent
delay”, the Overcurrent signalization is positioned.
If the value of the current becomes lower than the “overcurrent threshold”, the Overcurrent
signalization is reset.
The regulation locking information can be set/reset following the line overcurrent signalization.
If the line current value is not valid, the line overcurrent detection is not running.
Depending on the “Overcurrent detection behavior” value, the AVR can:

• position/reset the Overcurrent signalization,
• position/reset the Overcurrent signalization AND the Regulation Locking information.
4.6.2.5.3.10 Tap Changer Maintenance: Tap Counting
The numbers of automatic + manual tap changes are counted as follows:
286 C264/EN UM/E50.5

On the “slipping since latest operator

Number since MiCOM C264 init
period for counting” reset
Overall changes x up to 6,000,000 X
Raise x up to 3,000,000 X
Lower x up to 3,000,000 X
Limits reached x – –
For each tap as long as
Time of use – Time of use
voltage is present
The date of the latest operator reset is also recorded.
On operator reset
• the partial number of “tap changes”, “raise” and “lower” controls are reset,
• the partial time of use with voltage present of each tap is reset,
• the current date becomes the new “last reset date”.
The time of use is recorded, only if the voltage is present, and the Tap Position Indication and the
TCIP signalization are valid.
Data visualization and use
Histograms are shown on a dedicated page of the MiCOM C264 Maintenance Tool. Refer to the
IN chapter (Operations with buttons/Statements).
As counters, all the sums can be viewed:

• on the Station Bus (IEC 61850)
• on a SCADA line
• on the Local HMI
and be used as inputs of ISaGRAF® sequences, e.g. for threshold management.
Data storage
Data are stored in a secured SRAM memory and are not lost:
• on MiCOM C264 restart,
• on database switching (over some conditions),
• on power outage for less than 48h.
4.6.2.5.4 Line drop compensation

To regulate the voltage at a remote point on the feeder, the LDC simulates voltage drop of the line
and artificially boosts transformer voltage at times of high load.
The LDC is validated by the “compounding activation” and ruled by the active “compounding
method”.
C264/EN UM/E50.5 287

Vr = Vm - Vcomp
Z = R + jX, R and X are % of Vn/In
R = “Active compounding method parameter A1”, % of Vn/In (nominal voltage and current)
X = “Active compounding method parameter B1”, % of Vn/In (nominal voltage and current)
The reactive “compounding method” is used only when two transformers are in parallel.
4.6.2.5.5 Other functions
4.6.2.5.5.1 Additional Measurements (Optional)
If 3 CTs and 3 VTs are fed into the MiCOM C264, additional measurements can be computed:
• Frequency,
• φ,
• Cosφ,
• I sinφ, S I ² since the latest reset of counters,
• Active and apparent powers,
• Circulating current (transformers in parallel).
These calculated measurements can be viewed locally on the Local HMI (LCD Screen).
4.6.2.5.5.2 Raise lower control and voltage target from external signals
Depending on “AVR mode”, additional inputs can be used:

• “Automatic”: to activate a specific target voltage:
• Target Voltage 5 (Vn-5%),
• Target Voltage 2, 3, 4 (Voltage Boosting).
These external commands have precedence over the Local LCD commands and are active as the
external signal is positioned.
• “Manual”: to activate Raise/Lower commands from wired signals:
288 C264/EN UM/E50.5

• Raise Command Input,
• Lower Command Input.
The activation of Raise/lower Controls also depends on the usual AVR conditions (CB status, TC
fault,…).
4.6.2.5.5.3 Reverse Power Flow (RPF)
Detection
Reverse power flow is detected with the sign of the secondary Active Power measurement value.
If the Active Power measurement value is above 0, no reverse power flow is detected.
If the Active Power measurement value is under 0, the reverse power flow detection delay starts.
At the end of the delay, if the Active Power measurement value is still under 0, the signaling
Reverse power flow detected is positioned.
When reverse power flow is detected, if the Active Power measurement value is above 0, the
reverse power flow detection delay starts. At expiry, if the Active Power measurement value is still
above 0, the signaling Reverse power flow detected is reset.
Reverse power flow detection is done only if the line current value is more than or equal to the
defined RPF current threshold. Otherwise, no reverse power flow detection is performed.
Behavior
When reverse power flow is detected, the RPF management mode defines the behavior:
• Ignore: nothing specific is done is this case, regulation is still performed in the same way.
• Block operation: no more automatic regulation is performed; only manual raise and lower
control are allowed (if set). The automatic voltage regulation is locked by reverse power flow,
and the signal AVR locked by reverse power flow is positioned. This signal is reset when the
reverse power flow detection ends.
• Regulate in reverse: the automatic regulation is running in reverse power flow mode.
C264/EN UM/E50.5 289

The transformer primary side analog measurements (U, and if compounding is used: I and φ) are
needed for automatic regulation. These measurements are received by the AVR, and not
computed from transformer secondary side analog measurements.
The automatic voltage regulation is monitoring the primary voltage, current and phase difference,
and keeps the primary voltage in a deadband within a target voltage by activating raise/lower
controls. The parameters defined for “normal power flow” regulation are not used in the case of
RPF regulation.
The AVR activates the tap changer with a RAISE control, after a first (or next) tap delay, if:
• Primary Voltage > Target voltage for primary voltage x (1 + Deadband).
The AVR activates the tap changer with a LOWER control, after a first (or next) tap delay, if:
• Primary Voltage < Target voltage for primary voltage x (1 - Deadband).
With Primary Voltage = Measured primary voltage – Z x Measured primary current
The tap changer raise/lower activation is inverted in RPF regulation mode.
Compounding in RPF mode
Z is the complex load impedance defined by the parameters A1 and B1 for active compounding,
and parameters A2 and B2 for reactive compounding.
The values can be doubled individually by activating a setting.
Coefficients A1 and B2 are specific with the Compounding in RPF mode.
Active compounding: Z = R + jX, R = A1 x compounding ratio, X = B1 x compounding ratio.
Reactive compounding: Z = R - jX, R = A2 x compounding ratio, X = B2 x compounding ratio with:

• compounding ratio = (nominal voltage / √ 3) / (compounding nominal current x 100),
• nominal voltage: the same nominal voltage as for normal regulation (secondary of
transformer),
• Compounding nominal current: a nominal current defined in database only for compounding
management (this compounding nominal current is defined for both normal regulation and
reverse power flow regulation).
Compounding in reverse power flow mode is available only with single phase voltage.
If no compounding is needed, the A1, B1, A2 and B2 values must be set to 0.
Other differences
No check on voltage presence is done. When RPF is detected, it means the voltage is present on
both sides of the transformer.
The following AVR functions are not available:

• Abnormal voltage detection,
• Overcurrent detection,
• Overvoltage detection,
• Undervoltage detection,
290 C264/EN UM/E50.5

• Tap changer position on voltage loss,
• Fast tap changer move after voltage loss,
• Tap changer blocking,
• Tap changer with intermediate position,
• Transformer double wound voltage management.
The target voltage can be changed (within its range) with the setting tool or with a dedicated
setpoint control. All the target voltage management modes usable in the normal power flow
regulation mode are not available.
Limits:
• Not usable with a double wound transformer.
• Usable only with standalone transformer management even when in normal power flow (not
with a transformer in parallel method). Master / follower configuration must be set to none.
4.6.2.5.6 Transformers in parallel

Two methods can be used whether the transformers are identical and work together or not.
4.6.2.5.6.1 Master Followers method
ROLES:
In a group of transformer bays, one MiCOM C264 with AVR is appointed “Master”, the other
“followers”. The master transmits its TPI to the followers over the Station Bus and elaborates the
commands for all the transformers. All the operator controls (activation/deactivation), if any, are
put on the master MiCOM C264, which in turn activates/deactivates the followers.
The followers receive the master’s TPI, offset any discrepancy with their own TPI and execute the
commands coming from the master over the Station Bus.
C264/EN UM/E50.5 291

The Master compares the tap position of the followers with its own tap position and if deviations
are detected, the master put commands to bring them to its own position.
No circulation currents are evaluated; this imposes severe limitations on the network operation:
• transformers identical, with the same impedance,
• same number of taps,
• transformers on the same tap position.
The indication of which MiCOM C264 is the Master and which one is “Follower” can be viewed
• on LCD (optional MiMIC Page),
• on configurable Leds of the Front Panel,
It can be available
• on an output contact,
• on the Station Bus / Scada,
and used in PSL/ISaGRAF® automation.
In event of the Master failure (reboot, disconnection, switching to maintenance mode) the “Master
failure management” offers two possible fallback plans:
• a Backup Master can be selected among all the followers:
• manually by the operator (on LCD or from Station Bus),
• automatically to insure a continuous service, using the configured “Follower Master Backup”.
If the master recovers, the backup master remains master. The master regulates its voltage in
stand alone mode.
This backup mode requires a good health network. In event of a faulty network, the TPI received
by the followers, still have the quality Unknown. Then, after the “backup mode delay”, all the
followers will switch to a standalone mode.
If the mode goes automatically to standalone, returning requires a manual operation (reset
process in which the master restarts all the followers).
• drop the coupled regulation: all the MiCOM C264s operate standalone.
4.6.2.5.6.2 Standalone regulation
There are no restrictions on the transformers.
The differences between two transformers superimpose a current Ic in both incomers:
If the transformer #1 is on a higher tap than #2:

• Current seen by #1 = IL + Ic
• Current seen by #2 = IL – Ic
292 C264/EN UM/E50.5

Two methods are offered:

• “Minimizing circulating current”: refer to the ATCC section further.
The topology (i.e.which transformers are interconnected) is dynamically evaluated by a

MiCOM C264-MCC (minimize circulating current). It computes the U,I,P,Q for all the
MiCOM C264 that control transformers (up to 4) and transmits the values over the Station
Bus.
• “Negative reactance compensation”, in conjunction with the Reactive “Compounding
method”.
As Ic is not present in the feeder, another method is needed: compensating the voltage
attenuation due to currents circulating from one transformer to the other.
With reactive compounding, the voltage to be regulated (Vr) is evaluated as follows:
Vr = Vm – Vxl, where:
Vr = actual voltage to regulate,
Vm = measured voltage,
Vxl = Compounding voltage = Z.I where Z = R – jX,
R = “Reactive compounding method parameter A2”, % of Vn/In (nominal voltage & current),
this the resistive part of the load line,
C264/EN UM/E50.5 293

X = “Reactive compounding method parameter B2”, % of Vn/In (nominal voltage & current),
this the reactive part of the transformer impedance (the transformer impedance is mostly a
reactance).
For a power factor near 1, this negative reactance compensation has a good accuracy, but if
the power factor is low, this compensation mode is no more accurate.
4.6.2.6 Automatic voltage regulation–ATCC

The Automatic Voltage Regulation–ATCC function automatically maintains a correct voltage at
the lower voltage of transformers by controlling the tap changer of transformers.
4.6.2.6.1 Presentation
4.6.2.6.1.1 Topologies
A substation includes busbars and transformers.
A group is a set of interconnected busbars. A transformer belongs to a group if it is electrically

connected to a busbar of this group at the low voltage level. The voltage target is that of the
highest priority busbar.
The partition is dynamic: two independent groups may be merged as a result of the closing of a
circuit breaker.
Typical topologies:
• one busbar connected to one or several transformers in parallel. Transformers are in parallel
if their secondary poles are interconnected;
• several coupled busbars in a group that includes one transformer or several ones in parallel
(see an example further);
• Each transformer is controlled by one computer but ATCC function is only activated on one
computer. The figure that follows shows an example of the architecture for the ATCC function
that controls two transformers.
ATCC function is activated on computer C264-1. This computer gets analogue values through the
station bus from computers C264-2 and C264-3 and sends tap changer commands through the
station bus.
294 C264/EN UM/E50.5

4.6.2.6.1.2 Situations requiring ATCC
ATCC is activated when:

• The voltage in one group is far from the Target Voltage. This is the most common situation.
• The voltage is correct, but there is a circulating current between parallel transformers. This
happens when two groups are interconnected.
• The voltage is correct, but the Tpi range and patterning may be changed when the state of
any relevant switchgear changes.
4.6.2.6.1.3 Definitions and main attributes
For a transformer:
Homing (status): if a transformer is disconnected from the busbar (the “homing circuit breaker” at
the LV side of the transformer is open), it can follow the busbar voltage in order to avoid
overvoltage at re-connection. This capability is selected on a global basis.
Hunting (status): if the same transformer has received more change controls than the opposite
max tap changes within a time window, the ATCC is deactivated. These attributes are set on a
global basis.
For a busbar:
Line drop compensation: in case two interconnected busbars are far from each other, to
compensate the resistive and reactive voltage drops across the power line, several compounding
methods are available. The method is selected on a global basis and the coefficients on a per
busbar basis.
The main attributes to set on the various levels are as follows (bracketed):
This schematic exemplifies two independent cells:

• a stand-alone transformer operating in manual mode (ATCC status is off),
• a group operating in automatic mode (ATCC status is on).
The operator sets the global status to on.
C264/EN UM/E50.5 295

4.6.2.6.1.4 Capacity
A MiCOM C264 is able to manage a maximum of:

• 7 transformers,
• 4 transformers in parallel,
• 8 busbars,
• 4 transformers per busbar,
• 2 reactances per transformer,
• 2 voltage levels.
4.6.2.6.1.5 Alarm conditions
The attribute names used in SCE are bracketed if it helps identify the datapoint.
Transformer:
• MCB trip. If a transformer is in automatic control and there is an invalid evolution of the tap
changer, the tap changer MCB is tripped.
• Run away: if the Tap changer operates without valid commands or if tap changer operation
causes Tap Changer to move further away from the set values. This alarm is reset 30 s after
the group is switched to ATCC Off.
• Bay disconnected (includes power failure) [disc eqt].
• Local bay: contains the tap change control: local/remote, connected/disconnected

(supervision values).
• Invalid voltage [inv voltage].
• Tap changer abnormal if:
• TCIP signal is too late [TAP bad TCIP] or too long [TAP long TCIP],
• The tap is invalid [TAP invalid]: tap number is not the required tap; you may have this problem
after a tap operation if the tap number is not the expected one.
This TAP bad TCIP alarm is reset 30 s after the group is switched to ATCC Off.
• ATCC hunting: this alarm is reset 30 s after the group is switched to ATCC Off.
• Overcurrent, overvoltage.
Busbar:
• Invalid voltage (when different values for parallel transformers) [inv voltage],
• More than 4 transformers in the group [max transfo],
• A circuit breaker or a disconnector in an invalid state in the group [inv module].
Global:
• Target unreached,
• ATCC defect: raised if one of these alarms is raised, and is reset if all of them are reset,
296 C264/EN UM/E50.5

• Error Log Indication: raised if one of the inputs is raised and is reset if the operator selects the
"Clear ATCC Faults" command,
• DBI override.
4.6.2.6.2 Monitoring logic
4.6.2.6.2.1 Modes
From the EPAS HMI or from a SCADA, in agreement with the Substation control mode, the
operator controls the Global ATCC mode (substation level) and the busbar ATCC modes.
Substation
Control from the RCP (SCADA) Control from the SCP (HMI)
control mode
Local inhibited allowed
Remote allowed inhibited
It is up to the operator to choose, on a global basis, how the mode (that is, the ATCC status) is
changed:
• On group interconnection: the group resulting of the merging of two groups in different modes
can be off or on,
• When bay turns to local control: the bay can go off or on.
4.6.2.6.2.2 Conditions for an active automatic voltage regulation
The following conditions are required for automatic regulation to be active:

• The ATCC mode is on,
• The Circuit Breaker at the other side of the transformer (primary) is closed,
• No “regulation locking” information (AVR defect alarm, external lock, run away, overcurrent
on a transformer).
For ATCC/homing to take place:

• the measured voltage must be within tolerances set as ratios of the nominal voltage:
• tolerable nominal under voltage,
• tolerable nominal over voltage.
• the deviation to the target voltage must be lesser than a set ratio of the nominal voltage:
• max voltage difference.
Moreover, before sending a tap changer control (Raise/Lower), the following conditions are
required:
• No “tap in progress“,
• No “higher position” information, for a raise control,
• No “lower position” information, for a lower control.
C264/EN UM/E50.5 297

4.6.2.6.2.3 Transformers status logic
4.6.2.6.2.4 Busbars status logic
The current busbar mode is equal to (busbar ATCC status) AND (Global ATCC status).
The status is Off if:

• the status of one of the transformers connected to it is Off,
OR
• the busbar voltage is invalid.
4.6.2.6.2.5 Group status logic
The average voltage is invalid if:

• one of the voltage differs by more than “max voltage difference” (ratio) from the average
voltage,
OR
• one voltage is invalid.
The status is On if at least one of the busbars in the group is On.
The status is Off if at least one of the conditions that follow is met:
298 C264/EN UM/E50.5

If two busbars get disconnected, they keep their previous mode.
When a fault occurs, the related busbar ATCC turns off.
4.6.2.6.3 Moving tap changers
4.6.2.6.3.1 Target voltage
When the operator changes a target voltage, the new target voltage is indicated immediately. The
actual target voltage cannot change by more than the “voltage target ramping rate” if the busbar is
under automatic control. If the busbar is not under automatic control the new target voltage is
immediately in force.
Each voltage level has other attributes:

• 5 voltage targets, with a default target (one of the 5),
• 2 deadbands, one is coarse (DB1, to initiate tapping), the other is fine (DB2, to end tapping),
• a max tap change rate of change that cannot be exceeded when moving the tap.
Each busbar voltage target is selected among the 5 through controls, in accordance with the
voltage target ramping rate.
If the busbar is part of a group, the target in force is the one of the highest priority busbar. A single
tap is changed at a time within a group, but several groups may be active simultaneously.
Each group has to reach the target voltage.
If the voltage is outside DB1, then an initial timer T1 is set and the tap control is issued once the
timer has elapsed.
More tap changing may be necessary in order to enter DB2: they are actuated when the second
timer T2 has elapsed; the changing is subjected to the max tap change rate.
REMOTE BUSBAR:
The voltage target may be set for a point far from the LV transformer side.
Reference_Ulv = (Target_ Ulv + Drop_U) x set point ponderation (0.9 …1)
Ulv is the actual measured value
Compounding methods:
• Setpoint adjustment: Drop_U ² = Plv x R% + Qlv x X% where
Plv and Qlv are local measured active and reactive powers
R% and X% are resistive/reactive coefficients
C264/EN UM/E50.5 299

• Voltage adjustment: in place of Ulv, use Drop_U ² = (Ulv –A)² + B² where
A = (Rl x P + Xl x Q)/ Ulv
B = (Xl x P + Rl x Q)/ Ulv
Xl and Rl are transfo-busbar resistive/reactive coefficients
NOTE: If line drop compensation is not used, set the resistive and reactive coefficients to the
minimum.
4.6.2.6.3.2 Voltage is outside of the Target Voltage Deadband
When the regulated voltage moves outside of the deadband settings for a definite time, the
MiCOM C264 send commands to Tap Changer mechanism to bring it back within the set
deadband limits.
The Voltage Deadband is expressed as a percentage of the nominal voltage. Depending on the
number of transformers in a group, different set coefficients are applied.
Voltage deadband = Base Voltage deadband x voltage coefficient.
Examples:
example 1 example 2
Group with 1
1 1
transformer
Group with 2
1 1
transformers
Group with 3
1 2/3
transformers
Group with 4
1 1/2
transformers
Decision to move the tap changer is made when:

• Voltage > Target Voltage + Voltage Deadband x Nominal Voltage,
OR
300 C264/EN UM/E50.5

• Voltage < Target Voltage - Voltage Deadband x Nominal Voltage for more than the time-out
T1.
Dual deadbands are used to ensure that the post tapping voltage is sufficiently closed to the
selected target voltage. DB1 is used to initiate tapping and DB2 is used to end tapping.
4.6.2.6.3.3 Timeouts
Moving the taps of the transformers is achieved with respect to some time-outs:
The "Initial tap" of a transformer is delayed by a time out T1, the next ones by a time out T2.
Several taps are used if one is not enough to reach the voltage target or the optimization of the
circulating current. T2 begins after the end of the TCIP.
When the voltage drifts in and out of the deadbands, the system counts up to T1 when the voltage
is outside of the deadband1. If the voltage returns within the deadband2 before T1 is reached,
then the system counts down to 0.
Any voltage swing that passes from through the complete deadband from one side to the other,
causes the “initial tap time delay” to be reset and a new time cycle to be started.
After an auto-recloser operation, the group (or the two new groups) keeps the same ATCC
modes; however, the count is reset to zero and the new time delay is T1.
• Initial tap delay T1 is adjustable between 15 and 120 s in 0,1 s increments.
• Inter tap delay T2 is adjustable between 0 and 120 s in 0,1 s increments.
To ensure that transient voltage fluctuations do not cause unnecessary tap change, the voltage
must remain outside of the deadband for an “initial Tap Time Delay” (settable T1).
Any voltage swing that passes from through the complete deadband from one side to the other,
causes the “initial tap time delay” to be reset and a new time cycle to be started.
If a tap changing is required after a previous tap control:

• Ti is the date when the previous tapping was performed,
• T is the current time,
• RateMax is max tap change rate,
• T2 is the inter tap delay,
• Vi was the secondary voltage at Ti,
• V is the current secondary voltage.
For a Tap Up (to increase voltage), tap is changed when
T > Ti + T2 and V < Vi + RateMax x (T–Ti)
For a Tap Down (to decrease voltage), tap is changed when
T > Ti + T2 and V > Vi – RateMax x (T–Ti)
The maximum voltage rate is achieved as described in the example below:
C264/EN UM/E50.5 301

- Figure 69 - Voltage regulation
Tap RAISE 1 is performed after T1.
Tap RAISE 2 is performed T2 after Tap RAISE 1, at this time the voltage change rate is lower than
the maximum rate.
Tap RAISE 3 is NOT performed T2 after Tap RAISE 2, because at this time the voltage change
rate is more than the maximum rate. It is performed when the current voltage change rate
becomes lower than the maximum rate.
It is possible to choose a T1 delay as a fixed delay or not, i.e. an inverse time delay.
When inverse initial time delay is selected: the deviation is:
DV = | actual group voltage - deadband limit voltage |

• IF DV < 1% target voltage THEN initial tap delay = T1.
• IF 1% ≤ DV < 10% target voltage THEN initial tap delay = T1/DV.
• IF DV ≥ 10% target voltage THEN initial tapdelay = T1/10.
Example: Target = 135,96 T1= 40,00 s DeadBand2 = 136,64
302 C264/EN UM/E50.5

DV = (BusBar- %DV =
Busbar Time Out
DeadBand) (DV*100)/Target
%DV <1%:
137 0,36 0,26 40,00
Timeout = T1
139,03 2,39 1,76 22,75
140,01 3,37 2,48 16,14
141,01 4,37 3,21 12,44 1% < %DV <10%:
143,04 6,40 4,71 8,50 Timeout =
145,04 8,40 6,18 6,47 T1/%DV
146,01 9,37 6,89 5,80

150,01 13,37 9,83 4,07
151,02 14,38 10,58 4,00
%DV >10%:
152,05 15,41 11,33 4,00
Timeout = T1/10
153,03 16,39 12,06 4,00
When a transformer belongs to a group of several transformers, the time out is applied to the
group. 2 different groups have separate timeout references, thus allowing simultaneous taps.
The tap is defined as the "first one" when (logical OR):

• The group mode has changed,
• The voltage comes back into the deadband2,
• When the voltage crosses from one side of the deadband to the other side.
4.6.2.6.3.4 Homing
When the mode of the busbar is in automatic control, homing taps transformers such that their
open circuit terminal volts follows the volts on the busbars that they are selected to within 3% of
the busbar voltage.
Homing is active:
• If there is at least one transformer connected on the related busbar and,
• If the transformer busbar disconnector is closed and,
• If LV circuit breaker open.
Homing is disabled while the busbar voltage is less than Umin (80% of nominal voltage).
If a transformer is under Homing Mode, a manual control is not accepted.
If (and only) a fault on the Tap Changer remains active, the transformer remains OUT of
automatic control. As a consequence, homing ceases as long as the Tap Changer is faulty and
until the operator selects "Clear AVR faults".
Homing Initial tap delay is used for the first tap in the homing mode.
Homing Inter tap delay is used between successive taps.
C264/EN UM/E50.5 303

4.6.2.6.4 Calculation modes for a busbars group

If a group includes more than one transformer and is in automatic control mode, then the
coordination of the transformers of the group aims at minimizing the circulating power. To achieve
this, there exist three calculation modes depending on the substation constraint and customer
requirement. By configuration one of the three is chosen.
For the three following calculation modes, if all the transformer tap-changers reach their end stop
while tapping is required to go further, then the substation alarm "target unreached" is generated.
When the problem is cleared, this alarm disappears.
First calculation mode: “TAP”
In this event, the assumption is:

• The primary voltages of the transformers are identical,
• The number of taps and tapping ranges of the transformers are identical.
Then the maximum Tpi range between the transformers will be 1 and there will be a balanced
control of them when the voltage is changing.
Calculation is as follows:
• if voltage is OUT of the deadband and
• under the deadband -> action is raise on the transformer with the lowest Tap,
• over the deadband -> action is lower on the transformer with the highest Tap,
• if voltage is IN the deadband, the system sets the transformer within one tap.
Second calculation mode: “Transformer ratio”
In this event, the assumption is that the primary voltages of the transformers are identical.
Calculation is as follows:
• if voltage is OUT of the deadband and,
• under the deadband -> action is raise on the transformer with the lowest transformer ratio,
• over the deadband -> action is lower on the transformer with the highest transformer ratio,
• if voltage is IN the deadband, the system sets the transformer within a percentage of the
transformer ratio. This percentage P is calculated for all groups:
P = Maximum (Tpi range / (number of taps - 1))
Example:
Group with 3 transformers:

• SGT1: 19 taps, Tpi range = 30 %
P = Max (30 / 18; 30 / 18; 20 / 15) = 30/18 % = 1.67 %
So, the 3 transformers stay within 1.67 %.
Tap operation if (ratioMax - ratioMin) > 0,0167 ratioNom, with:
304 C264/EN UM/E50.5

• ratioMin = Minimum transformer ratio of the 3 transformers
• ratioMax = Maximum transformer ratio of the 3 transformers
• ratioNom = Nominal secondary voltage / Nominal primary voltage (defined in configuration)
Third calculation mode: “circulating current minimization”
There is no assumption that the primary voltages of the transformers are identical.
Example of two transformers:
Each transformer is characterized by:

• Sn (power value)
• x (% impedance at Sbase = 100 MVA), in other words X (reactance) = x . Un² / Sbase
• U, I, P, Q
• Current tap
• Un (nominal secondary voltage)
A transformer can be presented as below:
C264/EN UM/E50.5 305

The transformers can be presented as below:
306 C264/EN UM/E50.5

U = E1 - X1.I1 = E2 - X2.I2 => E1-E2 = X1.I1 - X2.I2
I = I1 + I2
E1 - E2 = (X1 + X2 ) . Ic
=> the circulating current Ic = (X1.I1 - X2.I2) / (X1 + X2)
For each transformer, we have U,I,P,Q (U1,I1,P1,Q1 and U2,I2,P2,Q2)
For i=1 or i=2, Qi/Pi = tan ji
According to the signs of Pi and Qi: -p < ji j2.
Voltage out of the deadband
If the voltage is out of the deadband and active power > 0 (|j| < p/2) then:
• If the voltage is under the target then transformer with highest |j| is tapped UP,
• If the voltage is over the target then transformer with lowest |j| is tapped DOWN.
If the voltage is out of the deadband and active power < 0 (|j| > p/2) then:
• If the voltage is under the target then transformer with lowest |j| is tapped UP,
• If the voltage is over the target then transformer with highest |j| is tapped DOWN.
For three or four transformers, the same algorithm is used.
C264/EN UM/E50.5 307

Voltage into the deadband
If the voltage is into the deadband then the circulating current must be checked to know if it is
possible to reduce it.
∆U = E1 – E2 = |X1*I1 - X2*I2|
∆U is compared to the voltage step corresponding to one tap (∆U1tap).
Tpi range: tap span for the transformer
NbTap: number of taps for the transformer
Un: nominal secondary voltage
∆U1tap = (Tpi range/(NbTap -1)) x Un
if ∆U > ∆U1tap and if ji > jj so
If the voltage is out of the deadband and active power > 0 (|j| < p/2) then:
• If the voltage is under the target then transformer with highest |j| is tapped UP,
• If the voltage is over the target then transformer with lowest |j| is tapped DOWN.
If the voltage is out of the deadband and active power < 0 (|j| > p/2) then:
• If the voltage is under the target then transformer with lowest |j| is tapped UP,
• If the voltage is over the target then transformer with highest |j| is tapped DOWN.
For three or four transformers, the same algorithm is used.
4.6.2.7 Synchrocheck
4.6.2.7.1 Synchrocheck – General
It is impossible to plug the computers directly into the high voltage electric network. The
computers receive the data from the Current Transformers (CT) and from Voltage Transformers
(VT) installed on the TMU2xx boards.
The purposes of the CT and VT include:

• To deliver current and voltage data that gives a reliable picture of what happens in the high
voltage part of an electrical substation,
• To make the galvanic insulation between the high voltage part and the measurement and
protection circuits,
• To protect the measurement circuits against damage when a fault comes onto the high
voltage network.
These measurements are used for the protection function and for the Internal Synchrocheck,
Type 1 and 2
The synchrocheck device allows you to couple together 2 electrical networks.
These networks can be connected to different sources (generator), so they are not synchronized
with each other.
The Synchrocheck function measures two voltages with respect to phase angle, frequency and
magnitude to protect against the connection of two systems that are not synchronized with each
other.
308 C264/EN UM/E50.5

In a computer, you can use the synchrocheck function for as many as 2 circuit breakers. You can
control only one circuit breaker at one time. The set of parameters defined for the synchrocheck
applies for both circuit breakers.
There are 2 types of internal synchrochecks (see "Synchrocheck Type 1 and Type 2" on page
311):
• • Type 1: actual internal synchrocheck,
• • Type 2: new internal synchrocheck.
When 2 electrical networks are synchronized with each other:

• Voltages are identical (plus or less a dispersion),
• Frequencies are identical (plus or less a dispersion),
• Phases are identical (plus or less a dispersion).
The synchrocheck computes these measurements and accepts or not the closure of the circuit
breaker that would connect them.
One phase voltage of the line and one phase of the busbar are connected to the synchrocheck.
- Figure 70 - Synchrocheck schematic
The busbar used phase isn’t always the first one. It is defined by configuration.
In event that you have two busbars, the used phase must be the same.
4.6.2.7.2 Synchrocheck Schemes

The synchrocheck schemes include:
• DD: Dead Line, Dead Bus
• DL: Dead Line, Live Bus
• LD: Live Line, Dead Bus
• LL: Live Line, Live Bus
C264/EN UM/E50.5 309

4.6.2.7.3 Synchrocheck Algorithm
4.6.2.7.4 Synchrocheck Applications

For synchrocheck applications, please refer to the figure that follows:
- Figure 71 - Synchrocheck applications
4.6.2.7.5 Synchrocheck Circuit Breaker Closure types

There are four types of circuit breaker closure types:
• Close with synchro
Close request with synchrocheck,
310 C264/EN UM/E50.5

• Manual Close
Close request without synchrocheck or when the synchrocheck is out of service,
• Automatic Close
Close request from auto-recloser,
• Manual override
Synchrocheck override.
4.6.2.7.6 Synchrocheck Type 1 and Type 2

Two types of synchrocheck are defined:
• Type 1: based on NGC,
• Type 2: specific for Terna.
The differences between them are the requirements used to accept closure.
4.6.2.7.7 Synchrocheck Hardware constraints and use
Synchrocheck Synchrocheck Second Busbar Open/close

Type 1 Type 2 usage contact
TMU220+DSP YES NO YES DOU

TMU210+DSPIO YES YES NO DSPIO or DOU
When the CB is wired on the DSPIO board, the DSPIO directly manages the close/open contacts.
Otherwise, the PPC manages the contacts using a CCU or a DOU board.
Both contacts must be wired on the same kind of board: 2 on DOU/CCU or 2 on DSPIO. One
contact wired on the DOU, and one contact wired on the DSPIO is not allowed.
4.6.2.7.8 Synchrocheck Calculation

Whatever the synchronizing mode DV, Dj and DF have to be calculated. These values are
available through the measurement module.
DV is calculated through the RMS value of the voltages on both bus bar and line side.
The value of DF is assumed to be constant across the period. As a result, knowing Dj (through
measurement), we know when the synchrocheck conditions are achieved (this will easily include
the reaction time of the breaker also).
time_synchro = 2 * pi *DF / Dj
For more details, please refer to the topic Focus 3: TMU2XX: CT / VT measurement processing
as far as Threshold Detection.
4.6.2.7.9 Synchrocheck Introduction to Harmonics

The use of power electronics distorts what would ideally be a perfect sine wave. These distortions
are called harmonics. Each individual harmonic has a sine wave shape. The order of the
harmonic is defined by the frequency of the harmonic divided by basic frequency (50 / 60 Hz). The
total harmonic distortion (THD) represents the sum of all voltage harmonics. The total demand
distortion (TDD) is like the THD but applied to currents and with a rated current (In) as reference.
C264/EN UM/E50.5 311

4.6.2.7.10 Synchrocheck – Check Synchronizing – Locking Mode

The check synchronizing mode is the default synchronizing mode. Check synchronizing is acting
when “the frequencies are similar”.
It is performed if the DF value is less than a user configured value (generally less than 0.1 Hz). If
so, the CT-VT module computes DV and Dj. If these values are less than a user configured
threshold, the system closes the breaker. In the other hand, the CT-VT module prevents the
closure of the breaker if the system synchronizing has not been activated and one of the previous
conditions is not achieved.
4.6.2.7.11 Synchrocheck – System Synchronizing – Coupling Mode

System Synchronizing is acting after Check synchronizing is being refused because of the
difference of frequencies that is greater than the configured threshold for Locking, and of course
inferior to the threshold of coupling.
System synchronizing is opposite to check synchronizing. When the CT-VT module receives a
close control and if the DF value is under a user defined threshold, the CT-VT module goes into
the system synchronizing mode.
The system synchronizing should have a predictive role. This means that the CT-VT module
should calculate the time to wait before the authorization of the closure by taking into account the
complete command line, including the mechanical characteristics of the circuit breaker. This time
should be user configured.
Note that after a user defined delay, the CT-VT module should exit the system synchronizing
mode.
4.6.2.7.12 Synchrocheck Scheme LL: Live Line, Live Bus: Real Time Sequences
For LL we have two types of synchronization:
• Locking: also referred to as check synchronizing
It is defined by some requirements: frequencies difference, and so on.
If they are all less than the configurable thresholds, the closure is immediately accepted.
Generally, these requirements are very restrictive: for example, Delta F < 0.1Hz
• Coupling: also referred to as system synchronizing
It is also defined by some requirements: frequencies difference, and so on.
This has a predictive mode: the computer includes a time T and calculates if the coupling
conditions will be met T seconds later. This time is user configurable.
4.6.2.7.12.1 Locking allowed / coupling not allowed by configuration
Example 1:
312 C264/EN UM/E50.5

1. If a close order comes before T1, it is rejected.
2. If a close order comes between T1 and T2, it is executed at T2 if the locking conditions are
not lost. If the locking conditions are lost before T2 then the command is rejected.
3. If a close order comes after T2, it is accepted.
4.6.2.7.12.2 Locking allowed / coupling allowed by configuration
Example 1:
1. If a close order comes before T1, it is sent to the DSP board, and the control is executed at
T2 coming from DSP board.
2. If a close order comes between T1 and T2, it is buffered until T2 if the locking conditions are
not lost. If the locking conditions are lost before T2 then the command is rejected.
3. If a close order comes after T2, it is accepted.
Example 2:
C264/EN UM/E50.5 313

2. If a close order comes between T1 and T2, it is buffered. As the locking conditions are lost
then the order is sent to the DSP and executed at T4.
3, 4. If a close order comes between T2 and T4, it is sent to the DSP board, and the control is
executed at T4 coming from DSP board.
5. If a close order comes after T4, it is sent to the DSP board, and the control is executed
immediately from DSP board.
Example 3:
2. If a close order comes between T1 and T2, it is buffered. As the locking conditions are lost
then the order is sent to the DSP and executed at T4.
3. / 4. If a close order comes between T2 and T4, it is sent to the DSP board, and the control
is executed at T4 coming from DSP board.
314 C264/EN UM/E50.5

5. If a close order comes between T4 and T5, it is sent to the DSP board, and the control is
executed immediately from DSP board.
6. If a close order comes after T5, it is sent to the DSP board, and the control is rejected after
the synchrocheck waiting time (not illustrated on the above drawing).
4.6.2.7.13 Synchrocheck Schema with VLINE and NOT(VBUSBAR) voltage controls

In event of the absence of one of the two voltages, at the end of a settable delay T2, the
authorization to close is given:
- Figure 72 - Vline and not(Vbusbar) voltage control
If, during the T2 delay time, one of the 2 criteria is lost, the timer is reinitialized and is launched
again on reappearance of all the criteria.
4.6.2.7.14 Synchrocheck Schema with NOT(VLINE) and VBUSBAR voltage controls

In event of the absence of one of the two voltages, at the end of a settable delay T2, the
authorization to close is given:
- Figure 73 - not(Vline) and Vbusbar voltage control
4.6.2.7.15 Synchrocheck Schema with NOT(VLINE) and NOT(VBUSBAR) voltage control

In event of the absence of both voltages, at the end of a settable delay T3, the authorization to
close is given:
- Figure 74 - Not(Vline) and not(Vbusbar) voltage control
4.6.2.7.16 Synchrocheck Schemes that use VLINE and VBUSBAR voltage control
4.6.2.7.16.1 Locking scheme ( synchronous mode )
If these conditions are met, the authorisation to close will be given:
C264/EN UM/E50.5 315

• Presence of both voltages AND,
• The difference in amplitude (algebraic) between the two voltages (DV) is lower than the
configurable / settable threshold (Evect) AND,
• The phase difference between the two voltages (Dj) is lower than the configurable / settable
threshold (Ephase) AND,
• For type 1:
• The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin and Fmax are
the extreme acceptable frequencies AND,
• The difference between the two frequencies (DF) is lower than the configurable / settable
threshold (Efreq).
• For type 2:
• The frequency shift between signals (S) is lower than the configurable / settable threshold
(Sfreq).
These conditions must be still met before the time-out of a delay T1 started on the appearance of
the conditions else the synchrocheck function will not authorise the CB closing.
If during the delay time T1 one of these conditions is lost, T1 is reinitialised and is re-launched on
reappearance of all the conditions.
Figure 72: Locking scheme for type 1
Figure 73: Locking scheme for type 2
4.6.2.7.16.2 Coupling scheme ( asynchronous mode )
In the coupling scheme, the CB can be closed only when the Dj is equal to 0.
To authorise the closing, these conditions must exist:
316 C264/EN UM/E50.5

• Presence of both voltages AND,
configurable / settable threshold (Evect) AND,
• For type 1
• The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin and Fmax are
the extreme acceptable frequencies AND,
• The difference between the two frequencies (DF) is lower than the configurable / settable
threshold (Efreq).
• For type 2
• The shift between signals (S) is lower than the configurable / settable threshold (Sfreq) AND,
• The shift acceleration (accShift) is lower than the configurable / settable threshold (accSfreq).
These conditions must still be met before the time-out of a delay T1 started on the appearance of
the conditions else the synchrocheck function will not authorise the CB closing.
If during T1 one of these conditions is lost, the delay time is reinitialised and is relaunched on
reappearance of all the conditions.
Figure 74: Coupling scheme for type 1
Figure 75: Coupling scheme for type 2
Since a CB has a response time, it is necessary to wait a known Dj to anticipate the response time
and to close the breaker with a Dj equal to 0.
When Dj = DF*360*Ta ± D(Dj), where Ta is the anticipation time or response time of the circuit
breaker and D(Dj) is the acceptable mistake on Dj, then the closing authorisation will be sent.
4.6.2.7.17 Synchrocheck Type 1 - Logic of Interlock Authorization

The voltage control depends on the synchrocheck type. The absolute values of the two voltages
(VLINE and VBUSBAR) must be above or below settable thresholds, to allow the circuit breaker
closing. VLINE is one of the phase voltages you define in the configuration.
The voltage controls include:

• VLINE and VBUSBAR for network coupling,
• VLINE and VBUSBAR for network locking,
• VLINE and not (VBUSBAR),
• Not (VLINE) and VBUSBAR,
• not(VLINE) and not (VBUSBAR).
If the measured voltage is above the threshold V>, then VLINE and VBUSBAR is TRUE.
If the measured voltage is below the threshold V<, then not(VLINE) and not(VBUSBAR) is TRUE.
The selection of the voltage control is made during the configuration phase.
By configuration, a single synchrocheck can manage two circuit breakers. In that case, voltage
switching is not managed by the computer.
C264/EN UM/E50.5 317

4.6.2.7.18 Synchrocheck Type 2 - Logic of Interlock Authorization

The voltage control depends on the synchrocheck type. The absolute values of the two voltages
(VLINE and VBUSBAR) must be above or below settable thresholds, to allow the circuit breaker
closing. If all three of the phase voltages are greater than the threshold, VLINE is present.
The following voltage controls are available:

• VLINE and VBUSBAR for network coupling,
• VLINE and VBUSBAR for network locking,
• VLINE and not (VBUSBAR),
• Not (VLINE) and VBUSBAR,
• not(VLINE) and not (VBUSBAR).
If the measured voltage is above the threshold V>, then VLINE and VBUSBAR is TRUE
If the measured voltage is below the dropout value defined by a configurable parameter, then not
(VLINE) and not(VBUSBAR) TRUE. The configurable parameter is a percent of the threshold V>
(95% for presence condition and 105% for absent condition).
By configuration, a single synchrocheck can manage two circuit breakers. In that case, voltage
switching is not managed by the computer.
4.6.2.7.19 Synchrocheck Bypass

4.6.2.7.20 Synchrocheck Bypass - Purpose
The internal synchrocheck has two main purposes:
• Close a CB between 2 non synchronized network (coupling mode),
• Ensure an energizing check when a CB is closed within a synchronized network (voltage

check).
If the synchrocheck is in service, the “Conduite” process sends a Coupling Close request to the
Synchrocheck process.
If the synchrocheck is out of service, the “Conduite” process sends a Manual Close request to the
Synchrocheck process.
Synchrocheck process replies with a positive (close is possible) or negative (close is not possible)
acknowledge.
4.6.2.7.21 Synchrocheck Bypass - Functional Description

To help determine if you must perform a voltage check, the MiCOM C264 database includes
definitions for closing schemes. For each type of control (Synchro Close, Manual Close and
Automatic Close) and for each type of voltage check (coupling, locking, bus dead line live, bus live
line dead and bus dead line dead), a yes/no flag is managed in the database.
For each type of voltage check, a new dedicated Binary Input (BI) (scheme BI) is used to
dynamically update the closing schemes in agreement with the type of control. For example, the
same Bus Live Line Dead Scheme BI is used for all the types of controls. Another dedicated BI
(bypass BI) is used to bypass the voltage check, whatever the type of control.
The added BI include:
318 C264/EN UM/E50.5

• Coupling scheme BI,
• Locking scheme BI,
• Bus Live Line Dead scheme BI,
• Bus Dead Line Live scheme BI,
• Bus Dead Line Dead scheme BI,
• Voltage check bypass BI.
When the BI bypass state is SET, the Bypass BI enables the closing.
If the Flag Yes/No is set to NO for one type of voltage check, the close request is refused
(acknowledge: Synchro NOK).
3. Close Requests:
- Synchro Close
2. State
- Manual Close
1. Voltage - Automatic Close
checks
BI scheme 4. Synchrocheck
Flag Yes / No BI bypass state
state Acknowledge
- Coupling
- Locking No Reset Reset Refused
- Bus Live No Reset Set Refused
Line Dead
No Set Reset Refused
- Bus Dead
No Set Set Refused
Line Live
- Bus Dead Yes Reset Reset Refused
Line Dead Yes Reset Set Bypassed
Yes Set Reset Accepted
Yes Set Set Bypassed
Refused: Involves a negative acknowledge (Synchro NOK) sent to the “Conduite” process.
Accepted: If the voltage conditions agree with the closing scheme, involves a positive
acknowledge sent to the “Conduite” process.
Bypassed: Involves a positive acknowledge sent to the “Conduite” process, without checking the
voltage conditions.
When the synchrocheck process sends the positive acknowledge to the “Conduite” process, an
interlock check is performed, before closing the Circuit Breaker. If the interlock condition is True,
the Circuit Breaker closes immediately, else the synchrocheck process sends a negative
acknowledge (Interlock NOK) to the control sender.
4.6.2.7.22 Phase-to-Phase Synchrocheck with the TMU210

4.6.2.7.23 Phase-to-Phase Synchrocheck with the TMU210 - General
With the TMU210 board with respect to the type of connection, some restrictions exist because of
the fourth VT.
C264/EN UM/E50.5 319

Measure Type of Connection: Direct or Indirect

3Vpn 3Vpn+Vo 2Vpn+Vo 2Vpp+Vo 3Vpp+Vo 3Vpn+VB 3Vpp+VB
UA direct Direct Direct indirect indirect direct not
UB direct Direct Direct indirect indirect direct not
UC direct Direct indirect indirect indirect direct not
UAB indirect Indirect indirect direct direct Indirect Direct
UBC indirect Indirect indirect direct Direct Indirect Direct
UCA indirect Indirect indirect indirect Direct Indirect Direct
UO indirect Direct Direct Direct Direct Indirect not
UBusbar not Not Not not not Direct Direct
Excepted
Protection all All all all all all 59N
dir 67N
Internal SC not Not not not not yes yes
In event of loss of (3vnb+Vb) or (3Vpp+Vb), then the tracking frequency defaults to the UBusbar.
The TMU210 type-of-connection parameters do not have as many possibilities as the TMU220
electrical-network-topology parameters. To be compatible, it is helpful to map the TMU210 type-
of-connection parameters into the TMU220 electrical-network topology parameters at SCE level:
TMU220
TMU210
Electrical-network-
Type-of-connection
topology
Parameters
parameters
3Vpn 3Vpn ( star )

3Vpn + Vo 3Vpn + Vo ( star )
2Vpn + Vo 2Vpn +Vo ( partial star )
2Vpp+ Vo 2Vpp + Vo ( delta partial )
3Vpp + Vo 3Vpp + Vo ( delta )
3Vpn + Vb 3Vpn + Vb ( star )
3Vpp + Vb 3Vpp + Vb ( delta )
320 C264/EN UM/E50.5

NOTE: Make sure that the VT wiring scheme is identical between line and busbar: delta:delta or
star:star. In a delta:star wiring scheme, there is no parameter to take into account the phase
difference and amplitude difference.
4.6.2.7.24 Phase-to-Phase Synchrocheck with the TMU210 - Description

Phase-to-phase synchrocheck allows you to configure a synchrocheck function with a delta
wiring. Do this configuration at the TMU210 level and use the attributes "type of connection" and
"reference phase".
For the phase-to-phase synchrocheck, set the “Type of connection” to 3 Vpp + Vb (delta).
Compare the busbar voltage to the phase-phase voltage defined as the reference in the
configuration. The reference phase-phase that you choose must match the phase-phase of the
busbar that is wired on the TMU210.
For example: If the reference phase-phase is configured as Vab then the phase-phase voltage
Vab busbar must be wired on TMU210.
NOTE: There is no check possible at the MiCOM C264 or SCE level. The operator is responsible
to make sure that the configuration agrees with the wiring.
In this configuration, the calculation of voltage, angle and frequency are the same as for phase
neutral.
Phase-to-Neutral synchro-check (SC PN) and Phase-to-phase synchrocheck (SC PP)

configurations show in the table that follows.
SC PN SC PP
Mounting
Star Delta
(wiring)
Type of
3Vpn + Vb (star) 3Vpp + Vb (delta)
connection
Reference Va, Vb, Vc of line or Vab, Vbc, Vca of
phase busbar line or busbar
When wiring is between Phase and Neutral, Vb is “Vbpn”.
When wiring is between Phases, Vb is “Vbpp”.
4.6.2.7.25 Phase-to-Phase Synchrocheck with the TMU210 - Configuration

For the Phase to phase synchro-check:
Only Vab, Vbc, Vca are available as “Reference phase”.
For the Phase to Neutral synchro-check:
Only Phase A, Phase B, Phase C are available as “Reference phase”.
4.6.2.7.26 Synchrocheck Close request

On close request, the schemes are tested. Depending on the test result a positive acknowledge to
the order is sent if close is possible, else a negative one.
When the LL scheme is valid and to allow the breaker to close, a check of the synchronization
conditions between the 2 voltages is performed.
C264/EN UM/E50.5 321

The locking mode is the default synchronizing mode. If the requirements are valid, at least during
a delay T1, the closure is made immediately. Otherwise the coupling mode is tried. The different
coupling modes are defined in agreement with the type of synchrocheck.
Define the authorized schemes that follow during the configuration phase. The synchrocheck
function operates for these schemes:
Operator
Operator manual
Synchrocheck Auto-recloser
closure
closure
Network locking on both voltages
presence and test of deltas
X X X
Automatic and manual network
locking on live line / live bar
Network coupling on both voltages
presence and test of deltas
X
Automatic and manual network
coupling on live line / live bar
Presence of only the line voltage
Automatic and manual network X X X

connection on live line / dead bar
Presence of only the busbar voltage

connection on dead line / live bar
Absence of both voltages

connection on dead line / dead bar
4.6.2.7.27 Synchrocheck General Configuration

The general configuration includes:
• Network frequency,
• VT connection: delta or star,
• Reference phase: A, B or C,
• Reference phase side: line or busbar,
• Nominal voltage.
4.6.2.7.28 Synchrocheck Voltage control

This function computes the BI’s presence/absence voltage of the line and the busbar.
In agreement with the configuration:

• The line can be the reference or the other voltage,
• The busbar can be the reference or the other voltage.
Four thresholds are defined:
322 C264/EN UM/E50.5

• Line voltage over: percent of the nominal voltage,
• Line voltage under: percent of the nominal voltage,
• Bus bar voltage over: percent of the nominal voltage,
• Bus bar voltage under: percent of the nominal voltage.
Two timers are defined:

• Absence delta test time (T3) to confirm the absence signals,
• Presence test time (T2) to confirm the presence signals.
4.6.2.7.29 Synchrocheck Schemes control

By configuration, each event that follows is allowed or not:
LL-
LL- locking DL LD DD
coupling
Close with synchro YES or NO YES or NO YES or NO YES or NO YES or NO
NOT
Manual Close YES or NO YES or NO YES or NO YES or NO
POSSIBLE
Automatic Close
NOT
request from auto- YES or NO YES or NO YES or NO YES or NO
POSSIBLE
recloser
In event of manual override, the close request is allowed and there is no check.
When coupling is configured, locking is mandatory.
In coupling conditions, a manual or automatic close is always refused: LL and locking conditions
not met.
4.6.2.7.30 Synchrocheck Parameters of the TMU2xx board

The parameters for the TMU220 are the same as for the TMU210:
• Reference phase: definition of the voltage reference phase for comparison,
• Reference phase side: definition of the energized reference voltage.
4.6.2.7.31 Synchrocheck Internal parameters
Parameter Label Range of value Type

General
Synchrocheck
SC type 1 or 2 1 and 2
kind
Voltage control
Delay of one
voltage From 200ms to 10s,
T2 1 and 2
presence 20ms step
control
C264/EN UM/E50.5 323


Delay of voltage From 200ms to 10s,
T3 1 and 2
absence control 20ms step
0 to 100%, 1% step (%
Line voltage
V> line of the nominal voltage 1 and 2
over threshold
value)
0 to 100%, 1% step (% 1 and defined by the
Line voltage
V< line of the nominal voltage fixed dropout percent for
under threshold
value) type 2
0 to 100%, 1% step (%
Busbar voltage
V> busbar of the nominal voltage 1 and 2
over threshold
value)
0 to 100%, 1% step (% 1 and defined by the
Busbar voltage
V< busbar of the nominal voltage fixed dropout percent for
under threshold
value) type 2
Locking
scheme
Delay of both
voltages 200ms to 10s, 20ms
T1 1 and 2
presence step
control
0 to 100%, 1% step (%
Voltage delta
Evect_locking of the nominal voltage 1 and 2
threshold
value)
Minimum 45 to 59,5 Hz, 0,1 Hz
Fmin_locking 1
frequency step
Maximum 50,5 to 66 Hz, 0,1 Hz
Fmax_locking 1
frequency step
Frequency delta
Efreq_locking 0 to 1 Hz, 0,01 Hz step 1
threshold
Phase delta
Ephase 0 to 90°, 1° step 1 and 2
threshold
Shift frequency
Sfreq_locking 0.02¸0.1 % step 0,01 % 2
threshold
Coupling
scheme
Delay of both
voltages T1 (for locking and 200ms to 10s, 20ms
1 and 2
presence coupling) step
control
324 C264/EN UM/E50.5


Circuit breaker
response time 1 and 2
Ta 0 to 1s, 10ms step
for coupling
scheme
0 to 100%, 1% step (%
Voltage delta
Evect_coupling of the nominal voltage 1 and 2
threshold
value)
Minimum 45 to 59,5 Hz, 0,1 Hz
Fmin_coupling 1
frequency step
Maximum 50,5 to 66 Hz, 0,1 Hz
Fmax_coupling 1
frequency step
Frequency delta
Efreq_coupling 0 to 1 Hz, 0,01 Hz step 1
threshold
Phase delta
Ephase 0 to 90°, 1° step 1
threshold
Shift frequency
Sfreq_coupling 0.1¸1 % step 0,1% 2
threshold
= Ks (Tk-Ta) where
Acceleration Ks = 1% fixed Not required to define
Shift frequency accSfreq_coupling
Tk = 0.5s this threshold
threshold
Ta: see above
The fixed hysteresis values follow:

• 5% on voltages thresholds,
• 2% on voltage delta threshold for locking and coupling,
• 0,014 Hz on frequency delta threshold for locking,
• 0,028 Hz on frequency delta threshold for coupling,
• 0,01 Hz on frequencies thresholds,
• 1° on phase delta threshold for locking.
4.6.2.7.32 Synchrocheck Digital Output (DO) of the circuit breaker

The DPC of the circuit breaker can be configured on the DSPIO or on a DOU board.
On DSPIO, the DPC close relay is mandatory connected to the contact 1 or contact 2 of relay 3
(pinout 9/10 or 11/12).
In this event there are only 2 choices for the DPC type:
• Transient,
• Permanent until feedback.
If you use a DOU, both contacts must be connected on it with same previous constraint.
C264/EN UM/E50.5 325

4.6.2.7.33 Voltage reference selection and Double busbar configuration

If a TMU220 board is used for measurements, the Synchrocheck allows us to configure two
different busbars. Thus, instead of comparing the Line and the BusBar in order to control a circuit
breaker, it is possible to take into account the combination the two busbars and the Line as shown
in the following table. Other combinations are not allowed.
Reference Compared
Voltage Voltage
Line Busbar1
Line Busbar2
Busbar1 Busbar2
Busbar2 Busbar1
4.6.2.8 Fast Load Shedding ( FLS )

The Fast Load Shedding (FLS) automation function description and implementation is part of the
Application Chapter (AP). For more data, please refer to C264_EN_AP.
4.6.2.9 Synchroscope and Power Synchronizer

4.6.2.9.1 General
In a power system, synchronization is the process of connecting two sources (single generator or
running network) by eliminating the risk of damage for the devices composing each side. For this,
it is necessary to match the frequency, the voltage level between each source and the phase
angle of the two voltages. An AC generator cannot deliver power to an electrical grid unless it is
synchronized to it.
There are some conditions that must be met before the synchronization process takes place. The
source (generator or sub-network) and the running network must have equal voltage, frequency
and phase angle. In other words,
1. |ΔF| < ΔFmax,
2. |ΔV| < ΔVmax
3. |Δφ| < Δφmax
A power synchronizer is a device monitoring and controlling the parts to be synchronized in order
to make them meet the required conditions with the purpose of connecting them.
The following figure schematizes how the power synchronizer interacts with the monitored and
controlled elements to be connected.
326 C264/EN UM/E50.5

- Figure 75 - Power synchronizer interacting with the network
The power synchronizer concerns three different but correlated processes :

• Monitoring
• Convergence control
• Closing control
4.6.2.9.1.1 Monitoring
The Power Synchronizer monitors two islands (usually designated by Line and Bar) to be
interconnected. It displays the values measured on both sides of the CB: VL, VB, FL and FB
(Voltage and Frequency on Line and on Bar sides). It also displays the differences (Deltas)
between measured Frequency, Voltage and Phase angle, respectively ∆F, ∆V and ∆φ.
4.6.2.9.1.2 Convergence
The power synchronizer also provides the mechanisms necessary to control one or both islands
in order to modify their provided phase angle, frequency or voltage so the connection between
them can be performed with no damage to their primary devices. This process is also known as
Convergence.
The Convergence process can be executed in Manual or in Automatic mode. In Manual mode, the
operator selects one of the CB’s side to control, then manually modifies the frequency and voltage
level by sending +/-F and/or +/-V controls in order to meet the synchronization conditions. In
Automatic mode, the Power Synchronizer sends the control signals. This automatic convergence
process is performed through a built-in automation.
C264/EN UM/E50.5 327

4.6.2.9.1.3 Closing
The power synchronizer provides the necessary mechanisms controlling the CB interconnecting
the involved islands (Closing process). The Closure process can be executed in two different
manners: Manual or Automatic. In Manual mode, the operator decides at which moment to close
the CB (Synchrocheck with Locking scheme); while in Automatic mode, this is the Power
Synchronizer itself who closes the CB when the synchronization conditions are met
(Synchrocheck with Synchro-coupling scheme). This automatic closing signal is sent through a
built-in automation.
In the
Locking
process,
the closing
conditions
are fixed:
1. ΔV <
ΔVmax
2. ΔF ≈ 0 (<
εFmax)
It means
that ΔφV
constant
3. ΔφV <
Δφmax
If conditions
1, 2 and 3
are true,
check is OK
and close
control will
be
accepted.
- Figure 76 - Fresnel Locking
328 C264/EN UM/E50.5

- Figure 77 - Locking: Constant phase and frequency delta over time
Closing
conditions
are fixed:
If εF < │ΔF│
< ΔFmax
and
│ΔV│ <
ΔVmax
then it waits
until ΔφV =
0 for closing
the CB
- Figure 78 - Fresnel Coupling
NOTE: In coupling mode, delta phi should not be ‘negative’ : you simply have to wait a bit more
time before requesting the closure. Then if the frequency is rising, indeed you take into account
this delta phi after the theorical 0° to see if you decide to close or not the circuit breaker.
- Figure 79 - Coupling: Frequency shift over time
C264/EN UM/E50.5 329

These different execution modes (Automatic or Manual) of the precedent processes lead to the
following combinations selectable by the operator.
Type HMI Description

1 OFF Monitoring only
2 ALL MANUAL All manual
Automatic
AUTCNVR &
3 Convergence and
MANCLS
Manual Closing
Manual Convergence
MANCNVR &
4 and Automatic
AUTCLOSE
Closing
5 ALL AUTOMATIC All Automatic
4.6.2.9.1.4 Connection schema
The following figure schematizes the power synchronizer’s internal components and their
connections to the CB and the elements to be synchronized.
- Figure 80 - Power synchronizer’s Connection schema
4.6.2.9.2 HMI
4.6.2.9.2.1 MiCOM C264’s Screens
The following figure shows the Power Synchronizer’s HMI on the MiCOM C264.
330 C264/EN UM/E50.5

The mode selection panel is shown in the left while the Synchroscope feature is shown in the
right.
- Figure 81 - Mode Selection and synchroscope panels
The following two figures describe the distribution of the information displayed in the
synchroscope panel shown in the previous figure
C264/EN UM/E50.5 331

- Figure 82 - General data displayed for the Power Synchronizer feature (1/2)
- Figure 83 - General data displayed for the Power Synchronizer feature (2/2)
4.6.2.9.2.2 Navigation in MiCOM C264
After selecting a CB linked to a Synchroscope built-in function, the control mode selection panel is
displayed when the user presses the right arrow button. From this panel, the operator can access
the synchroscope under different modes. Depending on the selected Control Mode, the operator
will be allowed to send control signals (+/- F or V) to the selected side (Line or Busbar) and to
close the Circuit Breaker.
332 C264/EN UM/E50.5

Panel Button Action Constraint

C Go back graphical bay panel
Control Mode
Up Select previous mode Up
Selection
Down Select next mode Down
Panel
Enter Go to selected mode Enter
Go back to control mode
C Always allowed
selection panel
L/R Control the Local/Remote mode L/R
Select next selectable side to Only allowed for any mode
Select
control (if any) different than OFF
Allowed only for one the Manual
Perform +F command on Convergence modes and only if
Up
selected side a “side to control” (Line or Bar) is
Synchroscope
selected
panel
Perform -F command on
Down Down
selected side
Perform -V command on
Left Left
selected side
Perform +V command on
Right Right
selected side
Perform a Sync Cb Close on the Allowed only for one the Manual
Close
CB Closing modes
4.6.2.9.3 Main MiCOM C264’s behavior

The Synchroscope view is only accessible for an Engineer Profile.
When entering to the Synchroscope panel no “side to control” is selected by default.
A side (Line or Bar) is considered as controllable if at least one control command is defined on it
within the configuration.
When the operator manually sends a control (+-F/ +-V) through the panel, the executed control
will be indicated to the operator by temporarily reversing the display corresponding to the control
sent. For example, if the operator sends a +F control to the Line side, then the Frequency
measurements for the Line side will be temporarily displayed in reverse mode. Similarly, when the
Operator manually closes the CB, the CB’s state label will be displayed in reverse mode until the
end of the command.
The control (+-F/ +-V) sent by the operator through the panel will be ignored in any of the two
modes concerning the Automatic Convergence.
When running in Automatic Closing mode, any close CB command from the operator will be
ignored.
During the execution of a Manual Closing command, the Power Synchronizer will ignore any other
command sent by the operator; i.e. no other action from the user can be executed until the
conclusion (successful or not) of the Manual Close command.
C264/EN UM/E50.5 333

When leaving the synchroscope panel, the synchronizer process is set to off; i.e. any automatic
process is stopped.
If the Synchroscope is launched for a closed CB, then the control commands (Open, Close, +-F/
+-V) will be ignored.
4.6.2.9.4 Error management in MiCOM C264

Whenever a measurement is invalid, the Synchroscope is stopped. Moreover, the label “Invalid”
will be displayed in the corresponding measurement place.
The convergence automation and the Synchrocheck mode.are reset when the synchroscope is
closed.
4.6.2.9.5 Performances
The Synchroscope displays measurements changes at a frequency of 100ms.
4.6.2.10 MiCOM C264 in eLSU application

4.6.2.10.1 Purpose
Intelligent Fast Load Shedding:
The iFLS know the substation topology and has predefined actions to execute depending on
monitoring control system substation topology.
Enhanced Load Shedding Unit:
The MiCOM C264 eLSU is used in context of iFLS. MiCOM C264 eLSU is a standard
MiCOM C264 with specific configuration and limitation. The MiCOM C264 eLSU is used in context
of iFLS.
MiCOM C264 eLSU manages 2 trip signals for each feeder. Those trip signals are received within
a GOOSE message. Those trip signals are called TRIP_M and TRIP_B.
- Figure 84 - IFLS topology
334 C264/EN UM/E50.5

4.6.2.10.2 MiCOM C264 eLSU configuration

MiCOM C264 eLSU is configured at SCE level. On Electrical view, at Generic bay level, “Shed
Automation” and “Shed Reflex” are available:
- Figure 85 - SCE configuration
It is possible to have at most one “Shed automation” function, and several “Shed Reflex” function.
4.6.2.10.2.1 Shed Reflex
- Figure 86 - Shed reflex
- Figure 87 - Shed reflex electrical view
Mirror SPS follow the state of DO which have been triggered by a shed order.
“acts on” is mandatory relation to a given Digital Output of DOU or CCU board. This digital output
corresponds to the shed DO.
“has for main trip given by” is a mandatory relation to a given SPS Datapoint called “TRIP_M”.
C264/EN UM/E50.5 335

“has for backup trip given by” is an optional relation to a given SPS Datapoint called “TRIP_B”
A shed reflex can be set as:

• Permanent, its state follows the state of the command,
• Transient, it will stay activated for a set duration
“order on duration (ms)” (range: [0..15000], step: 10, default value: 500)
- Figure 88 - Shed reflex ACtivation mode attribute
- Figure 89 - chronogram of do associated to shed
4.6.2.10.3 Shed automation
- Figure 90 - Shed automation
The “Shed Automation” object has object entries which are the inputs of the control type. Those
entries are the following SPS:
• Delta B Inval M
• Delta M Inval B
336 C264/EN UM/E50.5

• Enable Trip B
• Enable Trip M
• No Delta
The “Shed Automation” object has an attribute to “Control Type”. The “Control Type” define the
FBD equation used by the MiCOM C264. The “Control Type” can be either:
• Pre-defined
• Free designed
• No check
- Figure 91 - Shed automation control type attribute
4.6.2.10.3.1 Control Type of Shed Automation
CAUTION
UNEXPECTED EXECUTION OF CONTROL
• Carefully evaluate the impact of PLC automation before usage.
• Control executed without any checks (L/R, interlock,...)
• The eLSU Shed Reflex control shall be used only in case of DO (Direct Order)
Pre-defined
• Input:
A: DELTA_B_INVAL_M
B: TRIP_B
C: TRIP_M
D: DELTA_M_INVAL_B
E: NO_DELTA
• Output:
TRIP
Associated literal equation:
TRIP=A⋅ B+C⋅ D+(E⋅ (B+C)) = A⋅ B+C⋅ D+E⋅ B+E⋅ C
C264/EN UM/E50.5 337

Associated graphical equation:
- Figure 92 - Pre-defined equation
Free designed
• Input:
A: TRIP_M
B: enable_trip_M
C: TRIP_B
D: enable_trip_B
• Output:
TRIP
TRIP= A.B+C.D
- Figure 93 - Free designed equation
No check
338 C264/EN UM/E50.5

• Input:
A: TRIP_M
B: TRIP_B
• Output:
TRIP
TRIP= A+B
- Figure 94 - No check equation
4.6.2.10.3.2 MiCOM C264 specific configuration for MiCOM C264 eLSU
To use MiCOM C264 in eLSU mode. the following functionalities are not authorized:
• master legacy communications
• slave scada communication
• slow automation managed by ISaGRAF®
• IEC 61850 client for report
• built-in Synchro-check
• built-in AVR
• built-in Auto-recloser
• built-in ATCC
eLSU is able to manage 120 sheddable feeders. If multirack is configured, each MiCOM C264
eLSU extension rack can also manage 120 sheddable feeders.
There can be up to 120 load shedding DOs, i.e. one DO per sheddable feeder.
Redundancy
MiCOM C264 eLSU manages redundancy based on existing redundancy for standard
MiCOM C264 without any impact on eLSU process time. Only the MiCOM C264 master sheds
(current behavior of redundant MiCOM C264, using RedSt). Redundancy shall be applicable for
main MiCOM C264 and secondary in multirack.
Maintenance mode
In maintenance mode, MiCOM C264 eLSU feature is disabled.
C264/EN UM/E50.5 339

4.6.3 Fast automation: Programmable Scheme Logic (PSL)

Programmable Scheme Logic (PSL) via FBD editor, is the solution for implementation of
automatism that has to be performed as quickly as possible. The designed solution is mainly
based on the mechanism used for the computation of logical interlocking (see following chapter).
Logical gates AND, OR, NOT, NAND, NOR or a combination of these gates can be processed as
a logical equation. Some other functions (drop-off & pickup timer, bistables) are added to these
logic gates.
4.6.3.1 Interlocking equations as particular case of PSL

4.6.3.1.1 Introduction
The operating of a switching device is directly related on its nature and its environment. It can be
operated only with respect of certain conditions. These conditions, therefore called interlocking.
Interlocking prohibits an operation that would be ordered by error, in remote control, to a switching
device beyond its standard conditions of operation. They are managed in the form of logical
equations within the computer.
Result of the interlocking equation is transmitted through a system binary output (SPS datapoint)
and saved, locally in RAM, by the function managing interlocking logical equations.
Up to two interlocking equations can be defined for SPC / DPC datapoint, one for each available
order (open or close).
On reception of open or close request, if the logical equation related to with the switching device
exists, the “control of sequence” function used the service offered by the interlocking function to
get the result of the interlocking associated to the received request. If the result of the interlocking
is TRUE, the check is considered as achieved, otherwise the request have to be refused and a
negative acknowledgment sent to the origin of the request.
Interlocking equation is composed of Boolean information mainly representing the position of

other switching devices.
The interlocking for a switching device may be composed of substation interlocking equations and
local interlocking equations.
Both interlocking equations are managed by the computer that controls the switching device.
The local equation is made up of information obtained from its own digital inputs and IEDs
connected to this computer.
Substation interlocking is made up of information obtained from its digital inputs and inputs
provided by the communication network from other computers, from bay computers and from
IED’s (protection relays, etc.).
Interlocking equation is a case of PSL, limited to one output and logical function usage.
4.6.3.1.2 Interlocking bypass

Bypass made by key switch
Interlocking can be overridden (interlocking bypass mode). Overriding of interlocking can be set
from the local control point if it exists.
340 C264/EN UM/E50.5

During configuration optional overriding of interlocking from any other control point can be defined
according to customer requirements. This includes the possibility of overriding of interlocking per
switching device or per bay or per substation entity basis.
If an interlocking is overridden, the associated variable is true.
Bypass within the control
From any control point, operator can bypass the interlocking check. Bypass is then an attribute of
the control. If bypass is set, the function managing the “control of sequence” does not use the
service giving the current result of the interlocking equations.
4.6.3.1.3 Timer before interlock evaluation

During a control sequence, this function allows a delay before the interlock check. For each
device, one time-out attribute is available for each interlock: one time-out attribute for the Open
interlock and one time-out attribute for the Close interlock. By default, the value of this time-out
attribute is 0, meaning no timeout.
This timer shall be in the range of [0;10] seconds with a step of 1s. The timer shall be launched
only if the interlock is FALSE. If the interlock becomes TRUE while the timer operates, the control
sequence waits for the end of the timer before it validates the interlock. The timer applies to these
controls: Select Before Operate and Direct Execute.
4.6.3.1.4 Simulation and test of interlocking equations

In order to ease up the check of interlocking equations, a “SIMULATION mode“ is implemented in
the computer. In this operating mode, a valid control is sent to the output, but closing the contact is
not performed and a positive acknowledgement message is generated.
4.6.3.2 PSL/interlocking inputs

Any kind of input datapoint (xPS, MV, and TPI) can be used as input of PSL/interlocking. By
configuration are defined the logical states of the input datapoints, status value by status value, in
the following set: True, False, Invalid.
SPC/DPC can be used as input of PSL excepted interlock, to intercept a specific order on them.
By configuration are defined the “logical states” of SPC / DPC, order value by order value, in the
following set: True, False, Invalid.
4.6.3.3 PSL interlocking outputs

PSL can provide several SPS datapoint outputs. SPC/DPC can also be used as output of PSL
excepted interlock to launch a specific order on them, where the logical state True (respectively
False) is relevant to close (respectively Open) order.
Interlock equation provides only one output that is a SPS datapoint.
4.6.3.4 Functions
The following functions are available in PSL automation with restriction given for interlock.
Function Interlocking PSL

AND /
X X
NAND
C264/EN UM/E50.5 341

Function Interlocking PSL

OR /
NOR / X X
XOR
NOT X X
Flip Flop Not available X
Timers Not available X
4.6.3.5 Validity of data

PSL and Interlocking equation do not only use the value of their inputs but also their validity. The
evaluation of the result of basic logical function such as NOT, AND or OR is defined as follows:
NOT
True False
X False True
Invalid Invalid
Y
X OR Y
True False Invalid
True True True True
X False True False Invalid
Invalid True Invalid Invalid
Y
X AND Y
True False Invalid
True True False Invalid
X False False False False
Invalid Invalid False Invalid
An Interlocking equation in the INVALID state will be considered as FALSE for control sequence
checks. The SPS resulting of an interlocking equation is saved in RAM.
4.6.3.6 Computation
PSL and interlocking equations are computed each time that one of theirs input changes of state
or of validity, there is no associated cycle time.
4.6.4 Slow automation Programmable Logic Control (PLC)

During the substation configuration phase, MiCOM C264 allows you to configure the specific
control sequences or automations: for example, the switching sequences, busbar transfer, load
shedding, and GIS-pressure supervision.
342 C264/EN UM/E50.5

You create the Programmable Logic Controls (PLC) or Configurable Automations and build them
in the logic development ISaGRAF® workbench. The real time kernel of the computer operates
them.
ISaGRAF® workbench is a host-based software development environment integrated in the SCE.

ISaGRAF® workbench includes a set of tools that allow you to:
• Edit
• Generate code
• Simulate
• Debug via connecting a PC to the Ethernet port of MiCOM C264 and using the ISaGRAF®
workbench
The software logic package supports standard programming languages of the IEC 61131-3:
• Sequential Function Chart, SFC (GRAFCET)
For action and transition description, you can use this language with Function Block Diagram
(FBD), Ladder Diagram (LD) or Instruction List (IL).
• Structured Text, ST
The logic development workbench generates code. The code is uploaded to the computer target
system that operates the code.
- Figure 95 - PLC workbench
For more information relevant to ISaGRAF® workbench integration and usage in EPAS, refer to
the chapter SCE/EN AP.
4.6.4.1 Inputs
Any kind of input datapoints of the MiCOM C264 can be used as an input of a PLC:
• Value and quality of xPS
• Value and quality of MV/TPI
Any kind of output datapoint (xPC, setpoint) can be used as an input of a PLC. In that case, the
PLC can solicit an order on such datapoint through specific control function inside ISaGRAF®.
4.6.4.2 Outputs
Any kind of input datapoints can be produced by a PLC:
C264/EN UM/E50.5 343

• Value and quality of xPS
• Value and quality of MV/TPI
Any kind of output datapoint (xPC, setpoint) can be managed by a PLC. In that case, the PLC
manages all the control sequence and acknowledgment on such datapoint, by waiting for a
specific order request.
A PLC function can produce:

• Send binary order to computer boards or IED or to another computer
Send digital and analogue setpoints to computer boards or IED or to another computer.
4.6.4.3 PLC Behaviour

The communication between MiCOM C264 application and the ISaGRAF® application is done
through two mechanisms
• A Dictionary module: contain the current value for all Data Point (DP) used by ISaGRAF®
Automation.
• Hook functions: functions used to quickly interact with the electric process. These functions
are declared in the ISaGRAF® workbench and implemented in C by the BCPU. Update the
EPAS hook function list with this function to retrieve the current date and time.
The computer has a software execution engine that interprets the automation application code as
shown in the cycle that follows:
344 C264/EN UM/E50.5

The cycle duration depends on the number of I/O to be scanned and the complexity of the
operations to be performed. Set the cycle during the configuration process.
4.6.5 PSL/PLC behavior in case of MiCOM C264 redundancy

On the active MiCOM C264, when an PSL or PLC output is updated, it is recorded in FLASH (if
so-configured) and in SRAM. Then it is sent to the MiCOM C264 Standby.
On the standby MiCOM C264, the value of the output of PSL is received by and recorded in
FLASH (if so-configured) and in SRAM.
On the standby MiCOM C264, the PSL computation being stopped, the outputs of the PSL are
valued when switching from standby to active from SRAM and FLASH, then remain at unknown.
On the standby MiCOM C264, the PLC computation being stopped, the outputs of the PLC are
valued when switching from standby to active from SRAM and FLASH, without being set to
unknown.
The new active MiCOM C264 therefore inherits the states of the PSL/PLC present on the previous
active MiCOM C264 when the redundancy mode is changed.
C264/EN UM/E50.5 345

4.7 Records
4.7.1 Permanent records storage
4.7.1.1 Data storage
All parameters or settings that can be modified via front face LCD are stored in flash disk.
Lists of system information are also stored in the flash disk.
4.7.1.2 Waveform Recording: General

A waveform recording deals with the storage of measurement and logical information in order to
visualize the electrical network behavior when electrical events appear, such as the start of the
generator. These types of events are called “trigger of waveform recording”.
In order to see the influence of a trigger, data are recorded before (pre trigger time) and after (post
trigger time) the raise of the trigger.
Two types of waveform recording can be performed in the computer:

• Fast Waveform recording that gives access to samples. This record is useful for transient
electrical events.
• Slow scan triggered recording (SST) referred to as Slow Waveform recording that gives
access to RMS values. This record is useful to define load profile or power regulation.
4.7.1.3 Events
All data changed or events declared in the MiCOM C264 configuration database “To be logged”
are stored in a circular queue.
The event records are available for viewing either via the front panel LCD, via slave protocol at
SCADA level or on CAT equipment. They also can be printed.
Events, following the MiCOM C264 configuration, may typically contain the MiCOM C264
description, the date of the event and the time of the event with an accuracy of 1 ms, plus specific
information regarding the causes of the events.
The MiCOM C264 under the following circumstances may create events:
• Changes of state of SPS/DPS/MPS,
• Changes of state of MV and TPI,
• Devices Control actions and acknowledgments,
• Alarm acknowledgment.
The size of the queue is:

• 200 events for front panel,
• 2000 events for CAT,
• configurable for each slave protocol for SCADA.
4.7.1.4 Fast Waveform Recording

For the TMU2XX Boards, the inputs for the fast waveform records follow:
346 C264/EN UM/E50.5

INPUTS
CT: VT: Digital Analogue
TMU
as many as many DSP DSPIO Inputs and Inputs and
BOARD
as as Outputs Outputs
TMU210 4 4 NO DSPIO YES YES
TMU220 4 5 DSP NO NO YES
You can capture as many as 128 digital channels. The choice of selected inputs/outputs is
defined in configuration.
The waveform recorder provides as many as 8 analogue measurements and as many as 128
digital channels for extraction by a remote device.
A maximum of 480 cycles (9,6 seconds at 50 Hz) of measurements samples, with 32 samples per
cycle, can be stored, divided in 1, 2, 4 or 8 files saved in flash disk.
A timer channel is also required to provide accurate timing information for each sample. The delay
between each sample is assumed constant over a single cycle.
Number of Number of
Files cycles
8 60
4 120
2 240
1 480
The waveform recorder can be triggered by the following events, each of which is user
configurable:
• Changes in state of SPS/DPS/MPS Fast Waveform Recorder is triggered by the valid change
in state of events (like SPS ->SET /RESET, DPS -> OPEN >CLOSE). It changes the only with
VALID quality (ex SET/RESET; OPEN/CLOSE) to a state/value with VALID Quality
• Changes in state of digital outputs,
• Measurement threshold violations,
• Operator request.
Only one re-trig is allowed: it means that a new trigger can only be accepted after the end of
recording of the current waveform.
Waveform records are available in COMTRADE 2001 format.
NOTE: The triggering is available only from a state/value with VALID quality (ex: SET/REST;
OPEN/CLOSE) to a state/value with VALID quality.
4.7.1.5 Slow Waveform Recording

The inputs for the slow waveform records are:
C264/EN UM/E50.5 347

• MV coming from CT VT calculation (RMS values),
• MV coming from AIU boards,
• SPS/DPS/MPS,
• SPC/DPC (order values).
The slow waveform manages as many as 24 analogue and 48 digital values.
The MiCOM C264 stores at maximum 5000 integrated values as follows:
Number of
Number of
integrated
Files
values
1 5000
2 2500
5 1000
10 500
20 250
50 100
The integrated value has a duration up to one hour. It is defined in configuration.
For analogue, the stored value is the average value during integrated period.
For digital, the stored value depends also on the average:
If average value > x then the stored value is 1 else it is 0, x is defined in configuration and it is a
value between 0.1 and 0.9 The slow waveform recorder can be triggered by the following events,
each of which is user configurable:
• Changes in state of binary inputs (SPS/DPS/MPS). Slow Waveform Recorder is triggered by
the valid change in state of events (like SPS ->SET/RESET, DPS -> OPEN >CLOSE). It
changes the only with VALID quality (ex SET/RESET; OPEN/CLOSE) to a state/value with
VALID Quality
• orders on SPC/DPC
• MV threshold violations
• Operator request
• Periodically: that is, every day at 00h00
NOTE: The triggering is available only from a state/value with VALID quality (ex: SET/REST;
OPEN/CLOSE) to a state/value with VALID quality.
4.7.1.6 Slow Waveform Recording – Hypothesis

The hypothesis for slow waveform recording follows:
1. Digital inputs will be not recorded if the integration delay is superior to 100 ms
2. A digital input is recorded to “1” if it remains at “1” during x% of the integration delay (x
between 10 and 90%, with a 1% step)
348 C264/EN UM/E50.5

3. The allowed cycle numbers are the following:
From 1 to 180 000 at 50 Hz.
From 1 to 216 000 at 60 Hz.
4. The measurements issued from analogue inputs boards are processed as follows:
If the integration period is less or equal to 1 second, the recorded value is the current
measurement value
Otherwise, the recorded value is equal to:
Record: recorded value
N: number of seconds in the integration period
TMi: measurement value at the “i” second of the integration period
4.7.1.7 Disturbance Recorder

The PPC sends a command, referred to as a trigger, to the DSP to start a disturbance recorder.
The DSP stores in a buffer 32 samples by period of the 8 analogue channels according to the
configuration:
• - pre-time
• - total time
PPC convert this buffer in fast wave form adding binary inputs/output defined in configuration.
The maximum length of a disturbance buffer from the DSP is: 2 * total time.
One record contains at least one trigger and maximum 2 trigger.
If a second trigger appears during the post time of the first trigger, only one record is generated.
C264/EN UM/E50.5 349

If a second trigger appears after the post time of the first trigger, a second record is generated.
If a third trigger appears, it is ignored if the previous buffer are not downloaded by the PPC.
4.7.2 Non-permanent data storage of alarm

4.7.2.1 Definitions
4.7.2.1.1 Definition of an alarm
An alarm is a visual (and optionally audible) annunciation of the appearance and/or
disappearance, within the controlled electrical process or within the system itself, of an event,
defined during the configuration phase as ”to be alarmed”.
These definitions, of what is to be alarmed and what it is not, are completely user relevant.
However the concept of alarms into EPAS has been introduced to inform the operators of
“abnormal” or “special” events or other miscellaneous events that you must absolutely not
overlook.
4.7.2.1.2 Types of alarmed data

These events can generate an alarm:
• Each Binary Input (SP, DP, MP, SI, IED input, Groups) state related to “the reason for
change” of these events
• Each Measurement state related to “the reason for change” of these events
350 C264/EN UM/E50.5

• Each TPI state or value related to “the reason for change” of these events
• Each metering state related to “the reason for change” of these events
.For example, the OPEN state of a circuit breaker can be un-alarmed if the change is due to a
control, and alarmed if the change is due to another reason.
An alarm can be related to a control acknowledgment. In this event, the alarm is considered as
“spurious”.
4.7.2.1.3 Alarm states definition

An alarm is generated by an event: for example, a particular datapoint in a state defined during
the configuration phase as “to be alarmed”.
While this event is still present: for example, the previous particular datapoint is still in the same
state, the alarm is “active”.
When this event disappears: for example, the previous particular datapoint is now in another not
alarmed state; the previous alarm is “inactive”.
An existing alarm (active or inactive), can be acknowledged by an operator from the FP.
An alarm can have the following states:

• Inactive: no transition, no event
• Active-acknowledged: the cause is still present, but the active state has been taken into
account by the operator
• Active-unacknowledged: the cause is still present, and the active state has not been taken
into account by the operator
• Inactive-unacknowledged: the cause has disappeared, but the inactive state has not been
taken into account by the operator (only available for events alarmed on appearance and
disappearance)
• Inactive-acknowledged: the cause has disappeared, and the inactive state has been taken
into account by the operator
• Inactive-active-unacknowledged: the cause has disappeared but the active state (previous
state) has not been taken into account by the operator
4.7.2.1.4 Parameters associated to an alarm

The following user-selectable parameters can be associated with each alarm definition. The
values are set during the configuration phase for each alarm:
• Immediate or deferred:
an “immediate” alarm is displayed as soon it has been detected.
a “deferred” alarm is displayed only after a user-selectable time delay following its
detection (the event associated with the alarm must remain present during the delay; if
not, the alarm will be not displayed) ; this delay is in the range of 1 to 120 seconds and
can be set to particular value for each “deffered” alarm.
• Gravity level: this level is defined for each alarm allowing a hierarchical classification to deal
with the urgency of the events; the gravity level value can be: 0, 1, 2, 3, 4 or 5, 5 being the
gravest and 0 meaning that there is no gravity level.
C264/EN UM/E50.5 351

• Alarm generated:
only when the associated event appears
OR
when the associated event appears AND when it disappears
In this event the “differed” parameter is taken into account only when event appears;
when event disappears the new state of the alarm is displayed immediately.
• Alarm clearing mode:
manual: the alarm is cleared only on an operator request; this clearing command is only
allowed on inactive-acknowledged alarms.
automatic: an alarm is automatically cleared when it reaches the appropriate state.
gravity basis
• Audible or not when detected.
4.7.2.2 Alarm processing

Only one alarm (the last one) associated with a state change of data is displayed. The previous
one (concerning the data) is replaced by the current one.
According to the previous example, only one of the three alarmed states can be displayed for the
switching device: for example, « JAMMED » or « TOGGLING » or « OPEN » state (the last one
that has appeared).
By configuration, one of the following behaviours is chosen:
- Figure 96 - event alarmed on appearance only
352 C264/EN UM/E50.5

- Figure 97 - event alarmed on appearance and disappearance
Transition events:
• AL+: alarmed event appearance
• AL-: alarmed event disappearance
• ACK: operator acknowledgment of the alarm
• CLEAR: operator clearing of the alarm
Event «alarmed event disappears (AL-)» means that the associated data is now in another state
that is not alarmed. The time stamp of the alarm is modified.
Transition conditions:
• (auto) means Automatic clearing
Transition description:
The transition from alarm state "0" to alarm state "1" is crossed when the alarmed event appears
(AL+).
The alarm state transitions "1 ® 1" and "2 ® 1" are crossed when the state of the data associated
with the alarm goes from a state that is flagged to be alarmed with any gravity level to another
state that is also flagged to be alarmed with any gravity level (AL+). In this event the active alarm
C264/EN UM/E50.5 353

stays active but the time tagging of the alarm is changed. The new alarm time stamp corresponds
to the last associated data state change. The alarm becomes unacknowledged if not already
unacknowledged.
The alarm state transitions "1 ® 2", "3 ® 4" and “5 ® 3” are crossed on operator acknowledge
action. The time stamp of the alarm is unchanged.
The alarm state transitions "1 ® 3" and “1 ® 5” are crossed when the alarmed event disappears
(AL-). The time stamp of the alarm is modified.
The alarm state transition "2 ® 4" is crossed when the event disappears (AL-) the alarm being
configured to be activated only "on appearance of the event". The time stamp of the alarm is
modified.
configured to be activated "on appearance and disappearance of the event". The time stamp of
the alarm is modified and the alarm will have to be acknowledged again.
The alarm state transitions "3 ® 1", "4 ® 1" and “5 ® 1” are crossed when the previous alarmed
event appears again or when another state that is also flagged to be alarmed with any gravity
level appears (AL+). The alarm becomes active-unacknowledged. The time stamp of the alarm is
modified.
configured to be activated only "on appearance of the event" and «to be cleared automatically».
The alarm is suppressed from the alarm list.
The alarm state transition "3 ® 0" is crossed on operator acknowledgment only if the alarm
associated with the event is configured as «to be cleared automatically». The alarm is suppressed
from the alarm list.
The alarm state transition "4 ® 0" is crossed on operator clearing action. The alarm is suppressed
from the alarm list.
4.7.2.2.1 Acknowledgment
Acknowledgment of an alarm can be done by two ways:
• On operator request: an operator can acknowledge an existing alarm from the front panel to
signify that it has been taken into account.
• Globally: at substation level it is possible to use an SPS (named Global alarm ack) specially
dedicated to a global acknowledgment of alarms: When this SPS is set to the SET state all
alarms present in the computer are acknowledged. As long as this SPS remains in the SET
state, any new alarm is inserted in the alarm list with the ACKLOWLEDGED status.
• In addition to the Global Alarm Acknowledgment SPS, a Local Alarm Acknowledgment SPS
can be defined on a per MiCOM C264 basis: that is, one for eachMiCOM C264.
This SPS can be wired or managed by an automation. When this SPS is configured in a
MiCOM C264, the “Global Alarm Acknowledgment” SPS is no more taken into account by this
MiCOM C264.
When this SPS is SET, all MiCOM C264 alarms are immediately acknowledged.
This SPS cannot be transmitted on the Station Bus network: that is, it remains local to the
MiCOM C264, so it cannot be associated to a remote – HMI or SCADA - control.
354 C264/EN UM/E50.5

4.7.2.2.2 Clearing
Whatever the clearing mode is, the clearing of an alarm is immediately taken into account and
cleared from the alarm list.
Automatic clearing
An alarm can be configured as “to be cleared automatically”. It means that when this alarm
reaches the appropriate state, it is cleared automatically without any operator action. The events
of “automatic clearing” are:
• the alarm is in the active-acknowledged state and the alarm disappears (for event alarmed on
appearance only)
• the alarm is in the inactive-active-unacknowledged state and the operator acknowledges it
(for event alarmed on appearance only)
• the alarm is in the inactive-unacknowledged state and the operator acknowledges it (for event
alarmed on appearance and disappearance)
This feature can be configured on a per alarm basis.
Operator request clearing
An alarm that is not configured as “to be cleared automatically” has to be cleared by an explicit
operator action (this action being only possible when it is in the “inactive-acknowledged” state).
Otherwise it remains present in the alarm list.
As for acknowledgment done by an operator, clearing of alarms by an operator can be configured

as to be printed or not printed.
A global clearing procedure, that allows you to clear all “inactive-acknowledged” alarms in a single
operation, will be provided.
Audible alarms
An audible alarm can be associated with the “unacknowledged” state of an alarm. This facility is
configurable on a per alarm basis.
If an alarm is configured “audible” then the sound appears when the alarm is displayed.
The audible alarm is stopped when all audible alarms are acknowledged.
C264/EN UM/E50.5 355

4.8 Protection Functions
4.8.1 Undervoltage (ANSI code 27)

4.8.1.1 Description of the protection
Undervoltage conditions may occur on a power system for a variety of reasons, for instance
Increased system loading or complete loss of bus-bar voltage.
The undervoltage function [27] is used to detect an increase of load. It uses definite delay time
undervoltage protection.
The undervoltage protection element has two programmable stages (V<, V<<) with delay timers:
tV<, tV<<.
The protection element includes two thresholds. The two thresholds provide both alarm and trip
stages, where required. Alternatively, different time settings are settable, depending upon the
severity of the current dip.
4.8.1.2 Characteristics of the protection
Setting Value
Thresholds
Nominal range 57-130 V
V< 2 to 130 V, step of 0.1
V<< 2 to 130 V, step of 0.1
Nominal range 220 - 480
V
V< 10 to 480 V, step of 0.1
V<< 10 to 480 V, step of 0.1
Time delay
1st stage Definite Time (DT)
2nd stage Definite Time (DT)
Definite time delay
tV< 0 to 600s, step of 0.01
tV<< 0 to 600s, step of 0.01
356 C264/EN UM/E50.5

4.8.2 Earth Wattmetric Protection (ANSI code 32N)

The directional earth fault protection provides three directional / non directional earth overcurrent
thresholds and two wattmetric and active earth fault current thresholds.
Protective relays offer the possibility to choose between a Wattmetric (Pe) protection and IeCos
(active component of the earth fault current) protection functionality mode.
The Pe> and Pe>> settings are calculated as:
Vres x Ires x Cos(f - fc) = 9 x Ve x Ie x Cos(f - fc)
Where:
• f = angle between the polarising voltage (Vres) and the residual current
• fc = relay characteristic angle (RCA/torque angle)
• Vres = residual voltage
• Ires = residual current
• Ve = zero sequence voltage
• Ie = zero sequence current
The measurement of the Pe depends on the voltage wiring of the relay.
The residual current Ires can either be acquired through measurement or calculation with the local
CT/VT board.
In case of 3Vpn wiring, the Ve will be equal to Ve= 1/3(Va+VB+VC). In the other insertions way
the applied voltage to the relay is directly used to calculate the Pe.
NOTE: In case of VI #4 is wiring, the Ue (zero sequence voltage) is acquired, else the voltage is
computed by equation Ue= 1/3(Va+VB+VC).
Setting Value
Residual current Fundamental only
Residual voltage Fundamental only
Thresholds for Minimum
operating Power
P e> 57 to 130V, 0.2W
Pe>> 220 to 480V, 40W
Thresholds for Maximum
operating Power
P e> 57 to 130V, 20W
Pe>> 220 to 480V, 3200W
Pe> time delays
C264/EN UM/E50.5 357

Setting Value
DMT 0 ms to 150 s ; step of 10 ms
IDMT curves
Short time inverse (Schneider Electric),
Standard Inverse (IEC),
IEC Very inverse (IEC),
Extremely inverse (IEC),
Long time inverse (Schneider Electric)
RI Electromechanical type
RECT Rectifier
Short time inverse (CO2),
Moderately inverse (ANSI),
IEEE / ANSI Inverse (CO8),
Very inverse (ANSI),
Extremely inverse (ANSI)
Time multiplier setting
(TMS)
For IDMT curve 0.025 to 1.5 s ; step of 0.025 s
For RI curve 0.1 to 10 s ; step of 0.005 s
Reset time delay
For DMT 0 to 10 s ; step of 0.01 s
For IDMT 0.025 to 1.5 ; step of 0.025
Pe>> time delays
For DMT 0 to 150 s ; step of 0.01 s
NOTE: When Pe> or Iecos> is associated to an IDMT curve, the maximum setting
recommended should be the maximum of the range divided by 20.
4.8.3 Undercurrent protection (ANSI code 37)

The undercurrent function [37] is used to detect a loss of load (for example the draining of a pump
or breakage of a conveyor belt). It uses definite delay time undercurrent protection.
The undercurrent protection relays consists of one threshold. The user can set the following
parameters:
• Undercurrent threshold I<
• Time delayed undercurrent threshold tl<
The threshold provides alarm and trip stage, where required. Alternatively, time setting is settable,
depending upon the severity of the current dip.
358 C264/EN UM/E50.5

Setting Value
Current Fundamental only
Phase current range I< 0.1 to 100% rated current, step of 1%
Time delay tl< 0 to 150%, step of 10 ms
Hysteresis 105%
4.8.4 Negative sequence OC protection (ANSI code 46)

When applying traditional phase overcurrent protection, the overcurrent elements must be set
higher than maximum load current, thereby limiting the sensitivity of the element. Most protection
techniques also use an earth fault element operating from residual current, which improves
sensitivity for earth faults. However, certain faults may arise which can remain undetected by
such techniques.
Any unbalanced fault condition will produce negative sequence current. Thus, a negative phase
sequence overcurrent element can detect both phase-to-phase and phase to earth faults.
The negative phase sequence overcurrent elements have a current pick up settings I2>, I2>>,
I2>>>, and are time delayed in operation by the adjustable timers tI2>, tI2>>, tI2>>>.
The protection element includes three thresholds. The first threshold can be set as DT or IDMT
trip delay time.
The curves are the same as for the [50/51], [50N/51N] protection.
The three thresholds provide both alarm and trip stages, where required. Alternatively, different
time settings are settable, depending upon the severity of the current dip
Setting Value
Hysteresis 95%
Thresholds
I2> 0.5 to 25 Ien, step of 0.01
I2>> 0.5 to 40 Ien, step of 0.01
I2>>> 0.5 to 40 Ien, step of 0.01
I2> time delay
IDMT curves
C264/EN UM/E50.5 359

Setting Value
RECT Rectifier
Time Multiplier Setting
0.025 to 1.5 s ; step of 0.025 s
(TMS)
Reset time delay
If IEEE / ANSI I2> Time
Inverse (CO8),
delay
For DMT 0.04 to 100 s ; step of 0.01 s
Reset Time Multiplier
Setting
RTMS 0.025 to 3.2, step of 0.025
If IEC I2>Time delay 0.04 to 100 s, step of 0.01 s
I2>> time delays
For DMT 0 to 150 s ; step of 10 ms
NOTE: When I2> is associated to IDMT curve the maximum setting recommended should be
2In.
4.8.5 Thermal overload protection (ANSI code 49)

Thermal overload protection can be applied to prevent damages to the electrical plant equipment
when operating at temperatures in excess.
Protective relays incorporate a current based thermal replica, using load current to reproduce the
heating and cooling of the equipment to be protected. The element thermal overload protection
(corresponding to 49 th overload in SCE configurator) can be set with both alarm and trip stages
(49 th alarm and 49 trip th over.).
360 C264/EN UM/E50.5

The time to trip varies depending on the load current carried before application of the overload,
i.e. whether the overload was applied from “hot” or “cold”.
Setting Value
Current RMS
Current threshold I θ > 0.1 to 3.2 x rated current, step of 0.01
Thermal state (alarm and
50 to 200% x θ, step of 1%
trip)
Constant time Te 1 to 200 mn, step of 1 mn
k factor 1 to 1.5, step of 0.01
4.8.6 Overvoltage (ANSI code 59)

The overvoltage protection function (ANSI code 59) is used to detect system voltage that are too
high or to check that there is sufficient voltage to authorize a source transfer.
The overvoltage function measures the fundamental frequency component of the line-to-line
voltages regardless of the voltage measurement mode. By using line-to-line voltage any phase-
to-ground over-voltages during earth/ground faults have no effect. Whenever any of these three
line-to-line voltages exceeds the start setting of a particular stage, this stage starts and a start
signal is issued. If the fault situation remains on longer than the operative time setting, a trip signal
is issued.
In solidly earthed/grounded, four-wire networks with loads between phase and neutral voltages,
overvoltage protection may be needed for phase-to-ground voltages as well. In such application,
the programmables stages can be used.
Setting Value
Thresholds (secondary
values)
V> 2 to 260 V, step of 0.1
V>> 2 to 260 V, step of 0.1
V
V> 10 to 960 V, step of 0.1
V>> 10 to 960 V, step of 0.1
Time delay
C264/EN UM/E50.5 361

Setting Value
2nd stage Definite Time (DT)
Definite time delay
tV> 0 to 600s, step of 0.01
tV>> 0 to 600s, step of 0.01
4.8.7 Residual overvoltage / neutral displacement (ANSI code 59N)

On a healthy three phase power system, the addition of each of the three phase to earth voltages
is nominally zero, as this results from the vector addition of three balanced vectors. However,
when an earth fault occurs on the primary system this balance is upset and a ‘residual’ voltage is
produced. This can be measured, for example, at the secondary terminals of a voltage
transformer having a “broken delta” secondary connection. Hence, a residual voltage-measuring
relay can be used to offer earth fault protection on such a system. Note that this condition causes
a rise in the neutral voltage with respect to earth, which is commonly referred to as “neutral
voltage displacement”.
The voltage setting applied to the protection elements is dependent upon the magnitude of
residual voltage that is expected to occur during an earth fault condition.
This in turn is dependent upon the method of system earthing employed. It must also be ensured
that the relay is set above any standing level of residual voltage that is present on the system.
The protection element has one programmable element Uen> with delay time tUen>.
Setting Value
Thresholds (secondary
values)
V 0> 1 to 260 V, step of 0.1
V
V 0> 5 to 960 V, step of 0.1
Time delay
Definite time delay
tV0> 0 to 600s, step of 0.01
362 C264/EN UM/E50.5

NOTE: Each measuring element time delay can be blocked by the operation of a user defined
logic (optically isolated) input (see “Blocking logic1” or “Blocking logic2” functions).
4.8.8 Directional / Non-directional phase OC protection (ANSI code 67/50/51)

If a fault current can flow in both directions through a relay location, it is necessary to add
directionality to the overcurrent relays in order to obtain correct co-ordination. Typical systems
that require such protection are parallel feeders and ring main systems.
In order to give directionality to an overcurrent relay, it is necessary to provide it with a suitable

reference, or polarising signal. The reference generally used is the system voltage, as its angle
remains relatively constant under fault conditions.
Each directional threshold consists of:

• Current threshold,
• Relay Characteristic Angle angle (IÛ) / Torque angle and Trip boundary zone.
The directional overcurrent protection element compares the directional fault current with the set
thresholds I> [50/51-1], I>> [50/51-2], I>>> [50/51-3], voltage and the relevant angle between the I
and U for each threshold.
The first and second thresholds can be set as directional or non-directional as definite delay time
or inverse delay time. The third threshold can be set as directional or non-directional as definite
delay time only, but can be set to work on the peak of the current measured in non-directional
way.
The protection elements trip when the following conditions occur:

• The phase current exceeds the set overcurrent threshold,
• The current vector lies within the trip boundary zone.
The choice of interlock functionality is available when the IDMT delay trip time is chosen on the
first threshold: The 2nd and 3rd threshold pickup can suspend 1st threshold output control to save
selectivity.
C264/EN UM/E50.5 363

Setting Value
Phase current Fundamental only
Phase voltage Fundamental only
Phase current range 0.1 to 40 x rated current ; step of 0.01 In
Treshold 0.1 to 10 In for each phase
Minimum voltage operation 0.6 V (Un: 57 to 130 V) ; 3.0 V (Un: 220 to 480 V)
Minimum phase voltage treshold: 0.6 V
Synchronous polarisation
synchronous polarising permanent time: 5 s
Hysteresis 95%
Instantaneous time < 30 ms
Drop out time 30 ms
Phase time delays (tl > , tl >> , tl >>>)
Reset time (for DMT) 0 ms to 600 s ; step of 10 ms
IDMT curves
RECT Rectifier
0.025 to 3.2 s ; step of 0.025 s
(TMS)
Reset time
IEEE / ANSI phase time
Inverse (CO8),
delay
Extremely inverse (ANSI).
0.025 to 3.2 ; step of 0.025 / 0.4 s to 100 s ; step of 0.01 s (DMT)
Setting (RTMS)
IEC curves phase time
0.04 s to 100 s ; step of 0.01 s
delay
364 C264/EN UM/E50.5

NOTE: When I> [50/51-1] or I>> [50/51-2] is associated to an IDMT curve, the maximum setting
recommended should be 2In.

67N/50N/51N)
The directional earth/ground fault protection provides three directional / non directional
earth/ground overcurrent thresholds.
The directional earth/ground fault overcurrent protection element compares the earth/ground fault
current, residual voltage with the set thresholds Ie> [50N/51N-1], Ue> [50N-1], Ie>> [50N/51N-2],
Ue>> [50N-2], Ie>>> [50N/51N-3], Ue>>> [50N-3] and the relevant angle between the Ie and Ue
for each threshold.
The first threshold uses only the acquired earth fault current. Second and third tresholds can use
acquired or computed earth/ground fault current. If an earth default voltage is acquired, it is used,
in all other cases the computed earth fault voltage is used.
The first and second threshold can be set as definite or inverse delay time. The third current
threshold can be set as directional or non-directional but with only definite delay time setting.

• thresholds for Ie [50N/51N] and Ue are exceeded (earth/ground fault overcurrent protection
element)
• Ie [50N/51N] current vector is in the tripping area (IeÛe)
• the tripping timer expires
The peak detection is applied where a CT saturation condition occurs and the measure is not
more trustworthy.
selectivity.
C264/EN UM/E50.5 365

Setting Value
Residual voltage Fundamental only
Earth / Ground current
0.002 to 40 x rated current ; step of 0.001 Ien
ranges
Ie> [50N/51N-1] 0.002 to 40 Ien ; step of 0.001 Ien
Treshold Ie>> [50N/51N-2] 0.002 to 40 Ien ; step of 0.001 Ien
Ie>>> [50N/51N-3] 0.002 to 40 Ien ; step of 0.001 Ien
Minimum residual voltage
1 to 260 V ; step of 0.1 V
operation
Hysteresis 95%
Instantaneous time < 30 ms
Drop out time 30 ms
Earth / Ground time
(tle > , tle >> , tle >>>)
delays
IDMT curves
RECT Rectifier
0.025 to 3.2 s ; step of 0.025 s
(TMS)
Reset time
IEEE / ANSI Earth / Ground
Inverse (CO8),
time delay
DMT 0.04 s to 100 s ; step of 0.01 s
366 C264/EN UM/E50.5

Setting Value
0.025 to 3.2 ; step of 0.025
Setting (RTMS)
IEC curves phase time
0.04 s to 100 s ; step of 0.01 s
delay
NOTE: When Ie> (50N/51N-1) or Ie>> (50N/51N-2) is associated to an IDMT curve the
maximum setting recommended should be the maximum of the range /20.
4.8.10 Overfrequency (ANSI codes 81O)

Overfrequency running of a generator arises when the mechanical power input to the machine
exceeds the electrical output. This could happen, for instance, when there is a sudden loss of load
due to tripping of an outgoing feeder from the plant to a load center. Under such over speed
conditions, the governor should respond quickly so as to obtain a balance between the
mechanical input and electrical output, thereby restoring normal frequency. Over frequency
protection is required as a back-up to cater for slow response of frequency control equipment.
Following faults on the network, or other operational requirements, it is possible that various
subsystems will be formed within the power network and it is likely that each of these subsystems
will suffer from a generation to load imbalance. The “islands” where generation exceeds the
existing load will be subject to overfrequency conditions, the level of frequency being a function of
the percentage of excess generation.
The relatively long time delays are intended to provide time for the system controls to respond and
will work well in a situation where the increase of system frequency is slow.
Setting Value
Thresholds
F1 Fn-0.01Hz to Fn-5Hz, step of 0.01
Definite time delay
tF1 0 to 600s, step of 0.01
C264/EN UM/E50.5 367

Setting Value
Where Fn is the nominal frequency.
4.8.11 Rate of change of frequency (ANSI code 81R)

The range frequency protection allows the user to select the number of cycle to be involved in the
calculation of the rate of change of frequency elements, and the number of confirmation of
calculation for positioning the protection.
In fact, the instantaneous element is positioned after exceeding the threshold for a programmable
number of df/dt function calculation.
When the input voltage value is insufficient this will lead to irregular behavior and the frequency
elements could mal operate.
This is important during line energization, de-energization or a generator acceleration where

significant distortion can be experienced. To prevent the mal operation, all the frequency
elements and related thresholds are blocked by mean of an adjustable U/V blocking function.
Setting Value
Thresholds
df/dt 1 -9 to 9 Hz/s, step of 0.1
Integration time
Cycle number 5 to 100, step of 1
Validation number of
protection
Validation 2 or 4, step of 2
Time delay setting
Definite time delay
tdf/dt> 0 to 600 s, step of 0.01
368 C264/EN UM/E50.5

4.8.12 Underfrequency (ANSI codes 81U)

Frequency variations on a power system are an indication that the power balance between
generation and load has been lost. In particular, underfrequency implies that the net load is in
excess of the available generation. Such a condition can arise, when an interconnected system
splits, and the load left connected to one of the subsystems is in excess of the capacity of the
generators in that particular subsystem. Industrial plants that are dependent on utilities to supply
part of their loads will experience underfrequency conditions when the incoming lines are lost.
In order to minimize the effects of underfrequency on a system, a multi stage load shedding
scheme may be used with the plant loads prioritized and grouped. During an underfrequency
condition, the load groups are disconnected sequentially depending on the level of
underfrequency, with the highest priority group being the last one to be disconnected.
Time delays should be sufficient to override any transient dips in frequency, as well as to provide
time for the frequency controls in the system to respond.
Setting Value
Thresholds
Definite time delay
Where Fn is the nominal frequency.
4.8.13 VT supervision (ANSI code 60FL)

The VT supervision function is used to block the protection functions whose behavior is impacted
due to voltage measurements. It helps in detecting a failure in the secondary circuits between the
voltage transformer and IED to avoid unintended operations of the voltage protection functions. A
C264/EN UM/E50.5 369

fault in the voltage measuring circuit is referred to as a fuse failure (ANSI code 60FL). This term
may be misleading since a blown fuse is just one of the many possible reasons for a broken
circuit.
A fuse failure may occur due to blown fuses, broken wires or intended substation operations. An
incorrectly measured voltage can result in an undesired operation of some protection functions.
Setting name Values Description

This setting determines whether the following operations
will occur upon detection of VTS
VTS Status set to 'Indication' provides indication 'Fuse

Fail condition detected' only (impacting only the delayed
relay)
VTS Status set to 'Blocking' provides:

• Optional Blocking voltage dependent protection
Blocking /
VTS Status elements
Indication / Off
• Indication 'Fuse Fail condition detected'
• Indication 'Voltage dependent function blocked due

to Fuse Fail condition detected' (impacting the
delayed and trip signals)
VTS Status set to 'OFF': the function shall cease to work

in this case and no indication shall be provided to the
user in case of a Fuse Fail condition
The VTS block will be latched after a user settable time
delay 'VTS Time Delay'. Once the signal has latched
then two methods of resetting are available:
• Manual: reset done manually via front panel
VTS reset mode Manual / Auto
interface or remote communication
• Auto: reset done automatically provided the VTS
condition has been removed and the Live Line
condition has been restored
1 to 10 s Setting that determines operating time delay of the

VTS time delay element upon detection of a voltage supervision
step of 0.1 s condition.
0.08 to 32 In The setting is used to override a voltage supervision

VTS I1>Inhibit block in the event of a phase fault occurring on the
step of 0.01 In system that could trigger the voltage supervision logic.
The setting is used to override a voltage supervision
0.05 to 0.5 In block in the event of a phase fault occurring on the
VTS I2>Inhibit
step of 0.01 In system with negative sequence current above this
setting which could trigger the voltage supervision logic.
370 C264/EN UM/E50.5

4.8.14 Inrush current blocking (ANSI code H2)

The Inrush Blocking detects high inrush current flows that occur when transformers or machines
are connected. The function identifies an inrush current by evaluating the ratio of the second
harmonic current components to the fundamental wave. If this ratio exceeds the set threshold,
then the inrush blocking function operates and inhibits the following functions:
• phase directional overcurrent [67/50/51]
• earth directional overcurrent [67N/50N/51N]
• negative sequence overcurrent [46]
Another settable current threshold (H2_Imax_threshold) blocks Inrush Blocking, if the current
exceeds this threshold. A fixed threshold (8% In) blocks Inrush Blocking, if the current is less than
this threshold.
Setting Value
Phase current Fundamental and 2nd harmonic (H1 & H2)
Thresholds
Ratio H1/H2 0.05 to 0.7, step of 0.01
Imax 4 to 32 In, step of 0.01
C264/EN UM/E50.5 371

4.8.15 Extra functions

4.8.15.1 Circuit breaker failure (50BF or TCS)
4.8.15.1.1 Description of the protection
Following the inception of a fault one or more main protection devices will operate and issue a trip
output to the circuit breaker(s) associated with the faulted circuit. Operation of the circuit breaker
is essential to isolate the fault, and prevent damage or further damage to the power system.
For transmission and sub-transmission systems, slow fault clearance can also threaten system
stability. It is therefore common practice to install circuit breaker failure protection [50BF], which
monitors that the circuit breaker has opened within a reasonable time. If the fault current has not
been interrupted following a set time delay from circuit breaker trip initiation, breaker failure
protection (CBF) will operate.
CBF operation can be used to back-trip upstream circuit breakers to ensure that the fault is
isolated correctly. CBF can also operate to reset all start output contacts, by external logic,
ensuring that any blocks asserted on upstream protection are removed.
4.8.15.1.2 Characteristics of the protection
Setting Value
Undercurrent threshold I< 2 to 100% of rated current, step of 1%
Threshold hysteresis maximum 0.008 In or 0.95 Is
CB failure time tBF 0 to 10 s, step of 0.01
Threshold accuracy
From 0.02 In to 0.1 In 0.006 In
From 0.1 In to 1 In 0.02 Is
4.8.15.2 Cold load start

4.8.15.2.1 Description of the function
In a protective relay, the Cold Load Pick-up feature enables the selected settings to be changed to
react to temporary overload conditions that may occur during cold load starts.
This condition may occur by switching on large heating loads after a sufficient cooling period, or
loads that draw high initial starting currents.
When a feeder is energized, the current levels that flow for a period of time following energizing
may differ greatly from the normal load levels. Consequently, overcurrent settings that have been
applied to give short circuit protection may not be suitable during this period.
The Cold Load Pick-up logic raises the settings of selected stages for a set duration. This allows
the protection settings to be set closer to the load profile by automatically increasing them after
energizing.
4.8.15.2.2 Characteristics of the function
Setting Value
Range 100 to 500% x nominal settings, step of 1%
372 C264/EN UM/E50.5

Setting Value
Time delay tCL 0.1 to 3600 s, step of 0.1
4.8.15.3 RSE
• Time delay in RSEA 1.5 s
• Time delay in RSEB 130 ms
4.8.15.4 Trip management

The trip control allows closure of their respective trip contact using external to protection function
mechanism. 3 SPC control relays Trip #1, #2 and #3.
Each trip status reflects the position of the respective relay. 3 SPS monitor the status of relays
Trip #1, #2 and #3.
If for a given MiCOM C264P, all the protection functions configured in the EPAS-SCE use the
three trip relays, in this case, only the trip Status reflects the relays position.
- Figure 98 - Figure Setting trip Management
If for a given MiCOM C264P, all the protection functions configured in the EPAS-SCE use the
three trip relays, in this case, only the trip status reflects the relays position.
C264/EN UM/E50.5 373

4.9 Protection Curves
4.9.1 IDMT Curves

4.9.1.1 Mathematical formula
4.9.1.1.1 IDMT threshold
Inverse Time Curves:
The first and second phases (earth) overcurrent threshold can be selected with a dependent time
characteristic. The time delay is calculated with a mathematical formula.
In all, there are eleven inverse time characteristics available.
The mathematical formula applicable to the first ten curves is:
Where:
t = Tripping time
K = Coefficient (see table)
I = Value of measured current
IS = Value of the programmed threshold (Pick-up value)
a = Coefficient (see table)
L = ANSI/IEEE coefficient (zero for IEC curves)
T = Time multiplier between 0.025 and 1.5
Type of a
Standard K factor L factor
curve factor
Short Time
Schneider Electric 0.05 0.04 0
Inverse
Standard
IEC 0.14 0.02 0
inverse
Very inverse IEC 13.5 1 0
Extremely
IEC 80 2 0
inverse
374 C264/EN UM/E50.5

Type of a
Standard K factor L factor
curve factor
Long time
Schneider Electric 120 1 0
inverse
Rectifier Schneider Electric 45 900 5.6 0
Short Time
C02 0.02394 0.02 0.01694
Inverse
Moderately
ANSI/IEEE 0.0515 0.02 0.114
Inverse
Long Time
C08 5.95 2 0.18
Inverse
Very Inverse ANSI/IEEE 19.61 2 0.491
Extremely
ANSI/IEEE 28.2 2 0.1215
Inverse
The RI curve (electromechanical) is given by the following formula:
With K adjustable from 0.10 to 10 in steps of 0.05
This equation is valid for 1.1<= (I/Is) <= 20
Although the curves tend towards infinite when the current approaches Is, the minimum
guaranteed value of the operating current for all the curves with the inverse time characteristic is
1.1Is (with a tolerance of ± 0,05Is).
4.9.1.1.2 Reset timer

The first phase overcurrent threshold [I>/tI>] ([Ie>/tIe>] for the earth) has a reset time. The fixed
period for this determines the minimum time during the current need to remain lower than 95% of
the phase (earth) threshold before the time delay associated with the phase (earth) overcurrent
threshold resets.
NOTE: There is an exception to this rule when the protection triggers. In fact, in this situation, the
time delays tI>/tIe> are immediately reinitialized.
The value of the Reset Timer depends on the type of the timer associated to the pick-up first
phase (Earth) threshold.
Type of timer associated to the first &

Reset Timer
second phase (earth) threshold
DMT + RECT 0 ms
Settable from 40
IDMT IEC or RI
ms to 100s
IDMT IEEE or COx Inverse Time
C264/EN UM/E50.5 375

Reset timer:
The first phase and earth overcurrent stages are provided with a timer hold facility "t Reset", which
may be set to a definite time value or to an inverse time characteristic (IEEE/ANSI curves only).
This may be useful in certain applications, for example when grading with upstream
electromechanical overcurrent relays which have inherent reset time delays.
Another possible situation where the timer hold facility may be used to reduce fault clearance
times is where intermittent faults occur. An example of this may occur in a plastic insulated cable .
In this application it is possible that the fault energy melts and reseals the cable insulation, thereby
extinguishing the fault. This process repeats to give a succession of fault current pulses, each of
increasing duration with reducing intervals between the pulses, until the fault becomes
permanent.
When the reset time of the overcurrent relay is minimum the relay will be repeatedly reset and not
be able to trip until the fault becomes permanent. By using the Timer Hold facility the relay will
integrate the fault current pulses, thereby reducing fault clearance time.
The reset timer "t Reset" facility can be found in the following menu:
• If the first phase (earth) threshold is selected with an IDMT IEC or RI curve, the reset timer "t
Reset" with DMT characteristic is settable in the menu:
• Protection [67/50/51] Phase OC/t Reset for the phase
• Protection [67N/50N/51N] E/Gnd/t Reset for the earth.
• If the first phase (earth) threshold is selected with an IDMT IEEE or CO curve, the reset timer
"t Reset" with IDMT characteristic is not settable.
Reset Time "t Reset" with an IDMT characteristic:
The mathematical formula applicable to the five curves is:
Where:
t = Reset time
K = Coefficient (see table)
I = Value of the measured current
IS = Value of the programmed threshold (pick-up value)
a = Coefficient (see table)
T = Reset Time Multiplier (Rtms) between 0.025 and 3.2
376 C264/EN UM/E50.5

Type of K a
Standard
curves factor factor
Short time
C02 2.261 2
inverse
Moderately
ANSI/IEEE 4.85 2
Inverse
Long time
C08 5.95 2
Inverse
Very inverse ANSI/IEEE 21.6 2
Extremely
ANSI/IEEE 29.1 2
inverse
C264/EN UM/E50.5 377

4.9.1.2 IEC Curves
378 C264/EN UM/E50.5

C264/EN UM/E50.5 379

380 C264/EN UM/E50.5

C264/EN UM/E50.5 381

382 C264/EN UM/E50.5

C264/EN UM/E50.5 383

4.9.1.3 RI Curves
384 C264/EN UM/E50.5

4.9.1.4 IEEE/ANSI & CO Curves
C264/EN UM/E50.5 385

386 C264/EN UM/E50.5

C264/EN UM/E50.5 387

388 C264/EN UM/E50.5

C264/EN UM/E50.5 389

390 C264/EN UM/E50.5

4.9.2 Thermal overload curves

4.9.2.1 Mathematical formula
The thermal time characteristic is given by:
exp(-t/t) = (I2 - (k.IFLC)2 ) / (I2 - IP2)
Where:
t = Time to trip, following application of the overload current, I
t = Heating and cooling time constant of the protected plant
I = Largest phase current; (RMS value)
IFLC = Full load current rating (relay setting 'Thermal Trip')
k = 1.05 constant, allows continuous operation up to < 1.05 IFLC.
IP = Steady state pre-loading before application of the overload
i.e. whether the overload was applied from "hot" or "cold".
Mathematical formula applicable to the MiCOM C264-P:
The calculation of the Time to Trip is given by:
With:
Ttrip = Time to trip (in seconds)
Te = Thermal time constant of the protected element (in seconds)
K = Thermal overload equal to Ieq/k Iq>
Ieq = Equivalent current corresponding to the RMS value of the largest phase current
Iq> = Full load current rating given by the national standard or by the supplier
k = Factor associated to the thermal state formula
q2 = Initial thermal state. If the initial thermal state = 30% then q2 = 0.3
qtrip2 = Trip thermal state. If the trip thermal state is set at 100%, then q trip2 = 1
The calculation of the thermal state is given by the following formula:
qi+1 = (Ieq/ k Iq>)2 [1- exp(-t/Te)] + qi exp(-t/Te)
q being calculated every 100ms
C264/EN UM/E50.5 391

4.9.2.2 10.2.2 Tripping curve
392 C264/EN UM/E50.5

MiCOM C264 - User Manual 5 Hardware
5 Hardware
5.1 Hardware conformity 397

5.2 Range description 398
5.2.1.2.1 Drawings 400
5.2.1.2.1.1 Without CT/VT 400
5.2.1.2.1.2 With CT/VT 400
5.2.1.2.2 Rear panel 401
5.2.1.2.2.1 Without CT/VT 401
5.2.1.2.2.2 With CT/VT 401
5.2.1.3.1 Drawings 402
5.2.1.3.1.1 Without CT/VT 402
5.2.1.3.1.2 With CT/VT 403
5.2.1.3.2 Rear panel 403
5.2.1.3.2.1 Without CT/VT 403
5.2.1.3.2.2 With CT/VT 404
5.2.1.4.1 Drawings 405
5.2.1.4.1.1 Without CT/VT 405
5.2.1.4.1.2 With CT/VT 406
5.2.1.4.2 Rear panel 406
5.2.1.4.2.1 Without CT/VT 406
5.2.1.4.2.2 With CT/VT 406
5.3 Connection of the protective conductor (Earth) 418
C264/EN UM/E50.5 393

5 Hardware MiCOM C264 - User Manual
5.3.1 Earthing 418

5.3.2 Cable fitting 419
5.4 Electronic hardware description 421
5.4.1 Board addressing 422
5.4.2 Coating 422
5.4.3 Input/Output connector block 422
5.4.4 CT/VT connector block (MiDOS) 422
5.4.5 BIU241 board – Power supply 423
5.4.5.6 Redundancy wiring 430
5.4.6 BIU261 board – dual source power supply 431
5.4.6.2 Jumper configuration 432
5.4.7 CPU275 board - Central Processing Unit and base communications board 436
5.4.7.5 Accessories 438
5.4.7.5.1 ECU200 – RS 232 to Optical converter 438
5.4.7.5.2 ECU201 – RS 232 to RS 485 / RS 422 converter 440
5.4.10 CCU200 board - Circuit breaker Control Unit 449
5.4.11 CCU211 board – Circuit breaker Control Unit (multi-voltages) 453
394 C264/EN UM/E50.5


5.4.12 DOU201 board - Digital Output Unit 458
5.4.13 AIU211 board - DC Analog Input Unit 460
5.4.14 AOU200 board – Analog Output Unit 462
5.4.15 - AC Analog Input Unit + DSPIO 466
5.4.16 DSP211 board 469
5.4.17 TMU220 board - AC Analog Input Unit 472
5.4.18 DSP200 board 477
5.4.19 SBU200 board – Smart terminal Block Unit 477
C264/EN UM/E50.5 395


5.4.20 SBU400 board – optical Smart terminal Block Unit 479
5.4.21 SWU20x board - Ethernet-based SWitch Unit 481
5.4.22 SWR212 board - Ethernet-based SWitch Redundant Unit 485
5.4.22.4 Optical fiber budget calculations 488
5.4.22.6 Wiring between two SWR212 489
5.4.23 SWS212 board - Ethernet-based SWitch RSTP compatible 490
5.4.24 REU20X board – Redundant Ethernet-Unit – PRP/HSR/RSTP 493
5.5 Terminal technical data 497
5.5.1 PC Maintenance Interface 497
5.5.2 Ethernet LAN (installed on the CPU275 board) 497
5.5.3 IRIG-B interface (standard NF S 87-500, May 1987), installed on the CPU275 board 497
5.5.4 Conventional communication links 497
5.5.5 Input /Output or power supply modules 497
5.5.6 Current-measuring and Voltage-measuring inputs 497
396 C264/EN UM/E50.5

5.1 Hardware conformity

(Per Article 10 of EC Directive 2014/35/EU).
The product designated “MiCOM C264 computer” has been designed and manufactured in
conformance with the standard IEC 60255-27:2013 and is compliant with the European
Commission Low Voltage Directive 2014/35/EU.
C264/EN UM/E50.5 397

5.2 Range description


5.2.1.2.1 Drawings 400
5.2.1.2.1.1 Without CT/VT 400
5.2.1.2.1.2 With CT/VT 400
5.2.1.2.2 Rear panel 401
5.2.1.2.2.1 Without CT/VT 401
5.2.1.2.2.2 With CT/VT 401
5.2.1.3.1 Drawings 402
5.2.1.3.1.1 Without CT/VT 402
5.2.1.3.1.2 With CT/VT 403
5.2.1.3.2 Rear panel 403
5.2.1.3.2.1 Without CT/VT 403
5.2.1.3.2.2 With CT/VT 404
5.2.1.4.1 Drawings 405
5.2.1.4.1.1 Without CT/VT 405
5.2.1.4.1.2 With CT/VT 406
5.2.1.4.2 Rear panel 406
5.2.1.4.2.1 Without CT/VT 406
5.2.1.4.2.2 With CT/VT 406
398 C264/EN UM/E50.5

5.2.1 Rack styles

The product is available in 3 different sizes (4U high), with a rack variant for the use of CT/VT:
• MiCOM C264C/ MiCOM C264S (compact size), 40 TE-wide
• MiCOM C264T/MiCOM C264U (medium size), 60 TE-wide
• MiCOM C264L/MiCOM C264M (large size), 80 TE-wide
5.2.1.1 mechanical specification
Rack style 40TE compact size 60TE medium size 80TE large size
Without With Without With Without With
CT/VT CT/VT CT/VT CT/VT CT/VT CT/VT
Name (as CORTEC
C264C C264S C264T C264U C264L C264M
code)
Dimensions
Length x Width x 206 x 220 x 177 mm 310 x 220 x 177 mm 414 x 220 x 177 mm
Height
Weight
May vary 4.0 kg 6.5 kg 8.0 kg

depending on
equipment
Case IP IP50 IP20 IP20
Rear panel IP IP10 IP10 IP10
Surface-mounted case suitable for wall installation or flush-mounted case
Installation for 19” cabinets and for control panels
Installation position: Vertical ±15°
C264/EN UM/E50.5 399

5.2.1.2 Rack 40TE mechanical details

5.2.1.2.1 Drawings
5.2.1.2.1.1 Without CT/VT
- Figure 99 - 40TE - Drawings - Without CT/VT
5.2.1.2.1.2 With CT/VT
- Figure 100 - 40TE - Drawings - With CT/VT
400 C264/EN UM/E50.5

5.2.1.2.2 Rear panel
- Figure 101 - 40TE - Rear panel - Without CT/VT
5.2.1.2.2.2 With CT/VT
- Figure 102 - 40TE - Rear panel - With CT/VT
C264/EN UM/E50.5 401

5.2.1.2.3 Fastening holes
- Figure 103 - 40TE - Fastening holes

5.2.1.3.1 Drawings
402 C264/EN UM/E50.5

5.2.1.3.1.2 With CT/VT
C264/EN UM/E50.5 403

5.2.1.3.2.2 With CT/VT
404 C264/EN UM/E50.5


5.2.1.4.1 Drawings
C264/EN UM/E50.5 405

5.2.1.4.1.2 With CT/VT
5.2.1.4.2.2 With CT/VT
406 C264/EN UM/E50.5

5.2.2 Front panels

Front panel Blind LEDs LCD + LEDs
17 LEDs (13 are user
configurable)
7 pushbuttons (function
RJ11 connector for 17 LEDs (12 are user keys)
specifications remote front panel configurable)
5 pushbuttons (HMI
connection 1 pushbutton management
LCD (resolution of 128 x

128 pixels /16 lines of 21
characters each
Burden 0 400 mW 700 mW
IP IP10 IP52 IP52
GHU220 GHU210 GHU200
40TE -
Compact size
60TE -
Medium size
80TE -
Large size
C264/EN UM/E50.5 407

5.2.3 Basic functions/components

The MiCOM C264 is based on a modular and scalable architecture to support dedicated
hardware modules adapted to the plant data interfaces.
Each MiCOM C264 rack can be equipped with the following modules:
Short designation Designation

Front Back Plane FBP2xx
FBP243 Front Back Plane BUS Case 40 TE CPU275
Front panels
GHU20x Front Panel with Leds + Graphic Display LCD +L/R switch
GHU21x Front Panel Leds and L/R switch
GHU22x Simple Blind front panel
Power supply
BIU241-A0x power supply- watchdog relay - 2DO - 2DI - 2 serial ports
dual source power supply watchdog relay - 2DO - 2DI - 2 serial
BIU261-A0x
ports
CPU
CPU4, 2 ethernet ports, IRIG-B input + 2 Serial links, 256Mb
CPU275 -A0x
SDRAM memory
ECU converters
ECU201 RS 232/ RS 485 converter for CPU serial ports
ECU200 RS 232/ Optical converter for CPU serial ports
Transducerless Measurement Unit - Direct measuring value acquisition: 4 CT + 4 VT
TMU220 TMU220 (4*I + 5*U) 4-poles, Inom: 1 A / 5A, Vnom: 57 to 250 VAC
TMU210A0x TMU210 Protection functions
DSP200 DSP - to be used on TMU220
DSPIO with separated Trip Contacts - to be used with
DSP211 - A0x
TMU210A0x
DIU - 16 Digital input unit
DIU200-A0x 16 Inputs
16 Inputs: multi-voltage + peak current 24Vdc -> 250V dc,
DIU211
adjustable thresholds
DOU - Digital outputs module, with 10 digital outputs
10 Digital outputs: 8 outputs NO contacts + 2 outputs NO/NC
DOU201
contacts
408 C264/EN UM/E50.5

Short designation Designation

CCU - CB Control Unit - 8 DI + 4 DO module with 8 digital inputs and, 4 digital outputs
CCU200-A0x 8 Inputs and 4 output Contacts
8 Inputs- multiVoltage, adjustable thresholds + and 4 output
CCU211
Contacts
AIU - Analog inputs module
AIU211 8 DC Analog inputs module (Currents) -Isolated
AOU- Analog output module (Currents), with 4 analog outputs
AOU200 4 Analog Outputs
SBU200- Smart Block Acquisition Unit (DI/DO)
SBU200 8 ports acquisition units for Smart Terminal Blocks
SBU200
DI&DO
SBU400 - 2 optical Ports with Fiber Optic interface for acquisition
SBU400
from the SMTB-optical Converter -Slave
Ethernet-based Switch Unit (SWU20x)
SWU200 SWU200 - With four 10/100BaseT Ethernet ports (RJ45)
SWU202- With two 100BaseF Multimode Ethernet ports (ST) and
SWU202
four 10/100BaseT ports (RJ45)
Ethernet-based Switch Redundant Unit (SWR2xx)
SWR212 -With two 100BaseF Multimode ports (ST) + 4*
SWR212
10/100BaseT (RJ45) -SNMP
Ethernet-based Switch - RSTP compatible (SWS2xx)
SWS212 -With two 100BaseF Multimode ports (ST) + 4*
SWS212
10/100BaseT (RJ45) -SNMP
Redundant Ethernet Unit- PRP/HSR (REU20x)
REU202-V2 Multimode: with 2 Eth. Ports (HSR/PRP/RSTP) +
REU202- V2 10/100BaseT RJ45 Eth. Port with 2 SFP Connectors multimode
Ref: HUA26158
REU204-V2 SingleMode : with 2 Eth. Ports (HSR/PRP/RSTP) +
REU204- V2 10/100BaseT RJ45 Eth. Port with 2 SFP Connectors Single mode
Ref: HUA26502
REU-V2 : with 2 Eth. Ports (HSR/PRP/RSTP) + 10/100BaseT
REU-V2 RJ45 Eth. Port. SFP Fiber Optic interface not provided (separate
accessories)
5.2.4 Product configuration

The MiCOM C264 minimum equipment includes:
• A case(rack)
• A front panel
C264/EN UM/E50.5 409

• A BIU241 or BIU261 (in slot A)
• A CPU275 (in slot B)
The optional equipment includes communication, I/Os and acquisition modules.
The slot C (or D if TMU210/DSP211 is present) is reserved for SWx/REU board except if the rack
is full. In that case an additional standard IO module may be mounted in that slot.
The number of remaining slots depends on the size of the case and the choice of analog module.
The following tables give the maximum capability of products for each combination.
Please refer to the Cortec for complementary information on boards arrangement.
5.2.4.1 40TE slot configuration
- Figure 114 - 40TE slot configuration
Maximum number of boards in 40TE rack

Board
Without TMU With TMU220 With TMU210
SWx/REU 1 1 1
AIU 6 4 3
AOU 4 4 3
CCU 6 4 3
DIU 6 4 3
DOU 6 4 3
SBU 6 2 2
TOTAL 6 4 3
410 C264/EN UM/E50.5


Board
SWx/REU 1 1 1
AIU 6 6 6
AOU 4 4 4
CCU 10 9 8
DIU 10 9 8
DOU 10 9 8
SBU 9 7 7
TOTAL 10 9 8
C264/EN UM/E50.5 411


Board
SWx/REU 1 1 1
AIU 6 6 6
AOU 4 4 4
CCU 15 14 13
DIU 15 14 13
DOU 15 14 13
SBU 9 9 9
TOTAL 15 14 13
5.2.5 Environment conditions

Type Value / Range
Operating Temperature
-25 to +70°C
range
Ambient relative Humidity ≥75 % relative humidity (annual mean), up to 56 days at = 93%
range relative humidity and 40 °C, condensation not permissible.
412 C264/EN UM/E50.5

5.2.6 Power supply

Power Supply DC Power Supply AC
Product equipped with
Nominal Auxiliary Voltage Nominal Auxiliary Voltage
power supply board type
(+/- 20%) (+/- 20%)
Board BIU241 24 Vdc to 220Vdc 78 Vac to 230Vac
Board BIU261 48 Vdc to 220Vdc Not applicable
5.2.7 Consumption
Consumption highly depends on the product hardware configuration.
Example given for for a MiCOM C264 40TE including:

• one led+LCD front plate,
• one 48V power supply board,
• one CPU,
• one ethernet communication board,
• 3 digital outputs boards
• and 2 digital inputs boards.
- Figure 117 - Consumption sample
Board Nominal Additional

GHU200 600 mW +2.4W if screen is backlit
BIU241 +
3.7W
CPU275
SWU202 5.9 W
DOU201 250 mW (x3) +220 mW per activated relay
DIU211 210mW (x2) +10mW per activated input
Total 11.2W max 4.76W
Refer to the BIU241 or BIU261 technical characteristics to know the maximum consumption
allowed (internal available power).
C264/EN UM/E50.5 413

5.2.8 Reliability
Type Value / Range
Average life >12 years
MTBF 254000 hours
5.2.9 environmental characteristics

test name standard level/class value
product Safety
Dielectric IEC 60255-27
2640 Vac / 1500 Vac/ 1 mn
Withstand EN 60255-27
Insulation IEC 60255-27
100 Mohms 500 V
Resistance EN 60255-27
IEC 60255-27 1,2 / 50 µs ±5 kV / ±2 kV
Impulse voltage
EN 60255-27 CM, 3 kV DM
EMC
electrostatic
IEC 61000-4-2 level 4 ±8 kV contact - ±15 kV air
discharges
80MHz to 1GHz (16 V/m)
1,4GHz to 2GHz (20V/m)
2GHz to 2,7GHz (12V/m)
2.7GHz-6GHz (1V/m)
Radiated radio
sinus AM (80%, 1kHz)
frequency fields IEC 61000-4-3 level 3
3000ms
immunity
+ spot frequencies 80,160,
380, 450 & 900 MHz (30
V/m)
1.85 & 2.15 GHz (28V/m &

12V/m)
PS ±4kV 2,5 kHz
immunity to fast level 4
IEC 61000-4-4 signal ±2 kV 5 kHz and 100
transient burst level 4
kHz
PS ±4kV CM, ±2 kV DM
level 4
surge immunity IEC 61000-4-5 signal ±2 kV CM, ±1 kV DM
level 3
(signal)
414 C264/EN UM/E50.5


Frequency range: 150 kHz
to 80 MHz
HF conducted
IEC 61000-4-6 level 3 + Spot frequencies: 27
immunity
MHz & 68 MHz
10 V (PS) / 12 V (others)
100 A/m continuous1000
Magnetic field
IEC 61000-4-8 level 5 A/m short duration (2
immunity
seconds) 3 axes
Pulse magnetic
IEC 61000-4-9 level 5 1000 A/m 1.2 / 50μs 3 axes
field immunity
Damped
oscillatory ±100 A/m - 100 kHz & 1
IEC 61000-4-10 level 5
magnetic field MHz 3 axes
immunity
Damped ±2,5 kV CM / ±1 kV DM 100
oscillatory wave IEC 61000-4-18 level 3 kHz 1 MHz 3 MHz 100 MHz
immunity 100 kHz 1 MHz DM
common mode
disturbance 50/60 Hz 30 V 5 mn/ 300 V
IEC 61000-4-16 level 4
immunity / mains 1s
frequency
ΔU 30% for 0,1 sΔU 60%
voltage dips IEC 61000-4-29 -
for 0,1 s
voltage ΔU 100% for 0,05 s at 0,8
IEC 61000-4-29 -
interruption Un
Ripple on d.c.
IEC 60255-26 - 15% of Un
power supply
supply variations IEC 61000-4-29 - 0,8 Un and 1,2 Un; 1 min
0,15 to 0,5 Mhz max quasi
CISPR 11 pk 79 dBµV; average 66
conducted
CISPR 32 class A dBµV 0,5 to 30 Mhz max
emission PS
EN 55011 quasi pk 73 dBµV; average
60 dBµV
@ 3 m 30 to 230 MHz max
CISPR 11
radiated quasi pk 50 dBµV/m 230
CISPR 32 class A
emission Mhz to 1 GHz max quasi pk
EN 55011
57dBµV/m
Climatic
C264/EN UM/E50.5 415


5 cycles / -25°C (3 hours)
Cyclic
IEC 60068-2-14 to +55°C (3 hours);
temperature
slope1°C /min.
Dry heat and cold IEC 60068-2-1 -10°C for 2 hours

temperature IEC 60068-2-2 +55°C for 2 hours
EDF–HN 46-R-01-4
Damp heat stady +40°C, 93% RH for 21
EN 60068-2-78
state humidity days
IEC 60068-2-78
Prolongated
steady state +55°C ±2°C,
operation 1000 EDF HN 46-R-01-6
duration 1000 hours
hours at 55°C
Salt solution concentration:
5% ± 1% by weight
pH value of the solution

between: 6.5 and 7.2
Temperature during salt

mist: between 15°C and
Test Kb - Salt 35°C
mist, cyclic
IEC 60068-2-52 Severity (2) Temperature during
(tropicalized storage period: 40°C ± 2 °C
product)
Humidity during storage
period: 93+2-3%RH .
Severity: 3 spray periods,

each of 2 hours with a
humidity storage period
between 20 h and 22 h
after each.
Gas concentration :
H2S (10 ± 2) ppb;
Test Ke: Flowing NO2: (200± 2) ppb;
mixed gas CL2 : (10 ± 2) ppb;
corrosion test IEC 60068-2-60 SO2: (200± 2) ppb
(tropicalized Temperature (25 ± 2)°C
product)
Humidity : 75% ± 10%
21 days
Mechanical robustness
416 C264/EN UM/E50.5


Vibration
response and IEC 60255-21-1 Class 2 Axis X-Y-Z
endurance
Shock response,
shock withstand IEC 60255-21-2 Class 2 Axis X-Y-Z
and bump
Seismic IEC 60255-21-3 Class 2 Axis X-Y-Z
C264/EN UM/E50.5 417

5.3 Connection of the protective conductor (Earth)

5.3.1 Earthing
MiCOM C264 must be connected to the earth according to product safety standard EN 60255-
27:2014 using the protective conductor (earth) terminal located on the rear panel.
Connection of the Protective conductor (earth).
The MiCOM C264 racks must be earthed, for safety reasons, by connection of the protective
conductor (earth) to the M4 threaded stud allocated as the protective conductor terminal (PCT),
marked with the symbol shown.
DANGER
HAZARD OF ELECTRIC SHOCK, ELECTRIC ARC OR BURNS
• Connect the ground terminal of the equipment to the protective earth / ground.
• Comply with national and local electrical standards with respect to the earth / ground of each
equipment.
• Check equipotential earthing/grounding network and test earth/ground during installation.
• The recommended minimum protective conductor (earth) wire size is 2.5mm² (3.3mm² for
North America) unless otherwise stated in the technical data section of the equipment
documentation, or otherwise required by local or country wiring regulations.
• The protective conductor (earth) connection must be low-inductance and as short as
possible.
The protective conductor (earth) must be as short as possible with low resistance and inductance.
The best electrical conductivity must be maintained at all times, particularly the contact resistance
of the plated steel stud surface. The resistance between the MiCOM C264 protective conductor
(earth) terminal (PCT) and the protective earth conductor must be less than 10 mW at 12 Volt, 100
Hz.
- Figure 118 - Earthing connector
418 C264/EN UM/E50.5

5.3.2 Cable fitting

It is recommended to use cables (0.8 mm2) as following:
• Screened multi-strand cable has to be used for digital input-output signals. For cables within
the cubicle the cable screen can be connected to the earth at both ends of the cable. If the
cable is taken beyond the system cubicle the cable screen should be earthed at one end only
to prevent current flowing in the screen due any differences in ground potential.
• Screened and twisted pair has to be used for analogue input-output signals. The screen is
connected to the earth by the end of Bay Module side.
• One or two screened and twisted pairs have to be used for lower communication signals. The
screen is connected to the earth by two cable ends.
It is recommended to group cables and fit them as near as possible to an earth plane or to an
element of an earth wire-mesh.
First example: MiCOM C264 fitted without metallic cubicle:
- Figure 119 - MiCOM C264 fitted without metallic cubicle - sample #1
Second example: MiCOM C264 fitted in a metallic cubicle with other devices:
C264/EN UM/E50.5 419

- Figure 120 - MiCOM C264 fitted in a metallic cubicle with other devices - sample #2
420 C264/EN UM/E50.5

5.4 Electronic hardware description

Hereafter is an overview of boards available in MiCOM C264:
- Figure 121 - Electronic hardware description
C264/EN UM/E50.5 421

5.4.1 Board addressing

The same rule is applicable to all I/O boards (DIU200, DIU211, AIU211, AOU200, DOU201,
CCU200 and CCU211) :
Binary coding from 0 to 15 based on 4 jumpers:

• missing => binary value of bit is 1
• present => binary value of bit is 0
Example:
- Figure 122 - Board addressing - sample
NOTE: Two boards of the same type must not have the same address
5.4.2 Coating
For use case in harsh environment an optional coating (tropicalization) may be provided on
demand.
5.4.3 Input/Output connector block

Most of the input/output connection (except mentioned in board description) uses a standard type
of connector block with a 24-pin and 5.08 mm pitch.
The I/O connector block characteristics are the following:
Characteristic Value / Range

Continuous rating 10 A
Connection method Front screw M2,5
Cable size 0.34 - 2.5 mm2
Connection pitch 5,08 mm
Isolation to other terminal and to earth 300 V basic insulation
Standards UL, CSA
5.4.4 CT/VT connector block (MiDOS)

MiCOM C264 uses a MiDOS 28 terminal block for transformer connection.
CT connection has 2 dual terminal groups, this allows dual rated transformer (1A/5A). Each group
has shorting contact to allow disconnection of CTs without damage.
The CT/VT connector block characteristics are the following:
422 C264/EN UM/E50.5


VT connection
3 second rating 30 A
30 ms rating 250 A
Connection method Screw M4
Cable size 2 to 2.5 mm2
CT connection

Connection method Screw M4
Cable size 2 to 2.5 mm2 / 1 to 4 mm2
- Figure 123 - CT/VT connector block (MiDOS)
NOTE: The connector is fixed to the rack with 4 Phillips screws M4
5.4.5 BIU241 board – Power supply

5.4.5.1 Description
This board is the auxiliary power supply converter and offers the following additional features:
C264/EN UM/E50.5 423

• a watchdog relay NO/NC (operated if the product is healthy)
• 2 digital outputs (Normally Open) with a common and 2 isolated digital inputs with a common
intended to achieve a C264 redundancy configuration (optional)
• 2 isolated serial link interfaces (Port 1: RS 232 or RS 485, Port 2: RS 232, RS 422 or RS 485)
- Figure 124 - BIU241 board
5.4.5.2 Port 1 jumper configuration

Port 1 is configured depending on the selected protocol thanks to the addition of jumpers as
described in the following table.
Jumper configuration - port 1
RS 232
S14 S16 S12(1-3)
424 C264/EN UM/E50.5

RS 485
S13 S15 S12(1-2)
optionally S17 to add a termination resistor (124 Ω)
NOTE: For RS 485 serial communication interface a termination resistor must be connected at
each extremity of the bus.
5.4.5.3 Port 2 jumper configuration

Port 2 is configured depending on the selected protocol thanks to the addition of jumpers as
described in the following table.
RS 232
S3, S5, S6 and S9
C264/EN UM/E50.5 425

RS 485
S2 S7 and S8
RS 422
S1, S4, S7 and S8
Optionally S10 and S11 to add a termination resistor (124 Ω)
NOTE: For RS 485 or RS 422 serial communication interface a termination resistor must be
connected at each extremity of the bus.
426 C264/EN UM/E50.5

5.4.5.4 Technical characteristics
Variant A01 A02 A03 A04

DC nominal
auxiliary voltage 24 Vdc 48 – 60 Vdc 110 – 125 Vdc 220 Vdc
(+/-20%)
AC nominal
auxiliary voltage Not available 78 – 113 Vac 156 - 230 Vac
(+/- 20%)
AC frequency
Not available 50/60Hz +/-10%
operating range
I<20 A for t <1.5ms
Inrush current at
I<10A for 1.5ms < t <500 ms
start-up
I<1.2In for t >500 ms
Internal available
40W
power
Efficiency 75%
Burden (no load) 0.8W 1W 1W 1.32W
Reverse polarity
yes BIU operates regardless of polarity
protection
Digital inputs
Digital input
24 Vdc 48 – 60 Vdc 110 – 125 Vdc 220 Vdc
nominal voltage
Triggering
threshold pick up 17V 29V
(set)
Triggering
threshold drop off 12,1V 19,2V
(reset)
Digital Outputs - watchdog
Nominal 24 to 250 Vdc
Operating
voltage ranges 230 Vac
30 A (during 500 ms)

Current overload
Carry current
5A
(max)
C264/EN UM/E50.5 427


50 W on resistive load
30 W on inductive load (L/R = 40 ms)
2000 VA on resistive load

Max Breaking
capacity 1250 VA on inductive load (cos φ = 0.7)
10000 operations
Full load / Duty cycle: 1.5 s ON - 5s OFF. The contact resistance stays under
250 mΩ.
Serial link
Type Isolated RS 232 / RS 422 / RS 485
full duplex for RS 232 / RS 422
network
half duplex for RS 485
Transmission
50 b/s to 56 kb/s (set with EPAS SCE configurator or with GHU20x)
rate
Optional
termination 124 Ω
resistor
5.4.5.5 Rear panel connector
DANGER
HAZARD OF ELECTRIC SHOCK, EXPLOSION OR ARC-FLASH BEFORE PERFORMING
ANY INTERVENTION
When the communication ports are connected to devices:
• Do not connect the signal ground SG of the serial ports 1 (pin13) and 2 (pin 15) to the local
earth/ground.
• Do not connect the signal ground SG of the serial ports 1 (pin13) and 2 (pin15) together.
• The screen of RS 232 / RS 422 / RS 485 cable must be connected to a protective earth.
• If the same earth/ground potential is not insured between the two ends of the RS 232 / RS
422 / RS 485 cable or, if the connection is to cover a wide area or includes IT or TN-C
earthing systems it is recommended to implement a backup protective earthing/grounding
cable to connect the communicating equipment(16 mm²)
428 C264/EN UM/E50.5

Pin# Signal
Redundancy relay
1 DO2 NO contact
2 DO1/2 common
3 DO1 NO contact
Watchdog relay
4 WD NO contact
5 WD NC contact
6 WD common
Redundancy input
7 DI1+
8 DI common 1 / 2
9 DI2+
10 unused
11 unused
Port 1
RS 232 RS 485
12 RxD B
13 SG1 unused
14 TxD A
Port 2
RS 232 RS 485 RS 422
15 SG2 unused unused
16 CTS unused unused
17 RxD B TB
18 TxD A TA
19 RTS unused RB
20 unused unused RA
21 DCD unused unused
Voltage input AC/DC
22 PS Gnd (earth)
23 PS ( + )
24 PS ( ─ )
C264/EN UM/E50.5 429

5.4.5.6 Redundancy wiring
The following schema shows the wiring of a redundant MiCOM C264 pair, composed of 2
MiCOM C264 C264-1 and C264-2 linked together via redundancy relays and inputs.
- Figure 125 - MiCOM C264 redundant pair wiring
Here are the relays and inputs statuses depending on the MiCOM C264 redundant statuses
(Acive/Standby) in the pair:
Relays and inputs statuses in a redundant pair of MiCOM C264

C264-1 Active C264-2 Standby
DO1 closed DI1 set
DO2 closed DI2 set
DI1 reset DO1 open
DI2 reset DO2 open
C264-1 Standby C264-2 Active
DO1 open DI1 reset
DO2 open DI2 reset
DI1 set DO1 closed
DI2 set DO2 closed
430 C264/EN UM/E50.5

5.4.6 BIU261 board – dual source power supply

5.4.6.1 description
The BIU261 board is single power supply converter with a dual source auxiliary power supply.
The voltage range is the same for both input power supplies. In case of failure of the main power
supply the backup power source takes over.
At start-up the main input voltage must be at least 95% of nominal value otherwise the BIU starts
with the backup voltage source.
The main power supply is considered as missing (or failed) if the voltage is less than 80% of the
nominal value.
Switch from backup to main power supply occurs as soon as the main input voltage reaches 95%
of nominal value
This board offers the following additional features:

• a watchdog relay NO/NC (operated if the product is healthy)
• 1 isolated serial link interfaces (Port 2: RS 232, RS 422 or RS 485)
• Reverse polarity protection
- Figure 126 - BIU261 board
C264/EN UM/E50.5 431

5.4.6.2 Jumper configuration

The communication port (named port2) is configured depending on the selected protocol thanks
to the addition of jumpers as described in the following table.
RS 232
S3, S5, S6 and S9
RS 485
S2 S7 and S8
RS 422
S1, S4, S7 and S8
Optionally S10 and S11 to add a termination resistor (124 Ω)
Variant A02 A03 A04

DC nominal auxiliary
voltage for main 48 – 60 Vdc 110 – 125 Vdc 220 Vdc
source (+20%)
432 C264/EN UM/E50.5

Variant A02 A03 A04

Minimum DC nominal
auxiliary voltage to
46.5V 104.5V 203 V
start with main source
see Remark (*)
DC nominal auxiliary
voltage for backup 48 – 60 Vdc 110 – 125 Vdc 220 Vdc
source (+/- 20%)
I<20 A for t <1.5ms
Inrush current at start-
I<10A for 1.5ms < t <500 ms
up
I<1.2In for t >500 ms
Internal available
40W
power
Efficiency 75%
Burden 2,1W 2,6W 3,3W
Reverse polarity
yes
protection
Power source
-20%
switching threshold
Switching time from
main to backup 20 ms (max)
source
Switching time from
backup to main 20 ms (max)
source
Voltage insulation
between Main &
2500 V Rms
backup power supply
source
Watchdog relay
Nominal Operating 24 to 250 Vdc

voltage ranges 230 Vac
Current overload
Carry current (max) 5A
C264/EN UM/E50.5 433

Variant A02 A03 A04


Max Breaking
10000 operations
Full load / Duty cycle: 1.5 s ON - 5s OFF. The contact resistance stays
under 250 mΩ.
Serial link
Type Isolated RS 232 / RS 422 / RS 485
full duplex for RS 232 / RS 422
network
half duplex for RS 485
Transmission rate 50 b/s to 56 kb/s (set with EPAS SCE configurator or with GHU20x)
Optional termination
124 Ω
resistor
Remark (*): if main source is above these values the BIUR will start with the backup source.
DANGER
HAZARD OF ELECTRIC SHOCK, EXPLOSION OR ARC-FLASH BEFORE PERFORMING
ANY INTERVENTION
When the communication ports are connected to devices:
• Do not connect the signal ground SG of the serial ports 1 (pin13) and 2 (pin 15) to the local
earth/ground.
• Do not connect the signal ground SG of the serial ports 1 (pin13) and 2 (pin15) together.
• The screen of RS 232 / RS 422 / RS 485 cable must be connected to a protective earth.
• If the same earth/ground potential is not insured between the two ends of the RS 232 / RS
422 / RS 485 cable or, if the connection is to cover a wide area or includes IT or TN-C
earthing systems it is recommended to implement a backup protective earthing/grounding
cable to connect the communicating equipment(16 mm²)
434 C264/EN UM/E50.5

Pin# Signal
Unused pins
1 unused
2 unused
3 unused
Watchdog relay
4 WD NO contact
5 WD NC contact
6 WD common
Unused pins
7 unused
8 unused
9 unused
Backup DC voltage source
10 PS backup ( + )
11 PS backup ( ─ )
Unused pins
12 unused
13 unused
14 unused
Port 2
RS 232 RS 485 RS 422
15 SG2 unused unused
16 CTS unused unused
17 RxD B TB
18 TxD A TA
19 RTS unused RB
20 unused unused RA
21 DCD unused unused
Main DC voltage source
22 PS Gnd (earth)
23 PS ( + )
24 PS ( ─ )
C264/EN UM/E50.5 435

5.4.7 CPU275 board - Central Processing Unit and base communications

board
5.4.7.1 Description
The CPU275 board is the central processing unit of the MiCOM C264 based on a PowerPc
processor. This board is interfaced with all I/O boards and the front panel.
It offers the following additional features:

• Two 10/100 BaseT Ethernet ports
• Two non-isolated RS 232 links. The transmission rate must be the same on both links (values
from 50 to 56000 bps configurable with the configuration tool or settable via the front panel)
• Optionally : the ECU200/ECU201 external modules convert non-isolated RS 232 into optical
link/isolated RS 485 or RS 422.
• An IRIG-B interface (standard NF S 87-500, May 1987 )
• An optional daughter board (DSP or DSPIO) for CT/VT management
• Backed up Real Time Clock
- Figure 127 - CPU275 board
5.4.7.2 Configuration / options

Not available.
436 C264/EN UM/E50.5


256 Mbytes SDRAM
Memory 128 Mbytes flash memory
128 Kbytes VNRAM

Burden 2.7 W (may vary depending on application load)
Ethernet
Ethernet connection RJ45 10/100 Mbs
Maximum cable length 15 m
IRIG-B
connection BNC
Cable type 50 ohms coaxial
Maximum cable length < 150 m
modulation Amplitude modulated, 1 kHz carrier signal
BCD
Time code format
B122 compatible
RS 232 non-isolated
connection DIN 41652 connector; type D-Sub, 9-pin, male
C264/EN UM/E50.5 437

Overview Port pins
RJ45 -ETH
pin signal
1 Rx+
2 Rx-
3 Tx+
4 Not used
5 Not used
6 Tx-
7 Not used
8 Not used
DB9 – RS 232
pin signal
1 CD
2 RX
3 TX
4 5V (for ECU20x supply)
NOTE: Unlike standardized RS 232 5 SG (0 V)

connector, pin 4 is not used as the DTR 6 Not used
signal. It is permanently connected to power 7 RTS
supply +5 V. So this pin 4 must not be used 8 CTS
for a null-modem cable.
5.4.7.5 Accessories
Not available.
5.4.7.5.1 ECU200 – RS 232 to Optical converter

The ECU200 is an additional module to plug on the DB9 connector of the CPU board. This
module converts a non-isolated RS 232 port into an optical port with ST connectors for multi-
mode fiber.
438 C264/EN UM/E50.5

- Figure 128 - ECU200 convertor
Technical characteristics
Type Value / Range
Non-isolated com port
connector type D-SUB 9 pins
Optical port
Connector type ST
Fiber type Multimode glass fiber 62.5/125µm
wavelength 820nm
optical input power max for
-40 dBm
high level
optical input power for low
-24 dBm to -10dBm
level
Optical output power -15 dBm to -10 dBm
Overview Port pins
DB9
pin signal
1 not used
2 TX
3 RX
4 5V
5 0V
6 not used
7 not used
8 5V
9 not used
C264/EN UM/E50.5 439

5.4.7.5.2 ECU201 – RS 232 to RS 485 / RS 422 converter

The ECU201 external module converts a non-isolated RS 232 communication port into an
isolated RS 485 or RS 422 communication port.
- Figure 129 - ECU201 convertor
A switch allows to choose either RS 422 or RS 485:
- Figure 130 - ECU201 switch
To change the connection type, slide the tab:

• RS 422 (4 wires): The hole must be hidden.
• RS 485 (2 wires): The hole must be visible.
Type Value / Range
Non-isolated com port
connector type D-SUB 9 pins
Isolated com port
connector type 5 pins terminal block
440 C264/EN UM/E50.5

Type Value / Range
Continuous rating 6A
Nominal voltage 160 V
Connection method Screw M1,6
Cable size 0.14 – 0.5 mm2
Connection pitch 2,54 mm
Standards UL, CSA
Port pins
DB9
pin signal
1 not used Terminal block pinout
2 TX pin silkscreen RS 422 RS 485
3 RX 1 TA+ Rx+ Tx/Rx+
4 5V 2 TB Rx (-) Tx/Rx-
5 0V 3 GND shield shield
6 not used 4 RA+ Tx+ Not used
7 not used 5 RB Tx- Not used
8 5V
9 not used NOTE: pin 3 reserved for RS 422 / RS 485
cable shield connection.
5.4.8 DIU200 board - Digital Input Unit

5.4.8.1 Description
The Digital inputs Unit (DIU200) board provides 16 optically isolated digital inputs arranged by
pairs including:
C264/EN UM/E50.5 441

• 4 input voltage ranges
• 1 negative common contact for 2 inputs
• Protection against polarity reversal
- Figure 131 - DIU200 board

Board address configuration : see "Board addressing" on page 422.

Nominal voltage
24 Vdc 48 - 60 Vdc 110 – 125 Vdc 220 Vdc
+/- 20%
442 C264/EN UM/E50.5


Triggering
threshold pick up V >10 Vdc V >17.4 Vdc V > 50 Vdc if V > 108 Vdc
(set)
Triggering
threshold drop off V < 5Vdc V <13.5Vdc V < 34.4Vdc V < 63Vdc
(reset)
Input burden (per 5mA @ 48Vdc 2.5mA@110Vdc

3.5mA@24Vdc 2mA@220Vdc
active input) 6.8mA@60Vdc 3mA@125Vdc
Nominal voltage
24 Vdc 48 - 60 Vdc 110 – 125 Vdc 220 Vdc
+/- 20%
Efficiency 75%
Burden (no load) 150mW
C264/EN UM/E50.5 443

Pin# Signal
1 Digital Input 1+
2 Digital Input 2+
Negative Common
3
Digital Input 1 / 2
4 Digital Input 3+
5 Digital Input 4+
Negative Common
6
Digital Input 3 / 4
7 Digital Input 5+
8 Digital Input 6+
Negative Common
9
Digital Input 5 / 6
10 Digital Input 7+
11 Digital Input 8+
Negative Common
12
Digital Input 7 / 8
13 Digital Input 9+
14 Digital Input 10+
Negative Common
15
Digital Input 9 / 10
Negative Common
18 Digital Input 11 /
12
Negative Common
14
Negative Common
16
444 C264/EN UM/E50.5

5.4.9 DIU211 board - Digital Input Unit

5.4.9.1 Description
The Digital input Unit (DIU211) board provides 16 optically isolated digital inputs arranged by
pairs including:
• 1 common contact for 2 inputs (positive or negative)
• The digital inputs can be used for single or double status, pulse or digital measurement input
on the same unit.
• 4 voltage ranges
• 6 Pre-defined triggering thresholds selected by jumpers
• From 24Vdc to 220Vdc: a peak current (> 27mA) circulates during a short time (±2ms) to
clean external relay’s contacts:
- Figure 132 - DIU211 - peak current
- Figure 133 - DIU211 board
C264/EN UM/E50.5 445


- Figure 134 - DIU211 - voltage jumper
Version Th2 jumper Voltage jumper

24V/Th1 No 24V
48V/Th1 No 48V
110V/Th1 No 110V
220V/Th1 No 220V
110V/Th2 Yes 110V
220V/Th2 Yes 220V
446 C264/EN UM/E50.5

Nominal voltage
24 Vdc 48 - 60 Vdc 110 – 125 Vdc 220 Vdc
+/- 20%
characteristics Value / Range
Threshold pick
up (set) 1 (see V >10 Vdc V >17.4 Vdc V > 50 Vdc V > 77 Vdc
note)
Threshold drop
off (reset) 1 (see V < 7.5Vdc V <11Vdc V < 29Vdc V < 73Vdc
note)
Threshold pick
up (set) 2 (see - - V > 77 Vdc V > 155 Vdc
note)
Threshold drop
off (reset) 2 (see - - V < 73Vdc V< 140 Vdc
note)
Inrush current 30mA for ±2ms
Minimum
continuous 1.9mA@110Vdc
2.6mA@24Vdc 2.2mA@48Vdc 1mA@220Vdc
current (per 1.5mA@125Vdc
active input)
Maximum
continuous 2.9mA@110Vdc
3.6mA@24Vdc 3.4mA@48Vdc 2.3mA@220Vdc
current (per 2.8mA@125Vdc
active input)
Board burden 210mW (+10mW per activated input)
NOTE: Chose either threshold 1 or 2 and set jumper “Th2” accordingly.
C264/EN UM/E50.5 447

Pin# Signal
1 Digital Input 1-
2 Digital Input 2-
Common Digital Input
3
1/2
4 Digital Input 3-
5 Digital Input 4-
6
3/4
7 Digital Input 5-
8 Digital Input 6-
9
5/6
10 Digital Input 7-
11 Digital Input 8-
12
7/8
13 Digital Input 9-
14 Digital Input 10-
15
9 / 10
18
11 / 12
21
13 / 14
24
15 / 16
448 C264/EN UM/E50.5

5.4.10 CCU200 board - Circuit breaker Control Unit

5.4.10.1 Description
The Circuit breaker Control Unit (CCU200) board provides 8 digital inputs (8 DI with one common
for 2DI) and 4 double pole outputs (4 DO) using integrated relays.
Inputs specification:
• optically isolated and arranged by pairs
• polarized, the common point is the negative input
• protected against polarity reversal.
• 5 voltage versions
Outputs specification:
• The two pairs of double poles switching relays have normally open (NO) contacts arranged as
presented below:
- Figure 135 - CCU200 - double pole outputs

• Nominal operating voltage range from 24V to 250 VDC / 230 VAC
C264/EN UM/E50.5 449

- Figure 136 - CCU200 board

Variant A01 A02 A03 A04 A07

DI
Operating
nominal 110 – 125 110 – 125 Vdc
24 Vdc 48 – 60 Vdc 220 Vdc
voltage +/- Vdc 80%th
20%
Triggering
threshold pick 10 Vdc 18 Vdc 50 Vdc 108 Vdc 86 Vdc
up (set)
Triggering
threshold drop 5 Vdc 13 Vdc 34 Vdc 63 Vdc 67 Vdc
off (reset)
450 C264/EN UM/E50.5

Variant A01 A02 A03 A04 A07

5 mA @ 48 2,5 mA @ 110 3,4 mA @
Maximum input 3,5 mA @ 24 Vdc Vdc 2 mA @ 200 110Vdc
current Vdc 6,8 mA @ 60 3 mA @ 125 Vdc 5,4mA @ 132
Vdc Vdc Vdc
DO
Nominal
Operating 24 to 250 Vdc or 230 Vac 50/60 Hz
voltage ranges
Carry current
8A
(max)
Current 30 A (during 500 ms)

overload 250 A (during 30 ms)
Making
Max make current for 4s max = 15 A
capacity

Max Breaking
10000 operations
Full load / Duty cycle: 1.5 s ON - 5 s OFF. The contact resistance stays under
250 mΩ.
Dielectric
withstand
across 1 kV rms AC for 1 minute
normally open
contacts
Output burden 400 mW per activated relay
Board burden 400 mW
C264/EN UM/E50.5 451

Pin# Signal
1 Digital Input 1+
2 Digital Input 2+
Common Digital
3
Input 1 / 2
4 Digital Input 3+
5 Digital Input 4+
Common Digital
6
Input 3 / 4
7 Digital Input 5+
8 Digital Input 6+
Common Digital
9
Input 5 / 6
10 Digital Input 7+
11 Digital Input 8+
Common Digital
12
Input 7 / 8
13 Digital Output 1 B
14 Digital Output 1 A
Common Digital
15
Output 1 - 2 A
Common Digital
18
Output 1 - 2 B
Common Digital
21
Output 3 – 4 A
Common Digital
24
Output 3 - 4 B
452 C264/EN UM/E50.5

5.4.11 CCU211 board – Circuit breaker Control Unit (multi-voltages)

The Circuit breaker Control Unit (CCU211) board provides 8 optically isolated digital inputs
arranged by pairs and 4 double pole outputs using integrated relays.
Inputs specification:
• 1 common contact for 2 inputs (positive or negative)
• The digital inputs can be used for single or double status, pulse or digital measurement input
on the same unit.
• 4 voltage ranges
• 6 Pre-defined triggering thresholds selected by jumpers
• From 24Vdc to 220Vdc: a peak current (> 27mA) circulates during a short time (±2ms) to
clean external relay’s contacts:
- Figure 137 - CCU211 - peak current
Outputs specification:
• The two pairs of double poles switching relays have normally open (NO) contacts arranged as
presented below:
C264/EN UM/E50.5 453

- Figure 138 - CCU211 - double pole outputs

• Nominal operating voltage range from 24V to 250 VDC / 230 VAC
- Figure 139 - CCU211 board

454 C264/EN UM/E50.5

- Figure 140 - CCU211 - voltage jumper
Version Th2 jumper Voltage jumper

24V/Th1 No 24V
48V/Th1 No 48V
110V/Th1 No 110V
220V/Th1 No 220V
110V/Th2 Yes 110V
220V/Th2 Yes 220V
Nominal voltage
24 Vdc 48 - 60 Vdc 110 – 125 Vdc 220 Vdc
+/- 20%
DI
Threshold pick
up (set) 1 (see V >10 Vdc V >17.4 Vdc V > 50 Vdc V > 77 Vdc
note)
Threshold drop
off (reset) 1 (see V < 7.5 Vdc V <11 Vdc V < 29 Vdc V < 73 Vdc
note)
Threshold pick
up (set) 2 (see - - V > 77 Vdc V > 155 Vdc
note)
Threshold drop
off (reset) 2 (see - - V < 73 Vdc V< 140 Vdc
note)
C264/EN UM/E50.5 455

Nominal voltage
24 Vdc 48 - 60 Vdc 110 – 125 Vdc 220 Vdc
+/- 20%
Inrush current 30mA for ± 2ms
Minimum 1.9 mA @ 110

continuous Vdc
2.6 mA @ 24 Vdc 2.2mA @ 48 Vdc 1 mA @ 220 Vdc
current (per 1.5 mA @ 125
active input) Vdc
Maximum 2.9 mA @ 110

continuous Vdc 2.3 mA @ 220
3.6 mA @ 24 Vdc 3.4 mA @ 48 Vdc
current (per 2.8 mA @ 125 Vdc
active input) Vdc
DO
Nominal
Operating 24 to 250 Vdc or 230 Vac 50/60Hz
voltage range
Carry current
8A
(max)
Current overload

Max Breaking
10000 operations
Full load / Duty cycle: 1.5 s ON - 5 s OFF. The contact resistance stays
under 250 mΩ.
Dielectric
withstand across
1 kV rms AC for 1 minute
normally open
contacts
Burden 185 mW
NOTE: Chose either threshold 1 or 2 and set jumper “Th2” accordingly.
456 C264/EN UM/E50.5

Pin# Signal
1 Digital Input 1
2 Digital Input 2
Common Digital
3
Input 1 / 2
4 Digital Input 3
5 Digital Input 4
Common Digital
6
Input 3 / 4
7 Digital Input 5
8 Digital Input 6
Common Digital
9
Input 5 / 6
10 Digital Input 7
11 Digital Input 8
Common Digital
12
Input 7 / 8
Common Digital
15
Output 1/2 A
Common Digital
18
Output 1/2 B
Common Digital
21
Output 3/4 A
Common Digital
24
Output 3/4 B
C264/EN UM/E50.5 457

5.4.12 DOU201 board - Digital Output Unit

The Digital Outputs Unit (DOU201) board provides 10 isolated digital outputs using integrated
relays including:
• 8 single pole relays NO (with one normally open contact)
• 2 single pole relays CO (with one normally open and one normally closed contacts)
- Figure 141 - DOU201 board


Nominal Operating voltage
24 to 250 Vdc or 230 Vac 50/60Hz
ranges
Making capacity 5A
Current overload
458 C264/EN UM/E50.5



Max Breaking capacity 1250 VA on inductive load (cos φ = 0.7)
10000 operations
Full load / Duty cycle: 1.5 s ON - 5s OFF. The contact resistance

stays under 250 mΩ.
Dielectric withstand across
normally open contacts
Burden 250 mW + 220 mW per activated relay
C264/EN UM/E50.5 459

Pin# Signal
1 DO 1 +
2 DO 1 -
3 DO 2 +
4 DO 2 -
5 DO 3 +
6 DO 3 -
7 DO 4 +
8 DO 4 -
9 DO 5 +
10 DO 5 -
11 DO 6 +
12 DO 6 -
13 DO 7 +
14 DO 7 -
15 DO 8 +
16 DO 8 -
17 /
18 /
DO 9 – NO
19
contact
DO 9 – NC
20
contact
21 Common DO 9
DO 10 – NO
22
contact
DO 10 – NC
23
contact
24 Common DO 10
5.4.13 AIU211 board - DC Analog Input Unit

The Analogue input module (AIU211) has 8 isolated Analogue Inputs.
Analogue inputs (AI) are current DC signals delivered by transducers. Each AI can be software-
configured for a current input range (among five ranges).
You can set the ranges during the configuration phase.
460 C264/EN UM/E50.5

- Figure 142 - AIU211 board


± 1 mA
± 5 mA
Current Input range ± 10 mA
± 20 mA
4-20 mA
Accuracy 0,1% (full scale at +25°C )
Sampling period 100 ms
Common mode rejection
> 100 dB
ratio (CMMR) 50Hz, 60Hz
Serial mode rejection ratio
> 40 dB
(SMMR)
Temperature Drift 30 ppm/°C (0°C to +70°C)
Current input impedance 75 Ω
burden 1.1 W
C264/EN UM/E50.5 461

Pin# Signal
1 AI 5+ (current)
2 AI 5- (current)
3 AI 1+(current)
4 AI 1-(current)
5 Not Connected
6 Ground
7 AI 6+ (current)
8 AI 6- (current)
9 AI 2+ (current)
10 AI 2- (current)
11 Not Connected
12 Ground
13 AI 7+ (current)
14 AI 7- (current)
15 AI 3+ (current)
16 AI 3- (current)
17 Not Connected
18 Ground
19 AI 8+ (current)
20 AI 8- (current)
21 AI 4+ (current)
22 AI 4- (current)
23 Not Connected
24 Ground
5.4.14 AOU200 board – Analog Output Unit

The AOU200 board provides 4 analog current outputs. Each output is associated to a Read Inhibit
relay, closed when read is allowed.
The outputs are powered using an external power supply. The external power supply has to
provide a regulated voltage of +48V (+/- 5%).
462 C264/EN UM/E50.5

Each AO can be software-configured for a current input range (among five ranges).
Output management can be configured by software allowing two modes : either output current
maintained or pulse.
The AOU offers a watchdog relay contact (NO relay) with the following management:
Watchdog relay opens when:

• The external power supply is off
• The C264 is not operational or is powered off (no communication with the CPU board)
• An AOU internal fault is present
- Figure 143 - AOU200 board

C264/EN UM/E50.5 463


burden 700mW
External power supply requirements
Voltage/Accuracy 48V regulated +/-5%
power 10W (per AOU board)
Analog outputs
Time to new value output
120 ms
stable
± 5 mA 4 kΩ
Maximum
± 10 mA 2 kΩ
impedance
± 20 mA 1 kΩ
accuracy 0.1% full scale @25°C
Maximum drift <100ppm/°C
Watchdog and read inhibit relays
Maximum switching
30 Vdc or 250 Vac
voltage
Current overload
50 W on resistive load,
Max Breaking capacity 2000 VA on resistive load
10000 operations on resistive load at 250 VAC, 8 A

Operating time < 7ms
Output burden 245mW per activated relay
464 C264/EN UM/E50.5

Pin# Signal
External power
1
supply +48V
2 /
External power
3
supply (0V)
4 /
5 WDOG+
6 WDOG-
7 /
READ INHIBIT
8
AO n° 1+
READ INHIBIT
9
AO n° 1-
READ INHIBIT
10
AO n° 2+
READ INHIBIT
11
AO n° 2-
READ INHIBIT
12
AO n° 3+
READ INHIBIT
13
AO n° 3-
READ INHIBIT
14
AO n° 4+
READ INHIBIT
15
AO n° 4-
16 /
17 AO n° 1+
18 AO n° 1-
19 AO n° 2+
20 AO n° 2-
21 AO n° 3+
22 AO n° 3-
23 AO n° 4+
24 AO n° 4-
C264/EN UM/E50.5 465

5.4.15 - AC Analog Input Unit + DSPIO
The Transducerless Measurement Unit includes the following features:
• 4 measurement Current Transformers (4 CT) inputs, range 1 or 5 amperes, selectable by
jumper
• 4 measurement Voltage Transformers (4 VT) inputs, range (VN): 57.73 Vrms to 130 Vrms
• Frequency operating range: 50 or 60 Hz ± 10%
NOTE: The TMU210 board is necessary used in association with the DSP211 board.
- Figure 144 - TMU210 board

Current input range (1A / 5A) for N, A, B and C is selected thanks to jumpers:
5 A selection
1 A selection
5.4.15.3 technical characteristics

Connector Midos 28 pins
466 C264/EN UM/E50.5


VT measurements:
nominal AC voltage (Vn) 57.7 to 130 V rms
range
CT measurements:
1 A or 5 A
nominal current (In)
Current overload, not 30 A rms (30 In during 10 s)
measurable with no
destruction, for In=1A 100 A rms (100 In during 1 s)

measurable with no
Nominal Frequency (Fn) 50 or 60 Hz

Frequency operating range 45 to 65 Hz
Voltage accuracy +/- 2 % (see Conditions)
Current accuracy +/- 2 % (see Conditions)
Frequency accuracy +/- 0.01 Hz (see Conditions)
Phases-shift accuracy +/- 2 ° (see Conditions)
Harmonics H10
Conditions: The accuracy applies to the temperature operating range of MiCOM C264 and is
related to the pair TMU210 + DSPIO
Measurable current range Measurable current range

TMU210 variante
(In = 1 A) (In = 5 A)
4 CT:
4 CT:
• Steady state: 0.5 to 20 Arms (4
• Steady state: 0.1 to 4 Arms (4 In)
A01 In)
• Fault current: 0.1 to 40 Arms (40
• Fault current: 0.5 to 200 Arms
In)
(40 In)
3 CT:
3 CT:
• Steady state: 0.5 to 20 Arms (4
• Steady state: 0.1 to 4 Arms (4 In)
In)
• Fault current: 0.5 to 200 Arms
A02 In)
(40 In)
1 CT (earth current input):
In)
In)
C264/EN UM/E50.5 467

Measurable current range Measurable current range

TMU210 variante
(In = 1 A) (In = 5 A)
3 CT: 3 CT:
• Steady state: 0.1 to 4 Arms (4 In) • Steady state: 0.5 to 20 Arms (4
• Fault current: 0.1 to 40 Arms (40 In)
A03 In) • Fault current: 0.5 to 200 Arms

(40 In)
• Fault current: 0.002 to 1 Arms 1 CT (earth current input):
(In) • Fault current: 0.01 to 5 Arms (In)
4 CT (earth current input): 4 CT (erth current input):

A04 • Fault current: 0.01 to 8 Arms (8 • Fault current: 0.05 to 40 Arms (8
In) In)
468 C264/EN UM/E50.5

Pin# Signal
1 Not connected
2 Not connected
3 Current Input 1A or 5A- N-
4 Current Input 1A or 5A – N+
5 Not connected
6 Not connected
7 Current Input 1A or 5A – C-
8 Current Input 1A or 5A – C+
9 Not connected
10 Not connected
11 Current Input 1A or 5A – B-
12 Current Input 1A or 5A – B+
13 Not connected
14 Not connected
15 Current Input 1A or 5A – A-
16 Current Input 1A or 5A – A+
17 Not connected
18 Not connected
19 Not connected
20 Not connected
21 Voltage Input – U1
23 Voltage Input – V1
25 Voltage Input – W1
27 Voltage Input – N1
5.4.16 DSP211 board
C264/EN UM/E50.5 469

The DSP211 module is a daughter board connected to the CPU275 board dedicated to the
Circuit-breaker Protection feature management. The board is mated with the CPU but uses an
additional slot.
It provides:
• 4 optically isolated Inputs (with 1 common for 2 x DI) available in 4 ranges
• 5 Digital Outputs (3 Independent TRIP output contacts) using relays
NOTE: The DSP211 board is delivered in association with the TMU210 board only.
- Figure 145 - DSP211 board

Not available.

characteristic Value / Range
DI
470 C264/EN UM/E50.5


characteristic Value / Range
Operating
nominal voltage 24 Vdc 48 – 60 Vdc 110 – 125 Vdc 220 Vdc
+/- 20%
Triggering
threshold pick up 19,2 Vdc 38,4 Vdc 88 Vdc 176 Vdc
(set)
Triggering
threshold drop off 7,2 Vdc 14,4 Vdc 33 Vdc 66 Vdc
(reset)
Maximum input 21,7 mA @ 110 1, 5mA @ 220
3,5 mA @ 24 Vdc 4 mA @ 48 Vdc
current Vdc Vdc
DO
Nominal
Operating 24 to 250 Vdc or 230 Vac 50/60Hz
voltage ranges
Carry current
8A
(max)
Current overload
Making capacity Max make current for 4 s max = 15A

Max Breaking
10000 operations
Full load / Duty cycle: 1.5 s ON - 5 s OFF. The contact resistance stays
under 250 mΩ.
Dielectric
withstand across
1,5 kV rms AC for 1 minute on trip relays
normally open
contacts
Board burden 600 mW
C264/EN UM/E50.5 471

Pin# Signal
1 Input BLOCKING +
2 Common BLOCKING
3 Input SELECTIVITY +
4 Input 3 (not used)
Common SELECTIVITY and
5
Common Input 3
6 Input COLD LOAD START +
7 Input DISTURBANCE START +
Common COLD LOAD START
8
Common DISTURBANCESTART
9 Output Close CB Contact K5/1+
10 Output Close CB Contact K5/1-
11 Output Close CB Contact K5/2+
12 Output Close CB Contact K5/2-
Output 50BF Breaker Failure
13
Contact K4/1+
14
Contact K4/1-
15
Contact K4/2+
16
Contact K4/2-
17 Not connected
18 Output CB Open / TRIP Contact C +
19 Output CB Open / TRIP Contact C -
20 Output CB Open / TRIP Contact B +
21 Output CB Open / TRIP Contact B -
22 Output CB Open / TRIP Contact A +
23 Output CB Open / TRIP Contact A -
24 Output CB Open / TRIP Contact A -
5.4.17 TMU220 board - AC Analog Input Unit

The Transducerless Measurement Unit includes the following features:
472 C264/EN UM/E50.5

• 4 measurement Current Transformers (4 CT) inputs, range 1 or 5 amperes
• 5 measurement Voltage Transformers (5 VT) inputs, range (VN): 57.73 Vrms to 500 Vrms
• Frequency operating range: 50 or 60 Hz ± 10%
NOTE: The TMU220 board is necessary used in association with the DSP200 board.
- Figure 146 - TMU220 board

Not available.

Connector Midos 28 pins
VT measurements:
nominal AC voltage (Vn) 57.7 to 500 V rms
range
Measurable voltage range 7 to 577 V rms
C264/EN UM/E50.5 473


Voltage overload, with no
880 V rms (during 10 s)
destruction
CT measurements: 1A
nominal current (In) 5A
Mesurable current range
0.2 to 4 A rms (4 In)
for In=1 A
Mesurable current range
0.2 to 20 A rms (4 In)
for In=5 A
measurable with no

measurable with no
Nominal Frequency (Fn) 50 Hz or 60 Hz

Frequency operating range 45 to 66 Hz
Mesurable frequency 45 to 55 Hz (Fn = 50 Hz) or

ranges (50/60 Hz) 54 to 66 Hz (Fn = 60 Hz)
0.3 % 45 V (< 20 V),
0.2 % 45 V (20 V to 45 V),

Voltage accuracy
0.2 % measurement (45 V to 200 V),
0.3 % measurement (200 V to 550 V)

0.2 % In (0.2 A to In),
Current accuracy
0.2 % measurement (In to 4 In)
Active and reactive Power
0.5 % (φ = 0 °) – see Note
accuracy
Frequency accuracy +/- 0.01 Hz (see Conditions)
Phase-shift accuracy +/- 1 ° (see Conditions)
Overall heat transfer
+/- 10ppm/°C (-25 °C to +70 °C)
coefficient
Harmonics H15
Conditions: The accuracy applies to the temperature operating range of MiCOM C264 and is
related to the pair TMU200 + DSPIO
NOTE: The active and reactive power accuracy is not applicable in these cases:
474 C264/EN UM/E50.5

Operating range Active / Reactive Power Value

1A < 0.72 W / VA
5A < 3.2 W / VA
C264/EN UM/E50.5 475

Pin# Signal
1 Current Input 5A - N1
2 Current Input 5A – N2
5 Current Input 5A – C1
9 Current Input 5A – B1
13 Current Input 5A – A1
17 NC
18 NC
19 Voltage Input – X1
20 Voltage Input – X2
476 C264/EN UM/E50.5

5.4.18 DSP200 board

The DSP200 board is a daughter board connected to the CPU275 board. The board is mated with
the CPU and does not use an additional slot.
- Figure 147 - DSP200 board

Not available.

Burden 2,1 W

Not available.
5.4.19 SBU200 board – Smart terminal Block Unit

The SBU200 board is an 8 ports acquisition unit for interfacing with Smart Terminal Blocks.
Connection to SMTB is realized through a dedicated RJ45 connector which supports an individual
12V power supply and a serial Rx/Tx communication.
The power supply is protected against short-circuit.
Note : RJ45 is dedicated to SMTB link : do not connect on ethernet network.
A green LED (on each port) signals that a SMTB is connected.
C264/EN UM/E50.5 477

- Figure 148 - SBU200 board

Not available (plug & play facilities).
Characteristics Value / Range

Additional consumption for each SMTB connected (refer to Smart
Burden
terminal block I/O documentation ref R9)
Connector type RJ45
Twisted pair shielded (FTP, STP, S/FTP) cable rated category 5
Recommended cable type
with standard RJ45 connectors.
478 C264/EN UM/E50.5

5.4.19.4 Rear panel connectors
Overview Port pins
RJ45
pin signal
1 TXY
2 TXZ
3 RXA
4 Power supply +
5 Power supply +
6 RXB
7 Power supply -
8 Power supply -
5.4.20 SBU400 board – optical Smart terminal Block Unit

5.4.20.1 description
The SBU400 board is an acquisition unit for 8 Smart Terminal Blocks with an optical fiber interface
(ST connector). The two optical ports are dedicated to the SMTB Fiber Optic converter (SMTB-
FO) connection.
NOTE: optical ports are dedicated to SMTB link : do not connect on ethernet network.
C264/EN UM/E50.5 479

- Figure 149 - SBU400 - connection with Smart Terminal Blocks
- Figure 150 - SBU400 board

Not available (plug & play facilities).
480 C264/EN UM/E50.5

Characteristics Value / Range

Burden 0,70 W
Connector type ST
Wavelength 1300nm (typical)
Fiber type Multimode glass fiber 62.5/125 mm or 50/125 mm
7,6 dBm 62.5/125 mm fiber
Optical link budget
3,1 dBm 50/125 mm fiber
- Figure 151 - SBU400 - rear panel connector
5.4.21 SWU20x board - Ethernet-based SWitch Unit

The SWU20x Ethernet switch unit is available in two versions:
C264/EN UM/E50.5 481

• The SWU200 board offers 4 electrical ports 10/100BaseT RJ45:
- Figure 152 - SWU200 board

• The SWU202 board offers 4 electrical ports 10/100BaseT RJ45 and 2 optical ports with ST
connectors for multi-mode fiber:
- Figure 153 - SWU202 board
There is a C/O relay for optical links watching of SWU202. The relay is operated if the 2 links are
active. In case of fault on any of the two links, the relay is released.
This relay is not operational for the SWU200.

Not available.

SWU200
Burden 6 W – may vary depending on number of links used
482 C264/EN UM/E50.5


SWU200/SWU202
Ethernet connection RJ45 10/100 Mbps
SWU202
Burden 5.9 W
Optical ethernet
100 Mbps
connection
Wavelenght 1300 nm (typical)
Fiber type multimode
Maximum fiber length 2 km
Optical supervisor relay
24 to 250 Vdc or 230 Vac 50/60 Hz
ranges
Current overload

10000 operations
Full load / Duty cycle: 1.5 s ON - 5 s OFF. The contact resistance

C264/EN UM/E50.5 483

SWU200 Overview Port pins
RJ45
pin signal
1 Rx+
2 Rx-
3 Tx+
4 Not used
5 Not used
6 RXB
7 Not used
8 Not used
484 C264/EN UM/E50.5

RJ45
pin signal
1 Rx+
2 Rx-
3 Tx+
4 Not used
5 Not used
6 Tx-
7 Not used
8 Not used
Optical power fault relay

pin signal
1 NC contact
2 common
3 NO contact
5.4.22 SWR212 board - Ethernet-based SWitch Redundant Unit

This board in an Ethernet switch with 4 electrical ports 10/100 BaseT RJ45 and 2 multi-mode
optical ports with ST connectors dedicated to a dual ring topology.
C264/EN UM/E50.5 485

- Figure 154 - SWR212 - dual ring topology
The SWR212 switch is SNMP managed (it integrates an SNMP server) and it can be remotely
accessed from SNMP “client”.
The optical ring is monitored. If one link comes down the default is announced by one relay
contact.
- Figure 155 - SWR212 board

Network board address is configurable through jumpers.
486 C264/EN UM/E50.5

- Figure 156 - SWR212 - address jumpers

SWU200
Burden 4.25W – may vary depending on number of links used
RJ45 connection crossover
Cable type
Optical ethernet
100 Mbps
connection
Wavelength 1300 nm (typical)
Fiber type Multimode glass fiber
Maximum fiber length See example below
Maximum number of
127
repeaters on the ring
24 to 250 Vdc or 230 Vac 50/60 Hz
ranges
C264/EN UM/E50.5 487


Current overload

10000 operations

5.4.22.4 Optical fiber budget calculations

Optical power is expressed in Watts. However, the common unit of power measure is the dBm
and defined by the following equation: Power (dBm) = 10 log Power (mW) / 1 mW.
The following example shows the calculation of the maximum range between two SWR212
repeaters.
Fiber characteristic Value / Range

Fiber 1300nm - 62.5/125 mm 1300nm - 50/125 mm
Output optical power - 19 dBm to -14 dBm - 22.5 dBm to -14 dBm
Input Optical Power Minimum - 31 dBm
Input optical Power maximum -14 dBm
Example between two repeaters with a fiber 1300nm - 62.5/125 mm:

Link budget 12 dBm
Connector loss (2) 0.8 dBm
Safety Margin 4 dBm
Allowed link attenuation 6.4 dBm
Typical cable attenuation 1 dBm/km
Maximum range 6.4 km
The values given above are only approximate ones. Always use cable and connector losses as
specified by the manufacturer.
488 C264/EN UM/E50.5

auto-crossover, 2 possible wirings for

RJ45
RJ45 RJ45
pin signal pin signal
1 Rx+ 1 Tx+
2 Rx- 2 Tx-
3 Tx+ 3 Rx+
4 Not used 4 Not used
6 Tx- 6 Rx-

pin signal
1 Default Rp-Ts – open if faulty
2 Common
3 Default Rs-Tp – open if faulty
NOTE: relays are NC - if the board is not

powered the link is tagged as OK
5.4.22.6 Wiring between two SWR212
- Figure 157 - SWR212 - wiring between two SWR212
C264/EN UM/E50.5 489

RECOMMENDATION: Wiring
Due to the proximity of the port 1 Ethernet connector, it is strongly recommended to visually
check the “Fault signal connector” connections before any hand manipulation of the Ethernet
connectors.
Pay attention during the wiring phase to avoid damaging the cable’s isolation.
5.4.23 SWS212 board - Ethernet-based SWitch RSTP compatible

The SWS212 board is an Ethernet switch dedicated to simple star architecture. It is RSTP
compatible to provide redundancy.
It offers 4 electrical ports 10/100 BaseT RJ45 and 2 optical ports with ST connectors for multi-
mode fiber.
- Figure 158 - SWS212 - RSTP architecture
The SWS212 switch is SNMP managed (it integrates an SNMP server) and it can be remotely
accessed from SNMP “client”.
The optical links are monitored. If one link comes down or if the link doesn’t carry RSTP frames
the default is announced by switching the corresponding relay contact.
490 C264/EN UM/E50.5

- Figure 159 - SWS212 board

Network board address is configurable through jumpers.
- Figure 160 - SWS212 - address jumpers
C264/EN UM/E50.5 491

5.4.23.3 technical characteristics

SWU200
Burden 4.25W – may vary depending on number of links used
Cable type
Optical ethernet
100 Mbps
connection
Fiber type Multimode glass fiber
12 dBm for a 62.5/125 mm fiber
Optical link budget
8.5 dBm for a 50/125 mm fiber
24 to 250 Vdc or 230 Vac 50/60 Hz
ranges
Current overload

10000 operations

Fiber characteristic Value / Range

Fiber 1300nm - 62.5/125 mm 1300nm - 50/125 mm
Output optical power - 19 dBm to -14 dBm - 22.5 dBm to -14 dBm
Input Optical Power Minimum - 31 dBm
Input optical Power maximum -14 dBm
492 C264/EN UM/E50.5


RJ45
RJ45 RJ45
1 Rx+ 1 Tx+
2 Rx- 2 Tx-
3 Tx+ 3 Rx+
6 Tx- 6 Rx-

pin signal
1 Default link A if open
2 Common
3 Default link B if open
NOTE: relays are NC - if the board is not

powered the link is tagged as OK
5.4.24 REU20X board – Redundant Ethernet-Unit – PRP/HSR/RSTP

The REU20x board offers 3 full Duplex Ethernet 100Mbps ports:
• 1 internal port RJ45 intended to the Host network (Interlink)
• 2 redundant combo ports, each combo is composed by an optical and a RJ45 interface.
Inside the combo if both ports are connected, priority is always given to the SFP port.
REU20x board implements redundant protocols defined by the IEC 62439-3 (PRP/HSR):
• PRP for independent LAN attachment like dual star network topology
• HSR for dependent LAN attachment like dual ring network topology
REU20x board implements RSTP protocol
C264/EN UM/E50.5 493

- Figure 161 - REU20X board
Number Options
Multimode : with 2 Eth. Ports (HSR/PRP/RSTP) + 10/100BaseT
REU202- V2
RJ45 Eth. Port with 2 SFP Connectors multimode
SingleMode : with 2 Eth. Ports (HSR/PRP/RSTP) + 10/100BaseT
REU204- V2
RJ45 Eth. Port with 2 SFP Connectors Single mode
REU-V2 : with 2 Eth. Ports (HSR/PRP/RSTP) + 10/100BaseT
REU-V2 RJ45 Eth. Port. SFP Fiber Optic interface not provided (separate
accessories)

Burden 3W – may vary depending on number of links used
RJ45 ports
Ethernet connection RJ45 100 Mbps
Cable type
Maximum cable length 25m
SFP module multi-mode
494 C264/EN UM/E50.5


Fiber type Multimode glass fiber 62.5/125µm
Connector type Duplex LC
Optical ethernet
100 Mbps
connection
optical input power
-31 dBm
maximum
Optical output power -20 dBm to -15 dBm
SFP module single-mode
Fiber type single mode glass fiber 9/125µm
Connector type Duplex LC
Optical ethernet
100Mbps
connection
Wavelength 1310nm (typical)
optical input power
-30 dBm
maximum
Optical output power -15 dBm to -8dBm
24 to 250 Vdc or 230 Vac 50/60 Hz
ranges
Current overload

10000 operations

C264/EN UM/E50.5 495


RJ45
RJ45 RJ45
1 Rx+ 1 Tx+
2 Rx- 2 Tx-
3 Tx+ 3 Rx+
6 Tx- 6 Rx-

pin signal
1 Default link A if closed
2 Common
3 Default link B if closed
496 C264/EN UM/E50.5

5.5 Terminal technical data

5.5.1 PC Maintenance Interface
• DIN 41652 connector, type female D-Sub, 9-pin, installed on the front panel
• A direct wired cable is required.
5.5.2 Ethernet LAN (installed on the CPU275 board)

• Two of the RJ-45 female connector, 8-pin for the 10/100Base-T self-negotiation
5.5.3 IRIG-B interface (standard NF S 87-500, May 1987), installed on the

CPU275 board
• BNC plug
• Modulated amplitude, 1 kHz carrier signal
• Compatible with IRIG B122 code
5.5.4 Conventional communication links

• M3 threaded terminal ends, self-centering with wire protection for conductor cross sections
from 0.2 to 2.5 mm² for BIU241 board
• DIN 41652 connector; type D-Sub, 9-pin, installed on the CPU275 board.
• Optical fibers through ECU200 (external RS 232 / optical converter): optical plastic fiber
connection in agreement with IEC 874-2 or DIN 47258 or ST ® glass optical fiber connection
(ST ® is a registered trademark of AT&T Lightguide Cable Connectors).
5.5.5 Input /Output or power supply modules

• M3 threaded terminal ends, self-centring with wire protection for conductor cross sections
from 0.2 to 2.5 mm² for these boards:
AIU211
AOU200
BIU241
CCU200, CCU211
DIU200, DIU211
DOU201
DSPIO211
• The I/O boards and BIU241 include a 24-pin, 5.08 mm pitch male-connector.
5.5.6 Current-measuring and Voltage-measuring inputs

• M5 threaded terminal ends, self-centering with wire protection for conductor cross sections
between 2.5 and 4 mm² for the TMU board.
• The TMU board includes this connector. MIDOS 28 terminal block.
C264/EN UM/E50.5 497

6 Human Machine Interface MiCOM C264 - User Manual
6 Human Machine Interface

6.1 The Front Panel 500

6.1.1 Overview 500
6.1.2 LED’s management 501
6.1.2.1 First LEDs 501
6.1.2.2 Other LEDs 502
6.1.2.3 Example: AVR dedicated MiCOM C264 503
6.1.3 Configuration data 504
6.1.3.1 General display management 505
6.1.3.2 Language support 508
6.1.3.3 Time and date displaying 508
6.1.3.3.1 Time 508
6.1.3.3.2 Date 508
6.1.3.3.3 State of date and time 508
6.1.3.4 Bay panels 509
6.1.3.4.1 Case 1: display for specific CT/VT measurement 510
6.1.3.4.2 Case 2: other measurements 511
6.1.3.4.3 State sub-panel 512
6.1.3.4.4 Measurements, counters and TPI sub-panel 513
6.1.3.4.4.1 Display of measurements 514
6.1.3.4.4.2 Display of counters 514
6.1.3.4.4.3 Display of TPI 514
6.1.3.4.5 Control sub-panel 515
6.1.3.4.6 Interlocking sub-panel 517
6.1.3.5 AVR Panel 518
6.1.3.6 Generic Measurements Panel 520
6.1.3.6.1 Navigation 520
6.1.3.6.2 Main Page 521
6.1.3.6.3 Measurements display 522
6.1.3.6.4 Bargraph MV selection 523
6.1.3.6.5 Secondary pages 524
6.1.3.6.6 Empty pages 524
6.1.3.6.7 Selection persistence 525
6.1.3.6.8 Automatic return to the default panel 525
6.1.3.7 Events panel 525
6.1.3.7.1 Display mechanism for the first page 526
6.1.3.7.2 Display mechanism for an intermediate page: 526
6.1.3.7.3 Display mechanism for the last page: 526
6.1.3.8 Faults panel 527
6.1.3.9 Alarm panel 527
6.1.3.10 Disturbance record panel 529
498 C264/EN UM/E50.5

MiCOM C264 - User Manual 6 Human Machine Interface
6.1.3.11 Configuration panel 530

6.1.3.11.1 Boards panel 531
6.1.3.11.2 External devices panel 532
6.1.3.11.3 Service information panel 534
6.1.3.12 Display of binary input information 535
6.1.3.13 Display of binary output information 536
6.1.3.14 Menu tree 538
6.1.3.14.1 menu tree in operational or simulation mode (example) 539
6.1.3.14.2 menu tree in maintenance mode 540
6.1.3.15 Controls (subject to privilege) 540
6.1.3.15.1 Local / Remote control of bay 541
6.1.3.15.2 Commands of circuit breakers, disconnecting switches and generic devices541
6.1.3.15.2.1 SBO command 541
6.1.3.15.2.2 DE command 542
6.1.3.15.2.3 Interlocking bypass 542
6.1.3.15.2.4 Synchrocheck bypass 542
6.1.3.15.2.5 Interface with the operator on local control panel 543
6.1.3.15.3 Tap changer control request 543
6.1.3.15.5 Data base switch 544
6.1.3.15.6 Reset operating hours 545
6.1.3.15.7 Time and date setting 545
6.1.3.15.8 Manual value change of counters 545
6.1.3.15.9 Acknowledgement of alarms 545
6.1.3.15.9.1 Global acknowledge 546
6.1.3.15.9.2 Alarm per alarm acknowledge 546
6.1.3.15.10 Alarms clearing 546
6.1.3.15.10.1 Global clear 546
6.1.3.15.10.2 Alarm per alarm clear 547
6.1.3.15.11 Activate test mode 547
6.1.3.16 Password management 547
6.2 The Computer Administration Tool (CAT) 550
6.3 Printers 551
6.3.1 Inputs 551
6.3.2 Outputs 551
6.3.3 Printer management 551
6.3.3.1 Header & footer 551
6.3.3.2 Chronology & time stamp 552
6.3.3.3 Printer out of service 552
6.3.3.4 Circular FIFO management 552
C264/EN UM/E50.5 499

6.1 The Front Panel

6.1.1 Overview
The MiCOM C264 front panel exists in two versions:
• A simple front panel with LEDs, L/R push-button and the serial link (GHU21x)
• A graphical front panel with LEDs, L/R push-button, the Local Control Display and the serial
link ( GHU20x)
- Figure 162 - MiCOM C264 front panel GHU20x
The front panel is detachable up to 5 meters from the base case using a specific front panel
(GHU22x)
From the graphical panel, the operator can

• Control:
circuit breaker (open, close)
disconnecting switch (open, close)
transformer (raise, lower, go to min, go to max)
generic command (start, stop or open/close)
setpoint
bay mode (local/remote)
computer mode (operational, test, maintenance)
counters value
• Switch the database
• Modify Settings by menu tree
• Acknowledge and clear alarms
• Suppress datapoints
• Display:
500 C264/EN UM/E50.5

Device position
Alarms list
Disturbance record
Configuration
Events list
Fault list
Measurements, counter, and TPI
Physical binary input/output,
Status information
Bay mode (local/remote, SBMC)
Bypass indications
Setting points
Board state
IED state
• Activate LED depending on datapoint status
6.1.2 LED’s management

There are 17 LEDs available; 16 of them are managed by the software. One is directly connected
to the internal power.
6.1.2.1 First LEDs

The first LEDs indicate the MiCOM C264 status information, that is from top to down.
LED LED slow LED fast

Colour LED on LED off
id blinking blinking
There is at least 1
There is at least
minor fault (I/O Test mode
one major fault
1 Red board, commun- No fault
(hardware, enabled
ication to IEDs,
database) (1)
…) (2)
There is at least
All the alarms are All alarms
one not
ac-knowledged, displayed in the
acknowledged
2 Yellow but there is at alarm panel are No alarm
alarm displayed
least one alarm inactive &
in the alarm
still active. (3) acknowledged
panel
Computer in Computer in Computer in
3 Yellow Computer in test
operation maintenance reboot
4 Green Power on Not used Not used Power off
C264/EN UM/E50.5 501

LED LED slow LED fast

Colour LED on LED off
id blinking blinking
Bays managed
All bays All bays
by the computer
managed by the managed by the
5 (4) Red are not in the Not used
computer are in computer are in
same control
LOCAL mode REMOTE
mode
6 Red Global fault (5) Not used Not used No fault at all
(1) Major fault: MiCOM C264 not available due to internal failure (database error, CPU board
failure, …).
(2) A minor fault is a fault causing only the unavailability of a part of the functionality.
(3) When the alarm disappears, the LED returns automatically to OFF.
(4) Assigned by computer only for without LCD panel: GHU2x1 or for an extension
MiCOM C264.
(5) It may be a board fault, an IED fault, a power off, a watchdog issue (DO#0 of BIU board), an
IED or extension disconnected.
6.1.2.2 Other LEDs

Other LEDs’ default assignment:
• LED 7: DIU board fault
• LED 8: AIU board fault
• LED 9: DOU board fault
• LED 10: CCU board fault
• LED 11: AOU board fault
• LED 12: At least one IED is disconnected (mono / main / extension rack)
• LED 13: At least one extension rack is disconnected (main rack)
Connection status with main rack (extension rack)
On the extension racks, these default assignments cannot be modified.
The LEDS 14 to 17 can be used only on the main rack.
Summary table:
502 C264/EN UM/E50.5

Mono rack architecture Multi rack architecture

Extension
Computer Principal Rack
Rack
Simple
Led Graphical Panel Simple Panel Graphical Panel Simple Panel
Panel
1 Assigned
Assigned by Assigned by Assigned by Assigned by
2 by
computer computer computer computer
3 computer
4 Linked to power supply

5 Not Used Not Used Assigned
Assigned by Assigned by
Assigned by Assigned by by
6 computer computer
computer computer computer
7
8
9 Pre- Pre-
Pre- Pre- Pre-
10 defined defined
defined defined defined
11
12 Free Free Free Free
13
14
Not Not
15 Not Not
Used Used Not Used
16 Used Used
17
6.1.2.3 Example: AVR dedicated MiCOM C264

Up to 17 Leds are dedicated to AVR signalling and alarms:
Led # Color Description

01 red Hardware Fault
02 amber
03 amber Maintenance Mode
04 green Power Supply
05 red AVR Mode: MANU
06 red AVR AUTO : OFF
07 red Vn-5%
08 red
09 red Lower Tap Change Order
C264/EN UM/E50.5 503

Led # Color Description

10 red Raise tap Change Order
11 red Loss of Voltage
12 red Abnormal Voltage
13 red End of Tap reached
14 red Low Tap Signal
15 red High Tap Signal
16 red Tap Changer blocked
17 red Tap Changer Fault
6.1.3 Configuration data

The behaviour of the user-configurable LEDs is defined in the computer DataBase.
When using a simple DHMI, the 11 user-configurable LEDs give the status of the associated BI.
Each BI state is displayed using the ON / OFF / BLINKING led state.
When using a graphical DHMI (with LCD), the 13 user-configurable LEDs can be configured to
have 2 different behaviours:
1. give the status of the associated BI. Each BI state is displayed using the ON / OFF /
BLINKING led state (same way as with a Simple DHMI),
2. provide a way to manage BIs as alarms.
This behaviour 2 is detailed hereafter:

• if the BI is “transient”:
if the BI is SET, the associated LED is ON or Blinking Slow (depends of the DB),
after pressing the button, the LED’s state goes OFF (without any password).
• if the BI is “permanent”:
if the BI is SET, the associated LED is Blinking Slow,
after pressing the button, the LED goes ON (without any password),
if the BI is RESET, the associated LED remains Blinking if the ‘C’ button has not been
pressed or is OFF if it has.
Remarks:
•
The button is used for the navigation in the menu tree. This feature remains and so
alarm acknowledgement will be not allowed from the menu tree.
•
The alarm acknowledgement function is not available with the simple panel (no
button available).
504 C264/EN UM/E50.5

The 11 other LED’s are freely configurable: they can be attached to a datapoint. Furthermore, the
datapoint state is displayed through a led state: on, off, slow blinking, fast blinking.
For a Single Point, the Set / Reset / Invalid (i.e. all other states) can be attached to a LED. For a
Double Point, the Open / Close / Invalid (i.e. all other states) can be attached to a LED.
6.1.3.1 General display management
- Figure 163 - GHU20x - general display
The computer local HMI is composed of several “panels” and one “menu tree”. The panels allow
to display information, the menu tree allows to display and modify computer settings.
There are several panel groups; each group can contain several panels.
The key allows to display the next panel group.
The keys and allows to access to the different panels of a group.
From each panel, the key allows to confirm some actions or to enter to the menu tree
access.
The key is used to cancel some ongoing operations or to go a step back in the menu tree
navigation
For more information on the menu tree refer to section § Menu tree.
List of panel groups
C264/EN UM/E50.5 505

Group Description
Graphical bay panels – one or two panels for each electrical bay with sub-
panels displaying information linked to the displayed bay:
Group 1 • measurements, counters and TPI
• single, double and multiple datapoints status
• controls
Alarm - one panel displays the alarm list and allows acknowledgment and
Group 2
clearing
Generic measurement - one main panel and up to three secondary panels
displaying any measurement acquired by the MiCOM C264. These panels
are different in display format and content from the measurements sub-
Group 3 panels contained within each graphical bay panel. Sub-panels can display
only MVs under the bay linked to its graphical bay panel while these panels
can contain any MV regardless of its source, type or bay as long as it is
managed by the MiCOM C264
AVR - two or three panels
• AVR for 1 transformer:
AVR_VIEW1: large view
AVR_VIEW2: detail and control view

Group 4 • AVR for multiple transformers:
AVR_VIEW1: large view
AVR_VIEW2: detail and control view
AVR_VIEW3: analysis view on the MiCOM C264 (s) managing the

parallel aspects
Group 5 Event - one panel displays the event list
Fault - one panel displays the list of detected faults
• if a hardware fault occurs, the board panel is accessible and shows only
faulty boards
Group 6 • if an IED fault occurs, the IED panel is accessible and shows only
disconnected IEDs
• if one or several IEC 61850 clients are not connected, the number of real
connected clients is displayed against the maximum number of clients
Group 7 Disturbance - one panel displays the header of the disturbance file
Service:
• one panel displays general information
Group 8
• one panel displays the boards state
• one panel to display the IEDs state
506 C264/EN UM/E50.5

Group Description
Physical:
Group 9 • one panel displays the state of the physical inputs
• one panel displays the state of the physical outputs
Banner - one panel displays general information on MiCOM C264 to avoid

Group 10
any mistake
Login & Password - two panels, accessible from several panels and used to
Group 11
select login and enter password
Panel navigation is described as follows:
- Figure 164 - GHU20x - panel navigation
From any panel, a help panel is accessible using the key. From this panel, a new press
on this key allows to display the graphical panel of the first bay in active mode or the service panel
in maintenance mode.
C264/EN UM/E50.5 507

Some of the panels (graphical bay panels, faults, AVR, service, banner) are eligible as start panel
(Refer to the GHU2xx board configuration). If a login panel is required, banner must be the start
panel.
Inactivity panel (screen saver) and delay are configurable (Refer to the GHU2xx board
configuration).
6.1.3.2 Language support

The front panel human interface supports 2 languages that are chosen during configuration
phase. A parameter in the menu tree allows switching between both languages.
The MiCOM C264 Human interface is also available in Chinese language by now. Please, contact
the Schneider Electric’s local support for more information.
6.1.3.3 Time and date displaying

Local HMI displays time, date and state of time and date of the computer.
6.1.3.3.1 Time
Time of day is displayed in all the panels of the LCD. For each panel, time of day is displayed in
the first line of the panel.
The displaying format of the time is THH:MM:SS where T is the time state, HH the hour (0 to 23),
MM the minutes (00 to 59) and SS the seconds (0 to 59).
- Figure 165 - GHU20x - time and date displaying
In the events panel, in the alarms’ panel and in the disturbance records panel, time stamp must be
given at milliseconds. So, the format of time is THH:MM:SS.MMM.
6.1.3.3.2 Date
Date is displayed only in the panel of events and in the panel of alarms. Date is associated with
time for the displaying of each event and each alarm.
3 displaying formats for date are configurable, where DD is the month day (01 to 31), MM the
month (01 to 12) and YY the year (00 to 99):
• DD/MM/YY
• MM/DD/YY
• YY/MM/DD
6.1.3.3.3 State of date and time

The application software of the computer manages the different state of the date and time:
• not synchronized (“*”): the date/time has never been synchronized
• synchronized (“ “): date/time is synchronized
508 C264/EN UM/E50.5

Time, date and state are visible and modifiable in the menu tree. To modify time or date, refer to
chapter"Settings" on page 1008.
6.1.3.4 Bay panels

Graphical representations of bays are visible in panels. Each bay has its own panels (up to 2). Up
to 12 bays can be displayed via the Front Panel of the computer. A maximum of 9 devices can be
displayed on a per panel basis.
All information of these panels is configurable except for the time indication.
- Figure 166 - GHU20x - inter bay panel navigation
When a bay is displayed on two panels, key4 and key3 are used to move from one panel to the
other.
For one bay:
- Figure 167 - GHU20x - bay sub-panel navigation
The information displayed in the bay panel is:
C264/EN UM/E50.5 509

• the bay name (fixed position), 16 characters maximum
• the time (hh:mm:ss) preceded by its state (* means not synchronized)
• the bay graphical representation: the bay is displayed in single-pole presentation. Graphical
pictures are made of bitmaps for devices representation, vertical and horizontal lines and
labels.
• the SBMC mode
• the Local / Remote bay mode
• the synchrocheck bypass activation, if applicable and exists
• the interlock bypass activation (if it exists)
• the command report (fixed position)
• Access to the MSC (Measurements, States, Controls) sub-panels. They can be selected by
pressing for 1 second the button, navigate between M, S and C using the same button
and display one of the sub panel using the button.
• Measurements: up to 4 measurements can be displayed but not at the same time. They are
displayed within the same area one by one. By pressing the and buttons it is possible
to scroll among the 4 configured measurements. Any measurement belonging to the bay can
be configured to be displayed.
Measurement display depends on its type.
- Figure 168 - GHU20x - bay panel structure and information
6.1.3.4.1 Case 1: display for specific CT/VT measurement

This case concerns CT/VT measurement acquired by a TMU board and which type is: Van, Vbn,
Vcn, Vr, Vab, Vbc, Vca, Ia, Ib, Ic or Ir.
In this case, the measurement is displayed in the following way:
510 C264/EN UM/E50.5

• Measurement name area (fixed position): displays the MV short name
• Measurement value area (fixed position): in this case, this area displays the bargraph value
% instead of the value of the MV.
• Measurement bargraph: it can be configured to be displayed either in a vertical position
(VMGA: Vertical Measurement Graphical Area) or in a horizontal position (HMGA: Horizontal
Measurement Graphical Area).
The bargraph represents the ratio between the MV value (after scaling) and the nominal value
which is configured at the TMU board level:
Bargraph value (%) = (MV value / nominal value) x 100
Example:
MV value (“Van”) = 150 V
TMU board “nominal voltage (V)” = 1000 V
Bargraph value = (150/1000) x 100 = 15%
If the MV is a current (e.g. “Ia”) then the nominal value used for the calculation is the “nominal
current (mA)”.
The maximum value of the bargraph can be either 120% or 200% of the nominal value
(configurable per measurement):
- Figure 169 - GHU20x - specific CT/VT measurement display
6.1.3.4.2 Case 2: other measurements

This case concerns CT/VT measurements not listed in Case 1 or any other kind of
measurements.
In this case, the measurement is displayed in the following way:
- Figure 170 - GHU20x - specific standard measurement display
C264/EN UM/E50.5 511

• Measurement name area (fixed position): displays the MV short name
• Measurement value area (fixed position): displays the MV current value displayed on 8
characters for the value itself and 4 more characters are reserved for the unit. The value is
systematically (regardless of its profile) forced to 8 characters which includes sign and
decimal separator. For doing this, zeros are appended to the decimal part until reaching 8
characters. If the value is greater than “99999999”, the value is displayed in scientific
notation.
• Measurement bargraph: the bargraph is not displayed in this case.
6.1.3.4.3 State sub-panel

This panel allows to display the state of the digital datapoints (single points, double points and
multiple points).
- Figure 171 - GHU20x - state sub-panel

1 Bay name: fixed position, 16 characters maximum (Chinese LHMI: only 10 characters)
Three lines are necessary to display any information. An SPS / DPS / MPS is defined by:
- Figure 172 - GHU20x - SPS/DPS/MPS information in state sub-panel
From this panel, the operator can suppress a datapoint.
Hereafter, 2 samples of state sub-panels:
512 C264/EN UM/E50.5

- Figure 173 - GHU20x - sample of state sub-panel
6.1.3.4.4 Measurements, counters and TPI sub-panel

This panel allows displaying the state of the measurement, the counter and the TPI. It is defined
by 3 lists of elements (Measurement, counter and TPI), each list is composed of several pages (3
pieces of information per page).
C264/EN UM/E50.5 513

- Figure 174 - GHU20x - measurements, counters and TPI sub-panel

6.1.3.4.4.1 Display of measurements
Analogue values or digital measurements can be displayed in this panel if defined in database.
The value is displayed with 2 digits after the dot and 5 before.
- Figure 175 - GHU20x - measurement information in measurements, counters and TPI sub-
panel
1 Chinese LHMI: only 10 characters
6.1.3.4.4.2 Display of counters
Counter can be displayed in this panel if defined in database. The value is displayed with 2 digits
after the dot and 5 before.
- Figure 176 - GHU20x - counter information in measurements, counters and TPI sub-panel
The MiCOM C264 LHMI displays 32bits and 64bits counter data.
6.1.3.4.4.3 Display of TPI
TPI can be displayed in this panel if defined in database.
514 C264/EN UM/E50.5

- Figure 177 - GHU20x - TPI information in measurements, counters and TPI sub-panel
Hereafter, 2 samples of measurement sub-panels:
- Figure 178 - GHU20x - sample of measurements, counters and TPI sub-panel
6.1.3.4.5 Control sub-panel

The operator is allowed to control devices from the control sub-panel.
The content of this panel is displayed as follows:
C264/EN UM/E50.5 515

- Figure 179 - GHU20x - control sub-panel

2 Chinese LHMI: only two commands are displayed per page
Each of the commands is displayed as following:
- Figure 180 - GHU20x - command information in control sub-panel

1 Chinese LHMI: the module name is not displayed.
On this panel, the operator selects the chosen command using the key.
Select Before Operate (SBO) and Direct Execute (DE) controls are possible according to the
configuration.
To send a DE control, operator uses keys for OFF order and for ON order.
To send a SBO control, operator uses keys and to select the order. Then the
execution is sent using the key.
The current state is displayed on the third line (only ON or OFF).
The key allows to abort the control.
Hereafter, 2 samples of control sub-panels:
516 C264/EN UM/E50.5

- Figure 181 - GHU20x - sample of control sub-panel
6.1.3.4.6 Interlocking sub-panel
When a module is selected in the graphic bay panel, the button allows to access to the
interlocking panel. Any button allows to leave this panel and come back to the graphic bay panel.
This panel displays the interlocking equation result (TRUE / FALSE) associated to a device
control.
C264/EN UM/E50.5 517

- Figure 182 - GHU20x - interlocking sub-panel
6.1.3.5 AVR Panel

The AVR panel contains auto generated views which requires no extra configuration. However,
none of these views are available if the user has not configured the presence of the AVR panel in
the GHU board (refer to AP chapter § Setting specific features of the GHU2xx board) or if there is
no AVR function defined.
The content of these views are shown here after:
- Figure 183 - GHU20x - AVR panel - large view
518 C264/EN UM/E50.5

- Figure 184 - GHU20x - AVR panel - detail and control view
- Figure 185 - GHU20x - AVR panel - analysis view (only for AVR on multiple transformers)
where:
• Bay Name: Short name of the bay defined in configuration
• MODE: Current AVR running mode (MANUAL or AUTOMATIC)
• STATUS: Current AVR status (ON or OFF)
• V MEAS: Measured Voltage (regulated) – fixed format on 5 digits: xxx.xx
• TPI: Current Tap Position – fixed format on 2 digits: xx
• DEVIATION: Delta between Target voltage value and Measured Value (%): fixed format on 2
digits: xx
• V TARGET: Target Voltage for the concerned transformer (come from a remote Setpoint or
from local command, or from predefined value in database) – fixed format on 5 digits: xxx.xx
C264/EN UM/E50.5 519

• TARGET: Voltage Target shown as a % of the Nominal Value. (Configurable option on the
Page) – fixed format on 3 digits: xxx
• +RAISE / -LOW: Selectable button for control sequence for Raise/Lower
• V: Measured Voltage (regulated) – fixed format on 5 digits: xxx.xx
• I: Measured current 3 digits
• P: Measured Power 5 digits xxx.xx
• Q: Measured Reactive power 5 digits xxx.xx
• S: Measured Apparent power 5 digits xxx.xx
• COS φ: Measured cosinus phi 5 digits xxx.xx
• φ: Measured phi 5 digits xxx.xx
• I.SIN φ: Measured current x sinus phi 5 digits xxx.xx
When required, any other measurement useful to the AVR monitoring can be displayed via the
generic measurements panel (refer to topic "Generic Measurements Panel" on page 520).
Local HMI offers also all the needed maintenance functions to facilitate the MiCOM C264 with
AVR Commissioning and Maintenance (Visualization of input/outputs).
6.1.3.6 Generic Measurements Panel

The generic measurements panel can display any measurement acquired by the MiCOM C264
regardless of its acquisition source (boards, legacy bus, ISaGRAF) or type (generic, TPI or
“ISAGRAF user function MV”).
6.1.3.6.1 Navigation
The MiCOM C264 proposes one main page and up to three secondary pages.
When accessing to the generic measurements panel for the first time, the first page displayed is
the main page.
The secondary pages are accessed by pressing the and buttons of the front panel.
If the user quits and comes back to the generic measurements panel, then it is not the main page
which is displayed first but the last page accessed before quitting the panel group which can be
the main one but also a secondary page.
520 C264/EN UM/E50.5

6.1.3.6.2 Main Page
- Figure 186 - GHU20x - generic measurement panel - main page
The main page is composed by:

• Page number: the page1 is the main page and pages from 2 to 4 the secondary pages.
• Current time
• Bargraph: it graphically displays the current value percentage of a MV regarding the range
between its minimum and maximum values. 0% corresponds to the MV minimum value
defined in the configuration and 100% to the maximum one. The MV displayed by the
bargraph can be changed by the user at runtime. The label and value of the selected MV are
displayed at the top of the screen.
• Main MV area: it displays a Main MV highlighted in reverse video. This MV is selected by
configuration.
Scroll MV group area: a scroll MV group is a set of 1, 2 or 3 MVs displayed at the same
time in the scroll MV group area. The user can create several groups (up to 6) and by
pressing the and buttons he can change the scroll MV group displayed at
runtime (“scroll” action) while keeping the other areas of the screen unchanged. The
display order within a scroll MV group is defined by configuration.
For example, if two scroll MVs group are defined as follows:

Scroll MV group 1= VAB, VBC, VCA
Scroll MV group 2= IA, IB, IC
Initially, the scroll MV group 1 content will be displayed as shown in the following figure:
C264/EN UM/E50.5 521

- Figure 187 - GHU20x - generic measurement panel - main page - scroll MV #1
After pressing the button the second scroll MV group will be displayed keeping the
other areas unchanged.
- Figure 188 - GHU20x - generic measurement panel - main page - scroll MV #2
Fixed MV area: in contrast to the scroll MVs, the fixed MV area displays always the same
content (the MVs configured as “Fixed MV”) without change after a “scroll” action. In the
main page only two fixed MVs can be displayed. The display order of the MVs is defined
by configuration.
6.1.3.6.3 Measurements display

Each measurement is displayed using two lines:
• 1st line, left aligned: the MV label is displayed on 16 characters based on the “short name”
defined in the configuration. If any, extra characters are dismissed.
• 2nd line, right aligned: the MV value is displayed on 8 characters for the value itself and 4
more characters are reserved for the unit.
The value is systematically (regardless of its profile) forced to 8 characters which includes sign
and decimal separator. For doing this, zeros are appended to the decimal part until reaching 8
characters. In the case that the value is greater than “99999999”, this one is displayed in scientific
notation.
If the quality of the MV is not “valid” (e.g. MV in “Unknown” state), then the displayed value is “----“.
522 C264/EN UM/E50.5

If a MV is set as “spare” in the configuration, its display (label, value and unit) is left blank on the
page
- Figure 189 - GHU20x - generic measurement panel - measurements display
6.1.3.6.4 Bargraph MV selection

It is possible to change the MV associated to the bargraph at runtime at any time.
For doing this, the user has to:
• Press one time on the button to enter to the selection mode. The MV label on top of the
bargraph starts to blink.
•
Press the and buttons to navigate through the MVs available for selection which
are the ones displayed on the current page. In the case of the scroll MVs, only the MVs visible
at the screen at that time are available for selection.
- Figure 190 - GHU20x - generic measurement panel - bargraph MV selection
C264/EN UM/E50.5 523

•
Press the button to confirm the selection or to the button to cancel it.
The association between the bargraph and the MV selected is kept even when navigating to
the secondary pages or to other panel groups.
6.1.3.6.5 Secondary pages

The secondary pages content is similar to the main page except that there is no main MV and no
scroll MV group areas. These pages are used for displaying fixed MVs.
Up to 7 fixed MVs can be displayed per secondary page and up to 3 secondary pages can be
defined.
The bargraph is available for any of the secondary pages and any of the displayed MVs can be
associated to the bargraph using the same bargraph MV selection method as for the main page.
- Figure 191 - GHU20x - generic measurement panel - secondary pages
6.1.3.6.6 Empty pages

If in the configuration there is a gap between the indexes of the used pages (pages having
associated MVs) then the not used pages are considered as empty.
For example:
If MVs are associated to page 1 and 3 but no MV associated to page 2, then page 2 is considered
as empty.
When a page is empty, the screen displays the following message: “NO MV TO DISPLAY ON
THIS PAGE”.
524 C264/EN UM/E50.5

- Figure 192 - GHU20x - generic measurement panel - empty pages
6.1.3.6.7 Selection persistence

The displayed page and the selection of the bargraph MV and of the scroll MV group displayed
are saved into the SRAM. This is done even during a power-off of the MiCOM C264.
At start-up, the MiCOM C264 shows the last displayed page (main or secondary) with the last
known selection of the bargraph MV and scroll MV group.
In the same way, if the user quits the panel group (e.g. by switching to the “Alarms” panel) when
coming back to the generic measurements panel, the selections are also restored.
6.1.3.6.8 Automatic return to the default panel

There is no automatic return to the default panel in case of inactivity. When the measurements
panel is selected, this one remains displayed and refreshed. The only exception is when Cyber
Security is implemented: the Cyber Security inactivity policy applies notwithstanding the
measurements panel display.
6.1.3.7 Events panel

The event panel allows to display the event list of the computer in a chronological order. Display of
events is done from newest to oldest: that means that the newest event declared is displayed at
the top of the events panel (i.e. newest event is always rank 1).
This event list is a circular queue. List maximum size depends of computer version series. This list
is displayed in a scrollable view using arrows buttons. When the circular queue is full and a new
event appears, then the rank of each event is increased and the oldest event in the queue is
removed.
One screen of the LCD contains at maximum 2 events.
At first time the user enters the events’ panel, the 2 newest events are displayed.
C264/EN UM/E50.5 525

- Figure 193 - GHU20x - event panel
An event is composed of 7 lines:

• Line 1: rank of the event in the circular queue
• Line 2: event time stamp
• Line 3: label of the bay
• Line 4: label of the module
• Line 5: label of the datapoint
• Line 6: state of the datapoint
• Line 7: value and unit of the datapoint (if exists)
6.1.3.7.1 Display mechanism for the first page

If the operator visualises the first page, it is assumed that he is looking for the newest events.
Therefore, the page will be updated at the apparition of any new event.
6.1.3.7.2 Display mechanism for an intermediate page:

• The operator visualizes one page between the first page and the last one, it is assumed that
he examines more precisely these events.
• Therefore, when n events appear, the user keeps visualizing the 2 same events. However,
the rank of each event is incremented by n in real time in the list. When the displayed event is
removed from the FIFO, the oldest event is displayed.
6.1.3.7.3 Display mechanism for the last page:

Last page means visualization of the two oldest event of the FIFO and the FIFO is full. When the
displayed event is removed from the FIFO, the new oldest event is displayed.
526 C264/EN UM/E50.5

- Figure 194 - GHU20x - event panel - last page display
6.1.3.8 Faults panel

The first LED of the local HMI indicates 2 levels of fault.
When the LED is ON, a major fault is present. It can be:

• A database incoherence
• A hardware fault
If there is a minor fault the fault LED is blinking. It can be:

• A disconnected IED
• A problem about IRIG-B
• A problem about ISaGRAF
The Fault panel displays these faults.
6.1.3.9 Alarm panel

Alarms are displayed in the form of one list in the panel. This list is a circular buffer and is
displayed in a scrollable view in the same way as for the events panel.
One screen of the LCD can contain a maximum of 2 alarms:
C264/EN UM/E50.5 527

- Figure 195 - GHU20x - alarm panel
An alarm is composed of 7 lines:

• Line 1: alarm apparition time stamp
• Line 2: alarm state and gravity
• Line 3: label of the bay
• Line 4: label of the module
• Line 5: label of the datapoint
• Line 6: state of the datapoint
• Line 7: value and unit of the datapoint (if exists)
Alarms acknowledgment and clearing is defined in topic "Controls (subject to privilege)" on page
540.
528 C264/EN UM/E50.5

- Figure 196 - GHU20x - sample of alarm panel
6.1.3.10 Disturbance record panel

Display of disturbance records corresponds to the list of available disturbance records of the
computer. Two types of files are managed:
• Disturbance file from an IED
• Waveform computed inside the MiCOM C264
C264/EN UM/E50.5 529

- Figure 197 - GHU20x - disturbance record panel
The records are displayed on the panel using 2 lists according to the origin. Displayed information
depends on the origin of the file:
• waveform records are in COMTRADE format, 3 files can be displayed per page. Only the .cfg
file name is displayed on the panel (the .dat files are only available to be uploaded).
- Figure 198 - GHU20x - disturbance record information
(F for fast waveform, S for slow waveform)

• From an IED: 3 files can be displayed per page.
- Figure 199 - GHU20x - disturbance record file
6.1.3.11 Configuration panel

The configuration panel allows to display several panels concerning the computer itself:
• Board panel
• External devices panel
• Service information panel
530 C264/EN UM/E50.5

- Figure 200 - GHU20x - configuration panel navigation
6.1.3.11.1 Boards panel

Board’s list view is a text list containing the status of I/O boards.
For each board, the following information is displayed in one line of the board panel:
• its type,
• its state among the following ones: OK (Board connected and operational), MISSING (Board
missing), FAILURE (Board in fault), TOO MANY (Board present but not configured).
Hereafter, samples of board panel:
C264/EN UM/E50.5 531

- Figure 201 - GHU20x - board panel sample
6.1.3.11.2 External devices panel

This panel display all external devices connected to the computer by a legacy protocol and by the
IP protocols (as IEC 61850). This panel contains 3 sub-sets:
• IP client connection number: it defines the number of client currently connected to the
computer.
• IP server connection state: it defines the list of the server connected to the computer. Each
server is displayed with its name, its IP address, and the state of its connection.
- Figure 202 - GHU20x - external device panel - device information for IP protocol
• Legacy protocol connection state: each IED is displayed with its name, its address, and the
state of its connection.
532 C264/EN UM/E50.5

- Figure 203 - GHU20x - external device panel - device information for legacy protocol
The panel for “IP IED” is as follows:
- Figure 204 - GHU20x - external device panel - devices for IP protocol
The panel for “Legacy IED” is as follows:
- Figure 205 - GHU20x - external device panel - devices for legacy protocol
Hereafter, samples of external device panel:
C264/EN UM/E50.5 533

- Figure 206 - GHU20x - external device panel - samples
6.1.3.11.3 Service information panel

The local control panel is able to present computer related information on several views:
• serial number of computer
• software version
• version’s number and revision’s number of the first database
• version’s number and revision’s number of the second database
• state of both database
• operating hours of MiCOM computer
• operating modes
• redundancy mode
Hereafter a sample of Service information panel
534 C264/EN UM/E50.5

6.1.3.12 Display of binary input information

The state of the physical binary input can be displayed in the “binary input panel”. The operator
defines (with the EPAS-SCE) a list of binary input displayed in this panel among all binary input
defined in the computer.
Each panel contains:

• The board number and its type (DIU, CCU)
• A list of binary input defined by:
• The input number: DI xxx
• The state of the physical input with 3 possible values (On, off , fault)
C264/EN UM/E50.5 535

- Figure 207 - GHU20x - binary input panel
Hereafter a sample of binary input panel:
- Figure 208 - GHU20x - binary input panel - sample
6.1.3.13 Display of binary output information

The state of the physical binary output can be displayed in the “binary output panel”. The operator
defines (in the menu tree) a list of binary output displayed in this panel among all binary output
defined in the computer.
Each panel has:
536 C264/EN UM/E50.5

• The board number and its type (DOU, CCU)
• A list of binary output defined by:
• The output identifier: DO xxx
• The state of the physical output with 3 possible values (on, off, fault)
- Figure 209 - GHU20x - binary output panel
Hereafter a sample of binary output panel:
- Figure 210 - GHU20x - binary output panel - sample
C264/EN UM/E50.5 537

6.1.3.14 Menu tree

Some parameters of the computer can be set by the operator from local HMI. The display /
modification of the parameter value is done in the menu tree from the local HMI. All the
parameters are group in the same path of the menu tree.
The parameters that can be modified on-line are:

• language
• counters value
• synchrocheck parameters (if applicable)
• autorecloser parameters
• pulse delay for open / close controls
• motion 00 and motion 11 delays
• persistence filtering delays
• toggling parameters
• measurements thresholds, deadband and hysteresis
• serial communication parameters
The controls that can be performed from the menu tree are:
• reset of operating hours
• change of computer operating mode
• global alarm acknowledgement
• global alarm clearing
• database switching
• date and time setting
• modify counters value
• modify energy counters value
• activate test mode
The button is used for the navigation in the menu tree. This feature remains and so alarm
acknowledgement will be not allowed from the menu tree.
The following figures show the menu tree in the three operating modes.
538 C264/EN UM/E50.5

6.1.3.14.1 menu tree in operational or simulation mode (example)
- Figure 211 - GHU20x - menu tree sample in operational or simulation mode
C264/EN UM/E50.5 539

6.1.3.14.2 menu tree in maintenance mode
- Figure 212 - GHU20x - menu tree sample in maintenance mode
6.1.3.15 Controls (subject to privilege)

Some controls can be performed from the local HMI:
• Bay Local / Remote mode
• Control of circuit breakers or disconnecting switches
• Tap changer control
• Computer mode
• Database switch
• Reset of operating hours
• Time and date setting
• Manual reset/modification of counters and energy counters
• Alarms acknowledgement
• Alarms clearing
• Activate test mode
All of them require a system engineer being.
Some of these commands are accessible in a panel (bay panel or alarm panel), the others are
accessible in the menu tree. Some controls are protected either by the bay local mode or by a
password.
The following table sums up the protection rules and the accessibility of the controls:
Local Control Protection

Local / Remote control of bay Protected by a password (optional)
Not protected by a password.
X Device command But protected by the password of
command 1 if it exists
Computer mode Protected by a password
Data Base switch Protected by a password
Reset operating hours Protected by a password
540 C264/EN UM/E50.5

Local Control Protection

Time and date setting Protected by a password
Manual reset of counters Protected by a password
Alarms Acknowledge Protected by a password
Alarms clearing Protected by a password
6.1.3.15.1 Local / Remote control of bay

Local / Remote control of bay for LCD front panel (GHU20x)
The system engineer is allowed to change the bay mode:

• From local to remote
• From remote to local
If the computer manages several bays, the state local / remote of bays is set bay by bay. Change
of bay mode is enabled if a bay panel is defined. It means that, if a bay is not associated to a bay
panel, its local/remote control mode cannot be controlled through the L/R button of the panel.
Local / Remote control of bay for simple panel with LEDs (GHU21x)
In case of simple panel, the operator controls all the bays of the computer in the same time. To
change mode, s/he has to press of the button during at least 3 seconds. No password is
necessary to check the control. The 5th LED is used to display the current mode. If all the bays
are NOT in the same state, the command switches them all too local mode.
6.1.3.15.2 Commands of circuit breakers, disconnecting switches and generic devices

Device command is possible by 2 ways:
• From the graphical panel
• From the sub panels command
Circuit breakers, disconnecting switches or generic command are ordered from the local HMI by
the operator. Commands allowed from the local HMI are:
• open
• close
• close a synchronised circuit breaker
• close with bypass on a synchronised circuit breaker (forcing closure), available only when the
DI “Accept Forcing is configured
The button allows to abort the choice in event of command on a close_synchrocheck.
6.1.3.15.2.1 SBO command
In case of the select/execution order (SBO) for opening or closing a module, the operator has to
make on the local HMI a selection before an execution command.
For that, operator presses the command button (button for OFF or button for ON) a
first time for the selection command, and presses button for the execution command.
C264/EN UM/E50.5 541

After a positive acknowledgment of the selection command, the device is displayed in reverse
video.
6.1.3.15.2.2 DE command
In event of the Direct execute order (DE) for opening or closing module, the operator sends
directly the command using the command buttons.
6.1.3.15.2.3 Interlocking bypass
To get access to the bypass flag modification panel, use the button
Set the interlocking bypass command before you send the execute order.
To send the bypass command, use the bypass flag on the interlocking equation.
- Figure 213 - GHU20x - command of circuit breaker - interlocking bypass
6.1.3.15.2.4 Synchrocheck bypass
The operator can send the command using bypass flag on synchrocheck (forcing closure).
The S/C bypass flag is present when the “Accept Forcing” DI is configured. The S/C bypass flag
can be set before or after the execute order sending.
Operator accesses to the bypass flag modification panel by the enter button.
542 C264/EN UM/E50.5

- Figure 214 - GHU20x - command of circuit breaker - synchrocheck bypass
6.1.3.15.2.5 Interface with the operator on local control panel
The button allows to select graphically the device or the command of the bay. When a
device is selected, its label is displayed flashing.
The operator sends this command from the bay panel with button (for OFF) or button
(for ON).
The button allows to abort the choice during the selection step (in event of SBO order).
6.1.3.15.3 Tap changer control request
The button allows to select one by one the devices of the bay. When a transformer is
selected, the operator can control it from local control panel by dealing with associated tap
changer positions.
In order to command the tap changer, the bay that the transformer belongs to has to be in local
mode.
The commands that can be sent through the local HMI are:
• Raise (= current tap position + 1) with the button
for a Double Wound transformer the Low Voltage is increased
for an Auto-wound transformer the Low Voltage is reduced
C264/EN UM/E50.5 543

NOTE: A “raise” control is refused if the current tap position value corresponds to the
maximum position of the tap.
• Lower (= current tap position -1) with the button
for a Double Wound transformer the Low Voltage is reduced
for an Auto-wound transformer the Low Voltage is increased
NOTE: A “lower” control is refused if the current tap position value corresponds to the minimum
• In case of “go to min”, “go to max” or “go to position x” request, the computer uses an internal
automatic function (via ISaGRAF) which generates the desired controls sequences in order to
reach automatically the expected position. This function may generate “Direct execute”, “SBO
once” or “SBO many” sequences according the configuration of the device.
6.1.3.15.4 Computer mode

Control of the MiCOM C264 with AVR and manual orders to the Tap Change are available from
the MiCOM C264 with AVR local HMI with simple and intuitive actions on the animated “Single
Line Page”.
The operator controls:

• Commands on Single Line - View 1:
AVR ON/OFF (by HMI / SCADA)
AVR AUTO/MANU (by HMI / SCADA)
Raise (*) (by front panel keys)
Lower (*) (by front panel keys)
Target Vn-5% (Target Voltage 5) (by HMI / SCADA)

• Commands on LCD View 2:
Target Voltage 1 (Nominal 100% Vn) (by HMI / SCADA)
Target Voltage 2 (Boosting Voltage 2) (by HMI / SCADA)
Target Voltage 5 (Vn-5% ) (by HMI / SCADA)
NOTE: (*) Controls Raise and Lower use front panel keys for navigation: Selection, Enter, Up
and Down.
The Single Line “Page 1” is graphically showing the AVR Running Mode, CB status, Tap Changer
Position Indication and the Current Voltage.
6.1.3.15.5 Data base switch

MiCOM C264 Computer has 2 databases. The operator can switch between both databases.
The operator sends this command from the menu tree with a password protection.
544 C264/EN UM/E50.5

6.1.3.15.6 Reset operating hours

The operator is allowed to reset the operating hours counter.
The operator sends this command from the menu tree with a password protection.
6.1.3.15.7 Time and date setting

The operator is allowed to set time and date of the computer from the local HMI except if it is
synchronized with an external GPS clock.
Time and date are set from the menu tree with a password protection.
6.1.3.15.8 Manual value change of counters

Counters can be reset or affected to a new value manually by the operator at BCP.
Counters are changed from the menu tree with a password protection.
Herafter a sample of manual value change of counter
- Figure 215 - GHU20x - manual value change of counters - sample
When this panel is displayed the most right digit of the wanted value is in inverse video. Buttons
and are used to select the digit of the wanted value that has to be modified. Buttons
and allow to change the value of the selected digit.
Once the correct wanted counter value is defined, it can be validated by pressing the
button.
6.1.3.15.9 Acknowledgement of alarms

Acknowledgement of alarms is performed globally or on a per alarm basis:
• Global acknowledgement: the operator can acknowledge all the unacknowledged alarms of
the computer. It is performed from the menu tree (with password check).
• Alarm per alarm acknowledgement: the operator can perform the alarm acknowledge one by
one. It is performed from the alarm panel.
C264/EN UM/E50.5 545

6.1.3.15.9.1 Global acknowledge
The operator can acknowledge all the unacknowledged alarms of the computer
Interface with the operator on local control panel:
Acknowledgement of all alarms is done from the menu tree (with password check).
6.1.3.15.9.2 Alarm per alarm acknowledge
The operator can perform the alarm acknowledge one by one.
In this case, in the “alarm panel” he selects an alarm and can activate the acknowledge .
Acknowledgement alarm by alarm is done from the alarm panel.
The procedure of acknowledgement by the operator is the following one:
•
the operator select (in the alarm panel) one alarm with the select button: . Once the
alarm is selected, the two first lines of the alarm in the alarm panel are blinking. Deselecting is
performed by the button.
•
the operator press the button, enter the password if necessary
The button allows to abort the command.
If the button sequence is correct, the selected unacknowledged alarm is acknowledged.
The state of the alarm is then changed depending of its initial state:
active unacknowledged to active acknowledged
inactive unacknowledged to inactive acknowledged if the disappearance of the alarm has

to be acknowledged
The alarm list is updated with the new state of the alarm. The alarm in the inactive
acknowledged state is automatically cleared and removed from the alarm list if the automatic
clearing mode is set for this alarm in the database.
6.1.3.15.10 Alarms clearing

Clear of alarms is performed globally or on a per alarm basis:
• Global clear: the operator can clear all the inactive acknowledged alarms of the computer. It is
performed from the menu tree (with password check).
• Alarm per alarm clear: the operator can perform the alarm clear one by one. It is performed
from the alarm panel.
6.1.3.15.10.1 Global clear
The operator can clear all the inactive acknowledged alarms of the computer
clear of all alarms is done from the menu tree (with password check).
546 C264/EN UM/E50.5

6.1.3.15.10.2 Alarm per alarm clear
The operator can perform the alarm clear one by one.
In this case, in the “alarm panel” he selects an alarm and can activate the clear.
Clear alarm by alarm is done from the alarm panel.
The procedure of clear by the operator is the following one:
•
The operator selects (in the alarm panel) one alarm with the select button: .
Only the inactive acknowledged alarm can be selected.

• Once the alarm is selected, the two first lines of the alarm in the alarm panel are blinking.
Deselecting is performed by the button.
•
The operator presses the button, enters the password if necessary.
The button allows to abort the command.
If the button sequence is correct, the selected alarm is cleared and disappears from the list.
6.1.3.15.11 Activate test mode

The operator can activate the test mode for the BCPU, for more information about the test mode,
see the FT chapter. To activate the test mode, select Test mode in the menu tree and press the
button, press it again to deactivate the test mode.
6.1.3.16 Password management

2 profiles are defined in CAT and allowed in the computer:
• observer
• system engineer
These profiles can be named differently in the login panel depending on configuration.
The second one is necessary to activate commands from local HMI:

• command from bay panel
• command with menu tree
• remote to local bay mode
C264/EN UM/E50.5 547

Function Corresponding profiles

Display graphical bay panel
Enter in “measurement” panel from “graphical
bay panel
Enter in “status” panel from “graphical bay
panel
Display alarm list
Observer
Display event list
Display list of disturbance files
Display information on “services” panel
Display AVR information
Display “fault” panel
Display IO state
Acknowledge and clear alarm, alarm global
acknowledgement
Enter in “command” panel from “graphical bay
panel
Change Local/remote mode from “graphical
bay” panel
Switch database
System engineer
Change operating mode
Reset operating hours
Change date/time
Change language
Set counter values
Command Raise / Lower from AVR panel
If the Login panel is not required:

• there is only one account: System Engineer; an observer can still view data without entering
password
• the logoff timeout is the one defined for System Engineer
• a password is mandatory to change the Local/remote mode
When a password is required, a string “password??: “is displayed in the current panel. The
operator has to enter it.
The first character is selected. The and buttons are used to change of selected character.
The and buttons are used to change the value of selected character.
548 C264/EN UM/E50.5

The character is displayed at each button press. The button validates the entered
password. If you press the enter key without entering any password, the string AAAAAAAA is
taken by default.
The current type of characters is repeated in the right bottom corner of the panel:
• A B C for upper case alpha character
• a b c for lower case alpha character
• 0 1 2 for numerical character
• @ / # for special character
Cycle through them with button.
The password cannot be changed and its validity time is 15 minutes. During this delay, user can
run another command. This delay is re-armed at each button press.
C264/EN UM/E50.5 549

6.2 The Computer Administration Tool (CAT)

The Computer Administration Tool (CAT) is a graphical tool that offers an insight into the
MiCOM C264 and tools to modify its files and parameters. It is the unique HMI to view a security
log.
The available functions depend on the user's profile.
- Figure 216 - Computer Administration Tool (CAT)
For more details about CAT use, refer to chapter "Installation" on page 931.
550 C264/EN UM/E50.5

6.3 Printers
Some specific events (the events to log are declared in the database) are printed and
chronologically sorted on logbook printers. They are printed with their time stamping and a
complete description (location and event description).
Logbook printers can be connected to SCP operator interface or to a bay level computer. The
printout format, which can be defined by user during the system configuration phase, is the same
across the whole log book printers connected.
A computer does not print information coming from other computers.
6.3.1 Inputs
A computer receives acquisition from various equipment (protection, captors, etc.) and, after
processing, may generate events that have to be printed. These kinds of events are defined in the
database during the configuration phase.
Types of events can be:

• Binary inputs (SP, DP, MP, SI and Groups)
• Tap position indication
• Measurement
• Operator action:
• Log-in and log-off,
• Devices control
• Alarm acknowledgement / clearing
6.3.2 Outputs
The 5 following properties can be printed. Each property is separated from the other by one blank
character the position of each property in the printed line (i.e. position 1, 2, 3, 4 or 5) is defined in
configuration:
Chronology – 1 character: refer to § “SOE events”
TimeStamp – 24 or 26 characters: refer to § “SOE events”
Origin - 67 characters: for BI, TPI, measurements, controls and alarms, the origin gives the
access path to the object (refer to § “SOE events”)
ObjectName - 16 characters
ObjectMessage - 16 characters
The Origin, ObjectName and ObjectMessage properties contain different information

depending of the associated event type.
6.3.3 Printer management

6.3.3.1 Header & footer
A header and footer can be printed at each page. They are composed of one line, separated from
the events by a blank line.
C264/EN UM/E50.5 551

- Figure 217 - Printer - page format
The page number is in the range [1..999]. It is reset at 1 after reaching 999 and at each new day.
The date could have the following format: DD/MM/YY or MM/DD/YY or YY/MM/DD or
DD/MM/YYYY or MM/DD/YYYY or YYYY/MM/DD. The time has the following format: hh:mm:ss.
6.3.3.2 Chronology & time stamp

The printers are managed in a real-time printing mode.
All synchronised information is printed in a chronological order.
Events are printed with their time-stamping and a complete description (location and event
description). The equipment detecting the event does the time-stamping (time-stamping at
source).
6.3.3.3 Printer out of service

If a printer fails, all the messages are stored in a circular buffer
When the buffer is full, any new message replaces the oldest one.
An indication (Printer status) is generated to indicate the printer failure.
6.3.3.4 Circular FIFO management

Before being printed, all information goes into a circular buffer
A latency delay is configured to sort information.
- Figure 218 - Printer- FIFO management
The size of the buffer is 1000.
When the buffer is full, the oldest information are deleted (300 information suppressed) in order to
have place for new ones.
A specific message is inserted in the buffer to indicate the lost of information, this message has
the following information:
TimeStamp = date of the oldest suppress information
552 C264/EN UM/E50.5

Origin = Name of the computer (configurable)
ObjectName = SUPPRESSED INFOS (configurable)
ObjectMessage = number of lost information
The following extract shows an example of SOE page.
substation-C264_GTW 05/07/06 09:08:35.232
* 05/07/06 09:08:35.232 CALC C264N3 /Generic module Group Permanent Self Check fault
* 05/07/06 09:08:35.232 CALC C264N3 /Group 0 to 499 Group Self Check fault
* 05/07/06 09:08:35.232 CALC C264N3 /Group 0 to 499 Group 1 Self Check fault
C264/EN UM/E50.5 553

PAGE 001
554 C264/EN UM/E50.5

MiCOM C264 - User Manual 7 Application
7 Application
7.1 BCPU configuration scope 565

7.1.1 General EPAS system configuration 565
7.1.2 MiCOM C264 configuration in general EPAS system configuration 565
7.2 Defining BCPU configuration in system architecture 567
7.2.1 Setting general system configuration relevant to MiCOM C264 567
7.2.2 Adding a MiCOM C264 in the system architecture 569
7.2.3 Setting general attributes of MiCOM C264 571
7.2.3.1 Configuring binary input (BI) filtering 572
7.2.3.2 Configuring measurement acquisition and transmission 573
7.2.3.3 Configuring counter acquisition 573
7.2.3.4 Configuring internal fault characteristics 573
7.2.3.5 Locating computer in a substation (mandatory) 574
7.2.3.6 Configuration of SNTP Server 574
7.2.3.7 Defining a redundant computer (optional) 575
7.2.4 Adding BCPU hardware components 577
7.2.4.1 Adding boards 577
7.2.4.2 Setting specific attributes to BCPU boards 578
7.2.4.2.1 Setting common attributes to computer board 578
7.2.4.2.2 Setting specific features of the GHU2xx board 579
7.2.4.2.3 Setting attributes of a TMU220 board 580
7.2.4.2.4 Setting specific features of BIU2x1 board 581
7.2.4.2.5 Setting specific features of a TMU210 board 582
7.2.4.3 Configuring a communication channel 586
7.2.4.4 Configuring an AI channel 588
7.2.4.5 Adding a printer 590
7.2.4.6 Configuring an AO channel 592
7.2.5 MiCOM C264 IP address and routing table definition 594
7.2.5.1 MiCOM C264 as a gateway connected to a router and a remote IEC 60870-5-
104 SCADA 595
7.2.5.1.1 MiCOM C264 Routing table parameters 595
7.2.5.1.2 IEC 60870-5-104 protocol configuration 596
7.2.5.1.3 MiCOM C264 IP address definition 596
7.2.5.1.4 MiCOM C264 IP Parameters 597
7.2.5.1.5 Router-PC configuration (case of PC under Microsoft-windows) 597
7.2.5.1.6 Particular case of DHCP network 598
7.2.5.2 MiCOM C264 as a gateway directly connected to a remote DNP3 SCADA 598
7.2.5.3 MiCOM C264 as a gateway connect maximum of 4 DNP-IP SCADA Protocols 599
7.2.6 Networking BCPU on a Station Bus network 600
7.2.6.1 Adding an IEC 61850 Station Bus Process Bus in the system architecture 600
7.2.6.2 Connecting a BCPU to an IEC 61850 Station Bus network 600
C264/EN UM/E50.5 555

7 Application MiCOM C264 - User Manual
7.2.6.3 Connecting a BCPU to others station bus devices 601

7.2.7 Networking IED on computer legacy network 602
7.2.7.1 Creating a legacy network of IED 602
7.2.7.1.1 Adding a legacy network 602
7.2.7.1.2 Setting general attributes of a legacy network 603
7.2.7.1.2.1 Serial Port communication 603
7.2.7.1.2.2 Ethernet/IP communication 603
7.2.7.1.3 Setting acquisitions attributes of a IEC 60870-5-103 legacy network 604
7.2.7.2 Setting acquisition attributes of a IEC 60870-5-101 legacy network 604
7.2.7.2.1 Setting acquisition attributes of a Modbus legacy network 606
7.2.7.2.2 Setting acquisition attributes of a DNP3 legacy network 607
7.2.7.2.3 Adding an IED to a legacy network 607
7.2.7.2.4 Setting attributes of a legacy IED 609
7.2.7.2.4.1 Specific attributes for legacy DNP3 over IP IEDs 610
7.2.7.2.4.2 Specific attributes for legacy T104 IEDs 611
7.2.7.2.5 Adding an IED acquisition type to a legacy network 611
7.2.7.2.6 Setting attributes of a IEC 60870-5-103 acquisition type 612
7.2.7.2.7 Setting attributes of a MODBUS acquisition type 613
7.2.7.2.8 Setting attributes of a DNP3 acquisition type 614
7.2.7.2.9 Adding Serial Tunneling 614
7.2.7.2.10 Setting acquisition attributes of a IEC 60870-5-104 legacy network 615
7.2.7.3 Defining addressing mapping of a legacy IED 617
7.2.7.3.1 Defining an IED address for an SPS datapoint 618
7.2.7.3.2 Defining an IED address for a DPS datapoint 621
7.2.7.3.3 Defining an IED address for an MV datapoint 623
7.2.7.3.4 Defining an IED address for a Counter datapoint 626
7.2.7.3.5 Defining an IED address for an SPC datapoint 628
7.2.7.3.6 Defining an IED address for a DPC datapoint 630
7.2.7.3.7 Defining an IED address for a SetPoint datapoint 633
7.2.8 Networking SCADA on computer SCADA network 637
7.2.8.1 Creating a SCADA network 637
7.2.8.1.1 Adding a SCADA network 637
7.2.8.1.2 Setting general attributes of a SCADA network 638
7.2.8.1.3 Setting general attributes of a IEC 60870-5-101 SCADA network 639
7.2.8.1.5 Setting general attributes of a DNP3 SCADA network 641
7.2.8.1.5.1 How to Set the General Attributes of a DNP3-IP SCADA Network 641
7.2.8.1.7 Setting specific attributes of a MODBUS SCADA network 646
7.2.8.2 Defining addressing mapping of SCADA network 646
7.2.8.2.1 Defining a SCADA address for an SPS datapoint 647
7.2.8.2.2 Defining a SCADA address for a DPS datapoint 649
7.2.8.2.3 Defining a SCADA address for a MV datapoint 652
556 C264/EN UM/E50.5

7.2.8.2.4 Defining a SCADA address for a Counter datapoint 653

7.2.8.2.5 Defining a SCADA address for a SPC datapoint 655
7.2.8.2.6 Defining a SCADA address for a DPC datapoint 657
7.2.8.2.7 Defining a SCADA address for a SetPoint datapoint 659
7.2.8.2.8 Defining a SCADA address for bypass synchrocheck 661
7.2.8.3 How to configure a mapping of a SCADA network 662
7.2.8.4 Addressing datapoint on SCADA legacy network 664
7.2.9 Defining a time synchronization for an EPAS network 665
7.2.9.1 Setting a SNTP time synchronization 665
7.2.9.2 Setting an IEC 61588 time synchronization 666
7.2.10 Defining wave record file management 667
7.2.10.1 Defining management of disturbance file for IED 667
7.2.10.2 Defining IEC 60870-5-103 IED extra information for disturbance file 667
7.2.10.2.1 Adding an analog channel definition 667
7.2.10.2.2 Adding a digital channel definition 669
7.2.10.3 Defining management of wave record file for computer CT/VT board 669
7.2.10.3.1 Defining fast waveform recording 670
7.2.10.3.2 Defining slow waveform recording 673
7.2.11 Defining a computer klaxon 678
7.2.12 Setting system information for computer components 678
7.2.12.1 Setting general system information of a computer 679
7.2.12.2 Setting system information of board 684
7.2.12.3 Setting system information of legacy IED 685
7.2.12.4 Setting system information of serial printer 686
7.2.12.5 Setting system information of a SCADA network 687
7.3 Defining datapoint 689
7.3.1 Creating a datapoint 689
7.3.1.1 Defining SPS datapoint 690
7.3.1.3 Defining MPS datapoint 692
7.3.1.4 Defining MV datapoint 693
7.3.1.5 Defining TPI datapoint 696
7.3.1.6 Defining counter datapoint 698
7.3.1.7 Overview of control sequence processing 699
7.3.1.8 Defining SPC datapoint 700
7.3.1.8.1 Defining an SPC feedback 701
7.3.1.9.1 Defining a DPC feedback 703
7.3.1.10 Overview of SetPoint processing 705
7.3.1.11 Defining SetPoint datapoint 706
7.3.1.11.1 Defining SetPoint feedback 708
7.3.2 Linking a datapoint to a profile 708
7.3.2.1 Defining an SPS profile 709
C264/EN UM/E50.5 557

7.3.2.1.1 Setting 'General attributes' of an SPS profile 709

7.3.2.1.2 Setting 'State labels' attributes of an SPS profile 710
7.3.2.1.3 Setting 'State treatment' attributes of an SPS profile 710
7.3.2.1.4 Setting 'Alarms' attributes of an SPS profile 711
7.3.2.1.5 Setting 'Interlocking' attributes of an SPS profile 712
7.3.2.2 Defining a DPS profile 712
7.3.2.2.1 Setting 'General' attributes of a DPS profile 712
7.3.2.2.2 Setting 'State labels' attributes of a DPS profile 713
7.3.2.2.3 Setting 'State treatment' attributes of a DPS profile 713
7.3.2.2.4 Setting 'Alarms' attributes of a DPS profile 714
7.3.2.2.5 Setting 'Interlocking' attributes of a DPS profile 715
7.3.2.3 Defining an MPS profile 716
7.3.2.4 Setting 'General' attributes of an MPS profile 716
7.3.2.4.1 Setting 'State labels' attributes of an MPS profile 717
7.3.2.4.2 Setting 'State treatments' attributes of an MPS profile 717
7.3.2.4.3 Setting 'Alarms' attributes of an MPS profile 717
7.3.2.4.4 Setting 'Interlocking' attributes of an MPS profile 718
7.3.2.5 Defining an MV profile 719
7.3.2.5.1 Setting 'General' attributes of an MV profile 719
7.3.2.5.2 Setting 'State labels' attributes of an MV profile 720
7.3.2.5.3 Setting 'State treatments' attributes of an MV profile 720
7.3.2.5.4 Setting 'Alarms' attributes of an MV profile 721
7.3.2.5.5 Setting 'Interlocking' attributes of an MV profile 722
7.3.2.6 Defining a counter profile 722
7.3.2.6.1 Setting 'General' attributes of a counter profile 722
7.3.2.6.2 Setting 'State labels' attributes of a counter profile 722
7.3.2.6.3 Setting 'State treatments' attributes of a counter profile 723
7.3.2.6.4 Setting 'Alarms' attributes of a counter profile 723
7.3.2.6.5 Setting 'Mean value' attributes of a counter profile 724
7.3.2.7 Defining an SPC profile 724
7.3.2.7.1 Setting 'General attributes' of an SPC profile 725
7.3.2.7.2 Setting 'Order labels' attributes of an SPC profile 725
7.3.2.7.3 Setting 'State treatments' attributes of an SPC profile 726
7.3.2.7.4 Setting 'Alarms' attributes of an SPC profile 726
7.3.2.7.5 Setting 'Interlocking and FBD' attributes of an SPC profile 727
7.3.2.8 Defining a DPC profile 727
7.3.2.8.1 Setting 'General' attributes of a DPC profile 728
7.3.2.8.2 Setting 'Order labels' attributes of a DPC profile 728
7.3.2.8.3 Setting 'State treatments' attributes of a DPC profile 729
7.3.2.8.4 Setting 'Alarms' attributes of a DPC profile 729
7.3.2.8.5 Setting 'Interlocking and FBD' attributes of a DPC profile 730
7.3.2.9 Defining a Setpoint profile 731
7.3.2.9.1 Setting 'General' attributes of setpoint profile 731
558 C264/EN UM/E50.5

7.3.2.9.2 Setting 'Treatments on event' attributes of setpoint profile 732

7.3.2.9.3 Setting 'Alarms' attributes of setpoint profile 732
7.3.3 Defining computer local archiving of datapoint events 733
7.3.4 Defining computer local archiving of datapoint alarms 733
7.3.5 Defining computer local logging of datapoint events and alarms 733
7.3.6 Defining acquisition source for inputs datapoints 734
7.3.6.1 Acquiring input datapoint via input channels 734
7.3.6.1.1 Wiring an SPS datapoint via one DI channel 734
7.3.6.1.2 Wiring a DPS datapoint via two DI channels 735
7.3.6.1.3 Wiring a MPS datapoint via N DI channels 736
7.3.6.1.4 Wiring MV and TPI datapoint via N DI channels 736
7.3.6.1.5 Wiring a Counter datapoint 737
7.3.6.2 Acquiring input datapoint via an IED legacy network 738
7.3.6.3 Acquiring input datapoint via non-EPAS IEC 61850 communicant IED 739
7.3.6.4 Producing input datapoint 740
7.3.6.4.1 Implicit production of system input datapoint via system decomposition 740
7.3.6.4.2 Implicit production of electrical input datapoint via built-in function 740
7.3.6.4.3 Explicit production of electrical input datapoint via user function 740
7.3.6.4.4 Explicit electrical input datapoint via CT/VT computation 741
7.3.7 Defining control source for output datapoints 742
7.3.7.1 Controlling output datapoint via output channels 742
7.3.7.1.1 Wiring a SPC datapoint via one DO channel 742
7.3.7.1.2 Wiring DPC datapoint via two or four DO channels 742
7.3.7.1.3 Wiring SetPoint datapoint 743
7.3.7.1.4 Wiring from CCU datapoint 744
7.3.7.2 Controlling output datapoint via an IED legacy network 744
7.3.7.3 Controlling output datapoint via non-EPAS IEC 61850 communicant IED 745
7.3.7.4 Producing output datapoint 746
7.3.7.4.1 Implicit production of system output datapoint via system decomposition 746
7.3.7.4.2 Implicit production of electrical output datapoint via built-in function 746
7.3.7.4.3 Explicit production of output datapoint via user function 746
7.3.7.5 Acknowledgment definition in case of simultaneous ordersAcknowledgment
definition in case of simultaneous orders 747
7.3.8 Defining datapoint association 747
7.3.8.1 Adding a target datapoint 748
7.3.8.2 Linking the target datapoint to the original datapoint 748
7.3.8.3 Defining the states associations 749
7.4 Defining BCPU configuration in electrical architecture 751
7.4.1 Defining an electrical topology 751
7.4.1.1 Defining a Site 752
7.4.1.2 Defining a Substation 753
7.4.1.2.1 Adding a substation generic datapoint 753
7.4.1.2.2 Defining Local/Remote for substation 754
C264/EN UM/E50.5 559

7.4.1.2.3 Defining Taking Control for substation and SCADA links 755
7.4.1.2.4 Adding a user function to a substation 757
7.4.1.3 Defining a Voltage level 757
7.4.1.3.1 Adding voltage level generic datapoint 758
7.4.1.3.2 Adding user function to voltage level 758
7.4.1.4 Defining a Bay 758
7.4.1.4.1 Adding bay generic datapoint 760
7.4.1.4.2 Defining Local Remote for bay 761
7.4.1.4.3 Defining SBMC for bay 762
7.4.1.4.4 Adding a user function to a bay 764
7.4.1.4.5 Adding toggling signal detection 764
7.4.1.4.6 Adding Missing Signaling Voltage 765
7.4.1.5 Defining Module 766
7.4.1.5.1 Adding a module generic datapoint 768
7.4.1.5.2 Adding a user function to a module 768
7.4.1.5.3 Defining a lockable module 769
7.4.1.5.4 Defining withdrawable circuit-breaker or switchgear 770
7.4.1.5.5 Defining a circuit-breaker 770
7.4.1.5.6 Defining an I²t built-in function (relay folder) 774
7.4.1.5.7 Defining a switchgear 777
7.4.1.5.8 Defining a transformer 778
7.4.2 Defining a Synchrocheck function 780
7.4.2.1 Completing circuit-breaker definition for synchrocheck 780
7.4.2.2 External synchrocheck behavior 785
7.4.2.3 Internal synchrocheck behavior 785
7.4.2.4 Automation description of internal synchrocheck 785
7.4.2.5 Creating a synchrocheck function 788
7.4.2.5.1 Setting default settings of internal synchrocheck 790
7.4.2.5.2 Adding synchrocheck specific datapoints 793
7.4.2.5.3 Management of the 5th VT on TMU220: Double Busbar 794
7.4.2.5.4 Voltage reference selection 795
7.4.3 Defining an Auto-recloser built-in function 796
7.4.4 Defining a Tap changer built-in function 806
7.4.4.1 Tap changer behavior 806
7.4.4.2 Creating a tap changer built-in function 807
7.4.5 Defining an automatic voltage regulation–AVR built-in function 809
7.4.5.1 Creating an AVR function 809
7.4.5.2 AVR behaviour 819
7.4.6 Defining an automatic voltage regulation–ATCC built-in function 819
7.4.6.1 ATCC behavior 819
7.4.6.2 Creating an ATCC function 819
7.4.6.2.1 Defining ATCC function at substation level 820
7.4.6.2.2 Defining ATCC function needs at voltage level 824
560 C264/EN UM/E50.5

7.4.6.2.3 Defining ATCC function needs at busbar level 825

7.4.6.2.4 Defining ATCC function needs at transformer level 827
7.4.6.2.5 Defining an electrical topology for ATCC function 830
7.4.7 Defining an electrical regulation by user function 833
7.4.7.1 Defining an FBD fast automation 834
7.4.7.1.1 Creating an FBD fast automation (header definition) 834
7.4.7.1.2 Creating FBD input plug (header definition) 835
7.4.7.1.3 Creating FBD output plug (header definition) 836
7.4.7.1.4 Using FBD editor (body definition) 837
7.4.7.1.5 Linking datapoints to FBD inputs and outputs 838
7.4.7.1.6 Creating FBD timer plugs 839
7.4.7.2 Defining an ISaGRAF® slow automation 843
7.4.7.2.1 Creating an ISaGRAF® slow automation (header definition) 843
7.4.7.2.2 Adding specific datapoints to slow automation (interface definition) 844
7.4.7.2.3 Creating ISaGRAF® client link (interface definition) 845
7.4.7.2.4 Linking a datapoint to an ISaGRAF® client link 845
7.4.7.2.4.1 Defining ISaGRAF® IO prefix for an input 845
7.4.7.2.4.2 Creating ISaGRAF® server link (interface definition) 846
7.4.7.2.4.3 Linking a datapoint to an ISaGRAF® server link 846
7.4.7.2.4.4 Defining ISaGRAF® IO prefix for an output 847
7.4.7.2.4.5 Using ISaGRAF® editor (body definition) 848
7.4.7.3 Defining a group 848
7.4.7.5 Producing a DPS from two SPS 851
7.4.7.6 Defining interlocking 851
7.4.7.7 Defining an automatic/manual dependency 852
7.4.8 Defining a Fast Load Shedding application 853
7.4.8.1 Data flow 854
7.4.8.2 Priority Setpoints 855
7.4.8.3 Load Shedding Preselection (LSP) 855
7.4.8.4 Graphical animation with LSP 857
7.4.8.5 Use of LSP in PSL 857
7.4.8.6 Use of LSP in ISaGRAF® scheme 859
7.4.8.6.1 Set_LSP() ISaGRAF® function 859
7.4.8.6.2 Is_connected_to() ISaGRAF® function 860
7.4.8.7 Datapoints 860
7.4.8.8 MASK object and xPS triggers 860
7.4.8.8.1 MASK object 860
7.4.8.8.2 Trigger definition 860
7.4.8.9 Topology calculation 862
7.4.9 Defining a Synchroscope built-in function 863
7.4.9.1 Synchroscope behavior 863
7.4.9.2 Creating a Synchroscope built-in function 863
C264/EN UM/E50.5 561

7.4.9.3 Limitations 866

7.5 Defining Protection Functions 867
7.5.1 General 867
7.5.1.2 Defining a protection function 868
7.5.2.2 Defining Undervoltage protection function 870
7.5.3.2 Defining earth wattmetric protection function 872
7.5.4.2 Defining Undercurrent protection function 874
7.5.5.2 Defining Negative Sequence Overcurrent protection function 876
7.5.6.2 Defining Thermal overload protection function 878
7.5.7.2 Defining overvoltage protection function 880
7.5.8.2 Defining Zero Sequence Overvoltage protection function 881
7.5.9.2 Defining [67] Directional overcurrent protection function 883
7.5.10 Dir. / Non-dir. Neutral / Ground / Earth OC protection (ANSI code 67N/50N/51N) 884
7.5.10.2 Defining [67N] Directional Earth/ground Fault protection function 885
7.5.11.2 Defining Overfrequency protection function 887
7.5.12.2 Defining Range Frequency protection function 889
7.5.13.2 Defining Underfrequency protection function 891
562 C264/EN UM/E50.5

7.5.14.2 Defining a VT supervision protection function 893

7.5.15.2 Defining Inrush current blocking protection function 894
7.5.16 Defining automation of protection functions 895
7.5.16.1 General 895
7.5.16.2.1 Adding automation function 896
7.5.16.3 Protection setting groups 897
7.5.16.3.2 Setting “2 protection group” automation functions 897
7.5.16.4 [50BF] breaker failure 897
7.5.16.4.2 Setting “[50BF] breaker failure” automatism functions 898
7.5.16.5 Blocking protection 899
7.5.16.5.2 Setting ‘Blocking protection’ automation functions 899
7.5.16.6.2 Setting ‘Cold load start’ automation function 900
7.5.16.7 Logic selectivity 900
7.5.16.7.2 Setting ‘Logic selectivity’ automation function 901
7.5.16.8 Maintenance 901
7.5.16.8.2 Setting ‘Maintenance’ automatism menu 902
7.5.16.9 Miscellaneous 902
7.5.16.9.2 Setting ‘Miscellaneous’ automation menu 903
7.5.16.10.2 Setting ‘Trip management’ automation menu 904
7.6 Defining MiCOM C264 Local HMI 906
7.6.1 Defining a bitmap table 906
7.6.2 Defining a computer workspace 908
7.6.2.1 Settings LHMI labels 908
7.6.2.2 Creating a workspace 910
7.6.3 Defining a computer bay mimic 910
7.6.3.1 Creating a computer bay mimic 910
7.6.3.2 Defining static: part line, bitmap, fixed text 914
7.6.3.2.1 Adding a line 914
7.6.3.2.2 Adding a bitmap 916
7.6.3.2.3 Adding a fixed text 917
C264/EN UM/E50.5 563

7.6.3.3 Defining dynamic part: pre-defined dynamic text, generic module representation,
transformer representation 918
7.6.3.3.1 Adding time information 918
7.6.3.3.2 Positioning Local/Remote status, Synchrocheck bypass or Interlock bypass 919
7.6.3.3.3 Adding SBMC information 920
7.6.3.3.4 Adding a generic module representation 921
7.6.3.3.5 Adding a transformer representation 923
7.6.3.4 Assigning MV to bay mimic 925
7.6.4 Defining the generic measurements panel 927
7.6.4.1 Defining the presence of the main and secondary pages 927
7.6.4.2 Defining the MV display options 927
7.6.4.3 MV Bargraph 929
7.6.5 Displaying datapoint status with Led 929
564 C264/EN UM/E50.5

7.1 BCPU configuration scope

7.1.1 General EPAS system configuration
To define a complete EPAS system, three aspects should be considered.
The first one is the system topology. It consists of device composition that manages the
customer’s electrical process. Generally, this part of furniture is relevant to Schneider Electric and
corresponds to Schneider Electric system process definition to respond customer’s needs.
The second one is the electrical topology. It consists of the customer’s electrical process definition
in term of typed electrical devices (transformer, disconnector, circuit-breaker…) that are
connected each other through busbars or lines. Generally, this part of furniture is relevant to the
customer.
The third one is the graphical topology. It consists of the mimic and their graphical animation
descriptions that appear at substation control points (operator interface) and bay control points
(MiCOM C264 local HMI).
When creating a new configuration using EPAS-SCE, these three topologies are automatically
instantiated via root objects:
• A ‘Site’ object for the electrical topology, containing one ‘Substation’ object.
• A ‘Scs’ object for the system topology, containing two folders:
• ‘SubNetworks’, containing all the configured Station Bus and Process Bus networks
• ‘IEDs’, containing all the configured IEC 61850 IEDs connected on the previous subnetworks
• A ‘Graphic’ object for the graphical topology.
- Figure 219 - general architecture of a EPAS configuration in SCE
7.1.2 MiCOM C264 configuration in general EPAS system configuration

In EPAS system general configuration, MiCOM C264 is concerned by the three topologies:
• System topology (Scs):
MiCOM C264 as sub-component of IEDs folder whose AP is connected to an IEC 61850
network in SubNetworks folder.
• Electrical topology (Site):
MiCOM C264 manages bays and relevant modules or substation information.
C264/EN UM/E50.5 565

• Graphical topology (Graphic):

MiCOM C264 can own LCD display used for animated graphical bay panel representation
and others list panels.
566 C264/EN UM/E50.5

7.2 Defining BCPU configuration in system architecture

7.2.1 Setting general system configuration relevant to MiCOM C264
System configuration is done at SCS root. It is relevant to some general behavior of EPAS
devices.
It concerns those specific attributes:

• Common labels used for control acknowledgment, time quality logging, alarm management
logging, computer board management.
• Alarm management characteristics (alarm processing type, audibility delays, alarm clearing
mode per gravity basis).
And those specific relations:

• Designation of the master clock device in the system. This system device gives the time
reference to all other devices through the station-bus network.
• Designation of elementary action rights by default used by system datapoints of the SCS tree.
• Designation of the substation where the system devices are located.
Some attributes of SCS objects concern all the MiCOM C264 defined under the station network.
Hereafter, are listed these attributes:
• time zone: used for timestamp information.
• behavior on DOU failure (Control refused on faulty board / computer goes in faulty mode).
• computer password: local HMI password by default.
• Default board labels and status.
• Control acknowledgment labels used for order logging.
- Figure 220 - General and labels attributes OF SCS
C264/EN UM/E50.5 567

- Figure 221 - labels attributes of SCS (cont’d)
568 C264/EN UM/E50.5

- Figure 222 - alarm attributes OF SCS
At computer level, default alarm processing type is not significant, because alarm processing is
always ‘data basis’ for computer.
Audibility and clearing mode features are not applicable to computer configuration.
Only “alarm managed on computer” attribute is significant to set on “Yes” if alarms are managed
at computer level.
- Figure 223 - COMPUTER routing attributes of SCS
Routing attributes:
• Gateway TCP/IP address: IP address of intermediate “Router” (if present)
• Target TCP/IP address: IP address of authorized remote “Client” (Scada,)
7.2.2 Adding a MiCOM C264 in the system architecture

The addition of a MiCOM C264 definition is done via the “Objects entry” window at ‘IEDs’ folder
level by clicking on mouse’s right button as the following:
C264/EN UM/E50.5 569

- Figure 224 - Adding a computer in the system architecture
Default components of MiCOM C264
When you add a MiCOM C264 from the “Objects Entry” window, you will obtain the sub-tree of the
computer with its default components:
- Figure 225 - Default components of the computer

• Binder ‘Hardware’, that groups all defined boards and printers of the computer.
• Binder ‘System infos’, that groups all general system datapoints of the computer.
570 C264/EN UM/E50.5

• ‘PLC’ object for Programming Logic Chart that corresponds to ISaGRAF® and PSL project
directory.
7.2.3 Setting general attributes of MiCOM C264

When adding a MiCOM C264 in IEDs list, some of its attributes must be set and verified. Hereafter
are listed these attributes.
On MiCOM C264 object

• short name and long name: used for logging, alarms, …
• rack model (80 TE / 60 TE / 40 TE): rack size (width) . Whatever the width, the height of rack is
4U.
• date format: this attribute defines the date format used in the computer HMI (LCD).
• Timer for SCADA GI (ms): timer delay between to ASDU frames
• Timestamped ‘unknown‘ for SCADA: Yes/No
• synchronization source (None / IRIG-B): indicates if the computer is synchronized through

IRIG-B. The relation at SCS level “has for master clock” defines which device is the master
clock in the system. A master clock computer is necessary synchronized through IRIG-B.
• TCP/IP address and network name (limited to 15 characters) of the computer.
• Boards definition: kinds of board used at computer level
- Figure 226 - BCPU general attributes
On IEC 61850 Access Point (AP), sub object of MiCOM C264:

• TCP/IP adress of its access point
C264/EN UM/E50.5 571

- Figure 227 - AP general attributes
Configuration rules and checks

• The "TCP/IP address" value of a device must be unique among all the devices per Ethernet
Network.
• The "network name" value of a device must be unique among all the devices per Ethernet
Network.
7.2.3.1 Configuring binary input (BI) filtering

For more information about binary input filtering, refer to the chapter "Functional Description" on
page 100 of MiCOM C264.
A value of 0 means that no filter is applied: a change of state is validated as soon as it is detected.
Three couples of delays (debouncing/filtering) are defined:

• one for all Digital Inputs which will be used as Binary Inputs.
• one for all Digital Inputs which will be used as Digital Measurements.
• one for all Digital Inputs which will be used as counters.
- Figure 228 - Setting BI acquisition attributes
• debouncing delay (range [0, 20ms], step 1ms).
• filtering delay (range [0,.20ms], step 1ms)
Toggling attributes are defined as follow:
A digital input (DI) is said to be toggling if its state has changed more than N times in a given
period T1.
A toggling DI returns in the normal state if its state has not changed within another period T2.
N (toggling transition number), T1 (toggling delay) and T2 (toggling end delay) are parameters
determined during the configuration step on a per computer basis.
If the attribute "debouncing delay" is set to 0, then the attribute "filtering delay" must be set to 0.
572 C264/EN UM/E50.5

7.2.3.2 Configuring measurement acquisition and transmission

Configuring measurement acquisition and transmission is done via Measurements tab-pane of
MiCOM C264 attributes:
• Debouncing delay and filtering delay: used for digital measurements (see "Configuring binary
input (BI) filtering" on page 572 for details).
• Analogue measurements acquired on AIU board: acquisition sample ranges for long
scanning (range [500 ms, 10000 ms], step 500 ms) and short scanning (range [100 ms, 1000
ms], step 100 ms). For each channel of AIU board, short or long scan period should be
chosen.
• Acquisition on CTVT board with CTVT fundamental 50 or 60 Hz (number of harmonics is fixed
to maximum 16).
• Short transmission period on station bus (range [0, 60s], step 100ms) and long transmission
period given by a multiple of the short period ([0..600] x short transmission period).
If the attribute "debouncing delay" is set to 0, then the attribute "filtering delay" must be set to 0.
7.2.3.3 Configuring counter acquisition
- Figure 229 - counter acquisition attributes of a computer

• debouncing delay and filtering delay: used for digital counters (see "Configuring binary input
(BI) filtering" on page 572 for details)

• If the attribute "debouncing delay" is set to 0, then the attribute "filtering delay" must be set to
0.
7.2.3.4 Configuring internal fault characteristics
- Figure 230 - miscellaneous attributes
C264/EN UM/E50.5 573

• Number of software error detected allowed in a given period else the BCPU remains in HALT
mode. BCPU reboots automatically if it does not reach the ‘fault max number’ in the ‘fault
detection time’ period. When this criterion is reached the BCPU remains in HALT mode.
7.2.3.5 Locating computer in a substation (mandatory)

As said in section "Setting general attributes of MiCOM C264" on page 571, each system device
has to be located in a specific substation. This is done by defining the mandatory relation (1) “is
located in:“ for each system device, especially computers.
- Figure 231 - Locating computer in a substation
7.2.3.6 Configuration of SNTP Server

As said in section "Setting general attributes of MiCOM C264" on page 571, up to two computers
can be master clock for the system. This is done by defining TCP/IP address of main master and
TCP/IP of auxiliary MiCOM C264. These configurations define in SCS attributes. In the below
figure, MiCOM C264 having IP address 192.168.0.10 (TCP/IP address) acts as main source of
system synchronization and MiCOM C264 having IP address 192.168.0.12 (auxiliary TCP/IP
address) acts as secondary source of system synchronization in case of a main MiCOM C264
failure.
• Main MiCOM C264 acts as master clock.
• Auxiliary MiCOM C264 acts as master clock in case of a main MiCOM C264 failure.
- Figure 232 - SNTP configuration
574 C264/EN UM/E50.5

7.2.3.7 Defining a redundant computer (optional)
To define a redundant computer:

• Create the main computer, considered as master one.
• Via the contextual menu of the computer, run “Create backup” (1).
Then:
• An extra computer (considered as slave one) is automatically created with an implicit relation
of backup between the two computers.
• Once the backup computer has been created, its attributes and constitution are locked for
updating and follow the main computer ones. The only exceptions are its short name and long
name and network identification (IP address and network name) that must be correctly
updated. When an object is added to (resp. removed from) the main computer the same
object is added to (resp. removed from) the backup computer, but attributes cannot be
modified.
C264/EN UM/E50.5 575

- Figure 233 - DEFINING A REDUNDANT COMPUTER (CREATION ACTION)
- Figure 234 - DEFINING A REDUNDANT COMPUTER (ONCE CREATED)
The wiring report generates a mapping by available racks (main and extension) if applicable.
576 C264/EN UM/E50.5

7.2.4 Adding BCPU hardware components

7.2.4.1 Adding boards
MiCOM C264 computers are composed of boards, responding to specific functions:
• DIU2xx - Digital input boards with 16 digital input channels:
- digital and counter acquisition
- digital measurement acquisition
• AIU2xx - Analogue input boards with 8 analogue input channels:
- analogue measurement acquisition
• TMU2xx - CT and VT input board with CT and VT input channels:
- CT/VT sampling acquisition,
- MV computations based on acquired samples
• DOU2xx - Digital output boards with 10 digital output channels:
- execution of single or dual, transient or permanent commands
- setting of digital setpoints
• CCU2xx - Mixed digital 8 input and 4 output boards with digital input and output channels
(take good care that the DO 4,5,6,7 are defined but not used):
- Circuit Breaker Control Unit
• CPU275 - CPU board with communication channels (2 Ethernet and serial communication
ports)
• BIU241/261 - Power Supply board with serial communication channels
• GHU2xx - Graphical panel boards with led channels
• AOU200 - Analogue output board with 4 analogue output channels.
• Specific boards and modules for SMart Terminal Block (SMTB) usage (refer to Smart
Terminal Block I/O documentation for usage and configuration).
Computer hardware definition is done in SCE by adding typed boards below computer object.
Mandatory boards (CPU275, GHU2xx, BIU241/261) are automatically created at computer’s
creation.
Linking datapoint to channels corresponds to datapoint wiring.
The addition of a board definition is done via the “Objects entry” window by clicking on mouse’s
right button as the following:
C264/EN UM/E50.5 577

- Figure 235 - Adding a board to the computer
Refer to chapter Technical Data (TD) for further information relevant to configuration rules for
slots and boards of MiCOM C264.
7.2.4.2 Setting specific attributes to BCPU boards

7.2.4.2.1 Setting common attributes to computer board
For each board of the computer the short name attribute (1) may be updated for correct logging
and alarm discrimination concerning board status datapoint.
For boards AIU2xx, CCU2xx, DIU2x0, DIU211, DOU200, DOU201, AOU200 the physical board
number attribute (2) must be updated.
For boards CPU275, BIU241/BIU261, GHU200, TMU2x0 this attribute is forced to 0 by the SCE
and is not displayed in the attributes window.
- Figure 236 - General attributes of a board
578 C264/EN UM/E50.5


• Per board type (AIU210/AIU211, DOU200, DOU201, DIU20x, CCU2xx), the physical board
number attribute values must begin from 0, be unique and contiguous.
7.2.4.2.2 Setting specific features of the GHU2xx board

• the attribute HMI type has to be set to:
Simple if GHU 210/220 is used (no LCD)
Complete if GHU 200 is used (with LCD)

• the default start panel can be bay, defaults, AVR, service, banner; it must be set to banner if
the attribute Login panel present is set to Yes
• the attribute Login panel present is set to Yes (Login panel shows after the banner) or No
• the banner must include at least 32 characters (10 char per line at most):
- Figure 237 - General attributes of a GHU200 board
NOTE: The extra relation has for workspace (1) must be filled. For details about computer
workspace, refer to section "Defining a computer workspace" on page 908.
C264/EN UM/E50.5 579

- Figure 238 - Defining workspace for complete GHU200 board
For computer LED configuration, refer to section "Displaying datapoint status with Led" on page
929.

• If the value of the "HMI type" attribute is "Simple", then "Led#5" must not be used (no relation
link from "Led#5" to a datapoint).
• If the value of the "HMI type" attribute is different from "Complete", then the relation "has for
workspace" must not be linked.
7.2.4.2.3 Setting attributes of a TMU220 board

For TMU220 board, the following attributes have to be set for correct CT/VT computation of extra
measurements:
• short name
• electrical network topology (Star / Delta)
• reference phase (Phase A / Phase B / Phase C)
• reference phase side (Phase A, B, C wired line side / Phase A, B, C wired busbar side)
• power flow mode : Mode1, Mode2, Mode3, Mode 4
• nominal current
• nominal voltage.
• Number of periods to compute harmonic
• Number of periods to compute energy
• voltage ref change mode:
Default voltage reference: as soon as the stated reference phase is valid again, the TMU
locks onto it.
580 C264/EN UM/E50.5

Current voltage reference: the TMU stays locked onto the phase that has a valid signal.
• meas quality when missing (value=0; quality=VALID/ quality=FAULTY)
Unknown: When there is no signal on the TMU, the MiCOM C264 returns the value 0/self-
Check fault on the IEC 61850 network
Value 0: When there is no signal on the TMU, the MiCOM C264 returns the value 0 / Valid
on the IEC 61850
During the synchronization of the TMU frequency, set the related measurement values to 0 /self-
Check fault. Do not set the related measurement values to 0 / Valid.
If reference phase signal is absent, values transmitted by TMU board are set to invalid.
Extra attributes are reserved for future use. TMU220 board has the same attributes as TMU200
except that it has an additional attribute “physical board number” which is set to “0” by default.
- Figure 239 - TMU200/220 board specific attributes
Please refer to the Chapter CO (Connections) for the description of the TMU2xx electrical CT/VT
inputs and database association.
7.2.4.2.4 Setting specific features of BIU2x1 board

The BIU board type is chosen from BIU attributes
C264/EN UM/E50.5 581

- Figure 240 - Select type of BIU board

• BIU board type: choice BIU mono source for BIU241 / BIU dual source for BIU261
For BIU261, Three SPS are available in order to monitor dual source feature.
- Figure 241 - Display SPS voltage source for BIU261 board

• Voltage source 1: Indicate the presence (SET) of voltage at the right electrical level on main
power supply source.
• Voltage source 2: Indicate the presence (SET) of voltage at the right electrical level on
secondary power supply source.
• Volt source used: Indicate the secondary power supply in use (SET) / the main power
supply in use (RESET).
7.2.4.2.5 Setting specific features of a TMU210 board

When adding a TMU210 board to a MiCOM C264, the following optional fault information MV
datapoints can be added at 'System infos' level:
Short name Description Value

Fault Phase Voltage UA_
Flt_Phase_UA_RMS 60
RMS
Fault Phase Voltage UB_
Flt_Phase_UB_RMS 61
RMS
Fault Phase Voltage UC_
Flt_Phase_UC_RMS 62
RMS
582 C264/EN UM/E50.5


Fault Phase Voltage U0_
Flt_Phase_U0_RMS 63
RMS
Fault Phase Current IA_
Flt_Phase_IA_RMS 64
RMS
Fault Phase Current IB_
Flt_Phase_IB_RMS 65
RMS
Fault Phase Current IC_
Flt_Phase_IC_RMS 66
RMS
Fault Phase Current I0_
Flt_Phase_I0_RMS 67
RMS
Flt_Angle_IA_UBC Fault Angle IA_UBC 68
Flt_Angle_IB_UCA Fault Angle IB_UCA 69
Flt_Angle_IC_UAB Fault Angle IC_UAB 70
Flt_Angle_I0_U0 Fault Angle I0_U0 71
Flt_P_ActivePw Fault P Active Power 72
Flt_Q_ReactivePw Fault Q Reactive Power 73
Flt_Phase Fault Phase 74
Flt_Time_ms Fault Time (in ms) 75
Flt_Phase_IA Fault Phase Current IA 76
Flt_Phase_IB Fault Phase Current IB 77
Flt_Phase_IC Fault Phase Current IC 78
Flt_Phase_I0 Fault Phase Current I0 79
Flt_Frequency Fault Record Frequency 80
Flt_Duration Fault Record Duration 81
Flt_OperTime Fault Relay Operation Time 82
Flt_IN_Measured Fault Current IN Measured 83
Flt_IN_Derived Fault Current IN Derived 84
Fault Phase to Phase
Flt_PhPh_UAB 85
Voltage UAB
Flt_PhPh_UBC 86
Voltage UBC
Flt_PhPh_UCA 87
Voltage UCA
Flt_Phase_UA Fault Phase Voltage UA 88
Flt_Phase_UB Fault Phase Voltage UB 89
C264/EN UM/E50.5 583


Flt_Phase_UC Fault Phase Voltage UC 90
Flt_Phase_U0 Fault Phase Voltage U0 91
Flt_VN_Measured Fault Voltage VN Measured 92
Flt_VN_Derived Fault Voltage VN Derived 93
Flt_ActiveGroup Fault Active Group 94
Fault Time (s most
Flt_Time_s_up 95
significant bit)
Fault Time (s least
Flt_Time_s_lo 96
significant bit)
584 C264/EN UM/E50.5

These 'fault' datapoints provides key information and measurements captured during a fault
sequence for post fault analysis. At boot, MiCOM C264 initializes all fault information datapoints
defined in the database with the value 0 and quality Unknown. In run time, MiCOM C264 will
update these datapoints with Measure / Quality / Time values if a trip occurs in the relay managed
by the board.
The Flt_Phase datapoint is represented by an integer MV datapoint using the following values:
C264/EN UM/E50.5 585

Fault phase Value

AN 1
BN 2
CN 4
AB 3
CA 5
BC 6
ABC 7
N 8
Configuration rules and checks:

• Flt_Time: these datapoints represent time and date of the trip of the relay managed by the
board
Flt_Time_s_up: the 32 most significant bit of the second
Flt_Time_s_lo: the 32 least significant bit of the second
Flt_Time_ms: the millisecond range of the fault

• Flt_Duration: duration of the fault in the system (time between the Start of the fault and Reset
of the fault)
• Flt_OperTime: duration between the Start element and Trip element in the relay
Flt_IN_Measured and Flt_IN_Derived are exclusive, only one type of Fault current (Measured or
Derived) can be published on IEC 61850 at the same time in a given configuration.
Flt_VN_Measured and Flt_VN_Derived are exclusive, only one type of Fault voltage (Measured
or Derived) can be published on IEC 61850 at the same time in a given configuration.
7.2.4.3 Configuring a communication channel

A communication channel is a physical port available on CPU or the BIU board at their creation.
A communication channel can be used exclusively for:

• Communication with an IED legacy network.
• Communication with a SCADA network.
• Communication with a serial printer.
586 C264/EN UM/E50.5

- Figure 242 - Usage of communication channel
Once used by a communication link, the physical port has to be set relatively to the
communication link characteristics:
• RS type (RS 232 / RS 485).
• baud rate (bits/s) (50 / 100 / 200 / 300 / 600 / 1200 / 2400 / 4800 / 9600 / 19200 / 38400 /
56000 / 64000)
NOTE: For the CPU275 ports 3 and 4, the baud rates can be different.
• parity (No parity / Odd parity / Even parity)
• number of stop bits (1 bit / 2 bits)
• nb. bits per char (7 bits / 8 bits)
• Tx carrier management (Switched / Constant / Soft):
C264/EN UM/E50.5 587

Switched: when the computer has to send a frame it sets the RTS line and waits for the
CTS line to be set by the receiver. It then waits during a time defined by attribute (9)
before starting the transmission of the frame. At the end of the transmission the computer
waits during a time defined by attribute (10) before resetting the RTS line
Constant: the RTS line is always set by the computer. When it has to send a frame it waits
for the CTS line to be set by the receiver to start the transmission.
Soft: the RTS and CTS line are not managed by the computer.
• CTS wired (No / Yes): this attribute must be set to YES if the TX carrier management attribute
is set to Switched or to Constant
• CD wired (No / Yes): in order for the DCD line to be managed by the computer this attribute
must be set to YES if the TX carrier management parameter is set to Switched.
• pre TX time (range [0, 1 s], step 1 ms): this attribute is visible and therefore significant only if
attribute (6) is set to Switched.
• post TX time (range [0, 1 s], step 1 ms): this attribute is visible and therefore significant only if
attribute (6) is set to Switched.
- Figure 243 - General and transmission attributes of a communication channel
7.2.4.4 Configuring an AI channel

An AI channel is an analogue input available on AIU21x boards at their creation. AI channels are
used for analogue measurement acquisition.
588 C264/EN UM/E50.5

- Figure 244 - Usage of analogue channels
Once used by a MV, the AI has to be set relatively to the acquisition characteristics:
• Sensor range for AIU210/AIU211: -20 mA …+20 mA / -10 mA …+10 mA / -5 mA +5 mA / -1
mA …+1 mA / 0 mA …+1 mA / 0 mA …+5 mA / 0 mA …+10 mA / 0 mA +20 mA / 4 mA …+20
mA,
• acquisition period (short period / long period): refer to section "Configuring measurement
acquisition and transmission" on page 573.
C264/EN UM/E50.5 589

- Figure 245 - Configuring an AI channel
7.2.4.5 Adding a printer

SCE data modeling describes printers used in EPAS system for ‘sequence of events’ and log
book functions at operator interface level and computer level.
A printer at computer level must be a serial one connected to a communication channel of the
computer.
To create a computer printer:

• Add a serial printer from object entry available at computer level.
- Figure 246 - Adding a serial printer

• Update its ‘has for communication port’ relation (1) and its attribute ‘printer control’ (2).
590 C264/EN UM/E50.5

- Figure 247 - Updating the communication port relation for a serial printer
To control the way logging is managed and formatted on a serial printer, updating printer
attributes is necessary:
• page size (range [20 lines, 65535 lines], step 1 line).
• buffer size (range [100 events, 3000 events], step 100 events)
• number of events to suppress when buffer is saturated (range [30 events, 1000 events], step
10 events)
• Rank of the different columns used for printing formats.
C264/EN UM/E50.5 591

• The following constraint must be respected: buffer size > nb of events to suppress when
saturated
Hereafter an extract of logging that illustrates the different columns used for printing formats:
- Figure 248 - The different columns used for printing formats

• The value of each "… column rank" attribute must be unique.
7.2.4.6 Configuring an AO channel

An AO channel is an analogue output available on AOU200 at their creation in SCE.
592 C264/EN UM/E50.5

- Figure 249 - Usages of AO channels
The AO channel has following attributes:

• Output current maintained mode: Yes or No
• Each current output is individually managed in 2 modes:
Un-maintained Mode: in case of computer shut down or power off, the output is set to 0.
Maintained mode: in case of computer shut down or power off, the output level is
maintained (and the Read inhibit relay is set). Only the reception of a new set point will
lead to an output value modification.
• Sensor range for AOU200:
-20 mA …+20 mA / -10 mA …+10 mA / -5 mA …+5 mA /4 mA …+20 mA /
0 mA …+5 mA /0 mA …+10 mA/0 mA …+20 mA
C264/EN UM/E50.5 593

- Figure 250 - Show attributes of AO channels
7.2.5 MiCOM C264 IP address and routing table definition

You’ll find hereafter example of MiCOM C264 addressing and routing table definition in two typical
MiCOM C264 application cases.
594 C264/EN UM/E50.5

7.2.5.1 MiCOM C264 as a gateway connected to a router and a remote IEC 60870-
5-104 SCADA
- Figure 251 - MiCOM C264 connected to a SCADA via a router
7.2.5.1.1 MiCOM C264 Routing table parameters

In SCE configuration MiCOM C264 routing table is declared as follow:
“Gateway TCP/IP address” give the address of the router.

“Target TCP/IP address” is the address of the remote “Client” to be connected through this router.
C264/EN UM/E50.5 595

- Figure 252 - Attributes of Scs
NOTE: “Gateway TCP/IP address” is not linked to the MiCOM C264’s gateway functionality.
“Target TCP/IP address” a network but it can be a target.
Example: We can replace 192.168.30.0 by 192.168.30.2. In this case only the IP on 192.168.30.2
can be replied by MiCOM C264
The label “Gateway TCP/IP address” is to be understood as: “Router IP address”.

The label “Target TCP/IP address” is to be understood as: “Target or Network IP address”.
7.2.5.1.2 IEC 60870-5-104 protocol configuration

It is possible to secure IEC 60870-5-104 client remote connection by giving a short list of
authorized clients.
In the example, IEC 60870-5-104 SCADA link configuration is to be as defined as hereafter:
- Figure 253 - IEC 60870-5-104 configuration
7.2.5.1.3 MiCOM C264 IP address definition

The MiCOM C264 IP address is defined
596 C264/EN UM/E50.5

• locally with the MiCOM C264 LCD
• Using the CAT Tool
In the example the MiCOM C264 have address 192.168.20.1 and subnet mask 255.255.255.0
(default value) he is able to reach all equipment with address 192.168.30.x.
7.2.5.1.4 MiCOM C264 IP Parameters
The Internet addresses (IP) are specified in "dot" notation; This field can have an optional subnet
mask.
The CAT Tool helps to change the IP Address
Example: 60.8012.61 / 255.255.128.0.
7.2.5.1.5 Router-PC configuration (case of PC under Microsoft-windows)

In case of PC with two Ethernet boards, you have to configure both IP board and activate IP
routing thanks to a registry key.
In a registry editor, navigate to

HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\Tcpip \Parameters
Select the "IPEnableRouter" entry (by defining as value: 1):
C264/EN UM/E50.5 597

- Figure 254 - Registry edition
To enable IP routing for all network connections installed and used by this computer, assign a
value of 1.
This will be considered after rebooting computer.
7.2.5.1.6 Particular case of DHCP network

The Dynamic Host Configuration Protocol (DHCP) is based on automatic assignment of IP
addresses, subnet masks, default gateway, and other IP parameters.
NOTE: MiCOM C264 is designed for fixed IP address network, IP addressing conflicts could be
met with the MiCOM C264 installed on networks with DHCP addressing.
7.2.5.2 MiCOM C264 as a gateway directly connected to a remote DNP3 SCADA
- Figure 255 - MiCOM C264 connected to a SCADA
NOTE: In case of DNP3/IP SCADA connected to MiCOM C264-GTW without using any router, it
is not necessary to configure IP addresses at SCS level (Gateway TCP/IP address, Target
TCP/IP address).
598 C264/EN UM/E50.5

In this example, MiCOM C264 must have address 192.168.20.1 and SubNetwork mask must be
set to 255.255.0.0; it will accept connection from SCADA 192.168.30.4.
• In the attribute of MiCOM C264 SCADA port for DNP3 protocol, Link types are Serial, TCP/IP
and UDP
• Functionalities of Link type UDP is same as TCP/IP
- Figure 256 - MiCOM C264 SCADA DNP3 attribute
7.2.5.3 MiCOM C264 as a gateway connect maximum of 4 DNP-IP SCADA

Protocols
- Figure 257 - MiCOM C264 connected to a SCADA (Maximum DNP-IP SCADA Protocols)
In this example, MiCOM C264GTW must have address 192.168.20.1 and SubNetwork mask
must be set to 255.255.0.0; it will accept connection from SCADA 192.168.30.1, 192.168.30.2,
192.168.30.3, 192.168.30.4.
In this example, the IP address for the SCADA DNP-IP protocol defined for the client1
(192.168.30.1) is configured in the SCE as figure below:
C264/EN UM/E50.5 599

- Figure 258 - Defining DNP-IP Configuration with 4 SCADA DNP-IP
7.2.6 Networking BCPU on a Station Bus network

7.2.6.1 Adding an IEC 61850 Station Bus Process Bus in the system architecture
The addition of an IEC 61850 network definition is done via the “Objects entry” window at
‘SubNetworks’ folder level by clicking on mouse’s right button as the following:
- Figure 259 - Adding an IEC 61850 Network in the

system architecture
7.2.6.2 Connecting a BCPU to an IEC 61850 Station Bus network

BCPU connection to the Station Bus (SBUS) is done by linking the Access Point (AP) of the
computer to an SBUS network and by setting the IP characteristic of the access point of the BCPU
(see "Setting general attributes of MiCOM C264" on page 571).
- Figure 260 - Connecting a BCPU to an IEC 61850 Station Bus network
600 C264/EN UM/E50.5

7.2.6.3 Connecting a BCPU to others station bus devices

To transmit information between EPAS sub-systems and third-party IEC 61850 devices,
IEC 61850 protocol is used.
The data modelling of IEC 61850 protocol is based on client-server architecture. Each IEC 61850
communicant EPAS sub-system (HMI server, EPAS BCPU, and telecontrol gateway) owns an
IEC 61850 mapping of data which it is server of. A EPAS sub-system is server of a datapoint if it
manages it, that is to say it produces its real-time value (in case of input datapoint such as status,
measurement, counter) or executes its real-time controls (in case of output datapoint such as
binary controls and setpoints).
Connecting MiCOM C264 to other station-bus devices can be done by two ways:
• launching “Data model and data flow update” SCE function at IEDs folder level via its
contextual menu. In that case, SCE is considered as an IEC 61850 System Configuration
Tool (SCT).
• Importing SCD/SSD file to implement a EPAS device from its specification issued from
another IEC 61850 System Configurator, for instance EcoStruxure™ Grid Engineering
Advisor, then launching “Data model and data flow update” SCE function. In that case, SCE is
considered as an IEC 61850 IED Configuration Tool (ICT).
For more details concerning SCT, ICT roles and SCD/SDD importation, refer to chapter
Application of EPAS SCE User Manual (SCE as ICT).
For more details concerning IEC 61850 data model computation for EPAS device, refer to chapter
Application of EPAS SCE User Manual (SCE as ICT).
For more details concerning data flow computation refer to chapter Application of EPAS SCE
User Manual (SCE as ICT).
The tasks of the “Data model and data flow update” SCE function are:
• creating/updating IEC 61850 data model of IEC 61850 devices defined in a SCE configuration
• computing IEC 61850 data flow (Control Block and Client definition) between them, using
EPAS predefined rules.
• updating this data flow in a SCE configuration in SCT mode
• warning missing data flow in a SCE configuration in ICT mode
C264/EN UM/E50.5 601

- Figure 261 - Launching IEC 61850 data model

and dataflow update
7.2.7 Networking IED on computer legacy network

7.2.7.1 Creating a legacy network of IED
Generally, specific devices called relays or IEDs insure protection of electrical modules and bays.
IED connection to EPAS system is commonly done via IED legacy networks managed by EPAS
computer as master.
At SCE data modelling level, up to four IED legacy networks (relevant to a specific protocol) can
be located under a EPAS computer MiCOM C264. Each IED legacy network has to be linked to
communication port embedded in computer boards. Up to sixteen IEDs can be added under a
legacy network.
7.2.7.1.1 Adding a legacy network

To create a legacy network on a computer:
• Add a legacy network relevant to a specific protocol from object entry available at computer
level (1),
• Update the legacy network attributes relevant to its protocol characteristics,
• Update its ‘has for main comm. port’ relation and the communication port characteristics
(refer to "Configuring a communication channel" on page 586),
602 C264/EN UM/E50.5

- Figure 262 - Adding a Legacy network
7.2.7.1.2 Setting general attributes of a legacy network
7.2.7.1.2.1 Serial Port communication
Whatever the kind of legacy network, its short name and long name attributes (1) must be
updated for correct logging and alarm discrimination concerning IED status datapoint connected
to the legacy network.
- Figure 263 - General attributes of a serial Legacy network
7.2.7.1.2.2 Ethernet/IP communication
The DNP3 master protocol can be configured to use either a serial or an IP port. This
configuration is performed through the “Com. Interface” attribute available only for the legacy
DNP3 protocol.
C264/EN UM/E50.5 603

- Figure 264 - General attributes of an IP Legacy network
The protocol’s “main communication port” link is ignored if “Comm. Interface” is set to “Over IP”.
7.2.7.1.3 Setting acquisitions attributes of a IEC 60870-5-103 legacy network

When adding a IEC 60870-5-103 legacy network, the following attributes, available for all its IEDs,
must be updated:
• number of retries (range [1, 10]): number of tries of the same frame without IED response, the
computer will send it before setting it disconnected.
• acknowledgment time-out (range [100 ms, 30 s], step 100 ms): maximum delay an IED
answer is awaited when the computer asks it a information.
• synchronization cycle (range [10 s, 655350 s]): time synchronization period of the IED by the
computer.
• downgraded cycle (range [1 s, 10 s], step 100 ms): if an IED is set disconnected by the
computer, it tries to re-connect it regularly at this cycle.
• inter frame duration (range [1 , 50 ], step 1): this attribute represents the minimum time,
expressed in number of characters, that must exist between two frames.
- Figure 265 - Setting acquisition attributes of a IEC 60870-5-103 Legacy network
7.2.7.2 Setting acquisition attributes of a IEC 60870-5-101 legacy network

must be updated:
• IEC 60870-5-101 time synchro usage (No / Yes): The User can select if the MiCOM C264
shall distribute the time sync request over IEC 60870-5-101 master (Legacy network) or not.
604 C264/EN UM/E50.5

• Time Stamping source (Master / Slave): This attribute is displayed only if “IEC 60870-5-101
time synchro usage” equals “No”. If “Slave” is selected, then the time stamping of data points
is done by the IED and shall not be changed by MiCOM C264 IEC 60870-5-101 master. If IED
sends non-dated data points to MiCOM C264 IEC 60870-5-101 master, then they are time
stamped by MiCOM C264 IEC 60870-5-101 Master. On the contrary, if “Master” is selected,
then the MiCOM C264IEC 60870-5-101 Master considers that all data points provided by the
IED have no timestamp. In this case, the time stamping of the information is always done by
the MiCOM C264 IEC 60870-5-101 Master.
• Time reference (UTC / Local): used to adjust timestamping on IEDs of the legacy network.
- Figure 266 - Setting time synchronization of a IEC 60870-5-101 Legacy network

• number of retries (range [1, 10], step 1): corresponds to the number of tries of the same frame
without IED response, the computer will send it before setting it disconnected.
• station address size (range [1 byte, 2 bytes]): size of the IED addresses
• ASDU address size (range [1 byte, 2 bytes]): size of the ASDU.
• info address size (range [1 byte, 3 bytes]): size of the information addresses.
• transmission cause size (range [1 byte, 2 bytes]): size of the transmission cause.
• frame length (range [64 bytes, 255 bytes]): if an IED cannot manage frame whose length is
superior to 255, the frame length attribute must be set to the available length for the IED.
answer is awaited when the computer asks it an information.
• synchronization cycle (range [10 s, 655350 s], step 10 s): time synchronization period of the
IED by the computer.
• Type of link (Balanced / Unbalanced): if unbalanced link, only master (here computer) asks
IED. If balanced link, IED can also ask the master (here computer) without solicitation.
• test frame time-out (range [1 s, 255 s], step 1 s): in case of ‘balanced link’ (cf. attribute (10)), a
life message (test frame) is sent periodically between computer and IED. This attribute
corresponds to maximum delay to receive this life message, to computer’s point of view. If no
reception within this delay, IED is set disconnected.
C264/EN UM/E50.5 605

• inter frame duration (range [1, 50], step 1): this attribute represents the minimum time,
- Figure 267 - Setting acquisition attributes of a IEC 60870-5-101 Legacy network
7.2.7.2.1 Setting acquisition attributes of a Modbus legacy network

When adding a Modbus legacy network, the following attributes, available for all its IEDs, must be
updated:
answer is awaited when the computer asks it an information.
• synchronization (none / Schneider Electric / SEPAM / Flexgate): refer to chapter
Communication (CT) of MiCOM C264 and the reference document of the connected IED.
IED by the computer. Only significant if attribute (3) is set to ‘Schneider Electric’, 'Flexgate' or
to 'SEPAM'. To keep the Px4x synchronized, MiCOM C264 must send the frame at least
every 5 minutes; therefore, the value must be lesser than 30 in this case.
606 C264/EN UM/E50.5

- Figure 268 - Setting 'acquisition' attributes of a Modbus Legacy network
7.2.7.2.2 Setting acquisition attributes of a DNP3 legacy network

When adding a DNP3 legacy network, the following attributes, available for all its IEDs, must be
updated:
• master address: computer address on the DNP3 legacy network.
answer is awaited when the computer asks it a information.
• application time-out (range [0 s, 255 s], step 1 s): time-out used by the computer, at
application layer of DNP3 protocol.
• class 0 polling period (range [0 s, 3600 s], step 1 s): emission period of the general request
message. If this attribute equals zero, no general request message is sent.
IED by the computer.
- Figure 269 - Setting acquisition attributes of a DNP3 Legacy network
7.2.7.2.3 Adding an IED to a legacy network

To create an IED on a legacy network:
C264/EN UM/E50.5 607

• Add an IED from object entry available at ‘Legacy networks’ level (1).
• Update the IED attributes relevant to its protocol characteristics.
• For DNP3, T103, or Modbus IED, update the ‘has for acquisition profile’ relation with a
previously created IED acquisition type.
- Figure 270 - Adding an IED to a Legacy network
608 C264/EN UM/E50.5

- Figure 271 - Linking IED acquisition profile to an IED
7.2.7.2.4 Setting attributes of a legacy IED

Whatever the kind of IED, the following attributes must be updated:
• short name and long name: used for correct logging and alarm discrimination concerning IED
status datapoint.
• network address of the IED on the legacy network (4 byte-address). the network address is
not used in IEC 60870-5-104 protocol (the relevant information to address the IEC 60870-5-
104 IED are the TCP/IP address and Port number).
• automatic disturbance (No / Yes): not displayed for DNP3 IED. In case of IEC 60870-5-104
IED, the attribute is displayed and can be changed in SCE, but not used in MiCOM C264
because the disturbance is not managed on IEC 60870-5-104.
C264/EN UM/E50.5 609

• localization for disturbance file: non-significant for DNP3 (the disturbance is not managed on
IEC 60870-5-104 (as for DNP3)), used for basic file name upload by CAT on OWS hard disk:
<localization>_N#.
- Figure 272 - Setting general attributes of a Legacy IED

• For each IED, its "network address" and "short name" attributes value must be unique, per
Legacy Network.
• The standard port used for DNP3 is 20000. We highly recommend you use this port number.
7.2.7.2.4.1 Specific attributes for legacy DNP3 over IP IEDs
If the legacy DNP3 protocol is configured as IP, then two more attributes are available in the IED’s
interface:
• TCP/IP address: configures the IP address of the selected IED
• Port number applied to the configured IP address.
- Figure 273 - Setting specific attributes of an IP Legacy IED

• For each IED, its "TCP/IP address" attributes shall be unique, per Legacy Network.
610 C264/EN UM/E50.5

7.2.7.2.4.2 Specific attributes for legacy T104 IEDs
• default ASDU common address: 1…. 65534 If the “common address of ASDU” parameter for
a data point is set to “-1” then the “Default common address of ASDU” is used as “common
address of ASDU” for that data point.
• Port number: applied to the configured IP address. The standard port used for T104 is 2404.
We highly recommend you use this port number
• TCP/IP address: configures the IP address of the selected IED.
7.2.7.2.5 Adding an IED acquisition type to a legacy network

Common acquisition and communication characteristics are shared by IEDs. These ones are
grouped in an object called ‘IED acquisition type’, like acquisition profile. It is available for DNP3,
IEC 60870-5-103 and Modbus protocols.
To create an IED acquisition type on a legacy network:

• Add an IED acquisition from object entry available at legacy network level (1).
• Update the IED acquisition type attributes relevant to its protocol characteristics.
- Figure 274 - Adding an IED acquisition type to a Legacy network (e.g. for DNP3)
C264/EN UM/E50.5 611

• For each computer and all its Legacy Networks, the maximum count of "xxx acq type"
components is 10.
7.2.7.2.6 Setting attributes of a IEC 60870-5-103 acquisition type

When adding a IEC 60870-5-103 acquisition type, the following attributes, available for all its
linked IEDs, must be updated:
• IED type (IEC 60870-5-103 standard IED / Px3x Serie / Px2x Serie / REG-D / Tapcon 240)
• function type (range [0, 255]: function type number used for acquisition: see IED
documentation to set correctly this attribute
• general interrogation period (range [0, 24 h], step 1 s): cycle used to fetch regularly statuses
and measurements from IED and to avoid loss of event information
• MV reduction coefficient (1.2 / 2.4): used for scaling (ASDU 3 usage): refer to IEC 60870-5-
103 documentation for details about this scaling
• Four sets of three nominal values (voltage, current and frequency) used for scaling. Refer to
International Standard IEC 60870-5-103 for details about this scaling.
- Figure 275 - Setting attributes of a IEC 60870-5-103 acquisition type
612 C264/EN UM/E50.5

7.2.7.2.7 Setting attributes of a MODBUS acquisition type

When adding a Modbus acquisition type, the following attributes, available for all its linked IEDs,
must be updated:
• IED type:
Modicon to use the generic Modbus communication (refer to chapter communication of

MiCOM C264)
M300, Px2 series, MiCOM S40 (MiCOM Modbus communication)
M230, Wago, Rish Pro M10, ABB Flexgate, SEPAM (Specific Modbus communication)
• MODBUS function (1 / 2 / 3 / 4 / 7 / 8): function number used for polling frame: To test the
IED connection, this attribute gives which Modbus function is used. For Schneider Electric
IED product, the function 7 is generally used.
• mapping address (range [0, 232-1]): associated to attribute (2), it gives which start address
is used to test the IED connection
if MODBUS function is set to 1 or 2 this attributes defines a bit address
if MODBUS function is set to 3 or 4 this attributes defines a word address
if MODBUS function is set to 5 this attributes is not significant
if MODBUS function is set to 8 this attributes defines a sub-code
if MODBUS function is set to 7 this attributes is not significant

• size to read (range [0, 2048]: associated to attribute (3), it gives which length is used to test
the IED connection.
if MODBUS function is set to 1 or 2 this attributes defines a number of bits
if MODBUS function is set to 3 or 4 this attributes defines a number of words
if MODBUS function is set to 7 or 8 this attributes is not significant

• data frame length (range [2 bytes, 256 bytes]): if an IED cannot manage frames longer than
256 bytes, this attribute must be set to the available length for the IED.
C264/EN UM/E50.5 613

- Figure 276 - Setting attributes of a Modbus acquisition type
7.2.7.2.8 Setting attributes of a DNP3 acquisition type

When adding a DNP3 acquisition type, some attributes available for all its linked IEDs must be
updated:
• global class usage (No / Yes): used for addressing. Not yet implemented. Always considered
as ‘yes’ at computer level.
• synchronization type (Network synchronization / External synchronization): in case of
network’ synchronization, computer synchronizes the time of the IED, otherwise the
synchronization is assumed independently by an external equipment directly connected to
the IED. Not yet implemented. Always considered as ‘Network synchronization’ at computer
level.
• CROB parameters (Usage of 'code' field / Usage of 'Trip/Close' field / Usage of 'code' and
'trip/close' fields):
- Figure 277 - Setting attributes of a DNP3 acquisition type
7.2.7.2.9 Adding Serial Tunneling

Following figures defines how to add serial tunneling to MiCOM C264.
614 C264/EN UM/E50.5

- Figure 278 - Adding serial tunneling
- Figure 279 - Adding serial port to serial tunneling
7.2.7.2.10 Setting acquisition attributes of a IEC 60870-5-104 legacy network

must be updated:
C264/EN UM/E50.5 615

• T0: connection time-out (s): (range [1…255 (s)], step 1 s): Time-out of connection
establishment.
• T1: APDU time-out (s): (range [1….255(s)], step 1 s): Time out of send or test APDUs in
seconds
• T2: acknowledgment time-out (s): (range [1…255 (s)], step 1 s): Time-out for acknowledges
in case of no data messages. t2 < t1
• T3: test frame time-out (s): (range [1…172800 (s)], step 1 s): Time-out for sending test frames
in case of a long idle state, a life message (test frame) is sent periodically between computer
and IED. This attribute corresponds to maximum delay to receive this life message, to
computer’s point of view. If no reception within this delay, IED is set disconnected.
• K: sent unack. Frames (APDU): (range [1…32767], step 1): Window size in number of APDU
for transmitted unacknowledged frames.
• W: ack. Received frames (APDU): range [1…32767], step 1): Window size in number of
APDU for acknowledged received frames.
• synchronization cycle (x10 s): (range [10 s, 655350 s], step 10 s): time synchronization period
of the IED by the computer.
• Originator address: (range [0..255] (0:No originator address)). Originator address of the
IEC 60870-5-104 protocol. To be put in COT of requests sent to slaves.
616 C264/EN UM/E50.5

• Type of counter Interrogation: (range [0…6]): 0-Read Only (Default), 1-Reset Only, 2-Freeze
Only, 3-Reset and Freeze Only ,4-Reset With Read, 5-Freeze With Read and 6-Reset and
Freeze With Read
• Cyclic Counter GI Period: (range [0... 65535], 0 = No cyclic CT GI): If not 0, the Counter GI is
sent just after the global GI.
• Acquisition mode: If 1 then it’s Simplex and if it’s 2 then duplex. (This attribute is Not used for
IEC 60870-5-104)
• Timestamp Tolerancy Window: (range [0...2000]): by default, it is zero. (This attribute is Not
used for IEC 60870-5-104 because no redundancy managed on IEC 60870-5-104)
• IEC 60870-5-104 Profile ("Standard" or "RWE"): Profile of the IEC 60870-5-104 protocol. (At
the moment, this attribute has no impact on the MiCOM C264 behavior)
7.2.7.3 Defining addressing mapping of a legacy IED

To transmit information between IED and EPAS system, an IED legacy network connected to a
EPAS computer is used.
To receive or send information between legacy IED and EPAS system, each concerned data
must have a specific address on the legacy network relatively to its protocol. General modeling of
legacy network address mapping can be done. At SCE level, an IED of a legacy network owns an
“IED mapping” object, that is split in categories of mapping on a per datapoint kind basis. In each
category of mapping, elementary IED addresses can be created. For details about datapoint,
refer to section "Defining datapoint" on page 689. This mapping is implicitly created during the
addition of an IED at legacy network level. Addressing a MPS datapoint on legacy IED is not
available.
- Figure 280 - Structure of the addressing mapping of a Legacy IED (e.g. for T101 IED)
For details about addressing mapping of a given IED on a specific protocol, refer to relay
documentation.
C264/EN UM/E50.5 617


In the IED Mapping, the address identification of each "xxx addr. on IED" must be unique.
• DNP3: address identification is given by the attribute "address" of the "xxx addr. on IED".
• MODBUS: address identification is made of the following combinations of its attribute values:
- { "mapping address" , "function" , "bit number" }
- { "mapping address" , "function" }
• T103: address identification is made of the following combinations of its attribute values:
- { "ASDU number" , "function type" , "information number" , "common address of ASDU" ,
"index in the ASDU" }
- { "ASDU number" , "function type" , "information number" , "common address of ASDU" }
- { "ASDU number" , "function type" , "information number" }
• T101/T104: address identification is made of the following combinations of its attribute values:
- { "information object address" , "common address of ASDU" }
- { "information object address" }
7.2.7.3.1 Defining an IED address for an SPS datapoint

The addition of an IED address for an SPS datapoint is done via the “Objects entry” window at IED
SPS mapping level by clicking on mouse’s right button.
- Figure 281 - Adding an IED SPS address (e.g. for IEC 60870-5-101 IED)
Once added, IED SPS address attributes must be set at SCE level:
• short name: used for internal SCE identification.
For Modbus protocol:

• mapping address (range [0, 65535], step 1): word address or bit address depending on the
function
• bit number (range [0, 65535], step 1): used only if word read or status read is used
618 C264/EN UM/E50.5

• function (range [0, 65535], step 1): number of the Modbus function used to read the SPS:
- 1, 2: read bit,
- 3, 4: read word,
- 7 : read status
For IEC 60870-5-101/IEC 60870-5-104 protocol:

• information object address (range [0, 16777215],step 1).
• common address of ASDU (range [-1, 65535],step 1): by default set to (–1) meaning that the
value set at IED level (Default ASDU common address) is to be used.
For IEC 60870-5-103 protocol:

• ASDU number (range [0, 65535], step 1):
- 1, 2 (for all IED)
- 65,66,67,68 (Only for Px3x)
• function type (range [0, 65535], step 1).
• information number (range [0, 65535], step 1).
• common address of ASDU (range [-1, 65535],step 1): by default (–1) is equal to IED address
(refer to "Setting attributes of a legacy IED" on page 609).
For DNP3 protocol:

• address (range [0, 65535],step 1).
C264/EN UM/E50.5 619

- Figure 282 - Defining an IED address for an SPS datapoint
620 C264/EN UM/E50.5

7.2.7.3.2 Defining an IED address for a DPS datapoint

The addition of an IED address for a DPS datapoint is done via the “Objects entry” window at IED
DPS mapping level by clicking on mouse’s right button.
- Figure 283 - Adding an IED DPS address (e.g. for IEC 60870-5-101 IED)
Once added, IED DPS address attributes must be set at SCE level:
• short name of the address: used for internal SCE identification.

• mapping address (range [0, 65535], step 1): Word address or Bit address depending on the
function.
• bit number (range [0, 65535], step 1): Used only if Word read or status read is used
• function (range [0, 65535], step 1): Modbus function to use to read the DPS:
- 1, 2: read bit,
- 3, 4: read word,
- 7 : read status
For IEC 60870-5-101/IEC 60870-5-104 protocol:

• information object address (range [0, 16777215], step 1).
• common address of ASDU (range [-1, 65535], step 1): by default, set to (–1) meaning that the
For IEC 60870-5-103 protocol:

- 1, 2 (for all IED)
- 65,66,67,68 (Only for Px3x)
• function type (range [0, 65535], step 1): refer to relay documentation.
• information number (range [0, 65535], step 1): refer to relay documentation.
• common address of ASDU (range [-1, 65535],step 1): by default (–1) is equal to IED address
(see section ).
For DNP3 protocol:

• address (range [0, 65535], step 1).
C264/EN UM/E50.5 621

For all protocol types, DPS acquisition on IED can also be done via two different addresses. In
that case, two ‘DPS address on IED’ must be created for this DPS. For each of them, the attribute
contact identifier (12) must be set to ‘Open’ or ‘Closed’, to precise which state of the DPS is
concerned by the IED address. If DPS status is given by only one IED address, set ‘contact
identifier’ value to ‘unused’.
NOTE: "contact identifier" is not used/managed on T104 Protocol.
- Figure 284 - Defining an IED address for a DPS datapoint
622 C264/EN UM/E50.5

7.2.7.3.3 Defining an IED address for an MV datapoint

The addition of an IED address for an MV datapoint is done via the “Objects entry” window at IED
MV mapping level by clicking on mouse’s right button.
Once added, IED MV address attributes must be set at SCE level:


• mapping address (range [0, 65535], step 1): Word address
• function (range [0, 65535], step 1): Modbus function to use to read the MV:
- 3, 4: read word,
- 7 : read status
• data format: see following paragraph (Measurement formats that can be used with the
MODBUS protocol).
For T101/T104 protocol:

For T103 protocol:

- 3, 4, 9 (for all IED)
- 10 (for acquisition of measurement with "generic Services"
- 77 (Only for Px2x)
- 73 (Only for Px3x)
• function type (range [0, 65535], step 1).
• information number (range [0, 65535], step 1).
• index in the ASDU (range [0, 65535], step 1).
• common address of ASDU (range [-1, 65535], step 1): by default (–1) is equal to IED address.
• unit of the MEAS (Voltage / Current / Power / Frequency / No Unit).
• substituted if unknown (No / Yes)
For this protocol it is possible to perform acquisition of measurements only using the Generic
Services of IEC 60870-5-103 protocol by polling. This can be done by setting some parameters as
follows:
• ASDU number: 21
• function type 254
• information number: 244
• index in the ASDU: Generic Identification Number given by the mapping of the IED
For DNP3 protocol:

C264/EN UM/E50.5 623

- Figure 285 - Defining an IED address for an MV datapoint
Measurement formats that can be used with the MODBUS protocol
Because the Modbus norm only describes the transmission of 16 bits values (transmission of the
high order byte first), new formats must be defined to describe the different ways to transmit 32
bits values (whatever their type: signed or unsigned integers, real values) or 8 bits values.
So, the format to apply to an analog input depends on the way it is transmitted and consequently
on the representation of the value in the memory of the device.
In the following table, the “transmission order” column (4) indicates the way a value is transmitted,
i.e. the order in which the bytes of the value are transmitted. The bytes are numbered from 1
(lowest order byte) to 4 (highest order byte).
624 C264/EN UM/E50.5

Transmission
Format Description
order
Transmission of an 8 bit signed integer in a 16 bit value.
INT8_LB /
The significant byte is the low order byte of the word.
Transmission of an 8 bit signed integer in a 16 bit value.
INT8_HB /
The significant byte is the high order byte of the word.
Transmission of an 8 bit unsigned integer in a 16 bit
UINT8_LB value. The significant byte is the low order byte of the /
word.
Transmission of an 8 bit unsigned integer in a 16 bit
UINT8_HB value. The significant byte is the high order byte of the /
word.
Transmission of a 16 bit signed integer. The high order
INT16 2-1
byte is transmitted first (see Modbus standard)
Transmission of a 16 bit unsigned integer. The high
UINT16 2-1
order byte is transmitted first (see Modbus standard)
Transmission of a 32 bit signed integer. The low order
INT32_LW_LB word of the long value is transmitted first. The low order 1-2-3-4
byte of each word is transmitted first.
Transmission of a 32 bit signed integer. The low order
INT32_LW_HB word of the long value is transmitted first. The high order 2-1-4-3
Transmission of a 32 bit signed integer. The high word of
INT32_HW_LB the long value is transmitted first. The low byte of each 3-4-1-2
word is transmitted first.
Transmission of a 32 bit signed integer. The high order
INT32_HW_HB word of the long value is transmitted first. The high order 4-3-2-1
Transmission of a 32 bit unsigned integer. The low order
UINT32_LW_LB word of the long value is transmitted first. The low order 1-2-3-4
Transmission of a 32 bit unsigned integer. The low order
UINT32_LW_HB word of the long value is transmitted first. The high order 2-1-4-3
UINT32_HW_LB order word of the long value is transmitted first. The low 3-4-1-2
order byte of each word is transmitted first.
UINT32_HW_HB order word of the long value is transmitted first. The high 4-3-2-1
order byte of each word is transmitted first.
C264/EN UM/E50.5 625

Transmission
Format Description
order
Transmission of a 32 bit real value. The low order word
REAL32_LW_LB is transmitted first. The low order byte of each word is 1-2-3-4
transmitted first.
Transmission of a 32 bit real value. The low order word
REAL32_LW_HB is transmitted first. The high order byte of each word is 2-1-4-3
transmitted first.
Transmission of a 32 bit real value. The high order word
REAL32_HW_LB is transmitted first. The low order byte of each word is 3-4-1-2
transmitted first.
Transmission of a 32 bit real value. The high order word
REAL32_HW_
is transmitted first. The high order byte of each word is 4-3-2-1
HB
transmitted first.
Transmission of a 32 bit: Unsigned Measure
M230_T5_TYPE Bit 31to 24 decimal exposant (signed 8 bytes) 4-3-2-1
Bit 23…00 binary unsigned value 24 bytes

Transmission of a 32 bit: Signed Measure
M230_T6_TYPE Bit 31to 24 decimal exposant (signed 8 bytes) 4-3-2-1
Bit 23…00 binary signed value 24 bytes

Transmission of a 32 bit: power factor
Bit 31to 24 Signed:Import / Export (00/FF)

M230_T7_TYPE 4-3-2-1
Bit 23…16 Signed:Inductive / capacitive (00/FF)
Bit 15…00 Unsigned value (16 bytes)

Transmission of a 32 bit: ION Energy values
ION_ Bit 31to 16 reg Hight: RH= unsigned value/10000

MODULUS_ Bit 15…00 reg Low: RL = unsigned value modulus 4-3-2-1
10000_unsigned 10000
Value = RH*10000+RL
Transmission of a 32 bit: ION Energy values
Bit 31to 16 reg Hight: RH= signed value/10000

ION_
MODULUS_ Bit 15…00 reg Low: RL = signed value modulus 10000 4-3-2-1
10000_signed
Value = RH*10000+RL
Both reg high and low are signed
7.2.7.3.4 Defining an IED address for a Counter datapoint

The addition of an IED address for a Counter datapoint is done via the “Objects entry” window at
IED Counter mapping level by clicking on mouse’s right button.
626 C264/EN UM/E50.5

- Figure 286 - Adding an IED counter address (e.g. for IEC 60870-5-101 IED)
Once added, an IED Counter address attributes must be set at SCE level:
• short name of the address: used for internalSCE identification.

• mapping address (range [0, 65535], step 1): word address.
• fonction (range [0, 65535], step 1): Modbus function used to read the MV:
- 3, 4: read word
• data format: similar to MV.

For T103 protocol:

• function type (range [0, 65535], step 1):
• information number (range [0, 65535], step 1):
• index in the ASDU (range [0, 65535], step 1):
• common address of ASDU (range [-1, 65535], step 1):
For DNP3 protocol:

• address (range [0, 65535], step 1):
C264/EN UM/E50.5 627

- Figure 287 - Defining an IED address for a counter datapoint
7.2.7.3.5 Defining an IED address for an SPC datapoint

The addition of an IED address for an SPC datapoint is done via the “Objects entry” window at
IED SPC mapping level by clicking on mouse’s right button.
628 C264/EN UM/E50.5

- Figure 288 - Adding an IED SPC address (e.g. for IEC 60870-5-101 IED)
Once added, IED SPC address attributes must be set at SCE level:

• mapping address (range [0, 65535], step 1): Bit address for function 5 or 15, Word address for
function 6.
• bit number (range [0, 65535], step 1): Used only if Function 6 is used (see function attribute).
• function (range [0, 65535],step 1): Modbus function to use to send the SPC:
- 5: write 1 bit (Mapping address indicates the address of the bit),
- 6: write 1 word (Mapping address indicates the address of the word, bit number indicates the
number of the bit in the word),
- 15: write N bits (used to set only 1 bit at a time, Mapping address indicates the address of
the bit)

For T104 protocol:

• dated command (No / Yes) Indicates if the command is dated or not.
For T103 protocol:

- 20 (for all IED)
- 45,46 (Only for Px3x)
For DNP3 protocol:

C264/EN UM/E50.5 629

- Figure 289 - Defining an IED address for an SPC datapoint
7.2.7.3.6 Defining an IED address for a DPC datapoint

The addition of an IED address for a DPC datapoint is done via the “Objects entry” window at IED
DPC mapping level by clicking on mouse’s right button.
630 C264/EN UM/E50.5

- Figure 290 - Adding an IED DPC address (e.g. for IEC 60870-5-101 IED)
Once added, IED DPC address attributes must be set at SCE level:

• mapping address (range [0, 65535], step 1): Bit address for function 5 or 15, Word address for
function 6.
• bit number (range [0, 65535], step 1): used only if Function 6 is used (see function attribute).
• function (range [0, 65535], step 1): Modbus function to use to send the DPC:
- 5: write 1 bit (Mapping address indicates the address of the bit),
- 6: write 1 word (Mapping address indicates the address of the word, bit number indicates
the number of the bit in the word),
- 15: write N bits (used to set only 1 bit at a time, Mapping address indicates the address of
the bit)

For T104 protocol:

• dated command (No / Yes) Indicates if the command is dated or not.
For T103 protocol:

- 20 (for all IED)
- 45,46 (Only for Px3x)
For DNP3 protocol:

For all protocols:
C264/EN UM/E50.5 631

• contact type (open / close / unused): For all protocol type, DPC control on IED can also be
done via two different addresses. In that case, two ‘DPC address on IED’ must be created for
this DPC. For each of them, this attribute must be set to ‘Open’ or ‘Close’, to precise which
order of the DPC is concerned by the IED address. If DPC control is given by only one IED
address, set ‘contact type’ value to ‘unused’.
NOTE: "contact identifier" is not used/managed on T104 Protocol.
632 C264/EN UM/E50.5

- Figure 291 - Defining an IED address for a DPC datapoint
7.2.7.3.7 Defining an IED address for a SetPoint datapoint

The addition of an IED address for a SetPoint datapoint is done via the “Objects entry” window at
IED SetPoint mapping level by clicking on mouse’s right button.
C264/EN UM/E50.5 633

- Figure 292 - Adding an IED Setpoint address (e.g. for IEC 60870-5-101 IED)
Once added, IED SetPoint address attributes must be set at SCE level:
SetPoint address on Modbus is only available for WAGO relay, where output format is fixed to
UINT15 (unsigned integer, only 15 out of 16 bits are used). The IED type must be set to WAGO.
• mapping address (range [0, 65535], step 1): Word address for function 6.
• function (range [0, 65535], step 1): Modbus function to use to send the SetPoint:
- 6: write 1 word (Mapping address indicates the address of the word; bit number indicates the
number of the bit in the word).
• - 16: write N word (Mapping address indicates the address of the word; bit number indicates
the number of the bit in the word).
• output format (Normalized/Scaled/Natural): Output format data in transmission
• coding format: (INT16, UINT16, REAL32_LW_LB, REAL32_LW_HB, REAL32_HW_LB,

REAL32_HW_HB]): For details on formats, see § “Analogue Input” in chapter “Modbus” of
Master Protocol Profile (MPP) user guide.

• output format (REAL32 (IEEE 754) / Normalized / Scaled).
For T104 protocol:

• dated command (No / Yes) Indicates if the command has to be dated or not.
For T103 protocol:

• SetPoint address on T103 is only available for REGD relay, where output format is
configurable.
• ASDU number (range [0, 65535], step 1): refer to relay documentation.
634 C264/EN UM/E50.5

• output format (INT8 / UINT8 / INT16 / UNIT16 / REAL32 (IEEE754))
For DNP3 protocol:

For all protocol type, values of SetPoint control on IED must be verified and scaled depending on
output format, before transmission. This is done via two extra attributes ‘minimal value’ (11) and
‘maximal value’ (12).
C264/EN UM/E50.5 635

- Figure 293 - Defining an IED address for a Setpoint datapoint
636 C264/EN UM/E50.5

7.2.8 Networking SCADA on computer SCADA network

7.2.8.1 Creating a SCADA network
An electrical substation can be supervised and controlled from many points inside the substation
via EPAS operator interfaces (Substation Control Point or SCP) and/or EPAS computer bay
panels (Bay Control Point or BCP), and outside the substation. Generally, the distant control of
the substation (Remote Control Point or RCP) is done via specific networks called SCADA legacy
network.
Several SCADA legacy networks can be connected to a EPAS system, via EPAS computer or
EPAS telecontrol gateway sub-systems. SCADA legacy networks are managed as master by
distant SCADA and can be redundant for safety reason. A EPAS computer can manage up to two
SCADA networks.
At SCE data modeling level, only SCADA legacy networks and their protocol are modeled and
connected to gateway sub-systems. Each SCADA network has to be linked to a main
communication port and an optional auxiliary communication port in case of redundancy.
7.2.8.1.1 Adding a SCADA network

To create a SCADA network on a computer:
• Add a SCADA network from object entry available at computer level (1),
• Update the SCADA network attributes relevant to its protocol characteristics (see section
Defining addressing mapping of SCADA network).
• If SCADA does not use the substation network to communicate with the computer, update its
‘has for main communication port’ relation and the communication port characteristics.
• For DNP3 and IEC 60870-5-101 protocol on serial line, SCADA link can be redundant. To
create a redundant SCADA link, just add the relation ‘has for auxiliary communication port’ (2)
extra relation on computer SCADA network and fill it with the relevant serial port.
• A computer can manage up to two IEC 60870-5-104 SCADA clients. These two clients have
separate configurations but may have same data. On the SCADA port, up to four front ends
can be defined, corresponding to one active port and three backup ports. So, up to four IP
addresses will be defined during the configuration of each IEC 60870-5-104 client (attributes
(13) in section "Adding a SCADA network" on page 637). If both clients are communicating
with the computer, they must manage their own redundancy for doing controls with
coherency.
C264/EN UM/E50.5 637

- Figure 294 - Adding a SCADA network
- Figure 295 - Creating a redundant SCADA link
7.2.8.1.2 Setting general attributes of a SCADA network

Whatever the kind of SCADA network, its short name and long name attributes (1) must be
updated for correct logging and alarm discrimination concerning status datapoints managed by
the computer for each connected SCADA network. Then the supported protocol (2) must be
selected (IEC 60870-5-101 in the example given hereafter). So, the SCADA attributes tab-panes
(Protocol, SOE and Disturbance) are refreshed relatively to the selected protocol.
- Figure 296 - Setting general attributes of a SCADA network
638 C264/EN UM/E50.5

7.2.8.1.3 Setting general attributes of a IEC 60870-5-101 SCADA network

When adding a IEC 60870-5-101 SCADA network its general attributes must be updated (refer to
the previous figure)
• redundancy type (Active line after GI received / Active line after Reset line received / Active
line on traffic)
• time reference (UTC / local)
7.2.8.1.4 Setting specific attributes of a IEC 60870-5-101 SCADA network

When adding a IEC 60870-5-101 SCADA network, the following attributes available for this
protocol must be updated (Protocol and SOE tab-panes):
• link address length (1 byte / 2 bytes)
• link address (range [1, 65534], step 1)
• ASDU common address length (1 byte / 2 bytes)
• ASDU common address (range [1, 65534], step 1)
• address structure (Address on 8 bits (1 byte) / Address on 16 bits (2 bytes) / Address on 8

bits.8 bits / Address on 8 bits.16 bits / Address on 16 bits.8 bits / Address on 8 bits. 8 bits. 8
Bits / Address on 24 bits (3 bytes))
• frame max length (range [1, 255], step 1)
• cause of transmission length (Address on 8 bits / Address on 16 bits)
• MV periodic cycle (range [0 s, 65534 s], step 1 s)
• binary time size (CP24Time2A (3 bytes) / CP56Time2A (7 bytes))
• background scan cycle (range [0 s, 65535 s], step 1 s)
• type of link (unbalanced / balanced)
• T3: test frame time-out (range [1 s, 255 s], step 1 s)
• SBO time-out (range [0 s, 65535 s], step 1 s)
• interframe duration (range [1, 50], step 1): this attribute represents the minimum time,
expressed in number of characters, that must exist between two frames
• Quality value for 'Jammed' state (valid / IV invalid): this attribute defines the value of the
Quality Descriptor field when the event to transmit is in the 'Jammed' state.
• Quality value for 'Undefined' state (valid / IV invalid): this attribute defines the value of the
Quality Descriptor field when the event to transmit is in the 'Undefined' state.
• Quality value for toggling xPS (BL only (blocked) / IV only (invalid): this attribute defines the
value of the Quality Descriptor field when the event to transmit is an xPS in the TOGGLING
state.
• Quality value for 'Unknown' state (Not topical only / Not topical and IV invalid): this attribute
defines the value of the Quality Descriptor field when the event to transmit is in the 'Unknown'
state.
• SOE file support (No / Yes)
C264/EN UM/E50.5 639

• SOE file address: this attribute is visible and significant only if attribute SOE file support is set
to Yes
• SOE file format (T101 / S900) this attribute is visible and significant only if attribute SOE file
support is set to Yes
• SOE file nb of events (range [0, 1000], step 1) this attribute is visible and significant only if
attribute SOE file support is set to Yes
• 'full' SOE file nb of events (range [0, 1000], step 1) file message sent to SCADA (this attribute
is visible and significant only if attribute SOE file support is set to Yes)
• Disturbance file address for slow or fast wave
• Buffer overflow: Yes / No
- Figure 297 - Setting protocol and SOE attributes of a IEC 60870-5-101 SCADA network
The following constraints between the attributes must be respected:

"SOE file nb of events" > "'full' SOE file nb of events".
640 C264/EN UM/E50.5

7.2.8.1.5 Setting general attributes of a DNP3 SCADA network

In the following figure the selected protocol for the SCADA link is ‘DNP3’.
7.2.8.1.5.1 How to Set the General Attributes of a DNP3-IP SCADA Network
When you set a DNP3 SCADA network, some specific attributes available for the protocol must
be updated (Protocol tab-pane):
- Figure 299 - Defining DNP-IP Configuration

• TCP/IP usage (No / Yes): set to ‘Yes’ substation network is used by the DNP3-IP SCADA to
communicate with the computer
• Link address (1..65534)
• SPS/DPS class (1 / 2 / 3)
C264/EN UM/E50.5 641

• MV class (1 / 2 / 3)
• SPS/DPS class (1 / 2 / 3)
• Counter class (1 / 2 / 3)
• MV format (32 bits / 16 bits)
• static MV (without flag / with flag)
• event MV (without time, with time)
• counter format (32 bits / 16 bits)
• static counter (without flag / with flag)
• event counter (without time, with time)
• SBO time-out: maximum time between select order and execute order
expressed in number of characters, that must exist between two frames
• spontaneous message enable (No / Yes): this attribute defines if the unsolicited mode is
allowed or not for the protocol. If this attribute is set to No there is possibility to allowed it from
the SCADA. If this attribute is set to Yes the computer can send unsolicited messages as
soon as the SCADA is initialized. Furthermore, the SCADA may disable or enable this
unsolicited mode.
• spontaneous message class (none / class 1 / class 2 / class 1 & 2 / class 3 / class 1 & 3 / class
2 & 3 / class 1 & 2 & 3): This attribute is only significant if the previous attribute is set to Yes.
This attribute defines which class(es) is (are) concerned by this unsolicited mode.
• On-line bit Management (Unknown forced to 1 (default value) / Unknown forced to 0): this
attribute defines the DNP3 object flag ONLINE. It defines two modes of management for the
On-line Quality: Mode 1 and Mode 2.
- The Mode 1 is defined with DNP3 COMM_LOST flag (communication failure) set to
“Unknown forced to 1” and ONLINE flag set to “Unknown forced to 1”.
- The Mode 2 is defined with DNP3 COMM_LOST flag (communication failure) set to
“Unknown forced to 1” and ONLINE flag set to “Unknown forced to 0”.
Setting SOE information SOE tab-panes, for DNP3-IP SCADA network is not significant (not
implemented).
7.2.8.1.6 Setting specific attributes of a IEC 60870-5-104 SCADA network

In the following figure the selected protocol for the SCADA link is “T104” and the selected time
reference is “UTC”.
642 C264/EN UM/E50.5

When adding a IEC 60870-5-101 SCADA network, the following attributes available for this
protocol must be updated (Protocol and SOE tab-panes):
• ASDU common address (range [1, 65534], step 1)
• address structure (Address on 8 bits.16 bits / Address on 16 bits.8 bits /

Address on 8 bits.8bits.8bits / Address on 24 bits (3 bytes)).
• frame max length (range [1, 255], step 1)
• MV periodic cycle (range [0 s, 65534 s], step 1 s)
• binary time size (CP24Time2A (3 bytes) / CP56Time2A (7 bytes))
• background scan cycle (range [0 s, 65535 s], step 1 s)
• T0: connection time-out (range [1 s, 255 s], step 1 s)
• T1: APDU time-out (range [1 s, 255 s], step 1 s)
• T2: acknowledgement time-out (range [1 s, 255 s], step 1 s)
• T3: test frame time-out (range [1 s, 255 s], step 1 s)
• K: sent unack. frames (APDU) (range [1, 255], step 1)
• W: ack. received frames (APDU) (range [1, 255], step 1)
• max command delay (range [0 s, 32767 s], step 1 s)
• Client #i IP address (i Î [1, 4])
• SBO time-out (range [0 s, 65535 s], step 1 s)
• Quality value for 'Jammed' state (valid / IV invalid): this attribute defines the value of the
Quality Descriptor field when the event to transmit is in the 'Jammed' state.
• Quality value for 'Undefined' state (valid / IV invalid): this attribute defines the value of the
Quality Descriptor field when the event to transmit is in the 'Undefined' state.
• Quality value for toggling xPS (BL only (blocked) / IV only (invalid): this attribute defines the
value of the Quality Descriptor field when the event to transmit is an xPS in the TOGGLING
state.
• Quality value for 'Unknown' state (Not topical only / Not topical and IV invalid): this attribute
defines the value of the Quality Descriptor field when the event to transmit is in the 'Unknown'
state.
• Switchover (Automatic switchover / Manual switchover)
C264/EN UM/E50.5 643

- Figure 301 - Setting protocol attributes of a IEC 60870-5-104 SCADA network

• SOE file support (No / Yes)
• SOE file address (this attribute is visible and significant only if attribute SOE file support is set
to Yes)
• SOE file format (T101 / S900) (this attribute is visible and significant only if attribute SOE file
support is set to Yes)
• SOE file nb of events (range [0, 1000], step 1) (this attribute is visible and significant only if
attribute SOE file support is set to Yes)
• 'full' SOE file nb of events (range [0, 1000], step 1) file message sent to SCADA (this attribute
is visible and significant only if attribute SOE file support is set to Yes)
- Figure 302 - Setting SOE attributes of a IEC 60870-5-104SCADA network
644 C264/EN UM/E50.5

• Disturbance file address for IEC 60870-5-103, S20, M300, SlowWave and FastWave (this
attribute panel is visible and significant only when supported protocol is IEC 60870-5-101 or
IEC 60870-5-104
- Figure 303 - Setting disturbance attributes of a IEC 60870-5-104SCADA network

• Buffer overflow support (No (default) / Yes). Configures the use of a Buffer Overflow Flag.
Details on this attribute can be found in section 2.6.26 of “SPP T104” documentation.
• Buffer overflow address (This attribute to allocate a SCADA address to the information buffer
overflow. A SCE check ensure the address is unique.
• Buffer overflow empty condition (Without emptying / “Fifo full / SCADA (re)connection” / Fifo
full only) Attribute to set-up the condition of flush of the buffer of events, three possibilities:
Without The buffer is managed as a circular list. Upon overflow, the oldest
emptying element will be replaced by the new one.
The buffer is managed as a linear FIFO list. Upon buffer overflow, new
“Fifo full / SCADA
events are ignored. At SCADA reconnection the Buffer Overflow Flag is sent
(re)connection”
to the SCADA and the buffer is flushed without being sent to SCADA
The buffer is managed as a linear FIFO list. Upon buffer overflow, new
Fifo full only events are ignored. At SCADA reconnection the Buffer Overflow Flag is sent
to the SCADA followed by all the events in the list.
NOTE: In case of SCADA disconnection, the buffer records events at substation level in order to
transfer them to the SCADA at reconnection time. The size of the buffer is not configurable, and
it is limited to 1000 events.
- Figure 304 - Setting buffer overflow attributes of a IEC 60870-5-104SCADA network

• The following constraints between the attributes must be respected:
"SOE file nb of events" > "'full' SOE file nb of events"
"T2" < "T1"
"T3" > "T1"
"W" ≤ "K"
C264/EN UM/E50.5 645

7.2.8.1.7 Setting specific attributes of a MODBUS SCADA network

In the following figure the selected protocol for the SCADA link is ‘Modbus’.
- Figure 305 - Setting protocol type of a SCADA network
When setting a MODBUS SCADA network, some specific attributes available for the protocol
must be updated (Protocol tab-pane):
• link address.
• inter frame duration (range [1 , 50 ], step 1): this attribute represents the minimum time,
For a MODBUS SCADA network, the SOE tab-panes attributes are not significant (not
implemented).
- Figure 306 - Setting protocol attributes of a MODBUS SCADA network
7.2.8.2 Defining addressing mapping of SCADA network

To transmit information between EPAS system and SCADA, a SCADA legacy network is used. To
receive or send information between legacy IED and EPAS system, each concerned data must
have a specific address on the legacy network relatively to its protocol. General modeling of
SCADA legacy network address mapping can be done. At SCE level, a SCADA legacy network
owns a “SCADA mapping” object, that is split in categories of mapping on a per datapoint kind
646 C264/EN UM/E50.5

basis. In each category of mapping, elementary SCADA addresses can be created. For details
about datapoint, refer to "Defining datapoint" on page 689. This mapping is implicitly created
during IED adding at legacy network level.
NOTE: Addressing an MPS datapoint on a SCADA network is not available.
- Figure 307 - Structure of the addressing mapping of a SCADA network

• In the SCADA Mapping, the address identification of each "Gtw xxx addr." must be unique. In
the particular cases of IEC 60870-5-101 and IEC 60870-5-104 protocols, the uniqueness
constraint is applicable only for addresses of the same type. Addresses of different types can
have identical addresses and therefore this does not lead to an error but to a warning.
• On a DNP3 protocol, a "Gtw MV addr.", which is the SCADA address of a "Tap pos ind"
datapoint, must have its "Format" attribute set to the "Natural" value.
7.2.8.2.1 Defining a SCADA address for an SPS datapoint

The addition of a SCADA address for an SPS datapoint is done via the “Objects entry” window at
SCADA SPS mapping level by clicking on mouse’s right button.
C264/EN UM/E50.5 647

- Figure 308 - Adding a SCADA SPS address
Once added, SCADA SPS address attributes must be set at SCE level:
• shortname of the address used for internal SCE identification.

• object address - register

• object address.
• Event (No / Yes with time tag / Yes witout time tag): when set to ‘Yes with time tag’, indicates
that change of state of the datapoint are transmitted spontaneously with time Tag.
• Event record ( Does not involved in a transfert of file / Create a RECORD EVENT if there is
not it current / Add to the current record EVENT / Create a RECORD EVENT and adds to the
current record EVENT): when set to a value different from ‘Does not involved in a transfer of
file’, indicates if change of state of the datapoint must be saved in Sequence of Event file. At
computer level, values different from ‘Does not involved in a transfer of file’ are associated to
the same treatment, because only one SOE file is managed by computer. The set of available
values is maintained for compatibility with MiCOM gateway addressing in MiCOM gateway.
• Inversion (No / Yes): Indicates that the datapoint value needs to be inverted before
transmission.
• Background scan (No / Yes): indicates if the datapoint belongs to the background scan cycle.
• Group ([0..16)] / 0=no group): indicates to which “T101/T104 General Interrogation group” the
datapoint is assigned. 0 means ‘no group’ assignation.
648 C264/EN UM/E50.5

For DNP3 protocol:

• object address - index.
• Event (No / Yes with time tag): when set to ‘Yes with time tag’, indicates if change of state of
the datapoint are transmitted spontaneously with time Tag.
• Inversion (No / Yes): indicates that the datapoint value needs to be inverted before
transmission.
- Figure 309 - Defining a SCADA address for an SPS datapoint
7.2.8.2.2 Defining a SCADA address for a DPS datapoint

The addition of a SCADA address for a DPS datapoint is done via the “Objects entry” window at
SCADA DPS mapping level by clicking on mouse’s right button.
C264/EN UM/E50.5 649

- Figure 310 - Adding a SCADA DPS address
Once added, SCADA DPS address attributes must be set at SCE level:
• short name: used for internal SCE identification

• double address usage (No / Yes): only available for Modbus SCADA protocol. If set to ‘Yes’,
DPS is transmitted to SCADA via two distinct SCADA address, one for the open state, the
other one for the close state.
• object address - register: used if ‘Double address usage’ is set to ‘No’.
• open state address: used if ‘Double address usage’ is set to ‘Yes’. This attribute defines the
SCADA address for the open state of the DPS.
• Closed state address: used if ‘Double address usage’ is set to ‘Yes’. This attribute defines the
SCADA address for the closed state of the DPS.

• Event (No / Yes with time tag /Yes without time tag): when set to ‘Yes with time tag’, indicates
if change of state of the datapoint are transmitted spontaneously with time Tag.
• Event record (Does not involved in a transfert of file / Create a RECORD EVENT if there is not
it current / Add to the current record EVENT / Create a RECORD EVENT and adds to the
current record EVENT): when set to a value different from ‘Not involved in a transfer of file’,
indicates if change of state of the datapoint must be saved in Sequence of Event file. At
computer level, values different from ‘Not involved in a transfer of file’ are associated to the
same treatment, because only one SOE file is managed by computer. The set of available
values is maintained for compatibility with MiCOM gateway addressing in MiCOM gateway.
650 C264/EN UM/E50.5

transmission.
• Background scan: (No / Yes): indicates if the datapoint belongs to the background scan cycle.
• Group ([0..16)] / 0=no group): indicates to which “T101/T104 General Interrogation group” the
datapoint is assigned. 0 means ‘no group’ assignation
• object address (index)
For DNP3 protocol:

the datapoint are transmitted spontaneously with time Tag
transmission
• object address - index
- Figure 311 - Defining a SCADA address for a DPS datapoint
C264/EN UM/E50.5 651

7.2.8.2.3 Defining a SCADA address for a MV datapoint

The addition of a SCADA address for a MV datapoint is done via the “Objects entry” window at
SCADA MV mapping level by clicking on mouse’s right button.
- Figure 312 - Adding a SCADA MV address
Once added, SCADA MV address attributes must be set at SCE level:

• short name of the address used for internal SCE identification.

• Format (Natural / Unsigned normalized / Signed normalized /Real IEEE754 – little endian /
Real IEEE754 – big endian): transmission format.
• Precision (8..16): number of transmitted bits.

• object address.
• Event (No / Yes with time tag / Yes without time tag): when set to ‘Yes with time tag’, indicates
that change of state of the datapoint are transmitted spontaneously with time Tag.
• Event record (No / Yes): indicates if change of state of the datapoint must be saved in
Sequence of Event file or not..
• Format (Normalized / Adjusted / Float): transmission format.
• cycle type (None / Periodic / Background scan): indicates which transmission cycle the MEAS
belongs to.
652 C264/EN UM/E50.5

• Group ([0..16)] / 0=no group): indicates which “T101/T104 General Interrogation group” the
datapoint is assigned to. 0 means ‘no group’ assignation.
For DNP3 protocol:

• object address
• Format (Natural / Adjusted).
- Figure 313 - Defining a SCADA address for a MV datapoint
7.2.8.2.4 Defining a SCADA address for a Counter datapoint

The addition of a SCADA address for a Counter datapoint is done via the “Objects entry” window
at SCADA Counter mapping level by clicking on mouse’s right button.
C264/EN UM/E50.5 653

- Figure 314 - Adding a SCADA counter address
Once added, SCADA Counter address attributes must be set at SCE level:

• Format (Natural / Unsigned normalized / Real IEEE754 – little endian / Real IEEE754 – big
endian): transmission format.

• object address.
• Event (No / Yes with time tag / Yes without time tag): when set to ‘Yes with time tag’, indicates
if changes of state of the datapoint are transmitted spontaneously with time Tag.
• Group ([0..4] / 0=no group): indicates which “T101/T104 General Interrogation group” the
datapoint is assigned to. 0 means ‘no group’ assignation.
For DNP3 protocol:

• object address.
654 C264/EN UM/E50.5

- Figure 315 - Defining a SCADA address for a counter datapoint
7.2.8.2.5 Defining a SCADA address for a SPC datapoint

The addition of a SCADA address for a SPC datapoint is done via the “Objects entry” window at
SCADA SPC mapping level by clicking on mouse’s right button.
C264/EN UM/E50.5 655

- Figure 316 - Adding a SCADA SPC address
Once added, SCADASPC address attributes must be set at SCE level:


• object address - register.

• object address
• SCADA execute order type (Select execute / Direct execute): precise if SCADA uses a ‘Select
execute” or a ‘Direct execute’ sequence to send control on the datapoint.
For DNP3 protocol:

• object address
• SCADA execute order type (Select execute / Direct execute): precise if SCADA uses a ‘Select
execute” or a ‘Direct execute’ sequence to send control on the datapoint.
656 C264/EN UM/E50.5

- Figure 317 - Defining a SCADA address for a SPC datapoint
7.2.8.2.6 Defining a SCADA address for a DPC datapoint

The addition of a SCADA address for a DPC datapoint is done via the “Objects entry” window at
SCADA DPC mapping level by clicking on mouse’s right button.
C264/EN UM/E50.5 657

- Figure 318 - Adding a SCADA DPC address
Once added, SCADA DPC address attributes must be set at SCE level:


• object address.
• SCADA execute order type (Select execute / Direct execute): precises if SCADA uses a
‘Select execute” or a ‘Direct execute’ sequence to send control on the datapoint.
For DNP3 protocol:

• object address in [0..65535].
658 C264/EN UM/E50.5

- Figure 319 - Defining a SCADA address for a DPC datapoint
7.2.8.2.7 Defining a SCADA address for a SetPoint datapoint

The addition of a SCADA address for a SetPoint datapoint is done via the “Objects entry” window
at SCADA SetPoint mapping level by clicking on mouse’s right button.
C264/EN UM/E50.5 659

- Figure 320 - Adding a SCADA setpoint address
Once added, SCADA SetPoint address attributes must be set at SCE level:

• format.(signed 16 bits / Real IEEE754 – little endian: the lower byte is transmitted first / Real
IEEE754 – big endian: the higher byte is transmitted first)

• object address.
• SCADA execute order type (Select execute / Direct execute): this attribute defines if SCADA
uses a ‘Select execute” or a ‘Direct execute’ sequence to send control on the datapoint.
• Minimal value: available minimal value on the protocol (used for scaling and checks).
• Maximal value: available maximal value on the protocol (used for scaling and checks).
• Format (Normalized / Adjusted / Float).
For DNP3 protocol:

• object address [0..65535].
660 C264/EN UM/E50.5

• minimal value: available minimal value on the protocol (used for scaling and checks).
• maximal value: available maximal value on the protocol (used for scaling and checks).
• format (Natural / Adjusted).
- Figure 321 - Defining a SCADA address for a setpoint datapoint
7.2.8.2.8 Defining a SCADA address for bypass synchrocheck

For details about synchronized circuit-breakers, refer to "Defining a Synchrocheck function" on
page 780.
Synchronized circuit-breaker can be controlled through SCADA network. In that case, the SPC
(resp. DPC) control of the synchronized breaker is linked to a SCADA SPC (resp. DPC) address.
Unfortunately, bypass synchrocheck is not implemented in SCADA protocol. To solve this
problem, an extra SCADA SPC (resp. DPC) address that will bypass the synchrocheck must be
given to the SPC (resp. DPC) control of the breaker. At SCE level, this extra address is linked to
the SCADA address of the SPC (resp. DPC) control of the synchronized breaker.
To define a SCADA address for bypass synchrocheck:

• Create the SCADA SPC (resp. DPC) address (A) to send SPC (resp. DPC) control of the
synchronized breaker.
C264/EN UM/E50.5 661

• Create a SCADA SPC (resp. DPC) address (B) for bypass synchrocheck in the SCADA
mapping.
• Add the relation ‘has for bypass synchrocheck address’ via the “Objects entry” window at
SCADA address (A) and fill it with the SCADA address (B).
- Figure 322 - Adding a bypass S/C address to a SCADA SPC/DPC address (e.g. for DPC)
7.2.8.3 How to configure a mapping of a SCADA network

When a SCADA network is selected in the browser an extra item in its contextual menu is
available “Edit Scada mapping”. When selected, a modal window appears. It displays all
addresses existing under the mapping of the SCADA. The addresses are grouped by type; five
types exist:
• xPS present SPS / DPS addresses
• xPC present SPC / DPC addresses
• MV present measurement addresses
• SetPoint present SetPoint addresses
• Counter present Counter addresses
The following protocols of gateway: IEC 61850 and GI74 are not concerned by this edition.
Each tab present addresses datapoint data in left part of the table and address data in the right
part of the table.
For datapoint data, attributes displayed are:

• Kind
• Path
662 C264/EN UM/E50.5

• Short name
• Long name
For address data, attributes displayed are different for each type of protocol. For MODBUS C26x
protocol sample, attributes are:
• For xPS:
Addr: value of the SCADA address, only active for SPS address, or DPS address if
Double address usage is set to ‘No’.
Close Addr: value of the close state address for DPS address, only active for a DPS
address if Double address usage is set to ‘Yes’.
Open Addr: value of the open state address for DPS address, only active for a DPS
address if Double address usage is set to Yes’.
Double address: flag to indicate if the address is double or not, only active for a DPS
address.
• For xPC:
Addr: value of the SCADA address.

• For MV:
Format: format of the SCADA address.
Precision: accuracy of the analog input point in number of bits.

• For Counter:
Format: format of the SCADA address.

• For SetPoint:
Format: format of the SCADA address
C264/EN UM/E50.5 663

- Figure 323 - SCADA mapping address
7.2.8.4 Addressing datapoint on SCADA legacy network

For details about datapoint, refer to section "Defining datapoint" on page 689.
To exchange datapoint values between station-bus sub-systems and SCADA, datapoints should
be linked to specific SCADA addresses, by adding at datapoint level the relation ‘has for SCADA
address’ (1) and filling it with the corresponding SCADA address in a pre-configured SCADA
addressing mapping (refer to "Defining addressing mapping of SCADA network" on page 646).
Addressing MPS datapoint on the SCADA legacy network is not available.
664 C264/EN UM/E50.5

- Figure 324 - Realizing SCADA addressing of a datapoint (e.g. for bay SPS datapoint)
7.2.9 Defining a time synchronization for an EPAS network

EPAS SCE allows the setting of different time management protocols for IEC 61850 IEDs, for
more information about time management for BCPU refer to the Time Management section in FT
chapter.
7.2.9.1 Setting a SNTP time synchronization

To synchronize IEC 61850 devices via SNTP time synchronization on a specific IEC 61850
network:
For each Access Point (AP) of these devices connected to the IEC 61850 network, via the relation
‘is connected to’, set the attribute relation ‘SNTP server usage’ to the following values:
• Not used if the device can only be SNTP client
• Main SNTP Server if the device is considered as the main SNTP server for this network
• Auxiliary SNTP Server if the device is considered as the auxiliary SNTP server for this
network
- Figure 325 - Defining SNTP attributes at network level
C264/EN UM/E50.5 665

7.2.9.2 Setting an IEC 61588 time synchronization

To synchronize IEC 61850 devices via IEC 61588 time synchronization on a specific IEC 61850
network:
• At IEC 61850 Network level, in ‘IEC 61588’ tab pane, set the following attributes:
Parameters at network Default

Value Comment
level SCE Attribute name value
Yes IEC 61588 synchronisation mechanism is
IEC 61588 synchro usage No
No inactive.
If IEC 61588 synchro usage is set to yes, the following attributes appear
End to
Transparent clock end End to It is mandatory to set this attribute on Peer to
mechanism Peer to end Peer for transparent clock mechanism
peer
Yes
VLAN usage No VLAN used for IEC 61588 Synchro.
No
Integer 0
VLAN priority 4 VLAN priority, 7 it’s the highest priority.
to 7
Parameters at network
Value Default value Comment
level SCE Attribute name
Yes IEC 61588 synchronisation
IEC 61588 synchro usage No
No mechanism is inactive.
If IEC 61588 synchro usage is set to yes, the following attributes appear
It is mandatory to set this
Transparent clock End to end attribute on Peer to Peer for
End to end
mechanism Peer to peer transparent clock
mechanism
Yes VLAN used for IEC 61588
VLAN usage No
No Synchro.
VLAN priority, 7 it’s the

VLAN priority Integer 0 to 7 4
highest priority.
- Figure 326 - Defining IEC 61588 attributes at network level

• For each Access Point (AP) of these devices connected to the IEC 61850 network, via the
relation ‘is connected to’, set the relation attributes in ‘IEC 61588’ tab pane to the following
values:
666 C264/EN UM/E50.5

Master support
Priority 1 & 2 priority criteria’s regarding election of the Great Master Clock
- Figure 327 - Defining IEC 61588 attributes at AP level
7.2.10 Defining wave record file management

The MiCOM C264 computers manage two kinds of wave recording file:
• IED connected to computer legacy network can produce disturbance files. In that case,
computer monitors their availability. As soon as available, they are uploaded and stored at
computer level. Computer computes for Computer Administration Tool (CAT) a real-time data
per IED basis that gives the availability of a disturbance file, via station-bus network. Then,
CAT downloads it from computer. At the end of successful downloading, computer erases the
real-time data of availability.
• Via a CT/VT board (TMU220), computer can manage its own waveform record files.
Waveform channels are directly acquired on CT/VT board channels and buffered. Triggered
by pre-defined change of state, associated buffers are flushed on files that correspond to
waveform record files. In that case computer computes for DRM a real-time data that gives
the availability of a computer waveform record file, via station-bus network. Then processing
is similar to IED’s one.
7.2.10.1 Defining management of disturbance file for IED

Allowing computer to manage IED disturbance is done at IED configuration level by:
• Setting its ‘automatic disturbance’ attribute to yes.
• Adding the system SPS datapoint ‘DREC ready’ (2) at IED level, linked to a pre-defined
datapoint profile.
• Launching “Data model and data flow update” SCE function (refer to "Connecting a BCPU to
an IEC 61850 Station Bus network" on page 600), to get the IEC 61850 address of this SPS.
For IEC 60870-5-103 IED extra information must be configured to process correct disturbance file
COMTRADE structure at computer level (see following section).
7.2.10.2 Defining IEC 60870-5-103 IED extra information for disturbance file
IEC 60870-5-103 extra informations for disturbance file are located at IEC 60870-5-103
acquisition type and concern definition of analog and digital channels, stored in disturbance file,
relatively to COMTRADE format.
7.2.10.2.1 Adding an analog channel definition

The addition of an analog channel definition for IEC 60870-5-103 is done via the “Objects entry”
window at IEC 60870-5-103 acquisition type level by clicking on mouse’s right button. Up to 15
analog channels can be created under a IEC 60870-5-103 acquisition type.
C264/EN UM/E50.5 667

- Figure 328 - Adding an IEC 60870-5-103 analog channel definition
Once added, channel definition attributes must be set at SCE level:

• channel label.
• long name of the channel used for internal SCE identification.
• phase name: label of the phase corresponding to the channel.
• channel number: (cf. mapping IED– field ACC in IEC 60870-5-103 documentation).
• unit: unit corresponding to the channel.
• coefficient (0: not used): value which the samples must be multiplied by in order to get the real
value (0: not used). Generally, data uploaded from IED allows to compute this ‘multiply
coefficient’. Unfortunately, some IED don’t give correct data. In this case, this coefficient must
be set here.
• shift time (range [0 s, 1 s], step 1 ms): elapsed time since the beginning of the sampling
period.
• maximal sample value (range [0 , 32767], step 1).
• minimal sample value (range [-32768, 0], step 1).
- Figure 329 - Setting IEC 60870-5-103 analog channel definition
For more details about the analog channel definition, refer to COMTRADE (IEEE C37.11)
external documentation.
668 C264/EN UM/E50.5

7.2.10.2.2 Adding a digital channel definition

The addition of a digital channel definition for IEC 60870-5-103 is done via the “Objects entry”
window at IEC 60870-5-103 acquisition type level by clicking on mouse’s right button. Up to 255
digital channels can be created under a IEC 60870-5-103 acquisition type.
- Figure 330 - Adding a IEC 60870-5-103 digital channel definition
Once added, channel definition attributes must be set at SCE level:

• channel label.
• long name of the channel used for internal SCE identification.
• function number (range [0 , 255], step 1): corresponds to function type of the channel in
IEC 60870-5-103 protocol.
• information number (range [0 , 255], step 1): corresponds to information number of the
channel in IEC 60870-5-103 protocol.
• default state (Off / On).
- Figure 331 - Setting IEC 60870-5-103 digital channel definition
For more details about the digital channel definition, refer to COMTRADE (IEC 60255-24)
external documentation.
7.2.10.3 Defining management of wave record file for computer CT/VT board
Allowing computer to manage its own wave record file is done at computer configuration level by:
C264/EN UM/E50.5 669

• Defining a fast and/or slow waveform recording (see following sections):
fast waveform recording gives access to samples acquired via CT/VT board.
slow waveform recording gives access to analogues (MV) and digital values (SPS, DPS,
SPC, DPC) file recording.
• Adding the system SPS datapoint ‘C26x DREC ready’ at computer level, linked to a pre-
defined datapoint profile.
• Launching “Data model and data flow update” SCE function (refer to "Connecting a BCPU to
an IEC 61850 Station Bus network" on page 600), to get the IEC 61850 address of this SPS.
7.2.10.3.1 Defining fast waveform recording

The inputs for the fast waveform records are up to 4 CT samples and 4 VT samples, and the
values of selected digital SPS, DPS, SPC or DPC datapoints (for more details about datapoints,
refer to section ). Up to 128 digital datapoints may be captured. The choice of selected
inputs/outputs is defined in configuration.
The waveform recorder provides up to 8 CT/VT channels and up to 128 digital datapoints for
extraction by Disturbance Record Module (DRM).
A maximum of 480 cycles (9,6 seconds at 50 Hz) of measurements samples, with 32 samples per
cycle, can be stored, divided in 1, 2, 4 or 8 files saved in flash disk.
A timer channel is also required to provide accurate timing information for each sample. The delay
between each sample is assumed constant over a single cycle.
Number
Number
of
of Files
cycles
8 60
4 120
2 240
1 480
The waveform recorder can be triggered by the following events, each of which is user
configurable:
• Changes in state of binary inputs (SPS or DPS datapoint)
• Changes in state of digital outputs (SPC or DPC datapoint)
• Measurement threshold violations (MV datapoint)
Only one re-trig is allowed: it means that a new trigger can only be accepted after the end of
recording of the current waveform.
Waveform records are available in COMTRADE 2001 format.
The addition of a fast waveform recording is done via the “Objects entry” window at computer
level by clicking on mouse’s right button. Only one fast waveform recording can be created under
a computer.
670 C264/EN UM/E50.5

- Figure 332 - Adding a fast waveform recording
Once added, fast waveform recording attributes must be set at SCE level:
• short name and long name: used for internal SCE identification.
• pre-trigger cycle (range [0 , 480], step 1): corresponds to number of cycles (up to 480), that
are stored before triggering.
• total cycles (range [1 , 480], step 1): see previous description.
• number of files (1 / 2 / 4 / 8): see previous description.
- Figure 333 - Setting fast waveform recording
To define the inputs of a fast waveform recording, just add the relevant relation (1) available at
recording level and fill the relation with proper CT/VT channel or datapoint. Be careful, only CT/VT
channels and datapoints acquired on the computer can be defined as input of its fast waveform
recording.
C264/EN UM/E50.5 671

- Figure 334 - Defining inputs of fast waveform recording
To define the triggers of a fast waveform recording, just add the relevant relation (2) available at
recording level and fill the relation with proper datapoint. Be careful, only datapoints acquired on
the computer can be defined as input of its fast waveform recording.
- Figure 335 - Defining trigger of fast waveform recording
Depending on the datapoint type, extra attributes must be set for ‘has for trigger’ relation. These
attributes give the datapoint states (or thresholds for MV) that trig the record (see following figure).
672 C264/EN UM/E50.5

- Figure 336 - Defining trigger conditions of fast waveform recording

- "pre-trigger cycle" ≤ "total cycles"
- "number of files" * "total cycles" ≤ 480 cycles
7.2.10.3.2 Defining slow waveform recording

The inputs for the slow waveform records are:
• MV datapoint coming from CT VT computation.
• MV datapoint coming from AIU boards.
C264/EN UM/E50.5 673

• SPS or DPS datapoints.
• SPC or DPC datapoints.
The slow wave form manages up to 24 analogues (MV) and 48 digital values (SPS, DPS, SPC,
DPC).
MiCOM C264 stores at maximum 5000 integrated values as follow:
Number
Numb of
er of integrat
Files ed
values
1 5000
2 2500
5 1000
10 500
20 250
50 100
The integrated value has duration up to one hour. It is defined in configuration.
For analogue, the stored value is the average value during integrated period.
For digital, the stored value depends also on the average:
If average value > x then the stored value is 1 else it is 0, x is defined in configuration and it is a
value between 0.1 and 0.9.
The slow waveform recorder can be triggered by the following events, each of which is user
configurable:
• Changes in state of binary inputs (SPS or DPS datapoint)
• Changes in state of digital outputs (SPC or DPC datapoint)
• Measurement threshold violations (MV datapoint)
• Periodically (i.e. every day at 00h00)
The addition of a slow waveform recording is done via the “Objects entry” window at computer
level by clicking on mouse’s right button. Only one slow waveform recording can be created under
a computer.
674 C264/EN UM/E50.5

- Figure 337 - Adding a slow waveform recording
Once added, slow waveform recording attributes must be set at SCE level:
• short name and long name of the recording used for internal SCE identification.
• pre-trigger cycle (range [0 , 5000], step 1): corresponds to the number of cycles (up to 480)
that are stored before triggering.
• total records (range [0 , 5000], step 1): see previous description.
• number of files (1 / 2 / 5 / 10 / 20 / 50): see previous description.
• arbitration period (range [0 , 100], step 1): this data represents the percentage of time during
which the logical data must be set to 1 to consider the integrated data set to 1.
• integration time (range [0 , 216000], step 1): see previous description.
Data unit is number of cycles and has the following range:
[1, 180000] if electric network frequency is 50 Hz
[1, 216000] if 60 Hz
(for network frequency configuration, refer to section "Defining slow waveform recording"
on page 673)
• activation period (Non periodic trigger / Daily trigger / weekly trigger / Daily and weekly
trigger): see previous description.
- Figure 338 - Setting slow waveform recording
C264/EN UM/E50.5 675

To define the inputs of a slow waveform recording, just add the relevant relation (1) available at
recording level and fill the relation with proper datapoint. Be careful, only datapoints acquired on
the computer can be defined as input of its slow waveform recording.
- Figure 339 - Defining inputs of slow waveform recording
To define the datapoint-triggers of a slow waveform recording, just add the relevant relation (2)
available at recording level and fill the relation with proper datapoint. Be careful, only datapoints
acquired on the computer can be defined as input of its slow waveform recording. A slow
waveform can be configured without any datapoint-trigger, if a daily or weekly activation period
has been defined for it.
- Figure 340 - Defining trigger of slow waveform recording
Depending on the datapoint type, extra attributes must be set for ‘has for trigger’ relation. These
attributes give the datapoint states (or thresholds for MV) that trig the record (see following figure).
676 C264/EN UM/E50.5

- Figure 341 - Defining trigger conditions of slow waveform recording

- "pre-trigger cycle" < "total records"
- "number of files" * "total records" < 5000 records
• If "electrical frequency" º 50 Hz:
- The "integration time" value must be in the range [1..180000].
- If the "integration time" value is > 5, then no DPC, SPC, DPS, SPS recording is allowed.
• If "electrical frequency" º 60 Hz:
- The "integration time" value must be in the range [1..216000].
- If the "integration time" value is > 6, then no DPC, SPC, DPS, SPS recording is allowed.
C264/EN UM/E50.5 677

7.2.11 Defining a computer klaxon

A computer can manage up to one external klaxon, that is started as soon as an audible local
alarm is raised on computer (to define audible alarm refer to ). The external klaxon is managed by
a specific SPC datapoint wired on the computer (‘ON’ order starts the klaxon, ‘OFF’ order stops
it).
To define an external klaxon at computer level, just add the relation ‘has its klaxon managed by’ at
computer level and fill it with the relevant SPC.
- Figure 342 - Defining computer klaxon

• The "SPC" link of the relation "has its klaxon controlled by" must be wired on a DO channel of
the Computer.
7.2.12 Setting system information for computer components

When creating a computer, specific datapoints are automatically added in ‘system infos’ binder
(1) at computer level or PLC sub-component.
So it is when adding a board (2), an IED on legacy network (3), a serial printer (4), or a SCADA
network (5) attached to a computer. In that case, the ‘system infos’ binder is located under the
relevant added object.
For extra computer functionalities (wave recording, redundancy) some optional datapoints can be
required.
SCE calls such ‘system infos’ datapoints, system datapoints.
System datapoints provide real-time statuses and controls on system software or hardware
components, and generally can not be wired on board channels except for redundancy function.
As datapoint, system datapoints must be linked to a profile. For details about datapoint and
datapoint profile configuration, refer to ). Depending on its kind, the system datapoint and its
relevant profile have specific attributes to be set correctly to insure healthy behavior of computer.
Hereafter are listed the datapoint and profile requirements for each kind of system datapoint.
678 C264/EN UM/E50.5

System datapoints get their IEC 61850 address by launching “Data model and data flow update”
SCE function (refer to "Connecting a BCPU to an IEC 61850 Station Bus network" on page 600), if
available.
- Figure 343 - 'System infos' binders for a computer
7.2.12.1 Setting general system information of a computer

When creating a computer, the following mandatory datapoints are implicitly added.
C264/EN UM/E50.5 679

- Figure 344 - Mandatory 'System infos' datapoint for a computer
These datapoints must be configured (refer to ) according to their described features:

• Controls and statuses for functioning mode
Mode control DPC: this datapoint is only used by the CAT to turn device functioning mode
to Maintenance or Operational/Run.
The available orders of this datapoint are:
680 C264/EN UM/E50.5

“OPEN” for the Maintenance mode
“CLOSED” for Operational mode
Operating mode MPS: this datapoint is the MPS equivalence of Device mode DPS. The
available states of this datapoint are:
“STATE 0” for the Faulty mode
“STATE 1” for Operational mode
“STATE 3” for Simul mode
“STATE 5” for Maintenance mode
Test control DPC: this datapoint is used to turn device functioning mode to Test or
Normal.
“OPEN” for the Simul mode
“CLOSED” for Normal mode

No available IEC 61850 address
• Control and statuses for local/remote
Local/remote ctrl DPC: this datapoint is required by IEC 61850 protocol but is
meaningless for the computer.
“OPEN” for Remote
“CLOSED” for Local

Local/remote DPS:
The available states of this datapoint are:
“OPEN” for Remote
“CLOSED” for Local

Local/remote SPS:
“RESET” for Local mode
“SET” for Remote mode
This datapoint has the "RESET" state if the Local/remore DPS datapoint of all the
bays managed by the computer have the "OPEN" state and has the "SET" state if at
least the Local/remore DPS datapoint of one bay managed by the computer has not
the "OPEN" state.
• Control and status for database management
Database incoherency SPS: this datapoint is put in ‘SET’ state if current database is not
self-consistent. In that case, computer enters the Maintenance mode.
C264/EN UM/E50.5 681

“RESET” for coherent database
“SET” for incoherent database
Database switch control SPC: this datapoint is used to switch the current database to
standby, and the standby database to current.
The available order of this datapoint is:
“ON” for Switch

• Synchronization status
Synchronization SPS: this datapoint is put in ‘SET’ state if device is synchronized.

“RESET” for not synchronized device
“SET” for synchronized device

• Synthesis board/rack statuses
ALL AIU Status SPS

ALL AOU status SPS
ALL CCU status SPS
ALL DIU status SPS
ALL DOU status SPS
ALL IED status SPS
ALL Rack status SPS
ALL TMU status SPS: these datapoints are set in ‘SET’ state if their corresponding
hardware component is dysfunctional
• Saturation status
Buffer Overflow SPS

• Setting management statuses
Setting disc. SPS
Setting done SPS
Setting in prog SPS
Setting incoher. SPS

• Communication status
Device link SPS: although this datapoint is under the computer, it is not managed by it.
Each IEC 61850 client of the computer computes locally this datapoint status by
supervising the IEC 61850 real-time link with the computer. In fact, there are as many
‘Device link SPS’ per computer basis as IEC 61850 clients connected to the computer. Is
put in ‘SET’ state if device link is operational. The available states of this datapoint are:
“RESET” for not OK
“SET” for OK
682 C264/EN UM/E50.5

• Health statuses
DI acquisition stopped SPS: in case of saturation of the internal file used for acquisition of
wired digital inputs and gooses, acquisition is automatically stopped and this datapoint is
put in ‘SET’ state. As soon as this internal file is un-saturated, this datapoint is reset and
acquisition restarts.
“RESET” for acquisition running
“SET” for acquisition stopped
Software error SPS: in case of software error, this datapoint is set and computer enters
the Faulty mode.
“RESET” for software running
“SET” for software error
Watchdog SPS: in case of software watchdog time-out, this datapoint is put in ‘SET’ state
and computer enters the Faulty mode.
“RESET” for watchdog OK
“SET” for watchdog time-out

• Control and statuses for redundancy management
The five following datapoints are used internally by computer in redundancy management.
These datapoints must be linked to datapoint profiles by default for proper behavior of
redundancy.
Redundancy change mode SPS

Redundancy change status SPS
Redundancy mode control SPC
Redundancy status control SPC
Main status MV
At computer level, the following optional datapoint can be added.
C264/EN UM/E50.5 683

- Figure 345 - Optional 'System infos' datapoint for a computer
These datapoints must be configured (refer to ) according to their described features:

• Counter Top SPS: this datapoint is used to launch the transmission of counters value on
IEC 61850 and SCADA networks. Launching is done when the datapoint goes in ‘SET’ state.
This datapoint is generally wired.
“RESET” for no transmission
“SET” for transmission

• DREC ready SPS: this datapoint indicates the availability of a waveform record file for the
computer (refer to Defining wave record file management).
“RESET” for no waveform record available
“SET” for waveform record file available

• External clock status SPS: this datapoint indicates the status of the IRIG-B synchronization.
This datapoint is mandatory if ‘synchronization source’ attribute at computer level is set to
IRIG-B (refer to "Setting general attributes of MiCOM C264" on page 571). The available
states of this datapoint are:
“SET” for lack of IRIG-B signal
“RESET” for IRIG-B signal is present

• Local alarm ack
• Test Mode Status: this datapoint indicates the switching of BCPU into test mode. For
automation purposes this datapoint will be the only datapoint issued without the test quality
while BCPU is in test mode. The available states for this datapoint are:
Test Mode Status is SET if Test mode is ON
Test Mode Status is RESET if Test mode is OFF
7.2.12.2 Setting system information of board

When creating a board (except CPU board) the following mandatory datapoint is implicitly added.
684 C264/EN UM/E50.5

- Figure 346 - Mandatory 'System infos' datapoint for a board (e.g. for AIU board)
• Board status MPS (1): this datapoint indicates the status of the board.
• “STATE 0” for board OK
• “STATE 1” for self-check failure
• “STATE 2” for configured but missing
• “STATE 3” for not configured but present
• “STATE 4” for board not present
7.2.12.3 Setting system information of legacy IED

When creating a legacy IED, the following mandatory datapoints are implicitly added.
- Figure 347 - Mandatory 'System infos' datapoints for a Legacy IED
C264/EN UM/E50.5 685

These datapoints must be configured (see section ) according to their described features:
• IED communication status SPS (1): is put in ‘SET’ state if communication with the IED is
operational.
“RESET” for communication not OK
“SET” for communication OK

• IED synchronization status SPS (2): is put in ‘SET’ state if IED is synchronized.
“RESET” for IED not synchronized
“SET” for IED synchronized
At IED level, the following optional datapoint can be added:

• IED DREC Ready SPS: this datapoint indicates the availability of a disturbance file for the IED
(refer to "Defining management of disturbance file for IED" on page 667). This datapoint is put
in ‘SET’ state if a disturbance file is available.
“RESET” for no disturbance file available
“SET” for disturbance file available
- Figure 348 - Optional 'System infos' datapoints for a Legacy IED
7.2.12.4 Setting system information of serial printer

When creating a serial printer, the following mandatory datapoint is implicitly added.
686 C264/EN UM/E50.5

- Figure 349 - Mandatory 'System infos' datapoint for a serial printer

• Printer status MPS (1): this datapoint indicates the status of the printer.
• “STATE 0” for printer OK
• “STATE 1” for self-check failure
• “STATE 4” for printer not present
7.2.12.5 Setting system information of a SCADA network

When creating a SCADA network, the following mandatory datapoints are implicitly added.
- Figure 350 - Mandatory 'System infos' datapoint for a SCADA network
C264/EN UM/E50.5 687

• SCADA communication status SPS (1): this datapoint is put in “SET” state if communication
with the SCADA is operational.
“RESET” for communication with the SCADA not OK
“SET” for communication with the SCADA OK

• SCADA redundancy status SPS (2): this datapoint is put in “SET” state if redundancy with the
SCADA is active.
“RESET” for standby
“SET” for active
688 C264/EN UM/E50.5

7.3 Defining datapoint

7.3.1 Creating a datapoint
Electrical and system topologies share entities called datapoints. A datapoint corresponds to an
atomic object with real-time value, status or control relevant to electrical or system process.
Moreover, datapoints support extra system functions like forcing, suppression, filtering, and
alarms, logging.
Several kinds of datapoint exist:

• Input datapoints used for supervision:
• SPS (Single Point Status), DPS (Double Point Status), MPS (Multiple Point Status)
• MV (Measurement Value), Counter
• Output datapoints used for control:
• SPC (Single Point Control), DPC (Double Point Control)
• Setpoint
Input datapoints can be acquired through sensors (input channels), addressed on IED at IED
legacy network level or substation network level. They can also be calculated or deduced by the
system devices. They can be sent to SCADA by addressing them on SCADA networks.
Output datapoints can be controlled through relays (output channels), addressed on IED at IED
legacy network level or substation network level or on SCADA networks. They can also be
managed by built-in functions or user functions.
At SCE level, datapoints belonging to the system topology are called system datapoints, and
those of the electrical topology are named electrical datapoints.
Generally, system datapoint creation is automatic when adding system devices or sub-
components to system devices. They are never wired, except for system datapoint used by
redundancy (for MiCOM C264 only)and more often correspond to system diagnostics (device,
printer board status, control of device mode).
Electrical datapoint creation is rarely automatic except when they are required for correct EPAS
system behavior (for instance, ‘Order running SPS’ at bay level, ‘Computed switchgear position’
at circuit-break level), or relevant to an electrical built-in function that imposes their existence.
Binary input processing for SPS, DPS and MPS datapoints is described in section Binary Input
Processing of chapter Functional description (FT) of MiCOM C264.
Measurement input processing for MV and TPI datapoints is described in sections Measurement
Input Processing and Tap Position Indication measurement processing of chapter Functional
description (FT) of MiCOM C264.
Accumulator input processing and Energy counting for Counter datapoint are described in
sections Accumulator Input Processing and Energy Counting of chapter Functional description
(FT) of MiCOM C264.
Control sequences for SPC, DPC and Setpoint datapoint is described in section Control
sequences of chapter Functional description (FT) of MiCOM C264.
C264/EN UM/E50.5 689

Hereafter are described standard ways to define datapoint at SCE level. SCE provides facilities to
create and wire datapoints directly from specific wiring tables. The usage of these tables is
described more precisely in chapter Human Machine Interface of SCE User manual (part
Configuration facilities).
7.3.1.1 Defining SPS datapoint

To define a SPS datapoint, add a SPS from object entry available at the wished system or
electrical object level. Depending on the object level, different pre-defined kinds of SPS exist.
They are used for specific needs at electrical topology level (refer to "Defining BCPU configuration
in system architecture" on page 567) or system topology level (refer to "Setting system
information for computer components" on page 678).
- Figure 351 - adding an SPS datapoint (sample

given at bay level for generic SPS)
Then, update the SPS attributes where some can be fixed or masked depending on the pre-
defined kind of SPS (description given for generic SPS):
• short name and long name of the datapoint used for logging, alarms ...
• detection mode (Permanent / Transient / Permanent with computer auto-reset): when this
attribute is set to "Permanent with computer auto-reset" the SPS is reset automatically after 1
ms.
• used profile (refer to "Linking a datapoint to a profile" on page 708)
• stable state time reference (Start of filtering / End of filtering)
• reset confirmation delay (range [0 s, 120 s], step 100 ms]: confirmation delay for stable
‘reset’ state.
• set confirmation delay (range [0 s, 120 s], step 100 ms]: confirmation delay for stable ‘set’
state.
• forcing management (Not automatic / Automatic to reset state / Automatic to set state):
when a SPS goes in invalid state, computer can force or not its status to set or reset state
automatically. This attribute defines the way this forcing management is done. Automatic
forcing management is independent of FSS facility gives at user by the SPS profile.
• state panel assignment (No / Yes): set to ‘yes’ to enable SPS state display at computer local
HMI level. .
690 C264/EN UM/E50.5

- Figure 352 - Setting general attributes of an

SPS datapoint (sample given at bay level for
generic SPS)
7.3.1.2 Defining DPC datapoint

To define a DPC datapoint, add a DPC from object entry available at the wished system or
electrical object level. Depending on the object level, different pre-defined kinds of DPC exist.
in electrical architecture" on page 751) or system topology level (refer to "Setting system
information of board" on page 684).
- Figure 353 - Adding a DPS datapoint (sample

given at bay level for generic DPC)
Then, update the DPC attributes where some can be fixed or masked depending on the pre-
defined kind of DPC (description given for generic Bay DPC):
• short name and long name: used for logging, alarms ...
• activation mode (Permanent / Transient / Permanent until feedback).
• close duration (range [0, 15 s], step 10ms): this attribute is only available if the activation
mode is set to Transient. It defines the time while the DPC is held in the "close" state before
returning to the "open" state.
• open duration (range [0, 15 s], step 10ms): this attribute is only available if the activation
mode is set to Transient. It defines the time while the DPC is held in the "open" state before
returning to the "close" state.
• hold duration (range [0, 10 s], step 10ms): this attribute is only available if the activation
mode is set to Permanent until feedback. It defines the time while the contact is held in the
requested state after reception of the confirmation of the position of the device.
C264/EN UM/E50.5 691

• time between two orders (range [0, 10 s], step 100ms): this attribute corresponds to the
inter-control delay defined in section "Inter-control delay" on page 227 of chapter Functional
description (FT) and is also used for execution checks (see "Generic execution checks" on
page 230 in chapter Functional description (FT)).
• command panel assignment (No / Yes): set to ‘Yes’ to enable SPC control at computer
local HMI level.
• bay mode dependency: Yes /No
• SBMC mode dependency: Yes /No
• bay control uniqueness dependency: Yes / No (only significant if control uniqueness is set
to bay at substation level)
• Local substation dependency: Yes /No
• Remote substation dependency: Yes/ No
- Figure 354 - Setting general attributes of a DPC

datapoint (sample given at bay level for a generic
DPC)
7.3.1.3 Defining MPS datapoint

To define a MPS datapoint, add a MPS from object entry available at the wished system or
electrical object level. Depending on the object level, different pre-defined kinds of MPS exist.
- Figure 355 - Adding an MPS datapoint (sample

given at bay level for generic MPS)
692 C264/EN UM/E50.5

Then, update the MPS attributes where some can be fixed or masked depending on the pre-
defined kind of MPS (description given for generic MPS):
• filtering delay (range [0 s, 6553,5 s), step 10 ms).
• inhibition delay (range [0 s, 6553,5 s), step 10 ms).
• forcing management (Not automatic / Automatic to state (i ϵ [0, 15])): when MPS goes in
invalid state, computer can force or not its status to set or reset state automatically. This
attribute defines the way this forcing management is done. Automatic forcing management is
independent of FSS facility gives at user by the MPS profile.
• state panel assignment (No / Yes): set to ‘yes’ to enable MPS state display at computer
local HMI level.
- Figure 356 - Setting general attributes of an MPS

datapoint (sample given at bay level for generic
MPS)
7.3.1.4 Defining MV datapoint

To define a MV datapoint, add a MV from object entry available at the wished system or electrical
object level. Depending on the object level, different pre-defined kinds of MV exist. They are used
for specific needs at electrical topology level (refer to "Defining BCPU configuration in electrical
architecture" on page 751) or system topology level (refer to "Setting system information for
computer components" on page 678).
- Figure 357 - Adding an MV datapoint (sample

given at bay level for a generic MV)
Then, update the MV attributes where some can be fixed or masked depending on the pre-
defined kind of MV (description given for generic MV):
‘General’ attributes
C264/EN UM/E50.5 693

• type: available values are:

Analogue (used for analogue acquisition, IED acquisition, CT/VT calculation or system input)
Digital coded ‘BCD’ (only used for digital acquisition)
Digital coded ‘pure binary’ (only used for digital acquisition)
Digital coded ‘gray’ (only used for digital acquisition)
Digital coded ‘1 among n’ (only used for digital acquisition)
Digital coded ‘decimal’ (only used for digital acquisition)
• automatic forcing (No / Yes): when a MV goes in invalid state, computer can force or not its
value automatically. Automatic forcing management is independent of FSS facility gives at
user by the MV profile.
• value for automatic forcing: MV value when automatic forcing
• transmission on event (Cyclic long period / Cyclic short period / According to a ‰ of full
scale value / According to a ‰ of current value)
• deadband (‰ variation) (range [0,255], step 1): this attribute is significant only if the previous
parameter is set to ‘According to a ‰ of ...’: this attribute corresponds to ‘p’ parameter
described in section 5.2.9.2 of chapter Functional description (FT) MiCOM C264.
• MV panel assignment (No / Yes): set to ‘yes’ to enable MV value displayed at computer local
HMI level. .
- Figure 358 - Setting general attributes of an MV

datapoint
‘Value features’ attributes

• minimum value (range [-3.4e38, 3.4e38]): minimum expected value after scaling
conversion, used for full scale calculation
• maximum value (range [-3.4e38, 3.4e38]): maximum scaled value after scaling conversion,
used for full scale calculation. (Full scale = maximum value - minimum value)
• zero value suppression (% of full scale value) (range [0,10], step 0.1): this parameter is
used to define the zero suppression area for the zero value suppression processing (refer to
chapter Functional description (FT) of MiCOM C264 for details)
• Hysteresis used for threshold detection (refer to chapter Functional description (FT) of
MiCOM C264 for details)
For each available threshold:
694 C264/EN UM/E50.5

• Threshold usage (No / Yes)
• Threshold value
- Figure 359 - Setting value features attributes to

MV datapoint (sample given at bay level for generic
MV)
‘Scaling’ attributes
• scaling rule: available values are:
Linear
Quadratic
Quadratic with offset
Linear per pieces
• minimum acq. value: minimum acquired value by the BCPU, before applying scaling rules
• maximum acq. value: maximum acquired value by the BCPU, before applying scaling rules
• In case of multi-segment scaling (for details of the use of the coefficients, see Scaling ):
Ai coefficient
Bi coefficient
- Figure 360 - Setting scaling attributes of an MV

MV)
‘Digital acquisition’ attributes
When adding a generic digital MV datapoint, some ‘Digital acquisition’ attributes have to be
updated.
Refer to section Measurement Input Processing of chapter Functional description (FT) of

MiCOM C264 for attribute meaning.
C264/EN UM/E50.5 695

• Inhibition delay(x 10 ms): used for digital measurement with read inhibit signal
• Stabilisation delay (x 10 ms)
• Stabilisation value
• Validation delay (x 10 ms)
7.3.1.5 Defining TPI datapoint

Tap Position Indicator (TPI) is seen as MV with specific features:
• Its value is an integer in the range [1..64],
• Acquisition can be done via AI channel of AIU board.
• Acquisition can be done on digital channels of DI or DI/DO board (up to 64 DI channels). In

that case, available digital MV type are: Decimal, Gray, BCD or ‘1 among n’
TPI datapoint is automatically created when adding a tap changer built-in function under a
mandatory transformer module of a transformer bay. For details about transformer bay, module or
tap changer function creation refer to "Defining BCPU configuration in electrical architecture" on
page 751.
- Figure 361 - Automatic TPI creation for tap-

changer built-in function
Once a TPI has been created by adding a tap changer built-in function, update its attributes:
‘General’ attributes
• type: available values are:

Analogue tap position
Digital tap position coded ‘1 among N’ (only used for digital acquisition)
Digital tap position coded ‘decimal’ (only used for digital acquisition)
Digital tap position coded ‘gray’ (only used for digital acquisition)
Digital tap position coded ‘BCD’ (only used for digital acquisition)
• MV panel assignment (No / Yes): set to ‘yes’ to enable MV value display at computer local
HMI level.
696 C264/EN UM/E50.5

- Figure 362 - Setting general attributes of a TPI

datapoint
‘Value features’ attributes
Refer to section "Defining MV datapoint" on page 693

• The following constraint between the two attributes must be respected:
("maximum value" - "minimum value" + 1) ϵ [1..64]
‘Tap position’ attributes

• Filtering delay (range [0, 65535 s], step 10 ms):
for digital TPI, corresponds to Tstab of digital measurement,
for analogue TPI, corresponds to a delay to filter transient UNDEFINED state (delay to
confirm UNDEFINED state)
• current valid range (% maximum value) (range [0 , 20 %], step 1 %):
only used for analogue TPI corresponds to N parameter described in section 5.3 of chapter
Functional description (FT) of MiCOM C264.
- Figure 363 - Setting tap position attributes of a

TPI datapoint
‘Scaling’ attributes (for analogue TPI)

• minimum acq. value: corresponds to Imin parameter described in section "Tap Position
Indication (TPI) measurement processing" on page 207 of chapter Functional description
(FT).
• maximum acq. value: corresponds to Imax parameter described in section "Tap Position
Indication (TPI) measurement processing" on page 207 of chapter Functional description
(FT).
C264/EN UM/E50.5 697

- Figure 364 - Setting scaling attributes of a TPI

datapoint
7.3.1.6 Defining counter datapoint

To define a Counter datapoint, add a Counter from object entry available at the wished system or
electrical object level. Depending on the object level, different pre-defined kinds of Counter exist.
in system architecture" on page 567) or system topology level (refer to "Setting system
- Figure 365 - Adding a counter datapoint (sample

given at bay level for generic counter)
Then, update the Counter attributes (description given for generic Counter):
• used profile (refer to )
• counter type (Standard, Energy import, Energy export): when this attribute is set to
"Standard" associated attributes are Validation duration (3), Invalidity duration (4), IED value
already totalled (5), Cumul period (6) and Reset at cumulative period (7). When this attribute
is set to Energy import or Energy export associated attributes are energy type (9), Scale
factor (10), Transmission period (11) and reset after transmission (12).
• validation duration (range [0, 10 s], step 1 ms): corresponds to Tcount parameter described
in section "Digital measurement (DM)" on page 151 of chapter Functional description (FT).
• invalidity duration (range [5, 10 s], step 1 ms): corresponds to Tdef parameter described in
section "Digital measurement (DM)" on page 151 of chapter Functional description (FT).
• IED value already totalled (No / Yes): attribute must be set to Yes if counter value acquired
on IED must not be totalled periodically (total done at IED level)
698 C264/EN UM/E50.5

• cumul period (10 mn / 15 mn / 30 mn / N h (N ϵ [1, 24])): corresponds to period length of

internal clock parameter described in section1.
• reset at cumulative period (No / Yes): when set to ‘Yes’ that the way to transmit the periodic
register, if not the cumulative register is transmitted.
• MV panel assignment (No / Yes): set to ‘yes’ to enable Counter value display at computer
local HMI level.
• scale factor.
• energy type (Activ energy, Reactiv energy).
• transmission period (10 mn / 15 mn / 30 mn / N h (N ϵ [1, 24])).
• reset after transmission (No, Yes).
- Figure 366 - Setting general attributes of a

counter datapoint (sample given at bay level for
generic counter)
7.3.1.7 Overview of control sequence processing

This section is an introduction to SPC, DPC and SetPoint datapoint definition. It deals with
general control sequence and features associated to these kinds of datapoints, for better
comprehension of their configuration.
There are four types of Binary outputs:

• Single Point Status (SPC): derived from one Digital output.
• Double Point Status (DPC): derived from two Digital outputs.
• System output: control information related to the system, to configurable and built-in
automations or to electrical process but without acquisition possibilities.
• Setpoint (SetPoint): derived from n Digital outputs.
SPC, DPC and SetPoints are mainly controlled via digital output boards (board with DO channels)
or via legacy IED connected to the EPAS device .
By extension, at SCE level, system outputs are seen as particular SPC or DPC depending on the
number of elementary information they represent (for details about system outputs, see section
"Setting system information of board" on page 684).
Control sequences are described in chapter Functional description (FT) of BCPU.
C264/EN UM/E50.5 699

7.3.1.8 Defining SPC datapoint

To define a SPC datapoint, add a SPC from object entry available at the wished system or
electrical object level. Depending on the object level, different pre-defined kinds of SPC exist.
- Figure 367 - Adding an SPC datapoint (sample

given at bay level for generic SPC)
Then, update the SPC attributes where some can be fixed or masked depending on the pre-
defined kind of SPC (description given for generic Bay SPC):
• spare: datapoint can be spared
• order on duration (range [0, 15 s], step 10ms): this attribute is only available if the activation
mode is set to Transient. It defines the time while the contact is closed before re-opening. hold
duration (range [0, 10 s], step 10ms): this attribute is only available if the activation mode is
set to Permanent until feedback. It defines the time while the contact is held in the requested
position after reception of the confirmation of the position of the device.
inter-control delay.
• command panel assignment (No / Yes): set to ‘yes’ to enable SPC control at computer local
HMI level.
• bay Contol uniqueness: (No / Yes): only significant if control uniqueness is set to bay at
substation level.
• Local Substation Dependancy: Yes/No
• Remote Substation dependency: Yes /No
700 C264/EN UM/E50.5

- Figure 368 - Setting general attributes of an SPC

datapoint (sample given at bay level for generic
SPC)
7.3.1.8.1 Defining an SPC feedback

For correct execution behavior and control acknowledgment, an SPC datapoint can be linked to a
SPS or DPS datapoint that corresponds to a feedback. For instance, a circuit-breaker control SPC
is linked to the circuit-breaker status DPS.
To define an SPC feedback:

• Add the relation ‘has for feedback’ at SPC level: choose exclusively one of the two relations
‘has for feedback: SPS datapoint’ (1) or ‘has for feedback: DPS datapoint’ (2) depending on
the kind of feedback datapoint.
• Fill the relation with the relevant SPS or DPS datapoint.
- Figure 369 - defining SPC feedback
If necessary, update the relation attributes:

• execution time-out (range [0, 6000 s], step 100 ms): in this given delay, feedback must
change relatively to the control. If not, a negative acknowledgment is sent for the control
• status check for command (No check / Control authorized only if the device is in the
opposite state / Control authorized only if the device is in the opposite state, jammed or
undefined / Control refused if the device is in the same state): this attribute corresponds to the
‘current status check for the device’ described in section "Current status of the device" on
page 228 of chapter Functional description (FT) of BCPU. and used also for execution checks
(see "Generic execution checks" on page 230 in chapter Functional description (FT)).
C264/EN UM/E50.5 701

- Figure 370 - Setting attributes of an SPC

feedback relation

• For each "SPC", two relations "has for feedback" are available, but they are mutually
exclusive
• A datapoint and its feedback datapoint must comply with the following rules:
- both must have the same Server device
- if one of them is a "Wired" datapoint, the other one must be "Wired" too (Here, the term
"Wired" means that the datapoint is linked to a digital or analog channel of a computer, or
linked to an IED address, else it's "System")
- if one of them is a "System" datapoint, the other one must be "System" too.
- if one of them is linked to an " IEC 61850 gen IED" through the relation "has for IEC 61850
address", this relation must also be defined for the other one
• For a "SPC" datapoint, if its attribute "activation mode" is set to the "Transient" value, then the
following rule must be respected:
"execution timeout" > "order on duration"
7.3.1.9 Defining DPC datapoint

To define a DPC datapoint, add a DPC from object entry available at the wished system or
electrical object level. Depending on the object level, different pre-defined kinds of DPC exist.
- Figure 371 - Adding a DPS datapoint (sample

given at bay level for generic DPC)
Then, update the DPC attributes where some can be fixed or masked depending on the pre-
defined kind of DPC (description given for generic Bay DPC):
702 C264/EN UM/E50.5

• close duration (range [0, 15 s], step 10ms): this attribute is only available if the activation
mode is set to Transient. It defines the time while the DPC is held in the "close" state before
returning to the "open" state.
• open duration (range [0, 15 s], step 10ms): this attribute is only available if the activation
mode is set to Transient. It defines the time while the DPC is held in the "open" state before
returning to the "close" state.
• hold duration (range [0, 10 s], step 10ms): this attribute is only available if the activation
mode is set to Permanent until feedback. It defines the time while the contact is held in the
requested state after reception of the confirmation of the position of the device.
inter-control delay defined in section "Inter-control delay" on page 227 of chapter Functional
description (FT) and is also used for execution checks (see "Generic execution checks" on
page 230 in chapter Functional description (FT)).
• command panel assignment (No / Yes): set to ‘Yes’ to enable SPC control at computer
local HMI level.
• bay control uniqueness dependency: Yes / No (only significant if control uniqueness is set
• Local substation dependency: Yes /No
• Remote substation dependency: Yes/ No
- Figure 372 - Setting general attributes of a DPC

DPC)
7.3.1.9.1 Defining a DPC feedback

For correct execution behavior and control acknowledgment, a DPC datapoint can be linked to a
SPS or DPS datapoint that corresponds to a feedback. For instance, a circuit-breaker control
DPC is linked to the circuit-breaker status DPS.
To define a DPC feedback:
C264/EN UM/E50.5 703

• Add the relation ‘has for feedback’ at DPC level: choose exclusively one of the two relations
‘has for feedback: SPS datapoint’ (1) or ‘has for feedback: DPS datapoint’ (2) depending on
the kind of feedback datapoint.
• Fill the relation with the relevant SPS or DPS datapoint.
- Figure 373 - Defining a DPC feedback

• execution timeout (range [0, 6000 s] step 100 ms): in this given delay, feedback must
change relatively to the control. If not, a negative acknowledgment is sent for the control
• status check for command (No check / Control authorized only if the device is in the
opposite state / Control authorized only if the device is in the opposite state, jammed or
undefined / Control refused if the device is in the same state): this attribute corresponds to the
‘current status check for the device’. and also used for execution checks (see "Generic
execution checks" on page 230 in chapter Functional description (FT)).
- Figure 374 - Setting attributes of a DPC feedback

relation

• For each "DPC", two relations "has for feedback" are available, but they are mutually
exclusive
- if one of them is linked to an " IEC 61850 gen IED" through the relation "has for IEC 61850
704 C264/EN UM/E50.5

• For a "DPC" datapoint, if its attribute "activation mode" is set to the "Transient" value, then the
following rule must be respected: “execution timeout"> max [“open duration”, "close duration"]
7.3.1.10 Overview of SetPoint processing

Digital setpoints are described in section "Control sequences" on page 213 of chapter Functional
description (FT).
SetPoints are used to send instruction values to the process or to ancillary devices. BCPU
manages two types of SetPoints:
• Digital SetPoints
• System SetPoints
Digital SetPoints
Digital SetPoints are executed via DO channels of Digital Output boards. This type of controls is
managed in “Direct Execute mode” only.
The checks performed during execution phase for SetPoints are:

• Substation and bay modes: check user selectable.
• Uniqueness: check user selectable.
• Device Locked: check user selectable.
• Automatism running control: check user selectable.
Digital SetPoints may be configured with digital “refresh DO” (see following topic)
The configuration allows also to define two methods of activation of the SetPoint relays:
• Raw activation: all activated relays which must be open are deactivated, all relays which must
be closed are activated. If a “read inhibit DO” is configured this one must be deactivated
during the relay positioning (see following topic).
• Incremental activation: the restitution of the SetPoint and relays can be done by successive
increments from the initial value to the final one. The value of increments and the duration of
the activation are user selectable. If a “read inhibit DO” is configured this one must be
deactivated during every incremental activation (see following topic).
Digital SetPoint encoding
Described in section "Control sequences" on page 213 of chapter Functional description (FT).
Read inhibit signal for digital SetPoint
A dedicated binary output can be used to allow/ forbid reading the value by the external device.
There is one (or none) read inhibit (RI) output per value.
If the RI output is a logical one (external polarity applied), the reading is permitted.
The procedure used to output a value with a RI output is:

• Reset the RI output to a logical 0: read forbidden.
• Wait for N ms.
• Output the value.
C264/EN UM/E50.5 705

• Wait for N ms.
• Set the RI output to a logical 1: read permitted.
The 0 to 1 transition on the RI output can be used by the external device as a trigger, indicating
that a new value is available.
- Figure 375 - Read inhibit signal for digital setpoint
Refresh DO for digital SetPoint
SetPoints can be configured with a refresh period, this means that the SetPoint request must be
sent periodically by the transmitter.
If a request on the SetPoint is not received before the end of the refresh period, the SetPoint is set
to non-refreshed and an alarm is raised but and the last received SetPoint is maintained.
Once a new SetPoint request is received, the SetPoint is set to refreshed, DO are activated and
the alarm is reset.
System SetPoint
SetPoints can be locally managed by computer as a system control for automation for instance.
Execution phase is identical to the digital SetPoints.
7.3.1.11 Defining SetPoint datapoint

To define a SetPoint datapoint, add a SetPoint from object entry available at the wished system or
electrical object level. Depending on the object level, different pre-defined kinds of SetPoint exist.
- Figure 376 - Adding a SetPoint datapoint (sample

given at bay level for generic SetPoint)
706 C264/EN UM/E50.5

Then, update the SetPoint attributes where some can be fixed or masked depending on the pre-
defined kind of SetPoint (description given for generic Bay SetPoint):
• type:
Analogue: SetPoint is managed by IED, by system output, or by AOU board output
Digital coded BCD
Digital coded ‘Pure binary’
Digital coded ‘Gray’
Digital coded ‘1 among N’
Digital coded ‘decimal’
• progressive step usage: only used for digital SetPoint. No corresponds to Raw activation,
Yes to Incremental Activation
• minimum value (range [-3.4E38, 3.4E38]): used for value control and scaling.
• maximum value (range [-3.4E38, 3.4E38]): used for value control and scaling.
• command panel assignment (Yes / No): set to ‘yes’ to enable SetPoint control at computer
local HMI level.
• bay mode dependency: Yes/No
• SBMC mode dependency: Yes/No
• bay control uniqueness dependency: Yes/No (only significant if control uniqueness is set
• Local substation dependancy: From SCADA refused/Allowed
• Remote substation dependancy: From HMI refused/Allowed

SetPoint datapoint (sample given at bay level for
generic SetPoint)

• A Setpoint datapoint wired on DO channels of a computer, must be digital and have its profile
attribute “SBO mode” set to "Direct Execute" or “Direct Execute with SBO popup”.
C264/EN UM/E50.5 707

7.3.1.11.1 Defining SetPoint feedback

For correct execution behaviour and control acknowledgement, a SetPoint datapoint can be
linked to an MV datapoint that corresponds to a feedback.
To define SetPoint feedback:

• Add the relation ‘has for feedback’ (1) at SetPoint level
• Fill the relation with the relevant MV datapoint.
- Figure 378 - Defining SetPoint feedback

• execution timeout (range [0, 999 s], step 1 s): in this given delay, feedback must change
relatively to the control. If not, a negative acknowledgement is sent.
- Figure 379 - Setting attributes of a SetPoint

feedback relation

- if one of them is linked to an "IEC 61850 gen IED" through the relation "has for IEC 61850
7.3.2 Linking a datapoint to a profile

Many common characteristics are often shared by a set of datapoints. For instance, all feeder
breaker positions have the same state labels, alarm and logging behaviour. To group these
common characteristics, profile concept has been embedded in data modelling. For each kind of
708 C264/EN UM/E50.5

datapoints (SPS, DPS…) there exists a relevant profile (SPSProfile, DPSProfile…). Several
datapoints of the same kind can be linked to the same profile.
The profile attributes can be seen as the datapoint attributes as soon as this datapoint is linked to
the profile. For ease of explanation, this short-cut will be done in this document.
For input datapoints, the following characteristics are set at profile level:
• state labels and eventual unit label for MV and counter.
• definition of the archived and logged states.
• definition of the alarmed states (gravity, delay, audibility).
• definition of state interlocking values.
• definition of forcing/substitution/suppression (FSS) and SBMC facilities.
For output datapoints, the following characteristics are set at profile level:
• order labels and eventual unit label for setpoints.
• definition of the significant orders for SPC and DPC.
• definition of the alarmed order failure (gravity, delay, audibility).
• definition of the archived and logged transitions.
• SBO mode facility.
‘Profile’ objects are managed via a specific “Profiles” table at SCE level. The usage of this table is
described more precisely in chapter Human Machine Interface of SCE User manual (part
Configuration facilities).
7.3.2.1 Defining an SPS profile

To create an SPS profile:
• Click on ‘+’ icon in SPS tab of Profiles table.
• Update the profile attributes (see following sections).
- Figure 380 - Adding an SPS profile
7.3.2.1.1 Setting 'General attributes' of an SPS profile

When adding an SPS profile some general attributes have to be updated:
• short name and long name of the profile only used for profile identification in SCE.
And for linked SPS datapoints:
C264/EN UM/E50.5 709

• enable Force/Subst/Sup (No / Yes).
• SBMC dependant (No / Yes).
• SBMC state substitution value (Suppressed / Set / Reset): significant and visible if SBMC
dependant is set to Yes.
• toggling filtering (No / Yes): useful for a datapoint acquired on a DI board to filter toggling.
• initial status (Reset / Set): used for computer software initialisation especially for system
datapoints.
- Figure 381 - Setting general attributes of an SPS

profile

• The profile of a datapoint of the System topology has to have its enable Force/Subst/Sup
attribute set to No.
7.3.2.1.2 Setting 'State labels' attributes of an SPS profile

When adding an SPS profile, some State labels attributes have to be updated. They are used for
events and alarm management at EPAS device level (logging, display).
- Figure 382 - Setting 'State labels' attribute of an

SPS profile
7.3.2.1.3 Setting 'State treatment' attributes of an SPS profile

When adding a SPS profile, some State treatment attributes have to be updated, for each
available state of the linked datapoints (1), for the different OI printers (no more used).
Available attribute values concern:

• OI Printers (Sequence Of Events, LogBook): no more used
• OI treatment on : no more used
• BCPU treatment on :
For each available state, precise if the event associated to the change of state shall be:
710 C264/EN UM/E50.5

no archive, no logging
archive, logging
archive, no logging
no archive, logging
- Figure 383 - Setting 'state treatments' attributes

of an SPS profile
7.3.2.1.4 Setting 'Alarms' attributes of an SPS profile

When adding an SPS profile some Alarms attributes have to be updated, for each available state
of the linked datapoints.
• generation condition (Appearance / Appearance and disappearance): this attribute is
common for all the states of each SPS linked to this profile. It defines when alarm are
generated.
For each state the following attributes are settable:

• defined (No / Yes)
• masking due to control (No / Yes): this attribute have to be set to ‘Yes’ to manage correctly
discrepancy (alarm only appears in case of spontaneous change of state without previous
control).
• delay (range [0 s, 120 s], step 1 s): to avoid alarm generation if alarm condition disappears
within this delay.
• gravity (range [1, 5], step 1).
• audible (No / Yes): to activate a klaxon.
• clearing mode (Manual / Automatic / Gravity basis): to precise the way alarm is cleared when
alarm condition disappears:
• Manual: users have to be explicitly clear the alarm,
• Automatic: no user intervention is needed to clear the alarm,
• Gravity basis: the clearing mode is deduced from the one given at Scs object level for the
relevant gravity
For BCPU configuration, all attributes are significant for datapoints it is server of.
C264/EN UM/E50.5 711

- Figure 384 - Setting 'Alarms' attributes of an

SPS profile
7.3.2.1.5 Setting 'Interlocking' attributes of an SPS profile

For each possible state of an SPS (1) linked to this profile and belonging to an interlocking
equation the user chooses among three values (Invalid, False, True) which one will be used for
evaluation of the interlocking equation.
- Figure 385 - Setting 'interlocking' attributes of an

SPS profile
7.3.2.2 Defining a DPS profile

To create a DPS profile:
• Click on ‘+’ icon in DPS tabpane of Profiles table.
- Figure 386 - Adding a DPS profile
7.3.2.2.1 Setting 'General' attributes of a DPS profile

When adding an DPS profile some general attributes have to be updated:
And for linked DPS datapoints:
712 C264/EN UM/E50.5

• SBMC dependent (No / Yes).
• SBMC state substitution value (Suppressed / Open / Closed / Jammed), significant and
visible if SBMC dependent is set to Yes.
• toggling filtering (No / Yes): useful for datapoint acquired on DI board to filter toggling.
• initial status (Motion / Open / Closed / Undefined), used for computer software initialisation
especially for system datapoints.
- Figure 387 - Setting general attributes of an SPS

profile

• The profile of a datapoint of the System topology has to have its enable Force/Subst/Sup
attribute set to No.
7.3.2.2.2 Setting 'State labels' attributes of a DPS profile

When adding a DPS profile, some State labels attributes have to be updated (1). They are used
for events and alarm management at BCPU level (logging, display).
- Figure 388 - Setting 'State labels' attributes of a

DPS profile
7.3.2.2.3 Setting 'State treatment' attributes of a DPS profile

When adding a DPS profile, some State treatment attributes have to be updated, for each

C264/EN UM/E50.5 713

archive, logging
archive, no logging
no archive, logging
- Figure 389 - Setting 'State treatment' attributes of

a DPS profile
7.3.2.2.4 Setting 'Alarms' attributes of a DPS profile

When adding a DPS profile some Alarms attributes have to be updated, for each available state of
the linked datapoints.
For each state, following alarm information are settable:

common for all the states of each DPS linked to this profile. It defines when alarm are
generated.
For each state the following attributes are settable:

• defined (No / Yes).
control).
within this delay.
• audible (No / Yes): to activate an audible alarm.
• Manual: users have to be explicitly clear the alarm.
• Automatic: no user intervention is needed to clear the alarm.
relevant gravity.
714 C264/EN UM/E50.5

Figure 64 SETTING ‘ALARMS’ ATTRIBUTES of a DPS PROFILE
- Figure 390 - Setting 'Alarms' attributes of a DPS

profile
7.3.2.2.5 Setting 'Interlocking' attributes of a DPS profile

For each possible state (1) of a DPS linked to this profile and belonging to an interlocking equation
the user chooses among three values (Invalid, False, True) which one will be used for evaluation
of the interlocking equation.
C264/EN UM/E50.5 715

- Figure 391 - Setting 'Interlocking' attributes of a

DPS profile
7.3.2.3 Defining an MPS profile

To create an MPS profile:
• Add an MPS profile from object entry available at the desired system object level (1).
- Figure 392 - Adding an MPS profile
7.3.2.4 Setting 'General' attributes of an MPS profile

When adding an MPS profile, some general attributes have to be updated:
• short name and long name: only used for profile identification in SCE.
And for linked MPS datapoints:

• SBMC dependant (No / Yes).
• SBMC state substitution value (Suppressed / Open / Closed / Jammed): significant and
visible if SBMC dependant is set to Yes.
Figure 66 SETTING GENERAL ATTRIBUTES of an MPS PROFILE
716 C264/EN UM/E50.5

- Figure 393 - Setting general attributes of an MPS

profile

• The profile of a datapoint of the System topology needs its enable Force/Subst/Sup attribute
set to No.
7.3.2.4.1 Setting 'State labels' attributes of an MPS profile

When adding a MPS profile, some State labels attributes have to be updated (1). They are used
- Figure 394 - Setting 'State labels' attributes of an

MPS profile
7.3.2.4.2 Setting 'State treatments' attributes of an MPS profile

When adding an MPS profile, some State treatment attributes have to be updated, for each

archive, logging
archive, no logging
no archive, logging
7.3.2.4.3 Setting 'Alarms' attributes of an MPS profile

When adding an MPS profile some Alarms attributes have to be updated, for each available state
of the linked datapoints:
C264/EN UM/E50.5 717


common for all the states of each MPS linked to this profile. It defines when alarm are
generated.
For each state the following attributes are settable

control).
within this delay.
• Manual: users needs explicitly clear the alarm.
relevant gravity.
- Figure 395 - Setting 'Alarms' attributes of an MPS

profile
7.3.2.4.4 Setting 'Interlocking' attributes of an MPS profile

For each possible state of an MPS linked to this profile and belonging to an interlocking equation
718 C264/EN UM/E50.5

- Figure 396 - Setting 'Interlocking' attributes of an

MPS profile
7.3.2.5 Defining an MV profile

To create an MV profile:
• Add an MV profile from object entry available at the desired system object level (1).
- Figure 397 - Adding an MV profile
7.3.2.5.1 Setting 'General' attributes of an MV profile

When adding a MV profile, some general attributes have to be updated:
And for linked MV datapoints:

• SBMC dependant (Yes to suppressed / No).
• unit:used for display, logging and alarm at BCPU level.
• default format: Reserved for Substation control point usage.
C264/EN UM/E50.5 719

- Figure 398 - Setting 'General' attributes of an MV

profile

• The profile of a datapoint of the System topology needs enable Force/Subst/Sup attribute set
to No.
7.3.2.5.2 Setting 'State labels' attributes of an MV profile

When adding an MV profile, some State labels (1) attributes have to be updated. They are used
- Figure 399 - Setting 'State labels' attributes of an

MV profile
7.3.2.5.3 Setting 'State treatments' attributes of an MV profile

When adding a MV profile, some State treatment attributes have to be updated, for each available
state of the linked datapoints (1), for the different OI printers (no more used).

archive, logging
archive, no logging
no archive, logging
720 C264/EN UM/E50.5

- Figure 400 - Setting 'State treatments' attributes

of an MV profile
7.3.2.5.4 Setting 'Alarms' attributes of an MV profile

When adding an MV profile some Alarms attributes have to be updated, for each available state of
the linked datapoints.
For each state, following alarm information are settable:

common for all the states of each MV linked to this profile. It defines when alarm are
generated.
For each state the following attributes are settable

within this delay.
relevant gravity.
- Figure 401 - Setting 'Alarms' attributes of an MV

profile
C264/EN UM/E50.5 721

7.3.2.5.5 Setting 'Interlocking' attributes of an MV profile

For each possible state of an MV linked to this profile and belonging to an interlocking equation
- Figure 402 - Setting 'Interlocking' attributes of an

MV profile
7.3.2.6 Defining a counter profile

To create a Counter profile:
• Add a Counter profile from object entry available at the desired system object level (1).
- Figure 403 - Adding a counter profile (sample

given at BCPU level)
7.3.2.6.1 Setting 'General' attributes of a counter profile

When adding a Counter profile, some general attributes have to be updated:
And for linked Counter datapoints:

• SBMC dependant (Yes to suppressed / No).
• energy of a pulse (range [-3.4E38, +3.4E38].
• unit used for display, logging and alarm at protection level.
• default format: Reserved for Substation control point usage.
7.3.2.6.2 Setting 'State labels' attributes of a counter profile

When adding a Counter profile, some ‘State labels’ attributes have to be updated (1). They are
used for events and alarm management at BCPU level (logging, display).
722 C264/EN UM/E50.5

- Figure 404 - Setting 'State labels' attributes of a

counter profile
7.3.2.6.3 Setting 'State treatments' attributes of a counter profile

When adding a Counter profile, some State treatment attributes have to be updated, for each

• C5x treatment on :
archive, logging
archive, no logging
no archive, logging

of a counter profile
7.3.2.6.4 Setting 'Alarms' attributes of a counter profile

When adding a Counter profile, some ‘Alarms’ attributes have to be updated, for each available
state of the linked datapoints.
Globally to all Counter states, the attribute ‘generate condition’ (1) defines when alarms are
generated for the datapoint: ‘appearance of the event’ or ‘appearance and disappearance of the
event’.
For each state (Valid, SelfCheckFault, Unknown, Forced, Overrange, Undefined) the following
alarm attributes are settable:
C264/EN UM/E50.5 723

within this delay.
• audible (No / Yes), to activate a klaxon.
relevant gravity.
- Figure 406 - Setting 'alarms' attributes of a

counter profile
7.3.2.6.5 Setting 'Mean value' attributes of a counter profile

When adding a Counter profile, some ‘Mean value’ attributes have to be updated (1). They are
reserved for substation control point usage.
- Figure 407 - Setting 'Mean value' attributes of a

counter profile
7.3.2.7 Defining an SPC profile

To create an SPC profile:
• Add an SPC profile from object entry available at the desired system object level (1).
724 C264/EN UM/E50.5

- Figure 408 - Adding an SPC profile (sample

7.3.2.7.1 Setting 'General attributes' of an SPC profile

When adding an SPC profile, some general attributes have to be updated:
And for linked SPC datapoints:

• control mode available values are:
Direct execute
SBO operate once
SBO operate many
Direct execute with SBO popup (reserved to substation control point usage),
• SBO timeout (range [0, 600 s], step 1s), significant if SBO mode is set to ‘SBO operate once’
or ‘SBO operate many’.
• External fault management (External fault / OK).
- Figure 409 - Setting 'General attributes' of an

SPC profile
7.3.2.7.2 Setting 'Order labels' attributes of an SPC profile

When adding an SPC profile, some ‘Order labels’ attributes have to be updated. They are used for
events and alarm management at BCPU level (logging, display) and for correct SPC order
management:
• ‘Order off’ usage (No / Yes)
• ‘Order on’ usage (No / Yes)
• ‘Order off’ label
• ‘Order on’ label
C264/EN UM/E50.5 725

- Figure 410 - Setting 'Order labels' attributes of an

SPC profile
7.3.2.7.3 Setting 'State treatments' attributes of an SPC profile

When adding an SPC profile, some State treatment attributes have to be updated, for each

archive, logging
archive, no logging
no archive, logging
- Figure 411 - Setting 'State treatments' attribute of

an SPC profile
7.3.2.7.4 Setting 'Alarms' attributes of an SPC profile

When adding a SPC profile, some ‘Alarms’ attributes have to be updated, for the correct alarm
management in case of a negative acknowledgement concerning control of the linked datapoints.
The following alarm information is settable:

within this delay.
726 C264/EN UM/E50.5

• Manual: users needs explicitly clear the alarm,
relevant gravity.
- Figure 412 - Setting 'Alarms' attributes of an SPC

profile
7.3.2.7.5 Setting 'Interlocking and FBD' attributes of an SPC profile

When adding a SPC profile, some ‘Interlocking and FBD’ attributes can be updated for boolean
evaluation of interlocking equation, if the SPC belongs to an interlock equation or if the SPC is an
input of FBD automation (see sections Defining a FBD automation)
The following attributes are settable:

• ‘On order’ interlock value (Invalid / False / True): this attribute defines the value affected to
the On order state of the SPC for evaluation of an interlock equation or a FBD using this SPC.
• ‘Off order’ interlock value (Invalid / False / True): this attribute defines the value affected to
the Off order state of the SPC for evaluation of an interlock equation or a FBD using this SPC.
- Figure 413 - Setting 'Interlocking and FBD'

attributes of an SPC profile
7.3.2.8 Defining a DPC profile

To create a DPC profile:
C264/EN UM/E50.5 727

• Add a DPC profile from object entry available at the desired system object level (1).
• Update the profile attributes (see following sections)
- Figure 414 - Adding a DPC profile (sample given

at BCPU level)
7.3.2.8.1 Setting 'General' attributes of a DPC profile

When adding a DPC profile, some general attributes have to be updated:
And for linked DPC datapoints:

• control mode
Available values are:
Direct execute
SBO operate once
SBO operate many
Direct execute with SBO popup (reserved to substation control point usage),
• external fault management (external fault / OK).
- Figure 415 - Setting 'General' attributes of a DPC

profile
7.3.2.8.2 Setting 'Order labels' attributes of a DPC profile

‘Order labels’ attributes of a DPC profile are used for events and alarm management at BCPU
level (logging, display) and for correct SPC order management:
• ‘Order open’ (set to 01) usage (No / Yes)
• ‘Order close’ (set to 10) usage (No / Yes)
728 C264/EN UM/E50.5

• ‘Order open’ (set to 01) label
• ‘Order close’ (set to 10) label
- Figure 416 - Setting 'Order labels' attributes of a

DPC profile
7.3.2.8.3 Setting 'State treatments' attributes of a DPC profile

When adding a DPC profile, some State treatment attributes have to be updated, for each

archive, logging
archive, no logging
no archive, logging

of a DPC profile
7.3.2.8.4 Setting 'Alarms' attributes of a DPC profile

When adding a DPC profile, some ‘Alarms’ attributes have to be updated, for the correct alarm
The following alarm informations are settable:
C264/EN UM/E50.5 729

within this delay.
• Manual: users needs explicitly clear the alarm,
relevant gravity
Figure 91 SETTING ‘ALARMS’ ATTRIBUTES of a DPC PROFILE
- Figure 418 - Setting 'Alarms' attributes of a DPC

profile
7.3.2.8.5 Setting 'Interlocking and FBD' attributes of a DPC profile

When adding a DPC profile, some ‘Interlocking and FBD’ attributes can be updated for boolean
evaluation of interlocking equation, if the SPC belongs to an interlock equation or if the DPC is an
input of FBD automation (see sections Defining a FBD fast automation).
The following attributes are settable:

• ‘Open order’ interlock value (Invalid / False / True): this attribute defines the value affected to
the Open order state of the DPC for evaluation of an interlock equation or a FBD using this
DPC
730 C264/EN UM/E50.5

• ‘Close order’ interlock value (Invalid / False / True): this attribute defines the value affected
to the Close order state of the DPC for evaluation of an interlock equation or a FBD using this
DPC
Figure 92 SETTING ‘INTERLOCKING AND FBD’ ATTRIBUTES of a DPC PROFILE
- Figure 419 - Setting 'Interlocking and FBD'

attributes of a DPC profile
7.3.2.9 Defining a Setpoint profile

To create a SetPoint profile:
• Add a SetPoint profile from object entry available at the desired system object level .
- Figure 420 - Adding a Setpoint profile (sample

7.3.2.9.1 Setting 'General' attributes of setpoint profile

When adding a SetPoint profile, some general attributes have to be updated:
• short name and long name of the profile only used for profile identification in SCE
And for linked SetPoint datapoints:
C264/EN UM/E50.5 731

• control mode: available values are:
• Direct execute
• SBO operate once, reserved for future use
• SBO operate many, reserved for future use
• Direct execute with SBO control box (reserved to substation control point usage), similar to
‘Direct execute’ for computer, reserved for future use
• unit used for display, logging and alarm at BCPU level.
- Figure 421 - Setting 'General' attributes of a

Setpoint profile
7.3.2.9.2 Setting 'Treatments on event' attributes of setpoint profile

When adding a SetPoint profile, the ‘treatment on event’ attribute have to be updated globally for
all available control and acknowledgement steps of the linked datapoints (1).
The available values for this attribute are:

• No archive, no logging.
• Archive, logging.
• Archive, no logging.
For BCPU configuration, a more synthetic vision of logging and archiving is deduced from this
attribute.
- Figure 422 - Setting 'State treatment' of a

Setpoint profile
7.3.2.9.3 Setting 'Alarms' attributes of setpoint profile

When adding a SetPoint profile, some ‘Alarms’ attributes have to be updated, for the correct alarm
732 C264/EN UM/E50.5

The following alarm informations are settable:

• defined (No / Yes)
within this delay
• gravity (range [1, 5], step 1)
• audible (No / Yes), to activate a klaxon
• Manual: users needs explicitly clear the alarm ,
relevant gravity
- Figure 423 - Setting 'Alarms' attributes of

SetPoint profile
7.3.3 Defining computer local archiving of datapoint events

A computer manages only archiving of the datapoints it is server of (refer to "Networking BCPU on
a Station Bus network" on page 600 for Client / Server definition).
For computer, archiving is available or not for all the events appearing on a given datapoint.
Archiving is activated as soon as one ‘state treatment’ attribute is set to ‘Archive and logging’ or
‘archive only’ at datapoint profile level (refer to "Linking a datapoint to a profile" on page 708).
7.3.4 Defining computer local archiving of datapoint alarms

A computer manages only archiving of the datapoints it is server of (refer to "Networking BCPU on
a Station Bus network" on page 600 for Client / Server definition).
Alarm archiving at computer level is defined globally for all the computers at Scs object level refer
to "Setting general system configuration relevant to MiCOM C264" on page 567)
7.3.5 Defining computer local logging of datapoint events and alarms

A computer manages only logging of the datapoints it is server of (refer to "Networking BCPU on a
Station Bus network" on page 600 for Client / Server definition).
For computer, event logging is available or not for all the events appearing on a given datapoint.
C264/EN UM/E50.5 733

Event logging is activated as soon as the datapoint profile is linked to the local printer of the
computer via the relation ‘has events logged on’. To link a datapoint profile to a printer, refer to
"Linking a datapoint to a profile" on page 708.
Alarm logging is activated as soon as the datapoint profile is linked to the local printer of the
computer via the relation ‘has alarm events logged on’. To link a datapoint profile to a printer, refer
to "Linking a datapoint to a profile" on page 708.
To create a computer printer, refer to "Adding a printer" on page 590.
7.3.6 Defining acquisition source for inputs datapoints

Input datapoints have real-time values, fed by several ways exclusive each other:
• Acquisition via input channel(s)
• Acquisition via IED legacy network
• Acquisition via non-EPAS IEC 61850 communicant IED
• (virtual) acquisition via software production:
diagnostic and control of system components
datapoints relevant to built-in function and user’s function
MV datapoint produced by computation associated to Measurement Point
Hereafter are described standard ways to define acquisition source for input datapoints at SCE
level. SCE provides facilities to create and wire datapoints directly from specific wiring tables. The
usage of these tables is described more precisely in chapter Human Machine Interface of SCE
User manual (part Configuration facilities).
7.3.6.1 Acquiring input datapoint via input channels

At SCE level, linking datapoint to specific channels (DI) belonging to EPAS device boards does
input datapoint wiring.
An easier way to wire datapoints is using wiring table facilities provided by SCE (refer the SCE
documentation for details)
7.3.6.1.1 Wiring an SPS datapoint via one DI channel

A wired SPS is in the SET or in the RESET state, depending on the state of the associated Digital
Input and of the mode, normal or inverted (defined in configuration), of the SPS.
DI state Mode SPS state

ON Normal SET
OFF Normal RESET
ON Inverted RESET
OFF Inverted SET
Error detected * SELFCHECK ERROR DETECTED
To wire a SPS datapoint on a DI channel:
734 C264/EN UM/E50.5

• Add the relation ‘wired on’ (1) at SPS datapoint level.
• Fill the relation with the relevant DI channel:

When datapoint level is lower than or equal to bay level, only DI channels from DIU boards
belonging to the protection that manages the bay, are available. To define the computer that
manages a bay, refer to section "Defining a Bay" on page 758.
• If necessary, update the relation attribute ‘inverted value’ (2), whose meaning is given
previously.
- Figure 424 - Wiring one SPS datapoint via one DI

channel
- Figure 425 - Updating the wiring of an

SPS datapoint
7.3.6.1.2 Wiring a DPS datapoint via two DI channels

To wire a DPS datapoint on two DI channels:
• Add the relations ‘closed' wired on (1) and 'open' wired on (2) at DPS level.
• Fill the relations with the relevant DI channels:

When datapoint level is lower than or equal to bay level, only DI channels from DIU boards
belonging to the computer that manages the bay are available. To define the computer that
manages a bay, refer to section "Defining a Bay" on page 758.
C264/EN UM/E50.5 735

- Figure 426 - Wiring a DPS datapoint via two DI

channels
7.3.6.1.3 Wiring a MPS datapoint via N DI channels

MPS datapoint wiring is done via 3 or more DI channels (up to 16) for each state, and an optional
DI channel for ‘read inhibit’ indication.
To wire a MPS datapoint on n DI channels (n <=16):

• Add the relations ‘state wired on’ (1) at MPS datapoint level, for each available state of the
MPS (i begins from 0).
• Fill the relations with the relevant DI channels: when datapoint level is lower than or equal to
bay level, only DI channels from DIU boards belonging to the BCPU that manages the bay,
are available. To define the computer that manages a bay, refer to section "Defining a Bay" on
page 758.
• If a read inhibit signal exists for the MPS, add the relations ‘read inhibit wired on’ (2) at MPS
datapoint level.
- Figure 427 - Wiring a MPS datapoint via N DI

channels
7.3.6.1.4 Wiring MV and TPI datapoint via N DI channels

MV and TPI datapoint wiring is done via via up to 64 DI channels (for digital measurements) and
two optional DI channels for ‘read inhibit’ indication and sign bit.
To wire an MV or TPI datapoint on n DI channels (n <=64):

• Add the relations ‘bit wired on’ (1) at MV or TPI datapoint level, for each available bit
channel of the MV or TPI (i begins from 0).
736 C264/EN UM/E50.5

• Fill the relations with the relevant DI channels: when datapoint level is lower than or equal to
bay level, only DI channels from DIU boards belonging to the computer that manages the bay,
page 758.
• If a read inhibit signal exists for the MV or TPI, add the relations ‘read inhibit wired on’ (2) at
MV or TPI datapoint level.
• If a sign bit exists for the MV, add the relations ‘sign bit wired on’ (3) at MV datapoint level.
- Figure 428 - Wiring MV or TPI datapoint via N DI

channels
7.3.6.1.5 Wiring a Counter datapoint

A "standard" Counter datapoint ("counter type" attribute set to "standard") wiring is done via one
DI channel (simple standard counter) or two DI channels (double standard counter).
To wire a Counter datapoint on DI channel:

• Add the relation ‘primary input wired on’ (1) at Counter datapoint level.
• If it is a double counter, add the extra relation ‘secondary input wired on’ (2) at Counter
datapoint level.
• Fill the relations with the relevant DI channel: when datapoint level is lower than or equal to
bay level, only DI channels from DIU boards belonging to the computer that manages the bay,
page 758.
• When the counter is used as an energy counter ("counter type" attribute set to "Energy
import" or "Energy Export") no wiring is needed but the relation "integrate: MV electrical
datapoint" (3) must be added to define the input of the counter. This relation must be filled
with the relevant MV datapoint.
C264/EN UM/E50.5 737

- Figure 429 - Wiring counter datapoint via DI channel
7.3.6.2 Acquiring input datapoint via an IED legacy network

At SCE level, IED wiring is not described. Acquiring input datapoint issued from IED is done by
giving it a communication address in the relay’s legacy network mapping. This addressing can be
seen as a virtual wiring regardless to channel wiring.
Addressing a MPS datapoint on an IED legacy network is not available.
Depending on legacy network type, addressing information can be different.
See section "Defining BCPU configuration in system architecture" on page 567 for further details
about IED legacy network creation and addressing mapping definition.
To link an input datapoint to an existing IED address in an IED mapping:

• Add the relation ‘has for IED address’ (1) at datapoint level. Generally, only one relation
adding is available for datapoint, except for DPS datapoint where up to 2 relations can be
added, corresponding to each elementary bit of the DPS if the legacy protocol does not
support the DPS feature. In that case, the DPS is split in two SPS regarding to the legacy
protocol.
• Fill the relation with the relevant IED address: when datapoint level is lower than or equal to
bay level, only IED addresses from IEDs belonging to the computer that manages the bay,
page 758.
738 C264/EN UM/E50.5

- Figure 430 - Acquiring input datapoint via IED legacy network (e.g. SPS datapoint)

• A "DPS" datapoint can have one or two relation(s) "has for IED address":
- In the case of one IED address, the attribute "contact type" of the IED address must be set to
the "Unused" value.
- In the case of two IED addresses, the attribute "contact type" of one of the IED addresses
must be set to the "open" value, and the attribute "contact type" of the other IED address must
be set to the "close" value.
7.3.6.3 Acquiring input datapoint via non-EPAS IEC 61850 communicant IED
To use datapoints issued from a non-EPAS IEC 61850 communicant IED, realize the following
actions at SCE level:
• Create the non-EPAS IEC 61850 communicant IED in the system topology,
• Import its IEC 61850 ICD (IED capability description), to create its IEC 61850 mapping,
• Create the electrical topology (bay, module) relevant to the datapoints served by the non-
EPAS IEC 61850 communicant IED,
• Map manually the datapoints of this electrical topology to IEC 61850 addresses of the non-
EPAS IEC 61850 communicant IED (link data objects to datapoints) via launching ‘Manual
IEC Mapper’ SCE dialog on the IED (‘Manual IED mapping’ in the IED contextual menu),
• Configure the usage of datapoints of the IED in some functions of the MiCOM C264, e.g. input
plug of user function,
• Launch ‘data model and data flow update’ SCE function (refer to section "Networking BCPU
on a Station Bus network" on page 600).
Do not confuse:
C264/EN UM/E50.5 739

• Obtain an IEC 61850 address to a datapoint, wired on the MiCOM C264 , via ‘data model and
data flow update’ SCE function. In that case, the datapoint is served/produced/managed by
the MiCOM C264.
• Map an IEC 61850 address to a datapoint on a non-EPAS IEC 61850 communicant IED, via
‘Manual IED mapping’ SCE function. In that case the datapoint can not be wired, because it is
served/produced/managed by the non-EPAS IEC 61850 communicant IED.
7.3.6.4 Producing input datapoint

Another way to produce input datapoint real-time values is to allow software functions to generate
them.
This is done at several software levels:

• Supervision of IEC 61850 EPAS system device, where system datapoints are produced to
indicate mode device, synchro device, database status, …
• Supervision of IEC 61850 EPAS system device board (board status diagnostics).
• Supervision of legacy network and IED managed by EPAS computers (communication status
diagnostics).
• Supervision of redundancy between two EPAS computers (redundancy status diagnostics).
• Supervision of logging printers managed by HMI server or EPAS computer (printer status
diagnostics).
• Supervision of archiving managed by HMI server (archiving status diagnostics).
• Facilities given by built-in electrical and grouping functions or user’s function, in EPAS BCPU.
7.3.6.4.1 Implicit production of system input datapoint via system decomposition

In data modeling many components of the system topology own input datapoints. Their creation is
generally implicit when creating the component: they belong to its hierarchy.
Most of system input datapoints when transmitted on station bus network are addressed in
IEC 61850 diagnostics bricks.
The list of such system datapoints are given in section "Setting system information of board" on
page 684.
7.3.6.4.2 Implicit production of electrical input datapoint via built-in function

Implicit input datapoints can be embedded in built-in function creation. For details concerning
built-in functions refer to "Defining BCPU configuration in electrical architecture" on page 751
7.3.6.4.3 Explicit production of electrical input datapoint via user function

By setting output plug, fast automation can produce real-time value for electrical input datapoint
(see section "Defining an FBD fast automation" on page 834).
So can slow automation when it manages electrical datapoints or owns management input
datapoints (see section "Defining an ISaGRAF® slow automation" on page 843).
For group needs, an electrical SPS containing the group result must be created (see section
"Defining a group" on page 848).
For SPS-DPS association, the resulting DPS is the product of the two SPS associations (see
section "Producing a DPS from two SPS" on page 851).
740 C264/EN UM/E50.5

To define (open or close) interlocking equation on SPC or DPC datapoint, an extra (open or close)
SPS has to be produced, whose result is interlocking equation computation (see section "Defining
interlocking" on page 851).
7.3.6.4.4 Explicit electrical input datapoint via CT/VT computation

Another way to produce a MV electrical datapoint is to link it to a CT/VT computer board. Then, a
specific link attribute must be filled to precise which MV computation is concerned (power,
harmonic ...).
Data produced by CT/VT board computation concern:

• RMS Values of phase voltage
• RMS values of busbar voltage
• RMS values of phase current
• RMS values of residual voltage and current
• Fundamental sequence components
• Active Power
• Reactive Power
• Apparent Power
• Frequency
• Harmonics levels (expressed as a ratio of the magnitude of the fundamental voltage or

fundamental current)
To link a MV datapoint to a CT/VT computation:

• Add the relation ‘is computed by’ at MV datapoint level.
• Fill the relation with the relevant CT/VT board. When datapoint level is lower than or equal to
bay level, only the CT/VT board belonging to the computer that manages the bay, is available.
To define the computer that manages a bay, refer to section "Defining a Bay" on page 758.
• Update the relation attribute ‘measure type’, giving the computation type.
- Figure 431 - Defining CT/VT computation for a MV datapoint
SCE provides facilities to create MV datapoints issued from CT/VT computation directly from a
specific table (via contextual menu on the CT/VT board). The usage of this table is described
more precisely in chapter Human Machine Interface of SCE User manual (part Configuration
facilities).
C264/EN UM/E50.5 741

7.3.7 Defining control source for output datapoints

Output datapoints have real-time control values, managed by several ways exclusive each other:
• control via output channel(s)
• control via IED legacy network.
• control via non-EPAS IEC 61850 communicant IED
• (virtual) control via software production:
control of system components
datapoints relevant to built-in function and user’s function
Hereafter are described standard ways to define control source for output datapoints at SCE
level. SCE provides facilities to create and wire datapoints directly from specific wiring tables. The
usage of these tables is described more precisely in chapter Human Machine Interface of SCE
User manual (part Configuration facilities).
7.3.7.1 Controlling output datapoint via output channels

At SCE level, linking datapoint to specific channels (DO channels) belonging to EPAS BCPU’s DI
DO or POWER SUPPLY boards does output datapoint wiring.
7.3.7.1.1 Wiring a SPC datapoint via one DO channel

To wire a SPC datapoint on a DO channel:
• Add the relation ‘wired on’ (1) at SPC datapoint level.
• Fill the relation with the relevant DO channel: when datapoint level is lower than or equal to
bay level, only DO channels from boards belonging to the BCPU that manages the bay, are
available. To define the BCPU that manages a bay, refer to section "Defining a Bay" on page
758.
- Figure 432 - Wiring a SPC datapoint via one DO

channels
7.3.7.1.2 Wiring DPC datapoint via two or four DO channels

To wire a DPC datapoint on two or four DO channels:
• Add the relations ‘closed wired on’ (1) and ‘open wired on’ (2) at DPC datapoint level (these
relations can be added two times in case of 4 DO channels use).
742 C264/EN UM/E50.5

• Fill the relations with the relevant DO channels: when datapoint level is lower than or equal to
bay level, only DO channels from DOU boards belonging to the computer that manages the
bay, are available. To define the computer that manages a bay, refer to section .
- Figure 433 - Wiring a DPC datapoint via two DO

channels
7.3.7.1.3 Wiring SetPoint datapoint

SetPoint datapoints can only be wired on digital channels (up to 48 DO channels) and two
optional DO channel for ‘read inhibit’ indication and sign bit and can also be wired on 1 Analogue
channel.
To wire a SetPoint datapoint on n DO channels (n <=48):

• Add the relations ‘bit wired on’ (1) at SetPoint datapoint level, for each available bit
channel of the SetPoint (i begins from 0)
• Fill the relations with the relevant DO channels: when datapoint level is lower than or equal to
bay level, only DO channels from boards belonging to the BCPU that manages the bay, are
available. To define the BCPU that manages a bay, refer to section "Defining a Bay" on page
758
• If a read inhibit signal exists for the SetPoint (see section "Overview of SetPoint processing"
on page 705), add the relations ‘read inhibit wired on’ (2) at SetPoint datapoint level.
• If a refresh signal exists for the SetPoint (see section "Overview of SetPoint processing" on
page 705), add the relations ‘refresh wired on’ (3) at SetPoint datapoint level.
• If a sign bit exists for the SetPoint, add the relations ‘sign bit wired on’ (4) at SetPoint
datapoint level.
C264/EN UM/E50.5 743

- Figure 434 - Wiring a SetPoint datapoint via DO

channel and AO channel

• A Setpoint datapoint wired on DO channels of Computer, must be digital and have its profile
attribute “SBO mode” set to "Direct Execute" or “Direct Execute with SBO popup”
7.3.7.1.4 Wiring from CCU datapoint

SPC, DPC datapoint can also use digital outputs of CCU boards.
- Figure 435 - Acquiring output datapoint using CCU board
7.3.7.2 Controlling output datapoint via an IED legacy network

At SCE level IED wiring is not described. Controlling output datapoint issued from IED is done by
giving it a communication address in the relay’s legacy network mapping. This addressing can be
seen as a virtual wiring regardless to channel wiring (implicit association is done at IED level).
Depending on legacy network type, addressing information can be different.
See section "Networking IED on computer legacy network" on page 602 for further details about
IED legacy network creation and addressing mapping definition.
To link an output datapoint to an existing IED address in an IED mapping:
744 C264/EN UM/E50.5

• Add the relation ‘has for IED address’ (1) at datapoint level. Generally, only one relation
adding is available for a datapoint, except for a DPC datapoint where up to two relations can
be added, corresponding to each elementary bit of the DPC if the legacy protocol does not
support the DPC feature. In that case, the DPC is split in two SPC regarding to the legacy
protocol.
• Fill the relation with the relevant IED address: when datapoint level is lower than or equal to
bay level, only IED addresses from IEDs belonging to the computer that manages the bay,
page 758.
- Figure 436 - Acquiring output datapoint via IED legacy network (e.g. SPC datapoint)

• A "DPC" datapoint can have one or two relation(s) "has for IED address":
- In the case of one IED address, the attribute "contact type" of the IED address must be set to
the "Unused" value.
- In the case of two IED addresses, the attribute "contact type" of one of the IED addresses
must be set to the "open" value, and the attribute "contact type" of the other IED address must
be set to the "close" value.
7.3.7.3 Controlling output datapoint via non-EPAS IEC 61850 communicant IED
To use datapoints issued from a non-EPAS IEC 61850 communicant IED, realize the following
actions at SCE level:
• Create the non-EPAS IEC 61850 communicant IED in the system topology,
• Import its IEC 61850 ICD (IED capability description), to create its IEC 61850 mapping,
• Create the electrical topology (bay, module) relevant to the datapoints served by the non-
EPAS IEC 61850 communicant IED,
C264/EN UM/E50.5 745

• Map manually the datapoints of this electrical topology to IEC 61850 addresses of the non-
EPASIEC 61850 communicant IED (link data objects to datapoints) via launching ‘Manual
IEC Mapper’ SCE dialog on the IED (‘Manual IED mapping’ in the IED contextual menu),
• Configure the usage of datapoints of the IED in some functions of the MiCOM C264, e.g. input
plug of user function,
• Launch ‘data model and data flow update’ SCE function (refer to section "Networking BCPU
on a Station Bus network" on page 600).
Do not confuse:
• Obtain an IEC 61850 address to a datapoint, wired on the MiCOM C264 , via ‘data model and
data flow update’ SCE function. In that case, the datapoint is served/produced/managed by
the MiCOM C264.
• Map an IEC address to a datapoint on a non-EPAS IEC 61850 communicant IED, via ‘Manual
IED mapping’ SCE function. In that case the datapoint can not be wired, because it is
served/produced/managed by the non-EPAS IEC 61850 communicant IED.
7.3.7.4 Producing output datapoint

Another way to produce output datapoint real-time control values is to allow software functions to
generate them.
This is done at several software levels:

• Supervision of IEC 61850 EPAS system device, where system datapoints are produced to
control mode device, database switch.
These output system datapoints are only used by Web Computer Administation Tool.
• Supervision of redundancy between two EPAS computers (redundancy controls).
• Facilities given by built-in electrical and grouping functions or user’s function, in EPAS
computers.
7.3.7.4.1 Implicit production of system output datapoint via system decomposition

In data modeling, only EPAS devices of the system topology own output datapoints for device
mode management and database switch. Their creation is implicit when creating the device: they
belong to its hierarchy.
Computer redundancy needs specific output typed datapoints that must be manually added in
computer’s hierarchy.
Most of system output datapoints when transmitted on station bus network are addressed in
IEC 61850 diagnostics bricks.
The list of such system datapoints are given in section "Setting system information of board" on
page 684.
7.3.7.4.2 Implicit production of electrical output datapoint via built-in function

Implicit output datapoints can be embedded in built-in function creation. For details refer to
"Defining BCPU configuration in electrical architecture" on page 751.
7.3.7.4.3 Explicit production of output datapoint via user function

By setting output plug, fast automation can produce real-time order value for electrical output
datapoint (see section "Defining an FBD fast automation" on page 834).
746 C264/EN UM/E50.5

So can slow automation when it manages electrical output datapoints or owns management
output datapoints (see section "Defining BCPU configuration in electrical architecture" on page
751).
For xPS-xPC association, an electrical output SPC or DPC linked to the SPS or DPS must exist
and sometimes be created (see section "Controlling xPC by xPS change of state" on page 850).
7.3.7.5 Acknowledgment definition in case of simultaneous

ordersAcknowledgment definition in case of simultaneous orders
When two opposite orders (Open/Close or Close/Open) are simultaneous and from different
origins, the acknowledgment management is described on the following table:
Cmd1 Cmd2 Action Ack

Cmd 1
PSL PSL NA
cancelled
Cmd 1
PSL Operator NA
cancelled
CO_ACK_
Cmd 1
Operator PSL FAILED_ORDER
cancelled
(ACK 19)
CO_REQUEST_
Cmd 2
Operator Operator IN_PROGRESS
Ignored
(ACK 6)
When two identical orders (Open/Open or Close/Close) are simultaneous and from different
origins, the acknowledgment management is described on the following table:
Cmd1 Cmd2 Action Ack

Cmd 2
PSL PSL NA
Ignored
CO_REQUEST_
Cmd 2
PSL Operator IN_PROGRESS
Ignored
(ACK 6)
Cmd 2
Operator PSL NA
Ignored
CO_REQUEST_
Cmd 2
Operator Operator IN_PROGRESS
Ignored
(ACK 6)
7.3.8 Defining datapoint association

This functionality allows to create a link between two datapoints so that the state of one datapoint
(called the target datapoint) is defined by the state of the other datapoint (called the original
datapoint).
C264/EN UM/E50.5 747

Target datapoints can be one of the following types: SPS or DPS. They are available with default
name Mapping SPS and Mapping DPS at each level of the Electrical topology. In the example
given here after these two "target" datapoints are shown at the Substation level (1).
- Figure 437 - The two target datapoint of the

substation level
Original datapoints can be one of the following types: SPS, DPS, MPS, MV.
7.3.8.1 Adding a target datapoint

Addition of a target datapoint is done via the “Objects entry” area associated to the required
electrical level (Substation in our example) by double clicking the mapping xPS (or right-clicking it
and then clicking Add).
7.3.8.2 Linking the target datapoint to the original datapoint

To link the target datapoint to the original datapoint a relation 'is mapped on' (1) must be added to
the selected "original" datapoint (order running at generic bay level in our example). When added
the undefined relation is present in the "Contents of" window associated to the order running
datapoint (2).
- Figure 438 - Linking the target datapoint of the

original datapoint
748 C264/EN UM/E50.5

To select the target datapoint double-click the undefined relation "is mapped on:" (3). In the
Relation link editor dialog box are displayed all the available Mapping DPS datapoints (4). Click
the Mapping DPS datapoint you want to be associated to the order running datapoint (Subs
Mapping DPS in our example) then click the OK button.
- Figure 439 - Selecting the target datapoint
7.3.8.3 Defining the states associations

For every possible state of the original datapoint the user can define the corresponding state of
the target datapoint. To perform this association click the now defined relation "is mapped on:" (5)
in the "Contents of:" window associated to the "order running" datapoint. In the "Attributes of:"
window associated to this relation are listed all the possible states of the original datapoint (6) and
for each one the user has to select the corresponding state of the target datapoint (7).
- Figure 440 - Defining the states associations

• Up to 10 target datapoints can be associated to an original datapoint.
• Up to 100 datapoints can be defined as original datapoints.
• The original datapoint and the target datapoint can belong to different BCPUs. In this case the
states of the original datapoints are transmitted through GOOSE messages.
• A target datapoint is managed as any other datapoint: transmission, used in automation,
alarms, …
C264/EN UM/E50.5 749

• A SPS original datapoint can be associated to a SPS or a DPS.
• A DPS original datapoint can be associated to a SPS or a DPS.
• A MPS original datapoint can only be associated to a SPS ( the relation "is mapped on:
Mapping DPS Electrical datapoint" is not available in the "Object entry" window associated to
a MPS).
• A MV original datapoint can only be associated to a SPS ( the relation "is mapped on:
Mapping DPS Electrical datapoint" is not available in the "Object entry" window associated to
a MV).
750 C264/EN UM/E50.5

7.4 Defining BCPU configuration in electrical architecture

7.4.1 Defining an electrical topology
At SCE data modelling level, the entry point of electrical topology is the ‘Site’ object. At the
moment, a ‘Site object’ (1) can be composed of only one ‘Substation’ object.
A substation (2) is constituted of ‘Voltage level’ objects, each of them corresponding to an

electrical partitioning of the substation by voltage level value (in kV).
A voltage level (3) is an aggregation of ‘Bay’ object (4), grouping of electrical devices, called
module (5). Generally, this grouping is electrically self-protective, i.e. can be isolated from other
bays by switchgear for maintenance and managed by only one EPAS protection. There are
different kinds of bays: feeder, transformer, busbar, bus coupler, bus section, capacitor bank and
generic bay.
Coupling two voltage levels is commonly done via transformer. To respect SCE data modelling
electrical partitioning, this transformer has to belong to a transformer bay (6) arbitrary put in one of
both voltage levels (generally its primary). An extra relation on transformer defines to which
voltage level its secondary (or primary) belongs.
Final electrical components are modules composing bays. There are different kinds of modules:
circuit breaker, switchgear, transformer, motor, generator, battery, capacitor, inductor, converter
and generic module. An extra module exists to describe substation external connection (external
line).
Every level of the electrical topology, except Site level, can own datapoints whose features and
configuration are described in section Defining datapoint.htm.
- Figure 441 - Electrical topology definition (E.G.)
C264/EN UM/E50.5 751

- Figure 442 - Bay samples
- Figure 443 - Modules samples
7.4.1.1 Defining a Site

When creating a new configuration with the SCE, the electrical topology is automatically
instantiated via a ‘Site’ root object, containing a mandatory ‘Substation’ object.
A Site object corresponds to customer project identification: its attributes short name and long
name (1) can be entered at SCE level.
- Figure 444 - Setting attributes of a Site
752 C264/EN UM/E50.5

7.4.1.2 Defining a Substation

When creating a new configuration using SCE, the electrical topology is automatically instantiated
via ‘Site’ root object, containing a mandatory ‘Substation’ object.
A Substation object corresponds to customer substation identification: its attributes short name
and long name (1) have to be entered at SCE level, for proper logging formatting and datapoint
identification, at protection and operator interface levels.
At substation level, the attribute ‘default uniqueness’ (2) defines the way control uniqueness is
managed for the whole substation. Available values are:
• None: no control uniqueness is provided by EPAS system for the substation.
• Substation level: control uniqueness is provided by EPAS system for the whole substation,
i.e. two simultaneous controls are refused within the substation, except for control datapoints
configured as substation uniqueness independent (see sections "Defining SPC datapoint" on
page 700, "Defining DPC datapoint" on page 702 and "Defining SetPoint datapoint" on page
706).
• Bay level: control uniqueness is provided by EPAS system for an entire bay, i.e. 2
simultaneous controls are refused within the same bay, except for control datapoints
configured as bay uniqueness independent (see sections "Defining SPC datapoint" on page
700, "Defining DPC datapoint" on page 702 and "Defining SetPoint datapoint" on page 706).
- Figure 445 - Setting attributes of a Substation
Bay and substation uniqueness are managed by BCPU by synthesis of mandatory SPS
datapoints ‘Order running’, automatically added under a bay at its creation (see section
"Networking BCPU on a Station Bus network" on page 600).
7.4.1.2.1 Adding a substation generic datapoint

The addition of a substation typed datapoint is done via the “Objects entry” window at substation
level by clicking on mouse’s right button. Here are listed generic datapoint (standard usage) out of
scope of the specific substation function:
• Local/remote for substation (see section Defining Local Remote for substation.htm)
• Taking Control for substation and SCDA links (see section Defining Taking Control for
substation and SCADA links)
For more details about datapoints and their configuration, refer to section .
C264/EN UM/E50.5 753

- Figure 446 - Adding generic datapoint to a

substation
A Global alarm ack SPS (1) can be added to the substation level in order to automatically
acknowledge the new alarms in the MiCOM C264 and also in the OI. The detection mode attribute
of this SPS must be set to "Permanent" or "Permanent with computer auto-reset". This SPS may
be any wired SPS or SPS activated by a control ( by using the Glb alm ack ctrl SPC(2)) from the
SCADA or generated by any PSL. It is also possible to launch a global alarm acknowledgment at
a fixed time by using a cyclic SPS (described in section Adding bay generic datapoint)
7.4.1.2.2 Defining Local/Remote for substation

A substation can be in remote or local control mode.
The Remote mode indicates that the substation is controlled from Remote Control Point (RCP),
via gateway. No controls can be sent from Substation Control Point level (except if the concerned
bay is in SBMC mode).
The Local mode indicates that the substation is controlled from EPAS Operator Interface
(Substation Control Point). The controls issued from RCP are not taken into account by the
system, they are refused.
Some controls, defined during the configuration phase, can be independent of the substation
control mode: it means they can be issued from SCP or RCP whatever the current control mode
is. Controls from configurable automation are accepted whatever was the mode. For details about
the configuration of this dependency attribute, refer to sections "Defining SPC datapoint" on page
700, "Defining DPC datapoint" on page 702 and "Defining SetPoint datapoint" on page 706.
In Local or Remote mode the information acquired by BCPUs and IEDs are always sent to RCP
and EPAS Operator Interface.
The automatic “Forcing of Invalid BI” function is used to avoid processing of invalid states of the
substation mode (the local or remote replacement state is defined in configuration). The “Forced
Local” state is processed as the “Local” state. The “Forced Remote” state is processed as the
“Remote” state.
Moreover, all IEC 61850 clients (i.e. Operator Interface, gateway, protections) will automatically
force the substation mode to “Forced Local” or “Forced Remote” if it takes the UNKNOWN state
(due for example to the loss of communication detected between the protection which manages
the substation mode and the IEC 61850 clients).
754 C264/EN UM/E50.5

To activate Local/remote substation facilities:

• add the optional datapoints ‘Local/remote DPS’ (1) and/or ‘Loc/rem ctrl DPC’ (2), via the
“Objects entry” window at substation level by clicking on mouse’s right button,
• configure them (see section "Defining datapoint" on page 689),
• if necessary, links the control of the Local/remote with the Local/remote status datapoint, via
‘has for feedback’ relation.
- Figure 447 - Defining Local/Remote for

Substation
Hereafter, the term "wired" means that the datapoint has to be wired on digital channel(s) of a
BCPU.
• If "Loc/rem ctrl DPC" is present, then "Local/remote DPS" has to be present (it's the
feedback).
• If "Local/remote DPS" is not wired, then "Loc/rem ctrl DPC" is mandatory.
• If "Local/remote DPS" is wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's present, it
has to be wired.
• If, under a Substation, a "DPC" or "SPC" datapoint has its attribute "Substation mode
dependency" set to "Yes", then the Substation "Local/remote DPS" datapoint has to be
present.
• If the two datapoints "Local/remote DPS" and "Loc/rem ctrl DPC" are present, they have to
have the same Server device.
• "Loc/rem ctrl DPC" datapoint has to have its profile attribute “SBO mode” set to "Direct
Execute" or “Direct Execute with SBO popup”.
7.4.1.2.3 Defining Taking Control for substation and SCADA links

This facility allows a Remote Control Point (RCP) to force the mode of the substation from LOCAL
to REMOTE and to define on which link the SCADA controls must be accepted.
To activate Taking control facilities for a given SCADA network:

• add the optional datapoints ‘Taking Control’ (2) and ‘Taking status’ (1), via the “Objects entry”
window at substation level by clicking on mouse’s right button.
• configure them (see section ).
• add the relation ‘is taken control of’ at ‘Taking status’ datapoint level (3) and fill it with the
C264/EN UM/E50.5 755

relevant given SCADA network.

• do not forget to link via ‘has for feedback’ relation, the control with the status datapoint.
- Figure 448 - Defining taking control for a SCADA link

• If, at least, one SCADA network is linked to a Taking Control function, all the SCADA
Networks of the system must be linked to a Taking Control function.
• If a "Taking Status" datapoint is linked to a SCADA Network, it must also be linked to a
"Taking Control" datapoint through the relation "has for feedback".
• A "Taking Control" datapoint must be linked to a "Taking Status" datapoint through the
relation "has for feedback".
• The "Taking Control" datapoint must have its "activation mode" attribute set to a
"Permanent…" value. The "Taking Status" datapoint must have its "detection mode" attribute
set to the "Permanent" value.
• Both "Taking Control" and "Taking Status" datapoints must be linked to a SCADA address in
the mapping of their SCADA network.
• If a Taking-Control function is defined then, the "Loc/rem ctrl DPC" for substation must be
present and not wired.
• The Server of the Local/Remote datapoints is the Server of each datapoints couple "Taking
Status" / "Taking Control".
756 C264/EN UM/E50.5

• All the devices having a SCADA network linked to a Taking-Control function are:
- Clients of each datapoints couple "Taking Status" / "Taking Control".
- Clients of the datapoints couple "Local/remote DPS" / "Loc/rem ctrl DPC".
7.4.1.2.4 Adding a user function to a substation

The addition of a substation user function is done via the “Objects entry” window at substation
level by clicking on mouse’s right button.
- Figure 449 - Adding user function to Substation
7.4.1.3 Defining a Voltage level

At substation level, several ‘voltage level’ objects can be added. A voltage level corresponds to a
substation area whose electrical bays and sub-modules refer to the same nominal voltage. There
is an exception for transformer bay, coupling 2 different voltage levels, that must be arbitrary
located on one of the both.
To create a voltage level, add it from object entry available at substation level, as following:
- Figure 450 - Adding a Voltage level
When adding a voltage level, some general attributes must be updated:

• nominal value in Kv.
• ATCC existence (No / Yes): when set to ‘yes’, an extra tab-pane appears for the voltage
level, to enter specific ATCC regulation feature for the voltage level.
C264/EN UM/E50.5 757


Voltage level
7.4.1.3.1 Adding voltage level generic datapoint

The addition of a voltage level typed datapoint is done via the “Objects entry” window at voltage
level by clicking on mouse’s right button. Here are listed the generic datapoints (standard usage).
For more details about datapoints and their configuration refer to section "Defining datapoint" on
page 689.
- Figure 452 - Adding voltage level generic

datapoint
7.4.1.3.2 Adding user function to voltage level

The addition of a voltage level user function is done via the “Objects entry” area at voltage level by
clicking on mouse’s right button.
- Figure 453 - Adding a user function to voltage

level
7.4.1.4 Defining a Bay

At ‘voltage level’ level, several ‘bay’ objects can be added. A voltage level corresponds to a
substation area whose electrical bays and sub-modules refer to the same nominal voltage. There
is an exception for transformer bay, coupling two different voltage levels that has to be arbitrary
located on one of the both.
758 C264/EN UM/E50.5

To create a bay:
• Add a typed one from object entry available at voltage level (1).
• Update the bay attributes.
• Update its ‘is managed by’ relation, to define which protection manages the bay (2).
- Figure 454 - Adding a typed bay
- Figure 455 - Defining protection managing a bay
When adding a bay, some general attributes have to be updated:

• short name and long name of the bay used for logging, alarms ...
• control uniqueness used for output datapoints under the bay.

None: no control uniqueness is provided by EPAS system for output datapoints under the
bay.
See substation definition: control uniqueness is inherited from attribute ‘default

uniqueness’ at substation level.
- Figure 456 - Setting general attributes of a bay

(sample given for bay type 'Feeder')
C264/EN UM/E50.5 759

When adding a bay, a mandatory SPS datapoint ‘order running’ is automatically created at bay
level. This datapoint allows EPAS system to manage control uniqueness at substation and bay
level: it is set when a control is in progress on a bay.

• When control uniqueness is set to substation, all BCPU of substation have to be IEC 61850
client of all ‘order running’ SPS datapoints defined for all the bays. So, proper IEC 61850
configuration has to be done for all BCPUs to support that feature. For details about
IEC 61850 configuration, refer to section "Networking BCPU on a Station Bus network" on
page 600.
Typed bay features
Using typed bay allows implicit sub-component creation. Hereafter are listed all typed bays with
their sub-component features:
• Feeder: a circuit-breaker and external line modules are mandatory and implicitly created,
• Transformer: a transformer module is mandatory and implicitly created,
• Bus coupler: a circuit-breaker module is mandatory and implicitly created,
• Bus section: a circuit-breaker module is mandatory and implicitly created,
• Capacitor bank: a capacitor module is mandatory and implicitly created,
• Shunt: a circuit-breaker module is mandatory and implicitly created,
• Busbar: no module is available. This typed bay must be seen as a single electrical node. A
specific attribute ‘node reference’ used for electrical topology definition for ATCC function can
be entered for a busbar. .
• Generic bay: no sub-component constraint. Used for general usage outside the scope of
other previous typed bays.
7.4.1.4.1 Adding bay generic datapoint

The addition of a bay typed datapoint is done via the “Objects entry” window at bay level by
clicking on mouse’s right button. Here are listed generic datapoint (standard usage) out of scope
of the specific following bay functions:
• Local/remote for bay (see section "Defining Local Remote for bay" on page 761)
• SBMC for bay
• Group computation (see section "Defining a group" on page 848)
For more details about datapoints and their configuration, refer to section "Defining datapoint" on
page 689.
760 C264/EN UM/E50.5

- Figure 457 - Adding generic datapoint to a bay
NOTE: In BCPU, up to 8 transient SPS (1) can be defined as cyclic (day cycle). They can be
used to activate a periodic treatment. For these SPS the user has to configure, in addition to the
usual attributes of a SPS (previously listed in section "Defining datapoint" on page 689) two
specific attributes (2) which define the time when activation of the SPS will occur.
7.4.1.4.2 Defining Local Remote for bay

Each bay can be independently in Remote or Local mode.
The Remote mode indicates that the bay is controlled from the upper level, i.e. Remote Control
Point (RCP) or Substation Control Point (SCP) depending on the current substation control mode.
No controls can be sent from Bay Control Point (BCP) level, i.e. operator interface at the computer
that manages the bay.
The Local mode indicates that the bay is controlled from BCP. The controls issued from upper
level are not taken into account by the bay.
Some controls, defined during the configuration phase, can be independent of the bay control
mode: it means they can be issued from any control points whatever was the current control
mode. Controls from configurable automation (ISaGRAF®) are accepted in remote mode. For
details about the configuration of this dependency attribute, refer to sections:
• SPC: "Defining SPC datapoint" on page 700,
• DPC : "Defining DPC datapoint" on page 702
• SetPoint : "Defining SetPoint datapoint" on page 706
In Local or Remote mode, the information issued from the bay is always sent to SCP and RCP.
C264/EN UM/E50.5 761

The automatic “Forcing of Invalid BI” function is used to avoid processing of invalid states of the
bay mode (the local or remote replacement state is defined in configuration). The “Forced Local”
state is processed as the “Local” state. The “Forced Remote” state is processed as the “Remote”
state.
To activate Local/remote bay facilities:

• add the optional datapoints ‘Local/remote DPS’ (1) and/or ‘Loc/rem ctrl DPC’ (2), via the
“Objects entry” window at bay level by clicking on mouse’s right button
• configure them (see section ),
• if necessary, do not forget to link via ‘has for feedback’ relation, the control of the
Local/remote with the Local/remote status datapoint.
- Figure 458 - Defining Local/Remote for bay
Hereafter, the term "wired" means that the datapoint must be wired on digital channel(s) of a
computer
• If "Loc/rem ctrl DPC" is present, then "Local/remote DPS" must be present (it's the feedback).
• If "Local/remote DPS" is not wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must not be wired.
• If "Local/remote DPS" is wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's present, it
must be wired.
• If, under a Bay, a "DPC" or "SPC" datapoint has its attribute "bay mode dependency" set to
"Yes", then the Bay "Local/remote DPS" datapoint must be present.
• "Loc/rem ctrl DPC" datapoint must have its profile attribute “SBO mode” set to "Direct
If the "GHU200" board of a computer has its attribute "HMI type" set to the "Simple" value, then
the "Local/remote DPS" datapoints of the bays managed by this computer must be all be "Wired"
or all "System".
7.4.1.4.3 Defining SBMC for bay

Each bay can be set in SBMC mode (Site Based Maintenance Control mode).
In SBMC mode, a bay does not take into account the commands issued from Remote Control
Point (RCP), even if the substation is in remote control (see section ). Some controls, defined
during the configuration phase, can be independent of the SBMC mode. For details about the
configuration of this dependency attribute, refer to sections:
762 C264/EN UM/E50.5

• SPC: "Defining SPC datapoint" on page 700,
• DPC : "Defining DPC datapoint" on page 702
• SetPoint : "Defining SetPoint datapoint" on page 706
This function provides a facility to control selected bays from the Substation Control Point (SCP)
and optionally to suppress or force to a pre-defined state, datapoint for the RCP while the
substation is in Remote mode. If configured as SBMC dependent at its profile level, a datapoint
belonging to a bay in SBMC mode takes the state defined in the profile configuration for the RCP
but is still processed normally in the SCS (e.g. all processes inside the system are unaffected by
the state modification of an information at the RCP interface).
The state of a datapoint sent to RCP is defined in its profile configuration. For each type of
datapoint, they are:
SPS SUPPRESSED, SET, RESET

SUPPRESSED, OPEN,
DPS
CLOSE, JAMMED
MPS SUPPRESSED, UNDEFINED
MV, TPI and
SUPPRESSED
Counter
To activate SBMC facilities at bay level:

• add the optional datapoints ‘SBMC SPS’ (1) and ‘SBMC control SPC’ (2), via the “Objects
entry” window at bay level by clicking on mouse’s right button,
• configure them (see section ),
• do not forget to link via ‘has for feedback’ relation, the control of the SBMC with the SBMC
status datapoint.
- Figure 459 - Defining SBMC for a bay
C264/EN UM/E50.5 763

• If "SBMC SPS" is present, then "SBMC control SPC" must be present.
• If "SBMC control SPC" is present, then "SBMC SPS" must be present.
• If "SBMC control SPC" is present, then its attribute "bay mode dependency" must be set to
"No".
• If a "DPC" or "SPC" datapoint has its attribute "SBMC mode dependency" set to "Yes", then
the "SBMC SPS" datapoint must be present.
• If a "DPS" or "SPS" datapoint has the attribute "SBMC dependant" of its profile set to "Yes",
then the "SBMC SPS" datapoint must be present.
7.4.1.4.4 Adding a user function to a bay

The addition of a bay user function is done via the “Objects entry” window at bay level by clicking
on mouse’s right button.
For more details about user function usage and their configuration, refer to section Defining an
electrical regulation by user function.
- Figure 460 - Adding a user function to a bay
7.4.1.4.5 Adding toggling signal detection

The Toggling Signals SPS is a computed SPS belonging to a bay.
The Toggling Signals SPS is used to know if there is at least one DP with quality “toggling” in the
bay. While there is one or more DP in the quality “toggling”, the Toggling Signals SPS value is
TRUE.
While there is none DP in the quality “toggling”, the Toggling Signals SPS is FALSE.
If a DP in “Toggling” state is forced, substituted or suppressed, it shall be considered not toggling

anymore for the elaboration of the “Toggling Signals” SPS.
There can be only one Toggling Signals SPS per bay.
764 C264/EN UM/E50.5

- Figure 461 - Defining 'Toggling signal' for bay
NOTE: Only SPS, DPS and MPS can have the quality “toggling”. “Toggling” is a detailed quality
of the “invalid” quality.
7.4.1.4.6 Adding Missing Signaling Voltage

The Missing Signaling Voltage (MSV) is an SPS acquired locally and physically by the bay
computer.
This MSV SPS is used to monitor the presence of a voltage polarity.
When the polarity is missing, the value of the MSV SPS is “0” (RESET).
When the polarity is present, the MSV SPS value is “1” (SET).
Datapoints, locally and physically acquired by the bay computer, such as SPS, DPS, MPS and
MV, can be linked to an MSV SPS.
Computation of quality of the datapoints linked to MSV SPS:

• If MSV SPS is in RESET and VALID state, datapoints linked to this MSV have quality set to
“SELF-CHECK FAULT”. With that, false acquisition values acquired because of a missing
polarity voltage are clearly identified and flagged as invalid.
• If the MSV is SET and VALID (including FORCED and SUBSTITUTED) or SUPPRESSED,
the value and quality of linked datapoints are not modified.
• If MSV is SET or RESET and INVALID, datapoints linked to this MSV have quality set to
“SELF-CHECK FAULT”.
• The quality set is unchanged until the MSV goes to SET / VALID or SUPPRESSED.
• On MSV SPS transition to SET / VALID or SUPPRESSED, the current input datapoint [value /
quality] is transmitted, not modified, to the output.
• Datapoints is state FORCED, SUBSTITUTED or SUPPRESSED are not affected by MSV
SPS, the value and quality are not modified.
Configuration
The MSV SPS is created under a functional block named “Quality Manager”.
The SCE allow to add “Quality manager” under a bay, only one “Quality manager” by bay.
C264/EN UM/E50.5 765

- Figure 462 - Defining quality manager for bay
It is possible to configure a maximum of 10 MSV SPS per Quality manager.
- Figure 463 - Defining signaling voltage
Link “has quality overwritten by: Signaling Voltage” is available for datapoint type SPS, DPS, MPS
and MV (not TPI).
It is possible to configure a maximum of 200 data linked per MSV SPS.
- Figure 464 - Defining link “has quality overwritten by: Signaling Voltage”
7.4.1.5 Defining Module

his section deals with general module configuration. Configuring specific typed module is
described in following relevant section.
At ‘bay’ level, several ‘module’ objects can be implicitly or explicitly added. A module corresponds
generally to a substation electrical device.
To create explicitly a module:

• Add a typed one from object entry available at bay (1)
For implicit or explicit module:

• Update the module attributes (see following sections)
766 C264/EN UM/E50.5

- Figure 465 - Adding explicitly a typed module
When adding a module, some general attributes have to be updated:

• short name and long name of the module used for logging, alarms ...
• node reference, used for electrical topology definition for ATCC function.
- Figure 466 - Setting general attributes of a generic module
Typed module features
Using typed module specialises module configuration. Hereafter are listed all typed modules with
their main configuration features:
• Capacitor, Inductor:
Specific attribute ‘reactive power value’ (in MVA), used for ATCC regulation (when
available)
Not lockable module.

• Convertor, generator, motor:
Not lockable module.

• Transformer:
C264/EN UM/E50.5 767

Lockable module.
Supports Tap changer built-in function.
Supports ATCC function needs (when available)

• Circuit-breaker module:
Lockable module.
Supports synchrocheck and autorecloser built-in functions (when available).
May support withdrawing if it exists.

• Switchgear module
Lockable module.
May support withdrawing if it exists.

• External line:
Only support SPS and DPS attribution.

• Generic module:
Lockable module.
Used for general usage outside the scope of other previous typed modules.
7.4.1.5.1 Adding a module generic datapoint

The addition of a module typed datapoint is done via the “Objects entry” window at module level
by clicking on mouse’s right button. Here are listed generic datapoint (standard usage) out of
scope of the specific module functions:
• Group computation (see section "Defining a group" on page 848).
• Locking module (see section "Defining a lockable module" on page 769).
• Specific features and configuration of typed modules (see following sections).
For more details about datapoints and their configuration, refer to section "Defining datapoint" on
page 689.
- Figure 467 - Adding a module generic datapoint

(E. G. for generator module)
7.4.1.5.2 Adding a user function to a module

The addition of a module user function is done via the “Objects entry” window at module level by
Module does not support ISaGRAF® function.
768 C264/EN UM/E50.5

- Figure 468 - Adding user function to a module (E. G. for generator module)
7.4.1.5.3 Defining a lockable module

According to EPAS system, locking module is a system function running on the protection that
manages the bay containing the module.
When a module is locked, any subsequent control acting on it, is refused. Locking is checked
during control sequence processing at BCPU level.
At SCE level, only the following types modules are lockable:

• Circuit-breaker,
• Switchgear,
• Transformer,
• Generic module.
To configure such a module as lockable:

• Add the pre-defined SPS datapoint ‘Lock SPS’ at module level (1) and configure it (see
section "Defining datapoint" on page 689),
• Add the pre-defined SPC datapoint ‘Lock control SPC’ at module level (2) and configure it
(see section "Defining datapoint" on page 689),
• Define the ‘Lock SPS’ as feedback of the ‘Lock control SPC’ by adding and filling ‘has for
feedback’ relation at the SPC level (see section "Defining an SPC feedback" on page 701).
- Figure 469 - Defining a lockable module
C264/EN UM/E50.5 769

Lock SPS and Lock control SPC are datapoints fed and controlled directly by the BCPU that
manages the module. They cannot be wired.

• For “Lock control SPC“, the feedback to “Lock SPS“ is mandatory
7.4.1.5.4 Defining withdrawable circuit-breaker or switchgear

To define a withdrawable circuit-breaker or switchgear:
• add the pre-defined SPS ‘withdraw’ at module level
• configure it (see section "Defining datapoint" on page 689)
Withdraw information is useful for bay mimic animation at computer LCD level. For more details
see section "Defining a computer bay mimic" on page 910.
- Figure 470 - Defining a withdrawable module (E.

G. for circuit breaker)
7.4.1.5.5 Defining a circuit-breaker

This section deals with general circuit-breaker features and available associated input and output
datapoints at BCPU level.
General module features described in section "Defining Module" on page 766 are applicable to
circuit-breaker module and not reviewed here.
When adding a circuit-breaker module, the following specific general attribute have to be updated:
• Circuit-breaker type:
Single phase circuit-breaker, where the 3 phases can be managed independently
Triple phase circuit-breaker, where the 3 phases can only be managed together
Other circuit-breaker: obsolete
- Figure 471 - Setting circuit breaker type
770 C264/EN UM/E50.5

The following tables give inputs and outputs circuit breaker’s features controlled by the BCPU for
triple phase and single phase circuit-breaker. For each datapoint its SCE identification is given by
a number, referenced in the following figure.
When creating a circuit breaker module implicitly or explicitly (cf. section "Defining a Bay" on page
758), the mandatory pre-defined DPS datapoint ‘computed switch position’ (20) is automatically
created.
To configure correctly a circuit-breaker module:

• Add the relevant datapoints, relatively to the following tables,
• configure them (see section "Defining datapoint" on page 689),
• do not forget to link via ‘has for feedback’ relation, the control(s) (1), (11) or (10) of the breaker
with the computed switch position (20) datapoint.
Triple phase circuit-breaker

OUTPUTS CB TYPE B INPUTS CB ALL
OUTPUTS CB TYPE A
(IV) TYPES
(8) DPS or (19) SPS
physical position of the
device (1 phase)
(11) SPC control for
open of device (14) SPS (optional)
DEVICE (1) DPC control for
phase not together
CONTROL open/close of device (10) SPC control for information
close of device
(20) system DPS the
feedback of the control
(I)
DEVICE (9) SPC (optional) (9) SPC (optional) (15) SPS (optional)
SELECTION control of device control of device device selection position
(HARDWARE) selection selection information
Triple phase Triple phase circuit- Triple phase circuit- Triple phase circuit-
circuit-breaker breaker breaker breaker
Single phase circuit-breaker

OUTPUTS CB TYPE B INPUTS CB ALL
OUTPUTS CB TYPE A
(IV) TYPES
C264/EN UM/E50.5 771

Single phase circuit-breaker

(16) SPS or (5) DPS
physical position of
phase A
(2) DPC control for open
(17) SPS or (6) DPS
phase A
(3) DPC control for open phase B
phase B (pulse)
(18) SPS or (7) DPS
DEVICE (1) DPC control for
(4) DPC control for open physical position of
CONTROL open/close of device
phase C phase C
(1) DPC control for close (14) system SPS phase

of device not together information
(II)
(20) system DPS: the

(III)
DEVICE (9) SPC (optional) (9) SPC/DPC (optional) (15) SPS (optional)
SELECTION control of device control of device device selection position
(HARDWARE) selection selection information
Single phase Single phase circuit- Single phase circuit- Single phase circuit-
circuit-breaker breaker breaker breaker
(I) The computed double signal is equal to the physical status if the phase not together status
is equal to “false” else the computed signal is equal to “jammed”.
(II) The computed “phases not together” is equal to “false” if all phases are in the same
position else it is equal to “true”.
(III) The computed signal is equal to the phase A status if the phase not together status is
(IV) Only the “DPC close“ is known by the other IEC 61850 devices:
- For open the device they send the “DPC close” with “open” request
- For close the device they send the “DPC close” with “close” request
772 C264/EN UM/E50.5

- Figure 472 - Available pre-defined datapoints for

circuit breaker

• The two datapoints "Switch Ctrl DPC" and "Switch Ctrl SPC" are mutually exclusive. None is
mandatory
• If physical position of the device is given by an SPS (19), phase not together information (14)
is mandatory
• Set1: {Switch phA DPC, Switch phB DPC, Switch phC DPC}
Set2: {Switch phA SPC, Switch phB SPC, Switch phC SPC}
Set3: {Switch phA pos. DPS, Switch phB pos. DPS, Switch phC pos. DPS}
Set4: {Switch phA pos. SPS, Switch phB pos. SPS, Switch phC pos. SPS}
If the "circuit-breaker type" is set to the "Single phase CircuitBreaker" value, then:
- in a set, if one datapoint is present for a phase, then the two others must be present as well.
- the datapoints of the two sets (1) and (2) are mutually exclusive.
- if the datapoint "Switchgear pos." is present, but none of the three datapoints "Switch PhA
pos", "Switch PhB pos", and "Switch PhC pos" then the SPS datapoint "Ph not together" is
mandatory.
If the "circuit-breaker type" is set to the "Triple phase CircuitBreaker" value, then
no DPC referencing a phase (phA, phB or phC) is allowed.
• "Selection SPC" datapoint must have its profile attribute “SBO mode” set to "Direct Execute"
or “Direct Execute with SBO popup”
C264/EN UM/E50.5 773

7.4.1.5.6 Defining an I²t built-in function (relay folder)

The I²t function is described in chapter Functional description (FT) of MiCOM C264. It is
associated with an overcurrent protection.
• Define and wire a TMU210 board.
• Define the eight MVs that follow:
- Figure 473 - Defining the measurements

• Link them to the TMU210 and give the link the right Measurement type from the drop-down
list. Select the TMU210 board and do a check of the table summing up the wiring.
• Assign the MVs a link Has for IEC address.
• Define the I²t built-in function:
An SPS indicates the on/off status. Its attributes are as follows:
- Figure 474 - I2T computing attributes
A SPC is used to reset all the measurements:
774 C264/EN UM/E50.5

- Figure 475 - I2T reset CTRL attributes

• By launching “Data model and data flow update” SCE function these measurements are
mapped in the IEC 61850 XCBR Logical Node with the following objects (with BCR
IEC 61850 Common Data Class):
• IT_Phase A SumSwAARs
• IT_Phase B SumSwABRs
• IT_PhaseC SumSwACRs
• IT_Total SumSwARs
• I2T_Phase A SumSwA2ARs
• I2T_Phase B SumSwA2BRs
• I2T_PhaseC SumSwA2CRs
• I2T_Total SumSwA2Rs
C264/EN UM/E50.5 775

- Figure 476 - Mapping the measurements
Trip Relay Configuration
2 use cases are proposed:

• Global Trip
• Per function
Use Case Configuration

This mode of operation is recommended in case of operator does not wish to
differentiate the trip contacts according to the protection functions.
For protection functions, please configure the 3 x trip contact to “Yes”
Global Trip
This mode of operation is recommended in case of operator configures the

contacts according to the trip protection features.
Per function
For each protection function, configure only one trip contact to “Yes”
776 C264/EN UM/E50.5

Output Trip Relays
Three Additional SPC and SPS are created to control and Monitor Relay Trip A, B and C.
• 3 SPC (trip #A ctrl, trip #B ctrl and trip #C ctrl) to control the relay from a PSL for example.
• 3 SPS (trip #A status, trip #B status et trip #C status) to monitor the status of the relay.
The trip control allows closure of their respective trip contact using external to protection function
mechanism.
The use of the MiCOM S1 - PACiS allows to activate/de-activate trip of protection function on the
DSPIO board if at least one trip relay has been allocated in the SCE. This feature is available
using the Setting attribute located in the MiCOM S1 - PACiS AUTOMAT.CONTROL section.
Please find example below:
- Figure 477 - Setting DSPIO trip relays with MiCOM S1 - PACiS
7.4.1.5.7 Defining a switchgear

This section deals with general switchgear features and available associated input and output
datapoints at BCPU level.
When adding a switchgear module, the following specific general attributes have to be updated:
• Switchgear type:
Busbar disconnector
Disconnector
Bypass disconnector
Transfer busbar disconnector
Earth switch
C264/EN UM/E50.5 777

- Figure 478 - Setting switchgear type
The following tables give inputs and outputs for the switchgear’s features controlled by the BCPU.
For each datapoint, its SCE identification is given by a number, referenced in the following figure.
To correctly configure a switchgear module:

• Add the relevant datapoints, relative to the following tables,
• configure them (see section "Creating a datapoint" on page 689),
• link via ‘has for feedback’ relation, the control (3) of the switchgear (if it exists) with the switch
position (1) or (5) datapoint.
Switchgear
OUTPUTS TYPE A INPUTS CB ALL TYPES
DEVICE (3) DPC control for open/close of (1) DPS or (5) SPS physical position
CONTROL device of the device (1 phase) (V)
DEVICE
(2) SPC (optional) control of device (4) SPS (optional) device selection
SELECTION
selection position information
(HARDWARE)
- Figure 479 - Available pre-defined datapoints for

switchgear
Control sequence of switchgears
Switchgear devices are managed in “direct execute mode” and in “SBO once mode”.
7.4.1.5.8 Defining a transformer

This section deals with general transformer features and available associated input and output
datapoints at computer level.
778 C264/EN UM/E50.5

When adding implicitly a transformer module via transformer bay creation (refer to "Defining a
Bay" on page 758), the following general attribute must be updated:
• Transformer type:
Double wound: a double wound (or two winding transformer) is a transformer with
galvanic isolation between primary and secondary coil. Tap Changer (with additional
winding) is usually located at HV-neutral side for economic reasons. Tapping-up (raise
order) reduces primary winding and increase LV tension.
Auto transformer: an auto transformer (or Auto-wound or single wound) is a transformer

without galvanic isolation between primary and secondary. Secondary coil follows
primary coil, (windings are serial). Tap Changer (with tap of additional winding) is serial.
Increasing tap position (raise order) acts simultaneously on primary and secondary, it
reduces transformer ratio then voltage at LV side. So, for this type of transformers the
raise order must be inverted (consider as low order).
• Power value (range [1 to 300 MVA), useful for ATCC regulation
• Impedance, whose unit is a percent of value for S=100 MVA (range [0,01 to 24,99 by step
0,01) , useful for ATCC regulation
- Figure 480 - Setting transformer type
Transformer is used for coupling two voltage levels. To respect SCE data modeling electrical
partitioning, this transformer must belong to a transformer bay arbitrary put in one of both voltage
levels (generally its primary). An extra relation must be set on transformer refining which voltage
level its secondary (or primary) belongs to.
To create such a relation:

• Add the correct relation at transformer level
• Fill the relation with the relevant voltage level
C264/EN UM/E50.5 779

- Figure 481 - Completing primary/secondary of

transformer
When adding a transformer, some optional datapoints can be created at module level and must
be configured (see section "Defining datapoint" on page 689):
• MCB position DPS: used for ATCC function (see section Defining an automatic voltage
regulation–ATCC built-in function to give Mini Circuit-Breaker position of associated tap-
changer, via DPS datapoint)
• MCB position SPS: used for ATCC function (see section Defining an automatic voltage
regulation–ATCC built-in function)
- Figure 482 - Transformer optional datapoints
When it exists, tap position of transformer is controlled by a specific built-in function ‘Tap changer’
available at transformer module level. For details about transformer control via tap changer
function, refer to section "Defining a Tap changer built-in function" on page 806.
7.4.2 Defining a Synchrocheck function

7.4.2.1 Completing circuit-breaker definition for synchrocheck
The following tables give inputs and outputs circuit breaker’s features controlled by the computer
for three-phase and single-phase circuit-breaker, when it is concerned by synchrocheck function.
For each datapoint its SCE identification is given by a number, referenced in the following figure
or relevant to the synchrocheck configuration (for datapoints (22), (23), (24) and (25)).
These tables are complements to those described in section "Defining a circuit-breaker" on page
770.
To configure correctly a circuit-breaker module with synchrocheck:
780 C264/EN UM/E50.5

• add the relevant datapoints, relatively to the following tables.
• configure them (see section "Defining datapoint" on page 689).
• do not forget to link via ‘has for feedback’ relation, the control(s) (1), (11) or (10) of the breaker
with the computed switch position (20) datapoint.
• link the circuit-breaker with an existing synchrocheck function created at bay or substation
level. This link is done at synchrocheck level (for details see Creating a synchrocheck
function). Up to 2 circuit breakers can be linked to the same internal synchrocheck.
• configure properly the synchrocheck function itself (for details see Creating a synchrocheck
function.
Triple phase circuit-breaker with synchrocheck

OUTPUTS CB TYPE OUTPUTS CB TYPE INPUTS CB ALL
A B (iv) TYPES
(8) DPS or (19) SPS
(11) SPC control for physical position of the
(1) DPC control for
open of device device (1 phase)
open/close of device
(10) SPC control for (14) SPS (optional)
(23) SPC or (22) DPC
DEVICE CONTROL close of device phase not together
control for close with
information
synchrocheck (23) SPC control for
close with (20) system DPS the
synchrocheck feedback of the control
(I)
SELECTION control of device control of device device selection
(HARDWARE) selection selection position information
(26) SPS or (27) DPS
(24) SPC or (25) DPC (24) SPC or (25) DPC
SYNCHROCHECK (optional) on/off
(optional) control of (optional) control of
SET ON / SET OFF synchrocheck
on/off synchrocheck on/off synchrocheck
information
Single phase circuit-breaker with synchrocheck

OUTPUTS CB TYPE OUTPUTS CB TYPE B INPUTS CB ALL
A (IV) TYPES
C264/EN UM/E50.5 781

Single phase circuit-breaker with synchrocheck

(16) SPS or (5) DPS
(2) DPC control for phase A
open phase A
(17) SPS or (6) DPS
(3) DPC control for physical position of
(1) DPC control for
open phase B phase B
open/close of device
(4) DPC control for (18) SPS or (7) DPS
(23) SPC or (22) DPC
DEVICE CONTROL open phase C physical position of
control for close with
phase C
synchrocheck (1) DPC control for
close of device (14) system SPS
phase not together
(23) SPC control for
information (II)
close with
synchrocheck (20) system DPS: the
(III)
SELECTION control of device control of device device selection
(HARDWARE) selection selection position information
(26) SPS or (27) DPS
SYNCHROCHECK (24) SPC or (25) DPC (24) SPC/DPC
(optional) on/off
SET ON / SET OFF (optional) control of (optional) control of
synchrocheck
(V) on/off synchrocheck on/off synchrocheck
information
(I) The computed double signal is equal to the physical status if the phase not together status is
(II) The computed “phases not together” is equal to “false” if all phases are in the same position
(III) The computed signal is equal to the phase A status if the phase not together status is equal
(IV) Only the “DPC close“ is known by the other IEC 61850 devices:
- For open the device they send the “DPC close” with “open” request
- For close the device they send the “DPC close” with “close” request
(V) Wired SPC and SPS for external synchrocheck and system SPC and SPS for internal
synchrocheck. If is not configured the external synchrocheck module or the synchrocheck
automation is considered always “set on”. DPC and DPS are used only for manual synchrocheck.
782 C264/EN UM/E50.5

- Figure 483 - Available pre-defined datapoints for circuit-breaker breaker with synchrocheck
Do not forget to define ‘Comp. swit. pos.’ mandatory SPS at circuit-breaker level as feedback of
Sync CB close SPC/DPC.

• The two datapoints "Switch Ctrl DPC" and "Switch Ctrl SPC" are mutually exclusive. None is
mandatory.
• If physical position of the device is given by an SPS (19), phase not together information (14)
is mandatory.
C264/EN UM/E50.5 783

• Set1: {Switch phA DPC, Switch phB DPC, Switch phC DPC}
Set2: {Switch phA SPC, Switch phB SPC, Switch phC SPC}
Set3: {Switch phA pos. DPS, Switch phB pos. DPS, Switch phC pos. DPS}
Set4: {Switch phA pos. SPS, Switch phB pos. SPS, Switch phC pos. SPS}
If the "circuit-breaker type" is set to the "Single phase CircuitBreaker" value, then:
- in a set, if one datapoint is present for a phase, then the two others must be present as well.
- if the datapoint "Switchgear pos." is present, but none of the three datapoints "Switch PhA
pos", "Switch PhB pos", and "Switch PhC pos" then the SPS datapoint "Ph not together" is
mandatory.
If the "circuit-breaker type" is set to the "Triple phase CircuitBreaker" value, then no DPC
referencing a phase (phA, phB or phC) is allowed.
• A Circuit Breaker must be linked only once to a Synchrocheck function (relation "is
synchrocheck of").
• If a Circuit Breaker is linked to a Synchrocheck function (relation "is synchrocheck of"), then
its "Sync CB close" SPC datapoint must be present.
• "Sync CB close" datapoint of a "Circuit breaker" linked to a "Ext manual CS" or "Int
synchrocheck" synchrocheck must have its profile attribute “SBO mode” set to "Direct
• "Sync CB close" datapoint of a "Circuit breaker" linked to a "Ext auto CS" synchrocheck must
have its profile attribute “SBO mode” set to " SBO Operate Once”.
“Open” control sequence of synchronized circuit breakers
This sequence remains identical to the non-synchronized circuit-breaker (refer to section

"Defining a circuit-breaker" on page 770).
“Close” control sequence of synchronized circuit breakers
This sequence is different according to the configuration the synchrocheck type:

• External synchrocheck: the closure of the device is assumed by an external synchrocheck
module.
• Internal synchrocheck: the closure of the device is assumed by an internal synchrocheck
automation in the computer.
Close control sequence can be configured with:

• Manual set on of the external synchrocheck module or internal synchrocheck automation.
• Automatic set on of the external synchrocheck module or internal synchrocheck automation.
Furthermore, waiting closes the CB by the external module the initiator of the request can:
• Cancel the request.
• Close the device by forcing request.
784 C264/EN UM/E50.5

7.4.2.2 External synchrocheck behavior

This functionality is described in section "Circuit breakers with external synchrocheck" on page
240 of MiCOM C264 documentation.
7.4.2.3 Internal synchrocheck behavior

This functionality is described in section "Circuit breakers with internal synchrocheck" on page
249 of MiCOM C264 documentation.
7.4.2.4 Automation description of internal synchrocheck

For each parameter of the internal synchrocheck, its SCE identification is given by (param ),
referenced in "Automation description of internal synchrocheck" on page 785.
Principle
The synchrocheck function can work in the following schemes:
Operator Operator
Auto-
manual Synchrocheck
recloser
closure closure
Network locking on
X
both voltages X X
(param
presence and test of (param 20) (param 31)
26)
deltas
Network coupling on
both voltages X
presence and test of (param 19)
deltas
X
Presence of only the X X
(param
line voltage (param 22) (param 33)
28)
X
Presence of only the X X
(param
busbar voltage (param 21) (param 32)
27)
X
Absence of both X X
(param
voltages (param 23) (param 34)
29)
The authorized schemes are defined during the configuration phase. The operator synchrocheck
closure behavior is described in following sections.
Logic of authorization of interlocking
The absolute values of the two voltages (Vline and Vbusbar) must be above or below settable
thresholds, to permit the circuit breaker closing. The following voltage controls are available:
• Vline and Vbusbar for network coupling
• Vline and Vbusbar for network locking
• Vline and not(Vbusbar)
C264/EN UM/E50.5 785

• not(Vline) and Vbusbar
• not(Vline) and not(Vbusbar)
with Vline and Vbusbar TRUE if the measured voltage is above the threshold V> (param 15 and
param 17), and not(Vline) and not(Vbusbar) TRUE if the measured voltage is below the threshold
V< (param 16 and param 18). These threshold are given in % of the nominal voltage value,
updated at TMU200 board level (refer to section "Setting attributes of a TMU220 board" on page
580).
Schemes using Vline and not(Vbusbar) / not(Vline) and Vbusbar voltage controls
In case of the absence of one of the two voltages, at the end of a settable delay T2 (param 2), the
authorization of closing is given:
- Figure 484 - Vline and not(Vbusbar) voltage control
- Figure 485 - not(Vline) and Vbusbar voltage control
Schemes using not(Vline) or not(Vbusbar)voltage control
In case of the absence of both voltages, at the end of a settable delay T3 (param 1), the
authorization of closing is given:
- Figure 486 - Not(Vline) and not(Vbusbar) voltage control
Schemes using Vline and Vbusbar voltage control
Locking scheme
The closing authorization will be given if the following conditions are fulfilled:
786 C264/EN UM/E50.5

• Presence of both voltages, confirmed after a given delay (param 3) AND
seized threshold (Evect) (param 5) AND
• The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin (param 6) and
Fmax (param 7) are the extreme acceptable frequencies AND
• The difference between the two frequencies (DF) is lower than the seized threshold (Efreq)
(param 8) AND
• The phase difference between the two voltages (Dj) is lower than the seized threshold
(Ephase) (param 9)
These criteria must be still met before the time-out of a delay T1 started on the criteria
appearance else the synchrocheck function will not authorize the CB closing.
If during the delay time T1 one of these criteria is lost, T1 is reinitialized and is relaunched on
reappearance of all the criteria.
T1 depends on the way circuit breaker is controlled (manual closure, manual synchronized
closure, automatic with auto-recloser), given 3 parameters at SCE level: (param 25), (param 30),
(param 35).
- Figure 487 - Locking scheme
Coupling scheme
In the coupling scheme, the CB can be closed only when the Dj is equal to 0.
But, in order to authorize the closing, it is first necessary that the following conditions are fulfilled:
• Presence of both voltages AND
seized threshold (Evect) (param 10) AND
• The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin (param 11) and
Fmax (param 12) are the extreme acceptable frequencies AND
• The difference between the two frequencies (DF) is lower than the seized threshold (Efreq)
(param 13)
These criteria must be still met before the time-out of a delay T1 started on the criteria
appearance else the synchrocheck function will not authorize the CB closing.
C264/EN UM/E50.5 787

If during the delay time T1 one of these criteria is lost, T1 is reinitialized and is relaunched on
reappearance of all the criteria.
T1 depends on the way circuit breaker is controlled (manual closure, manual synchronized
closure, automatic with auto-recloser), given 3 parameters at SCE level: (param 25), (param 30),
(param 35).
- Figure 488 - Coupling scheme
Then, since a CB has a response time, it is necessary to wait a known Dj in order to anticipate the
response time and to close the breaker with a Dj equal to 0.
Therefore, the closing authorization will be sent when Dj = DF*360*Ta ± D(Dj) where Ta (param 4)
is the anticipation time or response time of the circuit breaker and D(Dj) (param 14) is the
acceptable mistake on Dj. There is a delay for such a coupling given in configuration (param 24).
7.4.2.5 Creating a synchrocheck function

Synchrocheck function can be created at several levels of the electrical topology:
• Substation level, in case of the synchrocheck function is shared by several breakers,
• Bay level, in case of the synchrocheck function dedicated to a breaker of the bay or shared by
two breakers in two different bays managed by the same computer.
The addition of a synchrocheck is done via the “Objects entry” window at substation or bay level
by clicking on mouse’s right button.
For more details about bay creation, refer to section "Defining a Bay" on page 758.
Several types of synchrochecks exist:

• External automatic synchrocheck
• External manual synchrocheck
• Internal automatic synchrocheck
• Internal manual synchrocheck
At substation level, only ‘external manual synchrocheck’ is available.
Only following typed bays allows synchrocheck creation:

• Busbar,
• Bus coupler,
• Bus section,
788 C264/EN UM/E50.5

• Feeder,
• Transformer,
• Generic bay.
- Figure 489 - Adding a synchrocheck at bay level (e.g. for feeder)
- Figure 490 - Adding a synchrocheck at substation level
Once added, synchrocheck general features must be set at SCE level:

• Fill the relation is synchrocheck of, giving which circuit-breaker module is concerned by the
function. For substation synchrocheck, several relations ‘is synchrocheck of’ can be added
and filled for all concerned breakers by the same synchrocheck. For bay synchrocheck, two
relations ‘is synchrocheck of’ can be filled for breakers of two different bays. Nevertheless,
these bays must be managed by the same computer, and the same synchrocheck
parameters will be used for the two breakers closure.
• short name and long name of the synchrocheck used for logging, alarms ...
• automatic out of service (No / Yes): defines if the synchrocheck is set off manually (No) or
automatically (Yes). When manually set off, an extra sequence is done by computer (see
previous sections). For automatic synchrocheck, this attribute is fixed to ‘Yes’.
• running time (range [0, 60s], step 1 s): this attribute appears in case of automatic out of
service. It corresponds to a latency time before setting out of service the synchrocheck after
successful or unsuccessful closure of the synchronized breaker.
C264/EN UM/E50.5 789

- Figure 491 - Setting synchrocheck general features (e.g. for external manual synchrocheck at
bay level)
In case of internal synchrocheck, extra configuration information must be set (see section Setting
default settings of internal synchrocheck).
When adding a synchrocheck, the following mandatory datapoints is automatically created at

function level and must be configured (see section "Defining datapoint" on page 689):
• Accept forcing: SPS datapoint, given the authorization to force synchrocheck. It is a system
datapoint: it cannot be wired and is managed by the computer running synchrocheck
sequence. Any automation or operator interface asking for a synchrocheck forcing, should be
client of this datapoint and test its status before forcing. So, proper IEC 61850 configuration is
done for all clients (computer, operator interface) for that feature.
- Figure 492 - Accept forcing mandatory datapoint for synchrocheck (e.g. for external manual
synchrocheck at bay level)
7.4.2.5.1 Setting default settings of internal synchrocheck

Default settings of internal synchrocheck are relevant to parameters of automation description
(see section "Automation description of internal synchrocheck" on page 785)
When adding an internal synchrocheck, the following specific attributes must be updated:
General attributes
• absence deltas test duration (ms)
• presence test duration (ms)
• presence deltas test duration (ms)
• close time of the Circuit Breaker (ms)
Acceptance Conditions
790 C264/EN UM/E50.5

• voltage delta threshold for locking (%)
• minimum frequency for locking (Hz)
• maximum frequency for locking (Hz)
• frequency delta threshold for locking (Hz)
• phase delta threshold for locking (°)
• voltage delta threshold for coupling (%)
• minimum frequency for coupling (Hz)
• maximum frequency for coupling (Hz)
• frequency delta threshold for coupling (Hz)
• phase delta threshold for coupling (°)
Voltage presence conditions

• line voltage over threshold (%)
• line voltage under threshold (%)
• bus voltage over threshold (%)
• bus voltage under threshold (%)
Used control schemes

• manual synchro close: coupling
• manual synchro close: locking
• manual synchro close: Line Dead and Bus Live
• manual synchro close: Line Live and Bus Dead
• manual synchro close: Line Dead and Bus Dead
• manual synchro close delay for coupling (s)
• manual synchro close delay (ms)
• manual close: locking
• manual close: Line Dead and Bus Live
• manual close: Line Live and Bus Dead
• manual close: Line Dead and Bus Dead
• manual close delay (ms)
• automatic close: locking
• automatic close: Line Dead and Bus Live
• automatic close: Line Live and Bus Dead
• automatic close: Line Dead and Bus Dead
• automatic close delay (ms)
C264/EN UM/E50.5 791

- Figure 493 - Setting 'default settings' attributes of an internal synchrocheck
When adding an internal synchrocheck, some mandatory system datapoints are automatically
created at function level and must be configured (see section ). They give information about
internal synchrocheck context (both voltage presences and absences) and statuses. They are
managed by the computer that runs the internal synchrocheck.
• Close order: transient SPS set as soon as a synchronized closure is in progress
• on/off SPS: see section Adding synchrocheck specific datapoints
• Possible closing SPS: in locking mode, all the conditions after delay are met to authorize
synchronized closure
• Ref. U absence SPS
• Ref. U presence SPS
• Voltage absence SPS
• Voltage presence SPS
792 C264/EN UM/E50.5

- Figure 494 - Internal synchrocheck mandatory datapoints
7.4.2.5.2 Adding synchrocheck specific datapoints

To assume previous described behavior of synchrocheck, when adding an auto-recloser, some
optional datapoints can be created at function level and must be configured (see section "Defining
datapoint" on page 689):
• on/off control DPC: to control in / out of service of the synchrocheck via DPC
• on/off control SPC: to control in / out of service of the synchrocheck via SPC
• on/off DPS (unauthorized on internal synchrocheck): giving in/out of service status of the
synchrocheck via DPS
• on/off SPS (mandatory on internal synchrocheck and implicitly created): giving in/out of
service status of the synchrocheck via SPS
Do not forget to define on/off SPS/DPS as feedback of on/off control SPC/DPC if they exist.
- Figure 495 - Synchrocheck optional datapoints
C264/EN UM/E50.5 793

• As shown in the following picture, under a Synchrocheck function, some datapoints are
mutually exclusive and some must be wired. Here, "wired" means that the datapoint must be
linked to a digital/analog channel of a computer, or linked to an IED address
• For an "Int synchrocheck" function, having its "automatic out of service" attribute set to the
"Yes" value, the "on/off ctrl DPC" or "on/off ctrl SPC" datapoint must be present.
• "on/off ctrl DPC" or "on/off ctrl SPC" datapoint of "Int synchrocheck" synchrocheck must have
its profile attribute “SBO mode” set to "Direct Execute" or “Direct Execute with SBO popup”
7.4.2.5.3 Management of the 5th VT on TMU220: Double Busbar

The fifth VT on TMU220 allows us to use 2 different busbar voltages for the synchrocheck control:
VBBARI and VBBARII.
- Figure 496 - Selecting between two busbars
794 C264/EN UM/E50.5

“Busbar V choice” is an optional SPS allowing the operator to chose between busbars’ voltages in
order to close the circuit breaker. This SPS can be directly acquired or generated by an
automation (PSL). According to its state, the selected busbar voltage is described in the following
table.
State of “Busbar V Selected

choice” Busbar
SET* VBBARII.
RESET* VBBARI
NOT CONFIGURED VBBARI
*Note that:
• SET stands for: Set or Forced Set or Substituted Set
• RESET stands for: Reset or Forced Reset or Substituted Reset
If the state of this SPS changes during a synchrocheck closure, the operation is aborted, a
negative acknowledgment (Hardware fault) is sent and the system is waiting a new order.
If the SPS is SELFCHECK FAULTY (or TOGGLING or UNKNOWN or SUPPRESSED), no

busbar voltage can be used (the automatic forcing can be used on this SPS to pre-defined a
behavior in case of invalid state)
The 5th voltage transformer is associated to a RMS measurement and can be used as the second
VTs. This new measurement is defined with the SCE with the TMU220 board.
The samples of the fifth transformer can be included into fast waveform records.
The RMS value of VBUSBARII can be included into a slow wave form record.
7.4.2.5.4 Voltage reference selection
- Figure 497 - Selecting reference voltage for synchronization
An optional SPS named “Synchro V choice” allows us, in combination with “Busbar V choice”
datapoint, to select the voltage reference between VBBARI, VBBARII and VLINE.
C264/EN UM/E50.5 795

SPS SPS
1st Voltage Second
Busbar V Synchro V
Reference Voltage
choice choice
NOT NOT
VLINE VBBARI
CONFIGURED CONFIGURED
NOT
SET* VLINE VBBARII
CONFIGURED
NOT
RESET* VLINE VBBARI
CONFIGURED
SET* SET* VBBARI VBBARII
RESET* RESET* VLINE VBBARI
SET* RESET* VLINE VBBARII
RESET* SET* VBBARII VBBARI
*Note that:
• SET stands for: Set or Forced Set or Substituted Set
• RESET stands for: Reset or Forced Reset or Substituted Reset
“Synchro V choice” is optional and has only sense in the case of a synchro-check CB built-in with
a TMU220 board and only if the optional SPS with “Busbar V choice” datapoint is also present.
No busbar voltage can be used for the synchro-check scheme if the SPS SynchroVchoice is
SELFCHECK FAULTY (or TOGGLING or UNKNOWN or SUPPRESSED). The operation is then
aborted and a negative acknowledgment (Hardware fault) is sent; after that, the system waits for a
new order.
Note: It is possible to use the automatic forcing on this SPS to pre-define a behavior in case of
invalid state.
The SCE generates a check error if the SPS SynchroVchoice is configured and the “reference
phase side” attribute is equal to “Phase A, B, C wired Busbar side”.
If the SCE user decides to generate the database despite the check error, the SCE will ignore the
real value of the attribute “reference phase side” and considered it as equal to “Phase A,B,C wired
line side”.
7.4.3 Defining an Auto-recloser built-in function

The addition of an auto-recloser is done via the “Objects entry” window at bay level by clicking on
mouse’s right button.
Only following typed bays allows auto-recloser creation:

• Busbar,
• Bus coupler,
• Bus section,
• Feeder,
796 C264/EN UM/E50.5

• Transformer,
• Generic bay.
- Figure 498 - Adding an auto-recloser at bay level
Once added, auto-recloser general features must be set at SCE level:

• Fill the relation ‘is auto-recloser of’, giving which circuit-breaker module is concerned by the
function.
• short name and long name of the auto-recloser used for logging, alarms ...
• functioning mode (1 ph trip) (Not used / 1P / 1P-3P / 1P-3P-3P / 1P-3P-3P-3P): useable

only for single phase circuit-breaker. Up to 4 cycles where the first one is single phase and the
others three phase.
• functioning mode (3 ph trip) (Not used / 3P / 3P-3P / 3P-3P-3P / 3P-3P-3P-3P): useable for
single and triple phase circuit-breaker. Up to 4 cycles where all are three phases.
• unlocking way (Not used / Reinitialization / Manual close / Both ways). For details refer to
previous description of ‘lock of auto-recloser’ in section "Auto-Recloser (AR)" on page 267.
C264/EN UM/E50.5 797

• Fast 3 P reclose enable (No, Yes): if a synchrocheck exists for the breaker, auto-recloser
can bypass it during the 3-phases first cycle if the attribute is set to ‘Yes’.
• 1st period monophased (range [100 ms, 5 s], step 10 ms): timer of the first single-phase
cycle.
• 1st period triphased (range [1 s, 60 s], step 10 ms): timer of the first 3-phases cycle.
• 2nd period triphased (range [1 s, 3600 s], step 1 s): timer of the second 3-phases cycle.
• 3rd period triphased (range [1 s, 3600 s], step 1 s): timer of the third 3-phases cycle.
• 4th period triphased (range [1 s, 3600 s] step 1 s): timer of the fourth 3-phases cycle.
• reclaim delay (range [1 s, 600 s], step 1 s): corresponds to ‘reclaimc recovering timer’
previously described in ‘launch recovering timer’ of section "Auto-Recloser (AR)" on page
267.
• unlock delay (range [1 s, 600 s], step 1 s): corresponds to ‘reclaimml recovering timer’
previously described in ‘lock of auto-recloser’ of section "Auto-Recloser (AR)" on page 267.
• manual close delay (range [1 s, 600 s], step 1 s): corresponds to ‘reclaimmc recovering
timer’ previously described in ‘lock of auto-recloser’ of section "Auto-Recloser (AR)" on page
267.
798 C264/EN UM/E50.5

- Figure 499 - (a) Setting auto-recloser features
C264/EN UM/E50.5 799

800 C264/EN UM/E50.5

- Figure 500 - (b) Setting auto-recloser features

• The two attributes "functioning mode (1 ph trip)" and "functioning mode (3 ph trip)" must not
be both set to "Not used" value
• If "functioning mode (1 ph trip)" value is set to "1P-3P-3P-3P", then the following rules must be
respected:
- "1st period monophased" < "2nd period triphased"
- "1st period monophased" < "3rd period triphased"
- "1st period monophased " < "4th period triphased"
• If "functioning mode (1 ph trip)" value is set to "1P-3P-3P", then the following rules must be
respected:
- "1st period monophased" < "3rd period triphased"
• If "functioning mode (1 ph trip)" value is set to "1P-3P", then the following rule must be
respected:
• If "functioning mode (3 ph trip)" value is set to "3P-3P-3P-3P", then the following rules must be
respected:
- "1st period triphased" < "2nd period triphased"
- "1st period triphased" < "3rd period triphased"
- "1st period triphased" < "4th period triphased"
• If "functioning mode (3 ph trip)" value is set to "3P-3P-3P", then the following rules must be
respected:
- "1st period triphased" < "3rd period triphased"
• If "functioning mode (3 ph trip)" value is set to "3P-3P", then the following rule must be
respected:
• If "functioning mode (1 ph trip)" value is different from "Not used", then the "circuit-breaker
type" must be set to "Single phase CircuitBreaker"
• If "functioning mode (3 ph trip)" value is set to "Not used", then the "circuit-breaker type" must
be set to "Single phase CircuitBreaker"
To assume previous described behavior, when adding an auto-recloser, some mandatory

datapoints are automatically created at function level and must be configured (see section
"Defining datapoint" on page 689):
• Autorecloser flt: is a MPS datapoint, given the failure reason of auto-recloser function. This
a system datapoint whose available states are:
State0: failure due to the synchrocheck
State1: failure to hardware, lock of device or another running automation linked to the
device
C264/EN UM/E50.5 801

State2: failure due to interlocking function
State3: no failure
• Auto-recloser st: is a MPS datapoint which gives the status of the auto-recloser function.
This is a system datapoint whose available states are:
State0: auto-recloser is in service, unlocked and no cycle is in progress
State1: auto-recloser is waiting CB opening
State2: the first single-phase cycle is in progress
State3: the first 3-phases cycle is in progress
State4: the second 3-phases cycle is in progress
State5: the third 3-phases cycle is in progress
State6: the fourth 3-phases cycle is in progress
State7: the auto-recloser is waiting CB closing
State8: the Reclaimc timer is launched
State9: auto-recloser locking due to a max number of reclosing cycles
State10: an auto-recloser locking
State11: the reclaimml timer is launched
State12: the reclaimmc timer is launched

• Force trip 3 P: is a SPC, used during a 3 phase cycle as mentioned in ‘Waiting CB
opening’ in section "Auto-Recloser (AR)" on page 267
• on/off: is a status DPS, corresponding to in / out of service status of the auto-recloser
• Trip 3 phases: is a SPS, giving information 3-phase trip provided by a relay
802 C264/EN UM/E50.5

- Figure 501 - (a) Auto-recloser mandatory datapoints
C264/EN UM/E50.5 803

- Figure 502 - (b) Auto-recloser mandatory datapoints
804 C264/EN UM/E50.5

To assume previous described behavior, when adding an auto-recloser, some optional datapoints
can be created at function level and must be configured (see section ):
• blocking SPS: corresponds to the ‘AR_BLOCKING’ BI described in section "Auto-Recloser
(AR)" on page 267
• lock/reinit: is a SPS used to lock / unlock the auto-recloser via SPS. Corresponds to the ‘AR_
LOCK’ signal described in section "Auto-Recloser (AR)" on page 267
• Trip PhA: is a SPS corresponding to trip status for pole A
• Trip PhB: is a SPS corresponding to trip status for pole B
• Trip PhC: is a SPS corresponding to trip status for pole C
• lock/reinit SPC: Signal to lock/unlock the auto-recloser via SPC. Corresponds to the ‘AR_
LOCK’ signal described in section "Auto-Recloser (AR)" on page 267
• on/off ctrl DPC: to control in/out of service of the auto-recloser via DPC
• on/off ctrl DPS: to control in/out of service of the auto-recloser via DPS
- Figure 503 - Auto-recloser optional datapoints

• If "functioning mode (1 ph trip)" value is different from "Not used", then at least one of the
three SPS datapoints { "Trip PhA", "Trip PhB", "Trip PhC" } is mandatory
• If "functioning mode (1 ph trip)" value is set to "Not used", then none of the three SPS
datapoints { "Trip PhA", "Trip PhB", "Trip PhC" } is allowed
• The two datapoints { "on/off ctrl DPC", "on/off ctrl DPS" } are mutually exclusive and, at least
one of them is mandatory
• The two datapoints { "lock/reinit SPC", "lock/reinit SPS" } are mutually exclusive. If the
"unlocking way" attribute value is set to "Reinitialization" or "Both ways" then, at least one of
the two datapoints is mandatory
To assume previous described behaviour, when adding an auto-recloser, some mandatory

datapoints are automatically created at circuit-breaker level and must be configured (see section
"Defining datapoint" on page 689):
• CB Healthy that corresponds to the ‘CB HEALTHY’ BI described in section "Auto-Recloser
(AR)" on page 267
C264/EN UM/E50.5 805

- Figure 504 - Available CB healthy pre-defined datapoints for circuit-breaker
7.4.4 Defining a Tap changer built-in function

7.4.4.1 Tap changer behavior
The control sequence of a transformer is described in "Control of transformers" on page 258 in
chapter Functional description (FT).
The control of a transformer is done via tap changer built-in function and can be performed in the
three modes “Direct Execute”, ”SBO once” and “SBO many mode” (refer to section "Overview of
control sequence processing" on page 699).
TCIP feature:
The TCIP input information is used to confirm the right execution of the low/raise execution. When
adding a TCIP at tap changer level, the two configurable delays must be set at TCIP datapoint
level for the correct TCIP management:
• reset confirmation delay (range [0 s, 120 s], step 100 ms]
• set confirmation delay (range [0 s, 120 s], step 100 ms]
• start confirmation delay (range [1 s, 60 s], step 100 ms): the TCIP information must appear
before the time-out of this delay
• stop confirmation delay (range [1 s, 60 s], step 100 ms): the TCIP information must
disappear before the time-out of this delay
- Figure 505 - Setting TCIP general attributes
TPI feature:
806 C264/EN UM/E50.5

Because the TCIP input information is not always configured, the tap control is performed by
using only the Tap Position Indication (TPI) value to verify the right execution of the request. The
TPI value must change in the given delay.
Control of a transformer with TCIP
This functionality is described in chapter "Control of transformers" on page 258 of Functional

description (FT).
Control of a transformer without TCIP

description (FT).
Suppression, Forcing or Substitution of the TPI

description (FT).
7.4.4.2 Creating a tap changer built-in function

Tap changer is considered as a function because it verifies maximal and minimal useable
positions of tap position indicator. It is like a sub-module of transformer module and owns the tap
position indicator and optional controls (Raise/Lower, Goto Min/Max).
To create a tap-changer built-in function, add it from object entry available at transformer module
level (1).
- Figure 506 - Adding a tap-changer built-in

function to transformer
When adding a tap changer function, the following general attributes must be updated:
• short name and long name of the tap changer used for logging, alarms ...
• minimal usable position (range [1, 64], step 1).
• maximal usable position (range [1, 64], step 1): must be greater than previous attribute.
• execution timeout (range [0, 60 s], step 100 ms): It is the maximum delay in which tap position
must have changed relatively to the current tap control in progress. If delay expired bad
acknowledgment is sent for tap control.
C264/EN UM/E50.5 807

- Figure 507 - Setting tap-changer attributes
When adding a tap changer function, the mandatory datapoint ‘Tap position indicator’ (TPI) is
automatically created at function level (8).
The following table gives inputs and outputs tap changer’s features controlled by the computer.
For each datapoint its SCE identification is given by a number, referenced in the following figure.
To configure correctly the tap changer of a transformer module:

• add the relevant datapoints, relatively to the following tables,
• configure them (see section "Creating a datapoint" on page 689).
Tap changer for transformer

OUTPUTS INPUTS
(8) TPI value
DEVICE (2) DPC raise/lower
CONTROL (7) SPS (optional) tap change in
(1) DPC (optional) goto min/max
progress
DEVICE
(4) SPC (optional) transformer (I) SPS (optional) selection position
SELECTION
selection information
(HARDWARE)
(I) This SPS is a generic one added at transformer module level and configured as feedback of
SPC transformer selection (4).
1. Goto min/max DPC: this datapoint is not managed by the tap changer built-in function. If it is
needed an ISaGRAF® automation has to be used.
2. Raise/lower DPC: this datapoint is managed by the tap changer built-in function.
3. MCB open SPC: this datapoint is managed by the tap changer built-in function.
4. TAP Select SPC: this datapoint is managed by the tap changer built-in function
5. Higher position: this SPS is not considered by the tap changer built-in function. If it is needed
an ISaGRAF® automation has to be used.
6. Lower position: this SPS is not considered by the tap changer built-in function. If it is needed
an ISaGRAF® automation has to be used.
7. Tap in progress: this SPS is considered by the tap changer built-in function.
808 C264/EN UM/E50.5

- Figure 508 - Available pre-defined datapoint for

tap-changer

• "Raise/lower DPC" datapoint must have its profile attribute “SBO mode” set to "SBO Operate
Many"
7.4.5 Defining an automatic voltage regulation–AVR built-in function

7.4.5.1 Creating an AVR function
AVR relates to the transformer bays; hence the configuration is done at this level. The topology is
defined by the node references of each individual transformer. Transformers in parallel are
located in separate bays; among them, one is master, the other followers. Several independent
groups can be configured in the same substation.
In the “Objects entry” window, select the AVR built-in function and right click on Add. This permits
creation of datapoints related to the AVR real-time information & controls of the transformer bay.
List of attributes (* means that it can be modified through operator controls, ** through setpoints):
C264/EN UM/E50.5 809

Tab Parameter name Values Min Max Step Default

AVR state* ON/OFF - - - ON
AVR mode* Manual / Automatic - - - Automatic
Transformer
20000.0 V
nominal voltage
Nominal voltage 100 V
Nominal current 1A
PhAse voltage / Phase
AVR Type of regulation - - -
Compound voltage voltage
Manual controls No/Only on AVR
No
allowed locked/Always
Automatic move to
No/ Yes (immed.)/ Yes
manual mode on - No
after delay
errors
Manual mode on
60 s
errors
810 C264/EN UM/E50.5


Target voltage Controls/Remote-
- - - Controls
management Local/Period dep
Target voltage
No/1/2/3/4/5 1
active
No target voltage
10 300 10 120
active delay
Remote target 0,2
In % of Vn 90% 105% 90%
voltage min value 5%
Remote target 0,2
In % of Vn 95% 110% 110%
voltage max value 5%
Remote target
maximum difference
In Volt (MV range value) 50V 500V 10V 200V
between 2 target
voltages
Target End of remote target 480m

0mn 10mn 60mn
Voltage voltage delay n
End of local target
3mn 10mn 1mn 5mn
voltage delay
Displayed in volt but
Target voltage 1 88% 112% 0.1% 100%
used as % Vn
Displayed in volt but 10
Target voltage 2 104% 0.1% 102%
used as % Vn 0%
used as % Vn 3%
used as % Vn 6%
Displayed in volt but
Target voltage 5 93% 97% 0.1% 95%
used as % Vn
Local Target Displayed in volt but 0.2
90% 110% 100%
Voltage used as % Vn 5%
C264/EN UM/E50.5 811


Voltage
0 10 0.1 0.5
confirmation delay
Double wound Yes/no - - - No
Double wound Voltage 1 / voltage 2 /
Voltage 1
voltage average
Double wound
% of Vn 0% 10% 1% 5%
voltage difference
Voltage presence Displayed in volt but
20% 80% 10% 50%
threshold used as % Vn
Regulation
% of Vc 0% 4% 0.2 1.25%
deadband
5%
Abnormal voltage
% of Vc 2% 11% 1% 5%
(threshold)
Abnormal voltage
20s 600s 10s 300s
delay present
Abnormal voltage
0s
delay missing
Voltage Voltage present

Tp 0s 120s 1s 0s
delay
Voltage missing
Ta 30s 180s 10s 120s
delay
Compounding
Active/ Inactive - - - Inactive
activation*
Compounding
Active / Reactive - - - Active
method
Active compounding
% of Vn/In 0% 20% 0.5% 0%
method par. A1**
Active compounding
% of Vn/In 0% 20% 0.5% 0%
method par. B1**
Reactive
compounding
% of Vn/In 0% 20% 0.5% 0%
method
p A2**
Reactive
compounding
% of Vn/In 0% 20% 0.5% 0%
method
p B2**
812 C264/EN UM/E50.5


Compound nominal
0 0.01 0.1
current
Voltage correction 0 0.01 0%
Double A1 No/yes - - - No
Double B1 No/yes - - - No
Double A2 No/yes - - - No
Double B2 No/yes - - - No
C264/EN UM/E50.5 813


Tap changer fault
Internal and/or external - - - Internal only
function
Tap changer fault Autom/manual reset/
- - - Automatic
behavior manual mode
Highest tap value 1 64 1 39
Lowest tap value 1 64 1 1
Intermediate
No/yes - - - No
position
Intermediate
Off/on Off
position active
Intermediate tap
0s 60s 1s 10s
delay
Intermediate tap 1 64 1 1
First tap delay T1 10s 70s 5s 60s
Next tap delay T2 2s 30s 2s 10s
End Tap delay 0s 180s 5s 60s
TAP
First tap delay
Tb 20s 120s 10s 30s
bypass delay
Preset tap 1 39 1 1
Preset tap delay 0s 10s 1s 1s
TCIP time out delay 5s 180s 5s 10s
TCIP End time out
1s 120s 1s 10s
delay
Tap Changer Fault
60s 600s 10s 120s
delay
Number of taps
1 10 1 4
before highest tap
Number of taps
1 10 1 4
before lowest tap
Slipping period for
Period in days 1 120 1 30
counting
Runaway tap delay 0s 60s 1s 30s
814 C264/EN UM/E50.5


Tap changer set Lower and/or raise Only lower
Voltage loss on defined tap/lock
defined tap
position tap automatic reg
Tap changer
Preset/current/lowest Preset
position behavior
Primary CB state Open/close Open
Overcurrent/overvol
Signalization / Signal. & Signalizatio
tage/
locking n
undervoltage
Tap changer
position on voltage
Off/on - - - Off
loss function
activation*
Fast tap changer
move after voltage
Off/on - - - Off
loss function
activation*
Overcurrent
Automati Off/on - - - Off
detection activation*
on
Overcurrent
% of In 50% 500% 10% 250%
threshold
Overcurrent delay 0s 30s 0.1s 2s
Overvoltage
Off/on - - - Off
Overvoltage 10
% of Vn 130% 1% 130%
threshold 0%
Overvoltage delay 0s 30s 0.1s 2s
Undervoltage
Off/on - - - Off
Undervoltage
% of Vn 50% 100% 1% 70%
threshold
Undervoltage delay 0s 30s 0.1s 2s
Tap Changer
Off/on - - - Off
blocking activation *
Tap Changer
0s 300s 10s 60s
blocking delay
C264/EN UM/E50.5 815


Transformer in
Yes/No - - - No
parallel
Master/Followe/Foll
Role
master backup
Initial state Off/on Off
TR in // Master failure Follow bec master Folbecmast
- - -
management /Standalone reg er
Neg
Used parallel Master/Foll
reactancecomp/Min.cir. - - -
method ow
current
Backup mode delay 0s 120s 1s 60s
RPF used Yes/No - - - No
Primary voltage
In kV 0 kV 400 k 1 kV 63 kV
used
RPF current
in % of In 0% 20% 1% 5%
threshold
RPF detection delay Tconfirm in seconds 0s 30s 1s 5s
RPF management Ignore/block operat/reg. Blockoperat
- - -
mode reversely on
RPF target voltage in % of primary Vn 88% 120% 0.1% 100%
RPF RPF deadband in % of primary Vn 0.5 4.0 0.25 2.0

RPF first tap delay 10s 70s 5s 60s
RPF next tap delay 2s 30s 2s 10s
No
RPF compound
compounding/Active/Re - - - No compdg
method
active
RPF compound A1 0 20 5 0
RPF compound B1 0 20 5 0
RPF compound A2 0 20 5 0
RPF compound B2 in % of primary Vn/In 0 20 5 0
To define the transformer, refer to section "Defining a transformer" on page 778.
To associate the AVR to a Tap changer:

• double click the link ‘Associated with’; this opens the Relation link editor
• select the desired path in the list beneath
• click OK
816 C264/EN UM/E50.5

To assign an IEC address to each datapoint, launch “data model and data flow update” SCE
function.
In the MiCOM C264 that manages the bay where the AVR built-in function is created, set that an
AVR panel must be present.
The Period binder includes four bricks. Each includes a timetable H1 thru H24 (Hour tab) and a
definition of the days where this timetable applies (third tab):
• Holidays target: days off round the year
• WE#1 target: first day in the week-end
• WE#2 target: second day in the week-end (it must follow the preceding day in order)
• Week target: regular days
Example: define the target voltage number according to the schedule that follows:
C264/EN UM/E50.5 817

Holidays definition is set in configuration, with a maximum of 10 days with a fixed date (ex: 14/07).
If the current day is defined as a holiday, the target voltage values used are the ones defined for
holiday.
Special days definition is set in configuration, with a maximum of 10 days with a fixed date (ex:
11/01). If the current day is defined as a special day, the target voltage values used are the ones
defined for the weekdays (even if the day is a week end day 1 or 2, or a holiday).
818 C264/EN UM/E50.5

Week days definition is set in configuration.
7.4.5.2 AVR behaviour

The AVR built-in function is described in "Built-in Automation functions" on page 267 of chapter
Functional description (FT).
7.4.6 Defining an automatic voltage regulation–ATCC built-in function

7.4.6.1 ATCC behavior
The ATCC built-in function is described in chapter "Automatic voltage regulation–ATCC" on page
294 of Functional description (FT).
7.4.6.2 Creating an ATCC function

ATCC is a complex built-in function for it concerns specific objects (transformer, busbar, voltage
level) constituting the substation. At SCE level, ATCC modeling is split into different objects
(ATCC function needs) located under each electrical component relevant to it. The set of these
objects corresponds to the parametrization of ATCC substation built-in function.
C264/EN UM/E50.5 819

Adding ‘ATCC function needs’ object under electrical component permits automatic datapoint
creation. These datapoints relate to the ATCC real-time information and controls relevant to this
electrical component.
Voltage levels managed by ATCC do not need specific datapoints for the ATCC function. So,
specific attributes put at voltage level objects are preferred to give extra ATCC function needs for
each voltage level.
In the following sub-sections, required datapoints for ATCC function are prefixed with an identifier,
referred in chapter Functional description (FT) of MiCOM C264.

• If there is NO ATCC under the Substation, then:
• a "Voltage level" must have its "ATCC existence" attribute set to "No".
• the "ATCC fct needs" is allowed neither under a "transformer" nor under a "BusBar".
• If there is an "ATCC fct needs" under a "transformer", then:
• the "Tap changer" with its "Raise/lower DPC" datapoint are mandatory.
• one of the two datapoints { "MCB position DPS", "MCB position SPS" } is mandatory. They
are mutually exclusive
• the "transformer" must be linked to a Voltage level through one and only one of the relations {
"has its primary on", "has its secondary on" }. The Voltage level must be different from the one
under which the transformer is located.
7.4.6.2.1 Defining ATCC function at substation level

The entry point of ATCC configuration is done at substation level.
This is done via the “Objects entry” window at substation level by clicking on mouse’s right button.
- Figure 509 - Adding an ATCC function at substation level
Once added, ATCC features must be set at SCE level:

• Fill the relation ‘is managed by’, giving which computer runs and supervises ATCC function at
substation level.
• short name and long name of the ATCC used for logging, alarms ...
‘General’ attributes:
‘calculation’ attributes
• calculation period
• calculation mode
820 C264/EN UM/E50.5

‘Homing’ attributes
• active homing
• homing deadband
‘ATCC mode changing’ attributes

• mode on group interconnection
• mode on bay in local
‘Compounding’ attributes
• compounding method
Delays’ attributes:
‘Nominal’ attributes
• fixed initial tap delay (no means inverse delay).
• initial tap delay (in ms)
• inter tap delay (in ms).
‘Homing’ attributes
• homing initial tap delay (in ms)
• homing inter tap delay (in ms)
‘Hunting’ attributes
• hunting window (in ms)
• opposite max tap changes (default value: 4 )”
‘Inhibition’ attributes
‘Inhibition conditions’ attributes

• max voltage difference (ratio) (default value: +2%)
• tolerable nominal under voltage (ratio) (default value: 80%)
• tolerable nominal over voltage (ratio) (default value: 120%).
‘Busbar voltage’ attributes
Coefficients for busbar voltage calculation attributes

• voltage coefficient for 1 transfo
• voltage coefficient for 2 transfos
C264/EN UM/E50.5 821

- Figure 510 - Setting general attributes of an ATCC
- Figure 511 - Setting 'delays' attributes of an ATCC
822 C264/EN UM/E50.5

- Figure 512 - Setting 'inhibition' attributes of an ATCC
- Figure 513 - Setting busbar voltage attributes of an ATCC
When adding an ATCC to a substation, the following mandatory datapoints are automatically
created and must be configured (see section ):
(DPT_Sub 1) ATCC clear alarm SPC
(DPT_Sub 2) ATCC on/off control SPC
(DPT_Sub 3) AVR defect alarm SPS
(DPT_Sub 4) DBI override SPS
(DPT_Sub 5) ErrorLog SPS
(DPT_Sub 6) On/off SPS
(DPT_Sub 7) Target unreached SPS
- Figure 514 - Mandatory datapoints for ATCC at substation level
C264/EN UM/E50.5 823

7.4.6.2.2 Defining ATCC function needs at voltage level

For each voltage level containing a transformer concerned by an ATCC function, extra ATCC
configuration must be done.
This is done under SCE at voltage level, by setting the attribute ‘ATCC existence’ to ‘Yes’ (1).
Then an extra ‘ATCC’ tab appears with the following attributes to update:
‘voltage targets’ attributes

• voltage target by default.
• voltage target 1
‘regulation’ attributes
• voltage target ramping rate (kV/mn)
• max tap change rate (kV/min)
• voltage deadband to end tapping
• voltage deadband to initiate tapping
When a voltage level is concerned by an AVR function, do not forget to set correctly its attribute
‘nominal value (kV)’ (refer to section "Defining a Voltage level" on page 757). It is used for
transformer nominal ratio computation.
824 C264/EN UM/E50.5

- Figure 515 - Setting ATCC function at voltage level
7.4.6.2.3 Defining ATCC function needs at busbar level

For each busbar bay concerned by an ATCC function, extra ATCC configuration must be done.
For details about busbar bay creation, refer to section "Defining a Bay" on page 758.
This is done via the “Objects entry” window at busbar level by clicking on mouse’s right button.
- Figure 516 - Adding ATCC function needs at busbar level
Once added, ATCC busbar features must be set at SCE level:
C264/EN UM/E50.5 825

• setpoint ponderation
• priority
‘line drop compensation (if setpoint adjustment)’ attributes

• resistive coefficient
• reactive coefficient
‘line drop compensation (if voltage adjustment)’ attributes

• transfo-busbar resistive coefficient
• transfo-busbar reactive coefficient
- Figure 517 - Setting general busbar features of an ATCC
When adding an ATCC function needs at busbar level, the following mandatory datapoints are
automatically created and must be configured (see section "Defining datapoint" on page 689):
(DPT_Bb 1) ATCC inhibited
(DPT_Bb 2) ATCC inv module
(DPT_Bb 3) ATCC inv voltage
(DPT_Bb 4) ATCC max transfo
(DPT_Bb 5) ATCC on/off
(DPT_Bb 6) ATCC on/off ctrl
(DPT_Bb 7) ATCC targ 1 ctrl
(DPT_Bb 12) ATCC target 1
826 C264/EN UM/E50.5

(DPT_Bb 17) ATCC to target
(DPT_Bb 18) BusBar voltage
- Figure 518 - Mandatory datapoints for AVR at busbar level
7.4.6.2.4 Defining ATCC function needs at transformer level

For details about transformer bay (and subsequent transformer module) creation, refer to
sections "Defining a Bay" on page 758.
For each transformer concerned by an ATCC function, extra ATCC configuration must be done at
several levels:
• Set properly the following features for transformer module:
‘Transformer type’ attribute
‘Power value’ attribute: (range [1, 300 MVA]).
‘Impedance’ attribute, whose unit is a percent of value for S=100 MVA (range [0,01 to
24,99 by step 0,01):
MCB position SPS or DPS is mandatory (refer to "Defining a transformer" on page 778).
• Add and configure a Tap-changer built-in function for the transformer module (refer to section
"Defining a Tap changer built-in function" on page 806), with the following features:
C264/EN UM/E50.5 827

Raise/Lower DPC is mandatory
Tap in progress SPS is mandatory
MCB open SPC is mandatory

• Add and configure an ‘ATCC fct needs’ object for transformer, via the “Objects entry” window
at transformer module level by clicking on mouse’s right button (1):
- Figure 519 - Adding ATCC function needs at transformer level
Once added, the features of ‘ATCC function needs for transformer’ must be set at SCE level:
‘Tpi range’ attributes

• up range
• down range
‘Inhibition conditions’ attributes:

• Overcurrent ratio
- Figure 520 - Setting general transformer features of an ATCC
When adding ATCC function needs at transformer level, the following mandatory datapoints are
automatically created and must be configured (see section "Defining datapoint" on page 689):
(DPT_Trf 1) ATCC on/off
(DPT_Trf 2) ATCC homing
(DPT_Trf 3) ATCC hunting
828 C264/EN UM/E50.5

(DPT_Trf 4) TAP bad TCIP
(DPT_Trf 5) TAP long TCIP
(DPT_Trf 6) TAP invalid
(DPT_Trf 7) Run away
(DPT_Trf 8) ATCC disc eqpt
(DPT_Trf 9) ATCC local bay
(DPT_Trf 10) MCB trip
(DPT_Trf 11) ATCC overcurrent
(DPT_Trf 12) ATCC overvoltage
(DPT_Trf 13) ATCC low-voltage
(DPT_Trf 14) ATCC inv voltage
(DPT_Trf 15) Second. voltage
(DPT_Trf 16) Second. current
(DPT_Trf 17) Second. active P
(DPT_Trf 18) Second. react. Q
C264/EN UM/E50.5 829

- Figure 521 - Mandatory datapoints for ATCC at transformer level
7.4.6.2.5 Defining an electrical topology for ATCC function

For correct behavior of ATCC function, electrical topology of the LV side, including connection of
the transformer to the busbar and coupling of busbars into the LV level must be defined.
Any electrical topology can be defined by modules interconnected by nodes.
A node is in relation with at least on module. The most common “node” is busbars.
Electric modules are mostly dipoles. Switchgears and circuit-breakers are connected to two
nodes. Special module cases are:
• motor/generator that are connected to only one node,
• line arrival that is a node,
• special (german) double switch, in fact association of earth switch and disconnector,
• transformer connected to 3 nodes but the third node is reserved to neutral compensation.
830 C264/EN UM/E50.5

At SCE level, nodes are special attributes of module, whose values are given by integers. Each
identified node in the electrical topology has a unique arbitrary value. Two interconnected
modules share the same node value. The best practice to value nodes is to do it directly from the
substation electrical diagram.
- Figure 522 - Identifying nodes in electrical diagram
This manual approach of nodes identification must be projected at SCE electrical object level:
• “Busbar” bay, where one node reference must be filled (1),
• “External line” module of “Feeder” bay, where one node reference must be filled (2),
• “Circuit-breaker” and “Switchgear” module, where two node references must be filled (3),
C264/EN UM/E50.5 831

• “Transformer” module, where at least two node references must be filled, and a extra one in
case of neutral compensation (4),
• “Capacitor” & “inductor” module, used for neutral compensation, where one node reference
must be filled (5); it corresponds to the neutral node of the associated transformer.
- Figure 523 - Setting busbar node reference (ATCC function)
- Figure 524 - Setting external line node reference (ATCC function)
- Figure 525 - Setting circuit breakernode reference (ATCC function)
832 C264/EN UM/E50.5

- Figure 526 - Setting transformer node reference (ATCC function)
- Figure 527 - Setting capacitor node reference (ATCC function)
7.4.7 Defining an electrical regulation by user function

EPAS allows the user to configure specific control sequences or automations (e.g. switching
sequences, busbar transfer, load shedding, GIS-pressure supervision, etc …) during the
configuration phase.
To do that, there are two main solutions:

• Using ISaGRAF® workbench for slow automations, where the execution of the automation is
cyclic, based on a cycle that cannot be less than 50 ms.
• Using extended logical function modeling (boolean, timer, bistable functions) via FBD
workbench, where the execution is event-driven.
User function can be put at any level of the electrical topology except Site. Moreover, slow
automation is unavailable at module level. User function must always specify on which computer
it runs.
Extra solutions for simpler needs exist at configuration level (they could be seen as restriction of
particular FBD functions):
• Group modeling: SPS production based on a pre-defined boolean function working on a set of
datapoint.
• xPS-xPC association: on a particular state of xPS, ability to control a given xPC.
• SPS-DPS association: DPS production based on the synthesis of 2 SPSs.
C264/EN UM/E50.5 833

• Interlocking definition: production of virtual SPS datapoints used to control opening and/or
closure of modules. These virtual datapoints are defined through specific FBD logical
diagrams where inputs are generally breaker and switch positions.
• Automatic/manual dependency set at control level (SPC, DPC or SetPoint): when a control is
linked to a SPS or DPS via the automatic/manual dependency, control is refused if the SPS
(resp. DPS) is in the SET (resp. CLOSED) state.
7.4.7.1 Defining an FBD fast automation
CAUTION
UNEXPECTED PSL EXECUTION OF CONTROL
Carefully evaluate the impact of FBD automation before usage.
To define an FBD fast automation, the three following steps must be done:
• FBD interface definition at SCE level:
FBD function ‘header’ creation.
creation of input plugs, that will be linked to SPS, DPS, MV, MPS, SPC or DPC (fast
automations take into account the logical value of these datapoints, defined for
interlocking management), added as sub-objects to this header.
creation of output plugs, that will be linked to SPC, DPC (control of relays) or to a SPS
(production of SPS real-time value), added as sub-objects to this header.
• FBD body (coding in PSL) definition via launching at SCE level the FBD editor (contextual
menu on the FBD interface object) and doing diagram edition of boolean, timer and bistable
functions, and links to input/output plugs.
• Effective linking of input and output plugs to existing datapoints
7.4.7.1.1 Creating an FBD fast automation (header definition)

The addition of a FBD fast automation is done via the “Objects entry” window at any level of the
electrical topology (except Site) by clicking on mouse’s right button.
For more details about electrical topology creation, refer to section "Defining an electrical
topology" on page 751.
834 C264/EN UM/E50.5

- Figure 528 - Adding a FBD fast automation (E. G.

for feeder bay level)
Once added, FBD fast automation features has to be set at SCE level:
• Edit the relation ‘runs on’, giving which BCPU PLC will manage the automation. This relation
is automatically filled by SCE if FBD automation is located under a bay whose BCPU
manager has ever been entered (inheritance mechanism, for details about computer
manager of a bay refer to section "Defining a Bay" on page 758)
• Type the short name and long name of the fast automation used for internal SCE
identification.
- Figure 529 - Setting FBD fast automation

features
7.4.7.1.2 Creating FBD input plug (header definition)

The addition of an FBD input plug is done via the “Objects entry” window at the FBD automation
C264/EN UM/E50.5 835

- Figure 530 - Adding a FBD input plug
Once added, FBD input plug features must be set at SCE level:
• short name and long name of the fast automation used for identification in FBD editor
- Figure 531 - Setting general FBD input attributes
7.4.7.1.3 Creating FBD output plug (header definition)

The addition of a FBD output plug is done via the “Objects entry” window at the FBD automation
- Figure 532 - Adding a FBD output plug
Once added, FBD output plug features has to be set at SCE level:
• short name and long name: used for identification in FDB editor
836 C264/EN UM/E50.5

- Figure 533 - Setting FBD output plug attributes
7.4.7.1.4 Using FBD editor (body definition)

The launching of the FBD editor is done at FBD automation level via its contextual menu (right
click).
- Figure 534 - Launching FBD editor
Once launched, FBD editor allows diagram edition of the automation. For details about FBD user
manual refer to the SCE Documentation.
- Figure 535 - Using FBD editor
1. FBD Boolean is Boolean type (True / false) input.
2. FBD Input is an input to FBD (Type – SPS, DPS etc.)
3. And Gate
4. TON Ton delay timer
5. FBD Output is output of FBD ( type SPS, SPC etc)
C264/EN UM/E50.5 837

7.4.7.1.5 Linking datapoints to FBD inputs and outputs

To assign a datapoint to a FBD input:
• Add the relation ‘uses <XXX>’ (1) at FBD input level, where XXX corresponds to the datapoint
kind (SPS, DPS, MPS, MV, SPC or DPC)
• Fill the relation with the relevant datapoint
- Figure 536 - Linking a FBD input to a datapoint
To assign a datapoint to a FBD output:

• Add the relation ‘controls <XXX>’ (1) or ‘produces SPS’ at FBD input level, where XXX
corresponds to the control datapoint kind (SPC or DPC)
• Fill the relation with the relevant datapoint
- Figure 537 - Linking a FBD output to a datapoint
Several datapoints can be assigned to the same FBD output.

• For one "FBD input" plug, only one relation is allowed.
• For one "FBD output" plug:
the count of relations towards DPC or SPC datapoints have to be ≤ 4
the count of relations towards SPS datapoints have to be be ≤ 4

• A "DPC" or "SPC" datapoint can be linked to an Output plug of a FBD Automation through the
relation "controls DPC" or "controls SPC". These relations are not compatible with the
following ones:
relations defining the Control Source, except the "…wired on" relation(s)
relation "has for IEC address" whatever the link type
838 C264/EN UM/E50.5

relation "has for SCADA address".
relation "is controlled on state change of".
relation "has for AutoManu dependency".
relation "has for feedback".
relation "has for local/remote dependency".

• A "DPC" or "SPC" datapoint can be linked to an Input plug of an FBD Automation through the
relation "uses DPC" or "uses SPC". These relations are not compatible with the following
ones:
relations defining the Control Source: "…wired on"
relation defining the Control Source: "has for IED address"
7.4.7.1.6 Creating FBD timer plugs

The FBD is associated to a computer PLC (Programmable logic controller).
The FBD timer plugs are used to enable/disable the TON/TOFF block output:
• the FBD timers and FBD accuracy timers are used only for TON or TOFF logics
• the FBD accuracy timers are used only for TON_A or TOFF_A logics
For TON, TOFF, TON_A and TOFF_A, the FBD timers and FBD accuracy timers are like an FBD
input on PT point.
In the FBD settings part, it is possible to define up to 100 FBD timers or FBD accuracy timers.
Add the object from the Objects entry window:
- Figure 538 - Creating FBD timer plugs
A new binder Settings holds the timer plugs. Set attributes of each plugs:
- Figure 539 - Set attributes of FBD timer plugs
C264/EN UM/E50.5 839

• Editable in MiCOM S1 - PACiS: “Visible and editable”, if it is possible to update value of FBD
timer (FBD accuracy timer) with MiCOM S1 - PACiS
• default value: that is the value till it is not modified with MiCOM S1 - PACiS
• minimal and maximal values, range is:
• 5 thru 50ms for an accurate timer
• 50ms thru 1h for a standard timer
• step, that is the resolution and accuracy; minimum value is:
• 1ms for an accurate timer
• 5ms for a standard timer
The MiCOM S1 - PACiS sends a file .VAL to MiCOM C264, which contains the new values of FBD
timer (FBD accuracy timer). This is considered by BCPU runtime dynamically.
Case of MV timer is used for FBD timer (FBD accuracy timer)
The modification of the FBD timers can be performed using an Integer MV as feedback of an
Integer Setpoint:
• the Setpoint is mandatory, shall be “system” and can only be used through IEC 61850
protocol
• the MV shall be “system” and can only be modified using the associated Setpoint
• the associated FBD Timer shall not be editable in MiCOM S1 - PACiS
Creates Setpoint and MV feedback, and add a new entry for FBD timer (FBD accuracy timer)
“uses MV: MV datapoint”:
- Figure 540 - Using an integer MV as feedback of

an integer SetPoint
The Setpoint timer needs to be configured with:

• “minimum value” and “maximum value” according with “minimal value” and “maximal value”
set for FBD timer (FBD accuracy timer)
840 C264/EN UM/E50.5

- Figure 541 - Configuring "minimum & maximum

values" of SetPoint timer
If incorrect entries the SCE logs the discrepancy and the values are corrected by BCPU.
The MV timer needs to be configured with:

• “minimum value” and “maximum value” according with “minimal value” and “maximal value”
set for FBD timer (FBD accuracy timer)
- Figure 542 - Configuring "minimum & maximum

values" of MV timer
If incorrect entries the SCE logs the discrepancy and the values are corrected by BCPU.
• “Value type” set to “Integer (INS)”
- Figure 543 - Configuring "value type" of MV timer
If incorrect entries the SCE logs the discrepancy (be careful: Value type = Integer measure (MVi)
is not implemented on BCPU).
• “saved in flash” attribute set to “Yes”
C264/EN UM/E50.5 841

- Figure 544 - Configuring "saved in flash" of MV

timer
If incorrect entries the SCE logs the discrepancy and the values are corrected.
• the “step” attribute is not known by the runtime. The runtime considers a fixed value for the
step, in function of the received value of the MV timer:
step=1ms, if value <=50ms (FBD accuracy timer)
step=5ms, if value > 50ms (FBD timer)
The value will be rounded down.
The FBD timer needs to be configured with:

• “Editable in MiCOM S1 - PACiS” set to “No visible”, to avoid access competition on the value
of the FBD timer (FBD accuracy timer)
- Figure 545 - Configuring "editable in

MiCOM S1 - PACiS" of FBD timer
If incorrect entries the SCE logs the discrepancy and the value is corrected by SCE generation.
The FBD timer (FBD accuracy timer) value and MV value are set to last value save at each BCPU
restart.
At first reboot with a new database, the FBD timer (FBD accuracy timer) and MV timer used are
set to “Default value” attribute configured for FBD timer (FBD accuracy timer) and the MV timer
quality have to be set to valid.
842 C264/EN UM/E50.5

7.4.7.2 Defining an ISaGRAF® slow automation
CAUTION
UNEXPECTED ISAGRAF® EXECUTION OF CONTROL
Carefully evaluate the impact of ISaGRAF® automation before usage.
The core of the slow automation modeling is a ‘Slow automation’ object that corresponds to an
ISaGRAF® project. Slow automation can own datapoints for status, control of automation itself
(automation management); for instance, a load shedding automation can have a control to put it
in/out of service and a relevant status.
They also reference via links datapoints located in system or electrical topologies. There are two
kinds of link:
• ‘client’ link, that means that the slow automation uses the datapoint that is acquired or
managed outside the ISaGRAF® automation. For instance, the load shedding automation
can be client of some ‘circuit-breaker status’ input datapoints and some ‘circuit-breaker
control’ output datapoints.
• ‘server’ link, that means that the slow automation produces or manages the datapoint. For
instance, a slow automation can be used to produce the sum of feeder measurements. This
sum is also a measurement located at voltage level for instance.
To define a slow automation, do the steps that follow:

• define the slow automation interface:
create the slow automation ‘header’
if required, create the datapoints at slow automation level, used for the function
management
create the client links for the slow automation
create the server links for the slow automation

• define the slow automation body definition via launching from the SCE the ISaGRAF® editor
(contextual menu on the slow automation interface object) and using available languages and
previously client/server defined links
• establish the effective client/server links entering to existing datapoints
7.4.7.2.1 Creating an ISaGRAF® slow automation (header definition)

To add an ISaGRAF® slow automation, tap into the “Objects entry” window at any level of the
electrical topology (except Site and module): select ‘Slow automation’ and right click Add.
C264/EN UM/E50.5 843

- Figure 546 - Adding an ISaGRAF® slow

automation automation (E. G. for feeder bay level)
Once added, ISaGRAF® slow automation features have to be set at SCE level:
1. Fill the relation ‘runs on’, giving which computer PLC will manage the automation. This
relation is automatically filled by SCE if slow automation is located under a bay whose
computer manager has ever been entered
2. short name and long name of the slow automation used for logging and alarm.
- Figure 547 - Setting ISaGRAF® slow automation

features
7.4.7.2.2 Adding specific datapoints to slow automation (interface definition)

The addition of a slow automation datapoint is done via the “Objects entry” window at slow
automation level by clicking on mouse’s right button.
For more details about datapoints and their configuration, refer to section .
- Figure 548 - Adding datapoints to slow

automation
844 C264/EN UM/E50.5

Slow automation datapoint is integrally produced or managed by the slow automation and
subsequently by ISaGRAF®. It cannot be linked to another acquisition or control source and the
ISaGRAF® project has to update/run its value changes or controls.
Slow automation input datapoints are stored in a non-volatile memory at BCPU level to restart on
their last known values in case of protection reboot.
7.4.7.2.3 Creating ISaGRAF® client link (interface definition)

The addition of an ISaGRAF® client is done via the “Objects entry” window at the slow automation
level by clicking on mouse’s right button and adding a ‘is client of’ relation. Choose the correct
relation depending on datapoint kind that will be used.
- Figure 549 - Adding an ISaGRAF® client link
Slow automation datapoint is integrally produced or managed by the slow automation and
subsequently by ISaGRAF®. It cannot be linked to another acquisition or control source and the
ISaGRAF® project has to update/run its value changes or controls.
Slow automation input datapoints are stored in a computer non-volatile memory to restart on their
latest known values in event of computer reboot.
7.4.7.2.4 Linking a datapoint to an ISaGRAF® client link

To link a datapoint to an ISaGRAF® client link the relation 'is client of' has to be defined. For that
double click this relation. The Relation Link Editor is then displayed. By expanding the tree view all
the available SPS datapoints are listed. Click the one you want to link then click the Ok button.
The relation is then displayed as 'defined'.
7.4.7.2.4.1 Defining ISaGRAF® IO prefix for an input
By clicking this 'is client of' relation the associated attributes window is displayed. Only the
'ISaGRAF® IO prefix' attribute (4) can be modified by the user. This attribute defines the prefix of
the identifier of this datapoint when used in ISaGRAF® workbench as an input signal of this
automation. It is built by concatenation the prefix, an underscore (if the prefix exists) and the input
IO reference automatically given by the SCE: In the example given hereafter the identifier of this
link will be: MY_INPUT_PREFIX_in_2.
C264/EN UM/E50.5 845

- Figure 550 - Defining ISaGRAF® IO prefix for an

input

• The first character has to be a letter
• The following characters have to be either a letter in upper case, either a digit or an
underscore
• The maximum length is 80 characters
7.4.7.2.4.2 Creating ISaGRAF® server link (interface definition)
The addition of an ISaGRAF® server is done via the “Objects entry” window at the slow
automation level by clicking on mouse’s right button and adding a ‘manages’ relation. Choose the
correct relation depending on datapoint kind that will be managed.
- Figure 551 - Adding an ISaGRAF® client link
7.4.7.2.4.3 Linking a datapoint to an ISaGRAF® server link
To link a datapoint to an ISaGRAF® server link the relation 'manages' has to be defined. For that
double click this relation (1). The Relation Link Editor is then displayed. By expanding the tree
view all the available DPS datapoints are listed. Click the one you want to link (2) then click the Ok
button. (In the example given hereafter the link has be done with the Substation DPS datapoint).
The relation is then displayed as 'defined' (3).
846 C264/EN UM/E50.5

- Figure 552 - Linking a datapoint to an ISaGRAF®

server link
7.4.7.2.4.4 Defining ISaGRAF® IO prefix for an output
By clicking this manages' relation the associated attributes window is displayed. Only the
'ISaGRAF® IO prefix' attribute (4) can be modified by the user. This attribute defines the prefix of
the identifier of this datapoint when used in ISaGRAF® workbench as an output signal of this
automation. It is built by concatenating the prefix, an underscore (if the prefix exists) and the
output IO reference automatically given by the SCE: In the example given hereafter the identifier
of this link will be: My_Output_Prefix_out_0.
- Figure 553 - Defining ISaGRAF® IO prefix for an

output

• The first character has to be a letter.
• The following characters have to be either a letter in upper case, either a digit or an
C264/EN UM/E50.5 847

underscore.
• The maximum length is 80 characters
7.4.7.2.4.5 Using ISaGRAF® editor (body definition)
The launching of the ISaGRAF® editor is done at slow automation level via its contextual menu
(right click).
- Figure 554 - Launching ISaGRAF® editor
Once launched, ISaGRAF® editor allows diagram edition of the automation. For details about
ISaGRAF® workbench and SCE datapoint coupling, refer to SCE_ENAP.
- Figure 555 - Using ISaGRAF® editor
7.4.7.3 Defining a group

A group is a logical OR, AND, NOR or NAND combination of components whose kind is SPS,
DPS or groups. A component can belong to several groups. Resulting datapoint associated to a
group is a SPS object called ‘Group SPS’ in data modeling.
848 C264/EN UM/E50.5

Group SPS can only belong to bays or modules. The BCPU that manages the bay (of eventually
the bay of the module) always computes it. Its composition description is done via linking it to
SPS, DPS, or Group SPS.
A group SPS can be seen as a particular fast automation reduced to one boolean function with
one implicit output plug (the group SPS itself) and input plugs corresponding to each component
of the group.
The addition of a group SPS is done via the “Objects entry” window at bay or module level of the
electrical topology by clicking on mouse’s right button.
- Figure 556 - Adding a group SPS (E. G. for

feeder bay level)
Once added, Group SPS features must be set at SCE level, as SPS datapoint. For details about
SPS datapoint configuration, refer to section "Defining datapoint" on page 689. Nevertheless, the
specific attribute ‘group type’ (1) must be set for the group. It corresponds to the logical function
(OR, AND, NOR or NAND) applied on all the components of the group.
- Figure 557 - Setting 'Group type' attribute of a

group SPS
To assign a component to a group (SPS, DPS or group):

• Add the relation ‘contains the <XXX>’ (1) at Group SPS level, where XXX corresponds to the
datapoint kind (SPS or DPS).
• Fill the relation with the relevant datapoint.
C264/EN UM/E50.5 849

- Figure 558 - Adding a component to a group
7.4.7.4 Controlling xPC by xPS change of state
CAUTION
For specific needs, some SPS or DPS can act on SPC or DPC. This relation is called xPS-xPC
association. Such an acted xPC may or may not need a channel for wiring. It can be an xPC used
for automation management for instance.
NOTE: xPS can be wired, but xPC cannot be wired. However, xPS have to be wired if a relation
“Controls On State Change” for xPC is used.
The link defines for each state of the xPS which order must be sent.
To create such a relation:

• Add the relation ‘controls on state change’ at SPS/DPS level; two relations are available
depending on control kind to act (SPC or DPC). Choose the correct one.
• Fill the relation with the relevant SPC (resp. DPC).
• Set the relation attributes (giving for each state of the xPS, the order to send: None, Reset
(resp. Open) or Set (resp. Close) for SPC (resp. DPC).
• Set the releation attribute “Control sequence activating” to ‘No’, to bypass generic execution
checks during control sequence.
850 C264/EN UM/E50.5

- Figure 559 - Controlling xPC by xPS change of

state
7.4.7.5 Producing a DPS from two SPS

For specific needs, two SPS (one for open state, and the other for closed state) can be used to
manage a DPS. This relation is called SPS-DPS association.
To produce a DPS from two SPS:

• Create the three datapoints and configure them (see section "Defining datapoint" on page
689)
• At the DPS level, add the relations ‘has open state given by’ (1) and ‘has closed state given
by’ (2)
• Fill the two relations with the previously created SPS datapoint
- Figure 560 - Producing DPS from 2 SPS
7.4.7.6 Defining interlocking

Any DPC (or SPC) belonging to a bay or module can have interlocking equation for opening order
(Off order for SPS) and/or closing order (On order for SPC).
Interlocking equation corresponds to a logical function that must be ‘true’ to send the order.
In data modeling, interlocking equation are put under SPC or DPC by adding specific SPS:
• ‘Off interlock SPS’ and ‘On interlock SPS’ for SPC
• ‘Open interlock SPS’ and ‘Close interlock SPS’ for DPC
These SPS contain the logical function definition of the interlocking that is coded with the FBD
editor.
Interlocking equation diagrams seem FBD fast automation diagrams, except that:
C264/EN UM/E50.5 851

• timer, bistable function are unusable
• there is no output plug
The addition of an interlock SPS is done via the “Objects entry” window at SPC/DPC datapoint
level by clicking on mouse’s right button (1).
- Figure 561 - Adding an interlock SPS (E. G. for

module DPC level)
Once added, interlock SPS features must be set at SCE level, as SPS datapoint. For details about
SPS datapoint configuration, refer to section .
To define interlocking equation for an interlock SPS:

• Add at interlock SPS level, a FBD interlock object (1)
• Configure this FBD interlock (refer to section Defining a FBD fast automation), with the
existing following restrictions:
• only input plugs are available for its interface definition.
• For its body description via FBD editor, timer and bistable functions do not exist.
- Figure 562 - Defining interlocking equation for an

interlock SPS
7.4.7.7 Defining an automatic/manual dependency

Automatic/manual dependency can be set at control level (SPC, DPC or SetPoint): when a control
is linked to a SPS or DPS via the automatic/manual dependency, control is refused if the SPS
(resp. DPS) is in the SET (resp. CLOSED) state.
To create an automatic/manual dependency:
852 C264/EN UM/E50.5

• Add the relation ‘has for AutoManu dependency’ (1) at control level; two relations are
available depending on the input kind setting the dependency (SPS or DPS). Choose the
correct one.
• Fill the relation with the relevant SPS or DPS (2).
- Figure 563 - Defining an automatic/manual

dependency

• For each "DPC", "SPC" or "Setpoint" datapoint, 2 relations "has for AutoManu dependency"
are available, but they are mutually exclusive.
7.4.8 Defining a Fast Load Shedding application

The goals of the The Fast Load Shedding include:
• Increasing the speed of the Load Shedding process using GOOSE system message
exchange
• Including ISaGRAF® functions for Load Shedding priority process and topology calculation
C264/EN UM/E50.5 853

7.4.8.1 Data flow
The MiCOM C264-M supports the ISaGRAF® automation which allows defining FLS
preselections and also automations (ISaGRAF® and/or PSL) which allow to test / simulate the
FLS.
It is a client of the HMI and receives the setpoints from it. The FLS preselections are transmitted to
MiCOM C264-Fi using the LSP (Load Shedding Preselection) datapoints, transmitted by GOOSE.
It is a server of the HMI and is used to re-transmit the datapoints coming from MiCOM C264-Fi to
HMI using datapoint associations mechanisms.
The MiCOM C264-Fi control the feeder and the breaker trip.
854 C264/EN UM/E50.5

In order to secure performance time of breaker trip, MiCOM C264-Fi are not servers of the HMI
and MiCOM C264-M. They only manage the PSL which allows to trip the feeder regarding the
cause and the preselection. They are dedicated to the acquisition of datapoints used for the Fast
Load Shedding function (only FLS triggers as input and breaker trip as output).
The MiCOM C264-Fi can be redundant. To avoid time performance limitation, the client/server
mechanism used in case of MiCOM C264 redundancy (to exchange the FailSt information) will be
replaced by a GOOSE transmission of this information.
7.4.8.2 Priority Setpoints

Priority setpoints are analogue setpoints whose value range from 0 to 65535.
The profile is as follows:
7.4.8.3 Load Shedding Preselection (LSP)

LSP is a 16-bit word in which several bits can be simultaneously set.
The LSP can be created under a module object or a breaker object.
The LSP is a sub-type of the MPS object. The SCE attributes of this object are:
• Short name
• Long name
• Meaning: fixed to “load shedding preselection”
C264/EN UM/E50.5 855

• Used profile – The profile is only used to define the printing / archiving status at HMI level
(alarms, interlocking values are not used).
No wiring, nor SCADA address can be associated to this object.
An LSP cannot be forced, suppressed or substituted (FSS).
This dedicated EPAS object is mapped on an IEC 61850 BSTR16 type:
856 C264/EN UM/E50.5

The Goose transmission can be automated (auto-addressing).
The LSP are not saved in MiCOM C264-Mx non-volatile memory.
In case of MiCOM C264-Mx re-initialization (or, in case of MiCOM C264-M redundancy, when the
Standby becomes Active), the LSP are initialized to 0.
The owner of the LSP is the MiCOM C264-Mx (and its redundant if it exists): it is the GOOSE
publisher and the server of the LSP. So, this computer must be clearly identified in the
configuration: a relation “has for LSP manager” is defined at Site level to define this computer.
Dedicated GOOSE message is used to transmit LSP (i.e. measurement GOOSE / status GOOSE
are not used): in this GOOSE, only the LSP status is transmitted: the quality and time-stamp are
not transmitted.
7.4.8.4 Graphical animation with LSP

Graphical animation is performed using an LSP Multistate. This object is composed of:
• 3 graphical symbols, associated to the ON, OFF and UNKNOWN states of the LSP bits
• Up to 16 components which allow to define the graphical position of the symbol associated to
each LSP bit
This representation forces to have the same graphical representation for the 16 bits of the LSP.
7.4.8.5 Use of LSP in PSL

A dedicated MASK operator allows to use the LSP in a PSL:
C264/EN UM/E50.5 857

This operator is equivalent to:
The MASK operator is generated as a sum of products in the MiCOM C264 database. The PSL
limitations are applicable on this operator.
858 C264/EN UM/E50.5

7.4.8.6 Use of LSP in ISaGRAF® scheme

An ISaGRAF® function allows to define LSP values. The prototype of this function is:
Unsigned char Set_LSP (int Value, long Ref_LSP)
The bit representation of the LSP is:
7.4.8.6.1 Set_LSP() ISaGRAF® function

ISaGRAF® manages the LSP registry through a function call Set_LSP(value, reference of nMPS)
An LSP registry is a 16bits value range which defines 16 bits priority mask. The value is in range
[0x0000 to 0xFFFF] which represents the 16-bit priority.
Value 0x0001 activate bit priority 1
One LSP registry is allocated to a MASK FBD/PSL object.
This LSP registry is sent from ISaGRAF® to MiCOM C264 Fi FBS/PSL through GOOSE status.
C264/EN UM/E50.5 859

7.4.8.6.2 Is_connected_to() ISaGRAF® function

This ISaGRAF® function is_connected_to(node1, node2, state) may be is used for operation
topology process.
The test of this function will be applied to the architecture as described below
The state as described in the specification can be

• Connected: the 2 node equipments are surely connected,
• Unconnected: the 2 node equipments are surely not connected
• Uncertain: if not connected or not unconnected (in the event of a faulty board connection
measurement for example)
7.4.8.7 Datapoints
For SPC data Point:
• value = 0 for open state
• value = 1 for close state
Datapoints possible states:

• LSP: the possible states are SET, RESET, UNKNOWN.
• Input xPS Triggers can be SPS, DPS. The possible states are described into the Product
specification document. The FSS can be applied to the xPS datapoints
Each bit of the LSP datapoint is graphically created at HMI part.
7.4.8.8 MASK object and xPS triggers

7.4.8.8.1 MASK object
For each command breaker using into Fast Load Shedding, a PSL/FBD is created.
This PSL included the new MASK object.
One or more MASK object can be created into the FBD/PSL.
This MASK object has:

• One Input LSP value. The LSP value is GOOSE sending from Isagraf.
• Up to 16 xPS input triggers.
• One xPS output open/close breaker command.
7.4.8.8.2 Trigger definition

The triggers are standard xPS. As soon as they will be used in a PSL, they will be automatically
GOOSE-defined using the SBUS automatic addressing.
An xPS input Trigger is mapped on input bit priority MASK Object of PSL/FBD
The combination of the xPS input triggers and the ISaGRAF® LSP (transmitted by GOOSE)
process the output PSL command datapoint (link to a breaker command).
The xPS input triggers state can be changed from:

• MiCOM C264 front panel Fi input command
• SCADA Equipement Simulator through ASE Gateway
860 C264/EN UM/E50.5

• HMI button with SPC command and SPS feedback
• Other IED equipment
• Another MiCOM C264 Fi
Wired triggers can be connected to extension rack or not.
Options:
• all xPS triggers are managed by the same computer:
• xPS triggers comes from another MiCOM C264 Fi:
C264/EN UM/E50.5 861

• multiple MASK objects can be created into a FBD/PSL:
• xPS triggers comes from another MiCOM C264 M, MiCOM C264P (frequency threshold),
SPS from out of range measurement:
7.4.8.9 Topology calculation

An ISaGRAF® function allows to define if 2 devices are connected:
is_connected_to (node1, node2, state) with state = connected, unconnected, uncertain, and
node1 / node2 the reference of the nodes of the 2 devices.
The FORCED <state> and SUBSTITUTED <state> status are considered as the normal <state>
of the datapoint in the topology calculation. The SUPPRESSED status is considered as the
UNKNOWN status.
862 C264/EN UM/E50.5

Two nodes are connected if it exists at least one chain of devices between the 2 nodes which are
closed, forced closed or substituted closed. Two nodes are unconnected if all chains of devices
between the 2 nodes are open, forced open or substituted open. In all other cases, the status
between two nodes is uncertain.
7.4.9 Defining a Synchroscope built-in function

7.4.9.1 Synchroscope behavior
The Synchroscope built-in function is described in section "Synchroscope and Power
Synchronizer" on page 326 of chapter Functional description (FT).
7.4.9.2 Creating a Synchroscope built-in function

The Power Synchronizer is a Sub-system component with the following characteristics:
• It shall be linked to a single phase or three phase Circuit Breaker
• The related CB shall be linked to a Synchrocheck built-in function
• The Synchrocheck built-in shall be of type 1 and Internal Manual
• The power synchronizer shall fulfill the following relations
Is Synchroscope of circuit breaker <Mandatory>
Has for Gov L Dpc
Has for Avc L Dpc
Has for Gov B Dpc
Has for Avc B Dpc
Has for On/Off Synchronizer automation Spc
Has for Auto/Manu convergence automation Spc
Has for Auto/Manu close automation Spc
Has for side convergence selection Spc
Has for VLine Mv <Mandatory>
Has for VBusbar Mv <Mandatory>
Has for FLine Mv <Mandatory>
Has for FBusbar Mv <Mandatory>
Has for DeltaV Mv <Mandatory>
Has for DeltaF Mv <Mandatory>
Has for DeltaPhase Mv <Mandatory>

• The power synchronizer’s MV datapoints shall be linked to a TMU210 board
• The power synchronizer’s DPC datapoints shall be linked to a DO board
• TMU210 “Mv read cycle” attribute shall be set to 100ms
• The power synchronizer shall define the following attributes
C264/EN UM/E50.5 863

Line side name
Busbar side name
The following figure shows how to add a Synchroscope built-in feature to a generic bay.
- Figure 564 - Adding a Synchroscope to a Bay
The following figure shows the mandatory and the optional links or relations of a synchroscope
buit-in function.
864 C264/EN UM/E50.5

- Figure 565 - Selecting links for the Synchroscope
The following figure shows the Synchroscope’s attributes: Line side name and Bar side name.
- Figure 566 - Setting Line and Busbar names
C264/EN UM/E50.5 865

7.4.9.3 Limitations
The closing control of the Circuit Breaker associated to the Synchroscope shall be configured as
“Direct Execute”; i.e. Select Before Execute (SBO) is not allowed.
- Figure 567 - Configuring closing control of the Circuit Breaker associated to the Synchroscope
866 C264/EN UM/E50.5

7.5 Defining Protection Functions
7.5.1 General
In the object view tree, the protection functions are associated with a relay (bay level). When the
first protection function is added to a bay, a relay is automatically added as a sub-component.
The following protections are available with C264Ps:

• Undervoltage protection ([27] function),
• Earth wattmetric protection ([32N] function),
• Undercurrent protection ([37] function),
• Negative Sequence Overcurrent protection ([46] function),
• Thermal overload protection ([49] function),
• Zero Sequence Overvoltage protection ([59N] function),
• Directional overcurrent protection ([67] function),
• Directional Earth Fault protection ([67N] function),
• Overfrequency protection ([81O] function),
• Range Frequency protection ([81R] function),
• Underfrequency protection ([81U] function),
• Fuse failure detection ([60FL] function)
7.5.1.1 General architecture

In the object view tree, the tree structure is used to present the protection functions.
- Figure 568 - Protection functions tree structure
Relay object is automatically created when a protection function is added to the bay. Relay does
not contain attribute and cannot be edited.
C264/EN UM/E50.5 867

Each Protection function sub-tree contains a folder representing the associated thresholds . The
characteristics (as instantaneous, temporization, trip signal, and mode of operation) and the links
of each characteristic are settable.
7.5.1.2 Defining a protection function

For each protection function the SCE allows to use the trip contacts 1, 2, 3 or any combination
(i.e.: 1 and 2, 1 and 3, 2 and 3, 1 and 2 and 3, None) using the attributes:
« trip contact #1 used » enumerate [No;Yes] default value: “Yes”
At bay level, to add a protection function:

• Add the protection function from Objects entry (Built-in function, Relay built-in function sub-
tree) at bay level (1): the relay folder (2) is automatically added with the first protection
function and the protection function (3) is added as well,
• Select the function (3),
• Update the function attributes: short name and long name, trip contacts to use (4).
- Figure 569 - Adding a protection function
These trip contacts relates to the serial SPS relays of the DSPIO board.
For each used function, select one or more DSPIO trip contacts by putting the value to Yes. A
relay can be used by several protection functions.
To allow backward compatibility these attributes are set to Yes.
To trip the circuit breaker associated with the protection function:
1. Define an SPC at electrical level associated to the circuit breaker trip
2. Wire this SPC on a digital output (trip relay of the circuit breaker) of one of the device boards
3. Set the SPC attributes:
868 C264/EN UM/E50.5

Used profile: Reference a direct execute profile
Activation mode: Permanent
Command panel assignment: No
Dependancies: No
- Figure 570 - Attributes of SPC
4. Control this SPC by a set of selected SPS produced by the protection function (refer to
"Controlling xPC by xPS change of state" on page 850), e.g. with a 67 protection function:
5. Set the attributes of the relations ‘is controlled on state change of’:
Reset order value: reset
Set order value: set
Selfcheck fault order value: reset
Control sequence activating: No
- Figure 571 - Relation attributes
7.5.2 Undervoltage (ANSI code 27)

Undervoltage conditions may occur on a power system for a variety of reasons, for instance
Increased system loading or complete loss of bus-bar voltage.
C264/EN UM/E50.5 869

The undervoltage function [27] is used to detect an increase of load. It uses definite delay time
undervoltage protection.
The undervoltage protection element has two programmable stages (V<, V<<) with delay timers:
tV<, tV<<.
The protection element includes two thresholds. The two thresholds provide both alarm and trip
stages, where required. Alternatively, different time settings are settable, depending upon the
severity of the current dip.
7.5.2.2 Defining Undervoltage protection function

An addition of [27] function is done under SCE via the “Object entry” area at bay level by clicking
To add [27] Undervoltage protection function, see chapter "Defining a protection function" on
page 868 .
The protection function sub-tree contains 2 thresholds (1): threshold 1, threshold 2
The first threshold sub-tree contains four nodes:

• 27 t1 inst. SPS (2) is the instantaneous undervoltage status for the first threshold,
corresponding to “V<” value. This SPS is a permanent signal (permanent “detection mode”
attribute not settable). To set 27 t1 inst. SPS attributes, see section ,
• 27 t1 mode MPS (3) is the mode of operation of the protection for the first threshold,
corresponding to “V< ? = ON, OR or AND”. All the attributes can be modified. To set 27 t1
mode MPS attributes, see section "Defining MPS datapoint" on page 692,
• 27 t1 temp. SPS (4) is temporization signal for the first threshold corresponding to “tV<” time
delay. This datapoint is a permanent signal (permanent “detection mode” attribute not
settable). To set 27 t1 temp. SPS attributes, see section ,
• 27 t1 trip SPS (5) is the trip signal for the first threshold (“V<” trip). The trip signal is a transient
(pulse) signal (transient “detection mode” not modifiable). Time reference, set and reset
delays are fixed. To set 27 t1 trip SPS attributes, see section .
870 C264/EN UM/E50.5

- Figure 572 - [27] Undercurrent sub-tree
Update the relations and the links of the datapoints to point to a specific existing profile. See
section "Linking a datapoint to a profile" on page 708, for details about profile definition and
setting.
The content of “threshold 2” is identical to “threshold 1”:

• 27 t2 inst. is identical to 27 t1 inst. SPS for threshold 2,
• 27 t2 mode is identical to 27 t1 mode MPS for threshold 2,
• 27 t2 temp. is identical to 27 t1 temp. SPS for threshold 2,
• 27 t2 trip is identical to 27 t1 trip SPS for threshold 2.
7.5.3 Earth Wattmetric Protection (ANSI code 32N)

The directional earth fault protection provides three directional / non directional earth overcurrent
thresholds and two wattmetric and active earth fault current thresholds.
Protective relays offer the possibility to choose between a Wattmetric (Pe) protection and IeCos
(active component of the earth fault current) protection functionality mode.
The Pe> and Pe>> settings are calculated as:
Vres x Ires x Cos(f - fc) = 9 x Ve x Ie x Cos(f - fc)
C264/EN UM/E50.5 871

Where:
• f = angle between the polarising voltage (Vres) and the residual current
• fc = relay characteristic angle (RCA/torque angle)
• Vres = residual voltage
• Ires = residual current
• Ve = zero sequence voltage
• Ie = zero sequence current
The measurement of the Pe depends on the voltage wiring of the relay.
The residual current Ires can either be acquired through measurement or calculation with the local
CT/VT board.
In case of 3Vpn wiring, the Ve will be equal to Ve= 1/3(Va+VB+VC). In the other insertions way
the applied voltage to the relay is directly used to calculate the Pe.
7.5.3.2 Defining earth wattmetric protection function

An addition of [32N] function is done under SCE via the “Object entry” area at bay level by clicking
To add [32N] earth wattmetric protection function, see chapter "Defining a protection function" on
page 868.
The protection function sub-tree contains two thresholds (1): threshold 1 and threshold 2,

• 32N t1 inst. SPS (2) is the instantaneous earth wattmetric status for the first threshold,
corresponding to “Pe>” value. This datapoint is a permanent signal (permanent “detection
mode” attribute not settable). To set 32N t1 inst. SPS attributes, see section ,
• 32N t1 mode MPS (3) is the mode of operation of the protection for the first threshold.
corresponding to “Pe> ?” = ON / OFF All the attributes are settable. To set 32N t1 mode MPS
attributes, see section "Defining MPS datapoint" on page 692,
• 32N t1 temp. SPS (4) is the temporization signal for the first threshold corresponding to “t
Pe >” time delay. This datapoint is a permanent signal (permanent “detection mode” attribute
nots settable). To set 32N t1 temp. SPS attributes, see section ,
• 32N t1 trip SPS (5) is the trip signal for the first threshold (“Pe> trip”). The trip signal is a
transient (pulse) signal (transient “detection mode” not settable). Time reference, set and
reset delays are fixed. To set 32N t1 trip SPS attributes, see section .
872 C264/EN UM/E50.5

- Figure 573 - [32N] Earth wattmetric sub-tree
setting.
The content of “threshold 2” is identical to “threshold 1”:

• 32N t2 inst. is identical to 32N t1 inst. SPS for threshold 2,
• 32N t2 mode is identical to 32N t1 mode MPS for threshold 2,
• 32N t2 temp. is identical to 32N t1 temp. SPS for threshold 2,
• 32N t2 trip is identical to 32N t1 trip SPS for threshold 2.
7.5.4 Undercurrent protection (ANSI code 37)

The undercurrent function [37] is used to detect a loss of load (for example the draining of a pump
or breakage of a conveyor belt). It uses definite delay time undercurrent protection.
The undercurrent protection relays consists of one threshold. The user can set the following
parameters:
• Undercurrent threshold I<
• Time delayed undercurrent threshold tl<
C264/EN UM/E50.5 873

The threshold provides alarm and trip stage, where required. Alternatively, time setting is settable,
depending upon the severity of the current dip.
7.5.4.2 Defining Undercurrent protection function

To add [37] earth wattmetric protection function, see chapter "Defining a protection function" on
page 868.
The sub-tree contains four nodes:

• 37 t inst. SPS (2) is the instantaneous undercurrent status for the first threshold,
corresponding to “I<” Value. This datapoint is a permanent signal (permanent “detection
mode” attribute not settable). To set 37 t inst. SPS attributes, see section ,
• 37 t mode MPS (3) is the mode of operation of the protection for the first threshold,
corresponding to “I< ?” = ON or OFF. All the attributes can be set. To set 37 t mode MPS
• 37 t temp. SPS (4) is the temporization signal for the first threshold, corresponding to “tI<”
delay time. This datapoint is a permanent signal (permanent “detection mode” attribute
cannot be set). To set 37 t temp. SPS attributes, see section ,
• 37 t trip SPS (5) is the trip signal for the first threshold (“I<” trip). This datapoint is a transient
(pulse) signal (transient “detection mode” not settable). Time reference, set and reset delays
are fixed. To set 37 t trip SPS attributes, see section .
874 C264/EN UM/E50.5

- Figure 574 - [37] Undercurrent sub-tree
setting.
7.5.5 Negative sequence OC protection (ANSI code 46)

When applying traditional phase overcurrent protection, the overcurrent elements must be set
higher than maximum load current, thereby limiting the sensitivity of the element. Most protection
techniques also use an earth fault element operating from residual current, which improves
sensitivity for earth faults. However, certain faults may arise which can remain undetected by
such techniques.
Any unbalanced fault condition will produce negative sequence current. Thus, a negative phase
sequence overcurrent element can detect both phase-to-phase and phase to earth faults.
The negative phase sequence overcurrent elements have a current pick up settings I2>, I2>>,
I2>>>, and are time delayed in operation by the adjustable timers tI2>, tI2>>, tI2>>>.
The protection element includes three thresholds. The first threshold can be set as DT or IDMT
trip delay time.
The curves are the same as for the [50/51], [50N/51N] protection.
C264/EN UM/E50.5 875

The three thresholds provide both alarm and trip stages, where required. Alternatively, different
time settings are settable, depending upon the severity of the current dip
7.5.5.2 Defining Negative Sequence Overcurrent protection function

To add [46] Negative Sequence Overcurrent protection function, see chapter "Defining a
protection function" on page 868.
The protection function sub-tree contains three thresholds (1): threshold 1, threshold 2 and
threshold 3.

• 46 t inst. SPS (2) is the instantaneous negative sequence overcurrent status for the first
threshold, corresponding to “I2>” value. This datapoint is a permanent signal (permanent
“detection mode” attribute not settable). To set 46 t inst. SPS attributes, see section ,
• 46 t mode MPS (3) is the mode of operation of the protection for the first threshold,
corresponding to “I2> ?” = ON or OFF. All the attributes can be set. To set 46 t mode MPS
• 46 t temp. SPS (4) is the temporization signal for the first threshold, corresponding to “tI2>”
time delay. This datapoint is a permanent signal (permanent “detection mode” attribute not
settable). To set 46 t temp. SPS attributes, see section ,
• 46 t trip SPS (5) is the trip signal for the first threshold (“I2>” trip). This datapoint is a transient
delays are fixed. To set 46 t trip SPS attributes, see section .
876 C264/EN UM/E50.5

- Figure 575 - [46] Negative Sequence Overcurrent sub-tree
setting.
The contents of “threshold 2” and “threshold 3” are identical to “threshold 1”.

• 46 t2 inst. and 46 t3 inst. are identical to 46 t1 inst. SPS for threshold 2 and threshold 3,
• 46 t2 mode and 46 t3 mode are identical to 46 t1 mode MPS for threshold 2 and threshold 3,
C264/EN UM/E50.5 877

• 46 t2 temp. and 46 t3 temp are identical to 46 t1 temp. SPS for threshold 2 and threshold 3,
• 46 t2 trip and 46 t3 mode are identical to 46 t1 trip SPS for threshold 2 and threshold 3.
7.5.6 Thermal overload protection (ANSI code 49)

Thermal overload protection can be applied to prevent damages to the electrical plant equipment
when operating at temperatures in excess.
Protective relays incorporate a current based thermal replica, using load current to reproduce the
heating and cooling of the equipment to be protected. The element thermal overload protection
(corresponding to 49 th overload in SCE configurator) can be set with both alarm and trip stages
(49 th alarm and 49 trip th over.).
i.e. whether the overload was applied from “hot” or “cold”.
7.5.6.2 Defining Thermal overload protection function

To add [49] Thermal overload protection function, see chapter "Defining a protection function" on
page 868.
The protection function sub-tree contains one threshold, with four nodes:
• 49 t mode MPS (2) is the mode of operation of the protection, corresponding to “Thermal OL”
(thermal overload ? = ON or OFF). All the attributes are settable. To set 49 t mode MPS
• 27 th alarm. SPS (3) is the instantaneous thermal alarm status, corresponding to thermal
alarm value. This datapoint is a permanent signal (permanent “detection mode” attribute not
settable). To set 27 th alarm SPS attributes, see section "Defining SPS datapoint" on page
690,
• 27 th overload SPS (4) is the thermal overload status, corresponding to thermal alarm value.
This datapoint is a permanent signal (permanent “detection mode” attribute not settable). To
set 27 th overload SPS attributes, see section "Defining SPS datapoint" on page 690 ,
• 27 trip th over. SPS (5) is the trip signal, corresponding to thermal trip. This datapoint is a
transient (pulse) signal (transient “detection mode” not modifiable). Time reference, set and
reset delays are fixed. To set 27 trip th over. SPS attributes, see section "Defining SPS
datapoint" on page 690 .
878 C264/EN UM/E50.5

- Figure 576 - [46] Negative Sequence Overcurrent sub-tree
C264/EN UM/E50.5 879

setting.
7.5.7 Overvoltage (ANSI code 59)

The overvoltage protection function (ANSI code 59) is used to detect system voltage that are too
high or to check that there is sufficient voltage to authorize a source transfer.
The overvoltage function measures the fundamental frequency component of the line-to-line
voltages regardless of the voltage measurement mode. By using line-to-line voltage any phase-
to-ground over-voltages during earth/ground faults have no effect. Whenever any of these three
line-to-line voltages exceeds the start setting of a particular stage, this stage starts and a start
signal is issued. If the fault situation remains on longer than the operative time setting, a trip signal
is issued.
In solidly earthed/grounded, four-wire networks with loads between phase and neutral voltages,
overvoltage protection may be needed for phase-to-ground voltages as well. In such application,
the programmables stages can be used.
7.5.7.2 Defining overvoltage protection function

To add [59] Overvoltage protection function, see chapter "Defining a protection function" on page
868.
The first protection function sub-tree contains one threshold with four nodes:
• 59 t1 inst. SPS indicates instantaneous directional overvoltage status for the first threshold
corresponding to “directional U>” value. This datapoint is a permanent signal (permanent
“detection mode” attribute not settable). To set 59 t1 inst. SPS attributes, see
section "Defining SPS datapoint" on page 690,
• 59 t1 mode MPS indicates the mode of operation of the protection for the first threshold
(“U> ?” = ON, OFF or DIR). All the attributes are settable. To set 59 t1 mode MPS attributes,
see section "Defining MPS datapoint" on page 692,
• 59 t1 temp. SPS indicates the temporization for the first threshold, corresponding to “tU>”
time delay. The temporization datapoint is a permanent signal (permanent “detection mode”
attribute not settable). To set 59 t1 temp. SPS attributes, see section "Defining SPS
datapoint" on page 690,
• 59 t1 trip SPS indicates the trip signal for the first threshold (U> trip). The trip signal is a
reset delays are fixed. To set 59 t1 trip SPS attributes, see section "Defining SPS datapoint"
on page 690.
The contents of “threshold 2” is similar to “threshold 1”.

• 59 t2 inst. is identical to 59 t1 inst. SPS,
• 59 t2 mode is identical to 59 t1 mode MPS,
880 C264/EN UM/E50.5

• 59 t2 temp. is identical to 59 t1 temp. SPS,
• 59 t2 trip is identical to 59 t1 trip SPS.
7.5.8 Residual overvoltage / neutral displacement (ANSI code 59N)

On a healthy three phase power system, the addition of each of the three phase to earth voltages
is nominally zero, as this results from the vector addition of three balanced vectors. However,
when an earth fault occurs on the primary system this balance is upset and a ‘residual’ voltage is
produced. This can be measured, for example, at the secondary terminals of a voltage
transformer having a “broken delta” secondary connection. Hence, a residual voltage-measuring
relay can be used to offer earth fault protection on such a system. Note that this condition causes
a rise in the neutral voltage with respect to earth, which is commonly referred to as “neutral
voltage displacement”.
The voltage setting applied to the protection elements is dependent upon the magnitude of
residual voltage that is expected to occur during an earth fault condition.
This in turn is dependent upon the method of system earthing employed. It must also be ensured
that the relay is set above any standing level of residual voltage that is present on the system.
The protection element has one programmable element Uen> with delay time tUen>.
7.5.8.2 Defining Zero Sequence Overvoltage protection function

To add [59N] Zero Sequence Overvoltage protection function, see chapter "Defining a protection
function" on page 868.
The protection function sub-tree contains one threshold with four nodes:
• 59N t inst. SPS (2) is the instantaneous zero sequence overvoltage status, corresponding to
“Uen>” value. This datapoint is a permanent signal (permanent “detection mode” attribute not
settable). To set 59N t inst. SPS attributes, see section "Defining SPS datapoint" on page
690,
• 59N t mode MPS (3), mode of operation of the protection corresponding to “Uen> ?” = ON or
OFF. All the attributes are settable. To set 59N t mode MPS attributes, see section "Defining
MPS datapoint" on page 692,
• 59N t temp. SPS (4) is the temporization signal corresponding to “t Uen>” delay time. This
datapoint is a permanent signal (permanent “detection mode” attribute not settable). To set
59N t temp. SPS attributes, see section "Defining SPS datapoint" on page 690,
• 59N t trip SPS (5). trip signal for the first threshold (Uen> trip). This trip signal is a transient
delays are fixed. To set 59N t trip SPS attributes, see section "Defining SPS datapoint" on
page 690.
C264/EN UM/E50.5 881

- Figure 577 - [59N] Zero Sequence Overvoltage sub-tree
setting.
7.5.9 Directional / Non-directional phase OC protection (ANSI code 67/50/51)

If a fault current can flow in both directions through a relay location, it is necessary to add
directionality to the overcurrent relays in order to obtain correct co-ordination. Typical systems
that require such protection are parallel feeders and ring main systems.
In order to give directionality to an overcurrent relay, it is necessary to provide it with a suitable

reference, or polarising signal. The reference generally used is the system voltage, as its angle
remains relatively constant under fault conditions.
Each directional threshold consists of:

• Current threshold,
• Relay Characteristic Angle angle (IÛ) / Torque angle and Trip boundary zone.
882 C264/EN UM/E50.5

The directional overcurrent protection element compares the directional fault current with the set
thresholds I> [50/51-1], I>> [50/51-2], I>>> [50/51-3], voltage and the relevant angle between the I
and U for each threshold.
The first and second thresholds can be set as directional or non-directional as definite delay time
or inverse delay time. The third threshold can be set as directional or non-directional as definite
delay time only, but can be set to work on the peak of the current measured in non-directional
way.

• The phase current exceeds the set overcurrent threshold,
• The current vector lies within the trip boundary zone.
selectivity.
7.5.9.2 Defining [67] Directional overcurrent protection function

To add [67] Directional overcurrent protection function, see chapter Defining a protection function.
threshold 3.
The first threshold sub-tree contains six nodes:

• 67 t1 in dir rev SPS (2) indicates instantaneous non-directional (reverse) overcurrent status
for the first threshold, corresponding to “non directional I>” value. This datapoint is a
permanent signal (permanent “detection mode” attribute is not settable). To set 67 t1 in dir rev
SPS attributes, see section "Defining SPS datapoint" on page 690
• 67 t1 inst. SPS (3) indicates instantaneous directional overcurrent status for the first
threshold corresponding to “directional I>” value. This datapoint is a permanent signal
(permanent “detection mode” attribute not settable). To set 67 t1 inst. SPS attributes, see
section "Defining SPS datapoint" on page 690
• 67 t1 interlock SPS (4) indicates interlock status (I> >> >>> Interlock). This datapoint is
available for the first threshold only. It is a permanent signal (permanent “detection mode”
attribute not settable). To set 67 t1 interlock SPS attributes, see section "Defining SPS
datapoint" on page 690
• 67 t1 mode MPS (5) indicates the mode of operation of the protection for the first threshold
(“I> ?” = ON, OFF or DIR). All the attributes are settable. To set 67 t1 mode MPS attributes,
see section Defining Automation Functions
• 67 t1 temp. SPS (5) indicates the temporization for the first threshold, corresponding to “tI>”
time delay. The temporization datapoint is a permanent signal (permanent “detection mode”
attribute not settable). To set 67 t1 temp. SPS attributes, see section "Defining SPS
C264/EN UM/E50.5 883

• 67 t1 trip SPS (6) indicates the trip signal for the first threshold (I> [50/51] trip). The trip signal
is a transient (pulse) signal (transient “detection mode” not settable). Time reference, set and
reset delays are fixed. To set 67 t1 trip SPS attributes, see section "Defining SPS datapoint"
on page 690
- Figure 578 - [67] Directional overcurrent sub-tree
Update the relations and the links of the datapoints to point to a specific existing profile
The contents of “threshold 2” and “threshold 3” are similar to “threshold 1”.

• 67 t2 in dir rev and 67 t3 in dir rev are identical to 67 t1 in dir rev SPS for thresholds 2 and 3,
• 67 t2 inst. and 67 t3 inst. are identical to 67 t1 inst. SPS,
• 67 t1 interlock menu doesn’t exist for thresholds 2 and 3,
• 67 t2 mode and 67 t2 mode are identical to 67 t1 mode MPS for thresholds 2 and 3,
• 67 t2 temp. and 67 t2 temp. are identical to 67 t1 temp. SPS for thresholds 2 and 3,
• 67 t2 trip and 67 t2 trip are identical to 67 t1 trip SPS for thresholds 2 and 3.

67N/50N/51N)
884 C264/EN UM/E50.5

The directional earth/ground fault protection provides three directional / non directional
earth/ground overcurrent thresholds.
The directional earth/ground fault overcurrent protection element compares the earth/ground fault
current, residual voltage with the set thresholds Ie> [50N/51N-1], Ue> [50N-1], Ie>> [50N/51N-2],
Ue>> [50N-2], Ie>>> [50N/51N-3], Ue>>> [50N-3] and the relevant angle between the Ie and Ue
for each threshold.
The first threshold uses only the acquired earth fault current. Second and third tresholds can use
acquired or computed earth/ground fault current. If an earth default voltage is acquired, it is used,
in all other cases the computed earth fault voltage is used.
The first and second threshold can be set as definite or inverse delay time. The third current
threshold can be set as directional or non-directional but with only definite delay time setting.

• thresholds for Ie [50N/51N] and Ue are exceeded (earth/ground fault overcurrent protection
element)
• Ie [50N/51N] current vector is in the tripping area (IeÛe)
• the tripping timer expires
The peak detection is applied where a CT saturation condition occurs and the measure is not
more trustworthy.
selectivity.
7.5.10.2 Defining [67N] Directional Earth/ground Fault protection function

To add [67N] Directional Earth/ground Fault protection function, see chapter Defining a protection
function.
threshold 3.
The first threshold sub-tree contains six nodes:

• 67N t1 in dir rev SPS (2) indicates instantaneous non-directional Earth/ground Fault
overcurrent status for the first threshold, corresponding to non-directional “Ie>” value. This
datapoint is a permanent signal (permanent “detection mode” not settable). To set 67N t1 in
dir rev SPS attributes, see section "Defining SPS datapoint" on page 690
• 67N t1 inst. SPS (3): indicates instantaneous directional Earth/ground Fault overcurrent
status for the first threshold, corresponding to directional “Ie>” value. This datapoint is a
permanent signal (permanent “detection mode” attribute not settable). To set 67N t1 inst. SPS
attributes, see section "Defining SPS datapoint" on page 690
• 67N t1 interlock SPS (4) is the Interlock status (“Ie> >> >>> Interlock”). This status is
available for the first threshold only. This datapoint is a permanent signal (the permanent
“detection mode” attribute cannot be modified). To set 67N t1 interlock SPS attributes, see
C264/EN UM/E50.5 885

section "Defining SPS datapoint" on page 690

• 67N t1 mode (5) is the mode of operation of the protection for the first threshold (Ie> ?” = ON,
OFF or DIR). All the attributes can be modified. To set 67N t1 mode MPS attributes, see
section Defining MPS datapoint
• 67N t1 temp. (5) is the temporization signal for the first threshold, corresponding to “tIe>”
time delay. The temporization signal is a permanent signal (the permanent “detection mode”
attribute cannot be modified). To set 67N t1 temp. SPS attributes, see section "Defining SPS
• 67N t1 trip (6). trip signal for the first threshold (Ie> trip). The trip signal is a transient (pulse)
signal (transient “detection mode” not modifiable). Time reference, set and reset delays are
fixed. To set 67N t1 trip SPS attributes, see section "Defining SPS datapoint" on page 690
- Figure 579 - [67N] Directional earth/ground fault

sub-tree
Update the relations and the links of the datapoints to point to a specific existing profile.
The contents of “threshold 2” and “threshold 3” are similar to “threshold 1”.

• 67N t2 in dir rev and 67N t3 in dir rev are identical to 67N t1 in dir rev SPS for thresholds 2 and
3,
• 67N t2 inst. and 67N t3 inst. are identical to 67N t1 inst. SPS for thresholds 2 and 3,
• 67N t1 interlock menu doesn’t exist for thresholds 2 and 3,
• 67N t2 mode and 67N t2 mode are identical to 67N t1 mode MPS for thresholds 2 and 3,
• 67N t2 temp. and 67N t2 temp. are identical to 67N t1 temp. SPS for thresholds 2 and 3,
• 67N t2 trip and 67N t2 trip are identical to 67N t1 trip SPS for thresholds 2 and 3.
886 C264/EN UM/E50.5

7.5.11 Overfrequency (ANSI codes 81O)

Overfrequency running of a generator arises when the mechanical power input to the machine
exceeds the electrical output. This could happen, for instance, when there is a sudden loss of load
due to tripping of an outgoing feeder from the plant to a load center. Under such over speed
conditions, the governor should respond quickly so as to obtain a balance between the
mechanical input and electrical output, thereby restoring normal frequency. Over frequency
protection is required as a back-up to cater for slow response of frequency control equipment.
Following faults on the network, or other operational requirements, it is possible that various
subsystems will be formed within the power network and it is likely that each of these subsystems
will suffer from a generation to load imbalance. The “islands” where generation exceeds the
existing load will be subject to overfrequency conditions, the level of frequency being a function of
the percentage of excess generation.
The relatively long time delays are intended to provide time for the system controls to respond and
will work well in a situation where the increase of system frequency is slow.
7.5.11.2 Defining Overfrequency protection function

An addition of [81O] function is done under SCE via the “Object entry” area at bay level by clicking
To add [81O] Overfrequency protection function, see chapter "Defining a protection function" on
page 868.
The protection function sub-tree contains six thresholds (1) from threshold 1 up to threshold 6.

• 81O t1 inst. SPS (2) is instantaneous overfrequency status for the first threshold,
corresponding to f1 Value. This datapoint is a permanent signal (permanent “detection mode”
attribute not settable). To set 81O t1 inst. SPS attributes, see section "Defining SPS
datapoint" on page 690 ,
• 81O t1 mode MPS (3) is the mode of operation of the protection for the first threshold,
corresponding to “f1 ?” = MAX or “81>”. All the attributes can be set. To set 81O t1 mode MPS
• 81O t1 temp. SPS (4) is the temporization signal for the first threshold, corresponding to tf1.
This datapoint is a permanent signal (permanent “detection mode” not settable). To set 81O
t1 temp. SPS attributes, see section "Defining SPS datapoint" on page 690,
• 81O t1 trip SPS (5) is the trip signal for the first threshold (f1 trip). This datapoint is a transient
delays are fixed. To set 81O t1 trip SPS attributes, see section "Defining SPS datapoint" on
page 690.
C264/EN UM/E50.5 887

- Figure 580 - [81O] Overfrequency sub-tree
setting.
The contents of “threshold 2” to “threshold 6” are identical to “threshold 1”.
888 C264/EN UM/E50.5

• 81O t2 inst. to 81O t6 inst. are identical to 81O t1 inst. SPS for thresholds 2 to 6,
• 81O t2 mode to 81O t6 mode are identical to 81O t1 mode MPS for thresholds 2 to 6,
• 81O t2 temp. to 81O t6 temp. are identical to 81O t1 temp. SPS for thresholds 2 to 6,
• 81O t2 trip to 81O t6 trip are identical to 81O t1 trip SPS for thresholds 2 to 6.
7.5.12 Rate of change of frequency (ANSI code 81R)

The range frequency protection allows the user to select the number of cycle to be involved in the
calculation of the rate of change of frequency elements, and the number of confirmation of
calculation for positioning the protection.
In fact, the instantaneous element is positioned after exceeding the threshold for a programmable
number of df/dt function calculation.
When the input voltage value is insufficient this will lead to irregular behavior and the frequency
elements could mal operate.
This is important during line energization, de-energization or a generator acceleration where

significant distortion can be experienced. To prevent the mal operation, all the frequency
elements and related thresholds are blocked by mean of an adjustable U/V blocking function.
7.5.12.2 Defining Range Frequency protection function

An addition of [81R] function is done under SCE via the “Object entry” area at bay level by clicking
To add [81R] Range Frequency protection function, see chapter "Defining a protection function"
on page 868.

• 81R t1 inst. SPS (2) is instantaneous range status for the first threshold, corresponding to
df/dt1 value. This datapoint is a permanent signal (permanent “detection mode” attribute not
settable). To set 81R t1 inst. SPS attributes, see section "Defining SPS datapoint" on page
690 ,
• 81R t1 mode MPS (3) is the mode of operation of the protection for the first threshold,
corresponding to “df/dt ?” = ON or OFF All the attributes can be set. To set 81R t1 mode MPS
• 81R t1 temp. SPS (4) is the temporization signal for the first threshold, corresponding to
“t df/dt1”. This datapoint is a permanent signal (permanent “detection mode” attribute not
settable). To set 81R t1 temp. SPS attributes, see section "Defining SPS datapoint" on page
690 ,
• 81R t1 trip SPS (5) is the trip signal for the first threshold (df/dt trip). This datapoint is a
reset delays are fixed. To set 81R t1 trip SPS attributes, see section "Defining SPS datapoint"
on page 690 .
C264/EN UM/E50.5 889

- Figure 581 - [81R] Range Frequency sub-tree
setting.

• 81R t2 inst. to 81R t6 inst. are identical to 81R t1 inst. SPS for thresholds 2 to 6,
• 81R t2 mode to 81R t6 mode are identical to 81R t1 mode MPS for thresholds 2 to 6,
890 C264/EN UM/E50.5

• 81R t2 temp. to 81R t6 temp. are identical to 81R t1 temp. SPS for thresholds 2 to 6,
• 81R t2 trip to 81R t6 trip are identical to 81R t1 trip SPS for thresholds 2 to 6.
7.5.13 Underfrequency (ANSI codes 81U)

Frequency variations on a power system are an indication that the power balance between
generation and load has been lost. In particular, underfrequency implies that the net load is in
excess of the available generation. Such a condition can arise, when an interconnected system
splits, and the load left connected to one of the subsystems is in excess of the capacity of the
generators in that particular subsystem. Industrial plants that are dependent on utilities to supply
part of their loads will experience underfrequency conditions when the incoming lines are lost.
In order to minimize the effects of underfrequency on a system, a multi stage load shedding
scheme may be used with the plant loads prioritized and grouped. During an underfrequency
condition, the load groups are disconnected sequentially depending on the level of
underfrequency, with the highest priority group being the last one to be disconnected.
Time delays should be sufficient to override any transient dips in frequency, as well as to provide
time for the frequency controls in the system to respond.
7.5.13.2 Defining Underfrequency protection function

An addition of [81U] function is done under SCE via the “Object entry” area at bay level by clicking
To add [81U] Underfrequency protection function, see chapter "Defining a protection function" on
page 868.

• 81U t1 inst. SPS (2) is instantaneous underfrequency status for the first threshold,
corresponding to f1 Value. This datapoint is a permanent signal (permanent “detection mode”
attribute not settable). To set 81U t1 inst. SPS attributes, see section "Defining SPS
datapoint" on page 690,
• 81U t1 mode MPS (3) is the mode of operation of the protection for the first threshold,
corresponding to “f1 ?” = MIN or “81<”. All the attributes can be set. To set 81U t1 mode MPS
• 81U t1 temp. SPS (4) is the temporization signal for the first threshold, corresponding to tf1.
set 81U t1 temp. SPS attributes, see section "Defining SPS datapoint" on page 690,
• 81U t1 trip SPS (5) is the trip signal for the first threshold (f1 trip). This datapoint is a transient
(pulse) signal (transient “detection mode” not settable). Time reference, set and reset delays
are fixed. To set 81U t1 trip SPS attributes, see section "Defining SPS datapoint" on page
690.
C264/EN UM/E50.5 891

- Figure 582 - [81R] Range Frequency sub-tree
setting.

• 81U t2 inst. to 81U t6 inst. are identical to 81U t1 inst. SPS for thresholds 2 to 6,
• 81U t2 mode to 81U t6 mode are identical to 81U t1 mode MPS for thresholds 2 to 6,
892 C264/EN UM/E50.5

• 81U t2 temp. to 81U t6 temp. are identical to 81U t1 temp. SPS for thresholds 2 to 6,
• 81U t2 trip to 81U t6 trip are identical to 81U t1 trip SPS for thresholds 2 to 6.
7.5.14 VT supervision (ANSI code 60FL)

The VT supervision function is used to block the protection functions whose behavior is impacted
due to voltage measurements. It helps in detecting a failure in the secondary circuits between the
voltage transformer and IED to avoid unintended operations of the voltage protection functions. A
fault in the voltage measuring circuit is referred to as a fuse failure (ANSI code 60FL). This term
may be misleading since a blown fuse is just one of the many possible reasons for a broken
circuit.
A fuse failure may occur due to blown fuses, broken wires or intended substation operations. An
incorrectly measured voltage can result in an undesired operation of some protection functions.
7.5.14.2 Defining a VT supervision protection function

An addition of [60FL] function is done under SCE via the “Object entry” area at bay level by
The protection function sub-tree contains one node:

• 60FL ff ind SPS is instantaneous fuse failure status. This datapoint is a permanent signal
(permanent “detection mode” attribute not settable). To set 60FL ff ind SPS attributes, see
section "Defining SPS datapoint" on page 690.
The automatism sub-tree contains two nodes:

• 60FL ff block SPS is the protection function blocking status. This datapoint is a permanent
signal (permanent “detection mode” attribute not settable). To set 60FL ff block SPS
attributes, see section "Defining SPS datapoint" on page 690 .
• 60FL ff reset block SPC is the reset blocking protection control. The activation mode of this
control is set to permanent. To set ‘general’ attributes of the 60FL ff reset block SPC, see
section "Defining SPC datapoint" on page 700,
- Figure 583 - [60FL] VT supervision sub-tree
C264/EN UM/E50.5 893

7.5.15 Inrush current blocking (ANSI code H2)

The Inrush Blocking detects high inrush current flows that occur when transformers or machines
are connected. The function identifies an inrush current by evaluating the ratio of the second
harmonic current components to the fundamental wave. If this ratio exceeds the set threshold,
then the inrush blocking function operates and inhibits the following functions:
• phase directional overcurrent [67/50/51]
• earth directional overcurrent [67N/50N/51N]
• negative sequence overcurrent [46]
Another settable current threshold (H2_Imax_threshold) blocks Inrush Blocking, if the current
exceeds this threshold. A fixed threshold (8% In) blocks Inrush Blocking, if the current is less than
this threshold.
7.5.15.2 Defining Inrush current blocking protection function

An addition of [H2] function is done under SCE via the “Object entry” area at bay level by clicking
To add [H2] Inrush current blocking protection function, see chapter "Defining a protection
function" on page 868.
The sub-tree contains four nodes:
894 C264/EN UM/E50.5

• IA Inrush detec SPS is the instantaneous inrush current status for the first threshold,
corresponding to “Imax” Value on line A. This datapoint is a permanent signal (permanent
“detection mode” attribute not settable). To set IA Inrush detec SPS attributes, see section
"Defining SPS datapoint" on page 690
• IB Inrush detec SPS is the instantaneous inrush current status for the first threshold,
corresponding to “Imax” Value on line B. This datapoint is a permanent signal (permanent
“detection mode” attribute not settable). To set IB Inrush detec SPS attributes, see section
• IC Inrush detec SPS is the instantaneous inrush current status for the first threshold,
corresponding to “Imax” Value on line C. This datapoint is a permanent signal (permanent
“detection mode” attribute not settable). To set IC Inrush detec SPS attributes, see section
• Inrush Blocking SPS is the instantaneous status for the blocking threshold for the three lines.
set Inrush Blocking SPS attributes, see section "Defining SPS datapoint" on page 690
- Figure 584 - [H2] inrush blocking sub-tree
7.5.16 Defining automation of protection functions

7.5.16.1 General
In the object view tree, the automation functions are associated with a relay (bay level). When
automation is added to a bay, a relay is automatically added as a sub-component.
The automation function contains the following operational components:

• 2 protections group,
• blocking protection,
• [50BF] breaker failure,
• cold load start,
• logic selectivity,
• maintenance,
C264/EN UM/E50.5 895

• miscellaneous,
• trip management.
7.5.16.2 General architecture

In the object view tree, the tree structure is used to present the protection functions.
- Figure 585 - Protection functions tree structure
Relay object is automatically created when a protection function is added to the bay. Relay does
not contain attribute and cannot be edited.
Each Protection function sub-tree contains a folder representing the associated thresholds . The
characteristics (as instantaneous, temporization, trip signal, and mode of operation) and the links
of each characteristic are settable.
7.5.16.2.1 Adding automation function

The addition of automation function is done under SCE via the “Object entry” area at bay level by
clicking on mouse’s right button or double clicking on the function.
To add automation function:

• Add the automation function from Objects entry (Built-in function, Relay built-in function sub-
tree) at bay level (1),
• The automation function (3) is added (Relay (2) is automatically added with the first protection
function),
• Update the function attributes: short name and long name (4).
- Figure 586 - Adding automation function
896 C264/EN UM/E50.5

7.5.16.3 Protection setting groups

7.5.16.3.1 Description
MiCOM C264 have two protection related setting groups named PROTECTION G1 and
PROTECTION G2. Only one of two setting groups is active.
Changes between the two groups are executed via a dedicated logic input, or through the
Ethernet communication port.
To avoid any undesirable tripping, the setting group change is only executed when none
protection function is running.
If a setting group change is received during any protection or automation function, it is stored and
executed after the last timer has elapsed.
7.5.16.3.2 Setting “2 protection group” automation functions

The “2 protection group” function sub-tree contains two datapoints:
• active prot. grp SPS indicates the active protection number (group 1 or group 2). This input is
a permanent signal (the permanent “detection mode” attribute cannot be modified). To modify
active prot. grp SPS attributes, see section "Defining SPS datapoint" on page 690
• set active group: SPC is the setting active group control. The activation mode of this control is
set to permanent. To set ‘general’ and ‘dependencies’ attributes of the set active group SPC,
see section "Defining SPC datapoint" on page 700
- Figure 587 - Setting ‘2 protection group’
section "Linking a datapoint to a profile" on page 708
7.5.16.4 [50BF] breaker failure

Following the inception of a fault one or more main protection devices will operate and issue a trip
output to the circuit breaker(s) associated with the faulted circuit. Operation of the circuit breaker
is essential to isolate the fault, and prevent damage or further damage to the power system.
C264/EN UM/E50.5 897

For transmission and sub-transmission systems, slow fault clearance can also threaten system
stability. It is therefore common practice to install circuit breaker failure protection [50BF], which
monitors that the circuit breaker has opened within a reasonable time. If the fault current has not
been interrupted following a set time delay from circuit breaker trip initiation, breaker failure
protection (CBF) will operate.
CBF operation can be used to back-trip upstream circuit breakers to ensure that the fault is
isolated correctly. CBF can also operate to reset all start output contacts, by external logic,
ensuring that any blocks asserted on upstream protection are removed.
7.5.16.4.2 Setting “[50BF] breaker failure” automatism functions

The “[50BF] breaker failure” function sub-tree contains two datapoints:
• break fail SPS (2) is the breaker failure status. This input is a permanent signal (permanent
“detection mode” attribute cannot be modified). To modify break fail SPS attributes, see
section .
• break fail mode MPS (3) is the breaker failure mode control. All the attributes can be modified.
To modify break fail mode MPS attributes, see section "Defining MPS datapoint" on page
692.
- Figure 588 - Setting ‘[50BF] breaker failure’
setting.
898 C264/EN UM/E50.5

7.5.16.5 Blocking protection

The directional, non directional overcurrent and overcurrent protection are applicable for radial
feeder circuits where there is little or no back feed.
This application shows that the upstream IDMT relay being blocked by the start output from a
downstream relay that has detected the presence of a fault current, which is above its threshold
settings. Thus both the upstream and downstream relays can then have the same current and the
blocking feature will automatically provide time settings and grading. If the CB failure protection
function is active, the blocking order on the upstream relay will be removed if the downstream
circuit breaker fails to trip.
7.5.16.5.2 Setting ‘Blocking protection’ automation functions

The “Blocking protection” function sub-tree contains four datapoints:
• bloc CO status SPS is the blocking protection command status input. This input is a
permanent signal (the permanent “detection mode” attribute cannot be modified). To modify
bloc CO status SPS attributes, see section "Defining SPS datapoint" on page 690
• bloc DI status SPS is the blocking protection digital input status. This input is a permanent
signal (the permanent “detection mode” attribute cannot be modified). To modify bloc DI
status SPS attributes, see section "Defining SPS datapoint" on page 690
• block protection SPC is the blocking protection control. The activation mode of this control is
set to permanent. To set ‘general’ and ‘dependencies’ attributes of the block protection SPC,
see section "Defining SPC datapoint" on page 700
• DI bloc SPS is the digital input blocking status. This input is a permanent signal (the
permanent “detection mode” attribute cannot be modified). To modify DI block SPS attributes,
see section "Defining SPS datapoint" on page 690
- Figure 589 - Setting ‘Blocking protection’
C264/EN UM/E50.5 899

7.5.16.6 Cold load start

In a protective relay, the Cold Load Pick-up feature enables the selected settings to be changed to
react to temporary overload conditions that may occur during cold load starts.
This condition may occur by switching on large heating loads after a sufficient cooling period, or
loads that draw high initial starting currents.
When a feeder is energized, the current levels that flow for a period of time following energizing
may differ greatly from the normal load levels. Consequently, overcurrent settings that have been
applied to give short circuit protection may not be suitable during this period.
The Cold Load Pick-up logic raises the settings of selected stages for a set duration. This allows
the protection settings to be set closer to the load profile by automatically increasing them after
energizing.
7.5.16.6.2 Setting ‘Cold load start’ automation function

The “Cold load start” function sub-tree (1) contains two datapoints:
• cls DI status SPS (2) is the status of the cold load start digital input status. This input is a
permanent signal (the permanent “detection mode” attribute cannot be modified). To modify
cls DI status SPS attributes, see section "Defining SPS datapoint" on page 690
• DI CLS SPS (3) is the cold load start digital input status. This input is a permanent signal (the
permanent “detection mode” attribute cannot be modified). To modify DI CLS SPS attributes,
- Figure 590 - Setting ‘cold load start’
7.5.16.7 Logic selectivity

The Logic selectivity is used in non-cascade protection schemes, using the start contacts from
downstream relays to block operation of upstream relays.
900 C264/EN UM/E50.5

In the case of selective overcurrent logic, the start contacts are used to increase the time delays of
upstream relays, instead of blocking them. This provides an alternative approach to achieving a
non-cascade type of overcurrent scheme. It may be more familiar to some utilities than the
blocked overcurrent arrangement.
The selective overcurrent logic function temporarily increases the time delay settings of the
second and third stages of phase overcurrent.
7.5.16.7.2 Setting ‘Logic selectivity’ automation function

The “logic selectivity” function sub-tree (1) contains four datapoints:
• DI sel SPS (2) is the digital input selectivity status. This input is a permanent signal (the
permanent “detection mode” attribute cannot be modified). To modify DI sel SPS attributes,
• log. selectivity SPC (3) is the logic selectivity control. The activation mode of this control is set
to permanent. To set ‘general’ and ‘dependencies’ attributes of the log. selectivity SPC, see
section "Defining SPC datapoint" on page 700
• sel CO status SPS (4) is the logic selectivity command status. This input is a permanent
signal (the permanent “detection mode” attribute cannot be modified). To modify sel CO
status SPS attributes, see section "Defining SPS datapoint" on page 690
• sel DI status SPS (5) is the logic selectivity digital input status. This input is a permanent
signal (the permanent “detection mode” attribute cannot be modified). To modify sel DI status
SPS attributes, see section "Defining SPS datapoint" on page 690
- Figure 591 - Setting ‘logic selectivity’
7.5.16.8 Maintenance
The maintenance mode allows the user to verify the operation of the protection functions without
sending any external order (tripping or signaling).
C264/EN UM/E50.5 901

The maintenance function is used when the selection or the end of the maintenance mode is
possible by logic input or control command.
7.5.16.8.2 Setting ‘Maintenance’ automatism menu

The “Maintenance” function sub-tree (1) contains two datapoints:
• maintenance SPS (2) is the maintenance status. This input is a permanent signal (the
permanent “detection mode” attribute cannot be modified). To modify maintenance SPS
attributes, see section "Defining SPS datapoint" on page 690 ,
• maintenance mode SPC (3) is the control of the mode of maintenance. The activation mode
of this control is set to permanent. To set ‘general’ and ‘dependencies’ attributes of the
maintenance mode SPC, see section "Defining SPC datapoint" on page 700.
- Figure 592 - Setting ‘Maintenance’
setting.
7.5.16.9 Miscellaneous
The “Miscellaneous” subtree contains the following operational automation functions:
• digital input start disturbance status,
• frequency protection status,
• protection state status,
• Reset thermal status control,
902 C264/EN UM/E50.5

• start disturbance control,
• synthesis of instantaneous fault signals status,
• synthesis of temporization signals status,
• synthesis of trip signals status.
7.5.16.9.2 Setting ‘Miscellaneous’ automation menu

The “Miscellaneous” function sub-tree (1) contains by default the following datapoints:
• DI start disturb SPS (start disturbance digital Input status). This input is a permanent signal
(permanent “detection mode” attribute not settable). To modify DI start disturb SPS attributes,
• Feq 81 invalid SPS corresponds to frequency invalid (overfrequency, underfrequency or out
of range frequency) status. This input is a permanent signal (the permanent “detection mode”
attribute not settable). To modify Feq 81 invalid SPS attributes, see section "Defining SPS
datapoint" on page 690 .
• protection state MPS (protection state status). All the attributes can be modified. To modify
protection state MPS attributes, see section "Defining MPS datapoint" on page 692.
• reset thermal st SPC (thermal reset status). The activation mode of this control is set to
permanent. To set ‘general’ and ‘dependencies’ attributes of the reset thermal st SPC, see
section "Defining SPC datapoint" on page 700.
• start dist ctrl SPC (start disturbance control). The activation mode of this control is set to
permanent. To set ‘general’ and ‘dependencies’ attributes of the start dist ctrl SPC, see
section "Defining SPC datapoint" on page 700 .
• synthesis inst. SPS (Synthesis of instantaneous). This input is a permanent signal (the
permanent “detection mode” attribute not settable). To modify synthesis inst. SPS attributes,
• synthesis temp. SPS (Synthesis of temporisation). This input is a permanent signal (the
permanent “detection mode” attribute not settable). To modify synthesis temp. SPS attributes,
• synthesis trip SPS (Synthesis of trip). This input is a permanent signal (the permanent
“detection mode” attribute not settable). To modify synthesis trip SPS attributes, see section
C264/EN UM/E50.5 903

- Figure 593 - Setting ‘Miscellaneous’
7.5.16.10 Trip management

The trip management corresponds to trip relay control and trip status.
7.5.16.10.2 Setting ‘Trip management’ automation menu

The “Trip management’” function sub-tree (1) contains eight datapoints (2):
• 3 SPCs (trip #1 ctrl, trip #2 ctrl and trip #3 ctrl) to control the relay
• 3 SPSs (trip #1 status, trip #2 status et trip #3 status) to monitor the status of the relay
• 1 trip relay ctrl and 1 trip status used for backward compatibility.
The activation mode of each SPC is set to permanent and cannot be modified. To set ‘general’
and ‘dependencies’ attributes, see section "Defining SPC datapoint" on page 700.
The detection mode attribute is set to permanent and cannot be modified. To modify trip status
SPS attributes, see section "Defining SPS datapoint" on page 690.
Assign a specific existing profile to each datapoint. See section "Linking a datapoint to a profile"
on page 708, for details about profile definition and setting.
Execute the auto-addressing.
904 C264/EN UM/E50.5

- Figure 594 - Setting ‘trip management’
C264/EN UM/E50.5 905

7.6 Defining MiCOM C264 Local HMI

All kinds of computers (except C364), can have a GHU2xx board for led managing and possible
local bay mimic panel animations in case of complete GHU2xx board (refer to section "Setting
specific features of the GHU2xx board" on page 579).
7.6.1 Defining a bitmap table

To define computer bay mimics, bitmaps are used. Their definition is located at graphic root of the
data modeling.
At computer bay mimic definition level, objects only reference these bitmaps. So, it is an easier
way to propagate a bitmap change for instance to all objects that reference it.
At SCE level, bitmap object definition is extended to embed animation: up to 5 elementary static
bitmaps can be grouped in a bitmap object:
• one (mandatory) for default representation
• one for ‘open’ (or reset) representation
• one for ‘closed’ (or set) representation
• one for ‘open withdrawn’ representation
• one for ‘closed withdrawn’ representation
Each representation corresponds to a filename containing the static bitmap definition.
The addition of a bitmap definition is done via the “Objects entry” window at Bitmap table level of
the graphical topology by clicking on mouse’s right button.
- Figure 595 - Adding a bitmap
Once added, bitmap attributes must be set at SCE level:

• short name and long name: used for internal SCE identification.
• reference index (range [0, 150]: that must be unique for the set of defined bitmaps. This index
will be used in bay mimic definition as described previously.
906 C264/EN UM/E50.5

• type (Single / 5-uple): single is used for static bitmap definition, 5-uple allows dynamic bitmap
definition as described previously.
• file name by default: corresponds to the filename containing the bitmap definition used for
default representation.
• file name for 'open' state: visible only if type is set to 5-uple: corresponds to the filename
containing the bitmap definition used for open state representation.
• file name for 'closed' state: visible if type is set to 5-uple: corresponds to the filename
containing the bitmap definition used for closed state representation.
• file name for 'withdrawn open' state: visible if type is set to 5-uple: corresponds to the filename
containing the bitmap definition used for withdrawn open state representation.
• file name for 'withdrawn closed' state: (visible if type is set to 5-uple): corresponds to the
filename containing the bitmap definition used for withdrawn closed state representation.
- Figure 596 - Setting bitmap attributes
Attributes (7) and (8) can be omitted if breakers and switchgears represented in bay mimic are not
concerned with withdrawn information.
To set a file name (attributes (4) to (8)) and define graphically a bitmap:
• select the attribute
• edit graphically a bitmap using the bitmap editor at SCE level
• save the graphical definition of the bitmap by giving a file name in bitmap editor
For details about bitmap editor usage refer to SCE user’s manual.
C264/EN UM/E50.5 907

- Figure 597 - Using bitmap editor
Color usage in bitmap editor is not significant for computer monochrome LCD.

• The "reference index" attribute value of each "Bitmap" of the "Bitmap table" must be unique.
• Depending on the "type" attribute value, 1 or 5 PNG file(s) can be linked to a Bitmap.
For each one, the bitmap size must be ≤ 512 bytes.
7.6.2 Defining a computer workspace

Via a complete GHU2xx board (refer to section "Setting specific features of the GHU2xx board" on
page 579), each computer with local HMI references a workspace that groups its bay mimic
definitions. Computer workspaces can not be shared by several computers because mimics are
local to bays managed by a specific computer.
Up to 24 bay mimics can be put in a computer workspace, and up to 2 mimics can be linked to the
same bay.
Usual labels are used by computer local HMI (LHMI). They are located for all computers LHMI in
one object grouping all translatable labels, located in “computer workspaces” folder in Graphic
topology.
7.6.2.1 Settings LHMI labels

It is possible to customize data model information (labels and values) which is displayed in the
front panel LHMI. For this, there is an embedded dictionary in the SCE accessible when selecting
the “LHMI labels” item. Each tab contains a category of labels.
For example, for the cyber security the login and banner panel titles can be changed as shown in
the following figure:
908 C264/EN UM/E50.5

- Figure 598 - Setting LHMI labels - login and banner panel titles
To define labels of login, 17 characters are available (only 10 in case of Chinese language).
The CYBER SECURITY tab is used to customize the warning and security log labels:
C264/EN UM/E50.5 909

- Figure 599 - Setting LHMI labels - cybersecurity tab
7.6.2.2 Creating a workspace

The addition of a workspace is done via the Objects entry window at graphic level by clicking on
the mouse’s right button. Once added, computer workspace general features must be set:
• Define which GHU2xx board is concerned by created workspace by filling the relation has for
workspace at concerned GHU board level (refer to section "Setting specific features of the
GHU2xx board" on page 579).
• Define the short and long name attributes of the workspace used for internal SCE id:
- Figure 600 - Adding a computer workspace
7.6.3 Defining a computer bay mimic

7.6.3.1 Creating a computer bay mimic
The addition of a computer bay mimic is done via the “Objects entry” window at computer
workspace level by clicking on mouse’s right button.
910 C264/EN UM/E50.5

- Figure 601 - Adding a computer bay mimic
Once added, bay mimic general attributes must be set at SCE level:
• short name of the bay mimic used for internal SCE identification.
• bargraph representation (none / Horizontal / Vertical): this attributes defines which

representation is used for bargraph associated to a MV datapoint assigned to a bay mimic
(refer to section Assigning MV to bay mimic).
• module name display (No / Yes) this attribute defines if module short names are displayed at
mimic level when a module is represented on bay mimic (refer to section Defining dynamic
part: pre-defined dynamic text, generic module representation, transformer representation).
• Fill the relation ‘represents’, giving which bay is represented by the mimic (for details about
bay refer to section "Defining a Bay" on page 758).
• If necessary, set the attribute ‘mimic rank’ of the ‘represents’ relation to correct value. This
attribute is used when 2 mimics are configured to display an entire bay: as bay is split in 2
representations, the ‘mimic rank’ attribute gives their display rank at computer LHMI level (1
or 2).
C264/EN UM/E50.5 911

- Figure 602 - Setting bay mimic features
When adding a bay mimic at workspace level, its core structure (canvas) is automatically created
and displayed at SCE level, via bay mimic editor and in SCE tree browser. Its core structure
consists of:
• Reserved zone for bay name display
• Reserved zone for bay local/remote display ((2’) in tree browser)
• Reserved zone for ‘interlocking bypass in progress’ information ((3’) in tree browser)
• Reserved zone for ‘synchrocheck bypass in progress’ information ((4’) in tree browser)
• Configurable zone for graphical representation of the bay (static and dynamic parts)
• Reserved zone for message
912 C264/EN UM/E50.5

- Figure 603 - Core structure of a bay mimic
For more details about computer LCD usage, refer to "Human Machine Interface" on page 498.
The configurable zone of a bay mimic can be split in two parts:

• A static part with no real-time animation
• A dynamic part with real-time animated representations.

• The computer managing a bay represented by a "Bay mimic" must be the same as the one
linked to the "Comp. workspace" (computer workspace) of this "Bay mimic".
C264/EN UM/E50.5 913

• A bay can be represented by 0, 1 or 2 "Bay mimic". Each "represents" relation has an attribute
"mimic rank for the set of bay mimic". In the case of 2 relations, each attribute value must be
unique.
• For a Computer, the maximum count of managed bays (relation "is managed by") which are
linked to a "Bay mimic" (relation "represents"), is 12.
• Limits of the count of symbols:
7.6.3.2 Defining static: part line, bitmap, fixed text

The static part of a computer bay mimic is described via graphical basic shapes:
• LHMI line: horizontal or vertical line with configurable thickness and length
• LHMI bitmap: bitmap that references a bitmap object in the bitmap table (see "Defining a
bitmap table" on page 906) where default representation is only taken into account
• Fixed text: multi-lingual fixed text
Once added, these elements automatically appear in the window of the bay mimic editor at SCE
level.

• The coordinates (x, y) of a symbol must not be located outside the mimic area.
7.6.3.2.1 Adding a line

The addition of a line in bay mimic is done via the “Objects entry” window at bay mimic level by
914 C264/EN UM/E50.5

- Figure 604 - Adding a line in computer bay mimic
Once added, line attributes must be set at SCE level:

• short name of the line used for internal SCE identification
• x (range [0, 127 pixels], step 1 pixel): abscissa
• y (range [0, 127 pixels], step 1 pixel): ordinate
• length (range [1 pixel, 127 pixels], step 1 pixel)
• orientation (Horizontal / Vertical)
• thickness (range [1 pixel, 8 pixels], step 1 pixel)
- Figure 605 - Setting line attributes
Abscissa, ordinate, length and thickness of a LHMI line can be directly adjusted with the mouse in
bay mimic editor (for detail, refer to SCE user’s manual)
C264/EN UM/E50.5 915

7.6.3.2.2 Adding a bitmap

The addition of a bitmap in bay mimic is done via the “Objects entry” window at bay mimic level by
- Figure 606 - Adding a bitmap in computer bay mimic
Once added, bitmap attributes must be set at SCE level:

• short name of the line used for internal SCE identification
• bitmap reference: corresponds to a link in the bitmap table (refer to section "Defining a bitmap
table" on page 906)
Abscissa and ordinate of a bitmap can be directly adjusted with the mouse in bay mimic editor (for
detail, refer to SCE user’s manual)
916 C264/EN UM/E50.5

• The link from an element to its bitmap is defined with the attribute "bitmap reference". The
value of this attribute must refer to an existing bitmap in the "Bitmap table".
7.6.3.2.3 Adding a fixed text

The addition of a fixed text in bay mimic is done via the “Objects entry” window at bay mimic level
by clicking on mouse’s right button.
- Figure 608 - Adding a fixed text in computer bay mimic
Once added, fixed text attributes must be set at SCE level:

• 1. fixed text value: text to display at mimic level
• 2. x (range [0, 127 pixels], step 1 pixel): abscissa
• 3. y (range [0, 127 pixels], step 1 pixel): ordinate
Abscissa and ordinate of a fixed text can be directly adjusted with the mouse in bay mimic editor
(for detail, refer to SCE user’s manual). Text area length at bay mimic is automatically deduced
from text value length (attribute (1)).
C264/EN UM/E50.5 917

7.6.3.3 Defining dynamic part: pre-defined dynamic text, generic module

representation, transformer representation
To define dynamic part of computer bay mimics, 3 kinds of objects are available:
• Pre-defined dynamic text, used:
to display local/remote and SBMC status of the bay
to manage Synchrocheck and interlock bypass during control sequence on the bay
to display time and synchronization status
Generic module representation: used to display module status, linked to a specific SPS or DPS
electrical datapoint. Implicit link to possible xPC associated datapoint is given to computer for
command purpose at local HMI level, via the existence of the relation ‘is feedback of’ between the
xPS and the xPC.
• A generic module is composed of 2 sub-objects:
a name for display (mandatory)
a ‘xPS muti-state’ for dynamic module state display (mandatory), referencing a dynamic
bitmap object in the bitmap table, and whose relation to a xPS datapoint (SPS or DPS)
has to be filled up to precise animation datapoint
• Transformer representation: used to display transformer module; linked to an optional Tap
Position Indicator. Transformer is composed of 5 sub-objects:
a name for display (mandatory)
a ‘TPI muti-state’ for transformer display (mandatory), referencing a dynamic bitmap

object in the bitmap table, and whose relation to a TPI datapoint can be filled up to precise
the concerned datapoint for the following animation
an optional ‘current TPI value’ object to display dynamically the current value of the TPI,
an optional ‘max TPI value’ object to display upper available value for the TPI
an optional ‘min TPI value’ object to display lower available value for the TPI
7.6.3.3.1 Adding time information

The addition of the time information in bay mimic is done via the “Objects entry” window at bay
mimic level by clicking on mouse’s right button.
918 C264/EN UM/E50.5

- Figure 610 - Adding time information in computer bay mimic
Once added, time information attributes must be set at SCE level:

• short name of the time information area used for internal SCE identification
- Figure 611 - Setting time information attributes
Abscissa and ordinate of time information can be directly adjusted with the mouse in bay mimic
editor (for detail, refer to SCE user’s manual)
7.6.3.3.2 Positioning Local/Remote status, Synchrocheck bypass or Interlock bypass

When creating a bay mimic, the following objects are implicitly created in the mimic at a pre-
defined location:
• Interlock bypass ‘button’(EQL BP object)
• Local/remote status (L/R object)
• Synchrocheck bypass ‘button’ (S/C BP object)
Depending on customer’s need, these data can be positioned at a different location:
C264/EN UM/E50.5 919

• directly by using mouse drag and drop in bay mimic editor
• by editing the abscissa and ordinate attributes of the object
- Figure 612 - Positioning pre-defined text information in bay mimic
7.6.3.3.3 Adding SBMC information

The addition of the SBMC information in bay mimic is done via the “Objects entry” window at bay
mimic level by clicking on mouse’s right button.
- Figure 613 - Adding SBMC information in computer bay mimic
Depending on customer’s need, SBMC information can be positioned at any location in bay
mimic:
• by editing the coordinates of the object
920 C264/EN UM/E50.5

7.6.3.3.4 Adding a generic module representation

In bay mimic, ‘LHMI Gen module’ is used for module dynamic representation. A ‘LHMI Gen
module’ is a graphical group constituted of:
• the dynamic representation itself (LHMI Gen module), that is linked to SPS or DPS datapoint
and to a dynamic bitmap in bitmap table
• the graphical name of the module (Name), always located on the right of the module
representation
The addition of a generic module representation in bay mimic is done via the “Objects entry”
window at bay mimic level by clicking on mouse’s right button.
- Figure 614 - Adding a generic module in computer bay mimic
Once added, the representation features must be set at SCE level:

• short name of the representation used for internal SCE identification
• control availability (No / Yes): attribute to precise if control of the module can be directly done
via bay mimic. This attribute is significant if SPS/DPS linked to the generic module
representation (via (5) relation) is feedback of a control SPC or DPC. If so, control availability
concerns this SPC/DPC
• Relation ‘is managed by’ that must be filled to precise which SPS or DPS is used for bitmap
animation
• multi-bitmap reference: corresponds to a link in the bitmap table (refer to section "Defining a
C264/EN UM/E50.5 921

bitmap table" on page 906)

• module name value: text displayed on LCD (up to 4 characters)
- Figure 615 - Setting features of generic module representation
Coordinates (x and y) of a generic module can be directly managed by using mouse in bay mimic
editor (for detail, refer to SCE user’s manual).

• The link from an element to its bitmap is defined with the attribute: "bitmap reference". The
• The "Bitmap" linked to a "LHMI xPS MultiSt" MultiState must be defined as follows:
- its "type" attribute must be set to "5-uple" value
-its 3 first file names { "file name by default", "file name for 'open' state", "file name for 'closed'
state" } are mandatory and each one must be unique.
Furthermore, if the MultiState is linked to a SPS or DPS datapoint of a module containing a
"Withdrawn" SPS datapoint, through the "is managed by" relation, then the following
constraints are added to the "Bitmap" definition:
- its 2 file names { "file name for 'withdrawn open' state", "file name for 'withdrawn closed'
state" } are both mandatory and each one must be unique.
922 C264/EN UM/E50.5

7.6.3.3.5 Adding a transformer representation

In bay mimic, ‘LHMI Transformer’ is used for dynamic transformer representation. A ‘LHMI
transformer’ is a graphical group constituted of:
• the dynamic representation itself (LHMI Gen module), that is linked to SPS or DPS datapoint
and to a dynamic bitmap in bitmap table
• the graphical name of the module (Name), always located on the right of the module
representation
The addition of a transformer representation in bay mimic is done via the “Objects entry” window
at bay mimic level by clicking on mouse’s right button.
- Figure 616 - Adding a generic module in computer bay mimic
Once added, the representation features must be set at SCE level:

• short name of the representation used for internal SCE identification.
• control availability (No / Yes): attribute to precise if control of the transformer can be directly
done via bay mimic. This attribute is significant if Raise/Lower DPC control exists for Tap
changer built-in function containing the TPI datapoint used for transformer animation (via (5)
relation). If so, control availability concerns this DPC.
• Relation ‘is managed by’ that must be filled to precise which TPI is used for transformer
animation.
• bitmap reference: corresponds to a link in the bitmap table (refer to section "Defining a bitmap
C264/EN UM/E50.5 923

table" on page 906).

• module name value: name of the transformer: text displayed on LCD (up to 4 characters).
- Figure 617 - Setting features of transformer representation
Abscissa and ordinate of a transformer can be directly adjusted with the mouse in bay mimic
editor (for detail, refer to SCE user’s manual)
When adding a transformer representation, extra values about associated TPI datapoint can be
placed in the bay mimic:
• Current TPI value (dynamic)
• Maximal TPI value
• Minimal TPI value
The addition of such TPI information in bay mimic is done via the “Objects entry” window at
transformer representation level by clicking on mouse’s right button.
924 C264/EN UM/E50.5

- Figure 618 - Adding a TPI information in computer bay mimic
Once added, TPI information can be positioned at a different location:

• by editing the X-coordinate and Y-coordinate attributes of the object

• The link from an element to its bitmap is defined with the attribute: "bitmap reference". The
7.6.3.4 Assigning MV to bay mimic

A MV datapoint can be assigned to a specific bay mimic by adding the ‘visualizes’ relation at bay
mimic level and assigning it to the MV.
- Figure 619 - Assigning MV datapoint to bay mimic
Case 1: CT/VT measurement acquired by a TMU board and which type is: Van, Vbn, Vcn, Vr,
Vab, Vbc, Vca, Ia, Ib, Ic or Ir.
C264/EN UM/E50.5 925

In this case a bargraph is used to represent the ratio between the MV value (after scaling) and the
nominal value which is configured at the TMU board level.
Bargraph value (%) = (MV value / nominal value) x 100
Therefore, once the ‘visualizes’ relation is added and assigned to the MV, the ‘scale’ attribute of
the relation must be chosen:
• scale (120% / 200% / No bargraph): precise the bargraph maximum value which can be
displayed by the bargraph.
- Figure 620 - Setting MV representation in bay mimic
- Figure 621 - TMU board nominal values used by the MV bargraph
Case 2: other measurements (CT/VT measurements not listed in Case 1 or any other kind of
measurements)
926 C264/EN UM/E50.5

In this case there is no bargraph displayed at runtime. The MV value is displayed instead of the
bargraph value %. Therefore, there is no need to configure the ‘scale’ attribute of the ‘visualizes’
relation.

• A MV datapoint visualized in a "Bay mimic" (relation "visualizes") must belong to the bay
represented by the "Bay mimic" (relation "represents").
• For each visualized MV datapoint, the "transmission on event" attribute must be set neither to
"Cyclic short period" value nor to "Cyclic long period" value to avoid overflow of the Bay mimic
input buffer.
7.6.4 Defining the generic measurements panel

7.6.4.1 Defining the presence of the main and secondary pages
The generic measurements panel contains one main and several secondary pages. Their
presence is not configured explicitly but it depends if there are measurements assigned to it or
not.
If there is no measurement assigned to it then the page is considered as empty and it is not
displayed. The only exception is when there is gap between the index of the used pages (pages
having associated MVs) then the not used pages are empty but displayed. This can occur when
setting all the MVs of a page as spare.
7.6.4.2 Defining the MV display options

The configuration of these pages resides entirely on the MV objects attributes.
Every MV object has a “Display” tab with attributes for associating the MV to a page as well as the
MV display type and order.
- Figure 622 - Display options
The different attributes of this tab are detailed here after:

• Display type: four possible values are available:
Not displayed: the MV is not displayed in any of the pages of the panel.
Main MV: the MV is displayed in the main MV area of the main page.
Only one main MV is allowed per MiCOM C264.
C264/EN UM/E50.5 927

Scroll MV: the MV is assigned to a scroll MV group and will be displayed in the scroll MV
area of the main page.
Fixed MV: the MV can be displayed in the fixed MV area of any page (main or secondary
pages).
• Display page: this attribute is only available if the display type is Scroll MV or Fixed MV.
However, the meaning of this attribute differs depending on the display type chosen.
For Fixed MV: it represents the page number where the measurement will be displayed (1
for the main page, 2 for the first secondary page, up to 4 for the third secondary page).
For Scroll MV: it represents the scroll group number to which the MV will be associated to.
Min. Max.
If Display type =
Scroll MV
1 6
(display page
Display means group)
page If Display type =
range Fixed MV
(display page 1 4
means page
number)
• Display order: this attribute is only available if the display type is Scroll MV or Fixed MV.
For Fixed MV: it is the display position within the fixed MV area. It must be different for all
the fixed MVs of the same page.
For Scroll MV: it is the display position within the scroll MV group area. It must be different
for all the scroll MVs of the same group.
The positions are always respected as defined even if they are not contiguous.
For example, if an MV is assigned to position 2 but there is no MV assigned to position 1,

then the position 1 will be left as blank.
In this way, if a MV is set as spare, a blank will be left in its defined position.
Min. Max.
Display type =
1 3
Scroll MV
Display type =
Display Fixed MV and 1 2
order range Display page = 1
Display type =
Fixed MV and 1 7
Display page ≠ 1
The following figure shows an example of how these attributes are used:
928 C264/EN UM/E50.5

- Figure 623 - MV display options example
7.6.4.3 MV Bargraph
The bargraph presence is not configurable it is always displayed in all the pages.
The MV association to the bargraph is done automatically at first MiCOM C264 start-up (the first
MV found in the first displayed page). The user can change the association at runtime at any time.
The bargraph % value is computed from based on the minimum and maximum values of the MV
associated at runtime:
• The “maximum value” represents the 0% of the bargraph.
• The “maximum value” represents the 100% of the bargraph.
- Figure 624 - Relation between the bargraph and MV values attributes
7.6.5 Displaying datapoint status with Led

SPS and DPS datapoint status can be displayed via leds of GHU200 board by adding the relation
‘has state displayed on’ at datapoint level (1). Only datapoint managed by computer can be
displayed via the Leds of its GHU2xx board.
C264/EN UM/E50.5 929

- Figure 625 - Displaying datapoint status with led (e.g. for bay SPS datapoint)
Once added at SPS (resp. DPS) level, the relation must be filled with the relevant associated led
and the following relation attributes should be updated:
• Led status for ‘Set’ state (resp 'Closed'): ( Off / On / Blinking slow / Blinking fast)
• Led status for ‘Reset’ state (resp 'Open'): ( Off / On / Blinking slow / Blinking fast)
• Led status for ‘Invalid’ state: ( Off / On / Blinking slow / Blinking fast)
- Figure 626 - Setting led status for a datapoint (e.g. for SPS datapoint)
Configuration and checks

• If the value of the "HMI type" attribute is "Simple", then "Led#4" must not be used (no relation
link from "Led#4" to a datapoint).
930 C264/EN UM/E50.5

MiCOM C264 - User Manual 8 Installation
8 Installation

8.1.1 MiCOM C264 933
8.1.2 Personal Computer 933
8.1.3 Communication wiring 933
8.2 Delivery reception 935
8.2.1 Packing inspection and opening 935
8.2.2 Delivery form checking 935
8.3 Mechanical mounting 936
8.3.1 Rack mounting 936
8.3.2 Panel mounting 936
8.4 Wiring installation 937
8.4.1 General wiring 937
8.4.2 Power supply wiring 937
8.4.3 I/O board wiring 937
8.4.4 Networks wiring 937
8.4.4.1 Serial communication 938
8.4.4.2 Optical communication 939
8.5 MiCOM C264 power up 940
8.6 MiCOM C264 installation 941
8.6.2 Prequisites 941
8.6.4 MiCOM C264 installation 943
8.6.4.2 Note for authentication certificate 943
8.6.4.3 MiCOM C264 installing from scratch 944
8.6.4.3.1 Establish computer connection with CAT 945
8.6.4.3.2 Set computer boot parameter to “Bootprom boot” mode 948
8.6.4.3.3 Update new release of VxWorks BOOTROM 949
8.6.4.3.4 Format flash memory of CPU 957
8.6.4.3.5 Update new release of MiCOM C264 application 959
8.6.4.3.6 Set computer boot parameter to “Flash boot” mode 963
8.6.4.4 MiCOM C264 updating 965
8.6.4.5 MiCOM C264 roll-back 965
8.6.5 CAT installation 966
8.6.5.2 Prequisites 966
8.6.5.4 CAT installing from scratch 966
8.6.5.4.1 Framework NET 3.5 SP1 installation 967
8.6.5.4.2 WinpCap 4.1.3 driver installation 968
C264/EN UM/E50.5 931

8 Installation MiCOM C264 - User Manual
8.6.5.4.3 CAT installation 970

8.6.5.5 CAT updating 973
8.6.5.6 CAT roll-back 973
8.6.6 CAT: How to use it? 974
8.6.6.1 Human Machine Interface 974
8.6.6.2 Language selection 974
8.6.6.3 Operator's record folders 975
8.6.6.4 Settings 975
8.6.6.5 Scan 975
8.6.6.6 Connection to a computer 979
8.6.6.7 Work pane 979
8.6.6.8 Modes and permitted operations 981
8.6.6.9 Routine operations 982
8.6.6.9.1 Display status and monitoring 982
8.6.6.9.2 Manage database (subject to privilege) 984
8.6.6.9.3 Edit settings (subject to privilege) 986
8.6.6.9.4 Manage events and states (subject to privilege) 986
8.6.6.9.4.1 Events 986
8.6.6.9.4.2 Latest datapoint values 989
8.6.6.9.5 Display errors and agency logs 990
8.6.6.9.6 Display AVR data 990
8.6.6.9.7 Waveforms 991
8.6.6.10 Expert Functions 992
8.6.6.10.1 Manage date and time (read, and change depending on profile) 992
8.6.6.10.2 Manage boot and network parameters 994
8.6.6.10.3 Manage communication ports 995
8.6.6.10.4 Load application software 996
8.6.6.10.5 Load bootrom software 996
8.6.6.10.6 Browse computer files 996
8.6.6.10.7 Launch a SSH session 997
8.6.6.11 REU board 997
8.6.6.11.1 REU Initial configuration with CAT 997
8.6.6.11.2 REU configuration with CAT 997
8.6.6.11.2.1 REU settings 997
8.6.6.11.2.2 REU firmware upgrade 1002
8.7 Uploading a security configuration with Cybersecurity Admin Expert 1004
8.8 Uploading database with CAT 1005
8.9 After computer installation 1006
8.10 Optional installation 1007
8.10.1 External master clock connection 1007
8.10.2 Printer installation 1007
932 C264/EN UM/E50.5

8.1 Requirements
MiCOM C264 boot setting and software installation is carried out using a Windows PC with
common utilities and serial/Ethernet link to the computer.
The EPAS Media System installation is needed to run the MiCOM C264’s install software on the
Host PC.
8.1.1 MiCOM C264

The MiCOM C264 needs at least
• CPU board CPU275 (CPU4)
• Power board BIU241
• Backplane FBP24x (for MiCOM C264 40TE), FPB26x (for MiCOM C264 60TE) or FBP28x
(for MiCOM C264 80TE)
The BIU241 needs to be correctly wired to its voltage level as described in chapter C264/EN CO
(Connections). Before any operational voltage is applied the shield wiring should be checked
following rules of chapters "Safety Information" on page 4 and "Safety and Handling" on page 55.
The CPU275 basically integrates factory parameters.
NOTE: The computer needs to be installed with the software that allows booting in flash.
Installation or reinstallation of BOOTPROM software in PROM is described in C264/EN MF
Maintenance chapter, and out of scope of this chapter.
Before starting installation, the following information is required:

• Computer IP address
• Computer alias name
Both parameters are also defined in computer database. If parameters inside database differ from
the CPU settings, the IEC 61850 communication with others EPAS equipment will not be
possible.
8.1.2 Personal Computer

A Personal Computer is used for setting and download. The required Windows Operating System
is Windows® 10 Enterprise Build 1809 LTSC.
Note: For earlier EPAS release Operating System requirements, please refer to related EPAS
release documentation.
The PC hardware requirement is:

• Ethernet port 10 Mb/s or 100 Mb/s
• 100 Mb of free space on hard disk
The PC software's needed is:

• Computer package named Computer_X.YZ.exe (X.YZ is the computer version)
8.1.3 Communication wiring

The link between PC and MiCOM C264 is Ethernet.
C264/EN UM/E50.5 933

For a direct connection (without Ethernet Switch) between the PC and the MiCOM C264, a
crossed wire is required.
934 C264/EN UM/E50.5

8.2 Delivery reception

Delivery reception is composed of:
• Packing inspection and opening
• Delivery form checking
• Feeling up commissioning
8.2.1 Packing inspection and opening

On receipt of the unit, inform the delivery agent if there is any sign of damage.
Check the box for documentation, or computer hardware option added in the delivery form like
ribbon, screws, port extension etc.
8.2.2 Delivery form checking

The delivery form is based on the order form issued from CORTEC. It lists computer type, boards
(with supply, serial numbers and position in the rack) and options.
Verify that the composition of the device is as ordered.
Computer is delivered with the required connectors.
C264/EN UM/E50.5 935

8.3 Mechanical mounting

The section "Hardware" on page 393 gives the size of MiCOM C264 rack, the fixation diameters
and their position.
If electric screwdriver is used the torque limitation should be set to the small diameters of the
screws.
The MiCOM C264 can be mounted in racks or panel.
8.3.1 Rack mounting

MiCOM C264 may be rack mounted using single tier rack frames (our part number is FX0021
001):
- Figure 627 - Rack mounting
These frames have been designed to have dimensions in accordance with IEC 60297 and are
supplied pre-assembled ready to use.
The two horizontal rails of the rack frame have holes drilled at approximately 26mm intervals and
MiCOM C264 cases are attached via their mounting flanges using M4 Taptite self-tapping screws
with captive 3 mm thick washers to ensure a good earth contact (our part number is ZB5865250).
It is possible to install two MiCOM C264 40TE side by side on the assembly panel or one
MiCOM C264 80TE.
Ensure that the computers are earthed, using the screw terminal on the rear of the unit.
8.3.2 Panel mounting

MiCOM C264 can be flush mounted into panels using M4 Taptite self-tapping screws with captive
3 mm thick washers to ensure a good earth contact (our part number is ZB5865250).
Alternatively, tapped holes can be used if the panel has a minimum thickness of 2.5 mm.
Where several MiCOM C264 are to be mounted in a single cut-out in the panel, it is advised that
they are mechanically grouped together horizontally and/or vertically to form rigid assemblies
prior to mounting in the panel.
NOTE: It is not advised that MiCOM C264 are fastened using pop rivets as this will not allow the
device to be easily removed from the panel in the future if repair is necessary.
936 C264/EN UM/E50.5

8.4 Wiring installation

Wiring has to be prepared before installation. The MiCOM C264 is delivered with required
connectors for I/O boards and Ethernet switches. The wire diameters stated in chapter C264/EN
CO are mandatory. Tighten the screws in a cross pattern (e.g. top left, then bottom right etc), take
care not to over torque the screws.
8.4.1 General wiring

Only two wires can be screwed together on any one MiCOM connector. The AC and DC
analogues, digital signal, and communication wires should use separate shielded cable.
From a practical point of view the power supply of each computer should have a switch (MCB,
link, or fuse) to turn off the power during installation and commissioning tests.
The MiCOM C264 description sheet describes the type of board Installed on each slot (C, D etc.)
It is very important to use it to correctly plug the connectors.
Connection diagrams of the MiCOM C264 are given in chapter "Hardware" on page 393. Wires
should be connected with the connector unplugged. Each wired signal has to be tested before
plugging and fixing the connectors. The connectors have to be fixed on the MiCOM C264 case
with the screws available at each extremity of the connector.
For connection of the protective (earth) conductor please refer to the topic "Connection of the
protective conductor (Earth)" on page 418.
8.4.2 Power supply wiring

The BIU connector wiring is vital as it provides the power supply. Power voltage should be tested
and checked to BIU reference defined in chapter "Hardware" on page 393 to ensure that supply is
compliant to BIU voltage.
The power has to be switched off before plugging in the connector.
8.4.3 I/O board wiring

Several DIU, CCU, BIU board voltage are available for Digital Input. Check that the DIU voltage
as stated on the delivery form matches with the nominal signal input before plugging connector to
the computer.
DOU and CCU boards generate Digital Output with a defined inductive characteristic. On the
other side of the wire the inductance should be compliant. To avoid damage to the DO board
connected to inductive circuits it may be necessary to connect an anti-surge diode.
8.4.4 Networks wiring

Network wiring can be optical fiber or copper.
If the IEDs or remote equipment (like Control Center, printer, etc) are located at a long distance
(>10 m for RS232, >100 m for RS422 and >1000 m for RS485) from the communication
equipment or if the cables run through a noisy area, then optical fiber communication should be
used.
Copper networks should follow class recommendation and shielding.
Copper Ethernet network have to stay inside a cubicle. Optical fiber has to be used between
cubicles.
C264/EN UM/E50.5 937

8.4.4.1 Serial communication

The “Daisy Chain or “straight line” configuration is recommended and the correct way to construct
field bus.
- Figure 628 - Daisy chain on serial communication link - sample
A “Star” or a network with “Stubs (Tees)” is not recommended as reflections within the cable may
result in data corruption: avoid to connect more than two wires to each terminal, this ensures that
a “Daisy Chain or “straight line” configuration is used.
- Figure 629 - Not commanded wiring on serial communication link
When using a Legacy bus (with IED mounted in daisy chain), the correct resistor, at both ends
only, should be fitted (120 ohms for RS 422 and RS 485).
938 C264/EN UM/E50.5

- Figure 630 - Daisy chain on serial communication link - resistors
The wiring recommendation for RS 422 is as follows:
Master (MiCOM C264) Slave (IED)

TA(+) R+
TB(-) R-
RA(+) T+
RB(-) T-
8.4.4.2 Optical communication

Optic fiber communication is an option and should be ordered as such along with the required
mechanical modules. Specific care should be taken with the bend radius of the fibers, and the use
of optical shunts is not recommended as these can degrade the transmission path over time.
For the use of SWR20x or SWD20x, the optical ring has to be connected as follows:
- Figure 631 - Optical ring connection with SWR20x or SWD20x
C264/EN UM/E50.5 939

8.5 MiCOM C264 power up

The MiCOM C264 as delivered has the following installed:
• Bootrom start-up software
• Factory Start-up Setting
Before powering up the computer all the DI/DO board connectors should be disconnected.
Tests are described in the section "Commissioning" on page 1119 to check that the computer with
its factory settings has not suffered damage during transport.
940 C264/EN UM/E50.5

8.6 MiCOM C264 installation

8.6.1 Introduction
This section describes procedures in order to Install, Update and Roll-back MiCOM C264
software with Cyber Security features or standard installation (without cyber-security).
Use Case Comment

"MiCOM C264 installing from scratch" on page Operator needs to install new release
944 compliant to MiCOM C264.
Operator needs to update new release
"MiCOM C264 updating" on page 965 compliant to MiCOM C264.
Operator needs to Roll-back (upgrade with

"MiCOM C264 roll-back" on page 965 previous release).
NOTE: This section describes MiCOM C264 upgrading from release B7.21 or upper.
8.6.2 Prequisites
Device Comment
Personal Computer used for connection with MiCOM C264
Operating System Supported:

• Windows® 10 Enterprise Build 1809 LTSC
Hardware configuration minimum:

• CPU 700 Mhz
PC • Hard disk 100 Mbytes space free
• 1 Ethernet port 10 or 100 Mb/s
NOTE: For earlier EPAS release Operating System

requirements, please refer to related EPAS release
documentation.
C264/EN UM/E50.5 941

Device Comment
The installer contains components:
• MiCOM C264 cpu275
• FTP Server
• MiCOM S1 Software (optional)
Components description:
• MiCOM C264 cpu275 is the MiCOM C264 release package.
It contains VxWorks BOOTROM and MiCOM C264
MiCOM C264 Computer
Application.
Installer
VxWorks BOOTROM is file system boot loader used by
embedded Operating System VxWorks. MiCOM C264.
Application is an image of Operating System VxWorks and
MiCOM C264 application release.
These files are upgraded to CPU flash memory of
MiCOM C264 device.
• FTP Server is a ftp tool.
• MiCOM S1 Software is setting software.
CAT Software is a graphical tool and communicates with

MiCOM C264 device via PERMA brick.
CAT Installer MiCOM C264 device is upgraded to CPU flash memory via the
CAT Software. CAT installer is a separate package delivery.
WinPcap Installer WinPcap is used by CAT Software. WinPcap installer is a

separate package delivery (example of installer WinPcap_4_1_
3.exe).
Windows Defender Antivirus, provided by Microsoft Windows
(certified solution for EPAS) which is installed on the PC guard
computer and updated regularly (manually by the Security
Antivirus administrator).
For the configuration and using, please refer to the documentation

EPAS Hardening Guide, section Windows Defender Antivirus.
8.6.3 MAC Address

By Schneider Electric, the MAC address range is included on domain:
942 C264/EN UM/E50.5

MiCOM C264-
Serial Number Range MAC Number MAC Address Range
CPU
00-80-F4-79- 00-80-F4-79-
Schneider 98304 139263 MAC 1
00-00 D7-FF
Electric
00-80-F4-79- 00-80-F4-7A-
MAC support 98304 139263 MAC 2
38-00 42-FF
00-02-84-00- 00-02-84-02-
00001 98303 MAC 1
Old 00-01 7F-FF
MAC support 00-02-84-00- 00-02-84-02-
00001 98303 MAC 2
80-01 FF-FF
BOOTROM without
BOOTROM with Schneider
Compatibilities Schneider Electric MAC
Electric MAC support
support
MiCOM C264-CPU with
Schneider Electric range +
Schneider Electric MAC Not Possible
Old range
support
MiCOM C264-CPU without
Schneider Electric MAC Old range only Old range only
support
In case of CPU with a serial number in the Schneider Electric range is boot with a EPAS version
without Schneider Electric Mac support, the MiCOM C264 does not start the application.
Moreover, the MiCOM C264 is seen by tool CAT with a bad serial number, which is not possible to
be change by CAT.
8.6.4 MiCOM C264 installation

8.6.4.1 Note for secured installation
Please, refer to the documentation EPAS Hardening Guide (section MiCOM C264 hardening) and
follow the procedure.
8.6.4.2 Note for authentication certificate

The certificate allows to authenticate the origin and the period of validity of an executable (setup).
Before running the setup program, the user can manually perform a security authentication.
When starting setup, Windows checks the presence of the embedded certificate in the executable
setup file.
The operator is informed by Windows:

• If the certificate is missing, an alert window will be displayed
• If the certificate is detected, a confirmation window appears with the associated informations
To check if an executable file is electronically signed:
C264/EN UM/E50.5 943

• Select the installation executable file (setup)
- Figure 632 - MiCOM C264 installation executable file - sample D1.40

• Click Right button on the executable file and select Properties from the menu
• Click on Digital Signature tab
• Select the name of the signatory = Schneider Electric
• Click on Details button to view the digital signature information
• Click on Display Certificate button to view the certificate information
• Click on General tab
• Authenticate the executable by checking the fields associated with the vendor's signature and
its period of validity.
8.6.4.3 MiCOM C264 installing from scratch

This section describes procedure for complete installation of MiCOM C264 software from scratch
with a new release.
The procedure to complete Installation of MiCOM C264 is as follows:
Step Procedure Comment

1 see topic "CAT installation" on page 966 Install CAT new release on PC
Anti-virus Software installed (Cyber-
Secured use case)
"Establish computer connection with CAT" on Please refer to the documentation

2 EPAS Hardening Guide (section
page 945
MiCOM C264 Hardening) and verify
that the procedure for a MiCOM C264
Hardening has been followed.
"Set computer boot parameter to “Bootprom
3
boot” mode" on page 948
"Update new release of VxWorks BOOTROM" Install new release of MiCOM C264
4
on page 949 computer on PC
5 "Format flash memory of CPU" on page 957
"Update new release of MiCOM C264
6
application" on page 959
"Set computer boot parameter to “Flash boot”
7
mode" on page 963
944 C264/EN UM/E50.5

8.6.4.3.1 Establish computer connection with CAT
Step Action
CAT Software of the current MiCOM C264 computer release is installed on PC:
From the Windows start menu folder “PACiS”, find CAT software (e.g. for release
A3.01):
Start CAT Software.
A disclaimer message is displayed, choose I Agree button to continue:
RECOMMENDATION: If Anti-virus software is not detected by CAT Software on PC,

an Anti-virus Message Box is displayed to notice operator cyber security risk. We
recommend use Anti-virus Avira Antivir Professional software to reduce the risk.
C264/EN UM/E50.5 945

Step Action
Establish computer connection with CAT:
1. Click on Refresh button:
2. Select the target computer to upgrade in devices available on network list and
click Connect to this device button:
NOTE: Red color indicates a correct connection with device selected.
946 C264/EN UM/E50.5

Step Action
The device login dialog box is displayed:
4
Choose “SystemAdministrator” profile and enter Password (none by default):
NOTE: Please, verify that CAT version used is compliant with firmware of MiCOM C264(s). If not
compliant, the MiCOM C264 will be not displayed at the end of Step 3; in this case, please
execute above and below procedures with the CAT version compliant with the current
MiCOM C264 firmware.
C264/EN UM/E50.5 947

8.6.4.3.2 Set computer boot parameter to “Bootprom boot” mode
Step Action
• Choose Expert Functions > Manage boot and network parameters function,
• Select Bootprom boot option,
• Click Apply parameters button:
• Confirm Yes, reboot now button:
• Wait for computer reboot ends (about 1 minute):
948 C264/EN UM/E50.5

Step Action
• After computer reboot, connect to the computer (refer to topic "Establish computer
connection with CAT" on page 945),
• Choose Display status and network parameters function > Tab General (1),
• Check computer mode value is set to BOOT (2):
• Close the CAT software:
8.6.4.3.3 Update new release of VxWorks BOOTROM
Step Action
Choose new release of MiCOM C264 computer installer setup
Access to the new release of MiCOM C264 computer Installation package.
The setup file name for installation is identified “Computer_<version>.exe”, where

<version>: The version of computer.
1
Example of setup file name:
Install new release MiCOM C264 computer on PC
C264/EN UM/E50.5 949

Step Action
Double-click the computer setup to install MiCOM C264 computer:
Choose Language in the Wizard:
Click Next.
NOTE: For Cyber Security use case, please refer to the documentation EPAS
Hardening Guide (section MiCOM C264 hardening) and follow the procedure.
Read the End User License Agreement, select “I accept the agreement”,
3
Click Next
950 C264/EN UM/E50.5

Step Action
In the "Select Destination Location" dialog box define the installation folder (the
default installation folder is C:\Program Files\Pacis\Computer):
Click Next.
RECOMMENDATION: it is recommended to create other default installation folder

name, if a previous release of MiCOM computer is already installed.
C264/EN UM/E50.5 951

Step Action
By default, a Full Installation is proposed.
With the check boxes select the components to be installed:
Click Next.
In the Select Start Menu dialog box define the Start Menu folder.
Click Next.
6 In the Select Additional Tasks dialog box, with the check box select the additional
icons Create FTPD desktop icon.
Click Next.
952 C264/EN UM/E50.5

Step Action
Check that the proposed settings are correct ones.
Click Install.
8 The installation is in progress…
9 Once the installation completed, click Finish button.
Check the correct installation result:
• From the Windows Start menu,
• Under Programs, find PACiS:
10
Update new release of VxWorks BOOTROM
C264/EN UM/E50.5 953

Step Action
Connect to the computer (refer to topic "Establish computer connection with CAT" on
page 945):
11
954 C264/EN UM/E50.5

Step Action
• Select Load bootrom software function (1),
• From tree area displayed, access to C:\Programs Files\PACiS\Computer\C264_

cpu3 location,
• select bootrom.flh file (2),
• Click Load this bootrom button (3):
12
• Confirm the file transfer starting, click Yes button:
C264/EN UM/E50.5 955

Step Action
The transfer of BOOTROM file system bootrom.fhl to CPU flash memory is in
progress…
Wait 1 minute.
A message box is displayed at the end of transfer:
NOTE: If bootrom.sig file has been bad or corrupted then MiCOM C264 shows an
13 error message “Operation Aborted”. In this case no bootrom.flh file will be updated.
If vxworks.sig file has been bad or corrupted then MiCOM C264 shows an error
message “Operation Aborted”. In this case no bootrom.flh file will be updated.
Reboot computer (MANDATORY):
956 C264/EN UM/E50.5

Step Action
• click Reboot computer button:
14 • and confirm reboot, click Yes, reboot now button:
Wait few minutes
8.6.4.3.4 Format flash memory of CPU
Step Action
page 945):
C264/EN UM/E50.5 957

Step Action
• Select Browse files function (1),
• Click Format flash memory button (2):
• Confirm format starting, click Yes button.
958 C264/EN UM/E50.5

Step Action
The flash memory formatting is indicated by a progress bar Formatting flash memory
displayed:
Wait few minutes.
The end of flash memory formatting is indicated with the progress bar ending.
8.6.4.3.5 Update new release of MiCOM C264 application
Step Action
Establish computer connection
page 945):
C264/EN UM/E50.5 959

Step Action
Update new release of computer application
960 C264/EN UM/E50.5

Step Action
• Select Load application software function (1),
• Select the path of computer software of new release. For a default installation the
directory is “C:\Program Files\PACiS\Computer\C264_cpu3” (2),
• Click Load this application software button (3):
• Confirm upload application software, click Yes Button:
C264/EN UM/E50.5 961

Step Action
Uploading application software files are indicated via the progress bar:
Wait a few minutes the end of uploading.
A message box is displayed at the end of transfer.
Reboot computer (MANDATORY):

• click Reboot computer button,
• and confirm the reboot, click Yes, reboot now button:
Wait a few minutes the reboot ending.
NOTE: After reboot the device is disconnected.
962 C264/EN UM/E50.5

8.6.4.3.6 Set computer boot parameter to “Flash boot” mode
Step Action
page 945):
Set computer boot parameter to “Flash boot” mode
C264/EN UM/E50.5 963

Step Action
• Select Manage boot and network parameters function (1),
• Choose on computer boot mode the option value Flash boot (2),
• Click Apply parameters button (3):
• Confirm reboot, click Yes, reboot now button:
Wait few minutes the reboot ending.
964 C264/EN UM/E50.5

Step Action
page 945):
5 Check.
8.6.4.4 MiCOM C264 updating

This section describes the procedure for a complete updating of MiCOM C264 release.
NOTE: For secured updating, please refer to the documentation EPAS Hardening Guide
(section MiCOM C264 hardening) and follow the procedure.
The procedure to complete updating of MiCOM C264 is as follows:

1 see topic "CAT installation" on page 966 Install CAT new release on PC
"Establish computer connection with Anti-virus Software installed (Cyber-
2
CAT" on page 945 Secured use case)
"Set computer boot parameter to
3
“Bootprom boot” mode" on page 948
"Update new release of VxWorks Install new release of MiCOM C264
4
BOOTROM" on page 949 computer on PC
"Update new release of MiCOM C264
5
application" on page 959
"Set computer boot parameter to “Flash
6
8.6.4.5 MiCOM C264 roll-back

This section describes the procedure for a complete roll-back MiCOM C264 release.
NOTE: For secured roll-back, please refer to the documentation EPAS Hardening Guide
(section MiCOM C264 hardening) and follow the procedure.
The procedure to complete roll-back of MiCOM C264 is as follows:
C264/EN UM/E50.5 965


Install CAT release on PC compliant with
1 see topic "CAT installation" on page 966
current computer release
"Establish computer connection with
2
CAT" on page 945
"Set computer boot parameter to
3
“Bootprom boot” mode" on page 948
use previous release of MiCOM C264
"Update new release of VxWorks
4 computer Installation package containing
BOOTROM" on page 949
the VxWorks to roll-back.
Install CAT release on PC compliant with
5 see topic "CAT installation" on page 966
previous computer release to roll-back.
use previous release of MiCOM C264
"Update new release of MiCOM C264 computer Installation package containing
6
application" on page 959 the application to roll-back, and compliant
CAT release (see previous step)
"Set computer boot parameter to “Flash
7
8.6.5 CAT installation

8.6.5.1 Introduction
This section describes procedures in order to install, update and roll-back Computer
Administration Tool software (CAT).
8.6.5.2 Prequisites
The Computer Administration Tool (CAT) software needs components:
• Framework NET 3.5 SP1,
• Driver WinPcap 4.1.3.
Components are located on the package in:

• \System\Delivery\PACiSVa.b.c\TOOLS\Framework .net 3.5 SP1,
• \System\Delivery\PACiSVa.b.c\TOOLS\WinPcap.
8.6.5.3 Note for secured installation

Please, refer to the documentation “EPAS Hardening Guide” (section “MiCOM C264 hardening”)
and follow the procedure.
8.6.5.4 CAT installing from scratch

This section describes procedure for complete installation for CATsoftware from scratch with new
release compliant cyber security.
This procedure is as follows:
966 C264/EN UM/E50.5

Step Procedure
1 " Framework NET 3.5 SP1 installation" on page 967 (if not installed)
2 "WinpCap 4.1.3 driver installation" on page 968 (if not installed)
3 "CAT installation" on page 970
Before installation or update, please follow instructions:
Step Action
1 Access with administrator account for CAT Installation.
Uninstall previous CATversion before installing the new version.
2 NOTE: For lower A1.24 versions, uninstall manually the previous version. For higher
A1.24 versions, un-installation is made automatically by CAT setup.
8.6.5.4.1 Framework NET 3.5 SP1 installation
Step Action
Double-click the dotnetfx35_xpsp1.exe to install the Framework NET 3.5 SP1:
NOTE: For cyber security use case, please refer to the above Note for secured
installation .
2 The installation is now complete.
C264/EN UM/E50.5 967

8.6.5.4.2 WinpCap 4.1.3 driver installation
Step Action
Double-click the WinPcap_4_x_y.exe to install the Driver WinPcap (x.y is the release
number):
NOTE: WinPcap version is 4.1.3 or higher.
Click Next in the Wizard.

2
Read the License Agreement, select I Agree.
968 C264/EN UM/E50.5

Step Action
Click Install.
The installation is now complete.
Click Finish
C264/EN UM/E50.5 969

8.6.5.4.3 CAT installation
Step Action
Run the CAT Software installer package of new release; the setup file name for
1 installation is identified
NOTE: For cyber security use case, please refer to the documentation “EPAS
Hardening Guide” (section “MiCOM C264 hardening”) and follow the procedure.
Read the License Agreement; select I Agree:
Click Next.
970 C264/EN UM/E50.5

Step Action
In the "Select Installation Folder" dialog box define the installation folder (the default
installation folder is C:\Program Files\PACiS\CAT
Click Next.
NOTE: it is recommended to create other default installation folder name, if previous

CAT is already installed.
C264/EN UM/E50.5 971

Step Action
The installation is in progress…
972 C264/EN UM/E50.5

Step Action
The installation is now complete.
Click Close .
Check the correct installation result:
• From the Windows Start menu,
• Under Programs, find PACiS > CAT:

6
8.6.5.5 CAT updating

Please, refer to the documentation “EPAS Hardening Guide” (section “MiCOM C264 hardening”)
and follow the procedure.
The procedure to complete updating of CAT is as follows:
Step Action
1 Login with Windows® User Account (with Administrator user right)
2 Refer to the topic "CAT installing from scratch" on page 966.
8.6.5.6 CAT roll-back

The procedure to complete roll-back of CAT is as follows:
C264/EN UM/E50.5 973

Step Action
1 Login with Windows® User Account (with Administrator user right)
2 Uninstall the actual CAT software via Windows Control Panel.
3 Install the previous CAT software.
8.6.6 CAT: How to use it?

8.6.6.1 Human Machine Interface
The accordion resizable window features a menu bar and three panes:
- Figure 633 - CAT - Human Machine Interface
To enlarge the Scan pane, collapse the Filter pane using the horizontal Auto hide toggle button.
To enlarge the Work pane, collapse the left panes using the vertical Auto hide toggle button.
To retain a shot of the whole window in png format, click the link Save As Snapshot.
8.6.6.2 Language selection

Select the HMI language among French, English:
974 C264/EN UM/E50.5

- Figure 634 - CAT - Language selection
Language can be changed on the spot; no need to restart CAT.
8.6.6.3 Operator's record folders

<Installation folder>/CAT/Files is the default destination folder for snapshots, security logs,
directories export.
<Installation folder>/CAT/Error_Reports is the destination folder for fault report. A fault report
might result from a window popping up, for example:
- Figure 635 - CAT - Window popping up
8.6.6.4 Settings
In case the PC has several network cards, click Select network adapter and select the desired
card. Some cards are not fit for the CAT (NdisWan Adapter, MS TCP Loop back interface…).
The selection is saved in the Windows registry. All the settings are restored at CAT next start.
8.6.6.5 Scan
To carry an inventory of the networked computers, click Refresh; this populates the computers
directory:
• Computer network name as input in SCE
• Cpu serial number (# stands for 000)
C264/EN UM/E50.5 975

• Computer IP address
• Computer mode: maintenance, active, stand-by (redundancy)
• Rack address: Main / Secondary (multi-rack architecture)
The text color reflects the computer's mode:

• red: maintenance
• blue: stopped
• black: bootprom
• green: active
• grey: disconnected
To sort the items according to the values in a column, click the column header; this reveals a click-
able sorting sign 6 or 5.
To deny access to computer information, click the computer eye icon, the icon looks crossed off;
select Hide selected computers option and the computer selected is off:
976 C264/EN UM/E50.5

- Figure 636 - CAT - Scan
To restore access, exit CAT using the upper corner red cross and restart it.
When computer is in maintenance the status shown in the close-up line-: MAINT DATA BASE.
- Figure 637 - CAT - Scan - computer in maintenance
However, when Computer is in Active state close-up line shows the banner text if configured in
EPAS-SCE else the space is blank:
C264/EN UM/E50.5 977

• sample of EPAS-SCE configuration:
- Figure 638 - EPAS-SCE - MiCOM C264 banner configuration - sample
• resulting CAT visualization:
- Figure 639 - CAT - MiCOM C264 banner configuration - sample
To export the directory to the txt format, click on icon .
To print the directory, click on icon .
The Filter pane is used to narrow the list of displayed computers:

• one computer, by typing an IP address (the wildcard character * is allowed),
• all the computers being in a given mode (first drop-down list),
• all the extensions with a given number (second drop-down list: 0 for main computer thru 16).
Any means that the criterion has no effect.
To dim a computer line, click the eye icon and select the box Hide selected computers.
978 C264/EN UM/E50.5

To take mute computers off the list, click the link Clear disconnected computers.
8.6.6.6 Connection to a computer

To select a computer, click on it in the directory; this displays the latest computer name and data
base number (if any) in the close-up line.
To establish a communication with the computer, click Connect to this computer (or click two
times). A login window shows:
- Figure 640 - CAT - Connection to a computer
Enter your username and password and click OK. The available usernames and passwords are
as defined in the cybersecurity chapter of the MiCOM C264 documentation.
Depending on the security policy, the account might be locked out due to several incorrect
password typed in; in this event, ask the Security administrator to unlock it.
Several sessions cannot be open simultaneously. To change profile, click again Connect to this
computer.
Note for Auto Log Off: when operator's does not place applicative requests for longer than a
timeout, any further action requires a reconnection. To set the time-out, ask the Security
administrator. Default value: 10min.
MiCOM C264 will refuses CAT connection if its embedded cyber security brick certificate has not
been renewed for 10 years. Once the certificate is expired, connection through CAT becomes
inaccessible.
To fix this issue, restart the MiCOM C264 to renew the validity date of certificate. Once the BCPU
has been restarted, the connection through CAT becomes available again for a further cycle of 10
years.
8.6.6.7 Work pane

The logon status is reminded in the upper right corner; the computer's information is reminded in
the work pane upper left corner:
C264/EN UM/E50.5 979

- Figure 641 - CAT - Work pane
The Reboot button is used to reboot the computer, it is only available when logged as a user with
the DefaultEngineer profile.
The ribbon menu shows items giving access to computer's updated information and allow the
databases managing. The list depends on the user's privileges and computer's mode.
The Log Off button disconnect you from the computer.
The ribbon menu depends on the profiles:
Items \ Profiles Viewer Operator Engineer

Display status and
X X X
monitoring
Manage databases X X
Edit settings X
Manage events and
X X X
states
Display error and
X X X
agency logs
Display AVR data X X X
Waveforms X X X
Expert functions
Manage date and time X X X
Manage boot and
X X X
network parameters
Manage
X X X
communication ports
Load application
X
software
Load bootrom
X
software
Browser computer
X X X
files
Launch a telnet X(*) X(*) X(*)
(*): telnet functionality is no longer supported by BCPU in EPAS 6.4.
980 C264/EN UM/E50.5

8.6.6.8 Modes and permitted operations
Mode Comment
MiCOM C264 stopped before the boot (whether a networkboot or
BOOTPROM (Boot) flashboot / first count-down), only the CAT can detect
MiCOM C264
MiCOM C264 stopped before the application launch after the boot
STOPPED (Stop) (whether a networkboot or flashboot / second count-down), or
after a Stop command
MAINTENANCE (Maint) Ready to receive a DB
ACTIVE (Activ) Nominal state
STAND-BY (Standby) Spare MiCOM C264 in redundancy architecture
SIMULATION (Simul)
FAULT (Fault) DB issue (confirmed by reboot)
HALT (Halt) The number of faults permitted per day (normally 5) is overrun
INITIALIZATION (Init) Transient state, no filter
Some operations might require the computer mode changing. An operation can be available for
the main (or mono) rack (M) or even for an extension (A for All):
Mode -> Simul Activ Standby Maint Fault Halt Stop Boot
Operation
general A A A A
board A A A A
Status
IEDs A A A A
Multir. M M M M
view M M M M M M M
load M M M M
Database
switch M M M M
suppr. M M M M M M M M
Settings M M M
Events M M M M
errors A A A A A A A A
Logs
agency M M M M M M M
AVR M M
Disturb. M M
Datehour A A A A
Bootnetw A A A A A A A A
C264/EN UM/E50.5 981

Mode -> Simul Activ Standby Maint Fault Halt Stop Boot
Operation
A if
System A A
stopped
A if
Bootrom A A
stopped
explore M M M M M M M M
Browse A if
form. fl. A A A A
stopped
SSH A A A A A A A A
No operation is available in Init mode of the MiCOM C264.
8.6.6.9 Routine operations

8.6.6.9.1 Display status and monitoring
Three tabs are available with a Refresh button for each of them:
• General lists the computer and database identification information; in multi-rack
configuration, the cluster membership is also displayed:
- Figure 642 - CAT - Display status and monitoring - general pane
982 C264/EN UM/E50.5

NOTE: Computer mode

With computer version older than B7.xx, the “Computer mode” is displayed with BOOT
mode status value instead of real mode (ACTIVE, MAINT…).
With computer version in version B7.xx, the “Computer mode” is displayed with the real
mode status value.
• Boards is a dashboard:
at the board level:
status (reflected in the board name: green for present and configured, blue for
missing or not configured, red for configured but faulty)
index (as in EPAS-SCE): @0, @1 etc
at the I/O level: status; tool tips include nature over the number, on/off over the led
- Figure 643 - CAT - Display status and monitoring - board pane
As the changes of state may be frequent, an auto refresh occurs at each tab opening, and can be
triggered each 5 second for 1 min (box Automatic refresh).
• IED Networks shows, for each computer port, the link status of the IEDs (red for mute, green
for present) and lists the configured IEDs on the legacy bus (name, connection state). A
banner identical to that in LHMI of MiCOM C264 is showed (see topic "General display
management" on page 505).
NOTE: In multirack configuration, extensions are also shown.
NOTE: Tunnelling requires PatuSpy software and MiCOM S1 - PACiS;
C264/EN UM/E50.5 983

8.6.6.9.2 Manage database (subject to privilege)

A sketch illustrates the present configuration:
• the active database, on the left (coloured)
• the standby database, on the right (grayed)
• both labels include versions number, order of downloading (DB1, DB2 ..), optional attribute
(Modified, Missing …)
- Figure 644 - CAT - Manage database
- Figure 645 - CAT - Manage database - MiCOM C264 database status
The setting can be done in various ways (through the computer LHMI, through uploading...). For
more details, refer to the chapter C264/EN FT.
To upload a database:
984 C264/EN UM/E50.5

• Browse the disk structure to select a version-ed database archive (the USB port is out of the
scope):
- Figure 646 - CAT - Manage database - upload database #1

• Click the button Select the SCE database; wait till a form shows (a maximum of 1 hour is
needed to transfer and store a 20 Mb file):
- Figure 647 - CAT - Manage database - upload database #2
The drop-down list enrolls all the computers in this session's databases (<network name in
SCE>.adb)
• Assign to the computer one MiCOM C264 in this list
• If the need arises:
C264/EN UM/E50.5 985

select another data base through the link Select another SCE database.
To change the version number, select the box Substitute the database and type a new
Version Number;
To upload also the mpc file, click Save the SCE database into the computer. In the
<DB_name>.zip, CAT selects and uploads the <BD_name>.mpc file. Only one .mpc file
can be archived (a new download deletes and replaces the previous file). As VxWorks
limits the file name to 8 characters, the downloaded file is renamed “DB.zip”.
• Click the button Start database uploading; this updates the databases sketch and displays
a report of the uploading:
- Figure 648 - CAT - Manage database - successful database upload

• To switch active and standby databases:
click Switch databases,
wait till the computer reboots.
reconnect: the version numbers are exchanged.

• To delete both databases, click clean all databases. This shows a disconnected mode.
8.6.6.9.3 Edit settings (subject to privilege)

Used to launch MiCOM S1 - PACiS. Refer to the chapter C264/EN ST.
CAT is disconnected for MiCOM S1 - PACiS to take over.
A setting in MiCOM S1 - PACiS results in the suffix Modified being appended to the database
label.
8.6.6.9.4 Manage events and states (subject to privilege)

Two kinds of information are displayed: events and latest datapoint values.
8.6.6.9.4.1 Events
Three tabs are available with a Refresh button and output buttons (Save as text files, Print)
For each of them; CAT reads the event log saved in computer flash memory and transfers the log
in a file.
986 C264/EN UM/E50.5

• Event Log displays:
the computer software content
the computer and database information (in SCE, 'Device name' is called 'Network name'
and 'Description' is Short name)
the events that occurred whether automatically or manually driven, in the reverse
chronological order, in a tabular way: <date> <time> <object> <sub-object> <event label>
<state>; the cyber security events are preceded with the character @
MiCOM C264 objects include #C264, HMILCD, MAINT (flash directory) …
For MiCOM C264 firmware signature, MAINT datapoint “Unsigned FW” signifies if the
firmware is correct or corrupted. If RESET, means Firmware is correct or If SET, means
Firmware is corrupted or wrong.
- Figure 649 - CAT - Event Log display
The date and time are provided by MiCOM C264 not by the CAT machine.
• Event Log Parameters and Printer Parameters tabs help you to choose the verbosity of
traces. The parameters are detailed in each information frame:
C264/EN UM/E50.5 987

- Figure 650 - CAT - Event Log and printer parameters
"Disable event log storage" (default state) disables event log storage mechanism. The state is
updated in function information frame:
- Figure 651 - CAT - Disable event log storage
Connection port can be:
/null: no printer
"/Smc1/tty": serial port on front panel (setting or shell connector)
"/Scc1/tty": port 1 on BIU
"/Scc2/tty": port 2 on BIU
"/Scc4/tty": port 4 on Cpu3 board (rear side)
Line: number of lines displayed per page (typical value: 50000)
988 C264/EN UM/E50.5

Suppress: number of suppressed lines when the buffer is full (typical value: 300)
Baud rate: 4800 thru 19200
Buffer size used by the PRINT task to sock lines (typical value: 1000)
Printer control mode can be one of:
"0 (none)" no control
"1 (Xon/Xoff)" software control
"2 (Hard)" hardware control
"3 (Both)" software and hardware control
8.6.6.9.4.2 Latest datapoint values
• States snapshots displays a header, identical to the display in Display status/general,

followed by the present time-tagged values of data points; they are sorted according to the
types:
Binary inputs
Measurements
Counters
Status Indication Group (MPS): boards status, built-in function MPS
Step Positions: TPI
The picture for each type are captured and saved by Capture Now button:
- Figure 652 - CAT - Latest datapoint values
C264/EN UM/E50.5 989

8.6.6.9.5 Display errors and agency logs

• System error files:
The content of /flash/systrap/index.txt is displayed. It shows the number of software errors

since the initialization of the index, the date and time of the last error and the name of the file
containing information on this error.
This file (containing the last systrap) is pre-selected in the drop-down list Select system
error file number.
The latest ten error files are archived: select one of them using this list.
- Figure 653 - CAT - Display errors and agency logs

• Agency Log: the content of /ramdev/agency.log is displayed.
8.6.6.9.6 Display AVR data

The AVR Log tab lists the number of tap changes on various time spans: since MiCOM C264
initialization (Global), since the latest reset time with the related button (Partial), permanently on a
slipping period set in MiCOM S1. At reset, the page is refreshed. The I² and times (0 thru 63) of
use of each tape are also summed:
990 C264/EN UM/E50.5

- Figure 654 - CAT - Display AVR data #1
The Global/Partial histogram tabs show the Pareto charts.
- Figure 655 - CAT - Display AVR data #2
8.6.6.9.7 Waveforms
The list of disturbance files is displayed in the text area.
To refresh it, press Refresh.
C264/EN UM/E50.5 991

- Figure 656 - CAT - Waveforms
To download COMTRADE files:

• Select the destination directory in the PC.
• Click the button Transfer waveforms from the computer to this directory. All the files are
uploaded.
The button Clear all waveforms is used to erase the Fast Waveform from MiCOM C264P flash
memory.
8.6.6.10 Expert Functions

8.6.6.10.1 Manage date and time (read, and change depending on profile)
This page is split in several sections:
• The first section shows data read on computer:
First running date of the computer (located in /flash/MAINT/firstrd)
Computer total usage duration: number of hours the computer has been running
(located in in /flash/MAINT/ophours)
992 C264/EN UM/E50.5

- Figure 657 - CAT - Expert Functions - Manage date and time

• The second section is used to set a time and date value and send it to the computer.
If the box Synchronize with Windows time is checked, the current computer time cannot be
set: the current date and time are taken from Windows on the PC and displayed.
Set year button: it is useful to set only the year on a new MiCOM C264 because the IRIG B
signal does not include the Year data; the new MiCOM C264 gets the default year value from
Windows.
• The third section specifies what defines the seasonal clock shifts:
the active database through the SCE attribute Scs/General/Time zone
forcefully set times daylight

• The fourth section displays synchronism and IRIG-B status
If IRIG-B interface is present on the cpu3 board, IRIG-B status displays IRIG-B validity, RTC
local time, IRIG-B signal level, MSP430 software version.
The EPAS system operates with the SNTP master server connected to the SBUS. The SNTP
master server synchronizes all of the devices connected to the SBUS.
In the EPAS system, every 20 seconds the GPS sends an IRIG B signal to the SNTP master
server. The IRIG B signal includes the second, minute, hour, day and month. The IRIG B signal
does not include the year.
C264/EN UM/E50.5 993

The SNTP master server changes the year and the day. Within 20 seconds, when the SNTP
master server receives the next IRIG B signal, the SNTP master server keeps the year you typed
and changes the day to agree with the IRIG B signal.
The SNTP master server sends the time-date data, including the correct year, over the SBUS to
all of the devices.
NOTICE
RISK OF DATA INCOHERENCY
• To change the year or the time-date data, connect the CAT only to the sntp master server.
Do not connect the CAT to the new MiCOM C264 or to a client.
• If you change the year or the time-date data on a new MiCOM C264 or on a client, the EPAS
system receives data from two sources: the irig b signal, and the new MiCOM C264 or client.
Failure to follow these instructions can result in data incoherency.
8.6.6.10.2 Manage boot and network parameters
- Figure 658 - CAT - Expert Functions - Manage boot and network parameters
This page is split in several sections:

• The first section allows to know and modify the disk the computer boots on:
Flash boot: flash memory
Network boot, that is using ftp (the IP address is in the second section)
Boot prom boot: the computer is stopped after the boot

• The second section allows to modify the network parameters:
994 C264/EN UM/E50.5

It is recommended that the two IP addresses belongs to different domains, otherwise CAT
does not allow to configure same IP address on both Ethernet ports.
FTP server host IP is the Internet address of the host to boot on (type 127.0.0.1, the local
host, if no host is defined).
• The third section allows to assign addresses to the racks in a multi-rack configuration
A group is a cluster including a main rack and several secondary racks. Main 2 means the
computer serves as a back up to the Main 1 one (redundancy).
• The fourth section allows to access the password required to log in WFTD (it is set in
WFTPD/Security/User-rights)
For the new parameters to be effective, click Apply parameters (click anywhere in the pane first,
if the button is dimmed).
8.6.6.10.3 Manage communication ports

It is possible to disable some communication ports for all users:
• a Shell: e.g. HyperTerminal through the serial front port (it applies only to Rx on MiCOM C264
side; Tx is always active, for debugging purpose)
• SSH server: see further; if it has been disabled, restart the MiCOM C264 after re-enabling
SSH server.
• Ethernet port No 2: Cpu3 board second port; it can be used to separate IEC 61850 flows and
Scada flows, reports and gooses, etc. For more details, refer to the chapter 3.5 in C264/EN
FT. In Multi-rack configuration, it must be enabled as it is used for inter-rack communication.
- Figure 659 - CAT - Expert Functions - Manage communication ports
C264/EN UM/E50.5 995

8.6.6.10.4 Load application software

Refer to topic "Update new release of MiCOM C264 application" on page 959.
8.6.6.10.5 Load bootrom software

Refer to topic "Update new release of VxWorks BOOTROM" on page 949.
8.6.6.10.6 Browse computer files

Files can be exchanged between the PC and the computer (RAMDEV and Flash) and also
deleted. If a new file does not show in the explorer, collapse the container (sign –) and expand it
again (sign +).
Tip out a file from one side to the other using the buttons:
- Figure 660 - CAT - Expert Functions - Browse computer files
The files name cannot be changed; only files with DOS name format (8.3 character format) can be
copied.
To format the flash memory:

• switch the computer to stopped or boot mode
• Click the Format flash memory button and wait till the end.
NOTE: The passwords and log-off time-outs are spared by this operation.
996 C264/EN UM/E50.5

8.6.6.10.7 Launch a SSH session

To perform tasks that CAT cannot handle, launch an SSH client on the operator PC and log to
computer.
As SSH session is launched independently of CAT, multi sessions on two or more computers are
possible.
As CAT session uses TCP/IP stack, the computer has to be accessible from the PC in this mode.
8.6.6.11 REU board

8.6.6.11.1 REU Initial configuration with CAT
At first, the REU board coming out from the factory is not configured. Please follow the steps
below to configure REU board first time:
1. Disconnect all network from REU board
2. If ETH1 and ETH2 not already configured, configure ethernet ETH1 and ETH2, the network
range are different on ETH1 and ETH2.
3. Connect ETH1 on Interlink port of REU board
4. Connect MiCOM C264 ETH2 port on same network as CAT computer
5. Configure REU board using CAT
NOTE: After the configuration of the REU board, it is possible to connect CAT directly on same
network, it is mandatory to connect CAT to ETH2 only for first REU configuration.
8.6.6.11.2 REU configuration with CAT

The CAT allows to monitor and update the firmware of the REU Boards.
NOTE: Use CAT version A3.15 or later.
8.6.6.11.2.1 REU settings
The specific REU settings are accessible on CAT.
To open the dialog box of REU parameters, do following:

• From CAT main panel, select Manage boot and network parameters view,
• On the panel, click on REU Switch Parameters button:
C264/EN UM/E50.5 997

- Figure 661 - CAT - Access to REU settings
The window REU settings is displayed as below (use the vertical scrollbar to access all settings):
- Figure 662 - CAT - REU setting display
The action asociated to buttons are as follows:
Button Action
Refresh Reload parameter from the board.
Apply Apply parameters set to the board.
Factory Mode Set the setting to default value
998 C264/EN UM/E50.5

The editable settings in RE parameters are the following:
Label Description Avaialable field values

Name Name of Certificate mandatory
Description Description of certificate
Status of flashing process.
IDLE
Status can be set only when
state is not BUSY. This is ERROR
FLASH
used to reset status before OK
new update
BUSY
HUB
SWITCH
HSR
Allows to set mode of PRP

MODE
HSR/PRP module RSTP
PORT_A
PORT_B
OFF
Enable/disable PTP ON
PTP
IEEE1588 protocol. OFF
Define the primary domain
PTP_PRIMARY_DOMAIN use to syntonizer internal 0..255
hsr/prp ptp clock.
PTP_ANNOUNCE_RECEIPT_ Timeout period of announce
2..10
TIMEOUT message.
Period of Pdelay_Req
PTP_LOG_MIN_PDELAY_
message sent to compute link 1/2/4/8/16/32
REQ_INTERVAL
delay.
HSR_PRP_LIFE_CHECK_ Period of hsr/prp supervision
100..5000
INTERVAL frame sending.
HSR_PRP_ENTRY_ Period of clearing the
10..1340
FORGET_TIME duplicate table.
HSR_PRP_SUPERVISION_ Enable or disable of hsr/prp ON

FRAME supervision frame. OFF
Enable or disable removing of ON
PRP_TRANSPARENT_
RCT PRP frame in PRP
RECEPTION OFF
mode.
C264/EN UM/E50.5 999

Enable to automatically switch ON

AUTO_INTERLINK
the interlink port. OFF
Enable interlink to sends
FLOW_CONTROL_ PAUSE frame according to ON
INTERLINK 802.3 when there is overflow OFF
in HSR mode.
Enable lldp on LanA and ON

LLDP_AB
LanB. OFF
ON
LLDP_I Enable lldp on Interlink port.
OFF
NONE
ChassisID
LLDP_A_REMOTE The LLDP remote state of
PortID
LLDP_B_REMOTE port.
TTL
LLDP_I_REMOTE
MAC_SRC
IP
Value prepended to Ethernet
RSTP_BRIDGE_PRIORITY mac address to form the 0..61440
Bridge Identifier.
Value prepended to port 0..240
RSTP_PORT_A_PRIORITY
number from the Port
RSTP_PORT_B_PRIORITY step of 16
Identifier.
RSTP_PORT_A_PATH_
COST Value added to current path
1..200000000
RSTP_PORT_B_PATH_ cost on root port.
COST
Parameter to force use
version of RSTP protocol RSTP
RSTP_FORCE_PROTOCOL_
backward to STP or to RSTP
VERSION STP.
(v2). RSTP is also STP
compatible
Determine the maximum
RSTP_BRIDGE_MAX_AGE distance between any bridge 6..40
and the current root bridge.
RSTP_BRIDGE_ FORWARD_ Delay used for compatibility
4..30
DELAY with older STP standard.
RSTP_BRIDGE_HELLO_
Period of BPDU frame. 1..2
TIME
1000 C264/EN UM/E50.5


Enable the forward to A or B ON
UNICAST_FORWARD_ALL port of unicast frame targeted
to interlink port. OFF
Define the sent to Interlink ON

ACCEPT_ALL
port. OFF
All multicast frames from port ON

MULTICAST_ALL
A & B are sent to Interlink port. OFF
Multicast address accepted

MULTICAST_yy xx-xx-xx-xx-xx-xx
toward Interlink.
For information, the setting table below describes the Read Only REU Parameters:
Label Description Field

x.y
VERSION Version of running software x = Major revision
y = Minor revision
FACTORY
FPGA Version of setting
USER
OK
EEPROM Status of internal EEPROM
KO
Status of external power ON

EXT_PWR
supply OFF
EXT_POWER
PSU_USE Current power supply source
IED_PWR
NOT_FITTED
Status of optical transceiver RX_OFF

TRA/TRB
A/B TX_OFF
OK
IP address used by internal
IP_ADDR CPU of HSR/PRP board for 0.0.0.0
LLDP protocol.
Source MAC address used to
ETH_MAC_S send supervision frame in xx-xx-xx-xx-xx-xx
HSR or PRP mode.
C264/EN UM/E50.5 1001

Label Description Field

Source MAC address used by
HSR/PRP module to answer
ETH_MAC_I xx-xx-xx-xx-xx-xx
to HOST_CPU on interlink
port only.
MAC address of the RSTP
RSTP_BRIDGE_ROOT xx-xx-xx-xx-xx-xx
root bridge.
State:
• FORWARDING
• DISCARDING
• DISABLED
RSTP_BRIDGE_PORT_A Current state of port Role:
RSTP_BRIDGE_PORT_B • ROOT
• DESIGNATED
• ALTERNATE
• BACKUP
• DISABLED
8.6.6.11.2.2 REU firmware upgrade
To upgrade a firmware of REU2 board, do following:

• From Configuration tool CAT main panel, select Browse files view,
• On Local PC Side tree, select the firmware file to send to board,
• Click on Send button to send the firmware file forward REU board:
1002 C264/EN UM/E50.5

- Figure 663 - CAT - REU firmware upgrade
The MiCOM C264 automatically detects the reception of firmware file and upgrade it to REU
board;
After upgrade, the REU board restarts with the new firmware.
C264/EN UM/E50.5 1003

8.7 Uploading a security configuration with Cybersecurity Admin

Expert
MiCOM C264requires a security configuration (RBAC and security policy) to operate. For more
details, refer to chapter Cyber security of MiCOM C264 user manual and Cybersecurity Admin
Expert user guide.
1004 C264/EN UM/E50.5

8.8 Uploading database with CAT

MiCOM C264requires a database to operate. It stores up to two databases, named “current” and
“stand-by”. Only the current database is used for operation. The second database can be
downloaded when the computer is in operational or maintenance mode. A specific control allows
switching between the two stored databases.
EPAS-SCE (System Configuration Editor) is used to generate the databases. CAT is used to
upload and switch the databases.
For more detail refer to topic "Manage database (subject to privilege)" on page 984.
C264/EN UM/E50.5 1005

8.9 After computer installation

Installation is now complete.
In the event of any problems refer to the section "Maintenance" on page 1144.
1006 C264/EN UM/E50.5

8.10 Optional installation

Optional hardware modules include:
• IRIG B connection,
• Printer.
8.10.1 External master clock connection

With the option of the CPU board, an external standard BNC connection is used to receive
external master clock synchronisation. The recommended external master clock is the hopf 6870
radio clock.
Installation should follow the standard rules of BNC cable installation including length limit and
optional 50 ohms termination.
For installation of the external master clock, refer to its documentation and to the summary in
EPAS system/EN IN chapter.
External IRIG B synchronisation should be configured in the computer database.
8.10.2 Printer installation

A printer can be installed permanently for the SOE, or temporally for commissioning/maintenance
use. Data labeling is defined with EPAS-SCE.
The printer should be connected to either port 1, 2, 3 or port 4 of the computer.
If the port is on the BIU board, the board has to be configured for RS 232 by using the correct
jumper configuration.
Furthermore, a configuration file (included in database) has to be installed onto the computer with
the printer communication parameters.
C264/EN UM/E50.5 1007

9 Settings MiCOM C264 - User Manual
9 Settings
9.1 Setting via local LCD 1009

9.1.1 Tree Panel Navigation 1009
9.1.2 Tree Panel Parameters 1009
9.2 Setting via MiCOM S1 - PACiS software and CAT application 1016
9.2.1 General presentation of parameters in MiCOM S1 - PACiS 1016
9.2.1.1 ARPCCN parameters 1017
9.2.1.2 AVR parameters 1018
9.2.1.3 Auto-Recloser (Type 1) parameters 1019
9.2.1.4 I²t parameters 1020
9.2.1.5 Internal Synchrocheck (Type 1) parameters 1020
9.2.1.6 FBD parameters 1022
9.2.1.7 Activate de-Activate protection function trip 1023
9.2.2 Upload a setting file to MiCOM C264 1023
9.2.3 Download a setting file from MiCOM C264 1029
9.2.4 Setting transfer’s dependence on computer modes 1035
9.2.5 MiCOM S1 - PACiS acknowledge 1035
1008 C264/EN UM/E50.5

MiCOM C264 - User Manual 9 Settings
9.1 Setting via local LCD

9.1.1 Tree Panel Navigation
Tree panel is accessible from bay panels by selecting the following key:
All data points are grouped into features and folders. To access a given feature the operator
should navigate the panels using the arrow keys. The folders hierarchy is displayed in each panel.
switches to neighbouring folder
switches to neighbouring folder
select and expand the folder switching to its first item
go up to father folder
At the bottom of the hierarchy, the folder is the single point of information, control or parameter.
Edit mode allows the operator to change values.
Enter into Edit mode. It then asks to enter the system engineer password.
Cancel edition and the data point modification
The most commonly used settings and controls are selected into a list. To browse the list the
operator navigates using the arrow keys. The modification/control sequence is cancelled by
. The selection is confirmed by .
9.1.2 Tree Panel Parameters

Available
Values or
MENU TREE Parameter signification
[min;max](step)
(unit)
COMMAND
MAIN
RESET OP
RESET To reset the number of the MiCOM C264 operating hours.
HOURS
CHANGE OPERAT, To change the MiCOM C264 mode into active,
MODE OP MAINT, TEST maintenance or simul mode.
GLB ACK
ACK To acknowledge all MiCOM C264 alarms
ALARM
GLB CLR
CLEAR To clear all acknowledged and reset alarms
ALARM
To change the date. Accepted if the MiCOM C264 is not
DATE DATE
synchronised
C264/EN UM/E50.5 1009

Available
Values or
[min;max](step)
(unit)
To change the time. Accepted if the MiCOM C264 is not
TIME TIME
synchronised. The time format is hh : mn : sec.
DB SWITCH YES To switchover active and standby databases.
LANGUAGE LG1, LG2 To switchover Language1 and language2.
COUNTER
Counter 1
…
Counter N
- COUNTER
Counter value To change the counter value.
value
CONFIG
COMPUTER
MAIN
IP ADDRESS xxx.xxx.xxx.xxx To read the MiCOM C264 IP address
BAY
Bay 0
…
Bay N
INTERNAL
S/C
S/C associated To read the name of the device associated to the
XXXX
Dev synchrocheck
THRES PRES
[0.5;1.1](0.01)(V) Multiplier of nominal voltage above which the line is LIVE.
LINE
THRES ABS
[0.1;0.6](0.01)(V) Multiplier of nominal voltage below which the line is DEAD.
LINE
THRES PRES
[0.5;1.1](0.01)(V) Multiplier of nominal voltage above which the bus is LIVE.
BUS
THRES ABS
[0.1;0.6](0.01)(V) Multiplier of nominal voltage below which the bus is DEAD.
BUS
DELTA VOLT [0.02;0.5](0.01) Voltage difference between bus and line above which
LOCK (V) locking close is not possible.
DELTA FREQ Frequency difference between bus and line above which
[0;1](0.01)(hz)
LOCK locking close is not possible.
1010 C264/EN UM/E50.5

Available
Values or
[min;max](step)
(unit)
DELTA PHASE Phase difference between bus and line above which
[0;30](1)(deg)
LOCK locking close is not possible.
FMIN LOCK [45;65](0.01)(hz) Minimum acceptable frequency for locking close.
FMAX LOCK [45;65](0.01)(hz) Maximum acceptable frequency for locking close.
DELTA VOLT [0.02;0.5](0.01) Voltage difference between bus and line above which
COUPL (V) coupling close is not possible.
DELTA FREQ Frequency difference between bus and line above which
[0;1](0.01)(hz)
COUPL coupling close is not possible.
DELTA PHASE Phase difference between bus and line above which
[0;30](1)(deg)
COUPL coupling close is not possible.
FMIN COUPL [45;65](0.01)(hz) Minimum acceptable frequency for coupling close.
FMAX COUPL [45;65](0.01)(hz) Maximum acceptable frequency for coupling close.
[0; 1000](10) Circuit breaker close time in order to anticipate the close
REAC TIME
(ms) order for the coupling.
ABS V CONF [200;10000](20)
Time after which the line and the bus are considered dead.
TIME (ms)
ONLY V CONF [200;10000](20) Time after which only one voltage among the line or the
TIME (ms) bus is considered live.
PRES V CONF [200;10000](20)
Time after which the line and the bus are considered live.
TIME (ms)
CLOSE TO [200;10000](20)
Time waited for having locking conditions.
MAN SYN (ms)
CLOSE TO
[1; 3600](20)(s) Time waited for having coupling conditions.
MAN SY C
CLOSE TO [200;10000](20)
Time waited for having dead-dead or dead-live conditions.
MANUAL (ms)
CLOSE TO [200;10000](20) Time waited for closing conditions in case of auto-recloser
AUTO (ms) control.
MAN SYN CLO Flag to permit or not the coupling for a “close with
YES, NO
COUPL synchrocheck” operator control.
MAN SYN CLO Flag to permit or not the locking for a “close with
YES, NO
LCK synchrocheck” operator control.
MAN SYN CLO Flag to permit or not a control with a dead line and a live
YES, NO
LDBL bus for a “close with synchrocheck” operator control.
C264/EN UM/E50.5 1011

Available
Values or
[min;max](step)
(unit)
MAN SYN CLO Flag to permit or not a control with a live line and a dead
YES, NO
LLBD bus for a “close with synchrocheck” operator control.
MAN SYN CLO Flag to permit or not a control with a dead line and a dead
YES, NO
LDBD bus. for a “close with synchrocheck” operator control.
Flag to permit or not the locking for a “normal close”
MAN CLO LCK YES, NO
operator control.
MAN CLO Flag to permit or not a control with a dead line and a live
YES, NO
LDBL bus for a “normal close” operator control.
MAN CLO Flag to permit or not a control with a live line and a dead
YES, NO
LLBD bus for a “normal close” operator control.
MAN CLO Flag to permit or not a control with a dead line and a dead
YES, NO
LDBD bus. for a “normal close” operator control.
AUTO CLO Flag to permit or not the locking in case of auto-recloser
YES, NO
LCK control.
AUTO CLO Flag to permit or not a control with a dead line and a live
YES, NO
LDBL bus in case of auto-recloser control.
AUTO CLO Flag to permit or not a control with a live line and a dead
YES, NO
LLBD bus in case of auto-recloser control.
AUTO CLO Flag to permit or not a control with a dead line and a dead
YES, NO
LDBD bus. in case of auto-recloser control.
AR
Circuit
breaker name
FIRST CYCLE [100;5000](10) Time between the first protection trip and the Circuit
MONO (ms) Breaker close order for a 1 phase trip.
FIRST CYCLE [100;60000](10) Time between the first protection trip and the Circuit
TRI (ms) Breaker close order for a 3 phases trip.
SECOND [1000;3600000] Time between the second protection trip and the Circuit
CYCLE (1000)(ms) Breaker close order.
[1000;3600000] Time between the third protection trip and the Circuit
THIRD CYCLE
(1000)(ms) Breaker close order.
FOURTH [1000;3600000] Time between the fourth protection trip and the Circuit
CYCLE (1000)(ms) Breaker close order.
RECLAIM [1000;600000] Time during which the Circuit Breaker must remain closed
TIME (1000)(ms) to consider that the reclose has succeeded.
1012 C264/EN UM/E50.5

Available
Values or
[min;max](step)
(unit)
Time during which the Circuit Breaker must remain closed
[1000;600000]
UNLOCK TIME after a manual close or reinit message in the lock state to
(1000)(ms)
consider that the unlocked has succeeded
Time during which the Circuit Breaker must remain closed
MAN CLOSE [1000;600000] after a manual close in clear state to consider that the
TIME (1000)(ms) closure has succeeded and to avoid locking definitively in
case of trip.
Indicates how to use the autorecloser with 1 phase trip:
0: AR_NOT_USED
1PH TRIP 1: AR_1P
0 to 4
SCHEME 2: AR_1P3P
3: AR_1P3P3P
4: AR_1P3P3P3P
Indicates how to use the autorecloser with 3 phases trip:
0: AR_NOT_USED,
3PH TRIP 1: AR_3P,
0 to 4
SCHEME 2: AR_3P3P,
3: AR_3P3P3P,
4: AR_3P3P3P3P
DEVICE
short name
1
…
short name
N
TIME OPEN [0;1000](1)(ms) Time duration for the open contact.
TIME CLOSE [0;1000](1)(ms) Time duration for the close contact.
BI
Bi 1
…
Bi N
MOTION00 Time of non complementarity filtering in the state 00: only
[0;600](100)(ms)
FILT use for double digital input.
MOTION11 Time of non complementarity filtering in the state 11: only
[0;600](100)(ms)
FILT use for double digital input.
PERS OPEN [0;1200](100)
Time of persistence filtering in the state Open or 0
FILT (ms)
C264/EN UM/E50.5 1013

Available
Values or
[min;max](step)
(unit)
PERS CLOSE [0;1200](100)
Time of persistence filtering in the state Close or 1
FILT (ms)
TOGGLING
YES, NO Flag to validate or inhibit the The toggling option.
OPTION
MV
Mv 1
…
Mv N
HYSTERESIS [1;50](1)(%) % of hysteresis applied on thresholds.
DEADBAND [1;50](1)(%) % of variation within the Analogue Input is not transmitted.
[Min;Max](0.01) Low low low threshold (Lowest threshold of the analogue
THRESHOLD 1
(XXX) input)
[Min;Max](0.01)
THRESHOLD 2 Low low threshold
(XXX)
[Min;Max](0.01)
THRESHOLD 3 Low threshold
(XXX)
[Min;Max](0.01)
THRESHOLD 4 High threshold
(XXX)
[Min;Max](0.01)
THRESHOLD 5 High high threshold
(XXX)
[Min;Max](0.01) High high high threshold (highest threshold of the analogue
THRESHOLD 6
(XXX) input)
COMM.
PORT
Com 1
…
Com 4
Baudrate of the communication port among:
BAUDRATE baudrate * 50,100,200,300,600,1200,2400,4800,9600,19200,38400,
56000.
NB STOP BIT 1, 2 Number of stop bits
NB BIT PER
7, 8 Number of bits per character
CHAR
PARITY odd, even, none Parity
HMI
MAIN
1014 C264/EN UM/E50.5

Available
Values or
[min;max](step)
(unit)
Time after which the Menu tree is automatically left if there
EXIT MT TIME [5;300](1)(s)
is no pressed button.
BACK LIGHT Time after which the back light disappears if there is no
[5;300](1)(s)
DELAY pressed button.
SELECT EXIT
[5;300](1)(s) Maximum time between selection and execution orders.
TIME
BYPASS
[20;120](1)(s) Time after which a bypass is automatically deselected.
DELAY
BAY
Bay 0
…
Bay N
SBMC
YES, NO Flag to validate or inhibit the display of the SBMC mode
DISPLAY
DISPLAY DEV Flag to validate or inhibit the display of the Name od
YES, NO
NAME Devices in the Bay Panel.
PARITY odd, even, none Parity
C264/EN UM/E50.5 1015

9.2 Setting via MiCOM S1 - PACiS software and CAT application

MiCOM S1 - PACiS software provides the facility to online view and edit the parameters of
MiCOM C264. Refer to the MiCOM S1 - PACiS User Guide for installation and use of the
MiCOM S1 - PACiS software.
Settings updated via MiCOM S1 - PACiS are sent to MiCOM C264 using Computer
Administration Tool (CAT) application. Refer to C264/EN IN (installation) chapter of C264 user
manual for CAT installation.
The setting of MiCOM C264 computer is performed using a file transfer mechanism. The setting is
allowed only if the MiCOM C264 is in Operational mode. In case of MiCOM C264 redundancy, the
setting can be performed only on the Active computer (to avoid discrepancy between both
computers parameters, a manual load of settings has to be realized on the backup MiCOM C264).
9.2.1 General presentation of parameters in MiCOM S1 - PACiS

The hierarchy of parameters in MiCOM S1 - PACiS is:
• OP.PARAMETERS: global MiCOM C264 parameters in read-only mode (database version,
IP address, computer name, …)
• CONFIGURATION : general parameters for protective functions
• PROTECTION GROUP 1 : parameters for each protective function
• PROTECTION GROUP 2 : parameters for each protective function
• AUTOMAT.CONTROL
• Synchrocheck
• AVR
• Auto-recloser bay 1
• Auto-recloser bay N
• ISaGRAF® Automatism 1
• …
• ISaGRAF® Automatism N
• PSL Automatism 1
• …
• PSL Automatism M
The description of each parameter can be seen in below figure.
1016 C264/EN UM/E50.5

Built in functions like ISaGRAF®, PSL automatism, AVR and Auto-Recloser are configured in
EPAS-SCE. Only parameters of configured functions are visible and editable
inMiCOM S1 - PACiS.
It is possible to set the following functions:

• Automates' built-in as autorecloser, AVR (if applicable), synchrocheck (if applicable),
protective function implemented for EPAS
• ISaGRAF®: (float or integer threshold & Boolean)
• Two kinds of parameters in FBD: The timeout used for (Ton / Toff) and the parameter
(Boolean) validation
The file .set can be found in the Settings folder of the database (.zip).
9.2.1.1 ARPCCN parameters

ARPCCN parameters are listed hereafter:
• Numbers of fast cycle for earth fault min = 0 , max = 1 step = 1 cycle step
• Numbers of slow cycle for earth fault min = 0 , max = 2 , step = 1 cycle step
• Numbers of fast cycle for phase fault min = 0 , max = 1 , step = 1 cycle step
• Numbers of slow cycle for phase fault min = 0, max = 2, step = 1 cycle step
• Reclaim time fast cycle, min = 10000 , max = 15000 , step = 1000
• Reclaim time slow cycle, min = 3000 , max = 10000 , step = 1000
• Reclaim time manual close , min = 10000, max = 20000 , step =1000
• Timer cycle fast earth , min = 100, max = 500 , step =1
C264/EN UM/E50.5 1017

• Timer cycle slow1 earth , min = 10000, max = 30000 , step =1000
• Timer cycle slow2 earth , min = 10000, max = 30000 , step =1000
• Timer cycle fast phase , min = 100 , max = 500 , step =1
• Timer cycle slow1 phase , min = 10000 , max = 30000 , step =1000
• Timer cycle slow2 phase , min = 10000 , max = 30000 , step =1000
9.2.1.2 AVR parameters

AVR parameters are listed hereafter:
1018 C264/EN UM/E50.5

To view the range allowed for each parameter, refer to the chapter AP.
9.2.1.3 Auto-Recloser (Type 1) parameters

Auto-Recloser (Type 1) parameters are listed hereafter:
• Ist period triphased time min = 100, max = 60000, step = 10
• 2nd period triphased time min = 1000, max = 3600000, step = 10
• 3rd period triphased time min = 1000, max = 3600000, step = 1000
• Reclaim delay time min = 1000, max = 600000, step = 1000
• Inhibition delay min = 1000, max = 3600000, step = 1000
• Unlock delay min = 1000, max = 600000, step = 1000
• Manual close delay min = 1000, max = 600000, step = 1000
C264/EN UM/E50.5 1019

• Functioning mode (1 ph trip) types = 1P, 1P-3P, 1P-3P-3P, 1P-3P-3P-3P
• Functioning mode (3 ph trip) types = 3P, 3P-3P, 3P-3P-3P, 3P-3P-3P-3P
9.2.1.4 I²t parameters

I²t parameters are listed hereafter:
9.2.1.5 Internal Synchrocheck (Type 1) parameters

Internal Synchrocheck (Type 1) parameters are listed hereafter:
SCHEMES
Close with synchro: Coupling and locking = YES/NO

Close with synchro: locking = YES/NO
Close with synchro: Line Dead and Bus Live = YES/NO
Close with synchro: Line live and Bus Dead = YES/NO
Close with synchro: Line Dead and Bus Dead = YES/NO
Close : Locking = YES/NO
Close : Line Dead and Bus Live = YES/NO
Close : Line live and Bus Dead = YES/NO
Close : Line Dead and Bus Dead = YES/NO
Autorecloser Locking = YES/NO
1020 C264/EN UM/E50.5

Autorecloser Line Dead and Bus Live: = YES/NO

Autorecloser Line live and Bus Dead: = YES/NO
Autorecloser Line Dead and Bus Dead = YES/NO
TIMINGS
Parameters T1 : Presence deltas test duration : min = 200, max =10000 ,step = 20
Parameters T2 : Presence test duration : min = 200, max =10000 ,step = 20
Parameters T3 : absence deltas test duration : min = 200, max =10000 ,step = 20
Parameters Ta : close time of circuit breaker : min = 0, max = 1000,step = 10
Close with synchro scheme delay : min = 1, max =3600 , step = 1
THRESHOLDS
Line voltage over threshold: min= 0, max = 100,step = 1

Line voltage under threshold: min= 0, max = 100,step = 1
Bus voltage overthreshold: min= 0, max = 100,step = 1
Bus voltage underthreshold: min= 0, max = 100,step = 1
Voltage delta threshold for locking: min= 0, max = 100,step = 1
Minimum frequency for locking: min= 45.5, max = 59.5,step = 0.1
Maximum frequency for locking: min= 50.5, max = 66, step = 0.1
Frequency delta threshold for locking: min= 0.02, max = 0.1,step = 0.01
Phase delta threshold for locking: min= 0, max = 90,step = 1
C264/EN UM/E50.5 1021

9.2.1.6 FBD parameters

Depending on the individual EPAS-SCE attribute ‘’Editable in MiCOM S1 - PACiS’’, each timer
value can be set or not, visible or dimmed.
Editable parameters of FBD Timer
Editable parameters of Boolean
FBD Boolean: True/false
1022 C264/EN UM/E50.5

9.2.1.7 Activate de-Activate protection function trip
The AUTOMAT.CONTROL section allows to activate/de-activate the protection function if at least

one trip relay has been defined in the EPAS-SCE to the TMU210 (DO#1 or DO #5). See an
example below:
9.2.2 Upload a setting file to MiCOM C264

This section describes the procedure to upload settings file to MiCOM C264.
WARNING
RISK OF SYSTEM BEHAVIOR MISMATCH
Check the consistency of all settings before any settings upload.
Failure to follow these instructions can result in serious injury or equipment damage.
CAUTION
UNEXPECTED PLC (ISAGRAF®) EXECUTION OF CONTROL
Carefully evaluate the impact of PLC (ISaGRAF®) setting modification before uploading a
setting file.
C264/EN UM/E50.5 1023

CAUTION
UNEXPECTED PSL (FBD) EXECUTION OF CONTROL
Carefully evaluate the impact of PSL (FBD) setting modification before uploading a setting file.
The transfer operation needs MiCOM S1 - PACiS and CAT applications. The CAT transfers the
settings file.
Stage Procedure Information

The settings file (.set) is open with
MiCOM S1 - PACiS and parameters
Export settings file with
A are updated. Parameters are
MiCOM S1 - PACiS
exported to generate settings file
(.val).
Start CAT and establish the
B Computer connection with CAT
computer connection
C Transfer settings file with CAT Transfer settings file with CAT
1024 C264/EN UM/E50.5

A. Export settings file with MiCOM S1 - PACiS, please follow instructions:
Step Action
Export settings file (.val) with MiCOM S1 - PACiS:
Select Convert > Set Settings (.set => .val)
After generation, press OK
B. Establish MiCOM C264 computer Connection with CAT, please follow instructions:
Step Action
Check CAT Software of the current MiCOM C264 computer release is
already installed on PC:
From the Windows start menu folder “PACiS”, find CAT software
C264/EN UM/E50.5 1025

Step Action
Start CAT Software :
Run the CAT Software
A disclaimer message is displayed, choose I Agree button to continue
Recommendation: If Antivirus software is not detected by CAT Software

on PC, an Antivirus Message Box is displayed to notice operator cyber
security risk. We recommend use Antivirus Avira Antivir Professional
software to reduce the risk.
1026 C264/EN UM/E50.5

Step Action
Establish MiCOM C264 computer connection with CAT :
Refresh button
Select the target computer to upgrade on Devices available on

network list
Click Connect to this device button
C264/EN UM/E50.5 1027

Step Action
NOTE: Red color indicates a correct connection with device selected.
WARNING
RISK OF UNEXPECTED SYSTEM BEHAVIOR
Ensure that the targeted MiCOM C264 selected by user to upload its
settings file, is the right device.
Failure to follow these instructions can result in death, serious

injury or equipment damage.
Choose Profile (Engineer)
Enter Password (none by default)
C. Transfer settings file with CAT to MiCOM C264, follow instructions:
1028 C264/EN UM/E50.5

Step Action
Select « Edit settings » function (1)
Select the settings file (.val) generated by MiCOM S1 - PACiS (2)
Click “Send this settings file” button (3)
Confirm, click Yes
Uploading settings file is indicated via the progress bar
2 Wait a few seconds the end of transfer
9.2.3 Download a setting file from MiCOM C264

This section describes procedure to download settings file from MiCOM C264.
C264/EN UM/E50.5 1029

The transfer operation needs both MiCOM S1 - PACiS and CAT applications. The CAT is used to
transfer settings file.
Stage Procedure Information

Start CAT and establish the
A Computer connection with CAT
computer connection
B Transfer settings file with CAT Transfer settings file (.val) with CAT
Import settings file with Settings file (.val) is imported with
C
MiCOM S1 - PACiS MiCOM S1 - PACiS
1030 C264/EN UM/E50.5

A. Establish MiCOM C264 computer Connection with CAT, please follow instructions:
Step Action
Check CAT Software of the current MiCOM C264 computer release is
already installed on PC:
From the Windows start menu folder “PACiS”, find CAT software
Start CAT Software :
Run the CAT Software
A disclaimer message is displayed, choose I Agree button to

continue
Recommendation: If Antivirus software is not detected by CAT Software

on PC, an Antivirus Message Box is displayed to notice operator cyber
security risk. We recommend use Antivirus Avira Antivir Professional
software to reduce the risk.
C264/EN UM/E50.5 1031

Step Action
Establish MiCOM C264 computer connection with CAT :
Refresh button
Select the target computer to upgrade on Devices available on

network list
Click Connect to this device button
Red color indicates a correct connection with device selected.
1032 C264/EN UM/E50.5

Step Action
Choose Profile (Engineer)
Enter Password (none by default)
B. Transfer settings file with CAT from MiCOM C264, follow instructions:
C264/EN UM/E50.5 1033

Step Action
Select « Edit settings » function (1)
Select the location for the settings file (.val) (2)
Click “Receive settings file” button (3)
Confirm, click Yes, overwrite this file Button
Downloading settings file is indicated via the progress bar
2 Wait a few seconds the end of transfer
C. Import settings file with MiCOM S1 - PACiS, please follow instructions:
1034 C264/EN UM/E50.5

Step Action
Import settings file (.val) with MiCOM S1 - PACiS:
Select Convert > Get Settings Settings (.val => .set)
9.2.4 Setting transfer’s dependence on computer modes

In “active” or ‘test” mode, the upload/download description previously described applies.
Otherwise, MiCOM C264 denies the transfer of the setting file via CAT application.
In case of redounded computer, setting transfer is available on the “active” computer. In order to
upload/download settings on the “inactive” one, stop the “active” MiCOM C264: that causes the
inactive MiCOM C264 to become active.
There is no automatic consistency check of the two setting files : this is to be verified by operator.
9.2.5 MiCOM S1 - PACiS acknowledge

Delete this text and replace it with your own content.
Receipt value MiCOM S1 - PACiS message

0 Setting done
1 Incorrect C264 DB Version revision
2 Number of protections incoherent with DB
3 No setting file in the C264
4 FTP server problem\nVerify that the FTP client is launched & try again
5 C264 internal error
6 C264 incorrect number
7 Setting impossible, command running
8 Error IED address
9 Incompatible data structure
10 IED setting failed
11 Compatibility error between C264 and SCE
12 Number of columns of the .VAL file incorrect
C264/EN UM/E50.5 1035

Receipt value MiCOM S1 - PACiS message

13 Error : label too long
14 Error PROTECTIONS C264 : Value not between MIN and MAX
15 Error ELECTRE d : Value not between MIN and MAX
16 Error FBD : Value not between MIN and MAX
17 Error ISAGRAF : Value not between MIN and MAX
18 Error AUTO RECLOSER : Value not between MIN and MAX
19 Error AUTO RECLOSER PCCN : Value not between MIN and MAX
20 Error SYNCHROCHECK : Value not between MIN and MAX
21 Error AVR : Value not between MIN and MAX
22 Error PROTECTIONS C264 : Verification phase incorrect
23 Error ELECTRE d : Verification phase incorrect
24 Error FBD : Verification phase incorrect
25 Error ISAGRAF : Verification phase incorrect
26 Error AUTO RECLOSER : Verification phase incorrect
27 Error AUTO RECLOSER PCCN : Verification phase incorrect
28 Error SYNCHROCHECK : Verification phase incorrect
29 Error AVR : Verification phase incorrect
30 Error : File OK but a problem occurred during file copy
31 Error : Setting file for CPU3 sent to a CPU2
32 Error in file checksum
33 Error : Micom S1 task not present
34 Error : Trip in progress
1036 C264/EN UM/E50.5

MiCOM C264 - User Manual 10 Communication
10 Communication
10.1 SCP Communication 1041

10.1.1 Communication on Station bus 1041
10.1.1.1 Finality 1041
10.1.1.2 Inputs 1042
10.1.1.2.1 Information: MiCOM C264 application / SCP 1042
10.1.1.2.2 Information: SCP / MiCOM C264 application 1042
10.1.1.3 Supported services 1042
10.1.1.4 Supported data objects 1042
10.2 Inter-rack Communication 1044
10.2.1 Main1-Main2 communication 1044
10.2.2 Main-Extension communication 1044
10.3 SCADA Communication 1045
10.3.2 SCADA common functionality 1045
10.3.2.1 Interface to SCADA 1045
10.3.2.2 BCU 1045
10.3.2.2.1 Input 1045
10.3.2.2.2 Output 1046
10.3.2.3 Behaviour and specific treatments 1046
10.3.2.3.1 Initialization 1046
10.3.2.3.2 General interrogation 1046
10.3.2.3.3 Clock synchronisation 1047
10.3.2.3.4 Database downloading and switching 1047
10.3.2.3.5 Local/remote mode 1047
10.3.2.3.6 Taking Control 1047
10.3.2.3.7 SBMC mode 1047
10.3.2.3.8 Redundancy 1048
10.3.2.3.9 Automatic synchrocheck 1048
10.3.2.4 Data sent to SCADA 1048
10.3.2.4.1 Binary inputs 1048
10.3.2.4.3 Counters 1048
10.3.2.4.4 Tap position 1048
10.3.2.4.5 Computer disturbance file 1049
10.3.2.4.6 Sequence Of Events file (SOE) 1049
10.3.2.4.7 Synchronization status 1049
10.3.2.5 Data sent to MiCOM C264 1049
10.3.2.5.1 Digital Controls or setpoints 1049
10.3.2.5.2 Counter commands 1050
C264/EN UM/E50.5 1037

10 Communication MiCOM C264 - User Manual
10.3.3 Slave DNP3 profile (serial or over IP) 1050

10.3.4 Slave IEC 60870-5-101 profile 1050
10.3.5 Slave IEC 60870-5-104 Server profile 1050
10.3.6 Slave Modbus (MODICON) profile 1050
10.4 IED Communication 1051
10.4.2 IED Common functionality 1051
10.4.2.1.1 Input 1051
10.4.2.1.2 Output 1052
10.4.2.2 Behavior 1052
10.4.2.2.1 Network supervision 1052
10.4.2.2.2 Time synchronization 1052
10.4.2.2.3 Polling of IED 1053
10.4.2.2.4 Monitoring of an IED 1053
10.4.2.3.3 Counters 1057
10.4.2.3.4 Tap position 1057
10.4.2.3.5 Disturbance File 1057
10.4.2.4.1 Controls 1057
10.4.2.4.2 Setpoints 1058
10.4.2.5 Tunneling 1058
10.4.3 MODBUS communication 1059
10.4.3.1 Scope of this section 1059
10.4.3.2 Generic MODBUS Communication 1059
10.4.3.2.1 Polling and connection test 1060
10.4.3.2.2.1 AIs 1060
10.4.3.2.2.2 DIs 1061
10.4.3.2.3.1 Connection check 1061
10.4.3.2.3.3 DOs 1062
10.4.3.2.4 Error management 1062
10.4.3.2.5 Limits and specifications 1062
10.4.3.3 Schneider Electric MODBUS COMMUNICATION 1062
10.4.3.3.1 Status byte 1063
10.4.3.3.1.1 Events buffer management 1064
10.4.3.3.1.2 M300 1064
10.4.3.3.1.3 MiCOM S40 (Px4x series) 1064
1038 C264/EN UM/E50.5


10.4.3.3.2.1 AIs 1065
10.4.3.3.2.2 M300 1066
10.4.3.3.2.3 MiCOM Px2 series and Px4 series 1068
10.4.3.3.2.4 DIs 1069
10.4.3.3.2.5 IED synchronized 1069
10.4.3.3.2.6 IED NOT synchronized 1069
10.4.3.3.2.7 Disturbance files 1071
10.4.3.3.2.8 M300 1073
10.4.3.3.2.9 MiCOM Px2 series and MiCOM Px4 series 1074
10.4.3.3.2.10 Events 1079
10.4.3.3.2.11 File upload 1083
10.4.3.3.3.2 Commands 1088
10.4.3.3.3.3 AOs 1093
10.4.3.3.3.4 Settings of the current relays 1094
10.4.3.3.3.5 Error management 1094
10.4.3.3.3.6 Limits and specifications 1095
10.4.3.4 IED SPECIFIC MODBUS 1096
10.4.3.4.1 M230 1096
10.4.3.4.2 Rish Pro M01 1097
10.4.3.4.3 Flexgate 1099
10.4.3.4.4 SEPAM 1100
10.4.3.4.5 WAGO 1101
10.4.4 DNP 3.0 Communication 1101
10.4.4.1.1 Input 1101
10.4.4.1.2 Output 1102
10.4.4.2 Behavior 1102
10.4.4.5 Master DNP3 Profile 1104
10.4.4.6 DNP3 Level 3 Implementation Table 1104
10.4.5.1.1 Input 1110
10.4.5.1.2 Output 1111
10.4.5.2 Behavior 1112
10.4.5.2.2 Polling 1112
10.4.5.2.3 IED monitoring 1112
10.4.5.2.4 Tunneling mode 1112
C264/EN UM/E50.5 1039

10.4.5.2.5 Station Interlocking 1112

10.4.5.2.6 REG D 1113
10.4.5.2.7 Tapcon260 1113
10.4.5.3.3 Bitstring 32-bits : 1114
10.4.5.3.4 Analog protection signal (ASDU 49) : 1114
10.4.5.3.5 Energy counter (ASDU 79) : 1114
10.4.5.4.1 Controls 1115
10.4.5.4.2 Setpoints Controls : 1116
10.4.5.4.3 Read protection parameter : 1116
10.4.5.4.4 ASDU 232 / 105 management 1116
10.4.6.1 Purpose 1117
10.4.7.1 Purpose 1117
1040 C264/EN UM/E50.5

10.1 SCP Communication

10.1.1 Communication on Station bus
10.1.1.1 Finality
This item describes IEC 61850-8-1 Editions 1 and 2 supported by MiCOM C264.
Certified documents applicable for MiCOM C264 Server are listed below:
DOCUMENTS REFERENCES
Model Implementation Conformance
Statement (MICS) for the IEC 61850-8-1 MiCOM C264 version D2.06 - MICS - Issue A3
edition 2 interface document
Protocol Implementation Conformance MiCOM C264 version D4.x - PICS - Issue A7,
Statement (PICS) for the IEC 61850-8-1
edition 2 interface MiCOM C264 version D4.x - PICS - Issue A7
Protocol Implementation eXtra Information for

MiCOM C264 version D2.06 - PIXIT - Issue A6
Testing (PIXIT) of the IEC 61850 document
Tissue Implementation Conformance
Statement (TICS) for the IEC 61850 interface MiCOM C264 version D2.06 - TICS - Issue A5
document
Wiring and Server settings for automated
MiCOM C264 - Wiring_Server Settings for
KEMA IEC 61850 conformance tests
KEMA IEC 61850 conformance tests - Issue C
document
The ACSI conformance statements are used to provide an overview and details about
MiCOM C264 with EPAS:
• ACSI basic conformance statement
• ACSI models conformance statement
• ACSI service conformance statement
The statements specify the communication features mapped to IEC 61850-8-1 Edition 2. Please
refer to above MiCOM C264 PICS document.
It is possible to bypass order from Client to MiCOM C264, however with standard IEC 61850-8-1
Editions 1 and 2, BYPASS attribute is not allowed and it is replaced by CHECK attribute.
Specific bypass attributes suppressed:

• BYPASS_LOCKING
• BYPASS_MODE
• BYPASS_UNIQUENESS
• BYPASS_AUTOMATION
• BYPASS_ALL
Bypass attributes are remaining:
C264/EN UM/E50.5 1041

• BYPASS_INTERLOCK is replaced by NO CHECK_INTERLOCK
• BYPASS_SYNCHROCHECK is replaced by NO CHECK_SYNCHROCHECK
• BYPASS_NONE is replaced by NO CHECK_NONE
10.1.1.2 Inputs
10.1.1.2.1 Information: MiCOM C264 application / SCP
The type of information that can be transmitted are:
• Changes of state of binary inputs
• Measurements (Analogue or CT/VT)
• Counters
• Controls
• Control acknowledgements
• Time synchronisation message
• Records (Event, fault, disturbance)
• MiCOM C264 information (Init. report, Operating mode, control mode, Date)
10.1.1.2.2 Information: SCP / MiCOM C264 application

The type of information that can be transmitted are:
• Changes of state of binary inputs
• Measurements (Analogue or CT/VT)
• Counters
• Controls
• Control acknowledgements
• Time synchronisation message
• Request for records
• Database downloading
10.1.1.3 Supported services

Services supported by the IEC 61850 agency integrated in the MiCOM C264 are listed in the
ACSI service conformance statement defined in Table A.3 of document MiCOM C264 PICS.
10.1.1.4 Supported data objects

The following table describes the common class supported by the IEC 61850 agency integrated in
the MiCOM C264:
Common Class Comment Client support Server support

Status
SPS Single input status YES YES
DPS Double input status YES YES
1042 C264/EN UM/E50.5

Common Class Comment Client support Server support

INS Integer input status YES YES
ACT Protection activation information YES YES
Directional protection activation
ACD YES YES
information
Measurements
MV Measurement value YES YES
CMV Complex measurement value YES YES
WYE 3 phase + N measurement YES YES
DELTA Phase to phase measurement YES YES
Counters
BCR Binary counter YES YES
Control
SPC Single point control YES YES
DPC Double control output YES YES
BSC Binary step control YES YES
APC Analogue output YES YES
INC Integer control output YES YES
ISC Integer step control output YES YES
Description
LPL Logical node name plate YES YES
DPL Device name plate YES YES
Report Control
Block
URCB Unbuffered report control block YES YES
BRCB Buffered report control block NO YES
C264/EN UM/E50.5 1043

10.2 Inter-rack Communication
A MiCOM C264 is used as a main rack connected to a cluster of MiCOM C264 extensions over an
Ethernet IEC 61850 network.
Tunnelling is not possible in this architecture and connecting IEDs directly on any MiCOM C264
either.
No CT/VT connected on extensions.
A similar branch can be installed for redundancy purpose. In this case, no AOU board is allowed.
10.2.1 Main1-Main2 communication

See FT chapter.
10.2.2 Main-Extension communication

An Ethernet IEC 61850 network supports the same objects and services as the SCP
communication.
1044 C264/EN UM/E50.5

10.3 SCADA Communication

10.3.1 Overview
This Chapter describes protocols implementation inside MiCOM C264 for communication via
Telecontrol network.
SCADA System is connected to a MiCOM C264 through networks using various Slave protocols:
Slave Protocol MiCOM C264 BCU

DNP3 Serial, TCP/IP & UDP
MODBUS Serial
IEC 60870-5-101 Serial
IEC 60870-5-104 TCP/IP
Multi protocol management (MiCOM C264 only):

• Four (4) different SCADA protocols can run simultaneously. Four (4) on Ethernet and two (2)
on Serial. Each protocol has an independant configuration and may have same data.
• In IEC 60870-5-104 protocol, from the SCADA side, up to four (4) ports can be defined,
corresponding to one active port and three backup ports. IP addresses are configured for
each IEC 60870-5-104 client. Each IEC 60870-5-104 protocol can manage up to four (4)
clients simultaneously.
• In DNP3 over IP (TCP/IP & UDP) is supported over two (2) Ethernet ports. Each DNP3
protocol can manage one (1) client only. All DNP3 on IP features are the same than DNP3
serial features.
Common features to all SCADA communication and all protocols are specified below.
Specific features to each protocol are specified in subsequent paragraphs.
10.3.2 SCADA common functionality

10.3.2.1 Interface to SCADA
This paragraph describes the exchange of data between the “SCADA communication” function
and the Master SCADA. It includes two sub-paragraphs:
• Inputs: data received from SCADA.
• Outputs: data sent from the “SCADA communication” function to SCADA.
For each kind of protocol, it is indicated if the data is treated or not.
10.3.2.2 BCU
10.3.2.2.1 Input
Data DNP3 T101 T104 MODBUS

Remote link initialisation Treated Treated Treated Treated
General interrogation Treated Treated Treated Not Treated
C264/EN UM/E50.5 1045


Control Treated Treated Treated Treated
Setpoint Treated Treated Treated Treated
Time synchronisation Treated Treated Treated Not Treated
Database (download) Not Treated Not Treated Not Treated Not Treated
10.3.2.2.2 Output

Digital input Treated Treated Treated Treated
Dated Digital input Treated Treated Treated Not Treated
Measurement (Events) Treated Treated Treated Not Treated
Measurement (Cyclical) Treated Treated Treated Treated
Counter Treated Treated Treated Treated
Tap position Treated Treated Treated Treated
Control acknowledgement Treated Treated Treated Treated
Setpoint acknowledgement Treated Treated Treated Treated
Slow
MiCOM C264
MiCOM C264 Disturbance Not Treated waveform Not Treated
Disturbance
only
Sequence Of Event file Not Treated Treated Treated Not Treated
10.3.2.3 Behaviour and specific treatments

In subsequent paragraphs, the master station (e.g.: SCADA) is referred to as the controlling
station.
10.3.2.3.1 Initialization
There is a running database for each SCADA link. At initialization, a GI is performed on the
application in order to initialize these databases.
The GI sequence consists of different requests to the MiCOM C264 application in order to get the
value and state of all data (Binary input, measurement, counter, step position indication).
10.3.2.3.2 General interrogation

The Outstation interrogation function is used for updating the controlling station after the internal
station initialisation procedure, or when the controlling station detects a loss of information, or
when the link layer connection has been re-established. The general interrogation function of the
controlling station requests the MiCOM C264 to transmit the actual values of all addressed
datapoints.
The MiCOM C264 marks the end of the general interrogation procedure by sending an indication
to the controlling station when the protocols allow it.
In multirack application and in redundant configuration, the main rack becomes the master rack
on General Interrogation reception.
1046 C264/EN UM/E50.5

10.3.2.3.3 Clock synchronisation

Clock in MiCOM C264 may be synchronised by the controlling station.
The clock can be synchronised by other means: external clock, Master Clock, operator. Only one
source will be selected at a given time. This selection is performed by the clock synchronisation
function based on configuration and priority level. However the controlling station is not informed
of this fact and must continue to send clock synchronisation commands.
The controlling station must perform the correction made on the time sent in synchronisation
commands.
10.3.2.3.4 Database downloading and switching

This function is only implemented in IEC 60870-5-101 and IEC 60870-5-104 protocols. The
SCADA can download a database and only a database. Then the type of file is 1 (Transparent file)
and the IOA (information object address) must be 1. The database downloaded will be the
standby database.
To switch over this database, the SCADA must send a reset process command (C_RP_NA_1
(105)) with cause of transmission equal to 6 (activation) and QRP field set to 1 (general reset of
process)
10.3.2.3.5 Local/remote mode

A substation or a bay can be in local or remote mode. When it is in local mode it can not be
controlled remotely and when it is in remote mode, it can not be controlled locally.
Each Mode can be associated to a binary input.
10.3.2.3.6 Taking Control

A Substation can be configured in taking control mode. This means:
• At a given time, only one SCADA can send controls to the substation (the one which has the
control).
• To be allowed to send controls, a SCADA must take control of the substation by sending a
specific command to the MiCOM C264.
On each SCADA link, there is a binary input indicating if the corresponding SCADA has the
control of the substation.
On reception of a Taking Control command, the MiCOM C264:

• Puts the substation in Remote mode (if it was in Local Mode)
• Gives the control to the (last) SCADA which asks for it
• Reset the “Taking Control Binary input” of the SCADA which had previously the control
• Set the “Taking Control Binary input” of the SCADA which asks the control
If the take control command is set for a SCADA, MiCOM C264 should refuse all commands from
other SCADAs.
10.3.2.3.7 SBMC mode

This mode is used to test a substation while it is in Remote mode. As this mode is a simul mode,
MiCOM C264 won’t send all changes of state to SCADA.
C264/EN UM/E50.5 1047

When bay turns to SBMC mode, MiCOM C264 will send to SCADA all concerned data (configured
Bay Based in the EPAS-SCE) at specific states defined in the EPAS-SCE for the management of
SBMC.
For those data, change of state won’t be transmitted, but will be memorized by MiCOM C264
while the Bay is in SBMC mode.
When the Bay returns to Non SBMC mode, MiCOM C264 will send the current state of any data
that has changed whilst the Bay has been in SBMC mode.
10.3.2.3.8 Redundancy
Serial links can be configured as redundant. In this case, SCADA can send requests on both
serial links: “main link “or “redundant link”.
MiCOM C264 always responds on the link used by SCADA for requesting the slave
10.3.2.3.9 Automatic synchrocheck

SCADA can send control to synchronised circuit breakers with a facility to bypass the
synchrocheck.
10.3.2.4 Data sent to SCADA

After the initialization sequence, MiCOM C264 Slave sends the state of all of its data to the
SCADA. The current state of data is sent as state or as change of state messages, depending on
the protocol.
The data, which can be sent to SCADA, is detailed in the paragraphs below.
10.3.2.4.1 Binary inputs

Binary inputs can be sent as states or as changes of state depending on the protocol.
A binary input can be associated with a single point or a double point.
NOTE: Multipoint status is not treated.
10.3.2.4.2 Measurements
Measurements can be sent in various formats: float, integer, normalized, scaled…
Measurements can be sent as periodical messages or as changes of state: variation, threshold,

and invalidity.
The choices of format and mode of transmission are done by configuration according to the
protocol.
10.3.2.4.3 Counters
Counters can be sent as spontaneous messages (changes of state) or on demand (counter
General Interrogation).
The choice whether to use spontaneous messages for a counter is done by configuration,
according to the protocol.
10.3.2.4.4 Tap position

Tap position indication (TPI) can be sent to SCADA as states or as changes of state. The choice
between state or change of state depends on the protocol. If the protocol allows the both, the
choice is done by configuration.
1048 C264/EN UM/E50.5

A digital input can be associated with a single point or a double point.
10.3.2.4.5 Computer disturbance file

Only Slow Wave Form is implemented for IEC 60870-5-101 or IEC 60870-5-104. At the most five
slow wave form files can be available at a time. The IOA of the first file is configured and the
others are consecutive. the type of file is 1 (Transparent file). When a slow wave form file is
available, an ASDU Directory (F_DR_TA_1 (126)) is sent by the computer with cause of
transmission spontaneous (3). The file is already available until a new file is created and replaces
it. The SCADA can identify the file only with its date. The size of file must be lower or equal to the
size of one section
10.3.2.4.6 Sequence Of Events file (SOE)

The SOE is a circular file where Events of the MiCOM C264 are stored. There is one SOE for
each SCADA link.
The Events, which can be stored in SOE, are Binary Input and measurements. The choice is done
by configuration.
Following information in MiCOM C264 configuration are used to manage SOE file:
• For each SCADA protocol
• A flag indicating if SOE file have to be managed
• Identification of the SOE file on the link (Name, Address, …)
• The maximum size of the file
• The percentage of filling from which the MiCOM C264 will try to transmit the SOE file
• For each BI / measurement
• A flag indicating if it must be stored in SOE
Rules for the SOE management are the following:

• At starting of the MiCOM C264, the SOE file is Empty
• When the SOE is full, the oldest Event is deleted and the new one is added
• As soon as the percentage of filling indicated in configuration is reached, the MiCOM C264
tries to up-load the SOE file
• Once a SOE file has been successfully up-loaded, all Event sent are deleted from SOE
10.3.2.4.7 Synchronization status

MiCOM C264 can inform the controlling station about its synchronization status.
According to the protocol, this may be done by a specific message or by a binary input.
10.3.2.5 Data sent to MiCOM C264

SCADA can send data to MiCOM C264. The type of data is described in subsequent paragraphs.
10.3.2.5.1 Digital Controls or setpoints

A control is transmitted to the handling of control sequences function.
At the end of the control sequence an acknowledgment is sent to SCADA if protocol allows it.
C264/EN UM/E50.5 1049

10.3.2.5.2 Counter commands

The commands allowed on counters are:
• Reset of a group of Counters
• Reset of all Counters
• Freeze of a group of counters
• Freeze of all counters
• Read ( frozen value) of a group of Counters
• Read ( frozen value) of all Counters
10.3.2.5.3 Synchronization
Depending on the configuration, MiCOM C264 can be synchronized by a SCADA.
10.3.3 Slave DNP3 profile (serial or over IP)

Please refer to the interoperability documentation EPAS 6 Slave Protocol Profile (SPP) DNP3.
10.3.4 Slave IEC 60870-5-101 profile

Please refer to the interoperability documentation EPAS 6 Slave Protocol Profile (SPP) T101.
10.3.5 Slave IEC 60870-5-104 Server profile

Please refer to the interoperability documentation EPAS 6 Slave Protocol Profile (SPP) T104.
10.3.6 Slave Modbus (MODICON) profile

Please refer to the interoperability documentation EPAS 6 Slave Protocol Profile (SPP)
MODBUS.
1050 C264/EN UM/E50.5

10.4 IED Communication

10.4.1 Overview
Different types of IEDs are connected to a MiCOM C264 through networks using various legacy
protocols:
1. IEC 60870-5-103 (T103)
2. Modbus
3. DNP3
4. IEC 60870-5-101 (T101)
5. IEC 60870-5-104 (T104)
All these networks use a serial link to communicate with IEDs. The DNP3 protocol can in addition
use the Ethernet/IP network. As there are several links on a MiCOM C264, it is possible to have:
• Different protocols running in parallel on different links
• The same protocol on several links
Note: The limitations concerning the protocols are described in the section "MiCOM C264:
Elements limits" on page 76 of the "Technical Data" on page 75 chapter.
All these networks use a Master / Slave protocol where the MiCOM C264 is the Master. So, there
are two kinds of exchange:
• Request / reply
Master emits a request to a slave of its choice and wait for the response. Between master and
slave, only one transaction can be initiated. Then, in order to transmit the same request to two
different slaves, two transactions are required.
• Broadcast
Master transmits a command to all of slaves connected to the network. They perform it
without send any response.
Common features to all IEDs and all protocols are specified hereafter.
Specific features to each protocol are specified in subsequent paragraphs.
10.4.2 IED Common functionality

10.4.2.1 Interface to IEDs
10.4.2.1.1 Input
Data Note
Digital input Treated
Measurement Treated
Default position Depending on the protocol
Counter Treated
Tap position Treated
C264/EN UM/E50.5 1051

Data Note
Control acknowledgement Treated
Setpoint acknowledgement Treated
Alarm Not Treated
Disturbance record Depending on the protocol
Tunnelling Frame response Depending on the protocol
10.4.2.1.2 Output
Data Note
Control Treated
Setpoint Depending on the protocol
Alarm acknowledgement Not Treated
Tunnelling Frame question Depending on the protocol
Time synchronisation Treated
10.4.2.2 Behavior
10.4.2.2.1 Network supervision
The number of networks and IEDs is known by configuration.
Each network is managed independently of the other networks.
The management of a network consists of:

• Initializing the serial line
At start-up of the network monitoring, the serial line has to be initialized according to the
configuration.
• Synchronizing the IEDs connected to the network.
• Polling the IEDs

This polling allows to connect IEDs, to exchange data with IEDs and to monitor the
connection of IEDs.
• Performing the monitoring of the each IED connected to this network.
Each IED is managed independently of the other IEDs. The state of each IED, i.e. connected,
disconnected, is monitored and every change of state is signaled to the MiCOM C264
management function.
10.4.2.2.2 Time synchronization

If the network has to be synchronized, the synchronization is performed in one of two ways:
1. At connection of an IED, a synchronization frame is sent to this IED.
2. Regularly, a synchronization frame is broadcasted on the network.
When this is supported by the IEDs, the calculation of the transmission delay is performed.
The synchronization is a network attribute [not an IED attribute]. That means, that the
synchronization is either sent to all the IEDs, or is not sent.
1052 C264/EN UM/E50.5

10.4.2.2.3 Polling of IED

Once the line is initialized, the MiCOM C264 has to try to connect IEDs and to manage exchanges
of data with each IEDs.
That’s done by polling: cyclically the MiCOM C264 questions each IED one after the other.
The polling manages the following items:

• Sequencing the questioning of the IEDs
• Connection of an IED [when a disconnected IED responds, it becomes Connected]
• Repetitions [if an IED doesn’t answer to a request, this request will be repeated the next cycle]
• Disconnection of an IED [after N questions without answer, an IED becomes Disconnected]
• Maximum time to wait for a response
• Minimum time between two frames on the network
• Sending functional requests to IEDs
Optimization of polling may be done according to the following ideas:

• When an IED is disconnected, it may be questioned only time to time [not all cycles]
• When an IED has important data to transmit [DI], it may be questioned successively several
times
• The maximum time to wait an answer may be configurable
The polling sequencing may be only stopped in the two following cases:
• Time synchronization
Synchronization is done periodically by sending a broadcast frame. After the synchronization
frame has been sent, the polling starts again.
• Remote control to transmit to a slave
Control is a priority request. So, when a control must be sent to an IED, the polling is stopped,
the control is sent, and the polling starts again.
10.4.2.2.4 Monitoring of an IED

Each IED is managed according to the following graph:
C264/EN UM/E50.5 1053

Description of the possible states of an IED:

• NOT_INITIALISED: That’s the initial state of an IED. The MiCOM C264 polls the IED every
cycle in order to connect it.
If the IED responds, it becomes CONNECTED 2 .
If after some attempts the IED doesn’t respond, it becomes DISCONNECTED 1 .
• DISCONNECTED: The IED is disconnected. The MiCOM C264 polls the IED time to time in
order to connect it.
If the IED responds, it becomes CONNECTED 2 .
• CONNECTED: The IED is connected. This state includes several states. When an IED
becomes Connected, it goes to the NOT_SYNCHRONISED state.
• NOT_SYNCHRONISED: The IED has just became Connected. It must be synchronized.
Once it is synchronized, according to the information given by the IED, it becomes IN_
SERVICE 3 or OUT_OF_SERVICE 4 . (This information isn’t available for some protocols. In
this case, the IED becomes IN_SERVICE by default).
• OUT_OF_SERVICE: The IED is connected and says it is Out of service. The MiCOM C264
polls the IED time to time waiting for the IED to become IN_SERVICE 5 .
• IN_SERVICE: The IED is connected and it says it is In Service. This state includes several
states. When an IED becomes In Service, it goes to the GI state.
• GI: The IED is In Service and a General Interrogation is going on.
For each information received during the GI, the information becomes available and its state
is transmitted to the application [see below for more information on GI treatment].
At the end of the GI, the IED goes in the NORMAL state 6 .
1054 C264/EN UM/E50.5

• NORMAL: The IED is In Service and the monitoring of DI, AO and DO are performed.
If a disturbance record becomes present and the MiCOM C264 have enough places to store
the file, the IED goes in the DISTURBANCE state 8 .
If a request to open a tunnel for the IED arrives, it is accepted and the IED goes in the
TUNNELING state 10 .
Time to Time, a GI may be done. In this case the IED goes in the GI state 7 .
• DISTURBANCE: The IED is In Service and a disturbance record is being uploaded.
When the uploading of the disturbance file is finished, the IED goes back in the NORMAL
state 9 .
• TUNNELING: Tunnelling communication is going on.
When the Tunnelling communication is finished, the IED goes back in the NORMAL state 9 .
That shows that GI, Disturbance uploading and tunnelling are mutually exclusive. That is done for
2 reasons:
• To limit the overload of the network
• To suppress interaction between Tunnelling access and MiCOM C264 access.
Description of the transitions between states:

• 0 : Initialization of the transmission.
• 1 : The IED becomes DISCONNECTED.

The disconnection is signaled to the application.
Every data normally received from the IED is marked as unknown and a change of state is
signaled for each one.
• 2 : The IED becomes CONNECTED.
A synchronization frame is sent to it and after, the status of the IED is red.
• 3 : The status of the IED is indicates the IED is In Service.
A General Interrogation is activated.
• 4 : The status of the IED is indicates the IED is Out Of Service.
• 5 : see 3
• 6 : The general Interrogation is finished.
• 7 : A general Interrogation is activated [cyclical GI].
• 8 : A disturbance file is available in the IED and there are enough places to store it in the
MiCOM C264.
A disturbance uploading is activated.
• 9 : End of disturbance file upload.
• 10 : A request to open a communication channel throw tunnelling is received.
• 11 : End of tunnelled communication.
• 12 : Request to send a control command to the IED.

The polling is interrupted and the command is sent as soon as possible.
Initialization procedure
C264/EN UM/E50.5 1055

Initially, all data normally received from an IED is marked as unknown. When an IED is first
connected, a general interrogation request is sent. A table is updated with data received in
response to the general interrogation. When the general interrogation is finished, the content of
the table is sent to the processing functions: binary inputs processing and measurement
treatment. Messages received subsequently are checked against the content of the table and a
change of state message is sent when there is a difference.
General interrogation
A general interrogation is performed:

• at initialization time
• upon reconnection
• Cyclically [optional]
Messages received during the initial general interrogation are not sent to the processing function.
Instead the content of the table is sent at the end of the sequence.
Messages received during a general interrogation performed after the initialization sequence are
sent immediately to the processing function
Some IEDs send a message indicating the end of the response to a general interrogation. When
this message is received, the sequence is considered as finished. If the IED does not send this
message, the MiCOM C264 must check that all data are received.
If all data are not received within a given time another request is sent. This process can be
repeated N times. If the response is still not received after N times a fault message is sent,
however the IED is still polled.
Disturbance File Management
The following rules apply for the management of the Disturbance Files of the IED:
• For each IED, there is an information in the configuration indicating if automatic upload of
Disturbance File has to be done. This indication may be overwritten by a command from the
application.
• When the MiCOM C264 detects that an IED has a Disturbance File ready to be uploaded and
that automatic upload is enabled, it uploads and stores it. When the upload is finished, an
indication is sent to the Upper transmission management to inform it that a Disturbance file is
ready.
• When there is not enough place to store a Disturbance File, the oldest file is deleted.
• The upper transmission management can only get Disturbance files stored in the
MiCOM C264. Once the upper transmission management has treated a file it is deleted.
10.4.2.3 Data received from IEDs

After the initialization sequence, IEDs are polled regularly. Depending on the type of IED the
current state of data can be received as state messages, or as change of state messages.
When a state message is received, the content is checked against the table and if there is a
difference a message is sent to processing functions and the table is updated. In this case, the
MiCOM C264 time stamps the change.
1056 C264/EN UM/E50.5

When a change of state message is received, the table is updated, and the message is
transmitted to processing functions. In this case, the time stamping is made by the IED.
The data, which can be received from IEDs, are detailed in the paragraphs below.
10.4.2.3.1 Digital inputs

Digital inputs can be received as states or as changes of state. The choice between state and
change of state depends on the IED and on the protocol. This is known by configuration.
Even if digital inputs are received as change of state, it is still possible to request data as states for
general interrogations.
The conversion from digital input to binary input is performed by the binary input processing
function. A digital input can be associated with a single point or a double point.
Measurements can be received in various formats: float, binary, BCD, etc. The received value is
converted into an internal format, which is common to all measurements in the MiCOM C264.
Measurements can be received as periodical messages or as changes of state: variation,

threshold, and invalidity.
A message is sent to the processing function whenever a measurement is received from an IED.
10.4.2.3.3 Counters
Counters are treated for DNP3.0
10.4.2.3.4 Tap position

Tap position are treated like measurements
10.4.2.3.5 Disturbance File

MiCOM C264 stores disturbance files as they are sent by IEDs without control of the format of the
Disturbance Files (Comtrade, …).
10.4.2.4 Data sent to IEDs

After the initialization sequence, data can be sent to IEDs. The type of data, which can be sent to
IEDs, is described in subsequent paragraphs.
10.4.2.4.1 Controls
Controls are priority message. The polling sequence must be interrupted in order to send the
control as soon as possible.
Not all IEDs send control acknowledgment. If they do not, an acknowledgment is simulated and
sent to the handling of control sequences function.
When an IED is disconnected [or out of service] a negative acknowledgment is sent.
If the command is a “select before operate” command, the application must send two commands
to the transmission software: the first one for the selection and the second for the execution.
If the command is a double command, the application sends one order, and depending on the
protocol, two cases have to be distinguished:
C264/EN UM/E50.5 1057

• The Double command is referenced only once in the IED Mapping. In this case, if an OPEN
(respectively CLOSE) command is received from the application, the master send an OFF
(respectively ON) order to the IED at the corresponding address.
• The double command is referenced by two addresses in the IED Mapping: one refers to the
Open Contact and the other to the Close Contact. In this case, if an OPEN (respectively
CLOSE) command is received from the application, the master sends an ON order to the IED,
at the address corresponding to the Open Contact (respectively Close Contact).
10.4.2.4.2 Setpoints
SP controls are priority message. The polling sequence must be interrupted in order to send the
SP control as soon as possible.
Not all IEDs send SP control acknowledgment. If they do not, an acknowledgment is simulated
and sent to the handling of SP control sequences function.
When an IED is disconnected [or out of service] a negative acknowledgment is sent.
If the SP commands are always "direct execute" command (no “select before operate”).
For an IED, only one SP command is possible at a time.
10.4.2.5 Tunneling
The serial tunneling enables to connect a lap top computer – which run an IED setting software –
to a serial (RS 232) line of the EPAS computer in order to communicate with an IED connected to
a legacy bus of the EPAS computer.
All serial RS 232 lines of the computer – including the port onto the front panel – can be used for
serial tunneling.
The choice of the serial line to be used for serial tunneling is done by the computer configuration.
The cable dedicated to tunneling must be disconnected from the front panel when tunneling is not
used.
1058 C264/EN UM/E50.5

Please refer to EPAS MiCOM C264 Tunneling Application Note

document (C264_TUNNELING_EN_AN_XX) to learn how to install
and configure the Tunneling Client and follow the instructions to
proceed with tunneling.
10.4.3 MODBUS communication
10.4.3.1 Scope of this section
MODBUS is a legacy bus master/slave protocol that is used by many devices such as relays,
computers or monitoring devices. The aim of this chapter is not to describe the protocol itself and
its mechanisms, but to describe the functions implemented in MiCOM C264:
• available function numbers
• the way in which each type of data is internally or externally updated
• general mechanisms used for the synchronization
The protocol is implemented in various ways:

• Generic: this implementation allows connecting most types of IED to a MODBUS network
• Schneider Electric: this implementation is based on the Schneider Electric rules (M300, Px2
series, Px4x series)
• Specific for one relay: M230, Rish Pro M10, ABB-Flexgate, Sepam 40 and 80, WAGO
10.4.3.2 Generic MODBUS Communication

The generic communication is the common base to most of the IEDs. The following MODBUS
functions are implemented in MiCOM C264:
Function No. Sub-code Used to Details

1–2 / Read DIs Read N bits
3–4 / Read AIs /DIs Read N words
5 / Write DO Write 1 bit
Write N bits
15 / Write DOs Restriction: write DOs after
one another
Read status byte
7 / Poll status Used to detect a DI change
of state
Echo
8 0 Poll presence Alternative to detect if a
device is connected or not
6 / tunneling if needed Write 1 word
16 / tunneling if needed Write N words
C264/EN UM/E50.5 1059

The disturbance files are not treated. The function 7 cannot be used fully or at all with a number of
IEDs (e.g.Rish Pro M10, Flexgate); they require a specific treatment.
10.4.3.2.1 Polling and connection test

All the slaves are polled after one another. This means that MiCOM C264 waits for the answer to
each polling request sent to a device before sending a new request to the same or another device.
There are 2 types of polling:

• the polling for the measurements and the digital inputs (functions 1 thru 4) or the byte status
(function 7)
• the polling for IEDs presence (low level polling)
If an IED does not correctly answer after a user-configurable timeout, MiCOM C264 repeats the
request.
If the IED does not correctly answer after a defined number of retries, it is considered as
disconnected. This status is updated by low-frequency polling.
Depending on configuration, MiCOM C264 tests the connections with:

• function 7
• functions 1 thru 4 (DIs)
• functions 3 thru 4 (AIs)
• function 8 (mirror frame)
or uses a user-defined frame.
10.4.3.2.2 Data received from IEDs
10.4.3.2.2.1 AIs
MiCOM C264 polls the AIs at a defined frequency.
A block of measurements is a set of measurements mapped at consecutive addresses. As a

result, all of them are read in one exchange.
MiCOM C264 supports 18 formats of Analogue Inputs:
Format Description Comment
INT8_LB Modbus does not provide a ‘Read

Signed integer on 8 bits byte’ function. So, a ‘Read word’
INT8_HB function is used.
UINT8_LB LB and HB indicate which byte in the

Unsigned integer on 8 bits word is used (respectively,
UINT8_HB Low/High)
INT16 Signed integer on 16 bits
UINT16 Unsigned integer on 16 bits
1060 C264/EN UM/E50.5

Format Description Comment

INT32_LW_LB
INT32_LW_HB
Signed integer on 32 bits
INT32_HW_LB
INT32_HW_HB
The first pair of letters indicates
UINT32_LW_LB which word is sent first: the lower
UINT32_LW_HB word (LW) or the higher word (HW).
Unsigned integer on 32 bits
UINT32_HW_LB
UINT32_HW_HB The second pair of letters indicates
which byte is sent first in a word: the
REAL32_LW_LB
lower byte (LB) or the higher byte.
REAL32_LW_HB
REAL32_HW_LB Float IEEE754 on 32 bits
REAL32_HW_
HB
10.4.3.2.2.2 DIs
A block of DIs is a set of DIs mapped at consecutive addresses. As a result, all of them are read in
one exchange.
By default, the function 1-2 polls for DI blocks. MiCOM C264 compares each DI state with the
latest state and time stamps the potential change of state.
10.4.3.2.3 Data sent to IEDs
10.4.3.2.3.1 Connection check
Generic IEDs
Each device on the network is regularly polled with a specific frame to know if it is connected or
not. This frame could be the status byte polling frame if it exists, the measurement polling frame if
it exists, the BI polling frame if it exists, the mirror frame if it has been implemented in the device or
a user defined frame. This choice is performed through the configuration options.
MiCOM IEDs
The “Read status byte” frame is used for checking the connection of the device.
10.4.3.2.3.2 Clock synchronization
All the devices connected to a given network must use the same synchronization method (and the
same address and time-date format) because MiCOM C264 synchronizes them through a
broadcast frame.
Synchronization is not specified generically, and no calculation of the transmission delay is

performed.
C264/EN UM/E50.5 1061

10.4.3.2.3.3 DOs
Commands are sent to the IED and have the highest priority level.
They have to be transmitted to the destination device as fast as possible.
MiCOM C264 waits for an acknowledgment (answer of the IED).
If the acknowledgment is not received after a defined timeout, MiCOM C264 considers that the
command has not been taken into account.
10.4.3.2.4 Error management

The MODBUS protocol handles a mechanism of exception answer. This means that an IED
answers with an exception frame if it does not understand the request. There are different
exception codes:
Exception code Description MiCOM C264 processing

Reports a "Configuration error” and
01 Illegal function
continue
Reports a “Configuration error”
02 Illegal data address
message and continues
Reports a “Configuration error”
03 Illegal data value
message and continues
04 Slave device failure Reports an “IED error” message
IED busy due to a long processing
05 Retries after a defined time-out
duration
06 IED busy Retries after a defined time-out
07 Processing not possible Reports an “IED error”
08 IED memory parity error Reports an “IED error”
10.4.3.2.5 Limits and specifications

The specifications depend a lot on the number of devices connected on the network. It is advised
to connect devices that have similar specifications on a given network, i.e. the same reply time for
instance.
Each device on a MODBUS network must have the same synchronization mode.
10.4.3.3 Schneider Electric MODBUS COMMUNICATION

Three ranges comply with the Schneider Electric rules:
• M300: Energy analyzer and measurement central unit
• Px2x: MiCOM S20
• Px4x: MiCOM S40
Function
Sub-code Used to Details
No.
1–2 / Read DIs Read N bits
1062 C264/EN UM/E50.5

Function
Sub-code Used to Details
No.
Read AIs
3–4 / Read N words
/DIs
5 / Write DO Write 1 bit
Write N bits
15 / Write DOs
Restriction: write DOs after one another
Read status byte.
7 / Poll status Used to detect a DI change of state and the
presence of disturbance files
Poll Echo
8 0
presence Alternative to detect if a device is connected or not
tunneling if
6 / Write 1 word
needed
tunneling if
16 / Write N words
needed
10.4.3.3.1 Status byte

The connection is tested using the function 7.
Event
Bit No Description Detail
generated
b0 General state of the device 1 = active, 0 = not active Yes
b1 Presence of a minor failure (*) 1 = present / 0 = absent Yes
Presence of a not
b2 acknowledged time-stamped 1 = present / 0 = absent No
event
1= synchronised, 0= out of
synchronisation
b3 State of synchronisation (**) Yes
Compatible with relays
OPN7000, MODN
1= present, 0 = absent
Presence of a not extracted
b4 Compatible with relays Yes on Set
Disturbance record
OPN7000, MODN
Presence of a not extracted
b5 1 = present / 0 = absent Yes on Set
Fault record
1= a trip has occurred, not
b6 Trip Alarm Set No
acknowledged
1= at least one alarm bit in the
b7 Alarm Set front panel alarm cell not No
acknowledged
C264/EN UM/E50.5 1063

If a bit of this status has no significance for the equipment, this bit is fixed to 0.
Any change of state generates an event. Except for b2 set/reset, b4 and b5 reset, b6 and b7
set/reset.
(*) Indicates a device failure («SRAM Failure»…) and generates an event.
(**) 0 indicates that synchronization was not received or not understood since 1 min, according
to protection criteria (by MODBUS or IRIG-B synchronization). This rule covers potential drift of 10
ms of non synchronized device. “Loss of synchronization” has a major impact in all events
treatment. All the events coming from a device that has lost its synchronization need special
treatment in substation chronological list of events. This particular event helps determine also any
network disconnection in the device history.
10.4.3.3.1.1 Events buffer management
The IEDs store the events, Fault Records, Disturbance files in a circular buffer of various sizes.
When MiCOM C264 acknowledges an event, a FREC or Disturbance file, the IED clears the
memory for future events, FREC …
When all events, FREC, DR have been cleared from buffer, the corresponding bit is reset in the
status byte without generating any event.
If a device is disconnected, the buffering function saves all of history. If one of its buffers gets filled
up, then the IED:
• generates an event to inform that this buffer is full,
• erases the oldest event if the queue is full
• sends a saturation reset event when the buffer is not full any more.
• replaces the oldest data in the full buffer by the newest ones (event, FREC, Disturbance file).
10.4.3.3.1.2 M300
The bits have other meanings:

• Bit 0: Availability of a Disturbance record [0 = not available; 1= available]
• Bit 4: 0 = active; 1 = inactive
• Bit 5: 1 = Presence of Event
• Bit 6: 1 = Presence of Alarm.
10.4.3.3.1.3 MiCOM S40 (Px4x series)
The status can be read with function 3 or 4 in register 3x00001 (@ 0).
The table that follows shows this 16-bit status:
Value/bit
Bit No Meaning Conform
mask
0 0x0001 Presence Status (1 = present / 0 = mute) OK
1064 C264/EN UM/E50.5

Value/bit
Bit No Meaning Conform
mask
1 0x0002 Minor Self Test Failure (1 = Failure / 0 = No failure) OK
New event available
2 0x0004 OK
(1 = Available / 0 = Not Available)
Clock synchronization (=1 after Modbus sync.
3 0x0008 Resets to 0 after 5 minutes unless it is synced OK
again. Other time sources do not affect this bit)
New auto extraction disturbance record available
4 0x0010 OK
(1 = Available / 0 = Not available)
5 0x0020 Fault (Not used - always 0). NOK
6 0x0040 Trip LED status (1 = LED on, 0 = LED off) -
Alarm status summary
7 0x0080 -
(logical OR of all alarm status bits)
8 0x0100 Unused -
9 0x0200 Unused -
10 0x0400 Unused -
11 0x0800 Unused -
12 0x1000 Unused -
13 0x2000 Unused -
14 0x4000 Unused -
15 0x8000 Unused -
Even if the access function (3 or 4 instead of 7) does not comply with the internal MODBUS rules,
the events can still be managed, as far as the bits 2 and 3 are compliant with them.
10.4.3.3.2 Data received from IEDs
10.4.3.3.2.1 AIs
The formats supported by MiCOM C264 include:

• IEEE 754 standard (recommended)
• integer signed or not on 1 Byte
• integer signed or not on 2 Bytes
• integer signed or not on 4 Bytes (for energy metering precision)
It is desirable that all the AIs have the same format (type and byte number); otherwise, divide
them in several groups, each with a given format.
The values must be directly usable. Single scaling (e.g. x1000) is accepted. As complex
computation use boundary, scaling is forbidden for measurements.
AIs are mapped at consecutive MODBUS addresses to increase the acquisition efficiency. Or,
they can be in a fundamental data area.
C264/EN UM/E50.5 1065

The transmission of the measurements in double word must start with the most significant byte,
which is not a common practice:
Bytes order
Intel products 1 2 3 4
Motorola products 4 3 2 1
Most common (2 consecutive addresses) 2 1 4 3
Recommended transmission with MODBUS 4 3 2 1
The units of the readings must be identical throughout a range of products. If possible stick to the
list of the recommended units. The format for encoding IEEE makes unit coding easy, as it makes
possible to treat at system level the large or small values without using derived units (example:
tenths of Amperes, tens of Volts, MW).
Description Units
volts V
amperes A
kilo Watt kW
kilo Volt Ampere kVA
kilo Volt-Ampere Reactive kvar
kilo Watt . Hour kWh
kilo Volt Ampere Hour kVAh
kilo VAR Hour kvarh
Hertz Hz
celsius or centigrade Degree °C
Mho 1/Ω
Ohms Ω
Seconds of closing time s
Degree of angle Angular degree
Without unit –
For all the quality descriptors used for the measurements or counters, split quality descriptor
indication (like CP8(i+1) Info + Quality from IEC 870-5-4) from the value in separate address
groups.
Some IEDs encode Valid/Invalid quality statuses with binary values. For such IED, map the AI
Statuses in consecutive words.
10.4.3.3.2.2 M300
The measurements are periodically polled for. The available formats include:
1066 C264/EN UM/E50.5

Format to configure Comments

16 bit unsigned value: "12345" (0x3039)
T1 UINT16 (5)
represents 12345
16 bit unsigned value with 2 decimals:
T3 UINT16 (5)
"12345" (0x3039) represents 123,45
16 bit signed value with 3 decimals: "-
T8 INT16 (4)
12345" (0xCFC6) represents -12,345
T9 UINT32_HW_HB (13) 32 bit signed value: “big Endian” *
32 bit signed value with 2 decimals: “big
T10 UINT32_HW_HB (13)
Endian”*
Endian”*
Endian”*
Energy: T09 for the primary values (base unit kWh),T11 for the secondary
T20
(base unit Wh)
Power: T10 for the primary values (base unit kW),T12 for the secondary values
T21
(base unit W)
Voltage: T10 for the primary values (base unit V),T11 for the secondary values
T39
(base unit V)
Current: T10 for the primary values (base unit A), T13 for the secondary values
T40
(base unit A)
T53 Idem T1
* the higher word is transmitted first, the higher byte in the word is transmitted first
These formats do not take into account the multiplying factor. Moreover, the next table gives a
non exhaustive list of measurements (in secondary mode):
MiCOM C264
Meas. Scaling factor Address Formats
type
UINT32_HW_ T39 (=T11 for the
Va 0.001 0x01C6
HB secondary mode)
Vb 0.001 0x01C8
HB secondary mode)
Vc 0.001 0x01CA
HB secondary mode)
Uab 0.001 0x01CC
HB secondary mode)
Ubc 0.001 0x01CE
HB secondary mode)
C264/EN UM/E50.5 1067

MiCOM C264
Meas. Scaling factor Address Formats
type
Uca 0.001 0x01D0
HB secondary mode)
T40 (=T12 for the
UINT32_HW_ secondary mode,
Ia 0.0001 0x01D2
HB mistaken as T11 in the
manual R8605C2)
T40 (=T12 for the
Ib 0.0001 0x01D4
manual R8605C2)
T40 (=T12 for the
Ic 0.0001 0x01D6
manual R8605C2)
T40 (=T12 for the
In 0.0001 0x01D8
manual R8605C2)
UINT32_HW_
Freq. 0.001 0x01DA T11
HB
T21 (=T12 for the
Power 0.0001
manual R8605C2)
Energies 0.001
HB secondary mode)
The addresses 0x01DB, 0x01DC, 0x01DE and 0x01DF generate an exception frame with code
number 2.
10.4.3.3.2.3 MiCOM Px2 series and Px4 series
Measurements are read through the Modbus functions 3 or 4 (read word functions). Select the
correct format for the measurement: 16 or 32 bits.
Notice that the lower word of 32 bit values is generally transmitted first and, in each word, the
higher byte is transmitted first (use formats such as YYYY32_LW_HB for 32 bit values).
• Basic Address (Mapping address) 0xyyyyy
• Extra Address 1: not used

• Extra Address 2: Modbus function (3 or 4)
• Extra Address 3: not used
• Format: See table
1068 C264/EN UM/E50.5

10.4.3.3.2.4 DIs
10.4.3.3.2.5 IED synchronized
Same as generic Modbus (block mode)
10.4.3.3.2.6 IED NOT synchronized
The status byte is regularly polled at low level and compared with the latest one. The status byte
in an Schneider Electric IED contains the indication that at least one DI change has occurred.
If a change is detected, MiCOM C264 reads the event queue inside the IED, checks out which
data have changed, checks if the data have been configured and reads the information itself.
In this case, the DI changes are time-stamped in the IED and MiCOM C264 downloads their date
and time.
Any DI change generates an event. For any event, there is a DI address that can be retrieved.
All the DIs have two states (0/1, on/off, open/closed, synchronized/out of synchronization). Each
DI generates 2 events (Reset to 0 at this time, Set to 1 at that time).
The DIs are stored at consecutive addresses. In consequence, all the DIs can be read in only one
request (except if the number of DIs exceeds the capacity of a MODBUS message, and except
may be for fast status word).
DIs at connection
At connection or periodically, MiCOM C264 can fetch the global states of one device in a single
message. Automation can start at once as it is based on states. Event reading can be delayed
due to the need to get the disconnection history and time stamp the current state.
A transient DI is in fact an event not associated to a real state but to a transition (e.g. Trip order). It
is only SET never RESET. The practice shows that state approach is more commonly used than
the transition approach and help know the global status at connection. For this purpose, a
transient DI like the trip order is held for a configurable time (300ms), and results in 2 events (set
and reset). The IED translates an inner transient DI to a pulsed indication over the network (with a
configurable time e.g. 100 to 300ms).
M300 read request
The time-stamped events of the M300 are NOT treated (there is no indication on the state of
synchronization of the M300). In consequence, the MiCOM C264 acquires the DIs of the M300 by
polling and time stamps them.
The DIs are read through the Modbus function 4 (read words) with the values that follow:
• mapping address in the basic address field
• 4 in the extra address 2 field
• bit number in the extra address 1 field
Example for reading the 2 DIs of an M300 device:
C264/EN UM/E50.5 1069

• BI0:
Base address: 28d
Extra address 1: 0
Extra address 2: 4
Extra address 3: /
• BI1:
Basic address: 28d
Extra address 1: 1
Extra address 2: 4
Extra address 3: /
Example for reading alarm status of an M300 device (@30030):

• BI16:
Base address: 30d
Extra address 1: 0 “Error EEPROM: alarm group 4”
Extra address 2: 4
Extra address 3: /
• BI17:
Base address: 30d
Extra address 1: 1
Extra address 2: 4
Extra address 3: /
• BI23:
Base address: 30d
Extra address 1: 7 “serial port default Analogue output”
Extra address 2: 4
Extra address 3: /
• BI0:
Base address: 31d
Extra address 1: 0 “Test timeout for watchdog”
Extra address 2: 4
Extra address 3: /
• BI1:
Base address: 31d
Extra address 1: 1
1070 C264/EN UM/E50.5

Extra address 2: 4
Extra address 3: /
• BI15:
Base address: 31d
Extra address 1: 15 “Error EEPROM: alarm group 3”
Extra address 2: 4
Extra address 3: /
To read bit fields in 32-bit values, configure at least one BI in each part of the long value (lower
word and higher word) as described in the previous example.
MiCOM Px2 series and Px4 series read request
MiCOM C264 acquires the DIs through the function Nr 3 or 4 (read word functions).
• Base Address (Mapping Address) 0x0010
• Extra Address 1 (bit Number) 0
• Extra Address 2 (Modbus function) 4
• Extra Address 3 (Not Used) X
To improve the process, the events are handled in MiCOM C264. This means that each action on
the relay activates an event that is uploaded and decoded in the relay. If the DI corresponding to
the event has been configured, MiCOM C264 reports the new DI value.
10.4.3.3.2.7 Disturbance files
The disturbance record includes any transfer of file of measurements sampled at high frequency:
• conventional disturbance
• monitoring data (pressure in GIS, harmonics, brush distance in CB closing ..)
Such a file is breakdown into limited size blocks (defined by MODBUS) to be uploaded.
Any file data format can be used as far as it can be converted to a standard file format, COMTRAD
or at least CSV format (Excel, Matlab…).
Regardless of the kind of transmission, a header must define the kind of data transfer (file or
column values) and the required file reader. The name of the exploitation files (usually
COMTRAD) is based on the configured device, master reference, IED MODBUS reference, and
cyclic disturbance number.
MiCOM C264 is informed that a disturbance is stored by reading the bit b4 in the Status byte.
Each block is transmitted on the MiCOM C264 request. At the global end of transfer, after a
check-up of the file, MiCOM C264 sends the “Ack.DO” and the device can erase its disturbance
file. If another “disturbance file” is still present, the bit b4 remains set (e.g. EPAC multi disturbance
upload).
The date in disturbance file must be the same as in events (for trip indication…). The device is
compliant with:
C264/EN UM/E50.5 1071

• the file upload mechanism (Stream of data)
• the disturbance upload mechanism (Column of values); example: series P20
1072 C264/EN UM/E50.5

10.4.3.3.2.8 M300
There are 2 types of Disturbance record:

• Waveform Analysis Record (max = 1 file)
• Disturbance Record (max = 4 files)
The detection of the availability of a disturbance record in the M300 is done by regularly polling
the status of the M300 (bit “Presence of a Disturbance record”).
The disturbance record of an IED is uploaded only if the maximum number of simultaneous
disturbance uploading is not reached for the Modbus line and the opening of a disturbance file on
the computer is possible.
Uploading
MiCOM C264 opens a file to store disturbance data. If it is not possible, the treatment ends.
The type of disturbance record to upload is selected by writing to register @40567 (0x0237):
• ‘0’ for a Waveform Analysis
• ‘1’ for a Disturbance Record
The record number is selected by writing to register@40568 (0x0238) the value ‘0’ in order to
select the last one.
MiCOM C264 reads the general information and writes the information that follows to the file:
• Serial number of the IED [8 words at @30001 (0x0001)]
• Frequency [@40572 (0x023C)]

• Trigger date [@30055 (0x0037) →@30060 (0x003C)]
• Available channels [@30061 (0x003D)]
• Type of channels [@30062 (0x003E)]
• Number of samples by channel [@30063 (0x003F)]

• Number of pages [of sample] by channel [@30064 (0x0040)]
• Number of samples by cycle [@40560 (0x0230)]
• Trigger position [@30066 (0x0042)]
• Time base [@30067 (0x0043)]

• Scaling factors of analogue channels [@30068 (0x0044) →@30081 (0x0044)]
• Names of analogue channels
• Names of TOR channels
The disturbance data are uploaded channel by channel, starting with channel ‘0’ which is the time
channel, and for each channel, page by page.
At last, MiCOM C264 closes the disturbance file.
The bit 7 of register @40047 allows to erase ALL the disturbance records.
For mapping information, refer to the Service manual volume 2, ref. R8605C2.
C264/EN UM/E50.5 1073

10.4.3.3.2.9 MiCOM Px2 series and MiCOM Px4 series
MiCOM Px4 series
No disturbance files.
MiCOM Px2 series
The Px2x can store up to five Disturbance records. The number of channels depends on the kind
of Px2x (6 thru 9).
MiCOM C264 detects the presence of a disturbance record in the Px2x by regularly polling for the
status of the Px2x (bit “Presence of a Disturbance record”).
Uploading
MiCOM C264:
1. Opens a file to store disturbance data; if this is not possible, the treatment ends
2. Reads the number of Disturbance records and the associated information (Read of 36
words at @0x3D00); this information enables to know the number (between 0 and 4) of the
latest unacknowledged disturbance records. If there is no unacknowledged disturbance
record, the treatment ends
3. Reads all the IED identification model based on the pattern “Px2x” in order to determine the
number of channels and the selection size (Read of 5 words at @0x0000) and after, it writes
this information to the disturbance file
4. Uploads the disturbance data channel by channel, and for each channel page by page.
5. Reads the index frame of the disturbance (Read 7 words at @ 0x2200) and writes this
information to the disturbance file
6. Closes the disturbances file
7. Acknowledges the disturbance records in the Px2x by setting the bit @0x4032 to 1; another
disturbance record can be uploaded from the IED
Differences between Px2x Models:
Overall selection
Number of analogue Number of TOR information size
Products channels
channels channels
number Pages 0x38-0x3C
P120 No disturbance management
5 ( IA, IB, IC, I0, 1 (3 Inputs,
P122 6 11 Words
Frequency) 7 Outputs)
P123 6 11 Words
P124D 6 11 Words
P124S No disturbance management
1074 C264/EN UM/E50.5

Overall selection
Number of analogue Number of TOR information size
Products channels
channels channels
number Pages 0x38-0x3C
6 (IA, IB, IC, I0, V, 1 (7 Inputs,
P126 7 19 Words
8 (IA, IB, IC, I0, VA, 1 (7 Inputs,
P127 9 19 Words
VB, VC, Frequency) 9 Outputs)
5 (IA, IB, IC, I0, 1 (5 Inputs,
P220 6 11 Words
6 (IA, IB, IC, I0, UAC, 1 (6 Inputs,
P225 7 19 Words
6 (IA, IB, IC, I0, UAC, 1 (6 Inputs,
P226C 7 19 Words
2 (5 Inputs,
7 ( IA, IB, IC, I0,
P521 9 Outputs, 9 11 Words
timing)
9 internal data)
5 ( Voltage, 1 (5 Inputs,
P922 6 19 Words
5 (Voltage, 1 (5 Inputs,
P923 6 19 Words
Modbus
@ Mapping Words Format Description
Function
Pages 0x09 thru 0x21: Disturbance Data. Each page contains the samples [250 data word] of
the selected channel
0x0900 →
3 250 Up to 250 samples
0x09FA
0x0A00 →
3 250 INT16 Up to 250 samples
0x0AFA
0x2100 →
3 250 Up to 250 samples
0x21FA
Page 0x22 : Index of the Disturbance
0x2200 3 1 UINT16 Disturbance record Number
C264/EN UM/E50.5 1075

Modbus
Function
0x2201 →
3 4 Time Stamp Disturbance record finish date
0x2204
0x2205 3 1 UINT16 Disturbance record starting condition
0x2206 3 1 UINT16 Frequency at post-time beginning
Modbus
Function
Page 0x3D : Number of disturbance records available
Number of disturbance records [1 ..
0x3D00 3 1 UINT16
5]
0x3D01 3 1 Oldest disturbance record (n)
0x3D02 →
3 4 Time Stamp disturbance record Date
0x3D05
0x3D06 3 1 disturbance record starting origin
0 ↔ Not Acknowledged
0x3D07 3 1
1 ↔ 1 Acknowledged
0x3D08 3 1 Preceding disturbance record (n+1)
0x3D09 →
0x3D0C
0x3D0D 3 1 disturbance record starting origin
0x3D0E 3 1
….
0x3D1D 3 1 Preceding disturbance record (n+4)
0x3D1E →
0x3D21
0x3D22 3 1 disturbance record starting origin
0x3D23 3 1
Pages 0x38 thru 0x3C: Selection of the Disturbance and channel [Each page correspond to one
out of the 5 Disturbance records]. The second header line is the number of words uploaded for
each access reading:
1076 C264/EN UM/E50.5

P122/P123/P124D P225/P2 P922/P92

Modb Word P126 P127 P521
/P220 26C 3
@mappi us s
11
ng functi numb
11 words 19 words word 19 words
on er
s
Pages 0x38 thru 0x3C: selection of the Disturbance and channel [Each page correspond to 1 of
the 5 Disturbance record]
0x..00 3 1 Ia Ia Ia Ia Ia Ua
0x..01 3 1 Ib Ib Ib Ib Ib Ub
0x..02 3 1 Ic Ic Ic Ic Ic Uc
0x..03 3 1 Io Io Io Io Io Vo
reserve Frequen Timin Frequen
0x..04 3 1 Frequency Ua
d cy g cy
reserve TOR
0x..05 3 1 TOR Ub TOR TOR
d 1
TOR unavaila
0x..06 3 1 unavailable Uo Uc/Uo Uac
2 ble
frequen unavaila unavaila 0x..0
0x..07 3 1 frequency 3
cy ble ble 7
0x..08 3 1 TOR TOR 0x..08 3 1 TOR
For each register read request, the following information is uploaded. This information describes
the selected channel:
P122/P123/ P225 /
Word P126 P127 P521 P922/P923
P124D/P220 P226C
0 Total samples number
1 Sample number in pre-time
2 Sample number in post-time
3 Primary phase CT ratio
4 Secondary phase CT ratio
5 Earth primary CT ratio
6 Earth secondary CT Ratio
7 Phase internal CT ratio
8 Earth internal CT Ratio
Primary
Last page Primary phase VT Ratio
9 Reserved Last page nb phase VT
Number [LB]
Ratio [LB]
C264/EN UM/E50.5 1077

P122/P123/ P225 /
Word P126 P127 P521 P922/P923
P124D/P220 P226C
Primary
Last page Primary phaseVT Ratio Last pg word
10 Reserved phaseVT
word number [HB] nb
Ratio [HB]
Secondary
11 Reserved Secondary phase VT ratio phase VT
ratio
Earth
12 Earth primary VT ratio [LB] Reserved primary VT
ratio [LB]
Earth
13 Earth primary VT ratio [HB] Reserved primary VT
ratio [HB]
Earth
14 Earth secondary VT ratio Reserved secondary
Unavailable Unavailable VT ratio
Internal VT
15 Internal VT ratio – numerator 100 ratio–num.
100
Internal VT
16 Internal VT Ratio – denominator ratio–
denom.
Last page
17 Last page Number
number
Last page
18 Last page words number words
number
Specific treatments
P126: the channels are not consecutive; the 5th & 6th channels must be skipped.
P127: the mapping address 0x0127 must be read. It gives the voltage wiring of the IED. This
value must be written in the file (but it doesn’t change the uploading process).
P922 &P923: the mapping address 0x0126 must be read. It gives the voltage wiring of the IED.
This value must be written in the file. This value changes the uploading process: in some cases,
the channels must be skipped.
1078 C264/EN UM/E50.5

Wiring
Voltage wiring of the IED Used channels
value
0 Ua
1 Ub
2 Uc
0 3Vpn (3 phase-to-neutral voltages)
3 Not used
4 Frequency
5 TOR
0 Ua
1 Ub
2 Uc
1 3Vpn + Vr (3 phase-to-neutral voltages + residual voltage)
3 Vo
4 Frequency
5 TOR
0 Uab
1 Ubc
2 Not used
2 2Vpp + Vr (2 phase-to-phase voltages + residual voltage)
3 Vo
4 Frequency
5 TOR
0 Uab
1 Ubc
2 Uca
3 3Vpp + Vr (3 phase-to-phase voltages + residual voltage)
3 Vo
4 Frequency
5 TOR
10.4.3.3.2.10 Events
An event is a time-stamped change of state of a logical data.
When the IED gets connected, MiCOM C264 reads the current status of logical information, then
manages the status changes from the file of the time-stamped events.
The time-stamped events are gathered in one file. The bit b2 of the status indicates the presence
of at least one event not extracted. Events are stored by IED, and are read one by one by the
master, starting from the oldest event.
MiCOM C264 reading of one event does not withdraw it from the file. An IED withdraws an event
from its list:
C264/EN UM/E50.5 1079

• when MiCOM C264 acknowledges it
• when the file of the events gets saturated (the queue sheds the oldest event)
• directly after MiCOM C264 reading if automatic event retrieval is set on IED. The event can be
read again at address @event +1 (3601h if the latest event address is 3600h). Event reply is 0
if the events list is empty.
• MiCOM C264 reads one event, and then sends “DO ok“ if it correctly receives the event.
When receiving this acknowledgment, the IED deletes its latest event, and updates its events
list (and resets the event bit in status word if applicable: refer to IED documentation). This
makes sure that no event is lost. DO acknowledgment is bit 13 (0400h).
• IED and MiCOM C264 are configured for automatic event retrieval (at start-up MiCOM C264
checks the bit b12 at 0400h). MiCOM C264 reads the latest event.
The IED shifts this event to the next address in the event list. If MiCOM C264 detects a
transmission error, it reads again the event at address +1.
Any event includes the information that follows:

• Date - Time, using inverse order as per IEC 870-5-4 CP56T2a format (no short format, no
CP16, same format as clock synchronization).
• MODBUS mapping address of logical information that has changed.
• New state value of the transmitted data (new value of the word, stored at the MODBUS
mapping address).
MiCOM C264 extracts the events meant for upper functions and sends them to the corresponding
service: automation, alarms, textual message converter, event & logging printing….).
Note: all textual information associated to events are not needed by a system master as
customers have their own labels, wording, or writing (Cyrillic, Cantonese …). A separate device is
in charge of textual logging. The text only reduces communication bandwidth.
MiCOM C264 can manage several changes of state in one event (for changes in same time
accuracy period, to increase transfer…), even if each event has only one change of state. Then,
one change of state is linked to one event and one event is linked to several possible changes of
state (if they are at the same MODBUS address).
MiCOM Px4 series
The command register can be written with Modbus function 6 in register 4x00400 [@ 399]. Each
action is activated when a ‘1’ is written to the corresponding bit.
Bit No. Value / bit mask Used to

0 0x0001 Select the next event
1 0x0002 Accept event
2 0x0004 Select the next disturbance record
3 0x0008 Accept disturbance record
4 0x0010 Select the next disturbance record page
x x Other bits are unused
1080 C264/EN UM/E50.5

Automatic event-record extraction allows records to be extracted as they occur. Event records are
extracted in sequential order:
MiCOM C264 determines whether the Px4x has any events stored that have not yet been
extracted by reading the Px4x’s status register 3x00001 (G26 data type). If the event bit is set, the
Px4x contains event records that have not yet been extracted.
To select the next event for sequential extraction, MiCOM C264 writes 1 to the command register
4x00400 (G18 data type). The event data together with any fault/maintenance data can be read
from the registers as specified in the flow chart and table.
Once the data has been read, the event record can be marked as read by writing 2 to register
4x00400.
Alternatively, since the G18 data type consists of bit fields, it is possible to both marks the current
record as having been read and to automatically select the next unread record by writing 3 to the
register.
When the latest (most recent) record has been accepted, the event flag in the status register
(3x00001) is reset.
If the latest record was accepted by writing 3 to the command register (4x00400), a dummy record
appears in the event record registers, with an “Event Type” value of 255.
Attempting to select another record, when none are available results in a Modbus exception code
3 – “Invalid value”.
C264/EN UM/E50.5 1081

Event formats:
Modbus Register Nb
Contents Description
/Address Register
3x00103…3x00106 (G12)
Time stamp of IEC 870 Time & Date 4
102 … 105 the event
0,1,2, 3 alarm
4 output contact
3x00107 (G13)
5 opto input 1
106 Event type
6 protection
255 dummy event
3x00108…3x00109 (G27) New values of the 32 bits register
2
107 ... 108 Event value containing the BI(s) which have changed.
Modbus address of the 32-bit register

containing the BI(s) that have changed.
CAUTION: real Modbus address must be

recomputed by subtracting 30001 !!!
3x00110 (G1) Event type Event index

32-bit Register 1
109 0,1,2,3 11
reference
4 723
5 725
727 thru 785 (associated DDB
6
status register)
Event type Event index
0,1,2,3 Alarm ID
3x00111
Event Index 4, 5 Not used – set to 0 1
110
bit 16 = state, bits 1-15 DDB
6
ID
Not used by
3x00112 – 1
MiCOM C264
According to the Event Type, the Event Index can be used – or not – to analyze the Event. Two
cases have to be considered:
• Event of type 0,1,2,3 and 6. In this case, the Event Index can be used.
• Bit16 of the Event Index indicates the new Digital Input state (0 or 1)
• Bit1-15 of the Event Index [modulo 32] indicate the Bit Number of the Digital Input in the 32bits
register
1082 C264/EN UM/E50.5

• The 32bits register reference and the Digital Input Bit Number allows finding the Digital Input
in the MiCOM C264 DB (if configured).
• Event of type 4 and 5. In this case, the Event Index is not significant and can't be used. The
MiCOM C264 DB has to be parsed against the Event Value, looking for a change of state of
all Digital Input of the 32-bit register reference.
10.4.3.3.2.11 File upload
A file is defined by a header, a parameter set and a stream of data. Each time MiCOM C264 reads
a block of data, the IED shifts data to the next page (Repeat page) and replaces it by a new block
of data. In event of transmission error, MiCOM C264 requests the block wrongly received to the
repeat page.
Addresses Function Contents

FA00 to FAFA Read 24 words Read header
Read N words of file parameters and
FB00 to FBFA Read N words
shift parameter stream
FC00 to FCFA Read N words Read N words again of file (repeat)
Read N words of file data and shift
FD00 to FDFA Read N words
data stream
FE00 to FEFA Read N words Read N words again of file (repeat)
The header defines data to transmit and file treatment to trigger by MiCOM C264 on data
reception:
Word Description Format

1 Kind of file transfer 0 for the following mechanism, 1 for a future one
Number of words in
2-3 Nb_Byte_Para
parameter field
Number of words in data
4-5 Nb_Byte_Data
field
6 Manufacturer 1 « Schneider Electric » (for M7xx)
4 ASCII {« M710 », « M711 » , « M720 »,
7-8 Product reference
« M721 »… }
Transmission product
9 1 First version or A
version
8 ASCII characters:
SS Week
10-13 Product serial number
AA Year
NNNN Number in week (shift left + blank).
C264/EN UM/E50.5 1083

Word Description Format

0 very short time
1 short time
Kind of File transfer
2 quality events
14 used below by the
product 3 disturbance
compressed
4
disturbance
15-18 First element time tag IEC 840-5-4 ( 64 bits = 4 x 16-bit words )
Reserved e.g. sampling,
19 0x0000
trigger timer
… … …
24 Reserved 0x0000
All the data samplings are transmitted after one another without compression.
Word Description for decoding software

0-1 First value of first sampling
2-3 Second value of first sampling
Nb_Byte_Data Last word
Algorithm:
1084 C264/EN UM/E50.5

Downloading is done using function 15 or 16 at specific address. Acceptance is signaled.
To speed up the global downloading, writing can be done to several consecutive addresses.
10.4.3.3.3 Data sent to IEDs
10.4.3.3.3.1 Clock synchronization
Type of synchronization: Schneider Electric
All the devices connected to a given network must have the same synchronization procedure
(address and time and date format) because the synchronization order is broadcast.
Date and time comply with the inverted IEC 870-5-4 CP56Time2a format:
C264/EN UM/E50.5 1085

Word 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
1 0 0 0 0 0 0 0 0 0 Year: 00…99
2 0 0 0 0 Month: 1...12 DayOfWeek:1..7 DayOfMonth:1..31
3 Su 0 0 Hour: 0…23 IV 0 Minutes: 0…59
4 Milliseconds (High) Milliseconds (Low)
Su (=0 for Standard, =1 for Summer Time)
IV (=0 for valid, =1 for non valid or out of synchronization for a system)
First day of the week: Monday
Date and time is set at address 0800h with function 16. No calculation of transmission delay.
If an IED does not have (this) synchronization, it must be unaware of these synchronization
messages (no error indication, no failure).
If an IED that does not stick to the rule, MiCOM C264 supplies out-of-synchronization devices with
its own time stamp. The time accuracy is deeply degraded.
An IED does not generate any event when receiving the synchronization, or when missing one
broadcast message.
Synchronization comes from a specialized clock device like GPS. The first bit is the reference.
MiCOM C264 transmits time corrected by its treatment delay. It sends a synchronize message
periodically (e.g. 3 times per minutes). The absence of reception within one minute results in a
“Loss of synchronization” event.
A “Loss of synchronization” event requires a set/reset. Synchronization information is also

signaled by the IV bit in the event time stamp: 0 means that when the event occurred, the IED was
out of synchronization.
Any IED with 2 clocks systems (MODBUS synchronization mechanism AND an IRIG B or other)
must have an inner setting to deactivate each clock.
If MiCOM C264 has lost its own synchronization, it still time stamps events (but with IV bit set) to
still synchronize the IEDs with a same reference (relative time tagging).
M300
The M300 supports 2 time formats:

• The Schneider Electric synchronization format, which is used only to set the Date & Time
• The M300 format which is used to set the Date & Time in the M300 or for time stamping in the
M300 (e.g. Disturbance time stamping)
The synchronization according to the Modbus Schneider Electric rules is accepted by the M300
only if the bit “summer” is NOT set.
MiCOM Px2 series
The Px2x support 2 time formats:
1086 C264/EN UM/E50.5

• the Schneider Electric synchronization format, which is used only to set the Date & Time in
the Px2x
• the Px2x format which is used for time stamping in the Px2x (e.g. Event & Disturbance time
stamping)
Time stamping format:
Word Description
0 Lower word of Seconds
1 Higher word of Seconds
2 Lower word of MilliSeconds
3 Higher word of MilliSeconds
The number of seconds given in the previous table (32-bit value in word 0 and 1) is the number of
seconds elapsed since 1994 January 1st.
Since the V4C version of the PX2X relays, a private format and the IEC format are both available.
Select the IEC format to obtain a correct event decoding.
Moreover, a PX2X relay goes out of synchronization after a 1 min delay. As a result, select a
synchronization period lesser than 60 seconds.
MiCOM Px4 series
The Px4x support the Schneider Electric format. To keep the Px4x synchronized, MiCOM C264
sends a synchronization frame at least once every 5 minutes.
It is possible to use both Px2x and Px4x relays on the same communication channel and to
activate the synchronization.
The register 4x00306 is used to configure the time format managed by the relay:
• Writing value '0' in this register selects the 'standard IEC' time format (default value).
• Writing value '1' in this register selects the 'reverse IEC' time format (Modbus
Schneider Electric time format used by MiCOM C264).
So, at Px4x connection, value "1" must be written in register @305 [4x00306] to signal the Px4x to
use the Schneider Electric time format.
If the 'Modbus Schneider Electric format' is selected (see above), the time tag format in events is
as show below:
Word No. Byte No. Data (MSB first) Mask

0 Dummy byte (set to 0) 0x00
0
1 Years 0x7F
2 Month 0x0F
1 Day of week / Day of
3 0xE0, 0x1F
Month
C264/EN UM/E50.5 1087

Word No. Byte No. Data (MSB first) Mask

4 Summertime / Hours 0x80, 0x1F
2
5 Validity / Minutes 0x80, 0x3F
6 Milliseconds MSB 0xFF
3
7 Milliseconds LSB 0xFF
10.4.3.3.3.2 Commands
Any control sent from MiCOM C264 to an IED is called a Digital Output:
• Logical control: DO to acknowledge a Disturbance record, a time stamped event, DO to
activate or inhibit a specific protective function.
• Physical control: DO to open or close a feeder circuit breaker, or specific output.
To simplify Master MODBUS configuration and run time, it is desirable to gather controls at
consecutive addresses.
Communication DOs or controls are transmitted by Modbus writing functions:

• function 5 (write 1 bit)
• function 6 (write 1 word)
• function 15 (write N bits)
If the function 6 or 15 are used, the word of control must be formatted in fields of bits.
The DO used to acknowledge reception of dated events must always be accepted by the IED,
even if it is in local mode (no protection mode filtering on this particular DO).
For a single control on a bit field, there is no special need or common description of “Control
accepted”. The DI changes subsequent to a control action are sufficient to control execution.
For other controls, reserve a special word on IED for all the device acknowledgment.
If there are several devices on IED, a more elaborate control message sequence between
MiCOM C264 & IED are required. For a control message, keep the Modbus acknowledgment
rules.
On reception of a control request, an IED sends 0 (OK) if function/address/data are correct.
If its inner algorithm forbids it to initiate ordered sequence with physical Digital Output (because of
interlock, locking, running control, invalid position…), the IED transmits an “application” error code
via an event DI configured in MiCOM C264. MiCOM C264 determines if the sequence is
acceptable and runs correctly (for higher control algorithm or protocol conversion).
When operating control is implemented on IED (OBS, Cx2x, P4xx) a lot of failure cases are
defined, and over several plants.
At least use for each controlled plant only one word (4 control bits set by MiCOM C264 and reset
by IED, and 12 main informative bits). Extra words can be defined for further automation
indication.
1088 C264/EN UM/E50.5

Case 1: Switching device may need to be split into synchronized CB and disconnections:
MONITORING
CONTROL *
Control Plant State Plant secondary DI
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Plant position
0 0 0
MOTION
Plant position
0 0 1
OPEN
Plant position
0 1 0
CLOSE
0 1 1 Error!
Plant position
1 0 0
INVALID (DBI00)
Plantposition
1 1 1
INVALID (DBI11)
Other INVALID
1 0 1
(polarity…)
Reserve other
1 1 0
INVALID
(opt) Plant
0/1 inLOCAL/REMOT
E
(opt) Plant
0/1 LOCKED
(WITHDRAW)
(opt) DI select in
0/1
SBO
(opt) Synchro-
0/1
check OK
Control Fail
1 Abnormal
termination
Control Fail
1 mismatch plant
position
Control Fail Lock
1
(pressure…)
Control Fail
1
Interlock
C264/EN UM/E50.5 1089

MONITORING
CONTROL *
Control accepted
1 Latch (any
control)
0 0 1 OPEN control
0 1 0 CLOSE control
(opt) CLOSE2
1 0 0
control (Forced)
(opt) SELECT
1
control
* All DOs latched by MiCOM C264, the front panel cell is reset at the sequence end by IED
1090 C264/EN UM/E50.5

Case 2: Transformer with TPI position on other word
MONITORING
CONTROL *
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Plant position
0/1 MOTION /
FIXE
Mini CB
0/1
OPEN/CLOSE
Plant position
1
INVALID
(opt)
0/1 AVRegulation
ON/OFF
(opt) Plant
0/1
LOCKED
x Reserve
Low Tap
1
Reach
High Tap
1
Reach
Control Fail
1 Abnormal
termination
Control Fail
1
Lock (oil,..)
Control Fail
1 Interlock
(unusual)
Control
1 accepted Latch
(any control)
Tap RAISE
0 0 1
control
Tap CLOSE
0 1 0
control
(opt)Regulatio
1 0 0
n ON Control
(opt)
1 Regulation
OFF Control
C264/EN UM/E50.5 1091

* All DOs latched by MiCOM C264, the front panel cell is reset at the sequence end by IED
Several kinds of control are defined to manage any measurement that can be frozen
(Maintenance counter, metering, or classical measurement). The following “control structure” byte
can be used for each measurement:
CONTROL MONITORING
7 6 5 4 3 2 1 0
0/1 AI Valid/Invalid
0/1 AI not Frozen/Frozen
x Reserve Topical, saturated…
x Reserve
1 Unitary reset
1 Unitary reset & start
1 Unitary restart
1 Unitary freeze
Any IED has kind of alarm management that deeply differs from the one used at system or
SCADA level. An alarm is any indication given to an operator to warn against a non standard
condition, usually by LED indications on IED (2 states ON/OFF), alarm list at upper level (with 4
states defined by STANDING/RESET, NOT_ACK/ACKNOWLEDGE).
It is asked that IED alarms indication be accessed in one address. A DO can globally
acknowledge/reset alarms (but one alarm is maintained if condition is still present). In the cell
words, a first byte is dedicated to indicating alarm, a byte+8 to resetting each alarm.
M300
There is one command register in the M300 [@40047 (0x002F)]. This register is set using the
function 6. Each bit of the register corresponds to a different command:
Basic Address (Mapping Address) 0x002F
Extra Address 1 (bit Number) Bit number to write
Extra Address 2 (Modbus function) 6
Extra Address 3 (Not Used) x
MiCOM Px2 series
There are 3 command registers in the Px2x [@0x0400, @0x0402, 0x0403]. This register is set
using the function 5, 6 or 15. Each bit of the register corresponds to a different command:
@ Mot @Bit Usable Function Comment

Remote control Word N°
0x0400 0x4000 → 0x400F 5, 6, 15
1
1092 C264/EN UM/E50.5

@ Mot @Bit Usable Function Comment

0x0402 0x4020 → 0x402F 5, 6, 15
2
0x0403 0x4030 → 0x403F 5, 6, 15
3
Configuration using function 5 of the bit4 [Remote closing] of register 0x0400:

• Basic Address (Mapping Address) 0x4003
• Extra Address 1 (bit Number) X

Configuration using function 6 of the bit4 of register 0x0402:

• Basic Address (Mapping Address) 0x0402
• Extra Address 1 (bit Number) 4

Special commands used by the computer:
@Bit Comment
Set in order to switch to manual
0x400C acknowledgement mode for Event and
Disturbance uploading
0x400D Set in order to acknowledge the latest Event
Set in order to acknowledge the latest
0x4032
uploaded Disturbance
MiCOM Px4 series
No specific treatment.
10.4.3.3.3.3 AOs
The analogue control or AO or Set point, or control reference is a value transmitted by

MiCOM C264 to device using the function 6 or 16. They can be used to define a reference (for
physical output in regulation scheme, generator…) or to define a protection parameter
(threshold…).
The values to write must comply with formats and units described for Analogues Inputs (IEEE 754
standard, Integer / not signed on 1/2/4 bytes).
C264/EN UM/E50.5 1093

When several values at consecutive addresses can be written, IED must support writing to this
block of addresses.
10.4.3.3.3.4 Settings of the current relays
In order to parameterize the remote relays, a setting software is necessary.
The tool is Modbus connected on the rear (as commonly used by system in run time).
A front connection with the same software and same framing protocol at both customer validation
and after sale phase is recommended.
Setting software requirements:

• Interface with at least a DLL for Emission / Acceptance of messages developed by the
supervisor system, in order to use the tool with other link than serial port. Modbus messages
are encapsulated by system sub-station protocol to be used in system architecture.
• Possibility of inhibiting some options of the menu (pooling, disturbance upload …).
• Complete management of the function by the application (Timer on failure to reply, causes of
failure…).
• Off-line setting before download
• In run-time the Modbus master is the only master. The tool should not disturb the standard
polling of events and data.
10.4.3.3.3.5 Error management
Faults records
The processing of recommended Fault records is as follows:

• Creation of a zone dedicated to describing Fault, apart from the Fault proper
• Sorting of information according to the type of data.
The Fault Record has the same Modbus address for a whole range of products – that means, for
all the IEDs in the series the same address for the latest not acknowledged fault. A good practice
is to have the same address for all MiCOM products (e.g. 0x003E for not acknowledged FREC).
To access to the Fault Record, use the functions 3 or 4.
Alarms
Most IED LEDs can be configured for alarms. In most cases they are managed in a two-state way
that differs a lot from an IED to another or to the system (5 states).
An alarm is a standard event (time-stamped change of state managed by event rules), stored in
the IED till acknowledgment, and that aims at warning the operator via a LED.
There are 2 kinds of alarm:

• TRIP (signalling that a control is sent to a breaker when a particular protective function is
triggered)
• ALARM (other information intended for the operator)
1094 C264/EN UM/E50.5

Each alarm/trip indication is controlled by a bit in a set of consecutive cells (like Digital Inputs).
Each bit retains that alarm condition has been set (even if the condition is no more fulfilled). A
global Digital Output acknowledgment ‘Alarm/trip’ is used to reset all alarm indications. If one
alarm condition is still fulfilled, the corresponding bit is not changed by the IED, else it is reset
(with an event generation).
When at least one alarm is set in alarm cells (single alarm appearance), the bit 7 of fast status
byte is set.
When at least one Trip function is set in trip cells, the bit 6 of fast status byte is set.
Each bit is reset when all the alarm/trip appearance conditions have disappeared and a global
ACK alarm Digital Output is received.
A global ALARM/TRIP_ACK_DO is mapped (reset bit). IED mapping must explicitly give the list of
cells/bits indicating alarm/trip and effect on bits b6 and b7.
The answer to global ALARM_ACK_DO or global TRIP_ACK_DO (if applicable) to MiCOM C264
can never be BUSY (no applicative mechanism, only transport error code).
The bits b6 and b7 are directly linked to LEDs on the front face. The rule manages only 2 states for
LED ON or OFF, and no third state is managed. The state ON can be fixed or blinking. The current
mechanism is a global acknowledgement AND clearance of alarm list if the alarm appearance
condition has been reset.
10.4.3.3.3.6 Limits and specifications
It is mandatory that within the same range, each piece of equipment has the same operation as
others:
• Management of events file (event format/file address/address of acknowledgement DO).
• Management of Fault records (fault format, base fault addresses, address descriptive zone,
address of acknowledgment DO…).
• DIs, DOs, AIs are grouped at identical base addresses.
• Format of AI.
• Format of Status.
• Address range of the fundamental data.
In order to use information coming from IED in fast automation, or to answer to the SCADA
inquiries, or in alarm tagging, the following specifications are recommended:
• Operating time, answering time to the various requests < 20 ms.
• Low-level address filtering of the irrelevant requests.
• Respect of MODBUS protocol control (correct CRC, parity check, separate message silence
of 3.5-char time, continuous flow in one message i.e. a silence limited to 1.5-char
transmission time).
• Speed of communication: at least 19200 bauds (38400 is usual, 128000 is a future standard).
• If it is overbooked, a device must answer BUSY (exception code 06) or at least not answer (it
is reputed disconnected to be reconnected).
C264/EN UM/E50.5 1095

• An IED must answer with a delay lesser than 20ms.
• An IED can ask to implement a FAR BUSY (code 05) to solve an SRAM access problem.
MiCOM C264 repeats the request at N times its polling period. After 10 BUSY answers, the
IED is disconnected.
The official number of devices on Modbus is 32, 16 on PSCN3020 and future system. Typically,
the application engineers must not include more 8 IEDs to comply with common customer needs
(triggered analogues < 500ms, triggered DI < 100ms, physical ping as control/Digital Output/bi-
stable/Digital Input/alarm < 300ms, network avalanche profiles, …).
10.4.3.4 IED SPECIFIC MODBUS

Summary:
Extra Setting
Read Synchroni Command Tunnelin
IED function DI AI softwar
status z. s g
s e
4,
address 6 new Set &
M230 – – – ISDP
1, length formats read
3
not
RishM10 – – Generic Generic Generic –
specified
Flexgate x Flexgate Generic Generic Generic
SEPAM x Sepam Generic Generic Generic SFT
WAGO x – Generic Generic SP: 15 bits
No disturbance files.
10.4.3.4.1 M230
In addition to the generic Modbus, to test IED communication, the function code 4, address 1,
length 3 can be used.
Data received from M230
No DIs.
Analogue Inputs are regularly polled.
MiCOM C264 supports six 32-bit extra formats of Analogue Inputs:
Format Value Bit 31 thru 24 Bit 23 thru 16 Bit 15 thru 00
M230_T5_TYPE decimal
Unsigned.meas exponent Binary value unsigned
(signed)
M230_T6_TYPE decimal
Signed meas. exponent Binary value unsigned
(signed)
1096 C264/EN UM/E50.5

Format Value Bit 31 thru 24 Bit 23 thru 16 Bit 15 thru 00

Signed:
M230_T7_TYPE signed: Import/ Inductive/ Unsigned value
Power factor
Export (00/FF) capacitive (16 bytes)
(00/FF)
ION_
Reg. Low:
MODULUS_
10000RH+RL Reg. High: unsigned value/10000 unsigned value
10000_
modulus 10000
UNSIGNED
ION_ Reg. Low: signed
MODULUS_ 10000RH+RL Reg. High: signed value/10000 value modulus
10000_SIGNED 10000
KITZ202_K8 Refer to KITZ202 documentation
The byte transmission order is: 4-3-2-1.
Data sent to M230
The M230 is NOT synchronized using Modbus.
Setting software: IDSP application can NOT be used to set Date and Time, only the front panel
can.
The M230 does NOT process the commands.
The M230 can be set using MiCOM C264 Tunneling mode. IDSP application M230 setting
software can be used through tunneling mode to set or read data.
10.4.3.4.2 Rish Pro M01

Initialization sequence
To establish a communication with the relay (at MiCOM C264 start-up),MiCOM C264 reads
registers 202, 221, 222 (table of measurements) and registers 300 thru 392 (scaling factors
table).This initialization sequence is done after each disconnection (i.e. loss of communication or
communication error with the IED).
Without interruption:
Step MiCOM C264 Rish Pro M01

State Request Frame State
1 ← connection
read "table of
2 →
measurements"
3 ← measurements
read "scaling
4 →
factors table"
Wait
5
TimeOut
C264/EN UM/E50.5 1097

Step MiCOM C264 Rish Pro M01

5bis ← error
5ter Stand by
go to 2
6 ← end Time Out
Writes general
7 → RUNNING
status
8 Stand by
Timeout Ready
Disconnection:
State Request Frame State

5 Wait TimeOut
6 disconnection
7 Stand by
Writes general
8 → DCNX
status
Polling
The beginning of Digital Inputs and Analogue Inputs polling is delayed by a time-out starting at the
end of the Rish Pro M01 initialization. MiCOM C264 can send a synchronous frame during the
initialization phase. Depending on the function and the read use in this frame, the M01 answers
with a correct frame or an exception frame but does not invalidate the initialization.
Error management
The Rish Pro M01 has no register to read status value and the function 7 is not supported. So, to
detect a problem, MiCOM C264 uses the exception codes sent by the Rish Pro M01. Rish Pro
M01 generates the error codes that follow:
Code Description
01h Unsupported function code
Invalid memory register address: use of invalid register number or attempt to
02h
write to a memory protected register
03h Invalid data, i.e. an invalid number of registers
Device is busy. This code signals that the relay is occupied with functions
06h performed via the local RS 232 interface (changing configuration, simulation
or calibration of analogue outputs...)
1098 C264/EN UM/E50.5

Code Description
Possible change of rated values. The device configuration has been
modified since the latest request for measurements or this is the first request
0Ah
for measurements since the relay was switched on. Read the table of
measurements and the scaling factors table.
Error code 06h and 0Ah must be treated as a disconnection of the IED and a new initialization
phase must be completed before reading the Rish Pro M01 data. Other codes can be treated as
usually.
Only errors from initialization sequence or polling DIs and AIs report an error code. Errors from
synchronous frame only generate an error message, but do not cause a new initialization
sequence.
At reception of the message error code 0x6h or 0xAh, if the mode polling is active, reauthorize
future polling. The IED general status goes to INIT and MiCOM C264 goes to state "STAND BY"
and extracts the event "RISHM01 CNX".
In event of trouble, the IED sends the Modbus exception 'Busy'. The MiCOM C264 considers the
IED as disconnected (that will force the initialization sequence to be redone) but DOES NOT PUT
the IED information to unknown.
10.4.3.4.3 Flexgate
Polling
At MiCOM C264 start-up, a polling request is sent to determine the status (function 7). A response
means that the Flexgate IED is connected.
No Digital Inputs polling: a DI change is signaled by an event.
MiCOM C264 polls for fields ‘Internal status bits’ at address 18993 to 19000 with function 2:
Fields Address Description

Events pending bit 18993 Is there a new event ?
Time is not sent from Modbus master Is Flexgate IED synchronized with
18994
within last 16 minutes MiCOM C264 ?
Time is not synchronized by minute
18995 Not used
pulse within last 1.5 min
Other data received from Flexgate
If an event is received (flag at Modbus address 18993), MiCOM C264 reads the events queue.
To read the events, MiCOM C264 realize an alternative reading between addresses 39001 and
39011, which allows reading next event.
If MiCOM C264 reads the same address – without any other request in between – it gives the
same event.
The Flexgate sends a response on six words. Refer to the converter documentation.
MiCOM C264 continues to read the event file until there is no new event. Then, it polls for the
‘Internal status bits’.
C264/EN UM/E50.5 1099

Sequence numbers
In the event response, the sequence number is between 1 and 65535.
Reserved numbers:
• 0 indicates that there is no event anymore
• 1 indicates that the converter (Flexgate) has been reinitialized
• 50 indicates the re-initialization of the converter (Flexgate)
• 51 indicates an overflow events buffer. The event buffer size is 200. The Flexgate does not
allow to add new events until the event 51 is read. At this time, MiCOM C264 considers that
one or more events have been lost. Then it repeats the General Interrogation, and the cycle
continues starting with the internal status bits polling.
If a gap appears in the sequence number, MiCOM C264 considers that an event has been lost.
Then it repeats the General Interrogation; the cycle continues polling the internal status bits.
Data sent to Flexgate
MiCOM C264 sends Date and Time in one request with function 16 at Modbus addresses
49001…49007 (2328h to 232Eh).
The following format is used to write the date: [year/month/day/hour/minutes/milliseconds since

midnight] to two words by data except for milliseconds which takes four words.
MiCOM C264 periodically sends the date to synchronize the Flexgate. The time must be sent with
a period smaller than 16 minutes.
As they are sent to a specific address, there can be only one Flexgate on the legacy bus.
Error management
Flexgate generates the error code that follows:
Code Description
Illegal data value, i.e. invalid number of register (send a “Configuration error” message
03h to the application and continue). Also used to indicate a hardware malfunction like an
interlock condition not ok on a protective relay
10.4.3.4.4 SEPAM
As for standard Modbus, three modes are available:
• ‘General Interrogation’: MiCOM C264 waits for the end of initialization, the disappearance of
data loss signal. Then, it polls for all the DIs.
• 'Desynchronized': events are NOT managed. The DIs are updated by polling. DIs are read
and decoded group by group. The status is read and decoded when all the groups have been
read.
• 'Synchronized': events are managed. MiCOM C264 reads the status word, then the events.
The DIs are updated when the events are decoded.
Data received from Sepam
DIs
1100 C264/EN UM/E50.5

• Modes GI and ‘not synchronized’:
a. MiCOM C264 reads DI group with function 3 at address that follow:
Mode Address Sepam 40 Address Sepam 80

GI 0x100 thru 0x10A 0xC10 thru 0xC16
‘not
0x100 thru 0x10A 0xC90 thru 0xC9F
synchronized’
b. When it receives a data, it decodes the status frame and the DI group frame.
• Mode ‘synchronized’:
a. MiCOM C264 reads the status frame (function 7) till it detects a data
b. it checks event and reads the event table using function 3 at address 0x40 with size 33.
c. it decodes the event frame and acknowledges using function 6 at address 0x40 with
value ‘ExchangeNumber’ at 0.
Data sent to Sepam
Date and time format: [Day/month/Year Hour.Min:Ms] [14/5/38 6.43:16785] for the 38th year
since 1970 (ie. 2008), the 14th May at 6 hours 43 minutes and 16785 milliseconds.
Address for synchronization: 0x0002.
10.4.3.4.5 WAGO
The Wago relay behaves generically except for the setpoints that are integers not signed on 15
bits.
10.4.4 DNP 3.0 Communication

The purpose of this chapter is not to describe the DNP3 protocol but to specify the use of the
DNP3 protocol on a legacy bus of the MiCOM C264.
As the MiCOM C264 is the master on the legacy bus - regards to protections and IEDs - this
protocol is referenced as “Master DNP3” in the MiCOM C264.
Here are described:

• Specific behaviours attached to the protocol DNP3
• Restriction and enhancement
• Part of the DNP3 protocol used and not used

10.4.4.1.1 Input
Object Variation Data GI Polling Function

01 0 Static BI (SPS) X [1] READ
02 0 BI Event (SPS) X [1] READ
20 0 Static Counter X [1] READ
C264/EN UM/E50.5 1101

Object Variation Data GI Polling Function

22 0 Counter Event X [1] READ
30 0 Static Measurement X [1] READ
32 0 Measurement Event X [1] READ
60 01 Class 0 X [1] READ
60 02, 03, 04 Class 1,2,3 X [1] READ
NOTE: BI, Measurement and Counter are polled with the variation 0. That means that all
variations are required.
All other DNP3 objects are not treated.
10.4.4.1.2 Output
Object Variation Data Function Note

[3] SELECT Treated
Command:
[4] OPERATE Treated
12 01 Control Relay
Output Block [5] DIRECT
Treated
OPERATE
50 01 Time and Date [2] WRITE Treated
The DNP3 Master manages both direct control Command and Select before Operate for digital
control only.
When operate command is received from application, the Master checks in database to know if
the command is:
1. An execute command, which belongs to a SBO Control: OPERATE function is used in this
case.
2. A direct control: DIRECT OPERATE function is used is this case
10.4.4.2 Behavior
• Synchronization:
The “Master DNP3” is always synchronized by the MiCOM C264. No calculation of the
transmission delay is performed.
The DNP3 object used to synchronize IEDs is “Write Date and Time Request (Object 50,
Variation 01).
Synchronization is performed first at connection of an IED.
Then, synchronization is sent cyclically to all the IEDs.

• Initialization:
To connect an IED, a “Reset CU” (function 0) frame is sent to the IED.
When the response is OK, the Master DNP3 send a message to the application to tell that
connection step is passed.
Next step is General Interrogation
1102 C264/EN UM/E50.5

• General Interrogation:
When the IED is connected, the MiCOM C264 ask for static data state and value with a
sequence of:
Read BI,
Read Measurement,
Read TPI,
Read Counter
This Sequence is the General Interrogation. Next step is Polling

• Polling:
The polling cycle depends on the configuration:
class 0 only: the CURRENT value of a BI, measurement, or counter, …. is polled for. The
GI polling period is configurable using the “class 0 polling period” configuration
parameter; when this parameter is set to 0 second, there is no cyclic GI.
Poll Class 0 or Class 1 or Class 2 or Class 3: this is a poll for all EVENT data followed in
return by all (static) current data.
The polling cycle must be interrupted at minimum in the two following cases:
Clock Synchronization
Remote control
• Event acquisition:
Event occurs spontaneously. The slave device waits for being polled by the master. With
unsolicited reporting, Slave devices can send updates as values change, without having
to wait for a poll from the Master.
• IED monitoring:
A General Interrogation may be done after connection of an IED

• Digital inputs:
A DI is identified by an Index, associated to a couple “Object + Variation” which identify

the type of data.
Digital inputs which are received as changes of state are identified by the DNP3 object
number 02
Digital inputs which are received as static data are identified by the DNP3 object number
01
• Measurements:
A Measurement is identified by an Index, associated to a couple “Object + Variation”

which identify the type of data.
Both analogue and numeric measurements are treated
C264/EN UM/E50.5 1103

Measurements which are received as changes of state are identified by the DNP3 object
number 32
Measurements which are received as static data are identified by the DNP3 object
number 30
• Counters:
A Counter is identified by an Index, associated to a couple “Object + Variation” which

identify the type of data.
Counters which are received as changes of state are identified by the DNP3 object
number 22
Counters which are received as static data are identified by the DNP3 object number 20

• Controls:
A Control is identified by an Index, associated to a couple “Object + Variation” which

identify the type of data.
In case of basic control (Set, Reset, Trip, Close), DNP3 object 12 is used with the
Variation 01
10.4.4.5 Master DNP3 Profile
NOTE: Please refer to the interoperability documentationEPAS 6 Master Protocol Profile (MPP)
DNP3.
10.4.4.6 DNP3 Level 3 Implementation Table

Underlined information in grey are not implemented
REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Func
Qual Codes Qual Codes
Obj Var Description Codes Code
(hex) (hex)
(dec) (dec)
Binary Input – All
1 0 1, 22 00,01,06
Variations
00,01 (start-
1 1 Binary Input 1 00,01,06 129
stop)
Binary Input with 00,01 (start-
1 2 1 00,01,06 129
Status stop)
Binary Input Change -

2 0 1 06,07,08
All Variations
Binary Input Change

2 1 1 06,07,08 129 17,28 (index)
without Time
1104 C264/EN UM/E50.5

REQUEST RESPONSE
OBJECT
Binary Input Change
2 2 1 06,07,08 129 17,28 (index)
with Time
Binary Input Change

2 3 1 06,07,08 129,130 17,28
with Relative Time
Binary Output - All

10 0 1 00,01,06
Variations
10 1 Binary Output
10 2 Binary Output Status 1 00,01,06 129 00,01
Control Relay Output Request

12 1 3,4,5,6 17,28 (index) 129
Block (1) echo
Binary Counter - All 1,

20 0 00,01,06
Variations 7,8,9,10,22
00,01 (start-
20 1 32-Bit Binary Counter 1 00,01,06 129
stop)
00,01 (start-
20 2 16-Bit Binary Counter 1 00,01,06 129
stop)
32-Bit Binary Counter 00,01 (start-
20 5 1 00,01,06 129
without Flag stop)
16-Bit Binary Counter 00,01 (start-
20 6 1 00,01,06 129
without Flag stop)
1. Commands must be selected/executed on one point
Frozen Counter - All

21 0 1 00,01,06
Variations
32-Bit Frozen
21 1 1 00,01,06 129 00,01
Counter
16-Bit Frozen
21 2 1 00,01,06 129 00,01
Counter
32-Bit Frozen
21 9 1 00,01,06 129 00,01
Counter without Flag
16-Bit Frozen
21 10 1 00,01,06 129 00,01
Counter without Flag
Counter Change
22 0 1 06,07,08
Event - All Variations
C264/EN UM/E50.5 1105

REQUEST RESPONSE
OBJECT
32-Bit Counter
22 1 Change Event 1 06,07,08 129 17,18 (index)
without Time
16-Bit Counter
without Time
32-Bit Counter
22 5 Change Event with 1 06,07,08 129 17,18 (index)
Time
16-Bit Counter
22 6 Change Event with 1 06,07,08 129 17,18 (index)
Time
Remarks: Frozen counters (type21) are uploaded during general interrogation, but never polled
after this.
Frozen Counter
23 0 1 06,07,08
32-Bit Frozen
23 1 Counter Event 1 06,07,08 129,130 17,18 (index)
without Time
16-Bit Frozen
23 2 Counter Event 1 06,07,08 129,130 17,18 (index)
without Time
32-Bit Frozen Delta

23 3 Counter Event 1 06,07,08 129,130 17,18
without Time
16-Bit Frozen Delta

23 4 Counter Event 1 06,07,08 129,130 17,18
without Time
Analogue Input - All

30 0 1 00,01,06
Variations
00,01 (start-
30 1 32-Bit Analogue Input 1 00,01,06 129
stop)
00,01 (start-
30 2 16-Bit Analogue Input 1 00,01,06 129
stop)
32-Bit Analogue Input 00,01 (start-
30 3 1 00,01,06 129
without Flag stop)
1106 C264/EN UM/E50.5

REQUEST RESPONSE
OBJECT
16-Bit Analogue Input 00,01 (start-
30 4 1 00,01,06 129
without Flag stop)
Analogue Change
32 0 1 06,07,08
32-Bit Analogue
without Time
16-Bit Analogue
32 2 Change Event 1 06,07,08 129, 17,18 (index)
without Time
32-Bit Analogue
32 3 Change Event with 1 06,07,08 129,130 17,18
Time
16-Bit Analogue
32 4 Change Event with 1 06,07,08 129,130 17,18
Time
Analogue Output
40 0 1 00,01,06
Status - All Variations
32-Bit Analogue 00,01 (start-

40 1 1 00,01,06 129
Output Status stop)
16-Bit Analogue 00,01 (start-

40 2 1 00,01,06 129
Output Status stop)
32-Bit Analogue Request

41 1 5,6 17,28 (index) 129
Output Block echo
16-Bit Analogue Request

41 2 5,6 17,28 (index) 129
Output Block echo
Time and Date - All

50 0
Variations
07 07
50 1 Time and Date 1 129
(quantity=1) (quantity=1)
Time and Date with 07

50 2 2
Interval (quantity=1)
07
51 1 Time and Date CTO 129,130
(quantity=1)
C264/EN UM/E50.5 1107

REQUEST RESPONSE
OBJECT
Unsynchronized 07
51 2 129,130
Time and Date CTO (quantity=1)
07
52 1 Time Delay Coarse 129,
(quantity=1)
07
52 2 Time Delay Fine 129,
(quantity=1)
60 1 Class 0 Data 1 06
1 06,07,08
60 2 Class 1 Data
20,21,22 06
1 06,07,08
60 3 Class 2 Data
20,21,22 06
1 06,07,08
60 4 Class 3 Data
20,21,22 06
00 (start-
2 stop)
80 1 Internal Indications (index=7)
00,01 (start- 00,01 (start-

1 129
stop) stop)
No Object (Cold Restart) 13
No Object (Delay Measurement 23
“On-line” Quality bit management:
The table below described the management of the DNP3 binary input status object for each SPS
status. This management is the same whether the information is with or without time tag. SBMC is
off.
[0x4100]
IEC 61850 SPS Quality [0x0000] VALID
UNKNOWN
IEC 61850 Associated SPS State V V
DNP3 binary input status object
State BS1[7] V X
Reserved BS1[6] X X
Chatter filter BS1[5] X X
Local Forced BS1[4] X X
1108 C264/EN UM/E50.5

[0x4100]
IEC 61850 SPS Quality [0x0000] VALID
UNKNOWN
Remote Forced BS1[3] X X
Comm.lost BS1[2] X X
RestartBS1[1] X X
On-line BS1[0] 1 0
V stands for received value or start-up value
“-“ stands for 0. When 0 is significant for the understanding, 0 appears in the cell.
“X” stands for “Status bit indifferent”.
NOTE: IEC 61850 TOGGLING, SELFCHECK FAULTY, SUPPRESSED, FORCED and

SUBSTITUED status are not used with DNP3 MASTER Protocol. When the IED is
disconnected, the SPS status is set to “UNKNOWN”.
IEC 61850 MV Quality [0x0000] [0x4100] [0x6000]

DNP3 Analogue input status object VALID UNKNOWN OVERRANGE
IEC MV VALUE V V V
Reserved [7] X X X
Reference error BS1[6] X X X
Over-range BS1[5] 0 0 1
Local Forced BS1[4] X X X
Remote Forced BS1[3] X X X
Comm.lost BS1[2] 0 1 X
RestartBS1[1] X X X
On-line BS1[0] 1 X X

DNP3 Analogue input status object VALID UNKNOWN UNDEFINED
IEC MV VALUE V V V
Reserved [7] X X X
Reference error BS1[6] X X X
Over-range BS1[5] 0 0 1
Local Forced BS1[4] X X X
Remote Forced BS1[3] X X X
Comm.lost BS1[2] 0 1 X
C264/EN UM/E50.5 1109


DNP3 Analogue input status object VALID UNKNOWN UNDEFINED
RestartBS1[1] X X X
On-line BS1[0] 1 X X
[0x4200]
IEC 61850 Quality Status [0x0000] [0x4100] [0x6000]
SELFCHECK
DNP3 counter status object VALID UNKNOWN OVERRANGE
FAULTY
Counter VALUE V V V V
Reserved [7] X X X X
Reserved BS1[6] X X X X
Roll-Over BS1[5] 0 0 0 1
Local Forced BS1[4] X X X X
Remote Forced BS1[3] X X X X
Comm.lost BS1[2] 0 0 1 X
RestartBS1[1] X X X X
On-line BS1[0] 1 0 X X
10.4.5 IEC 60870-5-103 Communication

The purpose of this chapter is not to describe the T103 but to specify the use of the T103 protocol
on a legacy bus of the MiCOM C264.
As the MiCOM C264 is the master on the legacy bus - regards to protections and IEDs - this
protocol is referenced as “Master T103” in the MiCOM C264.
Here are described:

• Specific behaviours attached to the protocol T103
• Restrictions and enhancements
• Part of the T103 protocol used and not used
• Specific behaviours attached to implementation of Private Range of T103

10.4.5.1.1 Input
ASDU Data Note

Dated Digital input (absolute dating)
1 Treated
Control acknowledgement
1110 C264/EN UM/E50.5

ASDU Data Note

2 Dated Digital input (relative dating) Treated
3 Measurement Treated
4 Measurement : Default position Treated
5 Identification Not treated
Time synchronisation
6 Treated
acknowledgement
8 End of GI Treated
9 Measurement Treated
Not treated (some measurements
10 General Data
only)
11 General Identification Not treated
17 Measurement Reg D only
23 … 31 Disturbance file management Treated
45 Ack of Single Command MiCOM Px3x only
46 Ack of Double Command MiCOM Px3x only
Analog protection signal
49 Only adress 0 which is DVICE: MiCOM Px3x only
Device type
65 Single Point MiCOM Px3x only
66 Single Point with Time Tag MiCOM Px3x only
67 Double Point MiCOM Px3x only
68 Double Point with Time Tag MiCOM Px3x only
BitString 32 Bit without time tag-
couple FUN /TYP computed :
71 MiCOM Px3x only
F8h / 70h : State of the IED
F8h / 74h : Request Station Interlock
BitString 32 Bit with time tag – see
72 MiCOM Px3x only
ASDU 71
73 Measurement, Normalised value MiCOM Px3x only
77 Measurement MiCOM Px2x only
79 Energy Counter MiCOM Px3x only
10.4.5.1.2 Output
ASDU Data Note

6 Time synchronisation Treated
7 Request a GI Treated
C264/EN UM/E50.5 1111

ASDU Data Note

20 Command Treated
23 … 31 Disturbance file management Treated
45 Single Command MiCOM Px3x only
46 Double Command MiCOM Px3x only
Read protection parameter
140 Only address 0 which is DVICE: MiCOM Px3x only
Device type
144 Setpoint Reg D only
10.4.5.2 Behavior
10.4.5.2.1 Synchronization
The “Master T103” link is always synchronized by the MiCOM C264. No calculation of the
transmission delay is performed.
10.4.5.2.2 Polling
To connect an IED, a “Reset CU” frame is sent to the IED.
By default, an IED is polled by a “Polling C2” frame, allowing to get “non priority information”.
If an IED signals it has “priority information”, it is polled with a “Polling C1” frame.
10.4.5.2.3 IED monitoring

The “OUT_OF_SERVICE” state is managed. It corresponds to the “Lock of communication” [DI
20].
A GI may be done after each end of Tunneling session.
The MiCOM C264 may regularly look for Disturbance file presence
10.4.5.2.4 Tunneling mode

During tunneling mode, only polling C2 may be done by the MiCOM C264 [Normally, if “priority
information” is present, the remote Master may send a “polling C1 frame”].
The MiCOM C264 must spy the tunneling exchange in order not to lose information [DI and AI
change].
For security reason, at the end of a tunneling session, a GI is done.
10.4.5.2.5 Station Interlocking

This functionality is only available on MiCOM P139 in private T103 range (Schneider Electric D
protocol variant)
After GI, and only if IED is MiCOM Px3x, we send a read on MiCOM Px3x parameter address 0
which corresponds to Device Type. If MiCOM Px3x responds with analog parameter set to 139,
we activate Station Interlocking Management.
Case of local control (front panel of the MiCOM P139) with Station interlock:
1112 C264/EN UM/E50.5

As soon as a user will try to control a switchgear by the front panel, the MiCOM P139 will send an
ASDU 72 with FUN/TYP = F8h/74h in order to request to EPAS system the station interlock
conditions. EPAS system should check if the command is allowed (specific treatment done by
CONDUITE of the computer) and respond to the MiCOM P139.
remote control (from EPAS system) with Station interlock:
As soon as a user will try to control a device managed by MiCOM P139 by EPAS system through
T103 communication, the MiCOM P139 will send an ASDU 72 with FUN/TYP = F8h/74h in order
to request to EPAS system the station interlock conditions. EPAS system should respond to the
MiCOM P139 with a positive acknowledgment (checks have already been done before)
If station Interlock is de-activated on MiCOM P139, the control of a switchgear on MiCOM P139
by EPAS system through T103 communication is done by an EXECUTE ORDER (selection will
be refused by MiCOM P139)
10.4.5.2.6 REG D
The Reg D equipment manages 2 ASDU (144 and 17), for control of setpoints (144) and setpoint
value feedback (17), which is treated as a measurement in the computer. Setpoints managed by
the Reg D are "Direct Execute" only, there is no SBO management. The Reg D setpoint command
sequence is like the command sequence (ASDU20). The computer sends the setpoint (ASDU
144), with the setpoint value, the Reg D sends its acknowledge (ASDU1), if the acknowledge is
OK, the Reg D sends the setpoint value feedback (ASDU17).
10.4.5.2.7 Tapcon260
The Tapcon260 equipment supports ASDU 204 / FUN TYP=110/ INF=54 for TPI acquisition.
Nevertheless, the object type in SCE must be MV, not TPI.

10.4.5.3.1 Digital inputs
An ASDU number [(1,2) in public Range],[(66,67,68,69) in private Range]
A DI is identified by a couple (Function Type, Information Number).
Digital inputs are received as changes of state.
Special DI may be managed:

• DI 20: Lock of the communication. A GI must be done when the communication is unlocked
• DI 23 to 26: Change of configuration number
• DI which are not transmitted during a GI. For these DI, the IED signals only change of state
from OFF to ON. The MiCOM C264 must generate by itself the change from ON to OFF.
A Measurement is identified by:
• An ASDU Number [(3,4,9) in public range, (10, 21, 73,77) in private range]
• a couple (Function Type, Information Number)
• the rank of the Measurements in the ASDU
C264/EN UM/E50.5 1113

• the kind of Measurements [Current, Voltage, Power, Frequency, Other]
• the common address of ASDU
ASDU 21 and 10 provide the acquisition of the following measurements coming from P44x relay:
• Current tripping values
• Residual voltages and currents
• Sum of trips
• Sum of cut amperes
MiCOM C264 polls regularly the cells containing the measurement values.
It reads by ASDU 21 a single entry:
Description TI VSQ COT ADR FUN INF RII NOG GIN KOD
Courier
Measurement 15H 81H 2AH CAD FEH F4H x 1 cell 1
number
TI = Type identification
VSQ = variable structure qualifier
COT = cause of transmission
ADR = CAD = common address
FUN = function number
INF = information number
RII = Return information identifier
NOG = Number Of Generic identification
GIN = Generic Identification Number
ASDU 10 provides the response.
10.4.5.3.3 Bitstring 32-bits :

The state of the IED is identify by the ASDU 71 or 72 with couple FUN / TYP = F8h / 70h. This
ASDU describes the status of the IED (Station Interlocking active or not …)
A request to check station interlocking is identify by the ASDU 71 or 72 with couple FUN / TYP =
F8h / 74h. In this request, the couple FUN/TYP of the command to spend is defined.
10.4.5.3.4 Analog protection signal (ASDU 49) :

Only for MiCOM Px3x, an analogue protection signal is received after GI
Only address 0 is managed. It is used to recognize MiCOM P139 in order to activate station
interlocking management.
10.4.5.3.5 Energy counter (ASDU 79) :

Only for MiCOM Px3x, four energy counters are available.
Energy counters are identified by:
1114 C264/EN UM/E50.5

• An ASDU number (79) in private range
• a couple Function Type, Information number
• the rank of the counter in the ASDU
• the common address of the ASDU
DB0- DB5- DB10- DB15-

Description TI VSQ COT ADR FUN INF
DB4 DB9 DB14 DB19
Energy Active Active Reactive Reactive
4FH 04H 01H CAD F8H 6CH
counter + - + -
TI = Type identification
VSQ = variable structure qualifier
COT = cause of transmission
ADR = CAD = common address
FUN = function number
INF= information number
DB0-DB4 = active energy output
DB5-DB9 = active energy input
DB10-DB14 = reactive energy output
DB15-DB19 = reactive energy input
Format of the energy counter value
Value
Value
Value
S Value
Sequence
IV CA CY
number
S : 0 Value positive, 1 = value negative
CY : 0 = no carry, 1= carry
CA : 0 = not adjusted, 1 = adjusted

10.4.5.4.1 Controls
An ASDU Number and a couple (Function Type, Information Number) identify a control.
The acknowledgment of a control is to be waited as:

• A DI with the same (Function Type, Information Number) as the control and with a ‘Cause Of
Transmission’ equals to ‘positive return’ or ‘negative return’ in public range
C264/EN UM/E50.5 1115

• A ASDU 45 or 46 with a ‘Cause Of Transmission’ equals to ‘end of activation OK’ or ‘en of

activation KO’, or ‘deactivation OK’, or ‘deactivation KO’ in private range
10.4.5.4.2 Setpoints Controls :

A setpoint control is identified by an ASDU Number plus a couple (Function Type, Information
Number). In the case of the Reg D equipment the ASDU is 144.
The acknowledgment of a setpoint control is to be waited as :

• A DI (ASDU 1) with the same (Function Type, Information Number) as the control and with a
‘Cause Of Transmission’ equals to ‘positive return’ or ‘negative return’ in public range.
• An ASDU 17 with a ‘Cause Of Transmission’ equals to ‘Local Operation’ in public range. The
ASDU is a measurement which contains the setpoint feedback value.
10.4.5.4.3 Read protection parameter :

Only for MiCOM Px3x, a read of protection parameter (ASDU 140) address 0 (Device Type) is
sent to IED
The IED responds with ASDU 49 in which Device Type is set (139 if IED is a MiCOM P139 for
example).
10.4.5.4.4 ASDU 232 / 105 management

It allows to send control to IEC 60870-5-103 legacy IED. It requires to manage also the ASDU 105
as response to ASDU 232.
Comparing ASDU232 & ASDU20
ASDU232 ASDU20
Field Value Field Value
ASDU No E8H ASDU No 14H
VSQ 81H VSQ 81H
COT 14H COT 14H
Common Address of
Device address @ied @ied
ASDU
DN2 Cfg Function type Cfg
DN3 Cfg Information Number Cfg
DC0 1=OFF; 2=ON DC0 1=OFF; 2=ON
X 0 RII Set by master
Comparing ASDU105 & ASDU01
ASDU105 ASDU01
Field Value Field Value
ASDU No 69H ASDU No 01H
VSQ 81H VSQ 81H
1116 C264/EN UM/E50.5

ASDU105 ASDU01
COT 45H, 46H, 47H, 7FH COT 14H, 15H, 0BH
Common Address of
Device address @ied @ied
ASDU
DN2 Idem ASDU232 Function type Idem ASDU20
DN3 Idem ASDU232 Information Number Idem ASDU20
DPI 1=OFF; 2=ON DPI 1=OFF; 2=ON
X 0 msLow
msLow msHigh Four octet binary time
Four octet binary
msHigh IV 0 mmmmmm CP32Time2a
time
IV 0 mmmmmm SU 00 hhhhhh
CP32Time2a
SU 00 hhhhhh SIN Idem RII ASDU20
Configuration
Management of commands through ASDU 232.

• The ASDU number [232]
• DN2 & DN3 (respectively ‘y’ & ‘x’ component of PID)
Management of state through ASDU 105.

• The ASDU number [232]
• DN2 & DN3 (respectively ‘y’ & ‘x’ component of PID)
DN2 & DN3 will be given – respectively – as ‘Function type’ & ‘Information Number’.

10.4.6.1 Purpose
The purpose of this chapter is not to describe the T101 but to specify the implementation of T101
protocol on a legacy bus inside the MiCOM C264.
10.4.6.2 Master IEC 60870-5-101 profile

The purpose of this section specifies the T101 protocol implementation for a legacy bus inside
MiCOM C264.
Please refer to the interoperability documentation EPAS 6 Master Protocol Profile (MPP) T101.

10.4.7.1 Purpose
The purpose of this chapter is not to describe the T104 but to specify the implementation of T104
protocol on a legacy bus inside the MiCOM C264.
10.4.7.2 Master IEC 60870-5-104 profile

The purpose of this section specifies the T104 protocol implementation for a legacy bus inside
MiCOM C264.
C264/EN UM/E50.5 1117

Please refer to the interoperability documentation EPAS 6 Master Protocol Profile (MPP) T104.
1118 C264/EN UM/E50.5

MiCOM C264 - User Manual 11 Commissioning
11 Commissioning
11.1 Scope 1120

11.1.1 Responsabilities 1120
11.1.3 Definition 1120
11.1.4 Commissioning the product 1120
11.1.5 Setting familiarization 1121
11.3 Commissioning Tests with GHU20x (with LCD) 1123
11.3.1 Preparation 1123
11.3.2 Check version & number 1123
11.3.4 Check the boards status 1124
11.3.5 Check the binary signal inputs 1125
11.3.6 Checking the output relays 1126
11.3.7 Testing the communication with external devices 1127
11.3.8 Testing the control functions 1127
11.3.9 Switching from local to remote control 1127
11.3.9.1 Local control 1127
11.3.9.2 Remote control 1127
11.3.10 Protection Commissioning Test environment 1128
11.3.10.1 Injection test sets 1128
11.3.10.2 Protection Commissioning test sheets 1128
11.3.10.3 Use of a Core Balance CT for earth faults 1129
11.3.10.3.1 Cable shields and core CT 1129
11.3.10.3.2 Core CT polarity 1129
11.3.10.3.3 Protection parameters check 1130
11.3.10.3.4 Settings 1130
11.3.10.3.6 MiCOM C264P procedure 1130
11.3.10.4 Thresholds validation 1131
11.3.10.4.1 MiCOM C264P protection parameters 1131
11.3.10.4.2 MiCOM C264P Overcurrent parameters 1131
11.3.10.4.2.1 Phase overcurrent I> threshold test 1132
11.3.10.4.2.2 Phase to phase (phase to neutral) over-voltage U> threshold test 1135
11.3.10.4.2.3 Earth fault overcurrent and residual over voltage test. 1135
11.3.10.4.3 MiCOM C264P frequency parameters 1137
11.3.10.4.3.1 Over and Underfrequency test 1137
11.3.10.4.3.2 Rate of change of frequency test 1138
11.4 Commissioning Tests with GHU21x (without LCD) 1140
C264/EN UM/E50.5 1119

11 Commissioning MiCOM C264 - User Manual
11.1 Scope
This chapter describes the commissioning of MiCOM C264 and should not be confused with its
application commissioning (see "Definition" on page 1120). MiCOM C264 commissioning follows
its installation (see "Installation" on page 931).
11.1.1 Responsabilities
Most commissioning activities involve a power supply that can damage the installation or cause
injury to the operator. The chapter "Safety and Handling" on page 55 and the other chapters
involved in commissioning should be read carefully before any handling.
Before starting commissioning, the contractual and human responsibilities should be clearly
defined.
Only qualified and competent persons should carry out commissioning and the validation tests.
11.1.2 Introduction
To commission MiCOM C264, it is necessary to verify that the hardware is functioning correctly
and that the application-specific software settings have been applied to the MiCOM C264.
To verify that the MiCOM C264 is operating correctly, a database has to be loaded into the
computer. Once the database has been loaded, tests should be performed on each a single
MiCOM C264 element.
As the MiCOM C264’s menu language is user-selectable, it is acceptable for the Commissioning
Engineer to change it to allow accurate testing as long as the menu is restored to the customer’s
preferred language on completion.
11.1.3 Definition
The objective of commissioning is to prove that the equipment, and any interconnections to
process and other system components, is suitable for its intended purpose.
Commissioning is the activity that demonstrates that the equipment is acceptable for service. As
digital devices are configured for specific application, the commissioning can be split into two
main parts:
• Commissioning the product.
• Commissioning the application (when product has had its database loaded). This second part
is documented and carried out through FAT (Factory Acceptance Tests), and SAT (Site
Acceptance Tests) activities.
The scope of this chapter is the description of commissioning tests that prove that the
MiCOM C264 is suitable for further application tests.
11.1.4 Commissioning the product

Commissioning the product starts with product reception and is continued through all off the
installation procedures. Activities are divided between: -
• Visual inspection at reception.
• Inspection at Front Panel when MiCOM C264 is powered up.
1120 C264/EN UM/E50.5

• The starting point is the delivery form that describes all of the delivered hardware components
that constitute the MiCOM C264.
11.1.5 Setting familiarization

Commissioning the MiCOM C264 requires operation of its Human Machine Interface (the Local
Control Display). The chapter "Human Machine Interface" on page 498 contains a detailed
description of the menu structure of MiCOM C264.
The commissioning engineer should have had training on the HMI or sufficient time should be
allowed to become familiar with it (with an already commissioned device).
C264/EN UM/E50.5 1121

11.2 Requirements
It is essential that all requirements expressed in chapter "Installation" on page 931 have been
fulfilled.
The delivery form is the starting document.
1122 C264/EN UM/E50.5

11.3 Commissioning Tests with GHU20x (with LCD)

11.3.1 Preparation
After the MiCOM C264 has been installed and connected as described in Chapters "Installation"
on page 931, the commissioning procedure can begin.
Before turning on the power supply voltage, the following items must be checked:
• Is the device connected to the protective ground at the specified location?
• Does the nominal (and measured) voltage of the battery agree with the nominal auxiliary
voltage of the device?
• Are the current and voltage transformer (if used) connections, grounding, and phase
sequences correct?
After the wiring work is completed, check the system to make sure it is properly isolated.
Once all checks have been made, the power supply voltage may be turned on.
After the voltage has been applied, the MiCOM C264 starts up.
During start-up, various tests are carried out (see section entitled ‘Diagnose level1’ in Chapter
"Maintenance" on page 1144.
The LED indicator labeled ‘HEALTHY’ (Fourth LED) will light up.
After approximately 30 s, the MiCOM C264 is ready for operation.
In initial, factory-set condition or after a cold restart, the front panel displays a message
“Schneider Electric”.
After the settings have been made, the following checks should be carried out before any
interlocks or isolation is canceled:
• Are the software and database versions compatible with the hardware?
• Are all boards correctly assigned within the MiCOM C264?
• Are all IOs correctly configured and recognized by the MiCOM C264?
• Are all communications (Station BUS, Telecontrol BUS, Legacy BUS) correctly configured
and recognized?
• Are the control functions fully operational?
• Is the automation running?
The following chapters describe the checks to be performed to answer these questions and
ensure that the MiCOM C264 is fully operational in its application.
11.3.2 Check version & number

In the commissioning process the Service panel is the first to check. The MiCOM C264 serial
number tells if the MiCOM C264 is the ordered one, and indirectly gives the hardware version.
The database version is given by EPAS-SCE database version and describes all the settings on
the MiCOM C264.
The operational mode indicates whether the device is in a maintenance or operational mode.
C264/EN UM/E50.5 1123

- Figure 664 - GHU20x - Service panel

11.3.3 Faults
If the first LED is alight, this means that there is something wrong inside the MiCOM C264.
The FAULT panel gives information about the problem.
- Figure 665 - GHU20x - Fault panel
11.3.4 Check the boards status

MiCOM C264 front panel gives access to MiCOM C264 boards status (refer to chapter "Human
Machine Interface" on page 498).
Board labels are defined during the configuration phase. They are based on short names and are
indexed automatically. The default configuration model is:
• GHU Graphical Human Unit
• BIU Basic Interface Unit (power supply)
• CCU Circuit breaker Control Unit (SBO board)
• DIU Digital Input Unit
• DOU Digital Output Unit
• AIU Analogue Input Unit (DC current and voltage input)
1124 C264/EN UM/E50.5

• TMU Transducerless Measurements Unit (CT/VT board)
• AOU Analogue Output Unit (4 current analogue output)
The product checks whether the number of installed boards matches with the number of boards
configured, the following messages are generated depending on the results:
• PresConf: Board configured present and operational
• Failure: Board configured present and faulty
• ConfButMissing: Board configured not present
• Too Many: Board not configured but present (spare)
- Figure 666 - GHU20x - Board panel
11.3.5 Check the binary signal inputs

MiCOM C264 front panel gives access to input status for all DI boards (DIU200, DIU211, CCU211
or CCU200).
For DIU200 and DIU211 boards:
- Figure 667 - GHU20x - DIU200 and DIU211 input status
For CCU200 and CCU211boards:
C264/EN UM/E50.5 1125

- Figure 668 - GHU20x - CCU200 and CCU211 input status
11.3.6 Checking the output relays

MiCOM C264 front panel gives access to output relays status for all DO boards (DOU201,
CCU211 or CCU200).
For DOU201 boards:
- Figure 669 - GHU20x - DOU201 output relays
For CCU200 and CCU211 boards:
- Figure 670 - GHU20x - CCU200 and CCU211 output relays
1126 C264/EN UM/E50.5

11.3.7 Testing the communication with external devices

The IED panel gives access to the connection state with external devices on Ethernet protocol or
serial links:
- Figure 671 - GHU20x - IED panel
11.3.8 Testing the control functions

The selected bay type is displayed on the Bay Panel. The activation of the Bay Panel display is
described in Chapter "Human Machine Interface" on page 498.
If the position signals of the switchgear units are connected correctly to the MiCOM C264, then
the updated switching status of the switchgear units will be displayed on the bay panel.
If the switching status is not displayed correctly, the user can check the physical state signals of
the binary inputs to determine whether the status signals in the MiCOM C264 are correct.
11.3.9 Switching from local to remote control

Bays can be controlled locally using the keys on the local control panel or remotely through the
communication interface (Telecontrol BUS or operator interface).
The control point – Local or Remote – is selected either by means of the L/R key on the local
control panel or via appropriately configured binary signal input. If binary signal input has been
configured, then the L/R key has no effect.
Switching from Remote to Local using the L/R key on the local control panel is only possible if the
L/R password has been entered. The selected control point is displayed on the Bay Panel.
11.3.9.1 Local control

Bay to be controlled is selected by pressing the Selection key on the local control panel.
If the bay is to be controlled through binary signal inputs, then the appropriate signal input must be
triggered.
11.3.9.2 Remote control

The switchgear units can be controlled via the communication interface or appropriately
configured binary signal inputs.
C264/EN UM/E50.5 1127

11.3.10 Protection Commissioning Test environment
11.3.10.1 Injection test sets

All the commissioning tests of the MiCOM C264P are carried out by injecting currents and
voltages to the secondary of the earth and/or phases CTs and VTs using appropriate injection test
sets provided for this purpose.
The test of directional protection within MiCOM C264P requires at least one phase current, phase
to phase and residual voltage injection.
The test equipment must provide tools to change the phase between voltage and current.
For reasons of convenience (weight, spatial requirement, transportation), a single-phased current

injection and single voltage test set is more suitable for commissioning and is able to perform all
commissioning tests regarding overcurrent directional/non directional protection of
MiCOM C264P.
Thus, the following descriptions indicate how to conduct the commissioning tests with a single-
phase injection test set.
However, for certain commissioning tests, the three-phase wiring diagrams are easier to
understand and in this case the description is also given in three-phase format.
Single-phase injection test set

• 1 current (0 to 50 A), timer (precision 1 ms)
• 1 voltage (30 to 130V), timer (precision 1 ms)
Three-phase injection test set

• 3 currents (0 to 50 A), timer (precision 1 ms)
• 3 voltage (30 to 130V), timer (precision 1 ms)
Possibility to lag the current respect to voltage injection.
Additional commissioning test equipment

• 1 multimeter (precision 1%)
• 1 connecting terminal to measure the currents exceeding 10 A (precision 2%)
Test plugs and wires to carry out injections to the CT's secondary (dimension according to the
currents injected).
11.3.10.2 Protection Commissioning test sheets

Commissioning test sheets are available in the chapter "Record Sheet" on page 1141.
The presentation of the Commissioning test sheets follows the description of the tests of this
chapter.
The contents of these Protection Commissioning test sheets enable you to log:
1128 C264/EN UM/E50.5

• The characteristics of the MiCOM C264P for the protection features
• The various settings
• The results of the protection checks
• The result of the test records after commissioning.
11.3.10.3 Use of a Core Balance CT for earth faults

If a core balance CT is used to detect earth faults, prior to any test, the user must check the
following points:
• MV or HV cable screens and core CT
• No current flow through the MV or HV cables
• Orientation of the core CT (P1-S1, P2-S2)
11.3.10.3.1 Cable shields and core CT

When mounting a core balance CT around electric cables, check the connection to the earth of
the cable shields and verify that the earth cable of the shield moves in the opposite direction
through the core CT. This cancels the currents carried by the cable shields through the core CT.
- Figure 672 - Cable shields and core CT
11.3.10.3.2 Core CT polarity

Check the polarity of the core CT by following the figure below:
Momentarily connect the battery + to P1 and – to P2. The center zero ammeter connected with +
to S1 and – to S2 will deflect in the positive direction if the wiring is correct.
The phase CT may be tested using the same method.
C264/EN UM/E50.5 1129

- Figure 673 - Core CT polarity
NOTE: Demagnetize the CT after polarity test. Inject an ac current starting from zero and
increase to slowly exceed the CT nominal value and then decrease slowly to zero.
11.3.10.3.3 Protection parameters check

The MiCOM C264P protection parameters checks must ensure that all MiCOM C264P
parameters have been correctly applied to the MiCOM C264P for the specific application.
Transfer the Protection parameters file to the MiCOM C264P using a laptop PC running the
appropriate software (MiCOM S1 - PACiS) via the Ethernet port.
Note: The EPAS-SCE settings are consider to be correctly download and compliant with the
application including the different DIs, Dos and AIs assignment.
The commissioning checks are as follows:
1. Protection parameters verify and delivery to customer
2. Validation of the measurements
3. Validation of the thresholds and associated timers.
11.3.10.3.4 Settings
Log the Protection parameters on the commissioning test sheets.
The MiCOM C264P measures phase and earth currents, phase (phase to phase) voltage, zero
sequence voltage as a True RMS value up to the 15th harmonics. The value(s) indicated take
account of the phase and/or earth CT ratio and VT ratio.
11.3.10.3.6 MiCOM C264P procedure

• Note the select phase and earth CTs ratio, phase voltage VTs ratio and neutral voltage VTs
ratio as configured in the EPAS-SCE and MiCOM S1 - PACiS files
• Energize the MiCOM C264P device.
• Apply current to TMU210 inputs terminals 15-16 and verify the IA value shown on the LCD or
on the CAT.
1130 C264/EN UM/E50.5

• Apply current to TMU210 inputs terminals 11-12 and verify the IB value shown on the LCD or
on the CAT.
• Apply current to TMU210 inputs terminals 7-8 and verify the IC value shown on the LCD or on
the CAT.
• Apply current to TMU210 inputs terminals 3-4 and verify the IN value shown on the LCD or on
the CAT.
• Apply voltage to TMU210 inputs terminals 21-22 and verify the VA value shown on the LCD or
on the CAT.
• Apply voltage to TMU210 inputs terminals 23-24 and verify the VB value shown on the LCD or
on the CAT.
• Apply voltage to TMU210 inputs terminals 25-26 and verify the VC value shown on the LCD or
on the CAT.
• Apply voltage to TMU210 inputs terminals 27-28 and verify the VN or VBB value shown on the
LCD or on the CAT.
Log the results to the Commissioning test sheets (Applied values and MiCOM C264P values
displayed).
11.3.10.4 Thresholds validation

This test type demonstrates that the MiCOM C264P is operating correctly at the application
specific protection parameters.
11.3.10.4.1 MiCOM C264P protection parameters

Set the following parameters for the MiCOM C264P
Applying the voltage and current to terminals as in wiring diagrams in chapter "Hardware" on page
393.
The applied current and voltage must be great than setting value.
11.3.10.4.2 MiCOM C264P Overcurrent parameters
Parameter Value
General Options
2Vpp+Vr
Transfo. Ratio
Line CT primary 1A
Line CT Sec 1A
E/Gnd CT primary 1A
E/Gnd CT Sec 1A
Line VT primary 0.100 kV
Line VT Sec 100.0 V
E/Gnd VT primary 0.100 kV
C264/EN UM/E50.5 1131

Parameter Value
E/Gnd VT Sec 100.0 V
Protection Menu G1
I> Yes
I> VALUE 1 In
tI> DT or IDMT or RI
tI> (if DT) 10 s
Curve (if IDMT) IEC VI or IEEE VI
TMS value (if IDMT) 1
K value (if RI) 1
U> OR
U> VALUE 20V
tU> 10 s
U< OR
U< VALUE 20V
tU< 10 s
Ie> Yes
Ie> VALUE 1 In
tIe> DT or IDMT or RI
tIe> (if DT) 20 s
Curve (if IDMT) IEC VI or IEEE VI
TMS value (if IDMT)1 K value (if RI)=1
Un> 10 V
tUn> 10 s
Automation Menu
TRIP tI> YES
TRIP tU> YES
TRIP tIe> YES
TRIP Un> YES
11.3.10.4.2.1 Phase overcurrent I> threshold test
After the setting is completed connect the MiCOM C264P using the wiring diagram in chapter
"Hardware" on page 393.
Phase overcurrent threshold check

• If the time delay tI> is short, gradually increase the injection current up to the value of the I>
threshold.
1132 C264/EN UM/E50.5

• If the time delay tI> is long, inject 0.95 x I threshold and check that there is no tripping. Then
inject 1,1 x I threshold and check the trip.
• Gradually decrease the injected current and record the value of the drop out off
(I> threshold).
Checks
• Alarm message on the LCD display. (if configured).
• Alarm LED flashes. (if configured).
• Trip LED on(if configured).
• I> threshold LED on (if configured).
• Trip output closes(if configured).
• I> threshold output closes (if configured).
Delay type: Definite time tI>

• Apply a current into one of the phases and measure the time delay tI> by pre-setting the
current above the I> threshold (I injected > 2 x I threshold).
• Apply a current onto one of the phases and measure the time delay tI> by pre-setting the
current above the I> threshold (I injected > 10 x I threshold).
Checks
• Alarm message on the LCD display for I> after that the setting trip delay time is expired (if
configured)..
• Alarm LED flashes > after that the setting trip delay time is expired (if configured)..
• Trip LED on after that the setting trip delay time is expired(if configured)..
• I> threshold LED on (if configured).> after that the setting trip delay time is expired.
• Trip output closes > after that the setting trip delay time is expired (if configured)..
• I> threshold output closes (if configured).> after that the setting trip delay time is expired.
Delay type: Inverse time (IDMT)
Used threshold for this test:

• I>, tI>
• Supply the MiCOM C264P, inject a current equal to 2 x I> threshold into one of the earth
current inputs. Repeat the operation for various current values (n x Ie threshold with n ranging
from 4 to 10, for example). Check that the values measured correspond to those indicated in
the table below (for TMS=1).
IEC curves
Type of curve Tripping time (in seconds) for TMS =1

IEC 2 x I threshold 10 x I threshold
Nominal Min - Max Nominal Min - Max
STI 1.78 1.62 - 1.98 0.5 0.45 - 0.55
C264/EN UM/E50.5 1133


SI 10.1 9.1 - 11.1 3 2.7 - 3.3
VI 13.5 12.2 - 14.9 1.5 1.35 - 1.65
EI 26.7 24 - 29.5 0.8 0.72 - 0.88
LTI 120 108 - 132 13.3 12 - 14.6
IEEE/ANSI curves

IEEE/ANSI 2 x I threshold 10 x I threshold
STI 0.25 0.22 - 0.28 0.08 0.07- 0.09
MI 3.8 3.4 - 4.2 1.2 1.08 - 1.32
I 2.2 1.9 - 2.4 0.3 0.27 - 0.33
VI 7.2 6.5 - 8 0.7 0.63 - 0.77
EI 9.5 8.5 - 10.5 0.4 0.36 - 0.44
RI electromechanical curve
Type of curve Tripping time (in seconds) for K =1

Electromechanical 2 x I threshold 10 x I threshold
RI 4.5 4-5 3.2 2.8 - 3.6
For other injected current values, compare the values found with the theoretical values calculated
according to the formula of the curves.
NOTE: Equations of IEC, IEEE/ANSI and RI curves are given in chapter "Technical Data" on
page 75.
Checks
• I> Alarm message on the LCD display (if configured).
• Alarm LED flashes (if configured).
• Trip LED on (if configured).
• I> threshold LED on (if configured).
• Trip output closes (if configured).
• I> threshold output closes (if configured).
1134 C264/EN UM/E50.5

11.3.10.4.2.2 Phase to phase (phase to neutral) over-voltage U> threshold test
After the setting is completed connect the MiCOM C264P using the wiring diagram in chapter
"Hardware" on page 393.
Phase overcurrent threshold check

• If tU> time delay is short, gradually raise the injection voltage up to the value of U> threshold.
• If U> time delay is long, inject 0.95 x U> threshold setting and check there is no trip. Then
inject 1.1 x U> threshold setting and check the trip output is close.
• Gradually lower the injected current and note the value of the drop out U> threshold.
Checks
• Alarm message on the LCD display for U> after that the setting trip delay time is expired (if
configured).
• Alarm LED flashes (if configured). after that the setting trip delay time is expired.
• Trip LED on, after that the setting trip delay time is expired (if configured).
• U> threshold LED on (if configured) > after that the setting trip delay time is expired.
• Trip output closes U> after that the setting trip delay time is expired (if configured).
• U> threshold output closes (if configured) after that the setting trip delay time is expired.
11.3.10.4.2.3 Earth fault overcurrent and residual over voltage test.
Delay type: Definite time
Used thresholds for this test:

• Ie>, tIe>, Un >, tUn>.
Test
• Supply the C264P, inject current and voltage with magnitude greater then Ie> and Un> setting
value.
• If the time delay tIe> is short, gradually increases injection current up to the value of the Ie>
threshold.
• If the time delay tIe> is long, inject 0.95 x I threshold and check that there is no tripping. Then
inject 1,1 x Ie threshold and check the trip.
• Gradually decreases the injected current and record the value of the drop out Ie> threshold.
• The same procedure above for Un>.
Checks
• Alarm message on the LCD display (if configured).
• Ie>, Un> threshold LED on (if configured).).
C264/EN UM/E50.5 1135

• Ie>, Un> threshold output closes (if configured).
Delay type: Inverse time (IDMT)
Used thresholds for this test:

• Ie>, tIe>
Test
• Supply the C264P inject a current equal to 2 x Ie> threshold into one of the earth current
inputs. Repeat the operation for various current values (n x Ie threshold with n ranging from 4
to 10, for example). Check that the values measured correspond to those indicated in the
table below (for TMS=1).
IEC curves

STI 1.78 1.62 - 1.98 0.5 0.45 - 0.55
SI 10.1 9.1 - 11.1 3 2.7 - 3.3
VI 13.5 12.2 - 14.9 1.5 1.35 - 1.65
EI 26.7 24 - 29.5 0.8 0.72 - 0.88
LTI 120 108 - 132 13.3 12 - 14.6
IEEE/ANSI curves

IEEE/ANSI 2 x I threshold 10 x I threshold
STI 0.25 0.22 - 0.28 0.08 0.07- 0.09
MI 3.8 3.4 - 4.2 1.2 1.08 - 1.32
I 2.2 1.9 - 2.4 0.3 0.27 - 0.33
VI 7.2 6.5 - 8 0.7 0.63 - 0.77
EI 9.5 8.5 - 10.5 0.4 0.36 - 0.44
Checks
• Ie> Alarm message on the LCD display (if configured).
• Ie> threshold LED on (if configured).
• Ie> threshold output closes (if configured).
1136 C264/EN UM/E50.5

11.3.10.4.3 MiCOM C264P frequency parameters
Parameter Value
General Options
3Vpp+Vr
Transfo. Ratio
Line VT primary 0.100 kV
Line VT Sec 100.0 V
E/Gnd VT primary 0.100 kV
E/Gnd VT Sec 100.0 V
Protection Menu G1
- [81] f1? MIN
- f1 VALUE 49Hz
- tf1 1s
- [81] f2? MAX
- f2 VALUE 51 Hz
- tf2 1s
- df/dt1? ON
- df/dt1 VALUE +0.5 Hz/s
- t df/dt1 1s
- df/dt1 Id 1A
- df/dt2? ON
- df/dt2 VALUE -0.5 Hz/s
- t df/dt2 1s
- df/dt2 Id 1A
Automation Menu
TRIP f1 YES
TRIP f2 YES
TRIP df/dt1 YES
TRIP df/dt2 YES
11.3.10.4.3.1 Over and Underfrequency test
Values to be measured
• stages (f1) and (f2)
• time delay (tf1) and (tf2)
Stage (f1) check
C264/EN UM/E50.5 1137

1. Gradually increase the frequency from the nominal frequency fn to the value of the stage
(f1): tripping should occur for a frequency in the range
[(f1) – 10mHz, (f1) + 10mHz].
2. Adjust the frequency to [(f1) – 50mHz] and check that tripping does not occur. Increase the
frequency to 1.2x(f1) and check that tripping occurs.
3. Gradually reduce the frequency and measure the value of the drop-off stage (f1): the
function must reset for a frequency less than or equal to [(f1) – 50mHz].
Stage (f2) check
1. Gradually decrease the frequency from the nominal frequency fn to the value of the stage
(f2): tripping should occur for a frequency in the range [(f2) – 10mHz, (f2) + 10mHz].
2. Adjust the frequency to [(f2) + 50mHz] and check that tripping does not occur. Increase the
frequency to 0.8x(f2) and check that tripping occurs.
3. Gradually increase the frequency and measure the value of the drop-off stage (f2): the
function must reset for a frequency less than or equal to [(f2) + 50mHz].
Checks
• f1 & f2 Alarm messages on the LCD display (if configured).
• f1 & f2 thresholds LED on (if configured).
• f1 & f2 threshold outputs close (if configured).
11.3.10.4.3.2 Rate of change of frequency test
Values to be measured
1. Stages (df/dt1) and (df/dt2)
Time delay (t df/dt1) and (t df/dt2)
Stage (df/dt1) check
1. Gradually increase the frequency from the nominal frequency from 50 Hz to 51 Hz with a
variation of 1 mHz every 1 ms and check for the tripping and information.
Stage (df/dt2) check
1. Gradually decrease the frequency from the nominal frequency from 50 Hz to 49 Hz with a
variation of 1 mHz every 1 ms and check for the tripping and information.
Checks
• df/dt1 & df/dt2 Alarm messages on the LCD display (if configured).
• df/dt1 & df/dt2 thresholds LED on (if configured).
1138 C264/EN UM/E50.5

• df/dt1 & df/dt2 threshold outputs close (if configured).
C264/EN UM/E50.5 1139

11.4 Commissioning Tests with GHU21x (without LCD)

After the MiCOM C264 has been installed and connected as described in chapter "Installation" on
page 931, the commissioning procedure can begin.
Before turning on the power supply voltage, the following items must be checked:
• Is the device connected to the protective ground at the specified location?
• Does the nominal (and measured) voltage of the battery agree with the nominal auxiliary
voltage of the device?
• Are the current and voltage transformer (if used) connections, grounding, and phase
sequences correct?
After the wiring work is completed, check the system to make sure it is properly isolated.
Once all checks have been made, the power supply voltage may be turned on.
After the voltage has been applied, the MiCOM C264 starts up.
During start-up, various tests are carried out (see section entitled ‘Diagnose level1’ in chapter
"Maintenance" on page 1144.
The LED indicator labelled ‘HEALTHY’ (Fourth LED) will light up.
After approximately 30 s, the MiCOM C264 is ready for operation.
After the settings have been made, it is necessary to check that the software and the database
versions are compatible with the hardware.
The following chapters describe the checks to be performed with Computer Administration Tool
software (CAT) software to answer these questions and ensure that the MiCOM C264 is fully
operational in its application.
CAT is fully described in chapter "Installation" on page 931.
With CAT, the “Computer version” button gives access to the current MiCOM C264 software
version, the active database and the computer operational mode.
For a normal behavior, the computer mode is “ACTIVE”
1140 C264/EN UM/E50.5

MiCOM C264 - User Manual 12 Record Sheet
12 Record Sheet
12.1 Commissioning Record 1142

12.2 Maintenance Record Sheet 1143
C264/EN UM/E50.5 1141

12 Record Sheet MiCOM C264 - User Manual
12.1 Commissioning Record

Commissioning Date:
Engineer:
Station Name:
Circuit Name:
Front Plate Information
Under the top access cover, there is the following type of label:
Fill in the following array according to the label under the top access cover:
Serial number
Cortec number
Auxiliary voltage for power supply
Nominal wetting voltage for digital
inputs
*Delete as appropriate
Have all relevant safety instructions been followed? Yes/No*
Product checks
Visual inspection with the computer de-energized
Relay damaged? Yes/No*

Rating information correct for installation? Yes/No*
Case earth installed? Yes/No*
1142 C264/EN UM/E50.5

MiCOM C264 - User Manual 12 Record Sheet
12.2 Maintenance Record Sheet

Product Serial number
Previous
Slot letter in the New board
board
DATE Engineer Board type rack (between A and Serial
Q) Serial
number
number
C264/EN UM/E50.5 1143

13 Maintenance MiCOM C264 - User Manual
13 Maintenance
13.1 Responsibilities 1145

13.2 Standard Maintenance Operation 1146
13.2.1 Level 1 diagnosis facilities 1146
13.2.1.1 Front panel LED indications 1146
13.2.1.2 Front panel LCD indications 1149
13.2.1.3 Adjustment of the brightness of the front panel LCD 1149
13.2.2 Maintenance period 1150
13.2.3 Method of repair 1150
13.2.3.1 Replacing and installing a complete MiCOM C264 1150
13.2.3.2 Replacing a board 1152
13.2.3.2.1 Replacement of the Binary Input Unit (BIU241/261) 1155
13.2.3.2.2 Replacement of the main processor board (CPU2xx) 1155
13.2.3.2.3 Replacement of the Ethernet switch boards (SWU20x or SWR20x) 1155
13.2.3.2.4 Replacement of the I/O boards (DIU200, DIU211, DOU201, CCU200,
CCU211, AIU210, AIU211, AOU200 ) 1155
13.2.3.2.5 Replacement of the Transducerless Measurements Unit (TMU) 1156
13.2.3.2.6 Refit the MiCOM C264 1156
13.3 Cleaning 1157
13.4 Engineering Maintenance Operation 1158
1144 C264/EN UM/E50.5

MiCOM C264 - User Manual 13 Maintenance
13.1 Responsibilities
Most maintenance activities involve a power supply that can damage the installation or cause
injury to the operator. The chapter "Safety and Handling" on page 55 and the other chapters
involved in maintenance should be read carefully before any handling.
Before starting maintenance, the contractual and human responsibilities should be clearly
defined.
Only qualified and competent persons should carry out maintenance.
C264/EN UM/E50.5 1145

13.2 Standard Maintenance Operation

13.2.1 Level 1 diagnosis facilities
When maintenance action is planned, the operator should prepare, act and report.
The minimal preparation is to get the commissioning Record Sheet (refer to"Record Sheet" on
page 1141) of installed MiCOM C264 in order to see the product configuration and its history. The
User should refer also to his own experience besides this manual. It is also recommended to
extract the logbook history in order to be informed of the intervention conditions.
At a first level the product provides several methods to check the context of the fault. The main
ones are:
• LEDs
• LCD (Liquid Crystal Display)
13.2.1.1 Front panel LED indications

Refer to topic "The Front Panel" on page 500 for the precise LED description.
- Figure 674 - MiCOM C264 front panel GHU20x
On a main rack, the first 5 LEDs indicate the MiCOM C264 status information. LEDs indicate from
top to down:
1146 C264/EN UM/E50.5

LED id - Color LED status Meaning

Off No fault
There is at least one major fault (hardware,
On
database) (1)
1 - Red
There is at least one minor fault (I/O board,
Slow blinking
communication to IEDs) (2)
Fast blinking Not used
Off No alarm
All the alarms are ac-knowledged, but there is
On
at least one alarm still active. (3)
2 - Yellow All alarms displayed in the alarm panel are
Slow blinking
inactive and acknowledged
There is at least 1 not acknowledged alarm
Fast blinking
displayed in the alarm panel
Off Computer in reboot
On Computer in operation
3 - Yellow
Slow blinking Computer in maintenance
Fast blinking Computer in test
Off Power off
On Power on
4 - Green
Slow blinking Not used
All bays managed by the computer are in
Off
REMOTE
All bays managed by the computer are in
On
5 - Red (4) LOCAL mode
Bays managed by the computer are not in the
Slow blinking
same control mode
Off No fault
On Global fault (5)
6 - Red
Slow blinking Not used
(1) Major fault: MiCOM C264 not available due to internal failure (database error, CPU board
failure, …).
(2) A minor fault is a fault causing only the non-availability of a part of the functionality.
(3) When the alarm disappears, the LED returns automatically to OFF.
C264/EN UM/E50.5 1147

(4) Assigned by computer only for without LCD panel: GHU2x1 or for an extension
MiCOM C264
(5) It may be a board fault, an IED fault, a power off, a watchdog issue (DO#0 of BIU board), an
IED or extension disconnected
A minor fault is a fault causing only the non-availability of a part of the functionality:
Symptom LED status Possible reason Way to solve

Verify the connection
Functions as commu- between CPU or
The cable between
nication, automation, GHU2xx. If connection
CPU and GHU2xx, or
printing are well ope- All LEDs are OFF is OK and the problem
GHU2xx itself is not
rating & the watchdog is not already solved
operational
on BIU is SET then change the
GHU2xx board.
The supply is ON and LED6 is ON (but LED7
Problem with BIU Replace BIU board or
the watch dog on BIU thru 13 are OFF if
board or CPU board CPU board.
is RESET. predefined)
Download a coherent
LED1 ON Incoherent database
MiCOM C264 is not database
running or not fully Go in Fault display
operational At least one prede-
and Board display to
fined LED among Hardware fault
determine the faulty
LED7 thru 13 is ON
board and change it.
1148 C264/EN UM/E50.5

Symptom LED status Possible reason Way to solve

Go into IED display to
determine the
disconnected IED and
verify the cable, the
An IED is BIU configuration, the
disconnected (LED 6 communication
and/or 12 ON) parameters inside the
EPAS-SCE database,
the communication
parameters inside the
relay.
Go into Fault display
and verify that paper is
MiCOM C264 is not The printer is
LED1 is blinking available, the printer is
fully operational disconnected
switch ON, the printer
cable
Go into Fault display &
verify that the external
clock is switch ON, the
A problem about clock external clock is
synchronisation connected to the
antenna, the external
clock is connected to
the MiCOM C264.
Go into Fault display &
connect
theISaGRAF®
A problem about PLC
workbench to the
(ISaGRAF®)
MiCOM C264. Verify
the behavior of the
PLC.
13.2.1.2 Front panel LCD indications

GHU200, GHU210 or GHU220 board gives access to the status of the boards, the state of digital
inputs, the state of digital outputs, the connection state with external devices. Refer to chapter
"Commissioning" on page 1119 and "Human Machine Interface" on page 498 for more details.
13.2.1.3 Adjustment of the brightness of the front panel LCD
When button and button are pressed simultaneously it is possible to increase (resp.
decrease) the brightness of the front panel LCD by pressing button (resp. button )
C264/EN UM/E50.5 1149

13.2.2 Maintenance period

It is recommended that Schneider Electric products receive periodic monitoring after their
installation. Deterioration may occur over time. Because of the electrical and disturbed
environment, it is recommended to confirm at regular intervals that the MiCOM C264 is operating
correctly.
MiCOM C264 has been designed for a life cycle of over 15 years.
MiCOM C264 is self-supervising and therefore requires less maintenance than previous products.
Most problems will lead to an alarm so fast and appropriate action can be done. However, some
periodic tests should be done to ensure MiCOM C264 is operating correctly and that the external
wiring in a good condition.
If a Preventative Maintenance Policy exists within the customer’s organization then the
recommended product checks should be included in the regular program. Maintenance periods
depend on many factors, such as:
• the operating environment,
• the accessibility of the site,
• the amount of available manpower,
• the importance of the installation in the power system,
• the consequences of failure.
13.2.3 Method of repair

If the MiCOM C264 should develop a fault whilst in service, depending on the nature of the fault,
the watchdog contacts will change state and an alarm condition will be flagged. Due to the
extensive use of surface-mount components (SMC) faulty boards should be replaced, as it is not
possible to perform repairs on damaged circuits with SMC technology. Thus, either the
completeMiCOM C264 or just the faulty board, identified by the in-built diagnostic software, can
be replaced.
The preferred method is to replace the complete MiCOM C264 as it ensures that the internal
circuitry is protected against electrostatic discharge and physical damage at all times and
overcomes the risk of incoherency with the new boards. In some cases, it may be difficult to
remove an installed MiCOM C264 due to limited access in the back of the cubicle and rigidity of
the scheme wiring then only the faulty elements will be replaced.
Replacing boards can reduce transport costs but requires clean, dry on-site conditions and higher
skills from the person performing the repair. If an unauthorized service center performs the repair,
the warranty will be invalidated.
13.2.3.1 Replacing and installing a complete MiCOM C264

The case and rear terminal blocks have been designed to facilitate removal of a complete
MiCOM C264.
Before working at the rear of a MiCOM C264, isolate all the voltages and currents connected to it.
NOTE: MiCOM C264 has current transformer shorting switches which close when terminal block
is removed.
1150 C264/EN UM/E50.5

Before any disconnection, check the labels correctly define the connectors and match with the
wishing description you have. Otherwise, note the current wiring in order to prepare the new
MiCOM C264 installation.
The general procedure to remove a MiCOM C264is as follows:
1. Disconnect the power supply connector,
2. Disconect theMiCOM C264 IRIG-B, fibre optic, Ethernet RJ45 and serial links connected on
CPU board,
3. Disconnect the input/output connectors,
4. Disconnect earth connection:
There are two types of terminal block used on the MiCOM C264:
- Figure 675 - Location of securing screws for terminal blocks
NOTE: The use of a magnetic bladed screwdriver is recommended to minimise the risk of
the screws being left in the terminal block or lost. A 3 mm flat head screwdriver is
recommended for fixation screws. A 6 mm flat head screwdriver is recommended for
CT/VT earthing connections.
Without exerting excessive force or damaging the scheme wiring, pull the terminal blocks
away from their internal connectors.
Remove the screws used to fasten the MiCOM C264to the panel, rack, etc. These are the
screws with the larger diameter cross heads that are accessible when the access covers are
fitted and open.
C264/EN UM/E50.5 1151

CAUTION
HAZARD OF FALLING FRONT PANEL
If the top and bottom access covers have been removed, do not remove the screws with
the smaller diameter heads which are accessible. These screws hold the front panel on
the MiCOM C264.
Failure to follow these instructions can result in injury or equipment damage.
5. Withdraw the MiCOM C264 from the panel or rack carefully and take care of its weight
because there are some heavy parts due to the internal transformers.
CAUTION
HAZARD OF FALLING DEVICE
Take care of the weight of the device during manipulation.
To reinstall the repaired or new MiCOM C264, follow the above procedure in reverse. Ensure that
each terminal block is relocated in the correct position and the case correctly earthed, IRIG-B and
optical fiber connections are put back in place.
Once re-installation is complete the MiCOM C264 should be commissioned again using the
instructions in chapter "Commissioning" on page 1119.
13.2.3.2 Replacing a board

To replace a MiCOM C264 board remove the front panel.
Before removing the front panel, the auxiliary supply must be switched off. It is also strongly
recommended that the voltage and current transformer connections and trip circuit are isolated.
Open the top and bottom access covers. With size 80TE cases the access covers have two
hinge-assistance T-pieces which clear the front panel molding when the access covers are
opened by more than 120°, thus allowing their removal. If fitted, remove the transparent
secondary front cover
By applying outward pressure to the middle of the access covers, they can be bowed sufficiently
so as to disengage the hinge lug allowing the access cover to be removed. The screws that fasten
the front panel to the case are now accessible.
The size 40TE case has four cross head screws fastening the front panel to the case, one in each
corner, in recessed holes. The size 60TE and 80TE case have an additional two screws, one
midway along each of the top and bottom edges of the front plate. Undo and remove the screws.
1152 C264/EN UM/E50.5

CAUTION
HAZARD OF FALLING DEVICE
Do not remove the screws with the larger diameter heads which are accessible when the
access covers are fitted and open. These screws hold the MiCOM C264 in its mounting (panel
or cubicle).
When the screws have been removed, the complete front panel can be pulled forward and
separated from the metal case.
NOTICE
RISK OF EQUIPMENT DAMAGE
Caution should be observed at this stage because a cable connects the front panel to the rest
of the device circuitry.
Additionally, from here on, the internal circuitry of the MiCOM C264 is exposed and not protected
against electrostatic discharges (ESD), dust ingress, etc. Therefore ESD precautions and clean
working conditions should be maintained at all times.
NOTICE
When the internal circuitry of the MiCOM C264 is exposed and not protected against
electrostatic discharges (ESD), dust ingress, etc. ESD precautions and clean working
conditions should be maintained at all times.
- Figure 676 - sample of MiCOM C264 40TE with TMU2xx board
C264/EN UM/E50.5 1153

- Figure 677 - sample of MiCOM C264 40TE without TMU2xx board
- Figure 678 - sample of MiCOM C264 80TE with TMU2xx board
- Figure 679 - sample of MiCOM C264 80TE without TMU2xx board
The boards within theMiCOM C264 are now accessible. Figures above show the board locations
for theMiCOM C264 in size 40TE and size 80TE with or without TMU2xx boards.
Looking to the front of the MiCOM C264 with the front panel off, you can have access to a printed
circuit that connects all the boards together: this is the back-plane board.
To remove a board, you need to:

• Pull the back-plane board (FBP28x for MiCOM C264 80TE, FBP24x for MiCOM C264 40TE
or FBP26x for MiCOM C264 60TE) out by holding it by the two extremities.
• Remove the screws and the maintain bar at the bottom of the case.
1154 C264/EN UM/E50.5

NOTICE
RISK OF EQUIPMENT MALFUNCTION
To ensure compatibility, always replace a faulty board with one of an identical part number and
set jumpers in identical position.
Failure to follow these instructions could result in equipment malfunction.
Boards and rack styles are described in chapter "Hardware" on page 393.
13.2.3.2.1 Replacement of the Binary Input Unit (BIU241/261)

The BIU is the power supply board located on the extreme left-hand side (slot A) of FBP2xx for
MiCOM C264.
Pull the power supply module forward, away from the rear terminal blocks and out of the case. A
reasonable amount of force will be required to achieve this due to the friction between the
contacts of the two medium duty terminal blocks. It is then recommended to use the special tool
for extracting board (internal reference is 2070860).
Do not forget to set the jumpers on the new board in the same position as the previous one.
13.2.3.2.2 Replacement of the main processor board (CPU2xx)

Depending on the model of the MiCOM C264 the processor board carried out the IRIG-B
functionality’s so if you identify an IRIG-B connection problem you will have to replace the
processor board.
After replacement of the main processor board, all the settings required for the application will
need to be re-entered.
The CPU board is located next to the BIU board (slot B).
Do not forget to disconnect the rear cables (RJ45 Ethernet, optical fibers, IRIG-B connector and
serial links) before replacing the board and to reconnect them after.
13.2.3.2.3 Replacement of the Ethernet switch boards (SWU20x or SWR20x)

The Ethernet switch board is located on slot C.
Do not forget to disconnect the rear cables (RJ45 Ethernet and optical fibers) before replacing the
board and to reconnect them after.
13.2.3.2.4 Replacement of the I/O boards (DIU200, DIU211, DOU201, CCU200, CCU211,
AIU210, AIU211, AOU200 )
The I/O boards can be located in any slot from C to Q.
C264/EN UM/E50.5 1155

CAUTION
HAZARD OF FIRE, DAMAGE TO ELECTRONICS OR MALFUNCTION
The insert or extraction of the AOU200 board in skew could lead one capacity (C27) to touch
an iron corner. The manipulation of boards is to be done carefully.
13.2.3.2.5 Replacement of the Transducerless Measurements Unit (TMU)

The measurement unit is on the extreme right-hand side of MiCOM C264.
13.2.3.2.6 Refit the MiCOM C264

Before re-assembling the module with a replacement board, make sure that the address for the
replacement board is the same address that the board replaced by checking the jumpers on the
boards.
Refit the FBP board.
Screw the bar in the bottom of the case.
Refit the front panel. After refitting and closing the access covers, press at the location of the
hinge-assistance T-pieces so that they click back into the front panel molding.
Once the relay has been reassembled after repair, it must be commissioned again (see chapter
"Commissioning" on page 1119).
1156 C264/EN UM/E50.5

13.3 Cleaning
Before cleaning the MiCOM C264 ensure that all ac/dc supplies, current transformer and voltage
transformer connections are isolated to prevent any chance of an electric shock whilst cleaning.
Front panel cleaning: use a smooth cloth. Do not use abrasive material or detergent chemicals.
C264/EN UM/E50.5 1157

13.4 Engineering Maintenance Operation

The Computer Administration Tool software (CAT) is able to:
• Upgrade the MiCOM C264 firmware,
• Upload and switch the databases to MiCOM C264,
• Upload setting file produced by MiCOM S1 - PACiS software to MiCOM C264,
• Download setting file from MiCOM C264.
These functions are needed for customizing the MiCOM C264.
For details on the CAT, refer to chapter "Installation" on page 931.
For details on the MiCOM S1 - PACiS, refer to the MiCOM S1 - PACiS user manual.
An Expert Maintenance involves the use of Hyperterminal; it is out of the scope of this
documentation.
1158 C264/EN UM/E50.5

MiCOM C264 - User Manual 14 Cyber Security
14 Cyber Security
14.1 Documentation Reference 1160

14.2 Cybersecurity Policy 1161
14.2.1 Applicability 1161
14.2.2 Banner 1161
14.2.3 Password 1162
14.2.3.1 NERC CIP compliance for MiCOM C264 1163
14.2.3.2 Privileges and Default password 1163
14.2.3.3 Security Policy 1163
14.2.4 Security Logs 1164
14.2.5 Hardening 1165
14.2.6 Reset to Factory 1165
14.2.7 Patch Management 1166
14.2.8 Authentication Configuration for RADIUS Client/Server 1166
14.2.9 Authentication Certificate for MiCOM C264 1170
14.2.10 Firmware Signature for MiCOM C264 1170
14.2.10.1 LOG (alarm) 1170
14.2.10.2 HMI (alarm) 1171
14.2.10.3 LED (alarm) 1171
14.2.10.4 Datapoint (alarm) 1171
C264/EN UM/E50.5 1159

14 Cyber Security MiCOM C264 - User Manual
14.1 Documentation Reference

Document Title
EPAS System Cyber Security (SCS) User

EPAS CS-SCS_EN_E50
Guide
EPAS HARDENING_EN_AN_E50 EPAS HARDENING Application Note
CAE_EN_UG_2.0.0_A Cybersecurity Admin Expert (CAE) User Guide
1160 C264/EN UM/E50.5

14.2 Cybersecurity Policy

The minimum Cyber Security policy includes:
• Disclaimer and banner
• RBAC policy
• Device hardening (unused ports)
• Security logs
General Cyber Security good practices
Schneider Electric strongly recommends:

• to install the device in a locked cubicle to reduce the cyber security risk and
• to implement badge restriction based on roles to enter the substation or to open the panel
containing the device.
Cyber Security good practices applied to communication protocols
The Modbus, DNP3, IEC 61850, IEC 60870-101 , IEC 60870-104, IEC 60870-103, OPC-UA
protocols are unsecure.
The MiCOM C264 devices in the system that support these protocols do not have the capability to
transmit data encrypted using these protocols. If a malicious user gained access to your network,
transmitted information could be disclosed or subject to tampering.
See the System Cyber Security Hardening recommendations on suggested compensating

controls.
14.2.1 Applicability
The main requirements for MiCOM C264 inside the cyber security scope are described on this
table below.
Requirement for MiCOM C264 Title

Banner Banner on Tools MiCOM S1 - PACiS & CAT
Profiles are managed by CAE RBAC
Profiles (password)
Configurator
Profile lockout
Yes
Log off
Unused ports Yes
Security Logs Yes
The DHMI MiCOM C264 banner is an easy-to-read message that plainly identifies the device
where the user is connected / working to prevent him/her from mistaking it for another one.
It is stored in MiCOM C264 or the connected PC.
14.2.2 Banner
The banner is fixed whatever language is selected; it is configurable in EPAS-SCE:
C264/EN UM/E50.5 1161

• It contains at least 32 characters, at most 6 lines and 10 characters by line,
• It can be the start and/or inactivity (screen saver) MiCOM C264 panel to comply with the
NERC standard, or neither.
14.2.3 Password
A password is required to place a command or set a parameter (whether from the front panel or
via a PC-based application). For this purpose, at some point, the user chooses a profile that
depends on the intended activity.
Important
The Schneider Electric password policy is one of the key elements of the Cyber Security Policy.
Here after are listed good practices to improve the Password definition:
• Use common Cyber Security Good Practice for password complexity definition by using
strong passwords.
• Change All Passwords from their default value when taking the device into use and specially
after the first login
• Change Passwords regularly.
• Update password after a certain period of time.
• Use NERC COP 007-05 Compliant password as much as possible.
• Enforce the use of strong and complexes Password containing : Caps characters +
Lowercases characters + Numbers + Special characters.
• Set the minimum password length to 10 characters.
• Disable all Communication ports unused on the device, if possible.
• Do not reuse old passwords.
• All devices installed before January 2020 should be checked separately case by case to
confirm the Cyber Security conformity to Standard/country law.
All user have to be aware of best practice concerning passwords; these include:
• Do not share any personal password.
• Do not display any password during password entry.
• Do not transmit any password in email or by other means.
• Do not save any password on PC’s or other devices.
• Do not write any password on any media.
• Do regular user reminders and trainings about best practices concerning password.
Password is setup from arrows key password for DHMI MiCOM C264:
Arrow
Key
Value 2 4 8 6
length of arrow key password is at least 8.
1162 C264/EN UM/E50.5

Important
If the Arrow Key password is not configured, the alphanumeric password will be used for the front
panel access. In this case, alphanumeric passwords longer than 16 characters are not allowed.
Access without a proper password is denied as soon as the security administrator has defined the
passwords.
NOTE: Please refer to the documentation CAE User Guide on chapter HI for password
configuration.
14.2.3.1 NERC CIP compliance for MiCOM C264

The password must have 8 caracters and in addition contains at least one character from all the
categories that follow:
• Upper case characters (A-Z)
• Lower case characters (a-z)
• Base 10 digits (0-9)
• Non-alphanumeric, that is:
! " # $ % & ' ( ) * + , - .

/ : ; < = > ? @ [ \ ] ^ _ `
NOTE: Please refer to the documentation EPAS System Cyber Security (SCS) User Guide on
chapter FT and section APPENDIX / STANDARDS for details.
14.2.3.2 Privileges and Default password
NOTE: Please refer to the documentation EPAS System Cyber Security (SCS) User Guide on
chapter FT and section RBAC Definition with CAE for overview and the documentation CAE
User Guide on chapter HI for password details.
14.2.3.3 Security Policy

The Security policy is the collection of all the security parameters that apply to the system.
Security policy parameters are setup by Security Administrator operator using the CAE tool.
Default Unit Min Max Possible

Parameters
Value Value Value Value Value
Inactivity automatic
15 Minute 1 99 Number
disconnection timeout
Maximum numbers of
5 - 1 99 Number
errors for password
C264/EN UM/E50.5 1163

Default Unit Min Max Possible

Parameters
Value Value Value Value Value
Password attempts
timer
(Time before the 3 Minute 1 30 Number

attempt counter can
be reset)
Allow user locking Yes - - - Yes / No
Automatic User
Yes - - - Yes / No
Account unlocking
Locking period
240 Second 1 86400 Number
duration
None / IEEE
Password Complexity IEEE 1686 - - - 1686/ NERC
COP 007-05
BDEW /
Security standards IECEE E3
and recommendations /NERC-CIP /
BDEW - - -
to apply to log and IEEE 1686 /
monitoring IEC 62351/
CS_PH1*
Syslog server IP
N/A - - - IP Address
address
SNMP Client IP
N/A - - - IP Address
Address
Inactivity automatic
15 Minute 1 99 Number
disconnection timeout
(*) CS_PH1 is a Schneider Electric Cybersecurity recommendation. See CAE documentation for
the definition of CS_PH1.
14.2.4 Security Logs

Security logs produced by application are archived to a central security server. A Security Logs
viewer allows displaying security logs.
1164 C264/EN UM/E50.5

- Figure 680 - Viewing security logs (sample)
NOTE: For the list of Security Logs produced by MiCOM C264, please refer to documentation
EPAS Hardening Guide on chapter MiCOM C264 Hardening and section C264 Log
Management.
14.2.5 Hardening
NOTE: Please refer to the documentation EPAS HARDENING Application Note for more details
and help to follow hardening procedures for EPAS System recommendations and the
documentation EPAS System Cyber Security (SCS) User Guide on section Device Hardening
for more details.
14.2.6 Reset to Factory

The “Factory mode” is the default configuration (RBAC and security policy) of any IED coming out
of the factory.
A manually operation (reset order) allows to retrieve the factory mode configuration for EPAS
component. This order is available according to role and permissions.
EPAS component Method Back to Factor Mode

MiCOM C264 Operator resets by front panel DHMI MiCOM C264 tree menu
The factory cyber security settings are restored through the DHMI, via the menu tree panel.
This below procedure allows retrieve the MiCOM C264 RBAC factory mode configuration:
Step Action
• Access to the DHMI MiCOM C264 first page: Press thrice”
1 page” key and “Return” key
• The MENU TREE is displayed
C264/EN UM/E50.5 1165

Step Action
• From “MENU TREE”, choose “CONFIG” option and “Return”
button
• From “MENU TREE/CONFIG”, choose “COMPUTER” option
2
and “Return” button
• From “MENU TREE/CONFIG/COMPUTER”, choose “FACT.
CYBER SETTINGS” option and “Return” button
• From “MENU TREE/CONFIG FACT. CYBER SETTINGS”,
3 choose “YES” option and “Return” button to valid the
MiCOM C264 RBAC factory mode configuration
NOTE: The “Factory mode” is accessible by Security Administrator only. Please refer to EPAS
System Cyber Security (SCS) User Guide on section Back to factory Mode for details.
14.2.7 Patch Management

NOTE: Please refer on chapter IN and section C264 Installation for details.
14.2.8 Authentication Configuration for RADIUS Client/Server

In Security Configuration Editor tab > Authentication Configuration tab
This feature allows the security administrator to implement a Local or Centralized authentication
policy for his/her system.
Centralized authentication makes it possible to connect to a trusted authentication server

(RADIUS, SAMBA) to validate the user credentials when connecting to devices.
CAE can be used to configure the:

• Authentication Mode and Common Parameters
To define the authentication mode and general parameters, click the Common tab:
Select the desired settings as detailed below:
1166 C264/EN UM/E50.5

Click OK to save the common parameters.
These parameters will be included in the Security Policies and sent to all the compatible
devices containing a Cyber Security brick from network device list tab.
• RADIUS Client/Server
RADIUS is a protocol used for authenticating and authorizing users. It allows for centralized
authentication, authorization and accounting (AAA) for user and/or network access control.
The RADIUS server is hosted by SAM. Also, Radius client (CS Brick 2.4) interacts with any
third-party RADIUS server (Microsoft NPS (Network policy sever), FreeRadius, etc…).
Any request to login by a user either through the PC configuration software or the front panel
HMI is routed to the main RADIUS server.
If no response is received from the main server, the control will then redirect the request to the
backup server. If no response is received from the backup server, the request will finally be
processed by the local authentication server which may or may not have the same security
credential database as the RADIUS servers.
NOTE: SAM provides only one RADIUS server. But in CAE, it can be defined one main and
one backup RADIUS servers.
C264/EN UM/E50.5 1167

Click RADIUS tab to configure the RADIUS parameters, including:
IP address of the RADIUS server,
Shared secret,
Default role…
Select the desired settings as detailed below:
1168 C264/EN UM/E50.5

Click OK to save the RADIUS settings
The RADIUS parameters will be included in the Security Policies and sent to all the
compatible devices Cyber Security brick from network device list tab.
Push RBAC status summary message appears that Security configuration successfully
updated and Security policies successfully updated.
C264/EN UM/E50.5 1169

SAM, a RADIUS server connected with EPAS RADIUS clients.
For example, Microsoft Network Policy Server as RADIUS server can be connected with
EPAS RADIUS clients.
14.2.9 Authentication Certificate for MiCOM C264

The certificate allows to authenticate the origin and the period of validity of an executable (setup).
Before running the setup program, the user can manually perform a security authentication.
For details, please refer on chapter IN § Note for Authentication Certificate.
14.2.10 Firmware Signature for MiCOM C264

To improve the Cyber Security offer of EPAS according to ANSSI, code signing process of
digitally signing executables and scripts used to confirm the software author and guarantee that
the code has not been altered or corrupted since it was signed.
The firmware signature is a pure software mechanism which can guarantee authenticity and
integrity of a digital content such as a binary file, text (xml) file, media resources (JPEG).
Therefore, VxWorks signature, bootrom files can be verified certificates in the MiCOM C264.
Schneider Electric has developed an alarm management for MiCOM C264 firmware signature
update as the following:
14.2.10.1 LOG (alarm)

Refer to SAM User guide.
1170 C264/EN UM/E50.5

14.2.10.2 HMI (alarm)

Refer Chapter IN/ § D. Update VxWorks BOOTROM of new release, please follow instructions.
14.2.10.3 LED (alarm)

Refer Chapter HI/ § First LEDs.
14.2.10.4 Datapoint (alarm)

Refer Chapter IN/ § Manage events and states (subject to privilege)
C264/EN UM/E50.5 1171

15 Annex MiCOM C264 - User Manual
15 Annex
15.1 Introduction 1176

15.1.1 MiCOM Ethernet Device Series 1176
15.1.2 MiCOM C264Ethernet switch boards 1176
15.1.3 MiCOM Ethernet Redundant REU20x 1176
15.2 Glossary and Definitions 1177
15.3 SWR21x Range – Dual Ring Architecture 1179
15.3.1 Fast redundant ring capability 1179
15.3.1.1 Self healing ring 1179
15.3.1.2 Ethernet switch with Self-healing ring facilities 1179
15.3.1.3 Schneider Electric Ethernet ring redundancy 1180
15.3.1.4 Ethernet system performances 1181
15.3.1.5 Max time of end to end delay 1181
15.3.1.6 Benefits 1182
15.3.2.1 SWR21x - MIB Structure 1182
15.3.3 SWR21x Leds 1184
15.3.4.2 Address of the board 1186
15.3.4.3 How to configure the address ? 1186
15.3.4.4 IP Address of the repeater 1186
15.4 SWD21x Range – Dual Homing Architecture 1188
15.4.1 Dual homing typical architecture 1188
15.4.2 Dual homing Switch Description 1189
15.4.3 Dual homing Features 1189
15.4.3.1 10Base T and 100Base Tx 1189
15.4.5 SWD21x Leds 1190
15.5 SWU20x Range – Star Architecture 1193
1172 C264/EN UM/E50.5

MiCOM C264 - User Manual 15 Annex
15.5.1 Ethernet Port Characteristics 1193

15.5.1.1 10/100BaseTx Port 1193
15.5.1.2 100BaseFx Multi Mode Port 1193
15.5.1.3 100BaseFx Single or Mono Mode Port 1193
15.5.2.2 100Base Fx 1194
15.5.3.2 Buffering 1194
15.5.3.3 Back off operation 1194
15.5.3.5 Broadcast storm protection 1194
15.6 SWS21X Range – Star Architecture 1196
15.6.1 Capability 1196
15.6.1.1 Principle 1196
15.6.1.2 Schneider Electric RSTP compatibility 1196
15.6.1.3 Configuration constraints 1196
15.6.2 Functional composition 1197
15.6.3 Power management 1198
15.6.4.2 100Base Fx 1198
15.6.5.1 Address lookup 1198
15.6.5.2 Auto-negociation and speed-sensing 1198
15.6.6.1 SWS21 MIB Structure 1199
15.6.7 Technical Data 1200
15.6.7.1 SWS21 Range 1200
15.6.7.2 Ethernet Port Characteristics 1201
15.6.7.2.1 10/100BaseTx Port 1201
15.6.7.2.2 100BaseFx Multi Mode Port 1201
15.6.7.2.3 100BaseFx Single Mode Port 1201
15.6.8 SWS21x Leds 1202
C264/EN UM/E50.5 1173


15.6.9.1.1 JP1 1204
15.6.9.1.2 J10 (board number) 1204
15.6.10 Connections 1206
15.6.10.1 Ethernet connection 1206
15.6.10.1.1 Ethernet cable type 1206
15.6.10.1.2 Ethernet optical fiber 1206
15.6.10.2 Internal connectors 1207
15.6.10.2.1 MiCOM C264 BUS (J13) 1207
15.6.10.2.2 10/100BaseTx ports 1 to 4 (J3) 1207
15.6.10.2.3 Fault signal output (J14) 1208
15.7 REU20x Range –Architecture with PRP, HSR and RSTP 1209
15.7.1.5 IEEE 1588 PTP 1213
15.7.2.1 REU20x Range 1214
15.7.2.3.2 Status Relay 1215
15.7.2.4.2 Insulation 1217
15.7.2.4.4 Climatic 1219
15.7.2.4.5 Mechanical 1219
1174 C264/EN UM/E50.5


15.8 Fiber Optic budget calculation 1226
15.8.1 Example 1: between devices 1226
15.8.2 Example 2: between devices with patch panel 1226
C264/EN UM/E50.5 1175

15.1 Introduction
The MiCOM Ethernet boards range is designed to deal with the needs of a wide range of electric
plants. Emphasis has been placed on strong compliance with standards, scalability, modularity
and open architecture.
These features facilitate the use of MiCOM products in several applications, from the most basic
to the most demanding. They also ensure interoperability with existing components.
The Schneider Electric philosophy is to provide a range of Ethernet products such as devices
taking into account the compulsory requirements of electrical substations, including power supply
and immunity to environmental constraints.
It also provides solutions to specific requirements such as network redundancy management.
Each of these products can be used independently or can be integrated to form a EPAS system,
which is a Digital Control System (DCS).
15.1.1 MiCOM Ethernet Device Series

Driven by requests from all over the world for advanced substation applications for Automation,
control and monitoring, Schneider Electric is committed to provide a comprehensive range of
Ethernet-based products that respond to our customers' needs.
Standard Ethernet products rarely meet the constraints of electrical plants: environmental, power
supply, redundancy, etc.
The MiCOM Ethernet Device series has been specially tailored to respond to all of these
requirements and is compatible with the EPAS system. The MiCOM Ethernet range is designed to
address different kinds of architectures and installations.
15.1.2 MiCOM C264Ethernet switch boards

The SWXxxx Ethernet switch board range relies on managed devices that are easy to install and
operate in an electrical plant environment (IEC 61000-4 & 60255-5).
The SWXxxx Ethernet switch board range supports 10BaseT, 100BaseTX and 100BaseFX (IEEE
802.3 standard). Management of full duplex communication is available for 100BaseTx or
100BaseFx.
To adapt a Switch board to your application, configure the necessary parameters with the
“jumpers” located in the board.
15.1.3 MiCOM Ethernet Redundant REU20x

The MiCOM REU20x range is a set of devices with a connector embedded with the
PRP/HSR/RSTP protocol to provide the Ethernet Redundancy (IEC 62439-3: PRP and HSR).
The MiCOM REU20x range relies on managed devices that are easy to install and operate in an
electrical plant environment (IEC 61000-4, IEC 60255-5 & IEC 61850-3).
MiCOM REU20x supports 100BaseTX and 100BaseFX (IEEE 802.3 standard).
The MiCOM REU20x is usable without configuring the host.
1176 C264/EN UM/E50.5

15.2 Glossary and Definitions

Term Definition
100Base TX The copper port (RJ45) is full duplex at 100 Mbps.
100Base FX The fiber optic ports are full duplex at 100 Mbps.
Category 5 unshielded twisted pair (UTP) cabling. An Ethernet
network operating at 10 Mbps (10BASE-T) will often tolerate low
quality cables, but at 100 Mbps (10BASE-Tx) the cable must be
rated as Category 5, or Cat 5 or Cat V, by the Electronic Industry
Cat. 5 Association (EIA). This rating is printed on the cable jacket. Cat 5
cable contains eight conductors, arranged in four twisted pairs,
and terminated with an RJ45 type connector. In addition, there are
restrictions on maximum cable length for both 10 and 100 Mbps
networks.
DAN Dual Attached Node
Fast Ethernet An Ethernet system designed to operate at 100 Mbps.
High-availability Seamless Redundancy (HSR) is a redundancy
HSR
protocol for Ethernet networks.
Industrial communication networks for electrical substation
IEC 61850-3
automation – Part 3: General requirements
Industrial communication networks – High availability automation
IEC 62439-3 networks – Part 3: Parallel Redundancy Protocol (PRP) and High-
availability Seamless Redundancy (HSR)
Interlink Link that connects two network hierarchies
An Internet Protocol address (IP address) is a numerical label
assigned to each device computer network that uses the Internet
IP address Protocol for communication. An IP address serves two principal
functions: host or network interface identification and location
addressing.
The Media Access Control (MAC) address is a unique 48-bit
MAC address hardware address assigned to every network interface card.
Usually written in the form 01:23:45:67:89:ab.
Management Information Base (MIB), refer in section IEC 62439-3
MIB
MIB
The Media Independent Interface (MII) was originally defined as a
standard interface used to connect a fast Ethernet (i.e., 100 Mbps)
MAC-block to a PHY chip. Being media independent means that
different types of PHY devices for connecting to different media
MII
(i.e. Twisted pair copper, fiber optic, etc.) can be used without
redesigning or replacing the MAC hardware. The MII bus
(standardized by IEEE 802.3u) connects different types of PHYs
(Physical Transceivers) to Media Access Controllers (MAC).
C264/EN UM/E50.5 1177

Term Definition
NU Not Used
OID Object Identifier
The OSI Physical Layer: The physical layer provides for
PHY
transmission of cells over a physical medium.
PC Personal Computer (Gateway or HMI)
If there is no cable on a port, most of the circuitry for that port is
Power management
disabled to save power.
REU Redundant Ethernet Unit
Parallel Redundancy Protocol (PRP) is a data communication
network standardized by the International Electrotechnical
PRP Commission as IEC 62439-3 Clause 4. It allows systems to
overcome any single network failure without affecting the data
transmission.
RedBox Device attaching Simple Attached Node to a redundant Network
Short for remote monitoring, a network management protocol that
allows network information to be gathered at a single workstation.
Whereas SNMP gathers network data from a single type of
Management Information Base (MIB), RMON 1 defines nine
additional MIBs that provide a much richer set of data about
RMON
network usage. For RMON to work, network devices, such as
hubs and switches, must be designed to support it. The newest
version of RMON, RMON 2, provides data about traffic at the
network layer in addition to the physical layer. This allows
administrators to analyze traffic by protocol.
Rapid Spanning Tree Protocol is a network protocol that provides
RSTP
a loop-free topology any bridged Ethernet local area network.
SAN Simple Attached Node
Small Form-factor Pluggable is a modular (hot-pluggable) slot for
SFP connector variable transceiver module (optical module, copper cable
module…)
Level 1 VLAN (also called a Port Based VLAN) defines a virtual
network according to the connection ports on the switch.
VLAN Level 2 VLAN (also called a MAC Address-Based VLAN)
comprises of defining a virtual network according to the MAC
addresses of the stations.
1178 C264/EN UM/E50.5

15.3 SWR21x Range – Dual Ring Architecture

The SWR21x range is dedicated for fast redundant Ethernet ring. All SWR21boards have 4
Copper connections through RJ45, with speed automatically adjusted from external emitters to 10
or 100 Mbps.
Copper Ethernet link is limited in distance and subject to perturbation. The Ethernet redundant
ring is based on optical inter-switch connection, depending on the link length.
Model Description Connectors

SWR212 Fast Ethernet industrial switch 4 x RJ45
(Ref: 2071646 A01) Multimode 1300 nm 2 x ST
15.3.1 Fast redundant ring capability

15.3.1.1 Self healing ring
Ethernet switches learn MAC addresses in order to switch packets to their destination port and
save the addresses in their memory if they are active. If a MAC address ceases to be active, it is
aged out of the switch memory after a few minutes.
This switch-address- ageing delay presents a problem when a LAN needs to be reconfigured
quickly.
There is no benefit to having a fast ring recovery technique if the switch members of the ring
prevent Ethernet traffic from moving to the recovery traffic path.
With the Schneider Electric redundant ring without or with ring default the all switch on the ring
sees no difference in the advance of the frame; no reset switch, no relearning for the MAC
address.
- Figure 681 - Self-Healing ring mechanism
15.3.1.2 Ethernet switch with Self-healing ring facilities

The SWR21x is a “repeater” with a standard 802.3 Ethernet switch plus the self healing manager
(SHM). The following drawing describes the internal architecture of such device.
C264/EN UM/E50.5 1179

- Figure 682 - Internal architecture of SWR21
15.3.1.3 Schneider Electric Ethernet ring redundancy

The SHM functions manage the ring. If the optic Fiber connection between two devices is broken,
the network continues to run correctly.
During nominal situation, Ethernet packet goes in primary Fiber always in the same direction, and
only a checking frames (4 bytes) is sent every 5 ms in secondary Fiber in the opposite direction.
If link is cut, both SHM start immediately the network self-healing. At one side messages receive
are no more emitted to the primary fiber but to the secondary fiber. On the other side of the cut off,
messages received to secondary are emitted to primary and the new topological loop is closed.
Thanks to this property it is possible to extend the number of equipments or the size of a sub-
station without stopping exploitation. When the loop is open, new equipments are connected on
one side and the redounded loop is closed.
To increase the reliability some specific mechanisms are used:

• Watching the quality of transmission. Each frame (Ethernet packet or checking frame) is
controlled by the SHM. A detection of large error rate will eliminate the faulty link and start
automatically the self healing,
• Supervising the link same in the absence of traffic on the primary link (every 5 ms checking
frames are sending to test the link). The link is supervised permanently with the real frame.
1180 C264/EN UM/E50.5

15.3.1.4 Ethernet system performances
- Figure 683 - Nominal redundant Ethernet ring architecture with MiCOM SWR21x and Hx5x
switches
- Figure 684 - Ethernet ring architecture with MiCOM SWR21x and Hx5x switches, after failure
15.3.1.5 Max time of end to end delay

To calculate the time end to end, use the following table based on the nominal situation:
Send a Goose frame from…. Time at

Abr. Comments
To… 100Mbps
IED 1 to Switch A 22 ms 262 bytes + inter-frame
Store and forward
Switch A to IED 2 22 ms
mechanism
Switch A to the network 2 ms tl Repeater latency time
Propagation time on the fiber ms 4,8 ms /km
Network to network 2 ms tl Repeater latency time
When the frame circulates on the ring it does not cross the switch the transit time is only tl.
C264/EN UM/E50.5 1181

15.3.1.6 Benefits
• Ultra fast ring redundant capability (< 1ms for network reconfiguration)
• Fast propagation on the ring (no transfer time with the switch via store and forward
mechanism)
• No central redundancy manager
• Specific mechanism of frames checking
• Ring management
15.3.2 SNMP Management

Simple Network Management Protocol is the network protocol developed to manage devices on
an IP network. With SNMP the available information is defined by Management Information
Bases (MIB). The format of SNMP data takes the form of a tree structure, with each node in the
tree being identified by a numerical Object IDentifier (OID). Each OID identifies a variable that can
be read or set via SNMP with an appropriate software. The information in the MIBs is
standardised.
15.3.2.1 SWR21x - MIB Structure

The SNMP MIB consists in distinct OIDs; each of them refers to a defined collection of specific
information used to manage devices on the Schneider Electric’ ring. The Schneider Electric MIB
uses three types of OID.
System:
Address Name
0 Ccitt
1 ISO
3 Org
6 DOD
1 Internet
2 mgmt
1 Mib-2
1 sys
Schneider Electric
1 sysDescr
Switch
Optical Link Status:
1 – No Default
2 sysObjectID 2 – Default Rs
3 – Default Rp
4 – No Link
1182 C264/EN UM/E50.5

Address Name
The time (in hundredths
of a second) since the
3 sysUpTime
switch was last re-
initialized.
4 sysContact
5 sysName SWR21
6 sysLocation
RMON:
Address Name
0 Ccitt
1 ISO
3 Org
6 DOD
1 Internet
2 mgmt
1 Mib-2
16 Rmon
1 stat
1 etherstat
1 Port number (*)
9 etherStatsIndex etherStatsUndersizePkts
10 etherStatsIndex etherStatsOversizePkts
12 etherStatsIndex etherStatsJabbers
13 etherStatsIndex etherStatsCollisions
14 etherStatsIndex etherStatsPkts64Octets
etherStatsIndex etherStatsPkts65to127Oct
15
ets
etherStatsIndex etherStatsPkts128to255O
16
ctets
17
ctets
etherStatsIndexetherStatsPkts512to1023Oc
18
tets
etherStatsIndexetherStatsPkts1024to1518O
19
ctets
(*) Port number:
C264/EN UM/E50.5 1183

• 1 to 4: standard ports
• 5 and 6: ports for redundant ring
15.3.2.2 SNMP Client Software

MIB Browser Software enables to perform all the basic SNMP operations, such as GET,
GETNEXT, RESPONSE, A very simple SNMP Client software is enough for using the Schneider
Electric MIB in Schneider Electric range of switches.
15.3.3 SWR21x Leds

LEDs are used to indicate the state of SWR21 and of the links. They are dedicated to Expert
Maintenance.
- Figure 685 - SWR21x Leds
The table below indicates the LED meaning:
LED # Color Description

E1 default L1 Red E1 Default
Rp (Reception
Link Rp L2 Green
Primary) Link OK
Receive Rp L3 Green Traffic detected
E2 default L4 Red E2 Default
Link Rs L5 Green Link OK
Receive Rs L6 Green Traffic detected
1184 C264/EN UM/E50.5


Number of switches detected on the
L7 Green
ring bit 0
L8 Green
ring bit 1
L9 Green
ring bit 2
L10 Green
ring bit 3
L11 Green
ring bit 4
L12 Green
ring bit 5
L13 Green
ring bit 6
L14 Green
ring bit 7
Off: no connection
Green: link
Link and activity port 1 L15 Green
Green + blink: link +
activity
Link and activity port 2 L16 Green “
Off: 10Mbps
Speed port 1 L20 Green
Green: 100Mbps
Speed port 2 L21 Green “
Speed port 5 L24 Green Port not used
Upon power up the SWD21xx will go through a series of self-testing. The 5 “link LED” will flash a
few seconds.
15.3.4 Settings
15.3.4.1 Internal Jumpers
- Figure 686 - Jumper settings
C264/EN UM/E50.5 1185

Status is “closed” when the jumper is setted.
# Open Closed Factory setting

J10-1 Board address bit 1 = 1 Board address bit 1 = 0 Closed
15.3.4.2 Address of the board

Each board on the ring has a specific address. Each address must be single and included
between 1 and 127.
15.3.4.3 How to configure the address ?

The address is equal to the sum of the « open bits ».
At the beginning address = 0

If J10-1 = open address = address + 1 if not address = address + 0
Example
J10-1 = open address = address + 1

J10-3 = close address = address + 0
Address = 11
15.3.4.4 IP Address of the repeater

The repeater IP address is accomplished in the following way:
1186 C264/EN UM/E50.5

- Figure 687 - IP address
NOTE: Schneider Electric switch manager software forces the third IP field to “254” value.
15.3.5 Connections: J14 Fault signal output

The optical ring is monitored. If one link come down the default is announced by the contacts:
- Figure 688 - J14 pin out
C264/EN UM/E50.5 1187

15.4 SWD21x Range – Dual Homing Architecture

The SWD21x range of Ethernet boards is dedicated to Dual Ethernet Star architecture and
defined by the type of Ethernet optical fiber it is connected (single mode or multi mode). All
equipment of the SWD21x range has 4 Copper connections through RJ45, with speed
automatically adjusted from external emitters to 10 or 100 Mbps, and 2 Ethernet optical ports with
dual homing mechanism.
The Ethernet dual homing star is based on optical connection; depending on the link length. The
user may choose between multi mode optic fiber (up to 2 km) and single mode optic fiber (up to 20
km) for long distance.

SWD212 Fast Ethernet industrial switch 4 x RJ45
(Ref: 2071647 A01) Multi mode 1300 nm 2 x ST
SWD214 Fast Ethernet industrial switch 4 x RJ45
(Ref: 2071647 A02) Single mode 1310 nm 2 x SC
15.4.1 Dual homing typical architecture
- Figure 689 - Dual homing typical architecture
1188 C264/EN UM/E50.5

15.4.2 Dual homing Switch Description
- Figure 690 - Dual homing switch description
15.4.3 Dual homing Features

15.4.3.1 10Base T and 100Base Tx
The copper ports are full/half duplex and auto-sense the transmission speed. They will auto-
negociate with the connected device to determinate the optimal speed. When the connected
device is only capable of transmitting at 10Mbps, the switch follows the 10Mbps.
15.4.3.2 Power management

If there is no cable on a port, most of the circuitry for that port is disabled to save power.
15.4.3.3 Address look up

Each Ethernet device inserts its unique “MAC address” into each message it sends out. The port
on the switch used for given MAC address is automatically learned when a frame is received from
that address. Once an address is learned, the switch will route messages to only the appropriate
port. A time stamp is also placed in memory when a new address is learned. This time stamp is
used with the aging feature, which will remove unused MAC Addresses from table after 300
seconds. The broadcasting messages are transmitted on all ports.
Up to 2048 MAC addresses can be stored and monitored at any time.
15.4.3.4 Back pressure for half duplex

The MICOM SWD2xx will apply « back pressure » when necessary with half-duplex operation.
This «back pressure » will reduce congestion on busy networks.
15.4.3.5 Auto Negotiation and Speed-Sensing

All six RJ45 ports independently support auto negotiation for speeds in the 10BaseT and
100BaseTx modes. Operation is according to the IEEE 802.3u standard.
C264/EN UM/E50.5 1189

15.4.3.6 Forwarding
The MICOM SWD2xx support store and forward mode. It will forward messages with know
addresses out only the appropriate port. Messages with unknown addresses, broadcast
messages and multicast messages will get forwarded out all ports except the source port. The
switch will not forward error packets, 802.3x pause frames or local packets.
15.4.3.7 Priority tagging

802.1p priority is enabled on all ports.
15.4.3.8 Flow control

The MiCOM SWD2xx automatically supports standard flow control frames on both the emission
and reception sides.
On the reception side, if the switch receives a pause control frame it will not transmit the next
normal frame until the timer, specified in the pause control frame, expires. If another pause frame
is received before the current timer expires, the timer will be updated with the new value in the
second pause frame. During this period (being flow controlled), only flow control packets from the
switch will be transmitted.
On the transmission side, the switch has intelligence and determines when to invoke the flow
control. The flow control is based on availability of the system resources, including available
buffers, available transmission queues and available reception queues. The switch will flow
control a port, which just received a packet, if the destination port resource is being used up. The
switch will issue a flow control frame (XOFF), containing the maximum pause time defined in
IEEE standard 802.3x. A hysteresis feature is provided to prevent flow control mechanism from
being activated and deactivated too many times.
The switch will flow control all ports if the reception queue becomes full.

For SNMP Management description, report to topic "SNMP Management" on page 1198.
15.4.5 SWD21x Leds

LEDs are used to indicate the state of SWD21x and of the links. They are dedicated to Expert
Maintenance.
1190 C264/EN UM/E50.5

- Figure 691 - SWD21x Leds

Link A fault L1 Red Fault on link A
Link A reception L2 green Reception Link A
Link A traffic L3 Green Traffic on Link A
Link B fault L4 Red Fault on Link B
Link B reception L5 Green Reception Link B
Link B traffic L6 Green Traffic Link B
Switch Number bit 0 L7 Green
Off: no connection
Green: link
Link and activity port 1 L15 Green
activity
Link and activity port 2 L16 Green «
C264/EN UM/E50.5 1191


Off: 10Mbps
Speed port 1 L20 Green
Green: 100Mbps
Speed port 2 L21 Green «
Speed port 5 L24 Green Port not used
15.4.6 Settings
Report to topic "Settings" on page 1185.
15.4.7 Connections: J14 Fault signal output

The optical health is monitored. If one link come down the default is announced by the contacts:
1192 C264/EN UM/E50.5

15.5 SWU20x Range – Star Architecture

The SWU20x range of Ethernet boards is dedicated to Ethernet Star architecture and defined by
the optional type of Ethernet optical fiber it is connected (single mode or multi mode). All
equipment of the SWU20x range has 4 Copper connections through RJ45, with speed
automatically adjusted from external emitters to 10 or 100 Mbps, and optionally 2 Ethernet optical
ports.
The Ethernet dual homing star is based on optical connection; depending on the link length the
user may choose between multi mode optic Fiber (up to 2 km) and Single mode optic Fiber for
long distance (up to 20 km).

SWU200
Fast Ethernet industrial switch 4 x RJ45
Ref: 2070745 A01
SWU202 Fast Ethernet industrial switch 4 x RJ45
Ref: 2070745 A03 Multimode 1300 nm 2 x ST
15.5.1 Ethernet Port Characteristics

15.5.1.1 10/100BaseTx Port
Connector type Shielded RJ45 jack

Twisted pair cable Cat 5
Max cable length with Cat 5 100m
15.5.1.2 100BaseFx Multi Mode Port
Fiber port connector ST

Optimal fiber cable 62,5/125 mm or 50/125 mm
Center wavelength 1300 nm
TX output power -19 dBm
RX input sensitivity -31 dBm
Maximum distance 2000 m
Half or full Duplex Switch selectable
15.5.1.3 100BaseFx Single or Mono Mode Port
Fiber port connector SC

Optimal fiber cable 9/125 or 10/125 mm
Maximum distance 20 000 m
C264/EN UM/E50.5 1193


15.5.2 Ethernet Port Switching Features

SWUxxx determines automatically at message reception the speed of its transmission layer 10 or
100 Mbps SWUxxx adapts automatically itself to this transmission speed and other transmission
parameters like half or full duplex.
15.5.2.1 10Base Tx and 100Base Tx

device is only capable of transmitting at 10 Mbps, the SWUxxx follows the 10 Mbps.
15.5.2.2 100Base Fx
The fiber optic ports are full/half duplex at 100 Mbps.
15.5.3 Ethernet Management

15.5.3.1 Address look up
on the SWUxxx used for given MAC address is automatically learned when a frame is received
from that address. Once an address is learned, the SWUxxx will route messages to only the
appropriate port. A time stamp is also placed in memory when a new address is learned. This time
stamp is used with the aging feature, which will remove unnused MAC Addresses from table after
300 seconds. The broadcasting messages are transmitted in the all ports.
15.5.3.2 Buffering
An internal buffer is used for buffering the messages. There are 1024 buffers available. The
factory setting mode adaptively allocates buffers up to 512 to a single port-based loading.
15.5.3.3 Back off operation

The SWUxxx will drop a packet after 16 collisions.
15.5.3.4 Back pressure for half duplex

The SWUxxx will apply « back pressure » when necessary with half-duplex operation. This «back
pressure » will reduce congestion on busy networks (J factory setting).
15.5.3.5 Broadcast storm protection

Broadcasts and multicasts are limited to 5% of the available bandwidth.
15.5.3.6 Auto Negotiation and Speed-Sensing

All the 4 RJ45 ports of the SWUxxx independently support auto negotiation for speeds in the
10BaseT and 100BaseTx modes. Operation is according to the IEEE 802.3u standard.
1194 C264/EN UM/E50.5

15.5.3.7 Forwarding
SWUxxx supports store and forward mode. SWUxxx will forward messages with know addresses
out only the appropriate port. Messages with unknown addresses, broadcast messages and
multicast messages will get forwarded out all ports except the source port. SWUxxx will not
forward error packets, 802.3x pause frames or local paquets.

802.1p priority is enabled on all ports. A 6 KB buffer is reserved for priority traffic.
15.5.3.9 Flow control

The switch automatically supports standard flow control frames on both the transmission and
reception sides.
On the reception side, if SWUxxx receives a pause control frame it will not transmit the next
normal frame until the timer, specified in the pause control frame, expires. If another pause frame
is received before the current timer expires, the timer will be updated with the new value in the
second pause frame. During this period (being flow controlled), only flow control packets from
SWUxxx will be transmitted.
On the transmission side, SWUxxx efficient ways to determine when to invoke flow control. The
flow control is based on availability of the system resources, including available buffers, available
transmission queues and available reception queues. SWUxxx will flow control a port, which just
received a packet, if the destination port resource is being used up. SWUxxx will issue a flow
control frame (XOFF), containing the maximum pause time defined in IEEE standard 802.3x. A
hysteresis feature is provided to prevent flow control mechanism from being activated and
deactivated too many times.
SWUxxx will flow control all ports if the reception queue becomes full.
C264/EN UM/E50.5 1195

15.6 SWS21X Range – Star Architecture

The SWS21x range of Ethernet boards is dedicated to Ethernet Start architecture and is
embedded with the RSTP compatible protocol to provide redundancy.
SWS21x boards have 4 copper connections through RJ45, with speed automatically adjusted
from external emitters to 10 or 100 Mbps, and 2 Ethernet optical ports.
The table below describes the SWS21x range, detailing the connectivity used.

SWS212 Fast Ethernet industrial switch 4 x RJ45
(Ref: 2071988 A01) Multimode 1310 nm 2 x ST
SWS214 Fast Ethernet industrial switch 4x RJ45
(Ref: 2071988 A02) Single mode 1310 nm 2 x SC
15.6.1 Capability
15.6.1.1 Principle
Ethernet redundancy is usually managed by protocols that calculates another path to a
destination (by sending BPDUs) when the main link breaks. This could take from hundreds of
milliseconds to seconds.
15.6.1.2 Schneider Electric RSTP compatibility

The Spanning Tree Protocol (STP) is a network protocol that ensures a loop-free topology any
bridged Ethernet local area network. The basic function of STP is to prevent bridge loops and the
broadcast radiation that results from them. Spanning tree also allows a network design to include
spare (redundant) links to provide automatic backup paths if an active link fails, without the
danger of bridge loops, or the need for manual enabling/disabling of these backup links.
RSTP is the Rapid Spanning Tree Protocol (RSTP). RSTP provides significantly faster spanning
tree convergence after a topology change.
15.6.1.3 Configuration constraints

Better performances are obtained with RSTP ports linked as EDGE ports configuration.
As in RSTP standard, detection of root switch failure is done in 3 “hello” times, which is 6 seconds
if default “hello” times have not been changed. With SWS21 “hello” time is configured at 2
seconds.
Only the simple star architecture is supported, this involves the dual start architecture, daisy chain
architectures and ring architectures are not allowed.
1196 C264/EN UM/E50.5

- Figure 693 - Simple star architecture
In RSTP mode, the performances of the GOOSE messaging transmission are not guaranteed
during time of network topology change.
15.6.2 Functional composition

The RSTP board is composed of the function blocs given below:
- Figure 694 - SWS21 functional composition
The central part is composed by switching component managing up to 8 Ethernet links. A FLASH
Memory stores the switching algorithm and manages minimum parameters of Ethernet switching
algorithm.
4 copper connections are defined in standard (there is the fifth port inside the board). 2 optic
connections are defined in the range (multi-mode or single-mode).
Internal LEDs and alarm contact are defined in standard to check that product operate correctly.
C264/EN UM/E50.5 1197

15.6.3 Power management

If there is no cable on an Ethernet port, most of the circuitry for that port is disabled to save power.
15.6.4 Ethernet Port Switching Features

SWS21 determines automatically at message reception the speed of its transmission layer 10 or
100 Mbps. It adapts automatically itself to this transmission speed and other transmission
parameters like half or full duplex.
15.6.4.1 10Base Tx and 100Base Tx

device is only capable of transmitting at 10Mbps, the SWS21 follows the 10Mbps.
15.6.4.2 100Base Fx
The fibber optic ports are full duplex at 100Mbps.
15.6.5 Ethernet Management

15.6.5.1 Address lookup
on the SWS21 used for given MAC address is automatically learned when a frame is received
from that address.
Once an address is learned, the SWS21 will route messages to only the appropriate port.
The broadcasting messages are transmitted in the all ports.
15.6.5.2 Auto-negociation and speed-sensing

All RJ45 ports of the SWS21 independently support auto negotiation for speeds in the 10BaseT
and 100BaseTx modes. Operation is according to the IEEE 802.3u standard.
15.6.5.3 Forwarding
SWS21 supports store and forward mode. SWS21 will forward messages with know addresses
out only the appropriate port. Messages with unknown addresses, broadcast messages and
multicast messages will get forwarded out all ports except the source port.
SWS21will not forward error packets, 802.3x pause frames or local paquets.

802.1p priority is enabled on all ports.

Simple Network Management Protocol is the network protocol developed to manage devices on
an IP network. With SNMP the available information is defined by Management Information
Bases (MIB). The format of SNMP data takes the form of a tree structure, with each node in the
1198 C264/EN UM/E50.5

tree being identified by a numerical Object IDentifier (OID). Each OID identifies a variable that can
be read or set via SNMP with an appropriate software. The information in the MIBs is
standardised.
15.6.6.1 SWS21 MIB Structure

The SNMP MIB consists in distinct OIDs; each of them refers to a defined collection of specific
information used to manage devices on the ring. The Schneider Electric MIB uses three types of
OID.
System:
Address Name
0 Ccitt
1 ISO
3 Org
6 DOD
1 Internet
2 mgmt
1 Mib-2
1 sys
1 sysDescr Schneider Electric Switch
Optical Link Status:
1 – No Default
2 sysObjectID 2 – Default Link A
3 – Default Link B
4 – No Link
3 sysUpTime xday yh :zm :zzs :yyms
4 sysName SWS21
RMON:
Address Name
0 Ccitt
1 ISO
3 Org
6 DOD
1 Internet
2 mgmt
1 Mib-2
16 Rmon
C264/EN UM/E50.5 1199

Address Name
1 stat
1 etherstat
1 Port number (*)
9 etherStatsIndex etherStatsUndersizePkts
10 etherStatsIndex etherStatsOversizePkts
12 etherStatsIndex etherStatsJabbers
13 etherStatsIndex etherStatsCollisions
14 etherStatsIndex etherStatsPkts64Octets
etherStatsIndex etherStatsPkts65to127Oct
15
ets
etherStatsIndex etherStatsPkts128to255Oc
16
tets
etherStatsIndex etherStatsPkts256to511Oc
17
tets
18
ctets
etherStatsIndex etherStatsPkts1024to1518
19
Octets
(*) Port number:

• Port #1 to #4: RJ45 ports
• Port #5: Internal port
• Port #6: FPGA port
15.6.6.2 SNMP Client Software

MIB Browser Software enables to perform all the basic SNMP operations, such as GET,
GETNEXT, RESPONSE, A very simple SNMP Client software is enough for using the Schneider
Electric MIB in Schneider Electric range of switches.
15.6.7 Technical Data

15.6.7.1 SWS21 Range
10/100BaseTx 100BaseFx Multi 100BaseFx Single

Ports
Copper Mode Mode
SWS212 4 2 (ST) -
SWS214 4 - 2 (SC)
1200 C264/EN UM/E50.5

15.6.7.2 Ethernet Port Characteristics

15.6.7.2.1 10/100BaseTx Port

15.6.7.2.2 100BaseFx Multi Mode Port
Fiber port connector ST

Optimal fiber cable 62,5/125 mm or 50/125 mm
Maximum distance 2000 m
15.6.7.2.3 100BaseFx Single Mode Port

Optimal fiber cable 9/125 or 10/125 mm
Maximum distance 20 000 m
15.6.7.3 General Characteristics
Auxilliary Fault Indication Relay

Connector 2 NC contact potential free
DC voltage 250 Vcc
Continuous current 5 Amps
Switching current 100 Amps / 30 ms
Power breaking with time constant 10 W under 48 Vcc with t = 20 ms
Ethernet Management
Standards IEEE802.3, 802.3u, 802.3x, 802.1p
Forwarding mode Store and forward
Memory bandwidth 2 Gbps
MAC Address 1K
C264/EN UM/E50.5 1201

Ethernet Management
Address learning Automatic
Broadcast storm protection Limited to 5%
Illegal frame Dropped per 802.3
Late collision Dropped after 512 bit times
15.6.8 SWS21x Leds

LEDs are used to indicate the state of SWS21 and of the links.
- Figure 695 - SWRS1x Leds
# Group LED Color Description

Fixed red if no healthy
Blinking red if active

L1 RSTP State Red link
Off : link healthy but

Optical LINK A
no active
L2 Link State green Green if light receive
Green during the
L3 Receive traffic Green
receipt of frame
1202 C264/EN UM/E50.5

# Group LED Color Description

Fixed red if no healthy
Blinking red if active

L4 RSTP State Red link
Off : link healthy but

Optical LINK B
no active
L5 Link State Green Green if light receive
Green during the
L6 Receive traffic Green
receipt of frame
L7 Board number Green bit 0
Board Address
Link and activity
L15 Green
port 4
Link and activity
L16 Green
port 3 Off: no connection
Link and activity Green: link

L17 Green
port 2
Link and activity activity
L18 Green
port 1
RJ45 link
Link and activity
L19 Green
port 5
L20 Speed port 4 Green
Off: 10Mbps
Green : 100Mbps
FPGA Off after the
L25 FPGA Red
initialization initialization
Upon power up the SWS21 will go through a series of self-testing. L25 is on during the FPGA
initialization and the 5 “link LED” (L15 to L19) will flash a few seconds.
C264/EN UM/E50.5 1203

15.6.9 Settings
15.6.9.1 Internal Jumpers
- Figure 696 - Internal jumpers
Status is “closed” when the jumper is setted.
15.6.9.1.1 JP1
JP1 is used to define the type of FPGA initialization:
- Figure 697 - JP1 default configuration
15.6.9.1.2 J10 (board number)

Each board has a specific IP address. The IP address is accomplished in the following way:
- Figure 698 - IP address
The board address is given by J10 jumpers:
1204 C264/EN UM/E50.5

- Figure 699 - J10 jumper for board address
# Open Closed Factory setting

The address is equal to the sum of the « open bits ».
Each board number must be single and included between 1 and 127.
At the beginning address = 0

C264/EN UM/E50.5 1205


Example

This gives the address = 11
15.6.10 Connections
15.6.10.1 Ethernet connection
15.6.10.1.1 Ethernet cable type
Only the cable insulated category 5 (FTP: Foil Twisted Pair) or insulated (STP – Shielded Twisted
Pairs) with RJ45 connectors must be used.
- Figure 700 - RJ45 connector
The norm is:

• 1 = white / orange
• 2 = orange
• 3 = white / green
• 4 = blue (non used)
• 5 = white / blue (non used)
• 6 = green
• 7 = white / brown (non used)
• 8 = brown (non used)
RECOMMENDATION: Maximum cable length is typically 100m for 10/100BaseTx.
15.6.10.1.2 Ethernet optical fiber

The FO cables are connected to the corresponding FO elements.
For the SWS212 (multi mode fiber) the connector is of ST Type.
For the SWS214 (single mode fiber) the connector is of SC Type.
1206 C264/EN UM/E50.5

- Figure 701 - Ethernet optical fiber – ST
- Figure 702 - Ethernet optical fiber – SC
15.6.10.2 Internal connectors

15.6.10.2.1 MiCOM C264 BUS (J13)
Pin Signal
A1 +5V
B1 +5V
C1 +5V
A3 GND
A6 GND
A9 GND
A15 GND
B5 GND
C6 GND
C9 GND
C15 GND
15.6.10.2.2 10/100BaseTx ports 1 to 4 (J3)
Connector #
J3-1 Tx1
J3-2 Tx2
J3-3 Tx3
J3-4 Tx4
C264/EN UM/E50.5 1207

15.6.10.2.3 Fault signal output (J14)

The optical ring is monitored. If one link come down the default is announced by contacts.
1208 C264/EN UM/E50.5

15.7 REU20x Range –Architecture with PRP, HSR and RSTP


15.7.1.5 IEEE 1588 PTP 1213
15.7.2.1 REU20x Range 1214
15.7.2.3.2 Status Relay 1215
15.7.2.4.2 Insulation 1217
15.7.2.4.4 Climatic 1219
15.7.2.4.5 Mechanical 1219
C264/EN UM/E50.5 1209

15.7.1 Functional Description

The MiCOM REU20x board is a Redundant Ethernet Unit compliant with the electric plant
environment. It supports standardized redundant protocols IEC 62439-3 (PRP/HSR) and RSTP
and allows to PC a PRP networking connection (100Mbps with Full Duplex mode). The board is
compliant with IEC 61850-3 standard.
The MiCOM REU20x board is configurable by Computer Administration Tool software (CAT).
Refer to topic "REU board" on page 997 in "Installation" on page 931 chapter for details.
Architecture HSR PRP RSTP

Ring Supported Not Supported
Supported
Redundant star Not Supported Supported
15.7.1.1 Product Range

The MiCOM REU20x range is dedicated to ultra fast Redundant Ethernet star or ring topologies
and is defined by the type of Ethernet connector. It has an Ethernet copper link via only one RJ45
connector, with speed automatically adjusted by the external emitters to 10 or 100 Mbps. The
Ethernet copper link is limited in distance and subject to interference.
The redundant Ethernet star or ring are based on optical inter-switch connection. The user has
the choice between using Multi-Mode Fiber optic for short distances or Single- Mode Fiber Optic
for long distances.
The table below describes the MICOM REU20x range, detailing the connectivity used.

Ethernet Redundant Board IEC
REU202 62439-3 (PRP/HSR) and RSTP
Multi-Mode fiber
1 x RJ45
Ethernet Redundant Board IEC 2 x combo ports:
REU204 62439-3 (PRP/HSR) and RSTP
Optical or RJ45
Single-Mode fiber
Ethernet Redundant Board IEC
REU
62439-3 (PRP/HSR) and RSTP
15.7.1.2 PRP/HSR/RSTP Architecture

The PRP, HSR and RSTP protocols manage network redundancy. Parallel Redundancy Protocol
(PRP), High-availability Seamless Redundancy (HSR) and Rapid Spanning Tree Protocol
(RSTP) is a standard data communication network. Protocol allows systems to overcome any
single network anomaly. In case deficiency of the optical fiber or RJ45 connection between two
devices, the network connection can be maintained.
PRP protocol can be applied to most Industrial Ethernet applications since it is independent of the
protocols and provides seamless failover. It is implemented in the end devices and two
independent paths are configured to exist between these end devices. The LAN networks (LAN_
A, LAN_B) are completely separated.
1210 C264/EN UM/E50.5

Redundancy management interface: MiCOM REU20x (DAN on figure below) allows to track the
health of each LAN, and especially to detect network traffic issues.
The Spanning Tree Protcocol (STP) is a network protocol that provides a loop-free topology any
bridged Ethernet local area network. The basic function of STP is to avoid bridge loops and the
broadcast radiation that results from them. STP also allows a network design to include spare
(redundant) links to provide automatic backup paths if an active link break and avoids bridge
loops, or the need for manual enabling/disabling of these backup links.
RSTP is the Rapid Spanning Tree Protocol (RSTP). RSTP provides significantly faster spanning
tree convergence after a topology change.
- Figure 704 - PRP network architecture
C264/EN UM/E50.5 1211

- Figure 705 - HSR network architecture
- Figure 706 - STP network architecture
DEVICE DESCRIPTION
The two LANs, named LAN_A and LAN_B are identical in protocol
at the MAC level, but they can differ in performance and topology
LAN (Ring or Star)
1212 C264/EN UM/E50.5

DEVICE DESCRIPTION
The Dual Attached Node (DAN) is connected to both LANs. Each

DAN has two ports that operate in parallel.
MiCOM REU20x is a DAN
The Virtual Dual Attached Node (VDAN), node that is connected to

both networks by a RedBox. A VDAN appears to other nodes like
a DAN.
Redundancy Box, bridging device to attach a network of VDANs or

a single VDAN
Single Attached Node (SAN), normal node with only one network
interface.
LAN Bridge
15.7.1.3 Power management

If Ethernet cable is not connected on port, most of the circuitry for that port is disabled to save
power.
The power consumption is 3W when the board is transferring data.
15.7.1.4 Ethernet Ports

The REU20x has a 100 Mbps speed transmission and full duplex.
The board has 2 Ethernet SFP FX ports. Fiber connector is a SFP slot and SFP modules for LC
1310 nm.
The Host port is a RJ45 connector and dedicated to PC RJ45 link.
The copper port (100BaseTX RJ45) is full duplex at 100 Mbps.
The fiber optic ports (100BaseFX) are full duplex at 100 Mbps.
15.7.1.5 IEEE 1588 PTP

The Precision Time Protocol (PTP) is a protocol used to synchronize clocks throughout a
computer network. On a local area network, it achieves clock accuracy, making it suitable for
measurement and control systems. The Transparent clock is a part of PTP and is implemented in
MICOM REUx board. HSR/PRP module implement a transparent clock on A, B and interlink port,
but grand master shall be on A and/or B port. Interlink is a slave only port. PTP is V2 in peer delay
mode.
C264/EN UM/E50.5 1213

15.7.2 Technical data

15.7.2.1 REU20x Range
100BaseTx
Ports SFP plug
Copper
2 SFP Multi-Mode fiber 100
REU202 V2 3
BaseFx
2 SFP Single-Mode fiber 100
REU204 V2 3
BaseFx
REU V2 3 0
15.7.2.2 Board Architecture
- Figure 707 - Board architecture
REU20x board offers 3 x MII 100Mbps, Full Duplex Ethernet connections:

• 1 internal port used by the Host network (Interlink)
• 2 redundant combo ports, each combo is composed by an optical port and a RJ45 port.
Priority is given to optical port
2 optical ports
2 RJ45 ports
REU20x board implements redundant protocols defined by the IEC 62439-3 (PRP/HSR):
• PRP for independent LAN attachment like dual star network topology
• HSR for dependent LAN attachment like dual ring network topology
REU20x board implements RSTP protocol:
1214 C264/EN UM/E50.5

• RSTP is protocol where redundancy is managed by network equipment as switch.
REU20x board has 1 x copper (RJ45), 2 x optical connections (Multi-Mode or Single-Mode) and 2
x RJ45 connections. Internal LEDs and Status Contact are available to check that product
operates correctly.
Component Usage
FLASH Memory for Saving FPGA firmware and board configuration
SDRAM Memory for Processor program execution and frame buffer
NIOS II 32-bit embedded RISC processor
Ethernet non redounded network 1 x MII port for connection to the
RJ45 Connector
HOST.
Ethernet redounded network 2 x (Optical or RJ45) + MII ports for
Combo Port A and B
connection to the external redounded network.
Relays Status Indication
15.7.2.2.1 10/100BaseTx port characteristics

15.7.2.3 General Characteristics

15.7.2.3.1 Protocols supported
The board is compliant with industrial communication networks for electrical substation
automation. The product supports standardized redundant protocols IEC 62439-3 (PRP/HSR)
and RSTP and Time synchronization protocols PTP (Transparent clock).
Protocol Norm
Redundancy Protocols IEC 62439-3 (PRP/HSR)
Spanning Tree Protocol IEEE 802.1D-2004 - RSTP
Time Synchronization IEEE 1588 V2-2008
15.7.2.3.2 Status Relay
Status Relay
Manufacturer / Reference OMRON / G6RN-15DC
Connector 2 NC contact potential free
Rated Voltage 5 VDC
Rated Current 8A
Max. switching voltage 250 VAC, 30 VDC
Max.switching current 8A
C264/EN UM/E50.5 1215

Status Relay
Mechanical durability 10 000 000 operations minimum
Operate time: 15 ms max
Rise time
Release time: 5 ms max
DANGER
HAZARD OF ELECTRIC SHOCK, EXPLOSION, OR ARC FLASH
For protective reasons and for compliance with the european commission low voltage directive
(2006/95/EC), the authorized voltage rating to be applied on the "status indication relay" is
limited to 75 Vdc or 50 Vac and with current not exceeding 5 A.
15.7.2.3.3 Ethernet Management
Ethernet Management
Standards IEEE802.3, 802.3u, 802.3x
Forwarding mode Cut-Through
Max Memory bandwidth 100 Mbps
Flow control Interlink port: yes
MAC Address learning Automatic
Illegal frame Dropped per 802.3
Max clients on interlink 1
Frame buffer size 12 Kbytes
Frame priority management None
Ethernet flow: 8 filters masks for the port
Filtering
Interlink
Supervision frame MAC multicast frame emission to 3 ports
15.7.2.3.4 Performances
Performances
Bytes, for case non redundant network side
Maximum frame length allowed 1536 Bytes, for case redundant network side
(Redundant Ethernet Link A, Redundant
Ethernet Link B)
IEEE 802.3 frame Supported
IEC 61850-8-3 frame Supported
Power consumption 3W
15.7.2.3.5 Interoperability
The board is compliant with standard
1216 C264/EN UM/E50.5

• CEI 62439-3 Edition 3 2016-03 for HSR/PRP.
• IEEE 802.1D-2004 – RSTP.
• IEEE 1588 V2 - 2008.
15.7.2.4 Environmental Characteristics

The MiCOM REU20x board supports climatic, mechanical and insulation tests complaint with
standard IEC 61850-3.
15.7.2.4.1 Definitions
Group identifier Description

B Relays Outputs
C Copper link (inter equipment link)
D Optical links (to distant connections)
15.7.2.4.2 Insulation
Type Test Name Standard Conditions

Insulated Resistance (B and C
IEC 60255-5 100 MOhm at 500 V (CM)
groups)
Group B
2kVAC 50 Hz duration: 1 min

Dielectric Withstand (B and C (CM)
IEC 60255-5
groups) Group C
1.5kVAC 50 Hz duration: 1
min (CM)
Group B
High Voltage Impulse (only B
IEC 60255-5 5 kV (CM)
group)
Group C: N.A.
15.7.2.4.3 Electromagnetic Compatibility

Case & Front Panel:
Electrostatic discharge IEC 61000-4-2 Test according IEC 61850-
3Ed1: 15KV air, 4KV contact
Group B:
IEC 60255-22-4 4 kV (CM)
Electrical Fast Transient/ Burst Coupling clamp
IEC 61000-4-4
(B group only)
2 .5KHz
100KHz
C264/EN UM/E50.5 1217


IEC 61000-4-5 Group B:
Surge Immunity (B group only)
IEC 60255-5 4 KV (CM) 40 ohm, 1KV (DM)
Group B:
High frequency conducted
IEC 61000-4-6 10 Vrms, 0.15 – 80 MHz, 80%
immunity (B group only)
AM 1kHz
Group Housing:
Power Frequency Magnetic
IEC 61000-4-8 100 A/m (60s), 1000 A/m
Field Immunity
(10s), 50 Hz
Group Housing:
Pulse Magnetic Field Immunity IEC 61000-4-9 Class 5 1000 A/m (1,2/50us 3 pulses
each 10s)
Class 5:
Damped Oscillatory Magnetic 100KHz 50pps

IEC 61000-4-10
Field Immunity 1MHz 400pps
100 A/m for 1mn

Group B:
Oscillatory waves immunity (B IEC 61000-4-12
group only) 2.5 kV (CM), 1 kV (RM),
IEC 61000-4-18
100kHz, 1Mhz
Group POWER SUPPLY:
Limits of Conducted Emission
EN 55022 0.15 to 30 MHz
(ATI)
Limit class A
Case:
Limit class A
Limits of Radiated Emission EN 55022 30Mhz – 1Ghz
Peak detection
10 meters measurement
Test according IEC61850-
3Ed1: 80MHz- 2,7GHz
Radiated Electromagnetic 10V/m 80% AM 1KHz
IEC 61000-4-3
Field Immunity DWELL time: 10s
On 4 sides
1218 C264/EN UM/E50.5

15.7.2.4.4 Climatic
Type Test Name Standard IEC61850-3 Conditions

Test Bd:
Dry Heat Operating IEC 60068-2-2 IEC 60870-2-2 +55 °C / 96 H &
+70 °C / 24 H
Test Bd:
Extended Dry Heat
IEC 60068-2-2 IEC 60870-2-2 +55 °C / 20 Days &
Operating
+70 °C / 24 H
Test Bd:
Hot Storage IEC 60068-2-2 IEC 60870-2-2
+85 °C / 96 H
Test Ab:
Cold Operating IEC 60068-2-1 IEC 60870-2-2
- 25 °C / 96 H
Test Ad:
Cold Storage IEC60068-2-1 IEC 60870-2-2
- 40 °C / 96 H
Test Ad:
Storage test at -25°C

Cold start test IEC60068-2-1 IEC 60870-2-2 then Power On , 5
cycles 3 minutes ON
an 10 minutes OFF)
Test Ca:
Humid Heat Operating IEC 60068-2-78 + 40 °C, 95 % RH, for
48 H
15.7.2.4.5 Mechanical

IEC 60255-21-1 Class Bm. 2 – 150Hz ,
Vibrations Operating EN 60068-2-6 3 axis , 3.5mm , 1g
1 cycle
Class 2 :
Vibrations No 2g from 10 to 500 Hz

IEC 60255-21-1
Operating
Class Bm. 2 – 500Hz ,
EN 60068-2-6
3 axis , 3.5mm , 2g
10 cycles
3 axis , 20g, 11ms ,
IEC 60255-21-2 half sinus form
Shock No Operating
EN 60068-2-27 100 shocks in each
direction
C264/EN UM/E50.5 1219


3 axis , 10g, 11ms ,
Shock Operating IEC 60255-21-2 half sinus form

direction
IEC 60255-21-2 Class1, 3 axis , 10g,

16ms , half sinus form
Bump No Operating EN 60068-2-27
1000 shocks in each
direction
Class 2 :
Vibrations No 2g from 10 to 500 Hz

IEC 60255-21-1
Operating
Class Bm. 2 – 500Hz ,
EN 60068-2-6
3 axis , 3.5mm , 2g
10 cycles
3 axis , 20g, 11ms ,
half sinus form
IEC 60255-21-2
Shock No Operating 100 shocks in each
EN 60068-2-27 direction
3 axis , 10g, 11ms ,

IEC 60255-21-2 half sinus form
Shock Operating
direction
IEC 60255-21-2 Class1, 3 axis , 10g,

16ms , half sinus form
Bump No Operating EN 60068-2-27
1000 shocks in each
direction
Class2, 3 axis ,
X and Y axis 2g from 8

Seismic Vibration IEC 60255-21-3 to 35Hz
Resistance EN 60068-2-6 Z axis 1g from 8 to
35Hz
1 cycle
Free fall on 6 sides
Drop test (free fall)
IEC 60068-2-31 2 falls a side
No Operating
Height: 5cm
1220 C264/EN UM/E50.5


Free fall on the 6 sides
of the package and
Package Drop test IEC 60068-2-31
one fall on one corner
and one fall on a edge
Bm test
2 – 500Hz according
Endurance Under the 3 axis
Sinusoïdal Vibrations NF EN 60068-2-6
No operating X and Y : 2g from 8 to
35Hz
One cycle
15.7.3 Connections and Led meaning
- Figure 708 - REU20x board
- Figure 709 - Rear view with connectors
C264/EN UM/E50.5 1221

15.7.3.1 Led meaning
- Figure 710 - Internal view with LEDs
# LED Color and meaning

OFF: Board NOT STARTED
L0 Board State GREEN: Board STARTING
GREEN Blinking: Board STARTED

OFF: Power OFF
L1 Power ON/OFF
GREEN: Power ON
15.7.3.2 Status connector

refer to topic "Status output" on page 1223.
15.7.4 Installation
NOTICE
When the internal circuitry of the MiCOM C264 is exposed and not protected against
electrostatic discharges (ESD), dust ingress, etc. ESD precautions and clean working
conditions should be maintained at all times.
To Install the REU20x board, do following:
1. MiCOM C264 Power supply off
2. Open the MiCOM C264 front panel
3. Unplug CPU/front panel link cable (RJ45)
4. Unscrew the holding screw to retain boards
5. Insert the REU20x board into free slot
6. Screw the holding screw to retain boards
7. Plug CPU/front panel link (RJ45)
8. Plug 2 x SFP transceivers (SFP connectors)
9. Connect 2 x optical fibers (SFP connectors)
10. Connect Ethernet cable (RJ45 connector)
1222 C264/EN UM/E50.5

11. Connect Relay Status cable
12. Close the MiCOM C264 front panel
13. MiCOM C264 Power supply on
NOTE: #1
REU20x is a pluggable board: No additional driver software is needed.
NOTE: #2
The MAC address and IP address are automatically configured when the board is power on. It
takes the addresses of the host.
15.7.4.1 Status output
- Figure 711 - Status connector
The optical redundant links A and B are monitored. If one link comes down the status error
detected is announced by relay contacts. The outputs of the two relays are connected to a Status
Connector. Two status contacts (see K1, K2 on Figure above) are used with one common
contact.
Relay Contact K1 (pin#1) Relay Contact K2 (pin#2) Description

OPEN OPEN Operating
Disconnection on Redundant
CLOSED OPEN
Ethernet Link A
OPEN CLOSED
Ethernet Link B
CLOSED CLOSED
Ethernet Link A and B or Power OFF.
C264/EN UM/E50.5 1223

DANGER
HAZARD OF ELECTRIC SHOCK, EXPLOSION, OR ARC FLASH
For protective reasons and for compliance with the european commission low voltage directive
(2006/95/EC), the authorized voltage rating to be applied on the "status indication relay" is
limited to 75 Vdc or 50 Vac and with current not exceeding 5 A.
15.7.4.2 Ethernet Connection

The Ethernet-based communication available in the REU20x uses either optical fiber media (LC
connector) or 4 twisted pair cable (RJ45 connector).
RECOMMENDATION: If the equipment is located at a long distance (>100 m for RJ45) from the
communication equipment or multiplexer, or if the cables run through a noisy area, then optical
communication should be used to interconnect the IEDs and the communication equipment.
Redundant ports are dedicated to 2 Ethernet combo ports composed with one SFP FX port and
one RJ45 port. Fibber connectors are SFP slot and SFP modules for LC type. LC SFP modules
support Single-Mode and Multi-Mode.
Device Type Optical Fiber Type Connector Type (see NOTE)

REU202 Multi-Mode • LC
REU204 Single-Mode • RJ45

• LC
REU -
• RJ45
NOTE: Only one is usable at same time. The SFP port take priority, mean if SFP and RJ45 are
connected only SFP works.
15.7.5 Maintenance
This topic describes the specific maintenance procedure for the REU20x. It is a complement to
chapter "Maintenance" on page 1144 of MiCOM C264 that should be read carefully before any
handling.
15.7.5.1 Uninstalling REU20x board
NOTE: NOTE: Before any disconnection, check that the labels correctly define the connectors
and match the description you have.
To uninstall REU20x board, do following:
2. Unplug Relay Status cable
3. Unplug Ethernet cable (RJ45 connector)
4. Unplug 2 x optical fibers (SFP connectors)
1224 C264/EN UM/E50.5

5. Unplug 2 x SFP transceivers (SFP connectors)
7. Unplug CPU/front panel link cable (RJ45)
8. Unscrew the holding screw to retain the REU20x board
9. Withdraw REU20x board from MiCOM C264 Rack
15.7.5.2 Reinstalling REU20x board

To reinstall a repaired or new REU20x board, do following:
3. Unscrew the holding screw to retain boards
4. Insert the REU20x board into free slot
5. Screw the holding screw to retain boards
6. Plug CPU/front panel link (RJ45)
7. Plug 2 x SFP transceivers (SFP connectors)
8. Connect 2 x optical fibers (SFP connectors)
9. Connect Ethernet cable (RJ45 connector)
10. Connect Relay Status cable
11. Close the MiCOM C264 front panel
12. MiCOM C264 Power supply on
13. Reconfiguring the board with the protocol of the network
C264/EN UM/E50.5 1225

15.8 Fiber Optic budget calculation

Optical power is expressed in Watts. However, the common unit of power measurement is the
dBm, defined by the following equation: Power (dBm) = 10 log Power (mW) / 1 mW.
The fiber optic budget is the difference between the power emitted into the fiber and the sensitivity
(minimum amount of power required) of the receiver connected through the fiber optic cable.
Link Power Budget = Transmitter Power (dBm) - Receiver Sensitivity (dBm)
- Figure 712 - Optical power transmission
Fiber Type Multi-Mode Single-Mode

Technology 62.5/125 micron 9/125 micron
Power coupled into fiber -20 dBm (Min.) -15 dBm
Receiver Sensitivity -31 dBm (Min.) -31 dBm
Link Power Budget 11 dB 16 dB
15.8.1 Example 1: between devices

Topic Multi-Mode Single-Mode
Link Power budget 11 dB 16 dB
Connector loss 1.6 dB 1.6 dB
Safety Margin 4 dB 4 dB
Allowed link attenuation 5.4 dB 10.4 dB
Typical cable attenuation 1 dB/km 0.4 dB/km
Maximum range 5.4 km 26 km
15.8.2 Example 2: between devices with patch panel

Link Power budget 11 dB 16 dB
Connector loss 1.6 dB 1.6 dB
Patch loss 2 dB 1 dB
Safety Margin 4 dB 4 dB
Allowed link attenuation 3.4 dB 9.4 dB
Typical cable attenuation 1 dB/km 0.4 dB/km
1226 C264/EN UM/E50.5


Maximum range 3.4 km 23.5 km
NOTE: The values given above are only approximate ones. Always use cable and connector
losses as specified by the manufacturer.
C264/EN UM/E50.5 1227

Schneider Electric
35 rue Joseph Monier
92500 Rueil Malmaison
France
+33 (0) 1 41 29 70 00
https://www.se.com
As standards, specifications, and designs change from time to time,

please ask for confirmation of the information given in this publication.
© 2010 - 2022 Schneider Electric. All Rights Reserved..
C264/EN UM/E50.5

Micom C264 en Um E50.5

Uploaded by

Copyright:

Available Formats

Micom C264 en Um E50.5

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Micom C264 en Um E50.5

Uploaded by

Copyright:

Available Formats

MiCOM C264

Bay Control and Protection Unit

To the extent permitted by applicable law, no responsibility or liability is assumed by Schneider

35 rue Joseph Monier

The addition of either symbol to a "Danger" or "Warning" safety label

Failure to follow these instructions will result in death or serious injury.

Failure to follow these instructions could result in injury or equipment damage.

Failure to follow these instructions could result in equipment damage.

It is recommended that incineration and disposal to water courses is avoided. The

2.8.2 General Labels 68

4.1.1.7 Halt mode 117

4.3.4.2 DI Debouncing and filtering 149

4.4.1.7 IED binary inputs 171

4.4.4 Accumulator Input Processing 209

4.5.3 Control of synchronized breakers 238

4.6.2 Built-in Automation functions 267

4.6.2.5.5 Other functions 288

4.6.2.7.14 Synchrocheck Schema with NOT(VLINE) and VBUSBAR voltage

4.8.3.2 Characteristics of the protection 359

4.9.1 IDMT Curves 374

5.2.4.3 80TE slot configuration 412

5.4.10 CCU200 board - Circuit breaker Control Unit 449

5.4.18.4 Rear panel connector 477

6.1.2 LED’s management 501

6.1.3.14 Menu tree 538

7.2.3.2 Configuring measurement acquisition and transmission 573

7.2.7.2.3 Adding an IED to a legacy network 607

7.3.2.4.1 Setting 'State labels' attributes of an MPS profile 717

7.3.6.4 Producing input datapoint 740

7.4.1.5.2 Adding a user function to a module 768

7.4.7.2.4 Linking a datapoint to an ISaGRAF® client link 845

7.5.5.2 Defining Negative Sequence Overcurrent protection function 876

7.5.16.5.2 Setting ‘Blocking protection’ automation functions 899

8.1.2 Personal Computer 933

8.6.6.3 Operator's record folders 975

9.2.1.4 I²t parameters 1020

10.3.2.4.7 Synchronization status 1049

10.4.3.3.1 Status byte 1063

10.4.5.2.2 Polling 1112

11.3.10.2 Protection Commissioning test sheets 1128

14.2 Cybersecurity Policy 1161

15.4.2 Dual homing Switch Description 1189

15.6.5.2 Auto-negociation and speed-sensing 1198

15.7.2.4.1 Definitions 1217

1.1 About this guide 46

1.1 About this guide

1.1.1 Document updates

1.2 What's new?

Chapter Topic Change

1.2.2 Previous guide revisions

Chapter Topic Change

1.2.2.2 Revision number: E50.3 (01/2022)

Chapter Topic Change

1.2.2.3 Revision number: E50.2 (08/2021)

Chapter Topic Change

1.3 Document organization and content

• handling and reception of MiCOM C264

• Copyrights and Trademarks of MiCOM C264