RTU Training Course Description 2014

MiCOM C264/C264C
Bay Computer
C264/EN T/C80
Technical Guide
Technical Guide C264/EN T/C80
MiCOM C264/C264C Page 1/2
MiCOM C264/C264C
BAY COMPUTER
CONTENTS
Safety & Handling C264/EN SA/C80
Introduction C264/EN IT/C80
Technical Data C264/EN TD/C80
Functional Description C264/EN FT/C80
Hardware C264/EN HW/C80
Connection C264/EN CO/C80
Installation C264/EN IN/C80
Settings C264/EN ST/C80
Communications C264/EN CT/C80
Commissioning C264/EN CM/C80
Commissioning Record Sheet C264/EN RS/C80
Maintenance C264/EN MF/C80
Lexicon C264/EN LX/C80
ANNEX: Communication ETHERNET Switches C264/EN AN/C80

C264/EN T/C80 Technical 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/C80 Safety & Handling
BLANK PAGE
1. INTRODUCTION
This document is a chapter of the MiCOM C264/C264C documentation. It describes the
safety, handling, packing and unpacking procedures applicable to MiCOM C264/C264C
modular computer series and associated equipment's and software tools.
2. HEALTH AND SAFETY

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

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

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

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

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

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

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

European Commission
Low Voltage Directive.
5. HANDLING OF ELECTRONIC EQUIPMENTS

A person’s normal movements can easily generate electrostatic potentials of several
thousand volts.
Discharge of these voltages into semiconductor devices when handling circuits can cause
serious damage, which often may not be immediately apparent but the reliability of the circuit
will have been reduced.
The electronic circuits of Schneider Electric products are immune to the relevant levels of
electrostatic discharge when housed in their cases. Do not expose them to the risk of
damage by withdrawing modules unnecessarily.
Each module incorporates the highest practicable protection for its semiconductor devices.
However, if it becomes necessary to withdraw a module, the following precautions should be
taken in order to preserve the high reliability and long life for which the equipment has been
designed and manufactured.
1. Before removing a module, ensure that you are a same electrostatic potential as the
equipment by touching the case.
2. Handle the module by its front-plate, frame, or edges of the printed circuit board. Avoid
touching the electronic components, printed circuit track or connectors.
3. Do not pass the module to any person without first ensuring that you are both at the
same electrostatic potential. Shaking hands achieves equipotential.
4. Place the module on an antistatic surface, or on a conducting surface, which is at the
same potential as you.
5. Store or transport the module in a conductive bag.
More information on safe working procedures for all electronic equipment can be found in
IEC 60147-0F and BS5783.
If you are making measurements on the internal electronic circuitry of any equipment in
service, it is preferable that you are earthen to the case with a conductive wrist strap.
Wrist straps should have a resistance to ground between 500k – 10M Ohms. If a wrist strap
is not available you should maintain regular contact with the case to prevent the build up of
static. Instrumentation which may be used for making measurements should be earthen to
the case whenever possible.
Schneider Electric strongly recommends that detailed investigations on the electronic
circuitry, or modification work, should be carried out in a Special Handling Area such as
described in IEC 60147-0F or BS5783.
6. PACKING AND UNPACKING

All MiCOM C264/C264C computers are packaged separately in their own cartons and
shipped inside outer packaging. Use special care when opening the cartons and unpacking
the device, and do not use force. In addition, make sure to remove from the inside carton the
supporting documents supplied with each individual device and the type identification label.
The design revision level of each module included with the device in its as-delivered
condition can be determined from the list of components. This list should be carefully saved.
After unpacking the device, inspect it visually to make sure it is in proper mechanical
condition.
If the MiCOM C264/C264C computer needs to be shipped, both inner and outer packaging
must be used. If the original packaging is no longer available, make sure that packaging
conforms to ISO 2248 specifications for a drop height ≤0.8m.
7. GUARANTEES
The media on which you received Schneider Electric software are guaranteed not to fail
executing programming instructions, due to defects in materials and workmanship, for a
period of 90 days from date of shipment, as evidenced by receipts or other documentation.
Schneider Electric will, at its option, repair or replace software media that do not execute
programming instructions if Schneider Electric receive notice of such defects during the
guaranty period. Schneider Electric does not guaranty that the operation of the software shall
be uninterrupted or error free.
A Return Material Authorisation (RMA) number must be obtained from the factory and clearly
marked on the package before any equipment acceptance for guaranty work.
Schneider Electric will pay the shipping costs of returning to the owner parts, which are
covered by warranty.
Schneider Electric believe that the information in this document is accurate. The document
has been carefully reviewed for technical accuracy. In the event that technical or
typographical errors exist, Schneider Electric reserves the right to make changes to
subsequent editions of this document without prior notice to holders of this edition. The
reader should consult Schneider Electric if errors are suspected. In no event shall
Schneider Electric be liable for any damages arising out of or related to this document or the
information contained in it.
Expect as specified herein, Schneider Electric makes no guaranties, express or implied and
specifically disclaims and guaranties of merchantability or fitness for a particular purpose.
Customer's rights to recover damages caused by fault or negligence on the part
Schneider Electric shall be limited to the amount therefore paid by the customer.
Schneider Electric will not be liable for damages resulting from loss of data, profits, use of
products or incidental or consequential damages even if advised of the possibility thereof.
This limitation of the liability of Schneider Electric will apply regardless of the form of action,
whether in contract or tort, including negligence. Any action against Schneider Electric must
be brought within one year after the cause of action accrues. Schneider Electric shall not be
liable for any delay in performance due to causes beyond its reasonable control. The
warranty provided herein does not cover damages, defects, malfunctions, or service failures
caused by owner's failure to follow the Schneider Electric installation, operation, or
maintenance instructions. Owner's modification of the product; owner's abuse, misuse, or
negligent acts; and power failure or surges, fire, flood, accident, actions of third parties, or
other events outside reasonable control.
8. COPYRIGHTS & TRADEMARKS

8.1 Copyrights
Under the copyright laws, this publication may not be reproduced or transmitted in any form,
electronic or mechanical, including photocopying, recording, storing in an information
retrieval system, or translating, in whole or in part, without the prior written consent of
Schneider Electric.
8.2 Trademarks
PACiS, PACiS SCE, PACiS ES, PACiS CMT, PACiS SMT, PACiS PS and PACiS SCE are
trademarks of Schneider Electric. Product and company names mentioned herein are
trademarks or trade names of their respective companies.
9. WARNINGS REGARDING USE OF SCHNEIDER ELECTRIC PRODUCTS

Schneider Electric products are not designed with components and testing for a level of
reliability suitable for use in connection with surgical implants or as critical components in
any life support systems whose failure to perform can reasonably be expected to cause
significant injuries to a human.
In any application, including the above reliability of operation of the software products can be
impaired by adverse factors, including - but not limited - to fluctuations in electrical power
supply, computer hardware malfunctions, computer operating system, software fitness,
fitness of compilers and development software used to develop an application, installation
errors, software and hardware compatibility problems, malfunctions or failures of electronic
monitoring or control devices, transient failures of electronic systems (hardware and/or
software), unanticipated uses or misuses, or errors from the user or applications designer
(adverse factors such as these are collectively termed "System failures").
Any application where a system failure would create a risk of harm to property or persons
(including the risk of bodily injuries and death) should not be reliant solely upon one form of
electronic system due to the risk of system failure to avoid damage, injury or death, the user
or application designer must take reasonably steps to protect against system failure,
including - but not limited - to back-up or shut-down mechanisms, not because end-user
system is customised and differs from Schneider Electric testing platforms but also a user or
application designer may use Schneider Electric products in combination with other
products. These actions cannot be evaluated or contemplated by Schneider Electric ; Thus,
the user or application designer is ultimately responsible for verifying and validating the
suitability of Schneider Electric products whenever they are incorporated in a system or
application, even without limitation of the appropriate design, process and safety levels of
such system or application.
MiCOM 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/C80 Introduction
BLANK PAGE
1. INTRODUCTION TO MiCOM
MiCOM is a comprehensive solution capable of meeting all electricity supply requirements. It
comprises a range of components, systems and services from Schneider Electric.
Central to the MiCOM concept is flexibility.
MiCOM provides the ability to define an application solution and, through extensive
communication capabilities, to integrate it with your power supply control system.
The components within MiCOM are:
• P range protection relays;
• C range control products;
• M range measurement products for accurate metering and monitoring;
• S range versatile PC support and substation control packages.
• A range industrial PC
MiCOM products include extensive facilities for recording information on the state and
behaviour of the power system using disturbance and fault records. They can also provide
measurements of the system at regular intervals to a control centre enabling remote
monitoring and control to take place.
The MiCOM range will continue to be expanded. The general features of MiCOM will also be
enhanced, as we are able to adopt new technology solutions.
For up-to-date information on any MiCOM product, visit our website:
www. schneider-electric.com
2. INTRODUCTION TO MiCOM GUIDES

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

This chapter provides the companion standard of all supported protocols toward SCADA
(Telecontrol BUS) and IED on LBUS. This is the list of protocol function that computer use in
this communication.
User minimal actions
2.1.11 Chapter Commissioning (CM)
This chapter contains instructions on how to commission the computer, comprising checks
on the settings and functionality of the computer.
2.1.12 Chapter Record Sheet (RS)
This chapter contains record sheet to follow the maintenance of the computer.
2.1.13 Chapter Maintenance, Fault finding, Repairs (MF)
This chapter advises on how to recognise failure modes, fault codes and describes the
recommended actions to repair.
2.1.14 Chapter Lexicon (LX)
This chapter contains lexical description of acronyms and definitions.
2.1.15 Chapter Applications (AP)
Comprehensive and detailed description of the features of the MiCOM C264/264C including
both the computer elements and the other functions such as transducerless (CT/VT)
measurements, events and disturbance recording, interlocking and programmable scheme
logic. This chapter includes a description of common power system applications of the
MiCOM C264/C264C computer, practical examples of how to do some basic functions,
suitable settings, some typical worked examples and how to apply the settings to the
computer.
2.1.16 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
CONTENT
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.3 C264-40TE Computer – Board Installation 11
3.6.4 C264-80TE Computer – Signals 12
3.6.5 C264C-40TE Computer – Signals 13
3.7 C264 Technical Data 14
3.7.1 C264: Element limits 14
3.7.2 C264: C264 with two extension racks with IEDs 16
3.8 Terminals 19
3.9 Creepage Distances and Clearances 20
4. RATINGS 21
4.1 Auxiliary Voltage 21
4.2 Power Supply 21
4.2.1 BIU241 Digital Outputs 21
4.2.2 BIU261 Dual Sources power supply board 21
4.3 Circuit breaker Control Unit (CCU) Digital Inputs 23
4.3.1 CCU200 Digital Inputs 23
4.3.2 CCU211 Digital Inputs 23
4.4 Circuit breaker Control Unit (CCU) Digital Outputs 24
4.4.1 CCU200 Digital Outputs 24
4.4.2 CCU211 Digital Output 25
4.5 Digital Input Unit (DIU) Digital Inputs 26
4.5.1 DIU200 Digital Inputs 26
4.5.2 DIU211 Digital Inputs 26
4.6 Digital Output Unit (DOU) Digital Outputs 27
4.6.1 DOU201 Digital Output 27
C264/EN TD/C80 Technical Data
4.7 Analogue Input Unit (AIU) Analogue Inputs 28

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

80TE 40TE Multirack Multirack
MAIN Rack Extension
Rack
BIU24x Power supply board X X X X
CPU 270 (CPU 3) 2 Ethernet communication channels X X X X
CCU200 Circuit breaker control unit X X X X
CCU211 Circuit breaker control unit X X X X
DIU200 Digital and counter acquisition X X X X
Digital measurement acquisition
Datapoints: SPS DPS SCT DCT DM
DIU211 Digital and counter acquisition 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
conditions
Set datapoints
AIU201 Analogue measurement acquisition X X X X
AIU211 Analogue measurement acquisition X X X X
TMU210 CT and VT sampling acquisition X X X
MV calculations with acquired samples
DSPIO for TMU 210 X X X
AOU200 Analogue output board X X X X
SWU20x X X X X
SWR2xx X X X X
SWD2xx X X X X
GHU2AB: NOTE 1 Graphic panel board with LED channels GHU GHU GHU GHU
2A1 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
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
3.6.3 C264-40TE Computer – Board Installation

Board Slots Maximum Number of Boards
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
SWU20x X X NOTE 2 NOTE 2
SWR2xx X X NOTE 2 NOTE 2
SWD2xx X X NOTE 2 NOTE 2
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.4 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.5 C264C-40TE 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)
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
NOTE 1: Do not install the CCU in the slot adjacent to the TMU.
.
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
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
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
FUNCTIONAL DESCRIPTION
MiCOM C264 Page 1/240
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
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
C264/EN FT/C80 Functional Description
Page 2/238 MiCOM C264
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 46
3.3.3 Controls 46
3.4 Inter-rack Ethernet communication 47
3.4.1 Internal Ethernet architecture 47
3.4.2 External network behaviour 47
3.4.3 Ethernet failure 48
3.4.4 Other Ethernet rupture 49
3.4.5 Ethernet Routing table 49
3.5 Ethernet port management on CPU Type 3, CPU 270 50
4. DIRECT PROCESS ACCESS 51

4.1 Input Check 51
4.2 Output check 51
4.3 Time tagging 51
4.4 Digital input acquisition (DI) 51
4.4.1 Acquisition 51
4.4.2 Debouncing and filtering 52
4.4.3 Toggling 52
4.5 Counters acquisition (CT) 53
4.5.1 Single counter (SCT) 53
4.5.2 Double counter (DCT) 54
4.6 Digital measurement (DM) 55
4.6.1 Acquisition without Read Inhibit signal 55
4.6.2 Acquisition with Read Inhibit signal 56
4.6.3 Encoding 57
4.7 Analogue input acquisition (AI) 58
4.7.1 Input ranges 58
4.7.2 Acquisition cycle 58
4.8 Digital outputs (DO) 58
4.9 Digital Setpoints: SPS, DPS, MPS 59
4.9.1 Encoding 59
4.9.2 Read Inhibit 59
4.9.3 Open / Close Select Order 60

4.10 Analog Setpoints 61
4.10.1 Output range 61
4.10.2 Output management 61
4.10.3 AOU Watchdog management 62
5. DATA PROCESSING 63
5.1 Binary Input Processing 63
5.1.1 Binary Input Definition 63
5.1.2 Processing of Single Point Status 64
5.1.3 Processing of Double Point Status 66
5.1.4 Processing of Multiple Point Status 71
5.1.5 System Inputs (SI) 72
5.1.6 IED inputs 73
5.1.7 Group processing 73
5.1.8 SBMC Mode Processing 74
5.1.9 BI sent to automatism features 74
5.2 Measurement Input Processing 75
5.2.1 Measurement Input Processing - Focus 75
5.2.2 Focus 1: Analogue Measurement Processing as far as Threshold Detection 76
5.2.3 Open circuit management 76
5.2.4 Scaling 76
5.2.5 Zero value suppression 77
5.2.6 Focus 2: Digital Measurement Processing as far as Threshold Detection 77
5.2.7 Focus 3: TMU2XX: CT/VT measurement processing as far as Threshold Detection 78
5.2.8 TMU2XX: CT / VT Calculations - General 79
5.2.9 TMU200 and TMU220: CT / VT Calculations – Inputs: Configuration 82
5.2.10 TMU200 and TMU220: CT / VT Calculations - Inputs: Samples 82
5.2.11 TMU200 and TMU220: CT / VT Calculations – Outputs: Set of measurements 83
5.2.12 TMU200 and TMU220: Measurements - General 84
5.2.13 TMU200 and TMU220: List of Measurements 85
5.2.14 TMU200 and TMU220: Algorithms 88
5.2.15 TMU210: CT / VT Calculations - Inputs: Configuration 90
5.2.16 TMU210: CT / VT Calculations - Inputs: Samples 90
5.2.17 TMU210: CT / VT Calculations – Outputs: Set of measurements 91
5.2.18 TMU210: Measurements - General 91
5.2.19 TMU210: List of Measurements 93
5.2.20 TMU210: Algorithms 95
5.2.21 Focus 4: All Measurement Values: Threshold Detection thru Transmission 103
5.2.22 Manual suppression 104
5.2.23 Substitution 104
5.2.24 Forcing an invalid measurement 104
5.2.25 Measurement resulting states 104
5.2.26 Transmission 105

5.3 Tap Position Indication (TPI) measurement processing 107
5.3.1 Acquisition from Digital Inputs 107
5.3.2 Acquisition from Analogue Inputs 107
5.3.3 Manual suppression 107
5.3.4 Substitution 107
5.3.5 Forcing an invalid TPI 107
5.3.6 TPI resulting states 108
5.4 Accumulator Input Processing 109
5.5 Energy counting 109
5.6 Basic Data Manipulation 110
5.6.1 Test Mode enhancements 110
5.6.2 Device order running 110
5.6.3 Controls management from PSL 111
5.6.4 PSL and Redundant Operation 112
6. CONTROL SEQUENCES 113

6.1 Description 113
6.1.1 General 113
6.1.2 Control sequence phase management 114
6.1.3 Direct Execute mode 117
6.1.4 SBO once mode 118
6.1.5 SBO many mode 121
6.1.6 Generic selection checks 123
6.1.7 Selection behaviour 127
6.1.8 Generic execution checks 128
6.1.9 Execution behaviour 128
6.1.10 Controls time sequencing 129
6.1.11 How an xPS starts a control sequence with following data 132
6.2 Control of non synchronised breakers 136
6.2.1 Non synchronised circuit breaker features 136
6.2.2 Control sequence of non-synchronised circuit breakers 136
6.3 Control of synchronised breakers 137
6.3.1 Synchronised circuit breaker features 137
6.3.2 Circuit breakers with external synchrocheck 138
6.3.3 Circuit breakers with internal synchrocheck 143
6.4 Control of disconnectors 147
6.4.1 Disconnectors features 147
6.4.2 Control sequence of disconnectors 147
6.5 Control of transformers 148
6.5.1 Transformer features 148
6.5.2 Control sequence of transformers 148
6.6 Control of ancillary devices 151

6.7 Control of Intelligent Electrical Devices (IED) 152
6.7.1 Control to IEDs 152
6.7.2 IED controls 152
6.7.3 Digital setting point (SP) 152
6.8 System controls 153
6.9 Kinds of control sequences 153
6.10 Control sequences checks 153
6.10.1 Mode Management 153
6.10.2 IED connected 153
6.10.3 Control mode 154
6.10.4 Uniqueness of control 154
6.10.5 Inter-control delay 154
6.10.6 Status of the device 154
6.10.7 Lock device 154
6.10.8 Running Automation 154
6.10.9 Interlocking 154
6.11 HV Control Sequences 155
6.11.1 Circuit breaker 155
6.11.2 Disconnector 155
6.11.3 Transformer 155
7. AUTOMATIONS 156
7.1 Built-in Automation functions 156
7.1.1 Auto-Recloser (AR) 156
7.1.2 Trip Circuit Supervision 162
7.1.3 Circuit breaker condition monitoring (I²t) 164
7.1.4 Automatic Voltage Regulation–AVR 166
7.1.5 Automatic voltage regulation–ATCC 181
7.2 Synchrocheck 194
7.2.1 Synchrocheck – General 194
7.2.2 Synchrocheck Schemes 195
7.2.3 Synchrocheck Algorithm 195
7.2.4 Synchrocheck Applications 196
7.2.5 Synchrocheck Circuit Breaker Closure types 196
7.2.6 Synchrocheck Type 1 and Type 2 196
7.2.7 Synchrocheck Hardware constraints and use 197
7.2.8 Synchrocheck Calculation 197
7.2.9 Synchrocheck Introduction to Harmonics 197
7.2.10 Synchrocheck – Check Synchronising – Locking Mode 197
7.2.11 Synchrocheck – System Synchronising – Coupling Mode 197
7.2.12 Synchrocheck: Scheme LL: Live Line, Live Bus: Real Time Sequences 198
7.2.13 Synchrocheck Schemes that use VLINE and not(VBUSBAR) or not(Vline) and
VBUSBAR voltage controls 200
7.2.14 Synchrocheck Schemes that use not(Vline) and not(VBUSBAR) voltage control 201
7.2.15 Synchrocheck Schemes that use Vline and Vbusbar voltage control 201
7.2.16 Synchrocheck Type 1 - Logic of Interlock Authorisation 203
7.2.17 Synchrocheck Type 2 - Logic of Interlock Authorisation 203
7.2.18 Synchrocheck Bypass 204
7.2.19 Phase-to-Phase Synchrocheck with the TMU210 206
7.2.20 Synchrocheck Close request 207
7.2.21 Synchrocheck General Configuration 208
7.2.22 Synchrocheck Voltage control 208
7.2.23 Synchrocheck Schemes control 209
7.2.24 Synchrocheck Parameters of the TMU2xx board 209
7.2.25 Synchrocheck Internal parameters 210
7.2.26 Synchrocheck Digital Output (DO) of the circuit breaker 211
7.3 Interlocking: logical equations 212
7.3.1 Interlocking: Inputs 212
7.3.2 Interlocking:Outputs 212
7.3.3 Interlocking: Control 212
7.3.4 Interlocking: Behaviour 212
7.4 Slow automation: Programmable Logic Control (PLC) 216
7.4.1 Inputs 217
7.4.2 Outputs 217
7.4.3 Control 217
7.4.4 Behaviour 218
7.4.5 Limits and specifications 218
7.5 Fast automation: Programmable Scheme Logic (PSL) 219
7.6 Fast Load Shedding ( FLS ) 220
7.6.1 C264M 220
7.6.2 C264Fi 220
7.7 Load Shedding – C264 Standalone 220
7.7.1 Inputs 220
7.7.2 Algorithm 221
7.7.3 Outputs 223
7.7.4 Hypothesis and Constraints 223
7.7.5 Configurable data 224
7.8 Load Curtailment – C264 Standalone 225
7.8.1 Inputs 225
7.8.2 Algorithm 225
7.8.3 Outputs 227
7.8.4 Hypothesis and Constraints 227
7.8.5 Configurable data 228
8. USER INTERFACE 229

9. RECORDS 230
9.1 Permanent records storage 230
9.1.1 Data storage 230
9.1.2 Waveform Recording: General 230
9.1.3 Events 230
9.1.4 Fast Waveform Recording 231
9.1.5 Slow Waveform Recording 231
9.1.6 Slow Waveform Recording – Hypothesis 233
9.1.7 Disturbance Recorder 233
9.2 Non-permanent data storage 235
9.2.1 Alarms 235
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.
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.
Computer CPU Operating Mode versus Commands Received by the CPU

2.1.6 Faulty mode

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

If the value of the internal counter remains lower than the Max_Fault parameter defined
during the configuration step, the computer goes into the Initialisation mode. When the
elapsed time since the last increment of the internal counter equals the value
Fault_Detection_Lasting parameter defined during the configuration step, the value of the
counter automatically resets
When the value of the internal counter reaches Max_Fault, the computer goes into the Halt
mode.
2.1.7 Halt mode
In this mode, the computer deactivates the watchdog relay and all the output relays. The
computer does not operate anymore. The only way to go out of this mode is to perform a
manual reset.
2.1.8 Summary of modes, tests, transitions, and faults
The different modes, tests, transitions, and faults of the computer show in the figure that
follows:
DB/software compatibility not OK

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

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

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

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/DIU210/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 9: 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 10: 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 11: 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 12: 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 13: 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 14: 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 15: 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.
• DOU200 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 16: 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 17: 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 18: 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 19: 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 20: 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 21: 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 22: 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 23: 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 24: 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 26: 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: TMU200 or TMU220 Board – CT / VT Calculations
Figure 28: Overview: TMU210 Board – CT / VT Calculations
OUTPUT
OUTPUT
INPUT
INPUT
FIGURE 29: OVERVIEW: TMU200 OR TMU220 BOARD – CT / VT CALCULATIONS
TMU210 Board Digital

Input / Output
CT / VT
Inputs
Acquisition
Function
Conventional CT / VT
TMU210 Calculation
inputs: 4 CT / 4 VT Function PPC
voltage (V) and
current (I) data DSPIO
Daughter
Board
4 CT / 5
20100706-01-RN
Set of computed
Voltage (V) and measurements
Current (I) data Samples
C0458ENa
FIGURE 30: 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 3
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)
TMU200 1 No External Type 1
TMU210 1 Yes External Type 2
TMU220 2 No Internal Type 1
CT / VT measurements are provided by 3 couples, or combinations, of boards:
• DSP + TMU200 ( 4 CT and 4 VT ), referred to as the DSP200 board installed on

TMU200
• 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 TMU200 and TMU220:
The TMU200 and the TMU220 boards have the same hardware attributes, except that
TMU220 has one more VT.
The DSP board computes the samples from the TMU200 and TMU220 and sends the set of
computed measurements to the PPC.
Please refer to Figure 29: Detail: TMU200 and TMU220 Boards – CT / VT Calculations
FIGURE 31: DETAIL: TMU200 AND TMU 220 BOARDS - CT / VT CALCULATIONS
TMU200 BOARDS – Signals, Ratings, and Range:
TMU 200 BOARDS

Signals Rating Range
Va, Vb, Vc, Vbusbar1 57V thru130V
Ia, Ib, Ic, Ir 1A or 5A
TMU220 BOARDS – Signals, Ratings, and Range:
TMU 220 BOARDS

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 32: DETAIL: TMU210 BOARD - CT / VT CALCULATIONS
TMU 210 BOARDS

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)
DSP+TMU200 X X X
or DSP200
DSPIO+TMU210 X X X X
or DSP210
DSP+TMU220 X X X
or DSP220
5.2.9 TMU200 and 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 TMU200 and 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 TMU200 and 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 TMU200 and 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 TMU200 and 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 TMU200 and 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)
Ubusbar k-1 (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 ) ⎞
⎜
= arctg⎜ ⎟ ⎜ ⎟
I A ^ U BC r ⎟ − arctg⎜ Im(U ) ⎟
r
⎝ Im( I A ) ⎠ ⎝ BC ⎠
r r
⎛ Re( I B ) ⎞ ⎛ Re(U CA ) ⎞
⎜
= arctg⎜ ⎟ ⎜ ⎟
I B ^ U CA r ⎟ − arctg⎜ Im(U ) ⎟
r
⎝ Im( I B ) ⎠ ⎝ CA ⎠
r r
⎛ Re( I C ) ⎞ ⎛ Re(U AB ) ⎞
⎜
= arctg⎜ ⎟ ⎜ ⎟
I C ^ U AB r ⎟ − arctg⎜ Im(U ) ⎟
r
⎝ Im( I C ) ⎠ ⎝ 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 φ =
P + Q2
2
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 34: 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 TMU200 TMU210 TMU220

Current (with measurement CT) 0.2% In 0.5% In 0.2% In
Voltage (with voltage droppers) 0.2% Vn 0.5% Vn 0.2% Vn
Frequency 0.01Hz 0.01Hz 0.01Hz
Angle 1° 1° 1°
Time 1 ms 1 ms 1 ms
Up to x harmonic 15th 15th 15th
Power (with measurement CT) 0.5% 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
MiCOM C264
Execution Execution via

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

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

with device selection
The following figures show the three control modes of the computer:
Execution via
FIGURE 35: 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
C264/EN FT/C80
Page 115/240
Execution via
Select Before Operate mode many
I/O boards
Execution or
checks
Execution via
Page 116/240
IED
Device
Device
C264/EN FT/C80
Selection
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 36: CONTROL MODES OF THE COMPUTER (2)

I/O boards
Execution
or
checks
Execution via
IED
selection phase execution phase (1) unselection phase
(1) An execution phase with two execution requests is given as an example, it may have more or less
C0315ENa
MiCOM C264
Functional Description
6.1.3 Direct Execute mode

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

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

acknowledge acknowledge
End of
sequence
C0316ENa
FIGURE 37: 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 38: 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 39: 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 40: 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 41: 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 42: 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 43: 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 44: 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 45: 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 46: 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 47: 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 48: 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 49: 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 50: 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 51: CONFIGURATION OF SYNOPTIC L/R PRIORITY IN CONTROL SEQUENCE

If the “synoptic L/R” is not configured, the control issued from an xPS is accepted whatever
is the Bay L/R mode.
SPS, DPS and MPS
SCE ISaGRAF
Status Status DINT
Quality Quality DINT
GlobalAlarmStatus Alarm SINT
Status attribute for SPS
• RESET / FORCED RESET / SUBSTITUTED RESET = 1
• SET / FORCED SET / SUBSTITUTED SET = 2

Status attribute for DPS
• MOTION 00 = 3
• OPEN / FORCED OPEN / SUBSTITUTED OPEN = 4
• CLOSED / FORCED CLOSED / SUBSTITUTED CLOSED = 5

NOTE: UNDEFINED state is seen as INVALID (see Quality attribute)
Status attribute for MPS
• State1 / FORCED state1 / SUBSTITUTED state1 = 7
• State6 / FORCED state6 / SUBSTITUTED state6 =12
• State7 / FORCED state7 / SUBSTITUTED state7 =13


Quality attribute
• VALID = 0
• SELFCHECK FAULTY = 1
• UNKNOWN = 2
• FORCED = 4
• SUPPRESSED = 8
• SUBSTITUTED = 16
• TOGGLING = 32
If Quality attribute is INVALID, Status attribute is non-significant.
Alarm attribute
Unusable
6.2 Control of non synchronised breakers

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

OUTPUTS OUTPUTS CB INPUTS CB OUTPUTS CB OUTPUTS INPUTS
CB TYPE A TYPE B (4) ALL TYPES TYPE A TYPE B (4) ALL TYPES
DEVICE DPC SPC control DPS physical DPC control DPC control for SPS/ DPS
CONTROL control for for open of position of the for open/close open phase A physical position
open/close device device(1 phase) of device of phase A
DPC control for
of device
SPC control SPS (optional) open phase B SPS/ DPS
for close of phase not (pulse) physical position
device together of phase B
DPC control for
information
open phase C SPS/ DPS
system DPS the physical position
DPC control for
feedback of the of phase C
close of device
control (1)
system SPS
phase not
together
information (2)
system DPS:
the feedback of
the control (3)
DEVICE SPC /DPC SPC /DPC SPS /DPS SPC /DPC SPC /DPC SPS /DPS
SELECTION (optional) (optional) (optional) device (optional) (optional) control (optional) device
control of control of selection control of of device selection
device device position device selection position
selection selection information selection information
1. The computed double signal is equal to the physical status if the phase not together
status is equal to “false” else the computed signal is equal to “jammed”.
2. The computed “phases not together” is equal to “false” if all phases are in the same
position else it is equal to “true”.
3. The computed signal is equal to the phase A status if the phase not together status is
equal to “false” else the computed signal is equal to “jammed”.
4. Only the “DPC close “ is known by the other IEC-61850 equipment:
• For open the device they send the “DPC close” with “open” request
• For close the device they send the “DPC close” with “close” request
6.2.2 Control sequence of non-synchronised circuit breakers
Circuit breakers devices are managed in ”Direct Execute” mode and in “SBO once” mode.
Refer to the generic description above.
6.3 Control of synchronised breakers

Circuit breakers devices are managed in “SBO once” mode only. The following paragraph
describes the specific features of synchronised circuit breakers whether are synchronised by
an external or internal synchrocheck module.
6.3.1 Synchronised circuit breaker features
For the circuit breakers, the table that follows gives the inputs and outputs that are controlled
by the computer:
THREE PHASED CIRCUIT BREAKERS ONE PHASED CB

OUTPUTS OUTPUTS CB INPUTS CB OUTPUTS OUTPUTS INPUTS ALL
CB TYPE A TYPE B (6) ALL TYPES (6) TYPE A TYPE B TYPES
DEVICE DPC control SPC control SPS/DPS DPC control SPC/DPC SPS/DPS
CONTROL for for open of physical for control for physical
open/close device position of the open/close open phase position of
of device device (1 of device A phase A
SPC control
phase)
SPC/DPC for close of SPC/DPC SPC/DPC SPS/DPS
control for device SPS (optional) control for control for physical
close with phase not close with open phase position of
SPC/DPC
synchrocheck together synchrocheck B phase B
control for
(5) information (5)
close with SPC/DPC SPS/DPS
synchrocheck system DPS control for physical
(5) optional): the open phase position of
feedback of C phase C
the control (1)
SPC/DPC system
control for SPS/DPS
close of phase not
device together
information (2)
SPC control
for close with system DPS:
synchrocheck the feedback
of the control
(3)
DEVICE SPC SPC (optional) SPS (optional) SPC SPC SPS (optional)
SELECTION (optional) control of device (optional) (optional) device
control of device selection control of control of selection
device selection position device device position
selection information selection selection information
SYNCHROCHEC SPC/DPC SPC/DPC SPS/DPS SPC/DPC SPC/DPC SPS/DPS
K SET ON/SET (optional) (optional) (optional) (optional) (optional) /DPS(optional)
OFF (4) control of control of ON/OFF control of control of ON/OFF
ON/OFF ON/OFF synchrocheck ON/OFF ON/OFF synchrocheck
synchrocheck synchrocheck information synchrocheck synchrocheck information
1. The computed double signal is equal to the physical status if the phase not together
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. 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 52: 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 53: 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 54: 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 55: 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 56: 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 57: ”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 58: 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 59: 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 60: 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 61: TRIP CIRCUIT SUPERVISION WITH TWO DI

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

The C264 makes records of various statistics related to each circuit breaker trip operation.
This allows you to make a more accurate assessment of the condition of the circuit breaker.
The C264 mainly calculates the sum of the switched current over a period.
The C264 can separately evaluate each phase current and estimate each CB pole wear.
The CB manufacturers usually provide the maximum number of permissible CB operations in
relation to the disconnection current characteristics.
When an overcurrent event causes a circuit breaker to trip, then the C264 performs the I²t
function.
7.1.3.1 Acquisition and computation
The C264 counts without consideration of disconnection currents:
• The number of CB operations per pole
• The number of CB operations for the 3 poles (i.e. the highest of the pole values)
The C264 cumulates from the latest reset:
• The current - time integrals per pole
• The square current - time integrals per pole
• The current - time integrals of all the poles
• The square current - time integrals of all the poles

Each integral is calculated between the trip command time and the time when the RMS
value is less than 0.1A.
Example:
FIGURE 62: 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
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 63: 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 64: 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 65: 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
TMU200+DSP YES NO NO DOU
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
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 66: VLINE AND NOT(VBUSBAR) VOLTAGE CONTROL
Vbusbar
Τ2 0
and Closing authorization
Not(Vline)
FIGURE 67: 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)
FIGURE 68: NOT(VLINE) AND NOT(VBUSBAR) VOLTAGE CONTROL

If, during the T3 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.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 69: LOCKING SCHEME FOR TYPE 1

Vline
Vbusbar
and T1 0 Reclosing authorization
ΔS <Sfreq
Δϕ < Ephase
ΔV < Evec t
FIGURE 70: 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:
• Presence of both voltages AND
• The difference in amplitude (algebraic) between the two voltages (ΔV) is lower than
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

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

Vline
Vbusbar
and T4 0 Authorisation to check Δϕ
ΔS <Sfreq
accShift< assSfreq
ΔV < Evec t
FIGURE 72: 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).
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.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
TMU200 / TMU220 electrical-network-topology parameters. To be compatible, it is helpful to
map the TMU210 type-of-connection parameters into the TMU200 / TMU220 electrical-
network topology parameters:
TMU210 TMU200 / 220

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 TMU200 / 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 73: 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 74: 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
TMU200 4 4 DSP NO NO YES
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
• Operator request
• Periodically: that is, every day at 00h00

NOTE: The triggering is available only from a state/value with VALID quality
(ex: SET/REST; OPEN/CLOSE) to a state/value with VALID quality.
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 75: 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 76: 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.
MiCOM C264/C264C
HARDWARE
CONTENT
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 10
2.3 Coding of board address 13
2.4 Modules description 14
2.4.1 Power auxiliary supply and legacy ports board – BIU241 14
2.4.2 Dual source power supply board – BIU261 16
2.4.3 Central Processing Unit and base communications board – CPU260 19
2.4.4 Central Processing Unit and base communications board – CPU270 20
2.4.5 DSPIO board 21
2.4.6 Circuit breaker Control Unit - CCU200 22
2.4.7 Circuit breaker Control Unit - CCU211 23
2.4.8 Digital Inputs Unit – DIU200 25
2.4.11 Digital Outputs Unit – DOU200 29
2.4.12 Digital Outputs Unit – DOU201 30
2.4.13 Analogue Input Unit – AIU201 31
2.4.14 Analogue Input Unit – AIU211 32
2.4.15 Transducerless Measurements Unit – TMU200/220 33
2.4.16 Transducerless Measurements Unit – TMU210 34
2.4.17 Analogue Output Unit – AOU200 35
2.4.18 Ethernet Switch Unit – SWU200/SWU202 36
2.4.19 Ethernet Switch Unit – SWx202/SWx212, SWx204/SWx214
(x=R for dual Ring, x= D for Dual homing) 38
2.4.20 Extended communication Unit – ECU200 42
2.4.21 Extended communication Unit – ECU210 43
C264/EN HW/C80 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
• 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
• DIU210: Digital Inputs Unit each with 16 digital inputs for voltages from 24 to 220Vdc
• DIU211: Digital Inputs Unit each with 16 digital inputs for voltages from 24 to 220Vdc
(versions are jumper-selected)
• DOU200: Digital Outputs Unit each with 10 digital outputs
• 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)
DOU200/201
(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 C0117 ENh

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:
• 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 13: MiCOM C264 – GHU201 BOARD

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

2.2.2.2.3 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 FBP28X board is the front backplane of MiCOM C264C equipped with the CPU260.
FIGURE 16: MiCOM C264 80TE – FBP280 BOARD

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

Rear panel without CT/VT BOARD:
FIGURE 19: 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,
DOU200, 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 20: MiCOM C264 - BIU241 BOARD

The BIU241 board provides two isolated serial links.
This following figure locates the serial links configuration jumpers.
C0033ENa
FIGURE 21: 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: MiCOM C264 - BIU261 BOARD

FIGURE: BIU261 JUMPERS
S6
S7
S3 S8
S2 S9
S4
S5
FIGURE: 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 S2, 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 22: 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 23: 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 24: 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 25: 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 26: 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

monitoring).
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
FIGURE 27: MiCOM C264 - DIU200 BOARD


Depending on the applied voltage, 4 versions of the DIU210 are available.
• 1 negative or positive common contact for 2 inputs
• All voltages between 24V and 220V DC
• From 48V to 220VDC: High current circulation inside binary contacts inputs during a
short time (to clean external contacts): see the current peak response curve
• With 24Vdc voltage, the high current consumption (>25mA) is permanent


• 1 common contact for 2 inputs (positive or negative)
measurement input on the same unit.
• All voltages between 24V and 220V DC
• Pre-defined triggering thresholds selected using jumpers:

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.11 Digital Outputs Unit – DOU200

The Digital Outputs Unit (DOU200) board provides 10 outputs using integrated relays.
The DOU200 board capabilities are:
• 2 single pole relays with 1 common for 2 outputs (NO/NC)

monitoring)
The digital outputs can be configured in single or double remote control or set point outputs
on the same module.
FIGURE 30: MiCOM C264 - DOU200 BOARD

2.4.12 Digital Outputs Unit – DOU201

The Digital Outputs Unit (DOU201) board provides 10 isolated digital outputs using
integrated relays.
The DOU201 board capabilities are:
• 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 31: MiCOM C264 - DOU201 BOARD

2.4.13 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 32: MiCOM C264 - AIU201 BOARD

2.4.14 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 33: MiCOM C264 - AIU211 BOARD

2.4.15 Transducerless Measurements Unit – TMU200/220

The transducerless measurement capabilities are the following:
• 4 measurement Current Transformers (4 CT) inputs
− Transformers have two ranges 1 and 5 amperes
• for the TMU200 4 measurement Voltage Transformers (4 VT) inputs. 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%
FIGURE 34: MiCOM C264 – TMU200 BOARD
The measured values are processed by an associated board:
Measurement unit Processor Processor board

TMU200 TMS320C6711 DSP260
TMU220 TMS320C6713 DSP220
2.4.16 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 35: MiCOM C264 – TMU210 BOARD

2.4.17 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 36: MICOM C264 – AOU200 BOARD

2.4.18 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 37: 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.19 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 38: MiCOM C264 – SWX202 BOARD
FIGURE 39: MiCOM C264 – SWX204 BOARD – WITH SC CONNECTOR

FIGURE 40: 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 41: 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 42: 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.20 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 43: MiCOM C264 – ECU200 MODULE
Optical characteristics:
• Connector type: ST
• Wavelength: 820 nm
• Recommended Fibre cable: 62.5/125 μm

2.4.21 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/C80
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.8 Digital Outputs module – DOU200/201 27
4.9 Analogue Input module – AIU201 29
4.10 Analogue Input module – AIU211 31
4.11 Transducerless Measurements Unit module –TMU200 33
4.14 Analogue Output module – AOU200 39
4.15 Ethernet Switch Unit - SWU200/SWU202 41
4.16 Ethernet Redundant Switch Unit - SWR202/SWR212, SWR204/SWR214 42
4.17 Dual Homing Ethernet Switch Unit - SWD202/SWD212, SWD204/SWD214 43
4.18 Front panel 44
C264/EN CO/C80 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.
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
Power auxiliary supply BIU241/

BIU100 and legacy ports board
PIN
Output relays
1 O2
2
3 O1
4 Watchdog
5
6
7 V IN VIN
+ +
DI1 DI2
8
10
11 RS232/
12 RXD / TB RS485 Serial
link 1
13 SG (0 V)
14 TXD / TA
#
15
SG (0 V)
16 RS232/
CTS RS422
17
RXD / TB RS485 Serial
18 TXD / TA
RTS / RB
link 2
19
RA #
20
DCD
21
22
V aux
23 + Power
supply
24
C0050ENf
FIGURE 10: BIU241 AND BIU100 BOARD – BLOCK DIAGRAM

WARNING: FOR SAFETY REASONS, WHEN THE COMMUNICATION PORT OF
BOARDS BIU241 REFERENCED 2070879 A03-Z AND 2070879 A04-Z IS
CONNECTED TO DEVICES, IT IS MANDATORY TO EARTH SOME OF
THE "SG PIN" OF THE COMMUNICATION PORT, ACCORDING TO THE
FOLLOWING APPLICATIONS.
RS232:
− If the C264/BIU241/Port 1 is used -> Pin No 13 (SG) is to be earthed
− If the C264/BIU241/Port 2 is used - > Pin No 15 (SG) is to be earthed

RS485 / RS422: daisy chain and equipements in the same cubicle:
− The GND signal of the daisy chain extremity is to be earthed.

RS485 / RS422: daisy chain and equipements in various cubicles:

NOTE: In this case, the GND signal of the daisy chain extremity is not to be
earthed.
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

For safety reasons, with the communication port of board BIU261 connected to devices, it is
mandatory to earth some of the "Signal Ground pin" of the communication port, according
to the following applications.
Interface Note Recommandation wiring

RS232 Pin n° 15 (SG) have to be earthed
RS485 / RS422 Case for Daisy chain and Pin n° 15 (SG) have to be earthed
equipements in the same The GND signal of the daisy chain
cubicle extremity have to be earthed.
RS485 / RS422 Case for daisy chain and The GND signal of the daisy chain
equipements in various extremity have not to be earthed.
cubicles
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”,
relay 1
(Closed when “Active”
Redundancy input - 8 (-) 8 Redundancy input - common
common 1 & 2 (-) 1 & 2 (-)
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.
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

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 - -
3
4 VIN VIN
+ DI3 + DI4
- -
5 - -
6
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

The Digital Input module (DIU210) provides 16 optically isolated digital inputs split in eight
groups of two inputs. Both inputs of a group have a common pin which can be used either as
a negative common pin or a positive common pin.
4.6.1 Block diagram

NOTE: There is only one type of DIU210 board, including all wetting voltages
between 24 and 220V AC/DC.

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

1 Digital Input 1
2 Digital Input 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
16 Digital Input 11
17 Digital Input 12
19 Digital Input 13
20 Digital Input 14
22 Digital Input 15
23 Digital Input 16
TABLE 9: DIU210 BOARD - CONNECTOR DESCRIPTION

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.7.1 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.8 Digital Outputs module – DOU200/201

The Digital Outputs Unit board (DOU200 or DOU201) provides 10 isolated outputs using
relays.
4.8.1 Block diagram
D igital Output U nit DOU200

board
PIN Signal outputs
1
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
C0057ENb
FIGURE 18: DOU200 BOARD – BLOCK DIAGRAM


The DOU200/201 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 10: DOU200/201 BOARD - CONNECTOR DESCRIPTION

4.9 Analogue Input module – AIU201

The Analogue input module (AIU201) provides 4 independent analogue inputs.
4.9.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 19: 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 11: AIU201 BOARD - CONNECTOR DESCRIPTION

4.10 Analogue Input module – AIU211

The Analogue input board AIU211 provides 8 isolated Analogue inputs.
4.10.1 Block diagram
FIGURE 20: 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 12: AIU211 BOARD - CONNECTOR DESCRIPTION

4.11 Transducerless Measurements Unit module –TMU200

The Transducerless Measurements Unit module TMU200 provides 4 transducerless voltage
inputs (VT) and 4 transducerless current inputs (CT).
Transducerless 1A Transducerless 5A
Current and Voltage TMU 200 Current and Voltage TMU 200
U nit board U nit board
Transducerless Transducerless
current inputs current inputs
PIN PIN
N1
1 2 1 2 N2
N1
3 4 N2 3 4
C1
5 6 5 6 C2
C1
7 8 C2 7 8
B1
9 10 9 10 B2
B1
11 12 B2 11 12
A1
13 14 13 14 A2
A1
15 16 A2 15 16
17 18 17 18
Transducerless Transducerless
voltage inputs voltage inputs
19 20 19 20
U1 U1
21 22 U2 21 22 U2
V1 V1
23 24 V2 23 24 V2
W1 W1
25 26 W2 25 26 W2
N1 N1
27 28 N2 27 28 N2
C0060ENb
FIGURE 21: TMU 200 BOARD – BLOCK DIAGRAM


The TMU200 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
5 Current Input 5A – C1
9 Current Input 5A – B1
13 Current Input 5A – A1
17 NC
18 NC
19 NC
20 NC
21 Voltage Input – U1
23 Voltage Input – V1
25 Voltage Input – W1
27 Voltage Input – N1
TABLE 13: TMU200 BOARD - CONNECTOR DESCRIPTION


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


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


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 23: TMU 210 BOARD – BLOCK DIAGRAM


Pin N°. Signal

1 Current Input 5A - N1
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

4.14 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.15 Ethernet Switch Unit - SWU200/SWU202

The SWU200 board provides four electrical links.
The SWU202 board provides four electrical links and two optical links.
4.15.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 16: SWU200/202 BOARD – RJ45 CONNECTOR DESCRIPTION

4.15.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 24: SWITCHES: PORT 4 ETHERNET AND FAULT SIGNAL CONNECTORS

4.16 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 17: 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.17 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 18: 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.18 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 25: 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 19: FRONT PANEL - CONNECTOR DESCRIPTION

MiCOM C264/C264C
INSTALLATION
CONTENT
2. REQUIREMENTS 4
2.1 MiCOM C264 4
2.2 Personal Computer 4
2.3 Communication wiring 4
3. DELIVERY RECEPTION 5
3.1 Packing inspection and opening 5
3.2 Delivery form checking 5
4. MECHANICAL MOUNTING 6
4.1 Rack mounting 6
4.2 Panel mounting 6
5. WIRING INSTALLATION 7
5.1 General wiring 7
5.2 Power supply wiring 7
5.3 I/O board wiring 7
5.4 Networks wiring 7
6. MiCOM C264 POWER UP 9
7. MiCOM C264 SOFTWARE INSTALLATION 10

7.1 Introduction 10
7.2 Prequisites 10
7.2.1 PC minimum configuration 10
7.2.2 Overview 10
7.2.3 Upgrading the C264 12
7.3 Computer_B7.21 installer 13
7.3.1 Before the installation 13
7.3.2 Computer Installation 13
7.4 Human Machine Interface 15
7.5 Operator's record folders 16
7.6 Settings 16
7.7 Scan 16
7.8 Connection to a computer 18
7.9 Work pane 19
7.10 Modes and permitted operations 21
C264/EN IN/C80 Installation
7.11 Routine operations 22

7.11.1 Display status and monitoring 22
7.11.2 Manage database (subject to privilege) 23
7.11.3 Edit settings (subject to privilege) 25
7.11.4 Manage events and states (subject to privilege) 26
7.11.5 Display errors and Agency logs 29
7.11.6 Display AVR data 29
7.11.7 Waveforms 30
7.12 Expert Functions 31
7.12.1 Manage date and time (read, and change depending on profile) 31
7.12.2 Manage boot and network parameters 32
7.12.3 Manage communication ports 33
7.12.4 Load application software 34
7.12.5 Load bootrom software 34
7.12.6 Browse computer files 35
7.12.7 Launch a telnet session 36
7.13 Security administrator functions 37
8. DOWNLOADING DATABASE 39
8.1 Database download with CAT 39
8.1.1 Loading DB under CAT 39
8.1.2 Download DB onto C264 39
8.2 Database download with SMT 40
8.2.1 Loading DB under SMT 40
8.2.2 Download DB onto C264 40
8.2.3 Switch to downloaded data base 40
9. AFTER COMPUTER INSTALLATION 41
10. OPTIONAL INSTALLATION 42

10.1 External master clock connection 42
10.2 Printer installation 42

This document is a chapter of the MiCOM C264 documentation. It describes the product
installation and start-up settings. Before any computer handling the chapter C264/EN SA
should be read carefully.
This document is split in the following parts:
• Delivery reception
• Mechanical fixation
• I/O board wiring
• Networks wiring
• Power supply wiring
• Power-up without I/O
• Network setting
• Data Base Download

This document should be used in conjunction with the C264/EN CM.
2. REQUIREMENTS
MiCOM C264 boot setting and software installation is carried out using a Windows PC with
common utilities and serial/Ethernet link to the computer.
The PACiS CD-ROM System installation is needed to run the C264’s install software on the
Host PC.
2.1 MiCOM C264
The MiCOM C264 needs at least
• CPU board CPU270
• Power board BIU241
• Backplane FBP242 (for MiCOM C264C) or FBP280 (for MiCOM C264)

The BIU241 needs to be correctly wired to its voltage level as described in chapter C264/EN
CO (Connections). Before any operational voltage is applied the shield wiring should be
checked following rules of the Safety Guide: SFTY/4L M/G11-S (or later issue) and rules
of chapter C264/EN SA (Safety & Handling).
The CPU270 basically integrates factory parameters.
NOTE: The computer needs to be installed with the software that allows
booting in flash. Installation or reinstallation of BOOTPROM software
in PROM is described in C264/EN MF Maintenance chapter, and out
of scope of this chapter.
Before starting installation the following information is required:
• Computer IP address
• Computer alias name

Both parameters are also defined in computer database. If parameters inside database differ
from the CPU settings, the IEC61850 communication with others PACiS equipment will not
be possible.
2.2 Personal Computer
A Personal Computer is used for setting and download. The required Windows operating
system is WinNT or Win2003 or Windows XP SP2.
The PC hardware requirement is:
• Ethernet port 10 Mb/s or 100 Mb/s
• 100 Mb of free space on hard disk

The PC software's needed is:
• Computer package named Computer_X.YZ.exe ( X.YZ is the computer version)

2.3 Communication wiring
The link between PC and MiCOM C264 is Ethernet.
For a direct connection (without Ethernet Switch) between the PC and the MiCOM C264, a
crossed wire is required.
3. DELIVERY RECEPTION
Delivery reception is composed of:
• Packing inspection and opening
• Delivery form checking
• Feeling up commissioning
3.1 Packing inspection and opening
On receipt of the unit, inform the delivery agent if there is any sign of damage.
Check the box for documentation, or computer hardware option added in the delivery form
like ribbon, screws, port extension etc.
3.2 Delivery form checking
The delivery form is based on the order form issued from CORTEC. It lists computer type,
boards (with supply, serial numbers and position in the rack) and options.
Verify that the composition of the device is as ordered.
Computer is delivered with the required connectors.
4. MECHANICAL MOUNTING
The chapter C264/EN HW gives the size of MiCOM C264 rack, the fixation diameters and
their position.
If electric screwdriver is used the torque limitation should be set to the small diameters of the
screws.
The MiCOM C264 can be mounted in racks or panel.
4.1 Rack mounting
MiCOM C264 may be rack mounted using single tier rack frames (our part number is
FX0021 001):
These frames have been designed to have dimensions in accordance with IEC60297 and
are supplied pre-assembled ready to use.
The two horizontal rails of the rack frame have holes drilled at approximately 26mm intervals
and C264 cases are attached via their mounting flanges using M4 Taptite self-tapping
screws with captive 3 mm thick washers to ensure a good earth contact (our part number is
ZB5865250).
It is possible to install two C264C side by side on the assembly panel or one C264.
Ensure that the computers are earthed, using the screw terminal on the rear of the unit.
4.2 Panel mounting
MiCOM C264 can be flush mounted into panels using M4 Taptite self-tapping screws with
captive 3 mm thick washers to ensure a good earth contact (our part number is ZB5865250).
Alternatively tapped holes can be used if the panel has a minimum thickness of 2.5 mm.
Where several MiCOM C264 are to be mounted in a single cut-out in the panel, it is advised
that they are mechanically grouped together horizontally and/or vertically to form rigid
assemblies prior to mounting in the panel.
NOTE: It is not advised that MiCOM C264 are fastened using pop rivets as
this will not allow the device to be easily removed from the panel in the
future if repair is necessary.
5. WIRING INSTALLATION
Wiring has to be prepared before installation. The MiCOM C264 is delivered with required
connectors for I/O boards and Ethernet switches. The wire diameters stated in chapter
C264/EN CO are mandatory. Tighten the screws in a cross pattern (e.g. top left, then bottom
right etc), take care not to over torque the screws.
5.1 General wiring
Only two wires can be screwed together on any one MiCOM connector. The AC and DC
analogues, digital signal, and communication wires should use separate shielded cable.
From a practical point of view the power supply of each computer should have a switch
(MCB, link, or fuse) to turn off the power during installation and commissioning tests.
The MiCOM C264 description sheet describes the type of board Installed on each slot (C, D
etc.) It is very important to use it to correctly plug the connectors.
Connection diagrams of the C264 are given in chapter C264/EN CO. Wires should be
connected with the connector unplugged. Each wired signal has to be tested before plugging
and fixing the connectors. The connectors have to be fixed on the C264 case with the
screws available at each extremity of the connector.
For connection of the protective (earth) conductor please refer to the section 3.1 of the
Connections chapter (C264/EN CO)
5.2 Power supply wiring
The BIU connector wiring is vital as it provides the power supply. Power voltage should be
tested and checked to BIU reference defined in chapter C264/EN HW to ensure that supply
is compliant to BIU voltage.
The power has to be switched off before plugging in the connector.
5.3 I/O board wiring
Several DIU, CCU, BIU board voltage are available for Digital Input. Check that the DIU
voltage as stated on the delivery form matches with the nominal signal input before plugging
connector to the computer.
DOU and CCU, the board generates Digital Output with a defined inductive characteristic.
On the other side of the wire the inductance should be compliant. To avoid damage to the
DO board connected to inductive circuits it may be necessary to connect an anti-surge
diode.
5.4 Networks wiring
Network wiring can be fibre optic or copper. Fibre optic communication is an option, and
should be ordered as such along with the required mechanical modules. There are specific
rules governing the installation of fibre optics (refer to the chapter C264/EN CO). Specific
care should be taken with the bend radius of the fibres, and the use of optical shunts is not
recommended as these can degrade the transmission path over time.
Never look into the end of a fibre optic due to the risk of causing serious damage to the eye.
Copper networks should follow class recommendation and shielding. When using a Legacy
bus (with IED mounted in daisy chain), the correct resistor, at both ends only, should be
fitted (120 ohms for RS422 and RS485).
Copper Ethernet network have to stay inside a cubicle. Fibre optic has to be used between
cubicles.
For the use of SWR20x or SWD20x, the optical ring has to be connected as follows:
Rp Rp Rp
Es Es Es
SWR20x SWR20x SWR20x
Rs or Rs or Rs or
SWD20x SWD20x SWD20x
Ep Ep Ep
C0295ENa
6. MiCOM C264 POWER UP

The MiCOM C264 as delivered has the following installed:
• Bootrom start-up software
• Factory Start-up Setting

Before powering up the computer all the DI/DO board connectors should be disconnected.
Tests are described in the C264/EN CM chapter to check that the computer with its factory
settings has not suffered damage during transport.
7. MiCOM C264 SOFTWARE INSTALLATION

7.1 Introduction
In this chapter, the word 'PC' refers to the PC where the CAT is installed, whereas the word
'computer' refers to the MiCOM C264. Generally, download is a transfer from the PC to the
computer, upload is the reverse transfer.
CAT simplifies and secures the basic maintenance interventions, CAT is a graphical tool.
CAT communicates with C264 by raw Ethernet packets in direct MAC addressing via
PERMA.
CAT manages only computers using CPU270 board. CAT uses PERMA instead of SBus
Agency.
Connect the MiCOM C264 and the PC on the same Ethernet switch or directly.
7.2 Prequisites
7.2.1 PC minimum configuration

• At least Pentium 3 or similar
• Processor frequency: At least 700MHz
• At least 100 Mb free space on hard disk
• A CD-ROM drive
• An Ethernet 10/100 Mb/s port (the board is referred to as Network Adapter)
• Operating System: Windows XP SP2 or SP3 32bits
• Windows installer 3.1
• Framework NET 3.5 SP1 to upload the disturbance files (installer: dotnetfx.exe)
• WinPcap 4
• Antivirus Avira Antivir Professional Version 9.0 or later (that is recommended for
PERMA A2.15 architecture).
7.2.2 Overview
Two CDROMs are required: B7.20 and B7.21. Each installer is located in:
\System\Delivery\PACiS Va.b.c\C264 VX.YZ (Va.b.c is the PACiS system version, X.YZ is
the computer version).
The installers include several components:
• C264 rev. Z, with a bootrom to partition the flash memory in a new way
• WFTP, ftp server used to download software to MiCOM C264 (expert use)
• Computer Maintenance Tool and /or Computer Administration Tool (CAT_A1)

In addition Computer_B7.20 creates the folder Program Files/WinPcap that includes the
installer Rpcapd.
Sequence of installation and components to be installed on the PC:
Initial state No CMT Release < B7.15 Release ≥ B7.15

Installer
Computer_B7.20.exe C264 rev Z C264 rev Z –
CMT CMT –
WFTP – –
Rpcapd (included in B7.20) WinPcap WinPcap WinPcap
Upgrade the C264
Uninstaller (Settings panel) CMT CMT CMT
Computer_B7.21.exe – – C264 rev Z
CAT CAT CAT
MiCOM S1 MiCOM S1 MiCOM S1
The steps include:

1. Upgrading CMT on the PC if the release was earlier than 7.15 (bootrom: BSP version
earlier than …/B1.xx)
2. Upgrading the C264 software to version Z
3. Uninstalling the CMT
4. Installing CAT
5. Putting in force the security policy (refer to section 1.13)
NOTE: Framework NET 3.5 SP1 must be previously installed.
7.2.3 Upgrading the C264

The flowchart that follows summarizes the procedure:
Start CAT from

Release 7.15 or later
DATA BASE
Clean all DB
PARAMETERS
Bootrom boot
Bootprom boot
forcing Set boot parameter
COMPUTER VERSION :
Computer mode : Boot
BOOTINSTALL
Select C:/Program Files/PACIS/Computer/C264_cpu3/bootrom.flh,
Update bootrom
COMPUTER VERSION :
Computer mode : Stopped
Bootrom Update
REBOOT COMPUTER
FILE EXPLORER
Flash format
Flash formatting
REBOOT COMPUTER
BOOTINSTALL
Select C:/Program Files/ PACIS/Computer/C264_cpu3/
Start bootinstall
Stop computer
Files transfer
PARAMETERS
Modifications Flashboot
application Set boot parameters
Flash partitioning REBOOT COMPUTER COMPUTER VERSION :

Computer mode :
Maintenance
C0509ENa
7.3 Computer_B7.21 installer

7.3.1 Before the installation
The CAT software needs the Framework NET 3.5 SP1. The Framework NET 3.5 SP1 has to
be installed manually.
The Framework NET 3.5 SP1 is located on the package in: \System\Delivery\PACiS
Va.b.c\TOOLS Framework .net 3.5 SP1\
Launch the setup from the dotnetfx35_standalone.exe and follow instructions.
FIGURE 1: EXTRACTING FILES FROM THE FRAMEWORK NET 3.5 SP1 INSTALLER
Choose the option I have read and ACCEPT the terms of the License Agreement, and Install
NOTE: The Framework 3.5 SP1 installation can take several minutes.
7.3.2 Computer Installation
Launch the setup from the B7.21 (or later) CDROM.
NOTE: If the dialog box below is displayed, cancel the computer Installation
and install the Framework NET 3.5 SP1 described on the previous
section §1.3.1.
Select the required components:
Continue till the Welcome screen shows.

NOTE: At the iend of nstallation, if the WinPcap is not installed, select the
option Install WinPcap 4.0 Driver and DLLs
7.4 Human Machine Interface

The accordion resizable window features a menu bar and three panes:
To enlarge the Scan pane, collapse the Filter pane using the horizontal Auto hide toggle
button.
To enlarge the Work pane, collapse the left panes using the vertical Auto hide toggle button.
Select the HMI language among French, English:
It can be changed on the spot; no need to restart the CAT.

To retain a shot of the whole window in png format, click the link Save As Snapshot.
7.5 Operator's record folders

<Installation folder>/CAT/Files is the default destination folder for snapshots, security logs,
directories export.
CAT Files: snapshots, security logs, directory exports (save)
Error_Reports: fault report (save)
Logs: technical traces
<Installation folder>/CAT/Error_Reports is the destination folder for fault report. A fault report
might result from a window popping up, for example:
7.6 Settings
In case the PC has several network cards, click Select Network adapter and select the
desired card. Some cards are not fit for the CAT (NdisWan Adapter, MS TCP Loop back
interface…).
The selection is saved in the Registry. All the settings are restored at CAT's next start.
7.7 Scan
To carry an inventory of the networked computers, click Refresh; this populates the
computers' directory:
• Computer network name as input in SCE
• Cpu3's serial number (# stands for 000)
• Computer's IP address
• Computer's mode: maintenance, active, stand-by (redundancy)
• Rack address: Main / Secondary (multi-rack architecture)

The text colour reflects the computer's mode:
• red: maintenance
• blue: stopped
• black: bootprom
• green: active
• grey: disconnected
To sort the items according to the values in a column, click the column header; this reveals a
clickable sorting sign or .
To deny access to computer's information, click the computer's eye icon, the icon looks
crossed off; select Hide selected computers option and the computer selected is off.
To restore access, exit CAT using the upper corner red cross and restart it.
When Computer in maintenance the status shown in the close up line-: MAINT DATA BASE.
However when Computer is in Active state Close up line shows the Banner text if configured
in SCE else the space is blank.
FIGURE 2: BANNER TEXT ON CAT FOR COMPUTER ON MAINTENANCE MODE
FIGURE 3: BANNER TEXT CONFIGURED ON SCE
FIGURE 4: BANNER TEXT ON CAT FOR COMPUTER ON ACTIVE MODE

To export the directory to the txt format, click on icon .
To print the directory, click on icon .

The Filter pane is used to narrow the list of displayed computers:
− one computer, by typing an IP address (the wildcard character * is allowed)
− all the computers being in a given mode (first drop-down list)
− all the extensions with a given number (second drop-down list: 0 for main
computer thru 16)
Any means that the criterion has no effect.
To dim a computer's line, click the eye icon and select the box Hide selected computers.
To take mute computers off the list, click the link Clear disconnected computers.
NOTE: If a distant computer is not detected, download cyberdb_orig.xml on
computer flash/maint directory, using the CMT file explorer.
7.8 Connection to a computer
To select a computer, click on it in the directory; this displays the latest computer's name and
data base number (if any) in the close-up line.
To establish a communication with the computer, click Connect to this computer (or click two
times). A login window shows:
Four profiles are defined. Select one as a username and enter the password.
Depending on the security policy, the account might be locked out due to several incorrect
password typed in; in this event, ask the Security administrator to unlock it.
Several sessions cannot be open simultaneously. To change profile, click again Connect to
this computer.
Note for Auto Log Off: when operator's does not place applicative requests for longer than a
timeout, any further action requires a reconnection. To set the time-out, ask the Security
administrator. Default value: 10min.
7.9 Work pane

The logon status is reminded in the upper right corner; the computer's information is
reminded in the Work pane upper left corner:
The Stop button is used to suspend all tasks except Synchro and Superv.
The Reboot button is used to reboot the computer.
Only the System administrator is entitled to access to the Boot and Stop buttons.
A vertical menu shows. The items give access to computer's updated information and allow
the databases managing. The list depends on the user's privileges and computer's mode.
The Log Off action is the reverse of the one of Connect to this computer.
The ribbon menu depends on the profiles:
Items \ Profiles Observer System Engin. System Admin

The Security administrator accesses only a private item (see below). Detail of privileges:
Privilege Observer System engineer System admin. Security admin.

Information pane x x x
Errors overlays x x x
View log (event and security) x x x x
View database information x x x
View date and time x x x
Monitoring x x x
Boards and IED states x x x
Download states x x x
Upload COMTRADE disturbance x x x
View and update database x x
Telnet (if enabled) x x
AVR pane x x
Modify date and time x x
Boot parameters x
Download software x
Update bootrom x
Stop application software x
File explorer x
Reboot x
Enable/deactivate communication x
port (shell+Telnet)
Change password x
Set security policy x
7.10 Modes and permitted operations
BOOTPROM C264 stopped before the boot (whether a networkboot or flashboot / first count-down),
only the CAT can detect C264
STOPPED C264 stopped before the application launch after the boot (whether a networkboot or
flashboot / second count-down), or after a Stop command
MAINTENANCE Ready to receive a DB
ACTIVE Nominal state
STAND-BY Spare C264 in redundancy architecture
SIMULATION
FAULT DB issue (confirmed by reboot)
HALT The number of faults permitted per day (normally 5) is overrun
INITIALIZATION Transient state, no filter
Some operations might require the computer's mode changing. An operation can be
available for the main (or mono) rack (M) or even for an extension (A for All):
INIT SIMUL ACTIVE STANDBY MAINT FAULT HALT STOPPED BOOT

Status general A A A A
board A A A A
IEDs A A A A
Multir. M M M M
Database view M M M M M M M
load M M M M
switch M M M M
suppr. M M M M M M M M
Settings M M M
Events M M M M
Logs errors A A A A A A A A
agency M M M M M M M
AVR M M
Disturb. M M
Datehour A A A A
Bootnetw A A A A A A A A
System A if stopped A A
Bootrom A if stopped A A
Browse explore M M M M M M M M
form. fl. A if stopped A A A A
Telnet A A A A A A A A
7.11 Routine operations

7.11.1 Display status and monitoring
Three tabs are available with a Refresh button for each of them:
• General lists the computer's and database identification information; in multirack

configuration, the cluster membership is also displayed
• Boards is a dashboard:
− at the board level:
- status (reflected in the board name: green for present and configured, blue for
missing or not configured, red for configured but faulty)
- index (as in SCE): @0, @1 etc

− at the I/O level: status; tool tips include nature over the number, on/off over the led
As the changes of state may be frequent, an auto refresh occurs at each tab opening, and
can be triggered each 5 second for 1 min (box Automatic refresh).
• IED Networks shows, for each computer's port, the link status of the IEDs (red for
mute, green for present) and lists the configured IEDs on the legacy bus (name,
connection state). A banner identical to that in LHMI and C264 shows (refer to
C264/EN HI chapter).
NOTE 1: In multirack configuration, extensions are also shown
NOTE 2: Tunnelling requires PatuSpy software and MiCOM S1
7.11.2 Manage database (subject to privilege)
A sketch illustrates the present configuration:
• the active database, on the left, is coloured
• the standby database, on the right is grayed
• both labels include versions number, order of downloading (DB1, DB2 ..), optional
attribute (Modified, Missing …)
The setting can be done in various ways (through the computer LHMI, through
downloading...). For more details, refer to the chapter C264/EN FT.
To download a database:
• browse the disk structure to select a versioned database archive (the USB port is out
of the scope):
• Click the button Select the SCE database; wait till a form shows (a maximum of 1 hour
is needed to transfer and store a 20 Mb file):
The drop-down list enrolls all the computers in this session's databases (<network
name in SCE>.adb)
• Assign to the computer one C264 in this list
• If the need arises:
− select another data base through the link Select another SCE database
− To change the version number, select the box Substitute the database and type a
new Version Number
− To download also the mpc file (e.g. in RTU standalone configuration, where no
SMT is available), click Save the SCE database into the computer. In the
<DB_name>.zip, CAT selects and downloads the <BD_name>.mpc file. Only one
.mpc file can be archived (a new download deletes and replaces the previous file).
As VxWorks limits the file name to 8 characters, the downloaded file is renamed
“DB.zip”.
<Current Database version><Standby Database version>
Start database
N-1 Z uploading
N Z
Sa
v <C264 Network name>.adb
DB_name.zip da t e t h
the abas e S C
co e in E
mp t o
ute
r
Z
DB.zip
• Click the button Start database uploading; this updates the databases sketch and
displays a report of the downloading:
• To switch active and standby databases:
− click Switch databases
− wait till the computer reboots
− reconnect: the version numbers are exchanged
• To delete both databases, click clean all databases. This shows a disconnected mode.
7.11.3 Edit settings (subject to privilege)
Used to launch MiCOM S1. Refer to the chapter C264/EN ST.
CAT is disconnected for MiCOM S1 to take over.
A setting in MiCOM S1 results in the suffix Modified being appended to the database label.
7.11.4 Manage events and states (subject to privilege)

Two kinds of information are displayed: events and latest datapoint values.
EVENTS:
Three tabs are available with a Refresh button and output buttons (Save as text files, Print)
for each of them; CAT reads the event log saved in computer's flash memory and transfers
the log in a file.
• Event Log displays:
− the computer's software content
− the computer's and database's information (in SCE, 'Device name' is called
'Network name' and 'Description' is Short name)
− the events that occurred whether automatically or manually driven, in the reverse
chronological order, in a tabular way: <date> <time> <object> <sub-object> <event
label> <state>; the cyber security events are preceded with the character @
C264 objects include #C264, HMILCD, MAINT (flash directory) …
The date and time are provided by C264 not by the CAT machine.
• Event Log Parameters and Printer Parameters tabs help you to choose the verbosity
of traces. The parameters are detailed in each information frame:
"Disable event log storage" (default state) disables event log storage mechanism. The state
is updated in function information frame.
− Connection port can be:
/null: no printer
"/Smc1/tty": serial port on front panel (setting or shell connector)
"/Scc1/tty": port 1 on BIU
"/Scc2/tty": port 2 on BIU
"/Scc4/tty": port 4 on Cpu3 board (rear side)
− Line: number of lines displayed per page (typical value: 50000)
− Suppress: number of suppressed lines when the buffer is full (typical value: 300)
− Baud rate: 4800 thru 19200
− Buffer size used by the PRINT task to sock lines (typical value: 1000)
− Printer control mode can be one of:
"0 (none)" no control

"1 (Xon/Xoff)" software control
"2 (Hard)" hardware control
"3 (Both)" software and hardware control
VALUES
• States snapshots displays a header, identical to the display in Display status/general,

followed by the present time-tagged values of data points; they are sorted according to
the types:
− Binary inputs
− Measurements
− Counters
− Status Indication Group (MPS): boards status, built-in function MPS
− Step Positions: TPI
The picture for each type are captured and saved by

7.11.5 Display errors and Agency logs
• System error files:

The content of /flash/systrap/index.txt is displayed. It shows the number of software errors
since the initialization of the index, the date and time of the last error and the name of the file
containing information on this error.
This file (containing the last systrap) is pre-selected in the drop-down list Select system error
file number.
The latest ten error files are archived: select one of them using this list.
• Agency Log: the content of /ramdev/agency.log is displayed.

7.11.6 Display AVR data
The AVR Log tab lists the number of tap changes on various time spans: since C264 init
(Global), since the latest reset time with the related button (Partial), permanently on a
slipping period set in MiCOM S1. At reset, the page is refreshed. The I² and times (0 thru 63)
of use of each tape are also summed:
The Global/Partial histogram tabs show the Pareto charts.
7.11.7 Waveforms
The list of disturbance files is displayed in the text area.
To refresh it, press Refresh.
To download COMTRADE files:
• Select the destination directory in the PC.
• Click the button Transfer waveforms from the computer to this directory. All the files
are uploaded.
The button Clear all waveforms is used to erase the Fast Waveform from MiCOM C264P
flash memory.
7.12 Expert Functions

7.12.1 Manage date and time (read, and change depending on profile)
• The first section shows data read on computer:
− First running date of the computer (located in /flash/MAINT/firstrd)
− Computer total usage duration: number of hours the computer has been running
(located in in /flash/MAINT/ophours)
• The second section is used to set a time and date value and send it to the computer.
If the box Synchronize with Windows time is checked, the Current computer time cannot be
set: the current date and time are taken from Windows XP on the PC and displayed.
Set year button: it is useful to set only the Year on a new C264 because the IRIG B signal
does not include the Year data; the new C264 gets the default Year value from Windows XP.
• The third section specifies what defines the seasonal clock shifts:
− the active database through the SCE attribute Scs/General/Time zone
− forcefully set times daylight
• Synchronism and IRIG-B status

The PACiS system operates with the SNTP master server connected to the SBUS. The
SNTP master server synchronizes all of the devices connected to the SBUS.
In the PACiS system, every 20 seconds the GPS sends an IRIG B signal to the SNTP
master server. The IRIG B signal includes the Second, Minute, Hour, Day and Month.
The IRIG B signal does not include the Year.

CAUTION: TO CHANGE THE YEAR OR THE TIME-DATE DATA, CONNECT THE
CAT ONLY TO THE SNTP MASTER SERVER. DO NOT CONNECT THE
CAT TO THE NEW C264 OR TO A CLIENT. IF YOU CHANGE THE YEAR
OR THE TIME-DATE DATA ON A NEW C264 OR ON A CLIENT, THE
PACIS SYSTEM RECEIVES DATA FROM TWO SOURCES: THE IRIG B
SIGNAL, AND THE NEW C264 OR CLIENT. THIS CAN CAUSE A DATA
INCOHERENCY.
− Make sure that the CAT is connected to the SNTP master server
− Set the year (refer to the second section)

The SNTP master server changes the Year and the Day. Within 20 seconds, when the
SNTP master server receives the next IRIG B signal, the SNTP master server keeps the
Year you typed and changes the Day to agree with the IRIG B signal.
The SNTP master server sends the time-date data, including the correct year, over the
SBUS to all of the devices.
IRIG-B STATUS
If IRIG-B interface is present on the cpu3 board, this displays IRIG-B validity, RTC local time,
IRIG-B signal level, MSP430 software version.
7.12.2 Manage boot and network parameters
• The first section allows to know and modify the disk the computer boots on:
− Flash boot: flash memory
− Network boot, that is using ftp (the IP address is in the second section)
− Boot prom boot: the computer is stopped after the boot
• The second section allows to modify the network parameters:

It is recommended that the two IP addresses belongs to different domains, otherwise CAT
does not allow to configure same IP address on both Ethernet ports.
FTP server host IP is the Internet address of the host to boot on (type 127.0.0.1, the local
host, if no host is defined).
• The third section allows to assign addresses to the racks in a multi-rack configuration
A group is a cluster including a main rack and several secondary racks. Main 2 means the
computer serves as a back up to the Main 1 one (redundancy).
• The fourth section allows to access the password required to log in WFTD (it is set in
WFTPD/Security/User-rights)
For the new parameters to be effective, click Apply parameters (click anywhere in the pane
first, if the button is dimmed).
7.12.3 Manage communication ports
It is possible to disable some communication ports for all users:
• a Shell: e.g. HyperTerminal through the serial front port (it applies only to Rx on C264
side; Tx is always active, for debugging purpose)
• Telnet: see further; if it has been disabled, restart the C264 after re-enabling Telnet.
• Ethernet port No 2: Cpu3 board second port; it can be used to separate IEC61850
flows and Scada flows, reports and gooses, etc. For more details, refer to the chapter
3.5 in C264/EN FT. In Multirack configuration, it must be enabled as it is used for inter-
rack communication.
7.12.4 Load application software

1. Stop the computer before loading new application software.
2. Select application software with the file explorer (USB ports are in the scope).
3. Download it.
4. Reboot the computer.
7.12.5 Load bootrom software
A file explorer is used to download a bootrom software (USB ports are in the scope)
1. Stop the computer before loading new bootrom software.
2. Select bootrom software (bootrom.ffh) with the file explorer (USB ports are in the
scope).
3. Download it: it is transferred to computer /RAMDEV/ and duplicated in the flash.
4. Reboot the computer.
7.12.6 Browse computer files

Files can be exchanged between the PC and the computer (RAMDEV and Flash) and also
deleted. If a new files does not show in the explorer, collapse the container (sign –) and
expand it again (sign +).
Tip out a file from one side to the other using the buttons:
The files name cannot be changed; only files with DOS name format (8. 3 character format)
can be copied.
To format the flash memory:
• switch the computer to stopped or boot mode
• Click the Format flash memory button and wait till the end.
NOTE: The passwords and logoff time-outs are spared by this operation.
7.12.7 Launch a telnet session

To perform tasks that CAT cannot handle, launch the default Windows Telnet client on the
operator PC and wait for the login request:
The "logout" command or the windows close can be used to terminate the session.
As Telnet is launched independently of CAT, multi sessions on two or more computers are
possible.
As Telnet used TCP/IP stack, the computer has to be accessible from the PC in this mode.
7.13 Security administrator functions

At installation, no account might be locked and no password is in force (keep the field blank).
The security tasks include:
• Management: all the parameters are profile-specific, but valid for all of the three clients
(LHMI, CAT, MiCOM S1): a strong password is desirable (refer to PACiS/EN CS
chapter), 8 characters are indispensable
To unlock an account (observer/system engineer/ system administrator):
− Select the user account in the drop-down list (second section)
− Click the button Unlock Account.
Settings:
Field Units Step Minimum Maximum Default

Lockout after … attempts – 1 0 4 2
Reset counter after Minutes 1 1 3 2
Lockout duration (blocking) Minutes 1 1 30 5
Logoff after Minutes 1 1 10 10
Setting cycle: select account, fill up the form, press Apply Settings, wait for the report, cycle.
• Security log reading: it is a subset of event logs: the events that occurred whether
automatically or manually driven, in the reverse chronological order, in a tabular way:
<date> <time> < HMI where event occurred > <profile><event type>
<state><description> the HMI field is empty if the log entry is generated at C264 init
for status of port:
Event types:
− Login/Log off
− Password change (NERC compliant or not; rules reminded in the Management

tab)
− Antivirus status
− Account un-/blocked (except automatic unblocking due to time-out expiry)
− Telnet de-/activated
− Shell write de-/activated
− ETHERNET port1 de-/activated

Press the Refresh button.
These cyber security events are preceded with the character @.

The log encompasses events from CAT, but also MiCOM S1 and DHMI. The circular file can
store up to 2048 events. Default name: <year><hh:mm:ss>_<short name>_SecurityLog.txt
It is used for a security audit.
• Denying access to the web server at any rate.

8. DOWNLOADING DATABASE
MiCOM C264 requires a database to operate. It stores up to two databases, named “current”
and “stand-by”. Only the current database is used for operation. The second database can
be downloaded when the computer is in operational or maintenance mode. A specific control
allows switching between the two stored databases.
PACiS SCE (System Configuration Editor) is used to generate the databases. SMT (System
Management Tool) or CAT (Computer Administration Tool) are used to download and switch
the databases.
The use of SMT or CAT depends on the number of computers. For several computers on the
same Ethernet network, it is recommended to use SMT in order to insure database
coherency between computers.
8.1 Database download with CAT
8.1.1 Loading DB under CAT
First action is to copy the .zip database issued from SCE on your PC.
8.1.2 Download DB onto C264
On the CAT application:
− Access your C264 by select “Search computers” button
− Select your MiCOM C264 in the list
− Click the “Data Base” Menu button
− Click the “Select a Data base version” button, choose the bd.x.xx.zip file
corresponding to the database you want to use and click on “OK”; as a result, the .adb
files in the archive are transferred in the folder <installation folder>/computer/cat/db
− In the “Choose your Download” list, choose the “Database Only” item; this
opens a dialog box where you choose one “.adb” file of your computer and click on
“OK”
− When it is done, click on “Switch data bases” button; the MiCOM C264 computer
restarts on the database you have downloaded. It starts in operational mode.
Remark: On standalone C264 application (C264 not associated to any other
PACiS IEC61850 equipment), the source database (MPC file) can be
stored on the CPU270 (up to 20MB file size); this will be possible by
selecting “DATABASE + MPC, on the download list box:
NOTE: Do not put your archive on the desktop nor in the MyDocuments folder
(the path must no include blanks).
8.2 Database download with SMT

8.2.1 Loading DB under SMT
First load the DB version (menu Databases > Add database…). The DB is then stored on the
hard disk and appears in the database list.
Right click to “set current” the DB, then to send a “connect all”. SMT should then be
communicating with the computer, if not communication wiring and settings should be
checked.
8.2.2 Download DB onto C264
Still using right buttons choose the “download all” option and wait for the acknowledgement
of a successful transfer.
NOTE: After a format and a bootInstall of VB6.19 version C264 and a C264 reboot
using the CAT, the SMT cannot find the connected C264; therefore it is not
possible to load a DB. To retrieve the C264, reboot it from the shell (Telnet button).
8.2.3 Switch to downloaded data base
If no database has previously been installed then the database is automatically set to be the
running database. If there is a database already installed then the downloaded database will
become the standby database. In this event, the new database has to be switched to make it
the running database. In both cases it is necessary to reboot the computer to put the
database into running mode.
9. AFTER COMPUTER INSTALLATION

Installation is now complete.
In the event of any problems refer to the chapter C264/EN MF Maintenance and faultfinding.
10. OPTIONAL INSTALLATION

Optional hardware modules include:
• IRIG B connection
• Printer
10.1 External master clock connection
With the option of the CPU board, an external standard BNC connection is used to receive
external master clock synchronisation. The recommended external master clock is the hopf
6870 radio clock.
Installation should follow the standard rules of BNC cable installation including length limit
and optional 50 ohms termination.
For installation of the external master clock, refer to its documentation and to the summary in
PACiS system/EN IN chapter.
External IRIG B synchronisation should be configured in the computer database.
10.2 Printer installation
A printer can be installed permanently for the SOE, or temporally for
commissioning/maintenance use. Data labelling is defined with PACiS SCE.
The printer should be connected to either port 1, 2, 3 or port 4 of the computer.
If the port is on the BIU board, the board has to be configured for RS232 by using the correct
jumper configuration.
Furthermore, a configuration file (included in database) has to be installed onto the computer
with the printer communication parameters.
MiCOM C264/C264C
SETTINGS
CONTENT
2. TREE PANEL NAVIGATION 4
3. TREE PANEL PARAMETERS 5
4. MiCOM S1 (MS1) 12
4.1 Presentation of parameters in MiCOM S1 12
4.2 Upload a setting file to C264 14
4.2.1 How to Send setting files to C264 14
4.2.2 How to navigate into MiCOM S1 15
4.2.3 How to edit online C264 values 15
4.2.4 Edit ARPCCN parameters 16
4.2.5 Edit AVR parameters 17
4.2.6 Edit AUTORECLOSER ( TYPE 1 ) parameters 19
4.2.7 Edit I²t parameters 19
4.2.8 Edit INTERNAL SYNCHROCHECK ( TYPE 1 ) parameters 20
4.2.9 Edit FBD parameters 21
4.3 Download a setting file from C264 22
4.4 The different computer modes of C264 23
4.5 MiCOM S1 acknowledge 24
C264/EN ST/C80 Settings
BLANK PAGE

This document is a chapter of the MiCOM C264 documentation. It describes the Settings -or
on-line- parameters, which can be modified in runtime on MiCOM C264 computers. The
setting is done through the LCD Local Control Display. It is only available with a GHU200 or
a GHU201 front face.
This chapter details settings mentioned in C264/EN HI (Human Interface) chapter with
default and range values.
2. TREE PANEL NAVIGATION
Tree panel is accessible from bay panels by selecting the following key:
All data points are grouped into features and folders. To access a given feature the operator
should navigate the panels using the arrow keys. The folders hierarchy is displayed in each
panel.
switches to neighbouring folder
switches to neighbouring folder
select and expand the folder switching to its first item
go up to father folder
At the bottom of the hierarchy, the folder is the single point of information, control or
parameter. Edit mode allows the operator to change values.
Enter into Edit mode. It then asks to enter the system engineer password.
Cancel edition and the data point modification
The most commonly used settings and controls are selected into a list. To browse the list the
operator navigates using the arrow keys. The modification/control sequence is cancelled by
. The selection is confirmed by .
3. TREE PANEL PARAMETERS

Available Values or
MENU TREE Parameter signification
[min;max](step)(unit)
COMMAND
MAIN
- RESET OP HOURS RESET To reset the number of
the C264 operating
hours.
- CHANGE MODE OP OPERAT, MAINT, TEST To change the C264
mode into active,
maintenance or test
mode.
- GLB ACK ALARM ACK To acknowledge all
C264 alarms
- GLB CLR ALARM CLEAR To clear all
acknowledged and reset
alarms
- DATE DATE To change the date.
Accepted if the C264 is
not synchronised
- TIME TIME To change the time.
Accepted if the C264 is
not synchronised. The
time format is hh : mn :
sec.
- DB SWITCH YES To switchover active and
standby databases.
- LANGUAGE LG1, LG2 To switchover
Language1 and
language2.
COUNTER
Counter 1
…
Counter N
- COUNTER value Counter value To change the counter
value.
CONFIG
COMPUTER
MAIN
- IP ADDRESS xxx.xxx.xxx.xxx To read the C264 IP
address
BAY
Bay 0
…
Bay N
INTERNAL S/C
- S/C associated Dev XXXX To read the name of the
device associated to the
synchrocheck
Available Values or
- THRES PRES LINE [0.5;1.1](0.01)(V) Multiplier of nominal
voltage above which the
line is LIVE.
- THRES ABS LINE [0.1;0.6](0.01)(V) Multiplier of nominal
voltage below which the
line is DEAD.
- THRES PRES BUS [0.5;1.1](0.01)(V) Multiplier of nominal
voltage above which the
bus is LIVE.
- THRES ABS BUS [0.1;0.6](0.01)(V) Multiplier of nominal
voltage below which the
bus is DEAD.
- DELTA VOLT LOCK [0.02;0.5](0.01)(V) Voltage difference
between bus and line
above which locking
close is not possible.
- DELTA FREQ LOCK [0;1](0.01)(hz) Frequency difference
above which locking
- DELTA PHASE LOCK [0;30](1)(deg) Phase difference
above which locking
- FMIN LOCK [45;65](0.01)(hz) Minimum acceptable
frequency for locking
close.
- FMAX LOCK [45;65](0.01)(hz) Maximum acceptable
frequency for locking
close.
- DELTA VOLT COUPL [0.02;0.5](0.01)(V) Voltage difference
above which coupling
- DELTA FREQ COUPL [0;1](0.01)(hz) Frequency difference
- DELTA PHASE COUPL [0;30](1)(deg) Phase difference
- FMIN COUPL [45;65](0.01)(hz) Minimum acceptable
frequency for coupling
close.
- FMAX COUPL [45;65](0.01)(hz) Maximum acceptable
frequency for coupling
close.
Available Values or
- REAC TIME [0; 1000](10)(ms) Circuit breaker close
time in order to
anticipate the close
order for the coupling.
- ABS V CONF TIME [200;10000](20)(ms) Time after which the line
and the bus are
considered dead.
- ONLY V CONF TIME [200;10000](20)(ms) Time after which only
one voltage among the
line or the bus is
considered live.
- PRES V CONF TIME [200;10000](20)(ms) Time after which the line
and the bus are
considered live.
- CLOSE TO MAN SYN [200;10000](20)(ms) Time waited for having
locking conditions.
- CLOSE TO MAN SY C [1; 3600](20)(s) Time waited for having
coupling conditions.
- CLOSE TO MANUAL [200;10000](20)(ms) Time waited for having
dead-dead or dead-live
conditions.
- CLOSE TO AUTO [200;10000](20)(ms) Time waited for closing
conditions in case of
auto-recloser control.
- MAN SYN CLO COUPL YES, NO Flag to permit or not the
coupling for a “close with
synchrccheck” operator
control.
- MAN SYN CLO LCK YES, NO Flag to permit or not the
locking for a “close with
synchrccheck” operator
control.
- MAN SYN CLO LDBL YES, NO Flag to permit or not a
control with a dead line
and a live bus for a
“close with
synchrocheck” operator
control.
- MAN SYN CLO LLBD YES, NO Flag to permit or not a
control with a live line
and a dead bus for a
“close with
control.
- MAN SYN CLO LDBD YES, NO Flag to permit or not a
and a dead bus. for a
“close with
control.
Available Values or
- MAN CLO LCK YES, NO Flag to permit or not the
locking for a “normal
close” operator control.
- MAN CLO LDBL YES, NO Flag to permit or not a
and a live bus for a
“normal close” operator
control.
- MAN CLO LLBD YES, NO Flag to permit or not a
and a dead bus for a
control.
- MAN CLO LDBD YES, NO Flag to permit or not a
and a dead bus. for a
control.
- AUTO CLO LCK YES, NO Flag to permit or not the
locking in case of auto-
recloser control.
- AUTO CLO LDBL YES, NO Flag to permit or not a
and a live bus in case of
auto-recloser control.
- AUTO CLO LLBD YES, NO Flag to permit or not a
and a dead bus in case
of auto-recloser control.
- AUTO CLO LDBD YES, NO Flag to permit or not a
and a dead bus. in case
of auto-recloser control.
AR
Circuit breaker name
- FIRST CYCLE MONO [100;5000](10)(ms) Time between the first
protection trip and the
Circuit Breaker close
order for a 1 phase trip.
- FIRST CYCLE TRI [100;60000](10)(ms) Time between the first
protection trip and the
order for a 3 phases trip.
Available Values or
- SECOND CYCLE [1000;3600000](1000)(ms Time between the
) second protection trip
and the Circuit Breaker
close order.
- THIRD CYCLE [1000;3600000](1000)(ms Time between the third
) protection trip and the
order.
- FOURTH CYCLE [1000;3600000](1000)(ms Time between the fourth
) protection trip and the
order.
- RECLAIM TIME [1000;600000](1000)(ms) Time during which the
Circuit Breaker must
remain closed to
consider that the reclose
has succeeded.
- UNLOCK TIME [1000;600000](1000)(ms) Time during which the
remain closed after a
manual close or reinit
message in the lock
state to consider that the
unlocked has
succeeded
- MAN CLOSE TIME [1000;600000](1000)(ms) Time during which the
remain closed after a
manual close in clear
state to consider that the
closure has succeeded
and to avoid locking
definitively in case of
trip.
- 1PH TRIP SCHEME 0 to 4 Indicates how to use the
autorecloser with 1
phase trip:
0: AR_NOT_USED
1: AR_1P
2: AR_1P3P
3: AR_1P3P3P
4: AR_1P3P3P3P
- 3PH TRIP SCHEME 0 to 4 Indicates how to use the
autorecloser with 3
phases trip:
0: AR_NOT_USED,
1: AR_3P,
2: AR_3P3P,
3: AR_3P3P3P,
4: AR_3P3P3P3P
Available Values or
DEVICE
short name 1
…
short name N
- TIME OPEN [0;1000](1)(ms) Time duration for the
open contact.
- TIME CLOSE [0;1000](1)(ms) Time duration for the
close contact.
BI
Bi 1
…
Bi N
- MOTION00 FILT [0;600](100)(ms) Time of non
complementarity filtering
in the state 00: only use
for double digital input.
- MOTION11 FILT [0;600](100)(ms) Time of non
complementarity filtering
in the state 11: only use
for double digital input.
- PERS OPEN FILT [0;1200](100)(ms) Time of persistence
filtering in the state
Open or 0
- PERS CLOSE FILT [0;1200](100)(ms) Time of persistence
filtering in the state
Close or 1
- TOGGLING OPTION YES, NO Flag to validate or inhibit
the The toggling option.
MV
Mv 1
…
Mv N
- HYSTERESIS [1;50](1)(%) % of hysteresis applied
on thresholds.
- DEADBAND [1;50](1)(%) % of variation within the
Analogue Input is not
transmitted.
- THRESHOLD 1 [Min;Max](0.01)(XXX) Low low low threshold
(Lowest threshold of the
analogue input)
- THRESHOLD 2 [Min;Max](0.01)(XXX) Low low threshold
- THRESHOLD 3 [Min;Max](0.01)(XXX) Low threshold
- THRESHOLD 4 [Min;Max](0.01)(XXX) High threshold
- THRESHOLD 5 [Min;Max](0.01)(XXX) High high threshold
Available Values or
- THRESHOLD 6 [Min;Max](0.01)(XXX) High high high threshold
(highest threshold of the
analogue input)
COMM. PORT
Com 1
…
Com 4
- BAUDRATE baudrate * Baudrate of the
communication port
among:
50,100,200,300,600,120
0,2400,4800,9600,1920
0,38400, 56000.
- NB STOP BIT 1, 2 Number of stop bits
- NB BIT PER CHAR 7, 8 Number of bits per
character
- PARITY odd, even, none Parity
HMI
MAIN
- EXIT MT TIME [5;300](1)(s) Time after which the
Menu tree is
automatically left if there
is no pressed button.
- BACK LIGHT DELAY [5;300](1)(s) Time after which the
back light disappears if
there is no pressed
button.
- SELECT EXIT TIME [5;300](1)(s) Maximum time between
selection and execution
orders.
- BYPASS DELAY [20;120](1)(s) Time after which a
bypass is automatically
deselected.
BAY
Bay 0
…
Bay N
- SBMC DISPLAY YES, NO Flag to validate or inhibit
the display of the SBMC
mode
- DISPLAY DEV NAME YES, NO Flag to validate or inhibit
the display of the Name
od Devices in the Bay
Panel.
4. MiCOM S1 (MS1)
It describes the Settings -or on-line- parameters, which can be modified in runtime on
MiCOM C264 computers. Micom S1 application provides the facility to online view and edit
the parameters of C264.
The setting for the C264 parameters will be performed using a file transfer mechanism. The
setting is allowed only if the C264 is in Operational mode. In case of C264 redundancy, the
setting can be performed only on the Active computer (to avoid discrepancy between both
computers parameters, a manual load of settings is to be realised on the backup C264).
PC minimum configuration:
• At least Pentium 3 or similar
• Processor frequency: At least 700MHz
• At least 100 Mb free space on hard disk
• A CD-ROM drive
• An Ethernet 10/100 Mb/s port
• Operating System: Windows XP SP2 or SP3 32bits
• Windows installer 3.1
• SBus agency
• WinPcap 4
• Antivirus Avira Antivir Professional Version 9.0 or later (that is recommended for
PERMA A2.15 architecture).
Install the CAT software. Go to Program -> Pacis -> Computer ->MicomS1 and click
settings.
At MiCOM S1 launch, the application requests the Microsoft security center to check that the
antivirus is present and up-to-date. If antivirus is not present or not up-to-date, MiCOM S1
can still be launched, but the user is warned that antivirus is not present or outdated.
Go to Program -> Pacis -> Computer -> FTPD and click wftpd32.
4.1 Presentation of parameters in MiCOM S1

The hierarchy of parameters in MiCOM S1 is:
• OP.PARAMETERS: global C264 parameters in read-only mode (database version,

IP address, computer name, …) ; it includes the same banner as C264:
• CONFIGURATION : general parameters for protective functions
• PROTECTION GROUP 1 : parameters for each protective function
• PROTECTION GROUP 2 : parameters for each protective function
• AUTOMAT.CONTROL
• Synchrocheck
• AVR
• Auto-recloser bay 1
• Auto-recloser bay N
• ISaGRAF Automatism 1
• …
• ISaGRAF Automatism N
• PSL Automatism 1
• …
• PSL Automatism M
The description of each parameter can be seen in below figure.
Built in functions like ISaGRAF, PSL automatism, AVR and Auto-Recloser are configured in
SCE. Only parameters of configured functions are visible and editable in MiCOM S1.
It is possible to set the following functions:
• Automates' built-in as autorecloser, AVR (if applicable), synchrocheck (if applicable),

protective function implemented for PACiS
• ISaGRAF: (float or integer threshold & Boolean)
• Two kinds of parameters in FBD: The timeout used for (Ton / Toff) and the parameter
(Boolean) validation
The file .set can be found in the Settings folder of the database (.zip).
4.2 Upload a setting file to C264
Schneider Electric
The MiCOM S1 application indicates that a file .VAL is available. The “VAL” file is transferred
via FTP. C264 is the FTP client. An FTP server is mandatory on the MiCOM S1 host PC.
MiCOM S1 application transfers “VAL” file to a computer defined by its IP address. Computer
checks the coherency of this file and acknowledges it positively or negatively.
MiCOM S1 uploads values to C264 using the function “Set Settings”
4.2.1 How to Send setting files to C264
Connect to the C264 as a System engineer using CAT.
Select a topic in the MS1 explorer.
Select the menu Transmission -> Set Settings.
Choose the type of generation Build values / Build and send values
Schneider Electric
=>
4.2.2 How to navigate into MiCOM S1

Click in the explorer pane:
4.2.3 How to edit online C264 values

After setting, a red star shows in the Edited column:
4.2.4 Edit ARPCCN parameters

List of parameters can be modified:
• Numbers of fast cycle for earth fault min = 0 , max = 1 step = 1 cycle step
• Numbers of slow cycle for earth fault min = 0 , max = 2 , step = 1 cycle step
• Numbers of fast cycle for phase fault min = 0 , max = 1 , step = 1 cycle step
• Numbers of slow cycle for phase fault min = 0, max = 2, step = 1 cycle step
• Reclaim time fast cycle, min = 10000 , max = 15000 , step = 1000
• Reclaim time slow cycle, min = 3000 , max = 10000 , step = 1000
• Reclaim time manual close , min = 10000, max = 20000 , step =1000
• Timer cycle fast earth , min = 100, max = 500 , step =1
• Timer cycle slow1 earth , min = 10000, max = 30000 , step =1000
• Timer cycle slow2 earth , min = 10000, max = 30000 , step =1000
• Timer cycle fast phase , min = 100 , max = 500 , step =1
• Timer cycle slow1 phase , min = 10000 , max = 30000 , step =1000
• Timer cycle slow2 phase , min = 10000 , max = 30000 , step =1000
4.2.5 Edit AVR parameters

To view the range allowed for each parameter, refer to the chapter AP.
4.2.6 Edit AUTORECLOSER ( TYPE 1 ) parameters

List of settable parameters:
• Ist period triphased time min = 100, max = 60000, step = 10
• 2nd period triphased time min = 1000, max = 3600000, step = 10
• 3rd period triphased time min = 1000, max = 3600000, step = 1000
• Reclaim delay time min = 1000, max = 600000, step = 1000
• Inhibition delay min = 1000, max = 3600000, step = 1000
• Unlock delay min = 1000, max = 600000, step = 1000
• Manual close delay min = 1000, max = 600000, step = 1000
• Functioning mode (1 ph trip) types = 1P, 1P-3P, 1P-3P-3P, 1P-3P-3P-3P
• Functioning mode (3 ph trip) types = 3P, 3P-3P, 3P-3P-3P, 3P-3P-3P-3P
4.2.7 Edit I²t parameters

4.2.8 Edit INTERNAL SYNCHROCHECK ( TYPE 1 ) parameters

List of parameters can be modified:
SCHEMES
Close with synchro: Coupling and locking = YES/NO
Close with synchro: locking = YES/NO
Close with synchro: Line Dead and Bus Live = YES/NO
Close with synchro: Line live and Bus Dead = YES/NO
Close with synchro: Line Dead and Bus Dead = YES/NO
Close : Locking = YES/NO
Close : Line Dead and Bus Live = YES/NO
Close : Line live and Bus Dead = YES/NO
Close : Line Dead and Bus Dead = YES/NO
Autorecloser Locking = YES/NO
Autorecloser Line Dead and Bus Live: = YES/NO
Autorecloser Line live and Bus Dead: = YES/NO
Autorecloser Line Dead and Bus Dead = YES/NO
TIMINGS
Parameters T1 : Presence deltas test duration : min = 200, max =10000 ,step = 20
Parameters T2 : Presence test duration : min = 200, max =10000 ,step = 20
Parameters T3 : absence deltas test duration : min = 200, max =10000 ,step = 20
Parameters Ta : close time of circuit breaker : min = 0, max = 1000,step = 10
Close with synchro scheme delay : min = 1, max =3600 , step = 1
THRESHOLDS
Line voltage over threshold: min= 0, max = 100,step = 1
Line voltage under threshold: min= 0, max = 100,step = 1
Bus voltage overthreshold: min= 0, max = 100,step = 1
Bus voltage underthreshold: min= 0, max = 100,step = 1
Voltage delta threshold for locking: min= 0, max = 100,step = 1
Minimum frequency for locking: min= 45.5, max = 59.5,step = 0.1
Maximum frequency for locking: min= 50.5, max = 66, step = 0.1
Frequency delta threshold for locking: min= 0.02, max = 0.1,step = 0.01
Phase delta threshold for locking: min= 0, max = 90,step = 1
4.2.9 Edit FBD parameters

Depending on the individual SCE attribute ‘’Editable in MiCOM S1’’, each timer value can be
set or not, visible or dimmed.
Editable parameters of FBD Timer
Editable parameters of Boolean

FBD Boolean: True/false
4.3 Download a setting file from C264
Schneider Electric
The MiCOM S1 application needs to have a .VAL file located in the computer’s flash. The
“VAL” file is transferred via FTP. When data transmission is finished; the C264 sends an
acknowledgement message. This message give permission to read the .VAL received.
MiCOM S1 uses the .VAL file in order to get back and update the .SET values. (Only values
are used by MiCOM S1).
MiCOM S1download values from C264 using the function “Get Settings”
NOTE: A new register key is created for use the settings. Refer to
C264/ENMF.
The following figures show the how to get val file from C264:
4.4 The different computer modes of C264

Active mode
In this mode, the description previously described applies.
Standby mode
In this mode, tasks that can be set are disarmed. In redundancy mode, the protection
functions are not activated.
The C264 denies the transfer of the setting file via MiCOM S1 application when it is in
standby mode.
In order to download settings in this case, the active C264 is to be stopped ; that causes the
inactive C264 to become active.
NOTE: There is no automatic consistency check of the two setting files : this
is to be verified by operator.
Test mode
In this mode, the description previously described for “active mode” applies.
Other mode
No possible operation.
4.5 MiCOM S1 acknowledge
Receipt value Micom S1 message

0 Setting done
1 Incorrect C264 DB Version revision
2 Number of protections incoherent with DB
3 No setting file in the C264
4 FTP server problem\nVerify that the FTP client is launched & try again
5 C264 internal error
6 C264 incorrect number
7 Setting impossible, command running
8 Error IED address
9 Incompatible data structure
10 IED setting failed
11 Compatibility error between C264 and SCE
12 Number of columns of the .VAL file incorrect
13 Error : label too long
14 Error PROTECTIONS C264 : Value not between MIN and MAX
15 Error ELECTRE d : Value not between MIN and MAX
16 Error FBD : Value not between MIN and MAX
17 Error ISAGRAF : Value not between MIN and MAX
18 Error AUTO RECLOSER : Value not between MIN and MAX
19 Error AUTO RECLOSER PCCN : Value not between MIN and MAX
20 Error SYNCHROCHECK : Value not between MIN and MAX
21 Error AVR : Value not between MIN and MAX
22 Error PROTECTIONS C264 : Verification phase incorrect
23 Error ELECTRE d : Verification phase incorrect
24 Error FBD : Verification phase incorrect
25 Error ISAGRAF : Verification phase incorrect
26 Error AUTO RECLOSER : Verification phase incorrect
27 Error AUTO RECLOSER PCCN : Verification phase incorrect
28 Error SYNCHROCHECK : Verification phase incorrect
29 Error AVR : Verification phase incorrect
30 Error : File OK but a problem occurred during file copy
31 Error : Setting file for CPU3 sent to a CPU2
32 Error in file checksum
33 Error : Micom S1 task not present
34 Error : Trip in progress
MiCOM C264/C264C
COMMUNICATIONS
CONTENT
2. SCP COMMUNICATION 6
2.1 Communication on Station bus 6
2.1.1 Finality 6
2.1.2 Inputs 6
2.1.3 Supported services 6
2.1.4 Supported data objects 7
3. INTER-RACK COMMUNICATION 8
3.1 Overview 8
3.2 Main1-Main2 communication 8
3.3 Main-Extension communication 8
4. SCADA COMMUNICATION 9
4.1 Overview 9
4.2 SCADA common functionality 9
4.2.1 Interface to SCADA 9
4.2.2 BCU 10
4.2.3 RTU standalone 10
4.2.4 Behaviour and specific treatments 11
4.2.5 Data sent to SCADA 13
4.2.6 Data sent to MiCOM C264 14
4.3 Slave DNP3 profile (serial or over IP) 15
4.4 Slave IEC 60870-5-101 profile 25
4.4.1 System or device 25
4.4.2 Network configuration 25
4.4.3 Physical layer 26
4.4.4 Link layer 26
4.4.5 Application layer 27
4.4.6 Basic application functions 31
4.4.7 Protocol Requirements 35
4.4.8 Application Functions 35
4.5 Slave IEC 60870-5-104 Server profile 38
4.5.1 System or device 38
4.5.2 Network configuration (Network-specific parameter) 38
4.5.3 Physical layer (Network-specific parameter) 39
4.5.4 Link layer (Network specific parameter) 39
4.5.5 Protocol Requirements 40
4.5.6 Application layer 40
4.5.7 Basic application functions 46
C264/EN CT/C80 Communications
4.6 Slave Modbus (MODICON) profile 50

4.6.1 Introducing MODBUS 50
4.6.2 Slave responses 51
4.6.3 Serial transmission mode 52
4.6.4 MODBUS Functions 53
4.6.5 Function 01 / 02 : Read Coil Status – Read Input Status 54
4.6.6 Function 03 / 04: Read Holding Registers / Input Registers 55
4.6.7 Function 05: Force Single Coil 57
4.6.8 Function 06: Preset single register 57
4.6.9 Function 08: Diagnostic [Sub-function 0 only] 58
4.6.10 Function 15 : Force Multiple Coils 58
4.6.11 Function 16 : Preset multiple registers 58
4.7 HNZ (Yemen) communication 59
4.7.1 Finality 59
4.7.2 Data sent to SCADA 59
4.7.3 Data sent to computer 62
4.7.4 Synchronisation 63
4.7.6 Structures of frames 66
4.7.7 Detailled list of messages of application 67
4.7.8 Sequence of dialogue 72
4.7.9 Summary of function code messages 76
4.7.10 Configuration 76
4.7.11 Cable 76
4.8 HNZ (Elenas) communication 77
4.8.1 Functional specifications 77
4.8.2 Data Specifications 85
4.8.3 Interface Specifications 93
4.8.4 Basic Concepts 96
4.8.5 Detailed Messages List 97
4.8.6 Startup Sequence 107
4.8.7 Message Summary 108
4.8.8 Cable 109
5. IED COMMUNICATION 110

5.1 Overview 110
5.2 IED Common functionality 110
5.2.1 Interface to IEDs 110
5.2.2 Behaviour 111
5.2.3 Data received from IEDs 115
5.2.4 Data sent to IEDs 115
5.2.5 Tunnelling 116
5.2.6 Limits and specifications 118
5.3 MODBUS communication 119

5.3.1 Scope of this section 119
5.3.2 Generic MODBUS Communication 119
5.3.3 Schneider Electric MODBUS COMMUNICATION 122
5.3.4 IED SPECIFIC MODBUS 151
5.4 DNP 3.0 Communication 156
5.4.3 Behaviour 157
5.4.6 Master DNP3.0 Profile 159
5.4.7 DNP.3 Level 3 Implementation Table 161
5.5 IEC 60870-5-103 Communication 167
5.5.3 Behaviour 168
5.6 IEC 60870-5-101 Communication 173
5.6.1 Purpose 173
5.6.2 Master IEC 60870-5-101 profile 173
BLANK PAGE

This document is a chapter of the MiCOM C264 documentation. It describes the various
standard communications protocols implemented in the MiCOM C264.
MiCOM C264 supports different types of communications:
• SCP Communication: communication over Ethernet IEC61850
• Inter-rack Communication: inside multirack configuration
• SCADA Communication: communication with an upper level SCADA system over

protocols (IEC 60870-5-101, IEC 60870-5-104, DNP3.0, MODBUS, DNP3 on TCP)
• IED Communication: communication with legacy IEDs. The MiCOM C264 is

considered as a master (IEC 60870-5-103, DNP3.0, MODBUS, IEC 60870-5-101)
2. SCP COMMUNICATION
2.1 Communication on Station bus
2.1.1 Finality
This item describes IEC61850-8-1 implementation inside MiCOM C264.
2.1.2 Inputs
2.1.2.1 Information: MiCOM C264 application SCP
The type of information that can be transmitted are:
• Changes of state of binary inputs
• Measurements (Analogue or CT/VT)
• Counters
• Controls
• Control acknowledgements
• Time synchronisation message
• Records (Event, fault, disturbance)
• MiCOM C264 information (Init. report, Operating mode, control mode, Date)
2.1.2.2 Information SCP MiCOM C264 application
The type of information that can be transmitted are:
• Changes of state of binary inputs
• Measurements (Analogue or CT/VT)
• Counters
• Controls
• Control acknowledgements
• Time synchronisation message
• Request for records
• Database downloading
2.1.3 Supported services
Services supported by the IEC61850 agency integrated in the MiCOM C264 are listed in the
ACSI service conformance statement defined in Table A.3 of document
MiCOM C264/C264P PICS.
2.1.4 Supported data objects

The following table describes the common class supported by the IEC61850 agency
integrated in the MiCOM C264:
Client Server
Common Class Comment
support support
Status
SPS Single input status YES YES
DPS Double input status YES YES
INS Integer input status YES YES
ACT Protection activation information YES YES
ACD Directional protection activation YES YES
information
Measurements
MV Measurement value YES YES
CMV Complex measurement value YES YES
WYE 3 phase + N measurement YES YES
DELTA Phase to phase measurement YES YES
Counters
BCR Binary counter YES YES
Control
SPC Single point control YES YES
DPC Double control output YES YES
BSC Binary step control YES YES
APC Analogue output YES YES
INC Integer control output YES YES
ISC Integer step control output YES YES
Description
LPL Logical node name plate YES YES
DPL Device name plate YES YES
Report Control Block
URCB Unbuffered report control block YES YES
BRCB Buffered report control block NO YES
3. INTER-RACK COMMUNICATION
3.1 Overview
A C264 is used as a main rack connected to a cluster of C264 extensions over an Ethernet
IEC61850 network.
Tunnelling is not possible in this architecture, and connecting IEDs directly on any C264
either.
No CT/VT connected on extensions.
A similar branch can be installed for redundancy purpose. In this case, no AOU board is
allowed.
3.2 Main1-Main2 communication

See FT chapter.
3.3 Main-Extension communication
An Ethernet IEC61850 network supports the same objects and services as the SCP
communication.
4. SCADA COMMUNICATION
4.1 Overview
C264 BCU C264 RTU Standalone

DNP3 Serial & over IP not supported
MODBUS Serial not supported
T101 Serial Serial
T104 TCP/IP TCP/IP
HNZ Not supported Elenas (Indonesia) & Yemen
Multi protocol management (C264 only):
• Four (4) different SCADA protocols can run simultaneously. Four (4) on Ethernet and
two (2) on Serial. Each protocol has an independant configuration and may have
same data.
• In T104 protocol, from the SCADA side, up to four (4) ports can be defined,
corresponding to one active port and three backup ports. IP addresses are configured
for each T104 client. Each T104 protocol can manage up to four (4) clients
simultaneously.
• In DNP3 over IP protocol is supported over two (2) Ethernet ports. Each DNP3
protocol can manage one (1) client only. All DNP3 on IP features are the same than
DNP3 serial features.
Redundancy (C264 only):
• The C264 RTU standalone redundancy (link and protocol) is supported by T101
protocol only. So the redundancy is not available for other protocols (DNP3, MODBUS,
T104, HNZ) and all protocols with the C264 BCU.
Common features to all SCADA communication and all protocols are specified below.
Specific features to each protocol are specified in subsequent paragraphs.
4.2 SCADA common functionality
4.2.1 Interface to SCADA
This paragraph describes the exchange of data between the “SCADA communication”
function and the Master SCADA. It includes two sub-paragraphs:
• Inputs: data received from SCADA.
• Outputs: data sent from the “SCADA communication” function to SCADA.

For each kind of protocol, it is indicated if the data is treated or not.
4.2.2 BCU
4.2.2.1 Input
Data DNP3 T101 T104 MODBUS

Remote link initialisation Treated Treated Treated Treated
General interrogation Treated Treated Treated Not Treated
Control Treated Treated Treated Treated
Setpoint Treated Treated Treated Treated
Time synchronisation Treated Treated Treated Not Treated
Database (download) Not Treated Not Treated Not Treated Not Treated
4.2.2.2 Output
Data DNP3 T101 T104 MODBUS

Digital input Treated Treated Treated Treated
Dated Digital input Treated Treated Treated Not Treated
Measurement (Events) Treated Treated Treated Not Treated
Measurement (Cyclical) Treated Treated Treated Treated
Counter Treated Treated Treated Treated
Tap position Treated Treated Treated Treated
Control acknowledgement Treated Treated Treated Treated
Setpoint acknowledgement Treated Treated Treated Treated
MiCOM C264 Disturbance Not Treated Slow waveform only Not Treated
Sequence Of Event file Not Treated Treated Treated Not Treated
4.2.3 RTU standalone

4.2.3.1 Input
Data T101 T104 HNZ HNZ

(Elenas) (Yemen)
Remote link initialisation Treated Treated Treated
General interrogation Treated Treated Treated
Control Treated Treated Treated
Setpoint Treated Treated Treated
Time synchronisation Treated Treated Treated
Database (download) Treated Treated Not treated
Switch database Treated Treated
Reboot computer Treated Treated
NOTE: The “Reboot Computer” function is restricted and only accessible after
the “database download”.
4.2.3.2 Output
Data T101 T104 HNZ HNZ

(Elenas) (Yemen)
Digital input Treated Treated Treated
Dated Digital input Treated Treated Treated
Measurement (Events) Treated Treated Treated
Measurement (Cyclical) Treated Treated Treated
Counter Treated Treated Not treated
Tap position Treated Treated Treated
Control acknowledgement Treated Treated Treated
Setpoint acknowledgement Treated Treated Treated
MiCOM C264 Disturbance Slow waveform only
Sequence Of Event file Treated Treated Not treated
4.2.4 Behaviour and specific treatments

NOTE: In subsequent paragraphs, the master station (e.g.: SCADA) is
referred to as the controlling station.
4.2.4.1 Initialisation
There is a running database for each SCADA link. At initialisation, a GI is performed on the
application in order to initialise these databases.
The GI sequence consists of different requests to the MiCOM C264 application in order to
get the value and state of all data (Binary input, measurement, counter, step position
indication).
4.2.4.2 General interrogation
The Outstation interrogation function is used for updating the controlling station after the
internal station initialisation procedure, or when the controlling station detects a loss of
information, or when the link layer connection has been re-established. The general
interrogation function of the controlling station requests the MiCOM C264 to transmit the
actual values of all addressed datapoints.
The MiCOM C264 marks the end of the general interrogation procedure by sending an
indication to the controlling station when the protocols allow it.
In multirack application and in redundant configuration, the main rack becomes the master
rack on General Interrogation reception.
4.2.4.3 Clock synchronisation
Clock in MiCOM C264 may be synchronised by the controlling station.
NOTE: The clock can be synchronised by other means: external clock, Master
Clock, operator. Only one source will be selected at a given time. This
selection is performed by the clock synchronisation function based on
configuration and priority level. However the controlling station is not
informed of this fact and must continue to send clock synchronisation
commands.
The controlling station must perform the correction made on the time sent in synchronisation
commands.
4.2.4.4 Database downloading and switching

This function is only implemented in T101 and T104 protocols. The SCADA can download a
database and only a database. Then the type of file is 1 (Transparent file) and the IOA
(information object address) must be 1. The database downloaded will be the standby
database.
To switch over this database, the SCADA must send a reset process command
(C_RP_NA_1 (105)) with cause of transmission equal to 6 (activation) and QRP field set to 1
(general reset of process)
4.2.4.5 Local/remote mode
A substation or a bay can be in local or remote mode. When it is in local mode it can not be
controlled remotely and when it is in remote mode, it can not be controlled locally.
Each Mode can be associated to a binary input.
4.2.4.6 Taking Control
A Substation can be configured in taking control mode. This means:
• At a given time, only one SCADA can send controls to the substation (the one which
has the control).
• To be allowed to send controls, a SCADA must take control of the substation by

sending a specific command to the MiCOM C264.
On each SCADA link, there is a binary input indicating if the corresponding SCADA has the
control of the substation.
On reception of a Taking Control command, the MiCOM C264:
• Puts the substation in Remote mode (if it was in Local Mode)
• Gives the control to the (last) SCADA which asks for it
− Reset the “Taking Control Binary input” of the SCADA which had previously the
control
− Set the “Taking Control Binary input” of the SCADA which asks the control
If the take control command is set for a SCADA, MiCOM C264 should refuse all commands
from other SCADAs.
4.2.4.7 SBMC mode
This mode is used to test a substation while it is in Remote mode. As this mode is a test
mode, MiCOM C264 won’t send all changes of state to SCADA.
When bay turns to SBMC mode, MiCOM C264 will send to SCADA all concerned data
(configured Bay Based in the SCE) at specific states defined in the SCE for the management
of SBMC.
For those data, change of state won’t be transmitted, but will be memorised by MiCOM C264
while the Bay is in SBMC mode.
When the Bay returns to Non SBMC mode, MiCOM C264 will send the current state of any
data that has changed whilst the Bay has been in SBMC mode.
4.2.4.8 Redundancy
Serial links can be configured as redundant. In this case, SCADA can send requests on both
serial links: “main link “or “redundant link”.
MiCOM C264 always responds on the link used by SCADA for requesting the slave
4.2.4.9 Automatic synchrocheck
SCADA can send control to synchronised circuit breakers with a facility to bypass the
synchrocheck.
4.2.5 Data sent to SCADA

After the initialisation sequence, MiCOM C264 Slave sends the state of all of its data to the
SCADA. The current state of data is sent as state or as change of state messages,
depending on the protocol.
The data, which can be sent to SCADA, is detailed in the paragraphs below.
4.2.5.1 Binary inputs
Binary inputs can be sent as states or as changes of state depending on the protocol.
A binary input can be associated with a single point or a double point.
NOTE: Multipoint status is not treated.
4.2.5.2 Measurements
Measurements can be sent in various formats: float, integer, normalised, scaled…
Measurements can be sent as periodical messages or as changes of state: variation,
threshold, and invalidity.
The choices of format and mode of transmission are done by configuration according to the
protocol.
4.2.5.3 Counters
Counters can be sent as spontaneous messages (changes of state) or on demand (counter
General Interrogation).
The choice whether to use spontaneous messages for a counter is done by configuration,
according to the protocol.
4.2.5.4 Tap position
Tap position indication (TPI) can be sent to SCADA as states or as changes of state. The
choice between state or change of state depends on the protocol. If the protocol allows the
both, the choice is done by configuration.
A digital input can be associated with a single point or a double point.
4.2.5.5 Computer disturbance file
Only Slow Wave Form is implemented for T101 or T104. At the most five slow wave form
files can be available at a time. The IOA of the first file is configured and the others are
consecutive. the type of file is 1 (Transparent file). When a slow wave form file is available,
an ASDU Directory (F_DR_TA_1 (126)) is sent by the computer with cause of transmission
spontaneous (3). The file is already available until a new file is created and replaces it. The
Scada can identify the file only with its date. The size of file must be lower or equal to the
size of one section
4.2.5.6 Sequence Of Events file (SOE)
The SOE is a circular file where Events of the MiCOM C264 are stored. There is one SOE
for each SCADA link.
The Events, which can be stored in SOE, are Binary Input and measurements. The choice is
done by configuration.
Following information in MiCOM C264 configuration are used to manage SOE file:
• For each SCADA protocol
− A flag indicating if SOE file have to be managed
− Identification of the SOE file on the link (Name, Address, …)
− The maximum size of the file
− The percentage of filling from which the MiCOM C264 will try to transmit the SOE
file
• For each BI / measurement
− A flag indicating if it must be stored in SOE

Rules for the SOE management are the following:
• At starting of the MiCOM C264, the SOE file is Empty
• When the SOE is full, the oldest Event is deleted and the new one is added
• As soon as the percentage of filling indicated in configuration is reached, the MiCOM

C264 tries to up-load the SOE file
• Once a SOE file has been successfully up-loaded, all Event sent are deleted from
SOE
4.2.5.7 Synchronisation status
MiCOM C264 can inform the controlling station about its synchronisation status.
According to the protocol, this may be done by a specific message or by a binary input.
4.2.6 Data sent to MiCOM C264
SCADA can send data to MiCOM C264. The type of data is described in subsequent
paragraphs.
4.2.6.1 Digital Controls or setpoints
A control is transmitted to the handling of control sequences function.
At the end of the control sequence an acknowledgement is sent to SCADA if protocol allows
it.
4.2.6.2 Counter commands
The commands allowed on counters are:
• Reset of a group of Counters
• Reset of all Counters
• Freeze of a group of counters
• Freeze of all counters
• Read ( frozen value) of a group of Counters
• Read ( frozen value) of all Counters

4.2.6.3 Synchronisation
Depending on the configuration, MiCOM C264 can be synchronised by a SCADA.
4.2.6.4 Computer reboot
The MiCOM C264 RTU standalone can be rebooted from SCADA. If a new database had
been downloaded and not switched yet, MICOM C264 performs a database switch before
rebooting.
4.3 Slave DNP3 profile (serial or over IP)
DNP V3.00 Device Profile
Highest DNP Level Supported : Device Function :

For Requests Level 3 Master Slave
For Responses Level 3
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels
supported :
_____________________________________________________________________________
_____________________________________________________________________________
Maximum Data Link Frame Size (octets) : Maximum Application Fragment Size (octets):
Transmitted: 292 Transmitted 2048
Received: (must be 292) (configurable: 15 to 2048 bytes)
Received 2048
Maximum Data Link Re-tries: Maximum Application Layer Re-tries:
None None
Fixed at 2 Configurable, range ____ to _____
Configurable, range ______ to ____ (Fixed is not permitted)
Requires Data Link Layer Confirmation:
Never
Always
Sometimes If ’Sometimes’, when?
________________________________________________________________
Configurable If ’Configurable’, how?
User option to set Data Link Confirmation to:
• Always – device will always request Data Link Confirmations.
• Multi-packet only – the device will request Data Link Confirmations when sending multi-packet
responses.
• Never – the device will never request Data Link Confirmations.
Requires Application Layer Confirmation:
Never
Always (not recommended)
When reporting Event Data (Slave devices only)
When sending multi-fragment responses (Slave devices only)
Sometimes _________ If 'Sometimes', when?
________________________________________________________________
Configurable If 'Configurable', how? _________________________________
Timeouts while waiting for:

Data Link Confirm None Fixed at ___ Variable Configurable
Complete Appl. Fragment None Fixed at ___ Variable Configurable
Application Confirm None Fixed at 10s Variable * Configurable
Complete Appl. Response None Fixed at ___ Variable Configurable
Others
* When reporting Event Data (Slave devices only) & When sending multi-fragment responses (Slave
devices only)
Sends/Executes Control Operations:
WRITE Binary Outputs Never Always Sometimes Configurable
SELECT/OPERATE Never Always Sometimes Configurable
DIRECT OPERATE Never Always Sometimes Configurable
DIRECT OPERATE - NO ACK Never Always Sometimes Configurable
Count > 1 Never Always Sometimes Configurable

Pulse On Never Always Sometimes Configurable
Pulse Off Never Always Sometimes Configurable
Latch On Never Always Sometimes Configurable
Latch Off Never Always Sometimes Configurable
Queue Never Always Sometimes Configurable

Clear Queue Never Always Sometimes Configurable
• Select timeout : configurable (same value for all controls)
A pulse duration can be specified from Scada, for trip and close control with a transient DO.
When no value is specified, the default configured value is used.
FILL OUT THE FOLLOWING ITEMS FOR SLAVE DEVICES ONLY:
Reports Binary Input Change Events when no Reports time-tagged Binary Input Change Events
Specific variation requested: When no specific variation requested:
Never Never
Only time-tagged Binary Input Change With Time
Only non-time-tagged Binary Input Change With Relative Time
Configurable to send both, one or the other Configurable (attach explanation)
(explanation below)
User option to have all Binary Input
Change Events returned as either:
• time-tagged OR
• non-time-tagged
Send Unsolicited Responses: Send Static Data in Unsolicited Responses:

Never Never
Configurable (attach explanation) When Device Restarts
Only certain objects When Status Flags Change
Sometimes (attach explanation)
ENABLE/DISABLE UNSOLICITED No other options are permitted.
Function codes supported
Default Counter Object/Variation: Counters Roll Over at:
No Counters Reported No Counters Reported
Configurable (explanation below) Configurable (explanation
below)
Default Object ____ 20 ______
16 Bits
Default Variation ____ 02 ______
32 Bits
Point-by-point list attached
Other Value ____________
Point-by-point list attached
User option to return all static counters in

User option to select roll over:
One of the following variations:
• 32 bit counters roll over at 2^32.
• 32-Bit Binary Counter
• 16 bit counters roll over at 2^16
• 32-Bit Binary Counter Without Flag
• 16-Bit Binary Counter
• 16-Bit Binary Counter Without Flag
Send Multi-Fragment Responses: Yes No
Binary Input (BI) double management :
For a BI double, two binary inputs are configured, with a point address for the open contact and the
address + 1 for the close contact. All the BI double are transmitted this way.
DNP3 level 3: IMPLEMENTATION TABLE
REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Codes Qual Codes (2) Func Codes Qual Codes
Obj Var Description
(dec) (hex) (dec) (hex)
1 0 Binary Input – All Variations 1 00,01,06,17,28 129 00,17,28

1 1 Binary Input 1 00,01,06,17,28 129 00,17,28
1 2 Binary Input with Status 1 00,01,06,17,28 129 00,17,28
2 0 Binary Input Event - All Variations
2 1 Binary Input Event without Time
2 2 Binary Input Event with Time
2 3 Binary Input Event with Relative Time
10 0 Binary Output - All Variations
10 1 Binary Output
10 2 Binary Output Status 1 129 00,17,28
12 0 Control Block - All Variations (1) 1 129 00,17,28
12 1 Control Relay Output Block (1) 1, 3,4,5,6 17,28 129 Request echo
12 2 Pattern Control Block 1 129 00,17,28
12 3 Pattern Mask 1 129 00,17,28
20 0 Binary Counter - All Variations 1, 7,8,9,10 06,17,28 1
20 1 32-Bit Binary Counter 1, 7,8,9,10 00,01,06,17,28 1129 00,17,28
20 2 16-Bit Binary Counter 1, 7,8,9,10 00,01,06,17,28 1129 00,17,28
20 3 32-Bit Delta Counter
20 4 16-Bit Delta Counter
20 5 32-Bit Binary Counter without Flag 1, 7,8,9,10 00,01,06,17,28 1 129 00,17,28
20 6 16-Bit Binary Counter without Flag 1, 7,8,9,10 00,01,06,17,28 1 129 00,17,28
20 7 32-Bit Delta Counter without Flag
20 8 16-Bit Delta Counter without Flag
1. Qualifier Codes (in hexa) (example of Binary Input)
Request Qualifier Response Qualifier

Range of Points (8 bits) 0 0
Range of Points (16 bits) 1 0
All Points 6 0
Count of Points (8 bits) 7 0
Count of Points (16 bits) 8 0
List of Points (8 bits) 17 17
List of Points (16 bits) 28 28
2. Qualifier Codes 17 and 28 are only available on one point, except for controls (controls can be selected/executed on one
or more points)
3. “Binary Counter - All Variations” (Object 20, Var 0):

Functions 7,8 ,9 & 10 are only available with qualifiers 06, 17 and 28
REQUEST RESPONSE
OBJECT
Obj Var Description
21 0 Frozen Counter - All Variations Static&event:1 00,01,06,17,28 129, 130

21 1 32-Bit Frozen Counter Static: 1 00,01,06,17,28 129 00,17,28
21 2 16-Bit Frozen Counter Static: 1 00,01,06,17,28 129 00,17,28
21 3 32-Bit Frozen Delta Counter
21 4 16-Bit Frozen Delta Counter
21 5 32-Bit Frozen Counter with Time of Freeze Event: 1
21 6 16-Bit Frozen Counter with Time of Freeze Event: 1
21 7 32-Bit Frozen Delta Counter with Time of
Freeze
21 8 16-Bit Frozen Delta Counter with Time of
Freeze
21 9 32-Bit Frozen Counter without Flag Static: 1 00,01,06,17,28 129 00,17,28
21 10 16-Bit Frozen Counter without Flag Static: 1 00,01,06,17,28 129 00,17,28
21 11 32-Bit Frozen Delta Counter without Flag
21 12 16-Bit Frozen Delta Counter without Flag
22 0 Counter Event - All Variations
22 1 32-Bit Counter Event without Time
22 2 16-Bit Counter Event without Time
22 3 32-Bit Delta Counter Event without Time
22 4 16-Bit Delta Counter Event without Time
22 5 32-Bit Counter Event with Time
22 6 16-Bit Counter Event with Time
22 7 32-Bit Delta Counter Event with Time
22 8 16-Bit Delta Counter Event with Time
23 0 Frozen Counter Event - All Variations 1 06,07,08 129, 130
23 1 32-Bit Frozen Counter Event without Time
23 2 16-Bit Frozen Counter Event without Time
23 3 32-Bit Frozen Delta Counter Event without
Time
23 4 16-Bit Frozen Delta Counter Event without
Time
23 5 32-Bit Frozen Counter Event with Time 1 06,07,08 129,130 17
23 6 16-Bit Frozen Counter Event with Time 1 06,07,08 129,130 17
23 7 32-Bit Frozen Delta Counter Event with Time
23 8 16-Bit Frozen Delta Counter Event with Time
REQUEST RESPONSE
OBJECT
Obj Var Description
30 0 Analog Input - All Variations 1 00,01,06,17,28 129

30 1 32-Bit Analog Input 1 00,01,06,17,28 129 00, 17,28
30 2 16-Bit Analog Input 1 00,01,06,17,28 129 00,17,28
30 3 32-Bit Analog Input without Flag 1 00,01,06,17,28 129 00,17,28
30 4 16-Bit Analog Input without Flag 1 00,01,06,17,28 129 00,17,28
31 0 Frozen Analog Input - All Variations
31 1 32-Bit Frozen Analog Input
31 2 16-Bit Frozen Analog Input
31 3 32-Bit Frozen Analog Input with Time of
Freeze
31 4 16-Bit Frozen Analog Input with Time of
Freeze
31 5 32-Bit Frozen Analog Input without Flag
31 6 16-Bit Frozen Analog Input without Flag
32 0 Analog Change Event - All Variations 1 06,07,08 129, 130
32 1 32-Bit Analog Change Event without Time
32 2 16-Bit Analog Change Event without Time
32 3 32-Bit Analog Change Event with Time 1 06,07,08 129,130 17
32 4 16-Bit Analog Change Event with Time 1 06,07,08 129,130 17
33 0 0 Frozen Analog Event - All Variations
33 1 32-Bit Frozen Analog Event without Time
33 2 16-Bit Frozen Analog Event without Time
33 3 32-Bit Frozen Analog Event with Time
33 4 16-Bit Frozen Analog Event with Time
40 0 Analog Output Status - All Variations
40 1 32-Bit Analog Output Status
40 2 16-Bit Analog Output Status
41 0 Analog Output Block - All Variations
41 1 32-Bit Analog Output Block 3,4,5,6 17,28 129 Request echo
41 2 16-Bit Analog Output Block 3,4,5,6 17,28 129 Request echo
50 0 Time and Date - All Variations
50 1 Time and Date
50 2 Time and Date with Interval
51 0 Time and Date CTO - All Variations
51 1 Time and Date CTO 1, 2 129
51 2 Unsynchronized Time and Date CTO
52 0 Time Delay - All Variations
52 1 Time Delay Coarse
52 2 Time Delay Fine
60 0
60 1 Class 0 Data 1 06,07,08 129
20,21 06
60 2 Class 1 Data 1 06,07,08 129
20,21 06
60 3 Class 2 Data 1 06,07,08 129
20,21 06
REQUEST RESPONSE
OBJECT
Obj Var Description
60 4 Class 3 Data 1 06,07,08 129

70 0 File management – All variations
80 1 Internal Indications 2
81 1 Storage Object
82 1 Device Profile
83 1 Private Registration Object
83 2 Private Registration Object Descriptor
90 1 Application Identifier
100 1 Short Floating Point
100 2 Long Floating Point
100 3 Extended Floating Point
101 1 Small Packed Binary-Coded Decimal
101 2 Medium Packed Binary-Coded Decimal
101 3 Large Packed Binary-Coded Decimal
No Object (Cold Restart)
No Object (Warm Restart)
No Object (Delay Measurement)
“On-line” Quality bit management:

The table below described the management of the DNP3 binary input status object for each
PACiS xPS status, MV and counter value.
This management is the same for data with or without the time tag. You can choose
between two modes. Only the mode 1 is backwards compatible.
MODE 1 / SBMC set to OFF
SPS:
DNP3 binary input status object
Remote Forced
On-line BS1[0]
RestartBS1[1]
Local Forced
State BS1[7]
Chatter filter
Comm.lost
Reserved
PACiS SPS Status

BS1[2]
BS1[3]
BS1[4]
BS1[5]
BS1[6]
SBMC is set to Off
RESET 1 - - - - - - 0
SET 1 - - - - - - 1
TOGGLING 1 - - - - 1 - 0
SELFCHECKFAULT 0 - - - - - - 0
UNKNOWN 1 - 1 - - - - (1)
SUPPRESSED 1 - - 1 - - - X
FORCED 1 - - 1 - - - (2)
SUBSTITUTED 1 - - 1 - - - (2)
DPS:
DNP3 binary input status object DNP3 binary input status object
DNP3 Address (CO) DNP3 Address + 1 (CC)
Local Forced BS1[4]
Local Forced BS1[4]

Chatter filter BS1[5]

Comm.lost BS1[2]
Comm.lost BS1[2]
Reserved BS1[6]
Reserved BS1[6]
Remote Forced
Remote Forced
On-line BS1[0]
On-line BS1[0]
RestartBS1[1]
RestartBS1[1]
State BS1[7]
State BS1[7]
PACiS DPS Status
SCE Inversion = No
BS1[3]
BS1[3]
SBMC is set to Off
OPEN 1 - - - - - - 1 1 - - - - - - 0
CLOSED 1 - 0 1 - - - - - - 1
JAMMED 0 - 0 0 - 1
UNDEFINED 0 - - - 0 0 - 1
TOGGLING 1 - - - - 1 - 0 1 - - - - 1 - 1
SELFCHECKFAULT 0 - - - - - - 0 0 - - - - - - 1
UNKNOWN 1 - 1 - - - - (1) 1 - 1 - - - - (1)
SUPPRESSED 1 - - 1 - - - X 1 - - 1 - - - X
FORCED 1 - - 1 - - - (2) 1 - - 1 - - - (2)
SUBSTITUTED 1 - - 1 - - - (2) 1 - - 1 - - - (2)
(1) For the the status UNKNOWN, the C264 acction for each data source shows in the
table that follows:
Data source Condition C264 action
IEC61850 server Server connection Data shows as transmitted on IEC61850
Server disconnection Resets the data from the server

a T101 IED or a DNP3 IED IED disconnection Resets the bit
a VDEW IED or a Modbus IED IED disconnection Does not change the previous status
(2) Value is given by the client that forces, suppresses or substitutes the data, also
assigns and gives the value to the data.
“-“ stands for 0 except when 0 is significant, in this case the 0 appears in the cell.
“X stands for No change. It means no change from the previous status.
The table that follows shows the management of the DNP3 Object coding status Flag and
current value for each PACiS MV and SPI status. This management is the same for data
with or without the time tag. The SBMC is set to off.
DNP3 object coding status flag
Reference check BS1[6]
Remote Forced BS1[3]
Local Forced BS1[4]
Over-range BS1[5]
Comm.lost BS1[2]
Reserved BS1[7]
On-line BS1[0]
RestartBS1[1]
PACiS MV and SPI Status

DNP3 object coding
SBMC is set to Off
status Current value
VALID 1 - - - - - - - VALUE*
SELFCHECK FAULT 0 - - - - - - - X*
UNKNOWN 1 - 1 - - - - - X*
FORCED 1 - - 1 - - - - VALUE*
SUPPRESSED 1 - - 1 - - - - VALUE*
SUBSTITUTED 1 - - 1 - - - - VALUE*
OVERRANGE (0x6000) 0 - - - - - - - Min or Max or (1)*
UNDEFINED 0 - - - - - - - X*
OPENCIRCUIT 0 - - - - - - - X*
* The value can be scaled and depends to the format: Natural or Adjusted. If the result of
the scaling is not between minimum and maximum as defined in the configuration, then
the MV shows as OVERRANGE
(1) If the scaling value is between minimum and maximum then this value is transmitted
For each PACiS COUNTER status, the table that follows shows the management of the
DNP3 Object coding status Flag and Delta value. This management is the same for data
with or without the time tag. The SBMC is set to off.

Local Forced BS1[4]
Over-range BS1[5]
Comm.lost BS1[2]
Reserved BS1[7]
On-line BS1[0]
RestartBS1[1]
PACiS Counter Status
DNP3 object coding
status Value
VALID 1 - - - - - - - VALUE
SELFCHECK FAULT 0 - - - - - - - X
UNKNOWN 1 - 1 - - - - - X
OVERRANGE 0 - - - - - - - X
UNDEFINED 0 - - - - - - - X
MODE 2 / SBMC set to OFF:

Comm.lost BS1[2]
Reserved BS1[6]
Remote Forced
On-line BS1[0]
RestartBS1[1]
Local Forced
State BS1[7]
Chatter filter
PACiS SPS Status
BS1[3]
BS1[4]
BS1[5]
SBMC is set to Off
RESET 1 - - - - - - 0
SET 1 - - - - - - 1
TOGGLING 1 - - - - 1 - 0
SELFCHECKFAULT 0 - - - - - - 0
UNKNOWN 0 - 1 - - - - (1)
SUPPRESSED 1 - - 1 - - - X
FORCED 1 - - 1 - - - (2)
SUBSTITUTED 1 - - 1 - - - (2)
Local Forced BS1[4]
Local Forced BS1[4]


Comm.lost BS1[2]
Comm.lost BS1[2]
Reserved BS1[6]
Reserved BS1[6]
Remote Forced
Remote Forced
On-line BS1[0]
On-line BS1[0]
PACiS DPS Status

RestartBS1[1]
RestartBS1[1]
State BS1[7]
State BS1[7]
SCE Inversion = No
BS1[3]
BS1[3]
SBMC is set to Off
OPEN 1 - - - - - - 1 1 - - - - - - 0
CLOSED 1 - 0 1 - - - - - - 1
JAMMED 0 - 1 0 - 0
UNDEFINED 0 - - - 1 0 - 0
TOGGLING 1 - - - - 1 - 1 1 - - - - 1 - 0
SELFCHECKFAULT 0 - - - - - - 1 0 - - - - - - 0
UNKNOWN 0 - 1 - - - - (1) 0 - 1 - - - - (1)
SUPPRESSED 1 - - 1 - - - X 1 - - 1 - - - X
FORCED 1 - - 1 - - - (2) 1 - - 1 - - - (2)
SUBSTITUTED 1 - - 1 - - - (2) 1 - - 1 - - - (2)

Local Forced BS1[4]
Over-range BS1[5]
Comm.lost BS1[2]
Reserved BS1[7]
On-line BS1[0]
RestartBS1[1]
PACiS MV and SPI Status
DNP3 object coding
SBMC is set to Off
VALID 1 - - - - - - - VALUE*
SELFCHECK FAULT 0 - 1 - - - - - X*
UNKNOWN 0 - 1 - - - - - X*
FORCED 1 - - 1 - - - - VALUE*
SUPPRESSED 1 - - 1 - - - - VALUE*
SUBSTITUTED 1 - - 1 - - - - VALUE*
OVERRANGE (0x6000) 0 - - - - - - - Min or Max or (1)*
UNDEFINED 0 - - - - - - - X*
OPENCIRCUIT 0 - 1 - - - - - X*
PACiS Counter Status: same as mode 1

MODE 1 = MODE 2 if SBMC is set to ON:
Comm.lost BS1[2]
SBMC is set to On
Reserved BS1[6]
Remote Forced
On-line BS1[0]
RestartBS1[1]
Local Forced
State BS1[7]
Chatter filter
SCE SPS profile
BS1[3]
BS1[4]
BS1[5]
attribute “Value”
equal to
RESET 1 - - - - - - 0
SET 1 - - - - - - 1
SUPPRESSED 1 - - 1 - - - 0
Local Forced BS1[4]
Local Forced BS1[4]

SBMC is set to On
Comm.lost BS1[2]
Comm.lost BS1[2]
Reserved BS1[6]
Reserved BS1[6]
Remote Forced
Remote Forced
On-line BS1[0]
On-line BS1[0]
RestartBS1[1]
RestartBS1[1]
State BS1[7]
State BS1[7]
SCE DPS profile
BS1[3]
BS1[3]
attribute “Value”
equal to
SUPPRESSED 1 - - - 1 - - 0 1 - - - 1 - - 0
OPEN 1 - - - - - - 1 1 - - - - - - 0
CLOSED 1 - - - - - - 0 1 - - - - - - 1
JAMMED 0 - - - - - - 0 0 - - 1 - - - 1

Local Forced BS1[4]
Over-range BS1[5]
Comm.lost BS1[2]
Reserved BS1[7]
SBMC is set to On
On-line BS1[0]
RestartBS1[1]
SCE MV profile attribute

DNP3 object coding
“Value” equal to
Yes to SUPPRESSED 1 - - - 1 - - - 0
4.4 Slave IEC 60870-5-101 profile

The companion standard presents sets of parameters and alternatives from which subsets
have to be selected to implement particular telecontrol systems. Certain parameters values,
such as the number of bytes in the COMMON ADDRESS of ASDUs represent mutually
exclusive alternatives. This means that only one value of the defined parameters is admitted
per system.
Other parameters, such as the listed set of different process information in command and in
monitor direction allow the specification of the complete set or subsets, as appropriate for
given applications. This clause summarizes the parameters of the previous clauses to
facilitate a suitable selection for a specific application. If a system is composed of equipment
stemming from different manufacturers it is necessary that all partners agree on the selected
parameters.
The selected parameters should be marked in the white boxes as follows:
Function or ASDU is not used

⌧ Function or ASDU is used as standardized (default)
R Function or ASDU is used in reverse mode
B Function or ASDU is used in standard and reverse mode

The possible selection (blank, X, R or B) is specified for each specific clause or parameter.
NOTE : In addition, the full specification of a system may require individual
selection of certain parameters for certain parts of the system, such as
the individual selection of scaling factors for individually addressable
measured values.
4.4.1 System or device
(system specific parameter, indicates the definition of a system or a device by marking one
of the following with ‘X’)
System definition
Controling station definition (Master)
⌧ Controlled station definition (Slave)

4.4.2 Network configuration
(network specific parameter, all configurations that are used are to be marked ‘X’)
⌧ Point-to-point ⌧ Multipoint-party line
⌧ Multiple point-to-point ⌧ Multipoint-star

4.4.3 Physical layer

(network specific parameter, all interfaces and data rates that are used are to be marked ‘X’)
Transmission speed (control direction)
Unbalanced interchange
CIRCUIT V24/V28 Balanced interchange
Recommended if Circuit X24/X27
Standard
> 1200 bits/s
100 bits/s ⌧ 2400 bits/s ⌧ 2400 bits/s 56000 bits/s

⌧ 300 bits/s ⌧ 9600 bits/s ⌧ 9600 bits/s

⌧ 1200 bits/s ⌧ 38400 bits/s
Transmission speed (monitor direction)
Circuit V24/V28 Balanced interchange
Standard
> 1200 bits/s

⌧ 1200 bits/s ⌧ 38400 bits/s
4.4.4 Link layer

(network specific parameter, all options that are used are to be marked ‘X’. Specify the
maximum frame length. If a non-standard assignment of class 2 messages is implemented
for unbalanced transmission, indicate the type ID and COT of all messages assigned to
class 2.)
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively
in this companion standard.
Link transmission procedure Address field of the link
⌧ Balanced transmission Not present (balanced transmission only)
⌧ Unbalanced transmission ⌧ One octet
⌧ Two octets
Structured
⌧ Unstructured
Frame length (number of bytes)
255 Maximum length L in control direction
up to 255 Maximum length L in monitor direction – configurable

4.4.5 Application layer

Transmission mode for application data
Mode 1 (Least significant octet first), as defined in clause 4.10 of IEC 870-5-4, is used
exclusively in this companion standard.
Common address of ASDU
(system-specific parameter, all configurations that are used are to be marked ‘X’)
⌧ One octet ⌧ Two octets

Information object address
⌧ One octet ⌧ Structured
⌧ Two octets ⌧ Unstructured
⌧ Three octets
Cause of transmission
⌧ One octet ⌧ Two octets (with originator address)

Selection of standard ASDUs
Process information in monitor direction
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)
⌧ <1> := Single-point information M_SP_NA_1
⌧ <2> := Single-point information with time tag M_SP_TA_1
⌧ <3> := Double-point information M_DP_NA_1
⌧ <4> := Double-point information with time tag M_DP_TA_1
⌧ <5> := Step-position information M_ST_NA_1
⌧ <6> := Step-position information with time tag M_ST_TA_1
<7> := BitString of 32 bit M_BO_NA_1
<8> := BitString of 32 bit with time tag M_BO_TA_1
⌧ <9> := Measured value, normalized value M_ME_NA_1
⌧ <10> := Measured value, normalized value with time tag M_ME_TA_1
⌧ <11> := Measured value, scaled value M_ME_NB_1
⌧ <12> := Measured value, scaled value with time tag M_ME_TB_1
⌧ <13> := Measured value, short floating point value M_ME_NC_1
⌧ <14> := Measured value, short floating point value with time tag M_ME_TC_1
⌧ <15> := Integrated totals M_IT_NA_1
⌧ <16> := Integrated totals with time tag M_IT_TA_1

<17> := Event of protection equipment with time tag M_EP_TA_1
⌧ <18> := Packed start events of protection equipment with time tag M_EP_TB_1
⌧ <19> := Packed output circuit transmission of protection equipment with time tag M_EP_TC_1
<20> := Packed single-point information with status change detection M_PS_NA_1
<21> := Measured value, normalized value without quality descriptor M_ME_ND_1
⌧ <30> := Single-point information with time tag CP56Time2a M_SP_TB_1
⌧ <31> := Double-point information with time tag CP56Time2a M_DP_TB_1
⌧ <32> := Step-position information with time tag CP56Time2a M_ST_TB_1
<33> := Bistring of 32 bits with with time tag CP56Time2a M_BO_TB_1
⌧ <34> := Measured value, normalized with time tag CP56Time2a M_ME_TD_1
⌧ <35> := Measured value, scaled with time tag CP56Time2a M_ME_TE_1
⌧ <36> := Measured value, short floating point number with time tag CP56Time2a M_ME_TF_1
⌧ <37> := Integrated totals with time tag CP56Time2a M_IT_TB_1
<38> := Event of protection equipment with time tag CP56Time2a M_EP_TD_1
⌧ <39> := Packed start events of protection equipment with time tag CP56Time2a M_EP_TE_1
⌧ <40> := Packed output circuit information of protection equipment with time tag CP56Time2a M_EP_TF_1
Process information in control direction

⌧ <45> := Single command C_SC_NA_1
⌧ <46> := Double command C_DC_NA_1
⌧ <47> := Regulating step command C_RC_NA_1
⌧ <48> := Set point command, normalized value C_SE_NA_1
⌧ <49> := Set point command, scaled value C_SE_NB_1
⌧ <50> := Set point command, short floating point value C_SE_NC_1
<51> := BitString of 32 bits C_BO_NA_1
System information in monitor direction

⌧ <70> := End of initialisation M_EI_NA_1

System information in control direction

⌧ <100> := Interrogation command C_IC_NA_1
⌧ <101> := Counter Interrogation Command C_CI_NA_1
<102> := Read command C_RD_NA_1
⌧ <103> := Clock synchronisation command C_CS_NA_1
⌧ <104> := Test command C_TS_NB_1
<105> := Reset process command C_RP_NC_1
⌧ <106> := Delay acquisition command C_CD_NA_1
Parameter in control direction

<110> := Parameter of measured value, normalized value P_ME_NA_1
<111> := Parameter of measured value, scaled value P_ME_NB_1
<112> := Parameter of measured value, short floating point value P_ME_NC_1
<113> := Parameter activation P_AC_NA_1
File transfer
⌧ <120> := File ready F_FR_NA_1
⌧ <121> := Section ready F_SR_NA_1
⌧ <122> := Call directory, select file, call file, call section F_SC_NA_1
⌧ <123> := Last section, last segment F_LS_NA_1
⌧ <124> := Ack file, ack section F_AF_NA_1
⌧ <125> := Segment F_SG_NA_1
⌧ <126> := Directory F_DR_TA_1
Special use (private range)

⌧ <136> := Database version M_DB_NA_1
⌧ <137> := Regulating delay command C_RC_NB_1

Type identifier and cause of transmission assignments

(station-specific parameters)
Shaded boxes are not required.
Blank = function or ASDU is not used
Mark type identification/cause of transmission combinations:
‘X’ if used only in the standard direction
‘R’ if used only in the reverse direction
‘B’ if used in both directions
Type ID Cause of transmission

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 thru thru 44 45 46 47
36 41
<1> M_SP_NA_1 X X X X
<2> M_SP_TA_1 X X
<3> M_DP_NA_1 X X X X
<4> M_DP_TA_1 X X
<5> M_ST_NA_1 X X X X
<6> M_ST_TA_1 X X
<7> M_BO_NA_1
<8> M_BO_TA_1
<9> M_ME_NA_1 X X X X
<10> M_ME_TA_1 X
<11> M_ME_NB_1 X X X X
<12> M_ME_TB_1 X
<13> M_ME_NC_1 X X X X
<14> M_ME_TC_1 X
<15> M_IT_NA_1 X X
<16> M_IT_TA_1 X X
<17> M_EP_TA_1
<18> M_EP_TB_1 X
<19> M_EP_TC_1 X
<20> M_PS_NA_1
<21> M_ME_ND_1
<30> M_SP_TB_1 X X X
<31> M_DP_TB_1 X X X
<32> M_ST_TB_1 X X X
<33> M_BO_TB_1
<34> M_ME_TD_1 X
<35> M_ME_TE_1 X
<36> M_ME_TF_1 X
<37> M_IT_TB_1 X X
<38> M_EP_TD_1
<39> M_EP_TE_1 X
<40> M_EP_TF_1 X
<45> C_SC_NA_1 X X X X X X X X
<46> C_DC_NA_1 X X X X X X X X

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 thru thru 44 45 46 47
36 41
<47> C_RC_NA_1 X X X X X X X X
<48> C_SE_NA_1 X X X X X X X X
<49> C_SE_NB_1 X X X X X X X X
<50> C_SE_NC_1 X X X X X X X X
<51> C_BO_NA_1 X
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X X X X X X
<101> C_CI_NA_1 X X X X X X
<102> C_RD_NA_1 X
<103> C_CS_NA_1 X X X X X
<104> C_TS_NA_1 X X X X X
<105> C_RP_NA_1 X
<106> C_CD_NA_1 X X X
<110> P_ME_NA_1 X
<111> P_ME_NB_1 X
<112> P_ME_NC_1 X
<113> P_AC_NA_1 X
<120> F_FR_NA_1 X X X X
<121> F_SR_NA_1 X X X X
<122> F_SC_NA_1 X X X X
<123> F_LS_NA_1 X X X X
<124> F_AF_NA_1 X X X X
<125> F_SG_NA_1 X X X X
<126> F_DR_TA_1 X X
<136> M_DB_NA_1 X
<137> C_RC_NB_1 X X X X X X X X
4.4.6 Basic application functions

Station initialisation
(station-specific parameter, mark ‘X’ if function is used)
Remote initialisation
Cyclic data transmission
⌧ Cyclic data transmission

Read procedure
Read procedure
Spontaneous transmission
⌧ Spontaneous transmission
Link state between Controlling and Controlled Station
⌧ Management of the COM lost (Problem detecting on the link)
⌧ Management of the COM recovering (Problem not detecting on the link)

General interrogation
⌧ global
⌧ group 1 ⌧ group 7 ⌧ group 13
⌧ group 5 ⌧ group 11 Addresses per group have to be defined
⌧ group 6 ⌧ group 12
Counter General interrogation
⌧ global
⌧ group 4
Clock synchronisation
⌧ Clock synchronisation
Notes: – The controlled station does not report the change of hour by
sending a clock synchronisation message (ASDU 103) to the
controlling station.
– When the controlling station send to controlled station a clock
synchronisation and if the system (includes controlled station), isn’t
synchronized by an other source : the clock synchronisation
response is positive.
– When the controlling station send to controlled station a clock
synchronisation and if the system (includes controlled station), is
synchronized by an other source : the clock synchronisation
response is negative.
Command transmission
(object -specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
⌧ Direct command transmission
⌧ Direct set-point command transmission
⌧ Select and execute command
⌧ Select and execute set-point command
⌧ C_SE ACTTERM used
⌧ No additional definition
Short pulse duration (duration determined by a system parameter in the outstation)
Long pulse duration (duration determined by a system parameter in the outstation)
Persistent output
Transmission of integrated totals
⌧ Mode A: local freeze with spontaneous transmission
Mode B: local freeze with counter interrogation
⌧ Mode C: freeze and transmit by counter interrogation commands
Mode D: freeze by counter interrogation command, frozen values reported

spontaneously
⌧ Counter read ⌧ General request counter
⌧ Counter freeze without reset ⌧ Request counter group 1
⌧ Counter freeze with reset ⌧ Request counter group 2
⌧ Counter reset ⌧ Request counter group 3
⌧ Request counter group 4

Parameter loading
(object-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
Threshold value
Smoothing factor
Low limit for transmission of measured value
High limit for transmission of measured value

Parameter activation
Act/deact of persistent cyclic or periodic transmission of the addressed object

Test procedure
⌧ Test procedure
File transfer
(station-specific parameter), mark ‘X’ if function is used)
File transfert in monitor direction
⌧ Transparent file
Transmission of disturbance data of protection equipment
⌧ Transmission of sequences of events
Transmission of sequences of recorded analogue values

File transfer in control direction
Transparent file
Background scan
⌧ Background scan
Acquisition of transmission delay

Management events priorities
Digitals Inputs and Analogs Inputs, management events priorities.

See T101 standard Amendment 2 §7.2.2.2
4.4.7 Protocol Requirements

Class 1 data
The following types of information must be configured at the controlled station to be Class 1:
The following types of information are to be configured at the controlled station to be Class 1:
Single point information with or without time tag (on change)

Double point information with or without time tag (on change)
Step position information with or without time tag (on change)
Measured value, normalised with or without time tag (on change)
Measured value, scaled with or without time tag (on change)
Measured value, floated with or without time tag (on change)
Integrated totals with or without time tag (on change)
Time messages
All command responses (ACT_CONF, and ACT_TERM)
Class 2 data
The following types of information must be configured at the controlled station to be Class 2:
Single point information (GI scan, or BackGroundScan cycle)

Double point information (GI scan, or BackGroundScan cycle)
Measured values, normalised (GI scan, or Periodic cycle, or BackGroundScan cycle)
Measured values, scaled (GI scan, or Periodic cycle, or BackGroundScan cycle)
Measured values, floated (GI scan, or Periodic cycle, or BackGroundScan cycle)
Step position values (GI scan, or BackGroundScan cycle)
Integrated totals (Counter GI scan)
4.4.8 Application Functions

The following IEC-60870-5-5 standard application processes are required to be supported.
Station Initialisation
Station initialisation consists of a reset of the communications link, followed by a general
interrogation of the controlled station. Once this initialisation sequence performed the
controlling station can start the polling for data report.
Communications failure
Communications to the controlled station must be re-initialised by the controlling station
when the frame repeat process has completed without successfully transmitting the frame (ie
the frame time-out period times the number of repeats).
If the controlled station fails to communicate with the controlling station then the controlling
station should perform a communications system initialisation for that controlled station.
Controlled station failure
The controlled station shall indicate to the controlling station that it has initialised by sending
a frame indicating End of Initialisation with a Cause of Initialisation (COI) field, which will
identify the reason for the initialisation in unbalanced mode only)
Data Acquisition by Polling

The default for all analogue values shall be reporting as Class 2 data (COT=1,
periodic/cyclic, or COT = 2, BackgroundScan cyclic).
Values returned as Class 2 data do not have a time tag (since they are constantly repeated).
The controlled station may return Class 1 data in response to a Class 2 request if no Class 2
data is available and Class 1 data is awaiting transmission.
At the controlled station, if a request for Class 2 data is received and no data is available a
negative response, data not available, shall be returned to the controlling Station. The
negative response may be a fixed length frame (FC=9), which in this case is treated as a
NACK.
Normal Acquisition of Events
The default for all status changes are reported as Class 1 data (COT=3, spontaneous).
Values returned as Class 1 data shall have a time tag (either CP24Time2a, or CP56Time2a).
Status changes at the controlled station shall cause the ACD bit to be set in the next Class 1
or Class 2 data response. The controlling station shall respond to ACD set by inserting a
scan for Class 1 (spontaneous) data as the next scan.
The response to a Class 1 data request shall also have the ACD bit set if more Class 1 data
is awaiting transmission. In this case a further scan for Class 1 data shall be scheduled by
the controlling station.
Abnormal Acquisition of Events
At the controlled station, if a request for Class 1 data is received and no data is available an
error should be raised and a negative response, data not available, returned to the
controlling Station. The negative response shall be a fixed length frame (FC=9), which in
this case is treated as a NACK.
At the controlling station, if a response to a scan for Class 1 data indicates no data is
available an error shall be raised and scanning returned to Class 2 data requests.
General Interrogation
The GI returns the current status information directly from the Computer database.
Time tags are not used for data items returned as part of the GI response.
The GI groups are supported so, these will be set up in the Computer configuration and each
of the (up to 16) groups shall be requested/reported individually.
The System (including the controlled station) may have different synchronisation sources
(IRIG-B, SCADA).
When the controlling station send to controlled station a clock synchronisation and if the
system isn’t synchronized by another source: the clock synchronisation response is positive.
system is synchronized by an other source: the clock synchronisation response is negative.
All Class 1 data are time-tagged with:
Either the 3 bytes time-stamp (CP24Time2a), giving minutes and milliseconds within the
hour, or the 7 bytes time-stamp (CP56Time2a), giving minutes, milliseconds, hours, day,
month and year according to the Computer configuration.
The invalid bit in the time-stamp is set when the computer is not synchronised.
All control commands shall be Select before Execute, or Direct Execute.
For only the control commands: Activation termination is returned to the controlling station to
signal the end of a control sequence.
The QU field of the Qualifier of Command shall be set to zero (0), no additional definition.
Test procedure
A test command may be issued by the controlling station to ensure the availability of the
communications link and the commands subsystem.
Test commands are received at the controlled station on the active link. The controlled
station mirrors the test command, on the link from which it was received, with a cause of
transmission indicating activation confirmation.
An error response should be sent if the command is incorrect, with a cause of transmission
indicating negative activation confirmation.
4.5 Slave IEC 60870-5-104 Server profile

This companion standard presents sets of parameters and alternatives from which subsets
have to be selected to implement particular telecontrol systems. Certain parameter values,
such as the choice of “structured” or “unstructured” fields of the INFORMATION OBJECT
ADDRESS of ASDU represent mutually exclusive alternatives. This means that only one value
of the defined parameters is admitted per system. Other parameters, such as the listed set of
different process information in command and in monitor direction allow the specification of
the complete set or subsets, as appropriate for given applications. This clause summarises
the parameters of the previous clauses to facilitate a suitable selection for a specific
application. If a system is composed of equipment stemming from different manufacturers it
is necessary that all partners agree on the selected parameters.
Paragraph in grey are those which are not applicable for the IEC 60870-5-104 profile.
The selected parameters should be filled up ( ).
NOTE: In addition, the full specification of a system may require individual selection of
certain parameters for certain parts of the system, such as the individual selection
of scaling factors for individually addressable measured values.
To simplify the PID , we use the following conventions:
Not supported
Supported
4.5.1 System or device
System definition
Controlling station definition (Master)
Controlled station definition (Slave)
4.5.2 Network configuration (Network-specific parameter)
Point-to-point Multipoint-party line
Multiple point-to-point Multipoint-star
4.5.3 Physical layer (Network-specific parameter)

Transmission speed (control direction):
Unbalanced interchange Unbalanced interchange Balanced interchange

circuit V.24/V.28 circuit V.24/V.28 circuit X.24/X.27, V35
Standard Recommended if >1 200 bit/s
100 bit/s 2 400 bit/s 2 400 bit/s
200 bit/s 4 800 bit/s 4 800 bit/s
300 bit/s 9 600 bit/s 9 600 bit/s
600 bit/s 19 200 bit/s 19 200 bit/s
1 200 bit/s 38 400 bit/s
56 000 bit/s
64 000 bit/s
Transmission speed (monitor direction):
Unbalanced interchange Unbalanced interchange Balanced interchange

circuit V.24/V.28 circuit V.24/V.28 circuit X.24/X.27, V35
Standard Recommended if >1 200 bit/s
100 bit/s 2 400 bit/s 2 400 bit/s
200 bit/s 4 800 bit/s 4 800 bit/s
300 bit/s 9 600 bit/s 9 600 bit/s
600 bit/s 19 200 bit/s 19 200 bit/s
1 200 bit/s 38 400 bit/s
56 000 bit/s
64 000 bit/s
4.5.4 Link layer (Network specific parameter)

(Network-specific parameter, all options that are used should be filled up ( ). Specify
the maximum frame length. If a non-standard assignment of class 2 messages is
implemented for unbalanced transmission, indicate the type ID and COT of all messages
assigned to class 2.)

Balanced transmission Not present (balanced transmission
only)
Unbalanced transmission One octet
Two octets
Structured
Unstructured
Frame length
_255_ Maximum length L (number of bytes)
When using an unbalanced link layer, the following ASDU types are returned in class 2
messages (low priority) with the indicated causes of transmission:
The standard assignment of ASDUs to class 2 messages is used as follows:
Type Identification Cause of transmission

9,11,13,21 <1>
A special assignment of ASDUs to class 2 messages is used as follows :
Type Identification Cause of transmission

1,3,5 <20> to <41>
NOTE : In response to a class 2 poll, a controlled station prevent the controlling station with
ACD parameter, when there is no class 2 data available.
4.5.5 Protocol Requirements
4.5.5.1 Event
The following types of information are to be configured at the controlled station to be Event:
Single point information with or without time tag (on change)

Double point information with or without time tag (on change)
Measured value, normalised with or without time tag (on change)
Measured value, scaled with or without time tag (on change)
Measured value, floated with or without time tag (on change)
Integrated totals with or without time tag (on change)
4.5.5.2 Static
The following types of information are to be configured at the controlled station to be Static:
Single point information (GI scan, or BackGroundScan cycle)

Double point information (GI scan, or BackGroundScan cycle)
Measured values, normalised (GI scan, or Periodic cycle, or BackGroundScan cycle)
Measured values, scaled (GI scan, or Periodic cycle, or BackGroundScan cycle)
Measured values, floated (GI scan, or Periodic cycle, or BackGroundScan cycle)
Step position values (GI scan, or BackGroundScan cycle)
Integrated totals (Counter GI scan)
4.5.6 Application layer

(System specific parameter)
The address field of the link and the common address of ASDU could have a different
number of bytes
One octet Two octets

(System specific parameter)
One octet Structured

Two octets Unstructured
Three octets
(System-specific parameter)
One octet Two octets (with originator address)
Length of APDU
(System-specific parameter)
The maximum length of APDU is 253 (default). The maximum length may be reduced by the
system.
Configurable Maximum length of APDU per system

(Station-specific parameter)
<1>: = Single-point information M-SP-NA-1

<2>: = Single-point information with time tag M-SP-TA-1
<3>: = Double-point information M-DP-NA-1
<4>: = Double-point information with time tag M-DP-TA-1
<5>: = Step position information M-ST-NA-1
<6>: = Step position information with time tag M-ST-TA-1
<7>: = Bit-string of 32 bit M-BO-NA-1
<8>: = Bit-string of 32 bit with time tag M-BO-TA-1
<9>: = Measured value, normalised value M-ME-NA-1
<10>: = Measured value, normalised value with time tag M-ME-TA-1
<11>: = Measured value, scaled value M-ME-NB-1
<12>: = Measured value, scaled value with time tag M-ME-TB-1
<13>: = Measured value, short floating point value M-ME-NC-1
<14>: = Measured value, short floating point value with time tag M-ME-TC-1
<15>: = Integrated totals M-IT-NA-1
<16>: = Integrated totals with time tag M-IT-TA-1
<17>: = Event of protection equipment with time tag M-EP-TA-1
<18>: = Packed starts events of protection equipment with time tag M-EP-TB-1
<19>: = Packed output circuit information of protection equipment M-EP-TC-1
with time tag
<20>: = Packed single-point information with status change detection M-PS-NA-1
<21>: = Measured value, normalised value without quality M-ME-ND-1
descriptor
Process information in monitor direction with the Extension of time tag

<30>: = Single-point information with time tag CP56Time2a M-SP-TB-1

<31>: = Double-point information with time tag CP56Time2a M-DP-TB-1
<32>: = Step position information with time tag CP56Time2a M-ST-TB-1
<33>: = Bit-string of 32 bit with time tag CP56Time2a M-BO-TB-1
<34>: = Measured value, normalised value with time tag M-ME-TD-1
CP56Time2a
<35>: = Measured value, scaled value with time tag CP56Time2a M-ME-TE-1
<36>: = Measured value, short floating point value, time tag CP56Time2a M-ME-TF-1
<37>: = Integrated totals with time tag CP56Time2a M-IT-TB-1
<38>: = Event of protection equipment with time tag CP56Time2a M-EP-TD-1
<39>: = Packed start event of protection equipment, time tag M-EP-TE-1
CP56Time2a
<40>: = Packed output circuit information of protection equipment M-EP-TF-1
with time tag CP56Time2a

(station specific parameter)
<45>: = Single command C-SC-NA-1

<46>: = Double command C-DC-NA-1
<47>: = Regulating step command C-RC-NA-1
<48>: = Set point command normalised value C-SE-NA-1
<49>: = Set point command scaled value C-SE-NB-1
<50>: = Set point command, short floating point value C-SE-NC-1
<51>: = Bit-string of 32 bit C-BO-NA-1
<58>: = Single command with time tag CP56Time2a C_SC_TA_1
<59>: = Double command with time tag CP56Time2a C_DC_TA_1
<60>: = Regulating step command with time tag CP56Time2a C_RC_TA_1
<61>: = Set point command normalized value with time tag CP56Time2a C_SE_TA_1
<62>: = Set point command scaled value with time tag C_SE_TB_1
CP56Time2a
<63>: = Set point command short floating point value with time tag C_SE_TC_1
CP56Time2a
<64>: = Bitstring of 32 bits with time tag CP56Time2a C_BO_TA_1
NOTE : Time tag command (ASDU 58 to 63) are managed as standard

command (ASDU 45 to 50), i.e. the time tag is not used.

<70>: = End of initialisation M-EI-NA-1


(station-specific parameter)
<100>: = Interrogation commands C-IC-NA-1

<101>: = Counter interrogation command C-CI-NA-1
<102>: = Read command C-RD-NA-1
<103>: = Clock synchronisation command C-CS-NA-1
<104>: = Test command C-TS-NA-1
<105>: = Reset process command C-RP-NA-1
<106>: = Delay acquisition command C-CD-NA-1
<107>: = Test command with time tag CP56time2a C-TS-TA-1

<110>: = Parameter of measured value, normalised value P-ME-NA-1

<111>: = Parameter of measured value, scaled value P-ME-NB-1
<112>: = Parameter of measured value, short floating point value P-ME-NC-1
<113>: = Parameter activation P-AC-NA-1
File transfer
<120>: = File ready F-FR-NA-1

<121>: = Section ready F-SR-NA-1
<122>: = Call directory, select file, call file, call section F-SC-NA-1
<123>: = Last section, last segment F-LS-NA-1
<124>: = Ack file, ack section F-AF-NA-1
<125>: = Segment F-SG-NA-1
<126>: = Directory F-DR-TA-1
File transfer is only implemented in computer gateway.

Special use
(private range)
<136>: = Data base version M-DB-NA-1

<137>: = Regulating delay command C-RC-NB-1
<138>: = Regulating delay command with time tag CP56Time2a C-RC-TB-1

(station specific parameters)
X Mark type identification/cause of transmission combinations: ‘X’ if used

Shaded boxes are not required
. Required in 1995 standard, suppressed in 2000.

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41
<1> M_SP_NA_1 X X X X X
<2> M_SP_TA_1
<3> M_DP_NA_1 X X X X X
<4> M_DP_TA_1 .
<5> M_ST_NA_1 X X X X X
<6> M_ST_TA_1 .
<7> M_BO_NA_1
<8> M_BO_TA_1
<10> M_ME_TA_1
<12> M_ME_TB_1
<14> M_ME_TC_1
<15> M_IT_NA_1 X X
<16> M_IT_TA_1
<17> M_EP_TA_1
<18> M_EP_TB_1
<19> M_EP_TC_1
<20> M_PS_NA_1
<21> M_ME_ND_1
<30> M_SP_TB_1 X X X
<31> M_DP_TB_1 X X X
<32> M_ST_TB_1 X X X
<33> M_BO_TB_1
<34> M_ME_TD_1 X
<35> M_ME_TE_1 X
<36> M_ME_TF_1 X
<37> M_IT_TB_1 X X
<38> M_EP_TD_1
<39> M_EP_TE_1 X
<40> M_EP_TF_1 X
<45> C_SC_NA_1 X X X X X X X X
<46> C_DC_NA_1 X X X X X X X X
<47> C_RC_NA_1 X X X X X X X X
<48> C_SE_NA_1 X X X X X X X X
<49> C_SE_NB_1 X X X X X X X X
<50> C_SE_NC_1 X X X X X X X X
<51> C_BO_NA_1

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41
<58> C_SC_TA_1 X X X X X X X X
<59> C_DC_TA_1 X X X X X X X X
<60> C_RC_TA_1 X X X X X X X X
<61> C_SE_TA_1 X X X X X X X X
<62> C_SE_TB_1 X X X X X X X X
<63> C_SE_TC_1 X X X X X X X X
<64> C_BO_TA_1
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X X X X X X
<101> C_CI_NA_1 X X X X X X
<102> C_RD_NA_1
<103> C_CS_NA_1 X X X X X
<104> C_TS_NA_1
<105> C_RP_NA_1
<106> C_CD_NA_1
<107> C_TS_TA_1 X X X
<110> P_ME_NA_1
<111> P_ME_NB_1
<112> P_ME_NC_1
<113> P_AC_NA_1
<120> F_FR_NA_1 X X
<121> F_SR_NA_1 X X
<122> F_SC_NA_1 X X X
<123> F_LS_NA_1 X X
<124> F_AF_NA_1 X X
<125> F_SG_NA_1 X X
<126> F_DR_TA_1 X X
<136> M_DB_NA_1
<137> C_RC_NB_1 X X X X X X X X
<138> C_RC_TB_1 X X X X X X X X
• COT <45> := Unknown Cause of Transmission

4.5.7 Basic application functions

(Station specific parameter)
(Between Reset User ASDU’s).

(It’s the same cyclic for all data).

Read procedure
Read procedure
Double transmission of information objects with cause of transmission spontaneous

(station specific parameter), each information is marked where both a Type ID without time
and corresponding Type ID with time are issued in response to a single spontaneous change
of a monitored object
The following type identifications may be transmitted in succession caused by a single status
change of an information object. The particular information object addresses for which
double transmission is enabled are defined in a project-specific list.
Single point information M_SP_NA_1, M_SP_TA_1, M_SP_TB_1 and

M_PS_NA_1
Double point information M_DP_NA_1, M_DP_TA_1 and M_DP_TB_1
Step position information M_ST_NA_1, M_ST_TA_1 and M_ST_TB_1
Bitstring of 32 bit M_BO_NA_1, M_BO_TA_1 and M_BO_TB_1
(if defined for a specific project)
Measured value, normalized value M_ME_NA_1, M_ME_TA_1, M_ME_ND_1 and
M_ME_TD_1
Measured value, scaled value M_ME_NB_1, M_ME_TB_1 and M_ME_TE_1
Measured value, short floating M_ME_NC_1, M_ME_TC_1 and M_ME_TF_1
point number
(System or station-specific parameter)
Global
Group 1 Group 7 Group 13
Group 5 Group 11
Group 6 Group 12 Information Object Addresses
assigned to each group must be
shown in a separate table

(System or station specific parameter)
Global
Group 1 Group 3
Group 2 Group 4
(Object specific parameter)
Direct command transmission Select and execute command

Direct set point command transmission Select and execute set point
command
C-SE ACTTERM used
No additional definition
Persistent output

(Station or object-specific parameter)
Mode A: local freeze with spontaneous.

Mode B: local freeze with counter.
Mode C: freeze and transmit by counter interrogation.
Mode D: freeze by counter interrogation command, frozen values reported.
Counter read General request counter

Counter freeze without reset Request counter group 1
Counter freeze with reset Request counter group 2
Counter reset Request counter group 3
Request counter group 4
Parameter loading
(Object-specific parameter)
Threshold value
Smoothing factor
(Object-specific parameter)
Act/Desactivation of persistent cyclic or periodic transmission of the addressed

object
Test procedure
Test procedure
File transfer
File transfer in monitor direction
Transparent file
Transmission of disturbance data of protection equipment
Transmission of sequences of events
Only in computer gateway

Transparent file
Background scan
Background scan

μ Acquisition of transmission delay

Digital Inputs, Step-position, Analogues Inputs and Integrated Totals, management

events priorities.
Definition of time outs
Parameter Default Remarks Selected

value value
t0 30s Time out of connection establishment configurable
t1 15s Time out of send or test APDUs configurable
t2 10s Time out for acknowledges in case of no configurable
data messages t2 < t1
t3 20s Time out for sending test frames in case configurable
of a long idle state
Maximum range of values for all time outs: 1 to 255 s, accuracy 1 s

Maximum number of outstanding I format APDUs k and latest acknowledge
Parameter Default Remarks Selected

value value
K 12 APDUs Maximum difference receive sequence configurable
number to send state variable
W 8 APDUs Latest acknowledge after receiving w I- configurable
format APDUs
Maximum range of values k: 1 to 255 APDUs, accuracy 1 APDU

Maximum range of values w: 1 to 255 APDUs, accuracy 1 APDU (Recommendation: w
should not exceed 2/3 of k).
Portnumber
Parameter Value Remarks

Portnumber 2404 In all cases, but configurable in Registry (only for Gateway
PC)
RFC 2200 suite

RFC 2200 is an official Internet Standard which describes the state of standardization of
protocols used in the Internet as determined by the Internet Architecture Board (IAB). It
offers a broad spectrum of actual standards used in the Internet. The suitable selection of
documents from RFC 2200 defined in this standard for given projects has to be chosen by
the user of this standard.
Ethernet 802.3
Serial X.21 interface
Other selection from RFC 2200
4.6 Slave Modbus (MODICON) profile

The purpose of this chapter is to describe the support of the MODBUS RTU protocol in the
PACiS system.
The MODBUS RTU protocol defines a message structure that controllers will recognise and
use. It describes the process a controller uses to request access to another device, how it
will respond to requests from other devices, and how errors will be detected.
4.6.1 Introducing MODBUS
Controllers communicate using a master-slave scheme, in which only the master (called
SCADA) can initiate requests. The MODBUS gateway is a slave device that responds by
supplying the requested data to the master.
Transmission mode used is the MODBUS RTU. Queries and replies have the same format
on a master-slave query-response cycle:
Query message from Server Response message from Slave

Function code Function code
Eight-bit Data bytes Eight-bit data bytes
Error check Error check
4.6.1.1 Device address field

The device address field of a message frame contains eight bits. Valid slave device
addresses in queries are in the range 0 – 247, but individual slave devices are assigned
addresses in the range 1- 247 and address 0 is reserved for broadcast operations.
The device address field of a message frame always identifies a slave (slave destination in
master to slave queries and slave source in slave to master responses).
If the gateway receives a frame with a broadcast device address, no reply is returned.
If the gateway receives a frame with a not expected device address, no reply is returned.
4.6.1.2 Function code field
The function code field of a message frame contains eight bits. Valid codes are in the range
1-255.
In master to slave queries, the function code identifies the operation that is to be executed by
the slave.
In slave to master responses, the function code is used to indicate either a normal (error-
free) response or a failure of the operation execution (called an exception response). For a
normal response, the slave simply echoes the original function code. For an exception
response, the slave returns a code that is equivalent to the original function code with its
MSB set to 1. In addition to the modification of the function code the slave places a unique
code into the data field of the response message, which identifies the reason for the
exception.
4.6.1.3 Data field
The data field of a message frame is constructed using sets of two hexadecimal digits, in the
range 00h to FFh.
In master to slave queries, the data field contains additional information to be used by the
slave to execute the operation defined by the function code.
In slave to master responses, the data field contains the data requested by the master.
The data field can be non-existent in some kind of messages.
4.6.1.4 Error check field

The error-checking field contains a 16-bit value implemented as two 8-bit bytes [low
significant byte first]. The error check value is the result of a Cyclical Redundancy Check
[CRC] calculation performed on the message contents.
The gateway does not reply to corrupted data messages, i.e when the CRC is not correct or
when parity is not correct.
4.6.2 Slave responses

4.6.2.1 When the slave answers
Except for broadcast messages (no response in this case), when a master device sends a
query to a slave device it expects a normal response.
One of four possible events can occur from the master’s query :
• If the slave device receives the query without communication error, and can handle
the query normally, it returns a normal response.
• If the slave does not receive the query due to a communication error, no response is
returned. The master program will process a timeout condition for query.
• If the slave receives the query, but detect a communication error [ bad CRC or framing
error for example ], no response is returned. The master program will process a
timeout condition for query.
• If the slave device receives the query without communication error, but cannot handle
it, the salve will return an exception response informing the master of the nature of the
error.
4.6.2.2 Exception Responses Codes
The exception code is sent as an 8-bit data, the range of valid codes is 1-8 in the protocol.
Supported exception responses codes are :
Code Name Meaning

01 ILLEGAL The function code received in the query is not an allowable
FUNCTION action for the slave.
An illegal function will be send in the main following cases :
An unsupported request [ see after, the table with the
functions supported ]
An unsupported sub-function code for Diagnostic request
02 ILLEGAL DATA The data address received in the query is not an allowable
ADDRESS address for the slave.
An illegal data address will be send in the main following
cases:
A read coil / input status starting to a none existent point in
configuration
A read holding registers / input registers starting to a none
existent point in configuration
A force coil / multiple coils request starting on an non-
configured address.
A preset single / multiple register(s) on an non-configured
point
Code Name Meaning

03 ILLEGAL DATA A value contained in the query data field is not an allowable
VALUE value for the slave.
An illegal data value exception will be send in the main
following cases :
An illegal value received in force coils request (so value
different from FF00h and 0000h)
Illegal count value for multiple preset registers
04 SLAVE DEVICE Not used in the gateway
FAILURE
05 ACKNOWLEDGE Not used in the gateway
06 SLAVE DEVICE Not used in the gateway
BUSY
07 NEGATIVE The slave cannot perform the program function received in
ACKNOWLEDGE the query.
A negative acknowledge will be send in the main following
cases :
Some errors in the frame
A read coil / input status on more than 2000 points
Force coil refused if command is incorrect or cannot be
executed (equipment absent, invalid, in local, …)
08 MEMORY PARITY Not used in the gateway
ERROR
4.6.3 Serial transmission mode

When messages are transmitted on standard MODBUS serial networks, each byte is sent
LSB first.
The format for each byte in MODBUS RTU mode is:
• Coding system: 8-bit binary, hexadecimal 0-9, A-F

Two hexadecimal characters contained in each 8-bit field of
the message
• Bits per Byte: 1 start bit8 data bits,

LSB sent first2 stop bits if no parity, or 1 parity bit and 1 stop
bit)
• Error Check Field: Cyclical Redundancy Check (CRC-16)

4.6.4 MODBUS Functions

MODBUS defines 24 functions, valid codes are in the range of 1-24.
4.6.4.1 Supported functions
Code Function name Supported

01 READ COIL STATUS [ identical to function code 02 ] YES
02 READ INPUT STATUS [ identical to function code 01 ] YES
03 READ HOLDING REGISTERS [ identical to function code 04 ] YES
04 READ INPUT REGISTERS [ identical to function code 03 ] YES
05 FORCE SINGLE COIL YES
06 PRESET SINGLE REGISTER YES
07 READ EXCEPTION STATUS YES
08 DIAGNOSTICS [ only sub function 0 is supported ] YES
09 PROGRAM 484 NO
10 POLL 484 NO
11 FETCH COMM. EVENT CTR. NO
12 FETCH COMM. EVENT LOG NO
13 PROGRAM CONTROLLER NO
14 POLL CONTROLLER NO
15 FORCE MULTIPLE COILS [ identical to function code 05, one point only ] YES
16 PRESET MULTIPLE REGISTERS [ identical to function code 06, one YES
point only ]
17 REPORT SLAVE ID NO
18 PROGRAM 884/M84 NO
19 RESET COMM. LINK NO
20 READ GENERAL REFERENCE NO
21 WRITE GENERAL REFERENCE NO
22 MASK WRITE 4X REGISTER NO
23 READ/WRITE 4X REGISTERS NO
24 READ FIFO QUEUE NO
4.6.4.2 General format of MODBUS functions

A query message typically contains some of the following 8-bit fields:
Starting Address Hi
Starting Address Lo
No. of Registers / Points Hi
No. of Registers / Points Lo
Force / Preset Data Hi
Force / Preset Data Lo
A response message typically contains some of the following fields:

Byte Count *
Data
Data Hi
Data Lo
No. of Registers / Points Hi
No. of Registers / Points Lo
Force / Preset Data Hi
Force / Preset Data Lo
(*) Byte Count Field :A Byte Count Field is used in slave responses to indicate the number of
8-bit bytes in the Data field; the value is exclusive of all other field contents, including the
Byte Count field.
4.6.4.3 MODBUS Data Addresses
Point addresses in the data field are 16-bit values in the range 0 – 65535 for each item type.
That’s means that you can have a coil item configured at address 100 for example, and a
holding register item configured at address 100 too.
Starting addresses in queries from SCADA may begin from address 0.
Example : request to read the 16 first coils on device 17.
Slave address 11
Function 01
Starting Address HI 00
Starting address LO 00
Number of points HI 00
Number of points LO 10
CRC XX
4.6.5 Function 01 / 02 : Read Coil Status – Read Input Status
The request function 01 or 02 reads the ON / OFF status of digital inputs in the slave. These
status may be any digital points (physical, automations, system information, grouping, …).
These two functions are the only way to read digital points with the MODBUS protocol.
Sequence of events, digital flags (validity, topical, ..) are not supported.
This is equal using the Read Coil Status request or the Read Input Status request.
Broadcast is not supported.
Addresses in frames may start from 0…65535.
Query :
Slave Function Code Starting Starting No. of No. of CRC CRC

Address Address Address
= 01 Points (H) Points (L) (H)
(H) (L) (L)
The query message specifies the starting coil address and the quantity of coils to be read.
Response :
Slave Function Byte Count Data Byte Data Byte Data Byte CRC CRC
Address Code = <nbytes> #1 #i #nbytes
(L) (H)
= 01
The coil or status in the response message is packed as one coil per bit of the data field.
Digital inputs can be single (coded on one bit) or double (in this case 1 or 2 bits defined in
configuration).
For Single DI or Double DI coded on one bit, status is indicated as: 1 = ON, 0 = OFF.
For double DI coded on two bits, status indicates: [open contact, closed contact] = [0,1] for
open, [1,0] for closed, [0,0] for jammed], [0,1] for the other states
The less significant bit of the first data byte contains the coil addressed in the query. The
other coils follow toward the high order end of this byte, and from 'low order to high order' in
subsequent bytes, as described in the frame example.
Important notes :
1. If the returned coil quantity is not a multiple of eight, the remaining bits in the final byte
will be padded with zeros (toward the high order end of the byte). The Byte Count
Field specifies the quantity of complete bytes of data.
For easiest understanding between the gateway and the SCADA, it is recommended
to read a number of points which is a multiple of 8.
2. If the starting address is not a point in configuration, the message will be not be
accepted, and an error exception 2 will be returned.
3. If the starting address is in configuration and if there is some “holes” (addresses not in
configuration) theses holes will be padded with 0 (i.e value OFF).
4.6.6 Function 03 / 04: Read Holding Registers / Input Registers
The request function 03 or 04 reads the values of analogue inputs, tap position and counters
values in the slave.
In case of tap position and counters values, only natural coding is supported.
These two functions are the only way to read registers points with the MODBUS protocol.
Flags (validity, topical, ..) are not supported in the MODBUS protocol base.
This is equal using the Read Holding Registers request or the Read Input Registers request.
Broadcast is not supported.
Addresses in frames may start from 0…65535.
Query :
Slave Function Code Starting Starting No. of No. of CRC CRC

Address Address Address
= 03 Points (H) Points (L) (H)
(H) (L) (L)
The query message specifies the starting register and the quantity of registers to be read.
Response :
Slave Function Byte Data Data Data Data Data Data CRC CRC
address code Count
(H) (L) (H) (L) (H) (L) (L) (H)
=
= 03 #1 #1 #i #i #nbytes/ 2 #nbytes/
<nbytes>
2
The register data in the response message are packed as two bytes per register, with the
binary contents right justified within each byte. For each register, the first byte contains the
high order bits and the second contains the low order bits.
Important notes :
1. If the starting address is not a point in configuration, the message will be not be
accepted, and an error exception 2 will be returned.
2. If the starting address is in configuration and if there is some “holes” (addresses not in
configuration) theses holes will be padded with the value 0
4.6.6.1 Signed normalised coding
The signed normalised coding is used to encode the 16 bits-registers. Analogue maximal
value will be coded 7FFFh (decimal value + 32767), and minimal value will be coded 8000h
(decimal value –32768).
For this mode, the gateway may now code the value on 8 to 16 bits [ low part of the register
will be used ]. But, 16 bits is normally the standard to use the full scale conversion.
Example :
in configuration the maximal value for an analogue point is +3000 and minimum value for
this analogue is 0.
That means that when the analogue is received with value 0 from the system, the gateway
will send to the SCADA the register with 8000h value. If this analogue is equal to the
maximal value +3000, the value sent to the SCADA is 7FFFh. Calculation is linear for the
coding between the min and max values.
4.6.6.2 Unsigned normalised coding
The unsigned normalised coding is used to encode the 16 bits-registers. Analogue maximal
value will be coded FFFFh (decimal value + 65535), and minimal value will be coded 0000h
(decimal value 0).
For this mode, the gateway may now code the value on 8 to 16 bits [ low part of the register
will be used ]. But, 16 bits is normally the standard to use the full scale conversion.
Example :
in configuration the maximal value for an analogue point is +3000 and minimum value for
this analogue is 0.
That means that when the analogue is received with value 0 from the system, the gateway
will send to the SCADA the register with 0h value. If this analogue is equal to the maximal
value +3000, the value sent to the SCADA is FFFFh. Calculation is linear for the coding
between the min and max values.
4.6.6.3 Natural coding
The natural coding is used to encode data without any calculation. That’s means that integer
value will be send.
Example :
if the gateway receives the value 10.xxxx, the value 0Ah will be set in the appropriate
register. The gateway receives the value –10,xxxx the value FFF6h will be coded. Sent
values are considered as signed values which are included between –32768 and +32767.
When minimum and maximum values are reached values FFF6h and FFFFh are
respectively sent.
4.6.7 Function 05: Force Single Coil

This request function 05 is used to realise a control on an address point.
When broadcast, the function forces the same coil reference in all attached slaves.
Query :
Slave Function Code Point Point Force Force CRC CRC

Address Address Address Data Data
= 05 (L) (H)
(H) (L) (H) (L)
The query message specifies the coil reference to be forced. Points addresses are between
0…65535. The requested ON / OFF state is specified by a constant in the query data field.
A value of FF00h requests the coil to be ON.
A value of 0000h requests it to be OFF.
Response :

= 05 (L) (H)
(H) (L) (H) (L)
The normal response is an echo of the query, returned after the command has been sent to
the system.
NOTE : If value is incorrect, or if the control is refused for any reason
(equipment absent, equipment present and in local mode, equipment
invalid, …) an exception error 7 is returned.
4.6.8 Function 06: Preset single register
This request function 06 is used to preset a value in a register.
Query :

= 06 (L) (H)
(H) (L) (H) (L)
The query message specifies the register address to be preset. Points addresses are
between 0…65535. The requested value is specified by in the query data field.
Response :

= 06 (L) (H)
(H) (L) (H) (L)
The normal response is an echo of the query, returned after the register has been preset.
NOTE : Only natural setpoints are managed by this function (no scaling is
done)
4.6.9 Function 08: Diagnostic [Sub-function 0 only]

This request function 08 sub-function 0 is used to test the transmission.
Query :
Slave Function Code Sub Function Sub Function Data Data CRC CRC
Address code code
= 08 (H) (L) (L) (H)
(H) (L)
The query message specifies the data that will be echoed.

Response :
Slave Function Code Sub Function Sub Function Echoed Echoed CRC CRC
Address code code
= 08 Data Data (L) (H)
(H) (L)
(H) (L)
The normal response is an echo of the query with the same data send in the request.
NOTE : If the sub-function is different from 0, an exception error “illegal
function” is returned.
4.6.10 Function 15 : Force Multiple Coils
Normally, this request function 15 is used to realise a control on several contiguous
addresses.
This function can be used, but only one control can be send at the same time.
NOTE : Only a count number equal to 1 is allowed, otherwise an exception
error 3 will be replied.
4.6.11 Function 16 : Preset multiple registers
Normally, this request function 16 is used to preset on several contiguous addresses.
This function can be used, but only one preset can be send at the same time.
NOTE : Only a count number equal to 1 is allowed, otherwise an exception
error 3 will be replied.
4.7 HNZ (Yemen) communication

4.7.1 Finality
The purpose of this section is to describe:
• The adaptations brought to the software of the RTU C264 to include transmission HNZ
“Yemen” allowing to connect the RTU C264 to Centre SCC “SANA’A” as a Master-
Slave mode via a Concentrator (FEC)
• The structure of the data used in the messages

This protocol takes into account only of those definite for the exchanges between
Concentrator FEC and the RTU C264.
The development is realised for the extension of the project SCC SANA’A which envisages
in particular the replacement of existing RTU S80 by RTU C264.
The objective of the software is to connect the RTU C264 to centre SCC SANA’A by a
connection of type point-to-point or multipoint via a concentrator FEC.
As the computer is the slave on the network - regards to SCADA - this protocol is referenced
as “Slave Hnz” in the computer.
By default, the behaviour is the one described in “§ 4.2 SCADA common ”. Here are
described:
• Specific behaviours attached to the protocol HNZ
• Restriction and enhancement regarding § 4.2
• Part of the HNZ protocol used and not used

Only part which are different from § 4.2 or which need precision are described.
NOTE: It is supposed that the reader knows the HNZ protocol.
4.7.2 Data sent to SCADA
4.7.2.1 Binary inputs or Remote Signalling (RS)
4.7.2.1.1 Addressing in transmission
The RS are classified in three types:
• the Internal RS states (IRS);
• the Simple RS (SRS), associated or not with RC (Remote Control);
• the Double RS (DRS), associated or not with RC (Remote Control);

There is no zone of addressing reserved by type, they could thus be mixed inside the zone
of addressing (byte 0 to 255).
By analogy with the RTU S80 and for reasons of identification of the frame, the field of
addressing in transmission of a RS (for every type of RS) is represented by an address byte
and a number in the byte defined as follows:
• address byte = the address typed in data base divided by 8;
• number of bit = the remainder of this same division (0 to 7).

The maximum number of RS is 2048.
4.7.2.1.2 Messages
Message treated in the Concentrating direction (Centre) towards RTU:
• Request for RS Overall Check (code function $13).

Messages treated in direction RTU towards Concentrator (Centre):
• Answer for RS Overall Check (code function $16)

Sending RS Change of State (code function $0B). The changes of state of RS, dated, are
sent to the conversion layer which, after conversion to format HNZ YEMEN, put them in
queue for emission by the protocol. In the event of saturation of this file, this one is emptied
and the message of “loss information ”is posted there.
A parameter in database allows to empty or not this file on a reconnection of transmission.
4.7.2.1.3 Treatment of the particular RS called of RTU STATUS
Often The byte of address of transmission 0 can be reserved for the declaration of the
internal RS.
One IRS is reserved for the transmission of the message of «loss information ». the byte and
the row of address of transmission is set by configuration.
The other IRS can be selected in the range of addressing of the RS and can represent the
status of RTU.
The IRS are emitted at the time of a message of Overall Check, at the same time as the
SRS and the DRS.
4.7.2.2 Chronology
In normal operating mode, the loss chronology cannot appear.
4.7.2.3 State of the hour
The RTU must receive a time message of synchronization periodically. The state of the hour
is updated in each message of change of state RS.
4.7.2.4 Loss of information
In C264, the message of loss of information is transmitted in the following cases:
• reinitialisation of the RTU;
• reconnection of the transmission;
• saturation of the file of send in transmission.

The IRS “Loss of information” used to transmit this message has a fugitive operating mode,
only the closed state is transmitted in change of state. In a Overall Check, he state of this
IRS is always the open state.
Upon the sending of this IRS, the centre must follow a request for Overall Check to recover
the real state of the RS, and RM.
This RS will have to be declared «loss of information» in database of the RTU with its
address transmission.
4.7.2.5 Remote measurement (RM)
The field of addressing in transmission of a Remove Measurement (RM) is represented by
an address on a byte in a zone ranging between 0 and 255, their is 256 possible RM.
The concept of Internal RM not existing in C264. These are is only Analogue Remote
Measurement (ARM) and Digital Remote Measurement (DRM) (Tap position).
4.7.2.5.2 Resolution
The RM of the RTU are received by the Protocol on float 32 bits for the ARM and integer 32
bits for the DRM. The protocol applies a conversion of the computed value to acquired value
on signed integer 16 bits. An adaptation for the transmission is done by extension of the sign
for the values acquired on 12 bits and by truncation of the lower bits for the values acquired
on 16 bits.
Truncation is done with round up/down the approximate value.
When a RM is invalid, the bit of invalidity and the bit of sign are positioned to «1», the
transmitted value is fixed at $7FF.
4.7.2.5.3 Frequency of acquisition and transmission
RM can be transmitted periodically towards the higher level, each RM can be affected in
database to a cycle among four possible.
As the message of cyclic transmission of RM contents two contiguous entities, a certain
constraint on the level of the choice of the cycle, number and addresses of transmission will
be necessary to apply at the time of the realization of the database.
At the time of a request for RS Overall Check, the RTU C264 will return towards the centre
the whole of RM having an address of transmission, in the form of RM message cyclic, that
these ones are declared cyclic or not in database. This choice is necessary for the update of
RM, at level of the centre, following the sending of a message «loss information» .
4.7.2.5.4 Messages
RM are transmitted « periodically or on variation » to the Control Centre
The messages treated in the direction Concentrator (Control Centre ) towards RTU are:
• Not message
In direction RTU towards Concentrator (Control Centre ), we have:
• Sending RM on Variation (code function $05)
• Sending Cyclic RM (code function $02)

4.7.2.5.5 Constraints for the database
To limit addressing in database from 0 to 255.
RM will be obligatorily defined in transmission, on variation and/or cyclic.
In the case of transmission cyclic it is necessary to define groups by cycle such as a group
must be made up at least of two RM of address contiguous transmission and to the
maximum of a multiple of two RM, of contiguous address transmission also all. Two groups
belonging to two cycles of transmission different can be juxtaposed.
These constraints will have to be respected by the operator having charges the typing of the
database of C264 “Yemen. ”
4.7.2.6 Counters
The CT are polled by the SCADA, they are represented on the Modbus mapping, by a word
(2 bytes), 2 formats are available (unsigned scale, and unsigned integer).
Modbus function 3 or 4 can be used to poll the CT. More than one CT can be polled at a
time.
4.7.2.7 Computer disturbance file
Not implemented
4.7.2.8 IED disturbance files
Not implemented
4.7.2.9 Sequence Of Events file (SOE)

Not implemented
4.7.3 Data sent to computer
4.7.3.1 Remote Controls (RC)
RC are classified in two types:
• Simple RC (permanent or fugitive);
• Double RC (permanent or fugitive).

RC can be associated or not with RS.
There is no specific zone of addressing for the two types of RC.
These dispositions will have to be respected by the operator having charges the realisation
of the data bases of C264 “YEMEN. ”
For reasons of identification of the frame, the field of addressing in transmission of a remote
control is represented by an address byte and a number in the byte defined as follows:
• address byte = the address typed in data base divided by 8;
• number of bit = the remainder of this same division (0 to 7).

4.7.3.1.2 Catch of activity
The concept of catch of activity by the centre does not exist in the transmission S80 YEMEN.
4.7.3.1.3 Bay / Substation Dependence
The concept of bay and substation does not appear in the specification for S80 YEMEN. In
C264 it is possible to decide RC by RC if they are dependent or not on the bay and the
substation.
When the substation or the bay is in local mode, the dependent remote controls, sent from
the centre, are refused.
4.7.3.1.4 Messages
The messages treated in the direction Concentrator (Control Centre) towards RTU are:
• Execution RC (code function $19)

In direction RTU towards Concentrator (Control Centre), we have:
• Execution RC Acknowledgement (code function $09)

In the cases of negative execution the indicators of fault are set in the acknowledgement
message.
4.7.3.1.5 Remote Control in local mode
In C264, Control can be ordered locally from the console operator, in this case their
acknowledgements are not transmitted towards the Control Centre.
The simple and double remote controls could be mixed inside their zone of addressing in
transmission from 0 to 2047
These constraints will have to be respected by the operator having charges the typing of the
databases of C264 “Yemen. ”
4.7.3.2 Setpoints
The SP can be classified in two types:
• Analogue SP
• Digital SP
There is no specific zone of addressing for the two types of SP.
These dispositions will have to be respected by the operator having charges the typing of the
databases of C264 “YEMEN. ”
By analogy with the RTU S80 and for reasons of identification of the frames, the field of
addressing in transmission of a Set Point is represented by an address contained on 5 bits in
a byte.
The maximun number of SP is 32.
4.7.3.2.2 Catch of activity
The concept of catch of activity by the centre does not exist in the transmission S80 YEMEN.
To get around it, S900 generates an internal catch of activity automatically when it receives a
message of Set Point.
4.7.3.2.3 Bay / Substation Dependence
The concept of bay and substation does not appear in the specification for S80 YEMEN. In
C264 it is possible to decide SP by SP if they are dependent or not on the bay and the
substation.
When the substation or the bay is local mode, the dependent Set Points, sent from the
centre, are refused.
4.7.3.2.4 Messages
• Execution SP (code function $1a)

In direction RTU towards Concentrator (Control Centre):
• Acknowledgement Execution SP (code function $0a acquired

In the cases of negative execution the indicators of fault are set in the acknowledgement
message.
4.7.3.2.5 Set point in local mode
In C264 the SP can be ordered locally from the console operator, in this case their
acknowledgements are not transmitted towards the Control Centre.
The analogue or digital set point could be mixed inside their zone of addressing in
transmission from 0 to 31.
These dispositions will have to be respected by the operator having charges the databases
of C264 “Yemen. ”
4.7.4 Synchronisation
4.7.4.1 Setting with the hour / date of the RTU
The synchronisation of the RTU C264 for Yemen is done by two distinct messages of setting
at the date on the one hand and setting per hour on the other hand.
4.7.4.2 Modulo
The RTU C264 does not send periodically a change of modulo 10 mn.
The modulo 10mn is sent before a change of state if this is not in same that the last
transmitted modulo 10mn
4.7.4.3 Messages
The messages treated in the direction Concentrator (Control Centre) towards RTU are used
to date the RS, the messages of changes of state RS are dated with only the number of
10ms top inside the last transmitted modulo.
• Request of Setting the Date (code function $1C)
• Request of Setting the Hour (code function $7F)

In direction RTU towards Concentrator (Control Centre):
• Response of Setting per Hour (code function $7E)
• Sending change of Modulo time (code function $0F)

4.7.5 Transmission
4.7.5.1 Connection / Disconnection
The connection of the link, at the level of the protocol, is done by a double exchange SARM
–UA. The Centre sends SARM and the RTU answers UA then sends SARM, the Centre
answers UA and the RTU sends FS (end of session).
As the protocol is of the type Master–Slave, the RTU which is slave cannot detect the
disconnection. On the other hand, on reception of SARM during a normal sequence of
exchanges , the RTU réinitialises variables and queues of the protocol. Otherwise an
inactivity timer can be configured to prevent the C264 that a possible disconnection is
happened to update the information about communication with the SCADA.
4.7.5.2 Field «address» in the frame.
Bit 0 called bit of extension of address is attached to value 1, because in our case the
address in transmission is coded on only one byte without extension.
Bit 1 called «bit STATION A/B» is not really in conformity with standard standard HNZ (HNZ
66-S-15) because it takes the following values following the cases:
• direction Centre (FEC) towards RTU bit positioned to «1» at the time of sending of
message of the type SARM, RR, RES, or of applicative information. In the other cases
it is to «0 ».
• direction RTU towards Centre (FEC) positioned bit with «1» at the time of sending
of the message of the type UA. In all the other cases it is to «0».
Bits 2 to 7 contain the address of the RTU in transmission limited from 0 to 63.
4.7.5.3 Length of frame
The length of the frame is variable because it is possible to make concatenation of
information.
The number of characters of the frame is calculated on totality of the frame from the field
«address» to the field «checksum». Its value should not exceed 40 characters .
4.7.5.4 Field «control » in the frame.
This field is in conformity with the standard HNZ (HNZ 66-S-15) except in the use of «the bit
P/F» which in the two directions of transmission is to «0» except when there is a repetition.
4.7.5.5 Byte of checksum
This field is in conformity with the standard HNZ (HNZ 66-S-15).
4.7.5.6 Mode of framing of the frame

The framing of the frame is done by cut of Data Carrier in the two directions of transmission.
Special characters DLE STX and DLE ETX are not used for the HNZ «Yemen ».
4.7.5.7 Characteristics of V24 line
The characteristics of the lines are selectable in the database of C264, some parameters to
be defined are:
• Speed: 50 to 64000 Bauds
• Format of a character: 1 or 2 bits of start, 7 or 8 data bits, 1 bit of parity (no,even,odd),

1 bit of stop
• Delimitation of the frames: by Data Carrier Detect in two directions.

To use the C264 with the simulator Yemen, line parameters are:
NOTE: CTS wired and CD wired are forced if “delimitation of the frames” is
Data Carrier Detect in two directions
4.7.5.8 Dimensioning
A pool of buffers is reserved for the system of transmission. The number of buffers available
is sufficient to ensure the management of all queues of the system.
Queues for sending can store 200 changes of RS before saturation, the dimensioning of
these queues is carried out dynamically, at the time of the initialization of the RTU, according
to the maximal length of frames defined in the database.
4.7.5.9 Concatenation of the messages
If the parameter «concatened message» defined in database in the level of «information
networks: station» was validated, the transmitted messages can be grouped until not to
exceed the maximum length of the frame.
4.7.5.10 Characteristics of the messages of information
By analogy with RTU ECP80, when the Centre or the Concentrator FEC sends frames of the
«Information type » , there is no response from the RTU C264 (neither ES nor RR).
The dialogue resumes only following one request for end of session «RES» which the RTU
answers end of session «ES». That seems to be related to the judicious choice of the values
of temporization defined to the FEC.
In addition the RTU never sends message of the type « RR» but always «ES». The
acknowledgements of the received frame from the FEC are done only on sending of frame of
information.
4.7.6 Structures of frames

4.7.6.1 Frame received and sent by the RTU
The structure of the frame is in conformity with the standard HNZ (HNZ 66-S-15)
7 0
Transmission Address 1 1 Field Address
RTU
N/R P/F N/S I Field Command
Information Field Information

0 à 35 or 36 bytes
Checksum Field checksum

1 ou 2 bytes
C0366ENa
The checksum is a polynomial of degree 7 or 15 calculated in accordance with the standard

defined in the document HNZ 66-S-15
Detailled describe of the command field
Format Command Answer 7 6 5 4 3 2 1 0
Frame I I: Information NR P NS 0
RR: Receiver Ready NR F 0 0 0 1

supervision
RNR: Receiver Not Ready NR F 0 1 0 1
REJ: Reject NR F 1 0 0 1
ROS: Request to open NR F 1 1 0 1
of session
SARM: connection 0 0 0 P 1 1 1 1
DM: connection 0 0 0 F 1 1 1 1
Unnumbered
frames SNRM: connection 1 0 0 P 0 0 1 1
DISC: disconnection 0 1 0 P 0 0 1 1
UA: Unnumbered 0 1 1 F 0 0 1 1
Acknowledgement
RES: Request to end of 1 0 0 P 0 1 1 1
session
ES: End of session 0 1 0 P 0 1 1 1
CMDR: refusal of 0 0 1 F 1 1 1 1
command
4.7.6.2 Protocol
The protocol is of the type Master–Slave. The centre is a Master of the connection, the RTU
makes only answer the interrogations of the Centre. If the Centre stops the polling of the
RTU, no alarm is generated. Only the loss of information could be sent in the form of an
indication of defect, with the resume of the polling and if the internal file of events is
saturated.
Transmission HNZ YEMEN is not designed to function in doubled lines.
4.7.7 Detailled list of messages of application
4.7.7.1 RQ-RS-OC: Request for RS Overall Check - origin: Centre
7 0
Function code FC : $ 13
Not used 0 0 T T : Type of request

1 => RTU
0 => Not used
C0367ENa
The value T=0 relates to all the other requests other than for the RTU
4.7.7.2 RS-OC: Answer for RS overall Check - origin: RTU
7 0
Byte address of 1st block Addr : $ 0…..$ FF
RS i.3 RS i.2 RS i.1 RS i.0

V S V S V S V S V . S : Validity and state
block 1 0 . 0 => Open state
RS i.7 RS i.6 RS i.5 RS i.4 0 . 1 => Closed state
V S V S V S V S 1 . 0 => Coupler fault
or
RS i+1.3 RS i+1.2 RS i+1.1 RS i+1.0 Temporary fault
1 . 1 => Complementarity fault
V S V S V S V S
block 2 or
RS i+1.7 RS i+1.6 RS i+1.5 RS i+1.4 RS not defined in DB
V S V S V S V S
C0368ENa
NOTE: Notation RS «i.j» represents a RS of address transmission byte «i

»and row of bit «j ».
The length of this type of message is strictly limited to two blocks.
4.7.7.3 RS-CS: RS Change of state - origin: RTU
7 0
Function code FC : $ 0B
Transmission address byte Addr : $ 0 ….$ FF
Row V S VH C Sy Row : Address bit in the byte

$ 0 ….. $ 7
(low byte) V . S : Validity and State
0 . 0 => Open state
Time modulus
0 . 1 => Closed state
(high byte) 1 . 0 => Coupler fault
or
temporary fault
1 . 1 => Complementarity fault
HV : Validity hour
Time modulus 0 => Valid hour
Value : $0 …….EA5F 1 => Invalid hour
or 60000 tops 10 mS C : Chronology
0 => Correct chronology
1 => Loss of chronology
Sy : Synhronisation time
0 => Not used
1 => Hour not synchronised
C0369ENa
When a change of hour appends on C264, all information are flushed from the Chronology
fifo and are sent with the bit HV set to 1 (invalid hour possible)
If an information is received with a timestamp newer than the current time plus the depth of
the Chronology fifo, the bit HV is set to 1 to prevent the SCADA that this information did not
be inserted in the Chronology fifo because it is too newer
If an information is received with a timestamp older than the current time minus the depth of
the Chronology fifo, the bit C is set to 1 to prevent the SCADA that this information did not be
inserted in the Chronology fifo because it is too older
The bits HV,C and Sy are transmitted without treatment by the FEC to the SCADA
4.7.7.4 CY-RM: Cyclic RM - origin: RTU
7 0
Address 1st RM of the block Addr : $ 0…..$ FF
Value RM i (low byte)

Value RM : on 11 bits (0…10)
block 1 1 complemented
S I NU NU NU value RM i S : Sign
(high byte) 0 => Positive
1 => Negative
Value RM i+1 (low byte) I : Invalidity
block 2 0 => Valid RM
value RM i+1 1 => Invalid RM
S I NU NU NU
(high byte) NU : Not used
0 => Advocated value
C0370ENa
NOTE: The notation invalid RM is represented by a negative value equal to

$7FF and the positioned bit of Invalidity with «1 ».
The length of this type of message is strictly limited to two blocks.
4.7.7.5 RM-CV: RM on variation - origin: RTU
7 0
Address RM of the block Addr : $ 0…..$ FF
Value RM (low byte)

Value RM : on 11 bits (0…10)
1 complemented
S I NU NU NU Value RM S : Sign
(high byte) 0 => Positive
1 => Negative
Absolute time (low byte) I : Invalidity
0 => Valid RM
Absolute time (high byte) 1 => Invalid RM
NU : Not used
Absolute time over 24 hours

Value : $0 …….. A8BF
or 43200 multiples of 2 seconds C0371ENa
NOTE: The notation «invalid RM» is represented by a negative value equal to

$7FF and the positioned bit of Invalidity with «1 ».
4.7.7.6 RQ-RC: Request RC - origin: CENTRE
7 0
Address of byte Addr : $ 0 ….$ FF
Row : Address bit into the byte

Row X Y NU NU NU $ 0 ….. $ 7
X . Y : Order of execution
0 . 1 => Close
1 . 0 => Open
0 . 0 => Not used
1 . 1 => Not used
NU : Not used
C0372ENa
4.7.7.7 ACK-RC: Acknowledgement of RC - origin: RTU
7 0
Address of byte Addr : $ 0 ….$ FF
Row ACK 1 ACK : Acknowledgement on 4 bits

$0 => positive ack
$1 => important fault
or failure RC function
Row : Address of the bit in the byte $2 => not important fault
$ 0 ….. $ 7 $3 => external fault
$9 => Substation or bay
in local mode
$0A => RC not defined in DB
or incorrect message
$0C => Invalid order
or signaling fault
the other codes are not used
C0373ENa
4.7.7.8 RQ-SP: Request Set point - origin: CENTRE
7 0
FC : $ 1A
Function code
NU NU 1 Transmission address Addr : $ 0 ….$ 1F
Value SP (low byte) Value SP : on 12 bits (0 …. 11) in BCD

S : Sign
0 => Positve
S NU NU NU Value SP (high byte)
1 => Negative
NU : Not used
C0374ENa
4.7.7.9 ACK-SP: Acknowledgement Set Point - origin: RTU
7 0
Function code FC : $ 0A
NU NU 1 Transmission address Addr : $ 0 ….$ 1F
Value SP (low byte) Value SP : on 12 bits (0 …. 11) in BCD

S : Sign
0 => Positve
S NU NU NU Value SP (high byte)
1 => Negative
ACK ACK : Acknowledgement

$0 => positive ACK
NU : Not used $2 => incorrect message
0 => advocated value $3 => coupler fault
$5 => important fault
$0A => SP not defined in DB
$0B => Substation or bay in local mode
The other codes are not used
C0375ENa
4.7.7.10 RQ-SET-DATE: Request setting DATE - origin: CENTRE
7 0
Function code FC : $ 1C
Day's number Day : $ 1 ….$ 1F
Month's number Month : $ 1 ….$ 0C
Year's number Year : $ 0 ….$ 63

C0376ENa
NOTE: There is no response from the RTU following this request.
4.7.7.11 RQ-SET-HOUR: Request setting hour - origin: CENTRE
7 0
Function code FC : $ 7F
NU NU : Not used
(high byte)
HS : Modulus of time of start
modulus modulus
=> Value : $0…….$EA5F
(low byte)
or 60000 tops 10 mS
HS
null byte => Value : 0
nul byte
M10M Modulus 10 minutes
=> Value : $0 …… $8F
M10M or 144 moduli day
(high byte)
TCT : time compensation
TCT Time compensation in transmission
in transmission
(low byte) => Value : $0…….$FFFF
or 65536 tops 10 ms
block NU Block NU : two bytes not used
C0377ENa
NOTE: Attention for the messages related to the hour the high byte are in the
first place.
The time compensation in transmission corresponds to the delta of time that puts to forward
a message between the Concentrator (Control Centre) and the RTU S900 or reciprocally.
This compensation is calculated by the Concentrator (Control Centre) following an exchange
«RQ-SET-HOUR» and «RE-SET-HOUR» following calculation below:
TCT = [ (HR - HS) –(TTRTU) ] / 2
TCT: Time compensation in transmission
HR: Hour of reception of the message of answer RE-SET-HOUR
HS: Hour of emission of the message of request RQ-SET-HOUR
TTRTU: Time of transit to the RTU (see following paragraph )
4.7.7.12 RE-SET-HOUR: Response set hour - origin: RTU
7 0
Function code FC : $ 7E
NU NU : Not used
(high byte)
HS : Modulus of time of start
modulus modulus
=> Value : $0…….$EA5F
(low byte)
or 60000 tops 10 mS
HS null byte => Value : 0
null byte
M10M Modulus 10 minutes
=> Value : $0 …… $8F
M10M
or 144 moduluss day
(high byte)
TCT : time compensation
TCT Time compensation in transmission
in transmission
(low byte) => Value : $0…….$FFFF
or 65536 tops 10 ms
(high byte)
TTRTU Time of Transit in RTU TTRTU : Time of transit in RTU
=> Value : $0…….$FFFF
(low byte) or 65536 tops 10 ms
C0378ENa
The time of transit to RTU (TTRTU) corresponds to the delta of time between the reception
of the message of request RQ-SET-HOUR and the emission of its answer RE-RE-HOUR.
4.7.7.13 M10M: Modulo 10 minutes - origin: RTU
7 0
Function code FC : $ 0F
M10M M10M : Number of modulus

=> Value : $0…..$8F
or 144 moduli day
C0379ENa
4.7.8 Sequence of dialogue

The sequence of dialogue can be defined in the following form:
• sequence of starting which starts with a connection HNZ
• sequence of initial exchanges
• sequence of information exchanges.

After connection, the diagrams below are just given as an example, sometime the
exchanges can be different.
4.7.8.1 Sequence of connection
RTU
CENTRE
SARM
SARM
UA
SARM
Connection HNZ
UA
ES
ROS
RS_CS For example RS_CS
RR Acknowledgement
ES End of session
C0380ENa
The sequence of connection of the protocol is represented above followed with a change of
state RS .
4.7.8.2 Sequence of initial exchanges
CENTRE RTU
ROS
Start and end of session without
ES information
ROS
Start and end of session with
RQ-SET-DATE setting of the date
ES
Waiting for repetition time-delay
or end of session
RES
ES Request and end of session
ROS
Open of session with setting of
RQ-SET-TIME time to calculate the
ES compensation

or end of session
RES
ES Request and end of session
ROS
RQ-SET-TIME Start of session with response
of setting time
RR Acknowledgement and end of
Session
ES
ROS
RQ-SET-TIME
Identical sequence for setting
time with compensated time
RR
ES
ROS
ES
C0381ENa
4.7.8.3 Sequence of information exchanges
CENTRE RTU
ROS
Start of session with request of
RQ-RS-OC overall check
ES

or end of session
RES
ES
Request and end of session
ROS
RS-OC
RR
RS-OC Responses to overall check
RR
RS-OC
ROS
CY-RM
RR Send cyclic RM
CY-RM
ROS
ES Interrogation at start of session
ROS
RQ-RC Start session with request RC

RES or end of session
ES Start and end session
ROS
ACK-RC Start session with
RR acknowledgement of RC
(it is same principle for the SP)
ES
ROS
RM-CV Send of change of value of RM
C0382ENa
4.7.9 Summary of function code messages

Origin: RTU
HEXADECIMAL CODE DECIMAL CODE NAME

02 02 CY-RM
05 05 RM-CV
09 09 ACK-RC
0A 10 ACK-SP
0B 11 RS-CS
0F 15 M10M
16 22 RS-OC
7E 126 RE-SET-HOUR
Origin: Centre
HEXADECIMAL CODE DECIMAL CODE NAME

13 19 RQ-RS-OC
19 25 RQ-RC
1A 26 RQ-SP
1C 28 RQ-SET-DATE
7F 127 RQ-SET-HOUR
4.7.10 Configuration
Refer to chapter AP
4.7.11 Cable
A specific cable must be used for HNZ Yemen Protocol:
V24 DB25 DB9 DB9 DB25 V24
101 1 1 101
102 7 5 5 7 102
103 2 3 2 3 104
104 3 2 3 2 103
109 8 1 7 4 105
8 5 106
105 4 7 1 8 109
106 5 8
4.8 HNZ (Elenas) communication

4.8.1 Functional specifications
4.8.1.1 Scope
The C264 RTU software is supplemented at the code conversion level to provide a message
handling system compatible with the messaging of the S900 RTU.
The following sections describe the changes made to C264 in order to incorporate the new
transmission into the standard C264 software. They also specify the restrictions from the
EPC 3200 specification and the constraints to be observed when generating the database
(DB).
4.8.1.2 Functional description
4.8.1.2.1 Processing Remote Signalings
4.8.1.2.1.1 Adressing
Single remote signalings (SRSs) and dual remote signalings (DRSs) are split into two blocks
with different address spaces, and separated by at least one byte.
This arrangement shall be strictly observed when entering the ELENAS and C264 database.
4.8.1.2.1.2 Supported messages
The table below lists the RS messages handled:
MS-to-RTU Query Fc Sc RTU-to-MS Response Fc Sc

(hex) (hex) (hex) (hex)
RS General Check 13 01 RS State Change 0A
Initiation General Check 13 00 RS General Check 16
(identical
for SRSs
& DRSs)
INValid SRSs in General Check 17
End of RS General Chek 18 0C
When invalid SRSs are embedded in GC responses, the following scheme is implemented:
If a SRS byte contains an invalid RS when constructing the SRS GC message (fc 16 h), the
construction process stops, and the message, without the byte, is buffered in the transmit
queue. An INV SRS GC message (17 h) is then constructed and issued. It contains all
invalid SRSs found in the GC block sent by the application program to the code conversion
layer. Normal SRS GC transmission resumes after this byte.
Also, as SRS and DRS addresses are clearly separated in BD, SRS and DRS states are
contained in different messages.
4.8.1.2.1.3 Internal Signalings

Internal signalings (ISs) are packed as two bytes addressed 02 and 03. The table below
shows how C264 ISs are coded.
Address 02
Bit EPC 3200 C264

0 Unused Unused
1 Unused Unused
2 RTU initialization RTU Reset
3 Real state of RC polarity Unused
4 Transmission link 1 failure Communications Line 1 Fault
5 Transmission link 2 failure Communications Line 2 Fault
6 Temperature warning (50° C) Unused
7 Temperature alarm (60° C) Unused
Address 03
Bit EPC 3200 C264

0 Output fault (Control output function invalid) (1) Global DOU board Status
1 Input hardware fault (3) Global DIU board Status
2 Analog hardware fault (Analog input function (2) Global AIU board Status
invalid)
3 Signalling input byte(S) invalid Unused
4 Digital output hardware fault Unused
5 Positions acquisition hardware fault Unused
6 Counting acquisition hardware fault Unused
7 Analog setpoint hardware fault (4)Global AOU board Status
When one or more DOU couplers fail, the RC function continues with the couplers that
remain valid.
When one or more AIU couplers fail, the RM function continues with the couplers that
remain valid.
When one or more DIU couplers fail, the RS function continues with the couplers that
remain valid.
When one or more AOU couplers fail, the SP function continues with the couplers that
remain valid.
4.8.1.2.1.4 Database Constraints
4.8.1.2.1.4.1 External RSs
To meet EPC 3200 requirements, DRSs must be specified in reverse state in the RTU
database.
4.8.1.2.1.4.2 Internal RSs
ISs sent to ELENAS derive from the C264 fault. The corresponding fault conditions must be
made transferable.
Note: ISs are automatically created in the ELENAS database and labeled identically to those
of the EPC 3200 RTUs. You must always observe this consistency when generating the
database of the C264 RTU.
4.8.1.2.1.5 Chronology loss

In EPC 3200, the start-of-chronology-loss (fc 18 h, sc 07 h) and end-of-chronology-loss
message (18 h, 06 h) is the same for the entire RTU.
In C264, the chronology loss condition relates to a rack and is reported to the MS in RS state
change messages.
At the code conversion level, the S900 is adapted to send the start-of-chronology-loss
message upon occurrence of the first RS containing the chronology loss flag.
4.8.1.2.1.6 Information loss
The information loss message (fc 18 h , code 05 h) is transmitted without specifying the
cause of such condition.
4.8.1.2.2 Processing Remote Measurements
4.8.1.2.2.1 Resolution
EPC 3200’s RMs are 8-bit values (coded in twos complement when signed) while C264’s
RMs are float(32bits) values. The EPC 3200/C264 match is done by scaling the float value in
8 bit values (coded in twos complement when signed). The scaling is made following if the
measurement has a symmetrical, positive/negative range (i.e. + 5 mA, + 10 mA, or + 20 mA),
or if the range is positive (i.e. 0-5 mA, 0-10 mA, or 0-20 mA). The same procedure applies to
voltage ranges.
The resulting value is rounded off.
In order to take into account this RM accuracy difference and avoid to transmit RM variations
with the same rounded off value, a transmitted 8 bit RM table has been defined.
4.8.1.2.2.2 Input rate and transmission cycle
In C264, the concept of Prioritized RMs - i.e. RMs captured more frequently - does not exist,
and you cannot modify the scan cycle online. The input rate is set on a per-rack basis.
For HNZ Elenas, no transmission cycle is available. The RM are only sent on variation.
4.8.1.2.2.3 Operating Mode
Byte (hex) Description

00 Not processed
01 RM transmission upon state change enabled, end of disable
FF RM transmission disabled
02-FE Unused
The operating mode of individual RMs(fc 01 h) is determined by the value of the op-mode
byte:
Byte (hex) Description

00 Not processed
01-FE RM deadband value, end of disable
FF Unused
Upon RTU reset, the transmission of all RMs is disabled until the end-of-RM-GC message is
issued.
Mode 0 of EPC 3200 is made functional by marking the relevant RMs as cyclical in the
RTU’s DB.
4.8.1.2.2.4 RM Snapshot
The function is not supported in S900 so it ‘s also not supported in C264.
4.8.1.2.2.5 Supported Messages
The table below lists the RM messages handled:
MS-to-RTU Query Fc Sc RTU-to-MS Response Fc Sc

(hex) (hex) (hex) (hex)
Initiation General Check 13 00 RS General Check 02
End of RM General Check 18 0E
Operating Mode of all 02 RM State Change 01
RMs
Operating Mode of 01
individual RMs
The following RM messages are not supported:
MS-to-RTU Query Fc RTU-to-MS Response Fc

(hex) (hex)
RM priority change 06* Priority Change Acknowledge 06
List of High-Priority RMs 26* List of High-Priority RMs 26
RM Snapshot 30* RM Snapshot 32
End of RM Snapshot 40
RM Snapshot Rejected 41
* When the message is not handled, the RTU returns a Request Reject message (22 h).
The Prioritized RMs concept does not exist in C264, no cyclical RMs are allowed for HNZ
Elenas.
4.8.1.2.3 Processing Remote Controls
4.8.1.2.3.1 Control Activity
The concept of Control Activity captured by the MS is not supported by the ELENAS HNZ
transmission. As a result, C264 automatically and internally generates an activity capture
upon receipt of a RC message.
4.8.1.2.3.2 Bay/Station Dependency
The Bay/Station concept exists . In C264, you can determine whether individual RCs depend
on the associated bay and station.
When the station or bay is under local control, all station/bay-dependent RCs originating
from the MS are rejected.

The following RC messages are handled:

(hex) (hex)
Send RC 19 RC Acknowledgement 09
The table below shows how the S900 acknowledgements are sent back to the MS.
C264 EPC 3200 (4)

Rejected Reject Code Acknowledgement No. Acknowledgement
No xxxx Positive 1 Positive
Yes The associated RS is Minor fault 10 Status confirmation
already in the required state
Yes Error during RC execution External fault 5 -
Yes RC does not exist Major fault 2 Wrong message
Yes Faulty RC coupler Major fault 3 Control function invalid
Yes Faulty rack Major fault 3 Control function invalid
Yes Local bay Major fault 11 Local operator
Yes Local station Major fault 11 Local operator
Yes Request being processed Major fault 7 Control function busy
4.8.1.2.3.4 Local RCs

In S900, RCs can be requested locally, in which case their acknowledgements are not
passed to ELENAS.
Anyone
4.8.1.2.4 Processing Analog Setpoints
4.8.1.2.4.1 Control Activity
The concept of Control Activity captured by the MS is not supported by the ELENAS HNZ
transmission. As a result, C264 automatically and internally generates an activity capture
upon receipt of an ASP message.
4.8.1.2.4.2 Bay/Station Dependency
The Bay/Station concept exists in C264. Consequently, all database-defined ASPs couldl
depend on the bay or station.
If the ASP depends on the station, the value originating from the MS is rejected when the
station is under local control.
EPC 3200’s ASPs are 8-bit values (coded in twos complement when signed) while C264’s
ASPs are float (32-bits) values. The EPC 3200/C264 match is done by scaling the 8 bit SP
value (coded in twos complement when signed) in float value. The scaling is made following
if the setpoint has a symmetrical, positive/negative range (i.e. + 5 mA, + 10 mA, or + 20 mA),
or if the range is positive (i.e. 0-5 mA, 0-10 mA, or 0-20 mA).

The following SP messages are handled:

(hex) (hex)
Send SP 1A SP Acknowledgement 1A
The table below shows how the S900 acknowledgements are sent back to the MS.
S900 EPC 3200 (2)

Rejected Reject Code Acknowledgement No. Acknowledgement
No xxxx Positive 1 Positive
Yes SP does not exist Major fault 2 Wrong message
Yes Faulty SP coupler Major fault 4 Analog setpoint function
invalid
Yes Faulty rack Major fault 4 Analog setpoint function
invalid
Yes Local bay Major fault 2 -
Yes Local station Major fault 2 -
Yes Error during execution Major fault 2 -
4.8.1.2.4.5 Local ASPs

In C264, ASPs can be requested locally, in which case their acknowledgements are not
passed to ELENAS.
Anyone
4.8.1.2.5 Processing Digital Setpoints
Digital setpoints exist in C264, but not in S900. As a result, the Send DSP and DSP
Acknowledgement messages (1B h) are ignored.
4.8.1.2.6 Processing Remote Counts
4.8.1.2.6.1 Counting down
The Count Down function is not supported by C264. Only up-counting inputs are processed,
and the counter values exchanged between the RTU and the MS are always positive (sign is
’0’).
The counter resolution is 22 bits plus sign in EPC 3200, and 32 bits unsigned in C264.
C264 must therefore be tuned to operate within 22-bit values during a cumulative period.It is
recommended to configure the RCT with automatic reset after the cumulative period.
4.8.1.2.6.3 Cumulated RCTs
If you reset a RCT from the alphanumeric display console, the value change message is not
sent to the MS. Note that the RCT reset operation does not alter the cycle of RCT
transmission at the end of the cumulative period.
The MS Set Time command can alter the cycle of RCT transmission. The cumulative period
is recalculate if the C264 sets a new time. The transmission is made always in fixed hour
(12h00,12h10….).

The table below lists the RCT messages handled:

(hex) (hex)
RCT Report 04 RCT Report (individual or all RCTs) 04
Cumulated RCTs 03
Invalid RCT 05*
* This message is spontaneously sent by the RTU to signal the RCT transition to invalid.
In order for the EPC 3200 to operate identically to the C264, complete the fields below as
follows:
Clear counter at the end of cumulative period True
Cumulative period storage capacity 12
Cumulative period 10 minutes
4.8.1.2.7 Processing Tap Changer Positions
4.8.1.2.7.1 Coding inputs
In C264, TPs can be 1 of N-, decimal-, or BCD-coded ….
An offset can be added.It is defined in the Data base.
The table below lists the TP messages handled:
MS-to-RTU Query Fc Sc RTU-to-MS Response Fc

(hex) (hex) (hex)
Initiation General Check 13 00 TP General Check 3D
TP State Change 0D
* In the MS-to-RTU direction, there is no TP-specific General Check Request.

Also, the TP Report Request is not supported by C264.
4.8.1.2.8 Setting RTU Time
The MS sends Set Time commands (fc 1D h) to the RTU, but no Set Date message. This
means that you must set the date from the operator console.
4.8.1.2.9 Synchronizing S900
4.8.1.2.9.1 Operation Principe
Under the EPC 3200 operating mode, C264 is timed by the MS as follows:
Definitions:
Trec Time received in the Set Time command
Tloc Local RTU time derived from the physical handler
Delta Trec - Tloc difference
Tcur Current time when setting the RTU time
Upon reception of the Set Time command (1D h), the logical handler stores Tloc at the end of
the message.
NOTE: On the C264 side, Trec contained in the message relates to the last bit
of the first byte.
The time processing function of the application performs the time setting with Tcur + Delta
and requests the transmission of a response with Delta.
The base rack then distributes timing to all of the expansion racks.
Remember, the C264 is synchronized only after 2 consecutive times setting with the delta
time between the time in second time setting and the current time C264 less than 200 ms.
The C264 remains synchronized during maximum 30 mn without receive time setting.
The Date concept does not exist in ELENAS HNZ. The date, however, is required for the
local RTU operation (i.e. for date/time-stamping logs, reports, etc.). Consequently, the
operator console and the MS will be able to set the RTU time, but the local operator can only
set the date and time if the MS is not accessible (transmission fault).
Anyone
4.8.1.2.10 Sending Modulo Message
The Modulo message (fc 0F h) is not sent to the MS every 10 minutes, but sent before each
message sending an information with the time within a new modulo.
4.8.1.2.11 Identifying RTU
The ID Request (fc 20 h) is processed by the RTU which returns a RTU ID response (20 h)
specifying the RCP number and DB revision.
The RTU ID message is spontaneously sent after the RTU reset.
4.8.1.2.12 Resetting RTU Remotely
The RTU Reset request (fc 21 h) from the RTU causes a complete RTU reset, with no
response expected. It is like a computer faulty with cause “from the SCADA protocole”
4.8.1.2.13 Rejecting Request
The Request Reject message (fc 22 h) is returned by the RTU upon receipt of a wrong
message from the MS
4.8.1.2.14 Requesting Initiation General Check
When receiving an Initiation General Check Request (fc 13 h, code 00 h), C264 returns the
following sequence of messages:
Message Sequence Fc (hex) Sc (hex)

RTU ID 20
RS General Check 16
End of RS General Check 18 0C
RM General Check 02
TP General Check 3D
End of RM General Check 18 0E
If during a GC sequence the transmission queue are full, the RTU transmits the End of RS
(and RM) GC for the interrupted GC.
4.8.1.2.15 Transmission
4.8.1.2.15.1 Queue and buffer size
A buffer pool is dedicated to the transmission system.
The number of available buffer is design to assume the all system queue number.
200 RS status change can be queued before saturating in the transmission queues.
At the RTU initialization, the queues sizing is dinamicaly done, depending on the frame
length defined in the DB.
4.8.1.2.15.2 Queue saturation processing
When a transmission queue is full, it is cleared and an Info Loss message is queued.
If a GC sequence is interrupted, the end of GC messages are sent before the Info Loss
message.
4.8.1.2.15.3 Transmission queue initialization
The transmission and protocol queue are cleared after a link initialization procedure (SNRM -
UA messages exchange).
4.8.2 Data Specifications
4.8.2.1 Scope
The purpose of this chapter is to describe the relationship between S9R and ELENAS’s
transmission addressing schemes.
4.8.2.2 Data Description
Remote Signalings, Remote Controls, and Internal Signalings
In ELENAS, RSs, RCs, and ISs are identified by a byte number (Byte #), and a bit position in
the byte (in the range of 0-7), which is always specified in the same way. The byte number,
however, is determined by the entity processed:
Entity Byte # (hex) ’i’ range (hex)

RS B0 + i 0-4F
RC (1C + i) x 04 0-0B
IS 02 + i 0-01
Remote Measurements and Setpoints

In ELENAS, RMs and SPs are only identified by a byte number (Byte #):

RM 20 + i 0-43
SP 04 + i 0-17
Tap Changer Positions and Remote Counts

TPs and RCTs are identified by a word number (Word #):

TP A0 + i 0-0F
RCT 64 + i 0-0B
In the S9R database, the description of the ELENAS HNZ transmission addresses is a two-
step procedure. First, each entity type is given a fixed base address, then each entity in the
type, also known as occurrence, is assigned a relative address. The absolute address of an
entity results from the following equation:
Absolute address = Base address + Relative address
The default base addresses for each entity type are listed below:
RS_base_add 176 (B0 h)
RC_base_add 112 (70 h)
IS_base_add 2
RM_base_add 32 (20 h)
SP_base_add 4
TP_base_add 160 (A0 h)
RCT_base_add 100 (64 h)
4.8.2.3 Identifying Remote Signalings in ELENAS and S9R
4.8.2.3.1 Single RSs
In S9R, SRSs are assigned transmission addresses in the range of 0-4096 decimal.
The ELENAS address (Byte #, Bit Position) is converted into the S900 address (X) using the
following equation:
X = (Byte # - RS_base_add) x 08 h + Bit Position + 10 h
The SRS address range used for ELENAS in S9R will therefore be of 16-655. SRS
addresses are shifted 16 bit positions (10 h) to avoid overlapping IS addresses. Note that ISs
and RSs hare the same address space.
The table below shows the ELENAS-to-S900 address conversion for the first and last SRSs.
It corresponds to the RS default base addresses. S9R addresses are entered by the
operator via GBD 900.
ELENAS ADDRESS S9R ADDRESS

Byte # (Hex) Bit Position X
B0 00 16
B0 01 17
B0 02 18
B0 03 19
B0 04 20
B0 05 21
B0 06 22
B0 07 23
B1 00 24
B1 01 25
B1 02 26
B1 03 27
B1 04 28
. . .
. . .
. . .
FF 06 654
FF 07 655
NOTE: In S9R, RS transmission addresses start at location 16. Addresses 0-15

are to be reserved for ISs.
4.8.2.3.2 Dual RSs

In S9R, DRSs are assigned transmission addresses in the range of 0-4096 decimal.
The ELENAS address (Byte #, Bit Position) is converted into the S9R address (X) using the
following equation:
X = (Byte # - RS_base_add) x 04 h + Bit Position + 320 h
The DRS address range used for ELENAS in S9R will therefore be of 800-1119. DRS
addresses in S9R are shifted 800 bit positions (320 h) to avoid overlapping SRS addresses.
NOTE: The SRS/DRS separation must be reproduced in ELENAS. The
ELENAS address of the SRS/DRS separation is peculiar to it, and not
fixed. Such separation is required to build GC messages, since the
two entities have different structures.
The table below shows the ELENAS-to-S9R address conversion for the first and last DRSs.
It corresponds to the RS default base addresses. S9R addresses are entered by the
operator via GBD 900. ELENAS

B0 00 800
B0 01 801
B0 02 802
B0 03 803
B1 00 804
B1 01 805
B1 02 806
B1 03 807
B2 00 808
. . .
. . .
. . .
FF 02 1118
FF 03 1119
NOTE: As shown above, the first ELENAS address within the RS space is B0
hex, 00, and the corresponding DRS address in GBD 900 is 800
decimal. This does not mean that the first DRS must start at this
address, but from this address. Since a typical configuration usually
combine SRSs and DRSs having the same address space (i.e. B0-FF
h), make sure you insert at least one byte between the two blocks
when generating the DB in order to avoid SRS/DRS overlap.
4.8.2.4 Identifying Remote Controls in ELENAS and S9R

In S9R, RCs are assigned transmission addresses in the range of 0-2047 decimal.
The ELENAS address (Byte # and Bit Position) is converted into the S9R address (X) using
X = (Byte # - RC_base_addr) x 02 h + Bit Position
The RC address range used for ELENAS in S9R will therefore be of 0-95.
The table below shows the ELENAS-to-S9R address conversion for the first and last RCs. It
corresponds to the RC default base addresses. S9R addresses are entered by the operator
via GBD 900.

70 00 0
70 01 1
70 02 2
70 03 3
70 04 4
70 05 5
70 06 6
70 07 7
74 00 8
74 01 9
74 02 10
74 03 11
74 04 12
. . .
. . .
. . .
9C 06 94
9C 07 95
4.8.2.5 Identifying Internal Signalings in ELENAS and S9R

In S9R, ISs are assigned transmission addresses in the range of 0-4096 decimal, and they
have the same address space as RSs.
The ELENAS address (Byte # and Bit Position) is converted into the S9R address (X) using
X = (Byte # - IS_base_addr) x 08 h + Bit Position
The IS address range used for ELENAS in S9R will therefore be of 0-15.
The table below shows the ELENAS-to-S9R address conversion for all ISs. It corresponds to
the IS default base addresses. S9R addresses are entered by the operator via GBD 900.

02 00 0
02 01 1
02 02 2
02 03 3
02 04 4
02 05 5
02 06 6
02 07 7
03 00 8
03 01 9
03 02 10
03 03 11
03 04 12
03 05 13
03 06 14
03 07 15
4.8.2.6 Identifying Remote Measurements in ELENAS and S9R

In S9R, RMs are assigned transmission addresses in the range of 0-2047 decimal.
The ELENAS address (Byte #) is converted into the S900 address (X) using the following
equation:
X = Byte # - RM_base_addr
The RM address range used for ELENAS in S9R will therefore be of 0-67, or 0-79 if there is
no RCT.
The table below shows the ELENAS-to-S9R address conversion for the first and last RMs. It
corresponds to the RM default base addresses. S9R addresses are entered by the operator
via GBD 900.
ELENAS S9R ADDRESS

ADDRESS
Byte # (Hex) X
20 0
21 1
22 2
23 3
24 4
25 5
26 6
27 7
28 8
29 9
. .
. .
63 67
4.8.2.7 Identifying Setpoints in ELENAS and S9R

In S9R, SPs are assigned transmission addresses in the range of 0-255 decimal.The
ELENAS address (Byte #) is converted into the S9R address (X) using the following
equation:
X = Byte # - SP_base_addr
The SP address range used for ELENAS in S9R will therefore be of 0-23.
The table below shows the ELENAS-to-S9R address conversion for the first and last SPs. It
corresponds to the SP default base addresses. S9R addresses are entered by the operator
via GBD 900.
ELENAS S9R ADDRESS

ADDRESS
Byte # (Hex) X
04 0
05 1
06 2
07 3
. .
. .
1B 23
4.8.2.8 Identifying Tap Changer Positions in ELENAS and S9R

In S9R, TPs are assigned transmission addresses in the range of 0-255 decimal.The
ELENAS address (Word #) is converted into the S9R address (X) using the following
equation:
X = Word # - TP_base_addr
The TP address range used for ELENAS in S9R will therefore be of 0-15.
The table below shows the ELENAS-to-S9R address conversion for the first and last TPs. It
corresponds to the TP default base addresses. S9R addresses are entered by the operator
via GBD 900.
ELENAS S9R ADDRESS

ADDRESS
Word # (Hex) X
A0 0
A1 1
A2 2
A3 3
. .
. .
AF 15
4.8.2.9 Identifying Remote Counts in ELENAS and S9R

In S9R, RCTs are assigned transmission addresses in the range of 0-2047 decimal.
The ELENAS address (Word #) is converted into a S9R address (X) using the following
equation:
X = Word # - RCT_base_addr
The RCT address range used for ELENAS in S9R will therefore be of 0-11.
The table below shows the ELENAS-to-S9R address conversion for the first and last RCTs.
It corresponds to the RCT default base addresses. S9R addresses are entered by the
operator via GBD 900.
ELENAS S9R ADDRESS

ADDRESS
Word # (Hex) X
64 0
65 1
66 2
67 3
. .
. .
6F 11
4.8.2.10 ELENAS/S9R Address Maps
ELENAS ADDRESSING S9R ADDRESSING
NO
00
0
02 ISs 16
ISs
03
04
ASPs
SRs
655
1C 700
1F
DRs
20
ARMs
63 939
64
RCTs
6F
70 0
RCc
SPs
A0
23
TPs
AF
B0
RMs
67
RSs RCTs
11
0
SRCs 95
100
DRCs
147
FF 0
TPs
3
C0383ENa
4.8.3 Interface Specifications

4.8.3.1 Scope
Only the communications interface between ELENAS and C264 is discussed in this chapter.
4.8.3.2 Interface Description
Refer to section 4.8.5 Detailed Messages List for a detailed description of the MS-RTU
messaging.
4.8.3.3 Interfacing
4.8.3.3.1 Purpose
The interface is used to connect C264 to ELENAS while maintaining the compatibility with
the EPC 3200 RTUs.
4.8.3.3.2 Static features
4.8.3.3.3 Drivers
C264 drivers establish the format of the frame in the transmit direction and perform the frame
integrity checks in the receive direction.
The ELENAS HNZ transmission driver adds to those already existing in C264.
The main differences between this driver and the standard C264 HNZ driver are as follows:
• When the MS communicates with the RTU through a dual line, the MS request is
always received by the RTU on only one of the two lines, and the RTU always
responds to the MS over this single line.
• The CRC generation is slightly different from the standard C264 HNZ procedure. The
CRC field contains the address, control byte, data block, and ETX character. Both the
transparent DLE character in the data and the DLE ETX sequence are processed by
the CRC.
DLE
DLE STX Addr Ctrl Data DLE ETX

C0384ENa
Only the first two bytes are ignored in the CRC generation.
4.8.3.3.3.1 Control Field (Ctrl)
Format Commands from Replies from RTU Memory coding MSB

Control Centre (RTU) 7 6 5 4 3 2 1 0
(CC).
"I" Information Information Information NR 1 NS 0
frame
S RR: receive ready RR: receive ready NR P/F 000
"S" Supervision RR: receive not RR: receive ready NR P/F 010 1
frame ready
Not used
Not used
S REJ: frame rejection REJ: frame rejection NR P/F 100
Not used Not used
"U" SNRM: set to 100 1 001 1
normal response
mode
UA: unsequenced 011 1 001 1
acknowledgement
Unsequenced DM: Disconnection DM: Disconnection 000 1 111 1
DIRECTION OF TRANSMISSION: LSB FIRST

4.8.3.3.3.2 Communication Protocol
The protocol is identical to that of the standard C264 HNZ transmission. ELENAS and C264
communicate using the master-slave technique, in which the RTU is always the slave
device.
4.8.3.3.3.3 Messaging
Refer to section 4.8.5 Detailed Messages List for the description of the messaging
From CC to RTU, information I frame includes:
P = 1, I = 0
DLE = $ 10
STX = $ 02
ETX = $ 83
In the address, control and information fields the transparency is made by repeating the
character when it is the same as the control character DLE: the maximum length of the
frame depends of the values of the 3-field characters.
The information field contains one or more message, each one identified by its function
code. The number of information-bearing characters of a message can be constant for a
given function code, or variable.
DLE Start flag

STX
RTU address 1 1 Address field
NR PF NS I Control field
Function code Information field
data’s
DLE END flag

ETX
CRC Frame checking sequence
16
4.8.3.3.4 Error Conditions

Transmission errors are handled by the protocol. It is important to note that the RTU as a
slave does not sense the communications link disconnections - the RTU responds to the MS
when polled, and the polling cycle is set by the MS.
4.8.3.3.5 Standard Compliance
The communication protocol conforms to the EDF HNZ Specification.
4.8.4 Basic Concepts

4.8.4.1 Time Criteria
The time specified in messages consists of the following two items:
• Fraction time (10-ms clock ticks); and
• Time of day.
7 0
Modulus 0-143 (x 10 minutes)
Time of day msb

fraction time 0-59.999 (x 10 milliseconds)
lsb
C0385ENa
NOTE: The date (yy/mm/dd) is not supported in ELENAS messaging.

4.8.4.2 Base Addresses of Transmitted Entities
Entities are transmitted with the following address ranges:
Entity Adress Space types

(hex)
IRS 02 -> 03 Internal RTU Status
ASP 04 -> 1B Analog Setpoints
ARM 20 -> 63 Analog remote
measurements
RCT 64 -> 6F Remote Counters
RC 70 -> 9C Remote Controls
TP A0 -> AF Tape Position Information
RS B0 -> FF Status (DRS & SRS)
4.8.5 Detailed Messages List

4.8.5.1 RS-SC: RS State Change - Source: RTU
7 0
Function code OA hex
Transmission address BO-FF hex
BNB V S 0 C 0 BNB : Bit number in the byte

0-7 for SRSs
0-3 for DRSs
V : Validity
1 = Invalid
S : Status
0 => SRS is 'false' or Reset
0-59.999 (x 10 milliseconds)
=> DRS is 'closed'
1 => SRS is 'true' or Set
=> DRS is 'open'
C : Chronology
1 => Chronology is lost
C0386ENa
NOTE: Unused bits are zeroed.

Complementary default: V=1 S=0 (DRS closed)
DRS invalid: V=1 S=1 (open)
SRS invalid: V=1 S=0 (false or reset)
4.8.5.2 RS-GC: RS General Check - Source: RTU
7 0
Function code 16 hex
See "Field description"

Number of blocks
below
Transmission address of block #1 02-03 hex or BO-FF hex
block #1 SRS byte

S7 S6 S5 S4 S3 S2 S1 S0 S0-S7 = Status*
DRS byte
V3 S3 V2 S2 V1 S1 V0 S0 S0-S3 = Status*
V0-V3 = Status*
* Same as RS-SC
Section 3.10.5.1
block #n
C0387ENa
Field Description:
The validity of SRSs is not transmitted in RS-GC; invalid SRSs are transmitted in INV-SRS-
GC (see Section 3.10.5.3).
Nb of blocks depends on the frame length.
4.8.5.3 INV-SRS-GC: Invalid SRS General Check - Source: RTU
7 0
Same as RS-GC
Number of blocks
Section 3.10.5.2
Transmission address of block #1 B0-FF hex
block #1 S7 S6 S5 S4 S3 S2 S1 S0 S0-S7 = Status*
V7 V6 V5 V4 V3 V2 V1 V0 V0-V7 = Status*
* Same à RS-GC
Section 3.10.5.1
Transmission address of block #n
block #n S7 S6 S5 S4 S3 S2 S1 S0
V7 V6 V5 V4 V3 V2 V1 V0
C0388ENa

4.8.5.4 RC-RQ: RC Request - Source: MS
7 0
Address 0 0 70-9C hex
Nb O C 0 0 0 Nb: RC number 0-7

O C: Open/closed bits
0 = Open
1 = Closed
C0389ENa

4.8.5.5 RC-ACK: RC Acknowledgement - Source: RTU
7 0
Address 0 0 70-9C hex
Nb ACK Nb: RC number 0-7

ACK: RC acknowledge code
01 = positive
> 01: negative, i.e.:
02 = RC is unknown, message is
errored
03 = Invalide function (coupleur fault)
05 = Error during RC execution
07 = RC is being executed
10 = The associated RS is already in
the required state
11 = The S/S or the bay is under local
control
C0390ENa

4.8.5.6 ASP-RQ: ASP Request - Source: MS
7 0
Function code 1A hex
Transmission Address 04-1B hex
Value
8 unsigned bits:
00 hex => Value => FF hex
8 signed bits:
80 hex => Value => 7F hex
C0391ENa
NOTE: Value is scaled by the C264 following the min and max values of the
Setpoint configured in the database
4.8.5.7 ASP-ACK: ASP Acknowledgement - Source: RTU
7 0
Function code 1A hex
Transmission Address 04-1B hex
Value
Same as ASP-RS, Section 3.6
ACK ACK: ASP acknowledge code
01 = positive
02 = wrong message
04 = invalid function (e.g. coupler fault)
C0392ENa
4.8.5.8 GC-RQ: General Check Request - Source: MS
7 0
Code Request:
00 hex = see "Field description"
01 hex = RS-GC
C0393ENa
Field Description:
Initialization GC code: 00 hex
Upon receipt of a GC-RQ command, the RTU shall return:
• RS general checks;
• Routine message (18 hex) with code 0C hex indicating the end of RS GCs (see
Section 3.9);
• RM general checks;
• TP general checks;
• Routine message (18 hex) with code 0E hex indicating the end of RM GCs (see
Section 3.9).
4.8.5.9 ROUT: Routine Message - Source: RTU
7 0
Code Information:
05 hex = Information loss
06 hex = End of chronology loss
07 hex = Start of chronology loss
0C hex = End of RS general checks
0E hex = End of RM general checks
C0394ENa
4.8.5.10 RM-SC: RM State Change - Source: RTU
7 0

Number of blocks
below
Transmission address 20-6F hex
block #1
Value 8 unsigned bits:
00 hex <= Value <= FE hex
FF = Invalid
8 signed bits:
81 hex <= Value <= 7F hex
80 = Invalid
Transmission address
block #n
Value
C0395ENa
Field Description:
For C264 Nb of blocks is always equal to 1 because the RM is configured in event and is
received one by one from the C264 Scada interface
4.8.5.11 RM-GC: RM General Check - Source: RTU
7 0

Number of blocks
below
Transmission address of block #1 20-6F hex
Value 8 unsigned bits:

block #1 00 hex <= Value <= FE hex
FF = Invalid
8 signed bits:
81 hex <= Value <= 7F hex
80 = Invalid
block #n Value
C0396ENa
Field Description:
Nb of blocks depends on the frame length.
NOTE: Upon completion of RM general check transmission, the RTU issues a
routine message with code 0E hex (refer back to Section 3.10.5.9).
4.8.5.12 RMA-OM: Operating Mode of All RMs - Source: MS
7 0
Mode 00 hex = unused,

FF hex = unused,
01-FE hex = End of RM
disabling, dead band value
C0398ENa
Field Description:
Mode 00 hex = Unused;
FF hex = All RMs are disabled;
01 hex = End of disabling; RMs operate in state change mode;
02-FE hex = Unused.
NOTE: After power-on or a Master reset, the RTU is in FF mode. It

automatically switches to 01 once it has replied to a GC-RQ command
from the Master with an End of RM general checks routine message.
4.8.5.13 RMI-OM: Operating Mode of Individual RMs - Source: MS
7 0
Mode 00 hex = unused,

FF hex = unused,
01-FE hex = End of RM
disabling, dead band value
C0398ENa
NOTE: Mode equal to FE hex means 100% dead band.

4.8.5.14 RCT-RQ: Cumulated RCT Report Request - Source: MS
7 0
Number of values 1-12

00 hex = all counters
C0399ENa
4.8.5.15 INV-RCT: Invalid RCT - Source: RTU
7 0
Fraction time 0-59.999 (x 10 milliseconds)
C0400ENa
NOTE: Only if the RCT is invalid. It is a spontaneous message

4.8.5.16 CUM-RCT-RP: Cumulated RCT Report - Source: RTU
7 0
Number of values 1-12 (see note 2)
I 0 b21 I: Invalid condition

block #1 1 = Invalid
Value:
Oldest value Bits b0-b21
Modulus
I 0 b21
block #n
Newest value
C0401ENa
NOTE(S): 1) Unused bits are zeroed

2) The number of values depends on the frame length
e-g: If the frame length is 37, the maximum Nb of values is 8.
4.8.5.17 CUM-RCT: End of Cumulated RCTs - Source: RTU
7 0
Number of RCTs N=1

64-6F hex
Transmission address
address of RCT #1
I 0 b21 I: Invalid condition

1 = Invalid
Value:
Oldest value Bits b0-b21
C0402ENa
NOTE: Unused bits are zeroed. It is a spontaneous message (no request

from the master)
4.8.5.18 TP-SC: TP State Change - Source: RTU
7 0
Function code 0D hex
Transmission address A0-AF hex

V:
V Value 1 = Invalid TPw/
value = 0 (80 hex)
Else, value on 8
signed bits with
value and bit V
C0403ENa
The value + V bit give the transmitted value in à 2’s complement code. It inlcudes the offset,
substracted to the acquired value. For example: TPI with value between 1 to 64, an offset
configured with 32, the values sent into the message will be between E1 hex to 20 hex (-31
to 32)
4.8.5.19 TP-GC: TP General Check - Source: RTU
7 0
See "Field
Number of TPs
Description" below
Transmission address of TP #1 A0-AF hex
block #1 Same as TP-SC
V Value
Section 3.18
Transmission address of last TP

block #n
V Value
C0404ENa
Field Description:
Nb of TPs depends on the frame length.
NOTE: There is no special Request for TP general checks message. TP-GC
is one of the RTU responses upon receipt of a GC-RQ command from
the Master (refer back to Section 3.8).
4.8.5.20 MODULO: Change Time Modulo - Source: RTU
7 0
Function code 0F hex

C0405ENa
Field Description:
MODULO is issued:
• after a RTU reset;

• when the modulo changes and an information with fraction time must be sent.
4.8.5.21 STIME: Set Time Command - Source: MS
7 0
Fraction time 0 to 59.999 (x 10 milliseconds)
00 hex = Every 10 minutes

Code
01 hex = Upon communications
initialisation
02 hex = Upon hour change
C0412ENa
4.8.5.22 STIME-R: Set Time Response - Source: RTU
7 0
Fraction time 0 to 59.999 (x 10 milliseconds)

S
below
C0406ENa
Field Description:
Modulo/Fraction time is the difference called ‘delta’ between the time received from the
Master and the current time in the RTU.
S specifies the delta sign as follows:
• 0 = The RTU internal time is greater than or equal to the time from the Master;
• 1 = The RTU internal time is less than the time from the Master.
4.8.5.23 ID-RQ: Identification Request - Source: MS
7 0
C0407ENa
4.8.5.24 RTU-ID: RTU Identification - Source: RTU
7 0
b7 RTU ID b0
See "Field
b7 b6 b0 Description" below
Version number
C0408ENa
Field Description:
RTU ID is numRcp (number of the remote control protocol for the C264) as defined in the
Databases. It is a 9-bit value, where the ninth bit b7 is the MSB of the version number.
Version number is a 7-bit value specifying the database revision level, as defined in
Database.
4.8.5.25 RTU-INI: Remote RTU Initialization - Source: MS
7 0
C0409ENa
NOTE: Upon receipt of a RTU-INI command, the RTU shall fully reset. There
is no RTU response.
This message builds a send_soft_signal with code COMM_INF_REBOOT_BY_SCADA
which will be recorded in the error log file read by the CAT error folder.
4.8.5.26 REQ-REJ: Request Reject - Source: RTU
7 0
Function code is
Rejected code
unknown
C0410ENa
4.8.6 Startup Sequence

This sequence starts with the establishment of the HNZ connection.
Once the connection is set up, spontaneous messages may be encapsulated into the initial
data stream.
MASTER RTU
SNRM
HNZ connection
UA
GC-RQ
STIME
RTU-ID
RS-GC*
ROUT (End of RS general check)
RM-GC*
TP-GC*
ROUT (End of RM general check)
STIME-R
C0411ENa
The number of GC messages per entity may differ depending on the RTU configuration.
4.8.7 Message Summary

Source: RTU
Function Code Name Description See Section

Hex Decimal
01 01 RM-SC RM State Change 4.8.5.10
02 02 RM-GC RM General Check 4.8.5.11
03 03 CUM-RCT End of Cumulated RCTs 4.8.5.17
04 04 CUM-RCT-RP Cumulated RCT Report 4.8.5.16
05 05 INV-RCT Invalid RCT 4.8.5.15
09 09 RC-ACK RC Acknowledgement 4.8.5.5
0A 10 RS-SC RS State Change 4.8.5.1
0D 13 TP-SC TP State Change 4.8.5.18
0F 15 MODULO Change Time Modulo 4.8.5.20
16 22 RS-GC RS General Check 4.8.5.2
17 23 INV-SRS-GC Invalid SRS General Check 4.8.5.3
18 24 ROUT Routine Message 4.8.5.9
1A 26 ASP-ACK ASP Acknowledgement 4.8.5.7
1D 29 STIME-R Set Time Response 4.8.5.22
20 32 RTU-ID RTU Identification 4.8.5.24
22 34 REQ-REJ Request Reject 4.8.5.26
3D 61 TP-GC TP General Check 4.8.5.19
Source: MS
Function Code Name Description See Section

Hex Decimal
01 01 RMI-OM Operating Mode of Individual RMs 4.8.5.13
02 02 RMA-OM Operating Mode of All RMs 4.8.5.12
04 04 RCT-RQ Cumulated RCT Report Request 4.8.5.14
13 19 GC-RQ General Check Request 4.8.5.8
19 25 RC-RQ RC Request 4.8.5.4
1A 26 ASP-RQ ASP Request 4.8.5.6
1D 29 STIME Set Time Command 4.8.5.21
20 32 ID-RQ RTU Identification Request 4.8.5.23
21 33 RTU-INI Remote RTU Initialization 4.8.5.25
4.8.8 Cable
A specific cable must be used for HNZ Elenas Protocol:
The communication function between a Remote Terminal Unit RTU and the Control Centre
CC is performed by data exchange through one link.
V24 DB25 DB9 DB9 DB25 V24
101 1 1 101
102 7 5 5 7 102
103 2 3 2 3 104
104 3 2 3 2 103
109 8 1 7 4 105
8 5 106
105 4 7 1 8 109
106 5 8
107 6 6 4 20 108
108 20 4 6 6 107
5. IED COMMUNICATION
5.1 Overview
Different types of IEDs are connected to a MiCOM C264 through networks using various
legacy protocols:
1. IEC 60870-5-103 (T103)
2. Modbus
3. DNP3
4. IEC 60870-5-101 (T101)
All these networks use a serial link to communicate with IEDs. As there are several serial
links on a MiCOM C264, it is possible to have:
• Different protocols running in parallel on different links
• The same protocol on several links

All these networks use a Master / Slave protocol where the MiCOM C264 is the Master. So,
there are two kinds of exchange:
• Request / reply
Master emits a request to a slave of its choice and wait for the response. Between
master and slave, only one transaction can be initiated. Then, in order to transmit the
same request to two different slaves, two transactions are required.
• Broadcast
Master transmits a command to all of slaves connected to the network. They perform it
without send any response.
Common features to all IEDs and all protocols are specified below in the paragraph 0
Specific features to each protocol are specified in subsequent paragraphs.
5.2 IED Common functionality
5.2.1 Interface to IEDs
5.2.1.1 Input
Data Note
Digital input Treated
Measurement Treated
Default position Depending on the protocol
Counter Treated
Tap position Treated
Control acknowledgement Treated
Setpoint acknowledgement Treated
Alarm Not Treated
Disturbance record Depending on the protocol
Tunnelling Frame response Depending on the protocol
5.2.1.2 Output
Data Note
Control Treated
Setpoint Depending on the protocol
Alarm acknowledgement Not Treated
Tunnelling Frame question Depending on the protocol
Time synchronisation Treated
5.2.2 Behaviour
5.2.2.1 Network supervision
The number of networks and IEDs is known by configuration.
Each network is managed independently of the other networks.
The management of a network consists of:
• Initialising the serial line

At start-up of the network monitoring, the serial line has to be initialised according to
the configuration.
• Synchronising the IEDs connected to the network.
• Polling the IEDs

This polling allows to connect IEDs, to exchange data with IEDs and to monitor the
connection of IEDs.
• Performing the monitoring of the each IED connected to this network.

Each IED is managed independently of the other IEDs. The state of each IED, i.e.
connected, disconnected, is monitored and every change of state is signalled to the
MiCOM C264 management function.
5.2.2.2 Time synchronisation
If the network has to be synchronised, the synchronisation is performed in one of two ways:
1. At connection of an IED, a synchronisation frame is sent to this IED.
2. Regularly, a synchronisation frame is broadcasted on the network.
When this is supported by the IEDs, the calculation of the transmission delay is performed.
NOTE: The synchronisation is a network attribute [not an IED attribute]. That
means, that the synchronisation is either sent to all the IEDs, or is not
sent.
5.2.2.3 Polling of IED
Once the line is initialised, the MiCOM C264 has to try to connect IEDs and to manage
exchanges of data with each IEDs.
That’s done by polling: cyclically the MiCOM C264 questions each IED one after the other.
The polling manages the following items:
• Sequencing the questioning of the IEDs
• Connection of an IED [when a disconnected IED responds, it becomes Connected]
• Repetitions [if an IED doesn’t answer to a request, this request will be repeated the
next cycle]
• Disconnection of an IED [after N questions without answer, an IED becomes

Disconnected]
• Maximum time to wait for a response

• Minimum time between two frames on the network
• Sending functional requests to IEDs

Optimisation of polling may be done according to the followings ideas:
• When an IED is disconnected, it may be questioned only time to time [not all cycles]
• When an IED has important data to transmit [DI], it may be questioned successively
several times
• The maximum time to wait an answer may be configurable

The polling sequencing may be only stopped in the two following cases:
• Time synchronisation
Synchronisation is done periodically by sending a broadcast frame. After the
synchronisation frame has been sent, the polling starts again.
• Remote control to transmit to a slave

Control is a priority request. So, when a control must be sent to an IED, the polling is
stopped, the control is sent and the polling starts again.
5.2.2.4 Monitoring of an IED
Each IED is managed according to the following graph:
NOT_
INITIALISED
1
DISCON-
2
NECTED
2
1
CONNECTED
NOT_SYNCHRONISED
12
3 4
IN_SERVICE
5 OUT_OF_
GI
SERVICE
6 7
NORMAL
10 8
11 9 DISTUR-
TUNNELING BANCE
C0109ENa
Description of the possible states of an IED:
• NOT_INITIALISED: That’s the initial state of an IED. The MiCOM C264 polls the IED
every cycle in order to connect it.
If the IED responds, it becomes CONNECTED 2 .
If after some attempts the IED doesn’t respond, it becomes DISCONNECTED 1 .
• DISCONNECTED: The IED is disconnected. The MiCOM C264 polls the IED time to
time in order to connect it.
If the IED responds, it becomes CONNECTED 2 .
• CONNECTED: The IED is connected. This state includes several states. When an IED
becomes Connected, it goes to the NOT_SYNCHRONISED state.
• NOT_SYNCHRONISED: The IED has just became Connected. It must be

synchronised. Once it is synchronised, according to the information given by the IED,
it becomes IN_SERVICE 3 or OUT_OF_SERVICE 4 . (This information isn’t
available for some protocols. In this case, the IED becomes IN_SERVICE by default).
• OUT_OF_SERVICE: The IED is connected and says it is Out of service. The MiCOM
C264 polls the IED time to time waiting for the IED to become IN_SERVICE 5 .
• IN_SERVICE: The IED is connected and it says it is In Service. This state includes
several states. When an IED becomes In Service, it goes to the GI state.
• GI: The IED is In Service and a General Interrogation is going on.

For each information received during the GI, the information becomes available and its
state is transmitted to the application [see below for more information on GI
treatment].
At the end of the GI, the IED goes in the NORMAL state 6 .
• NORMAL: The IED is In Service and the monitoring of DI, AO and DO are performed.
If a disturbance record becomes present and the MiCOM C264 have enough places to
store the file, the IED goes in the DISTURBANCE state 8 .
If a request to open a tunnel for the IED arrives, it is accepted and the IED goes in the
TUNNELING state 10 .
Time to Time, a GI may be done. In this case the IED goes in the GI state 7 .
• DISTURBANCE: The IED is In Service and a disturbance record is being uploaded.

When the uploading of the disturbance file is finished, the IED goes back in the
NORMAL state 9 .
• TUNNELING: Tunnelling communication is going on.

When the Tunnelling communication is finished, the IED goes back in the NORMAL
state 9 .
That shows that GI, Disturbance uploading and tunnelling are mutually exclusive. That is
done for 2 reasons:
• To limit the overload of the network
• To suppress interaction between Tunnelling access and MiCOM C264 access.

Description of the transitions between states:
• 0 : Initialisation of the transmission.
• 1 : The IED becomes DISCONNECTED.

The disconnection is signalled to the application.
Every data normally received from the IED is marked as unknown and a change of
state is signalled for each one.
• 2 : The IED becomes CONNECTED.

A synchronisation frame is sent to it and after, the status of the IED is red.
• 3 : The status of the IED is indicates the IED is In Service.

A General Interrogation is activated.
• 4 : The status of the IED is indicates the IED is Out Of Service.
• 5 : see 3
• 6 : The general Interrogation is finished.
• 7 : A general Interrogation is activated [cyclical GI].
• 8 : A disturbance file is available in the IED and there are enough places to store it in
the MiCOM C264.
A disturbance uploading is activated.
• 9 : End of disturbance file upload.
• 10 : A request to open a communication channel throw tunnelling is received.
• 11 : End of tunnelled communication.
• 12 : Request to send a control command to the IED.

The polling is interrupted and the command is sent as soon as possible.
Initialisation procedure
Initially, all data normally received from an IED is marked as unknown. When an IED is first
connected, a general interrogation request is sent. A table is updated with data received in
response to the general interrogation. When the general interrogation is finished, the content
of the table is sent to the processing functions: binary inputs processing and measurement
treatment. Messages received subsequently are checked against the content of the table
and a change of state message is sent when there is a difference.
A general interrogation is performed:
• at initialisation time
• upon reconnection
• Cyclically [optional]
Messages received during the initial general interrogation are not sent to the processing
function. Instead the content of the table is sent at the end of the sequence.
Messages received during a general interrogation performed after the initialisation sequence
are sent immediately to the processing function
Some IEDs send a message indicating the end of the response to a general interrogation.
When this message is received, the sequence is considered as finished. If the IED does not
send this message, the MiCOM C264 must check that all data are received.
If all data are not received within a given time another request is sent. This process can be
repeated N times. If the response is still not received after N times a fault message is sent,
however the IED is still polled.
Disturbance File Management
The following rules apply for the management of the Disturbance Files of the IED:
• For each IED, there is an information in the configuration indicating if automatic upload
of Disturbance File has to be done. This indication may be overwritten by a command
from the application.
• When the MiCOM C264 detects that an IED has a Disturbance File ready to be
uploaded and that automatic upload is enabled, it uploads and stores it. When the
upload is finished, an indication is sent to the Upper transmission management to
inform it that a Disturbance file is ready.
• When there isn’t enough places to store a Disturbance File, the oldest file is deleted.
• The upper transmission management can only get Disturbance files stored in the
MiCOM C264. Once the upper transmission management has treated a file it is
deleted.
5.2.3 Data received from IEDs

After the initialisation sequence, IEDs are polled regularly. Depending on the type of IED the
current state of data can be received as state messages, or as change of state messages.
When a state message is received, the content is checked against the table and if there is a
difference a message is sent to processing functions and the table is updated. In this case,
the MiCOM C264 time stamps the change.
When a change of state message is received, the table is updated and the message is
transmitted to processing functions. In this case, the time stamping is made by the IED.
The data, which can be received from IEDs, are detailed in the paragraphs below.
5.2.3.1 Digital inputs
Digital inputs can be received as states or as changes of state. The choice between state
and change of state depends on the IED and on the protocol. This is known by configuration.
Even if digital inputs are received as change of state, it is still possible to request data as
states for general interrogations.
The conversion from digital input to binary input is performed by the binary input processing
function. A digital input can be associated with a single point or a double point.
Measurements can be received in various formats: float, binary, BCD, etc. The received
value is converted into an internal format, which is common to all measurements in the
MiCOM C264.
Measurements can be received as periodical messages or as changes of state: variation,
threshold, and invalidity.
A message is sent to the processing function whenever a measurement is received from an
IED.
5.2.3.3 Counters
Counters are treated for DNP3.0
5.2.3.4 Tap position
Tap position are treated like measurements
5.2.3.5 Disturbance File
MiCOM C264 stores disturbance files as they are sent by IEDs without control of the format
of the Disturbance Files (Comtrade, …).
5.2.4 Data sent to IEDs
After the initialisation sequence, data can be sent to IEDs. The type of data, which can be
sent to IEDs, is described in subsequent paragraphs.
5.2.4.1 Controls
Controls are priority message. The polling sequence must be interrupted in order to send the
control as soon as possible.
Not all IEDs send control acknowledgement. If they do not, an acknowledgement is
simulated and sent to the handling of control sequences function.
When an IED is disconnected [or out of service] a negative acknowledgement is sent.
If the command is a “select before operate” command, the application must send two
commands to the transmission software: the first one for the selection and the second for the
execution.
If the command is a double command, the application sends one order, and depending on
the protocol, two cases have to be distinguished:
• The Double command is referenced only once in the IED Mapping. In this case, if an
OPEN (respectively CLOSE) command is received from the application, the master
send an OFF (respectively ON) order to the IED at the corresponding address.
• The double command is referenced by two addresses in the IED Mapping: one refers
to the Open Contact and the other to the Close Contact. In this case, if an OPEN
(respectively CLOSE) command is received from the application, the master sends an
ON order to the IED, at the address corresponding to the Open Contact (respectively
Close Contact).
5.2.4.2 Setpoints
SP controls are priority message. The polling sequence must be interrupted in order to send
the SP control as soon as possible.
Not all IEDs send SP control acknowledgement. If they do not, an acknowledgement is
simulated and sent to the handling of SP control sequences function.
When an IED is disconnected [or out of service] a negative acknowledgement is sent.
If the SP commands are always "direct execute" command (no “select before operate”).
For an IED, only one SP command is possible at a time.
5.2.5 Tunnelling
The serial tunnelling enable to connect a lap top computer – which run an IED setting
software – to a serial (RS232) line of the PACiS computer in order to communicate with an
IED connected to a legacy bus of the PACiS computer.
C264
Lap Top IED
Computer
RS232 link Legacy bus

dedicated to (Modbus, T103)
serial tunneling
C0149ENa
All serial RS232 lines of the computer – including the port onto the front panel – can be used
for serial tunnelling.
The choice of the serial line to be used for serial tunnelling is done by the computer
configuration.
The cable dedicated to tunnelling must be disconnected from the front panel when
tunnelling is not used.
5.2.5.1 Interface through the tunnelling serial line
The tunnelling serial line gives access to a user dialog.
This dialog enables an user to give commands to the Tunnelling RS232 software.
Commands are ASCII string terminated by ‘↵’ (code ASCII 13H) and are case sensitive.
A command is executed at the reception of the ‘↵’ character. An ASCII message is sent in
response, and a prompt message may be sent in order to indicate the computer is ready to
treat a new command.
If a command is unknown, an error message “Unknown command !” is sent.
List of the available commands:
• TunRSLines↵: List the legacy lines for which tunnelling is enabled.

Each line of the list corresponds to a legacy line for which tunnelling is enabled and have the
following format :
Line <line Number> : <Protocol>
If there is not any legacy line available for Tunnelling, the response is “No line available for
serial tunnelling.”
• TunRSIed nl↵: List the IED of a legacy line and their state [ln = line number].
The first line of the response gives information on the line :
Line <line Number> : <Protocol>
Each following line of the response corresponds to an IED and have the following format :
IED <Address> : <State>
Where <State> can be “available” or “not available”
If the line isn’t available for Tunnelling, the response is “The line nl is not available for serial
tunnelling.”
• TunRSStart ln, ad↵: Start a serial tunnelling session with the specified legacy line
[ln = legacy line number; ad = IED address].
The response is either “Serial Tunnelling started” or an error message explaining why the
command can’t be executed.
If the response is “Serial Tunnelling started”, legacy frames are awaited on the serial
Tunnelling link.
• TunRSStop↵: Stop the current serial tunnelling session.

The response is “Serial Tunnelling stopped”.
5.2.5.2 C264 Behaviour
Once the “TunRSStart” is accepted, the computer waits for Legacy frames on the serial
Tunnelling line.
Received frames are sent to the target legacy IED.
Response frames coming from the IED are sent back on the serial Tunnelling line.
If a tunnelling session is already running, the current session is ended and a new one is
started.
5.2.5.3 Procedure of use of the serial tunnelling
• Connect a LapTop to the computer with an RS232 serial cable

(On the computer, the cable is connected to the serial line dedicated to the tunnelling)
• Launch Hyperterminal on the LapTop
• Enter the serial tunnelling starting command [“TunRSStart”]

The computer answers “Serial Tunnelling started”.
• Quit Hyperterminal (be sure to close the connection)
• Launch an IED setting Software [e.g. : MiCOM S1] on the LapTop
• Execute settings actions with the setting Software (that implies exchange of legacy
frames between the setting software and the IED through the computer)
• Quit the setting Software
• Launch Hyperterminal on the LapTop

• Enter the serial tunnelling stopping command [“TunRSStop”]

The computer answers “Serial Tunnelling stopped”.
• Quit Hyperterminal (be sure to close the connection)

5.2.5.4 End of a serial tunnelling session
As described above, a serial tunnelling session may be ended by the “TunRSStop”
command.
If the user forgets to end the tunnelling session with the “TunRSStop” command, the session
will be automatically ended after expiry of a deadline - of about 2 minutes - without
exchange.
5.2.5.5 Fault case behaviours
• If the questioned IED does not answer, no frame of answer is returned to the setting
Software.
• If the setting software sends a new question frame [or repeats the last frame] whereas
the computer is still awaiting the answer from the IED, this new frame is ignored.
5.2.5.6 Serial tunnelling through a modem
Modem Lap Top
C264
Modem IED
Computer
Specialised
or RTC line RS232 link
Legacy bus
dedicated to serial
(Modbus,
tunneling
T103)
C0150ENa
If modems are well configured, this operating mode is transparent for the computer and no
specific management is needed in the software.
5.2.5.7 Tunnelling limits and specifications
The legacy protocols supported – protocols for which serial tunnelling is available – include:
• MODBUS
• T103
The line to be used for serial tunnelling can be set through computer configuration.
If the serial tunnelling line is “frontal RS232”, it is automatically configured to:
19200 Bd, 8 bits data, no parity, 1 stop bit.
For the other ports (COM1 to COM4), it follows the configuration parameters.
Only RS232 mode is supported.
5.2.6 Limits and specifications
• The number of serial links available limits the number of legacy network that can be
managed simultaneously by a MiCOM C264.
• The maximum number of IED that can be managed for a network is 16.
• Specifications depend on the used protocol and on the number of IEDs connected to
each network.
5.3 MODBUS communication

5.3.1 Scope of this section
MODBUS is a legacy bus master/slave protocol that is used by many devices such as
relays, computers or monitoring devices. The aim of this chapter is not to describe the
protocol itself and its mechanisms, but to describe the functions implemented in MiCOM
C264:
• available function numbers
• the way in which each type of data is internally or externally updated
• general mechanisms used for the synchronisation

The protocol is implemented in various ways:
• Generic: this implementation allows connecting most types of IED to a MODBUS

network
• Schneider Electric: this implementation is based on the Schneider Electric rules

(M300, Px2 series, Px4x series)
• Specific for one relay: M230, Rish Pro M10, ABB-Flexgate, Sepam 40 and 80, WAGO
5.3.2 Generic MODBUS Communication
The generic communication is the common base to most of the IEDs. The following
MODBUS functions are implemented in MiCOM C264:
Function
Sub-code Used to Details
No.
1–2 / Read DIs Read N bits
3–4 / Read AIs /DIs Read N words
5 / Write DO Write 1 bit
15 / Write DOs Write N bits
Restriction: write DOs after one another
7 / Poll status Read status byte
Used to detect a DI change of state
8 0 Poll presence Echo
Alternative to detect if a device is
connected or not
6 / tunnelling if Write 1 word
needed
16 / tunnelling if Write N words
needed
The disturbance files are not treated. The function 7 cannot be used fully or at all with a
number of IEDs (e.g.Rish Pro M10, Flexgate); they require a specific treatment.
5.3.2.1 Polling and connection test
All the slaves are polled after one another. This means that C264 waits for the answer to
each polling request sent to a device before sending a new request to the same or another
device.
There are 2 types of polling:
• the polling for the measurements and the digital inputs (functions 1 thru 4) or the byte
status (function 7)
• the polling for IEDs presence (low level polling)

If an IED does not correctly answer after a user-configurable timeout, C264 repeats the request.
If the IED does not correctly answer after a defined number of retries, it is considered as
disconnected. This status is updated by low-frequency polling.
Depending on configuration, C264 tests the connections with:
• function 7
• functions 1 thru 4 (DIs)
• functions 3 thru 4 (AIs)
• function 8 (mirror frame)

or uses a user-defined frame.
5.3.2.2 Data received from IEDs
5.3.2.2.1 AIs
C264 polls the AIs at a defined frequency.
A block of measurements is a set of measurements mapped at consecutive addresses. As a
result, all of them are read in one exchange.
C264 supports 18 formats of Analogue Inputs:
Format Description Comment

INT8_LB Signed integer on 8 bits Modbus does not provide a
‘Read byte’ function. So, a ‘Read
INT8_HB word’ function is used.
UINT8_LB Unsigned integer on 8 bits LB and HB indicate which byte in
UINT8_HB the word is used (respectively,
Low/High)
INT16 Signed integer on 16 bits
UINT16 Unsigned integer on 16 bits
INT32_LW_LB Signed integer on 32 bits
INT32_LW_HB
INT32_HW_LB
The first pair of letters indicates
INT32_HW_HB which word is sent first: the lower
UINT32_LW_LB Unsigned integer on 32 bits word (LW) or the higher word
(HW).
UINT32_LW_HB
UINT32_HW_LB
The second pair of letters
UINT32_HW_HB indicates which byte is sent first
in a word: the lower byte (LB) or
REAL32_LW_LB Float IEEE754 on 32 bits
the higher byte.
REAL32_LW_HB
REAL32_HW_LB
REAL32_HW_HB
5.3.2.2.2 DIs
A block of DIs is a set of DIs mapped at consecutive addresses. As a result, all of them are
read in one exchange.
By default, the function 1-2 polls for DI blocks. C264 compares each DI state with the latest
state and time stamps the potential change of state.
5.3.2.3 Data sent to IEDs

5.3.2.3.1 Connection check
Generic IEDs
Each device on the network is regularly polled with a specific frame to know if it is connected
or not. This frame could be the status byte polling frame if it exists, the measurement polling
frame if it exists, the BI polling frame if it exists, the mirror frame if it has been implemented
in the device or a user defined frame. This choice is performed through the configuration
options.
MiCOM IEDs
The “Read status byte” frame is used for checking the connection of the device.
5.3.2.3.2 Clock synchronisation
All the devices connected to a given network must use the same synchronisation method
(and the same address and time-date format) because C264 synchronises them through a
broadcast frame.
Synchronisation is not specified generically and no calculation of the transmission delay is
performed.
5.3.2.3.3 DOs
Commands are sent to the IED and have the highest priority level.
They have to be transmitted to the destination device as fast as possible.
C264 waits for an acknowledgement (answer of the IED).
If the acknowledgement is not received after a defined timeout, C264 considers that the
command has not been taken into account.
5.3.2.4 Error management
The MODBUS protocol handles a mechanism of exception answer. This means that an IED
answers with an exception frame if it does not understand the request. There are different
exception codes:
Exception code Description C264 processing

01 Illegal function Reports a "Configuration error” and continue
02 Illegal data Reports a “Configuration error” message and
address continues
03 Illegal data value Reports a “Configuration error” message and
continues
04 Slave device Reports an “IED error” message
failure
05 IED busy due to a Retries after a defined time-out
long processing
duration
06 IED busy Retries after a defined time-out
07 Processing not Reports an “IED error”
possible
08 IED memory parity Reports an “IED error”
error
5.3.2.5 Limits and specifications

The specifications depend a lot on the number of devices connected on the network. It is
advised to connect devices that have similar specifications on a given network, i.e. the same
reply time for instance.
Each device on a MODBUS network must have the same synchronisation mode.
5.3.3 Schneider Electric MODBUS COMMUNICATION

Three ranges comply with the Schneider Electric rules:
• M300: Energy analyzer and measurement central unit

• Px2x: MICOM S20
• Px4x: MICOM S40
Function No. Sub-code Used to Details

1–2 / Read DIs Read N bits
3–4 / Read AIs /DIs Read N words
5 / Write DO Write 1 bit
15 / Write DOs Write N bits
Restriction: write DOs after one another
7 / Poll status Read status byte.
Used to detect a DI change of state and
the presence of disturbance files
8 0 Poll presence Echo
Alternative to detect if a device is
connected or not
6 / tunnelling if Write 1 word
needed
16 / tunnelling if Write N words
needed
5.3.3.1 Status byte

The connection is tested using the function 7.
Bit Description Detail Event

No generated
b0 General state of the device 1 = active, 0 = not active Yes
b1 Presence of a minor failure 1 = present / 0 = absent Yes
(*)
b2 Presence of a not 1 = present / 0 = absent No
acknowledged time-
stamped event
b3 State of synchronisation 1= synchronised, 0= out of Yes
(**) synchronisation
Compatible with relays OPN7000,
MODN
b4 Presence of a not 1= present, 0 = absent Yes on Set
extracted Disturbance
Compatible with relays OPN7000,
record
MODN
b5 Presence of a not 1 = present / 0 = absent Yes on Set
extracted Fault record
b6 Trip Alarm Set 1= a trip has occurred, not No
acknowledged
b7 Alarm Set 1= at least one alarm bit in the No
front panel alarm cell not
acknowledged
If a bit of this status has no significance for the equipment, this bit is fixed to 0.
Any change of state generates an event. Except for b2 set/reset, b4 and b5 reset, b6 and b7
set/reset.
* Indicates a device failure («SRAM Failure»…) and generates an event.
** 0 indicates that synchronisation was not received or not understood since 1 min,
according to protection criteria (by MODBUS or IRIG-B synchronism). This rule covers
potential drift of 10 ms of non synchronised device. “Loss of synchronisation” has a
major impact in all events treatment. All the events coming from a device that has lost its
synchronisation need special treatment in substation chronological list of events. This
particular event helps determine also any network disconnection in the device history.
5.3.3.1.1 Events buffer management
The IEDs store the events, Fault Records, Disturbance files in a circular buffer of various
sizes.
When C264 acknowledges an event, a FREC or Disturbance file, the IED clears the memory
for future events, FREC …
When all events, FREC, DR have been cleared from buffer, the corresponding bit is reset in
the status byte without generating any event.
If a device is disconnected, the buffering function saves all of history. If one of its buffers gets
filled up then the IED:
• generates an event to inform that this buffer is full,
• erases the oldest event if the queue is full
• sends a saturation reset event when the buffer is not full any more.
• replaces the oldest data in the full buffer by the newest ones (event, FREC,
Disturbance file).
5.3.3.1.2 M300
The bits have other meanings:
• Bit 0: Availability of a Disturbance record [0 = not available; 1= available]
• Bit 4: 0 = active; 1 = inactive
• Bit 5: 1 = Presence of Event
• Bit 6: 1 = Presence of Alarm.

5.3.3.1.3 MiCOM S40 (Px4x series)

The status can be read with function 3 or 4 in register 3x00001 (@ 0).
The table that follows shows this 16-bit status:
Bit
Value/bit mask Meaning Conform
No
0 0x0001 Presence Status (1 = present / 0 = mute) OK
Minor Self Test Failure (1 = Failure / 0 = No
1 0x0002 OK
failure)
New event available
2 0x0004 OK
(1 = Available / 0 = Not Available)
Clock synchronization (=1 after Modbus sync.
3 0x0008 Resets to 0 after 5 minutes unless it is synced OK
again. Other time sources do not affect this bit)
New auto extraction disturbance record available
4 0x0010 OK
(1 = Available / 0 = Not available)
5 0x0020 Fault (Not used - always 0). NOK
6 0x0040 Trip LED status (1 = LED on, 0 = LED off) -
Alarm status summary
7 0x0080 -
(logical OR of all alarm status bits)
8 0x0100 Unused -
9 0x0200 Unused -
10 0x0400 Unused -
11 0x0800 Unused -
12 0x1000 Unused -
13 0x2000 Unused -
14 0x4000 Unused -
15 0x8000 Unused -
Even if the access function (3 or 4 instead of 7) does not comply with the internal MODBUS
rules, the events can still be managed, as far as the bits 2 and 3 are compliant with them.
5.3.3.2 Data received from IEDs

5.3.3.2.1 AIs
The formats supported by C264 include:
• IEEE STD 754 (recommended)
• integer signed or not on 1 Byte
• integer signed or not on 2 Bytes
• integer signed or not on 4 Bytes (for energy metering precision)

It is desirable that all the AIs have the same format (type and byte number); otherwise, divide
them in several groups, each with a given format.
The values must be directly usable. Single scaling (e.g. x1000) is accepted. As complex
computation use boundary, scaling is forbidden for measurements.
AIs are mapped at consecutive MODBUS addresses to increase the acquisition efficiency.
Or, they can be in a fundamental data area.
The transmission of the measurements in double word must start with the most significant
byte, which is not a common practice:
Bytes order
Intel products 1 2 3 4
Motorola products 4 3 2 1
Most common (2 consecutive addresses) 2 1 4 3
Recommended transmission with MODBUS 4 3 2 1
The units of the readings must be identical throughout a range of products. If possible stick
to the list of the recommended units. The format for encoding IEEE makes unit coding easy,
as it makes possible to treat at system level the large or small values without using derived
units (example: tenths of Amperes, tens of Volts, MW).
Description Units
Volts V
Amperes A
Kilowatt kW
Kilo Volt Ampere kVA
Kilo VAR kVAR
Kilo Watt . Hour kWh
Kilo Volt Ampere Hour kVAh
Kilo VAR Hour kVARh
Hertz Hz
Celsius or centigrade Degree °C
Mho 1/Ω
Ohms Ω
Seconds of closing time s
Degree of angle Angular degree
Without unit –
For all the quality descriptors used for the measurements or counters, split quality descriptor
indication (like CP8(i+1) Info + Quality from IEC 870-5-4) from the value in separate address
groups.
Some IEDs encode Valid/Invalid quality statuses with binary values. For such IED, map the
AI Statuses in consecutive words.
5.3.3.2.2 M300
The measurements are periodically polled for. The available formats include:
Format to configure Comments

T1 UINT16 (5) 16 bit unsigned value: "12345" (0x3039) represents 12345
T3 UINT16 (5) 16 bit unsigned value with 2 decimals: "12345" (0x3039)
represents 123,45
T8 INT16 (4) 16 bit signed value with 3 decimals: "-12345" (0xCFC6)
represents -12,345
T9 UINT32_HW_HB (13) 32 bit signed value: “big Endian” *
T10 UINT32_HW_HB (13) 32 bit signed value with 2 decimals: “big Endian”*
T20 Energy: T09 for the primary values (base unit kWh),T11 for the secondary
(base unit Wh)
T21 Power: T10 for the primary values (base unit kW),T12 for the secondary values
(base unit W)
T39 Voltage: T10 for the primary values (base unit V),T11 for the secondary values
(base unit V)
T40 Current: T10 for the primary values (base unit A), T13 for the secondary values
(base unit A)
T53 Idem T1
* the higher word is transmitted first, the higher byte in the word is transmitted first
These formats do not take into account the multiplying factor. Moreover, the next table gives
a non exhaustive list of measurements (in secondary mode):
Scalin
Meas. C264 type g Address Formats
factor
Va UINT32_HW_HB 0.001 0x01C6 T39 (=T11 for the secondary mode)
Vb UINT32_HW_HB 0.001 0x01C8 T39 (=T11 for the secondary mode)
Vc UINT32_HW_HB 0.001 0x01CA T39 (=T11 for the secondary mode)
Uab UINT32_HW_HB 0.001 0x01CC T39 (=T11 for the secondary mode)
Ubc UINT32_HW_HB 0.001 0x01CE T39 (=T11 for the secondary mode)
Uca UINT32_HW_HB 0.001 0x01D0 T39 (=T11 for the secondary mode)
Ia UINT32_HW_HB 0.0001 0x01D2 T40 (=T12 for the secondary mode,
mistaken as T11 in the manual R8605C2)
Ib UINT32_HW_HB 0.0001 0x01D4 T40 (=T12 for the secondary mode,
Ic UINT32_HW_HB 0.0001 0x01D6 T40 (=T12 for the secondary mode,
In UINT32_HW_HB 0.0001 0x01D8 T40 (=T12 for the secondary mode,
Freq. UINT32_HW_HB 0.001 0x01DA T11
Scalin
Meas. C264 type g Address Formats
factor
Power UINT32_HW_HB 0.0001 T21 (=T12 for the secondary mode,
Energies UINT32_HW_HB 0.001 T20 (=T11 for the secondary mode)
The addresses 0x01DB, 0x01DC, 0x01DE and 0x01DF generate an exception frame with
code number 2.
5.3.3.2.3 MiCOM Px2 series and Px4 series
Measurements are read through the Modbus functions 3 or 4 (read word functions). Select
the correct format for the measurement: 16 or 32 bits.
Notice that the lower word of 32 bit values is generally transmitted first and, in each word,
the higher byte is transmitted first (use formats such as YYYY32_LW_HB for 32 bit values).
• Basic Address (Mapping address) 0xyyyyy
• Extra Address 1: not used
• Extra Address 2: Modbus function (3 or 4)
• Extra Address 3: not used
• Format: See table

5.3.3.2.4 DIs
5.3.3.2.4.1 IED synchronised
Same as generic Modbus (block mode)
5.3.3.2.4.2 IED NOT synchronised
The status byte is regularly polled at low level and compared with the latest one. The status
byte in an Schneider Electric IED contains the indication that at least one DI change has
occurred.
If a change is detected, C264 reads the event queue inside the IED, checks out which data
have changed, checks if the data have been configured and reads the information itself.
In this case, the DI changes are time-stamped in the IED and C264 downloads their date
and time.
Any DI change generates an event. For any event, there is a DI address that can be
retrieved.
All the DIs have two states (0/1, on/off, open/closed, synchronised/out of synchronisation).
Each DI generates 2 events (Reset to 0 at this time, Set to 1 at that time).
The DIs are stored at consecutive addresses. In consequence, all the DIs can be read in
only one request (except if the number of DIs exceeds the capacity of a MODBUS message,
and except may be for fast status word).
DIs at connection
At connection or periodically, C264 can fetch the global states of one device in a single
message. Automation can start at once as it is based on states. Event reading can be
delayed due to the need to get the disconnection history and time stamp the current state.
A transient DI is in fact an event not associated to a real state but to a transition (e.g. Trip
order). It is only SET never RESET. The practice shows that state approach is more
commonly used than the transition approach and help know the global status at connection.
For this purpose, a transient DI like the trip order is held for a configurable time (300ms), and
results in 2 events (set and reset). The IED translates an inner transient DI to a pulsed
indication over the network (with a configurable time e.g. 100 to 300ms).
M300 read request

The time-stamped events of the M300 are NOT treated (there is no indication on the state of
synchronisation of the M300). In consequence, the C264 acquires the DIs of the M300 by
polling and time stamps them.
The DIs are read through the Modbus function 4 (read words) with the values that follow:
• mapping address in the basic address field
• 4 in the extra address 2 field
• bit number in the extra address 1 field

Example for reading the 2 DIs of an M300 device:
• BI0:
− Base address: 28d
− Extra address 1: 0
− Extra address 3: /
• BI1:
− Basic address: 28d
1
Example for reading alarm status of an M300 device (@30030):
• BI16:
− Extra address 1: 0 “Error EEPROM: alarm group 4”
• BI17:
• BI23:
− Extra address 1: 7 “serial port default Analogue output”
• BI0:
− Extra address 1: 0 “Test timeout for watchdog”
• BI1:
• BI15:
− Extra address 1: 15 “Error EEPROM: alarm group 3”
To read bit fields in 32-bit values, configure at least one BI in each part of the long value
(lower word and higher word) as described in the previous example.
MiCOM Px2 series and Px4 series read request
C264 acquires the DIs through the function Nr 3 or 4 (read word functions).
− Base Address (Mapping Address) 0x0010
− Extra Address 1 (bit Number) 0
− Extra Address 2 (Modbus function) 4
− Extra Address 3 (Not Used) X

To improve the process, the events are handled in C264. This means that each action on the
relay activates an event that is uploaded and decoded in the relay. If the DI corresponding to
the event has been configured, C264 reports the new DI value.
5.3.3.2.5 Disturbance files
The disturbance record includes any transfer of file of measurements sampled at high
frequency:
• conventional disturbance
• monitoring data (pressure in GIS, harmonics, brush distance in CB closing ..)

Such a file is breakdown into limited size blocks (defined by MODBUS) to be uploaded.
Any file data format can be used as far as it can be converted to a standard file format,
COMTRAD or at least CSV format (Excel, Matlab…).
Regardless of the kind of transmission, a header must define the kind of data transfer (file or
column values) and the required file reader. The name of the exploitation files (usually
COMTRAD) is based on the configured device, master reference, IED MODBUS reference,
and cyclic disturbance number.
C264 is informed that a disturbance is stored by reading the bit b4 in the Status byte. Each
block is transmitted on the C264 request. At the global end of transfer, after a check-up of
the file, C264 sends the “Ack.DO” and the device can erase its disturbance file. If another
“disturbance file” is still present, the bit b4 remains set (e.g. EPAC multi disturbance upload).
The date in disturbance file must be the same as in events (for trip indication…). The device
is compliant with:
• the file upload mechanism (Stream of data)
• the disturbance upload mechanism (Column of values); example: series P20

COMMENT IED NET MASTER
TRIP-storage disturb
Disturbance ready Poll status

Bit Disturbance ready
=>Disturbance available
Option Poll disturbance address

Option => Patrimoin ask
Option
Option @Disturb Word
@First Pack Page
@Last Pack Page
Number Channel/Pack
Option => Disturb. Addresses
Select Channel Select Channel/Pack

First non ack disturbance
=> channel selected
Prepare Block
Answer channel info

=>Get Channel data
Data upload Poll PACK

(PACK = Value column or
Poll Block
(Block 250 words) => read block
Answer Data Block => get block
=>until last Block
Repeat Next PACK

Until last PACK
Poll Index
First disturbance acknowledge => read index
Disturb READED => get index, time, no error
CHECK VALIDITY
Acknowledge Disturbance Send DO ACK

DO ACK
Disturb read
Erase disturb file
Change index disturb
Refresh bit disturb
5.3.3.2.5.1 M300
There are 2 types of Disturbance record:
• Waveform Analysis Record (max = 1 file)
• Disturbance Record (max = 4 files)

The detection of the availability of a disturbance record in the M300 is done by regularly
polling the status of the M300 (bit “Presence of a Disturbance record”).
The disturbance record of an IED is uploaded only if the maximum number of simultaneous
disturbance uploading is not reached for the Modbus line and the opening of a disturbance
file on the computer is possible.
Uploading
C264 opens a file to store disturbance data. If it is not possible, the treatment ends.
The type of disturbance record to upload is selected by writing to register @40567 (0x0237):
• ‘0’ for a Waveform Analysis
• ‘1’ for a Disturbance Record

The record number is selected by writing to register@40568 (0x0238) the value ‘0’ in order
to select the last one.
C264 reads the general information and writes the information that follows to the file:
• Serial number of the IED [8 words at @30001 (0x0001)]
• Frequency [@40572 (0x023C)]
• Trigger date [@30055 (0x0037) @30060 (0x003C)]
• Available channels [@30061 (0x003D)]
• Type of channels [@30062 (0x003E)]
• Number of samples by channel [@30063 (0x003F)]
• Number of pages [of sample] by channel [@30064 (0x0040)]
• Number of samples by cycle [@40560 (0x0230)]
• Trigger position [@30066 (0x0042)]
• Time base [@30067 (0x0043)]
• Scaling factors of analogue channels [@30068 (0x0044) @30081 (0x0044)]
• Names of analogue channels
• Names of TOR channels

The disturbance data are uploaded channel by channel, starting with channel ‘0’ which is the
time channel, and for each channel, page by page.
At last, C264 closes the disturbance file.
The bit 7 of register @40047 allows to erase ALL the disturbance records.
For mapping information, refer to the Service manual volume 2, ref. R8605C2.
5.3.3.2.5.2 MiCOM Px4 series
No disturbance files.
5.3.3.2.5.3 MiCOM Px2 series

The Px2x can store up to five Disturbance records. The number of channels depends on the
kind of Px2x (6 thru 9).
C264 detects the presence of a disturbance record in the Px2x by regularly polling for the
status of the Px2x (bit “Presence of a Disturbance record”).
Uploading
C264:
1. Opens a file to store disturbance data; if this is not possible, the treatment ends
2. Reads the number of Disturbance records and the associated information (Read of 36
words at @0x3D00); this information enables to know the number (between 0 and 4)
of the latest unacknowledged disturbance records. If there is no unacknowledged
disturbance record, the treatment ends
3. Reads all the IED identification model based on the pattern “Px2x” in order to
determine the number of channels and the selection size (Read of 5 words at
@0x0000) and after, it writes this information to the disturbance file
4. Uploads the disturbance data channel by channel, and for each channel page by
page.
5. Reads the index frame of the disturbance (Read 7 words at @ 0x2200) and writes this
information to the disturbance file
6. Closes the disturbances file
7. Acknowledges the disturbance records in the Px2x by setting the bit @0x4032 to 1;
another disturbance record can be uploaded from the IED
Differences between Px2x Models:
selection
Overall information
Number of analogue Number of TOR
Products channels size
channels channels
number Pages 0x38-
0x3C
P120 No disturbance management
5 ( IA, IB, IC, I0, 1 (3 Inputs,
P122 6 11 Words
Frequency) 7 Outputs)
P123 6 11 Words
P124D 6 11 Words
P124S No disturbance management
6 (IA, IB, IC, I0, V, 1 (7 Inputs,
P126 7 19 Words
8 (IA, IB, IC, I0, VA, VB, 1 (7 Inputs,
P127 9 19 Words
VC, Frequency) 9 Outputs)
1 (5 Inputs,
P220 5 (IA, IB, IC, I0, Frequency) 6 11 Words
6 Outputs)
6 (IA, IB, IC, I0, UAC, 1 (6 Inputs,
P225 7 19 Words
6 (IA, IB, IC, I0, UAC, 1 (6 Inputs,
P226C 7 19 Words
selection
Overall information
Number of analogue Number of TOR
Products channels size
channels channels
number Pages 0x38-
0x3C
2 (5 Inputs,
P521 7 ( IA, IB, IC, I0, timing) 9 Outputs, 9 11 Words
9 internal data)
1 (5 Inputs,
P922 5 ( Voltage, Frequency) 6 19 Words
9 Outputs)
1 (5 Inputs,
P923 5 (Voltage, Frequency) 6 19 Words
9 Outputs)
Modbus
@ Mapping Words Format Description
Function
Pages 0x09 thru 0x21: Disturbance Data. Each page contains the samples [250 data word]
of the selected channel
0x0900 3 250 Up to 250 samples
0x09FA
0x0A00 3 250
INT16 Up to 250 samples
0x0AFA
0x2100 3 250
Up to 250 samples
0x21FA
Page 0x22 : Index of the Disturbance
0x2200 3 1 UINT16 Disturbance record Number
0x2201 4 Time
3 Disturbance record finish date
0x2204 Stamp
1 Disturbance record starting
0x2205 3 UINT16
condition
0x2206 3 1 UINT16 Frequency at post-time beginning
Modbus
@ Mapping Words Format Description
Function
Page 0x3D : Number of disturbance records available
UINT16 Number of disturbance records [1
0x3D00 3 1
.. 5]
0x3D01 3 1 Oldest disturbance record (n)

0x3D02 Time
3 4 disturbance record Date
0x3D05 Stamp
0x3D06 3 1 disturbance record starting origin
0 Not Acknowledged
0x3D07 3 1
1 1 Acknowledged
Preceding disturbance record
0x3D08 3 1
(n+1)
0x3D09 Time
0x3D0C Stamp
0x3D0D 3 1 disturbance record starting origin
0 Not Acknowledged
0x3D0E 3 1
1 1 Acknowledged
….
Preceding disturbance record
0x3D1D 3 1
(n+4)
0x3D1E Time
0x3D21 Stamp
0x3D22 3 1 disturbance record starting origin
0 Not Acknowledged
0x3D23 3 1
1 1 Acknowledged
Pages 0x38 thru 0x3C: Selection of the Disturbance and channel [Each page correspond to
one out of the 5 Disturbance records]. The second header line is the number of words
uploaded for each access reading:
P122/P123/
@map Modbus Words P124D/P220 P126 P127 P225/P226C P521 P922/P923
-ping function number
11 words 19 words 11 words 19 words
Pages 0x38 thru 0x3C: selection of the Disturbance and channel [Each page correspond to 1 of the 5
Disturbance record]
0x..00 3 1 Ia Ia Ia Ia Ia Ua
0x..01 3 1 Ib Ib Ib Ib Ib Ub
0x..02 3 1 Ic Ic Ic Ic Ic Uc
0x..03 3 1 Io Io Io Io Io Vo
0x..04 3 1 Frequency reserved Ua Frequency Timing Frequency
0x..05 3 1 TOR reserved Ub TOR TOR1 TOR
0x..06 3 1 Uo Uc/Uo Uac TOR2
0x..07 3 1 unavailable frequency frequency unavailable unavailable unavailable
0x..08 3 1 TOR TOR
For each register read request, the following information is uploaded. This information
describes the selected channel:
P122/P123/ P225 /
Word P126 P127 P521 P922/P923
P124D/P220 P226C
0 Total samples number
1 Sample number in pre-time
2 Sample number in post-time
3 Primary phase CT ratio
4 Secondary phase CT ratio
5 Earth primary CT ratio
6 Earth secondary CT Ratio
7 Phase internal CT ratio
8 Earth internal CT Ratio
Last page Last Primary phase VT
9 Reserved Primary phase VT Ratio [LB]
Number page nb Ratio [LB]
Last page word Last pg Primary phaseVT
10 Reserved Primary phaseVT Ratio [HB]
number word nb Ratio [HB]
Secondary phase VT
11 Reserved Secondary phase VT ratio
ratio
Earth primary VT
12 Earth primary VT ratio [LB] Reserved
ratio [LB]
Earth primary VT
13 Earth primary VT ratio [HB] Reserved
Un- ratio [HB]
available
Earth secondary VT
14 Earth secondary VT ratio Reserved
unavailable ratio
Internal VT ratio–
15 Internal VT ratio – numerator 100
num. 100
Internal VT Ratio –
16 Internal VT Ratio – denominator
denom.
17 Last page Number Last page Number
Last page words
18 Last page words number
number
Specific treatments
P126: the channels are not consecutive; the 5th & 6th channels must be skipped.
P127: the mapping address 0x0127 must be read. It gives the voltage wiring of the IED. This
value must be written in the file (but it doesn’t change the uploading process).
P922 &P923: the mapping address 0x0126 must be read. It gives the voltage wiring of the
IED. This value must be written in the file. This value changes the uploading process: in
some cases, the channels must be skipped.
Wiring Voltage wiring of the IED Used channels

value
0 3Vpn (3 phase-to-neutral voltages) 0 Ua
1 Ub
2 Uc
3 Not used
4 Frequency
5 TOR
1 3Vpn + Vr (3 phase-to-neutral voltages + residual 0 Ua
voltage)
1 Ub
2 Uc
3 Vo
4 Frequency
5 TOR
2 2Vpp + Vr (2 phase-to-phase voltages + residual 0 Uab
voltage)
1 Ubc
2 Not used
3 Vo
4 Frequency
5 TOR
3 3Vpp + Vr (3 phase-to-phase voltages + residual 0 Uab
voltage)
1 Ubc
2 Uca
3 Vo
4 Frequency
5 TOR
5.3.3.2.6 Events
An event is a time-stamped change of state of a logical data.
When the IED gets connected, C264 reads the current status of logical information, then
manages the status changes from the file of the time-stamped events.
The time-stamped events are gathered in one file. The bit b2 of the status indicates the
presence of at least one event not extracted. Events are stored by IED, and are read one by
one by the master, starting from the oldest event.
C264 reading of one event does not withdraw it from the file. An IED withdraws an event
from its list:
• when C264 acknowledges it
• when the file of the events gets saturated (the queue sheds the oldest event)
• directly after C264 reading if automatic event retrieval is set on IED. The event can be
read again at address @event +1 (3601h if the latest event address is 3600h). Event
reply is 0 if the events list is empty.
• C264 reads one event, and then sends “DO ok“ if it correctly receives the event. When
receiving this acknowledgement, the IED deletes its latest event, and updates its
events list (and resets the event bit in status word if applicable: refer to IED
documentation). This makes sure that no event is lost. DO acknowledgement is bit 13
(0400h).
• IED and C264 are configured for automatic event retrieval (at start-up C264 checks
the bit b12 at 0400h). C264 reads the latest event.
The IED shifts this event to the next address in the event list. If C264 detects a
transmission error, it reads again the event at address +1.
Any event includes the information that follows:
• Date - Time, using inverse order as per IEC 870-5-4 CP56T2a format (no short format,
no CP16, same format as clock synchronisation).
• MODBUS mapping address of logical information that has changed.
• New state value of the transmitted data (new value of the word, stored at the
MODBUS mapping address).
C264 extracts the events meant for upper functions and sends them to the corresponding
service: automation, alarms, textual message converter, event & logging printing….).
Note: all textual information associated to events are not needed by a system master as
customers have their own labels, wording, or writing (Cyrillic, Cantonese …). A separate
device is in charge of textual logging. The text only reduces communication bandwidth.
C264 can manage several changes of state in one event (for changes in same time accuracy
period, to increase transfer…), even if each event has only one change of state. Then, one
change of state is linked to one event and one event is linked to several possible changes of
state (if they are at the same MODBUS address).
MiCOM Px4 series
The command register can be written with Modbus function 6 in register 4x00400 [@ 399].
Each action is activated when a ‘1’ is written to the corresponding bit.
Bit No. Value / bit mask Used to

0 0x0001 Select the next event
1 0x0002 Accept event
2 0x0004 Select the next disturbance record
3 0x0008 Accept disturbance record
4 0x0010 Select the next disturbance record page
x x Other bits are unused
Automatic event-record extraction allows records to be extracted as they occur. Event

records are extracted in sequential order:
Start
Function 4
@0
Read Status register (3x00001) Timer Nb word 1
Analyse Event Flag (bit 2)
No
Event flag set ?
Yes
Function 6
Select next Event @399
(Write 1 in register 4x00400) Value 1
Read the Event Function 4

(Read 10 registers from 3x10103) @102
Analyse Event Flag (bit 2) Nb word 10
AnalyseEvent
Analyse the Event
Flag Type
(bit 2)
Yes
Event type = 255 ?
No
Function 6
o
Acknowledge the Event @399
(write 2 in register 4x00400) Value 2
No
0 ≤ Event type ≤ 6
Yes Only Event type 0 thru

6 included are treated.
Treat the Event
C0446ENa
C264 determines whether the Px4x has any events stored that have not yet been extracted
by reading the Px4x’s status register 3x00001 (G26 data type). If the event bit is set, the
Px4x contains event records that have not yet been extracted.
To select the next event for sequential extraction, C264 writes 1 to the command register
4x00400 (G18 data type). The event data together with any fault/maintenance data can be
read from the registers as specified in the flow chart and table.
Once the data has been read, the event record can be marked as read by writing 2 to
register 4x00400.
Alternatively, since the G18 data type consists of bit fields, it is possible to both marks the
current record as having been read and to automatically select the next unread record by
writing 3 to the register.
When the latest (most recent) record has been accepted, the event flag in the status register
(3x00001) is reset.
If the latest record was accepted by writing 3 to the command register (4x00400), a dummy
record appears in the event record registers, with an “Event Type” value of 255.
Attempting to select another record, when none are available results in a Modbus exception
code 3 – “Invalid value”.
Event formats:
Modbus Register Contents Description Nb

/Address Registe
r
3x00103…3x00106 (G12) IEC870 Time & Date 4
Time stamp
102 … 105
of the event
3x00107 (G13) 0,1,2, 3 alarm 1
Event type
106 4 output contact
5 opto input
6 protection
255 dummy event
3x00108…3x00109 (G27) New values of the 32 bits register containing 2
Event value the BI(s) which have changed.
107 ... 108
3x00110 (G1) Modbus address of the 32-bit register 1
32-bit containing the BI(s) that have changed.
109
Register
CAUTION: real Modbus address must be
reference
recomputed by subtracting 30001 !!!
Event Event index
type
0,1,2,3 11
4 723
5 725
6 727 thru 785 (associated DDB
status register)
3x00111 Event Index Event Event index 1
type
110
0,1,2,3 Alarm ID
4, 5 Not used – set to 0
6 bit 16 = state, bits 1-15 DDB ID
3x00112 Not used by – 1
C264
According to the Event Type, the Event Index can be used – or not – to analyses the Event.
Two cases have to be considered:
• Event of type 0,1,2,3 and 6. In this case, the Event Index can be used.
− Bit16 of the Event Index indicates the new Digital Input state (0 or 1)
− Bit1-15 of the Event Index [modulo 32] indicate the Bit Number of the Digital Input
in the 32bits register
− The 32bits register reference and the Digital Input Bit Number allows finding the
Digital Input in the C264 DB (if configured).
• Event of type 4 and 5. In this case, the Event Index is not significant and can't be
used. The C264 DB has to be parsed against the Event Value, looking for a change of
state of all Digital Input of the 32-bit register reference.
5.3.3.2.7 File upload

A file is defined by a header, a parameter set and a stream of data. Each time C264 reads a
block of data, the IED shifts data to the next page (Repeat page) and replaces it by a new
block of data. In event of transmission error, C264 requests the block wrongly received to the
repeat page.
Addresses Function Contents

FA00 to FAFA Read 24 words Read header
FB00 to FBFA Read N words Read N words of file parameters and shift parameter
stream
FC00 to FCFA Read N words Read N words again of file (repeat)
FD00 to FDFA Read N words Read N words of file data and shift data stream
FE00 to FEFA Read N words Read N words again of file (repeat)
The header defines data to transmit and file treatment to trigger by C264 on data reception:
Word Description Format

1 Kind of file transfer 0 for the following mechanism, 1 for a future one
2-3 Number of words in parameter Nb_Byte_Para
field
4-5 Number of words in data field Nb_Byte_Data
6 Manufacturer 1 « Schneider Electric » (for M7xx)
7-8 Product reference 4 ASCII {« M710 », « M711 » , « M720 »,
« M721 »… }
9 Transmission product version 1 First version or A
10-13 Product serial number 8 ASCII characters:
SS Week
AA Year
NNNN Number in week (shift left + blank).
14 Kind of File transfer used below 0 very short time
by the product
1 short time
2 quality events
3 disturbance
4 compressed disturbance
15-18 First element time tag IEC 840-5-4 ( 64 bits = 4 x 16-bit words )
19 Reserved e.g. sampling, trigger 0x0000
timer
… … …
24 Reserved 0x0000
All the data samplings are transmitted after one another without compression.
Word Description for decoding software

0-1 First value of first sampling
2-3 Second value of first sampling
Nb_Byte_Data Last word

Algorithm:
COMMENT IED NET MASTER
TRIP-storage disturb
Disturbance ready Poll status

Bit Disturbance ready
=>Disturbance available
Poll File header

=> Patrimoin ask
Read header @Disturb Word

@First Pack Page
@Last Pack Page
Size of
Option => Disturb. Addresses
Read conversion parameter Read file parameters

Transmission parameter
Answer parameter
Block size =>Get data transmission
Number of blocks parameter
Data upload Number of Block-1

(PACK = Value column or
Poll Data Block @D
(Block parameter 250 words) => read block
Answer Data Block => get block
=>until last Block
CHECK VALIDITY
Acknowledge Disturbance Send DO ACK

- DO ACK
- Disturb read
Erase disturb file
Change index disturb
Refresh bit disturb
Downloading is done using function 15 or 16 at specific address. Acceptance is signalled.

To speed up the global downloading, writing can be done to several consecutive addresses.
5.3.3.3 Data sent to IEDs

5.3.3.3.1 Clock synchronization
Type of synchronization: Schneider Electric
All the devices connected to a given network must have the same synchronization procedure
(address and time and date format) because the synchronization order is broadcast.
Date and time comply with the inverted IEC 870-5-4 CP56Time2a format:
Word 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
1 0 0 0 0 0 0 0 0 0 Year: 00…99
2 0 0 0 0 Month: 1...12 DayOfWeek:1..7 DayOfMonth:1..31
3 su 0 0 Hour: 0…23 iv 0 Minutes: 0…59
4 Milliseconds (High) Milliseconds (Low)
Su (=0 for Standard, =1 for Summer Time)
iv (=0 for valid, =1 for non valid or out of synchronisation for a system)
First day of the week: Monday
Date and time is set at address 0800h with function 16. No calculation of transmission delay.
If an IED does not have (this) synchronisation, it must be unaware of these synchronisation
messages (no error indication, no failure).
If an IED that does not stick to the rule, C264 supplies out-of-synchronisation devices with its
own time stamp. The time accuracy is deeply degraded.
An IED does not generate any event when receiving the synchronisation, or when missing
one broadcast message.
Synchronisation comes from a specialised clock device like GPS. The first bit is the
reference. C264 transmits time corrected by its treatment delay. It sends a synchronic
message periodically (e.g. 3 times per minutes). The absence of reception within 1 minute
results in a “Loss of synchronisation” event.
A “Loss of synchronisation” event requires a set/reset. Synchronisation information is also
signalled by the IV bit in the event time stamp: 0 means that when the event occurred, the
IED was out of synchronisation.
Any IED with 2 clocks systems (MODBUS synchronization mechanism AND an IRIG B or
other) must have an inner setting to deactivate each clock.
If C264 has lost its own synchronisation, it still time stamps events (but with IV bit set) to still
synchronise the IEDs with a same reference (relative time tagging).
M300
The M300 supports 2 time formats:
• The Schneider Electric synchronization format, which is used only to set the Date &
Time
• The M300 format which is used to set the Date & Time in the M300 or for time
stamping in the M300 (e.g. Disturbance time stamping)
The synchronisation according to the Modbus Schneider Electric rules is accepted by the
M300 only if the bit “summer” is NOT set.
MiCOM Px2 series
The Px2x support 2 time formats:
• the Schneider Electric synchronization format, which is used only to set the Date &
Time in the Px2x
• the Px2x format which is used for time stamping in the Px2x (e.g. Event & Disturbance
time stamping)
Time stamping format:
Word Description
0 Lower word of Seconds
1 Higher word of Seconds
2 Lower word of MilliSeconds
3 Higher word of MilliSeconds
The number of seconds given in the previous table (32-bit value in word 0 and 1) is the
number of seconds elapsed since 1994 January 1st.
Since the V4C version of the PX2X relays, a private format and the IEC format are both
available. Select the IEC format to obtain a correct event decoding.
Moreover, a PX2X relay goes out of synchronization after a 1 min delay. As a result, select a
synchronization period lesser than 60 seconds.
MiCOM Px4 series
The Px4x support the Schneider Electric format. To keep the Px4x synchronized, C264
sends a synchronization frame at least once every 5 minutes.
It is possible to use both Px2x and Px4x relays on the same communication channel and to
activate the synchronization.
The register 4x00306 is used to configure the time format managed by the relay:
• Writing value '0' in this register selects the 'standard IEC' time format (default value).
• Writing value '1' in this register selects the 'reverse IEC' time format (Modbus
Schneider Electric time format used by C264).
So, at Px4x connection, value "1" must be written in register @305 [4x00306] to signal the
Px4x to use the Schneider Electric time format.
If the 'Modbus Schneider Electric format' is selected (see above), the time tag format in
events is as show below:
Word No. Byte No. Data (MSB first) Mask

0 0 Dummy byte (set to 0) 0x00
1 Years 0x7F
1 2 Month 0x0F
3 Day of week / Day of Month 0xE0, 0x1F
2 4 Summertime / Hours 0x80, 0x1F
5 Validity / Minutes 0x80, 0x3F
3 6 Milliseconds MSB 0xFF
7 Milliseconds LSB 0xFF
5.3.3.3.2 Commands
Any control sent from C264 to an IED is called a Digital Output:
• Logical control: DO to acknowledge a Disturbance record, a time stamped event, DO

to activate or inhibit a specific protective function.
• Physical control: DO to open or close a feeder circuit breaker, or specific output.
To simplify Master MODBUS configuration and run time, it is desirable to gather controls at
consecutive addresses.
Communication DOs or controls are transmitted by Modbus writing functions:
• function 5 (write 1 bit)
• function 6 (write 1 word)
• function 15 (write N bits)

If the function 6 or 15 are used, the word of control must be formatted in fields of bits.
The DO used to acknowledge reception of dated events must always be accepted by the
IED, even if it is in local mode (no protection mode filtering on this particular DO).
For a single control on a bits field, there is no special need or common description of
“Control accepted”. The DI changes subsequent to a control action are sufficient to control
execution.
For other controls, reserve a special word on IED for all the device acknowledgements.
If there are several devices on IED, a more elaborate control message sequence between
C264 & IED are required. For a control message, keep the Modbus acknowledgement rules.
On reception of a control request, an IED sends 0 (OK) if function/address/data are correct.
If its inner algorithm forbids it to initiate ordered sequence with physical Digital Output
(because of interlock, locking, running control, invalid position…), the IED transmits an
“application” error code via an event DI configured in C264. C264 determines if the
sequence is acceptable, and runs correctly (for higher control algorithm or protocol
conversion).
When operating control is implemented on IED (OBS, Cx2x, P4xx) a lot of failure cases are
defined, and over several plants.
At least use for each controlled plant only one word (4 control bits set by C264 and reset by
IED, and 12 main informative bits). Extra words can be defined for further automation
indication.
Case 1: Switching device may need to be split into synchronised CB and disconnections:
CONTROL * MONITORING
Control Plant State Plant secondary DI
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 0 0 Plant position MOTION
0 0 1 Plant position OPEN
0 1 0 Plant position CLOSE
0 1 1 Error!
1 0 0 Plant
positionINVALID(DBI00)
1 1 1 PlantpositionINVALID(DBI11)
1 0 1 Other INVALID (polarity…)
1 1 0 Reserve other INVALID
0/1 (opt) Plant
inLOCAL/REMOTE
0/1 (opt) Plant LOCKED
(WITHDRAW)
0/1 (opt) DI select in SBO
0/1 (opt) Synchro-check OK
1 Control Fail Abnormal
termination
1 Control Fail mismatch plant
position
1 Control Fail Lock
(pressure…)
1 Control Fail Interlock
1 Control accepted Latch (any
control)
0 0 1 OPEN control
0 1 0 CLOSE control
1 0 0 (opt) CLOSE2 control
(Forced)
1 (opt) SELECT control
* All DOs latched by C264, the front panel cell is reset at the sequence end by IED
Case 2: Transformer with TPI position on other word
CONTROL MONITORING
ControlPlant St Plant secondary DI
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0/1 Plant position MOTION / FIXE
0/1 Mini CB OPEN/CLOSE
1 Plant position INVALID
0/1 (opt) AVRegulation ON/OFF
0/1 (opt) Plant LOCKED
x Reserve
1 Low Tap Reach
1 High Tap Reach
1 Control Fail Abnormal termination
1 Control Fail Lock (oil,..)
1 Control Fail Interlock (unusual)
1 Control accepted Latch (any
control)
0 0 1 Tap RAISE control
0 1 0 Tap CLOSE control
1 0 0 (opt)Regulation ON Control
1 (opt) Regulation OFF Control
* All DOs latched by C264, the front panel cell is reset at the sequence end by IED
Several kinds of control are defined to manage any measurement that can be frozen
(Maintenance counter, metering, or classical measurement). The following “control structure”
byte can be used for each measurement:
CONTROL MONITORING
7 6 5 4 3 2 1 0
0/1 AI Valid/Invalid
0/1 AI not Frozen/Frozen
x Reserve Topical, saturated…
x Reserve
1 Unitary reset
1 Unitary reset & start
1 Unitary restart
1 Unitary freeze
Any IED has kind of alarm management that deeply differs from the one used at system or
SCADA level. An alarm is any indication given to an operator to warn against a non standard
condition, usually by LED indications on IED (2 states ON/OFF), alarm list at upper level
(with 4 states defined by STANDING/RESET, NOT_ACK/ACKNOWLEDGE).
It is asked that IED alarms indication be accessed in one address. A DO can globally
acknowledge/reset alarms (but one alarm is maintained if condition is still present). In the cell
words, a first byte is dedicated to indicating alarm, a byte+8 to resetting each alarm.
M300
There is one command register in the M300 [@40047 (0x002F)]. This register is set using
the function 6. Each bit of the register corresponds to a different command:
Basic Address (Mapping Address) 0x002F
Extra Address 1 (bit Number) Bit number to write
Extra Address 2 (Modbus function) 6
Extra Address 3 (Not Used) x
MiCOM Px2 series
There are 3 command registers in the Px2x [@0x0400, @0x0402, 0x0403]. This register is
set using the function 5, 6 or 15. Each bit of the register corresponds to a different command:
@ Mot @Bit Usable Function Comment

0x0400 0x4000 0x400F 5, 6, 15 Remote control Word N° 1
Configuration using function 5 of the bit4 [Remote closing] of register 0x0400:
• Basic Address (Mapping Address) 0x4003
• Extra Address 1 (bit Number) X
• Extra Address 2 (Modbus function) 5
• Extra Address 3 (Not Used) X
Configuration using function 6 of the bit4 of register 0x0402:
• Basic Address (Mapping Address) 0x0402
• Extra Address 1 (bit Number) 4
• Extra Address 2 (Modbus function) 6
• Extra Address 3 (Not Used) X
Special commands used by the computer:
@Bit Comment
Set in order to switch to manual acknowledgement mode for Event and
0x400C
Disturbance uploading
0x400D Set in order to acknowledge the latest Event
0x4032 Set in order to acknowledge the latest uploaded Disturbance
MiCOM Px4 series

No specific treatment.
5.3.3.3.3 AOs
The analogue control or AO or Set point, or control reference is a value transmitted by C264
to device using the function 6 or 16. They can be used to define a reference (for physical
output in regulation scheme, generator…) or to define a protection parameter (threshold…).
The values to write must comply with formats and units described for Analogues Inputs
(IEEE signed 754, Integer / not signed on 1/2/4 bytes).
When several values at consecutive addresses can be written, IED must support writing to
this block of addresses.
5.3.3.3.4 Settings of the current relays
In order to parameterize the remote relays, a setting software is necessary.
The tool is Modbus connected on the rear (as commonly used by system in run time).
A front connection with the same software and same framing protocol at both customer
validation and after sale phase is recommended.
Setting software requirements:
• Interface with at least a DLL for Emission / Acceptance of messages developed by the
supervisor system, in order to use the tool with other link than serial port. Modbus
messages are encapsulated by system sub-station protocol to be used in system
architecture.
• Possibility of inhibiting some options of the menu (pooling, disturbance upload …).
• Complete management of the function by the application (Timer on failure to reply,

causes of failure…).
• Off-line setting before download
• In run-time the Modbus master is the only master. The tool should not disturb the
standard polling of events and data.
5.3.3.3.5 Error management
5.3.3.3.5.1 Faults records
The processing of recommended Fault records is as follows:
• Creation of a zone dedicated to describing Fault, apart from the Fault proper
• Sorting of information according to the type of data.

The Fault Record has the same Modbus address for a whole range of products – that
means, for all the IEDs in the series the same address for the latest not acknowledged fault.
A good practice is to have the same address for all MiCOM products (e.g. 0x003E for not
acknowledged FREC).
To access to the Fault Record, use the functions 3 or 4.
5.3.3.3.5.2 Alarms
Most IED LEDs can be configured for alarms. In most cases they are managed in a two-state
way that differs a lot from an IED to another or to the system (5 states).
An alarm is a standard event (time-stamped change of state managed by event rules),
stored in the IED till acknowledgement, and that aims at warning the operator via a LED.
There are 2 kinds of alarm:
• TRIP (signalling that a control is sent to a breaker when a particular protective function
is triggered)
• ALARM (other information intended for the operator)

Each alarm/trip indication is controlled by a bit in a set of consecutive cells (like Digital
Inputs). Each bit retains that alarm condition has been set (even if the condition is no more
fulfilled). A global Digital Output acknowledgement ‘Alarm/trip’ is used to reset all alarm
indications. If one alarm condition is still fulfilled, the corresponding bit is not changed by the
IED, else it is reset (with an event generation).
When at least one alarm is set in alarm cells (single alarm appearance), the bit 7 of fast
status byte is set.
When at least one Trip function is set in trip cells, the bit 6 of fast status byte is set.
Each bit is reset when all the alarm/trip appearance conditions have disappeared and a
global ACK alarm Digital Output is received.
A global ALARM/TRIP_ACK_DO is mapped (reset bit). IED mapping must explicitly give the
list of cells/bits indicating alarm/trip and effect on bits b6 and b7.
The answer to global ALARM_ACK_DO or global TRIP_ACK_DO (if applicable) to C264 can
never be BUSY (no applicative mechanism, only transport error code).
The bits b6 and b7 are directly linked to LEDs on the front face. The rule manages only 2
states for LED ON or OFF, and no third state is managed. The state ON can be fixed or
blinking. The current mechanism is a global acknowledgement AND clearance of alarm list if
the alarm appearance condition has been reset.
5.3.3.3.6 Limits and specifications
It is mandatory that within the same range, each piece of equipment has the same operation
as others:
• Management of events file (event format/file address/address of acknowledgement

DO).
• Management of Fault records (fault format, base fault addresses, address descriptive
zone, address of acknowledgement DO…).
• DIs, DOs, AIs are grouped at identical base addresses.
• Format of AI.
• Format of Status.
• Address range of the fundamental data.

In order to use information coming from IED in fast automation, or to answer to the SCADA
inquiries, or in alarm tagging, the following specifications are recommended:
• Operating time, answering time to the various requests < 20 ms.
• Low-level address filtering of the irrelevant requests.
• Respect of MODBUS protocol control (correct CRC, parity check, separate message
silence of 3.5-char time, continuous flow in one message i.e. a silence limited to 1.5-
char transmission time).
• Speed of communication: at least 19200 bauds (38400 is usual, 128000 is a future

standard).
• If it is overbooked, a device must answer BUSY (exception code 06) or at least not
answer (it is reputed disconnected to be reconnected).
• An IED must answer with a delay lesser than 20ms.
• An IED can ask to implement a FAR BUSY (code 05) to solve an SRAM access
problem. C264 repeats the request at N times its polling period. After 10 BUSY
answers, the IED is disconnected.
The official number of devices on Modbus is 32, 16 on PSCN3020 and future system.
Typically the application engineers must not include more 8 IEDs to comply with common
customer needs (triggered analogues < 500ms, triggered DI < 100ms, physical ping as
control/Digital Output/bi-stable/Digital Input/alarm < 300ms, network avalanche profiles, …).
5.3.4 IED SPECIFIC MODBUS

Summary:
IED Read Extra Synchroni DI AI Command Tunneling Setting

status functions z. s software
4, address 1, – – 6 new – Set & read ISDP
M230
length 3 formats
RishM10 – – not specified Generic Generic Generic –
Flexgate x Flexgate Generic Generic Generic
SEPAM x Sepam Generic Generic Generic SFT
WAGO x – Generic Generic SP: 15 bits
No disturbance files.
5.3.4.1 M230
In addition to the generic Modbus, to test IED communication, the function code 4, address
1, length 3 can be used.
5.3.4.1.1 Data received from M230
No DIs.
Analogue Inputs are regularly polled.
C264 supports six 32-bit extra formats of Analogue Inputs:
Format Value Bit 31 thru 24 Bit 23 thru 16 Bit 15 thru 00
M230_T5_TYPE decimal
Unsigned.meas exponent Binary value unsigned
(signed)
M230_T6_TYPE decimal
Signed meas. exponent Binary value unsigned
(signed)
Signed:
M230_T7_TYPE signed: Import/ Inductive/ Unsigned value (16
Power factor
Export (00/FF) capacitive bytes)
(00/FF)
ION_MODULUS_
Reg. High: unsigned Reg. Low: unsigned
10000_UNSIGNE 10000RH+RL
value/10000 value modulus 10000
D
ION_MODULUS_ Reg. Low: signed
10000RH+RL Reg. High: signed value/10000
10000_SIGNED value modulus 10000
KITZ202_K8 Refer to KITZ202 documentation
The byte transmission order is: 4-3-2-1.

5.3.4.1.2 Data sent to M230
The M230 is NOT synchronized using Modbus.
Setting software: IDSP application can NOT be used to set Date and Time, only the front
panel can.
The M230 does NOT process the commands.
The M230 can be set using C264 Tunneling mode. IDSP application M230 setting software
can be used through tunneling mode to set or read data.
5.3.4.2 Rish Pro M01

5.3.4.2.1 Initialization sequence
To establish a communication with the relay (at C264 start-up), C264 reads registers 202,
221, 222 (table of measurements) and registers 300 thru 392 (scaling factors table).This
initialization sequence is done after each disconnection (i.e. loss of communication or
communication error with the IED).
Without interruption:
Step C264 Rish Pro M01

State Request Frame State
1 connection
2 read "table of
measurements"
3 measurements
4 read "scaling factors table"
5 Wait TimeOut
5bis error
5ter Stand by
go to 2
6 end Time Out
7 Writes general status RUNNING
8 Stand by
Timeout Ready
Disconnection:
State Request Frame State

5 Wait TimeOut
6 disconnection
7 Stand by
8 Writes general status DCNX
5.3.4.2.2 Polling
The beginning of Digital Inputs and Analogue Inputs polling is delayed by a time-out starting
at the end of the Rish Pro M01 initialization. C264 can send a synchronous frame during the
initialization phase. Depending on the function and the read use in this frame, the M01
answers with a correct frame or an exception frame but does not invalidate the initialization.

The Rish Pro M01 has no register to read status value and the function 7 is not supported.
So, to detect a problem, C264 uses the exception codes sent by the Rish Pro M01. Rish Pro
M01 generates the error codes that follow:
Code Description
01h Unsupported function code
02h Invalid memory register address: use of invalid register number or attempt to write
to a memory protected register
03h Invalid data, i.e. an invalid number of registers
06h Device is busy. This code signals that the relay is occupied with functions
performed via the local RS232 interface (changing configuration, simulation or
calibration of analogue outputs..)
0Ah Possible change of rated values. The device configuration has been modified since
the latest request for measurements or this is the first request for measurements
since the relay was switched on. Read the table of measurements and the scaling
factors table.
Error code 06h and 0Ah must be treated as a disconnection of the IED and a new
initialization phase must be completed before reading the Rish Pro M01 data. Other codes
can be treated as usually.
Only errors from initialization sequence or polling DIs and AIs report an error code. Errors
from synchronous frame only generate an error message, but do not cause a new
initialization sequence.
At reception of the message error code 0x6h or 0xAh, if the mode polling is active,
reauthorize future polling. The IED general status goes to INIT and C264 goes to state
"STAND BY" and extracts the event "RISHM01 CNX".
In event of trouble, the IED sends the Modbus exception 'Busy'. The C264 considers the IED
as disconnected (that will force the initialization sequence to be redone) but DOES NOT PUT
the IED information to unknown.
5.3.4.3 Flexgate
5.3.4.3.1 Polling
At C264 start-up, a polling request is sent to determine the status (function 7). A response
means that the Flexgate IED is connected.
No Digital Inputs polling: a DI change is signaled by an event.
C264 polls for fields ‘Internal status bits’ at address 18993 to 19000 with function 2:
Fields Address Description

Events pending bit 18993 Is there a new event ?
Time is not sent from Modbus master within last 18994 Is Flexgate IED
16 minutes synchronized with C264 ?
Time is not synchronized by minute pulse within 18995 Not used
last 1.5 min
5.3.4.3.2 Other data received from Flexgate

If an event is received (flag at Modbus address 18993), C264 reads the events queue.
To read the events, C264 realize an alternative reading between addresses 39001 and
39011, which allows reading next event.
If C264 reads the same address – without any other request in between – it gives the same
event.
The Flexgate sends a response on six words. Refer to the converter documentation.
C264 continues to read the event file until there is no new event. Then, it polls for the
‘Internal status bits’.
Sequence numbers
In the event response, the sequence number is between 1 and 65535.
Reserved numbers:
• 0 indicates that there is no event anymore
• 1 indicates that the converter (Flexgate) has been reinitialized
• 50 indicates the re-initialization of the converter (Flexgate)
• 51 indicates an overflow events buffer. The event buffer size is 200. The Flexgate
does not allow to add new events until the event 51 is read. At this time, C264
considers that one or more events have been lost. Then it repeats the General
Interrogation, and the cycle continues starting with the internal status bits polling.
If a gap appears in the sequence number, C264 considers that an event has been lost. Then
it repeats the General Interrogation; the cycle continues polling the internal status bits.
5.3.4.3.3 Data sent to Flexgate
C264 sends Date and Time in one request with function 16 at Modbus addresses
49001…49007 (2328h to 232Eh).
The following format is used to write the date: [year/month/day/hour/minutes/milliseconds
since midnight] to two words by data except for milliseconds which takes four words.
C264 periodically sends the date to synchronize the Flexgate. The time must be sent with a
period smaller than 16 minutes.
As they are sent to a specific address, there can be only one Flexgate on the legacy bus.
Flexgate generates the error code that follows:
Code Description
03h Illegal data value, i.e. invalid number of register (send a
“Configuration error” message to the application and continue). Also
used to indicate a hardware malfunction like an interlock condition
not ok on a protective relay
5.3.4.4 SEPAM
As for standard Modbus, three modes are available:
• ‘General Interrogation’: C264 waits for the end of initialization, the disappearance of
data loss signal. Then, it polls for all the DIs.
• 'Desynchronized': events are NOT managed. The DIs are updated by polling. DIs are
read and decoded group by group. The status is read and decoded when all the
groups have been read.
• 'Synchronized': events are managed. C264 reads the status word, then the events.
The DIs are updated when the events are decoded.
5.3.4.4.1 Data received from Sepam

DIs
• Modes GI and ‘not synchronized’:
1. C264 reads DI group with function 3 at address that follow:
Mode Address Sepam 40 Address Sepam 80

GI 0x100 thru 0x10A 0xC10 thru 0xC16
‘not synchronized’ 0x100 thru 0x10A 0xC90 thru 0xC9F
2. When it receives a data, it decodes the status frame and the DI group frame.
• Mode ‘synchronized’:
1. C264 reads the status frame (function 7) till it detects a data

2. it checks event and reads the event table using function 3 at address 0x40 with size
33.
3. it decodes the event frame and acknowledges using function 6 at address 0x40 with
value ‘ExchangeNumber’ at 0.
5.3.4.4.2 Data sent to Sepam
Date and time format: [Day/month/Year Hour.Min:Ms] [14/5/38 6.43:16785] for the 38th year
since 1970 (ie. 2008), the 14th May at 6 hours 43 minutes and 16785 milliseconds.
Address for synchronization: 0x0002.
5.3.4.5 WAGO
The Wago relay behaves generically except for the setpoints that are integers not signed on
15 bits.
5.4 DNP 3.0 Communication

The purpose of this chapter is not to describe the DNP3 protocol but to specify the use of the
DNP3 protocol on a legacy bus of the MiCOM C264.
As the MiCOM C264 is the master on the legacy bus - regards to protections and IEDs - this
protocol is referenced as “Master DNP3” in the MiCOM C264.
Here are described:
• Specific behaviours attached to the protocol DNP3
• Restriction and enhancement
• Part of the DNP3 protocol used and not used

5.4.2.1 Input
Object Variation Data GI Polling Function

01 0 Static BI (SPS) ♦ [1] READ
02 0 BI Event (SPS) ♦ [1] READ
20 0 Static Counter ♦ [1] READ
22 0 Counter Event ♦ [1] READ
30 0 Static Measurement ♦ [1] READ
32 0 Measurement Event ♦ [1] READ
60 01 Class 0 ♦ [1] READ
60 02, 03, 04 Class 1,2,3 ♦ [1] READ
NOTE: BI, Measurement and Counter are polled with the variation 0. That means
that all variations are required.
All other DNP3 objects are not treated.
5.4.2.2 Output
Object Variation Data Function Note

12 01 Command: Control [3] SELECT Treated
Relay Output Block
[4] OPERATE Treated
[5] DIRECT OPERATE Treated
50 01 Time and Date [2] WRITE Treated
The DNP3 Master manages both direct control Command and Select before Operate for
digital control only.
When operate command is received from application, the Master checks in database to
know if the command is:
1. An execute command, which belongs to a SBO Control: OPERATE function is used in
this case.
2. A direct control: DIRECT OPERATE function is used is this case
5.4.3 Behaviour
• Synchronisation:
− The “Master DNP3” is always synchronised by the MiCOM C264. No calculation of

the transmission delay is performed.
− The DNP3 object used to synchronise IEDs is “Write Date and Time Request
(Object 50, Variation 01).
− Synchronisation is performed first at connection of an IED.
− Then, synchronisation is sent cyclically to all the IEDs.
• Initialisation:
− To connect an IED, a “Reset CU” (function 0) frame is sent to the IED.
− When the response is OK, the Master DNP3 send a message to the application to
tell that connection step is passed.
− Next step is General Interrogation
• General Interrogation:
− When the IED is connected, the MiCOM C264 ask for static data state and value with
a sequence of:
− Read BI,
− Read Measurement,
− Read TPI,
− Read Counter
− This Sequence is the General Interrogation. Next step is Polling
• Polling:
− The polling cycle depends on the configuration:
− class 0 only: the CURRENT value of a BI, measurement, or counter, …. is polled

for. The GI polling period is configurable using the “class 0 polling period”
configuration parameter; when this parameter is set to 0 second, there is no cyclic
GI.
− Poll Class 0 or Class 1 or Class 2 or Class 3: this is a poll for all EVENT data
followed in return by all (static) current data.
− The polling cycle must be interrupted at minimum in the two following case:
− Clock Synchronisation
− Remote control
• Event acquisition:
− Event occurs spontaneously. The slave device waits for being polled by the master.
With unsolicited reporting, Slave devices can send updates as values change, without
having to wait for a poll from the Master.
• IED monitoring:
− A General Interrogation may be done after connection of an IED

• Digital inputs:
− A DI is identified by an Index, associated to a couple “Object + Variation” which

identify the type of data.
− Digital inputs which are received as changes of state are identified by the DNP3
object number 02
− Digital inputs which are received as static data are identified by the DNP3 object
number 01
• Measurements:
− A Measurement is identified by an Index, associated to a couple “Object +

Variation” which identify the type of data.
− Both analogue and numeric measurements are treated
− Measurements which are received as changes of state are identified by the DNP3
object number 32
− Measurements which are received as static data are identified by the DNP3 object
number 30
• Counters:
− A Counter is identified by an Index, associated to a couple “Object + Variation”

which identify the type of data.
− Counters which are received as changes of state are identified by the DNP3
object number 22
− Counters which are received as static data are identified by the DNP3 object
number 20
• Controls:
− A Control is identified by an Index, associated to a couple “Object + Variation”

which identify the type of data.
− In case of basic control (Set, Reset, Trip, Close), DNP3 object 12 is used with the
Variation 01
5.4.6 Master DNP3.0 Profile
Vendor Name: Schneider Electric

Device Name: PACIS Computer
Highest DNP Level Supported : Device Function :
For Requests Level 3 Master Slave
For Responses Level 3
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels
supported :
______________________________________________________________________________
______________________________________________________________________________
Maximum Data Link Frame Size (octets) : Maximum Application Fragment Size (octets):
Transmitted 292 Transmitted 2048
(configurable: 15 to 2048 octects)
Received: (must be 292) Received 2048
Maximum Data Link Re-tries: Maximum Application Layer Re-tries:
None None
Fixed at ______________________ Configurable, range ____ to _____
Configurable, range 1 to 10 (Fixed is not permitted)
Requires Data Link Layer Confirmation:
Never
Always
Sometimes If ’Sometimes’, when?
Configurable If ’Configurable’, how?

User option to set Data Link Confirmation to:
• Always – device will always request Data Link Confirmations.
• Multi-packet only – the device will request Data Link Confirmations when
sending multi-packet responses.
• Never – the device will never request Data Link Confirmations.
Requires Application Layer Confirmation:
Never
Always (not recommended)
When reporting Event Data (Slave devices only)
When sending multi-fragment responses (Slave devices only)
Sometimes _______ If 'Sometimes', when?
Configurable If 'Configurable', how? ____________________________________________

Timeouts while waiting for:

Data Link Confirm None Fixed at 3s _ Variable Configurable
Complete Appl. Fragment None Fixed at ___ Variable Configurable
Application Confirm None Fixed at ___ Variable Configurable
Complete Appl. Response None Fixed at ___ Variable Configurable
Others
______________________________________________________________________________
Attach explanation if 'Variable' or 'Configurable' was checked for any timeout
Sends/Executes Control Operations:
WRITE Binary Outputs Never Always Sometimes Configurable
SELECT/OPERATE Never Always Sometimes Configurable
DIRECT OPERATE Never Always Sometimes Configurable
DIRECT OPERATE - NO ACK Never Always Sometimes Configurable
Count > 1 Never Always Sometimes Configurable

Pulse On Never Always Sometimes Configurable
Pulse Off Never Always Sometimes Configurable
Latch On Never Always Sometimes Configurable
Latch Off Never Always Sometimes Configurable
Queue Never Always Sometimes Configurable

Clear Queue Never Always Sometimes Configurable
• Select timeout : configurable
5.4.7 DNP.3 Level 3 Implementation Table

Underlined information in grey are not implemented
REQUEST RESPONSE
OBJECT
Func Codes Qual Codes Func Code Qual Codes
Obj Var Description
1 0 Binary Input – All Variations 1, 22 00,01,06
1 1 Binary Input 1 00,01,06 129 00,01 (start-stop)
1 2 Binary Input with Status 1 00,01,06 129 00,01 (start-stop)
2 0 Binary Input Change - All Variations 1 06,07,08
2 1 Binary Input Change without Time 1 06,07,08 129 17,28 (index)
2 2 Binary Input Change with Time 1 06,07,08 129 17,28 (index)
2 3 Binary Input Change with Relative Time 1 06,07,08 129,130 17,28
10 0 Binary Output - All Variations 1 00,01,06
10 1 Binary Output
10 2 Binary Output Status 1 00,01,06 129 00,01
12 1 Control Relay Output Block (1) 3,4,5,6 17,28 (index) 129 Request echo
20 0 Binary Counter - All Variations 1,7,8,9,10, 00,01,06
22
20 1 32-Bit Binary Counter 1 00,01,06 129 00,01 (start-stop)
20 2 16-Bit Binary Counter 1 00,01,06 129 00,01 (start-stop)
20 5 32-Bit Binary Counter without Flag 1 00,01,06 129 00,01 (start-stop)
20 6 16-Bit Binary Counter without Flag 1 00,01,06 129 00,01 (start-stop)
1. Commands must be selected/executed on one point

REQUEST RESPONSE
OBJECT
Obj Var Description
21 0 Frozen Counter - All Variations 1 00,01,06
21 1 32-Bit Frozen Counter 1 00,01,06 129 00,01
21 2 16-Bit Frozen Counter 1 00,01,06 129 00,01
21 9 32-Bit Frozen Counter without Flag 1 00,01,06 129 00,01
21 10 16-Bit Frozen Counter without Flag 1 00,01,06 129 00,01
22 0 Counter Change Event - All Variations 1 06,07,08
22 1 32-Bit Counter Change Event without 1 06,07,08 129 17,18 (index)
Time
22 2 16-Bit Counter Change Event without 1 06,07,08 129 17,18 (index)
Time
22 5 32-Bit Counter Change Event with Time 1 06,07,08 129 17,18 (index)
22 6 16-Bit Counter Change Event with Time 1 06,07,08 129 17,18 (index)
Remarks:
Frozen counters (type21) are uploaded during general interrogation, but never polled after this.
REQUEST RESPONSE
OBJECT
Obj Var Description
23 0 Frozen Counter Event - All Variations 1 06,07,08
23 1 32-Bit Frozen Counter Event without 1 06,07,08 129,130 17,18 (index)
Time
23 2 16-Bit Frozen Counter Event without 1 06,07,08 129,130 17,18 (index)
Time
23 3 32-Bit Frozen Delta Counter Event 1 06,07,08 129,130 17,18
without Time
23 4 16-Bit Frozen Delta Counter Event 1 06,07,08 129,130 17,18
without Time
30 0 Analogue Input - All Variations 1 00,01,06
30 1 32-Bit Analogue Input 1 00,01,06 129 00,01 (start-stop)
30 2 16-Bit Analogue Input 1 00,01,06 129 00,01 (start-stop)
30 3 32-Bit Analogue Input without Flag 1 00,01,06 129 00,01 (start-stop)
30 4 16-Bit Analogue Input without Flag 1 00,01,06 129 00,01 (start-stop)
32 0 Analogue Change Event - All Variations 1 06,07,08
32 1 32-Bit Analogue Change Event without 1 06,07,08 129 17,18 (index)
Time
32 2 16-Bit Analogue Change Event without 1 06,07,08 129, 17,18 (index)
Time
32 3 32-Bit Analogue Change Event with Time 1 06,07,08 129,130 17,18
32 4 16-Bit Analogue Change Event with Time 1 06,07,08 129,130 17,18
40 0 Analogue Output Status - All Variations 1 00,01,06
40 1 32-Bit Analogue Output Status 1 00,01,06 129 00,01 (start-stop)
40 2 16-Bit Analogue Output Status 1 00,01,06 129 00,01 (start-stop)
41 1 32-Bit Analogue Output Block 5,6 17,28 (index) 129 Request echo
41 2 16-Bit Analogue Output Block 5,6 17,28 (index) 129 Request echo
50 0 Time and Date - All Variations
50 1 Time and Date 1 07 (quantity=1) 129 07 (quantity=1)
50 2 Time and Date with Interval 2 07 (quantity=1)
51 1 Time and Date CTO 129,130 07 (quantity=1)
51 2 Unsynchronized Time and Date CTO 129,130 07 (quantity=1)
52 1 Time Delay Coarse 129, 07 (quantity=1)
52 2 Time Delay Fine 129, 07 (quantity=1)
60 1 Class 0 Data 1 06
60 2 Class 1 Data 1 06,07,08
20,21,22 06
60 3 Class 2 Data 1 06,07,08
20,21,22 06
60 4 Class 3 Data 1 06,07,08
20,21,22 06
80 1 Internal Indications 2 00 (start-stop)

(index=7)
1 00,01 (start-stop) 129 00,01 (start-stop)
No Object (Cold Restart) 13
No Object (Delay Measurement 23

“On-line” Quality bit management:

The table below described the management of the DNP3 binary input status object for each
SPS status. This management is the same whether the information is with or without time
tag. SBMC is off.
IEC 61850
[0x0000]
[0x4100]
UNKNOWN
VALID
SPS Quality
IEC 61850 Associated SPS State V V

State BS1[7] V X
Reserved BS1[6] X X
Chatter filter BS1[5] X X
Local Forced BS1[4] X X
Remote Forced BS1[3] X X
Comm.lost BS1[2] X X
RestartBS1[1] X X
On-line BS1[0] 1 0
V stands for received value or start-up value

“-“ stands for 0. When 0 is significant for the understanding, 0 appears in the cell.
“X” stands for “Status bit indifferent”.
NOTE: IEC 61850 TOGGLING, SELFCHECK FAULTY, SUPPRESSED,
FORCED and SUBSTITUED status are not used with DNP3 MASTER
Protocol. When the IED is disconnected, the SPS status is set to
“UNKNOWN”.
IEC 61850
[0x0000]
[0x4100]
[0x6000]
VALID
OVERRANGE
UNKNOWN
MV Quality
DNP3 Measurement status object
IEC MV VALUE V V V
Reserved [7] X X X
Reference error BS1[6] X X X
Over-range BS1[5] 0 0 1
Local Forced BS1[4] X X X
Remote Forced BS1[3] X X X
Comm.lost BS1[2] 0 1 X
RestartBS1[1] X X X
On-line BS1[0] 1 X X
IEC 61850
[0x0000]
[0x4100]
[0x4080]
VALID
UNKNOWN
UNDEFINED
MV Quality
DNP3 Analogue input status

object
IEC MV VALUE V V V
Reserved [7] X X X
Reference error BS1[6] X X X
Over-range BS1[5] 0 0 1
Local Forced BS1[4] X X X
Remote Forced BS1[3] X X X
Comm.lost BS1[2] 0 1 X
RestartBS1[1] X X X
On-line BS1[0] 1 X X
IEC 61850 Quality Status
[0x0000]
[0x4200]
[0x4100]
[0x6000]
VALID
SELFCHECK
OVERRANGE
UNKNOWN
DNP3 counter status
object
FAULTY
Counter VALUE V V V V
Reserved [7] X X X X
Reserved BS1[6] X X X X
Roll-Over BS1[5] 0 0 0 1
Local Forced BS1[4] X X X X
Remote Forced BS1[3] X X X X
Comm.lost BS1[2] 0 0 1 X
RestartBS1[1] X X X X
On-line BS1[0] 1 0 X X
5.5 IEC 60870-5-103 Communication

The purpose of this chapter is not to describe the T103 but to specify the use of the T103
protocol on a legacy bus of the MiCOM C264.
As the MiCOM C264 is the master on the legacy bus - regards to protections and IEDs - this
protocol is referenced as “Master T103” in the MiCOM C264.
Here are described:
• Specific behaviours attached to the protocol T103
• Restrictions and enhancements
• Part of the T103 protocol used and not used
• Specific behaviours attached to implementation of Private Range of T103

5.5.2.1 Input
ASDU Data Note

1 Dated Digital input (absolute dating) Treated
Control acknowledgement
2 Dated Digital input (relative dating) Treated
3 Measurement Treated
4 Measurement : Default position Treated
5 Identification Not treated
6 Time synchronisation acknowledgement Treated
8 End of GI Treated
9 Measurement Treated
10 General Data Not treated (some
measurements only)
11 General Identification Not treated
17 Measurement Reg D only
23 … 31 Disturbance file management Treated
45 Ack of Single Command MiCOM Px3x only
46 Ack of Double Command MiCOM Px3x only
49 Analog protection signal MiCOM Px3x only
Only adress 0 which is DVICE: Device type
65 Single Point MiCOM Px3x only
66 Single Point with Time Tag MiCOM Px3x only
67 Double Point MiCOM Px3x only
68 Double Point with Time Tag MiCOM Px3x only
71 BitString 32 Bit without time tag-couple FUN MiCOM Px3x only
/TYP computed :
F8h / 70h : State of the IED
F8h / 74h : Request Station Interlock
72 BitString 32 Bit with time tag – see ASDU 71 MiCOM Px3x only
73 Measurement, Normalised value MiCOM Px3x only
77 Measurement MiCOM Px2x only
79 Energy Counter MiCOM Px3x only
5.5.2.2 Output
ASDU Data Note

6 Time synchronisation Treated
7 Request a GI Treated
20 Command Treated
23 … 31 Disturbance file management Treated
45 Single Command MiCOM Px3x only
46 Double Command MiCOM Px3x only
140 Read protection parameter MiCOM Px3x only
Only address 0 which is DVICE: Device type
144 Setpoint Reg D only
5.5.3 Behaviour
5.5.3.1 Synchronisation
The “Master T103” link is always synchronised by the MiCOM C264. No calculation of the
transmission delay is performed.
5.5.3.2 Polling
To connect an IED, a “Reset CU” frame is sent to the IED.
By default an IED is polled by a “Polling C2” frame, allowing to get “non priority information”.
If an IED signals it has “priority information”, it is polled with a “Polling C1” frame.
5.5.3.3 IED monitoring
The “OUT_OF_SERVICE” state is managed. It corresponds to the “Lock of communication”
[DI 20].
A GI may be done after each end of Tunnelling session.
The MiCOM C264 may regularly look for Disturbance file presence
5.5.3.4 Tunnelling mode
During tunnelling mode, only polling C2 may be done by the MiCOM C264 [Normally, if
“priority information” is present, the remote Master may send a “polling C1 frame”].
The MiCOM C264 must spy the tunnelling exchange in order not to loose information [DI and
AI change].
For security raison, at the end of a tunnelling session, a GI is done.
5.5.3.5 Station Interlocking
This functionality is only available on MiCOM P139 in private T103 range (Schneider Electric
D protocol variant)
After GI, and only if IED is MiCOM Px3x, we send a read on MiCOM Px3x parameter adress
0 which corresponds to Device Type. If MiCOM Px3x responds with analog parameter set to
139, we activate Station Interlocking Management.
Case of local control (front panel of the MiCOM P139) with Station interlock:
As soon as a user will try to control a switchgear by the front panel, the MiCOM P139 will
send an ASDU 72 with FUN/TYP = F8h/74h in order to request to PACiS system the station
interlock conditions. PACiS system should check if the command is allowed (specific
treatment done by CONDUITE of the computer) and respond to the MiCOM P139.
Case of remote control (from PACiS system) with Station interlock:

As soon as a user will try to control a device managed by MiCOM P139 by PACiS system
through T103 communication, the MiCOM P139 will send an ASDU 72 with FUN/TYP =
F8h/74h in order to request to PACiS system the station interlock conditions. PACiS system
should respond to the MiCOM P139 with a positive acknowledgement (checks have already
been done before)
If station Interlock is de-activated on MiCOM P139, the control of a switchgear on MiCOM
P139 by PACiS system through T103 communication is done by an EXECUTE ORDER
(selection will be refused by MiCOM P139)
5.5.3.6 REG D
The Reg D equipment manages 2 ASDU (144 and 17), for control of setpoints (144) and
setpoint value feedback (17), which is treated as a measurement in the computer. Setpoints
managed by the Reg D are "Direct Execute" only, there is no SBO management. The Reg D
setpoint command sequence is like the command sequence (ASDU20). The computer sends
the setpoint (ASDU 144), with the setpoint value, the Reg D sends its acknowledge
(ASDU1), if the acknowledge is OK, the Reg D sends the setpoint value feedback
(ASDU17).
5.5.3.7 Tapcon260
The Tapcon260 equipment supports ASDU 204 / FUN TYP=110/ INF=54 for TPI acquisition.
Nevertheless, the object type in SCE must be MV, not TPI.

5.5.4.1 Digital inputs
An ASDU number [(1,2) in public Range],[(66,67,68,69) in private Range]
A DI is identified by a couple (Function Type, Information Number).
Digital inputs are received as changes of state.
Special DI may be managed:
− DI 20: Lock of the communication. A GI must be done when the communication is

unlocked
− DI 23 to 26: Change of configuration number
− DI which are not transmitted during a GI. For these DI, the IED signals only
change of state from OFF to ON. The MiCOM C264 must generate by itself the
change from ON to OFF.
A Measurement is identified by:
− An ASDU Number [(3,4,9) in public range, (10, 21, 73,77) in private range]
− a couple (Function Type, Information Number)
− the rank of the Measurements in the ASDU
− the kind of Measurements [Current, Voltage, Power, Frequency, Other]
− the common address of ASDU

ASDU 21 and 10 provide the acquisition of the following measurements coming from P44x
relay:
• Current tripping values
• Residual voltages and currents
• Sum of trips
• Sum of cut amperes

C264 polls regularly the cells containing the measurement values.
It reads by ASDU 21 a single entry:
Description TI VSQ COT ADR FUN INF RII NOG GIN KOD
Measurement 15H 81H 2AH CAD FEH F4H x 1 Courier cell number 1
TI = Type identification
VSQ = variable structure qualifier
COT = cause of transmission
ADR = CAD = common address
FUN = function number
INF = information number
RII = Return information identifier
NOG = Number Of Generic identification
GIN = Generic Identification Number
ASDU 10 provides the response.
5.5.4.3 Bitstring 32-bits :
The state of the IED is identify by the ASDU 71 or 72 with couple FUN / TYP = F8h / 70h.
This ASDU describes the status of the IED (Station Interlocking active or not …)
A request to check station interlocking is identify by the ASDU 71 or 72 with couple FUN /
TYP = F8h / 74h. In this request, the couple FUN/TYP of the command to spend is defined.
5.5.4.4 Analog protection signal (ASDU 49) :
Only for MiCOM Px3x, an analogue protection signal is received after GI
Only address 0 is managed. It is used to recognise MiCOM P139 in order to activate station
interlocking management.
5.5.4.5 Energy counter (ASDU 79) :
Only for MiCOM Px3x, four energy counters are available.
Energy counters are identified by:
• An ASDU number (79) in private range
• a couple Function Type, Information number
• the rank of the counter in the ASDU
• the common address of the ASDU
Description TI VSQ COT ADR FUN INF DB0-DB4 DB5-DB9 DB10-DB14 DB15-DB19
Energy 4FH 04H 01H CAD F8H 6CH Active + Active - Reactive + Reactive -
counter
TI = Type identification
VSQ = variable structure qualifier
COT = cause of transmission
ADR = CAD = common address
FUN = function number
INF= information number

DB0-DB4 = active energy output
DB5-DB9 = active energy input
DB10-DB14 = reactive energy output
DB15-DB19 = reactive energy input
Format of the energy counter value
Value
Value
Value
S Value
IV CA CY Sequence number
S : 0 Value positive, 1 = value negative

CY : 0 = no carry, 1= carry
CA : 0 = not adjusted, 1 = adjusted
5.5.5.1 Controls
An ASDU Number and a couple (Function Type, Information Number) identify a control.
The acknowledgement of a control is to be waited as:
• A DI with the same (Function Type, Information Number) as the control and with a
‘Cause Of Transmission’ equals to ‘positive return’ or ‘negative return’ in public range
• A ASDU 45 or 46 with a ‘Cause Of Transmission’ equals to ‘end of activation OK’ or

‘en of activation KO’, or ‘deactivation OK’, or ‘deactivation KO’ in private range
5.5.5.2 Setpoints Controls :
A setpoint control is identified by an ASDU Number plus a couple (Function Type,
Information Number). In the case of the Reg D equipment the ASDU is 144.
The acknowledgement of a setpoint control is to be waited as :
• A DI (ASDU 1) with the same (Function Type, Information Number) as the control and
with a ‘Cause Of Transmission’ equals to ‘positive return’ or ‘negative return’ in public
range.
• An ASDU 17 with a ‘Cause Of Transmission’ equals to ‘Local Operation’ in public

range. The ASDU is a measurement which contains the setpoint feedback value.
5.5.5.3 Read protection parameter :
Only for MiCOM Px3x, a read of protection parameter (ASDU 140) address 0 (Device Type)
is sent to IED
The IED responds with ASDU 49 in which Device Type is set (139 if IED is a MiCOM P139
for example).
5.5.5.4 ASDU 232 / 105 management
It allows to send control to IEC60870-5-103 legacy IED. It requires to manage also the
ASDU 105 as response to ASDU 232.
Comparing ASDU232 & ASDU20
ASDU232 ASDU20
Field Value Field Value
ASDU No E8H ASDU No 14H
VSQ 81H VSQ 81H
COT 14H COT 14H
Device address @ied Common Address of @ied
DN2 Cfg Function type Cfg
DN3 Cfg Information Number Cfg
DC0 1=OFF; 2=ON DC0 1=OFF; 2=ON
X 0 RII Set by master
Comparing ASDU105 & ASDU01
ASDU105 ASDU01
Field Value Field Value
ASDU No 69H ASDU No 01H
VSQ 81H VSQ 81H
COT 45H, 46H, 47H, COT 14H, 15H, 0BH
Device address @ied Common Address of @ied
DN2 Idem ASDU232 Function type Idem ASDU20
DN3 Idem ASDU232 Information Number Idem ASDU20
DPI 1=OFF; 2=ON DPI 1=OFF; 2=ON
X 0 msLow
Four octet
msLow msHigh binary time
msHigh Four octet binary IV 0 mmmmmm
time CP32Time2a
IV 0 mmmmmm SU 00 hhhhhh
SU 00 hhhhhh CP32Time2a SIN Idem RII
ASDU20
Configuration
Management of commands through ASDU 232.
• The ASDU number [232]
• DN2 & DN3 (respectively ‘y’ & ‘x’ component of PID)

Management of state through ASDU 105.
• The ASDU number [232]
• DN2 & DN3 (respectively ‘y’ & ‘x’ component of PID)

DN2 & DN3 will be given – respectively – as ‘Function type’ & ‘Information Number’.
5.6 IEC 60870-5-101 Communication

5.6.1 Purpose
The purpose of this chapter is not to describe the T101 but to specify the implementation of
T101 protocol on a legacy bus inside the MiCOM C264.
5.6.2 Master IEC 60870-5-101 profile
The companion standard presents sets of parameters and alternatives from which subsets
have to be selected to implement particular telecontrol systems. Certain parameters values,
such as the number of bytes in the COMMON ADDRESS of ASDUs represent mutually
exclusive alternatives. This means that only one value of the defined parameters is admitted
per system.
Other parameters, such as the listed set of different process information in command and in
monitor direction allow the specification of the complete set or subsets, as appropriate for
given applications. This clause summarises the parameters of the previous clauses to
facilitate a suitable selection for a specific application. If a system is composed of equipment
stemming from different manufacturers it is necessary that all partners agree on the selected
parameters.
The selected parameters should be marked in the white boxes as follows :
Function or ASDU is not used
⌧ Function or ASDU is used as standardised (default)
R Function or ASDU is used in reverse mode
B Function or ASDU is used in standard and reverse mode

The possible selection (blank, X, R or B) is specified for each specific clause or parameter.
NOTE: In addition, the full specification of a system may require individual
selection of certain parameters for certain parts of the system, such as
the individual selection of scaling factors for individually addressable
measured values.
5.6.2.1 System or device
(system specific parameter, indicates the definition of a system or a device by marking one
of the following with ‘X’)
System definition
Controlling station definition (Master)
⌧ Controlled station definition (Slave)

5.6.2.2 Network configuration
(network specific parameter, all configurations that are used are to be marked ‘X’)
⌧ Point-to-point ⌧ Multipoint-party line
⌧ Multiple point-to-point ⌧ Multipoint-star

5.6.2.3 Physical layer

(network specific parameter, all interfaces and data rates that are used are to be marked ‘X’)
Transmission speed (control direction)
Standard
> 1200 bits/s
⌧ 100 bits/s ⌧ 2400 bits/s ⌧ 2400 bits/s 56000 bits/s
⌧ 1200 bits/s ⌧ 38400 bits/s
Transmission speed (monitor direction)
Standard
> 1200 bits/s
⌧ 1200 bits/s ⌧ 38400 bits/s
5.6.2.4 Link layer

(network specific parameter, all options that are used are to be marked ‘X’. Specify the
maximum frame length).
⌧ Balanced transmission Not present (balanced transmission only)
⌧ Unbalanced transmission ⌧ One octet
⌧ Two octets
⌧ Structured
⌧ Unstructured
Frame length (number of bytes)
255 Maximum length L in control direction
up to 255 Maximum length L in monitor direction – configurable

5.6.2.5 Application layer

⌧ One octet ⌧ Two octets

⌧ One octet ⌧ Structured
⌧ Two octets ⌧ Unstructured
⌧ Three octets
⌧ One octet ⌧ Two octets (with originator address)

Set to zero in case of no originator address.
⌧ <1> := Single-point information M_SP_NA_1
⌧ <2> := Single-point information with time tag M_SP_TA_1
⌧ <3> := Double-point information M_DP_NA_1
⌧ <4> := Double-point information with time tag M_DP_TA_1
⌧ <5> := Step-position information M_ST_NA_1
⌧ <6> := Step-position information with time tag M_ST_TA_1
<7> := BitString of 32 bit M_BO_NA_1
<8> := BitString of 32 bit with time tag M_BO_TA_1
⌧ <9> := Measured value, normalized value M_ME_NA_1
⌧ <10> := Measured value, normalized value with time tag M_ME_TA_1
⌧ <11> := Measured value, scaled value M_ME_NB_1
⌧ <12> := Measured value, scaled value with time tag M_ME_TB_1
⌧ <13> := Measured value, short floating point value M_ME_NC_1
⌧ <14> := Measured value, short floating point value with time tag M_ME_TC_1
⌧ <15> := Integrated totals M_IT_NA_1

⌧ <16> := Integrated totals with time tag M_IT_TA_1
<17> := Event of protection equipment with time tag M_EP_TA_1
<18> := Packed start events of protection equipment with time tag M_EP_TB_1
<19> := Packed output circuit transmission of protection equipment with time tag M_EP_TC_1
<20> := Packed single-point information with status change detection M_PS_NA_1
⌧ <21> := Measured value, normalized value without quality descriptor M_ME_ND_1
⌧ <30> := Single-point information with time tag CP56Time2a M_SP_TB_1
⌧ <31> := Double-point information with time tag CP56Time2a M_DP_TB_1
⌧ <32> := Step-position information with time tag CP56Time2a M_ST_TB_1
<33> := Bistring of 32 bits with with time tag CP56Time2a M_BO_TB_1
⌧ <34> := Measured value, normalized with time tag CP56Time2a M_ME_TD_1
⌧ <35> := Measured value, scaled with time tag CP56Time2a M_ME_TE_1
⌧ <36> := Measured value, short floating point number with time tag CP56Time2a M_ME_TF_1
⌧ <37> := Integrated totals with time tag CP56Time2a M_IT_TB_1
<38> := Event of protection equipment with time tag CP56Time2a M_EP_TD_1
<39> := Packed start events of protection equipment with time tag CP56Time2a M_EP_TE_1
<40> := Packed output circuit information of protection equipment with time tag CP56Time2a M_EP_TF_1

⌧ <45> := Single command C_SC_NA_1
⌧ <46> := Double command C_DC_NA_1
⌧ <47> := Regulating step command C_RC_NA_1
⌧ <48> := Set point command, normalized value C_SE_NA_1
⌧ <49> := Set point command, scaled value C_SE_NB_1
⌧ <50> := Set point command, short floating point value C_SE_NC_1
<51> := BitString of 32 bits C_BO_NA_1

⌧ <70> := End of initialisation M_EI_NA_1


⌧ <100> := Interrogation command C_IC_NA_1
⌧ <101> := Counter Interrogation Command C_CI_NA_1
<102> := Read command C_RD_NA_1
⌧ <103> := Clock synchronisation command C_CS_NA_1
⌧ <104> := Test command C_TS_NB_1
<105> := Reset process command C_RP_NC_1
<106> := Delay acquisition command C_CD_NA_1

<110> := Parameter of measured value, normalized value P_ME_NA_1
<111> := Parameter of measured value, scaled value P_ME_NB_1
<112> := Parameter of measured value, short floating point value P_ME_NC_1
<113> := Parameter activation P_AC_NA_1
File transfer
⌧ <120> := File ready F_FR_NA_1
⌧ <121> := Section ready F_SR_NA_1
⌧ <122> := Call directory, select file, call file, call section F_SC_NA_1
⌧ <123> := Last section, last segment F_LS_NA_1
⌧ <124> := Ack file, ack section F_AF_NA_1
⌧ <125> := Segment F_SG_NA_1
⌧ <126> := Directory F_DR_TA_1
Special use
None

(station-specific parameters)
Shaded boxes are not required.
Mark type identification/cause of transmission combinations:
‘X’ if used only in the standard direction
‘R’ if used only in the reverse direction
‘B’ if used in both directions

20 to 37 to
1 2 3 4 5 6 7 8 9 10 11 12 13 44 45 46 47
36 41
<1> M_SP_NA_1 X X X X X
<2> M_SP_TA_1 X X X
<3> M_DP_NA_1 X X X X X
<4> M_DP_TA_1 X X X
<5> M_ST_NA_1 X X X X X
<6> M_ST_TA_1 X X X
<7> M_BO_NA_1
<8> M_BO_TA_1
<10> M_ME_TA_1 X
<12> M_ME_TB_1 X
<14> M_ME_TC_1 X
<15> M_IT_NA_1 X X
<16> M_IT_TA_1 X
<17> M_EP_TA_1
<18> M_EP_TB_1
<19> M_EP_TC_1
<20> M_PS_NA_1
<21> M_ME_ND_1 X X X
<30> M_SP_TB_1 X X
<31> M_DP_TB_1 X X
<32> M_ST_TB_1 X X
<33> M_BO_TB_1
<34> M_ME_TD_1 X
<35> M_ME_TE_1 X
<36> M_ME_TF_1 X
<37> M_IT_TB_1 X
<38> M_EP_TD_1
<39> M_EP_TE_1
<40> M_EP_TF_1
<45> C_SC_NA_1 X X X X X X X X X
<46> C_DC_NA_1 X X X X X X X X X
<47> C_RC_NA_1 X X X X X X X X X

20 to 37 to
1 2 3 4 5 6 7 8 9 10 11 12 13 44 45 46 47
36 41
<48> C_SE_NA_1 X X X X X X X X X
<49> C_SE_NB_1 X X X X X X X X X
<50> C_SE_NC_1 X X X X X X X X X
<51> C_BO_NA_1
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X
<101> C_CI_NA_1 X X X
<102> C_RD_NA_1
<103> C_CS_NA_1 X X
<104> C_TS_NA_1 X X
<105> C_RP_NA_1
<106> C_CD_NA_1
<110> P_ME_NA_1
<111> P_ME_NB_1
<112> P_ME_NC_1
<113> P_AC_NA_1
<120> F_FR_NA_1 X
<121> F_SR_NA_1 X
<122> F_SC_NA_1 X
<123> F_LS_NA_1 X
<124> F_AF_NA_1 X
<125> F_SG_NA_1 X
<126> F_DR_TA_1 X X
5.6.2.6 Basic application functions

(station-specific parameter, mark ‘X’ if function is used)
⌧ Cyclic data transmission

Read procedure
Read procedure
⌧ Spontaneous transmission
Link state between Controlling and Controlled Station
⌧ Management of the COM lost (Problem detecting on the link)
⌧ Management of the COM recovering (Problem not detecting on the link)

⌧ Global
Group 5 Group 11 Addresses per group have to be defined
Group 6 Group 12
⌧ Global
Group 4
⌧ Clock synchronisation
Notes:
The controlled station reports the change of hour by sending a clock synchronisation message (ASDU 103) to the
controlling station.
⌧ Direct command transmission
⌧ Direct set-point command transmission
⌧ Select and execute command
⌧ Select and execute set-point command
⌧ C_SE_ACTTERM used
⌧ No additional definition

Persistent output
Mode A : local freeze with spontaneous transmission
Mode B : local freeze with counter interrogation
Mode C : freeze and transmit by counter interrogation commands
Mode D : freeze by counter interrogation command, frozen values reported

spontaneously
⌧ Counter read ⌧ General request counter
Counter freeze without reset Request counter group 1
Counter freeze with reset Request counter group 2
Counter reset Request counter group 3
Request counter group 4

Parameter loading
Threshold value
Smoothing factor

Act/deact of persistent cyclic or periodic transmission of the addressed object

Test procedure
⌧ Test procedure
File transfer
(station-specific parameter), mark ‘X’ if function is used)
File transfert in monitor direction
⌧ Transparent file
⌧ Transmission of disturbance data of protection equipment
⌧ Transmission of sequences of events


Transparent file
Background scan
⌧ Background scan

Digital Inputs and Analog Inputs, management events priorities.
See : T101 standard Amendment 2 §7.2.2.2
5.6.2.7 Application Functions

The following IEC-60870-5-5 standard application processes are required to be supported.
Station Initialisation
Station initialisation consists of a reset of the communications link, followed by a general
interrogation of the controlled station. Once this initialisation sequence performed the
controlling station can start the polling for data report.
Communications failure
Communications to the controlled station must be re-initialised by the controlling station
when the frame repeat process has completed without successfully transmitting the frame (ie
the frame time-out period times the number of repeats).
If the controlled station fails to communicate with the controlling station then the controlling
station should perform a communications system initialisation for that controlled station.
Controlled station failure
The controlled station shall indicate to the controlling station that it has initialised by sending
a frame indicating End of Initialisation with a Cause of Initialisation (COI) field, which will
identify the reason for the initialisation.
Data Acquisition by Polling
The default for all analogue values shall be reporting as Class 2 data (COT=1,
periodic/cyclic, or COT = 2, BackgroundScan cyclic).
Values returned as Class 2 data do not have a time tag (since they are constantly repeated).
The controlled station may return Class 1 data in response to a Class 2 request if no Class 2
data is available and Class 1 data is awaiting transmission.
At the controlled station, if a request for Class 2 data is received and no data is available a
negative response, data not available, shall be returned to the controlling Station. The
negative response is a fixed length frame (FC=9).
Normal Acquisition of Events

The default for all status changes are reported as Class 1 data (COT=3, spontaneous).
Values returned as Class 1 data shall have a time tag (either CP24Time2a, or CP56Time2a).
Status changes at the controlled station shall cause the ACD bit to be set in the next Class 1
or Class 2 data response. The controlling station shall respond to ACD set by inserting a
scan for Class 1 (spontaneous) data as the next scan.
The response to a Class 1 data request shall also have the ACD bit set if more Class 1 data
is awaiting transmission. In this case a further scan for Class 1 data shall be scheduled by
the controlling station.
Abnormal Acquisition of Events
At the controlled station, if a request for Class 1 data is received and no data is available an
error should be raised and a negative response, data not available, returned to the
controlling Station. The negative response shall be a fixed length frame (FC=9.
At the controlling station, if a response to a scan for Class 1 data indicates no data is
available an error shall be raised and scanning returned to Class 2 data requests.
General Interrogation
The GI returns the current status information directly from the Computer database.
Time tags are not used for data items returned as part of the GI response.
The GI groups are not supported, only the global general interrogation is supported.
The System (including the controlled station) may have different synchronisation sources
(IRIG-B, SCADA).
system isn’t synchronised by an other source : the clock synchronisation response is
positive.
system (including the controlled station) is synchronised by an other source : the clock
synchronisation response is negative.
All Class 1 data are time-tagged with :
Either the 3 bytes time-stamp (CP24Time2a), giving minutes and milliseconds within the
hour, or the 7 bytes time-stamp (CP56Time2a), giving minutes, milliseconds, hours, day,
month and year according to the Computer configuration.
In case of using relative time-Tag (CP24Time2a), the controlled station reports :
• the change of hour
• any time correction
• by sending a clock synchronisation message (ASDU 103) to the controlling station, as

Class 1 data, with a cause of transmission spontaneous (3).
The invalid bit in the time-stamp is set when the time source is not available.
All control commands shall be Select before Execute, or Direct Execute.
For only the control commands: Activation termination is returned to the controlling station to
signal the end of a control sequence.
The QU field of the Qualifier of Command shall be set to zero (0), no additional definition.
Test procedure
A test command may be issued by the controlling station to ensure the availability of the
communications link and the commands subsystem.
Test commands are received at the controlled station on the active link. The controlled
station mirrors the test command, on the link from which it was received, with a cause of
transmission indicating activation confirmation.
An error response should be sent if the command is incorrect, with a cause of transmission
indicating negative activation confirmation.
In the case of balanced mode, the controlled station may also send a test command to the
controlling station, to ensure the availability of the communications link as there is no polling
made by the controlling station.
MiCOM C264/C264C
COMMISSIONING
CONTENT

1.1 Introduction 3
1.2 Definition 3
1.3 Commissioning the product 3
1.4 Responsibility 3
1.5 Setting familiarisation 4
2. REQUIREMENTS 5
3. COMMISSIONING TESTS WITH GHU200 OR GHU201( WITH LCD) 6

3.1 Preparation 6
3.2 Check version & number 7
3.3 Faults 8
3.4 Check the boards status 8
3.5 Checking the binary signal inputs 9
3.6 Checking the output relays 10
3.7 Testing the communication with external devices 11
3.8 Testing the control functions 12
3.9 Switching from local to remote control 12
3.9.1 Local control 12
3.9.2 Remote control 12
4. COMMISSIONING TESTS WITH GHU210 OR GHU211(WITHOUT LCD) 13

C264/EN CM/C80 Commissioning
BLANK PAGE

This document is a chapter of the MiCOM C264/C264C manuals. It describes the
commissioning of the product and should not be confused with application commissioning.
This chapter follows the C264/EN IN (Installation) chapter.
1.1 Introduction
To commission MiCOM C264/C264C, it is necessary to verify that the hardware is
functioning correctly and that the application-specific software settings have been applied to
the MiCOM C264/C264C.
To verify that the MiCOM C264/C264C is operating correctly, a database has to be loaded
into the computer. Once the database has been loaded, tests should be performed on each
a single MiCOM C264/C264C element.
As the MiCOM C264/C264C’s menu language is user-selectable, it is acceptable for the
Commissioning Engineer to change it to allow accurate testing as long as the menu is
restored to the customer’s preferred language on completion.
Before carrying out any work on the equipment, the user should be familiar with the contents
of the chapter C264/EN SA (Safety), of the Schneider Electric Safety Guide: SFTY/4L M/G11
( or later issue), and of all the C264 technical data.
1.2 Definition
The objective of commissioning is to prove that the equipment, and any interconnections to
process and other system components, is suitable for its intended purpose.
Commissioning is the activity that demonstrates that the equipment is acceptable for service.
As digital devices are configured for specific application, the commissioning can be split into
two main parts:
• Commissioning the product.
• Commissioning the application (when product has had its database loaded). This
second part is documented and carried out through FAT (Factory Acceptance Tests),
and SAT (Site Acceptance Tests) activities.
The scope of this chapter is the description of commissioning tests that prove that the
MiCOM C264 is suitable for further application tests.
1.3 Commissioning the product
Commissioning the product starts with product reception and is continued through all off the
installation procedures. Activities are divided between: -
• Visual inspection at reception.
• Inspection at Front Panel when MiCOM C264/C264C is powered up.
• The starting point is the delivery form that describes all of the delivered hardware
components that constitute the MiCOM C264/C264C.
1.4 Responsibility
Most commissioning activities involve a power supply that can damage the installation or
cause injury to the operator. The chapter C264/EN SA (Safety) should be read carefully
before any handling.
Before starting commissioning, the contractual and human responsibilities should be clearly
defined.
Only qualified and competent persons should carry out commissioning and the validation
tests.
1.5 Setting familiarisation

Commissioning the MiCOM C264 requires operation of its Human Machine Interface (the
Local Control Display). The chapter C264/EN HI contains a detailed description of the menu
structure of MiCOM C264.
The commissioning engineer should have had training on the HMI or sufficient time should
be allowed to become familiar with it (with an already commissioned device).
2. REQUIREMENTS
It is essential that all requirements expressed in C264/EN IN (Installation) chapter have been
fulfilled.
The delivery form is the starting document.
3. COMMISSIONING TESTS WITH GHU200 OR GHU201( WITH LCD)

3.1 Preparation
After the MiCOM C264 has been installed and connected as described in Chapters
C264/EN IN and C264/EN CO, the commissioning procedure can begin.
Before turning on the power supply voltage, the following items must be checked:
• Is the device connected to the protective ground at the specified location?
• Does the nominal (and measured) voltage of the battery agree with the nominal
auxiliary voltage of the device?
• Are the current and voltage transformer (if used) connections, grounding, and phase
sequences correct?
After the wiring work is completed, check the system to make sure it is properly isolated.
Once all checks have been made, the power supply voltage may be turned on.
After the voltage has been applied, the MiCOM C264 starts up.
During start-up, various tests are carried out (see section entitled ‘Diagnose level1’ in
Chapter C264/EN MF (Maintenance)).
The LED indicator labelled ‘HEALTHY’ (Fourth LED) will light up.
After approximately 30 s, the MiCOM C264 is ready for operation.
In initial, factory-set condition or after a cold restart, the front panel displays a message
“Schneider Electric”.
After the settings have been made, the following checks should be carried out before any
interlocks or isolation is cancelled:
• Are the software and database versions compatible with the hardware?
• Are all boards correctly assigned within the MiCOM C264?
• Are all IOs correctly configured and recognised by the C264?
• Are all communications (S-BUS, T-BUS and L-BUS) correctly configured and
recognised?
• Are the control functions fully operational?
• Is the automation running?

The following chapters describe the checks to be performed to answer these questions and
ensure that the MiCOM C264 is fully operational in its application.
3.2 Check version & number

In the commissioning process this panel is the first to check. The MiCOM C264 serial
number tells if the C264 is the ordered one, and indirectly gives the hardware version.
The software version from the VC document gives features and limitation of the MiCOM
C264/C264C.
The database version is given by PACiS SCE database version and describes all the
settings on the MiCOM C264/C264C.
The operational mode indicates whether the device is in a maintenance or operational mode.
S E R V I C E <time>
S E R I A L N B :
S O F T W A R E V E R S I O N :
D B 1 V E R S I O N S T A T E :
D B 2 V E R S I O N S T A T E :
O P E R A T I N G H O U R S :
O P E R A T I N G M O D E :
R E D U N D A N C Y M O D E :
3.3 Faults
If the first LED is alight, this means that there is something wrong inside the C264.
The FAULT panel gives information about the problem.
F A U L T <time>
<Description of the problem>
3.4 Check the boards status

MiCOM C264 front panel gives access to C264 boards status (refer to chapter C264/EN HI).
Board labels are defined during the configuration phase. They are based on short names
and are indexed automatically. The default configuration model is:
• GHU Graphical Human Unit
• BIU Basic Interface Unit (power supply)
• CCU Circuit breaker Control Unit (SBO board)
• DIU Digital Input Unit
• DOU Digital Output Unit
• AIU Analogue Input Unit (DC current and voltage input)
• TMU Transducerless Measurements Unit (CT/VT board)
• AOU Analogue Output Unit (4 current analogue output)
The product checks whether the number of installed boards matches with the number of
boards configured, the following messages are generated depending on the results:
• PresConf Board configured present and operational
• Failure Board configured present and faulty
• ConfButMissing Board configured not present
• Too Many Board not configured but present (spare)

B O A R D <time>
<Board Label><Number>
<Board Status>
<Board Status>
<Board Status>
<Board Status>
<Board Status>
<Board Status>
N°page/Number of Pages
3.5 Checking the binary signal inputs

MiCOM C264 front panel gives access to input status for all DI boards (DIU200, DIU210,
DIU211, CCU211 or CCU200).
For DIU200, DIU210 and DIU211 boards:
D I <time>
DIU <Number>
DI 0 <status> DI 8 <status>
For CCU200 and CCU211boards:
D I <time>
CCU <Number>
DI 0 <status>
DI 1 <status>
DI 2 <status>
DI 3 <status>
DI 4 <status>
DI 5 <status>
DI 6 <status>
DI 7 <status>
3.6 Checking the output relays

MiCOM C264 front panel gives access to output relays status for all DO boards (DOU200,
DOU201, CCU211 or CCU200).
For DOU200 and DOU201 boards:
D O <time>
DOU <Number>
DO 0 <status> DO 8 <status>
DO 1 <status> DO 9 <status>
DO 2 <status>
DO 3 <status>
DO 4 <status>
DO 5 <status>
DO 6 <status>
DO 7 <status>
For CCU200 and CCU211 boards:
D O <time>
CCU <Number>
DO 0 <status>
DO 1 <status>
DO 2 <status>
DO 3 <status>
3.7 Testing the communication with external devices

The IED panel gives access to the connection state with external devices on Ethernet
protocol or serial links:
I E D <time>
IP CLIENT NB:
IP SERVER : <protocol>
<Server 1 Name>
<Server 1 IP address> <connection state>
<Server 2 Name>
<Server 2 IP address> <connection state>
…
LEGACY DEVICE : <protocol>
<IED 1 name>
<IED 1 address> <connection state>
<IED 1 name>
<IED 1 address> <connection state>
…
3.8 Testing the control functions

The selected bay type is displayed on the Bay Panel. The activation of the Bay Panel
display is described in Chapter C264/EN HI.
If the position signals of the switchgear units are connected correctly to the MiCOM C264,
then the updated switching status of the switchgear units will be displayed on the bay panel.
If the switching status is not displayed correctly, the user can check the physical state
signals of the binary inputs to determine whether the status signals in the MiCOM C264 are
correct.
3.9 Switching from local to remote control
Bays can be controlled locally using the keys on the local control panel or remotely through
the communication interface (SCADA or operator interface).
The control point – Local or Remote – is selected either by means of the L/R key on the local
control panel or via appropriately configured binary signal input. If binary signal input has
been configured, then the L/R key has no effect.
Switching from Remote to Local using the L/R key on the local control panel is only possible
if the L/R password has been entered. The selected control point is displayed on the Bay
Panel.
3.9.1 Local control
Bay to be controlled is selected by pressing the Selection key on the local control panel.
If the bay is to be controlled through binary signal inputs, then the appropriate signal input
must be triggered.
3.9.2 Remote control
The switchgear units can be controlled via the communication interface or appropriately
configured binary signal inputs.
4. COMMISSIONING TESTS WITH GHU210 OR GHU211(WITHOUT LCD)

After the MiCOM C264 has been installed and connected as described in Chapters C264/EN
IN and C264/EN CO, the commissioning procedure can begin.
Before turning on the power supply voltage, the following items must be checked:
• Is the device connected to the protective ground at the specified location?
• Does the nominal (and measured) voltage of the battery agree with the nominal
auxiliary voltage of the device?
• Are the current and voltage transformer (if used) connections, grounding, and phase
sequences correct?
After the wiring work is completed, check the system to make sure it is properly isolated.
Once all checks have been made, the power supply voltage may be turned on.
After the voltage has been applied, the MiCOM C264 starts up.
During start-up, various tests are carried out (see section entitled ‘Diagnose level1’ in
Chapter C264/EN MF (Maintenance)).
The LED indicator labelled ‘HEALTHY’ (Fourth LED) will light up.
After approximately 30 s, the MiCOM C264 is ready for operation.
After the settings have been made, it is necessary to check that the software and the
database versions are compatible with the hardware.
The following chapters describe the checks to be performed with CAT to answer these
questions and ensure that the MiCOM C264 is fully operational in its application.
The CAT is fully described in IN chapter.
With the CAT, the “Computer version” button gives access to the current C264 software
version, the active database and the computer operational mode.
For a normal behaviour, the computer mode is “ACTIVE”
BLANK PAGE
Record Sheet C264/EN RS/C80
MiCOM C264/C264C
RECORD SHEET
CONTENT
2. COMMISSIONING RECORD 4
3. MAINTENANCE RECORD SHEET 5

C264/EN RS/C80 Record Sheet
BLANK PAGE

This document is a chapter of the MiCOM C264 documentation. It describes the
Commissioning record sheet (RS) and the Maintenance Record of this computer.
The purpose of this chapter is to follow the history of the MiCOM C264 hardware
replacement.
2. COMMISSIONING RECORD
Commissioning Date:
Engineer:
Station Name:
Circuit Name:
Front Plate Information
Under the top access cover, there is the following type of label:
Cortec number
C264M11I2B00012530000111S1 Serial number
S.A 110 à 125 Vdc N˚ série 117268

Serial n˚
Nominal wetting
Voltage digital inputs 110 / 125 Vdc
Nominal wetting
Nominal Power voltage for digital
supply Input inputs
Voltage C0151ENa
Fill in the following array according to the label under the top access cover:
Serial number
Cortec number
Auxiliary voltage for power supply
Nominal wetting voltage for digital inputs
*Delete as appropriate
Have all relevant safety instructions been followed? Yes/No*
Product checks
Visual inspection with the computer de-energized
Relay damaged? Yes/No*

Rating information correct for installation? Yes/No*
Case earth installed? Yes/No*
3. MAINTENANCE RECORD SHEET

Product Serial number
Slot letter in
the rack Previous board New board
DATE Engineer Board type
(between A Serial number Serial number
and Q)
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
BLANK PAGE
MiCOM C264/C264C
MAINTENANCE
CONTENT
2. STANDARD MAINTENANCE OPERATION 4

2.1 Level 1 diagnosis facilities 4
2.1.1 Front panel LED indications 4
2.1.2 Front panel LCD indications 6
2.1.3 Adjustment of the brightness of the front panel LCD 6
2.2 Maintenance period 7
2.3 Method of repair 7
2.3.1 Replacing the complete MiCOM C264/C264C 7
2.3.2 Replacing a board 9
2.4 Cleaning 13
3. THE EMBEDDED MAINTENANCE WEB SERVER 14

3.1 Maintenance data pages 16
3.1.1 C264 general information page 16
3.1.2 Databases general information page 17
3.1.3 Racks and boards status page 18
3.1.4 IED networks page 19
3.1.5 CPU time and synchronisation page 20
3.2 Process data pages 22
3.2.1 Binary inputs page 22
3.2.2 Measurements page 23
3.2.3 Counters page 24
3.2.4 TPI page 25
3.3 Files upload pages 26
3.3.1 Systrap error file upload page 26
3.3.2 Stored event log file upload page 27
4. ENGINEERING MAINTENANCE OPERATION 28

C264/EN MF/C80 Maintenance
BLANK PAGE

Maintenance and FaultFinding procedures of the MiCOM C264/C264C. Reading of
C264/EN SA chapter is mandatory.
2. STANDARD MAINTENANCE OPERATION

The aim of this chapter is to describe standard methods to diagnose the MiCOM
C264/C264C status, and provide common maintenance procedures for the replacement
and/or addition of components.
Before any maintenance operation, please refer to the documentation chapter SA (Safety)
and to the Schneider Electric Safety Guide: SFTY/4L M/G11-S (or later issue).
2.1 Level 1 diagnosis facilities
When maintenance action is planned, the operator should prepare, act and report.
The minimal preparation is to get the commissioning Record Sheet (see the C264/EN RS
chapter) of installed MiCOM C264/C264C in order to see the product configuration and its
history. The User should refer also to his own experience besides this manual. It is also
recommended to extract the logbook history in order to be informed of the intervention
conditions.
At a first level the product provides several methods to check the context of the fault. The
main ones are:
• LEDs
• LCD (Liquid Crystal Display)

2.1.1 Front panel LED indications
Refer to C264/EN HI chapter for the precise Led’s description.
On the main rack:
The first 5 LEDs indicate the MiCOM C264/C264C status information. With reference to the
C264/EN HI (Human Interface) chapter, the LEDs indicate from top to down:
LED id Colour LED on LED slow blinking LED fast blinking LED off
1 Red There is at least one There is at least one minor Not used No fault
major fault (hardware, fault (I/O board,
database) (1) communication to IEDs)(2)
2 Yellow All the alarms are ac- All alarms displayed in There is at least 1 No alarm
knowledged, but there the alarm panel are not acknowledged
is at least one alarm inactive and alarm displayed in
still active. (3) acknowledged 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
A minor fault is a fault causing only the non-availability of a part of the functionality:
Symptom LED status Possible reason Way to solve

Functions as commu- All LEDs are OFF The cable between Verify the connection between
nication, automation, CPU and GHU2xx, CPU or GHU2xx. If connection is
printing are well ope- or GHU2xx itself is OK and the problem is not already
rating & the not operational solved then change the GHU2xx
watchdog on BIU is board.
SET
The supply is ON LED6 is ON (but Problem with BIU Replace BIU board or CPU board.
and the watch dog LED7 thru 13 are board or CPU
on BIU is RESET. OFF if predefined) board
C264 is not running LED1 ON Incoherent Download a coherent database
or not fully database
operational
At least one prede- Hardware fault Go in Fault display and Board
fined LED among display to determine the faulty
LED7 thru 13 is ON board and change it.
C264 is not fully LED1 is blinking An IED is Go into IED display to determine
operational disconnected (LED the disconnected IED and verify the
6 and/or 12 ON) cable, the BIU configuration, the
com-munication parameters inside
the PACiS configurator, the
commu-nication parameters inside
the relay.
The printer is Go into Fault display and verify
disconnected that paper is available, the printer
is switch ON, the printer cable
A problem about Go into Fault display & verify that
clock the external clock is switch ON,
synchronisation the external clock is connected to
the antenna, the external clock is
connected to the C264.
A problem about Go into Fault display & connect
PLC (ISaGRAF) the ISaGRAF work bench to the
C264. Verify the behaviour of the
PLC.
NOTE: After a reboot using the CAT, the PSL might do not work. Use the
serial link instead and type ‘reboot’ in Hyperterminal.
2.1.2 Front panel LCD indications

GHU200 or GHU210 board gives access to the status of the boards, the state of digital
inputs, the state of digital outputs, the connection state with external devices. The CM
chapter describes this.
2.1.3 Adjustment of the brightness of the front panel LCD
When button and button are pressed simultaneously it is possible to
increase (resp. decrease) the brightness of the front panel LCD by pressing button
(resp. button )
2.2 Maintenance period

It is recommended that Schneider Electric products receive periodic monitoring after their
installation. Deterioration may occur over time. Because of the electrical and disturbed
environment, it is recommended to confirm at regular intervals that the MiCOM C264 is
operating correctly.
The Schneider Electric MiCOM C264/C264C has been designed for a life cycle of over 15
years.
MiCOM C264/C264C is self-supervising and therefore requires less maintenance than
previous products. Most problems will lead to an alarm so fast and appropriate action can be
done. However, some periodic tests should be done to ensure the MiCOM C264/C264C is
operating correctly and that the external wiring in a good condition.
If a Preventative Maintenance Policy exists within the customer’s organisation then the
recommended product checks should be included in the regular programme. Maintenance
periods will depend on many factors, such as:
• the operating environment
• the accessibility of the site
• the amount of available manpower
• the importance of the installation in the power system
• the consequences of failure

2.3 Method of repair
If the MiCOM C264/C264C should develop a fault whilst in service, depending on the nature
of the fault, the watchdog contacts will change state and an alarm condition will be flagged.
Due to the extensive use of surface-mount components (SMC) faulty boards should be
replaced, as it is not possible to perform repairs on damaged circuits with SMC technology.
Thus either the complete MiCOM C264/C264C or just the faulty board, identified by the in-
built diagnostic software, can be replaced.
The preferred method is to replace the complete MiCOM C264/C264C as it ensures that the
internal circuitry is protected against electrostatic discharge and physical damage at all times
and overcomes the risk of incoherency with the new boards. In some cases, it may be
difficult to remove an installed MiCOM C264/C264C due to limited access in the back of the
cubicle and rigidity of the scheme wiring then only the faulty elements will be replaced.
Replacing boards can reduce transport costs but requires clean, dry on site conditions and
higher skills from the person performing the repair. If an unauthorised service centre
performs the repair, the warranty will be invalidated.
BEFORE CARRYING OUT ANY WORK ON THE EQUIPMENT,

THE USER SHOULD BE FAMILIAR WITH THE CONTENTS OF THE
SAFETY AND TECHNICAL DATA CHAPTERS (SCHNEIDER ELECTRIC
SAFETY GUIDE: SFTY/4L M/G11 OR LATER ISSUE) AND THE RATINGS
ON THE EQUIPMENT'S RATING LABEL.
THIS SHOULD AVOID INCORRECT HANDLING OF THE ELECTRONIC
COMPONENTS AND DAMAGE.
2.3.1 Replacing the complete MiCOM C264/C264C
The case and rear terminal blocks have been designed to facilitate removal of the complete
MiCOM C264/C264C.
Before working at the rear of the MiCOM C264/C264C, isolate all the voltages and currents
connected to the MiCOM C264/C264C.
NOTE: The MiCOM C264/C264C have current transformer shorting switches
which close when terminal block is removed.
2.3.1.1 Replacing the complete MiCOM C264/C264C

Before any disconnection, check the labels correctly define the connectors and match with
the wishing description you have. Otherwise, note the current wiring in order to prepare the
new C264 installation.
1. Disconnect the power supply connector
2. Disconect the MiCOM C264/C264C IRIG-B, fibre optic, Ethernet RJ45 and serial links
connected on CPU board.
3. Disconnect the input/output connectors
4. Disconnect earth connection
There are two types of terminal block used on the MiCOM C264/C264C:
1 2 1
3 4 Connector
CT/VT fixation screw
Earthing
connection 5 6
7 8
9 10
11 12
13 14
15 16
17 18
19 20
21 22
23 24
Connector
fixation screw
25 26
27 28
24
C0112ENa
FIGURE 1: LOCATION OF SECURING SCREWS FOR TERMINAL BLOCKS

NOTE: The use of a magnetic bladed screwdriver is recommended to
minimise the risk of the screws being left in the terminal block or lost.
A 3 mm flat head screwdriver is recommended for fixation screws. A 6
mm flat head screwdriver is recommended for CT/VT earthing
connections.
Without exerting excessive force or damaging the scheme wiring, pull the terminal blocks
away from their internal connectors.
Remove the screws used to fasten the MiCOM C264/C264C to the panel, rack, etc. These
are the screws with the larger diameter cross heads that are accessible when the access
covers are fitted and open.
IF THE TOP AND BOTTOM ACCESS COVERS HAVE BEEN REMOVED,

DO NOT REMOVE THE SCREWS WITH THE SMALLER DIAMETER
HEADS WHICH ARE ACCESSIBLE. THESE SCREWS HOLD THE FRONT
PANEL ON THE MiCOM C264/C264C.
5. Withdraw the MiCOM C264/C264C from the panel or rack carefully and take care of
its weight because there are some heavy parts due to the internal transformers.
2.3.1.2 Installation of new C264

To reinstall the repaired or new MiCOM C264/C264C, follow the above previous in reverse.
Ensure that each terminal block is relocated in the correct position and the case correctly
earthed, IRIG-B and fibre optic connections are put back in place.
Once reinstallation is complete the MiCOM C264/C264C should be commissioned again
using the instructions in CM chapter.
2.3.2 Replacing a board
To replace any of the MiCOM C264/C264C’s boards it is necessary to remove the front
panel.
Before removing the front panel the auxiliary supply must be switched off. It is also strongly
recommended that the voltage and current transformer connections and trip circuit are
isolated.
Open the top and bottom access covers. With size 80TE cases the access covers have two
hinge-assistance T-pieces which clear the front panel moulding when the access covers are
opened by more than 120°, thus allowing their removal.
If fitted, remove the transparent secondary front cover. A description of how to do this is
given in Chapter C264/EN IT (Introduction).
By applying outward pressure to the middle of the access covers, they can be bowed
sufficiently so as to disengage the hinge lug allowing the access cover to be removed. The
screws that fasten the front panel to the case are now accessible.
The size 40TE case has four cross head screws fastening the front panel to the case, one in
each corner, in recessed holes. The size 80TE case has an additional two screws, one
midway along each of the top and bottom edges of the front plate. Undo and remove the
screws.
DO NOT REMOVE THE SCREWS WITH THE LARGER DIAMETER

HEADS WHICH ARE ACCESSIBLE WHEN THE ACCESS COVERS ARE
FITTED AND OPEN. THESE SCREWS HOLD THE MiCOM C264/C264C IN
ITS MOUNTING (PANEL OR CUBICLE).
When the screws have been removed, the complete front panel can be pulled forward and
separated from the metal case.
CAUTION SHOULD BE OBSERVED AT THIS STAGE BECAUSE A CABLE

CONNECTS THE FRONT PANEL TO THE REST OF THE MICOM
C264/C264C CIRCUITRY.
Additionally, from here on, the internal circuitry of the MiCOM C264/C264C is exposed and
not protected against electrostatic discharges, dust ingress, etc. Therefore ESD precautions
and clean working conditions should be maintained at all times.
FIGURE 2: MiCOM C264C WITH TMU2XX BOARD
FIGURE 3: MiCOM C264C WITHOUT TMU2XX BOARD

FIGURE 4: MiCOM C264 WITH TMU2XX BOARD
FIGURE 5: MiCOM C264 WITHOUT TMU2XX BOARD

The boards within the MiCOM C264/C264C are now accessible. Figures above show the
board locations for the MiCOM C264/C264Cs in size 40TE (C264C) and size 80TE (C264)
cases respectively.
Looking to the front of the MiCOM C264/C264C with the front panel off, you can have access
to a printed circuit that connects all the boards together: this is the backplane board.
To remove a card you need to:
• Pull the backplane board (FBP280 for C264 or FBP242 for C264C) out by holding it by
the two extremities.
• Remove the screws and the maintain bar at the bottom of the case.
NOTE: To ensure compatibility, always replace a faulty board with one of an
identical part number and set jumpers in identical position.
All the boards are shown and described in HW chapter.
2.3.2.1 Replacement of the Binary Input Unit (BIU241/261)
The BIU is the power supply board located on the extreme left-hand side (slot A) of MiCOM
C264/C264C.
Pull the power supply module forward, away from the rear terminal blocks and out of the
case. A reasonable amount of force will be required to achieve this due to the friction
between the contacts of the two medium duty terminal blocks. It is then recommended to use
the special tool for extracting board (internal reference is 2070860).
Do not forget to set the jumpers on the new board in the same position as the previous one.
2.3.2.2 Replacement of the main processor board (CPU260/CPU270)
Depending on the model of the MiCOM C264/C264C the processor board carried out the
IRIG-B functionality’s so if you identify an IRIG-B connection problem you will have to
replace the processor board.
After replacement of the main processor board, all the settings required for the application
will need to be re-entered.
The CPU board is located next to the BIU board (slot B).
Do not forget to disconnect the rear cables (RJ45 Ethernet, optical fibres, IRIG-B connector
and serial links) before replacing the board and to reconnect them after.
2.3.2.3 Replacement of the Ethernet switch boards (SWU20x or SWR20x or SWD20x)
The Ethernet switch board is located on slot C.
Do not forget to disconnect the rear cables (RJ45 Ethernet and optical fibres) before
replacing the board and to reconnect them after.
2.3.2.4 Replacement of the I/O boards (DIU200, DIU210, DIU211, DOU200, DOU201, CCU200,
CCU211, AIU201, AIU210, AIU211, AOU200 )
The I/O boards can be located in any slot from C to Q.
WARNING: The insert or extraction of the AOU200 board in skew could lead one capacity
(C27) to touch an iron corner. The manipulation of boards is to be done carefully.
2.3.2.5 Replacement of the Transducerless Measurements Unit (TMU)
The measurement unit is on the extreme right-hand side of MiCOM C264/C264C.
2.3.2.6 Refit the MiCOM C264/C264C

Before re-assembling the module with a replacement board, make sure that the address for
the replacement board is the same address that the board replaced by checking the jumpers
on the boards.
Refit the FBP board.
Screw the bar in the bottom of the case.
Refit the front panel. After refitting and closing the access covers, press at the location of the
hinge-assistance T-pieces so that they click back into the front panel moulding.
Once the relay has been reassembled after repair, it must be commissioned again (see
chapter CM).
2.4 Cleaning
Before cleaning the MiCOM C264/C264C ensure that all ac/dc supplies, current transformer
and voltage transformer connections are isolated to prevent any chance of an electric shock
whilst cleaning.
Front panel cleaning: use a smooth cloth. Do not use abrasive material or detergent
chemicals.
3. THE EMBEDDED MAINTENANCE WEB SERVER

The Maintenance Web server is only embedded in a CPU270 (also name CPU 3) board.
This server can be accessed via the Internet Network with a standard web browser (Internet
Explorer 5.0 minimum or Mozilla Firefox 1.5 minimum).
URL used to access the web server: http://<ip_address>/fs/index.htm. The operator has to
know the IP address of the C264 web server to establish the link.
Two level of access rights are defined depending on User name and associated password
according to the following table:
User name password Access rights

level1 level1 Maintenance data
level2 level2 Maintenance data and upload files
When operator connects to the webserver the following dialog box is displayed.
FIGURE 6: THE LOGIN DIALOG BOX

After correct name and password are entered the home page is displayed. The user can
choose the language (English / French / Deutch / Spanish) then select the information to be
displayed.
FIGURE 7: WEBSERVER HOME PAGE

3.1 Maintenance data pages

3.1.1 C264 general information page
This page gives the following information:
• the computer identification ( name, serial number, IP addresses for port 1 and 2)
• information about software ( version, date, database compatibility)
• the computer operating mode ( OPERATIONAL / MAINTENANCE / TEST)
• the computer operating mode ( ACTIVE / STANDBY / NO REDUNDANCY)
FIGURE 8: C264 GENERAL INFORMATION PAGE

3.1.2 Databases general information page

For each of the two databases this page gives the following information:
• name
• version
• status (STANDBY / CURRENT)
FIGURE 9: DATABASE GENERAL INFORMATION PAGE

3.1.3 Racks and boards status page

• the composition of the computer
• the status of each board ( configured and present / configured and absent / present
and not configured / faulty)
• the status ( valid ON / valid OFF) of the binary inputs of boards BIU241, DIU2x0,
DIU211, CCU200, CCU211 ( if configured and present)
• the status ( valid OPEN / valid CLOSE) of the binary outputs of boards BIU241,
DOU200, DOU201, CCU200, CCU211 ( if configured and present)
FIGURE 10: RACKS AND BOARDS STATUS PAGE

3.1.4 IED networks page

• list of the configured IEDs
• protocol type and port for each legacy bus
• status ( connected / not connected) of each IED
FIGURE 11: IED NETWORKS PAGE

3.1.5 CPU time and synchronisation page

3.1.5.1 CPU information
• the computer date and time
• the total functioning time
• Temperature
• Voltage
• year number stored in SRAM

3.1.5.2 IRIG-B information
• status ( present / not present)
• validity
• signal level
3.1.5.3 Synchronisation information
• UTC date
• local date
• time zone
• synchronism status ( synchronous / not synchronous)
• synchronism equipment active ( Operator / IRIG-B / RCP / Sbus)
• synchronism equipment present ( Present / Not present)
• synchronism equipment priority ( 0 to 3)
• System master clock ( Yes / No)

FIGURE 12: CPU TIME AND SYNCHRONISATION PAGE

3.2 Process data pages

When the user requests the display of one these pages the computer performs the
acquisition of all the related information ( binary inputs, measurement, counters, TPI) then
displays them ( date and time, name, status).
3.2.1 Binary inputs page
FIGURE 13: BINARY INPUTS PAGE

3.2.2 Measurements page
FIGURE 14: MEASUREMENTS PAGE

3.2.3 Counters page
FIGURE 15: COUNTERS PAGE

3.2.4 TPI page
FIGURE 16: TPI PAGE

3.3 Files upload pages

This page allows the operator to upload two types of files
3.3.1 Systrap error file upload page
FIGURE 17: SYSTRAP ERROR FILE UPLOAD PAGE
FIGURE 18: A SYSTRAP ERROR FILE

3.3.2 Stored event log file upload page
FIGURE 19: STORED EVENT LOG FILE UPLOAD PAGE
FIGURE 20: AN STORED EVENT LOG FILE

4. ENGINEERING MAINTENANCE OPERATION

The CAT software is able to:
• Upgrade the C264 software
• Download and switch the databases
• Download the software key

These functions are needed for customising the C264.
For details on the CAT, refer to the C264/EN IN chapter.
An Expert Maintenance involves the use of Hyperterminal; it is out of the scope of this
documentation.
To upload the VAL file to Micom S1, create a new register key. The name of the key is
“VERSION”. It is located under :
HKEY_LOCAL_MACHINE\Software\PACIS\MICOM S1\Settings\ The value of this
key can be 0 or 1. The default value is 1.
LEXICON
Page 1/14
CONTENT
2. LEXICON 4
C264/EN LX/C80 Lexicon
Page 2/14
BLANK PAGE
Page 3/14

This document is the last chapter of each PACiS documentation. It is the lexicon.
Page 4/14
2. LEXICON
AC Alternating Current
AccI Accumulator Input
ACSI Abstract Communication Service Interface
Mapping from the standard IEC61850 abstract specification of communication
service to a concrete communication infrastructure based on CORBA specific.
A/D Analog/Digital
ADC Analogue to Digital Converter
AE Application Entity qualifier (Used internally by IEC61850 to identify a server
qualifier Application)
AI Analogue Input (Measurement Value including state attribute)
Commonly Voltage or current DC signals delivered by transducers, and
representing an external value (refer to CT/VT for AC).
AIS Air Insulated Substation
AIU Analogue Input Unit (Computer C264 Board name for DC Analogue Input)
Alarm An alarm is any event tagged as an alarm during configuration phase
AO Analogue Output
Value corresponding to a desired output current applied to a DAC.
AOU Analogue Output Unit (computer C264 board name for Analogue Output)
API Application Programming Interfaces
AR Auto-Reclose
ARS Auto-Recloser
ASCII American Standard Code for Information Interchange
ASDU Application Specific Data Unit
Name given in OSI protocol for applicative data (T103, T101..)
ASE Applied System Engineering
ATCC Automatic Tap Change Control
Automation in charge of secondary voltage regulation, more specific than AVR
AVR Automatic Voltage Regulator
Automatism used to regulate secondary voltage by automatic tap changer
control (see ATCC). Set of features can be added, see chapter C264 FT
Bay Set of LV, MV or HV plants (switchgears and transformers) and devices
(Protective, Measurement…) usually around a Circuit Breaker and controlled
by a bay computer.
BCD Binary Coded Decimal
One C264 supported coding on a set of Digital Inputs, that determine a Digital
Measurement, then Measurement value (with specific invalid code when
coding is not valid). Each decimal digit is coded by 4 binary digits.
BCP Bay Control Point
Name given to the device or part used to control a bay. It can be Mosaic Panel,
C264 LCD,… Usually associate with Remote/Local control.
BCU Bay Control Unit
Name given to the C264 in charge of a bay. Usually in contrast with
Standalone
BI Binary Input (or Information)
Name given into Computer C264 of information already filtered, before it
becomes an SPS, DPS… with time tag and quality attributes
Page 5/14
BIU Basic Interface Unit

C264 Board for auxiliary power supply(ies), watchdog relay, redundancy I/O,
serial port(s).
BNC A connector for coaxial cable.
B-Watch Monitoring and control device for GIS substation.
CAD Computer Aided Design
Computer application dedicated to design like wiring, protective setting…
CAS CASe
Computer C264 rack
CB Circuit Breaker
Specific dipole switch with capability to make line current and break fault
current. Some have isolation capability (nominal-earth at each side)
CBC Compact Bay Controller
Small capacity bay computer for Medium Voltage applications typically C264C
CC Complemented Contact
CCU Circuit breaker Control Unit
Computer C264 Board dedicated to switch control with 8DI, 4 DO
CDM Conceptual Data Modelling
Is the modelling of system/devices data using a hierarchy of structured data
(called object of class) with their attributes, method or properties and the
relations between themselves. It maps common data to devices or components
of devices, with guaranty of interoperability.
Class Define in IEC61850 as: description of a set of objects that share the same
attributes, services, relationships, and semantics
Client Define in IEC61850 as: entity that requests a service from a server and that
receives unsolicited messages from a server
CM CoMissioning
CAT Computer Administration Tool
CO Command, logic information Output (Functional Component) / Contact Open
COMTRA Common Format For Transient Data Exchange (international standard IEC
DE 60255-24)
CPU Central Processing Unit
Computer C264 main Board based on PowerPC
CRC Cyclic Redundancy Check
Coding result send with packet of transmitted data to guarantee their integrity.
Usually result of a division of transmitted data by polynomial.
CSV Character Separate Values
ASCII values separated by predefined character or string like in Excel or ASCII
Comtrade.
CT Current Transformer
Basically the electric device connected to process and extracting a current
measurement. By extension part of a device (C264) that receives AC values
and convert it to numerical measurement value.
CT/VT Current and Voltage transformers
(Conventio By extension, it is the C264 TMU board.
nal)
CT/VT Current and Voltage transformers
(Non- New generation of captor based for example on light diffraction under electric
Conventio field, without transformer, that gives directly numerical measurement of voltage
nal or and current like communicating IED.
intelligent)
Page 6/14
CSV Character Separate Values

Asci values separated by predefined character or string like in Excel or ASCII
Comtrade.
DAC Data Acquisition component of the GPT
DAC Digital to Analogue Converter
Used to generate analogue signals (usually DC) from a digital value.
DB DataBase
Tool or set of data that define all configuration of a system or specific device
like computer. Opposed to setting or parameter DB has a structure that can not
be modified on line. DB are always versioned.
DB-9 A 9-pin family of plugs and sockets widely used in communications and
computer devices.
DBI Don’t Believe It
Term used for undefined state of a double point when input are not
complementary. DBI00 is state motion or jammed. DBI11 is undefined.
DBID Databases Identity Brick
DC Direct Current
DC, DPC Double (Point) Control
Two digit and/or relays outputs used for device control with complementary
meaning (OPEN, CLOSE).
DCF77 External master clock and protocol transmission
LF transmitter located at Mainflingen, Germany, about 25 km south-east of
Frankfurt/Main, broadcasting legal time on a 77.5 kHz standard frequency.
DCO Double Control Output
DCP Device Control Point
Located at device level (electric device or IED). It should have its own
Remote/Local switch.
DCS Digital Control System
Generic name of system based on numeric communication and devices, to be
opposed to traditional electrically wired control.
DCT Double CounTer
Counter based on 2 DI with complementary states (counting switchgear
manoeuvre for example)
DE Direct Execute
DELTA Phase to phase delta values
Device Term used for one of the following unit:
Protective relays, metering units, IED, switchgear (switching device such as
CB, disconnector or earthing switch), disturbance or quality recorders.
DHMI C264 Display HMI
DI Digital Input
Binary information related to the presence or to the absence of an external
signal, delivered by a voltage source.
DIN Deutsche Institut für Normung
The German standardisation body.
DIU DC Input Unit
Computer C264 Board name for Digital Input
DLL Dynamic Link Library. Available on Windows XP.
A feature that allows executable code modules to be loaded on demand and
linked at run time. This enables the library-code fields to be updated
automatically, transparent to applications, and then unloaded when they are no
longer needed.
Page 7/14
DM Digital Measurement
Is a measurement value which acquisition is done by DI and a specific coding
BCD, Gray, 1 among N…
DNP3.0 Distributed Network Protocol
DNP3 is a set of communication protocols used between components in
process automation systems.
DO Digital Output
Used to apply a voltage to an external device via a relay, in order to execute
single or dual, transient or permanent commands.
DOF Degree Of Freedom
Used for a template attribute, that can be modified or not when used. An attri-
bute has a degree of freedom if a user can modify its values on its instances
DOU Digital Output Unit
Computer C264 Board name for Digital Output
DP Double Point
Information/control derived from 2 digital inputs/output; usually used for
position indication of switching devices (OPEN, CLOSE).
DPC Double Point Control
DPS Double Point Status
Position indication of switching devices (OPEN, CLOSE).
ECDD Coherent Extract of Distributed Data
ECU Extended Communication Unit.
External module connected to the CPU board. This module converts non-
insulated RS232 into optical signal or insulated RS485/RS422.
EH90 Transmission protocol dedicated to time synchronisation and standardised by
EDF. Specification document: D.652/90-26c, March 1991.
EMC Electro-Magnetic Compatibility
EPATR Ensemble de Protection Ampèremétrique de Terre Résistante (French Legacy
very resistive earth current module)
Event An event is a time tagged change of state/value acquired or transmitted by a
digital control system.
FAT Factory Acceptance Test
Validation procedures execution with the customer at factory.(i.e. SAT)
FBD Functional Block Diagram
One of the IEC61131-3 programming languages (language used to define
configurable automation).
FIFO First In First Out
FO Fibre Optic
FP Front Panel
FTP Foil Twisted Pair
FLS Fast Load Shedding
FSS Force Suppress Substitute
Gateway Level 6 session of OSI, the gateway is any device transferring data between
different networks and/or protocol. The RTU function of the C264 gives a
gateway behaviour to SCADA or RCP level. PACIS Gateway is separate PC
base device dedicated to this function.
GHU Graphic Human interface Unit
Computer C264 Front Panel digital part (LCD, buttons, Front RS)
GIS Gas Insulated Substation
Page 8/14
GLOBE GLOBE Brick

GMT Greenwich Mean Time
Absolute time reference
GPS Global Positioning System
Based on triangulation from satellite signal, that transmit also absolute GMT
time used to synchronise a master clock
GOOSE Generic Object Oriented Substation Event
GPT Generic Protocol Translator software, supplied by ASE
Group Logical combination of BI (i.e. SP, DP, SI or other groups).
GSSE Generic Substation Status Event
Hand Facility for an operator to set manually the position of a device (acquired by
Dressing other means) from the HMI at SCP level; e.g. from OPEN to CLOSE (without
any impact on the “physical” position of the electrical switching device).
HMGA Horizontal Measurement Graphical Area
HMI Human Machine Interface
Can be PACIS OI (Operator Interface) or C264 LCD (Local Control Display) or
Leds, mosaic...
HSR High Speed auto-Recloser, first cycles of AR
HTML Hyper Text Mark-up Language
Used as standard for formatting web display
HV High Voltage (for example 30kV to 150kV)
I/O Input/Output
ICD IED Capability Description
IEC International Electro-technical Commission
IED Intelligent Electronic Device
General expression for a whole range of microprocessor based products for
data collection and information processing
IP Internet Protocol
IRIG-B Inter-Range Instrumentation Group standard format B. This is an international
standard for time synchronisation based on analogue signal.
JAMMED Invalid state of a Double Point:
Occurs when the 2 associated digital inputs are still in state 0 after an user-
selectable delay, i.e. when the transient state “ motion ” is considered as ended
Kbus Term used for the protocol Courier on K-Bus network (kind of RS422).
(Kbus
Courier)
LAN Local Area Network
L-BUS Legacy Bus
Generic name of Legacy or field networks and protocols used to communicate
between C264 (Legacy Gateway function) and IED on field bus. Networks are
based on (RS232,) 422, 485. Protocols are IEC 60850-5-103 (T103 or VDEW),
Modbus Schneider Electric or MODICON
LCD Liquid Crystal Display or Local Control Display (on C264)
LD Ladder Diagram, one of the IEC1131-3 programming languages (language
used to define configurable automation).
LED Light Emitting Diode
LF Low Frequency
Page 9/14
LOC Local Operator Console

Dedicated to maintenance operation
L/R Local / Remote
Local / When set to local for a given control point it means that the commands can be
Remote issued from this point, else in remote control are issue for upper devices.
Control
Mode
LSB Least Significant Bit
LSP Load Shedding Preselection
LV Low Voltage
MAFS Marketing And Functional Specification
MC Modular Computer
MCB Mini Circuit Breaker. Its position is associated to tap changer.
MDIO Management Data Input/Output
A standard driven, dedicated-bus approach that is specified in IEEE802.3
Measurem Values issued from digital inputs or analogue inputs (with value, state, time tag)
ents
Metering Values computed depending on the values of digital or analogue inputs during
(non-tariff) variable periods of time (time integration).
Metering Values computed depending on the values of digital or analogue inputs during
(tariff) variable periods and dedicated to the energy tariff. These values are provided
by dedicated “tariff computer ” which are external to the MiCOM Systems.
MIDOS Schneider Electric Connector: Used for CT/VT acquisition
MMC Medium Modular Computer
MMS Manufacturing Message Specification (ISO 9506)
ModBus Communication protocol used on secondary networks with IED or with SCADA
RCP. 2 versions exist with standard MODICON or Schneider Electric one.
Module Word reserved in PACIS SCE for all electric HV devices. It groups all switch-
gears, transformer, motors, generators, capacitors, …
MOTION Transient state of a Double Point
Occurs when the two associated digital inputs are momentarily in state 0 (e.g.
position indication when an electrical device is switching). The concept of
“momentarily” depends on a user-selectable delay.
MPC Protection Module for Computer
MV Medium Voltage
MVAR Mega Volt Ampere Reactive
NBB Numerical Busbar Protection
NC Normally Closed (for a relay)
NO Normally Open (for a relay)
OBS One Box Solution
Computer that provides protection and control functions with local HMI. The
prime application of this device is intended for use in substations up to
distribution voltage levels, although it may also be used as backup protection in
transmission substations. Likewise, the OBS may be applied to the MV part of
a HV substation that is being controlled by the same substation control system.
OI Operator Interface
OLE Object Linking and Embedding
OLE is a Microsoft specification and defines standards for interfacing objects.
Page 10/14
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 Sum of time periods, a primary device is running under carrying energy, e.g.
hours circuit breaker is in Close state and the current is unequal 0 A.
OSI Open System Interconnection
Split and define communication in 7 layers : physical, link, network, transport,
session, presentation, application
OWS Operator WorkStation (PACiS OI)
PACiS Protection, Automation and Control Integrated Solutions
PLC Programmable Logic Control /Chart. Includes PSL and ISaGRAF
Within the PLC-programs are defined the configurable control sequences or
automations taken into account by the MiCOM Systems.
POW Point On Wave
Point on wave switching is the process to control the three poles of an HV-
circuit breaker in a way, to minimise the effects of switching.
PSL Programmable Scheme Logic
PSTN Public Switched Telephone Network
RCC Remote Control Centre
Is a computer or system that is not part of MiCOM system. RCC communicates
with and supervises MiCOM system using a protocol.
RCP Remote Control Point
Name given to the device or part used to control remotely several bay or sub-
station. Usually associated with Remote/Local sub-station control. It is a
SCADA interface managed by the MiCOM system through Telecontrol BUS.
Several RCPs can be managed with different protocols.
Remote When set for a control point it means that the commands are issued from an
Control upper level and are not allowed from this point.
Mode
Remote Remote HMI is a client of the substation HMI server. The client may provide all
HMI or part of functions handled by the substation HMI.
RI Read Inhibit
This output indicates the availability of an analogue output (e.g. during DAC
converting time)
RJ-45 Registered Jack-45
A 8-pin female connector for 10/100 Base-T Ethernet network
RMS Root Mean Square
RRC Rapid ReClosure
RSE Régime Spécial d’Exploitation
French grid function when works are being done on a HV feeder
RSVC Relocatable Static Var Compensator
RS-232 Recommended Standard 232
A standard for serial transmission between computers and peripheral devices.
RS-422 A standard for serial interfaces that extends distances and speeds beyond RS-
232. Is intended for use in multipoint lines.
RS-485 A standard for serial multipoint communication lines. RS-485 allows more
nodes per line than RS-422
Page 11/14
RSVC Relocatabled Static Var Compensator

RTC Real Time Clock
RTU Remote Terminal Unit
Stand alone computer that acquires data and transmit them to RCP or SCADA.
Typically it is the C964. RTU link is the TBUS.
SAT Site Acceptance Test
Validation procedures executed with the customer on the site.
SBMC Site Based Maintenance Control mode
A bay in SBMC mode does not take into account the commands issued from
RCP; moreover, some of its digital points & measurements (defined during the
configuration phase) are not sent anymore to the RCP (they are
“automatically” suppressed).
SBO Select Before Operate
A control made in two steps, selection and execution. Selection phase give a
feedback. It can be used to prepare, reserve during time, configure circuit
before execution. Controls are done into a protocol, or physical (DO select with
DI Select then DO execute).
S-BUS Station Bus, federal network between PACIS devices.
SCADA Supervisory Control And Data Acquisition
Equivalent to RCC
SCD Description file extension (SCE)
SCE System Configuration Editor
SCL substation automation System Configuration Language (IEC 61850-6)
SCP Substation Control Point
Name given to the device or part used to control locally several bays or sub-
station. Usually associated with Remote/Local sub-station control. It is
commonly PACIS Operator Interface.
SCS Substation Control System
SCSM Specific Communication Service Mapping
SCT Single Counter
SER Sequence of Event Recorder
Combines SOE with accurate Time synchronization and Maintenance facilities
over Ethernet communication
Server Define in IEC61850 as: entity that provides services to clients or issues
unsolicited messages
Setpoints Analogue setpoints are analogue outputs delivered as current loops. Analogue
(analogue) 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) represent a bit of the value. Digital setpoints are used to send instruction
values to the electrical process or to auxiliary devices.
SFC Sequential Function Chart
One of the IEC1131-3 programming languages (language used to define
configurable automation).
SI System Indication
Binary information that do not come from external interface. It is related to an
internal state of the computer (time status, hardware faults…). It is the result of
all inner function (AR, …), PSL, or ISaGRAF automation.
SICU 4 Switchgear Intelligent Control Unit
Control unit of an intelligent circuit breaker (fourth generation)
SIG Status Input Group
Page 12/14
SINAD Signal-plus-Noise-plus-Distorsion to Noise-plus-Distorsion ratio, in dB

SIT Status Input Double Bit
SNTP Simple Network Time Protocol
SOE Sequence Of Events
Other term for the event list.
SP Single Point
SPS Single Point Status
SPC Single Point Control
ST Structured Text
An IEC1131-3 programming languages to define configurable automation
STP Shielded Twisted Pair
Substation Bay computer used at substation level
computer
Suppression A binary information belonging to a bay in SBMC mode will be automatically
(Automatic) suppressed for the remote control. However changes of state will be signalled
locally, at SCP
Suppression A binary information can be suppressed by an order issued from an operator.
(Manual) No subsequent change of state on a “suppressed information ” can trigger any
action such as display, alarm and transmission
SWR Switch Redundant
Computer C264 board Ethernet switch with redundant Ethernet
SWU Switch Unit (Computer C264 board Ethernet switch)
T101 Term used for IEC60870-5-101 protocol
TBC / TBD To Be Completed / Defined
T-BUS Telecontrol Bus, generic name of networks and protocols used to communicate
between PACIS Gateway or C264 Telecontrol Interface function and the RCP.
Networks are based on RS232, 485, or Ethernet (T104). Protocols are IEC
60850-5-101 (T101), Modbus MODICON
TC True Contact
TCIP Tap Changer in Progress
TCU Transformer Current Unit
Computer C264 CT/VT Board : Current acquisition
TDD Total Demand Distorsion, similar to the THD but applied to currents and with a
rated current (In) as reference
TG Telecontrol Gateway
THD Total Harmonic Distorsion, sum of all voltage harmonics
TI Tele Interface
TM Analogue Measurement
TMU Transducerless Measurement Unit
Topological Interlocking algorithm, based on evaluation of topological information of the
interlocking switchgear arrangement in the HV network, the switchgear kind and position, &
defined rules for controlling this kind of switch (e.g. continuity of power supply)
TPI Tap Position Indication (for transformers).
Frequently acquired via a Digital Measurement
TS Logic position
Page 13/14
TVU Transformer Voltage Unit (computer C264 CT/VT Board : Voltage acquisition)
UCA Utility Communications Architecture
Communication standard (mainly US) used for PACIS SBUS communication
UPI Unit Per Impulse
Parameter of counter to convert number of pulse to Measurement value. Both
data (integer and scaled float) are in common class UCA2 Accumulator.
UTC Universal Time Co-ordinates (or Universal Time Code)
Naming that replace GMT (but it is the same)
VdBS Versioned data Base System, databag generated by SCE & ready to download
VDEW Term used for IEC60870-5-103 protocol
VMGA Vertical Measurement Graphical Area
Voltage Set of bays whose plants & devices are dealing with same voltage (e.g. 275kV)
level
VT Voltage Transformer
Basically the electric device connected to process and extracting a voltage
measurement. By extension part of a device (C264) that receives this AC value
and convert it to numerical measurement value. VT are wired in parallel.
WTS Windows Terminal Server, Microsoft’s remote desktop connection
WYE Three phases + neutral AI values
Page 14/14
BLANK PAGE
ANNEX C264/EN AN/C80
MiCOM C264/C264C
ANNEX:
COMMUNICATION
ETHERNET SWITCHES
Annex: SW Communication C264/EN AN/C80
CONTENT
1. INTRODUCTION 3
1.1 MiCOM C264 Ethernet Switch boards 3
1.2 Ethernet Switch names 3
1.3 C264 Ethernet switch boards 3
2. SWR21X RANGE - DUAL RING ARCHITECTURE 4

2.1 Fast redundant ring capability 4
2.1.1 Self healing ring 4
2.1.2 Ethernet switch with Self-healing ring facilities 5
2.1.3 Schneider Electric Ethernet ring redundancy 5
2.1.4 Ethernet system performances 6
2.1.5 Max time of end to end delay 6
2.1.6 Benefits 7
2.2 SNMP Management 7
2.2.1 SWR21x - MIB Structure 7
2.2.2 SNMP Client Software 8
2.3 SWR21x Leds 9
2.3.1 LEDs 9
2.4 Settings 10
2.4.1 Internal Jumpers 10
2.4.2 Address of the board : 10
2.4.3 How to configure the address ? 10
2.4.4 IP Address of the repeater 11
2.5 Connections 11
2.5.1 J14 Fault signal output 11
3. SWD21X RANGE - DUAL HOMING ARCHITECTURE 12

3.1 Dual homing typical architecture 12
3.2 Dual homing Switch Description 13
3.3 Dual Homing Features 13
3.3.1 10Base T and 100Base Tx 13
3.3.2 Power management 13
3.3.3 Address look up 13
3.3.4 Back pressure for half duplex 13
3.3.5 Auto Negotiation and Speed-Sensing 13
3.3.6 Forwarding 13
3.3.7 Priority tagging 14
3.3.8 Flow control 14
3.4 SNMP Management 14
C264/EN AN/C80 Annex: SW Communication
3.5 SWD21x Leds 14

3.5.1 LEDs 15
3.6 Settings 15
3.7 Connections 16
3.7.1 J14 Fault signal output 16
4. SWU20X RANGE - STAR ARCHITECTURE 17

4.1 Ethernet Port Characteristics 17
4.1.1 10/100BaseTx Port 17
4.1.2 100BaseFx Multi Mode Port 17
4.1.3 100BaseFx Single or Mono Mode Port 17
4.2 Ethernet Port Switching Features 18
4.2.1 10BaseTx and 100BaseTx 18
4.2.2 100Base Fx 18
4.3 Ethernet Management 18
4.3.1 Address look up 18
4.3.2 Buffering 18
4.3.3 Back off operation 18
4.3.4 Back pressure for half duplex 18
4.3.5 Broadcast storm protection 18
4.3.6 Auto Negotiation and Speed-Sensing 18
4.3.7 Forwarding 18
4.3.8 Priority tagging 18
1. INTRODUCTION
MiCOM C264 Ethernet switches are designed to address the needs of a wide range of
electric plant. Emphasis has been placed on strong compliance to standards, scalability,
modularity and open architecture.
These facilitate use in a range of applications from the most basic to the most demanding.
They also ensure interoperability with existing components.
Schneider Electric philosophy is to provide a range of Ethernet products like switch that
match all general requirements needed in electric substation: power supply, immunity to
environmental constraints.
It provides also solutions to specific requirement like for example network redundancy
management and high availability performances.
Each of these boards can be used in MiCOM C264 “standalone” application or can be
integrated to a Digital Control System (DCS) (as PACIS) or to various kind of systems and
SCADA architectures.
1.1 MiCOM C264 Ethernet Switch boards
Driven by the requirements around the world for advanced applications in SCADA, Digital
Control Systems, Automation, control and monitoring, Schneider Electric has designed and
still developing a complete range of products that communicate via Ethernet links.
Electric plant requirements lead to constraints that are rarely full-filled by standard Ethernet
products: environmental, power supply, redundancy, etc.
This new MiCOM range of Ethernet switch, the MiCOM Hxxx and SWxxx has been specially
tailored for the PACiS system. The MiCOM Hxxx and SWxxx range is designed to address
the needs of a wide range of installations, from small to large and customer applications.
1.2 Ethernet Switch names
Basically the naming of Ethernet switch boards depends on its facilities and its interface:
copper, optical single-Mode, optical Multi-Mode.
The existing devices are:
• SWU2xx Ethernet Switch board for Ethernet Star Architecture
• SWR2xx Ethernet Switch board for Ethernet Dual Ring Architecture
• SWD2xx Ethernet Switch board for Ethernet Dual Star Architecture

1.3 C264 Ethernet switch boards
The SWxxx Ethernet switch board range is composed of managed switches, easy to install
and operate, designed to be implemented in an electric plant environment (IEC 61000-4 &
60255-5).
On the media side, the range supports 10BaseT, 100BaseTX and 100BaseFX as specified
by the IEEE 802.3 committee. Management of the full duplex is available for 100BaseTx or
100BaseFx.
To adapt the switch to your application you have to configure the necessary parameters with
“jumpers” located on the board.
2. SWR21X RANGE - DUAL RING ARCHITECTURE

The SWR21x range is dedicated for fast redundant Ethernet ring. All SWR21boards have 4
Copper connections through RJ45, with speed automatically adjusted from external emitters
to 10 or 100 Mbps.
Copper Ethernet link is limited in distance and subject to perturbation. The Ethernet
redundant ring is based on optical inter-switch connection, depending on the link length. The
user may choose between Multi-mode Fibre optic, or Single mode Fibre Optic for long
distance.
Model Description Connectors

SWR212 Fast Ethernet industrial switch 4 x RJ45
(Ref: 2071646 A01) Multimode 1300 nm 2 x ST
SWR214 Fast Ethernet industrial switch 4 x RJ45
(Ref: 2071646 A02) Single mode 1310 nm 2 x SC
2.1 Fast redundant ring capability

2.1.1 Self healing ring
Ethernet switches learn MAC addresses in order to switch packets to their destination port,
and save the addresses in their memory as long as they are active. If a MAC address
ceases to be active, it is aged out of the switch memory after a few minutes.
This switch-address- ageing delay presents a problem when a LAN needs to be reconfigured
quickly.
There is no benefit to having a fast ring recovery technique if the switch members of the ring
prevent Ethernet traffic from moving to the recovery traffic path.
With the Schneider Electric redundant ring without or with ring default the all switch on the
ring sees no difference in the advance of the frame ; no reset switch, no relearning for the
MAC address.
MiCOM H35 MiCOM H35
MiCOM H15 MiCOM H15
S0204ENa
FIGURE 1: SELF-HEALING RING MECHANISM

2.1.2 Ethernet switch with Self-healing ring facilities

The SWR21x is a “repeater” with a standard 802.3 Ethernet switch plus the self healing
manager (SHM). The following drawing describes the internal architecture of such device.
Ethernet Ports 10/100 Base TX
MDIO bus FLASH

SWITCH
Port MII
SHM N°
Failsafe Self healing ring
output relays manager
100Mbs Full duplex

opto opto
Primary Fiber
Secondary Fiber
Optical Ring
C0420ENa
FIGURE 2: INTERNAL ARCHITECTURE OF SWR21

2.1.3 Schneider Electric Ethernet ring redundancy
The SHM functions manage the ring. If the optic Fibre connection between two devices is
broken, the network continues to run correctly.
During nominal situation, Ethernet packet goes in primary Fibre always in the same direction,
and only a checking frames (4 bytes) is sent every 5μs in secondary Fibre in the opposite
direction.
If link is cut, both SHM start immediately the network self-healing. At one side messages
receive are no more emitted to the primary fibre but to the secondary fibre. On the other side
of the cut off, messages received to secondary are emitted to primary and the new
topological loop is closed.
Thanks to this property it is possible to extend the number of equipments or the size of a
sub-station without stopping exploitation. When the loop is open, new equipments are
connected on one side and the redunded loop is closed.
To increase the reliability some specific mechanisms are used:
• Watching the quality of transmission. Each frame (Ethernet packet or checking frame)
is controlled by the SHM. A detection of large error rate will eliminate the faulty link
and start automatically the self healing,
• Supervising the link same in the absence of traffic on the primary link (every 5 μs
checking frames are sending to test the link). The link is supervised permanently with
the real frame.
2.1.4 Ethernet system performances
Primary fiber
1 2 3 4 5 6 7 8 9 10 11
switch switch switch

switch switch
RP EP
C D E
A B
ES RS
Secondary fiber S0206ENa
FIGURE 3: NOMINAL REDUNDANT ETHERNET RING ARCHITECTURE

WITH MiCOM SWR21X AND HX5X SWITCHES
Primary fiber
1 2 3 4 5 6 7 8 9 10 11
switch switch switch

switch switch
RP EP
C D E
A B
ES RS
Secondary fiber S0207ENa
FIGURE 4: ETHERNET RING ARCHITECTURE

WITH MiCOM SWR21X AND HX5X SWITCHES, AFTER FAILURE
2.1.5 Max time of end to end delay
To calculate the time end to end you must to used the following table based on the nominal
situation:
Send a Goose frame from…. Time at

Abr. Comments
To… 100Mbps
IED 1 to Switch A 22 μs 262 bytes + inter-frame
Switch A to IED 2 22 μs Store and forward mechanism
Switch A to the network 2 μs tl Repeater latency time
Propagation time on the fibre μs 4,8 μs /km
Network to network 2 μs tl Repeater latency time
When the frame circulates on the ring it does not cross the switch the transit time is only tl.
2.1.6 Benefits
• Ultra fast ring redundant capability (< 1ms for network reconfiguration)
• Fast propagation on the ring (no transfer time (Store and forward mechanism ) with
the switch)
• No central redundancy manager
• Specific mechanism of frames checking
• Ring management
2.2 SNMP Management
Simple Network Management Protocol is the network protocol developed to manage devices
on an IP network. With SNMP the available information is defined by Management
Information Bases (MIB). The format of SNMP data takes the form of a tree structure, with
each node in the tree being identified by a numerical Object IDentifier (OID). Each OID
identifies a variable that can be read or set via SNMP with an appropriate software. The
information in the MIBs is standardised.
2.2.1 SWR21x - MIB Structure
The SNMP MIB consists in distinct OIDs; each of them refers to a defined collection of
specific information used to manage devices on the Schneider Electric’ ring. The
Schneider Electric MIB uses three types of OID.
System:
Address Name
0 Ccitt
1 ISO
3 Org
6 DOD
1 Internet
2 mgmt
1 Mib-2
1 sys
1 sysDescr Schneider Electric repeater
2 sysObjectID Optical Link Status :
1 – No Default
2 – Default Rs
3 – Default Rp
4 – No Link
3 sysUpTime The time (in hundredths of a
second) since the switch was last
re-initialized.
4 sysContact
5 sysName SWR21
6 sysLocation
RMON:
Address Name
0 Ccitt
1 ISO
3 Org
6 DOD
1 Internet
2 mgmt
1 Mib-2
16 Rmon
1 stat
1 etherstat
1 Port number (*)
9 etherStatsIndex etherStatsUndersizePkts
10 etherStatsIndex etherStatsOversizePkts
12 etherStatsIndex etherStatsJabbers
13 etherStatsIndex etherStatsCollisions
14 etherStatsIndex etherStatsPkts64Octets
15 etherStatsIndex etherStatsPkts65to127Octets
18 etherStatsIndexetherStatsPkts512to1023Octets
19 etherStatsIndexetherStatsPkts1024to1518Octets
*Port number: 1 to 4: standard ports
5 and 6: ports for redundant ring
2.2.2 SNMP Client Software

MIB Browser Software enables to perform all the basic SNMP operations, such as GET,
GETNEXT, RESPONSE, A very simple SNMP Client software is sufficient for using the
Schneider Electric MIB in Schneider Electric range of switches.
2.3 SWR21x Leds

LEDs are used to indicate the state of SWR21 and of the links. They are dedicated to Expert
Maintenance.
2.3.1 LEDs
The table below indicates the function of each LED:
LED N° Color Description

E1 default L1 Red E1 Default
Link Rp L2 Green Rp (Reception Primary) Link OK
Receive Rp L3 Green Traffic detected
E2 default L4 Red E2 Default
Link Rs L5 Green Link OK
Receive Rs L6 Green Traffic detected
Number of switch detected on the ring bit 0 L7 Green
Link and activity port 1 L15 Green Off : no connection
Green : link
Green + blink : link + activity
Link and activity port 2 L16 Green “

Speed port 1 L20 Green Off: 10Mbps
Green : 100Mbps
Speed port 2 L21 Green “
Speed port 5 L24 Green Port not used
Upon power up the SWR21xx will go through a series of self-testing. The 5 “link LED” will
flash a few seconds.
2.4 Settings
2.4.1 Internal Jumpers
OPEN CLOSE
Status is “closed” when the jumper is setted.
N° Open Closed Factory setting

J10-1 Board address bit 1 = 1 Board address bit 1 = 0 Closed
2.4.2 Address of the board :

Each board on the ring has a specific address. Each address must be single and included
between 1 and 127.
2.4.3 How to configure the address ?
The address is equal to the sum of the « open bits ».
At the beginning address = 0
If J10-1 = open address = address + 1 if not address = address + 0
Example :
J10-1 = open address = address + 1
J10-3 = close address = address + 0
Address = 11
2.4.4 IP Address of the repeater

The repeater IP address is accomplished in the following way:
FIGURE 5: IP ADDRESS
Note: It is important to note that the Schneider Electric_Switch_manager Software
forces the third IP field to “254” value.
2.5 Connections
2.5.1 J14 Fault signal output
The optical ring is monitored. If one link come down the default is announced by the
contacts:
1 Self healing Rp-Es
2 Common
1 2 3 3 Self healing Rs-Ep
Closed if Self-healing
C0121ENb
FIGURE 6: J14 PIN OUT

3. SWD21X RANGE - DUAL HOMING ARCHITECTURE

The SWD21x range of Ethernet boards is dedicated to Dual Ethernet Star architecture and
defined by the type of Ethernet optical fibre it is connected (Single Mode or Multi Mode). All
equipment of the SWD21x range has 4 Copper connections through RJ45, with speed
automatically adjusted from external emitters to 10 or 100 Mbps, and 2 Ethernet optical ports
with dual homing mechanism.
The Ethernet dual homing star is based on optical connection; depending on the link length.
The user may choose between Multi-mode optic fibre (up to 2 km) and Single mode optic
fibre (up to 20 km) for long distance.
SWD212 Fast Ethernet industrial switch 4 x RJ45

(Ref: 2071647 A01) Multimode 1300 nm 2 x ST
SWD214 Fast Ethernet industrial switch 4 x RJ45

(Ref: 2071647 A02) Single mode 1310 nm 2 x SC
3.1 Dual homing typical architecture

3.2 Dual homing Switch Description
Ethernet Ports 10/100 Base TX
MDIO bus EEPROM

SWITCH
Port MII
SHM N°
Failsafe Self healing ring
output relays manager
100Mbs Full duplex

opto opto
Link A Dual Homing
Link B Dual Homing

Dual Homing optical Links
C0421ENa
3.3 Dual Homing Features

3.3.1 10Base T and 100Base Tx
The copper ports are full/half duplex and auto-sense the transmission speed. They will auto-
negociate with the connected device to determinate the optimal speed. When the connected
device is only capable of transmitting at 10Mbps, the switch follows the 10Mbps.
3.3.2 Power management
If there is no cable on a port, most of the circuitry for that port is disabled to save power.
3.3.3 Address look up
Each Ethernet device inserts its unique “MAC address” into each message it send out. The
port on the switch used for given MAC address is automatically learned when a frame is
received from that address. Once an address is learned, the switch will route messages to
only the appropriate port. A time stamp is also placed in memory when a new address is
learned. This time stamp is used with the aging feature, which will remove unused MAC
Addresses from table after 300 seconds. The broadcasting messages are transmit in the all
ports.
Up to 2048 MAC addresses can be stored and monitored at any time.
3.3.4 Back pressure for half duplex
The MICOM SWD2xx will apply « back pressure » when necessary with half-duplex
operation. This «back pressure » will reduce congestion on busy networks .
3.3.5 Auto Negotiation and Speed-Sensing
All six RJ45 ports independently support auto negotiation for speeds in the 10BaseT and
100BaseTx modes. Operation is according to the IEEE 802.3u standard.
3.3.6 Forwarding
The MICOM SWD2xx support store and forward mode. It will forward messages with know
addresses out only the appropriate port. Messages with unknown addresses, broadcast
messages and multicast messages will get forwarded out all ports except the source port.
The switch will not forward error packets, 802.3x pause frames or local packets.
3.3.7 Priority tagging

802.1p priority is enabled on all ports.
3.3.8 Flow control
The MiCOM SWD2xx automatically supports standard flow control frames on both the
emission and reception sides.
On the reception side, if the switch receives a pause control frame it will not transmit the next
normal frame until the timer, specified in the pause control frame, expires. If another pause
frame is received before the current timer expires, the timer will be updated with the new
value in the second pause frame. During this period (being flow controlled), only flow control
packets from the switch will be transmitted.
On the transmission side, the switch has intelligence and determines when to invoke the flow
control. The flow control is based on availability of the system resources, including available
buffers, available transmission queues and available reception queues. The switch will flow
control a port, which just received a packet, if the destination port resource is being used up.
The switch will issue a flow control frame (XOFF), containing the maximum pause time
defined in IEEE standard 802.3x. A hysteresis feature is provided to prevent flow control
mechanism from being activated and deactivated too many times.
The switch will flow control all ports if the reception queue becomes full.
3.4 SNMP Management
For SNMP Management description, report to §2.2.
3.5 SWD21x Leds
LEDs are used to indicate the state of SWD21x and of the links. They are dedicated to
Expert Maintenance.
Front Panel Rear Panel
R link A
E link A
R link B
E link B
J10:
Adress of
repeater
J12:
Reserved
C0425ENa
3.5.1 LEDs
The table below indicates the function of each LED:

Link A fault L1 Red Fault on link A
Link A reception L2 green Reception Link A
Link A traffic L3 Green Traffic on Link A
Link B fault L4 Red Fault on Link B
Link B reception L5 Green Reception Link B
Link B traffic L6 Green Traffic Link B
Switch Number bit 0 L7 Green
Link and activity port 1 L15 Green Off: no connection
Green: link
Green + blink: link + activity
Link and activity port 2 L16 Green «
Speed port 1 L20 Green Off: 10Mbps
Green: 100Mbps
Speed port 2 L21 Green «
Speed port 5 L24 Green Port not used
Upon power up the SWD21 will go through a series of self-testing. The 5 “link LED” will flash
a few seconds.
3.6 Settings
Report to § 2.4.
3.7 Connections
3.7.1 J14 Fault signal output
The optical health is monitored. If one link come down the default is announced by the
contacts:
1 Self healing Rp-Es
2 Common
1 2 3 3 Self healing Rs-Ep
Closed if Self-healing
C0121ENb
FIGURE 7: J14 PIN OUT

4. SWU20X RANGE - STAR ARCHITECTURE

The SWU20x range of Ethernet boards is dedicated to Ethernet Star architecture and
defined by the optional type of Ethernet optical fibre it is connected (single Mode or Multi
Mode). All equipment of the SWU20x range has 4 Copper connections through RJ45, with
speed automatically adjusted from external emitters to 10 or 100 Mbps, and optionally 2
Ethernet optical ports.
The Ethernet dual homing star is based on optical connection; depending on the link length
the user may choose between Multi-mode optic Fibre (up to 2km) and Single mode optic
Fibre for long distance (up to 20km).

SWU200
Fast Ethernet industrial switch 4 x RJ45
Ref: 2070745 A01
SWU202 Fast Ethernet industrial switch 4 x RJ45
Ref: 2070745 A03 Multimode 1300 nm 2 x ST
SWU204 Fast Ethernet industrial switch 4 x RJ45
Ref: 2070745 A05 Single mode 1310 nm 2 x SC
4.1 Ethernet Port Characteristics

4.1.1 10/100BaseTx Port
Connector type Shielded RJ45 jack

Twisted pair cable Cat 5
Max cable length with Cat 5 100m
4.1.2 100BaseFx Multi Mode Port
Fibre port connector ST

Optimal fibre cable 62,5/125 μm or 50/125 μm
Center wavelength 1300 nm
TX output power -19 dBm
RX input sensitivity -31 dBm
Maximum distance 2000 m
Half or full Duplex Switch selectable
4.1.3 100BaseFx Single or Mono Mode Port
Fibre port connector SC

Optimal fibre cable 9/125 or 10/125 μm
Center wavelength 1310 nm
TX output power -15 dBm
RX input sensitivity -34 dBm
Maximum distance 20 000 m
Half or full Duplex Switch selectable
4.2 Ethernet Port Switching Features

SWUxxx determines automatically at message reception the speed of its transmission layer
10 or 100 Mbps SWUxxx adapts automatically itself to this transmission speed and other
transmission parameters like half or full duplex.
4.2.1 10BaseTx and 100BaseTx
The copper ports are full/half duplex and auto-sense the transmission speed. They will auto-
negociate with the connected device to determinate the optimal speed. When the connected
device is only capable of transmitting at 10Mbps, the SWUxxx follows the 10Mbps.
4.2.2 100Base Fx
The fibre optic ports are full/half duplex at 100Mbps.
4.3 Ethernet Management
4.3.1 Address look up
Each Ethernet device inserts its unique “MAC address” into each message it send out. The
port on the SWUxxx used for given MAC address is automatically learned when a frame is
received from that address. Once an address is learned, the SWUxxx will route messages to
only the appropriate port. A time stamp is also placed in memory when a new address is
learned. This time stamp is used with the aging feature, which will remove unnused MAC
Addresses from table after 300 seconds. The broadcasting messages are transmit in the all
ports.
Up to 1024 MAC addresses can be stored and monitored at any time.
4.3.2 Buffering
An internal buffer is used for buffering the messages. There are 1024 buffers available. The
factory setting mode adaptively allocates buffers up to 512 to a single port based loading.
4.3.3 Back off operation
The SWUxxx will drop a packet after 16 collisions.
4.3.4 Back pressure for half duplex
The SWUxxx will apply « back pressure » when necessary with half-duplex operation. This
«back pressure » will reduce congestion on busy networks (J factory setting).
4.3.5 Broadcast storm protection
Broadcasts and multicasts are limited to 5% of the available bandwidth.
4.3.6 Auto Negotiation and Speed-Sensing
All the 4 RJ45 ports of the SWUxxx independently support auto negotiation for speeds in the
10BaseT and 100BaseTx modes. Operation is according to the IEEE 802.3u standard.
4.3.7 Forwarding
SWUxxx supports store and forward mode. SWUxxx will forward messages with know
addresses out only the appropriate port. Messages with unknown addresses, broadcast
messages and multicast messages will get forwarded out all ports except the source port.
SWUxxx will not forward error packets, 802.3x pause frames or local paquets.
4.3.8 Priority tagging
802.1p priority is enabled on all ports. A 6 KB buffer is reserved for priority traffic.
4.3.8.1 Flow control

The switch automatically supports standard flow control frames on both the transmission and
reception sides.
On the reception side, if SWUxxx receives a pause control frame it will not transmit the next
normal frame until the timer, specified in the pause control frame, expires. If another pause
frame is received before the current timer expires, the timer will be updated with the new
value in the second pause frame. During this period (being flow controlled), only flow control
packets from SWUxxx will be transmitted.
On the transmission side, SWUxxx efficient ways to determine when to invoke flow control.
The flow control is based on availability of the system resources, including available buffers,
available transmission queues and available reception queues. SWUxxx will flow control a
port, which just received a packet, if the destination port resource is being used up. SWUxxx
will issue a flow control frame (XOFF), containing the maximum pause time defined in IEEE
standard 802.3x. A hysteresis feature is provided to prevent flow control mechanism from
being activated and deactivated too many times.
SWUxxx will flow control all ports if the reception queue becomes full.
BLANK PAGE
Customer Care Centre
http://www.schneider-electric.com/CCC
© 2011 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 T/C80 10/2011

RTU Training Course Description 2014

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

RTU Training Course Description 2014

Hochgeladen von

Copyright:

Verfügbare Formate

MiCOM C264/C264C

MiCOM C264/C264C Page 1/2

Safety & Handling C264/EN SA/C80

Introduction C264/EN IT/C80

Technical Data C264/EN TD/C80

Functional Description C264/EN FT/C80

Hardware C264/EN HW/C80

Connection C264/EN CO/C80

Installation C264/EN IN/C80

Settings C264/EN ST/C80

Communications C264/EN CT/C80

Commissioning C264/EN CM/C80

Commissioning Record Sheet C264/EN RS/C80

Maintenance C264/EN MF/C80

Lexicon C264/EN LX/C80

ANNEX: Communication ETHERNET Switches C264/EN AN/C80

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