Micom C264P: Bay Computer With Feeder Protection C264P/En O/C80

MiCOM C264P
Bay Computer
with Feeder Protection
C264P/EN O/C80
Operation Guide
Operation Guide C264P/EN O/C80
MiCOM C264P Page 1/2
MiCOM C264P
BAY COMPUTER WITH FEEDER PROTECTION
CONTENTS
Safety & Handling C264P/EN SA/C80
Introduction C264P/EN IT/C80
Technical Data C264P/EN TD/C80
Functional Description C264P/EN FT/C80
Human Interface C264P/EN HI/C80
Application C264P/EN AP/C80
Lexicon C264P/EN LX/C80

C264P/EN O/C80 Operation Guide
Page 2/2 MiCOM C264P
BLANK PAGE
MiCOM C264P
SAFETY and HANDLING

TABLE OF CONTENTS
1. INTRODUCTION 3
2. HEALTH AND SAFETY 4

2.1 Health and Safety 4
2.2 Installing, Commissioning and Servicing 4
3. DECOMMISSIONING AND DISPOSAL 6
4. TECHNICAL SPECIFICATIONS FOR SAFETY 7
5. HANDLING OF ELECTRONIC EQUIPMENTS 8
6. PACKING AND UNPACKING 9
7. GUARANTEES 10
8. COPYRIGHTS & TRADEMARKS 11

8.1 Copyrights 11
8.2 Trademarks 11
9. WARNINGS REGARDING USE OF SCHNEIDER ELECTRIC

PRODUCTS 12
C264P/EN SA/C80 Safety & Handling
BLANK PAGE
1. INTRODUCTION
This document is a chapter of the MiCOM C264/C264C documentation. It describes the
safety, handling, packing and unpacking procedures applicable to MiCOM C264/C264C
modular computer series and associated equipment's and software tools.
2. HEALTH AND SAFETY

For all the safety purposes please refer to the Schneider Electric Safety Guide:
SFTY/4L M/G11-S (or later issue) and to the following chapters.
WARNING: THIS SAFETY SECTION SHOULD BE READ BEFORE COMMENCING
ANY WORK ON THE EQUIPMENT.
2.1 Health and Safety

The information in the Safety Section of the product documentation is intended to ensure
that products are properly installed and handled in order to maintain them in a safe condition.
It is assumed that everyone who will be associated with the equipment will be familiar with
the contents of the Safety Section.
2.2 Installing, Commissioning and Servicing
Equipment connections
Personnel undertaking installation, commissioning or servicing work on this equipment
should be aware of the correct working procedures to ensure safety. The product
documentation should be consulted before installing, commissioning or servicing the
equipment.
Terminals exposed during installation, commissioning and maintenance may present a
hazardous voltage unless the equipment is electrically isolated.
If there is unlocked access to the rear of the equipment, care should be taken by all
personnel to avoid electrical shock or energy hazards.
Voltage and current connections should be made using insulated crimp terminations to
ensure that terminal block insulation requirements are maintained for safety. To ensure that
wires are correctly terminated the correct crimp terminal and tool for the wire size should be
used.
Before energising the equipment it must be earthed using the protective earth terminal, or
the appropriate termination of the supply plug in the case of plug connected equipment.
Omitting or disconnecting the equipment earth may cause a safety hazard.
The recommended minimum earth wire size is 2.5mm², unless otherwise stated in the
technical data section of the product documentation.
When the protective (earth) conductor terminal (PCT) is also used to terminate cable
screens, etc., it is essential that the integrity of the protective (earth) conductor is checked
after the addition or removal of such functional earth connections.
For M4 stud PCTs the integrity of the protective (earth) connection should be ensured by use
of a locknut or similar."
Before energising the equipment, the following should be checked:
• Voltage rating and polarity;
• CT circuit rating and integrity of connections;
• Integrity of earth connection (where applicable)

Note: The term earth used throughout the product documentation is the direct equivalent of
the North American term ground.
Equipment operating conditions
The equipment should be operated within the specified electrical and environmental limits.
Current transformer circuits
Do not open the secondary circuit of a live CT since the high level voltage produced may be
lethal to personnel and could damage insulation.
Insulation and dielectric strength testing

Insulation testing may leave capacitors charged up to a hazardous voltage. At the end of
each part of the test, the voltage should be gradually reduced to zero, to discharge
capacitors, before the test leads are disconnected.
Insertion of modules and boards
These must not be inserted into or withdrawn from equipment whist it is energised since this
may result in damage.
Fibre optic communication
Where fibre optic communication devices are fitted, these should not be viewed directly.
Optical power meters should be used to determine the operation or signal level of the device.
3. DECOMMISSIONING AND DISPOSAL

Decommissioning:
The auxiliary supply circuit in the MiCOM computers may include capacitors across the
supply or to earth. To avoid electric shock or energy hazards, after completely isolating the
supplies to the MiCOM computers (both poles of any dc supply), the capacitors should be
safely discharged via the external terminals prior to decommissioning.
Disposal:
It is recommended that incineration and disposal to watercourses be avoided. The product
should be disposed of in a safe manner. Any products containing batteries should have them
removed before disposal, in order to avoid short circuits. Particular regulations within the
country of operation may apply to the disposal of lithium batteries.
4. TECHNICAL SPECIFICATIONS FOR SAFETY

The recommended maximum rating of the external protective fuse for this equipment is 16A,
High rupture capacity (HRC) Red Spot type NIT or TIA, or equivalent unless otherwise
stated in the technical data section of the product documentation. The protective fuse should
be located as close to the unit as possible.
1. Fuse rating is dependent of auxiliary voltage and circuit loading.
2. Differential protective switch on DC power supply is recommended.
3. Differential protective switch on AC power supply is mandatory (printers, PACiS
workstation…).
Protective class: IEC 60255-27: 2005 Class I This equipment requires

a protective (safety)
earth connection to
ensure user safety.
Installation IEC 60255-27: 2005 Installation Category III
Category:
EN 60255-27: 2006 Distribution level, fixed
installation.
Equipment in this
category is qualification
tested at 5kV peak,
1.2/50μs, 500Ω. 0.5J,
between all supply
circuits and earth and
also between
independent circuits.
Environment: IEC 60255-27: 2005 Compliance is
demonstrated by
Pollution degree 2
reference to safety
EN 60255-27: 2006 standards.
Product Safety: 73/23/EEC Compliance with the

European Commission
Low Voltage Directive.
5. 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.
More information on safe working procedures for all electronic equipment can be found in
IEC 60147-0F and BS5783.
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.
Schneider Electric strongly recommends that detailed investigations on the electronic
circuitry, or modification work, should be carried out in a Special Handling Area such as
described in IEC 60147-0F or BS5783.
6. PACKING AND UNPACKING

All MiCOM C264/C264C computers are packaged separately in their own cartons and
shipped inside outer packaging. Use special care when opening the cartons and unpacking
the device, and do not use force. In addition, make sure to remove from the inside carton the
supporting documents supplied with each individual device and the type identification label.
The design revision level of each module included with the device in its as-delivered
condition can be determined from the list of components. This list should be carefully saved.
After unpacking the device, inspect it visually to make sure it is in proper mechanical
condition.
If the MiCOM C264/C264C computer needs to be shipped, both inner and outer packaging
must be used. If the original packaging is no longer available, make sure that packaging
conforms to ISO 2248 specifications for a drop height ≤0.8m.
7. 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.
8. COPYRIGHTS & TRADEMARKS

8.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.
8.2 Trademarks
PACiS, PACiS SCE, PACiS ES, PACiS CMT, PACiS SMT, PACiS PS, and PACiS SCE are
trademarks of Schneider Electric. Product and company names mentioned herein are
trademarks or trade names of their respective companies.
9. 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 customised 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.
MiCOM C264P
INTRODUCTION
TABLE OF CONTENTS
1. INTRODUCTION TO MiCOM 3
2. INTRODUCTION TO MiCOM GUIDES 4

2.1 Chapters description 4
2.1.1 Chapter Safety (SA) 4
2.1.2 Chapter Introduction (IT) 4
2.1.3 Chapter Technical Data (TD) 4
2.1.4 Chapter Functional Description (FT) 4
2.1.5 Chapter Hardware Description (HW) 4
2.1.6 Chapter Connection diagrams (CO) 4
2.1.7 Chapter HMI, Local control and user interface (HI) 4
2.1.8 Chapter Installation (IN) 4
2.1.9 Chapter Settings (ST) 4
2.1.10 Chapter Communications (CT) 5
2.1.11 Chapter Commissioning (CM) 5
2.1.12 Chapter Record Sheet (RS) 5
2.1.13 Chapter Maintenance, Fault finding, Repairs (MF) 5
2.1.14 Chapter Lexicon (LX) 5
2.1.15 Chapter Applications (AP) 5
2.1.16 Chapter Current transformer technical Data (CD) 5
2.1.17 Annex (AN) 5
2.2 Operation guide 5
2.3 Technical guide 5
3. INTRODUCTION TO MiCOM APPLICATIONS 6

3.1 MiCOM Computers 6
3.2 Applications and Scope 6
C264P/EN IT/C80 Introduction
BLANK PAGE
1. INTRODUCTION TO MiCOM
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
behaviour of the power system using disturbance and fault records. They can also provide
measurements of the system at regular intervals to a control centre 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.
For up-to-date information on any MiCOM product, visit our website:
www.schneider-electric.com
2. INTRODUCTION TO MiCOM GUIDES

The guides provide a functional and technical description of the MiCOM C264/C264C
computers and a comprehensive set of instructions for the computer’s use and application.
MiCOM guides are divided into two volumes, as follows:
Operation Guide: includes information on the application of the computers and a technical
description of its features. It is mainly intended for protection & control engineers concerned
with the selection and application of the computers for the Control, Monitoring, Measurement
and Automation of electrical power processes.
Technical Guide: contains information on the installation and commissioning of the
computer, and also a section on fault finding. This volume is intended for site engineers who
are responsible for the installation, commissioning and maintenance of the MiCOM
C264/C264C computer.
2.1 Chapters description
2.1.1 Chapter Safety (SA)
This chapter contains the safety instructions, handling and reception of electronic equipment,
packing and unpacking parts, Copyrights and Trademarks.
Chapters on product definition and characteristics
2.1.2 Chapter Introduction (IT)
This is this document containing the description of each chapter of the MiCOM computer
guides. It is a brief introduction to MiCOM computer capabilities.
2.1.3 Chapter Technical Data (TD)
This chapter contains the technical data including, accuracy limits, recommended operating
conditions, ratings and performance data.
It also describes environment specification, compliance with technical standards.
2.1.4 Chapter Functional Description (FT)
This chapter contains a description of the product. It describes functions of the MiCOM
computer.
2.1.5 Chapter Hardware Description (HW)
This chapter contains the hardware product description (product identification, case,
electronic boards, operator interface, etc.).
2.1.6 Chapter Connection diagrams (CO)
This chapter contains the external wiring connections to the C264/C264C computers.
2.1.7 Chapter HMI, Local control and user interface (HI)
This chapter contains the operator interface description, Menu tree organisation and
navigation, LEDs description, Setting/configuration software.
Set of chapter upon Computer installation
2.1.8 Chapter Installation (IN)
This chapter contains the installation procedures.
2.1.9 Chapter Settings (ST)
This chapter contains the list of the setting with default values and range.
2.1.10 Chapter Communications (CT)

This chapter provides the companion standard of all supported protocols toward SCADA
(Telecontrol BUS) and IED on LBUS. This is the list of protocol function that computer use in
this communication.
User minimal actions
2.1.11 Chapter Commissioning (CM)
This chapter contains instructions on how to commission the computer, comprising checks
on the settings and functionality of the computer.
2.1.12 Chapter Record Sheet (RS)
This chapter contains record sheet to follow the maintenance of the computer.
2.1.13 Chapter Maintenance, Fault finding, Repairs (MF)
This chapter advises on how to recognise failure modes, fault codes and describes the
recommended actions to repair.
2.1.14 Chapter Lexicon (LX)
This chapter contains lexical description of acronyms and definitions.
2.1.15 Chapter Applications (AP)
Comprehensive and detailed description of the features of the MiCOM C264/264C including
both the computer elements and the other functions such as transducerless (CT/VT)
measurements, events and disturbance recording, interlocking and programmable scheme
logic. This chapter includes a description of common power system applications of the
MiCOM C264/C264C computer, practical examples of how to do some basic functions,
suitable settings, some typical worked examples and how to apply the settings to the
computer.
2.1.16 Chapter Current transformer technical Data (CD)
This chapter helps you select a current transformer.
2.1.17 Annex (AN)
This chapter contains instructions on how to set the networks.
2.2 Operation guide
This guide contains the following chapters:
SA, IT, TD, FT, HI, AP, LX.
2.3 Technical guide
This guide contains the following chapters:
SA, IT, TD, FT, HW, CO, IN, ST, CT, CM, RS, MF, CD, LX, AN.
3. INTRODUCTION TO MiCOM APPLICATIONS

Schneider Electric philosophy is to provide a range of computers, gateways and IEDs
products. Each of these products can be used independently, or can be integrated to form a
PACiS system, a Digital Control System (DCS) or a SCADA system.
3.1 MiCOM 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 products, MiCOM C264 specifically for the power
process environment and electric utility industry. It allows building a personalised solution for
Control, Monitoring, Measurement and Automation of electrical processes.
MiCOM C264/C264C 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 PACiS
capabilities to track customer requirements.
Key features are that this computer family is based on a Ethernet client/server architecture,
its 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.
3.2 Applications and Scope
The MiCOM C264/C264C modular bay controller, RTU or PLC is used to control and monitor
switchbays. The information capacity of the MiCOM C264/C264C 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 PACiS System
Configurator Editor (PACiS SCE).
The MiCOM C264/C264C can be connected to a higher control level, local control level or
lower levels by way of a built-in communications interface.
C264C WEB access

SCADA Interface
DNP3 & IEC 60870-5-101
& IEC 60870-5-104
Master clock
(GPS)
Operator
Interface
HV FEEDER BAY
Fast Ethernet
IEC 61850
C264
C264C
Main protection
EHV FEEDER BAY
I/Os
C264
I/Os
MV FEEDER BAYS
COMMON BAY
Cubicle/ Switchboard MV FEEDER BAYS

TRANSFORMER BAY integration
C0001ENc
FIGURE 1 : TYPICAL USE OF A MiCOM C264 – BAY CONTROLLER
PSTN or Remote
SCADA Interface
dedicated HMI
DNP3 & IEC 60870-5-101
line
& IEC 60870-5-104
Px30
Px40
NP3,
DBUS,
M720 IE 0-5-103,
I 870-5-101
Px20
Px30
PLC
BC
I/Os
I/Os
C0002ENb
FIGURE 2 : TYPICAL USE OF A MiCOM C264 – STANDALONE APPLICATION

The figures show some typical cases that can be mixed to face specific constraints. Two
examples can illustrate this case:
• The system application on “figure 1” uses several C264 linked together on SBUS
Ethernet. A gateway grants access to a SCADA.
• Standalone application use one C264 linked to IEDs and possibly to a remote SCADA.
BLANK PAGE
MiCOM C264P
TECHNICAL DATA
CONTENT
1. SCOPE OF THE DOCUMENT 3
2. CONFORMITY 4
3. GENERAL DATA 5
3.1 Design 5
3.2 Installation Position 5
3.3 Degree of Protection 5
3.4 Weight 5
3.5 Dimensions and Connections 5
3.6 MICOM C264 Computer: Configuration 5
3.7 C264 Technical Data 8
3.7.1 C264: Element limits 8
3.8 Terminals 9
3.9 Creepage Distances and Clearances 10
4. RATINGS 11
4.1 Auxiliary Voltage 11
4.2 Power Supply 11
4.2.1 BIU241 Digital Outputs 11
4.2.2 BIU261 Dual Sources power supply board 11
4.3 Circuit breaker Control Unit (CCU) Digital Inputs 13
4.3.1 CCU200 Digital Inputs 13
4.3.2 CCU211 Digital Inputs 13
4.4 Circuit breaker Control Unit (CCU) Digital Outputs 14
4.4.1 CCU200 Digital Outputs 14
4.4.2 CCU211 Digital Output 14
4.5 Digital Input Unit (DIU) Digital Inputs 16
4.5.1 DIU200 Digital Inputs 16
4.5.2 DIU211 Digital Inputs 17
4.6 Digital Output Unit (DOU) Digital Outputs 18
4.6.1 DOU201 Digital Output 18
4.7 Analogue Input Unit (AIU) Analogue Inputs 19
4.7.1 AIU201 Analogue Input 19
4.7.2 AIU211 Analogue Input 20
4.8 Protection CT/VT inputs 21
4.8.1 TMU210 – Current Transformers (CT) 21
4.8.2 TMU210 – Voltage Transformers (VT) 22
4.8.3 TMU210 - A/D Converter 22
4.9 Analogue Output Unit (AOU) 23
C264P/EN TD/C80 Technical Data
4.9.1 AOU200 Analogue Outputs 23
5. BURDENS 25
5.1 Auxiliary Voltage 25
5.2 Power Supply 25
5.3 CPU Boards 25
5.4 Circuit breaker Control Units (CCU) Input Burdens 26
5.4.1 CCU200 Input Burden 26
5.4.2 CCU211 Input Burden 26
5.5 Digital Input Unit (DIU) Input Burden 26
5.5.1 DIU200 Input Burden 26
5.5.2 DIU211 Input Burden 27
5.6 Digital Output Unit (DOU) Input Burden 27
5.6.1 DOU201 Input Burden 27
5.7 Analogue Input Unit (AIU) Input Burden 28
5.7.1 AIU201 Input Burden 28
5.7.2 AIU211 Input Burden 28
5.8 Transducerless Measurement Unit (TMU) Input Burden 28
5.9 Analogue Output Unit (AOU) Input Burden 28
5.9.1 AOU200 Input Burden 28
5.10 Ethernet Switches Board Input Burden 28
5.11 Front Panel Board Input Burden 28
6. ACCURACY 29
6.1 Reference Conditions 29
6.2 Measurement Accuracy 29
7. TYPE TESTS 30
7.1 Dielectric Strength Tests 30
7.1.1 AIU211 – Dielectric Strength Test 30
7.1.2 ECU200/ECU201 – Dielectric Strength Test 30
7.1.3 MiCOM C264 and C264C – Dielectric Strength Test 30
7.2 Mechanical Test 31
7.3 Atmospheric Test 32
7.4 DC Auxiliary Supply Test 32
7.5 AC Auxiliary Supply Test 33
7.6 Electromagnetic Compatibility (EMC) Tests 33
1. SCOPE OF THE DOCUMENT

This document is a chapter of the MiCOM C264P documentation, describing the Technical
data of this computer.
2. CONFORMITY
(Per Article 10 of EC Directive 72/73/EC).
The product designated “MiCOM C264P computer” has been designed and manufactured in
conformance with the European standards EN 60255-6 and EN 61010-1 and with the ‘EMC
Directive’ and the ‘Low Voltage Directive’ issued by the Council of the European Community.
3. GENERAL DATA
3.1 Design
Surface-mounted case suitable for wall installation or flush-mounted case for 19” cabinets
and for control panels.
3.2 Installation Position
Vertical ±15°
3.3 Degree of Protection
In agreement with DIN VDE 0470 and EN 60255-27:2006, or with IEC 60255-27:2005:
• IP52 for the front panel with LCD or LEDs
• IP10 for the “blind” front panel (GHU220,GHU221)
• IP50 for the body case of MiCOM C264C
• IP20 for the rack of MiCOM C264
• IP20 for rear panels of C264/C264C, except reduced to IP10 when the black MiDOS
28-pin terminal block is installed for the TMU board.
3.4 Weight
Case 40 TE: approximately 4 kg
Case 80 TE: approximately 8 kg
3.5 Dimensions and Connections
Please refer to the dimensional drawings (C264_EN_HW, hardware description chapter) and
to the terminal connection diagrams (C264_EN_CO).
3.6 MICOM C264 Computer: Configuration
The MiCOM C264 computer includes:
• A case
• A rack with slots for computer boards
• Some combination of the computer boards installed in the slots

There are many types of MICOM C264 computers. Each MICOM C264 computer has a
specific purpose and includes some combination of boards to achieve that purpose:
• C264 with an 80TE case
• C264C with a compact 40TE case

80TE Computer – Board installation

Board Slots (View when you look at the back of the computer) Max nb
Q P O N M L K J I H G F E D C B A
BIU24x X 1
CPU 270 X 1
CCU200 (1) X X X X X X X X X X X X X ≤ 12
CCU211 (1) X X X X X X X X X X X X X ≤ 12
DIU200 X X X X X X X X X X X X X X X ≤ 12
DIU211 X X X X X X X X X X X X X X X ≤ 12
DOU201 X X X X X X X X X X X X X X X ≤ 12
AIU201 X X X X X X X ≤7
AIU211 X X X X X X X ≤7
TMU210 (1) X 1
AOU200 X X X X X X X X X X X X X X X ≤4
SWU20x X ≤1
SWR2xx X ≤1
SWD2xx X ≤1
GHU2A1 (3) 1
40TE Computer – Board installation

Board Slots (View when you look at the back of the computer) Max nb
H G F E D C B A
BIU24x X 1
CPU 270 X 1
CCU200 (1) X X X ≤3
CCU211 (1) X X X ≤3
DIU200 X X X X ≤3
DIU211 X X X X ≤3
DOU201 X X X X ≤3
AIU201 X X X X ≤3
AIU211 X X X X ≤3
TMU210 (1) X=1 1
AOU200 X X X X ≤3
SWU20x X X ≤1
SWR2xx X X ≤1
SWD2xx X X ≤1
GHU2A0 (3) 1
(1)
Do not install the CCU in slot P and do not install the CCU in the slot adjacent to the TMU.
(3)
A = 0: Has LCD A=1: Has no LCD A= 2: Has remote LCD
80TE Computer – Signals

Board Signals Max nb
AI AO DI DO CT VT
BIU24x 2 2
CPU 270
CCU200 8 4 13: 104 DI + 52 DO
CCU211 8 4 13: 104 DI + 52 DO
DIU200 16 14: 224 DI
DIU211 16 14: 224 DI
DOU201 10 14: 140 DO
AIU201 4 6: 24 AI
AIU211 8 6: 48 AI
TMU210 8 4 4 1: 4 CT, 4 VT
AOU200 4 6: 24 AO
SWU20x
SWR2xx
SWD2xx
GHU2A1
40TE Computer – Signals

Board Signals Max nb
AI AO DI DO CT VT
BIU24x 2 2
CPU 270
CCU200 8 4 3: 24 DI + 12 DO
CCU211 8 4 3: 24 DI + 12 DO
DIU200 16 4: 64 DI
DIU211 16 4: 64 DI
DOU201 10 4: 40 DO
AIU201 4 4: 16 AI
AIU211 8 4: 32 AI
TMU210 8 4 4 1: 4 CT, 4 VT
AOU200 4 4: 16 AO
SWU20x
SWR2xx
SWD2xx
GHU2A1
3.7 C264 Technical Data

CAUTION: THE FILL PERFORMANCE OF THE C264 IS LESS THAN THE SUM OF
THE PERFORMANCES FOR EACH COMPONENT. FOR A DETAILED
PERORMANCE CHECK? PLEASE CONTACT US.
3.7.1 C264: Element limits
Element Limits for 1 of C264 with

extensions
Number of IEC61850 servers for a C264 client 32
Number of IEC61850 clients for a C264 server 16
GOOSE size (IEC61850) 128 binary inputs
64 measurements
Measurements / Wired MV 2400 / 48
Receiving flux of MV 200 values / sec
T104 server protocols 4
With as many as 4 clients,
only 1 is active at one time
T101 protocol 2
With 1 client managed by each
MODBUS protocol 2
With 1 client managed by each
PSL:
Number of items NOTE 1 256
Number of elements NOTE 2 256
FBD:
. Number of accurate timers 12
. Overall number of timers (configurated timers) 100
Printers at C264 level 1 (only on rear RS port)
Serial Communication port (for SCADA and/or legacy protocols) 4
SCADA protocols Serial/Ethernet: 2
Ethernet IEC104, T104: 4
Master legacy protocols (for IED communication) 4
IEDs allowed for each Legacy Bus 16 with a max of 32 per C264
Voltage level 2 per C264 if ATCC used
Bays 128
A maximum of 12 bays show on
the local HMI
Circuit breakers 128
Disconnectors 512
Transformers 128
Maximum managed datapoints 4 000
Digital Input Points / Wired DI / System DI 5600 / 240 / 100
Output Control Points / Wired DO 1 200 / 150
Tap Position Indication 128
Counters / Wired 128 / 8
Setpoint (digital / analyse) 256
ISaGRAF TPI 128
CO 256
SP 256
CT 512
MPS 512
MV 512
SPS/DPS 512
Equation 200
Time discrimination and tagging of events 1 ms
Input bandwidth 100 alarms/s
100 events/s
Fast waveform (disturbance) file storage capacity 480 cycles for 8 analogue values
+ 128 logical status
32 samples/period
3.8 Terminals
PC Maintenance Interface:
• DIN 41652 connector, type female D-Sub, 9-pin, installed on the front panel
• A direct wired cable is required.

Ethernet LAN (installed on the CPU260 board):
• RJ-45 female connector, 8-pin for the 10/100Base-T self-negotiation
• ST female connector for the 100Base-F.

Ethernet LAN (installed on the CPU270 board):
• Two of the RJ-45 female connector, 8-pin for the 10/100Base-T self-negotiation
The IRIG-B interface (standard NF S 87-500, May 1987), installed on the CPU260/270
board:
• BNC plug
• Modulated amplitude, 1 kHz carrier signal
• Time-of-year code: BCD
• Compatible with IRIG B122 code.

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 CPU260/270? board.
• Optical fibres through ECU200 (external RS232/optical converter): optical plastic fibre
connection in agreement with IEC 874-2 or DIN 47258 or ST ® glass fibre optic
connection (ST ® is a registered trademark of AT&T Lightguide Cable Connectors).
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:
− AIU201, AIU211
− AOU200
− BIU241
− CCU200, CCU211
− DIU200, DIU211
− DOU201
− DSP210
• The I/O boards and BIU241 include a 24-pin, 5.08 mm pitch male-connector.
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.

3.9 Creepage Distances and Clearances

Per EN 61010-1 and IEC 664-1.
Pollution degree 3, working voltage 250 V.
Overvoltage category III, impulse test voltage 5 kV.
4. RATINGS
4.1 Auxiliary Voltage
The C264 computer is available in four auxiliary voltage versions, as follows:
Version Nominal ranges Operative DC range Operative AC range

A01 24VDC 19.2 thru 28.8VDC -
A02 48 thru 60VDC 38.4 thru 72VDC -
A03 110 thru 125VDC 88 thru 150VDC -
A04 220VDC and 230VDC 176 thru 264VDC 176 thru 264VAC
The nominal frequency (Fn) for the AC auxiliary voltage is dual rated at 50/60Hz, the operate
range is 45Hz to 65Hz.
The BIU241 board includes these attributes:
• Inrush current : 6.2A at 125VDC during the first 50 ms at startup
• Power supply: 40 W
• Nominal output voltage: + 5V
• Supply monitoring
• Permitted power outage: 50 ms
• Protection against polarity reversal
• Insulation resistance: >100 MΩ ( CM) at 500 VDC
• Dielectric strength: 2 kV (CM) – 50 Hz for 1 minute

4.2 Power Supply
4.2.1 BIU241 Digital Outputs
On the BIU241 board, the attributes of the Watchdog Relay Contacts are the same as the
attributes for the NO+NC contacts installed on the DOU201 board.
On the BIU241 board, the attributes of the two output relays used for C264 redundancy are
the same as for the single-pole output-relay installed on the DOU201 board.
4.2.2 BIU261 Dual Sources power supply board
The BIU261 allows a dual source power supply from the same voltage range.
Voltage source switching sequence
The BIU261 has a voltage source switching mechanism.
Switch from main source to secondary Source: If the main power supply source disappears
(1), the secondary power supply source is supplied to C264.
Switch from secondary source to main Source: When the main power supply source
becomes available and stable the switch from secondary to main power supply source is
effective and C264 running without fugitive power supply fault.
Switching transition is logged.
(1) The board is equipped with a circuit to start / stop switching sequence. This circuit is
enabled to use the power supply if Voltage is above threshold. The absence of power supply
source voltage is considered when Usource < 80% Unominal. This thresthold is a factory
value.
Limitation
• The board contains the Port 2 only. The communication port 2 remains the same as
the BIU241.
• The board has been design to support two voltage ranges, direct current only:
Case Power supply range

A02 48VDC 60VDC
A03 110VDC 125VDC
Performances
• Switching lead time from Main source to Secondary source: 20 ms max.
• Switching lead time from Secondary source to Main source: 20 ms max.
• The board is protected against polarity reversal.

Voltage insulation between Main & Secondary power supply source : 2500 V Rms.
4.3 Circuit breaker Control Unit (CCU) Digital Inputs

4.3.1 CCU200 Digital Inputs
For the CCU200 board, for the versions A01 to A04, the eight inputs have the same
attributes as the inputs for the DIU200 board.
The CCU200 board is available in five nominal voltage versions, as follows:
Same for
Version Nominal voltage (+/-20%) Triggering threshold (VDC)
DIU200
A01 24VDC if V >10.1VDC Input status is set YES
if V < 5VDC Input status is reset
A02 48 thru 60VDC if V >17.4VDC Input status is set YES
if V < 13.5VDC Input status is reset
A03 110 thru 125VDC if V > 50VDC Input status is set YES
if V< 34.4VDC Input status is reset
A04 220VDC if V > 108VDC Input status is set YES
if V< 63VDC Input status is reset
A07 110 thru 125VDC if V > 86VDC input status is set NO
if V < 67VDC input status is reset
For more installation data about this board, please refer to the topic, MiCOM 264 Computer:
Configuration.
4.3.2 CCU211 Digital Inputs
There are six versions of the CCU211 board, as follows:

A01 24VDC if V >10VDC Input status is set
A02 48 thru 60VDC if V >17.4VDC Input status is set
A03 110 thru 125VDC if V > 50VDC Input status is set
A04 or 220VDC or if V > 86VDC Input status is set
A07 110 thru 125VDC (with 80%
Threshold)
A08 220VDC (with 80% if V > 176VDC Input status is set
Threshold) if V < 132VDC Input status is reset
Configuration.
4.4 Circuit breaker Control Unit (CCU) Digital Outputs

4.4.1 CCU200 Digital Outputs
Each relay of the CCU board has double pole contacts. To get the attributes described
below, you must wire the two output contacts of each relay in series.
In the table that follows, the Break attribute shows in two cases:
• You use each of the output contacts separately
• You wire the two output contacts of each relay in serial. In this event, you make the
best use of the Break function for each relay..
On the CCU200 board, the details of the 4 Output Relay Contacts show in the table that
follows:
Description Values
Nominal operating voltage range 24 thru 250VDC / 230VAC
Make 5A
Carry 5A continuously
30A for 500 ms or 250A for 30 ms
Break (Output contacts used DC: 50 W resistive, 30 W inductive (L/R = 40 ms)
separately)
AC: 1250 VA resistive, 1250 VA inductive (cos ϕ = 0,7)
In these conditions, the contact resistance is still lower
than 250 mΩ for 10000 operations
Break (Output contacts wired in DC: 80 W resistive for current lower than 1A,
serial) 100W resistive for current upper than 1A,
30 W inductive (L/R = 40 ms)
AC: 1250 VA resistive, 1250 VA inductive (cos ϕ = 0,7)

Operating time Break < 7 ms
Double pole contacts Normally open
• Dielectric strength of the coil contacts: 5000Vrms
• Dielectric strength of adjacent contacts: 2500Vrms.
• Isolation: 2 kV (CM) at 50 Hz for 1 minute
• The board is designed and monitored to prevent an uncommanded event.

Configuration.
4.4.2 CCU211 Digital Output
For the CCU211 board, the Digital Output (DO) attributes include:
• 4 double-pole switch-relays with normally open (NO) contacts
• 1 common +ve and 1 common -ve contact for 2 relays
• A self-monitoring device for the output control chain: address check, state monitoring
• The +5V voltage is monitored to prevent an uncommanded event.
• You can configure the digital outputs only in the double remote signalling
configuration.
• Dielectric strength of the coil contacts: 5000Vrms

• Dielectric strength of adjacent contacts: 2500Vrms.
• The board is designed and monitored to prevent an uncommanded event.

Configuration.
In the table that follows, the Break attribute shows in two cases:
• You use each of the output contacts separately
• You wire the two output contacts of each relay in serial. In this event, you make the
best use of the Break function for each relay.
For more details, please refer to the table that follows.
Description Values
Nominal operating voltage range 24 thru 250VDC / 230VAC
Make 5A
30A for 500 ms or 250A for 30 ms
Break (output contact used DC: 50 W resistive, 30 W inductive (L/R = 40 ms)
separately)
AC: 1250 VA resistive, 1250 VA inductive (cos ϕ = 0.7)
Break (Output contacts wired in DC: 80 W resistive for current lower than 1A,
serial) 100W resistive for current upper than 1A,
30 W inductive (L/R = 40 ms)

Double pole contacts Normally open
4.5 Digital Input Unit (DIU) Digital Inputs

4.5.1 DIU200 Digital Inputs
The DIU200 board has 16 digital inputs and is available in four nominal voltage versions, as
follows:

A01 24 VDC if V >10.1 VDC Input status is set
if V < 5 VDC Input status is reset
A02 48 thru 60 VDC if V >17.4 VDC Input status is set
if V < 13.5 VDC Input status is reset
A03 110 thru 125 VDC if V > 50 VDC Input status is set
if V< 34.4 VDC Input status is reset
A04 220 VDC if V > 108 VDC Input status is set
if V< 63 VDC Input status is reset
Configuration.
4.5.2 DIU211 Digital Inputs

In the C264 rack, the DIU211 board replaces a DIU200 board. External connections are the
same as the ones on the previous boards.
The DIU211 board includes 16 opto-isolated digital-inputs, with one common for two inputs.
There are six versions of the DIU211 board, as follows:

A01 24VDC if V >10VDC Input status is set
A02 48 to 60VDC if V >17.4VDC Input status is set
A03 110 to 125VDC if V > 50VDC Input status is set
A04 or 220VDC or if V >86VDC Input status is set
A07 110 to 125VDC (with 80% Threshold)
A08 220 VDC (with 80% Threshold) if V > 176VDC Input status is set
The inputs are suitable for use on systems with nominal battery voltages from 24Vd.c. to
220Vd.c (+/- 20%). The input responds to negative input voltages. The inputs are not self-
controlled. The threshold voltage depends on the selection of the voltage range :
Nominal voltage (+/-20%) Threshold (VDC)

24VDC 15V (drop off) -19V (pick up)
48 to 60VDC 15V (drop off) -19V (pick up)
110 to 125VDC 35V (drop off) -52V (pick up)
220VDC 65V (drop off) -106V (pick up)
For CPU2 and CPU3, use jumpers to select the nominal voltage.
For use with CPU 2 board, use a four-position header and jumper to select the address of
the board.
For use with CPU 3 board, the location of the DIU211 in the C264 rack defines the address
of the board. If you use the DIU211 as a spare of a previous board, you can use the jumper
to define the address of the board. Use the PACiS tool, System Configuration Editor (SCE)
to define this location.
For an input voltage from the threshold value to 18V, the input current is 30mA. The voltage
applied to the input terminals, with amplitude of between 19,2VDC and 264VDC powers the
pulse generation circuit. The circuit drives a pulse of current with amplitude of 30mA. The
pulse duration is between 1ms and 2ms.
To reduce thermal dissipation, especially at high input voltages, the inputs draw a current of
less than 1.6 mA.
For details about the input burdens, please refer to the topic DIU211 Input Burden in this
chapter.
Configuration.
4.6 Digital Output Unit (DOU) Digital Outputs

4.6.1 DOU201 Digital Output
The DOU201 board gives you:
• 10 insulated digital outputs (with relays)
• 8 single pole relays with one normally open (NO) contact
• 2 single pole relays with 1 common for 2 outputs (NO/NC).

For more details of the DOU201 board, please refer to the table that follows:
Description Values
Nominal operating voltage range 24 thru 250VDC / 230 VAC
Make 5A
30A for 500 ms or 250 A for 30 ms
Break DC: 50 W resistive, 15 W inductive (L/R = 40 ms)
than 250 m for 10000 operations
8 simple pole contacts Normally open
2 double pole contacts 1 Normally open +1 Normally close
For use with CPU 2 board, use a four-position header and jumper to select the address of
the board.
For use with CPU 3 board, the location of the DOU201 in the C264 rack defines the address
of the board. If you use the DOU201 as a spare of a previous board, you can use the jumper
to define the address of the board. Use the PACiS tool, System Configuration Editor (SCE)
to define this location.
Dielectric strength of the coil contacts: 5000Vrms.
Configuration
4.7 Analogue Input Unit (AIU) Analogue Inputs

4.7.1 AIU201 Analogue Input
The AIU201 board provides 4 independent analogue inputs (AI). You can set each AI input
current range or input voltage range as shown in the table that follows:
Type Ranges
Current input range ±1mA
±5 mA
±10 mA
±20 mA
+ 4mA thru +20mA
Voltage input range ± 1,25V
±2,5V
±5V
± 10V
Sampling period 100 ms
Accuracy 0,1% full scale at 25°C
AD conversion 16 bits (15bits+sign bit)
Common mode rejection ratio (CMMR) > 100dB
Serial mode rejection ratio (SMMR) > 40dB
Range of Gain: user-selectable 1, 2, 4, 16
Input impedance for voltage inputs 11 KΩ
Input impedance for current inputs 75 Ω
Temperature drift: as much as 30ppm/°C.

You can set the ranges during the configuration phase.
To select the current or voltage, choose the input number of the connector.
Configuration.
4.7.2 AIU211 Analogue Input

Transducers deliver the DC current signals to the AIU211 board. The AIU211 board provides
8 insulated analogue input values on 8 independent galvanic-isolated channels. This means
that there is no common point of contact between two analogue inputs.
You can configure each analogue input in the current range or voltage range as shown in the
table that follows:
Type Ranges
Current input range ±1mA
±5 mA
±10 mA
±20 mA
+ 4mA thru +20mA
Sampling period 100 ms
Accuracy 0,1% full scale for each range at 25°C
AD conversion 16 bits (15 bits+sign bit)
Common mode rejection ratio (CMMR) > 100dB
50Hz, 60Hz
Serial mode rejection ratio (SMMR) > 40dB
Input impedance for current inputs 75 Ω
Temperature drift: as much as 30ppm/°C between 0°C and 70°C

You can set the ranges during the configuration phase.
To select the current range or the voltage range, choose the input number of the connector.
The AIU211 board is dedicated to replace the AIU210 Board: the interface on the internal
Bus is compatible with the AIU210.
Configuration.
4.8 Protection CT/VT inputs

4.8.1 TMU210 – Current Transformers (CT)
On the terminal block, there are two available nominal currents: 1A and 5A. Each has
different attributes. Use jumpers to set the 1A or 5A nominal current.
The current measurement inputs to each of the 4 Current Transformers (CT) include the
attributes that follow:
Operating range
Description
1A 5A
Nominal AC current (In) 1Arms 5Arms
Minimum measurable current with same accuracy 0.1 A r m s 0.5 A r m s
Maximum measurable current 40 A r m s (4*In) 200 A r m s (4*In)
Frequency 50 or 60 Hz ± 10% 50 or 60 Hz ± 10%
Values
Pass band 10th harmonic
Current threshold accuracy 2%
Compatibility with external transformer 5VA 5P10
In addition, and specific for the 3 phase current inputs for each CT:
Operating range
Description
1A 5A
3 phase current inputs 1A 5A
Power consumption < 0.05 VA < 1,25 VA
Values
Operating range 0.1 thru 40 In
Thermal heating 100 In during 1 second
30 In during 10 seconds
4 In permanent
In addition, and specific for the 1 earth current input for each CT:
Operating range
Description
1A 5A
1 earth current inputs 1A 5A
Power consumption < 0.008 VA at 0.1Ion < 0.175 VA at 0.1Ion
Values
Operating range 0.01 thru 8 Ion
2 other possibilities by cortec code:
0.002 thru 1 Ion or 0.1 thru 40 Ion
Thermal heating 100 Ion during 1 second
30 Ion during 10 seconds
4 Ion permanent
TMU210 CT load rating:
Strength
Duration
1A 5A
3 seconds: not measurable, with no destruction 30 A r m s (30*In) 150 A r m s (30*In)
1 second: not measurable, with no destruction 100 A r m s (100*In) 500 A r m s (100*In)
4.8.2 TMU210 – Voltage Transformers (VT)

The 3 or 4 phase voltage measurement inputs to each of the 4 Voltage Transformers (VT)
include the attributes that follow:
Description Values
Power consumption < 0.5 VA at 130V
Vn range 57V thru 130V
Other possibility by cortec code:
220V thru 480V
Thermal heating 2 Vn phase-neutral permanent, and
2.6 Vn phase-neutral during 10 seconds
Pass band 10th harmonic

Voltage threshold accuracy 2%
• Connection option by setting:

For 3 phase voltage input:
3Vpn or 2 Vpn + Vr or 2Vpp + Vr
For 4 phase voltage input:
3Vpn or 3 Vpn + Vr or 2 Vpn + Vr or 3 Vpp + Vr or 2 Vpp + Vr
All voltage and power phase protection are done on Vpp voltage direct measured or derived,
and Vr is direct measured or derived.
4.8.3 TMU210 - A/D Converter
On the TMU210 board, the A/D converter includes the attributes that follow:
Description Values
Width 16 bits
Conversion period < 30 µs
Scanning period 64 samples/period
Linearity error ± 2 LSB
SINAD ratio as much as 1kHz 0db
Low passed filter at 1kHz -40db/decade
4.9 Analogue Output Unit (AOU)

4.9.1 AOU200 Analogue Outputs
The AOU200 board provides 4 analogue current outputs. Each output is related to a Read
Inhibit relay. An external power supply supplies power to the outputs.
The analogue outputs, the relays and the power supply are one isolated group.
The external power supply must supply a regulated voltage of +48V±5% and a power of
10 W for each AOU200 board
Configuration.
For the AOU200 board, the output attributes follow:
Value Maximal Impedance

± 5 mA
4KΩ
(± 20% Ö ± 6mA)
± 10 mA
2KΩ
(± 20% Ö ± 12mA)
± 20 mA
1KΩ
(± 20% Ö ± 24mA)
+ 4 mA thru +20 mA
After calibration, and at 25°C, the precision = 0,1% X (the full scale + 20%). .
Between -10°C and +70°C, the maximum deviation is <100ppm/°C.
100ms after the command, the current output is stable. The management of the AOU200
board with an RI relay shows in Figure 1. When the RI relay is in the closed position, you can
read the value.
AOUx
100 ms
10 ms 10 ms
RI relay
C0287ENa
FIGURE 1: AOU200 BOARD DIAGRAM - SHOWS CURRENT OUTPUT

The WatchDog relay and RI relays include the attributes that show in the table that follows:
Contact type NO
Max operating voltage 250VDC / 230VAC
2,5A continuously
Make and Carry 30A for 500ms
100A for 30ms
Break DC: 50W resistive, 15W inductive
(L/R = 40ms).
AC: 1250 VA resistive,
1250VA inductive (cosϕ = 0,7 – relay
duration is lower)
Operating time < 7ms
Maximum frequency of commutation 360 operations each hour, on nominal load
100 000 operations, on resistive load at
Life Period
250VAC, 8A
5. BURDENS
5.1 Auxiliary Voltage
The MiCOM C264/C264C computer burdens depend on the number of cards installed in the
computer and show in the table that follows:
Version Nominal Maximum

C264C 15W 22W
C264 20W 40W
Nominal
50% of the DI Maximum
Computer Version Case Size Voltage energized and All DI and all relays
one relay per board energized
energized
C264 A01 24VDC 30VADC 39VADC 39WAC 31WAC
C264 A02 48 thru 60VDC 35VADC NA NA 36WAC
C264 A03 C264 (4U – 80TE) 110 thru 125VDC
C264 A04 220VDC and 39VADC NA NA 40WAC
230VAC
C264C A01 24VDC 12VADC 17VADC 17WAC 13WAC

C264C A02 48 thru 60VDC 16VADC 22 VADC 22 WAC 17WAC
C264C A03 C264C (4U – 40TE) 110 thru 125VDC
C264C A04 220VDC and 19VADC 27VADC 27 WAC 20WAC
230VAC
5.2 Power Supply

For the BIU241 board, the input burden on the internal 5V bus is 1,25W. This includes the
watchdog, redundancy relays and communication ports.
The efficiency of the power supply is 78%.
NOTE: During the start of the C264, there is a peak current. During the first
50ms, the peak current can reach 6.2A, as measured on the BIU-A03
board with a source of 125VDC.
5.3 CPU Boards
The CPU270 board manages the Flash and Ram memory in order to allow the C264 to have
more than 16 servers when possible (depending of the size of the data model).
SCE zips data model files for C264 and memorizes zipped data model files in its flash
memory. Whilst launching, AGENCY uncompress data model files one after another in
computer RAM.
5.4 Circuit breaker Control Units (CCU) Input Burdens

5.4.1 CCU200 Input Burden
On the CCU200 board, the input burdens follow:
Version Nominal voltage Current at Un (mA)

A01 24VDC 3.5
A02 48 thru 60VDC 5 for 48VDC
6.8 for 60VDC
A03 110 thru 125VDC 2.5 for 110VDC
3 for 125VDC
A04 220VDC 2
A07 110 thru 125VDC 3.4 for 110VDC
5.4 for 132VDC
The CCU200 board burden on the internal 5V bus is 400mW plus 400mW for each activated
relay.
5.4.2 CCU211 Input Burden

On the CCU211 board, the input burdens follow:
Nominal voltage Current at Un (mA)- after peak

24VDC 2.6 mA
48VDC 2.2 mA
110VDC 1.9 mA
125VDC 1.5 mA
220VDC 1 mA
For the CCU211 board, the input burden on the internal 5V bus is 290mW plus 400mW for
each activated relay.
5.5 Digital Input Unit (DIU) Input Burden

5.5.1 DIU200 Input Burden
On the DIU200 board, the input burdens follow:
Version Nominal voltage Current at Un (mA)

A01 24 VDC 3.5
A02 48 thru 60 VDC 5 for 48 VDC
6.8 for 60 VDC
A03 110 thru 125 VDC 2.5 for 110 VDC
3 for 125 VDC
A04 220 VDC 2
The burden of the DIU200 board on the internal 5V bus is 75mW

5.5.2 DIU211 Input Burden

To reduce thermal dissipation, especially at high input voltage levels, the inputs use less
than 1.6mA.
The DIU211 board includes the input burdens that follow:
Nominal voltage Current at Un (mA)- after peak

24VDC 2.6 mA
48VDC 2.2 mA
110VDC 1.9 mA
125VDC 1.5 mA
220VDC 1 mA
The burden of the DIU211 board on the internal 5V bus is 75mW

From 48VDC to 220VDC voltage, a high current consumption is created on binary inputs
during a short period and circulates through external binary contacts to clean them. Please
refer to the peak current response curve.
IMPORTANT NOTE: For the 24VDC voltage, there is no short peak current because of
the permanent high consumption on inputs >25ma.
35
30
25
Current (mA)
20
15
10
0
0 50 100 150 200 250 300
Tension (V)
C0159ENa
FIGURE 2: PEAK CURRENT RESPONSE CURVE
5.6 Digital Output Unit (DOU) Input Burden

5.6.1 DOU201 Input Burden
For the DOU201 board, the input burden on the internal 5V bus is 250mW plus 200mW for
each activated relay.
5.7 Analogue Input Unit (AIU) Input Burden

5.7.1 AIU201 Input Burden
For the AIU201 board, the input burden on the internal 5V bus is 1 W.
5.7.2 AIU211 Input Burden
For the AIU211 board, the input burden on the internal 5V bus is 1.1 W.
5.8 Transducerless Measurement Unit (TMU) Input Burden
The TMU210 burdens on the internal transformers are specified in the table below:
CT burden (at nominal current – IN) Nominal consumption (VA)

1A <0.02
5A <0.2
VT burden (at nominal voltage – VN ) Nominal consumption (VA)

Vn = 130 Veff <0.1
The TMU210 board burden on the internal 5V bus is 300mW
5.9 Analogue Output Unit (AOU) Input Burden

5.9.1 AOU200 Input Burden
For the AOU200 board, the input burden on the internal 5V bus is 120 mA (maximum).
5.10 Ethernet Switches Board Input Burden

For the SWD202/SWD204 board, the burden on the internal 5V bus is 4W.
For the SWR20x board, the burden on the internal 5V bus is 4 W.
For the SWU20x board, the burden on the internal 5V bus is 3,85W with 2 optical ports.
5.11 Front Panel Board Input Burden

For the GHU200 and GHU210 boards, the input burden on the internal 5V bus is:
• 600mW when the LCD screen is not back-lit
• 3W when the LCD screen is back-lit.

For the GHU201 and GHU211 boards the input burden on the internal 5V bus is 600mW.
For the GHU202 and GHU212 boards, the input burden on the internal 5V bus is <1mW.
6. ACCURACY
For all specified accuracy, the repeatability is ± 2.5% unless otherwise specified.
If no range is specified for the validity of the accuracy, then the specified accuracy shall be
valid over the full setting range.
6.1 Reference Conditions
Quantity Reference conditions Test tolerance

General
Ambient temperature 20 °C ±2 °C
Atmospheric pressure 86kPa to 106kPa -
Relative humidity 45 to 75 % -
Input energising quantity
Current IN ±5%
Voltage VN ±5%
Frequency 50 or 60Hz ±0.5%
Auxiliary supply 24VDC, 48VDC-60VDC, ±5%
110VDC-125VDC,
220VDC
230VAC
6.2 Measurement Accuracy

The TMU210 board has the following characteristics:
Measurement Range Deviation

Phase current 0.1 to 40 In Typical ±0.5% at In
Earth current 0.002 to 1Ion Typical ±0.5% at Ion
0.01 to 8 Ion
0.1 to 40 Ion
Voltage 57 to 260V Typical ±0.5% at Un
220 to 960V
Active Power Reactive Power

Cos Deviation Sin Deviation
0.866 <1.5% 0.866 <3%
0.5 < 3% 0.5 < 1.5%
7. TYPE TESTS
7.1 Dielectric Strength Tests
7.1.1 AIU211 – Dielectric Strength Test
Type Test description Type Test Standard Conditions
Insulation Resistance IEC 60255-5 (2000) 100 MΩ at 500VDC (CM )
Dielectric Strength IEC 60255-5 (2000) 50Hz for 1 minute, 2kV (CM),
IEEE C37.90 (1989)
Impulse Voltage Strength
IEC 60255-5 (2000) 5kV (CM)
for inputs of the AIU211
7.1.2 ECU200/ECU201 – Dielectric Strength Test
Type Test description Type Test Standard Conditions
Insulation Resistance IEC 60255-5 (2000) 100 MΩ at 500 VDC (CM and DM)
(between groups)
7.1.3 MiCOM C264 and C264C – Dielectric Strength Test
Type Test Name Type Test Standard Conditions

Insulation Resistance IEC 60255-5 (2000) 100 MΩ at 500 VDC (CM and DM)
Dielectric Strength IEC 60255-5 (2000) 50 Hz for 1 minute, 2kV (CM), 1kV (DM)
IEEE C37.90 (1989)
High Voltage Impulse IEC 60255-5 (2000) 5 kV CM and 3 kV DM
Test
7.2 Mechanical Test

Free Fall Test IEC 60068-2-31 (1969) 2 falls of 5 cm (Computer not powered)
+ A1 (1982)
Free Fall Packaging
Test IEC 60068-2-32 (1975)
+A1 (1982) + A2 25 falls of 50 cm (Packaged computer)
(1990)
Vibration Response – IEC 60255-21-1 (1988) Class 2:
Powered On
Acceleration: 1g from 10 to 150Hz
Vibration Response – IEC 60255-21-1 (1988) Class 2:
Not Powered On
Vibration Endurance – IEC 60068-2-6 (1995) Class 2:
Not Powered On
Shocks – Not Powered IEC 60255-21-2 (1988) Class 1:
On
15g, 11 ms
Shocks – Powered On IEC 60255-21-2 (1988) Class 2:
10g, 11 ms
Bump Test – Not IEC 60255-21-2 (1988) Class 1:
Powered On
10g, 16ms, 2000/axis
Seismic Test – Powered IEC 60255-21-3 (1993) Class 2:
On
Acceleration: 2g
Displacement: 7.5mm upon axis H
Acceleration: 1g
Displacement: 3.5mm upon axis V
7.3 Atmospheric Test

Damp Heat Test – IEC 60068-2-3 (1969) Test Ca:
Operating
+40°C / 10 days / 93% RH
Cold Test - Operating IEC 60068-2-1 (1990) Test Ab: - 25°C / 96 h
Cold Test - Storage IEC60068-2-1 (1990) Test Ad:
-40°C / 96 h
Powered On at –25°C (for information)
Dry Heat Test – IEC 60068-2-2 (1974) 70°C / 24 h
Operating
Dry Heat Long Test – DICOT HN 46-R01-06 55°C / 10 days

Operating (1993)
Dry Heat Test – Storage IEC 60068-2-1 (1990) Test Bd:

+70°C / 96 h
Powered On at +70°C
Enclosure Protection IEC 60529 (1989) + A1 Front: IP52
(1999)
7.4 DC Auxiliary Supply Test

Inrush current (start-up) DICOT HN 46-R01-4 T < 1.5 ms / I < 20 A
(1993)
1.5ms < T < 150 ms / I < 10 A
T > 500 ms / I < 1.2 In
Supply variation IEC 60255-6 (1988) Vn ± 20%
Vn+30% & Vn-25% for information
Overvoltage (peak IEC 60255-6 (1988) 1.32 Vn max
strength)
2 Vn during 10 ms (for information)
Ramp down to zero N/A From Vn down to 0 within 1 minute
From Vn down to 0 within 100 minutes
Ramp up from zero N/A From 0 to Vn within 1 minute
From 0 to Vn within 100 minutes
Supply interruption IEC 60255-11 (1979) From 2.5 ms to 1 s at 0.8 Vn
50 ms at Vn, no malfunction
Reverse polarity N/A Polarity – for the lower potential of the
supply
Polarity + for the lower potential of the
supply
Ripple (frequency IEC 60255-11 (1979) 12% Vn at f=100Hz or 120Hz
fluctuations)
12% Vn at f=200Hz for information
7.5 AC Auxiliary Supply Test

Supply variations IEC 60255-6 (1988) Vn ± 20%
AC Voltage dips & short EN 61000-4-11 (1994) 2ms to 20ms & 50ms to 1s
interruptions 50 ms at Vn, no malfunction
Frequency fluctuations IEC 60255-6 (1988) 50 Hz: from 47 to 54 Hz
60 Hz: from 57 to 63 Hz
Voltage strength N/A 2 Vn during 10 ms (for information)
7.6 Electromagnetic Compatibility (EMC) Tests

High Frequency IEC 60255-22-1 (1988) Class 3: 2.5kV (CM) / 1kV (DM)
Disturbance IEC 61000-4-12 (1995)
IEEE C37.90.1 (1989)
Electrostatic discharge IEC 60255-22-2 (1996) Class 4:

IEC 61000-4-2 (1995) + 8kV contact / 15 kV air
A1 (1998) + A2 (2001)
Radiated Immunity IEC 60255-22-3 (2000) Class 3:
IEC 61000-4-3 (2002) + 10 V/m – 80 to 1000 MHz
A1 (2002)
IEEE C37.90.2 (1987) & spot tests
35 V/m – 25 to 1000 MHz
Fast Transient Burst IEC 60255-22-4 (2002) Class 4: 4kV – 2.5kHz (CM)
IEC 61000-4-4 (1995) + Class 4: 2.5kV – 2.5kHz (DM) on DI/DO
A1 (2001)
IEEE C37.90.1 (1989)
Surge immunity IEC 61000-4-5 (1995) + Class 4:
A1 (2001) 4kV (CM) – 2kV (DM)
High frequency IEC 61000-4-6 (2003) Class 3:
conducted immunity 10 V, 0.15 – 80 MHz
Harmonics Immunity IEC 61000-4-7 (2002) 5% & 10% from H2 thru H17
Power Frequency IEC 61000-4-8 (1993) Class 5:
Magnetic Field Immunity 100A/m for 1mn
1000A/m for 3s
Pulse magnetic field IEC 61000-4-9 (1993) Class 5:
immunity
6.4 / 16 µs
1000A/m for 3s
Damped oscillatory IEC 61000-4-10 (1993) Class 5:
magnetic field immunity + A1 (2001) 100 kHz & 1 MHz – 100A/m
Power Frequency IEC 61000-4-16 (1998) CM 500 V / DM 250 V via 0.1 μF
Conducted emission EN 55022 (1998) + A1 Gr. I, class A: from 0.15 to 30 MHz
(2000) + A2 (2003)
Radiated emission EN 55022(1998) + A1 Gr. I, class A: from 30 to 1000 MHz
(2000) + A2 (2003)
BLANK PAGE
MiCOM C264P
FUNCTIONAL DESCRIPTION
TABLE OF CONTENTS

1.1 Software features 7
1.2 C264 Standalone 7
2. MiCOM C264 MANAGEMENT 8

2.1 Operating mode management 8
2.1.1 Definitions 8
2.1.2 Initialisation mode 8
2.1.3 Operational mode 9
2.1.4 Maintenance mode 10
2.1.5 Test mode = DSPIO Maintenance Mode 10
2.1.6 Faulty mode 13
2.1.7 Halt mode 13
2.1.8 Summary of modes, tests, transitions, and faults 13
2.1.9 Redundancy mode management 14
2.2 Database management 17
2.2.1 General 17
2.2.2 How to download a database through the Ethernet 19
2.2.3 How to switch the databases 19
2.2.4 How to do a check of the database 20
2.2.5 How to modify the database 20
2.2.6 How to modify a parameter setting in the current DB 20
2.2.7 How to consult a parameter setting 21
2.3 Self tests 21
2.4 Time management 21
2.4.1 External clock 23
2.4.2 Clock synchronisation message from a SCADA gateway 23
2.4.3 SNTP Client and Servers 24
2.4.4 Time set by an operator 24
2.4.5 Local clock update 24
2.4.6 Management of loss of external time reference 25
2.4.7 Update method 26
2.4.8 Limits and performances 26
3. COMMUNICATIONS 27
3.1 Telecontrol bus - TBUS 28
3.2 Legacy bus - LBUS 28
C264P/EN FT/C80 Functional Description
3.3 Station bus - SBUS 29

3.3.1 Exchanges 29
3.3.2 Supported Common Data Classes 30
3.3.3 Controls 30
3.4 Ethernet port management on CPU Type 3, CPU 270 30
4. DIRECT PROCESS ACCESS 32

4.1 Input Check 32
4.2 Output check 32
4.3 Time tagging 32
4.4 Digital input acquisition (DI) 32
4.4.1 Acquisition 32
4.4.2 Debouncing and filtering 33
4.4.3 Toggling 34
4.5 Counters acquisition (CT) 34
4.5.1 Single counter (SCT) 34
4.5.2 Double counter (DCT) 35
4.6 Digital measurement (DM) 35
4.6.1 Acquisition without Read Inhibit signal 36
4.6.2 Acquisition with Read Inhibit signal 38
4.6.3 Encoding 38
4.7 Analogue input acquisition (AI) 39
4.7.1 Input ranges 39
4.7.2 Acquisition cycle 39
4.8 Digital outputs (DO) 39
4.9 Digital Setpoints: SPS, DPS, MPS 39
4.9.1 Encoding 40
4.9.2 Read Inhibit 40
4.9.3 Open / Close Select Order 41
4.10 Analog Setpoints 41
4.10.1 Output range 41
4.10.2 Output management 41
4.10.3 AOU Watchdog management 42
5. DATA PROCESSING 43
5.1 Binary Input processing 43
5.1.1 Binary Input definition 43
5.1.2 Processing of Single Point Status 44
5.1.3 Processing of Double Point Status 46
5.1.4 Processing of Multiple Point Status 50
5.1.5 System Inputs 51
5.1.6 IED inputs 52
5.1.7 Group processing 52
5.1.8 SBMC Mode Processing 53

5.1.9 BI sent to automatism features 53
5.2 Measurement Input Processing 54
5.2.1 Open circuit management 54
5.2.2 Scaling 54
5.2.3 Zero value suppression 55
5.2.4 Thresholds detection 56
5.2.5 Manual suppression 56
5.2.6 Substitution 56
5.2.7 Forcing an invalid measurement 56
5.2.8 Measurement resulting states 57
5.2.9 Transmission 57
5.2.10 CT/VT additional processing 58
5.2.11 Digital Measurement Processing 62
5.3 Tap Position Indication processing 62
5.3.1 Acquisition from Digital Inputs 62
5.3.2 Acquisition from Analogue Inputs 62
5.3.3 Manual suppression 62
5.3.4 Substitution 62
5.3.5 Forcing an invalid TPI 63
5.3.6 TPI resulting states 63
5.3.7 Transmission 63
5.4 Accumulator Input Processing 63
5.5 Energy counting 64
6. CONTROL SEQUENCES 65
6.1 Description 65
6.1.1 General 65
6.1.2 Control sequence phase management 66
6.1.3 Direct Execute mode 69
6.1.4 SBO once mode 70
6.1.5 SBO many mode 73
6.1.6 Generic selection checks 75
6.1.7 Selection behaviour 79
6.1.8 Generic execution checks 80
6.1.9 Execution behaviour 80
6.1.10 Controls time sequencing 81
6.1.11 How an xPS starts a control sequence 84
6.2 Control of non synchronised breakers 88
6.2.1 Non synchronised circuit breaker features 88
6.2.2 Control sequence of non-synchronised circuit breakers 88
6.3 Control of synchronised breakers 89

6.3.1 Synchronised circuit breaker features 89
6.3.2 Circuit breakers with external synchrocheck 90
6.3.3 Circuit breakers with internal synchrocheck 95
6.4 Control of disconnectors 99
6.4.1 Disconnectors features 99
6.4.2 Control sequence of disconnectors 99
6.5 Control of transformers 99
6.5.1 Transformer features 99
6.5.2 Control sequence of transformers 100
6.6 Control of ancillary devices 103
6.7 Control of Intelligent Electrical Devices (IED) 103
6.7.1 Control to IEDs 103
6.7.2 IED controls 104
6.7.3 Digital setting point (SP) 104
6.8 System controls 104
6.9 Kinds of control sequences 104
6.10 System controls 105
6.11 Kinds of control sequences 105
6.12 Control sequences checks 105
6.12.1 Mode Management 105
6.12.2 IED connected 105
6.12.3 Control mode 106
6.12.4 Uniqueness of control 106
6.12.5 Inter-control delay 106
6.12.6 Status of the device 106
6.12.7 Lock device 106
6.12.8 Running Automation 106
6.12.9 Interlocking 106
6.13 HV Control Sequences 107
6.13.1 Circuit breaker 107
6.13.2 Disconnector 107
6.13.3 Transformer 107
7. AUTOMATIONS 108
7.1 Built-in Automation functions 108
7.1.1 Auto-Recloser (AR) 108
7.1.2 Trip Circuit Supervision 114
7.1.3 Circuit breaker condition monitoring (I²t) 116
7.2 Interlocking: logical equations 117
7.2.1 Interlocking: Inputs 118
7.2.2 Interlocking:Outputs 118
7.2.3 Interlocking: Control 118
7.2.4 Interlocking: Behaviour 118

7.3 Interlocking: logical equations 121
7.3.1 Interlocking: Inputs 121
7.3.2 Interlocking:Outputs 121
7.3.3 Interlocking: Control 121
7.3.4 Interlocking: Behaviour 122
7.3.5 Limits and performance 124
7.3.6 Limits and performance 124
7.4 Slow automation: Programmable Logic Control (PLC) 125
7.4.1 Inputs 126
7.4.2 Outputs 126
7.4.3 Control 126
7.4.4 Behaviour 127
7.4.5 Limits and specifications 127
7.5 Fast automation: Programmable Scheme Logic (PSL) 128
8. USER INTERFACE 129

9. RECORDS 130
9.1 Permanent records storage 130
9.1.1 Data storage 130
9.1.2 Disturbance Recording: General 130
9.1.3 Disturbance recording 130
9.1.4 Slow Waveform Recording 131
9.1.5 Slow Waveform Recording – Hypothesis 132
9.1.6 Events 132
10. PROTECTION FUNCTIONS 138

10.1 Directional/Non-directional Phase OC Protection (ANSI code 67/50/51) 138
10.2 Dir. /Non-dir. Neutral/Ground/Earth OC Protection (ANSI code 67N/50N/51N) 139
10.3 Dir. /Non-dir. Sensitive ground/Earth OC protection (ANSI code 67N/50N/51N) 140
10.4 Thermal overload protection (ANSI code 49) 141
10.5 Undercurrent protection (ANSI code 46) 141
10.6 Earth Wattmetric Protection (ANSI code32N) 141
10.7 Negative sequence OC protection (ANSI code 27) 142
10.8 Undervoltage (ANSI code 27) 143
10.8.1 Threshold settings (secondary values) 143
10.8.2 Time delay settings 143
10.8.3 Definite time delay characteristics 143
10.9 Overvoltage (ANSI code 59) 144
10.10 Residual overvoltage / neutral displacement (ANSI code 59N) 145

10.11 Under/overfrequency (ANSI codes 81U/81O) 145
10.12 Rate of change of frequency (ANSI codes 81R) 146
10.12.1 Threshold settings 146
10.12.2 Integration time 146
10.12.3 Validation number of protection 146
10.12.4 Under voltage blocking 146
10.13 Extra functions 146
10.13.1 Circuit breaker failure (50BF or TCS) 146
10.13.2 Cold load pick-kup 146
10.13.3 RSE 146
10.13.4 Trip management 147
11. PROTECTION CURVES 148

11.1 IDMT Curves 148
11.1.1 Mathematical formula 148
11.1.2 IEC Curves 151
11.1.3 RI Curves 157
11.1.4 IEEE/ANSI & CO Curves 158
11.2 Thermal overload curves 164
11.2.1 Mathematical formula 164
11.2.2 Tripping curve 165

This document is a chapter of the MiCOM C264 Computer documentation. This chapter gives
you the functional description for this computer. You can find the hardware description in the
Hardware Description (HW) chapter. All of the connection diagrams show in the Connection
Diagrams (CO) chapter. You can find the technical data for this computer, such as the
capabilities, performances, and environmental limits, in the Technical Data (TD) chapter.
1.1 Software features
The C264 computer is a modular product at the hardware, software and functional levels. You
can fully configure all functions in agreement with customer needs and requirements. The C264
computer includes:
• Direct process interface through Digital Inputs (DI), Digital Outputs (DO), Analogue Inputs
(AI), Analogue Outputs (AO) and Current Transformer (CT)/Voltage Transformer (VT)
boards
• Direct Operator Interface (OI)
• Embedded parameters to control all common plants or devices
• High communication abilities to IED, Ethernet, and SCADA
• User configurable automation modules
• Events, alarms, measurement display, printing and archiving
• Enhanced inner management with database management, self-test controls and the
capability to synchronize all of the devices.
The components of the software management include:
• Input/Output boards: DI, DO, AI, AO
• Analogue Inputs: AI, and from the optional CT/VT board
• Communications with the Telecontrol Bus (TBUS), Station Bus (SBUS) and Legacy Bus
(LBUS). Please refer to the Communications (CT) chapter
• Communication with peripherals such as:
• Local Operator Interface: LCD, front panel
• Local Printer: local sequence of events (SOE)
• Three ways to perform automation functions:
− Programmable Scheme Logic (PSL) for all C264 computers except the C264
Standalone computer
− Programmable Logic Control (PLC) for all C264 computers
− Built-in automation functions, such as:
⇒ Auto-Recloser (AR)
⇒ Trip Circuit Supervision
⇒ Circuit Breaker Condition Monitoring (I2t)
⇒ xPS/xPC Association
⇒ Pole Discrepancy
1.2 C264 Standalone
The C264 Standalone computer includes the ISAGRaF and PSL automations.
2. MiCOM C264 MANAGEMENT

The computer manages its own mode, configuration (Databases), and time.
2.1 Operating mode management
2.1.1 Definitions
Computer modes: the computer operates in the modes that follow:
• Initialisation mode
• Operational mode
− Normal mode
− Downgraded mode
• Maintenance mode
• Test mode
• Faulty mode
• Halt mode
Computer faults include:
• Anomaly: a fault that causes a downgrade in the behaviour of the computer. There are
hardware and/or software anomalies, as follows:
− Board failure
− Loss of synchronisation
− Loss of communication.
• Software fault: a major software error causes a software fault, that causes the computer
to go into the Faulty mode.
• Vital hardware fault: a fault that causes a software halt, that causes the computer to stop
the application software. Vital hardware faults include:
− CPU fault
− Power supply fault
− Bus fault
− Permanent interruption fault

2.1.2 Initialisation mode
After a power on or a manual reset event occurs, the computer goes into the initialisation mode.
The initialisation mode does not exceed one minute. 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 initialisation 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:
− 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.
2.1.3 Operational mode
This mode includes two sub-modes: Normal mode and Downgraded mode.
2.1.3.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
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 Test 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 Test mode to the local HMI and to the upper level
remote control point (RCP).
2.1.3.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 devices
• A combination of two, or more, of these events.

When you or the computer resolve the cause of the transition into the Downgraded mode, the
computer returns to the Normal mode.
2.1.4 Maintenance mode
In Maintenance mode, the station bus (SBUS) operates: you can communicate on the SBUS to
manage the database. The Maintenance mode shows on the local HMI (LED and LCD) and on
the upper level.
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

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.
2.1.5 Test mode = DSPIO Maintenance Mode
To simulate the function of distributed automatic events, such as interlocks, you request to set
the computer to Test mode. In Test 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, you must manually force BI or Measurements on

different computers to create the test conditions. 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 Test mode shows on the local HMI (LED and LCD) and on the upper level.
In the Test 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.
The behavior of the CPU and the DSP in agreement with the C264 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
.
Computer CPU Operating Mode versus Commands Received by the CPU

2.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.
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 automatically resets
When the value of the internal counter reaches Max_Fault, the computer goes into the Halt
mode.
2.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.
2.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:
DB/software compatibility not OK

or
boot DB/equipment compatibility not OK
or
data of database not valid
INITIALISATION
Major
automatic hardware
reset fault Init OK manual reset
hardware test OK
and coherency not OK
FAULTY
no DB
major hardware fault major hardware fault
or software fault or software fault
simulation request maintenance request
TEST OPERATIONAL MAINTENANCE

end of simulation active request
vital
hardware vital hardware
fault vital hardware fault fault
vital hardware fault
HALT
Counter of faults = Max_Fault
C0288ENa
2.1.9 Redundancy mode management

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
• 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. A PACiS IEC-61850 client receives data
from the two computers: this client processes only the data it received from the computer in
the active mode. Only the computer in the active mode 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 1: 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.
The initial state is “Initialisation” (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 during 20 seconds.
T1 is the timer of Active status confirmation during the computer initialisation (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).
The switching time is less than 30 seconds.
State 0: State 1: State 2: State 3: State 4: State 5:

Initialisation Waiting end of Standby Standby / T2 Active Standby mode
initialisation / T1 timer on- on-going
timer on going going
DI1≠1 ≠ T1 timer / ≠ close DO1 ≠ stop T2 timer / /
≠ go to state 1 ≠ go to state 4 ≠ go to state 4
DI1=1 go to state 2 ≠ stop T1 timer / ≠ open DO1 go to state 5 /
≠ go to state 2 ≠ stop T2 timer
≠ go to state 2
“confirmed” / / ≠ T2 timer / / /
DI2≠1 launching
≠ close DO1
≠ go to state 3
Remore IS / / If (L_IS<R_IS) If (L_IS>R_IS) / /

then then
≠ T2 timer ≠ stop T2 timer
launching ≠ open DO1
≠ close DO1 ≠ go to state 2
≠ go to state 3
End of T1 / If DI1≠1 / not possible not possible /
timer
then:
≠ T2 timer
launching
≠ close DO1
≠ go to state 3
else:
≠ go to state 2
End of T2 / / / go to state 4 / /
timer
End of / not possible not possible not possible not possible open DO1 if
standby mode conditions to enter
going-on standby mode are
not true anymore
then
≠ T2 timer
launching
≠ go to state 3
else
≠ go to state 2
2.2 Database management

2.2.1 General
The C264 uses structured databases to manage data. The main principle is that the
computer will only operate with other PACIS 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 separate PACiS tool, the System Configuration Editor (SCE),
to create and version the databases. Each database has a related VDBS (System Baseline
Version).
You can download a standby database even if the computer is in operation: use the
filename.adb format.
You can download a database into the flash memory of the computer in two ways:
• Use the PACiS tool, the System Management Tool (SMT) to download the database
thru the IEC61850 station bus (SBUS).
• Use the PACiS tool, the Computer Administration Tool (CAT), to download the
database directly over Ethernet. Operators generally use the CAT only for the
download of the first database. During the download, the CAT sends the database to
all of the other racks. This database becomes the new Standby database. At the
Switch command, the computer cascades the switch operation to the other racks.
From SCADA, the standalone computer receives the database file and saves it in RAM, but
does not send it to the other racks.
On the standalone computer, the database status shows only on the main rack LCD.
If the main database on the main 1 rack is compatible with the standby database on the
other rack, the computer switches the database.
At any moment, the computer stores as many as 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 computer, 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:
Absent
Downloading
Switching
Standby Current
Parameter setting
Parameter setting
Standby Current
Modified Modified
Switching
C0308ENa
FIGURE 2: 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:
Database State 1 State 2 State 3 State 4

DB1 and VDBS1 Current Current Modified Current Current Modified
DB2 and VDBS2 Standby Standby Standby Standby Modified
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. This file descriptor, that includes
the state of each of the two databases and their related VDBS (for example, DB1 and
VDBS1; DB2 and VDBS2), allows you to know the configuration of the databases at the
moment of the computer boot (initialisation mode), and to start again with the Current
database, if it exists. To update the file descriptor DB Context, use these functions:
• Download a database
• Switch the databases
• Check a database
• Modify a Database.
2.2.2 How to download a database through the Ethernet

Connect the computer to the station bus (SBUS). Use the SMT tool to download the first DB.
The first time that you download the DB and the related Vdbs, make sure that the computer
is in maintenance mode.
When the computer operates with the first DB, and the computer is either in operational
mode or in maintenance mode, you can download the standby DB and its related Vdbs.
The sequence to download the DB follows:
1. Use the PACiS SMT tool to send a request to start the transfer of the database.
2. The receiver, the PC, gives a positive response.
3. Transmit the response to the device that called. If another request on the same DB is
already in progress, the device will refuse your request.
4. Download the DB file and the related Vdbs. The computer does a check of the
integrity of the files: it calculates the checksum and control of the DB
5. In event of a fault, the computer sends a signal to announce the failure of the transfer,
to the device that called
6. In event of a successful transfer of the DB, the computer controls the DB compatibility
7. In event of an invalid DB, the computer sends a signal to announce the failure of the
DB installation, to the device that called
8. In event of a valid DB, the computer:
a. Removes a possible standby DB and related Vdbs already installed in the
computer
b. Assigns the state standby to the downloaded DB and related Vdbs installed in the
computer
c. Sends a signal to announce the success of the DB installation to the device that
called.
9. The computer updates the file descriptor, Context DB, in flash memory.
2.2.3 How to switch the databases
The SBUS sends a request to switch the DB. This request specifies the Version of the
standby DB and related Vdbs to become current. Please refer to Figure 4 : Database
Download and to Figure 5 : Database Switching
SWITCH
T0 T0 + T1
CURRENT STANDBY CURRENT STANDBY
Vdbs n.m Vdbs x.y Vdbs x.y Vdbs n.m
DB1 DB2 DB2 DB1
T0 + T1 MAINTENANCE
MAINTENANCE
T0 + T1 CURRENT STAND-BY
Vdbs x.y Vdbs n.m
DB2 DB1
OPERATIONAL
C0309ENa
FIGURE 3: DATABASE SWITCHING

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.
2.2.4 How to do a check of the database
At each reboot, the computer does a check of the DB.
With the 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.
2.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.
2.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:
a. Is the object known to the computer, that is, is the object really present in the
database
b. Can the computer set the data
c. Is the value of the parameter setting compatible with the type of data conveyed:
does the value belong in the range of acceptable variation
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
2.2.7 How to consult a parameter setting
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:
a. Is the object known to the computer, that is, is the object really present in the
database
b. Can the computer set the data
c. Is the value of the parameter setting compatible with the type of data conveyed:
does the value belong in the range of acceptable variation
2. If the request is incoherent, the computer sends a negative report to the device that
sent the request:
3. Develop the response to include the parameter setting and to send it to the device that
sent the request
For the C264 standalone, you can use the Computer Administration Tool (CAT) to upload
and store a DB as large as 20 MB in the flash memory.
2.3 Self tests

The computer performs these self-tests:
• Hardware (hardware fault) at start-up and cyclically.

• Software (software fault) 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.
2.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 for all C264 computers
− SCADA for all C264 computers
− SBUS or LBUS for all C264 computers except C264 Standalone computers
− Operator for all C264 computers except C264 Standalone computers
• To update the local clock
• To synchronise other devices through the SBUS with the local clock
You can synchronize the local clock with an external time reference from four sources:
• External clock sends an IRIG-B signal 1
• SCADA sends a clock message through the TBUS and through the gateway1
• The system master clock sends a clock message through the SBUS - SNTP 2
• An operator who sets the time²
1
For all C264 computers
2
For all C264 computers except C264 Standalone computers
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

In event an external clock disconnects or does not operate, there is a priority order for the
three external time references that remain:
1. SCADA sends a clock message through the TBUS and through the gateway
or
2. The system master clock sends a clock message through the SBUS have priority over
3. 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 synchronises the Intelligent Electronic Device (IED) in agreement with the
synchronisation procedure of the protocol. If the local clock is not synchronised, the
computer synchronises periodically the IED all the same.
When the local clock is synchronised, all events and measurements include a time tag with a
synchronised attribute. If the synchronisation is lost, or was never achieved, the attributes
indicate that the time tag is not synchronised.
For a substation, the PACiS architecture can synchronize as many as 120 devices, such as
the C264, OI, gateways, IED Relays, IEC61850 Relays, and so on.
The organization of the time management follows:
FIGURE 4: TIME MANAGEMENT

2.4.1 External clock

The external clock receives the synchronisation signal through one of several protocols:
GPS, DCF77, and so on. Periodically, the external clock sends the synchronisation signal,
that includes the hour and the date, to the dedicated IRIG-B input of the MiCOM C264 /
C264C computer.
Each computer has its own local clock. The local clock synchronises 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:
1. Some external clocks include a very accurate oscillator. After a loss of radio signal,
these external clocks can synchronise 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 synchronised 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-synchronised.
2. 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-synchronised
If the computer operates as the system master clock for the other devices in the substation,
then it continues to send the clock synchronisation message to the other devices, even if the
local clock, or system master clock, is not synchronised with an external time reference. A
binary input is dedicated to monitor the status of the external clock.
2.4.2 Clock synchronisation message from a SCADA gateway
The acquisition of a SCADA clock synchronisation message is a SCADA gateway
specification.
The SCADA clock synchronisation depends on the protocol. The clock synchronisation
message goes directly thru the SCADA link to the C264 computer.
The clock synchronisation message from the SCADA gateway is in Universal Time
Coordinated (UTC) time.
From the SCADA, the clock synchronisation message goes to the “local clock update”
function in the computer. The computer does a check of the frame of the clock
synchronisation message, removes the control fields, and transmits the clock
synchronisation message.
When the SCADA gateway operates as the external time reference in agreement with the
priority, the computer receives the clock synchronisation messages from the SCADA. An
interruption relates to the arrival of the frame: the computer can acquire the clock
synchronisation message from the SCADA gateway. The delay in the transmission from the
SCADA gateway is compensated.
The clock synchronisation 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.
2.4.3 SNTP Client and Servers

On an IEC61850 network, the clock synchronisation uses the Simple Network Time Protocol
(SNTP). In a PACiS system, you can define as many as two computers as the System
Master Clock: they become SNTP servers. All other devices installed on the IEC61850
become SNTP clients. In event that one SNTP server fails, for example a computer is
unserviceable, or an external clock fails, the SNTP clients automatically connect to the
second SNTP server.
Use the PACIS tool, the System Configuration Editor (SCE), to configure a C264 as an
SNTP server, that could be redundant: you can define 2 IP addresses. These IP addresses
must be in the same range as the C264 Ethernet addresses.
In this event, no C264 is the Master Clock: all C264 computers are SNTP clients.
The synchronization performance of the system depends on the accuracy of the third-party
SNTP server.
You can connect one C264, that is configured as an SNTP server, to a second C264 SNTP
server to make a C264 redundant system.
2.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 synchronises any other device in a PACiS system architecture,
you cannot set the time for that device. However, in event the system master clock is
unserviceable or the connection fails, you can set the time for the device.
If the computer does not receive the clock synchronisation 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 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.
You use two commands:
• One to modify the time: hour/minutes/seconds
• One to modify the date: year/month/day

You can reserve a third command to do a check on the date and hour values.
You must raise a manual time-set-indication. The computer makes a record of all operator
actions.
2.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 synchronise 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 synchronisation message; or
loss of the system master clock
• An indication that the local clock was roughly synchronised. This indication shows any
time difference, between the local clock and the clock synchronisation message, that
is greater than the fixed value: Δthreshold = 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.
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 synchronisation 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.
At initialisation, the computer shows the external clock as not-synchronised with the local
clock. This status remains the same until you send a control message to the initialisation
driver to receive synchronisation frames from an external time reference. When the control is
OK and at the reception of the first external clock message, the synchronisation upon
external clock is declared valid and the external clock is considered connected.
This synchronisation with the external clock could fall back to invalid: for example, in event
the computer did not receive an external synchronisation 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-
synchronisation mark against each event, for as long as the synchronisation with the
external clock remains invalid.
When a device on the SBUS does not receive a clock synchronisation 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.
2.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
2.4.7 Update method

When the computer validates the external clock acquisition, the computer manages the
synchronisation 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] ≠ 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:
4. If [C Local – C External] ≤ Δ 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).
5. If [C Local – C External] ≥ Δ 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.
2.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 μs/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.
3. COMMUNICATIONS
MiCOM C264/ C264C includes different types of communications:
• Telecontrol Bus (TBUS)
• Legacy Bus (LBUS)
• Station Bus (SBUS)
FIGURE 5: COMMUNICATIONS
For the C264, the possible combinations of protocols follow:
Protocols Total number

Item Protocols on LBUS
on the TBUS of protocols allowed
1. 2 0 or 1 or 2 4 or less
2. 1 0 or 1 or 2 or 3 4 or less
3. 0 0 or 1 or 2 or 3 or 4 4 or less
3.1 Telecontrol bus - TBUS

You can connect a C264 through the TBUS to the SCADA. The TBUS can use a maximum
of two of these protocols:
Protocol Protocol C264 C264 BCU C264

Type behaves as Standalone
DNP 3.0 Master / Slave Slave Serial and over IP –
DNP3 Master / Slave Slave Serial and over IP –
MODBUS Master / Slave Slave Serial –
T101 Master / Slave Slave Serial Serial
or Balanced
T104 Balanced Slave Over IP Over IP
HNZ Master / Slave Slave – Elenas
(Indonesia)
HNZ Master / Slave Slave – Yemen
C264 behaves as a slave into:
• Master/slave protocols: DNP 3.0, DNP3 over IP, MODBUS, T101, HNZ-Elenas, HNZ-
Yemen
• Balanced protocols: T101, T104.

C264 connects direct or through a modem with SCADA.
Physical layer:
• DNP 3.0, MODBUS, T101, HNZ-Elenas, HNZ-Yemen: RS232, RS422, RS485
• DNP3 over IP, T104: Ethernet 10 or 100 Mb/s: RJ45 connector or optical fibre
(multimode or monomode)
On the C264, you can configure as many as 2 different serial telecontrol protocols. If you use
the Ethernet IEC 104 standard, you can connect as many as four independent clients.
CAUTION: WHEN YOU USE THE SERIAL PORTS ON THE CPU BOARD, MAKE SURE
THAT THE BAUDRATE IS THE SAME FOR BOTH CPU SERIAL PORTS:
COM3 AND COM4.
The redundancy is not available for T104, DNP3 over IP, and MODBUS.
3.2 Legacy bus - LBUS
C264 behaves as a master.
Protocols:
• IEC 60870-5-103 (T103)
• IEC 60870-5-101 (T101)
• ModBus
• DNP 3.0
Devices connected to: IEDs
Physical layer:
• RS232, RS422, RS485
• Optical fibre
CAUTION: WHEN YOU USE THE SERIAL PORTS ON THE CPU BOARD, MAKE
SURE THAT THE BAUDRATE IS THE SAME FOR BOTH CPU SERIAL
PORTS: COM3 AND COM4.
CAUTION: IF THE MAIN 1 RACK IS REDUNDANT, THERE IS NO LBUS
CONNECTED TO THE MAIN 1 RACK.
CAUTION: THERE IS NO REDUNDANCY FOR THE LBUS
On the C264, as many as four serial ports are available to make four networks with as many
as four different protocols.
3.3 Station bus - SBUS
The S-BUS Protocol is used for PACiS subsystems communication but it is also available for
other equipment.
A C264 computer behaves mainly as a server but it can be also a client of other C264
computers (distributed automations) or IEC 61850 IED.
Protocol:
• IEC 61850
Devices connected to:
• PACiS devices (OI, SMT, PACiS Gateway)
• Other C264 computers
• IEC 61850 IEDs

Link layer: Ethernet 10 or 100 Mb/s
Physical support:
• Copper twisted pair (RJ45 connector)
• Optical fiber (multimode or monomode)

The optical port is optional. To increase the number of Ethernet port, two Ethernet switch
boards are available:
• SWU with 4 RJ45 ports and up 2 optical ports (multimode or monomode)
• SWR with 4 RJ45 ports and 2 optical ports for a redundant ring (multimode or
monomode)
3.3.1 Exchanges
C264 computer acquires and sends data on IEC-61850 network using two mechanisms:
• 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 synchronised or not when event has occurred)
Data quality defines if data is valid or several kind 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.
3.3.2 Supported Common Data Classes

C264 computer exchanges data using Common Data Classes. The following list gives
implemented ones:
Kind of information IEC 61850 Common Data Classes

Status Information Single Point Status (SPS)
Double Point Status (DPS)
Integer Status (INS)
Protection Activation Information (ACT)
Directional Protection Activation Information (ACD)
Binary Counter Reading (BCR)
Measured Information Measured Value (MV)
WYE
Delta (DEL)
Controllable Status Information Controllable Single Point (SPC)
Controllable Double Point (DPC)
Controllable Integer Status (INC)
Binary Controlled Step Position Information (BSC)
Controllable Analogue Information Controllable Analogue Setpoint Information (APC)
TABLE 1: DATA MANAGEMENT
3.3.3 Controls
C264 supports Common Data Classes control expressed with SPC, DPC, INC and APC
configured as Direct Execute or SBO.
3.4 Ethernet port management on CPU Type 3, CPU 270
The 2 CPU Type 3 Ethernet ports can be configured as follows:
N° Port 1 Port 2 Comments

1 IEC61850 SBUS + SCADA IP 2 2 independent SCADA protocols
SCADA IP 1 with different database
2 SCADA IP 1 SCADA IP 2 2 independent SCADA protocols
with different database
3 IEC61850 SBUS SCADA IP
TABLE 2
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 IS 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.
FIGURE 6: CAT SHOWING TWO ETHERNET PORTS

4. DIRECT PROCESS ACCESS

Several kinds of boards can be used in C264 and extension racks. Digital Input & Outputs,
Measurement acquisitions are checked to validate information/action and time tagged on any
change of state or value.
The C264 acquires digital and analogue input, counters, digital measurements. Configuration
parameters, filtering and triggering are applied to these inputs and depend on their type.
4.1 Input Check
Input data coming from the physical MiCOM C264 boards or from the different
communication networks are periodically checked.
Invalidity status of these data is internally fixed for:
• Self-test (DI, AI, board self test failure)
• Unknown (DI, AI, communication failure to remote acquisition like IED)
• Toggling (DI, X change of state in given time)
• Over-range (AI, saturation of its transducer, or Counter value reaching limits)
• Open Circuit (AI kind 4-20 mA with current value under 4mA)
• Undefined (Digital Measurement or Counter with invalid DI coding)

4.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 Time tagging
All physical input data are time tagged at 1 ms accuracy. All internal logic data are time
stamped at 1 ms accuracy.
Analogues acquisition time tagging is done but driven by periodic polling of this kind of
board. Periods are based on multiple of 100ms.
Information coming from IED are time tagged by IED itself if it has this facility otherwise it is
performed at C264 level when receiving the data.
4.4 Digital input acquisition (DI)
4.4.1 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 stabilises. The software must filter these bounces.
Each change-of-state of a digital input is time-stamped with a resolution better than 1 ms.
Debouncing & Toggle

Filtering for BI Filtering for To BI
BI treatment
Hardware Software Time Debouncing & Special

acquisition acquisition stamping Filtering for treatment To measurements
DM for DM treatment
Debouncing & Special

Filtering for treatment To counters
counters for treatment
counters
C0126ENa
FIGURE 7: DIGITAL INPUT PROCESSING
4.4.2 Debouncing and filtering

A filter is applied on the digital inputs as follows:
Filtering time
Debouncing
time
t0 t1 t2
C0127ENa
FIGURE 8: 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.4.3 Toggling
A digital input is said to be toggling if its state has changed more than N times in a given
period of time T1.
A toggling DI returns in the normal state if its state has not changed within another period of
time T2.
N, T1 and T2 are parameters determined at configuration time on a per system basis (same
parameters for all MiCOM computers of a system).
The toggle filtering applies only on DI that will be used as BI (there is no toggle filtering on DI
that will be used for counters or DM).
4.5 Counters 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 48H when the C264 power supply is off.
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 C264. You can wire as many as
eight counters on the main 1 rack with no modifications.
4.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.
Tcount Tcount
Transition validated,
Low to high transition
counter is incremented
Transition discarded
Low to high transition
C0128ENa
FIGURE 9: SINGLE COUNTER CHRONOGRAM

4.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 can be taken into account only 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 it 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).
Tcount Tcount Tdef

TC
CC
Low to high transition Low to high transition, but no

validated high to low transition
Transition discarded, and before -> Tcount is not launched
high to low transition
Low to high transition Non-complementarity

confirmed, counter is invalid
Transition validated,
counter is incremented Detection of non-complementarity
C0129ENa
FIGURE 10: DOUBLE COUNTER CHRONOGRAM
4.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.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.
Confirmed Confirmed Confirmed

DM value DM value DM value
Tstab
Tstab
Bit change => new Bit change => Bit change =>
calculation new calculation new calculation
Δ≤V stab=> confirmed Δ>V stab => Tstab Δ>V stab => Tstab
DM value launched re-launched
Note : Δ= |confirmed DM value – new calculation|

C0130ENa
FIGURE 11: 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.
TInv
Confirmed
DM value DM UNDEFINED
Tstab
Tstab
Tstab
Bit change => Bit change => Bit change =>

new calculation new calculation new calculation
Δ>V stab => Tstab Δ>V stab => Tstab Δ>V stab => Tstab
launched re-launched re-launched
C0131ENa
TInv
Confirmed
DM value DM UNDEFINED
Ts tab
Tstab
Tstab
Bit change => Bit change => Bit change =>

new calculation new calculation new calculation
Δ>Vs tab => Tstab Δ>Vs tab => Tstab Δ>Vstab => Ts tab
launched re-launched re-launched
FIGURE 12: DM UNDEFINED
If Vstab is equal to 0, there is no stability processing: all DM values are sent at each
calculation.
4.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.
Tinh Tinh
RI
DM value transmitted DM UNDEFINED

C0132ENa
FIGURE 13: ACQUISITION WITH RI
If the RI signal is invalid, the DM will be invalid.

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

BCD 4 (1 BCD decade) 0 to 9
8 (2 BCD decades) 0 to 99
12 (3 BCD decades) 0 to 999
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
Decimal 16 0 to 69
(1 bit among 6 for the tens,
1 among 10 for the units)
32 0 to 4,999
(1 bit among 4 for the thousands,
1 bit among 9 for the hundreds,
1 bit among 9 for the tens,
1 bit among 10 for the units)
64 0 to 9,999,999
(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,
1 bit among 9 for the thousands,
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:
CODE Number of bits Range of value

1 among N 2 0 to 2
to 64 to 0 to 64
4.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 voltages or currents signals is done with the AIU201 (4 AIs) or AIU211 (8
AIs) boards. For those AI an input range and an acquisition cycle are defined in
configuration.
4.7.1 Input ranges
The different input ranges are:
For voltage inputs (AIU201 only): ± 10 V, ± 5 V, ± 2.5 V, ± 1.25 V
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.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 C264. and 200 MV/sec receiving flux for a C264.
4.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 C264:
• CCU200 boards for controls (8 DIs+4 normal open DOs), this board allows double
pole switching controls.
• DOU201 boards for alarms (8 normal open DOs + 2 normal open/normal close DOs).
4.9 Digital Setpoints: SPS, DPS, MPS
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.9.1 Encoding
The codes that follow are allowed:
CODE Number of bits ( max. 48) Range of value

BCD 4 ( 1 BCD decade) 0 to 9
8 ( 2 BCD decades) 0 to 99
12 ( 3 BCD decades) 0 to 999
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
Decimal 16 0 to 69
( 1 bit among 6 for the tens,
32 0 to 4,999
(1 bit among 4 for the thousands,
48 0 to 299,999
(1 bit among 2 for the hundreds of thousands,
1 bit among 9 for the tens of thousands,
1 bit among 9 for the thousands,
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.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
• 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.9.3 Open / Close Select Order

An option includes the order-running-SPS: one for the open order control, and one for the
close order control.
The order-running-SPS are available only for Double Point Control (DPC).
When the C264 receives the Select (for SBO control) or the Execute (for DE control) order,
and before the checks, it sets the order-running-SPS to the SET position.
When the C264 receives the control acknowledgement, the C264 sets the order-running-
SPS to the RESET position
In event of a direct negative acknowledgement, the C264 may set the order-running-SPS to
the SET position and to the RESET position with the same time-stamp.
4.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)
The Analog output values are secured with an external power supply that allows you to keep
the analog output value in event of C264 shutdown or power off.
A quality indication is available with the additional Read Inhibit output relays (NO) associated
to each analog output.
4.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.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.
Stable Output value modification Stable
Analog
Output
100 ms
10ms 10ms
Set
RI relay
status Reset
C0289ENa
FIGURE 14: DIAGRAM OF AOU CHANNEL
4.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 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, the AOU watchdog relay is set.
5. DATA PROCESSING
MiCOM C264 treatment entries can be Binary Inputs or Analogue Inputs. They are issued
from
• IO boards
• MiCOM C264 internal information (System Input, automation)
• Communication acquisition (IED or other computer from LBUS or SBUS)
5.1 Binary Input processing
5.1.1 Binary Input definition

The five types of Binary Inputs (BI) are:
• Single Point (SP): derived from one BI
• Double Point (DP): derived from two BIs
• Multiple Point (MP): derived from multiple BIs
• System Input (SI): information related to the system, to configurable and built-in
automations or to electrical process but without acquisition possibilities
• Group: logical combination of BIs

SP, DP and MP are acquired via digital input boards or via IEDs connected by a serial link.
5.1.1.1 Toggling Input

A binary input is said to be toggling if its state has changed more than N times within a given
period of time T.
After the acquisition on digital inputs boards, the computer performs toggle filtering, this
avoids loading the computer itself or other equipment when an input has an hazardous
behaviour
An SP associated with a toggling Binary Input is in the TOGGLING state.
A DP or an MP whose one of the associated DI is toggling ist in the TOGGLING state.
5.1.1.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 e.g. display, alarm, transmission.
The BI takes the “SUPPRESSED” state. When the operator unsuppresses the BI, this one
takes its actual state.
5.1.1.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 unsubstitutes 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 unsubstituted, the actual state is
transmitted to higher control levels and subsequent changes of state are transmitted again.
5.1.1.4 Forcing
When an information is invalid (i.e. SELFCHECK FAULTY, TOGGLING, UNDEFINED or
UNKNOWN), it can be manually forced by an operator (state “FORCED xxx”). This feature is
similar to the substitution but the information is automatically updated when valid information
is available again. A SUPPRESSED or SUBSTITUTED datapoint cannot be forced. The
forcing could also be automatic: in this case, the invalid information is automatically replaced
by the state defined in configuration.
5.1.1.5 Transmission
By configuration, a BI could be transmitted on a client-server basis on the station bus using
the two modes:
• Report based mode: in this mode, a confirmed change of status is spontaneously
transmitted to the subscribers with the time stamping and the reason for change. The
Report mode is used to transmit filtered data for displaying, printing and archiving.
• GOOSE based mode: in this mode, the change of status is transmitted in multicast to
the configured receivers. On IEC61850 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.
During a loss of communication, the events detected on the computer are not buffered.
5.1.2 Processing of Single Point Status
DI/DO
association
Group
processing
From Toggle
acquisition filtering Manual
suppression Persistance
filtering Transmission – To RCP
Substitution Report based To HMI
From IED IED To Printer
inputs To Archive
Forcing
System
Inputs
Transmission –
GOOSE based To
automation
C0133ENa
FIGURE 15: SINGLE POINT STATUS PROCESSING

A preliminary treatment (filtering) is applied to specific Single Points (SP) in order to confirm
the state.
The choice of these SPs and the filtering time are fixed by the MiCOM C264 configuration. If
the opposite transition occurs before this delay, both transitions are discarded.
This treatment is said to be a persistent filtering.
The SP resulting states are:
States (Report) Goose

RESET 01
SET 10
TOGGLING 11
SELFCHECK FAULTY 11
UNKNOWN 11
SUPPRESSED 11
FORCED RESET 01
FORCED SET 10
SUBSTITUTED RESET 01
SUBSTITUTED SET 10
For automation (interlock, PSL, PLC, and built in functions), GOOSE are used. Each valid
state (01, 10 and 00) is configurable to be seen by automation in False, True or Invalid sate.
5.1.2.1 Persistence filtering

For some SP, a transition must be confirmed on a certain period of time. If the opposite
transition occurs before this delay, both transitions are discarded.
Two time-out values can be associated with each SP:
• 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 stamped with the time of the transition.
• Mode 2: the status is stamped at the end of the persistent filtering.

TS TS
TR TR
SET
SP before filtering
RESET
SET
SP after filtering, mode 1
RESET
SET
SP after filtering, mode 2
RESET
t0 t1 t2 t3 t4 t5 t6 t7
• t0 : RESET to SET transition

• t1 : SET to RESET transition ; SET state not confirmed. The
transition is discarded (TR is not launched because there is no
change of state).
• t2 : RESET to SET transition
• t3 : SET state confirmed (stamped t2 if mode 1, stamped t3 if mode 2)
• t4 : SET to RESET transition
• t5: RESET to SET transition ; RESET state not confirmed. The
transition is discarded (TS is not launched because there is no
change of state).
• t6 : SET to RESET transition
• t7 : RESET state confirmed (stamped t6 if mode 1, stamped t7 if
mode 2) C0310ENa
FIGURE 16: PERSISTENCE FILTERING
5.1.2.2 DI/DO association for SP

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.
5.1.3 Processing of Double Point Status

A DP is derived from two Digital Inputs. One is called the closed contact, the other one is the
Open contact.
Close DI/DO
contact association
From Toggle
acquisition filtering Group
processing
Open Persistance
Manual
contact Toggle filtering
suppression
From filtering Motion
acquisition filtering
Substitution
Transmission – To RCP
Report based To HMI
From IED IED Forcing
To Printer
inputs To Archive
System
Inputs
Transmission –
GOOSE based To
automation
C0134ENa
FIGURE 17: DOUBLE POINT STATUS PROCESSING
DPS are commonly used for all switchgears 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

0 0 Below motion delay, the state is valid motion. For
REPORT no transmission of the transitory state.
After Motion filtering, state is invalid JAMMED
0 1 OPEN
1 0 CLOSE
1 1 UNDEFINED after a permanent filtering
Preliminary treatment (filtering) for some DPs is applied to filter the MOTION state during a
certain period of time. This avoids the transmission of this (normally) transient state.
This treatment is said to be a motion filtering.
• Mode 1: the valid state (OPEN or CLOSE) is stamped with the time of the beginning of
the MOTION state
• Mode 2: the valid state (OPEN or CLOSE) is 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 stamped with the time of the beginning of the
MOTION state. Furthermore, the BI takes the state JAMMED (in case of confirmed
MOTION00 state) or UNDEFINED (in case 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).
The DP resulting states are:
States (report) Goose

JAMMED 11
MOTION 00
OPEN 10
CLOSE 01
UNDEFINED 11
TOGGLING 11
SELFCHECK FAULTY 11
UNKNOWN 11
SUPPRESSED 11
FORCED JAMMED 11
FORCED OPEN 10
FORCED CLOSED 01
SUBSTITUTED JAMMED 11
SUBSTITUTED OPEN 10
SUBSTITUTED CLOSED 01
5.1.3.1 Motion filtering

For some DP, the MOTION state must be filtered on a certain period of time in order to avoid
the transmission of this (normally) transient state.
Two time-out values can be associated with each DP:
• T00: delay for the MOTION00 state filtering
• T11: delay for the MOTION11 state filtering

applied.
• Mode 1: the valid state (OPEN or CLOSE) is stamped with the time of the beginning of
the MOTION state
• Mode 2: the valid state (OPEN or CLOSE) is stamped with the time of this valid
transition
This time stamping can be superseded if a persistence filtering apply.
If the MOTION state is confirmed, it is always stamped with the time of the beginning of the
MOTION state. Furthermore, the BI takes the state JAMMED (in case of confirmed
MOTION00 state) or UNDEFINED (in case 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 of the persistence filtering feature).
OPEN
T00 T00 T11 T11
CLOSE
t0 t1 t2 t3 t4 t5 t6 t7 t8
• t0 : MOTION00 transition
• t1 : MOTION00 state not confirmed, CLOSE state time-stamped t0 if mode 1, t1 if mode 2
(if no persistence filtering applies)
• t3 : MOTION00 state confirmed, state JAMMED time-stamped t2
• t4 : OPEN transition, time-stamped t4 whatever was the mode (if no persistence filtering applies)
• t6 : MOTION11 state not confirmed
• t8 : MOTION11 state confirmed, state UNDEFINED time-stamped t8 C0311ENa
FIGURE 18: MOTION FILTERING
5.1.3.2 DP persistence filtering

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

applied.
• Mode 1: the status is stamped with the time of the transition
• Mode 2: the status is 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 (i.e.
mode 1 of motion filtering cannot apply).
TO TO
OPEN
TC TC
CLOSE
t0 t1 t2 t3 t4 t5 t6 t7
• t0 : CLOSE transition
• t1 : CLOSE state not confirmed
• t2 : CLOSE transition
• t3 : CLOSE state confirmed (stamped t2 if mode 1, stamped t3 if mode 2)
• t4 : OPEN transition
• t5 : OPEN state not confirmed
• t6 : OPEN transition
• t7 : OPEN state confirmed (stamped t6 if mode 1, stamped t7 if mode 2)
C0312ENa
FIGURE 19: DP PERSISTENCE FILTERING
5.1.3.3 DI/DO association for DP

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 of the closure of the output.
The relation between the state and the order is defined during the configuration phase.
5.1.4 Processing of Multiple Point Status

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 cases 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 MiCOM C264 configuration from 2 to 32. There is no GOOSE transmission
mechanism.
An MP can be used in two ways:
• as a status (MPS): in this case, N is up to 16
• as a value, only for TPI: in this case, N is up to 64
contact 1
Toggle
From
filtering
acquisition
contact N Manual
Toggle suppression
From
filtering
acquisition Transmission –
Substitution MP filtering Report based
Forcing
System
Inputs
C0135ENa
FIGURE 20: MULTI POINT STATUS PROCESSING

5.1.4.1 Multiple Point resulting states

The MP resulting states, following the various filters that can be applied, are:
• STATE1 to STATE32
• UNDEFINED
• TOGGLING
• SELFCHECK FAULTY
• UNKNOWN
• SUPPRESSED
• FORCED STATE1 to FORCED STATE32
• SUBSTITUTED STATE1 to SUBSTITUTED STATE32
NOTE 1: State names that will be displayed at the user interface are defined at
configuration time.
NOTE 2: For TPI states, refer to TPI chapter.
5.1.4.2 Multiple Point filtering

MP is not being considered in the UNDEFINED state if the position has changed by more
than one step.
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:
Time-out Time-out
undefined
MP before
filtering
valid
undefined
MP after
filtering valid
C0253ENa
FIGURE 21: MULTIPLE POINT FILTERING

The MP is time-tagged with the date of the last BI change.
5.1.5 System Inputs
System inputs are binary information related to:
• an equipment or system internal state, such as hardware faults or system faults
• a configurable or built-in automation (status of the automation, binary input created by

the automation, …)
• electrical process information which have no acquisition possibilities (i.e. no

acquisition through DI or through serial communication) but which must be managed
by the MiCOM computer: the status of these information are saved in non-volatile
memory.
A SI is of SP, DP or MP type and can belong to any type of group.
The processing of an SI is given in the SP / DP / MP data flow.
5.1.6 IED inputs

These inputs are acquired from IEDs or protective relays via serial links.
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 input is of SP, DP or MP type.
Double inputs can be processed in IEDs. If they are not, the computer must receive each
individual input and perform the DP processing. This must be configured for each IED.
The processing of an IED input is given in the SP / DP / MP data flow.
5.1.7 Group processing
A group is a logical OR, AND, NOR or NAND combination of Binary Inputs (BIs) or groups.
A group component can be a SP, DP (direct or via IED), SI, Group. A component can belong
to several groups.
A group is processed as a SP. It is time stamped with the date / time of the last data-point
which has modified the group status.
A group is calculated with filtered BIs (persistent filtering or motion filtering if configured).
Other computer BIs coming from reports.
The binary inputs states are taken into account as follows:
Single Point Status treated in a group as

SET, FORCED SET, SET
SUBSTITUTED SET
RESET, FORCED RESET, RESET
SUBSTITUTED RESET
SELFCHECK FAULTY, TOGGLING, INVALID
UNKNOWN
SUPPRESSED SUPPRESSED
Double Point Status treated in a group as

CLOSE, FORCED CLOSE, SET
SUBSTITUTED CLOSE
OPEN, FORCED OPEN, RESET
SUBSTITUTED OPEN
JAMMED, FORCED JAMMED, INVALID
SUBSTITUTED JAMMED,
UNDEFINED, SELFCHECK
FAULTY, TOGGLING, UNKNOWN
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
NOT
SET RESET
RESET SET
INVALID INVALID
SP and SI from different hierarchical levels can be mixed, for instance a group at substation
computer level can be composed of SP acquired at bay computer level or at substation
computer level.
A group is time stamped with the date / time of the last datapoint which has modified the
group status.
5.1.8 SBMC Mode Processing
When a Bay is in SBMC mode (Site Based Maintenance Control), the status of the Binary
Inputs (associated 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.
For a group a special feature is implemented: a BI belonging to a group, which 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, which 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.
5.1.9 BI sent to automatism features
In case of automatism running on a client computer, with BI information coming from a
server computer, BI are generally transmitted in the GOOSE based mode. In some cases
where the GOOSE based mode is not used, BI information received by IEC61850 reports
must be used in automatism features.
In any cases where GOOSE based mode and report based mode are used at the same time,
the BI information used is the one receive by GOOSE (faster transmission than reports).
5.2 Measurement Input Processing

Measurement Value can be Analogue Measurement, or Digital Measurement. Analogue
Measurements are acquired from communication or from computer boards (AIU201 or
AIU210 for DC or TMU210 for AC). Digital Measurement comes from Digital input boards.
The processing of a measurement is represented by the following dataflow:
from IED
acquisition
from analogue Open circuit Zero value

acquisition Scaling
management suppression
from digital Threshold

Scaling
acquisition detection
Manual
suppression
from CT/VT CT/VT
Substitution
acquisition calculations
Forcing
Transmission
to:
RCP
HMI
Printer
Archive
Automation
C0136ENb
FIGURE 22: ANALOGUE PROCESSING
5.2.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 considered to be equal to 0 mA.
5.2.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, multisegments
Value = Ai*X + Bi with Xi≤X<Xi+1 .

Up to 20 configurable segments [Xi .. Xi+1]
• Quadratic
Value = A X +B or
Value = AX + B
Transformation law and A / B coefficients are defined in configuration.
5.2.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

Notes: - X is an analogue measurement
- deadband is a percentage of the full scale value of the measurement. These two
parameters have to be set during the configuration of the computer.
Y
Zero value
X Y
suppression
zero suppression area
- deadband/2
+ deadband/2
C0360ENa
FIGURE 23: ZERO VALUE SUPPRESSION

5.2.4 Thresholds detection

Six thresholds can be defined for each measurement: 3 upper and 3 lower thresholds.
A hysteresis value configured on a per measurement basis is associated to the threshold
management.
upper
HYST
t3 t4
t1 t2
HYST
lower
t1 : upper threshold violation

t2 : end of upper threshold violation
t3 : lower threshold violation
t4 : end of lower threshold violation
C0190ENa
FIGURE 24: THRESHOLDS DETECTION
5.2.5 Manual suppression

A measurement can be suppressed by an order issued from an operator. No subsequent
change of value or state on a suppressed measurement can trigger any action e.g. display,
alarm, transmission. The measurement takes the “SUPPRESSED” state. When the operator
unsuppresses the measurement, this one takes its actual state.
5.2.6 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 unsubstitutes it.
When a measurement is substituted, no changes of value nor state are transmitted, and
computations are made with the substituted state. When the measurement is unsubstituted,
the actual state and value are transmitted to higher control levels and subsequent changes
of state and value are transmitted again.
5.2.7 Forcing an invalid measurement

When a measurement is invalid (i.e. SELFCHECK FAULTY, 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 case, the invalid information takes automatically
the FORCED state and the value defined in configuration.
5.2.8 Measurement resulting states

The Measurement resulting states, following the various filters, which can be applied, are:
State Meaning
VALID Not in one of the following states
SELFCHECK FAULTY AI, DI board fault
SUBSTITUTED Operator action set MV value as valid state
FORCED Automatic valid state and configured value when AI 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
UNDEFINED MV is Digital Measurement with invalid coding or computation on
analogue leads to error
OPEN CIRCUIT MV is DC 4-20 mA with input value under 4mA
OVERSHOOT[1..3] One of the 3 overshoot values has been cross
UNDERSHOOT[1..3] One of the 3 undershoot values has been cross
5.2.9 Transmission
The measurement value and state are transmitted on a client-server basis on the Ethernet
IEC-61850 network, using only the report mechanism and Common Data Classes MV, WYE
and DEL.
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 are:
• the real value (i.e. after scaling)
• the resulting state (mapped on the quality field on UCA2)
• the time stamping (in GMT time) and time quality
• the reason for change, which could be one of the below values:
− 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)
A Measurement value can be transmitted periodically or upon variation (% of nominal), and
anyway on state change.
5.2.9.1 Periodic Transmission

Two periods are defined in database, on a per MiCOM 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.
5.2.9.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 from the previously transmitted value (Vt) ( i.e
|Vacq-Vt| > ΔV).
ΔV is theThe minimal variation Δ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 .. 100 and Vt is the last transmitted
value.
or
ΔV = (p/1000) % * |Vmax| where p is a value in the range 0 .. 100 and Vmax is the full scale
value.
for both modes p is in the range 0 .. 255.
5.2.9.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 behaviour if the BI is in this state at the initialisation 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)
5.2.10 CT/VT additional processing

As it is impossible to plug directly the computers on the high voltage electric network, the
information that they receive come from Current Transformers (CT) and from Voltage
Transformers (VT).
From an electrical point of view, the CT and VT have several purposes:
• To deliver a current or a voltage at their secondary, reliable picture of what append in
the concerned high voltage part,
• To make the galvanic insulation between the high voltage part and the measurand and
protection circuits,
• To protect the measurand circuits against damage when a fault comes onto the high
voltage network.
On the output of the CT / VT inputs acquisitions function, I and V signals issued by the CT
and the VT are represented by samples.
The CT/VT calculation function carries out basic mathematical processing on the memorised
samples and gives derived values from I and V such as power, frequency, … This function
then makes it possible to place useful quantities at the disposal of the computer and the
user.
This function is used or computation of measures used for protection modules (overcurrent,
min/max voltage, frequency, etc…) or as information (measurements) for the operator.
5.2.10.1 Inputs
The inputs of the CT/VT Calculation function, issued from the conventional CT/VT inputs,
are:
• 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 V0 (Vr)
− Validity of Ia, Ib, Ic, Ir, Va, Vb, Vc, V0
• In case of delta coupling:
− Samples of Iab
− Samples of Ibc
− Samples of Ica (Ir)
− Samples of Vab
− Samples of Vbc
− Samples of Vca
− Samples of V0 (Vr)
− Validity of each sample.

NOTE: 64 samples per period are available;
5.2.10.2 Outputs
The CT/VT calculation functionality provides:
• RMS values, for currents and voltages
• Frequency of the network
• Active power (total and on a per phase basis)
• Reactive power (total and on a per phase basis)
• Apparent power (total and on a per phase basis)
• Power factor (total and on a per phase basis)
• Phase angles
• Sequence components (Id, Ii, I0, Vd, Vi, V0)
5.2.10.3 Behaviour
5.2.10.3.1 Principle
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).
5.2.10.3.2 Calculation of measurements
Let N be the number of samples recovered for one period of the signal (i.e. 64 samples per
period whatever the network frequency).
All these samples must be gathered in a revolving list stored in active memory. There is thus
in memory an active list of k.N elements. k is the number of sample channels.
Types
The following primary measurements shall be derived directly from sample values:
• RMS Current and Voltage
• Active Power (Watts)
• Vars (Using Active Power calculation method with the voltage samples retarded by
90°)
The following measurements shall be obtained from the Fourier of sample values or the
Fourier values of the above-derived measurements.
• Sequence Components (Id, Ii, I0, Vd, Vi, V0).
• Magnitudes.
• Phase angles.
• Power Factor.
• VA.
Algorithms
Frequency
The frequency is directly computed through the timer frequency.
Fast Fourier Transform
At each period, the FFT (Fast Fourier Transform) is performed. This gives (between other
things) the value of the phase angle and the magnitude of the fundamental.
RMS values
1 63
Vrms = ∑ Vi ²
64 i =0
Powers
1 63
Active power: P = ∑ Vi I i
64 i =0
1 63
Reactive power: Q = ∑ Vi I i−16
64 i =0
NOTE: 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: S = P² + Q²
P
Power factor: cos(ϕ ) =
S
Q
Angle: ϕ = tan −1 ( )
P
Harmonics
Harmonic values are directly issued from the FFT.
Sequence components
The sequence component computation is based on the fundamental values of phase and
magnitude (from the FFT), i.e. its imaginar and real part.
• Direct component
Re( direct ) = × (Re( A) + Re( B) × cos(120) − Im(B) × sin(120) + Re(C ) × cos(120) + Im(C ) × sin(120) )
1
3
Im(direct ) = × (Im( A) + Im( B) × cos(120) + Re( B) × sin(120) + Im(C ) × cos(120) − Re(C ) × sin(120) )
1
3
• Inverse component
Re( direct ) = × (Re( A) + Re( B) × cos(120) + Im(B) × sin(120) + Re(C ) × cos(120) − Im(C ) × sin(120) )
1
3
Im(direct ) = × (Im( A) + Im(B) × cos(120) − Re( B) × sin(120) + Im(C ) × cos(120) + Re(C ) × sin(120) )
1
3
• Homopolar component
Re(direct ) = × (Re( A) + Re( B ) + Re(C ) )

1
3
Im(direct ) = × (Im( A) + Im(B ) + Im(C ) )
1
3
5.2.10.4 Limits and performances

In order to secure proper accuracy for calculations, the sampling frequency must be exactly
adapted to the signal frequency that fluctuates around basic frequency (50 / 60 Hz).
The accuracy shall be:
• 0.5% In for the current (with Measurement CT)
• 0.5% Vn for the voltage (with voltage droppers)
• 0.01Hz for the frequency
• 1° for the angle
• 1 ms for the time
• Up to fifteenth harmonic
• 1% for the power (with Protection CT)

5.2.11 Digital Measurement Processing

A Digital Measurement is derived from a Digital input. Digital Measurements are used for
process measures or Tap indications.
The DM is UNDEFINED in the followings conditions:
• 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 others bits can be used:
• For read inhibit: in this case, the DM is acquired when the Read Inhibit bit is set.
• For the sign

5.3 Tap Position Indication processing
5.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
5.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.
However the tap is considered in the position K if the current is in the range [Ik-ΔI/2 ..
Ik+ΔI/2], with ΔI = N% of (Imax – Imin). The N percentage is defined in configuration.
The tap position is considered UNDEFINED outside of this range.
5.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 e.g. display, alarm, transmission.
The TPI takes the “SUPPRESSED” state. When the operator unsuppresses the TPI, this one
takes its actual state.
5.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 are 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.
5.3.5 Forcing an invalid TPI

When a TPI is invalid (i.e. SELFCHECK FAULTY, 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.
5.3.6 TPI resulting states
The state of a tap position can be:
State Comment
VALID not in one of the below states
SELFCHECK FAULTY Due to an AI board fault or a DI board fault
SUBSTITUTED See § 4.4
FORCED
SUPPRESSED
UNKNOWN If the tap position is acquired via a transmission link, the
information is unknown when the link is disconnected.
UNDEFINED Due to a wrong encoding for a digital acquisition, or a saturation,
an open-circuit or an out-of-range value for an analogue
acquisition
OVERSHOOT[1..3] It exists 3 “Overshoot” states, one for each upper threshold
violation. Only one could be set at one time
UNDERSHOOT[1..3] It exists 3 “Undershoot” states, one for each lower threshold
violation. Only one could be set at one time
5.3.7 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 UCA2)
− change of data (set if the value has changed)
− change of quality (set if the quality has changed)
− change due to control (set if the state or quality change is due to a control)
5.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 which 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).
5.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 IEDs
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:
E = ∑ Ei
⎛ ( M + M i −1 ) (ti − ti −1 ) ⎞
Ei = S f * ⎜ i * ⎟
⎝ 2 3600 ⎠
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.
WARNING: THE ENERGY COUNTER VALUES ARE NOT TO BE USED FOR BILLING
APPLICATION.
6. CONTROL SEQUENCES
6.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 feed back from protocol or
from DI.
6.1.1 General
The C264 allows the following functions:
• Control of switching devices (circuit breaker, switch, …)
• Control of transformers
• Control of secondary devices
• Locking of switching devices
• Control of IEDs
• 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 behaviour is different according to:
• The configuration of the device control,
• The type of the device,
• The computer operating mode.

6.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 must be selected before allowing the execution. In that
event the device is managed in two phases: selection and execution. Device
unselection is done automatically by the computer.
• “Select Before Operate many” (SBO many): usually for transformers. The device
must 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 unselection. The execution phase is repeated for every new control. To
end the controls sequence, the initiator of the request must send an “unselection”
request.
By configuration, each DPC order (close order or open order) and each SPC can activate
simultaneously two DO contacts.
6.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 more or less important depending on the device:
• Synchronised or not synchronised circuit breakers, disconnectors and earthing
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.
6.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 unselection)
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).
positive acknowledgement and the control sequence ends. In event of abnormal
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)
positive acknowledgement and waits a new execution request. In event of abnormal
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.
Direct execute Execution via
mode I/O boards
or
Execution Execution via

MiCOM C264P
checks IED
or
System
Functional Description
controls
execution phase
Select Before Operate

mode
Execution via
I/O boards
Selection Execution
or
checks checks
Execution via
IED
selection phase execution phase
Select Before Operate mode many

with device selection
The following figures show the three control modes of the computer:
Execution via
FIGURE 25: CONTROL MODES OF THE COMPUTER (1)

I/O boards
Selection Hardware Execution Hardware
or
checks selection checks Deselection
Execution via
IED
C0314ENa
selection phase execution phase
C264P/EN FT/C80
Page 67/166
Execution via
Select Before Operate mode many
I/O boards
Execution or
checks
Execution via
Page 68/166
IED
Device
Device
Selection
unselect
C264P/EN FT/C80
checks
Execution via
I/O boards
Execution
or
checks
Execution via
IED
selection phase execution phase (1) unselection phase
Select Before Operate mode many Execution via

with hardware device I/O boards
Execution or
checks
Execution via
IED
Selection Hardware Hardware Device
checks Selection Deselection unselect
Execution via
FIGURE 26: CONTROL MODES OF THE COMPUTER (2)

I/O boards
Execution
or
checks
Execution via
IED
selection phase execution phase (1) unselection phase
(1) An execution phase with two execution requests is given as an example, it may have more or less
C0315ENa
MiCOM C264P
Functional Description
6.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 “unselect” request has no meaning in ”Direct
Execute” mode.
Direct execution request start of

sequence
no
device direct execute
yes
execution already in
progress ?
execution in progress
Perform execution
checks
no
All checks OK
Perform execution
no
Execution OK
yes
End CO in progress End CO in progress
send negative send positive

acknowledge acknowledge
End of
sequence
C0316ENa
FIGURE 27: EXECUTION PHASE FOR DIRECT EXECUTE MODE

6.1.4 SBO once mode
6.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 fails cause. 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 unselected 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 taken into account (none acknowledgement is sent)
whichever of the initiator.
The diagram that follows shows the selection phase of a device configured in SBO once
mode.
Unselected
device
Selection request
no
Device selectable ?
yes
Device Already
selected
Perform Selection
no checks
All checks OK
Device selection
no
Device selection OK
Set “device selected”
send positive
acknowledge
Selection Time-out
launching
Wait new request

or time-out
Time-out
Cancel request
Deselect hardware
selection Device
Execution request
Set “device
unselected”
send negative
acknowledge
Execution
phase
C0317ENa
FIGURE 28: SELECTION PHASE IN SBO ONCE MODE

6.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).
EXECUTION PHASE IN SBO ONCE MODE Execution request –SBO

once device selected
yes
Execution in progress
to the device
Perform execution
checks
send negative
acknowledge no
All checks OK
Operator
Cancel request
Perform execution
no
Execution OK
yes

Reset execution in
progress
deselect the device
End of
sequence
C0318ENa
FIGURE 29: EXECUTION PHASE ON SBO ONCE MODE

6.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.
6.1.5.1 Selection phase in SBO many mode

The selection phase is identical to the “SBO once” mode selection phase.
6.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
“unselect” request. The execution phase ends only after an “unselect” request or “cancel”
request by the initiator.
Upon reception of an “unselect” request the computer ends the execution phase and goes
to the selection phase.
Execution Phase SBO many Execution phase- device

SBO many selectd
Wait request
Execution request
Unselect request cancel request
no
Device selected
yes
Execution in progress
to the device
Perform execution
send negative checks
acknowledge
no
All checks OK
Perform execution
no
Execution OK
yes

Reset execution in
progress
Deselect the device
Unselection
phase
End of
sequence
C0319ENa
FIGURE 30: EXECUTION PHASE IN SBO MANY MODE

6.1.5.3 Unselection phase in SBO many mode

The computer deselects the device and sends a positive acknowledgement.
Unselection Phase SBO many Unselection phase
hardware selection
Error during
Not configured
deselection
Deselect the device
Send negative Send positive

Set « device
deselected »
End of sequence
C0320ENa
FIGURE 31: UNSELECTION PHASE IN SBO MANY MODE
6.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
Next diagram schematises controls and bypass according the description of the device.
Selection checks for SBO device Unselected device
Inter-control delay Not configured

expired
yes
yes
Computer faulty or in
maint
no
no Substation and bay Not configured

mode OK
Bypass mode checks yes
no
Interlock checks
OK Not configured
no
Bypass interlock yes
checks
yes
Not configured
Automatism running
Bypass automatism no
no
Device selectable
yes
Device locked Not configured
no
no
Bypass locked device
no Not configured
Current status of the
device OK
yes
no Uniqueness
OK Not configured
no
Bypass uniqueness yes
check
Abort
selection Continue
selection
phase
phase
C0321ENa
FIGURE 32: SELECTION CHECKS FOR SBO DEVICE

6.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.
6.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.
• Faulty mode: no control is accepted when the computer is in this mode.
• Changing mode:
− 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.
− From “operational” mode to “maintenance” mode: all device controls in

progress are aborted and no acknowledgement is sent.
6.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 acknowledgement.
6.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.
6.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 automatism state
(active/inactive) can be used to prevent manually control execution in event an automatism
is active for device monitoring: for example, ATCC.
In this event the sequence is aborted with a negative acknowledgement, except if the user
asks to bypass this check.
6.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.
6.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.
6.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
6.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.
A
Uniqueness does not be checked for
this device or uniqueness is bypass
Uniqueness must be checked for this
device and there is no bypass
→ Goose is sent to other bays

D
B
Uniqueness check is OK
No control on going inside the One control on going

substation ( corresponding DI in OFF inside the
or invalid states) substation
Uniqueness check is NOK

→ Goose is sent to other bays in
C order to ask for the token
← A goose is received from an Time out (defined in

other bay which also requires database)
the uniqueness token
Uniqueness check is OK
Uniqueness check is NOK

C0322ENa
FIGURE 33: 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.
6.1.7 Selection behaviour

In SBO once mode and SBO many mode, the configuration process allows to describe
optionally, a device selection to control the device.
The following configurations must 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
1. verifies the selection position information, it must be open: if it is close, it is an
abnormal situation, the selection sequence is stopped with a negative
acknowledgement.
2. 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).
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 acknowledgement. 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 acknowledgement.
• 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 acknowledgement 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 acknowledgement.
6.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.
6.1.9 Execution behaviour

On this stage the control request is executed via:
• I/O boards
• IED communication
• System supervisor of the computer for system outputs

The execution via I/O boards is performed only if the computer is in “operational” mode. If
the computer is in “test” mode, the output relay is not set. In this event the computer
simulates a positive acknowledgement of hardware execution. It allows to perform control
sequence safety in order to test Automatisms configuration, control sequence configuration
etc. Controls to IEDs are sent if the computer is in “operational” mode or “test” mode.
6.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
• Double Control Points
• Digital Setpoints
• Analogue Setpoints
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 the 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 must be configured.
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.
A C264 can have 256 numbers of Digital or Analogue Setpoints
6.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.
6.1.9.3 System controls execution

For systems outputs the computer activate/deactivate the associated function (ATCC,
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.
6.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
• Destination: I/O board, IED
• Time-out delays: selection phase time-out, selection Feedback delays, open/close

Feedback delay and so on.
6.1.10.1 Direct execute time sequencing

The chronogram shows an example of normal termination on Direct Execute sequence.
DPC open
(resp. close)
DPS open/ resp close
(close/ resp open)
Feedback Delay
CO Pulse Delay
0-60s
0-5s
3 4 5
1 execution request C0323ENa
FIGURE 34: 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.
DPC open
(resp. close)
SPS close
(resp. open)
SPS open
(resp. close)
Feedback Delay
CO Pulse Delay
0-60s
0-5s
3 4 5
FIGURE 35: ABNORMAL TERMINATION OF DIRECT EXECUTE SEQUENCE

6.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.
Selection of the
device
Selection position
input
Device output control
Device status
Open/Close Selection
Selection
Feedback Feedback
Feedback
Selection time-out Delay Delay
Delay
0-60s
0-1 s 1-10mn 0-1 s
2 5
1 3 4
Selection phase Execution phase
C0325ENa
FIGURE 36: 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 deselect 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 37: ABORTED CONTROL SEQUENCE

• Stage 2: the selection is confirmed by the associated input information in the feedback
delay.
• 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.
Selection of the
device
Output Control Of
The Device
Device status
Open/Close
Feedback
Selection time-out Delay
0-60s
1-10mn
1 2 3
Execution phase
Selection phase
C0327ENa
FIGURE 38: NORMAL TERMINATION OF THE CONTROL SEQUENCE
• Stage 2: close the device before the end of the selection timeout delay (0 – 10 MN
user selectable)
• Stage 3: The device has taken the expected position (close) in the feedback delay (0–
1-sec user selectable). The computer deselect the device (open selection output
control)
6.1.10.3 SBO many time sequencing
SBO many mode is exclusively used for control of transformers. Refer to associated section.
6.1.11 How an xPS starts a control sequence

Control sequence launched by an xPS
The xPS 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 IEC61850 or the local C264 HMI. The sequence
cancel is not allowed. Only Direct Execute (DE) control types are allowed.
The xPS launches xPC (Direct Execute) with "control sequence activating Yes/No”
Value of
Activate control
xPS State xPC state Action
sequence in
SCE
YES SET xPS Open xPS launches xPC
YES RESET xPS Close xPS doesn’t launch xPC
NO SET xPS Open xPS launches xPC
NO RESET xPS Close xPS launches xPC
Configuration of Control Sequence launched by an xPS

The configuration of this function is performed by using the «control on state change »
relation with a new attribute “control” which can have “direct to output relay” or “through
control sequence” values. If “through control sequence”, the xPS activates a full control
sequence. If “No”, the xPS activates directly the associated xPC.
FIGURE 39: CONFIGURATION OF CONTROL SEQUENCE ACTIVATION
This datapoints can be wired or defined as outputs of configurable automations (PSL,

ISaGRAF).
• xPS output of PSL launch SPC/DPC
• xPS output of ISaGRAF launch SPC/DPC

The control is launched when the xPS becomes SET, after all xPS filtering (all others states
are ignored).
• The state of xPS is SET only after the time delay is obeyed when delay values of
Debouncing, filtering, toggling and toggling end of the C264 is set to its maximum,
minimum and an intermediate value possible within the specified range
The filtering delay is configured in the C264 attributes in SCE.
FIGURE 40: CONFIGURATION OF BI FILTERING IN CONTROL SEQUENCE

Control Sequence launched by xPS with Control Originator Fields

In case of controls launched by an xPS, the Control Originator fields are:
• orCat = Bay level
• orIdent = xPS label
• The xPC Control launched by bay xPS changes control originator field orCat to Bay
Level and orIdent to xPS label
NOTE 1: Usage of order labels in profile for SPC in SCE, "order on" and "order
off" should be "Yes".
NOTE 2: “Control Sequence Activating” attribute for SPC and DPC = "Yes".
Control Sequence launched by xPS priority management
An optional « synoptic Local/Remote (L/R) » is defined 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 synoptic Priority 2 n/a Local
Control authorized -> LCD xPS
Control is authorised 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 C264.
Control is authorised 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 synoptic Priority 1 Local Remote
Control authorized -> xPS LCD
Control is authorised by xPS and not by computer LCD when Bay L/R is priority 2 with
operating mode not taken into account by C264 and Synoptic L/R is priority 1and operating
in Local Mode.
Control is authorised 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 SCE:
FIGURE 41: 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.
SPS, DPS and MPS

SCE ISaGRAF
Status Status DINT
Quality Quality DINT
GlobalAlarmStatus Alarm SINT
Status attribute for SPS

• RESET / FORCED RESET / SUBSTITUTED RESET = 1
• SET / FORCED SET / SUBSTITUTED SET = 2
Status attribute for DPS
• MOTION 00 = 3
• OPEN / FORCED OPEN / SUBSTITUTED OPEN = 4
• CLOSED / FORCED CLOSED / SUBSTITUTED CLOSED = 5
NOTE: UNDEFINED state is seen as INVALID (see Quality attribute)
Status attribute for MPS
• State1 / FORCED state1 / SUBSTITUTED state1 = 7
• State6 / FORCED state6 / SUBSTITUTED state6 =12
• State7 / FORCED state7 / SUBSTITUTED state7 =13
Quality attribute
• VALID = 0
• SELFCHECK FAULTY = 1
• UNKNOWN = 2
• FORCED = 4
• SUPPRESSED = 8
• SUBSTITUTED = 16
• TOGGLING = 32
If Quality attribute is INVALID, Status attribute is non-significant.
Alarm attribute
Unusable
6.2 Control of non synchronised breakers

6.2.1 Non synchronised 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 ONE PHASED CIRCUIT BREAKERS

OUTPUTS OUTPUTS CB INPUTS CB OUTPUTS CB OUTPUTS INPUTS
CB TYPE A TYPE B (4) ALL TYPES TYPE A TYPE B (4) ALL TYPES
DEVICE DPC SPC control DPS physical DPC control DPC control for SPS/ DPS
CONTROL control for for open of position of the for open/close open phase A physical position
open/close device device(1 phase) of device of phase A
DPC control for
of device
SPC control SPS (optional) open phase B SPS/ DPS
for close of phase not (pulse) physical position
device together of phase B
DPC control for
information
open phase C SPS/ DPS
system DPS the physical position
DPC control for
feedback of the of phase C
close of device
control (1)
system SPS
phase not
together
information (2)
system DPS:
the feedback of
the control (3)
DEVICE SPC /DPC SPC /DPC SPS /DPS SPC /DPC SPC /DPC SPS /DPS
SELECTION (optional) (optional) (optional) device (optional) (optional) control (optional) device
control of control of selection control of of device selection
device device position device selection position
selection selection information selection information
(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 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
6.2.2 Control sequence of non-synchronised circuit breakers
Circuit breakers devices are managed in ”Direct Execute” mode and in “SBO once” mode.
Refer to the generic description above.
6.3 Control of synchronised breakers

Circuit breakers devices are managed in “SBO once” mode only. The following paragraph
describes the specific features of synchronised circuit breakers whether are synchronised by
an external or internal synchrocheck module.
6.3.1 Synchronised 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 ONE PHASED CB

OUTPUTS OUTPUTS CB INPUTS CB OUTPUTS OUTPUTS INPUTS ALL
CB TYPE A TYPE B (6) ALL TYPES (6) TYPE A TYPE B TYPES
DEVICE DPC control SPC control SPS/DPS DPC control SPC/DPC SPS/DPS
CONTROL for for open of physical for control for physical
open/close device position of the open/close open phase position of
of device device (1 of device A phase A
SPC control
phase)
SPC/DPC for close of SPC/DPC SPC/DPC SPS/DPS
control for device SPS (optional) control for control for physical
close with phase not close with open phase position of
SPC/DPC
synchrocheck together synchrocheck B phase B
control for
(5) information (5)
close with SPC/DPC SPS/DPS
synchrocheck system DPS control for physical
(5) optional): the open phase position of
feedback of C phase C
the control (1)
SPC/DPC system
control for SPS/DPS
close of phase not
device together
information (2)
SPC control
for close with system DPS:
synchrocheck the feedback
of the control
(3)
DEVICE SPC SPC (optional) SPS (optional) SPC SPC SPS (optional)
SELECTION (optional) control of device (optional) (optional) device
control of device selection control of control of selection
device selection position device device position
selection information selection selection information
SYNCHROCHEC SPC/DPC SPC/DPC SPS/DPS SPC/DPC SPC/DPC SPS/DPS
K SET ON/SET (optional) (optional) (optional) (optional) (optional) /DPS(optional)
OFF (4) control of control of ON/OFF control of control of ON/OFF
ON/OFF ON/OFF synchrocheck ON/OFF ON/OFF synchrocheck
synchrocheck synchrocheck information synchrocheck synchrocheck information
(1) The computed double signal is equal to the physical status if the phase not together
(2) The computed “phases not together” is equal to “false” if all phases are in the same
(3) The computed signal is equal to the phase A status if the phase not together status is
(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 automatism is considered always “set on”. DPC and DPS are used only
for manual synchrocheck.
For external synchrocheck only.

“Open” control sequence of synchronised circuit breakers remains identical to the non-
synchronised 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 automatism
A Close control sequence can be configured with:
• Manual set on of the external synchrocheck module or internal synchrocheck

automatism
• Automatic set on of the external synchrocheck module or internal synchrocheck

automatism
Furthermore, waiting closes the CB by the external module the initiator of the request may:
• Cancel the request
• Close the device by forcing request
6.3.2 Circuit breakers with external synchrocheck
6.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.
SPC close with SPC Select device

synchrocheck C26X
CIRCUIT
SPC/DPC ON/OFF BREAKER
(1) synchrocheck Synchro
(2) Check
(3) Module
OI SPC Close with

synchrocheck
or SPC/DPC
MES/MHS
GATE synchrocheck
WAY
DPC open/Close
device
select close
Execute close (x) sequences order
force close
C0328ENa
FIGURE 42: CLOSE CB BY EXTERNAL SYNCHROCHECK WITH AUTOMATIC SET ON
The “close” control sequence performed on the 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
acknowledgement
Execution phase:
1. Close the device using synchrocheck output control
2. Verify the device position become close in the given delay
3. Set off synchrocheck module if it previously set on
4. Deselect the device if it previously selected
The chronogram that follows shows a successful control sequence ”close with
synchrocheck”.
SPC ON/OFFt Sync
SPS ON/OFF Sync
SPC select
SPS select
SPC sync close
DPC open/close
device
DPS open
close
Feedback Feedback Feedback for DO

Delay Delay Selection timeOut sync close
0-1 s 0-5 s 0-10mn 0-60mn

1 2 3 4 5
1 selection request 3 execution request 5 End of control

C0329ENa
FIGURE 43: CHRONOGRAM OF A SUCCESSFUL "CLOSE WITH SYNCHROCHECK"
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 acknowledgement, deselecting previously
synchrocheck and device.
SPC ON/OFF Sync
SPS ON/OFF Sync
SPC select
SPS select
SPC sync close
DPC open/close
device
DPS open
close

0-1 s 0-5 s 0-10mn 0-60mn

1 2 3 4 5

C0330ENa
FIGURE 44: ABNORMAL TERMINATION OF "CLOSE WITH SYNCHROCHECK"

6.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 OI or
gateway manually manages the external synchrocheck module.
DPC open/close
device SPC Select device
C26X
CIRCUIT
(2) SPC/DPC ON/OFF BREAKER
(3) synchrocheck
(4) Synchro
Check
(1)
Module
OI SPC/DPC “SET SPC/DPC Close
or ON” synchrocheck with synchrocheck
GATE
WAY
(5)
SPC/DPC “SET
OFF”synchrocheck
(optional)
DPC open/Close
device
Direct execute The external synchrocheck module is set off automatically at the
end of the SBO sequence (if it is configured)
select close
Execute close
(x) sequences order
force close
C0331ENa
FIGURE 45: 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
acknowledgement
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)
4. In event of fail of one of these operations the controls sequence is stopped with a
negative acknowledgement
Execution phase:
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 remain identical. It is performed at the end of the SBO
sequence.
SPC ON/OFF Sync
SPS ON/OFF Sync
SPC select
device
SPS select device
SPC sync close
DPC open/close
device
DPS open
close

0-1 s 0-5 s 0-10mn 0-60mn

3
1 2 4 5 6
1 DE request set on 3 selection request : 4 execution request 5 DE request set 6 End of control
synchrocheck close the device off synchrocheck
C0332ENa
FIGURE 46: SUCCESSFUL CLOSE WITH SYNCHROCHECK
NOTE: During SBO sequence after step 5 the initiator of the request may
force the closing of the device.
6.3.2.3 Close synchronised 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”
SPC select Sync

(optional)
SPS select Sync

(optional)
SPC select
(optional)
SPS select
(optional)
SPC sync close
Forcing on DPC
close : DPC close
is set
SPS open
close
Feedback Delay Feedback Selection Timeout Feedback for DO sync close Feedback
Delay Delay
0-1 s 0-5 s 0-10mn 0-60mn 0-20s

1 2 3 4 5 6
3 execution request 4 synchrocheck bypass 5 End of control

1 selection request C0333ENa
FIGURE 47: ”CLOSE WITH SYNCHROCHECK” WITH “FORCING CLOSE REQUEST”
6.3.2.4 Cancel Close CB with external synchrocheck

Awaiting close the device (0 to 60 a MN) 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.
SPC select Sync
SPS select Sync
SPC select
SPS select
SPC sync close
DPS open
close
Feedback Feedback FeedBack Delay

Delay Delay Selection timeOut
0-1 s 0-5 s 0-10mn 0-60mn

3 4 5 6
1 2

4 Operator « CANCEL »
C0334ENa
FIGURE 48: CANCEL CLOSE REQUEST

6.3.3 Circuit breakers with internal synchrocheck

On this configuration synchrocheck is assumed by an internal computer automatism, that
proceeds to the synchrocheck voltage calculations and gives or not the authorisation to close
the device.
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
6.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 automatism is set on automatically.
In “Direct Execute” mode the processing remain similar without selection of the device.
SPC/DPC system
ON/OFF fonction
synchorcheck
SPC/DPC close
with synchrocheck SPC Select device
C26X
CIRCUIT
(1) BREAKER
(2) Fonction
(3) Synchro
Check
OI
or SPC/ DPC system
GATE Close with
WAY synchorcheck
DPC open/Close
device
select close
(x) sequences order
Execute close
force close
C0335ENa
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 acknowledgement.
Execution phase:
1. Active the associated internal synchrocheck automatism for authorisation to close the
device
2. Wait authorisation to close
Event 1: Synchrocheck automatism respond OK before the time-out of the given
delay
1. Close the device
2. Deselect the device (if it was previously selected)
3. Send a positive acknowledgement
Event 2: Synchrocheck automatism responds NO before the time-out of the given

delay
2. Send a negative acknowledgement
Event 3: time-out of the given delay without synchrocheck response
1. Stop the synchrocheck automatism
Event 4: reception of cancel request awaiting synchrocheck response
The chronogram that follows shows a successful control sequence ”close with internal
synchrocheck”.
SPC select
SPS select
Close/open
Device control
DPS open
close
Feedback Feedback feedback Delay

Delay Delay Selection time-out
0-1 s 0-5 s 0-10mn 0-60mn

1 2 3 4 5
1 selection close request 3 execution request 5 End of control

C0336ENa
The chronogram that follows shows an abnormal termination of control sequence ”close with
internal synchrocheck”.
SPC select
SPS select
Close/open
Device contro
DPS open
close

0-1 s 0-5 s 0-10mn 0-60mn

1 2 3 4 5
1 selection close request 3 execution request 5 End of control

C0337ENa
6.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 automatism is set on by a separate
direct execute control.
SPC/ DPC Close

with synchrocheck
SPC open/close SPC Select device

device C26X
CIRCUIT
(2) BREAKER
(3) Synchro
(4) Check
Module
OI SPC/ DPC set on

synchrocheck
or (1)
GATE
WAY
(5)
SPC/DPC set off

synchrocheck DPC open/Close
device
Direct execute
The external synchrocheck module is set off automatically at the
select close end of the SBO sequence (if it is configured)
Execute close
(x) sequences order
force close C0338ENa
First sequence (DIRECT EXECUTE): Set on the internal synchrocheck automatism:

1. Set on synchrocheck automatism 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:
4. In event of fail of one of these operations the controls sequence is stopped with a
negative acknowledgement
Execution phase:
5. Ask to the internal automatism to close the device
NOTE: The initiator of the request may force the closing of the device.
7. Set off the synchrocheck automatism if is configured to be set off automatically
Third sequence (DIRECT EXECUTE): set off the internal synchrocheck automatism
This sequence occurs only if the setting off of the synchrocheck automatism is
configured “manual”
1. Set off synchrocheck automatism
2. Reset system input “on/off synchrocheck” (if it is configured)
6.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
2. Close the device
4. Send a positive acknowledgement
SPC select
SPS select
Close via output

control
DPS open
close

0-1 s 0-5 s 0-10mn 0-60mn

1 2 3 4 5
6
C0339ENa
6.4 Control of disconnectors
6.4.1 Disconnectors features

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
6.4.2 Control sequence of disconnectors

The control sequence of disconnectors is identical to control sequence of the non-
synchronised circuit breakers.
6.5 Control of transformers
6.5.1 Transformer features
OUTPUTS INPUTS
TRANFORMER DPC: raise/lower TPI value
CONTROL
SPS (optional) tap change in progress
(TCIP)
TRANSFORMER SPC (optional) transformer SPS (optional) selection position
SELECTION selection information
TRANFORMER Double wound or Auto-wound
TYPE NOTE 1
NOTE 1: 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 tension.
Auto-wound (or auto-transformer or single wound) is a transformer without galvanic
isolation between primary and secondary. Secondary coil follows primary coil, (winding 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.
6.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 position of the tap.
• 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 automatism 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 must appear before the time-out of this
delay.
• TCIP disappearance delay: The TCIP information must 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 must 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 unselect order sent by the initiator of the control request.
6.5.2.1 Control of transformer with TCIP
In this mode, when the TCIP input information is configured, the selection and execution
phase are performed as follows: It is possible by configuration to prevent to have more than
one control at a time.
Selection phase:
1. Close device selection output to select the device (if 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, the controls
Execution phase:
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
acknowledgement and waits a new request (execution or unselection).
• 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
acknowledgement.
6. Wait for the new execution request or unselection request to deselect the device
• In event of new request the computer repeat the steps 4 and 5.
• In event of unselection request the computer deselects the device (if it

was previously selected), and ends the sequence with a positive
acknowledgement
The chronogram that follows shows a successful sequence with device selection, two “raise”
controls and device unselection
SPC select
(optional)
SPS select
(optional)
DPC raise/lower
OPEN
TPI Value
(1)
raise/lower
CLOSE
SPS TCIP
FeedbackSelection TCIP
Pulse
Delay timeOut disappearance FeedBack
Delay
time Delay Delay
0-5 s 4
0-1 s 0-10mn TCIP apparition 0-1 s 0-1 s

time Delay
11 End of control
1 2 3 0-5 s
4 5 6 7 8 9 10 11
1 selection “raise” request
3 first execution 6 second execution 10 unselect request
request request
C0340ENa
NOTE (1): The TPI value must 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 acknowledgement
SPC select
(optional)
SPS select
(optional)
OPEN
raise/lower
CLOSE
SPS TCIP
TIP value
Feedback Selection FeedBack

Pulse
Delay timeOut Delay
Delay
4
0-5 s
0-1 s 0-10mn 0-1 s
TCIP apparition time
1 2 Delay 5 6
1 selection request “raise” 6 End of control
3 0-5 s
6.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, the controls
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 must
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 acknowledgement and waits a new request
(execution or unselection) 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 acknowledgement.
6. Wait for the new execution request or unselection request to deselect the device
• In event of new request the computer repeat the steps 4 and 5.
• In event of unselection request the computer deselects the device (if it was
previously selected), and ends the sequence with a positive
acknowledgement.
The chronogram that follows shows a successful sequence with device selection, a raise
control and device unselection
SPC select
(optional)
SPS select
(optional)
DPC raise/lower
OPEN
raise/lower
CLOSE
TPI
feedback
Feedback Selection Delay
Pulse
Delay time-out
Delay
4
0-5 s
0-1 s 0-10mn 0-1 s
new TPI value
1 2 Delay 6
1 selection “raise” request 7 End of control
6 Unselect request
3 0-5 s 5
3 execution request
C0342ENa
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 acknowledgement.
SPC select
(optional)
SPS select
(optional)
DPC raise/lower
OPEN
raise/lower
CLOSE
TPI
Feedback Selection FeedBack

Pulse Delay
Delay timeOut
Delay
4
0-5 s
0-1 s 0-10mn 0-1 s
new SPI value
1 2 Delay 6
1 selection request “raise”
6 End of control
3 0-5 s 5
3 execution request
C0343ENa
6.5.2.3 Suppression, Forcing or Substitution of the TPI

In event of suppress or substitution of TPI value the control sequence is aborted with
negative Acknowledgement. In event of Forcing the sequence is not aborted but the value of
TPI taken in account during the control sequence is the forced value.
6.6 Control of ancillary devices
Ancillary devices are managed in “Direct Execute” or in “SBO once” mode. Refer to
generic explanations above.
6.7 Control of Intelligent Electrical Devices (IED)
6.7.1 Control to IEDs

Control requests to manage device via IEDs may be performed in the three modes (DE,
SBO once, SBO many).
6.7.1.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 acknowledgement 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 acknowledgement.
Otherwise the sequence ends with a positive acknowledgement.
6.7.1.2 SBO once mode

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

After you perform the selection checks
1. The computer sends a selection request to the IED,
2. Expects selection acknowledgement from IED in the given delay,
3. Generates a positive or negative selection acknowledgement according to the result
of the selection phase,
4. If positive acknowledgement, the computer starts selection time-out and waits
execution request, otherwise ends the controls sequence.
6.7.1.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
acknowledgement 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 acknowledgement. In event of a failure in
step 6 or 7, the sequence ends with a negative acknowledgement.
6.7.1.3 SBO many mode

In comparison with the “SBO once” mode, in this mode execution phase is repeated until an
unselection request. Unselection request allows you to end the sequence in the computer,
and it is not sent to the IED.
6.7.2 IED controls
6.7.3 Digital setting point (SP)
6.8 System controls

System control is used to activate or deactivate automatic functions, change computer’s
mode, bay mode, database management, etc.
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 automatism’s 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 initialisation, they are restored.
6.9 Kinds of control sequences

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

System control is used to activate or deactivate automatic functions, change computer’s
mode, bay mode, database management, etc.
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 automatism’s 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 initialisation, they are restored.
6.11 Kinds of control sequences

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

Receiving control, the control sequence executes configured checks:
Operational conditions
• 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.
6.12.1 Mode Management

Control sequences are only performed if the computer mode is in operational mode. In test
mode, control sequences are allowed but digital outputs are not set.
6.12.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.
6.12.3 Control mode

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

PACIS Gateway),
• Legacy BUS (from One Box Solution IED).

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.
6.12.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 acknowledgement. The user may bypass this control during selection
request.
6.12.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.
6.12.6 Status of the device

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

Controls are not allowed on a lock device.
6.12.8 Running Automation

If there is a related automation in operation, controls are not allowed on a device.
For example controls issued from PACiS OI or gateway are not allowed on a transformer
controlled by voltage regulation.
6.12.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 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.
6.13 HV Control Sequences
6.13.1 Circuit breaker

Several kind of circuit breaker can be managed:
• Three phases or single phase circuit breaker,
• Synchronised or non-synchronised, with internal or external synchrocheck,
• With and without Auto Recloser.

For three 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.
6.13.2 Disconnector
The control sequence of disconnectors is identical to single non-synchronised circuit
breakers.
6.13.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, also its Raise and Lower controls are defined for secondary
voltage (and not tap position). Except for auto wounded transformer, raise/lower voltage is
also a raise/lower tap.
7. AUTOMATIONS
C264 provides three different ways to perform automation functions:
• Programmable Scheme Logic (PSL) (True for all C264 except for the C264
Standalone)
• Programmable Logic Controller (PLC)
• Built-in automation functions

The choice between these three solutions depends on time and complexity.
7.1 Built-in Automation functions

Within the C264, some built-in automation functions are available and you can set them
directly:
• Auto-Recloser
• Trip Circuit Supervision
• Circuit Breaker Condition Monitoring (I2t)
• xPS/xPC Association
• Pole Discrepancy
7.1.1 Auto-Recloser (AR)
7.1.1.1 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.
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 the majority of 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. (A 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). (This is a Closed/Open/Closed/Open, 4 cycle system).
Auto-recloser (AR) schemes are implemented to carry out this duty automatically.
7.1.1.2 Behaviour
The general diagram of the auto-recloser function follows:
Auto-recloser out
of service
In Service request
Auto-recloser in
service
TRIP /TRIP_1P_X
3 phases
no 1 phase
CB_HEALTHY Analysis of the CB_HEALTHY no
Cycle n˚=1
= SET ? received trip = SET ?
yes yes
Waiting CB Waiting CB
opening opening
End of 150 ms timer End of 150 ms

CB open timer CB open
AR locked AR locked
Launch cycle timer Launch cycle timer
(for first single- (for 3-phases cycle)
phase cycle)
TRIP
TRIP_1P_X always set
End of
End of TRIP always set
timer
timer AR locked
AR locked
AR_BLOCKING no
AR_BLOCKING
no = RESET ?
= RESET ?
yes
yes
Closing the CB
Closing the CB
CB closed TRIP New CB

TRIP closed
Launch Cycle = cycle +1

recovering timer
Launch
recovering timer
End of TRIP
timer
Cycle n˚=2
TRIP End of
timer
no
Last cycle?
yes
AR locked
C0137ENa
FIGURE 49: AUTO-RECLOSER SCHEME LOGIC
7.1.1.2.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 authorised.
If an out of service request is received during an auto-reclosing cycle, the cycle is
immediately stopped.
7.1.1.2.2 Analysis of the receiving trip

This analysis allows you to detect the type of auto-recloser cycle, that can be:
• The first single-phase cycle
• The first 3-phases fast cycle
• The second 3-phases slow cycle
• The third 3-phases slow cycle
• The fourth 3-phases 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-
phases trip)
• The configured auto-recloser cycles

During this phase, if the CB_HEALTHY signal is not in the SET state, the cycle is not
authorised and the automation re-initialises to wait for the first cycle. The CB_HEALTHY BI
is optional: if it does not exist, no check is done.
7.1.1.2.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-phases 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-phases 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.
7.1.1.2.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-phases trip could appear. In this event, the current
cycle is stopped and the second 3-phases slow cycle is launched.
7.1.1.2.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-phases slow cycles. The use of
the synchrocheck function during the first 3-phases fast cycle is configurable.
If the AR_BLOCKING BI is in another state, the automation is re-initialised to wait for the first
cycle.
7.1.1.2.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.
7.1.1.2.7 Particular treatments
Reclaim time on manual close
If the CB becomes closed (through an external manoeuvre) during an auto-recloser cycle,
the Reclaimmc 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 SI 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 substitued)
• 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-phases
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.
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 Reclaimml timer is launched. If
the CB is not closed at the end of this timer, the auto-recloser is locked again.
7.1.1.3 Information and parameters
Information Description Type

CB_STATE_1P_x CB status, on a per pole basis BI (DP)
CB_STATE CB status (global) BI (DP)
TRIP_1P_x Trip status, on a per pole basis BI (SP)
TRIP 3-phases Trip status BI (SP)
AR_IS/OS Request to put in / out of service the auto-recloser BI (DP) or operator control
AR_LOCK Signal to lock / unlock the auto-recloser BI (SP, Group) or output of a
configurable automation or
operator control
CB_HEALTHY Availability of the breaker to be closed BI (SP)
AR_BLOCKING Signal to block the closure of the circuit breaker BI (SP, Group) or output of a
configurable automation
CB_ORDER_1P_x CB order, on a per pole basis DO
CB_ORDER CB order (global) DO
AR_TRIP_3P 3 phases trip forcing order This information can be wired
to a DO or can be used as an
internal signal.
AR_IS/OS Auto-recloser status: In / Out Of Service SI (DP)
AR_STATE Auto-recloser current state SI (MP)
AR_READY Indicate the auto-recloser is in service, unlocked State1
and no cycle is in progress
AR_WAIT_FOR_OPEN_CB Indicate the auto-recloser is waiting CB opening State2
AR_FIRST_CYCLE_1P Indicate the first single-phase cycle is in progress State3
AR_FIRST_CYCLE_3P Indicate the first 3-phases cycle is in progress State4
AR_SECOND_CYCLE_3P Indicate the second 3-phases cycle is in progress State5
AR_THIRD_CYCLE_3P Indicate the third 3-phases cycle is in progress State6
AR_FOURTH_CYCLE_3P Indicate the fourth 3-phases cycle is in progress State7
AR_WAIT_FOR_CLOSE_CB Indicate the auto-recloser is waiting CB closing State8
AR_RECLAIMC Indicate the Reclaimc timer is launched State9
AR_BAR_SHOTS Indicate an auto-recloser locking due to a max State10
number of reclosing cycles
AR_BAR_LOCK Indicate an auto-recloser locking State11
AR_RECLAIMML Indicate the reclaimml timer is launched State12
AR_RECLAIMMC Indicate the reclaimmc timer is launched State13
AR_FAIL Failure of the close order SI (MP)
AR_SYNC_NOK Due to the synchrocheck State0
AR_HARD_ERROR Due to hardware failure, lock of device or another State1
running automation linked to the device
AR_ILOCK_NOK Due to interlocking function State2
AR_NO_FAULT No failure State3
Parameter Description Value

AR_TYPE Auto-recloser type o cycle configuration Mono / Tri
AR_CYCLE_NUMBER Number of cycles 1, 2, 3 or 4
1P_CYCLE1_TIMER Timer of the first single-phase cycle From 10 ms to 5 seconds,
with a 10 ms step
3P_CYCLE1_TIMER Timer of the first 3-phases cycle From 10 ms to 60 seconds,
with a 10 ms step
3P_CYCLE2_TIMER Timer of the second 3-phases cycle From 1 to 3600 seconds,
with a 1 second step
3P_CYCLE3_TIMER Timer of the third 3-phases cycle From 1 to 3600 seconds,
3P_CYCLE4_TIMER Timer of the fourth 3-phases cycle From 1 to 3600 seconds,
RECLAIM_TIMER Reclaim timer From 1 to 600 seconds,
RECLAIMMC_TIMER Reclaimmc timer From 1 to 600 seconds,
RECLAIMML_TIMER Reclaimml timer From 1 to 600 seconds,
UNLOCKING_METHOD Method to unlock the auto-recloser None, manual close, unlock
signal, both
SYNC_ENABLE Use the synchrocheck function during the 3- Yes / No
phases first cycle
7.1.2 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 C264 by a separate input and inhibits the detection of continuity.
NOTE: For the DIU211/CCU211 boards, the Trip Circuit Supervision function
is not available.
The C264 computer supports these two diagrams used in Trip Circuit Supervision:
• Trip Circuit Supervision with one Digital Input + external resistor: FIGURE 55: TRIP
CIRCUIT SUPERVISION WITH ONE DI
• Trip Circuit Supervision with two Digital Inputs without external resistor: FIGURE 56:
TRIP CIRCUIT SUPERVISION WITH TWO DI.
For the Trip Circuit Supervision with one Digital Input + external resistor, please refer to
FIGURE 55: TRIP CIRCUIT SUPERVISION WITH ONE DI.
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 mecanism is released (within a
possible delay due to inductive effect of the coil).
2. Low enough so that the C264 input powered via the resistor (and the tripping coil) is
detected active.
Therefore:
3. 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 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.
4. 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 50: TRIP CIRCUIT SUPERVISION WITH ONE DI

For the Trip Circuit Supervision with two Digital Inputs without the external resistor, please
refer to FIGURE 56: TRIP CIRCUIT SUPERVISION WITH TWO DI.
FIGURE 51: TRIP CIRCUIT SUPERVISION WITH TWO DI

NOTE: Use this diagram for inputs that have a detection threshold > 55% for
the "set" state: for example, CCU200 A07.
7.1.3 Circuit breaker condition monitoring (I²t)

The 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 C264 mainly calculates the sum of the switched current over a period.
The 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 C264 performs the I²t
function.
7.1.3.1 Acquisition and computation
The C264 counts without consideration of disconnection currents:
• The number of CB operations per pole
• The number of CB operations for the 3 poles (i.e. the highest of the pole values)
The C264 cumulates 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:
FIGURE 52: INTEGRATION TIME
7.1.3.2 Reset
All the stored values can be simultaneously reset. This control can be available at all controls
points.
7.1.3.3 Monitoring
The C264 can monitor each cumulated 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.
7.1.3.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
7.1.3.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 C264 redundancy, the stored values in the standby computer are exchanged
from Main to Standby after each calculation.
7.2 Interlocking: logical equations

In an electrical substation, the switching devices are primarily the following:
• Circuit breakers
• Traditional disconnecting switches
• Disconnecting switches with abrupt rupture
• Ground disconnecting switches

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, are managed in the form of logical equations within the computer.
Moreover, interlocking can be applied on whatever module or whatever control.
Interlocking prohibits an operation that would be ordered by error, in remote control, to a
switching device beyond its standard conditions of operation.
Some equations of substation interlocking also manage the operations of the disconnecting
switches according to topology and by respecting some preset rules: topological interlocking.
The equations of topological interlocking are generated by independent software. This
software takes in account the topology and some predefined rules to provide these
equations
7.2.1 Interlocking: Inputs

Interlocking function can use the following inputs:
• Digital inputs from the systems digital input boards, from other system computers,
from protection relays and other IED’s via communication network (single and double
point, digital groups),
• Internal indications: for example, system failures, equipment operation modes and so
on.
• Limits derived from measured values from the systems analog input boards (CT, VT,
transducers), from other system computers, from protection relays and other IED’s via
communication network.
7.2.2 Interlocking:Outputs
Result of the interlocking equation is transmitted through a system binary output and saved,
locally in RAM, by the function managing interlocking logical equations.
And, a service is available for any task to get the result of the computation.
Thus , the function managing “control of sequence” uses this service to know whether control
can be executed.
Then, a simple transient binary input can be set if defined in configuration. The same SPS is
used for the commands “open” and “close” of a xPC
7.2.3 Interlocking: Control

No control. An equation is computed each time that one of its input changes of state or of
validity.
7.2.4 Interlocking: Behaviour
7.2.4.1 Principle
In computer, a logical interlocking equation is defined as a sum of product (AB+CDE+F for
example).
7.2.4.1.1 Introduction
Interlocking function uses as many as two interlocking equations per switching device on
bay-level and on substation-level. During configuration process the definition of the switching
devices can be:
• Without associated interlocking equations,
• With only one interlocking equation: for example, for opening, closing being not
checked or vice-versa,
• With two interlocking equations (for opening and closing). The interlocking equations
can be different but can also be identical.
The 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 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 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.). Substation interlocking can also be managed by the
topological interlocking function. Refer to Topological interlocking for more details.
7.2.4.1.2 Local interlocking

The local interlocking is done by calculation of a logical equation. You can have as many as
one equation for each switching device and for each direction (open and close). If there is no
equation for a switching device for a direction, the related variable is true.
7.2.4.1.3 Substation interlocking
The substation interlocking analyses the position of all switching devices in the substation
and calculates the substation interlocking equation to authorise control of a switching device
according to the mechanical and electrical capabilities of the switching device. If there is no
equation for a switching device for a direction, the corresponding variable is true.
7.2.4.1.4 Interlocking: Validity of data
The interlocking equation does not only use the value of the information but also the validity
of the information (invalid, ...).
Thus the result, saved in RAM, of a logical equation is only TRUE or FALSE, An Interlocking
equation in the INVALID state will be considered as FALSE .
But, the system binary input also generated can be valid (SET or RESET) or invalid.
The evaluation of the result of basic logical function such as NOT, AND or OR is defined as
follows:
NOT
True False
False True
Invalid Invalid
OR True False Invalid

True True True True
False True False Invalid
Invalid True Invalid Invalid
AND True False Invalid

True True False Invalid
False False False False
Invalid Invalid False Invalid
An Interlocking equation in the INVALID state will be considered as FALSE.

7.2.4.1.5 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.
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.
7.2.4.1.6 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 ILK: one time-out attribute for the Open
ILK and one time-out attribute for the Close ILK. 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 launch
only if the ILK is FALSE. If the ILK becomes TRUE while the timer operates, the control
sequence waits for the end of the timer before it validates the ILK. The timer applies to these
controls: Select Before Operate and Direct Execute.
7.2.4.2 Software tasks

A logical equation is a sum of products. Each product comprises logical data that can be
complemented. Each electrical component has two logical equations at the most, and each
logical equation is associated with one electrical component.
Example of Logical equation: X = A.B + C.D.E
In this example, the component X can be operated only if:
• (A is in the higher state) AND (B is in the lower state)
OR
• (C is in the lower state) AND (D is in the higher state) AND (E is in the lower state)
The terms of these equations can be issued from:
• Single point status (BI)
• Double point status (BI)
• 1 among N BI (SIG)
• Measurement (MEAS)
At configuration time, operator has to define the “interlocking profile” of each data included in
an interlocking equation. It means that operator must select for each state or validity of a
data a logical state: TRUE, FALSE or INVALID.
Interlocking computation
An interlocking equation:
• Is computed each time that one of its element changes of quality or state and
• Is defined by a sum of product.

Upon reception of a new state or quality for a data:
• Get logical state related to the received state and validity of the data
• For each equation that includes the data:
− Compute the sum of product
− Determine the result of the interlocking equation: TRUE or FALSE
− Send the new state of the system binary input (BI) that represents the result of the
interlock. BI can be: SET, RESET or INVALID
Interlocking consultation
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 result of the interlocking is TRUE, the check is considered as achieved, else request must
be refused and a negative acknowledgement sent to the origin of the request.
Simulation and test of interlocking equations

The interlocking system is checked during the in house test of the substation control system.
Each interlocking equation may be checked by issuing a control to the corresponding
switching device.
For checking the interlocking on site 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.
7.3 Interlocking: logical equations

In an electrical substation, the switching devices are primarily the following:
• Circuit breakers
• Traditional disconnecting switches
• Disconnecting switches with abrupt rupture
• Ground disconnecting switches

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, are managed in the form of logical equations within the computer.
Moreover, interlocking can be applied on whatever module or whatever control.
Interlocking prohibits an operation that would be ordered by error, in remote control, to a
switching device beyond its standard conditions of operation.
Some equations of substation interlocking also manage the operations of the disconnecting
switches according to topology and by respecting some preset rules: topological interlocking.
The equations of topological interlocking are generated by independent software. This
software takes in account the topology and some predefined rules to provide these
equations.
7.3.1 Interlocking: Inputs

Interlocking function can use the following inputs:
• Digital inputs from the systems digital input boards, from other system computers,
from protection relays and other IED’s via communication network (single and double
point, digital groups),
• Internal indications: for example, system failures, equipment operation modes and so
on.
• Limits derived from measured values from the systems analog input boards (CT, VT,
transducers), from other system computers, from protection relays and other IED’s via
communication network.
7.3.2 Interlocking:Outputs
Result of the interlocking equation is transmitted through a system binary output and saved,
locally in RAM, by the function managing interlocking logical equations.
And, a service is available for any task to get the result of the computation.
Thus , the function managing “control of sequence” uses this service to know whether control
can be executed.
Then, a simple transient binary input can be set if defined in configuration. The same SPS is
used for the commands “open” and “close” of a xPC
7.3.3 Interlocking: Control

No control. An equation is computed each time that one of its input changes of state or of
validity.
7.3.4 Interlocking: Behaviour
7.3.4.1 Principle
In computer, a logical interlocking equation is defined as a sum of product (AB+CDE+F for
example).
7.3.4.1.1 Introduction
Interlocking function uses as many as two interlocking equations per switching device on
bay-level and on substation-level. During configuration process the definition of the switching
devices can be:
• Without associated interlocking equations,
• With only one interlocking equation: for example, for opening, closing being not
checked or vice-versa,
• With two interlocking equations (for opening and closing). The interlocking equations
can be different but can also be identical.
The 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 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 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.). Substation interlocking can also be managed by the
topological interlocking function. Refer to Topological interlocking for more details.
7.3.4.1.2 Local interlocking
The local interlocking is done by calculation of a logical equation. You can have as many as
one equation for each switching device and for each direction (open and close). If there is no
equation for a switching device for a direction, the related variable is true.
7.3.4.1.3 Substation interlocking
The substation interlocking analyses the position of all switching devices in the substation
and calculates the substation interlocking equation to authorise control of a switching device
according to the mechanical and electrical capabilities of the switching device. If there is no
equation for a switching device for a direction, the corresponding variable is true.
7.3.4.1.4 Interlocking: Validity of data
The interlocking equation does not only use the value of the information but also the validity
of the information (invalid, ...).
Thus the result, saved in RAM, of a logical equation is only TRUE or FALSE, An Interlocking
equation in the INVALID state will be considered as FALSE .
But, the system binary input also generated can be valid (SET or RESET) or invalid.
The evaluation of the result of basic logical function such as NOT, AND or OR is defined as
follows:
NOT
True False
False True
Invalid Invalid
OR True False Invalid

True True True True
False True False Invalid
Invalid True Invalid Invalid
AND True False Invalid

True True False Invalid
False False False False
Invalid Invalid False Invalid
An Interlocking equation in the INVALID state will be considered as FALSE.

7.3.4.1.5 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.
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.
7.3.4.1.6 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 ILK: one time-out attribute for the Open
ILK and one time-out attribute for the Close ILK. 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 launch
only if the ILK is FALSE. If the ILK becomes TRUE while the timer operates, the control
sequence waits for the end of the timer before it validates the ILK. The timer applies to these
controls: Select Before Operate and Direct Execute.
7.3.4.2 Software tasks

A logical equation is a sum of products. Each product comprises logical data that can be
complemented. Each electrical component has two logical equations at the most, and each
logical equation is associated with one electrical component.
Example of Logical equation: X = A.B + C.D.E
In this example, the component X can be operated only if:
• (A is in the higher state) AND (B is in the lower state)
OR
• (C is in the lower state) AND (D is in the higher state) AND (E is in the lower state)
The terms of these equations can be issued from:

• Single point status (BI)
• Double point status (BI)
• 1 among N BI (SIG)
• Measurement (MEAS)
At configuration time, operator has to define the “interlocking profile” of each data included in
an interlocking equation. It means that operator must select for each state or validity of a
data a logical state: TRUE, FALSE or INVALID.
Interlocking computation
An interlocking equation:
• Is computed each time that one of its element changes of quality or state and
• Is defined by a sum of product.

Upon reception of a new state or quality for a data:
• Get logical state related to the received state and validity of the data
• For each equation that includes the data:
− Compute the sum of product
− Determine the result of the interlocking equation: TRUE or FALSE
− Send the new state of the system binary input (BI) that represents the result of the
interlock. BI can be: SET, RESET or INVALID
Interlocking consultation
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 result of the interlocking is TRUE, the check is considered as achieved, else request must
be refused and a negative acknowledgement sent to the origin of the request.
Simulation and test of interlocking equations
The interlocking system is checked during the in house test of the substation control system.
Each interlocking equation may be checked by issuing a control to the corresponding
switching device.
For checking the interlocking on site 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.
7.3.5 Limits and performance

You can use as many as 256 operands for each equation.
You can define as many as 256 equations in a computer.
You can use a datapoint in as many as 255 interlocking equations.
7.3.6 Limits and performance

You can use as many as 256 operands for each equation.
You can define as many as 256 equations in a computer.
You can use a datapoint in as many as 225 interlocking equations.
7.4 Slow automation: Programmable Logic Control (PLC)

During the substation configuration phase, the C264 allows you to configure the specific
control sequences or automations: for example, the switching sequences, busbar transfer,
load shedding, and GIS-pressure supervision.
You create the Programmable Logic Controls (PLC) or Configurable Automations and build
them onto a logic development workbench. The real time kernel of the computer operates
them.
The software logic package includes the logic development workbench. The logic
development workbench is a host-based software development environment related to the
SCE. Use the software logic package and the logic development workbench to create the
control logic programs in the MiCOM C264.
The logic development workbench includes a set of tools that allow you to:
• Edit
• Generate code
• Simulate
• Debug
• Project management.
The software logic package supports standard programming languages of the IEC 1131-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.
Control logic
application
code
Software Logic Package

Target
------------------------------- hardware
Logic Development Workbench
C0019ENb
FIGURE 53: PLC WORKBENCH
For ISaGRAF, refer to the chapter SCE/EN FT.

7.4.1 Inputs
All the datapoints of the C264 can be used as an input of a PLC.
7.4.1.1 Data acquired by C264
• BI: non filtered change of states are transmitted to PLC kernel
• MEAS
• CT
• Tap position (TPI or SPI)
7.4.1.2 Data managed by C264
• CO
NOTE: A CO can be used as input of a PLC function, but only through the
use of ‘C’ function present by default with the kernel.
7.4.1.3 Acknowledgement of control

A PLC function can manage a control sequence:
• Send control
• Process acknowledgement to the sent control
7.4.2 Outputs
A PLC function can:
• Generate a BI, for example. PLC is considered as source of acquisition of the data
point
• Generate an MEAS
• Generate a CT
• Generate an SPI
• Generate an SIG
• Modify quality of a Binary Input defined in the computer: force, suppress or

substitution request
• Modify quality of an MEAS defined in the computer: force, suppress or substitution

request
• Modify quality of an SIG defined in the computer: force, suppress or substitution

request
• 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.
7.4.3 Control
Automations can be triggered:
• By operator request,
• By events (digital or analogue input state changes),
• Cyclically (each day, each week or each month),
• At a specific date and time (e. g.: 20. 12. at 10:00).

7.4.4 Behaviour
The computer has a software execution engine that interprets the automation application
code as shown in the cycle that follows:
Read inputs
Execute programs
Write outputs
C0345ENa
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.
7.4.4.1 Interfacing with an HMI or an RCP/SCADA

A master station on a remote site can send and receive data to and from the automation
applications of C264.
In DB, the data sent by a master station to an automation application include DO and BI
entities. Conversely, the data received by a master station from automation applications
include DI, Measurements, Metering (non-tariff), and Tap Changer Position entities. These
data have a unique transmission address for C264.
7.4.5 Limits and specifications

• The execution of the automation sequences can be cyclic and/or event-driven.
• Maximum number of cyclic PLC-programs is 32.
• The two different time cycles of a PLC-program can be set from 10 ms up to several
seconds. For some specific equations a cycle less or equal to 10ms and a cycle less
or equal to 100ms for the other logic equations. The time cycle for the automatic
functions shall be less than 100ms.
• Each PLC-program operates on one computer: this means a PLC-program cannot be

distributed within the system. However, it is possible to use data obtained by other
computers.
• Routing of the automatism applications to the memory must be in agreement with the
memory and hardware design.
• To debug the applications, you can connect a PC to the front face. The hardware
design separates the debug function and the application download function.
7.5 Fast automation: Programmable Scheme Logic (PSL)

As automations created through ISaGRAF are dependent on the ISaGRAF cycle whose
value is about 50ms at least, it may be necessary to implement configurable automations
that can be achieved in less than 50ms.
PSL is the solution for implementation of automatism that must be performed as quickly as
possible.
Designed solution is mainly based on mechanism used for the computation of logical
interlocking (refer to §logical interlocking for more details). Indeed, 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 and pickup timer, bistables) are added to these logic gates.
These automations are event-driven: they are calculated each time an input changes: that is,
there is no cycle time.
Only BI and measurements described are usable as inputs (controls are not).
PSL are logical equations that use the following functions:
• AND, OR, XOR, NOT, NAND, NOR operators
• "bistable" functions
• pickup and drop-off timers (from 10 ms to 60 seconds, by step of 10 ms)
• BI setting – the system BI is:
− SET if the PSL is TRUE
− RESET if the PSL is FALSE
− INVALID if the PSL is INVALID
• Digital Output setting – the DO is:
− closed if the PSL is TRUE
− opened if the PSL is FALSE or INVALID (only in event of permanent DO)
− INVALID if the PSL is INVALID
The equations management rules described for interlocking equations apply on PSL.
Digital outputs used as outputs are mandatory local hardwired DO directly managed by the
computer. You can configure as many as 256 items and as many as 256 elements in the
PSL.
I1
& DO1
setting
I2
& DO2
setting
≥1 t
&
BI1
≥1
setting
≥1
I3
≥1
I4
C0140ENa
FIGURE 54: EXAMPLE OF PSL

8. USER INTERFACE
Please refer to the chapter Human Interface (HI).
9. RECORDS
Several kinds of records are stored in the C264.
9.1 Permanent records storage

They are stored on flash disk.
9.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.
9.1.2 Disturbance Recording: General
A waveform recording deals with the storage of measurement and logical information in
order to visualise the electrical network behaviour 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:
• Disturbance recording that gives access to samples. This record is useful for transient
electrical events.
• Slow disturbance recording that gives access to RMS values.

9.1.3 Disturbance recording
The inputs for the disturbance records are up to 4 CT samples and 4 VT samples, and the
values of the selected digital inputs and outputs. Up to 128 digital channels may be captured.
The choice of selected inputs/outputs is defined in configuration.
The disturbance recorder provides up to 8 analogue measurements and up to 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 Files Number of cycles

8 60
4 120
2 240
1 480
The disturbance recorder can be triggered by the following events, each of which is user
configurable:
• Changes in state of binary inputs (SP, DP, MP, SI or Groups)
• 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.
Disturbance records are available in COMTRADE 2001 format.
9.1.4 Slow Waveform Recording

The inputs for the slow waveform records are:
• Analogue values coming from CT VT calculation (RMS values)
• Analogue values coming from AIU boards
• Digital inputs
• Digital outputs
The slow waveform manages as many as 24 analogue and 48 digital values.
Data from CT/VT can be chosen among:
• 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
The C264 stores at maximum 5000 integrated values as follows:
Number of Files Number of integrated 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 (SP, DP, MP, SI or Groups). 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
• Changes in state of digital outputs
• Measurement threshold violations
• 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.
9.1.5 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)
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 :
N
TMi
Record = ∑
i =1 N
Record: recorded value
N: number of seconds in the integration period
TMi : measurement value at the “i” second of the integration period
9.1.6 Events
All data change or events declared in 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 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 Binary Inputs (SP, DP, MP, SI, Groups)
• Changes of state of Measurements
• Changes of state and value of Tap Position Indications
• Devices Control actions and acknowledgements.
• Alarm acknowledgement.
The size queue is:
• 200 data for front panel
• 2000 data for CAT
• configurable per slave protocol for SCADA

Non-permanent data storage
Alarms
Definitions
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 PACiS has been introduced to inform the operators of
“abnormal” or “special” events or other miscellaneous events that you must absolutely not
overlook.
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
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 an other reason.
An alarm can be related to a control acknowledgement. In this event, the alarm is considered
as “spurious”.
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
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 differed:
an “immediate” alarm is displayed as soon it has been detected.
a “differed” 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 “differed” 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
most grave and 0 meaning that there is no gravity level.
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.
Alarm processing
Only one alarm (the last one) associated with a state change of a data is displayed. The
previous one (concerning the data) is replaced by the current one.
According to the previous example, only one from 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:
Alarm inactive
/ cleared
0
AL+
AL+
Alarm active-
AL- (auto) unacknowledged AL+
AL+ ACK AL-
Alarm active- Alarm inactive-

acknowledged active-
unacknowledged
2 3
AL- ACK
ACK (auto)
Alarm inactive-
acknowledged
CLEAR AL+
4
C0143ENa
FIGURE 55: EVENT ALARMED ON APPEARANCE ONLY

Alarm inactive
/ cleared
0
AL+ AL+
AL+
Alarm active-
unacknowledged
AL+
1
AL+
AL-
ACK Alarm inactive-

active-
unacknowledged
5
ACK
Alarm active- Alarm inactive-

acknowledged unacknowledged
2 AL- 3
ACK
ACK (auto)
Alarm inactive-
CLEAR acknowledged AL+
4
C0144ENa
FIGURE 56: EVENT ALARMED ON APPEARANCE AND DISAPPEARANCE
Transition events:
AL+: alarmed event appearance
AL-: alarmed event disappearance
ACK: operator acknowledgement of the alarm
CLEAR: operator clearing of the alarm
NOTE:In that event «alarmed event disappears (AL-)» means that the associated data is now in another s
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 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.
being 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.
being 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 acknowledgement 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.
Acknowledgement
Acknowledgement 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 a SPS (named Global alarm ack) specially
dedicated to a global acknowledgement 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 Acknowledgement SPS, a Local Alarm Acknowledgement
SPS can be defined on a per C264 basis: that is, one for each C264.
This SPS can be wired or managed by an automation. When this SPS is configured in a
C264, the “Global Alarm Acknowledgement” SPS is no more taken into account by this
C264.
When this SPS is SET, all C264 alarms are immediately acknowledged.
This SPS cannot be transmitted on the Station Bus network: that is, it remains local to the
C264, so it cannot be associated to a remote – OI or SCADA - control.
Clearing
Whatever the clearing mode is, the clearing of an alarm is immediately taken into account:
suppression 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 acknowledgement 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.
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 as “audible” then the sound appears when the alarm is displayed.
The audible alarm is stopped when all audible alarms are acknowledged.
10. PROTECTION FUNCTIONS

10.1 Directional/Non-directional Phase OC Protection (ANSI code 67/50/51)
• Phase Current Fundamental only
• Phase Voltage Fundamental only
• Phase Current Range 0.1 to 40 x rated current, step of 0.01 In
• Thresholds 3 independent (I>, I>>, I>>>)

I> 0.1 to 40 In (see note)
I>> 0.5 to 40 In (see note)
I>>> 0.5 to 40 In
NOTE: When I> or I>> is associated to an IDMT curve, the maximum setting
recommended should be 2In.
• Minimum voltage operation 0.6V (Un: 57 to 130V)
• Minimum voltage operation 3.0V (Un: 220 to 480V)
• Synchronous Polarisation
Minimum phase voltage fixed threshold enabling synchronous polarising: 0.6V
Synchronous polarising permanence time phase voltage thresholds: 5 s
• Hysteresis 95%
• Instantaneous time < 30 ms
• Drop out time 30 ms
• Phase time delays (tI>, tI>>, tI>>>)

DMT 0 ms to 150 s, step of 10 ms
Reset time (for DMT) 0 ms to 600 s, step of 10 ms
IDMT curves:
IEC: Short time inverse (Schneider Electric),
Standard Inverse (IEC),
Very inverse (IEC),
Extremely inverse (IEC),
Long time inverse (Schneider Electric)
RI: (Electromechanical type).
RECT: Rectifier.
IEEE/ANSI: Short time inverse (CO2),
Moderately inverse (ANSI),
Inverse (CO8),
Very inverse (ANSI),
Extremely inverse (ANSI)
Time Multiplier Setting (TMS) 0.025 to 1.5, step of 0.025
• Reset time
− If IEEE/ANSI phase time delay: Short time inverse (CO2),

Inverse (CO8),
Extremely inverse (ANSI).
• Reset Time Multiplier Setting (RTMS) 0.025 to 3.2, step of 0.025

or DMT: 0.04s to 100s; step of 0.01 s
− If IEC curves phase time delay: 0.04s to 100s; step of 0.01 s

10.2 Dir. /Non-dir. Neutral/Ground/Earth OC Protection (ANSI code 67N/50N/51N)
• Residual Current Fundamental only
• Residual voltage Fundamental only
• Earth current Ranges 0.01 to 8 x rated current, step of 0.005 Ien

0.1 to 40 x rated current, step of 0.005 Ien
• Thresholds 3 independent (Ie>, Ie>>, Ie>>>)

Range: 0.01 to 8 x Ien
Ie> 0.01 to 1 Ien (see note)
Ie>> 0.01 to 8 Ien (see note)
Ie>>> 0.01 to 8 Ien
Range: 0.1 to 40 x Ion
Ie>>> 0.5 to 40 Ien
NOTE: When Ie> or Ie>> is associated to an IDMT curve the maximum setting
recommended should be the maximum of the range /20.
• Minimum residual voltage operation 0.7V (Uen: 57 to 130V)
• Hysteresis 95%
• Earth time delays (tIe>, tIe>>, tIe>>>)

IDMT Curves IEC: Short time inverse (Schneider Electric),
Very inverse (IEC),
Long time inverse (Schneider Electric).
RI: (Electromechanical type)
RECT: Rectifier.
Inverse (CO8),
• Reset time
− if IEEE/ANSI Earth time delay Short time inverse (CO2),

Inverse (CO8),
or DMT: 0.04s to 100s ; step of 0.01 s
− if IEC Curves Earth time delay 0.04s to 100s ; step of 0.01 s

10.3 Dir. /Non-dir. Sensitive ground/Earth OC protection (ANSI code 67N/50N/51N)
• Residual Current Fundamental only
• Residual Voltage Fundamental only
• Sensitive Earth current Range 0.002 to 1 x rated current, step of 0.001 Ien
• Thresholds 3 independent (Ie>, Ie>>, Ie>>>)

Range: 0.002 to 1 x Ion
Ie>>> 0.002 to 1 Ien
NOTE: When Ie> or Ie>> is associated to an IDMT curve the maximum setting
recommended should be 0.05 Ien.
• Hysteresis 95%
• Earth time delays (tIe>, tIe>>, tIe>>>)

IDMT curves
IEC: Short time inverse (Schneider Electric),
Very inverse (IEC),
RECT: Rectifier.
Inverse (CO8),
• Reset time
− if IEEE/ANSI Earth time delay: Short time inverse (CO2),

Inverse (CO8),
− if IEC curves Earth time delay: 0.04s to 100s ; step of 0.01 s

10.4 Thermal overload protection (ANSI code 49)

• Current RMS
• Current threshold I θ> 0.1 to 3.2 x rated current, step of 0.01
• Thermal state (alarm and trip) 50 to 200 % x θ, step of 1 %
• Constant Time Te 1 to 200 mn, step of 1 mn
• k factor 1 to 1.5, step of 0.01

10.5 Undercurrent protection (ANSI code 46)
• Current Fundamental only
• Phase Current Range I< 2 to 100 % x rated current, step of 1%
• Time delay tI< 0 to 150 s, step of 10 ms
• Hysteresis 105%
10.6 Earth Wattmetric Protection (ANSI code32N)
− Earth fault current Fundamental only
− Residual voltage Fundamental only
− Minimum Operating Voltage

Range from: 57 to 130V 0.7 V
Range from: 220 to 480V 3.0 V
− Minimum Operating Current with Ien=1A and Ien=5A

Range from: 0.002 to 1 Ien 1 mA
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.
10.7 Negative sequence OC protection (ANSI code 27)

• Curren Fundamental only
• Phase Current Range I2> & I2>> 0.1 to 40 x rated current

NOTE: When I2> is associated to IDMT curve the maximum setting
recommended should be 2In.
• Hysteresis 95%
• I2> Time delay

IDMT curves IEC: Short time inverse (Schneider Electric),
Very inverse (IEC),
RECT: Rectifier.
Inverse (CO8),
• Reset time
− If IEEE/ANSI I2> Time delay: Short time inverse (CO2),

Inverse (CO8),
− If IEC I2> Time delay: 0.04s to 100s ; step of 0.01 s
• I2>> Time delay

10.8 Undervoltage (ANSI code 27)

10.8.1 Threshold settings (secondary values)
− Nominal voltage range: 57 – 130V
Setting Range Step size

V<= Voltage Set 5 – 130V 0.1V
V<<= Voltage Set 5 – 130V 0.1V
Setting Range Step size

V<= Voltage Set 20 – 480V 0.5V
V<<= Voltage Set 20 – 480V 0.5V
10.8.2 Time delay settings

Each voltage element is associated to an independent time delay.
Element Time delay type

1st stage Definite Time (DT)
nd
2 stage Definite Time (DT)
rd
10.8.3 Definite time delay characteristics
Setting Range Step Size

tV< 0 – 600s 0.01s
tV<< 0 – 600s 0.01s
10.9 Overvoltage (ANSI code 59)


V>= Voltage Set 5 – 200V 0.1V
V>>= Voltage Set 5 – 260V 0.1V

V>= Voltage Set 20 – 720V 0.5V
V>>= Voltage Set 20 – 960V 0.5V


st
2nd stage Definite Time (DT)
rd

tV> 0 – 599s 0.01s
tV>> 0 – 599s 0.01s
10.10 Residual overvoltage / neutral displacement (ANSI code 59N)


V0> Voltage set 0.5 – 130V 0.1V

V0> Voltage set 2 – 480V 0.5V

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

st
1 stage Definite Time (DT) or IDMT

tV0> 0 – 599s 0.01s
10.11 Under/overfrequency (ANSI codes 81U/81O)

F1 threshold Fn – 10Hz, Fn + 10Hz 0.01 Hz
tF1 (definite time delay) 0 – 600s 0.01s
Where: Fn: nominal frequency

10.12 Rate of change of frequency (ANSI codes 81R)

10.12.1 Threshold settings

df/dt1 threshold –10 Hz/s, +10 Hz/s 0.1 Hz/s
10.12.2 Integration time

cycle number 1 – 200 1 cycle
10.12.3 Validation number of protection

Validation 2 or 4 2
10.12.4 Under voltage blocking
− Nominal voltage range: 57-130V

protection block 5.7 – 130V 0.1
− Nominal voltage range: 220-480V

protection block 20 – 480V 0.1
10.13 Extra functions

10.13.1 Circuit breaker failure (50BF or TCS)
• Under current threshold I< 2% to 100% x rated current, step of 1%
• Threshold accuracy from 0.02 In to 0.1 In: 0.006 In

from 0.1 In to 1 In: 2% Is
• Threshold hysteresis max. 0.008 In or 0.95 Is
• CB failure time tBF 30 ms to 10 s; step of 10 ms

10.13.2 Cold load pick-kup
• Range 100 to 500 % x nominal settings, step of 1%
• Time delay tCL 0.1 s to 3600 s, step of 100 ms

10.13.3 RSE
• Time delay in RSEA 1.5 s
• Time delay in RSEB 130 ms

10.13.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 C264, all the protection functions configured in the SCE use the three trip
relays, in this case, only the trip Status reflects the relays position.
FIGURE 57: FIGURE SETTING TRIP MANAGEMENT

If for a given C264, all the protection functions configured in the SCE use the three trip
relays, in this case, only the trip status reflects the relays position.
11. PROTECTION CURVES

11.1 IDMT Curves
11.1.1 Mathematical formula
11.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:
⎛ K ⎞
t = T×⎜ + L⎟
⎜ (I I ) − 1 ⎟
α
⎝ S ⎠
Where:
t = Tripping time
K = Coefficient (see table)
I = Value of measured current
IS = Value of the programmed threshold (Pick-up value)
α = Coefficient (see table)
L = ANSI/IEEE coefficient (zero for IEC curves)
T = Time multiplier between 0.025 and 1.5
Type of curve Standard K factor α factor L factor

Short Time Inverse Schneider Electric 0.05 0.04 0
Standard inverse IEC 0.14 0.02 0
Very inverse IEC 13.5 1 0
Extremely inverse IEC 80 2 0
Long time inverse Schneider Electric 120 1 0
Rectifier Schneider Electric 45 900 5.6 0
Short Time Inverse C02 0.02394 0.02 0.01694
Moderately Inverse ANSI/IEEE 0.0515 0.02 0.114
Long Time Inverse C08 5.95 2 0.18
Very Inverse ANSI/IEEE 19.61 2 0.491
Extremely Inverse ANSI/IEEE 28.2 2 0.1215
The RI curve (electromechanical) is given by the following formula:
⎛ 1 ⎞
t = K × ⎜⎜ ⎟⎟
⎝ 0.339 − 0.236 /(I / Is) ⎠
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).
11.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 reinitialised.
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 Reset Timer

the first & second phase
(earth) threshold
DMT + RECT 0 ms
IDMT IEC or RI Settable from 40 ms to 100s

Inverse Time
IDMT IEEE or COx
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:
⎛ K ⎞
t = T × ⎜⎜ ⎟
⎝ 1 − (I Is ) ⎠
α ⎟
Where:
t = Reset time
K = Coefficient (see table)
I = Value of the measured current
IS = Value of the programmed threshold (pick-up value)
α = Coefficient (see table)

T = Reset Time Multiplier (Rtms) between 0.025 and 3.2
Type of curves Standard K factor α factor

Short time inverse C02 2.261 2
Moderately Inverse ANSI/IEEE 4.85 2
Long time Inverse C08 5.95 2
Very inverse ANSI/IEEE 21.6 2
Extremely inverse ANSI/IEEE 29.1 2
11.1.2 IEC Curves
IEC & Schneider Electric Curves

(TMS=0,025)
10
1
TIME I N SE CONDS
0,1
0,01
0,001
1 10 100
MULTIPLES OF PI CK UP SETTI NG
Short time inverse (Schneider Electric)

Standard I nverse
Very I nverse
Extremely I nverse
Long Time Inverse (Schneider Electric)
P0006ENc
Short Time Inverse (Schneider Electric)
10
A
B
C
TIME I N SE CONDS
0,1
D
0,01 E
0,001
1 10 100
E TMS=0.025
: DTMS=0.2
: C TMS=0.5
: B TMS=1
: A TMS=1.25
:
P0007ENc
STANDARD INVERSE (IEC)
100
10
A
B
TIME IN SECONDS
C
1
0,1
0,01
1 10 100
MULTIPLES OF PICK UP SETTING
E : TMS=0.025 D : TMS=0.2 C : TMS=0.5 B : TMS=1 A : TMS=1.25
P0008ENa
VERY INVERSE (IEC)

100
10
TIME IN SECONDS
1 A
B
0,01
0,001
1 10 100
E : TMS=0.025 D : TMS=0.2 C : TMS=0.5 B : TMS=1 A : TMS=1.25
P0009ENa
EXTREMEMELY INVERSE (IEC)
10000
1000
100
TIME IN SECONDS
10
A
B
0,1 C
0,01
0,001
1 10 100
E :TMS=0.025 D : TMS=0.2 C : TMS=0.5 B : TMS=1 A : TMS=1.25
P00010ENa
LONG TIME INVERSE (Schneider Electric)
10000
1000
100
TIME I N SE CONDS
A
B
D
1
E
0,1
1 10 100
E : T MS=0.025 D : T MS=0.2 C : T MS=0.5 B : T MS=1 A : T MS=1.25
P0011ENc
11.1.3 RI Curves
RI CURVES
100
10
TIME IN SECONDS
0,1
1 10 100
E : k=0.1 D : k=1 C : k=2 B : k=5 A : k=10
P0012ENa
11.1.4 IEEE/ANSI & CO Curves
ANSI/IEEE & CO curves

(TMS/RTMS=0.025)
100
10
1
TIME IN SECONDS
0,1
0,01
0,001
0,0001
0,01 0,1 1 10 100
Short Time Inverse (CO2) Moderately Inverse

Long Time Inverse (CO8) Very Inverse
Extremely Inverse
P0013ENa
SHORT TIME INVERSE (CO2)

100
10
1
TIME IN SECONDS
0,1
A
A B
B C
C
D
0,01
D
E
0,001 E
0,0001
0,01 0,1 1 10 100
B : TMS/RTMS=1 A : TMS/RTMS=1.25
E : TMS/RTMS=0.025 D : TMS/RTMS=0.2 C : TMS/RTMS=0.5

P0014ENa
MODERATELY INVERSE (ANSI/IEEE)
1000
100
10
TIME IN SECONDS
A
1
A B
B C
C
D
D
0,1
E
E
0,01
0,01 0,1 1 10 100

P0015ENa
LONG TIME INVERSE (CO8)
100
10
A
B
C
D
1
TIME IN SECONDS
A
E B
0,1 C
0,01
0,001
0,01 0,1 1 10 100

P0016ENa
VERY INVERSE (ANSI/IEEE)
1000
100
B
C
TIME IN SECONDS
10
1
A
E B
0,1
D
E
0,01
0,01 0,1 1 10 100

P0017ENa
EXTREMELY INVERSE (ANSI/IEEE)
1000
100
A
B
10 C
D
TIME IN SECONDS
A
B
0,1 C
0,01
0,001
0,01 0,1 1 10 100

P0018ENa
11.2 Thermal overload curves

11.2.1 Mathematical formula
The thermal time characteristic is given by:
exp(-t/τ) = (I2 - (k.IFLC)2 ) / (I2 - IP2)

Where:
t = Time to trip, following application of the overload current, I
τ = 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
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".
Mathematical formula applicable to the MiCOM C264-P:

The calculation of the Time to Trip is given by:
⎛ K ² − θ² ⎞
Ttrip = Te In⎜ ⎟
⎜ K ² − θtrip² ⎟
⎝ ⎠
With:
Ttrip = Time to trip (in seconds)
Te = Thermal time constant of the protected element (in seconds)
K = Thermal overload equal to Ieq/k Iθ>

Ieq = Equivalent current corresponding to the RMS value of the largest phase current
Iθ> = Full load current rating given by the national standard or by the supplier
k = Factor associated to the thermal state formula
θ2 = Initial thermal state. If the initial thermal state = 30% then θ2 = 0.3
θtrip2 = Trip thermal state. If the trip thermal state is set at 100%, then θ trip2 = 1
The calculation of the thermal state is given by the following formula:
θι+1 = (Ieq/ k Iθ>)2 [1- exp(-t/Te)] + θι exp(-t/Te)
θ being calculated every 100ms

11.2.2 Tripping curve
TRIPPING CURVE FUNCTION OF THE PREFAULT LOAD

(k=1.1 & T e=10mn)
10000
1000
100
TIME IN SECONDS
A
10
B
C
D
E
1
0,1
1 10
MULTIPLES OF THERMAL THRESHOLD SETTING I >
A : No prefault load, thermal state = 0%

B : Thermal state=30%
C : Thermal state=50%
D : Thermal state=70%
E : Thermal state=90%
P0021ENa
BLANK PAGE
MiCOM C264P
HUMAN INTERFACE
CONTENT
2. THE FRONT PANEL 4

2.1 Overview 4
2.1.1 LED’s management 5
2.2 Configuration data 6
2.2.1 General display management 8
2.2.2 Language support 10
2.2.3 Time and date displaying 10
2.2.4 Bay panels 11
2.2.5 Events panel 19
2.2.6 Faults panel 20
2.2.7 Alarms panel 21
2.2.8 Disturbance records panel 22
2.2.9 Configuration panel 23
2.2.10 Display of binary input information 28
2.2.11 Display of binary output information 29
2.2.12 Menu tree 30
2.2.13 Controls (subject to privilege) 32
2.2.14 Password management 38
3. THE COMPUTER MAINTENANCE TOOL 40
4. THE EMBEDDED MAINTENANCE WEB SERVER 41
5. THE PRINTER 42
5.1 Inputs 42
5.2 Outputs 42
5.3 Printer management 43
5.3.1 Header & footer 43
5.3.2 Chronology & time stamp 43
5.3.3 Printer out of service 43
5.3.4 Circular FIFO management 43
C264P/EN HI/C80 Human Interface
6. MiCOM S1 V4 FOR MiCOM C264P 45

6.1 MiCOM S1 V4 Main Window 45
6.2 How to use MiCOM S1 V4 46
6.2.1 Create a new default settings file 47
6.2.2 Extract a setting file from a device 47
6.2.3 Modify a settings file 48
6.2.4 Save a settings file 48
6.2.5 Send modified settings to a device 48
6.2.6 Create a print file 48
6.3 Menu and Toolbar 49
6.3.1 The Menu functions 49
6.3.2 TheTool bar functions 51

This document is a chapter of the MiCOM C264 documentation. It describes the User
Interfaces (coded HI for Human Interface) of this computer:
• The Front Panel (FP alias DHMI)
• The Computer Administration Tool (CAT)
• The Printer
• The Protection Parameters Software (MiCOM S1 V4)

2. THE FRONT PANEL

2.1 Overview
The MiCOM C264/C264C front panel exists in two versions:
• A simple FP with LEDs, L/R push-button and the serial link (GHU21x)
• A graphical FP with LEDs, L/R push-button, the Local Control Display and the serial
link ( GHU20x)
LEDs
Key-pad
Local/Remote
Graphical push-button
LCD
RS 232 Serial port
C0020ENd
FIGURE 1: MiCOM C264C FRONT PANEL (GHU20X)

The FP is detachable up to 5 meters from the MiCOM C264/C264C 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:
• 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
2.1.1 LED’s management
There are 17 LEDs available; 16 of them are managed by the software. One is directly
connected to the internal power.
2.1.1.1 First 5 LEDs
The first 5 LEDs indicate the MiCOM C264/C264C status information. They indicate from top
to down:
LED id Colour LED on LED slow blinking LED fast blinking LED off
1 Red There is at least one There is at least one Not used There is no fault
major fault minor fault (I/O board,
(hardware, database) communication to IEDs,
…)
2 Yellow All the alarms are All alarms displayed in There is at least There is no
acknowledged, but the alarm panel are one not alarm
there is at least one inactive and acknowledged
alarm still active. acknowledged alarm displayed in
the alarm panel
NOTE: When the
alarm disappears,
the LED returns
automatically to OFF
3 Yellow Computer in service Computer in Computer in test Computer in
maintenance reboot
4 Green Power up is present Not used Not used Power up is out
5 (Fixed Red All bays managed by Bays managed by the Not used All bays managed
only for the computer are in computer are not in by the computer
without LOCAL mode the same control mode are in REMOTE
LCD panel:
GHU2x1)
Major fault: MiCOM C26x not available due to internal major fault (database error, CPU
watchdog, …).
A minor fault is a fault causing only the non-availability of a part of the functionality.
When the alarm disappears, the LED returns automatically to OFF.
Table explaining the fixed LEDs for the graphical DHMI:
LED id Colour LED on LED slow blinking LED fast blinking LED off
1 Red Fault There is at least one There is at least one minor No fault
major fault (hardware, fault (I/O board,
database) communication to IEDs, …)
(2)
(1)
2 Yellow Alarm All the alarms are acknow- All alarms displayed in the There is at least
ledged, but there is at alarm panel are inactive and one not acknow-
least one alarm still active. acknowledged ledged alarm
(3) displayed in the
alarm panel
3 Yellow Mode Computer in service Computer in maintenance Computer in test
4 Green Power on Not used Not used Power off
(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.
The LEDS 1 to 2 are not used by the extension racks.
2.1.1.2 Other LEDs
Other LEDs’ default assignment:
• LED 6: DIU board fault
• LED 7: AIU board fault
• LED 8: DOU board fault
• LED 9: CCU board fault
• LED 10: AOU board fault
• LED 11: IED fault
• LED 12: Connection status with main rack (redundancy)
• LED 13: Data base version discrepancy with main rack (redundancy)
2.2 Configuration data
The behaviour of the user-configurable LEDs is defined in the computer DataBase.
When using a simple DHMI, the 12 user-configurable LEDs give the status of the associated
BI. Each BI state is displayed using the ON / OFF / BLINKING led state (defined in the DS).
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 ‘C’ 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 ‘C’ 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.
Symptom LED status Possible reason Way to solve

Functions as All LEDs are OFF The cable between Verify the connection
communication, CPU and GHU2xx, or between CPU or GHU2xx.
automation, printing GHU2xx itself is not
If connection is OK and the
are well operating operational
problem is not already solved
and the watchdog on
then change the GHU2xx
BIU is SET.
board.
The supply is ON and All LEDs are OFF Problem with BIU Replace BIU board or CPU
the watch dog on BIU board or CPU board board.
is RESET.
C264 is not running LED1 ON Incoherent database Download a coherent
or not fully database
operational
Hardware fault Go in Fault panel and Board
panel to determine the faulty
board and change it.
C264 is not fully LED1 is blinking A IED is disconnected Go into IED panel to
operational determine the disconnected
IED and verify the cable, the
BIU configuration, the com-
munication parameters inside
the PACiS configurator, the
communication parameters
inside the relay.
The printer is Go into Fault panel and verify
disconnected that paper is available, the
printer is switch ON, the
printer cable
A problem about clock Go into Fault panel and verify
synchronisation that the external clock is
switch ON, the external clock
is connected to the antenna,
the external clock is
connected to the C264.
A problem about PLC Go into Fault panel and
(ISaGRAF) connect the ISaGRAF work
bench to the C264. Verify the
behaviour of the PLC.
The 12 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.
2.2.1 General display management

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.
The key is used for menu navigation. During the menu navigation it has no effect on
LED management.
There are 7 main groups of panels; each group can have several kinds of panel.
The key allows to display the next panel.
From each panel, the key allows the menu tree access.
The keys and allows to access to the different panels of a group.
List of panel groups

Group 1: graphical – one or two panels for each bay with sub panel displays:
− measurement, counter and TPI
− single, double and multiple datapoints status
− controls
Group 2: alarm - one panel displays the alarm list and allows acknowledgement and
clearing
Group 3: two or three panels
• AVR for 1 transformer:
− AVR_VIEW1: large view
− AVR_VIEW2: detail and control view
• AVR for multiple transformers:
− AVR_VIEW1: large View
− AVR_VIEW2: detail and control view
− AVR_VIEW3: analysis view on the C264(s) managing the parallel aspects

Group 4: event - one panel displays the event list
Group 5: defaults - one panel displays the fault list
− if a hardware fault occurs, the board panel is accessible and shows only faulty
boards
− if an IED fault occurs, the IED panel is accessible and shows only disconnected
IEDs
− if one or several IEC61850 clients are not connected, the number of real
connected clients is displayed against the maximum number of clients
Group 6: disturbance - one panel displays the header of the disturbance file
Group 7: service:
− one panel displays general information
− one panel displays the boards state
− one panel to display the IEDs state

Group 8: physical:
− one panel displays the state of the physical inputs
− one panel displays the state of the physical outputs

Group 9: banner - one panel displays general information on C264 to avoid any mistake
Group 10: login & password - two panels, accessible from several panels and used to
select login and enter password
From any panel, a help panel is accessible using the book key. From this panel, a new press
on help key allows to display the graphical panel of the first bay in active mode or the service
panel in maintenance mode.
A number of panels (graphic bay, defaults, AVR, service, banner) are eligible as start panel.
Refer to the AP chapter. If a login panel is required, banner must be the start panel.
Inactivity panel (screen saver) and delay are configurable. Refer to the AP chapter.
2.2.2 Language support

The LHMI supports 2 languages that are chosen during configuration phase. A parameter in
the menu tree allows switching between both languages.
NOTE: The C264 Human interface is also available in Chinese language by
now. Please, contact the Schneider Electric’s local support for more
informations.
2.2.3 Time and date displaying
Local HMI displays time, date and state of time and date of the computer.
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).
12 characters 1 char 8 characters
P A N E L _ N A M E T H H : M M : S S
C0154ENa
FIGURE 2: TIME DISPLAY
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
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
State of date and time: the application software of the computer manages the different
state of the date and time:
• not synchronised (“*”): the date/time has never been synchronised
• synchronised (“ “): date/time is synchronised

Time, date and state are visible and modifiable in the menu tree. To modify time or date,
refer to ST chapter.
2.2.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.
Bay Bay Bay

Panel 1 Panel 2 Panel n
Key 4 Key 4 Key 4
…
Key 4
Key 3 Key 3 Key 3
…
Key 3
Key 2 Key 2 Key 2

…
Key 1
Key 1 = page key :
Key 2 = enter key :

Menu tree
Key 3 = cursor left key :
Key 4 = cursor right key :
C0155ENa
FIGURE 3: BAYS MANAGEMENT

When a bay is displayed on two panels, key4 and key3 are used to move from one panel to
the other.
For one bay:
Graphical Bay Panel Help

sub-panel
Measurement Control State Bypass Interlock

sub-panel sub-panel sub-panel sub-panel sub-panel
C0156ENa
FIGURE 4: BAY MANAGEMENT (CONT'D)

Information displayed in the bay panel is:
• the bay name (fixed position)
• the time (hh:mm:ss) and its status
• 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 exists
• a measurement of CT/VT displayed on a vertical graphical bargraph (Vertical

Measurement Graphical Area) or on a horizontal graphical bargraph (Horizontal
Measurement Graphical Area). VMGA and HMGA are exclusive. Only CT/VT
measurements can be displayed on a bargraph. Up to four CT/VT measurements can
be associated to a bargraph. Buttons and allow to select the

measurement to display on the bargraph. The totality of the bargraph represents either
120% or 200% of the nominal value.
• the name of the measurement (fixed position)
• the value of the measurement (fixed position)
• the command report (fixed position)
• the access to datapoints panels

Example:
Name of the bay
*hh :mm :ss

time and its status
graphical representation
SBMC DPS1
SBMC mode
local/remote mode L/R
interlock bypass EQL BP
synchrocheck bypass S/C BP
vertical bargraph
DPS2
measure value value horizontal bargraph

measure name measure name
command report message message M S C
access to the measurement panel

access to the state panel
access to the command panel
C0300ENa
FIGURE 5: EXAMPLE OF A BAY PANEL

2.2.4.1 State sub-panel

This panel allows to display the state of the digital datapoints (single points, double points
and multiple points).
3 lines are necessary to display any information.
S T A T E <state of the time> <time>

B A Y i
SPS, DPS or MPS 1 (3 lines)
SPS, DPS or MPS 4 (3 lines)…
A SPS / DPS / MPS is defined by:
<Label of the datapoint > = 16 characters maximum

Module of the BI = 16 characters maximum
State of the BI = 21 characters maximum
From this panel, the operator can suppress a datapoint.
S T A T E * 1 2 : 3 4 : 5 6
C 2 6 4 P
D B i n c o h . S P S
C 2 6 4 P
R e s e t
S L o c a l / r e m o t e D P S
R e m o t e
G o s M s g
S e l f c h e c k f a u l t
M o d u l e D P S
G e n e r a l
J a mm e d
1 / 5
S T A T E * H H : MM : S S
C 2 6 4 P
M o d u l e S P S
G e n e r a l
S e t
L o c a l / r e m o t e D P S
L o c a l
S B MC S P S
R e s e t
D S 1 s w g r p o s .
D S 1
C l o s e d
2 / 5
FIGURE 6: EXAMPLES OF STATE SUB-PANELS
2.2.4.2 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 element (Measurement, counter and TPI), each list is composed of
several pages (3 pieces of information per page).
M E A S C O U N T <state of the time> <time>

B A Y i
Measurement 1
Measurement 2
Measurement 3
…
Bay name (fixed position), 16 characters maximum ²

² Chinese: only 10 characters
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.
<Label of the meas > = 16 characters maximum ²

Module of the measurement = 16 characters maximum ²
Value: 7 char Unit (5 char)
State of the meas = 21 characters maximum ²
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.
<Label of the counter > = 16 characters maximum ²

Module of the counter = 16 characters maximum ²
Value: 7 char Unit (5 char)
State of the counter = 21 characters maximum ²
The C264 LHMI displays 32bits and 64bits counter data.

Display of TPI
TPI can be displayed in this panel if defined in database.
<Label of the tpi > = 16 characters maximum

Module of the counter = 16 characters maximum ²
Value: 3 char
State of the tpi = 21 characters maximum ²

M E A S C O U N T
C 2 6 4 P
T e m p 1
M E A S
U n d e f i n e d
_ _ _ _ _ _ _ _ _ _ _ _ _
T e m p 2
M E A S
U n d e f i n e d
1 / 1
M E A S C O U N T
C A L C U 1
M V
D a t a p o i n t s C 1
U n k n o w n
M V 1
U n k n o w n
M V 2
U n k n o w n
1 / 2
FIGURE 7: EXAMPLES OF MEASUREMENTS SUB-PANELS
C O M M A N D <state of the time> <time>

N A M E O F T H E B A Y
Command 1
Command 2
Command 3 ²
Command 4 ²
Page
² does not exist in Chinese LHMI

NOTE: In Chinese LHMI, the bay and module names are not displayed, only
the data point label does.
Name of the bay: only 10 Chinese characters.
The SCE software permits to customize data model informations (labels and values), for
example, operator can be the need to modify some informations (embedded dictionary in the
langage) in order to obtain more accuracy; refer to the SCE operating guide for langage
customization process.
2.2.4.3 Controls sub-panel

The operator is allowed to control devices from the controls sub-panel.
The commands are displayed as following:
Name of the control

Name of the module
state Label order
On this panel, the operator selects the chosen command using the key .
SBO and DE controls are possible according to the configuration
and for OFF and ON

To send a DE control,, operator uses keys
To send a SBO control, operator uses keys and to select OFF or ON. Then
the execution is sent using key .
The current state is displayed on the third line (only ON or OFF).
The button allows to abort the control.
C O M M A N D <state of the time> <time>

N A M E O F T H E B A Y
Command 1
Command 2
Command 3
Command 4
Page
C OMM A N D
C A L C U 1
D P C 1
O N O r d e r O p e n
K l a x o n
S B MC c o n t r o l S P C
O f f O r d e r O n
1 / 2
C OMM A N D
C A L C U 1
S e t P o i n t
+ 0 0 0 0 6 . 0 0
2 / 2
FIGURE 8: EXAMPLES OF CONTROL SUB-PANELS
2.2.4.4 Interlocking sub-panel
When a module is selected in the graphic bay panel, the button c 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.
C O N D I T I O N S <state of the time> <time>
< Label of the device > = 16 characters
E Q L O P E N : state
E Q L C L O S E : state
E X I T
2.2.5 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.
E V E N T <state of the time> <time>

0 0 1 ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯
<Date, time and state of time of the event> =21 char.
<Information about event>
5 lines * 21 char./line maximum:
0 0 2 ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯
<Date, time and state of time of the event> =21 char.
<Information about event>
5 lines * 21 char./line maximum
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)
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.
Display mechanism for an intermediate page:
• The operator visualises 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 visualising 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.
Display mechanism for the last page:
• Last page means visualisation 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.
E V E N T * 1 2 : 3 4 : 5 6
0 0 1 - - - - - - - - - - - - - - - - - -
0 6 /M 0 5 / 10 2 * 1 1 : 2 2 : 3 3 . 1 2 3
C 2 6 4 P
C 2 6 4 P
L o c a l / r e m o t e D P S
R e m o t e
0 0 2 - - - - - - - - - - - - - - - - - -
0 6 /M 0 5 / 10 2 * 1 1 : 2 2 : 3 3 . 5 6 7
C 2 6 4 P
C 2 6 4 P
I S A G R A F s t a t u s
WA I T I N G
0 0 1 / 10 0 0
FIGURE 9: EXAMPLE OF EVENT SUB-PANEL
2.2.6 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.
2.2.7 Alarms 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:
A L A R M <state of the time> <time>
<Date, time and state of time of the last alarm state change > =21 char.
<State of the alarm>=19 char. Max. Gr
<Information about event that generate
the apparition or the state change of the alarm>
5 lines * 21 char./line maximum.
<Date, time and state of time of the last alarm state change > =21 char.
<State of the alarm>=19 char. Max. Gr
<Information about event that generate
the apparition or the state change of the alarm>
5 lines * 21 char./line maximum
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 acknowledgement and clearing is defined in “Controls” chapter.
A L A R M * 1 2 : 3 4 : 5 6
0 6 /M 0 5 / 0 4 * 1 1 : 2 2 : 3 3 . 1 2 3
I N C T A C T U N A C K A L 1
C 2 6 4 P
D S 1
D S 1 C t r l D P C
S e l e c t e d
K O - i n t e r l o c k
0 6 /M 0 5 / 0 4 * 1 1 : 2 2 : 3 2 . 4 5 6
A C T U N A C K A L
C 2 6 4 P
C 2 6 4 P
G o s M s g
R e s e t
0 0 1 / 0 0 2
A L A R M 0 1 : 0 2 : 0 3
0 6 /M 0 5 / 0 4 * 1 1 : 2 2 : 3 3 . 7 8 9
A C T U N A C K A L
C A L C U 1
S P S 7
R e s e t
0 6 /M 0 5 / 0 4 * 1 1 : 2 2 : 3 1 . 9 6 3
A C T U N A C K A L
C A L C U 1
S P S 7
R e s e t
0 0 1 / 0 1 6
FIGURE 10: EXAMPLE OF ALARM SUB-PANEL
2.2.8 Disturbance records 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 C264
D I S T U R B . <state of the time> <time>

FileName ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯
<Record beginning date, time and state of time > =21 char.
<Information about event that causes the recording>:
2 lines * 21 char./line maximum for computer waveform record
Name of the IED for IED disturbance record
FileName ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯
<Record beginning date, time and state of time > =21 char.
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).
Name of the file (format name . cfg) Type (F,S)

Time stamp
Bay Name / Module Name / Datapoint label (up to 2 lines)
(F for fast waveform, S for slow waveform)
• From an IED: 3 files can be displayed per page.
Name of the file (format name . ext)

Time stamp
Name the IED
2.2.9 Configuration panel

The configuration panel allows to display several panels concerning the computer itself:
• Board panel
• External devices panel
• Service information panel
Board Ext. device Service Information

panels panels panel
Key 4 Key 4 Key 4
Key 3 Key 3 Key 3
Key 2 Key 2 Key 2
Key 1
Key 1 = page key :
Key 2 = enter key :

Menu tree Key 3 = cursor left key :
Key 4 = cursor right key :
C0158ENa
FIGURE 11: CONFIGURATION PANELS MANAGEMENT

2.2.9.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).
B O A R D * 1 2 : 3 4 : 5 6
board label B I U
board status O k
G H U 2 0 0
O k
D I 0
O k
D I 1
O k
D I 2
O k
D I 3
O k
1 / 2
B O A R D * 1 2 : 3 4 : 5 7
D O 0
O k
D O 1
O k
D O 2
O k
D O 3
O k
A I U 2 1 0
O k
A I U 2 1 0 1
O k
page number 2 / 2
number of pages
C0301ENa
FIGURE 12: EXAMPLE OF BOARDS SUB-PANEL

2.2.9.2 External devices panel

This panel display all external devices connected to the computer by a legacy protocol and
by the IP protocols (as IEC61850). 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.
server name
IP address state
• Legacy protocol connection state: each IED is displayed with its name, its address,
and the state of its connection.
IED name
address state
The panel for “IP IED” is as follows:
E X . D E V I C E S <state of the time> <time>
I P C L I E N T N B :
I P S E R V E R : protocol
Server 1
Server 2
Server 3
page
The panel for “Legacy IED” is as follows:
E X . D E V I C E S <state of the time> <time>
L E G A C Y D E V I C E protocol
IED 1
IED 2
IED 3
IED 4
page
I E D * 1 2 : 3 4 : 5 6
I P C L I E N T N B : 0 0 0
S C A D A I E D
T 1 0 1 D I S C O N N
0 0 1 / 0 0 2
I E D * 1 2 : 3 4 : 5 7
I E D s : T 1 0 3
P 4 4 2 _3 3
0 0 3 D I S C O N N
P 6 3 2 _4 4
0 0 4 D I S C O N N
P 1 3 9 _ 2
0 0 2 D I S C O N N
P 1 2 7 _ 1
0 0 1 D I S C O N N
0 0 2 / 0 0 2
FIGURE 13: EXAMPLE OF EXTERNAL DEVICES PANEL
2.2.9.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
S E R V I C E * 1 2 : 3 4 : 5 6
S E R I A L N B
0 0 0 0 3 9 6 2
S O F T WA R E V E R S I O N
A 4 . 3 1 A
D B 1 V E R S I O N S T A T E
0 . 3 A C T I V E
D B 2 V E R S I O N S T A T E
N O B D
O P E R A T I N G H O U R S
6 0 1
O P E R A T I N G MO D E
O P E R A T I O N A L
R E D U N D A N C Y MO D E
N O T R E D U N D E
FIGURE 14: EXAMPLE OF SERVICE INFORMATION PANEL
2.2.10 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 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)
E T O R <state of the time> <time>
B O A R D X X Board type
D I X X X value D I X X X value
E T O R * 1 2 : 3 4 : 5 6
board number
B O A R D 0 D I U
board type
D I 0 O N D I 8 O N
D I 1 O F F D I 9 O F F
D I 2 O N D I 1 0 O N
D I 3 O F F D I 1 1 O F F
D I 4 O N D I 1 2 O N
D I 6 O N D I 1 4 O N
input number
input status
1 / 4
C0302ENa
FIGURE 15: EXAMPLE OF BINARY INPUT SUB-PANEL

2.2.11 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:
• 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)
S T O R <state of the time> <time>
B O A R D X X
D O X X X value D O X X X value
S T O R * H H : M M : S S
board number
B O A R D 0 D O U
board type
D O 0 O N D O 8 O N
D O 1 O F F D O 9 O F F
D O 2 O N
D O 3 O F F
D O 4 O N
D O 5 O F F
D O 6 O N
D O 7 O F F
output number
output status
1 / 4
C0303ENa
FIGURE 16: EXAMPLE OF BINARY OUTPUT SUB-PANEL

2.2.12 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

The following figures show the menu tree in the three operating modes.
root
COMMAND MAIN RESET OP HOURS

CHANGE MODE OP
GLB ACK ALARM
GLB CLR ALARM
DATE
TIME
DB SWITCH
LANGUAGE
COUNTER
CONFIG COMPUTER MAIN IP ADDRESS
BAY (name of bay) INTERNAL S/C
AR
DEVICE (name of device 1) TIME OPEN

TIME CLOSE
(name of device i) TIME OPEN
TIME CLOSE
BI ( name of BI 1) MOTION 00 FILT

MOTION 11 FILT
PERS CLOSE FILT
PERS OPEN FILT
TOGGLING OPTION
( name of BI i) MOTION 00 FILT

MOTION 11 FILT
PERS CLOSE FILT
PERS OPEN FILT
TOGGLING OPTION
MV ( name of MV 1) HYSTERESIS
DEADBAND
THRESHOLD1
THRESHOLD2
THRESHOLD3
THRESHOLD4
THRESHOLD5
THRESHOLD6
( name of MV i) HYSTERESIS
DEADBAND
THRESHOLD1
THRESHOLD2
THRESHOLD3
THRESHOLD4
THRESHOLD5
THRESHOLD6
COMM. PORT COMM. PORT 4 BAUDRATE

PARITY
STOP BIT
NB BIT PER CHAR
HMI MAIN EXIT MT TIME
BACK LIGHT DELAY
SELECT EXIT TIME
PASSWORD
BYPASS DELAY
BAY (name of bay) DISPLAY DEV NAME

C0304ENa
FIGURE 17: MENU TREE IN OPERATIONAL AND TEST MODES

root
COMMAND MAIN CHANGE MODE OP

DATE
TIME
DB SWITCH
CONFIG COMPUTER MAIN IP ADDRESS
HMI MAIN EXIT MT TIME

BACK LIGHT DELAY
SELECT EXIT TIME
PASSWORD
BYPASS DELAY
C0305ENa
FIGURE 18: MENU TREE IN MAINTENANCE MODE
2.2.13 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
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)
X Device command Not protected by a password.
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
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
2.2.13.1 Local / Remote control of bay

Local / Remote control of bay for LCD front panel (GHU20x)
The system engineer is allowed changing 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.
2.2.13.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
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.
After a positive acknowledgement of the selection command, the device is displayed in
reverse video.
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.
Interlocking bypass
The operator can send the command using bypass flag on interlocking equation.
The interlocking bypass is set before the execute order sending.
The operator accesses to the bypass flag modification panel by the enter button.
B Y P A S S <state of the time> <time>
N A M E O F T H E D E V I C E
E Q L B Y P A S S O N
E X I T
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).
2.2.13.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 whose 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
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 position of the tap.
• 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.
2.2.13.4 Computer mode

The operator is allowed to change the computer mode between:
• Operational
• Maintenance
• Test
The operator sends this command from the menu tree with a password protection.
2.2.13.5 Data base switch
MiCOM C264 Computer has 2 databases. The operator can switch between both databases.
2.2.13.6 Reset operating hours
The operator is allowed to reset the operating hours counter.
2.2.13.7 Time and date setting
The operator is allowed to set time and date of the computer from the local HMI.
Time and date are set from the menu tree with a password protection.
2.2.13.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.
M E N U T R E E * H H : M M : S S
/ / C O M M A N D / C O U N T E R /
c o u n t e r 1 /
C O U N T E R v a l u e
current value
0 0 0 0 0 0 0 0 0 4
wanted value
0 0 0 0 0 0 0 0 0 4
M I N 0
M A X 2 1 4 7 4 8 3 6 4 7
C0306ENa
FIGURE 19: EXAMPLE OF MANUAL CHANGE VALUE OF A COUNTER

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 button .
2.2.13.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.
2.2.13.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).
2.2.13.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 ‘enter’ 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 Î active acknowledged
inactive unacknowledged Î 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.
2.2.13.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.
2.2.13.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).
2.2.13.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 press the ‘enter’ 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.
2.2.14 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
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
Display event list
Observer
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
Change operating mode
System engineer
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 buttons ½ and ¾ are used to change of selected
character.
The buttons ¿ and À are used to change the value of selected character.
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 in.
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 key .

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.
3. THE COMPUTER MAINTENANCE TOOL

The Computer Administration Tool 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.
For more details, refer to the IN chapter.

4. THE EMBEDDED MAINTENANCE WEB SERVER

When the C264 is equipped with a CPU270 (also named CPU type 3) some maintenance
web facilities are available through the Internet Network. For detailed information, refer to
section 4 of chapter C264/EN MF.
5. THE PRINTER
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.
5.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

5.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, measures, 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.
5.3 Printer management

5.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.
Site Name – Computer Name Date / Time

<blank line>
<Log Book>
<blank line>
Page Number
C0141ENa
FIGURE 20: 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.
5.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).
5.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.
5.3.4 Circular FIFO management
Before being printed, all information goes into a circular buffer
A latency delay is configured to sort information.
latency
Printers Buffer Length Data flow

C0142ENa
FIGURE 21: 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
Origin = Name of the computer (configurable)
ObjectName = SUPPRESSED INFOS (configurable)
ObjectMessage = number of lost information
The following figure 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
PAGE 001
FIGURE 22: EXAMPLE OF SOE PRINT

6. MiCOM S1 V4 FOR MICOM C264P

The C264P Parameter Tool – MiCOM S1 V4 is a tool that gives access to all Protection
parameters of the MiCOM C264P. It allows real-time Proection parameters modification in
complement with the setting fixed by the PACiS SCE.
To access to MiCOM S1 V4 for MiCOM C264P click on
MiCOM S1 V4 enables you to connect to any MiCOM C264P device using the Ethernet
connection, read out and edit its settings and send the modified file back to the choosen
MiCOM C264P device.
NOTE: You find also a direct access to MiCOM S1 V4 , in the CAT page Key
and DB (cf C264P/EN/IN)
6.1 MiCOM S1 V4 Main Window
The main window of the MiCOM S1 V4 comprises the following items:
FIGURE 23: MiCOM S1 V4 PACIS

The Title Bar displays the program’s name and - in square brackets - the name of the open
file (directly derived from the PACiS SCE configurator or upload from the C264P). If a new
settings file has been created, the text "Default Setting" is displayed in place of the file name.
If the file has been edited, a star "*" is displayed additionally. The star disappears after
saving the edited file.
The Menu Bar of the Operating Program is subdivided into the File menu, the Edit menu,
the View menu, the Transmission menu, the Window menu and the Help menu. Many of
the menu commands are not available unless a document window is open. Unavailable
menu commands are shaded in gray.
The Toolbar is aligned horizontally below the menu bar in the application window. It
provides rapid access by mouse click to commands that are frequently used. Non-available
tools are shaded gray just like the associated menu commands.
The Setting Data Window is a split window similar to the Windows explorer.
In the left part of the setting data window, the selected device type and the three top level
folders in the menu tree (Parameters, Operation, Events) are displayed. The menu tree
folder structure corresponds to the branch structure of the menu tree implemented in the
device. Click the '+' next to the folder icon or press the RIGHT key to open the next level. If
there is no '+' next to the folder icon, no subfolders exist. In this case, the function groups
belonging to this level will be displayed.
When a function group is highlighted in the left part of the setting data window, the
parameters present in this folder and assigned to the selected function group will be shown
in the right part of the setting data window.
If the level above the function groups is highlighted then the parameters of all function
groups will be displayed in the right window.
If a data could not be modified, it presented in light grey:
If a data could be modified, it presented in black:
In the column Edited, the following icon is displayed when a data have been modified
6.2 How to use MiCOM S1 V4

The main functions available within MiCOM S1 V4 are:
• Create a new default settings file
• Read out, modify and send a settings file
• Print a settings file
• Read out and save fault data from a device

6.2.1 Create a new default settings file

1. Choose New... from the File menu. The New File dialog box is displayed.
2. Select Settings File and click the OK button.
3. Select the required data model from the list.
4. Select the language
5. Click on the OK button. A new settings file with default settings based on the selected
data model is generated and a new setting data window will be displayed.
FIGURE 24: OPEN EXISTING PARAMETER FILE

6.2.2 Extract a setting file from a device
To open a setting data window, perform one of the following steps:
• Create a new default settings file (see above).
• Choose Open... from the File menu, highlight Settings File in the file type box, and
select an existing settings file.
• Choose Identify Device... from the Communication menu. Select the ranges for baud
rate and device address, select the parity and click the Identity button. If a device is
identified, the Device dialog box with information on this device is displayed. Click the
Settings File button, and a new default settings file suitable for the data model of the
identified device will be created.
Highlight the folder in the left part of the setting data window or highlight the parameter you
want to read out and choose Read Value... from the Communication menu. If the first entry
is highlighted in the left part of the setting data window, that is the name of the IED, the
complete setting will be read out.
NOTE: If you are connected to the device the first time, you should first adapt
the settings file to the design version of the device. Choose Version...
from the Tools menu and click on the Update button.
6.2.3 Modify a settings file
• Highlight the function group in the left part of the setting data window that contains the
parameter to be modified. The parameters in the group are displayed in the right part
of the setting data window.
• Either double-click the parameter to be modified, or highlight the parameter and

choose Set Value... from the Edit menu. The appropriate dialog box for this type of
parameter will be displayed.
• Change the parameter as required and click the OK button to accept the new value.
The parameter will now have a symbol in the Status column to show it has been
changed. In the title bar an asterisk “*” will show that the settings file has been
changed. Both symbols will disappear if the settings file is saved.
6.2.4 Save a settings file
• To save a settings file with the same name, choose Save from the File menu.
• To save a settings file with a new name or in a new location, choose Save As... from
the File menu.
• The User Comment dialog box is displayed. Enter any text up to 255 characters.
6.2.5 Send modified settings to a device
Highlight the folder in the left part of the setting data window or highlight the parameter you
want to send and choose Send Value... from the Communication menu. If the first entry is
highlighted in the left part of the setting data window, that is the name of the IED, the
complete settings file will be sent.
6.2.6 Create a print file
• Highlight the folder in the left part of the setting data window or highlight the parameter
you want to print and choose Print File... from the File menu. If the first entry is
highlighted in the left part of the setting data window, that is the name of the IED, the
complete settings file will be printed.
• Enter a file name and click the OK button.
• The setting will be printed to a text file and will be displayed in the text editor.
• You can print out that print file by using the print function of the text editor.
6.3 Menu and Toolbar

6.3.1 The Menu functions
Six main functions are available within the MiCOM C264 Parameter menus:
• File
• Edit
• View
• Transmission
• Window
• Help
NOTE: Some menu commands are only available if a setting data window is
opened.
6.3.1.1 File commands
FIGURE 25: FILE COMMANDS

New: This menu is only accessible when no C264 Parameter file is open. Display the File
New dialog box, enabling you to open a new parameter file. The following file types are
supported:
Setting File: Create a new setting file.
DNP File: Create a new DNP file (no use in this version).
Open: Display the File Open dialog box, enabling you to open an existing file. The following
file types are supported:
Setting File: Open an existing Setting file.
DNP File: Open an existing DNP file (no use in this version)..
Events File: Open an existing Event file (no use in this version).
Error Log: Open an existing Error Log window(no use in this version).
Close: Close the active document.
Save: Save the active document.
Save as: Save the active document with a new name or in a new location.
Send To: Send the active document to .
Print File: Print the active document.
Page Setup: Display the Print Setup dialog box, enabling you to select a printer and to
modify the printer settings.
Exit: Quit the application.
6.3.1.2 Edit commands
FIGURE 26: EDIT COMMANDS
Undo: Allows to cancel the last made modification.
Copy: Copies the text or the selection and put it on the clipboard.
Paste: Insert the clipboard contents.

Settings: Edits selected cell settings.
6.3.1.3 View commands
FIGURE 27: VIEW COMMANDS
Toolbar: Hide or show the Toolbar (icon bar just bellow the menu bar of the S1V4 screen)..
Statusbar: Hide or show the Statusbar (bottom part of the S1V4 screen).
Expand: Expand the currently selected tree item.
Collapse: Collapse the currently selected tree item.
6.3.1.4 Transmission commands
FIGURE 28: TRANSMISSION COMMANDS
Get Settings: Read the Setting file from the MiCOM C264 connected computer.
Set Settings: Send the Setting file from the MiCOM C264 connected computer.
6.3.1.5 Window commands
FIGURE 29: WINDOW COMMANDS
Cascade: Cascade the open windows.

Tile horizontally: Tile the open windows horizontally.
Tile vertically: Tile the open windows vertically.
Arrange Icons: Arrange icons at the bottom of the window.
6.3.1.6 Help commands
FIGURE 30: HELP COMMANDS
Help Topics: Display the Windows Help File at the Contents page.
About Settings: Display program information, version number and copyright.
6.3.2 TheTool bar functions
The Tool Bar is subdivided into several parts:
• New: by clicking on this button, the user can create a new MiCOM C264P
parameter file.
• Open: by clicking on this button, the user can open an existing MiCOM C264P
parameter file.
• Save: by clicking on this button, the user can save the open MiCOM C264P
parameter file with the modifications or uploaded data.
• Copy: by clicking on this button, the user can copy a data.
• Paste: by clicking on this button, the user can paste the copied data.
• Print: by clicking on this button, the user can print the open MiCOM C264P
parameter file.
• Help button: When the mouse points to a menu command, the left-hand part of
the status bar shows the menu command function. As you open a settings file, the
user comment - as stored in this file - is displayed.
BLANK PAGE
MiCOM C264P
APPLICATION
CONTENT
2. REQUIREMENTS 8
3. MiCOM C264P CONFIGURATION SCOPE 9

3.1 General PACiS system configuration 9
3.2 MiCOM C264P configuration in general PACiS system configuration 9
3.3 Sparing object 10
4. DEFINING MiCOM C264P CONFIGURATION IN SYSTEM

ARCHITECTURE 11
4.1 Setting general system configuration relevant to MiCOM C264P 11
4.2 Adding a MiCOM C264P in the system architecture 15
4.3 Setting general attributes of a MiCOM C264P 17
4.3.1 Configuring binary input (BI) filtering 18
4.3.2 Configuring measurement acquisition and transmission 19
4.3.3 Configuring counter acquisition 20
4.3.4 Configuring internal fault characteristics 20
4.3.5 Locating MiCOM C264P in a substation (mandatory) 20
4.3.6 Defining a MiCOM C264P as system master clock 21
4.3.7 Defining a redundant MiCOM C264P (optional) 22
4.4 Adding MiCOM C264P hardware components 24
4.4.1 Adding boards 24
4.4.2 Setting specific attributes to MiCOM C264P boards 26
4.4.3 Adding extra communication channels to CPU board 29
4.4.4 Configuring a communication channel 29
4.4.5 Configuring an AI channel 32
4.4.6 Adding a printer 33
4.4.7 Configuring an Analogue Output (AO) channel 35
4.5 C264P IP adress and routing table definition 37
4.5.1 C264P as a gateway connected to a router and a remote IEC104 Scada 37
4.5.2 C264P as a gateway directly connected to a remote DNP3 Scada 40
4.6 Networking MiCOM C264P on the station-bus network 41
4.6.1 Connecting MiCOM C264P to others station-bus sub-systems 41
4.6.2 Defining addressing mapping of station-bus network 43
4.6.3 Addressing datapoint on station-bus network 55
4.7 Networking IED on MiCOM C264P legacy network 56
4.7.1 Creating a legacy network of IED 56
4.7.2 Defining addressing mapping of a legacy IED 64
4.7.3 Addressing a datapoint on an IED legacy network 82
C264P/EN AP/C80 Application
4.8 Networking SCADA on MiCOM C264P SCADA network 83

4.8.1 Creating a SCADA network 83
4.8.2 Defining addressing mapping of SCADA network 92
4.8.3 Addressing datapoint on SCADA legacy network 106
4.9 Defining wave record file management (Disturbance File) 107
4.9.1 Defining management of disturbance file for IED 107
4.9.2 Defining T103 IED extra information for disturbance file 109
4.9.3 Defining management of wave record file for MiCOM C264P CT/VT board 111
4.10 Defining a MiCOM C264P klaxon 119
4.11 Setting system information for components 120
4.11.1 Setting general system information of a MiCOM C264P 121
4.11.2 Setting system information of board 125
4.11.3 Setting system information of legacy IED 127
4.11.4 Setting system information of serial printer 128
4.11.5 Setting system information of a SCADA network 129
5. DEFINING DATAPOINT 130

5.1 Creating a datapoint 130
5.1.1 Overview of binary input processing 130
5.1.2 Defining an SPS datapoint 131
5.1.3 Defining a DPS datapoint 133
5.1.4 Defining an MPS datapoint 135
5.1.5 Overview of measurement processing 137
5.1.6 Defining MV datapoint 139
5.1.7 Defining a TPI datapoint 143
5.1.8 Defining a Counter datapoint 146
5.1.9 Overview of control sequence processing 150
5.1.10 Defining an SPC datapoint 150
5.1.11 Defining a DPC datapoint 156
5.1.12 Defining a SetPoint datapoint 160
5.2 Linking a datapoint to a profile 166
5.2.1 Defining an SPS profile 168
5.2.1.1 Adding an SPS Profile 168
5.2.2 Defining a DPS profile 172
5.2.3 Defining an MPS profile 177
5.2.4 Defining an MV profile 183
5.2.5 Defining a Counter profile 189
5.2.6 Defining an SPC profile 193
5.2.7 Defining a DPC profile 197
5.2.8 Defining a SetPoint profile 201
5.3 Defining MiCOM C264P local archiving of datapoint events 204
5.4 Defining MiCOM C264P local archiving of datapoint alarms 204
5.5 Defining MiCOM C264P local logging of datapoint events and alarms 204
5.6 Defining acquisition source for input datapoints 204

5.6.1 Acquiring input datapoint via input channels 204
5.6.2 Acquiring input datapoint via an IED legacy network 209
5.6.3 Acquiring input datapoint via non-PACiS IEC61850 communicant IED 210
5.6.4 Producing input datapoint 211
5.7 Defining control source for output datapoints 213
5.7.1 Controlling output datapoint via output channels 213
5.7.2 Controlling output datapoint via an IED legacy network 216
5.7.3 Controlling output datapoint via non-PACiS IEC61850 communicant IED 217
5.7.4 Producing output datapoint 218
5.8 Defining datapoint association 219
5.8.1 Adding a target datapoint 219
5.8.2 Linking the target datapoint to the original datapoint 220
5.8.3 Defining the states associations 222
6. DEFINING MiCOM C264P CONFIGURATION IN ELECTRICAL

ARCHITECTURE 223
6.1 Defining an electrical topology 223
6.1.1 Defining a Site 225
6.1.2 Defining a Substation 225
6.1.3 Defining a Voltage level 230
6.1.4 Defining a Bay 232
6.1.5 Defining Module 238
6.2 Defining a Synchrocheck function 249
6.3 Defining an Auto-Recloser built-in function 249
6.3.1 Auto-Recloser behaviour 249
6.3.2 Creating an auto-recloser (AR type 1) function 249
6.3.3 Creating an auto-recloser (AR type 2) function 254
6.4 Defining a Tap changer built-in function 260
6.4.1 Tap changer behaviour 260
6.4.2 Creating a tap changer built-in function 261
6.4.3 Controlling xPC by xPS change of state 263
6.5 Defining an Automatic Voltage Regulation (AVR) or Automatic Tap Change
Control (ATCC) built-in function 264
6.6 Defining an electrical automation/regulation by user function 264
6.6.1 Defining a FBD fast automation 264
6.6.2 Defining an ISaGRAF slow automation 270
6.6.3 Defining a group 278
6.6.4 Controlling xPC by xPS change of state 280
6.6.5 Producing a DPS from two SPS 281
6.6.6 Defining interlocking 281
6.6.7 Defining an automatic/manual dependency 283
7. DEFINING MiCOM C264P LOCAL HMI 284

7.1 Using bitmap table 284

7.2 Defining a MiCOM C264P workspace 285
7.2.1 Settings LHMI labels 285
7.2.2 Creating a workspace 286
7.3 Defining a MiCOM C264P bay mimic 288
7.3.1 Creating a MiCOM C264P bay mimic 288
7.3.2 Defining static part: line, bitmap, fixed text 290
7.3.3 Defining dynamic part: pre-defined dynamic text, generic module representation,
transformer representation 293
7.3.4 Assigning MV to bay mimic 300
7.4 Displaying datapoint status with Led 302
8. DEFINING PROTECTION FUNCTIONS 303

8.1 General 303
8.1.1 General architecture 303
8.1.2 Defining a protection function 304
8.2 [27] Undervoltage protection 305
8.2.1 Description of the protection 305
8.2.2 Defining Undervoltage protection function 305
8.3 [32N] Earth wattmetric protection 307
8.3.2 Defining earth wattmetric protection function 307
8.4 [37] Undercurrent protection 309
8.4.2 Defining Undercurrent protection function 309
8.5 [46] Negative Sequence Overcurrent protection 310
8.5.2 Defining Negative Sequence Overcurrent protection function 310
8.6 [49] Thermal overload protection 312
8.6.2 Defining Thermal overload protection function 312
8.7 [59N] Zero Sequence Overvoltage protection 313
8.7.2 Defining [59N] Zero Sequence Overvoltage protection function 313
8.8 [67] Directional overcurrent protection 314
8.8.2 Defining [67] Directional overcurrent protection function 314
8.9 [67N] Directional Earth Fault protection 316
8.9.2 Defining [67N] Directional earth fault protection function 316
8.10 [81O] Overfrequency protection 318
8.10.2 Defining [81O] Overfrequency protection function 318
8.11 [81R] Range Frequency protection 320

8.11.2 Defining [81R] Range Frequency protection function 320
8.12 [81U] Underfrequency protection 322
8.12.2 Defining [81U] Underfrequency protection function 322
9. DEFINING AUTOMATISM FUNCTIONS 324

9.1 General 324
9.2 General architecture 324
9.2.1 Adding automatism function 325
9.3 Protection setting groups 326
9.3.1 Description 326
9.3.2 Setting “2 protection group” automatism functions 326
9.4 [50BF] breaker failure 327
9.4.2 Setting “[50BF] breaker failure” automatism functions 327
9.5 Blocking protection 328
9.5.2 Setting ‘Blocking protection’ automatism functions 328
9.6 Cold load start 329
9.6.2 Setting ‘Cold load start’ automatism function 329
9.7 Logic selectivity 330
9.7.2 Setting ‘Logic selectivity’ automatism function 330
9.8 Maintenance 331
9.8.2 Setting ‘Maintenance’ automatism menu 331
9.9 Miscellaneous 332
9.9.2 Setting ‘Miscellaneous’ automatism menu 332
9.10 Trip management 334
9.10.2 Setting ‘Trip management’ automatism menu 334
BLANK PAGE

The present document is a MiCOM C264P section of the documentation binder. This
document is intended to present you how to configure the MiCOM C264P. It is the section
Application (AP) of this Product.
2. REQUIREMENTS
First, if it is not already done, you will need to install the PACiS SCE (System Configuration
Editor), see the chapter IN (Installation) of this product.
This document presents you the objects and the attributes of a referenced database made
with the PACiS SCE. For understanding this document you first need to be familiar with
PACiS SCE and PACiS C264P.
To add an IEC-61850 MiCOM C264P into an existing system you need to have the mapping
of the system (IP address, Network names of equipment…).
To generate a template, for an existent IEC-61850 MiCOM C264P, see the chapter
Functional Description of the SCE product.
3. MiCOM C264P CONFIGURATION SCOPE

3.1 General PACiS system configuration
To define a complete PACiS system, three aspects should be taken into account.
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 C264P local HMI).
When creating a new configuration using 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 one ‘Ethernet network’ object (Scs is
an abbreviation of Substation Control System).
− A ‘Graphic’ object for the graphical topology.
FIGURE 1: GENERAL ARCHITECTURE OF A PACiS CONFIGURATION IN SCE

3.2 MiCOM C264P configuration in general PACiS system configuration
In general PACiS system configuration, MiCOM C264P is concerned by the three topologies:
− System topology (Scs): MiCOM C264P is a direct sub-component of the Ethernet

network used for communication at station bus level.
− Electrical topology (Site): MiCOM C264P manages bays and relevant modules or
substation information.
− Graphical topology (Graphic): MiCOM C264P can own a LCD display used for
animated graphical bay panel representation and others list panels.
3.3 Sparing object

At SCE level, a spare object is an object having its spare attribute set to true. The
configurations of this object and of its spare attribute are the same as for any other object
and attribute. Any objects can be spare and particularly those concerning the MiCOM C264P
configuration.
Spare objects are not provided to the generator tools, respecting the following rules:
− An object O2, not spare, linked directly or not to a spare composite parent object O1,
is considered as spare.
O1 (Spare = Yes)
O2 (Spare = No)
S0387ENa
− A relation defined on an object O1, not spare, and linked to a spare object O2, is
considered as a relation without link.
O1 (Spare = No)
link
Relation O2 (Spare = Yes)
S0388ENa
4. DEFINING MiCOM C264P CONFIGURATION IN SYSTEM ARCHITECTURE

4.1 Setting general system configuration relevant to MiCOM C264P
System configuration is done at Scs root. It is relevant to some general behaviour of PACiS
devices.
It concerns those specific attributes:
− Common labels used for control acknowledgement, 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 others 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.

As system device, MiCOM C264P can be master clock of the system and is always located
in a substation.
Some attributes of Scs objects concern all the MiCOM C264P defined under the station
network. Hereafter, are listed these attributes:
‘General’ tab:
1. time zone: used for timestamp information.
2. behaviour on DOU failure (Control refused on faulty board / Computer goes in faulty
mode).
3. computer password: local HMI password by default.
4. SBMC management for group (Yes/No): SBMC (Site Based maintenance Control)
mode management for group.
5. TCP/IP addressing for SMT: TCP/IP address using System management Tool
(SMT). The value must be unique among all the devices per Ethernet Network (except
for OI server and OI client).
6. TCP/IP addressing for SNTP Server: TCP/IP addresses (main and secondary) using
Simple Network Time Protocol (SNTP). The value must be unique among all the
devices per Ethernet Network (except for OI server and OI client).
‘Label’ tab:
7. Labels for missing card: Default board labels and status.
8. Order steps are unused at protection level.
9. Control acknowledgement labels used for order logging.
10. Timestamp quality labels are unused at computer level.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
FIGURE 2: GENERAL AND LABELS ATTRIBUTES OF SCS

(9)
(10)
FIGURE 3: LABELS ATTRIBUTES OF SCS (CONT’D)

‘Alarm’ tab:
11. Unused at computer level.
12. G1 to G5 default alarm clearing mode (Manual / Automatic).
At MiCOM C264P level, default alarm processing type is not significant, because alarm
processing is always ‘data basis’ for computer.
Audibility features are not applicable to MiCOM C264P configuration.
(11)
(12)
FIGURE 4: ALARM ATTRIBUTES OF SCS

13. ’Computer routing’ attributes:
− Gateway TCP/IP address: IP address of intermediate “Router” (if present)
− Target TCP/IP address: IP address of authorised remote “Client” (Scada,…)

Please refer to the “C264P IP address and routing table” paragraph for details.
(13)
FIGURE 5: MiCOM C264P ROUTING ATTRIBUTES OF SCS

4.2 Adding a MiCOM C264P in the system architecture

Two models of MiCOM C264Ps are available: C264P 40TE and C264P 80TE.
The height for the both MiCOM C264Ps is 4U.
The different kinds of MiCOM C264P have the following features:
Type Width Mandatory hardware Bus width Input/Output

C264P 40TE BIU with 2 serial ports 3 free slots DIU, DOU,
CPU with 2 optional serial ports CCU, AIU, AOU
C264P 80TE BIU with 2 serial ports 13 free slots DIU, DOU,
CPU with 2 serial ports optional CCU, AIU, AOU
The addition of a MiCOM C264P definition is done via the “Objects entry” window at Ethernet
network level by clicking on mouse’s right button as the following:
FIGURE 6: ADDING A MiCOM C264P IN THE SYSTEM ARCHITECTURE

Default components of MiCOM C264P
When you add from the “Objects Entry” window, for example a MiCOM C264P, you will
obtain the following sub-tree of the MiCOM C264P definition with the default components as
follows:
(1)
(2)
(3)
(4)
FIGURE 7: DEFAULT COMPONENTS OF THE MiCOM C264P

1. Binder ‘Hardware’, that groups all defined boards and printers of the MiCOM C264P
(see § 4.4).
2. Binder ‘System infos’, that groups all general system datapoints of the MiCOM C264P
(see § 4.11).
3. ‘PLC’ object for Programming Logic Chart that corresponds to ISAGRAF and PSL
project directory (see § 8).
4. ‘IEC mapping’ object, that describes the station-bus network addressing mapping of
datapoints managed by the MiCOM C264P (see § 4.5).
4.3 Setting general attributes of a MiCOM C264P

When adding a MiCOM C264P on the Ethernet network, some of its attributes must be set
and verified. Hereafter are listed these attributes.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 8: GENERAL ATTRIBUTES

1. short name and long name: used for logging, alarms…
2. rack model (80 TE / 40 TE): there exist two models of MiCOM C264P: one is a large
size computer model (80TE), the second is a compact model (40TE). The height of
both MiCOM C264P is 4U.
3. with Switch board (Yes / No): Presence of switch board (SWU200, SWR212 (or 214)
or SWD212 (or214)).
4. date format: this attribute defines the date format used in the MiCOM C264P HMI
(LCD).
5. Timer for Scada GI (ms) is unused at computer level.
6. Timestamped ‘unknown’ for SCADA is unused at computer level.
7. synchronisation source (None / IRIG-B): indicates if the MiCOM C264P 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.
8. TCP/IP address and network name of the MiCOM C264P.
Configuration rules and checks
• The "TCP/IP address" value of a device must be unique among all the devices per
Ethernet Network (except for OI server and OI client).
• The "network name" value of a device must be unique among all the devices per
Ethernet Network (except for OI server and OI client).
4.3.1 Configuring binary input (BI) filtering

There exist two types of input signal handling:
• Debouncing: the start transition is signalled with the correct time, the following
changes within the debounce time are ignored. The range of the debounce time is
from 0 to 20ms (with a 1ms step). The event is time tagged at the instant of the first
transition.
• Filtering: the transition is only signalled if the signal is stable for minimum as long as
the filtering time. The range of the filtering time is from 0 to 20ms (with a 1ms step).
The filtering is allowed only if the debouncing is applied (i.e. the filtering cannot be
applied if there is no debouncing before).
The event is time tagged at the instant of the first transition.
Filtering time
Debouncing
time
t0 t1 t2
C0127ENa
FIGURE 9: DEBOUNCING AND FILTERING

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.
(1)
(2)
(3)
FIGURE 10: SETTING BI ACQUISITION ATTRIBUTES

1. debouncing delay (range [0, 20ms], step 1ms).
2. filtering delay (range [0,.20ms], step 1ms.
3. Toggling attributes are defined as the following:

A digital input (DI) is said to be toggling if its state has changed more than N times in a
given period of time T1.
A toggling DI returns in the normal state if its state has not changed within another
period of time 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.
4.3.2 Configuring measurement acquisition and transmission
(1)
(2)
(3)
(4)
FIGURE 11: MEASUREMENTS VALUES ATTRIBUTES

1. Debouncing delay and filtering delay: used for digital measurements (see 4.3.1 –
Configuring binary input (BI) filtering for details).
2. Analogue measurements acquired on AIU board: acquisition samples ranges for long
scanning (range [500ms, 10000ms], step 500ms) and short scanning (range [100ms,
1000ms], step 100ms). For each channel of AIU board, short or long scan period
should be chosen (refer to section 4.4.5 – Configuring an AI channel).
3. Acquisition on TMU board with CTVT fundamental 50 or 60 Hz (number of harmonics
is fixed to maximum 16).
4. 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).
be set to 0.
4.3.3 Configuring counter acquisition
(1)
FIGURE 12: COUNTER ACQUISITION ATTRIBUTES

1. debouncing delay and filtering delay: used for digital counters (see 4.3.1 for details)
be set to 0.
4.3.4 Configuring internal fault characteristics
(1)
FIGURE 13: MISCELLANEAOUS ATTRIBUTES

1. Number of software faults allowed in a given period else the MiCOM C264P remains
in HALT mode. MiCOM C264P reboots automatically as long as it does not reach the
‘fault max number’ in the ‘fault detection time’ period. When this critera is reached
MiCOM C264P remains in HALT mode.
4.3.5 Locating MiCOM C264P in a substation (mandatory)
As said in section 4.1 – Setting general system configuration relevant to MiCOM C264P ,
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 MiCOM C264P.
(1)
FIGURE 14: LOCATING MiCOM C264P IN A SUBSTATION

4.3.6 Defining a MiCOM C264P as system master clock

As said in section 4.1 – Setting general system configuration relevant to MiCOM C264P ,
only one system device can be master clock for the system. This is done by entering the
mandatory relation (1) “has for master clock:“ at Scs level. Only a MiCOM C264P can be
defined as system master clock.
(2)
(1)
(3)
(4)
FIGURE 15: DEFINING A (TWO) PROTECTION(S) AS SYSTEM MASTER CLOCK

4.3.7 Defining a redundant MiCOM C264P (optional)

To define a redundant MiCOM C264P:
• Create the main MiCOM C264P, considered as master one.
• Via the contextual menu of the protection, run “Create backup” (1).
Then:
• An extra MiCOM C264P (considered as slave one) is automatically created with an

implicit relation of backup between the two MiCOM C264P.
• Extra relation ‘has for IEC61850/IEC server’ is automatically created for the main
protection.
• Once the backup MiCOM C264P has been created, its attributes and constitution are
locked for updating and follow the main MiCOM C264P 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 the main MiCOM
C264P the same object is added to (resp. removed from) the backup MiCOM C264P,
but attributes cannot be modified.
To finalise redundant MiCOM C264P configuration, an extra system datapoint ‘redundancy
mode’ has to be added in ‘System infos’ binder of the main MiCOM C264P. IEC61850
addressing of this datapoint is required and automatically done during its creation (see
chapter 4.6.2 – Defining addressing mapping of station-bus network for details about
IEC61850). Do not forget to configure a relevant SPS profile for ‘redundancy mode’ SPS
datapoint (refer to chapter 5 – Defining datapoint).
(1)
FIGURE 16: DEFINING A REDUNDANT MiCOM C264P (CREATION ACTION)

Automatic creation of
"has for UCA2/IEC
server" relation for the
main computer
Slave computer created

after manual updating of
its short and long names,
and IP characterisitics
Automatic creation of
"backup" relation between
the two computers
C0166ENc
FIGURE 17: DEFINING A REDUNDANT MiCOM C264P (ONCE CREATED)

4.4 Adding MiCOM C264P hardware components

4.4.1 Adding boards
PACiS MiCOM C264Ps are composed of boards, responding to specific functions (refer to
chapter C264P/EN HW for the complete description of the protection):
• DIU200 Digital input boards with 16 digital input channels:

- digital and counter acquisition
- digital measurement acquisition
• AIU201 - Analogue input board with 4 analogue input channels:

- analogue measurement acquisition
• AIU211 - Analogue input board with 8 analogue input channels:

- analogue measurement acquisition
• optional SWU200 (Ethernet SWitch Unit board) with 4 RJ45 ports and up 2 optical
ports (multimode or monomode),
• optional SWR212 (Ethernet SWitch for Redudancy board) with 4 RJ45 ports and 2
optical ports for a redundant ring (multimode or singlemode),
• optional SWD212 (SWD214) (Ethernet SWitch for Dual attachement board) with 4
RJ45 ports and 2 optical ports for a dual attachement star architecture (multimode or
singlemode
• TMU210 - CT and VT input board with 4 CT and 4 VT input channels:

- ct/vt sampling acquisition,
- MV computations based on acquired samples
• DSPIO – Protection calculation and input/output board ; daughter board on the CPU
board; the DSPIO is associated to TMU210 and equipped with a DSP Processor
(floating point calculation): it supports the protection functions
• DOU201 - Digital output board with 10 digital output channels:

- execution of single or dual, transient or permanent commands
- setting of digital setpoints
• CCU200 - Mixed digital 8 input and 4 output board with digital input and output
channels (take good care the DO 4,5,6,7 are defined but not used):
- Circuit breaker Control Unit
• ECU200 or ECU201 (Extended Communication Unit board)
• CPU260: CPU board with communication channels (1*Ethernet on CPU260)
• BIU241/BIU261: Power Supply board with communication channel(s) (serial

communication port(s))
• GHU200, GHU 201 Graphical panel boards with led channels (GHU200 for 40TE and
GHU 201 for 80TE)
• AOU200: Analogue output board with 4 Analogue output channels.

Computer hardware definition is done in SCE by adding typed boards below computer
object. Mandatory boards (CPU260/CPU270, GHU200, BIU241/BIU261) are automatically
created at computer’s creation.
Linking datapoint to channels does datapoint wiring (see chapter 5 – Defining datapoint).
An addition of a board definition is done via the “Objects entry” window by clicking on
mouse’s right button as the following:
FIGURE 18: ADDING A BOARD TO THE MiCOM C264P

Slots and boards in a C264P 80TE protection
A B C D E F G H I J K L M N O P Q
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]
BIU CPU DSP TMU210
Slots and boards in a C264P 40TE protection
A B C D E F G H
[1] [2] [3] [4]
BIU CPU DSP TMU210
• Slot A contains BIU241 board; Slot B contains CPU2xx board.
• Slots 2 to 13 (from D to P) (80TE) or 2 to 4 (D to F) (40TE) may contain a board of the

following types: AIU201, AIU211, AOU200, DOU201, DIU200, DIU211, CCU200 or
optional switch boards (SWU21x, SWD21x or SWR21x).
• If present the Ethernet boards (SWU21x, SWR21x, SWD21x) are to be installed in

slots D.
• Slots P and Q (80TE) or G and H (40TE) may contain one TMU210 board.
• A MiCOM C264P is able to manage up to 4 AOU boards and the AOU board cannot
be used in a MiCOM C264P redundant environment.
4.4.2 Setting specific attributes to MiCOM C264P boards

4.4.2.1 Setting common attributes to MiCOM C264P board
For each board of the MiCOM C264P, the short (or long) name attribute (1) may be updated
for correct logging and alarm discrimination concerning board status datapoint.
For boards AIU2xx, CCU200, DIU200, DOU201 or AOU200 the physical board number
attribute (2) must be updated.
For boards CPU260, BIU241/BIU261, GHU200 and TMU2x0, this attribute is forced to 0 by
the SCE and is not displayed in the attributes window.
(1)
(2)
FIGURE 19: GENERAL ATTRIBUTES OF A BOARD

• Per board type (AIU201, AIU211, AOU200, DOU201, DIU20x, CCU20x), the physical
board number attribute values must begin from 0, be unique and contiguous.
4.4.2.2 Setting specific features of a 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 20: 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 7.2 defining a
computer workspace.
FIGURE 21: DEFINING WORKSPACE FOR COMPLETE GHU200 BOARD

For computer LED configuration, refer to section 7.4 Displaying datapoint status with Led.
• 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.
4.4.2.3 Setting specific attributes of a TMU210 board
For TMU210 board, the following attributes have to be set for correct CT/VT computation of
extra measurements:
1. electrical network topology (3 Vpn (star) / 3 Vpn + V0 (star) / 3 Vpn + V0 (partial
star), 3 Vpn + V0 (partial delta) / 3 Vpn + V0 (delta), 3 Vpn + Vb (star), 3 Vpn + Vb
(delta)).
2. reference phase (Phase A / Phase B / Phase C).
3. reference phase side (Phase A, B, C wired line side / Phase A, B, C wired busbar
side).
4. voltage range (57 V - 130 V / 220 V - 480 V).
5. nominal and transformer nominal currents (positive and zero sequence) and
nominal and transformer nominal voltages (positive and zero sequence).
6. Transformer sensibility (not sensible / sensible / very sensible).
Extra attributes are reserved for future use.
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 22 TMU210 BOARD SPECIFIC ATTRIBUTES

If reference phase signal is absent, values transmitted by TMU board are set to invalid.
Please refer to the Chapter CO (Connections) for the description of the TMU2xx electrical
CT/VT inputs and database association.
4.4.2.4 Setting specific features of BIU241/BIU261 board
The BIU board type is choiced from BIU attributes
FIGURE 23: SELECT TYPE 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 24: DISPLAY SPS VOLTAGE SOURCE 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).
4.4.3 Adding extra communication channels to CPU board
At CPU260 board level, the frontal RS232 port is mandatory and automatically created at
board creation. Two extra communication channels can be added from SCE objects entry
window (Figure 27: General and transmission attributes of a communication channel).
FIGURE 25: ADDING COMMUNICATION CHANNELS

4.4.4 Configuring a communication channel
A communication channel is a physical port available on CPU or the BIU board at their
creation (see chapter 4.4.1 – Adding boards) or manually added as option (see chapter
4.4.3 – Adding extra communication channels to CPU board).
A communication channel can be used exclusively for:
1. Communication with an IED legacy network.
2. Communication with a SCADA network.
3. Communication with a serial printer.
(1)
(2)
mandatory frontal port
(3)
C0167ENb
FIGURE 26: USAGE OF COMMUNICATION CHANNEL

Once used by a communication link, the physical port has to be set relatively to the
communication link characteristics (Figure 27):
− “General” window:
1. RS type (RS232 / RS485).
− “transmission” window:
2. baud rate (bits/s) (50 / 100 / 200 / 300 / 600 / 1200 / 2400 / 4800 / 9600 / 19200 /
38400 / 56000 / 64000)
NOTE: For the CPU260 board with serial ports 3 and 4, this attribute (baud
rate) must be set to the same value . For the CPU270 ports 3 and 4,
the baud rate can be different.
3. parity (No parity / Odd parity / Even parity)
4. number of stop bits (1 bit / 2 bits)
5. nb. bits per char (7 bits / 8 bits)
6. Tx carrier management (Switched / Constant / Soft):
− Switched: when the MiCOM C264P 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 MiCOM C264P waits during a time defined by attribute
(10) before resetting the RTS line.
− Constant: the RTS line is always set by the MiCOM C264P. 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 MiCOM C264P.
7. CTS wired (No / Yes): this attribute must be set to YES if the TX carrier
management attribute is set to Switched or to Constant.
8. CD wired (No / Yes): in order for the DCD line to be managed by the MiCOM C264P
this attribute must be set to YES if the TX carrier management parameter is set to
Switched.
9. pre TX time (range [0, 1s], step 1ms): this attribute is visible and therefore significant
only if attribute (6) is set to Switched.
10. post TX time (range [0, 1s], step 1ms): this attribute is visible and therefore significant
only if attribute (6) is set to Switched.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10
)
FIGURE 27: GENERAL AND TRANSMISSION ATTRIBUTES OF A COMMUNICATION CHANNEL

4.4.5 Configuring an AI channel

An AI channel is an analogue input available on AIU201 and AIU211 boards at their creation.
AI channels are used for analogue measurement acquisition.
implicit AI#0 to
AI#3 channels
creation on
AIU200 board
C0168ENb
FIGURE 28: USAGE OF ANALOGUE CHANNELS

Once used by a MV, the AI has to be set relatively to the acquisition characteristics:
1. sensor range for AIU201 –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 / -10 V … +10 V / –5 V … +5 V / –2.5 V … +2.5 V / –1.25 V …
+1.25 V
sensor range for AIU211/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
2. acquisition period (short period / long period): refer to section 4.3.2 – Configuring
measurement acquisition and transmission.
(1)
(2)
FIGURE 29: CONFIGURING AN AI CHANNEL

4.4.6 Adding a printer

SCE data modelling describes printers used in PACiS system for ‘sequence of events’ and
log book functions at operator interface level and MiCOM C264P level.
A printer at MiCOM C264P level must be a serial one connected to a communication
channel of the.
To create a MiCOM C264P printer:
• Add a serial printer from object entry available at MiCOM C264P level.
FIGURE 30: ADDING A SERIAL PRINTER
• Update its ‘has for communication port’ relation (1) and its attribute ‘printer control’ (2).
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 31: 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:
3. page size (range [20 lines, 65535 lines ], step 1 line).
4. buffer size (range [100 events, 3000 events ], step 100 events).
5. number of events to suppress when buffer is saturated (range [30 events, 1000
events ], step 10 events).
6. Rank of the different columns used for printing formats.
• 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:
origine
time stamp object name
chronology object message
C0169ENa
FIGURE 32: THE DIFFERENT COLUMNS USED FOR PRINTING FORMATS

• The value of each "… column rank" attribute must be unique.

4.4.7 Configuring an Analogue Output (AO) channel
An AO channel is an analogue output (AO) available on AOU200 at their creation in SCE.
Four Analog Output (AO) channels (1) are available.
(1)
FIGURE 33: USAGE OF ANALOGUE CHANNEL

An AO channel has following attributes:

1. Output current maintained mode: (Yes No)
Each current output is individually managed in 2 modes:
• 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.
• Un-maintained Mode: in case of computer shut down or power off, the output is
set to 0.
2. 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
(1)
(2)
FIGURE 34: CONFIGURING AN AO CHANNEL

4.5 C264P IP adress and routing table definition

You’ll find hereafter example of C264P adressing and routing table definition in two typical
C264P application cases.
4.5.1 C264P as a gateway connected to a router and a remote IEC104 Scada
T104 SCADA
client address
192.168.10.5,
192.168.10.9,
192.168.10.110,
192.168.10.54
192.168.10.0
192.168.10.99
192.168.20.99
PACiS
192.168.20.0
192.168.20.1
subnet mask 255.255.255.0
192.168.20.98
192.168.30.12
WebServer or other IP application (CMT, SMT, ...)

192.168.30.2
192.168.30.0
C0426ENa
4.5.1.1 C264P Routing table parameters

In SCE configuration C264’s 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.
NOTE: “Gateway TCP/IP address” is not linked to the C264P’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 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”.
4.5.1.2 T104 protocol configuration

It is possible to secure T104 client remote connection by giving a short list of authorized
clients.
In the example, T104 SCADA link configuration is to be as defined as hereafter:
4.5.1.3 C264P IP adress definition

The C264P IP adresss is defined
− locally with the C264P LCD
− Using the CMT maintenance Tool (Over Ethernet)
− Using C264P’s maintenance shell (for maintenance Experts only)

In the example the C264P 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.
4.5.1.4 C264P IP Parameters with the maintenance CMT tool
IP on Ethernet: the Internet address of the Ethernet interface.

The Internet addresses (IP) are specified in "dot" notation (e.g., 10.22.92.52).
Example: 10.22.92.52
This field can have an optional subnet mask of the form inet_adrs:subnet_mask.
Example: 10.22.92.52:0xFFFF0000 Î subnet mask = 255.255.0.0

10.22.92.52:0xFF000000 Î subnet mask = 255.0.0.0
By default, the subnet mask is set to 0xFFFFFF00 Î subnet mask = 255.255.255.0

4.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 boards 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):
To enable IP routing for all network connections installed and used by this MiCOM C264P,
assign a value of 1.
This will take effect after rebooting MiCOM C264P.
4.5.1.6 PC configuration when using the C264P maintenance Webserver
On WebServer’s PC it is necessary to define and add the “route” to access the C264:
-> open a DOS command and type: Route ADD 192.168.20.1 MASK 255.255.0.0
192.168.30.12.
(According the usual definition “route ADD @target MASK mask @gateway”)
4.5.1.7 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.
WARNING: C264P IS DESIGNED FOR FIXED IP ADRESS NETWORK: IP
ADRESSING CONFLICTS COULD BE MET WITH THE C264P INSTALLED
ON NETWORKS WITH DHCP ADRESSING.
4.5.2 C264P as a gateway directly connected to a remote DNP3 Scada
NOTE: In case of DNP3/IP SCADA connected to C264-GTW without using

any router, it is not necessary to configure IP addressess at SCS level
(Gateway TCP/IP address, Target TCP/IP address).
In this example, C264P 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.
4.5.3 C264P as a gateway connect maximum of 4 DNP-IP SCADA Protocols
FIGURE 35: C264P CONNECTED TO A SCADA (MAXIMUM DNP-IP SCADA PROTOCOLS)

In this example, 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:
FIGURE 36: DEFINING DNP-IP CONFIGURATION WITH 4 SCADA DNP-IP

4.6 Networking MiCOM C264P on the station-bus network

MiCOM C264P connection to the station-bus is implicitly done by adding the protection
hierarchically to the Ethernet network (see section 4.2 – Adding a MiCOM C264P in the
system architecture) and by setting the IP characteristic of the MiCOM C264P (see 4.3 –
Setting general attributes of a MiCOM C264P ).
4.6.1 Connecting MiCOM C264P to others station-bus sub-systems
To transmit information between PACiS sub-systems, IEC-61850 protocol is used.
The data modelling of IEC-61850 protocol is based on client-server architecture. Each IEC-
61850 communicant PACiS sub-system (OI server, PACiS MiCOM C264P, and telecontrol
gateway) owns an IEC-61850 mapping of data which it is server of. A PACiS 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).
To connect a MiCOM C264P (A) to a specific IEC-61850 communicant sub-system (B) on
the station-bus, an extra relation ‘has for IEC61850/IEC server’ must be created for (A) and
point to (B). That means protection (A) is client of sub-system (B) and can access to data
managed by the sub-system (B), i.e. read relevant real-time values from (B) and send real-
time controls to (B).
FIGURE 37: CONNECTING MiCOM C264P TO OTHERS STATION-BUS SUB-SYSTEMS

When adding the ‘has for IEC server’ relation to MiCOM C264P (A), a specific attribute of the
relation, modelling/goose usage (1), can be set to precise the way data are transmitted from
server (B) to MiCOM C264P (A). There are three possibilities:
• Data model only (or report mode only).
• Goose only.
• Data model and goose.

Basically, the Report mode is used to transmit filtered data for displaying, printing and
archiving. The Goose mode is used to transmit data as soon as possible after their
acquisition and as quickly as possible, for automation purpose.
Goose transmission must be used if MiCOM C264P (A) uses BIs served by MiCOM C264P
(B), for ISaGRAF, FBD or interlock computation (refer to section Erreur ! Source du renvoi
introuvable. – Erreur ! Source du renvoi introuvable.).
During a loss of communication between a client and a server, all server BIs are set to
• A client must not be linked to the same server through multiple relations "has for
IEC61850/IEC server".
Report based mode

Via its IEC-61850 address, a BI (see section 5.1.1 – Overview of binary input processing)
can be configured to be transmitted in Report mode. In this mode, a confirmed change of
status is spontaneously transmitted to the subscribers.
The BI information transmitted in a report is:
• the state and quality (the BI resulting state is split in state and quality on IEC-61850)
− change of data (set if the state has changed, before persistence or motion filtering)
− change of quality (set if the quality has changed, before persistence or motion
filtering)
− change due to control (set if the state or quality change is due to a control)
From one server, all BI reports are not transmitted in a chronological order (it is an IEC-
61850 client feature to put, if needed, all information in a chronological order).
During a loss of communication, the events detected on the MiCOM C264P are not buffered.
GOOSE based mode
A BI (only SPS and DPS) can be configured to be transmitted in GOOSE mode. In this
mode, the change of status is transmitted in multicast to the configured receivers. Only the
BI unfiltered states are transmitted, the time stamping and the reason for change are not.
Due to GOOSE format, all BI resulting states given below cannot be transmitted. So, the
following mapping is applied:
BI Resulting State GOOSE value

RESET, FORCED RESET, SUBSTITUTED RESET, 01
CLOSE, FORCED CLOSE, SUBSTITUTED CLOSE
SET, FORCED SET, SUBSTITUTED SET, 10
OPEN, FORCED OPEN, SUBSTITUTED OPEN
MOTION00 00
MOTION11, TOGGLING, SELFCHECK FAULTY, 11
JAMMED, SUPPRESSED, UNKNOWN
A measurement can be configured to be transmitted in GOOSE mode as well (refer to

section 4.2.9 of chapter C264P/EN FT).
Be careful
If an IEC61850 client needs to use a measurement or counter, a non-goosed status or a
control managed by a server, setting the attribute (1) to ‘Data model only’ or ‘Data model and
goose’ is required.
MPS, measurement and counters are only transmitted by reports.
For details about goose configuration see chapter 4.6.2.4 – Configuring goose manually.
Computer A has
for IEC- 61850
server computer B
Computer B has
for IEC- 61850
client computer A
(1)
C0170ENb
FIGURE 38: MiCOM C264P (A) AS IEC61850 CLIENT OF MiCOM C264P (B)
4.6.2 Defining addressing mapping of station-bus network
An IEC 61850 mapping is an aggregation of logical devices, composed of bricks. Generally,
a brick corresponds to an electrical device or function. It provides its real-time data (status,
measurements, and controls…) and some configuration aspects. To do that, a brick groups
data by categories (Status, measurements, Control, Configuration), called functional
components.
A functional component groups data objects. A data object must be seen as a real-time
equivalent of a PACiS datapoint. So, when a PACiS sub-system (IEC 61850 client) needs
the real-time value of a datapoint managed by another sub-system (IEC 61850 server), this
last one transmits the information via a data object of its own IEC 61850 mapping. At SCE
data modelling level, IEC 61850 clients must precise which IEC 61850 servers it retrieves
information from (see section 4.6.1 – Connecting MiCOM C264P to others station-bus sub-
systems).
Generally, an IEC 61850 data object has a stereotype, called common class. The structures
of these ones are known by all PACiS IEC 61850 communicant sub-systems. For PACiS
sub-systems, the number and structure of common classes are fixed. They are the terminal
description of IEC 61850 PACiS data modelling.
In IEC 61850 mapping of PACiS sub-system, there is a native logical device LD0 with fixed
and hard-coded bricks (DBID, DI (LPHD), GLOBE (LLN0), and DIAG). When creating a
PACiS C264P at SCE level, an IEC 61850 mapping with LD0 and its default bricks is also
created. LD0 is a system logical device that groups all system diagnostics and controls
relevant to the MiCOM C264P. Datapoints addressed in the brick of LD0 are only relevant to
system topology.
Extra logical devices can be created in the IEC 61850 mapping of a MiCOM C264P.
Generally, there is one logical device for each bay managed by the MiCOM C264P, and, in
each logical device, there is one brick for each module or built-in function.
4.6.2.1 SBUS automatic addressing

“SBUS automatic addressing” function is based on the substation electrical topology and
especially on bays.
The easiest way to create application logical devices relevant to electrical bays managed by
a MiCOM C264P is to run “SBUS automatic addressing function” for the protection. The
contextual menu (mouse right click) of the protection (1) can launch this function.
(1)
FIGURE 39: SBUS AUTOMATIC ADDRESSING

NOTE: Only no-Spared datapoints are taken into account in automatic
addressing. If a datapoint is unspared then an automatic addressing
treatment must be done again.
• Some datapoints are out of scope of automatic addressing. Theses datapoints are
identified by their data model mnemonic and their short name. They are listed in the
following table:
Excluded datapoints
Parent object
mnemonic name
Module Circuit breaker SynCheck_Close_DPC Sync CB close
SynCheck_Close_SPC Sync CB close

Select_SPC Selection SPC
Switch_SPC_PhA Switch phA SPC
Switch_SPC_PhB Switch phB SPC
Switch_SPC_PhC Switch phC SPC
SwitchPos_PhA (DPS) Switch PhA pos.
SwitchPos_PhB (DPS) Switch PhB pos.
SwitchPos_PhC (DPS) Switch PhC pos.
SwitchPos_SPS_PhA Switch PhA pos. SPS
SwitchPos_SPS_PhB Switch PhB pos. SPS
SwitchPos_SPS_PhC Switch PhB pos. SPS
SwitchPos (DPS) Switchgear pos.
SwitchPos_SPS Switchgear pos.
PhaseNotTogether_SPS Ph not together
External automatic CS_CtrlOnOff_DPC on/off ctrl DPC
synchrocheck built-in function
CS_CtrlOnOff_SPC on/off ctrl SPC
Relay [XX] function XX_thresholdY_trip XX tY trip
examples:
With:XX = function number
46 t1 trip
Y = threshold number 67 t3 trip
XX_thresholdY_inst_dir_rev XX tY in di rev
examples:
With:XX = function number
67 t1 in dir rev
Y = threshold number 67 t3 in dir rev
XX_thresholdY_interlock XX tY interlock
With:XX = function number example:
67 t1 interlock
Y = threshold number
Relay [automatism] start_disturbance start dist ctrl
Relay [49] function 49_trip_th_overload 49 trip th over.
• Some measurements computed by a TMU 210 are out of scope of automatic

addressing if the measure type ( measure type attribute of the relation "is computed
by" linked to the related MV) is one of the followings:
− mod Vo (ADC)
− mod I1 (ADC)
− mod I2 (ADC)
− mod V1 (ADC)
− mod V2 (ADC)
− thermal status
NOTE: For the datapoints which are excluded of the automatic addressing it
is possible to add the relation "has for IEC address and then define it.
4.6.2.2 Updating LD0 of MiCOM C264P IEC61850 mapping
In LD0 of PACiS MiCOM C264P, the fixed part is composed of the following bricks:
• DBID (DataBase IDentity) used for MiCOM C264P databases identification and
management,
• DI (Device Identity) used for MiCOM C264P identification,
• GLOBE used for MiCOM C264P mode management,
• C26xDIAG brick.
FIGURE 40: STANDARD LD0 EXTENSION FOR C26X MiCOM C264P (SCE)
The LD0 can be completed with extra DIAG bricks, relative to some optional components of
the MiCOM C264P. For ease of use, such extra DIAG bricks are seen as elements of an
“extended IEC61850 mapping” object generally added automatically under the system
component associated to the extra DIAG.
Hereafter, are listed these extra DIAG bricks:
• For each IED connected to a PACiS MiCOM C264P via an IED legacy network, an
implicit IEDDIAG (diagnostic for the IED) brick exists, and an extra brick RDRE (for
disturbance information) can be added.
Be careful, when creating an IED on a MiCOM C264P legacy network, its IEDDIAG
brick name must be updated to avoid double values of bricks in the MiCOM C264P
LD0.
LD0 extension optional RDRE

for IED brick for IED
C0172ENa
FIGURE 41: LD0 EXTENSION FOR IED
• For each SCADA network connected to a PACiS MiCOM C264P, an implicit TCIDIAG
(diagnostic for the SCADA network) brick exists.
Be careful, when creating a SCADA network on a MiCOM C264P, its TCIDIAG brick
name must be updated to avoid double values of bricks in the MiCOM C264P LD0.
LD0 extension for

SCADA network
C0173ENa
FIGURE 42: LD0 EXTENSION FOR SCADA NETWORK
• An extra brick RDRE (for disturbance information) can be added in LD0 of the MiCOM
C264P if it manages its own disturbance file.
optional
standard LD0 RDRE brick
for computer for computer
C0174ENa
FIGURE 43: LD0 EXTENSION FOR C26X MiCOM C264P (SCE)

4.6.2.3 Creating application Logical device manually

Real-time data exchange between PACiS sub-systems is required for many purposes:
• At OI level:
− System and electrical process supervision and control (mimic animation,
controlpopup),
− Alarm management (generation, viewing, acknowledgement, clearing …),
− Logging (Sequence of event, log book),
− Event and value archiving (curve viewing, event analysis).
• At SMT level:
− System management (database loading and switching, device mode supervision
and control),
− Disturbance file storing.
• At PACiS MiCOM C264P level:
− Sharing datapoint for automation and built-in function,
− Feeding OI acquisition to insure its system functionality,
− Feeding PACiS Gateway acquisition to transmit data between PACiS system and
SCADA,
− Responding to system specific needs (command uniqueness).
• At PACiS gateway level:
− Transmit data between PACiS system and SCADA.
To insure real-time data exchange on station-bus, specific logical devices (called here
application logical devices) must be created in the IEC61850 mapping of the PACiS sub-
system that is server of the exchanged data (for definition of client/server, see chapter
4.6.1 – Connecting MiCOM C264P to others station-bus sub-systems). PACiS MiCOM
C264P is the only PACiS sub-system that allows user-defined application logical devices.
The general philosophy to create manually application logical devices is:
• one application logical device per bay managed by MiCOM C264P,

• in each application logical device, one brick per module or function contained in the
bay,
• for each brick, one data object per datapoint contained in the module/function, that
needs to be exchanged on the station-bus. In a brick, data object are grouped by
functional component. Datapoint addressing on station-bus network is done via linking
datapoint to the relevant IEC61850 data object. Available associations between type
of datapoint and type of IEC61850 data object are described in the following table.
Type of datapoint Type of IEC61850 data object

Relation: has for IEC61850 address (->)
SPS SI
DPS SIT
MPS SIG
MV AI, WYE phase or DELTA phase, ISI
Counter ACCI
SPC BO
DPC DCO
SetPoint AO
Manual creation of an application logical device

To create manually an application logical device:
• add ‘IECxLD’ from object entry available at IEC61850 mapping level,
• update its IEC name attribute (1), that must be unique for a given IEC61850 mapping.
FIGURE 44: ADDING AN APPLICATION LOGICAL DEVICE
(1)
FIGURE 45: UPDATING THE IEC61850 NAME OF AN APPLICATION LOGICAL DEVICE

Naming rule
‘IEC name’ is a free name up to 32 characters, made with the following characters: 0-9, a-z,
A-Z. It can not begin with a digit.
• For each Logical Device defined under the IEC61850/IEC mapping, its name must be
unique in the mapping.
• if the Logical Device is a generic one, its name must not contain the sub-string "LD0"
(reserved for system Logical Devices).
Manual creation of an IEC61850 Logical Node
To create manually an IEC61850 LN:
• add ‘GenLNxx’ from object entry available at IEC61850 logical device level; do not
use RDRE brick reserved for non-PACiS IEC61850 IED.
• update its IEC61850 name attribute (1), that must be unique for a given IEC61850
logical device.
FIGURE 46: ADDING AN IEC61850 LOGICAL NODE

(1)
FIGURE 47: UPDATING THE IEC61850 NAME OF A BRICK

Naming rule
‘IEC61850 name’ is a name made with 3 parts:
• optional wrapper (up to 6 characters), that can not begin with a digit.
• standard brick name (4 uppercase characters).
• optional index (1 character).

Each part is made with the following characters: 0-9, a-z, A-Z.
• For each Brick defined under a Logical Device, its name must be unique in the Logical
Device.
Manual creation of an IEC61850 functional component
To create manually an IEC61850 functional component, add specific functional component
from object entry available at MiCOM C264P IEC61850 brick level. For MiCOM C264Ps,
useful functional components are:
• ST to group statuses,
• CO to group controls,
• MX to group measurements,
• SV to group setpoints,
• CF to group configuration information relevant to CO or SP data objects.
FIGURE 48: ADDING AN IEC61850 FUNCTIONAL COMPONENT

Manual creation of an IEC61850 data object
To create manually an IEC61850 data object:
• add specific data object from object entry available at IEC61850 functional component
level. Each kind of functional components owns its own available list of data objects.
The following table shows the different lists useful for MiCOM C264P IEC61850
mapping:
Functional component Available data object

ST ACDxST
ACDxSTPhs
ACTxST
ACTxSTPhs
BCRxST
BCSxST
BCSxORxST
DPCxST
DPCxORxST
DPSxST
INC8xST
INCxST
INCxORIGxST
INS8xST
INSxST
SPCxORxST
SPCxST
SPSxST
MX APCxMX
APCxORxMX
CMVxMX
DELxMX
MVxMX
WYExMX
CO APCxDir
APCxSBOxS
BSCxDir
BSCxSBOxS
INCxDir
SPCDPCxDir
SPCDPCxSBO
SV BSCxSV
CMVxSV
DELxSV
SPCxSV
DPSxSV
INSxSV
MVxSV
SPCxSV
SPSxSV
WYExSV
CF APCxCF
BCRxCF
BSCxCF
DELxCF
DirectxCF
DPCxCF
MVxCF
SPCxCF
WYExCF
• update its IEC61850 name attribute (1), that must be unique for a given IEC61850
functional component.
FIGURE 49: ADDING AN IEC61850 DATA OBJECT
(1)
FIGURE 50: UPDATING THE IEC61850 NAME OF A DATA OBJECT

Naming rule
‘IECname’ is a free name up to 9 characters, made with the following characters: 0-9, a-z, A-
Z. It can not begin with a digit.
• For each Data Object defined under a Functional Component (CO), its name must be
unique in the Functional Component.
• For the following Functional Component types of a MiCOM C264P: CO, MX and ST,
the maximum count of Data Objects is 50.
4.6.2.4 Configuring goose manually

Goose is a mean given by IEC61850 protocol to send and take into account faster the binary
status changes of state. That is very useful for time-critical fast automation or interlocking. In
a given IEC61850 mapping, only its SI and SIT data objects are goose-able. Goose is
attached to and managed by the IEC61850 server of the goosed data objects.
Goose configuration is done at SI/SIT data object level via specific attributes:
Goose transmission:
1. Goose transmission (Auto) (Yes / No): Specifies if the Goose transmission (bit pair
rank) is automatic or not. In case of automatic affectation, the rank of bit-pair is fixed at
MiCOM C264P databag generation.
2. Goose transmission (Manu) (Yes / No): Specifies if the Goose transmission (bit pair
rank) is manual or not. In case of manual affectation, the rank of bit-pair must be filled
by user in the following attribute:
(1)
(2)
FIGURE 51: CONFIGURING GOOSE MANUALLY

• Among all the SI and SIT Data Objects having their attribute "goose transmission" set
to the "Manual DNA vector" value, the value of the attribute "rank in goose" must be
unique.
• Among all the SI and SIT Data Objects having their attribute "goose transmission" set
to the "Manual user status vector" value, the value of the attribute "rank in goose"
must be unique.
4.6.2.5 Creating application Logical Device automatically by using SBUS automatic addressing
IEC61850 automatic addressing function is based on the substation electrical topology and
especially on bays. For details about the way to configure this topology see chapter 6 –
Defining MICOM C264P configuration in electrical architecture).
The easiest way to create application logical devices relevant to electrical bays managed by
a MiCOM C264P, is to run IEC61850 automatic addressing function for the protection. The
contextual menu (mouse right click) of the MiCOM C264P IEC61850 mapping (1) can launch
this function.
IEC61850 automatic addressing for a given MiCOM C264P concerns only the bays and
ATCC function it manages, i.e. whose relation ‘is managed by’ has been filled to the MiCOM
C264P. So, for extra IEC61850 addressing concerning non-ATCC datapoints whose level is
higher than bay (substation, site or voltage level), manual creation of application logical
device must be done (see chapter 4.6.2.3 – Creating application Logical device manually).
IEC61850 automatic addressing procedure includes GOOSE addressing: GOOSE bit-pair

buffers status are sequentially filled with automatism datapoints exchanged between servers.
As for GOOSE manual addressing, result of GOOSE automatic addressing is set for a
datapoint as a “Manual attachment” or User status bit-pair, thus preserving this association
over any new automatic-addressing session. Size limit of buffers result in considering priority
levels for GOOSE addressing: existing “Manual attachments” (operator’s manual selections
and previous GOOSE addressing results) are considered first and left unchanged, than fast
automation datapoints are processed and finally slow automation datapoints. Case of
GOOSE buffer overflow is signalled and stop the process of GOOSE addressing.
For details about Goose modelling and configuration see chapter 4.6.2.4 – Configuring
goose manually).
(1)
FIGURE 52: IEC61850 AUTOMATIC ADDRESSING

4.6.3 Addressing datapoint on station-bus network

For details about datapoint, refer to chapter 5 – Defining datapoint.
To exchange datapoint values between station-bus sub-systems, datapoints should be
linked to specific IEC61850 data objects. There are 2 ways to resolve this link:
• Doing a manual addressing, by adding at datapoint level the relation ‘has for
IEC61850 address’ (1) and filling it with the corresponding IEC61850 data object in a
pre-configured IEC61850 addressing mapping (refer to chapter 4.6.2.3 – Creating
application Logical device manually for manual definition of an IEC61850 addressing
mapping).
(1)
FIGURE 53: REALISING IEC61850 MANUAL ADDRESSING OF DATAPOINT

(E.G. FOR BAY SPS DATAPOINT)
• Using automatic IEC61850 addressing, function available at SCE level (refer to

chapter 4.6.2.1 – SBUS automatic addressing), whose objectives are:
− automatic IEC61850 mapping creation at MiCOM C264P level,
− automatic linking between data objects in this IEC61850 mapping and datapoints
managed by the MiCOM C264P.
4.7 Networking IED on MiCOM C264P legacy network

4.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 PACiS system is commonly done via IED legacy networks managed
by PACiS protection as master.
At SCE data modelling level, up to four IED legacy networks (relevant to a specific protocol)
can be located under a PACiS C264P. Each IED legacy network has to be linked to
communication port embedded in MiCOM C264P boards. Up to sixteen IED can be added
under a legacy network.
4.7.1.1 Adding a legacy network

To create a legacy network on a MiCOM C264P:
• Add a legacy network relevant to a specific protocol from object entry available at
MiCOM C264P 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 (see section 4.4.4 – Configuring a communication channel).
(1)
FIGURE 54: ADDING A LEGACY NETWORK

4.7.1.2 Setting general attributes of a legacy network
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.
(1)
FIGURE 55: GENERAL ATTRIBUTES OF A LEGACY NETWORK

4.7.1.3 Setting acquisitions attributes of a T103 legacy network

When adding a T103 legacy network, the following attributes, available for all its IEDs, must
be updated:
1. number of retries (range [1, 10]): number of tries of the same frame without IED
response, the MiCOM C264P will send it before setting it disconnected.
2. acknowledgement time-out (range [100 ms, 30 s], step 100 ms): maximum delay an
IED answer is awaited when the MiCOM C264P asks it a information.
3. synchronisation cycle (range [10 s, 655350 s]): time synchronisation period of the
IED by the MiCOM C264P.
4. downgraded cycle (range [1 s, 10 s], step 100 ms): if an IED is set disconnected by
the MiCOM C264P, it tries to re-connect it regularly at this cycle.
5. 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.
(1)
(2)
(3)
(4)
(5)
FIGURE 56: SETTING ACQUISITION ATTRIBUTES OF A T103 LEGACY NETWORK

4.7.1.4 Setting acquisition attributes of a T101 legacy network
When adding a T101 legacy network, the following attributes, available for all its IEDs, must
be updated:
1. number of retries (range [1, 10], step 1): corresponds to the number of tries of the
same frame without IED response, the MiCOM C264P will send it before setting it
disconnected.
2. station address size (range [1 byte, 2 bytes]): size of the IED addresses
3. ASDU address size (range [1 byte, 2 bytes]): size of the ASDU.
4. info address size (range [1 byte, 3 bytes]): size of the information addresses.
5. transmission cause size (range [1 byte, 2 bytes]): size of the transmission cause.
6. 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.
7. acknowledgement time-out (range [100 ms, 30 s], step 100ms): maximum delay an
IED answer is awaited when the MiCOM C264P asks it an information.
8. synchronisation cycle (range [10 s, 655350 s], step 10 s): time synchronisation
period of the IED by the MiCOM C264P.
10. Type of link (Balanced / Unbalanced): if unbalanced link, only master (here
protection) asks IED. If balanced link, IED can also ask the master (here protection)
without sollicitation.
11. 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 MiCOM C264P
and IED. This attribute corresponds to maximum delay to receive this life message, to
protection’s point of view. If no reception within this delay, IED is set disconnected.
12. inter frame duration (range [1, 50 ], step 1): this attribute represents the minimum
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
FIGURE 57: SETTING ACQUISITION ATTRIBUTES OF A T101 LEGACY NETWORK

4.7.1.5 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:
disconnected.
IED answer is awaited when the MiCOM C264P asks it an information.
3. synchronisation (none / Schneider Electric / SEPAM / Flexgate): refer to section
4.3.5.2 of chapter C264P/EN CT for details and to the reference document of the
connected IED).
period of the IED by the computer. Only significant if attribute (3) is set to
‘Schneider Electric’, 'Flexgate' or to 'SEPAM'.
5. downgraded cycle (range [1s, 10 s], step 100 ms): if an IED is set disconnected by
6. inter frame duration (range [1, 50], step 1): this attribute represents the minimum
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 58: SETTING ‘ACQUISITION’ ATTRIBUTES OF A MODBUS LEGACY NETWORK

4.7.1.6 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:
1. master address: MiCOM C264P address on the DNP3 legacy network.
IED answer is awaited when the MiCOM C264P asks it a information.
disconnected.
4. application time-out (range [0 s, 255 s], step 1 s): time-out used by the MiCOM
C264P, at application layer of DNP3 protocol.
5. 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.
period of the IED by the MiCOM C264P.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 59: SETTING ACQUISITION ATTRIBUTES OF A DNP3 LEGACY NETWORK

4.7.1.7 Adding an IED to a legacy network

To create an IED on a legacy network:
• 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 Mobdus IED, update the ‘has for acquisition profile’ relation with a
previously created IED acquisition type.
(1)
FIGURE 60: ADDING AN IED TO A LEGACY NETWORK
updated relation
netween IED and
IED acquisition type
C0176ENb
FIGURE 61: LINKING IED ACQUISITION PROFILE TO AN IED

4.7.1.8 Setting attributes of a legacy IED
Whatever the kind of IED, the following attributes must be updated:
1. short name and long name: used for correct logging and alarm discrimination
concerning IED status datapoint.
2. network address of the IED on the legacy network (4 byte-address).
3. automatic disturbance (No / Yes): unavailable for DNP3 IED.
4. localisation for disturbance file: non-significant for DNP3 IED, used for basic file
name upload by SMT on OWS hard disk: <localisation>_N#.
(1)
(2)
(3)
(4)
FIGURE 62: SETTING GENERAL ATTRIBUTES OF A LEGACY IED

• For each IED, its "network address" and "short name" attributes value must be unique,
per Legacy Network.
4.7.1.9 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’, similar to acquisition profile. It is available
for DNP3, T103 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.
(1)
FIGURE 63: ADDING AN IED ACQUISITION TYPE TO A LEGACY NETWORK

(E.G. FOR DNP3)
• For each MiCOM C264P and all its Legacy Networks, the maximum count of "xxx acq
type" components is 10.
4.7.1.10 Setting attributes of a T103 acquisition type

When adding a T103 acquisition type, the following attributes, available for all its linked IEDs,
must be updated:
1. IED type (T103 standard IED / Px3x Serie / Px2x Serie / REG-D / Tapcon 240),
2. function type (range [0, 255]: function type number used for acquisition: see IED
documentation to set correctly this attribute,
3. 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,
4. MV reduction coefficient (1.2 / 2.4 ): used for scaling (ASDU 3 usage): refer to T103
documentation for details about this scaling,
5. 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.
(1)
(2)
(3)
(4)
(5)
FIGURE 64: SETTING ATTRIBUTES OF A T103 ACQUISITION TYPE

4.7.1.11 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:
2. IED type:
• Modicon to use the generic Modbus communication
• M300, Px2 series, MiCOM S40 (MiCOM Modbus communication)
• M230, Rish Pro M10, ABB Flexgate, SEPAM (Specific Modbus communication)
2. 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,
3. 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

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

5. 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.
(1)
(2)
(3)
(4)
(5)
FIGURE 65: SETTING ATTRIBUTES OF A MODBUS ACQUISITION TYPE

4.7.1.12 Setting attributes of a DNP3 acquisition type

When adding a DNP3 acquisition type, some attributes available for all its linked IEDs must
be updated:
1. global class usage (No / Yes): used for addressing. Not yet implemented. Always
considered as ‘yes’ at MiCOM C264P level.
2. synchronisation type (Network synchronisation / External synchronisation): in case
of network’ synchronisation, MiCOM C264P synchronises the time of the IED,
otherwise the synchronisation is assumed independently by an external equipment
directly connected to the IED. Not yet implemented. Always considered as ‘Network
synchronisation’ at protection level.
3. CROB parameters (Usage of 'code' field / Usage of 'Trip/Close' field / Usage of 'code'
and 'trip/close' fields):
(1)
(2)
FIGURE 66: SETTING ATTRIBUTES OF A DNP3 ACQUISITION TYPE

4.7.2 Defining addressing mapping of a legacy IED
To transmit information between IED and PACiS system, an IED legacy network connected
to a PACiS protection is used.
To receive or send information between legacy IED and PACiS system, each concerned
data must have a specific address on the legacy network relatively to its protocol. General
modelling 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 5 – Defining datapoint. This mapping is
implicitly created during IED adding at legacy network level. Addressing a MPS datapoint on
legacy IED is not available.
created DO
C0355ENa
FIGURE 67: STRUCTURE OF THE ADDRESSING MAPPING OF LEGACY IED

(E.G. FOR T101 IED)
For details about addressing mapping of a given IED on a specific protocol, refer to relay
documentation.
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:address identification is made of the following combinations of its attribute

values:
- { "information object address" , "common address of ASDU" }
- { "information object address" }
4.7.2.1 Defining an IED address for a SPS datapoint

The addition of an IED address for a SPS datapoint is done via the “Objects entry” window at
IED SPS mapping level by clicking on mouse’s right button.
FIGURE 68: ADDING AN IED SPS ADDRESS (E.G. FOR T101 IED)
Once added, IED SPS address attributes must be set at SCE level:
1. short name: used for internal SCE identification.
For Modbus protocol:
2. mapping address (range [0, 65535],step 1): word address or bit address depending
on the bit number attribute.
3. bit number (range [0, 65535],step 1): used only if word read or status read is used
(see function attribute).
4. fonction (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 T101 protocol:
5. information object address (range [0, 16777215],step 1).
6. common address of ASDU (range [-1, 65535],step 1): by default (–1) is equal to IED
address (see section 4.7.1.8 – Setting attributes of a legacy IED).
For T103 protocol:
7. ASDU number (range [0, 65535],step 1):
- 1, 2 (for all IED)
- 65,66,67,68 (Only for Px3x)
8. fonction type (range [0, 65535],step 1).
9. information number (range [0, 65535],step 1).
address (see section 4.7.1.8 – Setting attributes of a legacy IED.).
For DNP3 protocol:
11. address (range [0, 65535],step 1).
Modbus
(1)
(2)
(3)
(4)
T101
(5)
(6)
T103 (7)
(8)
(9)
(10
)
DNP3
(11
)
FIGURE 69: DEFINING AN IED ADDRESS FOR A SPS DATAPOINT

4.7.2.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 70: ADDING AN IED DPS ADDRESS (E.G. FOR T101 IED)
Once added, IED DPS address attributes must be set at SCE level:
1. short name of the address: used for internal SCE identification.
2. mapping address (range [0, 65535],step 1): Word address or Bit address depending
on bit number attribute.
3. bit number (range [0, 65535],step 1): Used only if Word read or status read is used
(see function attribute).
4. fonction (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 T101 protocol:
For T103 protocol:
- 1, 2 (for all IED)
- 65,66,67,68 (Only for Px3x)
8. fonction type (range [0, 65535],step 1): refer to relay documentation.
9. information number (range [0, 65535],step 1): refer to relay documentation.
For DNP3 protocol:
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’.
Modbus
(1)
(2)
(3)
(4)
(12
)
T101
(5)
(6)
(12
)
T103
(7)
(8)
(9)
(10
(12 )
)
DNP3
(11
)
(12
)
FIGURE 71: DEFINING AN IED ADDRESS FOR A DPS DATAPOINT

4.7.2.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:
2. mapping address (range [0, 65535],step 1): Word address
3. fonction (range [0, 65535],step 1): Modbus function to use to read the MV:
- 3, 4: read word,
- 7 : read status
4. data format: see following paragraph (Measurement formats that can be used with
the MODBUS protocol).
For T101 protocol:

address (see section 4.7.1.8 Setting attributes of a legacy IED).
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)
8. fonction type (range [0, 65535],step 1).
10. index in the ASDU (range [0, 65535],step 1).
address.
12. unit of the MEAS (Voltage / Current / Power / Frequency / No Unit).
13. 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: 10
− function type 254
− information number: 244
− index in the ASDU: Generic Identification Number given by the mapping of the IED
For DNP3 protocol:
Modbus
(1)
(2)
(3)
(4)
T101
(5)
(6)
T103
(7)
(8)
(9)
(10
(11 )
) (12
(13 )
)
DNP3
(14
)
FIGURE 72: DEFINING AN IED ADDRESS FOR AN MV DATAPOINT

Measurement formats that can be used with the MODBUS protocol

Because the Modbus standard only describes the transmission of 16-bit values (transmission
of the higher 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).
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 value.
UINT8_LB /
The significant byte is the low order byte of the word.
Transmission of an 8 bit unsigned integer in a 16 bit value.
UINT8_HB /
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 norm)
Transmission of a 16 bit unsigned integer. The high order
UINT16 2-1
byte is transmitted first (see Modbus norm)
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 word of the long value is transmitted first. The low order 3-4-1-2
UINT32_HW_HB word of the long value is transmitted first. The high order 4-3-2-1
Transmission of a 32 bit real value. The low order word is
REAL32_LW_LB 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 is
REAL32_LW_HB 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 is
REAL32_HW_LB 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 is
REAL32_HW_HB transmitted first. The high order byte of each word is 4-3-2-1
transmitted first.
Transmission
Format Description
order
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_MODULUS_ Bit 31to 16 reg Hight: RH= unsigned value/10000
4-3-2-1
10000_unsigned Bit 15…00 reg Low: RL = unsigned value modulus 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
4.7.2.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.
FIGURE 73: ADDING AN IED COUNTER ADDRESS (E.G. FOR T101 IED)
Once added, an IED Counter address attributes must be set at SCE level:
2. mapping address (range [0, 65535],step 1): word address.
3. fonction (range [0, 65535],step 1): Modbus function used to read the MV:
- 3, 4: read word.
4. data format: similar to MV.
For T101 protocol:
6. common address of ASDU (range [-1, 65535], step 1): by default (–1) is equal to IED
address.
For T103 protocol:
7. ASDU number (range [0, 65535],step 1).
8. function type (range [0, 65535],step 1).
10. index in the ASDU (range [0, 65535],step 1).
11. common address of ASDU (range [-1, 65535],step 1).
For DNP3 protocol:
Modbus
(1)
(2)
(3)
(4)
T101
(5)
(6)
T103
(7)
(8)
(9)
(10
)
(11
DNP3
)
(12
)
FIGURE 74: DEFINING AN IED ADDRESS FOR A COUNTER DATAPOINT

4.7.2.5 Defining an IED address for an SPC datapoint

The addition of an IED address for a SPC datapoint is done via the “Objects entry” window at
IED SPC mapping level by clicking on mouse’s right button.
FIGURE 75: ADDING AN IED SPC ADDRESS (E.G. FOR T101 IED)
Once added, IED SPC address attributes must be set at SCE level:
2. mapping address (range [0, 65535],step 1): Bit address for function 5 or 15, Word
address for function 6.
3. bit number (range [0, 65535],step 1): Used only if Function 6 is used (see function
attribute).
4. 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 T101 protocol:
address.
For T103 protocol:
- 20 (for all IED)
- 45,46 (Only for Px3x)
8. function type (range [0, 65535],step 1): refer to relay documentation.
For DNP3 protocol:
Modbus (1)
(2)
(3)
(4)
unused
T101
(5)
(6)
unused
T103 (7)
(8)
(9)
unused
DNP3
(10)
)
unused
C0178ENb
FIGURE 76: DEFINING AN IED ADDRESS FOR AN SPC DATAPOINT

4.7.2.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.
FIGURE 77: ADDING AN IED DPC ADDRESS (E.G. FOR T101 IED)
Once added, IED DPC address attributes must be set at SCE level:
2. mapping address (range [0, 65535],step 1): Bit address for function 5 or 15, Word
address for function 6.
3. bit number (range [0, 65535],step 1): used only if Function 6 is used (see function
attribute).
4. 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),
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 T101 protocol:
address.
For T103 protocol:
- 20 (for all IED)
- 45,46 (Only for Px3x)
For DNP3 protocol:
For all protocols:

11. 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’.
Modbus (1)
(2)
(3)
(4)
(unused)
(11
)
T101
(5)
(6)
(unused
(11 )
)
T103 (7)
(8)
(9)
(unused)
(11)
DNP3
(10)
(unused)
(11)
C0179ENb
FIGURE 78: DEFINING AN IED ADDRESS FOR A DPC DATAPOINT

4.7.2.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.
FIGURE 79: ADDING AN IED SETPOINT ADDRESS (E.G. FOR T101 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 UINT16.
2. mapping address (range [0, 65535],step 1): Word address for function 6.
3. function (range [0, 65535],step 1): Modbus function to use to send the SetPoint:
indicates the number of the bit in the word).
For T101 protocol:
5. output format (REAL32 (IEEE 754) / Normalized / Scaled).
For T103 protocol:
6. SetPoint address on T103 is only available for REGD relay, where output format is
configurable.
7. ASDU number (range [0, 65535],step 1): refer to relay documentation.
10. 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).
Modbus (1)
(2)
(3)
(unused)
(11)
(12)
T101 (4)
(unused)
(5)
(11)
(12)
(6)
T103
(7)
(8)
(unused)
(9)
(11)
(12)
DNP3 (10)
(unused)
(11)
(12)
C0180ENb
FIGURE 80: DEFINING AN IED ADDRESS FOR A SETPOINT DATAPOINT

4.7.3 Addressing a datapoint on an IED legacy network
Refer to chapters:
• 5.6.2 – Acquiring input datapoint via an IED legacy network
• 5.7.2 – Controlling output datapoint via an IED legacy network
Protocol
DP type Identifier DNP3 ModBus T103 T101
basic address Mapping
default address address ASDU number Not used
extra address #1 Not
default used Not used fonction type Not used
extra address #2 Not Information object
Counter
default used fonction information number address
extra address #3 Not common address
default used Not used index in the ASDU of ASDU
extra address #4 Not common address of
default used Not used ASDU Not used
Mapping
basic address address address ASDU number Not used
default used bit number fonction type Not used
xPC
extra address #3 Not common address
default used Not used Not used of ASDU
Mapping
default used bit number fonction type Not used
xPS
extra address #3 Not common address of common address
default used Not used ASDU of ASDU
Mapping
default used Not used fonction type Not used
MV extra address #2 Not Information object

default used Not used index in the ASDU Not used
Mapping
Set default used bit number fonction type Not used
point extra address #2 Not Information object
4.8 Networking SCADA on MiCOM C264P SCADA network

4.8.1 Creating a SCADA network
An electrical substation can be supervised and controlled from many points inside the
substation via PACiS operator interfaces (Substation Control Point or SCP) and/or PACiS
MiCOM 264P 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 PACiS system, via PACiS MiCOM
C264P or PACiS telecontrol gateway sub-systems. SCADA legacy networks are managed
as master by distant SCADA and can be redundant for safety reason. A PACiS MiCOM
C264P can manage up to two SCADA networks.
At SCE data modelling level, only SCADA legacy networks and their protocol are modelled
and connected to gateway sub-systems. Each SCADA network has to be linked to a main
communication port and eventually an auxiliary communication port in case of redundancy.
4.8.1.1 Adding a SCADA network
To create a SCADA network on a MiCOM C264P:
• Add a SCADA network from object entry available at protection level (1).
• Update the SCADA network attributes relevant to its protocol characteristics (see
section 4.8.2 – Defining addressing mapping of SCADA network).
• If SCADA does not use the substation network to communicate with the protection,
update its ‘has for main communication port’ relation and the communication port
characteristics (see chapter 4.4.4 – Configuring a communication channel).
• For DNP3 and T101 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 MiCOM C264P SCADA network and fill it with the relevant
serial port.
(1)
FIGURE 81: ADDING A SCADA NETWORK

(2)
FIGURE 82: CREATING A REDUNDANT SCADA LINK

4.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 MiCOM C264P for each connected SCADA network. Then the supported protocol (2)
must be selected (T101 in the example given hereafter). So the SCADA attributes tab-panes
(Protocol, SOE, Disturbance and Buffer overflow) are refreshed relatively to the selected
protocol.
(1)
(2)
(3)
(4)
FIGURE 83: SETTING GENERAL ATTRIBUTES OF A SCADA NETWORK

4.8.1.3 Setting general attributes of a T101 SCADA network
When adding a T101 SCADA network its general attributes must be updated (refer to the
previous figure)
3. redundancy type (Active line after GI received / Active line after Reset line received /
Active line on trafic).
4. time reference (UTC / local).
4.8.1.4 Setting specific attributes of a T101 SCADA network

When adding a T101 SCADA network, the following attributes available for this protocol must
be updated (Protocol and SOE tab-panes):
1. link address length (1 byte / 2 bytes)
2. link address (range [1, 65534], step 1)
3. ASDU common address length (1 byte / 2 bytes)
4. ASDU common address (range [1, 65534], step 1)
5. 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))
6. frame max length (range [1, 255], step 1)
7. cause of transmission length (Address on 8 bits / Address on 16 bits)
8. MV periodic cycle (range [0 s, 65534 s], step 1 s)
9. binary time size (CP24Time2A (3 bytes) / CP56Time2A (7 bytes))
10. background scan cycle (range [0 s, 65535 s], step 1 s)
11. type of link (unbalanced / balanced)
12. T3: test frame time-out (range [1 s, 255 s], step 1 s)
13. SBO time-out (range [0 s, 65535 s], step 1 s)
14. interframe duration (range [1, 50], step 1): this attribute represents the minimum
time, expressed in number of characters, that must exist between two frames
15. quality for 'Jammed' state (Valid / Invalid)
16. quality value for toggling xPS: ‘IV only’ for invalid only / ‘BL only’ for blocked only.
17. quality value for ‘unknown’ state (Not topical and IV (for invalid) / Not topical only)
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
FIGURE 84: SETTING PROTOCOL ATTRIBUTES OF A T101 SCADA NETWORK

18. SOE file support (Yes / No): Sequence Of Events support

19. SOE file address: this attribute is visible and significant only if attribute SOE file
support is set to Yes
20. SOE file format (T101 / S900) this attribute is visible and significant only if attribute
SOE file support is set to Yes
21. 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
22. '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)
(18)
(19)
(20)
(21)
(22)
FIGURE 85: SETTING SOE ATTRIBUTES OF A T101 SCADA NETWORK

The following constraints between the attributes must be respected:
"SOE file nb of events" > "'full' SOE file nb of events".
23. Disturbance file address for T103, S20, M300, SlowWave and FastWave (this
attribute panel is visible and significant only when supported protocol is T101 or T104)
(23)
FIGURE 86: SETTING DISTURBANCE ATTRIBUTES OF A T101 SCADA NETWORK

24. buffer overflow support (Yes / No),
25. buffer overflow address,
26. buffer overflow empty condition (Without emptying / “Fifo full / SCADA
(re)connection” / Fifo full only)
(24)
(25)
(26)
FIGURE 87: SETTING BUFFER OVERFLOW ATTRIBUTES OF A T101 SCADA NETWORK

4.8.1.5 Setting general attributes of a DNP3 SCADA network

In the following figure the selected protocol for the SCADA link is ‘DNP3’ (1).
(1)
4.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):
1. TCP/IP usage (No / Yes): set to ‘Yes’ substation network is used by the DNP3-IP
SCADA to communicate with the computer
2. Link address (1..65534)
3. SPS/DPS class (1 / 2 / 3)
4. MV class (1 / 2 / 3)
5. SPS/DPS class (1 / 2 / 3)
6. Counter class (1 / 2 / 3)
7. MV format (32 bits / 16 bits)
8. static MV (without flag / with flag)
9. event MV (without time, with time)
10. counter format (32 bits / 16 bits)
11. static counter (without flag / with flag)
12. event counter (without time, with time)
13. SBO time-out: maximum time between select orde and execute order
time, expressed in number of characters, that must exist between two frames
15. 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 initialiazed. Furthermore the SCADA
may disable or enable this unsolicited mode.
16. 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.
Setting SOE information SOE tab-panes, for DNP3-IP SCADA network is not significant (not
implemented).
FIGURE 89: DEFINING DNP-IP CONFIGURATION
4.8.1.6 Setting specific attributes of a T104 SCADA network

In the following figure the selected protocol for the SCADA link is ‘T104’ and the selected
time reference is UTC.
(1)

When setting a T104 SCADA network, some specific attributes available for the protocol
must be updated (Protocol and SOE tab-panes):
1. ASDU common address (range [1, 65534], step 1)
2. 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)):
3. frame max length (range [1, 255], step 1)
4. MV periodic cycle (range [0 s, 65534 s], step 1 s)
5. binary time size (CP24Time2A (3 bytes) / CP56Time2A (7 bytes))
6. background scan cycle (range [0 s, 65535 s], step 1 s)
7. T1: APDU time-out (range [1 s, 255 s], step 1 s)
8. T2: acknowledgement time-out (range [1 s, 255 s], step 1 s)
9. T3: test frame time-out (range [1 s, 255 s], step 1 s)
10. K: sent unack. frames (APDU) (range [1, 255], step 1)
11. W: ack. received frames (APDU) (range [1, 255], step 1)
12. max command delay (range [0 s, 32767 s], step 1 s)
13. socket IP #i (i ∈ [1, 4])

14. SBO time-out (range [0 s, 65535 s], step 1 s)

15. quality for 'Jammed' state (Valid / Invalid)
16. quality value for toggling xPS: ‘IV only’ (for invalid only) / ‘BL only’ (for blocked only)
17. quality value for ‘unknown’ state (Not topical and IV (invalid) / Not topical only)
18. Switchover (Automatic switchover / manual switchover)
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
FIGURE 91: SETTING PROTOCOL ATTRIBUTES OF A T104 SCADA NETWORK

19. SOE file support (No / Yes)

20. SOE file address (this attribute is visible and significant only if attribute SOE file
support is set to Yes)
21. SOE file format (T101 / S900) (this attribute is visible and significant only if attribute
SOE file support is set to Yes)
22. 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)
23. '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)
(19)
(20)
(21)
(22)
(23)
FIGURE 92: SETTING SOE ATTRIBUTES OF A T104 SCADA NETWORK

24. Disturbance file address for T103, S20, M300, SlowWave and FastWave (this
attribute panel is visible and significant only when supported protocol is T101 or T104
(24)
FIGURE 93: SETTING DISTURBANCE ATTRIBUTES OF A T104 SCADA NETWORK

24. buffer overflow support (Yes / No),
25. buffer overflow address,
26. buffer overflow empty condition (Without emptying / “Fifo full / SCADA
(re)connection” / Fifo full only)
(24)
(25)
(26)
FIGURE 94: SETTING BUFFER OVERFLOW ATTRIBUTES OF A T104 SCADA 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"
4.8.1.7 Setting specific attributes of a MODBUS SCADA network

In the following figure the selected protocol for the SCADA link is ‘Modbus’.
(1)
FIGURE 95: 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):
1. link address
2. inter frame duration (range [1 , 50 ], step 1): this attribute represents the minimum
For a MODBUS SCADA network, the SOE tab-panes attributes are not significant (not
implemented).
FIGURE 96: SETTING PROTOCOL ATTRIBUTES OF A MODBUS SCADA NETWORK

4.8.2 Defining addressing mapping of SCADA network

To transmit information between PACiS system and SCADA, a SCADA legacy network is
used.
To receive or send information between legacy IED and PACiS system, each concerned
data must have a specific address on the legacy network relatively to its protocol. General
modelling 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 basis. In each category of mapping, elementary SCADA addresses can
be created. For details about datapoint, refer to section 5 – Defining datapoint. This mapping
is implicitly created during IED adding at legacy network level.
WARNING: ADDRESSING A MPS DATAPOINT ON A SCADA NETWORK IS NOT
AVAILABLE.
Entry point
of SCADA
mapping
Categories
per datapoint
kind basis
C0181ENb
FIGURE 97: 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 T101 and T104 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.
4.8.2.1 Defining a SCADA address for a SPS datapoint
The addition of a SCADA address for a SPS datapoint is done via the “Objects entry”
window at SCADA SPS mapping level by clicking on mouse’s right button.
FIGURE 98: ADDING A SCADA SPS ADDRESS

Once added, SCADA SPS address attributes must be set at SCE level:
1. shortname of the address used for internal SCE identification.
2. object address - register
For T101/T104 protocol:
3. object address.
4. 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.
5. 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 MiCOM C264P 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 protection. The set of available values is maintained for
compatibility with MiCOM C264P MiCOM gateway addressing in MiCOM gateway.
6. Inversion (No / Yes): Indicates that the datapoint value needs to be inverted before
transmission.
7. Background scan (No / Yes): indicates if the datapoint belongs to the background
scan cycle.
8. Group ([0..16)] / 0=no group): indicates to which “T101/T104 General Interrogation
group” the datapoint is assigned. 0 means ‘no group’ assignation.
For DNP3 protocol:

9. object address - index.
10. 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.
11. Inversion (No / Yes): indicates that the datapoint value needs to be inverted before
transmission.
Modbus
(1)
(2)
T101/T104
(3)
(4)
(5)
(6)
(7)
(8)
DNP3
(9)
(10)
(11)
FIGURE 99: DEFINING A SCADA ADDRESS FOR A SPS DATAPOINT

4.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.
FIGURE 100: ADDING A SCADA DPS ADDRESS

Once added, SCADA DPS address attributes must be set at SCE level:
1. short name: used for internal SCE identification
2. 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.
3. object address - register: used if ‘Double address usage’ is set to ‘No’.
4. 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.
5. 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.
6. 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.
7. 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 MiCOM C264P 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 MiCOM C264P. The set of available values is maintained for
compatibility with MiCOM gateway addressing in MiCOM gateway.
transmission.
9. Background scan: (No / Yes): indicates if the datapoint belongs to the background
scan cycle.
10. Group ([0..16)] / 0=no group): indicates to which “T101/T104 General Interrogation
group” the datapoint is assigned. 0 means ‘no group’ assignation
11. object address (index)
For DNP3 protocol:

state of the datapoint are transmitted spontaneously with time Tag
transmission
14. object address - index
Modbus
(1)
(2)
(3)
(4)
(5)
T101/T104
(6)
(7)
(8)
(9)
(10
)
(11)
DNP3
(12)
(13)
(14)
FIGURE 101: DEFINING A SCADA ADDRESS FOR A DPS DATAPOINT

4.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 102: ADDING A SCADA MV ADDRESS

Once added, SCADA MV address attributes must be set at SCE level:
1. short name of the address used for internal SCE identification.
2. object address – register (Yes / No): 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.
3. Format (Natural / Unsigned normalized / Signed normalized /Real IEEE754 – little
endian / Real IEEE754 – big endian): transmission format.
4. Precision (8..16): number of transmitted bits.
5. object address.
indicates that change of state of the datapoint are transmitted spontaneously with time Tag.
7. Event record ( No / Yes): indicates if change of state of the datapoint must be saved
in Sequence of Event file or not. 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 MiCOM C264P 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 MiCOM C264P. The set of available values is maintained for
compatibility with MiCOM gateway addressing in MiCOM gateway.
8. Format (Normalized / Adjusted / Float):transmission format.
9. cycle type (None / Periodic / Background scan): indicates which transmission cycle
the MEAS belongs to.
10. 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:

11. object address
13. Format (Natural / Adjusted).
Modbus
(1)
(2)
(3)
(4)
T101/T104
(5)
(6)
(7)
(8)
(9)
(10)
DNP3
(11)
(12)
(13)
FIGURE 103: DEFINING A SCADA ADDRESS FOR A MV DATAPOINT

4.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.
FIGURE 104: ADDING A SCADA COUNTER ADDRESS

Once added, SCADA Counter address attributes must be set at SCE level:
2. object address – register.
3. Format (Natural / Unsigned normalized / Real IEEE754 – little endian / Real IEEE754
– big endian): transmission format.
4. object address.
indicates if changes of state of the datapoint are transmitted spontaneously with time
Tag.
6. 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:
7. object address.
Modbus
(1)
(2)
(3)
T101/T104
(4)
(5)
(6)
DNP3
(7)
(8)
FIGURE 105: DEFINING A SCADA ADDRESS FOR A COUNTER DATAPOINT

4.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.
FIGURE 106: ADDING A SCADA SPC ADDRESS

Once added, SCADA SPC address attributes must be set at SCE level:

2. object address - register.
3. object address.
4. 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:
5. object address.
6. 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.
Modbus
(1)
(2)
T101/T104
(3)
(4)
DNP3
(5)
(6)
FIGURE 107: DEFINING A SCADA ADDRESS FOR AN SPC DATAPOINT

4.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.
FIGURE 108: ADDING A SCADA DPC ADDRESS

Once added, SCADA DPC address attributes must be set at SCE level:
3. object address.
4. 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:
5. object address in [0..65535].
datapoint.
Modbus
(1)
(2)
T101/T104
(3)
(4)
DNP3
(5)
(6)
FIGURE 109: DEFINING A SCADA ADDRESS FOR A DPC DATAPOINT

4.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.
FIGURE 110: ADDING A SCADA SETPOINT ADDRESS

Once added, SCADA SetPoint address attributes must be set at SCE level:

3. format.(signed 16 bits / Real IEEE754 – little endian: the lower byte is transmitted first
/ Real IEEE754 – big endian: the higher byte is transmitted first)
4. object address.
5. SCADA execute order type (Select execute / Direct execute): this attibute defines if
SCADA uses a ‘Select execute” or a ‘Direct execute’ sequence to send control on the
datapoint.
6. Minimal value: available minimal value on the protocol (used for scaling and checks).
7. Maximal value: available maximal value on the protocol (used for scaling and
checks).
8. Format (Normalized / Adjusted / Float).
For DNP3 protocol:
9. object address [0..65535].
datapoint.
11. minimal value: available minimal value on the protocol (used for scaling and checks).
12. maximal value: available maximal value on the protocol (used for scaling and
checks).
13. format (Natural / Adjusted).
Modbus
(1)
(2)
(3)
T101/T104
(4)
(5)
(6)
(7)
(8)
DNP3
(9)
(10)
(11)
(12)
(13)
FIGURE 111: DEFINING A SCADA ADDRESS FOR A SETPOINT DATAPOINT

4.8.2.8 Defining a SCADA address for bypass synchrocheck

For details about synchronised circuit-breakers, refer to section 6.2 – Defining a
Synchrocheck function.
Synchronised circuit-breaker can be controlled through SCADA network. In that case, the
SPC (resp. DPC) control of the synchronised 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
synchronised 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 synchronised breaker.
• 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).
address (A)
address (B)
C0347ENa
FIGURE 112: ADDING A BYPASS SYNCHROCHECK ADDRESS TO A SCADA SPC/DPC ADDRESS

(E.G. FOR SCADA DPC ADDRESS)
4.8.3 Addressing datapoint on SCADA legacy network

For details about datapoint, refer to section 5 – Defining datapoint.
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 section 4.8.2 – Defining addressing
mapping of SCADA network, for SCADA mapping definition).
Addressing a MPS datapoint on the SCADA legacy network is not available.
(1)
FIGURE 113: REALISING SCADA ADDRESSING OF A DATAPOINT

(E.G. FOR BAY SPS DATAPOINT)
4.9 Defining wave record file management (Disturbance File)

The MiCOM C264Ps manage two kinds of wave recording file:
• IED connected to MiCOM C264P legacy network can produce disturbance files. In that
case, MiCOM C264P monitors their availability. As soon as available, they are
uploaded and stored at protection level. MiCOM C264P computes for System
management Tool (SMT) a real-time data per IED basis that gives the availability of a
disturbance file, via station-bus network. Then, SMT downloads it from MiCOM
C264P. At the end of successful downloading, MiCOM C264P erases the real-time
data of availability.
• Via a CT/VT board (TMU210), MiCOM C264P can manage its own waveform record
files (fast waveforms are also nammed disturbance 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 MiCOM C264P computes for SMT a real-time data that gives
the availability of a MiCOM C264P waveform record file, via station-bus network. Then
processing is similar to IED’s one.
4.9.1 Defining management of disturbance file for IED
Allowing MiCOM C264P to manage IED disturbance is done at IED configuration level by:
• Setting its ‘automatic disturbance’ attribute to yes (see chapter 4.7.1.8 – Setting
attributes of a legacy IED.
• Adding RDRE brick (1) for the IED in LD0 logical device of the IEC-61850 mapping of
the MiCOM C264P (see chapter 4.6.2.2 – Updating LD0 of MiCOM C264P IEC61850).
• Adding the system SPS datapoint ‘DREC ready’ (2) at IED level, linked to a pre-
defined datapoint profile.
• Fill the mandatory IEC address for this datapoint, with the relevant data object of the
RDRE brick (3).
(2)
(1)
FIGURE 114: ADDING RDRE BRICK AND DREC READY DATAPOINT FOR IED
(3)
FIGURE 115: SETTING IEC-61850 ADDRESS OF DREC READY DATAPOINT FOR IED
For T103 IED extra information must be configured to process correct disturbance file
COMTRADE structure at MiCOM C264P level (see following section).
4.9.2 Defining T103 IED extra information for disturbance file

T103 extra informations for disturbance file are located at T103 acquisition type (see details
in chapter 4.7.1.10 – Setting attributes of a T103 acquisition type) and concern definition of
analog and digital channels, stored in disturbance file, relatively to COMTRADE format.
4.9.2.1 Adding an analog channel definition
The addition of an analog channel definition for T103 is done via the “Objects entry” window
at T103 acquisition type level by clicking on mouse’s right button. Up to 15 analog channels
can be created under a T103 acquisition type.
FIGURE 116: ADDING A T103 ANALOG CHANNEL DEFINITION

Once added, channel definition attributes must be set at SCE level:
1. channel label.
2. long name of the channel used for internal SCE identification.
3. phase name: label of the phase corresponding to the channel.
4. channel number: (cf. mapping IED– field ACC in IEC 60870-5-103 documentation).
5. unit: unit corresponding to the channel.
6. 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.
7. shift time (range [0 s, 1 s], step 1 μs): elapsed time since the beginning of the
sampling period.
8. maximal sample value (range [0 , 32767], step 1).
9. minimal sample value (range [-32768, 0], step 1)..
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
FIGURE 117: SETTING T103 ANALOG CHANNEL DEFINITION

For more details about the analog channel definition, refer to COMTRADE (IEEE C37.11)
external documentation.
4.9.2.2 Adding a digital channel definition

The addition of a digital channel definition for T103 is done via the “Objects entry” window at
T103 acquisition type level by clicking on mouse’s right button. Up to 255 digital channels
can be created under a T103 acquisition type.
FIGURE 118: ADDING A T103 DIGITAL CHANNEL DEFINITION

Once added, channel definition attributes must be set at SCE level:
1. channel label.
2. long name of the channel used for internal SCE identification.
3. function number (range [0 , 255], step 1): corresponds to function type of the channel
in T103 protocol.
4. information number (range [0 , 255], step 1): corresponds to information number of
the channel in T103 protocol.
5. default state (Off / On).
(1)
(2)
(3)
(4)
(5)
FIGURE 119: SETTING T103 DIGITAL CHANNEL DEFINITION

For more details about the digital channel definition, refer to COMTRADE (IEEE C37.11)
external documentation.
4.9.3 Defining management of wave record file for MiCOM C264P CT/VT board
NOTE: For MiCOM C264P, the Disturbance Files are called “Fast wave
forms” in the following paragraphs.
Allowing MiCOM C264P to manage its own wave record file is done at protection
configuration level by:
• 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 RDRE brick (1) for the protection in LD0 logical device of the IEC-61850
mapping of the MiCOM C264P (see chapter 4.6.2.2 – Updating LD0 of MiCOM C264P
IEC61850).
• Adding the system SPS datapoint ‘C26x DREC ready’ (2) at MiCOM C264P level,
linked to a pre-defined datapoint profile.
• Fill the mandatory address for this datapoint, with the relevant data object of the
RDRE brick (3).
(2)
(1)
FIGURE 120: ADDING A RDRE IEC-61850 BRICK AND A DREC READY DATAPOINT
FOR A MiCOM C264P
(3)
FIGURE 121: SETTING IEC 61850 ADDRESS OF DREC READY DATAPOINT FOR MiCOM C264P
4.9.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 5 – Defining datapoint). 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 SMT.
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 Files Number of 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 MiCOM
C264P level by clicking on mouse’s right button. Only one fast waveform recording can be
created under a MiCOM C264P.
FIGURE 122: ADDING A FAST WAVEFORM RECORDING

Once added, fast waveform recording attributes must be set at SCE level:
1. short name and long name: used for internal SCE identification.
2. pre-trigger cycle (range [0 , 480], step 1): corresponds to number of cycles (up to
480), that are stored before triggering.
3. total cycles (range [0 , 480], step 1): see previous description.
4. number of files (1 / 2 / 3 / 4 / 5): see previous description.
(1)
(2)
(3)
(4)
FIGURE 123: 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 MiCOM C264P can be defined as input
of its fast waveform recording.
(1)
FIGURE 124: 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
MiCOM C264P can be defined as input of its fast waveform recording.
(2)
FIGURE 125: DEFINING TRIGGERS OF FAST WAVEFORM RECORDING

Depending on the datapoint type, extra attributes must be set for ‘has for trigger’ relation.
These attributes gives the datapoint states (or thresholds for MV) that trig the record (see
following figure).
Triggering state for DPC:

Open, Close or “Open and Close”
Triggering state for DPS:

Open, Closed or “Open and Closed”
Triggering state for MV,

for each state:
- No trigger,
- Trigger on threshold shot,
- Trigger on threshold reset,
- Trigger on threshold shot and reset
Triggering state for SPC:

Reset Set or “Set and Reset”
Triggering state for SPS:

Off, On or “On and Off”
C0183ENc
FIGURE 126: DEFINING TRIGGER CONDITIONS OF FAST WAVEFORM RECORDING


- "pre-trigger cycle" ≤ "total cycles"
- "number of files" ∗ "total cycles" ≤ 480 cycles
4.9.3.2 Defining slow waveform recording

The inputs for the slow waveform records are:
• MV datapoint coming from CT VT computation (refer to chapter 5.6.4.4 – Explicit

electrical input datapoint via CT/VT computation).
• MV datapoint coming from AIU boards.
• 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 C264P stores at maximum 5000 integrated values as follow:
Number of Files Number of integrated 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 MiCOM
C264P level by clicking on mouse’s right button. Only one slow waveform recording can be
created under a MiCOM C264P.
FIGURE 127: ADDING A SLOW WAVEFORM RECORDING

Once added, slow waveform recording attributes must be set at SCE level:
1. short name and long name of the recording used for internal SCE identification.
2. pre-trigger cycle (range [0 , 5000], step 1): corresponds to the number of cycles (up
to 480) that are stored before triggering.
3. total records (range [0 , 5000], step 1): see previous description.
4. number of files (1 / 2 / 5 / 10 / 20 / 50): see previous description.
5. 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.
6. 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 4.3.2 – Configuring measurement
acquisition and transmission)
7. activation period (Non periodic trigger / Daily trigger / weekly trigger / Daily and
weekly trigger): see previous description.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 128: SETTING FAST WAVEFORM RECORDING

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 MiCOM C264P can be defined as input of its slow waveform recording.
(1)
FIGURE 129: 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 MiCOM C264P 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.
(2)
FIGURE 130: DEFINING TRIGGERS 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).
Triggering state for DPC:

Open, Close or “Open and Close”
Triggering state for DPS:

Open, Closed or “Open and Closed”
Triggering state for MV,

for each state:
- No trigger,
- Trigger on threshold shot,
- Trigger on threshold reset,
- Trigger on threshold shot and reset
Triggering state for SPC:

Reset Set or “Set and Reset”
Triggering state for SPS:

Off, On or “On and Off”
C0184ENc
FIGURE 131: DEFINING TRIGGERS 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.
4.10 Defining a MiCOM C264P klaxon

A MiCOM C264P can manage up to one external klaxon, that is started as soon as an
audible local alarm is raised on protection (to define audible alarm refer to section 5 –
Defining datapoint). The external klaxon is managed by a specific SPC datapoint wired on
the MiCOM C264P (‘ON’ order starts the klaxon, ‘OFF’ order stops it).
To define an external klaxon at MiCOM C264P level, just add the relation ‘has its klaxon
managed by’ at protection level and fill it with the relevant SPC.
FIGURE 132: DEFINING MiCOM C264P KLAXON

• The "SPC" link of the relation "has its klaxon controlled by" must be wired on a DO
channel of the protection.
4.11 Setting system information for components

When creating a MiCOM C264P, specific datapoints are automatically added in ‘system
infos’ binder (1) at global 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 MiCOM C264P. In that case, the ‘system infos’ binder is
located under the relevant added object.
For extra MiCOM C264P 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 section 5 – Defining datapoint). Depending on its kind,
the system datapoint and its relevant profile have specific attributes to be set correctly to
insure healthy behaviour of MiCOM C264P. Hereafter, are listed the datapoint and profile
requirements for each kind of system datapoint.
Generally system datapoints are automatically addressed in IEC-61850 mapping of the
relevant MiCOM C264P at their creation. If manual addressing is necessary, it is stressed in
following sections by given the associated available data object of a given protection brick in
LD0 (⇔<brick name>.<data object name>). For details about SBUS addressing see section
4.6 – Networking MiCOM C264P on the station-bus network.
(2)
(4)
(3)
(5)
(1)
FIGURE 133: ‘SYSTEM INFOS’ BINDERS FOR A MiCOM C264P

4.11.1 Setting general system information of a MiCOM C264P

When creating a MiCOM C264P, the following mandatory datapoints are implicitly added.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
(20)
(21)
(22)
(23)
(24)
(25)
FIGURE 134: MANDATORY ‘SYSTEM INFOS’ DATAPOINTS FOR A MiCOM C264P

These datapoints must be configured (see section 5 – Defining datapoint) according to their
described features:
• Controls and statuses for functioning mode
− Mode control DPC (10): this datapoint is only used by the SMT to turn device
functioning mode to maintenance or Operational/Run.
The available states of this datapoint are:
“OPEN” for the maintenance mode
“CLOSED” for Operational mode
An IEC address for this datapoint is defined by using SBUS automatic addressing.
− Operating mode MPS (11): this datapoint is the MPS equivalence of Device mode
DPS (4).
“STATE 0” for the Faulty mode
“STATE 1” for Operational mode
“STATE 3” for Test mode
“STATE 5” for maintenance mode
− Test control DPC (23): this datapoint is only used by the SMT to turn device
functioning mode to Test or Normal.
“OPEN” for the Test mode
“CLOSED” for Normal mode
This datapoint has no IEC-61850 address
• Control and status for local/remote
− Local/remote ctrl DPC (6): this datapoint is required by IEC-61850 protocol but is
meaningless for the protection.
“OPEN” for Remote
“CLOSED” for Local
This datapoint has no IEC address
− Local/remote DPS (7):
“OPEN” for Remote
“CLOSED” for Local
− Local/remote SPS (8):
“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 MiCOM C264P have the "OPEN" state and has the "SET"
state if at least the Local/remore DPS datapoint of one bay managed by the
protection has not the "OPEN" state.
The IEC-61850 address of this datapoint is defined by using SBUS automatic
addressing.
• Control and status for database management
− Database incoherency SPS (2): this datapoint is put in ‘SET’ state if current
database is not self-consistent. In that case, MiCOM C264P enters the
maintenance mode.
“RESET” for coherent database
“SET” for incoherent database
− Database switch control SPC (3): this datapoint is only used by the SMT to turn
device functioning mode to maintenance or Operational/Run.
The available state of this datapoint is:
“ON” for Switch
• Synchronisation status
− Synchronisation SPS (22): this is put in ‘SET’ state if device is synchronised.

“RESET” for not synchronised device
“SET” for synchronised device
An IEC-61850 address for this datapoint is defined by using SBUS automatic
addressing.
• Communication status
− Device link SPS (4): although this datapoint is under the MiCOM C264P, it is not
managed by it. Each IEC-61850 client of the protection computes locally this
datapoint status by supervising the IEC-61850 real-time link with the protection. In
fact, there are as many ‘Device link SPS’ per MiCOM C264P basis as IEC-61850
clients connected to the protection. Is put in ‘SET’ state if device link is operational.
“RESET” for not OK
“SET” for OK
This datapoint has no IEC address
• Health statuses
− DI acquisition stopped SPS (5): 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
addressing.
− Software error SPS (21): in case of software error, this datapoint is set and
MiCOM C264P enters the Faulty mode.
“RESET” for software running
“SET” for software error
− Watchdog SPS (24): in case of software watchdog time-out, this datapoint is put in
‘SET’ state and MiCOM C264P enters the Faulty mode.
“RESET” for watchdog OK
“SET” for watchdog time-out
− ISaGRAF status MPS (25):

“STATE 0”: Isagraf is running normally
“STATE 1”: Not activated
“STATE 2”: Cycle too long
“STATE 3”: Queue overflow (Isagraf queue has reached overflow limit)
“STATE 4”: An Isafraf POU (Program Organisation Unit) is faulty
addressing.
• Control and statuses for redundancy management:
The four following datapoints are used internally by MiCOM C264P if it is redunded.
These datapoints must be linked to datapoint profiles by default for proper behaviour
of redundancy.
− Redundancy change mode (16),
− Redundancy change mode SPS (14)
− Redundancy change status SPS (15)
− Redundancy change mode control SPC (11)
− Redundancy change status control SPC (12)
These datapoints have no IEC-61850 address.
− Main status MV (9)

addressing.
At MiCOM C264P level, the following optional datapoint can be added.
(21)
(22)
(23)
(24)
FIGURE 135: OPTIONAL ‘SYSTEM INFOS’ DATAPOINTS FOR A MiCOM C264P

described features:
− Counter Top SPS (21): 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
An IEC-61850 address can be manually added to this datapoint.
− DREC ready SPS (22): this datapoint indicates the availability of a waveform
record file for the MiCOM C264P (for details, refer to section 4.9 – Defining wave
record file).
“RESET” for no waveform record available
“SET” for waveform record file available
addressing.
− External clock status SPS (23): this datapoint indicates the status of the IRIG-B
synchronisation. This datapoint is mandatory if ‘synchronisation source’ attribute at
MiCOM C264P level is set to IRIG-B (for details, refer to section 4.3 – Setting
general attributes of a MiCOM C264P ). The available states of this datapoint are:
“SET” for lack of IRIG-B signal
“RESET” for IRIG-B signal is present
An IEC-61850 address can be manually added to this datapoint.
− Device mode DPS (24): this datapoint gives the current functioning mode of the
MiCOM C264P.
“JAMMED” for the Test mode
"OPEN" for the maintenance mode
"CLOSED" for the Operational mode
“UNDEFINED” for the Operational mode
This datapoint has no IEC-61850 address.
4.11.2 Setting system information of board

When creating a board (except CPU board) the following mandatory datapoint is implicitly
added.
(1)
FIGURE 136: MANDATORY ‘SYSTEM INFOS’ DATAPOINT FOR A BOARD

(E.G. FOR AIU BOARD)
− Board status MPS (1): this datapoint indicates the status of the board. Addressing
this datapoint can be done:
1) by using SBUS automatic addressing.
FIGURE 137: AUTOMATIC IEC ADDRESSING OF A BOARD STATUS DATAPOINT

2) Manually. In that case, the relevant data object given the IEC address of the
status, must be coherent with the board number (e.g. if AIU board number is 3,
corresponding data object is AIUSt3).
“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
FIGURE 138: MANUAL IEC ADDRESSING OF A BOARD STATUS DATAPOINT

4.11.3 Setting system information of legacy IED

When creating a legacy IED, the following mandatory datapoints are implicitly added.
(1)
(2)
FIGURE 139: MANDATORY ‘SYSTEM INFOS’ DATAPOINTS FOR A LEGACY IED

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 synchronisation status SPS (2): is put in ‘SET’ state if IED is synchronised.
“RESET” for IED not synchronised
“SET” for IED synchronised
At IED level, the following optional datapoint can be added.
(3)
FIGURE 140: OPTIONAL ‘SYSTEM INFOS’ DATAPOINT FOR A LEGACY IED
− IED disturbance status SPS (3): this datapoint indicates the availability of a
disturbance file for the IED (for details, refer to section 4.9.1 – Defining management
of disturbance file for IED). This datapoint is put in ‘SET’ state if a disturbance file is
available.
“RESET” for no disturbance file available
“SET” for disturbance file available
4.11.4 Setting system information of serial printer

When creating a serial printer, the following mandatory datapoint is implicitly added.
(1)
FIGURE 141: MANDATORY ‘SYSTEM INFOS’ DATAPOINT FOR A SERIAL PRINTER
• Printer status MPS (1): this datapoint indicates the status of the printer.
Addressing this datapoint on IEC61850 can be done:
− By using ‘IEC61850 automatic addressing function’.
− Manually. In that case, the relevant data object given the IEC61850 address of the
status, must be ‘PrintSt’ in the MiCOM C264P C26xDIAG brick.
− The available states of this datapoint are:

“STATE 0” for printer OK
“STATE 1” for self-check failure
“STATE 2” for configured but missing,
“STATE 3” for not configured but present
“STATE 4” for printer not present
4.11.5 Setting system information of a SCADA network

When creating a SCADA network, the following mandatory datapoints are implicitly added
and must be configured (see chapter 5 – Defining datapoint) according to their described
features.
(2)
(1)
FIGURE 142: MANDATORY ‘SYSTEM INFOS’ DATAPOINT FOR A SCADA NETWORK
− 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
5. DEFINING DATAPOINT
5.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 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
PACiS system behaviour (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.
Be careful:
(Refer to section 4.6.1 – Connecting MiCOM C264P to others station-bus sub-systems, for
Client / Server definition).
In the set of all the protections of a SCS, the previous described SPS attributes (except short
name and long name) are only useful and given to the MiCOM C264P that serves the
datapoint because the relevant functions are always done at protection server level.
5.1.1 Overview of binary input processing
Binary input processing is described in section 4.1 of chapter C264P/EN FT
By extension, at SCE level:
• System inputs (SI) are seen as particular SPS, DPS or MPS depending on the number
of elementary information they represents (for details about SI, see section 4.11 –
Setting system information for components).
• Group binary input is seen as particular SPS.

5.1.2 Defining an SPS datapoint

5.1.2.1 SPS processing
Processing of an SPS is described in section 5.1.2 of chapter C264P/EN.
5.1.2.2 Creating an SPS datapoint
To create an SPS datapoint:
• Add an SPS from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of SPS exist. They are
used for specific needs at electrical topology level (for details see relevant section in
6 – Defining MiCOM C264P configuration in electrical architecture) or system topology
level (for details see section 4.11 – Setting system information for components).
• Update the SPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SPS.
• Update its relation ‘has for profile’ to point to a specific existing profile (2). See section
5.2 – Linking a datapoint to a profile, for details about profile definition and setting.
(1)
FIGURE 143: ADDING A SPS DATAPOINT (SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPS)
(2)
FIGURE 144: LINKING A SPS DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPS)
Updating SPS attributes (description for generic SPS)

When adding a generic SPS datapoint, some general attributes must be updated:
1. short name and long name of the datapoint used for logging, alarms ...
2. 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 1ms.
3. stable state time reference (Start of filtering / End of filtering)
4. reset confirmation delay TR (range [0 s, 120 s], step 100 ms]: confirmation delay for
stable ‘reset’ state.
5. set confirmation delay TS (range [0 s, 120 s], step 100 ms]: confirmation delay for
stable ‘set’ state.
6. forcing management (Not automatic / Automatic to reset state / Automatic to set
state): when a SPS goes in invalid state, protection 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.
7. state panel assignment (No / Yes): set to ‘yes’ to enable SPS state display at
MiCOM C264P local HMI level.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 145: SETTING GENERAL ATTRIBUTES OF AN SPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPS)
5.1.3 Defining a DPS datapoint

5.1.3.1 DPS processing
Processing of a DPS is described in section 4.1.3 of chapter C264P/EN FT.
5.1.3.2 Creating a DPS datapoint
To create a DPS datapoint:
• Add a DPS from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of DPS exist. They are
• Update the DPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of DPS.
(1)
FIGURE 146: ADDING A DPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC DPS)
(2)
FIGURE 147: LINKING DPS DATAPOINT TO ITS PROFILE

Updating DPS attributes (description for generic DPS)

When adding a generic DPS datapoint, some general attributes must be updated:
2. stable state time reference ( Start motion / End motion): this attribute defines the
time reference for a stable state: at start of motion filtering or end of motion filtering.
3. complementary delay jammed (range [0 s, 60 s), step 100 ms): this attribute defines
the delay for the MOTION00 (JAMMED) state filtering. It corresponds to parameter T00
mentioned in § 4.1.3.1 of chapter C264P/EN FT.
4. complementary delay undefined (range [0 s, 60 s), step 100 ms): this attribute
defines the delay for the MOTION11 (UNDEFINED) state filtering. It corresponds to
parameter T11 mentioned in § 4.1.3.1 of chapter C264P/EN FT.
5. open confirmation delay (range [0 s, 60 s), step 100 ms): this attribute defines the
confirmation delay for the OPEN state. It corresponds to parameter TO mentioned in §
4.1.3.2 of chapter C264P/EN FT.
6. closed confirmation delay (range [0 s, 60 s), step 100 ms): this attribute defines the
confirmation delay for the CLOSE state. It corresponds to parameter TC mentioned in
§ 4.1.3.2 of chapter C264P/EN FT.
7. forcing management (Not automatic / Automatic to reset state / Automatic to set
state): when a DPS is in an invalid state, the MiCOM C264P 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
given to the user by the DPS profile.
8. state panel assignment (No / Yes): set to ‘yes’ to enable the display of the DPS state
at the MiCOM C264P local HMI level.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 148: SETTING GENERAL ATTRIBUTES OF A DPS DATAPOINT

5.1.4 Defining an MPS datapoint

5.1.4.1 MPS processing
Processing of an MPS is described in section 4.1.4 of chapter C264P/EN FT.
5.1.4.2 Creating an MPS datapoint
To create an MPS datapoint:
• Add an MPS from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of MPS exist. They are
• Update the MPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of MPS.
(1)
FIGURE 149: ADDING A MPS DATAPOINT (SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MPS)
(2)
FIGURE 150: LINKING MPS DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MPS)
Updating MPS attributes (description for generic MPS)

When adding a generic MPS datapoint, some general attributes must be updated:
2. filtering delay (range [0 s, 6553,5 s), step 10 ms).
3. inhibition delay (range [0 s, 6553,5 s), step 10 ms).
2. forcing management (Not automatic / Automatic to state <i> (i ∈ [0, 15])): when a
MPS goes in invalid state, MiCOM C264P 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.
3. state panel assignment (No / Yes): set to ‘yes’ to enable MPS state display at
(1)
(2)
(3)
(4)
(5)
FIGURE 151: SETTING GENERAL ATTRIBUTES OF A MPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MPS)
5.1.5 Overview of measurement processing

Processing of a measurement is described in section 4.2 of chapter C264P/EN FT.
Features of digital measurements are described in section 4.2.11 of chapter C264P/EN FT.
5.1.5.1 Analogue measurement acquisition
Analogue measurements are acquired via input analogue channel (AI) of AIU board. These
AI are voltage or current DC signals (only current for AIU211 board) delivered by
transducers, and representing an external value.
Input characteristics
Input range
• For voltage inputs:
± 10V
± 5V
± 2.5V
± 1.25V
• For current inputs:
0 - 1mA
± 1mA
0 - 5mA
± 5mA
0 - 10mA
± 10mA
4 - 20mA
0 - 20mA
± 20mA
Each channel on a board can be assigned one of these ranges (voltage or current)
independently of the others channels (see chapter 4.4.5 – Configuring an AI channel).
Each AI should be able to convert the nominal range +20%, this feature being configurable.
The same accuracy must be achieved over the whole range: nominal+20%.
For the 4-20mA range, the value provided by the analogue board is 0-16Ma.
Overall accuracy
The accuracy of the complete acquisition chain is 0.1 % of the full scale for each range at a
reference temperature of 25 °C.
The error due to a shift from the reference temperature is 30 ppm/°C between
–10°C and +55°C.
Rejection ratios
CMMR: The common mode rejection ratio of the 50 / 60 Hz is greater than 100 dB.
SMRR: The serial mode rejection ratio of the 50/60 Hz is greater than 40 dB.
Overload condition
The saturation value, for each range, is the following:
Range Saturation values

± 10V -12.6V / +12.6V
± 5V -6.3V / +6.3V
± 2.5V -3.2V / +3.2V
± 1.25V -1.26V / +1.26V
0 - 1mA 1.26mA
± 1mA -1.26mA / +1.26mA
0 – 5mA 6.3mA
± 5mA -6.3mA / +6.3mA
0 – 10mA 12.5mA
± 10mA -12.5mA / +12.5mA
0 – 20mA 25mA
± 20mA -25mA / +25mA
4-20mA 26mA
Acquisition
Acquisition cycle
The analogue inputs are acquired on a periodical basis. Each channel on a board can be
assigned one of these cycles independently of the others channels (see section 4.4.5 –
Configuring an AI channel).
There exists two acquisition cycles:
− a short cycle (Nsc x 100 ms, Nsc configurable from 1 to 10 with a default value of 1).
− a long cycle (Nlc x 500 ms, Nlc configurable from 1 to 20, with a default value of 2).
AD conversion
The Analogue to Digital Converter has a 16 bits resolution (15 bits + sign bit).
The zero offset value is computed by the conversion of a 0 V voltage reference.
The gain is adjusted automatically by software by connecting a known voltage reference to
the amplifier.
The zero offset values and the gain are adjusted regularly in order to compensate for the
deviations caused by variations of temperature and ageing.
Self-checks
Two two kinds of self-checks are performed:
• the board address coherency
• the complementarity control of the measured value

These self-checks are performed at each scan (defined during the configuration phase).
Time tagging
An AI is time stamped with the date/time of the scanned value.
5.1.6 Defining MV datapoint

5.1.6.1 Adding an MV datapoint
To create an MV datapoint:
• Add an MV from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of MV exist. They are
• Update the MV attributes (see following sections); some attributes can be fixed or
masked depending on the pre-defined kind of MV.
(1)
FIGURE 152: ADDING AN MV DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR A GENERIC MV)
(2)
FIGURE 153: LINKING A MV DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR A GENERIC MV)
5.1.6.2 Setting ‘General’ attributes of an MV datapoint

When adding a generic MV datapoint, some general attributes must be updated:
1. short name and long name: used for logging, alarms ...
2. 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)
For details about digital encoding see section 4.2.11 of chapter C264P/EN FT.
3. automatic forcing (No / Yes): when an MV goes in invalid state, MiCOM C264P can
force or not its value automatically. Automatic forcing management is independent of
FSS facility gives at user by the MV profile.
4. value for automatic forcing: MV value when automatic forcing
5. transmission on event (Cyclic long period / Cyclic short period / According to a ‰ of
full scale value / According to a ‰ of current value)
6. 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 4.2.9.2 of chapter C264P/EN FT.
7. MV panel assignment (No / Yes): set to ‘yes’ to enable MV value displayed at
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 154: SETTING GENERAL ATTRIBUTES OF A MV DATAPOINT

5.1.6.3 Setting ‘Value features’ attributes of a MV datapoint

When adding a generic MV datapoint, some ‘Value features’ attributes must be updated:
1. minimum value (range [-3.4e38, 3.4e38]: used for full scale calculation and scaling
2. maximum value (range [-3.4e38, 3.4e38]: used for full scale calculation and scaling.
(Full scale = maximum value - minimum value)
3. 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 section 4.2.3 of chapter C264P/EN FT for details)
4. Hysteresis used for threshold detection (see section 4.2.4 of chapter C264P/EN FT for
details)
For each available threshold (see section 4.2.4 of chapter C264P/EN FT for details):
5. Threshold usage (No / Yes)
6. Threshold value
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 155: SETTING VALUE FEATURES ATTRIBUTES TO MV DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MV)
5.1.6.4 Setting ‘Scaling’ attributes of a MV datapoint

When adding a generic MV datapoint, some ‘Scaling’ attributes must be updated:
1. scaling rule: available values are (see section 4.2.2 of chapter C264P/EN FT for details):
− Linear
− Quadratic
− Quadratic with offset
2. minimum acq. value (used for scaling)
3. maximum acq. value (used for scaling)
In case of multi-segment scaling:
4. Ai coefficient
5. Bi coefficient
(1)
(2)
(3)
(4)
(5)
FIGURE 156: SETTING SCALING ATTRIBUTES OF A MV DATAPOINT

5.1.6.4.1 Setting ‘Digital acquisition’ attributes of MV datapoint
When adding a generic digital MV datapoint, some ‘Digital acquisition’ attributes must be
updated.
Refer to section 4.2.11 (Features of digital measurements) of chapter C264P/EN FT for
attribute meaning.
1. Inhibition delay (x 10 ms): used for digital measurement with read inhibit signal
3. Stabilisation delay (x 10 ms)
4. Stabilisation value
5. Validation delay (x 10 ms):
(1)
(2)
(3)
(4)
FIGURE 157: SETTING DIGITAL ACQUISITION ATTRIBUTES TO MV DATAPOINT

• If the attribute "type" of the "MV" Datapoint is set to a "Digital…" value, then the
following constraint between the two attributes must be respected:
- "validation delay" ≥ 5 ∗ "stabilization delay"
5.1.7 Defining a TPI datapoint

5.1.7.1 Overview of Tap Position Indicator processing
Tap Position Indicator (TPI) is described section 4.3 of chapter C264P/EN FT
Tap Position Indicator (TPI) must be 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 DIU board (up to 64 DI channels). In

that case, available digital MV type are: Decimal, Gray, BCD or ‘1 among n’.
5.1.7.2 Adding a TPI datapoint
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 see section 6 – Defining MICOM C264P
configuration in electrical architecture.
Once a TPI has been created by adding a tap changer built-in function (1):
• Update the TPI attributes (see following sections).
• Update its relation ‘has for profile’ to point to a specific existing MV profile (2). See
section 5.2 – Linking a datapoint to a profile, for details about profile definition and
setting.
Bay transformer
Mandatory transformer module
(1) Tap changer built-in function
Mandatory TPI
C0191ENb
FIGURE 158: AUTOMATIC TPI CREATION FOR TAP-CHANGER BUILT-IN FUNCTION
(2)
FIGURE 159: LINKING TPI DATAPOINT TO ITS PROFILE

5.1.7.3 Setting ‘General’ attributes of a TPI datapoint

For a TPI datapoint, some general attributes, similar to MV attributes, must be updated:
2. 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)
For details about digital encoding see section 4.2.11 of chapter C264P/EN FT.
3. MV panel assignment (No / Yes): set to ‘yes’ to enable MV value display at MiCOM
C264P local HMI level.
(1)
(2)
(3)
FIGURE 160: SETTING GENERAL ATTRIBUTES OF A TPI DATAPOINT

5.1.7.4 Setting ‘Value features’ attributes of a TPI datapoint
Refer to section 5.1.6.3 – Setting ‘Value features’ attributes of a MV datapoint
• The following constraint between the two attributes must be respected:

("maximum value" − "minimum value" + 1) ∈ [1..64]
5.1.7.5 Setting ‘Tap position’ attributes of a TPI datapoint
For a TPI datapoint, some specific attributes must be updated:
1. Filtering delay (range [0 , 655,35 s], step 10 ms):
− for digital TPI, corresponds to Tstab of digital measurement

(Refer to section 4.3 of chapter C264P/EN FT for attribute meaning)
− for analog TPI, corresponds to a delay to filter transient UNDEFINED state (delay
to confirm UNDEFINED state)
2. current valid range (% maximum value) (range [0 , 20 %], step 1 %): only used for
analogue TPI corresponds to N parameter described in section 4.3 of chapter
C264P/EN FT.
(1)
(2)
FIGURE 161: SETTING TAP POSITION ATTRIBUTES OF A TPI DATAPOINT

5.1.7.6 Setting ‘Scaling’ attributes of a TPI datapoint

For an analogue TPI datapoint, some ‘Scaling’ attributes appears and must be updated:
1. minimum acq. value: corresponds to Imin parameter described in section 4.3.2 of
chapter C264P/EN FT.
2. maximum acq. value: corresponds to Imax parameter described in section 4.3 of
chapter C264P/EN FT.
(1)
(2)
FIGURE 162: SETTING SCALING ATTRIBUTES OF A TPI DATAPOINT

5.1.8 Defining a Counter datapoint

5.1.8.1 Overview of counter processing
Single counters and double counters are described in section §4.5 of chapter C264P/EN FT.
Continuous register Scaling

From counters
acquisition
+
+1
Accumulator Transmission
= To RCP
To HMI
To archive
Periodic register Scaling To automation
in
24h - FIFO
C0195ENa
FIGURE 163: COUNTER PROCESSING
• The accumulator is incremented at each valid counter pulse.
• The periodic register is used to store the accumulator value of the previous period.
• The continuous register is used to store the accumulator value since the origin.
• The FIFO memory is used to store the periodic register of each period (up to 16
counters), during 24h.
Periodic processing
A period is defined either:
• By an external pulse on a digital input.
• By the internal clock: the period length is settable: 10', 15', 30', 1h to 24h , each period
begins at a regular hour: 12:00 , 12:30 , 13:00 ...
This choice is defined during the configuration phase on a per MiCOM C264P basis. The
period delimiter is also defined at configuration time for each counter.
At each period:
• The content of the accumulator is added to the continuous register.
• The content of the accumulator is transferred to the periodic register.
• The content of the periodic register is inserted into the FIFO queue.
• The accumulator is reset to 0 (a pending pulse is not lost ).
• Either the continuous register or the periodic register is transmitted. The choice is
made by configuration on a per accumulator basis.
If the chosen transmitted register reaches its maximum value (232), the counter status is set
to OVERRANGE. Only a counter modification can re-validate the counter.
Scaling
Scaling is used for printing or displaying a counter. EPI is a parameter giving the amount of
energy in KW-h or KVAR-h equivalent to a pulse. The displayed value is:
N x EPI KW-h
With N = the value of a counter.
Counter resulting states
The state of a counter can be:
State Comment
VALID not in one of the below states
SELFCHECK Due to the SELFCHECK FAULTY of the DI
FAULTY
UNKNOWN If the counter is acquired via a transmission link, the
information is unknown when the link is disconnected.
UNDEFINED Due to a counting failure of DCT (non-complementarity of
the 2 contacts)
OVERRANGE when the maximum value is reached
Transmission
The counters 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 counters are set to
The counter informations transmitted in a report are:
• the number of pulses (i.e. accumulator value before scaling).
• the real value.
• the time stamping (in GMT time) and time quality.
• the resulting state (mapped on the quality field on IEC-61850).
• the reason for change, which could be one of the following values:
− cyclic change (set if the value has changed)

− change of quality (set if the quality has changed)
− change due to control (set if the value or quality change is due to a control)
Counter modification
When an accumulator value is modified, the request is immediately taken into account. The
continuous register is set with the accumulator value.
The modification could be a reset of the counter.
5.1.8.2 Adding a Counter datapoint
To create a Counter datapoint:
• Add a Counter from object entry available at the wished system or electrical object
level (1). Depending on the object level, different pre-defined kinds of counter exist.
They are used for specific needs at electrical topology level (for details see relevant
section in 6 – Defining MiCOM C264P configuration in electrical architecture) or
system topology level (for details see section 4.11 – Setting system information for
components).
• Update the Counter attributes (see following sections).

(1)
FIGURE 164: ADDING A COUNTER DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC COUNTER)
(2)
FIGURE 165: LINKING COUNTER DATAPOINT TO ITS PROFILE

5.1.8.3 Setting ‘General’ attributes of a Counter datapoint
When adding a generic Counter datapoint, some general attributes must be updated:
2. 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).
3. validation duration (range [0, 10 s], step 1 ms): corresponds to Tcount parameter
described in section 4.5 of chapter C264P/EN FT.
4. invalidity duration (range [5, 10 s], step 1 ms): corresponds to Tdef parameter
described in section 4.5 of chapter C264P/EN FT.
5. 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).
6. cumul period (10 mn / 15 mn / 30 mn / N h (N ∈ [1, 24])): corresponds to period

length of internal clock parameter described in section1.
7. 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.
8. MV panel assignment (No / Yes): set to ‘yes’ to enable Counter value display at
9. scale factor.
10. energy type (Activ energy, Reactiv energy).
11. transmission period (10 mn / 15 mn / 30 mn / N h (N ∈ [1, 24])).

12. reset after transmission (No, Yes).
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
FIGURE 166: SETTING GENERAL ATTRIBUTES OF A COUNTER DATAPOINT

5.1.9 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 (DOU board) or via
IEDs connected by a serial link (for details see section 5.6).
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 4.11 – Setting system information for components).
Control sequences are described in section 5 of chapter C264P/EN FT (Functional
Description).
5.1.10 Defining an SPC datapoint
To create an SPC datapoint:
• Add ann SPC from object entry available at the wished system or electrical object
level (1). Depending on the object level, different pre-defined kinds of SPC exist. They
are used for specific needs at electrical topology level (for details see relevant section
in 6 – Defining MiCOM C264P configuration in electrical architecture) or system
topology level (for details see section 4.11 – Setting system information for
components).
• Update the SPC attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SPC.
(1)
FIGURE 167: ADDING AN SPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPC)
(2)
FIGURE 168: LINKING A SPC DATAPOINT TO ITS PROFILE

5.1.10.1 Setting ‘General’ attributes of a SPC datapoint
When adding a generic SPC datapoint, some general attributes must be updated:
2. activation mode (Permanent / Transient / Permanent until feedback).
3. 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.
4. hold duration (range [0, 10 s], step 10 ms): 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.
5. time between two orders (range [0, 10 s], step 100 ms): this attribute corresponds to
the inter-control delay defined in section 5.1.6.1 of chapter C264P/EN FT and use also
used for execution checks (see section 5.1.8 of chapter C264P/EN FT).
6. command panel assignment (No / Yes): set to ‘yes’ to enable SPC control at
(1)
(2)
(5)
(6)
(1)
(2)
(3)
(5)
(6)
(1)
(2)
(4)
(5)
(6)
FIGURE 169: SETTING GENERAL ATTRIBUTES OF A SPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR A GENERIC SPC)
5.1.10.2 Setting ‘Dependencies’ attributes of a SPC datapoint
When adding a generic SPC datapoint, some ‘dependencies’ attributes must be updated,
that correspond to:
• substation and bay mode controls and bay uniqueness control defined in section 5.1.6
of chapter C264P/EN FT and use also for execution checks (see section 5.1.8 of
chapter C264P/EN FT), if SPC datapoint is located under a bay.
• substation mode control and substation uniqueness control, if SPC level is higher than
bay level.
Substation/Bay control uniqueness is globally set at substation level (see section 6.1.2 –
Defining a Substation). When substation uniqueness is set, bay uniqueness is implicitly set
for all bays.
Dependencies for SPC level lower than or equal to bay level

1. bay mode dependency (No / Yes).
2. SBMC mode dependency (No / Yes).
3. bay control uniqueness dependency (No / Yes): only significant if control
uniqueness is set to bay at substation level.
4. Local substation dependency (Command from SCADA is refused / Command from
SCADA is accepted)
5. Remote substation dependency (Command from OI is refused / Command from OI
is accepted)
(1)
(2)
(3)
(4)
(5)
FIGURE 170: SETTING DEPENDENCIES ATTRIBUTES OF A SPC DATAPOINT

Dependencies for SPC level higher than bay level (in the exemple voltage or substation
level)
1. Substation control uniqueness dependency (No / Yes): only significant if control
uniqueness is set to substation at substation level.
SCADA is accepted)
is accepted)
(1)
(2)
(3)
(1)
(2)
(3)
FIGURE 171: SETTING DEPENDENCIES ATTRIBUTES OF A SPC DATAPOINT

(SAMPLE GIVEN AT VOLTAGE LEVEL FOR GENERIC SPC)
5.1.10.3 Defining a SPC feedback

For correct execution behaviour and control acknowledgement, a 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 a 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.
− If necessary update the relation attributes:
(1)
(2)
FIGURE 172: DEFINING SPC FEEDBACK

3. 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 acknowledgement is sent for
the control (for details see section 5.1.9 – Overview of control sequence processing).
4. 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 5.1.6.8 of
chapter C264P/EN FT and used also for execution checks (see section 5.1.8 of
chapter C264P/EN FT).
(3)
(4)
FIGURE 173: SETTING ATTRIBUTES OF A 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
MiCOM C264P, 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 "IEC64850/IEC gen IED" through the relation "has for
IEC64850/IEC 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"
5.1.11 Defining a DPC datapoint

To create a DPC datapoint:
• Add a DPC from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of DPC exist. They are
6 – Defining MiCOM C264P configuration in electrical architecture) or system
topology level (for details see section 4.11 – Setting system information for
components).
• Update the DPC attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of DPC.
5.2.7, for details about profile definition and setting.
(1)
FIGURE 174: ADDING A DPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC DPC)
(2)
FIGURE 175: LINKING A DPC DATAPOINT TO ITS PROFILE

5.1.11.1 Setting ‘General’ attributes of a DPC datapoint
When adding a generic DPC datapoint, some general attributes must be updated:
2. activation mode (Permanent / Transient / Permanent until feedback).
3. close duration (range [0, 15 s], step 10 ms): 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.
4. open duration (range [0, 15 s], step 10 ms): 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.
5. hold duration (range [0, 10 s], step 10 ms): 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.
6. time between two orders (range [0, 10 s], step 100 ms): this attribute corresponds to
the inter-control delay defined in section 5.1.6.1 of chapter C264P/EN FT and use also
used for execution checks (see section 5.1.8 of chapter C264P/EN FT).
7. command panel assignment (No / Yes): set to ‘Yes’ to enable SPC control at
(1)
(2)
(4)
(5)
(6)
(1)
(2)
(5)
(6)
(1)
(2)
(3)
(5)
(6)
(7)
FIGURE 176: SETTING GENERAL ATTRIBUTES OF A DPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR A GENERIC DPC)
5.1.11.2 Setting ‘Dependencies’ attributes of a DPC datapoint
When adding a generic DPC datapoint, some ‘dependencies’ attributes must be updated,
that correspond to:
• substation and bay mode controls and bay uniqueness control (defined in section
5.1.6 of chapter C264P/EN FT) and also used for execution checks if DPC datapoint is
located under a bay.
• substation mode control and substation uniqueness control, if DPC level is higher than
bay level.
for all bays.
Dependencies for DPC level lower than or equal to bay level
SCADA is accepted)
is accepted)
(1)
(2)
(3)
(4)
(5)
FIGURE 177: SETTING DEPENDENCIES ATTRIBUTES OF A DPC DATAPOINT

Dependencies for DPC level higher than bay level
1. substation control uniqueness dependency (No / Yes): only significant if control
SCADA is accepted)
is accepted)
(1)
(2)
(3)
(1)
(2)
(3)
FIGURE 178: SETTING DEPENDENCIES ATTRIBUTES OF A DPC DATAPOINT

(SAMPLE GIVEN AT VOLTAGE LEVEL FOR GENERIC DPC)
5.1.11.3 Defining a DPC feedback

For correct execution behaviour and control acknowledgement, 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:
• 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.
• If necessary update the relation attributes:

3. execution timeout (range [0, 6000 s] step 100 ms): in this given delay, feedback
must change relatively to the control. If not, a negative acknowledgement is sent for
the control (for details see section 5.1.9 – Overview of control sequence processing).
4. 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, jemmed
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 5.1.6.8 of
chapter C264P/EN FT and also used for execution checks (see section 5.1.8 of
chapter C264P/EN FT).
(1)
(2)
FIGURE 179: DEFINING A DPC FEEDBACK
(3)
(4)
FIGURE 180: SETTING ATTRIBUTES OF A DPC FEEDBACK RELATION

• For each "DPC", two relations "has for feedback" are available, but they are mutually
exclusive.
IEC61850/IEC address", this relation must also be defined for the other one.
• 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" ].
5.1.12 Defining a SetPoint datapoint
5.1.12.1 Overview of SetPoint processing
Digital setpoints are described in section 5.8.3 of chapter C264P/EN FT.
SetPoints are used to send instruction values to the process or to ancillary devices. MiCOM
C264Ps manage four types of SetPoints:
• Digital SetPoints.
• SetPoints to IEDs.
• System SetPoints.
• Analogue 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 5.8.3 of chapter C264P/EN FT.
Read inhibit signal for digital SetPoint

A dedicated binary output can be used 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.
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.
• 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.
Value
RI
C0210ENa
FIGURE 181: 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.
SetPoints to IEDs
SetPoints controls towards IEDs are managed in “Direct execute mode”. Execution phase is
identical to the digital SetPoints. The execution is performed via the communication protocol
of the concerned IED.
System SetPoint
SetPoints can be locally managed by MiCOM C264P as a system control for automation for
instance. Execution phase is identical to the digital SetPoints.
Analog Setpoints
Analog setpoints are measurement values sent on the Analog Output board.
These setpoints 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).
The Analog output values are secured with an external power supply which allows keeping
the analog output value in case of MiCOM C264P shutdown or power off.
A quality indication is available with the additional Read Inhibit output relays (normally open)
associated to each analog output.
5.1.12.2 Adding a SetPoint datapoint
To create a SetPoint datapoint:
• Add a SetPoint from object entry available at the wished system or electrical object
level (1). Depending on the object level, different pre-defined kinds of SetPoint exist.
They are used for specific needs at electrical topology level (for details see relevant
section in 6 – Defining MiCOM C264P configuration in electrical architecture) or
system topology level (for details see section 4.11 – Setting system information for
components).
• Update the SetPoint attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SetPoint.
5.2.8 – Defining a SetPoint profile, for details about profile definition and setting.
(1)
FIGURE 182: ADDING A SETPOINT DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SETPOINT)
(2)
FIGURE 183: LINKING A SETPOINT DATAPOINT TO ITS PROFILE

5.1.12.3 Setting ‘General’ attributes of a SetPoint datapoint

When adding a generic SetPoint datapoint, some general attributes must be updated:
2. type:
a. Analogue: SetPoint is managed by IED, by system output or by AOU board
ouptut
− Digital coded ‘BCD’
− Digital coded ‘Pure binary’

b. Digital coded ‘Gray’
− Digital coded ‘1 among N’
− Digital coded ‘decimal’

For details refer to section 5.8.3 of chapter C264P/EN FT.
3. progressive step usage: only used for digital SetPoint. No corresponds to Raw
activation, Yes to Incremental Activation, described in section 5.1.12.1 – Overview of
SetPoint processing.
4. minimum value (range [-3.4E38, 3.4E38]): used for value control and scaling.
5. maximum value (range [-3.4E38, 3.4E38]): used for value control and scaling.
6. command panel assignment (Yes / No): set to ‘yes’ to enable SetPoint control at
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 184: SETTING GENERAL ATTRIBUTES OF A SETPOINT DATAPOINT

• A Setpoint datapoint wired on DO channels of a MiCOM C264P, must be digital and

have its profile attribute “SBO mode” set to "Direct Execute" or “Direct Execute with
SBO popup”.
• A Setpoint datapoint wired on AO channel of a MiCOM C264P must be analogue and

have its profile attribute “SBO mode” set to "Direct Execute" only.
5.1.12.4 Setting ‘Dependencies’ attributes of a SetPoint datapoint

When adding a generic SetPoint datapoint, some ‘dependencies’ attributes must be updated,
that correspond to:
• substation and bay mode controls and bay uniqueness control defined in section 5.1.6
of chapter C264P/EN FT and use also for execution checks (see section 5.1.8 of
chapter C264P/EN FT), if a Setpoint datapoint is located under a bay.
• substation mode control and substation uniqueness control, if SetPoint level is higher
than bay level.
for all bays.
Dependencies for SetPoint level lower than or equal to bay level
SCADA is accepted).
is accepted).
(1)
(2)
(3)
(4)
(5)
FIGURE 185: SETTING DEPENDENCIES ATTRIBUTES OF A SETPOINT DATAPOINT

Dependencies for SetPoint level higher than bay level
1. substation control uniqueness dependency (No / Yes): only significant if control
SCADA is accepted).
is accepted).
(1)
(2)
(3)
(1)
(2)
(3)
FIGURE 186: SETTING DEPENDENCIES ATTRIBUTES OF A SETPOINT DATAPOINT

(SAMPLE GIVEN AT VOLTAGE LEVEL FOR GENERIC SETPOINT)
5.1.12.5 Defining a SetPoint feedback

For correct execution behaviour and control acknowledgement, a SetPoint datapoint can be
linked to a 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.
• If necessary update the relation attributes:
• 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 for the
control (for details see section 5.1.9 – Overview of control sequence processing).
(1)
FIGURE 187: DEFINING SETPOINT FEEDBACK
(2)
FIGURE 188: SETTING ATTRIBUTES OF A SETPOINT FEEDBACK RELATION

IEC61850/IEC address", this relation must also be defined for the other one.
5.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 got 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 datapoints (SPS, DPS…) there exists a relevant profile (SPSProfile,
DPSProfile…). Several datapoints of the same kind are link-able to the same profile.
Be careful:
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.
• links to printers defined in the system topology for alarm and event logging purpose.
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.
• links to printers defined in the system topology for alarm and event logging purpose.
‘Profile’ objects can be put at any level of the system topology but never in the electrical
topology: they concern only system characteristics. For details about the system topology,
see section 4 – Defining MICOM C264P configuration in system architecture.
A profile object can be added at the following levels of the system topology:
• SCS.
• Ethernet network.
• Any instance of MiCOM C264P.
• Any instance of MiCOM C264P board.
• Any protection printer.
• Any SCADA network managed by a MiCOM C264P.
• Any IED managed by a MiCOM C264P.

When configuring a MiCOM C264P, the best practice is to group all profiles relevant to its
system datapoints at MiCOM C264P level or eventually its sub-components. Upper levels
(Ethernet network or SCS) can be used to define profiles if sharing datapoint profile between
several protections is wished.
For electrical datapoints, different approaches can be done:
• Grouping datapoint profiles at MiCOM C264P level per bay basis it manages.
• Grouping datapoint profiles at SCS level by kind of bays/modules managed by the

system.
• Mixing the two previous approaches, particularly for profiles relevant to datapoints
whose level is upper than bay or belonging to same kind of bays fed by several bay
protections.
Be careful:
(Refer to section 4.6.1 – Connecting MiCOM C264P to others station-bus sub-systems, for
Client / Server definition).
In the set of all the protections of a SCS:
• the following profile functional characteristics logging, alarm, archiving and FSS, are
only useful and given to the MiCOM C264P that serves the linked datapoints because
these functions are always done at protection server level. So, a MiCOM C264P A
using a datapoint acquired on a protection B will never log, alarm or archive events
relevant to this datapoint.
• the following profile functional characteristics ‘state interlocking values’ are given to
server and client protections using a datapoint, because interlock evaluation is a
distributed function done on every MiCOM C264P that needs it before controlling its
own electrical modules.
• the following profile functional characteristics ‘SBMC facilities’ are given to server or
client protections using a datapoint exchanged on a SCADA network they manage,
because SBMC filtering is a distributed function done on MiCOM C264Ps managing
SCADA networks.
• the following profile characteristics ‘state/order labels’ are given to server or client
protections using a datapoint but are only used by the server: MiCOM C264P bay
mimics, logging, alarm definitions are reduced to datapoints that the protection is
server of.
5.2.1 Defining an SPS profile

5.2.1.1 Adding an SPS Profile
To create an SPS profile:
• Add an SPS profile from object entry available at the wished system object level (1).
• Update the profile attributes (see following sections).
• Define if necessary on which printers event logging of linked SPS datapoint is done,
via adding and filling the relation ‘has events logged on’ at profile level (2).
• Define if necessary on which printers alarm event logging of linked SPS datapoint is
done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).
(1)
FIGURE 189: ADDING AN SPS PROFILE (SAMPLE GIVEN AT MICOM C264P LEVEL)
(2)
FIGURE 190: DEFINING EVENT LOGGING PRINTER FOR SPS PROFILE
(3)
FIGURE 191: DEFINING ALARM LOGGING PRINTER FOR SPS PROFILE

5.2.1.2 Setting ‘General’ attributes of an SPS Profile

When adding an SPS profile some general attributes must be updated:
1. short name and long name of the profile only used for profile identification in SCE.
And for linked SPS datapoints:
2. enable Force/Subst/Sup (No / Yes).
3. SBMC dependant (No / Yes).
4. SBMC state substitution value (Suppressed / Set / Reset): significant and visible if
SBMC dependant is set to Yes.
5. toggling filtering (No / Yes): useful for a datapoint acquired on a DI board to filter
toggling.
6. initial status (Reset / Set): used for MiCOM C264P software initialisation especially
for system datapoints.
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 192: SETTING GENERAL ATTRIBUTES OF AN SPS PROFILE

• The profile of a datapoint of the System topology must have its enable
Force/Subst/Sup attribute set to No.
5.2.1.3 Setting ‘State labels’ attributes of an SPS Profile
When adding an SPS profile, some State labels attributes must be updated (1). They are
used for events and alarm management at MiCOM C264P level (logging, display).
(1)
FIGURE 193: SETTING ‘STATE LABELS’ ATTRIBUTES OF AN SPS PROFILE

5.2.1.4 Setting ‘State treatment’ attributes of an SPS Profile

When adding an SPS profile, some State treatment attributes must be updated, for each
available state of the linked datapoints (1).
Available attribute values are:
• OI & C264: no archive, no logging.

• OI & C264: archive, logging.
• OI & C264: archive, no logging.
• only C264: no archive, logging.
• only C264: archive, logging.
• only C264: archive, no logging.
• only OI: archive, logging.
• only OI: archive, no logging.
For MiCOM C264P configuration, a more synthetic vision of logging and archiving is
deduced from these attributes: for details refer to sections 5.3 – Defining MiCOM C264P
local archiving of datapoint events and 5.5 – Defining MiCOM C264P local logging of
datapoint events and alarms.
(1)
FIGURE 194: SETTING ‘STATE TREATMENTS’ ATTRIBUTES OF A SPS PROFILE

5.2.1.5 Setting ‘Alarms’ attributes of an SPS Profile
When adding an SPS profile some Alarms attributes must be updated, for each available
state of the linked datapoints.
1. 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:
2. defined (No / Yes).
3. masking due to control (No / Yes): this attribute must be set to ‘Yes’ to manage
correctly discrepancy (alarm only appears in case of spontaneous change of state
without previous control).
4. delay (range [0 s, 120 s], step 1 s): to avoid alarm generation if alarm condition
disappears within this delay.
5. gravity (range [1, 5], step 1).
6. audible (No / Yes): to activate a klaxon.
7. clearing mode (Manual / Automatic / Gravity basis): to precise the way alarm is
cleared when alarm condition disappears:
− Manual: users must 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 ‘Set’ and ‘Reset’ state, extra attribute spurious is settable ((8) and (9)). This information
is only significant when the user wants to alarm a spurious SPS datapoint on a particular
event Set or Reset. In fact, the datapoint has got no state, but generates an event. It is
useful to alarm trip information of relays for instance. When setting a spurious alarm, only the
relative state must be defined as alarmed; the other states must be set to ‘not defined alarm’.
For MiCOM C264P configuration, all attributes are significant for datapoints it is server of.
(1)
(2)
(8)
(3)
(4)
(5)
(6)
(7)
(9)
FIGURE 195: SETTING ‘ALARMS’ ATTRIBUTES OF AN SPS PROFILE

5.2.1.6 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.
(1)
FIGURE 196: SETTING ‘INTERLOCKING’ ATTRIBUTES OF AN SPS PROFILE

5.2.2 Defining a DPS profile
5.2.2.1 Adding a DPS Profile
To create a DPS profile:
• Add a DPS profile from object entry available at the wished system object level (1).
• Defines if necessary on which printers event logging of linked DPS datapoint is done,
• Defines if necessary on which printers alarm event logging of linked DPS datapoint is
(3).
(1)
FIGURE 197: ADDING A DPS PROFILE (SAMPLE GIVEN AT MICOM C264P LEVEL)
(2)
FIGURE 198: DEFINING EVENT LOGGING PRINTER FOR DPS PROFILE
(3)
FIGURE 199: DEFINING ALARM LOGGING PRINTER FOR DPS PROFILE

5.2.2.2 Setting ‘General’ attributes of a DPS Profile
When adding a DPS profile, some general attributes must be updated:
And for linked DPS datapoints:
4. SBMC state substitution value (Suppressed / Open / Closed / Jammed), significant
and visible if SBMC dependant is set to Yes.
5. toggling filtering (No / Yes): useful for datapoint acquired on DI board to filter
toggling.
6. initial status (Motion / Open / Closed / Undefined), used for MiCOM C264P software
initialisation especially for system datapoints.
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 200: SETTING GENERAL ATTRIBUTES OF A DPS PROFILE

5.2.2.3 Setting ‘State labels’ attributes of a DPS Profile
When adding a DPS profile, some State labels attributes must be updated (1). They are
(1)
FIGURE 201: SETTING ‘STATE LABELS’ ATTRIBUTES OF A DPS PROFILE

5.2.2.4 Setting ‘State treatment’ attributes of a DPS Profile
When adding a DPS profile, some State treatment attributes must be updated, for each

(1)
FIGURE 202: SETTING ‘STATE TREATMENT’ ATTRIBUTES OF A DPS PROFILE

5.2.2.5 Setting ‘Alarms’ attributes of a DPS Profile
When adding a DPS profile some Alarms attributes must be updated, for each available
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:
− Manual: users must explicitly clear the alarm.

− Automatic: no user intervention is needed to clear the alarm.
For ‘Open’ and ‘Closed’ states, extra attribute spurious is settable ((8) and (9)). This
information is only significant when the user wants to alarm a spurious DPS datapoint on a
particular event Open or Closed. In fact, the datapoint has got no state, but generates an
event. It is useful to alarm trip information of relays for instance. When setting a spurious
alarm, only the relative state must be defined as alarmed; the other states must be set to ‘not
defined alarm’.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
FIGURE 203: SETTING ‘ALARMS’ ATTRIBUTES OF A DPS PROFILE

5.2.2.6 Setting ‘Interlocking’ attributes of a DPS Profile

For each possible state (1) of a DPS linked to this profile and belonging to an interlocking
(1)
FIGURE 204: SETTING ‘INTERLOCKING’ ATTRIBUTES OF A DPS PROFILE

5.2.3 Defining an MPS profile
5.2.3.1 Adding an MPS Profile
To create an MPS profile:
• Add an MPS profile from object entry available at the wished system object level (1).
• Defines if necessary on which printers event logging of linked MPS datapoint is done,
• Defines if necessary on which printers alarm event logging of linked MPS datapoint is
(3).
(1)
FIGURE 205: ADDING AN MPS PROFILE (SAMPLE GIVEN AT MICOM C264P LEVEL)
(2)
FIGURE 206: DEFINING EVENT LOGGING PRINTER FOR MPS PROFILE
(3)
FIGURE 207: DEFINING ALARM LOGGING PRINTER FOR AN MPS PROFILE

5.2.3.2 Setting ‘General’ attributes of an MPS Profile

When adding an MPS profile, some general attributes must be updated:
1. short name and long name: only used for profile identification in SCE.
And for linked MPS datapoints:
4. SBMC state substitution value (Suppressed / Open / Closed / Jammed): significant
and visible if SBMC dependant is set to Yes.
(1)
(2)
(3)
(4)
FIGURE 208: SETTING GENERAL ATTRIBUTES OF AN MPS PROFILE

5.2.3.3 Setting ‘State labels’ attributes of an MPS Profile
When adding an MPS profile, some State labels attributes must be updated (1). They are
(1)
FIGURE 209: SETTING ‘STATE LABELS’ ATTRIBUTES OF AN MPS PROFILE

5.2.3.4 Setting ‘State treatment’ attributes of an MPS Profile

When adding an MPS profile, some State treatment attributes must be updated, for each

(1)
FIGURE 210: SETTING ‘STATE TREATMENT’ ATTRIBUTES OF AN MPS PROFILE

5.2.3.5 Setting ‘Alarms’ attributes of an MPS Profile

When adding an MPS profile some Alarms attributes must be updated, for each available
state of the linked datapoints:
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
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 211: SETTING ‘ALARMS‘ ATTRIBUTES OF AN MPS PROFILE

5.2.3.6 Setting ‘Interlocking’ attributes of an MPS Profile

For each possible state of an MPS linked to this profile and belonging to an interlocking
(1)
FIGURE 212: SETTING ‘INTERLOCKING’ ATTRIBUTES OF AN MPS PROFILE

5.2.4 Defining an MV profile

5.2.4.1 Adding an MV Profile
To create an MV profile:
• Add an MV profile from object entry available at the wished system object level (1).
• Defines if necessary on which printers event logging of linked MV datapoint is done,

• Defines if necessary on which printers alarm event logging of linked MV datapoint is

(3).
(1)
FIGURE 213: SETTING ‘INTERLOCKING’ ATTRIBUTES OF AN MPS PROFILE
(2)
FIGURE 214: DEFINING EVENT LOGGING PRINTER FOR MV PROFILE

(3)
FIGURE 215: DEFINING ALARM LOGGING PRINTER FOR MV PROFILE

5.2.4.2 Setting ‘General’ attributes of an MV Profile
When adding a MV profile, some general attributes must be updated:
And for linked MV datapoints:
3. SBMC dependant (Yes to suppressed / No).
4. unit:used for display, logging and alarm at MiCOM C264P level.
5. default format: Reserved for Substation control point usage.
(1)
(2)
(3)
(4)
(5)
FIGURE 216: SETTING GENERAL ATTRIBUTES OF A MV PROFILE

5.2.4.3 Setting ‘State labels’ attributes of an MV Profile

When adding an MV profile, some State labels (1) attributes must be updated. They are
(1)
FIGURE 217: SETTING ‘STATE LABELS’ ATTRIBUTES OF A MV PROFILE

5.2.4.4 Setting ‘State treatment’ attributes of an MV Profile
When adding an MV profile, some State treatment attributes must be updated, for each

(1)
FIGURE 218: SETTING ‘STATE TREATMENTS’ ATTRIBUTES OF A MV PROFILE

5.2.4.5 Setting ‘Alarms’ attributes of an MV Profile
When adding an MV profile some Alarms attributes must be updated, for each available
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
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 219: SETTING ‘ALARMS’ ATTRIBUTES OF A MV PROFILE

5.2.4.6 Setting ‘Interlocking’ attributes of an MV Profile
For each possible state of an MV linked to this profile and belonging to an interlocking
(1)
FIGURE 220: SETTING ‘INTERLOCKING’ ATTRIBUTES OF AN MV PROFILE

5.2.4.7 Setting ‘Mean value’ attributes of an MV Profile

When adding an MV profile, some ‘Mean value’ attributes must be updated. They are
reserved for substation control point usage.
1. computation (No / Yes).
2. reference hour (range [0, 23], step 1).
3. reference day (range [0, 31], step 1).
(1)
(2)
(3)
FIGURE 221: SETTING ‘MEAN VALUE’ ATTRIBUTES OF AN MV PROFILE

5.2.5 Defining a Counter profile

5.2.5.1 Adding a Counter Profile
To create a Counter profile:
• Add a Counter profile from object entry available at the wished system object level (1).
• Defines if necessary on which printers event logging of linked Counter datapoint is

done, via adding and filling the relation ‘has events logged on’ at profile level (2).
• Defines if necessary on which printers alarm event logging of linked Counter datapoint
is done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).
(1)
FIGURE 222: ADDING A COUNTER PROFILE (SAMPLE GIVEN AT MiCOM C264P LEVEL)
(2)
FIGURE 223: DEFINING EVENT LOGGING PRINTER FOR COUNTER PROFILE
(3)
FIGURE 224: DEFINING ALARM LOGGING PRINTER FOR COUNTER PROFILE

5.2.5.2 Setting ‘General’ attributes of a Counter Profile

When adding a Counter profile, some general attributes must be updated:
And for linked Counter datapoints:
2. SBMC dependant (Yes to suppressed / No).
3. energy of a pulse (range [-3.4E38, +3.4E38].
4. unit used for display, logging and alarm at protection level.
5. default format: Reserved for Substation control point usage.
(1)
(2)
(3)
(4)
(5)
FIGURE 225: SETTING GENERAL ATTRIBUTES OF A COUNTER PROFILE

5.2.5.3 Setting ‘State labels’ attributes of a Counter Profile
When adding a Counter profile, some ‘State labels’ attributes must be updated (1). They are
(1)
FIGURE 226: SETTING ‘STATE LABELS’ ATTRIBUTES OF A COUNTER PROFILE

5.2.5.4 Setting ‘State treatment’ attributes of a Counter Profile
When adding a Counter profile, some ‘State treatment’ attributes must be updated, for each
• OI & C264: no archive, no logging:

• OI & C264: archive, logging:
• OI & C264: archive, no logging:
• only C264: no archive, logging:
• only C264: archive, logging:
• only C264: archive, no logging:

• only OI: archive, logging:
• only OI: archive, no logging:
(1)
FIGURE 227: SETTING ‘STATE TREATMENT’ ATTRIBUTES OF A COUNTER PROFILE

5.2.5.5 Setting ‘Alarms’ attributes of a Counter Profile
When adding a Counter profile, some ‘Alarms’ attributes must be updated, for each available
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:
4. audible (No / Yes), to activate a klaxon.
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 228: SETTING ‘ALARMS’ ATTRIBUTES OF A COUNTER PROFILE

5.2.5.6 Setting ‘Mean value’ attributes of a Counter Profile
When adding a Counter profile, some ‘Mean value’ attributes must be updated (1). They are
reserved for substation control point usage.
(1)
FIGURE 229: SETTING ‘MEAN VALUE’ ATTRIBUTES OF A COUNTER PROFILE

5.2.6 Defining an SPC profile

5.2.6.1 Adding an SPC Profile
To create an SPC profile:
• Add an SPC profile from object entry available at the wished system object level (1).
• Define if necessary on which printers event logging of linked SPC datapoint is done,
• Define if necessary on which printers alarm event logging of linked SPC datapoint is
(3).
(1)
FIGURE 230: ADDING AN SPC PROFILE (SAMPLE GIVEN AT MiCOM C264P LEVEL)
(2)
FIGURE 231: DEFINING EVENT LOGGING PRINTER FOR SPC PROFILE
(3)
FIGURE 232: DEFINING ALARM LOGGING PRINTER FOR SPC PROFILE

5.2.6.2 Setting ‘General’ attributes of an SPC Profile

When adding an SPC profile, some general attributes must be updated:
And for linked SPC datapoints:
2. control mode (for details see section 5.1.2 of chapter C264P/EN FT)
Available values are:
− Direct execute
− SBO operate once
− SBO operate many
− Direct execute with SBO popup (reserved to substation control point usage),
similar to ‘Direct execute’ for MiCOM C264P
3. SBO timeout (range [0, 600 s], step 1s), significant if SBO mode is set to ‘SBO
operate once’ or ‘SBO operate many’.
4. External fault management (External fault / OK).
(1)
(2)
(3)
(4)
FIGURE 233: SETTING GENERAL ATTRIBUTES OF AN SPC PROFILE

5.2.6.3 Setting ‘Order labels’ attributes of an SPC Profile
When adding an SPC profile, some ‘Order labels’ attributes must be updated. They are used
for events and alarm management at MiCOM C264P level (logging, display) and for correct
SPC order management:
1. ‘Order off’ usage (No / Yes)
2. ‘Order on’ usage (No / Yes)
3. ‘Order off’ label
4. ‘Order on’ label
(1)
(2)
(3)
(4)
FIGURE 234: SETTING ‘ORDER LABELS’ ATTRIBUTES OF AN SPC PROFILE

5.2.6.4 Setting ‘State treatment’ attribute of an SPC Profile

When adding an SPC profile, A ‘State treatment’ attribute must be updated globally for all
available control and acknowledgement steps of the linked datapoints (1).

deduced from this attribute: for details refer to sections 5.3 – Defining MiCOM C264P local
archiving of datapoint events and 5.5 – Defining MiCOM C264P local logging of datapoint
events and alarms.
(1)
FIGURE 235: SETTING ‘STATE TREATMENT’ ATTRIBUTE OF AN SPC PROFILE

5.2.6.5 Setting ‘Alarms’ attributes of an SPC Profile
When adding a SPC profile, some ‘Alarms’ attributes must 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:
(1)
(2)
(3)
(4)
(5)
FIGURE 236: SETTING ‘ALARMS’ ATTRIBUTES OF AN SPC PROFILE

5.2.6.6 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 6.6.1 – Defining a FBD fast automation
and 6.6.6 – Defining interlocking):
The following attributes are settable:
1. ‘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.
2. ‘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.
(1)
(2)
FIGURE 237: SETTING ‘INTERLOCKING AND FBD’ ATTRIBUTES OF AN SPC PROFILE

5.2.7 Defining a DPC profile

5.2.7.1 Adding a DPC Profile
To create a DPC profile:
• Add a DPC profile from object entry available at the wished system object level (1).
• Define if necessary on which printers event logging of linked DPC datapoint is done,
• Define if necessary on which printers alarm event logging of linked DPC datapoint is
(3).
(1)
FIGURE 238: ADDING A DPC PROFILE (SAMPLE GIVEN AT MiCOM C264P LEVEL)
(2)
FIGURE 239: DEFINING EVENT LOGGING PRINTER FOR DPC PROFILE

(3)
FIGURE 240: DEFINING ALARM LOGGING PRINTER FOR DPC PROFILE

5.2.7.2 Setting ‘General’ attributes of a DPC Profile
When adding a DPC profile, some general attributes must be updated:
And for linked DPC datapoints:
2. control mode
− Direct execute
− SBO operate once
− SBO operate many
similar to ‘Direct execute’ for MiCOM C264P
3. SBO timeout (range [0, 600 s], step 1s), significant if SBO mode is set to ‘SBO
operate once’ or ‘SBO operate many’.
4. external fault management (external fault / OK).
(1)
(2)
(3)
(4)
FIGURE 241: SETTING GENERAL ATTRIBUTES OF A DPC PROFILE

5.2.7.3 Setting ‘Order labels’ attributes of a DPC Profile

‘Order labels’ attributes of a DPC profile are used for events and alarm management at
MiCOM C264P level (logging, display) and for correct SPC order management:
1. ‘Order open’ (01) usage (No / Yes)
2. ‘Order close’ 10) usage (No / Yes)
3. ‘Order open’ (01) label
4. ‘Order close’ (10) label
(1)
(2)
(3)
(4)
FIGURE 242: SETTING ‘ORDER LABELS’ ATTRIBUTES OF A DPC PROFILE

5.2.7.4 Setting ‘State treatment’ attribute of a DPC Profile
When adding a DPC profile the treatment on event attribute must be updated globally for all
available control and acknowledgement steps of the linked datapoints (1).

events and alarms.
(1)
FIGURE 243: SETTING ‘STATE TREATMENT’ ATTRIBUTE OF A DPC PROFILE

5.2.7.5 Setting ‘Alarms’ attributes of a DPC Profile

When adding a DPC profile, some ‘Alarms’ attributes must be updated, for the correct alarm
management in case of a negative acknowledgement concerning control of the linked
datapoints.
The following alarm informations are settable:
level for the relevant gravity
(1)
(2)
(3)
(4)
(5)
FIGURE 244: SETTING ‘ALARMS’ ATTRIBUTES OF A DPC PROFILE

5.2.7.6 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 6.6.1 – Defining a FBD fast automation
and 6.6.6 – Defining interlocking):
The following attributes are settable:
1. ‘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
2. ‘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
(1)
(2)
FIGURE 245: SETTING ‘INTERLOCKING AND FBD’ ATTRIBUTES OF A DPC PROFILE

5.2.8 Defining a SetPoint profile
5.2.8.1 Adding a SetPoint Profile
To create a SetPoint profile:
• Add a SetPoint profile from object entry available at the wished system object level
(1).
• Define if necessary on which printers event logging of linked SetPoint datapoint is

done, via adding and filling the relation ‘has events logged on’ at profile level (2).
• Define if necessary on which printers alarm event logging of linked SetPoint datapoint
is done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).
(1)
FIGURE 246: ADDING A SETPOINT PROFILE (SAMPLE GIVEN AT MiCOM C264P LEVEL)
(2)
FIGURE 247: DEFINING EVENT LOGGING PRINTER FOR SETPOINT PROFILE

(3)
FIGURE 248: DEFINING ALARM LOGGING PRINTER FOR SETPOINT PROFILE

5.2.8.2 Setting ‘General’ attributes of a SetPoint Profile
When adding a SetPoint profile, some general attributes must be updated:
1. short name and long name of the profile only used for profile identification in SCE
And for linked SetPoint datapoints:
2. control mode: available values are:
− Direct execute
similar to ‘Direct execute’ for protection, reserved for future use
3. unit used for display, logging and alarm at MiCOM C264P level.
(1)
(2)
(3)
FIGURE 249: SETTING GENERAL ATTRIBUTES OF A SETPOINT PROFILE

5.2.8.3 Setting ‘treatment on event’ attribute of a SetPoint Profile
When adding a SetPoint profile, the ‘treatment on event’ attribute must be updated globally
for all available control and acknowledgement steps of the linked datapoints (1).
The available values for this attribute are:

events and alarms.
(1)
FIGURE 250: SETTING ‘STATE TREATMENT’ ATTRIBUTE OF A SETPOINT PROFILE

5.2.8.4 Setting ‘Alarms’ attributes of SetPoint Profile
When adding a SetPoint profile, some ‘Alarms’ attributes must be updated, for the correct
alarm management in case of a negative acknowledgement concerning control of the linked
datapoints.
The following alarm informations are settable:
1. defined (No / Yes)
disappears within this delay
3. gravity (range [1, 5], step 1)
4. audible (No / Yes), to activate a klaxon
− Manual: users must explicitly clear the alarm ,
level for the relevant gravity
(1)
(2)
(3)
(4)
(5)
FIGURE 251: SETTING ‘ALARMS’ ATTRIBUTES OF A SETPOINT PROFILE

5.3 Defining MiCOM C264P local archiving of datapoint events

A MiCOM C264P manages only archiving of the datapoints it is server of (Refer to section
4.6.1 – Connecting MiCOM C264P to others station-bus sub-systems, for Client/Server
definition).
For MiCOM C264P, 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 (see relevant section of 5.2 – Linking a
datapoint to a profile).
5.4 Defining MiCOM C264P local archiving of datapoint alarms
A MiCOM C264P manages only archiving of the datapoints it is server of (Refer to section
definition).
Alarm archiving at MiCOM C264P level is defined globally for all the protections at Scs
object level (see section 4.1 – Setting general system configuration relevant to MiCOM
C264P - point (6)).
5.5 Defining MiCOM C264P local logging of datapoint events and alarms
A MiCOM C264P manages only logging of the datapoints it is server of (Refer to section
definition).
For MiCOM C264P, event logging is available or not for all the events appearing on a given
datapoint.
Event logging is activated as soon as the datapoint profile is linked to the local printer of the
protection via the relation ‘has events logged on’. To link a datapoint profile to a printer, see
relevant section of 5.2 – Linking a datapoint to a profile.
Alarm logging is activated as soon as the datapoint profile is linked to the local printer of the
protection via the relation ‘has alarm events logged on’. To link a datapoint profile to a
printer, see relevant section of 5.2 – Linking a datapoint to a profile.
To create a MiCOM C264P printer, see section 4.4.6 – Adding a printer.
5.6 Defining acquisition source for input 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-PACiS IEC61850 communicant IED
• (virtual) acquisition via software production:
− diagnostic and control of system components
− datapoints relevant to built-in function and user’s function
− MV or counter datapoint relevant to CT/VT board computation

5.6.1 Acquiring input datapoint via input channels
At SCE level, linking datapoint to specific channels (DI or AI channels) belonging to PACiS
protection’s DIU200, CCU200, AIU201 or AIU211 boards does input datapoint wiring.
5.6.1.1 Wiring a 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
Faulty * SELFCHECK FAULTY
To wire a SPS datapoint on a DI channel:
• 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
protection that manages a bay, refer to section 6.1.4 – Defining a Bay.
• If necessary update the relation attribute ‘inverted value’ (2), whose meaning is given
previously.
(1)
FIGURE 252: WIRING ONE SPS DATAPOINT VIA ONE DI CHANNEL
(2)
FIGURE 253: UPDATING THE WIRING OF A SPS DATAPOINT

5.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 MiCOM C264P that manages the bay are available. To define
the protection that manages a bay, refer to section 6.1.4 – Defining a Bay.
(1)
(2)
FIGURE 254: WIRING A DPS DATAPOINT VIA TWO DI CHANNELS

5.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 <i> 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 MiCOM C264P
that manages the bay, are available. To define the protection that manages a bay,
refer to section 6.1.4 – Defining a Bay.
• If a read inhibit signal exists for the MPS, add the relations ‘read inhibit wired on’ (2) at
MPS datapoint level.
(2)
(1)
FIGURE 255: WIRING A MPS DATAPOINT VIA N DI CHANNEL

5.6.1.4 Wiring MV and TPI datapoint

MV and TPI datapoint wiring is done via 1 AI channel (analogue measurement) or 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 AI channel:
• Add the relation ‘wired on’ (1) at MV or TPI datapoint level.
• Fill the relation with the relevant AI channel: when datapoint level is lower than or
equal to bay level, only AI channels from AIU boards belonging to the MiCOM C264P
• To define sensor range of the AI channel, refer to section 4.4.5 – Configuring an AI

channel.
(1)
FIGURE 256: WIRING A MV DATAPOINT OR A TPI DATAPOINT VIA ONE AI CHANNEL

To wire an MV or TPI datapoint on n DI channels (n <=64):
• Add the relations ‘bit <i> wired on’ (1) at MV or TPI datapoint level, for each available
bit channel of the MV or TPI (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 protection that
manages the bay, are available. To define the protection that manages a bay, refer to
section 6.1.4 – Defining a Bay.
• 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.
(1)
(2) (3)
FIGURE 257: WIRING MV OR TPI DATAPOINT, VIA N DI CHANNEL

5.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 MiCOM C264P
• 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.
(1) (2)
(3)
FIGURE 258: WIRING COUNTER DATAPOINT, VIA DI CHANNEL

5.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 an MPS datapoint on an IED legacy network is not available.
Depending on legacy network type, addressing information can be different.
See section 4 – Defining MICOM C264P configuration in system architecture 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 MiCOM C264P that
manages the bay, are available. To define the protection that manages a bay, refer to
(1)
FIGURE 259: 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.
5.6.3 Acquiring input datapoint via non-PACiS IEC61850 communicant IED

At SCE level, IED wiring is not described. Acquiring input datapoint issued from IEC61850
IED is done by giving it a communication address in the relay’s IEC61850 mapping. This
addressing can be seen as a virtual wiring regardless to channel wiring (implicit association
is done at IED level).
See relevant application guide for further details about IED creation and corresponding
IEC61650/IEC addressing mapping definition (nevertheless, similar IEC61650/IEC
addressing mapping is described in section 4.5.2 – C264P as a gateway directly connected
to a remote DNP3 Scada of the present guide).
To link an input datapoint to an existing IEC61850 IED address in the IED mapping:
• Add the relation ‘has for IED address’ (1) at datapoint level.
• Fill the relation with the relevant IEC61850 address.

Do not confuse:
• Give an IEC61850 address to a datapoint, still wired on a MiCOM C264P, via ‘has for
IEC address’ relation adding.
• Give an IEC address to a datapoint on an IEC IED. In that case the datapoint can not
be wired, because it is seen as produced or managed by the IEC IED.
(1)
FIGURE 260: ACQUIRING INPUT DATAPOINT VIA NON-PACIS IED

(E.G. SPS DATAPOINT)
5.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 IEC61850 PACiS system device, where system datapoints are produced
to indicate mode device, synchro device, database status,…
• Supervision of IEC61850 PACiS system device board (board status diagnostics).
• Supervision of legacy network and IED managed by PACiS MiCOM C264Ps
(communication status diagnostics).
• Supervision of redundancy between two PACiS MiCOM C264Ps (redundancy status
diagnostics).
• Supervision of logging printers managed by OI server or PACiS MiCOM C264P (printer
status diagnostics).
• Supervision of archiving managed by OI server (archiving status diagnostics).
• Facilities given by built-in electrical and grouping functions or user’s function, in PACiS
MiCOM C264Ps.
5.6.4.1 Implicit system input datapoint via system decomposition
In data modelling 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
IEC61850 diagnostics bricks.
The list of such system datapoints are given in section 4.11 – Setting system information for
components.
5.6.4.2 Implicit electrical input datapoint via built-in function
Implicit input datapoints can be embedded in built-in function creation. For details refer to the
following sections:
• 6.2 – Defining a Synchrocheck function,
• 6.3 – Defining an Auto-Recloser built-in function,
• 6.4 – Defining a Tap changer built-in function,
• 6.5 – Defining an Automatic Voltage Regulation (AVR) or Automatic Tap Change

Control (ATCC) built-in function.
Generally, these electrical datapoints are transmitted on station bus network in a specific
IEC61850 brick of built-in function.
5.6.4.3 Explicit electrical input datapoint via user function
By setting output plug, fast automation can produce real-time value for electrical input
datapoint (see section 6.6.1 – Defining a FBD fast automation).
So can slow automation when it manages electrical datapoints or owns management input
datapoints (see section 6.6.2 – Defining an ISaGRAF slow automation).
For group needs, an electrical SPS containing the group result must be created (see section
6.6.3 – Defining a group).
For SPS-DPS association, the resulting DPS is the product of the two SPS associations (see
section 6.6.5 – Producing a DPS ).
To define (open or close) interlocking equation on SPC or DPC datapoint, an extra (open or
close) SPS should be produced, whose result is interlocking equation computation (see
section 6.6.6 – Defining interlocking).
5.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 MiCOM C264P
board. Then, a specific link attribute must be filled to precise which MV computation is
concerned (power factor, power, ...).
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 (H1 Harmonic) of Phase current and voltages
• Total Active Power
• Total Reactive Power
• Frequency
• Power Factor - Cos φ

To link a MV datapoint to a CT/VT computation:
• Add the relation ‘is computed by’ (1) at 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 MiCOM C264P that
manages the bay, is available. To define the protection that manages a bay, refer to
• Update the relation attribute ‘measure type’ (2), giving the computation type.
(1)
FIGURE 261: DEFINING CT/VT COMPUTATION FOR A MV DATAPOINT

5.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-PACiS IEC61850 communicant IED
• (virtual) control via software production:
− control of system components
− datapoints relevant to built-in function and user’s function

5.7.1 Controlling output datapoint via output channels
At SCE level, linking datapoint to specific channels (DO channels) belonging to PACiS
MiCOM C264P’s DOU201 or CCU200 boards does output datapoint wiring.
5.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 DOU boards belonging to the protection
that manages the bay, are available. To define the MiCOM C264P that manages a
bay, refer to section 6.1.4 – Defining a Bay.
(1)
FIGURE 262: WIRING A SPC DATAPOINT VIA ONE DO CHANNEL

5.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 twice in case of 4 DO channels use).
• Fill the relations with the relevant DO channels: when datapoint level is lower than or
(1)
(2)
FIGURE 263: WIRING A DPC DATAPOINT VIA TWO DO CHANNEL

5.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 <i> 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
• If a read inhibit signal exists for the SetPoint (see section 5.1.12.1 – Overview of
SetPoint processing), add the relations ‘read inhibit wired on’ (2) at SetPoint datapoint
level.
• If a refresh signal exists for the SetPoint (see section 5.1.12.1 – Overview of SetPoint
processing), 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.
FIGURE 264: WIRING A SETPOINT DATAPOINT VIA N DO CHANNEL

• A Setpoint datapoint wired on DO channels of MiCOM C264P, must be digital and

have its profile attribute “SBO mode” set to "Direct Execute" or “Direct Execute with
SBO popup”
• A Setpoint datapoint wired on AO channel of MiCOM C264P, must be analogue and

have its profile attribute “SBO mode” set to "Direct Execute" only.
5.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 4 – Defining MiCOM C264P configuration in system architecture 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:
• 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 protection that
manages the bay, are available. To define the MiCOM C264P that manages a bay,
(1)
FIGURE 265: 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.
5.7.3 Controlling output datapoint via non-PACiS IEC61850 communicant IED

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 IEC61850 mapping. This
addressing can be seen as a virtual wiring regardless to channel wiring.
See relevant application guide for further details about IEC61850 IED creation and
corresponding IEC addressing mapping definition (nevertheless, similar IEC addressing
mapping is described in section 4.6.2 – Defining addressing mapping of station-bus network
of the present guide).
To link an output datapoint to an existing IED address in the IED IEC mapping:
• Add the relation ‘has for IED address’ (1) at datapoint level.
• Fill the relation with the relevant IEC address.

Do not confuse:
• Give an IEC address to a datapoint, still wired on a MiCOM C264P, via ‘has for IEC
address’ relation adding.
• Give an IEC address to a datapoint on an IEC IED. In that case the datapoint can not
be wired, because it is seen as produced or managed by the IEC IED.
(1)
FIGURE 266: ACQUIRING OUTPUT DATAPOINT VIA NON-PACIS IEC IED

5.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 IEC61850 PACiS system device, where system datapoints are

produced to control mode device, database switch.
These output system datapoints are only used by System Management Tool.
• Supervision of redundancy between two PACiS protections (redundancy controls).
• Facilities given by built-in electrical and grouping functions or user’s function, in PACiS
protections.
5.7.4.1 Implicit system output datapoint via system decomposition
In data modelling, only PACiS 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.
MiCOM C264P redundancy needs specific output typed datapoints that must be manually
added in protection’s hierarchy.
Most of system output datapoints when transmitted on station bus network are addressed in
IEC61850 diagnostics bricks.
The list of such system datapoints are given in section 4.11 – Setting system information for
components.
5.7.4.2 Implicit electrical output datapoint via built-in function
Implicit output datapoints can be embedded in built-in function creation. For details refer to
the following sections:
• 6.2 – Defining a Synchrocheck function,
• 6.3 – Defining an Auto-Recloser built-in function,
• 6.4 – Defining a Tap changer built-in function,
• 6.5 – Defining an Automatic Voltage Regulation (AVR) or Automatic Tap Change

Control (ATCC) built-in function.
Generally, these electrical datapoints are transmitted on station bus network in a specific
IEC61850 brick of built-in function.
5.7.4.3 Explicit electrical datapoint via user function
By setting output plug, fast automation can produce real-time order value for electrical output
datapoint (see section 6.6.1 – Defining a FBD fast automation).
So can slow automation when it manages electrical output datapoints or owns management
output datapoints (see section 6.6.2 – Defining an ISaGRAF slow automation).
For xPS-xPC association, an electrical output SPC or DPC linked to the SPS or DPS must
exist and sometimes be created (see section 6.6.4 – Controlling xPC ).
5.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).
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).
(1)
FIGURE 267: THE TWO TARGET DATAPOINTS OF THE SUBSTATION LEVEL

Original datapoints can be one of the following types: SPS, DPS, MPS, MV.
5.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).
5.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).
(1)
(2)
FIGURE 268: LINKING THE TARGET DATAPOINT OF THE ORIGINAL DATAPOINT

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.
(3)
(4)
FIGURE 269: SELECTING THE TARGET DATAPOINT

5.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).
(5)
(6)
(7)
FIGURE 270: 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 MiCOM
C264Ps. 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, …
• 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).
6. DEFINING MiCOM C264P CONFIGURATION IN ELECTRICAL

ARCHITECTURE
6.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-safety, i.e. can be isolated from others
bays by switchgears for maintenance and managed by only one PACiS 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 must 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 5 – Defining datapoint
(1) : Site
(2): Substation
n
(3) : Voltage level
(4) : Bay 'Feeder'
datapoints
(5): Module 'Circuit breaker'
(6) : Bay 'Transformer'
C0211ENb
FIGURE 271: ELECTRICAL TOPOLOGY DEFINITION (E.G.)

Feeder bay
Bus coupling bay
Transformer bay
Busbar bay
Bus section bay
C0212ENa
FIGURE 272: BAY SAMPLES
Switchgear
module
Q1
Circuit-breaker
module
Q0
Switchgear
module Q9
Switchgear Q8
Module (earth)
External line
module
C0213ENa
FIGURE 273: MODULE SAMPLES

6.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. At the moment, these attributes are not used.
(1)
FIGURE 274: SETTING ATTRIBUTES OF A SITE

6.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) must 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 PACiS system for the substation.
• Substation level: control uniqueness is provided by PACiS 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
5.1.10.2 – Setting ‘Dependencies’ attributes of a SPC datapoint, 5.1.11.2 – Setting
‘Dependencies’ attributes of a DPC datapoint, 5.1.12.4 – Setting ‘Dependencies’
attributes of a SetPoint datapoint.
• Bay level: control uniqueness is provided by PACiS 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 5.1.10.2 – Setting
‘Dependencies’ attributes of a SPC datapoint, 5.1.11.2 – Setting ‘Dependencies’
attributes of a DPC datapoint, 5.1.12.4 – Setting ‘Dependencies’ attributes of a
SetPoint datapoint).
(1)
(2)
FIGURE 275: SETTING ATTRIBUTES OF A SUBSTATION

Bay and substation uniqueness are managed by MiCOM C264P by synthesis of mandatory
SPS datapoints ‘Order running’, automatically added under a bay at its creation (see section
6.1.4 – Defining a Bay).
• When control uniqueness is set to substation, all protections of substation must be

IEC-61850 client of all ‘order running’ SPS datapoints defined for all the bays. So,
proper IEC-61850 configuration must be done for all protections to insure that feature.
For details about IEC-61850 configuration, refer to section 4.6 – Networking MiCOM
C264P on the station-bus network.
6.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 functions:
• Local/remote for substation (see section 6.1.2.2 – Defining Local/Remote for

substation)
• Taking Control for substation and SCDA links (see section 6.1.2.3 – Defining Taking
Control for substation and SCADA links)
For more details about datapoints and their configuration, refer to section 5 – Defining
datapoint.
(2)
(1)
FIGURE 276: ADDING GENERIC DATAPOINT TO A SUBSTATION

NOTE: A Global alarm ack SPS (1) can be added to the substation level in
order to automatically acknowledge the new alarms in the C264P and
also in the OI. The detection mode attribute of this SPS must be set
to "Permanent" or "Permanent with protection 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 acknowledment at a fixed
time by using a cyclic SPS (described in section 6.1.4.1 – Adding bay
generic datapoint).
6.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, see section 6.1.4.3 – Defining SBMC for bay).
The Local mode indicates that the substation is controlled from PACiS 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:
• SPC: 5.1.10.2 – Setting ‘Dependencies’ attributes of a SPC datapoint,
• DPC: 5.1.11.2 – Setting ‘Dependencies’ attributes of a DPC datapoint,
• SetPoint: 5.1.12.4 – Setting ‘Dependencies’ attributes of a SetPoint datapoint.

In Local or Remote mode the information acquired by MiCOM C264Ps and IEDs are always
sent to RCP and PACiS 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 IEC61850 clients (i.e. Operator Interface, gateway, protections) will
automatically forced the substation mode to “Forced Local” or “Forced Remote” if it takes the
UNKNOWN state (due for example to the loss of communication between the protection
which manages the substation mode and the IEC61850 clients).
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 5 – Defining datapoint),
• if necessary, do not forget to link via ‘has for feedback’ relation, the control of the
Local/remote with the Local/remote status datapoint.
(2)
(1)
FIGURE 277: DEFINING LOCAL/REMOTE FOR SUBSTATION


Hereafter, the term "wired" means that the datapoint must be wired on digital channel(s) of a
MiCOM C264P.
• 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 mandatory.
• 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 Substation, a "DPC" or "SPC" datapoint has its attribute "Substation mode
dependency" set to "Yes", then the Substation "Local/remote DPS" datapoint must be
present.
• If the two datapoints "Local/remote DPS" and "Loc/rem ctrl DPC" are present, they
must have the same Server device.
• "Loc/rem ctrl DPC" datapoint must have its profile attribute “SBO mode” set to "Direct
Execute" or “Direct Execute with SBO popup”.
6.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 5 – Defining datapoint).
• add the relation ‘is taken control of’ at ‘Taking status’ datapoint level (3), and fill it with
the relevant given SCADA network.
• do not forget to link via ‘has for feedback’ relation, the control with the status
datapoint.
(2)
(1)
(1)
FIGURE 278: 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".
• 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".
6.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.
FBD user function
ISAGRAF user function
C0214ENb
FIGURE 279: ADDING USER FUNCTION TO SUBSTATION

6.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 280: ADDING A VOLTAGE LEVEL

When adding a voltage level, some general attributes must be updated:
2. nominal value in Kv.
3. 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. For
details about ATCC configuration and this attribute, refer to section 6.5 – Defining an
Automatic Voltage Regulation (AVR) or Automatic Tap Change Control (ATCC) built-in
function.
(1)
(2)
(3)
FIGURE 281: SETTING GENERAL ATTRIBUTES OF A MV DATAPOINT

6.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 5 – Defining
datapoint.
FIGURE 282: ADDING VOLTAGE LEVEL GENERIC DATAPOINT

6.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.
FBD user function
C0214ENb
FIGURE 283: ADDING A USER FUNCTION TO VOLTAGE LEVEL

6.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 must be
arbitrary located on one of the both.
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).
(1)
FIGURE 284: ADDING A TYPED BAY
(2)
FIGURE 285: DEFINING PROTECTION MANAGING A BAY

When adding a bay, some general attributes must be updated:
1. short name and long name of the bay used for logging, alarms ...
2. control uniqueness used for output datapoints under the bay.
− None: no control uniqueness is provided by PACiS system for output datapoints

under the bay.
− See substation definition: control uniqueness is inherited from attribute ‘default

uniqueness’ at substation level (see section 6.1.2 – Defining a Substation).
(1)
(2)
FIGURE 286: SETTING GENERAL ATTRIBUTES OF A BAY

(SAMPLE GIVEN FOR BAY TYPE ‘FEEDER’)
When adding a bay, a mandatory SPS datapoint ‘order running’ is automatically created at
bay level. This datapoint allows PACiS 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 protections of substation must be

IEC61850 client of all ‘order running’ SPS datapoints defined for all the bays. So,
proper IEC61850 configuration must be done for all MiCOM C264Ps to insure that
feature. For details about IEC61850 configuration, refer to section 4.6 – Networking
MiCOM C264P on the station-bus network.
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. For details about ATCC configuration and
this attribute, refer to section 6.5 – Defining an Automatic Voltage Regulation (AVR) or
Automatic Tap Change Control (ATCC) built-in function,
• Generic bay: no sub-component constraint. Used for general usage outside the scope
of other previous typed bays.
6.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 bay functions:
• Local/remote for bay (see section 6.1.4.2 – Defining Local/Remote for bay)
• SBMC for bay (see section 6.1.4.3 – Defining SBMC for bay)
• Group computation (see section 6.6.3 – Defining a group)

datapoint.
(1)
(2)
FIGURE 287: ADDING GENERIC DATAPOINT TO A BAY

6.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 MiCOM C264P 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:

In Local or Remote mode, the information issued from the bay is always sent to SCP and
RCP.
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
• if necessary, do not forget to link via ‘has for feedback’ relation, the control of the
Local/remote with the Local/remote status datapoint.
(2)
(1)
FIGURE 288: DEFINING LOCAL/REMOTE FOR BAY


Hereafter, the term "wired" means that the datapoint must be wired on digital channel(s) of a
MiCOM C264P.
• 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
Execute" or “Direct Execute with SBO popup”.
If the "GHU200" board of a MiCOM C264P has its attribute "HMI type" set to the "Simple"
value, then the "Local/remote DPS" datapoints of the bays managed by this protection must
be all be "Wired" or all "System".
6.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 6.1.4.2 –
Defining Local/Remote for bay). 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:

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 dependant 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

DPS SUPPRESSED, OPEN, CLOSE, JAMMED
MPS SUPPRESSED, UNDEFINED
MV, TPI and Counter SUPPRESSED
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,
• do not forget to link via ‘has for feedback’ relation, the control of the SBMC with the
SBMC status datapoint.
(2)
(1)
FIGURE 289: DEFINING SBMC FOR BAY

• 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.
6.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.
FBD user function
C0216ENb
FIGURE 290: ADDING USER FUNCTION TO BAY

6.1.5 Defining Module

This 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)
(1)
FIGURE 291: ADDING EXPLICITLY A TYPED MODULE

When adding a module, some general attributes must be updated:
1. short name and long name of the module used for logging, alarms ...
2. ‘node reference’, used for electrical topology definition for ATCC function. For details
about ATCC configuration and this attribute, refer to section 6.5 – Defining an
Automatic Voltage Regulation (AVR) or Automatic Tap Change Control (ATCC) built-in
function.
(1)
(2)
FIGURE 292: 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). For details about ATCC configuration and this attribute, refer to
section 6.5 – Defining an Automatic Voltage Regulation (AVR) or Automatic Tap
Change Control (ATCC) built-in function.
− Not lockable module.
• Convertor, generator, motor:
− Not lockable module.
• Transformer:
− Lockable module.
− Supports Tap changer built-in function.
− Supports ATCC function needs (when available). For details about ATCC
configuration and this attribute, refer to section 6.5 – Defining an Automatic
Voltage Regulation (AVR) or Automatic Tap Change Control (ATCC) built-in
function.
• Circuit-breaker module:
− Supports synchrocheck (when available) and autorecloser built-in functions.
− May support withdrawing if it exists.
• Switchgear module
− May support withdrawing if it exists.
• External line:
− Only support SPS and DPS attribution.
• Generic module:
− Used for general usage outside the scope of other previous typed modules.
6.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 6.6.3 – Defining a group).
• Locking module (see section 6.1.5.3 – Defining a lockable module).
• Specific features and configuration of typed modules (see following sections).

datapoint.
FIGURE 293: ADDING A MODULE GENERIC DATAPOINT

(E.G. FOR GENERATOR MODULE)
6.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
Module does not support ISAGRAF function.
FBD user
FIGURE 294: A USER FUNCTION TO A MODULE (E.G. FOR GENERATOR MODULE)

6.1.5.3 Defining a lockable module
According to PACiS 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 MiCOM C264P level (see section 5.1.9 – Overview of
control sequence processing).
At SCE level, only 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 5 – Defining datapoint),
• Add the pre-defined SPC datapoint ‘Lock control SPC’ at module level (2) and
configure it (see section 5 – Defining datapoint),
• 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 5.1.10.3 – Defining a SPC
feedback).
(2)
(1)
FIGURE 295: DEFINING A LOCKABLE MODULE

Lock SPS and Lock control SPC are datapoints fed and controlled directly by the MiCON
C264P that manages the module. They can not be wired.
• For “Lock control SPC“, the feedback to “Lock SPS“ is mandatory

6.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 5 – Defining datapoint)

Withdraw information is useful for bay mimic animation at MiCOM C264P LCD level. For
more details see section 7.3 – Defining a MiCOM C264P bay mimic.
(1)
FIGURE 296: DEFINING A WITHDRAWABLE MODULE

(E.G. FOR CIRCUIT BREAKER)
6.1.5.5 Defining a circuit-breaker

This section deals with general circuit-breaker features and available associated input and
output datapoints at MiCOM C264P level.
General module features described in section 6.1.5 – Defining Module are applicable to
circuit-breaker module and not reviewed here.
When adding a circuit-breaker module, the following specific general attribute must be
updated:
1. 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
(1)
obsolete
C0218ENb
FIGURE 297: SETTING CIRCUIT-BREAKER TYPE

The following tables give inputs and outputs circuit breaker’s features controlled by the
MiCOM C264P 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 6.1.4 – Defining a
Bay), the mandatory pre-defined DPS datapoint ‘computed switch position’ (31) is
automatically created.
To configure correctly a circuit-breaker module:
• Add the relevant datapoints, relatively to the following tables,
• do not forget to link via ‘has for feedback’ relation, the control(s) (1), (13) or (14) of the
breaker with the computed switch position (31) datapoint.
Triple phase circuit-breaker

OUTPUTS CB TYPE A OUTPUTS CB TYPE B (iv) INPUTS CB ALL TYPES
DEVICE (1) DPC control for (11) SPC control for open of (10) DPS or (30) SPS
open/close of device device physical position of the device
CONTROL
(1 phase)
(10) SPC control for close of
device (24) SPS (optional) phase not
together information
(31) system DPS the
feedback of the control (i)
DEVICE (14) SPC (optional) control of (14) SPC (optional) control of (28) SPS (optional) device
device selection device selection selection position information
SELECTION
(HARDWARE)
Single phase circuit-breaker

OUTPUTS CB TYPE A OUTPUTS CB TYPE B (iv) INPUTS CB ALL TYPES
DEVICE (1) DPC control for (2) DPC or (16) SPC control (25) SPS or (7) DPS physical
open/close of device for open phase A position of phase A
CONTROL
(3) DPC or (17) SPC control (26) SPS or (8) DPS physical
for open phase B (pulse) position of phase B
(4) DPC or (18) SPC control (27) SPS or (9) DPS physical
for open phase C position of phase C
(1) DPC control for close of (24) system SPS phase not
device together information (ii)
(31) system DPS: the
feedback of the control (iii)
DEVICE (14) SPC (optional) control of (14) SPC (optional) control of (28) SPS (optional) device
device selection device selection selection position information
SELECTION
(HARDWARE)
(i) The computed double signal is equal to the physical status if the phase not together
(ii) The computed “phases not together” is equal to “false” if all phases are in the same
(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 IEC61850 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
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
(20)
(21)
(22)
(23)
(24)
(25)
(26) (31)
(27)
(28)
(29)
(30)
FIGURE 298: 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 (30), phase not together
information (24) 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.
- the datapoints of the two sets (3) and (4) 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:
- none of the datapoints 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”
Control sequence of non-synchronised circuit breakers
Circuit breakers devices are managed in “direct execute mode” and in “SBO once mode”.
Refer to the generic description in section 5.1.9 – Overview of control sequence processing.
Control sequence of synchronised circuit breakers
Refer to section 6.2 – Defining a Synchrocheck function.
6.1.5.6 Defining a switchgear
This section deals with general switchgear features and available associated input and
output datapoints at MiCON C264P level.
switchgear module and not reviewed here.
When adding a switchgear module, the following specific general attribute must be updated:
1. Switchgear type:
− Busbar disconnector
− Disconnector
− Bypass disconnector
− Transfer busbar disconnector
− Earth switch
(1)
obsolete
C0219ENb
FIGURE 299: SETTING SWITCHGEAR TYPE

The following tables give inputs and outputs switchgear’s features controlled by the MiCOM
C264P. For each datapoint its SCE identification is given by a number, referenced in the
following figure.
To configure correctly a switchgear module:
• do not forget to 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 (1) DPS or (5) SPS physical
open/close of device position of the device (1
CONTROL
phase) (v)
DEVICE (2) SPC (optional) control of (4) SPS (optional) device

device selection selection position information
SELECTION
(HARDWARE)
(1)
(2)
(3)
(4)
(5)
FIGURE 300: AVAILABLE PRE-DEFINED DATAPOINTS FOR SWITCHGEAR

Control sequence of switchgears
Switchgear devices are managed in “direct execute mode” and in “SBO once mode”. Refer
to the generic description in section 5.1.9 – Overview of control sequence processing.
6.1.5.7 Defining a transformer
This section deals with general transformer features and available associated input and
output datapoints at MiCOM C264P level.
transformer module and not reviewed here.
When adding implicitly a transformer module via transformer bay creation (refer to 6.1.4 –
Defining a Bay), the following general attribute must be updated:
1. 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, (winding 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).
2. power value (range [1 to 300 MVA), useful for ATCC regulation
(refer to section 6.5 – Defining an Automatic Voltage Regulation (AVR) or Automatic
Tap Change Control (ATCC) built-in function).
3. 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 (refer to section 6.5 – Defining an Automatic
Voltage Regulation (AVR) or Automatic Tap Change Control (ATCC) built-in function).
(1)
(2)
(3)
FIGURE 301: SETTING TRANSFORMER TYPE

Transformer is used for coupling two voltage levels. To respect SCE data modelling
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
(1)
FIGURE 302: COMPLETING PRIMARY/SECONDARY OF TRANSFORMER

When adding a transformer, some optional datapoints can be created at module level and
must be configured (see section 5 – Defining datapoint):
1. MCB position DPS: used for AVR function (see section 6.5 – Defining an Automatic
Voltage Regulation (AVR) or Automatic Tap Change Control (ATCC) built-in function),
to give Mini Circuit-Breaker position of associated tap-changer, via DPS datapoint.
2. MCB position SPS: used for AVR function (see section 6.5 – Defining an Automatic
Voltage Regulation (AVR) or Automatic Tap Change Control (ATCC) built-in function),
to give Mini Circuit-Breaker position of associated tap-changer, via SPS datapoint.
(1)
(2)
FIGURE 303: 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 6.4 – Defining a Tap changer built-in function.
6.2 Defining a Synchrocheck function

NOTE: This function is not available on this release of MiCOM C264P –
Feeder Protection application.
6.3 Defining an Auto-Recloser built-in function
6.3.1 Auto-Recloser behaviour
The Auto–Recloser built-in function is described in section 6.1.1 of chapter C264P/EN FT.
6.3.2 Creating an auto-recloser (AR type 1) function
The addition of an auto-recloser (AR type 1) is done via the “Objects entry” window at bay
Only following typed bays allows auto-recloser creation:
• Busbar,
• Bus coupler,
• Bus section,
• Feeder,
• Transformer,
• Generic bay.
FIGURE 304: ADDING AN AUTO-RECLOSER (TYPE 1) AT BAY LEVEL

Once added, auto-recloser general features must be set at SCE level:
1. Fill the relation ‘is auto-recloser of’, giving which circuit-breaker module is concerned
by the function.
2. short name and long name of the auto-recloser used for logging, alarms ...
3. 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.
4. 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
phase.
5. unlocking way (Not used / Reinitialisation / Manual close / Both ways). For details
refer to previous description of ‘lock of auto-recloser’ in section 6.3.1 – Auto-Recloser
behaviour.
6. 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’.
7. 1st period monophased (range [100 ms, 5 s], step 10 ms): timer of the first single-
phase cycle.
8. 1st period triphased (range [1 s, 60 s], step 10 ms): timer of the first 3-phases cycle.
9. 2nd period triphased (range [1 s, 3600 s], step 1 s): timer of the second 3-phases
cycle.
10. 3rd period triphased (range [1 s, 3600 s], step 1 s): timer of the third 3-phases cycle.
11. 4th period triphased (range [1 s, 3600 s] step 1 s): timer of the fourth 3-phases cycle.
12. reclaim delay (range [1 s, 600 s], step 1 s): corresponds to ‘reclaimc recovering timer’
previously described in ‘launch recovering timer’ of section 6.3.1 – Auto-Recloser
behaviour.
13. unlock delay (range [1 s, 600 s], step 1 s): corresponds to ‘reclaimml recovering
timer’ previously described in ‘lock of auto-recloser’ of section 6.3.1 – Auto-Recloser
behaviour.
14. 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 6.3.1 – Auto-
Recloser behaviour.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
obsolete (12)
(13)
)
(14)
FIGURE 305: SETTING AUTO-RECLOSER (AR TYPE 1) 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 behaviour, when adding an auto-recloser, some mandatory
datapoints are automatically created at function level and must be configured (see section
5 – Defining datapoint):
1. 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
− State2: failure due to interlocking function
− State3: no failure
2. 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

3. Force trip 3 P: is a SPC, used during a 3 phase cycle as mentioned in ‘Waiting CB
opening’ in section 6.3.1 – Auto-Recloser behaviour
4. on/off: is a status DPS, corresponding to in / out of service status of the auto-recloser
5. Trip 3 phases: is a SPS, giving information 3-phase trip provided by a relay
(1)
(2)
(3)
(4)
(5)
FIGURE 306: AUTO-RECLOSER (AR TYPE 1) MANDATORY DATAPOINTS

To assume previous described behaviour, when adding an auto-recloser, some optional

datapoints can be created at function level and must be configured (see section 5 – Defining
datapoint):
1. blocking SPS: corresponds to the ‘AR_BLOCKING’ BI described in section 6.3.1 –
Auto-Recloser behaviour
2. lock/reinit: is a SPS used to lock / unlock the auto-recloser via SPS. Corresponds to
the ‘AR_LOCK’ signal described in section 6.3.1 – Auto-Recloser behaviour
3. Trip PhA: is a SPS corresponding to trip status for pole A
4. Trip PhB: is a SPS corresponding to trip status for pole B
5. Trip PhC: is a SPS corresponding to trip status for pole C
6. lock/reinit SPC: Signal to lock/unlock the auto-recloser via SPC. Corresponds to the
‘AR_LOCK’ signal described in section 6.3.1 – Auto-Recloser behaviour
7. on/off ctrl DPC: to control in/out of service of the auto-recloser via DPC
8. on/off ctrl DPS: to control in/out of service of the auto-recloser via DPS
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 307: AUTO-RECLOSER (AR TYPE 1) 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 5 – Defining datapoint):
1. CB Healthy: corresponds to the ‘CB HEALTHY’ BI described in
section 6.3.1 – Auto-Recloser behaviour
(1)
FIGURE 308: AVAILABLE CB HEALTHY PRE-DEFINED DATAPOINTS FOR CIRCUIT-BREAKER

6.3.3 Creating an auto-recloser (AR type 2) function
The addition of an auto-recloser (AR type 2) is done via the “Objects entry” window at bay
Only following typed bays allows auto-recloser creation:
• Busbar,
• Bus coupler,
• Bus section,
• Feeder,
• Transformer,
• Generic bay.
FIGURE 309: ADDING AN AUTO-RECLOSER (TYPE 2) AT BAY LEVEL

Once added, auto-recloser general features must be set at SCE level:

1. Fill the relation ‘is auto-recloser of’, giving which circuit-breaker module is concerned
by the function.
2. short name and long name of the auto-recloser used for logging, alarms ...
3. Initial state (On / Off): corresponding to the initial state of the recloser (active = On).
4. Nbr of fast cycle for earth fault (0 / 1): corresponding to the number of cycle shots
required for fast cycle for earth fault. 0 = no action on autorecloser.
5. Nbr of slow cycle for earth fault (0 / 1 / 2): corresponding to the number of cycle
shots required for slow cycle for earth fault. 0 = no action on autorecloser. If the fault is
present at the end of the first cycle and if 2 is selected, a second autoreclose cycle is
performed.
6. Nbr of fast cycle for phase fault (0 / 1): corresponding to the number of cycle shots
required for fast cycle for phase fault. 0 = no action on autorecloser.
7. Nbr of slow cycle for phase fault (0 / 1 / 2): corresponding to the number of cycle
shots required for slow cycle for phase fault. 0 = no action on autorecloser. If the fault
is present at the end of the first cycle and if 2 is selected, a second autoreclose cycle
is performed.
8. Reclaim time fast cycle (range [10 s, 15 s], step 1 s):
Timer corresponding to ‘reclaimc recovering timer’ for fast cycle. The reclaim time
starts when the CB has closed. If the circuit breaker does not trip again, the
autoreclose function resets at the end of the reclaim time (the “Autoreclose in
progress” signal is present during the complete reclose cycles from protection initiation
to the end of the reclaim time or lockout; see section 6.1.1 of chapter C264P/EN FT).
9. Reclaim time slow cycle (range [3 s, 10 s], step 1 s):
Timer corresponding to ‘reclaimc recovering timer’ for slow cycle. The reclaim time
10. Reclaim time manual close (range [10 , 20 s], step 1 s):
Timer corresponding to ‘reclaimc recovering timer’ for fast cycle. The reclaim time
11. Timer cycle fast earth (range [100 ms, 500 ms], step 1 ms)
corresponding to the ‘launch cycle time’ for fast cycle for earth fault. This timer starts
when the CB has tripped and is adjusted to start autoreclose when CB is closed.
12. Timer cycle slow1 earth (range [10 s, 30 s], step 1 s)
corresponding to the ‘launch cycle time’ for the first slow cycle for earth fault. This
timer starts when the CB has tripped and is adjusted to start autoreclose when CB is
closed.
13. Timer cycle slow2 earth (range [10 s, 30s], step 1 s)
Timer corresponding to the ‘launch cycle time’ for the second slow cycle for earth fault.
This timer starts when the CB has tripped and is adjusted to start autoreclose when
CB is closed.
14. Timer cycle fast phase (range 100 ms, 500 ms], step 1 ms)
Timer corresponding to the ‘launch cycle time’ for fast cycle for phase fault. This timer
starts when the CB has tripped and is adjusted to start autoreclose when CB is closed.
15. Timer cycle slow1 phase (range[ 10 s, 30 s], step 1 s)
Timer corresponding to the ‘launch cycle time’ for the first cycle for fast cycle for fast
fault. This timer starts when the CB has tripped and is adjusted to start autoreclose
when CB is closed.
16. Timer cycle slow2 phase(range [10 s, 30 s], step 1 s)

Timer corresponding to the ‘launch cycle time’ for the second cycle for fast cycle for
fast fault. This timer starts when the CB has tripped and is adjusted to start
autoreclose when CB is closed.
17. Voltage presence delay (range [1 s, 20 s], step 1 s).
18. Shifting reclose delay (range [1 s, 30 s], step 1 s).
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
FIGURE 310: SETTING AUTO-RECLOSER (AR TYPE 2) FEATURES

When adding an auto-recloser, some mandatory datapoints are automatically created at
input or output level and must be configured (see section 5 – Defining datapoint).
Inputs (datapoints received):

1. CTRL.CB.CLOSE and CTRL.CB.OPEN SPS indicate the circuit breaker status (close
or open). To modify SPS attributes, see section 5.1.2 – Defining an SPS datapoint.
2. LINE.LIVE SPS indicates line status (live or dead). To modify SPS attributes, see
section 5.1.2 – Defining an SPS datapoint.
3. MES.ARPCCN SPC is a specific signal used with Sx7x (PCCN) products (Autoreclose
from PCCN).
4. REC.REQ.DBL, REC.REQ.GND and REC.REQ.PHA SPS indicate a reclose request
(respectively phase and earth request, ground request or phase request). To modify
SPS attributes, see section 5.1.2 – Defining an SPS datapoint.
5. RECLOSE.SHIFT SPS indicates a change of state of the recloser. To modify SPS
attributes, see section 5.1.2 – Defining an SPS datapoint.
6. RRL.OFF.CTRL and RRL.ON.CTRL SPS corresponding to the local autorecloser
(RRL) control state (ON or OFF). To modify SPS attributes, see section 5.1.2 –
Defining an SPS datapoint.
Outputs (datapoints transmitted):
7. AR.ON.OFF DPS corresponding to the autoreclose command. To modify SPS
attributes, see section 5.1.3 – Defining a DPS datapoint.
8. ARPCCN.RESUL and ARPCCN.STATE MPS are specific signals used with Sx7x
(PCCN) products (respectively PCCN autoreclose result and state).
9. CB.CLOSE.RRL SPS corresponding to the circuit breaker autoreclose (RRL)
command. To modify SPS attributes, see section 5.1.3 – Defining a DPS datapoint.
10. FAST.EARTH, FAST.EARTH.DONE and FAST.EARTH.FAIL SPS, corresponding to
the first fast cycle for earth fault (respectively ‘autoreclose in progress and waiting the
end of timer’, ‘cycle terminated (end of timer)’ and ‘fault present at the end of the
cycle’) outputs. To modify SPS attributes, see section 5.1.2 – Defining an SPS
datapoint.
11. FAST.PHASE, FAST.PHASE.DONE and FAST.PHASE.FAIL SPS, corresponding to
the first fast cycle for phase fault (respectively ‘autoreclose in progress and waiting the
end of timer’, ‘cycle terminated (end of timer)’ and ‘fault present at the end of the
cycle’) outputs. To modify SPS attributes, see section 5.1.2 – Defining an SPS
datapoint.
12. INSTANT.EARTH and INSTANT.PHASE SPS corresponding to instantaneous earth
and instantaneous phase.
13. RECLOSE.IN.PRO1 SPS corresponding to an autoreclose in progress (signal present
during the complete reclose cycles from protection initiation to the end of the reclaim
time or lockout). To modify SPS attributes, see section 5.1.2 – Defining an SPS
datapoint.
14. RRL.DEF.OPEN SPS corresponding to the end of the autoreclose cycle (end of
reclaim time and lockput). To modify SPS attributes, see section 5.1.2 – Defining an
SPS datapoint.
15. RRL.STDBY SPS corresponding to an autorecloser standby signal. To modify SPS
16. SLOW1.EARTH, SLOW1.EARTH.DONE and SLOW1.EARTH.FAIL SPS,
corresponding to the first slow cycle for earth fault (respectively ‘autoreclose in
progress and waiting the end of timer’, ‘cycle terminated (end of timer)’ and ‘fault
present at the end of the cycle’). To modify SPS attributes, see section 5.1.2 –
17. SLOW1.PHASE, SLOW1.PHASE.DONE and SLOW1.PHASE.FAIL, SPS,

corresponding to the first slow cycle for phase fault (respectively ‘autoreclose in
18. SLOW2.EARTH, SLOW2.EARTH.DONE and SLOW2.EARTH.FAIL SPS,
corresponding to the second slow cycle for earth fault (respectively ‘autoreclose in
19. SLOW2.PHASE, SLOW2.PHASE.DONE and SLOW2.PHASE.FAIL SPS,
corresponding to the second slow cycle for phase fault (respectively ‘autoreclose in
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 311: AUTO-RECLOSER (AR TYPE 2) MANDATORY DATAPOINTS (1/2)

(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
FIGURE 312: AUTO-RECLOSER (AR TYPE 2) MANDATORY DATAPOINTS (2/2)

Update the relations and the links of the datapoints to point to a specific existing profile. See
section 5.2 – Linking a datapoint to a profile, for details about profile definition and setting.
6.4 Defining a Tap changer built-in function

6.4.1 Tap changer behaviour
The control sequence of a transformer is described in section 5.6 of chapter C264P/EN 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
5.1.9 – Overview of control sequence processing).
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:
1. reset confirmation delay (range [0 s, 120 s], step 100 ms]: this delay corresponds to
time-out TR given in section 4.1.2.1 – Persistence filtering of chapter C264P/EN FT.
2. set confirmation delay (range [0 s, 120 s], step 100 ms]: this delay corresponds to
time-out TS given in section 4.1.2.1 – Persistence filtering of chapter C264P/EN FT.
3. start confirmation delay (range [1 s, 60 s], step 100 ms): the TCIP information must
appear before the time-out of this delay.
4. stop confirmation delay (range [1 s, 60 s], step 100 ms): the TCIP information must
disappear before the time-out of this delay.
(1)
(2)
(3)
(4)
FIGURE 313: SETTING TCIP GENERAL ATTRIBUTES OF A TCIP

TPI feature:
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 section 5.6.2.1 of chapter C264P/EN FT.
Control of a transformer without TCIP
Suppression, Forcing or Substitution of the TPI
6.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).
(1)
FIGURE 314: ADDING A TAP CHANGER BUILT-IN FUNCTION TO TRANSFORMER

When adding a tap changer function, the following general attributes must be updated:
1. short name and long name of the tap changer used for logging, alarms ...
2. minimal usable position (range [1, 64], step 1).
3. maximal usable position (range [1, 64], step 1): must be greater than attribute (2).
4. 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 acknowledgement is sent for tap control.
(1)
(2)
(3)
(4)
obsolete
C0244ENb
FIGURE 315: 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 MiCOM
C264P. 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:
• configure them (see section 5 – Defining datapoint).
Tap changer for transformer

OUTPUTS INPUTS
DEVICE (2) DPC raise/lower (8) TPI value

CONTROL (1) DPC (optional) goto (7) SPS (optional) tap change
min/max in progress
DEVICE (4) SPC (optional) transformer (i) SPS (optional) selection

selection position information
SELECTION
(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 ISAGRAPH 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 taken into account by the tap changer built-in
6. Lower position: this SPS is not taken into account by the tap changer built-in
7. Tap in progress: this SPS is taken into account by the tap changer built-in function.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 316: AVAILABLE PRE-DEFINED DATAPOINTS FOR TAP CHANGER

• "Raise/lower DPC" datapoint must have its profile attribute “SBO mode” set to "SBO
Operate Many".
6.4.3 Controlling xPC by xPS change of state

For specific needs, some SPS or DPS can acts on SPC or DPC. This relation is called xPS-
xPC association. Such an acted xPC need a channel for wiring. It can be a xPC used for
automation management for instance.
The link defines for each state of the xPS which order must be sent.
− Add the relation ‘controls on state change’ (1) 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 or DPC (2).
− Set the relation attributes (3) giving for each state of the xPS, the order to send: None,
Open (resp. Off) or Close (resp. On) for DPC (resp. SPC).
(1)
(2)
(3)
FIGURE 317: CONTROLLING XPC THROUGH XPS (E.G.)

6.5 Defining an Automatic Voltage Regulation (AVR) or Automatic Tap Change Control
(ATCC) built-in function
NOTE: This function is not available on the MiCOM C264P – feeder
Protection application.
6.6 Defining an electrical automation/regulation by user function
PACiS 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 can not be less than 50ms.
• Using extended logical function modelling (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
MiCOM C264P it runs.
Extra solutions for simpler needs exist at configuration level (they could be seen as
restriction of particular FBD functions):
• Group modelling: 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 SPS.
• 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.
6.6.1 Defining a FBD fast automation
To define a FBD fast automation, the three following steps must be done:
• FBD interface definition at SCE level:
− FBD function ‘header’ creation.

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

6.6.1.1 Creating a 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 6.1 – Defining an
electrical topology.
FIGURE 318: ADDING A FBD FAST AUTOMATION (E.G. FOR FEEDER BAY LEVEL)
Once added, FBD fast automation features must be set at SCE level:
1. Fill the relation ‘runs on’, giving which MiCOM C264P PLC will manage the
automation. This relation is automatically filled by SCE if FBD automation is located
under a bay whose MiCOM C264P manager has ever been entered (for details about
protection manager of a bay refer to section 6.1.4 – Defining a Bay).
2. short name and long name of the fast automation used for internal SCE
identification.
(1)
(2)
FIGURE 319: SETTING FBD FAST AUTOMATION FEATURES

6.6.1.2 Creating FBD input plug (header definition)

The addition of a FBD input plug is done via the “Objects entry” window at the FBD
automation level by clicking on mouse’s right button.
FIGURE 320: ADDING A FBD INPUT PLUG

Once added, FBD input plug features must be set at SCE level:
1. short name and long name of the fast automation used for identification in FDB
editor
(1)
FIGURE 321: SETTING GENERAL FBD INPUT ATTRIBUTES

6.6.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
FIGURE 322: ADDING A FBD OUTPUT PLUG

Once added, FBD output plug features must be set at SCE level:
1. short name and long name: used for identification in FDB editor
(1)
FIGURE 323: SETTING FBD OUTPUT PLUG ATTRIBUTES

6.6.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).
(1)
FIGURE 324: LAUNCHING FBD EDITOR

Once launched, FBD editor allows diagram edition of the automation. For details about FBD
user manual refer to <the PACiS-SCE Documentation>.
FIGURE 325: USING FBD EDITOR

6.6.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
(1)
FIGURE 326: 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
(1)
FIGURE 327: 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 must be ≤ 4
- the count of relations towards SPS datapoints must 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
- 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".
6.6.2 Defining an ISaGRAF slow automation

A "DPC" or "SPC" datapoint can be linked to an Input plug of a 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"
Slow automation modelling is articulated around 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, the three following steps must be done:
• interface definition of the slow automation at SCE level:
− slow automation ‘header’ creation.
− if required, creation of datapoints at slow automation level, used for the function
management.
− creation of the client links for the slow automation.
− creation of the server links for the slow automation.
• slow automation body definition via launching at SCE level the ISaGRAF editor
(contextual menu on the slow automation interface object) and using available
languages and previously client/server defined links.
• Effective client/server links entering to existing datapoints.

6.6.2.1 Creating an ISaGRAF slow automation (header definition)

The addition of an ISaGRAF slow automation is done via the “Objects entry” window at any
level of the electrical topology (except Site and module) by clicking on mouse’s right button.
FIGURE 328: ADDING AN ISAGRAF SLOW AUTOMATION AUTOMATION

(E.G. FOR FEEDER BAY LEVEL)
Once added, ISaGRAF slow automation features must be set at SCE level:
1. Fill the relation ‘runs on’, giving which protection PLC will manage the automation.
This relation is automatically filled by SCE if slow automation is located under a bay
whose protection manager has ever been entered (for details about protection
manager of a bay refer to section 6.1.4 – Defining a Bay).
2. short name and long name of the slow automation used for logging and alarm.
(1)
(2)
FIGURE 329: SETTING ISAGRAF SLOW AUTOMATION FEATURES

6.6.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
datapoint.
FIGURE 330: ADDING DATAPOINTS TO SLOW AUTOMATION

Slow automation datapoint is integrally produced or managed by the slow automation and
subsequently by ISaGRAF. It can not be linked to another acquisition or control source and
the ISaGRAF project must update/run its value changes or controls.
Slow automation input datapoints are stored in a non-volatile memory at MiCOM C264P
level to restart on their last known values in case of protection reboot.
6.6.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 331: ADDING AN ISAGRAF CLIENT LINK

6.6.2.4 Linking a datapoint to an ISAGRAF client link

To link a datapoint to an ISAGRAF client link the relation 'is client of' must be defined. For
that double click this relation (1). 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 (2)
then click the Ok button. (In the example given hereafter the link has be done with the
VoltageLevel SPS datapoint). The relation is then displayed as 'defined' (3).
(1)
(2)
(3)
FIGURE 332: LINKING A DATAPOINT TO AN ISAGRAF CLIENT LINK

6.6.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 concanetating 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.
(4)
FIGURE 333: DEFINING ISAGRAF IO PREFIX FOR AN INPUT

• The first character must be a letter
• The following characters must be either a letter in upper case, either a digit or an
underscore
• The maximum length is 80 characters

6.6.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 334: ADDING AN ISAGRAF CLIENT LINK

6.6.2.4.3 Linking a datapoint to an ISAGRAF server link

To link a datapoint to an ISAGRAF server link the relation 'manages' must 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).
(1)
(2)
(3)
FIGURE 335: LINKING A DATAPOINT TO AN ISAGRAF SERVER LINK

6.6.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 concanetating 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_1.
(4)
FIGURE 336: DEFINING ISAGRAF IO PREFIX FOR AN OUTPUT

• The first character must be a letter.
• The following characters must be either a letter in upper case, either a digit or an
underscore.
• The maximum length is 80 characters

6.6.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).
(1)
FIGURE 337: LAUNCHING ISAGRAF EDITOR

Once launched, ISaGRAF editor allows diagram edition of the automation. For details about
ISaGRAF workbench and SCE datapoint coupling, refer to section Erreur ! Source du
renvoi introuvable. –.Erreur ! Source du renvoi introuvable..
FIGURE 338: USING ISAGRAF EDITOR

6.6.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 modelling.
Group SPS can only belong to bays or modules. The MiCOM C264P 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 339: 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 5.1.2 – Defining an SPS datapoint.
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.
(1)
FIGURE 340: 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.
(1)
FIGURE 341: ADDING A COMPONENT TO A GROUP

6.6.4 Controlling xPC by xPS change of state

For specific needs, some SPS or DPS can acts on SPC or DPC. This relation is called xPS-
xPC association. Such an acted xPC does not necessary need a channel for wiring. It can be
a xPC used for automation management for instance.
The link defines for each state of the xPS which order must be sent.
• Add the relation ‘controls on state change’ (1) 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 or DPC (2).
• Set the relation attributes (3) giving for each state of the xPS, the order to send: None,
Open (resp. Off) or Close (resp. On) for DPC (resp. SPC).
(1)
(2)
(3)
FIGURE 342: CONTROLLING XPC THROUGH XPS (E.G.)

6.6.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 5 – Defining datapoint)
• 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
(1)
(2)
FIGURE 343: PRODUCING DPS FROM 2 SPS (E.G.)

6.6.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 modelling, 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:
• 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).
(1)
FIGURE 344: 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 5.1.2 – Defining an SPS datapoint.
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 6.6.1 – 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.
(1)
FIGURE 345: DEFINING INTERLOCKING EQUATION FOR AN INTERLOCK SPS

6.6.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:
• 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).
(1)
FIGURE 346: DEFINING AN AUTOMATIC/MANUAL DEPENDENCY (E.G.)

• For each "DPC", "SPC" or "Setpoint" datapoint, 2 relations "has for AutoManu
dependency" are available, but they are mutually exclusive.
7. DEFINING MiCOM C264P LOCAL HMI

All kinds of MiCOM C264Ps (except C364), can have a GHU200 board for led managing and
possible local bay mimic panel animations in case of complete GHU200 board (refer to
section 4.4.2.2 – Setting specific features of a GHU2xx board),.
7.1 Using bitmap table
To define MiCOM C264P bay mimics, bitmaps are used. Their definition is located at graphic
root of the data modelling.
At MiCOM C264P 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.
Default bay mimics (1) are accessible in the ‘Object view’ area.
(1)
FIGURE 347: BAY MIMICS

To see the graphically representation of a bitmap, select its name in the ‘object view’ area
and use the “graphical editor” at SCE level:
FIGURE 348: USING BITMAP EDITOR

7.2 Defining a MiCOM C264P workspace

Via a complete GHU200 board (refer to section 4.4.2.2 – Setting specific features of a
GHU2xx board), each protection with local HMI references a workspace that groups its bay
mimic definitions. MiCOM C264P computer workspaces can not be shared by several
protections because mimics are local to bays managed by a specific protection.
Up to 24 bay mimics can be put in a MiCOM C264P workspace, and up to 2 mimics can be
linked to the same bay.
Usual labels are used by MiCOM C264P local HMI (LHMI). They are located for all
protections LHMI in one object grouping all translatable labels, located in “computer
workspaces” folder in Graphic topology.
7.2.1 Settings LHMI labels
To modify a label shown on computer LHMI, update the corresponding attribute.
The Panels tab is used to customize the panels title, such that of Login and banner:
FIGURE 349: SETTINGS LHMI LABELS

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:
7.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 GHU200 board is concerned by created workspace by filling the relation
has for workspace at concerned GHU board level (refer to section 4.4.2.2).
• Define the short and long name attributes of the workspace used for internal SCE id:
FIGURE 350: ADDING A COMPUTER WORKSPACE

Once added, computer workspace general features must be set at SCE level:
• Precise which GHU200 board is concerned by created workspace by filling the relation
‘has for workspace’ at concerned GHU board level (refer to section 4.4.2.2 – Setting
specific features of a GHU2xx board).
• Setting the short and long name (1) attributes of the workspace used for internal SCE
identification.
• Setting ‘local/remote password usage’ (No / Yes) attribute (2), to precise if password is
required to set Local/remote for bays managed by the MiCOM C264P.
(1)
(2)
FIGURE 351: SETTING MiCOM C264P WORKSPACE ATTRIBUTES

7.3 Defining a MiCOM C264P bay mimic

7.3.1 Creating a MiCOM C264P bay mimic
The addition of a MiCOM C264P bay mimic is done via the “Objects entry” window at
protection workspace level by clicking on mouse’s right button.
FIGURE 352: ADDING A MiCOM C264P BAY MIMIC

Once added, bay mimic general attributes must be set at SCE level:
1. short name of the bay mimic used for internal SCE identification.
2. 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 7.3.4 – Assigning MV to bay mimic).
3. 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
7.3.3 – Defining dynamic part: pre-defined dynamic text, generic module
representation, transformer representation).
4. Fill the relation ‘represents’, giving which bay is represented by the mimic (for details
about bay refer to section 6.1.4 – Defining a Bay).
5. 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 MiCOM
C264P LHMI level (1 or 2).
(1)
(2)
(3)
(4)
(5)
FIGURE 353: 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:
1. Reserved zone for bay name display
2. Reserved zone for bay local/remote display ((2’) in tree browser)
3. Reserved zone for ‘interlocking bypass in progress’ information ((3’) in tree browser)
4. Reserved zone for ‘synchrocheck bypass in progress’ information ((4’) in tree browser)
5. Configurable zone for graphical representation of the bay (static and dynamic parts)
6. Reserved zone for message
(1)
(2)
(3)
(4)
(5)
(3’)
(2’)
(4’)
FIGURE 354: CORE STRUCTURE OF BAY MIMIC

For more details about protection LCD usage, refer to document User Interface (coded HI for
Human Interface) of MiCOM C264P documentation binders.
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 MiCOM C264P managing a bay represented by a "Bay mimic" must be the same
as the one linked to the "Comp. workspace" (protection workspace) of this "Bay
mimic".
• 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 MiCOM C264P, 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:
Graphic
Comp. workspace
Bay mimic max = 24 / Comp. workspace
LHMI Transformer max = 9 / Bay mimic
LHMI Gen module
LHMI bitmap max = 5 / Bay mimic
LHMI line max = 30 / Comp. workspace max = 18 / Bay mimic
LHMI text max = 5 / Bay mimic (1 is reserved for the Bay name) + 1 reserved
… for the Bay name
S0285ENa
7.3.2 Defining static part: line, bitmap, fixed text

The static part of a MiCOM C264P 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 7.1 –
Using bitmap table) 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.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 clicking on mouse’s right button.
FIGURE 355: ADDING A LINE IN MiCOM C264P BAY MIMIC

Once added, line attributes must be set at SCE level:

1. short name of the line used for internal SCE identification
2. x ( range [0, 127 pixels], step 1 pixel): abscissa
3. y ( range [0, 127 pixels], step 1 pixel): ordinate
4. length ( range [1 pixel, 127 pixels], step 1 pixel)
5. orientation ( Horizontal / Vertical)
6. thickness ( range [1 pixel, 8 pixels], step 1 pixel)
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 356: 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)
7.3.2.2 Adding a bitmap
The addition of a bitmap in bay mimic is done via the “Objects entry” window at bay mimic
FIGURE 357: ADDING A BITMAP IN MiCOM C264P BAY MIMIC

Once added, bitmap attributes must be set at SCE level:

1. short name of the line used for internal SCE identification
4. bitmap reference: corresponds to a link in the bitmap table (refer to section 7.1 –
Using bitmap table)
(1)
(2)
(3)
(4)
FIGURE 358: SETTING BITMAP ATTRIBUTES

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)
• 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.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
FIGURE 359: ADDING A FIXED TEXT IN MiCOM C264P BAY MIMIC

Once added, fixed text attributes must be set at SCE level:

1. fixed text value: text to display at mimic level
(1)
(2)
(3)
FIGURE 360: SETTING BITMAP ATTRIBUTES

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)).
7.3.3 Defining dynamic part: pre-defined dynamic text, generic module representation, transformer
representation
To define dynamic part of protection 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 synchronisation 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
MiCOM C264P 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 a 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.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.
FIGURE 361: ADDING TIME INFORMATION IN PROTECTION BAY MIMIC

Once added, time information attributes must be set at SCE level:
1. short name of the time information area used for internal SCE identification
(1)
(2)
(3)
FIGURE 362: 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.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:
1. Interlock bypass ‘button’
2. Local/remote status
3. Synchrocheck bypass ‘button’
Depending on customer’s need, these data can be positioned at a different location:
• directly by using mouse drag and drop in bay mimic editor
• by editing the abscissa and ordinate attributes of the object
(1)
(2)
(3)
FIGURE 363: POSITIONNING PRE-DEFINED TEXT INFORMATION IN BAY MIMIC
7.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 364: ADDING SBMC INFORMATION IN MiCOM C264P 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

7.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 365: ADDING A GENERIC MODULE IN MiCOM C264P BAY MIMIC

Once added, the representation features must be set at SCE level:

1. short name of the representation used for internal SCE identification
4. 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
5. Relation ‘is managed by’ that must be filled to precise which SPS or DPS is used for
bitmap animation
6. multi-bitmap reference: corresponds to a link in the bitmap table (refer to section
7.1 – Using bitmap table)
7. module name value: text displayed on LCD (up to 4 characters)
(1)
(2)
(3)
(4)
(5) (7)
(6)
FIGURE 366: 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 "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.
7.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 367: ADDING A GENERIC MODULE IN MiCOM C264P BAY MIMIC

Once added, the representation features must be set at SCE level:

1. short name of the representation used for internal SCE identification.
4. 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.
5. Relation ‘is managed by’ that must be filled to precise which TPI is used for
transformer animation.
6. bitmap reference: corresponds to a link in the bitmap table (refer to section 7.1 –
Using bitmap table).
7. module name value: name of the transformer: text displayed on LCD (up to 4
characters).
(1)
(2)
(3)
(4)
(5) (7)
(6)
FIGURE 368: 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.
FIGURE 369: ADDING A TPI INFORMATIION IN MiCOM C264P 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".
7.3.4 Assigning MV to bay mimic
A MV datapoint is assigned to a specific bay mimic by adding the relation ‘visualizes’ at bay
mimic level and filling it with the MV.
FIGURE 370: ASSIGNING MV DATAPOINT TO BAY MIMIC

Once the relation added and filled, its attributes ‘scale’ must be set at SCE level:
1. scale (120% / 200% / No bargraph), to precise which representation is used for the
MV in the bay mimic.
(1)
FIGURE 371: SETTING MV REPRESENTATION IN BAY MIMIC

• 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.4 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 MiCOM
C264P can be displayed via the Leds of its GHU200 board.
(1)
FIGURE 372: 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:
1. Led status for ‘Set’ state (resp 'Closed'): ( Off / On / Blinking slow / Blinking fast)
2. Led status for ‘Reset’ state (resp 'Open'): ( Off / On / Blinking slow / Blinking fast)
3. Led status for ‘Invalid’ state: ( Off / On / Blinking slow / Blinking fast)
(1)
(2)
(3)
FIGURE 373: SETTING LED STATUS FOR A DATAPOINT (E.G. FOR SPS DATAPOINT)
• 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).
8. DEFINING PROTECTION FUNCTIONS

8.1 General
Protection and automatism functions are respectively described in sections 6 and 7 of
chapter C264P/EN FT. Automatism functions are presented in section 9 – Defining
automatism functions.
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 MiCOM C264Ps:
− Undervoltage protection ([27] function),
− Earth wattmetric protection ([27N] 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).

8.1.1 General architecture
In the object view tree, the following tree structure is used to present the protection functions:
(1)
(2)
(3)
(4)
(5)
FIGURE 374: PROTECTION FUNCTIONS TREE STRUCTURE

Relay (1) 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 (2) contains a folder representing the associated
thresholds (3). The characteristics (4) (as instantaneous, temporization, trip signal, and
mode of operation) and the links (5) of each characteristic are settable.
8.1.2 Defining a protection function
For each protection function the SCE allows to use the DSPIO 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 375: ADDING A PROTECTION FUNCTION
These trip contacts relates to the serial SPST 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.
8.2 [27] Undervoltage protection

8.2.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] makes it possible 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 three 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.
8.2.2 Defining Undervoltage protection function
An addition of [27] function is done under SCE via the “Object entry” area at bay level by
To add [27] Undervoltage protection function, see chapter 8.1.2 – Defining a protection
function.
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 5.1.2 –
Defining an SPS datapoint,
− 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 5.1.4 – Defining an MPS datapoint,
− 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 5.1.2 – Defining
an SPS datapoint,
− 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 5.1.2 –
(1)
(2)
(3)
(4)
(5)
FIGURE 376: [27] UNDERCURRENT SUB-TREE

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.

8.3 [32N] Earth wattmetric protection

The directional earth fault protection provides three directional / non directional earth
overcurrent thresholds and two wattmetric and active earth fault current thresholds (see
section 8.9 – [67N] Directional Earth Fault protection for more details about directional earth
fault).
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.
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.
8.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
To add [32N] earth wattmetric protection function, see chapter 8.1.2 – Defining a protection
function.
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 5.1.2 – Defining an SPS datapoint,
− 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 5.1.4 – Defining an MPS datapoint,
− 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 5.1.2 –
− 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 5.1.2 –
(1)
(2)
(3)
(4)
(5)
FIGURE 377: [32N] EARTH WATTMETRIC SUB-TREE

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.

8.4 [37] Undercurrent protection

The undercurrent function [37] makes it possible 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 tI<

The threshold provides alarm and trip stage, where required. Alternatively, time setting is
settable, depending upon the severity of the current dip.
8.4.2 Defining Undercurrent protection function
To add [32N] earth wattmetric protection function, see chapter 8.1.2 – Defining a protection
function.
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
5.1.2 – Defining an SPS datapoint,
− 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 attributes, see section 5.1.4 – Defining an MPS datapoint,
− 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 5.1.2 – Defining
an SPS datapoint,
− 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 5.1.2 – Defining
an SPS datapoint.
(1)
(2)
(3)
(4)
(5)
FIGURE 378: [37] UNDERCURRENT SUB-TREE

8.5 [46] Negative Sequence Overcurrent protection

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.
8.5.2 Defining Negative Sequence Overcurrent protection function
To add [46] Negative Sequence Overcurrent protection function, see chapter 8.1.2 –
Defining a protection function.
The protection function sub-tree contains three thresholds (1): threshold 1, threshold2 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 5.1.2 – Defining an SPS datapoint,
− 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
− 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 5.1.2 – Defining
an SPS datapoint,
− 46 t trip SPS (5) is the trip signal for the first threshold (“I2>” trip). This datapoint is a
set and reset delays are fixed. To set 46 t trip SPS attributes, see section 5.1.2 –
(1)
(2)
(3)
(4)
(5)
FIGURE 379: [46] NEGATIVE SEQUENCE OVERCURRENT SUB-TREE

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,
− 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.
8.6 [49] Thermal overload protection

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.).
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”. Curves of the thermal
overload time characteristic are given in C264P/EN FT (Functional Description) section.
8.6.2 Defining Thermal overload protection function
To add [49] Thermal overload protection function, see chapter 8.1.2 – Defining a protection
function.
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 attributes, see section 5.1.4 – Defining an MPS datapoint,
− 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 5.1.2 –
− 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 5.1.2 –
− 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 5.1.2 – Defining an SPS datapoint.
(1)
(2)
(3)
(4)
(5)
FIGURE 380: [46] NEGATIVE SEQUENCE OVERCURRENT SUB-TREE

8.7 [59N] Zero Sequence Overvoltage protection

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>.
8.7.2 Defining [59N] Zero Sequence Overvoltage protection function
To add [59N] Zero Sequence Overvoltage protection function, see chapter 8.1.2 – Defining a
protection function.
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
− 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 5.1.4 – Defining an MPS datapoint,
− 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 5.1.2 – Defining an SPS
datapoint,
− 59N t trip SPS (5). trip signal for the first threshold (Uen> trip). This trip signal is a
set and reset delays are fixed. To set 59N t trip SPS attributes, see section 5.1.2 –
(1)
(2)
(3)
(4)
(5)
FIGURE 381: [59N] ZERO SEQUENCE OVERVOLTAGE SUB-TREE

8.8 [67] Directional overcurrent protection

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^U) / Torque angle and Trip boundary zone.
The directional overcurrent protection element compares the directional fault current,
residual voltage with the set thresholds I>, U>, I>>, U>>, I>>>, U>>> 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
nd rd st
the first threshold: The 2 and 3 threshold pickup can suspend 1 threshold output control
to save selectivity.
8.8.2 Defining [67] Directional overcurrent protection function
To add [67] Directional overcurrent protection function, see chapter 8.1.2 – Defining a
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 5.1.2 – Defining an SPS datapoint,
− 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,
− 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
− 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
− 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 5.1.2 – Defining an SPS datapoint,
− 67 t1 trip SPS (6) indicates the trip signal for the first threshold (I> 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 5.1.2 –
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 382: [67] DIRECTIONAL OVERCURRENT SUB-TREE

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.
8.9 [67N] Directional Earth Fault protection

The directional earth fault protection provides three directional / non directional earth
overcurrent thresholds and two wattmetric and active earth fault current thresholds (see
section 8.3 – [32N] Earth wattmetric protection for more details about this protection).
The directional earth fault overcurrent protection element compares the earth fault current,
residual voltage with the set thresholds Ie>, Ue>, Ie>>, Ue>>, Ie>>>, Ue>>> and the relevant
angle between the Ie and Ue for each threshold.
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.
The protection elements trip when the following conditions occur:
− thresholds for Ie and Ue are exceeded (earth fault overcurrent protection element)
− Ie current vector is in the tripping area (Ie^Ue)
− Ie [mA] + Ue [V] > 18 (Ien=1A) or Ie [mA] + Ue [V] > 90 (Ien=5A)
− the tripping timer expires

The peak detection is applied where a CT saturation condition occurs and the measure is not
more trustworthy.
The reset delay time for each threshold provides protection against intermittent faults.
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.
8.9.2 Defining [67N] Directional earth fault protection function
To add [67N] Directional earth fault protection function, see chapter 8.1.2 – Defining a
threshold 3.
The first threshold sub-tree contains six nodes:
− 67N t1 in dir rev SPS (2) indicates instantaneous non-directional earth 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 5.1.2 – Defining an SPS datapoint,
− 67N t1 inst. SPS (3): indicates instantaneous directional earth 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 5.1.2 – Defining an SPS datapoint,
− 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 section 5.1.2 – Defining an SPS datapoint,
− 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
− 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,
− 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 5.1.2 – Defining
an SPS datapoint.
FIGURE 383: [67N] DIRECTIONAL EARTH FAULT SUB-TREE

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.
8.10 [81O] Overfrequency protection

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.
8.10.2 Defining [81O] Overfrequency protection function
An addition of [81O] function is done under SCE via the “Object entry” area at bay level by
To add [81O] Overfrequency protection function, see chapter 8.1.2 – Defining a protection
function.
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 5.1.2 –
− 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
− 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 5.1.2 – Defining an SPS datapoint,
− 81O t1 trip SPS (5) is the trip signal for the first threshold (f1 trip). This datapoint is a
set and reset delays are fixed. To set 81O t1 trip SPS attributes, see section 5.1.2 –
(1)
(2)
(3)
(4)
(5)
FIGURE 384: [81O] OVERFREQUENCY SUB-TREE

The contents of “threshold 2” to “threshold 6” are identical to “threshold 1”.
− 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.
8.11 [81R] Range Frequency protection

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 positionning the protection.
In fact, the instantaneous element is positionned after exceeding the threshold for a
programmable number of df/dt function calculation.
When the input voltage value is unsufficient this will lead to irregular behavior and it is
imaginable that 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.
8.11.2 Defining [81R] Range Frequency protection function
An addition of [81R] function is done under SCE via the “Object entry” area at bay level by
To add [81R] Range Frequency protection function, see chapter 8.1.2 – Defining a protection
function.
threshold 6.
− 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 5.1.2 – Defining an SPS datapoint,
− 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
− 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 5.1.2 –
− 81R t1 trip SPS (5) is the trip signal for the first threshold (df/dt trip). This datapoint is
a transient (pulse) signal (transient “detection mode” not settable). Time reference, set
and reset delays are fixed. To set 81R t1 trip SPS attributes, see section 5.1.2 –
(1)
(2)
(3)
(4)
(5)
FIGURE 385: [81R] RANGE FREQUENCY SUB-TREE

− 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,
− 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.
8.12 [81U] Underfrequency protection

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.
8.12.2 Defining [81U] Underfrequency protection function
An addition of [81U] function is done under SCE via the “Object entry” area at bay level by
To add [81U] Underfrequency protection function, see chapter 8.1.2 – Defining a protection
function.
threshold 6.
− 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 5.1.2 –
− 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
− 81U t1 temp. SPS (4) is the temporization signal for the first threshold, corresponding
to tf1. This datapoint is a permanent signal (permanent “detection mode” attribute not
settable). To set 81U t1 temp. SPS attributes, see section 5.1.2 – Defining an SPS
datapoint,
− 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 5.1.2 –
(1)
(2)
(3)
(4)
(5)
FIGURE 386: [81R] RANGE FREQUENCY SUB-TREE

− 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,
− 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.
9. DEFINING AUTOMATISM FUNCTIONS

9.1 General
Protection and automatism functions are respectively described in sections 6 and 7 of
chapter C264P/EN FT. Protection functions are presented in section 8 – Defining Protection
functions.
In the object view tree, the automatism functions are associated with a relay (bay level).
When automatism is added to a bay, a relay is automatically added as a sub-component.
The automatism function contains the following components:
− 2 protections group,
− [50BF] breaker failure,
− blocking protection,
− cold load start,
− logic selectivity,
− maintenance,
− miscellaneous,
− trip management.
9.2 General architecture
In the object view tree, the automatism function contains the following architecture:
(1)
(2)
(3)
(4)
(5)
FIGURE 387: AUTOMATISM SUB-TREE

Relay (1) object is automatically created when automatism function is added to the bay.
Relay does not contain attribute and cannot be edited.
The automatism sub-tree (2) contains folders corresponding to the automatic control
functions (3). The parameters (4) of the functions and profiles (5) are settable.
9.2.1 Adding automatism function

The addition of automatism 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 automatism function:
− Add the automatism function from Objects entry (Built-in function, Relay built-in
function sub-tree) at bay level (1),
− The automatism function (3) is added (Relay (2) is automatically added with the first
protection function),
− Update the function attibutes: short name and long name (4).
(1)
(2)
(3)
(4)
FIGURE 388: ADDING AUTOMATISM FUNCTION

9.3 Protection setting groups

9.3.1 Description
The MiCOM protections 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 excepted than for thermal overload function.
If a setting group change is received during any protection or automation function, it is stored
and executed after the last timer has elapsed.
9.3.2 Setting “2 protection group” automatism 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 5.1.2 – Defining an
SPS datapoint.
− 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 5.1.10 – Defining an SPC datapoint.
(1)
(2)
(3)
FIGURE 389: SETTING ‘2 PROTECTION GROUP’

9.4 [50BF] breaker failure

9.4.1 Description
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.
9.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
− 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 5.1.4 – Defining an
MPS datapoint.
(1)
(2)
(3)
FIGURE 390: SETTING ‘[50BF] BREAKER FAILURE’

9.5 Blocking protection

9.5.1 Description
The directional, non directional overcurrent and overcurrent protection are applicable for
radial feeder circuits where there is small 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.
9.5.2 Setting ‘Blocking protection’ automatism 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 5.1.2 – Defining an SPS datapoint,
− bloc DI status SPS is the blocking protection digital input status. This input is a
modify bloc DI status SPS attributes, see section 5.1.2 – Defining an SPS datapoint,
− 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 5.1.10 – Defining an SPC datapoint,
− 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
(1)
(2)
(3)
(4)
(5)
FIGURE 391: SETTING ‘BLOCKING PROTECTION’

9.6 Cold load start

9.6.1 Description
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 energised, the current levels that flow for a period of time following
energising 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 energising.
9.6.2 Setting ‘Cold load start’ automatism 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 5.1.2 – Defining an SPS
datapoint,
− 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, see section 5.1.2 – Defining an SPS datapoint.
(1)
(2)
(3)
FIGURE 392: SETTING ‘COLD LOAD START’

9.7 Logic selectivity

9.7.1 Description
The Logic selectivity is used in non-cascade protection schemes, using the start contacts
from downstream relays to block operation of upstream relays.
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.
9.7.2 Setting ‘Logic selectivity’ automatism 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, see section 5.1.2 – Defining an SPS datapoint,
− 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 5.1.10 – Defining an SPC datapoint,
− sel CO status SPS (4) is the logic selectivity command status. This input is a
modify sel CO status SPS attributes, see section 5.1.2 – Defining an SPS datapoint,
− sel DI status SPS (5) is the logic selectivity digital input status. This input is a
modify sel DI status SPS attributes, see section 5.1.2 – Defining an SPS datapoint.
(1)
(2)
(3)
(4)
(5)
FIGURE 393: SETTING ‘LOGIC SELECTIVITY’

9.8 Maintenance
9.8.1 Description
The maintenance mode allows the user to verify the operation of the protection functions
without sending any external order (tripping or signalling).
The maintenance function is used when the selection or the end of the maintenance mode is
possible by logic input or control command.
9.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 5.1.2 – Defining an SPS datapoint,
− 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 5.1.10 –
Defining an SPC datapoint.
(1)
(2)
(3)
FIGURE 394: SETTING ‘MAINTENANCE’

9.9 Miscellaneous
9.9.1 Description
The “Miscellaneous” subtree contains the following automatism functions:
− digital input start disturbance status,
− frequency protection status,
− protection state status,
− Reset thermal status control,
− start disturbance control,
− synthesis of instantaneous fault signals status,
− synthesis of temporization signals status,
− synthesis of trip signals status.

9.9.2 Setting ‘Miscellaneous’ automatism menu
The “Miscellaneous” function sub-tree (1) contains eight datapoints:
− DI start disturb SPS (2) (start disturbance digital Input status). This input is a
permanent signal (permanent “detection mode” attribute not settable). To modify DI
start disturb SPS attributes, see section 5.1.2 – Defining an SPS datapoint.
− Feq 81 invalid SPS (3) 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 5.1.2 – Defining an SPS datapoint.
− protection state MPS (4) (protection state status). All the attributes can be modified.
To modify protection state MPS attributes, see section 5.1.4 – Defining an MPS
datapoint.
− reset thermal st SPC (5) (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 5.1.10 – Defining an SPC datapoint.
− start dist ctrl SPC (6) (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 5.1.10 – Defining an SPC datapoint.
− synthesis inst. SPS (7) (Synthesis of instantaneous). This input is a permanent

signal (the permanent “detection mode” attribute not settable). To modify synthesis
inst. SPS attributes, see section 5.1.2 – Defining an SPS datapoint.
− synthesis temp. SPS (8) (Synthesis of temporisation). This input is a permanent

signal (the permanent “detection mode” attribute not settable). To modify synthesis
temp. SPS attributes, see section 5.1.2 – Defining an SPS datapoint.
− synthesis trip SPS (9) (Synthesis of trip). This input is a permanent signal (the
permanent “detection mode” attribute not settable). To modify synthesis trip SPS
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
FIGURE 395: SETTING ‘MISCELLANEOUS’

9.10 Trip management

9.10.1 Description
The trip management corresponds to trip relay control and trip status.
9.10.2 Setting ‘Trip management’ automatism menu
The “Trip management’” function sub-tree (1) contains eight datapoints (2):
10.3 SPCs (trip #1 ctrl, trip #2 ctrl and trip #3 ctrl) to control the relay
11.3 SPSs (trip #1 status, trip #2 status et trip #3 status) to monitor the status of the relay
12.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 5.1.10 – Defining an SPC datapoint.
The detection mode attribute is set to permanent and cannot be modified. To modify trip
status SPS attributes, see section 5.1.2 – Defining an SPS datapoint.
Assign a specific existing profile to each datapoint. See section 5.2 – Linking a datapoint to a
profile, for details about profile definition and setting.
Execute the auto-addressing.
(1)
(2)
FIGURE 396: SETTING ‘TRIP MANAGEMENT’

LEXICON
Page 1/14
CONTENT
2. LEXICON 4
C264P/EN LX/C80 Lexicon
Page 2/14
BLANK PAGE
.
Page 3/14

This document is the last chapter of each PACiS documentation. It is the lexicon.
Page 4/14
2. LEXICON
AC Alternating Current
AccI Accumulator Input
ACSI Abstract Communication Service Interface
Mapping from the standard IEC61850 abstract specification of communication
service to a concrete communication infrastructure based on CORBA specific.
A/D Analog/Digital
ADC Analogue to Digital Converter
AE qualifier Application Entity qualifier (Used internally by IEC61850 to identify a server
Application)
AI Analogue Input (Measurement Value including state attribute)
Commonly Voltage or current DC signals delivered by transducers, and
representing an external value (refer to CT/VT for AC).
AIS Air Insulated Substation
AIU Analogue Input Unit (Computer C264 Board name for DC Analogue Input)
Alarm An alarm is any event tagged as an alarm during configuration phase
AO Analogue Output
Value corresponding to a desired output current applied to a DAC.
AOU Analogue Output Unit (computer C264 board name for Analogue Output)
API Application Programming Interfaces
AR Auto-Reclose
ARS Auto-Recloser
ASCII American Standard Code for Information Interchange
ASDU Application Specific Data Unit
Name given in OSI protocol for applicative data (T103, T101..)
ASE Applied System Engineering
ATCC Automatic Tap Change Control
Automation in charge of secondary voltage regulation, more specific than AVR
AVR Automatic Voltage Regulator
Automatism used to regulate secondary voltage by automatic tap changer
control (see ATCC). Set of features can be added, see chapter C264 FT
Bay Set of LV, MV or HV plants (switchgears and transformers) and devices
(Protective, Measurement…) usually around a Circuit Breaker and controlled
by a bay computer.
BCD Binary Coded Decimal
One C264 supported coding on a set of Digital Inputs, that determine a Digital
Measurement, then Measurement value (with specific invalid code when coding
is not valid). Each decimal digit is coded by 4 binary digits.
BCP Bay Control Point
Name given to the device or part used to control a bay. It can be Mosaic Panel,
C264 LCD,… Usually associate with Remote/Local control.
BCU Bay Control Unit
Name given to the C264 in charge of a bay. Usually in contrast with Standalone
BI Binary Input (or Information)
Name given into Computer C264 of information already filtered, before it
becomes an SPS, DPS… with time tag and quality attributes
BIU Basic Interface Unit
C264 Board for auxiliary power supply(ies), watchdog relay, redundancy I/O,
serial port(s).
Page 5/14
BNC A connector for coaxial cable.

B-Watch Monitoring and control device for GIS substation.
CAD Computer Aided Design
Computer application dedicated to design like wiring, protective setting…
CAS CASe
Computer C264 rack
CAT Computer Administration Tool
CB Circuit Breaker
Specific dipole switch with capability to make line current and break fault
current. Some have isolation capability (nominal-earth at each side)
CBC Compact Bay Controller
Small capacity bay computer for Medium Voltage applications typically C264C
CC Complemented Contact
CCU Circuit breaker Control Unit
Computer C264 Board dedicated to switch control with 8DI, 4 DO
CDM Conceptual Data Modelling
Is the modelling of system/devices data using a hierarchy of structured data
(called object of class) with their attributes, method or properties and the
relations between themselves. It maps common data to devices or components
of devices, with guaranty of interoperability.
Class Define in IEC61850 as: description of a set of objects that share the same
attributes, services, relationships, and semantics
Client Define in IEC61850 as: entity that requests a service from a server and that
receives unsolicited messages from a server
CM CoMissioning
CO Command, logic information Output (Functional Component) / Contact Open
COMTRADE Common Format For Transient Data Exchange (international standard IEC
60255-24)
CPU Central Processing Unit
Computer C264 main Board based on PowerPC
CRC Cyclic Redundancy Check
Coding result send with packet of transmitted data to guarantee their integrity.
Usually result of a division of transmitted data by polynomial.
CSV Character Separate Values
ASCII values separated by predefined character or string like in Excel or ASCII
Comtrade.
CT Current Transformer
Basically the electric device connected to process and extracting a current
measurement. By extension part of a device (C264) that receives AC values
and convert it to numerical measurement value.
CT/VT Current and Voltage transformers
(Conventional) By extension, it is the C264 TMU board.
CT/VT Current and Voltage transformers
(Non-Conventional or New generation of captor based for example on light diffraction under electric
intelligent) field, without transformer, that gives directly numerical measurement of voltage
and current like communicating IED.
CSV Character Separate Values
Asci values separated by predefined character or string like in Excel or ASCII
Comtrade.
DAC Data Acquisition component of the GPT
Page 6/14
DAC Digital to Analogue Converter

Used to generate analogue signals (usually DC) from a digital value.
DB DataBase
Tool or set of data that define all configuration of a system or specific device
like computer. Opposed to setting or parameter DB has a structure that can not
be modified on line. DB are always versioned.
DB-9 A 9-pin family of plugs and sockets widely used in communications and
computer devices.
DBI Don’t Believe It
Term used for undefined state of a double point when input are not
complementary. DBI00 is state motion or jammed. DBI11 is undefined.
DBID Databases Identity Brick
DC Direct Current
DC, DPC Double (Point) Control
Two digit and/or relays outputs used for device control with complementary
meaning (OPEN, CLOSE).
DCF77 External master clock and protocol transmission
LF transmitter located at Mainflingen, Germany, about 25 km south-east of
Frankfurt/Main, broadcasting legal time on a 77.5 kHz standard frequency.
DCO Double Control Output
DCP Device Control Point
Located at device level (electric device or IED). It should have its own
Remote/Local switch.
DCS Digital Control System
Generic name of system based on numeric communication and devices, to be
opposed to traditional electrically wired control.
DCT Double CounTer
Counter based on 2 DI with complementary states (counting switchgear
manoeuvre for example)
DE Direct Execute
DELTA Phase to phase delta values
Device Term used for one of the following unit:
Protective relays, metering units, IED, switchgear (switching device such as
CB, disconnector or earthing switch), disturbance or quality recorders.
DHMI C264 Display HMI
DI Digital Input
Binary information related to the presence or to the absence of an external
signal, delivered by a voltage source.
DIN Deutsche Institut für Normung
The German standardisation body.
DIU DC Input Unit
Computer C264 Board name for Digital Input
DLL Dynamic Link Library. Available on Windows XP.
A feature that allows executable code modules to be loaded on demand and
linked at run time. This enables the library-code fields to be updated
automatically, transparent to applications, and then unloaded when they are no
longer needed.
DM Digital Measurement
Is a measurement value which acquisition is done by DI and a specific coding
BCD, Gray, 1 among N…
Page 7/14
DNP3.0 Distributed Network Protocol

DNP3 is a set of communication protocols used between components in
process automation systems.
DO Digital Output
Used to apply a voltage to an external device via a relay, in order to execute
single or dual, transient or permanent commands.
DOF Degree Of Freedom
Used for a template attribute, that can be modified or not when used. An attri-
bute has a degree of freedom if a user can modify its values on its instances
DOU Digital Output Unit
Computer C264 Board name for Digital Output
DP Double Point
Information/control derived from 2 digital inputs/output; usually used for position
indication of switching devices (OPEN, CLOSE).
DPC Double Point Control
DPS Double Point Status
Position indication of switching devices (OPEN, CLOSE).
ECDD Coherent Extract of Distributed Data
ECU Extended Communication Unit.
External module connected to the CPU board. This module converts non-
insulated RS232 into optical signal or insulated RS485/RS422.
EH90 Transmission protocol dedicated to time synchronisation and standardised by
EDF. Specification document: D.652/90-26c, March 1991.
EMC Electro-Magnetic Compatibility
EPATR Ensemble de Protection Ampèremétrique de Terre Résistante (French Legacy
very resistive earth current module)
Event An event is a time tagged change of state/value acquired or transmitted by a
digital control system.
FAT Factory Acceptance Test
Validation procedures execution with the customer at factory.(i.e. SAT)
FBD Functional Block Diagram
One of the IEC61131-3 programming languages (language used to define
configurable automation).
FIFO First In First Out
FO Fibre Optic
FP Front Panel
FTP Foil Twisted Pair
FLS Fast Load Shedding
FSS Force Suppress Substitute
Gateway Level 6 session of OSI, the gateway is any device transferring data between
different networks and/or protocol. The RTU function of the C264 gives a
gateway behaviour to SCADA or RCP level. PACIS Gateway is separate PC
base device dedicated to this function.
GHU Graphic Human interface Unit
Computer C264 Front Panel digital part (LCD, buttons, Front RS)
GIS Gas Insulated Substation
GLOBE GLOBE Brick
GMT Greenwich Mean Time
Absolute time reference
Page 8/14
GPS Global Positioning System

Based on triangulation from satellite signal, that transmit also absolute GMT
time used to synchronise a master clock
GOOSE Generic Object Oriented Substation Event
GPT Generic Protocol Translator software, supplied by ASE
Group Logical combination of BI (i.e. SP, DP, SI or other groups).
GSSE Generic Substation Status Event
Hand Dressing Facility for an operator to set manually the position of a device (acquired by
other means) from the HMI at SCP level; e.g. from OPEN to CLOSE (without
any impact on the “physical” position of the electrical switching device).
HMGA Horizontal Measurement Graphical Area
HMI Human Machine Interface
Can be PACIS OI (Operator Interface) or C264 LCD (Local Control Display) or
Leds, mosaic...
HSR High Speed auto-Recloser, first cycles of AR
HTML Hyper Text Mark-up Language
Used as standard for formatting web display
HV High Voltage (for example 30kV to 150kV)
I/O Input/Output
ICD IED Capability Description
IEC International Electro-technical Commission
IED Intelligent Electronic Device
General expression for a whole range of microprocessor based products for
data collection and information processing
IP Internet Protocol
IRIG-B Inter-Range Instrumentation Group standard format B. This is an international
standard for time synchronisation based on analogue signal.
JAMMED Invalid state of a Double Point:
Occurs when the 2 associated digital inputs are still in state 0 after an user-
selectable delay, i.e. when the transient state “ motion ” is considered as ended
Kbus Term used for the protocol Courier on K-Bus network (kind of RS422).
(Kbus Courier)
LAN Local Area Network
L-BUS Legacy Bus
Generic name of Legacy or field networks and protocols used to communicate
between C264 (Legacy Gateway function) and IED on field bus. Networks are
based on (RS232,) 422, 485. Protocols are IEC 60850-5-103 (T103 or VDEW),
Modbus or MODICON
LCD Liquid Crystal Display or Local Control Display (on C264)
LD Ladder Diagram, one of the IEC1131-3 programming languages (language
used to define configurable automation).
LED Light Emitting Diode
LF Low Frequency
LOC Local Operator Console
Dedicated to maintenance operation
L/R Local / Remote
Local / Remote When set to local for a given control point it means that the commands can be
Control Mode issued from this point, else in remote control are issue for upper devices.
LSB Least Significant Bit
Page 9/14
LSP Load Shedding Preselection

LV Low Voltage
MAFS Marketing And Functional Specification
MC Modular Computer
MCB Mini Circuit Breaker. Its position is associated to tap changer.
MDIO Management Data Input/Output
A standard driven, dedicated-bus approach that is specified in IEEE802.3
Measurements Values issued from digital inputs or analogue inputs (with value, state, time tag)
Metering Values computed depending on the values of digital or analogue inputs during
(non-tariff) variable periods of time (time integration).
Metering Values computed depending on the values of digital or analogue inputs during
(tariff) variable periods and dedicated to the energy tariff. These values are provided
by dedicated “tariff computer ” which are external to the MiCOM Systems.
MIDOS Schneider Electric Connector: Used for CT/VT acquisition
MMC Medium Modular Computer
MMS Manufacturing Message Specification (ISO 9506)
ModBus Communication protocol used on secondary networks with IED or with SCADA
RCP. 2 versions exist with standard MODICON or Schneider Electric one.
Module Word reserved in PACIS SCE for all electric HV devices. It groups all switch-
gears, transformer, motors, generators, capacitors, …
MOTION Transient state of a Double Point
Occurs when the two associated digital inputs are momentarily in state 0 (e.g.
position indication when an electrical device is switching). The concept of
“momentarily” depends on a user-selectable delay.
MPC Protection Module for Computer
MV Medium Voltage
MVAR Mega Volt Ampere Reactive
NBB Numerical Busbar Protection
NC Normally Closed (for a relay)
NO Normally Open (for a relay)
OBS One Box Solution
Computer that provides protection and control functions with local HMI. The
prime application of this device is intended for use in substations up to
distribution voltage levels, although it may also be used as backup protection in
transmission substations. Likewise, the OBS may be applied to the MV part of
a HV substation that is being controlled by the same substation control system.
OI Operator Interface
OLE Object Linking and Embedding
OLE is a Microsoft specification and defines standards for interfacing objects.
OLTC On Line Tap Changing
OMM Operating Mode Management
OPC OLE for process control
OPC is a registered trademark of Microsoft, and is designed to be a method to
allow business management access to plant floor data in a consistent manner.
Operation hours Sum of time periods, a primary device is running under carrying energy, e.g.
circuit breaker is in Close state and the current is unequal 0 A.
OSI Open System Interconnection
Split and define communication in 7 layers : physical, link, network, transport,
session, presentation, application
Page 10/14
OWS Operator WorkStation (PACiS OI)

PACiS Protection, Automation and Control Integrated Solutions
PLC Programmable Logic Control /Chart. Includes PSL and ISaGRAF
Within the PLC-programs are defined the configurable control sequences or
automations taken into account by the MiCOM Systems.
POW Point On Wave
Point on wave switching is the process to control the three poles of an HV-
circuit breaker in a way, to minimise the effects of switching.
PSL Programmable Scheme Logic
PSTN Public Switched Telephone Network
RCC Remote Control Centre
Is a computer or system that is not part of MiCOM system. RCC communicates
with and supervises MiCOM system using a protocol.
RCP Remote Control Point
Name given to the device or part used to control remotely several bay or sub-
station. Usually associated with Remote/Local sub-station control. It is a
SCADA interface managed by the MiCOM system through Telecontrol BUS.
Several RCPs can be managed with different protocols.
Remote Control Mode When set for a control point it means that the commands are issued from an
upper level and are not allowed from this point.
Remote HMI Remote HMI is a client of the substation HMI server. The client may provide all
or part of functions handled by the substation HMI.
RI Read Inhibit
This output indicates the availability of an analogue output (e.g. during DAC
converting time)
RJ-45 Registered Jack-45
A 8-pin female connector for 10/100 Base-T Ethernet network
RMS Root Mean Square
RRC Rapid ReClosure
RSE Régime Spécial d’Exploitation
French grid function when works are being done on a HV feeder
RSVC Relocatable Static Var Compensator
RS-232 Recommended Standard 232
A standard for serial transmission between computers and peripheral devices.
RS-422 A standard for serial interfaces that extends distances and speeds beyond RS-
232. Is intended for use in multipoint lines.
RS-485 A standard for serial multipoint communication lines. RS-485 allows more
nodes per line than RS-422
RSVC Relocatabled Static Var Compensator
RTC Real Time Clock
RTU Remote Terminal Unit
Stand alone computer that acquires data and transmit them to RCP or SCADA.
Typically it is the C964. RTU link is the TBUS.
SAT Site Acceptance Test
Validation procedures executed with the customer on the site.
SBMC Site Based Maintenance Control mode
A bay in SBMC mode does not take into account the commands issued from
RCP; moreover, some of its digital points & measurements (defined during the
configuration phase) are not sent anymore to the RCP (they are
“automatically” suppressed).
Page 11/14
SBO Select Before Operate

A control made in two steps, selection and execution. Selection phase give a
feedback. It can be used to prepare, reserve during time, configure circuit
before execution. Controls are done into a protocol, or physical (DO select with
DI Select then DO execute).
S-BUS Station Bus, federal network between PACIS devices.
SCADA Supervisory Control And Data Acquisition
Equivalent to RCC
SCD Description file extension (SCE)
SCE System Configuration Editor
SCL substation automation System Configuration Language (IEC 61850-6)
SCP Substation Control Point
Name given to the device or part used to control locally several bays or sub-
station. Usually associated with Remote/Local sub-station control. It is
commonly PACIS Operator Interface.
SCS Substation Control System
SCSM Specific Communication Service Mapping
SCT Single Counter
SER Sequence of Event Recorder
Combines SOE with accurate Time synchronization and Maintenance facilities
over Ethernet communication
Server Define in IEC61850 as: entity that provides services to clients or issues
unsolicited messages
Setpoints (analogue) Analogue setpoints are analogue outputs delivered as current loops. Analogue
setpoints are used to send instruction values to the process or auxiliary device
Setpoints (digital) Digital values sent on multiple parallel wired outputs Each wired output
represent a bit of the value. Digital setpoints are used to send instruction
values to the electrical process or to auxiliary devices.
SFC Sequential Function Chart
One of the IEC1131-3 programming languages (language used to define
configurable automation).
SI System Indication
Binary information that do not come from external interface. It is related to an
internal state of the computer (time status, hardware faults…). It is the result of
all inner function (AR, …), PSL, or ISaGRAF automation.
SICU 4 Switchgear Intelligent Control Unit
Control unit of an intelligent circuit breaker (fourth generation)
SIG Status Input Group
SINAD Signal-plus-Noise-plus-Distorsion to Noise-plus-Distorsion ratio, in dB
SIT Status Input Double Bit
SNTP Simple Network Time Protocol
SOE Sequence Of Events
Other term for the event list.
SP Single Point
SPS Single Point Status
SPC Single Point Control
ST Structured Text
An IEC1131-3 programming languages to define configurable automation
STP Shielded Twisted Pair
Page 12/14
Substation computer Bay computer used at substation level

Suppression A binary information belonging to a bay in SBMC mode will be automatically
(Automatic) suppressed for the remote control. However changes of state will be signalled
locally, at SCP
Suppression (Manual) A binary information can be suppressed by an order issued from an operator.
No subsequent change of state on a “suppressed information ” can trigger any
action such as display, alarm and transmission
SWR Switch Redundant
Computer C264 board Ethernet switch with redundant Ethernet
SWU Switch Unit (Computer C264 board Ethernet switch)
T101 Term used for IEC60870-5-101 protocol
TBC / TBD To Be Completed / Defined
T-BUS Telecontrol Bus, generic name of networks and protocols used to communicate
between PACIS Gateway or C264 Telecontrol Interface function and the RCP.
Networks are based on RS232, 485, or Ethernet (T104). Protocols are IEC
60850-5-101 (T101), Modbus MODICON
TC True Contact
TCIP Tap Changer in Progress
TCU Transformer Current Unit
Computer C264 CT/VT Board : Current acquisition
TDD Total Demand Distorsion, similar to the THD but applied to currents and with a
rated current (In) as reference
TG Telecontrol Gateway
THD Total Harmonic Distorsion, sum of all voltage harmonics
TI Tele Interface
TM Analogue Measurement
TMU Transducerless Measurement Unit
Topological Interlocking algorithm, based on evaluation of topological information of the
interlocking switchgear arrangement in the HV network, the switchgear kind and position, &
defined rules for controlling this kind of switch (e.g. continuity of power supply)
TPI Tap Position Indication (for transformers).
Frequently acquired via a Digital Measurement
TS Logic position
TVU Transformer Voltage Unit (computer C264 CT/VT Board : Voltage acquisition)
UCA Utility Communications Architecture
Communication standard (mainly US) used for PACIS SBUS communication
UPI Unit Per Impulse
Parameter of counter to convert number of pulse to Measurement value. Both
data (integer and scaled float) are in common class UCA2 Accumulator.
UTC Universal Time Co-ordinates (or Universal Time Code)
Naming that replace GMT (but it is the same)
VdBS Versioned data Base System, databag generated by SCE & ready to download
VDEW Term used for IEC60870-5-103 protocol
VMGA Vertical Measurement Graphical Area
Voltage level Set of bays whose plants & devices are dealing with same voltage (e.g. 275kV)
Page 13/14
VT Voltage Transformer
Basically the electric device connected to process and extracting a voltage
measurement. By extension part of a device (C264) that receives this AC value
and convert it to numerical measurement value. VT are wired in parallel.
WTS Windows Terminal Server, Microsoft’s remote desktop connection
WYE Three phases + neutral AI values
Page 14/14
BLANK PAGE
Customer Care Centre
http://www.schneider-electric.com/CCC
© 2012 Schneider Electric. All rights reserved.
Schneider Electric
35 rue Joseph Monier
92506 Rueil-Malmaison
FRANCE
Phone: +33 (0) 1 41 29 70 00
Fax: +33 (0) 1 41 29 71 00
www.schneider-electric.com Publishing: Schneider Electric
Publication: C264P/EN O/C80 01/2012

Micom C264P: Bay Computer With Feeder Protection C264P/En O/C80

Uploaded by

Copyright:

Available Formats

Micom C264P: Bay Computer With Feeder Protection C264P/En O/C80

Uploaded by

Document Information

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 C264P: Bay Computer With Feeder Protection C264P/En O/C80

Uploaded by

Copyright:

Available Formats

MiCOM C264P

MiCOM C264P Page 1/2

Safety & Handling C264P/EN SA/C80

Introduction C264P/EN IT/C80

Technical Data C264P/EN TD/C80

Functional Description C264P/EN FT/C80

Human Interface C264P/EN HI/C80

Application C264P/EN AP/C80

Lexicon C264P/EN LX/C80

Page 2/2 MiCOM C264P

SAFETY and HANDLING

MiCOM C264P Page 1/12

2. HEALTH AND SAFETY 4

3. DECOMMISSIONING AND DISPOSAL 6

4. TECHNICAL SPECIFICATIONS FOR SAFETY 7

5. HANDLING OF ELECTRONIC EQUIPMENTS 8

6. PACKING AND UNPACKING 9

8. COPYRIGHTS & TRADEMARKS 11

9. WARNINGS REGARDING USE OF SCHNEIDER ELECTRIC

Page 2/12 MiCOM C264P

MiCOM C264P Page 3/12

Page 4/12 MiCOM C264P

2. HEALTH AND SAFETY

2.1 Health and Safety

• Voltage rating and polarity;

• CT circuit rating and integrity of connections;

• Integrity of earth connection (where applicable)

MiCOM C264P Page 5/12

Insulation and dielectric strength testing

Page 6/12 MiCOM C264P

3. DECOMMISSIONING AND DISPOSAL

MiCOM C264P Page 7/12

4. TECHNICAL SPECIFICATIONS FOR SAFETY

Protective class: IEC 60255-27: 2005 Class I This equipment requires

Product Safety: 73/23/EEC Compliance with the

Page 8/12 MiCOM C264P

5. HANDLING OF ELECTRONIC EQUIPMENTS

MiCOM C264P Page 9/12

6. PACKING AND UNPACKING

Page 10/12 MiCOM C264P

MiCOM C264P Page 11/12

8. COPYRIGHTS & TRADEMARKS

Page 12/12 MiCOM C264P

9. WARNINGS REGARDING USE OF SCHNEIDER ELECTRIC PRODUCTS

MiCOM C264P Page 1/8

2. INTRODUCTION TO MiCOM GUIDES 4

3. INTRODUCTION TO MiCOM APPLICATIONS 6

Page 2/8 MiCOM C264P

MiCOM C264P Page 3/8

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

Page 4/8 MiCOM C264P

2. INTRODUCTION TO MiCOM GUIDES

MiCOM C264P Page 5/8

2.1.10 Chapter Communications (CT)

Page 6/8 MiCOM C264P

3. INTRODUCTION TO MiCOM APPLICATIONS