Micom C264/C264C: Bay Computer

MiCOM C264/C264C
Bay Computer
C264/EN O/D10

Operation Guide

Operation Guide C264/EN O/D10
MiCOM C264/C264C Page 1/2
MiCOM C264/C264C
BAY COMPUTER
CONTENTS
Safety & Handling C264/EN SA/D10
Introduction C264/EN IT/D10
Technical Data C264/EN TD/D10
Functional Description C264/EN FT/D10
Hardware C264/EN HW/D10
Connection C264/EN CO/D10
Human Machine Interface C264/EN HI/D10
Application C264/EN AP/D10
Glossary PACiS/EN LX/D10

C264/EN O/D10 Operation Guide
Page 2/2 MiCOM C264/C264C
BLANK PAGE
MiCOM C264/C264C
SAFETY & HANDLING

CONTENT
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
C264/EN SA/D10 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/H11-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 C264/C264C
INTRODUCTION
CONTENT
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 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
C264/EN IT/D10 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 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, 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 C264/C264C
TECHNICAL DATA
CONTENTS
1. SCOPE OF THE DOCUMENT 5
2. CONFORMITY 6
3. GENERAL DATA 7
3.1 Design 7
3.2 Installation Position 7
3.3 Degree of Protection 7
3.4 Weight 7
3.5 Dimensions and Connections 7
3.6 MiCOM C264 Computer: Configuration 7
3.6.1 C264 Computer – Comparison of Board Installations Between Models 8
3.6.2 C264-80TE Computer – Board Installation 10
3.6.5 C264-80TE Computer – Signals 13
3.6.6 C264C-40TE Computer – Signals 14
3.6.7 C264-60TE Computer - Signals 15
3.7 C264 Technical Data 16
3.7.1 C264: Element limits 16
3.7.2 C264: C264 with two extension racks with IEDs 18
3.8 Terminals 21
3.9 Creepage Distances and Clearances 22
4. RATINGS 23
4.1 Auxiliary Voltage 23
4.2 Power Supply 23
4.2.1 BIU241 Digital Outputs 23
4.2.2 BIU261 Dual Sources power supply board 23
4.3 Circuit breaker Control Unit (CCU) Digital Inputs 25
4.3.1 CCU200 Digital Inputs 25
4.3.2 CCU211 Digital Inputs 25
4.4 Circuit breaker Control Unit (CCU) Digital Outputs 26
4.4.1 CCU200 Digital Outputs 26
4.4.2 CCU211 Digital Output 27
4.5 Digital Input Unit (DIU) Digital Inputs 28
4.5.1 DIU200 Digital Inputs 28
4.5.2 DIU211 Digital Inputs 28
4.6 Digital Output Unit (DOU) Digital Outputs 29
4.6.1 DOU201 Digital Output 29
C264/EN TD/D10 Technical Data
4.7 Analogue Input Unit (AIU) Analogue Inputs 30

4.7.1 AIU201 Analogue Input 30
4.7.2 AIU211 Analogue Input 31
4.8 Transducerless Measurement Unit (TMU) CT/VT Analogue Inputs 32
4.8.1 General 32
4.8.2 TMU220 – Current Transformers (CT) 32
4.8.3 TMU220 – Voltage Transformers (VT) 33
4.8.4 TMU210 – Current Transformers (CT) 33
4.8.5 TMU210 – Voltage Transformers (VT) 34
4.8.6 TMU2xx - A/D Converter 35
4.9 Analogue Output Unit (AOU) 35
4.9.1 AOU200 Analogue Outputs 35
5. BURDENS 37
5.1 Auxiliary Voltage 37
5.2 Power Supply 39
5.3 CPU Boards 39
5.4 Circuit breaker Control Units (CCU) Input Burdens 39
5.4.1 CCU200 Input Burden 39
5.4.2 CCU211 Input Burden 39
5.5 Digital Input Unit (DIU) Input Burden 40
5.5.1 DIU200 Input Burden 40
5.5.2 DIU211 Input Burden 40
5.6 Digital Output Unit (DOU) Input Burden 41
5.6.1 DOU201 Input Burden 41
5.7 Analogue Input Unit (AIU) Input Burden 41
5.7.1 AIU201 Input Burden 41
5.7.2 AIU211 Input Burden 41
5.8 Transducerless Measurement Unit (TMU) CT/VT Input Burden 41
5.8.1 General 41
5.8.2 TMU210 / TMU220 Input Burden 41
5.9 Analogue Output Unit (AOU) Input Burden 41
5.9.1 AOU200 Input Burden 41
5.10 Ethernet Switches Board Input Burden 41
5.11 Front Panel Board Input Burden 41
6. ACCURACY 42
6.1 Reference Conditions 42
6.2 Measurement Accuracy 42
6.2.1 Measurement Accuracy – TMU220 42
6.2.2 Measurement Accuracy – TMU210 43
6.3 How to Measure the Isolation Resistance 43
7. TYPE TESTS 44
7.1 Dielectric Strength Tests 44
7.1.1 AIU211 – Dielectric Strength Test 44
7.1.2 ECU200/ECU201 – Dielectric Strength Test 44
7.1.3 MiCOM C264 and C264C – Dielectric Strength Test 44
7.2 Mechanical Test 45
7.3 Atmospheric Test 46
7.4 DC Auxiliary Supply Test 46
7.5 AC Auxiliary Supply Test 47
7.6 Electromagnetic Compatibility (EMC) Tests 47
BLANK PAGE
1. SCOPE OF THE DOCUMENT

This document is a chapter of the MiCOM C264 documentation, and describes the Technical
data of this computer.
2. CONFORMITY
(Per Article 10 of EC Directive 73/23/EEC).
The product designated “MiCOM C264/C264C computer” has been designed and
manufactured in conformance with the standard IEC 60255-27:2005 and is compliant with
the European Commission Low Voltage Directive 73/23/EEC.
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
− C264 with an 60TE case (C264M)
− C264 with an 40TE case (C264C)
− C264 Multirack
− C264 Multirack Redundant

NOTE: The C264 Multirack includes a C264 computer.and one or more
extension racks. Each of these computers, through its interrack
communication port, can connect to its own group of IEDs. This
extension possibility through the interrack communications port to
multiple devices, that allows for more racks with many more slots for
additional computer boards, gives us the name, Multirack. The C264
Multirack can function as a C264 Redundant computer.
3.6.1 C264 Computer – Comparison of Board Installations Between Models
Board Purpose C264 C264 C264 C264 C264

80TE 60TE 40TE Multirack Multirack
MAIN Rack Extension
Rack
BIU24x Power supply board X X X X X
CPU 270 (CPU 3) 2 Ethernet communication channels X X X X X
CCU200 Circuit breaker control unit X X X X X
CCU211 Circuit breaker control unit X X X X X
DIU200 Digital and counter acquisition X X X X X
Digital measurement acquisition
Datapoints: SPS DPS SCT DCT DM
DIU211 Digital and counter acquisition X X X X X
Digital measurement acquisition
Datapoints: SPS DPS SCT DCT DM
DOU201 Execution of single or dual, transient or permanent X X X X X
conditions
Set datapoints
AIU201 Analogue measurement acquisition X X X X X
AIU211 Analogue measurement acquisition X X X X X
TMU210 CT and VT sampling acquisition X X X X
MV calculations with acquired samples
DSPIO for TMU 210 X X X X
AOU200 Analogue output board X X X X X
SWU20x X X X X X
SWR2xx X X X X
SWD2xx X X X X X
GHU2AB: NOTE 1 Graphic panel board with LED channels GHU GHU GHU GHU GHU
2A1 202 2A0 2AB 2AB
NOTE 1:
For GHU2 A B:
B for the size

B=B includes all possibilities: B=0 or 1
B=0 Small
B=1 Large
B=2 Medium
A for the LCD

A=A includes all possibilities: A=0,1, or 2
A=0 Has LCD
A=1 Has no LCD
A=2 Has remote LCD
3.6.2 C264-80TE Computer – Board Installation

Board Slots Maximum Number of Boards
View when you look at the back of the computer that you can install
Q P O N M L K J I H G F E D C B A With TMU With No TMU
BIU24x X 1 1
CPU 270 (CPU 3) X 1 1
CCU200 NOTE 1 X X X X X X X X X X X X X X X ≤ 14 ≤ 15
CCU211 NOTE 1 X X X X X X X X X X X X X X X ≤ 14 ≤ 15
DIU200 X X X X X X X X X X X X X X X ≤ 14 ≤ 15
DIU211 X X X X X X X X X X X X X X X ≤ 14 ≤ 15
DOU201 X X X X X X X X X X X X X X X ≤ 14 NOTE 4 ≤ 15 NOTE 4
AIU201 X X X X X X X X X X X X X X X ≤6 ≤6
AIU211 X X X X X X X X X X X X X X X ≤6 ≤6
TMU210 NOTE 1 X 1 0
TMU220 NOTE 1 X 1 0
AOU200 X X X X X X X X X X X X X X X ≤4 ≤4
SWU20x X X NOTE 2 NOTE 2
SWR2xx X X NOTE 2 NOTE 2
SWD2xx X X NOTE 2 NOTE 2
GHU2A1 NOTE 3 1 1
NOTE 1: If you install a TMU, do not install the CCU in slot P and do not install the CCU in the slot adjacent to the TMU.
NOTE 2: If the board is installed in Slot C; If the rack is full; and if you have no DSPIO installed; ≤ 1
If the board is installed in Slot D; If the rack is full; and if you have a DSPIO or others installed: ≤ 1
NOTE 3: For an explanation of the GHU2AB codes, please refer to C264 Computer – Comparison of Board Installations Between Models
NOTE 4: If the application causes all of the DOs to go active at the same time: ≤ 6

View when you look at the back of the computer that you can install
L K J I H G F E D C B A With TMU With No TMU
BIU24x X 1 1
CPU 270 (CPU 3) X 1 1
CCU200 NOTE 1 X X X X X X X X X X ≤8 ≤ 10
CCU211 NOTE 1 X X X X X X X X X X ≤8 ≤ 10
DIU200 X X X X X X X X X X ≤9 ≤ 10
DIU211 X X X X X X X X X X ≤9 ≤ 10
DOU201 X X X X X X X X X X ≤ 9 NOTE 4 ≤ 10 NOTE 4
AIU201 X X X X X X X X X X ≤6 ≤6
AIU211 X X X X X X X X X X ≤6 ≤6
TMU210 NOTE 1 X 1 0
TMU220 NOTE 1 X 1 0
AOU200 X X X X X X X X X X ≤4 ≤4
GHU202 NOTE 3 1 1
NOTE 1: If you install a TMU, do not install the CCU in slot K and do not install the CCU in the slot adjacent to the TMU.
NOTE 2: If the board is installed in Slot C; If the rack is full; and if you have no DSPIO installed; ≤ 1
If the board is installed in Slot D; If the rack is full; and if you have a DSPIO or others installed: ≤ 1
NOTE 4: If the application causes all of the DOs to go active at the same time: ≤ 6

View when you look at the back that you can install
of the computer
H G F E D C B A With TMU With No TMU
BIU24x X 1 1
CPU 270 (CPU 3) X 1 1
CCU200 NOTE 1 X X X X X X ≤3 ≤6
CCU211 NOTE 1 X X X X X X ≤3 ≤6
DIU200 X X X X X X ≤3 ≤6
DIU211 X X X X X X ≤4 ≤6
DOU201 X X X X X X ≤4 ≤6
AIU201 X X X X X X ≤4 ≤6
AIU211 X X X X X X ≤4 ≤6
TMU210 NOTE 1 X=1 1 0
TMU220 NOTE 1 X=1 1 0
AOU200 X X X X X X ≤4 ≤4
GHU2A0: NOTE 3 1 1
NOTE 1: If you install a TMU, do not install the CCU in slot F and do not install the CCU in the slot adjacent to the TMU.
NOTE 2: If you do not install a DSP/DSPIO: ≤ 2 If you do install a DSP/DSPIO: ≤ 1
NOTE 3: For an explanation of the GHU2xx codes, please refer to C264 Computer – Comparison of Board Installations Between Models
3.6.5 C264-80TE Computer – Signals

Board Signals Maximum Number of Boards:
Signals that you can install
AI AO DI DO CT VT With TMU With No TMU
BIU24x 2 2
CPU 270 (CPU 3)
CCU200 NOTE 1 8 4 13: 104 DI + 52 DO 15: 120 DI + 60 DO
DIU200 16 14: 224 DI 15: 240 DI
DIU211 16 14: 224 DI 15: 240 DI
DOU201 10 14: 140 DO 15: 150 DO
AIU201 4 6: 24 AI 6: 24 AI
AIU211 8 6: 48 AI 6: 48 AI
TMU210 NOTE 1 8 4 4 1: 4 CT, 4 VT
TMU220 NOTE 1 9 4 5 1: 4 CT, 5 VT
AOU200 4 6: 24 AO 6: 24 AO
SWU20x
SWR2xx
SWD2xx
GHU2A1 NOTE 2
NOTE 1: Do not install the CCU in the slot adjacent to the TMU.
3.6.6 C264C-40TE Computer – Signals

BIU24x 2 2
CPU 270 (CPU 3)
DIU200 16 4: 64 DI 6: 96 DI
DIU211 16 4: 64 DI 6: 96 DI
DOU201 10 4: 40 DO 6: 60 DO
AIU201 4 4: 16 AI 6: 24 AI
AIU211 8 4: 32 AI 6: 48 AI
TMU210 NOTE 1 8 4 4 1: 4 CT, 4 VT
TMU220 NOTE 1 9 4 5 1: 4 CT, 5 VT
AOU200 4 4: 16 AO 6: 24 AO
SWU20x
SWR2xx
SWD2xx
GHU2A0 NOTE 2
3.6.7 C264-60TE Computer - Signals

BIU24x 2 2
CPU 270 (CPU 3)
DIU200 16 9: 144 DI 10: 160 DI
DIU211 16 9: 144 DI 10: 160 DI
DOU201 10 9: 90 DO 10: 100 DO
AIU201 4 6: 24 AI 6: 24 AI
AIU211 8 6: 48 AI 6: 48 AI
TMU210 NOTE 1 8 4 4 1: 4 CT, 4 VT
TMU220 NOTE 1 9 4 5 1: 4 CT, 5 VT
AOU200 4 4: 16 AO 4: 16 AO
SWU20x
SWR2xx
SWD2xx
GHU202 NOTE 2
.
3.7 C264 Technical Data

CAUTION: THE FULL PERFORMANCE OF THE C264 IS LESS THAN THE SUM OF
THE PERFORMANCES FOR EACH COMPONENT. FOR A DETAILED
PERFORMANCE 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
T104 protocol 4
with 4 clients managed by each
DNP3 serial protocol 2
DNP3 over IP protocol 4
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
Element Limits for 1 of C264 with

extensions
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
NOTE 1: Item: for the interlock / PSL, an item is the output of an Interlock / PSL, or an intermediate
variable used as an output (such as for the TON/TOFF/SR latch operators). In an interlock
equation, an interlock output is equal to one item.
NOTE 2: Element: After the decomposition of the equation into the sum of multiplications, an element
is the operand of an operator.
3.7.2 C264: C264 with two extension racks with IEDs

The C264 connects through Ethernet Port 1 to the SBUS and uses protocol IEC61850
The C264 connects through Ethernet Port 2 to the two extension racks
Each extension rack connects through the LBUS to the IEDs
The C264 includes a CPU 270.
CAUTION: THE FULL PERFORMANCE OF THE C264 IS LESS THAN THE SUM OF
THE PERFORMANCES FOR EACH COMPONENT. FOR A DETAILED
PERFORMANCE CHECK, PLEASE CONTACT US.
Global Limits for the C264 connected to the two extension racks and to the IEDs:
Element Maximum Number (NB) Limits

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

BI Total 5600 Including the system BI
Wired DI limits of the hardware
DI IED IEC-61850 5300
SP 256
TPI 128
Command 1200
CT Total 8 CT at 20 Hz
AI TOTAL 600
Wired AI limits of the hardware
AI IED 600
Extension racks 16 If you have 4 or more extension racks, make
sure that the MAIN rack has no I/O boards.
DIU 15
DOU 15
CCU 15
AIU 6
CT/VT 1
AOU 4
serial lines 4
SCADA Serial/Ethernet: 2
Ethernet IEC104, T104: 4
IED Total 0
State / bay 2300 Including wired DI, IED DI, system BI and
MPS
Analogue bay 221 Including wired AI, IED AI, TPI and counter
Command / bay 430 Including CO and SP
GOOSE Tx 1 GOOSE xPS, 1 GOOSE MV 128 xPS /GOOSE 64 MV / GOOSE A.C.U.
GOOSE Rx 128 A.C.U. 128 xPS /GOOSE 64 MV / GOOSE A.C.U.
PSL For example:
256 items NOTE 1
256 elements NOTE 2
Isagraf 128 TPI
256 CO
256 SP
512 CT
512 MPS
512 MV
512 SPS / DPS
NOTE 1: Item: for the interlock / PSL, an item is the output of an Interlock / PSL, or an intermediate
variable used as an output (such as for the TON/TOFF/SR latch operators). In an interlock
equation, an interlock output is equal to one item.
NOTE 2: Element: After the decomposition of the equation into the sum of multiplications, an element
is the operand of an operator.
Limits for the Extension Racks:

General BLANK If you have 4 or more extension racks, make
sure that the MAIN rack has no I/O boards
Wired DI limits of the hardware
DI IED 1000
SP 128
TPI 128
Command 1200
CT Total 128
CT wired 16 CT at 20 Hz for each extension rack Total frequency for the 16 counters is 160 Hz
8 CT at 20 Hz for the MAIN 1 rack
128 CT for a full C264
CT IED 128
AI TOTAL 600
Wired AI limits of the hardware
AI IED 600
DIU 15
DOU 15
CCU 15
CT/VT 0
AIU 6
AOU 4
serial lines 4
SCADA 0
IED 64 For the best performance, we recommend a
maximum of 10 IEDs for each link
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

In agreement with IEC 60255-27:2005 and IEC 664-1:1992.
Pollution degree 2, 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.2 A at 125 VDC 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 boards.
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 boards.
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
A04 220VDC 230VDC
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:
Nominal voltage Same for DIU200

Version Triggering threshold (VDC)
(+/-20%)
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:
Nominal voltage
Version Triggering threshold (VDC)
(+/-20%)
A01 24VDC if V >10VDC Input status is set
A02 48 thru 60VDC if V >10VDC Input status is set
A03 110 thru 125VDC if V >17.4VDC Input status is set
if V < 12.5VDC Input status is reset
A04 or 220VDC or if V > 50VDC Input status is set
A07 110 thru 125VDC if V< 29.9VDC Input status is reset
(with 80% Threshold)
A08 220VDC if V > 86VDC Input status is set
(with 80% Threshold) if V< 67VDC Input status is reset
if V > 176VDC Input status is set
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
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:
Version Nominal voltage (+/-20%) Triggering threshold (VDC)

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 24 VDC if V >10 VDC Input status is set
if V < 8 VDC Input status is reset
A02 48 to 60 VDC if V >17.4 VDC Input status is set
if V < 12.5 VDC Input status is reset
A03 110 to 125 VDC if V > 50 VDC Input status is set
if V< 20.9 VDC Input status is reset
A04 or 220 VDC or if V > 86 VDC Input status is set
A07 110 to 125VDC (with 80% Threshold) if V< 67 VDC Input status is reset
A08 220 VDC (with 80% Threshold) if V > 176 VDC Input status is set
if V< 132 VDC Input status is reset
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:

24 VDC 15V (drop off) – 19V (pick up)
48 to 60 VDC 15V (drop off) – 19V (pick up)
110 to 125 VDC 35V (drop off) – 52V (pick up)
220 VDC 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).
In the C264 rack, a DOU201 board replaces a DOU200 board. External connections remain
the same as for earlier versions of the board.
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
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: 5000 Vrms.
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 Transducerless Measurement Unit (TMU) CT/VT Analogue Inputs

4.8.1 General
For C264 and C264C computers, you can install TMU210, and TMU220 boards.
For C264 Standalone computers, these are no TMU2XX boards installaed.
For the CPU260, on the TMU board, the DSP daughter board can store data for two days.
The TMU210 board provides 4 Current Transformer (CT) inputs and 4 Voltage Transformer
(VT) Inputs.
The TMU220 board provides 4 Current Transformer (CT) inputs and 5 Voltage Transformer
(VT) Inputs.
For more installation data about these boards, please refer to the topic, MiCOM 264
Computer: Configuration.
4.8.2 TMU220 – Current Transformers (CT)
On the terminal block, there are two available nominal currents, each with different attributes.
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 0.2 A r m s 0.2 A r m s
accuracy
Maximum measurable current 4 A r m s (4*In) 20 A r m s (4*In)
Frequency 50 or 60 Hz ± 10% 50 or 60 Hz ± 10%
TMU220 CT load rating:
Strength
Duration
1A 5A
3 seconds: not measurable, with no destruction 6 A r m s (6*In) 30 A r m s (6*In)
1 second: not measurable, with no destruction 20 A r m s (20*In) 100 A r m s (20*In)
4.8.3 TMU220 – Voltage Transformers (VT)

The voltage measurement inputs to each of the 5 Voltage Transformers (VT) include the
attributes that follow:
Description Operating range

Nominal AC voltage (Vn) range 57.73 V r m s to 500 V r m s
Minimum measurable voltage 7Vrms
Maximum measurable voltage 577 V r m s
Frequency operating range 50 or 60 Hz ± 10%
VT load rating:
Duration Strength
10 seconds with no destruction 880 V r m s
4.8.4 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 0.1 A r m s 0.5 A r m s
accuracy
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.1 Ion < 0.175 VA at 0.1 Ion
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.5 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.6 TMU2xx - A/D Converter

On the TMU2xx boards, 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
360 operations each hour, on nominal load
commutation
Life Period 100 000 operations, on resistive load at 250 VAC, 8 A
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
For more specific details about the MiCOM C264 / C264C computer burdens, please refer to the table that follows:
Computer Version Case Size Voltage Nominal Maximum

50% of the DI energized and All DI and all relays
one relay per board energized energized
C264 A01 24VDC 30VADC 31WAC 39VADC 39WAC
C264 A02 48 thru 60VDC 35VADC 36WAC NA NA
C264 A03 C264 (4U – 80TE) 110 thru
125VDC
C264 A04 220VDC and 39VADC 40WAC NA NA
230VAC
C264M A01 24VDC 30VADC 31WAC 39VADC 39WAC
C264M A02 48 thru 60VDC 35VADC 36WAC NA NA
C264M A03 C264M (4U – 60 TE) 110 thru
125VDC
C264M A04 220VDC and 39VADC 40WAC NA NA
230VAC
C264C A01 24VDC 12VADC 13WAC 17VADC 17WAC
C264C A02 48 thru 60VDC 16VADC 17WAC 22 VADC 22 WAC
C264C A03 C264C (4U – 40TE) 110 thru
125VDC
C264C A04 220VDC and 19VADC 20WAC 27VADC 27 WAC
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 3: 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) CT/VT Input Burden
5.8.1 General
N.A.
5.8.2 TMU210 / TMU220 Input Burden
For the TMU210 / TMU220 boards, the input burdens on the internal transformers follow:
CT burden (at nominal current – In) Nominal consumption (VA)
TMU210 TMU220
1A < 0.02 < 0.02
5A < 0.02 < 0.2
VT burden (at nominal voltage – Vn) Nominal consumption (VA)
TMU210 TMU220
Vn = 130 V r m s < 0.01 < 0.01
For the TMU210 board, the input burden on the internal 5V bus is 300mW.
For the TMU220 board, the input 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

6.2.1 Measurement Accuracy – TMU220
The TMU220 board includes the attributes that follow:
Quantity Accuracy
Current 0.2% full scale
Voltage 0.2% full scale
Frequency ± 0.01 Hz
Amplitude < 1%
Phase ± 1°
Overall temperature coefficient ± 10 ppm/°C
Harmonics H15
6.2.2 Measurement Accuracy – TMU210

The TMU210 board includes the attributes that follow:
Measurement Range Deviation

Phase current 0.1 to 40 In Typical ±0.5% at In
Earth current 0.002 to 1 Ion 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%
6.3 How to Measure the Isolation Resistance

To measure the isolation resistance, do the steps that follow:
1. Apply a continuous voltage of 500 V to the two points.
2. Wait a minimum of 5 seconds to stabilize the reading.
3. Make a record of the isolation resistance.
4. The isolation resistance must be higher than 100 M ohms, in agreement with procedure
LQD/P52/1
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 C264/C264C
FUNCTIONAL DESCRIPTION
CONTENTS

1.1 Software features 9
1.2 C264 Configurations 10
1.2.1 SBUS - C264 with no IED 10
1.2.2 SBUS - C264 with IEDs 11
1.2.3 SBUS - C264 with two extension racks with IEDs 12
1.2.4 SBUS - Two C264 redundant computers with IEDs 13
1.2.5 SBUS - Two C264 redundant computers with two extension racks with IEDs 14
1.2.6 SCADA – TBUS - C264 Standalone computer with no IEDs 15
1.2.7 SCADA – TBUS - C264 Standalone computer with IEDs 16
1.2.8 SCADA – TBUS - C264 Standalone with two extension racks with IEDs 17
1.2.9 SCADA – TBUS - Two C264 Standalone computers, redundant 18
1.3 CPU Boards: CPU260 Compared with CPU 270 20
1.4 C264 Standalone 20
2. MiCOM C264 MANAGEMENT 21

2.1 Operating mode management 21
2.1.1 Definitions 21
2.1.2 Initialisation mode 21
2.1.3 Operational mode 22
2.1.4 Maintenance mode 23
2.1.5 Test mode = DSPIO Maintenance Mode 24
2.1.6 Faulty mode 27
2.1.7 Halt mode 27
2.1.8 Summary of modes, tests, transitions, and faults 27
2.1.9 Redundancy Mode management 28
2.2 Database management 32
2.2.1 General 32
2.2.2 How to download a database through the Ethernet 34
2.2.3 How to switch the databases 35
2.2.4 How to do a check of the database 36
2.2.5 How to modify the database 36
2.2.6 How to modify a parameter setting in the current DB 37
2.2.7 How to consult a parameter setting 37
2.3 Self tests 37
C264/EN FT/D10 Functional Description
2.4 Time management 38

2.4.1 External clock 39
2.4.2 Clock synchronisation message from a SCADA gateway 40
2.4.3 SNTP Client and Servers 40
2.4.4 Time set by an operator 40
2.4.5 Local clock update 41
2.4.6 Management of loss of external time reference 42
2.4.7 Update method 42
2.4.8 Limits and performances 42
3. COMMUNICATIONS 43
3.1 Telecontrol bus - TBUS 44
3.2 Legacy bus - LBUS 44
3.3 Station bus - SBUS 45
3.3.1 Exchanges 45
3.3.2 Supported Common Data Classes 47
3.3.3 Controls 47
3.4 Inter-rack Ethernet communication 48
3.4.1 Internal Ethernet architecture 48
3.4.2 External network behaviour 48
3.4.3 Ethernet failure 49
3.4.4 Other Ethernet rupture 50
3.4.5 Ethernet Routing table 50
3.5 Ethernet port management on CPU Type 3, CPU 270 51
3.6 Telecontrol Bus redundancy 52
3.6.1 Overview 52
3.6.2 Link Redundancy 52
3.6.3 Protocol Redundancy 53
3.6.4 TBUS Redundancy T101 example 54
3.6.5 Event file synchronization 55
4. DIRECT PROCESS ACCESS 56

4.1 Input Check 56
4.2 Output check 56
4.3 Time tagging 56
4.4 Digital input acquisition (DI) 56
4.4.1 Acquisition 56
4.4.2 Debouncing and filtering 57
4.4.3 Toggling 57
4.5 Counters acquisition (CT) 58
4.5.1 Single counter (SCT) 58
4.5.2 Double counter (DCT) 59
4.6 Digital measurement (DM) 60

4.6.1 Acquisition without Read Inhibit signal 60
4.6.2 Acquisition with Read Inhibit signal 61
4.6.3 Encoding 62
4.7 Analogue input acquisition (AI) 63
4.7.1 Input ranges 63
4.7.2 Acquisition cycle 63
4.8 Digital outputs (DO) 63
4.9 Digital Setpoints: SPS, DPS, MPS 64
4.9.1 Encoding 64
4.9.2 Read Inhibit 64
4.9.3 Open / Close Select Order 65
4.10 Analog Setpoints 66
4.10.1 Output range 66
4.10.2 Output management 66
4.10.3 AOU Watchdog management 67
5. DATA PROCESSING 68
5.1 Binary Input Processing 68
5.1.1 Binary Input Definition 68
5.1.2 Processing of Single Point Status 69
5.1.3 Processing of Double Point Status 71
5.1.4 Processing of Multiple Point Status 76
5.1.5 System Inputs (SI) 77
5.1.6 IED inputs 78
5.1.7 Group processing 78
5.1.8 SBMC Mode Processing 79
5.1.9 BI sent to automatism features 79
5.2 Measurement Input Processing 80
5.2.1 Measurement Input Processing - Focus 80
5.2.2 Focus 1: Analogue Measurement Processing as far as Threshold Detection 81
5.2.3 Open circuit management 81
5.2.4 Scaling 81
5.2.5 Zero value suppression 82
5.2.6 Focus 2: Digital Measurement Processing as far as Threshold Detection 82
5.2.7 Focus 3: TMU2XX: CT/VT measurement processing as far as Threshold Detection 83
5.2.8 TMU2XX: CT / VT Calculations - General 84
5.2.9 TMU220: CT / VT Calculations – Inputs: Configuration 87
5.2.10 TMU220: CT / VT Calculations - Inputs: Samples 87
5.2.11 TMU220: CT / VT Calculations – Outputs: Set of measurements 88
5.2.12 TMU220: Measurements - General 89
5.2.13 TMU220: List of Measurements 90
5.2.14 TMU220: Algorithms 93
5.2.15 TMU210: CT / VT Calculations - Inputs: Configuration 95

5.2.16 TMU210: CT / VT Calculations - Inputs: Samples 95
5.2.17 TMU210: CT / VT Calculations – Outputs: Set of measurements 96
5.2.18 TMU210: Measurements - General 96
5.2.19 TMU210: List of Measurements 98
5.2.20 TMU210: Algorithms 100
5.2.21 Focus 4: All Measurement Values: Threshold Detection thru Transmission 108
5.2.22 Manual suppression 109
5.2.23 Substitution 109
5.2.24 Forcing an invalid measurement 109
5.2.25 Measurement resulting states 109
5.2.26 Transmission 110
5.3 Tap Position Indication (TPI) measurement processing 112
5.3.1 Acquisition from Digital Inputs 112
5.3.2 Acquisition from Analogue Inputs 112
5.3.3 Manual suppression 112
5.3.4 Substitution 112
5.3.5 Forcing an invalid TPI 112
5.3.6 TPI resulting states 113
5.3.7 Transmission 113
5.4 Accumulator Input Processing 114
5.5 Energy counting 114
5.6 Basic Data Manipulation 115
5.6.1 Test Mode enhancements 115
5.6.2 Device order running 115
5.6.3 Controls management from PSL 116
5.6.4 PSL and Redundant Operation 117
6. CONTROL SEQUENCES 118

6.1 Description 118
6.1.1 General 118
6.1.2 Control sequence phase management 119
6.1.3 Direct Execute mode 122
6.1.4 SBO once mode 123
6.1.5 SBO many mode 126
6.1.6 Generic selection checks 128
6.1.7 Selection behaviour 132
6.1.8 Generic execution checks 133
6.1.9 Execution behaviour 133
6.1.10 Controls time sequencing 134
6.1.11 How an xPS starts a control sequence with following data 137
6.1.12 Attribute Words definition 139
6.2 Control of non synchronised breakers 143

6.2.1 Non synchronised circuit breaker features 143
6.2.2 Control sequence of non-synchronised circuit breakers 143
6.3 Control of synchronised breakers 144
6.3.1 Synchronised circuit breaker features 144
6.3.2 Circuit breakers with external synchrocheck 145
6.3.3 Circuit breakers with internal synchrocheck 150
6.4 Control of disconnectors 154
6.4.1 Disconnectors features 154
6.4.2 Control sequence of disconnectors 154
6.5 Control of transformers 155
6.5.1 Transformer features 155
6.5.2 Control sequence of transformers 155
6.6 Control of ancillary devices 158
6.7 Control of Intelligent Electrical Devices (IED) 159
6.7.1 Control to IEDs 159
6.7.2 IED controls 159
6.7.3 Digital setting point (SP) 159
6.8 System controls 160
6.9 Kinds of control sequences 160
6.10 Control sequences checks 160
6.10.1 Mode Management 160
6.10.2 IED connected 160
6.10.3 Control mode 161
6.10.4 Uniqueness of control 161
6.10.5 Inter-control delay 161
6.10.6 Status of the device 161
6.10.7 Lock device 161
6.10.8 Running Automation 161
6.10.9 Interlocking 161
6.11 HV Control Sequences 162
6.11.1 Circuit breaker 162
6.11.2 Disconnector 162
6.11.3 Transformer 162
7. AUTOMATIONS 163
7.1 Built-in Automation functions 163
7.1.1 Auto-Recloser (AR) 163
7.1.2 Trip Circuit Supervision 169
7.1.3 Circuit breaker condition monitoring (I²t) 171
7.1.4 Automatic Voltage Regulation–AVR 173
7.1.5 Automatic voltage regulation–ATCC 188
7.2 Synchrocheck 201

7.2.1 Synchrocheck – General 201
7.2.2 Synchrocheck Schemes 202
7.2.3 Synchrocheck Algorithm 202
7.2.4 Synchrocheck Applications 203
7.2.5 Synchrocheck Circuit Breaker Closure types 203
7.2.6 Synchrocheck Type 1 and Type 2 203
7.2.7 Synchrocheck Hardware constraints and use 204
7.2.8 Synchrocheck Calculation 204
7.2.9 Synchrocheck Introduction to Harmonics 204
7.2.10 Synchrocheck – Check Synchronising – Locking Mode 204
7.2.11 Synchrocheck – System Synchronising – Coupling Mode 204
7.2.12 Synchrocheck: Scheme LL: Live Line, Live Bus: Real Time Sequences 205
7.2.13 Synchrocheck Schemes that use VLINE and not(VBUSBAR) or not(Vline) and
VBUSBAR voltage controls 207
7.2.14 Synchrocheck Schemes that use not(Vline) and not(VBUSBAR) voltage control 208
7.2.15 Synchrocheck Schemes that use Vline and Vbusbar voltage control 208
7.2.16 Synchrocheck Type 1 - Logic of Interlock Authorisation 210
7.2.17 Synchrocheck Type 2 - Logic of Interlock Authorisation 210
7.2.18 Synchrocheck Bypass 211
7.2.19 Phase-to-Phase Synchrocheck with the TMU210 213
7.2.20 Synchrocheck Close request 214
7.2.21 Synchrocheck General Configuration 215
7.2.22 Synchrocheck Voltage control 215
7.2.23 Synchrocheck Schemes control 216
7.2.24 Synchrocheck Parameters of the TMU2xx board 216
7.2.25 Synchrocheck Internal parameters 217
7.2.26 Synchrocheck Digital Output (DO) of the circuit breaker 218
7.3 Interlocking: logical equations 219
7.3.1 Interlocking: Inputs 219
7.3.2 Interlocking:Outputs 219
7.3.3 Interlocking: Control 219
7.3.4 Interlocking: Behaviour 219
7.4 Slow automation: Programmable Logic Control (PLC) 223
7.4.1 Inputs 224
7.4.2 Outputs 224
7.4.3 Control 224
7.4.4 Behaviour 225
7.4.5 Limits and specifications 225
7.5 Fast automation: Programmable Scheme Logic (PSL) 226
7.6 Fast Load Shedding ( FLS ) 227
7.6.1 C264M 227
7.6.2 C264Fi 227
7.7 Load Shedding – C264 Standalone 227

7.7.1 Inputs 227
7.7.2 Algorithm 228
7.7.3 Outputs 230
7.7.4 Hypothesis and Constraints 230
7.7.5 Configurable data 231
7.8 Load Curtailment – C264 Standalone 232
7.8.1 Inputs 232
7.8.2 Algorithm 232
7.8.3 Outputs 234
7.8.4 Hypothesis and Constraints 234
7.8.5 Configurable data 235
8. USER INTERFACE 236
9. RECORDS 237
9.1 Permanent records storage 237
9.1.1 Data storage 237
9.1.2 Waveform Recording: General 237
9.1.3 Events 237
9.1.4 Fast Waveform Recording 238
9.1.5 Slow Waveform Recording 238
9.1.6 Slow Waveform Recording – Hypothesis 240
9.1.7 Disturbance Recorder 240
9.2 Non-permanent data storage 242
9.2.1 Alarms 242
BLANK PAGE

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
Automatic Voltage Regulation (AVR)
Automatic Tap Change Control (ATCC)
Synchrocheck
Synchrocheck Bypass
Phase-to-Phase Synchrocheck with the TMU210
Depending on whether the Main Rack is redundant or not, the software features are different
for a redundant main 1 rack and for a non-redundant main rack.
1.2 C264 Configurations
The MICOM C264 computer is the base module of the PACiS architectures.
Each C264 computer includes a rack. Computer boards are installed on the rack. The rack is
the technical name, but it can have different functional names.
The functional name depends where the C264 computer is installed in a system. The
functional names for the rack include:
• Main rack: In a standalone system, the first (only) rack
• Main 1 rack: In a redundant system, the active rack
• In a multirack system, the active first rack
• Main 2 rack: In a redundant system, the standby rack
• Extension rack: In a multirack system, one or more extension racks that cascade
from the active Main 1 rack or standby Main 2 rack
• Multirack system: A system that includes a Main rack and one or more extension
racks
• Redundant system: A system that includes an active Main 1 rack and a standby Main
2 rack
The family of C264 computers included in this chapter include the devices and configurations
that follow:
1.2.1 SBUS - C264 with no IED
The C264 connects through the Ethernet Port to the SBUS and uses protocol IEC61850.
1.2.2 SBUS - C264 with IEDs

The C264 connects through the Ethernet Port to the SBUS and uses protocol IEC61850.
The C264 connects through the LBUS to the IEDs.
1.2.3 SBUS - C264 with two extension racks with IEDs

The C264 connects through Ethernet Port 1 to the SBUS and uses protocol IEC61850
The C264 connects through Ethernet Port 2 to the two extension racks
Each extension rack connects through the LBUS to the IEDs. The C264 includes a CPU 270.
IEC 61850
SBUS
Ethernet port 1
C264
Main
Rack
Ethernet port 2 LBUS

Inter Rack Extension
connection Rack
LBUS
Extension
Rack
C0435ENb
For more technical data about the C264 with two extension racks with IEDs, please refer to
the chapter Technical Data.
1.2.4 SBUS - Two C264 redundant computers with IEDs

Each C264 connects through the Ethernet Port 1 to the SBUS and uses protocol IEC61850
Each C264 connects through the LBUS to the IEDS
IEC 61850
SBUS
C264 C264
Main 1 I/O Main 2
Rack redundancy Rack
IED
LBUS
IED
IED
C0436ENb
1.2.5 SBUS - Two C264 redundant computers with two extension racks with IEDs
Each C264 connects through the Ethernet Port 1 to the SBUS and uses protocol IEC61850
Each C264 connects through Ethernet Port 2 to two extension racks
Each extension rack connects through the LBUS to the IEDs. These C264s each include a
CPU 270.
For more technical data about the two C264 redundant computers with two extension racks
with IEDs, please refer to the chapter Technical Data C264/EN TD/Cxx.
1.2.6 SCADA – TBUS - C264 Standalone computer with no IEDs

The C264 connects through the Ethernet port through the TBUS to the SCADA
In the C264 Standalone configuration, you do not have C264 redundancy nor the multi rack.
Only one C264 Standalone computer is provided. The main rack (not redundant) manages
the direct acquisitions and controls. The C264 Standalone computer with the main rack:
• Manages the communications with the SCADA
• Receives all data from the IO boards on the rack and updates the archives (SOE
waveform)
• Transmits with the SCADA
• Manages the database downloads through the SCADA connection
• Manages the controls received through the active SCADA connection and sends them
to the extension racks
• Manages the digital input and measurement acquisition. In event the main 1 rack and
main 2 rack are in a redundant configuration, this function is not available.
• Manages the controls. In event the main 1 rack and main 2 rack are in a redundant
configuration, this function is not available.
NOTE: The C264 Standalone is the new technical name for the C264 Remote
Terminal Unit (RTU).
1.2.7 SCADA – TBUS - C264 Standalone computer with IEDs

The C264 connects through the Ethernet port through the TBUS to the SCADA
The C264 connects through the LBUS to the IEDs
TBU
C264
Main
Rack
LBUS
In the C264 Standalone configuration, you do not have C264 redundancy nor multi rack
configuration. Only one C264 Standalone computer is provided. The main rack (not
redundant) manages the direct acquisitions and controls. The C264 Standalone computer
with the main rack:
• Receives all data from the IO boards on the rack and updates the archives (SOE
waveform)
• Transmits with the SCADA
• Manages the digital input and measurement acquisition. In event the main 1 rack and
Main 2 rack are in a redundant configuration, this function is not available.
• Manages the controls. In event the main 1 rack and main 2 rack are in a redundant
configuration, this function is not available.
• Manages the communication with the IEDs, and the acquisition of the real time data.
In event the main 1 rack and main 2 rack are in a redundant configuration, this
function is not available.
1.2.8 SCADA – TBUS - C264 Standalone with two extension racks with IEDs
The C264 connects through the Ethernet Port 1 through the TBUS to the SCADA
The C264 connects through the Ethernet Port 2 to two extension racks.
Each extension rack connects through the LBUS to the IEDs. This C264 includes a CPU
270.
TBUS
Main
Rack
Extension LBUS
Rack
Extension LBUS
Rack
C0440ENb
The main rack centralises all of the data acquired by all of the extension racks, and manages
the SCADA interface. In this configuration, you can configure as many as 16 extension
racks. The main rack (non redundant) manages direct acquisitions and controls. The main
rack:
• Receives all data acquired from the extension rack and updates the archives (SOE
waveform)
• Transmits all of this data through the SCADA interface
• Manages the communication with the SCADA
• Manages the database downloads through the SCADA connection and distributes the
new configuration to all of the other extension racks
• Receives the controls through the SCADA connection, manages the controls, and
sends the controls to the extension racks
• Manages the digital input and measurement acquisition. In event of a redundant

configuration, this function is not available
• Manages the control, that is directly handled by the main rack. In event of a redundant
configuration, this function is not available
• Manages the communication with the IEDs, and real-time data acquisition. In event of
a redundant configuration, this function is not available.
The extension racks:
• Send all of the acquired data to the main rack
• Manage the controls that they receive from the main rack
• Manage the digital and measurement acquisition
• Manage the IED communication and real-time data acquisition
• If there are no serial ports available on the main rack, the extension rack can manage
the printer.
There is no rack to manage the Automation functions: Auto-recloser, Synchrocheck, AVR,
ATCC. You can install a CPU2 or CPU3 on the main rack and on the extension rack. If you
install a CPU3 in the extension rack, you must use a CPU3 on the main rack.
1.2.9 SCADA – TBUS - Two C264 Standalone computers, redundant
Each C264 connects through the Ethernet Port 1 through the TBUS to the SCADA
Each C264 connects through Ethernet Port 2 to two extension racks
Each extension rack connects through the LBUS to the IEDs. This C264 includes a CPU
270.
Serial Serial
Port 1 Port 2
TBUS TBUS
Serial Serial
Port 1 Port 1
Main 1 Main 2
Rack Rack
LBUS
Extension
Rack
IED
IED
Inter-rack Ethernet
communication IED
Extension
Rack
IED
IED
IED
C0441ENc
The main 1 rack and the main 2 rack centralise all of the data acquired by the extension
racks and manage the SCADA interface. In this redundant C264 Configuration:
• There are no I/O boards installed in the main 1 rack or in the main 2 rack
• There are no PSL or Isagraf functions available
• There are no IEDs connected to the serial ports of the main 1 rack and main 2 rack
Of the two computers, SCADA makes the selection and designates one computer as the
main 1 rack and the other computer as the main 2 rack.
• Neither the main 1 rack nor the main 2 rack manage these Automations: PSL, PLC,
Auto-recloser, Synchrocheck, AVR, ATCC.
• For hardware, the main 1 rack and main 2 rack are identical.
The main 1 rack:
• Manages the communication with the SCADA
• Receives all of the data acquired on the extension racks and updates the archives
(SOE waveform)
• Transmits through the SCADA of all this data
• Manages the database downloads through the SCADA connection and distributes the
new configuration to all of the other extension racks and to the main 2 rack
• Receives the controls through the SCADA connection, manages the controls, and
sends the controls to the extension racks.
The main 2 rack:
• Receives all of the data acquired on the extension racks and updates the archives
(SOE waveform)
• Freezes all of the transmissions on the SCADA link: Reset of the Link: Function 0
• In event of a SCADA General Interrogation (GI Request) to the main 2 rack, the main
2 rack assumes the functions of the main 1 rack
• Receives the configuration database from the main 1 rack and updates it
• Communicates the status of the main 1 rack and main 2 rack to the SCADA. You can
connect the watchdog relays to the standard DI of one extension rack.
1.3 CPU Boards: CPU260 Compared with CPU 270

The CPU260 board is also referred to as the CPU Type 2 or CPU2.
The CPU270 board is also referred to as the CPU Type 3 or CPU3.
For the functions available on the C264 CPU2 and CPU3, please refer to the table that
follows:
Function CPU 260 CPU 270

CPU Type 2 CPU Type 3
CPU2 CPU3
Circuit breaker condition monitoring I²T No Yes
Control Sequence launched by xPS Yes Yes
Automatic Voltage Regulation No Yes
Synchrocheck for TMU210 No Yes
Limits improvement: please refer to No Yes
SCE/EN_TD/Cxx.
Counter management No Yes
1.4 C264 Standalone

The C264 Standalone computer includes the functions that follow:
Function Available on the C264

Standalone
ISAGRaF Yes
PSL Yes
Load Shedding Yes
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.
Functional Description C264/EN FT/C50
MiCOM C264 Page 25/234
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:
CAT request
STOPPED
reboot (CAT request),

on/off power supply,
CAT request
DB/software compatibility not OK
or
CAT request DB/equipment compatibility not OK
or
data of database not valid
INITIALISATION or no DB
reboot , reboot,
on/off power supply reboot ,
on/off power on/off power supply,
Init OK automatic reboot
supply
after a switch DB
hardware test OK
FAULT and coherency not OK
reboot ,
on/off power
major hardware supply
fault
operator request,
Switch DB/clean DB
operator request
TEST OPERATIONAL MAINTENANCE
operator request,
end of active mode
major software major software major software

fault fault fault
Counter faults <

Max_Fault in delay
Control
error
Counter faults =
Max_Fault in delay
reboot,
HALT on/off power
supply,
operator request,
Switch DB C0288ENa
2.1.9 Redundancy Mode management

Two identical computers with the same hardware and the same database versions manage
the main 1 rack redundancy.
• For the C264 Multirack system:

The two SCADA connections, one to the main 1 rack and one to the main 2 rack, are
completely independent. For these two connections, there is no synchronisation of protocols,
and each of these racks can have a different station address. The principle here is different
from the standard redundant function, where the sequence of the messages on each
connection are synchronised and where each rack has the same station address.
In the redundant configuration, the main 1 rack does not manage direct acquisitions,
controls, or IED connections.
The main 1 rack and the main 2 rack have a single address on one of the two SCADA
connections. This allows the main 1 rack and the main 2 rack to manage two different
networks.
The main 1 rack operates when:
− The communication was set up on the main 1 rack connection to the SCADA. The GI
request (ASDU 100) message confirms the set-up of the connection.
− The main 2 rack was in operation, a failure occurred, and the main 1 rack received a
GI request.
When the SCADA detects a communication failure, the main 1 rack in operation becomes
the main 2 rack. The SCADA must stop to communicate with one rack when it decides to
communicate with the other rack.
For more details, please refer to the figure that follows:
C0447ENa
The main 1 rack:
• Receives all of the data acquired on the extension rack and updates the archives
(SOE, slow waveform)
• Transmits all of the data acquired on the extension rack through the SCADA
• Receives the database through the SCADA connection or from the CAT and
distributes the new configuration to all of the other racks, including the main 2 rack
The main 2 rack:
• Receives all of the data acquired on the extension rack and updates the archives
(SOE, slow waveform)
• In event of a SCADA connection reset (GI Request), the main 2 rack does the
functions of the main 1 rack
• Receives the configuration database from the main 1 rack and updates its own
configuration database
To communicate the status of the main 1 rack and main 2 rack to the SCADA, you can wire
the watchdog relays to the standard DI of one extension rack.
For the C264:
The two redundant computers are the main 1 computer and the main 2 computer. The
computer that performs the bay management is the active computer; the other one is the
standby computer. In this configuration, the redundant computer can be:
• Main 1 computer in active mode
• Main 1 computer in standby mode
• 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 C264 receives the database file and saves it in RAM, but does not send it
to the other racks.
On the C264, the database status shows only on the main rack LCD.
The main 1 rack does a check for the compatibility between its database and the database
installed in the main 2 rack and in the extension racks. It the databases are different, the
main 1 rack has the most recent version and deletes the databases on the other racks.
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 Modified Standby Modified
A file descriptor with the label DB context, stored in the flash memory of the computer,
includes the configuration of the DB installed on the device. 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:
− Removes a possible standby DB and related Vdbs already installed in the

computer
− Assigns the state standby to the downloaded DB and related Vdbs installed in the
computer
− 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
FIGURE 4: DATABASE DOWNLOAD
After a successful database download, the SCADA sends the switch command with the “Reset
process command” standard message (ASDU 105) to the computer.
When the computer receives the switch command, the computer downloads the database to
the other racks. Please refer to Figure 5: Database Switching
FIGURE 5: 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:
− Is the object known to the computer, that is, is the object really present in the
database
− Can the computer set the data
− Is the value of the parameter setting compatible with the type of data conveyed:
does the value belong 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:
− Is the object known to the computer, that is, is the object really present in the
database
− Can the computer set the data
− Is the value of the parameter setting compatible with the type of data conveyed:
does the value belong 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 , 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 time2

There is a priority rule for these four external time references. If the external clock operates,
it locks out changes from the three other sources: you cannot make modifications to the local
clock in these ways:
• Locked out: SCADA sends a clock message through the TBUS and through the
gateway
• Locked out: The system master clock sends a clock message through the SBUS
• Locked out: An operator who sets the time

For the C264 Multirack system, the main 1 rack delivers time synchronization for the main 2
rack and for the extension racks.
In event an external clock disconnects or does not operate, there is a priority order for the
three external time references that remain:
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.
1
For all C264 computers
2
For all C264 computers except C264 Standalone computers
The organization of the time management follows:
FIGURE 6: 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:
1. 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).
2. 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
The C264 includes different types of communications:
• Telecontrol Bus (TBUS)
• Legacy Bus (LBUS)
• Station Bus (SBUS)
• Inter-rack Ethernet communications.

For the C264, the possible combinations of protocols follow:
Item For this number You can have this Total number of protocols
of Protocols on number of Protocols
allowed
the TBUS on the LBUS
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
The basic communications follow:
SCADA PACiS System, IEC 61850 IEDs
TBUS SBUS
Telecontrol Interface IEC 61850
C264 Computer Kernel
Legacy Gateway I / O Boards
LBUS
IED
C0005ENd
FIGURE 7: COMMUNICATIONS
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 Type C264 C264 BCU C264 Standalone

behaves as
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, you can connect as many as 4 independent clients.
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: 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 & sends data on IEC-61850 network using REPORT/ GOOSE.
The REPORT is specific between a server and one client, it provides:
• data value
• data state or quality attribute (validity and several kind of invalid state)
• time tag of last data value change
• time tag quality attribute (server 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.
REPORTS
SCADA
PACiS HMI PACiS HMI

GTW Main
Server Client
C264
GTW is a
Report Client GTW Backup
Red
link
HMI is a Report
Client
Report Client
IEC 61850 UPPER NETWORK (TBUS)
AP2
IEC/IEC GTW1 IEC/IEC GTW2
Main Backup
Red
GTW1 is a Report Server link GTW is a Report Client
(4 buffered clients maxi)
+
GTW is a Report Client AP1
IEC 61850 LOWER NETWORK (SBUS)
C264
C264 is a Report Server
(4 buffered clients Maxi)
IED
PACiS HMI 1 PACiS HMI 1 IEC 61850
Server Client
PACiS HMI 1 Server
is a Report Client
C264 computer provides BRCB (buffered report) to PACiS device clients. A device client is
either HMI (OI / SUI) or IEC/IEC Gateway connected on IEC 61850 SBUS. Total BRCB
client is limited to 4.
C264 records only ST events in buffer to generate buffered report. Buffers are cyclical, FIFO
and unitary event replacement. One Buffer Overflow Information is available for each client
of buffer report configured with SCE.
IEC61850 Device BRCB Client BRCB Server

GTW YES YES (on TBUS only)
C264 NO YES
OI YES NO
SUI YES NO
C264 BRCB Server BRCB Client Buffer Overflow Buffer Capacity

information
Buffer 1 OI / SUI Main YES 100 ST events
Buffer 2 OI / SUI Standby YES 100 ST events
Buffer 3 Gateway 1 Main YES 100 ST events
Buffer 4 Gateway 2 Backup YES 100 ST events
Note: Data are buffered only after connection established once between
C264 BRCB server and its client
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 Inter-rack Ethernet communication

3.4.1 Internal Ethernet architecture
The internal communication on the Ethernet C264 network uses proprietary protocol with
unicast messages. Consecutively all messages used by the computer for internal data
exchanges remain inside the C264. These messages do not pollute the external network
reserved for the SCADA interface.
Furthermore, the CAT tool uses also the Ethernet broadcast to identify racks. This tool is
used only for maintenance purpose (Software and configuration downloading)
Acquisition and front-end racks must have the same group number when they are attached
to the same C264. This group number is defined using the CAT and is limited to 16.
3.4.2 External network behaviour
Due to the connection of the C264 with the external network for the SCADA communication
(T104) a precaution shall be taken in order to avoid Ethernet loops. External switches of the
upstream communication must be able to use the spanning tree algorithm to prevent
Ethernet loops.
The Spanning Tree (802.1D) or the Fast Spanning Tree (802.1W) algorithm of the external
switches identifies the Ethernet ring created with the external and internal Ethernet
infrastructure and computes the appropriate path avoiding Ethernet Loops.
The computation of the network tree is done only one time by the spanning tree algorithm of
External switches.
3.4.3 Ethernet failure
Ethernet ring opening
The consequence of the ring opening involves to lose the communication between the Main
1 rack and the Main 2 rack.
Consecutively we have:
- Data transfer from extension rack #1 through the External Ethernet infrastructure
(outside the C264 Ethernet network) to the Main 2 rack.
- Ethernet ring opening and rebuilding of routine table ordered by the spanning tree
algorithm (> 30 s if 802.1D used)
3.4.4 Other Ethernet rupture
T104 T104
C264 C264
Main 1 Rack Main 2 Rack
C264
CAT Extension Rack No.1
C264
Extension Rack No.2
Ethernet Link
Ethernet Switch
C0455ENb
The other events of rupture of the Ethernet C264 network do not involve:
- Data Routine outside of the internal Standalone Ethernet network
- Starting of the spanning tree algorithm (Ethernet ring maintained)
All data produced by the insulated rack are defined in an unknown state.
The other racks of the C264 (remaining on Ethernet continuity) are fully operational. Data
transferred to the Main racks through the Standalone private communication do not use the
external Ethernet infrastructures.
3.4.5 Ethernet Routing table
C264 connects to a router and a remote IEC104 SCADA
3.5 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
SCADA IP 1 protocols 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 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 8: CAT SHOWING TWO ETHERNET PORTS

3.6 Telecontrol Bus redundancy

3.6.1 Overview
The C264 may be redundant in the PACiS system in order to ensure the quality of service
incase of a communication failure.
The C264 communication with the SCADA uses Serial links or Ethernet link.
The management of TBUS redundancy is driven by SCADA.
There are 2 redundancy types
• Link Redundancy (for e.g. 2 lines for the one protocol).
• Protocol Redundancy (for e.g. the same protocol on the 2 devices).

3.6.2 Link Redundancy
The Link Redundancy is a same protocol and data on a redundant link managed by SCACA.
(The Link Redundancy is a same protocol and data are sent or received through 2 redundant
links). The SCADA manages the switching redundant link. It chooses the active link. The
switching conditions are described in the SPP_T101.
The Link Redundancy is applicable for MiCOM C264 RTU standalone and C264 BCU
configuration.
The Link Redundancy is applicable for serial (RS232/485) lines only.
TBUS
Serial Serial
Port 1 Port 2
Serial Serial
Port 1 Port 2
FIGURE 9: LINK REDUNDANCY

C264 connects through the Serial Port 1 and Serial Port 2 through the TBUS to the SCADA.
CAUTION: THE LINK REDUNDANCY IS NOT APPLICABLE FOR PROTOCOLS
USING EHERNET LINK.
3.6.3 Protocol Redundancy

The Protocol Redundancy is an identical or a same protocol with separate dynamic data to
transmit when asked by SCADA. The SCADA drives the switching C264 redundant link.
The Protocol Redundancy is applicable for C264 RTU standalone configuration only.
The protocol redundancy is supported by T101 only.
Serial Serial
Port 1 Port 2
TBUS TBUS
Serial Serial
Port 1 Port 1
Main 1 Main 2
Rack Rack
Event files
synchronisation
LBUS
Extension
Rack
IED
IED
Inter-rack Ethernet
communication IED
(NOTE1)
Extension
Rack
IED
IED
IED
FIGURE 10: PROTOCOL REDUNDANCY

NOTE: The Ethernet inter-rack uses swich(es). For more explanations, please
refer to the section § 3.4 Inter-rack Ethernet communication (C264/EN
FN).
Each C264 connects through the Serial Port through the TBUS to the SCADA. Each C264
connects through Ethernet Port 2 (InterRack) to two extension racks. Each extension rack
connects through the LBUS to the IEDs.
The Main 1 rack and the Main 2 rack receive all data acquired by the extension racks and
manage the SCADA interface.
SCADA makes the selection and designates one computer as the "Main rack" and the other
computer as the "Auxiliary rack". Scada have to initiate the protocol communication in order
to choose the Main C264.
For more explanations, please refer to the section §1.2.9 SCADA – TBUS - Two C264
Standalone computers, redundant (C264/EN FN) and Slave Profile Protocol for T101.
CAUTION: THE PROTOCOL REDUNDANCY IS NOT APPLICABLE FOR MICOM

C264 BCU CONFIGURATION.
CAUTION: THE PROTOCOL REDUNDANCY IS NOT APPLICABLE FOR TBUS
PROTOCOLS : T104 , DNP3 (SERIAL OR OVER IP), MODBUS AND HNZ.
3.6.4 TBUS Redundancy T101 example
This example includes TBUS T101 Redundancy (both link and protocol) on MiCOM C264
RTU standalone configuration.
Serial Serial Serial Serial

Port 1 Port 2 Port 3 Port 4
TBUS
TBUS
Serial Serial Serial Serial
Port 1 Port 2 Port 1 Port 2
Main 1 Main 2
Rack Rack
Event files
synchronisation
LBUS
Extension
Rack
IED
IED
Inter-rack Ethernet
communication IED
(NOTE1)
Extension
Rack
IED
IED
IED
FIGURE 11: TBUS REDUNDANCY PROTOCOL T101

NOTE: The Ethernet inter-rack uses swich(es). For more explanations, please
refer to the section § 3.4 Inter-rack Ethernet communication (C264/EN
FN).
Each C264 connects through the Serial Port 1 and Serial Port 2 through the TBUS to the
SCADA.
Each C264 connects through Ethernet Port to two extension racks. Each extension rack
connects through the LBUS to the IEDs.
3.6.5 Event file synchronization

With Redundancy protocol and MiCOM C264 RTU standalone configuration, buffer of events
and SOE file of Main 1 Rack and Main 2 Rack are synchronized via the Ethernet link 2
(InterRack).
The event file synchronization mechanism permits to avoid incoherent events when the
SCADA drives the C264 switching after communication failure.
When the "Auxiliary Main Rack" becomes the "Main Rack", events that are already
transmitted to the SCADA (by the previous Main) are not resent.
CAUTION: THE EVENT FILE SYNCHRONIZATION BETWEEN MAIN 1 RACK AND
MAIN 2 RACK IS SUPPORTED IN CASE OF DATAPOINT AQCUISITION
ARE MADE FROM C264 EXTENSION RACK ONLY.
3.6.5.1 Details about event file synchronization management:
The event file synchronization mechanism consists of delete the event (previously
transmitted to SCADA) from the event file on Auxiliary Main Rack through the InterRack
link.The Auxiliary Main Rack looks for this event in its event files and suppresses it.
CAUTION: THE DATAPOINT COMPUTED (TIME STAMPED) BY MAIN RACKS CAN
NOT BE SYNCHRONIZED. TYPICALLY THESE DATAPOINT ARE ALL
SYSTEM INFORMATION (RACK STATUS, COMMUNICATION STATUS,
SYNCHRONIZATION STATUS, COUNTERS, BUFFER OVERFLOW).
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 12: 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
C0127ENb
FIGURE 13: 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 14: 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 15: 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 16: 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
FIGURE 17: 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 18: 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 19: 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
C264 treatment entries can be Binary Inputs or Analogue Inputs. They are issued from
• IO boards
• C264 internal data: System Input, automation
• Communication acquisition: IED or another computer from LBUS or SBUS
5.1 Binary Input Processing

5.1.1 Binary Input Definition
The five types of Binary Inputs (BI) include:
• 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 with digital input boards or with IEDs connected with a serial
link.
After the acquisition on the digital input boards, the computer performs toggle filtering. When
an input has an hazardous behaviour, such as more than N state changes during a given
duration, toggle filtering prevents the input to load into the computer or into other devices.
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: for example, display, alarm,
transmission. The BI takes the “SUPPRESSED” state. When the operator un-suppresses 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 un-substitutes it. When a BI is
substituted, no changes of state are transmitted, and computations, for instance groupings,
are made with the substituted state. When the BI is un-substituted, the actual state is
transmitted to higher control levels and subsequent changes of state are transmitted again.
5.1.1.4 Forcing
When data is invalid: that is, 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 data is automatically updated when valid data is available
again. A SUPPRESSED or SUBSTITUTED datapoint cannot be forced. The forcing could
also be automatic: in this event, the invalid data is automatically replaced by the state
defined in configuration.
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 20: 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 C264 configuration. If the
opposite transition occurs before this delay, both transitions are discarded.
This treatment is called persistent filtering.
The status is stamped with the time of the transition.
The SP resulting states include:
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 21: 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 22: 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 treatments (filtering) for some DPs is applied to filter the MOTION state on a
certain period of time. This avoids the transmission of this (normally) transient state.
This treatment is called 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 event of confirmed
MOTION00 state) or UNDEFINED (in event of confirmed MOTION11 state). In this event,
the following valid state (OPEN or CLOSE) is always time-stamped with the time of this valid
transition (depending on the persistence filtering feature).
5.1.3.1 Motion filtering

For some DP, the MOTION state must be filtered during 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 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 event of confirmed
MOTION00 state) or UNDEFINED (in event of confirmed MOTION11 state). In this event,
the following valid state (OPEN or CLOSE) is always time-stamped with the time of this valid
transition (depending on 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 23: 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: that is,
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 24: DP PERSISTENCE FILTERING

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.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 or the closure of the output.
The relation between the state and the order is defined during the configuration phase.
5.1.3.4 MOTION states management

MOTION states are the valid intermediate states of the Double Point Status (DPS), when the
DPS state changes from OPEN to CLOSE or from CLOSE to OPEN. MOTION states are not
managed in event of REPORT data transmission.
In event of GOOSE data transmission, a new MOTION states management exists:
• MOTION states are transmitted only in GOOSE transmission mode.
• The quality value for MOTION states: q = 0x0000
• The quality value for JAMMED states: q = 0x0000
• The quality value for UNDEFINED states: q = 0x0000
• stVal values are the same as the previous values.

The codes for the DPS data on the C264 server, on IEC61850, and on IEC61850 clients
show in the table that follows:
Server Data on IEC61850 Server Client
Acquired state stVal Quality Resulting state Resulting state

C264 C264 OI/GTW PC
MOTION00 0x00 All bits = 0 MOTION00 N/A
(GOOSE only) q= 0x0000 (GOOSE only)
JAMMED 0x00 B1=1, other bits = 0 JAMMED JAMMED
q= 0x4000
OPEN 0x40 All bits = 0 OPEN OPEN
q= 0x0000
CLOSED 0x80 All bits = 0 CLOSED CLOSED
q= 0x0000
MOTION11 0xC0 All bits = 0 MOTION11 N/A
(GOOSE only) q= 0x0000 (GOOSE only)
UNDEFINED 0xC0 B1=1, other bits = 0 UNDEFINED UNDEFINED
q= 0x4000
NA: Not Applicable
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 events where no Digital Inputs is
SET or more than one Digital Inputs are SET. After this delay, the MP becomes
UNDEFINED.
N is fixed by C264 configuration from 2 to 32. There is no GOOSE transmission mechanism.
You can use an MP in two ways:
• As a status (MPS): in this event, N is as many as 16
• As a value, only for TPI: in this event, N is as many as 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 25: 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
C0313ENa
FIGURE 26: MULTIPLE POINT FILTERING

The MP is time-tagged with the date of the last BI change.
5.1.5 System Inputs (SI)
System inputs (SI) 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 data that have no acquisition possibilities: no acquisition through DI

or through serial communication. However, they must be managed by the C264
computer. The status of this data are saved in non-volatile memory.
An SI is of SP, DP or MP type and can belong to any type of group.
The processing of a 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
that 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 that has modified the group
status.
5.1.8 SBMC Mode Processing
When a Bay is in Site Based Maintenance Control (SBMC) mode, the status of the Binary
Inputs (related to this Bay and defined as “SBMC dependant”), takes the forced state defined
in the configuration.
This forced information is delivered to the Remote Control Point (RCP) as long as the SBMC
mode is active on the Bay.
For a group a special feature is implemented: a BI belonging to a group, that is dependent of
SBMC bay state, is not taken into account in group computation if the bay is set in SBMC
mode. If all the BI of a group belong to one or more bays, that are all in SBMC mode, the
group is then in the suppressed state. At the end of a bay SBMC mode, all groups owning BI
of this bay are re-computed.
5.1.9 BI sent to automatism features
In event that an automatism operates on a client computer, with BI information coming from
a server computer, BI are generally transmitted in the GOOSE based mode. In some events
where the GOOSE based mode is not used, BI information received by IEC61850 reports
must be used in automatism features.
In any events 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:
• For DC: AIU201 or AIU211
• For AC: TMU2xx.

Digital Measurement comes from Digital input boards.
5.2.1 Measurement Input Processing - Focus
We examine four areas of focus, as follows:
FIGURE 27: PROCESS OF A MEASUREMENT VALUE

Focus 1: Analogue measurement processing as far as threshold detection
Focus 1: Digital measurement processing as far as threshold detection
Focus 1: CT / VT measurement processing as far as threshold detection
Focus 4: All Measurement Values: Threshold Detection thru Transmission
5.2.2 Focus 1: Analogue Measurement Processing as far as Threshold Detection

The process of a measurement value shows as follows:

Focus 1: Analogue processing as far as threshold detection
5.2.3 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.4 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 .

As many as 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.5 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
C0359ENa
FIGURE 29: ZERO VALUE SUPPRESSION
5.2.6 Focus 2: Digital Measurement Processing as far as Threshold Detection

A Digital Measurement is derived from a Digital input. Digital Measurements are used for
process measures or Tap indications.

Focus 2: Digital Measurement processing as far as threshold detection
For the conditions that follow, the DM is UNDEFINED:

• The value is not stable.
• BCD: a quartet is more than 9
• Decimal: no bit is set or more than one for tens or unit.
Two others bits can be used:
• For read inhibit: in this event, the DM is acquired when the Read Inhibit bit is set.
• For the sign.
5.2.7 Focus 3: TMU2XX: CT/VT measurement processing as far as Threshold Detection

Focus 3: CT / VT Measurement processing as far as threshold detection
It is impossible to plug the computers directly into the high voltage electric network. The
computers receive the data from the Current Transformers (CT) and from Voltage
Transformers (VT) installed on the TMU2XX boards.
The purposes of the CT and VT include:
• To deliver current and voltage data that gives a reliable picture of what happens in the
high voltage part of an electrical substation
• To make the galvanic insulation between the high voltage part and the measurement
and protection circuits,
• To protect the measurement circuits against damage when a fault comes onto the
high voltage network.
A given electrical network sends voltage (V) and current (I) data to a CT / VT inputs
acquisition function installed on a TMU2XX board.
From the output of the CT / VT inputs acquisitions function, these samples become inputs of
the CT / VT calculation function
The CT / VT calculation function performs basic mathematical processing on the memorised
samples and gives this set of computed measurements, such as power, frequency, and so
on, to the C264 main CPU, the Power PC (PPC).
These measurements are used for the protection function and for the Internal Synchrocheck,
Type 1 and 2
Please refer to: Figure 27: Overview: TMU220 Board – CT / VT Calculations
Figure 28: Overview: TMU210 Board – CT / VT Calculations
FIGURE 32: OVERVIEW: TMU220 BOARD – CT / VT CALCULATIONS
FIGURE 33: OVERVIEW: TMU210 BOARD – CT / VT CALCULATIONS
5.2.8 TMU2XX: CT / VT Calculations - General

The voltage measurements come from the VT installed on the TMU2XX boards. There are 2
possibilities for the number of busbar voltages and protection attributes of the computer.
CTVT Board Wired Busbar Protection Busbar Synchrocheck

voltage nb Attributes selection (SC)
TMU210 1 Yes External Type 2
TMU220 2 No Internal Type 1
CT / VT measurements are provided by 3 couples, or combinations, of boards:
• DSPIO + TMU210 ( 4 CT and 4 VT ), referred to as the DSP210 board installed on

TMU210
• DSP + TMU220 ( 4 CT and 5 VT ), referred to as the DSP200 board installed on

TMU220
For the TMU220:
The TMU220 boards have the same hardware attributes, except that TMU220 has one more
VT.
The DSP board computes the samples from the TMU220 and sends the set of computed
measurements to the PPC.
Please refer to Figure 29: Detail: TMU220 Boards – CT / VT Calculations
FIGURE 34: DETAIL: TMU 220 BOARDS - CT / VT CALCULATIONS
TMU220 BOARDS – Signals, Ratings, and Range:
TMU 220 BOARDS

Signals Rating Range
Va, Vb, Vc, Vbusbar1, Vbusbar2 57V thru 480V
Ia, Ib, Ic, Ir 1A or 5A
For the TMU210:

The hardware attributes of the TMU210 are different and oriented towards protection.
The DSPIO board computes the samples from the TMU210 analogue inputs, and from the
digital inputs and digital outputs located on the DSPIO board. The DSPIO Board sends the
set of computed measurements to the C264-PowerPC (PPC) – CPU3.
Please refer to: Figure 30: Detail: TMU210 Board – CT / VT Calculations
FIGURE 35: DETAIL: TMU210 BOARD - CT / VT CALCULATIONS
TMU 210 BOARDS

Signals Rating Range
Va, Vb, Vc, Vo, Vbusbar NA 57V to 130V
Ia, Ib, Ic, 1A or 5A 0.1 to 40 In
Io normal: 1A or 5A
Io normal: Normal 0.1 to 40 Ion
Io normal: Sensitive 0.01 to 8 Ion
Io normal: Very sensitive 0.002 to 1 Ion
CT / VT Functions
These functions use the measurements from the TMU2XX boards:
• Internal synchrocheck: Type 1 and Type 2
• Protection
• Waveform
The CTVT measurements can be included in the waveform function.
2 types of waveform are defined: Fast waveform and Slow waveform.
Board Internal Internal Protection Fast Slow

synchrocheck synchrocheck waveform waveform
Type 1 Type 2 (Disturbance)
DSP200 X X X
DSPIO+TMU210 X X X X
or DSP210
DSP+TMU220 X X X
or DSP220
5.2.9 TMU220: CT / VT Calculations – Inputs: Configuration

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

5.2.10 TMU220: CT / VT Calculations - Inputs: Samples
The inputs of the CT / VT Calculation function (issued from the Conventional CT/VT inputs)
include:
In event of star coupling:
• Samples of Ia
• Samples of Va
• Samples of Ib
• Samples of Vb
• Samples of Ic
• Samples of Vc
• Samples of Io or Ibb1
• Samples of Vbb1 (Vr) or VBUSBAR in event of the presence of the synchrocheck

function
• Samples of Vbb2 or VBUSBAR2 in event of presence of the synchrocheck function
• Validity of each sample.

In event of delta coupling:
• Samples of Ia
• Samples of Ib
• Samples of Ic
• Samples of Io or Ibb1
• Samples of Vab
• Samples of Vbc
• Samples of Vca
• Samples of VBUSBAR1 or Vbb1
• Samples of VBUSBAR2 or Vbb2

64 samples per period are available.
5.2.11 TMU220: CT / VT Calculations – Outputs: Set of measurements
The CT / VT calculation function places at the disposal:
• RMS currents and voltages
• Frequency
• Active power P (Watts – total and on a per phase basis )
• Reactive power Q (Vars – total and on a per phase basis)
• Apparent power S (VA – total and on a per phase basis)
• Power factor pf (total and on a per phase basis) – pf = P / S
• Sequence components: Id, Ii, Io, Vd, Vi
• Phase angles
• Total Harmonic Distortion (THD) & Total Demand Distortion (TDD) – Harmonics are
evaluated through to the 15th order.
• Fundamental (H1 harmonic) of phase A current
• Fundamental (H1 harmonic) of phase B current
• Fundamental (H1 harmonic) of phase C current
• Fundamental (H1 harmonic) of phase A voltage
• Fundamental (H1 harmonic) of phase B voltage
• Fundamental (H1 harmonic) of phase C voltage
• Fundamental measurements
• Synchrocheck data: ΔF ΔV ΔΦ
• With the synchrocheck option, the values that follow are computed:
− Slip frequency
− Amplitude
− Phase difference
− Synchrocheck voltage
These measurements are put at the disposal of the PPC at every measurement reading
cycle defined by the configuration.
A configuration option [ meas quality when missing ] allows you to choose 2 different
behaviours when all the Input signals disappear: all below the minimum thresholds, 10V for
voltage and 100mA for current:
• Behaviour 1: the measures associated to the acquired signals are set to value 0 and
state VALID
• Behaviour 2: the measures associated to the acquired signals are set to value 0 and
state FAULTY
5.2.12 TMU220: Measurements - General
Whatever the signal frequency, 64 samples are available for all the input signals.
All these samples are gathered in a revolving list stored in active memory.
A timer is adapted permanently to the frequency of the signal and provides the frequency
measurement
The primary measurements that follow are derived from sample values:
• RMS Current and Voltage
• P: Active Power (Watts)
• Q: Vars (Using Active Power calculation method with the voltage samples retarded by
90°)
The measurements that follow are obtained from the Fourier of sample values or the Fourier
values of the above-derived measurements (DFT ).
• Sequence Components (Id, Ii, Io, Vd, Vi, Vo)
• Fundamental and harmonics
• Phase angles
• Power Factor
• SVA
• THD and TDD
• Specials (for products with check-sync.).

5.2.13 TMU220: List of Measurements
Measurements Star delta Accuracy ( TMU220) Unit id

RMS current phase samples samples F < 70hz: Ampere
Ia I< In: 0.2% of In 7
Ib I>In: 0.2% of I 8
Ic F>70Hz: 9
Ir I< In: 4% of In 10
Ibusbar1 I>In: 4% of I 184
RMS Volt phase Not F<70Hz Volts
available
Va samples U<45V: 0.3% of 45 0
Vb samples 45v<U<200v: 0.2% of U 1
Vc samples U>200V: 0.3%of U 2
Vr computed F>70Hz 3
Vbusbar1 samples U<45V: 4% of 45 3
Vbusbar2 samples U>45V: 4% of U 185
RMS volt phase F<70Hz Volts
Vab Computed samples U<45V: 0.3% of 45 4
Vbc Computed samples 45v<U<200v: 0.2% of U 5
Vca Computed samples U>200V: 0.3%of U 6
Vr Computed computed F>70Hz 3
Vbusbar1 samples U<45V: 4% of 45 3
Vbusbar2 samples U>45V: 4%of U 185
Frequency computed computed Hertz 36

Power Phase A Not
available
Active power ( P ) Samples Watts 11
Reactive power (Q) Samples Vars 12
Apparent power (S) Computed VA 13
Cos phi Computed 14
angle computed Degree 15
Power Phase B Not
available
Cos phi Computed 19

Power Phase C Not
available
Cos phi Computed 24
Power r Not
available
Cos phi Computed 34
Power total computed computed
Active power ( P ) Watts 26
Reactive power (Q) Vars 27
Apparent power (S) VA 28
Cos phi 29
angle Degree 30
V Sequence components DFT Not volts
computed available
Direct 175
Inverse 176
Homopolar 177
ratio 178
I Sequence components DFT DFT Ampere
computed computed
Direct 179
Inverse 180
Homopolar 181
ratio 182
Harmonics for Va DFT DFT Volts
Fundamental 186
15 Harmonic 40->53
distortion ration 54
Harmonics for Vb DFT DFT Volts
Fundamental 187
15 Harmonic 55->68
distortion ratio 69
Harmonics for Vc DFT DFT Volts
Fundamental 188
15 Harmonic 70->83
distortion ratio 84

Harmonics for Vab DFT DFT Volts
Fundamental
15 Harmonic 85->98
distortion ration 99
Harmonics for Vbc DFT DFT Volts
Fundamental
15 Harmonic 100->113
distortion ratio 114
Harmonics for Vca DFT DFT Volts
Fundamental
Harmonics for Ia DFT DFT Ampere
Fundamental 189
Harmonics for Ib DFT DFT Ampere
Fundamental 190
Harmonics for Ic DFT DFT Ampere
Fundamental 191
Delta F computed computed Hertz 37
Delta phi computed computed Degree 38
Delta V computed computed Volts 39
5.2.14 TMU220: Algorithms

Frequency
The frequency is directly computed through the timer frequency.
The reference phase used to set the timer frequency is chosen in the configuration
(“reference phase”).
Frequency tracking is performed according to the following order:
1. on reference voltage defined in configuration ( higher priority )
2. Vbusbar
3. Vbusbar_bis (if TMU220 is used)
4. VB and then VC if the reference voltage if VA
VC and then VA if the reference voltage if VB
VA and then VB if the reference voltage if VC
5. I1
6. I2
7. I3
8. I4 ( lower priority )
A configuration option (“voltage ref change mode”) allows choosing 2 different behaviours of
the frequency tracking:
• Behaviour 1 – Default Voltage Reference:
− When the signal with the highest priority disappears, the frequency tracking is
performed on the signal with next priority.
− When a signal with a higher priority appears, the frequency tracking is performed
on this signal, even if the current reference signal is still present.
• Behaviour 2 – Current Voltage Reference:
− When the signal with the highest priority disappears, the frequency tracking is
performed on the signal with next priority.
− Even when a signal with a higher priority appears, the frequency tracking remains
on the current reference signal.
In all events, the reference change computation (about 2 seconds), all the measurements
are considered as INVALID (SELFCHECK FAULT).
Fourier Transform
At each period, the DFT (Discrete Fourier Transform) is performed. This gives (among other
things) the value of the phase angle and the magnitude of the fundamental.
RMS values
1 63
Vrms = ∑ Vi ²
64 i =0
Powers phase in star coupling
Active power: Pa, Pb, Pc
1 63
P= ∑ Vi I i
64 i =0
Reactive power: Qa, Qb, Qc
1 63
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) ]
5.2.14.1 Total power
Star Coupling: Total Power
P = Pa+Pb + Pc
Q = Qa + Qb + Qc
Delta Coupling: Total Active Power
1 63
P= ∑U BC (i ).I B (i ) − U CA (i ).I A (i )
64 i =0
Delta Coupling: Total Reactive Power
1 63
P= ∑U BC (i).I B (i − π / 2) − U CA (i).I A (i − π / 2)
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 DFT.
Sequence components
The sequence component computation is based on the fundamental values of phase and
magnitude (from the DFT): that is its imaginary part and real part.
• 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
Synchrocheck measurements:
ΔF = | Fline – Fbusbar |
ΔV = | Vline – Vbusbar |
Δϕ= | ϕline – ϕ Vbusbar
5.2.15 TMU210: CT / VT Calculations - Inputs: Configuration

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

With the TMU210 board with respect to the type of connection, some restrictions exist
because of the fourth VT.
At this time, please refer to the topic Phase-to-Phase Synchrocheck with the TMU210 –
General and to the Table: TMU210 Type of Connection: Direct or Indirect .
The inputs of the CT / VT Calculation function (issued from the Conventional CT/VT inputs)
include:
In event of star coupling:
• I1: samples of IA
• I2: samples of IB
• I3: samples of IC
• I4: samples of Io
• V1: samples of UA
• V2: samples of UB
• V3: samples of UC
• V4: samples of U0 or UBUSBAR

In event of delta coupling:
• I1: samples of IA
• I2: samples of IB
• I3: samples of IC
• I4: samples of Io
• V1: samples of UA
• V2: samples of UB
• V3: samples of UC
• V4: samples of U0 or UBUSBAR
32 samples per period are available.
5.2.17 TMU210: CT / VT Calculations – Outputs: Set of measurements

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

Whatever the signal frequency, 32 samples are available for all the input signals.
All these samples are gathered in a revolving list stored in active memory.
A timer is adapted permanently to the frequency of the signal and provides the frequency
measurement.
The primary measurements that follow are derived directly from sample values:
• RMS: Current and Voltage
• It and I2t measurements
• Thermal status
The following measurements are obtained from the Fourier of sample values or from the
Fourier values of the derived measurements (DFT ):
• DFT: Current and Voltage
• DFT Sequence Components: Current and Voltage (positive and negative)
• Current voltage angle
• Active phase Power
• Active earth Power
• Reactive phase power
• Power Factor
• Synchrocheck measurements.
5.2.19 TMU210: List of Measurements
Measurements Accuracy Unit id

RMS current phase 2% In
Rms_Ia 7
Rms_Ib 8
Rms_Ic 9
Rms_Io 10
RMS Voltage phase 2% Volts

Rms_Va_Vab 0
Rms_Vb_Vbc 1
Rms_Vc_Vca 2
Rms_Vo 3
Rms_Vbusbar
Frequency 0.01Hz
F: frequency tracking Hertz 36
F81: frequency used by 81 Hertz
Index of F 323
Index of F81 324
Rate of frequency_81 0.03Hz/sec Hertz/sec
DFT current phase 2%

Ia In 300
Ib In 301
Ic In 302
Io Ion 303
Io_computed Ion 313
EPATR Io ampere
DFT Voltage phase 2% Volts

UA
UB
UC
UAB 304
UBC 305
UCA 306
Uo 307
Ubusbar 183
DFT Sequence voltage volts

U_positive
U_negative
DFT Sequence current In

I_positive
I_negative
Total power
Active phase power ( P ) <3% Watts 26
Active earth power(Po) <3% watts
Reactive power (Q) Vars 28
Cos phi 29
Measurements Accuracy Unit id

Thermal status % 312
IT measurement Ampere / second

IT phase A 340
IT phase B 341
IT phase C 342
IT total 343
2
I t measurement Ampere²/second
I2T phase A 344
I2T phase B 345
I2T phase C 346
I2T total 347
Synchrocheck
Delta F Hertz 37
Delta V Volts 38
Delta phi Degree 39
Freq line Hertz 330
Freq bar Hertz 331
Phase Angle Degree 332
Anticipation angle Degree 333
Shift freq % 334
Acceleration shift freq % 335
5.2.20 TMU210: Algorithms

Calibration
3 calibration parameters are stored in EEPROM for each input:
• Amplitude
• Phase
• offset
The offset correction has to be re-evaluate in real time and not in static way.
So the offset correction is made by a low pass filter (0.5Hz ). So the offset parameter stored
in EEPROM is not used.
The amplitude offset is used at each acquisition cycle.
Frequencies:
Frequency tracking
The frequency tracking is made by calculating the frequency of a voltage or current channel.
For each channel a minimum threshold is used to validate the signal (1 volt for VT, 0.1A pour
CT).
If a tracking is done on a channel, there is no change until the value of this channel becomes
lower than the threshold. There is no hysteresis on them. The channel changing respects the
following list:
• V1 (first)
• V2
• V3
• I1
• I2
• I3 (last)
Frequency computation
The first phase voltage channel over minimum threshold (Umin_F_enable) is selected, then
a filter FIR is applied to reject harmonic. On result, we calculate period by cross zero
method, on leading edge and on trailing edge, average result of this both measurement
generated frequency used.
Between 2 computations of the frequency, if the frequency change is more than 20Hz/s
(equals to a brutal step 400mHz at 50Hz), then the frequency calculation will be frozen and
INVALID during 7 cycles (for example, at 50Hz the frequency will be frozen during 120ms)
Frequency81 and frequency rating computation

According to the configuration parameter “VT_connection”, there are 2 events:
• VT_connection = 3Vpn or 3Vpn+Vo or 2 Vpn+Vo or 2Vpp+Vo or 3Vpp+Ve

Frequency81 computation without priority
• VT_connection = 3Vpn +Vb or 3Vpp+Vb

Frequency81 computation with priority
Frequency81 computation without priority

The first voltage upper than the threshold (Umin_F_enable, SEE GPS 8) is given as
reference. When this voltage goes down the threshold, the next voltage is tested as
reference.
The cycle of reference test is V1, V2, V3, V1, V2 …etc
Frequency81 computation with priority
In priority, V4 (bus bar voltage) is used for reference comparing to the threshold. If this
voltage goes down the threshold, a valid line voltage is searched. When the bus bar voltage
is detected back over the threshold, the bus bar VT is reassigning to be the frequency
tracking reference.
RMS measurements
The RMS measurement of the last period recorded is calculated as the square root of the
square sum of the samples in the period divided by the number of samples examined.
The square sum is calculated every period (32 samples recordings).
1 31
Vrms = ∑ Vi ²
32 i =0
3Vpn 3Vpn+Vo 2Vpn+Vo 2Vpp+Vo 3Vpp+Vo 3Vpn+Vb 3Vpp+Vb

Rms_IA Rms_IA
Rms_IA Rms_IB
Rms_IC Rms_IC
Rms_Io Rms_Io
Rms_UA_UAB Rms_UA Rms_UA Rms_UA Rms_UAB Rms_UAB Rms_UA Rms_UAB
Rms_UB_UBC Rms_UB Rms_UB Rms_UB Rms_UBC Rms_UBC Rms_UB Rms_UBC
Rms_UC_UCA Rms_UC Rms_UC NOT VALID NOT VALID Rms_UCA Rms_UC Rms_UCA
Rms_Uo NOT VALID Rms_Uo Rms_Uo Rms_Uo Rms_Uo NOT VALID NOT VALID
Rms_U_busbar NOT VALID NOT VALID NOT VALID NOT VALID NOT VALID Rms_u_busbar Rms_u_busbar
Fundamental measurements:
General
The instantaneous direct effective fundamental measurement, to be utilised by the
protections, is supplied every samples reception frame, in terms of both module and phase
as well as that for the real part and the imaginary part of the current vector. This is calculated
using the Fourier transform (DFT), applied to the samples of the last period recorded (32
samples) and expressed in ADC points.
So a multiplier coefficient is necessary to scale them in the appropriated unit.
3Vpn 3Vpn+Vo 2Vpn+Vo 2Vpp+Vo 3Vpp+Vo 3Vpn+Vb 3Vpp+Vb
Mod_IA Direct
Mod IB Direct
Mod IC Direct
Mod Io Direct
Mod_UA Direct Direct Direct Derived Derived Direct Not valid
Mod _UB Direct Direct Direct Derived Derived Direct Not valid
Mod _UC Direct Direct Derived Derived Derived Direct Not valid
Mod _UAB Derived Derived Derived Direct Direct Derived Direct
Mod _UBC Derived Derived Derived Direct Direct Derived Direct
Mod _UCA Derived Derived Derived Derived Direct Derived Direct
Mod _Uo Derived Direct Direct Direct Direct Derived Not valid
Mod _U_busbar Not valid Not valid Not valid Not valid Not valid Direct Direct
Mod_I1 Derived
Mod_I2 Derived
Mod_V1 Derived
Mod_V2 Derived
Ioc Derived
Conversion
• KUADC is the number of ADC points corresponding to a phase voltage of 1V to the

secondary side.
• KUoADC is the number of ADC points corresponding to an earth voltage of 1V to the
secondary side.
• KIADC is the number of ADC points corresponding to the nominal phase current to the
secondary side.
• KIoADC is the number of ADC points corresponding to the nominal earth current to the
secondary side.
• X is the value of the module expressed in ADC points (X = I, Io, Uxy, Uo)
• X” is the effective value of the module expressed in voltage or ampere to the primary
side (X = I, Io, Uxy, Uo).
I
I "= * CT _ In
KI ADC
Io
Io"= * CT _ Ion
KIo ADC
U xy
U xy " = *VT _ Un
KU ADC ⋅ Un
Uo
Uo" = *VT _ Uon
KUo ADC ⋅ Uon
Direct measurements
The real and the imaginary part are determined using the DFT method.
N
⎛ 2π * i ⎞
Re(G ) = ∑ sample * cos⎜ ⎟
i =1
i
⎝ N ⎠
N
⎛ 2π * i ⎞
Im(G ) = ∑ sample * sin⎜ ⎟
i =1
i
⎝ N ⎠
The real part and the imaginary part of every received valid sample are calculated.
Derived measurements
Voltages
3Vpn 3Vpn+Vo 2Vpn+Vo 2Vpp+Vo 3Vpp+Vo 3Vpp+Vb 3Vpn+Vb
UA V1 V1 V1 (kVo +2V1 –V2)/3 (kVo +V1 – V3)/3 Not valid V1
UB V2 V2 V2 (kVo +V2 –V1)/3 (kVo +V2 – V1)/3 Not valid V2
UC V3 V3 kVo – V1-V2 (kVo-V1 + 2V2)/3 (kVo-V3 + V2) Not valid V3
UAB V1-V2 V1-V2 V1-V2 V1 V1 V1 V1-V2
UBC V2-V3 V2-V3 2V2+V1-kVO V2 V2 V2 V2-V3
UCA V3-V1 V3-V1 kVO-2V1-V2 V1-V2 V3 V3 V3-V1

-1 -1
UO k (V1+V2+V3) k (V1+V2+V3) Not valid k-1 (V1+V2+V3)
-1
Ubusbar k (V1+V2+V3) Not valid Not valid Not valid Not valid
k The earth to phase adaptation coefficient - (necessary for expressing the earth ADC
points in phase ADC points) amounting to:
Un ⋅ KU ADC VT _ Uon
k= ⋅
Uon ⋅ KUo ADC VT _ Un
Positive and negative sequence current
The definition of positive sequence current, I1, indicates the current vector obtained by the
sum of the phase A vector, plus the phase B vector rotated by 120° in advance plus the
phase C vector rotated by a lag of 120°.
The definition of the negative sequence current, I2, indicates the current vector obtained by
the sum of the phase A vector, plus the phase B vector rotated by a lag of 120° plus the
phase C vector rotated by 120° in advance.
Derived vectors:
Positive sequence current I1 IA+(IB-120°)+(IC+120°)

Negative sequence current I2 IA+(IB+120°)+(IC-120°)
Where the writing <IB/C+/-120°> points out that the vector is considered rotated of +/- 120°
Positive and negative sequence voltage

Derived vectors:
3Vpn, 3Vpn+Vo, 2Vpn+Vo 3Vpp+Vo, 2Vpp+Vo,

3Vpn+Vb 3Vpp+Vb
Positive sequence voltage U1 (UA+(UB+120°)+(IC+240°))/ (UA+(UB+240°)+(IC+120°))/3
3
Negative sequence voltage U2 (UA-(UB-120°))/3 (UA-(UB+120°))/3
Where the writing <UB/C+/-alfa> points out that the vector is considered rotated of +/- alfa
Computed Homopolar current
In order to use the protective function 67N in several specific conditions, the Homopolar
current must be computed from the values of the 3 phase currents:
→
I The generic current vector
Re(…) The operator that returns the real part of a generic vector;
Im(…) The operator that returns the imaginary part of a generic vector;
k The earth to phase adaptation coefficient - (necessary for expressing the earth
ADC points in phase ADC points) amounting to:
In ⋅ KI ADC CT _ Ion
k= ⋅
Ion ⋅ KIo ADC CT _ In
The real and imaginary part of the derived current vectors, expressed in ADC points, will be
given by:
r 1
( r r r
Re( I OC ) = Re( I A ) + Re( I B ) + Re( I C )
k
)
Ioc
( )
r 1 r r r
Im( I OC ) = Im( I A ) + Im( I B ) + Im( I C )
k
Phase and earth current - voltage angle measurement

The instantaneous angle between the generic phase current and the phase-phase
quadrature voltage, to be used for protection purposes is obtained as the relative angle
between the involved vectors.
The formulas are:
r r
⎛ Re( I A ) ⎞ ⎛ Re(U BC ) ⎞
I A ^ U BC = arctg⎜⎜ r ⎟⎟ − arctg⎜⎜ r ⎟
⎟
⎝ Im( I A ) ⎠ ⎝ Im(U BC ) ⎠
r r
⎛ Re( I B ) ⎞ ⎛ Re(U CA ) ⎞
I B ^ U CA = arctg⎜⎜ r ⎟⎟ − arctg⎜⎜ r ⎟⎟
⎝ Im( I B ) ⎠ ⎝ Im(U CA ) ⎠
r r
⎛ Re( I C ) ⎞ ⎛ Re(U AB ) ⎞
I C ^ U AB = arctg⎜⎜ r ⎟⎟ − arctg⎜⎜ r ⎟
⎟
⎝ Im( I C ) ⎠ ⎝ Im(U AB ) ⎠
Where:
I^U is the angle between the generic phase current and the phase-phase quadrature
voltage.
r
I is the generic current vector.
r
U is the generic voltage vector (phase-phase).
Re(…) is the operator that returns the real part of a generic vector.
Im(…) is the operator that returns the imaginary part of a generic vector;
Active earth power

With any type of phase voltage insertion it is always possible to derive the vectors of the
earth voltage’s fundamentals that, together with the earth current, allow the active earth
power calculation. The formula is:
r r r r
Po = Re ( I o ) ⋅ Re (U o ) + Im( I o ) ⋅ Im( U o )
Where:
Po The active earth power expressed in ADC points.
Active three-phase power
With any type of phase voltage insertion it is always possible to derive the vectors of the
phase-phase voltage’s fundamental.
Therefore, it is quite easy to calculate the three phase active power by using the Aaron
method; the formulas are:
r r r r r r r r
P = Re ( I A ) ⋅ Re (U AB ) + Im( I A ) ⋅ Im( U AB ) − Re ( I C ) ⋅ Re (U BC ) − Im( I C ) ⋅ Im( U BC )
P
P" =
3 ⋅ KI ADC ⋅ KU ADC ⋅ Un
CT _ In ⋅ VT _ Un
P ' = InTA ⋅ UnTV ⋅ P" = P
Where:
P is the active three phase power expressed in ADC points;
Pn is the nominal three phase power to the secondary side, amounting to: Pn = 3 ⋅ In ⋅ Un
Since In and Un are respectively the nominal current and the voltage to the secondary side;
P” is the active three phase power to the secondary side, expressed in Watt;
P’ is the active three phase power to the primary side expressed in Watt;
Reactive three-phase power
With whatever type of phase voltage insertion, it is always possible to draw the vectors of the
phase-phase voltage’s fundamental.
Therefore, it is easy to calculate the reactive three-phase power by using the Aaron method;
the formulas are:
r r r r r r r r
Q = Im( I A ) ⋅ Re(U AB ) − Re( I A ) ⋅ Im(U AB ) − Im( I C ) ⋅ Re(U BC ) + Re( I C ) ⋅ Im(U BC )
Q
Q" =
InTA ⋅ UnTV
Q ' = InTA ⋅ UnTV ⋅ Q" = Q
Where:
Q is the three phase reactive power expressed in ADC points;
Qn is the nominal three phase active power to the secondary side, amounting
to: Qn = 3 ⋅ In ⋅ Un
Since In and Un are respectively the nominal current and the voltage to the secondary side;
Q” is the active three phase power to the secondary side, expressed in Qn;
Q’ is the active three phase power to the primary side expressed in VAR;
Power factor
The power factor is an instantaneous value, used only for visualising purposes. Indicated by:
P the three phase active power expressed in ADC points;
Q the three phase reactive power expressed in ADC points;
The power factor, or three phase cosφ, is calculated according to the following algebraic
function:
P
cos φ =
P2 + Q2
The sign of three phases cosφ is determined according to the following conventions:
P positive P negative
Q positive +L -C
Q negative +C -L
Thermal status
It can be demonstrated that, for dt=0.02s, the thermal status can be estimated according to
the following equation:
2
⎛ IMAX ⎞ dt dt
θ (t + dt ) = θ (t ) + ⎜⎜ ⎟⎟ − θ (t )
⎝ θ ⎠
I τ τ
Where:
IMAX is the maximum of the three instantaneous values of the three phase RMS
currents.
τ is the thermal constant of the device to be protected.
Iθ is the base current of the device to be protected (ratio between the device’s
nominal current – in other words the current that, at full operation, implies over-
temperature by 100% - and the nominal current of the TA).
Iθ = K * Ith
θ is the thermal status or over-temperature of the device (over-temperature in p.u. in

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

I2T Measurements
There are 8 measurements dividable in 3 sets:
• 3 IT phase measurements
• 3 I2T phase measurements
• 2 measurements computer by the sum of the IT phase measurements and I2T phase
measurements.
These measurements are always valid.
IT phase measurements
3 measurements based on the samples of the current phase:
T nb−1
( IT _ PhaseA) N = ( IT _ PhaseA) N − 1 + ∑ ia [t j ]
32 j =0
T nb−1
( IT _ PhaseB) N = ( IT _ PhaseB) N − 1 + ∑ ib [t j ]
32 j =0
T nb−1
( IT _ PhaseC ) N = ( IT _ PhaseC ) N − 1 + ∑ ic [t j ]
32 j =0
where:
• nb is the number of samples
• T is the period of the signal.
• 32 is the number of samples by period

These measurements must reside in a non-volatile variable (SRAM) to allow its recovery in
I2T phase measurements
3 measurements based on the samples of the current phase
T nb −1 2
( I 2T _ PhaseA) N = ( I 2T _ PhaseA) N − 1 + ∑ ia [t j ]
32 j =0
T nb −1 2
( I 2T _ PhaseB) N = ( I 2T _ PhaseB) N − 1 + ∑ ib [t j ]
32 j =0
T nb −1 2
( I 2T _ PhaseC ) N = ( I 2T _ PhaseC ) N − 1 + ∑ ic [t j ]
32 j =0
These measurements must reside in a non-volatile variable (SRAM) to allow its recovery in
IT and I2T sum measurements
These 2 measurements are computed by the sum of the IT phase measurements and I2T
phase measurements.
IT _ Total = IT _ PhaseA + IT _ PhaseB + IT __ PhaseC

I 2T _ Total = I 2T _ PhaseA + I 2T _ PhaseB + I 2T _ PhaseC
5.2.21 Focus 4: All Measurement Values: Threshold Detection thru Transmission

Focus 4: - Threshold detection THRU transmission
Six thresholds can be defined for each measurement: 3 upper thresholds and 3 lower
thresholds.
A hysteresis value configured on a per measurement basis is associated to the threshold
management. This value is a percentage of the full scale value of the measurement.
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 C0313ENa
FIGURE 37: THRESHOLDS DETECTION

5.2.22 Manual suppression

A measurement can be assigned to the SUPPRESSED state by an order issued from an
operator. No subsequent change of value or state on a "SUPPRESSED" measurement can
trigger any action: for example, display, alarm, transmission. The measurement takes the
SUPPRESSED state. When the operator "un-suppresses" the measurement, this one takes
its actual state.
5.2.23 Substitution
The value of a measurement can be substituted by an operator (state “SUBSTITUTED”,
value defined by the operator). The measurement stays in this state until he un-substitutes it.
When a measurement is substituted, no change of value nor state is transmitted, and
computations are made with the substituted state. When the measurement is un-substituted,
the actual state and value are transmitted to higher control levels and subsequent changes
of state and value are transmitted again.
5.2.24 Forcing an invalid measurement
When a measurement is invalid: that is, 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 event, the invalid information takes automatically
the FORCED state and the value defined in configuration.
The forced/substituted data are saved in SRAM (kept for minimum 48h without C264 power
supply).
The modified states are not reset by a C264 reboot.
A database switch (or evolution) reset the forced/substituted data.
5.2.25 Measurement resulting states
The Measurement resulting states, following the various filters, that you can apply include:
State Meaning
VALID Not in one of the following states
SELFCHECK FAULTY 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 crossed
UNDERSHOOT[1..3] One of the 3 undershoot values has been crossed
5.2.26 Transmission
The measurement value and state are transmitted on a client-server basis on the Ethernet
IEC-61850 network, using two modes:
• Report based mode: the measurement is transmitted to the subscribers with its value,
its status, its time stamping and the reason for change.
• GOOSE based mode (only on IEC61850 network): the measurement is transmitted in

multicast to the configured receivers.
NOTE: - A C264 client can have 32 numbers of IEC61850 servers and a
C264 server can have 16 numbers of IEC61850 clients
- GOOSE size is restricted to 128 binary inputs and 64 measurements
During a loss of communication between a client and a server, all server measurements are
set to UNKNOWN on the client.
The measurement information transmitted in a report include:
• The real value: that is, after scaling
• The resulting state: mapped on the quality field on IEC-61850
• The time stamping: in GMT time; and time quality
• The reason for the change:
− Change of quality: set if the measurement resulting state has changed
− Cyclic change: set if the measurement value has changed, without modification of
the resulting state
A Measurement value can be transmitted periodically or upon variation (% of nominal), and
anyway on state change.
5.2.26.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.26.2 Transmission upon variation
Measurements can be transmitted upon variation: a value is sent if the acquired value (Vacq)
is different from more than a specified amount ΔV from the previously transmitted value (Vt) (
i.e |Vacq-Vt| > ΔV).
ΔV is computed either from the last transmitted value (mode 1) or from the full scale value
(mode 2):
ΔV = (p/1000) * |Vt| where p is a value in the range 0 .. 255 and Vt is the last transmitted
value.
or
ΔV = (p/1000) * |Vmax| where p is a value in the range 0 .. 255 and Vmax is the full scale
value.
5.2.26.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.26.4 Limits and performances

To secure the proper accuracy for calculations, the sampling frequency must be exactly
adapted to the signal frequency that fluctuates around the basic frequency (50 / 60 Hz).
The required accuracy shows in the table that follows:
ITEM TMU210 TMU220

Current (with measurement CT) 0.5% In 0.2% In
Voltage (with voltage droppers) 0.5% Vn 0.2% Vn
Frequency 0.01Hz 0.01Hz
Angle 1° 1°
Time 1 ms 1 ms
Up to x harmonic 15th 15th
Power (with measurement CT) 1% 0.5%
5.3 Tap Position Indication (TPI) measurement 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: for example, 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 is transmitted, and computations,
for instance groupings, are made with the substituted state. When the TPI is unsubstituted,
the actual state and value are transmitted to higher control levels and subsequent changes
of state and value are transmitted again.
5.3.5 Forcing an invalid TPI
When a TPI is invalid: that is, 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 IEC 61850
• The time stamping: in GMT time; and time quality
• The reason for the change:
− Change of data: set if the value changed
− Change of quality: set if the quality changed
− Change due to control: set if the state or quality change is due to a control
The TPI information transmitted in a GOOSE is the same than in a report, except for the
"reason for change" and the time-stamping.
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 that count complementary states.
At processing level special persistent and complementary filters eliminate non-stable pulses.
The integer counter (also transmitted) can be scaled (among of energy of valid pulse).
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 i + M i −1 ) (ti − ti −1 ) ⎞
Ei = S f * ⎜ * ⎟
⎝ 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.
NOTE: Do not use the energy counter values for the billing application.
5.6 Basic Data Manipulation

5.6.1 Test Mode enhancements
The C264 Test Mode allows you to deactivate the DOU/CCU relays output in event of control
sequence.
The enhancements allow to:
1. manage the Test Mode in event of C264 redundancy (Test Mode is managed only if
the computer is in active mode, so a computer in standby mode can't be set in Test
Mode)
2. manage the control feedback datapoints
In event of computer redundancy, the Test Mode activation is performed independently for
each C264 (Main 1 rack and Main 2 rack) from SMT. If the Active C264 is set in Test Mode,
it remains Active. A Standby C264 cannot be set in Test Mode.
If the control is related to a datapoint: that is, feedback datapoint defined in configuration;
this one takes the control value in Test Mode:
• Open / Reset order => Open state for DPS, Reset state for SPS
• Close / Set order => Close state for DPS, Set state for SPS
To leave the Test mode, the user, through the SMT, changes the C264 mode to Operational.
The C264 automatically goes in Maintenance mode (transient) before going in Operational
mode.
The user of the Test Mode owns all responsibility of controls performed during the Test
Mode, and before leaving the Test Mode, he owns all responsibility to restore the system. In
Test Mode, all controls performed may impact Isagraf programs or PSL automatisms.
NOTE 1: Digital and Analogue Setpoint with measurement feedback are not
managed in Test Mode: that is, they are managed as in Operational
mode.
NOTE 2: IEC61850 exchanges (reports, gooses) are not impacted by the C264
Test Mode. That means that a control done in Test Mode, that is sent
to another computer - that is not in test mode - or to an IED (legacy or
not) may be fully and physically executed on the device.
5.6.2 Device order running
An « order running » SPS is managed on a per module basis. The “bay order running” is still
managed.
In event of Direct Execute control, this SPS is:
• SET as soon as the C264 accepts the control: that is, after the control checks
• RESET when the final control acknowledgement is sent

In event of SBO control, this SPS is:
• SET as soon as the C264 accepts the control selection: that is, after the selection
checks

An optional "order running SPS" on a per control type basis shall be available: that is, one for
open order / one for close order
In event of Direct Execute control, this SPS is:
• SET as soon as the execute control is received by the C264: that is, before the checks

In event of SBO control, this SPS is:
• SET as soon as the control selection is received by the C264: that is, before the
checks

In event of direct negative acknowledgement, those SPS may be SET then RESET with the
same time stamping. Those SPS shall be available only for DPC.
5.6.3 Controls management from PSL
A control issued from a PSL (or an DI/DO association) will be accepted even if an other
control is already on-going on the same output. In this event, the previous control is stopped
and the new control is launched (except if the new one is the same order than the previous
one: in this event, the new control is refused).
There are three ways to manage. PSL refers to PSL or DI/DO association, and Operator
refers to IEC61850 / ISAGRAF / local HMI:
• Control 1 from PSL and Control 2 from Operator
• Control 1 from Operator and Control 2 from PSL
• Control 1 from PSL and Control 2 from PSL

The event « Control 1 from Operator and Control 2 from Operator » is already managed: in
this event, the control 2 is rejected.
Events – Control 2 different from Control 1
Control 1 Control 2 Action Acknowledgement

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

PSL Operator Control 2 ignored Ack “Control in progress”
Operator PSL Control 2 ignored n/a (no ack managed in PSL)
PSL PSL Control 2 ignored n/a (no ack managed in PSL)
Operator Operator Control 2 ignored Ack “Control in progress”
5.6.4 PSL and Redundant Operation

Computer A is in active mode and Computer B is in standby mode. On the OI, the operator
uses C264 DI operation mimics and applies input to the PSL. After the Timer time (T-ON is
equal to 20 seconds), these events occur:
• The FBD output, an SPS on computer A/B, goes to the SET position
• FBD output 1, an SPC wired on DO of A/B and looped to DI for feedback, goes to the
SET position
• FBD output 2, an SPC wired on DO of A/B and looped to DI for feedback, goes to the
SET position
When Computer B goes into active mode and Computer A goes into standby mode, these
events occur:
• The FBD output 1 (SPC) and the FBD output 2 (SPC) stay in the SET position
• The FBD Output (SPS) goes to the RESET position for the Timer time (T-ON is equal
to 20 seconds).
After this time, the FBD Output (SPS) goes to the SET position.
When you use Micom S1 to modify the time of the timer, the FBD Output (SPS) goes to the
RESET position. It stays in the RESET position for the modified time and then goes to the
SET position.
When Computer A goes into the Faulty mode and Computer B goes into the active mode,
the FBD Output (SPS) goes to the RESET position for the duration equal to the Timer time.
Then the FBD Output (SPS) goes to the SET position. The FBD Output 1 (SPC) and FBD
Output 2 (SPC) stay in the SET position.
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
Page 120/248
Execution Execution via

C264/EN FT/D10
checks IED
or
System
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 38: 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
MiCOM C264/C264C
Functional Description
Execution via
Select Before Operate mode many
I/O boards
Execution or
checks
Execution via
IED
Device
Device
MiCOM C264/C264C
Selection
Functional Description
unselect
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 39: 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
Page 121/248
C264/EN FT/D10
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 40: 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 41: 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 42: 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 43: 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 44: 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 45: 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 46: CHECK OF UNIQUENESS

If a device is under control and another control is sent on this device, the second one is
ignored.
In event of uniqueness of the command at least to one of these levels the selection is
refused, with negative acknowledgement. The user may bypass this control during selection
request.
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 47: NORMAL TERMINATION OF DIRECT EXECUTE SEQUENCE

The chronogram that follows shows an abnormal termination of Direct Execute sequence.
The device hasn’t taken the expected position in the given delay.
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 48: 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 49: NORMAL TERMINATION OF THE CONTROL SEQUENCE
• Stage 1: device selection (closing the associated output control)
• Stage 2: the selection is confirmed by the associated input information in the feedback
delay (0 – 1-sec user selectable)
• Stage 3: close the device before the end of the selection timeout delay (0 – 10 MN
user selectable)
• Stage 4: the device has taken the expected position (close) in the feedback delay (0–
60 sec user selectable). The computer 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 50: 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 51: 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 with following data

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 52: 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 53: 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 54: 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
For ISaGRAF details, refer on §6.1.12 Attribute Words definition on Status Table (SPS, DPS,
MPS) and Quality Table (DP quality : xPS / MV).
6.1.12 Attribute Words definition

Status Table
Attribute for Attribute Word Define
SPS Status RESET 1
SUBST_RESET
FORCED_RESET
SET 2
SUBST_SET
FORCED_SET
DPS Status JAMMMED 3
OPEN 4
SUBST_OPEN
FORCED_OPEN
CLOSE 5
SUBST_CLOSE
FORCED_CLOSE
UNDEFINED_STATUS 6
Status Table
MPS State MPS_STATE1 7
MPS_STATE2 8
MPS_STATE3 9
MPS_STATE4 10
MPS_STATE5 11
MPS_STATE6 12
MPS_STATE7 13
MPS_STATE8 14
MPS_STATE9 15
MPS_STATE10 16
MPS_STATE11 17
MPS_STATE12 18
MPS_STATE13 19
MPS_STATE14 20
MPS_STATE15 21
MPS_STATE16 22
Quality Table
DP quality : xPS / MV VALID 0
SELFCHECK_FAULTY 1
UNKNOWN 2
FORCED 4
SUPPRESSED 8
SUBSTITUTED 16
TOGGLING 32
UNDEFINED_QUALITY 128
DP quality : MV SATURATED 64
UNDEFINED_QUALITY 128
OPEN_CIRCUIT 256
L_THRESHOLDVIOLATION 512
LL_THRESHOLDVIOLATION 1024
LLL_THRESHOLDVIOLATION 2048
H_THRESHOLDVIOLATION 4096
HH_THRESHOLDVIOLATION 8192
HHH_THRESHOLDVIOLATION 16384
DP quality : CT OVERRANGE 64
Quality and Ret code TOPO_UNCERTAIN 0
for is_connected_to FORCING
TOPO_UNCONNECTED 1
SUBSTITUTING
TOPO_CONNECTED 2
UNFORCING 3
UNSUBSTITUTING 4
SUPPRESSING 5
UNSUPPRESSING 6
Order Table
SPC ORDER_OFF 0
ORDER_ON 1
SELECT_OFF 4
SELECT_ON 5
DPC ORDER_OPEN 0
ORDER_CLOSE 1
SELECT_OPEN 4
SELECT_CLOSE 5
SPC / DPC ORDER_RAISE 0
ORDER_LOWER 1
SELECT_RAISE 4
SELECT_LOWER 5
BYPASS BYPASS_NONE 0
BYPASS_INTERLOCK 1
BYPASS_LOCKING 2
BYPASS_MODE 4
BYPASS_UNIQUENESS 8
BYPASS_AUTOMATION 16
BYPASS_SYNCHROCHECK 32
BYPASS_ALL 63
Acknowledge Table
Designation Attribute Word Define
Acknowledge Code : Positive
acknowledge ACK_OK 0
Acknowledge Code : Incoherent
command ACK_INCOHERENT_REQUEST 1
Acknowledge Code : Command
sent while computer is being
initialized ACK_COMPUTER_NOT_READY 2
Acknowledge Code : Site or bay
exploitation mode error ACK_BAY_SUBST_MODE_FAULT 3
Acknowledge Code : Computer
or GTW is in maintenance mode
or faulty ACK_CONTROL_MODE_FAULT 4
Acknowledge Code : Device
locked ACK_DEVICE_LOCKED 5
Acknowledge Code : A
command is being processed on
the device, or command
received during command
prohibited delay ACK_REQUEST_IN_PROGRESS 6
Acknowledge Code : Interlock
has refused command ACK_INTERLOCK_NOK 7
Acknowledge Code : Command
does not change device state ACK_DEVICE_ALREADY_IN_POS 8
Acknowledge Code : Board
fault ACK_HW_FAULT 9
Acknowledge Code : Device is
in an invalid position ACK_POS_INVALID 10
Acknowledge Code : Time-out
between selection and
execution or time-out in IED
answer ACK_TIMEOUT_FAILED 11
Acknowledge Table
Designation Attribute Word Define
Acknowledge Code : Device is
locked by an automation
function ACK_AUTOMATION_RUNNING 12
Acknowledge Code : Selection
received on an already selected ACK_DEVICE_ALREADY_SELECT
device ED 13
Acknowledge Code : Selection
received on a device configured
as Direct Execute ACK_DEVICE_NOT_SELECTABLE 14
Acknowledge Code : Command ACK_UNIQUENESS_INCOHEREN
uniqueness default CY 15
Acknowledge Code : Execution
command received on a non
selected device ACK_NO_SELECTED 16
Acknowledge Code : Operator
has cancelled command ACK_OPERATOR_CANCEL 17
while waiting for feedback TS ACK_EXTERNAL_FAULT 18
Acknowledge Code :
Acknowledgement failed ACK_FAILED_ORDER 19
waiting for TS TCIP present ACK_BAD_TCIP 20
Acknowledge Code : Bad tap
position after a command ACK_BAD_TAP 22
Acknowledge Code : Received
command "lower" while tap is
already at min ACK_MIN_TAP 23
Acknowledge Code : Received
command "raise" while tap is
already at max ACK_MAX_TAP 24
Acknowledge Code : Command ACK_DEVICE_FAILED_TO_OPER
to a non connected IED ATE 25
Acknowledge Code :
Synchrocheck has refused
command ACK_SYNCHRO_NOK 26
Acknowledge Code : ATCC is
stopped ACK_GLOBAL_ATCC_OFF 27
ACK_TOO_MANY_TRANSFOR
Acknowledge Code : MER 28
Acknowledge Code : ACK_INVALID_TOPOLOGY 29
Acknowledge Code : ACK_INVALID_TPI 30
ACK_TRANSFORMER_BAY_DI
Acknowledge Code : SCONNECTED 31
Acknowledge Code : ACK_MCB_TRIP 32
ACK_INVALID_TRANSFORME
Acknowledge Code : R_VOLTAGE 33
ACK_INVALID_BUSBAR_VOLT
Acknowledge Code : AGE 34
Acknowledge Code : IEC61850 ACK_PARAMETER_CHANGE_
conformance test add on IN_EXECUTION 35
Acknowledge Code : Non
PACiS IED failed on select ACK_SELECT_FAILED 36
Acknowledge Code : ACK_ICT_OUVERT 37
waiting OFF state of TCIP
information ACK_TCIP_TOO_LONG 21
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 55: 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:
6. Close the device using synchrocheck output control
7. Verify the device position become close in the given delay
8. Set off synchrocheck module if it previously set on
9. Deselect the device if it previously selected
The chronogram that follows shows a successful control sequence ”close with
synchrocheck”.
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 56: 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 57: 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 58: 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 59: 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 60: ”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 61: 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:
2. Verify selection device input information associated to the output (if is configured)
3. Wait for the execution close request or timeout selection
In event of fail of one of these operations, the device is deselected and the controls
sequence is aborted with a negative acknowledgement.
Execution phase:
4. Active the associated internal synchrocheck automatism for authorisation to close the
device
5. Wait authorisation to close
Event 1: Synchrocheck automatism respond OK before the time-out of the given delay
• Close the device
• Deselect the device (if it was previously selected)
• Send a positive acknowledgement

Event 2: Synchrocheck automatism responds NO before the time-out of the given

delay
• Send a negative acknowledgement

Event 3: time-out of the given delay without synchrocheck response
• 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:
configured)
4. In event of fail of one of these operations the controls sequence is stopped with
a negative acknowledgement
Execution phase:
1. Ask to the internal automatism to close the device
NOTE: The initiator of the request may force the closing of the device.
3. 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:
• Close the device
• 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)
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 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.10.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.10.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.10.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.10.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.10.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.10.6 Status of the device
If the status of the device is not valid, it is possible by configuration to prevent control.
6.10.7 Lock device
Controls are not allowed on a lock device.
6.10.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.10.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.11 HV Control Sequences

6.11.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.11.2 Disconnector
The control sequence of disconnectors is identical to single non-synchronised circuit
breakers.
6.11.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)
• 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
• Automatic Voltage Regulation (AVR)
• Automatic Tap Change Control (ATCC)
• Synchrocheck
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:
FIGURE 62: 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:
1. It is assumed that 10% of nominal voltage applied on the tripping coil makes its
magnetic effect low enough to release the tripping mechanism after activation. Taking
into account normal tolerance on power supply, this leads to a minimum value of R
being approximately 10 to 12 times the resistance of the tripping coil.
2. The input was tested to operate with a series resistor up to 40kOhm, still leaving
voltage across the input above the minimum. Taking into account tolerances, this
defines a maximum value for the resistor of 20kOhm.
We recommend the value in the middle of the range (geometrically). If Rc is the resistance of
the tripping coil, then:
R / 12xRc = 20kOhm / R
The power rating of the resistor must be such that it withstands permanent application of
maximum trip circuit voltage. Therefore:
P = (1.2 x Uaux)2 / R
+ Uaux
Computer
Protection relay
Vn+
DI-1
Vn-
Vn+
DI-2
Vn- Load Supply
Vn+
DI-3
Vn-
CB
Uaux
C0138ENc
FIGURE 63: 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 64: 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:
C0461ENa
FIGURE 65: 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.1.4 Automatic Voltage Regulation–AVR

7.1.4.1 Presentation
7.1.4.1.1 Role
MiCOM C264 with AVR (Automatic Voltage Regulation) is a compact Voltage Regulation
solution for Electrical Substations; it automatically regulates the voltage level on the
secondary side of HV/MV and/or MV/MV transformers.
It is able to automatically send secured commands (Raise, Lower) to the Tap Changer, fully
aware of the transformer characteristics (voltage,…), the Tap Changer characteristics
(position number, inter tap timers,…), the voltage targets and the various transformer or tap
changer alarms.
Note: the AVR function cannot be used on one C264 together with another built-in function.
7.1.4.1.2 Topologies
Two C264 types are defined to address specific AVR issues:
• Type 1 for a single transformer
• Type 2 for transformers in parallel (secondary poles are interconnected in pairs) –

mode Master-Followers (up to 4 followers C264 with AVR)
7.1.4.1.3 Modes
The operator decides on the LHMI which way he/she wants to operate the AVR:
• Manual (open loop): the operator forcefully issues Raise/Lower commands to the tap
changer from the LHMI
• Automatic (closed loop): the AVR algorithm issues Raise/Lower commands to the tap
changer when the voltage is outside limits and tap changer conditions permit; the
operator can still deactivate the algorithm from the LHMI.
The possibilily of other manual controls In automatic mode depends on the parameter
manual controls allowed:
• Not allowed
• Only when AVR is locked (whether it is due to the External regulation locking or to an
AVR additional features: overcurrent detection, tap changer blocking)
• Always
7.1.4.1.4 Interfaces for a single transformer
Optional:
Raise/lower
Analog Inputs
WD
output signals
contacts
Optional:
Analog Outputs
Optional:
VT fuse
Serial Comm.
CB posit. to IEDs
Settings (S1-PACiS Tool)

Maintenance (Web Browser)
C0462ENb
7.1.4.1.5 Hardware
The MiCOM C264 includes in a 40 TE rack:
• An LCD screen, a BIU2xx board and a CPU270 board

• A DIU2xx board to acquire 16 Digital Inputs:
− 5 Tap Position Indications (typically on 6 bits with BCD encoding, up to 64 bits
with BCD, Gray, binary codes,…)
− 2 CB positions
− 1 VT Fuse
− 1 Tap Changer fault (option)
− +7 customizable DIs (Bay L/R, AVR Auto/Manu, AVR on/off, alarms, external lock,
voltage target selection)
• A DOU20x board to control 10 powerful Digital Output relays:
− 2 Raise/Lower controls
− 1 AVR fault (WatchDog)
− 1 AVR Mode Auto/Manu
− 1 AVR ON/OFF
− 1 Master /Follower signal (type 2 only)
− 1 Minimize Circulating Current signal (type 2 only)
− +3 (type 1) or 5 (type 2) customizable DOs (I>, V>, alarms, locking, …)
• A TMU220 board (4 CTs / 5 VTs) for direct acquisition of currents and voltages
− CT: 1 thru 3 phases (type 1), 3 phases (type 2) + 1 earth
− VT: 1 thru 3 phases (type 1), 3 phases (type 2) + 2 customizable inputs
• An AIU board (option) to acquire Tap positions, voltages…(4-20 mA)

• An AOU board (option) for analogue outputs (4-20 mA) to repeat the Tap changer
positions or measurement values (voltages, circulating currents,…)
7.1.4.1.6 Exchanges over the bus
The IEC 61850 bus can convey additional data:
• TPI and Tap changer status, “tap pulse duration”

• power factor
• target voltages and target voltage setpoint, compounding method
• topology information from IEDs (in place of serial bus) or other C264
• settings from MiCOM S1
• measurements and commands when several transformers are involved:
Each transformer is controlled by one computer but the AVR function is only activated on
one computer. The figure exemplifies an architecture that controls two transformers:
acquisition of U,I,Q,P
Tr2
station bus C264-2
(iec 61850)
command of tap changer

C264-1
AVR on
Tr3
C264-3

C0344ENa
AVR function is activated on computer C264-1. This computer gets analogue values through
the station bus from computers C264-2 and C264-3 and issues tap changer commands
through the station bus.
7.1.4.2 Moving a tap changer
In this part, the settings name and values are surrounded with quote marks (“…”), while the
first letters of status labels are capitalized. The former are set, the latter positioned.
7.1.4.2.1 Actual voltage
Depending on the “Regulation types”, the actual (i.e. measured) voltage can be:
• either a “phase voltage Van” (Vpn on the first schematic)

• or a “compound voltage Ubc” (Vpp on the first schematic)
The actual voltage can include a Line Drop Compensation (see further).
For double wound transformer (“double wound” set to Yes), according to the setting “double
wound voltage”, the automatic voltage regulation applies to the:
• voltage and current of one winding (voltage 1)
• voltage and current of the other winding (voltage 2)
• average voltage and current of the 2 windings (average voltage)

If the difference between the 2 voltages is larger than a set value (“double wound voltage
difference”), the signal Double wound voltage difference is positioned.
7.1.4.2.2 Target voltage

Depending on the Target voltage management, the target voltage can be:
Locally or Remotely
The Remote / Local target voltage management mode is running when the Target Voltage
Management Mode is set to Remote/Local and the AVR is in automatic mode. The target
voltage used by the AVR is either a remote target voltage received from a remote control
point, or a local target voltage used in the case of unavailable remote target voltage
(invalidity, loss of connection).
The remote target voltage comes from a remote control point (setpoint from any client by
IEC61850 or other available protocol); to be valid, it is subjected to min, max, max
difference; until the end of the confirmation delay, the latest valid remote target voltage value
is used.
In event of invalid remote target received, the local target voltage takes over. The local
target voltage is configured with SCE and can be modified with MiCOM S1
Controlled
The remote / local target voltage is selected through controls.
In local target voltage mode, the AVR is able to treat an incoming remote target voltage
value (in order to return to the remote target voltage mode). If a received remote target
voltage value is valid, the remote target voltage becomes the new target voltage mode,
following the transition local to remote conditions:
• At AVR start up, the local target voltage mode is active for a defined delay (end of
local target voltage delay).
• If a valid remote target voltage value is received before the end of the delay, the
remote target voltage mode is set at the end of the delay.
• If a valid remote target voltage value is received after the end of the delay, the remote
target voltage mode is set immediately.
When the target voltage mode changes from remote to local, the same delay is launched,
and the behavior is identical.
An operator can, with a dedicated control, forcefully put the target voltage mode to local
target voltage. In this event, the mode is set immediately.
Period dependent
For example:
7.1.4.2.3 Regulation
The actual voltage is compared to the target voltage.
If the actual voltage remains outside of the “regulation deadband” for an “initial tap time
delay” (TA1), the C264 with AVR commands a tap change.
Any voltage swing that passes through the complete deadband, causes the “initial tap time
delay” to be reset and a new time cycle to be started.
If more than one tap change is required to bring back the voltage within the deadband, the
second tap changer is activated after TA2 (“inter tap time delay”). Note: TA2 < TA1.
If applicable, the last tap changing is delayed by an “end tap delay”.
The command occurs only if the following conditions prevail:
• AVR mode is automatic

• voltage is above the “voltage presence threshold”
• “Primary CB state”, Circuit Breaker position on the primary side of the transformer is
set to CLOSED
• No VT fuse information positioned
• No regulation locking signal (External Lock or Tap Changer fault) positioned
7.1.4.3 Additional monitoring functions

7.1.4.3.1 Tap Changer position on Voltage Loss
The actual voltage is present/missing (lost) whether it is above/under the “voltage presence
threshold”.
According to the “voltage loss position tap”, the AVR can:
• either move the tap changer “on a defined tap”

• or “lock the automatic” regulation as long as the voltage is missing.
In the first case, the “tap changer position (on voltage loss) behaviour” can be set to:
• keep the tap changer on the “current tap” (no tap control performed)
• move the tap changer to the “preset tap”
• move the tap changer to the “lowest tap”
The function sets the tap changer on the “defined tap” position, only if the following
conditions prevail:
• The AVR mode is automatic

• “Tap changer position on voltage loss” function is active
• The “Primary CB state”, Circuit Breaker position on the primary side of the transformer
is set to OPEN
• No other regulation locking information is set

Sequencing of commands: the subsequent command occurs not earlier than the “preset tap
delay”.
7.1.4.3.2 Fast Tap Changer move AFTER Voltage Loss and Voltage recovery
When the “Fast tap changer move after voltage loss” function is set, the AVR issues
Lower/Raise commands TA3 after the voltage has overrun the “voltage presence threshold“.
The command occurs only if the following conditions prevail:
• The AVR mode is automatic

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

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

• position/reset the Overvoltage signalisation AND the Regulation Locking information
7.1.4.3.8 UnderVoltage Detection

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

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

• position/reset the Overcurrent signalisation AND the Regulation Locking information
7.1.4.3.10 Tap Changer Maintenance: Tap Counting

The numbers of automatic + manual tap changes are counted as follows:
Number On the “slipping since C264 init since latest operator

period for counting” reset
Overall x up to 6,000,000 x
changes
Raise x up to 3,000,000 x
Lower x up to 3,000,000 x
Limits x – –
reached
Time of use – For each tap as long as voltage is present
The date of the latest operator reset is also recorded.

NOTE 1: On operator reset
• the partial number of “tap changes”, “raise” and “lower” controls are reset
• the partial time of use with voltage present of each tap is reset
• the current date becomes the new “last reset date”

NOTE 2: The time of use is recorded, only if the voltage is present, and the Tap
Position Indication and the TCIP signalisation are valid.
Data visualization and use

Histograms are shown on a dedicated page of the C264 Maintenance Tool. Refer to the IN
chapter (Operations with buttons/Statements).
As counters, all the sums can be viewed:
⇒ on the Station Bus (IEC61850)

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

7.1.4.4 Line drop compensation
To regulate the voltage at a remote point on the feeder, the LDC simulates voltage drop of
the line and artificially boosts transformer voltage at times of high load.
The LDC is validated by the “compounding activation” and ruled by the active “compounding
method”.
Vr = Vm - Vcomp
Z = R + jX, R and X are % of Vn/In
R = “Active compounding method parameter A1”, % of Vn/In (nominal voltage and current)
X = “Active compounding method parameter B1”, % of Vn/In (nominal voltage and current)
The reactive “compounding method” is used only when two transformers are in parallel.
7.1.4.5 Other functions

7.1.4.5.1 Additional Measurements (Optional)
If 3 CTs and 3 VTs are fed into the C264, additional measurements can be computed:
• Frequency
• φ
• Cosφ
• I sinφ, Σ I ² since the latest reset of counters
• Active and apparent powers
• Circulating current (transformers in parallel)
These calculated measurements can be viewed locally on the Local HMI (LCD Screen).
7.1.4.5.2 Raise/lower control and voltage target from external signals
Depending on “AVR mode”, additional inputs can be used:
• “Automatic”: to activate a specific target voltage:
⇒ Target Voltage 5 (Vn-5%)

⇒ Target Voltage 2, 3, 4 (Voltage Boosting)
These external commands have precedence over the Local LCD commands and are active
as the external signal is positioned.
• “Manual”: to activate Raise/Lower commands from wired signals:
⇒ Raise Command Input

⇒ Lower Command Input
The activation of Raise/lower Controls also depends on the usual AVR conditions (CB
status, TC fault,…).
7.1.4.5.3 Reverse Power Flow (RPF)
7.1.4.5.3.1 Detection
Reverse power flow is detected with the sign of the secondary Active Power measurement
value.
As long as the Active Power measurement value is above 0, no reverse power flow is
detected.
If the Active Power measurement value is under 0, the reverse power flow detection delay
starts. At the end of the delay, if the Active Power measurement value is still under 0, the
signaling Reverse power flow detected is positioned.
When reverse power flow is detected, if the Active Power measurement value is above 0, the
reverse power flow detection delay starts. At expiry, if the Active Power measurement value
is still above 0, the signaling Reverse power flow detected is reset.
Reverse power flow detection is done only if the line current value is more than or equal to
the defined RPF current threshold. Otherwise, no reverse power flow detection is
performed.
Active power
0 T
Time counter
Tconfirm
T
Reverse power
flow detected On On
7.1.4.5.3.2 Behavior
When reverse power flow is detected, the RPF management mode defines the behavior:
• Ignore: nothing specific is done is this case, regulation is still performed in the same
way.
• Block operation: no more automatic regulation is performed, only manual raise and
lower control are allowed (if set). The automatic voltage regulation is locked by
reverse power flow, and the signal AVR locked by reverse power flow is positioned.
This signal is reset when the reverse power flow detection ends.
• Regulate in reverse: the automatic regulation is running in reverse power flow mode.
The transformer primary side analog measurements (U, and if compounding is used: I and
φ) are needed for automatic regulation. These measurements are received by the AVR, and
not computed from transformer secondary side analog measurements.
The automatic voltage regulation is monitoring the primary voltage, current and phase
difference, and keeps the primary voltage in a deadband within a target voltage by activating
raise/lower controls. The parameters defined for “normal power flow” regulation are not used
in the case of RPF regulation.
The AVR activates the tap changer with a RAISE control, after a first (or next) tap delay, if:
• Primary Voltage > Target voltage for primary voltage x (1 + Deadband)
The AVR activates the tap changer with a LOWER control, after a first (or next) tap delay, if:
• Primary Voltage < Target voltage for primary voltage x (1 - Deadband)

With Primary Voltage = Measured primary voltage – Z x Measured primary current
NOTE: The tap changer raise/lower activation is inverted in RPF regulation
mode.
7.1.4.5.3.3 Compounding in RPF mode
Z is the complex load impedance defined by the parameters A1 and B1 for active
compounding, and parameters A2 and B2 for reactive compounding.
The values can be doubled individually by activating a setting.
Coefficients A1 and B2 are specific with the Compounding in RPF mode.
Active compounding: Z = R + jX, R = A1 x compounding ratio, X = B1 x compounding ratio.
Reactive compounding: Z = R - jX, R = A2 x compounding ratio, X = B2 x compounding ratio

with:
• compounding ratio = (nominal voltage / √ 3) / (compounding nominal current x 100)
• nominal voltage: the same nominal voltage as for normal regulation (secondary of
transformer)
• Compounding nominal current: a nominal current defined in database only for

compounding management (this compounding nominal current is defined for both
normal regulation and reverse power flow regulation).
Compounding in reverse power flow mode is available only with single phase voltage.
If no compounding is needed, the A1, B1, A2 and B2 values must be set to 0.
7.1.4.5.3.4 Other differences
No check on voltage presence is done. When RPF is detected, it means the voltage is
present on both sides of the transformer.
The following AVR functions are not available:
• Abnormal voltage detection
• Overcurrent detection
• Overvoltage detection
• Undervoltage detection
• Tap changer position on voltage loss
• Fast tap changer move after voltage loss
• Tap changer blocking
• Tap changer with intermediate position
• Transformer double wound voltage management.

The target voltage can be changed (within its range) with the setting tool or with a dedicated
setpoint control. All the target voltage management modes usable in the normal power flow
regulation mode are not available.
Limits:
• Not usable with a double wound transformer.
• Usable only with standalone transformer management even when in normal power
flow (not with a transformer in parallel method). Master / follower configuration must
be set to none.
7.1.4.6 Transformers in parallel
Two methods can be used whether the transformers are identical and work together or not.
7.1.4.6.1 Master/Followers method
ROLES:
In a group of transformer bays, one C264 with AVR is appointed “Master”, the others
“followers”. The master transmits its TPI to the followers over the Station Bus and elaborates
the commands for all the transformers. All the operator controls (activation/deactivation), if
any, are put on the master C264, which in turn activates/deactivates the followers.
The followers receive the master’s TPI, offset any discrepancy with their own TPI and
execute the commands coming from the master over the Station Bus.
C264 with AVR1 C264 with C264 with AVR3
IEC61850
T T T
C C C
BB
BB
C0467ENa
The Master compares the tap position of the followers with its own tap position and if
deviations are detected, the master put commands to bring them to its own position.
No circulation currents are evaluated; this imposes severe limitations on the network
operation:
• transformers identical, with the same impedance

• same number of taps
• transformers on the same tap position
The indication of which C264 is the Master and which one is “Follower” can be viewed
• on LCD (optional MiMIC Page)

• on configurable Leds of the Front Panel
It can be available
• on an output contact
• on the Station Bus / Scada
and used in PSL/Isagraf automation.
In event of the Master failure (reboot, disconnection, switching to maintenance mode) the
“Master failure management” offers two possible fallback plans:
• a Backup Master can be selected among all the followers:
⇒ manually by the operator (on LCD or from Station Bus)

⇒ automatically to insure a continuous service, using the configured “Follower
Master Backup”.
If the master recovers, the backup master remains master. The master regulates its voltage
in stand alone mode.
NOTE: This backup mode requires a good health network. In event of a faulty
network, the TPI received by the followers, still have the quality
Unknown. Then, after the “backup mode delay”, all the followers will
switch to a standalone mode.
If the mode goes automatically to standalone, returning requires a manual operation (reset
process in which the master restarts all the followers).
• drop the coupled regulation: all the C264s operate standalone.
7.1.4.6.2 “Standalone regulation”

There are no restrictions on the transformers.
The differences between two transformers superimpose a current Ic in both incomers:
If the transformer #1 is on a higher tap than #2:
− Current seen by #1 = IL + Ic
− Current seen by #2 = IL – Ic
#2
T IL-Ic
2IL
Ic
T
IL+ Ic
#1
C0468ENa
Two methods are offered:
⇒ “Minimizing circulating current”: refer to the ATCC section further
The topology (i.e.which transformers are interconnected) is dynamically evaluated

by a C264-MCC (minimize circulating current). It computes the U,I,P,Q for all the C264
that control transformers (up to 4) and transmits the values over the Station Bus.
⇒ “Negative reactance compensation”, in conjunction with the Reactive

“Compounding method”.
#2
T IL-Ic
Vxl Vr
2IL
Ic
T
IL+ Ic
#1
As Ic is not present in the feeder, another method is needed: compensating the voltage
attenuation due to currents circulating from one transformer to the other.
With reactive compounding, the voltage to be regulated (Vr) is evaluated as follows:
Vr = Vm – Vxl, where:
Vr = actual voltage to regulate
Vm = measured voltage
Vxl = Compounding voltage = Z.I where Z = R – jX
R = “Reactive compounding method parameter A2”, % of Vn/In (nominal voltage & current),
this the resistive part of the load line
X = “Reactive compounding method parameter B2”, % of Vn/In (nominal voltage & current),
this the reactive part of the transformer impedance (the transformer impedance is mostly a
reactance)
NOTE: For a power factor near 1, this negative reactance compensation has
a good accuracy, but if the power factor is low, this compensation
mode is no more accurate.
7.1.5 Automatic voltage regulation–ATCC
The Automatic Voltage Regulation–ATCC function automatically maintains a correct voltage
at the lower voltage of transformers by controlling the tap changer of transformers.
7.1.5.1 Presentation
7.1.5.1.1 Topologies
A substation includes busbars and transformers.
A group is a set of interconnected busbars. A transformer belongs to a group if it is
electrically connected to a busbar of this group at the low voltage level. The voltage target is
that of the highest priority busbar.
The partition is dynamic: two independent groups may be merged as a result of the closing
of a circuit breaker.
Typical topologies:
• one busbar connected to one or several transformers in parallel. Transformers are in
parallel if their secondary poles are interconnected.
• several coupled busbars in a group that includes one transformer or several ones in
parallel (see an example further)
• Each transformer is controlled by one computer but ATCC function is only activated on
one computer. The figure that follows shows an example of the architecture for the
ATCC function that controls two transformers
Tr2
station bus C264-2
(iec 61850)

C264-1
AVR on
Tr3
C264-3

C0344ENa
ATCC function is activated on computer C264-1. This computer gets analogue values
through the station bus from computers C264-2 and C264-3 and sends tap changer
commands through the station bus.
7.1.5.1.2 Situations requiring ATCC

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

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

(supervision values)
• Invalid voltage [inv voltage]
• Tap changer abnormal if:
− TCIP signal is too late [TAP bad TCIP] or too long [TAP long TCIP]
− The tap is invalid [TAP invalid]: tap number is not the required tap; you may have
this problem after a tap operation if the tap number is not the expected one.
This TAP bad TCIP alarm is reset 30 s after the group is switched to ATCC Off
• ATCC hunting: this alarm is reset 30 s after the group is switched to ATCC Off.
• Overcurrent, overvoltage
Busbar:
• Invalid voltage (when different values for parallel transformers) [inv voltage]
• More than 4 transformers in the group [max transfo]
• A circuit breaker or a disconnector in an invalid state in the group [inv module]

Global:
• Target unreached
• ATCC defect: raised if one of these alarms is raised, and is reset if all of them are
reset
• Error Log Indication: raised if one of the input is raised and is reset if the operator
selects the "Clear ATCC Faults" command.
• DBI override
7.1.5.2 Monitoring logic

7.1.5.2.1 Modes
From the PACiS OI or from a SCADA, in agreement with the Substation control mode, the
operator controls the Global ATCC mode (substation level) and the busbar ATCC modes.
Substation control mode Control from the RCP Control from the SCP (OI)
(SCADA)
Local inhibited allowed
Remote allowed inhibited
It is up to the operator to choose, on a global basis, how the mode (that is, the ATCC status)
is changed:
⇒ On group interconnection: the group resulting of the merging of two groups in

different modes can be off or on
⇒ When bay turns to local control: the bay can go off or on
7.1.5.2.2 Conditions for an active automatic voltage regulation

The following conditions are required for automatic regulation to be active:
• The ATCC mode is on
• The Circuit Breaker at the other side of the transformer (primary) is closed
• No “regulation locking” information (AVR defect alarm, external lock, run away,
overcurrent on a transformer)
For ATCC/homing to take place:
• the measured voltage must be within tolerances set as ratios of the nominal voltage:
⇒ tolerable nominal under voltage

⇒ tolerable nominal over voltage
• the deviation to the target voltage must be lesser than a set ratio of the nominal
voltage:
⇒ max voltage difference

Moreover, before sending a tap changer control (Raise/Lower), the following conditions are
required:
• No “tap in progress“
• No “higher position” information, for a raise control
• No “lower position” information, for a lower control

7.1.5.2.3 Transformers status logic
7.1.5.2.4 Busbars status logic

The current busbar mode is equal to (busbar ATCC status) AND (Global ATCC status).
The status is Off if:
− the status of one of the transformers connected to it is Off

OR
− the busbar voltage is invalid

7.1.5.2.5 Group status logic
The average voltage is invalid if:
− one of the voltage differs by more than “max voltage difference” (ratio) from the
average voltage
OR
− one voltage is invalid.

The status is On if at least one of the busbars in the group is On.
The status is Off if at least one of the conditions that follow is met:
A busbar in
the group &
Mode on
group inter-
connection are
Off
More than 4
Global ATCC transformers
status is Off in the group
Group Status
= Off
Invalid Invalid
average disconnector/
voltage circuit breaker
in the group
C0472ENa
If two busbars get disconnected, they keep their previous mode.

When a fault occurs, the related busbar ATCC turns off.
7.1.5.3 Moving tap changers

7.1.5.3.1 Target voltage
When the operator changes a target voltage, the new target voltage is indicated immediately.
The actual target voltage cannot changed by more than the “voltage target ramping rate” if
the busbar is under automatic control. If the busbar is not under automatic control the new
target voltage is immediately in force.
Each voltage level has other attributes:
• 5 voltage targets, with a default target (one of the 5)
• 2 deadbands, one is coarse (DB1, to initiate tapping), the other is fine (DB2, to end
tapping)
• a max tap change rate of change that cannot be exceeded when moving the tap.
Each busbar voltage target is selected among the 5 through controls, in accordance with the
voltage target ramping rate.
If the busbar is part of a group, the target in force is the one of the highest priority busbar. A
single tap is changed at a time within a group but several groups may be active
simultaneously.
Each group has to reach the target voltage.
If the voltage is outside DB1, then an initial timer T1 is set and the tap control is issued once
the timer has elapsed.
More tap changing may be necessary in order to enter DB2: they are actuated when the
second timer T2 has elapsed; the changing is subjected to the max tap change rate.
+ DB1
+ DB2
Vtarge
-DB2
-DB1
Time
T1 T2
REMOTE BUSBAR:
The voltage target may be set for a point far from the LV transformer side.
Reference_ULV = (Target_ ULV + Drop_U) x set point ponderation (0.9 …1)
ULV is the actual measured value
Compounding methods:
• Setpoint adjustment: Drop_U ² = PLV x R% + QLV x X% where

PLV and QLV are local measured active and reactive powers
R% and X% are resistive/reactive coefficients
• Voltage adjustment: in place of ULV, use Drop_U ² = (ULV –A)² + B² where

A = (RL X P + XL X Q)/ ULV
B = (XL X P + RL X Q)/ ULV
XL and RL are transfo-busbar resistive/reactive coefficients
C0474ENa
NOTE: If line drop compensation is not used, set the resistive and reactive
coefficients to the minimum.
7.1.5.3.2 Voltage is outside of the Target Voltage Deadband

When the regulated voltage moves outside of the deadband settings for a definite time, the
C264 send commands to Tap Changer mechanism to bring it back within the set deadband
limits.
The Voltage Deadband is expressed as a percentage of the nominal voltage. Depending on
the number of transformers in a group, different set coefficients are applied.
Voltage deadband = Base Voltage deadband x voltage coefficient.
Examples:
example 1 example 2
Group with 1 transformer 1 1
Group with 2 transformers 1 1
Group with 3 transformers 1 2/3
Group with 4 transformers 1 1/2
Decision to move the tap changer is made when:
• Voltage > Target Voltage + Voltage Deadband x Nominal Voltage

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

⇒ Inter tap delay T2 is adjustable between 0 and 120 s in 0,1 s increments.
To ensure that transient voltage fluctuations do not cause unnecessary tap change, the
voltage must remain outside of the deadband for an “initial Tap Time Delay” (settable T1).
Any voltage swing that passes from through the complete deadband from one side to the
other, causes the “initial tap time delay” to be reset and a new time cycle to be started.
If a tap changing is required after a previous tap control:
• Ti is the date when the previous tapping was performed
• T is the current time
• RateMax is max tap change rate
• T2 is the inter tap delay
• Vi was the secondary voltage at Ti
• V is the current secondary voltage

For a Tap Up (to increase voltage), tap is changed when
T > Ti + T2 and V < Vi + RateMax x (T–Ti)
For a Tap Down (to decrease voltage), tap is changed when
T > Ti + T2 and V > Vi – RateMax x (T–Ti)
The maximum voltage rate is achieved as described in the example below:
Volt
RateMax
Time
T1 T2 T2
T0
Tap RAISE 1 Tap RAISE 2 Tap RAISE 3

C0010ENa
FIGURE 66: VOLTAGE REGULATION

Tap RAISE 1 is performed after T1.
Tap RAISE 2 is performed T2 after Tap RAISE 1, at this time the voltage change rate is
lower than the maximum rate.
Tap RAISE 3 is NOT performed T2 after Tap RAISE 2, because at this time the voltage
change rate is more than the maximum rate. It is performed when the current voltage change
rate becomes lower than the maximum rate.
It is possible to choose a T1 delay as a fixed delay or not, i.e. an inverse time delay.
When inverse initial time delay is selected: the deviation is:

DV = | actual group voltage - deadband limit voltage |
• IF DV < 1% target voltage THEN initial tap delay = T1.
• IF 1% ≤ DV < 10% target voltage THEN initial tap delay = T1/DV.
• IF DV ≥ 10% target voltage THEN initial tapdelay = T1/10.
Example: Target = 135,96 T1= 40,00 s DeadBand2 = 136,64
Busbar DV = (BusBar-DeadBand) %DV = (DV*100)/Target Time Out

137 0,36 0,26 40,00 %DV <1%: Timeout = T1
139,03 2,39 1,76 22,75
140,01 3,37 2,48 16,14
141,01 4,37 3,21 12,44
1% < %DV <10%:
143,04 6,40 4,71 8,50 Timeout = T1/%DV
145,04 8,40 6,18 6,47
146,01 9,37 6,89 5,80
150,01 13,37 9,83 4,07
151,02 14,38 10,58 4,00
%DV >10%: Timeout =
152,05 15,41 11,33 4,00 T1/10
153,03 16,39 12,06 4,00
When a transformer belongs to a group of several transformers, the time out is applied to the
group. 2 different groups have separate timeout references, thus allowing simultaneous taps.
The tap is defined as the "first one" when (logical OR):
• The group mode has changed
• The voltage comes back into the deadband2
• When the voltage crosses from one side of the deadband to the other side.
7.1.5.3.4 Homing
When the mode of the busbar is in automatic control, homing taps transformers such that
their open circuit terminal volts follows the volts on the busbars that they are selected to
within 3% of the busbar voltage.
Homing is active:
• If there is at least one transformer connected on the related busbar and
• If the transformer busbar disconnector is closed and
• If LV circuit breaker open.

Homing is disabled while the busbar voltage is less than Umin (80% of nominal voltage).
If a transformer is under Homing Mode, a manual control is not accepted.
If (and only) a fault on the Tap Changer remains active, the transformer remains OUT of
automatic control. As a consequence, homing ceases as long as the Tap Changer is faulty
and until the operator selects "Clear AVR faults".
Homing Initial tap delay is used for the first tap in the homing mode.
Homing Inter tap delay is used between successive taps.
7.1.5.4 Calculation modes for a busbars group
If a group includes more than one transformer and is in automatic control mode, then the
coordination of the transformers of the group aims at minimising the circulating power. To
achieve this, there exist three calculation modes depending on the substation constraint and
customer requirement. By configuration one of the three is chosen.
For the three following calculation modes, if all the transformer tap-changers reach their end
stop while tapping is required to go further, then the substation alarm "target unreached" is
generated. When the problem is cleared, this alarm disappears.
First calculation mode: “TAP”
In this event, the assumption is:
• The primary voltages of the transformers are identical
• The number of taps and tapping ranges of the transformers are identical
Then the maximum Tpi range between the transformers will be 1 and there will be a
balanced control of them when the voltage is changing.
Calculation is as follows:
• if voltage is OUT of the deadband and
⇒ under the deadband -> action is raise on the transformer with the lowest Tap
⇒ over the deadband -> action is lower on the transformer with the highest Tap
• if voltage is IN the deadband, the system sets the transformer within one tap
Second calculation mode: “Transformer ratio”

In this event, the assumption is that the primary voltages of the transformers are identical.
Calculation is as follows:
• if voltage is OUT of the deadband and,

⇒ under the deadband -> action is raise on the transformer with the lowest
transformer ratio
⇒ over the deadband -> action is lower on the transformer with the highest
transformer ratio
• if voltage is IN the deadband, the system sets the transformer within a percentage of the
transformer ratio. This percentage P is calculated for all groups:
P = Maximum (Tpi range / (number of taps - 1 ))
Example:
Group with 3 transformers:
• SGT1: 19 taps, Tpi range = 30 %

P = Max (30 / 18; 30 / 18; 20 / 15) = 30/18 % = 1.67 %
So, the 3 transformers stay within 1.67 %.
Tap operation if (ratioMax - ratioMin) > 0,0167 ratioNom, with:
• ratioMin = Minimum transformer ratio of the 3 transformers
• ratioMax = Maximum transformer ratio of the 3 transformers
• ratioNom = Nominal secondary voltage / Nominal primary voltage (defined in

configuration)
Third calculation mode: “circulating current minimisation”
There is no assumption that the primary voltages of the transformers are identical.
Example of two transformers:
SGT1 SGT2
I1 I2
Each transformer is characterized by:
• Sn (power value)
• x (% impedance at Sbase = 100 MVA), in other words X (reactance) = x . Un² / Sbase
• U, I, P, Q
• Current tap
• Un (nominal secondary voltage)
A transformer can be presented as below:
The transformers can be presented as below:
I
Ic
X1
X2
U
I1 I2
E1 E2
U = E1 - X1.I1 = E2 - X2.I2 => E1-E2 = X1.I1 - X2.I2

I = I1 + I2
E1 - E2 = (X1 + X2 ) . Ic
=> the circulating current Ic = (X1.I1 - X2.I2) / (X1 + X2)
For each transformer, we have U,I,P,Q (U1,I1,P1,Q1 and U2,I2,P2,Q2)
For i=1 or i=2, Qi/Pi = tan ϕi
According to the signs of Pi and Qi: -π < ϕi < π
If there is a circulating current from transformer 1 to transformer 2 then ϕ1 > ϕ2.
U1 = U2
I
I2
φ1
I1
Voltage out of the deadband
If the voltage is out of the deadband and active power > 0 (|ϕ| < π/2) then:
• If the voltage is under the target then transformer with highest |ϕ| is tapped UP
• If the voltage is over the target then transformer with lowest |ϕ| is tapped DOWN
If the voltage is out of the deadband and active power < 0 (|ϕ| > π/2) then:
• If the voltage is under the target then transformer with lowest |ϕ| is tapped UP
• If the voltage is over the target then transformer with highest |ϕ| is tapped DOWN
For three or four transformers, the same algorithm is used.
Voltage into the deadband
If the voltage is into the deadband then the circulating current must be checked to know if it
is possible to reduce it.
∆U = E1 – E2 = |X1*I1 - X2*I2|
∆U is compared to the voltage step corresponding to one tap (∆U1tap).
Tpi range: tap span for the transformer
NbTap: number of taps for the transformer
Un: nominal secondary voltage
∆U1tap = (Tpi range/(NbTap -1)) x Un
if ∆U > ∆U1tap and if ϕi > ϕj so
If the voltage is out of the deadband and active power > 0 (|ϕ| < π/2) then:
• If the voltage is under the target then transformer with highest |ϕ| is tapped UP
• If the voltage is over the target then transformer with lowest |ϕ| is tapped DOWN
If the voltage is out of the deadband and active power < 0 (|ϕ| > π/2) then:
• If the voltage is under the target then transformer with lowest |ϕ| is tapped UP
• If the voltage is over the target then transformer with highest |ϕ| is tapped DOWN
For three or four transformers, the same algorithm is used.
7.2 Synchrocheck
7.2.1 Synchrocheck – General

It is impossible to plug the computers directly into the high voltage electric network. The
computers receive the data from the Current Transformers (CT) and from Voltage
Transformers (VT) installed on the TMU2xx boards.
The purposes of the CT and VT include:
• To deliver current and voltage data that gives a reliable picture of what happens in the
high voltage part of an electrical substation
• To make the galvanic insulation between the high voltage part and the measurement
and protection circuits,
• To protect the measurement circuits against damage when a fault comes onto the
high voltage network.
These measurements are used for the protection function and for the Internal Synchrocheck,
Type 1 and 2
The synchrocheck device allows you to couple together 2 electrical networks.
These networks can be connected to different sources (generator), so they are not
synchronised with each other.
The Synchrocheck function measures two voltages with respect to phase angle, frequency
and magnitude to protect against the connection of two systems that are not synchronized
with each other.
In a computer, you can use the synchrocheck function for as many as 2 circuit breakers. You
can control only one circuit breaker at one time. The set of parameters defined for the
synchrocheck applies for both circuit breakers.
There are 2 types of internal synchrochecks:
− • Type 1: actual internal synchrocheck
− • Type 2: new internal synchrocheck

When 2 electrical networks are synchronized with each other:
• Voltages are identical (plus or less a dispersion)
• Frequencies are identical (plus or less a dispersion)
• Phases are identical (plus or less a dispersion)

The synchrocheck computes these measurements and accepts or not the closure of the
circuit breaker that would connect them.
The three phase voltages of the line and one phase of the bus bar are connected to the
synchrocheck.
Line
SYNCHROCHECK
SYNCHRO
L CHECK
L
L
CB B1 B2
Bus Bar 1
Bus Bar 2
C0476ENa
FIGURE 67: SYNCHROCHECK SCHEMATIC
The busbar used phase isn’t always the first one. It is defined by configuration.
In event that you have two busbars, the used phase must be the same.
7.2.2 Synchrocheck Schemes
The synchrocheck schemes include:
• DD: Dead Line, Dead Bus
• DL: Dead Line, Live Bus
• LD: Live Line, Dead Bus
• LL: Live Line, Live Bus
7.2.3 Synchrocheck Algorithm

7.2.4 Synchrocheck Applications

For synchrocheck applications, please refer to the figure that follows:
CB Check
close synchroniser
controls
Close
Generator
Network
Busbar
(a) Application to generator
CB Check
close synchroniser
controls
Close
Network
# Network
Line A CB 1 #1
Busbar B
(b) Application to two networks
C0006ENa
FIGURE 68: SYNCHROCHECK APPLICATIONS
7.2.5 Synchrocheck Circuit Breaker Closure types
There are four types of circuit breaker closure types:
• Close with synchro Close request with synchrocheck
• Manual Close Close request without synchrocheck or when the synchrocheck is out
of service.
• Automatic Close Close request from auto-recloser
• Manual override Synchrocheck override.
7.2.6 Synchrocheck Type 1 and Type 2
Two types of synchrocheck are defined:
• Type 1: based on NGC
• Type 2: specific for Terna

The differences between them are the requirements used to accept closure.
7.2.7 Synchrocheck Hardware constraints and use
Synchrocheck Synchrocheck Bus bar 2 Open/close

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

Whatever the synchronising mode ΔV, Δϕ and ΔF have to be calculated. These values are
available through the measurement module.
ΔV is calculated through the RMS value of the voltages on both bus bar and line side.
The value of ΔF is assumed to be constant across the period. As a result, knowing Δϕ

(through measurement), we know when the synchrocheck conditions are achieved (this will
easily include the reaction time of the breaker aso).
time_synchro = 2 * pi *ΔF / Δϕ
For more details, please refer to the topic Focus 3: TMU2XX: CT / VT measurement
processing as far as Threshold Detection.
7.2.9 Synchrocheck Introduction to Harmonics
The use of power electronics distorts what would ideally be a perfect sine wave. These
distortions are called harmonics. Each individual harmonic has a sine wave shape. The order
of the harmonic is defined by the frequency of the harmonic divided by basic frequency (50 /
60 Hz). The total harmonic distortion (THD) represents the sum of all voltage harmonics. The
total demand distortion (TDD) is similar to the THD but applied to currents and with a rated
current (In) as reference.
7.2.10 Synchrocheck – Check Synchronising – Locking Mode

The check synchronising mode is the default synchronising mode.
It is performed if the ΔF value is less than a user configured value (generally less than 0.1
Hz). If so, the CT-VT module computes ΔV and Δϕ. If these values are less than a user
configured threshold, the system closes the breaker. In the other hand, the CT-VT module
prevents the closure of the breaker if the system synchronising has not been activated and
one of the previous conditions is not achieved.
7.2.11 Synchrocheck – System Synchronising – Coupling Mode

System synchronizing is opposite to check synchronising. When the CT-VT module receives
a close control and if the ΔF value is under a user defined threshold, the CT-VT module goes
into the system synchronising mode.
The system synchronising should have a predictive role. This means that the CT-VT module
should calculate the time to wait before the authorisation of the closure by taking into
account the complete command line, including the mechanical characteristics of the circuit
breaker. This time should be user configured.
Note that after a user defined delay, the CT-VT module should exit the system synchronising
mode.
7.2.12 Synchrocheck: Scheme LL: Live Line, Live Bus: Real Time Sequences
For LL we have two types of synchronization:
• Locking: also referred to as check synchronising

It is defined by some requirements: frequencies difference, and so on
If they are all less than the configurable thresholds, the closure is immediately accepted.
Generally, these requirements are very restrictive: for example, Delta F < 0.1Hz
• Coupling: also referred to as system synchronizing

It is also defined by some requirements: frequencies difference, and so on
This has a predictive mode: the computer includes a time T and calculates if the coupling
conditions will be met T seconds later. This time is user configurable.
7.2.12.1 Locking allowed / coupling not allowed by configuration
Example 1
Locking Conditions
Confirmation
Time
1 2 3
T1 T2
C0478ENa
1. If a close order comes before T1, it is rejected.

2. If a close order comes between T1 and T2, it is executed at T2 if the locking
conditions are not lost. If the locking conditions are lost before T2 then the command
is rejected.
3. If a close order comes after T2, it is accepted.
7.2.12.2 Locking allowed / coupling allowed by configuration

Example 1
Locking Conditions
Confirmation
Time
1 2 3 4
T1 T2 T3 T4
C0479ENa
1. If a close order comes before T1, it is sent to the DSP board, and the control is
executed at T2 coming from DSP board.
2. If a close order comes between T1 and T2, it is buffered until T2 if the locking
conditions are not lost. If the locking conditions are lost before T2 then the command
is rejected.
3. If a close order comes after T2, it is accepted.
Example 2
2. If a close order comes between T1 and T2, it is buffered. As the locking conditions are
lost then the order is sent to the DSP and executed at T4.
3, 4. If a close order comes between T2 and T4, it is sent to the DSP board, and the control
is executed at T4 coming from DSP board.
5. If a close order comes after T4, it is sent to the DSP board, and the control is executed
immediately from DSP board.
Example 3
Anticipation Time
Coupling Conditions
Locking Conditions
Confirmation
Time
1 2 3 4 5 6
T1 T2 T3 T4 T5
2. If a close order comes between T1 and T2, it is buffered. As the locking conditions are
lost then the order is sent to the DSP and executed at T4.
3, 4. If a close order comes between T2 and T4, it is sent to the DSP board, and the control
is executed at T4 coming from DSP board.
5. If a close order comes between T4 and T5, it is sent to the DSP board, and the control
is executed immediately from DSP board.
6. If a close order comes after T5, it is sent to the DSP board, and the control is rejected
after the synchrocheck waiting time (not illustrated on the above drawing).
7.2.13 Synchrocheck Schemes that use VLINE and not(VBUSBAR) or not(Vline) and VBUSBAR
voltage controls
In event of the absence of one of the two voltages, at the end of a settable delay T2, the
authorisation to close is given:
Vline
Τ2 0
and Closing authorization
Not(Vbusbar)
C0482ENa
FIGURE 69: VLINE AND NOT(VBUSBAR) VOLTAGE CONTROL
Vbusbar
Τ2 0
and Closing authorization
Not(Vline)
FIGURE 70: NOT(VLINE) AND VBUSBAR VOLTAGE CONTROL

If, during the T2 delay time, one of the 2 criteria is lost, the timer is reinitialised and is
launched again on reappearance of all the criteria.
7.2.14 Synchrocheck Schemes that use not(Vline) and not(VBUSBAR) voltage control
In event of the absence of both voltages, at the end of a settable delay T3, the authorisation
to cllose is given:
Not(Vline)
and Τ3 0
Closing authorization
Not(Vbusbar)
C0484ENa
FIGURE 71: NOT(VLINE) AND NOT(VBUSBAR) VOLTAGE CONTROL

7.2.15 Synchrocheck Schemes that use Vline and Vbusbar voltage control
7.2.15.1.1 Locking scheme ( synchronous mode )
If these conditions are met, the authorisation to close will be given:
• Presence of both voltages AND
• The difference in amplitude (algebraic) between the two voltages (ΔV) is lower than
the configurable / settable threshold (Evect) AND
• The phase difference between the two voltages (Δϕ) is lower than the configurable /
settable threshold (Ephase) AND
• For type 1:
− The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin
and Fmax are the extreme acceptable frequencies AND
− The difference between the two frequencies (ΔF) is lower than the configurable /
settable threshold (Efreq)
• For type 2:
− The frequency shift between signals (S) is lower than the configurable / settable
threshold (Sfreq)
These conditions must be still met before the time-out of a delay T1 started on the
appearance of the conditions else the synchrocheck function will not authorise the CB
closing.
If during the delay time T1 one of these conditions is lost, T1 is reinitialised and is re-
launched on reappearance of all the conditions.
Fmin < Fline < Fmax

Fmin < Fbusbar < Fmax
Vline
Vbusbar
and T1 0 Reclosing authorization
ΔF < Efreq
Δϕ < Ephase
ΔV < Evect
FIGURE 72: LOCKING SCHEME FOR TYPE 1

Vline
Vbusbar
and T1 0 Reclosing authorization
ΔS < Sfreq
Δϕ < Ephase
ΔV < Evec t
FIGURE 73: LOCKING SCHEME FOR TYPE 2
7.2.15.1.2 Coupling scheme ( asynchronous mode )
In the coupling scheme, the CB can be closed only when the Δϕ is equal to 0.
To authorise the closing, these conditions must exist:
the configurable / settable threshold (Evect) AND
• For type 1
− The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin
and Fmax are the extreme acceptable frequencies AND
− The difference between the two frequencies (ΔF) is lower than the configurable /
settable threshold (Efreq)
• For type 2
− The shift between signals (S) is lower than the configurable / settable threshold
(Sfreq) AND
− The shift acceleration (accShift) is lower than the configurable / settable threshold
(accSfreq)
These conditions must be still met before the time-out of a delay T4 started on the
appearance of the conditions else the synchrocheck function will not authorise the CB
closing.
If during the delay time T4 one of these conditions is lost, T4 is reinitialised and is relaunched
on reappearance of all the conditions.
Fmin < Fline < Fmax

Vline T4 0
and Authorisation to check Δϕ
Vbusbar
ΔF < Efreq
ΔV < Evec t
FIGURE 74: COUPLING SCHEME FOR TYPE 1

Vline
Vbusbar
and T4 0 Authorisation to check Δϕ
ΔS < Sfreq
accShift< assSfreq
ΔV < Evec t
FIGURE 75: COUPLING SCHEME FOR TYPE 2
Since a CB has a response time, it is necessary to wait a known Δϕ to anticipate the

response time and to close the breaker with a Δϕ equal to 0.
When Δϕ = ΔF*360*Ta ± Δ(Δϕ), where Ta is the anticipation time or response time of the
circuit breaker and Δ(Δϕ) is the acceptable mistake on Δϕ, then the closing authorisation will
be sent.
7.2.16 Synchrocheck Type 1 - Logic of Interlock Authorisation
The voltage control depends on the synchrocheck type. The absolute values of the two
voltages (VLINE and VBUSBAR) must be above or below settable thresholds, to allow the
circuit breaker closing. VLINE is one of the phase voltages you define in the configuration.
The voltage controls include:
• VLINE and VBUSBAR for network coupling
• VLINE and VBUSBAR for network locking
• VLINE and not (VBUSBAR)
• Not (VLINE) and VBUSBAR
• not( VLINE) and not (VBUSBAR)

If the measured voltage is above the threshold V>, then VLINE and VBUSBAR TRUE
If the measured voltage is below the threshold V<, then not(VLINE) and not(VBUSBAR)
TRUE.
The selection of the voltage control is made during the configuration phase.
CAUTION: BE CAREFUL: FOR THE EVENT THAT FOLLOWS, THE COMPUTER
DOES NOT MANAGE THE VOLTAGE SWITCHING.
By configuration, a single synchrocheck can manage two circuit breakers.
7.2.17 Synchrocheck Type 2 - Logic of Interlock Authorisation
The voltage control depends on the synchrocheck type. The absolute values of the two
voltages (VLINE and VBUSBAR) must be above or below settable thresholds, to allow the
circuit breaker closing. If all three of the phase voltages are greater than the threshold,
VLINE is present.
The following voltage controls are available:
• VLINE and VBUSBAR for network coupling
• VLINE and VBUSBAR for network locking
• VLINE and not (VBUSBAR)
• Not (VLINE) and VBUSBAR
• not( VLINE) and not (VBUSBAR)

If the measured voltage is above the threshold V>, then VLINE and VBUSBAR TRUE
If the measured voltage is below the dropout value defined by a configurable parameter,
then not(VLINE) and not(VBUSBAR) TRUE. The configurable parameter is a percent of the
threshold V> (95% for presence condition and 105% for absent condition).
CAUTION: BE CAREFUL: FOR THE EVENT THAT FOLLOWS, THE COMPUTER DOES
NOT MANAGE THE VOLTAGE SWITCHING.
By configuration, a single synchrocheck can manage two circuit breakers.
7.2.18 Synchrocheck Bypass

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

(voltage check)
If the synchrocheck is in service, the “Conduite” process sends a Coupling Close request to
the Synchrocheck process.
If the synchrocheck is out of service, the “Conduite” process sends a Manual Close request
to the Synchrocheck process.
Synchrocheck process replies with a positive (close is possible) or negative (close is not
possible) acknowledge.
7.2.18.2 Synchrocheck Bypass - Functional Description
To help determine if you must perform a voltage check, the C264 database includes
definitions for closing schemes. For each type of control (Synchro Close, Manual Close and
Automatic Close) and for each type of voltage check (coupling, locking, bus dead line live,
bus live line dead and bus dead line dead), a yes/no flag is managed in the database.
For each type of voltage check, a new dedicated Binary Input (BI) (scheme BI) is used to
dynamically update the closing schemes in agreement with the type of control. For example,
the same Bus Live Line Dead Scheme BI is used for all the types of controls. Another
dedicated BI (bypass BI) is used to bypass the voltage check, whatever the type of control.
The added BI include:
• Coupling scheme BI
• Locking scheme BI
• Bus Live Line Dead scheme BI
• Bus Dead Line Live scheme BI
• Bus Dead Line Dead scheme BI
• Voltage check bypass BI
When the BI bypass state is SET, the Bypass BI enables the closing.
If the Flag Yes/No is set to NO for one type of voltage check, the close request is refused
(acknowledge: Synchro NOK).
The table that follows shows 1. the different voltage checks; 2. the state; 3. the close
requests; and 4. the synchrocheck aknowledge:
1. Voltage checks 2. State 3. Close Requests:
- Coupling - Synchro Close

- Locking - Manual Close
- Bus Live Line Dead - Automatic Close
- Bus Dead Line Live
- Bus Dead Line Dead
Flag Yes / BI scheme BI bypass 4. Synchrocheck
No state state Acknowledge
No Reset Reset Refused
No Reset Set Refused
No Set Reset Refused
No Set Set Refused
Yes Reset Reset Refused
Yes Reset Set Bypassed
Yes Set Reset Accepted
Yes Set Set Bypassed
Refused: Involves a negative acknowledge (Synchro NOK) sent to the “Conduite”

process.
Accepted: If the voltage conditions agree with the closing scheme, involves a positive
acknowledge sent to the “Conduite” process.
Bypassed: Involves a positive acknowledge sent to the “Conduite” process, without
checking the voltage conditions.
When the synchrocheck process sends the positive acknowledge to the “Conduite” process,
perform a new interlock check, before you close the Circuit Breaker. If the interlock condition
is True, the Circuit Breaker closes immediately, else the synchrocheck process sends a
negative acknowledge (Interlock NOK) to the control sender.
7.2.19 Phase-to-Phase Synchrocheck with the TMU210

7.2.19.1 Phase-to-Phase Synchrocheck with the TMU210 - General
With the TMU210 board with respect to the type of connection, some restrictions exist
because of the fourth VT.
Measure Type of Connection: Direct or Indirect

3Vpn 3Vpn+Vo 2Vpn+Vo 2Vpp+Vo 3Vpp+Vo 3Vpn+VB 3Vpp+VB
UA direct Direct Direct indirect indirect direct not
UB direct Direct Direct indirect indirect direct not
UC direct Direct indirect indirect indirect direct not
UAB indirect Indirect indirect direct direct Indirect Direct
UBC indirect Indirect indirect direct Direct Indirect Direct
UCA indirect Indirect indirect indirect Direct Indirect Direct
UO indirect Direct Direct Direct Direct Indirect not
UBusbar not Not Not not not Direct Direct
Protection all All all all all all Excepted

59N
dir 67N
Internal not Not not not not yes yes
SC
Table: TMU210 Type of Connection: Direct or Indirect

In event of loss of (3vnb+Vb) or (3Vpp+Vb), then the tracking frequency defaults to the
Ubusbar.
The TMU210 type-of-connection parameters do not have as many possibilities as the
TMU220 electrical-network-topology parameters. To be compatible, it is helpful to map the
TMU210 type-of-connection parameters into the TMU220 electrical-network topology
parameters:
TMU210 TMU220
Type-of-connection Electrical-network-topology
parameters parameters
3Vpn 3Vpn ( star )

3Vpn + Vo 3Vpn + Vo ( star )
2Vpn + Vo 2Vpn +Vo ( partial star )
2Vpp+ Vo 2Vpp + Vo ( delta partial )
3Vpp + Vo 3Vpp + Vo ( delta )
3Vpn + Vb 3Vpn + Vb ( star )
3Vpp + Vb 3Vpp + Vb ( delta )
CAUTION: THE VT WIRING SCHEME MUST BE IDENTICAL BETWEEN LINE AND

BUSBAR: DELTA: DELTA OR STAR: STAR. IN A DELTA X STAR WIRING
SCEME, THERE IS NO PARAMETER TO TAKE INTO ACCOUNT THE
PHASE DIFFERENCE AND AMPLITUDE DIFFERENCE.
Make sure that the VT wiring scheme is identical between line and busbar: Delta: Delta or
Star: Star.
7.2.19.2 Phase-to-Phase Synchrocheck with the TMU210 - Description
Phase-to-phase synchrocheck allows you to configure a synchrocheck function with a delta
wiring. Do this configuration at the TMU210 level and use the attributes "type of connection"
and "reference phase".
For the phase-to-phase synchrocheck, set the “Type of connection” to 3 Vpp + Vb (delta).
Compare the busbar voltage to the phase-phase voltage defined as the reference in the
configuration. The reference phase-phase that you choose must match the phase-phase of
the busbar that is wired on the TMU210.
For example: If the reference phase-phase is configured as Vab then the phase-phase
voltage Vab busbar must be wired on TMU210.
NOTE: There is no check possible at the C264 or SCE level. The operator is
responsible to make sure that the configuration agrees with the wiring.
In this configuration, the calculation of voltage, angle and frequency are the same as for
phase neutral.
Phase-to-Neutral synchro-check (SC PN) and Phase-to-phase synchrocheck (SC PP)
configurations show in the table that follows.
SC PN SC PP
Mounting (wiring) Star Delta
Type of connection 3Vpn + Vb (star) 3Vpp + Vb (delta)
Reference phase Va, Vb, Vc Vab, Vbc, Vca
When wiring is between Phase and Neutral, Vb is “Vbpn”

When wiring is between Phases, Vb is “Vbpp”.
7.2.19.3 Phase-to-Phase Synchrocheck with the TMU210 - Configuration

For the Phase to phase synchro-check:
Only Vab, Vbc, Vca are available as “Reference phase”.
For the Phase to Neutral synchro-check:
Only Phase A, Phase B, Phase C are available as “Reference phase”.
7.2.20 Synchrocheck Close request
On close request, the schemes are tested and the close order is sent with the answer:
• OK: close is possible
• KO: close is impossible

When the LL scheme is valid and to allow the breaker to close, you must do a check of the
synchronization conditions between the 2 voltages.
The locking mode is the default synchronising mode. If the requirements are valid, at least
during a delay T1, the closure is made immediately. Otherwise the coupling mode is tried.
The different coupling modes are defined in agreement with the type of synchrocheck.
Define the authorized schemes that follow during the configuration phase. The synchrocheck
function operates for these schemes:
Operator Operator Auto-recloser

manual closure Synchrocheck
closure
Network locking on both voltages X X X
presence and test of deltas
Automatic and manual network locking
on live line / live bar
Network coupling on both voltages X
presence and test of deltas
Automatic and manual network
coupling on live line / live bar
Presence of only the line voltage X X X
connection on live line / dead bar
Presence of only the busbar voltage X X X
connection on dead line / live bar
Absence of both voltages X X X
connection on dead line / dead bar
7.2.21 Synchrocheck General Configuration
The general configuration includes:
• Network frequency
• VT connection: delta or triangle
• Reference phase: A, B or C
• Reference phase side: line or busbar
• Nominal voltage
7.2.22 Synchrocheck Voltage control
This function computes the BI’s presence/absence voltage of the line and the busbar.
In agreement with the configuration:
• The line can be the reference or the other voltage
• The busbar can be the reference or the other voltage.

Four thresholds are defined:
• Line voltage over: percent of the nominal voltage
• Line voltage under: percent of the nominal voltage
• Bus bar voltage over: percent of the nominal voltage
• Bus bar voltage under: percent of the nominal voltage

Two timers are defined:
• Absence delta test ( T3 ) time to confirm the absence signals
• Presence test ( T2), time to confirm the presence signals
7.2.23 Synchrocheck Schemes control
By configuration, each event that follows is allowed or not:
LL- coupling LL- locking DL LD DD

Close with YES or NO YES or NO YES or NO YES or NO YES or NO
synchro
Manual Close NOT YES or NO YES or NO YES or NO YES or NO
POSSIBLE
Automatic Close NOT YES or NO YES or NO YES or NO YES or NO
request from POSSIBLE
auto-recloser
In event of manual override, the close request is allowed and there is no check.
When coupling is configured, locking is mandatory.
In coupling conditions, a manual or automatic close is always refused: LL and locking
conditions not met.
7.2.24 Synchrocheck Parameters of the TMU2xx board
The parameters for the TMU220 are the same as for the TMU210:
• Reference phase: definition of the voltage reference phase for comparison
• Reference phase side: definition of the energised reference voltage

7.2.25 Synchrocheck Internal parameters
Parameter Label Range of value Type

General
Synchrocheck kind SC type 1 or 2 1 and 2
Voltage control
Delay of one voltage presence T2 From 200ms to 10s, 20ms 1 and 2
control step
Delay of voltage absence control T3 From 200ms to 10s, 20ms 1 and 2
step
Line voltage over threshold V> line 0 to 100%, 1% step (% of the 1 and 2
nominal voltage value)
Line voltage under threshold V< line 0 to 100%, 1% step (% of the 1 and defined by the
nominal voltage value) fixed dropout percent
for type 2
Busbar voltage over threshold V> busbar 0 to 100%, 1% step (% of the 1 and 2
Busbar voltage under threshold V< busbar 0 to 100%, 1% step (% of the 1 and defined by the
nominal voltage value) fixed dropout percent
for type 2
Locking scheme
Delay of both voltages presence T1 200ms to 10s, 20ms step 1 and 2
control
Voltage delta threshold Evect_locking 0 to 100%, 1% step (% of the 1 and 2
Minimum frequency Fmin_locking 45 to 59,5 Hz, 0,1 Hz step 1
Maximum frequency Fmax_locking 50,5 to 66 Hz, 0,1 Hz step 1
Frequency delta threshold Efreq_locking 0 to 1 Hz, 0,01 Hz step 1
Phase delta threshold Ephase 0 to 90°, 1° step 1 and 2
Shift frequency threshold Sfreq_locking 0.02÷0.1 % step 0,01 % 2
Coupling scheme
Delay of both voltages presence T4 200ms to 10s, 20ms step 1 and 2
control
(for SCE’s upgrade, use T1 )
Delay of both voltages presence T1 (for locking and 200ms to 10s, 20ms step 1 and 2
control coupling)
Circuit breaker response time for Ta 0 to 1s, 10ms step 1 and 2
coupling scheme
Voltage delta threshold Evect_coupling 0 to 100%, 1% step (% of the 1 and 2

Minimum frequency Fmin_coupling 45 to 59,5 Hz, 0,1 Hz step 1
Maximum frequency Fmax_coupling 50,5 to 66 Hz, 0,1 Hz step 1
Frequency delta threshold Efreq_coupling 0 to 1 Hz, 0,01 Hz step 1
Phase delta threshold Ephase 0 to 90°, 1° step 1
Shift frequency threshold Sfreq_coupling 0.1÷1 % step 0,1% 2
Acceleration Shift frequency accSfreq_coupling = Ks (Tk-Ta) where Not required to define
threshold this threshold
Ks = 1% fixed
Tk = 0.5s
Ta: see above
The fixed hysteresis values follow:
• 5% on voltages thresholds
• 2% on voltage delta threshold for locking and coupling
• 0,014 Hz on frequency delta threshold for locking
• 0,028 Hz on frequency delta threshold for coupling
• 0,01 Hz on frequencies thresholds
• 1° on phase delta threshold for locking.

7.2.26 Synchrocheck Digital Output (DO) of the circuit breaker
The DPC of the circuit breaker can be configured on the DSPIO or on a DOU board.
On DSPIO, the DPC close relay is mandatory connected to the contact 1 or contact 2 of
relay 3 (pinout 9/10 or 11/12).
In this event there are only 2 choices for the DPC type:
• Transient
• Permanent until feedback

If you use a DOU, both contacts must be connected on it with same previous constraint.
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.4.3 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.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 76: 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 (see logical interlocking for 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 & 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.
I1
& DO1
setting
I2
& DO2
setting
≥1 t
&
BI1
≥1
setting
≥1
I3
≥1
I4
C0140ENa
FIGURE 77: EXAMPLE OF PSL

7.6 Fast Load Shedding ( FLS )

The Fast Load Shedding (FLS) automation function description and implementation is part of
the Application Chapter (AP). For more data, please refer to C264_ENAP.
NOTE: FLS requires a dedicated FLS architecture. For more details, please
consult us.
7.6.1 C264M
The C264M supports:
• The ISAGRAF automation that allows you to define the FLS preselections
• Automations (ISAGRAF and/or PSL) that allow you to test or simulate the FLS.
7.6.2 C264Fi
As many as 48 C264Fi (feeder) computers support the FLS Function. You can create as
many as 300 output breaker commands.
7.7 Load Shedding – C264 Standalone
List1 List2 List3 List4

f1< control f2< control f3< control f4< control
LS On/Off Status
LS On/Off control
LS Group x status
Blocking condition x GROUP 1 GROUP 2 GROUP 3 GROUP 4 LS CB x rejected by
setting blocking condition
blocking condition LS CB x completed
information LS CB x failed
CBx status List x Status
Inter-group delay Blocking condition
x status
CBx control LOAD SHEDDING CBx open control
time-out
C0293ENa
Database (.adb)
NOTE: The Load Shedding function is available only on the C264 Standalone.
7.7.1 Inputs
• f1<, f2<, f3<, f4<: digital inputs, coming from frequency relay. Each input is a
frequency threshold and is associated to a group.
• List1, List2, List3, List4 control: each “list” input is a set of three setpoints associated
to a group. These setpoints give the list of Circuit Breaker attached to a group. They
can be only received from the SCADA interface. ASDU 48 (setpoint normalised value)
is used for these setpoints.
• LS On/Off Control: control (DPC type) that allows you to set On or Off the Load
Shedding automation. This control can be received from the SCADA interface or from
the C264 local HMI.
• Blocking condition x setting (1≤x≤6): each blocking condition setting is a set of three
setpoints. These setpoints give the list of Circuit Breaker blocked by the condition x. It
can be only received from the SCADA interface. ASDU 48 (setpoint normalised value)
is used for these setpoints.
• Blocking condition data: digital inputs that blocks the CB trip is set, according to the
CBx blocking condition setting. A maximum of 6 SPS / DPS can be defined as
blocking condition information.
• CBx status: status of each circuit breaker (Feedback of the CBx control).
• Inter-group delay: delay between each group when several group are activated: that
is, when CB of a group have to be tripped. This delay is defined in configuration and
settable through a setpoint (ASDU 48) that can be only received from the SCADA
interface. The delay is stored in flash memory, but set to the value defined in
configuration in event of database switch.
• CBx control time-out: one time-out per circuit breaker. For a circuit breaker, this time-
out defines the authorized delay between the CB control activation and the CB
position change. These time-out are defined in configuration – thru PACiS SCE – as
the CB control’s Feedback time-out.
• Database: C264 database (.adb file).

7.7.2 Algorithm
Group definition
At configuration time (with PACiS SCE), the operator defines the list of CB attached to each
Load Shedding group. The minimum number of CB in a group is 0, the maximum number is
40. No more than 40 CB can be defined for the whole automation. The 40 CB that you can
use in the load shedding function are tagged in configuration with a number from 1 to 40.
When the database is downloaded and switched, the load shedding automation considers
the data described in the database (last setting sent by the SCADA is lost). The Listx status
information is updated and sent to the SCADA.
The assignment of CB to the groups is performed on-line through the SCADA interface,
whatever was the status of the automation (On or Off). Three setpoints are defined per
group, each value combination gives the allocation of a CB to the group as defined in the
table below:
Breaker Number / / 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
setpoint 1
Breaker Number / / 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
setpoint 2
Breaker Number / / / / / / / 40 39 38 37 36 35 34 33 32 31
setpoint 3
Bit 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Value 16384 8192 4096 2048 1024 512 256 128 64 32 16 8 4 2 1
If a CB is already assigned to an other group, it is automatically re-assigned to the new

group (a CB can be affected to only one group). After assignment, the Listx status
information for group(s) that has(have) been modified is sent to the SCADA.
During CB assignment (from the reception of the Listx control up to the sending of the Listx
status), the load shedding function cannot be started.
The group definition is saved in flash memory and restored after a computer reboot. It is
erased in event of database switch.
Locally to the computer, assignments of CB to a group can be performed only through a
database download.
Blocking conditions
You can define as many as 6 SPS / DPS as blocking condition: they are numbered from 1 to 6.
At configuration time (with PACiS SCE), the operator defines the list of blocking conditions
activated for each Circuit Breaker.
When the database is downloaded and switched, the load shedding automation takes into
account information described in the database (last setting sent by the SCADA is lost).
The use of blocking condition is also performed through the SCADA interface, whatever was
the status of the automation (On or Off). Three setpoints are defined on a per blocking
condition basis; each value combination gives the association between the CB and the
blocking condition (refer to the table of group definition).
The usage of blocking conditions is saved in flash memory and restored after a computer
reboot. It is erased in event of database switch.
After assignment, the Blocking condition x status information for blocking condition(s) that
has(have) been modified is sent to the SCADA.
Automation
The automation is activated only if it is On. The On / Off control (DPC) is performed through
the SCADA interface or the computer local HMI. The automation status is provided through a
DPS.
As soon as a fx< SPS is detected in a SET state, the CB belonging to the group x are
tripped, with the following constraints:
• The order to trip the first CB will be sent in less than 100ms after the fx< detection
whatever was the number of CB in the group
• If the group contains as many as 20 CB, the order to trip the 20th CB will be sent in
less than 500 ms after the fx< detection
• If the group contains as many as 40 CB, the order to trip the 20th CB will be sent in
less than 500 ms after the fx< detection and the order to trip the last CB will be sent in
less than 1 second after the fx< detection
• A blocking condition on a CB prevents its trip
• No other information than the blocking condition can prevent the CB trip, such as
interlocking, control uniqueness, bad CB state (already open, jammed, and so on….)
NOTE: Time constraints are given from fx< transition detection to Digital
Output closure.
Any invalid state of the fx< SPS (Selfcheck faulty, toggling) will be not taken into account to
trig the automation.
In event of simultaneous fx< detection: that is, multiple fx< detection with the same time tag,
the groups will be activated in the order of trigger detection:
• If the « inter-group delay » is null, the time constraints given above will be respected
for each group ;
• If the « inter-group delay » is not null, all CB of one group will be tripped before
beginning to trip all CB of the following group.
In event of multiple fx< detection: that is, fx detection during activation of an other group, the
groups will be activated in the order of trigger detection. So, all CB of the first group will be
tripped before beginning to trip all CB of the following group.
7.7.3 Outputs
• LS On/Off Status (DPS type): status of the Load Shedding automation

• LS Group x status (SPS permanent type, 1≤x≤4): set as soon as a group is activated:
that is, the fx< input is set and automation status is On. Reset when the last CB
control has been performed, whatever was the control result
• LS CB x rejected for blocking condition (SPS transient type, 1≤x≤40): one information
on a per circuit breaker basis. Set during 100 ms if the control is refused due to a
blocking condition
• LS CB x completed (SPS transient type, 1≤x≤40): one information on a per circuit
breaker basis. Set during 100 ms if the control has been correctly performed: that is,
the breaker opened before the end of the control time-out.
• LS CB x failed (SPS transient type, 1≤x≤40): one information on a per circuit breaker
basis. Set during 100 ms if the CB is not opened at the end of the control time-out
• Listx Status (1≤x≤4): status of the assignment of CB to a group, transmitted to the
SCADA through an analogue value (ASDU 09 or 10)
• Blocking condition x Status (1≤x≤6): list of CBs for which the blocking condition is set,
transmitted to the SCADA through an analogue value (ASDU 09 or 10)
• CBx open control: control for CB trip
7.7.4 Hypothesis and Constraints
• Only one frequency relay provides frequency thresholds to the C264

• The Load Shedding automation can manage as many as 40 Circuit Breakers
• All DOU or CCU boards used for CB controls must be in the same rack
• All configurable information used for Load Shedding function are configured using the
PACiS SCE
• There is no way to visualise / modify the settings from the computer local HMI or from
the CAT
• Functioning in event of main 1 rack redundancy
− Load Shedding must operate in event of main 1 rack redundancy.
− LS function can be set On or Off from the SCADA interface. The SCADA sends
this order to only one main 1 rack. The order must be automatically transmitted to
other main 1 racks.
− All settings defined on a main 1 rack are also automatically transmitted to other
main 1 racks.
[settings = Inter-group delay; List of Circuit Breaker attached to each group; List of
Circuit Breaker blocked by each blocking condition]
− In event of a group activation (fx< goes in Set state), the LS automation operates
in parallel on all front-end main racks.
• Management of the LS On/Off state
− The LS On/Off state is saved in non volatile memory. This data is erased only
when the computer boots with a DB without LS (so, this information is kept on DB
switch).
− After a computer reboot, if a “saved LS On/Off state” is found the LS function is
set in this saved state, otherwise the LS is set in On state (default state).
• Management of Settings
− LS setting are saved in non volatile memory. These information are erased on DB
switch.
− After a computer reboot, if “saved LS settings” are found these settings are used,
otherwise settings given by the DB are used.
7.7.5 Configurable data
Attribute Default Range Provided Comments

Value through
S9R file
Load Shedding Automation
Inter-group delay 100 milli- from 0 to Yes with a 100 ms step
second 9999ms
Circuit Breaker
Group assignment 0 [0..4] Yes 0 = no assignment to a group
Breaker number 0 [0..40] Yes 0 = not used in Load
Shedding automation
control time-out 600 ms [0..6000000] Yes Given by the feedback timeout
on the CB control.
Blocking condition n° 1 No Yes / No Yes No = the blocking condition is
not used for the breaker
Blocking condition n° 2 No Yes / No Yes
SPS / DPS datapoint
Blocking condition 0 [0..6] Yes 0 = the SPS / DPS is not used
number as a blocking condition
Blocking state On On / Off Yes Indicates if the blocking
condition is active with the ON
or OFF state.
Furthermore, all datapoints described above are configured using the PACiS SCE and must
be provided by the S9R file.
7.8 Load Curtailment – C264 Standalone
List1 List2 List3 List4

control control control control
G1 G2 G3 G4
activation activation activation activation
LC On/Off Status
LC On/Off control
LC Group x status
Blocking condition x GROUP 1 GROUP 2 GROUP 3 GROUP 4 LC CB x rejected by
setting blocking condition
blocking condition LC CB x completed
information LC CB x failed
List x Status
CBx status
Blocking condition
x status
CBx control LOAD CURTAILMENT CBx open control
time-out
C0294ENa
Database (.adb)
7.8.1 Inputs
• List1, List2, List3, List4 control: each “list” input is a set of two setpoints associated to
a group. These setpoints give the list of Circuit Breaker attached to a group. They can
be only received from the SCADA interface. ASDU 48 (setpoint normalised value) is
used for these setpoints.
• Gx activation: SPC, for each group, that allows you to activate the Load Curtailment
function for the Group x when a SET control is received (the RESET control has no
effect).
• LC On/Off Control: control (DPC type) that allows you to set On or Off the Load
Curtailment automation. This control can be received from the SCADA interface or
from the C264 local HMI.
• Blocking condition x setting (1≤x≤6): each blocking condition setting is a set of 2

setpoints. These setpoints gives the list of circuit breakers blocked by the condition x.
It can be only received from the SCADA interface. ASDU 48 (setpoint normalised
value) is used for these setpoints.
• Blocking condition information: digital inputs that block the CB trip is set, according to
the CBx blocking condition setting. A maximum of 6 SPS / DPS can be defined as
blocking condition information.
• CBx status: status of each circuit breaker (Feedback of the CBx control).
• CBx control time-out: one time-out per circuit breaker. For a circuit breaker, this time-
out defines the authorized delay between the CB control activation and the CB
position change. These time-outs are defined in configuration – thru PACiS SCE – as
the CB control’s Feedback time-out.
• Database: C264 database (.adb file), refer to § 6.2.4.

7.8.2 Algorithm
Group definition
At configuration time (with PACiS SCE), the operator defines the list of CB attached to each
Load Curtailment group. The minimum number of CB in a group is 0, the maximum number
is 5. No more than 20 CB can be defined for the whole automation. The 20 CB that can be
used in load curtailment function are tagged in configuration with a number from 1 to 20.
When the database is downloaded and switched, the load curtailment automation takes into
account information described in the database (last setting sent by the SCADA is lost). The
Listx status information is updated and sent to the SCADA.
The assignment of CB to the groups is performed on-line through the SCADA interface,
whatever was the status of the automation (On or Off). Two setpoints are defined per group,
each value combination gives the allocation of a CB to the group as defined in the table
below:
Breaker Number / / 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
setpoint 1
Breaker Number / / / / / / / / / / / / 20 19 18 17 16
setpoint 2
Bit 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Value 16384 8192 4096 2048 1024 512 256 128 64 32 16 8 4 2 1
If a CB is already assigned to another group, it is automatically re-assigned to the new group

(a CB can be affected to only one group). After assignment, the Listx status information for
group(s) that has(have) been modified is sent to the SCADA.
During CB assignment (from the reception of the Listx control up to the sending of the Listx
status), the load curtailment function cannot be started.
The group definition is saved in flash memory and restored after a computer reboot. It is
erased in event of database switch.
Locally to the computer, assignments of CB to a group can be performed only through a
database download.
Blocking conditions
You can define as many as 6 SPS / DPS as blocking condition: they are numbered from 1 to 6.
At configuration time (with PACiS SCE), the operator defines the list of blocking conditions
activated for each Circuit Breaker.
When the database is downloaded and switched, the load shedding automation takes into
account information described in the database (last setting sent by the SCADA is lost).
The use of blocking condition is performed through the SCADA interface, whatever was the
status of the automation (On or Off). Two setpoints are defined on a per blocking condition
basis; each value combination gives the association between the CB and the blocking
condition (refer to the table of group definition).
The usage of blocking conditions is saved in flash memory and restored after a computer
reboot. It is erased in event of database switch.
After assignment, the Blocking condition x status information for blocking condition(s) that
has (have) been modified is sent to the SCADA.
Automation
The automation is activated only if it is On. The On / Off control (DPC) is performed through
the SCADA interface or the computer local HMI. The automation status is provided through a
DPS.
When the SET control is received through the Gx Activation SPC: that is, reception by the
computer of the order, all the CB belonging to the group x must be tripped in less than 300
ms.
NOTES: - A blocking condition on a CB prevents its trip
- No other information than the blocking condition can prevent the CB
trip [ interlocking, control uniqueness, bad CB state (already open,
jammed, …), ….]
In event of multiple reception of Gx Activation controls, the groups will be activated in the
order of control reception. So the CB of one group will be tripped before beginning to trip the
CB of an other group. In this event, the time to trip the CB of the other(s) group(s) can be
more then 300ms.
7.8.3 Outputs
• LC On/Off Status (DPS type): status of the Load Curtailment automation
• LC Group x status (SPS permanent type, 1≤x≤4): set as soon as a group is activated:
that is, one Gx Activation control received and automation status is On. Reset when
the last CB control has been performed, whatever was the control result
• LC CB x rejected for blocking condition (SPS transient type, 1≤x≤20): one information
on a per circuit breaker basis. Set during 100 ms if the control is refused due to a
blocking condition
• LC CB x completed (SPS transient type, 1≤x≤20): one information on a per circuit

breaker basis. Set during 100 ms if the control has been correctly performed: that is,
the breaker opened before the end of the control time-out.
• LC CB x failed (SPS transient type, 1≤x≤20): one information on a per circuit breaker
basis. Set during 100 ms if the CB is not opened at the end of the control time-out
• Listx Status (1≤x≤4): status of the assignment of CB to a group, transmitted to the

SCADA through an analogue value (ASDU 09 or 10)
• Blocking condition x Status (1≤x≤6): list of CBs for which the blocking condition is set,
transmitted to the SCADA through an analogue value (ASDU 09 or 10)
• CBx open control: control for CB trip

7.8.4 Hypothesis and Constraints
• The Load Curtailment automation can manage as many as 20 Circuit Breakers
• All DOU or CCU board used for CB controls must be in the same rack
• All configurable information used for Load Curtailment function are configured using
the PACiS SCE
• There is no mean of visualisation/modification of settings from the computer local HMI

or from the CAT
• Functioning in event of main 1 rack redundancy is identical to LS except for group

activation: as the ‘Gi activation’ is received from SCADA interface, the LC automation
operates only on the Front-end main rack that received this activation.
• Management of the LC On/Off state: identical to LS
• Management of Settings: identical to LS

7.8.5 Configurable data
Attribute Default Range Provided Comments

Value through
S9R file
Circuit Breaker
Group assignment 0 [0..4] Yes 0 = no assignment to a group
Breaker number 0 [0..20] Yes 0 = not used in Load
Curtailment automation
control time-out 600 ms [0..6000000] Yes Given by the feedback timeout
on the CB control.
Blocking condition n° 1 No Yes / No Yes No = the blocking condition is
not used for the breaker
SPS / DPS datapoint
Blocking condition 0 [0..6] Yes 0 = the SPS / DPS is not used
number as a blocking condition
Blocking state On On / Off Yes Indicates if the blocking
condition is active with the ON
or OFF state.
Furthermore, all datapoints described above are configured using the PACiS SCE and must
be provided by the S9R file.
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 Waveform 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:
• Fast Waveform recording that gives access to samples. This record is useful for
transient electrical events.
• Slow scan triggered recording (SST) referred to as Slow Waveform recording that
gives access to RMS values. This record is useful to define load profile or power
regulation.
9.1.3 Events
All data change or events declared in the C264 configuration database “To be logged” are
stored in a circular queue.
The event records are available for viewing either via the front panel LCD, via slave protocol
at SCADA level or on CAT equipment. They also can be printed.
Events, following the C264 configuration, may typically contain the 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 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 of the queue is:
• 200 data for front panel
• 2000 data for CAT
• configurable for each slave protocol for SCADA.

9.1.4 Fast Waveform Recording

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

The hypothesis for slow waveform recording follows:
1) Digital inputs will be not recorded if the integration delay is superior to 100 ms
2) A digital input is recorded to “1” if it remains at “1” during x% of the integration delay (x
between 10 and 90%, with a 1% step)
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.7 Disturbance Recorder

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

trigger
post time of the second trigger
pre
time
One Disturbance buffer
If a second trigger appears after the post time of the first trigger, a second record is
generated.
1° trigger 2° trigger
pre post time

time
post time
pre
time
post time
pre
1° disturbance time
buffer
2° disturbance
buffer
C0491ENa
If a third trigger appears, it is ignored if the previous buffer are not downloaded by the PPC.
9.2 Non-permanent data storage

9.2.1 Alarms
9.2.1.1 Definitions
9.2.1.1.1 Definition of an alarm
An alarm is a visual (and optionally audible) annunciation of the appearance and/or
disappearance, within the controlled electrical process or within the system itself, of an
event, defined during the configuration phase as ”to be alarmed”.
These definitions, of what is to be alarmed and what it is not, are completely user relevant.
However the concept of alarms into PACiS has been introduced to inform the operators of
“abnormal” or “special” events or other miscellaneous events that you must absolutely not
overlook.
9.2.1.1.2 Types of alarmed data
These events can generate an alarm:
• Each Binary Input (SP, DP, MP, SI, IED input, Groups) state related to “the reason for
change” of these events
• Each Measurement state related to “the reason for change” of these events
• 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”.
9.2.1.1.3 Alarm states definition
An alarm is generated by an event: for example, a particular datapoint in a state defined
during the configuration phase as “to be alarmed”.
While this event is still present: for example, the previous particular datapoint is still in the
same state, the alarm is “active”.
When this event disappears: for example, the previous particular datapoint is now in another
not alarmed state; the previous alarm is “inactive”.
An existing alarm (active or inactive), can be acknowledged by an operator from the FP.
An alarm can have the following states:
• Inactive: no transition, no event
• Active-acknowledged: the cause is still present but the active state has been taken
into account by the operator
• Active-unacknowledged: the cause is still present and the active state has not been
taken into account by the operator
• Inactive-unacknowledged: the cause has disappeared but the inactive state has not
been taken into account by the operator (only available for events alarmed on
appearance and disappearance)
• Inactive-acknowledged: the cause has disappeared and the inactive state has been
taken into account by the operator
• Inactive-active-unacknowledged: the cause has disappeared but the active state

(previous state) has not been taken into account by the operator
9.2.1.1.4 Parameters associated to an alarm

The following user-selectable parameters can be associated with each alarm definition. The
values are set during the configuration phase for each alarm:
• Immediate or 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.
9.2.1.2 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 78: 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 79: 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 state that is not alarmed. The time
stamp of the alarm is modified.
Transition conditions:
• (auto) means Automatic clearing

Transition description:
The transition from alarm state "0" to alarm state "1" is crossed when the alarmed event
appears (AL+).
The alarm state transitions "1 → 1" and "2 → 1" are crossed when the state of the data
associated with the alarm goes from a state that is flagged to be alarmed with any gravity
level to another state that is also flagged to be alarmed with any gravity level (AL+). In this
event the active alarm 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.
9.2.1.2.1 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 an 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.
9.2.1.2.2 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.
BLANK PAGE
MiCOM C264/C264C
HARDWARE
CONTENTS
2. HARDWARE DESCRIPTION 4
2.1 Components 4
2.1.1 Hardware Overview 5
2.2 Rack styles 6
2.2.1 MiCOM C264C 6
2.2.2 MiCOM C264 11
2.3 Coding of board address 15
2.4 Modules description 16
2.4.1 Power auxiliary supply and legacy ports board – BIU241 16
2.4.2 Dual source power supply board – BIU261 18
2.4.3 Central Processing Unit and base communications board – CPU260 21
2.4.4 Central Processing Unit and base communications board – CPU270 22
2.4.5 DSPIO board 23
2.4.6 Circuit breaker Control Unit - CCU200 24
2.4.7 Circuit breaker Control Unit - CCU211 25
2.4.8 Digital Inputs Unit – DIU200 27
2.4.9 Digital Inputs Unit – DIU211 28
2.4.10 Digital Outputs Unit – DOU201 30
2.4.11 Analogue Input Unit – AIU201 31
2.4.12 Analogue Input Unit – AIU211 32
2.4.13 Transducerless Measurements Unit – TMU220 33
2.4.14 Transducerless Measurements Unit – TMU210 34
2.4.15 Analogue Output Unit – AOU200 35
2.4.16 Ethernet Switch Unit – SWU200/SWU202 36
2.4.17 Ethernet Switch Unit – SWx202/SWx212, SWx204/SWx214 (x=R for dual Ring,
x= D for Dual homing) 38
2.4.18 Extended communication Unit – ECU200 42
2.4.19 Extended communication Unit – ECU210 43
C264/EN HW/D10 Hardware
BLANK PAGE

product hardware, which is not described in the Commissioning chapter.
2. HARDWARE DESCRIPTION
2.1 Components
The MiCOM C264/C264C is based on a modular and scalable architecture to support
dedicated hardware modules adapted to the plant data interfaces.
Each MiCOM C264/C264C rack can be equipped with the following modules:
• BIU241: Basic Interface Unit. This board includes the auxiliary power supply
converter, the watchdog relay, 2 digital outputs/2 digital inputs for C264 redundancy
and 2 isolated RS485/RS232 interfaces
• BIU 261: Basic Interface Unit. This board includes the dual source power supply for
C264 power supply redundancy, the watchdog relay, 2 digital outputs/2 digital inputs
for C264 redundancy and 1 isolated RS232/RS422RS485 interfaces
• CPU260 (also named CPU2) or CPU270 (also named CPU3): Central Processing
Unit and communications board based on PowerPC processor
• FBP28x: Front BackPlane: bus for 80TE case
• FPB26x: Front BackPlane: bus for 60TE case
• FBP24x: Front BackPlane: bus for 40TE case
• CCU200: Circuit breaker Control Unit each with 8 digital inputs and 4 digital outputs
• CCU211: Circuit breaker Control Unit each with 8 digital inputs and 4 digital outputs
(versions are jumper-selected)
• DIU200: Digital Inputs Unit each with 16 digital inputs
• DIU211: Digital Inputs Unit each with 16 digital inputs for voltages from 24 to 220Vdc
(versions are jumper-selected)
• DOU201: Digital Outputs Unit each with 10 digital outputs
• AIU201: Analogue Input Unit each with 4 analogue inputs direct current or voltage
• AIU211: Analogue Input Unit each with 8 analogue inputs direct current
• TMU2xx: Transducerless Measurements Unit board for direct CT/VT measurement
used together with DSPxxx: Digital Signal Processing board.
• AOU200: Analogue Output Unit each with 4 current analogue outputs
• SWU20x: Ethernet SWitch Unit board with 4 electrical links and x= 0 or x=2 optical links
• SWR2xx: Ethernet SWitch board for Redundant Ethernet ring with 4 electrical links
and 2 optical links for the Dual ring.
• SWD2xx: Ethernet SWitch board for Dual Homing Ethernet star, with 4 electrical links
and 2 optical links for a Dual star.
• ECU200: Extended Communication Unit board to convert non isolated RS232 into
optical signal
• ECU201: Extended Communication Unit board to convert non isolated RS232 into
isolated RS485 signal
• GHU201 (for C264) or GHU200 (for C264C): Graphical Human machine interface
Unit: Front Panel including 17 LEDs (13 are user-configurable) + 7 pushbuttons (L/R,
Open, Close, etc) + LCD (resolution of 128 x 128 pixels /16 lines of 21 characters
each) and a keypad at the front plate for local HMI management
• GHU211 (for C264) or GHU210 (for C264C): Front Panel including 17 LEDs (12 are
user-configurable) + 1 pushbutton (L/R)
• GHU221 (for C264) or GHU220 (for C264C): Front Face used to connect a
detachable HMI (GHU20x or GHU21x)
2.1.1 Hardware Overview
Watchdog
FBP28x BIU 241/261
or FBP24x (1) Redundancy RS 232 /RS 485 /RS 422
COM 1 / COM 2 Dual source power

RS 232 /RS 485
Power Supply supply (BIU261)
Electrical link (CPU270)
Ethernet
CPU 260/270 Optical link (CPU260) or Electrical link (CPU270)
(1)
COM 1 / COM 2
RS 232 ECU20x RS 485
DSP200 for RS 422
CPU260 IRIG -B RS 232 ECU20x Optical
GHU200/201
OR
GHU210/211
OR
GHU220/221 GHU20X/21X
SWU20x Optical 1 / Optical 2

(up to 1)
Electrical 1 to 4
SWR 2xx/SWD2xx Optical 1 / Optical 2

(up to 1) Mandatory standalone C264 does
Optional not include SWD2xx
Electrical 1 to 4 nor TMU2xx and DSP
AIU2x1
(up to 6) 4 digital inputs (AIU201)
8 digital inputs (AIU211)
DOU201
(up to 15) 10 digital outputs
CCU 200/211
(up to 15) 8 digital intputs
4 digital outputs
DIU200 /DIU21X
(up to 15) 16 digital inputs
AOU 200
4 analogue outputs
(up to 4)
4 current intputs C0117ENi

TMU2xx
4/5 voltage inputs
(up to 1)
FIGURE 1: HARDWARE OVERVIEW

2.2 Rack styles

The mechanical rack is 4 U high.
Two styles are available:
• MiCOM C264C (Compact), that is 40 TE-wide
• MiCOM C264, that is 80 TE-wide

2.2.1 MiCOM C264C
2.2.1.1 Overview
Dimensions of this rack are in the figure below:
FIGURE 2: MiCOM C264C – RACK SIZE

Case properties:
• Case degree of protection: IP52 in standard
• Front Panel degree of protection: IP52
• Metallic case
C264C fixation holes position:
FIGURE 3: FIXATION HOLES POSITION FOR C264C

2.2.1.2 Front Panels
2.2.1.2.1 GHU200
The GHU200 is the front panel with LCD and LEDs used for the MiCOM C264C:
• 17 LEDs (13 are user-configurable)
• 7 pushbuttons (L/R, Open, Close, etc)
• a keypad at the front plate for local HMI management with 5 pushbuttons
• an LCD (resolution of 128 x 128 pixels /16 lines of 21 characters each)
FIGURE 4: MiCOM C264C – GHU200 BOARD

2.2.1.2.2 GHU210
The GHU210 is the front panel with LEDs used for the MiCOM C264C:
• 1 pushbutton (L/R)

2.2.1.2.3 GHU220
The GHU220 is the front panel used for the MiCOM C264C. This includes only an RJ11
coupler in order to connect a remote GHU20x or GHU21x.
2.2.1.3 Sockets
The FBP242 board is the front backplane of MiCOM C264C equipped with the CPU260.
FIGURE 7: MiCOM C264C – FBP242 BOARD

Rear panel featuring the CT/VT BOARD:
FIGURE 8: MiCOM C264C – REAR PANEL EQUIPPED WITH A CT/VT BOARD (TMU2XX)
The FBP243 board is the front backplane of the MiCOM C264C equipped with the CPU270:
FIGURE 9: MiCOM C264C – FBP243 BOARD

Rear panel without CT/VT BOARD:
FIGURE 10: MiCOM C264C – REAR PANEL OVERVIEW WITHOUT CT/VT BOARD
2.2.2 MiCOM C264

2.2.2.1 Overview
Dimensions of this rack are in the figure below:
FIGURE 11: MiCOM C264 – FRONT PANEL OVERVIEW

Case properties:
• Case degree of protection: IP20 in standard
• Front Panel degree of protection: IP52 (for front panel with LEds or LCD)
• Metallic case
C264 fixation holes position:
FIGURE 12: FIXATION HOLES POSITION FOR C264

2.2.2.2 Front Panels

2.2.2.2.1 GHU201
The GHU201 is the front panel with LCD and LEDs used for the MiCOM C264:
• a keypad at the front plate for local HMI management with 5 pushbuttons
• an LCD (resolution of 128 x 128 pixels /16 lines of 21 characters each)
FIGURE 13: MiCOM C264 – GHU201 BOARD

2.2.2.2.2 GHU202
• The GHU202 is the front panel with LCD and LEDs used for the MiCOM C264 60TE
• A keypad at the front plate for local HMI management with 5 pushbuttons
• A LCD (resolution of 128 x 128 pixels /16 lines of 21 characters each)
FIGURE 14: MiCOM C264M – GHU202 BOARD

2.2.2.2.3 GHU211
The GHU211 is the front panel with LEDs used for the MiCOM C264:
• 1 pushbutton (L/R)

2.2.2.2.4 GHU221
The GHU221 is the front panel used for the MiCOM C264. This includes only an RJ11
coupler in order to connect a remote GHU20x or GHU21x.

2.2.2.3 Sockets
The FBP26X board is the front backplane of MiCOM C264M 60TE equipped with the
CPU270.
FIGURE 17: MiCOM C264M – FBP26X BOARD

Rear panel with CT/VT BOARD:
FIGURE 18: MiCOM C264M – REAR PANEL OVERVIEW WITH CT/VT CONNECTOR
The FBP283 board is the front backplane of the MiCOM C264 equipped with the CPU270.
FIGURE 19: MiCOM C264 – FBP283 BOARD

Rear panel without CT/VT BOARD:
FIGURE 20: MiCOM C264 – REAR PANEL OVERVIEW WITHOUT CT/VT CONNECTOR
2.3 Coding of board address

The same rule is applicable to all I/O boards (DIU200, DIU210, DIU211, AIU201, AIU211,
DOU201, CCU200 and CCU211) controlled by CPU 260:
Binary coding from 0 to 15 based on 4 jumpers top down:
− Jumper
− missing => 1
− present => 0
Example:
1 0
0 2
0 0
0 8
address =1 address = 10
C0030ENa
NOTE: Two boards of the same type must not have the same address
In option, the MiCOM C264/C264C hardware can be protected from moisture.

In this case, each board is coated with a special varnish.
2.4 Modules description

2.4.1 Power auxiliary supply and legacy ports board – BIU241
This board includes:
• the auxiliary power supply converter
• the watchdog relay (closed if the product is healthy)
• 2 outputs (Normally Open contacts) and 2 inputs for redundancy
• 2 isolated interfaces (Port 1: RS232 or RS485, Port 2: RS232, RS422 or RS485)

The power auxiliary supply board is protected against polarity reversal.
FIGURE 21: MiCOM C264 - BIU241 BOARD

The BIU241 board provides two isolated serial links.
This following figure locates the serial links configuration jumpers.
C0033ENa
FIGURE 22: BIU JUMPERS

2.4.1.1 Configurable communication Port 1 - RS232/485
The communication link characteristics are:
• full duplex serial protocol
• Transmission rate: 50 bps to 56 kbps (configurable with PACiS configurator or

settable via GHU20x)
Configuration:
The hardware jumpers arrangement is as follow.
• In RS232 set the jumpers S14, S16 and between S12.1 and S12.3
• In RS485 set the jumpers S13, S15 and between S12.1 and S12.2. It is possible to
end the line with a 124Ω resistor by setting S17. (See CO chapter to know when the
resistor has to be used).
2.4.1.2 Configurable communication Port 2 - RS232/422/485
• Transmission rate: 50 b/s to 56 kb/s (configurable with PACiS configurator or settable

via GHU20x)
Configuration:
The hardware jumpers arrangement is as follow.
• In RS232 set the jumpers S5, S6, S9 and S3
• In RS485 set the jumpers S7, S8, S2. It is possible to end the line with a 124Ω
resistor by setting S11. (See CO chapter to know when the resistor has to be used).
• In RS422 set the jumpers S7, S8, S4 and S2. It is possible to end the line with a 124Ω
resistor by setting the jumpers S10 and S11. (See CO chapter to know when the
2.4.2 Dual source power supply board – BIU261

The BIU261 board is the C264 dual source power supply. If the main power supply source
disappears the C264 shall be supply from the secondary source.
The board includes:
• Supply C264 from two power supplies (main and secondary) of the same range.
• The watchdog relay.
• 2 outputs and 2 inputs for redundancy.
• 1 isolated serial link (Port 2 only).
• The board is protected against polarity reversal.

This following figure locates the serial link configuration jumpers (S2 to S9)
FIGURE 23: MiCOM C264 - BIU261 BOARD

FIGURE 24: BIU261 JUMPERS
S6
S7
S3 S8
S2 S9
S4
S5
FIGURE 25: BIU261 JUMPERS DETAILS

2.4.2.1 Configurable communication Port 2

• Transmission rate: 50 b/s to 56 kb/s (configurable with PACiS configurator SCE)
• The configuration of communication link is configurated with hardware jumpers as

follow:
Interface Jumper Note

RS232 set S3, S5, S6, S9
RS422 set S1, S4, S7, S8 It is possible to end the line with a
120 Ω resistor by setting the jumpers
S10 and S11. (See CO chapter §2.3
to know when the resistor has to be
used).
RS485 set S2, S7, S8 It is possible to end the line with a
120 Ω resistor by setting S11. (See
CO chapter §2.3 to know when the
2.4.3 Central Processing Unit and base communications board – CPU260

The CPU260 board is based on a PowerPC processor including the 10/100BaseT Ethernet
communication.
This board includes the following optional capabilities:
• One 100BaseF Ethernet port (ST connector)
• Two non isolated RS232 links. The transmission rate must be the same on both links
(values from 50 to 56000 bps configurable with the configuration tool or settable via
GHU20x)
• An IRIG-B input
• A daughter board (DSPIO) for CT/VT management

The board is interfaced with all I/O boards and the front panel.
CPU260 has the following key features:
• 32-bit Power PC-based microprocessor (MPC860DP or MPC860P) clocked at 80 MHz
• 64 Mbytes Dynamic memory DRAM
• 16 Mbytes Flash memory
• 256 Kbytes static memory SRAM
• Calendar saved
FIGURE 26: MiCOM C264 - CPU260 BOARD

2.4.4 Central Processing Unit and base communications board – CPU270

The CPU270 board is based on a PowerPC processor including the 10/100BaseT Ethernet
communication.
• Two 100BaseTx Ethernet port
• Two non isolated RS232 links. The transmission rate must be the same on both links
(values from 50 to 56000 bps configurable with the configuration tool or settable via
GHU20x)
• An IRIG-B input
• An optional daughter board (DSPIO) for CT/VT management

This board is interfaced with all I/O boards and the front panel.
CPU270 has the following key features:
• 64-bit Power PC-based microprocessor (MPC8270VR) clocked at 266 MHz

(theoretical frequency); the real frequency is 262 MHz (shown at serial link)
• 256 Mbytes SDRAM
• 64 Mbytes Flash memory
• 128 Kbytes static memory SRAM
• Calendar saved
FIGURE 27: MiCOM C264 - CPU270 BOARD

2.4.5 DSPIO board

The DSPIO board is carried by the CPU260/270 board. It is used in conjunction with the
TMU210 board.
FIGURE 28: MiCOM C264 – DSPIO DAUGHTER BOARD ON CPU260

2.4.6 Circuit breaker Control Unit - CCU200

The Circuit breaker Control Unit (CCU200) board provides 8 digital inputs and 4 double pole
outputs using integrated relays.
The digital input (DI) capabilities of the CCU200 boards are:
• 8 optically isolated digital inputs
• 1 common contact for 2 inputs

The digital inputs can be configured in single or double remote signalling inputs on the same
module.
The digital output (DO) capabilities of the CCU200 boards are:
• 4 double pole switching relays with normally open (NO) contacts
• 1 common + and 1 common - contacts per 2 relays

A self-monitoring device for the output control chain is provided (address check, state
monitoring)
The +5V voltage is monitored to avoid issuing uncommanded events.
The digital outputs can be configured in double remote signalling only.
FIGURE 29: MiCOM C264 - CCU200 BOARD

2.4.7 Circuit breaker Control Unit - CCU211

The CCU211 board provides 8 digital inputs and 4 digital outputs using integrated relays.
The Digital Input capabilities of the CCU211 board are:
• 1 common contact for 2 inputs (positive or negative)
• The digital inputs can be used for single or double remote signalling, pulse or digital
measurement input on the same module.
• The input responds to negative input voltages and they are not self controlled
• All voltages between 24V and 220V DC selected using jumpers (with CPU3)
• Pre-defined triggering thresholds selected using jumpers:
FIGURE 30: MiCOM C264 - CCU211 BOARD

J1 connector: the ”jumper” is to be installed on J1 for A08
In all the others cases, no jumper is to be installed
J2 connector:
J2-4
J2-3
J2- 2
J2-1
Only one jumper is to be installed on J2 connector.
Version Jumper present on J1 Connector Place of jumper on J2 connector

A01 No J2-1
A02 No J2-2
A03 No J2-3
A04- A07 No J2-4
A08 Yes J2-4
• From 24V to 220VDC: a peak current (> 27mA) circulates during a short time (± 2 ms)
to clean external contacts:
The Digital Output capabilities of the CCU211 board are:
• 4 double pole switching relays with normally open (NO) contacts
• 1 common + and 1 common - contacts per 2 relays
• Nominal operating voltage range of 24V to 250 VDC / 230 VAC

A self-monitoring device for the output control chain is provided (address check, state
monitoring).
The +5V voltage is monitored to avoid issuing uncommanded events.
The digital outputs can be configured in double remote signalling only.
Board address setting:
• For use with CPU 2 board, the address of the board is selected using a four-position
header and jumper.
• For use with CPU 3 board, the address of the board can be defined by the location of
the CCU211 in the C264 rack (or by jumper if the board is used as spare of a previous
board). This location is defined using the SCE.
2.4.8 Digital Inputs Unit – DIU200

Depending on the applied voltage, 4 versions of the DIU200 are available.
The capabilities of the DIU200 boards are:
• 1 negative common contact for 2 inputs
• The digital inputs can be used for single or double status, pulse or digital
measurement input on the same module.
FIGURE 31: MiCOM C264 - DIU200 BOARD

2.4.9 Digital Inputs Unit – DIU211

The capabilities of the DIU211 boards are:
• 1 common contact for 2 inputs (positive or negative)
• The digital inputs can be used for single or double status, pulse or digital
measurement input on the same unit.
• All voltages between 24V and 220V DC
• Pre-defined triggering thresholds selected using jumpers:
FIGURE 32: MiCOM C264 - DIU211 BOARD

J1 connector: the ”jumper” is to be installed on J1 for A08
In all the others cases, no jumper is to be installed
J2 connector:
J2-4
J2-3
J2- 2
J2-1
Only one jumper is to be installed on J2 connector.
Version Jumper present on J1 Connector Place of jumper on J2 connector

A01 No J2-1
A02 No J2-2
A03 No J2-3
A04- A07 No J2-4
A08 Yes J2-4
• From 24Vdc to 220Vdc: a peak current (> 27mA) circulates during a short time
(± 2 ms) to clean external relay’s contacts:
• With 24VDC voltage, the high current consumption (>25mA) is permanent
Settings: for use with CPU 3 board, the address of the board can be defined by the location
of the DIU211 in the C264 rack (or by jumper if the board is used as spare of a previous
board). This location is defined using the SCE.
2.4.10 Digital Outputs Unit – DOU201

The Digital Outputs Unit (DOU201) board provides 10 isolated digital outputs using
integrated relays.
The DOU201 board capabilities are:
• 8 single pole relays with one normally open (NO) contact
• 2 single pole relays with 1 common for 2 outputs (NO/NC)
• Nominal operating voltage range of 24V to 250 VDC / 230 VAC

DOU201 has 8 single pole contacts which are normally open and 2 double pole contacts in
which one pole contact is normally open and one pole contact is normally close.
For use with CPU 2 board, the address of the board is selected using a four-position header
and jumper.
For use with CPU 3 board, the address of the board can be defined by the location of the
DOU201 in the C264 rack (or by jumper if the board is used as spare of a previous board).
This location is defined using the SCE.
FIGURE 33: MiCOM C264 - DOU201 BOARD

2.4.11 Analogue Input Unit – AIU201

The Analogue input module (AIU201) has 4 independent Analogue Inputs. Each AI can be
software-configured in a voltage or current range.
FIGURE 34: MiCOM C264 - AIU201 BOARD

2.4.12 Analogue Input Unit – AIU211

The Analogue input module (AIU211) has 8 isolated Analogue Inputs.
Analogue inputs (AI) are current DC signals delivered by transducers. Each AI can be
software-configured in a current input range (among five ranges).
FIGURE 35: MiCOM C264 - AIU211 BOARD

2.4.13 Transducerless Measurements Unit – TMU220

The transducerless measurement capabilities are the following:
• 4 measurement Current Transformers (4 CT) inputs
− Transformers have two ranges 1 and 5 amperes
• For the TMU220 5 measurement Voltage Transformers (5 VT) inputs
− AC voltage (VN): 57.73 Vrms to 500 Vrms
• Frequency operating range: 50 or 60 Hz ± 10%

The measured values are processed by an associated board:
Measurement unit Processor Processor board

TMU220 TMS320C6713 DSP220
2.4.14 Transducerless Measurements Unit – TMU210

The transducerless measurement capabilities are the following:
• 4 measurement Current Transformers (4 CT) inputs
− Each transformer has two ranges 1 and 5 amperes, selectable by a jumper
• 4 measurement Voltage Transformers (4 VT) inputs.
− Each transformer has two AC voltage ranges (VN): 57.73 Vrms to 130 Vrms or
220Vrms to 480 Vrms
• Frequency operating range: 50 or 60 Hz ± 10%
FIGURE 36: MiCOM C264 – TMU210 BOARD

2.4.15 Analogue Output Unit – AOU200

The AOU200 board provides 4 current analogue outputs. Each output is associated to a
Read Inhibit relay. The outputs are powered using an external power supply. The external
power supply has to provide a regulated voltage of +48V (+/- 5%).
FIGURE 37: MICOM C264 – AOU200 BOARD

2.4.16 Ethernet Switch Unit – SWU200/SWU202

The SWU200 board is an Ethernet switch with 4 electrical links.
The SWU202 board is an Ethernet switch with 4 electrical links and 2 optical links (multi-
mode).
FIGURE 38: MiCOM C264 – SWU200 BOARD

Jumpers are used to adapt the switch to your network:
Factory
N° Open Closed
setting
W1 No watching port 5 Fault watching Port 5 (Fx) Open
W3 Enable more aggressive back-off Enable less aggressive back-off Open
W4 Max length is 1536 byte Enable enforce the max frame Open
length for VLAN is 1522
W5 Enable half duplex back pressure Disable half duplex back pressure Open
W6 Continue sending frame regard- Enable to drop frame after 16 Open
less of number of collisions collisions
W7 Enable flow control Disable flow control Closed
W8 No priority reserve Enable 6KB priority buffer reserved Closed
W9 Half duplex for port 5 (Fx) Full duplex for port 5 (Fx) Closed
W10 Unlimited broadcast frames Enable 5% broadcast frame allowed Open
W11 Half duplex for port 6 (Fx) Full duplex for port 6 (Fx) Closed
W12 Enable 802.1p selected by Enable 802.1p field for all port Closed
EEPROM
W13 Share buffers up to 512 buffers Enable equal amount of buffers per Open
on a single port port (113 buffers)
OPEN CLOSE
Port 6
W12
Port 5 (optional)
LED1
LED2
LED3 Port 4
LED4
LED5
Port 3
LED6
W13
W4 Port 2
W3
W5
W6 W8
W7 W9
W10 W1 Port 1
W11
C0118ENa
SWU202 optical links: these 2 optical links are monitored; if one link comes down the default
is announced by the contacts (250V/5A):
Components side Pin State
1 Open
2 Common
1 2 3 3 Close
Close if default
C0119ENa
2.4.17 Ethernet Switch Unit – SWx202/SWx212, SWx204/SWx214 (x=R for dual Ring, x= D for
Dual homing)
These boards include 4 electrical links and 2 optical links for a dual ring/homing.
The SWx21y switches are SNMP-managed.
The SWx202/SWx212 models have a Multi-mode optical interface.
The SWx204/SWx214 models have a Single mode (mono-mode) optical interface.
FIGURE 39: MiCOM C264 – SWX202 BOARD
FIGURE 40: MiCOM C264 – SWX204 BOARD – WITH SC CONNECTOR

FIGURE 41: MiCOM C264 – SWX212 BOARD

To set the address board, see the AN chapter.
Switch management:
It is possible to manage the switch with the MDIO bus (J6).
Sub D 25 male
J2
8
1 9
MDC 2
3 11
4 18
19
20
21
22
C0122ENa
FIGURE 42: MiCOM C264 – MDIO BUS
Ethernet cable type

Use data quality twisted pair shielded cable rated category 5 with standard RJ45 connectors.
The maximum cable length for 10/100BaseT(x) is typically 100 meters.
Ethernet Optical Fibre
The FO cables are connected to the corresponding FO elements.
On the SWx202, the connector type for the multi mode fibre is ST.
On the SWx204 (Ref 2071021 A02 – up to Index B), the connector type for the single mode
fibre is ST.
On the SWx204 (Ref 2071021 A02 – from Index C and upper), the connector type for the
single mode fibre is SC.
Fibre Optic budget calculations

Optical power is expressed in Watts. However, the common unit of power measure is the
dBm and defined by the following equation: Power (dBm) = 10 log Power (mW) / 1 mW.
The following example shows the calculation of the maximum range for various types of
fibre:
SWR200 SWR200
SWR200 SWR200
2
Patch Patch
Panel Panel
SWR200 SWR200
C0123ENa
FIGURE 43: MiCOM C264 – DUAL RING ARCHITECTURE
Fibre type Multi mode (SWR202) Single mode (SWR204)

Wavelengh:1300nm
62.5/125 μm or 9/125 μm or 10/125 μm
50/125 μm
Power coupled into fibre - 19 dBm - 15 dBm
Sensitivity - 31 dBm - 34 dBm
Exemple 1: between two switches
Link budget 12 dB 19 dB
Connector loss (2) 0.8 dB 0.8 dB
Safety Margin 4 dB 4 dB
Allowed link attenuation 6.4 dB 13.4 dB
Typical cable attenuation 1 dB/km 0.4 dB/km
Maximum range 6.4 km 33 km
Example 2: between two switches via patch panel
Link budget 12 dB 19 dB
Connector loss (6) 0.8 dB 0.8 dB
Patch loss (2) 2 dB 1 dB
Safety Margin 4 dB 4 dB
Allowed link attenuation -0.8 dB 8.2 dB
Typical cable attenuation 1 dB/km 0.4 dB/km
Maximum range 0 20 km
The values given above are only approximate ones. Always use cable and connector losses
as specified by the manufacturer.
Connecting Dual Homing.

Between 2 Dual Homing SWD2xx
RA LINK A
RA
LINK A
EA
EA
SWD2xx SWD2xx
RB
RB LINK B
LINK B EB
EB
C0298ENa
B
Between more than 2 Dual Homing SWD2xx
RA LINK A
RA
LINK A
EA
EA
SWD2xx SWD2xx
RB
RB LINK B
LINK B EB
EB
RE RE RE RE
Simple Switch Fx Simple Switch Fx
A B
C0299ENb
2.4.18 Extended communication Unit – ECU200

This is an additional module plugged on DB9 connector of the CPU board. This module
converts non-isolated RS232 into optical signal.
A tab can be slided to change the coding:
• For IEC870-5-103 standard, the circle must be visible (light is sent for the “0” level)
• Otherwise the circle must be hidden (light is sent for the “1” level).
FIGURE 44: MiCOM C264 – ECU200 MODULE
Optical characteristics:
• Connector type: ST
• Wavelength: 820 nm
• Recommended Fibre cable: 62.5/125 μm

2.4.19 Extended communication Unit – ECU210

This is an additional module plugged on DB9 connector of the CPU board. This module
converts non-isolated RS232 into isolated RS485/RS422.
A tab can be slided to change the connection type:
• RS422 (4 wires): TA (+), TB(-), RA (+) and RA (-) are used. The circle must be hidden
• RS485 (2 wires): only TA (+), TB (-) are used. The circle must be visible
The indication on the module from bottom to top is as follows:
TA (+)
TB (-)
Ground
RA (+)
RB (-)
NOTE : There is no resistor to polarize the line
BLANK PAGE
Connections C264/EN CO/D10
MiCOM C264/C264C
CONNECTIONS
CONTENT
2. CONNECTOR BLOCKS 3
2.1 I/O Connector Block 3
2.2 CT/VT Connector Block 4
2.3 Serial communications connections 5
2.4 Optical communications connections 6
2.5 Ethernet-based communications connections 7
3. CONNECTION OF THE PROTECTIVE CONDUCTOR (EARTH) 8

3.1 Earthing 8
3.2 Cable fitting 8
4. CONNECTION DIAGRAMS FOR EACH I/O BOARDS 11

4.1 Power auxiliary supply and legacy ports board – BIU241 11
4.2 Dual source power supply board – BIU261 14
4.3 Central Processing Unit – CPU260/CPU270 16
4.4 Circuit breaker Control Unit - CCU200/CCU211 19
4.5 Digital Inputs module – DIU200 21
4.6 Digital Inputs module – DIU211 23
4.7 Digital Outputs module – DOU201 25
4.8 Analogue Input module – AIU201 27
4.9 Analogue Input module – AIU211 29
4.10 Transducerless Measurements Unit module –TMU220 31
4.11 Transducerless Measurements Unit module –TMU210 33
4.12 Analogue Output module – AOU200 35
4.13 Ethernet Switch Unit - SWU200/SWU202 37
4.14 Ethernet Redundant Switch Unit - SWR202/SWR212, SWR204/SWR214 38
4.15 Dual Homing Ethernet Switch Unit - SWD202/SWD212, SWD204/SWD214 39
4.16 Front panel 40
C264/EN CO/D10 Connections

connectors of the product IOs connectors and the connection diagrams of each I/O boards.
2. CONNECTOR BLOCKS
2.1 I/O Connector Block
All the I/O connection uses a standard type of connector block with a 24-pin and 5.08 mm
pitch.
The I/O connector block characteristics are the following:
Parameter Value
Continuous rating 10 A
Connection method Screw M3
Cable size 1.0 - 2.5 mm2
Connection pitch 5,08 mm
Isolation to other terminal and to earth 300 V basic insulation
Standards UL, CSA
TABLE 1: I/O CONNECTOR BLOCKS
PIN
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
C0041ENa
FIGURE 1: SAMPLE OF FEMALE CONNECTOR

NOTE: The connector is fixed with 2 screws M3 located on both vertical sides
of the connector.
2.2 CT/VT Connector Block

MiCOM C264 uses a standard black MiDOS 28 terminal block for transformer connection.
CT connection has 2 dual terminal groups, this allows dual rated transformer (1A/5A). Each
group has shorting contact to allow disconnection of CTs without damage.
The CT/VT connector block characteristics are the following:
Parameter Value
VT connection
3 second rating 30 A
30 ms rating 250 A
Cable size 2 off 2.5 mm2
CT connection
Cable size 2 off 2.5 mm2 / 1 off 4 mm2
TABLE 2: CT/VT CONNECTOR BLOCK
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
27 28
C0042ENa
FIGURE 2: STANDARD MIDOS 28 CONNECTOR

NOTE: The connector is fixed to the rack with 4 Phillips screws M4; 2 are
located on the top part and 2 on the bottom part.
2.3 Serial communications connections

For a RS485 or RS422 serial communication interface a termination resistor has to be
connected at each extremity of the bus.
If the IEDs or remote equipment (like Control Centre, printer, etc) are located at a long
distance (>10 m for RS232, >100 m for RS422 and >1000 m for RS485) from the
communication equipment or if the cables run through a noisy area, then optical fibre
communication should be used.
For both RS422 and RS485, the cable should be terminated at each end with a 120 ohm
resistor or the resistance of the BIU board can be used.
MiCOM C264 (Slave) (Slave) (Slave)

Rear panel Relay or IED Relay or IED Relay or IED
RS485 connector
Rx Tx Gnd Rx Tx Gnd Rx Tx Gnd Rx Tx Gnd
120 Ohms 120 Ohms
Earthing Earthing (*)

( )
* only if the IEDs are in the same cubicle
C0043ENb
FIGURE 3: EXAMPLE OF RS485 CONNECTIONS

There must be no more than two wires connected to each terminal, this ensures that a
“Daisy Chain or “straight line” configuration is used.
MiCOM C264 (Slave) (Slave) (Slave)

Relay or IED Relay or IED Relay or IED
C0044ENa
FIGURE 4: DAISY CHAIN CONNECTION

NOTE: The “Daisy Chain or “straight line” configuration is recommended and
the correct way to construct fieldbus.
WARNING: FOR SAFETY REASONS, WHEN THE COMMUNICATION PORTS ARE

CONNECTED TO DEVICES, FIRST OF ALL, IT IS MANDATORY THAT
SIGNAL GROUND SG (0 V) PIN OF THE COMMUNICATION PORTS
SHALL NOT BE CONNECTED TO EARTH, SECOND, THE SCREEN OF
RS232/RS422/RS485 CABLE SHALL BE CONNECTED TO A
PROTECTIVE EARTH.
MiCOM C264 MiCOM C264 (Slave) (Slave) (Slave)

Relay or IED Relay or IED Relay or IED
(Slave) (Slave) (Slave) (Slave)

Relay or IED Relay or IED Relay or IED Relay or IED
C0045ENa
FIGURE 5: STAR NETWORK OR NETWORK WITH TEES – WRONG CONNECTIONS

NOTE: A “Star” or a network with “Stubs (Tees)” is not recommended as
reflections within the cable may result in data corruption.
Wiring recommendation for RS422:
Master (c264) Slave(IED)
TA(+) R+
TB(-) R-
RA(+) T+
RB(-) T-
2.4 Optical communications connections

WARNING ABOUT LASER RAYS:
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.
Non–observance of this rule could possibly result in personal injury.
Signals transmitted via optical fibres are unaffected by interference. The fibres guarantee
electrical isolation between the connections.
If electrical to optical converters are used, they must have management of character idle
state capability (for when the fibre optic cable interface is "Light off").
2.5 Ethernet-based communications connections

The Ethernet-based communication available in the MiCOM C264 works in full duplex mode,
using either fibre optic media (ST connector) or 4 pair twisted cable.
Only the cable isolated category 5 (FTP: Foil Twisted Pair) or isolated (STP - Shielded
Twisted Pairs) with RJ45 connectors must be used.
1 2 3 4 5 6 7 8
C0046ENa
FIGURE 6: RJ45 CONNECTOR

Only pins N°1, 2, 3 and 6 is used in RJ45 Ethernet 10/100BaseTX.
The norm is:
1 = white / orange
2 = orange
3 = white / green
4 = blue (non used)
5 = white / blue (non used)
6 = green
7 = white / brown (non used)
8 = brown (non used)
The RJ45 connector when seen face on, flat side on bottom, side tab on top, then pin 1 is on
the left and pin 8 on the right.
3. CONNECTION OF THE PROTECTIVE CONDUCTOR (EARTH)

3.1 Earthing
MiCOM C264/C264C must be connected to the earth according to product safety standard
EN60255-27:2005 clause 5.1.5 using the protective conductor (earth) terminal located on
the rear panel.
Connection of the Protective conductor (earth).
The MiCOM C264/C264C racks must be earthed, for safety reasons, by connection of the
protective conductor (earth) to the M4 threaded stud allocated as the protective conductor
terminal (PCT), marked with the symbol shown.
WARNING – TO MAINTAIN THE SAFETY FEATURES OF THE EQUIPMENT
IT IS ESSENTIAL THAT THE PROTECTIVE CONDUCTOR
(EARTH) IS NOT DISTURBED WHEN CONNECTING OR
DISCONNECTING FUNCTIONAL EARTH CONDUCTORS
SUCH AS CABLE SCREENS, TO THE PCT STUD.
THE PROTECTIVE CONDUCTOR MUST BE CONNECTED FIRST, IN
SUCH A WAY THAT IT IS UNLIKELY TO BE LOOSENED OR REMOVED
DURING INSTALLATION, COMMISSIONING OR MAINTENANCE. IT IS
RECOMMENDED THAT THIS IS ACHIEVED BY USE OF AN ADDITIONAL
LOCKING NUT.
The protective conductor (earth) must be as short as possible with low resistance and
inductance. The best electrical conductivity must be maintained at all times, particularly the
contact resistance of the plated steel stud surface. The resistance between the MiCOM
C264/C264C protective conductor (earth) terminal (PCT) and the protective earth conductor
must be less than 10 mΩ at 12 Volt, 100 Hz.
Good conductor surface
Cable crimp
Copper cable
minimum section: 2.5mm²
C0047ENb
FIGURE 7: EARTHING CABLE EXAMPLE

3.2 Cable fitting
It is recommended to use cables (0.8 mm2) as following:
• Screened multi-strand cable has to be used for digital input-output signals. For cables
within the cubicle the cable screen can be connected to the earth at both ends of the
cable. If the cable is taken beyond the system cubicle the cable screen should be
earthed at one end only to prevent current flowing in the screen due any differences in
ground potential.
• Screened and twisted pair has to be used for analogue input-output signals. The
screen is connected to the earth by the end of Bay Module side.
• One or two screened and twisted pairs have to be used for lower communication
signals. The screen is connected to the earth by two cable ends.
It is recommended to group cables and fit them as near as possible to an earth plane or to
an element of an earth wire-mesh.
First example: MiCOM C264/C264C fitted without metallic cubicle.
MiCOM C264 - Rear panel
Protective
Functional earth Conductor (earth)
Terminal
Signal cable earth should Power supply cable earth

be connected to the should be connected to
suitable functional earth the suitable functional
connector earth connector
C0048ENd
FIGURE 8: FIRST EXAMPLE OF EARTHING ARRANGEMENT

Second example: MiCOM C264/C264C fitted in a metallic cubicle with other devices.
Metallic cubicle
other device
Earth
Functional Earth Protective Conductor

(earth) Terminal
MiCOM Cx64 or other device
Protective Conductor
(earth)
Auxiliary power Digital

boundary
connector
Protective Conductor
(earth)
Analogue
Power boundary
connector connector
Mount cables with fixings attached to the cubicle metallic surface

C0049ENd
FIGURE 9: SECOND EXAMPLE OF CABLE FITTING

4. CONNECTION DIAGRAMS FOR EACH I/O BOARDS

4.1 Power auxiliary supply and legacy ports board – BIU241
This board includes the auxiliary power supply converter, the watchdog relay, 2 inputs
/outputs for computer redundancy and 2 legacy ports (Ports N°1 / N°2).
The factory settled possibilities for the two isolated base legacy ports are:
Case Port N°1 Port N°2

1 RS232 RS232
2 RS232 RS485
3 RS422 RS232
4 RS422 RS485
5 RS485 RS232
6 RS485 RS485
TABLE 3: BASE LEGACY PORTS (PORTS N°1 / N°2) - CAPABILITIES
4.1.1 Connector description
Pin n° Signal
1 Redundancy relay 2 - NO contact
2 Redundancy relay - common 1-2
3 Redundancy relay 1 - NO contact
4 Watchdog relay - NO contact
5 Watchdog relay - NC contact
6 Watchdog relay - common
7 Redundancy input - 1+
8 Redundancy input - common 1 / 2
9 Redundancy input - 2+
10
11
12 RS232: RxD RS485: B - Port 1
13 RS232: SG (0 V) - Port 1
14 RS232: TxD RS485: A - Port 1
15 RS232: SG (0 V) - Port 2
16 RS232: CTS - Port 2
17 RS232: RxD RS485 B RS422: TB - Port 2
18 RS232: TxD RS485 A RS422: TA - Port 2
19 RS232: RTS RS422: RB - Port 2
20 RS422: RA - Port 2
21 RS232: DCD - Port 2
22 Voltage input: Gnd Gnd
23 Voltage input: AC/DC (+)
24 Voltage input: AC/DC (─)
TABLE 4: BIU241 BOARD - CONNECTOR DESCRIPTION

4.1.2 Block diagram
FIGURE 10: BIU241 AND BIU100 BOARD – BLOCK DIAGRAM

SIGNAL GROUND SG (OV) PIN (PIN 13/15 DB25 CONNECTOR) OF THE
COMMUNICATION PORTS SHALL NOT BE CONNECTED TO EARTH,
SECOND, THE SCREEN OF RS232/RS422/RS485 CABLE SHALL BE
CONNECTED TO A PROTECTIVE EARTH.
4.1.3 BIU wiring for redundant C264

In case of C264 redundancy, the following signals are to be wired for the management of the
main/ backup redundancy:
C264_1 C264_1 C264_2 C264_2

Signal BIU Pin BIU Pin Signal
Redundancy output contact 1 ------> 9 Redundancy input: 2+
relay 2
(Open on C264 Failure)
Redundancy relay: common 2 (+) 2 Redundancy relays: common
1& 2 (+) 1& 2 (+)
relay 1
(Closed when “Active”,
Open when “Standby”)
Redundancy input: 1+ 7 <------ 3 Redundancy output contact
relay 1
(Closed when “Active”
Redundancy input - common 8 (-) 8 Redundancy input - common
1 & 2 (-) 1 & 2 (-)
Redundancy input: - 2+ 9 <------ 1 Redundancy output contact
relay 2
4.2 Dual source power supply board – BIU261

The BIU261 board is the C264 dual source power supply. If the main power supply source
disappears the C264 shall be supply from the secondary source.
The board includes:
− Supply C264 from two power supplies (Main and secondary) of the same range.
− The watchdog relay.
− 2 outputs and 2 inputs for redundancy.
− 1 isolated serial link (Port 2 only).
− The board is protected against polarity reversal.

The factory settled possibilities for the isolated base legacy port are configurated by
hardware jumpers:
Case Port N°2

1 RS232
2 RS422
3 RS485
TABLE: BASE LEGACY PORT - CAPABILITIES

Pin n° Signal
1 Redundancy relay 2 NO contact
2 Redundancy relay common 1-2
3 Redundancy relay 1 NO contact
4 Watchdog relay NO contact
5 Watchdog relay NC contact
6 Watchdog relay common
7 Redundancy input 1+
8 Redundancy input common 1-2
9 Redundancy input 2+
10 Voltage source 2 : Secondary power supply DC( + )
11 Voltage source 2 : Secondary power supply DC( ─ )
12 Not Used
13 Not Used
14 Not Used
15 RS232: SG (0 V) Port 2
16 RS232: CTS Port 2
17 RS232: RxD RS485 B / RS422: TB Port 2
18 RS232: TxD RS485 A / RS422: TA Port 2
19 RS232: RTS RS422: RB Port 2
20 RS422: RA Port 2
21 RS232: DCD Port 2
22 Voltage source GND GND
23 Voltage source 1 : Main power supply DC( + )
24 Voltage source 1 : Main power supply DC( ─ )
TABLE: BIU261 BOARD - CONNECTOR DESCRIPTION

4.2.2 Safety recommandations

SIGNAL GROUND SG (OV) OF THE COMMUNICATION PORTS SHALL
NOT BE CONNECTED TO EARTH, SECOND, THE SCREEN OF
RS232/RS422/RS485 CABLE SHALL BE CONNECTED TO A
PROTECTIVE EARTH.
4.2.3 BIU wiring for redundant C264

In case of C264 redundancy, the following signals are to be wired for the management of the
main/ backup redundancy:
C264_1 C264_1 C264_2 C264_2

Signal BIU Pin BIU Pin Signal
relay 2
Redundancy relay: common 2 (+) 2 Redundancy relays: common
1& 2 (+) 1& 2 (+)
relay 1
(Closed when “Active”,
Redundancy input: 1+ 7 <------ 3 Redundancy output contact
relay 1
(Closed when “Active”
Redundancy input - common 8 (-) 8 Redundancy input - common
1 & 2 (-) 1 & 2 (-)
Redundancy input: - 2+ 9 <------ 1 Redundancy output contact
relay 2
4.3 Central Processing Unit – CPU260/CPU270

In addition to two 10/100BaseT Ethernet interfaces, these boards include:
• The IRIG-B interface: BNC plug
• Two non-isolated RS232 interfaces (DB9 male connector)

4.3.1 Block diagram
FIGURE 11: CPU260/CPU270 BOARDS – BLOCK DIAGRAM

DB9 connectors:
1 CD
2 RX
3 TX
4 5V ( for ECU20x supply)
5 SG (0 V)
6 Not used
7 RTS
8 CTS
9 Not used
NOTE: Unlike standardized RS232 connector, pin 4 is not normally used as

the DTR signal (Data Terminal ready). It is here permanently
connected to power supply +5 V. So this pin 4 must not be used in a
null-modem cable.
SIGNAL GROUND SG (0 V) PIN (PIN 5 DB9 CONNECTOR) OF THE
COMMUNICATION PORTS SHALL NOT BE CONNECTED TO EARTH,
SECOND, THE SCREEN OF RS232 CABLE SHALL BE CONNECTED TO
A PROTECTIVE EARTH.
Connector DB 9
5
1
6 9
1
5
9 6
C0152ENa
FIGURE 12: OPTIONAL LEGACY PORTS (PORTS N°3 / N°4) – DESCRIPTION

The ECU200/ECU201 external modules convert non-isolated RS232 into optical link/isolated
RS485 or RS422.
The ECU201 module has a 5-wire female connector.
1 TA (+)
2 TB (-)
3 Ground
4 RA (+)
5 RB (-)
TABLE 5: ECU201 - DESCRIPTION
To change the connection type, slide the tab:
• RS422 (4 wires): TA(+), TB(-), RA(+), RB(-) are used. The circle must be hidden.
• RS485 (2 wires): only TA(+) and TB(-) are used. The circle must be visible.
The ECU200 module has 2 optical fibre connectors (ST type):
• TX: optical emitter
• RX: optical receiver

NOTE : For ecu201 module, the "ground" pin (pin 3 of the 5-wire female
connector) of the communication ports rs422/rs485 is not connected.
4.3.3 DSPIO board
The Protection Input & Ouputs module is a daughter board of the CPU board dedicated to
the Circuit-breaker Protection feature management. It provides 4 optically isolated digital
inputs (with 1 common for 2DI) and 3 outputs (3 DO with 1 common) using relays.
FIGURE 13: DSPIO BOARD – BLOCK DIAGRAM

The DSPIO board is equipped with a 24-way 5.08 mm pitch connector.
Pin N°. Signal

1 + Digital Input Blocking
2 - Digital Input Blocking
3 Logic Selectivity
4 Digital Input
5 Common to Digital Input & Logic Selectivity
6 Cold Load Start
7 Disturbance start
8 Common to Cold Load Start & Disturbance start
9 K4/1 + Output
10 K4/1 – Output
11 K4/2 + Output
12 K4/2 – Output
13 K3/1 + Output
14 K3/1 – Output
15 K3/2 + Output
16 K3/2 – Output
17 Not connected
18 Trip phase C
19 Not connected
20 Trip phase B
21 Not connected
22 Trip phase A
23-24 Common Digital outputs A, B & C
TABLE 6: DSPIO BOARD - CONNECTOR DESCRIPTION
4.4 Circuit breaker Control Unit - CCU200/CCU211

The Circuit breaker Control boards provide 8 digital inputs (8 DI with one common for 2DI)
and 4 double pole outputs (4 DO) using integrated relays.
4.4.1 Block diagram
Circuit breaker CCU 200

Control U nit
board
PIN Digital Inputs
1 VIN VIN
+ DI1 + DI2
- -
2 - -
3
4 VIN VIN
+ DI3 + DI4
- -
5 - -
6
7 VIN VIN
+ DI5 + DI6
- -
8 - -
9
10 VIN VIN
+ DI7 + DI8
- -
11 - -
12
13 Digital Outputs
14 B
CO 1
15 A
16 A
17 B CO 2
18
19
20 B
CO 3
21 A
22 A
23 B CO 4
24
C0058ENa
FIGURE 14: CCU2XX BOARD – BLOCK DIAGRAM

NOTE: On CCU211, the + and – of Digital Inputs can be inversed
NOTE: Different types of CCU200 boards exist depending on the input

voltage range so before connection, a special attention is to be paid to
the version of the board:
- version A01 for 24VDC,
- version A02 for 48/60 VDC,
- version A03 for 110/125VDC
- version A04 for 220 VDC

The CCU2xx board is equipped with a 24-pin 5.08 mm pitch connector.
Pin N°. Signal

1 Digital Input 1+
2 Digital Input 2+
3 Common Digital Input 1 / 2
4 Digital Input 3+
5 Digital Input 4+
7 Digital Input 5+
8 Digital Input 6+
10 Digital Input 7+
11 Digital Input 8+
13 Digital Output 1 B
14 Digital Output 1 A
15 Common Digital Output 1 - 2 A
18 Common Digital Output 1 - 2 B
21 Common Digital Output 3 – 4 A
24 Common Digital Output 3 - 4 B
TABLE 7: CCU2XX BOARD - CONNECTOR DESCRIPTION

NOTE : On CCU211, “Common Digital inputs” can be connected with a
positive or negative polarity.
4.5 Digital Inputs module – DIU200

The Digital Input module (DIU200) provides 16 optically isolated Digital Inputs (with one
common for two DI).
4.5.1 Block diagram
D igital Input U nit DIU200

board
PIN Signal inputs
1 VIN VIN
+ DI1 + DI2
- -
2 - -
4 VIN VIN
+ DI3 + DI4
- -
5 - -
7 VIN VIN
+ DI5 + DI6
- -
8 - -
10 VIN VIN
+ DI7 + DI8
- -
11 - -
12
13 VIN VIN
+ +
DI9 DI10
- -
14 - -
15
16 VIN VIN
+ +
-
DI11 -
DI12
17 - -
18
19 VIN VIN
+ DI13 + DI14
- -
20 - -
21
22 VIN VIN
+ DI15 + DI16
- -
23 - -
24
C0056ENa
FIGURE 15: DIU200 BOARD – BLOCK DIAGRAM

NOTE: Different types of DIU200 boards exist depending on the input voltage
range
Before connection, a special attention is to be paid about the version
of the board:
- version A01 for 24VDC,
- version A02 for 48/60 VDC,
- version A03 for 110/125VDC
- version A04 for 220 VDC

The DIU200 board is equipped with a 24-pin 5.08 mm pitch connector.
Pin N°. Signal

1 Digital Input 1+
2 Digital Input 2+
3 Negative Common Digital Input 1 / 2
4 Digital Input 3+
5 Digital Input 4+
7 Digital Input 5+
8 Digital Input 6+
10 Digital Input 7+
11 Digital Input 8+
13 Digital Input 9+
14 Digital Input 10+
TABLE 8: DIU200 BOARD - CONNECTOR DESCRIPTION
4.6 Digital Inputs module – DIU211

The Digital Input module (DIU211) provides 16 optically isolated digital inputs with one
common for two DI. This common links the positive inputs of the two opto-couplers.
4.6.1 Block diagram
FIGURE 16: DIU211 BOARD – BLOCK DIAGRAM


The DIU211 board is equipped with a standard type of connector with a 24-pin and 5.08mm
pitch.
Pin N°. Signal

1 Digital Input 1-
2 Digital Input 2-
3 Positive Common Digital Input 1 / 2
4 Digital Input 3-
5 Digital Input 4-
7 Digital Input 5-
8 Digital Input 6-
10 Digital Input 7-
11 Digital Input 8-
13 Digital Input 9-
14 Digital Input 10-
NOTE: The triggering threshold depends on jumper positions; see the HW

chapter.
4.7 Digital Outputs module – DOU201

The Digital Outputs Unit board provides 10 isolated outputs using relays.
4.7.1 Block diagram
D igital O utput U nit DOU201

board
PIN Signal outputs
2 DO 1
3
4 DO 2
5
6 DO 3
7
8 DO 4
9
10 DO 5
11
12 DO 6
13
14 DO 7
15
16 DO 8
17
18
19
20
DO 9
21
22
23
DO 10
24
C0057ENc
FIGURE 17: DOU201 BOARD – BLOCK DIAGRAM


The DOU201 board is equipped with a 24pin 5.08 mm pitch connector.
Pin N°. Signal

1 Digital output 1 +
2 Digital output 1 -
17 NC
18 NC
19 Digital output 9 – NO contact
20 Digital output 9 – NC contact
21 Common Digital output 9
22 Digital output 10 – NO contact
23 Digital output 10 – NC contact
24 Common Digital output 10
TABLE 9: DOU201 BOARD - CONNECTOR DESCRIPTION

4.8 Analogue Input module – AIU201

The Analogue input module (AIU201) provides 4 independent analogue inputs.
4.8.1 Block diagram
Analogue Input U nit AIU201

board
PIN Signal inputs
1 + U
2 - V AI 1
#
3 + U
4 - mA AI 1
#
5 Insulated
GND
6
GND
7 + U
8 - V AI 2
#
9 + U
10 - mA AI 2
#
11 Insulated
GND
12
GND
13 + U
14 - V AI 3
#
15 + U
16 - mA AI 3
#
17 Insulated
GND
18
GND
19 + U
20 - V AI 4
#
21 + U
22 - mA AI 4
#
23 Insulated
GND
24
GND
C0059ENb
FIGURE 18: AIU201 BOARD – BLOCK DIAGRAM


The AIU201 board is equipped with a 24-pin 5.08 mm pitch connector.
Pin N°. Signal

1 Analogue Input 1+ (voltage)
2 Analogue Input 1-(voltage)
3 Analogue Input 1+(current)
4 Analogue Input 1-(current)
5 Insulated Ground 1
6 Ground
12 Ground
18 Ground
24 Ground
TABLE 10: AIU201 BOARD - CONNECTOR DESCRIPTION

4.9 Analogue Input module – AIU211

The Analogue input board AIU211 provides 8 isolated Analogue inputs.
4.9.1 Block diagram
FIGURE 19: AIU211 BOARD – BLOCK DIAGRAM


The AIU211 board is equipped with a 24-pin 5.08 mm pitch connector.
Pin N°. Signal

1 Analogue Input 5+ (current)
2 Analogue Input 5- (current)
5 Not Connected
6 Ground
11 Not Connected
12 Ground
17 Not Connected
18 Ground
23 Not Connected
24 Ground
TABLE 11: AIU211 BOARD - CONNECTOR DESCRIPTION

4.10 Transducerless Measurements Unit module –TMU220

The Transducerless Measurements Unit module (TMU220) provides 5 transducerless
voltage inputs (VT) and 4 transducerless current inputs (CT).
4.10.1 Block diagram
FIGURE 20: TMU220 BOARD – BLOCK DIAGRAM


The TMU220 board is equipped with a standard MiDOS 28 connector (see Figure 2:
Standard MiDOS 28 connectors).
STAR topology DELTA topology

Wave form:
Electrical Measure type in Measure type in
Pin N°. Signal Related
Signal PACIS PACIS
channel
Configurator Configurator
1 Current Input 5A - N1 IBusbar1 5A -
Ibusbar RMS 1 Ibusbar RMS 1
2 Current Input 5A – N2 IBusbar1 5A + value of the value of the
CI#3
3 Current Input 1A – N1 IBusbar1 1A - busbar current busbar current
phase phase
4 Current Input 1A – N2 IBusbar1 1A +
5 Current Input 5A – C1 IC 5A -
6 Current Input 5A – C2 IC 5A + IC, RMS value of IC, RMS value of
the current phase the current phase CI#2
7 Current Input 1A – C1 IC 1A - C C
8 Current Input 1A – C2 IC 1A +
9 Current Input 5A – B1 IB 5A -
10 Current Input 5A – B2 IB 5A + IB, RMS value of
B IB, RMS value of
B

11 Current Input 1A – B1 IB 1A - B B
12 Current Input 1A – B2 IB 1A +
13 Current Input 5A – A1 IA 5A -
14 Current Input 5A – A2 IA 5A + IA, RMS value of IA, RMS value of
15 Current Input 1A – A1 IA 1A - A A
16 Current Input 1A – A2 IA 1A +
17 NC NC NA NA NA
18 NC NC NA NA NA
19 Voltage Input – X1 U Busbar2 - Vbusbar RMS 2 Vbusbar RMS 2
value of the value of the
20 Voltage Input – X2 VI#4
busbar voltage busbar voltage
U Busbar2 + phase phase
21 Voltage Input – U1 UA - VAN, RMS value VAB, RMS value
of the voltage of the voltage VI#0
22 Voltage Input – U2 UA + phase A phase AB
23 Voltage Input – V1 UB - VBN, RMS value VBC, RMS value
24 Voltage Input – V2 UB + phase B phase BC
25 Voltage Input – W1 UC - VCN, RMS value VCA, RMS value
26 Voltage Input – W2 UC+ phase C phase CA
27 Voltage Input – N1 U Busbar1 - Vbusbar RMS 1 Vbusbar RMS 1
value of the value of the
28 Voltage Input – N2 VI#3
busbar voltage busbar voltage
U Busbar1 + phase phase
TABLE 12: TMU220 BOARD - CONNECTOR DESCRIPTION

4.11 Transducerless Measurements Unit module –TMU210

The Transducerless Measurements Unit module TMU210 provides 4 transducerless voltage
inputs (VT) and 4 transducerless current inputs (CT).
Protection TMU 210

Current & Voltage
Unit board 1 & 5 Amps
PIN
Current inputs
Voltage inputs
C0363ENa
FIGURE 21: TMU 210 BOARD – BLOCK DIAGRAM


The TMU210 board is equipped with a standard MiDOS 28 connector (see Figure 2:
Standard MiDOS 28 connectors).
Pin N°. Signal

1 Current Input 5A - N1
2 Current Input 5A – N2
3 Current Input 1 Amps or 5 Amps – N-
4 Current Input 1 Amps or 5 Amps – N+
5 Not connected
6 Not connected
7 Current Input 1 Amps or 5 Amps – C-
8 Current Input 1 Amps or 5 Amps – C+
9 Not connected
10 Not connected
11 Current Input 1 Amps or 5 Amps – B-
12 Current Input 1 Amps or 5 Amps – B+
13 Not connected
14 Not connected
15 Current Input 1 Amps or 5 Amps – A-
16 Current Input 1 Amps or 5 Amps – A+
17 Not connected
18 Not connected
19 Not connected
20 Not connected
21 Voltage Input – U1
22 Voltage Input – U2
23 Voltage Input – V1
24 Voltage Input – V2
25 Voltage Input – W1
26 Voltage Input – W2
27 Voltage Input – N1
28 Voltage Input – N2
TABLE 13: TMU210 BOARD - CONNECTOR DESCRIPTION

4.12 Analogue Output module – AOU200

The AOU200 board provides 4 current analogue outputs. Each output is associated to a
Read Inhibit relay. The outputs are powered using an external power supply. The external
power supply has to provide a regulated voltage of +48V (+/- 5%).
This power supply will supply a minimum of 7W per AOU200 board.
Exemple: If four AOU200 boards are installed in the C264, it must supply at
least 28 W.
FIGURE 25: AOU200 BOARD – BLOCK DIAGRAM

N° Description
1 External power supply +48V
2 NIL
3 External power supply (0V)
4 NIL
5 WDOG+
6 WDOG-
7 NIL
8 READ INHIBIT AO n° 1+
9 READ INHIBIT AO n° 1-
16 NIL
17 AO n° 1+
18 AO n° 1-
19 AO n° 2+
20 AO n° 2-
21 AO n° 3+
22 AO n° 3-
23 AO n° 4+
24 AO n° 4-
TABLE 20: AOU200 BOARD – CONNECTOR DESCRIPTION

4.13 Ethernet Switch Unit - SWU200/SWU202

The SWU200 board provides four electrical links.
The SWU202 board provides four electrical links and two optical links.
4.13.1 Ethernet connectors description
These boards are equipped with four RJ45 connectors.
The lower connector is for port 1. The upper connector is for port 4.
Pin N°. Signal

1 Rx+
2 Rx-
3 Tx+
4 not used
5 not used
6 Tx-
7 not used
TABLE 14: SWU200/202 BOARD – RJ45 CONNECTOR DESCRIPTION

4.13.2 Fault signal connector description
These boards are equipped with a 3 pin connector block to deliver a communication fault
signal.
1 Open
2 Common
1 2 3 3 Close
Close if default
C0119ENa
Wiring recommendation:
Due to the proximity of the port 4 Ethernet connector, it is strongly recommended that the
“Fault signal connector” connections are visually checked before any hand manipulation of
the Ethernet connectors.
Particular attention is to be paid during the wiring phase, not to damage the cable’s isolation.
FIGURE 22: SWITCHES: PORT 4 ETHERNET AND FAULT SIGNAL CONNECTORS

4.14 Ethernet Redundant Switch Unit - SWR202/SWR212, SWR204/SWR214

These boards are Ethernet switches with 4 electrical links and 2 optical links for a
redundancy ring.
The SWR21x switches are SNMP managed (they integrate an SNMP server) and can be
remotely accessed from SNMP “client”.
The SWR202/SWR212 model has a Multi-mode optical interface.
The SWR204/SWR214 model has a Single mode (mono-mode) optical interface.
The upper connector is for port 1. The lower connector is for port 4.
Pin N°. Signal

1 Rx+
2 Rx-
3 Tx+
4 not used
5 not used
6 Tx-
7 not used
TABLE 15: SWR2X2/2X4 BOARD – RJ45 CONNECTOR DESCRIPTION

signal.
If one link of the optical ring comes down the default is announced by the output contacts
(max 250V/5A):
1 Default Rp-Es
2 Common
1 2 3 3 Default Rs-Ep
Close if default
C0121ENa
4.15 Dual Homing Ethernet Switch Unit - SWD202/SWD212, SWD204/SWD214

These boards are Ethernet switches with 4 electrical links and 2 optical links for a dual
homing solution.
The SWD21x switches are SNMP managed (they integrate an SNMP server) and can be
remotely accessed from SNMP “client”.
The SWD202/SWD212 model has a multi-mode optical interface.
The SWD204/SWD214 model has a single mode (mono-mode) optical interface.
The upper connector is for port 1. The lower connector is for port 4.
Pin N°. Signal

1 Rx+
2 Rx-
3 Tx+
4 not used
5 not used
6 Tx-
7 not used
TABLE 16: SWD2X2/SWD2X4 BOARD – RJ45 CONNECTOR DESCRIPTION

signal.
If one link of the optical ring comes down the default is announced by the output contacts
(max 250V/5A):
1 Default Link A
2 common
1 2 3 3 Default Link B
Close if default
C0297ENa
4.16 Front panel

The front panel includes an RS232 interface, not galvanically isolated. This RS232 interface
is dedicated to maintenance and settings.
The properties of the serial link (DB9 female connector) for the maintenance dialogue are:
• Baud rate: 19200
• Data bits: 8
• Parity: No
• Stop bit: 1
• Control Xon/Xoff
Connector description:
5 4 3 2 1
9 8 7 6
C0061ENa
FIGURE 23: FRONT PANEL CONNECTOR VIEW
Pin N°. Signal

1 Data Carrier Detect (DCD) – input
2 Receive Data (RxD) – input
3 Transmit data (TxD) – output
4 Data Terminal Ready (DTR) – output
5 Signal Ground (SG) - 0V
6 Data Set Ready (DSR) – input
7 Ready To Send (RTS) – input
8 Clear To Send (CTS) – input
9 NC
TABLE 17: FRONT PANEL - CONNECTOR DESCRIPTION

Human Interface C264/EN HI/D10
MiCOM C264/C264C
HUMAN INTERFACE
CONTENTS
2. THE FRONT PANEL 4

2.1 Overview 4
2.1.1 LED’s management 5
2.2 Configuration data 8
2.2.1 General display management 8
2.2.2 Language support 10
2.2.3 Time and date displaying 11
2.2.4 Bay panels 12
2.2.5 Events panel 22
2.2.6 Faults panel 23
2.2.7 Alarms panel 24
2.2.8 Disturbance records panel 25
2.2.9 Configuration panel 26
2.2.10 Display of binary input information 31
2.2.11 Display of binary output information 32
2.2.12 Menu tree 33
2.2.13 Controls (subject to privilege) 35
2.2.14 Password management 42
3. THE COMPUTER MAINTENANCE TOOL 44
4. THE EMBEDDED MAINTENANCE WEB SERVER 45
5. THE PRINTER 46
5.1 Inputs 46
5.2 Outputs 46
5.3 Printer management 47
5.3.1 Header & footer 47
5.3.2 Chronology & time stamp 47
5.3.3 Printer out of service 47
5.3.4 Circular FIFO management 47
C264/EN HI/D10 Human Interface
BLANK PAGE

This document is a chapter of the MiCOM C264 documentation. It describes the three User
Interfaces (coded HI for Human Interface) of this computer:
• The Front Panel (FP alias DHMI)
• The Computer Administration Tool ( CAT)
• The Printer
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 LEDs
The first LEDs indicate the MiCOM C264/C264C status information, that is 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 1 minor Not used No fault
major fault (hardware, fault (I/O board, commun-
database) (1) ication to IEDs, …) (2)
2 Yellow All the alarms are ac- All alarms displayed in There is at least one No alarm
knowledged, but there the alarm panel are not acknowledged
is at least one alarm inactive & acknowledged alarm displayed in
still active. (3) the alarm panel
3 Yellow Computer in operation Computer in maintenance Computer in test Computer in
reboot
4 Green Power on Not used Not used Power off
5 (4) Red All bays managed by Bays managed by the Not used All bays
the computer are in computer are not in the managed by the
LOCAL mode same control mode computer are in
REMOTE
6 Red Global fault (5) Not used Not used No fault at all
(1) Major fault: MiCOM C264 not available due to internal failure (database error, CPU
board failure, …).
(2) A minor fault is a fault causing only the non availability of a part of the functionality.
(3) When the alarm disappears, the LED returns automatically to OFF.
(4) Assigned by computer only for without LCD panel: GHU2x1 or for an extension C264.
(5) It may be a board fault, an IED fault, a power off, a watchdog issue (DO#0 of BIU
board), an IED or extension disconnected.
2.1.1.2 Other LEDs

Other LEDs’ default assignment:
• LED 7: DIU board fault

• LED 8: AIU board fault
• LED 9: DOU board fault
• LED 10: CCU board fault
• LED 11: AOU board fault
• LED 12: At least one IED is disconnected (mono / main / extension rack)
• LED 13: At least one extension rack is disconnected (main rack)
Connection status with main rack (extension rack)
On the extension racks, these default assignments cannot be modified.
The LEDS 14 to 17 can be used only on the main rack.
Summary table:
Mono rack architecture Multi rack architecture

Computer Principal Rack Extension Rack
Led Graphical Panel Simple Panel Graphical Panel Simple Panel Simple Panel
1
Assigned by Assigned by Assigned by Assigned by Assigned by
2
computer computer computer computer computer
3
4 Linked to power supply
5 Not Used Not Used
Assigned by Assigned by Assigned by
6 Assigned by computer Assigned by computer computer
computer computer
7
8
9 Pre- Pre-
defined defined Pre- Pre-
10 Pre-defined
defined defined
11
12 Free Free Free Free
13
14
Not Not
15 Not
Used Used Not Used Not Used
16 Used
17
2.1.1.3 Example: AVR dedicated C264

Up to 17 Leds are dedicated to AVR signalling and alarms:
Led # Color Description

01 red Hardware Fault
02 amber
03 amber Maintenance Mode
04 green Power Supply
05 red AVR Mode: MANU
06 red AVR AUTO : OFF
07 red Vn-5%
08 red
09 red Lower Tap Change Order
10 red Raise tap Change Order
11 red Loss of Voltage
12 red Abnormal Voltage
13 red End of Tap reached
14 red Low Tap Signal
15 red High Tap Signal
16 red Tap Changer blocked
17 red Tap Changer Fault
2.2 Configuration data

The behaviour of the user-configurable LEDs is defined in the computer DataBase.
When using a simple DHMI, the 11 user-configurable LEDs give the status of the associated
BI. Each BI state is displayed using the ON / OFF / BLINKING led state.
When using a graphical DHMI (with LCD), the 13 user-configurable LEDs can be configured
to have 2 different behaviours:
1. give the status of the associated BI. Each BI state is displayed using the ON / OFF /
BLINKING led state (same way as with a Simple DHMI),
2. provide a way to manage BIs as alarms.
This behaviour 2 is detailed hereafter:
• if the BI is “transient”:
− if the BI is SET, the associated LED is ON or Blinking Slow (depends of the DB),
− after pressing the ‘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.
Remarks:
− The “C” button is used for the navigation in the menu tree. This feature remains and
so alarm acknowledgement will be not allowed from the menu tree.
− The alarm acknowledgement function is not available with the simple panel (no “C”
button available).
The 11 other LED’s are freely configurable: they can be attached to a datapoint.
Furthermore, the datapoint state is displayed through a led state: on, off, slow blinking, fast
blinking.
For a Single Point, the Set / Reset / Invalid (i.e. all other states) can be attached to a LED.
For a Double Point, the Open / Close / Invalid (i.e. all other states) can be attached to a LED.
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
Panel navigation is described as follow:
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 the 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), 16 characters maximum
• the time (hh:mm:ss) preceded by its state (* means not synchronised)
• 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

The AVR Graphical bay panel shows up to 8 measurement values; their position and label
are settable, but the top and bottom lines are excluded.
Format: <Measure Name> : <Value> <Unit>
• Measurement Name : 8 characters max, settable
• Value: up to 8 characters with ± , decimal separator Ex:-12345.56 or 120 or 12345678
• Unit: 4 characters max, settable
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)…
An 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.
Display of AVR measurements

The panels dedicated to AVR Measurement show:
• Target Voltage value (%),
• Target Voltage value (kV).
• Voltage/Target V” in %
View 1
A V R 1 / 3 H H : M M : S S
<Bay name>= 16 char max
M O D E : <AVR running mode>= 11 char max

S T A T U S : <AVR status>= 11 char max
V M E A S :
<measurement 3 digits <decimal part 2
. k V
double size> digits double size>
T P I :
<meas 2 digit>
D E V I A T I O N : ± <Meas> %
View 2
A V R 2 / 3 H H : M M : S S

V M E A S : <meas 5 digits> k V
V T A R G E T : <meas 5 digits> k V
T A R G E T : <meas 3digits> %
D E V I A T I O N : <meas 3digits> %
T P I : <meas 2dg + R A I S E
- L O W
View 3
A V R 3 / 3 H H : M M : S S

V k V
I : <meas 5 digits> A
P : <meas 5 digits> M W
Q : <meas 5 digits> M V A r
S : <meas 5 digits> M V A
C O S φ : <meas 5 digits>
φ : <meas 5 digits>
I . S I N φ : <meas 5 digits> A
• Bay Name: Short name of the bay defined in configuration
• MODE: Actual AVR running mode (MANUAL or AUTOMATIC)
• STATUS: Actual AVR status (ON or OFF)
• V MEAS: Measured Voltage (regulated) – fixed format on 5 digits: xxx.xx
• TPI: actual Tap Position – fixed format on 2 digits: xx
• DEVIATION: Delta between Target voltage value and Measured Value (%): fixed
format on 2 digits: xx
• V TARGET: Target Voltage for the concerned transformer (come from a remote
Setpoint or from local command, or from predefined value in database) – fixed format
on 5 digits: xxx.xx
• TARGET: Voltage Target shown as a % of the Nominal Value. (Configurable option on

the Page) – fixed format on 3 digits: xxx
• +RAISE / -LOW: Selectable button for control sequence for Raise/Lower
• V: Measured Voltage (regulated) – fixed format on 5 digits: xxx.xx
• I: Measured current 3 digits
• P: Measured Power 5 digits xxx.xx
• Q: Measured Reactive power 5 digits xxx.xx
• S: Measured Apparent power 5 digits xxx.xx
• COS φ: Measured cosinus phi 5 digits xxx.xx
• φ: Measured phi 5 digits xxx.xx
• I.SIN φ: Measured current x sinus phi 5 digits xxx.xx

Local HMI offers also all the needed maintenance Functions to facilitate the C264 with AVR
Commissioning and Maintenance (Visualization of input/outputs)
Local HMI offers facility to adjust the local date/Time (when not synchronized with an
external GPS Clock).
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
ON 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
NOTE: The “C” button is used for the navigation in the menu tree. This
feature remains and so alarm acknowledgement will be not allowed
from the menu tree.
The following figures show the menu tree in the three operating modes.
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 (EXAMPLE)

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 to change the bay mode:
• From local to remote
• From remote to local

If the computer manages several bays, the state local / remote of bays is set bay by bay.
Change of bay mode is enabled if a bay panel is defined. It means that, if a bay is not
associated to a bay panel, its local/remote control mode cannot be controlled through the
L/R button of the panel.
Local / Remote control of bay for simple panel with LEDs (GHU21x)
In case of simple panel, the operator controls all the bays of the computer in the same time.
To change mode, s/he has to press of the button during at least 3 seconds. No password is
necessary to check the control. The 5th LED is used to display the current mode. If all the
bays are NOT in the same state, the command switches them all too local mode.
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
• close a synchronised circuit breaker
• close with bypass on a synchronised circuit breaker (forcing closure), available only
when the DI “Accept Forcing is configured
The button allows to abort the choice in event of command on a close_synchrocheck.

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
To get access to the bypass flag modification panel, use the [ ENTER ] button
Set the interlocking bypass command before you send the execute order.
To send the bypass command, use the bypass flag on the interlocking equation.
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
Synchrocheck bypass
The operator can send the command using bypass flag on synchrocheck (forcing closure).
The S/C bypass flag is present when the “Accept Forcing” DI is configured. The S/C bypass
flag can be set before or after the execute order sending.
Operator accesses to the bypass flag modification panel by the enter button.
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
S / C 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 that the transformer belongs to has to be in
local mode.
The commands that can be sent through the local HMI are:
• Raise (= current tap position + 1) with the button

⇒ for a Double Wound transformer the Low Voltage is increased
⇒ for an Auto-wound transformer the Low Voltage is reduced
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

Control of the C264 with AVR and manual orders to the Tap Change are available from the
C264 with AVR local HMI with simple and intuitive actions on the animated “Single Line
Page”.
The operator controls:
• Commands on Single Line - View 1:
− AVR ON/OFF (by OI / SCADA)
− AVR AUTO/MANU (by OI / SCADA)
− Raise * (by front panel keys)
− Lower * (by front panel keys)
− Target Vn-5% (Target Voltage 5) (by OI / SCADA)
• Commands on LCD View 2:
− Target Voltage 1 (Nominal 100% Vn) (by OI / SCADA)
− Target Voltage 2 (Boosting Voltage 2) (by OI / SCADA)
− Target Voltage 5 (Vn-5% ) (by OI / SCADA)

* NOTE: Controls Raise and Lower use front panel keys for navigation:
Selection, Enter, Up and Down.
The Single Line “Page 1” is graphically showing the AVR Running Mode, CB status, Tap
Changer Position Indication and the Current Voltage.
2.2.13.5 Data base switch
MiCOM C264 Computer has 2 databases. The operator can switch between both databases.
The operator sends this command from the menu tree with a password protection.
2.2.13.6 Reset operating hours
The operator is allowed to reset the operating hours counter.
The operator sends this command from the menu tree with a password protection.
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 are used to select the digit of the wanted value that has to be
and
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, measurements, controls and alarms, the origin gives the
access path to the object (refer to § “SOE events”)
ObjectName - 16 characters
ObjectMessage - 16 characters
The Origin, ObjectName and ObjectMessage properties contain different information
depending of the associated event type.
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

MiCOM C264/C264C
APPLICATION
CONTENT
2. REQUIREMENTS 10
3. COMPUTER CONFIGURATION SCOPE 11

3.1 General PACiS system configuration 11
3.2 Computer configuration in general PACiS system configuration 11
3.3 Sparing object 12
4. DEFINING COMPUTER CONFIGURATION IN SYSTEM

ARCHITECTURE 13
4.1 Setting general system configuration relevant to computers 13
4.2 Adding a computer in the system architecture 16
4.3 Setting general attributes of a computer 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 computer internal fault characteristics 20
4.3.5 Locating computer in a substation (mandatory) 20
4.3.6 Configuration of SNTP Server 21
4.3.7 Defining a redundant computer (optional) 21
4.4 Adding computer hardware components 23
4.4.1 Adding boards 23
4.4.2 Setting specific attributes to computer boards 24
4.4.2.1 Setting common attributes to computer board 24
4.4.2.2 Setting specific features of the GHU2xx board 25
4.4.2.3 Setting attributes of a TMU220 board 27
4.4.3 Adding extra communication channels to CPU board 29
4.4.4 Configuring a communication channel 30
4.4.5 Configuring an AI channel 32
4.4.6 Adding a printer 33
4.4.7 Configuring an AO channel 36
4.5 C264 IP adress and routing table definition 37
4.5.1 C264 as a gateway connected to a router and a remote IEC104 Scada 37
4.5.2 C264 as a gateway directly connected to a remote DNP3 Scada 40
4.5.3 C264 as a gateway connect maximum of 4 DNP-IP SCADA Protocols 40
4.6 Networking computer on the station-bus network 42
4.6.1 Connecting computer to other station-bus sub-systems 42
4.6.2 Defining addressing mapping of station-bus network 44
4.6.2.1 SBUS automatic addressing 45
C264/EN AP/D10 Application
4.6.3 Addressing datapoint on station-bus network 60

4.6.4 Setting BRCB 60
4.7 Networking IED on computer legacy network 62
4.7.1 Creating a legacy network of IED 62
4.7.1.1 Adding a legacy network 62
4.7.1.2 Setting general attributes of a legacy network 62
4.7.1.3 Setting acquisitions attributes of a T103 legacy network 63
4.7.1.4 Setting acquisition attributes of a T101 legacy network 63
4.7.1.5 Setting acquisition attributes of a Modbus legacy network 64
4.7.1.6 Setting acquisition attributes of a DNP3 legacy network 65
4.7.1.7 Adding an IED to a legacy network 66
4.7.1.8 Setting attributes of a legacy IED 66
4.7.1.9 Adding an IED acquisition type to a legacy network 67
4.7.1.10 Setting attributes of a T103 acquisition type 68
4.7.1.11 Setting attributes of a MODBUS acquisition type 69
4.7.1.12 Setting attributes of a DNP3 acquisition type 70
4.7.2 Defining addressing mapping of a legacy IED 72
4.7.2.1 Defining an IED address for an SPS datapoint 73
4.7.2.2 Defining an IED address for a DPS datapoint 75
4.7.2.3 Defining an IED address for an MV datapoint 76
4.7.2.4 Defining an IED address for a Counter datapoint 81
4.7.2.5 Defining an IED address for an SPC datapoint 83
4.7.2.6 Defining an IED address for a DPC datapoint 85
4.7.2.7 Defining an IED address for a SetPoint datapoint 87
4.7.3 Addressing a datapoint on an IED legacy network 89
4.8 Networking SCADA on computer SCADA network 90
4.8.1 Creating a SCADA network 90
4.8.1.1 Adding a SCADA network 90
4.8.1.2 Setting general attributes of a SCADA network 91
4.8.1.3 Setting general attributes of a T101 SCADA network 91
4.8.1.4 Setting specific attributes of a T101 SCADA network 92
4.8.1.5 Setting general attributes of a DNP3 SCADA network 93
4.8.1.6 Setting specific attributes of a T104 SCADA network 95
4.8.1.7 Setting specific attributes of a MODBUS SCADA network 97
4.8.2 Defining addressing mapping of SCADA network 98
4.8.2.1 Defining a SCADA address for an SPS datapoint 98
4.8.2.2 Defining a SCADA address for a DPS datapoint 101
4.8.2.3 Defining a SCADA address for a MV datapoint 103
4.8.2.4 Defining a SCADA address for a Counter datapoint 105
4.8.2.5 Defining a SCADA address for a SPC datapoint 106
4.8.2.6 Defining a SCADA address for a DPC datapoint 108
4.8.2.7 Defining a SCADA address for a SetPoint datapoint 109
4.8.2.8 Defining a SCADA address for bypass synchrocheck 111

4.8.3 How to configure a mapping of a SCADA network 112
4.8.4 Addressing datapoint on SCADA legacy network 114
4.9 Defining wave record file management 115
4.9.1 Defining management of disturbance file for IED 115
4.9.2 Defining T103 IED extra information for disturbance file 116
4.9.2.1 Adding an analog channel definition 116
4.9.2.2 Adding a digital channel definition 117
4.9.3 Defining management of wave record file for computer CT/VT board 119
4.9.3.1 Defining fast waveform recording 120
4.9.3.2 Defining slow waveform recording 124
4.10 Defining a computer klaxon 128
4.11 Setting system information for computer components 129
4.11.1 Setting general system information of a computer 130
4.11.2 Setting system information of board 135
4.11.3 Setting system information of legacy IED 136
4.11.4 Setting system information of serial printer 137
4.11.5 Setting system information of a SCADA network 138
5. DEFINING DATAPOINT 139

5.1 Creating a datapoint 139
5.1.1 Overview of binary input processing 139
5.1.2 Defining an SPS datapoint 140
5.1.2.1 SPS processing 140
5.1.2.2 Creating an SPS datapoint 140
5.1.3 Defining a DPS datapoint 144
5.1.3.1 DPS processing 144
5.1.3.2 Creating a DPS datapoint 144
5.1.4 Defining an MPS datapoint 147
5.1.4.1 MPS processing 147
5.1.4.2 Creating an MPS datapoint 147
5.1.5 Overview of measurement processing 150
5.1.5.1 Analogue measurement acquisition 150
5.1.5.2 Adding an MV datapoint 151
5.1.5.3 Setting ‘General’ attributes of an MV datapoint 153
5.1.5.4 Setting ‘Value features’ attributes of an MV datapoint 154
5.1.5.5 Setting ‘Scaling’ attributes of an MV datapoint 154
5.1.6 Defining a TPI datapoint 156
5.1.6.1 Overview of Tap Position Indicator processing 156
5.1.6.2 Adding a TPI datapoint 156
5.1.6.3 Setting ‘General’ attributes of a TPI datapoint 157
5.1.6.4 Setting ‘Value features’ attributes of a TPI datapoint 157
5.1.6.5 Setting ‘Tap position’ attributes of a TPI datapoint 157
5.1.6.6 Setting ‘Scaling’ attributes of a TPI datapoint 158

5.1.7 Defining a Counter datapoint 159
5.1.7.1 Overview of counter processing 159
5.1.7.2 Adding a Counter datapoint 160
5.1.7.3 Setting ‘General’ attributes of a Counter datapoint 162
5.1.8 Overview of control sequence processing 164
5.1.9 Defining an SPC datapoint 164
5.1.9.1 Setting ‘General’ attributes of an SPC datapoint 166
5.1.9.2 Defining an SPC feedback 166
5.1.10 Defining a DPC datapoint 168
5.1.10.1 Setting ‘General’ attributes of a DPC datapoint 170
5.1.10.2 Defining a DPC feedback 171
5.1.11 Defining a SetPoint datapoint 172
5.1.11.1 Overview of SetPoint processing 172
5.1.11.2 Adding a SetPoint datapoint 174
5.1.11.3 Setting ‘General’ attributes of a SetPoint datapoint 176
5.1.11.4 Defining a SetPoint feedback 177
5.2 Linking a datapoint to a profile 178
5.2.1 Defining an SPS profile 180
5.2.1.1 Adding an SPS Profile 180
5.2.1.2 Setting ‘General’ attributes of an SPS Profile 180
5.2.1.3 Setting ‘State labels’ attributes of an SPS Profile 181
5.2.1.4 Setting ‘State treatment’ attributes of an SPS Profile 181
5.2.1.5 Setting ‘Alarms’ attributes of an SPS Profile 182
5.2.1.6 Setting ‘Interlocking’ attributes of an SPS Profile 183
5.2.2 Defining a DPS profile 184
5.2.2.1 Adding a DPS Profile 184
5.2.2.2 Setting ‘General’ attributes of a DPS Profile 185
5.2.2.3 Setting ‘State labels’ attributes of a DPS Profile 185
5.2.2.4 Setting ‘State treatment’ attributes of a DPS Profile 185
5.2.2.5 Setting ‘Alarms’ attributes of a DPS Profile 186
5.2.2.6 Setting ‘Interlocking’ attributes of a DPS Profile 188
5.2.3 Defining an MPS profile 188
5.2.3.1 Adding an MPS Profile 188
5.2.3.2 Setting ‘General’ attributes of an MPS Profile 189
5.2.3.3 Setting ‘State labels’ attributes of an MPS Profile 189
5.2.3.4 Setting ‘State treatment’ attributes of an MPS Profile 190
5.2.3.5 Setting ‘Alarms’ attributes of an MPS Profile 190
5.2.3.6 Setting ‘Interlocking’ attributes of an MPS Profile 191
5.2.4 Defining an MV profile 192
5.2.4.1 Adding an MV Profile 192
5.2.4.2 Setting ‘General’ attributes of an MV Profile 193
5.2.4.3 Setting ‘State labels’ attributes of an MV Profile 193

5.2.4.4 Setting ‘State treatment’ attributes of an MV Profile 193
5.2.4.5 Setting ‘Alarms’ attributes of an MV Profile 194
5.2.4.6 Setting ‘Interlocking’ attributes of an MV Profile 195
5.2.4.7 Setting ‘Mean value’ attributes of an MV Profile 195
5.2.5 Defining a Counter profile 196
5.2.5.1 Adding a Counter Profile 196
5.2.5.2 Setting ‘General’ attributes of a Counter Profile 197
5.2.5.3 Setting ‘State labels’ attributes of a Counter Profile 197
5.2.5.4 Setting ‘State treatment’ attributes of a Counter Profile 198
5.2.5.5 Setting ‘Alarms’ attributes of a Counter Profile 198
5.2.5.6 Setting ‘Mean value’ attributes of a Counter Profile 199
5.2.6 Defining an SPC profile 199
5.2.6.1 Adding an SPC Profile 199
5.2.6.2 Setting ‘General’ attributes of an SPC Profile 200
5.2.6.3 Setting ‘Order labels’ attributes of an SPC Profile 200
5.2.6.4 Setting ‘State treatment’ attribute of an SPC Profile 201
5.2.6.5 Setting ‘Alarms’ attributes of an SPC Profile 201
5.2.6.6 Setting ‘Interlocking and FBD’ attributes of an SPC Profile 202
5.2.7 Defining a DPC profile 202
5.2.7.1 Adding a DPC Profile 202
5.2.7.2 Setting ‘General’ attributes of a DPC Profile 203
5.2.7.3 Setting ‘Order labels’ attributes of a DPC Profile 203
5.2.7.4 Setting ‘State treatment’ attribute of a DPC Profile 204
5.2.7.5 Setting ‘Alarms’ attributes of a DPC Profile 204
5.2.7.6 Setting ‘Interlocking and FBD’ attributes of a DPC Profile 205
5.2.8 Defining a SetPoint profile 205
5.2.8.1 Adding a SetPoint Profile 205
5.2.8.2 Setting ‘General’ attributes of a SetPoint Profile 206
5.2.8.3 Setting ‘treatment on event’ attribute of a SetPoint Profile 207
5.3 Defining computer local archiving of datapoint events 209
5.4 Defining computer local archiving of datapoint alarms 209
5.5 Defining computer local logging of datapoint events and alarms 209
5.6 Defining acquisition source for input datapoints 210
5.6.1 Acquiring input datapoint via input channels 210
5.6.1.1 Wiring a SPS datapoint, via one DI channel 210
5.6.1.2 Wiring a DPS datapoint via two DI channels 211
5.6.1.3 Wiring a MPS datapoint via n DI channels 212
5.6.1.4 Wiring MV and TPI datapoint 212
5.6.1.5 Wiring a Counter datapoint 213
5.6.2 Acquiring input datapoint via an IED legacy network 214
5.6.3 Acquiring input datapoint via non-PACiS IEC61850 communicant IED 215
5.6.4 Producing input datapoint 216

5.6.4.1 Implicit system input datapoint via system decomposition 216
5.6.4.2 Implicit electrical input datapoint via built-in function 216
5.6.4.3 Defining an ISaGRAF slow automation 216
5.6.4.4 Explicit electrical input datapoint via CT/VT computation 217
5.7 Defining control source for output datapoints 218
5.7.1 Controlling output datapoint via output channels 218
5.7.1.1 Wiring a SPC datapoint via one DO channel 218
5.7.1.2 Wiring DPC datapoint via two or four DO channels 218
5.7.1.3 Wiring SetPoint datapoint 219
5.7.1.4 Wiring from CCU datapoint 220
5.7.2 Controlling output datapoint via an IED legacy network 221
5.7.3 Controlling output datapoint via non-PACiS IEC61850 communicant IED 222
5.7.4 Producing output datapoint 223
5.7.4.1 Implicit system output datapoint via system decomposition 223
5.7.4.2 Implicit electrical output datapoint via built-in function 223
5.7.4.3 Defining an ISaGRAF slow automation 223
5.7.5 Acknowledgement definition in case of simultaneous orders 223
5.8 Defining datapoint association 224
5.8.1 Adding a target datapoint 224
5.8.2 Linking the target datapoint to the original datapoint 225
5.8.3 Defining the states associations 226
6. DEFINING COMPUTER CONFIGURATION IN

ELECTRICAL ARCHITECTURE 227
6.1 Defining an electrical topology 227
6.1.1 Defining a Site 229
6.1.2 Defining a Substation 229
6.1.2.1 Adding a substation generic datapoint 230
6.1.2.2 Defining Local/Remote for substation 231
6.1.2.3 Defining Taking Control for substation and SCADA links 232
6.1.2.4 Adding a user function to a substation 233
6.1.3 Defining a Voltage level 234
6.1.3.1 Adding voltage level generic datapoint 235
6.1.3.2 Adding user function to voltage level 235
6.1.4 Defining a Bay 236
6.1.4.1 Adding bay generic datapoint 238
6.1.4.2 Defining Local/Remote for bay 238
6.1.4.3 Defining SBMC for bay 240
6.1.4.4 Adding a user function to a bay 241
6.1.5 Defining Module 241
6.1.5.1 Adding a module generic datapoint 243
6.1.5.2 Adding a user function to a module 244
6.1.5.3 Defining a lockable module 244

6.1.5.4 Defining withdrawable circuit-breaker or switchgear 245
6.1.5.5 Defining a circuit-breaker 246
6.1.5.8 Defining a transformer 252
6.2 Defining a Synchrocheck function 255
6.2.1 Completing circuit-breaker definition for synchrocheck 255
6.2.2 External synchrocheck behaviour 259
6.2.3 Internal synchrocheck behaviour 259
6.2.4 Automation description of internal synchrocheck 259
6.2.5 Creating a synchrocheck function 262
6.2.5.1 Setting default settings of internal synchrocheck 264
6.2.5.2 Adding synchrocheck specific datapoints 266
6.3 Defining an Auto-recloser built-in function 268
6.3.1 Auto-recloser behaviour 268
6.3.2 Creating an auto-recloser function 268
6.4 Defining a Tap changer built-in function 277
6.4.1 Tap changer behaviour 277
6.4.2 Creating a tap changer built-in function 278
6.5 Defining an automatic voltage regulation–AVR built-in function 280
6.5.1 Creating an AVR function 280
6.5.2 AVR behaviour 285
6.6 Defining an automatic voltage regulation–ATCC built-in function 286
6.6.1 ATCC behaviour 286
6.6.2 Creating an ATCC function 286
6.6.2.1 Defining ATCC function needs at substation level 286
6.6.2.2 Defining ATCC function needs at voltage level 289
6.6.2.3 Defining ATCC function needs at busbar level 290
6.6.2.4 Defining ATCC function needs at transformer level 292
6.6.2.5 Defining an electrical topology for ATCC function 294
6.7 Defining an electrical regulation by user function 297
6.7.1 Defining an FBD fast automation 297
6.7.1.1 Creating an FBD fast automation (header definition) 297
6.7.1.2 Creating FBD input plug (header definition) 299
6.7.1.3 Creating FBD output plug (header definition) 299
6.7.1.4 Using FBD editor (body definition) 300
6.7.1.5 Linking datapoints to FBD inputs and outputs 301
6.7.1.6 Creating FBD timer plugs 303
6.7.2 Defining an ISaGRAF slow automation 304
6.7.2.1 Creating an ISaGRAF slow automation (header definition) 305
6.7.2.2 Adding specific datapoints to slow automation (interface definition) 306
6.7.2.3 Creating ISaGRAF client link (interface definition) 307
6.7.2.4 Linking a datapoint to an ISAGRAF client link 308
6.7.3 Defining a group 312

6.7.4 Controlling xPC by xPS change of state 314
6.7.5 Producing a DPS from two SPSs 315
6.7.6 Defining interlocking 315
6.7.7 Defining an automatic/manual dependency 317
6.8 Defining a Fast Load Shedding application 318
6.8.1 Data flow 318
6.8.2 Priority Setpoints 319
6.8.3 Load Shedding Preselection (LSP) 319
6.8.4 Graphical animation with LSP 321
6.8.5 Use of LSP in PSL 321
6.8.6 Use of LSP in ISaGRAF scheme 322
6.8.7 Datapoints 323
6.8.8 MASK object and xPS triggers 323
6.8.9 Topology calculation 325
6.8.10 Operator Interface example 326
6.9 Defining a Load application (C264 standalone RTU) 327
7. DEFINING COMPUTER LOCAL HMI 329

7.1 Defining a bitmap table 329
7.2 Defining a computer workspace 332
7.2.1 Settings LHMI labels 332
7.2.2 Creating a workspace 333
7.3 Defining a computer bay mimic 334
7.3.1 Creating a computer bay mimic 334
7.3.2 Defining static part: line, bitmap, fixed text 337
7.3.2.1 Adding a line 337
7.3.2.2 Adding a bitmap 338
7.3.2.3 Adding a fixed text 339
7.3.3 Defining dynamic part: pre-defined dynamic text, generic module representation,
transformer representation 340
7.3.3.1 Adding time information 341
7.3.3.2 Positioning Local/Remote status, Synchrocheck bypass or Interlock bypass 342
7.3.3.3 Adding SBMC information 342
7.3.3.4 Adding a generic module representation 343
7.3.3.5 Adding a transformer representation 345
7.3.4 Assigning MV to bay mimic 347
7.4 Displaying datapoint status with Led 348

The present document is a MiCOM C264/C264C section of the documentation binder. This
document is intended to present you how to configure the Computer. 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 computer C264.
To add an IEC-61850 computer 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 computer, see the chapter Functional
Description of the SCE product.
3. COMPUTER 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 (computer 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 Computer configuration in general PACiS system configuration

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

used for communication at station bus level.
− Electrical topology (Site): computer manages bays and relevant modules or substation
information.
− Graphical topology (Graphic): computer 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 computer
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 COMPUTER CONFIGURATION IN SYSTEM ARCHITECTURE

4.1 Setting general system configuration relevant to computers
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 computer(s) in the system. Up to two computers can
be declared as System Master Clock. A System Master Clock computer gives the time
reference to all others devices connected to the station-bus network through SNTP
(Simple Network Time Protocol). A System Master Clock computer is always located
in a substation.
− Designation of elementary action rights by default used by system datapoints of the

SCS tree.
− Designation of the substation where the system devices are located.

Some attributes of SCS objects concern all the computers defined under the station network.
Hereafter, are listed these attributes:
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. Default board labels and status.
5. Control acknowledgement labels used for order logging.
FIGURE 2: GENERAL AND LABELS ATTRIBUTES OF SCS

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

FIGURE 4: ALARM ATTRIBUTES OF SCS

Gi (1≤i<:5) default alarm clearing mode (Manual / Automatic)
At computer level, default alarm processing type is not significant, because alarm processing
is always ‘data basis’ for computer.
Audibility features are not applicable to computer configuration.
FIGURE 5: COMPUTER ROUTING ATTRIBUTES OF SCS

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

Please refer to the “C264 IP address and routing table” paragraph for details.
4.2 Adding a computer in the system architecture

The addition of a computer 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 COMPUTER IN THE SYSTEM ARCHITECTURE

Default components of computer
When you add from the “Objects Entry” window, for example a C264 computer, you will
obtain the following sub-tree of the computer definition with the default components as
follows:
FIGURE 7: DEFAULT COMPONENTS OF THE COMPUTER

1. Binder ‘Hardware’, that groups all defined boards and printers of the computer.
2. Binder ‘System infos’, that groups all general system datapoints of the computer.
3. ‘PLC’ object for Programming Logic Chart that corresponds to ISaGRAF and PSL
project directory.
4.3 Setting general attributes of a computer

When adding a computer on the Ethernet network, some of its attributes must be set and
verified. Hereafter are listed these attributes.
FIGURE 8: GENERAL ATTRIBUTES OF A COMPUTER

1. short name and long name: used for logging, alarms, …
2. rack model (80 TE / 60 TE / 40 TE): there exist three models of computers: C264,
C264M and C264C. The C264 is a large size computer (80TE), the medium one is
C264M (60TE) and C264C is the compact one (40TE). The height of both computers
is 4U.
3. date format: this attribute defines the date format used in the computer HMI (LCD).
4. Timer for SCDA GI (ms): timer delay between to ASDU frames
5. Timestamped ‘unknown‘ for SCADA: Yes/No
6. synchronisation source (None / IRIG-B): indicates if the computer is synchronized
through IRIG-B. The relation at SCS level “has for master clock” defines which device
is the master clock in the system. A master clock computer is necessary synchronized
through IRIG-B.
7. TCP/IP address and network name (limited to 15 characters) of the computer.
8. Define the board defination.
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 20 ms (with a 1 ms 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 20 ms (with a 1 ms 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.
FIGURE 10: SETTING BI ACQUISITION ATTRIBUTES

1. debouncing delay (range [0, 20 ms], step 1 ms).
2. filtering delay (range [0,.20 ms], step 1 ms.
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
FIGURE 11: MEASUREMENTS VALUES ATTRIBUTES FOR A COMPUTER

1. Debouncing delay and filtering delay: used for digital measurements.
2. Analogue measurements acquired on AIU board: acquisition samples ranges for long
scanning (range [500 ms, 10000 ms], step 500 ms) and short scanning (range [100
ms, 1000 ms], step 100 ms). For each channel of AIU board, short or long scan period
should be chosen (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,.60 s],step 100 ms) 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
FIGURE 12: COUNTER ACQUISITION ATTRIBUTES OF A COMPUTER

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

1. Number of software faults allowed in a given period else the computer remains in
HALT mode. Computer reboots automatically as long as it does not reach the ‘fault
max number’ in the ‘fault detection time’ period. When this critera is reached computer
remains in HALT mode.
4.3.5 Locating computer in a substation (mandatory)
As said in section 4.1 (Setting general system configuration relevant to computers), each
system device has to be located in a specific substation. This is done by defining the
mandatory relation (1) “is located in:“ for each system device, especially computers.
FIGURE 14: LOCATING COMPUTER IN A SUBSTATION

4.3.6 Configuration of SNTP Server

As said in section 4.1 (Setting general system configuration relevant to computers), up to two
computers can be master clock for the system. I.This is done by defining TCP/IP address of
main master and TCP/IP of auxillary C264. These configurations define in SCS attributes. In
the below figure, C264 having IP address 192.168.0.10 (TCP/IP address ) acts as main
source of system synchronization and C264 having IP address 192.168.0.12 (auxillary
TCP/IP address ) acts as secondary source of system synchronization in case of a main
C264 failure.
1. Main C264 acts as master clock.
2. Auxillary C264 acts as master clock in case of a main C264 failure.
FIGURE 15: SNTP CONFIGURATION

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

relation of backup between the two computers.
• Extra relation ‘has for IEC server’ is automatically created for the main computer.
• Once the backup computer has been created, its attributes and constitution are locked
for updating and follow the main computer ones. The only exceptions are its short
name and long name and network identification (IP address and network name) that
must be correctly updated. When an object is added to (resp. removed from ) the main
computer the same object is added to (resp. removed from) the backup computer but
attributes cannot be modified.
FIGURE 16: DEFINING A REDUNDANT COMPUTER (CREATION ACTION)
FIGURE 17: DEFINING A REDUNDANT COMPUTER (ONCE CREATED)

To assign a C264-Standalone a redundant computer, just set its attribute “number of
masters” to 2.
Such a C264-Standalone can’t manage ISaGRAF or PSL functions. A check controls that
there is no inconsistency about this.
The wiring report generates a mapping by available racks (main and extension) if applicable.
When the main rack of a C264-Standalone is assigned a redundant computer, the mapping
is generated a second time with name suffixed by “#master 2”.
4.4 Adding computer hardware components

4.4.1 Adding boards
PACiS computers are composed of boards, responding to specific functions:
• DIU200-211 - Digital input boards with 16 digital input channels:

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

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

- analogue measurement acquisition
• TMU210/TMU220 - CT and VT input boards with 4 CT and 4 VT input channels (5 VT

inputs on TMU220):
- CT/VT sampling acquisition,
- MV computations based on acquired samples
• DOU201 - Digital output boards with 10 digital output channels:

- execution of single or dual, transient or permanent commands
- setting of digital setpoints
• CCU2xx - Mixed digital 8 input and 4 output boards with digital input and output
channels (take good care that the DO 4,5,6,7 are defined but not used):
- Circuit breaker Control Unit
• CPU260, CPU270 - CPU boards with communication channels (1*Ethernet on

CPU260, 2 Ethernet on CPU270 and serial communication ports)
• BIU241/BIU261 - Power Supply board with communication channel(s) (serial

communication port(s))
• GHU200 - Graphical panel boards with led channels
• 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 corresponds to datapoint wiring.
The addition of a board definition is done via the “Objects entry” window by clicking on
mouse’s right button as the following:
FIGURE 18: ADDING A BOARD TO THE COMPUTER


Slots and boards in a C264 computer
A B C D E F G H I J K L M N O P Q
BIU CPU
• Slots from C to P may contain a board of the following types: AIU201, AIU211,
AOU200, DOU201, DIU20x, DIU211 or CCU2xx
• Slot Q may contain one board of the above types.
• If a TMU220 is present, then the maximum count of boards must be ≤ 14; else the
maximum count of boards must be ≤ 15.
• If present the Ethernet boards (SWU20x, SWR2xx, SWD2xx) are to be installed in

slots C or D.
Slots and boards in a C264C computer
A B C D E F G H
BIU CPU
• Slots from C to F may contain a board of the following types: AIU201, AIU211,
AOU200, DOU201, DIU20x, DIU211 or CCU2xx
• Slots G and H may contain one board or two boards of the above types.
• The maximum count of boards must be ≤ 6.
• If present the Ethernet boards (SWU20x, SWR2xx, SWD2xx) are to be installed in

slots C or D.
• A C264 is able to manage up to 4 AOU boards and the AOU board cannot be used in
a C264 redundant environment
4.4.2 Setting specific attributes to computer boards
4.4.2.1 Setting common attributes to computer board
For each board of the computer the short name attribute (1) may be updated for correct
logging and alarm discrimination concerning board status datapoint.
For boards AIU2xx, CCU2xx, DIU2x0, DIU211, DOU200, DOU201, AOU200 the physical
board number attribute (2) must be updated.
For boards CPU260, BIU241/BIU261, GHU200, TMU2x0 this attribute is forced to 0 by the
SCE and is not displayed in the attributes window.
FIGURE 19: GENERAL ATTRIBUTES OF A BOARD

• Per board type (AIU201, AIU210/AIU211, DOU200, DOU201, DIU20x, CCU2xx), the
physical board number attribute values must begin from 0, be unique and
contiguous.
4.4.2.2 Setting specific features of the GHU2xx board
• the attribute HMI type has to be set to:
− Simple if GHU 210/220 is used (no LCD)
− Complete if GHU 200 is used (with LCD)
• the default start panel can be bay, defaults, AVR, service, banner; it must be set to
banner if the attribute Login panel present is set to Yes
• the attribute Login panel present is set to Yes (Login panel shows after the banner)
or No
• the banner must include at least 32 characters (10 char per line at most):
FIGURE 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 attributes of a TMU220 board

For TMU220 board, the following attributes have to be set for correct CT/VT computation of
extra measurements:
1. short name
2. electrical network topology (Star / Delta).
3. reference phase (Phase A / Phase B / Phase C).
4. reference phase side (Phase A, B, C wired line side / Phase A, B, C wired busbar
side).
5. power flow mode: Mode1, Mode2, Mode3, Mode 4
6. nominal current
7. nominal voltage.
8. period No. to compute harmonic
9. period No. to compute energy
10. voltage ref change mode:
• Default voltage reference: as soon as the stated reference phase is valid again,
the TMU locks onto it.
• Current voltage reference: the TMU stays locked onto the phase that has a valid
signal.
11. meas quality when missing (value=0; quality=VALID/ quality=FAULTY)
• Unknown: When there is no signal on the TMU, the C264 returns the value
0/self-Check fault on the network: IEC, HMI, Gateway….
• Value 0: When there is no signal on the TMU, the C264 returns the value 0 /
Valid on the network: IEC, HMI, Gateway….
During the synchronisation of the TMU frequency, set the related measurement values to 0
/self-Check fault. Do not set the related measurement values to 0 / Valid.
If reference phase signal is absent, values transmitted by TMU board are set to invalid.
Extra attributes are reserved for future use. TMU220 board has the same attributes as
TMU200 except that it has an additional attribute “physical board number” which is set to “0”
by default.
FIGURE 22 TMU200/220 BOARD SPECIFIC ATTRIBUTES

Please refer to the Chapter CO (Connections) for the description of the TMU2xx electrical
CT/VT inputs and database association.
4.4.2.4 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 23 TMU210 BOARD SPECIFIC ATTRIBUTES

If reference phase signal is absent, values transmitted by TMU210 board are set to invalid.
Please refer to the Chapter CO (Connections) for the description of the TMU210 electrical
CT/VT inputs and database association.
4.4.2.5 Setting specific features of BIU241/BIU261 board
The BIU board type is choiced from BIU attributes
FIGURE 24: 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 25: 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 CPU270 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 26: 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 or manually added as option.
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.
FIGURE 27: USAGE OF COMMUNICATION CHANNEL

Once used by a communication link, the physical port has to be set relatively to the
communication link characteristics:
1. RS type (RS232 / RS485).
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 rates 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 computer has to send a frame it sets the RTS line and
waits for the CTS line to be set by the receiver. It then waits during a time
defined by attribute (9) before starting the transmission of the frame. At the end
of the transmission the computer waits during a time defined by attribute (10)
before resetting the RTS line
− Constant: the RTS line is always set by the computer. When it has to send a
frame it waits for the CTS line to be set by the receiver to start the transmission.
− Soft: the RTS and CTS line are not managed by the computer.
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 computer this
attribute must be set to YES if the TX carrier management parameter is set to
Switched.
9. pre TX time (range [0, 1 s], step 1 ms): this attribute is visible and therefore significant
only if attribute (6) is set to Switched.
10. post TX time (range [0, 1 s], step 1 ms): this attribute is visible and therefore significant
only if attribute (6) is set to Switched.
FIGURE 28: 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 AIU21x boards at their creation.
AI channels are used for analogue measurement acquisition.
FIGURE 29: 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 AIU210/AIU211: -20 mA …+20 mA / -10 mA …+10 mA / -5 mA
+5 mA / -1 mA …+1 mA / 0 mA …+1 mA / 0 mA …+5 mA / 0 mA …+10 mA / 0 mA
+20 mA / 4 mA …+20 mA
2. acquisition period (short period / long period): refer to section 4.3.2 Configuring
measurement acquisition and transmission.
FIGURE 30: 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 computer level.
A printer at computer level must be a serial one connected to a communication channel of
the computer.
To create a computer printer:
• Add a serial printer from object entry available at computer level.
FIGURE 31: 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 32: 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:
FIGURE 33: THE DIFFERENT COLUMNS USED FOR PRINTING FORMATS

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

4.4.7 Configuring an AO channel

An AO channel is an analogue output available on AOU200 at their creation in SCE.
FIGURE 34: USAGES OF AO CHANNELS

The AO channel has following attributes:
1. Output current maintained mode: yes or 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
FIGURE 35: SHOW ATTRIBUTES OF AO CHANNELS

4.5 C264 IP adress and routing table definition

You’ll find hereafter example of C264 adressing and routing table definition in two typical
C264 application cases.
4.5.1 C264 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
FIGURE 36: C264 CONNECTED TO A SCADA VIA A ROUTER

4.5.1.1 C264 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.
FIGURE 37: ATTRIBUTES OF Scs
NOTE: “Gateway TCP/IP address” is not linked to the C264’s gateway

functionality.
“Target TCP/IP address” a network but it can be a target.
Example: We can replace 192.168.30.0 by 192.168.30.2. In this case only the IP on

192.168.30.2 can be replied by 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:
FIGURE 38: T104 CONFIGURATION
4.5.1.3 C264 IP adress definition

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

In the example the C264 have address 192.168.20.1 and subnet mask 255.255.255.0
(default value) he is able to reach all equipment with address 192.168.30.x.
4.5.1.4 C264 IP Parameters with the maintenance CMT tool
FIGURE 39: 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 board and activate IP
routing thanks to a registry key.
In a registry editor, navigate to
HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\Tcpip \Parameters
Select the "IPEnableRouter" entry (by defining as value: 1):
FIGURE 40: REGISTRY EDITION

To enable IP routing for all network connections installed and used by this computer, assign
a value of 1.
This will be taken into account after rebooting computer.
4.5.1.6 PC configuration when using the C264 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: C264 IS DESIGNED FOR FIXED IP ADRESS NETWORK: IP ADRESSING
CONFLICTS COULD BE MET WITH THE C264 INSTALLED ON
NETWORKS WITH DHCP ADRESSING.
4.5.2 C264 as a gateway directly connected to a remote DNP3 Scada
FIGURE 41: C264 CONNECTED TO A 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, C264 must have address 192.168.20.1 and SubNetwork mask must be set
to 255.255.0.0; it will accept connection from SCADA 192.168.30.4
4.5.3 C264 as a gateway connect maximum of 4 DNP-IP SCADA Protocols
FIGURE 42: C264 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 43: DEFINING DNP-IP CONFIGURATION WITH 4 SCADA DNP-IP

4.6 Networking computer on the station-bus network

Computer connection to the station-bus is implicitly done by adding the computer
hierarchically to the Ethernet network (see section 4.2 Adding a computer in the system
architecture) and by setting the IP characteristic of the computer (see 4.3 Setting general
attributes of a computer).
4.6.1 Connecting computer to other 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 computer, 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 computer (A) to a specific IEC-61850 communicant sub-system (B) on the
station-bus, an extra relation ‘has for IEC61850 server’ must be created for (A) and point to
(B). That means computer (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 44: CONNECTING COMPUTER TO OTHERS STATION-BUS SUB-SYSTEMS
FIGURE 45: COMPUTER (A) AS IEC61850 CLIENT OF COMPUTER (B)

When adding the ‘has for IEC61850 server’ relation to computer (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 computer (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 computer (A) uses BIs served by computer (B), for
ISaGRAF, FBD or interlock computation (refer to section 6.7 Defining an electrical regulation
by user function).
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 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)
• the time stamping (in GMT time) and time quality
• the reason for change, which could be one of the below values:
− 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 computer 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
JAMMED 00
UNDEFINED, TOGGLING, SELFCHECK FAULTY, 11
SUPPRESSED, UNKNOWN
A measurement can be configured to be transmitted in GOOSE mode as well (refer to

chapter C264/EN FT).
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 computer to other 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 computer 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 computer. 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 computer. Generally,
there is one logical device for each bay managed by the computer, 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 computer is to run “SBUS automatic addressing function” for the computer. The contextual
menu (mouse right click) of the computer (1) can launch this function.
FIGURE 46: SBUS AUTOMATIC ADDRESSING

NOTE: Only no-Spare datapoints are taken into account in automatic
addressing. If a datapoint is not spared anymore 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 a computer IEC61850 mapping
In LD0 of a PACiS computer, the fixed part is composed of the following bricks:
• DBID (DataBase IDentity) used for computer databases identification and

management,
• DI (Device Identity) used for computer identification,
• GLOBE used computer mode management,
• C26xDIAG brick.
FIGURE 47: STANDARD LD0 EXTENSION FOR C264 (SCE)

The LD0 can be completed with extra DIAG bricks, relative to some optional components of
the computer. 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 computer 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 computer legacy network, its IEDDIAG brick
name must be updated to avoid double values of bricks in the computer LD0.
LD0 extension optional RDRE

for IED brick for IED
C0172ENa
FIGURE 48: LD0 EXTENSION FOR IED
• For each SCADA network connected to a PACiS computer, an implicit TCIDIAG

(diagnostic for the SCADA network) brick exists.
Be careful, when creating a SCADA network on a computer, its TCIDIAG brick name
must be updated to avoid double values of bricks in the computer LD0.
LD0 extension for

SCADA network
C0173ENa
FIGURE 49: LD0 EXTENSION FOR SCADA NETWORK (STANDALONE CONFIGURATION)
• An extra brick RDRE (for disturbance information) can be added in LD0 of the
computer if it manages its own disturbance file.
optional
standard LD0 RDRE brick
for computer for computer
C0174ENa
FIGURE 50: LD0 EXTENSION FOR MiCOM C264

• C26xDIAG brick:
Object name CDC Description Comment

Mod INC Device Mode (status only) Mandatory
Beh INS Behaviour Mandatory
Health INS Health Mandatory
NamPlt LPL Name plate Mandatory
SyncSt SPS Device Synchronisation status stVal =0= non-synchronised
stVal =1= synchronised
AllBIUSt SPS All boards (BIU20x) synthetic status
AllCCUSt SPS All boards (CCU20x) synthetic status
AllDIUSt SPS All boards (DIU20x) synthetic status
AllDOUSt SPS All boards (DOU20x) synthetic status
AllAIUSt SPS All boards (AIU20x) synthetic status
AllAOUSt SPS All boards (AOU20x) synthetic status
AllCOMMSt SPS All rack synthetic status
AllIEDSt SPS All IED synthetic status
GHUSt INS Local HMI (GHU200) Status stVal =0= OK
stVal =1= self-check failure
(INS8_ST) stVal =2= configured but missing
stVal =3= not configured but present
stVal =4 = missing
BIUSt INS (INS8_ST) BIU240 status Idem GHUSt
CCUSt<15> INS (INS8_ST) I/O board (CCU20x) status Idem GHUSt
DIStop SPS Digital input acquisition stopped
DIUSt<15> INS (INS8_ST) DI board (DIU20x) status Idem GHUSt
DOUSt<15> INS (INS8_ST) DO board (DOU20x) status Idem GHUSt
AIUSt<6> INS (INS8_ST) AI board (AIU200) status Idem GHUSt
AOUSt<4> INS (INS8_ST) AO board (AOU) status Idem GHUSt
TMUSt INS (INS8_ST) CT/VT board (TMU) status Idem GHUSt
PrintSt INS (INS8_ST) Printer Status stVal = 0 => OK
stVal = ???
RedSt SPS Redundancy Mode stVal = 0 => StandBy
stVal = 1 => Active
FailSt INS (INS8_ST) Failure Status
PLCSt INS (INS8_ST) PLC Status
urcbST URCB Basic report control block for status Unbuffered
• C26xEDIAG brick for extension computers:
Object name CDC Description Comment

Mod INC Device Mode (status only) Mandatory
Beh INS Behaviour Mandatory
Health INS Health Mandatory
NamPlt LPL Name plate Mandatory
BIUSt INS BIU 240 status stVal =0= OK
(INS8_ST) stVal =1= self-check failure
stVal =2= configured but missing
stVal =3= not configured but present
stVal =4 = missing
CCUSt<15> INS (INS8_ST) I/O board (CCU 20x) status Idem GHUSt
DIStop SPS Digital input acquisition stopped
DIUSt<15> INS (INS8_ST) DI board (DIU 20x) status Idem GHUSt
DOUSt<15> INS (INS8_ST) DO board (DOU 20x) status Idem GHUSt
AIUSt<6> INS (INS8_ST) AI board (AIU 200) status Idem GHUSt
AOUSt<4> INS (INS8_ST) AO board (AOU) status Idem GHUSt
TMUSt INS (INS8_ST) CT/VT board (TMU 200) status Not managed.
CommIRSt SPS Communication status with the stVal = 0 => failure
extension rack stVal = 1 => OK
PLCSt INS (INS8_ST) PLC Status
urcbST URCB Basic report control block for status Unbuffered
FIGURE 51: SYSTEM FOR MICOM C264 WITH HARDWARE EXTENSION (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, control
popup),
− 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),
− Waveform file storing.
• At PACiS computer 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 computer to other station-bus sub-systems). PACiS MiCOM C264 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 C264,
• 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 52: ADDING AN APPLICATION LOGICAL DEVICE
(1)
FIGURE 53: 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 54: ADDING AN IEC61850 LOGICAL NODE
(1)
FIGURE 55: 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 upper case 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 C264 IEC61850 brick level. For MiCOM C264, useful
functional components are:
• ST to group statuses (SI, SIT, SIG),
• CO to group controls,
• MX to group measurements (MV),
• SV to group setpoints,
• CF to group configuration information relevant to CO or SP data objects.
FIGURE 56: 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 C264 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 57: ADDING AN IEC61850 DATA OBJECT
(1)
FIGURE 58: 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 C264: CO, MX and ST, the
maximum count of Data Objects is 50.
4.6.2.4 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 COMPUTER CONFIGURATION IN ELECTRICAL ARCHITECTURE).
The easiest way to create application logical devices relevant to electrical bays managed by
a MiCOM C264, is to run IEC61850 automatic addressing function for the protection. The
contextual menu of the MiCOM C264 IEC61850 mapping (1) can launch this function.
IEC61850 automatic addressing for a given MiCOM C264 concerns only the bays and ATCC
function it manages, i.e. whose relation ‘is managed by’ has been filled to the MiCOM C264.
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 results 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, then fast automation datapoints are
processed and finally slow automation datapoints. An event of GOOSE buffer overflow is
signalled and stops the process of GOOSE addressing. For details about Goose modelling /
configuration see further).
(1)
FIGURE 59: IEC61850 AUTOMATIC ADDRESSING

4.6.2.5 Configuring goose manually
Goose is a means 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 ST / MX data objects are goose-able (in
addition to these are the LSPs used in fast load shedding). Goose is attached to and
managed by the IEC61850 server of the goosed data objects.
Goose configuration is done at the data object level via specific attributes:
• Goose transmission (Auto) (Yes/No): indicates if the data object is transmitted by

goose and automatically addressed or not (this flag, raised to Yes by the SBUS auto-
addressing process, can be changed afterwards).
• Goose transmission (Manu) (Yes/No): specifies if the mapping is manual or not:
(1)
FIGURE 60: CONFIGURING GOOSE MANUALLY

4.6.2.6 Ranking goose manually
In addition to these two goose transmission attributes, the Goose rank is used to modify
manually the position of Data Object in the Goose messages.
FIGURE 61: GOOSE RANK

Suppose you have generated the database 1.0 for IED1 only. After adding IED2, you
generate a version 1.1.
SBUS IEC61850
n o
In regular text is the IED1: IED2:
Goose ST message: content of the goose
<DATASET>
ST message At IED configuration time
<FCDA Î SPS1.stVal> At IED2 configuration time
broadcast over - import the C264 SCL file - import the C264 SCL file -
<FCDA Î SPS1.q>
IEC61850 with the - assign assign
<FCDA Î SPS2.stVal>
C264 database 1.0 Index1 to SPS1.stVal 1 Index 3 to SPS2.stVal
<FCDA Î SPS2.q>
<FCDA Î SPS3.stVal> In bolded text is the Index3 to SPS1.stVal 3
<FCDA Î SPS3.q> modification of the
goose ST message IED1 uses Index 1 & Index 3 IED2 uses Index 3 as an input
broadcast over as inputs to one of the PSLs to one of the PSLs
IEC61850 with the
C264 C264 database 1.1 r
q
SPS1 SPS2 SPS3
sent as sent as sent as
goose goose goose
to
IED1
to
IED2
to
IED1
s
The Index 3 previously pointing to stVal of
SPS3 is now pointing to stVal of SPS2,
which obviously changes the behavior of
the IED1 PSL. Modify the goose rank to
m
SPS1, SPS2 and SPS3 configured in change it.
database version 1.0 but only SPS1 and
SPS3 are sent by goose to IED1 in
database version 1.0.
In database 1.1 SPS2 is then sent as goose

to IED2 added in the database
p
FIGURE 62: GOOSE RANK PROBLEM

To resolve the conflict, change the position of SPS1.stVal3.
The aim is to have goose messages from C264 with new DataObject (DtObj) at the end of
the messages to keep the rank of the other DtObjs inside the goose messages.
The attribute is set to 0 by default. This value indicates that the position is undefined. You
can modify this attribute to the desired rank.
When the SCE auto-addresses all subsystems, these events occur for each DtObj:
• The defined 'goose rank' is not updated if the DtObj is still 'transmitted by goose' (that
is either ‘goose transmission’ attribute is set to Yes),
• The undefined 'goose rank' is ranked after the last used rank for the whole 61850
mapping,
• The defined 'goose rank' is reset with an undefined value (0) if the DtObj’s is NOT
'transmitted by goose'.
If gaps show in the goose ranking, the pop-up message shows:
In this event, do a check of the configuration and fix it manually (see the SCE/ EN MF
chapter).
NOTE: The SBUS Automatic addressing dialog box features a box, which is
useful when goose links of some data objects have been removed.
You can check the box ‘reset of goose rank' to forcefully reset ALL of the Goose ranks of
61850 mapping at the current level in the treelike structure: they are reset with an undefined
value (as they are not goosed anymore) & all the remaining goose ranks are re-computed in
a new order.
Typical update cycle of data objects:
4.6.3 Addressing datapoint on station-bus network

For details about datapoint, refer to chapter 6.
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:
(1)
FIGURE 63: 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 C264 level,
− automatic linking between data objects in this IEC61850 mapping and datapoints
managed by the MiCOM C264.
4.6.4 Setting BRCB
4.6.4.1 Setting C264 BRCB server
C264 computer provides BRCB (buffered report) to PACiS device clients. A device client is
either HMI (OI / SUI) or IEC/IEC Gateway connected on IEC 61850 SBUS. Total BRCB
client is limited to 4.
4.6.4.2 Setting Device BRCB client

IHM (OI / SUI) or Gateway can become a client to BRCB server (buffered report). A BRCB
server is a C264 connected on IEC 61850 SBUS.
4.7 Networking IED on computer 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 computer as master.
At SCE data modelling level, up to four IED legacy networks (relevant to a specific protocol)
can be located under a PACiS computer C264 or C264C. Each IED legacy network has to
be linked to communication port embedded in computer boards. Up to sixteen IEDs can be
added under a legacy network.
4.7.1.1 Adding a legacy network

To create a legacy network on a computer:
• Add a legacy network relevant to a specific protocol from object entry available at
computer level (1),
• Update the legacy network attributes relevant to its protocol characteristics,
• Update its ‘has for main comm. port’ relation and the communication port
characteristics (see section 4.4.4 Configuring a communication channel),
FIGURE 64: 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.
FIGURE 65: 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 computer 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 computer asks it a information.
3. synchronisation cycle (range [10 s, 655350 s]): time synchronisation period of the IED
by the computer.
4. downgraded cycle (range [1 s, 10 s], step 100 ms): if an IED is set disconnected by
the computer, it tries to re-connect it regularly at this cycle.
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.
FIGURE 66: 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 computer 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.
IED answer is awaited when the computer asks it an information.
8. synchronisation cycle (range [10 s, 655350 s], step 10 s): time synchronisation period
of the IED by the computer.
10. Type of link (Balanced / Unbalanced): if unbalanced link, only master (here computer)
asks IED. If balanced link, IED can also ask the master (here computer) without
solicitation.
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 computer and IED. This
attribute corresponds to maximum delay to receive this life message, to computer’s
point of view. If no reception within this delay, IED is set disconnected.
12. inter frame duration (range [1, 50 ], step 1): this attribute represents the minimum
FIGURE 67: 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 computer asks it an information.
3. synchronisation (none / Schneider Electric / SEPAM / Flexgate): refer to
C264_ENCT and the reference document of the connected IED.
4. synchronisation cycle (range [10 s, 655350 s], step 10 s): time synchronisation
period of the IED by the computer. Only significant if attribute (3) is set to
‘Schneider Electric’, 'Flexgate' or to 'SEPAM'. To keep the Px4x synchronised, C264
must send the frame at least every 5 minutes; therefore the value must be lesser than
30 in this case.
6. inter frame duration (range [1, 50], step 1): this attribute represents the minimum
Schneider Electric
FIGURE 68: 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: computer address on the DNP3 legacy network.
IED answer is awaited when the computer asks it a information.
disconnected.
4. application time-out (range [0 s, 255 s], step 1 s): time-out used by the computer, 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.
6. synchronisation cycle (range [10 s, 655350 s], step 10 s): time synchronisation period
of the IED by the computer.
8. inter frame duration (range [1, 50], step 1): this attribute represents the minimum time,
expressed in number of characters, that must exist between two frames.
FIGURE 69: 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.
FIGURE 70: ADDING AN IED TO A LEGACY NETWORK
FIGURE 71: 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#.
FIGURE 72: 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.
FIGURE 73: ADDING AN IED ACQUISITION TYPE TO A LEGACY NETWORK

(E.G. FOR DNP3)
• For each computer 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.
FIGURE 74: 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:
1. IED type:
• Modicon to use the generic Modbus communication (refer to C264_ENCT)
• M300, Px2 series, MiCOM S40 (MiCOM Modbus communication)
• M230, Wago, 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.
FIGURE 75: 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 computer level.
2. synchronisation type (Network synchronisation / External synchronisation): in case
of network’ synchronisation, computer 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 computer level.
3. CROB parameters (Usage of 'code' field / Usage of 'Trip/Close' field / Usage of 'code'
and 'trip/close' fields):
FIGURE 76: SETTING ATTRIBUTES OF A DNP3 ACQUISITION TYPE
4.7.1.13 Adding Serial Tunneling

Following figures defines how to add serial tunneling to C264.
FIGURE 77: ADDING SERIAL TUNNELING

FIGURE 78: ADDING SERIAL PORT TO SERIAL TUNNELING

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 computer 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.
FIGURE 79: 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 an SPS datapoint

The addition of an IED address for an SPS datapoint is done via the “Objects entry” window
at IED SPS mapping level by clicking on mouse’s right button.
FIGURE 80: 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 function
3. bit number (range [0, 65535], step 1): used only if word read or status read is used
4. function (range [0, 65535], step 1): number of the Modbus function used to read the
SPS:
- 1, 2: read bit,
- 3, 4: read word,
- 7 : read status
For 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. function 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).
FIGURE 81: DEFINING AN IED ADDRESS FOR AN 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 82: 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 the function.
3. bit number (range [0, 65535], step 1): Used only if Word read or status read is used
4. function (range [0, 65535], step 1): Modbus function to use to read the DPS:
- 1, 2: read bit,
- 3, 4: read word,
- 7 : read status
For T101 protocol:
For T103 protocol:
- 1, 2 (for all IED)
- 65,66,67,68 (Only for Px3x)
8. function 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’.
FIGURE 83: 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. function (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:
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. function type (range [0, 65535],step 1).
9. information number (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: 21
− function type 254
− information number: 244
− index in the ASDU: Generic Identification Number given by the mapping of the IED
For DNP3 protocol:
FIGURE 84: DEFINING AN IED ADDRESS FOR AN MV DATAPOINT

Measurement formats that can be used with the MODBUS protocol

Because the Modbus norm only describes the transmission of 16 bits values (transmission of
the high order byte first), new formats must be defined to describe the different ways to
transmit 32 bits values (whatever their type: signed or unsigned integers, real values) or 8
bits values.
So the format to apply to an analog input depends on the way it is transmitted and
consequently on the representation of the value in the memory of the device.
In the following table, the “transmission order” column (4) indicates the way a value is
transmitted, i.e. the order in which the bytes of the value are transmitted. The bytes are
numbered from 1 (lowest order byte) to 4 (highest order byte).
Format Description Transmission order

INT8_LB Transmission of an 8 bit signed integer in a 16 bit value. /
The significant byte is the low order byte of the word.
INT8_HB Transmission of an 8 bit signed integer in a 16 bit value. /
The significant byte is the high order byte of the word.
UINT8_LB Transmission of an 8 bit unsigned integer in a 16 bit value. /
The significant byte is the low order byte of the word.
UINT8_HB Transmission of an 8 bit unsigned integer in a 16 bit value. /
The significant byte is the high order byte of the word.
INT16 Transmission of a 16 bit signed integer. The high order 2-1
byte is transmitted first (see Modbus standard)
UINT16 Transmission of a 16 bit unsigned integer. The high order 2-1
byte is transmitted first (see Modbus standard)
INT32_LW_LB Transmission of a 32 bit signed integer. The low order 1-2-3-4
word of the long value is transmitted first. The low order
byte of each word is transmitted first.
INT32_LW_HB Transmission of a 32 bit signed integer. The low order 2-1-4-3
word of the long value is transmitted first. The high order
INT32_HW_LB Transmission of a 32 bit signed integer. The high word of 3-4-1-2
the long value is transmitted first. The low byte of each
word is transmitted first.
INT32_HW_HB Transmission of a 32 bit signed integer. The high order 4-3-2-1
UINT32_LW_LB Transmission of a 32 bit unsigned integer. The low order 1-2-3-4
UINT32_LW_HB Transmission of a 32 bit unsigned integer. The low order 2-1-4-3
UINT32_HW_LB Transmission of a 32 bit unsigned integer. The high order 3-4-1-2
UINT32_HW_HB Transmission of a 32 bit unsigned integer. The high order 4-3-2-1
REAL32_LW_LB Transmission of a 32 bit real value. The low order word is 1-2-3-4
transmitted first. The low order byte of each word is
transmitted first.
Format Description Transmission order

REAL32_LW_HB Transmission of a 32 bit real value. The low order word is 2-1-4-3
transmitted first. The high order byte of each word is
transmitted first.
REAL32_HW_LB Transmission of a 32 bit real value. The high order word is 3-4-1-2
transmitted first. The low order byte of each word is
transmitted first.
REAL32_HW_HB Transmission of a 32 bit real value. The high order word is 4-3-2-1
transmitted first. The high order byte of each word is
transmitted first.
M230_T5_TYPE Transmission of a 32 bit: Unsigned Measure 4-3-2-1
Bit 31to 24 decimal exposant (signed 8 bytes)
Bit 23…00 binary unsigned value 24 bytes
M230_T6_TYPE Transmission of a 32 bit: Signed Measure 4-3-2-1
Bit 31to 24 decimal exposant (signed 8 bytes)
Bit 23…00 binary signed value 24 bytes
M230_T7_TYPE Transmission of a 32 bit: power factor 4-3-2-1
Bit 31to 24 Signed:Import / Export (00/FF)
Bit 23…16 Signed:Inductive / capacitive (00/FF)
Bit 15…00 Unsigned value (16 bytes)
ION_MODULUS_ Transmission of a 32 bit: ION Energy values 4-3-2-1
10000_unsigned
Bit 31to 16 reg Hight: RH= unsigned value/10000
Bit 15…00 reg Low: RL = unsigned value modulus 10000
Value = RH*10000+RL
ION_MODULUS_ Transmission of a 32 bit: ION Energy values 4-3-2-1
10000_signed
Bit 31to 16 reg Hight: RH= signed value/10000
Bit 15…00 reg Low: RL = signed value modulus 10000
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 85: 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:
8. function type (range [0, 65535],step 1):
9. information number (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:
12. address (range [0, 65535],step 1):
FIGURE 86: 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 an SPC datapoint is done via the “Objects entry” window
at IED SPC mapping level by clicking on mouse’s right button.
FIGURE 87: 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)
For DNP3 protocol:
FIGURE 88: 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 89: 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’.
FIGURE 90: 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 91: 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 UINT15 (unsigned integer, only 15 out of 16 bits are used). The IED type must be set to
WAGO.
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).
FIGURE 92: DEFINING AN IED ADDRESS FOR A SETPOINT DATAPOINT

4.7.3 Addressing a datapoint on 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
4.8 Networking SCADA on computer 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
computer bay panels (Bay Control Point or BCP), and outside the substation. Generally, the
distant control of the substation (Remote Control Point or RCP) is done via specific networks
called SCADA legacy network.
Several SCADA legacy networks can be connected to a PACiS system, via PACiS computer
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 computer 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 an optional auxiliary communication port in case of redundancy.
4.8.1.1 Adding a SCADA network
To create a SCADA network on a computer:
• Add a SCADA network from object entry available at computer level (1),
• Update the SCADA network attributes relevant to its protocol characteristics (see
section 4.8.2 Defining addressing mapping of SCADA network).
• If SCADA does not use the substation network to communicate with the computer,
update its ‘has for main communication port’ relation and the communication port
characteristics.
• For DNP3 and 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 computer SCADA network and fill it with the relevant serial port.
• A computer can manage up to two T104 SCADA clients. These two clients have
separate configurations but may have same data. On the SCADA port, up to four front
ends can be defined, corresponding to one active port and three backup ports. So, up
to four IP addresses will be defined during the configuration of each T104 client
(attributes (13) in section 4.8.1.6 Setting specific attributes of a T104 SCADA
network). If both clients are communicating with the computer, they must manage
thein own redundancy for doing controls with coherency.
FIGURE 93: ADDING A SCADA NETWORK

FIGURE 94: 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 computer 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 and Disturbance) are refreshed relatively to the selected protocol.
FIGURE 95: 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 traffic):
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. validity for 'Jammed' state (Valid / Invalid)
16. SOE file support (No / Yes)
17. SOE file address: this attribute is visible and significant only if attribute SOE file
support is set to Yes
18. SOE file format (T101 / S900) this attribute is visible and significant only if attribute
SOE file support is set to Yes
19. 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
20. '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)
21. Disturbance file address for slow wave , fast wave etc
22. Buffer overflow: Yes / No
FIGURE 96: SETTING PROTOCOL AND 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".
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).

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
14. 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
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 98: 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.

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. validity for 'Jammed' state (Valid / Invalid)
16. Switchover (Automatic switchover / Manual switchover)
17. SOE file support (No / Yes)
18. SOE file address (this attribute is visible and significant only if attribute SOE file
support is set to Yes)
19. SOE file format (T101 / S900) (this attribute is visible and significant only if attribute
SOE file support is set to Yes)
20. 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)
21. 'full' SOE file nb of events (range [0, 1000], step 1) file message sent to SCADA
(this attribute is visible and significant only if attribute SOE file support is set to Yes)
FIGURE 100: SETTING SPECIFIC 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’.
FIGURE 101: 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.
3. 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 102: 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 AN MPS DATAPOINT ON A SCADA NETWORK IS NOT
AVAILABLE.
FIGURE 103: 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 an SPS datapoint
The addition of a SCADA address for an SPS datapoint is done via the “Objects entry”
window at SCADA SPS mapping level by clicking on mouse’s right button.
FIGURE 104: 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 witout 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 computer level, values different from ‘Does not
involved in a transfer of file’ are associated to the same treatment, because only one
SOE file is managed by computer. The set of available values is maintained for
compatibility with MiCOM gateway addressing in MiCOM gateway.
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 105: DEFINING A SCADA ADDRESS FOR AN 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 106: 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 computer level, values different from ‘Not involved
in a transfer of file’ are associated to the same treatment, because only one SOE file
is managed by computer. The set of available values is maintained for compatibility
with MiCOM gateway addressing in MiCOM gateway.
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 107: 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 108: 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.
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.
6. 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.
7. Event record ( No / Yes): indicates if change of state of the datapoint must be saved
in Sequence of Event file or not..
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 109: 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 110: ADDING A SCADA COUNTER ADDRESS

Once added, SCADA Counter address attributes must be set at SCE level:
3. Format (Natural / Unsigned normalized / Real IEEE754 – little endian / Real IEEE754
– big endian): transmission format.
4. object address.
5. Event (No / Yes with time tag / Yes without time tag): when set to ‘Yes with time tag’,
indicates if changes of state of the datapoint are transmitted spontaneously with time
Tag.
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 111: 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 112: 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 113: DEFINING A SCADA ADDRESS FOR A 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 114: 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 115: 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 116: 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 117: 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).
FIGURE 118: ADDING A BYPASS S/C ADDRESS TO A SCADA SPC/DPC ADDRESS (E.G. FOR DPC)
4.8.3 How to configure a mapping of a SCADA network
When a SCADA network is selected in the browser an extra item in its contextual menu is
available: “Edit Scada mapping”. When selected, a modal window appears. It displays all
addresses existing under the mapping of the SCADA. The addresses are grouped by type,
five types exists:
• xPS present SPS / DPS addresses
• xPC present SPC / DPC addresses
• MV present measurement addresses
• SetPoint present SetPoint addresses
• Counter present Counter addresses

The following protocols of gateway: IEC61850 and GI74 are not concerned by this edition.
Each tab present addresses datapoint data in left part of the table and address data in the
right part of the table.
For datapoint data, attributes displayed are the same than other table:
− Kind
− Path
− Short name
− Long name
For address data, attributes displayed are different for each type of protocol:
− For example given of MODBUS C26x Protocol attributes are:
• For xPS:
⇒ Addr: value of the SCADA address, only active for SPS address, or DPS
address if Double address usage is set to ‘No’.
⇒ Close Addr: value of the close state address for DPS address, only active for a
DPS address if Double address usage is set to ‘Yes’.
⇒ Open Addr: value of the open state address for DPS address, only active for a
DPS address if Double address usage is set to Yes’.
⇒ Double address: flag to indicate if the address is double or not, only active for a
DPS address.
• For xPC:
⇒ Addr: value of the SCADA address.
• For MV:
⇒ Forma: format of the SCADA address.
⇒ Precision: accuracy of the analog input point in number of bits.
• For Counter:
⇒ Format: format of the SCADA address.
• For SetPoint:

Format: format of the SCADA address
FIGURE 119: SCADA MAPPING ADDRESS

4.8.4 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 120: REALISING SCADA ADDRESSING OF A DATAPOINT

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

The C264/C264C computers manage two kinds of wave recording file:
• IED connected to computer legacy network can produce disturbance files. In that
case, computer monitors their availability. As soon as available, they are uploaded
and stored at computer level. Computer computes for 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 computer. At the end of successful
downloading, computer erases the real-time data of availability.
• Via a CT/VT board (TMU220), computer can manage its own waveform record files.
Waveform channels are directly acquired on CT/VT board channels and buffered.
Triggered by pre-defined change of state, associated buffers are flushed on files that
correspond to waveform record files. In that case computer computes for SMT a real-
time data that gives the availability of a computer waveform record file, via station-bus
network. Then processing is similar to IED’s one.
4.9.1 Defining management of disturbance file for IED
Allowing computer to manage IED disturbance is done at IED configuration level by:
• Setting its ‘automatic disturbance’ attribute to yes.
• Adding RDRE brick (1) for the IED in LD0 logical device of the IEC-61850 mapping of
the computer.
• 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).
FIGURE 121: ADDING RDRE BRICK AND DREC READY DATAPOINT FOR IED
FIGURE 122: 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 computer 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 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 123: 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)..
FIGURE 124: 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 125: 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 126: 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 computer CT/VT board
Allowing computer to manage its own wave record file is done at computer 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 computer in LD0 logical device of the IEC-61850
mapping of the computer.
• Adding the system SPS datapoint ‘C26x DREC ready’ (2) at computer 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 127: ADDING A RDRE IEC-61850 BRICK AND A DREC READY DATAPOINT FOR A
COMPUTER
(3)
FIGURE 128: SETTING IEC 61850 ADDRESS OF DREC READY DATAPOINT FOR COMPUTER
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
computer level by clicking on mouse’s right button. Only one fast waveform recording can be
created under a computer.
FIGURE 129: 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 [1 , 480], step 1): see previous description.
4. number of files (1 / 2 / 4 / 8): see previous description.
(1)
(2)
(3)
(4)
FIGURE 130: SETTING FAST WAVEFORM RECORDING

To define the inputs of a fast waveform recording, just add the relevant relation (1) available
at recording level and fill the relation with proper CT/VT channel or datapoint. Be careful,
only CT/VT channels and datapoints acquired on the computer can be defined as input of its
fast waveform recording.
(1)
FIGURE 131: DEFINING INPUTS OF FAST WAVEFORM RECORDING

To define the triggers of a fast waveform recording, just add the relevant relation (2)
available at recording level and fill the relation with proper datapoint. Be careful, only
datapoints acquired on the computer can be defined as input of its fast waveform recording.
(2)
FIGURE 132: 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).
FIGURE 133: 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.
• 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 C264 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
computer level by clicking on mouse’s right button. Only one slow waveform recording can
be created under a computer.
FIGURE 134: 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 135: 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 computer can be defined as input of its slow waveform recording.
(1)
FIGURE 136: DEFINING INPUTS OF SLOW WAVEFORM RECORDING

To define the datapoint-triggers of a slow waveform recording, just add the relevant relation
(2) available at recording level and fill the relation with proper datapoint. Be careful, only
datapoints acquired on the computer can be defined as input of its slow waveform recording.
A slow waveform can be configured without any datapoint-trigger, if a daily or weekly
activation period has been defined for it.
(2)
FIGURE 137: 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).
FIGURE 138: 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 computer klaxon

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

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

When creating a computer, specific datapoints are automatically added in ‘system infos’
binder (1) at computer level or PLC sub-component.
So it is when adding a board (2), an IED on legacy network (3), a serial printer (4), or a
SCADA network (5) attached to a computer. In that case, the ‘system infos’ binder is located
under the relevant added object.
For extra computer functionalities (wave recording, redundancy) some optional datapoints
can be required.
SCE calls such ‘system infos’ datapoints, system datapoints.
System datapoints provide real-time statuses and controls on system software or hardware
components, and generally can not be wired on board channels except for redundancy
function.
As datapoint, system datapoints must be linked to a profile. For details about datapoint and
datapoint profile configuration, refer to 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 computer. 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 computer at their creation. If manual addressing is necessary, it is stressed in
following sections by given the associated available data object of a given computer brick in
LD0 (⇔<brick name>.<data object name>). For details about SBUS addressing see section
4.6 Networking computer on the station-bus network.
(2)
(4)
(3)
(5)
(1)
FIGURE 140: ‘SYSTEM INFOS’ BINDERS FOR A COMPUTER

4.11.1 Setting general system information of a computer

When creating a computer, the following mandatory datapoints are implicitly added.
FIGURE 141: MANDATORY ‘SYSTEM INFOS’ DATAPOINTS FOR A COMPUTER

These datapoints must be configured (see section 5 DEFINING DATAPOINT) according to

their described features:
• Controls and statuses for functioning mode
− Mode control DPC (9): 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 (10): 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
addressing.
− Test control DPC (18): 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 (5): this datapoint is required by IEC-61850 protocol but is
meaningless for the computer.
“OPEN” for Remote
“CLOSED” for Local
− This datapoint has no IEC address
− Local/remote DPS (6):
“OPEN” for Remote
“CLOSED” for Local
− Local/remote SPS (7):
− The available states of this datapoint are:
“RESET” for Local mode
“SET” for Remote mode
− This datapoint has the "RESET" state if the Local/remore DPS datapoint of all
the bays managed by the computer have the "OPEN" state and has the "SET"
state if at least the Local/remore DPS datapoint of one bay managed by the
computer has not the "OPEN" state.
− The IEC-61850 address of this datapoint is defined by using SBUS automatic
addressing.
• Control and status for database management
− Database incoherency SPS (1): this datapoint is put in ‘SET’ state if current
database is not self-consistent. In that case, computer enters the Maintenance
mode.
“RESET” for coherent database
“SET” for incoherent database
− Database switch control SPC (2): 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 (17): 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.
− All AIU Status SPS
− ALL AOU status SPS
− ALL CCU status SPS
− ALL DIU status SPS
− ALL DOU status SPS
− ALL IED status SPS
− ALL Rack status SPS
− ALL TMU status SPS
− Buffer Overflow SPS
− Setting disc. SPS
− Setting done SPS
− Setting in prog SPS
− Setting incoher. SPS
• Communication status
− Device link SPS (3): although this datapoint is under the computer, it is not
managed by it. Each IEC-61850 client of the computer computes locally this
datapoint status by supervising the IEC-61850 real-time link with the computer. In
fact, there are as many ‘Device link SPS’ per computer basis as IEC-61850 clients
connected to the computer. Is put in ‘SET’ state if device link is operational. The
available states of this datapoint are:
“RESET” for not OK
“SET” for OK
− This datapoint has no IEC address
• Health statuses
− DI acquisition stopped SPS (4): 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 (16): in case of software error, this datapoint is set and
computer enters the Faulty mode.
“RESET” for software running
“SET” for software error
− Watchdog SPS (19): in case of software watchdog time-out, this datapoint is put in
‘SET’ state and computer enters the Faulty mode.
“RESET” for watchdog OK
“SET” for watchdog time-out
• Control and statuses for redundancy management:
The four following datapoints are used internally by computer in case of redundancy.
These datapoints must be linked to datapoint profiles by default for proper behaviour
of redundancy.
− Redundancy change mode SPS (11)

− Redundancy change status SPS (12)
− Redundancy mode control SPC (13)
− Redundancy status control SPC (14)
− These datapoints have no IEC-61850 address.
− Main status MV (8)
addressing.
At computer level, the following optional datapoint can be added.
FIGURE 142: OPTIONAL ‘SYSTEM INFOS’ DATAPOINTS FOR A COMPUTER


− 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 computer (for details, refer to section 4.9 Defining wave record
file management).
“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
computer level is set to IRIG-B (for details, refer to section 4.3 Setting general
attributes of a computer). 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.
− Local alarm ack
4.11.2 Setting system information of board

When creating a board (except CPU board) the following mandatory datapoint is implicitly
added.
(1)
FIGURE 143: 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 144: 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 145: 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 146: MANDATORY ‘SYSTEM INFOS’ DATAPOINTS FOR A LEGACY IED

− 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
addressing.
− IED synchronisation status SPS (2): is put in ‘SET’ state if IED is synchronised.
“RESET” for IED not synchronised
“SET” for IED synchronised
addressing.
At IED level, the following optional datapoint can be added.
FIGURE 147: OPTIONAL ‘SYSTEM INFOS’ DATAPOINT FOR A LEGACY IED
− IED disturbance status SPS (2): 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
addressing.
4.11.4 Setting system information of serial printer
When creating a serial printer, the following mandatory datapoint is implicitly added.
(1)
FIGURE 148: MANDATORY ‘SYSTEM INFOS’ DATAPOINT FOR A SERIAL PRINTER
− Printer status MPS (1): this datapoint indicates the status of the printer.
“STATE 0” for printer OK
“STATE 1” for self-check failure
“STATE 4” for printer not present
addressing.
4.11.5 Setting system information of a SCADA network

When creating a SCADA network, the following mandatory datapoints are implicitly added.
(2)
(1)
FIGURE 149: 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
addressing.
− 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
addressing.
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 computer to other station-bus sub-systems, for Client /
Server definition).
In the set of all the computers of a SCS, the previous described SPS attributes (except short
name and long name) are only useful and given to the computer that serves the datapoint
because the relevant functions are always done at computer server level.
5.1.1 Overview of binary input processing
Binary input processing is described in section 5.1 of chapter C264/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 section4.11
Setting system information for computer 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 C264/EN FT.
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 COMPUTER CONFIGURATION IN ELECTRICAL ARCHITECTURE) or
system topology level (for details see section 4.11 Setting system information for
computer 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.
FIGURE 150: ADDING AN SPS DATAPOINT (SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPS)

FIGURE 151: LINKING AN 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 1 ms.
3. stable state time reference (Start of filtering / End of filtering)
4. reset confirmation delay (range [0 s, 120 s], step 100 ms]: confirmation delay for
stable ‘reset’ state.
5. set confirmation delay (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, computer can force or not its status to set or
reset state automatically. This attribute defines the way this forcing management is
done. Automatic forcing management is independent of FSS facility gives at user by
the SPS profile.
7. state panel assignment (No / Yes): set to ‘yes’ to enable SPS state display at
computer local HMI level.
FIGURE 152: 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 5.1.3 of chapter C264/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 153: ADDING A DPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC DPS)
FIGURE 154: 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 § 5.1.3.1 of chapter C264/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 § 5.1.3.1 of chapter C264/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 §
5.1.3.2 of chapter C264/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
§ 5.1.3.2 of chapter C264/EN FT
7. forcing management (Not automatic / Automatic to reset state / Automatic to set
state): when a DPS is in an invalid state, the computer can force or not its status to set
or reset state automatically. This attribute defines the way this forcing management is
done. Automatic forcing management is independent of FSS facility 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 computer local HMI level.
FIGURE 155: 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 5.1.4 of chapter C264/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 156: ADDING AN MPS DATAPOINT (SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MPS)
FIGURE 157: 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).
4. forcing management (Not automatic / Automatic to state (i ∈ [0, 15])): when a
MPS goes in invalid state, computer can force or not its status to set or reset state
automatically. This attribute defines the way this forcing management is done.
Automatic forcing management is independent of FSS facility gives at user by the
MPS profile.
5. state panel assignment (No / Yes): set to ‘yes’ to enable MPS state display at
FIGURE 158: SETTING GENERAL ATTRIBUTES OF AN 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 5.2 of chapter C264/EN FT.
Features of digital measurements are described in section 4.6 of chapter C264/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 AIU210 board) delivered by
transducers, and representing an external value.
Input characteristics
The saturation value, for each range, is the following:
Range Saturation values

± 10 V -12.6 V / +12.6 V
±5V -6.3 V / +6.3 V
± 2.5 V -3.2 V / +3.2 V
± 1.25 V -1.26 V / +1.26 V
0 - 1 mA 1.26 mA
± 1 mA -1.26 mA / +1.26 mA
0 – 5 mA 6.3 mA
± 5 mA -6.3 mA / +6.3 mA
0 – 10 mA 12.5 mA
± 10 mA -12.5 mA / +12.5 mA
0 – 20 mA 25 mA
± 20 mA -25 mA / +25 mA
4-20 mA 26 mA
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.5.2 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 159: ADDING AN MV DATAPOINT

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

(SAMPLE GIVEN AT BAY LEVEL FOR A GENERIC MV)
5.1.5.3 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.6.3 of chapter C264/EN FT.
3. IDRC: not significant
4. automatic forcing (No / Yes): when a MV goes in invalid state, computer can force or
not its value automatically. Automatic forcing management is independent of FSS
facility gives at user by the MV profile.
5. value for automatic forcing: MV value when automatic forcing
6. transmission on event (Cyclic long period / Cyclic short period / According to a ‰ of
full scale value / According to a ‰ of current value)
7. deadband (‰ variation) (range [0,255], step 1): this attribute is significant only if the
previous parameter is set to ‘According to a ‰ of ...’: this attribute corresponds to ‘p’
parameter described in section 5.2.9.2 of chapter C264/EN FT.
8. MV panel assignment (No / Yes): set to ‘yes’ to enable MV value displayed at
FIGURE 161: SETTING GENERAL ATTRIBUTES OF AN MV DATAPOINT

5.1.5.4 Setting ‘Value features’ attributes of an 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 5.2.3 of chapter C264/EN FT for details)
4. Hysteresis used for threshold detection (see section 5.2.4 of chapter C264/EN FT for
details)
For each available threshold (see section 5.2.4 of chapter C264/EN FT for details):
5. Threshold usage (No / Yes)
6. Threshold value
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 162: SETTING VALUE FEATURES ATTRIBUTES TO MV DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MV)
5.1.5.5 Setting ‘Scaling’ attributes of an MV datapoint
When adding a generic MV datapoint, some ‘Scaling’ attributes must be updated:
1. scaling rule: available values are (see section 5.2.4 of chapter C264/EN FT for
details):
− Linear
− Quadratic
− Quadratic with offset
− Linear per pieces
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 163: SETTING SCALING ATTRIBUTES OF AN MV DATAPOINT

5.1.6 Defining a TPI datapoint

5.1.6.1 Overview of Tap Position Indicator processing
Tap Position Indicator (TPI) is described section 5.3 of chapter C264/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.6.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 COMPUTER
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.
FIGURE 164: AUTOMATIC TPI CREATION FOR TAP-CHANGER BUILT-IN FUNCTION
(2)
FIGURE 165: LINKING TPI DATAPOINT TO ITS PROFILE
5.1.6.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.6.3 of chapter C264/EN FT.
3. MV panel assignment (No / Yes): set to ‘yes’ to enable MV value display at computer
local HMI level.
(1)
(2)
(3)
FIGURE 166: SETTING GENERAL ATTRIBUTES OF A TPI DATAPOINT

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

("maximum value" − "minimum value" + 1) ∈ [1..64]
5.1.6.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.6 of chapter C264/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 5.3 of chapter
C264/EN FT.
(1)
(2)
FIGURE 167: SETTING TAP POSITION ATTRIBUTES OF A TPI DATAPOINT

5.1.6.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 5.3.2 of
chapter C264/EN FT.
2. maximum acq. value: corresponds to Imax parameter described in section 5.3 of
chapter C264/EN FT.
(1)
(2)
FIGURE 168: SETTING SCALING ATTRIBUTES OF A TPI DATAPOINT

5.1.7 Defining a Counter datapoint

5.1.7.1 Overview of counter processing
Single counters and double counters are described in section §4.5 of chapter C264/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 169: 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 computer 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.7.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 COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE) or system topology level (for details see section 4.11 Setting
system information for computer components).
• Update the Counter attributes (see following sections).

(1)
FIGURE 170: ADDING A COUNTER DATAPOINT

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

5.1.7.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 C264/EN FT.
4. invalidity duration (range [5, 10 s], step 1 ms): corresponds to Tdef parameter
described in section 4.5 of chapter C264/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).
FIGURE 172: SETTING GENERAL ATTRIBUTES OF A COUNTER DATAPOINT

5.1.8 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 computer components).
Control sequences are described in chapter C264/EN FT (Functional Description).
5.1.9 Defining an SPC datapoint
To create an SPC datapoint:
• Add an 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
• Update the SPC attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SPC.
(1)
FIGURE 173: ADDING AN SPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPC)
FIGURE 174: LINKING AN SPC DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPC)
5.1.9.1 Setting ‘General’ attributes of an SPC datapoint

When adding a generic SPC datapoint, some general attributes must be updated:
2. used Profile: select the profile
3. spare: datapoint can be spared
4. activation mode (Permanent / Transient / Permanent until feedback).
5. order on duration (range [0, 15 s], step 10ms): this attribute is only available if the
activation mode is set to Transient. It defines the time while the contact is closed
before re-opening. hold duration (range [0, 10 s], step 10ms): this attribute is only
available if the activation mode is set to Permanent until feedback. It defines the
time while the contact is held in the requested position after reception of the
confirmation of the position of the device.
6. time between two orders (range [0, 10 s], step 100ms): this attribute corresponds to
the inter-control delay .
7. command panel assignment (No / Yes): set to ‘yes’ to enable SPC control at
8. bay mode dependency: Yes /No
9. SBMC mode dependency: Yes /No
10. bay Contol uniqueness: (No / Yes): only significant if control uniqueness is set to
bay at substation level.
11. Local Substation Dependancy: Yes/No
12. Remote Substation dependency: Yes /No
FIGURE 175: SETTING GENERAL ATTRIBUTES OF AN SPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR A GENERIC SPC)
5.1.9.2 Defining an SPC feedback
For correct execution behaviour and control acknowledgement, an SPC datapoint can be
linked to a SPS or DPS datapoint that corresponds to a feedback. For instance a circuit-
breaker control SPC is linked to the circuit-breaker status DPS.
To define an SPC feedback:
− Add the relation ‘has for feedback’ at SPC level: choose exclusively one of the two
relations ‘has for feedback: SPS datapoint’ (1) or ‘has for feedback: DPS datapoint’ (2)
depending on the kind of feedback datapoint.
− Fill the relation with the relevant SPS or DPS datapoint.
− If necessary update the relation attributes:
(1)
(2)
FIGURE 176: 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.8 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 6.1.6.8 of
chapter C264/EN FT and used also for execution checks (see section 6.1.8 of chapter
C264/EN FT).
(3)
(4)
FIGURE 177: SETTING ATTRIBUTES OF AN SPC FEEDBACK RELATION

• For each "SPC", two relations "has for feedback" are available, but they are mutually
exclusive
• A datapoint and its feedback datapoint must comply with the following rules:
- both must have the same Server device
- if one of them is a "Wired" datapoint, the other one must be "Wired" too (Here, the
term "Wired" means that the datapoint is linked to a digital or analog channel of a
computer, or linked to an IED address, else it's "System")
- if one of them is a "System" datapoint, the other one must be "System" too.
- if one of them is linked to an " IEC61850 gen IED" through the relation "has for
IEC61850 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.10 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
• 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 178: ADDING A DPC DATAPOINT

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

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC DPC)
5.1.10.1 Setting ‘General’ attributes of a DPC datapoint

When adding a generic DPC datapoint, some general attributes must be updated:
2. used profile: link to other DPC datapoint profile.
3. activation mode (Permanent / Transient / Permanent until feedback).
4. close duration (range [0, 15 s], step 10ms): this attribute is only available if the
activation mode is set to Transient. It defines the time while the DPC is held in the
"close" state before returning to the "open" state.
5. open duration (range [0, 15 s], step 10ms): this attribute is only available if the
activation mode is set to Transient. It defines the time while the DPC is held in the
"open" state before returning to the "close" state.
6. hold duration (range [0, 10 s], step 10ms): this attribute is only available if the
activation mode is set to Permanent until feedback. It defines the time while the
contact is held in the requested state after reception of the confirmation of the position
of the device.
7. time between two orders (range [0, 10 s], step 100ms): this attribute corresponds to
the inter-control delay defined in section 6.1.6.1 of chapter C264/EN FT and use also
used for execution checks (see section 6.1.8 of chapter C264/EN FT).
8. command panel assignment (No / Yes): set to ‘Yes’ to enable SPC control at
9. bay mode dependency: Yes /No
10. SBMC mode dependency: Yes /No
11. bay control uniqueness dependency: Yes / No (only significant if control
uniqueness is set to bay at substation level)
12. Local substation dependency: Yes /No
13. Remote substation dependency: Yes/ No
FIGURE 180: SETTING GENERAL ATTRIBUTES OF A DPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR A GENERIC DPC)
5.1.10.2 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:
1. 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.
2. 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.8 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 6.1.6.8 of
chapter C264/EN FT and also used for execution checks (see section 6.1.8 of chapter
C264/EN FT).
(1)
(2)
FIGURE 181: DEFINING A DPC FEEDBACK
FIGURE 182: SETTING ATTRIBUTES OF A DPC FEEDBACK RELATION

• For each "DPC", two relations "has for feedback" are available, but they are mutually
exclusive
- if one of them is linked to an " IEC61850 gen IED" through the relation "has for
• 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.11 Defining a SetPoint datapoint
5.1.11.1 Overview of SetPoint processing
Digital setpoints are described in section 4.9 of chapter C264/EN FT.
SetPoints are used to send instruction values to the process or to ancillary devices. MiCOM
Computers manage four types of SetPoints:
• Digital SetPoints
• SetPoints to IEDs
• System SetPoints
• Analog 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 chapter C264/EN FT.
Read inhibit signal for digital SetPoint

A dedicated binary output can be used to allow/ forbid reading the value by the external
device.
There is one (or none) read inhibit (RI) output per value.
If the RI output is a logical one (external polarity applied), the reading is permitted.
The procedure used to output a value with a RI output is:
• Reset the RI output to a logical 0: read forbidden.
• Wait for N ms.
• Output the value.
• 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 183: 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 computer 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 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 AO values are secured with an external power supply which allows keeping the analog
output value in case of C264 shutdown or power off. A quality indication is available with the
additional Read Inhibit output relays (NO) associated to each AO.
5.1.11.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 COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE) or system topology level (for details see section 4.11 Setting
system information for computer 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 184: ADDING A SETPOINT DATAPOINT

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

5.1.11.3 Setting ‘General’ attributes of a SetPoint datapoint

When adding a generic SetPoint datapoint, some general attributes must be updated:
2. type:
− Analogue: SetPoint is managed by IED by system output or by AOU board

ouptut
− Digital coded BCD
− Digital coded ‘Pure binary’
− Digital coded ‘Gray’
− Digital coded ‘1 among N’
− Digital coded ‘decimal’
3. used profile: can used other setpoints profile
4. progressive step usage: only used for digital SetPoint. No corresponds to Raw
activation, Yes to Incremental Activation, described in section Defining a SetPoint
datapoint.
5. minimum value (range [-3.4E38, 3.4E38]): used for value control and scaling.
6. maximum value (range [-3.4E38, 3.4E38]): used for value control and scaling.
7. command panel assignment (Yes / No): set to ‘yes’ to enable SetPoint control at
8. bay mode dependency: Yes/No
9. SBMC mode dependency:Yes/N
10. bay control uniqueness dependency:Yes/No (only significant if control uniqueness is
set to bay at substation level)
11. Local substation dependancy: From SCADA refused/Allowed
12. Remote substation dependancy: From OI refused/Allowed
FIGURE 186: SETTING GENERAL ATTRIBUTES OF A SETPOINT DATAPOINT

• A Setpoint datapoint wired on DO channels of a computer, must be digital and have its
profile attribute “SBO mode” set to "Direct Execute" or “Direct Execute with SBO
popup”.
5.1.11.4 Defining a SetPoint feedback
For correct execution behaviour and control acknowledgement, a SetPoint datapoint can be
linked to an MV datapoint that corresponds to a feedback.
To define SetPoint feedback:
• Add the relation ‘has for feedback’ (1) at SetPoint level
• Fill the relation with the relevant MV datapoint.
• 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.8 Overview of control sequence processing).
(1)
FIGURE 187: DEFINING SETPOINT FEEDBACK
(2)
FIGURE 188: SETTING ATTRIBUTES OF A SETPOINT FEEDBACK RELATION

- if one of them is linked to an "IEC61850 gen IED" through the relation "has for
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 COMPUTER CONFIGURATION IN SYSTEM ARCHITECTURE.
A profile object can be added at the following levels of the system topology:
• SCS.
• Ethernet network.
• Any instance of computer.
• Any instance of computer board.
• Any computer printer.
• Any SCADA network managed by a computer.
• Any IED managed by a computer.

When configuring a computer, the best practice is to group all profiles relevant to its system
datapoints at computer level or eventually its sub-components. Upper levels (Ethernet
network or SCS) can be used to define profiles if sharing datapoint profile between several
computers is wished.
For electrical datapoints, different approaches can be done:
• Grouping datapoint profiles at computer 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
computers.
Be careful:
(Refer to section 4.6.1 Connecting computer to other station-bus sub-systems, for Client /
Server definition)
In the set of all the computers of an SCS:
• the following profile functional characteristics logging, alarm, archiving and FSS, are
only useful and given to the computer that serves the linked datapoints because these
functions are always done at computer server level. So, a computer A using a
datapoint acquired on a computer 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 computers using a datapoint, because interlock evaluation is a
distributed function done on every computer that needs it before controlling its own
electrical modules.
• the following profile functional characteristics ‘SBMC facilities’ are given to server or
client computers using a datapoint exchanged on a SCADA network they manage,
because SBMC filtering is a distributed function done on computers managing SCADA
networks.
• the following profile characteristics ‘state/order labels’ are given to server or client
computers using a datapoint but are only used by the server: computer bay mimics,
logging, alarm definitions are reduced to datapoints that the computer is server of.
5.2.1 Defining an SPS profile

5.2.1.1 Adding an SPS Profile
To create an SPS profile:
• Add (icon +) 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).
• The alarm logging printer is defined at the same time as Event Logging (figure 163)
FIGURE 189: ADDING AN SPS PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)
FIGURE 190: DEFINING EVENT 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 computer software initialisation especially for
system datapoints.
FIGURE 191: 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 computer level (logging, display).
FIGURE 192: 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 no archive, no logging:
• OI: archive, logging:
• OI: archive, no logging:
• C264: no archive, no logging:
• C264: archive, logging:
• C264: archive, no logging:
• C264 : no archive, logging:
FIGURE 193: SETTING ‘STATE TREATMENTS’ ATTRIBUTES OF AN 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 computer configuration, all attributes are significant for datapoints it is server of.
FIGURE 194: 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 linked to this profile and belonging to an interlocking
equation the user chooses among three values (Invalid, False, True) which one will be used
for evaluation of the interlocking equation.
FIGURE 195: 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).
• The alarm logging printer is defined is the same time as Event Logging.
FIGURE 196: ADDING A DPS PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)
FIGURE 197: DEFINING EVENT 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:
1. short name and long name of the profile only used for profile identification in SCE.
And for linked DPS datapoints:
3. SBMC dependent (No / Yes).
4. SBMC state substitution value (Suppressed / Open / Closed / Jammed), significant
and visible if SBMC dependent 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 computer software
initialisation especially for system datapoints.
FIGURE 198: 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
FIGURE 199: 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
• OI : no archive, no logging:
• OI : archive, no logging:
• C264: no archive, logging:
• C264 : archive, logging:
FIGURE 200: 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:
without previous control)
disappears within this delay
6. audible (No / Yes): to activate a klaxon
− 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 ‘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’.
FIGURE 201: SETTING ‘ALARMS’ ATTRIBUTES OF A DPS PROFILE

5.2.2.6 Setting ‘Interlocking’ attributes of a DPS Profile

For each possible state of a DPS linked to this profile and belonging to an interlocking
FIGURE 202: 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).
• The alarm logging printer is defined is the same time as Event Logging (figure 179)
FIGURE 203: ADDING AN MPS PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)
FIGURE 204: DEFINING EVENT LOGGING PRINTER FOR 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:
2. enable Force/Subst/Sup (No / Yes)
3. SBMC dependent (No / Yes).
4. SBMC state substitution value (Suppressed / Open / Closed / Jammed): significant
and visible if SBMC dependent is set to Yes.
FIGURE 205: 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
FIGURE 206: 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
• OI : archive, logging:
FIGURE 207: 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
2. defined (No / Yes).
without previous control).
6. audible (No / Yes): to activate a klaxon.
− Gravity basis: the clearing mode is deduced from the one given at Scs object level
for the relevant gravity.
FIGURE 208: 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
FIGURE 209: 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).
The alarm logging printer is defined is the same time as Event Logging.
FIGURE 210: SETTING ‘INTERLOCKING’ ATTRIBUTES OF AN MPS PROFILE
FIGURE 211: DEFINING EVENT LOGGING PRINTER FOR MV PROFILE

5.2.4.2 Setting ‘General’ attributes of an MV Profile

When adding an 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 computer level.
5. default format: Reserved for Substation control point usage.
FIGURE 212: SETTING GENERAL ATTRIBUTES OF AN MV PROFILE

5.2.4.3 Setting ‘State labels’ attributes of an MV Profile
When adding a MV profile, some State labels attributes must be updated (1). They are used
for events and alarm management at computer level (logging, display).
FIGURE 213: SETTING ‘STATE LABELS’ ATTRIBUTES OF AN 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
• OI: no archive, no logging:

• OI: archive, no logging:
FIGURE 214: SETTING ‘STATE TREATMENTS’ ATTRIBUTES OF AN 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
5. audible (No / Yes): to activate a klaxon
FIGURE 215: SETTING ‘ALARMS’ ATTRIBUTES OF AN 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
FIGURE 216: 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)
FIGURE 217: 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).
FIGURE 218: ADDING A COUNTER PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)
FIGURE 219: DEFINING EVENT 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 equivalent to a pulse (range [-3.4E38, +3.4E38].
4. unit used for display, logging and alarm at computer level.
5. default format: Reserved for Substation control point usage.
(1)
(2)
(3)
(4)
(5)
FIGURE 220: 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
FIGURE 221: 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
FIGURE 222: 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:
1. defined (No / Yes).
4. audible (No / Yes), to activate a klaxon.
FIGURE 223: 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.
FIGURE 224: 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).
FIGURE 225: ADDING AN SPC PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)
FIGURE 226: DEFINING EVENT 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:
1. short name and long name of the profile only used for profile identification in SCE
And for linked SPC datapoints:
2. SBO mode (for details see section 6.1.2 of chapter C264/EN FT)
Available values are:
− Direct execute
− SBO operate once
− SBO operate many
− Direct execute with SBO control box (reserved to substation control point usage),
similar to ‘Direct execute’ for computer
3. SBO timeout (range [0, 600 s], step 1s), significant if SBO mode is set to ‘SBO
operate once’ or ‘SBO operate many’.
FIGURE 227: 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 computer 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
FIGURE 228: 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).
FIGURE 229: SETTING ‘STATE TREATMENT’ ATTRIBUTE OF AN SPC PROFILE

5.2.6.5 Setting ‘Alarms’ attributes of an SPC Profile
When adding an 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 are settable:
3. gravity (range [1, 5], step 1)
4. audible (No / Yes), to activate a klaxon
for the relevant gravity
FIGURE 230: SETTING ‘ALARMS’ ATTRIBUTES OF AN SPC PROFILE

5.2.6.6 Setting ‘Interlocking and FBD’ attributes of an SPC Profile

When adding an 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.7.1 Defining an FBD fast automation
and 6.7.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.
FIGURE 231: 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).
FIGURE 232: ADDING A DPC PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)

FIGURE 233: 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:
1. short name and long name: only used for profile identification in SCE
And for linked DPC datapoints:
2. SBO mode
− Direct execute
− SBO operate once
− SBO operate many
similar to ‘Direct execute’ for computer
FIGURE 234: 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
computer level (logging, display) and for correct SPC order management:
1. ‘Order open’ (set to 01) usage (No / Yes)
2. ‘Order close’ (set to 10) usage (No / Yes)
3. ‘Order open’ (set to 01) label
4. ‘Order close’ (set to 10) label
FIGURE 235: 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).
FIGURE 236: 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:
FIGURE 237: 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.7.1 Defining an FBD fast automation
and 6.7.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
FIGURE 238: 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).
FIGURE 239: ADDING A SETPOINT PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)
FIGURE 240: DEFINING EVENT 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. SBO mode: available values are:
− Direct execute
− SBO operate once, reserved for future use
− SBO operate many, reserved for future use
similar to ‘Direct execute’ for computer, reserved for future use
4. unit used for display, logging and alarm at computer level.
FIGURE 241: 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:
• OI: no archive, no logging:

FIGURE 242: 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:
− Manual: users must explicitly clear the alarm,
FIGURE 243: SETTING ‘ALARMS’ ATTRIBUTES OF A SETPOINT PROFILE

5.3 Defining computer local archiving of datapoint events

A computer manages only archiving of the datapoints it is server of (Refer to section 4.6.1
Connecting computer to other station-bus sub-systems, for Client/Server definition).
For computer, archiving is available or not for all the events appearing on a given datapoint.
Archiving is activated as soon as one ‘state treatment’ attribute is set to ‘Archive and logging’
or ‘archive only’ at datapoint profile level (see relevant section of 5.2 Linking a datapoint to a
profile).
5.4 Defining computer local archiving of datapoint alarms
A computer manages only archiving of the datapoints it is server of (Refer to section 4.6.1
Alarm archiving at computer level is defined globally for all the computers at Scs object level
(see section 4.1 Setting general system configuration relevant to computers - point (6))
5.5 Defining computer local logging of datapoint events and alarms
A computer manages only logging of the datapoints it is server of (Refer to section 4.6.1
For computer, 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
computer 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
computer 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 computer 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
computer’s DIU210-211, CCU200, AIU201 or AIU210 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 an 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 computer that manages the bay, are available. To define the
computer 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 244: WIRING ONE SPS DATAPOINT VIA ONE DI CHANNEL
(2)
FIGURE 245: 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 computer that manages the bay are available. To define the
computer that manages a bay, refer to section 6.1.4 Defining a Bay.
(1)
(2)
FIGURE 246: 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 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 computer that
manages the bay, are available. To define the computer 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 247: WIRING A MPS DATAPOINT VIA N DI CHANNELS

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 a 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 computer that
• To define sensor range of the AI channel, refer to section 4.4.5 Configuring an AI

channel.
(1)
FIGURE 248: WIRING A MV DATAPOINT OR A TPI DATAPOINT VIA ONE AI CHANNEL

To wire a MV or TPI datapoint on n DI channels (n <=64):
• Add the relations ‘bit wired on’ (1) at MV or TPI datapoint level, for each available
bit channel of the MV or TPI (i begins from 0).
• Fill the relations with the relevant DI channels: when datapoint level is lower than or
• 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 249: 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
• 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 250: 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 a MPS datapoint on an IED legacy network is not available.
Depending on legacy network type, addressing information can be different.
See section 4 DEFINING COMPUTER 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 computer that
(1)
FIGURE 251: 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
IEC61850 addressing mapping definition (nevertheless, similar IEC 61850 addressing
mapping is described in section 4.6.2 Defining addressing mapping of station-bus network 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 computer, 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 252: 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 computers
(communication status diagnostics).
• Supervision of redundancy between two PACiS computers (redundancy status
diagnostics).
• Supervision of logging printers managed by OI server or PACiS computer (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 computers.
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
computer 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,

5.6.4.3 Defining an ISaGRAF slow automation
By setting output plug, fast automation can produce real-time value for electrical input
datapoint (see section 6.7.1 Defining an FBD fast automation).
So can slow automation when it manages electrical datapoints or owns management input
datapoints (see section 6.7.2).
For group needs, an electrical SPS containing the group result must be created (see section
6.7.3 Defining a group).
For SPS-DPS association, the resulting DPS is the product of the two SPS associations (see
section 6.7.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.7.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 computer board.
Then, a specific link attribute must be filled to precise which MV computation is concerned
(power, harmonic ...).
Data produced by CT/VT board computation concern:
• RMS Values of phase voltage
• RMS values of busbar voltage
• RMS values of phase current
• RMS values of residual voltage and current
• Fundamental sequence components
• Active Power
• Reactive Power
• Apparent Power
• Frequency
• Harmonics levels (expressed as a ratio of the magnitude of the fundamental voltage or

fundamental current)
To link a MV datapoint to a CT/VT computation:
• Add the relation ‘is computed by’ (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 computer that manages the
bay, is available. To define the computer that manages a bay, refer to section 6.1.4
Defining a Bay.
• Update the relation attribute ‘measure type’ (2), giving the computation type.
(1)
FIGURE 253: 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
computer’s DOU201 or CCU2xx 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 computer that
(1)
FIGURE 254: 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 two times 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 255: WIRING A DPC DATAPOINT VIA TWO DO CHANNELS

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 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.11.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.11.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 256: WIRING A SETPOINT DATAPOINT VIA DO CHANNEL AND AO CHANNEL

• A Setpoint datapoint wired on DO channels of Computer, must be digital and have its
profile attribute “SBO mode” set to "Direct Execute" or “Direct Execute with SBO
popup”
5.7.1.4 Wiring from CCU datapoint
SPC, DPC datapoint can also use digital outputs of CCU boards.
FIGURE 257: ACQUIRING OUTPUT DATAPOINT USING CCU CARD)

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 COMPUTER 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 computer that
(1)
FIGURE 258: 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 computer, 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 259: 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 computers (redundancy controls).
• Facilities given by built-in electrical and grouping functions or user’s function, in PACiS
computers.
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.
Computer redundancy needs specific output typed datapoints that must be manually added
in computer’s hierarchy.
Most of system output datapoints when transmitted on station bus network are addressed in
IEC61850 diagnostics bricks.
The list of such system datapoints are given in section 4.11 Setting system information for
computer 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,

5.7.4.3 Defining an ISaGRAF slow automation
By setting output plug, fast automation can produce real-time order value for electrical output
datapoint (see section 6.7.1 Defining an FBD fast automation).
So can slow automation when it manages electrical output datapoints or owns management
output datapoints (see section 6.7.2).
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.7.4 Controlling xPC ).
5.7.5 Acknowledgement definition in case of simultaneous orders
When two opposite orders (Open/Close or Close/Open) are simultaneous and from different
origins, the acknowledgment management is described on the following table:
Cmd1 Cmd2 Action Ack

PSL PSL Cmd 1 cancelled NA
PSL Operator Cmd 1 cancelled NA
Operator PSL Cmd 1 cancelled CO_ACK_FAILED_ORDER (ACK 19)
Operator Operator Cmd 2 Ignored CO_REQUEST_IN_PROGRESS (ACK 6)
When two identical orders (Open/Open or Close/Close) are simultaneous and from different
origins, the acknowledgment management is described on the following table:
Cmd1 Cmd2 Action Ack

PSL PSL Cmd 2 Ignored NA
PSL Operator Cmd 2 Ignored CO_REQUEST_IN_PROGRESS (ACK 6)
Operator PSL Cmd 2 Ignored NA
Operator Operator Cmd 2 Ignored CO_REQUEST_IN_PROGRESS (ACK 6)
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 260: 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 261: 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.
FIGURE 262: 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 263: 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 computers. 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 COMPUTER 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 computer. 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.
FIGURE 264: ELECTRICAL TOPOLOGY DEFINITION (E.G.)

Feeder bay
Bus coupling bay
Transformer bay
Busbar bay
Bus section bay
C0212ENa
FIGURE 265: BAY SAMPLES
Switchgear
module
Q1
Circuit-breaker
module
Q0
Switchgear
module Q9
Switchgear Q8
Module (earth)
External line
module
C0213ENa
FIGURE 266: 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 267: 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 computer 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. 2 simultaneous controls are refused within the substation, except for
control datapoints configured as substation uniqueness independent (see section
Erreur ! Source du renvoi introuvable.) Erreur ! Source du renvoi introuvable.,
• 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 section Erreur ! Source du renvoi
introuvable. Erreur ! Source du renvoi introuvable.,Erreur ! Source du renvoi
introuvable.).
(1)
(2)
FIGURE 268: SETTING ATTRIBUTES OF A SUBSTATION

Bay and substation uniqueness are managed by computer 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 computers 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 computers to insure that feature.
For details about IEC-61850 configuration, refer to section 4.6 Networking computer
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 269: 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 C264 and
also in the OI. The detection mode attribute of this SPS must be set
to "Permanent" or "Permanent with computer auto-reset". This SPS
may be any wired SPS or SPS activated by a control ( by using the
Glb alm ack ctrl SPC(2)) from the SCADA or generated by any PSL.
It is also possible to launch a global alarm 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 (see section 6.7 Defining an electrical
regulation by user function) are accepted whatever was the mode. For details about the
configuration of this dependency attribute, refer to sections:
• SPC: 5.1.9,
• DPC: 5.1.10,
• SetPoint: 5.1.11.
In Local or Remote mode the information acquired by computers 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, computers) 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 computer
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 270: DEFINING LOCAL/REMOTE FOR SUBSTATION


Hereafter, the term "wired" means that the datapoint must be wired on digital channel(s) of a
computer.
• If "Loc/rem ctrl DPC" is present, then "Local/remote DPS" must be present (it's the
feedback).
• If "Local/remote DPS" is not wired, then "Loc/rem ctrl DPC" is 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 271: 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.
For more details about user function usage and their configuration, refer to section 6.7
Defining an electrical regulation by user function.
FIGURE 272: 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 273: 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.6)
(1)
(2)
(3)
FIGURE 274: SETTING GENERAL ATTRIBUTES OF AN 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 275: 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.
FIGURE 276: 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 computer manages the bay (2).
(1)
FIGURE 277: ADDING A TYPED BAY
FIGURE 278: DEFINING COMPUTER 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 279: 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 computers 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 computers to insure that feature.
For details about IEC61850 configuration, refer to section 4.6 Networking computer 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.6).
• 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.7.3 Defining a group)

DATAPOINT.
FIGURE 280: ADDING GENERIC DATAPOINT TO A BAY

NOTE: In C264, up to 8 transient SPS (1) can be defined as cyclic (day
cycle). They can be used to activate a periodic treatment. For these
SPS the user has to configure, in addition to the usual attributes of a
SPS (previously listed in section 5.1.2.2 Creating an SPS datapoint)
two specific attributes (2) which define the time when activation of the
SPS will occur.
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 computer that manages the bay.
The Local mode indicates that the bay is controlled from BCP. The controls issued from
upper level are not taken into account by the bay.
Some controls, defined during the configuration phase, can be independent of the bay
control mode: it means they can be issued from any control points whatever was the current
control mode. Controls from configurable automation (ISaGRAF) are accepted in remote
mode. For details about the configuration of this dependency attribute, refer to sections:
• SPC: 5.1.9,
• DPC: 5.1.10,
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 281: DEFINING LOCAL/REMOTE FOR BAY

Hereafter, the term "wired" means that the datapoint must be wired on digital channel(s) of a
computer
• If "Loc/rem ctrl DPC" is present, then "Local/remote DPS" must be present (it's the
feedback).
• If "Local/remote DPS" is not wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must not be wired.
• If "Local/remote DPS" is wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must be wired.
• If, under a Bay, a "DPC" or "SPC" datapoint has its attribute "bay mode dependency"
set to "Yes", then the Bay "Local/remote DPS" datapoint must be present.
• "Loc/rem ctrl DPC" datapoint must have its profile attribute “SBO mode” set to "Direct
If the "GHU200" board of a computer has its attribute "HMI type" set to the "Simple" value,
then the "Local/remote DPS" datapoints of the bays managed by this computer must be all
be "Wired" or all "System".
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:
• SPC: 5.1.9,
• DPC: 5.1.10,
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 282: 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.
FIGURE 283: 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 284: 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 details about this
attribute, refer to section 6.6)
(1)
(2)
FIGURE 285: 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). For details about this attribute,
refer to section 6.6..
− Not lockable module.
• Convertor, generator, motor:
− Not lockable module.
• Transformer:
− Lockable module.
− Supports Tap changer built-in function.
− Supports ATCC function needs.
• Circuit-breaker module:
− Supports synchrocheck 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.7.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 286: 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 287: 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 computer
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 computer level (see section 5.1.8 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.9.2 Defining an SPC
feedback).
(2)
(1)
FIGURE 288: DEFINING A LOCKABLE MODULE

Lock SPS and Lock control SPC are datapoints fed and controlled directly by the computer
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 computer LCD level. For more
details see section 7.3 Defining a computer bay mimic.
(1)
FIGURE 289: 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 computer level.
If the circuit-breaker is synchronised by internal or external synchrocheck, extra datapoints
exist. For more details refer to section 6.2 Defining a Synchrocheck function.
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
FIGURE 290: SETTING CIRCUIT-BREAKER TYPE

The following tables give inputs and outputs circuit breaker’s features controlled by the
computer 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’ (20) 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), (11) or (10) of the
breaker with the computed switch position (20) 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 (8) DPS or (19) SPS physical
open/close of device device position of the device (1
CONTROL
phase)
(10) SPC control for close of
device (14) SPS (optional) phase not
together information
(20) system DPS the
feedback of the control (i)
DEVICE (9) SPC (optional) control of (9) SPC (optional) control of (15) SPS (optional) device
device selection device selection selection position information
SELECTION
(HARDWARE)
Single phase circuit-breaker

DEVICE (1) DPC control for (2) DPC control for open (16) SPS or (5) DPS physical
open/close of device phase A position of phase A
CONTROL
(3) DPC control for open (17) SPS or (6) DPS physical
phase B (pulse) position of phase B
(4) DPC control for open (18) SPS or (7) DPS physical
phase C position of phase C
(1) DPC control for close of (14) system SPS phase not
device together information (ii)
(20) system DPS: the
feedback of the control (iii)
DEVICE (9) SPC (optional) control of (9) SPC/DPC (optional) (15) SPS (optional) device
device selection control of 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
FIGURE 291: AVAILABLE PRE-DEFINED DATAPOINTS FOR CIRCUIT-BREAKER
• The two datapoints "Switch Ctrl DPC" and "Switch Ctrl SPC" are mutually exclusive.
None is mandatory
• If physical position of the device is given by an SPS (19), phase not together
information (14) is mandatory
• Set1: {Switch phA DPC, Switch phB DPC, Switch phC DPC}
Set2: {Switch phA SPC, Switch phB SPC, Switch phC SPC}
Set3: {Switch phA pos. DPS, Switch phB pos. DPS, Switch phC pos. DPS}
Set4: {Switch phA pos. SPS, Switch phB pos. SPS, Switch phC pos. SPS}
If the "circuit-breaker type" is set to the "Single phase CircuitBreaker" value, then:
- in a set, if one datapoint is present for a phase, then the two others must be present
as well.
- the datapoints of the two sets (1) and (2) are mutually exclusive.
- if the datapoint "Switchgear pos." is present, but none of the three datapoints "Switch
PhA pos", "Switch PhB pos", and "Switch PhC pos" then the SPS datapoint "Ph not
together" is mandatory.
If the "circuit-breaker type" is set to the "Triple phase CircuitBreaker" value, then
no DPC referencing a phase (phA, phB or phC) is allowed.
• "Selection SPC" datapoint must have its profile attribute “SBO mode” set to "Direct
Execute" or “Direct Execute with SBO popup”
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.8 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 an I²t built-in function (relay folder)
The I²t function is described in C264/EN FT. It is associated with an overcurrent protection.
1. Define and wire a TMU210 board.
2. Define the eight MVs that follow:
FIGURE 292: DEFINING THE MEASUREMENTS
3. Link them to the TMU210 and give the link the right Measurement type from the drop-
down list. Select the TMU210 board and do a check of the table suming up the wiring.
4. Assign the MVs a link Has for IEC address.
5. Define the I²t built-in function:
An SPS indicates the on/off status. Its attributes are as follows:
FIGURE 293: I²T COMPUTING ATTRIBUTES
A SPC is used to reset all the measurements:
FIGURE 294: I²T RESET CTRL ATTRIBUTES
6. Map the measurements in the IEC 61850 XCBR Logical Node with the following
objects:
− IT_Phase A SumSwAARs
− IT_Phase B SumSwABRs
− IT_PhaseC SumSwACRs
− IT_Total SumSwARs
− I2T_Phase A SumSwA2ARs
− I2T_Phase B SumSwA2BRs
− I2T_PhaseC SumSwA2CRs
− I2T_Total SumSwA2Rs
These objects are BCR_ST type.ssd
Figure 295: MAPPING THE MEASUREMENTS

6.1.5.7 Defining a switchgear
This section deals with general switchgear features and available associated input and
General module features described in section 6.1.5 Defining Module are applicable to
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
FIGURE 296: SETTING SWITCHGEAR TYPE

The following tables give inputs and outputs switchgear’s features controlled by the
computer. For each datapoint its SCE identification is given by a number, referenced in the
following figure.
To configure correctly a switchgear module:
• Add the relevant datapoints, relatively to the following tables,
• 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)
FIGURE 297: 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.8 Overview of control sequence processing.
6.1.5.8 Defining a transformer
This section deals with general transformer features and available associated input and
General module features described in section 6.1.5 Defining Module are applicable to
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
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
(1)
(2)
(3)
FIGURE 298: 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 299: 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 ATCC function (see section 6.5 to give Mini Circuit-Breaker
position of associated tap-changer, via DPS datapoint
2. MCB position SPS: used for ATCC function (see section 6.5 )
CO495ENa
FIGURE 300: 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

6.2.1 Completing circuit-breaker definition for synchrocheck
The following tables give inputs and outputs circuit breaker’s features controlled by the
computer for triple phase and single phase circuit-breaker, when it is concerned by
synchrocheck function. For each datapoint its SCE identification is given by a number,
referenced in the following figure or relevant to the synchrocheck configuration (for
datapoints (22), (23), (24) and (25)).
These tables are complements to those described in section 6.1.5.5 Defining a circuit-
breaker.
To configure correctly a circuit-breaker module with synchrocheck:
• add the relevant datapoints, relatively to the following tables.
• do not forget to link via ‘has for feedback’ relation, the control(s) (1), (11) or (10) of the
breaker with the computed switch position (20) datapoint.
• link the circuit-breaker with an existing synchrocheck function created at bay or

substation level. This link is done at synchrocheck level (for details see 6.2.5 Creating
a synchrocheck function). Up to 2 circuit breakers can be linked to the same internal
synchrocheck.
• configure properly the synchrocheck function itself (for details see 6.2.5 Creating a
synchrocheck function).
Triple phase circuit-breaker with synchrocheck

DEVICE CONTROL (1) DPC control for (11) SPC control for open of (8) DPS or (19) SPS physical
open/close of device device position of the device (1 phase)
(23) SPC or (22) DPC (10) SPC control for close of (14) SPS (optional) phase not
control for close with device together information
synchrocheck
(23) SPC control for close with (20) system DPS the feedback
synchrocheck of the control (i)
DEVICE SELECTION (9) SPC (optional) (9) SPC (optional) control of (15) SPS (optional) device
control of device device selection selection position information
(HARDWARE)
selection
SYNCHROCHECK (24) SPC or (25) DPC (24) SPC or (25) DPC (26) SPS or (27) DPS (optional)
(optional) control of (optional) control of on/off on/off synchrocheck information
SET ON / SET OFF
on/off synchrocheck synchrocheck
Single phase circuit-breaker with synchrocheck

DEVICE CONTROL (1) DPC control for (2) DPC control for open (16) SPS or (5) DPS
open/close of device phase A physical position of phase A
(23) SPC or (22) DPC (3) DPC control for open (17) SPS or (6) DPS
control for close with phase B physical position of phase B
synchrocheck
(4) DPC control for open (18) SPS or (7) DPS
phase C physical position of phase C
(1) DPC control for close of (14) system SPS phase not
device together information (ii)
(23) SPC control for close (20) system DPS: the
with synchrocheck feedback of the control (iii)
DEVICE SELECTION (9) SPC (optional) control of (9) SPC (optional) control of (15) SPS (optional) device
device selection device selection selection position
(HARDWARE)
information
SYNCHROCHECK (24) SPC or (25) DPC (24) SPC/DPC (optional) (26) SPS or (27) DPS
(optional) control of on/off control of on/off (optional) on/off
SET ON / SET OFF (v)
synchrocheck synchrocheck synchrocheck information
(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
(v) Wired SPC and SPS for external synchrocheck and system SPC and SPS for internal
synchrocheck. If is not configured the external synchrocheck module or the
synchrocheck automatism is considered always “set on”. DPC and DPS are used only
for manual synchrocheck.
C0496ENa
FIGURE 301: AVAILABLE PRE-DEFINED DATAPOINTS FOR CIRCUIT-BREAKER BREAKER

WITH SYNCHROCHECK
Do not forget to define ‘Comp. swit. pos.’ mandatory SPS at circuit-breaker level as
feedback of Sync CB close SPC/DPC.
• The two datapoints "Switch Ctrl DPC" and "Switch Ctrl SPC" are mutually exclusive.
None is mandatory.
• If physical position of the device is given by an SPS (19), phase not together
information (14) is mandatory.
• Set1: {Switch phA DPC, Switch phB DPC, Switch phC DPC}
Set2: {Switch phA SPC, Switch phB SPC, Switch phC SPC}
Set3: {Switch phA pos. DPS, Switch phB pos. DPS, Switch phC pos. DPS}
Set4: {Switch phA pos. SPS, Switch phB pos. SPS, Switch phC pos. SPS}
If the "circuit-breaker type" is set to the "Single phase CircuitBreaker" value, then:
- in a set, if one datapoint is present for a phase, then the two others must be present
as well.
- if the datapoint "Switchgear pos." is present, but none of the three datapoints "Switch
PhA pos", "Switch PhB pos", and "Switch PhC pos" then the SPS datapoint "Ph not
together" is mandatory.
If the "circuit-breaker type" is set to the "Triple phase CircuitBreaker" value, then no
DPC referencing a phase (phA, phB or phC) is allowed.
• A Circuit Breaker must be linked only once to a Synchrocheck function (relation "is
synchrocheck of").
• If a Circuit Breaker is linked to a Synchrocheck function (relation "is synchrocheck of"),

then its "Sync CB close" SPC datapoint must be present.
• "Sync CB close" datapoint of a "Circuit breaker" linked to a "Ext manual CS" or "Int
synchrocheck" synchrocheck must have its profile attribute “SBO mode” set to "Direct
• "Sync CB close" datapoint of a "Circuit breaker" linked to a "Ext auto CS"

synchrocheck must have its profile attribute “SBO mode” set to " SBO Operate Once”.
“Open” control sequence of synchronised circuit breakers
This sequence remains identical to the non-synchronised circuit-breaker (refer to section
6.1.5.5 Defining a circuit-breaker).
“Close” control sequence of synchronised circuit breakers
This sequence is different according to the configuration the synchrocheck type:
• External synchrocheck: the closure of the device is assumed by an external

synchrocheck module.
• Internal synchrocheck: the closure of the device is assumed by an internal

synchrocheck automatism in the computer.
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 can:
• Cancel the request.
• Close the device by forcing request.

6.2.2 External synchrocheck behaviour

This functionality is described in section 6.3.2 of chapter C264/EN FT.
6.2.3 Internal synchrocheck behaviour
This functionality is described in section 6.3.3 of chapter C264/EN FT.
6.2.4 Automation description of internal synchrocheck
For each parameter of the internal synchrocheck, its SCE identification is given by (param
), referenced in Figure 311: SETTING ‘default settings’ attributes of an INTERNAL
SYNCHROCHECK.
Principle
The synchrocheck function can work in the following schemes:
Operator manual Operator Auto-recloser

closure Synchrocheck
closure
Network locking on both voltages X X X
presence and test of deltas (param 26) (param 20) (param 31)
Network coupling on both voltages X
presence and test of deltas (param 19)
Presence of only the line voltage X X X
(param 28) (param 22) (param 33)
Presence of only the busbar voltage X X X
Absence of both voltages X X X
The authorised schemes are defined during the configuration phase. The operator
synchrocheck closure behaviour is described in following sections.
Logic of authorisation of interlocking
The absolute values of the two voltages (Vline and Vbusbar) must be above or below settable
thresholds, to permit the circuit breaker closing. The following voltage controls are available:
• Vline and Vbusbar for network coupling
• Vline and Vbusbar for network locking
• Vline and not(Vbusbar)
• not(Vline) and Vbusbar
• not(Vline) and not(Vbusbar)

with Vline and Vbusbar TRUE if the measured voltage is above the threshold V> (param 15 and
param 17), and not(Vline) and not(Vbusbar) TRUE if the measured voltage is below the
threshold V< (param 16 and param 18). These threshold are given in % of the nominal
voltage value, updated at TMU200 board level (refer to section 4.4.2.3 Setting attributes of a
TMU220 board).
Schemes using Vline and not(Vbusbar) / not(Vline) and Vbusbar voltage controls
In case of the absence of one of the two voltages, at the end of a settable delay T2 (param
2), the authorisation of closing is given:
Vline
T2 0
& Closing authorization
Not(Vbusbar)
C0227ENa
FIGURE 302: VLINE AND NOT(VBUSBAR) VOLTAGE CONTROL
Vbusbar
T2 0
Not(Vline)
C0228ENa
FIGURE 303: NOT(VLINE) AND VBUSBAR VOLTAGE CONTROL

Schemes using not(Vline) or not(Vbusbar)voltage control
In case of the absence of both voltages, at the end of a settable delay T3 (param 1), the
authorisation of closing is given:
Not(Vline)
T3 0
Not(Vbusbar)
C0229ENa
FIGURE 304: NOT(VLINE) AND NOT(VBUSBAR) VOLTAGE CONTROL

Schemes using Vline and Vbusbar voltage control
Locking scheme
The closing authorisation will be given if the following conditions are fulfilled:
• Presence of both voltages , confirmed after a given delay (param 3) AND
the seized threshold (Evect) (param 5) AND
• The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin (param 6) and
Fmax (param 7) are the extreme acceptable frequencies AND
• The difference between the two frequencies (ΔF) is lower than the seized threshold
(Efreq) (param 8) AND
• The phase difference between the two voltages (Δϕ) is lower than the seized threshold
(Ephase) (param 9)
These criteria must be still met before the time-out of a delay T1 started on the criteria
appearance else the synchrocheck function will not authorise the CB closing.
If during the delay time T1 one of these criteria is lost, T1 is reinitialised and is relaunched on
reappearance of all the criteria.
T1 depends on the way circuit breaker is controlled (manual closure, manual synchronised
closure, automatic with auto-recloser), given 3 parameters at SCE level: (param 25), (param
30), (param 35).
Fmin < Fline < Fmax

Vline
Vbusbar
& T1 0 Reclosing authorization
ΔF <Efreq
Δϕ < Ephase
ΔV < Evect
C0230ENa
FIGURE 305: LOCKING SCHEME

Coupling scheme
In the coupling scheme, the CB can be closed only when the Δϕ is equal to 0.
But, in order to authorise the closing, it is first necessary that the following conditions are
fulfilled:
the seized threshold (Evect) (param 10) AND
• The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin (param 11)
and Fmax (param 12) are the extreme acceptable frequencies AND
• The difference between the two frequencies (ΔF) is lower than the seized threshold
(Efreq) (param 13)
These criteria must be still met before the time-out of a delay T1 started on the criteria
appearance else the synchrocheck function will not authorise the CB closing.
If during the delay time T1 one of these criteria is lost, T1 is reinitialised and is relaunched on
reappearance of all the criteria.
T1 depends on the way circuit breaker is controlled (manual closure, manual synchronised
closure, automatic with auto-recloser), given 3 parameters at SCE level: (param 25), (param
30), (param 35).
Fmin < Fline < Fmax

Vline T1 0 Autorisation to check Δϕ
&
Vbusbar
ΔF <Efreq
ΔV < Evect
C0231ENa
FIGURE 306: COUPLING SCHEME
Then, since a CB has a response time, it is necessary to wait a known Δϕ in order to

anticipate the response time and to close the breaker with a Δϕ equal to 0.
Therefore, the closing authorisation will be sent when Δϕ = ΔF*360*Ta ± Δ(Δϕ) where Ta
(param 4) is the anticipation time or response time of the circuit breaker and Δ(Δϕ) (param
14) is the acceptable mistake on Δϕ. There is a delay for such a coupling given in
configuration (param 24).
6.2.5 Creating a synchrocheck function

Synchrocheck function can be created at several levels of the electrical topology:
• Substation level, in case of the synchrocheck function is shared by several breakers,
• Bay level, in case of the synchrocheck function dedicated to a particular breaker of the
bay, or shared by two breakers in two different bays managed by the same computer.
The addition of a synchrocheck is done via the “Objects entry” window at substation or bay
For more details about bay creation, refer to section 6.1.4 Defining a Bay.
Several types of synchrochecks exist:
• External automatic synchrocheck
• External manual synchrocheck
• Internal automatic synchrocheck
• Internal manual synchrocheck

At substation level, only ‘external manual synchrocheck’ is available.
Only following typed bays allows synchrocheck creation:
• Busbar,
• Bus coupler,
• Bus section,
• Feeder,
• Transformer,
• Generic bay.
(1)
(2)
(3)
(4)
FIGURE 307: ADDING A SYNCHROCHECK AT BAY LEVEL (E.G. FOR FEEDER)
(2)
FIGURE 308: ADDING A SYNCHROCHECK AT SUBSTATION LEVEL

Once added, synchrocheck general features must be set at SCE level:

1. Fill the relation is synchrocheck of, giving which circuit-breaker module is concerned
by the function. For substation synchrocheck, several relations ‘is synchrocheck of’
can be added and filled for all concerned breakers by the same synchrocheck. For
bay synchrocheck, two relations ‘is synchrocheck of’ can be filled for breakers of two
different bays. Nevertheless, these bays must be managed by the same computer,
and the same synchrocheck parameters will be used for the two breakers closure.
2. short name and long name of the synchrocheck used for logging, alarms ...
3. automatic out of service (No / Yes): defines if the synchrocheck is set off manually
(No) or automatically (Yes). When manually set off, an extra sequence is done by
computer (see previous sections). For automatic synchrocheck, this attribute is fixed
to ‘Yes’.
4. running time (range [0, 60s],step 1 s): this attribute appears in case of automatic out
of service. It corresponds to a latency time before setting out of service the
synchrocheck after successful or unsuccessful closure of the synchronised breaker.
FIGURE 309: SETTING SYNCHROCHECK GENERAL FEATURES

(E.G. FOR EXTERNAL MANUAL SYNCHROCHECK AT BAY LEVEL)
In case of internal synchrocheck, extra configuration information must be set (see section
6.2.5.1Setting default settings of internal synchrocheck).
When adding a synchrocheck, the following mandatory datapoints is automatically created at
function level and must be configured (see section 5 DEFINING DATAPOINT):
1. Accept forcing: SPS datapoint, given the authorisation to force synchrocheck. It is a
system datapoint: it cannot be wired and is managed by the computer running
synchrocheck sequence. Any automation or operator interface asking for a
synchrocheck forcing, should be client of this datapoint and test its status before
forcing. So, proper IEC61850 configuration must be done for all clients (computer,
operator interface) to insure that feature.
(1)
FIGURE 310: ACCEPT FORCING MANDATORY DATAPOINT FOR SYNCHROCHECK

(E.G. FOR EXTERNAL MANUAL SYNCHROCHECK AT BAY LEVEL)
6.2.5.1 Setting default settings of internal synchrocheck

Default settings of internal synchrocheck are relevant to parameters of automation
description (see section 6.2.4 Automation description of internal synchrocheck)
When adding an internal synchrocheck, the following specific attributes must be updated:
General attributes
• absence deltas test duration (ms)
• presence test duration (ms)
• presence deltas test duration (ms)
• close time of the Circuit Breaker (ms)

Acceptance Conditions
• voltage delta threshold for locking (%)
• minimum frequency for locking (Hz)
• maximum frequency for locking (Hz)
• frequency delta threshold for locking (Hz)
• phase delta threshold for locking (°)
• voltage delta threshold for coupling (%)
• minimum frequency for coupling (Hz)
• maximum frequency for coupling (Hz)
• frequency delta threshold for coupling (Hz)
• phase delta threshold for coupling (°)

Voltage presence conditions
• line voltage over threshold (%)
• line voltage under threshold (%)
• bus voltage over threshold (%)
• bus voltage under threshold (%)

Used control schemes
• manual synchro close: coupling
• manual synchro close: locking
• manual synchro close: Line Dead and Bus Live
• manual synchro close: Line Live and Bus Dead
• manual synchro close: Line Dead and Bus Dead
• manual synchro close delay for coupling (s)
• manual synchro close delay (ms)
• manual close: locking
• manual close: Line Dead and Bus Live
• manual close: Line Live and Bus Dead
• manual close: Line Dead and Bus Dead

• manual close delay (ms)
• automatic close: locking
• automatic close: Line Dead and Bus Live
• automatic close: Line Live and Bus Dead
• automatic close: Line Dead and Bus Dead
• automatic close delay (ms)
FIGURE 311: SETTING ‘DEFAULT SETTINGS’ ATTRIBUTES OF AN INTERNAL SYNCHROCHECK
When adding an internal synchrocheck, some mandatory system datapoints are

automatically created at function level and must be configured (see section 5 DEFINING
DATAPOINT). They give information about internal synchrocheck context (both voltage
presences and absences) and statuses. They are managed by the computer that runs the
internal synchrocheck.
1. Close order: transient SPS set as soon as a synchronised closure is in progress
2. on/off SPS: see section 6.2.5.2 Adding synchrocheck specific datapoints
3. Possible closing SPS: in locking mode, all the conditions after delay are met to
authorise synchronised closure
4. Ref. U absence SPS
5. Ref. U presence SPS
6. Voltage absence SPS
7. Voltage presence SPS
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 312: INTERNAL SYNCHROCHECK MANDATORY DATAPOINTS

6.2.5.2 Adding synchrocheck specific datapoints
To assume previous described behaviour of synchrocheck, when adding an auto-recloser,
some optional datapoints can be created at function level and must be configured (see
section 5 DEFINING DATAPOINT):
1. on/off control DPC: to control in / out of service of the synchrocheck via DPC
2. on/off control SPC: to control in / out of service of the synchrocheck via SPC
3. on/off DPS (unauthorised on internal synchrocheck): giving in/out of service status of
the synchrocheck via DPS
4. on/off SPS (mandatory on internal synchrocheck and implicitly created): giving in/out
of service status of the synchrocheck via SPS
Do not forget to define on/off SPS/DPS as feedback of on/off control SPC/DPC if they exist.
(1)
(2)
(3)
(4)
FIGURE 313: SYNCHROCHECK OPTIONAL DATAPOINTS

• As shown in the following picture, under a Synchrocheck function, some datapoints

are mutually exclusive and some must be wired. Here, "wired" means that the
datapoint must be linked to a digital/analog channel of a computer, or linked to an IED
address
Substation
Ext manual CS
on/off ctrl DPC
mutually exclusive + wired
on/off ctrl SPC
on/off DPS
on/off SPS mutually exclusive
Feeder
Ext auto CS
on/off ctrl DPC
on/off ctrl SPC mutually exclusive
on/off DPS
Ext manual CS
on/off ctrl DPC mutually exclusive + wired
on/off ctrl SPC
on/off DPS
(A) automatic out of service - Yes

Int synchrocheck
on/off ctrl DPC - No
mutually exclusive
on/off ctrl SPC
on/off SPS
S0280ENa
• For an "Int synchrocheck" function, having its "automatic out of service" attribute set to
the "Yes" value, the "on/off ctrl DPC" or "on/off ctrl SPC" datapoint must be present.
• "on/off ctrl DPC" or "on/off ctrl SPC" datapoint of "Int synchrocheck" synchrocheck
must have its profile attribute “SBO mode” set to "Direct Execute" or “Direct Execute
with SBO popup”
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 3.1.2 of chapter C264/EN FT.
6.3.2 Creating an auto-recloser function
The addition of an auto-recloser is done via the “Objects entry” window at bay level by
clicking on mouse’s right button.
Only following typed bays allows auto-recloser creation:
• Busbar,
• Bus coupler,
• Bus section,
• Feeder,
• Transformer,
• Generic bay.
FIGURE 314: ADDING AN AUTO-RECLOSER 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.
FIGURE 315 (A): SETTING AUTO-RECLOSER FEATURES

FIGURE 316 (B): SETTING AUTO-RECLOSER FEATURES

• The two attributes "functioning mode (1 ph trip)" and "functioning mode (3 ph trip)"
must not be both set to "Not used" value
• If "functioning mode (1 ph trip)" value is set to "1P-3P-3P-3P", then the following rules
must be respected:
- "1st period monophased" < "2nd period triphased"
- "1st period monophased" < "3rd period triphased"
- "1st period monophased " < "4th period triphased"
• If "functioning mode (1 ph trip)" value is set to "1P-3P-3P", then the following rules
must be respected:
- "1st period monophased" < "3rd period triphased"
• If "functioning mode (1 ph trip)" value is set to "1P-3P", then the following rule must be
respected:
• If "functioning mode (3 ph trip)" value is set to "3P-3P-3P-3P", then the following rules
must be respected:
- "1st period triphased" < "2nd period triphased"
- "1st period triphased" < "3rd period triphased"
- "1st period triphased" < "4th period triphased"
• If "functioning mode (3 ph trip)" value is set to "3P-3P-3P", then the following rules
must be respected:
- "1st period triphased" < "3rd period triphased"
• If "functioning mode (3 ph trip)" value is set to "3P-3P", then the following rule must be
respected:
• If "functioning mode (1 ph trip)" value is different from "Not used", then the "circuit-
breaker type" must be set to "Single phase CircuitBreaker"
• If "functioning mode (3 ph trip)" value is set to "Not used", then the "circuit-breaker
type" must be set to "Single phase CircuitBreaker"
To assume previous described 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
FIGURE 317 (A): AUTO-RECLOSER MANDATORY DATAPOINTS

FIGURE 318 (B): AUTO-RECLOSER 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
FIGURE 319: AUTO-RECLOSER OPTIONAL DATAPOINTS

• If "functioning mode (1 ph trip)" value is different from "Not used", then at least one of
the three SPS datapoints { "Trip PhA", "Trip PhB", "Trip PhC" } is mandatory
• If "functioning mode (1 ph trip)" value is set to "Not used", then none of the three SPS
datapoints { "Trip PhA", "Trip PhB", "Trip PhC" } is allowed
• The two datapoints { "on/off ctrl DPC", "on/off ctrl DPS" } are mutually exclusive and,
at least one of them is mandatory
• The two datapoints { "lock/reinit SPC", "lock/reinit SPS" } are mutually exclusive. If the
"unlocking way" attribute value is set to "Reinitialization" or "Both ways" then, at least
one of the two datapoints is mandatory
To assume previous described behaviour, when adding an auto-recloser, some mandatory
datapoints are automatically created at circuit-breaker level and must be configured (see
section 5 DEFINING DATAPOINT):
1. CB Healthy: corresponds to the ‘CB HEALTHY’ BI described in
section 6.3.1 Auto-recloser behaviour
FIGURE 320: AVAILABLE CB HEALTHY PRE-DEFINED DATAPOINTS FOR CIRCUIT-BREAKER

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 6.5 of chapter C264/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.8
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 5.1.2.1 Persistence filtering of chapter C264/EN FT.
2. set confirmation delay (range [0 s, 120 s], step 100 ms]: this delay corresponds to
time-out TS given in section 5.1.2.1 Persistence filtering of chapter C264/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
FIGURE 321: 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 6.5.2.1 of chapter C264/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 322: 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.
FIGURE 323: SETTING TAP CHANGER ATTRIBUTES

When adding a tap changer function, the mandatory datapoint ‘Tap position indicator’ (TPI)
is automatically created at function level (8).
The following table gives inputs and outputs tap changer’s features controlled by the
computer. For each datapoint its SCE identification is given by a number, referenced in the
following figure.
To configure correctly the tap changer of a transformer module:
• add the relevant datapoints, relatively to the following tables,
Tap changer for transformer

OUTPUTS INPUTS
DEVICE CONTROL (2) DPC raise/lower (8) TPI value

(1) DPC (optional) goto min/max (7) SPS (optional) tap change in progress
DEVICE SELECTION (4) SPC (optional) transformer (i) SPS (optional) selection position
(HARDWARE) selection information
(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 324: AVAILABLE PRE-DEFINED DATAPOINTS FOR TAP CHANGER

• "Raise/lower DPC" datapoint must have its profile attribute “SBO mode” set to "SBO
Operate Many"
6.5 Defining an automatic voltage regulation–AVR built-in function

6.5.1 Creating an AVR function
AVR relates to the transformer bays; hence the configuration is done at this level. The
topology is defined by the node references of each individual transformer. Transformers in
parallel are located in separate bays; among them, one is master, the others followers.
Several independent groups can be configured in the same substation.
In the “Objects entry” window, select the AVR built-in function and right click on Add. This
permits creation of datapoints related to the AVR real-time information & controls of the
transformer bay.
List of attributes (* means that it can be modified through operator controls, ** through
setpoints):
Tab Parameter name Values Min Max Step Default

AVR state* ON/OFF - - - ON
AVR mode* Manual / Automatic - - - Automatic
Transformer nominal voltage 20000.0 V
A Nominal voltage 100 V
Nominal current 1A
V Type of regulation
PhAse voltage /
- - - Phase voltage
Compound voltage
R Manual controls allowed
No/Only on AVR
No
locked/Always
Automatic move to manual mode No/ Yes (immed.)/ Yes
- No
on errors after delay
Manual mode on errors 60 s
Target voltage management Controls/Remote- - - - Controls
Target voltage active No/1/2/3/4/5 1
No target voltage active delay 10 300 10 120
T Remote target voltage min value In % of Vn 90% 105% 0,25% 90%
A Remote target voltage max value In % of Vn 95% 110% 0,25% 110%
R Remote target maximum difference
In Volt (MV range value) 50V 500V 10V 200V
G between 2 target voltages
E End of remote target voltage delay 0mn 480mn 10mn 60mn
T End of local target voltage delay 3mn 10mn 1mn 5mn
Displayed in volt but used as
Target voltage 1 88% 112% 0.1% 100%
V % Vn
O Target voltage 2
100% 104% 0.1% 102%
% Vn
L
T Target voltage 3
% Vn
103% 107% 0.1% 105%
A Displayed in volt but used as
Target voltage 4 106% 110% 0.1% 108%
G % Vn
E Target voltage 5
93% 97% 0.1% 95%
% Vn
Local Target Voltage 90% 110% 0.25% 100%
% Vn

Voltage confirmation delay 0 10 0.1 0.5
Double wound Yes/no - - - No
Voltage 1 / voltage 2 /
Double wound voltage Voltage 1
average
Double wound voltage difference % of Vn 0% 10% 1% 5%
Voltage presence threshold Displayed in volt but used as 20% 80% 10% 50%
% Vn
V Regulation deadband % of Vc 0% 4% 0.25% 1.25%
Abnormal voltage (threshold) % of Vc 2% 11% 1% 5%
O Abnormal voltage delay present 20s 600s 10s 300s
Abnormal voltage delay missing 0s
L Voltage present delay Tp 0s 120s 1s 0s
Voltage missing delay Ta 30s 180s 10s 120s
T Compounding activation* Active/ Inactive - - - Inactive
Compounding method Active / Reactive - - - Active
A Active compounding method par. % of Vn/In 0% 20% 0.5% 0%
A1**
Active compounding method par. % of Vn/In
G B1**
0% 20% 0.5% 0%
Reactive compounding method

% of Vn/In 0% 20% 0.5% 0%
E p A2**
Reactive compounding method
% of Vn/In 0% 20% 0.5% 0%
p B2**
Compound nominal current 0 0.01 0.1
Voltage correction 0 0.01 0%
Double A1 No/yes - - - No
Double B1 No/yes - - - No
Double A2 No/yes - - - No
Double B2 No/yes - - - No
Tap changer fault function Internal and/or external - - - Internal only
Autom/manual reset/
Tap changer fault behavior - - - Automatic
manual mode
Highest tap value 1 64 1 39
Lowest tap value 1 64 1 1
Intermediate position No/yes - - - No
Intermediate position active Off/on Off
Intermediate tap delay 0s 60s 1s 10s
T Intermediate tap 1 64 1 1
First tap delay T1 10s 70s 5s 60s
A Next tap delay T2 2s 30s 2s 10s
End Tap delay 0s 180s 5s 60s
P First tap delay bypass delay Tb 20s 120s 10s 30s
Preset tap 1 39 1 1
Preset tap delay 0s 10s 1s 1s
TCIP time out delay 5s 180s 5s 10s
TCIP End time out delay 1s 120s 1s 10s
Tap Changer Fault delay 60s 600s 10s 120s
Number of taps before highest tap 1 10 1 4
Number of taps before lowest tap 1 10 1 4
Slipping period for counting Period in days 1 120 1 30
Runaway tap delay 0s 60s 1s 30s

Tap changer set Lower and/or raise Only lower
on defined tap/lock
Voltage loss position tap defined tap
A automatic reg
Tap changer position behavior Preset/current/lowest Preset
U Primary CB state Open/close Open
Overcurrent/overvoltage/ Signalization / Signal. &
Signalization
T undervoltage locking
Tap changer position on voltage
Off/on - - - Off
O loss function activation*
Fast tap changer move after
Off/on - - - Off
M voltage loss function activation*
Overcurrent detection activation* Off/on - - - Off
A Overcurrent threshold % of In 50% 500% 10% 250%
Overcurrent delay 0s 30s 0.1s 2s
T Overvoltage detection activation* Off/on - - - Off
Overvoltage threshold % of Vn 100% 130% 1% 130%
I Overvoltage delay 0s 30s 0.1s 2s
Undervoltage detection activation* Off/on - - - Off
O Undervoltage threshold % of Vn 50% 100% 1% 70%
Undervoltage delay 0s 30s 0.1s 2s
N Tap Changer blocking activation * Off/on - - - Off
Tap Changer blocking delay 0s 300s 10s 60s
Transformer in parallel Yes/No - - - No
T
Master/Followe/Foll master
R Role
backup
Initial state Off/on Off
in
Master failure management Follow bec master - - - Folbecmaster
Used parallel method Neg - - - Master/Follow
//
Backup mode delay 0s 120s 1s 60s
RPF used Yes/No - - - No
Primary voltage used In kV 0 kV 400 k 1 kV 63 kV
RPF current threshold in % of In 0% 20% 1% 5%
RPF detection delay Tconfirm in seconds 0s 30s 1s 5s
Ignore/block operat/reg.
RPF management mode - - - Blockoperaton
R reversely
RPF target voltage in % of primary Vn 88% 120% 0.1% 100%
P RPF deadband in % of primary Vn 0.5 4.0 0.25 2.0
RPF first tap delay 10s 70s 5s 60s
F RPF next tap delay 2s 30s 2s 10s
RPF compound method No - - - No compdg
RPF compound A1 0 20 5 0
RPF compound B1 0 20 5 0
RPF compound A2 0 20 5 0
RPF compound B2 in % of primary Vn/In 0 20 5 0
To define the transformer, refer to section §6.1.5.8.

To associate the AVR to a Tap changer:
• double click the link ‘Associated with’; this opens the Relation link editor
• select the desired path in the list beneath
• click OK
To assign an IEC address to each datapoint:
• select the data point
• tap into the ‘Objects entry’ window to add a link
• double click the link
• select the path in the list
• click OK
In the MiCOM C264 that manages the bay where the AVR built-in function is created, set
that an AVR panel must be present.
The Period binder includes four bricks. Each includes a timetable H1 thru H24 (Hour tab)
and a definition of the days where this timetable applies (third tab):
• Holidays target: days off round the year
• WE#1 target: first day in the week-end
• WE#2 target: second day in the week-end (it must follow the preceding day in order)
• Week target: regular days

Example: define the target voltage number according to the schedule that follows:
Holidays definition is set in configuration, with a maximum of 10 days with a fixed date (ex:
14/07). If the current day is defined as a holiday, the target voltage values used are the ones
defined for holiday.
Special days definition is set in configuration, with a maximum of 10 days with a fixed date
(ex: 11/01). If the current day is defined as a special day, the target voltage values used are
the ones defined for the weekdays (even if the day is a week end day 1 or 2, or a holiday).
Week days definition is set in configuration.
6.5.2 AVR behaviour

The AVR built-in function is described in chapter C264/EN FT.
6.6 Defining an automatic voltage regulation–ATCC built-in function

6.6.1 ATCC behaviour
The ATCC built-in function is described in chapter C264/EN FT.
6.6.2 Creating an ATCC function
ATCC is a complex built-in function for it concerns specific objects (transformer, busbar,
voltage level) constituting the substation. At SCE level, ATCC modelling is split into different
objects (ATCC function needs) located under each electrical component relevant to it. The
set of these objects corresponds to the parameterisation of ATCC substation built-in
function.
Adding ‘ATCC function needs’ object under electrical component permits automatic
datapoint creation. These datapoints relate to the ATCC real-time information and controls
relevant to this electrical component.
Voltage levels managed by ATCC do not need specific datapoints for the ATCC function. So,
specific attributes put at voltage level objets are preferred to give extra ATCC function needs
for each voltage level.
In the following sub-sections, required datapoints for ATCC function are prefixed with an
identifier, referred in chapter C264/EN FT.
• If there is NO ATCC under the Substation, then:
− a "Voltage level" must have its "ATCC existence" attribute set to "No".
− the "ATCC fct needs" is allowed neither under a "transformer" nor under a
"BusBar".
• If there is an "ATCC fct needs" under a "transformer", then:
− the "Tap changer" with its "Raise/lower DPC" datapoint are mandatory.
− one of the two datapoints { "MCB position DPS", "MCB position SPS" } is
mandatory. They are mutually exclusive
− the "transformer" must be linked to a Voltage level through one and only one of
the relations { "has its primary on", "has its secondary on" }. The Voltage level
must be different from the one under which the transformer is located.
6.6.2.1 Defining ATCC function needs at substation level
The entry point of ATCC configuration is done at substation level.
This is done via the “Objects entry” window at substation level by clicking on mouse’s right
button.
(1)
FIGURE 325: ADDING AN ATCC FUNCTION AT SUBSTATION LEVEL

Once added, ATCC features must be set at SCE level:
1. Fill the relation ‘is managed by’, giving which computer runs and supervises ATCC
function at substation level.
2. short name and long name of the ATCC used for logging, alarms ...
‘General’ attributes:
‘calculation’ attributes
− calculation period
− calculation mode
‘Homing’ attributes
− active homing
− homing deadband
‘ATCC mode changing’ attributes
− mode on group interconnection
− mode on bay in local

‘Compounding’ attributes
− compounding method
Delays’ attributes:
‘Nominal’ attributes
− fixed initial tap delay (no means inverse delay).
− initial tap delay (in ms)
− inter tap delay (in ms).

‘Homing’ attributes
− homing initial tap delay (in ms)
− homing inter tap delay (in ms)

‘Hunting’ attributes
− hunting window (in ms)
− opposite max tap changes (default value: 4 )”
‘Inhibition’ attributes
‘Inhibition conditions’ attributes
− max voltage difference (ratio) (default value: +2%)
− tolerable nominal under voltage (ratio) (default value: 80%)
− tolerable nominal over voltage (ratio) (default value: 120%).
‘Busbar voltage’ attributes

Coefficients for busbar voltage calculation attributes
− voltage coefficient for 1 transfo
− voltage coefficient for 2 transfos

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
FIGURE 326: SETTING GENERAL FEATURES OF ATCC
(10)
(11)
(12)
(13)
(14)
(15)
(16)
FIGURE 327: SETTING ‘DELAYS’ ATTRIBUTES OF ATCC
(17)
(18)
(19)
FIGURE 328: SETTING ‘INHIBITION’ ATTRIBUTES OF AN ATCC
(20)
(21)
(22)
(23)
FIGURE 329: SETTING BUSBAR VOLTAGE ATTRIBUTES OF AN ATCC

When adding an ATCC to a substation, the following mandatory datapoints are automatically
created and must be configured (see section 5 DEFINING DATAPOINT):
(DPT_Sub 1) ATCC clear alarm SPC
(DPT_Sub 2) ATCC on/off control SPC
(DPT_Sub 3) AVR defect alarm SPS
(DPT_Sub 4) DBI override SPS
(DPT_Sub 5) ErrorLog SPS
(DPT_Sub 6) On/off SPS
(DPT_Sub 7) Target unreached SPS
(DPT_Sub 1)
(DPT_Sub 2)
(DPT_Sub 3)
(DPT_Sub 4)
(DPT_Sub 5)
(DPT_Sub 6)
(DPT_Sub 7)
C0246ENb
FIGURE 330: MANDATORY DATAPOINTS FOR ATCC AT SUBSTATION LEVEL
6.6.2.2 Defining ATCC function needs at voltage level

For each voltage level containing a transformer concerned by an ATCC function, extra ATCC
configuration must be done.
This is done under SCE at voltage level, by setting the attribute ‘ATCC existence’ to ‘Yes’
(1).
Then an extra ‘ATCC’ tab appears with the following attributes to update:
‘voltage targets’ attributes
− voltage target by default.
− voltage target 1
‘regulation’ attributes
− voltage target ramping rate (kV/mn)
− max tap change rate (kV/min)
− voltage deadband to end tapping
− voltage deadband to initiate tapping

When a voltage level is concerned by an AVR function, do not forget to set correctly its
attribute ‘nominal value (kV)’ (refer to section 6.1.3 Defining a Voltage level). It is used for
transformer nominal ratio computation.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
FIGURE 331: SETTING ATCC FUNCTION ATTRIBUTES AT VOLTAGE LEVEL
6.6.2.3 Defining ATCC function needs at busbar level

For each busbar bay concerned by an ATCC function, extra ATCC configuration must be
done. For details about busbar bay creation, refer to section 6.1.4 Defining a Bay.
This is done via the “Objects entry” window at busbar level by clicking on mouse’s right
button.
FIGURE 332: ADDING ATCC FUNCTION NEEDS AT BUSBAR LEVEL
Once added, ATCC busbar features must be set at SCE level:

− setpoint ponderation
− priority
‘line drop compensation (if setpoint adjustement)’ attributes
− resistive coefficient
− reactive coefficient
‘line drop compensation (if voltage adjustement)’ attributes
− transfo-busbar resistive coefficient
− transfo-busbar reactive coefficient
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 333: SETTING GENERAL BUSBAR FEATURES OF AN ATCC

When adding an ATCC function needs at busbar level, the following mandatory datapoints
are automatically created and must be configured (see section 5 DEFINING DATAPOINT):
(DPT_Bb 1) ATCC inhibited
(DPT_Bb 2) ATCC inv module
(DPT_Bb 3) ATCC inv voltage
(DPT_Bb 4) ATCC max transfo
(DPT_Bb 5) ATCC on/off
(DPT_Bb 6) ATCC on/off ctrl
(DPT_Bb 7) ATCC targ 1 ctrl
(DPT_Bb 12) ATCC target 1
(DPT_Bb 17) ATCC to target
(DPT_Bb 18) BusBar voltage
(DPT_Bb 1) (DPT _Bb 2)
(DPT_Bb 3) (DPT_Bb 4)

C0348ENa
FIGURE 334: MANDATORY DATAPOINTS FOR AVR AT BUSBAR LEVEL
6.6.2.4 Defining ATCC function needs at transformer level

For details about transformer bay (and subsequent transformer module) creation, refer to
sections 6.1.4 Defining a Bay.
For each transformer concerned by an ATCC function, extra ATCC configuration must be
done at several levels:
• Set properly the following features for transformer module:
− ‘Transformer type’ attribute
− ‘Power value’ attribute: (range [1, 300 MVA]).
− ‘Impedance’ attribute, whose unit is a percent of value for S=100 MVA (range
[0,01 to 24,99 by step 0,01):
− MCB position SPS or DPS is mandatory (refer to 6.1.5.8).
• Add and configure a Tap-changer built-in function for the transformer module (refer to
section 6.4 Defining a Tap changer built-in function), with the following features:
− Raise/Lower DPC is mandatory
− Tap in progress SPS is mandatory
− MCB open SPC is mandatory
• Add and configure an ‘ATCC fct needs’ object for transformer, via the “Objects entry”
window at transformer module level by clicking on mouse’s right button (1):
(1)
FIGURE 335: ADDING ATCC FUNCTION NEEDS AT TRANSFORMER LEVEL

Once added, the features of ‘ATCC function needs for transformer’ must be set at SCE level:
‘Tpi range’ attributes
− up range
− down range
‘Inhibition conditions’ attributes:
− Overcurrent ratio
(1)
(2)
(3)
FIGURE 336: SETTING GENERAL TRANSFORMER FEATURES OF AN ATCC

When adding ATCC function needs at transformer level, the following mandatory datapoints
are automatically created and must be configured (see section 5 DEFINING DATAPOINT):
(DPT_Trf 1) ATCC on/off
(DPT_Trf 2) ATCC homing
(DPT_Trf 3) ATCC hunting
(DPT_Trf 4) TAP bad TCIP
(DPT_Trf 5) TAP long TCIP
(DPT_Trf 6) TAP invalid
(DPT_Trf 7) Run away
(DPT_Trf 8) ATCC disc eqpt
(DPT_Trf 9) ATCC local bay
(DPT_Trf 10) MCB trip
(DPT_Trf 11) ATCC overcurrent
(DPT_Trf 12) ATCC overvoltage
(DPT_Trf 13) ATCC low-voltage

(DPT_Trf 14) ATCC inv voltage
(DPT_Trf 15) Second. voltage
(DPT_Trf 16) Second. current
(DPT_Trf 17) Second. active P
(DPT_Trf 18) Second. react. Q
(DPT_Trf 1) (DPT_Trf 2)
C0349ENa
FIGURE 337: MANDATORY DATAPOINTS FOR ATCC AT TRANSFORMER LEVEL
6.6.2.5 Defining an electrical topology for ATCC function

For correct behaviour of ATCC function, electrical topology of the LV side, including
connection of the transformer to the busbar and coupling of busbars into the LV level must
be defined.
Any electrical topology can be defined by modules interconnected by nodes.
A node is in relation with at least on module. The most common “node” is busbars.
Electric modules are mostly dipoles. Switchgears and circuit-breakers are connected to two
nodes. Special module cases are:
• motor/generator that are connected to only one node,
• line arrival that is a node,
• special (german) double switch, in fact association of earth switch and disconnector,
• transformer connected to 3 nodes but the third node is reserved to neutral

compensation.
At SCE level, nodes are special attributes of module, whose values are given by integers.
Each identified node in the electrical topology has a unique arbitrary value. Two
interconnected modules share the same node value. The best practice to value nodes is to
do it directly from the substation electrical diagram.
obsolete
FIGURE 338: IDENTIFYING NODES IN ELECTRICAL DIAGRAM (E.G.)

This manual approach of nodes identification must be projected at SCE electrical object
level:
• “Busbar” bay, where one node reference must be filled (1),
• “External line” module of “Feeder” bay, where one node reference must be filled (2),
• “Circuit-breaker” and “Switchgear” module, where two node references must be filled
(3),
• “Transformer” module, where at least two node references must be filled, and a extra
one in case of neutral compensation (4),
• “Capacitor” & “inductor” module, used for neutral compensation, where one node
reference must be filled (5); it corresponds to the neutral node of the associated
transformer.
(1)
FIGURE 339: SETTING BUSBAR NODE REFERENCE (ATCC FUNCTION)

(2)
FIGURE 340: SETTING EXTERNAL LINE NODE REFERENCE (ATCC FUNCTION)
(3)
FIGURE 341: SETTING CIRCUIT-BREAKER NODE REFERENCES (ATCC FUNCTION)
(4)
FIGURE 342: SETTING TRANSFORMER NODE REFERENCES (ATCC FUNCTION)
(5)
FIGURE 343: SETTING CAPACITOR NODE REFERENCES (ATCC FUNCTION)

6.7 Defining an electrical 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 50 ms.
• 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
computer 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 SPSs.
• 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.7.1 Defining an FBD fast automation
To define an FBD fast automation, the three following steps must be done:
• FBD interface definition at SCE level:
− FBD function ‘header’ creation.
− creation of input plugs, that will be linked to SPS, DPS, MV, MPS, SPC or DPC
(fast automations take into account the logical value of these datapoints, defined
for interlocking management), added as sub-objects to this header.
− creation of output plugs, that will be linked to SPC, DPC (control of relays) or to a
SPS (production of SPS real-time value), added as sub-objects to this header.
• FBD body (coding in PSL) definition via launching at SCE level the FBD editor
(contextual menu on the FBD interface object) and doing diagram edition of boolean,
timer and bistable functions, and links to input/output plugs.
• Effective linking of input and output plugs to existing datapoints

6.7.1.1 Creating an FBD fast automation (header definition)
The addition of an 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 344: ADDING AN FBD FAST AUTOMATION (E.G. FOR FEEDER BAY LEVEL)
The FBD fast automation features must be set:
1. Edit the relation ‘runs on’, to set computer PLC manages the automation. This relation
is automatically established by SCE if FBD automation is located under a bay whose
computer manager has ever been entered (inheritance mechanism, for details about
computer manager of a bay refer to section 6.1.4 Defining a Bay).
2. Type the short name and long name of the fast automation used for internal SCE
identification.
FIGURE 345: SETTING FBD FAST AUTOMATION FEATURES

6.7.1.2 Creating FBD input plug (header definition)

The addition of an FBD input plug is done via the “Objects entry” window at the FBD
automation level by clicking on mouse’s right button.
FIGURE 346: 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
FIGURE 347: SETTING GENERAL FBD INPUT ATTRIBUTES

6.7.1.3 Creating FBD output plug (header definition)
The addition of a FBD output plug is done via the “Objects entry” window at the FBD
automation level by clicking on mouse’s right button.
FIGURE 348: 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
FIGURE 349: SETTING FBD OUTPUT PLUG ATTRIBUTES

6.7.1.4 Using FBD editor (body definition)
The launching of the FBD editor is done at FBD automation level via its contextual menu
(right click).
FIGURE 350: 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>
1. FBD Boolean is Boolean type (True / false) input.

2. FBD Input is an input to FBD (Type – SPS, DPS etc.)
3. And Gate
4. TON Ton delay timer
5. FBD Output is output of FBD ( type SPS, SPC etc)
FIGURE 351: USING FBD EDITOR
6.7.1.5 Linking datapoints to FBD inputs and outputs
To assign a datapoint to an 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 352: LINKING A FBD INPUT TO A DATAPOINT

To assign a datapoint to an 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)
(1)
FIGURE 353: 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".
• A "DPC" or "SPC" datapoint can be linked to an Input plug of an FBD Automation

through the relation "uses DPC" or "uses SPC". These relations are not compatible
with the following ones:
• - relations defining the Control Source: "…wired on"

- relation defining the Control Source: "has for IED address"
6.7.1.6 Creating FBD timer plugs

Timer plugs are used to enable/disable the TON/TOFF block output.
Add the object from the Objects entry window:
A new binder Settings holds the timers plugs.

Set attributes of each plugs:
• Visibility and edition with MiCOM S1
• Default value, that is the value till it is not modified with MiCOM S1
• Minimal and maximal values; range is:
− 5 thru 50ms for an accurate timer
− 50ms thru 1h for a standard timer
• Step, that is the resolution and accuracy; minimum value is:
− 1ms for an accurate timer
− 5ms for a standard timer

6.7.2 Defining an ISaGRAF slow automation

The core of the slow automation modelling is a ‘Slow automation’ object that corresponds to
an ISaGRAF project. Slow automation can own datapoints for status, control of automation
itself (automation management); for instance, a load shedding automation can have a control
to put it in/out of service and a relevant status.
They also reference via links datapoints located in system or electrical topologies. There are
two kinds of link:
• ‘client’ link, that means that the slow automation uses the datapoint that is acquired or
managed outside the ISaGRAF automation. For instance, the load shedding
automation can be client of some ‘circuit-breaker status’ input datapoints and some
‘circuit-breaker control’ output datapoints.
• ‘server’ link, that means that the slow automation produces or manages the datapoint.
For instance, a slow automation can be used to produce the sum of feeder
measurements. This sum is also a measurement located at voltage level for instance.
To define a slow automation, do the steps that follow:
• define the slow automation interface:
− create the slow automation ‘header’
− if required, create the datapoints at slow automation level, used for the function
management
− create the client links for the slow automation
− create the server links for the slow automation
• define the slow automation body definition via launching from the SCE the ISaGRAF
editor (contextual menu on the slow automation interface object) and using available
languages and previously client/server defined links
• establish the effective client/server links entering to existing datapoints.

6.7.2.1 Creating an ISaGRAF slow automation (header definition)

To add an ISaGRAF slow automation, tap into the “Objects entry” window at any level of the
electrical topology (except Site and module): select ‘Slow automation’ and right click Add.
topology.
FIGURE 354: ADDING AN ISAGRAF SLOW AUTOMATION AUTOMATION

(E.G. FOR FEEDER BAY LEVEL)
ISaGRAF slow automation features must be set at SCE level:
1. Fill the relation ‘runs on’, giving which computer PLC will manage the automation. This
relation is automatically filled by SCE if slow automation is located under a bay whose
computer manager has ever been entered (for details about computer 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
FIGURE 355: SETTING ISAGRAF SLOW AUTOMATION FEATURES

6.7.2.2 Adding specific datapoints to slow automation (interface definition)

To add a slow automation datapoint, tap into the “Objects entry” window at slow automation
DATAPOINT.
FIGURE 356: 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 computer non-volatile memory to restart on
their latest known values in event of computer reboot.
6.7.2.3 Creating ISaGRAF client link (interface definition)

The addition of an ISaGRAF client is done via the “Objects entry” window at the slow
automation level by clicking on mouse’s right button and adding a ‘is client of’ relation.
Choose the correct relation depending on datapoint kind to use.
FIGURE 357: ADDING AN ISAGRAF CLIENT LINK

6.7.2.4 Linking a datapoint to an ISAGRAF client link

To link a datapoint to an ISAGRAF client link, define the relation 'is client of'. For that
double click this relation (1). The Relation Link Editor is then displayed. Expand the tree view
to list all the available SPS datapoints. 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).
FIGURE 358
6.7.2.5 Defining Isagraf IO prefix for an input

Click this 'is client of' relation to display the associated attributes window. 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 the concatenation of 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 359: DEFINING ISAGRAF IO PREFIX FOR AN INPUT

• first character: letter only
• following characters: capital, digit or underscore
• maximum length: 80 characters

6.7.2.6 Creating ISaGRAF server link (interface definition)
To add an ISaGRAF server, tap into 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 to manage.
FIGURE 360: ADDING AN ISAGRAF CLIENT LINK

6.7.2.7 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). This displays the Relation Link Editor. Expand the tree view
to list all the available DPS datapoints.. 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).
FIGURE 361: LINKING A DATAPOINT TO AN ISAGRAF SERVER LINK

6.7.2.8 Defining ISaGRAF IO prefix for an output

Click this manages' relation to display the associated attributes window.. You can modify
only the 'Isagraf IO prefix' attribute (4). This attribute defines the prefix of the identifier of
this datapoint when used in ISaGRAF workbench as an output signal of this automation. It It
is the concatenation of 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 is: My_Output_Prefix_out_0
FIGURE 362: DEFINING ISAGRAF IO PREFIX FOR AN OUTPUT

Configuration rules and checks:
• first character: letter only
• following characters: capital, digit or underscore
• maximum length: 80 characters

6.7.2.9 Using ISaGRAF editor (body definition)
To launch the ISaGRAF editor at RT automation level via, right click ISaGRAF Edit.
FIGURE 363: LAUNCHING ISAGRAF EDITOR

ISaGRAF editor allows diagram edition of the automation. For details about ISaGRAF
workbench and SCE datapoint coupling, refer to SCE_ENAP.Erreur ! Source du renvoi
introuvable..
FIGURE 364: USING ISAGRAF EDITOR

6.7.3 Defining a group
A group is a logical OR, AND, NOR or NAND combination of components whose kind is
SPS, DPS or groups. A component can belong to several groups. Resulting datapoint
associated to a group is a SPS object called ‘Group SPS’ in data modelling.
Group SPS can only belong to bays or modules. The computer 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.
topology.
FIGURE 365: 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.
FIGURE 366: 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)
(1)
FIGURE 367: ADDING A COMPONENT TO A GROUP

6.7.4 Controlling xPC by xPS change of state

For specific needs, some SPS or DPS can act on SPC or DPC. This relation is called xPS-
xPC association. Such an acted xPC may or may not need a channel for wiring. It can be an
xPC used for automation management for instance.
The link defines for each state of the xPS which order must be sent.
To create such a relation:
• Add the relation ‘controls on state change’ (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).
FIGURE 368: CONTROLLING XPC THROUGH XPS (E.G.)

New attribute: Control, whose values can be
• “direct to output relay” i.e the xPS activates directly the associated xPC
• “through control sequence” i.e. the xPS activates a full control sequence
In case of controls launched by an xPS, the Control Originator fields are:
• orCat = Bay level
• orIdent = xPS label

6.7.5 Producing a DPS from two SPSs

For specific needs, two SPSs (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 SPSs:
• 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 369: PRODUCING DPS FROM 2 SPSS (E.G.)

6.7.6 Defining interlocking
Any DPC (or SPC) belonging to a bay or module can have interlocking equation for opening
order (Off order for SPS) and/or closing order (On order for SPC).
Interlocking equation corresponds to a logical function that must be ‘true’ to send the order.
In data 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).
topology.
FIGURE 370: 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 SPS datapoint.
To define interlocking equation for an interlock SPS:
• Add at interlock SPS level, an FBD interlock object (1)
• Configure this FBD interlock (refer to section 6.7.1 Defining an FBD fast automation),
with the existing following restrictions:
− only input plugs are available for its interface definition.

− For its body description via FBD editor, timer and bistable functions do not exist.
FIGURE 371: DEFINING INTERLOCKING EQUATION FOR AN INTERLOCK SPS

6.7.7 Defining an automatic/manual dependency

Automatic/manual dependency can be set at control level (SPC, DPC or SetPoint):
When a control is linked to a SPS or DPS via the automatic/manual dependency, control is
refused if the SPS (resp. DPS) is in the SET (resp. CLOSED) state.To create an
automatic/manual dependency:
• Add the relation ‘has for AutoManu dependency’ (1) at control level; two relations are
available depending on the input kind setting the dependency (SPS or DPS). Choose
the correct one.
• Fill the relation with the relevant SPS or DPS (2).
FIGURE 372: 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.
6.8 Defining a Fast Load Shedding application

The goals of the The Fast Load Shedding include:
• Increasing the speed of the Load Shedding process using GOOSE system
message exchange
• Including IsaGraf functions for Load Shedding priority process and topology
calculation
6.8.1 Data flow
Input xPS triggers

Output MASK result to CB breaker
SetPoint LSP config
Goose status
C264 M
IEC 61850
IsaGraph
OI or (Scada+GTW) Begin
Set_LSP (MaskPrio, REF_LSP1-1)
SetPoint for MaskPrio x LSP1-1 Set_LSP (MaskPrio, REF_LSP2-1)
…
SetPoint for MaskPrio x LSP2-1 Set_LSP (MaskPrio, REF_LSPi-1)
End
SetPoint for MaskPrio x LSPi-1
C264 F1 C264F2 C264 Fi

LSPi-1
LSP1-1
LSP2-1
MASK PSL 1-1 MASK PSL 2-1 MASK PSL i-1

- - -
R output MASK
R output MASK
R output MASK
xPSTriggers xPSTriggers xPSTriggers

input input input
C0497ENa
The C264-M supports the ISAGRAF automation which allows defining FLS preselections
and also automations (ISAGRAF and/or PSL) which allow to test / simulate the FLS.
It is a client of the OI and receives the setpoints from it. The FLS preselections are
transmitted to C264-Fi using the LSP (Load Shedding Preselection) datapoints, transmitted
by GOOSE.
It is a server of the OI and is used to re-transmit the datapoints coming from C264-Fi to OI
using datapoint associations mechanisms.
The C264-Fi control the feeder and the breaker trip.
In order to secure performance time of breaker trip, C264-Fi are not servers of the OI and
C264-M. They only manage the PSL which allows to trip the feeder regarding the cause and
the preselection. They are dedicated to the acquisition of datapoints used for the Fast Load
Shedding function (only FLS triggers as input and breaker trip as output).
The C264-Fi can be redundant. To avoid time performance limitation, the client/server
mechanism used in case of C264 redundancy (to exchange the FailSt information) will be
replaced by a GOOSE transmission of this information.
6.8.2 Priority Setpoints
Priority setpoints are analogue setpoints whose value range from 0 to 65535.
The profile is as follows:
6.8.3 Load Shedding Preselection (LSP)

LSP is a 16 bit word in which several bits can be simultaneously set.
The LSP can be created under a module object or a breaker object.
The LSP is a sub-type of the MPS object. The SCE attributes of this object are:
• Short name
• Long name
• Meaning: fixed to “load shedding preselection”
• Used profile – The profile is only used to define the printing / archiving status at OI
level (alarms, interlocking values are not used).
No wiring, nor SCADA address can be associated to this object.

An LSP cannot be forced, suppressed or substituted (FSS).
This dedicated PACiS object is mapped on an IEC61850 BSTR16 type:
The Goose transmission can be automated (auto-addressing).

The LSP are not saved in C264-Mx non-volatile memory.
In case of C264-Mx re-initialisation (or, in case of C264-M redundancy, when the Standby
becomes Active), the LSP are initialized to 0.
The owner of the LSP is the C264-Mx (and its redundant if it exists): it is the GOOSE
publisher and the server of the LSP. So this computer must be clearly identified in the
configuration: a relation “has for LSP manager” is defined at Site level to define this
computer. Dedicated GOOSE message is used to transmit LSP (i.e. measurement GOOSE /
status GOOSE are not used): in this GOOSE, only the LSP status is transmitted: the quality
and time-stamp are not transmitted.
6.8.4 Graphical animation with LSP

Graphical animation is performed using an LSP Multistate. This object is composed of:
• 3 graphical symbols, associated to the ON, OFF and UNKNOWN states of the LSP
bits
• Up to 16 components which allow to define the graphical position of the symbol

associated to each LSP bit
This representation forces to have the same graphical representation for the 16 bits of the
LSP.
6.8.5 Use of LSP in PSL
A dedicated MASK operator allows to use the LSP in a PSL:
This operator is equivalent to:
NOTE: The MASK operator is generated as a sum of products in the C264

database. The PSL limitations are applicable on this operator.
6.8.6 Use of LSP in ISaGRAF scheme

An ISaGRAF function allows to define LSP values. The prototype of this function is:
Unsigned char Set_LSP (int Value, long Ref_LSP)
The bit representation of the LSP is:
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
6.8.6.1 Set_LSP() ISaGRAF function

ISaGRAF manages the LSP registry through a new function call Set_LSP.(value, reference
of nMPS)
An LSP registry is a 16bits value range which defines 16 bits priority mask. The value is in
range [0x0000 to 0xFFFF] which represents the 16 bit priority.
Value 0x0001 activate bit priority 1
…
One LSP registry is allocated to a MASK FBD/PSL object.
This LSP registry is sent from ISaGRAF to C264 Fi FBS/PSL through GOOSE status.
6.8.6.2 Is_connected_to() ISaGRAF function
This Isagraf function is_connected_to(node1,node2,state) may be is used for operation
topology process.
The test of this function will be applied to the architecture as described below
The state as described in the specification can be
• Connected: the 2 node equipments are surely connected,
• Unconnected: the 2 node equipments are surely not connected
• Uncertain: if not connected or not unconnected (in the event of a faulty board
connection measurement for example)
6.8.7 Datapoints
For SPC data Point:
• value = 0 for open state
• value = 1 for close state

Datapoints possible states:
• LSP: the possible states are SET, RESET, UNKNOWN.
• Input xPS Triggers can be SPS, DPS. The possible states are described into the
Product specification document. The FSS can be applied to the xPS datapoints
Each bit of the LSP datapoint is graphically created at OI part.
6.8.8 MASK object and xPS triggers
6.8.8.1 MASK object
For each command breaker using into Fast Load Shedding, a PSL/FBD is created.
This PSL included the new MASK object.
One or more MASK object can be created into the FBD/PSL.
This MASK object has:
• One Input LSP value. The LSP value is GOOSE sending from Isagraf.
• Up to 16 xPS input triggers.
• One xPS output open/close breaker command.

6.8.8.2 Trigger definition
The triggers are standard xPS. As soon as they will be used in a PSL, they will be
automatically GOOSE-defined using the SBUS automatic addressing.
An xPS input Trigger is mapped on input bit priority MASK Object of PSL/FBD
The combination of the xPS input triggers and the ISaGRAF LSP (transmitted by GOOSE)
process the output PSL command datapoint (link to a breaker command).
The xPS input triggers state can be changed from:
• C264 front panel Fi input command
• Scada Equipement Simulator through ASE gateway
• OI button with SPC command and SPS feedback
• Other IED equipment
• Another C264 Fi
Wired triggers can be connected to extension rack or not.
Options:
• all xPS triggers are managed by the same computer:
• xPS triggers comes from another C264 Fi:

• multiple MASK objects can be created into a FBD/PSL:
• xPS triggers comes from another C264 M, C264P (frequency threshold), SPS from out
of range measurement:
6.8.9 Topology calculation

An ISaGRAF function allows to define if 2 devices are connected:
is_connected_to (node1, node2, state) with state = connected, unconnected, uncertain, and
node1 / node2 the reference of the nodes of the 2 devices.
The FORCED <state> and SUBSTITUTED <state> status are taken into account as the
normal <state> of the datapoint in the topology calculation. The SUPPRESSED status is
taken into account as the UNKNOWN status.
Two nodes are connected if it exists at least one chain of devices between the 2 nodes
which are closed, forced closed or substituted closed. Two nodes are unconnected if all
chains of devices between the 2 nodes are open, forced open or substituted open. In all
others cases, the status between two nodes is uncertain.
6.8.10 Operator Interface example

6.9 Defining a Load application (C264 standalone RTU)

A Load function can be either a Load Shedding function or a Load Curtailment function.The
“Type” attribute of “Load function” object allows to select either. The creation of a Load
function template can’t be done; it is only possible in Object mode.
All data points of a “Load function” object have a predefined profile. The user can change it if
he/she wishes it.
Restrictions on the “Load function” object and its children in the browser:
• Once the “Load function” object is edited, the user can’t change its type,
• No child of “Load function” object can be added from the Object Entry Area,
• No child of “Load function” object can be deleted in the browser,
• The “Load function” object and its components can’t be ‘’spared’’,
• The “number” attribute of a “Load group” is not modifiable,
• The “number” attribute of a “Load blocking” is not modifiable,
• No predefined profile available for data points of a “Load function” object can be
deleted.
The user can edit a “Load function” by the contextual menu “Load function Edit …” as show it
the figure below:
Fill out the window fields:

7. DEFINING COMPUTER LOCAL HMI

All kinds of computers (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 the GHU2xx board),.
7.1 Defining a bitmap table
To define computer bay mimics, bitmaps are used. Their definition is located at graphic root
of the data modelling.
At computer bay mimic definition level, objects only reference these bitmaps. So it is an
easier way to propagate a bitmap change for instance to all objects that reference it.
At SCE level, bitmap object definition is extended to embed animation: up to 5 elementary
static bitmaps can be grouped in a bitmap object:
• one (mandatory) for default representation
• one for ‘open’ (or reset) representation
• one for ‘closed’ (or set) representation
• one for ‘open withdrawn’ representation
• one for ‘closed withdrawn’ representation

Each representation corresponds to a filename containing the static bitmap definition.
The addition of a bitmap definition is done via the “Objects entry” window at Bitmap table
level of the graphical topology by clicking on mouse’s right button.
FIGURE 373: ADDING A BITMAP

Once added, bitmap attributes must be set at SCE level:
1. short name and long name: used for internal SCE identification.
2. reference index (range [0, 150]: that must be unique for the set of defined bitmaps.
This index will be used in bay mimic definition as described previously.
3. type (Single / 5-uple): single is used for static bitmap definition, 5-uple allows dynamic
bitmap definition as described previously.
4. file name by default: corresponds to the filename containing the bitmap definition
used for default representation.
5. file name for 'open' state: visible only if type is set to 5-uple: corresponds to the
filename containing the bitmap definition used for open state representation.
6. file name for 'closed' state: visible if type is set to 5-uple: corresponds to the
filename containing the bitmap definition used for closed state representation.
7. file name for 'withdrawn open' state: visible if type is set to 5-uple: corresponds to
the filename containing the bitmap definition used for withdrawn open state
representation.
8. file name for 'withdrawn closed' state: (visible if type is set to 5-uple): corresponds
to the filename containing the bitmap definition used for withdrawn closed state
representation.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 374: SETTING BITMAP ATTRIBUTES

Attributes (7) and (8) can be omitted if breakers and switchgears represented in bay mimic
are not concerned with withdrawn information.
To set a file name (attributes (4) to (8)) and define graphically a bitmap:
• select the attribute
• edit graphically a bitmap using the bitmap editor at SCE level
• save the graphical definition of the bitmap by giving a file name in bitmap editor
For details about bitmap editor usage refer to SCE user’s manual.
FIGURE 375: USING BITMAP EDITOR

Color usage in bitmap editor is not significant for computer monochrome LCD.
• The "reference index" attribute value of each "Bitmap" of the "Bitmap table" must be
unique.
• Depending on the "type" attribute value, 1 or 5 PNG file(s) can be linked to a Bitmap.
For each one, the bitmap size must be ≤ 512 bytes.
7.2 Defining a computer workspace

Via a complete GHU200 board (refer to section 4.4.2.2 Setting specific features of the
GHU2xx board), each computer with local HMI references a workspace that groups its bay
mimic definitions. Computer workspaces can not be shared by several computers because
mimics are local to bays managed by a specific computer.
Up to 24 bay mimics can be put in a computer workspace, and up to 2 mimics can be linked
to the same bay.
Usual labels are used by computer local HMI (LHMI). They are located for all computers
LHMI in one object grouping all translatable labels, located in “computer workspaces” folder
in Graphic topology.
7.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 376: 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 377: ADDING A COMPUTER WORKSPACE

7.3 Defining a computer bay mimic

7.3.1 Creating a computer bay mimic
The addition of a computer bay mimic is done via the “Objects entry” window at computer
workspace level by clicking on mouse’s right button.
FIGURE 378: ADDING A COMPUTER 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 computer
LHMI level (1 or 2).
(1)
(2)
(3)
(4)
(5)
FIGURE 379: 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 380: CORE STRUCTURE OF BAY MIMIC

For more details about computer LCD usage, refer to document User Interface (coded HI for
Human Interface) of MiCOM C264 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 computer managing a bay represented by a "Bay mimic" must be the same as the
one linked to the "Comp. workspace" (computer workspace) of this "Bay mimic".
• A bay can be represented by 0, 1 or 2 "Bay mimic". Each "represents" relation has an

attribute "mimic rank for the set of bay mimic". In the case of 2 relations, each attribute
value must be unique.
• For a Computer, the maximum count of managed bays (relation "is managed by")
which are linked to a "Bay mimic" (relation "represents"), is 12.
• Limits of the count of symbols:
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 computer bay mimic is described via graphical basic shapes:
• LHMI line: horizontal or vertical line with configurable thickness and length
• LHMI bitmap: bitmap that references a bitmap object in the bitmap table (see 7.1
Defining a bitmap) 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 381: ADDING A LINE IN COMPUTER 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 382: 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 383: ADDING A BITMAP IN COMPUTER 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
Defining a bitmap table)
(1)
(2)
(3)
(4)

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 385: ADDING A FIXED TEXT IN COMPUTER BAY MIMIC

Once added, fixed text attributes must be set at SCE level:

1. fixed text value: text to display at mimic level

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 computer bay mimics, 3 kinds of objects are available:
• Pre-defined dynamic text, used:
− to display local/remote and SBMC status of the bay

− to manage Synchrocheck and interlock bypass during control sequence on the
bay
− to display time and 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
computer for command purpose at local HMI level, via the existence of the relation ‘is
feedback of’ between the xPS and the xPC.
• A generic module is composed of 2 sub-objects:
− a name for display (mandatory)
− a ‘xPS muti-state’ for dynamic module state display (mandatory), referencing a

dynamic bitmap object in the bitmap table, and whose relation to a xPS
datapoint (SPS or DPS) has to be filled up to precise animation datapoint
• Transformer representation: used to display transformer module; linked to 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 387: ADDING TIME INFORMATION IN COMPUTER 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
FIGURE 388: 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 389: 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 390: ADDING SBMC INFORMATION IN COMPUTER BAY MIMIC

Depending on customer’s need, SBMC information can be positioned at any location in bay
mimic:
• by editing the coordinates of the object

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 391: ADDING A GENERIC MODULE IN COMPUTER 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
Defining a bitmap table)
7. module name value: text displayed on LCD (up to 4 characters)
(1)
(2)
(3)
(4)
(5) (7)
(6)
FIGURE 392: 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 393: ADDING A GENERIC MODULE IN COMPUTER 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
Defining a 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 394: 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 395: ADDING A TPI INFORMATIION IN COMPUTER BAY MIMIC

Once added, TPI information can be positioned at a different location:

• by editing the X-coordinate and Y-coordinate attributes of the object
• The link from an element to its bitmap is defined with the attribute: "bitmap reference".
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 396: 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
FIGURE 397: 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 computer
can be displayed via the Leds of its GHU200 board.
(1)
FIGURE 398: 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 399: SETTING LED STATUS FOR A DATAPOINT (E.G. FOR SPS DATAPOINT)
Configuration and checks
• If the value of the "HMI type" attribute is "Simple", then "Led#4" must not be used (no
relation link from "Led#4" to a datapoint).
GLOSSARY
Page 1/14
CONTENTS

2. GLOSSARY 4
PACiS/EN LX/D10 Glossary
Page 2/14
BLANK PAGE
Page 3/14

This document is the last chapter of each PACiS documentation. It is the glossary.
Page 4/14
2. GLOSSARY
AC Alternating Current
AccI Accumulator Input
ACSI Abstract Communication Service Interface
Mapping from the standard IEC 61850 abstract specification of
communication service to a concrete communication infrastructure based
on CORBA.
A/D Analog/Digital
ADC Analog to Digital Converter
AE qualifier Application Entity qualifier
Used internally by IEC 61850 to identify a server application
AI Analog 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 Analog Input Unit ( C264 Bay Computer board name for DC Analog Input)
Alarm An alarm is any event tagged as an alarm during the configuration phase
AO Analog Output
Value corresponding to a desired output current applied to a DAC.
AOU Analog Output Unit ( C264 Bay Computer board name for Analog 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 the OSI protocol for applicable 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
Automatic system used to regulate the 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 equipment (switchgears and transformers) and
devices (Protective, Measurement…) usually encompassing a Circuit
Breaker and ancillary devices, 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 a 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 associated with Remote/Local control.
BCU Bay Control Unit
Name given to the C264 controlling a bay. Usually in contrast to
Standalone.
Page 5/14
BI Binary Input (or Information)

Designation of already filtered data entered into the C264 Bay Computer
before they become SPS, DPS with time tag and quality attributes
BIU Basic Interface Unit
C264 board for auxiliary power supply, watchdog relay, redundancy I/O
BNC A connector for coaxial cable.
B-Watch Monitoring and control device for GIS substation.
CAD Computer Aided Design
Computer application dedicated to the design of wiring, for example.
CAS CASe
C264 Bay Computer rack
CAT Computer Administration Tool
CB Circuit Breaker
Specific dipole switch with the capability to make line current and break
fault current. Some have isolation capability, i.e. nominal grounding
(earthing) 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
C264 Bay Computer board dedicated to switch control with 8DI, 4 DO
CDM Conceptual Data Modeling
This is the modeling of system/devices data using a hierarchy of
structured data (called object or class) with their attributes, methods or
properties and the relations between each other. It maps common data to
devices or components of devices, with guarantee of interoperability.
Class Defined in IEC 61850 as: description of a set of objects that share the
same attributes, services, relationships, and semantics
Client Defined in IEC 61850 as: entity that requests a service from a server and
that receives unsolicited messages from a server
CM Commissioning
CMT Computer Maintenance Tool
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
C264 Bay Computer main board based on a Power PC
CRC Cyclic Redundancy Check
Coding result sent 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 a predefined character or string as in Excel or
ASCII Comtrade.
CT Current Transformer
Basically the electric device connected to process and extract a current
measurement. By extension, part of a device (C264) that receives an AC
value and converts it into a numerical measurement value.
CT/VT Current and Voltage transformers
(Conventional) By extension, the C264 TMU board.
Page 6/14
CT/VT Current and Voltage transformers

(Non- New generation of transducer based for example on light diffraction under
Conventional or an electric field. Without transformer, gives a direct numerical
intelligent) measurement of voltage and current as a communicating IED.
CSV Character Separated Values
ASCII values separated by predefined character or string as in Excel or
ASCII Comtrade.
DAC Data Acquisition component of the GPT
DAC Digital to Analog Converter
Used to generate an analog signal (usually DC) from a digital value.
DB DataBase
Tool or set of data that defines the entire configuration of a system or
specific device such as a computer. In contrast to a setting or parameter,
the DB has a structure that cannot be modified on-line. DBs 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 an undefined state of a double point when inputs are not
complementary. DBI00 signifies dynamic state or jammed. DBI11 signifies
undefined.
DBID Databases Identity Brick
DC Direct Current
DC, DPC Double (Point) Control
Two digits and/or relay 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 switching
operations, for example)
DE Direct Execute
DELTA Phase-to-phase delta values
Device Term used for one of the following units:
Protective relays, metering units, IED, switchgear), disturbance or quality
recorders.
Switchgear: switching device such as a CB, disconnector or grounding
(earthing) switch
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.
Page 7/14
DIN Deutsche Institut für Normung

The German standardization body.
DIU DC Input Unit
C264 Bay Computer 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
A measurement value with acquisition by DI and a specific coding BCD,
Gray, 1-out-of-n, and so on.
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
attribute has a degree of freedom if a user can modify its values on its
instances
DOU Digital Output Unit
C264 Bay Computer board name for Digital Output
DP Double Point
Information/control derived from 2 digital inputs/output; usually employed
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 synchronization and standardized
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.
EWS Engineering Workstation
FAT Factory Acceptance Test
Validation procedures execution with the customer at factory.(i.e. SAT)
FBD Functional Block Diagram
One of the IEC 61131-3 programming languages (language used to define
configurable automation).
FIFO First In First Out
FO Fiber-Optic
FP Front Panel
Page 8/14
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 protocols. The RTU function of the
C264 gives a gateway behavior to SCADA or RCP level. PACiS Gateway
is separate PC base device dedicated to this function.
GHU Graphic Human interface Unit
C264 Bay Computer Front Panel digital part (LCD, buttons, Front RS)
GIS Gas Insulated Substation
GLOBE GLOBE Brick
GMT Greenwich Mean Time
Absolute time reference
GPS Global Positioning System
Based on triangulation from satellite signals.
Also transmits absolute GMT time used to synchronize 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 the position of a device manually (position
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).
HELPS Hostable Emulator for Load and Protocol Simulation. HELPS simulates
an Intelligent Electronic Device (IED)
HMGA Horizontal Measurement Graphical Area
HMI Human Machine Interface
Can be PACiS OI (Operator Interface) or C264 LCD (Local Control
Display) or set of LEDs, mosaic...
HSR High Speed Auto-Recloser, first cycles of AR
HTML Hyper Text Mark-up Language
Used as standard format for 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 synchronization based on an analog signal.
Page 9/14
JAMMED Invalid state of a Double Point:

Occurs when two associated digital inputs are still in state 0 after a user-
selected delay, i.e. when the transient state “ motion ” is considered as
ended
Kbus Term used for the Courier protocol on a K-Bus network (RS 422 type).
(Kbus Courier)
LAN Local Area Network
L-BUS Legacy Bus
Generic name of Legacy or field networks and protocols that are 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 Schneider Electric or MODICON
LCD Liquid Crystal Display or Local Control Display (on C264)
LD Ladder Diagram, one of the IEC 1131-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
Control Mode can be issued from this point, or in remote control from higher-level
devices.
LSB Least Significant Bit
LSP Load Shedding Pre-Selection
LV Low Voltage
MAFS Marketing And Functional Specification
MC Modular Computer
MCB Mini Circuit Breaker. Position associated to the tap changer.
MDIO Management Data Input/Output
A standard driven, dedicated-bus approach that is specified in IEEE 802.3
Measurements Values issued from digital inputs or analog inputs (with value, state, time
tag)
Metering Values computed depending on the values of digital or analog inputs
(non-tariff) during variable periods of time (time integration).
Metering Values computed depending on the values of digital or analog inputs
(tariff) during variable periods and dedicated to the energy tariff. These values
are provided by dedicated “tariff computers” 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. Standard MODICON or Schneider Electric.
Module Word reserved in PACiS SCE for all electric HV devices. It groups all
switch-gear devices, transformers, motors, generators, capacitors, …
Page 10/14
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 during which, a primary device is running in the
energized state. For example, a circuit breaker is in Closed state and the
current is not equal to 0 A.
OSI Open System Interconnection
Split and define communication in 7 layers : physical, link, network,
transport, session, presentation, application
OWS Operator WorkStation (PACiS OI)
PACiS Protection, Automation and Control Integrated Solutions
PLC Programmable Logic Control /Chart. Includes PSL and ISaGRAF.
The configurable control sequences or automations taken into account by
the MiCOM Systems are defined within the PLC program.
POW Point On Wave
Point on wave switching is the control process of the three poles of an
HV-circuit breaker in a manner that to minimizes the effects of switching.
PSL Programmable Scheme Logic
PSTN Public Switched Telephone Network
RCC Remote Control Centre
Computer or system that is not part of a MiCOM system. RCC
communicates with and supervises a MiCOM system using a protocol.
Page 11/14
RCP Remote Control Point

Name given to the device or part used to control remotely several bays or
sub-stations. Usually associated with Remote/Local sub-station control. It
is a SCADA interface managed by the MiCOM system through the
Telecontrol BUS. Several RCPs can be managed with different protocols.
Remote Control When set for a control point, it means that the commands are issued from
Mode 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 analog 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 work is being done on an HV feeder
RSVC Re-locatable 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 Re-Locatable Static Var Compensator
RTC Real Time Clock
RTU Remote Terminal Unit
Stand-alone computer that acquires data and transmits 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 to the RCP anymore (they are
“automatically” suppressed).
SBO Select Before Operate
A control made in two steps, selection and execution. The selection phase
gives a feedback. It can be used to prepare, reserve during time,
configure a circuit before execution. Controls are done into a protocol, or
physically (select with DI Select then DO execute).
S-BUS Station Bus, network between PACIS devices.
SCADA Supervisory Control And Data Acquisition
Equivalent to RCC
SCD Description file extension
SCE System Configuration Editor
SCL Substation automation system Configuration Language ( IEC 61850-6)
Page 12/14
SCP Substation Control Point

Name given to the device or part used to control several bays or
substation locally. Usually associated with Remote/Local substation
control. It is commonly the 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 Defined in IEC 61850 as: entity that provides services to clients or issues
unsolicited messages
Setpoints Analog setpoints are analog outputs delivered as current loops. Analog
(analog) setpoints are used to send instruction values to the process or auxiliary
device
Setpoints Digital values sent on multiple parallel wired outputs. Each wired output
(digital) represents 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 IEC 1131-3 programming languages (language used to define
configurable automation).
SI System Indication
Binary information that does not come from an external interface. It is
related to an internal state of the computer (time status, hardware faults,
and so on). It is the result of all inner functions (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-Distortion to Noise-plus-Distortion ratio, in dB
SIT Status Input Double Bit
SMT System Management Tool
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 IEC 1131-3 programming languages to define configurable automation
STP Shielded Twisted Pair
Substation Bay computer used at substation level
computer
SUI Substation User Interface
Suppression A binary information belonging to a bay in SBMC mode will be
(Automatic) automatically suppressed for the remote control. However changes of
state will be signaled locally, at SCP
Suppression A binary information can be suppressed by an order issued from an
(Manual) operator. No subsequent change of state on “suppressed information ”
can trigger any action such as display, alarm and transmission
Page 13/14
SWR Switch Redundant

C264 Bay Computer board Ethernet switch with redundant Ethernet
SWU Switch Unit ( C264 Bay Computer board Ethernet switch)
T101 Term used for IEC 60870-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 RS 232, RS 485 or
Ethernet (T104). Protocols are IEC 60850-5-101 (T101), Modbus
MODICON
TC True Contact
TCIP Tap Change in Progress
TCU Transformer Current Unit
C264 Bay Computer CT/VT board : Current acquisition
TDD Total Demand Distortion, similar to the THD but applied to currents and
with a rated current (In) as reference
TG Telecontrol Gateway
THD Total Harmonic Distortion, sum of all voltage harmonics
TI Tele Interface
TM Analog Measurement
TMU Transducer-Less Measurement Unit
Topological Interlocking algorithm, based on evaluation of topological information of
interlocking the switchgear arrangement in the HV network, the switchgear type and
position, and 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

C264 Bay Computer 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 pulses to Measurement value.
Both data (integer and scaled floating) are in a common class UCA2
Accumulator.
UTC Universal Time Co-ordinates (or Universal Time Code)
This designation replaces GMT (but it is practically the same for our
purposes).
VdBS Versioned data Base System, databag generated by SCE & ready to
download
VDEW Term used for IEC 60870-5-103 protocol
VDU Visual Display Unit
VMGA Vertical Measurement Graphical Area
Page 14/14
Voltage level Set of bays, whose plants & devices deal with the same voltage (for
example, 275 kV)
VT Voltage Transformer
Electric device connected to process and extract a voltage measurement.
By extension, part of a device (C264) that receives this AC value and
converts it to a numerical measurement value. VTs are wired in parallel.
WTS Windows Terminal Server, Microsoft remote desktop connection

WYE Three phases + neutral AI values
xPC Single Point Control, Double Point Control
Customer Care Centre
http://www.schneider‐electric.com/CCC
© 2013 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: C264/EN O/D10 04/2013

Micom C264/C264C: Bay Computer

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Micom C264/C264C: Bay Computer

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 C264/C264C: Bay Computer

Uploaded by

Copyright:

Available Formats

MiCOM C264/C264C Page 1/2

Safety & Handling C264/EN SA/D10

Introduction C264/EN IT/D10

Technical Data C264/EN TD/D10

Functional Description C264/EN FT/D10

Hardware C264/EN HW/D10

Connection C264/EN CO/D10

Human Machine Interface C264/EN HI/D10

Application C264/EN AP/D10

Glossary PACiS/EN LX/D10

Page 2/2 MiCOM C264/C264C

SAFETY & HANDLING

MiCOM C264/C264C 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 C264/C264C

MiCOM C264/C264C Page 3/12

Page 4/12 MiCOM C264/C264C

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 C264/C264C Page 5/12

Insulation and dielectric strength testing

Page 6/12 MiCOM C264/C264C

3. DECOMMISSIONING AND DISPOSAL

MiCOM C264/C264C 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 C264/C264C

5. HANDLING OF ELECTRONIC EQUIPMENTS

MiCOM C264/C264C Page 9/12

6. PACKING AND UNPACKING

Page 10/12 MiCOM C264/C264C

MiCOM C264/C264C Page 11/12

8. COPYRIGHTS & TRADEMARKS

Page 12/12 MiCOM C264/C264C

9. WARNINGS REGARDING USE OF SCHNEIDER ELECTRIC PRODUCTS

MiCOM C264/C264C Page 1/8

2. INTRODUCTION TO MiCOM GUIDES 4

3. INTRODUCTION TO MiCOM APPLICATIONS 6

Page 2/8 MiCOM C264/C264C

MiCOM C264/C264C 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 C264/C264C

2. INTRODUCTION TO MiCOM GUIDES

MiCOM C264/C264C Page 5/8